Bug 1927186

Summary:	Configure pv-pool as backing store if cos creds secret not found in IBM Cloud
Product:	[Red Hat Storage] Red Hat OpenShift Container Storage	Reporter:	Neeraj K Kashyap <nkashyap>
Component:	Multi-Cloud Object Gateway	Assignee:	Nimrod Becker <nbecker>
Status:	CLOSED ERRATA	QA Contact:	Petr Balogh <pbalogh>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.6	CC:	dwalveka, ebenahar, etamir, nbecker, ocs-bugs, pbalogh
Target Milestone:	---
Target Release:	OCS 4.7.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	v4.7.0-263.ci	Doc Type:	Enhancement
Doc Text:	.OpenShift Container Storage deployed on ROKS without credentials in the IBM cloud setup With this update, for the ease of installation in the IBM cloud setup when OpenShift Container Storage is deployed on ROKS and no credentials are provided for using ROKS as the default BackingStore, a PV pool default BackingStore is created.	Story Points:	---
Clone Of:
Clones:	1931451 (view as bug list)		Environment:
Last Closed:	2021-05-19 09:19:24 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1931451, 1938134

Description Neeraj K Kashyap 2021-02-10 10:14:59 UTC

Description of problem (please be detailed as possible and provide log
snippests):

Currently, in IBM Cloud NooBaa Operator is keep on waiting for ibm-cloud-cos-creds under target NS, to configure IBM COS as backing store. There are certain situation where customer in IBM Cloud cloud do not want to configure IBM COS as backing store and want to default back to pv-pool as backing store. In this situation ocs-storagecluster is not getting into ready state as noobaa operator keep waiting for secret. 

Version of all relevant components (if applicable):

OCS 4.6.2
ROKS 4.6.9

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)? None


Is there any workaround available to the best of your knowledge? None


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:


Steps to Reproduce:
1. Deploy OCS in ROKS 4.6 (without ibm-cloud-cos-creds )in IBM Cloud
2. Run oc describe noobaa -n openshift-storage
3. You will see "Cloud credentials secret "ibm-cloud-cos-creds" is not ready yet"


Actual results:


Expected results:


Additional info:

Comment 4 Petr Balogh 2021-03-08 09:07:07 UTC

I ran verification tier1 job here:
https://ocs4-jenkins-csb-ocsqe.apps.ocp4.prod.psi.redhat.com/job/qe-deploy-ocs-cluster-prod/92/

With build:
4.7.0-281.ci

Deployment passed

Logs: http://magna002.ceph.redhat.com/ocsci-jenkins/openshift-clusters/j010icm1r3-t1/j010icm1r3-t1_20210304T145650

This execution ran without COS secret defined, using this PR:
https://github.com/red-hat-storage/ocs-ci/pull/3940/files

So I think we can mark it as verified I think.

Comment 11 errata-xmlrpc 2021-05-19 09:19:24 UTC

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.7.0 security, 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/RHSA-2021:2041