action #161819
closedRegistry 3.126.238.126:5000 is broken
0%
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
Updated by mloviska about 1 month ago
- Status changed from New to Workable
- Priority changed from High to Urgent
Updated by rbranco about 1 month ago
- Status changed from Workable to In Progress
Updated by rbranco about 1 month 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
Updated by szarate about 1 month 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.
Updated by rbranco about 1 month 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.
Updated by rbranco about 1 month ago
- Status changed from In Progress to Resolved