This job view page is being replaced by Spyglass soon. Check out the new job view.
PRjonathanrainer: Adds capability to provision directories on the EFS dynamically
ResultFAILURE
Tests 1 failed / 36 succeeded
Started2023-02-04 15:15
Elapsed24m44s
Revision4a2d3428f97687ab248e1252ea44bb382778b03a
Refs 732

Test Failures


EFS CSI Suite [efs-csi] EFS CSI [Driver: efs.csi.aws.com] should create a directory with the correct permissions when in directory provisioning mode 37s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=EFS\sCSI\sSuite\s\[efs\-csi\]\sEFS\sCSI\s\[Driver\:\sefs\.csi\.aws\.com\]\sshould\screate\sa\sdirectory\swith\sthe\scorrect\spermissions\swhen\sin\sdirectory\sprovisioning\smode$'
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:398
Checking File Permissions of mounted folder
Expected
    <string>: 755
to equal
    <string>: 777
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:426
				
				Click to see stdout/stderrfrom junit_04.xml

Filter through log files | View test history on testgrid


Show 36 Passed Tests

Show 153 Skipped Tests

Error lines from build-log.txt

... skipping 352 lines ...
#11 2.608 --> Processing Dependency: libperl.so()(64bit) for package: 4:perl-5.16.3-299.amzn2.0.1.x86_64
#11 2.609 ---> Package perl-File-Temp.noarch 0:0.23.01-3.amzn2 will be installed
#11 2.611 ---> Package perl-Getopt-Long.noarch 0:2.40-3.amzn2 will be installed
#11 2.613 --> Processing Dependency: perl(Pod::Usage) >= 1.14 for package: perl-Getopt-Long-2.40-3.amzn2.noarch
#11 2.615 --> Processing Dependency: perl(Text::ParseWords) for package: perl-Getopt-Long-2.40-3.amzn2.noarch
#11 2.616 ---> Package perl-Git.noarch 0:2.39.1-1.amzn2.0.1 will be installed
#11 2.617 --> Processing Dependency: perl(Error) for package: perl-Git-2.39.1-1.amzn2.0.1.noarch
#11 2.618 ---> Package perl-PathTools.x86_64 0:3.40-5.amzn2.0.2 will be installed
#11 2.621 ---> Package perl-TermReadKey.x86_64 0:2.30-20.amzn2.0.2 will be installed
#11 2.622 ---> Package perl-Thread-Queue.noarch 0:3.02-2.amzn2 will be installed
#11 2.623 ---> Package perl-threads.x86_64 0:1.87-4.amzn2.0.2 will be installed
#11 2.625 ---> Package pkgconfig.x86_64 1:0.27.1-4.amzn2.0.2 will be installed
#11 2.628 ---> Package system-rpm-config.noarch 0:9.1.0-76.amzn2.0.14 will be installed
... skipping 15 lines ...
#11 2.709 --> Processing Dependency: openssh = 7.4p1-22.amzn2.0.1 for package: openssh-clients-7.4p1-22.amzn2.0.1.x86_64
#11 2.711 --> Processing Dependency: fipscheck-lib(x86-64) >= 1.3.0 for package: openssh-clients-7.4p1-22.amzn2.0.1.x86_64
#11 2.714 --> Processing Dependency: libfipscheck.so.1()(64bit) for package: openssh-clients-7.4p1-22.amzn2.0.1.x86_64
#11 2.714 --> Processing Dependency: libedit.so.0()(64bit) for package: openssh-clients-7.4p1-22.amzn2.0.1.x86_64
#11 2.716 ---> Package pcre2.x86_64 0:10.23-11.amzn2.0.1 will be installed
#11 2.718 ---> Package perl-Carp.noarch 0:1.26-244.amzn2 will be installed
#11 2.719 ---> Package perl-Error.noarch 1:0.17020-2.amzn2 will be installed
#11 2.720 ---> Package perl-Exporter.noarch 0:5.68-3.amzn2 will be installed
#11 2.721 ---> Package perl-File-Path.noarch 0:2.09-2.amzn2 will be installed
#11 2.722 ---> Package perl-Filter.x86_64 0:1.49-3.amzn2.0.2 will be installed
#11 2.724 ---> Package perl-Pod-Simple.noarch 1:3.28-4.amzn2 will be installed
#11 2.728 --> Processing Dependency: perl(Pod::Escapes) >= 1.04 for package: 1:perl-Pod-Simple-3.28-4.amzn2.noarch
#11 2.730 --> Processing Dependency: perl(Encode) for package: 1:perl-Pod-Simple-3.28-4.amzn2.noarch
... skipping 168 lines ...
#11 3.197  pam                       x86_64 1.1.8-23.amzn2.0.1           amzn2-core 715 k
#11 3.197  patch                     x86_64 2.7.1-12.amzn2.0.2           amzn2-core 110 k
#11 3.197  pcre2                     x86_64 10.23-11.amzn2.0.1           amzn2-core 207 k
#11 3.197  perl                      x86_64 4:5.16.3-299.amzn2.0.1       amzn2-core 8.0 M
#11 3.197  perl-Carp                 noarch 1.26-244.amzn2               amzn2-core  19 k
#11 3.197  perl-Encode               x86_64 2.51-7.amzn2.0.2             amzn2-core 1.5 M
#11 3.197  perl-Error                noarch 1:0.17020-2.amzn2            amzn2-core  32 k
#11 3.197  perl-Exporter             noarch 5.68-3.amzn2                 amzn2-core  29 k
#11 3.197  perl-File-Path            noarch 2.09-2.amzn2                 amzn2-core  27 k
#11 3.197  perl-File-Temp            noarch 0.23.01-3.amzn2              amzn2-core  56 k
#11 3.197  perl-Filter               x86_64 1.49-3.amzn2.0.2             amzn2-core  76 k
#11 3.197  perl-Getopt-Long          noarch 2.40-3.amzn2                 amzn2-core  56 k
#11 3.197  perl-Git                  noarch 2.39.1-1.amzn2.0.1           amzn2-core  41 k
... skipping 91 lines ...
#11 9.137   Installing : 1:perl-Pod-Simple-3.28-4.amzn2.noarch                      34/87 
#11 9.189   Installing : perl-Getopt-Long-2.40-3.amzn2.noarch                       35/87 
#11 9.334   Installing : 4:perl-libs-5.16.3-299.amzn2.0.1.x86_64                    36/87 
#11 11.06   Installing : 4:perl-5.16.3-299.amzn2.0.1.x86_64                         37/87 
#11 11.13   Installing : perl-Thread-Queue-3.02-2.amzn2.noarch                      38/87 
#11 11.16   Installing : perl-TermReadKey-2.30-20.amzn2.0.2.x86_64                  39/87 
#11 11.20   Installing : 1:perl-Error-0.17020-2.amzn2.noarch                        40/87 
#11 11.23   Installing : fipscheck-lib-1.4.1-6.amzn2.0.2.x86_64                     41/87 
#11 11.27   Installing : fipscheck-1.4.1-6.amzn2.0.2.x86_64                         42/87 
#11 11.32   Installing : dwz-0.11-3.amzn2.0.3.x86_64                                43/87 
#11 11.38   Installing : 1:pkgconfig-0.27.1-4.amzn2.0.2.x86_64                      44/87 
#11 11.43   Installing : kmod-libs-25-3.amzn2.0.2.x86_64                            45/87 
#11 11.51   Installing : unzip-6.0-57.amzn2.0.1.x86_64                              46/87 
... skipping 24 lines ...
#11 15.88   Installing : 7:device-mapper-libs-1.02.170-6.amzn2.5.x86_64             71/87 
#11 15.97   Installing : cryptsetup-libs-1.7.4-4.amzn2.x86_64                       72/87 
#11 16.08   Installing : elfutils-libs-0.176-2.amzn2.x86_64                         73/87 
#11 16.19   Installing : systemd-libs-219-78.amzn2.0.21.x86_64                      74/87 
#11 16.27   Installing : 1:dbus-libs-1.10.24-7.amzn2.0.2.x86_64                     75/87 
#11 17.76   Installing : systemd-219-78.amzn2.0.21.x86_64                           76/87 
#11 18.29 Failed to get D-Bus connection: Operation not permitted
#11 18.49   Installing : 1:dbus-1.10.24-7.amzn2.0.2.x86_64                          77/87 
#11 18.53   Installing : elfutils-default-yama-scope-0.176-2.amzn2.noarch           78/87 
#11 18.63   Installing : elfutils-0.176-2.amzn2.x86_64                              79/87 
#11 18.81   Installing : openssh-7.4p1-22.amzn2.0.1.x86_64                          80/87 
#11 18.97   Installing : openssh-clients-7.4p1-22.amzn2.0.1.x86_64                  81/87 
#11 20.67   Installing : git-core-2.39.1-1.amzn2.0.1.x86_64                         82/87 
... skipping 57 lines ...
#11 22.85   Verifying  : util-linux-2.30.2-2.amzn2.0.11.x86_64                      53/87 
#11 22.88   Verifying  : pam-1.1.8-23.amzn2.0.1.x86_64                              54/87 
#11 22.90   Verifying  : xz-5.2.2-1.amzn2.0.3.x86_64                                55/87 
#11 22.92   Verifying  : ustr-1.0.4-16.amzn2.0.3.x86_64                             56/87 
#11 22.93   Verifying  : less-458-9.amzn2.0.2.x86_64                                57/87 
#11 22.95   Verifying  : 1:perl-Pod-Escapes-1.04-299.amzn2.0.1.noarch               58/87 
#11 22.97   Verifying  : 1:perl-Error-0.17020-2.amzn2.noarch                        59/87 
#11 22.99   Verifying  : perl-Pod-Usage-1.63-3.amzn2.noarch                         60/87 
#11 23.00   Verifying  : 1:perl-parent-0.225-244.amzn2.0.1.noarch                   61/87 
#11 23.02   Verifying  : perl-Pod-Perldoc-3.20-4.amzn2.noarch                       62/87 
#11 23.06   Verifying  : 2:tar-1.26-35.amzn2.x86_64                                 63/87 
#11 23.08   Verifying  : zip-3.0-11.amzn2.0.2.x86_64                                64/87 
#11 23.12   Verifying  : 1:dbus-libs-1.10.24-7.amzn2.0.2.x86_64                     65/87 
... skipping 65 lines ...
#11 23.58   pam.x86_64 0:1.1.8-23.amzn2.0.1                                               
#11 23.58   patch.x86_64 0:2.7.1-12.amzn2.0.2                                             
#11 23.58   pcre2.x86_64 0:10.23-11.amzn2.0.1                                             
#11 23.58   perl.x86_64 4:5.16.3-299.amzn2.0.1                                            
#11 23.58   perl-Carp.noarch 0:1.26-244.amzn2                                             
#11 23.58   perl-Encode.x86_64 0:2.51-7.amzn2.0.2                                         
#11 23.58   perl-Error.noarch 1:0.17020-2.amzn2                                           
#11 23.58   perl-Exporter.noarch 0:5.68-3.amzn2                                           
#11 23.58   perl-File-Path.noarch 0:2.09-2.amzn2                                          
#11 23.58   perl-File-Temp.noarch 0:0.23.01-3.amzn2                                       
#11 23.58   perl-Filter.x86_64 0:1.49-3.amzn2.0.2                                         
#11 23.58   perl-Getopt-Long.noarch 0:2.40-3.amzn2                                        
#11 23.58   perl-Git.noarch 0:2.39.1-1.amzn2.0.1                                          
... skipping 514 lines ...
#19 exporting to image
#19 exporting layers
#19 exporting layers 2.8s done
#19 writing image sha256:d2a03021c6cb96ddeb7f983543a8b2bd3b1b11b25a7c9d069aeb747d540473a3 done
#19 naming to 607362164682.dkr.ecr.us-west-2.amazonaws.com/aws-efs-csi-driver:7412-linux-amd64-amazon done
#19 DONE 2.8s
WARNING: failed to get git remote url: fatal: No remote configured to list refs from.
touch .image-7412-linux-amd64-amazon
make[1]: Leaving directory '/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver'
The push refers to repository [607362164682.dkr.ecr.us-west-2.amazonaws.com/aws-efs-csi-driver]
afdc45ef9437: Preparing
3119c43fe67e: Preparing
be1116011055: Preparing
... skipping 118 lines ...
## Validating cluster test-cluster-7412.k8s.local
#
Using cluster from kubectl context: test-cluster-7412.k8s.local

Validating cluster test-cluster-7412.k8s.local

W0204 15:19:05.569667    5579 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-7412-k8s-i0tdeg-1770285821.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-7412-k8s-i0tdeg-1770285821.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0204 15:19:15.596860    5579 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-7412-k8s-i0tdeg-1770285821.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-7412-k8s-i0tdeg-1770285821.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0204 15:19:25.630567    5579 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-7412-k8s-i0tdeg-1770285821.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-7412-k8s-i0tdeg-1770285821.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0204 15:19:35.664899    5579 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-7412-k8s-i0tdeg-1770285821.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-7412-k8s-i0tdeg-1770285821.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0204 15:19:45.703494    5579 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-7412-k8s-i0tdeg-1770285821.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-7412-k8s-i0tdeg-1770285821.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0204 15:19:55.753620    5579 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-7412-k8s-i0tdeg-1770285821.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-7412-k8s-i0tdeg-1770285821.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0204 15:20:05.792840    5579 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-7412-k8s-i0tdeg-1770285821.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-7412-k8s-i0tdeg-1770285821.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0204 15:20:27.538904    5579 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)
W0204 15:20:38.722468    5579 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-7412-k8s-i0tdeg-1770285821.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-7412-k8s-i0tdeg-1770285821.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0204 15:21:00.384422    5579 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)
W0204 15:21:22.049552    5579 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	c5.large	1	1	us-west-2a
nodes-us-west-2b	Node	c5.large	1	1	us-west-2b
nodes-us-west-2c	Node	c5.large	1	1	us-west-2c
... skipping 6 lines ...
KIND	NAME						MESSAGE
Machine	i-05ac8ce6d5d7fd60b				machine "i-05ac8ce6d5d7fd60b" has not yet joined cluster
Machine	i-08769ae138455d8cc				machine "i-08769ae138455d8cc" has not yet joined cluster
Machine	i-093eb1f658393afca				machine "i-093eb1f658393afca" has not yet joined cluster
Node	ip-172-20-61-236.us-west-2.compute.internal	node "ip-172-20-61-236.us-west-2.compute.internal" of role "master" is not ready

Validation Failed
W0204 15:21:42.999276    5579 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	c5.large	1	1	us-west-2a
nodes-us-west-2b	Node	c5.large	1	1	us-west-2b
... skipping 9 lines ...
Machine	i-08769ae138455d8cc				machine "i-08769ae138455d8cc" has not yet joined cluster
Machine	i-093eb1f658393afca				machine "i-093eb1f658393afca" has not yet joined cluster
Pod	kube-system/coredns-8f5559c9b-d28pc		system-cluster-critical pod "coredns-8f5559c9b-d28pc" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-k8fsm	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-k8fsm" is pending
Pod	kube-system/dns-controller-5d59c585d8-fcxvb	system-cluster-critical pod "dns-controller-5d59c585d8-fcxvb" is pending

Validation Failed
W0204 15:21:55.302411    5579 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	c5.large	1	1	us-west-2a
nodes-us-west-2b	Node	c5.large	1	1	us-west-2b
... skipping 9 lines ...
Machine	i-08769ae138455d8cc				machine "i-08769ae138455d8cc" has not yet joined cluster
Machine	i-093eb1f658393afca				machine "i-093eb1f658393afca" has not yet joined cluster
Pod	kube-system/coredns-8f5559c9b-d28pc		system-cluster-critical pod "coredns-8f5559c9b-d28pc" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-k8fsm	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-k8fsm" is pending
Pod	kube-system/dns-controller-5d59c585d8-fcxvb	system-cluster-critical pod "dns-controller-5d59c585d8-fcxvb" is pending

Validation Failed
W0204 15:22:07.434179    5579 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	c5.large	1	1	us-west-2a
nodes-us-west-2b	Node	c5.large	1	1	us-west-2b
... skipping 11 lines ...
Pod	kube-system/coredns-8f5559c9b-d28pc					system-cluster-critical pod "coredns-8f5559c9b-d28pc" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-k8fsm				system-cluster-critical pod "coredns-autoscaler-6f594f4c58-k8fsm" is pending
Pod	kube-system/dns-controller-5d59c585d8-fcxvb				system-cluster-critical pod "dns-controller-5d59c585d8-fcxvb" is pending
Pod	kube-system/kube-proxy-ip-172-20-61-236.us-west-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-61-236.us-west-2.compute.internal" is pending
Pod	kube-system/kube-scheduler-ip-172-20-61-236.us-west-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-61-236.us-west-2.compute.internal" is pending

Validation Failed
W0204 15:22:19.557439    5579 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	c5.large	1	1	us-west-2a
nodes-us-west-2b	Node	c5.large	1	1	us-west-2b
... skipping 11 lines ...
Pod	kube-system/coredns-8f5559c9b-d28pc						system-cluster-critical pod "coredns-8f5559c9b-d28pc" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-k8fsm					system-cluster-critical pod "coredns-autoscaler-6f594f4c58-k8fsm" is pending
Pod	kube-system/dns-controller-5d59c585d8-fcxvb					system-cluster-critical pod "dns-controller-5d59c585d8-fcxvb" is pending
Pod	kube-system/etcd-manager-main-ip-172-20-61-236.us-west-2.compute.internal	system-cluster-critical pod "etcd-manager-main-ip-172-20-61-236.us-west-2.compute.internal" is pending
Pod	kube-system/kube-controller-manager-ip-172-20-61-236.us-west-2.compute.internal	system-cluster-critical pod "kube-controller-manager-ip-172-20-61-236.us-west-2.compute.internal" is pending

Validation Failed
W0204 15:22:31.648114    5579 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	c5.large	1	1	us-west-2a
nodes-us-west-2b	Node	c5.large	1	1	us-west-2b
... skipping 8 lines ...
Machine	i-05ac8ce6d5d7fd60b				machine "i-05ac8ce6d5d7fd60b" has not yet joined cluster
Machine	i-08769ae138455d8cc				machine "i-08769ae138455d8cc" has not yet joined cluster
Machine	i-093eb1f658393afca				machine "i-093eb1f658393afca" has not yet joined cluster
Pod	kube-system/coredns-8f5559c9b-d28pc		system-cluster-critical pod "coredns-8f5559c9b-d28pc" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-k8fsm	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-k8fsm" is pending

Validation Failed
W0204 15:22:43.732751    5579 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	c5.large	1	1	us-west-2a
nodes-us-west-2b	Node	c5.large	1	1	us-west-2b
... skipping 9 lines ...
Machine	i-08769ae138455d8cc							machine "i-08769ae138455d8cc" has not yet joined cluster
Machine	i-093eb1f658393afca							machine "i-093eb1f658393afca" has not yet joined cluster
Pod	kube-system/coredns-8f5559c9b-d28pc					system-cluster-critical pod "coredns-8f5559c9b-d28pc" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-k8fsm				system-cluster-critical pod "coredns-autoscaler-6f594f4c58-k8fsm" is pending
Pod	kube-system/kube-proxy-ip-172-20-66-157.us-west-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-66-157.us-west-2.compute.internal" is pending

Validation Failed
W0204 15:22:56.368286    5579 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	c5.large	1	1	us-west-2a
nodes-us-west-2b	Node	c5.large	1	1	us-west-2b
... skipping 9 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Node	ip-172-20-104-189.us-west-2.compute.internal	node "ip-172-20-104-189.us-west-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-8f5559c9b-d28pc		system-cluster-critical pod "coredns-8f5559c9b-d28pc" is pending
Pod	kube-system/coredns-8f5559c9b-hfx5p		system-cluster-critical pod "coredns-8f5559c9b-hfx5p" is pending

Validation Failed
W0204 15:23:08.440275    5579 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	c5.large	1	1	us-west-2a
nodes-us-west-2b	Node	c5.large	1	1	us-west-2b
... skipping 739 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Feb  4 15:26:30.361: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-7412.k8s.local.kops.kubeconfig
STEP: Building a namespace api object, basename volumemode
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail to use a volume in a pod with mismatched mode [Slow]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:297
Feb  4 15:26:30.699: INFO: Driver "efs.csi.aws.com" does not provide raw block - skipping
[AfterEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Feb  4 15:26:30.699: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-6258" for this suite.
... skipping 7 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227
    [Testpattern: Dynamic PV (block volmode)] volumeMode
    /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail to use a volume in a pod with mismatched mode [Slow] [It]
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:297

      Driver "efs.csi.aws.com" does not provide raw block - skipping

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:113
------------------------------
... skipping 43 lines ...
STEP: Building a namespace api object, basename efs
STEP: Waiting for a default service account to be provisioned in namespace
[It] should mount with option tls when encryptInTransit set true
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:367
STEP: Creating efs pvc & pv
STEP: Creating pod to mount pvc "efs-6831" and run "mount && mount | grep /mnt/volume1 | grep 127.0.0.1"
Feb  4 15:26:32.017: INFO: Waiting up to 5m0s for pod "pvc-tester-mn9r7" in namespace "efs-6831" to be "Succeeded or Failed"
Feb  4 15:26:32.086: INFO: Pod "pvc-tester-mn9r7": Phase="Pending", Reason="", readiness=false. Elapsed: 69.428928ms
Feb  4 15:26:34.170: INFO: Pod "pvc-tester-mn9r7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.152979414s
Feb  4 15:26:36.240: INFO: Pod "pvc-tester-mn9r7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.222636373s
Feb  4 15:26:38.308: INFO: Pod "pvc-tester-mn9r7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.291358414s
Feb  4 15:26:40.378: INFO: Pod "pvc-tester-mn9r7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.360686001s
Feb  4 15:26:42.447: INFO: Pod "pvc-tester-mn9r7": Phase="Pending", Reason="", readiness=false. Elapsed: 10.429900173s
Feb  4 15:26:44.515: INFO: Pod "pvc-tester-mn9r7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.49750197s
STEP: Saw pod success
Feb  4 15:26:44.515: INFO: Pod "pvc-tester-mn9r7" satisfied condition "Succeeded or Failed"
Feb  4 15:26:44.595: INFO: pod "pvc-tester-mn9r7" logs:
 overlay on / type overlay (rw,relatime,lowerdir=/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/34/fs,upperdir=/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/49/fs,workdir=/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/49/work)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev type tmpfs (rw,nosuid,size=65536k,mode=755,inode64)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=666)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
... skipping 76 lines ...
Feb  4 15:26:24.858: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.comvhcjj] to have phase Bound
Feb  4 15:26:24.923: INFO: PersistentVolumeClaim efs.csi.aws.comvhcjj found but phase is Pending instead of Bound.
Feb  4 15:26:26.994: INFO: PersistentVolumeClaim efs.csi.aws.comvhcjj found but phase is Pending instead of Bound.
Feb  4 15:26:29.065: INFO: PersistentVolumeClaim efs.csi.aws.comvhcjj found and phase=Bound (4.207216077s)
STEP: Creating pod pod-subpath-test-dynamicpv-xhd7
STEP: Creating a pod to test subpath
Feb  4 15:26:29.275: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-xhd7" in namespace "provisioning-495" to be "Succeeded or Failed"
Feb  4 15:26:29.341: INFO: Pod "pod-subpath-test-dynamicpv-xhd7": Phase="Pending", Reason="", readiness=false. Elapsed: 65.97129ms
Feb  4 15:26:31.408: INFO: Pod "pod-subpath-test-dynamicpv-xhd7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.132372096s
Feb  4 15:26:33.473: INFO: Pod "pod-subpath-test-dynamicpv-xhd7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.198076581s
Feb  4 15:26:35.540: INFO: Pod "pod-subpath-test-dynamicpv-xhd7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.264791383s
Feb  4 15:26:37.606: INFO: Pod "pod-subpath-test-dynamicpv-xhd7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.331009164s
Feb  4 15:26:39.672: INFO: Pod "pod-subpath-test-dynamicpv-xhd7": Phase="Pending", Reason="", readiness=false. Elapsed: 10.397230165s
Feb  4 15:26:41.740: INFO: Pod "pod-subpath-test-dynamicpv-xhd7": Phase="Pending", Reason="", readiness=false. Elapsed: 12.464575858s
Feb  4 15:26:43.806: INFO: Pod "pod-subpath-test-dynamicpv-xhd7": Phase="Pending", Reason="", readiness=false. Elapsed: 14.531064803s
Feb  4 15:26:45.874: INFO: Pod "pod-subpath-test-dynamicpv-xhd7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.599212947s
STEP: Saw pod success
Feb  4 15:26:45.874: INFO: Pod "pod-subpath-test-dynamicpv-xhd7" satisfied condition "Succeeded or Failed"
Feb  4 15:26:45.939: INFO: Trying to get logs from node ip-172-20-104-189.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-xhd7 container test-container-subpath-dynamicpv-xhd7: <nil>
STEP: delete the pod
Feb  4 15:26:46.089: INFO: Waiting for pod pod-subpath-test-dynamicpv-xhd7 to disappear
Feb  4 15:26:46.154: INFO: Pod pod-subpath-test-dynamicpv-xhd7 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-xhd7
Feb  4 15:26:46.154: INFO: Deleting pod "pod-subpath-test-dynamicpv-xhd7" in namespace "provisioning-495"
... skipping 127 lines ...

      Driver "efs.csi.aws.com" does not provide raw block - skipping

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:113
------------------------------
[efs-csi] EFS CSI [Driver: efs.csi.aws.com] [Testpattern: Dynamic PV (default fs)] subPath 
  should fail if subpath file is outside the volume [Slow][LinuxOnly]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 6 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Feb  4 15:26:29.427: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-7412.k8s.local.kops.kubeconfig
STEP: Building a namespace api object, basename provisioning
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail if subpath file is outside the volume [Slow][LinuxOnly]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Feb  4 15:26:29.932: INFO: Creating resource for dynamic PV
Feb  4 15:26:29.932: INFO: Using claimSize:1Mi, test suite supported size:{ 1Mi}, driver(efs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass 
STEP: creating a claim
Feb  4 15:26:29.997: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Feb  4 15:26:30.062: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.comdgslb] to have phase Bound
Feb  4 15:26:30.133: INFO: PersistentVolumeClaim efs.csi.aws.comdgslb found but phase is Pending instead of Bound.
Feb  4 15:26:32.198: INFO: PersistentVolumeClaim efs.csi.aws.comdgslb found and phase=Bound (2.135388379s)
STEP: Creating pod pod-subpath-test-dynamicpv-pkhp
STEP: Checking for subpath error in container status
Feb  4 15:26:44.527: INFO: Deleting pod "pod-subpath-test-dynamicpv-pkhp" in namespace "provisioning-2888"
Feb  4 15:26:44.592: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-pkhp" to be fully deleted
STEP: Deleting pod
Feb  4 15:26:54.720: INFO: Deleting pod "pod-subpath-test-dynamicpv-pkhp" in namespace "provisioning-2888"
STEP: Deleting pvc
Feb  4 15:26:54.785: INFO: Deleting PersistentVolumeClaim "efs.csi.aws.comdgslb"
... skipping 15 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227
    [Testpattern: Dynamic PV (default fs)] subPath
    /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath file is outside the volume [Slow][LinuxOnly]
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[efs-csi] EFS CSI [Driver: efs.csi.aws.com] [Testpattern: Dynamic PV (default fs)] subPath 
  should verify container cannot write to subpath readonly volumes [Slow]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:423

... skipping 21 lines ...
STEP: creating a claim
Feb  4 15:26:58.586: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Feb  4 15:26:58.656: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.com4xtk7] to have phase Bound
Feb  4 15:26:58.724: INFO: PersistentVolumeClaim efs.csi.aws.com4xtk7 found but phase is Pending instead of Bound.
Feb  4 15:27:00.793: INFO: PersistentVolumeClaim efs.csi.aws.com4xtk7 found and phase=Bound (2.136629025s)
STEP: Creating pod to format volume volume-prep-provisioning-4324
Feb  4 15:27:00.997: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-4324" in namespace "provisioning-4324" to be "Succeeded or Failed"
Feb  4 15:27:01.070: INFO: Pod "volume-prep-provisioning-4324": Phase="Pending", Reason="", readiness=false. Elapsed: 72.715774ms
Feb  4 15:27:03.140: INFO: Pod "volume-prep-provisioning-4324": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.142705149s
STEP: Saw pod success
Feb  4 15:27:03.140: INFO: Pod "volume-prep-provisioning-4324" satisfied condition "Succeeded or Failed"
Feb  4 15:27:03.140: INFO: Deleting pod "volume-prep-provisioning-4324" in namespace "provisioning-4324"
Feb  4 15:27:03.217: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-4324" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-95c4
STEP: Checking for subpath error in container status
Feb  4 15:27:05.494: INFO: Deleting pod "pod-subpath-test-dynamicpv-95c4" in namespace "provisioning-4324"
Feb  4 15:27:05.580: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-95c4" to be fully deleted
STEP: Deleting pod
Feb  4 15:27:07.717: INFO: Deleting pod "pod-subpath-test-dynamicpv-95c4" in namespace "provisioning-4324"
STEP: Deleting pvc
Feb  4 15:27:07.784: INFO: Deleting PersistentVolumeClaim "efs.csi.aws.com4xtk7"
... skipping 318 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath file is outside the volume [Slow][LinuxOnly] [BeforeEach]
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:244
------------------------------
... skipping 211 lines ...
    [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
    /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should concurrently access the single volume from pods on different node
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/multivolume.go:460
------------------------------
[efs-csi] EFS CSI [Driver: efs.csi.aws.com] [Testpattern: Dynamic PV (default fs)] subPath 
  should fail if subpath directory is outside the volume [Slow][LinuxOnly]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 6 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Feb  4 15:27:20.165: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-7412.k8s.local.kops.kubeconfig
STEP: Building a namespace api object, basename provisioning
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail if subpath directory is outside the volume [Slow][LinuxOnly]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Feb  4 15:27:20.720: INFO: Creating resource for dynamic PV
Feb  4 15:27:20.720: INFO: Using claimSize:1Mi, test suite supported size:{ 1Mi}, driver(efs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass 
STEP: creating a claim
Feb  4 15:27:20.789: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Feb  4 15:27:20.860: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.comr2mds] to have phase Bound
Feb  4 15:27:20.928: INFO: PersistentVolumeClaim efs.csi.aws.comr2mds found but phase is Pending instead of Bound.
Feb  4 15:27:22.995: INFO: PersistentVolumeClaim efs.csi.aws.comr2mds found and phase=Bound (2.135101055s)
STEP: Creating pod pod-subpath-test-dynamicpv-zw6z
STEP: Checking for subpath error in container status
Feb  4 15:27:27.340: INFO: Deleting pod "pod-subpath-test-dynamicpv-zw6z" in namespace "provisioning-3981"
Feb  4 15:27:27.411: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-zw6z" to be fully deleted
STEP: Deleting pod
Feb  4 15:27:37.546: INFO: Deleting pod "pod-subpath-test-dynamicpv-zw6z" in namespace "provisioning-3981"
STEP: Deleting pvc
Feb  4 15:27:37.614: INFO: Deleting PersistentVolumeClaim "efs.csi.aws.comr2mds"
... skipping 14 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227
    [Testpattern: Dynamic PV (default fs)] subPath
    /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath directory is outside the volume [Slow][LinuxOnly]
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 74 lines ...
STEP: Building a namespace api object, basename efs
STEP: Waiting for a default service account to be provisioned in namespace
[It] should mount different paths on same volume on same node
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:234
STEP: Creating efs pvc & pv with no subpath
STEP: Creating pod to make subpaths /a and /b
Feb  4 15:26:52.344: INFO: Waiting up to 5m0s for pod "pvc-tester-tm6fw" in namespace "efs-9947" to be "Succeeded or Failed"
Feb  4 15:26:52.409: INFO: Pod "pvc-tester-tm6fw": Phase="Pending", Reason="", readiness=false. Elapsed: 65.176663ms
Feb  4 15:26:54.475: INFO: Pod "pvc-tester-tm6fw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.130456344s
Feb  4 15:26:56.539: INFO: Pod "pvc-tester-tm6fw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.195275799s
Feb  4 15:26:58.606: INFO: Pod "pvc-tester-tm6fw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.261947413s
Feb  4 15:27:00.673: INFO: Pod "pvc-tester-tm6fw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.328675626s
Feb  4 15:27:02.750: INFO: Pod "pvc-tester-tm6fw": Phase="Pending", Reason="", readiness=false. Elapsed: 10.40539598s
... skipping 8 lines ...
Feb  4 15:27:21.352: INFO: Pod "pvc-tester-tm6fw": Phase="Pending", Reason="", readiness=false. Elapsed: 29.00755958s
Feb  4 15:27:23.418: INFO: Pod "pvc-tester-tm6fw": Phase="Pending", Reason="", readiness=false. Elapsed: 31.073532367s
Feb  4 15:27:25.483: INFO: Pod "pvc-tester-tm6fw": Phase="Pending", Reason="", readiness=false. Elapsed: 33.139247796s
Feb  4 15:27:27.549: INFO: Pod "pvc-tester-tm6fw": Phase="Pending", Reason="", readiness=false. Elapsed: 35.204811268s
Feb  4 15:27:29.622: INFO: Pod "pvc-tester-tm6fw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 37.27764616s
STEP: Saw pod success
Feb  4 15:27:29.622: INFO: Pod "pvc-tester-tm6fw" satisfied condition "Succeeded or Failed"
STEP: Creating efs pvc & pv with subpath /a
STEP: Creating efs pvc & pv with subpath /b
STEP: Creating pod to mount subpaths /a and /b
[AfterEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Feb  4 15:27:40.304: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
... skipping 39 lines ...
Feb  4 15:27:34.926: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Feb  4 15:27:35.001: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.com8dkxh] to have phase Bound
Feb  4 15:27:35.069: INFO: PersistentVolumeClaim efs.csi.aws.com8dkxh found but phase is Pending instead of Bound.
Feb  4 15:27:37.137: INFO: PersistentVolumeClaim efs.csi.aws.com8dkxh found and phase=Bound (2.136159238s)
STEP: Creating pod pod-subpath-test-dynamicpv-rp6c
STEP: Creating a pod to test multi_subpath
Feb  4 15:27:37.345: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-rp6c" in namespace "provisioning-999" to be "Succeeded or Failed"
Feb  4 15:27:37.412: INFO: Pod "pod-subpath-test-dynamicpv-rp6c": Phase="Pending", Reason="", readiness=false. Elapsed: 67.388417ms
Feb  4 15:27:39.484: INFO: Pod "pod-subpath-test-dynamicpv-rp6c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.138699885s
Feb  4 15:27:41.552: INFO: Pod "pod-subpath-test-dynamicpv-rp6c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.206581873s
STEP: Saw pod success
Feb  4 15:27:41.552: INFO: Pod "pod-subpath-test-dynamicpv-rp6c" satisfied condition "Succeeded or Failed"
Feb  4 15:27:41.620: INFO: Trying to get logs from node ip-172-20-104-189.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-rp6c container test-container-subpath-dynamicpv-rp6c: <nil>
STEP: delete the pod
Feb  4 15:27:41.765: INFO: Waiting for pod pod-subpath-test-dynamicpv-rp6c to disappear
Feb  4 15:27:41.832: INFO: Pod pod-subpath-test-dynamicpv-rp6c no longer exists
STEP: Deleting pod
Feb  4 15:27:41.832: INFO: Deleting pod "pod-subpath-test-dynamicpv-rp6c" in namespace "provisioning-999"
... skipping 245 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if non-existent subpath is outside the volume [Slow][LinuxOnly] [BeforeEach]
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:244
------------------------------
... skipping 528 lines ...
Feb  4 15:28:58.774: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Feb  4 15:28:58.844: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.com927l8] to have phase Bound
Feb  4 15:28:58.915: INFO: PersistentVolumeClaim efs.csi.aws.com927l8 found but phase is Pending instead of Bound.
Feb  4 15:29:00.986: INFO: PersistentVolumeClaim efs.csi.aws.com927l8 found and phase=Bound (2.141476491s)
STEP: Creating pod pod-subpath-test-dynamicpv-fdf7
STEP: Creating a pod to test atomic-volume-subpath
Feb  4 15:29:01.192: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-fdf7" in namespace "provisioning-1954" to be "Succeeded or Failed"
Feb  4 15:29:01.260: INFO: Pod "pod-subpath-test-dynamicpv-fdf7": Phase="Pending", Reason="", readiness=false. Elapsed: 67.892233ms
Feb  4 15:29:03.329: INFO: Pod "pod-subpath-test-dynamicpv-fdf7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.136249419s
Feb  4 15:29:05.397: INFO: Pod "pod-subpath-test-dynamicpv-fdf7": Phase="Running", Reason="", readiness=true. Elapsed: 4.204643899s
Feb  4 15:29:07.467: INFO: Pod "pod-subpath-test-dynamicpv-fdf7": Phase="Running", Reason="", readiness=true. Elapsed: 6.274585028s
Feb  4 15:29:09.540: INFO: Pod "pod-subpath-test-dynamicpv-fdf7": Phase="Running", Reason="", readiness=true. Elapsed: 8.347267641s
Feb  4 15:29:11.609: INFO: Pod "pod-subpath-test-dynamicpv-fdf7": Phase="Running", Reason="", readiness=true. Elapsed: 10.416734135s
... skipping 2 lines ...
Feb  4 15:29:17.816: INFO: Pod "pod-subpath-test-dynamicpv-fdf7": Phase="Running", Reason="", readiness=true. Elapsed: 16.623594445s
Feb  4 15:29:19.886: INFO: Pod "pod-subpath-test-dynamicpv-fdf7": Phase="Running", Reason="", readiness=true. Elapsed: 18.693960948s
Feb  4 15:29:21.955: INFO: Pod "pod-subpath-test-dynamicpv-fdf7": Phase="Running", Reason="", readiness=true. Elapsed: 20.762562363s
Feb  4 15:29:24.024: INFO: Pod "pod-subpath-test-dynamicpv-fdf7": Phase="Running", Reason="", readiness=true. Elapsed: 22.831356605s
Feb  4 15:29:26.092: INFO: Pod "pod-subpath-test-dynamicpv-fdf7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.899723835s
STEP: Saw pod success
Feb  4 15:29:26.092: INFO: Pod "pod-subpath-test-dynamicpv-fdf7" satisfied condition "Succeeded or Failed"
Feb  4 15:29:26.162: INFO: Trying to get logs from node ip-172-20-33-213.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-fdf7 container test-container-subpath-dynamicpv-fdf7: <nil>
STEP: delete the pod
Feb  4 15:29:26.314: INFO: Waiting for pod pod-subpath-test-dynamicpv-fdf7 to disappear
Feb  4 15:29:26.386: INFO: Pod pod-subpath-test-dynamicpv-fdf7 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-fdf7
Feb  4 15:29:26.386: INFO: Deleting pod "pod-subpath-test-dynamicpv-fdf7" in namespace "provisioning-1954"
... skipping 308 lines ...
Feb  4 15:29:33.101: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Feb  4 15:29:33.184: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.com26g2s] to have phase Bound
Feb  4 15:29:33.252: INFO: PersistentVolumeClaim efs.csi.aws.com26g2s found but phase is Pending instead of Bound.
Feb  4 15:29:35.320: INFO: PersistentVolumeClaim efs.csi.aws.com26g2s found and phase=Bound (2.13646504s)
STEP: Creating pod pod-subpath-test-dynamicpv-j9t6
STEP: Creating a pod to test subpath
Feb  4 15:29:35.526: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-j9t6" in namespace "provisioning-3142" to be "Succeeded or Failed"
Feb  4 15:29:35.595: INFO: Pod "pod-subpath-test-dynamicpv-j9t6": Phase="Pending", Reason="", readiness=false. Elapsed: 68.838646ms
Feb  4 15:29:37.664: INFO: Pod "pod-subpath-test-dynamicpv-j9t6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.137893197s
Feb  4 15:29:39.735: INFO: Pod "pod-subpath-test-dynamicpv-j9t6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.209631283s
STEP: Saw pod success
Feb  4 15:29:39.736: INFO: Pod "pod-subpath-test-dynamicpv-j9t6" satisfied condition "Succeeded or Failed"
Feb  4 15:29:39.803: INFO: Trying to get logs from node ip-172-20-104-189.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-j9t6 container test-container-volume-dynamicpv-j9t6: <nil>
STEP: delete the pod
Feb  4 15:29:39.949: INFO: Waiting for pod pod-subpath-test-dynamicpv-j9t6 to disappear
Feb  4 15:29:40.016: INFO: Pod pod-subpath-test-dynamicpv-j9t6 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-j9t6
Feb  4 15:29:40.016: INFO: Deleting pod "pod-subpath-test-dynamicpv-j9t6" in namespace "provisioning-3142"
... skipping 80 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath file is outside the volume [Slow][LinuxOnly] [BeforeEach]
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Driver efs.csi.aws.com doesn't support ntfs -- skipping

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 125 lines ...
Feb  4 15:29:43.516: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Feb  4 15:29:43.586: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.com72k2v] to have phase Bound
Feb  4 15:29:43.654: INFO: PersistentVolumeClaim efs.csi.aws.com72k2v found but phase is Pending instead of Bound.
Feb  4 15:29:45.726: INFO: PersistentVolumeClaim efs.csi.aws.com72k2v found and phase=Bound (2.140399393s)
STEP: Creating pod pod-subpath-test-dynamicpv-cntb
STEP: Creating a pod to test subpath
Feb  4 15:29:45.937: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-cntb" in namespace "provisioning-9150" to be "Succeeded or Failed"
Feb  4 15:29:46.006: INFO: Pod "pod-subpath-test-dynamicpv-cntb": Phase="Pending", Reason="", readiness=false. Elapsed: 68.619383ms
Feb  4 15:29:48.075: INFO: Pod "pod-subpath-test-dynamicpv-cntb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.137982523s
Feb  4 15:29:50.145: INFO: Pod "pod-subpath-test-dynamicpv-cntb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.207974038s
STEP: Saw pod success
Feb  4 15:29:50.145: INFO: Pod "pod-subpath-test-dynamicpv-cntb" satisfied condition "Succeeded or Failed"
Feb  4 15:29:50.214: INFO: Trying to get logs from node ip-172-20-104-189.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-cntb container test-container-subpath-dynamicpv-cntb: <nil>
STEP: delete the pod
Feb  4 15:29:50.359: INFO: Waiting for pod pod-subpath-test-dynamicpv-cntb to disappear
Feb  4 15:29:50.426: INFO: Pod pod-subpath-test-dynamicpv-cntb no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-cntb
Feb  4 15:29:50.426: INFO: Deleting pod "pod-subpath-test-dynamicpv-cntb" in namespace "provisioning-9150"
... skipping 188 lines ...

      Driver efs.csi.aws.com doesn't support Block -- skipping

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/provisioning.go:106
------------------------------
[efs-csi] EFS CSI [Driver: efs.csi.aws.com] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode 
  should fail to create pod by failing to mount volume [Slow]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:197

[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 6 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Feb  4 15:27:40.765: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-7412.k8s.local.kops.kubeconfig
STEP: Building a namespace api object, basename volumemode
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail to create pod by failing to mount volume [Slow]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:197
STEP: Creating sc
STEP: Creating pv and pvc
Feb  4 15:27:41.483: INFO: Waiting for PV pvp595f to bind to PVC pvc-pj2cm
Feb  4 15:27:41.483: INFO: Waiting up to timeout=3m0s for PersistentVolumeClaims [pvc-pj2cm] to have phase Bound
Feb  4 15:27:41.548: INFO: PersistentVolumeClaim pvc-pj2cm found and phase=Bound (64.748143ms)
... skipping 20 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227
    [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
    /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail to create pod by failing to mount volume [Slow]
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:197
------------------------------
[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 49 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath directory is outside the volume [Slow][LinuxOnly] [BeforeEach]
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Driver efs.csi.aws.com doesn't support ntfs -- skipping

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 109 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Feb  4 15:29:59.845: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-7412.k8s.local.kops.kubeconfig
STEP: Building a namespace api object, basename volumemode
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail to use a volume in a pod with mismatched mode [Slow]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:297
Feb  4 15:30:00.184: INFO: Driver "efs.csi.aws.com" does not provide raw block - skipping
[AfterEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Feb  4 15:30:00.185: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-6745" for this suite.
... skipping 7 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227
    [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
    /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail to use a volume in a pod with mismatched mode [Slow] [It]
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:297

      Driver "efs.csi.aws.com" does not provide raw block - skipping

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:113
------------------------------
... skipping 76 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Feb  4 15:30:01.364: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-7412.k8s.local.kops.kubeconfig
STEP: Building a namespace api object, basename volumemode
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail to use a volume in a pod with mismatched mode [Slow]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:297
Feb  4 15:30:01.824: INFO: Driver "efs.csi.aws.com" does not provide raw block - skipping
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Feb  4 15:30:01.825: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-6698" for this suite.
... skipping 7 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227
    [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
    /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail to use a volume in a pod with mismatched mode [Slow] [It]
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:297

      Driver "efs.csi.aws.com" does not provide raw block - skipping

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:113
------------------------------
... skipping 222 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227
    [Testpattern: Inline-volume (default fs)] subPath
    /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath file is outside the volume [Slow][LinuxOnly] [BeforeEach]
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Driver efs.csi.aws.com doesn't support InlineVolume -- skipping

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:116
------------------------------
... skipping 119 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227
    [Testpattern: Inline-volume (default fs)] subPath
    /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath directory is outside the volume [Slow][LinuxOnly] [BeforeEach]
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Driver efs.csi.aws.com doesn't support InlineVolume -- skipping

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:116
------------------------------
... skipping 69 lines ...
Feb  4 15:30:01.590: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Feb  4 15:30:01.689: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.comvg864] to have phase Bound
Feb  4 15:30:01.779: INFO: PersistentVolumeClaim efs.csi.aws.comvg864 found but phase is Pending instead of Bound.
Feb  4 15:30:03.847: INFO: PersistentVolumeClaim efs.csi.aws.comvg864 found and phase=Bound (2.157510551s)
STEP: Creating pod exec-volume-test-dynamicpv-7j8k
STEP: Creating a pod to test exec-volume-test
Feb  4 15:30:04.053: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-7j8k" in namespace "volume-9828" to be "Succeeded or Failed"
Feb  4 15:30:04.118: INFO: Pod "exec-volume-test-dynamicpv-7j8k": Phase="Pending", Reason="", readiness=false. Elapsed: 65.402248ms
Feb  4 15:30:06.184: INFO: Pod "exec-volume-test-dynamicpv-7j8k": Phase="Pending", Reason="", readiness=false. Elapsed: 2.131243802s
Feb  4 15:30:08.251: INFO: Pod "exec-volume-test-dynamicpv-7j8k": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.198111241s
STEP: Saw pod success
Feb  4 15:30:08.251: INFO: Pod "exec-volume-test-dynamicpv-7j8k" satisfied condition "Succeeded or Failed"
Feb  4 15:30:08.316: INFO: Trying to get logs from node ip-172-20-104-189.us-west-2.compute.internal pod exec-volume-test-dynamicpv-7j8k container exec-container-dynamicpv-7j8k: <nil>
STEP: delete the pod
Feb  4 15:30:08.459: INFO: Waiting for pod exec-volume-test-dynamicpv-7j8k to disappear
Feb  4 15:30:08.525: INFO: Pod exec-volume-test-dynamicpv-7j8k no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-7j8k
Feb  4 15:30:08.525: INFO: Deleting pod "exec-volume-test-dynamicpv-7j8k" in namespace "volume-9828"
... skipping 471 lines ...
STEP: Building a namespace api object, basename efs
STEP: Waiting for a default service account to be provisioned in namespace
[It] should mount without option tls when encryptInTransit set false
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:372
STEP: Creating efs pvc & pv
STEP: Creating pod to mount pvc "efs-1162" and run "mount && mount | grep /mnt/volume1 | grep fs-022d0bbb666889720"
Feb  4 15:30:10.408: INFO: Waiting up to 5m0s for pod "pvc-tester-kvbbj" in namespace "efs-1162" to be "Succeeded or Failed"
Feb  4 15:30:10.475: INFO: Pod "pvc-tester-kvbbj": Phase="Pending", Reason="", readiness=false. Elapsed: 67.064433ms
Feb  4 15:30:12.543: INFO: Pod "pvc-tester-kvbbj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.135084411s
Feb  4 15:30:14.611: INFO: Pod "pvc-tester-kvbbj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.203234312s
Feb  4 15:30:16.683: INFO: Pod "pvc-tester-kvbbj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.274437329s
Feb  4 15:30:18.753: INFO: Pod "pvc-tester-kvbbj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.345157905s
Feb  4 15:30:20.822: INFO: Pod "pvc-tester-kvbbj": Phase="Pending", Reason="", readiness=false. Elapsed: 10.413496507s
... skipping 4 lines ...
Feb  4 15:30:31.167: INFO: Pod "pvc-tester-kvbbj": Phase="Pending", Reason="", readiness=false. Elapsed: 20.758848135s
Feb  4 15:30:33.236: INFO: Pod "pvc-tester-kvbbj": Phase="Pending", Reason="", readiness=false. Elapsed: 22.82805489s
Feb  4 15:30:35.370: INFO: Pod "pvc-tester-kvbbj": Phase="Pending", Reason="", readiness=false. Elapsed: 24.962056799s
Feb  4 15:30:37.439: INFO: Pod "pvc-tester-kvbbj": Phase="Pending", Reason="", readiness=false. Elapsed: 27.030620735s
Feb  4 15:30:39.508: INFO: Pod "pvc-tester-kvbbj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 29.09970872s
STEP: Saw pod success
Feb  4 15:30:39.508: INFO: Pod "pvc-tester-kvbbj" satisfied condition "Succeeded or Failed"
Feb  4 15:30:39.578: INFO: pod "pvc-tester-kvbbj" logs:
 overlay on / type overlay (rw,relatime,lowerdir=/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/34/fs,upperdir=/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/113/fs,workdir=/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/113/work)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev type tmpfs (rw,nosuid,size=65536k,mode=755,inode64)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=666)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
... skipping 69 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227
    [Testpattern: Inline-volume (default fs)] subPath
    /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if non-existent subpath is outside the volume [Slow][LinuxOnly] [BeforeEach]
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Driver efs.csi.aws.com doesn't support InlineVolume -- skipping

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:116
------------------------------
... skipping 119 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly] [BeforeEach]
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:244
------------------------------
... skipping 86 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Feb  4 15:30:42.785: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-7412.k8s.local.kops.kubeconfig
STEP: Building a namespace api object, basename volumemode
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail to use a volume in a pod with mismatched mode [Slow]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:297
Feb  4 15:30:43.110: INFO: Driver "efs.csi.aws.com" does not provide raw block - skipping
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Feb  4 15:30:43.110: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-1297" for this suite.
... skipping 7 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227
    [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
    /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail to use a volume in a pod with mismatched mode [Slow] [It]
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:297

      Driver "efs.csi.aws.com" does not provide raw block - skipping

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:113
------------------------------
... skipping 277 lines ...
Feb  4 15:30:45.991: INFO: PersistentVolumeClaim pvc-s5ncn found but phase is Pending instead of Bound.
Feb  4 15:30:48.060: INFO: PersistentVolumeClaim pvc-s5ncn found and phase=Bound (6.273122355s)
Feb  4 15:30:48.060: INFO: Waiting up to 3m0s for PersistentVolume efs.csi.aws.com-sm494 to have phase Bound
Feb  4 15:30:48.128: INFO: PersistentVolume efs.csi.aws.com-sm494 found and phase=Bound (67.214215ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-gqkm
STEP: Creating a pod to test exec-volume-test
Feb  4 15:30:48.335: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-gqkm" in namespace "volume-8996" to be "Succeeded or Failed"
Feb  4 15:30:48.403: INFO: Pod "exec-volume-test-preprovisionedpv-gqkm": Phase="Pending", Reason="", readiness=false. Elapsed: 68.153942ms
Feb  4 15:30:50.470: INFO: Pod "exec-volume-test-preprovisionedpv-gqkm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.135947631s
Feb  4 15:30:52.540: INFO: Pod "exec-volume-test-preprovisionedpv-gqkm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.205681531s
Feb  4 15:30:54.609: INFO: Pod "exec-volume-test-preprovisionedpv-gqkm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.274837588s
Feb  4 15:30:56.677: INFO: Pod "exec-volume-test-preprovisionedpv-gqkm": Phase="Pending", Reason="", readiness=false. Elapsed: 8.342808221s
Feb  4 15:30:58.745: INFO: Pod "exec-volume-test-preprovisionedpv-gqkm": Phase="Pending", Reason="", readiness=false. Elapsed: 10.410790806s
Feb  4 15:31:00.816: INFO: Pod "exec-volume-test-preprovisionedpv-gqkm": Phase="Pending", Reason="", readiness=false. Elapsed: 12.481039239s
Feb  4 15:31:02.885: INFO: Pod "exec-volume-test-preprovisionedpv-gqkm": Phase="Pending", Reason="", readiness=false. Elapsed: 14.55014926s
Feb  4 15:31:04.953: INFO: Pod "exec-volume-test-preprovisionedpv-gqkm": Phase="Pending", Reason="", readiness=false. Elapsed: 16.618324825s
Feb  4 15:31:07.021: INFO: Pod "exec-volume-test-preprovisionedpv-gqkm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.686472859s
STEP: Saw pod success
Feb  4 15:31:07.021: INFO: Pod "exec-volume-test-preprovisionedpv-gqkm" satisfied condition "Succeeded or Failed"
Feb  4 15:31:07.090: INFO: Trying to get logs from node ip-172-20-104-189.us-west-2.compute.internal pod exec-volume-test-preprovisionedpv-gqkm container exec-container-preprovisionedpv-gqkm: <nil>
STEP: delete the pod
Feb  4 15:31:07.236: INFO: Waiting for pod exec-volume-test-preprovisionedpv-gqkm to disappear
Feb  4 15:31:07.303: INFO: Pod exec-volume-test-preprovisionedpv-gqkm no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-gqkm
Feb  4 15:31:07.304: INFO: Deleting pod "exec-volume-test-preprovisionedpv-gqkm" in namespace "volume-8996"
... skipping 356 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath directory is outside the volume [Slow][LinuxOnly] [BeforeEach]
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:244
------------------------------
... skipping 224 lines ...
Feb  4 15:31:09.703: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Feb  4 15:31:09.772: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.commmdzt] to have phase Bound
Feb  4 15:31:09.840: INFO: PersistentVolumeClaim efs.csi.aws.commmdzt found but phase is Pending instead of Bound.
Feb  4 15:31:11.909: INFO: PersistentVolumeClaim efs.csi.aws.commmdzt found and phase=Bound (2.136574375s)
STEP: Creating pod pod-subpath-test-dynamicpv-4c2q
STEP: Creating a pod to test subpath
Feb  4 15:31:12.113: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-4c2q" in namespace "provisioning-4637" to be "Succeeded or Failed"
Feb  4 15:31:12.180: INFO: Pod "pod-subpath-test-dynamicpv-4c2q": Phase="Pending", Reason="", readiness=false. Elapsed: 67.734431ms
Feb  4 15:31:14.249: INFO: Pod "pod-subpath-test-dynamicpv-4c2q": Phase="Pending", Reason="", readiness=false. Elapsed: 2.135828129s
Feb  4 15:31:16.318: INFO: Pod "pod-subpath-test-dynamicpv-4c2q": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.205245606s
STEP: Saw pod success
Feb  4 15:31:16.318: INFO: Pod "pod-subpath-test-dynamicpv-4c2q" satisfied condition "Succeeded or Failed"
Feb  4 15:31:16.386: INFO: Trying to get logs from node ip-172-20-104-189.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-4c2q container test-container-volume-dynamicpv-4c2q: <nil>
STEP: delete the pod
Feb  4 15:31:16.552: INFO: Waiting for pod pod-subpath-test-dynamicpv-4c2q to disappear
Feb  4 15:31:16.619: INFO: Pod pod-subpath-test-dynamicpv-4c2q no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-4c2q
Feb  4 15:31:16.619: INFO: Deleting pod "pod-subpath-test-dynamicpv-4c2q" in namespace "provisioning-4637"
... skipping 71 lines ...
STEP: Building a namespace api object, basename efs
STEP: Waiting for a default service account to be provisioned in namespace
[It] should mount with option tls when encryptInTransit unset
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:363
STEP: Creating efs pvc & pv
STEP: Creating pod to mount pvc "efs-3931" and run "mount && mount | grep /mnt/volume1 | grep 127.0.0.1"
Feb  4 15:31:14.406: INFO: Waiting up to 5m0s for pod "pvc-tester-ng7xr" in namespace "efs-3931" to be "Succeeded or Failed"
Feb  4 15:31:14.474: INFO: Pod "pvc-tester-ng7xr": Phase="Pending", Reason="", readiness=false. Elapsed: 67.743477ms
Feb  4 15:31:16.550: INFO: Pod "pvc-tester-ng7xr": Phase="Pending", Reason="", readiness=false. Elapsed: 2.143196536s
Feb  4 15:31:18.624: INFO: Pod "pvc-tester-ng7xr": Phase="Pending", Reason="", readiness=false. Elapsed: 4.217497731s
Feb  4 15:31:20.694: INFO: Pod "pvc-tester-ng7xr": Phase="Pending", Reason="", readiness=false. Elapsed: 6.287073944s
Feb  4 15:31:22.763: INFO: Pod "pvc-tester-ng7xr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.356211168s
STEP: Saw pod success
Feb  4 15:31:22.763: INFO: Pod "pvc-tester-ng7xr" satisfied condition "Succeeded or Failed"
Feb  4 15:31:22.832: INFO: pod "pvc-tester-ng7xr" logs:
 overlay on / type overlay (rw,relatime,lowerdir=/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/34/fs,upperdir=/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/131/fs,workdir=/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/131/work)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev type tmpfs (rw,nosuid,size=65536k,mode=755,inode64)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=666)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
... skipping 141 lines ...
Feb  4 15:31:24.211: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Feb  4 15:31:24.281: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.com88w2b] to have phase Bound
Feb  4 15:31:24.348: INFO: PersistentVolumeClaim efs.csi.aws.com88w2b found but phase is Pending instead of Bound.
Feb  4 15:31:26.416: INFO: PersistentVolumeClaim efs.csi.aws.com88w2b found and phase=Bound (2.135228058s)
STEP: Creating pod pod-subpath-test-dynamicpv-9kn2
STEP: Creating a pod to test subpath
Feb  4 15:31:26.623: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-9kn2" in namespace "provisioning-2869" to be "Succeeded or Failed"
Feb  4 15:31:26.710: INFO: Pod "pod-subpath-test-dynamicpv-9kn2": Phase="Pending", Reason="", readiness=false. Elapsed: 87.044327ms
Feb  4 15:31:28.779: INFO: Pod "pod-subpath-test-dynamicpv-9kn2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.155409341s
Feb  4 15:31:30.847: INFO: Pod "pod-subpath-test-dynamicpv-9kn2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.223742538s
STEP: Saw pod success
Feb  4 15:31:30.847: INFO: Pod "pod-subpath-test-dynamicpv-9kn2" satisfied condition "Succeeded or Failed"
Feb  4 15:31:30.915: INFO: Trying to get logs from node ip-172-20-104-189.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-9kn2 container test-container-subpath-dynamicpv-9kn2: <nil>
STEP: delete the pod
Feb  4 15:31:31.075: INFO: Waiting for pod pod-subpath-test-dynamicpv-9kn2 to disappear
Feb  4 15:31:31.147: INFO: Pod pod-subpath-test-dynamicpv-9kn2 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-9kn2
Feb  4 15:31:31.147: INFO: Deleting pod "pod-subpath-test-dynamicpv-9kn2" in namespace "provisioning-2869"
... skipping 221 lines ...

      Driver efs.csi.aws.com doesn't support Block -- skipping

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/multivolume.go:82
------------------------------
[efs-csi] EFS CSI [Driver: efs.csi.aws.com] [Testpattern: Dynamic PV (default fs)] subPath 
  should fail if non-existent subpath is outside the volume [Slow][LinuxOnly]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 6 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Feb  4 15:31:16.995: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-7412.k8s.local.kops.kubeconfig
STEP: Building a namespace api object, basename provisioning
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail if non-existent subpath is outside the volume [Slow][LinuxOnly]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Feb  4 15:31:17.524: INFO: Creating resource for dynamic PV
Feb  4 15:31:17.524: INFO: Using claimSize:1Mi, test suite supported size:{ 1Mi}, driver(efs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass 
STEP: creating a claim
Feb  4 15:31:17.590: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Feb  4 15:31:17.658: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.comfjpmk] to have phase Bound
Feb  4 15:31:17.725: INFO: PersistentVolumeClaim efs.csi.aws.comfjpmk found but phase is Pending instead of Bound.
Feb  4 15:31:19.793: INFO: PersistentVolumeClaim efs.csi.aws.comfjpmk found and phase=Bound (2.135318166s)
STEP: Creating pod pod-subpath-test-dynamicpv-plqq
STEP: Checking for subpath error in container status
Feb  4 15:31:24.125: INFO: Deleting pod "pod-subpath-test-dynamicpv-plqq" in namespace "provisioning-565"
Feb  4 15:31:24.191: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-plqq" to be fully deleted
STEP: Deleting pod
Feb  4 15:31:34.324: INFO: Deleting pod "pod-subpath-test-dynamicpv-plqq" in namespace "provisioning-565"
STEP: Deleting pvc
Feb  4 15:31:34.389: INFO: Deleting PersistentVolumeClaim "efs.csi.aws.comfjpmk"
... skipping 15 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227
    [Testpattern: Dynamic PV (default fs)] subPath
    /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if non-existent subpath is outside the volume [Slow][LinuxOnly]
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 82 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if non-existent subpath is outside the volume [Slow][LinuxOnly] [BeforeEach]
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Driver efs.csi.aws.com doesn't support ntfs -- skipping

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 334 lines ...
Feb  4 15:31:44.065: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Feb  4 15:31:44.135: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.comv26gf] to have phase Bound
Feb  4 15:31:44.202: INFO: PersistentVolumeClaim efs.csi.aws.comv26gf found but phase is Pending instead of Bound.
Feb  4 15:31:46.269: INFO: PersistentVolumeClaim efs.csi.aws.comv26gf found and phase=Bound (2.134456277s)
STEP: Creating pod pod-subpath-test-dynamicpv-nw2w
STEP: Creating a pod to test subpath
Feb  4 15:31:46.473: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-nw2w" in namespace "provisioning-8602" to be "Succeeded or Failed"
Feb  4 15:31:46.542: INFO: Pod "pod-subpath-test-dynamicpv-nw2w": Phase="Pending", Reason="", readiness=false. Elapsed: 68.84436ms
Feb  4 15:31:48.610: INFO: Pod "pod-subpath-test-dynamicpv-nw2w": Phase="Pending", Reason="", readiness=false. Elapsed: 2.136846624s
Feb  4 15:31:50.679: INFO: Pod "pod-subpath-test-dynamicpv-nw2w": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.205586076s
STEP: Saw pod success
Feb  4 15:31:50.679: INFO: Pod "pod-subpath-test-dynamicpv-nw2w" satisfied condition "Succeeded or Failed"
Feb  4 15:31:50.747: INFO: Trying to get logs from node ip-172-20-104-189.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-nw2w container test-container-subpath-dynamicpv-nw2w: <nil>
STEP: delete the pod
Feb  4 15:31:51.530: INFO: Waiting for pod pod-subpath-test-dynamicpv-nw2w to disappear
Feb  4 15:31:51.599: INFO: Pod pod-subpath-test-dynamicpv-nw2w no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-nw2w
Feb  4 15:31:51.599: INFO: Deleting pod "pod-subpath-test-dynamicpv-nw2w" in namespace "provisioning-8602"
STEP: Creating pod pod-subpath-test-dynamicpv-nw2w
STEP: Creating a pod to test subpath
Feb  4 15:31:51.735: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-nw2w" in namespace "provisioning-8602" to be "Succeeded or Failed"
Feb  4 15:31:51.803: INFO: Pod "pod-subpath-test-dynamicpv-nw2w": Phase="Pending", Reason="", readiness=false. Elapsed: 68.414235ms
Feb  4 15:31:53.872: INFO: Pod "pod-subpath-test-dynamicpv-nw2w": Phase="Pending", Reason="", readiness=false. Elapsed: 2.137304006s
Feb  4 15:31:55.941: INFO: Pod "pod-subpath-test-dynamicpv-nw2w": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.205542346s
STEP: Saw pod success
Feb  4 15:31:55.941: INFO: Pod "pod-subpath-test-dynamicpv-nw2w" satisfied condition "Succeeded or Failed"
Feb  4 15:31:56.008: INFO: Trying to get logs from node ip-172-20-104-189.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-nw2w container test-container-subpath-dynamicpv-nw2w: <nil>
STEP: delete the pod
Feb  4 15:31:56.151: INFO: Waiting for pod pod-subpath-test-dynamicpv-nw2w to disappear
Feb  4 15:31:56.218: INFO: Pod pod-subpath-test-dynamicpv-nw2w no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-nw2w
Feb  4 15:31:56.218: INFO: Deleting pod "pod-subpath-test-dynamicpv-nw2w" in namespace "provisioning-8602"
... skipping 268 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly] [BeforeEach]
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Driver efs.csi.aws.com doesn't support ntfs -- skipping

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 119 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227
    [Testpattern: Inline-volume (default fs)] subPath
    /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly] [BeforeEach]
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Driver efs.csi.aws.com doesn't support InlineVolume -- skipping

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:116
------------------------------
... skipping 160 lines ...

      Driver efs.csi.aws.com doesn't support InlineVolume -- skipping

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:116
------------------------------
[efs-csi] EFS CSI [Driver: efs.csi.aws.com] [Testpattern: Dynamic PV (default fs)] subPath 
  should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 6 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Feb  4 15:31:40.719: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-7412.k8s.local.kops.kubeconfig
STEP: Building a namespace api object, basename provisioning
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Feb  4 15:31:41.243: INFO: Creating resource for dynamic PV
Feb  4 15:31:41.243: INFO: Using claimSize:1Mi, test suite supported size:{ 1Mi}, driver(efs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass 
STEP: creating a claim
Feb  4 15:31:41.310: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Feb  4 15:31:41.377: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.comw5rsb] to have phase Bound
Feb  4 15:31:41.443: INFO: PersistentVolumeClaim efs.csi.aws.comw5rsb found but phase is Pending instead of Bound.
Feb  4 15:31:43.508: INFO: PersistentVolumeClaim efs.csi.aws.comw5rsb found and phase=Bound (2.13123012s)
STEP: Creating pod pod-subpath-test-dynamicpv-lxhx
STEP: Checking for subpath error in container status
Feb  4 15:31:47.837: INFO: Deleting pod "pod-subpath-test-dynamicpv-lxhx" in namespace "provisioning-5320"
Feb  4 15:31:47.915: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-lxhx" to be fully deleted
STEP: Deleting pod
Feb  4 15:31:58.046: INFO: Deleting pod "pod-subpath-test-dynamicpv-lxhx" in namespace "provisioning-5320"
STEP: Deleting pvc
Feb  4 15:31:58.111: INFO: Deleting PersistentVolumeClaim "efs.csi.aws.comw5rsb"
... skipping 15 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227
    [Testpattern: Dynamic PV (default fs)] subPath
    /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly]
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[efs-csi] EFS CSI [Driver: efs.csi.aws.com] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] 
  should access to two volumes with the same volume mode and retain data across pod recreation on the same node
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/multivolume.go:135

... skipping 135 lines ...
    [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
    /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should access to two volumes with the same volume mode and retain data across pod recreation on the same node
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/multivolume.go:135
------------------------------
[efs-csi] EFS CSI [Driver: efs.csi.aws.com] [Testpattern: Dynamic PV (block volmode)] volumeMode 
  should fail in binding dynamic provisioned PV to PVC [Slow][LinuxOnly]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:258

[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 6 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Feb  4 15:32:01.241: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-7412.k8s.local.kops.kubeconfig
STEP: Building a namespace api object, basename volumemode
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail in binding dynamic provisioned PV to PVC [Slow][LinuxOnly]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:258
STEP: Creating sc
STEP: Creating pv and pvc
Feb  4 15:37:02.130: INFO: Warning: did not get event about provisioing failed
STEP: Deleting pvc
Feb  4 15:37:02.266: INFO: Deleting PersistentVolumeClaim "pvc-8mfv7"
STEP: Deleting sc
[AfterEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Feb  4 15:37:02.404: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
... skipping 8 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227
    [Testpattern: Dynamic PV (block volmode)] volumeMode
    /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail in binding dynamic provisioned PV to PVC [Slow][LinuxOnly]
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:258
------------------------------
STEP: Deleting EFS filesystem "fs-022d0bbb666889720"
STEP: Deleted EFS filesystem "fs-022d0bbb666889720"



Summarizing 1 Failure:

[Fail] [efs-csi] EFS CSI [Driver: efs.csi.aws.com] [It] should create a directory with the correct permissions when in directory provisioning mode 
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:426

Ran 37 of 190 Specs in 747.760 seconds
FAIL! -- 36 Passed | 1 Failed | 0 Pending | 153 Skipped


Ginkgo ran 1 suite in 13m34.111443667s
Test Suite Failed
+ TEST_PASSED=1
+ set -e
+ set +x
###
## TEST_PASSED: 1
#
... skipping 1608 lines ...

Deleted cluster: "test-cluster-7412.k8s.local"
###
## OVERALL_TEST_PASSED: 1
#
###
## FAIL!
#
make: *** [Makefile:119: 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 ...