This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 5 succeeded
Started2021-10-13 19:13
Elapsed18m15s
Revision
job-versionv1.23.0-alpha.3.304+92f67c6347c6ed
kubetest-version
revisionv1.23.0-alpha.3.304+92f67c6347c6ed

Test Failures


kubetest Up 15m23s

kops validate cluster failed: error during /tmp/kops2258164994/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=33
+ wait 33
+ /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)=6159c3b951661a7ed9ccbbf668bc2af1
sha512sum(kubernetes-test-linux-amd64.tar.gz)=b6b6d7a11982c849e1ce20510f2fa5416dd7af66aedd0c2d3661a837e0e0cb574812494c38e889feb6dca98770114b31bb087a171ad6ff5088c940f2c44f3b75

Extracting /workspace/kubernetes/test/kubernetes-test-linux-amd64.tar.gz into /workspace/kubernetes/platforms/linux/amd64
2021/10/13 19:14:18 process.go:155: Step './get-kube.sh' finished in 27.103788068s
2021/10/13 19:14:18 process.go:153: Running: /tmp/kops2258164994/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/13 19:14:18 process.go:155: Step '/tmp/kops2258164994/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 495.129194ms
2021/10/13 19:14:18 util.go:42: curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/13 19:14:18 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/13 19:14:18 util.go:68: curl https://ip.jsb.workers.dev
2021/10/13 19:14:18 kops.go:439: Using external IP for admin access: 34.133.64.240/32
2021/10/13 19:14:18 process.go:153: Running: /tmp/kops2258164994/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-1b --master-size c5.large --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.23.0-alpha.3.304+92f67c6347c6ed --admin-access 34.133.64.240/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
I1013 19:14:18.903781     993 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1013 19:14:18.929887     993 create_cluster.go:838] Using SSH public key: /workspace/.ssh/kube_aws_rsa.pub
I1013 19:14:19.420796     993 new_cluster.go:1077]  Cloud Provider ID = aws
... skipping 29 lines ...

2021/10/13 19:14:37 process.go:155: Step '/tmp/kops2258164994/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-1b --master-size c5.large --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.23.0-alpha.3.304+92f67c6347c6ed --admin-access 34.133.64.240/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 18.977040587s
2021/10/13 19:14:37 process.go:153: Running: /tmp/kops2258164994/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m
I1013 19:14:37.880646    1013 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io

W1013 19:14:40.013623    1013 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-1b	Master	c5.large	1	1	ap-south-1b
nodes-ap-south-1b	Node	t3.medium	4	4	ap-south-1b

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1013 19:16:00.302161    1013 validate_cluster.go:232] (will retry): cluster not yet healthy
W1013 19:16:10.331760    1013 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-1b	Master	c5.large	1	1	ap-south-1b
nodes-ap-south-1b	Node	t3.medium	4	4	ap-south-1b

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1013 19:18:30.908024    1013 validate_cluster.go:232] (will retry): cluster not yet healthy
W1013 19:19:10.952284    1013 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://api.e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 203.0.113.123:443: i/o timeout
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1b	Master	c5.large	1	1	ap-south-1b
nodes-ap-south-1b	Node	t3.medium	4	4	ap-south-1b

NODE STATUS
... skipping 6 lines ...
Machine	i-01340c203684b30f2				machine "i-01340c203684b30f2" has not yet joined cluster
Machine	i-050cd20c43ddd6a2b				machine "i-050cd20c43ddd6a2b" has not yet joined cluster
Machine	i-06c45a9e06d6f5e3e				machine "i-06c45a9e06d6f5e3e" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-bzhzf		system-cluster-critical pod "coredns-6c8944dbdc-bzhzf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-s8g97	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-s8g97" is pending

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

... skipping 7 lines ...
Machine	i-01340c203684b30f2				machine "i-01340c203684b30f2" has not yet joined cluster
Machine	i-050cd20c43ddd6a2b				machine "i-050cd20c43ddd6a2b" has not yet joined cluster
Machine	i-06c45a9e06d6f5e3e				machine "i-06c45a9e06d6f5e3e" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-bzhzf		system-cluster-critical pod "coredns-6c8944dbdc-bzhzf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-s8g97	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-s8g97" is pending

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

... skipping 7 lines ...
Machine	i-01340c203684b30f2				machine "i-01340c203684b30f2" has not yet joined cluster
Machine	i-050cd20c43ddd6a2b				machine "i-050cd20c43ddd6a2b" has not yet joined cluster
Machine	i-06c45a9e06d6f5e3e				machine "i-06c45a9e06d6f5e3e" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-bzhzf		system-cluster-critical pod "coredns-6c8944dbdc-bzhzf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-s8g97	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-s8g97" is pending

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

... skipping 7 lines ...
Machine	i-01340c203684b30f2				machine "i-01340c203684b30f2" has not yet joined cluster
Machine	i-050cd20c43ddd6a2b				machine "i-050cd20c43ddd6a2b" has not yet joined cluster
Machine	i-06c45a9e06d6f5e3e				machine "i-06c45a9e06d6f5e3e" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-bzhzf		system-cluster-critical pod "coredns-6c8944dbdc-bzhzf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-s8g97	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-s8g97" is pending

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

... skipping 7 lines ...
Machine	i-01340c203684b30f2				machine "i-01340c203684b30f2" has not yet joined cluster
Machine	i-050cd20c43ddd6a2b				machine "i-050cd20c43ddd6a2b" has not yet joined cluster
Machine	i-06c45a9e06d6f5e3e				machine "i-06c45a9e06d6f5e3e" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-bzhzf		system-cluster-critical pod "coredns-6c8944dbdc-bzhzf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-s8g97	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-s8g97" is pending

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

... skipping 7 lines ...
Machine	i-01340c203684b30f2				machine "i-01340c203684b30f2" has not yet joined cluster
Machine	i-050cd20c43ddd6a2b				machine "i-050cd20c43ddd6a2b" has not yet joined cluster
Machine	i-06c45a9e06d6f5e3e				machine "i-06c45a9e06d6f5e3e" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-bzhzf		system-cluster-critical pod "coredns-6c8944dbdc-bzhzf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-s8g97	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-s8g97" is pending

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

... skipping 7 lines ...
Machine	i-01340c203684b30f2				machine "i-01340c203684b30f2" has not yet joined cluster
Machine	i-050cd20c43ddd6a2b				machine "i-050cd20c43ddd6a2b" has not yet joined cluster
Machine	i-06c45a9e06d6f5e3e				machine "i-06c45a9e06d6f5e3e" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-bzhzf		system-cluster-critical pod "coredns-6c8944dbdc-bzhzf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-s8g97	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-s8g97" is pending

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

... skipping 7 lines ...
Machine	i-01340c203684b30f2				machine "i-01340c203684b30f2" has not yet joined cluster
Machine	i-050cd20c43ddd6a2b				machine "i-050cd20c43ddd6a2b" has not yet joined cluster
Machine	i-06c45a9e06d6f5e3e				machine "i-06c45a9e06d6f5e3e" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-bzhzf		system-cluster-critical pod "coredns-6c8944dbdc-bzhzf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-s8g97	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-s8g97" is pending

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

... skipping 7 lines ...
Machine	i-01340c203684b30f2				machine "i-01340c203684b30f2" has not yet joined cluster
Machine	i-050cd20c43ddd6a2b				machine "i-050cd20c43ddd6a2b" has not yet joined cluster
Machine	i-06c45a9e06d6f5e3e				machine "i-06c45a9e06d6f5e3e" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-bzhzf		system-cluster-critical pod "coredns-6c8944dbdc-bzhzf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-s8g97	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-s8g97" is pending

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

... skipping 7 lines ...
Machine	i-01340c203684b30f2				machine "i-01340c203684b30f2" has not yet joined cluster
Machine	i-050cd20c43ddd6a2b				machine "i-050cd20c43ddd6a2b" has not yet joined cluster
Machine	i-06c45a9e06d6f5e3e				machine "i-06c45a9e06d6f5e3e" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-bzhzf		system-cluster-critical pod "coredns-6c8944dbdc-bzhzf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-s8g97	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-s8g97" is pending

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

... skipping 7 lines ...
Machine	i-01340c203684b30f2				machine "i-01340c203684b30f2" has not yet joined cluster
Machine	i-050cd20c43ddd6a2b				machine "i-050cd20c43ddd6a2b" has not yet joined cluster
Machine	i-06c45a9e06d6f5e3e				machine "i-06c45a9e06d6f5e3e" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-bzhzf		system-cluster-critical pod "coredns-6c8944dbdc-bzhzf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-s8g97	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-s8g97" is pending

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

... skipping 7 lines ...
Machine	i-01340c203684b30f2				machine "i-01340c203684b30f2" has not yet joined cluster
Machine	i-050cd20c43ddd6a2b				machine "i-050cd20c43ddd6a2b" has not yet joined cluster
Machine	i-06c45a9e06d6f5e3e				machine "i-06c45a9e06d6f5e3e" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-bzhzf		system-cluster-critical pod "coredns-6c8944dbdc-bzhzf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-s8g97	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-s8g97" is pending

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

... skipping 7 lines ...
Machine	i-01340c203684b30f2				machine "i-01340c203684b30f2" has not yet joined cluster
Machine	i-050cd20c43ddd6a2b				machine "i-050cd20c43ddd6a2b" has not yet joined cluster
Machine	i-06c45a9e06d6f5e3e				machine "i-06c45a9e06d6f5e3e" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-bzhzf		system-cluster-critical pod "coredns-6c8944dbdc-bzhzf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-s8g97	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-s8g97" is pending

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

... skipping 7 lines ...
Machine	i-01340c203684b30f2				machine "i-01340c203684b30f2" has not yet joined cluster
Machine	i-050cd20c43ddd6a2b				machine "i-050cd20c43ddd6a2b" has not yet joined cluster
Machine	i-06c45a9e06d6f5e3e				machine "i-06c45a9e06d6f5e3e" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-bzhzf		system-cluster-critical pod "coredns-6c8944dbdc-bzhzf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-s8g97	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-s8g97" is pending

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

... skipping 7 lines ...
Machine	i-01340c203684b30f2				machine "i-01340c203684b30f2" has not yet joined cluster
Machine	i-050cd20c43ddd6a2b				machine "i-050cd20c43ddd6a2b" has not yet joined cluster
Machine	i-06c45a9e06d6f5e3e				machine "i-06c45a9e06d6f5e3e" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-bzhzf		system-cluster-critical pod "coredns-6c8944dbdc-bzhzf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-s8g97	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-s8g97" is pending

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

... skipping 7 lines ...
Machine	i-01340c203684b30f2				machine "i-01340c203684b30f2" has not yet joined cluster
Machine	i-050cd20c43ddd6a2b				machine "i-050cd20c43ddd6a2b" has not yet joined cluster
Machine	i-06c45a9e06d6f5e3e				machine "i-06c45a9e06d6f5e3e" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-bzhzf		system-cluster-critical pod "coredns-6c8944dbdc-bzhzf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-s8g97	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-s8g97" is pending

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

... skipping 7 lines ...
Machine	i-01340c203684b30f2				machine "i-01340c203684b30f2" has not yet joined cluster
Machine	i-050cd20c43ddd6a2b				machine "i-050cd20c43ddd6a2b" has not yet joined cluster
Machine	i-06c45a9e06d6f5e3e				machine "i-06c45a9e06d6f5e3e" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-bzhzf		system-cluster-critical pod "coredns-6c8944dbdc-bzhzf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-s8g97	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-s8g97" is pending

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

... skipping 7 lines ...
Machine	i-01340c203684b30f2				machine "i-01340c203684b30f2" has not yet joined cluster
Machine	i-050cd20c43ddd6a2b				machine "i-050cd20c43ddd6a2b" has not yet joined cluster
Machine	i-06c45a9e06d6f5e3e				machine "i-06c45a9e06d6f5e3e" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-bzhzf		system-cluster-critical pod "coredns-6c8944dbdc-bzhzf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-s8g97	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-s8g97" is pending

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

... skipping 7 lines ...
Machine	i-01340c203684b30f2				machine "i-01340c203684b30f2" has not yet joined cluster
Machine	i-050cd20c43ddd6a2b				machine "i-050cd20c43ddd6a2b" has not yet joined cluster
Machine	i-06c45a9e06d6f5e3e				machine "i-06c45a9e06d6f5e3e" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-bzhzf		system-cluster-critical pod "coredns-6c8944dbdc-bzhzf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-s8g97	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-s8g97" is pending

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

... skipping 7 lines ...
Machine	i-01340c203684b30f2				machine "i-01340c203684b30f2" has not yet joined cluster
Machine	i-050cd20c43ddd6a2b				machine "i-050cd20c43ddd6a2b" has not yet joined cluster
Machine	i-06c45a9e06d6f5e3e				machine "i-06c45a9e06d6f5e3e" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-bzhzf		system-cluster-critical pod "coredns-6c8944dbdc-bzhzf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-s8g97	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-s8g97" is pending

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

... skipping 7 lines ...
Machine	i-01340c203684b30f2				machine "i-01340c203684b30f2" has not yet joined cluster
Machine	i-050cd20c43ddd6a2b				machine "i-050cd20c43ddd6a2b" has not yet joined cluster
Machine	i-06c45a9e06d6f5e3e				machine "i-06c45a9e06d6f5e3e" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-bzhzf		system-cluster-critical pod "coredns-6c8944dbdc-bzhzf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-s8g97	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-s8g97" is pending

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

... skipping 7 lines ...
Machine	i-01340c203684b30f2				machine "i-01340c203684b30f2" has not yet joined cluster
Machine	i-050cd20c43ddd6a2b				machine "i-050cd20c43ddd6a2b" has not yet joined cluster
Machine	i-06c45a9e06d6f5e3e				machine "i-06c45a9e06d6f5e3e" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-bzhzf		system-cluster-critical pod "coredns-6c8944dbdc-bzhzf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-s8g97	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-s8g97" is pending

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

... skipping 7 lines ...
Machine	i-01340c203684b30f2				machine "i-01340c203684b30f2" has not yet joined cluster
Machine	i-050cd20c43ddd6a2b				machine "i-050cd20c43ddd6a2b" has not yet joined cluster
Machine	i-06c45a9e06d6f5e3e				machine "i-06c45a9e06d6f5e3e" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-bzhzf		system-cluster-critical pod "coredns-6c8944dbdc-bzhzf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-s8g97	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-s8g97" is pending

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

... skipping 7 lines ...
Machine	i-01340c203684b30f2				machine "i-01340c203684b30f2" has not yet joined cluster
Machine	i-050cd20c43ddd6a2b				machine "i-050cd20c43ddd6a2b" has not yet joined cluster
Machine	i-06c45a9e06d6f5e3e				machine "i-06c45a9e06d6f5e3e" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-bzhzf		system-cluster-critical pod "coredns-6c8944dbdc-bzhzf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-s8g97	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-s8g97" is pending

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

... skipping 7 lines ...
Machine	i-01340c203684b30f2				machine "i-01340c203684b30f2" has not yet joined cluster
Machine	i-050cd20c43ddd6a2b				machine "i-050cd20c43ddd6a2b" has not yet joined cluster
Machine	i-06c45a9e06d6f5e3e				machine "i-06c45a9e06d6f5e3e" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-bzhzf		system-cluster-critical pod "coredns-6c8944dbdc-bzhzf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-s8g97	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-s8g97" is pending

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

... skipping 7 lines ...
Machine	i-01340c203684b30f2				machine "i-01340c203684b30f2" has not yet joined cluster
Machine	i-050cd20c43ddd6a2b				machine "i-050cd20c43ddd6a2b" has not yet joined cluster
Machine	i-06c45a9e06d6f5e3e				machine "i-06c45a9e06d6f5e3e" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-bzhzf		system-cluster-critical pod "coredns-6c8944dbdc-bzhzf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-s8g97	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-s8g97" is pending

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

... skipping 7 lines ...
Machine	i-01340c203684b30f2				machine "i-01340c203684b30f2" has not yet joined cluster
Machine	i-050cd20c43ddd6a2b				machine "i-050cd20c43ddd6a2b" has not yet joined cluster
Machine	i-06c45a9e06d6f5e3e				machine "i-06c45a9e06d6f5e3e" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-bzhzf		system-cluster-critical pod "coredns-6c8944dbdc-bzhzf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-s8g97	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-s8g97" is pending

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

... skipping 7 lines ...
Machine	i-01340c203684b30f2				machine "i-01340c203684b30f2" has not yet joined cluster
Machine	i-050cd20c43ddd6a2b				machine "i-050cd20c43ddd6a2b" has not yet joined cluster
Machine	i-06c45a9e06d6f5e3e				machine "i-06c45a9e06d6f5e3e" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-bzhzf		system-cluster-critical pod "coredns-6c8944dbdc-bzhzf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-s8g97	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-s8g97" is pending

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

... skipping 7 lines ...
Machine	i-01340c203684b30f2				machine "i-01340c203684b30f2" has not yet joined cluster
Machine	i-050cd20c43ddd6a2b				machine "i-050cd20c43ddd6a2b" has not yet joined cluster
Machine	i-06c45a9e06d6f5e3e				machine "i-06c45a9e06d6f5e3e" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-bzhzf		system-cluster-critical pod "coredns-6c8944dbdc-bzhzf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-s8g97	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-s8g97" is pending

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

... skipping 7 lines ...
Machine	i-01340c203684b30f2				machine "i-01340c203684b30f2" has not yet joined cluster
Machine	i-050cd20c43ddd6a2b				machine "i-050cd20c43ddd6a2b" has not yet joined cluster
Machine	i-06c45a9e06d6f5e3e				machine "i-06c45a9e06d6f5e3e" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-bzhzf		system-cluster-critical pod "coredns-6c8944dbdc-bzhzf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-s8g97	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-s8g97" is pending

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

... skipping 7 lines ...
Machine	i-01340c203684b30f2				machine "i-01340c203684b30f2" has not yet joined cluster
Machine	i-050cd20c43ddd6a2b				machine "i-050cd20c43ddd6a2b" has not yet joined cluster
Machine	i-06c45a9e06d6f5e3e				machine "i-06c45a9e06d6f5e3e" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-bzhzf		system-cluster-critical pod "coredns-6c8944dbdc-bzhzf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-s8g97	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-s8g97" is pending

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

... skipping 7 lines ...
Machine	i-01340c203684b30f2				machine "i-01340c203684b30f2" has not yet joined cluster
Machine	i-050cd20c43ddd6a2b				machine "i-050cd20c43ddd6a2b" has not yet joined cluster
Machine	i-06c45a9e06d6f5e3e				machine "i-06c45a9e06d6f5e3e" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-bzhzf		system-cluster-critical pod "coredns-6c8944dbdc-bzhzf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-s8g97	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-s8g97" is pending

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

... skipping 7 lines ...
Machine	i-01340c203684b30f2				machine "i-01340c203684b30f2" has not yet joined cluster
Machine	i-050cd20c43ddd6a2b				machine "i-050cd20c43ddd6a2b" has not yet joined cluster
Machine	i-06c45a9e06d6f5e3e				machine "i-06c45a9e06d6f5e3e" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-bzhzf		system-cluster-critical pod "coredns-6c8944dbdc-bzhzf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-s8g97	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-s8g97" is pending

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

... skipping 7 lines ...
Machine	i-01340c203684b30f2				machine "i-01340c203684b30f2" has not yet joined cluster
Machine	i-050cd20c43ddd6a2b				machine "i-050cd20c43ddd6a2b" has not yet joined cluster
Machine	i-06c45a9e06d6f5e3e				machine "i-06c45a9e06d6f5e3e" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-bzhzf		system-cluster-critical pod "coredns-6c8944dbdc-bzhzf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-s8g97	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-s8g97" is pending

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

... skipping 7 lines ...
Machine	i-01340c203684b30f2				machine "i-01340c203684b30f2" has not yet joined cluster
Machine	i-050cd20c43ddd6a2b				machine "i-050cd20c43ddd6a2b" has not yet joined cluster
Machine	i-06c45a9e06d6f5e3e				machine "i-06c45a9e06d6f5e3e" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-bzhzf		system-cluster-critical pod "coredns-6c8944dbdc-bzhzf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-s8g97	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-s8g97" is pending

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

... skipping 7 lines ...
Machine	i-01340c203684b30f2				machine "i-01340c203684b30f2" has not yet joined cluster
Machine	i-050cd20c43ddd6a2b				machine "i-050cd20c43ddd6a2b" has not yet joined cluster
Machine	i-06c45a9e06d6f5e3e				machine "i-06c45a9e06d6f5e3e" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-bzhzf		system-cluster-critical pod "coredns-6c8944dbdc-bzhzf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-s8g97	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-s8g97" is pending

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

... skipping 7 lines ...
Machine	i-01340c203684b30f2				machine "i-01340c203684b30f2" has not yet joined cluster
Machine	i-050cd20c43ddd6a2b				machine "i-050cd20c43ddd6a2b" has not yet joined cluster
Machine	i-06c45a9e06d6f5e3e				machine "i-06c45a9e06d6f5e3e" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-bzhzf		system-cluster-critical pod "coredns-6c8944dbdc-bzhzf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-s8g97	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-s8g97" is pending

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

... skipping 7 lines ...
Machine	i-01340c203684b30f2				machine "i-01340c203684b30f2" has not yet joined cluster
Machine	i-050cd20c43ddd6a2b				machine "i-050cd20c43ddd6a2b" has not yet joined cluster
Machine	i-06c45a9e06d6f5e3e				machine "i-06c45a9e06d6f5e3e" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-bzhzf		system-cluster-critical pod "coredns-6c8944dbdc-bzhzf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-s8g97	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-s8g97" is pending

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

... skipping 7 lines ...
Machine	i-01340c203684b30f2				machine "i-01340c203684b30f2" has not yet joined cluster
Machine	i-050cd20c43ddd6a2b				machine "i-050cd20c43ddd6a2b" has not yet joined cluster
Machine	i-06c45a9e06d6f5e3e				machine "i-06c45a9e06d6f5e3e" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-bzhzf		system-cluster-critical pod "coredns-6c8944dbdc-bzhzf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-s8g97	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-s8g97" is pending

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

... skipping 7 lines ...
Machine	i-01340c203684b30f2				machine "i-01340c203684b30f2" has not yet joined cluster
Machine	i-050cd20c43ddd6a2b				machine "i-050cd20c43ddd6a2b" has not yet joined cluster
Machine	i-06c45a9e06d6f5e3e				machine "i-06c45a9e06d6f5e3e" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-bzhzf		system-cluster-critical pod "coredns-6c8944dbdc-bzhzf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-s8g97	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-s8g97" is pending

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

... skipping 7 lines ...
Machine	i-01340c203684b30f2				machine "i-01340c203684b30f2" has not yet joined cluster
Machine	i-050cd20c43ddd6a2b				machine "i-050cd20c43ddd6a2b" has not yet joined cluster
Machine	i-06c45a9e06d6f5e3e				machine "i-06c45a9e06d6f5e3e" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-bzhzf		system-cluster-critical pod "coredns-6c8944dbdc-bzhzf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-s8g97	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-s8g97" is pending

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

... skipping 7 lines ...
Machine	i-01340c203684b30f2				machine "i-01340c203684b30f2" has not yet joined cluster
Machine	i-050cd20c43ddd6a2b				machine "i-050cd20c43ddd6a2b" has not yet joined cluster
Machine	i-06c45a9e06d6f5e3e				machine "i-06c45a9e06d6f5e3e" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-bzhzf		system-cluster-critical pod "coredns-6c8944dbdc-bzhzf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-s8g97	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-s8g97" is pending

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

... skipping 7 lines ...
Machine	i-01340c203684b30f2				machine "i-01340c203684b30f2" has not yet joined cluster
Machine	i-050cd20c43ddd6a2b				machine "i-050cd20c43ddd6a2b" has not yet joined cluster
Machine	i-06c45a9e06d6f5e3e				machine "i-06c45a9e06d6f5e3e" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-bzhzf		system-cluster-critical pod "coredns-6c8944dbdc-bzhzf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-s8g97	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-s8g97" is pending

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

... skipping 7 lines ...
Machine	i-01340c203684b30f2				machine "i-01340c203684b30f2" has not yet joined cluster
Machine	i-050cd20c43ddd6a2b				machine "i-050cd20c43ddd6a2b" has not yet joined cluster
Machine	i-06c45a9e06d6f5e3e				machine "i-06c45a9e06d6f5e3e" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-bzhzf		system-cluster-critical pod "coredns-6c8944dbdc-bzhzf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-s8g97	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-s8g97" is pending

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

... skipping 7 lines ...
Machine	i-01340c203684b30f2				machine "i-01340c203684b30f2" has not yet joined cluster
Machine	i-050cd20c43ddd6a2b				machine "i-050cd20c43ddd6a2b" has not yet joined cluster
Machine	i-06c45a9e06d6f5e3e				machine "i-06c45a9e06d6f5e3e" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-bzhzf		system-cluster-critical pod "coredns-6c8944dbdc-bzhzf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-s8g97	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-s8g97" is pending

Validation Failed
W1013 19:29:32.703330    1013 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
2021/10/13 19:29:42 process.go:155: Step '/tmp/kops2258164994/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m' finished in 15m4.849798126s
2021/10/13 19:29:42 process.go:153: Running: kubectl -n kube-system get pods -ojson
2021/10/13 19:29:42 process.go:153: Running: /tmp/kops2258164994/kops toolbox dump --name e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io -ojson
I1013 19:29:42.733952    1026 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
2021/10/13 19:29:44 process.go:155: Step 'kubectl -n kube-system get pods -ojson' finished in 2.137729737s
2021/10/13 19:29:44 process.go:153: Running: kubectl -n kube-system logs --all-containers coredns-6c8944dbdc-bzhzf
... skipping 40 lines ...
2021/10/13 19:30:09 dump.go:413: Running SSH command: sudo cat /var/log/etcd.log
2021/10/13 19:30:09 dump.go:413: Running SSH command: sudo cat /var/log/etcd-events.log
2021/10/13 19:30:10 dump.go:413: Running SSH command: sudo cat /var/log/kube-proxy.log
2021/10/13 19:30:10 dump.go:413: Running SSH command: sudo cat /var/log/cloud-init-output.log
2021/10/13 19:30:11 dump.go:129: dumping node not registered in kubernetes: 3.109.58.247
2021/10/13 19:30:11 dump.go:163: Dumping node 3.109.58.247
2021/10/13 19:30:13 dump.go:132: error dumping node 3.109.58.247: could not connect: unable to SSH to "3.109.58.247": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/13 19:30:13 dump.go:129: dumping node not registered in kubernetes: 52.66.237.172
2021/10/13 19:30:13 dump.go:163: Dumping node 52.66.237.172
2021/10/13 19:30:14 dump.go:132: error dumping node 52.66.237.172: could not connect: unable to SSH to "52.66.237.172": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/13 19:30:14 dump.go:129: dumping node not registered in kubernetes: 52.66.246.95
2021/10/13 19:30:14 dump.go:163: Dumping node 52.66.246.95
2021/10/13 19:30:17 dump.go:132: error dumping node 52.66.246.95: could not connect: unable to SSH to "52.66.246.95": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/13 19:30:17 dump.go:129: dumping node not registered in kubernetes: 15.206.205.247
2021/10/13 19:30:17 dump.go:163: Dumping node 15.206.205.247
2021/10/13 19:30:18 dump.go:132: error dumping node 15.206.205.247: could not connect: unable to SSH to "15.206.205.247": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/13 19:30:18 process.go:153: Running: /tmp/kops2258164994/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io
I1013 19:30:18.832962    1172 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
NAME							CLOUD	ZONES
e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io	aws	ap-south-1b
2021/10/13 19:30:19 process.go:155: Step '/tmp/kops2258164994/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 498.247405ms
2021/10/13 19:30:19 process.go:153: Running: /tmp/kops2258164994/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes
... skipping 192 lines ...
dhcp-options:dopt-03132b3f9989e15fe	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/13 19:32:00 process.go:155: Step '/tmp/kops2258164994/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes' finished in 1m41.083462004s
2021/10/13 19:32:00 process.go:96: Saved XML output to /logs/artifacts/junit_runner.xml.
2021/10/13 19:32:00 main.go:331: Something went wrong: starting e2e cluster: kops validate cluster failed: error during /tmp/kops2258164994/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 ...