Description of problem (please be detailed as possible and provide log snippests): Currently when OCS is getting deployed in IBM Cloud (ROKS), rook-ceph is getting configured as backing store $ kubectl get BackingStore -n openshift-storage NAME TYPE PHASE AGE noobaa-default-backing-store s3-compatible Ready 23h $ kubectl describe BackingStore -n openshift-storage s3Compatible: Endpoint: http://rook-ceph-rgw-ocs-storagecluster-cephobjectstore.openshift-storage.svc.cluster.local:80 Secret: Name: rook-ceph-object-user-ocs-storagecluster-cephobjectstore-noobaa-ceph-objectstore-user Namespace: openshift-storage Signature Version: v4 Target Bucket: nb.1598351939348.us-south.containers.appdomain.cloud Type: s3-compatible Instead we want option to auto configure IBM COS as default backing store. Version of all relevant components (if applicable): Openshift OCP 4.3 (ROKS) OCS 4.5.0 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? Manual configure "S3 default placement" from the NooBaa console. 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? Yes Can this issue reproduce from the UI? If this is a regression, please provide more details to justify this: It is not a regression, this is more like a new feature request. Steps to Reproduce: 1. Deploy OCS 4.5 in IBM Cloud (ROKS) https://cloud.ibm.com 2. 3. Actual results: $ kubectl get BackingStore -n openshift-storage NAME TYPE PHASE AGE noobaa-default-backing-store s3-compatible Ready 24h $ noobaa backingstore list -n openshift-storage NAME TYPE TARGET-BUCKET PHASE AGE noobaa-default-backing-store s3-compatible nb.1598351939348.us-south.containers.appdomain.cloud Ready 24h18m22s Expected results: $ noobaa backingstore list -n openshift-storage NAME TYPE TARGET-BUCKET PHASE AGE noobaa-default-backing-store ibm-cos bucket-name Ready ---- Additional info:
Update, Working on code change, will raise PR in couple of days https://github.com/nkkashyap/noobaa-operator/commit/02bac5546e1621f99df133aef6b05cb25fc23998
Raised PR: https://github.com/noobaa/noobaa-operator/pull/446
Moving to VERIFIED based on OCS 4.6 RC7 regression cycle automation runs
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 Container Storage 4.6.0 security, bug fix, 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/RHSA-2020:5605