This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 5 succeeded
Started2021-10-23 19:20
Elapsed18m24s
Revision
job-versionv1.23.0-alpha.3.499+89dd275dde0d19
kubetest-version
revisionv1.23.0-alpha.3.499+89dd275dde0d19

Test Failures


kubetest Up 15m33s

kops validate cluster failed: error during /tmp/kops2757280768/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)=8e961795aac1e017018f48ec581cf1db
sha512sum(kubernetes-test-linux-amd64.tar.gz)=8bd95c68ea2efe40850e0d176a719850c03a2e965a795c0ac2ed76bac412fd5d8cdd31a115075c3b5454495d2d829932e99836b8da88a17195d5ec30424c2c31

Extracting /workspace/kubernetes/test/kubernetes-test-linux-amd64.tar.gz into /workspace/kubernetes/platforms/linux/amd64
2021/10/23 19:21:15 process.go:155: Step './get-kube.sh' finished in 26.820939012s
2021/10/23 19:21:15 process.go:153: Running: /tmp/kops2757280768/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/23 19:21:16 process.go:155: Step '/tmp/kops2757280768/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 524.585838ms
2021/10/23 19:21:16 util.go:42: curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/23 19:21:16 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/23 19:21:16 util.go:68: curl https://ip.jsb.workers.dev
2021/10/23 19:21:16 kops.go:439: Using external IP for admin access: 35.226.128.128/32
2021/10/23 19:21:16 process.go:153: Running: /tmp/kops2757280768/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.499+89dd275dde0d19 --admin-access 35.226.128.128/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
I1023 19:21:16.610973     986 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1023 19:21:16.633245     986 create_cluster.go:838] Using SSH public key: /workspace/.ssh/kube_aws_rsa.pub
I1023 19:21:17.110849     986 new_cluster.go:1077]  Cloud Provider ID = aws
... skipping 30 lines ...

2021/10/23 19:21:37 process.go:155: Step '/tmp/kops2757280768/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.499+89dd275dde0d19 --admin-access 35.226.128.128/32 --image 309956199498/RHEL-7.8_HVM_GA-20200225-x86_64-1-Hourly2-GP2 --cloud aws --master-image=137112412989/amzn2-ami-hvm-2.0.20200617.0-x86_64-gp2 --override spec.docker.selinuxEnabled=true,cluster.spec.nodePortAccess=0.0.0.0/0 --yes' finished in 21.169443457s
2021/10/23 19:21:37 process.go:153: Running: /tmp/kops2757280768/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m
I1023 19:21:37.776103    1007 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io

W1023 19:21:39.558635    1007 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
W1023 19:21:49.586709    1007 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
W1023 19:21:59.630572    1007 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
W1023 19:22:09.659340    1007 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
W1023 19:22:19.709599    1007 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
W1023 19:22:29.742409    1007 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
W1023 19:22:39.774591    1007 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
W1023 19:22:49.805996    1007 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
W1023 19:22:59.838405    1007 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
W1023 19:23:09.874354    1007 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
W1023 19:23:19.903638    1007 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
W1023 19:23:29.938781    1007 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
W1023 19:23:39.971573    1007 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
W1023 19:23:50.014298    1007 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
W1023 19:24:00.050841    1007 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
W1023 19:24:10.094260    1007 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
W1023 19:24:20.126045    1007 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
W1023 19:24:30.155047    1007 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
W1023 19:24:40.190496    1007 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
W1023 19:24:50.237667    1007 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
W1023 19:25:00.267543    1007 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
W1023 19:25:10.302000    1007 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
W1023 19:25:20.344836    1007 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
W1023 19:25:30.376829    1007 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
W1023 19:25:40.408853    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:25:55.861861    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:26:09.782661    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
W1023 19:26:19.800165    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:26:33.474537    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:26:47.053247    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:27:00.650682    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:27:14.448535    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:27:28.274650    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:27:42.131577    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:27:55.802231    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:28:09.526529    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:28:23.177510    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:28:37.109717    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:28:51.042253    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:29:04.722010    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:29:18.520409    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:29:32.339846    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:29:46.639974    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:30:00.534397    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:30:14.138443    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:30:27.734794    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:30:41.355506    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:30:55.005005    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:31:08.611088    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:31:22.343392    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:31:36.184224    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:31:49.817930    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:32:03.425529    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:32:17.275373    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:32:30.832488    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:32:44.663718    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:32:58.623586    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:33:12.512223    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:33:26.113180    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:33:40.494381    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:33:54.538907    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:34:08.459886    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:34:22.250927    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:34:35.938517    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:34:49.788022    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:35:03.657021    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:35:17.397290    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:35:31.331069    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:35:44.989196    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:35:58.701568    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:36:12.361428    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:36:25.956258    1007 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-06041b985c63bbf38				machine "i-06041b985c63bbf38" has not yet joined cluster
Machine	i-0a1f67f14589bd9fd				machine "i-0a1f67f14589bd9fd" has not yet joined cluster
Machine	i-0a35b40087c96169c				machine "i-0a35b40087c96169c" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-v6dcc		system-cluster-critical pod "coredns-6c8944dbdc-v6dcc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nzbxq	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nzbxq" is pending

Validation Failed
W1023 19:36:39.710179    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
2021/10/23 19:36:49 process.go:155: Step '/tmp/kops2757280768/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m' finished in 15m11.955233209s
2021/10/23 19:36:49 process.go:153: Running: kubectl -n kube-system get pods -ojson
2021/10/23 19:36:49 process.go:153: Running: /tmp/kops2757280768/kops toolbox dump --name e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io -ojson
I1023 19:36:49.735631    1020 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
2021/10/23 19:36:52 process.go:155: Step 'kubectl -n kube-system get pods -ojson' finished in 2.292301022s
2021/10/23 19:36:52 process.go:153: Running: kubectl -n kube-system logs --all-containers coredns-6c8944dbdc-v6dcc
... skipping 40 lines ...
2021/10/23 19:37:16 dump.go:413: Running SSH command: sudo cat /var/log/etcd.log
2021/10/23 19:37:16 dump.go:413: Running SSH command: sudo cat /var/log/etcd-events.log
2021/10/23 19:37:17 dump.go:413: Running SSH command: sudo cat /var/log/kube-proxy.log
2021/10/23 19:37:17 dump.go:413: Running SSH command: sudo cat /var/log/cloud-init-output.log
2021/10/23 19:37:17 dump.go:129: dumping node not registered in kubernetes: 3.109.182.133
2021/10/23 19:37:17 dump.go:163: Dumping node 3.109.182.133
2021/10/23 19:37:19 dump.go:132: error dumping node 3.109.182.133: could not connect: unable to SSH to "3.109.182.133": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/23 19:37:19 dump.go:129: dumping node not registered in kubernetes: 65.1.114.57
2021/10/23 19:37:19 dump.go:163: Dumping node 65.1.114.57
2021/10/23 19:37:21 dump.go:132: error dumping node 65.1.114.57: could not connect: unable to SSH to "65.1.114.57": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/23 19:37:21 dump.go:129: dumping node not registered in kubernetes: 13.235.18.92
2021/10/23 19:37:21 dump.go:163: Dumping node 13.235.18.92
2021/10/23 19:37:23 dump.go:132: error dumping node 13.235.18.92: could not connect: unable to SSH to "13.235.18.92": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/23 19:37:23 dump.go:129: dumping node not registered in kubernetes: 65.2.148.235
2021/10/23 19:37:23 dump.go:163: Dumping node 65.2.148.235
2021/10/23 19:37:25 dump.go:132: error dumping node 65.2.148.235: could not connect: unable to SSH to "65.2.148.235": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/23 19:37:25 process.go:153: Running: /tmp/kops2757280768/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io
I1023 19:37:25.221642    1169 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/23 19:37:25 process.go:155: Step '/tmp/kops2757280768/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 533.657884ms
2021/10/23 19:37:25 process.go:153: Running: /tmp/kops2757280768/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes
... skipping 216 lines ...
dhcp-options:dopt-0ef43e836190bc1e7	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/23 19:39:07 process.go:155: Step '/tmp/kops2757280768/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes' finished in 1m41.61268077s
2021/10/23 19:39:07 process.go:96: Saved XML output to /logs/artifacts/junit_runner.xml.
2021/10/23 19:39:07 main.go:331: Something went wrong: starting e2e cluster: kops validate cluster failed: error during /tmp/kops2757280768/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 ...