action #174583
open
openqa/scripts-ci pipeline fails, jobs obsoleted
Added by jbaier_cz about 7 hours ago.
Updated about 5 hours ago.
Category:
Regressions/Crashes
Description
Observation¶
The pipeline is failing because the openQA jobs got obsoleted:
See: https://gitlab.suse.de/openqa/scripts-ci/-/pipelines/1472522
{"blocked_by_id":null,"id":4713396,"result":"obsoleted","state":"done"}
{"blocked_by_id":null,"id":4713397,"result":"obsoleted","state":"done"}
Suggestions¶
- Verify if this is a specific worker or workers and take them out of production
- Consider restarting affected jobs
- Description updated (diff)
- Tags changed from alert to alert, infra, reactive work
- Priority changed from High to Urgent
- Description updated (diff)
- Description updated (diff)
- Status changed from New to Resolved
- % Done changed from 0 to 100
- Status changed from Resolved to Feedback
- Priority changed from Urgent to Normal
That won't stop the issue from happening again. Of course the rerun helped, because now the openQA jobs are not obsoleted (and that mitigates the urgency). IMHO the solution to this ticket is to not consider obsoleted jobs as a failure in the pipeline.
Also available in: Atom
PDF