This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 5 succeeded
Started2020-09-24 21:18
Elapsed19m4s
Revision
job-versionv1.16.15
revisionv1.16.15

Test Failures


Up 15m33s

kops validate cluster failed: error during /tmp/kops896168616/kops validate cluster e2e-kops-flanl-rhel8-k16-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-flanl-rhel8-k16-ko18.test-cncf-aws.k8s.io --deployment=kops --kops-ssh-user=ec2-user --env=KUBE_SSH_USER=ec2-user --env=KOPS_DEPLOY_LATEST_URL=https://storage.googleapis.com/kubernetes-release/release/stable-1.16.txt --env=KOPS_KUBE_RELEASE_URL=https://storage.googleapis.com/kubernetes-release/release --env=KOPS_RUN_TOO_NEW_VERSION=1 --extract=release/stable-1.16 --ginkgo-parallel --kops-args=--networking=flannel --kops-image=309956199498/RHEL-8.2.0_HVM-20200423-x86_64-0-Hourly2-GP2 --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 148 lines ...
2020/09/24 21:19:20 process.go:155: Step './get-kube.sh' finished in 18.455536967s
2020/09/24 21:19:20 process.go:153: Running: /tmp/kops896168616/kops get clusters e2e-kops-flanl-rhel8-k16-ko18.test-cncf-aws.k8s.io

cluster not found "e2e-kops-flanl-rhel8-k16-ko18.test-cncf-aws.k8s.io"
2020/09/24 21:19:20 process.go:155: Step '/tmp/kops896168616/kops get clusters e2e-kops-flanl-rhel8-k16-ko18.test-cncf-aws.k8s.io' finished in 650.944097ms
2020/09/24 21:19:20 util.go:42: curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2020/09/24 21:19:20 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/24 21:19:20 util.go:68: curl https://ip.jsb.workers.dev
2020/09/24 21:19:21 kops.go:439: Using external IP for admin access: 35.239.212.76/32
2020/09/24 21:19:21 process.go:153: Running: /tmp/kops896168616/kops create cluster --name e2e-kops-flanl-rhel8-k16-ko18.test-cncf-aws.k8s.io --ssh-public-key /workspace/.ssh/kube_aws_rsa.pub --node-count 4 --node-volume-size 48 --master-volume-size 48 --master-count 1 --zones ap-northeast-2a --master-size c5.large --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.16.15 --admin-access 35.239.212.76/32 --image 309956199498/RHEL-8.2.0_HVM-20200423-x86_64-0-Hourly2-GP2 --cloud aws --networking=flannel --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes
I0924 21:19:21.112709     163 featureflag.go:154] FeatureFlag "SpecOverrideFlag"=true
I0924 21:19:21.168707     163 create_cluster.go:1537] Using SSH public key: /workspace/.ssh/kube_aws_rsa.pub
I0924 21:19:22.435673     163 subnets.go:184] Assigned CIDR 172.20.32.0/19 to subnet ap-northeast-2a
... skipping 47 lines ...

2020/09/24 21:19:46 process.go:155: Step '/tmp/kops896168616/kops create cluster --name e2e-kops-flanl-rhel8-k16-ko18.test-cncf-aws.k8s.io --ssh-public-key /workspace/.ssh/kube_aws_rsa.pub --node-count 4 --node-volume-size 48 --master-volume-size 48 --master-count 1 --zones ap-northeast-2a --master-size c5.large --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.16.15 --admin-access 35.239.212.76/32 --image 309956199498/RHEL-8.2.0_HVM-20200423-x86_64-0-Hourly2-GP2 --cloud aws --networking=flannel --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes' finished in 25.404376153s
2020/09/24 21:19:46 process.go:153: Running: /tmp/kops896168616/kops validate cluster e2e-kops-flanl-rhel8-k16-ko18.test-cncf-aws.k8s.io --wait 15m
I0924 21:19:46.515442     194 featureflag.go:154] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-kops-flanl-rhel8-k16-ko18.test-cncf-aws.k8s.io

W0924 21:19:48.349255     194 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-flanl-rhel8-k16-ko18.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0924 21:19:58.393273     194 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-flanl-rhel8-k16-ko18.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0924 21:20:08.444106     194 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-flanl-rhel8-k16-ko18.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0924 21:20:18.494804     194 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-flanl-rhel8-k16-ko18.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0924 21:20:28.533553     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0924 21:20:38.565952     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0924 21:20:48.631017     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0924 21:20:58.689029     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0924 21:21:38.888283     194 validate_cluster.go:221] (will retry): cluster not yet healthy
W0924 21:21:48.921235     194 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-flanl-rhel8-k16-ko18.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0924 21:21:58.959841     194 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-flanl-rhel8-k16-ko18.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0924 21:23:49.527143     194 validate_cluster.go:221] (will retry): cluster not yet healthy
W0924 21:23:59.562481     194 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-flanl-rhel8-k16-ko18.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0924 21:24:09.597780     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0924 21:24:19.637260     194 validate_cluster.go:221] (will retry): cluster not yet healthy
W0924 21:24:29.678686     194 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-flanl-rhel8-k16-ko18.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0924 21:24:39.734544     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0924 21:24:49.793885     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0924 21:24:59.857580     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0924 21:25:09.926977     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0924 21:25:19.965790     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0924 21:25:30.008193     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0924 21:25:40.041456     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0924 21:25:50.089720     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0924 21:26:00.162965     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0924 21:26:10.226408     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 8 lines ...
Machine	i-09c3a2f12342b7ba2				machine "i-09c3a2f12342b7ba2" has not yet joined cluster
Machine	i-0d46daf8a949ffd84				machine "i-0d46daf8a949ffd84" has not yet joined cluster
Pod	kube-system/kube-dns-5c594c474c-mb76x		system-cluster-critical pod "kube-dns-5c594c474c-mb76x" is pending
Pod	kube-system/kube-dns-autoscaler-b48d96894-lqnhq	system-cluster-critical pod "kube-dns-autoscaler-b48d96894-lqnhq" is pending
Pod	kube-system/kube-flannel-ds-tjrpx		system-node-critical pod "kube-flannel-ds-tjrpx" is pending

Validation Failed
W0924 21:26:23.104070     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 13 lines ...
Pod	kube-system/kube-dns-5c594c474c-mb76x					system-cluster-critical pod "kube-dns-5c594c474c-mb76x" is pending
Pod	kube-system/kube-dns-autoscaler-b48d96894-lqnhq				system-cluster-critical pod "kube-dns-autoscaler-b48d96894-lqnhq" is pending
Pod	kube-system/kube-flannel-ds-gwj84					system-node-critical pod "kube-flannel-ds-gwj84" is pending
Pod	kube-system/kube-flannel-ds-qtd2m					system-node-critical pod "kube-flannel-ds-qtd2m" is pending
Pod	kube-system/kube-proxy-ip-172-20-51-207.ap-northeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-51-207.ap-northeast-2.compute.internal" is pending

Validation Failed
W0924 21:26:35.118529     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 8 lines ...
KIND	NAME							MESSAGE
Machine	i-0d46daf8a949ffd84					machine "i-0d46daf8a949ffd84" has not yet joined cluster
Node	ip-172-20-51-207.ap-northeast-2.compute.internal	node "ip-172-20-51-207.ap-northeast-2.compute.internal" is not ready
Pod	kube-system/kube-dns-5c594c474c-mb76x			system-cluster-critical pod "kube-dns-5c594c474c-mb76x" is pending
Pod	kube-system/kube-dns-autoscaler-b48d96894-lqnhq		system-cluster-critical pod "kube-dns-autoscaler-b48d96894-lqnhq" is pending

Validation Failed
W0924 21:26:47.058611     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 8 lines ...
KIND	NAME									MESSAGE
Machine	i-0d46daf8a949ffd84							machine "i-0d46daf8a949ffd84" has not yet joined cluster
Pod	kube-system/kube-dns-5c594c474c-mb76x					system-cluster-critical pod "kube-dns-5c594c474c-mb76x" is pending
Pod	kube-system/kube-dns-autoscaler-b48d96894-lqnhq				system-cluster-critical pod "kube-dns-autoscaler-b48d96894-lqnhq" is pending
Pod	kube-system/kube-proxy-ip-172-20-35-117.ap-northeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-35-117.ap-northeast-2.compute.internal" is pending

Validation Failed
W0924 21:26:58.958973     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 8 lines ...
KIND	NAME						MESSAGE
Machine	i-0d46daf8a949ffd84				machine "i-0d46daf8a949ffd84" has not yet joined cluster
Pod	kube-system/kube-dns-5c594c474c-mb76x		system-cluster-critical pod "kube-dns-5c594c474c-mb76x" is pending
Pod	kube-system/kube-dns-5c594c474c-pzl6n		system-cluster-critical pod "kube-dns-5c594c474c-pzl6n" is pending
Pod	kube-system/kube-dns-autoscaler-b48d96894-lqnhq	system-cluster-critical pod "kube-dns-autoscaler-b48d96894-lqnhq" is pending

Validation Failed
W0924 21:27:10.805353     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
VALIDATION ERRORS
KIND	NAME					MESSAGE
Machine	i-0d46daf8a949ffd84			machine "i-0d46daf8a949ffd84" has not yet joined cluster
Pod	kube-system/kube-dns-5c594c474c-mb76x	system-cluster-critical pod "kube-dns-5c594c474c-mb76x" is not ready (kubedns)
Pod	kube-system/kube-dns-5c594c474c-pzl6n	system-cluster-critical pod "kube-dns-5c594c474c-pzl6n" is not ready (kubedns)

Validation Failed
W0924 21:27:22.690045     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-58-214.ap-northeast-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0d46daf8a949ffd84	machine "i-0d46daf8a949ffd84" has not yet joined cluster

Validation Failed
W0924 21:27:34.664116     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-58-214.ap-northeast-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0d46daf8a949ffd84	machine "i-0d46daf8a949ffd84" has not yet joined cluster

Validation Failed
W0924 21:27:46.505433     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-58-214.ap-northeast-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0d46daf8a949ffd84	machine "i-0d46daf8a949ffd84" has not yet joined cluster

Validation Failed
W0924 21:27:58.398697     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-58-214.ap-northeast-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0d46daf8a949ffd84	machine "i-0d46daf8a949ffd84" has not yet joined cluster

Validation Failed
W0924 21:28:10.233863     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-58-214.ap-northeast-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0d46daf8a949ffd84	machine "i-0d46daf8a949ffd84" has not yet joined cluster

Validation Failed
W0924 21:28:22.148289     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-58-214.ap-northeast-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0d46daf8a949ffd84	machine "i-0d46daf8a949ffd84" has not yet joined cluster

Validation Failed
W0924 21:28:34.004654     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-58-214.ap-northeast-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0d46daf8a949ffd84	machine "i-0d46daf8a949ffd84" has not yet joined cluster

Validation Failed
W0924 21:28:45.885483     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-58-214.ap-northeast-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0d46daf8a949ffd84	machine "i-0d46daf8a949ffd84" has not yet joined cluster

Validation Failed
W0924 21:28:57.701755     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-58-214.ap-northeast-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0d46daf8a949ffd84	machine "i-0d46daf8a949ffd84" has not yet joined cluster

Validation Failed
W0924 21:29:09.611898     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-58-214.ap-northeast-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0d46daf8a949ffd84	machine "i-0d46daf8a949ffd84" has not yet joined cluster

Validation Failed
W0924 21:29:21.461675     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-58-214.ap-northeast-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0d46daf8a949ffd84	machine "i-0d46daf8a949ffd84" has not yet joined cluster

Validation Failed
W0924 21:29:33.377288     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-58-214.ap-northeast-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0d46daf8a949ffd84	machine "i-0d46daf8a949ffd84" has not yet joined cluster

Validation Failed
W0924 21:29:45.217969     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-58-214.ap-northeast-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0d46daf8a949ffd84	machine "i-0d46daf8a949ffd84" has not yet joined cluster

Validation Failed
W0924 21:29:57.148579     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-58-214.ap-northeast-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0d46daf8a949ffd84	machine "i-0d46daf8a949ffd84" has not yet joined cluster

Validation Failed
W0924 21:30:09.035449     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-58-214.ap-northeast-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0d46daf8a949ffd84	machine "i-0d46daf8a949ffd84" has not yet joined cluster

Validation Failed
W0924 21:30:21.430631     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-58-214.ap-northeast-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0d46daf8a949ffd84	machine "i-0d46daf8a949ffd84" has not yet joined cluster

Validation Failed
W0924 21:30:33.355129     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-58-214.ap-northeast-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0d46daf8a949ffd84	machine "i-0d46daf8a949ffd84" has not yet joined cluster

Validation Failed
W0924 21:30:45.209663     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-58-214.ap-northeast-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0d46daf8a949ffd84	machine "i-0d46daf8a949ffd84" has not yet joined cluster

Validation Failed
W0924 21:30:57.103378     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-58-214.ap-northeast-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0d46daf8a949ffd84	machine "i-0d46daf8a949ffd84" has not yet joined cluster

Validation Failed
W0924 21:31:09.167015     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-58-214.ap-northeast-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0d46daf8a949ffd84	machine "i-0d46daf8a949ffd84" has not yet joined cluster

Validation Failed
W0924 21:31:21.004540     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-58-214.ap-northeast-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0d46daf8a949ffd84	machine "i-0d46daf8a949ffd84" has not yet joined cluster

Validation Failed
W0924 21:31:32.882559     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-58-214.ap-northeast-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0d46daf8a949ffd84	machine "i-0d46daf8a949ffd84" has not yet joined cluster

Validation Failed
W0924 21:31:44.730608     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-58-214.ap-northeast-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0d46daf8a949ffd84	machine "i-0d46daf8a949ffd84" has not yet joined cluster

Validation Failed
W0924 21:31:56.687148     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-58-214.ap-northeast-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0d46daf8a949ffd84	machine "i-0d46daf8a949ffd84" has not yet joined cluster

Validation Failed
W0924 21:32:08.589710     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-58-214.ap-northeast-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0d46daf8a949ffd84	machine "i-0d46daf8a949ffd84" has not yet joined cluster

Validation Failed
W0924 21:32:20.473913     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-58-214.ap-northeast-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0d46daf8a949ffd84	machine "i-0d46daf8a949ffd84" has not yet joined cluster

Validation Failed
W0924 21:32:32.468379     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-58-214.ap-northeast-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0d46daf8a949ffd84	machine "i-0d46daf8a949ffd84" has not yet joined cluster

Validation Failed
W0924 21:32:44.320639     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-58-214.ap-northeast-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0d46daf8a949ffd84	machine "i-0d46daf8a949ffd84" has not yet joined cluster

Validation Failed
W0924 21:32:56.206719     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-58-214.ap-northeast-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0d46daf8a949ffd84	machine "i-0d46daf8a949ffd84" has not yet joined cluster

Validation Failed
W0924 21:33:08.036128     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-58-214.ap-northeast-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0d46daf8a949ffd84	machine "i-0d46daf8a949ffd84" has not yet joined cluster

Validation Failed
W0924 21:33:19.957724     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-58-214.ap-northeast-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0d46daf8a949ffd84	machine "i-0d46daf8a949ffd84" has not yet joined cluster

Validation Failed
W0924 21:33:31.856272     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-58-214.ap-northeast-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0d46daf8a949ffd84	machine "i-0d46daf8a949ffd84" has not yet joined cluster

Validation Failed
W0924 21:33:43.887162     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-58-214.ap-northeast-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0d46daf8a949ffd84	machine "i-0d46daf8a949ffd84" has not yet joined cluster

Validation Failed
W0924 21:33:55.756226     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-58-214.ap-northeast-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0d46daf8a949ffd84	machine "i-0d46daf8a949ffd84" has not yet joined cluster

Validation Failed
W0924 21:34:07.808354     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-58-214.ap-northeast-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0d46daf8a949ffd84	machine "i-0d46daf8a949ffd84" has not yet joined cluster

Validation Failed
W0924 21:34:20.172549     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-58-214.ap-northeast-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0d46daf8a949ffd84	machine "i-0d46daf8a949ffd84" has not yet joined cluster

Validation Failed
W0924 21:34:32.097175     194 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes			Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-58-214.ap-northeast-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0d46daf8a949ffd84	machine "i-0d46daf8a949ffd84" has not yet joined cluster

Validation Failed
W0924 21:34:43.945909     194 validate_cluster.go:221] (will retry): cluster not yet healthy

Validation failed: wait time exceeded during validation
2020/09/24 21:34:53 process.go:155: Step '/tmp/kops896168616/kops validate cluster e2e-kops-flanl-rhel8-k16-ko18.test-cncf-aws.k8s.io --wait 15m' finished in 15m7.477295314s
2020/09/24 21:34:53 process.go:153: Running: kubectl -n kube-system get pods -ojson -l k8s-app=kops-controller
2020/09/24 21:34:53 process.go:153: Running: /tmp/kops896168616/kops toolbox dump --name e2e-kops-flanl-rhel8-k16-ko18.test-cncf-aws.k8s.io -ojson
I0924 21:34:53.994504     211 featureflag.go:154] FeatureFlag "SpecOverrideFlag"=true
2020/09/24 21:34:55 process.go:155: Step 'kubectl -n kube-system get pods -ojson -l k8s-app=kops-controller' finished in 1.341220608s
2020/09/24 21:34:55 process.go:153: Running: kubectl -n kube-system logs --all-containers kops-controller-9jznb
... skipping 271 lines ...
dhcp-options:dopt-0b8b8807cd31b3b4f	ok
Deleted kubectl config for e2e-kops-flanl-rhel8-k16-ko18.test-cncf-aws.k8s.io

Deleted cluster: "e2e-kops-flanl-rhel8-k16-ko18.test-cncf-aws.k8s.io"
2020/09/24 21:37:58 process.go:155: Step '/tmp/kops896168616/kops delete cluster e2e-kops-flanl-rhel8-k16-ko18.test-cncf-aws.k8s.io --yes' finished in 2m21.096947825s
2020/09/24 21:37:58 process.go:96: Saved XML output to /logs/artifacts/junit_runner.xml.
2020/09/24 21:37:58 main.go:312: Something went wrong: starting e2e cluster: kops validate cluster failed: error during /tmp/kops896168616/kops validate cluster e2e-kops-flanl-rhel8-k16-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 ...