action #160802
Updated by livdywan about 2 months ago
## 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