This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 1 succeeded
Started2022-08-08 22:53
Elapsed34m53s
Revisionmaster

No Test Failures!


Show 1 Passed Tests

Error lines from build-log.txt

... skipping 234 lines ...
I0808 22:54:27.802944    6325 app.go:62] pass rundir-in-artifacts flag True for RunDir to be part of Artifacts
I0808 22:54:27.802967    6325 app.go:64] RunDir for this run: "/home/prow/go/src/k8s.io/kops/_rundir/cd280120-176c-11ed-962a-a69410124b4c"
I0808 22:54:27.844916    6325 app.go:128] ID for this run: "cd280120-176c-11ed-962a-a69410124b4c"
I0808 22:54:27.845156    6325 local.go:42] ⚙️ ssh-keygen -t ed25519 -N  -q -f /tmp/kops/e2e-ed4da97961-6b857.test-cncf-aws.k8s.io/id_ed25519
I0808 22:54:27.854406    6325 dumplogs.go:45] /tmp/kops.wfUQN6dLX toolbox dump --name e2e-ed4da97961-6b857.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-ed4da97961-6b857.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
I0808 22:54:27.854455    6325 local.go:42] ⚙️ /tmp/kops.wfUQN6dLX toolbox dump --name e2e-ed4da97961-6b857.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-ed4da97961-6b857.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
W0808 22:54:28.349413    6325 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0808 22:54:28.349483    6325 down.go:48] /tmp/kops.wfUQN6dLX delete cluster --name e2e-ed4da97961-6b857.test-cncf-aws.k8s.io --yes
I0808 22:54:28.349492    6325 local.go:42] ⚙️ /tmp/kops.wfUQN6dLX delete cluster --name e2e-ed4da97961-6b857.test-cncf-aws.k8s.io --yes
I0808 22:54:28.382151    6345 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true
I0808 22:54:28.382246    6345 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-ed4da97961-6b857.test-cncf-aws.k8s.io" not found
Error: exit status 1
+ echo 'kubetest2 down failed'
kubetest2 down failed
+ [[ l == \v ]]
++ kops-base-from-marker latest
++ [[ latest =~ ^https: ]]
++ [[ latest == \l\a\t\e\s\t ]]
++ curl -s https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt
+ KOPS_BASE_URL=https://storage.googleapis.com/kops-ci/bin/1.25.0-alpha.3+v1.25.0-alpha.2-62-g82ec66a033
... skipping 14 lines ...
I0808 22:54:30.181498    6382 app.go:62] pass rundir-in-artifacts flag True for RunDir to be part of Artifacts
I0808 22:54:30.181541    6382 app.go:64] RunDir for this run: "/home/prow/go/src/k8s.io/kops/_rundir/cd280120-176c-11ed-962a-a69410124b4c"
I0808 22:54:30.205822    6382 app.go:128] ID for this run: "cd280120-176c-11ed-962a-a69410124b4c"
I0808 22:54:30.206105    6382 up.go:44] Cleaning up any leaked resources from previous cluster
I0808 22:54:30.206168    6382 dumplogs.go:45] /tmp/kops.ntZWtWLX4 toolbox dump --name e2e-ed4da97961-6b857.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-ed4da97961-6b857.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
I0808 22:54:30.206220    6382 local.go:42] ⚙️ /tmp/kops.ntZWtWLX4 toolbox dump --name e2e-ed4da97961-6b857.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-ed4da97961-6b857.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
W0808 22:54:30.707793    6382 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0808 22:54:30.707869    6382 down.go:48] /tmp/kops.ntZWtWLX4 delete cluster --name e2e-ed4da97961-6b857.test-cncf-aws.k8s.io --yes
I0808 22:54:30.707886    6382 local.go:42] ⚙️ /tmp/kops.ntZWtWLX4 delete cluster --name e2e-ed4da97961-6b857.test-cncf-aws.k8s.io --yes
I0808 22:54:30.745192    6402 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true
I0808 22:54:30.745323    6402 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-ed4da97961-6b857.test-cncf-aws.k8s.io" not found
I0808 22:54:31.287452    6382 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2022/08/08 22:54:31 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
I0808 22:54:31.302007    6382 http.go:37] curl https://ip.jsb.workers.dev
I0808 22:54:31.432563    6382 up.go:159] /tmp/kops.ntZWtWLX4 create cluster --name e2e-ed4da97961-6b857.test-cncf-aws.k8s.io --cloud aws --kubernetes-version v1.24.3 --ssh-public-key /tmp/kops/e2e-ed4da97961-6b857.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --networking calico --admin-access 34.68.225.152/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones us-west-2a --master-size c5.large
I0808 22:54:31.432627    6382 local.go:42] ⚙️ /tmp/kops.ntZWtWLX4 create cluster --name e2e-ed4da97961-6b857.test-cncf-aws.k8s.io --cloud aws --kubernetes-version v1.24.3 --ssh-public-key /tmp/kops/e2e-ed4da97961-6b857.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --networking calico --admin-access 34.68.225.152/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones us-west-2a --master-size c5.large
I0808 22:54:31.464039    6414 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true
I0808 22:54:31.464131    6414 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true
I0808 22:54:31.479432    6414 create_cluster.go:862] Using SSH public key: /tmp/kops/e2e-ed4da97961-6b857.test-cncf-aws.k8s.io/id_ed25519.pub
... skipping 525 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
W0808 22:55:15.568588    6454 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

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
W0808 22:55:25.601560    6454 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

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
W0808 22:55:35.657531    6454 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

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
W0808 22:55:45.708405    6454 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

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
W0808 22:55:55.742395    6454 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

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
W0808 22:56:05.775165    6454 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

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
W0808 22:56:15.813130    6454 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

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
W0808 22:56:25.854392    6454 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

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
W0808 22:56:35.892277    6454 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

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
W0808 22:56:45.940213    6454 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

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
W0808 22:56:55.988817    6454 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

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
W0808 22:57:06.041532    6454 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

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
W0808 22:57:16.081793    6454 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

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
W0808 22:57:26.120166    6454 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

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
W0808 22:57:36.159127    6454 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

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
W0808 22:57:46.207374    6454 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

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
W0808 22:57:56.239041    6454 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

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
W0808 22:58:06.272852    6454 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

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
W0808 22:58:16.307534    6454 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

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
W0808 22:58:26.359176    6454 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

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
W0808 22:58:36.449844    6454 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 19 lines ...
Pod	kube-system/coredns-autoscaler-f85cf5c-mbh8r	system-cluster-critical pod "coredns-autoscaler-f85cf5c-mbh8r" is pending
Pod	kube-system/ebs-csi-node-5jsnn			system-node-critical pod "ebs-csi-node-5jsnn" is pending
Pod	kube-system/ebs-csi-node-9rqs5			system-node-critical pod "ebs-csi-node-9rqs5" is pending
Pod	kube-system/ebs-csi-node-ntr29			system-node-critical pod "ebs-csi-node-ntr29" is pending
Pod	kube-system/ebs-csi-node-wdn5g			system-node-critical pod "ebs-csi-node-wdn5g" is pending

Validation Failed
W0808 22:58:48.449678    6454 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 17 lines ...
Pod	kube-system/coredns-5c44b6cf7d-9tqwn	system-cluster-critical pod "coredns-5c44b6cf7d-9tqwn" is pending
Pod	kube-system/ebs-csi-node-5jsnn		system-node-critical pod "ebs-csi-node-5jsnn" is pending
Pod	kube-system/ebs-csi-node-9rqs5		system-node-critical pod "ebs-csi-node-9rqs5" is pending
Pod	kube-system/ebs-csi-node-ntr29		system-node-critical pod "ebs-csi-node-ntr29" is pending
Pod	kube-system/ebs-csi-node-wdn5g		system-node-critical pod "ebs-csi-node-wdn5g" is pending

Validation Failed
W0808 22:58:59.944771    6454 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 14 lines ...
Pod	kube-system/calico-node-rx2nb	system-node-critical pod "calico-node-rx2nb" is pending
Pod	kube-system/calico-node-szqj6	system-node-critical pod "calico-node-szqj6" is pending
Pod	kube-system/ebs-csi-node-5jsnn	system-node-critical pod "ebs-csi-node-5jsnn" is pending
Pod	kube-system/ebs-csi-node-ntr29	system-node-critical pod "ebs-csi-node-ntr29" is pending
Pod	kube-system/ebs-csi-node-wdn5g	system-node-critical pod "ebs-csi-node-wdn5g" is pending

Validation Failed
W0808 22:59:11.379390    6454 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 14 lines ...
Pod	kube-system/calico-node-rx2nb	system-node-critical pod "calico-node-rx2nb" is pending
Pod	kube-system/calico-node-szqj6	system-node-critical pod "calico-node-szqj6" is pending
Pod	kube-system/ebs-csi-node-5jsnn	system-node-critical pod "ebs-csi-node-5jsnn" is pending
Pod	kube-system/ebs-csi-node-ntr29	system-node-critical pod "ebs-csi-node-ntr29" is pending
Pod	kube-system/ebs-csi-node-wdn5g	system-node-critical pod "ebs-csi-node-wdn5g" is pending

Validation Failed
W0808 22:59:22.887456    6454 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 11 lines ...
Pod	kube-system/calico-node-rx2nb	system-node-critical pod "calico-node-rx2nb" is not ready (calico-node)
Pod	kube-system/calico-node-szqj6	system-node-critical pod "calico-node-szqj6" is not ready (calico-node)
Pod	kube-system/ebs-csi-node-5jsnn	system-node-critical pod "ebs-csi-node-5jsnn" is pending
Pod	kube-system/ebs-csi-node-ntr29	system-node-critical pod "ebs-csi-node-ntr29" is pending
Pod	kube-system/ebs-csi-node-wdn5g	system-node-critical pod "ebs-csi-node-wdn5g" is pending

Validation Failed
W0808 22:59:34.422752    6454 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME				MESSAGE
Pod	kube-system/calico-node-czhc4	system-node-critical pod "calico-node-czhc4" is not ready (calico-node)
Pod	kube-system/ebs-csi-node-ntr29	system-node-critical pod "ebs-csi-node-ntr29" is pending

Validation Failed
W0808 22:59:45.866483    6454 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 6 lines ...
i-0c8de6d0fb5599277	master	True

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

Validation Failed
W0808 22:59:57.502612    6454 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 513 lines ...
evicting pod kube-system/calico-kube-controllers-75f4df896c-g8prc
evicting pod kube-system/dns-controller-6684cc95dc-cw6ht
I0808 23:04:32.314853    6571 instancegroups.go:660] Waiting for 5s for pods to stabilize after draining.
I0808 23:04:37.316061    6571 instancegroups.go:591] Stopping instance "i-0c8de6d0fb5599277", node "i-0c8de6d0fb5599277", in group "master-us-west-2a.masters.e2e-ed4da97961-6b857.test-cncf-aws.k8s.io" (this may take a while).
I0808 23:04:37.519265    6571 instancegroups.go:436] waiting for 15s after terminating instance
I0808 23:04:52.526662    6571 instancegroups.go:470] Validating the cluster.
I0808 23:04:52.657064    6571 instancegroups.go:516] Cluster did not validate, will retry in "30s": error listing nodes: Get "https://api.e2e-ed4da97961-6b857.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 35.87.203.68:443: connect: connection refused.
I0808 23:05:52.698564    6571 instancegroups.go:516] Cluster did not validate, will retry in "30s": error listing nodes: Get "https://api.e2e-ed4da97961-6b857.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 35.87.203.68:443: i/o timeout.
I0808 23:06:52.734322    6571 instancegroups.go:516] Cluster did not validate, will retry in "30s": error listing nodes: Get "https://api.e2e-ed4da97961-6b857.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 35.87.203.68:443: i/o timeout.
I0808 23:07:52.779343    6571 instancegroups.go:516] Cluster did not validate, will retry in "30s": error listing nodes: Get "https://api.e2e-ed4da97961-6b857.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 35.87.203.68:443: i/o timeout.
I0808 23:08:22.838605    6571 instancegroups.go:516] Cluster did not validate, will retry in "30s": unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-ed4da97961-6b857.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host.
I0808 23:08:54.836912    6571 instancegroups.go:526] Cluster did not pass validation, will retry in "30s": node "i-0c77b6cf18de15d71" of role "node" is not ready, system-cluster-critical pod "calico-kube-controllers-75f4df896c-6whpx" is not ready (calico-kube-controllers), system-cluster-critical pod "ebs-csi-controller-5b4bd8874c-jzz8v" is not ready (ebs-plugin).
I0808 23:09:26.299382    6571 instancegroups.go:506] Cluster validated; revalidating in 10s to make sure it does not flap.
I0808 23:09:37.701404    6571 instancegroups.go:503] Cluster validated.
I0808 23:09:37.701464    6571 instancegroups.go:470] Validating the cluster.
I0808 23:09:38.928434    6571 instancegroups.go:503] Cluster validated.
... skipping 9 lines ...
I0808 23:12:14.097552    6571 instancegroups.go:503] Cluster validated.
I0808 23:12:14.097623    6571 instancegroups.go:400] Draining the node: "i-015c7da20ba7ffb2c".
WARNING: ignoring DaemonSet-managed Pods: kube-system/calico-node-24hp5, kube-system/ebs-csi-node-9rqs5
evicting pod kube-system/coredns-autoscaler-f85cf5c-mbh8r
evicting pod kube-system/coredns-5c44b6cf7d-9tqwn
evicting pod kube-system/coredns-5c44b6cf7d-gc4jj
error when evicting pods/"coredns-5c44b6cf7d-9tqwn" -n "kube-system" (will retry after 5s): Cannot evict pod as it would violate the pod's disruption budget.
evicting pod kube-system/coredns-5c44b6cf7d-9tqwn
I0808 23:12:26.407393    6571 instancegroups.go:660] Waiting for 5s for pods to stabilize after draining.
I0808 23:12:31.410928    6571 instancegroups.go:591] Stopping instance "i-015c7da20ba7ffb2c", node "i-015c7da20ba7ffb2c", in group "nodes-us-west-2a.e2e-ed4da97961-6b857.test-cncf-aws.k8s.io" (this may take a while).
I0808 23:12:31.627715    6571 instancegroups.go:436] waiting for 15s after terminating instance
I0808 23:12:46.627985    6571 instancegroups.go:470] Validating the cluster.
I0808 23:12:48.405522    6571 instancegroups.go:526] Cluster did not pass validation, will retry in "30s": InstanceGroup "nodes-us-west-2a" did not have enough nodes 3 vs 4.
... skipping 85 lines ...
I0808 23:25:28.985847    6620 app.go:62] pass rundir-in-artifacts flag True for RunDir to be part of Artifacts
I0808 23:25:28.985896    6620 app.go:64] RunDir for this run: "/home/prow/go/src/k8s.io/kops/_rundir/cd280120-176c-11ed-962a-a69410124b4c"
I0808 23:25:28.989934    6620 app.go:128] ID for this run: "cd280120-176c-11ed-962a-a69410124b4c"
I0808 23:25:28.989974    6620 local.go:42] ⚙️ /home/prow/go/bin/kubetest2-tester-kops --test-package-version=https://storage.googleapis.com/k8s-release-dev/ci/v1.25.0-beta.0.24+759785ea147bc1 --parallel 25
I0808 23:25:29.017954    6638 kubectl.go:148] gsutil cp gs://kubernetes-release/release/https://storage.googleapis.com/k8s-release-dev/ci/v1.25.0-beta.0.24+759785ea147bc1/kubernetes-client-linux-amd64.tar.gz /root/.cache/kubernetes-client-linux-amd64.tar.gz
CommandException: No URLs matched: gs://kubernetes-release/release/https://storage.googleapis.com/k8s-release-dev/ci/v1.25.0-beta.0.24+759785ea147bc1/kubernetes-client-linux-amd64.tar.gz
F0808 23:25:31.811301    6638 tester.go:482] failed to run ginkgo tester: failed to get kubectl package from published releases: failed to download release tar kubernetes-client-linux-amd64.tar.gz for release https://storage.googleapis.com/k8s-release-dev/ci/v1.25.0-beta.0.24+759785ea147bc1: exit status 1
Error: exit status 255
+ kops-finish
+ kubetest2 kops -v=2 --cloud-provider=aws --cluster-name=e2e-ed4da97961-6b857.test-cncf-aws.k8s.io --kops-root=/home/prow/go/src/k8s.io/kops --admin-access= --env=KOPS_FEATURE_FLAGS=SpecOverrideFlag --kops-binary-path=/tmp/kops.wfUQN6dLX --down
I0808 23:25:31.849669    6829 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true
I0808 23:25:31.853220    6829 app.go:61] The files in RunDir shall not be part of Artifacts
I0808 23:25:31.853254    6829 app.go:62] pass rundir-in-artifacts flag True for RunDir to be part of Artifacts
I0808 23:25:31.853291    6829 app.go:64] RunDir for this run: "/home/prow/go/src/k8s.io/kops/_rundir/cd280120-176c-11ed-962a-a69410124b4c"
... skipping 288 lines ...