-
Bug
-
Resolution: Done
-
Major
-
None
-
4.11.z
-
None
-
Proposed
-
True
-
-
When deploying HardwareEvent CR with BMER operator in 4.11.12, hw-event-proxy pod failed to deploy due to error in pulling image.
$ oc get pods NAME READY STATUS RESTARTS AGE hw-event-proxy-5694d674fc-gfxqw 2/3 ImagePullBackOff 0 12m $ oc describe pod hw-event-proxy-5694d674fc-gfxqw Name: hw-event-proxy-5694d674fc-gfxqw Namespace: openshift-bare-metal-events Priority: 0 Node: cnfde10.ptp.lab.eng.bos.redhat.com/10.16.231.49 Start Time: Mon, 31 Oct 2022 16:52:28 -0400 Labels: app=hw-event-proxy pod-template-hash=5694d674fc .... Warning Failed 7m49s (x3 over 8m31s) kubelet Error: ErrImagePull Warning Failed 7m49s (x3 over 8m31s) kubelet Failed to pull image "registry.redhat.io/openshift4/baremetal-hardware-event-proxy-rhel8@sha256:7d6012066ffafc3c1c6511df807ce627fb51332c3cf10502fcaabef9ac6595f5": rpc error: code = Unknown desc = reading manifest sha256:7d6012066ffafc3c1c6511df807ce627fb51332c3cf10502fcaabef9ac6595f5 in registry.redhat.io/openshift4/baremetal-hardware-event-proxy-rhel8: unsupported: Not Found, or unsupported. V2 schema 1 manifest digest are no longer supported for image pulls. Use the equivalent schema 2 manifest digest instead. For more information see https://access.redhat.com/articles/6138332 Normal Pulling 7m49s (x3 over 8m32s) kubelet Pulling image "registry.redhat.io/openshift4/baremetal-hardware-event-proxy-rhel8@sha256:7d6012066ffafc3c1c6511df807ce627fb51332c3cf10502fcaabef9ac6595f5" Warning Failed 7m20s (x4 over 8m15s) kubelet Error: ImagePullBackOff Normal BackOff 3m24s (x20 over 8m15s) kubelet Back-off pulling image "registry.redhat.io/openshift4/baremetal-hardware-event-proxy-rhel8@sha256:7d6012066ffafc3c1c6511df807ce627fb51332c3cf10502fcaabef9ac6595f5"