action #150869
Updated by mkittler 23 days ago
## Motivation As part of #136133 aarch64-o3 was ensured to be working from FC Basement but not capable yet to run openQA multi-machine tests. As this machine may be the only one able to execute aarch32 jobs the machine should be setup for multi-machine tests accordingly. ## Acceptance criteria * **AC1:** Only one machine is successfully working on aarch32 o3 multi-machine jobs at a time * **AC2:** Inventory management systems are up-to-date * **AC3:** The machine is not connected to any other o3 machines by GRE tunnels ## Suggestions * Find out why other openQA workers connected to o3 already successfully do aarch32 multi-machine tests like oss-cobbler-03 in https://openqa.opensuse.org/tests/latest?arch=arm&distri=opensuse&flavor=NET&machine=aarch32&test=wicked_basic_ref&version=Tumbleweed * ~~Talk Talk to ggardet to resolve that conflict to ensure that there is only one machine executing aarch32 MM jobs at a time as we can't have GRE tunnels to all and we don't have a feature yet to limit clusters to a single machine yet, see #135035~~ We have `PARALLEL_ONE_HOST_ONLY=1` now which could be added to relevant test scenarios (but #158146 is still open) #135035 * Execute `os-autoinst-setup-multi-machine` on aarch64-o3, add "tap" to worker instances * Find a scenario to test the MM setup, use "wicked_basic_sut/ref" https://openqa.opensuse.org/tests/latest?arch=arm&distri=opensuse&flavor=NET&machine=aarch32&test=wicked_basic_ref&version=Tumbleweed * Do not add GRE tunnels to other o3 machines as this machine should be the only one working on aarch32 MM jobs * Inventory management systems are probably already up to date ## Further details Currently openQA would schedule MM jobs for all workers with a matching worker class connected to one openQA instance. But if those workers can not reach each other which we normally achieve with GRE tunnels then those jobs would fail. And we shouldn't try to connect an ARM/ggardet maintained cloud ARM machine like oss-cobbler-03 to a SUSE internal machine due to security best practices. Hence there should be only machine it a time for a matching worker class to work on such jobs.