Description of problem: Creating a LocalVolume instance fails as the diskmaker-manager daemonset uses the "quay.io/openshift/origin-kube-rbac-proxy:latest" image which is x86 only and fails on ppc64le architecture. Version-Release number of selected component (if applicable): # oc get csv -A NAMESPACE NAME DISPLAY VERSION REPLACES PHASE openshift-local-storage local-storage-operator.4.10.0-202112110159 Local Storage 4.10.0-202112110159 Succeeded How reproducible: Always Steps to Reproduce: 1. Deploy Local storage operator 2. Create a Local Volume instance Actual results: The diskmaker-manager daemonset uses the "quay.io/openshift/origin-kube-rbac-proxy:latest" image which is x86 only. # oc get pods -A | grep local openshift-local-storage diskmaker-manager-ftf6c 1/2 CrashLoopBackOff 29 (2m18s ago) 126m openshift-local-storage diskmaker-manager-sxr5l 1/2 CrashLoopBackOff 29 (2m54s ago) 126m openshift-local-storage local-storage-operator-86b9cff8cd-fgqq7 1/1 Running 0 3h36m diskmaker-manager pod events: Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 126m default-scheduler Successfully assigned openshift-local-storage/diskmaker-manager-ftf6c to worker-0 Normal AddedInterface 126m multus Add eth0 [10.128.2.186/23] from ovn-kubernetes Normal Pulled 126m kubelet Container image "registry.redhat.io/openshift4/ose-local-storage-diskmaker@sha256:e5181166b2d5ca3ed9485b558ffaf328d24002b297f3cc0c1013e705d94c0b1e" already present on machine Normal Created 126m kubelet Created container diskmaker-manager Normal Started 126m kubelet Started container diskmaker-manager Normal Pulled 124m (x5 over 126m) kubelet Container image "quay.io/openshift/origin-kube-rbac-proxy:latest" already present on machine Normal Created 124m (x5 over 126m) kubelet Created container kube-rbac-proxy Normal Started 124m (x5 over 126m) kubelet Started container kube-rbac-proxy Warning BackOff 85s (x573 over 126m) kubelet Back-off restarting failed container # oc logs diskmaker-manager-ftf6c -n openshift-local-storage kube-rbac-proxy standard_init_linux.go:228: exec user process caused: exec format error Expected results: Require multi-arch image for kube-rbac-proxy. The csv for local storage operator shows the following image and expectation is that the multi-arch image is pulled - name: KUBE_RBAC_PROXY_IMAGE value: registry.redhat.io/openshift4/ose-kube-rbac-proxy@sha256:001e4df621f23b9a13b77f8f9d21a79c1272bd840b09934e04c4d7eb1bf4c6d9
I was going to post that this commit is the likely cause: https://github.com/openshift/local-storage-operator/commit/16ea6b42b44741d86bc3781236076333ade36e0c But then Yaakov already posted a patch. :) Thanks Yaakov!! :D
Verified with local-storage-operator.4.10.0-202112211727 # oc get csv -A | grep local openshift-local-storage local-storage-operator.4.10.0-202112211727 Local Storage 4.10.0-202112211727 Succeeded # oc get pods -n openshift-local-storage NAME READY STATUS RESTARTS AGE diskmaker-manager-b4bdq 2/2 Running 0 100s diskmaker-manager-dsgzs 2/2 Running 0 100s local-storage-operator-745c8df996-8767g 1/1 Running 0 5m29s Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 2m7s default-scheduler Successfully assigned openshift-local-storage/diskmaker-manager-b4bdq to worker-1 Normal AddedInterface 2m6s multus Add eth0 [10.128.3.34/23] from openshift-sdn Normal Pulling 2m5s kubelet Pulling image "registry.redhat.io/openshift4/ose-local-storage-diskmaker@sha256:b445d8e464237b99f4914f080dbdf4e9ed8d2504110262674b5ed5de31115b7a" Normal Pulled 119s kubelet Successfully pulled image "registry.redhat.io/openshift4/ose-local-storage-diskmaker@sha256:b445d8e464237b99f4914f080dbdf4e9ed8d2504110262674b5ed5de31115b7a" in 6.808480268s Normal Created 118s kubelet Created container diskmaker-manager Normal Started 118s kubelet Started container diskmaker-manager Normal Pulling 118s kubelet Pulling image "registry.redhat.io/openshift4/ose-kube-rbac-proxy@sha256:7367f418a530a7ba41cff6a6a1b8d25c3ea4e8ec16e56d037795e7b260169a29" Normal Pulled 112s kubelet Successfully pulled image "registry.redhat.io/openshift4/ose-kube-rbac-proxy@sha256:7367f418a530a7ba41cff6a6a1b8d25c3ea4e8ec16e56d037795e7b260169a29" in 6.350894722s Normal Created 112s kubelet Created container kube-rbac-proxy Normal Started 112s kubelet Started container kube-rbac-proxy
@danili As verification is complete in Comment 3, could you please update this issue to Verified state. Thanks :)
Marking Verified per Comment 4 from Pravin.
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: OpenShift Container Platform 4.10.3 security 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-2022:0056