This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 5 succeeded
Started2021-10-22 19:20
Elapsed18m45s
Revision
job-versionv1.23.0-alpha.3.489+679f520acccbf5
kubetest-version
revisionv1.23.0-alpha.3.489+679f520acccbf5

Test Failures


kubetest Up 15m42s

kops validate cluster failed: error during /tmp/kops3395341141/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=32
+ wait 32
+ /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)=bef5260d6683cd1b2c3f0df9dba17af1
sha512sum(kubernetes-test-linux-amd64.tar.gz)=5c644c50dc15c8dbcce42b5027c4000105e5e81f3e9656e9c166c5e26969ceac56b4ed84485bd874f1e305ec1ad0866c0d33f805f8b3e794540b3cb9dc4a831d

Extracting /workspace/kubernetes/test/kubernetes-test-linux-amd64.tar.gz into /workspace/kubernetes/platforms/linux/amd64
2021/10/22 19:21:13 process.go:155: Step './get-kube.sh' finished in 26.0856846s
2021/10/22 19:21:13 process.go:153: Running: /tmp/kops3395341141/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/22 19:21:14 process.go:155: Step '/tmp/kops3395341141/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 477.12084ms
2021/10/22 19:21:14 util.go:42: curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/22 19:21:14 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/22 19:21:14 util.go:68: curl https://ip.jsb.workers.dev
2021/10/22 19:21:14 kops.go:439: Using external IP for admin access: 34.134.86.254/32
2021/10/22 19:21:14 process.go:153: Running: /tmp/kops3395341141/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.489+679f520acccbf5 --admin-access 34.134.86.254/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
I1022 19:21:14.337529     987 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1022 19:21:14.363507     987 create_cluster.go:838] Using SSH public key: /workspace/.ssh/kube_aws_rsa.pub
I1022 19:21:14.817933     987 new_cluster.go:1077]  Cloud Provider ID = aws
... skipping 31 lines ...

2021/10/22 19:21:45 process.go:155: Step '/tmp/kops3395341141/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.489+679f520acccbf5 --admin-access 34.134.86.254/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 30.79905762s
2021/10/22 19:21:45 process.go:153: Running: /tmp/kops3395341141/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m
I1022 19:21:45.138938    1008 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io

W1022 19:21:46.901136    1008 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-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
W1022 19:21:56.933547    1008 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
W1022 19:22:06.987930    1008 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
W1022 19:22:17.032554    1008 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
W1022 19:22:27.082802    1008 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
W1022 19:22:37.113662    1008 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
W1022 19:22:47.160511    1008 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
W1022 19:22:57.191592    1008 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
W1022 19:23:07.229269    1008 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
W1022 19:23:17.273102    1008 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
W1022 19:23:27.306887    1008 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
W1022 19:23:37.342080    1008 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
W1022 19:23:47.375414    1008 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
W1022 19:23:57.407190    1008 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
W1022 19:24:07.439656    1008 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
W1022 19:24:17.473554    1008 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
W1022 19:24:27.502979    1008 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
W1022 19:24:37.546508    1008 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
W1022 19:24:47.578978    1008 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
W1022 19:24:57.625303    1008 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
W1022 19:25:07.662249    1008 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
W1022 19:25:17.702337    1008 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
W1022 19:25:27.738343    1008 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
W1022 19:25:37.771064    1008 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
W1022 19:25:47.802733    1008 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
W1022 19:25:57.835084    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:26:13.560998    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:26:27.354323    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:26:41.211344    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:26:54.752024    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:27:08.595230    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:27:22.276890    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:27:35.862098    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:27:49.756948    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:28:03.407634    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:28:17.003218    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:28:30.679132    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:28:44.675930    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:28:58.361714    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:29:12.003256    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:29:25.811272    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:29:39.464779    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:29:53.365400    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:30:07.886041    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:30:21.883253    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:30:35.584676    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:30:49.368039    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:31:03.377055    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:31:17.055968    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:31:30.643198    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:31:44.313259    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:31:57.974965    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:32:11.588665    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:32:25.300544    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:32:38.918550    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:32:52.488800    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:33:06.180815    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:33:19.908734    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:33:33.530842    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:33:47.440537    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:34:01.921161    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:34:15.568484    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:34:29.447215    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:34:43.342750    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:34:57.002766    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:35:10.920854    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:35:24.540138    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:35:38.216586    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:35:51.866984    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:36:05.577352    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:36:19.293870    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:36:33.293798    1008 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-01809c902525dd5ba				machine "i-01809c902525dd5ba" has not yet joined cluster
Machine	i-021ea61e9519ed82c				machine "i-021ea61e9519ed82c" has not yet joined cluster
Machine	i-04133040363f3caac				machine "i-04133040363f3caac" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-szxnd		system-cluster-critical pod "coredns-6c8944dbdc-szxnd" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8wqz2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8wqz2" is pending

Validation Failed
W1022 19:36:46.982625    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
2021/10/22 19:36:56 process.go:155: Step '/tmp/kops3395341141/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m' finished in 15m11.873262187s
2021/10/22 19:36:56 process.go:153: Running: kubectl -n kube-system get pods -ojson
2021/10/22 19:36:56 process.go:153: Running: /tmp/kops3395341141/kops toolbox dump --name e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io -ojson
I1022 19:36:57.009625    1021 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
2021/10/22 19:36:59 process.go:155: Step 'kubectl -n kube-system get pods -ojson' finished in 2.38314183s
2021/10/22 19:36:59 process.go:153: Running: kubectl -n kube-system logs --all-containers coredns-6c8944dbdc-szxnd
... skipping 40 lines ...
2021/10/22 19:37:24 dump.go:413: Running SSH command: sudo cat /var/log/etcd.log
2021/10/22 19:37:24 dump.go:413: Running SSH command: sudo cat /var/log/etcd-events.log
2021/10/22 19:37:25 dump.go:413: Running SSH command: sudo cat /var/log/kube-proxy.log
2021/10/22 19:37:25 dump.go:413: Running SSH command: sudo cat /var/log/cloud-init-output.log
2021/10/22 19:37:26 dump.go:129: dumping node not registered in kubernetes: 3.109.208.52
2021/10/22 19:37:26 dump.go:163: Dumping node 3.109.208.52
2021/10/22 19:37:27 dump.go:132: error dumping node 3.109.208.52: could not connect: unable to SSH to "3.109.208.52": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/22 19:37:27 dump.go:129: dumping node not registered in kubernetes: 3.108.249.76
2021/10/22 19:37:27 dump.go:163: Dumping node 3.108.249.76
2021/10/22 19:37:29 dump.go:132: error dumping node 3.108.249.76: could not connect: unable to SSH to "3.108.249.76": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/22 19:37:29 dump.go:129: dumping node not registered in kubernetes: 13.127.85.54
2021/10/22 19:37:29 dump.go:163: Dumping node 13.127.85.54
2021/10/22 19:37:31 dump.go:132: error dumping node 13.127.85.54: could not connect: unable to SSH to "13.127.85.54": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/22 19:37:31 dump.go:129: dumping node not registered in kubernetes: 13.127.188.162
2021/10/22 19:37:31 dump.go:163: Dumping node 13.127.188.162
2021/10/22 19:37:33 dump.go:132: error dumping node 13.127.188.162: could not connect: unable to SSH to "13.127.188.162": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/22 19:37:33 process.go:153: Running: /tmp/kops3395341141/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io
I1022 19:37:33.622169    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/22 19:37:34 process.go:155: Step '/tmp/kops3395341141/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 463.39934ms
2021/10/22 19:37:34 process.go:153: Running: /tmp/kops3395341141/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes
... skipping 230 lines ...
dhcp-options:dopt-0b3c52faaec4e3a5b	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/22 19:39:26 process.go:155: Step '/tmp/kops3395341141/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes' finished in 1m52.473342778s
2021/10/22 19:39:26 process.go:96: Saved XML output to /logs/artifacts/junit_runner.xml.
2021/10/22 19:39:26 main.go:331: Something went wrong: starting e2e cluster: kops validate cluster failed: error during /tmp/kops3395341141/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 ...