Project

General

Profile

Actions
Copy link

action #174583

open

openqa/scripts-ci pipeline fails, jobs obsoleted

Added by jbaier_cz about 6 hours ago. Updated about 5 hours ago.

Status:
Feedback
Priority:
Normal
Assignee:
gpuliti
Category:
Regressions/Crashes
Target version:
Ready
Start date:
2024-12-19
Due date:
% Done:

100%

Estimated time:
Tags:
alert, infra, reactive work

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
Actions
Copy link
 #1

Updated by jbaier_cz about 5 hours ago

  • Description updated (diff)
Actions
Copy link
 #2

Updated by okurz about 5 hours ago

  • Tags changed from alert to alert, infra, reactive work
  • Priority changed from High to Urgent
Actions
Copy link
 #3

Updated by gpuliti about 5 hours ago

  • Assignee set to gpuliti
Actions
Copy link
 #4

Updated by jbaier_cz about 5 hours ago

  • Description updated (diff)
Actions
Copy link
 #5

Updated by livdywan about 5 hours ago

  • Description updated (diff)
Actions
Copy link
 #6

Updated by gpuliti about 5 hours ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

I've rerun the job and now is successful https://gitlab.suse.de/openqa/scripts-ci/-/jobs/3564579

Actions
Copy link
 #7

Updated by jbaier_cz about 5 hours ago

  • 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.

Actions
Copy link

Also available in: Atom PDF