This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 5 succeeded
Started2020-09-18 18:32
Elapsed19m2s
Revision
job-versionv1.20.0-alpha.0
revisionv1.20.0-alpha.0

Test Failures


Up 15m45s

kops validate cluster failed: error during /tmp/kops640417643/kops validate cluster e2e-kops-flanl-centos7.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
+ /workspace/scenarios/kubernetes_e2e.py --cluster=e2e-kops-flanl-centos7.test-cncf-aws.k8s.io --deployment=kops --kops-ssh-user=centos --env=KUBE_SSH_USER=centos --env=KOPS_DEPLOY_LATEST_URL=https://storage.googleapis.com/kubernetes-release/release/latest.txt --env=KOPS_KUBE_RELEASE_URL=https://storage.googleapis.com/kubernetes-release/release --env=KOPS_RUN_TOO_NEW_VERSION=1 --extract=release/latest --ginkgo-parallel --kops-args=--networking=flannel '--kops-image=679593333241/CentOS Linux 7 x86_64 HVM EBS ENA 2002_01-b7ee8a69-ee97-4a49-9e68-afaee216db2e-ami-0042af67f8e4dcc20.4' --kops-priority-path=/workspace/kubernetes/platforms/linux/amd64 --kops-version=https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt --provider=aws '--test_args=--ginkgo.skip=\[Slow\]|\[Serial\]|\[Disruptive\]|\[Flaky\]|\[Feature:.+\]|\[HPA\]|Dashboard|Services.*functioning.*NodePort|Services.*rejected.*endpoints|Services.*affinity' --timeout=60m
starts with local mode
Environment:
ARTIFACTS=/logs/artifacts
AWS_DEFAULT_PROFILE=default
AWS_PROFILE=default
... skipping 148 lines ...
2020/09/18 18:33:25 process.go:155: Step './get-kube.sh' finished in 33.356350416s
2020/09/18 18:33:25 process.go:153: Running: /tmp/kops640417643/kops get clusters e2e-kops-flanl-centos7.test-cncf-aws.k8s.io

cluster not found "e2e-kops-flanl-centos7.test-cncf-aws.k8s.io"
2020/09/18 18:33:26 process.go:155: Step '/tmp/kops640417643/kops get clusters e2e-kops-flanl-centos7.test-cncf-aws.k8s.io' finished in 712.679647ms
2020/09/18 18:33:26 util.go:42: curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2020/09/18 18:33:26 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
2020/09/18 18:33:26 util.go:68: curl https://ip.jsb.workers.dev
2020/09/18 18:33:26 kops.go:439: Using external IP for admin access: 34.71.37.131/32
2020/09/18 18:33:26 process.go:153: Running: /tmp/kops640417643/kops create cluster --name e2e-kops-flanl-centos7.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/kubernetes-release/release/v1.20.0-alpha.0 --admin-access 34.71.37.131/32 --image 679593333241/CentOS Linux 7 x86_64 HVM EBS ENA 2002_01-b7ee8a69-ee97-4a49-9e68-afaee216db2e-ami-0042af67f8e4dcc20.4 --cloud aws --networking=flannel --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes
I0918 18:33:26.603894     156 featureflag.go:167] FeatureFlag "SpecOverrideFlag"=true
I0918 18:33:26.746488     156 create_cluster.go:706] Using SSH public key: /workspace/.ssh/kube_aws_rsa.pub
I0918 18:33:28.438193     156 subnets.go:184] Assigned CIDR 172.20.32.0/19 to subnet ap-south-1b
... skipping 40 lines ...

2020/09/18 18:33:59 process.go:155: Step '/tmp/kops640417643/kops create cluster --name e2e-kops-flanl-centos7.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/kubernetes-release/release/v1.20.0-alpha.0 --admin-access 34.71.37.131/32 --image 679593333241/CentOS Linux 7 x86_64 HVM EBS ENA 2002_01-b7ee8a69-ee97-4a49-9e68-afaee216db2e-ami-0042af67f8e4dcc20.4 --cloud aws --networking=flannel --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes' finished in 32.85450822s
2020/09/18 18:33:59 process.go:153: Running: /tmp/kops640417643/kops validate cluster e2e-kops-flanl-centos7.test-cncf-aws.k8s.io --wait 15m
I0918 18:33:59.452912     177 featureflag.go:167] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-kops-flanl-centos7.test-cncf-aws.k8s.io

W0918 18:34:01.476578     177 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-flanl-centos7.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0918 18:34:11.533123     177 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-flanl-centos7.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
W0918 18:34:21.580261     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:34:31.629526     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:34:41.705382     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:34:51.769620     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:35:01.829814     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:35:11.869635     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:35:21.911895     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:35:31.963580     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:35:42.003782     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:35:52.062276     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:36:02.113510     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:36:12.150174     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:36:22.189416     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:36:32.227586     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:36:42.267640     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:36:52.304177     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:37:02.355468     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:37:12.413292     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:37:22.465396     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:37:32.540278     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:37:42.581191     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:37:52.633508     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:38:02.681641     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:38:12.753085     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:38:22.810183     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:38:32.856893     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:38:42.898554     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:38:52.945235     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:39:03.000505     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:39:13.040478     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:39:23.073968     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:39:33.133971     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:39:43.173744     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:39:53.227284     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:40:03.287957     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:40:13.343710     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:40:23.386694     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:40:33.427194     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:40:43.484263     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:40:53.529975     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:41:03.568067     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:41:13.629620     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:41:23.673710     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:41:33.713473     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:41:43.782487     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:41:53.864365     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:42:03.979819     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:42:14.042136     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:42:24.103044     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:42:34.145433     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:42:44.180049     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:42:54.235695     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:43:04.296063     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:43:14.346584     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:43:24.400429     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:43:34.438208     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:43:44.499700     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:43:54.563478     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:44:04.614772     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:44:14.659341     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:44:24.708109     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:44:34.751350     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:44:44.811813     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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
W0918 18:44:54.854316     177 validate_cluster.go:221] (will retry): cluster not yet healthy
W0918 18:45:34.894224     177 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api.e2e-kops-flanl-centos7.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-0872b7666027821cd					machine "i-0872b7666027821cd" has not yet joined cluster
Machine	i-08e9000ef8d35d030					machine "i-08e9000ef8d35d030" has not yet joined cluster
Machine	i-0a1fd43d6ad78d275					machine "i-0a1fd43d6ad78d275" has not yet joined cluster
Pod	kube-system/kube-dns-77cbd9bf6f-xc9ns			system-cluster-critical pod "kube-dns-77cbd9bf6f-xc9ns" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-2hbvv	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-2hbvv" is pending

Validation Failed
W0918 18:45:49.661674     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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-0872b7666027821cd					machine "i-0872b7666027821cd" has not yet joined cluster
Machine	i-08e9000ef8d35d030					machine "i-08e9000ef8d35d030" has not yet joined cluster
Machine	i-0a1fd43d6ad78d275					machine "i-0a1fd43d6ad78d275" has not yet joined cluster
Pod	kube-system/kube-dns-77cbd9bf6f-xc9ns			system-cluster-critical pod "kube-dns-77cbd9bf6f-xc9ns" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-2hbvv	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-2hbvv" is pending

Validation Failed
W0918 18:46:02.614900     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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-0872b7666027821cd					machine "i-0872b7666027821cd" has not yet joined cluster
Machine	i-08e9000ef8d35d030					machine "i-08e9000ef8d35d030" has not yet joined cluster
Machine	i-0a1fd43d6ad78d275					machine "i-0a1fd43d6ad78d275" has not yet joined cluster
Pod	kube-system/kube-dns-77cbd9bf6f-xc9ns			system-cluster-critical pod "kube-dns-77cbd9bf6f-xc9ns" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-2hbvv	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-2hbvv" is pending

Validation Failed
W0918 18:46:15.515328     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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-0872b7666027821cd					machine "i-0872b7666027821cd" has not yet joined cluster
Machine	i-08e9000ef8d35d030					machine "i-08e9000ef8d35d030" has not yet joined cluster
Machine	i-0a1fd43d6ad78d275					machine "i-0a1fd43d6ad78d275" has not yet joined cluster
Pod	kube-system/kube-dns-77cbd9bf6f-xc9ns			system-cluster-critical pod "kube-dns-77cbd9bf6f-xc9ns" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-2hbvv	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-2hbvv" is pending

Validation Failed
W0918 18:46:28.414047     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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-0872b7666027821cd					machine "i-0872b7666027821cd" has not yet joined cluster
Machine	i-08e9000ef8d35d030					machine "i-08e9000ef8d35d030" has not yet joined cluster
Machine	i-0a1fd43d6ad78d275					machine "i-0a1fd43d6ad78d275" has not yet joined cluster
Pod	kube-system/kube-dns-77cbd9bf6f-xc9ns			system-cluster-critical pod "kube-dns-77cbd9bf6f-xc9ns" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-2hbvv	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-2hbvv" is pending

Validation Failed
W0918 18:46:41.175981     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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-0872b7666027821cd					machine "i-0872b7666027821cd" has not yet joined cluster
Machine	i-08e9000ef8d35d030					machine "i-08e9000ef8d35d030" has not yet joined cluster
Machine	i-0a1fd43d6ad78d275					machine "i-0a1fd43d6ad78d275" has not yet joined cluster
Pod	kube-system/kube-dns-77cbd9bf6f-xc9ns			system-cluster-critical pod "kube-dns-77cbd9bf6f-xc9ns" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-2hbvv	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-2hbvv" is pending

Validation Failed
W0918 18:46:54.009857     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 10 lines ...
Node	ip-172-20-38-221.ap-south-1.compute.internal				node "ip-172-20-38-221.ap-south-1.compute.internal" is not ready
Pod	kube-system/kube-dns-77cbd9bf6f-xc9ns					system-cluster-critical pod "kube-dns-77cbd9bf6f-xc9ns" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-2hbvv			system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-2hbvv" is pending
Pod	kube-system/kube-flannel-ds-w8qvm					system-node-critical pod "kube-flannel-ds-w8qvm" is pending
Pod	kube-system/kube-proxy-ip-172-20-38-221.ap-south-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-38-221.ap-south-1.compute.internal" is pending

Validation Failed
W0918 18:47:06.857926     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 10 lines ...
Node	ip-172-20-38-221.ap-south-1.compute.internal		node "ip-172-20-38-221.ap-south-1.compute.internal" is not ready
Node	ip-172-20-53-215.ap-south-1.compute.internal		node "ip-172-20-53-215.ap-south-1.compute.internal" is not ready
Pod	kube-system/kube-dns-77cbd9bf6f-xc9ns			system-cluster-critical pod "kube-dns-77cbd9bf6f-xc9ns" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-2hbvv	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-2hbvv" is pending
Pod	kube-system/kube-flannel-ds-klwf5			system-node-critical pod "kube-flannel-ds-klwf5" is pending

Validation Failed
W0918 18:47:19.583602     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1b	Master	c5.large	1	1	ap-south-1b
nodes-ap-south-1b	Node	t3.medium	4	4	ap-south-1b

... skipping 8 lines ...
Machine	i-08e9000ef8d35d030				machine "i-08e9000ef8d35d030" has not yet joined cluster
Machine	i-0a1fd43d6ad78d275				machine "i-0a1fd43d6ad78d275" has not yet joined cluster
Node	ip-172-20-53-215.ap-south-1.compute.internal	node "ip-172-20-53-215.ap-south-1.compute.internal" is not ready
Pod	kube-system/kube-dns-77cbd9bf6f-f7cqh		system-cluster-critical pod "kube-dns-77cbd9bf6f-f7cqh" is pending
Pod	kube-system/kube-dns-77cbd9bf6f-xc9ns		system-cluster-critical pod "kube-dns-77cbd9bf6f-xc9ns" is pending

Validation Failed
W0918 18:47:32.421157     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1b	Master	c5.large	1	1	ap-south-1b
nodes-ap-south-1b	Node	t3.medium	4	4	ap-south-1b

... skipping 8 lines ...
KIND	NAME						MESSAGE
Machine	i-0a1fd43d6ad78d275				machine "i-0a1fd43d6ad78d275" has not yet joined cluster
Node	ip-172-20-39-211.ap-south-1.compute.internal	node "ip-172-20-39-211.ap-south-1.compute.internal" is not ready
Pod	kube-system/kube-dns-77cbd9bf6f-xc9ns		system-cluster-critical pod "kube-dns-77cbd9bf6f-xc9ns" is not ready (kubedns)
Pod	kube-system/kube-flannel-ds-mf87q		system-node-critical pod "kube-flannel-ds-mf87q" is pending

Validation Failed
W0918 18:47:45.191637     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 5 lines ...
ip-172-20-55-98.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a1fd43d6ad78d275	machine "i-0a1fd43d6ad78d275" has not yet joined cluster

Validation Failed
W0918 18:47:57.961116     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 5 lines ...
ip-172-20-55-98.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a1fd43d6ad78d275	machine "i-0a1fd43d6ad78d275" has not yet joined cluster

Validation Failed
W0918 18:48:10.782041     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 5 lines ...
ip-172-20-55-98.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a1fd43d6ad78d275	machine "i-0a1fd43d6ad78d275" has not yet joined cluster

Validation Failed
W0918 18:48:23.628659     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 5 lines ...
ip-172-20-55-98.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a1fd43d6ad78d275	machine "i-0a1fd43d6ad78d275" has not yet joined cluster

Validation Failed
W0918 18:48:36.678873     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 5 lines ...
ip-172-20-55-98.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a1fd43d6ad78d275	machine "i-0a1fd43d6ad78d275" has not yet joined cluster

Validation Failed
W0918 18:48:49.560037     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 5 lines ...
ip-172-20-55-98.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a1fd43d6ad78d275	machine "i-0a1fd43d6ad78d275" has not yet joined cluster

Validation Failed
W0918 18:49:02.344811     177 validate_cluster.go:221] (will retry): cluster not yet healthy

Validation failed: wait time exceeded during validation
2020/09/18 18:49:12 process.go:155: Step '/tmp/kops640417643/kops validate cluster e2e-kops-flanl-centos7.test-cncf-aws.k8s.io --wait 15m' finished in 15m13.001033505s
2020/09/18 18:49:12 process.go:153: Running: kubectl -n kube-system get pods -ojson -l k8s-app=kops-controller
2020/09/18 18:49:12 process.go:153: Running: /tmp/kops640417643/kops toolbox dump --name e2e-kops-flanl-centos7.test-cncf-aws.k8s.io -ojson
I0918 18:49:12.452764     188 featureflag.go:167] FeatureFlag "SpecOverrideFlag"=true
2020/09/18 18:49:14 process.go:155: Step 'kubectl -n kube-system get pods -ojson -l k8s-app=kops-controller' finished in 2.154911312s
2020/09/18 18:49:14 process.go:153: Running: kubectl -n kube-system logs --all-containers kops-controller-x2zkc
... skipping 215 lines ...
	security-group:sg-04f267c4bb7d1fb8f
	dhcp-options:dopt-06c2322a2bf1b578e
	volume:vol-01df433a10409fa4f
	volume:vol-08b8943736a7862fc
	route-table:rtb-0b9c062f02e62b89d
volume:vol-08b8943736a7862fc	still has dependencies, will retry
I0918 18:51:15.216084     240 errors.go:32] unexpected aws error code: "InvalidVolume.NotFound"
volume:vol-0609816ab7b83fb2c	ok
I0918 18:51:15.219887     240 errors.go:32] unexpected aws error code: "InvalidVolume.NotFound"
volume:vol-04c251d1e6a1ba15d	ok
volume:vol-01df433a10409fa4f	still has dependencies, will retry
volume:vol-047e46dac5c555d64	ok
volume:vol-0aae1431fb21149ed	ok
volume:vol-078437b32410cdcac	ok
subnet:subnet-01dfe0800976cd1fa	still has dependencies, will retry
... skipping 9 lines ...
	route-table:rtb-0b9c062f02e62b89d
	vpc:vpc-02649c8568905ec26
	security-group:sg-0060e8479e10f53e7
	internet-gateway:igw-0d7b72f3c90fa7ff5
subnet:subnet-01dfe0800976cd1fa	still has dependencies, will retry
volume:vol-01df433a10409fa4f	still has dependencies, will retry
I0918 18:51:26.762662     240 errors.go:32] unexpected aws error code: "InvalidVolume.NotFound"
volume:vol-08b8943736a7862fc	ok
security-group:sg-04f267c4bb7d1fb8f	ok
security-group:sg-0060e8479e10f53e7	still has dependencies, will retry
internet-gateway:igw-0d7b72f3c90fa7ff5	ok
Not all resources deleted; waiting before reattempting deletion
	dhcp-options:dopt-06c2322a2bf1b578e
	volume:vol-01df433a10409fa4f
	route-table:rtb-0b9c062f02e62b89d
	vpc:vpc-02649c8568905ec26
	security-group:sg-0060e8479e10f53e7
	subnet:subnet-01dfe0800976cd1fa
subnet:subnet-01dfe0800976cd1fa	ok
I0918 18:51:38.110107     240 errors.go:32] unexpected aws error code: "InvalidVolume.NotFound"
volume:vol-01df433a10409fa4f	ok
security-group:sg-0060e8479e10f53e7	ok
route-table:rtb-0b9c062f02e62b89d	ok
vpc:vpc-02649c8568905ec26	ok
dhcp-options:dopt-06c2322a2bf1b578e	ok
Deleted kubectl config for e2e-kops-flanl-centos7.test-cncf-aws.k8s.io

Deleted cluster: "e2e-kops-flanl-centos7.test-cncf-aws.k8s.io"
2020/09/18 18:51:45 process.go:155: Step '/tmp/kops640417643/kops delete cluster e2e-kops-flanl-centos7.test-cncf-aws.k8s.io --yes' finished in 1m31.198851642s
2020/09/18 18:51:45 process.go:96: Saved XML output to /logs/artifacts/junit_runner.xml.
2020/09/18 18:51:45 main.go:312: Something went wrong: starting e2e cluster: kops validate cluster failed: error during /tmp/kops640417643/kops validate cluster e2e-kops-flanl-centos7.test-cncf-aws.k8s.io --wait 15m: exit status 1
Traceback (most recent call last):
  File "/workspace/scenarios/kubernetes_e2e.py", line 720, in <module>
    main(parse_args())
  File "/workspace/scenarios/kubernetes_e2e.py", line 570, in main
    mode.start(runner_args)
  File "/workspace/scenarios/kubernetes_e2e.py", line 228, in start
... skipping 9 lines ...