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

Test Failures


kubetest2 Up 16m29s

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-gci-gce-reboot-1-5].
..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.
I0201 13:51:45.753092    5900 up.go:44] Cleaning up any leaked resources from previous cluster
I0201 13:51:45.753386    5900 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/21ede299-a237-11ed-9efc-5e7820dba16b/kops toolbox dump --name ha-migration.k8s.local --dir /logs/artifacts --private-key /tmp/kops-ssh2302611607/key --ssh-user prow
I0201 13:51:45.753431    5900 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/21ede299-a237-11ed-9efc-5e7820dba16b/kops toolbox dump --name ha-migration.k8s.local --dir /logs/artifacts --private-key /tmp/kops-ssh2302611607/key --ssh-user prow
Error: Cluster.kops.k8s.io "ha-migration.k8s.local" not found
W0201 13:51:46.072951    5900 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0201 13:51:46.073040    5900 down.go:48] /home/prow/go/src/k8s.io/kops/_rundir/21ede299-a237-11ed-9efc-5e7820dba16b/kops delete cluster --name ha-migration.k8s.local --yes
I0201 13:51:46.073052    5900 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/21ede299-a237-11ed-9efc-5e7820dba16b/kops delete cluster --name ha-migration.k8s.local --yes
Error: error reading cluster configuration: Cluster.kops.k8s.io "ha-migration.k8s.local" not found
I0201 13:51:46.411847    5900 gcs.go:51] gsutil ls -b -p k8s-gci-gce-reboot-1-5 gs://k8s-gci-gce-reboot-1-5-state-21
I0201 13:51:46.411955    5900 local.go:42] ⚙️ gsutil ls -b -p k8s-gci-gce-reboot-1-5 gs://k8s-gci-gce-reboot-1-5-state-21
I0201 13:51:50.219397    5900 gcs.go:70] gsutil mb -p k8s-gci-gce-reboot-1-5 gs://k8s-gci-gce-reboot-1-5-state-21
I0201 13:51:50.219451    5900 local.go:42] ⚙️ gsutil mb -p k8s-gci-gce-reboot-1-5 gs://k8s-gci-gce-reboot-1-5-state-21
Creating gs://k8s-gci-gce-reboot-1-5-state-21/...
I0201 13:51:54.492472    5900 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2023/02/01 13:51:54 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
I0201 13:51:54.510393    5900 http.go:37] curl https://ip.jsb.workers.dev
I0201 13:51:54.616572    5900 up.go:167] /home/prow/go/src/k8s.io/kops/_rundir/21ede299-a237-11ed-9efc-5e7820dba16b/kops create cluster --name ha-migration.k8s.local --cloud gce --kubernetes-version v1.23.16 --ssh-public-key /tmp/kops-ssh2302611607/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.222.114.179/32 --master-volume-size 48 --node-volume-size 48 --master-size e2-standard-2 --project k8s-gci-gce-reboot-1-5
I0201 13:51:54.616612    5900 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/21ede299-a237-11ed-9efc-5e7820dba16b/kops create cluster --name ha-migration.k8s.local --cloud gce --kubernetes-version v1.23.16 --ssh-public-key /tmp/kops-ssh2302611607/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.222.114.179/32 --master-volume-size 48 --node-volume-size 48 --master-size e2-standard-2 --project k8s-gci-gce-reboot-1-5
I0201 13:51:54.730066    6221 create_cluster.go:882] Using SSH public key: /tmp/kops-ssh2302611607/key.pub
I0201 13:51:55.034546    6221 new_cluster.go:573] VMs will be configured to use specified Service Account: default
I0201 13:51:55.034700    6221 new_cluster.go:1339] Cloud Provider ID: "gce"
... skipping 527 lines ...
I0201 13:52:08.987069    6243 keypair.go:226] Issuing new certificate: "etcd-manager-ca-events"
I0201 13:52:08.987537    6243 keypair.go:226] Issuing new certificate: "etcd-manager-ca-main"
W0201 13:52:09.181308    6243 vfs_keystorereader.go:143] CA private key was not found
I0201 13:52:09.382686    6243 keypair.go:226] Issuing new certificate: "service-account"
I0201 13:52:09.383482    6243 keypair.go:226] Issuing new certificate: "kubernetes-ca"
I0201 13:52:21.597696    6243 executor.go:111] Tasks: 50 done / 91 total; 23 can run
W0201 13:52:31.356445    6243 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/k8s-gci-gce-reboot-1-5/regions/us-central1/targetPools/api-ha-migration-k8s-local' is not ready, resourceNotReady
I0201 13:52:31.356807    6243 executor.go:111] Tasks: 72 done / 91 total; 13 can run
I0201 13:52:38.193662    6243 executor.go:111] Tasks: 85 done / 91 total; 6 can run
I0201 13:52:51.193894    6243 executor.go:111] Tasks: 91 done / 91 total; 0 can run
I0201 13:52:51.364900    6243 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.

I0201 13:53:01.873750    5900 up.go:251] /home/prow/go/src/k8s.io/kops/_rundir/21ede299-a237-11ed-9efc-5e7820dba16b/kops validate cluster --name ha-migration.k8s.local --count 10 --wait 15m0s
I0201 13:53:01.873819    5900 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/21ede299-a237-11ed-9efc-5e7820dba16b/kops validate cluster --name ha-migration.k8s.local --count 10 --wait 15m0s
Validating cluster ha-migration.k8s.local

W0201 13:53:32.779765    6260 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.27.144.252/api/v1/nodes": dial tcp 34.27.144.252:443: i/o timeout
W0201 13:53:58.263425    6260 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.27.144.252/api/v1/nodes": dial tcp 34.27.144.252:443: connect: connection refused
W0201 13:54:08.270201    6260 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.27.144.252/api/v1/nodes": dial tcp 34.27.144.252:443: connect: connection refused
W0201 13:54:18.273989    6260 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.27.144.252/api/v1/nodes": dial tcp 34.27.144.252:443: connect: connection refused
W0201 13:54:28.280628    6260 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.27.144.252/api/v1/nodes": dial tcp 34.27.144.252:443: connect: connection refused
W0201 13:54:38.291033    6260 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.27.144.252/api/v1/nodes": dial tcp 34.27.144.252:443: connect: connection refused
W0201 13:54:48.299240    6260 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.27.144.252/api/v1/nodes": dial tcp 34.27.144.252:443: connect: connection refused
W0201 13:54:58.307509    6260 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.27.144.252/api/v1/nodes": dial tcp 34.27.144.252:443: connect: connection refused
W0201 13:55:08.311605    6260 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.27.144.252/api/v1/nodes": dial tcp 34.27.144.252:443: connect: connection refused
W0201 13:55:18.319757    6260 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.27.144.252/api/v1/nodes": dial tcp 34.27.144.252:443: connect: connection refused
W0201 13:55:28.327096    6260 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.27.144.252/api/v1/nodes": dial tcp 34.27.144.252:443: connect: connection refused
W0201 13:55:48.340719    6260 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.27.144.252/api/v1/nodes": net/http: TLS handshake timeout
W0201 13:56:13.323162    6260 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.27.144.252/api/v1/nodes": net/http: TLS handshake timeout - error from a previous attempt: read tcp 10.60.40.195:48430->34.27.144.252:443: read: connection reset by peer
W0201 13:56:23.332619    6260 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.27.144.252/api/v1/nodes": dial tcp 34.27.144.252:443: connect: connection refused
W0201 13:56:33.335565    6260 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.27.144.252/api/v1/nodes": dial tcp 34.27.144.252:443: connect: connection refused
I0201 13:56:36.646562    5900 boskos.go:86] Sending heartbeat to Boskos
W0201 13:56:53.340005    6260 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.27.144.252/api/v1/nodes": net/http: TLS handshake timeout
W0201 13:57:06.916122    6260 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.27.144.252/api/v1/nodes": dial tcp 34.27.144.252:443: connect: connection refused - error from a previous attempt: read tcp 10.60.40.195:40366->34.27.144.252:443: read: connection reset by peer
W0201 13:57:16.920720    6260 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.27.144.252/api/v1/nodes": dial tcp 34.27.144.252:443: connect: connection refused
W0201 13:57:36.928667    6260 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.27.144.252/api/v1/nodes": net/http: TLS handshake timeout
W0201 13:57:56.936630    6260 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.27.144.252/api/v1/nodes": net/http: TLS handshake timeout
I0201 13:58:07.327326    6260 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 11 lines ...
Machine	https://www.googleapis.com/compute/v1/projects/k8s-gci-gce-reboot-1-5/zones/us-central1-a/instances/nodes-us-central1-a-q6fm		machine "https://www.googleapis.com/compute/v1/projects/k8s-gci-gce-reboot-1-5/zones/us-central1-a/instances/nodes-us-central1-a-q6fm" has not yet joined cluster
Machine	https://www.googleapis.com/compute/v1/projects/k8s-gci-gce-reboot-1-5/zones/us-central1-b/instances/control-plane-us-central1-b-5046	machine "https://www.googleapis.com/compute/v1/projects/k8s-gci-gce-reboot-1-5/zones/us-central1-b/instances/control-plane-us-central1-b-5046" has not yet joined cluster
Node	control-plane-us-central1-c-mxg3													node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/kube-controller-manager-control-plane-us-central1-c-mxg3									system-cluster-critical pod "kube-controller-manager-control-plane-us-central1-c-mxg3" is pending
Pod	kube-system/kube-scheduler-control-plane-us-central1-c-mxg3										system-cluster-critical pod "kube-scheduler-control-plane-us-central1-c-mxg3" is pending

Validation Failed
W0201 13:58:08.312011    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 13:58:18.736771    6260 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 12 lines ...
Machine	https://www.googleapis.com/compute/v1/projects/k8s-gci-gce-reboot-1-5/zones/us-central1-a/instances/nodes-us-central1-a-q6fm		machine "https://www.googleapis.com/compute/v1/projects/k8s-gci-gce-reboot-1-5/zones/us-central1-a/instances/nodes-us-central1-a-q6fm" has not yet joined cluster
Machine	https://www.googleapis.com/compute/v1/projects/k8s-gci-gce-reboot-1-5/zones/us-central1-b/instances/control-plane-us-central1-b-5046	machine "https://www.googleapis.com/compute/v1/projects/k8s-gci-gce-reboot-1-5/zones/us-central1-b/instances/control-plane-us-central1-b-5046" has not yet joined cluster
Node	control-plane-us-central1-c-mxg3													node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/etcd-manager-events-control-plane-us-central1-c-mxg3									system-cluster-critical pod "etcd-manager-events-control-plane-us-central1-c-mxg3" is pending
Pod	kube-system/kube-controller-manager-control-plane-us-central1-c-mxg3									system-cluster-critical pod "kube-controller-manager-control-plane-us-central1-c-mxg3" is not ready (kube-controller-manager)

Validation Failed
W0201 13:58:19.574422    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 13:58:29.994176    6260 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 13 lines ...
Machine	https://www.googleapis.com/compute/v1/projects/k8s-gci-gce-reboot-1-5/zones/us-central1-b/instances/control-plane-us-central1-b-5046	machine "https://www.googleapis.com/compute/v1/projects/k8s-gci-gce-reboot-1-5/zones/us-central1-b/instances/control-plane-us-central1-b-5046" has not yet joined cluster
Node	control-plane-us-central1-a-4lp9													node "control-plane-us-central1-a-4lp9" of role "control-plane" is not ready
Node	control-plane-us-central1-c-mxg3													node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/etcd-manager-main-control-plane-us-central1-c-mxg3										system-cluster-critical pod "etcd-manager-main-control-plane-us-central1-c-mxg3" is pending
Pod	kube-system/kube-controller-manager-control-plane-us-central1-c-mxg3									system-cluster-critical pod "kube-controller-manager-control-plane-us-central1-c-mxg3" is not ready (kube-controller-manager)

Validation Failed
W0201 13:58:30.807948    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 13:58:41.178210    6260 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 13 lines ...
Machine	https://www.googleapis.com/compute/v1/projects/k8s-gci-gce-reboot-1-5/zones/us-central1-a/instances/nodes-us-central1-a-q6fm	machine "https://www.googleapis.com/compute/v1/projects/k8s-gci-gce-reboot-1-5/zones/us-central1-a/instances/nodes-us-central1-a-q6fm" has not yet joined cluster
Node	control-plane-us-central1-a-4lp9												node "control-plane-us-central1-a-4lp9" of role "control-plane" is not ready
Node	control-plane-us-central1-b-5046												node "control-plane-us-central1-b-5046" of role "control-plane" is not ready
Node	control-plane-us-central1-c-mxg3												node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/kube-controller-manager-control-plane-us-central1-c-mxg3								system-cluster-critical pod "kube-controller-manager-control-plane-us-central1-c-mxg3" is not ready (kube-controller-manager)

Validation Failed
W0201 13:58:42.002789    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 13:58:52.257189    6260 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-4lp9												node "control-plane-us-central1-a-4lp9" of role "control-plane" is not ready
Node	control-plane-us-central1-b-5046												node "control-plane-us-central1-b-5046" of role "control-plane" is not ready
Node	control-plane-us-central1-c-mxg3												node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/kube-controller-manager-control-plane-us-central1-b-5046								system-cluster-critical pod "kube-controller-manager-control-plane-us-central1-b-5046" is pending
Pod	kube-system/kube-controller-manager-control-plane-us-central1-c-mxg3								system-cluster-critical pod "kube-controller-manager-control-plane-us-central1-c-mxg3" is not ready (kube-controller-manager)

Validation Failed
W0201 13:58:53.065206    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 13:59:03.392627    6260 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-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending
Pod	kube-system/kube-controller-manager-control-plane-us-central1-b-5046								system-cluster-critical pod "kube-controller-manager-control-plane-us-central1-b-5046" is not ready (kube-controller-manager)
Pod	kube-system/kube-scheduler-control-plane-us-central1-a-4lp9									system-cluster-critical pod "kube-scheduler-control-plane-us-central1-a-4lp9" is pending

Validation Failed
W0201 13:59:04.248351    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 13:59:14.600939    6260 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-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending
Pod	kube-system/etcd-manager-events-control-plane-us-central1-b-5046								system-cluster-critical pod "etcd-manager-events-control-plane-us-central1-b-5046" is pending
Pod	kube-system/kube-controller-manager-control-plane-us-central1-b-5046								system-cluster-critical pod "kube-controller-manager-control-plane-us-central1-b-5046" is not ready (kube-controller-manager)

Validation Failed
W0201 13:59:15.488783    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 13:59:25.818279    6260 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-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending
Pod	kube-system/etcd-manager-main-control-plane-us-central1-b-5046									system-cluster-critical pod "etcd-manager-main-control-plane-us-central1-b-5046" is pending
Pod	kube-system/kube-controller-manager-control-plane-us-central1-b-5046								system-cluster-critical pod "kube-controller-manager-control-plane-us-central1-b-5046" is not ready (kube-controller-manager)

Validation Failed
W0201 13:59:26.736864    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 13:59:37.049242    6260 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-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending
Pod	kube-system/etcd-manager-main-control-plane-us-central1-a-4lp9									system-cluster-critical pod "etcd-manager-main-control-plane-us-central1-a-4lp9" is pending
Pod	kube-system/kube-apiserver-control-plane-us-central1-b-5046									system-cluster-critical pod "kube-apiserver-control-plane-us-central1-b-5046" is pending
Pod	kube-system/kube-controller-manager-control-plane-us-central1-b-5046								system-cluster-critical pod "kube-controller-manager-control-plane-us-central1-b-5046" is not ready (kube-controller-manager)

Validation Failed
W0201 13:59:37.878639    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 13:59:48.229666    6260 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-mxg3												node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending
Pod	kube-system/kube-controller-manager-control-plane-us-central1-b-5046								system-cluster-critical pod "kube-controller-manager-control-plane-us-central1-b-5046" is not ready (kube-controller-manager)

Validation Failed
W0201 13:59:49.148792    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 13:59:59.685624    6260 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-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending
Pod	kube-system/kube-controller-manager-control-plane-us-central1-a-4lp9								system-cluster-critical pod "kube-controller-manager-control-plane-us-central1-a-4lp9" is pending
Pod	kube-system/kube-controller-manager-control-plane-us-central1-b-5046								system-cluster-critical pod "kube-controller-manager-control-plane-us-central1-b-5046" is not ready (kube-controller-manager)

Validation Failed
W0201 14:00:00.694737    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 14:00:11.027521    6260 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-mxg3												node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending
Pod	kube-system/kube-controller-manager-control-plane-us-central1-b-5046								system-cluster-critical pod "kube-controller-manager-control-plane-us-central1-b-5046" is not ready (kube-controller-manager)

Validation Failed
W0201 14:00:11.879403    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 14:00:22.197582    6260 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-mxg3												node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending
Pod	kube-system/kube-controller-manager-control-plane-us-central1-b-5046								system-cluster-critical pod "kube-controller-manager-control-plane-us-central1-b-5046" is not ready (kube-controller-manager)

Validation Failed
W0201 14:00:23.086976    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 14:00:33.489569    6260 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-mxg3												node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending
Pod	kube-system/kube-controller-manager-control-plane-us-central1-b-5046								system-cluster-critical pod "kube-controller-manager-control-plane-us-central1-b-5046" is not ready (kube-controller-manager)

Validation Failed
W0201 14:00:34.424721    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 14:00:44.754718    6260 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-mxg3												node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending
Pod	kube-system/kube-controller-manager-control-plane-us-central1-b-5046								system-cluster-critical pod "kube-controller-manager-control-plane-us-central1-b-5046" is not ready (kube-controller-manager)

Validation Failed
W0201 14:00:45.661307    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 14:00:56.087157    6260 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-mxg3												node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending
Pod	kube-system/kube-controller-manager-control-plane-us-central1-b-5046								system-cluster-critical pod "kube-controller-manager-control-plane-us-central1-b-5046" is not ready (kube-controller-manager)

Validation Failed
W0201 14:00:56.961452    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 14:01:07.344913    6260 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-mxg3												node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending
Pod	kube-system/kube-controller-manager-control-plane-us-central1-b-5046								system-cluster-critical pod "kube-controller-manager-control-plane-us-central1-b-5046" is not ready (kube-controller-manager)

Validation Failed
W0201 14:01:08.133591    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 14:01:18.544368    6260 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-mxg3												node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending
Pod	kube-system/kube-controller-manager-control-plane-us-central1-b-5046								system-cluster-critical pod "kube-controller-manager-control-plane-us-central1-b-5046" is not ready (kube-controller-manager)

Validation Failed
W0201 14:01:19.428883    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 14:01:29.833009    6260 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-5046												node "control-plane-us-central1-b-5046" of role "control-plane" is not ready
Node	control-plane-us-central1-c-mxg3												node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending

Validation Failed
W0201 14:01:30.682356    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 14:01:36.657430    5900 boskos.go:86] Sending heartbeat to Boskos
I0201 14:01:41.060512    6260 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-5046												node "control-plane-us-central1-b-5046" of role "control-plane" is not ready
Node	control-plane-us-central1-c-mxg3												node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending

Validation Failed
W0201 14:01:41.944049    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 14:01:52.322610    6260 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-5046												node "control-plane-us-central1-b-5046" of role "control-plane" is not ready
Node	control-plane-us-central1-c-mxg3												node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending

Validation Failed
W0201 14:01:53.202872    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 14:02:03.525767    6260 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-5046												node "control-plane-us-central1-b-5046" of role "control-plane" is not ready
Node	control-plane-us-central1-c-mxg3												node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending

Validation Failed
W0201 14:02:04.452053    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 14:02:14.803324    6260 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-5046												node "control-plane-us-central1-b-5046" of role "control-plane" is not ready
Node	control-plane-us-central1-c-mxg3												node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending

Validation Failed
W0201 14:02:15.599029    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 14:02:25.887424    6260 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-5046												node "control-plane-us-central1-b-5046" of role "control-plane" is not ready
Node	control-plane-us-central1-c-mxg3												node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending

Validation Failed
W0201 14:02:26.738470    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 14:02:37.104487    6260 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-5046												node "control-plane-us-central1-b-5046" of role "control-plane" is not ready
Node	control-plane-us-central1-c-mxg3												node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending

Validation Failed
W0201 14:02:38.010188    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 14:02:48.361462    6260 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-5046												node "control-plane-us-central1-b-5046" of role "control-plane" is not ready
Node	control-plane-us-central1-c-mxg3												node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending

Validation Failed
W0201 14:02:49.218284    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 14:02:59.559928    6260 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-5046												node "control-plane-us-central1-b-5046" of role "control-plane" is not ready
Node	control-plane-us-central1-c-mxg3												node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending

Validation Failed
W0201 14:03:00.420832    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 14:03:10.758906    6260 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-5046												node "control-plane-us-central1-b-5046" of role "control-plane" is not ready
Node	control-plane-us-central1-c-mxg3												node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending

Validation Failed
W0201 14:03:11.621367    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 14:03:22.043215    6260 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-5046												node "control-plane-us-central1-b-5046" of role "control-plane" is not ready
Node	control-plane-us-central1-c-mxg3												node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending

Validation Failed
W0201 14:03:22.910360    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 14:03:33.268724    6260 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-5046												node "control-plane-us-central1-b-5046" of role "control-plane" is not ready
Node	control-plane-us-central1-c-mxg3												node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending

Validation Failed
W0201 14:03:34.186688    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 14:03:44.550520    6260 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-5046												node "control-plane-us-central1-b-5046" of role "control-plane" is not ready
Node	control-plane-us-central1-c-mxg3												node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending

Validation Failed
W0201 14:03:45.408619    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 14:03:55.704120    6260 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-5046												node "control-plane-us-central1-b-5046" of role "control-plane" is not ready
Node	control-plane-us-central1-c-mxg3												node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending

Validation Failed
W0201 14:03:56.524728    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 14:04:06.913422    6260 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-5046												node "control-plane-us-central1-b-5046" of role "control-plane" is not ready
Node	control-plane-us-central1-c-mxg3												node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending

Validation Failed
W0201 14:04:07.749165    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 14:04:18.127460    6260 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-5046												node "control-plane-us-central1-b-5046" of role "control-plane" is not ready
Node	control-plane-us-central1-c-mxg3												node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending

Validation Failed
W0201 14:04:18.977556    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 14:04:29.347156    6260 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-5046												node "control-plane-us-central1-b-5046" of role "control-plane" is not ready
Node	control-plane-us-central1-c-mxg3												node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending

Validation Failed
W0201 14:04:30.200025    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 14:04:40.623536    6260 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-5046												node "control-plane-us-central1-b-5046" of role "control-plane" is not ready
Node	control-plane-us-central1-c-mxg3												node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending

Validation Failed
W0201 14:04:41.457329    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 14:04:51.840900    6260 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-5046												node "control-plane-us-central1-b-5046" of role "control-plane" is not ready
Node	control-plane-us-central1-c-mxg3												node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending

Validation Failed
W0201 14:04:52.689887    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 14:05:03.052949    6260 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-5046												node "control-plane-us-central1-b-5046" of role "control-plane" is not ready
Node	control-plane-us-central1-c-mxg3												node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending

Validation Failed
W0201 14:05:03.927037    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 14:05:14.235685    6260 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-5046												node "control-plane-us-central1-b-5046" of role "control-plane" is not ready
Node	control-plane-us-central1-c-mxg3												node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending

Validation Failed
W0201 14:05:15.086777    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 14:05:25.466450    6260 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-5046												node "control-plane-us-central1-b-5046" of role "control-plane" is not ready
Node	control-plane-us-central1-c-mxg3												node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending

Validation Failed
W0201 14:05:26.259725    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 14:05:36.721835    6260 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-5046												node "control-plane-us-central1-b-5046" of role "control-plane" is not ready
Node	control-plane-us-central1-c-mxg3												node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending

Validation Failed
W0201 14:05:37.545967    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 14:05:47.926867    6260 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-5046												node "control-plane-us-central1-b-5046" of role "control-plane" is not ready
Node	control-plane-us-central1-c-mxg3												node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending

Validation Failed
W0201 14:05:48.704229    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 14:05:59.035866    6260 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-5046												node "control-plane-us-central1-b-5046" of role "control-plane" is not ready
Node	control-plane-us-central1-c-mxg3												node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending

Validation Failed
W0201 14:05:59.922385    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 14:06:10.214240    6260 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-5046												node "control-plane-us-central1-b-5046" of role "control-plane" is not ready
Node	control-plane-us-central1-c-mxg3												node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending

Validation Failed
W0201 14:06:11.091574    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 14:06:21.477930    6260 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-5046												node "control-plane-us-central1-b-5046" of role "control-plane" is not ready
Node	control-plane-us-central1-c-mxg3												node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending

Validation Failed
W0201 14:06:22.243495    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 14:06:32.574133    6260 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-5046												node "control-plane-us-central1-b-5046" of role "control-plane" is not ready
Node	control-plane-us-central1-c-mxg3												node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending

Validation Failed
W0201 14:06:33.395269    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 14:06:36.667792    5900 boskos.go:86] Sending heartbeat to Boskos
I0201 14:06:43.695361    6260 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-5046												node "control-plane-us-central1-b-5046" of role "control-plane" is not ready
Node	control-plane-us-central1-c-mxg3												node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending

Validation Failed
W0201 14:06:44.481495    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 14:06:54.814463    6260 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-5046												node "control-plane-us-central1-b-5046" of role "control-plane" is not ready
Node	control-plane-us-central1-c-mxg3												node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending

Validation Failed
W0201 14:06:55.648855    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 14:07:06.008964    6260 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-5046												node "control-plane-us-central1-b-5046" of role "control-plane" is not ready
Node	control-plane-us-central1-c-mxg3												node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending

Validation Failed
W0201 14:07:06.870440    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 14:07:17.211824    6260 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-5046												node "control-plane-us-central1-b-5046" of role "control-plane" is not ready
Node	control-plane-us-central1-c-mxg3												node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending

Validation Failed
W0201 14:07:17.982700    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 14:07:28.254128    6260 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-5046												node "control-plane-us-central1-b-5046" of role "control-plane" is not ready
Node	control-plane-us-central1-c-mxg3												node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending

Validation Failed
W0201 14:07:29.040381    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 14:07:39.440675    6260 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-5046												node "control-plane-us-central1-b-5046" of role "control-plane" is not ready
Node	control-plane-us-central1-c-mxg3												node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending

Validation Failed
W0201 14:07:40.305585    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
I0201 14:07:50.640729    6260 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-5046												node "control-plane-us-central1-b-5046" of role "control-plane" is not ready
Node	control-plane-us-central1-c-mxg3												node "control-plane-us-central1-c-mxg3" of role "control-plane" is not ready
Pod	kube-system/coredns-5d479c4f64-gghx9												system-cluster-critical pod "coredns-5d479c4f64-gghx9" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-2phzj											system-cluster-critical pod "coredns-autoscaler-557ccb4c66-2phzj" is pending
Pod	kube-system/dns-controller-6f69f47785-xjv66											system-cluster-critical pod "dns-controller-6f69f47785-xjv66" is pending

Validation Failed
W0201 14:07:54.992043    6260 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: validation failed: wait time exceeded during validation
I0201 14:08:04.999448    5900 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/21ede299-a237-11ed-9efc-5e7820dba16b/kops toolbox dump --name ha-migration.k8s.local --dir /logs/artifacts --private-key /tmp/kops-ssh2302611607/key --ssh-user prow
I0201 14:08:04.999493    5900 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/21ede299-a237-11ed-9efc-5e7820dba16b/kops toolbox dump --name ha-migration.k8s.local --dir /logs/artifacts --private-key /tmp/kops-ssh2302611607/key --ssh-user prow
I0201 14:08:05.437528    6270 gce.go:99] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d]
2023/02/01 14:08:09 Dumping node control-plane-us-central1-a-4lp9
2023/02/01 14:08:14 error dumping node control-plane-us-central1-a-4lp9: 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/01 14:08:14 error dumping node control-plane-us-central1-a-4lp9: 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/01 14:08:14 Dumping node control-plane-us-central1-b-5046
2023/02/01 14:08:17 error dumping node control-plane-us-central1-b-5046: 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/01 14:08:17 error dumping node control-plane-us-central1-b-5046: 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/01 14:08:17 Dumping node control-plane-us-central1-c-mxg3
2023/02/01 14:08:22 error dumping node control-plane-us-central1-c-mxg3: 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/01 14:08:22 error dumping node control-plane-us-central1-c-mxg3: 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/01 14:08:22 dumping node not registered in kubernetes: 35.188.29.207
2023/02/01 14:08:22 Dumping node 35.188.29.207
I0201 14:08:24.618822    5900 dumplogs.go:79] /home/prow/go/src/k8s.io/kops/_rundir/21ede299-a237-11ed-9efc-5e7820dba16b/kops get cluster --name ha-migration.k8s.local -o yaml
I0201 14:08:24.618857    5900 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/21ede299-a237-11ed-9efc-5e7820dba16b/kops get cluster --name ha-migration.k8s.local -o yaml
I0201 14:08:24.759810    5900 dumplogs.go:79] /home/prow/go/src/k8s.io/kops/_rundir/21ede299-a237-11ed-9efc-5e7820dba16b/kops get instancegroups --name ha-migration.k8s.local -o yaml
I0201 14:08:24.759842    5900 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/21ede299-a237-11ed-9efc-5e7820dba16b/kops get instancegroups --name ha-migration.k8s.local -o yaml
... skipping 166 lines ...
Deleted cluster: "ha-migration.k8s.local"
I0201 14:10:39.042254    5900 gcs.go:88] gsutil -u k8s-gci-gce-reboot-1-5 rm -r gs://k8s-gci-gce-reboot-1-5-state-21
I0201 14:10:39.042298    5900 local.go:42] ⚙️ gsutil -u k8s-gci-gce-reboot-1-5 rm -r gs://k8s-gci-gce-reboot-1-5-state-21
Removing gs://k8s-gci-gce-reboot-1-5-state-21/...
I0201 14:10:41.620401    5900 down.go:62] releasing boskos project
I0201 14:10:41.629476    5900 boskos.go:83] Boskos heartbeat func received signal to close
Error: exit status 1
+ EXIT_VALUE=1
+ set +o xtrace