This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 1 succeeded
Started2022-08-15 09:03
Elapsed40m9s
Revisionmaster

No Test Failures!


Show 1 Passed Tests

Error lines from build-log.txt

... skipping 224 lines ...
I0815 09:05:03.349439    6303 app.go:62] pass rundir-in-artifacts flag True for RunDir to be part of Artifacts
I0815 09:05:03.349471    6303 app.go:64] RunDir for this run: "/home/prow/go/src/k8s.io/kops/_rundir/10c2e06b-1c79-11ed-9820-1e463d3c6692"
I0815 09:05:03.393196    6303 app.go:128] ID for this run: "10c2e06b-1c79-11ed-9820-1e463d3c6692"
I0815 09:05:03.393688    6303 local.go:42] ⚙️ ssh-keygen -t ed25519 -N  -q -f /tmp/kops/e2e-c668105d47-ed761.test-cncf-aws.k8s.io/id_ed25519
I0815 09:05:03.403609    6303 dumplogs.go:45] /tmp/kops.knyaIRX6r toolbox dump --name e2e-c668105d47-ed761.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-c668105d47-ed761.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
I0815 09:05:03.403657    6303 local.go:42] ⚙️ /tmp/kops.knyaIRX6r toolbox dump --name e2e-c668105d47-ed761.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-c668105d47-ed761.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
W0815 09:05:03.906084    6303 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0815 09:05:03.906128    6303 down.go:48] /tmp/kops.knyaIRX6r delete cluster --name e2e-c668105d47-ed761.test-cncf-aws.k8s.io --yes
I0815 09:05:03.906140    6303 local.go:42] ⚙️ /tmp/kops.knyaIRX6r delete cluster --name e2e-c668105d47-ed761.test-cncf-aws.k8s.io --yes
I0815 09:05:03.946847    6323 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true
I0815 09:05:03.946939    6323 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-c668105d47-ed761.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-85-g429ebecdca
... skipping 14 lines ...
I0815 09:05:05.747353    6359 app.go:62] pass rundir-in-artifacts flag True for RunDir to be part of Artifacts
I0815 09:05:05.747461    6359 app.go:64] RunDir for this run: "/home/prow/go/src/k8s.io/kops/_rundir/10c2e06b-1c79-11ed-9820-1e463d3c6692"
I0815 09:05:05.782478    6359 app.go:128] ID for this run: "10c2e06b-1c79-11ed-9820-1e463d3c6692"
I0815 09:05:05.782789    6359 up.go:44] Cleaning up any leaked resources from previous cluster
I0815 09:05:05.782876    6359 dumplogs.go:45] /tmp/kops.aLtoOYxr9 toolbox dump --name e2e-c668105d47-ed761.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-c668105d47-ed761.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
I0815 09:05:05.782918    6359 local.go:42] ⚙️ /tmp/kops.aLtoOYxr9 toolbox dump --name e2e-c668105d47-ed761.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-c668105d47-ed761.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
W0815 09:05:06.294136    6359 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0815 09:05:06.294206    6359 down.go:48] /tmp/kops.aLtoOYxr9 delete cluster --name e2e-c668105d47-ed761.test-cncf-aws.k8s.io --yes
I0815 09:05:06.294223    6359 local.go:42] ⚙️ /tmp/kops.aLtoOYxr9 delete cluster --name e2e-c668105d47-ed761.test-cncf-aws.k8s.io --yes
I0815 09:05:06.339479    6377 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true
I0815 09:05:06.339602    6377 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-c668105d47-ed761.test-cncf-aws.k8s.io" not found
I0815 09:05:06.861973    6359 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2022/08/15 09:05:06 failed to get external ip from metadata service: http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip returned 404
I0815 09:05:06.880223    6359 http.go:37] curl https://ip.jsb.workers.dev
I0815 09:05:06.993837    6359 up.go:159] /tmp/kops.aLtoOYxr9 create cluster --name e2e-c668105d47-ed761.test-cncf-aws.k8s.io --cloud aws --kubernetes-version v1.20.6 --ssh-public-key /tmp/kops/e2e-c668105d47-ed761.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --networking calico --admin-access 35.226.238.237/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones eu-west-2a --master-size c5.large
I0815 09:05:06.994015    6359 local.go:42] ⚙️ /tmp/kops.aLtoOYxr9 create cluster --name e2e-c668105d47-ed761.test-cncf-aws.k8s.io --cloud aws --kubernetes-version v1.20.6 --ssh-public-key /tmp/kops/e2e-c668105d47-ed761.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --networking calico --admin-access 35.226.238.237/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones eu-west-2a --master-size c5.large
I0815 09:05:07.026121    6387 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true
I0815 09:05:07.026213    6387 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true
I0815 09:05:07.044970    6387 create_cluster.go:862] Using SSH public key: /tmp/kops/e2e-c668105d47-ed761.test-cncf-aws.k8s.io/id_ed25519.pub
... skipping 555 lines ...

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0815 09:05:51.876326    6426 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-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
W0815 09:06:01.911704    6426 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-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
W0815 09:06:11.951767    6426 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-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
W0815 09:06:21.997871    6426 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-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
W0815 09:06:32.032474    6426 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-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
W0815 09:06:42.074050    6426 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-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
W0815 09:06:52.120036    6426 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-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
W0815 09:07:02.167634    6426 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-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
W0815 09:07:12.216549    6426 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-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
W0815 09:07:22.251219    6426 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-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
W0815 09:07:32.286418    6426 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-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
W0815 09:07:42.331666    6426 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-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
W0815 09:07:52.374102    6426 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-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
W0815 09:08:02.407113    6426 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-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
W0815 09:08:12.463145    6426 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-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
W0815 09:08:22.495635    6426 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-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
W0815 09:08:32.534129    6426 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-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
W0815 09:08:42.568149    6426 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-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
W0815 09:08:52.605000    6426 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-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
W0815 09:09:02.646713    6426 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-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
W0815 09:09:12.680084    6426 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-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
W0815 09:09:22.718236    6426 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-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
W0815 09:09:32.761889    6426 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 15 lines ...
Pod	kube-system/calico-node-zdw22						system-node-critical pod "calico-node-zdw22" is pending
Pod	kube-system/coredns-696464bdb8-nspp6					system-cluster-critical pod "coredns-696464bdb8-nspp6" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-7pnhl				system-cluster-critical pod "coredns-autoscaler-6658b4bf85-7pnhl" is pending
Pod	kube-system/kube-proxy-ip-172-20-48-112.eu-west-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-48-112.eu-west-2.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-59-71.eu-west-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-59-71.eu-west-2.compute.internal" is pending

Validation Failed
W0815 09:09:45.444893    6426 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 17 lines ...
Pod	kube-system/calico-node-zdw22						system-node-critical pod "calico-node-zdw22" is pending
Pod	kube-system/coredns-696464bdb8-nspp6					system-cluster-critical pod "coredns-696464bdb8-nspp6" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-7pnhl				system-cluster-critical pod "coredns-autoscaler-6658b4bf85-7pnhl" is pending
Pod	kube-system/kube-proxy-ip-172-20-42-151.eu-west-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-42-151.eu-west-2.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-54-224.eu-west-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-54-224.eu-west-2.compute.internal" is pending

Validation Failed
W0815 09:09:57.251946    6426 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 13 lines ...
Pod	kube-system/calico-node-6th92			system-node-critical pod "calico-node-6th92" is pending
Pod	kube-system/calico-node-pxbzm			system-node-critical pod "calico-node-pxbzm" is not ready (calico-node)
Pod	kube-system/calico-node-zdw22			system-node-critical pod "calico-node-zdw22" is pending
Pod	kube-system/coredns-696464bdb8-nspp6		system-cluster-critical pod "coredns-696464bdb8-nspp6" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-7pnhl	system-cluster-critical pod "coredns-autoscaler-6658b4bf85-7pnhl" is pending

Validation Failed
W0815 09:10:09.112102    6426 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 10 lines ...
Pod	kube-system/calico-node-45q8p		system-node-critical pod "calico-node-45q8p" is not ready (calico-node)
Pod	kube-system/calico-node-6th92		system-node-critical pod "calico-node-6th92" is not ready (calico-node)
Pod	kube-system/calico-node-zdw22		system-node-critical pod "calico-node-zdw22" is not ready (calico-node)
Pod	kube-system/coredns-696464bdb8-lnrht	system-cluster-critical pod "coredns-696464bdb8-lnrht" is not ready (coredns)
Pod	kube-system/coredns-696464bdb8-nspp6	system-cluster-critical pod "coredns-696464bdb8-nspp6" is pending

Validation Failed
W0815 09:10:20.973441    6426 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 509 lines ...
evicting pod kube-system/dns-controller-6cdd4f9c8c-lx6d2
evicting pod kube-system/calico-kube-controllers-57fd98f9d9-m9rgk
I0815 09:15:11.669821    6536 instancegroups.go:660] Waiting for 5s for pods to stabilize after draining.
I0815 09:15:16.671639    6536 instancegroups.go:591] Stopping instance "i-03daf4b55a92ef5ed", node "ip-172-20-54-187.eu-west-2.compute.internal", in group "master-eu-west-2a.masters.e2e-c668105d47-ed761.test-cncf-aws.k8s.io" (this may take a while).
I0815 09:15:16.926728    6536 instancegroups.go:436] waiting for 15s after terminating instance
I0815 09:15:31.926952    6536 instancegroups.go:470] Validating the cluster.
I0815 09:16:01.968175    6536 instancegroups.go:516] Cluster did not validate, will retry in "30s": error listing nodes: Get "https://api.e2e-c668105d47-ed761.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 3.9.139.203:443: i/o timeout.
I0815 09:17:02.020723    6536 instancegroups.go:516] Cluster did not validate, will retry in "30s": error listing nodes: Get "https://api.e2e-c668105d47-ed761.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 3.9.139.203:443: i/o timeout.
I0815 09:18:02.058866    6536 instancegroups.go:516] Cluster did not validate, will retry in "30s": error listing nodes: Get "https://api.e2e-c668105d47-ed761.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 3.9.139.203:443: i/o timeout.
I0815 09:19:02.112882    6536 instancegroups.go:516] Cluster did not validate, will retry in "30s": error listing nodes: Get "https://api.e2e-c668105d47-ed761.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 3.9.139.203:443: i/o timeout.
I0815 09:20:02.155891    6536 instancegroups.go:516] Cluster did not validate, will retry in "30s": error listing nodes: Get "https://api.e2e-c668105d47-ed761.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 3.9.139.203:443: i/o timeout.
I0815 09:21:02.211474    6536 instancegroups.go:516] Cluster did not validate, will retry in "30s": error listing nodes: Get "https://api.e2e-c668105d47-ed761.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 3.9.139.203:443: i/o timeout.
I0815 09:22:02.256414    6536 instancegroups.go:516] Cluster did not validate, will retry in "30s": error listing nodes: Get "https://api.e2e-c668105d47-ed761.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 3.9.139.203:443: i/o timeout.
I0815 09:22:34.877854    6536 instancegroups.go:526] Cluster did not pass validation, will retry in "30s": node "ip-172-20-54-224.eu-west-2.compute.internal" of role "node" is not ready, node "ip-172-20-42-151.eu-west-2.compute.internal" of role "node" is not ready, system-cluster-critical pod "calico-kube-controllers-57fd98f9d9-f7hn7" is not ready (calico-kube-controllers).
I0815 09:23:06.638639    6536 instancegroups.go:526] Cluster did not pass validation, will retry in "30s": system-cluster-critical pod "calico-kube-controllers-57fd98f9d9-f7hn7" is not ready (calico-kube-controllers).
I0815 09:23:38.468241    6536 instancegroups.go:506] Cluster validated; revalidating in 10s to make sure it does not flap.
I0815 09:23:50.242491    6536 instancegroups.go:503] Cluster validated.
I0815 09:23:50.242688    6536 instancegroups.go:470] Validating the cluster.
I0815 09:23:51.703980    6536 instancegroups.go:503] Cluster validated.
... skipping 109 lines ...
I0815 09:39:30.352564    6584 app.go:128] ID for this run: "10c2e06b-1c79-11ed-9820-1e463d3c6692"
I0815 09:39:30.352629    6584 local.go:42] ⚙️ /home/prow/go/bin/kubetest2-tester-kops --test-package-version=v1.21.7 --parallel 25
I0815 09:39:30.370453    6606 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true
I0815 09:39:30.376917    6606 kubectl.go:148] gsutil cp gs://kubernetes-release/release/v1.21.7/kubernetes-client-linux-amd64.tar.gz /root/.cache/kubernetes-client-linux-amd64.tar.gz
Your credentials are invalid. Please run
$ gcloud auth login
F0815 09:39:31.943740    6606 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 v1.21.7: exit status 1
Error: exit status 255
+ kops-finish
+ kubetest2 kops -v=2 --cloud-provider=aws --cluster-name=e2e-c668105d47-ed761.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.knyaIRX6r --down
I0815 09:39:31.978466    6794 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true
I0815 09:39:31.979447    6794 app.go:61] The files in RunDir shall not be part of Artifacts
I0815 09:39:31.979466    6794 app.go:62] pass rundir-in-artifacts flag True for RunDir to be part of Artifacts
I0815 09:39:31.979489    6794 app.go:64] RunDir for this run: "/home/prow/go/src/k8s.io/kops/_rundir/10c2e06b-1c79-11ed-9820-1e463d3c6692"
... skipping 342 lines ...