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

Test Failures


kubetest Up 15m32s

kops validate cluster failed: error during /tmp/kops2943012788/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
+ wait 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
starts with local mode
Environment:
ARTIFACTS=/logs/artifacts
... skipping 158 lines ...
md5sum(kubernetes-test-linux-amd64.tar.gz)=71e7a5e6c2f6cab092e46cfd2c7c8e65
sha512sum(kubernetes-test-linux-amd64.tar.gz)=f83d5b17251529eef5f14983ed7f70749a08de16c0cf53dfc75da961a864047c16404b18cdd08a19b94e0358230a610550f6e68c30c54a4107be07ef13c2bd5e

Extracting /workspace/kubernetes/test/kubernetes-test-linux-amd64.tar.gz into /workspace/kubernetes/platforms/linux/amd64
2021/10/21 07:19:31 process.go:155: Step './get-kube.sh' finished in 25.314529336s
2021/10/21 07:19:31 process.go:153: Running: /tmp/kops2943012788/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/21 07:19:31 process.go:155: Step '/tmp/kops2943012788/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 555.015299ms
2021/10/21 07:19:31 util.go:42: curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/21 07:19:31 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/21 07:19:31 util.go:68: curl https://ip.jsb.workers.dev
2021/10/21 07:19:31 kops.go:439: Using external IP for admin access: 35.193.138.120/32
2021/10/21 07:19:31 process.go:153: Running: /tmp/kops2943012788/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 us-west-1a --master-size c5.large --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.23.0-alpha.3.462+ae9ca48f01ddb0 --admin-access 35.193.138.120/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
I1021 07:19:31.776759     988 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1021 07:19:31.796075     988 create_cluster.go:838] Using SSH public key: /workspace/.ssh/kube_aws_rsa.pub
I1021 07:19:32.311278     988 new_cluster.go:1077]  Cloud Provider ID = aws
... skipping 31 lines ...

2021/10/21 07:19:56 process.go:155: Step '/tmp/kops2943012788/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 us-west-1a --master-size c5.large --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.23.0-alpha.3.462+ae9ca48f01ddb0 --admin-access 35.193.138.120/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 24.345985627s
2021/10/21 07:19:56 process.go:153: Running: /tmp/kops2943012788/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m
I1021 07:19:56.120104    1008 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io

W1021 07:19:57.135004    1008 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-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-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
W1021 07:20:07.163400    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-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
W1021 07:20:17.192890    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-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
W1021 07:20:27.222215    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-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
W1021 07:20:37.265962    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-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
W1021 07:20:47.301443    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-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
W1021 07:20:57.329902    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-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
W1021 07:21:07.362675    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-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
W1021 07:21:17.394502    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-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
W1021 07:21:27.425075    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-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
W1021 07:21:37.461279    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-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
W1021 07:21:47.490409    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-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
W1021 07:21:57.538245    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-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
W1021 07:22:07.604168    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-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
W1021 07:22:17.649001    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-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
W1021 07:22:27.678890    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-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
W1021 07:22:37.713674    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-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
W1021 07:22:47.744132    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-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
W1021 07:22:57.774450    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-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
W1021 07:23:07.806197    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-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
W1021 07:23:17.841185    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-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
W1021 07:23:27.870267    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-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
W1021 07:23:37.907025    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-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
W1021 07:23:47.939164    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
W1021 07:24:27.984808    1008 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
W1021 07:24:38.002802    1008 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-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

NODE STATUS
... skipping 6 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:24:49.765384    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:25:01.105469    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:25:12.458955    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:25:23.642290    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:25:34.782145    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:25:46.018852    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:25:57.168436    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:26:08.374728    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:26:19.613205    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:26:30.760548    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:26:42.044130    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:26:53.246914    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:27:04.376284    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:27:15.500456    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:27:26.605621    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:27:37.865280    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:27:49.056725    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:28:00.334171    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:28:11.431910    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:28:22.506569    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:28:33.685890    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:28:45.076060    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:28:56.206317    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:29:07.463040    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:29:18.595720    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:29:29.876642    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:29:41.049539    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:29:52.185410    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:30:03.414486    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:30:14.562874    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:30:25.708096    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:30:37.007213    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:30:48.156579    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:30:59.332965    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:31:10.463637    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:31:21.641654    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:31:32.819731    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:31:43.961190    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:31:55.170129    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:32:06.398022    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:32:17.511919    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:32:28.726522    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:32:40.191903    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:32:51.441761    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:33:02.583741    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:33:13.779786    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:33:24.896186    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:33:36.004263    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:33:47.240618    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:33:58.590593    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:34:09.768853    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:34:20.979602    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:34:32.072791    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:34:43.359134    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...
Machine	i-06e5384aa2729183d				machine "i-06e5384aa2729183d" has not yet joined cluster
Machine	i-0c674d322d12192a9				machine "i-0c674d322d12192a9" has not yet joined cluster
Machine	i-0e530f1a7e9db1105				machine "i-0e530f1a7e9db1105" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-zpgbz		system-cluster-critical pod "coredns-6c8944dbdc-zpgbz" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6p8m9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6p8m9" is pending

Validation Failed
W1021 07:34:54.590493    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
2021/10/21 07:35:04 process.go:155: Step '/tmp/kops2943012788/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m' finished in 15m8.494407823s
2021/10/21 07:35:04 process.go:153: Running: kubectl -n kube-system get pods -ojson
2021/10/21 07:35:04 process.go:153: Running: /tmp/kops2943012788/kops toolbox dump --name e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io -ojson
I1021 07:35:04.617340    1020 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
2021/10/21 07:35:05 process.go:155: Step 'kubectl -n kube-system get pods -ojson' finished in 630.711686ms
2021/10/21 07:35:05 process.go:153: Running: kubectl -n kube-system logs --all-containers coredns-6c8944dbdc-zpgbz
... skipping 40 lines ...
2021/10/21 07:35:15 dump.go:413: Running SSH command: sudo cat /var/log/etcd.log
2021/10/21 07:35:15 dump.go:413: Running SSH command: sudo cat /var/log/etcd-events.log
2021/10/21 07:35:15 dump.go:413: Running SSH command: sudo cat /var/log/kube-proxy.log
2021/10/21 07:35:15 dump.go:413: Running SSH command: sudo cat /var/log/cloud-init-output.log
2021/10/21 07:35:15 dump.go:129: dumping node not registered in kubernetes: 52.53.219.232
2021/10/21 07:35:15 dump.go:163: Dumping node 52.53.219.232
2021/10/21 07:35:16 dump.go:132: error dumping node 52.53.219.232: could not connect: unable to SSH to "52.53.219.232": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/21 07:35:16 dump.go:129: dumping node not registered in kubernetes: 54.153.112.240
2021/10/21 07:35:16 dump.go:163: Dumping node 54.153.112.240
2021/10/21 07:35:16 dump.go:132: error dumping node 54.153.112.240: could not connect: unable to SSH to "54.153.112.240": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/21 07:35:16 dump.go:129: dumping node not registered in kubernetes: 54.151.7.155
2021/10/21 07:35:16 dump.go:163: Dumping node 54.151.7.155
2021/10/21 07:35:17 dump.go:132: error dumping node 54.151.7.155: could not connect: unable to SSH to "54.151.7.155": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/21 07:35:17 dump.go:129: dumping node not registered in kubernetes: 54.176.25.201
2021/10/21 07:35:17 dump.go:163: Dumping node 54.176.25.201
2021/10/21 07:35:17 dump.go:132: error dumping node 54.176.25.201: could not connect: unable to SSH to "54.176.25.201": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/21 07:35:17 process.go:153: Running: /tmp/kops2943012788/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io
I1021 07:35:17.741495    1170 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
NAME							CLOUD	ZONES
e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io	aws	us-west-1a
2021/10/21 07:35:18 process.go:155: Step '/tmp/kops2943012788/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 548.236757ms
2021/10/21 07:35:18 process.go:153: Running: /tmp/kops2943012788/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes
... skipping 178 lines ...
dhcp-options:dopt-07400b862cc3af99a	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/21 07:36:45 process.go:155: Step '/tmp/kops2943012788/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes' finished in 1m27.461217563s
2021/10/21 07:36:45 process.go:96: Saved XML output to /logs/artifacts/junit_runner.xml.
2021/10/21 07:36:45 main.go:331: Something went wrong: starting e2e cluster: kops validate cluster failed: error during /tmp/kops2943012788/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 ...