Bug 2211392
| Summary: | [MDR] Internal Upgrade of Openshift DR Cluster Operator failed within 4.13 builds | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat OpenShift Data Foundation | Reporter: | avdhoot <asagare> |
| Component: | odf-dr | Assignee: | Karolin Seeger <kseeger> |
| odf-dr sub component: | ramen | QA Contact: | krishnaram Karthick <kramdoss> |
| Status: | CLOSED NOTABUG | Docs Contact: | |
| Severity: | high | ||
| Priority: | unspecified | CC: | muagarwa, ocs-bugs, odf-bz-bot, srangana |
| Version: | 4.13 | ||
| 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-05-31 12:40:14 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: | |||
Since multicluster-orchestrator was upgraded but dr-cluster-operator wasn't, changing the component to ramen. Seems to be a breaking change in API. |
Created attachment 1968067 [details] screenshot_1 Description of problem (please be detailed as possible and provide log snippests): Trying to do internal upgrade of Openshift DR Cluster Operator by editing catalog source(ocs-catalogsource) from 4.13.0-170 to 4.13.0-207, but it stuck in pending state. while upgrade of ODF from 4.13.0-170 to 4.13.0-207 is successful. Please find attached screenshot of Openshift DR Cluster Operator with error.- screenshot_1 Version of all relevant components (if applicable): OCP- 4.13.0-0.nightly-2023-04-18-005127 ODF- 4.13.207 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)? 3 Can this issue reproducible? yes Can this issue reproduce from the UI? If this is a regression, please provide more details to justify this: Steps to Reproduce: 1. configured MDR cluster with build 4.13.0-170. 2. Edit image build in ocs-catalogsource to 4.13.0-207 on managed cluster c1 and c2. 3. Changed subscription of DR operator to ocs-catalogsource oc edit subscriptions.operators.coreos.com/ramen-dr-cluster-subscription -n openshift-dr-system 4.check Openshift DR cluster operator status Actual results: Openshift DR Cluster Operator is in pending state Expected results: Openshift DR Cluster Operator status should be successful after upgrade. Additional info: On hub cluster MCO got upgraded to 4.13.0-207 by changing catalogsource.