This job view page is being replaced by Spyglass soon. Check out the new job view.
PRmichalschott: Better control over log verbosity.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-07-13 08:30
Elapsed8m40s
Revisionade5e3460ff18f32317dfb7cccaa0d5e0bdbe7f7
Refs 969

No Test Failures!


Error lines from build-log.txt

... skipping 297 lines ...
  Installing : 7:device-mapper-libs-1.02.146-4.amzn2.0.2.x86_64           23/32 
  Installing : cryptsetup-libs-1.7.4-4.amzn2.x86_64                       24/32 
  Installing : elfutils-libs-0.176-2.amzn2.x86_64                         25/32 
  Installing : systemd-libs-219-78.amzn2.0.14.x86_64                      26/32 
  Installing : 1:dbus-libs-1.10.24-7.amzn2.x86_64                         27/32 
  Installing : systemd-219-78.amzn2.0.14.x86_64                           28/32 
Failed to get D-Bus connection: Operation not permitted
  Installing : elfutils-default-yama-scope-0.176-2.amzn2.noarch           29/32 
  Installing : 1:dbus-1.10.24-7.amzn2.x86_64                              30/32 
  Installing : e2fsprogs-1.42.9-19.amzn2.x86_64                           31/32 
  Installing : xfsprogs-4.5.0-18.amzn2.0.1.x86_64                         32/32 
  Verifying  : gzip-1.5-10.amzn2.x86_64                                    1/32 
  Verifying  : elfutils-default-yama-scope-0.176-2.amzn2.noarch            2/32 
... skipping 460 lines ...
## Validating cluster test-cluster-19390.k8s.local
#
Using cluster from kubectl context: test-cluster-19390.k8s.local

Validating cluster test-cluster-19390.k8s.local

W0713 08:33:39.115281    9363 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-19390-k8-87astv-597508872.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-19390-k8-87astv-597508872.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0713 08:33:49.149364    9363 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-19390-k8-87astv-597508872.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-19390-k8-87astv-597508872.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0713 08:33:59.181526    9363 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-19390-k8-87astv-597508872.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-19390-k8-87astv-597508872.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0713 08:34:09.227024    9363 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-19390-k8-87astv-597508872.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-19390-k8-87astv-597508872.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0713 08:34:19.264512    9363 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-19390-k8-87astv-597508872.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-19390-k8-87astv-597508872.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0713 08:34:29.293765    9363 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-19390-k8-87astv-597508872.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-19390-k8-87astv-597508872.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0713 08:34:39.327951    9363 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-19390-k8-87astv-597508872.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-19390-k8-87astv-597508872.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0713 08:34:49.374509    9363 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-19390-k8-87astv-597508872.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-19390-k8-87astv-597508872.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0713 08:35:01.697298    9363 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-19390-k8-87astv-597508872.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-19390-k8-87astv-597508872.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0713 08:35:26.375608    9363 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: an error on the server ("") has prevented the request from succeeding (get nodes)
W0713 08:35:48.020191    9363 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: an error on the server ("") has prevented the request from succeeding (get nodes)
W0713 08:36:09.627247    9363 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: an error on the server ("") has prevented the request from succeeding (get nodes)
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	t3.medium	1	1	us-west-2a
nodes-us-west-2a	Node	c4.large	3	3	us-west-2a

NODE STATUS
... skipping 4 lines ...
KIND	NAME						MESSAGE
Machine	i-0029c368420e72f3d				machine "i-0029c368420e72f3d" has not yet joined cluster
Machine	i-0568bda0307f8ccce				machine "i-0568bda0307f8ccce" has not yet joined cluster
Machine	i-0e07c3c97a8d3d1ef				machine "i-0e07c3c97a8d3d1ef" has not yet joined cluster
Node	ip-172-20-36-164.us-west-2.compute.internal	node "ip-172-20-36-164.us-west-2.compute.internal" of role "master" is not ready

Validation Failed
W0713 08:36:28.524401    9363 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	t3.medium	1	1	us-west-2a
nodes-us-west-2a	Node	c4.large	3	3	us-west-2a

... skipping 9 lines ...
Node	ip-172-20-36-164.us-west-2.compute.internal	master "ip-172-20-36-164.us-west-2.compute.internal" is missing kube-apiserver pod
Node	ip-172-20-36-164.us-west-2.compute.internal	master "ip-172-20-36-164.us-west-2.compute.internal" is missing kube-controller-manager pod
Node	ip-172-20-36-164.us-west-2.compute.internal	master "ip-172-20-36-164.us-west-2.compute.internal" is missing kube-scheduler pod
Pod	kube-system/coredns-8f5559c9b-krvnf		system-cluster-critical pod "coredns-8f5559c9b-krvnf" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-zz5mn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-zz5mn" is pending

Validation Failed
W0713 08:36:40.011798    9363 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	t3.medium	1	1	us-west-2a
nodes-us-west-2a	Node	c4.large	3	3	us-west-2a

... skipping 10 lines ...
Node	ip-172-20-36-164.us-west-2.compute.internal					master "ip-172-20-36-164.us-west-2.compute.internal" is missing kube-controller-manager pod
Node	ip-172-20-36-164.us-west-2.compute.internal					master "ip-172-20-36-164.us-west-2.compute.internal" is missing kube-scheduler pod
Pod	kube-system/coredns-8f5559c9b-krvnf						system-cluster-critical pod "coredns-8f5559c9b-krvnf" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-zz5mn					system-cluster-critical pod "coredns-autoscaler-6f594f4c58-zz5mn" is pending
Pod	kube-system/kube-controller-manager-ip-172-20-36-164.us-west-2.compute.internal	system-cluster-critical pod "kube-controller-manager-ip-172-20-36-164.us-west-2.compute.internal" is pending

Validation Failed
W0713 08:36:51.330451    9363 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	t3.medium	1	1	us-west-2a
nodes-us-west-2a	Node	c4.large	3	3	us-west-2a

... skipping 9 lines ...
Node	ip-172-20-36-164.us-west-2.compute.internal					master "ip-172-20-36-164.us-west-2.compute.internal" is missing kube-apiserver pod
Node	ip-172-20-36-164.us-west-2.compute.internal					master "ip-172-20-36-164.us-west-2.compute.internal" is missing kube-scheduler pod
Pod	kube-system/coredns-8f5559c9b-krvnf						system-cluster-critical pod "coredns-8f5559c9b-krvnf" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-zz5mn					system-cluster-critical pod "coredns-autoscaler-6f594f4c58-zz5mn" is pending
Pod	kube-system/etcd-manager-events-ip-172-20-36-164.us-west-2.compute.internal	system-cluster-critical pod "etcd-manager-events-ip-172-20-36-164.us-west-2.compute.internal" is pending

Validation Failed
W0713 08:37:02.870720    9363 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	t3.medium	1	1	us-west-2a
nodes-us-west-2a	Node	c4.large	3	3	us-west-2a

... skipping 7 lines ...
Machine	i-0568bda0307f8ccce				machine "i-0568bda0307f8ccce" has not yet joined cluster
Machine	i-0e07c3c97a8d3d1ef				machine "i-0e07c3c97a8d3d1ef" has not yet joined cluster
Node	ip-172-20-36-164.us-west-2.compute.internal	master "ip-172-20-36-164.us-west-2.compute.internal" is missing kube-apiserver pod
Pod	kube-system/coredns-8f5559c9b-krvnf		system-cluster-critical pod "coredns-8f5559c9b-krvnf" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-zz5mn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-zz5mn" is pending

Validation Failed
W0713 08:37:14.503963    9363 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	t3.medium	1	1	us-west-2a
nodes-us-west-2a	Node	c4.large	3	3	us-west-2a

... skipping 6 lines ...
Machine	i-0029c368420e72f3d				machine "i-0029c368420e72f3d" has not yet joined cluster
Machine	i-0568bda0307f8ccce				machine "i-0568bda0307f8ccce" has not yet joined cluster
Machine	i-0e07c3c97a8d3d1ef				machine "i-0e07c3c97a8d3d1ef" has not yet joined cluster
Pod	kube-system/coredns-8f5559c9b-krvnf		system-cluster-critical pod "coredns-8f5559c9b-krvnf" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-zz5mn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-zz5mn" is pending

Validation Failed
W0713 08:37:25.924337    9363 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	t3.medium	1	1	us-west-2a
nodes-us-west-2a	Node	c4.large	3	3	us-west-2a

... skipping 9 lines ...
Node	ip-172-20-52-24.us-west-2.compute.internal	node "ip-172-20-52-24.us-west-2.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.us-west-2.compute.internal	node "ip-172-20-58-226.us-west-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-234.us-west-2.compute.internal	node "ip-172-20-59-234.us-west-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-8f5559c9b-krvnf		system-cluster-critical pod "coredns-8f5559c9b-krvnf" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-zz5mn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-zz5mn" is pending

Validation Failed
W0713 08:37:37.343338    9363 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	t3.medium	1	1	us-west-2a
nodes-us-west-2a	Node	c4.large	3	3	us-west-2a

... skipping 8 lines ...
KIND	NAME						MESSAGE
Node	ip-172-20-52-24.us-west-2.compute.internal	node "ip-172-20-52-24.us-west-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-234.us-west-2.compute.internal	node "ip-172-20-59-234.us-west-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-8f5559c9b-krvnf		system-cluster-critical pod "coredns-8f5559c9b-krvnf" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-zz5mn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-zz5mn" is pending

Validation Failed
W0713 08:37:48.736828    9363 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	t3.medium	1	1	us-west-2a
nodes-us-west-2a	Node	c4.large	3	3	us-west-2a

... skipping 5 lines ...
ip-172-20-59-234.us-west-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-8f5559c9b-xfb66	system-cluster-critical pod "coredns-8f5559c9b-xfb66" is pending

Validation Failed
W0713 08:38:00.446253    9363 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	t3.medium	1	1	us-west-2a
nodes-us-west-2a	Node	c4.large	3	3	us-west-2a

... skipping 5 lines ...
ip-172-20-59-234.us-west-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-8f5559c9b-xfb66	system-cluster-critical pod "coredns-8f5559c9b-xfb66" is pending

Validation Failed
W0713 08:38:11.864216    9363 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	t3.medium	1	1	us-west-2a
nodes-us-west-2a	Node	c4.large	3	3	us-west-2a

... skipping 5 lines ...
ip-172-20-59-234.us-west-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-proxy-ip-172-20-52-24.us-west-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-52-24.us-west-2.compute.internal" is pending

Validation Failed
W0713 08:38:23.288996    9363 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	t3.medium	1	1	us-west-2a
nodes-us-west-2a	Node	c4.large	3	3	us-west-2a

... skipping 19 lines ...
customresourcedefinition.apiextensions.k8s.io/volumesnapshots.snapshot.storage.k8s.io created
###
## Deploying driver
#
+ /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/hack/e2e/csi-test-artifacts/bin/helm upgrade --install aws-ebs-csi-driver --namespace kube-system --set image.repository=607362164682.dkr.ecr.us-west-2.amazonaws.com/aws-ebs-csi-driver --set image.tag=19390 --wait --kubeconfig /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-19390.k8s.local.kops.kubeconfig ./charts/aws-ebs-csi-driver -f ./hack/values.yaml --set=controller.k8sTagClusterId=test-cluster-19390.k8s.local
Release "aws-ebs-csi-driver" does not exist. Installing it now.
Error: template: aws-ebs-csi-driver/templates/node-windows.yaml:111:28: executing "aws-ebs-csi-driver/templates/node-windows.yaml" at <.Values.nodeWindows.logLevel>: nil pointer evaluating interface {}.logLevel
make: *** [Makefile:82: test-e2e-single-az] Error 1
+ EXIT_VALUE=2
+ set +o xtrace
Cleaning up after docker in docker.
================================================================================
Cleaning up after docker
Stopping Docker: dockerProgram process in pidfile '/var/run/docker-ssd.pid', 1 process(es), refused to die.
... skipping 3 lines ...