e2e-kops-grid-cilium-eni-u2004-k26 #1608709341941075968
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 1 failed / 1 succeeded |
| Started | |
| Elapsed | 21m47s |
| Revision | master |
exit status 1
from junit_runner.xml
Filter through log files | View test history on testgrid
kubetest2 Down
... skipping 135 lines ... I1230 06:21:39.602690 5516 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt I1230 06:21:39.605013 5516 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/1.27.0-alpha.2+v1.27.0-alpha.1-35-g351a75dbdd/linux/amd64/kops I1230 06:21:40.374704 5516 local.go:42] ⚙️ ssh-keygen -t ed25519 -N -q -f /tmp/kops/e2e-e2e-kops-grid-cilium-eni-u2004-k26.test-cncf-aws.k8s.io/id_ed25519 I1230 06:21:40.384145 5516 up.go:44] Cleaning up any leaked resources from previous cluster I1230 06:21:40.384240 5516 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/eb40c079-8809-11ed-b47a-e2b55b2f9198/kops toolbox dump --name e2e-e2e-kops-grid-cilium-eni-u2004-k26.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-eni-u2004-k26.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu I1230 06:21:40.384258 5516 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/eb40c079-8809-11ed-b47a-e2b55b2f9198/kops toolbox dump --name e2e-e2e-kops-grid-cilium-eni-u2004-k26.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-eni-u2004-k26.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu W1230 06:21:40.921507 5516 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1 I1230 06:21:40.921567 5516 down.go:48] /home/prow/go/src/k8s.io/kops/_rundir/eb40c079-8809-11ed-b47a-e2b55b2f9198/kops delete cluster --name e2e-e2e-kops-grid-cilium-eni-u2004-k26.test-cncf-aws.k8s.io --yes I1230 06:21:40.921581 5516 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/eb40c079-8809-11ed-b47a-e2b55b2f9198/kops delete cluster --name e2e-e2e-kops-grid-cilium-eni-u2004-k26.test-cncf-aws.k8s.io --yes I1230 06:21:40.955378 5547 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-e2e-kops-grid-cilium-eni-u2004-k26.test-cncf-aws.k8s.io" not found I1230 06:21:41.407253 5516 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip 2022/12/30 06:21: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 I1230 06:21:41.420199 5516 http.go:37] curl https://ip.jsb.workers.dev I1230 06:21:41.506636 5516 up.go:167] /home/prow/go/src/k8s.io/kops/_rundir/eb40c079-8809-11ed-b47a-e2b55b2f9198/kops create cluster --name e2e-e2e-kops-grid-cilium-eni-u2004-k26.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.26.0 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-cilium-eni-u2004-k26.test-cncf-aws.k8s.io/id_ed25519.pub --set cluster.spec.nodePortAccess=0.0.0.0/0 --image=099720109477/ubuntu/images/hvm-ssd/ubuntu-focal-20.04-amd64-server-20221212 --channel=alpha --networking=cilium-eni --container-runtime=containerd --admin-access 35.226.241.93/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-south-1a --master-size c5.large I1230 06:21:41.506675 5516 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/eb40c079-8809-11ed-b47a-e2b55b2f9198/kops create cluster --name e2e-e2e-kops-grid-cilium-eni-u2004-k26.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.26.0 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-cilium-eni-u2004-k26.test-cncf-aws.k8s.io/id_ed25519.pub --set cluster.spec.nodePortAccess=0.0.0.0/0 --image=099720109477/ubuntu/images/hvm-ssd/ubuntu-focal-20.04-amd64-server-20221212 --channel=alpha --networking=cilium-eni --container-runtime=containerd --admin-access 35.226.241.93/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-south-1a --master-size c5.large I1230 06:21:41.540943 5556 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true I1230 06:21:41.558877 5556 create_cluster.go:878] Using SSH public key: /tmp/kops/e2e-e2e-kops-grid-cilium-eni-u2004-k26.test-cncf-aws.k8s.io/id_ed25519.pub I1230 06:21:42.146935 5556 new_cluster.go:1326] Cloud Provider ID: "aws" ... skipping 515 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 W1230 06:22:27.376573 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a 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 W1230 06:22:37.423977 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a 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 W1230 06:22:47.464768 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a 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 W1230 06:22:57.513775 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a 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 W1230 06:23:07.551809 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a 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 W1230 06:23:17.593396 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a 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 W1230 06:23:27.642341 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a 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 W1230 06:23:37.697372 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a 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 W1230 06:23:47.738515 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a 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 W1230 06:23:57.772330 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a 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 W1230 06:24:07.826984 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a 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 W1230 06:24:17.885438 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a 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 W1230 06:24:27.928975 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a 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 W1230 06:24:37.984400 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a 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 W1230 06:24:48.021542 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a 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 W1230 06:24:58.064827 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a 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 W1230 06:25:08.099760 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a 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 W1230 06:25:18.142143 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a 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 W1230 06:25:28.188501 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a 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 W1230 06:25:38.236235 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a 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 W1230 06:25:48.288846 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 10 lines ... Pod kube-system/cilium-4l6jk system-node-critical pod "cilium-4l6jk" is not ready (cilium-agent) Pod kube-system/coredns-559769c974-6k54t system-cluster-critical pod "coredns-559769c974-6k54t" is pending Pod kube-system/coredns-autoscaler-7cb5c5b969-z7pfj system-cluster-critical pod "coredns-autoscaler-7cb5c5b969-z7pfj" is pending Pod kube-system/ebs-csi-controller-89b649c94-zg9fx system-cluster-critical pod "ebs-csi-controller-89b649c94-zg9fx" is pending Pod kube-system/ebs-csi-node-pmlgn system-node-critical pod "ebs-csi-node-pmlgn" is pending Validation Failed W1230 06:26:04.009135 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 15 lines ... Pod kube-system/coredns-autoscaler-7cb5c5b969-z7pfj system-cluster-critical pod "coredns-autoscaler-7cb5c5b969-z7pfj" is pending Pod kube-system/ebs-csi-controller-89b649c94-zg9fx system-cluster-critical pod "ebs-csi-controller-89b649c94-zg9fx" is pending Pod kube-system/ebs-csi-node-4x22p system-node-critical pod "ebs-csi-node-4x22p" is pending Pod kube-system/ebs-csi-node-pmlgn system-node-critical pod "ebs-csi-node-pmlgn" is pending Pod kube-system/ebs-csi-node-xf9bj system-node-critical pod "ebs-csi-node-xf9bj" is pending Validation Failed W1230 06:26:17.701909 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 13 lines ... Pod kube-system/coredns-autoscaler-7cb5c5b969-z7pfj system-cluster-critical pod "coredns-autoscaler-7cb5c5b969-z7pfj" is pending Pod kube-system/ebs-csi-controller-89b649c94-zg9fx system-cluster-critical pod "ebs-csi-controller-89b649c94-zg9fx" is pending Pod kube-system/ebs-csi-node-4x22p system-node-critical pod "ebs-csi-node-4x22p" is pending Pod kube-system/ebs-csi-node-pmlgn system-node-critical pod "ebs-csi-node-pmlgn" is pending Pod kube-system/ebs-csi-node-xf9bj system-node-critical pod "ebs-csi-node-xf9bj" is pending Validation Failed W1230 06:26:31.454734 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 9 lines ... Machine i-0adfe66ab1ea2df49 machine "i-0adfe66ab1ea2df49" has not yet joined cluster Pod kube-system/coredns-559769c974-6k54t system-cluster-critical pod "coredns-559769c974-6k54t" is pending Pod kube-system/coredns-autoscaler-7cb5c5b969-z7pfj system-cluster-critical pod "coredns-autoscaler-7cb5c5b969-z7pfj" is pending Pod kube-system/ebs-csi-node-4x22p system-node-critical pod "ebs-csi-node-4x22p" is pending Pod kube-system/ebs-csi-node-xf9bj system-node-critical pod "ebs-csi-node-xf9bj" is pending Validation Failed W1230 06:26:45.215327 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 5 lines ... VALIDATION ERRORS KIND NAME MESSAGE Machine i-00749f9417c4d09d1 machine "i-00749f9417c4d09d1" has not yet joined cluster Machine i-0adfe66ab1ea2df49 machine "i-0adfe66ab1ea2df49" has not yet joined cluster Validation Failed W1230 06:26:58.825592 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 5 lines ... VALIDATION ERRORS KIND NAME MESSAGE Machine i-00749f9417c4d09d1 machine "i-00749f9417c4d09d1" has not yet joined cluster Machine i-0adfe66ab1ea2df49 machine "i-0adfe66ab1ea2df49" has not yet joined cluster Validation Failed W1230 06:27:12.512743 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 5 lines ... VALIDATION ERRORS KIND NAME MESSAGE Machine i-00749f9417c4d09d1 machine "i-00749f9417c4d09d1" has not yet joined cluster Machine i-0adfe66ab1ea2df49 machine "i-0adfe66ab1ea2df49" has not yet joined cluster Validation Failed W1230 06:27:26.122325 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 5 lines ... VALIDATION ERRORS KIND NAME MESSAGE Machine i-00749f9417c4d09d1 machine "i-00749f9417c4d09d1" has not yet joined cluster Machine i-0adfe66ab1ea2df49 machine "i-0adfe66ab1ea2df49" has not yet joined cluster Validation Failed W1230 06:27:39.745985 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 5 lines ... VALIDATION ERRORS KIND NAME MESSAGE Machine i-00749f9417c4d09d1 machine "i-00749f9417c4d09d1" has not yet joined cluster Machine i-0adfe66ab1ea2df49 machine "i-0adfe66ab1ea2df49" has not yet joined cluster Validation Failed W1230 06:27:53.320185 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 5 lines ... VALIDATION ERRORS KIND NAME MESSAGE Machine i-00749f9417c4d09d1 machine "i-00749f9417c4d09d1" has not yet joined cluster Machine i-0adfe66ab1ea2df49 machine "i-0adfe66ab1ea2df49" has not yet joined cluster Validation Failed W1230 06:28:06.869648 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 5 lines ... VALIDATION ERRORS KIND NAME MESSAGE Machine i-00749f9417c4d09d1 machine "i-00749f9417c4d09d1" has not yet joined cluster Machine i-0adfe66ab1ea2df49 machine "i-0adfe66ab1ea2df49" has not yet joined cluster Validation Failed W1230 06:28:20.439862 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 5 lines ... VALIDATION ERRORS KIND NAME MESSAGE Machine i-00749f9417c4d09d1 machine "i-00749f9417c4d09d1" has not yet joined cluster Machine i-0adfe66ab1ea2df49 machine "i-0adfe66ab1ea2df49" has not yet joined cluster Validation Failed W1230 06:28:34.077558 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 5 lines ... VALIDATION ERRORS KIND NAME MESSAGE Machine i-00749f9417c4d09d1 machine "i-00749f9417c4d09d1" has not yet joined cluster Machine i-0adfe66ab1ea2df49 machine "i-0adfe66ab1ea2df49" has not yet joined cluster Validation Failed W1230 06:28:47.704445 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 5 lines ... VALIDATION ERRORS KIND NAME MESSAGE Machine i-00749f9417c4d09d1 machine "i-00749f9417c4d09d1" has not yet joined cluster Machine i-0adfe66ab1ea2df49 machine "i-0adfe66ab1ea2df49" has not yet joined cluster Validation Failed W1230 06:29:01.329085 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 5 lines ... VALIDATION ERRORS KIND NAME MESSAGE Machine i-00749f9417c4d09d1 machine "i-00749f9417c4d09d1" has not yet joined cluster Machine i-0adfe66ab1ea2df49 machine "i-0adfe66ab1ea2df49" has not yet joined cluster Validation Failed W1230 06:29:15.122044 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 5 lines ... VALIDATION ERRORS KIND NAME MESSAGE Machine i-00749f9417c4d09d1 machine "i-00749f9417c4d09d1" has not yet joined cluster Machine i-0adfe66ab1ea2df49 machine "i-0adfe66ab1ea2df49" has not yet joined cluster Validation Failed W1230 06:29:28.769995 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 5 lines ... VALIDATION ERRORS KIND NAME MESSAGE Machine i-00749f9417c4d09d1 machine "i-00749f9417c4d09d1" has not yet joined cluster Machine i-0adfe66ab1ea2df49 machine "i-0adfe66ab1ea2df49" has not yet joined cluster Validation Failed W1230 06:29:42.398701 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 5 lines ... VALIDATION ERRORS KIND NAME MESSAGE Machine i-00749f9417c4d09d1 machine "i-00749f9417c4d09d1" has not yet joined cluster Machine i-0adfe66ab1ea2df49 machine "i-0adfe66ab1ea2df49" has not yet joined cluster Validation Failed W1230 06:29:56.807124 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 5 lines ... VALIDATION ERRORS KIND NAME MESSAGE Machine i-00749f9417c4d09d1 machine "i-00749f9417c4d09d1" has not yet joined cluster Machine i-0adfe66ab1ea2df49 machine "i-0adfe66ab1ea2df49" has not yet joined cluster Validation Failed W1230 06:30:10.443624 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 5 lines ... VALIDATION ERRORS KIND NAME MESSAGE Machine i-00749f9417c4d09d1 machine "i-00749f9417c4d09d1" has not yet joined cluster Machine i-0adfe66ab1ea2df49 machine "i-0adfe66ab1ea2df49" has not yet joined cluster Validation Failed W1230 06:30:24.296418 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 5 lines ... VALIDATION ERRORS KIND NAME MESSAGE Machine i-00749f9417c4d09d1 machine "i-00749f9417c4d09d1" has not yet joined cluster Machine i-0adfe66ab1ea2df49 machine "i-0adfe66ab1ea2df49" has not yet joined cluster Validation Failed W1230 06:30:38.025262 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 5 lines ... VALIDATION ERRORS KIND NAME MESSAGE Machine i-00749f9417c4d09d1 machine "i-00749f9417c4d09d1" has not yet joined cluster Machine i-0adfe66ab1ea2df49 machine "i-0adfe66ab1ea2df49" has not yet joined cluster Validation Failed W1230 06:30:51.733164 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 5 lines ... VALIDATION ERRORS KIND NAME MESSAGE Machine i-00749f9417c4d09d1 machine "i-00749f9417c4d09d1" has not yet joined cluster Machine i-0adfe66ab1ea2df49 machine "i-0adfe66ab1ea2df49" has not yet joined cluster Validation Failed W1230 06:31:05.288013 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 5 lines ... VALIDATION ERRORS KIND NAME MESSAGE Machine i-00749f9417c4d09d1 machine "i-00749f9417c4d09d1" has not yet joined cluster Machine i-0adfe66ab1ea2df49 machine "i-0adfe66ab1ea2df49" has not yet joined cluster Validation Failed W1230 06:31:19.003644 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 5 lines ... VALIDATION ERRORS KIND NAME MESSAGE Machine i-00749f9417c4d09d1 machine "i-00749f9417c4d09d1" has not yet joined cluster Machine i-0adfe66ab1ea2df49 machine "i-0adfe66ab1ea2df49" has not yet joined cluster Validation Failed W1230 06:31:32.725670 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 5 lines ... VALIDATION ERRORS KIND NAME MESSAGE Machine i-00749f9417c4d09d1 machine "i-00749f9417c4d09d1" has not yet joined cluster Machine i-0adfe66ab1ea2df49 machine "i-0adfe66ab1ea2df49" has not yet joined cluster Validation Failed W1230 06:31:46.352529 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 5 lines ... VALIDATION ERRORS KIND NAME MESSAGE Machine i-00749f9417c4d09d1 machine "i-00749f9417c4d09d1" has not yet joined cluster Machine i-0adfe66ab1ea2df49 machine "i-0adfe66ab1ea2df49" has not yet joined cluster Validation Failed W1230 06:32:00.031274 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 5 lines ... VALIDATION ERRORS KIND NAME MESSAGE Machine i-00749f9417c4d09d1 machine "i-00749f9417c4d09d1" has not yet joined cluster Machine i-0adfe66ab1ea2df49 machine "i-0adfe66ab1ea2df49" has not yet joined cluster Validation Failed W1230 06:32:13.671034 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 5 lines ... VALIDATION ERRORS KIND NAME MESSAGE Machine i-00749f9417c4d09d1 machine "i-00749f9417c4d09d1" has not yet joined cluster Machine i-0adfe66ab1ea2df49 machine "i-0adfe66ab1ea2df49" has not yet joined cluster Validation Failed W1230 06:32:27.355586 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 5 lines ... VALIDATION ERRORS KIND NAME MESSAGE Machine i-00749f9417c4d09d1 machine "i-00749f9417c4d09d1" has not yet joined cluster Machine i-0adfe66ab1ea2df49 machine "i-0adfe66ab1ea2df49" has not yet joined cluster Validation Failed W1230 06:32:41.019601 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 5 lines ... VALIDATION ERRORS KIND NAME MESSAGE Machine i-00749f9417c4d09d1 machine "i-00749f9417c4d09d1" has not yet joined cluster Machine i-0adfe66ab1ea2df49 machine "i-0adfe66ab1ea2df49" has not yet joined cluster Validation Failed W1230 06:32:54.681066 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 5 lines ... VALIDATION ERRORS KIND NAME MESSAGE Machine i-00749f9417c4d09d1 machine "i-00749f9417c4d09d1" has not yet joined cluster Machine i-0adfe66ab1ea2df49 machine "i-0adfe66ab1ea2df49" has not yet joined cluster Validation Failed W1230 06:33:08.402609 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 5 lines ... VALIDATION ERRORS KIND NAME MESSAGE Machine i-00749f9417c4d09d1 machine "i-00749f9417c4d09d1" has not yet joined cluster Machine i-0adfe66ab1ea2df49 machine "i-0adfe66ab1ea2df49" has not yet joined cluster Validation Failed W1230 06:33:22.019733 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 5 lines ... VALIDATION ERRORS KIND NAME MESSAGE Machine i-00749f9417c4d09d1 machine "i-00749f9417c4d09d1" has not yet joined cluster Machine i-0adfe66ab1ea2df49 machine "i-0adfe66ab1ea2df49" has not yet joined cluster Validation Failed W1230 06:33:35.711393 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 5 lines ... VALIDATION ERRORS KIND NAME MESSAGE Machine i-00749f9417c4d09d1 machine "i-00749f9417c4d09d1" has not yet joined cluster Machine i-0adfe66ab1ea2df49 machine "i-0adfe66ab1ea2df49" has not yet joined cluster Validation Failed W1230 06:33:50.178293 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 5 lines ... VALIDATION ERRORS KIND NAME MESSAGE Machine i-00749f9417c4d09d1 machine "i-00749f9417c4d09d1" has not yet joined cluster Machine i-0adfe66ab1ea2df49 machine "i-0adfe66ab1ea2df49" has not yet joined cluster Validation Failed W1230 06:34:03.881182 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 5 lines ... VALIDATION ERRORS KIND NAME MESSAGE Machine i-00749f9417c4d09d1 machine "i-00749f9417c4d09d1" has not yet joined cluster Machine i-0adfe66ab1ea2df49 machine "i-0adfe66ab1ea2df49" has not yet joined cluster Validation Failed W1230 06:34:17.481079 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 5 lines ... VALIDATION ERRORS KIND NAME MESSAGE Machine i-00749f9417c4d09d1 machine "i-00749f9417c4d09d1" has not yet joined cluster Machine i-0adfe66ab1ea2df49 machine "i-0adfe66ab1ea2df49" has not yet joined cluster Validation Failed W1230 06:34:31.121206 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 5 lines ... VALIDATION ERRORS KIND NAME MESSAGE Machine i-00749f9417c4d09d1 machine "i-00749f9417c4d09d1" has not yet joined cluster Machine i-0adfe66ab1ea2df49 machine "i-0adfe66ab1ea2df49" has not yet joined cluster Validation Failed W1230 06:34:44.832357 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 5 lines ... VALIDATION ERRORS KIND NAME MESSAGE Machine i-00749f9417c4d09d1 machine "i-00749f9417c4d09d1" has not yet joined cluster Machine i-0adfe66ab1ea2df49 machine "i-0adfe66ab1ea2df49" has not yet joined cluster Validation Failed W1230 06:34:58.488706 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 5 lines ... VALIDATION ERRORS KIND NAME MESSAGE Machine i-00749f9417c4d09d1 machine "i-00749f9417c4d09d1" has not yet joined cluster Machine i-0adfe66ab1ea2df49 machine "i-0adfe66ab1ea2df49" has not yet joined cluster Validation Failed W1230 06:35:12.016782 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 5 lines ... VALIDATION ERRORS KIND NAME MESSAGE Machine i-00749f9417c4d09d1 machine "i-00749f9417c4d09d1" has not yet joined cluster Machine i-0adfe66ab1ea2df49 machine "i-0adfe66ab1ea2df49" has not yet joined cluster Validation Failed W1230 06:35:25.605319 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 5 lines ... VALIDATION ERRORS KIND NAME MESSAGE Machine i-00749f9417c4d09d1 machine "i-00749f9417c4d09d1" has not yet joined cluster Machine i-0adfe66ab1ea2df49 machine "i-0adfe66ab1ea2df49" has not yet joined cluster Validation Failed W1230 06:35:39.209033 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 5 lines ... VALIDATION ERRORS KIND NAME MESSAGE Machine i-00749f9417c4d09d1 machine "i-00749f9417c4d09d1" has not yet joined cluster Machine i-0adfe66ab1ea2df49 machine "i-0adfe66ab1ea2df49" has not yet joined cluster Validation Failed W1230 06:35:52.826513 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 5 lines ... VALIDATION ERRORS KIND NAME MESSAGE Machine i-00749f9417c4d09d1 machine "i-00749f9417c4d09d1" has not yet joined cluster Machine i-0adfe66ab1ea2df49 machine "i-0adfe66ab1ea2df49" has not yet joined cluster Validation Failed W1230 06:36:06.410453 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 5 lines ... VALIDATION ERRORS KIND NAME MESSAGE Machine i-00749f9417c4d09d1 machine "i-00749f9417c4d09d1" has not yet joined cluster Machine i-0adfe66ab1ea2df49 machine "i-0adfe66ab1ea2df49" has not yet joined cluster Validation Failed W1230 06:36:19.944408 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 5 lines ... VALIDATION ERRORS KIND NAME MESSAGE Machine i-00749f9417c4d09d1 machine "i-00749f9417c4d09d1" has not yet joined cluster Machine i-0adfe66ab1ea2df49 machine "i-0adfe66ab1ea2df49" has not yet joined cluster Validation Failed W1230 06:36:33.551618 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 5 lines ... VALIDATION ERRORS KIND NAME MESSAGE Machine i-00749f9417c4d09d1 machine "i-00749f9417c4d09d1" has not yet joined cluster Machine i-0adfe66ab1ea2df49 machine "i-0adfe66ab1ea2df49" has not yet joined cluster Validation Failed W1230 06:36:47.140502 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 11 lines ... Node i-0adfe66ab1ea2df49 node "i-0adfe66ab1ea2df49" of role "node" is not ready Pod kube-system/cilium-blrqk system-node-critical pod "cilium-blrqk" is pending Pod kube-system/cilium-fnrpc system-node-critical pod "cilium-fnrpc" is pending Pod kube-system/ebs-csi-node-jxk2r system-node-critical pod "ebs-csi-node-jxk2r" is pending Pod kube-system/ebs-csi-node-wm9pl system-node-critical pod "ebs-csi-node-wm9pl" is pending Validation Failed W1230 06:37:00.863802 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 9 lines ... KIND NAME MESSAGE Pod kube-system/cilium-blrqk system-node-critical pod "cilium-blrqk" is not ready (cilium-agent) Pod kube-system/cilium-fnrpc system-node-critical pod "cilium-fnrpc" is not ready (cilium-agent) Pod kube-system/ebs-csi-node-jxk2r system-node-critical pod "ebs-csi-node-jxk2r" is pending Pod kube-system/ebs-csi-node-wm9pl system-node-critical pod "ebs-csi-node-wm9pl" is pending Validation Failed W1230 06:37:14.520844 5594 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-south-1a ControlPlane c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/ebs-csi-node-jxk2r system-node-critical pod "ebs-csi-node-jxk2r" is pending Pod kube-system/ebs-csi-node-wm9pl system-node-critical pod "ebs-csi-node-wm9pl" is pending Validation Failed W1230 06:37:28.257940 5594 validate_cluster.go:232] (will retry): cluster not yet healthy Error: validation failed: wait time exceeded during validation I1230 06:37:38.263871 5516 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/eb40c079-8809-11ed-b47a-e2b55b2f9198/kops toolbox dump --name e2e-e2e-kops-grid-cilium-eni-u2004-k26.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-eni-u2004-k26.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu I1230 06:37:38.263958 5516 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/eb40c079-8809-11ed-b47a-e2b55b2f9198/kops toolbox dump --name e2e-e2e-kops-grid-cilium-eni-u2004-k26.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-eni-u2004-k26.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu I1230 06:39:01.894214 5516 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/eb40c079-8809-11ed-b47a-e2b55b2f9198/kops get cluster --name e2e-e2e-kops-grid-cilium-eni-u2004-k26.test-cncf-aws.k8s.io -o yaml I1230 06:39:01.894284 5516 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/eb40c079-8809-11ed-b47a-e2b55b2f9198/kops get cluster --name e2e-e2e-kops-grid-cilium-eni-u2004-k26.test-cncf-aws.k8s.io -o yaml I1230 06:39:02.402267 5516 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/eb40c079-8809-11ed-b47a-e2b55b2f9198/kops get instancegroups --name e2e-e2e-kops-grid-cilium-eni-u2004-k26.test-cncf-aws.k8s.io -o yaml I1230 06:39:02.402302 5516 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/eb40c079-8809-11ed-b47a-e2b55b2f9198/kops get instancegroups --name e2e-e2e-kops-grid-cilium-eni-u2004-k26.test-cncf-aws.k8s.io -o yaml ... skipping 306 lines ... route-table:rtb-05beb49c811fc52ae ok vpc:vpc-0806f08c2a9ccee94 ok dhcp-options:dopt-0fa0b0cbe36ca6b6f ok Deleted kubectl config for e2e-e2e-kops-grid-cilium-eni-u2004-k26.test-cncf-aws.k8s.io Deleted cluster: "e2e-e2e-kops-grid-cilium-eni-u2004-k26.test-cncf-aws.k8s.io" Error: exit status 1 + EXIT_VALUE=1 + set +o xtrace