e2e-kops-grid-cilium-etcd-deb10-k23-ko25-docker #1619270895375749120
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 1 failed / 1 succeeded |
| Started | |
| Elapsed | 21m11s |
| Revision | master |
kubetest2 Down
... skipping 135 lines ... I0128 09:49:04.629355 5538 http.go:37] curl https://storage.googleapis.com/kops-ci/markers/release-1.25/latest-ci-updown-green.txt I0128 09:49:04.661729 5538 http.go:37] curl https://storage.googleapis.com/k8s-staging-kops/kops/releases/1.25.4+v1.25.3-40-g875953166f/linux/amd64/kops I0128 09:49:07.092610 5538 local.go:42] ⚙️ ssh-keygen -t ed25519 -N -q -f /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-deb10-k23-ko25-docker.test-cncf-aws.k8s.io/id_ed25519 I0128 09:49:07.099493 5538 up.go:44] Cleaning up any leaked resources from previous cluster I0128 09:49:07.099575 5538 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/c2451746-9ef0-11ed-9a0c-f25a29267a91/kops toolbox dump --name e2e-e2e-kops-grid-cilium-etcd-deb10-k23-ko25-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-deb10-k23-ko25-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user admin I0128 09:49:07.099592 5538 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/c2451746-9ef0-11ed-9a0c-f25a29267a91/kops toolbox dump --name e2e-e2e-kops-grid-cilium-etcd-deb10-k23-ko25-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-deb10-k23-ko25-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user admin Error: Cluster.kops.k8s.io "e2e-e2e-kops-grid-cilium-etcd-deb10-k23-ko25-docker.test-cncf-aws.k8s.io" not found W0128 09:49:07.592078 5538 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1 I0128 09:49:07.592119 5538 down.go:48] /home/prow/go/src/k8s.io/kops/_rundir/c2451746-9ef0-11ed-9a0c-f25a29267a91/kops delete cluster --name e2e-e2e-kops-grid-cilium-etcd-deb10-k23-ko25-docker.test-cncf-aws.k8s.io --yes I0128 09:49:07.592130 5538 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/c2451746-9ef0-11ed-9a0c-f25a29267a91/kops delete cluster --name e2e-e2e-kops-grid-cilium-etcd-deb10-k23-ko25-docker.test-cncf-aws.k8s.io --yes Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-e2e-kops-grid-cilium-etcd-deb10-k23-ko25-docker.test-cncf-aws.k8s.io" not found I0128 09:49:08.091156 5538 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip 2023/01/28 09:49:08 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 I0128 09:49:08.105876 5538 http.go:37] curl https://ip.jsb.workers.dev I0128 09:49:08.191163 5538 up.go:167] /home/prow/go/src/k8s.io/kops/_rundir/c2451746-9ef0-11ed-9a0c-f25a29267a91/kops create cluster --name e2e-e2e-kops-grid-cilium-etcd-deb10-k23-ko25-docker.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.23.16 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-deb10-k23-ko25-docker.test-cncf-aws.k8s.io/id_ed25519.pub --set cluster.spec.nodePortAccess=0.0.0.0/0 --image=136693071363/debian-10-amd64-20221224-1239 --channel=alpha --networking=cilium-etcd --container-runtime=docker --admin-access 34.170.210.157/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-south-1a --master-size c5.large I0128 09:49:08.191200 5538 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/c2451746-9ef0-11ed-9a0c-f25a29267a91/kops create cluster --name e2e-e2e-kops-grid-cilium-etcd-deb10-k23-ko25-docker.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.23.16 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-deb10-k23-ko25-docker.test-cncf-aws.k8s.io/id_ed25519.pub --set cluster.spec.nodePortAccess=0.0.0.0/0 --image=136693071363/debian-10-amd64-20221224-1239 --channel=alpha --networking=cilium-etcd --container-runtime=docker --admin-access 34.170.210.157/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-south-1a --master-size c5.large I0128 09:49:08.242538 5581 create_cluster.go:831] Using SSH public key: /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-deb10-k23-ko25-docker.test-cncf-aws.k8s.io/id_ed25519.pub I0128 09:49:08.743127 5581 new_cluster.go:1279] Cloud Provider ID = aws I0128 09:49:10.171808 5581 subnets.go:185] Assigned CIDR 172.20.32.0/19 to subnet ap-south-1a ... skipping 566 lines ... NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 09:49:50.064946 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master 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 master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 09:50:00.099635 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master 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 master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 09:50:10.134224 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master 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 master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 09:50:20.168410 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master 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 master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 09:50:30.214514 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master 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 master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 09:50:40.252392 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master 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 master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 09:50:50.289214 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master 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 master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 09:51:00.321057 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master 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 master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 09:51:10.356758 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master 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 master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 09:51:20.393930 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master 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 master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 09:51:30.439816 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master 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 master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 09:51:40.472696 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master 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 master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 09:51:50.505471 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master 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 master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 09:52:00.554429 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master 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 master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 09:52:10.588452 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master 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 master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 09:52:20.637720 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master 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 master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 09:52:30.673120 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master 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 master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 09:52:40.713460 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master 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 master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 09:52:50.761119 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 22 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 09:53:05.988171 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 21 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 09:53:19.663944 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 09:53:33.316255 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 09:53:47.003737 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 09:54:00.691680 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 09:54:14.301325 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 09:54:27.947917 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 09:54:41.656324 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 09:54:55.244226 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 09:55:08.900342 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 09:55:22.566983 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 09:55:36.210266 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 09:55:49.871091 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 09:56:03.545604 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 09:56:17.143900 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 09:56:30.760431 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 09:56:44.457606 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 09:56:58.942731 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 09:57:12.535476 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 09:57:26.141217 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 09:57:39.824305 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 09:57:53.435698 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 09:58:07.001208 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 09:58:20.632779 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 09:58:34.210800 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 09:58:47.757935 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 09:59:01.419571 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 09:59:15.070528 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 09:59:28.765890 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 09:59:42.428556 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 09:59:56.082056 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 10:00:09.722539 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 10:00:23.437567 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 10:00:37.173968 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 10:00:51.586864 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 10:01:05.354360 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 10:01:18.965201 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 10:01:32.612709 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 10:01:46.235534 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 10:01:59.879751 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 10:02:13.489097 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 10:02:27.152678 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 10:02:40.713633 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 10:02:54.347080 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 10:03:08.069769 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 10:03:21.711286 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 10:03:35.372423 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 10:03:49.001742 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 10:04:02.656509 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master c5.large 1 1 ap-south-1a nodes-ap-south-1a Node t3.medium 4 4 ap-south-1a ... skipping 18 lines ... Pod kube-system/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 10:04:16.234412 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master 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/ebs-csi-node-dblgk system-node-critical pod "ebs-csi-node-dblgk" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-gsx2p system-node-critical pod "ebs-csi-node-gsx2p" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Pod kube-system/ebs-csi-node-xlrxg system-node-critical pod "ebs-csi-node-xlrxg" is pending Validation Failed W0128 10:04:29.832289 5621 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-south-1a Master 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/coredns-57645f5c8d-m6pfv system-cluster-critical pod "coredns-57645f5c8d-m6pfv" is pending Pod kube-system/ebs-csi-controller-557fc4d747-vp4fz system-cluster-critical pod "ebs-csi-controller-557fc4d747-vp4fz" is pending Pod kube-system/ebs-csi-node-fd2ck system-node-critical pod "ebs-csi-node-fd2ck" is pending Pod kube-system/ebs-csi-node-l44js system-node-critical pod "ebs-csi-node-l44js" is pending Validation Failed W0128 10:04:44.264714 5621 validate_cluster.go:232] (will retry): cluster not yet healthy Error: Validation failed: wait time exceeded during validation I0128 10:04:54.274092 5538 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/c2451746-9ef0-11ed-9a0c-f25a29267a91/kops toolbox dump --name e2e-e2e-kops-grid-cilium-etcd-deb10-k23-ko25-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-deb10-k23-ko25-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user admin I0128 10:04:54.274143 5538 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/c2451746-9ef0-11ed-9a0c-f25a29267a91/kops toolbox dump --name e2e-e2e-kops-grid-cilium-etcd-deb10-k23-ko25-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-deb10-k23-ko25-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user admin 2023/01/28 10:05:22 Dumping node ip-172-20-33-37.ap-south-1.compute.internal 2023/01/28 10:05:33 error dumping node ip-172-20-33-37.ap-south-1.compute.internal: error executing command "sysctl -a": Process exited with status 127 2023/01/28 10:05:33 Dumping node ip-172-20-35-100.ap-south-1.compute.internal 2023/01/28 10:05:43 error dumping node ip-172-20-35-100.ap-south-1.compute.internal: error executing command "sysctl -a": Process exited with status 127 2023/01/28 10:05:43 Dumping node ip-172-20-38-189.ap-south-1.compute.internal 2023/01/28 10:05:54 error dumping node ip-172-20-38-189.ap-south-1.compute.internal: error executing command "sysctl -a": Process exited with status 127 2023/01/28 10:05:54 Dumping node ip-172-20-59-80.ap-south-1.compute.internal 2023/01/28 10:06:04 error dumping node ip-172-20-59-80.ap-south-1.compute.internal: error executing command "sysctl -a": Process exited with status 127 2023/01/28 10:06:04 Dumping node ip-172-20-61-224.ap-south-1.compute.internal 2023/01/28 10:06:18 error dumping node ip-172-20-61-224.ap-south-1.compute.internal: error executing command "sysctl -a": Process exited with status 127 I0128 10:06:18.419830 5538 dumplogs.go:79] /home/prow/go/src/k8s.io/kops/_rundir/c2451746-9ef0-11ed-9a0c-f25a29267a91/kops get cluster --name e2e-e2e-kops-grid-cilium-etcd-deb10-k23-ko25-docker.test-cncf-aws.k8s.io -o yaml I0128 10:06:18.419889 5538 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/c2451746-9ef0-11ed-9a0c-f25a29267a91/kops get cluster --name e2e-e2e-kops-grid-cilium-etcd-deb10-k23-ko25-docker.test-cncf-aws.k8s.io -o yaml I0128 10:06:18.925241 5538 dumplogs.go:79] /home/prow/go/src/k8s.io/kops/_rundir/c2451746-9ef0-11ed-9a0c-f25a29267a91/kops get instancegroups --name e2e-e2e-kops-grid-cilium-etcd-deb10-k23-ko25-docker.test-cncf-aws.k8s.io -o yaml I0128 10:06:18.925271 5538 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/c2451746-9ef0-11ed-9a0c-f25a29267a91/kops get instancegroups --name e2e-e2e-kops-grid-cilium-etcd-deb10-k23-ko25-docker.test-cncf-aws.k8s.io -o yaml I0128 10:06:19.674442 5538 dumplogs.go:98] kubectl cluster-info dump --all-namespaces -o yaml --output-directory /logs/artifacts/cluster-info I0128 10:06:19.674500 5538 local.go:42] ⚙️ kubectl cluster-info dump --all-namespaces -o yaml --output-directory /logs/artifacts/cluster-info ... skipping 300 lines ... route-table:rtb-00db4717c180254d9 ok vpc:vpc-0d9db71463d1651d0 ok dhcp-options:dopt-024792b5a2f191529 ok Deleted kubectl config for e2e-e2e-kops-grid-cilium-etcd-deb10-k23-ko25-docker.test-cncf-aws.k8s.io Deleted cluster: "e2e-e2e-kops-grid-cilium-etcd-deb10-k23-ko25-docker.test-cncf-aws.k8s.io" Error: exit status 1 + EXIT_VALUE=1 + set +o xtrace