Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-20508

[HCI only] Applying the ManifestWork on a managed cluster takes over an hour

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • False
    • None

      Description of problem: drpolicy is stuck in Not validated state, the reason is the drclusters are not deployed. ManifestWork on the hub was created on April 28th around 12:45, it was only applied on the DRCluster on April 28th around 14:02

      Version-Release number of selected component (if applicable):

      OCP 4.18
      ODF 4.18.2
      ACM 2.13.2

      How reproducible:

      1. Setup RDR cluster
      2. Create drpolicy
      3. check drpolicy status - not validated

      oc get drcluster -o yaml
      apiVersion: v1
      items:
      - apiVersion: ramendr.openshift.io/v1alpha1
        kind: DRCluster
        metadata:
          creationTimestamp: "2025-04-28T12:45:07Z"
          finalizers:
          - drclusters.ramendr.openshift.io/ramen
          generation: 1
          labels:
            cluster.open-cluster-management.io/backup: ramen
          name: rackm03
          resourceVersion: "59867605"
          uid: 68cf1c2a-1f55-4240-b784-670d9abec9a8
        spec:
          region: 5e7feeab-0335-4d5f-8da4-87af9d39bbb0
          s3ProfileName: s3profile-rackm03-ocs-storagecluster
        status:
          conditions:
          - lastTransitionTime: "2025-04-28T12:45:09Z"
            message: Cluster Clean
            observedGeneration: 1
            reason: Clean
            status: "False"
            type: Fenced
          - lastTransitionTime: "2025-04-28T12:45:09Z"
            message: Cluster Clean
            observedGeneration: 1
            reason: Clean
            status: "True"
            type: Clean
          - lastTransitionTime: "2025-04-28T12:45:10Z"
            message: DRCluster ManifestWork is not in applied state
            observedGeneration: 1
            reason: DrClustersDeployStatusCheckFailed
            status: "False"
            type: Validated
          phase: Available
      - apiVersion: ramendr.openshift.io/v1alpha1
        kind: DRCluster
        metadata:
          creationTimestamp: "2025-04-28T12:45:07Z"
          finalizers:
          - drclusters.ramendr.openshift.io/ramen
          generation: 1
          labels:
            cluster.open-cluster-management.io/backup: ramen
          name: rackm14
          resourceVersion: "59867583"
          uid: 980e95c7-11b8-469a-899a-cae5f2819785
        spec:
          region: 2a8f90c8-4e04-4b4b-9e97-d718d11e4ae4
          s3ProfileName: s3profile-rackm14-ocs-storagecluster
        status:
          conditions:
          - lastTransitionTime: "2025-04-28T12:45:07Z"
            message: Cluster Clean
            observedGeneration: 1
            reason: Clean
            status: "False"
            type: Fenced
          - lastTransitionTime: "2025-04-28T12:45:07Z"
            message: Cluster Clean
            observedGeneration: 1
            reason: Clean
            status: "True"
            type: Clean
          - lastTransitionTime: "2025-04-28T12:45:09Z"
            message: DRCluster ManifestWork is not in applied state
            observedGeneration: 1
            reason: DrClustersDeployStatusCheckFailed
            status: "False"
            type: Validated
          phase: Available
      kind: List
      metadata:
        resourceVersion: "" 
      

      Must-gather logs :- http://rhsqe-repo.lab.eng.blr.redhat.com/ocs4qe/pratik/bz/olm/

              leyan@redhat.com Le Yang
              egershko Elena Gershkovich
              Hui Chen Hui Chen
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: