This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 5 succeeded
Started2021-10-12 07:11
Elapsed17m59s
Revision
job-versionv1.23.0-alpha.3.278+a7c67c03ff09c2
kubetest-version
revisionv1.23.0-alpha.3.278+a7c67c03ff09c2

Test Failures


kubetest Up 15m43s

kops validate cluster failed: error during /tmp/kops4054548213/kops validate cluster e2e-kops-aws-k8s-storage-selinux.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
+ WRAPPED_COMMAND_PID=32
+ wait 32
+ /workspace/scenarios/kubernetes_e2e.py --cluster=e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --deployment=kops --env=KOPS_ARCH=amd64 --env=KUBE_SSH_USER=ec2-user --env=KOPS_RUN_TOO_NEW_VERSION=1 --extract=ci/latest --ginkgo-parallel --kops-image=309956199498/RHEL-7.8_HVM_GA-20200225-x86_64-1-Hourly2-GP2 --kops-args=--master-image=137112412989/amzn2-ami-hvm-2.0.20200617.0-x86_64-gp2 --kops-overrides=spec.docker.selinuxEnabled=true --kops-priority-path=/workspace/kubernetes/platforms/linux/amd64 --kops-ssh-user=ec2-user --kops-version=https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt --provider=aws '--test_args=--ginkgo.focus=\[sig-storage\].*\[Slow\] --ginkgo.skip=\[Serial\]|\[Disruptive\]|\[Flaky\]|\[Feature:.+\] --minStartupPods=8' --timeout=120m
starts with local mode
Environment:
ARTIFACTS=/logs/artifacts
... skipping 158 lines ...
md5sum(kubernetes-test-linux-amd64.tar.gz)=05e7ee8bd82e2cc57756f24ce868e9b4
sha512sum(kubernetes-test-linux-amd64.tar.gz)=4d0b09446bd562c8784a207267a5b620e731e86bfc1688d88e0a878779f58b145705084f5c3033976f467e3165ec526702e1bad006a555e2cf353f9ee9d2be81

Extracting /workspace/kubernetes/test/kubernetes-test-linux-amd64.tar.gz into /workspace/kubernetes/platforms/linux/amd64
2021/10/12 07:12:10 process.go:155: Step './get-kube.sh' finished in 28.664254051s
2021/10/12 07:12:10 process.go:153: Running: /tmp/kops4054548213/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io
Error: cluster not found "e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io"
2021/10/12 07:12:10 process.go:155: Step '/tmp/kops4054548213/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 490.828436ms
2021/10/12 07:12:10 util.go:42: curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/12 07:12:10 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
2021/10/12 07:12:10 util.go:68: curl https://ip.jsb.workers.dev
2021/10/12 07:12:11 kops.go:439: Using external IP for admin access: 34.68.52.185/32
2021/10/12 07:12:11 process.go:153: Running: /tmp/kops4054548213/kops create cluster --name e2e-kops-aws-k8s-storage-selinux.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/k8s-release-dev/ci/v1.23.0-alpha.3.278+a7c67c03ff09c2 --admin-access 34.68.52.185/32 --image 309956199498/RHEL-7.8_HVM_GA-20200225-x86_64-1-Hourly2-GP2 --cloud aws --master-image=137112412989/amzn2-ami-hvm-2.0.20200617.0-x86_64-gp2 --override spec.docker.selinuxEnabled=true,cluster.spec.nodePortAccess=0.0.0.0/0 --yes
I1012 07:12:11.076069     988 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1012 07:12:11.100991     988 create_cluster.go:838] Using SSH public key: /workspace/.ssh/kube_aws_rsa.pub
I1012 07:12:11.594912     988 new_cluster.go:1077]  Cloud Provider ID = aws
... skipping 31 lines ...

2021/10/12 07:12:40 process.go:155: Step '/tmp/kops4054548213/kops create cluster --name e2e-kops-aws-k8s-storage-selinux.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/k8s-release-dev/ci/v1.23.0-alpha.3.278+a7c67c03ff09c2 --admin-access 34.68.52.185/32 --image 309956199498/RHEL-7.8_HVM_GA-20200225-x86_64-1-Hourly2-GP2 --cloud aws --master-image=137112412989/amzn2-ami-hvm-2.0.20200617.0-x86_64-gp2 --override spec.docker.selinuxEnabled=true,cluster.spec.nodePortAccess=0.0.0.0/0 --yes' finished in 29.397623517s
2021/10/12 07:12:40 process.go:153: Running: /tmp/kops4054548213/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m
I1012 07:12:40.475168    1010 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io

W1012 07:12:42.022760    1010 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-aws-k8s-storage-selinux.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-ap-northeast-2a	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
W1012 07:12:52.055034    1010 validate_cluster.go:232] (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-ap-northeast-2a	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
W1012 07:13:02.091440    1010 validate_cluster.go:232] (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-ap-northeast-2a	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
W1012 07:13:12.127751    1010 validate_cluster.go:232] (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-ap-northeast-2a	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
W1012 07:13:22.159560    1010 validate_cluster.go:232] (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-ap-northeast-2a	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
W1012 07:13:32.188962    1010 validate_cluster.go:232] (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-ap-northeast-2a	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
W1012 07:13:42.233138    1010 validate_cluster.go:232] (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-ap-northeast-2a	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
W1012 07:13:52.264460    1010 validate_cluster.go:232] (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-ap-northeast-2a	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
W1012 07:14:02.302650    1010 validate_cluster.go:232] (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-ap-northeast-2a	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
W1012 07:14:12.347169    1010 validate_cluster.go:232] (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-ap-northeast-2a	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
W1012 07:14:22.380243    1010 validate_cluster.go:232] (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-ap-northeast-2a	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
W1012 07:14:32.410864    1010 validate_cluster.go:232] (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-ap-northeast-2a	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
W1012 07:14:42.440691    1010 validate_cluster.go:232] (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-ap-northeast-2a	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
W1012 07:14:52.504428    1010 validate_cluster.go:232] (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-ap-northeast-2a	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
W1012 07:15:02.574143    1010 validate_cluster.go:232] (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-ap-northeast-2a	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
W1012 07:15:12.608795    1010 validate_cluster.go:232] (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-ap-northeast-2a	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
W1012 07:15:22.674999    1010 validate_cluster.go:232] (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-ap-northeast-2a	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
W1012 07:15:32.706666    1010 validate_cluster.go:232] (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-ap-northeast-2a	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
W1012 07:15:42.740922    1010 validate_cluster.go:232] (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-ap-northeast-2a	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
W1012 07:15:52.777351    1010 validate_cluster.go:232] (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-ap-northeast-2a	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
W1012 07:16:02.813103    1010 validate_cluster.go:232] (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-ap-northeast-2a	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
W1012 07:16:12.847589    1010 validate_cluster.go:232] (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-ap-northeast-2a	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
W1012 07:16:22.882047    1010 validate_cluster.go:232] (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-ap-northeast-2a	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
W1012 07:16:32.915768    1010 validate_cluster.go:232] (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-ap-northeast-2a	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
W1012 07:16:42.949136    1010 validate_cluster.go:232] (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-ap-northeast-2a	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
W1012 07:16:53.005451    1010 validate_cluster.go:232] (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-ap-northeast-2a	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
W1012 07:17:03.039574    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
W1012 07:17:43.086166    1010 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://api.e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 203.0.113.123:443: i/o timeout
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
... skipping 7 lines ...
Machine	i-09d17b2c7754915cb					machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1					machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Node	ip-172-20-59-221.ap-northeast-2.compute.internal	master "ip-172-20-59-221.ap-northeast-2.compute.internal" is missing kube-scheduler pod
Pod	kube-system/coredns-6c8944dbdc-hrhvs			system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:17:57.291355    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:18:10.213187    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:18:23.091217    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:18:35.823017    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:18:48.730559    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:19:01.409188    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:19:14.079134    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:19:26.841812    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:19:39.624811    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:19:52.412239    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:20:05.112619    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:20:17.879512    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:20:30.571613    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:20:43.387089    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:20:56.119769    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:21:08.932994    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:21:21.636381    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:21:34.380660    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:21:47.642094    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:22:00.384261    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:22:13.123807    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:22:25.728001    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:22:38.445387    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:22:51.051902    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:23:03.710336    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:23:16.415352    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:23:29.557878    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:23:42.232450    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:23:54.824762    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:24:07.506526    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:24:20.138725    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:24:32.875632    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:24:45.570379    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:24:58.250945    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:25:10.849865    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:25:23.550219    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:25:36.399087    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:25:49.545028    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:26:02.331547    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:26:15.078541    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:26:27.761192    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:26:40.353015    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:26:53.112614    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:27:05.857131    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:27:18.590589    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:27:31.324649    1010 validate_cluster.go:232] (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-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-0500ab7d307cd36c6				machine "i-0500ab7d307cd36c6" has not yet joined cluster
Machine	i-09d17b2c7754915cb				machine "i-09d17b2c7754915cb" has not yet joined cluster
Machine	i-0fca3c7f8be6051d1				machine "i-0fca3c7f8be6051d1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-hrhvs		system-cluster-critical pod "coredns-6c8944dbdc-hrhvs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-575hd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-575hd" is pending

Validation Failed
W1012 07:27:44.082114    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
2021/10/12 07:27:54 process.go:155: Step '/tmp/kops4054548213/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m' finished in 15m13.636180421s
2021/10/12 07:27:54 process.go:153: Running: kubectl -n kube-system get pods -ojson
2021/10/12 07:27:54 process.go:153: Running: /tmp/kops4054548213/kops toolbox dump --name e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io -ojson
I1012 07:27:54.127434    1024 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
2021/10/12 07:27:56 process.go:155: Step 'kubectl -n kube-system get pods -ojson' finished in 2.028875881s
2021/10/12 07:27:56 process.go:153: Running: kubectl -n kube-system logs --all-containers coredns-6c8944dbdc-hrhvs
... skipping 40 lines ...
2021/10/12 07:28:14 dump.go:413: Running SSH command: sudo cat /var/log/etcd.log
2021/10/12 07:28:14 dump.go:413: Running SSH command: sudo cat /var/log/etcd-events.log
2021/10/12 07:28:15 dump.go:413: Running SSH command: sudo cat /var/log/kube-proxy.log
2021/10/12 07:28:15 dump.go:413: Running SSH command: sudo cat /var/log/cloud-init-output.log
2021/10/12 07:28:15 dump.go:129: dumping node not registered in kubernetes: 3.35.48.84
2021/10/12 07:28:15 dump.go:163: Dumping node 3.35.48.84
2021/10/12 07:28:16 dump.go:132: error dumping node 3.35.48.84: could not connect: unable to SSH to "3.35.48.84": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/12 07:28:16 dump.go:129: dumping node not registered in kubernetes: 13.125.91.240
2021/10/12 07:28:16 dump.go:163: Dumping node 13.125.91.240
2021/10/12 07:28:18 dump.go:132: error dumping node 13.125.91.240: could not connect: unable to SSH to "13.125.91.240": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/12 07:28:18 dump.go:129: dumping node not registered in kubernetes: 13.125.226.86
2021/10/12 07:28:18 dump.go:163: Dumping node 13.125.226.86
2021/10/12 07:28:19 dump.go:132: error dumping node 13.125.226.86: could not connect: unable to SSH to "13.125.226.86": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/12 07:28:19 dump.go:129: dumping node not registered in kubernetes: 13.124.237.156
2021/10/12 07:28:19 dump.go:163: Dumping node 13.124.237.156
2021/10/12 07:28:20 dump.go:132: error dumping node 13.124.237.156: could not connect: unable to SSH to "13.124.237.156": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/12 07:28:20 process.go:153: Running: /tmp/kops4054548213/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io
I1012 07:28:20.712524    1167 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
NAME							CLOUD	ZONES
e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io	aws	ap-northeast-2a
2021/10/12 07:28:21 process.go:155: Step '/tmp/kops4054548213/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 595.593278ms
2021/10/12 07:28:21 process.go:153: Running: /tmp/kops4054548213/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes
... skipping 168 lines ...
dhcp-options:dopt-03235ea0c47560011	ok
Deleted kubectl config for e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io

Deleted cluster: "e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io"
2021/10/12 07:29:34 process.go:155: Step '/tmp/kops4054548213/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes' finished in 1m13.45115689s
2021/10/12 07:29:34 process.go:96: Saved XML output to /logs/artifacts/junit_runner.xml.
2021/10/12 07:29:34 main.go:331: Something went wrong: starting e2e cluster: kops validate cluster failed: error during /tmp/kops4054548213/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m: exit status 1
Traceback (most recent call last):
  File "/workspace/scenarios/kubernetes_e2e.py", line 723, in <module>
    main(parse_args())
  File "/workspace/scenarios/kubernetes_e2e.py", line 569, in main
    mode.start(runner_args)
  File "/workspace/scenarios/kubernetes_e2e.py", line 228, in start
... skipping 9 lines ...