You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened:
Failed to pull cdi-operator container image.
What you expected to happen:
I would have expected that after creating the cdi-operator, it would have pulled the image from quay and I would have the cdi-operator running.
How to reproduce it (as minimally and precisely as possible):
I ran this, and no dice:
Happy to help with a fix, if you point me in the direction of past art and/or where in the codebase I might need to look at to revamp this. I tried on 2 versions: v1.61.0 & v1.60.4. Also happy to provide more context if needed. Thanks!
What happened:
Failed to pull cdi-operator container image.
What you expected to happen:
I would have expected that after creating the cdi-operator, it would have pulled the image from quay and I would have the cdi-operator running.
How to reproduce it (as minimally and precisely as possible):
I ran this, and no dice:
Additional context:
It appears that the Image is not sync'd up with the Image ID (as in the Image ID is empty). However the image does exist in quay: https://quay.io/repository/kubevirt/cdi-operator?tab=tags&tag=v1.60.4
After running
kubectl describe po cdi-operator-8f5f4b54b-bcnh4
:Environment:
kubectl get deployments cdi-deployment -o yaml
):I used
kubectl get deployments cdi-operator -o yaml
:kubectl version
):uname -a
):The text was updated successfully, but these errors were encountered: