This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-09-22 20:51
Elapsed19m5s
Revisionmaster

No Test Failures!


Error lines from build-log.txt

... skipping 134 lines ...
I0922 20:52:42.546224    4671 up.go:43] Cleaning up any leaked resources from previous cluster
I0922 20:52:42.546262    4671 dumplogs.go:40] /logs/artifacts/d6011455-1be6-11ec-ab4b-8aa8b3c2a036/kops toolbox dump --name e2e-672956aa90-be72a.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0922 20:52:42.562273    4691 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0922 20:52:42.562357    4691 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-672956aa90-be72a.test-cncf-aws.k8s.io" not found
W0922 20:52:43.053583    4671 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0922 20:52:43.053624    4671 down.go:48] /logs/artifacts/d6011455-1be6-11ec-ab4b-8aa8b3c2a036/kops delete cluster --name e2e-672956aa90-be72a.test-cncf-aws.k8s.io --yes
I0922 20:52:43.069800    4700 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0922 20:52:43.070765    4700 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-672956aa90-be72a.test-cncf-aws.k8s.io" not found
I0922 20:52:43.566189    4671 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/09/22 20:52:43 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
I0922 20:52:43.573045    4671 http.go:37] curl https://ip.jsb.workers.dev
I0922 20:52:43.659449    4671 up.go:144] /logs/artifacts/d6011455-1be6-11ec-ab4b-8aa8b3c2a036/kops create cluster --name e2e-672956aa90-be72a.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.21.5 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --image=309956199498/RHEL-8.2.0_HVM-20210907-x86_64-0-Hourly2-GP2 --channel=alpha --networking=kopeio --container-runtime=docker --admin-access 34.121.191.223/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-southeast-2a --master-size c5.large
I0922 20:52:43.674852    4710 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0922 20:52:43.674949    4710 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I0922 20:52:43.719802    4710 create_cluster.go:728] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0922 20:52:44.306977    4710 new_cluster.go:1011]  Cloud Provider ID = aws
... skipping 42 lines ...

I0922 20:53:14.196822    4671 up.go:181] /logs/artifacts/d6011455-1be6-11ec-ab4b-8aa8b3c2a036/kops validate cluster --name e2e-672956aa90-be72a.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0922 20:53:14.211402    4731 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0922 20:53:14.211644    4731 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-672956aa90-be72a.test-cncf-aws.k8s.io

W0922 20:53:15.833705    4731 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-672956aa90-be72a.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0922 20:53:25.864573    4731 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-672956aa90-be72a.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-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
W0922 20:53:35.894451    4731 validate_cluster.go:221] (will retry): cluster not yet healthy
W0922 20:53:45.926345    4731 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-672956aa90-be72a.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-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
W0922 20:53:55.960820    4731 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-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
W0922 20:54:06.001774    4731 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-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
W0922 20:54:16.039302    4731 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-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
W0922 20:54:26.075446    4731 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-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
W0922 20:54:36.113200    4731 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-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
W0922 20:54:46.145059    4731 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-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
W0922 20:54:56.181833    4731 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-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
W0922 20:55:06.215094    4731 validate_cluster.go:221] (will retry): cluster not yet healthy
W0922 20:55:16.253891    4731 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-672956aa90-be72a.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-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
W0922 20:55:26.298800    4731 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-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
W0922 20:55:36.343044    4731 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-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
W0922 20:55:46.373537    4731 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-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
W0922 20:55:56.414197    4731 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-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
W0922 20:56:06.447340    4731 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-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
W0922 20:56:16.479556    4731 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-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
W0922 20:56:26.522824    4731 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-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
W0922 20:56:36.558368    4731 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-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
W0922 20:56:46.588987    4731 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-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
W0922 20:56:56.628348    4731 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-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
W0922 20:57:06.667546    4731 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-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
W0922 20:57:16.710848    4731 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-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
W0922 20:57:26.743409    4731 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-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
W0922 20:57:36.788167    4731 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-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
W0922 20:57:46.832878    4731 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-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
W0922 20:57:56.864452    4731 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-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
W0922 20:58:06.908195    4731 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-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
W0922 20:58:16.936475    4731 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-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
W0922 20:58:26.971015    4731 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-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
W0922 20:58:37.009970    4731 validate_cluster.go:221] (will retry): cluster not yet healthy
W0922 20:59:17.042060    4731 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api.e2e-672956aa90-be72a.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 203.0.113.123:443: i/o timeout
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

NODE STATUS
... skipping 6 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kopeio-networking-agent-k46kz				system-node-critical pod "kopeio-networking-agent-k46kz" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal" is not ready (kube-proxy)

Validation Failed
W0922 20:59:31.439005    4731 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kopeio-networking-agent-k46kz				system-node-critical pod "kopeio-networking-agent-k46kz" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal" is not ready (kube-proxy)

Validation Failed
W0922 20:59:44.442979    4731 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kopeio-networking-agent-k46kz				system-node-critical pod "kopeio-networking-agent-k46kz" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal" is not ready (kube-proxy)

Validation Failed
W0922 20:59:57.496410    4731 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kopeio-networking-agent-k46kz				system-node-critical pod "kopeio-networking-agent-k46kz" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal" is not ready (kube-proxy)

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

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kopeio-networking-agent-k46kz				system-node-critical pod "kopeio-networking-agent-k46kz" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal" is not ready (kube-proxy)

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

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kopeio-networking-agent-k46kz				system-node-critical pod "kopeio-networking-agent-k46kz" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal" is not ready (kube-proxy)

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

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kopeio-networking-agent-k46kz				system-node-critical pod "kopeio-networking-agent-k46kz" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal" is not ready (kube-proxy)

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

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kopeio-networking-agent-k46kz				system-node-critical pod "kopeio-networking-agent-k46kz" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal" is not ready (kube-proxy)

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

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kopeio-networking-agent-k46kz				system-node-critical pod "kopeio-networking-agent-k46kz" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal" is not ready (kube-proxy)

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

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kopeio-networking-agent-k46kz				system-node-critical pod "kopeio-networking-agent-k46kz" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal" is not ready (kube-proxy)

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

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kopeio-networking-agent-k46kz				system-node-critical pod "kopeio-networking-agent-k46kz" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal" is not ready (kube-proxy)

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

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kopeio-networking-agent-k46kz				system-node-critical pod "kopeio-networking-agent-k46kz" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal" is not ready (kube-proxy)

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

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kopeio-networking-agent-k46kz				system-node-critical pod "kopeio-networking-agent-k46kz" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal" is not ready (kube-proxy)

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

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kopeio-networking-agent-k46kz				system-node-critical pod "kopeio-networking-agent-k46kz" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal" is not ready (kube-proxy)

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

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kopeio-networking-agent-k46kz				system-node-critical pod "kopeio-networking-agent-k46kz" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal" is not ready (kube-proxy)

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

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kopeio-networking-agent-k46kz				system-node-critical pod "kopeio-networking-agent-k46kz" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal" is not ready (kube-proxy)

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

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kopeio-networking-agent-k46kz				system-node-critical pod "kopeio-networking-agent-k46kz" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal" is not ready (kube-proxy)

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

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kopeio-networking-agent-k46kz				system-node-critical pod "kopeio-networking-agent-k46kz" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal" is not ready (kube-proxy)

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

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kopeio-networking-agent-k46kz				system-node-critical pod "kopeio-networking-agent-k46kz" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal" is not ready (kube-proxy)

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

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kopeio-networking-agent-k46kz				system-node-critical pod "kopeio-networking-agent-k46kz" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal" is not ready (kube-proxy)

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

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kopeio-networking-agent-k46kz				system-node-critical pod "kopeio-networking-agent-k46kz" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal" is not ready (kube-proxy)

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

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kopeio-networking-agent-k46kz				system-node-critical pod "kopeio-networking-agent-k46kz" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal" is not ready (kube-proxy)

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

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kopeio-networking-agent-k46kz				system-node-critical pod "kopeio-networking-agent-k46kz" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal" is not ready (kube-proxy)

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

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kopeio-networking-agent-k46kz				system-node-critical pod "kopeio-networking-agent-k46kz" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal" is not ready (kube-proxy)

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

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kopeio-networking-agent-k46kz				system-node-critical pod "kopeio-networking-agent-k46kz" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal" is not ready (kube-proxy)

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

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kopeio-networking-agent-k46kz				system-node-critical pod "kopeio-networking-agent-k46kz" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal" is not ready (kube-proxy)

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

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kopeio-networking-agent-k46kz				system-node-critical pod "kopeio-networking-agent-k46kz" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal" is not ready (kube-proxy)

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

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kopeio-networking-agent-k46kz				system-node-critical pod "kopeio-networking-agent-k46kz" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal" is not ready (kube-proxy)

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

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kopeio-networking-agent-k46kz				system-node-critical pod "kopeio-networking-agent-k46kz" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal" is not ready (kube-proxy)

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

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kopeio-networking-agent-k46kz				system-node-critical pod "kopeio-networking-agent-k46kz" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal" is not ready (kube-proxy)

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

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kopeio-networking-agent-k46kz				system-node-critical pod "kopeio-networking-agent-k46kz" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal" is not ready (kube-proxy)

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

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kopeio-networking-agent-k46kz				system-node-critical pod "kopeio-networking-agent-k46kz" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal" is not ready (kube-proxy)

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

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kopeio-networking-agent-k46kz				system-node-critical pod "kopeio-networking-agent-k46kz" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal" is not ready (kube-proxy)

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

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kopeio-networking-agent-k46kz				system-node-critical pod "kopeio-networking-agent-k46kz" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal" is not ready (kube-proxy)

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

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kopeio-networking-agent-k46kz				system-node-critical pod "kopeio-networking-agent-k46kz" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal" is not ready (kube-proxy)

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

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kopeio-networking-agent-k46kz				system-node-critical pod "kopeio-networking-agent-k46kz" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal" is not ready (kube-proxy)

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

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kopeio-networking-agent-k46kz				system-node-critical pod "kopeio-networking-agent-k46kz" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal" is not ready (kube-proxy)

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

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kopeio-networking-agent-k46kz				system-node-critical pod "kopeio-networking-agent-k46kz" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal" is not ready (kube-proxy)

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

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kopeio-networking-agent-k46kz				system-node-critical pod "kopeio-networking-agent-k46kz" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal" is not ready (kube-proxy)

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

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kopeio-networking-agent-k46kz				system-node-critical pod "kopeio-networking-agent-k46kz" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal" is not ready (kube-proxy)

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

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kopeio-networking-agent-k46kz				system-node-critical pod "kopeio-networking-agent-k46kz" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-0.ap-southeast-2.compute.internal" is not ready (kube-proxy)

Validation Failed
W0922 21:08:16.166114    4731 validate_cluster.go:221] (will retry): cluster not yet healthy

Validation failed: wait time exceeded during validation
I0922 21:08:26.172191    4671 dumplogs.go:40] /logs/artifacts/d6011455-1be6-11ec-ab4b-8aa8b3c2a036/kops toolbox dump --name e2e-672956aa90-be72a.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0922 21:08:26.196312    4744 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0922 21:08:26.196495    4744 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
2021/09/22 21:08:39 Dumping node ip-172-20-32-223.ap-southeast-2.compute.internal
2021/09/22 21:08:46 Dumping node ip-172-20-34-0.ap-southeast-2.compute.internal
2021/09/22 21:08:53 Dumping node ip-172-20-36-184.ap-southeast-2.compute.internal
... skipping 1207 lines ...
route-table:rtb-06622440760c90e00	ok
vpc:vpc-0e7bc95ec100961bc	ok
dhcp-options:dopt-0b14f205c0f212819	ok
Deleted kubectl config for e2e-672956aa90-be72a.test-cncf-aws.k8s.io

Deleted cluster: "e2e-672956aa90-be72a.test-cncf-aws.k8s.io"
Error: exit status 1
+ EXIT_VALUE=1
+ set +o xtrace