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

No Test Failures!


Error lines from build-log.txt

... skipping 124 lines ...
I0915 13:26:34.944063    4097 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt
I0915 13:26:34.945666    4097 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/1.23.0-alpha.2+v1.23.0-alpha.1-136-gb4ba59993e/linux/amd64/kops
I0915 13:26:36.000690    4097 up.go:43] Cleaning up any leaked resources from previous cluster
I0915 13:26:36.000853    4097 dumplogs.go:38] /logs/artifacts/5c4766eb-1628-11ec-ae24-a216a961216b/kops toolbox dump --name e2e-029ff09590-b172d.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ubuntu
I0915 13:26:36.022176    4117 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0915 13:26:36.022330    4117 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Error: Cluster.kops.k8s.io "e2e-029ff09590-b172d.test-cncf-aws.k8s.io" not found
W0915 13:26:36.609259    4097 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0915 13:26:36.609310    4097 down.go:48] /logs/artifacts/5c4766eb-1628-11ec-ae24-a216a961216b/kops delete cluster --name e2e-029ff09590-b172d.test-cncf-aws.k8s.io --yes
I0915 13:26:36.626872    4127 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0915 13:26:36.627011    4127 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-029ff09590-b172d.test-cncf-aws.k8s.io" not found
I0915 13:26:37.176755    4097 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/09/15 13:26:37 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
I0915 13:26:37.185202    4097 http.go:37] curl https://ip.jsb.workers.dev
I0915 13:26:37.274234    4097 up.go:144] /logs/artifacts/5c4766eb-1628-11ec-ae24-a216a961216b/kops create cluster --name e2e-029ff09590-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 34.70.165.211/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48
I0915 13:26:37.294679    4136 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0915 13:26:37.295675    4136 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I0915 13:26:37.321066    4136 create_cluster.go:827] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0915 13:26:37.935823    4136 new_cluster.go:1052]  Cloud Provider ID = aws
... skipping 31 lines ...

I0915 13:27:03.326905    4097 up.go:181] /logs/artifacts/5c4766eb-1628-11ec-ae24-a216a961216b/kops validate cluster --name e2e-029ff09590-b172d.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0915 13:27:03.344824    4157 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0915 13:27:03.344937    4157 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-029ff09590-b172d.test-cncf-aws.k8s.io

W0915 13:27:04.783864    4157 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-029ff09590-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
W0915 13:27:14.823069    4157 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
W0915 13:27:24.868057    4157 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
W0915 13:27:34.902612    4157 validate_cluster.go:232] (will retry): cluster not yet healthy
W0915 13:27:44.940151    4157 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-029ff09590-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
W0915 13:27:54.969972    4157 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
W0915 13:28:05.140056    4157 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
W0915 13:28:15.172022    4157 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
W0915 13:28:25.203901    4157 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
W0915 13:28:35.248943    4157 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
W0915 13:28:45.296344    4157 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
W0915 13:28:55.340848    4157 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
W0915 13:29:05.370718    4157 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
W0915 13:29:15.404137    4157 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
W0915 13:29:25.481852    4157 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
W0915 13:29:35.571964    4157 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
W0915 13:29:45.622113    4157 validate_cluster.go:232] (will retry): cluster not yet healthy
W0915 13:29:55.794365    4157 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-029ff09590-b172d.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0915 13:30:05.845208    4157 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-029ff09590-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
W0915 13:30:15.897768    4157 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
W0915 13:30:25.943554    4157 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
W0915 13:30:35.989285    4157 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
W0915 13:30:46.025306    4157 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
W0915 13:30:56.124791    4157 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-qrt2g			system-node-critical pod "cilium-qrt2g" is not ready (cilium-agent)
Pod	kube-system/coredns-5dc785954d-998hq		system-cluster-critical pod "coredns-5dc785954d-998hq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lgflp	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lgflp" is pending
Pod	kube-system/ebs-csi-controller-774f7c8cf4-zlcm2	system-cluster-critical pod "ebs-csi-controller-774f7c8cf4-zlcm2" is pending
Pod	kube-system/ebs-csi-node-zhlln			system-node-critical pod "ebs-csi-node-zhlln" is pending

Validation Failed
W0915 13:31:09.186329    4157 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 21 lines ...
Pod	kube-system/ebs-csi-node-94trv			system-node-critical pod "ebs-csi-node-94trv" is pending
Pod	kube-system/ebs-csi-node-9tt8t			system-node-critical pod "ebs-csi-node-9tt8t" is pending
Pod	kube-system/ebs-csi-node-kq2wt			system-node-critical pod "ebs-csi-node-kq2wt" is pending
Pod	kube-system/ebs-csi-node-vz62z			system-node-critical pod "ebs-csi-node-vz62z" is pending
Pod	kube-system/ebs-csi-node-zhlln			system-node-critical pod "ebs-csi-node-zhlln" is pending

Validation Failed
W0915 13:31:21.348810    4157 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 21 lines ...
Pod	kube-system/ebs-csi-node-94trv			system-node-critical pod "ebs-csi-node-94trv" is pending
Pod	kube-system/ebs-csi-node-9tt8t			system-node-critical pod "ebs-csi-node-9tt8t" is pending
Pod	kube-system/ebs-csi-node-kq2wt			system-node-critical pod "ebs-csi-node-kq2wt" is pending
Pod	kube-system/ebs-csi-node-vz62z			system-node-critical pod "ebs-csi-node-vz62z" is pending
Pod	kube-system/ebs-csi-node-zhlln			system-node-critical pod "ebs-csi-node-zhlln" is pending

Validation Failed
W0915 13:31:33.439356    4157 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 14 lines ...
Pod	kube-system/ebs-csi-node-94trv			system-node-critical pod "ebs-csi-node-94trv" is pending
Pod	kube-system/ebs-csi-node-9tt8t			system-node-critical pod "ebs-csi-node-9tt8t" is pending
Pod	kube-system/ebs-csi-node-kq2wt			system-node-critical pod "ebs-csi-node-kq2wt" is pending
Pod	kube-system/ebs-csi-node-vz62z			system-node-critical pod "ebs-csi-node-vz62z" is pending
Pod	kube-system/ebs-csi-node-zhlln			system-node-critical pod "ebs-csi-node-zhlln" is pending

Validation Failed
W0915 13:31:45.493898    4157 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 12 lines ...
Pod	kube-system/ebs-csi-node-94trv			system-node-critical pod "ebs-csi-node-94trv" is pending
Pod	kube-system/ebs-csi-node-9tt8t			system-node-critical pod "ebs-csi-node-9tt8t" is pending
Pod	kube-system/ebs-csi-node-kq2wt			system-node-critical pod "ebs-csi-node-kq2wt" is pending
Pod	kube-system/ebs-csi-node-vz62z			system-node-critical pod "ebs-csi-node-vz62z" is pending
Pod	kube-system/ebs-csi-node-zhlln			system-node-critical pod "ebs-csi-node-zhlln" is pending

Validation Failed
W0915 13:31:57.394038    4157 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-52-150.eu-central-1.compute.internal	master	True

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

Validation Failed
W0915 13:33:09.722898    4157 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-52-150.eu-central-1.compute.internal	master	True

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

Validation Failed
W0915 13:33:21.594460    4157 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-52-150.eu-central-1.compute.internal	master	True

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

Validation Failed
W0915 13:33:33.573113    4157 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-52-150.eu-central-1.compute.internal	master	True

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

Validation Failed
W0915 13:33:45.728772    4157 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-52-150.eu-central-1.compute.internal	master	True

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

Validation Failed
W0915 13:33:57.864424    4157 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-52-150.eu-central-1.compute.internal	master	True

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

Validation Failed
W0915 13:34:09.881781    4157 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-52-150.eu-central-1.compute.internal	master	True

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

Validation Failed
W0915 13:34:21.931543    4157 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-52-150.eu-central-1.compute.internal	master	True

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

Validation Failed
W0915 13:34:34.167310    4157 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-52-150.eu-central-1.compute.internal	master	True

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

Validation Failed
W0915 13:35:22.763619    4157 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-52-150.eu-central-1.compute.internal	master	True

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

Validation Failed
W0915 13:35:34.799115    4157 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-52-150.eu-central-1.compute.internal	master	True

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

Validation Failed
W0915 13:35:46.852089    4157 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-52-150.eu-central-1.compute.internal	master	True

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

Validation Failed
W0915 13:35:59.082722    4157 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-52-150.eu-central-1.compute.internal	master	True

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

Validation Failed
W0915 13:36:11.034887    4157 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-52-150.eu-central-1.compute.internal	master	True

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

Validation Failed
W0915 13:36:22.965823    4157 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-52-150.eu-central-1.compute.internal	master	True

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

Validation Failed
W0915 13:36:35.476598    4157 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-52-150.eu-central-1.compute.internal	master	True

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

Validation Failed
W0915 13:36:47.435234    4157 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-52-150.eu-central-1.compute.internal	master	True

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

Validation Failed
W0915 13:36:59.365203    4157 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-52-150.eu-central-1.compute.internal	master	True

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

Validation Failed
W0915 13:37:12.007915    4157 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-52-150.eu-central-1.compute.internal	master	True

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

Validation Failed
W0915 13:37:24.259286    4157 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-52-150.eu-central-1.compute.internal	master	True

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

Validation Failed
W0915 13:37:36.220641    4157 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-52-150.eu-central-1.compute.internal	master	True

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

Validation Failed
W0915 13:37:48.288690    4157 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-52-150.eu-central-1.compute.internal	master	True

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

Validation Failed
W0915 13:38:36.294593    4157 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-52-150.eu-central-1.compute.internal	master	True

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

Validation Failed
W0915 13:38:48.231205    4157 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-52-150.eu-central-1.compute.internal	master	True

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

Validation Failed
W0915 13:39:00.575135    4157 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-52-150.eu-central-1.compute.internal	master	True

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

Validation Failed
W0915 13:39:12.523993    4157 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-52-150.eu-central-1.compute.internal	master	True

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

Validation Failed
W0915 13:39:24.615429    4157 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-52-150.eu-central-1.compute.internal	master	True

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

Validation Failed
W0915 13:39:36.599626    4157 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-52-150.eu-central-1.compute.internal	master	True

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

Validation Failed
W0915 13:39:48.532584    4157 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-52-150.eu-central-1.compute.internal	master	True

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

Validation Failed
W0915 13:40:00.449488    4157 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-52-150.eu-central-1.compute.internal	master	True

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

Validation Failed
W0915 13:40:12.429096    4157 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-52-150.eu-central-1.compute.internal	master	True

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

Validation Failed
W0915 13:40:24.379059    4157 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-52-150.eu-central-1.compute.internal	master	True

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

Validation Failed
W0915 13:40:36.318086    4157 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-52-150.eu-central-1.compute.internal	master	True

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

Validation Failed
W0915 13:40:48.300948    4157 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-52-150.eu-central-1.compute.internal	master	True

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

Validation Failed
W0915 13:41:00.188462    4157 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-52-150.eu-central-1.compute.internal	master	True

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

Validation Failed
W0915 13:41:12.353958    4157 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-52-150.eu-central-1.compute.internal	master	True

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

Validation Failed
W0915 13:41:24.616200    4157 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-52-150.eu-central-1.compute.internal	master	True

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

Validation Failed
W0915 13:41:36.535343    4157 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-52-150.eu-central-1.compute.internal	master	True

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

Validation Failed
W0915 13:41:48.539582    4157 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-52-150.eu-central-1.compute.internal	master	True

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

Validation Failed
W0915 13:42:00.555226    4157 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
I0915 13:42:10.561693    4097 dumplogs.go:38] /logs/artifacts/5c4766eb-1628-11ec-ae24-a216a961216b/kops toolbox dump --name e2e-029ff09590-b172d.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ubuntu
I0915 13:42:10.582871    4169 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0915 13:42:10.583004    4169 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
2021/09/15 13:42:21 Dumping node ip-172-20-32-155.eu-central-1.compute.internal
2021/09/15 13:42:26 Dumping node ip-172-20-40-182.eu-central-1.compute.internal
2021/09/15 13:42:30 Dumping node ip-172-20-46-108.eu-central-1.compute.internal
... skipping 1451 lines ...
route-table:rtb-0569cd9709c153f54	ok
vpc:vpc-07755d9c605885e30	ok
dhcp-options:dopt-0d08c03c8b684aecc	ok
Deleted kubectl config for e2e-029ff09590-b172d.test-cncf-aws.k8s.io

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