Bug 2276550

Summary:	[IBM Support] After upgrade to 4.14 noobaa-default-backing-store shows "Object Storage" having a status of "Phase: Rejected"
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Steve Baldwin <sbaldwin>
Component:	Multi-Cloud Object Gateway	Assignee:	Nimrod Becker <nbecker>
Status:	CLOSED DUPLICATE	QA Contact:	krishnaram Karthick <kramdoss>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.14	CC:	belimele, bkunal, mhackett, nbecker, odf-bz-bot, usrivast
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:	2024-05-06 20:06:07 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 Steve Baldwin 2024-04-23 00:17:57 UTC

Description of problem (please be detailed as possible and provide log
snippests):
User upgraded OCP/ODF from 4.12 to 4.14 and post upgrade they started receiving errors on the noobaa-default-backing-store showing a status of "Phase: Rejected"
The mcodes reported in events for "Backing store mode":
NO_CAPACITY
ALL_NODES_OFFLINE

The backing pv has adequate space (50gb) and only consuming 10gb.

Version of all relevant components (if applicable):
ODF 4.14.6

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
Yes, the user is unable to use Multi Cloud Gateway

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

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?
Only at customer site

Can this issue reproduce from the UI?
Yes

If this is a regression, please provide more details to justify this:
N/A

Actual results:


Expected results:


Additional info:
++ This is a stand-alone MCG cluster
++ User indicates during upgrade they were unable to select 4.13 so they upgraded OCP/ODF directly from 4.12 to 4.14.