This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 5 succeeded
Started2021-10-09 07:09
Elapsed18m42s
Revision
job-versionv1.23.0-alpha.3.249+80056f73a614b2
kubetest-version
revisionv1.23.0-alpha.3.249+80056f73a614b2

Test Failures


kubetest Up 15m34s

kops validate cluster failed: error during /tmp/kops501577758/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=31
+ wait 31
+ /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 156 lines ...
md5sum(kubernetes-test-linux-amd64.tar.gz)=f94333404bad0f981b14ecdee09cf682
sha512sum(kubernetes-test-linux-amd64.tar.gz)=f4a8b8b91044ed753e57bcfa93cf37c0426b62267c72868ec0f73e705152a097abefdc1790a8cde4ff240cc2c6d31ba64766660416aab65c6a830b4c28effdfb

Extracting /workspace/kubernetes/test/kubernetes-test-linux-amd64.tar.gz into /workspace/kubernetes/platforms/linux/amd64
2021/10/09 07:10:32 process.go:155: Step './get-kube.sh' finished in 47.862684364s
2021/10/09 07:10:32 process.go:153: Running: /tmp/kops501577758/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/09 07:10:32 process.go:155: Step '/tmp/kops501577758/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 680.669597ms
2021/10/09 07:10:32 util.go:42: curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/09 07:10:32 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/09 07:10:32 util.go:68: curl https://ip.jsb.workers.dev
2021/10/09 07:10:32 kops.go:439: Using external IP for admin access: 35.193.93.145/32
2021/10/09 07:10:32 process.go:153: Running: /tmp/kops501577758/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-southeast-1a --master-size c5.large --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.23.0-alpha.3.249+80056f73a614b2 --admin-access 35.193.93.145/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
I1009 07:10:33.007077     985 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1009 07:10:33.066862     985 create_cluster.go:838] Using SSH public key: /workspace/.ssh/kube_aws_rsa.pub
I1009 07:10:33.730457     985 new_cluster.go:1077]  Cloud Provider ID = aws
... skipping 31 lines ...

2021/10/09 07:11:03 process.go:155: Step '/tmp/kops501577758/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-southeast-1a --master-size c5.large --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.23.0-alpha.3.249+80056f73a614b2 --admin-access 35.193.93.145/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 30.974572646s
2021/10/09 07:11:03 process.go:153: Running: /tmp/kops501577758/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m
I1009 07:11:03.922119    1003 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io

W1009 07:11:05.561587    1003 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-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1009 07:11:15.612352    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1009 07:11:25.645235    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1009 07:11:35.677908    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1009 07:11:45.713794    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1009 07:11:55.741843    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1009 07:12:05.787925    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1009 07:12:15.821712    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1009 07:12:25.852930    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1009 07:12:35.882727    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1009 07:12:45.919991    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1009 07:12:55.952512    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1009 07:13:05.981162    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1009 07:13:16.013114    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1009 07:13:26.042710    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1009 07:13:36.070543    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
W1009 07:13:46.089692    1003 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-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1009 07:13:56.132304    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1009 07:14:06.162530    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1009 07:14:16.190712    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1009 07:14:26.324091    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1009 07:14:36.358332    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1009 07:14:46.396540    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1009 07:14:56.439025    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1009 07:15:06.471163    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1009 07:15:16.502564    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 8 lines ...
Machine	i-0877064ff454541b6					machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff					machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Node	ip-172-20-59-240.ap-southeast-1.compute.internal	master "ip-172-20-59-240.ap-southeast-1.compute.internal" is missing kube-scheduler pod
Pod	kube-system/coredns-5dc785954d-b454n			system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:15:31.397422    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:15:44.774775    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:15:57.926641    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:16:10.978021    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:16:24.125574    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:16:37.318450    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:16:50.426535    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:17:03.748370    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:17:17.326770    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:17:30.532401    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:17:43.881596    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:17:57.366636    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:18:10.662467    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:18:24.000684    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:18:37.239982    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:18:50.324561    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:19:03.550132    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:19:16.832554    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:19:30.643328    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:19:43.834668    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:19:56.982560    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:20:10.443891    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:20:23.727109    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:20:37.058823    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:20:50.317188    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:21:03.496375    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:21:16.887049    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:21:29.993047    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:21:43.425860    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:21:56.763623    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:22:10.156784    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:22:23.337377    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:22:36.492048    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:22:49.701005    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:23:02.806739    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:23:16.123633    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:23:30.110691    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:23:43.439235    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:23:56.555575    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:24:10.317506    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:24:23.782855    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:24:37.406344    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:24:50.815488    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:25:04.260239    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:25:17.618177    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:25:31.013861    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:25:44.191232    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 7 lines ...
Machine	i-0561e3821e14d3008				machine "i-0561e3821e14d3008" has not yet joined cluster
Machine	i-0877064ff454541b6				machine "i-0877064ff454541b6" has not yet joined cluster
Machine	i-0d0cbd87697c0e8ff				machine "i-0d0cbd87697c0e8ff" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-b454n		system-cluster-critical pod "coredns-5dc785954d-b454n" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f5rxz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f5rxz" is pending

Validation Failed
W1009 07:25:57.509287    1003 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
2021/10/09 07:26:07 process.go:155: Step '/tmp/kops501577758/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m' finished in 15m3.612846833s
2021/10/09 07:26:07 process.go:153: Running: kubectl -n kube-system get pods -ojson
2021/10/09 07:26:07 process.go:153: Running: /tmp/kops501577758/kops toolbox dump --name e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io -ojson
I1009 07:26:07.534858    1017 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
2021/10/09 07:26:09 process.go:155: Step 'kubectl -n kube-system get pods -ojson' finished in 2.078986756s
2021/10/09 07:26:09 process.go:153: Running: kubectl -n kube-system logs --all-containers coredns-5dc785954d-b454n
... skipping 40 lines ...
2021/10/09 07:26:31 dump.go:413: Running SSH command: sudo cat /var/log/etcd.log
2021/10/09 07:26:31 dump.go:413: Running SSH command: sudo cat /var/log/etcd-events.log
2021/10/09 07:26:31 dump.go:413: Running SSH command: sudo cat /var/log/kube-proxy.log
2021/10/09 07:26:32 dump.go:413: Running SSH command: sudo cat /var/log/cloud-init-output.log
2021/10/09 07:26:32 dump.go:129: dumping node not registered in kubernetes: 54.151.209.31
2021/10/09 07:26:32 dump.go:163: Dumping node 54.151.209.31
2021/10/09 07:26:34 dump.go:132: error dumping node 54.151.209.31: could not connect: unable to SSH to "54.151.209.31": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/09 07:26:34 dump.go:129: dumping node not registered in kubernetes: 13.212.177.220
2021/10/09 07:26:34 dump.go:163: Dumping node 13.212.177.220
2021/10/09 07:26:35 dump.go:132: error dumping node 13.212.177.220: could not connect: unable to SSH to "13.212.177.220": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/09 07:26:35 dump.go:129: dumping node not registered in kubernetes: 46.137.234.108
2021/10/09 07:26:35 dump.go:163: Dumping node 46.137.234.108
2021/10/09 07:26:36 dump.go:132: error dumping node 46.137.234.108: could not connect: unable to SSH to "46.137.234.108": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/09 07:26:36 dump.go:129: dumping node not registered in kubernetes: 13.212.204.158
2021/10/09 07:26:36 dump.go:163: Dumping node 13.212.204.158
2021/10/09 07:26:38 dump.go:132: error dumping node 13.212.204.158: could not connect: unable to SSH to "13.212.204.158": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/09 07:26:38 process.go:153: Running: /tmp/kops501577758/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io
I1009 07:26:38.655545    1161 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
NAME							CLOUD	ZONES
e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io	aws	ap-southeast-1a
2021/10/09 07:26:39 process.go:155: Step '/tmp/kops501577758/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 540.393223ms
2021/10/09 07:26:39 process.go:153: Running: /tmp/kops501577758/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes
... skipping 202 lines ...
dhcp-options:dopt-01881b1e6f1b0de5e	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/09 07:28:17 process.go:155: Step '/tmp/kops501577758/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes' finished in 1m38.060973315s
2021/10/09 07:28:17 process.go:96: Saved XML output to /logs/artifacts/junit_runner.xml.
2021/10/09 07:28:17 main.go:331: Something went wrong: starting e2e cluster: kops validate cluster failed: error during /tmp/kops501577758/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 ...