This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 5 succeeded
Started2020-08-01 14:44
Elapsed20m1s
Revision
links{u'resultstore': {u'url': u'https://source.cloud.google.com/results/invocations/35a6bc5b-f74d-4ee4-a4c9-ebe1df226fc4/targets/test'}}
resultstorehttps://source.cloud.google.com/results/invocations/35a6bc5b-f74d-4ee4-a4c9-ebe1df226fc4/targets/test
job-versionv1.18.6
revisionv1.18.6

Test Failures


Up 15m35s

kops validate cluster failed: error during /tmp/kops330773354/kops validate cluster e2e-kops-kopeio-centos7-k18.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-kopeio-centos7-k18.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/stable-1.18.txt --env=KOPS_KUBE_RELEASE_URL=https://storage.googleapis.com/kubernetes-release/release --env=KOPS_RUN_TOO_NEW_VERSION=1 --extract=release/stable-1.18 --ginkgo-parallel --kops-args=--networking=kopeio '--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/08/01 14:46:56 process.go:155: Step './get-kube.sh' finished in 1m50.041634228s
2020/08/01 14:46:56 process.go:153: Running: /tmp/kops330773354/kops get clusters e2e-kops-kopeio-centos7-k18.test-cncf-aws.k8s.io

cluster not found "e2e-kops-kopeio-centos7-k18.test-cncf-aws.k8s.io"
2020/08/01 14:46:58 process.go:155: Step '/tmp/kops330773354/kops get clusters e2e-kops-kopeio-centos7-k18.test-cncf-aws.k8s.io' finished in 1.786817951s
2020/08/01 14:46:58 util.go:42: curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2020/08/01 14:46:58 kops.go:505: 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/08/01 14:46:58 util.go:68: curl https://ip.jsb.workers.dev
2020/08/01 14:46:58 kops.go:430: Using external IP for admin access: 104.197.154.8/32
2020/08/01 14:46:58 process.go:153: Running: /tmp/kops330773354/kops create cluster --name e2e-kops-kopeio-centos7-k18.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-southeast-1b --master-size c5.large --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.18.6 --admin-access 104.197.154.8/32 --image 679593333241/CentOS Linux 7 x86_64 HVM EBS ENA 2002_01-b7ee8a69-ee97-4a49-9e68-afaee216db2e-ami-0042af67f8e4dcc20.4 --cloud aws --networking=kopeio --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes
I0801 14:46:58.639880     154 featureflag.go:158] FeatureFlag "SpecOverrideFlag"=true
I0801 14:46:59.194652     154 create_cluster.go:687] Using SSH public key: /workspace/.ssh/kube_aws_rsa.pub
I0801 14:47:01.111624     154 subnets.go:184] Assigned CIDR 172.20.32.0/19 to subnet ap-southeast-1b
... skipping 43 lines ...

2020/08/01 14:47:20 process.go:155: Step '/tmp/kops330773354/kops create cluster --name e2e-kops-kopeio-centos7-k18.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-southeast-1b --master-size c5.large --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.18.6 --admin-access 104.197.154.8/32 --image 679593333241/CentOS Linux 7 x86_64 HVM EBS ENA 2002_01-b7ee8a69-ee97-4a49-9e68-afaee216db2e-ami-0042af67f8e4dcc20.4 --cloud aws --networking=kopeio --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes' finished in 22.503186225s
2020/08/01 14:47:20 process.go:153: Running: /tmp/kops330773354/kops validate cluster e2e-kops-kopeio-centos7-k18.test-cncf-aws.k8s.io --wait 15m
I0801 14:47:21.166897     177 featureflag.go:158] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-kops-kopeio-centos7-k18.test-cncf-aws.k8s.io

W0801 14:47:23.740283     177 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-kopeio-centos7-k18.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0801 14:47:33.838875     177 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-kopeio-centos7-k18.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-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
W0801 14:47:43.908432     177 validate_cluster.go:221] (will retry): cluster not yet healthy
W0801 14:47:53.961232     177 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-kopeio-centos7-k18.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-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
W0801 14:48:04.086704     177 validate_cluster.go:221] (will retry): cluster not yet healthy
W0801 14:48:14.155619     177 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-kopeio-centos7-k18.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-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
W0801 14:48:24.236732     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-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
W0801 14:48:34.316339     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-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
W0801 14:48:44.399771     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-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
W0801 14:48:54.481155     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-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
W0801 14:49:04.581578     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-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
W0801 14:49:14.691619     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-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
W0801 14:49:24.814933     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-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
W0801 14:49:34.887681     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-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
W0801 14:49:44.973073     177 validate_cluster.go:221] (will retry): cluster not yet healthy
W0801 14:49:55.043441     177 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-kopeio-centos7-k18.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-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
W0801 14:50:05.086936     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-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
W0801 14:50:15.136502     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-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
W0801 14:50:25.238761     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-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
W0801 14:50:35.283992     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-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
W0801 14:50:45.358408     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-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
W0801 14:50:55.472300     177 validate_cluster.go:221] (will retry): cluster not yet healthy
W0801 14:51:05.542624     177 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-kopeio-centos7-k18.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-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
W0801 14:51:15.619978     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-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
W0801 14:51:25.726898     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-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
W0801 14:51:35.820016     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-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
W0801 14:51:45.910861     177 validate_cluster.go:221] (will retry): cluster not yet healthy
W0801 14:51:55.984450     177 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-kopeio-centos7-k18.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-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
W0801 14:52:06.038940     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-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
W0801 14:52:16.107408     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-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
W0801 14:52:26.191260     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-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
W0801 14:52:36.267345     177 validate_cluster.go:221] (will retry): cluster not yet healthy
W0801 14:53:16.371202     177 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api.e2e-kops-kopeio-centos7-k18.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-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

NODE STATUS
... skipping 4 lines ...

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0303bdc1b98e308ed	machine "i-0303bdc1b98e308ed" has not yet joined cluster
Machine	i-09decd17c312ce5fe	machine "i-09decd17c312ce5fe" has not yet joined cluster

Validation Failed
W0801 14:53:30.568040     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 5 lines ...

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0303bdc1b98e308ed	machine "i-0303bdc1b98e308ed" has not yet joined cluster
Machine	i-09decd17c312ce5fe	machine "i-09decd17c312ce5fe" has not yet joined cluster

Validation Failed
W0801 14:53:42.804369     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 6 lines ...
VALIDATION ERRORS
KIND	NAME									MESSAGE
Machine	i-0303bdc1b98e308ed							machine "i-0303bdc1b98e308ed" has not yet joined cluster
Machine	i-09decd17c312ce5fe							machine "i-09decd17c312ce5fe" has not yet joined cluster
Pod	kube-system/kube-proxy-ip-172-20-59-184.ap-southeast-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-59-184.ap-southeast-1.compute.internal" is pending

Validation Failed
W0801 14:53:55.228817     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 5 lines ...

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0303bdc1b98e308ed	machine "i-0303bdc1b98e308ed" has not yet joined cluster
Machine	i-09decd17c312ce5fe	machine "i-09decd17c312ce5fe" has not yet joined cluster

Validation Failed
W0801 14:54:07.617975     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 5 lines ...

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0303bdc1b98e308ed	machine "i-0303bdc1b98e308ed" has not yet joined cluster
Machine	i-09decd17c312ce5fe	machine "i-09decd17c312ce5fe" has not yet joined cluster

Validation Failed
W0801 14:54:20.024156     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 5 lines ...

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0303bdc1b98e308ed	machine "i-0303bdc1b98e308ed" has not yet joined cluster
Machine	i-09decd17c312ce5fe	machine "i-09decd17c312ce5fe" has not yet joined cluster

Validation Failed
W0801 14:54:32.392454     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 5 lines ...

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0303bdc1b98e308ed	machine "i-0303bdc1b98e308ed" has not yet joined cluster
Machine	i-09decd17c312ce5fe	machine "i-09decd17c312ce5fe" has not yet joined cluster

Validation Failed
W0801 14:54:44.752438     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 5 lines ...

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0303bdc1b98e308ed	machine "i-0303bdc1b98e308ed" has not yet joined cluster
Machine	i-09decd17c312ce5fe	machine "i-09decd17c312ce5fe" has not yet joined cluster

Validation Failed
W0801 14:54:57.085324     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 5 lines ...

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0303bdc1b98e308ed	machine "i-0303bdc1b98e308ed" has not yet joined cluster
Machine	i-09decd17c312ce5fe	machine "i-09decd17c312ce5fe" has not yet joined cluster

Validation Failed
W0801 14:55:09.458375     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 5 lines ...

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0303bdc1b98e308ed	machine "i-0303bdc1b98e308ed" has not yet joined cluster
Machine	i-09decd17c312ce5fe	machine "i-09decd17c312ce5fe" has not yet joined cluster

Validation Failed
W0801 14:55:21.980223     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 5 lines ...

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0303bdc1b98e308ed	machine "i-0303bdc1b98e308ed" has not yet joined cluster
Machine	i-09decd17c312ce5fe	machine "i-09decd17c312ce5fe" has not yet joined cluster

Validation Failed
W0801 14:55:34.325669     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 5 lines ...

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0303bdc1b98e308ed	machine "i-0303bdc1b98e308ed" has not yet joined cluster
Machine	i-09decd17c312ce5fe	machine "i-09decd17c312ce5fe" has not yet joined cluster

Validation Failed
W0801 14:55:46.775058     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 5 lines ...

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0303bdc1b98e308ed	machine "i-0303bdc1b98e308ed" has not yet joined cluster
Machine	i-09decd17c312ce5fe	machine "i-09decd17c312ce5fe" has not yet joined cluster

Validation Failed
W0801 14:55:59.093566     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 5 lines ...

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0303bdc1b98e308ed	machine "i-0303bdc1b98e308ed" has not yet joined cluster
Machine	i-09decd17c312ce5fe	machine "i-09decd17c312ce5fe" has not yet joined cluster

Validation Failed
W0801 14:56:11.444996     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 5 lines ...

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0303bdc1b98e308ed	machine "i-0303bdc1b98e308ed" has not yet joined cluster
Machine	i-09decd17c312ce5fe	machine "i-09decd17c312ce5fe" has not yet joined cluster

Validation Failed
W0801 14:56:23.779560     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 5 lines ...

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0303bdc1b98e308ed	machine "i-0303bdc1b98e308ed" has not yet joined cluster
Machine	i-09decd17c312ce5fe	machine "i-09decd17c312ce5fe" has not yet joined cluster

Validation Failed
W0801 14:56:36.156223     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 5 lines ...

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0303bdc1b98e308ed	machine "i-0303bdc1b98e308ed" has not yet joined cluster
Machine	i-09decd17c312ce5fe	machine "i-09decd17c312ce5fe" has not yet joined cluster

Validation Failed
W0801 14:56:48.409046     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 5 lines ...

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0303bdc1b98e308ed	machine "i-0303bdc1b98e308ed" has not yet joined cluster
Machine	i-09decd17c312ce5fe	machine "i-09decd17c312ce5fe" has not yet joined cluster

Validation Failed
W0801 14:57:00.715411     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 5 lines ...

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0303bdc1b98e308ed	machine "i-0303bdc1b98e308ed" has not yet joined cluster
Machine	i-09decd17c312ce5fe	machine "i-09decd17c312ce5fe" has not yet joined cluster

Validation Failed
W0801 14:57:13.029055     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 5 lines ...

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0303bdc1b98e308ed	machine "i-0303bdc1b98e308ed" has not yet joined cluster
Machine	i-09decd17c312ce5fe	machine "i-09decd17c312ce5fe" has not yet joined cluster

Validation Failed
W0801 14:57:26.046757     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 5 lines ...

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0303bdc1b98e308ed	machine "i-0303bdc1b98e308ed" has not yet joined cluster
Machine	i-09decd17c312ce5fe	machine "i-09decd17c312ce5fe" has not yet joined cluster

Validation Failed
W0801 14:57:38.428549     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 5 lines ...

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0303bdc1b98e308ed	machine "i-0303bdc1b98e308ed" has not yet joined cluster
Machine	i-09decd17c312ce5fe	machine "i-09decd17c312ce5fe" has not yet joined cluster

Validation Failed
W0801 14:57:50.757045     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 5 lines ...

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0303bdc1b98e308ed	machine "i-0303bdc1b98e308ed" has not yet joined cluster
Machine	i-09decd17c312ce5fe	machine "i-09decd17c312ce5fe" has not yet joined cluster

Validation Failed
W0801 14:58:03.196979     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 5 lines ...

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0303bdc1b98e308ed	machine "i-0303bdc1b98e308ed" has not yet joined cluster
Machine	i-09decd17c312ce5fe	machine "i-09decd17c312ce5fe" has not yet joined cluster

Validation Failed
W0801 14:58:15.645698     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 5 lines ...

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0303bdc1b98e308ed	machine "i-0303bdc1b98e308ed" has not yet joined cluster
Machine	i-09decd17c312ce5fe	machine "i-09decd17c312ce5fe" has not yet joined cluster

Validation Failed
W0801 14:58:27.981018     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 5 lines ...

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0303bdc1b98e308ed	machine "i-0303bdc1b98e308ed" has not yet joined cluster
Machine	i-09decd17c312ce5fe	machine "i-09decd17c312ce5fe" has not yet joined cluster

Validation Failed
W0801 14:58:40.378826     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 5 lines ...

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0303bdc1b98e308ed	machine "i-0303bdc1b98e308ed" has not yet joined cluster
Machine	i-09decd17c312ce5fe	machine "i-09decd17c312ce5fe" has not yet joined cluster

Validation Failed
W0801 14:58:52.686301     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 5 lines ...

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0303bdc1b98e308ed	machine "i-0303bdc1b98e308ed" has not yet joined cluster
Machine	i-09decd17c312ce5fe	machine "i-09decd17c312ce5fe" has not yet joined cluster

Validation Failed
W0801 14:59:05.065931     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 5 lines ...

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0303bdc1b98e308ed	machine "i-0303bdc1b98e308ed" has not yet joined cluster
Machine	i-09decd17c312ce5fe	machine "i-09decd17c312ce5fe" has not yet joined cluster

Validation Failed
W0801 14:59:17.492828     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 5 lines ...

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0303bdc1b98e308ed	machine "i-0303bdc1b98e308ed" has not yet joined cluster
Machine	i-09decd17c312ce5fe	machine "i-09decd17c312ce5fe" has not yet joined cluster

Validation Failed
W0801 14:59:29.824674     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 5 lines ...

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0303bdc1b98e308ed	machine "i-0303bdc1b98e308ed" has not yet joined cluster
Machine	i-09decd17c312ce5fe	machine "i-09decd17c312ce5fe" has not yet joined cluster

Validation Failed
W0801 14:59:42.197170     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 5 lines ...

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0303bdc1b98e308ed	machine "i-0303bdc1b98e308ed" has not yet joined cluster
Machine	i-09decd17c312ce5fe	machine "i-09decd17c312ce5fe" has not yet joined cluster

Validation Failed
W0801 14:59:54.523975     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 5 lines ...

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0303bdc1b98e308ed	machine "i-0303bdc1b98e308ed" has not yet joined cluster
Machine	i-09decd17c312ce5fe	machine "i-09decd17c312ce5fe" has not yet joined cluster

Validation Failed
W0801 15:00:06.900644     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 5 lines ...

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0303bdc1b98e308ed	machine "i-0303bdc1b98e308ed" has not yet joined cluster
Machine	i-09decd17c312ce5fe	machine "i-09decd17c312ce5fe" has not yet joined cluster

Validation Failed
W0801 15:00:19.273690     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 5 lines ...

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0303bdc1b98e308ed	machine "i-0303bdc1b98e308ed" has not yet joined cluster
Machine	i-09decd17c312ce5fe	machine "i-09decd17c312ce5fe" has not yet joined cluster

Validation Failed
W0801 15:00:31.732958     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 5 lines ...

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0303bdc1b98e308ed	machine "i-0303bdc1b98e308ed" has not yet joined cluster
Machine	i-09decd17c312ce5fe	machine "i-09decd17c312ce5fe" has not yet joined cluster

Validation Failed
W0801 15:00:44.057919     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 5 lines ...

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0303bdc1b98e308ed	machine "i-0303bdc1b98e308ed" has not yet joined cluster
Machine	i-09decd17c312ce5fe	machine "i-09decd17c312ce5fe" has not yet joined cluster

Validation Failed
W0801 15:00:56.336728     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 5 lines ...

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0303bdc1b98e308ed	machine "i-0303bdc1b98e308ed" has not yet joined cluster
Machine	i-09decd17c312ce5fe	machine "i-09decd17c312ce5fe" has not yet joined cluster

Validation Failed
W0801 15:01:08.714047     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 5 lines ...

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0303bdc1b98e308ed	machine "i-0303bdc1b98e308ed" has not yet joined cluster
Machine	i-09decd17c312ce5fe	machine "i-09decd17c312ce5fe" has not yet joined cluster

Validation Failed
W0801 15:01:21.733093     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 5 lines ...

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0303bdc1b98e308ed	machine "i-0303bdc1b98e308ed" has not yet joined cluster
Machine	i-09decd17c312ce5fe	machine "i-09decd17c312ce5fe" has not yet joined cluster

Validation Failed
W0801 15:01:34.073512     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 5 lines ...

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0303bdc1b98e308ed	machine "i-0303bdc1b98e308ed" has not yet joined cluster
Machine	i-09decd17c312ce5fe	machine "i-09decd17c312ce5fe" has not yet joined cluster

Validation Failed
W0801 15:01:46.487748     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 5 lines ...

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0303bdc1b98e308ed	machine "i-0303bdc1b98e308ed" has not yet joined cluster
Machine	i-09decd17c312ce5fe	machine "i-09decd17c312ce5fe" has not yet joined cluster

Validation Failed
W0801 15:01:58.829123     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 5 lines ...

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0303bdc1b98e308ed	machine "i-0303bdc1b98e308ed" has not yet joined cluster
Machine	i-09decd17c312ce5fe	machine "i-09decd17c312ce5fe" has not yet joined cluster

Validation Failed
W0801 15:02:11.234703     177 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 5 lines ...

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0303bdc1b98e308ed	machine "i-0303bdc1b98e308ed" has not yet joined cluster
Machine	i-09decd17c312ce5fe	machine "i-09decd17c312ce5fe" has not yet joined cluster

Validation Failed
W0801 15:02:23.615943     177 validate_cluster.go:221] (will retry): cluster not yet healthy

Validation failed: wait time exceeded during validation
2020/08/01 15:02:33 process.go:155: Step '/tmp/kops330773354/kops validate cluster e2e-kops-kopeio-centos7-k18.test-cncf-aws.k8s.io --wait 15m' finished in 15m12.856097641s
2020/08/01 15:02:33 process.go:153: Running: kubectl -n kube-system get pods -ojson -l k8s-app=kops-controller
2020/08/01 15:02:33 process.go:153: Running: /tmp/kops330773354/kops toolbox dump --name e2e-kops-kopeio-centos7-k18.test-cncf-aws.k8s.io -ojson
I0801 15:02:34.021242     188 featureflag.go:158] FeatureFlag "SpecOverrideFlag"=true
2020/08/01 15:02:37 process.go:155: Step 'kubectl -n kube-system get pods -ojson -l k8s-app=kops-controller' finished in 3.772677355s
2020/08/01 15:02:37 process.go:153: Running: kubectl -n kube-system logs --all-containers kops-controller-gwn6k
... skipping 162 lines ...
	internet-gateway:igw-0cda537a9378d9e2b
	volume:vol-08ba804254e4010f8
	subnet:subnet-0a5a30ab018094162
volume:vol-0ec59c0e1eb1d9aa0	still has dependencies, will retry
volume:vol-031aab210913536bc	ok
volume:vol-01669d6662ef570d6	still has dependencies, will retry
I0801 15:04:01.975706     248 errors.go:32] unexpected aws error code: "InvalidVolume.NotFound"
volume:vol-0e3a59bfc4cae9355	ok
volume:vol-012528a54d5315f2d	still has dependencies, will retry
volume:vol-08ba804254e4010f8	ok
volume:vol-0eb1976de3c6f53f2	ok
subnet:subnet-0a5a30ab018094162	still has dependencies, will retry
internet-gateway:igw-0cda537a9378d9e2b	still has dependencies, will retry
... skipping 9 lines ...
	internet-gateway:igw-0cda537a9378d9e2b
	subnet:subnet-0a5a30ab018094162
	route-table:rtb-02b8ad55cd65dcfae
subnet:subnet-0a5a30ab018094162	still has dependencies, will retry
volume:vol-0ec59c0e1eb1d9aa0	still has dependencies, will retry
volume:vol-01669d6662ef570d6	still has dependencies, will retry
I0801 15:04:13.359991     248 errors.go:32] unexpected aws error code: "InvalidVolume.NotFound"
volume:vol-012528a54d5315f2d	ok
internet-gateway:igw-0cda537a9378d9e2b	still has dependencies, will retry
security-group:sg-0d17ea75c798d61a8	still has dependencies, will retry
Not all resources deleted; waiting before reattempting deletion
	route-table:rtb-02b8ad55cd65dcfae
	internet-gateway:igw-0cda537a9378d9e2b
	subnet:subnet-0a5a30ab018094162
	vpc:vpc-00af79c70c2a61163
	security-group:sg-0d17ea75c798d61a8
	volume:vol-0ec59c0e1eb1d9aa0
	volume:vol-01669d6662ef570d6
	dhcp-options:dopt-08417bf76530d4fdc
subnet:subnet-0a5a30ab018094162	still has dependencies, will retry
I0801 15:04:24.332663     248 errors.go:32] unexpected aws error code: "InvalidVolume.NotFound"
volume:vol-0ec59c0e1eb1d9aa0	ok
volume:vol-01669d6662ef570d6	ok
security-group:sg-0d17ea75c798d61a8	still has dependencies, will retry
internet-gateway:igw-0cda537a9378d9e2b	ok
Not all resources deleted; waiting before reattempting deletion
	dhcp-options:dopt-08417bf76530d4fdc
... skipping 8 lines ...
dhcp-options:dopt-08417bf76530d4fdc	ok
Deleted kubectl config for e2e-kops-kopeio-centos7-k18.test-cncf-aws.k8s.io

Deleted cluster: "e2e-kops-kopeio-centos7-k18.test-cncf-aws.k8s.io"
2020/08/01 15:04:43 process.go:155: Step '/tmp/kops330773354/kops delete cluster e2e-kops-kopeio-centos7-k18.test-cncf-aws.k8s.io --yes' finished in 1m16.743147491s
2020/08/01 15:04:43 process.go:96: Saved XML output to /logs/artifacts/junit_runner.xml.
2020/08/01 15:04:43 main.go:312: Something went wrong: starting e2e cluster: kops validate cluster failed: error during /tmp/kops330773354/kops validate cluster e2e-kops-kopeio-centos7-k18.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 ...