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

[RDR] [Hub recovery] Auto import of managed clusters remains stuck on switching hubs

XMLWordPrintable

    • Important
    • No

      Description of problem:

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

      OCP 4.16.0-0.nightly-2024-05-23-173505

      ACM 2.11.0-DOWNSTREAM-2024-05-23-15-16-26

      MCE 2.6.0-104 

      ODF 4.16.0-108.stable

      Gitops v1.12.3 

      Platform- VMware

      How reproducible: Almost always

      Steps to Reproduce:

      1. Configure a ODF Regional DR setup and switch to passive hub by performing hub recovery using backup and restore.
      2. Make sure the setup is done to allow automatic import of the managed clusters on the new hub after switching to it.
        Follow- https://www.redhat.com/en/blog/a-guide-to-automatically-reconnecting-managed-clusters-when-restoring-a-red-hat-advanced-cluster-management-for-kubernetes-2.7-hub-cluster
      3.  Check the status of managed clusters on the new hub. For me, they remain stuck in Pending import state.
      4.  
      5.  
      6. ...

      Actual results: Auto import of managed clusters remains stuck on switching hubs

      ACM Must-gather logs- http://rhsqe-repo.lab.eng.blr.redhat.com/OCS/ocs-qe-bugs/bz-aman/30may24/

       

      ```
      oc describe restore.cluster.open-cluster-management.io -n open-cluster-management-backup Name: restore-acm Namespace: open-cluster-management-backup Labels: <none> Annotations: <none> API Version: cluster.open-cluster-management.io/v1beta1 Kind: Restore Metadata: Creation Timestamp: 2024-05-30T12:13:04Z Generation: 1 Resource Version: 2704848 UID: 1842341f-0417-411f-a820-3f343b409cb3 Spec: Cleanup Before Restore: None Velero Credentials Backup Name: latest Velero Managed Clusters Backup Name: latest Velero Resources Backup Name: latest Status: Last Message: All Velero restores have run successfully Phase: Finished Velero Credentials Restore Name: restore-acm-acm-credentials-schedule-20240530120055-active Velero Generic Resources Restore Name: restore-acm-acm-resources-generic-schedule-20240530120055 Velero Managed Clusters Restore Name: restore-acm-acm-managed-clusters-schedule-20240530120055 Velero Resources Restore Name: restore-acm-acm-resources-schedule-20240530120055 Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Velero restore created: 75m Restore controller restore-acm-acm-credentials-schedule-20240530120055-active Normal Velero restore created: 75m Restore controller restore-acm-acm-credentials-schedule-20240530120055 Normal Velero restore created: 75m Restore controller restore-acm-acm-resources-schedule-20240530120055 Normal Velero restore created: 75m Restore controller restore-acm-acm-resources-generic-schedule-20240530120055 Normal Velero restore created: 75m Restore controller restore-acm-acm-managed-clusters-schedule-20240530120055
      ```

       

      Expected results: The auto import of managed clusters post switching hubs should work when the setup is done correctly using the documentation.

      Additional info:

              vbirsan@redhat.com Valentina Birsan
              amagrawa@redhat.com Aman Agrawal
              Thuy Nguyen Thuy Nguyen
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: