Description of problem (please be detailed as possible and provide log snippests): Version of all relevant components (if applicable): Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? Is there any workaround available to the best of your knowledge? Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? Can this issue reproducible? Can this issue reproduce from the UI? If this is a regression, please provide more details to justify this: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Description of problem (please be detailed as possible and provide log snippests): Under StorageCluster.Status , desired image of noobaaCore is pointing rhceph image, desired image is not matching with the actual image output of : # oc get storagecluster -o yaml apiVersion: v1 items: - apiVersion: ocs.openshift.io/v1 kind: StorageCluster metadata: <...> name: ocs-storagecluster namespace: openshift-storage resourceVersion: "102319" selfLink: /apis/ocs.openshift.io/v1/namespaces/openshift-storage/storageclusters/ocs-storagecluster uid: 42dc57d7-cedf-4d1f-a524-62730ccc025b spec: <...> status: conditions: <...> images: ceph: actualImage: quay.io/rhceph-dev/rhceph@sha256:4bd7cc7ab108c7519be318ba7c892d7c262efcab36b15527dd2f2a6eb168fc77 desiredImage: quay.io/rhceph-dev/rhceph@sha256:4bd7cc7ab108c7519be318ba7c892d7c262efcab36b15527dd2f2a6eb168fc77 noobaaCore: actualImage: quay.io/rhceph-dev/mcg-core@sha256:54d2ea9d4e18f6c4bb1a11dfec741d1adb62c34d98ca4c488f9b06c070a794d3 desiredImage: quay.io/rhceph-dev/rhceph@sha256:4bd7cc7ab108c7519be318ba7c892d7c262efcab36b15527dd2f2a6eb168fc77 noobaaDB: actualImage: registry.redhat.io/rhel8/postgresql-12@sha256:ed859e2054840467e9a0ffc310ddf74ff64a8743c236598ca41c7557d8cdc767 desiredImage: registry.redhat.io/rhel8/postgresql-12@sha256:ed859e2054840467e9a0ffc310ddf74ff64a8743c236598ca41c7557d8cdc767 nodeTopologies: labels: failure-domain.beta.kubernetes.io/region: - us-east-2 failure-domain.beta.kubernetes.io/zone: - us-east-2a - us-east-2b - us-east-2c kubernetes.io/hostname: - ip-10-0-218-98 - ip-10-0-138-82 - ip-10-0-186-126 phase: Ready <...> Refer https://bugzilla.redhat.com/show_bug.cgi?id=1830215#c37 for info Version of all relevant components (if applicable): OCS 4.7.0-324.ci Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? Is there any workaround available to the best of your knowledge? Na Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? Can this issue reproducible? 1/1 Can this issue reproduce from the UI? If this is a regression, please provide more details to justify this: Steps to Reproduce: 1. Refer https://bugzilla.redhat.com/show_bug.cgi?id=1830215#c28 2. 3. Actual results: noobaaCore's actual and desired images are different Expected results: noobaaCore's actual and desired images should match Additional info:
Valid bug! Fix is upstream: https://github.com/openshift/ocs-operator/pull/1167
Not a blocker, if someone need to check this they can inspect the Pod spec directly. Already fixed in 4.8, if required can be taken in 4.7.z
Tested on ocs-operator.v4.8.0-402.ci $ oc describe storagecluster ocs-storagecluster Images: Ceph: Actual Image: quay.io/rhceph-dev/rhceph@sha256:d2e99edf733960244256ad82e761acffe9f09e76749bb769469b4b929b25c509 Desired Image: quay.io/rhceph-dev/rhceph@sha256:d2e99edf733960244256ad82e761acffe9f09e76749bb769469b4b929b25c509 Noobaa Core: Actual Image: quay.io/rhceph-dev/mcg-core@sha256:4a3795aa03eb8609fc5e1d3e2e75f841c665e53d9dd4e60b4279a7edd103fb46 Desired Image: quay.io/rhceph-dev/mcg-core@sha256:4a3795aa03eb8609fc5e1d3e2e75f841c665e53d9dd4e60b4279a7edd103fb46 Noobaa DB: Actual Image: registry.redhat.io/rhel8/postgresql-12@sha256:03a1e02a1b3245f9aa0ddd3f7507b915a8f7387a1674969f6ef039a5d7fd8bf0 Desired Image: registry.redhat.io/rhel8/postgresql-12@sha256:03a1e02a1b3245f9aa0ddd3f7507b915a8f7387a1674969f6ef039a5d7fd8bf0 Moving to Verified
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 (Red Hat OpenShift Container Storage 4.8.0 container images bug fix and enhancement 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/RHBA-2021:3003