Bug 2184160 - [RDR] odr-cluster-operator status becomes Unknown when Hub and Managed clusters have different sub-versions of MCO/ODF
Summary: [RDR] odr-cluster-operator status becomes Unknown when Hub and Managed cluste...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: documentation
Version: 4.13
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Olive Lakra
QA Contact: Neha Berry
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-03 19:05 UTC by Aman Agrawal
Modified: 2023-08-09 16:43 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-04-05 17:05:57 UTC
Embargoed:


Attachments (Terms of Use)

Comment 5 Shyamsundar 2023-04-04 13:10:06 UTC
If you note the odr-cluster subscription its is attempting to use a starting version 4.13.0-114, but the catsrc on the managed clusters (potentially) are at 4.13.0-121, so this base version would never be found, hence the failure.

This happens, as the hub attempts to install the same version on the managed clusters, which results in the dr-cluster requiring the 114 version of the subscription. This would happen on an initial install, further upgrades (say ODF on the managed clusters from 114 -> 121) would update the dr operator bundles appropriately.

This is not a bug per-se, and if a user requires that the hub be older than the managed cluster, then the ramen hub configmap needs to be edited to provide appropriate starting CSV versions for the installs on the managed cluster.

This potentially needs some documentation, if at all any, to handle such install situations. Moving this to the doc component at present for a decision regarding the same.


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