Bug 2298152 - Subsequent upgrade to ODF 4.16 will end up with noobaa-db pod in CLBO in case the cluster got upgraded from ODF 4.14 to ODF 4.15 and PGSQL version failed to get upgraded to v15
Summary: Subsequent upgrade to ODF 4.16 will end up with noobaa-db pod in CLBO in case...
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: Multi-Cloud Object Gateway
Version: 4.16
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Nimrod Becker
QA Contact: krishnaram Karthick
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-07-16 12:44 UTC by Prasad Desala
Modified: 2024-08-07 04:58 UTC (History)
4 users (show)

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


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OCSBZM-8706 0 None None None 2024-07-16 12:45:18 UTC

Description Prasad Desala 2024-07-16 12:44:55 UTC
Description of problem (please be detailed as possible and provide log
snippests):
==================================================================================
In ODF 4.15.5 we included the fix for BZ 2280834 (noobaa-db-pg-0 in CLBO post ODF upgrade from ODF 4.14 to 4.15).

The problem is that even if the cluster is running ODF 4.15.5 but was previously upgraded from ODF 4.14 to ODF 4.15, and the cluster hit the issue reported in BZ 2280834, upgrading the cluster to ODF 4.16 will result in the noobaa-db in CLBO state, ODF upgrade failure and the need to recover NooBaa.


Version of all relevant components (if applicable):
In case the cluster was upgraded from ODF 4.14 to ODF 4.15.{0..4}


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
MCG operations may impact as noobaa-db pod will stay at CLBO 

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


Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?


Can this issue reproducible?
Yes

Can this issue reproduce from the UI?
N/A

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


Steps to Reproduce:
===================
1. Upgrade cluster from ODF 4.14 to ODF4.15.{0..4}
2. Hit BZ 2280834
3. With cluster in the same state, either upgrade the cluster to ODF 4.16.0 or to ODF 4.15.5 and then to ODF 4.16

Actual results:
===============
Post cluster upgrade to ODF 4.16.0, noobaa-db-pg-0 will stay at CLBO state

Expected results:
=================
Noobaa db pod should be healthy and running without any issues post cluster upgrade to ODF 4.16.0.


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