This job view page is being replaced by Spyglass soon. Check out the new job view.
PRwongma7: Helm chart 1.0
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-07-15 22:16
Elapsed12m42s
Revision7a5c2d1085b93e989049230fd6c8bf264e875874
Refs 194

No Test Failures!


Error lines from build-log.txt

... skipping 322 lines ...
  Installing : 7:device-mapper-libs-1.02.146-4.amzn2.0.2.x86_64           21/29 
  Installing : cryptsetup-libs-1.7.4-4.amzn2.x86_64                       22/29 
  Installing : elfutils-libs-0.176-2.amzn2.x86_64                         23/29 
  Installing : systemd-libs-219-78.amzn2.0.14.x86_64                      24/29 
  Installing : 1:dbus-libs-1.10.24-7.amzn2.x86_64                         25/29 
  Installing : systemd-219-78.amzn2.0.14.x86_64                           26/29 
Failed to get D-Bus connection: Operation not permitted
  Installing : elfutils-default-yama-scope-0.176-2.amzn2.noarch           27/29 
  Installing : 1:dbus-1.10.24-7.amzn2.x86_64                              28/29 
  Installing : libyaml-0.1.4-11.amzn2.0.2.x86_64                          29/29 
  Verifying  : gzip-1.5-10.amzn2.x86_64                                    1/29 
  Verifying  : elfutils-default-yama-scope-0.176-2.amzn2.noarch            2/29 
  Verifying  : cracklib-2.9.0-11.amzn2.0.2.x86_64                          3/29 
... skipping 604 lines ...
## Validating cluster test-cluster-1752.k8s.local
#
Using cluster from kubectl context: test-cluster-1752.k8s.local

Validating cluster test-cluster-1752.k8s.local

W0715 22:24:14.274690   17158 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-1752-k8s-m7k6nm-56034866.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-1752-k8s-m7k6nm-56034866.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0715 22:24:24.308809   17158 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-1752-k8s-m7k6nm-56034866.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-1752-k8s-m7k6nm-56034866.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0715 22:24:34.354928   17158 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-1752-k8s-m7k6nm-56034866.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-1752-k8s-m7k6nm-56034866.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0715 22:24:44.385451   17158 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-1752-k8s-m7k6nm-56034866.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-1752-k8s-m7k6nm-56034866.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0715 22:24:54.421618   17158 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-1752-k8s-m7k6nm-56034866.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-1752-k8s-m7k6nm-56034866.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0715 22:25:04.474488   17158 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-1752-k8s-m7k6nm-56034866.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-1752-k8s-m7k6nm-56034866.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0715 22:25:14.519144   17158 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-1752-k8s-m7k6nm-56034866.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-1752-k8s-m7k6nm-56034866.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0715 22:25:24.564077   17158 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-1752-k8s-m7k6nm-56034866.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-1752-k8s-m7k6nm-56034866.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0715 22:25:34.597168   17158 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-1752-k8s-m7k6nm-56034866.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-1752-k8s-m7k6nm-56034866.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0715 22:25:44.628035   17158 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-1752-k8s-m7k6nm-56034866.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-1752-k8s-m7k6nm-56034866.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0715 22:25:54.656928   17158 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-1752-k8s-m7k6nm-56034866.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-1752-k8s-m7k6nm-56034866.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0715 22:26:05.835190   17158 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-1752-k8s-m7k6nm-56034866.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-1752-k8s-m7k6nm-56034866.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0715 22:26:15.872774   17158 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-1752-k8s-m7k6nm-56034866.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-1752-k8s-m7k6nm-56034866.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0715 22:26:37.472510   17158 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)
W0715 22:26:59.053695   17158 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)
W0715 22:27:20.635872   17158 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	1	1	us-west-2a

NODE STATUS
... skipping 2 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Machine	i-026ee07a5c60277d9				machine "i-026ee07a5c60277d9" has not yet joined cluster
Node	ip-172-20-57-66.us-west-2.compute.internal	master "ip-172-20-57-66.us-west-2.compute.internal" is not ready

Validation Failed
W0715 22:27:40.142063   17158 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	1	1	us-west-2a

... skipping 3 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Machine	i-026ee07a5c60277d9				machine "i-026ee07a5c60277d9" has not yet joined cluster
Node	ip-172-20-57-66.us-west-2.compute.internal	master "ip-172-20-57-66.us-west-2.compute.internal" is not ready

Validation Failed
W0715 22:27:51.220082   17158 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	1	1	us-west-2a

... skipping 6 lines ...
Machine	i-026ee07a5c60277d9				machine "i-026ee07a5c60277d9" has not yet joined cluster
Pod	kube-system/coredns-5489b75945-vbtm6		system-cluster-critical pod "coredns-5489b75945-vbtm6" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-cm7b8	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-cm7b8" is pending
Pod	kube-system/dns-controller-8574dcc89d-mn6cx	system-cluster-critical pod "dns-controller-8574dcc89d-mn6cx" is pending
Pod	kube-system/kops-controller-7q775		system-node-critical pod "kops-controller-7q775" is pending

Validation Failed
W0715 22:28:02.523362   17158 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	1	1	us-west-2a

... skipping 6 lines ...
Machine	i-026ee07a5c60277d9				machine "i-026ee07a5c60277d9" has not yet joined cluster
Pod	kube-system/coredns-5489b75945-vbtm6		system-cluster-critical pod "coredns-5489b75945-vbtm6" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-cm7b8	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-cm7b8" is pending
Pod	kube-system/dns-controller-8574dcc89d-mn6cx	system-cluster-critical pod "dns-controller-8574dcc89d-mn6cx" is pending
Pod	kube-system/kops-controller-7q775		system-node-critical pod "kops-controller-7q775" is pending

Validation Failed
W0715 22:28:13.683477   17158 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	1	1	us-west-2a

... skipping 5 lines ...
KIND	NAME						MESSAGE
Machine	i-026ee07a5c60277d9				machine "i-026ee07a5c60277d9" has not yet joined cluster
Pod	kube-system/coredns-5489b75945-vbtm6		system-cluster-critical pod "coredns-5489b75945-vbtm6" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-cm7b8	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-cm7b8" is pending
Pod	kube-system/kops-controller-7q775		system-node-critical pod "kops-controller-7q775" is pending

Validation Failed
W0715 22:28:24.763425   17158 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	1	1	us-west-2a

... skipping 4 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Machine	i-026ee07a5c60277d9				machine "i-026ee07a5c60277d9" has not yet joined cluster
Pod	kube-system/coredns-5489b75945-vbtm6		system-cluster-critical pod "coredns-5489b75945-vbtm6" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-cm7b8	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-cm7b8" is pending

Validation Failed
W0715 22:28:35.857739   17158 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	1	1	us-west-2a

... skipping 5 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Node	ip-172-20-54-114.us-west-2.compute.internal	node "ip-172-20-54-114.us-west-2.compute.internal" is not ready
Pod	kube-system/coredns-5489b75945-vbtm6		system-cluster-critical pod "coredns-5489b75945-vbtm6" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-cm7b8	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-cm7b8" is pending

Validation Failed
W0715 22:28:46.951315   17158 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	1	1	us-west-2a

... skipping 4 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5489b75945-vbtm6		system-cluster-critical pod "coredns-5489b75945-vbtm6" is not ready (coredns)
Pod	kube-system/coredns-autoscaler-6f594f4c58-cm7b8	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-cm7b8" is pending

Validation Failed
W0715 22:28:58.124889   17158 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	1	1	us-west-2a

... skipping 5 lines ...
Your cluster test-cluster-1752.k8s.local is ready
###
## Deploying driver
#
+ /home/prow/go/src/github.com/kubernetes-sigs/aws-fsx-csi-driver/hack/e2e/csi-test-artifacts/bin/helm upgrade --install aws-fsx-csi-driver --namespace kube-system --set image.repository=607362164682.dkr.ecr.us-west-2.amazonaws.com/aws-fsx-csi-driver --set image.tag=1752 --wait --kubeconfig /home/prow/go/src/github.com/kubernetes-sigs/aws-fsx-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-1752.k8s.local.kops.kubeconfig ./charts/aws-fsx-csi-driver -f ./hack/values.yaml
Release "aws-fsx-csi-driver" does not exist. Installing it now.
Error: parse error at (aws-fsx-csi-driver/templates/wip-node-serviceaccount.yaml:59): unexpected {{end}}
make: *** [Makefile:43: test-e2e] 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 ...