1.9.6 hyperkube exited

[rushins]

tectonic installer 1.96 failing and all the RKT instances are exited particularly hyperkube quay.io/coreos/hyperkube:v1.9.6_coreos.0 is exited.

What keywords did you search in tectonic-installer issues before filing this one?

tectonic installer and hyperkube
If you have found any duplicates, you should instead reply there and close this page.
none
If you have not found any duplicates, delete this section and continue on.

Is this a BUG REPORT or FEATURE REQUEST?

kind of bug i think
Choose one: BUG REPORT or FEATURE REQUEST

Versions

• Tectonic version (release or commit hash):
  1.9.6

• Terraform version (terraform version):
  Terraform v0.10.7

• Platform (aws|azure|openstack|metal):
  metal

What happened?

running tectonic installer 1.9.6 ..nodes booted but after connected nodes to see RKT list "hyperkube quay.io/coreos/hyperkube:v1.9.6_coreos.0 is exited" and docker is also not running.

What you expected to happen?

docker should run but docker is not started

How to reproduce it (as minimally and precisely as possible)?

i repeated several installation but same error.

Anything else we need to know?

this is the journalctl -xe shows

Aug 04 15:28:34 lspal177.pal.sap.corp kubelet-wrapper[41033]: + exec /usr/bin/rkt run --uuid-file-save=/var/cache/kubelet-pod.uuid --volume=resolv,kind=host,source=/etc/resolv.conf --mount volume=resolv,t
Aug 04 15:28:34 lspal177.pal.sap.corp kubelet-wrapper[41033]: --client-ca-file=/etc/kubernetes/ca.crt --cloud-provider= --anonymous-auth=false
Aug 04 15:28:35 lspal177.pal.sap.corp kubelet-wrapper[41033]: Flag --require-kubeconfig has been deprecated, You no longer need to use --require-kubeconfig. This will be removed in a future version. Provi
Aug 04 15:28:35 lspal177.pal.sap.corp kubelet-wrapper[41033]: Flag --minimum-container-ttl-duration has been deprecated, Use --eviction-hard or --eviction-soft instead. Will be removed in a future version
Aug 04 15:28:35 lspal177.pal.sap.corp kubelet-wrapper[41033]: I0804 15:28:35.276990 41033 server.go:182] Version: v1.9.6+coreos.0
Aug 04 15:28:35 lspal177.pal.sap.corp kubelet-wrapper[41033]: I0804 15:28:35.277216 41033 feature_gate.go:226] feature gates: &{{} map[]}
Aug 04 15:28:35 lspal177.pal.sap.corp kubelet-wrapper[41033]: I0804 15:28:35.277299 41033 server.go:257] acquiring file lock on "/var/run/lock/kubelet.lock"
Aug 04 15:28:35 lspal177.pal.sap.corp kubelet-wrapper[41033]: I0804 15:28:35.277383 41033 server.go:262] watching for inotify events for: /var/run/lock/kubelet.lock
Aug 04 15:28:35 lspal177.pal.sap.corp kubelet-wrapper[41033]: W0804 15:28:35.277895 41033 server.go:280] --require-kubeconfig is deprecated. Set --kubeconfig without using --require-kubeconfig.
Aug 04 15:28:35 lspal177.pal.sap.corp kubelet-wrapper[41033]: W0804 15:28:35.279168 41033 cni.go:171] Unable to update cni config: No networks found in /etc/kubernetes/cni/net.d
Aug 04 15:28:35 lspal177.pal.sap.corp kubelet-wrapper[41033]: I0804 15:28:35.288289 41033 plugins.go:101] No cloud provider specified.
Aug 04 15:28:35 lspal177.pal.sap.corp kubelet-wrapper[41033]: I0804 15:28:35.316855 41033 server.go:428] --cgroups-per-qos enabled, but --cgroup-root was not specified. defaulting to /
Aug 04 15:28:35 lspal177.pal.sap.corp kubelet-wrapper[41033]: I0804 15:28:35.317783 41033 container_manager_linux.go:242] container manager verified user specified cgroup-root exists: /
Aug 04 15:28:35 lspal177.pal.sap.corp kubelet-wrapper[41033]: I0804 15:28:35.317842 41033 container_manager_linux.go:247] Creating Container Manager object based on Node Config: {RuntimeCgroupsName: Sys
Aug 04 15:28:35 lspal177.pal.sap.corp kubelet-wrapper[41033]: I0804 15:28:35.318161 41033 container_manager_linux.go:266] Creating device plugin manager: false
Aug 04 15:28:35 lspal177.pal.sap.corp kubelet-wrapper[41033]: I0804 15:28:35.318697 41033 kubelet.go:291] Adding manifest path: /etc/kubernetes/manifests
Aug 04 15:28:35 lspal177.pal.sap.corp kubelet-wrapper[41033]: I0804 15:28:35.318778 41033 kubelet.go:316] Watching apiserver
Aug 04 15:28:35 lspal177.pal.sap.corp kubelet-wrapper[41033]: E0804 15:28:35.321080 41033 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:471: Failed to list *v1.Service: Get https://lamak8s-
Aug 04 15:28:35 lspal177.pal.sap.corp kubelet-wrapper[41033]: E0804 15:28:35.321083 41033 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: Get https://lama
Aug 04 15:28:35 lspal177.pal.sap.corp kubelet-wrapper[41033]: E0804 15:28:35.321151 41033 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:480: Failed to list *v1.Node: Get https://lamak8s-api
Aug 04 15:28:35 lspal177.pal.sap.corp kubelet-wrapper[41033]: W0804 15:28:35.324979 41033 kubelet_network.go:139] Hairpin mode set to "promiscuous-bridge" but kubenet is not enabled, falling back to "ha
Aug 04 15:28:35 lspal177.pal.sap.corp kubelet-wrapper[41033]: I0804 15:28:35.325050 41033 kubelet.go:577] Hairpin mode set to "hairpin-veth"
Aug 04 15:28:35 lspal177.pal.sap.corp kubelet-wrapper[41033]: W0804 15:28:35.325292 41033 cni.go:171] Unable to update cni config: No networks found in /etc/kubernetes/cni/net.d
Aug 04 15:28:35 lspal177.pal.sap.corp kubelet-wrapper[41033]: I0804 15:28:35.325377 41033 client.go:80] Connecting to docker on unix:///var/run/docker.sock
Aug 04 15:28:35 lspal177.pal.sap.corp kubelet-wrapper[41033]: I0804 15:28:35.325405 41033 client.go:109] Start docker client with request timeout=2m0s
Aug 04 15:28:35 lspal177.pal.sap.corp kubelet-wrapper[41033]: E0804 15:28:35.325695 41033 kube_docker_client.go:91] failed to retrieve docker version: Cannot connect to the Docker daemon at unix:///var/
Aug 04 15:28:35 lspal177.pal.sap.corp kubelet-wrapper[41033]: W0804 15:28:35.325756 41033 kube_docker_client.go:92] Using empty version for docker client, this may sometimes cause compatibility issue.
Aug 04 15:28:35 lspal177.pal.sap.corp kubelet-wrapper[41033]: Error: failed to run Kubelet: failed to create kubelet: failed to get docker version: Cannot connect to the Docker daemon at unix:///var/run/d
Aug 04 15:28:35 lspal177.pal.sap.corp systemd[1]: kubelet.service: Main process exited, code=exited, status=1/FAILURE
Aug 04 15:28:35 lspal177.pal.sap.corp systemd[1]: kubelet.service: Unit entered failed state.
Aug 04 15:28:35 lspal177.pal.sap.corp systemd[1]: kubelet.service: Failed with result 'exit-code'.