This job view page is being replaced by Spyglass soon. Check out the new job view.
PRolemarkus: Make it possible to remove addons
ResultFAILURE
Tests 0 failed / 1 succeeded
Started2022-07-09 09:34
Elapsed32m34s
Revision713294378111c0c6f6b8a869056cfb4bd9bdbcd7
Refs 13962

No Test Failures!


Show 1 Passed Tests

Error lines from build-log.txt

... skipping 190 lines ...
I0709 09:35:31.724166    6200 app.go:65] RunDir for this run: "/home/prow/go/src/k8s.io/kops/_rundir/2698c532-ff6a-11ec-b755-6eb26a4f4b38"
I0709 09:35:31.728464    6200 app.go:129] ID for this run: "2698c532-ff6a-11ec-b755-6eb26a4f4b38"
I0709 09:35:31.728924    6200 local.go:42] ⚙️ ssh-keygen -t ed25519 -N  -q -f /tmp/kops/e2e-8f6cf1d295-e5e21.test-cncf-aws.k8s.io/id_ed25519
I0709 09:35:31.737328    6200 up.go:44] Cleaning up any leaked resources from previous cluster
I0709 09:35:31.737414    6200 dumplogs.go:45] /tmp/kops.Ln0JiHPoC toolbox dump --name e2e-8f6cf1d295-e5e21.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-8f6cf1d295-e5e21.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
I0709 09:35:31.737433    6200 local.go:42] ⚙️ /tmp/kops.Ln0JiHPoC toolbox dump --name e2e-8f6cf1d295-e5e21.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-8f6cf1d295-e5e21.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
W0709 09:35:32.370330    6200 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0709 09:35:32.370453    6200 down.go:48] /tmp/kops.Ln0JiHPoC delete cluster --name e2e-8f6cf1d295-e5e21.test-cncf-aws.k8s.io --yes
I0709 09:35:32.370465    6200 local.go:42] ⚙️ /tmp/kops.Ln0JiHPoC delete cluster --name e2e-8f6cf1d295-e5e21.test-cncf-aws.k8s.io --yes
I0709 09:35:32.397142    6223 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0709 09:35:32.397250    6223 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-8f6cf1d295-e5e21.test-cncf-aws.k8s.io" not found
I0709 09:35:32.973869    6200 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2022/07/09 09:35:32 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
I0709 09:35:32.986914    6200 http.go:37] curl https://ip.jsb.workers.dev
I0709 09:35:33.096271    6200 up.go:159] /tmp/kops.Ln0JiHPoC create cluster --name e2e-8f6cf1d295-e5e21.test-cncf-aws.k8s.io --cloud aws --kubernetes-version 1.21.0 --ssh-public-key /tmp/kops/e2e-8f6cf1d295-e5e21.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --override=cluster.spec.nodeTerminationHandler.enabled=true --admin-access 34.68.176.126/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones us-west-2a --master-size c5.large
I0709 09:35:33.096313    6200 local.go:42] ⚙️ /tmp/kops.Ln0JiHPoC create cluster --name e2e-8f6cf1d295-e5e21.test-cncf-aws.k8s.io --cloud aws --kubernetes-version 1.21.0 --ssh-public-key /tmp/kops/e2e-8f6cf1d295-e5e21.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --override=cluster.spec.nodeTerminationHandler.enabled=true --admin-access 34.68.176.126/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones us-west-2a --master-size c5.large
I0709 09:35:33.122520    6233 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0709 09:35:33.122768    6233 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0709 09:35:33.184275    6233 create_cluster.go:728] Using SSH public key: /tmp/kops/e2e-8f6cf1d295-e5e21.test-cncf-aws.k8s.io/id_ed25519.pub
... skipping 490 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
W0709 09:36:18.576446    6271 validate_cluster.go:221] (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
W0709 09:36:28.609070    6271 validate_cluster.go:221] (will retry): cluster not yet healthy
W0709 09:36:38.651127    6271 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-8f6cf1d295-e5e21.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0709 09:36:48.674102    6271 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-8f6cf1d295-e5e21.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
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
W0709 09:36:58.707994    6271 validate_cluster.go:221] (will retry): cluster not yet healthy
W0709 09:37:08.742740    6271 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-8f6cf1d295-e5e21.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
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
W0709 09:37:18.782032    6271 validate_cluster.go:221] (will retry): cluster not yet healthy
W0709 09:37:28.805508    6271 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-8f6cf1d295-e5e21.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0709 09:37:38.830357    6271 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-8f6cf1d295-e5e21.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
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
W0709 09:37:48.862695    6271 validate_cluster.go:221] (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
W0709 09:37:58.911280    6271 validate_cluster.go:221] (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
W0709 09:38:08.948704    6271 validate_cluster.go:221] (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
W0709 09:38:18.988688    6271 validate_cluster.go:221] (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
W0709 09:38:29.031677    6271 validate_cluster.go:221] (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
W0709 09:38:39.073835    6271 validate_cluster.go:221] (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
W0709 09:38:49.124963    6271 validate_cluster.go:221] (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
W0709 09:38:59.161244    6271 validate_cluster.go:221] (will retry): cluster not yet healthy
W0709 09:39:09.187725    6271 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-8f6cf1d295-e5e21.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
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
W0709 09:39:19.223607    6271 validate_cluster.go:221] (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
W0709 09:39:29.269881    6271 validate_cluster.go:221] (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
W0709 09:39:39.306042    6271 validate_cluster.go:221] (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
W0709 09:39:49.357701    6271 validate_cluster.go:221] (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
W0709 09:39:59.409269    6271 validate_cluster.go:221] (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/coredns-5dc785954d-clntq					system-cluster-critical pod "coredns-5dc785954d-clntq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-zfzll				system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-zfzll" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-99.us-west-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-99.us-west-2.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-51-175.us-west-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-51-175.us-west-2.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-62-221.us-west-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-62-221.us-west-2.compute.internal" is pending

Validation Failed
W0709 09:40:11.702277    6271 validate_cluster.go:221] (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 8 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Node	ip-172-20-47-162.us-west-2.compute.internal	node "ip-172-20-47-162.us-west-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5dc785954d-clntq		system-cluster-critical pod "coredns-5dc785954d-clntq" is pending
Pod	kube-system/coredns-5dc785954d-j8zvn		system-cluster-critical pod "coredns-5dc785954d-j8zvn" is pending

Validation Failed
W0709 09:40:23.279521    6271 validate_cluster.go:221] (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 1154 lines ...
  	                    	        for cmd in "${commands[@]}"; do
  	                    	...
  	                    	            continue
  	                    	          fi
  	                    	+         if ! validate-hash "${file}" "${hash}"; then
  	                    	-         if [[ -n "${hash}" ]] && ! validate-hash "${file}" "${hash}"; then
  	                    	            echo "== Hash validation of ${url} failed. Retrying. =="
  	                    	            rm -f "${file}"
  	                    	          else
  	                    	-           if [[ -n "${hash}" ]]; then
  	                    	+           echo "== Downloaded ${url} (SHA256 = ${hash}) =="
  	                    	-             echo "== Downloaded ${url} (SHA1 = ${hash}) =="
  	                    	-           else
... skipping 268 lines ...
  	                    	        for cmd in "${commands[@]}"; do
  	                    	...
  	                    	            continue
  	                    	          fi
  	                    	+         if ! validate-hash "${file}" "${hash}"; then
  	                    	-         if [[ -n "${hash}" ]] && ! validate-hash "${file}" "${hash}"; then
  	                    	            echo "== Hash validation of ${url} failed. Retrying. =="
  	                    	            rm -f "${file}"
  	                    	          else
  	                    	-           if [[ -n "${hash}" ]]; then
  	                    	+           echo "== Downloaded ${url} (SHA256 = ${hash}) =="
  	                    	-             echo "== Downloaded ${url} (SHA1 = ${hash}) =="
  	                    	-           else
... skipping 1148 lines ...
WARNING: ignoring DaemonSet-managed Pods: kube-system/aws-node-termination-handler-vvbgx, kube-system/kops-controller-5t8rd
evicting pod kube-system/dns-controller-7fc66c4dd4-dbwlg
I0709 09:49:22.114877   38758 instancegroups.go:660] Waiting for 5s for pods to stabilize after draining.
I0709 09:49:27.115916   38758 instancegroups.go:591] Stopping instance "i-08862be96874c2a64", node "ip-172-20-55-137.us-west-2.compute.internal", in group "master-us-west-2a.masters.e2e-8f6cf1d295-e5e21.test-cncf-aws.k8s.io" (this may take a while).
I0709 09:49:27.327698   38758 instancegroups.go:436] waiting for 15s after terminating instance
I0709 09:49:42.328002   38758 instancegroups.go:470] Validating the cluster.
I0709 09:50:12.364698   38758 instancegroups.go:516] Cluster did not validate, will retry in "30s": error listing nodes: Get "https://api.e2e-8f6cf1d295-e5e21.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 34.213.162.202:443: i/o timeout.
I0709 09:51:12.407700   38758 instancegroups.go:516] Cluster did not validate, will retry in "30s": error listing nodes: Get "https://api.e2e-8f6cf1d295-e5e21.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 34.213.162.202:443: i/o timeout.
I0709 09:52:12.460583   38758 instancegroups.go:516] Cluster did not validate, will retry in "30s": error listing nodes: Get "https://api.e2e-8f6cf1d295-e5e21.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 34.213.162.202:443: i/o timeout.
I0709 09:53:12.512017   38758 instancegroups.go:516] Cluster did not validate, will retry in "30s": error listing nodes: Get "https://api.e2e-8f6cf1d295-e5e21.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 34.213.162.202:443: i/o timeout.
I0709 09:54:12.557541   38758 instancegroups.go:516] Cluster did not validate, will retry in "30s": error listing nodes: Get "https://api.e2e-8f6cf1d295-e5e21.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 34.213.162.202:443: i/o timeout.
I0709 09:55:12.599538   38758 instancegroups.go:516] Cluster did not validate, will retry in "30s": error listing nodes: Get "https://api.e2e-8f6cf1d295-e5e21.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 34.213.162.202:443: i/o timeout.
I0709 09:56:12.659719   38758 instancegroups.go:516] Cluster did not validate, will retry in "30s": error listing nodes: Get "https://api.e2e-8f6cf1d295-e5e21.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 34.213.162.202:443: i/o timeout.
I0709 09:57:12.705330   38758 instancegroups.go:516] Cluster did not validate, will retry in "30s": error listing nodes: Get "https://api.e2e-8f6cf1d295-e5e21.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 34.213.162.202:443: i/o timeout.
I0709 09:57:44.704130   38758 instancegroups.go:526] Cluster did not pass validation, will retry in "30s": node "ip-172-20-34-99.us-west-2.compute.internal" of role "node" is not ready, node "ip-172-20-51-175.us-west-2.compute.internal" of role "node" is not ready, node "ip-172-20-47-162.us-west-2.compute.internal" of role "node" is not ready, node "ip-172-20-62-221.us-west-2.compute.internal" of role "node" is not ready, system-cluster-critical pod "coredns-5dc785954d-j8zvn" is not ready (coredns), system-cluster-critical pod "coredns-5fcc7b6498-j966q" is not ready (coredns), system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-zfzll" is not ready (autoscaler).
I0709 09:58:16.336795   38758 instancegroups.go:526] Cluster did not pass validation, will retry in "30s": system-cluster-critical pod "coredns-5fcc7b6498-782pg" is pending.
I0709 09:58:47.713166   38758 instancegroups.go:506] Cluster validated; revalidating in 10s to make sure it does not flap.
I0709 09:58:59.152583   38758 instancegroups.go:503] Cluster validated.
I0709 09:58:59.152641   38758 rollingupdate.go:210] Rolling update completed for cluster "e2e-8f6cf1d295-e5e21.test-cncf-aws.k8s.io"!
+ sleep 120s
... skipping 727 lines ...