Project

General

Profile

Actions

action #160802

closed

bot-ng and openQABot pipelines fail to pull containers from registry.suse.de - again

Added by livdywan 23 days ago. Updated 22 days ago.

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

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

Related issues 1 (0 open1 closed)

Copied from openQA Infrastructure - action #138377: bot-ng and openQABot pipelines fail to pull containers from registry.suse.de size:MResolvedlivdywan2023-10-232023-11-08

Actions
Actions #1

Updated by livdywan 23 days ago

  • Copied from action #138377: bot-ng and openQABot pipelines fail to pull containers from registry.suse.de size:M added
Actions #2

Updated by livdywan 23 days ago

  • Description updated (diff)
Actions #3

Updated by livdywan 23 days ago

  • Status changed from In Progress to Blocked
Actions #4

Updated by livdywan 22 days 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

Actions #5

Updated by livdywan 22 days ago

  • Status changed from In Progress to Resolved
Actions

Also available in: Atom PDF