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

Test Failures


kubetest Up 15m33s

kops validate cluster failed: error during /tmp/kops2755668396/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=30
+ wait 30
+ /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)=07dfc25925249106a12c5021e458b565
sha512sum(kubernetes-test-linux-amd64.tar.gz)=ede05d2a7370ea0c1b1313c9b8b989f79c1517e07f8295d70bfe25b6ffa4c4f580421ee1c5f13f4b6f746583412e2c236aee49cc5be58c0130ff2b447b53cfee

Extracting /workspace/kubernetes/test/kubernetes-test-linux-amd64.tar.gz into /workspace/kubernetes/platforms/linux/amd64
2021/10/22 07:20:51 process.go:155: Step './get-kube.sh' finished in 29.146891446s
2021/10/22 07:20:51 process.go:153: Running: /tmp/kops2755668396/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/22 07:20:51 process.go:155: Step '/tmp/kops2755668396/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 493.833797ms
2021/10/22 07:20:51 util.go:42: curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/22 07:20:51 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/22 07:20:51 util.go:68: curl https://ip.jsb.workers.dev
2021/10/22 07:20:51 kops.go:439: Using external IP for admin access: 34.68.176.126/32
2021/10/22 07:20:51 process.go:153: Running: /tmp/kops2755668396/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-1c --master-size c5.large --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.23.0-alpha.3.479+cc25656b00baa3 --admin-access 34.68.176.126/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
I1022 07:20:51.866936     987 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1022 07:20:51.890149     987 create_cluster.go:838] Using SSH public key: /workspace/.ssh/kube_aws_rsa.pub
I1022 07:20:52.365986     987 new_cluster.go:1077]  Cloud Provider ID = aws
... skipping 31 lines ...

2021/10/22 07:21:19 process.go:155: Step '/tmp/kops2755668396/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-1c --master-size c5.large --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.23.0-alpha.3.479+cc25656b00baa3 --admin-access 34.68.176.126/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 27.897815245s
2021/10/22 07:21:19 process.go:153: Running: /tmp/kops2755668396/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m
I1022 07:21:19.767925    1009 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io

W1022 07:21:21.096490    1009 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-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

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
W1022 07:21:31.127265    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

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
W1022 07:21:41.163318    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

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
W1022 07:21:51.202614    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

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
W1022 07:22:01.235742    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

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
W1022 07:22:11.275777    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

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
W1022 07:22:21.323719    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

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
W1022 07:22:31.354537    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

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
W1022 07:22:41.386432    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

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
W1022 07:22:51.418331    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

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
W1022 07:23:01.471547    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

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
W1022 07:23:11.508532    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

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
W1022 07:23:21.543251    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

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
W1022 07:23:31.592640    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

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
W1022 07:23:41.644996    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

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
W1022 07:23:51.677045    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

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
W1022 07:24:01.715101    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

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
W1022 07:24:11.753108    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

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
W1022 07:24:21.786465    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

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
W1022 07:24:31.827126    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

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
W1022 07:24:41.860970    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

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
W1022 07:24:51.891860    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

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
W1022 07:25:01.927092    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

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
W1022 07:25:11.960968    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

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
W1022 07:25:21.995097    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

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
W1022 07:25:32.028085    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:25:45.498101    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:25:57.935343    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:26:10.336922    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
W1022 07:26:20.366885    1009 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-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

NODE STATUS
... skipping 6 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:26:32.746101    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:26:45.126006    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:26:57.486671    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:27:09.883945    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:27:22.230728    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:27:34.531215    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:27:46.959463    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:27:59.230473    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:28:11.478190    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:28:23.955429    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:28:36.237056    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:28:48.606539    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:29:01.017563    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:29:13.355165    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:29:25.715183    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:29:38.456137    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:29:50.703632    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:30:03.274269    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:30:15.648493    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:30:27.994926    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:30:40.341749    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:30:52.635638    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:31:05.135172    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:31:17.481524    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:31:29.832209    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:31:42.121295    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:31:54.504836    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:32:06.849916    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:32:19.255899    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:32:31.694633    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:32:44.118150    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:32:56.525710    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:33:08.859549    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:33:21.227167    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:33:34.002104    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:33:46.492011    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:33:58.838197    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:34:11.168493    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:34:23.488018    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:34:35.861061    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:34:48.179579    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:35:00.712416    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:35:12.969366    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:35:25.365568    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:35:37.769072    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:35:50.166512    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:36:02.472433    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 7 lines ...
Machine	i-036d46aab0a964a37				machine "i-036d46aab0a964a37" has not yet joined cluster
Machine	i-04834f35ef1826959				machine "i-04834f35ef1826959" has not yet joined cluster
Machine	i-0f38c7c3bae6f82e1				machine "i-0f38c7c3bae6f82e1" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r62qn		system-cluster-critical pod "coredns-6c8944dbdc-r62qn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cxkcf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cxkcf" is pending

Validation Failed
W1022 07:36:14.838691    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
2021/10/22 07:36:24 process.go:155: Step '/tmp/kops2755668396/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m' finished in 15m5.101584869s
2021/10/22 07:36:24 process.go:153: Running: kubectl -n kube-system get pods -ojson
2021/10/22 07:36:24 process.go:153: Running: /tmp/kops2755668396/kops toolbox dump --name e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io -ojson
I1022 07:36:24.902677    1021 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
2021/10/22 07:36:26 process.go:155: Step 'kubectl -n kube-system get pods -ojson' finished in 1.496644011s
2021/10/22 07:36:26 process.go:153: Running: kubectl -n kube-system logs --all-containers coredns-6c8944dbdc-r62qn
... skipping 40 lines ...
2021/10/22 07:36:44 dump.go:413: Running SSH command: sudo cat /var/log/etcd.log
2021/10/22 07:36:44 dump.go:413: Running SSH command: sudo cat /var/log/etcd-events.log
2021/10/22 07:36:45 dump.go:413: Running SSH command: sudo cat /var/log/kube-proxy.log
2021/10/22 07:36:45 dump.go:413: Running SSH command: sudo cat /var/log/cloud-init-output.log
2021/10/22 07:36:45 dump.go:129: dumping node not registered in kubernetes: 13.112.91.11
2021/10/22 07:36:45 dump.go:163: Dumping node 13.112.91.11
2021/10/22 07:36:46 dump.go:132: error dumping node 13.112.91.11: could not connect: unable to SSH to "13.112.91.11": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/22 07:36:46 dump.go:129: dumping node not registered in kubernetes: 18.183.86.0
2021/10/22 07:36:46 dump.go:163: Dumping node 18.183.86.0
2021/10/22 07:36:47 dump.go:132: error dumping node 18.183.86.0: could not connect: unable to SSH to "18.183.86.0": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/22 07:36:47 dump.go:129: dumping node not registered in kubernetes: 18.181.78.255
2021/10/22 07:36:47 dump.go:163: Dumping node 18.181.78.255
2021/10/22 07:36:48 dump.go:132: error dumping node 18.181.78.255: could not connect: unable to SSH to "18.181.78.255": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/22 07:36:48 dump.go:129: dumping node not registered in kubernetes: 3.112.50.163
2021/10/22 07:36:48 dump.go:163: Dumping node 3.112.50.163
2021/10/22 07:36:49 dump.go:132: error dumping node 3.112.50.163: could not connect: unable to SSH to "3.112.50.163": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/22 07:36:49 process.go:153: Running: /tmp/kops2755668396/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io
I1022 07:36:49.978673    1144 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
NAME							CLOUD	ZONES
e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io	aws	ap-northeast-1c
2021/10/22 07:36:50 process.go:155: Step '/tmp/kops2755668396/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 506.736991ms
2021/10/22 07:36:50 process.go:153: Running: /tmp/kops2755668396/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes
... skipping 192 lines ...
dhcp-options:dopt-05c3e204e51eeba35	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/22 07:38:15 process.go:155: Step '/tmp/kops2755668396/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes' finished in 1m24.834826758s
2021/10/22 07:38:15 process.go:96: Saved XML output to /logs/artifacts/junit_runner.xml.
2021/10/22 07:38:15 main.go:331: Something went wrong: starting e2e cluster: kops validate cluster failed: error during /tmp/kops2755668396/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 ...