Description of problem (please be detailed as possible and provide log snippests): During the deploy of OFD 4.9 the CSV is failing to install. Version of all relevant components (if applicable): 4.9 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? Yes Is there any workaround available to the best of your knowledge? No Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? 1 Can this issue reproducible? Yes Can this issue reproduce from the UI? N/A If this is a regression, please provide more details to justify this: Yes. This was working in previous levels. Steps to Reproduce: 1.Deploy ODF 4.9 on OCP 4.9. 2. 3. Actual results: [root@rdr-sri-b76e-lon06-bastion-0 ~]# oc describe pod odf-operator-controller-manager-655446dd6-rgbzd -n openshift-storage Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 42m default-scheduler Successfully assigned openshift-storage/odf-operator-controller-manager-655446dd6-rgbzd to rdr-sri-b76e-lon06-worker-0 Normal AddedInterface 42m multus Add eth0 [10.128.2.12/23] from openshift-sdn Warning Failed 41m kubelet Failed to pull image "registry.redhat.io/openshift4/ose-kube-rbac-proxy:v4.7.0": rpc error: code = Unknown desc = can't talk to a V1 container registry Normal Pulling 41m kubelet Pulling image "quay.io/rhceph-dev/odf-operator@sha256:55a4880999850da3917934396df84c93ed5678deb035b202b63b94e3883e7544" Normal Pulled 41m kubelet Successfully pulled image "quay.io/rhceph-dev/odf-operator@sha256:55a4880999850da3917934396df84c93ed5678deb035b202b63b94e3883e7544" in 7.796474757s Normal Started 41m kubelet Started container manager Normal Created 41m kubelet Created container manager Warning Failed 39m kubelet Failed to pull image "registry.redhat.io/openshift4/ose-kube-rbac-proxy:v4.7.0": rpc error: code = Unknown desc = reading manifest v4.7.0 in registry.redhat.io/openshift4/ose-kube-rbac-proxy: received unexpected HTTP status: 503 Service Unavailable Normal Pulling 39m (x3 over 42m) kubelet Pulling image "registry.redhat.io/openshift4/ose-kube-rbac-proxy:v4.7.0" Warning Failed 37m (x3 over 41m) kubelet Error: ErrImagePull Warning Failed 36m (x6 over 41m) kubelet Error: ImagePullBackOff Warning Failed 26m (x4 over 37m) kubelet Failed to pull image "registry.redhat.io/openshift4/ose-kube-rbac-proxy:v4.7.0": rpc error: code = Unknown desc = pinging container registry registry.redhat.io: invalid status code from registry 503 (Service Unavailable) Warning Failed 9m38s kubelet Failed to pull image "registry.redhat.io/openshift4/ose-kube-rbac-proxy:v4.7.0": rpc error: code = Unknown desc = pinging container registry registry.redhat.io: invalid status code from registry 504 (Gateway Timeout) Normal BackOff 2m33s (x93 over 41m) kubelet Back-off pulling image "registry.redhat.io/openshift4/ose-kube-rbac-proxy:v4.7.0" [root@rdr-sri-b76e-lon06-bastion-0 ~]# oc get csv -A NAMESPACE NAME DISPLAY VERSION REPLACES PHASE openshift-local-storage local-storage-operator.4.9.0-202109071344 Local Storage 4.9.0-202109071344 Succeeded openshift-operator-lifecycle-manager packageserver Package Server 0.18.3 Succeeded openshift-storage noobaa-operator.v4.9.0-158.ci NooBaa Operator 4.9.0-158.ci Succeeded openshift-storage ocs-operator.v4.9.0-158.ci OpenShift Container Storage 4.9.0-158.ci Succeeded openshift-storage odf-operator.v4.9.0-158.ci OpenShift Data Foundation 4.9.0-158.ci Failed Expected results: Additional info:
This is for IBM System P environment.
@svenkat Can you pls try this again? It should be able to pull the image. If it does not work pls let us know.
We are able to deploy ODF 4.9. The issue is now resolved. This can be closed.
@branto Can you pls move this bug to the build component and move it to ONQA so that this can be verified?
This was fixed by properly overriding the rbac proxy image in the DS builds: https://gitlab.cee.redhat.com/ceph/rhcs-jenkins-jobs/-/merge_requests/748 Moving directly to verified as per comment #5.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: Red Hat OpenShift Data Foundation 4.9.0 enhancement, security, and bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:5086