deploy_kubify.sh fails to deploy etcd

[alban]

I followed the instructions in landscape-setup-template and deploy_kubify.sh fails to deploy etcd:

./deploy_kubify.sh
...
Amount of etcd pods (0) doesn't equal specified amount of master nodes (3) yet. Waiting ...
./wait_for_cluster.sh: line 103: fail: command not found

More logs:

``` Waiting for the cluster ... Give the cluster some time to come up ... (waiting for 1 minute) Waiting time is up. Now trying to reach the cluster ... Cluster not yet reachable. Waiting ... Cluster not yet reachable. Waiting ... Cluster reachable. Waiting for all pods to be running ... No resources found. Amount of api server pods (0) doesn't equal specified amount of master nodes (3) yet. Waiting ... Amount of api server pods (1) doesn't equal specified amount of master nodes (3) yet. Waiting ... Amount of api server pods equals specified amount of master nodes: 3 Amount of etcd pods (0) doesn't equal specified amount of master nodes (3) yet. Waiting ... Amount of etcd pods (0) doesn't equal specified amount of master nodes (3) yet. Waiting ... Amount of etcd pods (0) doesn't equal specified amount of master nodes (3) yet. Waiting ... Unable to connect to the server: unexpected EOF Amount of etcd pods (0) doesn't equal specified amount of master nodes (3) yet. Waiting ... Unable to connect to the server: unexpected EOF Amount of etcd pods (0) doesn't equal specified amount of master nodes (3) yet. Waiting ... Amount of etcd pods (1) doesn't equal specified amount of master nodes (3) yet. Waiting ... Amount of etcd pods (1) doesn't equal specified amount of master nodes (3) yet. Waiting ... Amount of etcd pods (1) doesn't equal specified amount of master nodes (3) yet. Waiting ... Amount of etcd pods (1) doesn't equal specified amount of master nodes (3) yet. Waiting ... Amount of etcd pods (1) doesn't equal specified amount of master nodes (3) yet. Waiting ... Amount of etcd pods (1) doesn't equal specified amount of master nodes (3) yet. Waiting ... Amount of etcd pods (1) doesn't equal specified amount of master nodes (3) yet. Waiting ... Amount of etcd pods (1) doesn't equal specified amount of master nodes (3) yet. Waiting ... Amount of etcd pods (1) doesn't equal specified amount of master nodes (3) yet. Waiting ... Amount of etcd pods (1) doesn't equal specified amount of master nodes (3) yet. Waiting ... Amount of etcd pods (1) doesn't equal specified amount of master nodes (3) yet. Waiting ... Amount of etcd pods (1) doesn't equal specified amount of master nodes (3) yet. Waiting ... Amount of etcd pods (1) doesn't equal specified amount of master nodes (3) yet. Waiting ... Amount of etcd pods (1) doesn't equal specified amount of master nodes (3) yet. Waiting ... Amount of etcd pods (1) doesn't equal specified amount of master nodes (3) yet. Waiting ... Amount of etcd pods (1) doesn't equal specified amount of master nodes (3) yet. Waiting ... Amount of etcd pods (1) doesn't equal specified amount of master nodes (3) yet. Waiting ... Amount of etcd pods (1) doesn't equal specified amount of master nodes (3) yet. Waiting ... Amount of etcd pods (1) doesn't equal specified amount of master nodes (3) yet. Waiting ... Amount of etcd pods (1) doesn't equal specified amount of master nodes (3) yet. Waiting ... Amount of etcd pods (1) doesn't equal specified amount of master nodes (3) yet. Waiting ... Amount of etcd pods (1) doesn't equal specified amount of master nodes (3) yet. Waiting ... Amount of etcd pods (1) doesn't equal specified amount of master nodes (3) yet. Waiting ... Unable to connect to the server: unexpected EOF Amount of etcd pods (0) doesn't equal specified amount of master nodes (3) yet. Waiting ... Unable to connect to the server: unexpected EOF Amount of etcd pods (0) doesn't equal specified amount of master nodes (3) yet. Waiting ... Unable to connect to the server: unexpected EOF Amount of etcd pods (0) doesn't equal specified amount of master nodes (3) yet. Waiting ... ./wait_for_cluster.sh: line 103: fail: command not found ```

I got more logs from the master 0:

``` journalctl -u bootkube.service -- Logs begin at Tue 2018-06-12 12:00:02 UTC, end at Tue 2018-06-12 12:25:26 UTC. -- Jun 12 12:01:36 ip-10-251-161-198.eu-west-1.compute.internal systemd[1]: Starting Bootstrap a Kubernetes cluster... Jun 12 12:01:59 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: pubkey: prefix: "quay.io/coreos/bootkube" Jun 12 12:01:59 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: key: "https://quay.io/aci-signing-key" Jun 12 12:01:59 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: gpg key fingerprint is: BFF3 13CD AA56 0B16 A898 7B8F 72AB F5F6 799D 33BC Jun 12 12:01:59 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: Quay.io ACI Converter (ACI conversion signing key) Jun 12 12:01:59 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: Trusting "https://quay.io/aci-signing-key" for prefix "quay.io/coreos/bootkube" without fingerprint review. Jun 12 12:01:59 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: Added key for prefix "quay.io/coreos/bootkube" at "/etc/rkt/trustedkeys/prefix.d/quay.io/coreos/bootkube/bff313cdaa560b16a8987b8f72abf5f6799d33bc" Jun 12 12:01:59 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: Downloading signature: 0 B/473 B Jun 12 12:01:59 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: Downloading signature: 473 B/473 B Jun 12 12:01:59 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: Downloading signature: 473 B/473 B Jun 12 12:02:00 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: Downloading ACI: 0 B/21.2 MB Jun 12 12:02:00 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: Downloading ACI: 32.8 KB/21.2 MB Jun 12 12:02:01 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: Downloading ACI: 21.2 MB/21.2 MB Jun 12 12:02:01 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: image: signature verified: Jun 12 12:02:01 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: Quay.io ACI Converter (ACI conversion signing key) Jun 12 12:02:41 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 160.119241] bootkube[6]: Starting temporary bootstrap control plane... Jun 12 12:02:41 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 160.121004] bootkube[6]: Waiting for api-server... Jun 12 12:02:46 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 165.164586] bootkube[6]: W0612 12:02:46.452714 6 create.go:40] Unable to determine api-server readiness: API Server http status: 0 Jun 12 12:02:51 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 170.124268] bootkube[6]: W0612 12:02:51.412428 6 create.go:40] Unable to determine api-server readiness: API Server http status: 0 Jun 12 12:02:56 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 175.124552] bootkube[6]: W0612 12:02:56.412711 6 create.go:40] Unable to determine api-server readiness: API Server http status: 0 Jun 12 12:03:01 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 180.124785] bootkube[6]: W0612 12:03:01.412949 6 create.go:40] Unable to determine api-server readiness: API Server http status: 0 Jun 12 12:03:06 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 185.124346] bootkube[6]: W0612 12:03:06.412508 6 create.go:40] Unable to determine api-server readiness: API Server http status: 0 Jun 12 12:03:11 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 190.124738] bootkube[6]: W0612 12:03:11.412890 6 create.go:40] Unable to determine api-server readiness: API Server http status: 0 Jun 12 12:03:16 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 195.124978] bootkube[6]: W0612 12:03:16.413130 6 create.go:40] Unable to determine api-server readiness: API Server http status: 0 Jun 12 12:03:21 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 200.125271] bootkube[6]: W0612 12:03:21.413425 6 create.go:40] Unable to determine api-server readiness: API Server http status: 0 Jun 12 12:03:26 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 205.124757] bootkube[6]: W0612 12:03:26.412909 6 create.go:40] Unable to determine api-server readiness: API Server http status: 0 Jun 12 12:03:32 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 211.149248] bootkube[6]: Creating self-hosted assets... Jun 12 12:03:32 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 211.318956] bootkube[6]: I0612 12:03:32.607113 6 log.go:19] secret "etcd-backup" created Jun 12 12:03:32 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 211.319340] bootkube[6]: created etcd-backup secret Jun 12 12:03:32 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 211.384234] bootkube[6]: I0612 12:03:32.671691 6 log.go:19] secret "etcd-client-tls" created Jun 12 12:03:32 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 211.384568] bootkube[6]: created etcd-client-tls secret Jun 12 12:03:32 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 211.546796] bootkube[6]: I0612 12:03:32.834899 6 log.go:19] deployment "etcd-operator" created Jun 12 12:03:32 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 211.547310] bootkube[6]: created etcd-operator deployment Jun 12 12:03:32 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 211.606547] bootkube[6]: I0612 12:03:32.894682 6 log.go:19] secret "etcd-peer-tls" created Jun 12 12:03:32 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 211.606950] bootkube[6]: created etcd-peer-tls secret Jun 12 12:03:32 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 211.672789] bootkube[6]: I0612 12:03:32.960947 6 log.go:19] secret "etcd-server-tls" created Jun 12 12:03:32 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 211.673492] bootkube[6]: created etcd-server-tls secret Jun 12 12:03:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 211.740468] bootkube[6]: I0612 12:03:33.028610 6 log.go:19] service "etcd-service" created Jun 12 12:03:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 211.740834] bootkube[6]: created etcd-service service Jun 12 12:03:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 211.764242] bootkube[6]: I0612 12:03:33.052009 6 log.go:19] storageclass "etcd" created Jun 12 12:03:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 211.764613] bootkube[6]: created etcd storageclasse Jun 12 12:03:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 211.829026] bootkube[6]: I0612 12:03:33.117196 6 log.go:19] secret "kube-apiserver" created Jun 12 12:03:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 211.829469] bootkube[6]: created kube-apiserver secret Jun 12 12:03:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 211.854681] bootkube[6]: I0612 12:03:33.142854 6 log.go:19] daemonset "kube-apiserver" created Jun 12 12:03:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 211.855402] bootkube[6]: created kube-apiserver daemonset Jun 12 12:03:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 211.876549] bootkube[6]: I0612 12:03:33.164723 6 log.go:19] poddisruptionbudget "kube-controller-manager" created Jun 12 12:03:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 211.877153] bootkube[6]: created kube-controller-manager poddisruptionbudget Jun 12 12:03:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 211.934326] bootkube[6]: I0612 12:03:33.222481 6 log.go:19] secret "kube-controller-manager" created Jun 12 12:03:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 211.935350] bootkube[6]: created kube-controller-manager secret Jun 12 12:03:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 211.943334] bootkube[6]: I0612 12:03:33.231522 6 log.go:19] deployment "kube-controller-manager" created Jun 12 12:03:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 211.943878] bootkube[6]: created kube-controller-manager deployment Jun 12 12:03:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 211.955722] bootkube[6]: I0612 12:03:33.243901 6 log.go:19] daemonset "kube-dns" created Jun 12 12:03:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 211.956450] bootkube[6]: created kube-dns daemonset Jun 12 12:03:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 212.024766] bootkube[6]: I0612 12:03:33.312896 6 log.go:19] service "kube-dns" created Jun 12 12:03:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 212.025296] bootkube[6]: created kube-dns service Jun 12 12:03:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 212.032971] bootkube[6]: I0612 12:03:33.321141 6 log.go:19] daemonset "kube-etcd-network-checkpointer" created Jun 12 12:03:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 212.033680] bootkube[6]: created kube-etcd-network-checkpointer daemonset Jun 12 12:03:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 212.091783] bootkube[6]: I0612 12:03:33.379870 6 log.go:19] configmap "kube-flannel-cfg" created Jun 12 12:03:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 212.092270] bootkube[6]: created kube-flannel-cfg configmap Jun 12 12:03:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 212.101143] bootkube[6]: I0612 12:03:33.389256 6 log.go:19] daemonset "kube-flannel" created Jun 12 12:03:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 212.101568] bootkube[6]: created kube-flannel daemonset Jun 12 12:03:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 212.108735] bootkube[6]: I0612 12:03:33.396906 6 log.go:19] daemonset "kube-proxy" created Jun 12 12:03:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 212.109191] bootkube[6]: created kube-proxy daemonset Jun 12 12:03:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 212.119031] bootkube[6]: I0612 12:03:33.407205 6 log.go:19] poddisruptionbudget "kube-scheduler" created Jun 12 12:03:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 212.119600] bootkube[6]: created kube-scheduler poddisruptionbudget Jun 12 12:03:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 212.126492] bootkube[6]: I0612 12:03:33.414672 6 log.go:19] deployment "kube-scheduler" created Jun 12 12:03:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 212.127129] bootkube[6]: created kube-scheduler deployment Jun 12 12:03:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 212.136583] bootkube[6]: I0612 12:03:33.424734 6 log.go:19] storageclass "aws-ebs" created Jun 12 12:03:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 212.137046] bootkube[6]: created aws-ebs storageclasse Jun 12 12:03:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 212.149423] bootkube[6]: I0612 12:03:33.437600 6 log.go:19] clusterrolebinding "system:default-sa" created Jun 12 12:03:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 212.150146] bootkube[6]: created system:default-sa clusterrolebinding Jun 12 12:03:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 212.218409] bootkube[6]: I0612 12:03:33.501847 6 log.go:19] serviceaccount "kubernetes-kube2iam" created Jun 12 12:03:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 212.219525] bootkube[6]: created kubernetes-kube2iam serviceaccount Jun 12 12:03:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 212.247072] bootkube[6]: I0612 12:03:33.535235 6 log.go:19] clusterrole "kubernetes-kube2iam" created Jun 12 12:03:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 212.247495] bootkube[6]: created kubernetes-kube2iam clusterrole Jun 12 12:03:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 212.269345] bootkube[6]: I0612 12:03:33.557509 6 log.go:19] clusterrolebinding "kubernetes-kube2iam" created Jun 12 12:03:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 212.270100] bootkube[6]: created kubernetes-kube2iam clusterrolebinding Jun 12 12:03:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 212.332728] bootkube[6]: I0612 12:03:33.620851 6 log.go:19] daemonset "kube2iam" created Jun 12 12:03:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 212.333179] bootkube[6]: created kube2iam daemonset Jun 12 12:03:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 212.340493] bootkube[6]: I0612 12:03:33.628677 6 log.go:19] daemonset "pod-checkpointer" created Jun 12 12:03:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 212.340770] bootkube[6]: created pod-checkpointer daemonset Jun 12 12:03:48 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 227.342178] bootkube[6]: Pod Status: pod-checkpointer Pending Jun 12 12:03:48 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 227.342579] bootkube[6]: Pod Status: kube-apiserver Pending Jun 12 12:03:48 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 227.342895] bootkube[6]: Pod Status: kube-scheduler Pending Jun 12 12:03:48 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 227.343146] bootkube[6]: Pod Status: kube-controller-manager Pending Jun 12 12:03:48 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 227.343408] bootkube[6]: Pod Status: etcd-operator Pending Jun 12 12:03:48 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 227.343603] bootkube[6]: Pod Status: kube-dns Pending Jun 12 12:04:13 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 252.342294] bootkube[6]: Pod Status: kube-controller-manager Pending Jun 12 12:04:13 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 252.342978] bootkube[6]: Pod Status: etcd-operator Pending Jun 12 12:04:13 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 252.343474] bootkube[6]: Pod Status: kube-dns Pending Jun 12 12:04:13 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 252.343860] bootkube[6]: Pod Status: pod-checkpointer Running Jun 12 12:04:13 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 252.344289] bootkube[6]: Pod Status: kube-apiserver Pending Jun 12 12:04:13 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 252.344663] bootkube[6]: Pod Status: kube-scheduler Pending Jun 12 12:04:23 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 262.342236] bootkube[6]: Pod Status: kube-apiserver Running Jun 12 12:04:23 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 262.342712] bootkube[6]: Pod Status: kube-scheduler Pending Jun 12 12:04:23 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 262.343001] bootkube[6]: Pod Status: kube-controller-manager Pending Jun 12 12:04:23 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 262.343253] bootkube[6]: Pod Status: etcd-operator Pending Jun 12 12:04:23 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 262.343462] bootkube[6]: Pod Status: kube-dns Pending Jun 12 12:04:23 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 262.343662] bootkube[6]: Pod Status: pod-checkpointer Running Jun 12 12:04:28 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 267.342244] bootkube[6]: Pod Status: kube-controller-manager Pending Jun 12 12:04:28 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 267.342687] bootkube[6]: Pod Status: etcd-operator Pending Jun 12 12:04:28 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 267.343415] bootkube[6]: Pod Status: kube-dns Pending Jun 12 12:04:28 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 267.344278] bootkube[6]: Pod Status: pod-checkpointer Pending Jun 12 12:04:28 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 267.344571] bootkube[6]: Pod Status: kube-apiserver Running Jun 12 12:04:28 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 267.345179] bootkube[6]: Pod Status: kube-scheduler Pending Jun 12 12:04:38 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 277.342252] bootkube[6]: Pod Status: pod-checkpointer Running Jun 12 12:04:38 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 277.342827] bootkube[6]: Pod Status: kube-apiserver Running Jun 12 12:04:38 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 277.343282] bootkube[6]: Pod Status: kube-scheduler Pending Jun 12 12:04:38 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 277.343706] bootkube[6]: Pod Status: kube-controller-manager Pending Jun 12 12:04:38 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 277.344431] bootkube[6]: Pod Status: etcd-operator Pending Jun 12 12:04:38 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 277.345091] bootkube[6]: Pod Status: kube-dns Pending Jun 12 12:04:48 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 287.342237] bootkube[6]: Pod Status: kube-dns Running Jun 12 12:04:48 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 287.342662] bootkube[6]: Pod Status: pod-checkpointer Running Jun 12 12:04:48 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 287.342868] bootkube[6]: Pod Status: kube-apiserver Running Jun 12 12:04:48 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 287.343108] bootkube[6]: Pod Status: kube-scheduler Pending Jun 12 12:04:48 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 287.343321] bootkube[6]: Pod Status: kube-controller-manager Pending Jun 12 12:04:48 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 287.343525] bootkube[6]: Pod Status: etcd-operator Pending Jun 12 12:04:53 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 292.342228] bootkube[6]: Pod Status: pod-checkpointer Running Jun 12 12:04:53 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 292.342611] bootkube[6]: Pod Status: kube-apiserver Running Jun 12 12:04:53 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 292.342872] bootkube[6]: Pod Status: kube-scheduler Pending Jun 12 12:04:53 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 292.343121] bootkube[6]: Pod Status: kube-controller-manager Pending Jun 12 12:04:53 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 292.343327] bootkube[6]: Pod Status: etcd-operator Pending Jun 12 12:04:53 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 292.343531] bootkube[6]: Pod Status: kube-dns Pending Jun 12 12:05:03 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 302.342291] bootkube[6]: Pod Status: pod-checkpointer Running Jun 12 12:05:03 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 302.342759] bootkube[6]: Pod Status: kube-apiserver Running Jun 12 12:05:03 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 302.343075] bootkube[6]: Pod Status: kube-scheduler Running Jun 12 12:05:03 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 302.343360] bootkube[6]: Pod Status: kube-controller-manager Running Jun 12 12:05:03 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 302.343654] bootkube[6]: Pod Status: etcd-operator Pending Jun 12 12:05:03 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 302.343958] bootkube[6]: Pod Status: kube-dns Pending Jun 12 12:05:08 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 307.342248] bootkube[6]: Pod Status: kube-controller-manager Running Jun 12 12:05:08 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 307.342687] bootkube[6]: Pod Status: etcd-operator Running Jun 12 12:05:08 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 307.342914] bootkube[6]: Pod Status: kube-dns Pending Jun 12 12:05:08 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 307.343169] bootkube[6]: Pod Status: pod-checkpointer Running Jun 12 12:05:08 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 307.343415] bootkube[6]: Pod Status: kube-apiserver Running Jun 12 12:05:08 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 307.343623] bootkube[6]: Pod Status: kube-scheduler Running Jun 12 12:05:13 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 312.342232] bootkube[6]: Pod Status: kube-dns Running Jun 12 12:05:13 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 312.343016] bootkube[6]: Pod Status: pod-checkpointer Running Jun 12 12:05:13 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 312.344046] bootkube[6]: Pod Status: kube-apiserver Running Jun 12 12:05:13 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 312.344909] bootkube[6]: Pod Status: kube-scheduler Running Jun 12 12:05:13 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 312.345271] bootkube[6]: Pod Status: kube-controller-manager Running Jun 12 12:05:13 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 312.345608] bootkube[6]: Pod Status: etcd-operator Running Jun 12 12:05:13 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 312.345946] bootkube[6]: All self-hosted control plane components successfully started Jun 12 12:05:13 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 312.346305] bootkube[6]: Migrating to self-hosted etcd cluster... Jun 12 12:05:13 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 312.346684] bootkube[6]: I0612 12:05:13.631325 6 log.go:19] warning: ignoring ServerName for user-provided CA for backwards compatibility is deprecated Jun 12 12:05:18 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 317.347400] bootkube[6]: I0612 12:05:18.635559 6 migrate.go:65] created etcd cluster CRD Jun 12 12:05:23 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 322.398350] bootkube[6]: I0612 12:05:23.686510 6 migrate.go:76] etcd-service IP is 10.241.0.15 Jun 12 12:05:23 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 322.403314] bootkube[6]: I0612 12:05:23.691482 6 migrate.go:81] created etcd cluster for migration Jun 12 12:05:38 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 337.406958] bootkube[6]: I0612 12:05:38.695069 6 migrate.go:86] etcd cluster for migration is now running Jun 12 12:05:48 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 347.408000] bootkube[6]: E0612 12:05:48.696154 6 migrate.go:201] failed to create etcd client, will retry: grpc: timed out when dialing Jun 12 12:05:58 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 357.407460] bootkube[6]: E0612 12:05:58.695613 6 migrate.go:201] failed to create etcd client, will retry: grpc: timed out when dialing Jun 12 12:06:08 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 367.407280] bootkube[6]: E0612 12:06:08.695433 6 migrate.go:201] failed to create etcd client, will retry: grpc: timed out when dialing Jun 12 12:06:18 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 377.407370] bootkube[6]: E0612 12:06:18.695520 6 migrate.go:201] failed to create etcd client, will retry: grpc: timed out when dialing Jun 12 12:06:28 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 387.407399] bootkube[6]: E0612 12:06:28.695554 6 migrate.go:201] failed to create etcd client, will retry: grpc: timed out when dialing Jun 12 12:06:38 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 397.407297] bootkube[6]: E0612 12:06:38.695449 6 migrate.go:201] failed to create etcd client, will retry: grpc: timed out when dialing Jun 12 12:06:44 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 402.793096] bootkube[6]: I0612 12:06:44.081254 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:06:48 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 407.418350] bootkube[6]: I0612 12:06:48.706491 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:06:53 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 412.422006] bootkube[6]: I0612 12:06:53.710169 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:06:58 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 417.422114] bootkube[6]: I0612 12:06:58.710272 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:07:03 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 422.421303] bootkube[6]: I0612 12:07:03.709467 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:07:08 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 427.421780] bootkube[6]: I0612 12:07:08.709945 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:07:13 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 432.420267] bootkube[6]: I0612 12:07:13.708350 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:07:18 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 437.421193] bootkube[6]: I0612 12:07:18.709354 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:07:23 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 442.427034] bootkube[6]: I0612 12:07:23.715199 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:07:28 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 447.425255] bootkube[6]: I0612 12:07:28.713306 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:07:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 452.421869] bootkube[6]: I0612 12:07:33.710030 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:07:38 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 457.418666] bootkube[6]: I0612 12:07:38.706830 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:07:43 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 462.418576] bootkube[6]: I0612 12:07:43.706645 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:07:48 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 467.419865] bootkube[6]: I0612 12:07:48.708001 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:07:53 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 472.418443] bootkube[6]: I0612 12:07:53.706595 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:07:58 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 477.419238] bootkube[6]: I0612 12:07:58.707408 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:08:03 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 482.419323] bootkube[6]: I0612 12:08:03.707417 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:08:08 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 487.421043] bootkube[6]: I0612 12:08:08.709199 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:08:13 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 492.425894] bootkube[6]: I0612 12:08:13.714054 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:08:18 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 497.420443] bootkube[6]: I0612 12:08:18.708567 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:08:23 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 502.420021] bootkube[6]: I0612 12:08:23.708095 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:08:28 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 507.420062] bootkube[6]: I0612 12:08:28.708160 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:08:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 512.419445] bootkube[6]: I0612 12:08:33.707571 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:08:38 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 517.418333] bootkube[6]: I0612 12:08:38.706493 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:08:43 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 522.418377] bootkube[6]: I0612 12:08:43.706460 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:08:48 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 527.419674] bootkube[6]: I0612 12:08:48.707834 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:08:53 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 532.418884] bootkube[6]: I0612 12:08:53.707016 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:08:58 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 537.418283] bootkube[6]: I0612 12:08:58.706443 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:09:03 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 542.419955] bootkube[6]: I0612 12:09:03.708091 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:09:08 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 547.418278] bootkube[6]: I0612 12:09:08.706412 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:09:13 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 552.418333] bootkube[6]: I0612 12:09:13.706493 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:09:18 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 557.419737] bootkube[6]: I0612 12:09:18.707893 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:09:23 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 562.419283] bootkube[6]: I0612 12:09:23.707441 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:09:28 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 567.418357] bootkube[6]: I0612 12:09:28.706441 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:09:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 572.419225] bootkube[6]: I0612 12:09:33.707367 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:09:38 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 577.418349] bootkube[6]: I0612 12:09:38.706514 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:09:43 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 582.421014] bootkube[6]: I0612 12:09:43.709171 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:09:48 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 587.419085] bootkube[6]: I0612 12:09:48.707250 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:09:53 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 592.418540] bootkube[6]: I0612 12:09:53.706686 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:09:58 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 597.418486] bootkube[6]: I0612 12:09:58.706638 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:10:03 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 602.418789] bootkube[6]: I0612 12:10:03.706943 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:10:08 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 607.418724] bootkube[6]: I0612 12:10:08.706890 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:10:13 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 612.418973] bootkube[6]: I0612 12:10:13.706994 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:10:18 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 617.418589] bootkube[6]: I0612 12:10:18.706711 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:10:23 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 622.419301] bootkube[6]: I0612 12:10:23.707458 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:10:28 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 627.422099] bootkube[6]: I0612 12:10:28.710234 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:10:33 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 632.418561] bootkube[6]: I0612 12:10:33.706726 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:10:38 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 637.418533] bootkube[6]: I0612 12:10:38.706704 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:10:38 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 637.430243] bootkube[6]: I0612 12:10:38.718423 6 migrate.go:215] still waiting for boot-etcd to be deleted... Jun 12 12:10:43 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 642.460225] bootkube[6]: Error: failed to wait for boot-etcd to be removed: timed out waiting for the condition Jun 12 12:10:43 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 642.460644] bootkube[6]: Tearing down temporary bootstrap control plane... Jun 12 12:10:43 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 642.461553] bootkube[6]: Error: failed to wait for boot-etcd to be removed: timed out waiting for the condition Jun 12 12:10:43 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 642.461884] bootkube[6]: Error: failed to wait for boot-etcd to be removed: timed out waiting for the condition Jun 12 12:10:43 ip-10-251-161-198.eu-west-1.compute.internal rkt[3452]: [ 642.462087] bootkube[6]: failed to wait for boot-etcd to be removed: timed out waiting for the condition Jun 12 12:10:43 ip-10-251-161-198.eu-west-1.compute.internal systemd[1]: bootkube.service: Main process exited, code=exited, status=1/FAILURE Jun 12 12:10:43 ip-10-251-161-198.eu-west-1.compute.internal systemd[1]: Failed to start Bootstrap a Kubernetes cluster. Jun 12 12:10:43 ip-10-251-161-198.eu-west-1.compute.internal systemd[1]: bootkube.service: Unit entered failed state. Jun 12 12:10:43 ip-10-251-161-198.eu-west-1.compute.internal systemd[1]: bootkube.service: Failed with result 'exit-code'. ```

The process etcd-operator is running but no further etcd processes. The Docker logs of the etcd-operator container are the following:

``` time="2018-06-12T12:14:44Z" level=info msg="DEPRECATION WARNING: the pv-provisioner flag will be removed in next release." time="2018-06-12T12:14:44Z" level=info msg="etcd-operator Version: 0.6.1" time="2018-06-12T12:14:44Z" level=info msg="Git SHA: ba44539" time="2018-06-12T12:14:44Z" level=info msg="Go Version: go1.9.1" time="2018-06-12T12:14:44Z" level=info msg="Go OS/Arch: linux/amd64" E0612 12:14:44.604912 1 leaderelection.go:224] error retrieving resource lock kube-system/etcd-operator: Get https://10.241.0.1:443/api/v1/namespaces/kube-system/endpoints/etcd-operator: dial tcp 10.241.0.1:443: getsockopt: connection refused E0612 12:15:49.843625 1 leaderelection.go:224] error retrieving resource lock kube-system/etcd-operator: the server was unable to return a response in the time allotted, but may still be processing the request (get endpoints etcd-operator) E0612 12:16:50.776395 1 leaderelection.go:224] error retrieving resource lock kube-system/etcd-operator: Get https://10.241.0.1:443/api/v1/namespaces/kube-system/endpoints/etcd-operator: unexpected EOF E0612 12:16:54.377420 1 leaderelection.go:224] error retrieving resource lock kube-system/etcd-operator: Get https://10.241.0.1:443/api/v1/namespaces/kube-system/endpoints/etcd-operator: dial tcp 10.241.0.1:443: getsockopt: connection refused ```

And the errors go on for a while.

On master 1, neither etcd-operator or etcd are running.

On master 2, etcd is running but cannot complete an election because it's alone.

[schu]

E0612 12:16:54.377420       1 leaderelection.go:224] error retrieving resource lock kube-system/etcd-operator: Get https://10.241.0.1:443/api/v1/namespaces/kube-system/endpoints/etcd-operator: dial tcp 10.241.0.1:443: getsockopt: connection refused

10.241.0.1 is the service address of the Kubernetes API. There is an unknown issue with failed apiserver pods that I'm currently looking into (hence connection refused). It can lead to different errors during setup, the error above is just one of the symptoms that we observe.

./wait_for_cluster.sh: line 103: fail: command not found

I created a separate issue for that: https://github.com/gardener/landscape-setup/issues/11

[afritzler]

Is this issue related to kubify or the landscape setup project?

[afritzler]

@Diaphteiros can you comment on that one?

[schu]

@afritzler as far as I have seen, that was also due to https://github.com/gardener/kubify/issues/49 and can be closed as well.

[afritzler]

Understood. Well, I would suggest closing this one here and opening an issue in the landscape setup.

[Diaphteiros]

@afritzler That issue is related to kubify, but I also think it could have been connected to https://github.com/gardener/kubify/issues/49 and be resolved by now. I should probably update the kubify submodule in the landscape setup project soon to see whether this problem still occurs.

[afritzler]

Closing this one since the this should be resolved with #49.