Bug 2032690 - [GSS] Noobaa components are not created properly on upgrading from OCS 4.6 to 4.8 [NEEDINFO]
Summary: [GSS] Noobaa components are not created properly on upgrading from OCS 4.6 to...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: Multi-Cloud Object Gateway
Version: 4.8
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: Romy Ayalon
QA Contact: Raz Tamir
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-15 02:31 UTC by Sonal
Modified: 2023-08-09 16:49 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-01-06 09:03:47 UTC
Embargoed:
sarora: needinfo? (mhackett)

Attachments (Terms of Use)

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:
Note You need to log in before you can comment on or make changes to this bug.