This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 2 succeeded
Started2022-08-15 17:24
Elapsed11m51s
Revisionmaster

Test Failures


kubetest2 Test 1.96s

exit status 255
				from junit_runner.xml

Filter through log files | View test history on testgrid


Show 2 Passed Tests

Error lines from build-log.txt

ERROR: (gcloud.auth.activate-service-account) There was a problem refreshing your current auth tokens: ('invalid_grant: Invalid JWT Signature.', {'error': 'invalid_grant', 'error_description': 'Invalid JWT Signature.'})
Please run:

  $ gcloud auth login

to obtain new credentials.

... skipping 171 lines ...
I0815 17:25:52.191842    6127 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt
I0815 17:25:52.193694    6127 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/1.25.0-alpha.3+v1.25.0-alpha.2-88-gf442cc2d0a/linux/amd64/kops
I0815 17:25:53.010693    6127 local.go:42] ⚙️ ssh-keygen -t ed25519 -N  -q -f /tmp/kops/e2e-e2e-kops-aws-misc-ha-euwest1.test-cncf-aws.k8s.io/id_ed25519
I0815 17:25:53.025285    6127 up.go:44] Cleaning up any leaked resources from previous cluster
I0815 17:25:53.025401    6127 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/0e09f375-1cbf-11ed-9820-1e463d3c6692/kops toolbox dump --name e2e-e2e-kops-aws-misc-ha-euwest1.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-aws-misc-ha-euwest1.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
I0815 17:25:53.025430    6127 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/0e09f375-1cbf-11ed-9820-1e463d3c6692/kops toolbox dump --name e2e-e2e-kops-aws-misc-ha-euwest1.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-aws-misc-ha-euwest1.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
W0815 17:25:53.523795    6127 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0815 17:25:53.523848    6127 down.go:48] /home/prow/go/src/k8s.io/kops/_rundir/0e09f375-1cbf-11ed-9820-1e463d3c6692/kops delete cluster --name e2e-e2e-kops-aws-misc-ha-euwest1.test-cncf-aws.k8s.io --yes
I0815 17:25:53.523861    6127 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/0e09f375-1cbf-11ed-9820-1e463d3c6692/kops delete cluster --name e2e-e2e-kops-aws-misc-ha-euwest1.test-cncf-aws.k8s.io --yes
I0815 17:25:53.558613    6161 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-e2e-kops-aws-misc-ha-euwest1.test-cncf-aws.k8s.io" not found
I0815 17:25:54.038639    6127 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2022/08/15 17:25:54 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
I0815 17:25:54.056146    6127 http.go:37] curl https://ip.jsb.workers.dev
I0815 17:25:54.205792    6127 up.go:159] /home/prow/go/src/k8s.io/kops/_rundir/0e09f375-1cbf-11ed-9820-1e463d3c6692/kops create cluster --name e2e-e2e-kops-aws-misc-ha-euwest1.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.24.3 --ssh-public-key /tmp/kops/e2e-e2e-kops-aws-misc-ha-euwest1.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --image=099720109477/ubuntu/images/hvm-ssd/ubuntu-focal-20.04-amd64-server-20220810 --channel=alpha --networking=calico --container-runtime=containerd --master-count=3 --zones=eu-west-1a,eu-west-1b,eu-west-1c --discovery-store=s3://k8s-kops-prow/discovery --admin-access 35.223.186.31/32 --master-volume-size 48 --node-count 4 --node-volume-size 48 --master-size c5.large
I0815 17:25:54.205835    6127 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/0e09f375-1cbf-11ed-9820-1e463d3c6692/kops create cluster --name e2e-e2e-kops-aws-misc-ha-euwest1.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.24.3 --ssh-public-key /tmp/kops/e2e-e2e-kops-aws-misc-ha-euwest1.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --image=099720109477/ubuntu/images/hvm-ssd/ubuntu-focal-20.04-amd64-server-20220810 --channel=alpha --networking=calico --container-runtime=containerd --master-count=3 --zones=eu-west-1a,eu-west-1b,eu-west-1c --discovery-store=s3://k8s-kops-prow/discovery --admin-access 35.223.186.31/32 --master-volume-size 48 --node-count 4 --node-volume-size 48 --master-size c5.large
I0815 17:25:54.238937    6171 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true
I0815 17:25:54.256150    6171 create_cluster.go:862] Using SSH public key: /tmp/kops/e2e-e2e-kops-aws-misc-ha-euwest1.test-cncf-aws.k8s.io/id_ed25519.pub
I0815 17:25:54.852469    6171 new_cluster.go:1168]  Cloud Provider ID = aws
... skipping 834 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
W0815 17:26:45.542480    6207 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
master-eu-west-1b	Master	c5.large	1	1	eu-west-1b
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
... skipping 3 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
W0815 17:26:55.634928    6207 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
master-eu-west-1b	Master	c5.large	1	1	eu-west-1b
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
... skipping 3 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
W0815 17:27:05.679823    6207 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
master-eu-west-1b	Master	c5.large	1	1	eu-west-1b
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
... skipping 3 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
W0815 17:27:15.729226    6207 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
master-eu-west-1b	Master	c5.large	1	1	eu-west-1b
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
... skipping 3 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
W0815 17:27:25.766651    6207 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
master-eu-west-1b	Master	c5.large	1	1	eu-west-1b
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
... skipping 3 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
W0815 17:27:35.821785    6207 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
master-eu-west-1b	Master	c5.large	1	1	eu-west-1b
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
... skipping 3 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
W0815 17:27:45.874306    6207 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
master-eu-west-1b	Master	c5.large	1	1	eu-west-1b
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
... skipping 3 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
W0815 17:27:55.915226    6207 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
master-eu-west-1b	Master	c5.large	1	1	eu-west-1b
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
... skipping 3 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
W0815 17:28:05.951830    6207 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
master-eu-west-1b	Master	c5.large	1	1	eu-west-1b
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
... skipping 3 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
W0815 17:28:15.999754    6207 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
master-eu-west-1b	Master	c5.large	1	1	eu-west-1b
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
... skipping 3 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
W0815 17:28:26.047612    6207 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
master-eu-west-1b	Master	c5.large	1	1	eu-west-1b
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
... skipping 3 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
W0815 17:28:36.103188    6207 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
master-eu-west-1b	Master	c5.large	1	1	eu-west-1b
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
... skipping 3 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
W0815 17:28:46.139913    6207 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
master-eu-west-1b	Master	c5.large	1	1	eu-west-1b
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
... skipping 3 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
W0815 17:28:56.180152    6207 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
master-eu-west-1b	Master	c5.large	1	1	eu-west-1b
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
... skipping 3 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
W0815 17:29:06.232647    6207 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
master-eu-west-1b	Master	c5.large	1	1	eu-west-1b
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
... skipping 3 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
W0815 17:29:16.268365    6207 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
master-eu-west-1b	Master	c5.large	1	1	eu-west-1b
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
... skipping 3 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
W0815 17:29:26.309911    6207 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
master-eu-west-1b	Master	c5.large	1	1	eu-west-1b
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
... skipping 3 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
W0815 17:29:36.362870    6207 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
master-eu-west-1b	Master	c5.large	1	1	eu-west-1b
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
... skipping 3 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
W0815 17:29:46.410569    6207 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
master-eu-west-1b	Master	c5.large	1	1	eu-west-1b
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
... skipping 3 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
W0815 17:29:56.451826    6207 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
master-eu-west-1b	Master	c5.large	1	1	eu-west-1b
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
... skipping 28 lines ...
Pod	kube-system/ebs-csi-controller-59c98fb857-knb6w	system-cluster-critical pod "ebs-csi-controller-59c98fb857-knb6w" is pending
Pod	kube-system/ebs-csi-node-b5pdp			system-node-critical pod "ebs-csi-node-b5pdp" is pending
Pod	kube-system/ebs-csi-node-mmtp8			system-node-critical pod "ebs-csi-node-mmtp8" is pending
Pod	kube-system/ebs-csi-node-r259s			system-node-critical pod "ebs-csi-node-r259s" is pending
Pod	kube-system/ebs-csi-node-tms6d			system-node-critical pod "ebs-csi-node-tms6d" is pending

Validation Failed
W0815 17:30:11.275737    6207 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
master-eu-west-1b	Master	c5.large	1	1	eu-west-1b
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
... skipping 26 lines ...
Pod	kube-system/ebs-csi-controller-59c98fb857-knb6w	system-cluster-critical pod "ebs-csi-controller-59c98fb857-knb6w" is pending
Pod	kube-system/ebs-csi-node-b5pdp			system-node-critical pod "ebs-csi-node-b5pdp" is pending
Pod	kube-system/ebs-csi-node-mmtp8			system-node-critical pod "ebs-csi-node-mmtp8" is pending
Pod	kube-system/ebs-csi-node-r259s			system-node-critical pod "ebs-csi-node-r259s" is pending
Pod	kube-system/ebs-csi-node-tms6d			system-node-critical pod "ebs-csi-node-tms6d" is pending

Validation Failed
W0815 17:30:25.600136    6207 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
master-eu-west-1b	Master	c5.large	1	1	eu-west-1b
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
... skipping 24 lines ...
Pod	kube-system/ebs-csi-controller-59c98fb857-knb6w	system-cluster-critical pod "ebs-csi-controller-59c98fb857-knb6w" is pending
Pod	kube-system/ebs-csi-node-b5pdp			system-node-critical pod "ebs-csi-node-b5pdp" is pending
Pod	kube-system/ebs-csi-node-mmtp8			system-node-critical pod "ebs-csi-node-mmtp8" is pending
Pod	kube-system/ebs-csi-node-r259s			system-node-critical pod "ebs-csi-node-r259s" is pending
Pod	kube-system/ebs-csi-node-tms6d			system-node-critical pod "ebs-csi-node-tms6d" is pending

Validation Failed
W0815 17:30:39.580373    6207 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
master-eu-west-1b	Master	c5.large	1	1	eu-west-1b
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
... skipping 20 lines ...
Pod	kube-system/ebs-csi-controller-59c98fb857-hpnrc	system-cluster-critical pod "ebs-csi-controller-59c98fb857-hpnrc" is pending
Pod	kube-system/ebs-csi-node-b5pdp			system-node-critical pod "ebs-csi-node-b5pdp" is pending
Pod	kube-system/ebs-csi-node-r259s			system-node-critical pod "ebs-csi-node-r259s" is pending
Pod	kube-system/ebs-csi-node-tms6d			system-node-critical pod "ebs-csi-node-tms6d" is pending
Pod	kube-system/kube-proxy-i-090901e2029be3f99	system-node-critical pod "kube-proxy-i-090901e2029be3f99" is pending

Validation Failed
W0815 17:30:53.741848    6207 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
master-eu-west-1b	Master	c5.large	1	1	eu-west-1b
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
... skipping 14 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/calico-node-8vpdt			system-node-critical pod "calico-node-8vpdt" is not ready (calico-node)
Pod	kube-system/calico-node-kt86c			system-node-critical pod "calico-node-kt86c" is not ready (calico-node)
Pod	kube-system/ebs-csi-controller-59c98fb857-hpnrc	system-cluster-critical pod "ebs-csi-controller-59c98fb857-hpnrc" is pending

Validation Failed
W0815 17:31:07.709842    6207 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
master-eu-west-1b	Master	c5.large	1	1	eu-west-1b
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
... skipping 201 lines ...
i-0d9f2ab0a0bcf6215	node	True

Your cluster e2e-e2e-kops-aws-misc-ha-euwest1.test-cncf-aws.k8s.io is ready
I0815 17:33:27.268428    6127 up.go:105] cluster reported as up
I0815 17:33:27.268517    6127 local.go:42] ⚙️ /home/prow/go/bin/kubetest2-tester-kops --ginkgo-args=--debug --test-args=-test.timeout=60m -num-nodes=0 --test-package-marker=stable.txt --parallel=25
I0815 17:33:27.289872    6218 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true
F0815 17:33:29.229580    6218 tester.go:482] failed to run ginkgo tester: failed to get kubectl package from published releases: failed to get latest release name: exit status 1
I0815 17:33:29.232692    6127 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/0e09f375-1cbf-11ed-9820-1e463d3c6692/kops toolbox dump --name e2e-e2e-kops-aws-misc-ha-euwest1.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-aws-misc-ha-euwest1.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
I0815 17:33:29.232737    6127 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/0e09f375-1cbf-11ed-9820-1e463d3c6692/kops toolbox dump --name e2e-e2e-kops-aws-misc-ha-euwest1.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-aws-misc-ha-euwest1.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
I0815 17:34:28.627328    6127 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/0e09f375-1cbf-11ed-9820-1e463d3c6692/kops get cluster --name e2e-e2e-kops-aws-misc-ha-euwest1.test-cncf-aws.k8s.io -o yaml
I0815 17:34:28.627392    6127 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/0e09f375-1cbf-11ed-9820-1e463d3c6692/kops get cluster --name e2e-e2e-kops-aws-misc-ha-euwest1.test-cncf-aws.k8s.io -o yaml
I0815 17:34:29.208599    6127 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/0e09f375-1cbf-11ed-9820-1e463d3c6692/kops get instancegroups --name e2e-e2e-kops-aws-misc-ha-euwest1.test-cncf-aws.k8s.io -o yaml
I0815 17:34:29.208645    6127 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/0e09f375-1cbf-11ed-9820-1e463d3c6692/kops get instancegroups --name e2e-e2e-kops-aws-misc-ha-euwest1.test-cncf-aws.k8s.io -o yaml
... skipping 383 lines ...
route-table:rtb-0943b77783c23229d	ok
vpc:vpc-0a805cd2e4acb94e9	ok
dhcp-options:dopt-0b9be419bc2e1ff8b	ok
Deleted kubectl config for e2e-e2e-kops-aws-misc-ha-euwest1.test-cncf-aws.k8s.io

Deleted cluster: "e2e-e2e-kops-aws-misc-ha-euwest1.test-cncf-aws.k8s.io"
Error: exit status 255
+ EXIT_VALUE=1
+ set +o xtrace