This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 5 succeeded
Started2020-09-10 19:03
Elapsed18m24s
Revision
job-versionv1.17.11
revisionv1.17.11

Test Failures


Up 15m26s

kops validate cluster failed: error during /tmp/kops669722338/kops validate cluster e2e-kops-kopeio-flatcar-k17-ko18.test-cncf-aws.k8s.io --wait 15m: exit status 1
				from junit_runner.xml

Filter through log files


Show 5 Passed Tests

Error lines from build-log.txt

Activated service account credentials for: [pr-kubekins@kubernetes-jenkins-pull.iam.gserviceaccount.com]
fatal: not a git repository (or any of the parent directories): .git
+ /workspace/scenarios/kubernetes_e2e.py --cluster=e2e-kops-kopeio-flatcar-k17-ko18.test-cncf-aws.k8s.io --deployment=kops --kops-ssh-user=core --env=KUBE_SSH_USER=core --env=KOPS_DEPLOY_LATEST_URL=https://storage.googleapis.com/kubernetes-release/release/stable-1.17.txt --env=KOPS_KUBE_RELEASE_URL=https://storage.googleapis.com/kubernetes-release/release --env=KOPS_RUN_TOO_NEW_VERSION=1 --extract=release/stable-1.17 --ginkgo-parallel --kops-args=--networking=kopeio --kops-image=075585003325/Flatcar-stable-2512.2.0-hvm --kops-priority-path=/workspace/kubernetes/platforms/linux/amd64 --kops-version=https://storage.googleapis.com/kops-ci/markers/release-1.18/latest-ci-updown-green.txt --provider=aws '--test_args=--ginkgo.skip=\[Slow\]|\[Serial\]|\[Disruptive\]|\[Flaky\]|\[Feature:.+\]|\[HPA\]|Dashboard|Services.*functioning.*NodePort|Services.*rejected.*endpoints|Services.*affinity' --timeout=60m
starts with local mode
Environment:
ARTIFACTS=/logs/artifacts
AWS_DEFAULT_PROFILE=default
AWS_PROFILE=default
... skipping 153 lines ...
2020/09/10 19:04:55 process.go:153: Running: /tmp/kops669722338/kops delete cluster e2e-kops-kopeio-flatcar-k17-ko18.test-cncf-aws.k8s.io --yes
No cloud resources to delete

Deleted cluster: "e2e-kops-kopeio-flatcar-k17-ko18.test-cncf-aws.k8s.io"
2020/09/10 19:05:12 process.go:155: Step '/tmp/kops669722338/kops delete cluster e2e-kops-kopeio-flatcar-k17-ko18.test-cncf-aws.k8s.io --yes' finished in 17.147095162s
2020/09/10 19:05:12 util.go:42: curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2020/09/10 19:05:12 kops.go:514: failed to get external ip from metadata service: http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip returned 404
2020/09/10 19:05:12 util.go:68: curl https://ip.jsb.workers.dev
2020/09/10 19:05:12 kops.go:439: Using external IP for admin access: 35.202.85.104/32
2020/09/10 19:05:12 process.go:153: Running: /tmp/kops669722338/kops create cluster --name e2e-kops-kopeio-flatcar-k17-ko18.test-cncf-aws.k8s.io --ssh-public-key /workspace/.ssh/kube_aws_rsa.pub --node-count 4 --node-volume-size 48 --master-volume-size 48 --master-count 1 --zones ca-central-1a --master-size c5.large --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.17.11 --admin-access 35.202.85.104/32 --image 075585003325/Flatcar-stable-2512.2.0-hvm --cloud aws --networking=kopeio --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes
I0910 19:05:13.058978     177 featureflag.go:154] FeatureFlag "SpecOverrideFlag"=true
I0910 19:05:13.168929     177 create_cluster.go:1537] Using SSH public key: /workspace/.ssh/kube_aws_rsa.pub
I0910 19:05:14.025875     177 subnets.go:184] Assigned CIDR 172.20.32.0/19 to subnet ca-central-1a
... skipping 47 lines ...

2020/09/10 19:05:36 process.go:155: Step '/tmp/kops669722338/kops create cluster --name e2e-kops-kopeio-flatcar-k17-ko18.test-cncf-aws.k8s.io --ssh-public-key /workspace/.ssh/kube_aws_rsa.pub --node-count 4 --node-volume-size 48 --master-volume-size 48 --master-count 1 --zones ca-central-1a --master-size c5.large --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.17.11 --admin-access 35.202.85.104/32 --image 075585003325/Flatcar-stable-2512.2.0-hvm --cloud aws --networking=kopeio --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes' finished in 23.758683849s
2020/09/10 19:05:36 process.go:153: Running: /tmp/kops669722338/kops validate cluster e2e-kops-kopeio-flatcar-k17-ko18.test-cncf-aws.k8s.io --wait 15m
I0910 19:05:36.819615     209 featureflag.go:154] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-kops-kopeio-flatcar-k17-ko18.test-cncf-aws.k8s.io

W0910 19:05:38.023032     209 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-kopeio-flatcar-k17-ko18.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0910 19:05:48.078085     209 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-kopeio-flatcar-k17-ko18.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0910 19:05:58.123711     209 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-kopeio-flatcar-k17-ko18.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-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
W0910 19:06:08.180338     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-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
W0910 19:06:18.226009     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-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
W0910 19:06:28.268772     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-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
W0910 19:06:38.323919     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-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
W0910 19:06:48.389120     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-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
W0910 19:06:58.447301     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-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
W0910 19:07:08.504970     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-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
W0910 19:07:18.545884     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-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
W0910 19:07:28.589318     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-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
W0910 19:07:38.633032     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-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
W0910 19:07:48.675465     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-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
W0910 19:07:58.716743     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-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
W0910 19:08:08.781353     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-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
W0910 19:08:18.827531     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-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
W0910 19:08:28.864953     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-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
W0910 19:08:38.921586     209 validate_cluster.go:221] (will retry): cluster not yet healthy
W0910 19:08:48.959574     209 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-kopeio-flatcar-k17-ko18.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-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
W0910 19:08:59.001670     209 validate_cluster.go:221] (will retry): cluster not yet healthy
W0910 19:09:09.039982     209 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-kopeio-flatcar-k17-ko18.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-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
W0910 19:09:19.087560     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-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
W0910 19:09:29.149456     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-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
W0910 19:09:39.227756     209 validate_cluster.go:221] (will retry): cluster not yet healthy
W0910 19:09:49.270968     209 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-kopeio-flatcar-k17-ko18.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

NODE STATUS
... skipping 8 lines ...
Machine	i-0fcdb35d154e332d4							machine "i-0fcdb35d154e332d4" has not yet joined cluster
Pod	kube-system/kopeio-networking-agent-kzldx				system-node-critical pod "kopeio-networking-agent-kzldx" is pending
Pod	kube-system/kube-dns-5c594c474c-p7gjk					system-cluster-critical pod "kube-dns-5c594c474c-p7gjk" is pending
Pod	kube-system/kube-dns-autoscaler-b48d96894-zjlwr				system-cluster-critical pod "kube-dns-autoscaler-b48d96894-zjlwr" is pending
Pod	kube-system/kube-proxy-ip-172-20-48-146.ca-central-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-48-146.ca-central-1.compute.internal" is pending

Validation Failed
W0910 19:10:00.265075     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/kube-dns-5c594c474c-mbp5m	system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is pending
Pod	kube-system/kube-dns-5c594c474c-p7gjk	system-cluster-critical pod "kube-dns-5c594c474c-p7gjk" is pending

Validation Failed
W0910 19:10:11.041891     209 validate_cluster.go:221] (will retry): cluster not yet healthy
W0910 19:10:21.087691     209 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-kopeio-flatcar-k17-ko18.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0910 19:10:31.118820     209 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-kopeio-flatcar-k17-ko18.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

NODE STATUS
... skipping 7 lines ...
VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-dns-5c594c474c-mbp5m					system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns)
Pod	kube-system/kube-proxy-ip-172-20-34-232.ca-central-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-232.ca-central-1.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-51-142.ca-central-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-51-142.ca-central-1.compute.internal" is pending

Validation Failed
W0910 19:10:41.752093     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

... skipping 6 lines ...
ip-172-20-57-226.ca-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/kube-dns-5c594c474c-mbp5m	system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns)

Validation Failed
W0910 19:10:52.356499     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Node	ip-172-20-48-146.ca-central-1.compute.internal	node "ip-172-20-48-146.ca-central-1.compute.internal" is not ready
Pod	kube-system/kube-dns-5c594c474c-mbp5m		system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns)

Validation Failed
W0910 19:11:02.938955     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

... skipping 6 lines ...
ip-172-20-57-226.ca-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/kube-dns-5c594c474c-mbp5m	system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns)

Validation Failed
W0910 19:11:13.545119     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

... skipping 6 lines ...
ip-172-20-57-226.ca-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/kube-dns-5c594c474c-mbp5m	system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns)

Validation Failed
W0910 19:11:24.117099     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

... skipping 6 lines ...
ip-172-20-57-226.ca-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/kube-dns-5c594c474c-mbp5m	system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns)

Validation Failed
W0910 19:11:34.734070     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

... skipping 6 lines ...
ip-172-20-57-226.ca-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/kube-dns-5c594c474c-mbp5m	system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns)

Validation Failed
W0910 19:11:45.346092     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

... skipping 6 lines ...
ip-172-20-57-226.ca-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/kube-dns-5c594c474c-mbp5m	system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns)

Validation Failed
W0910 19:11:55.995249     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

... skipping 6 lines ...
ip-172-20-57-226.ca-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/kube-dns-5c594c474c-mbp5m	system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns)

Validation Failed
W0910 19:12:06.655868     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

... skipping 6 lines ...
ip-172-20-57-226.ca-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/kube-dns-5c594c474c-mbp5m	system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns)

Validation Failed
W0910 19:12:17.391463     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

... skipping 6 lines ...
ip-172-20-57-226.ca-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/kube-dns-5c594c474c-mbp5m	system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns)

Validation Failed
W0910 19:12:28.044869     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

... skipping 6 lines ...
ip-172-20-57-226.ca-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/kube-dns-5c594c474c-mbp5m	system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns)

Validation Failed
W0910 19:12:38.597017     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

... skipping 6 lines ...
ip-172-20-57-226.ca-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/kube-dns-5c594c474c-mbp5m	system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns)

Validation Failed
W0910 19:12:49.216966     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

... skipping 6 lines ...
ip-172-20-57-226.ca-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/kube-dns-5c594c474c-mbp5m	system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns)

Validation Failed
W0910 19:12:59.901729     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

... skipping 6 lines ...
ip-172-20-57-226.ca-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/kube-dns-5c594c474c-mbp5m	system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns)

Validation Failed
W0910 19:13:10.563867     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Node	ip-172-20-57-226.ca-central-1.compute.internal	node "ip-172-20-57-226.ca-central-1.compute.internal" is not ready
Pod	kube-system/kube-dns-5c594c474c-mbp5m		system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns)

Validation Failed
W0910 19:13:21.216887     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/kube-dns-5c594c474c-mbp5m	system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns)
Pod	kube-system/kube-dns-5c594c474c-p7gjk	system-cluster-critical pod "kube-dns-5c594c474c-p7gjk" is not ready (kubedns)

Validation Failed
W0910 19:13:31.853429     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/kube-dns-5c594c474c-mbp5m	system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns)
Pod	kube-system/kube-dns-5c594c474c-p7gjk	system-cluster-critical pod "kube-dns-5c594c474c-p7gjk" is not ready (kubedns)

Validation Failed
W0910 19:13:42.390049     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/kube-dns-5c594c474c-mbp5m	system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns)
Pod	kube-system/kube-dns-5c594c474c-p7gjk	system-cluster-critical pod "kube-dns-5c594c474c-p7gjk" is not ready (kubedns)

Validation Failed
W0910 19:13:53.280780     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

... skipping 6 lines ...
ip-172-20-57-226.ca-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/kube-dns-5c594c474c-mbp5m	system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns)

Validation Failed
W0910 19:14:03.887652     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

... skipping 6 lines ...
ip-172-20-57-226.ca-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/kube-dns-5c594c474c-mbp5m	system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns)

Validation Failed
W0910 19:14:14.489464     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

... skipping 6 lines ...
ip-172-20-57-226.ca-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/kube-dns-5c594c474c-mbp5m	system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns)

Validation Failed
W0910 19:14:25.128725     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

... skipping 6 lines ...
ip-172-20-57-226.ca-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/kube-dns-5c594c474c-mbp5m	system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns)

Validation Failed
W0910 19:14:35.749043     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

... skipping 6 lines ...
ip-172-20-57-226.ca-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/kube-dns-5c594c474c-mbp5m	system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns)

Validation Failed
W0910 19:14:46.392414     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

... skipping 6 lines ...
ip-172-20-57-226.ca-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/kube-dns-5c594c474c-mbp5m	system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns)

Validation Failed
W0910 19:14:57.035994     209 validate_cluster.go:221] (will retry): cluster not yet healthy
W0910 19:15:07.160783     209 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get https://api.e2e-kops-kopeio-flatcar-k17-ko18.test-cncf-aws.k8s.io/api/v1/nodes: dial tcp 35.182.253.47:443: connect: connection refused
W0910 19:15:32.640270     209 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get https://api.e2e-kops-kopeio-flatcar-k17-ko18.test-cncf-aws.k8s.io/api/v1/nodes: dial tcp 35.182.253.47:443: connect: connection refused
W0910 19:15:42.754500     209 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get https://api.e2e-kops-kopeio-flatcar-k17-ko18.test-cncf-aws.k8s.io/api/v1/nodes: dial tcp 35.182.253.47:443: connect: connection refused
W0910 19:15:52.940933     209 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get https://api.e2e-kops-kopeio-flatcar-k17-ko18.test-cncf-aws.k8s.io/api/v1/nodes: dial tcp 35.182.253.47:443: connect: connection refused
W0910 19:16:03.021266     209 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get https://api.e2e-kops-kopeio-flatcar-k17-ko18.test-cncf-aws.k8s.io/api/v1/nodes: dial tcp 35.182.253.47:443: connect: connection refused
W0910 19:16:13.171305     209 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get https://api.e2e-kops-kopeio-flatcar-k17-ko18.test-cncf-aws.k8s.io/api/v1/nodes: dial tcp 35.182.253.47:443: connect: connection refused
W0910 19:16:23.275202     209 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get https://api.e2e-kops-kopeio-flatcar-k17-ko18.test-cncf-aws.k8s.io/api/v1/nodes: dial tcp 35.182.253.47:443: connect: connection refused
W0910 19:16:33.391483     209 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get https://api.e2e-kops-kopeio-flatcar-k17-ko18.test-cncf-aws.k8s.io/api/v1/nodes: dial tcp 35.182.253.47:443: connect: connection refused
W0910 19:16:43.517096     209 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get https://api.e2e-kops-kopeio-flatcar-k17-ko18.test-cncf-aws.k8s.io/api/v1/nodes: dial tcp 35.182.253.47:443: connect: connection refused
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

NODE STATUS
... skipping 5 lines ...
ip-172-20-57-226.ca-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/kube-dns-5c594c474c-mbp5m	system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns)

Validation Failed
W0910 19:16:56.230718     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

... skipping 6 lines ...
ip-172-20-57-226.ca-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/kube-dns-5c594c474c-mbp5m	system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns)

Validation Failed
W0910 19:17:06.853340     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

... skipping 6 lines ...
ip-172-20-57-226.ca-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/kube-dns-5c594c474c-mbp5m	system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns)

Validation Failed
W0910 19:17:17.488497     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

... skipping 6 lines ...
ip-172-20-57-226.ca-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/kube-dns-5c594c474c-mbp5m	system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns)

Validation Failed
W0910 19:17:28.084468     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

... skipping 6 lines ...
ip-172-20-57-226.ca-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/kube-dns-5c594c474c-mbp5m	system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns)

Validation Failed
W0910 19:17:38.735492     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

... skipping 6 lines ...
ip-172-20-57-226.ca-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/kube-dns-5c594c474c-mbp5m	system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns)

Validation Failed
W0910 19:17:49.372681     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

... skipping 6 lines ...
ip-172-20-57-226.ca-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/kube-dns-5c594c474c-mbp5m	system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns)

Validation Failed
W0910 19:17:59.991021     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

... skipping 6 lines ...
ip-172-20-57-226.ca-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/kube-dns-5c594c474c-mbp5m	system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns)

Validation Failed
W0910 19:18:10.587396     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

... skipping 6 lines ...
ip-172-20-57-226.ca-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/kube-dns-5c594c474c-mbp5m	system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns)

Validation Failed
W0910 19:18:21.203040     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

... skipping 6 lines ...
ip-172-20-57-226.ca-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/kube-dns-5c594c474c-mbp5m	system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns)

Validation Failed
W0910 19:18:31.812574     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

... skipping 6 lines ...
ip-172-20-57-226.ca-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/kube-dns-5c594c474c-mbp5m	system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns)

Validation Failed
W0910 19:18:42.395203     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

... skipping 6 lines ...
ip-172-20-57-226.ca-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/kube-dns-5c594c474c-mbp5m	system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns)

Validation Failed
W0910 19:18:53.016804     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

... skipping 6 lines ...
ip-172-20-57-226.ca-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/kube-dns-5c594c474c-mbp5m	system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns)

Validation Failed
W0910 19:19:03.663373     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

... skipping 6 lines ...
ip-172-20-57-226.ca-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/kube-dns-5c594c474c-mbp5m	system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns)

Validation Failed
W0910 19:19:14.323859     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

... skipping 6 lines ...
ip-172-20-57-226.ca-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/kube-dns-5c594c474c-mbp5m	system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns)

Validation Failed
W0910 19:19:24.912842     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

... skipping 6 lines ...
ip-172-20-57-226.ca-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/kube-dns-5c594c474c-mbp5m	system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns)

Validation Failed
W0910 19:19:35.516394     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

... skipping 6 lines ...
ip-172-20-57-226.ca-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/kube-dns-5c594c474c-mbp5m	system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns)

Validation Failed
W0910 19:19:46.184792     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

... skipping 6 lines ...
ip-172-20-57-226.ca-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/kube-dns-5c594c474c-mbp5m	system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns)

Validation Failed
W0910 19:19:56.841728     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

... skipping 6 lines ...
ip-172-20-57-226.ca-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/kube-dns-5c594c474c-mbp5m	system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns)

Validation Failed
W0910 19:20:07.489589     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

... skipping 6 lines ...
ip-172-20-57-226.ca-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/kube-dns-5c594c474c-mbp5m	system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns)

Validation Failed
W0910 19:20:18.145022     209 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes			Node	t3.medium	4	4	ca-central-1a

... skipping 6 lines ...
ip-172-20-57-226.ca-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/kube-dns-5c594c474c-mbp5m	system-cluster-critical pod "kube-dns-5c594c474c-mbp5m" is not ready (kubedns,sidecar)

Validation Failed
W0910 19:20:28.857046     209 validate_cluster.go:221] (will retry): cluster not yet healthy

Validation failed: wait time exceeded during validation
2020/09/10 19:20:38 process.go:155: Step '/tmp/kops669722338/kops validate cluster e2e-kops-kopeio-flatcar-k17-ko18.test-cncf-aws.k8s.io --wait 15m' finished in 15m2.165302148s
2020/09/10 19:20:38 process.go:153: Running: kubectl -n kube-system get pods -ojson -l k8s-app=kops-controller
2020/09/10 19:20:38 process.go:153: Running: /tmp/kops669722338/kops toolbox dump --name e2e-kops-kopeio-flatcar-k17-ko18.test-cncf-aws.k8s.io -ojson
I0910 19:20:38.993518     227 featureflag.go:154] FeatureFlag "SpecOverrideFlag"=true
2020/09/10 19:20:39 process.go:155: Step 'kubectl -n kube-system get pods -ojson -l k8s-app=kops-controller' finished in 822.567979ms
2020/09/10 19:20:39 process.go:153: Running: kubectl -n kube-system logs --all-containers kops-controller-86p62
... skipping 208 lines ...
dhcp-options:dopt-0524ab2f9c8221d00	ok
Deleted kubectl config for e2e-kops-kopeio-flatcar-k17-ko18.test-cncf-aws.k8s.io

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