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.