Cattle-cluster-agent in CrashLoopBackoff state

Hello Community members,

Below are the details

$ kubectl describe pod/cattle-cluster-agent-76866dbc87-s2kzb -n cattle-system
Name: cattle-cluster-agent-76866dbc87-s2kzb
Namespace: cattle-system
Priority: 0
Node: 192.168.62.111/192.168.62.111
Start Time: Fri, 12 Feb 2021 15:39:08 -0800
Labels: app=cattle-cluster-agent
pod-template-hash=76866dbc87
Annotations: cni.projectcalico.org/podIP: 10.42.0.5/32

Status: Running
IP: 10.42.0.5
IPs:
IP: 10.42.0.5
Controlled By: ReplicaSet/cattle-cluster-agent-76866dbc87
Containers:
cluster-register:
Container ID: docker://80970c3de72f274e9d0f2217e0bce1ee76ecd29a9cc489974f31bab36ecefe05
Image: rancher/rancher-agent:v2.5.5
Image ID: docker-pullable://rancher/rancher-agent@sha256:ddba352d8b1389741ed0b768b85c6fbc921889d350d7c54364c87b4d5849481b
Port:
Host Port:
State: Waiting
Reason: CrashLoopBackOff
Last State: Terminated
Reason: Error
Exit Code: 1
Started: Fri, 12 Feb 2021 15:42:05 -0800
Finished: Fri, 12 Feb 2021 15:42:05 -0800
Ready: False
Restart Count: 5
Readiness: http-get http://:8080/health delay=2s timeout=1s period=5s #success=1 #failure=3
Environment:
CATTLE_FEATURES:
CATTLE_IS_RKE: false
CATTLE_SERVER: https://local.system
CATTLE_CA_CHECKSUM: 19c892327bc278dcda327885e4df9b7499c9ad84dddca6e465abf9bf2ac506be
CATTLE_CLUSTER: true
CATTLE_K8S_MANAGED: true
Mounts:
/cattle-credentials from cattle-credentials (ro)
/var/run/secrets/kubernetes.io/serviceaccount from cattle-token-286mr (ro)
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
cattle-credentials:
Type: Secret (a volume populated by a Secret)
SecretName: cattle-credentials-8ea79b4
Optional: false
cattle-token-286mr:
Type: Secret (a volume populated by a Secret)
SecretName: cattle-token-286mr
Optional: false
QoS Class: BestEffort
Node-Selectors:

Events:
Type Reason Age From Message


Normal Scheduled 5m34s default-scheduler Successfully assigned cattle-system/cattle-cluster-agent-76866dbc87-s2kzb to 192.168.62.111
Normal Pulling 5m33s kubelet Pulling image “rancher/rancher-agent:v2.5.5”
Normal Pulled 5m24s kubelet Successfully pulled image “rancher/rancher-agent:v2.5.5”
Normal Created 3m58s (x5 over 5m23s) kubelet Created container cluster-register
Normal Started 3m58s (x5 over 5m23s) kubelet Started container cluster-register
Normal Pulled 3m58s (x4 over 5m23s) kubelet Container image “rancher/rancher-agent:v2.5.5” already present on machine
Warning BackOff 23s (x24 over 5m22s) kubelet Back-off restarting failed container

Tried restarting the cluster, but still seeing the CrashLoopBackOff.

$ kubectl logs --follow pod/cattle-cluster-agent-76866dbc87-s2kzb -n cattle-system
INFO: Environment: CATTLE_ADDRESS=10.42.0.5 CATTLE_CA_CHECKSUM=19c892327bc278dcda327885e4df9b7499c9ad84dddca6e465abf9bf2ac506be CATTLE_CLUSTER=true CATTLE_FEATURES= CATTLE_INTERNAL_ADDRESS= CATTLE_IS_RKE=false CATTLE_K8S_MANAGED=true CATTLE_NODE_NAME=cattle-cluster-agent-76866dbc87-s2kzb CATTLE_SERVER=https://local.system
INFO: Using resolv.conf: nameserver 10.43.0.10 search cattle-system.svc.cluster.local svc.cluster.local cluster.local options ndots:5
ERROR: https://local.system/ping is not accessible (Could not resolve host: local.system)