QA (public) » openQA Project (public) » openQA Infrastructure (public)

Waiting for response from Viktor Karpovych who contacted me by DM

There was no response so far.

vkarpovych answered, I responded:

Oliver Kurz: https://confluence.suse.com/display/qasle/2022-05-16+SUSE+IT+and+Networking has the corresponding entry: "Prague status: Discuss where to locate new QE-SAP servers: Could ask about Rack B4 or B5 - the servers are old and could maybe go to make space for SAP ? (they were cloud/SES, all out of warranty)". I don't have more details the current status, that's on mcaj and lmartin
Viktor Karpovych: those 3 servers occupy some space in Storage room, I want to mount it to Rack PRG-SRV1-B :5 just for space release in storage room.
Could I just put it to bottom of that rack? How to name those servers for put it to Racktables and after PDUs and Network Switches arrived and we will move everything from Rack 5 we can decide in which units those servers will be moved.
Oliver Kurz: Sounds ok. Please name them openqaworker16, openqaworker17, openqaworker18 with configuration and network setup same as openqaworker14+15. Those machines were setup by mcaj last year IIRC

racktable entries:

• openqaworker16
• openqaworker17
• openqaworker18

I have received no response since a month so I assume we are still waiting for network switches or somebody forgot to continue. I suggest to report a ticket with SUSE-IT to request the further setup steps.

Request for network connection done in https://sd.suse.com/servicedesk/customer/portal/1/SD-99844

cool. We have access to the SD ticket so we can treat this as "Blocked"

no further update till today. Asked again and move due date

I have received IPMI credentials and can confirm that I can access.

https://gitlab.suse.de/openqa/salt-pillars-openqa/-/merge_requests/466

for IPMI credentials.
https://sd.suse.com/servicedesk/customer/portal/1/SD-99844 is still open. I commented there:

Could you please add L2 address entries on racktables as well? E.g. on https://racktables.nue.suse.com/index.php?page=object&tab=default&object_id=17946 . I think that’s all that is left to do for the work in this ticket.

However now we can already continue the work to setup the machines as OSD workers.

I had to disable legacy boot again since we need to boot from NVMes which is only possible with UEFI. I chose "hybrid mode" which might still allow PXE boot but the booting OS will not be able to install the OS in a way the system can access it later on after installing. Therefore I had to use IPMIView from Supermicro to mount a installer disk and boot from it in UEFI mode. Worker 16 and 17 are accessible now, salt-minion is installed but not yet connected to our infrastructure. Worker 18 still needs an OS.

Setting due date based on mean cycle time of SUSE QE Tools

I think an update got lost here. We discussed it in the infra daily yesterday and confirmed that Nick is still looking into setting up worker 18 with salt, delayed mainly due to #123028.

We decided that due to the update regarding new QE labs in Nbg FC we did not actually conclude with that. This is free to be picked up by anybody again. Next steps:

• Come up with fitting worker config in salt pillars (likely prerequisite for successful high state application) with "test" worker class
• Accept salt key of one machine on osd, apply high state
• After successful high state trigger openQA jobs on that worker for testing
• Use production worker class
• Repeat above steps for 2nd and 3rd machine

1) serial is directed to wrong port -> ipmi stops working during initrd initialization.
2) WebUI works correctly only in Firefox.

Setting due date based on mean cycle time of SUSE QE Tools

https://gitlab.suse.de/openqa/salt-pillars-openqa/-/merge_requests/491 - merged ( deploy CI failed, but we don't know why because Gitlab truncated log ), salt openqa.... atate.apply passed and workers seems working as intendet --> setting to feedback

PS: WebUI of supermicro on this workers usualy hangs in any browser except anonymous mode ( clean new run of browser )

Examples of successfully executed jobs:

• worker16 / https://openqa.suse.de/tests/10503349
• worker17 / https://openqa.suse.de/tests/10505095
• worker18 / https://openqa.suse.de/tests/10503829

Looks like things are working well.