e2e-kops-gce-leader-migration #1620962265391960064
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 1 failed / 1 succeeded |
| Started | |
| Elapsed | 20m29s |
| Revision | master |
exit status 1
from junit_runner.xml
Filter through log files | View test history on testgrid
kubetest2 Down
... skipping 156 lines ... ................................Updated [https://www.googleapis.com/compute/v1/projects/k8s-gce-serial-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. I0202 01:50:18.251669 5779 up.go:44] Cleaning up any leaked resources from previous cluster I0202 01:50:18.251801 5779 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/a867d40e-a29b-11ed-8c0a-1250e2f4dc61/kops toolbox dump --name ha-migration.k8s.local --dir /logs/artifacts --private-key /tmp/kops-ssh2365865112/key --ssh-user prow I0202 01:50:18.251819 5779 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/a867d40e-a29b-11ed-8c0a-1250e2f4dc61/kops toolbox dump --name ha-migration.k8s.local --dir /logs/artifacts --private-key /tmp/kops-ssh2365865112/key --ssh-user prow Error: Cluster.kops.k8s.io "ha-migration.k8s.local" not found W0202 01:50:18.475329 5779 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1 I0202 01:50:18.475369 5779 down.go:48] /home/prow/go/src/k8s.io/kops/_rundir/a867d40e-a29b-11ed-8c0a-1250e2f4dc61/kops delete cluster --name ha-migration.k8s.local --yes I0202 01:50:18.475382 5779 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/a867d40e-a29b-11ed-8c0a-1250e2f4dc61/kops delete cluster --name ha-migration.k8s.local --yes Error: error reading cluster configuration: Cluster.kops.k8s.io "ha-migration.k8s.local" not found I0202 01:50:18.624786 5779 gcs.go:51] gsutil ls -b -p k8s-gce-serial-1-5 gs://k8s-gce-serial-1-5-state-a8 I0202 01:50:18.624835 5779 local.go:42] ⚙️ gsutil ls -b -p k8s-gce-serial-1-5 gs://k8s-gce-serial-1-5-state-a8 I0202 01:50:20.803823 5779 gcs.go:70] gsutil mb -p k8s-gce-serial-1-5 gs://k8s-gce-serial-1-5-state-a8 I0202 01:50:20.803869 5779 local.go:42] ⚙️ gsutil mb -p k8s-gce-serial-1-5 gs://k8s-gce-serial-1-5-state-a8 Creating gs://k8s-gce-serial-1-5-state-a8/... I0202 01:50:23.495268 5779 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip 2023/02/02 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 I0202 01:50:23.512707 5779 http.go:37] curl https://ip.jsb.workers.dev I0202 01:50:23.650434 5779 up.go:167] /home/prow/go/src/k8s.io/kops/_rundir/a867d40e-a29b-11ed-8c0a-1250e2f4dc61/kops create cluster --name ha-migration.k8s.local --cloud gce --kubernetes-version v1.23.16 --ssh-public-key /tmp/kops-ssh2365865112/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.224.73.140/32 --master-volume-size 48 --node-volume-size 48 --master-size e2-standard-2 --project k8s-gce-serial-1-5 I0202 01:50:23.650522 5779 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/a867d40e-a29b-11ed-8c0a-1250e2f4dc61/kops create cluster --name ha-migration.k8s.local --cloud gce --kubernetes-version v1.23.16 --ssh-public-key /tmp/kops-ssh2365865112/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.224.73.140/32 --master-volume-size 48 --node-volume-size 48 --master-size e2-standard-2 --project k8s-gce-serial-1-5 I0202 01:50:23.699969 6101 create_cluster.go:882] Using SSH public key: /tmp/kops-ssh2365865112/key.pub I0202 01:50:23.949985 6101 new_cluster.go:573] VMs will be configured to use specified Service Account: default I0202 01:50:23.950121 6101 new_cluster.go:1339] Cloud Provider ID: "gce" ... skipping 527 lines ... I0202 01:50:36.686309 6119 keypair.go:226] Issuing new certificate: "apiserver-aggregator-ca" I0202 01:50:36.687387 6119 keypair.go:226] Issuing new certificate: "etcd-peers-ca-events" W0202 01:50:36.871502 6119 vfs_keystorereader.go:143] CA private key was not found I0202 01:50:36.994987 6119 keypair.go:226] Issuing new certificate: "kubernetes-ca" I0202 01:50:37.084609 6119 keypair.go:226] Issuing new certificate: "service-account" I0202 01:50:52.290732 6119 executor.go:111] Tasks: 50 done / 91 total; 23 can run W0202 01:51:05.342069 6119 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-gce-serial-1-5/regions/us-central1/targetPools/api-ha-migration-k8s-local' is not ready, resourceNotReady I0202 01:51:05.342135 6119 executor.go:111] Tasks: 72 done / 91 total; 13 can run I0202 01:51:12.214797 6119 executor.go:111] Tasks: 85 done / 91 total; 6 can run I0202 01:51:26.180809 6119 executor.go:111] Tasks: 91 done / 91 total; 0 can run I0202 01:51:26.255402 6119 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. I0202 01:51:36.611029 5779 up.go:251] /home/prow/go/src/k8s.io/kops/_rundir/a867d40e-a29b-11ed-8c0a-1250e2f4dc61/kops validate cluster --name ha-migration.k8s.local --count 10 --wait 15m0s I0202 01:51:36.611090 5779 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/a867d40e-a29b-11ed-8c0a-1250e2f4dc61/kops validate cluster --name ha-migration.k8s.local --count 10 --wait 15m0s Validating cluster ha-migration.k8s.local W0202 01:52:07.246569 6139 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.136.42.53/api/v1/nodes": dial tcp 34.136.42.53:443: i/o timeout W0202 01:52:47.248867 6139 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.136.42.53/api/v1/nodes": dial tcp 34.136.42.53:443: i/o timeout W0202 01:52:57.252390 6139 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.136.42.53/api/v1/nodes": dial tcp 34.136.42.53:443: connect: connection refused W0202 01:53:07.255956 6139 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.136.42.53/api/v1/nodes": dial tcp 34.136.42.53:443: connect: connection refused W0202 01:53:17.258765 6139 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.136.42.53/api/v1/nodes": dial tcp 34.136.42.53:443: connect: connection refused W0202 01:53:27.261442 6139 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.136.42.53/api/v1/nodes": dial tcp 34.136.42.53:443: connect: connection refused W0202 01:53:37.264647 6139 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.136.42.53/api/v1/nodes": dial tcp 34.136.42.53:443: connect: connection refused W0202 01:53:47.267757 6139 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.136.42.53/api/v1/nodes": dial tcp 34.136.42.53:443: connect: connection refused W0202 01:54:07.272003 6139 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.136.42.53/api/v1/nodes": net/http: TLS handshake timeout W0202 01:54:28.248473 6139 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.136.42.53/api/v1/nodes": dial tcp 34.136.42.53:443: connect: connection refused - error from a previous attempt: read tcp 10.60.165.241:46748->34.136.42.53:443: read: connection reset by peer W0202 01:54:48.252279 6139 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.136.42.53/api/v1/nodes": net/http: TLS handshake timeout W0202 01:54:58.256785 6139 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.136.42.53/api/v1/nodes": dial tcp 34.136.42.53:443: connect: connection refused I0202 01:55:07.638163 5779 boskos.go:86] Sending heartbeat to Boskos W0202 01:55:08.261679 6139 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.136.42.53/api/v1/nodes": dial tcp 34.136.42.53:443: connect: connection refused W0202 01:55:28.267674 6139 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.136.42.53/api/v1/nodes": net/http: TLS handshake timeout W0202 01:55:38.271896 6139 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.136.42.53/api/v1/nodes": dial tcp 34.136.42.53:443: connect: connection refused W0202 01:55:48.276109 6139 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.136.42.53/api/v1/nodes": dial tcp 34.136.42.53:443: connect: connection refused W0202 01:56:12.055876 6139 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.136.42.53/api/v1/nodes": net/http: TLS handshake timeout - error from a previous attempt: read tcp 10.60.165.241:38612->34.136.42.53:443: read: connection reset by peer W0202 01:56:22.063667 6139 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://34.136.42.53/api/v1/nodes": dial tcp 34.136.42.53:443: connect: connection refused I0202 01:56:32.526531 6139 gce_cloud.go:301] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d] INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-central1-a ControlPlane e2-standard-2 1 1 us-central1 control-plane-us-central1-b ControlPlane e2-standard-2 1 1 us-central1 control-plane-us-central1-c ControlPlane e2-standard-2 1 1 us-central1 ... skipping 10 lines ... Machine https://www.googleapis.com/compute/v1/projects/k8s-gce-serial-1-5/zones/us-central1-a/instances/nodes-us-central1-a-5j3x machine "https://www.googleapis.com/compute/v1/projects/k8s-gce-serial-1-5/zones/us-central1-a/instances/nodes-us-central1-a-5j3x" has not yet joined cluster Machine https://www.googleapis.com/compute/v1/projects/k8s-gce-serial-1-5/zones/us-central1-b/instances/control-plane-us-central1-b-26dq machine "https://www.googleapis.com/compute/v1/projects/k8s-gce-serial-1-5/zones/us-central1-b/instances/control-plane-us-central1-b-26dq" has not yet joined cluster Machine https://www.googleapis.com/compute/v1/projects/k8s-gce-serial-1-5/zones/us-central1-c/instances/control-plane-us-central1-c-pfd4 machine "https://www.googleapis.com/compute/v1/projects/k8s-gce-serial-1-5/zones/us-central1-c/instances/control-plane-us-central1-c-pfd4" has not yet joined cluster Node control-plane-us-central1-a-xw5s node "control-plane-us-central1-a-xw5s" of role "control-plane" is not ready Pod kube-system/kube-controller-manager-control-plane-us-central1-a-xw5s system-cluster-critical pod "kube-controller-manager-control-plane-us-central1-a-xw5s" is not ready (kube-controller-manager) Validation Failed W0202 01:56:33.471353 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 01:56:43.922131 6139 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 11 lines ... Machine https://www.googleapis.com/compute/v1/projects/k8s-gce-serial-1-5/zones/us-central1-a/instances/nodes-us-central1-a-5j3x machine "https://www.googleapis.com/compute/v1/projects/k8s-gce-serial-1-5/zones/us-central1-a/instances/nodes-us-central1-a-5j3x" has not yet joined cluster Machine https://www.googleapis.com/compute/v1/projects/k8s-gce-serial-1-5/zones/us-central1-b/instances/control-plane-us-central1-b-26dq machine "https://www.googleapis.com/compute/v1/projects/k8s-gce-serial-1-5/zones/us-central1-b/instances/control-plane-us-central1-b-26dq" has not yet joined cluster Machine https://www.googleapis.com/compute/v1/projects/k8s-gce-serial-1-5/zones/us-central1-c/instances/control-plane-us-central1-c-pfd4 machine "https://www.googleapis.com/compute/v1/projects/k8s-gce-serial-1-5/zones/us-central1-c/instances/control-plane-us-central1-c-pfd4" has not yet joined cluster Node control-plane-us-central1-a-xw5s node "control-plane-us-central1-a-xw5s" of role "control-plane" is not ready Pod kube-system/kube-controller-manager-control-plane-us-central1-a-xw5s system-cluster-critical pod "kube-controller-manager-control-plane-us-central1-a-xw5s" is not ready (kube-controller-manager) Validation Failed W0202 01:56:44.854778 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 01:56:55.290685 6139 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 11 lines ... Machine https://www.googleapis.com/compute/v1/projects/k8s-gce-serial-1-5/zones/us-central1-a/instances/nodes-us-central1-a-5j3x machine "https://www.googleapis.com/compute/v1/projects/k8s-gce-serial-1-5/zones/us-central1-a/instances/nodes-us-central1-a-5j3x" has not yet joined cluster Machine https://www.googleapis.com/compute/v1/projects/k8s-gce-serial-1-5/zones/us-central1-b/instances/control-plane-us-central1-b-26dq machine "https://www.googleapis.com/compute/v1/projects/k8s-gce-serial-1-5/zones/us-central1-b/instances/control-plane-us-central1-b-26dq" has not yet joined cluster Machine https://www.googleapis.com/compute/v1/projects/k8s-gce-serial-1-5/zones/us-central1-c/instances/control-plane-us-central1-c-pfd4 machine "https://www.googleapis.com/compute/v1/projects/k8s-gce-serial-1-5/zones/us-central1-c/instances/control-plane-us-central1-c-pfd4" has not yet joined cluster Node control-plane-us-central1-a-xw5s node "control-plane-us-central1-a-xw5s" of role "control-plane" is not ready Pod kube-system/kube-controller-manager-control-plane-us-central1-a-xw5s system-cluster-critical pod "kube-controller-manager-control-plane-us-central1-a-xw5s" is not ready (kube-controller-manager) Validation Failed W0202 01:56:56.126704 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 01:57:06.502186 6139 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-gce-serial-1-5/zones/us-central1-b/instances/control-plane-us-central1-b-26dq machine "https://www.googleapis.com/compute/v1/projects/k8s-gce-serial-1-5/zones/us-central1-b/instances/control-plane-us-central1-b-26dq" has not yet joined cluster Node control-plane-us-central1-a-xw5s node "control-plane-us-central1-a-xw5s" of role "control-plane" is not ready Node control-plane-us-central1-c-pfd4 node "control-plane-us-central1-c-pfd4" of role "control-plane" is not ready Pod kube-system/kube-apiserver-control-plane-us-central1-a-xw5s system-cluster-critical pod "kube-apiserver-control-plane-us-central1-a-xw5s" is pending Pod kube-system/kube-controller-manager-control-plane-us-central1-a-xw5s system-cluster-critical pod "kube-controller-manager-control-plane-us-central1-a-xw5s" is not ready (kube-controller-manager) Validation Failed W0202 01:57:07.419206 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 01:57:17.875570 6139 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-xw5s node "control-plane-us-central1-a-xw5s" of role "control-plane" is not ready Node control-plane-us-central1-c-pfd4 node "control-plane-us-central1-c-pfd4" of role "control-plane" is not ready Pod kube-system/kube-controller-manager-control-plane-us-central1-a-xw5s system-cluster-critical pod "kube-controller-manager-control-plane-us-central1-a-xw5s" is not ready (kube-controller-manager) Pod kube-system/kube-controller-manager-control-plane-us-central1-c-pfd4 system-cluster-critical pod "kube-controller-manager-control-plane-us-central1-c-pfd4" is not ready (kube-controller-manager) Pod kube-system/kube-scheduler-control-plane-us-central1-c-pfd4 system-cluster-critical pod "kube-scheduler-control-plane-us-central1-c-pfd4" is pending Validation Failed W0202 01:57:18.735878 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 01:57:29.201188 6139 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-gce-serial-1-5/zones/us-central1-b/instances/control-plane-us-central1-b-26dq machine "https://www.googleapis.com/compute/v1/projects/k8s-gce-serial-1-5/zones/us-central1-b/instances/control-plane-us-central1-b-26dq" has not yet joined cluster Node control-plane-us-central1-a-xw5s node "control-plane-us-central1-a-xw5s" of role "control-plane" is not ready Node control-plane-us-central1-c-pfd4 node "control-plane-us-central1-c-pfd4" of role "control-plane" is not ready Pod kube-system/kube-controller-manager-control-plane-us-central1-a-xw5s system-cluster-critical pod "kube-controller-manager-control-plane-us-central1-a-xw5s" is not ready (kube-controller-manager) Pod kube-system/kube-controller-manager-control-plane-us-central1-c-pfd4 system-cluster-critical pod "kube-controller-manager-control-plane-us-central1-c-pfd4" is not ready (kube-controller-manager) Validation Failed W0202 01:57:30.069040 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 01:57:40.533840 6139 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 11 lines ... KIND NAME MESSAGE Machine https://www.googleapis.com/compute/v1/projects/k8s-gce-serial-1-5/zones/us-central1-a/instances/nodes-us-central1-a-5j3x machine "https://www.googleapis.com/compute/v1/projects/k8s-gce-serial-1-5/zones/us-central1-a/instances/nodes-us-central1-a-5j3x" has not yet joined cluster Machine https://www.googleapis.com/compute/v1/projects/k8s-gce-serial-1-5/zones/us-central1-b/instances/control-plane-us-central1-b-26dq machine "https://www.googleapis.com/compute/v1/projects/k8s-gce-serial-1-5/zones/us-central1-b/instances/control-plane-us-central1-b-26dq" has not yet joined cluster Node control-plane-us-central1-a-xw5s node "control-plane-us-central1-a-xw5s" of role "control-plane" is not ready Node control-plane-us-central1-c-pfd4 node "control-plane-us-central1-c-pfd4" of role "control-plane" is not ready Validation Failed W0202 01:57:41.328194 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 01:57:51.713040 6139 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-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Pod kube-system/dns-controller-6f69f47785-ngc7x system-cluster-critical pod "dns-controller-6f69f47785-ngc7x" is pending Pod kube-system/kops-controller-ms9nj system-cluster-critical pod "kops-controller-ms9nj" is pending Pod kube-system/kops-controller-s4fh8 system-cluster-critical pod "kops-controller-s4fh8" is pending Validation Failed W0202 01:57:52.558248 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 01:58:02.929483 6139 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/cilium-sj7pd system-node-critical pod "cilium-sj7pd" is pending Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Pod kube-system/dns-controller-6f69f47785-ngc7x system-cluster-critical pod "dns-controller-6f69f47785-ngc7x" is pending Pod kube-system/kops-controller-cclbz system-cluster-critical pod "kops-controller-cclbz" is pending Validation Failed W0202 01:58:03.806905 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 01:58:14.225403 6139 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/cilium-sj7pd system-node-critical pod "cilium-sj7pd" is pending Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Pod kube-system/etcd-manager-main-control-plane-us-central1-c-pfd4 system-cluster-critical pod "etcd-manager-main-control-plane-us-central1-c-pfd4" is pending Pod kube-system/kube-controller-manager-control-plane-us-central1-b-26dq system-cluster-critical pod "kube-controller-manager-control-plane-us-central1-b-26dq" is not ready (kube-controller-manager) Validation Failed W0202 01:58:15.037272 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 01:58:25.480796 6139 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-sj7pd system-node-critical pod "cilium-sj7pd" is not ready (cilium-agent) Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Pod kube-system/kube-apiserver-control-plane-us-central1-c-pfd4 system-cluster-critical pod "kube-apiserver-control-plane-us-central1-c-pfd4" is pending Pod kube-system/kube-scheduler-control-plane-us-central1-b-26dq system-cluster-critical pod "kube-scheduler-control-plane-us-central1-b-26dq" is pending Validation Failed W0202 01:58:26.286745 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 01:58:36.706867 6139 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-msqgd system-node-critical pod "cilium-msqgd" is pending Pod kube-system/cilium-qmtlz system-node-critical pod "cilium-qmtlz" is not ready (cilium-agent) Pod kube-system/cilium-sj7pd system-node-critical pod "cilium-sj7pd" is not ready (cilium-agent) Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Validation Failed W0202 01:58:37.589026 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 01:58:49.011252 6139 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 ... Node nodes-us-central1-a-5j3x node "nodes-us-central1-a-5j3x" of role "node" is not ready Pod kube-system/cilium-msqgd system-node-critical pod "cilium-msqgd" is not ready (cilium-agent) Pod kube-system/cilium-qmtlz system-node-critical pod "cilium-qmtlz" is not ready (cilium-agent) Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Validation Failed W0202 01:58:49.841193 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 01:59:00.269550 6139 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-msqgd system-node-critical pod "cilium-msqgd" is not ready (cilium-agent) Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Pod kube-system/etcd-manager-main-control-plane-us-central1-b-26dq system-cluster-critical pod "etcd-manager-main-control-plane-us-central1-b-26dq" is pending Pod kube-system/kube-apiserver-control-plane-us-central1-b-26dq system-cluster-critical pod "kube-apiserver-control-plane-us-central1-b-26dq" is pending Validation Failed W0202 01:59:01.169812 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 01:59:11.582199 6139 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-26dq node "control-plane-us-central1-b-26dq" of role "control-plane" is not ready Node control-plane-us-central1-c-pfd4 node "control-plane-us-central1-c-pfd4" of role "control-plane" is not ready Node nodes-us-central1-a-5j3x node "nodes-us-central1-a-5j3x" of role "node" is not ready Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Validation Failed W0202 01:59:12.451221 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 01:59:22.835230 6139 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-26dq node "control-plane-us-central1-b-26dq" of role "control-plane" is not ready Node control-plane-us-central1-c-pfd4 node "control-plane-us-central1-c-pfd4" of role "control-plane" is not ready Node nodes-us-central1-a-5j3x node "nodes-us-central1-a-5j3x" of role "node" is not ready Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Validation Failed W0202 01:59:23.731191 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 01:59:34.162926 6139 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-26dq node "control-plane-us-central1-b-26dq" of role "control-plane" is not ready Node control-plane-us-central1-c-pfd4 node "control-plane-us-central1-c-pfd4" of role "control-plane" is not ready Node nodes-us-central1-a-5j3x node "nodes-us-central1-a-5j3x" of role "node" is not ready Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Validation Failed W0202 01:59:35.029406 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 01:59:45.493947 6139 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-26dq node "control-plane-us-central1-b-26dq" of role "control-plane" is not ready Node control-plane-us-central1-c-pfd4 node "control-plane-us-central1-c-pfd4" of role "control-plane" is not ready Node nodes-us-central1-a-5j3x node "nodes-us-central1-a-5j3x" of role "node" is not ready Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Validation Failed W0202 01:59:46.285318 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 01:59:56.695529 6139 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-26dq node "control-plane-us-central1-b-26dq" of role "control-plane" is not ready Node control-plane-us-central1-c-pfd4 node "control-plane-us-central1-c-pfd4" of role "control-plane" is not ready Node nodes-us-central1-a-5j3x node "nodes-us-central1-a-5j3x" of role "node" is not ready Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Validation Failed W0202 01:59:57.497261 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 02:00:07.649880 5779 boskos.go:86] Sending heartbeat to Boskos I0202 02:00:07.965412 6139 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-26dq node "control-plane-us-central1-b-26dq" of role "control-plane" is not ready Node control-plane-us-central1-c-pfd4 node "control-plane-us-central1-c-pfd4" of role "control-plane" is not ready Node nodes-us-central1-a-5j3x node "nodes-us-central1-a-5j3x" of role "node" is not ready Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Validation Failed W0202 02:00:08.940159 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 02:00:19.346236 6139 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-26dq node "control-plane-us-central1-b-26dq" of role "control-plane" is not ready Node control-plane-us-central1-c-pfd4 node "control-plane-us-central1-c-pfd4" of role "control-plane" is not ready Node nodes-us-central1-a-5j3x node "nodes-us-central1-a-5j3x" of role "node" is not ready Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Validation Failed W0202 02:00:20.226743 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 02:00:30.675660 6139 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-26dq node "control-plane-us-central1-b-26dq" of role "control-plane" is not ready Node control-plane-us-central1-c-pfd4 node "control-plane-us-central1-c-pfd4" of role "control-plane" is not ready Node nodes-us-central1-a-5j3x node "nodes-us-central1-a-5j3x" of role "node" is not ready Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Validation Failed W0202 02:00:31.788110 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 02:00:42.214691 6139 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-26dq node "control-plane-us-central1-b-26dq" of role "control-plane" is not ready Node control-plane-us-central1-c-pfd4 node "control-plane-us-central1-c-pfd4" of role "control-plane" is not ready Node nodes-us-central1-a-5j3x node "nodes-us-central1-a-5j3x" of role "node" is not ready Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Validation Failed W0202 02:00:43.151770 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 02:00:53.550052 6139 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-26dq node "control-plane-us-central1-b-26dq" of role "control-plane" is not ready Node control-plane-us-central1-c-pfd4 node "control-plane-us-central1-c-pfd4" of role "control-plane" is not ready Node nodes-us-central1-a-5j3x node "nodes-us-central1-a-5j3x" of role "node" is not ready Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Validation Failed W0202 02:00:54.366779 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 02:01:04.795658 6139 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-26dq node "control-plane-us-central1-b-26dq" of role "control-plane" is not ready Node control-plane-us-central1-c-pfd4 node "control-plane-us-central1-c-pfd4" of role "control-plane" is not ready Node nodes-us-central1-a-5j3x node "nodes-us-central1-a-5j3x" of role "node" is not ready Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Validation Failed W0202 02:01:05.842600 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 02:01:16.319285 6139 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-26dq node "control-plane-us-central1-b-26dq" of role "control-plane" is not ready Node control-plane-us-central1-c-pfd4 node "control-plane-us-central1-c-pfd4" of role "control-plane" is not ready Node nodes-us-central1-a-5j3x node "nodes-us-central1-a-5j3x" of role "node" is not ready Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Validation Failed W0202 02:01:17.648680 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 02:01:28.120101 6139 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-26dq node "control-plane-us-central1-b-26dq" of role "control-plane" is not ready Node control-plane-us-central1-c-pfd4 node "control-plane-us-central1-c-pfd4" of role "control-plane" is not ready Node nodes-us-central1-a-5j3x node "nodes-us-central1-a-5j3x" of role "node" is not ready Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Validation Failed W0202 02:01:28.986119 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 02:01:39.341171 6139 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-26dq node "control-plane-us-central1-b-26dq" of role "control-plane" is not ready Node control-plane-us-central1-c-pfd4 node "control-plane-us-central1-c-pfd4" of role "control-plane" is not ready Node nodes-us-central1-a-5j3x node "nodes-us-central1-a-5j3x" of role "node" is not ready Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Validation Failed W0202 02:01:40.188149 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 02:01:50.609265 6139 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-26dq node "control-plane-us-central1-b-26dq" of role "control-plane" is not ready Node control-plane-us-central1-c-pfd4 node "control-plane-us-central1-c-pfd4" of role "control-plane" is not ready Node nodes-us-central1-a-5j3x node "nodes-us-central1-a-5j3x" of role "node" is not ready Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Validation Failed W0202 02:01:51.464428 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 02:02:01.883516 6139 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-26dq node "control-plane-us-central1-b-26dq" of role "control-plane" is not ready Node control-plane-us-central1-c-pfd4 node "control-plane-us-central1-c-pfd4" of role "control-plane" is not ready Node nodes-us-central1-a-5j3x node "nodes-us-central1-a-5j3x" of role "node" is not ready Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Validation Failed W0202 02:02:02.676709 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 02:02:13.099476 6139 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-26dq node "control-plane-us-central1-b-26dq" of role "control-plane" is not ready Node control-plane-us-central1-c-pfd4 node "control-plane-us-central1-c-pfd4" of role "control-plane" is not ready Node nodes-us-central1-a-5j3x node "nodes-us-central1-a-5j3x" of role "node" is not ready Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Validation Failed W0202 02:02:13.983169 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 02:02:24.376900 6139 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-26dq node "control-plane-us-central1-b-26dq" of role "control-plane" is not ready Node control-plane-us-central1-c-pfd4 node "control-plane-us-central1-c-pfd4" of role "control-plane" is not ready Node nodes-us-central1-a-5j3x node "nodes-us-central1-a-5j3x" of role "node" is not ready Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Validation Failed W0202 02:02:25.287911 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 02:02:35.765151 6139 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-26dq node "control-plane-us-central1-b-26dq" of role "control-plane" is not ready Node control-plane-us-central1-c-pfd4 node "control-plane-us-central1-c-pfd4" of role "control-plane" is not ready Node nodes-us-central1-a-5j3x node "nodes-us-central1-a-5j3x" of role "node" is not ready Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Validation Failed W0202 02:02:36.604096 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 02:02:47.082158 6139 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-26dq node "control-plane-us-central1-b-26dq" of role "control-plane" is not ready Node control-plane-us-central1-c-pfd4 node "control-plane-us-central1-c-pfd4" of role "control-plane" is not ready Node nodes-us-central1-a-5j3x node "nodes-us-central1-a-5j3x" of role "node" is not ready Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Validation Failed W0202 02:02:48.004605 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 02:02:58.418138 6139 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-26dq node "control-plane-us-central1-b-26dq" of role "control-plane" is not ready Node control-plane-us-central1-c-pfd4 node "control-plane-us-central1-c-pfd4" of role "control-plane" is not ready Node nodes-us-central1-a-5j3x node "nodes-us-central1-a-5j3x" of role "node" is not ready Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Validation Failed W0202 02:02:59.384726 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 02:03:09.814674 6139 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-26dq node "control-plane-us-central1-b-26dq" of role "control-plane" is not ready Node control-plane-us-central1-c-pfd4 node "control-plane-us-central1-c-pfd4" of role "control-plane" is not ready Node nodes-us-central1-a-5j3x node "nodes-us-central1-a-5j3x" of role "node" is not ready Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Validation Failed W0202 02:03:10.721435 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 02:03:21.179430 6139 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-26dq node "control-plane-us-central1-b-26dq" of role "control-plane" is not ready Node control-plane-us-central1-c-pfd4 node "control-plane-us-central1-c-pfd4" of role "control-plane" is not ready Node nodes-us-central1-a-5j3x node "nodes-us-central1-a-5j3x" of role "node" is not ready Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Validation Failed W0202 02:03:22.076185 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 02:03:32.528820 6139 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-26dq node "control-plane-us-central1-b-26dq" of role "control-plane" is not ready Node control-plane-us-central1-c-pfd4 node "control-plane-us-central1-c-pfd4" of role "control-plane" is not ready Node nodes-us-central1-a-5j3x node "nodes-us-central1-a-5j3x" of role "node" is not ready Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Validation Failed W0202 02:03:33.379661 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 02:03:43.917201 6139 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-26dq node "control-plane-us-central1-b-26dq" of role "control-plane" is not ready Node control-plane-us-central1-c-pfd4 node "control-plane-us-central1-c-pfd4" of role "control-plane" is not ready Node nodes-us-central1-a-5j3x node "nodes-us-central1-a-5j3x" of role "node" is not ready Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Validation Failed W0202 02:03:44.785830 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 02:03:55.283381 6139 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-26dq node "control-plane-us-central1-b-26dq" of role "control-plane" is not ready Node control-plane-us-central1-c-pfd4 node "control-plane-us-central1-c-pfd4" of role "control-plane" is not ready Node nodes-us-central1-a-5j3x node "nodes-us-central1-a-5j3x" of role "node" is not ready Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Validation Failed W0202 02:03:56.102545 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 02:04:06.491317 6139 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-26dq node "control-plane-us-central1-b-26dq" of role "control-plane" is not ready Node control-plane-us-central1-c-pfd4 node "control-plane-us-central1-c-pfd4" of role "control-plane" is not ready Node nodes-us-central1-a-5j3x node "nodes-us-central1-a-5j3x" of role "node" is not ready Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Validation Failed W0202 02:04:07.391162 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 02:04:17.799527 6139 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-26dq node "control-plane-us-central1-b-26dq" of role "control-plane" is not ready Node control-plane-us-central1-c-pfd4 node "control-plane-us-central1-c-pfd4" of role "control-plane" is not ready Node nodes-us-central1-a-5j3x node "nodes-us-central1-a-5j3x" of role "node" is not ready Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Validation Failed W0202 02:04:18.606560 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 02:04:29.121200 6139 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-26dq node "control-plane-us-central1-b-26dq" of role "control-plane" is not ready Node control-plane-us-central1-c-pfd4 node "control-plane-us-central1-c-pfd4" of role "control-plane" is not ready Node nodes-us-central1-a-5j3x node "nodes-us-central1-a-5j3x" of role "node" is not ready Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Validation Failed W0202 02:04:29.975542 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 02:04:40.392364 6139 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-26dq node "control-plane-us-central1-b-26dq" of role "control-plane" is not ready Node control-plane-us-central1-c-pfd4 node "control-plane-us-central1-c-pfd4" of role "control-plane" is not ready Node nodes-us-central1-a-5j3x node "nodes-us-central1-a-5j3x" of role "node" is not ready Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Validation Failed W0202 02:04:41.325291 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 02:04:51.777167 6139 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-26dq node "control-plane-us-central1-b-26dq" of role "control-plane" is not ready Node control-plane-us-central1-c-pfd4 node "control-plane-us-central1-c-pfd4" of role "control-plane" is not ready Node nodes-us-central1-a-5j3x node "nodes-us-central1-a-5j3x" of role "node" is not ready Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Validation Failed W0202 02:04:52.614181 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 02:05:03.031703 6139 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-26dq node "control-plane-us-central1-b-26dq" of role "control-plane" is not ready Node control-plane-us-central1-c-pfd4 node "control-plane-us-central1-c-pfd4" of role "control-plane" is not ready Node nodes-us-central1-a-5j3x node "nodes-us-central1-a-5j3x" of role "node" is not ready Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Validation Failed W0202 02:05:03.882233 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 02:05:07.661370 5779 boskos.go:86] Sending heartbeat to Boskos I0202 02:05:14.302431 6139 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-26dq node "control-plane-us-central1-b-26dq" of role "control-plane" is not ready Node control-plane-us-central1-c-pfd4 node "control-plane-us-central1-c-pfd4" of role "control-plane" is not ready Node nodes-us-central1-a-5j3x node "nodes-us-central1-a-5j3x" of role "node" is not ready Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Validation Failed W0202 02:05:15.161641 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 02:05:25.634698 6139 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-26dq node "control-plane-us-central1-b-26dq" of role "control-plane" is not ready Node control-plane-us-central1-c-pfd4 node "control-plane-us-central1-c-pfd4" of role "control-plane" is not ready Node nodes-us-central1-a-5j3x node "nodes-us-central1-a-5j3x" of role "node" is not ready Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Validation Failed W0202 02:05:26.482724 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 02:05:36.961618 6139 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-26dq node "control-plane-us-central1-b-26dq" of role "control-plane" is not ready Node control-plane-us-central1-c-pfd4 node "control-plane-us-central1-c-pfd4" of role "control-plane" is not ready Node nodes-us-central1-a-5j3x node "nodes-us-central1-a-5j3x" of role "node" is not ready Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Validation Failed W0202 02:05:37.809110 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 02:05:48.243335 6139 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-26dq node "control-plane-us-central1-b-26dq" of role "control-plane" is not ready Node control-plane-us-central1-c-pfd4 node "control-plane-us-central1-c-pfd4" of role "control-plane" is not ready Node nodes-us-central1-a-5j3x node "nodes-us-central1-a-5j3x" of role "node" is not ready Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Validation Failed W0202 02:05:49.058969 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 02:05:59.615836 6139 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-26dq node "control-plane-us-central1-b-26dq" of role "control-plane" is not ready Node control-plane-us-central1-c-pfd4 node "control-plane-us-central1-c-pfd4" of role "control-plane" is not ready Node nodes-us-central1-a-5j3x node "nodes-us-central1-a-5j3x" of role "node" is not ready Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Validation Failed W0202 02:06:00.434140 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 02:06:10.844067 6139 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-26dq node "control-plane-us-central1-b-26dq" of role "control-plane" is not ready Node control-plane-us-central1-c-pfd4 node "control-plane-us-central1-c-pfd4" of role "control-plane" is not ready Node nodes-us-central1-a-5j3x node "nodes-us-central1-a-5j3x" of role "node" is not ready Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Validation Failed W0202 02:06:11.690888 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 02:06:22.158582 6139 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-26dq node "control-plane-us-central1-b-26dq" of role "control-plane" is not ready Node control-plane-us-central1-c-pfd4 node "control-plane-us-central1-c-pfd4" of role "control-plane" is not ready Node nodes-us-central1-a-5j3x node "nodes-us-central1-a-5j3x" of role "node" is not ready Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Validation Failed W0202 02:06:23.010274 6139 validate_cluster.go:232] (will retry): cluster not yet healthy I0202 02:06:33.426984 6139 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-26dq node "control-plane-us-central1-b-26dq" of role "control-plane" is not ready Node control-plane-us-central1-c-pfd4 node "control-plane-us-central1-c-pfd4" of role "control-plane" is not ready Node nodes-us-central1-a-5j3x node "nodes-us-central1-a-5j3x" of role "node" is not ready Pod kube-system/coredns-5d479c4f64-n2hlj system-cluster-critical pod "coredns-5d479c4f64-n2hlj" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-jv6qn system-cluster-critical pod "coredns-autoscaler-557ccb4c66-jv6qn" is pending Validation Failed W0202 02:06:34.352502 6139 validate_cluster.go:232] (will retry): cluster not yet healthy Error: validation failed: wait time exceeded during validation I0202 02:06:44.359040 5779 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/a867d40e-a29b-11ed-8c0a-1250e2f4dc61/kops toolbox dump --name ha-migration.k8s.local --dir /logs/artifacts --private-key /tmp/kops-ssh2365865112/key --ssh-user prow I0202 02:06:44.359091 5779 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/a867d40e-a29b-11ed-8c0a-1250e2f4dc61/kops toolbox dump --name ha-migration.k8s.local --dir /logs/artifacts --private-key /tmp/kops-ssh2365865112/key --ssh-user prow I0202 02:06:44.846870 6149 gce.go:99] Scanning zones: [us-central1-c us-central1-a us-central1-f us-central1-b us-central1-d] 2023/02/02 02:06:49 Dumping node control-plane-us-central1-a-xw5s 2023/02/02 02:06:53 error dumping node control-plane-us-central1-a-xw5s: 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/02 02:06:53 error dumping node control-plane-us-central1-a-xw5s: 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/02 02:06:53 Dumping node control-plane-us-central1-b-26dq 2023/02/02 02:06:58 error dumping node control-plane-us-central1-b-26dq: 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/02 02:06:58 error dumping node control-plane-us-central1-b-26dq: 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/02 02:06:58 Dumping node control-plane-us-central1-c-pfd4 2023/02/02 02:07:02 error dumping node control-plane-us-central1-c-pfd4: 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/02 02:07:02 error dumping node control-plane-us-central1-c-pfd4: 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/02 02:07:02 Dumping node nodes-us-central1-a-5j3x I0202 02:07:04.871527 5779 dumplogs.go:79] /home/prow/go/src/k8s.io/kops/_rundir/a867d40e-a29b-11ed-8c0a-1250e2f4dc61/kops get cluster --name ha-migration.k8s.local -o yaml I0202 02:07:04.871568 5779 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/a867d40e-a29b-11ed-8c0a-1250e2f4dc61/kops get cluster --name ha-migration.k8s.local -o yaml I0202 02:07:05.046173 5779 dumplogs.go:79] /home/prow/go/src/k8s.io/kops/_rundir/a867d40e-a29b-11ed-8c0a-1250e2f4dc61/kops get instancegroups --name ha-migration.k8s.local -o yaml I0202 02:07:05.046218 5779 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/a867d40e-a29b-11ed-8c0a-1250e2f4dc61/kops get instancegroups --name ha-migration.k8s.local -o yaml I0202 02:07:05.587196 5779 dumplogs.go:98] kubectl cluster-info dump --all-namespaces -o yaml --output-directory /logs/artifacts/cluster-info ... skipping 165 lines ... Deleted cluster: "ha-migration.k8s.local" I0202 02:09:26.844163 5779 gcs.go:88] gsutil -u k8s-gce-serial-1-5 rm -r gs://k8s-gce-serial-1-5-state-a8 I0202 02:09:26.844222 5779 local.go:42] ⚙️ gsutil -u k8s-gce-serial-1-5 rm -r gs://k8s-gce-serial-1-5-state-a8 Removing gs://k8s-gce-serial-1-5-state-a8/... I0202 02:09:29.433495 5779 down.go:62] releasing boskos project I0202 02:09:29.445387 5779 boskos.go:83] Boskos heartbeat func received signal to close Error: exit status 1 + EXIT_VALUE=1 + set +o xtrace