e2e-kops-grid-cilium-eni-amzn2-k26 #1616121371815841792
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 1 failed / 1 succeeded |
| Started | |
| Elapsed | 19m52s |
| Revision | master |
exit status 1
from junit_runner.xml
Filter through log files | View test history on testgrid
kubetest2 Down
... skipping 135 lines ... I0119 17:14:36.848584 5529 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt I0119 17:14:36.850866 5529 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/1.27.0-alpha.2+v1.27.0-alpha.1-225-gddd1583244/linux/amd64/kops I0119 17:14:37.703981 5529 local.go:42] ⚙️ ssh-keygen -t ed25519 -N -q -f /tmp/kops/e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io/id_ed25519 I0119 17:14:37.718720 5529 up.go:44] Cleaning up any leaked resources from previous cluster I0119 17:14:37.718922 5529 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/6c0daa24-981c-11ed-824d-f64c9135b4ea/kops toolbox dump --name e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ec2-user I0119 17:14:37.718952 5529 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/6c0daa24-981c-11ed-824d-f64c9135b4ea/kops toolbox dump --name e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ec2-user Error: Cluster.kops.k8s.io "e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io" not found W0119 17:14:38.255390 5529 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1 I0119 17:14:38.255442 5529 down.go:48] /home/prow/go/src/k8s.io/kops/_rundir/6c0daa24-981c-11ed-824d-f64c9135b4ea/kops delete cluster --name e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io --yes I0119 17:14:38.255456 5529 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/6c0daa24-981c-11ed-824d-f64c9135b4ea/kops delete cluster --name e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io --yes Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io" not found I0119 17:14:38.836846 5529 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip 2023/01/19 17:14:38 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 I0119 17:14:38.859906 5529 http.go:37] curl https://ip.jsb.workers.dev I0119 17:14:38.962588 5529 up.go:167] /home/prow/go/src/k8s.io/kops/_rundir/6c0daa24-981c-11ed-824d-f64c9135b4ea/kops create cluster --name e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.26.1 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io/id_ed25519.pub --set cluster.spec.nodePortAccess=0.0.0.0/0 --image=137112412989/amzn2-ami-kernel-5.10-hvm-2.0.20221210.1-x86_64-gp2 --channel=alpha --networking=cilium-eni --container-runtime=containerd --admin-access 35.184.42.228/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones eu-central-1a --master-size c5.large I0119 17:14:38.962641 5529 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/6c0daa24-981c-11ed-824d-f64c9135b4ea/kops create cluster --name e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.26.1 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io/id_ed25519.pub --set cluster.spec.nodePortAccess=0.0.0.0/0 --image=137112412989/amzn2-ami-kernel-5.10-hvm-2.0.20221210.1-x86_64-gp2 --channel=alpha --networking=cilium-eni --container-runtime=containerd --admin-access 35.184.42.228/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones eu-central-1a --master-size c5.large I0119 17:14:39.066665 5566 create_cluster.go:882] Using SSH public key: /tmp/kops/e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io/id_ed25519.pub I0119 17:14:39.580279 5566 new_cluster.go:1338] Cloud Provider ID: "aws" I0119 17:14:40.517289 5566 subnets.go:185] Assigned CIDR 172.20.32.0/19 to subnet eu-central-1a ... skipping 513 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 W0119 17:15:25.955805 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W0119 17:15:36.065593 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W0119 17:15:46.104149 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W0119 17:15:56.139024 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W0119 17:16:06.186966 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W0119 17:16:16.251909 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W0119 17:16:26.292633 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W0119 17:16:36.341826 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W0119 17:16:46.383562 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W0119 17:16:56.419376 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W0119 17:17:06.458044 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W0119 17:17:16.507480 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W0119 17:17:26.545032 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W0119 17:17:36.584410 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W0119 17:17:46.627583 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W0119 17:17:56.766425 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W0119 17:18:06.805024 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W0119 17:18:16.841150 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W0119 17:18:26.882056 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W0119 17:18:36.919446 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W0119 17:18:46.958877 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W0119 17:18:57.000383 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W0119 17:19:07.033732 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W0119 17:19:17.080316 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 9 lines ... Machine i-0ea5d595644e30236 machine "i-0ea5d595644e30236" has not yet joined cluster Pod kube-system/cilium-9f2nw system-node-critical pod "cilium-9f2nw" is not ready (cilium-agent) Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is pending Pod kube-system/coredns-autoscaler-7cb5c5b969-p5m4l system-cluster-critical pod "coredns-autoscaler-7cb5c5b969-p5m4l" is pending Pod kube-system/ebs-csi-node-w6jk6 system-node-critical pod "ebs-csi-node-w6jk6" is pending Validation Failed W0119 17:19:30.418373 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 9 lines ... Machine i-0ea5d595644e30236 machine "i-0ea5d595644e30236" has not yet joined cluster Pod kube-system/cilium-9f2nw system-node-critical pod "cilium-9f2nw" is not ready (cilium-agent) Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is pending Pod kube-system/coredns-autoscaler-7cb5c5b969-p5m4l system-cluster-critical pod "coredns-autoscaler-7cb5c5b969-p5m4l" is pending Pod kube-system/ebs-csi-node-w6jk6 system-node-critical pod "ebs-csi-node-w6jk6" is pending Validation Failed W0119 17:19:42.614503 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 14 lines ... Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is pending Pod kube-system/coredns-autoscaler-7cb5c5b969-p5m4l system-cluster-critical pod "coredns-autoscaler-7cb5c5b969-p5m4l" is pending Pod kube-system/ebs-csi-node-shpd8 system-node-critical pod "ebs-csi-node-shpd8" is pending Pod kube-system/ebs-csi-node-sp7zr system-node-critical pod "ebs-csi-node-sp7zr" is pending Pod kube-system/ebs-csi-node-w6jk6 system-node-critical pod "ebs-csi-node-w6jk6" is pending Validation Failed W0119 17:19:54.796886 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 18 lines ... Pod kube-system/coredns-autoscaler-7cb5c5b969-p5m4l system-cluster-critical pod "coredns-autoscaler-7cb5c5b969-p5m4l" is pending Pod kube-system/ebs-csi-node-5drsr system-node-critical pod "ebs-csi-node-5drsr" is pending Pod kube-system/ebs-csi-node-shpd8 system-node-critical pod "ebs-csi-node-shpd8" is pending Pod kube-system/ebs-csi-node-sp7zr system-node-critical pod "ebs-csi-node-sp7zr" is pending Pod kube-system/ebs-csi-node-wrxqn system-node-critical pod "ebs-csi-node-wrxqn" is pending Validation Failed W0119 17:20:06.888920 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 14 lines ... Pod kube-system/coredns-autoscaler-7cb5c5b969-p5m4l system-cluster-critical pod "coredns-autoscaler-7cb5c5b969-p5m4l" is pending Pod kube-system/ebs-csi-node-5drsr system-node-critical pod "ebs-csi-node-5drsr" is pending Pod kube-system/ebs-csi-node-shpd8 system-node-critical pod "ebs-csi-node-shpd8" is pending Pod kube-system/ebs-csi-node-sp7zr system-node-critical pod "ebs-csi-node-sp7zr" is pending Pod kube-system/ebs-csi-node-wrxqn system-node-critical pod "ebs-csi-node-wrxqn" is pending Validation Failed W0119 17:20:18.983786 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 10 lines ... Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is pending Pod kube-system/ebs-csi-node-5drsr system-node-critical pod "ebs-csi-node-5drsr" is pending Pod kube-system/ebs-csi-node-sp7zr system-node-critical pod "ebs-csi-node-sp7zr" is pending Pod kube-system/ebs-csi-node-wrxqn system-node-critical pod "ebs-csi-node-wrxqn" is pending Validation Failed W0119 17:20:31.153498 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Validation Failed W0119 17:20:43.259551 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Validation Failed W0119 17:20:55.240528 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Validation Failed W0119 17:21:07.276511 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Validation Failed W0119 17:21:19.305683 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Validation Failed W0119 17:21:31.395838 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Validation Failed W0119 17:21:43.529575 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Validation Failed W0119 17:21:55.682069 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Validation Failed W0119 17:22:07.742896 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Validation Failed W0119 17:22:19.761822 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Validation Failed W0119 17:22:31.785939 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Validation Failed W0119 17:22:43.750297 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Validation Failed W0119 17:22:55.688109 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Validation Failed W0119 17:23:07.688810 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Validation Failed W0119 17:23:20.179817 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Validation Failed W0119 17:23:32.272160 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Validation Failed W0119 17:23:44.282446 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Validation Failed W0119 17:23:56.265076 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Validation Failed W0119 17:24:08.260028 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Validation Failed W0119 17:24:20.198937 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Validation Failed W0119 17:24:32.399230 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Validation Failed W0119 17:24:44.408752 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Validation Failed W0119 17:24:56.368012 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Validation Failed W0119 17:25:08.334025 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Validation Failed W0119 17:25:20.335762 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Validation Failed W0119 17:25:32.412584 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Validation Failed W0119 17:25:44.513401 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Validation Failed W0119 17:25:56.503935 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Validation Failed W0119 17:26:08.561928 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Validation Failed W0119 17:26:20.617636 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 8 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Pod kube-system/ebs-csi-node-sp7zr system-node-critical pod "ebs-csi-node-sp7zr" is not ready (ebs-plugin) Validation Failed W0119 17:26:32.605405 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 9 lines ... KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Pod kube-system/ebs-csi-node-5drsr system-node-critical pod "ebs-csi-node-5drsr" is not ready (ebs-plugin) Pod kube-system/ebs-csi-node-sp7zr system-node-critical pod "ebs-csi-node-sp7zr" is not ready (ebs-plugin) Validation Failed W0119 17:26:44.599110 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 9 lines ... KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Pod kube-system/ebs-csi-node-5drsr system-node-critical pod "ebs-csi-node-5drsr" is not ready (ebs-plugin) Pod kube-system/ebs-csi-node-sp7zr system-node-critical pod "ebs-csi-node-sp7zr" is not ready (ebs-plugin) Validation Failed W0119 17:26:56.583156 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 9 lines ... KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Pod kube-system/ebs-csi-node-5drsr system-node-critical pod "ebs-csi-node-5drsr" is not ready (ebs-plugin) Pod kube-system/ebs-csi-node-sp7zr system-node-critical pod "ebs-csi-node-sp7zr" is not ready (ebs-plugin) Validation Failed W0119 17:27:08.714685 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 9 lines ... KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Pod kube-system/ebs-csi-node-5drsr system-node-critical pod "ebs-csi-node-5drsr" is not ready (ebs-plugin) Pod kube-system/ebs-csi-node-sp7zr system-node-critical pod "ebs-csi-node-sp7zr" is not ready (ebs-plugin) Validation Failed W0119 17:27:21.259678 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 9 lines ... KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Pod kube-system/ebs-csi-node-5drsr system-node-critical pod "ebs-csi-node-5drsr" is not ready (ebs-plugin) Pod kube-system/ebs-csi-node-sp7zr system-node-critical pod "ebs-csi-node-sp7zr" is not ready (ebs-plugin) Validation Failed W0119 17:27:33.317911 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 9 lines ... KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Pod kube-system/ebs-csi-node-5drsr system-node-critical pod "ebs-csi-node-5drsr" is not ready (ebs-plugin) Pod kube-system/ebs-csi-node-sp7zr system-node-critical pod "ebs-csi-node-sp7zr" is not ready (ebs-plugin) Validation Failed W0119 17:27:45.385687 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 9 lines ... KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Pod kube-system/ebs-csi-node-5drsr system-node-critical pod "ebs-csi-node-5drsr" is not ready (ebs-plugin) Pod kube-system/ebs-csi-node-sp7zr system-node-critical pod "ebs-csi-node-sp7zr" is not ready (ebs-plugin) Validation Failed W0119 17:27:57.459253 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Validation Failed W0119 17:28:09.438004 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Validation Failed W0119 17:28:21.506987 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Validation Failed W0119 17:28:33.502563 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Validation Failed W0119 17:28:45.584282 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 8 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Pod kube-system/ebs-csi-node-5drsr system-node-critical pod "ebs-csi-node-5drsr" is not ready (ebs-plugin) Validation Failed W0119 17:28:57.520142 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 9 lines ... KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Pod kube-system/ebs-csi-node-5drsr system-node-critical pod "ebs-csi-node-5drsr" is not ready (ebs-plugin) Pod kube-system/ebs-csi-node-sp7zr system-node-critical pod "ebs-csi-node-sp7zr" is not ready (ebs-plugin) Validation Failed W0119 17:29:09.581251 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 9 lines ... KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Pod kube-system/ebs-csi-node-5drsr system-node-critical pod "ebs-csi-node-5drsr" is not ready (ebs-plugin) Pod kube-system/ebs-csi-node-sp7zr system-node-critical pod "ebs-csi-node-sp7zr" is not ready (ebs-plugin) Validation Failed W0119 17:29:21.765918 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 9 lines ... KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Pod kube-system/ebs-csi-node-5drsr system-node-critical pod "ebs-csi-node-5drsr" is not ready (ebs-plugin) Pod kube-system/ebs-csi-node-sp7zr system-node-critical pod "ebs-csi-node-sp7zr" is not ready (ebs-plugin) Validation Failed W0119 17:29:33.787008 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 9 lines ... KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Pod kube-system/ebs-csi-node-5drsr system-node-critical pod "ebs-csi-node-5drsr" is not ready (ebs-plugin) Pod kube-system/ebs-csi-node-sp7zr system-node-critical pod "ebs-csi-node-sp7zr" is not ready (ebs-plugin) Validation Failed W0119 17:29:45.903880 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 9 lines ... KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Pod kube-system/ebs-csi-node-5drsr system-node-critical pod "ebs-csi-node-5drsr" is not ready (ebs-plugin) Pod kube-system/ebs-csi-node-sp7zr system-node-critical pod "ebs-csi-node-sp7zr" is not ready (ebs-plugin) Validation Failed W0119 17:29:57.963570 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 9 lines ... KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Pod kube-system/ebs-csi-node-5drsr system-node-critical pod "ebs-csi-node-5drsr" is not ready (ebs-plugin) Pod kube-system/ebs-csi-node-sp7zr system-node-critical pod "ebs-csi-node-sp7zr" is not ready (ebs-plugin) Validation Failed W0119 17:30:09.987336 5606 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-eu-central-1a ControlPlane c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 9 lines ... KIND NAME MESSAGE Pod kube-system/coredns-559769c974-d95pv system-cluster-critical pod "coredns-559769c974-d95pv" is not ready (coredns) Pod kube-system/coredns-559769c974-khnx7 system-cluster-critical pod "coredns-559769c974-khnx7" is not ready (coredns) Pod kube-system/ebs-csi-node-5drsr system-node-critical pod "ebs-csi-node-5drsr" is not ready (ebs-plugin) Pod kube-system/ebs-csi-node-sp7zr system-node-critical pod "ebs-csi-node-sp7zr" is not ready (ebs-plugin) Validation Failed W0119 17:30:22.052854 5606 validate_cluster.go:232] (will retry): cluster not yet healthy Error: validation failed: wait time exceeded during validation I0119 17:30:32.063220 5529 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/6c0daa24-981c-11ed-824d-f64c9135b4ea/kops toolbox dump --name e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ec2-user I0119 17:30:32.063429 5529 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/6c0daa24-981c-11ed-824d-f64c9135b4ea/kops toolbox dump --name e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ec2-user 2023/01/19 17:30:50 Dumping node i-084dc0daa797be419 2023/01/19 17:30:55 error dumping node i-084dc0daa797be419: error executing command "sysctl -a": Process exited with status 127 2023/01/19 17:30:55 Dumping node i-08abbb6ec3afb3e3a 2023/01/19 17:31:00 error dumping node i-08abbb6ec3afb3e3a: error executing command "sysctl -a": Process exited with status 127 2023/01/19 17:31:00 Dumping node i-0b4a5e1e82db2678d 2023/01/19 17:31:06 error dumping node i-0b4a5e1e82db2678d: error executing command "sysctl -a": Process exited with status 127 2023/01/19 17:31:06 Dumping node i-0c18144c733a1454f 2023/01/19 17:31:11 error dumping node i-0c18144c733a1454f: error executing command "sysctl -a": Process exited with status 127 2023/01/19 17:31:11 Dumping node i-0ea5d595644e30236 2023/01/19 17:31:16 error dumping node i-0ea5d595644e30236: error executing command "sysctl -a": Process exited with status 127 I0119 17:31:16.608007 5529 dumplogs.go:79] /home/prow/go/src/k8s.io/kops/_rundir/6c0daa24-981c-11ed-824d-f64c9135b4ea/kops get cluster --name e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io -o yaml I0119 17:31:16.608051 5529 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/6c0daa24-981c-11ed-824d-f64c9135b4ea/kops get cluster --name e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io -o yaml I0119 17:31:17.210134 5529 dumplogs.go:79] /home/prow/go/src/k8s.io/kops/_rundir/6c0daa24-981c-11ed-824d-f64c9135b4ea/kops get instancegroups --name e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io -o yaml I0119 17:31:17.210170 5529 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/6c0daa24-981c-11ed-824d-f64c9135b4ea/kops get instancegroups --name e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io -o yaml I0119 17:31:18.065976 5529 dumplogs.go:98] kubectl cluster-info dump --all-namespaces -o yaml --output-directory /logs/artifacts/cluster-info I0119 17:31:18.066068 5529 local.go:42] ⚙️ kubectl cluster-info dump --all-namespaces -o yaml --output-directory /logs/artifacts/cluster-info ... skipping 225 lines ... route-table:rtb-06af66ba479760c3d ok vpc:vpc-0f1b5bb9bb097fc41 ok dhcp-options:dopt-07ff19baf85185a0d ok Deleted kubectl config for e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io Deleted cluster: "e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io" Error: exit status 1 + EXIT_VALUE=1 + set +o xtrace