Intermittent Error creating pod: container failed to start, ImagePullBackOff

Get Help
, , ,
1

Has anyone ever run into this error with AWX-operator? It just started happening to me today intermittently. I launch my Job Templates and sometimes they fail with this error:

Error creating pod: container failed to start, ImagePullBackOff

I am running AWX-operator on a K3 kubernetes cluster.
On froom k8 dashboard I see this error:

Failed to pull image "quay.io/ansible/awx-ee:latest": rpc error: code = Unknown desc = failed to pull and unpack image "quay.io/ansible/awx-ee:latest": failed to resolve reference "quay.io/ansible/awx-ee:latest": pulling from host quay.io failed with status code [manifests latest]: 502 Bad Gateway

Is there something up with quay.io?

Thanks

2

Apologizes for answering my own question and not checking before posting but quay.io is having an major outage.

Screenshot 2023-11-14 at 1.44.42 PM
Screenshot 2023-11-14 at 1.44.42 PM1355×500 50 KB

2 Likes
3

yep…

would u mind marking this topic solved

1 Like
4

Would using something like OpenShift have helped with reliable access to containers?

5

For AWX not really since we host image on Quay.

6

Thanks. I understand. Quay did fix the problem pretty quickly, but can you recommend a course of action that could make my AWX more resilient to such outages?

1 Like
7

Mirroring to a private image registry and deploy using private image registry would probably work.

2 Likes
8

Also we have the image in ghcr.io/ansible as well. This is our staging image registry

1 Like
9

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.