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

Test Failures


kubetest Up 15m28s

kops validate cluster failed: error during /tmp/kops2497100979/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=30
+ wait 30
+ /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)=f94333404bad0f981b14ecdee09cf682
sha512sum(kubernetes-test-linux-amd64.tar.gz)=f4a8b8b91044ed753e57bcfa93cf37c0426b62267c72868ec0f73e705152a097abefdc1790a8cde4ff240cc2c6d31ba64766660416aab65c6a830b4c28effdfb

Extracting /workspace/kubernetes/test/kubernetes-test-linux-amd64.tar.gz into /workspace/kubernetes/platforms/linux/amd64
2021/10/09 19:11:02 process.go:155: Step './get-kube.sh' finished in 28.225041488s
2021/10/09 19:11:02 process.go:153: Running: /tmp/kops2497100979/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/09 19:11:02 process.go:155: Step '/tmp/kops2497100979/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 506.856625ms
2021/10/09 19:11:02 util.go:42: curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/09 19:11:02 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/09 19:11:02 util.go:68: curl https://ip.jsb.workers.dev
2021/10/09 19:11:02 kops.go:439: Using external IP for admin access: 35.184.205.92/32
2021/10/09 19:11:02 process.go:153: Running: /tmp/kops2497100979/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 ap-south-1a --master-size c5.large --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.23.0-alpha.3.249+80056f73a614b2 --admin-access 35.184.205.92/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
I1009 19:11:02.693877     987 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1009 19:11:02.717808     987 create_cluster.go:838] Using SSH public key: /workspace/.ssh/kube_aws_rsa.pub
I1009 19:11:03.387620     987 new_cluster.go:1077]  Cloud Provider ID = aws
... skipping 29 lines ...

2021/10/09 19:11:22 process.go:155: Step '/tmp/kops2497100979/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 ap-south-1a --master-size c5.large --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.23.0-alpha.3.249+80056f73a614b2 --admin-access 35.184.205.92/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 19.589012603s
2021/10/09 19:11:22 process.go:153: Running: /tmp/kops2497100979/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m
I1009 19:11:22.282770    1008 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io

W1009 19:11:24.049014    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
W1009 19:11:34.081001    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-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W1009 19:11:44.115694    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W1009 19:11:54.144522    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W1009 19:12:04.174867    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W1009 19:12:14.216839    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W1009 19:12:24.258618    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W1009 19:12:34.302137    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W1009 19:12:44.338738    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W1009 19:12:54.365664    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W1009 19:13:04.397212    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W1009 19:13:14.428924    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W1009 19:13:24.472238    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W1009 19:13:34.518966    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W1009 19:13:44.551548    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W1009 19:13:54.582985    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W1009 19:14:04.625344    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W1009 19:14:14.661518    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W1009 19:14:24.708355    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W1009 19:14:34.737048    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W1009 19:14:44.764026    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
W1009 19:14:54.781740    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-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W1009 19:15:04.810557    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W1009 19:15:14.854164    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W1009 19:15:24.890900    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:15:40.324920    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:15:54.153971    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:16:07.914829    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
W1009 19:16:17.957307    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-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

NODE STATUS
... skipping 6 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:16:31.647384    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:16:45.229593    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:16:58.882670    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:17:12.475702    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:17:26.090653    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:17:39.921759    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:17:53.470401    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:18:07.065531    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:18:20.755202    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:18:34.594948    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:18:48.271942    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:19:01.873074    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:19:15.462474    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:19:29.863350    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:19:43.456207    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:19:57.038807    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:20:10.599509    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:20:24.214558    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:20:38.024326    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:20:51.604753    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:21:05.455005    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:21:19.011582    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:21:32.682165    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:21:46.200156    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:21:59.813041    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:22:13.560863    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:22:27.682031    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:22:41.263445    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:22:54.826104    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:23:08.378333    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:23:22.749258    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:23:36.393082    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:23:50.077975    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:24:03.923522    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:24:17.510472    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:24:31.225443    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:24:44.794621    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:24:58.738474    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:25:12.405361    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:25:26.077574    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:25:39.924985    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:25:53.743452    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:26:07.515726    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...
Machine	i-053cb25c08dc5aa5c				machine "i-053cb25c08dc5aa5c" has not yet joined cluster
Machine	i-0a77f594cb56881aa				machine "i-0a77f594cb56881aa" has not yet joined cluster
Machine	i-0e7c7de27409f4c28				machine "i-0e7c7de27409f4c28" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-68sjh		system-cluster-critical pod "coredns-5dc785954d-68sjh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kkq6p	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kkq6p" is pending

Validation Failed
W1009 19:26:21.328682    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
2021/10/09 19:26:31 process.go:155: Step '/tmp/kops2497100979/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m' finished in 15m9.072636446s
2021/10/09 19:26:31 process.go:153: Running: kubectl -n kube-system get pods -ojson
2021/10/09 19:26:31 process.go:153: Running: /tmp/kops2497100979/kops toolbox dump --name e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io -ojson
I1009 19:26:31.356824    1019 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
2021/10/09 19:26:33 process.go:155: Step 'kubectl -n kube-system get pods -ojson' finished in 2.373888646s
2021/10/09 19:26:33 process.go:153: Running: kubectl -n kube-system logs --all-containers coredns-5dc785954d-68sjh
... skipping 40 lines ...
2021/10/09 19:26:58 dump.go:413: Running SSH command: sudo cat /var/log/etcd.log
2021/10/09 19:26:58 dump.go:413: Running SSH command: sudo cat /var/log/etcd-events.log
2021/10/09 19:26:59 dump.go:413: Running SSH command: sudo cat /var/log/kube-proxy.log
2021/10/09 19:26:59 dump.go:413: Running SSH command: sudo cat /var/log/cloud-init-output.log
2021/10/09 19:26:59 dump.go:129: dumping node not registered in kubernetes: 13.233.113.228
2021/10/09 19:26:59 dump.go:163: Dumping node 13.233.113.228
2021/10/09 19:27:01 dump.go:132: error dumping node 13.233.113.228: could not connect: unable to SSH to "13.233.113.228": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/09 19:27:01 dump.go:129: dumping node not registered in kubernetes: 52.66.183.66
2021/10/09 19:27:01 dump.go:163: Dumping node 52.66.183.66
2021/10/09 19:27:03 dump.go:132: error dumping node 52.66.183.66: could not connect: unable to SSH to "52.66.183.66": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/09 19:27:03 dump.go:129: dumping node not registered in kubernetes: 3.109.216.58
2021/10/09 19:27:03 dump.go:163: Dumping node 3.109.216.58
2021/10/09 19:27:05 dump.go:132: error dumping node 3.109.216.58: could not connect: unable to SSH to "3.109.216.58": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/09 19:27:05 dump.go:129: dumping node not registered in kubernetes: 13.232.49.189
2021/10/09 19:27:05 dump.go:163: Dumping node 13.232.49.189
2021/10/09 19:27:07 dump.go:132: error dumping node 13.232.49.189: could not connect: unable to SSH to "13.232.49.189": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/09 19:27:07 process.go:153: Running: /tmp/kops2497100979/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io
I1009 19:27:07.437875    1168 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
NAME							CLOUD	ZONES
e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io	aws	ap-south-1a
2021/10/09 19:27:07 process.go:155: Step '/tmp/kops2497100979/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 477.891954ms
2021/10/09 19:27:07 process.go:153: Running: /tmp/kops2497100979/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes
... skipping 168 lines ...
dhcp-options:dopt-01ff16af4ef250a56	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/09 19:28:26 process.go:155: Step '/tmp/kops2497100979/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes' finished in 1m18.671449215s
2021/10/09 19:28:26 process.go:96: Saved XML output to /logs/artifacts/junit_runner.xml.
2021/10/09 19:28:26 main.go:331: Something went wrong: starting e2e cluster: kops validate cluster failed: error during /tmp/kops2497100979/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 ...