Install failed at verify healthcheck [kubelet]

Rancher 2.x
1

i have three nodes for demo ,one for etcd and control ,two for worker 。
at etcd and control node startup cluster was failed:
[workerPlane] Failed to bring up Worker Plane: Failed to verify healthcheck: Failed to check https://localhost:10250/healthz for service [kubelet]
and docker ps :
351cc8392af9 rancher/hyperkube:v1.10.1-rancher2 “/opt/rke/entrypoi…” 9 minutes ago Restarting (255) 2 minutes ago kubelet

OS:ubuntu 16.04 docker 1.13.1

and docker logs :
W0514 08:20:05.887644 8373 cni.go:171] Unable to update cni config: No networks found in /etc/cni/net.d
E0514 08:20:05.887889 8373 kubelet.go:2125] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized
F0514 08:20:05.888668 8373 server.go:141] tls: failed to find any PEM data in certificate input

who can help me ,thank you

2

Had the same issue when selecting Amazon EC2 cluster + cluster options > cloud provider > Amazon.
If I set cloud provider “none”, then everything works.

3

Had the similar issue during create first demo cluster, kept on “Provisioning” state. any suggestions?

[controlPlane] Failed to bring up Control Plane: Failed to verify healthcheck: Failed to check https://localhost:6443/healthz for service [kube-apiserver] on host [192.168.7.211]: Get https://localhost:6443/healthz: dial tcp [::1]:6443: getsockopt: connection refused

logs related

I0521 14:58:30.408229 1 server.go:135] Version: v1.10.1
Unable to find suitable network address.error=‘No default routes.’. Try to set the AdvertiseAddress directly or provide a valid BindAddress to fix this.

  • echo kube-apiserver --tls-cert-file=/etc/kubernetes/ssl/kube-apiserver.pem --kubelet-client-key=/etc/kubernetes/ssl/kube-apiserver-key.pem --insecure-port=0 --storage-backend=etcd3 --cloud-provider= --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --feature-gates=MountPropagation=false --insecure-bind-address=127.0.0.1 --secure-port=6443 --service-cluster-ip-range=10.43.0.0/16 --service-account-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --tls-private-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --authorization-mode=Node,RBAC --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --bind-address=0.0.0.0 --allow-privileged=true --admission-control=ServiceAccount,NamespaceLifecycle,LimitRanger,PersistentVolumeLabel,DefaultStorageClass,ResourceQuota,DefaultTolerationSeconds --kubelet-client-certificate=/etc/kubernetes/ssl/kube-apiserver.pem --etcd-cafile=/etc/kubernetes/ssl/kube-ca.pem --etcd-certfile=/etc/kubernetes/ssl/kube-node.pem --etcd-keyfile=/etc/kubernetes/ssl/kube-node-key.pem --etcd-servers=https://192.168.7.211:2379 --etcd-prefix=/registry
  • grep -q cloud-provider=azure
  • ‘[’ kube-apiserver = kubelet ‘]’
  • exec kube-apiserver --tls-cert-file=/etc/kubernetes/ssl/kube-apiserver.pem --kubelet-client-key=/etc/kubernetes/ssl/kube-apiserver-key.pem --insecure-port=0 --storage-backend=etcd3 --cloud-provider= --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --feature-gates=MountPropagation=false --insecure-bind-address=127.0.0.1 --secure-port=6443 --service-cluster-ip-range=10.43.0.0/16 --service-account-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --tls-private-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --authorization-mode=Node,RBAC --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --bind-address=0.0.0.0 --allow-privileged=true --admission-control=ServiceAccount,NamespaceLifecycle,LimitRanger,PersistentVolumeLabel,DefaultStorageClass,ResourceQuota,DefaultTolerationSeconds --kubelet-client-certificate=/etc/kubernetes/ssl/kube-apiserver.pem --etcd-cafile=/etc/kubernetes/ssl/kube-ca.pem --etcd-certfile=/etc/kubernetes/ssl/kube-node.pem --etcd-keyfile=/etc/kubernetes/ssl/kube-node-key.pem --etcd-servers=https://192.168.7.211:2379 --etcd-prefix=/registry
    I0521 14:59:30.716578 1 feature_gate.go:190] feature gates: map[MountPropagation:false]
    Flag --insecure-port has been deprecated, This flag will be removed in a future version.
    Flag --insecure-bind-address has been deprecated, This flag will be removed in a future version.
    Flag --admission-control has been deprecated, Use --enable-admission-plugins or --disable-admission-plugins instead. Will be removed in a future version.
    I0521 14:59:30.722350 1 server.go:135] Version: v1.10.1
    Unable to find suitable network address.error=‘No default routes.’. Try to set the AdvertiseAddress directly or provide a valid BindAddress to fix this.