action #94765
Updated by okurz over 3 years ago
## Motivation
See #93050#note-15
## Acceptance criteria
* **AC1:** openqaworker12 is verified to use for production multi-machine tests
* **AC2:** Same as AC1 but after additional reboots to ensure reboot stability
* **AC3:** openqaworker12 is controlled over salt
## Suggestions
* Look into the error report of #93050#note-15
* Find a good "multi-machine test scenario" to verify
* Bring the machine up with a dedicated worker class selection for investigation, e.g. `openqaworker12,tap`
* Fix any found problems
* Accept salt key for openqaworker12 on osd `sudo salt-key -y -a openqaworker12.suse.de`
* Apply full salt state and check for success
* Unpause "openqaworker12: host up alert" https://stats.openqa-monitor.qa.suse.de/alerting/list?state=not_ok
* Crosscheck monitoring results
## Further details
As alternative to fixing multi-machine we can also remove the "tap" from worker class settings and bring back the machine for single-machine jobs only first