gluster
etcd pods goto Completed state
vagrant@kube1 ~]$ kubectl get pods -ngcs NAME READY STATUS RESTARTS AGE csi-attacher-glusterfsplugin-0 2/2 Running 0 45m csi-nodeplugin-glusterfsplugin-bh5ww 2/2 Running 0 45m csi-nodeplugin-glusterfsplugin-d7db4 2/2 Running 0 45m csi-nodeplugin-glusterfsplugin-vfd2v 2/2 Running 0 45m csi-provisioner-glusterfsplugin-0 3/3 Running 0 45m etcd-b2d2czvkq2 0/1 Completed 0 14m etcd-operator-7cb5bd459b-hl7hs 1/1 Running 0 51m etcd-p5gk77fp5h 0/1 Completed 0 14m gluster-kube1-0 1/1 Running 0 49m gluster-kube2-0 1/1 Running 1 49m gluster-kube3-0 1/1 Running 0 49m [vagrant@kube1 ~]$
Normal Pulled 15m kubelet, kube1 Container image "quay.io/coreos/etcd:v3.3.8" already present on machine Normal Created 15m kubelet, kube1 Created container Normal Started 15m kubelet, kube1 Started container Warning Unhealthy 13m (x2 over 14m) kubelet, kube1 Liveness probe failed: rpc error: code = 2 desc = oci runtime error: exec failed: container_linux.go:247: starting container process caused "process_linux.go:110: decoding init error from pipe caused "read parent: connection reset by peer"" Warning Unhealthy 13m (x17 over 14m) kubelet, kube1 Readiness probe failed: rpc error: code = 2 desc = oci runtime error: exec failed: container_linux.go:247: starting container process caused "process_linux.go:110: decoding init error from pipe caused "read parent: connection reset by peer"" [vagrant@kube1 ~]$
Warning Unhealthy 15m kubelet, kube2 Liveness probe failed: rpc error: code = 2 desc = oci runtime error: exec failed: container_linux.go:247: starting container process caused "process_linux.go:110: decoding init error from pipe caused "read parent: connection reset by peer"" Warning Unhealthy 14m (x18 over 16m) kubelet, kube2 Readiness probe failed: rpc error: code = 2 desc = oci runtime error: exec failed: container_linux.go:247: starting container process caused "process_linux.go:110: decoding init error from pipe caused "read parent: connection reset by peer"" [vagrant@kube1 ~]$
I have the commits: commit d40e12a4c69256194d2a198c07469fde50b2725e commit c164b49befa86f71caaeac1baa4e6bfa5928a25d
Looks like the errors are due to docker, https://github.com/openshift/origin/issues/21590 build docker-1.13.1-88 seems to have the fix, will verify the same and close the issue.
I ran into this as well. The fix I went with was continuing to use the 1808.01 version of the centos/atomic-host Vagrant box. The 1811.01 version is the one that has the bad Docker version.
