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:34
Elapsed14m42s
Revisionb8cae73aa978082911e4777f961ac472b5cd319c
Refs 194

No Test Failures!


Error lines from build-log.txt

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

Validating cluster test-cluster-1209.k8s.local

W0715 22:43:51.839448   17231 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-1209-k8s-n7qj4n-123648200.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-1209-k8s-n7qj4n-123648200.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0715 22:44:01.891503   17231 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-1209-k8s-n7qj4n-123648200.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-1209-k8s-n7qj4n-123648200.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0715 22:44:11.934410   17231 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-1209-k8s-n7qj4n-123648200.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-1209-k8s-n7qj4n-123648200.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0715 22:44:21.979136   17231 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-1209-k8s-n7qj4n-123648200.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-1209-k8s-n7qj4n-123648200.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0715 22:44:32.030410   17231 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-1209-k8s-n7qj4n-123648200.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-1209-k8s-n7qj4n-123648200.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0715 22:44:42.079093   17231 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-1209-k8s-n7qj4n-123648200.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-1209-k8s-n7qj4n-123648200.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0715 22:44:52.133203   17231 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-1209-k8s-n7qj4n-123648200.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-1209-k8s-n7qj4n-123648200.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0715 22:45:02.166428   17231 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-1209-k8s-n7qj4n-123648200.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-1209-k8s-n7qj4n-123648200.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0715 22:45:13.359331   17231 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-1209-k8s-n7qj4n-123648200.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-1209-k8s-n7qj4n-123648200.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0715 22:45:26.872863   17231 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-1209-k8s-n7qj4n-123648200.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-1209-k8s-n7qj4n-123648200.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0715 22:45:44.950178   17231 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-1209-k8s-n7qj4n-123648200.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-1209-k8s-n7qj4n-123648200.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0715 22:46:06.565780   17231 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:46:28.300973   17231 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:46:49.910032   17231 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:47:11.546331   17231 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-0d35dfb81fee2a231				machine "i-0d35dfb81fee2a231" has not yet joined cluster
Node	ip-172-20-49-157.us-west-2.compute.internal	master "ip-172-20-49-157.us-west-2.compute.internal" is not ready

Validation Failed
W0715 22:47:24.408909   17231 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-0d35dfb81fee2a231								machine "i-0d35dfb81fee2a231" has not yet joined cluster
Node	ip-172-20-49-157.us-west-2.compute.internal					master "ip-172-20-49-157.us-west-2.compute.internal" is not ready
Pod	kube-system/etcd-manager-events-ip-172-20-49-157.us-west-2.compute.internal	system-cluster-critical pod "etcd-manager-events-ip-172-20-49-157.us-west-2.compute.internal" is pending
Pod	kube-system/etcd-manager-main-ip-172-20-49-157.us-west-2.compute.internal	system-cluster-critical pod "etcd-manager-main-ip-172-20-49-157.us-west-2.compute.internal" is pending
Pod	kube-system/kube-apiserver-ip-172-20-49-157.us-west-2.compute.internal		system-cluster-critical pod "kube-apiserver-ip-172-20-49-157.us-west-2.compute.internal" is pending

Validation Failed
W0715 22:47:35.515247   17231 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 7 lines ...
Node	ip-172-20-49-157.us-west-2.compute.internal	master "ip-172-20-49-157.us-west-2.compute.internal" is not ready
Pod	kube-system/coredns-5489b75945-kbk86		system-cluster-critical pod "coredns-5489b75945-kbk86" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-7d6kp	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-7d6kp" is pending
Pod	kube-system/dns-controller-8574dcc89d-w7s5p	system-cluster-critical pod "dns-controller-8574dcc89d-w7s5p" is pending
Pod	kube-system/kops-controller-wz8s4		system-node-critical pod "kops-controller-wz8s4" is pending

Validation Failed
W0715 22:47:46.623599   17231 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-0d35dfb81fee2a231				machine "i-0d35dfb81fee2a231" has not yet joined cluster
Pod	kube-system/coredns-5489b75945-kbk86		system-cluster-critical pod "coredns-5489b75945-kbk86" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-7d6kp	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-7d6kp" is pending
Pod	kube-system/dns-controller-8574dcc89d-w7s5p	system-cluster-critical pod "dns-controller-8574dcc89d-w7s5p" is pending
Pod	kube-system/kops-controller-wz8s4		system-node-critical pod "kops-controller-wz8s4" is pending

Validation Failed
W0715 22:47:57.749537   17231 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-0d35dfb81fee2a231				machine "i-0d35dfb81fee2a231" has not yet joined cluster
Pod	kube-system/coredns-5489b75945-kbk86		system-cluster-critical pod "coredns-5489b75945-kbk86" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-7d6kp	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-7d6kp" is pending
Pod	kube-system/dns-controller-8574dcc89d-w7s5p	system-cluster-critical pod "dns-controller-8574dcc89d-w7s5p" is pending
Pod	kube-system/kops-controller-wz8s4		system-node-critical pod "kops-controller-wz8s4" is pending

Validation Failed
W0715 22:48:08.996854   17231 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-0d35dfb81fee2a231				machine "i-0d35dfb81fee2a231" has not yet joined cluster
Pod	kube-system/coredns-5489b75945-kbk86		system-cluster-critical pod "coredns-5489b75945-kbk86" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-7d6kp	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-7d6kp" is pending

Validation Failed
W0715 22:48:20.032415   17231 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-0d35dfb81fee2a231				machine "i-0d35dfb81fee2a231" has not yet joined cluster
Node	ip-172-20-49-157.us-west-2.compute.internal	master "ip-172-20-49-157.us-west-2.compute.internal" is missing kube-controller-manager pod
Node	ip-172-20-49-157.us-west-2.compute.internal	master "ip-172-20-49-157.us-west-2.compute.internal" is missing kube-scheduler pod
Pod	kube-system/coredns-5489b75945-kbk86		system-cluster-critical pod "coredns-5489b75945-kbk86" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-7d6kp	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-7d6kp" is pending

Validation Failed
W0715 22:48:31.156073   17231 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 8 lines ...
Node	ip-172-20-49-157.us-west-2.compute.internal				master "ip-172-20-49-157.us-west-2.compute.internal" is missing kube-controller-manager pod
Pod	kube-system/coredns-5489b75945-kbk86					system-cluster-critical pod "coredns-5489b75945-kbk86" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-7d6kp				system-cluster-critical pod "coredns-autoscaler-6f594f4c58-7d6kp" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-223.us-west-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-223.us-west-2.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-49-157.us-west-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-49-157.us-west-2.compute.internal" is pending

Validation Failed
W0715 22:48:42.255646   17231 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-kbk86		system-cluster-critical pod "coredns-5489b75945-kbk86" is not ready (coredns)
Pod	kube-system/coredns-autoscaler-6f594f4c58-7d6kp	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-7d6kp" is pending

Validation Failed
W0715 22:48:53.395380   17231 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 ...
ip-172-20-49-157.us-west-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5489b75945-pd527	system-cluster-critical pod "coredns-5489b75945-pd527" is not ready (coredns)

Validation Failed
W0715 22:49:04.441632   17231 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-1209.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=1209 --wait --kubeconfig /home/prow/go/src/github.com/kubernetes-sigs/aws-fsx-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-1209.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/node.yaml:126): unexpected EOF
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 ...