This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 5 succeeded
Started2021-10-18 19:16
Elapsed18m5s
Revision
job-versionv1.23.0-alpha.3.366+a78e3133a0d040
kubetest-version
revisionv1.23.0-alpha.3.366+a78e3133a0d040

Test Failures


kubetest Up 15m35s

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

Filter through log files | View test history on testgrid


Show 5 Passed Tests

Error lines from build-log.txt

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

Extracting /workspace/kubernetes/test/kubernetes-test-linux-amd64.tar.gz into /workspace/kubernetes/platforms/linux/amd64
2021/10/18 19:17:24 process.go:155: Step './get-kube.sh' finished in 27.033455601s
2021/10/18 19:17:24 process.go:153: Running: /tmp/kops2875186422/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/18 19:17:24 process.go:155: Step '/tmp/kops2875186422/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 514.517623ms
2021/10/18 19:17:24 util.go:42: curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/18 19:17:24 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/18 19:17:24 util.go:68: curl https://ip.jsb.workers.dev
2021/10/18 19:17:25 kops.go:439: Using external IP for admin access: 35.192.147.67/32
2021/10/18 19:17:25 process.go:153: Running: /tmp/kops2875186422/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.366+a78e3133a0d040 --admin-access 35.192.147.67/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
I1018 19:17:25.085592     989 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1018 19:17:25.108728     989 create_cluster.go:838] Using SSH public key: /workspace/.ssh/kube_aws_rsa.pub
I1018 19:17:25.635633     989 new_cluster.go:1077]  Cloud Provider ID = aws
... skipping 31 lines ...

2021/10/18 19:17:56 process.go:155: Step '/tmp/kops2875186422/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.366+a78e3133a0d040 --admin-access 35.192.147.67/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 31.131117917s
2021/10/18 19:17:56 process.go:153: Running: /tmp/kops2875186422/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m
I1018 19:17:56.216807    1010 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io

W1018 19:17:58.008311    1010 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
W1018 19:18:08.041525    1010 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
W1018 19:18:18.077443    1010 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
W1018 19:18:28.109349    1010 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
W1018 19:18:38.147877    1010 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
W1018 19:18:48.197641    1010 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
W1018 19:18:58.231117    1010 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
W1018 19:19:08.265013    1010 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
W1018 19:19:18.298288    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
W1018 19:19:28.329551    1010 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
W1018 19:19:38.362982    1010 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
W1018 19:19:48.399446    1010 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
W1018 19:19:58.445427    1010 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
W1018 19:20:08.490888    1010 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
W1018 19:20:18.527781    1010 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
W1018 19:20:28.563639    1010 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
W1018 19:20:38.630791    1010 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
W1018 19:20:48.665963    1010 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
W1018 19:20:58.707233    1010 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
W1018 19:21:08.745757    1010 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
W1018 19:21:18.778272    1010 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
W1018 19:21:28.829653    1010 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
W1018 19:21:38.859789    1010 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
W1018 19:21:48.896563    1010 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
W1018 19:21:58.939597    1010 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
W1018 19:22:08.974937    1010 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
W1018 19:22:19.006889    1010 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
W1018 19:22:29.044122    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
W1018 19:23:09.081147    1010 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-064e78ffb1eeee82b				machine "i-064e78ffb1eeee82b" has not yet joined cluster
Machine	i-06c79888ec9bc683e				machine "i-06c79888ec9bc683e" has not yet joined cluster
Machine	i-0c2f541aef7566ada				machine "i-0c2f541aef7566ada" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-6wzxh		system-cluster-critical pod "coredns-6c8944dbdc-6wzxh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-chw4b	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-chw4b" is pending

Validation Failed
W1018 19:23:24.625700    1010 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-064e78ffb1eeee82b				machine "i-064e78ffb1eeee82b" has not yet joined cluster
Machine	i-06c79888ec9bc683e				machine "i-06c79888ec9bc683e" has not yet joined cluster
Machine	i-0c2f541aef7566ada				machine "i-0c2f541aef7566ada" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-6wzxh		system-cluster-critical pod "coredns-6c8944dbdc-6wzxh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-chw4b	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-chw4b" is pending

Validation Failed
W1018 19:23:38.588269    1010 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-064e78ffb1eeee82b				machine "i-064e78ffb1eeee82b" has not yet joined cluster
Machine	i-06c79888ec9bc683e				machine "i-06c79888ec9bc683e" has not yet joined cluster
Machine	i-0c2f541aef7566ada				machine "i-0c2f541aef7566ada" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-6wzxh		system-cluster-critical pod "coredns-6c8944dbdc-6wzxh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-chw4b	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-chw4b" is pending

Validation Failed
W1018 19:23:52.212223    1010 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-064e78ffb1eeee82b				machine "i-064e78ffb1eeee82b" has not yet joined cluster
Machine	i-06c79888ec9bc683e				machine "i-06c79888ec9bc683e" has not yet joined cluster
Machine	i-0c2f541aef7566ada				machine "i-0c2f541aef7566ada" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-6wzxh		system-cluster-critical pod "coredns-6c8944dbdc-6wzxh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-chw4b	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-chw4b" is pending

Validation Failed
W1018 19:24:05.830566    1010 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-064e78ffb1eeee82b				machine "i-064e78ffb1eeee82b" has not yet joined cluster
Machine	i-06c79888ec9bc683e				machine "i-06c79888ec9bc683e" has not yet joined cluster
Machine	i-0c2f541aef7566ada				machine "i-0c2f541aef7566ada" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-6wzxh		system-cluster-critical pod "coredns-6c8944dbdc-6wzxh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-chw4b	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-chw4b" is pending

Validation Failed
W1018 19:24:19.559371    1010 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-064e78ffb1eeee82b				machine "i-064e78ffb1eeee82b" has not yet joined cluster
Machine	i-06c79888ec9bc683e				machine "i-06c79888ec9bc683e" has not yet joined cluster
Machine	i-0c2f541aef7566ada				machine "i-0c2f541aef7566ada" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-6wzxh		system-cluster-critical pod "coredns-6c8944dbdc-6wzxh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-chw4b	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-chw4b" is pending

Validation Failed
W1018 19:24:33.214414    1010 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-064e78ffb1eeee82b				machine "i-064e78ffb1eeee82b" has not yet joined cluster
Machine	i-06c79888ec9bc683e				machine "i-06c79888ec9bc683e" has not yet joined cluster
Machine	i-0c2f541aef7566ada				machine "i-0c2f541aef7566ada" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-6wzxh		system-cluster-critical pod "coredns-6c8944dbdc-6wzxh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-chw4b	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-chw4b" is pending

Validation Failed
W1018 19:24:46.864530    1010 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-064e78ffb1eeee82b				machine "i-064e78ffb1eeee82b" has not yet joined cluster
Machine	i-06c79888ec9bc683e				machine "i-06c79888ec9bc683e" has not yet joined cluster
Machine	i-0c2f541aef7566ada				machine "i-0c2f541aef7566ada" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-6wzxh		system-cluster-critical pod "coredns-6c8944dbdc-6wzxh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-chw4b	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-chw4b" is pending

Validation Failed
W1018 19:25:00.748359    1010 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-064e78ffb1eeee82b				machine "i-064e78ffb1eeee82b" has not yet joined cluster
Machine	i-06c79888ec9bc683e				machine "i-06c79888ec9bc683e" has not yet joined cluster
Machine	i-0c2f541aef7566ada				machine "i-0c2f541aef7566ada" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-6wzxh		system-cluster-critical pod "coredns-6c8944dbdc-6wzxh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-chw4b	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-chw4b" is pending

Validation Failed
W1018 19:25:14.448269    1010 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-064e78ffb1eeee82b				machine "i-064e78ffb1eeee82b" has not yet joined cluster
Machine	i-06c79888ec9bc683e				machine "i-06c79888ec9bc683e" has not yet joined cluster
Machine	i-0c2f541aef7566ada				machine "i-0c2f541aef7566ada" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-6wzxh		system-cluster-critical pod "coredns-6c8944dbdc-6wzxh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-chw4b	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-chw4b" is pending

Validation Failed
W1018 19:25:28.126803    1010 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-064e78ffb1eeee82b				machine "i-064e78ffb1eeee82b" has not yet joined cluster
Machine	i-06c79888ec9bc683e				machine "i-06c79888ec9bc683e" has not yet joined cluster
Machine	i-0c2f541aef7566ada				machine "i-0c2f541aef7566ada" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-6wzxh		system-cluster-critical pod "coredns-6c8944dbdc-6wzxh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-chw4b	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-chw4b" is pending

Validation Failed
W1018 19:25:42.304963    1010 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-064e78ffb1eeee82b				machine "i-064e78ffb1eeee82b" has not yet joined cluster
Machine	i-06c79888ec9bc683e				machine "i-06c79888ec9bc683e" has not yet joined cluster
Machine	i-0c2f541aef7566ada				machine "i-0c2f541aef7566ada" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-6wzxh		system-cluster-critical pod "coredns-6c8944dbdc-6wzxh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-chw4b	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-chw4b" is pending

Validation Failed
W1018 19:25:56.092319    1010 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-064e78ffb1eeee82b				machine "i-064e78ffb1eeee82b" has not yet joined cluster
Machine	i-06c79888ec9bc683e				machine "i-06c79888ec9bc683e" has not yet joined cluster
Machine	i-0c2f541aef7566ada				machine "i-0c2f541aef7566ada" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-6wzxh		system-cluster-critical pod "coredns-6c8944dbdc-6wzxh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-chw4b	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-chw4b" is pending

Validation Failed
W1018 19:26:09.825841    1010 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-064e78ffb1eeee82b				machine "i-064e78ffb1eeee82b" has not yet joined cluster
Machine	i-06c79888ec9bc683e				machine "i-06c79888ec9bc683e" has not yet joined cluster
Machine	i-0c2f541aef7566ada				machine "i-0c2f541aef7566ada" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-6wzxh		system-cluster-critical pod "coredns-6c8944dbdc-6wzxh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-chw4b	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-chw4b" is pending

Validation Failed
W1018 19:26:23.744362    1010 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-064e78ffb1eeee82b				machine "i-064e78ffb1eeee82b" has not yet joined cluster
Machine	i-06c79888ec9bc683e				machine "i-06c79888ec9bc683e" has not yet joined cluster
Machine	i-0c2f541aef7566ada				machine "i-0c2f541aef7566ada" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-6wzxh		system-cluster-critical pod "coredns-6c8944dbdc-6wzxh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-chw4b	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-chw4b" is pending

Validation Failed
W1018 19:26:37.659615    1010 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-064e78ffb1eeee82b				machine "i-064e78ffb1eeee82b" has not yet joined cluster
Machine	i-06c79888ec9bc683e				machine "i-06c79888ec9bc683e" has not yet joined cluster
Machine	i-0c2f541aef7566ada				machine "i-0c2f541aef7566ada" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-6wzxh		system-cluster-critical pod "coredns-6c8944dbdc-6wzxh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-chw4b	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-chw4b" is pending

Validation Failed
W1018 19:26:51.259349    1010 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-064e78ffb1eeee82b				machine "i-064e78ffb1eeee82b" has not yet joined cluster
Machine	i-06c79888ec9bc683e				machine "i-06c79888ec9bc683e" has not yet joined cluster
Machine	i-0c2f541aef7566ada				machine "i-0c2f541aef7566ada" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-6wzxh		system-cluster-critical pod "coredns-6c8944dbdc-6wzxh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-chw4b	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-chw4b" is pending

Validation Failed
W1018 19:27:04.990835    1010 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-064e78ffb1eeee82b				machine "i-064e78ffb1eeee82b" has not yet joined cluster
Machine	i-06c79888ec9bc683e				machine "i-06c79888ec9bc683e" has not yet joined cluster
Machine	i-0c2f541aef7566ada				machine "i-0c2f541aef7566ada" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-6wzxh		system-cluster-critical pod "coredns-6c8944dbdc-6wzxh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-chw4b	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-chw4b" is pending

Validation Failed
W1018 19:27:19.444668    1010 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-064e78ffb1eeee82b				machine "i-064e78ffb1eeee82b" has not yet joined cluster
Machine	i-06c79888ec9bc683e				machine "i-06c79888ec9bc683e" has not yet joined cluster
Machine	i-0c2f541aef7566ada				machine "i-0c2f541aef7566ada" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-6wzxh		system-cluster-critical pod "coredns-6c8944dbdc-6wzxh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-chw4b	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-chw4b" is pending

Validation Failed
W1018 19:27:33.187271    1010 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-064e78ffb1eeee82b				machine "i-064e78ffb1eeee82b" has not yet joined cluster
Machine	i-06c79888ec9bc683e				machine "i-06c79888ec9bc683e" has not yet joined cluster
Machine	i-0c2f541aef7566ada				machine "i-0c2f541aef7566ada" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-6wzxh		system-cluster-critical pod "coredns-6c8944dbdc-6wzxh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-chw4b	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-chw4b" is pending

Validation Failed
W1018 19:27:46.836357    1010 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-064e78ffb1eeee82b				machine "i-064e78ffb1eeee82b" has not yet joined cluster
Machine	i-06c79888ec9bc683e				machine "i-06c79888ec9bc683e" has not yet joined cluster
Machine	i-0c2f541aef7566ada				machine "i-0c2f541aef7566ada" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-6wzxh		system-cluster-critical pod "coredns-6c8944dbdc-6wzxh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-chw4b	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-chw4b" is pending

Validation Failed
W1018 19:28:00.581963    1010 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-064e78ffb1eeee82b				machine "i-064e78ffb1eeee82b" has not yet joined cluster
Machine	i-06c79888ec9bc683e				machine "i-06c79888ec9bc683e" has not yet joined cluster
Machine	i-0c2f541aef7566ada				machine "i-0c2f541aef7566ada" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-6wzxh		system-cluster-critical pod "coredns-6c8944dbdc-6wzxh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-chw4b	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-chw4b" is pending

Validation Failed
W1018 19:28:14.556244    1010 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-064e78ffb1eeee82b				machine "i-064e78ffb1eeee82b" has not yet joined cluster
Machine	i-06c79888ec9bc683e				machine "i-06c79888ec9bc683e" has not yet joined cluster
Machine	i-0c2f541aef7566ada				machine "i-0c2f541aef7566ada" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-6wzxh		system-cluster-critical pod "coredns-6c8944dbdc-6wzxh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-chw4b	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-chw4b" is pending

Validation Failed
W1018 19:28:28.208654    1010 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-064e78ffb1eeee82b				machine "i-064e78ffb1eeee82b" has not yet joined cluster
Machine	i-06c79888ec9bc683e				machine "i-06c79888ec9bc683e" has not yet joined cluster
Machine	i-0c2f541aef7566ada				machine "i-0c2f541aef7566ada" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-6wzxh		system-cluster-critical pod "coredns-6c8944dbdc-6wzxh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-chw4b	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-chw4b" is pending

Validation Failed
W1018 19:28:42.105541    1010 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-064e78ffb1eeee82b				machine "i-064e78ffb1eeee82b" has not yet joined cluster
Machine	i-06c79888ec9bc683e				machine "i-06c79888ec9bc683e" has not yet joined cluster
Machine	i-0c2f541aef7566ada				machine "i-0c2f541aef7566ada" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-6wzxh		system-cluster-critical pod "coredns-6c8944dbdc-6wzxh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-chw4b	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-chw4b" is pending

Validation Failed
W1018 19:28:55.849078    1010 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-064e78ffb1eeee82b				machine "i-064e78ffb1eeee82b" has not yet joined cluster
Machine	i-06c79888ec9bc683e				machine "i-06c79888ec9bc683e" has not yet joined cluster
Machine	i-0c2f541aef7566ada				machine "i-0c2f541aef7566ada" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-6wzxh		system-cluster-critical pod "coredns-6c8944dbdc-6wzxh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-chw4b	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-chw4b" is pending

Validation Failed
W1018 19:29:09.556759    1010 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-064e78ffb1eeee82b				machine "i-064e78ffb1eeee82b" has not yet joined cluster
Machine	i-06c79888ec9bc683e				machine "i-06c79888ec9bc683e" has not yet joined cluster
Machine	i-0c2f541aef7566ada				machine "i-0c2f541aef7566ada" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-6wzxh		system-cluster-critical pod "coredns-6c8944dbdc-6wzxh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-chw4b	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-chw4b" is pending

Validation Failed
W1018 19:29:23.170125    1010 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-064e78ffb1eeee82b				machine "i-064e78ffb1eeee82b" has not yet joined cluster
Machine	i-06c79888ec9bc683e				machine "i-06c79888ec9bc683e" has not yet joined cluster
Machine	i-0c2f541aef7566ada				machine "i-0c2f541aef7566ada" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-6wzxh		system-cluster-critical pod "coredns-6c8944dbdc-6wzxh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-chw4b	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-chw4b" is pending

Validation Failed
W1018 19:29:36.789477    1010 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-064e78ffb1eeee82b				machine "i-064e78ffb1eeee82b" has not yet joined cluster
Machine	i-06c79888ec9bc683e				machine "i-06c79888ec9bc683e" has not yet joined cluster
Machine	i-0c2f541aef7566ada				machine "i-0c2f541aef7566ada" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-6wzxh		system-cluster-critical pod "coredns-6c8944dbdc-6wzxh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-chw4b	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-chw4b" is pending

Validation Failed
W1018 19:29:50.507807    1010 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-064e78ffb1eeee82b				machine "i-064e78ffb1eeee82b" has not yet joined cluster
Machine	i-06c79888ec9bc683e				machine "i-06c79888ec9bc683e" has not yet joined cluster
Machine	i-0c2f541aef7566ada				machine "i-0c2f541aef7566ada" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-6wzxh		system-cluster-critical pod "coredns-6c8944dbdc-6wzxh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-chw4b	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-chw4b" is pending

Validation Failed
W1018 19:30:04.490585    1010 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-064e78ffb1eeee82b				machine "i-064e78ffb1eeee82b" has not yet joined cluster
Machine	i-06c79888ec9bc683e				machine "i-06c79888ec9bc683e" has not yet joined cluster
Machine	i-0c2f541aef7566ada				machine "i-0c2f541aef7566ada" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-6wzxh		system-cluster-critical pod "coredns-6c8944dbdc-6wzxh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-chw4b	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-chw4b" is pending

Validation Failed
W1018 19:30:18.176835    1010 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-064e78ffb1eeee82b				machine "i-064e78ffb1eeee82b" has not yet joined cluster
Machine	i-06c79888ec9bc683e				machine "i-06c79888ec9bc683e" has not yet joined cluster
Machine	i-0c2f541aef7566ada				machine "i-0c2f541aef7566ada" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-6wzxh		system-cluster-critical pod "coredns-6c8944dbdc-6wzxh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-chw4b	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-chw4b" is pending

Validation Failed
W1018 19:30:31.895965    1010 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-064e78ffb1eeee82b				machine "i-064e78ffb1eeee82b" has not yet joined cluster
Machine	i-06c79888ec9bc683e				machine "i-06c79888ec9bc683e" has not yet joined cluster
Machine	i-0c2f541aef7566ada				machine "i-0c2f541aef7566ada" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-6wzxh		system-cluster-critical pod "coredns-6c8944dbdc-6wzxh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-chw4b	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-chw4b" is pending

Validation Failed
W1018 19:30:45.629637    1010 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-064e78ffb1eeee82b				machine "i-064e78ffb1eeee82b" has not yet joined cluster
Machine	i-06c79888ec9bc683e				machine "i-06c79888ec9bc683e" has not yet joined cluster
Machine	i-0c2f541aef7566ada				machine "i-0c2f541aef7566ada" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-6wzxh		system-cluster-critical pod "coredns-6c8944dbdc-6wzxh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-chw4b	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-chw4b" is pending

Validation Failed
W1018 19:30:59.346033    1010 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-064e78ffb1eeee82b				machine "i-064e78ffb1eeee82b" has not yet joined cluster
Machine	i-06c79888ec9bc683e				machine "i-06c79888ec9bc683e" has not yet joined cluster
Machine	i-0c2f541aef7566ada				machine "i-0c2f541aef7566ada" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-6wzxh		system-cluster-critical pod "coredns-6c8944dbdc-6wzxh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-chw4b	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-chw4b" is pending

Validation Failed
W1018 19:31:13.752137    1010 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-064e78ffb1eeee82b				machine "i-064e78ffb1eeee82b" has not yet joined cluster
Machine	i-06c79888ec9bc683e				machine "i-06c79888ec9bc683e" has not yet joined cluster
Machine	i-0c2f541aef7566ada				machine "i-0c2f541aef7566ada" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-6wzxh		system-cluster-critical pod "coredns-6c8944dbdc-6wzxh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-chw4b	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-chw4b" is pending

Validation Failed
W1018 19:31:27.558494    1010 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-064e78ffb1eeee82b				machine "i-064e78ffb1eeee82b" has not yet joined cluster
Machine	i-06c79888ec9bc683e				machine "i-06c79888ec9bc683e" has not yet joined cluster
Machine	i-0c2f541aef7566ada				machine "i-0c2f541aef7566ada" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-6wzxh		system-cluster-critical pod "coredns-6c8944dbdc-6wzxh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-chw4b	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-chw4b" is pending

Validation Failed
W1018 19:31:41.238061    1010 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-064e78ffb1eeee82b				machine "i-064e78ffb1eeee82b" has not yet joined cluster
Machine	i-06c79888ec9bc683e				machine "i-06c79888ec9bc683e" has not yet joined cluster
Machine	i-0c2f541aef7566ada				machine "i-0c2f541aef7566ada" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-6wzxh		system-cluster-critical pod "coredns-6c8944dbdc-6wzxh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-chw4b	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-chw4b" is pending

Validation Failed
W1018 19:31:55.197357    1010 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-064e78ffb1eeee82b				machine "i-064e78ffb1eeee82b" has not yet joined cluster
Machine	i-06c79888ec9bc683e				machine "i-06c79888ec9bc683e" has not yet joined cluster
Machine	i-0c2f541aef7566ada				machine "i-0c2f541aef7566ada" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-6wzxh		system-cluster-critical pod "coredns-6c8944dbdc-6wzxh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-chw4b	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-chw4b" is pending

Validation Failed
W1018 19:32:08.886484    1010 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-064e78ffb1eeee82b				machine "i-064e78ffb1eeee82b" has not yet joined cluster
Machine	i-06c79888ec9bc683e				machine "i-06c79888ec9bc683e" has not yet joined cluster
Machine	i-0c2f541aef7566ada				machine "i-0c2f541aef7566ada" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-6wzxh		system-cluster-critical pod "coredns-6c8944dbdc-6wzxh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-chw4b	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-chw4b" is pending

Validation Failed
W1018 19:32:22.854811    1010 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-064e78ffb1eeee82b				machine "i-064e78ffb1eeee82b" has not yet joined cluster
Machine	i-06c79888ec9bc683e				machine "i-06c79888ec9bc683e" has not yet joined cluster
Machine	i-0c2f541aef7566ada				machine "i-0c2f541aef7566ada" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-6wzxh		system-cluster-critical pod "coredns-6c8944dbdc-6wzxh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-chw4b	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-chw4b" is pending

Validation Failed
W1018 19:32:36.803974    1010 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-064e78ffb1eeee82b				machine "i-064e78ffb1eeee82b" has not yet joined cluster
Machine	i-06c79888ec9bc683e				machine "i-06c79888ec9bc683e" has not yet joined cluster
Machine	i-0c2f541aef7566ada				machine "i-0c2f541aef7566ada" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-6wzxh		system-cluster-critical pod "coredns-6c8944dbdc-6wzxh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-chw4b	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-chw4b" is pending

Validation Failed
W1018 19:32:50.700324    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
2021/10/18 19:33:00 process.go:155: Step '/tmp/kops2875186422/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m' finished in 15m4.51536579s
2021/10/18 19:33:00 process.go:153: Running: kubectl -n kube-system get pods -ojson
2021/10/18 19:33:00 process.go:153: Running: /tmp/kops2875186422/kops toolbox dump --name e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io -ojson
I1018 19:33:00.737832    1021 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
2021/10/18 19:33:03 process.go:155: Step 'kubectl -n kube-system get pods -ojson' finished in 2.379073604s
2021/10/18 19:33:03 process.go:153: Running: kubectl -n kube-system logs --all-containers coredns-6c8944dbdc-6wzxh
... skipping 40 lines ...
2021/10/18 19:33:27 dump.go:413: Running SSH command: sudo cat /var/log/etcd.log
2021/10/18 19:33:28 dump.go:413: Running SSH command: sudo cat /var/log/etcd-events.log
2021/10/18 19:33:28 dump.go:413: Running SSH command: sudo cat /var/log/kube-proxy.log
2021/10/18 19:33:29 dump.go:413: Running SSH command: sudo cat /var/log/cloud-init-output.log
2021/10/18 19:33:29 dump.go:129: dumping node not registered in kubernetes: 13.126.17.100
2021/10/18 19:33:29 dump.go:163: Dumping node 13.126.17.100
2021/10/18 19:33:31 dump.go:132: error dumping node 13.126.17.100: could not connect: unable to SSH to "13.126.17.100": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/18 19:33:31 dump.go:129: dumping node not registered in kubernetes: 65.1.108.115
2021/10/18 19:33:31 dump.go:163: Dumping node 65.1.108.115
2021/10/18 19:33:33 dump.go:132: error dumping node 65.1.108.115: could not connect: unable to SSH to "65.1.108.115": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/18 19:33:33 dump.go:129: dumping node not registered in kubernetes: 13.232.252.204
2021/10/18 19:33:33 dump.go:163: Dumping node 13.232.252.204
2021/10/18 19:33:35 dump.go:132: error dumping node 13.232.252.204: could not connect: unable to SSH to "13.232.252.204": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/18 19:33:35 dump.go:129: dumping node not registered in kubernetes: 13.232.150.6
2021/10/18 19:33:35 dump.go:163: Dumping node 13.232.150.6
2021/10/18 19:33:37 dump.go:132: error dumping node 13.232.150.6: could not connect: unable to SSH to "13.232.150.6": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/18 19:33:37 process.go:153: Running: /tmp/kops2875186422/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io
I1018 19:33:37.402372    1171 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/18 19:33:37 process.go:155: Step '/tmp/kops2875186422/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 512.562665ms
2021/10/18 19:33:37 process.go:153: Running: /tmp/kops2875186422/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes
... skipping 170 lines ...
dhcp-options:dopt-0be3ef862fdee6e0b	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/18 19:34:57 process.go:155: Step '/tmp/kops2875186422/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes' finished in 1m19.617164252s
2021/10/18 19:34:57 process.go:96: Saved XML output to /logs/artifacts/junit_runner.xml.
2021/10/18 19:34:57 main.go:331: Something went wrong: starting e2e cluster: kops validate cluster failed: error during /tmp/kops2875186422/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 ...