Description of problem (please be detailed as possible and provide log snippests): While deploying OCS cluster on Azure and GCP deployments, RGW pods should not be deployed. Version of all relevant components (if applicable): 4.3 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? No Is there any workaround available to the best of your knowledge? None that I'm aware of 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? Yes If this is a regression, please provide more details to justify this: No Steps to Reproduce: 1. On an OCP installation on Azure, install OCS via UI. 2. Check the pods/services that are displayed Actual results: pod/rook-ceph-rgw-ocs-storagecluster-cephobjectstore , service/rook-ceph-rgw-ocs-storagecluster-cephobjectstore etc are deployed Expected results: RGW is not deployed by default Additional info:
Pulkit, can you look into this?
https://github.com/openshift/ocs-operator/pull/492
Raz, can you ack this?
acked, removing needinfo
Same for COS
For gcp this is the bug https://bugzilla.redhat.com/show_bug.cgi?id=1848867.
I checked that with OCS 4.4.1 on Azure, the RGW pod is there. Then with OCS 4.5.0-515.ci (full version report bellow) on Azure, I see that RGW pod is no longer deployed: ``` $ oc get pods -n openshift-storage | grep -i rgw $ oc describe backingstore noobaa-default-backing-store | grep -i rgw $ ``` Full version report: ``` cluster channel: stable-4.5 cluster version: 4.5.4 cluster image: quay.io/openshift-release-dev/ocp-release@sha256:02dfcae8f6a67e715380542654c952c981c59604b1ba7f569b13b9e5d0fbbed3 storage namespace openshift-cluster-storage-operator image quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:063d93072a78b6ee6a1312861cc230180960eaf41c2562d4b7e53960e4f02f93 * quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:063d93072a78b6ee6a1312861cc230180960eaf41c2562d4b7e53960e4f02f93 image quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:331121562e985265d9ce51807d58b6806087528242d0aa10b980a287bea89314 * quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:331121562e985265d9ce51807d58b6806087528242d0aa10b980a287bea89314 image quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:08098ccf17bb74420d2ef3faf2638717b24324a5ba50183b06278e32eacea23f * quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:08098ccf17bb74420d2ef3faf2638717b24324a5ba50183b06278e32eacea23f storage namespace openshift-kube-storage-version-migrator image quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:763d2be9190b0668d94ea715e12f2adc463aa633e1cc3b343b7132cb6b6d7d24 * quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:763d2be9190b0668d94ea715e12f2adc463aa633e1cc3b343b7132cb6b6d7d24 storage namespace openshift-kube-storage-version-migrator-operator image quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:5c513d16bbccf8361c6f3ad5af54831bd24a897fb374a3e640688687248c6333 * quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:5c513d16bbccf8361c6f3ad5af54831bd24a897fb374a3e640688687248c6333 storage namespace openshift-storage image quay.io/rhceph-dev/cephcsi@sha256:244099ffc77fe965cd258e105aeff127de08673830a679ecb2525d9220e161fb * quay.io/rhceph-dev/cephcsi@sha256:244099ffc77fe965cd258e105aeff127de08673830a679ecb2525d9220e161fb image registry.redhat.io/openshift4/ose-csi-driver-registrar@sha256:5ed44407414538adcba19f3780be37193f1b5a8789fbf3a4e7ed65c7693f1b66 * registry.redhat.io/openshift4/ose-csi-driver-registrar@sha256:3be38cacdce4218756d927fff577b32fb2cf0e168a26a3713d92208d6df98bc0 image registry.redhat.io/openshift4/ose-csi-external-attacher@sha256:fc97bc7790703299ee19d9c4353699e049773babbfe74d0b7691ad8536cf250a * registry.redhat.io/openshift4/ose-csi-external-attacher@sha256:86a4e81a39f5e9682ecfcb02c2af236fd4a05679f82d6e538dc5209fc6b18093 image registry.redhat.io/openshift4/ose-csi-external-provisioner-rhel7@sha256:f04a827f92c355f3f486957518bcf282fd7b9546ecdc275d04e8389f6290e712 * registry.redhat.io/openshift4/ose-csi-external-provisioner-rhel7@sha256:0fd907aec05ffa8d46af15fdd1d23aa7fb0cc1283dfad31b086e34551e10295e image registry.redhat.io/openshift4/ose-csi-external-resizer-rhel7@sha256:bc1b07743216f68f0d292e7ed7607b2ce04c7f81d453a09cecc4cc3571eb19e5 * registry.redhat.io/openshift4/ose-csi-external-resizer-rhel7@sha256:bc1b07743216f68f0d292e7ed7607b2ce04c7f81d453a09cecc4cc3571eb19e5 image quay.io/rhceph-dev/mcg-core@sha256:241d9693c1166273ae386e51c317035785eaa24c31d0341e2a72a55d089d2558 * quay.io/rhceph-dev/mcg-core@sha256:241d9693c1166273ae386e51c317035785eaa24c31d0341e2a72a55d089d2558 image registry.redhat.io/rhscl/mongodb-36-rhel7@sha256:ba74027bb4b244df0b0823ee29aa927d729da33edaa20ebdf51a2430cc6b4e95 * registry.redhat.io/rhscl/mongodb-36-rhel7@sha256:ba74027bb4b244df0b0823ee29aa927d729da33edaa20ebdf51a2430cc6b4e95 image quay.io/rhceph-dev/mcg-operator@sha256:c0f05d916cd630c318a47958d11aa4249e849192fe5c905fdbba077486e06548 * quay.io/rhceph-dev/mcg-operator@sha256:c0f05d916cd630c318a47958d11aa4249e849192fe5c905fdbba077486e06548 image quay.io/rhceph-dev/ocs-operator@sha256:aafb92673728056210641e0ffb54a551d471247a79caed02c76dc992babe04e8 * quay.io/rhceph-dev/ocs-operator@sha256:aafb92673728056210641e0ffb54a551d471247a79caed02c76dc992babe04e8 image quay.io/rhceph-dev/rhceph@sha256:df67e134c9037707118a8533670b2f77647355a4af2fdc1247d79679cb6bb676 * quay.io/rhceph-dev/rhceph@sha256:df67e134c9037707118a8533670b2f77647355a4af2fdc1247d79679cb6bb676 image quay.io/rhceph-dev/rook-ceph@sha256:6aaf689232cb7fcb44e37dc1c34b17c7cc81d5fe244cfb4277fafdb5a3865ee4 * quay.io/rhceph-dev/rook-ceph@sha256:6aaf689232cb7fcb44e37dc1c34b17c7cc81d5fe244cfb4277fafdb5a3865ee4 ```
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.5.0 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-2020:3754