This job view page is being replaced by Spyglass soon. Check out the new job view.
Resultsuccess
Tests 0 failed / 1 succeeded
Started2022-09-05 21:37
Elapsed1h0m
Revision
uploadercrier
uploadercrier

No Test Failures!


Show 1 Passed Tests

Error lines from build-log.txt

... skipping 222 lines ...
I0905 21:39:43.651641    6294 app.go:64] RunDir for this run: "/home/prow/go/src/k8s.io/kops/_rundir/fe5213c3-2d62-11ed-af55-42d5248344a4"
I0905 21:39:43.658170    6294 app.go:128] ID for this run: "fe5213c3-2d62-11ed-af55-42d5248344a4"
I0905 21:39:43.658779    6294 local.go:42] ⚙️ ssh-keygen -t ed25519 -N  -q -f /tmp/kops/e2e-4342699135-9b4dd.test-cncf-aws.k8s.io/id_ed25519
I0905 21:39:43.666290    6294 up.go:44] Cleaning up any leaked resources from previous cluster
I0905 21:39:43.666661    6294 dumplogs.go:45] /tmp/kops.G22Usp3LR toolbox dump --name e2e-4342699135-9b4dd.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-4342699135-9b4dd.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
I0905 21:39:43.666729    6294 local.go:42] ⚙️ /tmp/kops.G22Usp3LR toolbox dump --name e2e-4342699135-9b4dd.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-4342699135-9b4dd.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
W0905 21:39:44.192677    6294 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0905 21:39:44.192742    6294 down.go:48] /tmp/kops.G22Usp3LR delete cluster --name e2e-4342699135-9b4dd.test-cncf-aws.k8s.io --yes
I0905 21:39:44.192753    6294 local.go:42] ⚙️ /tmp/kops.G22Usp3LR delete cluster --name e2e-4342699135-9b4dd.test-cncf-aws.k8s.io --yes
I0905 21:39:44.228350    6317 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
I0905 21:39:44.228466    6317 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-4342699135-9b4dd.test-cncf-aws.k8s.io" not found
I0905 21:39:44.697946    6294 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2022/09/05 21:39:44 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
I0905 21:39:44.712911    6294 http.go:37] curl https://ip.jsb.workers.dev
I0905 21:39:44.833932    6294 up.go:159] /tmp/kops.G22Usp3LR create cluster --name e2e-4342699135-9b4dd.test-cncf-aws.k8s.io --cloud aws --kubernetes-version v1.25.0 --ssh-public-key /tmp/kops/e2e-4342699135-9b4dd.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --networking amazonvpc --set=cluster.spec.awsLoadBalancerController.enabled=true --set=cluster.spec.certManager.enabled=true --zones=eu-west-1a,eu-west-1b,eu-west-1c --discovery-store=s3://k8s-kops-prow/e2e-4342699135-9b4dd.test-cncf-aws.k8s.io/discovery --admin-access 34.123.240.199/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --master-size c5.large
I0905 21:39:44.833988    6294 local.go:42] ⚙️ /tmp/kops.G22Usp3LR create cluster --name e2e-4342699135-9b4dd.test-cncf-aws.k8s.io --cloud aws --kubernetes-version v1.25.0 --ssh-public-key /tmp/kops/e2e-4342699135-9b4dd.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --networking amazonvpc --set=cluster.spec.awsLoadBalancerController.enabled=true --set=cluster.spec.certManager.enabled=true --zones=eu-west-1a,eu-west-1b,eu-west-1c --discovery-store=s3://k8s-kops-prow/e2e-4342699135-9b4dd.test-cncf-aws.k8s.io/discovery --admin-access 34.123.240.199/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --master-size c5.large
I0905 21:39:44.873866    6326 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
I0905 21:39:44.874044    6326 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
I0905 21:39:44.893406    6326 create_cluster.go:843] Using SSH public key: /tmp/kops/e2e-4342699135-9b4dd.test-cncf-aws.k8s.io/id_ed25519.pub
... skipping 710 lines ...

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
W0905 21:40:35.857559    6367 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
nodes-eu-west-1c	Node	t3.medium	1	1	eu-west-1c

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0905 21:40:45.896004    6367 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
nodes-eu-west-1c	Node	t3.medium	1	1	eu-west-1c

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0905 21:40:55.929869    6367 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
nodes-eu-west-1c	Node	t3.medium	1	1	eu-west-1c

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0905 21:41:05.968306    6367 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
nodes-eu-west-1c	Node	t3.medium	1	1	eu-west-1c

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0905 21:41:16.002355    6367 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
nodes-eu-west-1c	Node	t3.medium	1	1	eu-west-1c

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0905 21:41:26.042281    6367 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
nodes-eu-west-1c	Node	t3.medium	1	1	eu-west-1c

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0905 21:41:36.083149    6367 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
nodes-eu-west-1c	Node	t3.medium	1	1	eu-west-1c

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0905 21:41:46.120456    6367 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
nodes-eu-west-1c	Node	t3.medium	1	1	eu-west-1c

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0905 21:41:56.156908    6367 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
nodes-eu-west-1c	Node	t3.medium	1	1	eu-west-1c

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0905 21:42:06.205018    6367 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
nodes-eu-west-1c	Node	t3.medium	1	1	eu-west-1c

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0905 21:42:16.242057    6367 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
nodes-eu-west-1c	Node	t3.medium	1	1	eu-west-1c

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0905 21:42:26.290941    6367 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
nodes-eu-west-1c	Node	t3.medium	1	1	eu-west-1c

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0905 21:42:36.336252    6367 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
nodes-eu-west-1c	Node	t3.medium	1	1	eu-west-1c

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0905 21:42:46.372395    6367 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
nodes-eu-west-1c	Node	t3.medium	1	1	eu-west-1c

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0905 21:42:56.410853    6367 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
nodes-eu-west-1c	Node	t3.medium	1	1	eu-west-1c

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0905 21:43:06.449077    6367 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
nodes-eu-west-1c	Node	t3.medium	1	1	eu-west-1c

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0905 21:43:16.480488    6367 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
nodes-eu-west-1c	Node	t3.medium	1	1	eu-west-1c

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0905 21:43:26.534879    6367 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
nodes-eu-west-1c	Node	t3.medium	1	1	eu-west-1c

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0905 21:43:36.584598    6367 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
... skipping 25 lines ...
Pod	kube-system/ebs-csi-node-6xv6s					system-node-critical pod "ebs-csi-node-6xv6s" is pending
Pod	kube-system/ebs-csi-node-8t45q					system-node-critical pod "ebs-csi-node-8t45q" is pending
Pod	kube-system/ebs-csi-node-crc8v					system-node-critical pod "ebs-csi-node-crc8v" is pending
Pod	kube-system/ebs-csi-node-n8zbs					system-node-critical pod "ebs-csi-node-n8zbs" is pending
Pod	kube-system/kube-proxy-i-08f1d4bc9f9a407c1			system-node-critical pod "kube-proxy-i-08f1d4bc9f9a407c1" is pending

Validation Failed
W0905 21:43:50.392637    6367 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
... skipping 20 lines ...
Pod	kube-system/ebs-csi-controller-575f78655f-d8jmd			system-cluster-critical pod "ebs-csi-controller-575f78655f-d8jmd" is pending
Pod	kube-system/ebs-csi-node-6xv6s					system-node-critical pod "ebs-csi-node-6xv6s" is pending
Pod	kube-system/ebs-csi-node-8t45q					system-node-critical pod "ebs-csi-node-8t45q" is pending
Pod	kube-system/ebs-csi-node-crc8v					system-node-critical pod "ebs-csi-node-crc8v" is pending
Pod	kube-system/ebs-csi-node-n8zbs					system-node-critical pod "ebs-csi-node-n8zbs" is pending

Validation Failed
W0905 21:44:03.570989    6367 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
... skipping 10 lines ...
VALIDATION ERRORS
KIND	NAME								MESSAGE
Node	i-0020df1b1aa80fd19						node "i-0020df1b1aa80fd19" of role "node" is not ready
Pod	kube-system/aws-load-balancer-controller-6b9486954-c9cfx	system-cluster-critical pod "aws-load-balancer-controller-6b9486954-c9cfx" is pending
Pod	kube-system/ebs-csi-controller-575f78655f-9pp5s			system-cluster-critical pod "ebs-csi-controller-575f78655f-9pp5s" is pending

Validation Failed
W0905 21:44:16.630260    6367 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
... skipping 9 lines ...

VALIDATION ERRORS
KIND	NAME								MESSAGE
Pod	kube-system/aws-load-balancer-controller-6b9486954-c9cfx	system-cluster-critical pod "aws-load-balancer-controller-6b9486954-c9cfx" is pending
Pod	kube-system/ebs-csi-controller-575f78655f-9pp5s			system-cluster-critical pod "ebs-csi-controller-575f78655f-9pp5s" is not ready (ebs-plugin)

Validation Failed
W0905 21:44:29.508708    6367 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
... skipping 8 lines ...
i-0fa7a785e0146c7fd	master	True

VALIDATION ERRORS
KIND	NAME								MESSAGE
Pod	kube-system/aws-load-balancer-controller-6b9486954-c9cfx	system-cluster-critical pod "aws-load-balancer-controller-6b9486954-c9cfx" is pending

Validation Failed
W0905 21:44:42.566862    6367 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
... skipping 8 lines ...
i-0fa7a785e0146c7fd	master	True

VALIDATION ERRORS
KIND	NAME								MESSAGE
Pod	kube-system/aws-load-balancer-controller-6b9486954-c9cfx	system-cluster-critical pod "aws-load-balancer-controller-6b9486954-c9cfx" is pending

Validation Failed
W0905 21:44:55.418901    6367 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
... skipping 8 lines ...
i-0fa7a785e0146c7fd	master	True

VALIDATION ERRORS
KIND	NAME								MESSAGE
Pod	kube-system/aws-load-balancer-controller-6b9486954-c9cfx	system-cluster-critical pod "aws-load-balancer-controller-6b9486954-c9cfx" is pending

Validation Failed
W0905 21:45:08.389002    6367 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
... skipping 8 lines ...
i-0fa7a785e0146c7fd	master	True

VALIDATION ERRORS
KIND	NAME								MESSAGE
Pod	kube-system/aws-load-balancer-controller-6b9486954-c9cfx	system-cluster-critical pod "aws-load-balancer-controller-6b9486954-c9cfx" is pending

Validation Failed
W0905 21:45:21.340947    6367 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
... skipping 8 lines ...
i-0fa7a785e0146c7fd	master	True

VALIDATION ERRORS
KIND	NAME								MESSAGE
Pod	kube-system/aws-load-balancer-controller-6b9486954-c9cfx	system-cluster-critical pod "aws-load-balancer-controller-6b9486954-c9cfx" is pending

Validation Failed
W0905 21:45:34.475393    6367 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
... skipping 8 lines ...
i-0fa7a785e0146c7fd	master	True

VALIDATION ERRORS
KIND	NAME								MESSAGE
Pod	kube-system/aws-load-balancer-controller-6b9486954-c9cfx	system-cluster-critical pod "aws-load-balancer-controller-6b9486954-c9cfx" is pending

Validation Failed
W0905 21:45:47.552080    6367 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
... skipping 371 lines ...
• [SLOW TEST] [260.442 seconds]
test ingresses with multiple path and backends with podReadinessGate enabled IngressGroup across namespaces should behaves correctly
/tmp/kops.p3yaN4hnx/test/e2e/ingress/multi_path_backend_test.go:110
------------------------------

Ran 11 of 11 Specs in 1970.626 seconds
SUCCESS! -- 11 Passed | 0 Failed | 0 Pending | 0 Skipped
--- PASS: TestIngress (1970.63s)
PASS

Ginkgo ran 1 suite in 34m12.751480539s
Test Suite Passed
+ ginkgo -v -r test/e2e/service -- -cluster-name=e2e-4342699135-9b4dd.test-cncf-aws.k8s.io -aws-region=eu-west-1 -aws-vpc-id=vpc-09abf4aa7b8803f0e -ginkgo.junit-report=/logs/artifacts/aws-lb-controller/junit-service.xml
... skipping 49 lines ...
• [SLOW TEST] [12.278 seconds]
k8s service reconciled by the aws load balancer NLB IP Load Balancer with name Should create and verify service
/tmp/kops.p3yaN4hnx/test/e2e/service/nlb_ip_target_test.go:348
------------------------------

Ran 6 of 8 Specs in 642.832 seconds
SUCCESS! -- 6 Passed | 0 Failed | 0 Pending | 2 Skipped
--- PASS: TestService (642.83s)
PASS

Ginkgo ran 1 suite in 10m57.83601364s
Test Suite Passed
+ kops-finish
... skipping 535 lines ...