Bug 2032690

Summary: [GSS] Noobaa components are not created properly on upgrading from OCS 4.6 to 4.8
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: Sonal <sarora>
Component: Multi-Cloud Object GatewayAssignee: Romy Ayalon <rayalon>
Status: CLOSED NOTABUG QA Contact: Raz Tamir <ratamir>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.8CC: etamir, hnallurv, mduasope, mhackett, nbecker, ocs-bugs, odf-bz-bot, prpandey, rayalon, smulay
Target Milestone: ---Flags: sarora: needinfo? (mhackett)
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-01-06 09:03:47 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 2021-12-15 02:31:09 UTC 
Description of problem (please be detailed as possible and provide log
snippests):
On upgrading from OCS 4.6 to 4.8, ocs-operator is in installing phase:

Noobaa components are not created properly. noobaa-endpoint and noobaa-core pods are missing.
Backingstore is in the Connecting state.

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

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

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

Can this issue reproduce from the UI?
Yes

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

Steps to Reproduce:
1. Upgrade from OCS 4.6 to 4.8


Actual results:
OCS operator is in installing phase.


Expected results:
OCS should upgrade successfully.

Additional info: