e2e-kops-grid-cilium-eni-amzn2-k23 #1617886885026205696
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 1 failed / 1 succeeded |
| Started | |
| Elapsed | 19m24s |
| Revision | master |
exit status 1
from junit_runner.xml
Filter through log files | View test history on testgrid
kubetest2 Down
... skipping 135 lines ... I0124 14:09:48.125864 5498 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt I0124 14:09:48.128047 5498 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/1.27.0-alpha.2+v1.27.0-alpha.1-260-g68705f39c9/linux/amd64/kops I0124 14:09:48.801104 5498 local.go:42] ⚙️ ssh-keygen -t ed25519 -N -q -f /tmp/kops/e2e-e2e-kops-grid-cilium-eni-amzn2-k23.test-cncf-aws.k8s.io/id_ed25519 I0124 14:09:48.816228 5498 up.go:44] Cleaning up any leaked resources from previous cluster I0124 14:09:48.816354 5498 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/7a91f7b7-9bf0-11ed-b10d-8a774b882db2/kops toolbox dump --name e2e-e2e-kops-grid-cilium-eni-amzn2-k23.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-eni-amzn2-k23.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ec2-user I0124 14:09:48.816372 5498 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/7a91f7b7-9bf0-11ed-b10d-8a774b882db2/kops toolbox dump --name e2e-e2e-kops-grid-cilium-eni-amzn2-k23.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-eni-amzn2-k23.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ec2-user Error: Cluster.kops.k8s.io "e2e-e2e-kops-grid-cilium-eni-amzn2-k23.test-cncf-aws.k8s.io" not found W0124 14:09:49.341218 5498 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1 I0124 14:09:49.341259 5498 down.go:48] /home/prow/go/src/k8s.io/kops/_rundir/7a91f7b7-9bf0-11ed-b10d-8a774b882db2/kops delete cluster --name e2e-e2e-kops-grid-cilium-eni-amzn2-k23.test-cncf-aws.k8s.io --yes I0124 14:09:49.341270 5498 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/7a91f7b7-9bf0-11ed-b10d-8a774b882db2/kops delete cluster --name e2e-e2e-kops-grid-cilium-eni-amzn2-k23.test-cncf-aws.k8s.io --yes Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-e2e-kops-grid-cilium-eni-amzn2-k23.test-cncf-aws.k8s.io" not found I0124 14:09:49.868748 5498 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip 2023/01/24 14:09:49 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 I0124 14:09:49.884491 5498 http.go:37] curl https://ip.jsb.workers.dev I0124 14:09:49.981884 5498 up.go:167] /home/prow/go/src/k8s.io/kops/_rundir/7a91f7b7-9bf0-11ed-b10d-8a774b882db2/kops create cluster --name e2e-e2e-kops-grid-cilium-eni-amzn2-k23.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.23.16 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-cilium-eni-amzn2-k23.test-cncf-aws.k8s.io/id_ed25519.pub --set cluster.spec.nodePortAccess=0.0.0.0/0 --image=137112412989/amzn2-ami-kernel-5.10-hvm-2.0.20221210.1-x86_64-gp2 --channel=alpha --networking=cilium-eni --container-runtime=containerd --admin-access 35.202.151.134/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones us-east-2a --master-size c5.large I0124 14:09:49.981924 5498 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/7a91f7b7-9bf0-11ed-b10d-8a774b882db2/kops create cluster --name e2e-e2e-kops-grid-cilium-eni-amzn2-k23.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.23.16 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-cilium-eni-amzn2-k23.test-cncf-aws.k8s.io/id_ed25519.pub --set cluster.spec.nodePortAccess=0.0.0.0/0 --image=137112412989/amzn2-ami-kernel-5.10-hvm-2.0.20221210.1-x86_64-gp2 --channel=alpha --networking=cilium-eni --container-runtime=containerd --admin-access 35.202.151.134/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones us-east-2a --master-size c5.large I0124 14:09:50.038271 5539 create_cluster.go:882] Using SSH public key: /tmp/kops/e2e-e2e-kops-grid-cilium-eni-amzn2-k23.test-cncf-aws.k8s.io/id_ed25519.pub I0124 14:09:50.555572 5539 new_cluster.go:1338] Cloud Provider ID: "aws" I0124 14:09:51.028443 5539 subnets.go:185] Assigned CIDR 172.20.32.0/19 to subnet us-east-2a ... skipping 552 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 control plane node 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 W0124 14:10:32.887170 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 control plane node 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 W0124 14:10:42.928898 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 control plane node 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 W0124 14:10:52.963857 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 control plane node 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 W0124 14:11:03.003506 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 control plane node 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 W0124 14:11:13.040130 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 control plane node 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 W0124 14:11:23.075384 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 control plane node 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 W0124 14:11:33.111714 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 control plane node 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 W0124 14:11:43.150644 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 control plane node 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 W0124 14:11:53.185240 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 control plane node 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 W0124 14:12:03.234310 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 control plane node 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 W0124 14:12:13.283839 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 control plane node 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 W0124 14:12:23.316401 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 control plane node 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 W0124 14:12:33.357261 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 control plane node 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 W0124 14:12:43.394481 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 control plane node 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 W0124 14:12:53.426264 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 control plane node 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 W0124 14:13:03.461174 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 control plane node 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 W0124 14:13:13.497087 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 control plane node 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 W0124 14:13:23.534756 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 control plane node 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 W0124 14:13:33.577123 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 control plane node 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 W0124 14:13:43.611238 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 control plane node 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 W0124 14:13:53.646061 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 control plane node 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 W0124 14:14:03.692510 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 control plane node 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 W0124 14:14:13.727338 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 control plane node 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 W0124 14:14:23.767692 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 control plane node 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 W0124 14:14:33.807441 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 control plane node 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 W0124 14:14:43.846557 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 control plane node 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 W0124 14:14:53.884895 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 control plane node 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 W0124 14:15:03.920489 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 11 lines ... Node ip-172-20-51-61.us-east-2.compute.internal control-plane node "ip-172-20-51-61.us-east-2.compute.internal" is missing kube-scheduler pod Pod kube-system/cilium-ctl7b system-node-critical pod "cilium-ctl7b" is not ready (cilium-agent) Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9nskx system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9nskx" is pending Pod kube-system/ebs-csi-node-pnscj system-node-critical pod "ebs-csi-node-pnscj" is pending Validation Failed W0124 14:15:15.186684 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 12 lines ... Pod kube-system/cilium-ctl7b system-node-critical pod "cilium-ctl7b" is not ready (cilium-agent) Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9nskx system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9nskx" is pending Pod kube-system/ebs-csi-node-pnscj system-node-critical pod "ebs-csi-node-pnscj" is pending Pod kube-system/kube-controller-manager-ip-172-20-51-61.us-east-2.compute.internal system-cluster-critical pod "kube-controller-manager-ip-172-20-51-61.us-east-2.compute.internal" is pending Validation Failed W0124 14:15:26.187684 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 10 lines ... Node ip-172-20-51-61.us-east-2.compute.internal control-plane node "ip-172-20-51-61.us-east-2.compute.internal" is missing kube-scheduler pod Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9nskx system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9nskx" is pending Pod kube-system/ebs-csi-node-pnscj system-node-critical pod "ebs-csi-node-pnscj" is pending Pod kube-system/kube-scheduler-ip-172-20-51-61.us-east-2.compute.internal system-cluster-critical pod "kube-scheduler-ip-172-20-51-61.us-east-2.compute.internal" is pending Validation Failed W0124 14:15:37.177137 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 18 lines ... Pod kube-system/coredns-autoscaler-557ccb4c66-9nskx system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9nskx" is pending Pod kube-system/ebs-csi-node-5v2wj system-node-critical pod "ebs-csi-node-5v2wj" is pending Pod kube-system/ebs-csi-node-lcbjn system-node-critical pod "ebs-csi-node-lcbjn" is pending Pod kube-system/ebs-csi-node-n6wd6 system-node-critical pod "ebs-csi-node-n6wd6" is pending Pod kube-system/ebs-csi-node-rrfrp system-node-critical pod "ebs-csi-node-rrfrp" is pending Validation Failed W0124 14:15:48.044801 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 19 lines ... Pod kube-system/coredns-autoscaler-557ccb4c66-9nskx system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9nskx" is pending Pod kube-system/ebs-csi-node-5v2wj system-node-critical pod "ebs-csi-node-5v2wj" is pending Pod kube-system/ebs-csi-node-lcbjn system-node-critical pod "ebs-csi-node-lcbjn" is pending Pod kube-system/ebs-csi-node-n6wd6 system-node-critical pod "ebs-csi-node-n6wd6" is pending Pod kube-system/ebs-csi-node-rrfrp system-node-critical pod "ebs-csi-node-rrfrp" is pending Validation Failed W0124 14:15:59.091108 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 13 lines ... Pod kube-system/coredns-autoscaler-557ccb4c66-9nskx system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9nskx" is pending Pod kube-system/ebs-csi-node-5v2wj system-node-critical pod "ebs-csi-node-5v2wj" is pending Pod kube-system/ebs-csi-node-lcbjn system-node-critical pod "ebs-csi-node-lcbjn" is pending Pod kube-system/ebs-csi-node-n6wd6 system-node-critical pod "ebs-csi-node-n6wd6" is pending Pod kube-system/ebs-csi-node-rrfrp system-node-critical pod "ebs-csi-node-rrfrp" is pending Validation Failed W0124 14:16:10.073513 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 10 lines ... Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Pod kube-system/coredns-867df8f45c-ffr46 system-cluster-critical pod "coredns-867df8f45c-ffr46" is pending Pod kube-system/ebs-csi-node-5v2wj system-node-critical pod "ebs-csi-node-5v2wj" is pending Pod kube-system/ebs-csi-node-lcbjn system-node-critical pod "ebs-csi-node-lcbjn" is pending Pod kube-system/ebs-csi-node-n6wd6 system-node-critical pod "ebs-csi-node-n6wd6" is pending Validation Failed W0124 14:16:21.070460 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 6 lines ... ip-172-20-58-18.us-east-2.compute.internal node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Validation Failed W0124 14:16:32.080621 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 6 lines ... ip-172-20-58-18.us-east-2.compute.internal node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Validation Failed W0124 14:16:43.012192 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 6 lines ... ip-172-20-58-18.us-east-2.compute.internal node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Validation Failed W0124 14:16:53.863720 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 6 lines ... ip-172-20-58-18.us-east-2.compute.internal node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Validation Failed W0124 14:17:04.707654 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 6 lines ... ip-172-20-58-18.us-east-2.compute.internal node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Validation Failed W0124 14:17:15.649433 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 6 lines ... ip-172-20-58-18.us-east-2.compute.internal node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Validation Failed W0124 14:17:26.651635 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 6 lines ... ip-172-20-58-18.us-east-2.compute.internal node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Validation Failed W0124 14:17:37.589843 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 6 lines ... ip-172-20-58-18.us-east-2.compute.internal node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Validation Failed W0124 14:17:48.529309 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 6 lines ... ip-172-20-58-18.us-east-2.compute.internal node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Validation Failed W0124 14:17:59.523445 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 6 lines ... ip-172-20-58-18.us-east-2.compute.internal node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Validation Failed W0124 14:18:10.439557 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 6 lines ... ip-172-20-58-18.us-east-2.compute.internal node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Validation Failed W0124 14:18:21.385754 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 6 lines ... ip-172-20-58-18.us-east-2.compute.internal node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Validation Failed W0124 14:18:32.301819 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 6 lines ... ip-172-20-58-18.us-east-2.compute.internal node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Validation Failed W0124 14:18:43.206291 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 6 lines ... ip-172-20-58-18.us-east-2.compute.internal node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Validation Failed W0124 14:18:54.198711 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 6 lines ... ip-172-20-58-18.us-east-2.compute.internal node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Validation Failed W0124 14:19:05.271006 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 6 lines ... ip-172-20-58-18.us-east-2.compute.internal node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Validation Failed W0124 14:19:16.310343 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 6 lines ... ip-172-20-58-18.us-east-2.compute.internal node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Validation Failed W0124 14:19:27.237478 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 6 lines ... ip-172-20-58-18.us-east-2.compute.internal node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Validation Failed W0124 14:19:38.234734 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 6 lines ... ip-172-20-58-18.us-east-2.compute.internal node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Validation Failed W0124 14:19:49.145049 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 6 lines ... ip-172-20-58-18.us-east-2.compute.internal node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Validation Failed W0124 14:20:00.094934 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 6 lines ... ip-172-20-58-18.us-east-2.compute.internal node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Validation Failed W0124 14:20:11.323909 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 6 lines ... ip-172-20-58-18.us-east-2.compute.internal node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Validation Failed W0124 14:20:22.293552 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 6 lines ... ip-172-20-58-18.us-east-2.compute.internal node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Validation Failed W0124 14:20:33.157072 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 6 lines ... ip-172-20-58-18.us-east-2.compute.internal node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Validation Failed W0124 14:20:44.087871 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 6 lines ... ip-172-20-58-18.us-east-2.compute.internal node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Validation Failed W0124 14:20:55.031333 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 6 lines ... ip-172-20-58-18.us-east-2.compute.internal node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Validation Failed W0124 14:21:05.962972 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 6 lines ... ip-172-20-58-18.us-east-2.compute.internal node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Validation Failed W0124 14:21:16.988124 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 6 lines ... ip-172-20-58-18.us-east-2.compute.internal node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Validation Failed W0124 14:21:27.872695 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 6 lines ... ip-172-20-58-18.us-east-2.compute.internal node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Validation Failed W0124 14:21:38.825449 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 6 lines ... ip-172-20-58-18.us-east-2.compute.internal node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Validation Failed W0124 14:21:49.882753 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 6 lines ... ip-172-20-58-18.us-east-2.compute.internal node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Validation Failed W0124 14:22:00.914823 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 6 lines ... ip-172-20-58-18.us-east-2.compute.internal node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Validation Failed W0124 14:22:11.775081 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Pod kube-system/ebs-csi-node-rrfrp system-node-critical pod "ebs-csi-node-rrfrp" is not ready (ebs-plugin) Validation Failed W0124 14:22:22.701263 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Pod kube-system/ebs-csi-node-rrfrp system-node-critical pod "ebs-csi-node-rrfrp" is not ready (ebs-plugin) Validation Failed W0124 14:22:33.525302 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Pod kube-system/ebs-csi-node-rrfrp system-node-critical pod "ebs-csi-node-rrfrp" is not ready (ebs-plugin) Validation Failed W0124 14:22:44.392267 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Pod kube-system/ebs-csi-node-rrfrp system-node-critical pod "ebs-csi-node-rrfrp" is not ready (ebs-plugin) Validation Failed W0124 14:22:55.372086 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Pod kube-system/ebs-csi-node-rrfrp system-node-critical pod "ebs-csi-node-rrfrp" is not ready (ebs-plugin) Validation Failed W0124 14:23:06.272382 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Pod kube-system/ebs-csi-node-rrfrp system-node-critical pod "ebs-csi-node-rrfrp" is not ready (ebs-plugin) Validation Failed W0124 14:23:17.185200 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Pod kube-system/ebs-csi-node-rrfrp system-node-critical pod "ebs-csi-node-rrfrp" is not ready (ebs-plugin) Validation Failed W0124 14:23:28.127651 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Pod kube-system/ebs-csi-node-rrfrp system-node-critical pod "ebs-csi-node-rrfrp" is not ready (ebs-plugin) Validation Failed W0124 14:23:38.942577 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 6 lines ... ip-172-20-58-18.us-east-2.compute.internal node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Validation Failed W0124 14:23:49.889780 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 6 lines ... ip-172-20-58-18.us-east-2.compute.internal node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Validation Failed W0124 14:24:00.835500 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 6 lines ... ip-172-20-58-18.us-east-2.compute.internal node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Validation Failed W0124 14:24:11.787771 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 6 lines ... ip-172-20-58-18.us-east-2.compute.internal node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Validation Failed W0124 14:24:22.724284 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 6 lines ... ip-172-20-58-18.us-east-2.compute.internal node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Validation Failed W0124 14:24:33.655577 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Pod kube-system/ebs-csi-node-rrfrp system-node-critical pod "ebs-csi-node-rrfrp" is not ready (ebs-plugin) Validation Failed W0124 14:24:44.593165 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Pod kube-system/ebs-csi-node-rrfrp system-node-critical pod "ebs-csi-node-rrfrp" is not ready (ebs-plugin) Validation Failed W0124 14:24:55.608475 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Pod kube-system/ebs-csi-node-rrfrp system-node-critical pod "ebs-csi-node-rrfrp" is not ready (ebs-plugin) Validation Failed W0124 14:25:06.571367 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Pod kube-system/ebs-csi-node-rrfrp system-node-critical pod "ebs-csi-node-rrfrp" is not ready (ebs-plugin) Validation Failed W0124 14:25:17.411416 5581 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-us-east-2a ControlPlane c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-867df8f45c-4swk6 system-cluster-critical pod "coredns-867df8f45c-4swk6" is not ready (coredns) Pod kube-system/ebs-csi-node-rrfrp system-node-critical pod "ebs-csi-node-rrfrp" is not ready (ebs-plugin) Validation Failed W0124 14:25:28.372338 5581 validate_cluster.go:232] (will retry): cluster not yet healthy Error: validation failed: wait time exceeded during validation I0124 14:25:38.382057 5498 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/7a91f7b7-9bf0-11ed-b10d-8a774b882db2/kops toolbox dump --name e2e-e2e-kops-grid-cilium-eni-amzn2-k23.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-eni-amzn2-k23.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ec2-user I0124 14:25:38.382115 5498 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/7a91f7b7-9bf0-11ed-b10d-8a774b882db2/kops toolbox dump --name e2e-e2e-kops-grid-cilium-eni-amzn2-k23.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-eni-amzn2-k23.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ec2-user 2023/01/24 14:25:58 Dumping node ip-172-20-32-72.us-east-2.compute.internal 2023/01/24 14:26:00 error dumping node ip-172-20-32-72.us-east-2.compute.internal: error executing command "sysctl -a": Process exited with status 127 2023/01/24 14:26:00 Dumping node ip-172-20-51-150.us-east-2.compute.internal 2023/01/24 14:26:02 error dumping node ip-172-20-51-150.us-east-2.compute.internal: error executing command "sysctl -a": Process exited with status 127 2023/01/24 14:26:02 Dumping node ip-172-20-51-61.us-east-2.compute.internal 2023/01/24 14:26:05 error dumping node ip-172-20-51-61.us-east-2.compute.internal: error executing command "sysctl -a": Process exited with status 127 2023/01/24 14:26:05 Dumping node ip-172-20-52-20.us-east-2.compute.internal 2023/01/24 14:26:07 error dumping node ip-172-20-52-20.us-east-2.compute.internal: error executing command "sysctl -a": Process exited with status 127 2023/01/24 14:26:07 Dumping node ip-172-20-58-18.us-east-2.compute.internal 2023/01/24 14:26:09 error dumping node ip-172-20-58-18.us-east-2.compute.internal: error executing command "sysctl -a": Process exited with status 127 I0124 14:26:09.156131 5498 dumplogs.go:79] /home/prow/go/src/k8s.io/kops/_rundir/7a91f7b7-9bf0-11ed-b10d-8a774b882db2/kops get cluster --name e2e-e2e-kops-grid-cilium-eni-amzn2-k23.test-cncf-aws.k8s.io -o yaml I0124 14:26:09.156197 5498 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/7a91f7b7-9bf0-11ed-b10d-8a774b882db2/kops get cluster --name e2e-e2e-kops-grid-cilium-eni-amzn2-k23.test-cncf-aws.k8s.io -o yaml I0124 14:26:09.693756 5498 dumplogs.go:79] /home/prow/go/src/k8s.io/kops/_rundir/7a91f7b7-9bf0-11ed-b10d-8a774b882db2/kops get instancegroups --name e2e-e2e-kops-grid-cilium-eni-amzn2-k23.test-cncf-aws.k8s.io -o yaml I0124 14:26:09.693790 5498 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/7a91f7b7-9bf0-11ed-b10d-8a774b882db2/kops get instancegroups --name e2e-e2e-kops-grid-cilium-eni-amzn2-k23.test-cncf-aws.k8s.io -o yaml I0124 14:26:10.515523 5498 dumplogs.go:98] kubectl cluster-info dump --all-namespaces -o yaml --output-directory /logs/artifacts/cluster-info I0124 14:26:10.515579 5498 local.go:42] ⚙️ kubectl cluster-info dump --all-namespaces -o yaml --output-directory /logs/artifacts/cluster-info ... skipping 275 lines ... route-table:rtb-013fba200dd9f446e ok vpc:vpc-0ac9fefb5fea089c6 ok dhcp-options:dopt-01303843cb84317b7 ok Deleted kubectl config for e2e-e2e-kops-grid-cilium-eni-amzn2-k23.test-cncf-aws.k8s.io Deleted cluster: "e2e-e2e-kops-grid-cilium-eni-amzn2-k23.test-cncf-aws.k8s.io" Error: exit status 1 + EXIT_VALUE=1 + set +o xtrace