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:49
Elapsed16m25s
Revisionbc9e87eac67099994c8c32f970658044b5c00ae9
Refs 194

No Test Failures!


Error lines from build-log.txt

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

Validating cluster test-cluster-14683.k8s.local

W0716 20:56:07.283665   17028 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-14683-k8-ksbjv5-311262087.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-14683-k8-ksbjv5-311262087.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0716 20:56:17.315383   17028 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-14683-k8-ksbjv5-311262087.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-14683-k8-ksbjv5-311262087.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0716 20:56:27.345855   17028 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-14683-k8-ksbjv5-311262087.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-14683-k8-ksbjv5-311262087.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0716 20:56:37.383310   17028 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-14683-k8-ksbjv5-311262087.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-14683-k8-ksbjv5-311262087.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0716 20:56:48.577261   17028 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-14683-k8-ksbjv5-311262087.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-14683-k8-ksbjv5-311262087.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0716 20:57:11.220498   17028 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:57:32.825316   17028 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:57:54.429875   17028 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:58:16.068535   17028 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:58:38.739475   17028 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:59:00.327045   17028 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-08b13771689e5b456				machine "i-08b13771689e5b456" has not yet joined cluster
Node	ip-172-20-55-231.us-west-2.compute.internal	master "ip-172-20-55-231.us-west-2.compute.internal" is not ready

Validation Failed
W0716 20:59:20.978194   17028 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 13 lines ...
Pod	kube-system/kops-controller-gz867						system-node-critical pod "kops-controller-gz867" is pending
Pod	kube-system/kube-apiserver-ip-172-20-55-231.us-west-2.compute.internal		system-cluster-critical pod "kube-apiserver-ip-172-20-55-231.us-west-2.compute.internal" is pending
Pod	kube-system/kube-controller-manager-ip-172-20-55-231.us-west-2.compute.internal	system-cluster-critical pod "kube-controller-manager-ip-172-20-55-231.us-west-2.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-55-231.us-west-2.compute.internal		system-node-critical pod "kube-proxy-ip-172-20-55-231.us-west-2.compute.internal" is pending
Pod	kube-system/kube-scheduler-ip-172-20-55-231.us-west-2.compute.internal		system-cluster-critical pod "kube-scheduler-ip-172-20-55-231.us-west-2.compute.internal" is pending

Validation Failed
W0716 20:59:32.102904   17028 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-08b13771689e5b456				machine "i-08b13771689e5b456" has not yet joined cluster
Pod	kube-system/coredns-5489b75945-ltdfk		system-cluster-critical pod "coredns-5489b75945-ltdfk" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-kx672	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-kx672" is pending

Validation Failed
W0716 20:59:43.166634   17028 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-08b13771689e5b456				machine "i-08b13771689e5b456" has not yet joined cluster
Pod	kube-system/coredns-5489b75945-ltdfk		system-cluster-critical pod "coredns-5489b75945-ltdfk" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-kx672	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-kx672" is pending

Validation Failed
W0716 20:59:54.257328   17028 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-53-170.us-west-2.compute.internal	node "ip-172-20-53-170.us-west-2.compute.internal" is not ready
Pod	kube-system/coredns-5489b75945-ltdfk		system-cluster-critical pod "coredns-5489b75945-ltdfk" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-kx672	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-kx672" is pending

Validation Failed
W0716 21:00:05.583879   17028 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-14683.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=14683 --wait --kubeconfig /home/prow/go/src/github.com/kubernetes-sigs/aws-fsx-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-14683.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 ...