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

Test Failures


Up 15m32s

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

Filter through log files | View test history on testgrid


Show 5 Passed Tests

Error lines from build-log.txt

Activated service account credentials for: [pr-kubekins@kubernetes-jenkins-pull.iam.gserviceaccount.com]
fatal: not a git repository (or any of the parent directories): .git
+ /workspace/scenarios/kubernetes_e2e.py --cluster=e2e-kops-flanl-centos7.test-cncf-aws.k8s.io --deployment=kops --kops-ssh-user=centos --env=KUBE_SSH_USER=centos --env=KOPS_DEPLOY_LATEST_URL=https://storage.googleapis.com/kubernetes-release/release/latest.txt --env=KOPS_KUBE_RELEASE_URL=https://storage.googleapis.com/kubernetes-release/release --env=KOPS_RUN_TOO_NEW_VERSION=1 --extract=release/latest --ginkgo-parallel --kops-args=--networking=flannel '--kops-image=679593333241/CentOS Linux 7 x86_64 HVM EBS ENA 2002_01-b7ee8a69-ee97-4a49-9e68-afaee216db2e-ami-0042af67f8e4dcc20.4' --kops-priority-path=/workspace/kubernetes/platforms/linux/amd64 --kops-version=https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt --provider=aws '--test_args=--ginkgo.skip=\[Slow\]|\[Serial\]|\[Disruptive\]|\[Flaky\]|\[Feature:.+\]|\[HPA\]|Dashboard|Services.*functioning.*NodePort|Services.*rejected.*endpoints|Services.*affinity' --timeout=60m
starts with local mode
Environment:
ARTIFACTS=/logs/artifacts
AWS_DEFAULT_PROFILE=default
AWS_PROFILE=default
... skipping 148 lines ...
2020/09/11 18:33:09 process.go:155: Step './get-kube.sh' finished in 26.53062248s
2020/09/11 18:33:09 process.go:153: Running: /tmp/kops217661516/kops get clusters e2e-kops-flanl-centos7.test-cncf-aws.k8s.io

cluster not found "e2e-kops-flanl-centos7.test-cncf-aws.k8s.io"
2020/09/11 18:33:09 process.go:155: Step '/tmp/kops217661516/kops get clusters e2e-kops-flanl-centos7.test-cncf-aws.k8s.io' finished in 740.447345ms
2020/09/11 18:33:09 util.go:42: curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2020/09/11 18:33:09 kops.go:514: failed to get external ip from metadata service: http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip returned 404
2020/09/11 18:33:09 util.go:68: curl https://ip.jsb.workers.dev
2020/09/11 18:33:09 kops.go:439: Using external IP for admin access: 35.223.174.242/32
2020/09/11 18:33:09 process.go:153: Running: /tmp/kops217661516/kops create cluster --name e2e-kops-flanl-centos7.test-cncf-aws.k8s.io --ssh-public-key /workspace/.ssh/kube_aws_rsa.pub --node-count 4 --node-volume-size 48 --master-volume-size 48 --master-count 1 --zones ap-southeast-1a --master-size c5.large --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.20.0-alpha.0 --admin-access 35.223.174.242/32 --image 679593333241/CentOS Linux 7 x86_64 HVM EBS ENA 2002_01-b7ee8a69-ee97-4a49-9e68-afaee216db2e-ami-0042af67f8e4dcc20.4 --cloud aws --networking=flannel --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes
I0911 18:33:09.948066     154 featureflag.go:167] FeatureFlag "SpecOverrideFlag"=true
I0911 18:33:10.042809     154 create_cluster.go:706] Using SSH public key: /workspace/.ssh/kube_aws_rsa.pub
I0911 18:33:11.599719     154 subnets.go:184] Assigned CIDR 172.20.32.0/19 to subnet ap-southeast-1a
... skipping 40 lines ...

2020/09/11 18:33:40 process.go:155: Step '/tmp/kops217661516/kops create cluster --name e2e-kops-flanl-centos7.test-cncf-aws.k8s.io --ssh-public-key /workspace/.ssh/kube_aws_rsa.pub --node-count 4 --node-volume-size 48 --master-volume-size 48 --master-count 1 --zones ap-southeast-1a --master-size c5.large --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.20.0-alpha.0 --admin-access 35.223.174.242/32 --image 679593333241/CentOS Linux 7 x86_64 HVM EBS ENA 2002_01-b7ee8a69-ee97-4a49-9e68-afaee216db2e-ami-0042af67f8e4dcc20.4 --cloud aws --networking=flannel --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes' finished in 30.14626631s
2020/09/11 18:33:40 process.go:153: Running: /tmp/kops217661516/kops validate cluster e2e-kops-flanl-centos7.test-cncf-aws.k8s.io --wait 15m
I0911 18:33:40.097652     173 featureflag.go:167] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-kops-flanl-centos7.test-cncf-aws.k8s.io

W0911 18:33:42.040821     173 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-flanl-centos7.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0911 18:33:52.125474     173 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-flanl-centos7.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0911 18:34:02.171196     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0911 18:34:12.235649     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0911 18:34:22.274737     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0911 18:34:32.328688     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0911 18:34:42.389033     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0911 18:34:52.436682     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0911 18:35:02.517666     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0911 18:35:12.551255     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0911 18:35:22.601322     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0911 18:35:32.645642     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0911 18:35:42.683859     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0911 18:35:52.737613     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0911 18:36:02.821866     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0911 18:36:12.864394     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0911 18:36:22.930878     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0911 18:36:32.977008     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0911 18:36:43.017377     173 validate_cluster.go:221] (will retry): cluster not yet healthy
W0911 18:36:53.059142     173 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-flanl-centos7.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0911 18:37:03.113879     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0911 18:37:13.148020     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0911 18:37:23.205101     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0911 18:37:33.272496     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0911 18:37:43.314778     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0911 18:37:53.366377     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0911 18:38:03.409080     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0911 18:38:13.450539     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 8 lines ...
Machine	i-062d93a30639b40da					machine "i-062d93a30639b40da" has not yet joined cluster
Machine	i-092e162190fc71ac0					machine "i-092e162190fc71ac0" has not yet joined cluster
Node	ip-172-20-33-16.ap-southeast-1.compute.internal		master "ip-172-20-33-16.ap-southeast-1.compute.internal" is missing kube-controller-manager pod
Pod	kube-system/kube-dns-77cbd9bf6f-4grbx			system-cluster-critical pod "kube-dns-77cbd9bf6f-4grbx" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-h4qlp	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-h4qlp" is pending

Validation Failed
W0911 18:38:27.351497     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 8 lines ...
Machine	i-062d93a30639b40da					machine "i-062d93a30639b40da" has not yet joined cluster
Machine	i-092e162190fc71ac0					machine "i-092e162190fc71ac0" has not yet joined cluster
Node	ip-172-20-33-16.ap-southeast-1.compute.internal		master "ip-172-20-33-16.ap-southeast-1.compute.internal" is missing kube-controller-manager pod
Pod	kube-system/kube-dns-77cbd9bf6f-4grbx			system-cluster-critical pod "kube-dns-77cbd9bf6f-4grbx" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-h4qlp	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-h4qlp" is pending

Validation Failed
W0911 18:38:39.627383     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-33-16.ap-southeast-1.compute.internal						master "ip-172-20-33-16.ap-southeast-1.compute.internal" is missing kube-controller-manager pod
Pod	kube-system/etcd-manager-events-ip-172-20-33-16.ap-southeast-1.compute.internal		system-cluster-critical pod "etcd-manager-events-ip-172-20-33-16.ap-southeast-1.compute.internal" is pending
Pod	kube-system/kube-controller-manager-ip-172-20-33-16.ap-southeast-1.compute.internal	system-cluster-critical pod "kube-controller-manager-ip-172-20-33-16.ap-southeast-1.compute.internal" is pending
Pod	kube-system/kube-dns-77cbd9bf6f-4grbx							system-cluster-critical pod "kube-dns-77cbd9bf6f-4grbx" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-h4qlp					system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-h4qlp" is pending

Validation Failed
W0911 18:38:51.933499     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-03d91f655d473ab71					machine "i-03d91f655d473ab71" has not yet joined cluster
Machine	i-062d93a30639b40da					machine "i-062d93a30639b40da" has not yet joined cluster
Machine	i-092e162190fc71ac0					machine "i-092e162190fc71ac0" has not yet joined cluster
Pod	kube-system/kube-dns-77cbd9bf6f-4grbx			system-cluster-critical pod "kube-dns-77cbd9bf6f-4grbx" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-h4qlp	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-h4qlp" is pending

Validation Failed
W0911 18:39:04.252050     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-03d91f655d473ab71					machine "i-03d91f655d473ab71" has not yet joined cluster
Machine	i-062d93a30639b40da					machine "i-062d93a30639b40da" has not yet joined cluster
Machine	i-092e162190fc71ac0					machine "i-092e162190fc71ac0" has not yet joined cluster
Pod	kube-system/kube-dns-77cbd9bf6f-4grbx			system-cluster-critical pod "kube-dns-77cbd9bf6f-4grbx" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-h4qlp	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-h4qlp" is pending

Validation Failed
W0911 18:39:16.595040     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-03d91f655d473ab71					machine "i-03d91f655d473ab71" has not yet joined cluster
Machine	i-062d93a30639b40da					machine "i-062d93a30639b40da" has not yet joined cluster
Machine	i-092e162190fc71ac0					machine "i-092e162190fc71ac0" has not yet joined cluster
Pod	kube-system/kube-dns-77cbd9bf6f-4grbx			system-cluster-critical pod "kube-dns-77cbd9bf6f-4grbx" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-h4qlp	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-h4qlp" is pending

Validation Failed
W0911 18:39:28.892134     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 11 lines ...
Node	ip-172-20-61-15.ap-southeast-1.compute.internal		node "ip-172-20-61-15.ap-southeast-1.compute.internal" is not ready
Pod	kube-system/kube-dns-77cbd9bf6f-4grbx			system-cluster-critical pod "kube-dns-77cbd9bf6f-4grbx" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-h4qlp	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-h4qlp" is pending
Pod	kube-system/kube-flannel-ds-92k6h			system-node-critical pod "kube-flannel-ds-92k6h" is pending
Pod	kube-system/kube-flannel-ds-ltxgv			system-node-critical pod "kube-flannel-ds-ltxgv" is pending

Validation Failed
W0911 18:39:41.255325     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-53-20.ap-southeast-1.compute.internal				node "ip-172-20-53-20.ap-southeast-1.compute.internal" is not ready
Pod	kube-system/kube-dns-77cbd9bf6f-4grbx					system-cluster-critical pod "kube-dns-77cbd9bf6f-4grbx" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-h4qlp			system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-h4qlp" is pending
Pod	kube-system/kube-flannel-ds-62htq					system-node-critical pod "kube-flannel-ds-62htq" is pending
Pod	kube-system/kube-proxy-ip-172-20-53-20.ap-southeast-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-53-20.ap-southeast-1.compute.internal" is pending

Validation Failed
W0911 18:39:53.578766     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Machine	i-029ba5fe62a295d64				machine "i-029ba5fe62a295d64" has not yet joined cluster
Node	ip-172-20-53-20.ap-southeast-1.compute.internal	node "ip-172-20-53-20.ap-southeast-1.compute.internal" is not ready
Pod	kube-system/kube-dns-77cbd9bf6f-2trb5		system-cluster-critical pod "kube-dns-77cbd9bf6f-2trb5" is not ready (kubedns)

Validation Failed
W0911 18:40:05.909553     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 5 lines ...
ip-172-20-61-15.ap-southeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-029ba5fe62a295d64	machine "i-029ba5fe62a295d64" has not yet joined cluster

Validation Failed
W0911 18:40:18.203381     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 5 lines ...
ip-172-20-61-15.ap-southeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-029ba5fe62a295d64	machine "i-029ba5fe62a295d64" has not yet joined cluster

Validation Failed
W0911 18:40:30.523488     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 5 lines ...
ip-172-20-61-15.ap-southeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-029ba5fe62a295d64	machine "i-029ba5fe62a295d64" has not yet joined cluster

Validation Failed
W0911 18:40:42.858688     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 5 lines ...
ip-172-20-61-15.ap-southeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-029ba5fe62a295d64	machine "i-029ba5fe62a295d64" has not yet joined cluster

Validation Failed
W0911 18:40:55.166873     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 5 lines ...
ip-172-20-61-15.ap-southeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-029ba5fe62a295d64	machine "i-029ba5fe62a295d64" has not yet joined cluster

Validation Failed
W0911 18:41:07.612333     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 5 lines ...
ip-172-20-61-15.ap-southeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-029ba5fe62a295d64	machine "i-029ba5fe62a295d64" has not yet joined cluster

Validation Failed
W0911 18:41:19.946479     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 5 lines ...
ip-172-20-61-15.ap-southeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-029ba5fe62a295d64	machine "i-029ba5fe62a295d64" has not yet joined cluster

Validation Failed
W0911 18:41:32.246145     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 5 lines ...
ip-172-20-61-15.ap-southeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-029ba5fe62a295d64	machine "i-029ba5fe62a295d64" has not yet joined cluster

Validation Failed
W0911 18:41:44.493527     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 5 lines ...
ip-172-20-61-15.ap-southeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-029ba5fe62a295d64	machine "i-029ba5fe62a295d64" has not yet joined cluster

Validation Failed
W0911 18:41:56.868282     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 5 lines ...
ip-172-20-61-15.ap-southeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-029ba5fe62a295d64	machine "i-029ba5fe62a295d64" has not yet joined cluster

Validation Failed
W0911 18:42:09.137248     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 5 lines ...
ip-172-20-61-15.ap-southeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-029ba5fe62a295d64	machine "i-029ba5fe62a295d64" has not yet joined cluster

Validation Failed
W0911 18:42:22.061489     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 5 lines ...
ip-172-20-61-15.ap-southeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-029ba5fe62a295d64	machine "i-029ba5fe62a295d64" has not yet joined cluster

Validation Failed
W0911 18:42:34.428408     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 5 lines ...
ip-172-20-61-15.ap-southeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-029ba5fe62a295d64	machine "i-029ba5fe62a295d64" has not yet joined cluster

Validation Failed
W0911 18:42:46.739325     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 5 lines ...
ip-172-20-61-15.ap-southeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-029ba5fe62a295d64	machine "i-029ba5fe62a295d64" has not yet joined cluster

Validation Failed
W0911 18:42:59.082491     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 5 lines ...
ip-172-20-61-15.ap-southeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-029ba5fe62a295d64	machine "i-029ba5fe62a295d64" has not yet joined cluster

Validation Failed
W0911 18:43:11.397401     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 5 lines ...
ip-172-20-61-15.ap-southeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-029ba5fe62a295d64	machine "i-029ba5fe62a295d64" has not yet joined cluster

Validation Failed
W0911 18:43:23.689722     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 5 lines ...
ip-172-20-61-15.ap-southeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-029ba5fe62a295d64	machine "i-029ba5fe62a295d64" has not yet joined cluster

Validation Failed
W0911 18:43:36.005659     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 5 lines ...
ip-172-20-61-15.ap-southeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-029ba5fe62a295d64	machine "i-029ba5fe62a295d64" has not yet joined cluster

Validation Failed
W0911 18:43:48.544962     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 5 lines ...
ip-172-20-61-15.ap-southeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-029ba5fe62a295d64	machine "i-029ba5fe62a295d64" has not yet joined cluster

Validation Failed
W0911 18:44:00.825346     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 5 lines ...
ip-172-20-61-15.ap-southeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-029ba5fe62a295d64	machine "i-029ba5fe62a295d64" has not yet joined cluster

Validation Failed
W0911 18:44:13.089262     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 5 lines ...
ip-172-20-61-15.ap-southeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-029ba5fe62a295d64	machine "i-029ba5fe62a295d64" has not yet joined cluster

Validation Failed
W0911 18:44:25.450280     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 5 lines ...
ip-172-20-61-15.ap-southeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-029ba5fe62a295d64	machine "i-029ba5fe62a295d64" has not yet joined cluster

Validation Failed
W0911 18:44:37.756566     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 5 lines ...
ip-172-20-61-15.ap-southeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-029ba5fe62a295d64	machine "i-029ba5fe62a295d64" has not yet joined cluster

Validation Failed
W0911 18:44:50.038209     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 5 lines ...
ip-172-20-61-15.ap-southeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-029ba5fe62a295d64	machine "i-029ba5fe62a295d64" has not yet joined cluster

Validation Failed
W0911 18:45:02.413357     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 5 lines ...
ip-172-20-61-15.ap-southeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-029ba5fe62a295d64	machine "i-029ba5fe62a295d64" has not yet joined cluster

Validation Failed
W0911 18:45:14.669209     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 5 lines ...
ip-172-20-61-15.ap-southeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-029ba5fe62a295d64	machine "i-029ba5fe62a295d64" has not yet joined cluster

Validation Failed
W0911 18:45:26.896891     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 5 lines ...
ip-172-20-61-15.ap-southeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-029ba5fe62a295d64	machine "i-029ba5fe62a295d64" has not yet joined cluster

Validation Failed
W0911 18:45:39.295806     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 5 lines ...
ip-172-20-61-15.ap-southeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-029ba5fe62a295d64	machine "i-029ba5fe62a295d64" has not yet joined cluster

Validation Failed
W0911 18:45:51.577292     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 5 lines ...
ip-172-20-61-15.ap-southeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-029ba5fe62a295d64	machine "i-029ba5fe62a295d64" has not yet joined cluster

Validation Failed
W0911 18:46:03.901617     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 5 lines ...
ip-172-20-61-15.ap-southeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-029ba5fe62a295d64	machine "i-029ba5fe62a295d64" has not yet joined cluster

Validation Failed
W0911 18:46:16.876733     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 5 lines ...
ip-172-20-61-15.ap-southeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-029ba5fe62a295d64	machine "i-029ba5fe62a295d64" has not yet joined cluster

Validation Failed
W0911 18:46:29.352818     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 5 lines ...
ip-172-20-61-15.ap-southeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-029ba5fe62a295d64	machine "i-029ba5fe62a295d64" has not yet joined cluster

Validation Failed
W0911 18:46:41.587061     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 5 lines ...
ip-172-20-61-15.ap-southeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-029ba5fe62a295d64	machine "i-029ba5fe62a295d64" has not yet joined cluster

Validation Failed
W0911 18:46:53.902305     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 5 lines ...
ip-172-20-61-15.ap-southeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-029ba5fe62a295d64	machine "i-029ba5fe62a295d64" has not yet joined cluster

Validation Failed
W0911 18:47:06.305349     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 5 lines ...
ip-172-20-61-15.ap-southeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-029ba5fe62a295d64	machine "i-029ba5fe62a295d64" has not yet joined cluster

Validation Failed
W0911 18:47:18.580114     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 5 lines ...
ip-172-20-61-15.ap-southeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-029ba5fe62a295d64	machine "i-029ba5fe62a295d64" has not yet joined cluster

Validation Failed
W0911 18:47:30.838782     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 5 lines ...
ip-172-20-61-15.ap-southeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-029ba5fe62a295d64	machine "i-029ba5fe62a295d64" has not yet joined cluster

Validation Failed
W0911 18:47:43.155726     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 5 lines ...
ip-172-20-61-15.ap-southeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-029ba5fe62a295d64	machine "i-029ba5fe62a295d64" has not yet joined cluster

Validation Failed
W0911 18:47:55.463338     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 5 lines ...
ip-172-20-61-15.ap-southeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-029ba5fe62a295d64	machine "i-029ba5fe62a295d64" has not yet joined cluster

Validation Failed
W0911 18:48:07.753286     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 5 lines ...
ip-172-20-61-15.ap-southeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-029ba5fe62a295d64	machine "i-029ba5fe62a295d64" has not yet joined cluster

Validation Failed
W0911 18:48:20.028979     173 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 5 lines ...
ip-172-20-61-15.ap-southeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-029ba5fe62a295d64	machine "i-029ba5fe62a295d64" has not yet joined cluster

Validation Failed
W0911 18:48:32.325852     173 validate_cluster.go:221] (will retry): cluster not yet healthy

Validation failed: wait time exceeded during validation
2020/09/11 18:48:42 process.go:155: Step '/tmp/kops217661516/kops validate cluster e2e-kops-flanl-centos7.test-cncf-aws.k8s.io --wait 15m' finished in 15m2.291183996s
2020/09/11 18:48:42 process.go:153: Running: kubectl -n kube-system get pods -ojson -l k8s-app=kops-controller
2020/09/11 18:48:42 process.go:153: Running: /tmp/kops217661516/kops toolbox dump --name e2e-kops-flanl-centos7.test-cncf-aws.k8s.io -ojson
I0911 18:48:42.389608     185 featureflag.go:167] FeatureFlag "SpecOverrideFlag"=true
2020/09/11 18:48:44 process.go:155: Step 'kubectl -n kube-system get pods -ojson -l k8s-app=kops-controller' finished in 1.939836141s
2020/09/11 18:48:44 process.go:153: Running: kubectl -n kube-system logs --all-containers kops-controller-5bd7n
... skipping 188 lines ...
	volume:vol-04429969b6191f4ff
	volume:vol-0f3fa81f6c87c8e82
	internet-gateway:igw-08e0342959b5526ad
	subnet:subnet-06160e0ad76c4f405
	volume:vol-026ab49a819c66a92
volume:vol-0085d9042c5d79ffb	still has dependencies, will retry
I0911 18:50:19.821970     237 errors.go:32] unexpected aws error code: "InvalidVolume.NotFound"
volume:vol-0e68c14458418a15c	ok
volume:vol-09b26bde95a2cc168	still has dependencies, will retry
volume:vol-0f3fa81f6c87c8e82	still has dependencies, will retry
volume:vol-026ab49a819c66a92	still has dependencies, will retry
volume:vol-04429969b6191f4ff	still has dependencies, will retry
subnet:subnet-06160e0ad76c4f405	still has dependencies, will retry
... skipping 51 lines ...
	route-table:rtb-07422e548d73110a9
	dhcp-options:dopt-07abbd53f8aee2969
	security-group:sg-00fe60ce6ada599f2
	vpc:vpc-064c7ea6a146638d8
	volume:vol-09b26bde95a2cc168
	security-group:sg-032f0a60b92d84a65
I0911 18:50:53.580408     237 errors.go:32] unexpected aws error code: "InvalidVolume.NotFound"
volume:vol-026ab49a819c66a92	ok
I0911 18:50:53.710169     237 errors.go:32] unexpected aws error code: "InvalidVolume.NotFound"
volume:vol-09b26bde95a2cc168	ok
security-group:sg-032f0a60b92d84a65	ok
subnet:subnet-06160e0ad76c4f405	ok
internet-gateway:igw-08e0342959b5526ad	ok
security-group:sg-00fe60ce6ada599f2	ok
route-table:rtb-07422e548d73110a9	ok
vpc:vpc-064c7ea6a146638d8	ok
dhcp-options:dopt-07abbd53f8aee2969	ok
Deleted kubectl config for e2e-kops-flanl-centos7.test-cncf-aws.k8s.io

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