This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 5 succeeded
Started2021-10-11 19:10
Elapsed17m59s
Revision
job-versionv1.23.0-alpha.3.266+194a3dea5de35d
kubetest-version
revisionv1.23.0-alpha.3.266+194a3dea5de35d

Test Failures


kubetest Up 15m29s

kops validate cluster failed: error during /tmp/kops2132763908/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m: exit status 1
				from junit_runner.xml

Filter through log files | View test history on testgrid


Show 5 Passed Tests

Error lines from build-log.txt

Activated service account credentials for: [pr-kubekins@kubernetes-jenkins-pull.iam.gserviceaccount.com]
fatal: not a git repository (or any of the parent directories): .git
+ WRAPPED_COMMAND_PID=30
+ wait 30
+ /workspace/scenarios/kubernetes_e2e.py --cluster=e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --deployment=kops --env=KOPS_ARCH=amd64 --env=KUBE_SSH_USER=ec2-user --env=KOPS_RUN_TOO_NEW_VERSION=1 --extract=ci/latest --ginkgo-parallel --kops-image=309956199498/RHEL-7.8_HVM_GA-20200225-x86_64-1-Hourly2-GP2 --kops-args=--master-image=137112412989/amzn2-ami-hvm-2.0.20200617.0-x86_64-gp2 --kops-overrides=spec.docker.selinuxEnabled=true --kops-priority-path=/workspace/kubernetes/platforms/linux/amd64 --kops-ssh-user=ec2-user --kops-version=https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt --provider=aws '--test_args=--ginkgo.focus=\[sig-storage\].*\[Slow\] --ginkgo.skip=\[Serial\]|\[Disruptive\]|\[Flaky\]|\[Feature:.+\] --minStartupPods=8' --timeout=120m
starts with local mode
Environment:
ARTIFACTS=/logs/artifacts
... skipping 156 lines ...
md5sum(kubernetes-test-linux-amd64.tar.gz)=885e0f7edcec5c0e19c760d5bc2cd2d1
sha512sum(kubernetes-test-linux-amd64.tar.gz)=597640a51da4797878c3e0c94c3054dc23ac608d832f458204acc53f8be41a306aed4e9df8b7d180fdf4fe5deeedf6538078983e50bd6b809e197327e85fb9b3

Extracting /workspace/kubernetes/test/kubernetes-test-linux-amd64.tar.gz into /workspace/kubernetes/platforms/linux/amd64
2021/10/11 19:11:28 process.go:155: Step './get-kube.sh' finished in 27.868420355s
2021/10/11 19:11:28 process.go:153: Running: /tmp/kops2132763908/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/11 19:11:29 process.go:155: Step '/tmp/kops2132763908/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 462.846096ms
2021/10/11 19:11:29 util.go:42: curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/11 19:11:29 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/11 19:11:29 util.go:68: curl https://ip.jsb.workers.dev
2021/10/11 19:11:29 kops.go:439: Using external IP for admin access: 34.66.93.24/32
2021/10/11 19:11:29 process.go:153: Running: /tmp/kops2132763908/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.266+194a3dea5de35d --admin-access 34.66.93.24/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
I1011 19:11:29.193293     987 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1011 19:11:29.214023     987 create_cluster.go:838] Using SSH public key: /workspace/.ssh/kube_aws_rsa.pub
I1011 19:11:29.721401     987 new_cluster.go:1077]  Cloud Provider ID = aws
... skipping 30 lines ...

2021/10/11 19:11:49 process.go:155: Step '/tmp/kops2132763908/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.266+194a3dea5de35d --admin-access 34.66.93.24/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 20.803485153s
2021/10/11 19:11:49 process.go:153: Running: /tmp/kops2132763908/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m
I1011 19:11:49.996269    1009 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io

W1011 19:11:51.814454    1009 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
W1011 19:12:01.845713    1009 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
W1011 19:12:11.881328    1009 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
W1011 19:12:21.917662    1009 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
W1011 19:12:31.955940    1009 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
W1011 19:12:41.986656    1009 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
W1011 19:12:52.018493    1009 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
W1011 19:13:02.060556    1009 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
W1011 19:13:12.097772    1009 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
W1011 19:13:22.129043    1009 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
W1011 19:13:32.194723    1009 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
W1011 19:13:42.226897    1009 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
W1011 19:13:52.258081    1009 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
W1011 19:14:02.288920    1009 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
W1011 19:14:12.353751    1009 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
W1011 19:14:22.388409    1009 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
W1011 19:14:32.423078    1009 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
W1011 19:14:42.490594    1009 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
W1011 19:14:52.571626    1009 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
W1011 19:15:02.599352    1009 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
W1011 19:15:12.637993    1009 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
W1011 19:15:22.673156    1009 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
W1011 19:15:32.720410    1009 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
W1011 19:15:42.753045    1009 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
W1011 19:15:52.808950    1009 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
W1011 19:16:02.858095    1009 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 8 lines ...
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Node	ip-172-20-41-176.ap-south-1.compute.internal	master "ip-172-20-41-176.ap-south-1.compute.internal" is missing kube-scheduler pod
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:16:18.581482    1009 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 8 lines ...
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Node	ip-172-20-41-176.ap-south-1.compute.internal	master "ip-172-20-41-176.ap-south-1.compute.internal" is missing kube-scheduler pod
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:16:32.175863    1009 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 8 lines ...
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Node	ip-172-20-41-176.ap-south-1.compute.internal	master "ip-172-20-41-176.ap-south-1.compute.internal" is missing kube-scheduler pod
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:16:46.051420    1009 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 8 lines ...
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Node	ip-172-20-41-176.ap-south-1.compute.internal	master "ip-172-20-41-176.ap-south-1.compute.internal" is missing kube-scheduler pod
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:16:59.614867    1009 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-073f83d49c0a86578				machine "i-073f83d49c0a86578" has not yet joined cluster
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:17:13.201188    1009 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-073f83d49c0a86578				machine "i-073f83d49c0a86578" has not yet joined cluster
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:17:26.802305    1009 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-073f83d49c0a86578				machine "i-073f83d49c0a86578" has not yet joined cluster
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:17:40.388846    1009 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-073f83d49c0a86578				machine "i-073f83d49c0a86578" has not yet joined cluster
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:17:54.168990    1009 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-073f83d49c0a86578				machine "i-073f83d49c0a86578" has not yet joined cluster
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:18:08.035420    1009 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-073f83d49c0a86578				machine "i-073f83d49c0a86578" has not yet joined cluster
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:18:21.773440    1009 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-073f83d49c0a86578				machine "i-073f83d49c0a86578" has not yet joined cluster
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:18:35.488989    1009 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-073f83d49c0a86578				machine "i-073f83d49c0a86578" has not yet joined cluster
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:18:49.082681    1009 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-073f83d49c0a86578				machine "i-073f83d49c0a86578" has not yet joined cluster
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:19:02.773357    1009 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-073f83d49c0a86578				machine "i-073f83d49c0a86578" has not yet joined cluster
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:19:16.594557    1009 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-073f83d49c0a86578				machine "i-073f83d49c0a86578" has not yet joined cluster
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:19:30.211607    1009 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-073f83d49c0a86578				machine "i-073f83d49c0a86578" has not yet joined cluster
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:19:44.024816    1009 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-073f83d49c0a86578				machine "i-073f83d49c0a86578" has not yet joined cluster
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:19:57.616813    1009 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-073f83d49c0a86578				machine "i-073f83d49c0a86578" has not yet joined cluster
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:20:11.852686    1009 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-073f83d49c0a86578				machine "i-073f83d49c0a86578" has not yet joined cluster
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:20:25.546341    1009 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-073f83d49c0a86578				machine "i-073f83d49c0a86578" has not yet joined cluster
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:20:39.190708    1009 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-073f83d49c0a86578				machine "i-073f83d49c0a86578" has not yet joined cluster
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:20:53.045289    1009 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-073f83d49c0a86578				machine "i-073f83d49c0a86578" has not yet joined cluster
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:21:06.694640    1009 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-073f83d49c0a86578				machine "i-073f83d49c0a86578" has not yet joined cluster
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:21:20.264920    1009 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-073f83d49c0a86578				machine "i-073f83d49c0a86578" has not yet joined cluster
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:21:33.849015    1009 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-073f83d49c0a86578				machine "i-073f83d49c0a86578" has not yet joined cluster
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:21:47.496658    1009 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-073f83d49c0a86578				machine "i-073f83d49c0a86578" has not yet joined cluster
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:22:01.181933    1009 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-073f83d49c0a86578				machine "i-073f83d49c0a86578" has not yet joined cluster
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:22:14.982539    1009 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-073f83d49c0a86578				machine "i-073f83d49c0a86578" has not yet joined cluster
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:22:28.562952    1009 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-073f83d49c0a86578				machine "i-073f83d49c0a86578" has not yet joined cluster
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:22:42.120423    1009 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-073f83d49c0a86578				machine "i-073f83d49c0a86578" has not yet joined cluster
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:22:56.019049    1009 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-073f83d49c0a86578				machine "i-073f83d49c0a86578" has not yet joined cluster
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:23:09.555383    1009 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-073f83d49c0a86578				machine "i-073f83d49c0a86578" has not yet joined cluster
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:23:23.247695    1009 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-073f83d49c0a86578				machine "i-073f83d49c0a86578" has not yet joined cluster
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:23:37.030349    1009 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-073f83d49c0a86578				machine "i-073f83d49c0a86578" has not yet joined cluster
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:23:50.607396    1009 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-073f83d49c0a86578				machine "i-073f83d49c0a86578" has not yet joined cluster
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:24:05.045202    1009 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-073f83d49c0a86578				machine "i-073f83d49c0a86578" has not yet joined cluster
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:24:18.602929    1009 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-073f83d49c0a86578				machine "i-073f83d49c0a86578" has not yet joined cluster
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:24:32.172807    1009 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-073f83d49c0a86578				machine "i-073f83d49c0a86578" has not yet joined cluster
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:24:45.785043    1009 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-073f83d49c0a86578				machine "i-073f83d49c0a86578" has not yet joined cluster
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:24:59.590562    1009 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-073f83d49c0a86578				machine "i-073f83d49c0a86578" has not yet joined cluster
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:25:13.068882    1009 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-073f83d49c0a86578				machine "i-073f83d49c0a86578" has not yet joined cluster
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:25:26.665921    1009 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-073f83d49c0a86578				machine "i-073f83d49c0a86578" has not yet joined cluster
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:25:40.193011    1009 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-073f83d49c0a86578				machine "i-073f83d49c0a86578" has not yet joined cluster
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:25:53.811162    1009 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-073f83d49c0a86578				machine "i-073f83d49c0a86578" has not yet joined cluster
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:26:07.557872    1009 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-073f83d49c0a86578				machine "i-073f83d49c0a86578" has not yet joined cluster
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:26:21.157743    1009 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-073f83d49c0a86578				machine "i-073f83d49c0a86578" has not yet joined cluster
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:26:35.012077    1009 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-073f83d49c0a86578				machine "i-073f83d49c0a86578" has not yet joined cluster
Machine	i-080df4527722cff35				machine "i-080df4527722cff35" has not yet joined cluster
Machine	i-0e0d9db8a457e4c9d				machine "i-0e0d9db8a457e4c9d" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-t625l		system-cluster-critical pod "coredns-6c8944dbdc-t625l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jm4jh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jm4jh" is pending

Validation Failed
W1011 19:26:48.661805    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
2021/10/11 19:26:58 process.go:155: Step '/tmp/kops2132763908/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m' finished in 15m8.693518731s
2021/10/11 19:26:58 process.go:153: Running: kubectl -n kube-system get pods -ojson
2021/10/11 19:26:58 process.go:153: Running: /tmp/kops2132763908/kops toolbox dump --name e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io -ojson
I1011 19:26:58.693093    1023 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
2021/10/11 19:27:00 process.go:155: Step 'kubectl -n kube-system get pods -ojson' finished in 2.310695012s
2021/10/11 19:27:00 process.go:153: Running: kubectl -n kube-system logs --all-containers coredns-6c8944dbdc-t625l
... skipping 40 lines ...
2021/10/11 19:27:24 dump.go:413: Running SSH command: sudo cat /var/log/etcd.log
2021/10/11 19:27:25 dump.go:413: Running SSH command: sudo cat /var/log/etcd-events.log
2021/10/11 19:27:25 dump.go:413: Running SSH command: sudo cat /var/log/kube-proxy.log
2021/10/11 19:27:26 dump.go:413: Running SSH command: sudo cat /var/log/cloud-init-output.log
2021/10/11 19:27:26 dump.go:129: dumping node not registered in kubernetes: 13.232.53.200
2021/10/11 19:27:26 dump.go:163: Dumping node 13.232.53.200
2021/10/11 19:27:28 dump.go:132: error dumping node 13.232.53.200: could not connect: unable to SSH to "13.232.53.200": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/11 19:27:28 dump.go:129: dumping node not registered in kubernetes: 35.154.178.191
2021/10/11 19:27:28 dump.go:163: Dumping node 35.154.178.191
2021/10/11 19:27:30 dump.go:132: error dumping node 35.154.178.191: could not connect: unable to SSH to "35.154.178.191": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/11 19:27:30 dump.go:129: dumping node not registered in kubernetes: 13.127.104.119
2021/10/11 19:27:30 dump.go:163: Dumping node 13.127.104.119
2021/10/11 19:27:32 dump.go:132: error dumping node 13.127.104.119: could not connect: unable to SSH to "13.127.104.119": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/11 19:27:32 dump.go:129: dumping node not registered in kubernetes: 3.109.210.50
2021/10/11 19:27:32 dump.go:163: Dumping node 3.109.210.50
2021/10/11 19:27:33 dump.go:132: error dumping node 3.109.210.50: could not connect: unable to SSH to "3.109.210.50": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/11 19:27:33 process.go:153: Running: /tmp/kops2132763908/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io
I1011 19:27:33.991177    1168 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/11 19:27:34 process.go:155: Step '/tmp/kops2132763908/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 502.431371ms
2021/10/11 19:27:34 process.go:153: Running: /tmp/kops2132763908/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes
... skipping 164 lines ...
dhcp-options:dopt-0970b67c60227decc	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/11 19:28:52 process.go:155: Step '/tmp/kops2132763908/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes' finished in 1m18.216847967s
2021/10/11 19:28:52 process.go:96: Saved XML output to /logs/artifacts/junit_runner.xml.
2021/10/11 19:28:52 main.go:331: Something went wrong: starting e2e cluster: kops validate cluster failed: error during /tmp/kops2132763908/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 ...