Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

quay flake: 502 Bad Gateway #17802

Open
edsantiago opened this issue Mar 15, 2023 · 2 comments
Open

quay flake: 502 Bad Gateway #17802

edsantiago opened this issue Mar 15, 2023 · 2 comments
Labels
flakes Flakes from Continuous Integration

Comments

@edsantiago
Copy link
Member

Seeing this one a lot recently, many different variations across many CI runs:

Error: initializing source docker://quay.io/libpod/alpine:latest: Requesting bearer token: invalid status code from registry 502 (Bad Gateway)

Error: copying system image from manifest list: determining manifest MIME type for docker://quay.io/libpod/testimage:00000004:
    reading manifest sha256:xxx in quay.io/libpod/testimage: received unexpected HTTP status: 502 Bad Gateway

Error: reading blob sha256:xxx: fetching blob: received unexpected HTTP status: 502 Bad Gateway
@edsantiago edsantiago added the flakes Flakes from Continuous Integration label Mar 15, 2023
@edsantiago
Copy link
Member Author

This has blown up today. I don't think it's related to #18124 (new VM images) because #18140, if I'm reading git-log correctly, is based on an earlier main that does not include those VMs. So it's something broken in quay today. (Yes, I checked https://status.quay.io/ - nothing reported, but that's always the case even when we're seeing major breakage).

@github-actions
Copy link

A friendly reminder that this issue had no activity for 30 days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flakes Flakes from Continuous Integration
Projects
None yet
Development

No branches or pull requests

2 participants