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

Restart the agent pod to pick hub the new hub kubeconfig after restore

XMLWordPrintable

    • No

       When the hub is restored on a different cluster and the managed clusters are restored and join the new hub cluster, the hypershift addon agent on the managed clusters are still running with the old hub kubeconfig causing hub connection failures.

       

      2023-03-28T18:14:45.379Z	ERROR	agent.agent-reconciler	agent/agent.go:626	failed to create or update the addOnPlacementScore resource in hosting-cluster	{"error": "Get \"https://api.app-aws-412ga-hub-dqh8q.dev06.red-chesterfield.com:6443/apis/cluster.open-cluster-management.io/v1alpha1/namespaces/hosting-cluster/addonplacementscores/hosted-clusters-score\": dial tcp 3.212.150.25:6443: i/o timeout"} 

       

      The agent needs to be restarted after the hub restore.

       

              rokejungrh Roke Jung
              rokejungrh Roke Jung
              David Huynh David Huynh
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: