This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 5 succeeded
Started2021-10-10 19:10
Elapsed18m2s
Revision
job-versionv1.23.0-alpha.3.249+80056f73a614b2
kubetest-version
revisionv1.23.0-alpha.3.249+80056f73a614b2

Test Failures


kubetest Up 15m33s

kops validate cluster failed: error during /tmp/kops3340584361/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m: exit status 1
				from junit_runner.xml

Filter through log files | View test history on testgrid


Show 5 Passed Tests

Error lines from build-log.txt

Activated service account credentials for: [pr-kubekins@kubernetes-jenkins-pull.iam.gserviceaccount.com]
fatal: not a git repository (or any of the parent directories): .git
+ WRAPPED_COMMAND_PID=31
+ /workspace/scenarios/kubernetes_e2e.py --cluster=e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --deployment=kops --env=KOPS_ARCH=amd64 --env=KUBE_SSH_USER=ec2-user --env=KOPS_RUN_TOO_NEW_VERSION=1 --extract=ci/latest --ginkgo-parallel --kops-image=309956199498/RHEL-7.8_HVM_GA-20200225-x86_64-1-Hourly2-GP2 --kops-args=--master-image=137112412989/amzn2-ami-hvm-2.0.20200617.0-x86_64-gp2 --kops-overrides=spec.docker.selinuxEnabled=true --kops-priority-path=/workspace/kubernetes/platforms/linux/amd64 --kops-ssh-user=ec2-user --kops-version=https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt --provider=aws '--test_args=--ginkgo.focus=\[sig-storage\].*\[Slow\] --ginkgo.skip=\[Serial\]|\[Disruptive\]|\[Flaky\]|\[Feature:.+\] --minStartupPods=8' --timeout=120m
+ wait 31
starts with local mode
Environment:
ARTIFACTS=/logs/artifacts
... skipping 156 lines ...
md5sum(kubernetes-test-linux-amd64.tar.gz)=f94333404bad0f981b14ecdee09cf682
sha512sum(kubernetes-test-linux-amd64.tar.gz)=f4a8b8b91044ed753e57bcfa93cf37c0426b62267c72868ec0f73e705152a097abefdc1790a8cde4ff240cc2c6d31ba64766660416aab65c6a830b4c28effdfb

Extracting /workspace/kubernetes/test/kubernetes-test-linux-amd64.tar.gz into /workspace/kubernetes/platforms/linux/amd64
2021/10/10 19:11:05 process.go:155: Step './get-kube.sh' finished in 29.937532625s
2021/10/10 19:11:05 process.go:153: Running: /tmp/kops3340584361/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io
Error: cluster not found "e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io"
2021/10/10 19:11:06 process.go:155: Step '/tmp/kops3340584361/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 555.251147ms
2021/10/10 19:11:06 util.go:42: curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/10 19:11:06 kops.go:514: 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
2021/10/10 19:11:06 util.go:68: curl https://ip.jsb.workers.dev
2021/10/10 19:11:06 kops.go:439: Using external IP for admin access: 35.193.93.145/32
2021/10/10 19:11:06 process.go:153: Running: /tmp/kops3340584361/kops create cluster --name e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --ssh-public-key /workspace/.ssh/kube_aws_rsa.pub --node-count 4 --node-volume-size 48 --master-volume-size 48 --master-count 1 --zones eu-central-1a --master-size c5.large --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.23.0-alpha.3.249+80056f73a614b2 --admin-access 35.193.93.145/32 --image 309956199498/RHEL-7.8_HVM_GA-20200225-x86_64-1-Hourly2-GP2 --cloud aws --master-image=137112412989/amzn2-ami-hvm-2.0.20200617.0-x86_64-gp2 --override spec.docker.selinuxEnabled=true,cluster.spec.nodePortAccess=0.0.0.0/0 --yes
I1010 19:11:06.426902     990 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1010 19:11:06.451501     990 create_cluster.go:838] Using SSH public key: /workspace/.ssh/kube_aws_rsa.pub
I1010 19:11:06.949020     990 new_cluster.go:1077]  Cloud Provider ID = aws
... skipping 31 lines ...

2021/10/10 19:11:31 process.go:155: Step '/tmp/kops3340584361/kops create cluster --name e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --ssh-public-key /workspace/.ssh/kube_aws_rsa.pub --node-count 4 --node-volume-size 48 --master-volume-size 48 --master-count 1 --zones eu-central-1a --master-size c5.large --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.23.0-alpha.3.249+80056f73a614b2 --admin-access 35.193.93.145/32 --image 309956199498/RHEL-7.8_HVM_GA-20200225-x86_64-1-Hourly2-GP2 --cloud aws --master-image=137112412989/amzn2-ami-hvm-2.0.20200617.0-x86_64-gp2 --override spec.docker.selinuxEnabled=true,cluster.spec.nodePortAccess=0.0.0.0/0 --yes' finished in 25.430205058s
2021/10/10 19:11:31 process.go:153: Running: /tmp/kops3340584361/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m
I1010 19:11:31.859568    1012 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io

W1010 19:11:33.050053    1012 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W1010 19:11:43.091529    1012 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W1010 19:11:53.122807    1012 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-aws-k8s-storage-selinux.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	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a 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
W1010 19:12:03.154094    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a 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
W1010 19:12:13.183903    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a 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
W1010 19:12:23.249553    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a 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
W1010 19:12:33.292531    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a 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
W1010 19:12:43.320696    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a 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
W1010 19:12:53.348796    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a 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
W1010 19:13:03.379509    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a 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
W1010 19:13:13.413841    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a 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
W1010 19:13:23.456628    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a 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
W1010 19:13:33.517951    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a 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
W1010 19:13:43.546757    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a 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
W1010 19:13:53.590915    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a 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
W1010 19:14:03.651826    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a 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
W1010 19:14:13.693004    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a 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
W1010 19:14:23.736413    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a 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
W1010 19:14:33.767180    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a 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
W1010 19:14:43.813779    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a 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
W1010 19:14:53.855803    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a 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
W1010 19:15:03.884457    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a 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
W1010 19:15:13.927000    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
W1010 19:15:53.959011    1012 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://api.e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 203.0.113.123:443: i/o timeout
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
... skipping 6 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:16:07.089683    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:16:19.168425    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:16:31.074474    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:16:42.959764    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:16:54.864980    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:17:06.762746    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:17:18.716084    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:17:30.608529    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:17:42.615369    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:17:54.522817    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:18:06.496159    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:18:18.371661    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:18:30.338513    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:18:42.323516    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:18:54.260374    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:19:06.224241    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:19:18.318960    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:19:30.244428    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:19:42.126571    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:19:54.064914    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:20:06.359544    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:20:18.242934    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:20:30.110844    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:20:42.042006    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:20:53.915334    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:21:05.892426    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:21:17.884367    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:21:29.846735    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:21:41.862403    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:21:53.820835    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:22:05.681609    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:22:17.604610    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:22:29.434817    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:22:41.432941    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:22:53.364383    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:23:05.299856    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:23:17.279192    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:23:29.474509    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:23:41.379109    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:23:53.332862    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:24:05.677844    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:24:17.652545    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:24:29.580417    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:24:41.544076    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:24:53.464376    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:25:05.502739    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:25:17.606486    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:25:29.564603    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:25:41.490578    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:25:53.389982    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:26:05.812361    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:26:17.772167    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 7 lines ...
Machine	i-0685f991e59b7b31e				machine "i-0685f991e59b7b31e" has not yet joined cluster
Machine	i-0e6434d94643d6849				machine "i-0e6434d94643d6849" has not yet joined cluster
Machine	i-0feadf95b3fe7f80c				machine "i-0feadf95b3fe7f80c" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8kklj		system-cluster-critical pod "coredns-5dc785954d-8kklj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kllv2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kllv2" is pending

Validation Failed
W1010 19:26:29.719095    1012 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
2021/10/10 19:26:39 process.go:155: Step '/tmp/kops3340584361/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m' finished in 15m7.888626381s
2021/10/10 19:26:39 process.go:153: Running: kubectl -n kube-system get pods -ojson
2021/10/10 19:26:39 process.go:153: Running: /tmp/kops3340584361/kops toolbox dump --name e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io -ojson
I1010 19:26:39.759994    1024 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
2021/10/10 19:26:40 process.go:155: Step 'kubectl -n kube-system get pods -ojson' finished in 1.182664347s
2021/10/10 19:26:40 process.go:153: Running: kubectl -n kube-system logs --all-containers coredns-5dc785954d-8kklj
... skipping 40 lines ...
2021/10/10 19:26:55 dump.go:413: Running SSH command: sudo cat /var/log/etcd.log
2021/10/10 19:26:55 dump.go:413: Running SSH command: sudo cat /var/log/etcd-events.log
2021/10/10 19:26:55 dump.go:413: Running SSH command: sudo cat /var/log/kube-proxy.log
2021/10/10 19:26:56 dump.go:413: Running SSH command: sudo cat /var/log/cloud-init-output.log
2021/10/10 19:26:56 dump.go:129: dumping node not registered in kubernetes: 54.93.241.88
2021/10/10 19:26:56 dump.go:163: Dumping node 54.93.241.88
2021/10/10 19:26:57 dump.go:132: error dumping node 54.93.241.88: could not connect: unable to SSH to "54.93.241.88": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/10 19:26:57 dump.go:129: dumping node not registered in kubernetes: 18.185.103.34
2021/10/10 19:26:57 dump.go:163: Dumping node 18.185.103.34
2021/10/10 19:26:57 dump.go:132: error dumping node 18.185.103.34: could not connect: unable to SSH to "18.185.103.34": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/10 19:26:57 dump.go:129: dumping node not registered in kubernetes: 18.197.27.97
2021/10/10 19:26:57 dump.go:163: Dumping node 18.197.27.97
2021/10/10 19:26:58 dump.go:132: error dumping node 18.197.27.97: could not connect: unable to SSH to "18.197.27.97": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/10 19:26:58 dump.go:129: dumping node not registered in kubernetes: 18.185.87.199
2021/10/10 19:26:58 dump.go:163: Dumping node 18.185.87.199
2021/10/10 19:26:59 dump.go:132: error dumping node 18.185.87.199: could not connect: unable to SSH to "18.185.87.199": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/10 19:26:59 process.go:153: Running: /tmp/kops3340584361/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io
I1010 19:26:59.620139    1174 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
NAME							CLOUD	ZONES
e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io	aws	eu-central-1a
2021/10/10 19:27:00 process.go:155: Step '/tmp/kops3340584361/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 521.314081ms
2021/10/10 19:27:00 process.go:153: Running: /tmp/kops3340584361/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes
... skipping 224 lines ...
dhcp-options:dopt-074ee4faee6df5045	ok
Deleted kubectl config for e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io

Deleted cluster: "e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io"
2021/10/10 19:28:31 process.go:155: Step '/tmp/kops3340584361/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes' finished in 1m31.186637917s
2021/10/10 19:28:31 process.go:96: Saved XML output to /logs/artifacts/junit_runner.xml.
2021/10/10 19:28:31 main.go:331: Something went wrong: starting e2e cluster: kops validate cluster failed: error during /tmp/kops3340584361/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m: exit status 1
Traceback (most recent call last):
  File "/workspace/scenarios/kubernetes_e2e.py", line 723, in <module>
    main(parse_args())
  File "/workspace/scenarios/kubernetes_e2e.py", line 569, in main
    mode.start(runner_args)
  File "/workspace/scenarios/kubernetes_e2e.py", line 228, in start
... skipping 9 lines ...