This job view page is being replaced by Spyglass soon. Check out the new job view.
PRwongma7: Helm chart 1.0
ResultABORTED
Tests 0 failed / 0 succeeded
Started2021-07-16 21:58
Elapsed17m26s
Revisionbc9e87eac67099994c8c32f970658044b5c00ae9
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-18016.k8s.local
#
Using cluster from kubectl context: test-cluster-18016.k8s.local

Validating cluster test-cluster-18016.k8s.local

W0716 22:05:09.341568   17231 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-18016-k8-0v8ig3-1465934571.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-18016-k8-0v8ig3-1465934571.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0716 22:05:19.377660   17231 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-18016-k8-0v8ig3-1465934571.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-18016-k8-0v8ig3-1465934571.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0716 22:05:29.413124   17231 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-18016-k8-0v8ig3-1465934571.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-18016-k8-0v8ig3-1465934571.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0716 22:05:39.448758   17231 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-18016-k8-0v8ig3-1465934571.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-18016-k8-0v8ig3-1465934571.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0716 22:05:49.495769   17231 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-18016-k8-0v8ig3-1465934571.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-18016-k8-0v8ig3-1465934571.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0716 22:06:01.864812   17231 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-18016-k8-0v8ig3-1465934571.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-18016-k8-0v8ig3-1465934571.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0716 22:06:13.068135   17231 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-18016-k8-0v8ig3-1465934571.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-18016-k8-0v8ig3-1465934571.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0716 22:06:34.720723   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)
W0716 22:06:56.496868   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)
W0716 22:07:18.097662   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)
W0716 22:07:39.756825   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)
W0716 22:08:01.378709   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)
W0716 22:08:23.036515   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)
W0716 22:08:44.829987   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 5 lines ...
Machine	i-02fa8f8174b5a8b3e								machine "i-02fa8f8174b5a8b3e" has not yet joined cluster
Node	ip-172-20-35-72.us-west-2.compute.internal					master "ip-172-20-35-72.us-west-2.compute.internal" is not ready
Pod	kube-system/etcd-manager-events-ip-172-20-35-72.us-west-2.compute.internal	system-cluster-critical pod "etcd-manager-events-ip-172-20-35-72.us-west-2.compute.internal" is pending
Pod	kube-system/kube-apiserver-ip-172-20-35-72.us-west-2.compute.internal		system-cluster-critical pod "kube-apiserver-ip-172-20-35-72.us-west-2.compute.internal" is pending
Pod	kube-system/kube-scheduler-ip-172-20-35-72.us-west-2.compute.internal		system-cluster-critical pod "kube-scheduler-ip-172-20-35-72.us-west-2.compute.internal" is pending

Validation Failed
W0716 22:09:03.413829   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-02fa8f8174b5a8b3e				machine "i-02fa8f8174b5a8b3e" has not yet joined cluster
Node	ip-172-20-35-72.us-west-2.compute.internal	master "ip-172-20-35-72.us-west-2.compute.internal" is missing kube-controller-manager pod
Pod	kube-system/coredns-5489b75945-qj7ts		system-cluster-critical pod "coredns-5489b75945-qj7ts" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-d48km	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-d48km" is pending
Pod	kube-system/dns-controller-8574dcc89d-xbbpl	system-cluster-critical pod "dns-controller-8574dcc89d-xbbpl" is pending

Validation Failed
W0716 22:09:14.617133   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 ...
KIND	NAME						MESSAGE
Machine	i-02fa8f8174b5a8b3e				machine "i-02fa8f8174b5a8b3e" has not yet joined cluster
Node	ip-172-20-35-72.us-west-2.compute.internal	master "ip-172-20-35-72.us-west-2.compute.internal" is missing kube-controller-manager pod
Pod	kube-system/coredns-5489b75945-qj7ts		system-cluster-critical pod "coredns-5489b75945-qj7ts" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-d48km	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-d48km" is pending

Validation Failed
W0716 22:09:25.884125   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-35-72.us-west-2.compute.internal				master "ip-172-20-35-72.us-west-2.compute.internal" is missing kube-controller-manager pod
Node	ip-172-20-38-218.us-west-2.compute.internal				node "ip-172-20-38-218.us-west-2.compute.internal" is not ready
Pod	kube-system/coredns-5489b75945-qj7ts					system-cluster-critical pod "coredns-5489b75945-qj7ts" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-d48km				system-cluster-critical pod "coredns-autoscaler-6f594f4c58-d48km" is pending
Pod	kube-system/kube-proxy-ip-172-20-38-218.us-west-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-38-218.us-west-2.compute.internal" is pending

Validation Failed
W0716 22:09:36.992974   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 ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Node	ip-172-20-35-72.us-west-2.compute.internal	master "ip-172-20-35-72.us-west-2.compute.internal" is missing kube-controller-manager pod
Pod	kube-system/coredns-5489b75945-qj7ts		system-cluster-critical pod "coredns-5489b75945-qj7ts" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-d48km	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-d48km" is pending

Validation Failed
W0716 22:09:48.185938   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-38-218.us-west-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Node	ip-172-20-35-72.us-west-2.compute.internal	master "ip-172-20-35-72.us-west-2.compute.internal" is missing kube-controller-manager pod

Validation Failed
W0716 22:09:59.351138   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
Node	ip-172-20-35-72.us-west-2.compute.internal					master "ip-172-20-35-72.us-west-2.compute.internal" is missing kube-controller-manager pod
Pod	kube-system/kube-controller-manager-ip-172-20-35-72.us-west-2.compute.internal	system-cluster-critical pod "kube-controller-manager-ip-172-20-35-72.us-west-2.compute.internal" is pending

Validation Failed
W0716 22:10:10.541930   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-38-218.us-west-2.compute.internal	node	True

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

Validation Failed
W0716 22:10:21.612766   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-18016.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=18016 --wait --kubeconfig /home/prow/go/src/github.com/kubernetes-sigs/aws-fsx-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-18016.k8s.local.kops.kubeconfig ./charts/aws-fsx-csi-driver -f ./hack/values.yaml
Release "aws-fsx-csi-driver" does not exist. Installing it now.
{"component":"entrypoint","file":"prow/entrypoint/run.go:169","func":"k8s.io/test-infra/prow/entrypoint.Options.ExecuteProcess","level":"error","msg":"Entrypoint received interrupt: terminated","severity":"error","time":"2021-07-16T22:10:46Z"}
++ early_exit_handler
++ '[' -n 187 ']'
++ kill -TERM 187
++ cleanup_dind
++ [[ true == \t\r\u\e ]]
++ echo 'Cleaning up after docker'
... skipping 5 lines ...