Description of problem (please be detailed as possible and provide log snippests): If the ManifestWork on the ACM Hub cluster for ramen-dr-cluster is deleted it is not recreated by the operator. We found that we could "kickstart" a reconcile operation by the operator by editing the ConfigMap on the hub cluster ramen-hub-operator-config Version of all relevant components (if applicable): OpenShift DR Hub Operator: odr-hub-operator.v4.11.2 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? no Is there any workaround available to the best of your knowledge? touch a value on the configmap and the ManifestWork will be recreated Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? 1 Steps to Reproduce: 1. Delete ManifestWork ramen-hub-operator-config on hub cluster for a managed cluster 2. wait Actual results: No ManifestWork is recreated Expected results: ManifestWork is recreated Additional info:
Current Workaround: If the ManifestWork on the ACM Hub cluster for ramen-dr-cluster is deleted it is not recreated by the operator. You can "kickstart" a reconcile operation by the operator by editing the ConfigMap on the hub cluster ramen-hub-operator-config: $ oc edit configmap ramen-hub-operator-config -n openshift-operators [...] apiVersion: v1 data: ramen_manager_config.yaml: | apiVersion: ramendr.openshift.io/v1alpha1 drClusterOperator: catalogSourceName: redhat-operators catalogSourceNamespaceName: openshift-marketplace channelName: stable-4.11 clusterServiceVersionName: odr-cluster-operator.v4.11.3 deploymentAutomationEnabled: true namespaceName: openshift-dr-system [...] Change 'deploymentAutomationEnabled' to 'false' and save change. Edit configmap again and modify 'deploymentAutomationEnabled' back to true. Check that the 'ramen-dr-cluster' ManifestWork is created again in the correct managedcluster namespace (wherever it was deleted from): $ oc get manifestworks.work.open-cluster-management.io -A | grep ramen cluster1 ramen-dr-cluster 6d21h cluster2 ramen-dr-cluster 33s