action #123382
closedrepurpose openqaworker-arm-3 as baremetal worker
0%
Description
After handing over "unarmed" to serve as openQA worker, we agreed to repurpose openqaworker-arm-3 for baremetal testing on arm in exchange.
In order to do so we have to:
- disable the workers on this machine and remove them from osd
- add an ipmi worker configuration similar to our other baremetal machines
- configure ipxe boot via pxe/tftp environment
Updated by okurz over 2 years ago
- Tags set to infra
- Status changed from New to Feedback
- Assignee set to okurz
- Target version set to Ready
Let me track that for you.
Updated by MMoese over 2 years ago
Updated by okurz about 2 years ago
@MMoese can you clarify who is using "unarmed" currently?
What's up with https://gitlab.suse.de/qa-sle/qanet-configs/-/merge_requests/47?
Updated by okurz about 2 years ago
- Due date set to 2023-03-24
I asked in https://suse.slack.com/archives/C02CANHLANP/p1678452529647499
@Michael Moese @Felix Niederwanger @Santiago Zarate Regarding https://progress.opensuse.org/issues/123382 and https://progress.opensuse.org/issues/123382 I assume that openqaworker-arm-3 will stay with OSD and you move back unarmed to kernel testing and we can close https://gitlab.suse.de/qa-sle/qanet-configs/-/merge_requests/47 ?
If there is no response then I will close the qanet-configs MR and we keep openqaworker-arm-3 in OSD testing.
Updated by okurz about 2 years ago
- Due date deleted (
2023-03-24) - Status changed from Feedback to Resolved
https://gitlab.suse.de/qa-sle/qanet-configs/-/merge_requests/47 is closed. openqaworker-arm-3 is part of active salt config on OSD and I checked on the machine, the openQA worker instances are alive and running and working on jobs.