QA » openQA Project » openQA Infrastructure

As the Virt squad is looking for new bare-metal testing hardware I mentioned the available hardware and that it could be used for that purpose. See https://suse.slack.com/archives/C02CGKV748P/p1716970043840679?thread_ts=1716792965.061679&cid=C02CGKV748P for context.
We should take https://racktables.suse.de/index.php?page=object&tab=default&object_id=1160 and https://racktables.suse.de/index.php?page=object&tab=default&object_id=10126 as reference and get IPMI and system ethernet connected with the help of IT accordingly for bare-metal testing.

cachen wrote in #note-9:

Hello @okurz Oli, is there any progress on this setup?

Unfortunately not otherwise progress would be visible here. But I already made the team aware about the urgency.

I must kickoff my HW purchase process on earlier July, very appreciate if we can have the final verification of these 4 nodes for Virtualization team by end of June. Thank you!

Understood, bumped to "Urgent".

okurz wrote in #note-18:

@ybonatakis why did you add only worker41 and worker44 and not 42 and 43? Also you need the IPMI interfaces, e.g. "worker41-ipmi" and such

on it.
I noticed the missing machines yesterday. For the ipmi I will have to ask you

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

ybonatakis wrote in #note-20:

https://gitlab.suse.de/OPS-Service/salt/-/merge_requests/5202 submitted but without the IPMI. I hope we can take a look at it during the unblock meeting

#5202 is closed. new PR https://gitlab.suse.de/OPS-Service/salt/-/merge_requests/5209

1. https://gitlab.suse.de/OPS-Service/salt/-/merge_requests/5209 was merged. As you also changed IPv4 addresses for suttner1+2 which are the DHCP servers and have a static configuration: Did you coordinate the change with someone from IT? If not I suggest you propose that you do the change yourself ask IT for approval and them to stand by in case you loose SSH access.
2. to ensure timely updates immediate/urgent tickets must never be in status "Blocked" or "Feedback", see https://progress.opensuse.org/projects/qa/wiki/Tools#SLAs-service-level-agreements
3. Please prioritize verifying the functionality of the hardware to be able to meet the time expectations as layed out by @cachen in #134081-9
4. Update racktables entries accordingly in https://racktables.nue.suse.com/index.php?page=object&object_id=23373 and the sub-elements

changes are in place and indeed suttner1+2 as well as the other new machines are not accessible.
I tried to reach out to IT guys https://suse.slack.com/archives/C029APBKLGK/p1719236874744979.

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