Pods fails with ImagePullBackOff after upgrade from 4.13 to 4.14

Solution Verified - Updated -

Issue

  • Pods using images that are stored in the default OpenShift internal registry fails to be pull:
112s        Warning   Failed              pod/new-default-deploy-547ccb8549-9wll5    Failed to pull image "default-route-openshift-image-registry.apps.mycluster.aroapp.io/new-default-app/ubi8:latest": rpc error: code = Unknown desc = reading manifest latest in default-route-openshift-image-registry.apps.mycluster.aroapp.io/new-default-app/ubi8: manifest unknown
112s        Normal    Pulling             pod/new-default-deploy-547ccb8549-9wll5    Pulling image "default-route-openshift-image-registry.apps.mycluster.aroapp.io/new-default-app/ubi8:latest"
112s        Warning   Failed              pod/new-default-deploy-547ccb8549-9wll5    Error: ErrImagePull
98s         Warning   Failed              pod/new-default-deploy-547ccb8549-9wll5    Error: ImagePullBackOff
84s         Normal    BackOff             pod/new-default-deploy-547ccb8549-9wll5    Back-off pulling image "default-route-openshift-image-registry.apps.mycluster.aroapp.io/new-default-app/ubi8:latest"

Environment

  • Managed Microsoft Azure Red Hat OpenShift (ARO)
  • Red Hat OpenShift on Azure (RHOCP on Azure)

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content