Unable to import cluster to ACM due to klusterlet-work-agent pod failure

Solution Verified - Updated -

Issue

When trying to import a cluster into ACM the request gets stuck in the Pending Import state and the klusterlet-work-agent pods are continuously restarting.

In the klusterlet-work-agent pod logs we see the error:

controllers failed with error: stat /spoke/hub-kubeconfig/kubeconfig: no such file or directory

Additionally, in the logs for the klusterlet-registration pod we see the following error where the kube-apiserver of the Hub Cluster cannot be reached:

 reflector.go:178] k8s.io/client-go@v0.18.3/tools/cache/reflector.go:125: Failed to list *v1beta1.CertificateSigningRequest: Get https://api.ocp.example.com:6443/apis/certificates.k8s.io/v1beta1/certificatesigningrequests?limit=500&resourceVersion=0: dial tcp: lookup api.ocp.example.com on 10.0.0.1: no such host

Environment

  • Red Hat Advanced Cluster Management for Kubernetes 2.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content