Bug 2184160

Summary: [RDR] odr-cluster-operator status becomes Unknown when Hub and Managed clusters have different sub-versions of MCO/ODF
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: Aman Agrawal <amagrawa>
Component: documentationAssignee: Olive Lakra <olakra>
Status: CLOSED NOTABUG QA Contact: Neha Berry <nberry>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.13CC: muagarwa, ocs-bugs, odf-bz-bot, skatiyar, srangana
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-04-05 17:05:57 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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.