Bug 2276550 - [IBM Support] After upgrade to 4.14 noobaa-default-backing-store shows "Object Storage" having a status of "Phase: Rejected"
Summary: [IBM Support] After upgrade to 4.14 noobaa-default-backing-store shows "Objec...
Keywords:
Status: CLOSED DUPLICATE of bug 2278389
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: Multi-Cloud Object Gateway
Version: 4.14
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: Nimrod Becker
QA Contact: krishnaram Karthick
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-04-23 00:17 UTC by Steve Baldwin
Modified: 2024-05-06 20:06 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-05-06 20:06:07 UTC
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.