Project

General

Profile

Actions
Copy link

action #161819

closed

Registry 3.126.238.126:5000 is broken

Added by ggardet_arm 25 days ago. Updated 25 days ago.

Status:
Resolved
Priority:
Urgent
Assignee:
rbranco
Category:
Bugs in existing tests
Target version:
-
Start date:
2024-06-05
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario microos-Tumbleweed-DVD-aarch64-container-host@aarch64-4G-HD40G fails in
podman_3rd_party_images

Multiple tests (podman, docker, etc.) are failing because of registry 3.126.238.126:5000

Test suite description

Reproducible

Fails since (at least) Build 20240604

Expected result

Last good: 20240603 (or more recent)

Further details

Always latest result in this scenario: latest

Actions
Copy link
 #1

Updated by mloviska 25 days ago

  • Status changed from New to Workable
  • Priority changed from High to Urgent
Actions
Copy link
 #2

Updated by rbranco 25 days ago

  • Assignee set to rbranco
Actions
Copy link
 #3

Updated by rbranco 25 days ago

  • Status changed from Workable to In Progress
Actions
Copy link
 #4

Updated by rbranco 25 days ago

Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit

Actions
Copy link
 #5

Updated by szarate 25 days ago

I'm thinking about #155059. Is it possible to cache these images on a local registry or something? I mean, we don't have to test the images on the bleeding edge.

Actions
Copy link
 #7

Updated by rbranco 25 days ago

I created an account in Docker Hub to have twice the rate limit. Restarting tests.

After the mirror is populated I will freeze it.

Actions
Copy link
 #8

Updated by rbranco 25 days ago

  • Status changed from In Progress to Resolved
Actions
Copy link

Also available in: Atom PDF