This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 5 succeeded
Started2020-10-10 22:44
Elapsed19m18s
Revision
job-versionv1.18.9
revisionv1.18.9

Test Failures


Up 15m32s

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

Filter through log files


Show 5 Passed Tests

Error lines from build-log.txt

Activated service account credentials for: [pr-kubekins@kubernetes-jenkins-pull.iam.gserviceaccount.com]
fatal: not a git repository (or any of the parent directories): .git
+ /workspace/scenarios/kubernetes_e2e.py --cluster=e2e-kops-centos7-k18-ko18.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= '--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/markers/release-1.18/latest-ci-updown-green.txt --provider=aws '--test_args=--ginkgo.skip=\[Slow\]|\[Serial\]|\[Disruptive\]|\[Flaky\]|\[Feature:.+\]|\[HPA\]|Dashboard|Services.*functioning.*NodePort|Services.*rejected.*endpoints|Services.*affinity' --timeout=60m
starts with local mode
Environment:
ARTIFACTS=/logs/artifacts
AWS_DEFAULT_PROFILE=default
AWS_PROFILE=default
... skipping 146 lines ...
2020/10/10 22:45:39 process.go:155: Step './get-kube.sh' finished in 55.98747385s
2020/10/10 22:45:39 process.go:153: Running: /tmp/kops902174236/kops get clusters e2e-kops-centos7-k18-ko18.test-cncf-aws.k8s.io

cluster not found "e2e-kops-centos7-k18-ko18.test-cncf-aws.k8s.io"
2020/10/10 22:45:40 process.go:155: Step '/tmp/kops902174236/kops get clusters e2e-kops-centos7-k18-ko18.test-cncf-aws.k8s.io' finished in 1.120107341s
2020/10/10 22:45:40 util.go:42: curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2020/10/10 22:45:40 kops.go:514: failed to get external ip from metadata service: http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip returned 404
2020/10/10 22:45:40 util.go:68: curl https://ip.jsb.workers.dev
2020/10/10 22:45:41 kops.go:439: Using external IP for admin access: 34.69.232.45/32
2020/10/10 22:45:41 process.go:153: Running: /tmp/kops902174236/kops create cluster --name e2e-kops-centos7-k18-ko18.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-northeast-2a --master-size c5.large --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.18.9 --admin-access 34.69.232.45/32 --image 679593333241/CentOS Linux 7 x86_64 HVM EBS ENA 2002_01-b7ee8a69-ee97-4a49-9e68-afaee216db2e-ami-0042af67f8e4dcc20.4 --cloud aws --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes
I1010 22:45:41.173941     163 featureflag.go:154] FeatureFlag "SpecOverrideFlag"=true
I1010 22:45:41.412985     163 create_cluster.go:1537] Using SSH public key: /workspace/.ssh/kube_aws_rsa.pub
I1010 22:45:43.078256     163 subnets.go:184] Assigned CIDR 172.20.32.0/19 to subnet ap-northeast-2a
... skipping 47 lines ...

2020/10/10 22:46:08 process.go:155: Step '/tmp/kops902174236/kops create cluster --name e2e-kops-centos7-k18-ko18.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-northeast-2a --master-size c5.large --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.18.9 --admin-access 34.69.232.45/32 --image 679593333241/CentOS Linux 7 x86_64 HVM EBS ENA 2002_01-b7ee8a69-ee97-4a49-9e68-afaee216db2e-ami-0042af67f8e4dcc20.4 --cloud aws --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes' finished in 27.357883078s
2020/10/10 22:46:08 process.go:153: Running: /tmp/kops902174236/kops validate cluster e2e-kops-centos7-k18-ko18.test-cncf-aws.k8s.io --wait 15m
I1010 22:46:08.532511     192 featureflag.go:154] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-kops-centos7-k18-ko18.test-cncf-aws.k8s.io

W1010 22:46:10.423276     192 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-centos7-k18-ko18.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W1010 22:46:20.639399     192 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-centos7-k18-ko18.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

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
W1010 22:46:30.700499     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

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
W1010 22:46:40.816243     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

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
W1010 22:46:51.021085     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

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
W1010 22:47:01.083599     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

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

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
W1010 22:47:31.279373     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

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
W1010 22:47:41.358481     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

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
W1010 22:47:51.453324     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

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
W1010 22:48:01.529099     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

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
W1010 22:48:11.604956     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

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
W1010 22:48:21.663550     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

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
W1010 22:48:31.731406     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

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

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
W1010 22:49:01.921648     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

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
W1010 22:49:11.997871     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

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
W1010 22:49:22.089280     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

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
W1010 22:49:32.157046     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

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
W1010 22:49:42.224867     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

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
W1010 22:49:52.379271     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

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
W1010 22:50:02.441223     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

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
W1010 22:50:12.501005     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

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

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

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
W1010 22:51:02.765751     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

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
W1010 22:51:12.820434     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

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
W1010 22:51:22.908756     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

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
W1010 22:51:33.026971     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

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
W1010 22:51:43.105433     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

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
W1010 22:51:53.195049     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

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
W1010 22:52:03.256113     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

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
W1010 22:52:13.341773     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-06c9280ff342e9976				machine "i-06c9280ff342e9976" has not yet joined cluster
Machine	i-0a806353621ba1ee0				machine "i-0a806353621ba1ee0" has not yet joined cluster
Machine	i-0ff61a1adbad0ed8d				machine "i-0ff61a1adbad0ed8d" has not yet joined cluster
Pod	kube-system/kube-dns-6c699b5445-6l77n		system-cluster-critical pod "kube-dns-6c699b5445-6l77n" is pending
Pod	kube-system/kube-dns-autoscaler-cd7778b7b-gjlhc	system-cluster-critical pod "kube-dns-autoscaler-cd7778b7b-gjlhc" is pending

Validation Failed
W1010 22:52:26.731611     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 8 lines ...
Machine	i-06c9280ff342e9976							machine "i-06c9280ff342e9976" has not yet joined cluster
Machine	i-0ff61a1adbad0ed8d							machine "i-0ff61a1adbad0ed8d" has not yet joined cluster
Pod	kube-system/kube-dns-6c699b5445-6l77n					system-cluster-critical pod "kube-dns-6c699b5445-6l77n" is pending
Pod	kube-system/kube-dns-autoscaler-cd7778b7b-gjlhc				system-cluster-critical pod "kube-dns-autoscaler-cd7778b7b-gjlhc" is pending
Pod	kube-system/kube-proxy-ip-172-20-46-229.ap-northeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-46-229.ap-northeast-2.compute.internal" is pending

Validation Failed
W1010 22:52:38.705450     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 8 lines ...
Machine	i-06c9280ff342e9976							machine "i-06c9280ff342e9976" has not yet joined cluster
Machine	i-0ff61a1adbad0ed8d							machine "i-0ff61a1adbad0ed8d" has not yet joined cluster
Pod	kube-system/kube-dns-6c699b5445-6l77n					system-cluster-critical pod "kube-dns-6c699b5445-6l77n" is pending
Pod	kube-system/kube-dns-autoscaler-cd7778b7b-gjlhc				system-cluster-critical pod "kube-dns-autoscaler-cd7778b7b-gjlhc" is pending
Pod	kube-system/kube-proxy-ip-172-20-46-229.ap-northeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-46-229.ap-northeast-2.compute.internal" is pending

Validation Failed
W1010 22:52:50.667252     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-065a0250fb8ec7264				machine "i-065a0250fb8ec7264" has not yet joined cluster
Machine	i-06c9280ff342e9976				machine "i-06c9280ff342e9976" has not yet joined cluster
Machine	i-0ff61a1adbad0ed8d				machine "i-0ff61a1adbad0ed8d" has not yet joined cluster
Pod	kube-system/kube-dns-6c699b5445-6l77n		system-cluster-critical pod "kube-dns-6c699b5445-6l77n" is pending
Pod	kube-system/kube-dns-autoscaler-cd7778b7b-gjlhc	system-cluster-critical pod "kube-dns-autoscaler-cd7778b7b-gjlhc" is pending

Validation Failed
W1010 22:53:02.550014     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-065a0250fb8ec7264			machine "i-065a0250fb8ec7264" has not yet joined cluster
Machine	i-06c9280ff342e9976			machine "i-06c9280ff342e9976" has not yet joined cluster
Machine	i-0ff61a1adbad0ed8d			machine "i-0ff61a1adbad0ed8d" has not yet joined cluster
Pod	kube-system/kube-dns-6c699b5445-6l77n	system-cluster-critical pod "kube-dns-6c699b5445-6l77n" is not ready (kubedns)
Pod	kube-system/kube-dns-6c699b5445-qz8kk	system-cluster-critical pod "kube-dns-6c699b5445-qz8kk" is pending

Validation Failed
W1010 22:53:14.513612     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-065a0250fb8ec7264	machine "i-065a0250fb8ec7264" has not yet joined cluster
Machine	i-06c9280ff342e9976	machine "i-06c9280ff342e9976" has not yet joined cluster
Machine	i-0ff61a1adbad0ed8d	machine "i-0ff61a1adbad0ed8d" has not yet joined cluster

Validation Failed
W1010 22:53:26.460266     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-065a0250fb8ec7264	machine "i-065a0250fb8ec7264" has not yet joined cluster
Machine	i-06c9280ff342e9976	machine "i-06c9280ff342e9976" has not yet joined cluster
Machine	i-0ff61a1adbad0ed8d	machine "i-0ff61a1adbad0ed8d" has not yet joined cluster

Validation Failed
W1010 22:53:38.397849     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-065a0250fb8ec7264	machine "i-065a0250fb8ec7264" has not yet joined cluster
Machine	i-06c9280ff342e9976	machine "i-06c9280ff342e9976" has not yet joined cluster
Machine	i-0ff61a1adbad0ed8d	machine "i-0ff61a1adbad0ed8d" has not yet joined cluster

Validation Failed
W1010 22:53:50.455997     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-065a0250fb8ec7264	machine "i-065a0250fb8ec7264" has not yet joined cluster
Machine	i-06c9280ff342e9976	machine "i-06c9280ff342e9976" has not yet joined cluster
Machine	i-0ff61a1adbad0ed8d	machine "i-0ff61a1adbad0ed8d" has not yet joined cluster

Validation Failed
W1010 22:54:02.542576     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-065a0250fb8ec7264	machine "i-065a0250fb8ec7264" has not yet joined cluster
Machine	i-06c9280ff342e9976	machine "i-06c9280ff342e9976" has not yet joined cluster
Machine	i-0ff61a1adbad0ed8d	machine "i-0ff61a1adbad0ed8d" has not yet joined cluster

Validation Failed
W1010 22:54:14.440529     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-065a0250fb8ec7264	machine "i-065a0250fb8ec7264" has not yet joined cluster
Machine	i-06c9280ff342e9976	machine "i-06c9280ff342e9976" has not yet joined cluster
Machine	i-0ff61a1adbad0ed8d	machine "i-0ff61a1adbad0ed8d" has not yet joined cluster

Validation Failed
W1010 22:54:26.508914     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
KIND	NAME									MESSAGE
Machine	i-065a0250fb8ec7264							machine "i-065a0250fb8ec7264" has not yet joined cluster
Machine	i-06c9280ff342e9976							machine "i-06c9280ff342e9976" has not yet joined cluster
Node	ip-172-20-49-52.ap-northeast-2.compute.internal				node "ip-172-20-49-52.ap-northeast-2.compute.internal" is not ready
Pod	kube-system/kube-proxy-ip-172-20-49-52.ap-northeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-49-52.ap-northeast-2.compute.internal" is pending

Validation Failed
W1010 22:54:38.521751     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-065a0250fb8ec7264	machine "i-065a0250fb8ec7264" has not yet joined cluster
Machine	i-06c9280ff342e9976	machine "i-06c9280ff342e9976" has not yet joined cluster

Validation Failed
W1010 22:54:50.539603     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 6 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Machine	i-065a0250fb8ec7264				machine "i-065a0250fb8ec7264" has not yet joined cluster
Node	ip-172-20-39-9.ap-northeast-2.compute.internal	node "ip-172-20-39-9.ap-northeast-2.compute.internal" is not ready

Validation Failed
W1010 22:55:02.569555     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-96.ap-northeast-2.compute.internal		master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-065a0250fb8ec7264	machine "i-065a0250fb8ec7264" has not yet joined cluster

Validation Failed
W1010 22:55:14.539238     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-96.ap-northeast-2.compute.internal		master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-065a0250fb8ec7264	machine "i-065a0250fb8ec7264" has not yet joined cluster

Validation Failed
W1010 22:55:26.476210     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-96.ap-northeast-2.compute.internal		master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-065a0250fb8ec7264	machine "i-065a0250fb8ec7264" has not yet joined cluster

Validation Failed
W1010 22:55:38.581406     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-96.ap-northeast-2.compute.internal		master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-065a0250fb8ec7264	machine "i-065a0250fb8ec7264" has not yet joined cluster

Validation Failed
W1010 22:55:50.564174     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-96.ap-northeast-2.compute.internal		master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-065a0250fb8ec7264	machine "i-065a0250fb8ec7264" has not yet joined cluster

Validation Failed
W1010 22:56:02.555479     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-96.ap-northeast-2.compute.internal		master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-065a0250fb8ec7264	machine "i-065a0250fb8ec7264" has not yet joined cluster

Validation Failed
W1010 22:56:14.532173     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-96.ap-northeast-2.compute.internal		master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-065a0250fb8ec7264	machine "i-065a0250fb8ec7264" has not yet joined cluster

Validation Failed
W1010 22:56:27.258570     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-96.ap-northeast-2.compute.internal		master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-065a0250fb8ec7264	machine "i-065a0250fb8ec7264" has not yet joined cluster

Validation Failed
W1010 22:56:39.235445     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-96.ap-northeast-2.compute.internal		master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-065a0250fb8ec7264	machine "i-065a0250fb8ec7264" has not yet joined cluster

Validation Failed
W1010 22:56:51.101384     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-96.ap-northeast-2.compute.internal		master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-065a0250fb8ec7264	machine "i-065a0250fb8ec7264" has not yet joined cluster

Validation Failed
W1010 22:57:03.103727     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-96.ap-northeast-2.compute.internal		master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-065a0250fb8ec7264	machine "i-065a0250fb8ec7264" has not yet joined cluster

Validation Failed
W1010 22:57:15.167715     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-96.ap-northeast-2.compute.internal		master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-065a0250fb8ec7264	machine "i-065a0250fb8ec7264" has not yet joined cluster

Validation Failed
W1010 22:57:27.136978     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-96.ap-northeast-2.compute.internal		master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-065a0250fb8ec7264	machine "i-065a0250fb8ec7264" has not yet joined cluster

Validation Failed
W1010 22:57:39.298220     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-96.ap-northeast-2.compute.internal		master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-065a0250fb8ec7264	machine "i-065a0250fb8ec7264" has not yet joined cluster

Validation Failed
W1010 22:57:51.352856     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-96.ap-northeast-2.compute.internal		master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-065a0250fb8ec7264	machine "i-065a0250fb8ec7264" has not yet joined cluster

Validation Failed
W1010 22:58:03.376991     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-96.ap-northeast-2.compute.internal		master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-065a0250fb8ec7264	machine "i-065a0250fb8ec7264" has not yet joined cluster

Validation Failed
W1010 22:58:15.252973     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-96.ap-northeast-2.compute.internal		master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-065a0250fb8ec7264	machine "i-065a0250fb8ec7264" has not yet joined cluster

Validation Failed
W1010 22:58:27.167134     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-96.ap-northeast-2.compute.internal		master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-065a0250fb8ec7264	machine "i-065a0250fb8ec7264" has not yet joined cluster

Validation Failed
W1010 22:58:39.095436     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-96.ap-northeast-2.compute.internal		master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-065a0250fb8ec7264	machine "i-065a0250fb8ec7264" has not yet joined cluster

Validation Failed
W1010 22:58:51.046615     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-96.ap-northeast-2.compute.internal		master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-065a0250fb8ec7264	machine "i-065a0250fb8ec7264" has not yet joined cluster

Validation Failed
W1010 22:59:03.086764     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-96.ap-northeast-2.compute.internal		master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-065a0250fb8ec7264	machine "i-065a0250fb8ec7264" has not yet joined cluster

Validation Failed
W1010 22:59:15.000333     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-96.ap-northeast-2.compute.internal		master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-065a0250fb8ec7264	machine "i-065a0250fb8ec7264" has not yet joined cluster

Validation Failed
W1010 22:59:26.898373     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-96.ap-northeast-2.compute.internal		master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-065a0250fb8ec7264	machine "i-065a0250fb8ec7264" has not yet joined cluster

Validation Failed
W1010 22:59:38.957205     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-96.ap-northeast-2.compute.internal		master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-065a0250fb8ec7264	machine "i-065a0250fb8ec7264" has not yet joined cluster

Validation Failed
W1010 22:59:50.936475     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-96.ap-northeast-2.compute.internal		master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-065a0250fb8ec7264	machine "i-065a0250fb8ec7264" has not yet joined cluster

Validation Failed
W1010 23:00:03.064590     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-96.ap-northeast-2.compute.internal		master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-065a0250fb8ec7264	machine "i-065a0250fb8ec7264" has not yet joined cluster

Validation Failed
W1010 23:00:15.148033     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-96.ap-northeast-2.compute.internal		master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-065a0250fb8ec7264	machine "i-065a0250fb8ec7264" has not yet joined cluster

Validation Failed
W1010 23:00:27.687229     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-96.ap-northeast-2.compute.internal		master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-065a0250fb8ec7264	machine "i-065a0250fb8ec7264" has not yet joined cluster

Validation Failed
W1010 23:00:39.627847     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-96.ap-northeast-2.compute.internal		master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-065a0250fb8ec7264	machine "i-065a0250fb8ec7264" has not yet joined cluster

Validation Failed
W1010 23:00:51.539861     192 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-96.ap-northeast-2.compute.internal		master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-065a0250fb8ec7264	machine "i-065a0250fb8ec7264" has not yet joined cluster

Validation Failed
W1010 23:01:03.620791     192 validate_cluster.go:221] (will retry): cluster not yet healthy

Validation failed: wait time exceeded during validation
2020/10/10 23:01:13 process.go:155: Step '/tmp/kops902174236/kops validate cluster e2e-kops-centos7-k18-ko18.test-cncf-aws.k8s.io --wait 15m' finished in 15m5.256016452s
2020/10/10 23:01:13 process.go:153: Running: kubectl -n kube-system get pods -ojson -l k8s-app=kops-controller
2020/10/10 23:01:13 process.go:153: Running: /tmp/kops902174236/kops toolbox dump --name e2e-kops-centos7-k18-ko18.test-cncf-aws.k8s.io -ojson
I1010 23:01:13.777833     210 featureflag.go:154] FeatureFlag "SpecOverrideFlag"=true
2020/10/10 23:01:15 process.go:155: Step 'kubectl -n kube-system get pods -ojson -l k8s-app=kops-controller' finished in 2.016597115s
2020/10/10 23:01:15 process.go:153: Running: kubectl -n kube-system logs --all-containers kops-controller-kqdb6
... skipping 237 lines ...
dhcp-options:dopt-08f951038016d8fb1	ok
Deleted kubectl config for e2e-kops-centos7-k18-ko18.test-cncf-aws.k8s.io

Deleted cluster: "e2e-kops-centos7-k18-ko18.test-cncf-aws.k8s.io"
2020/10/10 23:03:46 process.go:155: Step '/tmp/kops902174236/kops delete cluster e2e-kops-centos7-k18-ko18.test-cncf-aws.k8s.io --yes' finished in 1m49.867914833s
2020/10/10 23:03:46 process.go:96: Saved XML output to /logs/artifacts/junit_runner.xml.
2020/10/10 23:03:46 main.go:312: Something went wrong: starting e2e cluster: kops validate cluster failed: error during /tmp/kops902174236/kops validate cluster e2e-kops-centos7-k18-ko18.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 ...