This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE

Test Failures


kubetest2 Test 1.84s

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 ...
I0817 01:26:21.628525    6126 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt
I0817 01:26:21.630864    6126 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
I0817 01:26:22.338696    6126 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
I0817 01:26:22.345811    6126 up.go:44] Cleaning up any leaked resources from previous cluster
I0817 01:26:22.345923    6126 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/59085070-1dcb-11ed-a994-1ec15ee5f766/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
I0817 01:26:22.345942    6126 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/59085070-1dcb-11ed-a994-1ec15ee5f766/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
W0817 01:26:22.823288    6126 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0817 01:26:22.823343    6126 down.go:48] /home/prow/go/src/k8s.io/kops/_rundir/59085070-1dcb-11ed-a994-1ec15ee5f766/kops delete cluster --name e2e-e2e-kops-aws-misc-ha-euwest1.test-cncf-aws.k8s.io --yes
I0817 01:26:22.823356    6126 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/59085070-1dcb-11ed-a994-1ec15ee5f766/kops delete cluster --name e2e-e2e-kops-aws-misc-ha-euwest1.test-cncf-aws.k8s.io --yes
I0817 01:26:22.854727    6159 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
I0817 01:26:23.305495    6126 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2022/08/17 01:26:23 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
I0817 01:26:23.318523    6126 http.go:37] curl https://ip.jsb.workers.dev
I0817 01:26:23.441261    6126 up.go:159] /home/prow/go/src/k8s.io/kops/_rundir/59085070-1dcb-11ed-a994-1ec15ee5f766/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.224.130.54/32 --master-volume-size 48 --node-count 4 --node-volume-size 48 --master-size c5.large
I0817 01:26:23.441306    6126 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/59085070-1dcb-11ed-a994-1ec15ee5f766/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.224.130.54/32 --master-volume-size 48 --node-count 4 --node-volume-size 48 --master-size c5.large
I0817 01:26:23.473393    6169 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true
I0817 01:26:23.491131    6169 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
I0817 01:26:24.046326    6169 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
W0817 01:27:14.231151    6209 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
W0817 01:27:24.273117    6209 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
W0817 01:27:34.306492    6209 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
W0817 01:27:44.344311    6209 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
W0817 01:27:54.387549    6209 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
W0817 01:28:04.437877    6209 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
W0817 01:28:14.486959    6209 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
W0817 01:28:24.523563    6209 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
W0817 01:28:34.573304    6209 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
W0817 01:28:44.613206    6209 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
W0817 01:28:54.653021    6209 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
W0817 01:29:04.694249    6209 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
W0817 01:29:14.743714    6209 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
W0817 01:29:24.780709    6209 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
W0817 01:29:34.828667    6209 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
W0817 01:29:44.865965    6209 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
W0817 01:29:54.900183    6209 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
W0817 01:30:04.942914    6209 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
W0817 01:30:14.981269    6209 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 31 lines ...
Pod	kube-system/ebs-csi-node-rpndn			system-node-critical pod "ebs-csi-node-rpndn" is pending
Pod	kube-system/ebs-csi-node-s6jzf			system-node-critical pod "ebs-csi-node-s6jzf" is pending
Pod	kube-system/ebs-csi-node-tkhsv			system-node-critical pod "ebs-csi-node-tkhsv" is pending
Pod	kube-system/kube-apiserver-i-087bfc3a86275513c	system-cluster-critical pod "kube-apiserver-i-087bfc3a86275513c" is pending
Pod	kube-system/kube-apiserver-i-0be35a916e88cfa8a	system-cluster-critical pod "kube-apiserver-i-0be35a916e88cfa8a" is pending

Validation Failed
W0817 01:30:29.999802    6209 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-ljlmz	system-cluster-critical pod "ebs-csi-controller-59c98fb857-ljlmz" is pending
Pod	kube-system/ebs-csi-node-kjkht			system-node-critical pod "ebs-csi-node-kjkht" is pending
Pod	kube-system/ebs-csi-node-rpndn			system-node-critical pod "ebs-csi-node-rpndn" is pending
Pod	kube-system/ebs-csi-node-s6jzf			system-node-critical pod "ebs-csi-node-s6jzf" is pending
Pod	kube-system/ebs-csi-node-tkhsv			system-node-critical pod "ebs-csi-node-tkhsv" is pending

Validation Failed
W0817 01:30:43.836704    6209 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 23 lines ...
Pod	kube-system/ebs-csi-controller-59c98fb857-dgwbg	system-cluster-critical pod "ebs-csi-controller-59c98fb857-dgwbg" is pending
Pod	kube-system/ebs-csi-controller-59c98fb857-ljlmz	system-cluster-critical pod "ebs-csi-controller-59c98fb857-ljlmz" is pending
Pod	kube-system/ebs-csi-node-kjkht			system-node-critical pod "ebs-csi-node-kjkht" is pending
Pod	kube-system/ebs-csi-node-rpndn			system-node-critical pod "ebs-csi-node-rpndn" is pending
Pod	kube-system/ebs-csi-node-s6jzf			system-node-critical pod "ebs-csi-node-s6jzf" is pending

Validation Failed
W0817 01:30:57.976616    6209 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 17 lines ...
Node	i-0c8a6f68c41e5029a		node "i-0c8a6f68c41e5029a" of role "node" is not ready
Pod	kube-system/calico-node-g8jkq	system-node-critical pod "calico-node-g8jkq" is pending
Pod	kube-system/calico-node-t7z54	system-node-critical pod "calico-node-t7z54" is pending
Pod	kube-system/ebs-csi-node-kjkht	system-node-critical pod "ebs-csi-node-kjkht" is pending
Pod	kube-system/ebs-csi-node-s6jzf	system-node-critical pod "ebs-csi-node-s6jzf" is pending

Validation Failed
W0817 01:31:11.960023    6209 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 15 lines ...
KIND	NAME				MESSAGE
Pod	kube-system/calico-node-g8jkq	system-node-critical pod "calico-node-g8jkq" is not ready (calico-node)
Pod	kube-system/calico-node-t7z54	system-node-critical pod "calico-node-t7z54" is not ready (calico-node)
Pod	kube-system/ebs-csi-node-kjkht	system-node-critical pod "ebs-csi-node-kjkht" is pending
Pod	kube-system/ebs-csi-node-s6jzf	system-node-critical pod "ebs-csi-node-s6jzf" is pending

Validation Failed
W0817 01:31:26.052049    6209 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-0f4f616a6f3633dd6	master	True

Your cluster e2e-e2e-kops-aws-misc-ha-euwest1.test-cncf-aws.k8s.io is ready
I0817 01:33:46.339207    6126 up.go:105] cluster reported as up
I0817 01:33:46.339276    6126 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
I0817 01:33:46.359457    6220 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true
F0817 01:33:48.178594    6220 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
I0817 01:33:48.181151    6126 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/59085070-1dcb-11ed-a994-1ec15ee5f766/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
I0817 01:33:48.181185    6126 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/59085070-1dcb-11ed-a994-1ec15ee5f766/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
I0817 01:34:47.059726    6126 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/59085070-1dcb-11ed-a994-1ec15ee5f766/kops get cluster --name e2e-e2e-kops-aws-misc-ha-euwest1.test-cncf-aws.k8s.io -o yaml
I0817 01:34:47.059763    6126 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/59085070-1dcb-11ed-a994-1ec15ee5f766/kops get cluster --name e2e-e2e-kops-aws-misc-ha-euwest1.test-cncf-aws.k8s.io -o yaml
I0817 01:34:47.601709    6126 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/59085070-1dcb-11ed-a994-1ec15ee5f766/kops get instancegroups --name e2e-e2e-kops-aws-misc-ha-euwest1.test-cncf-aws.k8s.io -o yaml
I0817 01:34:47.601748    6126 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/59085070-1dcb-11ed-a994-1ec15ee5f766/kops get instancegroups --name e2e-e2e-kops-aws-misc-ha-euwest1.test-cncf-aws.k8s.io -o yaml
... skipping 431 lines ...
route-table:rtb-0c7429936d53a2ed9	ok
vpc:vpc-017e5467653af92a7	ok
dhcp-options:dopt-030213f192fb46aa9	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