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

No Test Failures!


Show 1 Passed Tests

Error lines from build-log.txt

... skipping 222 lines ...
I0907 21:39:04.981477    6267 app.go:64] RunDir for this run: "/home/prow/go/src/k8s.io/kops/_rundir/3eab63c2-2ef5-11ed-8857-d61b7b5f68bf"
I0907 21:39:04.988459    6267 app.go:128] ID for this run: "3eab63c2-2ef5-11ed-8857-d61b7b5f68bf"
I0907 21:39:04.988802    6267 local.go:42] ⚙️ ssh-keygen -t ed25519 -N  -q -f /tmp/kops/e2e-4342699135-9b4dd.test-cncf-aws.k8s.io/id_ed25519
I0907 21:39:04.995371    6267 up.go:44] Cleaning up any leaked resources from previous cluster
I0907 21:39:04.995474    6267 dumplogs.go:45] /tmp/kops.XTL2H7fZw 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
I0907 21:39:04.995490    6267 local.go:42] ⚙️ /tmp/kops.XTL2H7fZw 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
W0907 21:39:05.486494    6267 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0907 21:39:05.486568    6267 down.go:48] /tmp/kops.XTL2H7fZw delete cluster --name e2e-4342699135-9b4dd.test-cncf-aws.k8s.io --yes
I0907 21:39:05.486578    6267 local.go:42] ⚙️ /tmp/kops.XTL2H7fZw delete cluster --name e2e-4342699135-9b4dd.test-cncf-aws.k8s.io --yes
I0907 21:39:05.520794    6287 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
I0907 21:39:05.520912    6287 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
I0907 21:39:06.013346    6267 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2022/09/07 21:39:06 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
I0907 21:39:06.026101    6267 http.go:37] curl https://ip.jsb.workers.dev
I0907 21:39:06.165369    6267 up.go:159] /tmp/kops.XTL2H7fZw 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 35.232.95.31/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --master-size c5.large
I0907 21:39:06.165413    6267 local.go:42] ⚙️ /tmp/kops.XTL2H7fZw 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 35.232.95.31/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --master-size c5.large
I0907 21:39:06.196176    6299 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
I0907 21:39:06.196372    6299 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
I0907 21:39:06.213551    6299 create_cluster.go:843] Using SSH public key: /tmp/kops/e2e-4342699135-9b4dd.test-cncf-aws.k8s.io/id_ed25519.pub
... skipping 698 lines ...
I0907 21:39:55.087666    6267 up.go:243] /tmp/kops.XTL2H7fZw validate cluster --name e2e-4342699135-9b4dd.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0907 21:39:55.087721    6267 local.go:42] ⚙️ /tmp/kops.XTL2H7fZw validate cluster --name e2e-4342699135-9b4dd.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0907 21:39:55.118802    6340 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
I0907 21:39:55.119011    6340 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-4342699135-9b4dd.test-cncf-aws.k8s.io

W0907 21:39:56.490476    6340 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-4342699135-9b4dd.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
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
W0907 21:40:06.535918    6340 validate_cluster.go:232] (will retry): cluster not yet healthy
W0907 21:40:16.603876    6340 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-4342699135-9b4dd.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
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
W0907 21:40:26.684969    6340 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
W0907 21:40:36.768144    6340 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
W0907 21:40:46.851846    6340 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
W0907 21:40:56.893834    6340 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
W0907 21:41:06.934298    6340 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
W0907 21:41:16.968863    6340 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
W0907 21:41:27.018956    6340 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
W0907 21:41:37.073097    6340 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
W0907 21:41:47.125638    6340 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
W0907 21:41:57.180942    6340 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
W0907 21:42:07.258047    6340 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
W0907 21:42:17.299747    6340 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
W0907 21:42:27.366913    6340 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
W0907 21:42:37.406629    6340 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
W0907 21:42:47.458394    6340 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
W0907 21:42:57.501698    6340 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
W0907 21:43:07.560559    6340 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 24 lines ...
Pod	kube-system/ebs-csi-controller-575f78655f-76gpl	system-cluster-critical pod "ebs-csi-controller-575f78655f-76gpl" is pending
Pod	kube-system/ebs-csi-node-j8r72			system-node-critical pod "ebs-csi-node-j8r72" is pending
Pod	kube-system/ebs-csi-node-ld4wc			system-node-critical pod "ebs-csi-node-ld4wc" is pending
Pod	kube-system/ebs-csi-node-qcjwq			system-node-critical pod "ebs-csi-node-qcjwq" is pending
Pod	kube-system/ebs-csi-node-tm4x9			system-node-critical pod "ebs-csi-node-tm4x9" is pending

Validation Failed
W0907 21:43:22.533103    6340 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 22 lines ...
Pod	kube-system/ebs-csi-controller-575f78655f-76gpl	system-cluster-critical pod "ebs-csi-controller-575f78655f-76gpl" is pending
Pod	kube-system/ebs-csi-node-j8r72			system-node-critical pod "ebs-csi-node-j8r72" is pending
Pod	kube-system/ebs-csi-node-ld4wc			system-node-critical pod "ebs-csi-node-ld4wc" is pending
Pod	kube-system/ebs-csi-node-qcjwq			system-node-critical pod "ebs-csi-node-qcjwq" is pending
Pod	kube-system/ebs-csi-node-tm4x9			system-node-critical pod "ebs-csi-node-tm4x9" is pending

Validation Failed
W0907 21:43:35.648115    6340 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
Node	i-0acc1fbad9361d0c3				node "i-0acc1fbad9361d0c3" of role "node" is not ready
Pod	kube-system/ebs-csi-controller-575f78655f-57bsh	system-cluster-critical pod "ebs-csi-controller-575f78655f-57bsh" is pending

Validation Failed
W0907 21:43:48.798022    6340 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 40 lines ...
i-0acc1fbad9361d0c3	node	True
i-0b6a27d9a42100a32	master	True
i-0c82298266cd029f4	node	True

Your cluster e2e-4342699135-9b4dd.test-cncf-aws.k8s.io is ready
I0907 21:44:27.618252    6340 validate_cluster.go:220] (will retry): cluster passed validation 3 consecutive times
W0907 21:44:37.684704    6340 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-4342699135-9b4dd.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
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
... skipping 370 lines ...
• [SLOW TEST] [325.001 seconds]
test ingresses with multiple path and backends with podReadinessGate enabled IngressGroup across namespaces should behaves correctly
/tmp/kops.CFMXAGsJV/test/e2e/ingress/multi_path_backend_test.go:110
------------------------------

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

Ginkgo ran 1 suite in 37m35.095445262s
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-0b2708dc58bf09068 -ginkgo.junit-report=/logs/artifacts/aws-lb-controller/junit-service.xml
... skipping 49 lines ...
• [SLOW TEST] [12.317 seconds]
k8s service reconciled by the aws load balancer NLB IP Load Balancer with name Should create and verify service
/tmp/kops.CFMXAGsJV/test/e2e/service/nlb_ip_target_test.go:348
------------------------------

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

Ginkgo ran 1 suite in 9m44.694202045s
Test Suite Passed
+ kops-finish
... skipping 561 lines ...