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

No Test Failures!


Show 1 Passed Tests

Error lines from build-log.txt

... skipping 234 lines ...
I0810 13:54:15.839553    6285 app.go:62] pass rundir-in-artifacts flag True for RunDir to be part of Artifacts
I0810 13:54:15.839579    6285 app.go:64] RunDir for this run: "/home/prow/go/src/k8s.io/kops/_rundir/ada24aab-18b3-11ed-a3cd-9a8e9eec334c"
I0810 13:54:15.876984    6285 app.go:128] ID for this run: "ada24aab-18b3-11ed-a3cd-9a8e9eec334c"
I0810 13:54:15.877352    6285 local.go:42] ⚙️ ssh-keygen -t ed25519 -N  -q -f /tmp/kops/e2e-ed4da97961-6b857.test-cncf-aws.k8s.io/id_ed25519
I0810 13:54:15.889295    6285 dumplogs.go:45] /tmp/kops.ydECsNwb0 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
I0810 13:54:15.889460    6285 local.go:42] ⚙️ /tmp/kops.ydECsNwb0 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
W0810 13:54:16.402918    6285 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0810 13:54:16.402963    6285 down.go:48] /tmp/kops.ydECsNwb0 delete cluster --name e2e-ed4da97961-6b857.test-cncf-aws.k8s.io --yes
I0810 13:54:16.402975    6285 local.go:42] ⚙️ /tmp/kops.ydECsNwb0 delete cluster --name e2e-ed4da97961-6b857.test-cncf-aws.k8s.io --yes
I0810 13:54:16.433757    6306 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true
I0810 13:54:16.433958    6306 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-70-g53eb302e26
... skipping 14 lines ...
I0810 13:54:18.257816    6344 app.go:62] pass rundir-in-artifacts flag True for RunDir to be part of Artifacts
I0810 13:54:18.257842    6344 app.go:64] RunDir for this run: "/home/prow/go/src/k8s.io/kops/_rundir/ada24aab-18b3-11ed-a3cd-9a8e9eec334c"
I0810 13:54:18.309961    6344 app.go:128] ID for this run: "ada24aab-18b3-11ed-a3cd-9a8e9eec334c"
I0810 13:54:18.310050    6344 up.go:44] Cleaning up any leaked resources from previous cluster
I0810 13:54:18.310103    6344 dumplogs.go:45] /tmp/kops.DiqpZoTY6 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
I0810 13:54:18.310150    6344 local.go:42] ⚙️ /tmp/kops.DiqpZoTY6 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
W0810 13:54:18.785909    6344 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0810 13:54:18.785955    6344 down.go:48] /tmp/kops.DiqpZoTY6 delete cluster --name e2e-ed4da97961-6b857.test-cncf-aws.k8s.io --yes
I0810 13:54:18.785970    6344 local.go:42] ⚙️ /tmp/kops.DiqpZoTY6 delete cluster --name e2e-ed4da97961-6b857.test-cncf-aws.k8s.io --yes
I0810 13:54:18.816555    6365 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true
I0810 13:54:18.816658    6365 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
I0810 13:54:19.272418    6344 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2022/08/10 13:54:19 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
I0810 13:54:19.285899    6344 http.go:37] curl https://ip.jsb.workers.dev
I0810 13:54:19.419110    6344 up.go:159] /tmp/kops.DiqpZoTY6 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.70.205.183/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones us-west-1a --master-size c5.large
I0810 13:54:19.419178    6344 local.go:42] ⚙️ /tmp/kops.DiqpZoTY6 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.70.205.183/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones us-west-1a --master-size c5.large
I0810 13:54:19.449470    6377 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true
I0810 13:54:19.449678    6377 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true
I0810 13:54:19.466703    6377 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
W0810 13:55:02.326234    6417 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

... skipping 18 lines ...
Pod	kube-system/coredns-autoscaler-f85cf5c-v2bn4	system-cluster-critical pod "coredns-autoscaler-f85cf5c-v2bn4" is pending
Pod	kube-system/ebs-csi-node-cr6z7			system-node-critical pod "ebs-csi-node-cr6z7" is pending
Pod	kube-system/ebs-csi-node-d7f28			system-node-critical pod "ebs-csi-node-d7f28" is pending
Pod	kube-system/ebs-csi-node-qv4p9			system-node-critical pod "ebs-csi-node-qv4p9" is pending
Pod	kube-system/ebs-csi-node-tkmv9			system-node-critical pod "ebs-csi-node-tkmv9" is pending

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

... skipping 19 lines ...
Pod	kube-system/coredns-autoscaler-f85cf5c-v2bn4	system-cluster-critical pod "coredns-autoscaler-f85cf5c-v2bn4" is pending
Pod	kube-system/ebs-csi-node-cr6z7			system-node-critical pod "ebs-csi-node-cr6z7" is pending
Pod	kube-system/ebs-csi-node-d7f28			system-node-critical pod "ebs-csi-node-d7f28" is pending
Pod	kube-system/ebs-csi-node-qv4p9			system-node-critical pod "ebs-csi-node-qv4p9" is pending
Pod	kube-system/ebs-csi-node-tkmv9			system-node-critical pod "ebs-csi-node-tkmv9" is pending

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

... skipping 18 lines ...
Pod	kube-system/coredns-autoscaler-f85cf5c-v2bn4	system-cluster-critical pod "coredns-autoscaler-f85cf5c-v2bn4" is pending
Pod	kube-system/ebs-csi-node-cr6z7			system-node-critical pod "ebs-csi-node-cr6z7" is pending
Pod	kube-system/ebs-csi-node-d7f28			system-node-critical pod "ebs-csi-node-d7f28" is pending
Pod	kube-system/ebs-csi-node-qv4p9			system-node-critical pod "ebs-csi-node-qv4p9" is pending
Pod	kube-system/ebs-csi-node-tkmv9			system-node-critical pod "ebs-csi-node-tkmv9" is pending

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

... skipping 15 lines ...
Pod	kube-system/calico-node-q24ql	system-node-critical pod "calico-node-q24ql" is pending
Pod	kube-system/ebs-csi-node-cr6z7	system-node-critical pod "ebs-csi-node-cr6z7" is pending
Pod	kube-system/ebs-csi-node-d7f28	system-node-critical pod "ebs-csi-node-d7f28" is pending
Pod	kube-system/ebs-csi-node-qv4p9	system-node-critical pod "ebs-csi-node-qv4p9" is pending
Pod	kube-system/ebs-csi-node-tkmv9	system-node-critical pod "ebs-csi-node-tkmv9" is pending

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

... skipping 13 lines ...
Pod	kube-system/ebs-csi-node-d7f28			system-node-critical pod "ebs-csi-node-d7f28" is pending
Pod	kube-system/ebs-csi-node-qv4p9			system-node-critical pod "ebs-csi-node-qv4p9" is pending
Pod	kube-system/ebs-csi-node-tkmv9			system-node-critical pod "ebs-csi-node-tkmv9" is pending
Pod	kube-system/kube-proxy-i-01f6b15c3d10423ce	system-node-critical pod "kube-proxy-i-01f6b15c3d10423ce" is pending
Pod	kube-system/kube-proxy-i-0f10fb9fae6c6a89f	system-node-critical pod "kube-proxy-i-0f10fb9fae6c6a89f" is pending

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

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME				MESSAGE
Pod	kube-system/ebs-csi-node-d7f28	system-node-critical pod "ebs-csi-node-d7f28" is pending
Pod	kube-system/ebs-csi-node-qv4p9	system-node-critical pod "ebs-csi-node-qv4p9" is pending

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

... skipping 6 lines ...
i-0f10fb9fae6c6a89f	node	True

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

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

... skipping 548 lines ...
evicting pod kube-system/dns-controller-6684cc95dc-52blt
evicting pod kube-system/calico-kube-controllers-75f4df896c-qlzwc
I0810 14:03:50.261616    6529 instancegroups.go:660] Waiting for 5s for pods to stabilize after draining.
I0810 14:03:55.262602    6529 instancegroups.go:591] Stopping instance "i-0aa2872968bfcd78b", node "i-0aa2872968bfcd78b", in group "master-us-west-1a.masters.e2e-ed4da97961-6b857.test-cncf-aws.k8s.io" (this may take a while).
I0810 14:03:55.511444    6529 instancegroups.go:436] waiting for 15s after terminating instance
I0810 14:04:10.511758    6529 instancegroups.go:470] Validating the cluster.
I0810 14:04:10.647454    6529 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 52.53.171.93:443: connect: connection refused.
I0810 14:05:10.692687    6529 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 52.53.171.93:443: i/o timeout.
I0810 14:06:10.784120    6529 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 52.53.171.93:443: i/o timeout.
I0810 14:07:10.863672    6529 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 52.53.171.93:443: i/o timeout.
I0810 14:08:10.911202    6529 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 52.53.171.93:443: i/o timeout.
I0810 14:08:42.777538    6529 instancegroups.go:526] Cluster did not pass validation, will retry in "30s": system-cluster-critical pod "calico-kube-controllers-75f4df896c-rx9n8" is not ready (calico-kube-controllers), system-node-critical pod "calico-node-8wwkd" is not ready (calico-node), system-cluster-critical pod "ebs-csi-controller-5b4bd8874c-wwx56" is not ready (ebs-plugin).
I0810 14:09:13.993031    6529 instancegroups.go:526] Cluster did not pass validation, will retry in "30s": system-cluster-critical pod "calico-kube-controllers-75f4df896c-rx9n8" is not ready (calico-kube-controllers), system-cluster-critical pod "ebs-csi-controller-5b4bd8874c-fs47g" is not ready (ebs-plugin).
I0810 14:09:45.249682    6529 instancegroups.go:526] Cluster did not pass validation, will retry in "30s": system-cluster-critical pod "calico-kube-controllers-75f4df896c-rx9n8" is not ready (calico-kube-controllers).
I0810 14:10:16.494603    6529 instancegroups.go:526] Cluster did not pass validation, will retry in "30s": system-cluster-critical pod "calico-kube-controllers-75f4df896c-rx9n8" is not ready (calico-kube-controllers).
I0810 14:10:47.782222    6529 instancegroups.go:526] Cluster did not pass validation, will retry in "30s": system-cluster-critical pod "calico-kube-controllers-75f4df896c-rx9n8" is not ready (calico-kube-controllers).
I0810 14:11:19.131660    6529 instancegroups.go:526] Cluster did not pass validation, will retry in "30s": system-cluster-critical pod "calico-kube-controllers-75f4df896c-rx9n8" is not ready (calico-kube-controllers).
... skipping 58 lines ...
I0810 14:25:42.084313    6529 instancegroups.go:503] Cluster validated.
I0810 14:25:42.084387    6529 instancegroups.go:400] Draining the node: "i-0f10fb9fae6c6a89f".
WARNING: ignoring DaemonSet-managed Pods: kube-system/calico-node-9jc8c, kube-system/ebs-csi-node-cr6z7
evicting pod kube-system/coredns-autoscaler-f85cf5c-v2bn4
evicting pod kube-system/coredns-5c44b6cf7d-j5bj6
evicting pod kube-system/coredns-5c44b6cf7d-tgjr7
error when evicting pods/"coredns-5c44b6cf7d-j5bj6" -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-j5bj6
I0810 14:25:54.266393    6529 instancegroups.go:660] Waiting for 5s for pods to stabilize after draining.
I0810 14:25:59.270427    6529 instancegroups.go:591] Stopping instance "i-0f10fb9fae6c6a89f", node "i-0f10fb9fae6c6a89f", in group "nodes-us-west-1a.e2e-ed4da97961-6b857.test-cncf-aws.k8s.io" (this may take a while).
I0810 14:25:59.508019    6529 instancegroups.go:436] waiting for 15s after terminating instance
I0810 14:26:14.508901    6529 instancegroups.go:470] Validating the cluster.
I0810 14:26:15.747793    6529 instancegroups.go:506] Cluster validated; revalidating in 10s to make sure it does not flap.
... skipping 39 lines ...
I0810 14:26:31.367778    6580 app.go:64] RunDir for this run: "/home/prow/go/src/k8s.io/kops/_rundir/ada24aab-18b3-11ed-a3cd-9a8e9eec334c"
I0810 14:26:31.372476    6580 app.go:128] ID for this run: "ada24aab-18b3-11ed-a3cd-9a8e9eec334c"
I0810 14:26:31.372524    6580 local.go:42] ⚙️ /home/prow/go/bin/kubetest2-tester-kops --test-package-version=https://storage.googleapis.com/k8s-release-dev/ci/v1.26.0-alpha.0.5+a38bb7ed811a18 --parallel 25
I0810 14:26:31.392017    6599 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true
I0810 14:26:31.400296    6599 kubectl.go:148] gsutil cp gs://kubernetes-release/release/https://storage.googleapis.com/k8s-release-dev/ci/v1.26.0-alpha.0.5+a38bb7ed811a18/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.26.0-alpha.0.5+a38bb7ed811a18/kubernetes-client-linux-amd64.tar.gz
F0810 14:26:33.518900    6599 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.26.0-alpha.0.5+a38bb7ed811a18: 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.ydECsNwb0 --down
I0810 14:26:33.552647    6786 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true
I0810 14:26:33.555559    6786 app.go:61] The files in RunDir shall not be part of Artifacts
I0810 14:26:33.555698    6786 app.go:62] pass rundir-in-artifacts flag True for RunDir to be part of Artifacts
I0810 14:26:33.555768    6786 app.go:64] RunDir for this run: "/home/prow/go/src/k8s.io/kops/_rundir/ada24aab-18b3-11ed-a3cd-9a8e9eec334c"
... skipping 298 lines ...