Actions
action #178306
opencoordination #110833: [saga][epic] Scale up: openQA can handle a schedule of 100k jobs with 1k worker instances
coordination #178243: [epic] More efficient handling of big job schedules, not executable jobs, never matching worker classes, etc.
Detect jobs that can not be picked up by any current matching worker class
Start date:
2025-03-05
Due date:
% Done:
0%
Estimated time:
Description
Motivation¶
In particular on OSD we can often observe that there are some tests scheduled with worker class combinations that are never fulfilled by any currently or recently registered worker instance. To be able to better inform test owners about that misconfiguration as well as to improve our alerting on unexpected cases we should we detect jobs that can not be picked up by any current matching worker class and provide clear user feedback for those jobs
Acceptance Criteria¶
- AC1: The job status as requested over at least API provides clear indication if there is currently or recently no registered worker for the selected worker class combination
Suggestions¶
- Look up potentially matching worker class combinations whenever the status of a scheduled job is requested, e.g. when displaying
/tests/<id>
or/api/v1/jobs/<id>
- Don't duplicate code that the scheduler itself already has
Updated by okurz about 1 month ago
- Copied from action #178204: Reduce test start time on openqa.suse.de size:S added
Actions