Bug 2238720
Summary: | [ACM Tracker] [IBMZ / MDR]: Ramen-dr-cluster-operator is not deployed on managed clusters after applying drpolicy | ||||||
---|---|---|---|---|---|---|---|
Product: | [Red Hat Storage] Red Hat OpenShift Data Foundation | Reporter: | Sravika <sbalusu> | ||||
Component: | odf-dr | Assignee: | Shyamsundar <srangana> | ||||
odf-dr sub component: | ramen | QA Contact: | avdhoot <asagare> | ||||
Status: | CLOSED ERRATA | Docs Contact: | |||||
Severity: | urgent | ||||||
Priority: | unspecified | CC: | aclewett, amagrawa, asagare, hnallurv, kseeger, ming, muagarwa, rtalur, srangana, tflower, zxue | ||||
Version: | 4.14 | ||||||
Target Milestone: | --- | ||||||
Target Release: | ODF 4.14.0 | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | acm-operator-bundle-container-v2.9.0-150 | Doc Type: | No Doc Update | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2023-11-08 18:54:31 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: | |||||||
Attachments: |
|
Description
Sravika
2023-09-13 10:36:07 UTC
Created attachment 1988631 [details]
ramen-hub-operator.log
Fixed in later than acm-operator-bundle-container-v2.9.0-150 ACM 2.9 internal releases. With the latest acm-operator-bundle-container-v2.9.0-150 I do not see this anymore and the ramen-dr-cluster-operator is deployed on managed clusters after applying drpolicy. # oc get sa -n open-cluster-management-agent NAME SECRETS AGE builder 1 16h default 1 16h deployer 1 16h klusterlet 1 16h klusterlet-work-sa 1 16h Observation- --------------- With the latest acm-operator-bundle-container-v2.9.0-165 . ramen-dr-cluster-operator is deployed on managed clusters after deleting and again applying drpolicy. Also ramen-hub-operator restarted on hub and ramen-dr-cluster-operator restarted on primary managed cluster. No ramen-dr-cluster-operator restarts seen on secondary cluster. Steps Performed: --------------------- 1. With existing Metro DR environment deleted all apps(subscription + Appset) and drpolicy. 2. Created new drpolicy with same name. 3. Created subscription set app. 4. Applied drpolicy tp app. hub% oc get pods -n openshift-operators NAME READY STATUS RESTARTS AGE odf-multicluster-console-854b88488b-q6tpn 1/1 Running 0 4d21h odfmo-controller-manager-8585fbddb8-jctpj 1/1 Running 2 (45h ago) 4d21h ramen-hub-operator-7dc77db778-szcw4 2/2 Running 1 (45h ago) 4d21h clust1% oc get csv,pod -n openshift-dr-system NAME DISPLAY VERSION REPLACES PHASE clusterserviceversion.operators.coreos.com/odr-cluster-operator.v4.14.0-146.stable Openshift DR Cluster Operator 4.14.0-146.stable odr-cluster-operator.v4.14.0-139.stable Succeeded clusterserviceversion.operators.coreos.com/volsync-product.v0.7.4 VolSync 0.7.4 volsync-product.v0.7.3 Succeeded NAME READY STATUS RESTARTS AGE pod/ramen-dr-cluster-operator-9c78ffc78-xqz9m 2/2 Running 1 (2d20h ago) 2d20h Raised new Bugzilla for issue mentioned in comment 12. https://bugzilla.redhat.com/show_bug.cgi?id=2245230 Hence marking this BZ as verified. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: Red Hat OpenShift Data Foundation 4.14.0 security, enhancement & bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2023:6832 |