This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 5 succeeded
Started2020-10-06 19:30
Elapsed18m55s
Revision
job-versionv1.20.0-alpha.1
revisionv1.20.0-alpha.1

Test Failures


Up 15m38s

kops validate cluster failed: error during /tmp/kops141348565/kops validate cluster e2e-kops-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-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= '--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 146 lines ...
2020/10/06 19:31:29 process.go:155: Step './get-kube.sh' finished in 32.250520943s
2020/10/06 19:31:29 process.go:153: Running: /tmp/kops141348565/kops get clusters e2e-kops-centos7.test-cncf-aws.k8s.io

cluster not found "e2e-kops-centos7.test-cncf-aws.k8s.io"
2020/10/06 19:31:30 process.go:155: Step '/tmp/kops141348565/kops get clusters e2e-kops-centos7.test-cncf-aws.k8s.io' finished in 794.608157ms
2020/10/06 19:31:30 util.go:42: curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2020/10/06 19:31:30 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/10/06 19:31:30 util.go:68: curl https://ip.jsb.workers.dev
2020/10/06 19:31:30 kops.go:439: Using external IP for admin access: 104.154.229.244/32
2020/10/06 19:31:30 process.go:153: Running: /tmp/kops141348565/kops create cluster --name e2e-kops-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.1 --admin-access 104.154.229.244/32 --image 679593333241/CentOS Linux 7 x86_64 HVM EBS ENA 2002_01-b7ee8a69-ee97-4a49-9e68-afaee216db2e-ami-0042af67f8e4dcc20.4 --cloud aws --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes
I1006 19:31:30.867583     155 featureflag.go:167] FeatureFlag "SpecOverrideFlag"=true
I1006 19:31:30.985669     155 create_cluster.go:711] Using SSH public key: /workspace/.ssh/kube_aws_rsa.pub
I1006 19:31:32.703697     155 subnets.go:180] Assigned CIDR 172.20.32.0/19 to subnet ap-south-1b
... skipping 40 lines ...

2020/10/06 19:32:03 process.go:155: Step '/tmp/kops141348565/kops create cluster --name e2e-kops-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.1 --admin-access 104.154.229.244/32 --image 679593333241/CentOS Linux 7 x86_64 HVM EBS ENA 2002_01-b7ee8a69-ee97-4a49-9e68-afaee216db2e-ami-0042af67f8e4dcc20.4 --cloud aws --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes' finished in 32.570592219s
2020/10/06 19:32:03 process.go:153: Running: /tmp/kops141348565/kops validate cluster e2e-kops-centos7.test-cncf-aws.k8s.io --wait 15m
I1006 19:32:03.451984     176 featureflag.go:167] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-kops-centos7.test-cncf-aws.k8s.io

W1006 19:32:05.506251     176 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-centos7.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W1006 19:32:15.585551     176 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-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
W1006 19:32:25.635605     176 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
W1006 19:32:35.697029     176 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
W1006 19:32:45.751078     176 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
W1006 19:32:55.818367     176 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
W1006 19:33:05.869747     176 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
W1006 19:33:15.904920     176 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
W1006 19:33:25.970467     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:33:36.017980     176 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-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
W1006 19:33:46.107842     176 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
W1006 19:33:56.219660     176 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
W1006 19:34:06.268312     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:34:16.320029     176 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-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
W1006 19:34:26.370034     176 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
W1006 19:34:36.466689     176 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
W1006 19:34:46.514969     176 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
W1006 19:34:56.568069     176 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
W1006 19:35:06.629664     176 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
W1006 19:35:16.678471     176 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
W1006 19:35:26.784222     176 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
W1006 19:35:36.843598     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:35:46.940202     176 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-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
W1006 19:35:57.028055     176 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
W1006 19:36:07.073813     176 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
W1006 19:36:17.117697     176 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
W1006 19:36:27.159025     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:36:37.201011     176 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-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
W1006 19:36:47.274361     176 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
W1006 19:36:57.321881     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:37:07.376810     176 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-centos7.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W1006 19:37:21.493690     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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-05a3ecab63cf717b8					machine "i-05a3ecab63cf717b8" has not yet joined cluster
Machine	i-061471bf89d3f927c					machine "i-061471bf89d3f927c" has not yet joined cluster
Machine	i-0a32c8ace6d068020					machine "i-0a32c8ace6d068020" has not yet joined cluster
Pod	kube-system/kube-dns-696cb84c7-vp8pz			system-cluster-critical pod "kube-dns-696cb84c7-vp8pz" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-mgxtx	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-mgxtx" is pending

Validation Failed
W1006 19:37:21.978901     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:37:34.479874     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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-05a3ecab63cf717b8					machine "i-05a3ecab63cf717b8" has not yet joined cluster
Machine	i-061471bf89d3f927c					machine "i-061471bf89d3f927c" has not yet joined cluster
Machine	i-0a32c8ace6d068020					machine "i-0a32c8ace6d068020" has not yet joined cluster
Pod	kube-system/kube-dns-696cb84c7-vp8pz			system-cluster-critical pod "kube-dns-696cb84c7-vp8pz" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-mgxtx	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-mgxtx" is pending

Validation Failed
W1006 19:37:34.720804     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:37:47.195807     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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-05a3ecab63cf717b8					machine "i-05a3ecab63cf717b8" has not yet joined cluster
Machine	i-061471bf89d3f927c					machine "i-061471bf89d3f927c" has not yet joined cluster
Machine	i-0a32c8ace6d068020					machine "i-0a32c8ace6d068020" has not yet joined cluster
Pod	kube-system/kube-dns-696cb84c7-vp8pz			system-cluster-critical pod "kube-dns-696cb84c7-vp8pz" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-mgxtx	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-mgxtx" is pending

Validation Failed
W1006 19:37:47.439433     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:37:59.949112     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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-05a3ecab63cf717b8					machine "i-05a3ecab63cf717b8" has not yet joined cluster
Machine	i-061471bf89d3f927c					machine "i-061471bf89d3f927c" has not yet joined cluster
Machine	i-0a32c8ace6d068020					machine "i-0a32c8ace6d068020" has not yet joined cluster
Pod	kube-system/kube-dns-696cb84c7-vp8pz			system-cluster-critical pod "kube-dns-696cb84c7-vp8pz" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-mgxtx	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-mgxtx" is pending

Validation Failed
W1006 19:38:00.190925     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:38:12.759009     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 13 lines ...
Node	ip-172-20-41-242.ap-south-1.compute.internal				node "ip-172-20-41-242.ap-south-1.compute.internal" is not ready
Pod	kube-system/kube-dns-696cb84c7-vp8pz					system-cluster-critical pod "kube-dns-696cb84c7-vp8pz" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-mgxtx			system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-mgxtx" is pending
Pod	kube-system/kube-proxy-ip-172-20-40-126.ap-south-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-40-126.ap-south-1.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-41-242.ap-south-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-41-242.ap-south-1.compute.internal" is pending

Validation Failed
W1006 19:38:13.001561     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:38:25.553828     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 ...
VALIDATION ERRORS
KIND	NAME					MESSAGE
Machine	i-061471bf89d3f927c			machine "i-061471bf89d3f927c" has not yet joined cluster
Pod	kube-system/kube-dns-696cb84c7-vp8pz	system-cluster-critical pod "kube-dns-696cb84c7-vp8pz" is pending
Pod	kube-system/kube-dns-696cb84c7-ws2k4	system-cluster-critical pod "kube-dns-696cb84c7-ws2k4" is pending

Validation Failed
W1006 19:38:25.801045     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:38:38.492183     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 6 lines ...
ip-172-20-61-67.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-061471bf89d3f927c	machine "i-061471bf89d3f927c" has not yet joined cluster

Validation Failed
W1006 19:38:38.736785     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:38:51.346514     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 6 lines ...
ip-172-20-61-67.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-061471bf89d3f927c	machine "i-061471bf89d3f927c" has not yet joined cluster

Validation Failed
W1006 19:38:51.593993     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:39:04.176969     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 6 lines ...
ip-172-20-61-67.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-061471bf89d3f927c	machine "i-061471bf89d3f927c" has not yet joined cluster

Validation Failed
W1006 19:39:04.420166     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:39:16.936020     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 6 lines ...
ip-172-20-61-67.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-061471bf89d3f927c	machine "i-061471bf89d3f927c" has not yet joined cluster

Validation Failed
W1006 19:39:17.184671     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:39:29.749694     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 6 lines ...
ip-172-20-61-67.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-061471bf89d3f927c	machine "i-061471bf89d3f927c" has not yet joined cluster

Validation Failed
W1006 19:39:29.992277     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:39:42.442097     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 6 lines ...
ip-172-20-61-67.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-061471bf89d3f927c	machine "i-061471bf89d3f927c" has not yet joined cluster

Validation Failed
W1006 19:39:42.684493     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:39:55.226284     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 6 lines ...
ip-172-20-61-67.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-061471bf89d3f927c	machine "i-061471bf89d3f927c" has not yet joined cluster

Validation Failed
W1006 19:39:55.469033     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:40:08.007798     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 6 lines ...
ip-172-20-61-67.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-061471bf89d3f927c	machine "i-061471bf89d3f927c" has not yet joined cluster

Validation Failed
W1006 19:40:08.250447     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:40:20.761641     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 6 lines ...
ip-172-20-61-67.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-061471bf89d3f927c	machine "i-061471bf89d3f927c" has not yet joined cluster

Validation Failed
W1006 19:40:21.007971     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:40:33.520766     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 6 lines ...
ip-172-20-61-67.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-061471bf89d3f927c	machine "i-061471bf89d3f927c" has not yet joined cluster

Validation Failed
W1006 19:40:33.772073     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:40:46.314239     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 6 lines ...
ip-172-20-61-67.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-061471bf89d3f927c	machine "i-061471bf89d3f927c" has not yet joined cluster

Validation Failed
W1006 19:40:46.557171     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:40:59.110596     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 6 lines ...
ip-172-20-61-67.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-061471bf89d3f927c	machine "i-061471bf89d3f927c" has not yet joined cluster

Validation Failed
W1006 19:40:59.353224     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:41:12.801231     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 6 lines ...
ip-172-20-61-67.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-061471bf89d3f927c	machine "i-061471bf89d3f927c" has not yet joined cluster

Validation Failed
W1006 19:41:13.044407     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:41:25.568536     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 6 lines ...
ip-172-20-61-67.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-061471bf89d3f927c	machine "i-061471bf89d3f927c" has not yet joined cluster

Validation Failed
W1006 19:41:25.812560     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:41:38.444385     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 6 lines ...
ip-172-20-61-67.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-061471bf89d3f927c	machine "i-061471bf89d3f927c" has not yet joined cluster

Validation Failed
W1006 19:41:38.686474     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:41:51.280286     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 6 lines ...
ip-172-20-61-67.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-061471bf89d3f927c	machine "i-061471bf89d3f927c" has not yet joined cluster

Validation Failed
W1006 19:41:51.522374     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:42:04.099590     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 6 lines ...
ip-172-20-61-67.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-061471bf89d3f927c	machine "i-061471bf89d3f927c" has not yet joined cluster

Validation Failed
W1006 19:42:04.342262     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:42:16.877305     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 6 lines ...
ip-172-20-61-67.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-061471bf89d3f927c	machine "i-061471bf89d3f927c" has not yet joined cluster

Validation Failed
W1006 19:42:17.121625     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:42:29.681517     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 6 lines ...
ip-172-20-61-67.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-061471bf89d3f927c	machine "i-061471bf89d3f927c" has not yet joined cluster

Validation Failed
W1006 19:42:29.923657     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:42:42.411688     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 6 lines ...
ip-172-20-61-67.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-061471bf89d3f927c	machine "i-061471bf89d3f927c" has not yet joined cluster

Validation Failed
W1006 19:42:42.654321     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:42:55.209296     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 6 lines ...
ip-172-20-61-67.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-061471bf89d3f927c	machine "i-061471bf89d3f927c" has not yet joined cluster

Validation Failed
W1006 19:42:55.452450     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:43:07.998729     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 6 lines ...
ip-172-20-61-67.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-061471bf89d3f927c	machine "i-061471bf89d3f927c" has not yet joined cluster

Validation Failed
W1006 19:43:08.241786     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:43:20.792176     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 6 lines ...
ip-172-20-61-67.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-061471bf89d3f927c	machine "i-061471bf89d3f927c" has not yet joined cluster

Validation Failed
W1006 19:43:21.034389     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:43:33.538699     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 6 lines ...
ip-172-20-61-67.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-061471bf89d3f927c	machine "i-061471bf89d3f927c" has not yet joined cluster

Validation Failed
W1006 19:43:33.783541     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:43:46.364480     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 6 lines ...
ip-172-20-61-67.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-061471bf89d3f927c	machine "i-061471bf89d3f927c" has not yet joined cluster

Validation Failed
W1006 19:43:46.606224     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:43:59.083969     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 6 lines ...
ip-172-20-61-67.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-061471bf89d3f927c	machine "i-061471bf89d3f927c" has not yet joined cluster

Validation Failed
W1006 19:43:59.326685     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:44:11.878163     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 6 lines ...
ip-172-20-61-67.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-061471bf89d3f927c	machine "i-061471bf89d3f927c" has not yet joined cluster

Validation Failed
W1006 19:44:12.120648     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:44:24.700793     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 6 lines ...
ip-172-20-61-67.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-061471bf89d3f927c	machine "i-061471bf89d3f927c" has not yet joined cluster

Validation Failed
W1006 19:44:24.945794     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:44:37.409564     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 6 lines ...
ip-172-20-61-67.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-061471bf89d3f927c	machine "i-061471bf89d3f927c" has not yet joined cluster

Validation Failed
W1006 19:44:37.651768     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:44:50.210609     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 6 lines ...
ip-172-20-61-67.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-061471bf89d3f927c	machine "i-061471bf89d3f927c" has not yet joined cluster

Validation Failed
W1006 19:44:50.456099     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:45:03.808062     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 6 lines ...
ip-172-20-61-67.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-061471bf89d3f927c	machine "i-061471bf89d3f927c" has not yet joined cluster

Validation Failed
W1006 19:45:04.050507     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:45:16.592868     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 6 lines ...
ip-172-20-61-67.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-061471bf89d3f927c	machine "i-061471bf89d3f927c" has not yet joined cluster

Validation Failed
W1006 19:45:16.836365     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:45:29.431993     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 6 lines ...
ip-172-20-61-67.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-061471bf89d3f927c	machine "i-061471bf89d3f927c" has not yet joined cluster

Validation Failed
W1006 19:45:29.674175     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:45:42.307908     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 6 lines ...
ip-172-20-61-67.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-061471bf89d3f927c	machine "i-061471bf89d3f927c" has not yet joined cluster

Validation Failed
W1006 19:45:42.550466     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:45:55.038804     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 6 lines ...
ip-172-20-61-67.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-061471bf89d3f927c	machine "i-061471bf89d3f927c" has not yet joined cluster

Validation Failed
W1006 19:45:55.281707     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:46:07.777665     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 6 lines ...
ip-172-20-61-67.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-061471bf89d3f927c	machine "i-061471bf89d3f927c" has not yet joined cluster

Validation Failed
W1006 19:46:08.019849     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:46:20.492576     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 6 lines ...
ip-172-20-61-67.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-061471bf89d3f927c	machine "i-061471bf89d3f927c" has not yet joined cluster

Validation Failed
W1006 19:46:20.737608     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:46:33.202174     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 6 lines ...
ip-172-20-61-67.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-061471bf89d3f927c	machine "i-061471bf89d3f927c" has not yet joined cluster

Validation Failed
W1006 19:46:33.444935     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:46:45.928322     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 6 lines ...
ip-172-20-61-67.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-061471bf89d3f927c	machine "i-061471bf89d3f927c" has not yet joined cluster

Validation Failed
W1006 19:46:46.173844     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1006 19:46:58.658552     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
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 6 lines ...
ip-172-20-61-67.ap-south-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-061471bf89d3f927c	machine "i-061471bf89d3f927c" has not yet joined cluster

Validation Failed
W1006 19:46:58.901060     176 validate_cluster.go:221] (will retry): cluster not yet healthy

Validation failed: wait time exceeded during validation
2020/10/06 19:47:08 process.go:155: Step '/tmp/kops141348565/kops validate cluster e2e-kops-centos7.test-cncf-aws.k8s.io --wait 15m' finished in 15m5.568241508s
2020/10/06 19:47:08 process.go:153: Running: kubectl -n kube-system get pods -ojson -l k8s-app=kops-controller
2020/10/06 19:47:08 process.go:153: Running: /tmp/kops141348565/kops toolbox dump --name e2e-kops-centos7.test-cncf-aws.k8s.io -ojson
I1006 19:47:09.008007     188 featureflag.go:167] FeatureFlag "SpecOverrideFlag"=true
2020/10/06 19:47:11 process.go:155: Step 'kubectl -n kube-system get pods -ojson -l k8s-app=kops-controller' finished in 2.13293847s
2020/10/06 19:47:11 process.go:153: Running: kubectl -n kube-system logs --all-containers kops-controller-qk9cd
... skipping 142 lines ...
volume:vol-0c5680057aaa8a60e	still has dependencies, will retry
volume:vol-08af867fc3c873160	still has dependencies, will retry
volume:vol-0224d34b14d7f39f4	still has dependencies, will retry
volume:vol-0549a6e49498a30ec	still has dependencies, will retry
volume:vol-0f6eecf34cdaaf36b	still has dependencies, will retry
volume:vol-0cd19e3520a704535	still has dependencies, will retry
I1006 19:48:36.786071     239 errors.go:32] unexpected aws error code: "InvalidVolume.NotFound"
volume:vol-0a1cfd78f7e45897d	ok
subnet:subnet-0a94d283b75b8fc92	still has dependencies, will retry
security-group:sg-005368ca1ce1fe180	still has dependencies, will retry
internet-gateway:igw-0015dab25b11ae99d	still has dependencies, will retry
security-group:sg-0de24c64ec5a36fb3	still has dependencies, will retry
Not all resources deleted; waiting before reattempting deletion
... skipping 36 lines ...
	security-group:sg-005368ca1ce1fe180
volume:vol-0224d34b14d7f39f4	still has dependencies, will retry
volume:vol-0c5680057aaa8a60e	still has dependencies, will retry
volume:vol-0f6eecf34cdaaf36b	still has dependencies, will retry
volume:vol-08af867fc3c873160	still has dependencies, will retry
volume:vol-0549a6e49498a30ec	still has dependencies, will retry
I1006 19:48:59.812571     239 errors.go:32] unexpected aws error code: "InvalidVolume.NotFound"
volume:vol-0cd19e3520a704535	ok
subnet:subnet-0a94d283b75b8fc92	still has dependencies, will retry
internet-gateway:igw-0015dab25b11ae99d	still has dependencies, will retry
security-group:sg-005368ca1ce1fe180	still has dependencies, will retry
security-group:sg-0de24c64ec5a36fb3	still has dependencies, will retry
Not all resources deleted; waiting before reattempting deletion
... skipping 27 lines ...
	volume:vol-0549a6e49498a30ec
	vpc:vpc-0cb73940cd1882d78
	volume:vol-0224d34b14d7f39f4
	security-group:sg-0de24c64ec5a36fb3
	subnet:subnet-0a94d283b75b8fc92
	dhcp-options:dopt-0e72842fa247e566a
I1006 19:49:22.042741     239 errors.go:32] unexpected aws error code: "InvalidVolume.NotFound"
volume:vol-08af867fc3c873160	ok
volume:vol-0224d34b14d7f39f4	still has dependencies, will retry
volume:vol-0f6eecf34cdaaf36b	still has dependencies, will retry
volume:vol-0549a6e49498a30ec	still has dependencies, will retry
subnet:subnet-0a94d283b75b8fc92	still has dependencies, will retry
internet-gateway:igw-0015dab25b11ae99d	still has dependencies, will retry
... skipping 6 lines ...
	subnet:subnet-0a94d283b75b8fc92
	dhcp-options:dopt-0e72842fa247e566a
	internet-gateway:igw-0015dab25b11ae99d
	security-group:sg-005368ca1ce1fe180
	volume:vol-0f6eecf34cdaaf36b
	route-table:rtb-09ed35b639ff9f440
I1006 19:49:33.565486     239 errors.go:32] unexpected aws error code: "InvalidVolume.NotFound"
volume:vol-0224d34b14d7f39f4	ok
volume:vol-0f6eecf34cdaaf36b	ok
volume:vol-0549a6e49498a30ec	ok
subnet:subnet-0a94d283b75b8fc92	ok
security-group:sg-005368ca1ce1fe180	ok
internet-gateway:igw-0015dab25b11ae99d	ok
... skipping 2 lines ...
dhcp-options:dopt-0e72842fa247e566a	ok
Deleted kubectl config for e2e-kops-centos7.test-cncf-aws.k8s.io

Deleted cluster: "e2e-kops-centos7.test-cncf-aws.k8s.io"
2020/10/06 19:49:42 process.go:155: Step '/tmp/kops141348565/kops delete cluster e2e-kops-centos7.test-cncf-aws.k8s.io --yes' finished in 1m31.853244903s
2020/10/06 19:49:42 process.go:96: Saved XML output to /logs/artifacts/junit_runner.xml.
2020/10/06 19:49:42 main.go:312: Something went wrong: starting e2e cluster: kops validate cluster failed: error during /tmp/kops141348565/kops validate cluster e2e-kops-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 ...