e2e-kops-grid-cilium-eni-amzn2-k26 #1611047955668668416
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 1 failed / 1 succeeded |
| Started | |
| Elapsed | 20m38s |
| Revision | master |
exit status 1
from junit_runner.xml
Filter through log files | View test history on testgrid
kubetest2 Down
... skipping 135 lines ... I0105 17:15:01.918687 5589 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt I0105 17:15:01.920355 5589 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/1.27.0-alpha.2+v1.27.0-alpha.1-108-ga3f4f97a53/linux/amd64/kops I0105 17:15:02.937012 5589 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 I0105 17:15:02.950173 5589 up.go:44] Cleaning up any leaked resources from previous cluster I0105 17:15:02.950382 5589 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/1c413e82-8d1c-11ed-b023-4ae401093a81/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 I0105 17:15:02.950501 5589 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/1c413e82-8d1c-11ed-b023-4ae401093a81/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 W0105 17:15:03.512563 5589 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1 I0105 17:15:03.512616 5589 down.go:48] /home/prow/go/src/k8s.io/kops/_rundir/1c413e82-8d1c-11ed-b023-4ae401093a81/kops delete cluster --name e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io --yes I0105 17:15:03.512628 5589 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/1c413e82-8d1c-11ed-b023-4ae401093a81/kops delete cluster --name e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io --yes I0105 17:15:03.548608 5622 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io" not found I0105 17:15:04.007733 5589 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip 2023/01/05 17:15:04 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 I0105 17:15:04.022022 5589 http.go:37] curl https://ip.jsb.workers.dev I0105 17:15:04.127030 5589 up.go:167] /home/prow/go/src/k8s.io/kops/_rundir/1c413e82-8d1c-11ed-b023-4ae401093a81/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.0 --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 104.198.245.181/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones eu-central-1a --master-size c5.large I0105 17:15:04.127392 5589 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/1c413e82-8d1c-11ed-b023-4ae401093a81/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.0 --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 104.198.245.181/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones eu-central-1a --master-size c5.large I0105 17:15:04.160697 5633 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true I0105 17:15:04.179628 5633 create_cluster.go:884] Using SSH public key: /tmp/kops/e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io/id_ed25519.pub I0105 17:15:04.680405 5633 new_cluster.go:1327] Cloud Provider ID: "aws" ... skipping 516 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 W0105 17:15:52.814573 5669 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 W0105 17:16:02.855456 5669 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 W0105 17:16:12.891127 5669 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 W0105 17:16:22.926605 5669 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 W0105 17:16:32.967607 5669 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 W0105 17:16:43.006196 5669 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 W0105 17:16:53.042433 5669 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 W0105 17:17:03.077446 5669 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 W0105 17:17:13.110768 5669 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 W0105 17:17:23.158572 5669 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 W0105 17:17:33.201768 5669 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 W0105 17:17:43.300347 5669 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 W0105 17:17:53.337094 5669 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 W0105 17:18:03.400019 5669 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 W0105 17:18:13.441622 5669 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 W0105 17:18:23.485074 5669 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 W0105 17:18:33.534667 5669 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/cilium-md6v9 system-node-critical pod "cilium-md6v9" is not ready (cilium-agent) Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is pending Pod kube-system/coredns-autoscaler-7cb5c5b969-qf7wh system-cluster-critical pod "coredns-autoscaler-7cb5c5b969-qf7wh" is pending Pod kube-system/ebs-csi-controller-86d44d7948-ht6lh system-cluster-critical pod "ebs-csi-controller-86d44d7948-ht6lh" is pending Pod kube-system/ebs-csi-node-95ppq system-node-critical pod "ebs-csi-node-95ppq" is pending Validation Failed W0105 17:18:46.433916 5669 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 22 lines ... Pod kube-system/ebs-csi-node-6xf4b system-node-critical pod "ebs-csi-node-6xf4b" is pending Pod kube-system/ebs-csi-node-95ppq system-node-critical pod "ebs-csi-node-95ppq" is pending Pod kube-system/ebs-csi-node-lm7gc system-node-critical pod "ebs-csi-node-lm7gc" is pending Pod kube-system/ebs-csi-node-rntx7 system-node-critical pod "ebs-csi-node-rntx7" is pending Pod kube-system/ebs-csi-node-xsqdn system-node-critical pod "ebs-csi-node-xsqdn" is pending Validation Failed W0105 17:18:58.492364 5669 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 17 lines ... Pod kube-system/ebs-csi-node-6xf4b system-node-critical pod "ebs-csi-node-6xf4b" is pending Pod kube-system/ebs-csi-node-95ppq system-node-critical pod "ebs-csi-node-95ppq" is pending Pod kube-system/ebs-csi-node-lm7gc system-node-critical pod "ebs-csi-node-lm7gc" is pending Pod kube-system/ebs-csi-node-rntx7 system-node-critical pod "ebs-csi-node-rntx7" is pending Pod kube-system/ebs-csi-node-xsqdn system-node-critical pod "ebs-csi-node-xsqdn" is pending Validation Failed W0105 17:19:10.582871 5669 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 12 lines ... Pod kube-system/ebs-csi-controller-86d44d7948-ht6lh system-cluster-critical pod "ebs-csi-controller-86d44d7948-ht6lh" is pending Pod kube-system/ebs-csi-node-6xf4b system-node-critical pod "ebs-csi-node-6xf4b" is pending Pod kube-system/ebs-csi-node-lm7gc system-node-critical pod "ebs-csi-node-lm7gc" is pending Pod kube-system/ebs-csi-node-rntx7 system-node-critical pod "ebs-csi-node-rntx7" is pending Pod kube-system/ebs-csi-node-xsqdn system-node-critical pod "ebs-csi-node-xsqdn" is pending Validation Failed W0105 17:19:22.577683 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:19:34.742956 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:19:46.848084 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:19:58.896550 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:20:11.027470 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:20:23.008512 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:20:35.167764 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:20:47.308454 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:20:59.429833 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:21:11.396260 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:21:23.527933 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:21:36.399083 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:21:48.376603 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:22:00.484724 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:22:12.471758 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:22:24.365743 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:22:36.662262 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:22:49.013851 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:23:01.033516 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:23:12.968914 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:23:24.979813 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:23:37.097221 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:23:49.142562 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:24:01.148898 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:24:13.188340 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:24:25.183329 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:24:37.212357 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:24:49.242948 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:25:01.207234 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:25:13.242377 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:25:25.291230 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:25:37.297847 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:25:49.306767 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:26:01.289121 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:26:13.457648 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:26:25.576943 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:26:37.959261 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:26:50.020665 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:27:02.035955 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:27:14.025184 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:27:26.088905 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:27:38.165777 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:27:50.279340 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:28:02.329186 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:28:14.595401 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:28:26.766222 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:28:38.943641 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:28:51.057752 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:29:03.167107 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:29:15.179497 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:29:27.195835 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:29:39.225755 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:29:51.262144 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:30:03.543910 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:30:15.546734 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:30:27.940629 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:30:39.879960 5669 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 6 lines ... i-0e452c60406f46c83 node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-559769c974-gmtqj system-cluster-critical pod "coredns-559769c974-gmtqj" is not ready (coredns) Validation Failed W0105 17:30:51.886480 5669 validate_cluster.go:232] (will retry): cluster not yet healthy Error: validation failed: wait time exceeded during validation I0105 17:31:01.897423 5589 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/1c413e82-8d1c-11ed-b023-4ae401093a81/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 I0105 17:31:01.897480 5589 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/1c413e82-8d1c-11ed-b023-4ae401093a81/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 I0105 17:31:46.938179 5589 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/1c413e82-8d1c-11ed-b023-4ae401093a81/kops get cluster --name e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io -o yaml I0105 17:31:46.938239 5589 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/1c413e82-8d1c-11ed-b023-4ae401093a81/kops get cluster --name e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io -o yaml I0105 17:31:47.447884 5589 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/1c413e82-8d1c-11ed-b023-4ae401093a81/kops get instancegroups --name e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io -o yaml I0105 17:31:47.447918 5589 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/1c413e82-8d1c-11ed-b023-4ae401093a81/kops get instancegroups --name e2e-e2e-kops-grid-cilium-eni-amzn2-k26.test-cncf-aws.k8s.io -o yaml ... skipping 266 lines ... route-table:rtb-0e848ba609bde6aea ok vpc:vpc-09b9045c7f7fac8c2 ok dhcp-options:dopt-08405fb838a9bd689 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