e2e-kops-grid-cilium-eni-u2004-k26 #1613058075185385472
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 1 failed / 1 succeeded |
| Started | |
| Elapsed | 21m3s |
| Revision | master |
exit status 1
from junit_runner.xml
Filter through log files | View test history on testgrid
kubetest2 Down
... skipping 136 lines ... I0111 06:21:29.423441 5484 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/1.27.0-alpha.2+v1.27.0-alpha.1-141-gf6a36bfc42/linux/amd64/kops I0111 06:21:30.087486 5484 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 I0111 06:21:30.095352 5484 up.go:44] Cleaning up any leaked resources from previous cluster I0111 06:21:30.095705 5484 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/f36a6d1d-9177-11ed-abd8-968f3792f350/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 I0111 06:21:30.095834 5484 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/f36a6d1d-9177-11ed-abd8-968f3792f350/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 I0111 06:21:30.128696 5507 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true Error: Cluster.kops.k8s.io "e2e-e2e-kops-grid-cilium-eni-u2004-k26.test-cncf-aws.k8s.io" not found W0111 06:21:30.590087 5484 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1 I0111 06:21:30.590129 5484 down.go:48] /home/prow/go/src/k8s.io/kops/_rundir/f36a6d1d-9177-11ed-abd8-968f3792f350/kops delete cluster --name e2e-e2e-kops-grid-cilium-eni-u2004-k26.test-cncf-aws.k8s.io --yes I0111 06:21:30.590140 5484 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/f36a6d1d-9177-11ed-abd8-968f3792f350/kops delete cluster --name e2e-e2e-kops-grid-cilium-eni-u2004-k26.test-cncf-aws.k8s.io --yes I0111 06:21:30.623276 5516 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 I0111 06:21:31.096473 5484 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip 2023/01/11 06:21:31 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 I0111 06:21:31.110462 5484 http.go:37] curl https://ip.jsb.workers.dev I0111 06:21:31.203227 5484 up.go:167] /home/prow/go/src/k8s.io/kops/_rundir/f36a6d1d-9177-11ed-abd8-968f3792f350/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.192.181.89/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-south-1a --master-size c5.large I0111 06:21:31.203260 5484 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/f36a6d1d-9177-11ed-abd8-968f3792f350/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.192.181.89/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-south-1a --master-size c5.large I0111 06:21:31.236839 5525 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true I0111 06:21:31.254304 5525 create_cluster.go:884] Using SSH public key: /tmp/kops/e2e-e2e-kops-grid-cilium-eni-u2004-k26.test-cncf-aws.k8s.io/id_ed25519.pub I0111 06:21:31.891956 5525 new_cluster.go:1327] Cloud Provider ID: "aws" ... skipping 518 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 W0111 06:22:28.317085 5563 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 W0111 06:22:38.358150 5563 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 W0111 06:22:48.396356 5563 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 W0111 06:22:58.435750 5563 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 W0111 06:23:08.473514 5563 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 W0111 06:23:18.511263 5563 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 W0111 06:23:28.542411 5563 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 W0111 06:23:38.580428 5563 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 W0111 06:23:48.621127 5563 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 W0111 06:23:58.671696 5563 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 W0111 06:24:08.711814 5563 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 W0111 06:24:18.750345 5563 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 W0111 06:24:28.797633 5563 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 W0111 06:24:38.838151 5563 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 W0111 06:24:48.878493 5563 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 W0111 06:24:58.913417 5563 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 W0111 06:25:08.954180 5563 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 W0111 06:25:18.989945 5563 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 W0111 06:25:29.025616 5563 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 W0111 06:25:39.080794 5563 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 W0111 06:25:49.113583 5563 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 W0111 06:25:59.149858 5563 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-559769c974-4n5zj system-cluster-critical pod "coredns-559769c974-4n5zj" is pending Pod kube-system/coredns-autoscaler-7cb5c5b969-x4gqb system-cluster-critical pod "coredns-autoscaler-7cb5c5b969-x4gqb" is pending Pod kube-system/ebs-csi-controller-7547c5f48-ntpfb system-cluster-critical pod "ebs-csi-controller-7547c5f48-ntpfb" is pending Pod kube-system/ebs-csi-node-7g7cg system-node-critical pod "ebs-csi-node-7g7cg" is pending Pod kube-system/ebs-csi-node-8hnx8 system-node-critical pod "ebs-csi-node-8hnx8" is pending Validation Failed W0111 06:26:14.347492 5563 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-x4gqb system-cluster-critical pod "coredns-autoscaler-7cb5c5b969-x4gqb" is pending Pod kube-system/ebs-csi-controller-7547c5f48-ntpfb system-cluster-critical pod "ebs-csi-controller-7547c5f48-ntpfb" is pending Pod kube-system/ebs-csi-node-7g7cg system-node-critical pod "ebs-csi-node-7g7cg" is pending Pod kube-system/ebs-csi-node-8hnx8 system-node-critical pod "ebs-csi-node-8hnx8" is pending Pod kube-system/ebs-csi-node-qmxtd system-node-critical pod "ebs-csi-node-qmxtd" is pending Validation Failed W0111 06:26:27.956947 5563 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 12 lines ... Pod kube-system/coredns-559769c974-4n5zj system-cluster-critical pod "coredns-559769c974-4n5zj" is pending Pod kube-system/coredns-autoscaler-7cb5c5b969-x4gqb system-cluster-critical pod "coredns-autoscaler-7cb5c5b969-x4gqb" is pending Pod kube-system/ebs-csi-controller-7547c5f48-ntpfb system-cluster-critical pod "ebs-csi-controller-7547c5f48-ntpfb" is pending Pod kube-system/ebs-csi-node-7g7cg system-node-critical pod "ebs-csi-node-7g7cg" is pending Pod kube-system/ebs-csi-node-qmxtd system-node-critical pod "ebs-csi-node-qmxtd" is pending Validation Failed W0111 06:26:41.554651 5563 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 8 lines ... Machine i-00f9860425b3dc449 machine "i-00f9860425b3dc449" has not yet joined cluster Machine i-091f872a9438e3a57 machine "i-091f872a9438e3a57" has not yet joined cluster Pod kube-system/cilium-x84m8 system-node-critical pod "cilium-x84m8" is not ready (cilium-agent) Pod kube-system/coredns-559769c974-pd25t system-cluster-critical pod "coredns-559769c974-pd25t" is pending Pod kube-system/ebs-csi-node-qmxtd system-node-critical pod "ebs-csi-node-qmxtd" is pending Validation Failed W0111 06:26:55.156509 5563 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 6 lines ... VALIDATION ERRORS KIND NAME MESSAGE Machine i-00f9860425b3dc449 machine "i-00f9860425b3dc449" has not yet joined cluster Machine i-091f872a9438e3a57 machine "i-091f872a9438e3a57" has not yet joined cluster Pod kube-system/ebs-csi-node-qmxtd system-node-critical pod "ebs-csi-node-qmxtd" is pending Validation Failed W0111 06:27:08.859041 5563 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-00f9860425b3dc449 machine "i-00f9860425b3dc449" has not yet joined cluster Machine i-091f872a9438e3a57 machine "i-091f872a9438e3a57" has not yet joined cluster Validation Failed W0111 06:27:22.506194 5563 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-00f9860425b3dc449 machine "i-00f9860425b3dc449" has not yet joined cluster Machine i-091f872a9438e3a57 machine "i-091f872a9438e3a57" has not yet joined cluster Validation Failed W0111 06:27:36.075213 5563 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-00f9860425b3dc449 machine "i-00f9860425b3dc449" has not yet joined cluster Machine i-091f872a9438e3a57 machine "i-091f872a9438e3a57" has not yet joined cluster Validation Failed W0111 06:27:49.735485 5563 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-00f9860425b3dc449 machine "i-00f9860425b3dc449" has not yet joined cluster Machine i-091f872a9438e3a57 machine "i-091f872a9438e3a57" has not yet joined cluster Validation Failed W0111 06:28:03.243746 5563 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-00f9860425b3dc449 machine "i-00f9860425b3dc449" has not yet joined cluster Machine i-091f872a9438e3a57 machine "i-091f872a9438e3a57" has not yet joined cluster Validation Failed W0111 06:28:16.801267 5563 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-00f9860425b3dc449 machine "i-00f9860425b3dc449" has not yet joined cluster Machine i-091f872a9438e3a57 machine "i-091f872a9438e3a57" has not yet joined cluster Validation Failed W0111 06:28:30.439273 5563 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-00f9860425b3dc449 machine "i-00f9860425b3dc449" has not yet joined cluster Machine i-091f872a9438e3a57 machine "i-091f872a9438e3a57" has not yet joined cluster Validation Failed W0111 06:28:43.997892 5563 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-00f9860425b3dc449 machine "i-00f9860425b3dc449" has not yet joined cluster Machine i-091f872a9438e3a57 machine "i-091f872a9438e3a57" has not yet joined cluster Validation Failed W0111 06:28:57.497912 5563 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-00f9860425b3dc449 machine "i-00f9860425b3dc449" has not yet joined cluster Machine i-091f872a9438e3a57 machine "i-091f872a9438e3a57" has not yet joined cluster Validation Failed W0111 06:29:11.038131 5563 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-00f9860425b3dc449 machine "i-00f9860425b3dc449" has not yet joined cluster Machine i-091f872a9438e3a57 machine "i-091f872a9438e3a57" has not yet joined cluster Validation Failed W0111 06:29:24.527103 5563 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-00f9860425b3dc449 machine "i-00f9860425b3dc449" has not yet joined cluster Machine i-091f872a9438e3a57 machine "i-091f872a9438e3a57" has not yet joined cluster Validation Failed W0111 06:29:38.059356 5563 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-00f9860425b3dc449 machine "i-00f9860425b3dc449" has not yet joined cluster Machine i-091f872a9438e3a57 machine "i-091f872a9438e3a57" has not yet joined cluster Validation Failed W0111 06:29:51.630903 5563 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-00f9860425b3dc449 machine "i-00f9860425b3dc449" has not yet joined cluster Machine i-091f872a9438e3a57 machine "i-091f872a9438e3a57" has not yet joined cluster Validation Failed W0111 06:30:05.995445 5563 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-00f9860425b3dc449 machine "i-00f9860425b3dc449" has not yet joined cluster Machine i-091f872a9438e3a57 machine "i-091f872a9438e3a57" has not yet joined cluster Validation Failed W0111 06:30:19.594284 5563 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-00f9860425b3dc449 machine "i-00f9860425b3dc449" has not yet joined cluster Machine i-091f872a9438e3a57 machine "i-091f872a9438e3a57" has not yet joined cluster Validation Failed W0111 06:30:33.154577 5563 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-00f9860425b3dc449 machine "i-00f9860425b3dc449" has not yet joined cluster Machine i-091f872a9438e3a57 machine "i-091f872a9438e3a57" has not yet joined cluster Validation Failed W0111 06:30:46.744490 5563 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-00f9860425b3dc449 machine "i-00f9860425b3dc449" has not yet joined cluster Machine i-091f872a9438e3a57 machine "i-091f872a9438e3a57" has not yet joined cluster Validation Failed W0111 06:31:00.258379 5563 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-00f9860425b3dc449 machine "i-00f9860425b3dc449" has not yet joined cluster Machine i-091f872a9438e3a57 machine "i-091f872a9438e3a57" has not yet joined cluster Validation Failed W0111 06:31:13.974037 5563 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-00f9860425b3dc449 machine "i-00f9860425b3dc449" has not yet joined cluster Machine i-091f872a9438e3a57 machine "i-091f872a9438e3a57" has not yet joined cluster Validation Failed W0111 06:31:27.472550 5563 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-00f9860425b3dc449 machine "i-00f9860425b3dc449" has not yet joined cluster Machine i-091f872a9438e3a57 machine "i-091f872a9438e3a57" has not yet joined cluster Validation Failed W0111 06:31:41.103735 5563 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-00f9860425b3dc449 machine "i-00f9860425b3dc449" has not yet joined cluster Machine i-091f872a9438e3a57 machine "i-091f872a9438e3a57" has not yet joined cluster Validation Failed W0111 06:31:54.625513 5563 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-00f9860425b3dc449 machine "i-00f9860425b3dc449" has not yet joined cluster Machine i-091f872a9438e3a57 machine "i-091f872a9438e3a57" has not yet joined cluster Validation Failed W0111 06:32:08.270305 5563 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-00f9860425b3dc449 machine "i-00f9860425b3dc449" has not yet joined cluster Machine i-091f872a9438e3a57 machine "i-091f872a9438e3a57" has not yet joined cluster Validation Failed W0111 06:32:21.871015 5563 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-00f9860425b3dc449 machine "i-00f9860425b3dc449" has not yet joined cluster Machine i-091f872a9438e3a57 machine "i-091f872a9438e3a57" has not yet joined cluster Validation Failed W0111 06:32:35.529485 5563 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-00f9860425b3dc449 machine "i-00f9860425b3dc449" has not yet joined cluster Machine i-091f872a9438e3a57 machine "i-091f872a9438e3a57" has not yet joined cluster Validation Failed W0111 06:32:49.101294 5563 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-00f9860425b3dc449 machine "i-00f9860425b3dc449" has not yet joined cluster Machine i-091f872a9438e3a57 machine "i-091f872a9438e3a57" has not yet joined cluster Validation Failed W0111 06:33:02.636281 5563 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-00f9860425b3dc449 machine "i-00f9860425b3dc449" has not yet joined cluster Machine i-091f872a9438e3a57 machine "i-091f872a9438e3a57" has not yet joined cluster Validation Failed W0111 06:33:16.212773 5563 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-00f9860425b3dc449 machine "i-00f9860425b3dc449" has not yet joined cluster Machine i-091f872a9438e3a57 machine "i-091f872a9438e3a57" has not yet joined cluster Validation Failed W0111 06:33:29.757064 5563 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-00f9860425b3dc449 machine "i-00f9860425b3dc449" has not yet joined cluster Machine i-091f872a9438e3a57 machine "i-091f872a9438e3a57" has not yet joined cluster Validation Failed W0111 06:33:43.267183 5563 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-00f9860425b3dc449 machine "i-00f9860425b3dc449" has not yet joined cluster Machine i-091f872a9438e3a57 machine "i-091f872a9438e3a57" has not yet joined cluster Validation Failed W0111 06:33:57.582827 5563 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-00f9860425b3dc449 machine "i-00f9860425b3dc449" has not yet joined cluster Machine i-091f872a9438e3a57 machine "i-091f872a9438e3a57" has not yet joined cluster Validation Failed W0111 06:34:11.242882 5563 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-00f9860425b3dc449 machine "i-00f9860425b3dc449" has not yet joined cluster Machine i-091f872a9438e3a57 machine "i-091f872a9438e3a57" has not yet joined cluster Validation Failed W0111 06:34:24.900966 5563 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-00f9860425b3dc449 machine "i-00f9860425b3dc449" has not yet joined cluster Machine i-091f872a9438e3a57 machine "i-091f872a9438e3a57" has not yet joined cluster Validation Failed W0111 06:34:38.380893 5563 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-00f9860425b3dc449 machine "i-00f9860425b3dc449" has not yet joined cluster Machine i-091f872a9438e3a57 machine "i-091f872a9438e3a57" has not yet joined cluster Validation Failed W0111 06:34:52.009863 5563 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-00f9860425b3dc449 machine "i-00f9860425b3dc449" has not yet joined cluster Machine i-091f872a9438e3a57 machine "i-091f872a9438e3a57" has not yet joined cluster Validation Failed W0111 06:35:05.655846 5563 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-00f9860425b3dc449 machine "i-00f9860425b3dc449" has not yet joined cluster Machine i-091f872a9438e3a57 machine "i-091f872a9438e3a57" has not yet joined cluster Validation Failed W0111 06:35:19.338379 5563 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-00f9860425b3dc449 machine "i-00f9860425b3dc449" has not yet joined cluster Machine i-091f872a9438e3a57 machine "i-091f872a9438e3a57" has not yet joined cluster Validation Failed W0111 06:35:32.966277 5563 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-00f9860425b3dc449 machine "i-00f9860425b3dc449" has not yet joined cluster Machine i-091f872a9438e3a57 machine "i-091f872a9438e3a57" has not yet joined cluster Validation Failed W0111 06:35:46.498411 5563 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-00f9860425b3dc449 machine "i-00f9860425b3dc449" has not yet joined cluster Machine i-091f872a9438e3a57 machine "i-091f872a9438e3a57" has not yet joined cluster Validation Failed W0111 06:36:00.016025 5563 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-00f9860425b3dc449 machine "i-00f9860425b3dc449" has not yet joined cluster Machine i-091f872a9438e3a57 machine "i-091f872a9438e3a57" has not yet joined cluster Validation Failed W0111 06:36:13.561104 5563 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-00f9860425b3dc449 machine "i-00f9860425b3dc449" has not yet joined cluster Machine i-091f872a9438e3a57 machine "i-091f872a9438e3a57" has not yet joined cluster Validation Failed W0111 06:36:27.044139 5563 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-00f9860425b3dc449 machine "i-00f9860425b3dc449" has not yet joined cluster Machine i-091f872a9438e3a57 machine "i-091f872a9438e3a57" has not yet joined cluster Validation Failed W0111 06:36:40.685538 5563 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 ... KIND NAME MESSAGE Machine i-00f9860425b3dc449 machine "i-00f9860425b3dc449" has not yet joined cluster Machine i-091f872a9438e3a57 machine "i-091f872a9438e3a57" has not yet joined cluster Pod kube-system/cilium-vzbdp system-node-critical pod "cilium-vzbdp" is pending Pod kube-system/ebs-csi-node-wshbf system-node-critical pod "ebs-csi-node-wshbf" is pending Validation Failed W0111 06:36:54.210661 5563 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 ... Node i-00f9860425b3dc449 node "i-00f9860425b3dc449" of role "node" is not ready Pod kube-system/cilium-fzt59 system-node-critical pod "cilium-fzt59" is pending Pod kube-system/cilium-vzbdp system-node-critical pod "cilium-vzbdp" is pending Pod kube-system/ebs-csi-node-r6ktf system-node-critical pod "ebs-csi-node-r6ktf" is pending Pod kube-system/ebs-csi-node-wshbf system-node-critical pod "ebs-csi-node-wshbf" is pending Validation Failed W0111 06:37:07.853687 5563 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 ... Node i-091f872a9438e3a57 node "i-091f872a9438e3a57" of role "node" is not ready Pod kube-system/cilium-fzt59 system-node-critical pod "cilium-fzt59" is pending Pod kube-system/cilium-vzbdp system-node-critical pod "cilium-vzbdp" is not ready (cilium-agent) Pod kube-system/ebs-csi-node-r6ktf system-node-critical pod "ebs-csi-node-r6ktf" is pending Pod kube-system/ebs-csi-node-wshbf system-node-critical pod "ebs-csi-node-wshbf" is pending Validation Failed W0111 06:37:21.578151 5563 validate_cluster.go:232] (will retry): cluster not yet healthy Error: validation failed: wait time exceeded during validation I0111 06:37:31.589615 5484 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/f36a6d1d-9177-11ed-abd8-968f3792f350/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 I0111 06:37:31.589673 5484 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/f36a6d1d-9177-11ed-abd8-968f3792f350/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 I0111 06:37:31.623532 5574 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true 2023/01/11 06:37:57 Dumping node i-00f9860425b3dc449 2023/01/11 06:38:08 Dumping node i-06ed4fab4d0a83e64 2023/01/11 06:38:22 Dumping node i-091f872a9438e3a57 ... skipping 274 lines ... route-table:rtb-026016de9189e8d5e ok vpc:vpc-06cd5649b759b2ee4 ok dhcp-options:dopt-007cfdc4c470bc2a6 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