This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultNot Finished
Started2022-08-16 17:25
Revision

Test Failures


kubetest2 Test 2.54s

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 ...
I0816 17:26:35.292173    6139 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt
I0816 17:26:35.293947    6139 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
I0816 17:26:36.020187    6139 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
I0816 17:26:36.033187    6139 up.go:44] Cleaning up any leaked resources from previous cluster
I0816 17:26:36.033288    6139 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/584be5fa-1d88-11ed-83e0-3ab8bc69b7f6/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
I0816 17:26:36.033320    6139 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/584be5fa-1d88-11ed-83e0-3ab8bc69b7f6/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
W0816 17:26:36.521795    6139 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0816 17:26:36.521844    6139 down.go:48] /home/prow/go/src/k8s.io/kops/_rundir/584be5fa-1d88-11ed-83e0-3ab8bc69b7f6/kops delete cluster --name e2e-e2e-kops-aws-misc-ha-euwest1.test-cncf-aws.k8s.io --yes
I0816 17:26:36.521858    6139 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/584be5fa-1d88-11ed-83e0-3ab8bc69b7f6/kops delete cluster --name e2e-e2e-kops-aws-misc-ha-euwest1.test-cncf-aws.k8s.io --yes
I0816 17:26:36.555040    6172 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
I0816 17:26:37.046835    6139 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2022/08/16 17:26:37 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
I0816 17:26:37.061549    6139 http.go:37] curl https://ip.jsb.workers.dev
I0816 17:26:37.208520    6139 up.go:159] /home/prow/go/src/k8s.io/kops/_rundir/584be5fa-1d88-11ed-83e0-3ab8bc69b7f6/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 34.136.249.216/32 --master-volume-size 48 --node-count 4 --node-volume-size 48 --master-size c5.large
I0816 17:26:37.208559    6139 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/584be5fa-1d88-11ed-83e0-3ab8bc69b7f6/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 34.136.249.216/32 --master-volume-size 48 --node-count 4 --node-volume-size 48 --master-size c5.large
I0816 17:26:37.243022    6182 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true
I0816 17:26:37.262551    6182 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
I0816 17:26:37.827093    6182 new_cluster.go:1168]  Cloud Provider ID = aws
... skipping 820 lines ...

I0816 17:27:27.601432    6139 up.go:243] /home/prow/go/src/k8s.io/kops/_rundir/584be5fa-1d88-11ed-83e0-3ab8bc69b7f6/kops validate cluster --name e2e-e2e-kops-aws-misc-ha-euwest1.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0816 17:27:27.601532    6139 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/584be5fa-1d88-11ed-83e0-3ab8bc69b7f6/kops validate cluster --name e2e-e2e-kops-aws-misc-ha-euwest1.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0816 17:27:27.672760    6224 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-e2e-kops-aws-misc-ha-euwest1.test-cncf-aws.k8s.io

W0816 17:27:29.399999    6224 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-e2e-kops-aws-misc-ha-euwest1.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
master-eu-west-1b	Master	c5.large	1	1	eu-west-1b
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
... skipping 2 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
W0816 17:27:39.442016    6224 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
W0816 17:27:49.478921    6224 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
W0816 17:27:59.533217    6224 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
W0816 17:28:09.570308    6224 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
W0816 17:28:19.602601    6224 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
W0816 17:28:29.637608    6224 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
W0816 17:28:39.685721    6224 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
W0816 17:28:49.728941    6224 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
W0816 17:28:59.768619    6224 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
W0816 17:29:09.810076    6224 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
W0816 17:29:19.845339    6224 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
W0816 17:29:29.885819    6224 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
W0816 17:29:39.926461    6224 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
W0816 17:29:49.976714    6224 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
W0816 17:30:00.009910    6224 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
W0816 17:30:10.056258    6224 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
W0816 17:30:20.108187    6224 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
W0816 17:30:30.150258    6224 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
W0816 17:30:40.188503    6224 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
W0816 17:30:50.221878    6224 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
W0816 17:31:00.256352    6224 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
W0816 17:31:10.293993    6224 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-2wsx8			system-node-critical pod "ebs-csi-node-2wsx8" is pending
Pod	kube-system/ebs-csi-node-49mgp			system-node-critical pod "ebs-csi-node-49mgp" is pending
Pod	kube-system/ebs-csi-node-ht2gn			system-node-critical pod "ebs-csi-node-ht2gn" is pending
Pod	kube-system/ebs-csi-node-x5frj			system-node-critical pod "ebs-csi-node-x5frj" is pending
Pod	kube-system/kube-apiserver-i-0724eba8959f62597	system-cluster-critical pod "kube-apiserver-i-0724eba8959f62597" is pending

Validation Failed
W0816 17:31:25.033640    6224 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-node-2wsx8			system-node-critical pod "ebs-csi-node-2wsx8" is pending
Pod	kube-system/ebs-csi-node-49mgp			system-node-critical pod "ebs-csi-node-49mgp" is pending
Pod	kube-system/ebs-csi-node-ht2gn			system-node-critical pod "ebs-csi-node-ht2gn" is pending
Pod	kube-system/ebs-csi-node-x5frj			system-node-critical pod "ebs-csi-node-x5frj" is pending
Pod	kube-system/kube-scheduler-i-0870d22e87bdefe70	system-cluster-critical pod "kube-scheduler-i-0870d22e87bdefe70" is pending

Validation Failed
W0816 17:31:39.136163    6224 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 22 lines ...
Pod	kube-system/ebs-csi-controller-59c98fb857-dsk8m	system-cluster-critical pod "ebs-csi-controller-59c98fb857-dsk8m" is pending
Pod	kube-system/ebs-csi-controller-59c98fb857-j9h5c	system-cluster-critical pod "ebs-csi-controller-59c98fb857-j9h5c" is pending
Pod	kube-system/ebs-csi-node-2wsx8			system-node-critical pod "ebs-csi-node-2wsx8" is pending
Pod	kube-system/ebs-csi-node-49mgp			system-node-critical pod "ebs-csi-node-49mgp" is pending
Pod	kube-system/ebs-csi-node-ht2gn			system-node-critical pod "ebs-csi-node-ht2gn" is pending

Validation Failed
W0816 17:31:52.989320    6224 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 19 lines ...
Pod	kube-system/calico-node-s6jx7			system-node-critical pod "calico-node-s6jx7" is not ready (calico-node)
Pod	kube-system/ebs-csi-controller-59c98fb857-j9h5c	system-cluster-critical pod "ebs-csi-controller-59c98fb857-j9h5c" is pending
Pod	kube-system/ebs-csi-node-2wsx8			system-node-critical pod "ebs-csi-node-2wsx8" is pending
Pod	kube-system/ebs-csi-node-49mgp			system-node-critical pod "ebs-csi-node-49mgp" is pending
Pod	kube-system/ebs-csi-node-ht2gn			system-node-critical pod "ebs-csi-node-ht2gn" is pending

Validation Failed
W0816 17:32:06.980686    6224 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-64z7z			system-node-critical pod "calico-node-64z7z" is not ready (calico-node)
Pod	kube-system/calico-node-s6jx7			system-node-critical pod "calico-node-s6jx7" is not ready (calico-node)
Pod	kube-system/ebs-csi-controller-59c98fb857-j9h5c	system-cluster-critical pod "ebs-csi-controller-59c98fb857-j9h5c" is pending

Validation Failed
W0816 17:32:21.040113    6224 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 12 lines ...
i-0fb8c880752bb4875	node	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/kube-proxy-i-0f3d3d6102b246734	system-node-critical pod "kube-proxy-i-0f3d3d6102b246734" is pending

Validation Failed
W0816 17:32:35.007471    6224 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-0fb8c880752bb4875	node	True

Your cluster e2e-e2e-kops-aws-misc-ha-euwest1.test-cncf-aws.k8s.io is ready
I0816 17:34:55.933972    6139 up.go:105] cluster reported as up
I0816 17:34:55.934486    6139 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
I0816 17:34:55.958009    6234 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true
F0816 17:34:58.475661    6234 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
I0816 17:34:58.479586    6139 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/584be5fa-1d88-11ed-83e0-3ab8bc69b7f6/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
I0816 17:34:58.479640    6139 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/584be5fa-1d88-11ed-83e0-3ab8bc69b7f6/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
I0816 17:35:58.205956    6139 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/584be5fa-1d88-11ed-83e0-3ab8bc69b7f6/kops get cluster --name e2e-e2e-kops-aws-misc-ha-euwest1.test-cncf-aws.k8s.io -o yaml
I0816 17:35:58.206019    6139 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/584be5fa-1d88-11ed-83e0-3ab8bc69b7f6/kops get cluster --name e2e-e2e-kops-aws-misc-ha-euwest1.test-cncf-aws.k8s.io -o yaml
I0816 17:35:58.767406    6139 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/584be5fa-1d88-11ed-83e0-3ab8bc69b7f6/kops get instancegroups --name e2e-e2e-kops-aws-misc-ha-euwest1.test-cncf-aws.k8s.io -o yaml
I0816 17:35:58.767452    6139 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/584be5fa-1d88-11ed-83e0-3ab8bc69b7f6/kops get instancegroups --name e2e-e2e-kops-aws-misc-ha-euwest1.test-cncf-aws.k8s.io -o yaml
... skipping 451 lines ...
route-table:rtb-02916957ced532bfa	ok
vpc:vpc-0460c2a3f7959217e	ok
dhcp-options:dopt-0673e3996c939d6fc	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