e2e-kops-grid-cilium-eni-amzn2-k26 #1618658229233913856
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 1 failed / 1 succeeded |
| Started | |
| Elapsed | 20m16s |
| Revision | master |
exit status 1
from junit_runner.xml
Filter through log files | View test history on testgrid
kubetest2 Down
... skipping 135 lines ... I0126 17:14:39.449902 5526 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt I0126 17:14:39.452616 5526 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/1.27.0-alpha.2+v1.27.0-alpha.1-274-gbded65a685/linux/amd64/kops I0126 17:14:40.436513 5526 local.go:42] ⚙️ ssh-keygen -t ed25519 -N -q -f /tmp/kops/e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io/id_ed25519 I0126 17:14:40.450196 5526 up.go:44] Cleaning up any leaked resources from previous cluster I0126 17:14:40.450495 5526 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/a92bfbc5-9d9c-11ed-b1bb-1299ca1e1805/kops toolbox dump --name e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ec2-user I0126 17:14:40.450578 5526 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/a92bfbc5-9d9c-11ed-b1bb-1299ca1e1805/kops toolbox dump --name e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ec2-user Error: Cluster.kops.k8s.io "e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io" not found W0126 17:14:40.973704 5526 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1 I0126 17:14:40.973751 5526 down.go:48] /home/prow/go/src/k8s.io/kops/_rundir/a92bfbc5-9d9c-11ed-b1bb-1299ca1e1805/kops delete cluster --name e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io --yes I0126 17:14:40.973765 5526 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/a92bfbc5-9d9c-11ed-b1bb-1299ca1e1805/kops delete cluster --name e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io --yes Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io" not found I0126 17:14:41.459132 5526 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip 2023/01/26 17:14:41 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 I0126 17:14:41.472461 5526 http.go:37] curl https://ip.jsb.workers.dev I0126 17:14:41.594853 5526 up.go:167] /home/prow/go/src/k8s.io/kops/_rundir/a92bfbc5-9d9c-11ed-b1bb-1299ca1e1805/kops create cluster --name e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.26.1 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-cilium-eni-amzn2-k26.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.188.33.172/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-southeast-2a --master-size c5.large I0126 17:14:41.594903 5526 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/a92bfbc5-9d9c-11ed-b1bb-1299ca1e1805/kops create cluster --name e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.26.1 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-cilium-eni-amzn2-k26.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.188.33.172/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-southeast-2a --master-size c5.large I0126 17:14:41.644199 5568 create_cluster.go:882] Using SSH public key: /tmp/kops/e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io/id_ed25519.pub I0126 17:14:42.139847 5568 new_cluster.go:1338] Cloud Provider ID: "aws" I0126 17:14:43.635354 5568 subnets.go:185] Assigned CIDR 172.20.32.0/19 to subnet ap-southeast-2a ... skipping 511 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 W0126 17:15:22.759045 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-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 W0126 17:15:32.798731 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-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 W0126 17:15:42.832046 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-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 W0126 17:15:52.872981 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-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 W0126 17:16:02.929660 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-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 W0126 17:16:12.980466 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-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 W0126 17:16:23.031984 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-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 W0126 17:16:33.085050 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-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 W0126 17:16:43.125697 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-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 W0126 17:16:53.163253 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-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 W0126 17:17:03.208696 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-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 W0126 17:17:13.251465 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-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 W0126 17:17:23.293627 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-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 W0126 17:17:33.345959 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-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 W0126 17:17:43.382686 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-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 W0126 17:17:53.419443 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-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 W0126 17:18:03.463949 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-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 W0126 17:18:13.512929 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-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 W0126 17:18:23.566331 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-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 W0126 17:18:33.608533 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-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 W0126 17:18:43.641856 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-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 W0126 17:18:53.682739 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-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 W0126 17:19:03.747416 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-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 W0126 17:19:13.795822 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-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 W0126 17:19:23.830694 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-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 W0126 17:19:33.866478 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-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 W0126 17:19:43.912730 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-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 W0126 17:19:53.960590 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-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 W0126 17:20:04.016272 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-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 W0126 17:20:14.057302 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-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 W0126 17:20:24.095472 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-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 W0126 17:20:34.129887 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-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 W0126 17:20:44.169902 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-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 W0126 17:20:54.209640 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-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 W0126 17:21:04.249370 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-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 W0126 17:21:14.289856 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 11 lines ... Pod kube-system/cilium-l7nw5 system-node-critical pod "cilium-l7nw5" is not ready (cilium-agent) Pod kube-system/coredns-559769c974-llfq6 system-cluster-critical pod "coredns-559769c974-llfq6" is pending Pod kube-system/coredns-autoscaler-7cb5c5b969-sqcv2 system-cluster-critical pod "coredns-autoscaler-7cb5c5b969-sqcv2" is pending Pod kube-system/ebs-csi-node-6qc2l system-node-critical pod "ebs-csi-node-6qc2l" is pending Pod kube-system/etcd-manager-events-i-0bcf38121f68de400 system-cluster-critical pod "etcd-manager-events-i-0bcf38121f68de400" is pending Validation Failed W0126 17:21:28.865347 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 9 lines ... Machine i-0f94864916d76a630 machine "i-0f94864916d76a630" has not yet joined cluster Pod kube-system/cilium-l7nw5 system-node-critical pod "cilium-l7nw5" is not ready (cilium-agent) Pod kube-system/coredns-559769c974-llfq6 system-cluster-critical pod "coredns-559769c974-llfq6" is pending Pod kube-system/coredns-autoscaler-7cb5c5b969-sqcv2 system-cluster-critical pod "coredns-autoscaler-7cb5c5b969-sqcv2" is pending Pod kube-system/ebs-csi-node-6qc2l system-node-critical pod "ebs-csi-node-6qc2l" is pending Validation Failed W0126 17:21:41.945040 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 20 lines ... Pod kube-system/ebs-csi-node-4prtt system-node-critical pod "ebs-csi-node-4prtt" is pending Pod kube-system/ebs-csi-node-6qc2l system-node-critical pod "ebs-csi-node-6qc2l" is pending Pod kube-system/ebs-csi-node-fdv5w system-node-critical pod "ebs-csi-node-fdv5w" is pending Pod kube-system/ebs-csi-node-hprlm system-node-critical pod "ebs-csi-node-hprlm" is pending Pod kube-system/ebs-csi-node-lwnt7 system-node-critical pod "ebs-csi-node-lwnt7" is pending Validation Failed W0126 17:21:54.879100 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 17 lines ... Pod kube-system/coredns-autoscaler-7cb5c5b969-sqcv2 system-cluster-critical pod "coredns-autoscaler-7cb5c5b969-sqcv2" is pending Pod kube-system/ebs-csi-node-4prtt system-node-critical pod "ebs-csi-node-4prtt" is pending Pod kube-system/ebs-csi-node-fdv5w system-node-critical pod "ebs-csi-node-fdv5w" is pending Pod kube-system/ebs-csi-node-hprlm system-node-critical pod "ebs-csi-node-hprlm" is pending Pod kube-system/ebs-csi-node-lwnt7 system-node-critical pod "ebs-csi-node-lwnt7" is pending Validation Failed W0126 17:22:07.897950 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 11 lines ... Pod kube-system/coredns-autoscaler-7cb5c5b969-sqcv2 system-cluster-critical pod "coredns-autoscaler-7cb5c5b969-sqcv2" is pending Pod kube-system/ebs-csi-node-4prtt system-node-critical pod "ebs-csi-node-4prtt" is pending Pod kube-system/ebs-csi-node-fdv5w system-node-critical pod "ebs-csi-node-fdv5w" is pending Pod kube-system/ebs-csi-node-hprlm system-node-critical pod "ebs-csi-node-hprlm" is pending Pod kube-system/ebs-csi-node-lwnt7 system-node-critical pod "ebs-csi-node-lwnt7" is pending Validation Failed W0126 17:22:20.940513 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 11 lines ... Pod kube-system/coredns-559769c974-llfq6 system-cluster-critical pod "coredns-559769c974-llfq6" is not ready (coredns) Pod kube-system/ebs-csi-node-4prtt system-node-critical pod "ebs-csi-node-4prtt" is pending Pod kube-system/ebs-csi-node-fdv5w system-node-critical pod "ebs-csi-node-fdv5w" is pending Pod kube-system/ebs-csi-node-hprlm system-node-critical pod "ebs-csi-node-hprlm" is pending Pod kube-system/ebs-csi-node-lwnt7 system-node-critical pod "ebs-csi-node-lwnt7" is pending Validation Failed W0126 17:22:34.150493 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 6 lines ... i-0f94864916d76a630 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-llfq6 system-cluster-critical pod "coredns-559769c974-llfq6" is not ready (coredns) Validation Failed W0126 17:22:47.139700 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 6 lines ... i-0f94864916d76a630 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-llfq6 system-cluster-critical pod "coredns-559769c974-llfq6" is not ready (coredns) Validation Failed W0126 17:23:00.109799 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 6 lines ... i-0f94864916d76a630 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-llfq6 system-cluster-critical pod "coredns-559769c974-llfq6" is not ready (coredns) Validation Failed W0126 17:23:13.137583 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 6 lines ... i-0f94864916d76a630 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-llfq6 system-cluster-critical pod "coredns-559769c974-llfq6" is not ready (coredns) Validation Failed W0126 17:23:26.263661 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 6 lines ... i-0f94864916d76a630 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-llfq6 system-cluster-critical pod "coredns-559769c974-llfq6" is not ready (coredns) Validation Failed W0126 17:23:39.225933 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 6 lines ... i-0f94864916d76a630 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-llfq6 system-cluster-critical pod "coredns-559769c974-llfq6" is not ready (coredns) Validation Failed W0126 17:23:52.449885 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 6 lines ... i-0f94864916d76a630 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-llfq6 system-cluster-critical pod "coredns-559769c974-llfq6" is not ready (coredns) Validation Failed W0126 17:24:05.515344 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 6 lines ... i-0f94864916d76a630 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-llfq6 system-cluster-critical pod "coredns-559769c974-llfq6" is not ready (coredns) Validation Failed W0126 17:24:19.576801 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 6 lines ... i-0f94864916d76a630 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-llfq6 system-cluster-critical pod "coredns-559769c974-llfq6" is not ready (coredns) Validation Failed W0126 17:24:32.633934 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 6 lines ... i-0f94864916d76a630 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-llfq6 system-cluster-critical pod "coredns-559769c974-llfq6" is not ready (coredns) Validation Failed W0126 17:24:45.670535 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 6 lines ... i-0f94864916d76a630 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-llfq6 system-cluster-critical pod "coredns-559769c974-llfq6" is not ready (coredns) Validation Failed W0126 17:24:58.819872 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 6 lines ... i-0f94864916d76a630 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-llfq6 system-cluster-critical pod "coredns-559769c974-llfq6" is not ready (coredns) Validation Failed W0126 17:25:11.763111 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 6 lines ... i-0f94864916d76a630 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-llfq6 system-cluster-critical pod "coredns-559769c974-llfq6" is not ready (coredns) Validation Failed W0126 17:25:25.387736 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 6 lines ... i-0f94864916d76a630 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-llfq6 system-cluster-critical pod "coredns-559769c974-llfq6" is not ready (coredns) Validation Failed W0126 17:25:38.304768 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 6 lines ... i-0f94864916d76a630 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-llfq6 system-cluster-critical pod "coredns-559769c974-llfq6" is not ready (coredns) Validation Failed W0126 17:25:51.303598 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 6 lines ... i-0f94864916d76a630 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-llfq6 system-cluster-critical pod "coredns-559769c974-llfq6" is not ready (coredns) Validation Failed W0126 17:26:04.277181 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 6 lines ... i-0f94864916d76a630 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-llfq6 system-cluster-critical pod "coredns-559769c974-llfq6" is not ready (coredns) Validation Failed W0126 17:26:17.250016 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 6 lines ... i-0f94864916d76a630 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-llfq6 system-cluster-critical pod "coredns-559769c974-llfq6" is not ready (coredns) Validation Failed W0126 17:26:30.233382 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 6 lines ... i-0f94864916d76a630 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-llfq6 system-cluster-critical pod "coredns-559769c974-llfq6" is not ready (coredns) Validation Failed W0126 17:26:43.290893 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 6 lines ... i-0f94864916d76a630 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-llfq6 system-cluster-critical pod "coredns-559769c974-llfq6" is not ready (coredns) Validation Failed W0126 17:26:56.215617 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 6 lines ... i-0f94864916d76a630 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-llfq6 system-cluster-critical pod "coredns-559769c974-llfq6" is not ready (coredns) Validation Failed W0126 17:27:09.194297 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 6 lines ... i-0f94864916d76a630 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-llfq6 system-cluster-critical pod "coredns-559769c974-llfq6" is not ready (coredns) Validation Failed W0126 17:27:22.215341 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 6 lines ... i-0f94864916d76a630 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-llfq6 system-cluster-critical pod "coredns-559769c974-llfq6" is not ready (coredns) Validation Failed W0126 17:27:35.284808 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 6 lines ... i-0f94864916d76a630 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-llfq6 system-cluster-critical pod "coredns-559769c974-llfq6" is not ready (coredns) Validation Failed W0126 17:27:48.184105 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 6 lines ... i-0f94864916d76a630 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-llfq6 system-cluster-critical pod "coredns-559769c974-llfq6" is not ready (coredns) Validation Failed W0126 17:28:01.163870 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 6 lines ... i-0f94864916d76a630 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-llfq6 system-cluster-critical pod "coredns-559769c974-llfq6" is not ready (coredns) Validation Failed W0126 17:28:14.144507 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 6 lines ... i-0f94864916d76a630 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-llfq6 system-cluster-critical pod "coredns-559769c974-llfq6" is not ready (coredns) Validation Failed W0126 17:28:27.104834 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-llfq6 system-cluster-critical pod "coredns-559769c974-llfq6" is not ready (coredns) Pod kube-system/ebs-csi-node-fdv5w system-node-critical pod "ebs-csi-node-fdv5w" is not ready (ebs-plugin) Validation Failed W0126 17:28:40.334698 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-llfq6 system-cluster-critical pod "coredns-559769c974-llfq6" is not ready (coredns) Pod kube-system/ebs-csi-node-fdv5w system-node-critical pod "ebs-csi-node-fdv5w" is not ready (ebs-plugin) Validation Failed W0126 17:28:53.347865 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-llfq6 system-cluster-critical pod "coredns-559769c974-llfq6" is not ready (coredns) Pod kube-system/ebs-csi-node-fdv5w system-node-critical pod "ebs-csi-node-fdv5w" is not ready (ebs-plugin) Validation Failed W0126 17:29:06.255648 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-llfq6 system-cluster-critical pod "coredns-559769c974-llfq6" is not ready (coredns) Pod kube-system/ebs-csi-node-fdv5w system-node-critical pod "ebs-csi-node-fdv5w" is not ready (ebs-plugin) Validation Failed W0126 17:29:19.811116 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-llfq6 system-cluster-critical pod "coredns-559769c974-llfq6" is not ready (coredns) Pod kube-system/ebs-csi-node-fdv5w system-node-critical pod "ebs-csi-node-fdv5w" is not ready (ebs-plugin) Validation Failed W0126 17:29:32.835410 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-llfq6 system-cluster-critical pod "coredns-559769c974-llfq6" is not ready (coredns) Pod kube-system/ebs-csi-node-fdv5w system-node-critical pod "ebs-csi-node-fdv5w" is not ready (ebs-plugin) Validation Failed W0126 17:29:45.749245 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-llfq6 system-cluster-critical pod "coredns-559769c974-llfq6" is not ready (coredns) Pod kube-system/ebs-csi-node-fdv5w system-node-critical pod "ebs-csi-node-fdv5w" is not ready (ebs-plugin) Validation Failed W0126 17:29:58.672993 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 6 lines ... i-0f94864916d76a630 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-llfq6 system-cluster-critical pod "coredns-559769c974-llfq6" is not ready (coredns) Validation Failed W0126 17:30:11.730627 5609 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-southeast-2a ControlPlane c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 6 lines ... i-0f94864916d76a630 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-llfq6 system-cluster-critical pod "coredns-559769c974-llfq6" is not ready (coredns) Validation Failed W0126 17:30:24.700857 5609 validate_cluster.go:232] (will retry): cluster not yet healthy Error: validation failed: wait time exceeded during validation I0126 17:30:34.708409 5526 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/a92bfbc5-9d9c-11ed-b1bb-1299ca1e1805/kops toolbox dump --name e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ec2-user I0126 17:30:34.708461 5526 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/a92bfbc5-9d9c-11ed-b1bb-1299ca1e1805/kops toolbox dump --name e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ec2-user 2023/01/26 17:30:57 Dumping node i-0068ed0b9ff649b3e 2023/01/26 17:31:05 error dumping node i-0068ed0b9ff649b3e: error executing command "sysctl -a": Process exited with status 127 2023/01/26 17:31:05 Dumping node i-08ae091f616c03ce2 2023/01/26 17:31:14 error dumping node i-08ae091f616c03ce2: error executing command "sysctl -a": Process exited with status 127 2023/01/26 17:31:14 Dumping node i-0bcf38121f68de400 2023/01/26 17:31:26 error dumping node i-0bcf38121f68de400: error executing command "sysctl -a": Process exited with status 127 2023/01/26 17:31:26 Dumping node i-0ecb9dd962aeb39a1 2023/01/26 17:31:34 error dumping node i-0ecb9dd962aeb39a1: error executing command "sysctl -a": Process exited with status 127 2023/01/26 17:31:34 Dumping node i-0f94864916d76a630 2023/01/26 17:31:43 error dumping node i-0f94864916d76a630: error executing command "sysctl -a": Process exited with status 127 I0126 17:31:43.440735 5526 dumplogs.go:79] /home/prow/go/src/k8s.io/kops/_rundir/a92bfbc5-9d9c-11ed-b1bb-1299ca1e1805/kops get cluster --name e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io -o yaml I0126 17:31:43.440800 5526 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/a92bfbc5-9d9c-11ed-b1bb-1299ca1e1805/kops get cluster --name e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io -o yaml I0126 17:31:43.952738 5526 dumplogs.go:79] /home/prow/go/src/k8s.io/kops/_rundir/a92bfbc5-9d9c-11ed-b1bb-1299ca1e1805/kops get instancegroups --name e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io -o yaml I0126 17:31:43.952782 5526 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/a92bfbc5-9d9c-11ed-b1bb-1299ca1e1805/kops get instancegroups --name e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io -o yaml I0126 17:31:44.739842 5526 dumplogs.go:98] kubectl cluster-info dump --all-namespaces -o yaml --output-directory /logs/artifacts/cluster-info I0126 17:31:44.739891 5526 local.go:42] ⚙️ kubectl cluster-info dump --all-namespaces -o yaml --output-directory /logs/artifacts/cluster-info ... skipping 235 lines ... route-table:rtb-0e9f9cf4e79571f81 ok vpc:vpc-0c15beaa45d0ae8da ok dhcp-options:dopt-0cdb2a0edc3eab5ff ok Deleted kubectl config for e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io Deleted cluster: "e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io" Error: exit status 1 + EXIT_VALUE=1 + set +o xtrace