This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-09-16 13:25
Elapsed20m15s
Revisionmaster

No Test Failures!


Error lines from build-log.txt

... skipping 124 lines ...
I0916 13:26:21.079290    4120 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt
I0916 13:26:21.080946    4120 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/1.23.0-alpha.2+v1.23.0-alpha.1-140-g5a6b55d7ba/linux/amd64/kops
I0916 13:26:21.955332    4120 up.go:43] Cleaning up any leaked resources from previous cluster
I0916 13:26:21.955361    4120 dumplogs.go:38] /logs/artifacts/7f7d2f80-16f1-11ec-a0c8-aafcb65c973d/kops toolbox dump --name e2e-a093b3fadd-b172d.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ubuntu
I0916 13:26:21.974658    4138 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0916 13:26:21.974730    4138 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Error: Cluster.kops.k8s.io "e2e-a093b3fadd-b172d.test-cncf-aws.k8s.io" not found
W0916 13:26:22.504474    4120 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0916 13:26:22.504537    4120 down.go:48] /logs/artifacts/7f7d2f80-16f1-11ec-a0c8-aafcb65c973d/kops delete cluster --name e2e-a093b3fadd-b172d.test-cncf-aws.k8s.io --yes
I0916 13:26:22.522925    4149 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0916 13:26:22.523031    4149 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-a093b3fadd-b172d.test-cncf-aws.k8s.io" not found
I0916 13:26:23.061943    4120 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/09/16 13:26:23 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
I0916 13:26:23.070953    4120 http.go:37] curl https://ip.jsb.workers.dev
I0916 13:26:23.172312    4120 up.go:144] /logs/artifacts/7f7d2f80-16f1-11ec-a0c8-aafcb65c973d/kops create cluster --name e2e-a093b3fadd-b172d.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.23.0-alpha.2 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --image=099720109477/ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20210907 --channel=alpha --networking=cilium --container-runtime=containerd --zones=eu-central-1a --node-size=m6g.large --master-size=m6g.large --admin-access 35.239.195.150/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48
I0916 13:26:23.189870    4159 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0916 13:26:23.189966    4159 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I0916 13:26:23.215118    4159 create_cluster.go:827] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0916 13:26:23.775079    4159 new_cluster.go:1052]  Cloud Provider ID = aws
... skipping 31 lines ...

I0916 13:26:49.181033    4120 up.go:181] /logs/artifacts/7f7d2f80-16f1-11ec-a0c8-aafcb65c973d/kops validate cluster --name e2e-a093b3fadd-b172d.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0916 13:26:49.198602    4179 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0916 13:26:49.199441    4179 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-a093b3fadd-b172d.test-cncf-aws.k8s.io

W0916 13:26:50.794308    4179 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-a093b3fadd-b172d.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0916 13:27:00.869684    4179 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-a093b3fadd-b172d.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	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 master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0916 13:27:10.933729    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	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 master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0916 13:27:20.988225    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	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 master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0916 13:27:31.018751    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	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 master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0916 13:27:41.078757    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	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 master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0916 13:27:51.127094    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	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 master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0916 13:28:01.194839    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
W0916 13:28:11.255498    4179 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-a093b3fadd-b172d.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	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 master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0916 13:28:21.286219    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	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 master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0916 13:28:31.318306    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	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 master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0916 13:28:41.353775    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
W0916 13:28:51.626290    4179 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-a093b3fadd-b172d.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	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 master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0916 13:29:01.677715    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	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 master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0916 13:29:11.725777    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	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 master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0916 13:29:21.763413    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	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 master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0916 13:29:31.798753    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	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 master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0916 13:29:41.863254    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	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 master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0916 13:29:51.990615    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	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 master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0916 13:30:02.022136    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	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 master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0916 13:30:12.054189    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	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 master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0916 13:30:22.086646    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	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 master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0916 13:30:32.132972    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	4	4	eu-central-1a

... skipping 10 lines ...
Pod	kube-system/cilium-5rj7k			system-node-critical pod "cilium-5rj7k" is not ready (cilium-agent)
Pod	kube-system/coredns-5dc785954d-82jjg		system-cluster-critical pod "coredns-5dc785954d-82jjg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8r4gb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8r4gb" is pending
Pod	kube-system/ebs-csi-controller-bfd5c8576-7qpzz	system-cluster-critical pod "ebs-csi-controller-bfd5c8576-7qpzz" is pending
Pod	kube-system/ebs-csi-node-gfhcn			system-node-critical pod "ebs-csi-node-gfhcn" is pending

Validation Failed
W0916 13:30:44.934867    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	4	4	eu-central-1a

... skipping 10 lines ...
Pod	kube-system/cilium-5rj7k			system-node-critical pod "cilium-5rj7k" is not ready (cilium-agent)
Pod	kube-system/coredns-5dc785954d-82jjg		system-cluster-critical pod "coredns-5dc785954d-82jjg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8r4gb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8r4gb" is pending
Pod	kube-system/ebs-csi-controller-bfd5c8576-7qpzz	system-cluster-critical pod "ebs-csi-controller-bfd5c8576-7qpzz" is pending
Pod	kube-system/ebs-csi-node-gfhcn			system-node-critical pod "ebs-csi-node-gfhcn" is pending

Validation Failed
W0916 13:30:57.076686    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	4	4	eu-central-1a

... skipping 22 lines ...
Pod	kube-system/ebs-csi-node-bdpwv			system-node-critical pod "ebs-csi-node-bdpwv" is pending
Pod	kube-system/ebs-csi-node-gfhcn			system-node-critical pod "ebs-csi-node-gfhcn" is pending
Pod	kube-system/ebs-csi-node-sq85z			system-node-critical pod "ebs-csi-node-sq85z" is pending
Pod	kube-system/ebs-csi-node-tvlmq			system-node-critical pod "ebs-csi-node-tvlmq" is pending
Pod	kube-system/ebs-csi-node-wgzgc			system-node-critical pod "ebs-csi-node-wgzgc" is pending

Validation Failed
W0916 13:31:09.254035    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	4	4	eu-central-1a

... skipping 20 lines ...
Pod	kube-system/ebs-csi-node-bdpwv			system-node-critical pod "ebs-csi-node-bdpwv" is pending
Pod	kube-system/ebs-csi-node-gfhcn			system-node-critical pod "ebs-csi-node-gfhcn" is pending
Pod	kube-system/ebs-csi-node-sq85z			system-node-critical pod "ebs-csi-node-sq85z" is pending
Pod	kube-system/ebs-csi-node-tvlmq			system-node-critical pod "ebs-csi-node-tvlmq" is pending
Pod	kube-system/ebs-csi-node-wgzgc			system-node-critical pod "ebs-csi-node-wgzgc" is pending

Validation Failed
W0916 13:31:21.322705    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	4	4	eu-central-1a

... skipping 13 lines ...
Pod	kube-system/ebs-csi-node-bdpwv			system-node-critical pod "ebs-csi-node-bdpwv" is pending
Pod	kube-system/ebs-csi-node-gfhcn			system-node-critical pod "ebs-csi-node-gfhcn" is pending
Pod	kube-system/ebs-csi-node-sq85z			system-node-critical pod "ebs-csi-node-sq85z" is pending
Pod	kube-system/ebs-csi-node-tvlmq			system-node-critical pod "ebs-csi-node-tvlmq" is pending
Pod	kube-system/ebs-csi-node-wgzgc			system-node-critical pod "ebs-csi-node-wgzgc" is pending

Validation Failed
W0916 13:31:33.229115    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	4	4	eu-central-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5dc785954d-wgt7w		system-cluster-critical pod "coredns-5dc785954d-wgt7w" is pending
Pod	kube-system/ebs-csi-controller-bfd5c8576-7qpzz	system-cluster-critical pod "ebs-csi-controller-bfd5c8576-7qpzz" is pending
Pod	kube-system/ebs-csi-node-gfhcn			system-node-critical pod "ebs-csi-node-gfhcn" is pending

Validation Failed
W0916 13:31:45.196061    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	4	4	eu-central-1a

... skipping 81 lines ...
ip-172-20-55-39.eu-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 13:32:57.371268    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	4	4	eu-central-1a

... skipping 6 lines ...
ip-172-20-55-39.eu-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 13:33:09.359255    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	4	4	eu-central-1a

... skipping 6 lines ...
ip-172-20-55-39.eu-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 13:33:21.405602    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	4	4	eu-central-1a

... skipping 6 lines ...
ip-172-20-55-39.eu-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 13:33:33.426880    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	4	4	eu-central-1a

... skipping 6 lines ...
ip-172-20-55-39.eu-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 13:33:45.401781    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	4	4	eu-central-1a

... skipping 6 lines ...
ip-172-20-55-39.eu-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 13:33:57.295847    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	4	4	eu-central-1a

... skipping 6 lines ...
ip-172-20-55-39.eu-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 13:34:09.149025    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	4	4	eu-central-1a

... skipping 6 lines ...
ip-172-20-55-39.eu-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 13:34:21.205416    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	4	4	eu-central-1a

... skipping 51 lines ...
ip-172-20-55-39.eu-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 13:35:09.633221    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	4	4	eu-central-1a

... skipping 6 lines ...
ip-172-20-55-39.eu-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 13:35:21.619751    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	4	4	eu-central-1a

... skipping 6 lines ...
ip-172-20-55-39.eu-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 13:35:33.617495    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	4	4	eu-central-1a

... skipping 6 lines ...
ip-172-20-55-39.eu-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 13:35:45.634967    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	4	4	eu-central-1a

... skipping 6 lines ...
ip-172-20-55-39.eu-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 13:35:57.621340    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	4	4	eu-central-1a

... skipping 6 lines ...
ip-172-20-55-39.eu-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 13:36:09.748049    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	4	4	eu-central-1a

... skipping 6 lines ...
ip-172-20-55-39.eu-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 13:36:21.720220    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	4	4	eu-central-1a

... skipping 6 lines ...
ip-172-20-55-39.eu-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 13:36:33.821304    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	4	4	eu-central-1a

... skipping 6 lines ...
ip-172-20-55-39.eu-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 13:36:45.795914    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	4	4	eu-central-1a

... skipping 6 lines ...
ip-172-20-55-39.eu-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 13:36:57.702140    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	4	4	eu-central-1a

... skipping 6 lines ...
ip-172-20-55-39.eu-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 13:37:09.636274    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	4	4	eu-central-1a

... skipping 6 lines ...
ip-172-20-55-39.eu-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 13:37:21.576686    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	4	4	eu-central-1a

... skipping 6 lines ...
ip-172-20-55-39.eu-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 13:37:33.482422    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	4	4	eu-central-1a

... skipping 51 lines ...
ip-172-20-55-39.eu-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 13:38:21.391161    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	4	4	eu-central-1a

... skipping 6 lines ...
ip-172-20-55-39.eu-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 13:38:33.358603    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	4	4	eu-central-1a

... skipping 6 lines ...
ip-172-20-55-39.eu-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 13:38:45.812007    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	4	4	eu-central-1a

... skipping 6 lines ...
ip-172-20-55-39.eu-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 13:38:57.722517    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	4	4	eu-central-1a

... skipping 6 lines ...
ip-172-20-55-39.eu-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 13:39:09.706157    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	4	4	eu-central-1a

... skipping 6 lines ...
ip-172-20-55-39.eu-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 13:39:21.678878    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	4	4	eu-central-1a

... skipping 6 lines ...
ip-172-20-55-39.eu-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 13:39:33.796498    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	4	4	eu-central-1a

... skipping 6 lines ...
ip-172-20-55-39.eu-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 13:39:45.748421    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	4	4	eu-central-1a

... skipping 6 lines ...
ip-172-20-55-39.eu-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 13:39:57.659434    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	4	4	eu-central-1a

... skipping 6 lines ...
ip-172-20-55-39.eu-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 13:40:09.913097    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	4	4	eu-central-1a

... skipping 6 lines ...
ip-172-20-55-39.eu-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 13:40:21.976670    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	4	4	eu-central-1a

... skipping 6 lines ...
ip-172-20-55-39.eu-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 13:40:34.048016    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	4	4	eu-central-1a

... skipping 6 lines ...
ip-172-20-55-39.eu-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 13:40:46.095493    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	4	4	eu-central-1a

... skipping 6 lines ...
ip-172-20-55-39.eu-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 13:40:57.961922    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	4	4	eu-central-1a

... skipping 6 lines ...
ip-172-20-55-39.eu-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 13:41:10.030697    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	4	4	eu-central-1a

... skipping 6 lines ...
ip-172-20-55-39.eu-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 13:41:22.025801    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	4	4	eu-central-1a

... skipping 6 lines ...
ip-172-20-55-39.eu-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 13:41:33.884586    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	m6g.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	m6g.large	4	4	eu-central-1a

... skipping 6 lines ...
ip-172-20-55-39.eu-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-37-83.eu-central-1.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 13:41:45.859290    4179 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
I0916 13:41:55.872900    4120 dumplogs.go:38] /logs/artifacts/7f7d2f80-16f1-11ec-a0c8-aafcb65c973d/kops toolbox dump --name e2e-a093b3fadd-b172d.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ubuntu
I0916 13:41:55.893106    4191 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0916 13:41:55.893210    4191 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
2021/09/16 13:42:07 Dumping node ip-172-20-37-83.eu-central-1.compute.internal
2021/09/16 13:42:13 Dumping node ip-172-20-38-1.eu-central-1.compute.internal
2021/09/16 13:42:18 Dumping node ip-172-20-43-83.eu-central-1.compute.internal
... skipping 1459 lines ...
route-table:rtb-01b32783231c9a03c	ok
vpc:vpc-017102cfa49e42edc	ok
dhcp-options:dopt-013d79e374336db68	ok
Deleted kubectl config for e2e-a093b3fadd-b172d.test-cncf-aws.k8s.io

Deleted cluster: "e2e-a093b3fadd-b172d.test-cncf-aws.k8s.io"
Error: exit status 1
+ EXIT_VALUE=1
+ set +o xtrace