openQA Project (public) » openQA Infrastructure (public)

Motivation¶

I observed on https://openqa.suse.de/admin/workers that openqa-piworker had old os-autoinst version. On the host we confirmed that the package is up-to-date but the openQA workers were not restarted yet. For historical reasons the node was brought into salt as "generic" machine, not "worker" causing this and multiple inconsistencies. We should make sure the machine is treated as proper worker

Acceptance criteria¶

• AC1: openqa-piworker has salt role "worker" and salt high state cleanly applied
• AC2: RPi related openQA jobs on related nodes still work as expected
• AC3: No related alerts for old "generic" openqa-piworker or "worker" openqa-piworker in https://monitor.qa.suse.de

Suggestions¶

• Add the role as documented in https://gitlab.suse.de/openqa/salt-states-openqa#openqa-salt-states and apply a high state as test with e.g. salt-call --local state.test or from OSD salt --state-output=changes 'openqa-piworker* state.test and then apply without test if ok
• Ensure RPi related openQA jobs on related nodes still work as expected
• Ensure no related alerts for old "generic" openqa-piworker or "worker" openqa-piworker in https://monitor.qa.suse.de