Actions
action #162455
openopenQA Project - coordination #112862: [saga][epic] Future ideas for easy multi-machine handling: MM-tests as first-class citizens
openQA Project - coordination #111929: [epic] Stable multi-machine tests covering multiple physical workers
Secondary TAP worker class instead of "tap_poo…" on closed tickets
Status:
Feedback
Priority:
Low
Assignee:
Category:
Feature requests
Target version:
Start date:
2024-06-18
Due date:
2024-07-13 (Due in 13 days)
% Done:
0%
Estimated time:
Tags:
Description
Motivation¶
With #160652 we introduced the concept of "tap_secondary" as a worker class for hosts that are for indefinite time disabled from multi-machine tests but right now still have references like "tap_poo136130" even though #136130 is already closed for longer. We should revisit all "tap_poo[,]*" classes and use "tap_secondary" for all with no open ticket as reference and where it makes sense to keep the host out of production "tap" for good.
Acceptance criteria¶
- AC1: https://gitlab.suse.de/openqa/salt-pillars-openqa/-/blob/master/openqa/workerconf.sls has no mention of "tap_poo[,]*" for any closed ticket
- AC2: We can still explicitly schedule multi-machine tests on those workers
Suggestions¶
- Revisit all "tap_poo[,]*" classes and use "tap_secondary" for all with no open ticket as reference and where it makes sense to keep the host out of production "tap" for good.
Actions