Observed in #18672 (comment)
Probably contributing to: #20916 (comment)
INSTANCE_GROUPS=e2e-gce-builder-2-0-minion-group
NODE_NAMES=e2e-gce-builder-2-0-minion-0501 e2e-gce-builder-2-0-minion-4pdi e2e-gce-builder-2-0-minion-ekcs e2e-gce-builder-2-0-minion-gj5m e2e-gce-builder-2-0-minion-h9co e2e-gce-builder-2-0-minion-pv6j
ERROR: (gcloud.compute.instances.describe) Could not fetch resource:
- The resource 'projects/kubernetes-jenkins-pull/zones/us-central1-f/instances/e2e-gce-builder-2-0-master' was not found
2016/03/07 10:20:02 e2e.go:200: Error running up: exit status 1
2016/03/07 10:20:02 e2e.go:196: Step 'up' finished in 7m42.604863565s
2016/03/07 10:20:02 e2e.go:110: Error starting e2e cluster. Aborting.
Of course the kubelets are complaining:
I0307 18:22:10.110980 3364 kubelet.go:1129] Unable to register e2e-gce-builder-2-0-minion-ekcs with the apiserver: Post https://e2e-gce-builder-2-0-master/api/v1/nodes: dial tcp: lookup e2e-gce-builder-2-0-master: no such host
I0307 18:22:10.170923 3364 kubelet.go:2355] skipping pod synchronization - [ConfigureCBR0 requested, but PodCIDR not set. Will not configure CBR0 right now container runtime is down]
E0307 18:22:10.175011 3364 kubelet.go:2696] Container runtime sanity check failed: docker: failed to get docker version: cannot connect to Docker endpoint
Looks like we didn't even create the master vm, but the error is lost.
Observed in #18672 (comment)
Probably contributing to: #20916 (comment)
Of course the kubelets are complaining:
Looks like we didn't even create the master vm, but the error is lost.