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-16 20:08
Elapsed17m36s
Revision295421f19e97d1d6a9814c3d0c8f69dd06614f16
Refs 194

No Test Failures!


Error lines from build-log.txt

... skipping 323 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-18758.k8s.local
#
Using cluster from kubectl context: test-cluster-18758.k8s.local

Validating cluster test-cluster-18758.k8s.local

W0716 20:15:20.896114   17256 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-18758-k8-a9b0bt-549596376.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-18758-k8-a9b0bt-549596376.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0716 20:15:30.928319   17256 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-18758-k8-a9b0bt-549596376.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-18758-k8-a9b0bt-549596376.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0716 20:15:40.986046   17256 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-18758-k8-a9b0bt-549596376.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-18758-k8-a9b0bt-549596376.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0716 20:15:51.033280   17256 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-18758-k8-a9b0bt-549596376.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-18758-k8-a9b0bt-549596376.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0716 20:16:01.069600   17256 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-18758-k8-a9b0bt-549596376.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-18758-k8-a9b0bt-549596376.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0716 20:16:11.100218   17256 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-18758-k8-a9b0bt-549596376.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-18758-k8-a9b0bt-549596376.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0716 20:16:22.276802   17256 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-18758-k8-a9b0bt-549596376.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-18758-k8-a9b0bt-549596376.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0716 20:16:43.937587   17256 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)
W0716 20:17:05.590796   17256 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)
W0716 20:17:27.219432   17256 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)
W0716 20:17:48.833150   17256 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)
W0716 20:18:10.440812   17256 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)
W0716 20:18:32.026071   17256 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)
W0716 20:18:53.701788   17256 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)
W0716 20:19:15.333676   17256 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)
W0716 20:19:36.999048   17256 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 8 lines ...
Pod	kube-system/etcd-manager-main-ip-172-20-38-41.us-west-2.compute.internal	system-cluster-critical pod "etcd-manager-main-ip-172-20-38-41.us-west-2.compute.internal" is pending
Pod	kube-system/kube-apiserver-ip-172-20-38-41.us-west-2.compute.internal		system-cluster-critical pod "kube-apiserver-ip-172-20-38-41.us-west-2.compute.internal" is pending
Pod	kube-system/kube-controller-manager-ip-172-20-38-41.us-west-2.compute.internal	system-cluster-critical pod "kube-controller-manager-ip-172-20-38-41.us-west-2.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-38-41.us-west-2.compute.internal		system-node-critical pod "kube-proxy-ip-172-20-38-41.us-west-2.compute.internal" is pending
Pod	kube-system/kube-scheduler-ip-172-20-38-41.us-west-2.compute.internal		system-cluster-critical pod "kube-scheduler-ip-172-20-38-41.us-west-2.compute.internal" is pending

Validation Failed
W0716 20:20:00.010330   17256 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-0ab2b258521a146a5				machine "i-0ab2b258521a146a5" has not yet joined cluster
Node	ip-172-20-38-41.us-west-2.compute.internal	master "ip-172-20-38-41.us-west-2.compute.internal" is not ready
Pod	kube-system/coredns-5489b75945-2vvtq		system-cluster-critical pod "coredns-5489b75945-2vvtq" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-f6lx2	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-f6lx2" is pending
Pod	kube-system/dns-controller-8574dcc89d-xvxkl	system-cluster-critical pod "dns-controller-8574dcc89d-xvxkl" is pending

Validation Failed
W0716 20:20:11.224206   17256 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-0ab2b258521a146a5				machine "i-0ab2b258521a146a5" has not yet joined cluster
Pod	kube-system/coredns-5489b75945-2vvtq		system-cluster-critical pod "coredns-5489b75945-2vvtq" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-f6lx2	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-f6lx2" is pending

Validation Failed
W0716 20:20:22.338772   17256 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 ...
KIND	NAME									MESSAGE
Node	ip-172-20-47-93.us-west-2.compute.internal				node "ip-172-20-47-93.us-west-2.compute.internal" is not ready
Pod	kube-system/coredns-5489b75945-2vvtq					system-cluster-critical pod "coredns-5489b75945-2vvtq" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-f6lx2				system-cluster-critical pod "coredns-autoscaler-6f594f4c58-f6lx2" is pending
Pod	kube-system/kube-proxy-ip-172-20-47-93.us-west-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-47-93.us-west-2.compute.internal" is pending

Validation Failed
W0716 20:20:33.495006   17256 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-2vvtq		system-cluster-critical pod "coredns-5489b75945-2vvtq" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-f6lx2	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-f6lx2" is pending

Validation Failed
W0716 20:20:44.588713   17256 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-2vvtq	system-cluster-critical pod "coredns-5489b75945-2vvtq" is not ready (coredns)
Pod	kube-system/coredns-5489b75945-9ldmz	system-cluster-critical pod "coredns-5489b75945-9ldmz" is not ready (coredns)

Validation Failed
W0716 20:20:55.839653   17256 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-18758.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=18758 --wait --kubeconfig /home/prow/go/src/github.com/kubernetes-sigs/aws-fsx-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-18758.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: timed out waiting for the condition
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 ...