Bug 2100224

Summary:	[GSS] ocs-operator and mcg-operator csv is stuck in pending state on upgrading from ODF 4.9.8 to ODF 4.10.3
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Sonal <sarora>
Component:	odf-operator	Assignee:	Nitin Goyal <nigoyal>
Status:	CLOSED NOTABUG	QA Contact:	Martin Bukatovic <mbukatov>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.9	CC:	dzaken, hnallurv, jrivera, muagarwa, nbecker, nigoyal, ocs-bugs, odf-bz-bot
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-07-28 17:38:50 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 Sonal 2022-06-22 18:39:33 UTC

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

On upgrading from ODF 4.9.8 to 4.10.3, CSV of ocs-operator.v4.10.3 and mcg-operator.v4.10.3 is stuck in the Pending state:


Version of all relevant components (if applicable):
OCS 4.9.8


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)?
2

Can this issue reproducible?
Yes, in customer's environment

Can this issue reproduce from the UI?
Yes

If this is a regression, please provide more details to justify this:
-


Actual results:
ocs-operator.v.4.10.3 and mcg-operator.v.4.10.3 CSV is stuck in pending state.

Expected results:
ODF upgrade should succeed

Additional info:
In the next comment

Comment 7 Jose A. Rivera 2022-06-28 14:39:55 UTC

...I think something is missing from your chronology, some steps are missing important details that may or may not explain what's happening.

> 4. We followed https://bugzilla.redhat.com/show_bug.cgi?id=2023755#c18 and created catalogsource with image   image: registry.redhat.io/redhat/redhat-operator-index:v4.9. We observed csv got created for 4.8.12 and 4.9.8. ODF 4.9.8 was upgraded successfully.

I'd like to know the exact patch commands and YAML manifests you used during this step. Similarly:

> $ cat namespaces/openshift-storage/oc_output/subscription 
> NAME           PACKAGE        SOURCE             CHANNEL
> ocs-operator   ocs-operator   redhat-operators   eus-4.8
> odf-operator   odf-operator   redhat-operators   stable-4.9

Did you wait for `eus-4.8` to change to `stable-4.9` before continuing? The upgrade process involves allowing odf-operator to update the ocs-operator Subscription's channel to match the expected version (in this case, `stable-4.9`). Similarly you should've waited for the ocs-operator CSV to upgrade to it's v4.9 version.