Description of the problem:
A new hub cluster has been created and the ACM hub backup/restore operation has been carried out as described in the docs:
After the restore operation is completed some of the managed clusters have been imported successfully to the ACM hub. Several others (~half) are stuck in the 'Pending import/Unknown' state.
OCP version: 4.9.37
Steps to reproduce:
1. Deploy 15+ clusters through the ACM hub (Created via Hive)
2. Perform the Backup procedure on the old ACM hub
3. Create a new ACM hub
4. Shutdown the old ACM Hub
5. Perform Restore operation on the new ACM hub
Some of the managed clusters have been imported successfully to the ACM hub. However, Several others (~half) are stuck in the 'Pending import/Unknown' state.
All managed clusters should be restored successfully as they all were created using ACM(Hive).
The failing clusters indicate it is still attempting to communicate with the Old ACM hub, not the new one.
G2Bsync 1171868820 comment
zhiweiyin318 Fri, 01 Jul 2022 02:47:39 UTC
discuss slack thread https://coreos.slack.com/archives/C0282HW2YHZ/p1656402856382809
the kubeconfig of `qasp-uat-cct-01` hive cluster in `qasp-uat-cct-01-0-xnxvg-admin-kubeconfig `secret is incorrect.
we cannot access the cluster by this kubeconfig with error from hub cluster.
Unable to connect to the server: x509: certificate signed by unknown authority
need DR squad and hive team take a look to figure out why this kubeconfig is incorrect.
added a known issue for this.
22.214.171.124. Restored Hive managed clusters might be able to connect with the new hub cluster in https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.6/html/release_notes/red-hat-advanced-cluster-management-for-kubernetes-release-notes#backup-known-issues
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 (Critical: Red Hat Advanced Cluster Management 2.4.6 security update and bug fixes), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.