e2e-kops-grid-kubenet-flatcar-k23-ko25 #1614186202385092608
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 1 failed / 1 succeeded |
| Started | |
| Elapsed | 24m27s |
| Revision | master |
exit status 1
from junit_runner.xml
Filter through log files | View test history on testgrid
kubetest2 Down
... skipping 136 lines ... I0114 09:04:27.140249 5492 http.go:37] curl https://storage.googleapis.com/kops-ci/markers/release-1.25/latest-ci-updown-green.txt I0114 09:04:27.142659 5492 http.go:37] curl https://storage.googleapis.com/k8s-staging-kops/kops/releases/1.25.4+v1.25.3-36-ge54c316bd9/linux/amd64/kops I0114 09:04:27.839439 5492 local.go:42] ⚙️ ssh-keygen -t ed25519 -N -q -f /tmp/kops/e2e-e2e-kops-grid-kubenet-flatcar-k23-ko25.test-cncf-aws.k8s.io/id_ed25519 I0114 09:04:27.852247 5492 up.go:44] Cleaning up any leaked resources from previous cluster I0114 09:04:27.852529 5492 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/2fefd7c4-93ea-11ed-bd5d-72eebb4d772a/kops toolbox dump --name e2e-e2e-kops-grid-kubenet-flatcar-k23-ko25.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-kubenet-flatcar-k23-ko25.test-cncf-aws.k8s.io/id_ed25519 --ssh-user core I0114 09:04:27.852561 5492 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/2fefd7c4-93ea-11ed-bd5d-72eebb4d772a/kops toolbox dump --name e2e-e2e-kops-grid-kubenet-flatcar-k23-ko25.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-kubenet-flatcar-k23-ko25.test-cncf-aws.k8s.io/id_ed25519 --ssh-user core Error: Cluster.kops.k8s.io "e2e-e2e-kops-grid-kubenet-flatcar-k23-ko25.test-cncf-aws.k8s.io" not found W0114 09:04:28.353333 5492 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1 I0114 09:04:28.353387 5492 down.go:48] /home/prow/go/src/k8s.io/kops/_rundir/2fefd7c4-93ea-11ed-bd5d-72eebb4d772a/kops delete cluster --name e2e-e2e-kops-grid-kubenet-flatcar-k23-ko25.test-cncf-aws.k8s.io --yes I0114 09:04:28.353402 5492 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/2fefd7c4-93ea-11ed-bd5d-72eebb4d772a/kops delete cluster --name e2e-e2e-kops-grid-kubenet-flatcar-k23-ko25.test-cncf-aws.k8s.io --yes Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-e2e-kops-grid-kubenet-flatcar-k23-ko25.test-cncf-aws.k8s.io" not found I0114 09:04:28.882694 5492 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip 2023/01/14 09:04:28 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 I0114 09:04:28.896798 5492 http.go:37] curl https://ip.jsb.workers.dev I0114 09:04:28.989900 5492 up.go:167] /home/prow/go/src/k8s.io/kops/_rundir/2fefd7c4-93ea-11ed-bd5d-72eebb4d772a/kops create cluster --name e2e-e2e-kops-grid-kubenet-flatcar-k23-ko25.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.23.15 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-kubenet-flatcar-k23-ko25.test-cncf-aws.k8s.io/id_ed25519.pub --set cluster.spec.nodePortAccess=0.0.0.0/0 --image=075585003325/Flatcar-beta-3432.1.0-hvm --channel=alpha --networking=kubenet --container-runtime=containerd --admin-access 35.184.42.228/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones us-west-2a --master-size c5.large I0114 09:04:28.989943 5492 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/2fefd7c4-93ea-11ed-bd5d-72eebb4d772a/kops create cluster --name e2e-e2e-kops-grid-kubenet-flatcar-k23-ko25.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.23.15 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-kubenet-flatcar-k23-ko25.test-cncf-aws.k8s.io/id_ed25519.pub --set cluster.spec.nodePortAccess=0.0.0.0/0 --image=075585003325/Flatcar-beta-3432.1.0-hvm --channel=alpha --networking=kubenet --container-runtime=containerd --admin-access 35.184.42.228/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones us-west-2a --master-size c5.large I0114 09:04:29.043920 5535 create_cluster.go:831] Using SSH public key: /tmp/kops/e2e-e2e-kops-grid-kubenet-flatcar-k23-ko25.test-cncf-aws.k8s.io/id_ed25519.pub I0114 09:04:29.634530 5535 new_cluster.go:1279] Cloud Provider ID = aws I0114 09:04:30.172512 5535 subnets.go:185] Assigned CIDR 172.20.32.0/19 to subnet us-west-2a ... skipping 528 lines ... NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0114 09:05:11.027827 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0114 09:05:21.065614 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0114 09:05:31.100280 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0114 09:05:41.136284 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0114 09:05:51.188128 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0114 09:06:01.240622 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0114 09:06:11.293116 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0114 09:06:21.344856 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0114 09:06:31.389588 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0114 09:06:41.432084 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0114 09:06:51.467553 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0114 09:07:01.514285 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0114 09:07:11.550302 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0114 09:07:21.589700 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0114 09:07:31.627429 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0114 09:07:41.676410 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0114 09:07:51.711620 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0114 09:08:01.761633 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0114 09:08:11.795582 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0114 09:08:21.842099 5575 validate_cluster.go:232] (will retry): cluster not yet healthy W0114 09:09:01.877263 5575 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://api.e2e-e2e-kops-grid-kubenet-flatcar-k23-ko25.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 203.0.113.123:443: i/o timeout INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a NODE STATUS ... skipping 125 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Node ip-172-20-34-174.us-west-2.compute.internal node "ip-172-20-34-174.us-west-2.compute.internal" of role "node" is not ready Validation Failed W0114 09:10:45.617980 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Node ip-172-20-34-174.us-west-2.compute.internal node "ip-172-20-34-174.us-west-2.compute.internal" of role "node" is not ready Validation Failed W0114 09:10:57.119081 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Node ip-172-20-34-174.us-west-2.compute.internal node "ip-172-20-34-174.us-west-2.compute.internal" of role "node" is not ready Validation Failed W0114 09:11:08.537745 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 52 lines ... VALIDATION ERRORS KIND NAME MESSAGE Node ip-172-20-53-14.us-west-2.compute.internal node "ip-172-20-53-14.us-west-2.compute.internal" of role "node" is not ready Node ip-172-20-55-194.us-west-2.compute.internal node "ip-172-20-55-194.us-west-2.compute.internal" of role "node" is not ready Validation Failed W0114 09:11:54.662681 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Node ip-172-20-53-14.us-west-2.compute.internal node "ip-172-20-53-14.us-west-2.compute.internal" of role "node" is not ready Node ip-172-20-55-194.us-west-2.compute.internal node "ip-172-20-55-194.us-west-2.compute.internal" of role "node" is not ready Validation Failed W0114 09:12:06.109978 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Node ip-172-20-53-14.us-west-2.compute.internal node "ip-172-20-53-14.us-west-2.compute.internal" of role "node" is not ready Node ip-172-20-55-194.us-west-2.compute.internal node "ip-172-20-55-194.us-west-2.compute.internal" of role "node" is not ready Validation Failed W0114 09:12:17.697066 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 34 lines ... ip-172-20-55-194.us-west-2.compute.internal node True ip-172-20-55-39.us-west-2.compute.internal node True ip-172-20-60-45.us-west-2.compute.internal master True Your cluster e2e-e2e-kops-grid-kubenet-flatcar-k23-ko25.test-cncf-aws.k8s.io is ready I0114 09:12:52.033874 5575 validate_cluster.go:220] (will retry): cluster passed validation 3 consecutive times W0114 09:13:02.153659 5575 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://api.e2e-e2e-kops-grid-kubenet-flatcar-k23-ko25.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 35.90.24.117:443: connect: connection refused W0114 09:13:12.269709 5575 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://api.e2e-e2e-kops-grid-kubenet-flatcar-k23-ko25.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 35.90.24.117:443: connect: connection refused W0114 09:13:37.855074 5575 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://api.e2e-e2e-kops-grid-kubenet-flatcar-k23-ko25.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 35.90.24.117:443: connect: connection refused INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a NODE STATUS ... skipping 8 lines ... KIND NAME MESSAGE Node ip-172-20-60-45.us-west-2.compute.internal node "ip-172-20-60-45.us-west-2.compute.internal" of role "master" is not ready Pod kube-system/dns-controller-669d8ccd4f-fjmx8 system-cluster-critical pod "dns-controller-669d8ccd4f-fjmx8" is not ready (dns-controller) Pod kube-system/ebs-csi-node-hxj5c system-node-critical pod "ebs-csi-node-hxj5c" is not ready (ebs-plugin,liveness-probe,node-driver-registrar) Pod kube-system/kops-controller-s5vxq system-cluster-critical pod "kops-controller-s5vxq" is not ready (kops-controller) Validation Failed W0114 09:13:50.315441 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/ebs-csi-controller-7cc9f4d6f7-mn277 system-cluster-critical pod "ebs-csi-controller-7cc9f4d6f7-mn277" is not ready (ebs-plugin) Pod kube-system/kube-controller-manager-ip-172-20-60-45.us-west-2.compute.internal system-cluster-critical pod "kube-controller-manager-ip-172-20-60-45.us-west-2.compute.internal" is not ready (kube-controller-manager) Validation Failed W0114 09:14:01.727302 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 128 lines ... VALIDATION ERRORS KIND NAME MESSAGE Node ip-172-20-55-39.us-west-2.compute.internal node "ip-172-20-55-39.us-west-2.compute.internal" of role "node" is not ready Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Pod kube-system/kube-proxy-ip-172-20-55-39.us-west-2.compute.internal system-node-critical pod "kube-proxy-ip-172-20-55-39.us-west-2.compute.internal" is not ready (kube-proxy) Validation Failed W0114 09:15:45.031481 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 9 lines ... KIND NAME MESSAGE Node ip-172-20-55-39.us-west-2.compute.internal node "ip-172-20-55-39.us-west-2.compute.internal" of role "node" is not ready Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Pod kube-system/ebs-csi-node-zvfpg system-node-critical pod "ebs-csi-node-zvfpg" is pending Pod kube-system/kube-proxy-ip-172-20-55-39.us-west-2.compute.internal system-node-critical pod "kube-proxy-ip-172-20-55-39.us-west-2.compute.internal" is not ready (kube-proxy) Validation Failed W0114 09:15:56.582076 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 8 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Pod kube-system/ebs-csi-node-zvfpg system-node-critical pod "ebs-csi-node-zvfpg" is pending Pod kube-system/kube-proxy-ip-172-20-55-39.us-west-2.compute.internal system-node-critical pod "kube-proxy-ip-172-20-55-39.us-west-2.compute.internal" is not ready (kube-proxy) Validation Failed W0114 09:16:08.226689 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:16:19.694325 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:16:31.106040 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:16:42.557453 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:16:54.022979 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:17:05.529916 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:17:17.001026 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:17:28.369072 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:17:40.072313 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:17:51.518994 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:18:03.262071 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:18:14.619189 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:18:26.057792 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:18:37.519102 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:18:49.060367 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:19:00.411310 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:19:11.917871 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:19:23.361327 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:19:34.680637 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:19:46.071717 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:19:57.480996 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:20:08.981324 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:20:20.467110 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:20:31.932664 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:20:43.293757 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:20:54.627079 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:21:06.137510 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:21:17.558904 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:21:28.986479 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:21:40.624463 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:21:52.032389 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:22:03.486429 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:22:14.986806 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:22:26.339077 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:22:37.809805 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:22:49.207608 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:23:00.663867 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:23:12.109675 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:23:23.620680 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:23:35.079339 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:23:46.426959 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:23:58.036203 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:24:09.777734 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:24:21.215610 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:24:32.778030 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:24:44.164782 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:24:55.598645 5575 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 6 lines ... ip-172-20-60-45.us-west-2.compute.internal master True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-autoscaler-6bc4c99775-rbmnb system-cluster-critical pod "coredns-autoscaler-6bc4c99775-rbmnb" is not ready (autoscaler) Validation Failed W0114 09:25:07.131012 5575 validate_cluster.go:232] (will retry): cluster not yet healthy Error: Validation failed: wait time exceeded during validation I0114 09:25:17.140381 5492 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/2fefd7c4-93ea-11ed-bd5d-72eebb4d772a/kops toolbox dump --name e2e-e2e-kops-grid-kubenet-flatcar-k23-ko25.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-kubenet-flatcar-k23-ko25.test-cncf-aws.k8s.io/id_ed25519 --ssh-user core I0114 09:25:17.140504 5492 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/2fefd7c4-93ea-11ed-bd5d-72eebb4d772a/kops toolbox dump --name e2e-e2e-kops-grid-kubenet-flatcar-k23-ko25.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-kubenet-flatcar-k23-ko25.test-cncf-aws.k8s.io/id_ed25519 --ssh-user core 2023/01/14 09:25:35 Dumping node ip-172-20-34-174.us-west-2.compute.internal 2023/01/14 09:25:38 Dumping node ip-172-20-53-14.us-west-2.compute.internal 2023/01/14 09:25:41 Dumping node ip-172-20-55-194.us-west-2.compute.internal 2023/01/14 09:25:44 Dumping node ip-172-20-55-39.us-west-2.compute.internal ... skipping 275 lines ... route-table:rtb-00534647b8156fcf0 ok vpc:vpc-0b55fe2c257ee7e7b ok dhcp-options:dopt-080cca3c62b416892 ok Deleted kubectl config for e2e-e2e-kops-grid-kubenet-flatcar-k23-ko25.test-cncf-aws.k8s.io Deleted cluster: "e2e-e2e-kops-grid-kubenet-flatcar-k23-ko25.test-cncf-aws.k8s.io" Error: exit status 1 + EXIT_VALUE=1 + set +o xtrace