This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 1 succeeded
Started2023-01-30 16:49
Elapsed20m22s
Revisionmaster

Test Failures


kubetest2 Up 16m31s

exit status 1
				from junit_runner.xml

Filter through log files | View test history on testgrid


Show 1 Passed Tests

Error lines from build-log.txt

... skipping 156 lines ...
....................................Updated [https://www.googleapis.com/compute/v1/projects/kubernetes-gci-ingress-1-3].
...done.
WARNING: No host aliases were added to your SSH configs because you do not have any running instances. Try running this command again after running some instances.
I0130 16:50:30.878148    5730 up.go:44] Cleaning up any leaked resources from previous cluster
I0130 16:50:30.878276    5730 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/e89b0cf7-a0bd-11ed-9a0c-f25a29267a91/kops toolbox dump --name ha-migration.k8s.local --dir /logs/artifacts --private-key /tmp/kops-ssh3122357587/key --ssh-user prow
I0130 16:50:30.878293    5730 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/e89b0cf7-a0bd-11ed-9a0c-f25a29267a91/kops toolbox dump --name ha-migration.k8s.local --dir /logs/artifacts --private-key /tmp/kops-ssh3122357587/key --ssh-user prow
Error: Cluster.kops.k8s.io "ha-migration.k8s.local" not found
W0130 16:50:31.099703    5730 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0130 16:50:31.099755    5730 down.go:48] /home/prow/go/src/k8s.io/kops/_rundir/e89b0cf7-a0bd-11ed-9a0c-f25a29267a91/kops delete cluster --name ha-migration.k8s.local --yes
I0130 16:50:31.099767    5730 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/e89b0cf7-a0bd-11ed-9a0c-f25a29267a91/kops delete cluster --name ha-migration.k8s.local --yes
Error: error reading cluster configuration: Cluster.kops.k8s.io "ha-migration.k8s.local" not found
I0130 16:50:31.237584    5730 gcs.go:51] gsutil ls -b -p kubernetes-gci-ingress-1-3 gs://kubernetes-gci-ingress-1-3-state-e8
I0130 16:50:31.237646    5730 local.go:42] ⚙️ gsutil ls -b -p kubernetes-gci-ingress-1-3 gs://kubernetes-gci-ingress-1-3-state-e8
I0130 16:50:33.797637    5730 gcs.go:70] gsutil mb -p kubernetes-gci-ingress-1-3 gs://kubernetes-gci-ingress-1-3-state-e8
I0130 16:50:33.797711    5730 local.go:42] ⚙️ gsutil mb -p kubernetes-gci-ingress-1-3 gs://kubernetes-gci-ingress-1-3-state-e8
Creating gs://kubernetes-gci-ingress-1-3-state-e8/...
I0130 16:50:36.410034    5730 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2023/01/30 16:50:36 failed to get external ip from metadata service: http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip returned 404
I0130 16:50:36.426168    5730 http.go:37] curl https://ip.jsb.workers.dev
I0130 16:50:36.526520    5730 up.go:167] /home/prow/go/src/k8s.io/kops/_rundir/e89b0cf7-a0bd-11ed-9a0c-f25a29267a91/kops create cluster --name ha-migration.k8s.local --cloud gce --kubernetes-version v1.23.16 --ssh-public-key /tmp/kops-ssh3122357587/key.pub --set cluster.spec.nodePortAccess=0.0.0.0/0 --channel=alpha --node-count=1 --master-count=3 --zones=us-central1-a,us-central1-b,us-central1-c --master-zones=us-central1-a,us-central1-b,us-central1-c --gce-service-account=default --admin-access 34.72.53.191/32 --master-volume-size 48 --node-volume-size 48 --master-size e2-standard-2 --project kubernetes-gci-ingress-1-3
I0130 16:50:36.526587    5730 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/e89b0cf7-a0bd-11ed-9a0c-f25a29267a91/kops create cluster --name ha-migration.k8s.local --cloud gce --kubernetes-version v1.23.16 --ssh-public-key /tmp/kops-ssh3122357587/key.pub --set cluster.spec.nodePortAccess=0.0.0.0/0 --channel=alpha --node-count=1 --master-count=3 --zones=us-central1-a,us-central1-b,us-central1-c --master-zones=us-central1-a,us-central1-b,us-central1-c --gce-service-account=default --admin-access 34.72.53.191/32 --master-volume-size 48 --node-volume-size 48 --master-size e2-standard-2 --project kubernetes-gci-ingress-1-3
I0130 16:50:36.583264    6049 create_cluster.go:882] Using SSH public key: /tmp/kops-ssh3122357587/key.pub
I0130 16:50:36.835935    6049 new_cluster.go:573] VMs will be configured to use specified Service Account: default
I0130 16:50:36.836067    6049 new_cluster.go:1338] Cloud Provider ID: "gce"
... skipping 527 lines ...
I0130 16:50:49.000856    6069 keypair.go:226] Issuing new certificate: "etcd-peers-ca-events"
I0130 16:50:49.001730    6069 keypair.go:226] Issuing new certificate: "apiserver-aggregator-ca"
W0130 16:50:49.179603    6069 vfs_keystorereader.go:143] CA private key was not found
I0130 16:50:49.383734    6069 keypair.go:226] Issuing new certificate: "kubernetes-ca"
I0130 16:50:49.386464    6069 keypair.go:226] Issuing new certificate: "service-account"
I0130 16:51:01.454234    6069 executor.go:111] Tasks: 50 done / 91 total; 23 can run
W0130 16:51:11.447036    6069 executor.go:139] error running task "ForwardingRule/api-ha-migration-k8s-local" (9m50s remaining to succeed): error creating ForwardingRule "api-ha-migration-k8s-local": googleapi: Error 400: The resource 'projects/kubernetes-gci-ingress-1-3/regions/us-central1/targetPools/api-ha-migration-k8s-local' is not ready, resourceNotReady
I0130 16:51:11.447127    6069 executor.go:111] Tasks: 72 done / 91 total; 13 can run
I0130 16:51:18.230490    6069 executor.go:111] Tasks: 85 done / 91 total; 6 can run
I0130 16:51:35.144551    6069 executor.go:111] Tasks: 91 done / 91 total; 0 can run
I0130 16:51:35.238791    6069 update_cluster.go:323] Exporting kubeconfig for cluster
kOps has set your kubectl context to ha-migration.k8s.local

... skipping 7 lines ...
 * read about installing addons at: https://kops.sigs.k8s.io/addons.

I0130 16:51:45.619098    5730 up.go:251] /home/prow/go/src/k8s.io/kops/_rundir/e89b0cf7-a0bd-11ed-9a0c-f25a29267a91/kops validate cluster --name ha-migration.k8s.local --count 10 --wait 15m0s
I0130 16:51:45.619172    5730 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/e89b0cf7-a0bd-11ed-9a0c-f25a29267a91/kops validate cluster --name ha-migration.k8s.local --count 10 --wait 15m0s
Validating cluster ha-migration.k8s.local

W0130 16:52:16.139367    6088 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.28.123.124/api/v1/nodes": dial tcp 34.28.123.124:443: i/o timeout
W0130 16:52:33.288384    6088 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.28.123.124/api/v1/nodes": dial tcp 34.28.123.124:443: connect: connection refused
W0130 16:52:43.298888    6088 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.28.123.124/api/v1/nodes": dial tcp 34.28.123.124:443: connect: connection refused
W0130 16:52:53.302441    6088 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.28.123.124/api/v1/nodes": dial tcp 34.28.123.124:443: connect: connection refused
W0130 16:53:03.306251    6088 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.28.123.124/api/v1/nodes": dial tcp 34.28.123.124:443: connect: connection refused
W0130 16:53:13.310150    6088 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.28.123.124/api/v1/nodes": dial tcp 34.28.123.124:443: connect: connection refused
W0130 16:53:23.315950    6088 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.28.123.124/api/v1/nodes": dial tcp 34.28.123.124:443: connect: connection refused
W0130 16:53:33.318993    6088 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.28.123.124/api/v1/nodes": dial tcp 34.28.123.124:443: connect: connection refused
W0130 16:53:43.322431    6088 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.28.123.124/api/v1/nodes": dial tcp 34.28.123.124:443: connect: connection refused
W0130 16:53:53.328765    6088 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.28.123.124/api/v1/nodes": dial tcp 34.28.123.124:443: connect: connection refused
W0130 16:54:03.341107    6088 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.28.123.124/api/v1/nodes": dial tcp 34.28.123.124:443: connect: connection refused
W0130 16:54:23.350085    6088 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.28.123.124/api/v1/nodes": net/http: TLS handshake timeout
W0130 16:54:33.354521    6088 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.28.123.124/api/v1/nodes": dial tcp 34.28.123.124:443: connect: connection refused
W0130 16:54:59.605147    6088 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.28.123.124/api/v1/nodes": dial tcp 34.28.123.124:443: connect: connection refused - error from a previous attempt: read tcp 10.60.205.183:49506->34.28.123.124:443: read: connection reset by peer
I0130 16:55:18.382287    5730 boskos.go:86] Sending heartbeat to Boskos
W0130 16:55:19.612667    6088 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.28.123.124/api/v1/nodes": net/http: TLS handshake timeout
W0130 16:55:29.618958    6088 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.28.123.124/api/v1/nodes": dial tcp 34.28.123.124:443: connect: connection refused
W0130 16:55:39.624774    6088 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.28.123.124/api/v1/nodes": dial tcp 34.28.123.124:443: connect: connection refused
W0130 16:55:49.628760    6088 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.28.123.124/api/v1/nodes": dial tcp 34.28.123.124:443: connect: connection refused
W0130 16:55:59.633365    6088 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.28.123.124/api/v1/nodes": dial tcp 34.28.123.124:443: connect: connection refused
W0130 16:56:09.636537    6088 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.28.123.124/api/v1/nodes": dial tcp 34.28.123.124:443: connect: connection refused
W0130 16:56:19.641043    6088 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.28.123.124/api/v1/nodes": dial tcp 34.28.123.124:443: connect: connection refused
I0130 16:56:30.114540    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-c	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 10 lines ...
KIND	NAME																		MESSAGE
Machine	https://www.googleapis.com/compute/v1/projects/kubernetes-gci-ingress-1-3/zones/us-central1-a/instances/control-plane-us-central1-a-8bbk	machine "https://www.googleapis.com/compute/v1/projects/kubernetes-gci-ingress-1-3/zones/us-central1-a/instances/control-plane-us-central1-a-8bbk" has not yet joined cluster
Machine	https://www.googleapis.com/compute/v1/projects/kubernetes-gci-ingress-1-3/zones/us-central1-a/instances/nodes-us-central1-a-jftg		machine "https://www.googleapis.com/compute/v1/projects/kubernetes-gci-ingress-1-3/zones/us-central1-a/instances/nodes-us-central1-a-jftg" has not yet joined cluster
Node	control-plane-us-central1-b-n3nc														node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6														node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready

Validation Failed
W0130 16:56:31.087810    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 16:56:41.439593    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 19 lines ...
Pod	kube-system/cilium-rmsx5															system-node-critical pod "cilium-rmsx5" is pending
Pod	kube-system/coredns-5d479c4f64-9g56d														system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq													system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b													system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending
Pod	kube-system/kube-controller-manager-control-plane-us-central1-c-jnn6										system-cluster-critical pod "kube-controller-manager-control-plane-us-central1-c-jnn6" is not ready (kube-controller-manager)

Validation Failed
W0130 16:56:42.354346    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 16:56:52.803722    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 21 lines ...
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq													system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b													system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending
Pod	kube-system/kops-controller-9kn9s														system-cluster-critical pod "kops-controller-9kn9s" is pending
Pod	kube-system/kops-controller-wcslm														system-cluster-critical pod "kops-controller-wcslm" is pending
Pod	kube-system/kube-controller-manager-control-plane-us-central1-c-jnn6										system-cluster-critical pod "kube-controller-manager-control-plane-us-central1-c-jnn6" is not ready (kube-controller-manager)

Validation Failed
W0130 16:56:53.792716    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 16:57:04.132260    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 24 lines ...
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending
Pod	kube-system/kops-controller-9kn9s													system-cluster-critical pod "kops-controller-9kn9s" is pending
Pod	kube-system/kops-controller-ls6rt													system-cluster-critical pod "kops-controller-ls6rt" is pending
Pod	kube-system/kops-controller-wcslm													system-cluster-critical pod "kops-controller-wcslm" is pending
Pod	kube-system/kube-controller-manager-control-plane-us-central1-c-jnn6									system-cluster-critical pod "kube-controller-manager-control-plane-us-central1-c-jnn6" is not ready (kube-controller-manager)

Validation Failed
W0130 16:57:05.047512    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 16:57:15.434397    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 24 lines ...
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending
Pod	kube-system/kops-controller-ls6rt													system-cluster-critical pod "kops-controller-ls6rt" is pending
Pod	kube-system/kube-apiserver-control-plane-us-central1-c-jnn6										system-cluster-critical pod "kube-apiserver-control-plane-us-central1-c-jnn6" is pending
Pod	kube-system/kube-controller-manager-control-plane-us-central1-a-8bbk									system-cluster-critical pod "kube-controller-manager-control-plane-us-central1-a-8bbk" is pending
Pod	kube-system/kube-controller-manager-control-plane-us-central1-c-jnn6									system-cluster-critical pod "kube-controller-manager-control-plane-us-central1-c-jnn6" is not ready (kube-controller-manager)

Validation Failed
W0130 16:57:16.337936    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 16:57:26.718627    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 22 lines ...
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending
Pod	kube-system/kube-controller-manager-control-plane-us-central1-a-8bbk									system-cluster-critical pod "kube-controller-manager-control-plane-us-central1-a-8bbk" is not ready (kube-controller-manager)
Pod	kube-system/kube-controller-manager-control-plane-us-central1-c-jnn6									system-cluster-critical pod "kube-controller-manager-control-plane-us-central1-c-jnn6" is not ready (kube-controller-manager)

Validation Failed
W0130 16:57:27.595894    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 16:57:37.990783    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 20 lines ...
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending
Pod	kube-system/kube-controller-manager-control-plane-us-central1-a-8bbk									system-cluster-critical pod "kube-controller-manager-control-plane-us-central1-a-8bbk" is not ready (kube-controller-manager)
Pod	kube-system/kube-controller-manager-control-plane-us-central1-c-jnn6									system-cluster-critical pod "kube-controller-manager-control-plane-us-central1-c-jnn6" is not ready (kube-controller-manager)

Validation Failed
W0130 16:57:38.841278    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 16:57:49.184461    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 18 lines ...
Pod	kube-system/cilium-gq8cp														system-node-critical pod "cilium-gq8cp" is not ready (cilium-agent)
Pod	kube-system/cilium-rmsx5														system-node-critical pod "cilium-rmsx5" is not ready (cilium-agent)
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 16:57:50.034527    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 16:58:00.345874    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 15 lines ...
Node	control-plane-us-central1-b-n3nc													node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 16:58:01.295359    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 16:58:11.686198    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 17 lines ...
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending
Pod	kube-system/etcd-manager-events-control-plane-us-central1-a-8bbk									system-cluster-critical pod "etcd-manager-events-control-plane-us-central1-a-8bbk" is pending
Pod	kube-system/etcd-manager-main-control-plane-us-central1-a-8bbk										system-cluster-critical pod "etcd-manager-main-control-plane-us-central1-a-8bbk" is pending

Validation Failed
W0130 16:58:12.610200    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 16:58:22.866820    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 16 lines ...
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending
Pod	kube-system/kube-apiserver-control-plane-us-central1-a-8bbk										system-cluster-critical pod "kube-apiserver-control-plane-us-central1-a-8bbk" is pending

Validation Failed
W0130 16:58:23.795937    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 16:58:34.108459    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 15 lines ...
Node	control-plane-us-central1-b-n3nc													node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 16:58:35.008946    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 16:58:45.346553    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 15 lines ...
Node	control-plane-us-central1-b-n3nc													node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 16:58:46.297539    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 16:58:56.641717    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 15 lines ...
Node	control-plane-us-central1-b-n3nc													node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 16:58:57.506196    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 16:59:07.919671    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 15 lines ...
Node	control-plane-us-central1-b-n3nc													node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 16:59:08.791585    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 16:59:19.230485    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 15 lines ...
Node	control-plane-us-central1-b-n3nc													node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 16:59:20.131667    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 16:59:30.500623    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 15 lines ...
Node	control-plane-us-central1-b-n3nc													node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 16:59:31.391452    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 16:59:41.782534    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 15 lines ...
Node	control-plane-us-central1-b-n3nc													node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 16:59:42.680439    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 16:59:53.125158    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 15 lines ...
Node	control-plane-us-central1-b-n3nc													node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 16:59:53.988893    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 17:00:04.468282    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 15 lines ...
Node	control-plane-us-central1-b-n3nc													node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 17:00:05.283987    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 17:00:15.610319    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 15 lines ...
Node	control-plane-us-central1-b-n3nc													node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 17:00:16.512257    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 17:00:18.394546    5730 boskos.go:86] Sending heartbeat to Boskos
I0130 17:00:26.781645    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 16 lines ...
Node	control-plane-us-central1-b-n3nc													node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 17:00:27.720514    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 17:00:38.010588    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 15 lines ...
Node	control-plane-us-central1-b-n3nc													node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 17:00:38.837979    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 17:00:49.139345    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 15 lines ...
Node	control-plane-us-central1-b-n3nc													node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 17:00:50.054278    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 17:01:00.396437    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 15 lines ...
Node	control-plane-us-central1-b-n3nc													node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 17:01:01.319667    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 17:01:11.599187    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 15 lines ...
Node	control-plane-us-central1-b-n3nc													node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 17:01:12.432750    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 17:01:22.757947    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 15 lines ...
Node	control-plane-us-central1-b-n3nc													node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 17:01:23.626767    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 17:01:33.990820    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 15 lines ...
Node	control-plane-us-central1-b-n3nc													node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 17:01:34.898243    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 17:01:45.246266    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 15 lines ...
Node	control-plane-us-central1-b-n3nc													node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 17:01:46.044843    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 17:01:56.359473    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 15 lines ...
Node	control-plane-us-central1-b-n3nc													node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 17:01:57.283326    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 17:02:07.687556    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 15 lines ...
Node	control-plane-us-central1-b-n3nc													node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 17:02:08.560236    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 17:02:18.840909    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 15 lines ...
Node	control-plane-us-central1-b-n3nc													node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 17:02:19.733594    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 17:02:30.149294    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 15 lines ...
Node	control-plane-us-central1-b-n3nc													node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 17:02:30.979842    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 17:02:41.338639    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 15 lines ...
Node	control-plane-us-central1-b-n3nc													node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 17:02:42.234747    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 17:02:52.575200    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 15 lines ...
Node	control-plane-us-central1-b-n3nc													node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 17:02:53.527296    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 17:03:03.870407    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 15 lines ...
Node	control-plane-us-central1-b-n3nc													node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 17:03:04.739523    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 17:03:15.122411    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 15 lines ...
Node	control-plane-us-central1-b-n3nc													node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 17:03:16.007864    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 17:03:26.435655    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 15 lines ...
Node	control-plane-us-central1-b-n3nc													node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 17:03:27.316732    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 17:03:37.610970    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 15 lines ...
Node	control-plane-us-central1-b-n3nc													node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 17:03:38.541910    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 17:03:48.989963    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 15 lines ...
Node	control-plane-us-central1-b-n3nc													node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 17:03:49.838076    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 17:04:00.159186    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 15 lines ...
Node	control-plane-us-central1-b-n3nc													node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 17:04:01.159240    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 17:04:11.551604    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 15 lines ...
Node	control-plane-us-central1-b-n3nc													node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 17:04:12.364617    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 17:04:22.741639    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 15 lines ...
Node	control-plane-us-central1-b-n3nc													node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 17:04:23.589975    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 17:04:33.944647    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 15 lines ...
Node	control-plane-us-central1-b-n3nc													node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 17:04:34.776116    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 17:04:45.263010    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 15 lines ...
Node	control-plane-us-central1-b-n3nc													node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 17:04:46.151912    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 17:04:56.465937    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 15 lines ...
Node	control-plane-us-central1-b-n3nc													node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 17:04:57.329599    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 17:05:07.673837    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 15 lines ...
Node	control-plane-us-central1-b-n3nc													node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 17:05:08.587579    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 17:05:18.405982    5730 boskos.go:86] Sending heartbeat to Boskos
I0130 17:05:18.936115    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 16 lines ...
Node	control-plane-us-central1-b-n3nc													node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 17:05:19.804775    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 17:05:30.119918    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 15 lines ...
Node	control-plane-us-central1-b-n3nc													node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 17:05:30.985130    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 17:05:41.296346    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 15 lines ...
Node	control-plane-us-central1-b-n3nc													node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 17:05:42.105166    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 17:05:52.455156    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 15 lines ...
Node	control-plane-us-central1-b-n3nc													node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 17:05:53.351371    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 17:06:03.750625    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 15 lines ...
Node	control-plane-us-central1-b-n3nc													node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 17:06:04.617383    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 17:06:14.951207    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 15 lines ...
Node	control-plane-us-central1-b-n3nc													node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 17:06:15.812120    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 17:06:26.113812    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 15 lines ...
Node	control-plane-us-central1-b-n3nc													node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 17:06:26.928267    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
I0130 17:06:37.225499    6088 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-us-central1-a	ControlPlane	e2-standard-2	1	1	us-central1
control-plane-us-central1-b	ControlPlane	e2-standard-2	1	1	us-central1
... skipping 15 lines ...
Node	control-plane-us-central1-b-n3nc													node "control-plane-us-central1-b-n3nc" of role "control-plane" is not ready
Node	control-plane-us-central1-c-jnn6													node "control-plane-us-central1-c-jnn6" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-9g56d													system-cluster-critical pod "coredns-5d479c4f64-9g56d" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-s5lmq												system-cluster-critical pod "coredns-autoscaler-557ccb4c66-s5lmq" is pending
Pod	kube-system/dns-controller-6f69f47785-rdl7b												system-cluster-critical pod "dns-controller-6f69f47785-rdl7b" is pending

Validation Failed
W0130 17:06:38.024097    6088 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: validation failed: wait time exceeded during validation
I0130 17:06:48.034218    5730 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/e89b0cf7-a0bd-11ed-9a0c-f25a29267a91/kops toolbox dump --name ha-migration.k8s.local --dir /logs/artifacts --private-key /tmp/kops-ssh3122357587/key --ssh-user prow
I0130 17:06:48.034277    5730 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/e89b0cf7-a0bd-11ed-9a0c-f25a29267a91/kops toolbox dump --name ha-migration.k8s.local --dir /logs/artifacts --private-key /tmp/kops-ssh3122357587/key --ssh-user prow
I0130 17:06:48.431678    6098 gce.go:99] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
2023/01/30 17:06:53 Dumping node control-plane-us-central1-a-8bbk
2023/01/30 17:06:57 error dumping node control-plane-us-central1-a-8bbk: error executing command "if command -v kubectl &> /dev/null; then kubectl logs -n kube-system --all-containers -l \"k8s-app=external-dns\"; fi": Process exited with status 1
2023/01/30 17:06:57 error dumping node control-plane-us-central1-a-8bbk: error executing command "if command -v kubectl &> /dev/null; then kubectl logs -n kube-system --all-containers -l \"k8s-app=dns-controller\"; fi": Process exited with status 1
2023/01/30 17:06:57 Dumping node control-plane-us-central1-b-n3nc
2023/01/30 17:07:01 error dumping node control-plane-us-central1-b-n3nc: error executing command "if command -v kubectl &> /dev/null; then kubectl logs -n kube-system --all-containers -l \"k8s-app=external-dns\"; fi": Process exited with status 1
2023/01/30 17:07:01 error dumping node control-plane-us-central1-b-n3nc: error executing command "if command -v kubectl &> /dev/null; then kubectl logs -n kube-system --all-containers -l \"k8s-app=dns-controller\"; fi": Process exited with status 1
2023/01/30 17:07:01 Dumping node control-plane-us-central1-c-jnn6
2023/01/30 17:07:05 error dumping node control-plane-us-central1-c-jnn6: error executing command "if command -v kubectl &> /dev/null; then kubectl logs -n kube-system --all-containers -l \"k8s-app=external-dns\"; fi": Process exited with status 1
2023/01/30 17:07:05 error dumping node control-plane-us-central1-c-jnn6: error executing command "if command -v kubectl &> /dev/null; then kubectl logs -n kube-system --all-containers -l \"k8s-app=dns-controller\"; fi": Process exited with status 1
2023/01/30 17:07:05 dumping node not registered in kubernetes: 34.133.7.22
2023/01/30 17:07:05 Dumping node 34.133.7.22
I0130 17:07:07.351464    5730 dumplogs.go:79] /home/prow/go/src/k8s.io/kops/_rundir/e89b0cf7-a0bd-11ed-9a0c-f25a29267a91/kops get cluster --name ha-migration.k8s.local -o yaml
I0130 17:07:07.351511    5730 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/e89b0cf7-a0bd-11ed-9a0c-f25a29267a91/kops get cluster --name ha-migration.k8s.local -o yaml
I0130 17:07:07.507344    5730 dumplogs.go:79] /home/prow/go/src/k8s.io/kops/_rundir/e89b0cf7-a0bd-11ed-9a0c-f25a29267a91/kops get instancegroups --name ha-migration.k8s.local -o yaml
I0130 17:07:07.507376    5730 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/e89b0cf7-a0bd-11ed-9a0c-f25a29267a91/kops get instancegroups --name ha-migration.k8s.local -o yaml
... skipping 167 lines ...
Deleted cluster: "ha-migration.k8s.local"
I0130 17:09:27.720781    5730 gcs.go:88] gsutil -u kubernetes-gci-ingress-1-3 rm -r gs://kubernetes-gci-ingress-1-3-state-e8
I0130 17:09:27.720861    5730 local.go:42] ⚙️ gsutil -u kubernetes-gci-ingress-1-3 rm -r gs://kubernetes-gci-ingress-1-3-state-e8
Removing gs://kubernetes-gci-ingress-1-3-state-e8/...
I0130 17:09:30.424038    5730 down.go:62] releasing boskos project
I0130 17:09:30.433447    5730 boskos.go:83] Boskos heartbeat func received signal to close
Error: exit status 1
+ EXIT_VALUE=1
+ set +o xtrace