rancher: New Issues of Cattle-Cluster-Agent: (Could not resolve host: rancher..com)

@v15170r

Adding host alias to the cattle agent can be done in this way:

kubectl -n cattle-system patch  deployments cattle-cluster-agent --patch '{
    "spec": {
        "template": {
            "spec": {
                "hostAliases": [
                    {
                      "hostnames":
                      [
                        "{{ rancher_server_hostname }}"
                      ],
                      "ip": "{{ rancher_server_ip }}"
                    }
                ]
            }
        }
    }
}'

kubectl -n cattle-system patch  daemonsets cattle-node-agent --patch '{
 "spec": {
     "template": {
         "spec": {
             "hostAliases": [
                 {
                    "hostnames":
                      [
                        "{{ rancher_server_hostname }}"
                      ],
                    "ip": "{{ rancher_server_ip }}"
                 }
             ]
         }
     }
 }
}'

@armanriazi HI! I solved the problem. cattle-cluster-agent edit networking add Host Aliases (/etc/hosts entries)

@superseb I solved value of server-url/v3/settings/cacerts and intermediate CA but I still getting this error (I saw issues similar but there was’t full solver and I think it not granular nature system yet) Thanks friends. INFO: Environment: CATTLE_ADDRESS=10.42.0.14 CATTLE_CA_CHECKSUM=f4400caeebc0e481b1edfa15e5ba19b9756bc132d0a9448dc82479b718f8cdc9 CATTLE_CLUSTER=true CATTLE_INTERNAL_ADDRESS= CATTLE_K8S_MANAGED=true CATTLE_NODE_NAME=cattle-cluster-agent-88dbc897d-x9hp7 CATTLE_SERVER=https://rancher.nik.com CATTLE_SERVICE_PORT=tcp://10.43.131.37:80 CATTLE_SERVICE_PORT_443_TCP=tcp://10.43.131.37:443 CATTLE_SERVICE_PORT_443_TCP_ADDR=10.43.131.37 CATTLE_SERVICE_PORT_443_TCP_PORT=443 CATTLE_SERVICE_PORT_443_TCP_PROTO=tcp CATTLE_SERVICE_PORT_80_TCP=tcp://10.43.131.37:80 CATTLE_SERVICE_PORT_80_TCP_ADDR=10.43.131.37 CATTLE_SERVICE_PORT_80_TCP_PORT=80 CATTLE_SERVICE_PORT_80_TCP_PROTO=tcp CATTLE_SERVICE_SERVICE_HOST=10.43.131.37 CATTLE_SERVICE_SERVICE_PORT=80 CATTLE_SERVICE_SERVICE_PORT_HTTP=80 CATTLE_SERVICE_SERVICE_PORT_HTTPS=443

INFO: Using resolv.conf: nameserver 10.43.0.10 search cattle-system.svc.cluster.local svc.cluster.local cluster.local options ndots:5 error : ERROR: https://rancher.nik.com/ping is not accessible (Could not resolve host:)

The cluster-agent uses cluster DNS which uses DNS resolving, not a /etc/hosts workaround. Make sure it can properly resolve the configured server-url. Regarding the certificates, the configured CA cert is retrieved from server-url/v3/settings/cacerts and used to verify the certificate. Make sure it is configured correctly and uses the correct certificate. If this is correct, possibly it needs an intermediate certificate which needs to be added to the server certificate configured to provide the complete chain to the client (agent).

@v15170r 我的英文不好，我是在无法启动的cattle-cluster-agent 容器的网络设置的host Aliases中加入不能访问的域名，这样容器就能启动了

@armanriazi
HI！ I have the same problem as you. Have you solved it?

INFO: Environment: CATTLE_ADDRESS=10.42.2.12 CATTLE_CA_CHECKSUM=4721728379bf3c59b576e7392e743c220136aa73d0297b5a0e46487cdec7f01d CATTLE_CLUSTER=true CATTLE_INTERNAL_ADDRESS= CATTLE_K8S_MANAGED=true CATTLE_NODE_NAME=cattle-cluster-agent-5fcf59f8b7-4pbhx CATTLE_SERVER=https://rancher.xxx.com 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://rancher.xxx.com/ping is not accessible (Could not resolve host: rancher.xxx.com)

I get the same problem. Looks like this:

kubectl get deployments -n cattle-system
NAME                   READY   UP-TO-DATE   AVAILABLE   AGE
cattle-cluster-agent   0/1     1            0           23h
rancher                3/3     3            3           23h

kubectl -n cattle-system logs -f cattle-cluster-agent-9c64ff5d6-7q5fw
INFO: Environment: CATTLE_ADDRESS=10.42.1.9 
                                  CATTLE_CA_CHECKSUM=baa47<xxx>bd47459f92 
                                  CATTLE_CLUSTER=true 
                                  CATTLE_FEATURES=dashboard=true 
                                  CATTLE_INTERNAL_ADDRESS= 
                                  CATTLE_K8S_MANAGED=true 
                                  CATTLE_NODE_NAME=cattle-cluster-agent-9c64ff5d6-7q5fw 
                                  CATTLE_SERVER=https://stage-k8senv1.xxx.se

INFO: Using resolv.conf: nameserver 10.43.0.10 search cattle-system.svc.stage-k8senv1.xxx.se 
                                  svc.stage-k8senv1.xxx.se 
                                  stage-k8senv1.xxx.se options ndots:5

ERROR: https://stage-k8senv1.xxx.se/ping is not accessible (Could not resolve host: stage-k8senv1.xxx.se)

I’ve applied the patch against deployment rancher

This fully solved the problem.

kubectl -n cattle-system patch  deployments cattle-cluster-agent --patch '{
    "spec": {
        "template": {
            "spec": {
                "hostAliases": [
                    {
                      "hostnames":
                      [
                        "stage-k8senv1.xxx.se"
                      ],
                      "ip": "172.20.10.100"
                    },
                    {
                      "hostnames":
                      [
                        "stage-k8senv1.xxx.se"
                      ],
                      "ip": "172.20.10.101"
                    }

                ]
            }
        }
    }
}'

kubectl -n cattle-system patch  daemonsets cattle-node-agent --patch '{
    "spec": {
        "template": {
            "spec": {
                "hostAliases": [
                    {
                      "hostnames":
                      [
                        "stage-k8senv1.xxx.se"
                      ],
                      "ip": "172.20.10.100"
                    },
                    {
                      "hostnames":
                      [
                        "stage-k8senv1.xxx.se"
                      ],
                      "ip": "172.20.10.101"
                    }

                ]
            }
        }
    }
}'

@superseb Would you be so kind as to explain how to Make sure it can properly resolve the configured server-url, please? I’ve run into the same issue on Minikube over and over again. Adding an entry to /etc/hosts inside Minikube pointing to minikube ip will get the cattle-node-agent pod up and running, but the cattle-cluster-agent keeps failing. FYI Rancher seems to work though, even without that cattle-cluster-agent running.