This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 5 succeeded
Started2021-10-07 19:08
Elapsed17m43s
Revision
job-versionv1.23.0-alpha.3.207+b0eac84937f7f5
kubetest-version
revisionv1.23.0-alpha.3.207+b0eac84937f7f5

Test Failures


kubetest Up 15m27s

kops validate cluster failed: error during /tmp/kops3978246819/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=32
+ wait 32
+ /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
starts with local mode
Environment:
ARTIFACTS=/logs/artifacts
... skipping 156 lines ...
md5sum(kubernetes-test-linux-amd64.tar.gz)=b4c6aa012d6eb35952fd20191e6efbc8
sha512sum(kubernetes-test-linux-amd64.tar.gz)=12a266ca5add3ac0014d1633ab3cd07ef2da3785ef82321cc53258877bbb46a04a28aa66d57cb7f33f2101850280ee33608e862276986d90449c6dfba3b061d6

Extracting /workspace/kubernetes/test/kubernetes-test-linux-amd64.tar.gz into /workspace/kubernetes/platforms/linux/amd64
2021/10/07 19:08:52 process.go:155: Step './get-kube.sh' finished in 30.832176161s
2021/10/07 19:08:52 process.go:153: Running: /tmp/kops3978246819/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/07 19:08:53 process.go:155: Step '/tmp/kops3978246819/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 507.749443ms
2021/10/07 19:08:53 util.go:42: curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/07 19:08:53 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/07 19:08:53 util.go:68: curl https://ip.jsb.workers.dev
2021/10/07 19:08:53 kops.go:439: Using external IP for admin access: 35.202.129.61/32
2021/10/07 19:08:53 process.go:153: Running: /tmp/kops3978246819/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 ca-central-1b --master-size c5.large --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.23.0-alpha.3.207+b0eac84937f7f5 --admin-access 35.202.129.61/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
I1007 19:08:53.170812     990 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1007 19:08:53.193473     990 create_cluster.go:838] Using SSH public key: /workspace/.ssh/kube_aws_rsa.pub
I1007 19:08:53.655425     990 new_cluster.go:1077]  Cloud Provider ID = aws
... skipping 31 lines ...

2021/10/07 19:09:15 process.go:155: Step '/tmp/kops3978246819/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 ca-central-1b --master-size c5.large --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.23.0-alpha.3.207+b0eac84937f7f5 --admin-access 35.202.129.61/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 21.917220178s
2021/10/07 19:09:15 process.go:153: Running: /tmp/kops3978246819/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m
I1007 19:09:15.085897    1011 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io

W1007 19:09:16.004338    1011 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-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1007 19:09:26.047463    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1007 19:09:36.085549    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1007 19:09:46.116501    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
W1007 19:09:56.156363    1011 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-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1007 19:10:06.222564    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1007 19:10:16.260780    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1007 19:10:26.296990    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1007 19:10:36.345218    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1007 19:10:46.391204    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1007 19:10:56.423212    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1007 19:11:06.471141    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1007 19:11:16.516925    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1007 19:11:26.548943    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1007 19:11:36.581363    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1007 19:11:46.626021    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1007 19:11:56.659456    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1007 19:12:06.692211    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1007 19:12:16.740956    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1007 19:12:26.772616    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1007 19:12:36.813477    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1007 19:12:46.851547    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1007 19:12:56.890654    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1007 19:13:06.925130    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1007 19:13:16.975021    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1007 19:13:27.008131    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
W1007 19:14:07.047364    1011 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-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

NODE STATUS
... skipping 6 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:14:18.476036    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:14:29.379291    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:14:40.293673    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:14:51.201355    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:15:02.131101    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:15:13.055515    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:15:23.958797    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:15:34.850358    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:15:45.812575    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:15:56.778030    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:16:07.666506    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:16:18.566857    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:16:29.464384    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:16:40.678939    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:16:51.645598    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:17:02.827887    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:17:13.761526    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:17:24.698222    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:17:36.358549    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:17:47.652390    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:17:58.857750    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:18:09.919560    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:18:20.829916    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:18:31.757001    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:18:42.606398    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:18:53.499360    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:19:04.527595    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:19:15.425949    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:19:26.360171    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:19:37.288572    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:19:48.246304    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:19:59.089839    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:20:09.966803    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:20:21.086428    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:20:32.004145    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:20:42.894087    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:20:53.766424    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:21:04.721663    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:21:15.558935    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:21:26.438103    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:21:37.266044    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:21:48.138632    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:21:59.088059    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:22:10.159271    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:22:21.071443    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:22:32.013181    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:22:42.872232    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:22:53.930403    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:23:04.882941    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:23:15.907341    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:23:26.902831    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:23:37.903013    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:23:48.867932    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:23:59.817347    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-00a30878a54d57451				machine "i-00a30878a54d57451" has not yet joined cluster
Machine	i-090033b9974e44e00				machine "i-090033b9974e44e00" has not yet joined cluster
Machine	i-0e80b3e25028d3eaa				machine "i-0e80b3e25028d3eaa" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-qck7q		system-cluster-critical pod "coredns-5dc785954d-qck7q" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sv9p4	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sv9p4" is pending

Validation Failed
W1007 19:24:10.732328    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
2021/10/07 19:24:20 process.go:155: Step '/tmp/kops3978246819/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m' finished in 15m5.680186436s
2021/10/07 19:24:20 process.go:153: Running: kubectl -n kube-system get pods -ojson
2021/10/07 19:24:20 process.go:153: Running: /tmp/kops3978246819/kops toolbox dump --name e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io -ojson
I1007 19:24:20.881271    1024 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
2021/10/07 19:24:21 process.go:155: Step 'kubectl -n kube-system get pods -ojson' finished in 1.049968839s
2021/10/07 19:24:21 process.go:153: Running: kubectl -n kube-system logs --all-containers coredns-5dc785954d-qck7q
... skipping 40 lines ...
2021/10/07 19:24:29 dump.go:413: Running SSH command: sudo cat /var/log/etcd.log
2021/10/07 19:24:30 dump.go:413: Running SSH command: sudo cat /var/log/etcd-events.log
2021/10/07 19:24:30 dump.go:413: Running SSH command: sudo cat /var/log/kube-proxy.log
2021/10/07 19:24:30 dump.go:413: Running SSH command: sudo cat /var/log/cloud-init-output.log
2021/10/07 19:24:30 dump.go:129: dumping node not registered in kubernetes: 35.182.217.208
2021/10/07 19:24:30 dump.go:163: Dumping node 35.182.217.208
2021/10/07 19:24:30 dump.go:132: error dumping node 35.182.217.208: could not connect: unable to SSH to "35.182.217.208": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/07 19:24:30 dump.go:129: dumping node not registered in kubernetes: 52.60.222.174
2021/10/07 19:24:30 dump.go:163: Dumping node 52.60.222.174
2021/10/07 19:24:30 dump.go:132: error dumping node 52.60.222.174: could not connect: unable to SSH to "52.60.222.174": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/07 19:24:30 dump.go:129: dumping node not registered in kubernetes: 15.223.77.250
2021/10/07 19:24:30 dump.go:163: Dumping node 15.223.77.250
2021/10/07 19:24:31 dump.go:132: error dumping node 15.223.77.250: could not connect: unable to SSH to "15.223.77.250": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/07 19:24:31 dump.go:129: dumping node not registered in kubernetes: 99.79.74.197
2021/10/07 19:24:31 dump.go:163: Dumping node 99.79.74.197
2021/10/07 19:24:31 dump.go:132: error dumping node 99.79.74.197: could not connect: unable to SSH to "99.79.74.197": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/07 19:24:31 process.go:153: Running: /tmp/kops3978246819/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io
I1007 19:24:31.569117    1152 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
NAME							CLOUD	ZONES
e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io	aws	ca-central-1b
2021/10/07 19:24:32 process.go:155: Step '/tmp/kops3978246819/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 1.057707916s
2021/10/07 19:24:32 process.go:153: Running: /tmp/kops3978246819/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes
... skipping 198 lines ...
dhcp-options:dopt-0ba725f7ac71ea3a5	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/07 19:25:56 process.go:155: Step '/tmp/kops3978246819/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes' finished in 1m24.195707954s
2021/10/07 19:25:56 process.go:96: Saved XML output to /logs/artifacts/junit_runner.xml.
2021/10/07 19:25:56 main.go:331: Something went wrong: starting e2e cluster: kops validate cluster failed: error during /tmp/kops3978246819/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 ...