Actions
action #160802
closedbot-ng and openQABot pipelines fail to pull containers from registry.suse.de - again
Status:
Resolved
Priority:
High
Assignee:
Category:
Regressions/Crashes
Target version:
Start date:
2023-10-23
Due date:
% Done:
0%
Estimated time:
Tags:
Description
Observation¶
https://gitlab.suse.de/qa-maintenance/bot-ng/-/jobs/2647221
ERROR: Job failed: failed to pull image "registry.suse.de/qa/maintenance/containers/qam-ci-leap:latest" with specified policies [always]: Error response from daemon: received unexpected HTTP status: 503 Service Unavailable (manager.go:250:9s)
This is causing many pipeline failure emails.
Acceptance Criteria¶
- AC1: Pipelines relying on registry.suse.de are known to work
Rollback steps¶
- DONE Re-activate pipelines https://gitlab.suse.de/qa-maintenance/bot-ng/-/pipeline_schedules
- Approve incidents (28,58 * * * *)
- Synchronize inc. results into QEM Dashboard (8,38 * * * *)
- Synchronize aggr. results into QEM Dashboard (3,33 * * * *)
- Synchronize SMELT to QEM Dashboard (3,33 * * * *)
Suggestions¶
- File an SD ticket
- Look into a way to ensure we retry those pipelines - if we don't yet
- Consider alternatives to avoid the waves of un-actionable alert emails
Updated by livdywan about 2 months ago
- Copied from action #138377: bot-ng and openQABot pipelines fail to pull containers from registry.suse.de size:M added
Updated by livdywan about 2 months ago
- Status changed from In Progress to Blocked
Updated by livdywan about 2 months ago
- Description updated (diff)
- Status changed from Blocked to In Progress
livdywan wrote in #note-3:
Blocking on https://sd.suse.com/servicedesk/customer/portal/1/SD-157761
https://suse.slack.com/archives/C02BXKBMXNV/p1716463246475349
Well, it "should work again" so let's see if it will
Updated by livdywan about 2 months ago
- Status changed from In Progress to Resolved
Recent runs are good I guess: https://gitlab.suse.de/qa-maintenance/bot-ng/-/jobs
Actions