Bug 2181982

Summary:	[GSS] [ODF 4.10] Problems with SCC installing ODF in a production OCP
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	amansan <amanzane>
Component:	ocs-operator	Assignee:	Madhu Rajanna <mrajanna>
Status:	CLOSED NOTABUG	QA Contact:	Elad <ebenahar>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.10	CC:	hnallurv, kjosy, mrajanna, muagarwa, ocs-bugs, odf-bz-bot, paarora
Target Milestone:	---	Flags:	mrajanna: needinfo? (amanzane)
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-04-05 06:20:00 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:

Description amansan 2023-03-27 07:07:47 UTC

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

The customer has OCP 4.10 installed and now is installing ODF 4.10, once the installation is done the provisioner pods for rbd and cephfs go into CLBO

Version of all relevant components (if applicable):

OCP 4.10 and ODF 4.10

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

Yes, as the provisioners are in CLBO the customer can’t use ODF

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

No

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?

3

Can this issue reproducible?

Not sure, but I think could be done

1. Installing OCP and configuring it
2. Installing ODF after that


Actual results:

Provisioner pods in CLBO

Expected results:

Provisioner pods Running