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

Test Failures


kubetest2 Up 16m33s

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/k8s-jkns-gce-etcd2-1-6].
..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.
I0203 01:50:17.975456    5744 up.go:44] Cleaning up any leaked resources from previous cluster
I0203 01:50:17.975615    5744 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/d2e91870-a364-11ed-987c-c2f4825a9650/kops toolbox dump --name ha-migration.k8s.local --dir /logs/artifacts --private-key /tmp/kops-ssh2268574484/key --ssh-user prow
I0203 01:50:17.975633    5744 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/d2e91870-a364-11ed-987c-c2f4825a9650/kops toolbox dump --name ha-migration.k8s.local --dir /logs/artifacts --private-key /tmp/kops-ssh2268574484/key --ssh-user prow
Error: Cluster.kops.k8s.io "ha-migration.k8s.local" not found
W0203 01:50:18.281107    5744 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0203 01:50:18.281173    5744 down.go:48] /home/prow/go/src/k8s.io/kops/_rundir/d2e91870-a364-11ed-987c-c2f4825a9650/kops delete cluster --name ha-migration.k8s.local --yes
I0203 01:50:18.281188    5744 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/d2e91870-a364-11ed-987c-c2f4825a9650/kops delete cluster --name ha-migration.k8s.local --yes
Error: error reading cluster configuration: Cluster.kops.k8s.io "ha-migration.k8s.local" not found
I0203 01:50:18.511229    5744 gcs.go:51] gsutil ls -b -p k8s-jkns-gce-etcd2-1-6 gs://k8s-jkns-gce-etcd2-1-6-state-d2
I0203 01:50:18.511271    5744 local.go:42] ⚙️ gsutil ls -b -p k8s-jkns-gce-etcd2-1-6 gs://k8s-jkns-gce-etcd2-1-6-state-d2
I0203 01:50:20.618196    5744 gcs.go:70] gsutil mb -p k8s-jkns-gce-etcd2-1-6 gs://k8s-jkns-gce-etcd2-1-6-state-d2
I0203 01:50:20.618229    5744 local.go:42] ⚙️ gsutil mb -p k8s-jkns-gce-etcd2-1-6 gs://k8s-jkns-gce-etcd2-1-6-state-d2
Creating gs://k8s-jkns-gce-etcd2-1-6-state-d2/...
I0203 01:50:23.629722    5744 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2023/02/03 01:50:23 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
I0203 01:50:23.644326    5744 http.go:37] curl https://ip.jsb.workers.dev
I0203 01:50:23.712874    5744 up.go:167] /home/prow/go/src/k8s.io/kops/_rundir/d2e91870-a364-11ed-987c-c2f4825a9650/kops create cluster --name ha-migration.k8s.local --cloud gce --kubernetes-version v1.23.16 --ssh-public-key /tmp/kops-ssh2268574484/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 35.188.190.85/32 --master-volume-size 48 --node-volume-size 48 --master-size e2-standard-2 --project k8s-jkns-gce-etcd2-1-6
I0203 01:50:23.712922    5744 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/d2e91870-a364-11ed-987c-c2f4825a9650/kops create cluster --name ha-migration.k8s.local --cloud gce --kubernetes-version v1.23.16 --ssh-public-key /tmp/kops-ssh2268574484/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 35.188.190.85/32 --master-volume-size 48 --node-volume-size 48 --master-size e2-standard-2 --project k8s-jkns-gce-etcd2-1-6
I0203 01:50:23.759744    6063 create_cluster.go:882] Using SSH public key: /tmp/kops-ssh2268574484/key.pub
I0203 01:50:24.049424    6063 new_cluster.go:573] VMs will be configured to use specified Service Account: default
I0203 01:50:24.049575    6063 new_cluster.go:1339] Cloud Provider ID: "gce"
... skipping 527 lines ...
I0203 01:50:36.586603    6083 keypair.go:226] Issuing new certificate: "etcd-manager-ca-events"
I0203 01:50:36.589011    6083 keypair.go:226] Issuing new certificate: "etcd-peers-ca-main"
W0203 01:50:36.778314    6083 vfs_keystorereader.go:143] CA private key was not found
I0203 01:50:36.895033    6083 keypair.go:226] Issuing new certificate: "service-account"
I0203 01:50:36.994790    6083 keypair.go:226] Issuing new certificate: "kubernetes-ca"
I0203 01:50:49.064469    6083 executor.go:111] Tasks: 50 done / 91 total; 23 can run
W0203 01:51:02.154175    6083 executor.go:139] error running task "ForwardingRule/api-ha-migration-k8s-local" (9m46s remaining to succeed): error creating ForwardingRule "api-ha-migration-k8s-local": googleapi: Error 400: The resource 'projects/k8s-jkns-gce-etcd2-1-6/regions/us-central1/targetPools/api-ha-migration-k8s-local' is not ready, resourceNotReady
I0203 01:51:02.154481    6083 executor.go:111] Tasks: 72 done / 91 total; 13 can run
I0203 01:51:09.007450    6083 executor.go:111] Tasks: 85 done / 91 total; 6 can run
I0203 01:51:25.847323    6083 executor.go:111] Tasks: 91 done / 91 total; 0 can run
I0203 01:51:26.325786    6083 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.

I0203 01:51:36.702088    5744 up.go:251] /home/prow/go/src/k8s.io/kops/_rundir/d2e91870-a364-11ed-987c-c2f4825a9650/kops validate cluster --name ha-migration.k8s.local --count 10 --wait 15m0s
I0203 01:51:36.702146    5744 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/d2e91870-a364-11ed-987c-c2f4825a9650/kops validate cluster --name ha-migration.k8s.local --count 10 --wait 15m0s
Validating cluster ha-migration.k8s.local

W0203 01:52:07.195566    6104 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.136.6.71/api/v1/nodes": dial tcp 34.136.6.71:443: i/o timeout
W0203 01:52:47.197153    6104 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.136.6.71/api/v1/nodes": dial tcp 34.136.6.71:443: i/o timeout
W0203 01:52:57.201012    6104 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.136.6.71/api/v1/nodes": dial tcp 34.136.6.71:443: connect: connection refused
W0203 01:53:10.234312    6104 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.136.6.71/api/v1/nodes": dial tcp 34.136.6.71:443: connect: connection refused
W0203 01:53:20.240165    6104 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.136.6.71/api/v1/nodes": dial tcp 34.136.6.71:443: connect: connection refused
W0203 01:53:30.243130    6104 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.136.6.71/api/v1/nodes": dial tcp 34.136.6.71:443: connect: connection refused
W0203 01:53:40.247090    6104 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.136.6.71/api/v1/nodes": dial tcp 34.136.6.71:443: connect: connection refused
W0203 01:53:50.252692    6104 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.136.6.71/api/v1/nodes": dial tcp 34.136.6.71:443: connect: connection refused
W0203 01:54:10.260649    6104 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.136.6.71/api/v1/nodes": net/http: TLS handshake timeout
W0203 01:54:30.349512    6104 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.136.6.71/api/v1/nodes": dial tcp 34.136.6.71:443: connect: connection refused - error from a previous attempt: read tcp 10.60.135.177:50750->34.136.6.71:443: read: connection reset by peer
W0203 01:54:40.357527    6104 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.136.6.71/api/v1/nodes": dial tcp 34.136.6.71:443: connect: connection refused
W0203 01:55:00.367128    6104 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.136.6.71/api/v1/nodes": net/http: TLS handshake timeout
I0203 01:55:08.166372    5744 boskos.go:86] Sending heartbeat to Boskos
W0203 01:55:10.372663    6104 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.136.6.71/api/v1/nodes": dial tcp 34.136.6.71:443: connect: connection refused
W0203 01:55:20.378254    6104 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.136.6.71/api/v1/nodes": dial tcp 34.136.6.71:443: connect: connection refused
W0203 01:55:30.382585    6104 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.136.6.71/api/v1/nodes": dial tcp 34.136.6.71:443: connect: connection refused
W0203 01:55:50.388681    6104 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.136.6.71/api/v1/nodes": net/http: TLS handshake timeout
W0203 01:56:00.392130    6104 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.136.6.71/api/v1/nodes": dial tcp 34.136.6.71:443: connect: connection refused
W0203 01:56:10.396541    6104 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.136.6.71/api/v1/nodes": dial tcp 34.136.6.71:443: connect: connection refused
W0203 01:56:30.404973    6104 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.136.6.71/api/v1/nodes": net/http: TLS handshake timeout
I0203 01:56:40.955926    6104 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 12 lines ...
Machine	https://www.googleapis.com/compute/v1/projects/k8s-jkns-gce-etcd2-1-6/zones/us-central1-a/instances/nodes-us-central1-a-40nf	machine "https://www.googleapis.com/compute/v1/projects/k8s-jkns-gce-etcd2-1-6/zones/us-central1-a/instances/nodes-us-central1-a-40nf" has not yet joined cluster
Node	control-plane-us-central1-a-l26w												node "control-plane-us-central1-a-l26w" of role "control-plane" is not ready
Node	control-plane-us-central1-b-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/kube-controller-manager-control-plane-us-central1-a-l26w								system-cluster-critical pod "kube-controller-manager-control-plane-us-central1-a-l26w" is not ready (kube-controller-manager)

Validation Failed
W0203 01:56:41.933581    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 01:56:52.387716    6104 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 14 lines ...
Node	control-plane-us-central1-a-l26w												node "control-plane-us-central1-a-l26w" of role "control-plane" is not ready
Node	control-plane-us-central1-b-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/kube-controller-manager-control-plane-us-central1-a-l26w								system-cluster-critical pod "kube-controller-manager-control-plane-us-central1-a-l26w" is not ready (kube-controller-manager)
Pod	kube-system/kube-controller-manager-control-plane-us-central1-c-kq04								system-cluster-critical pod "kube-controller-manager-control-plane-us-central1-c-kq04" is pending

Validation Failed
W0203 01:56:53.290266    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 01:57:03.702100    6104 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/cilium-xzfx8													system-node-critical pod "cilium-xzfx8" is pending
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending
Pod	kube-system/kube-controller-manager-control-plane-us-central1-c-kq04								system-cluster-critical pod "kube-controller-manager-control-plane-us-central1-c-kq04" is not ready (kube-controller-manager)

Validation Failed
W0203 01:57:04.590776    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 01:57:15.020667    6104 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-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending
Pod	kube-system/kube-apiserver-control-plane-us-central1-a-l26w									system-cluster-critical pod "kube-apiserver-control-plane-us-central1-a-l26w" is pending
Pod	kube-system/kube-controller-manager-control-plane-us-central1-c-kq04								system-cluster-critical pod "kube-controller-manager-control-plane-us-central1-c-kq04" is not ready (kube-controller-manager)

Validation Failed
W0203 01:57:16.007731    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 01:57:26.403065    6104 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-xzfx8													system-node-critical pod "cilium-xzfx8" is not ready (cilium-agent)
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending
Pod	kube-system/kube-apiserver-control-plane-us-central1-c-kq04									system-cluster-critical pod "kube-apiserver-control-plane-us-central1-c-kq04" is pending

Validation Failed
W0203 01:57:27.319531    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 01:57:37.738707    6104 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-xr7w6													system-node-critical pod "cilium-xr7w6" is not ready (cilium-agent)
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending
Pod	kube-system/kube-scheduler-control-plane-us-central1-b-jm08									system-cluster-critical pod "kube-scheduler-control-plane-us-central1-b-jm08" is pending

Validation Failed
W0203 01:57:38.573871    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 01:57:49.073988    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 01:57:50.004262    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 01:58:00.441466    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 01:58:01.392949    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 01:58:11.747694    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 01:58:12.574314    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 01:58:22.989027    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 01:58:23.897694    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 01:58:34.330415    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 01:58:35.181016    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 01:58:45.607945    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 01:58:46.556417    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 01:58:56.947205    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 01:58:57.794969    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 01:59:08.227366    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 01:59:09.136716    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 01:59:19.548514    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 01:59:20.381251    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 01:59:30.779874    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 01:59:31.704984    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 01:59:42.089514    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 01:59:42.955427    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 01:59:53.386290    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 01:59:54.328523    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 02:00:04.774086    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 02:00:05.662403    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 02:00:08.178484    5744 boskos.go:86] Sending heartbeat to Boskos
I0203 02:00:16.085961    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 02:00:16.917152    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 02:00:27.392007    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 02:00:28.311783    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 02:00:38.777499    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 02:00:39.669140    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 02:00:50.062903    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 02:00:51.037312    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 02:01:01.459456    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 02:01:02.330670    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 02:01:12.710781    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 02:01:13.567878    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 02:01:23.988324    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 02:01:24.914526    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 02:01:35.394017    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 02:01:36.267002    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 02:01:46.784137    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 02:01:47.745862    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 02:01:58.258127    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 02:01:59.175110    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 02:02:09.516321    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 02:02:10.406847    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 02:02:20.787558    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 02:02:21.681245    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 02:02:32.168372    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 02:02:33.050069    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 02:02:43.427839    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 02:02:44.273529    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 02:02:54.663486    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 02:02:55.523784    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 02:03:05.965814    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 02:03:06.872416    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 02:03:17.278182    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 02:03:18.171989    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 02:03:28.601208    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 02:03:29.497816    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 02:03:39.886171    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 02:03:40.794388    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 02:03:51.209533    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 02:03:52.053586    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 02:04:02.507615    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 02:04:03.397920    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 02:04:13.782455    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 02:04:14.668087    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 02:04:25.087973    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 02:04:25.972717    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 02:04:36.483677    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 02:04:37.302695    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 02:04:47.738432    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 02:04:48.648446    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 02:04:59.084749    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 02:05:00.071877    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 02:05:08.191259    5744 boskos.go:86] Sending heartbeat to Boskos
I0203 02:05:10.519088    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 02:05:11.385597    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 02:05:21.846244    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 02:05:22.788625    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 02:05:33.228335    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 02:05:34.069989    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 02:05:44.551115    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 02:05:45.460484    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 02:05:55.851987    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 02:05:56.720690    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 02:06:07.235960    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 02:06:08.199864    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 02:06:18.635322    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 02:06:19.457978    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
I0203 02:06:29.824327    6104 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-jm08												node "control-plane-us-central1-b-jm08" of role "control-plane" is not ready
Node	control-plane-us-central1-c-kq04												node "control-plane-us-central1-c-kq04" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-bldjm												system-cluster-critical pod "coredns-5d479c4f64-bldjm" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-c7wqb											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-c7wqb" is pending
Pod	kube-system/dns-controller-6f69f47785-rzs4j											system-cluster-critical pod "dns-controller-6f69f47785-rzs4j" is pending

Validation Failed
W0203 02:06:30.700498    6104 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: validation failed: wait time exceeded during validation
I0203 02:06:40.707602    5744 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/d2e91870-a364-11ed-987c-c2f4825a9650/kops toolbox dump --name ha-migration.k8s.local --dir /logs/artifacts --private-key /tmp/kops-ssh2268574484/key --ssh-user prow
I0203 02:06:40.707686    5744 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/d2e91870-a364-11ed-987c-c2f4825a9650/kops toolbox dump --name ha-migration.k8s.local --dir /logs/artifacts --private-key /tmp/kops-ssh2268574484/key --ssh-user prow
I0203 02:06:41.196440    6114 gce.go:99] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
2023/02/03 02:06:46 Dumping node control-plane-us-central1-a-l26w
2023/02/03 02:06:49 error dumping node control-plane-us-central1-a-l26w: 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/02/03 02:06:49 error dumping node control-plane-us-central1-a-l26w: 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/02/03 02:06:49 Dumping node control-plane-us-central1-b-jm08
2023/02/03 02:06:52 error dumping node control-plane-us-central1-b-jm08: 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/02/03 02:06:52 error dumping node control-plane-us-central1-b-jm08: 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/02/03 02:06:52 Dumping node control-plane-us-central1-c-kq04
2023/02/03 02:06:56 error dumping node control-plane-us-central1-c-kq04: 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/02/03 02:06:56 error dumping node control-plane-us-central1-c-kq04: 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/02/03 02:06:56 dumping node not registered in kubernetes: 35.193.43.235
2023/02/03 02:06:56 Dumping node 35.193.43.235
I0203 02:06:57.836946    5744 dumplogs.go:79] /home/prow/go/src/k8s.io/kops/_rundir/d2e91870-a364-11ed-987c-c2f4825a9650/kops get cluster --name ha-migration.k8s.local -o yaml
I0203 02:06:57.836984    5744 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/d2e91870-a364-11ed-987c-c2f4825a9650/kops get cluster --name ha-migration.k8s.local -o yaml
I0203 02:06:57.990273    5744 dumplogs.go:79] /home/prow/go/src/k8s.io/kops/_rundir/d2e91870-a364-11ed-987c-c2f4825a9650/kops get instancegroups --name ha-migration.k8s.local -o yaml
I0203 02:06:57.990310    5744 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/d2e91870-a364-11ed-987c-c2f4825a9650/kops get instancegroups --name ha-migration.k8s.local -o yaml
... skipping 166 lines ...
Deleted cluster: "ha-migration.k8s.local"
I0203 02:09:10.415502    5744 gcs.go:88] gsutil -u k8s-jkns-gce-etcd2-1-6 rm -r gs://k8s-jkns-gce-etcd2-1-6-state-d2
I0203 02:09:10.415553    5744 local.go:42] ⚙️ gsutil -u k8s-jkns-gce-etcd2-1-6 rm -r gs://k8s-jkns-gce-etcd2-1-6-state-d2
Removing gs://k8s-jkns-gce-etcd2-1-6-state-d2/...
I0203 02:09:13.137415    5744 down.go:62] releasing boskos project
I0203 02:09:13.146925    5744 boskos.go:83] Boskos heartbeat func received signal to close
Error: exit status 1
+ EXIT_VALUE=1
+ set +o xtrace