This job view page is being replaced by Spyglass soon. Check out the new job view.
PRjonathanrainer: Support ReadWriteOncePod
ResultABORTED
Tests 0 failed / 35 succeeded
Started2022-06-25 07:33
Elapsed39m53s
Revision0f8595ceee6590000681dc6b1e596e5d7699548d
Refs 714

No Test Failures!


Show 35 Passed Tests

Show 155 Skipped Tests

Error lines from build-log.txt

... skipping 244 lines ...
#9 2.852 --> Processing Dependency: libperl.so()(64bit) for package: 4:perl-5.16.3-299.amzn2.0.1.x86_64
#9 2.853 ---> Package perl-File-Temp.noarch 0:0.23.01-3.amzn2 will be installed
#9 2.855 ---> Package perl-Getopt-Long.noarch 0:2.40-3.amzn2 will be installed
#9 2.856 --> Processing Dependency: perl(Pod::Usage) >= 1.14 for package: perl-Getopt-Long-2.40-3.amzn2.noarch
#9 2.857 --> Processing Dependency: perl(Text::ParseWords) for package: perl-Getopt-Long-2.40-3.amzn2.noarch
#9 2.858 ---> Package perl-Git.noarch 0:2.32.0-1.amzn2.0.1 will be installed
#9 2.860 --> Processing Dependency: perl(Error) for package: perl-Git-2.32.0-1.amzn2.0.1.noarch
#9 2.861 ---> Package perl-PathTools.x86_64 0:3.40-5.amzn2.0.2 will be installed
#9 2.862 ---> Package perl-TermReadKey.x86_64 0:2.30-20.amzn2.0.2 will be installed
#9 2.864 ---> Package perl-Thread-Queue.noarch 0:3.02-2.amzn2 will be installed
#9 2.864 ---> Package perl-threads.x86_64 0:1.87-4.amzn2.0.2 will be installed
#9 2.866 ---> Package pkgconfig.x86_64 1:0.27.1-4.amzn2.0.2 will be installed
#9 2.869 ---> Package system-rpm-config.noarch 0:9.1.0-76.amzn2.0.14 will be installed
... skipping 15 lines ...
#9 2.934 --> Processing Dependency: openssh = 7.4p1-22.amzn2.0.1 for package: openssh-clients-7.4p1-22.amzn2.0.1.x86_64
#9 2.935 --> Processing Dependency: fipscheck-lib(x86-64) >= 1.3.0 for package: openssh-clients-7.4p1-22.amzn2.0.1.x86_64
#9 2.937 --> Processing Dependency: libfipscheck.so.1()(64bit) for package: openssh-clients-7.4p1-22.amzn2.0.1.x86_64
#9 2.937 --> Processing Dependency: libedit.so.0()(64bit) for package: openssh-clients-7.4p1-22.amzn2.0.1.x86_64
#9 2.939 ---> Package pcre2.x86_64 0:10.23-2.amzn2.0.2 will be installed
#9 2.941 ---> Package perl-Carp.noarch 0:1.26-244.amzn2 will be installed
#9 2.941 ---> Package perl-Error.noarch 1:0.17020-2.amzn2 will be installed
#9 2.942 ---> Package perl-Exporter.noarch 0:5.68-3.amzn2 will be installed
#9 2.943 ---> Package perl-File-Path.noarch 0:2.09-2.amzn2 will be installed
#9 2.944 ---> Package perl-Filter.x86_64 0:1.49-3.amzn2.0.2 will be installed
#9 2.945 ---> Package perl-Pod-Simple.noarch 1:3.28-4.amzn2 will be installed
#9 2.948 --> Processing Dependency: perl(Pod::Escapes) >= 1.04 for package: 1:perl-Pod-Simple-3.28-4.amzn2.noarch
#9 2.950 --> Processing Dependency: perl(Encode) for package: 1:perl-Pod-Simple-3.28-4.amzn2.noarch
... skipping 169 lines ...
#9 3.364  pam                       x86_64 1.1.8-23.amzn2.0.1           amzn2-core 715 k
#9 3.364  patch                     x86_64 2.7.1-12.amzn2.0.2           amzn2-core 110 k
#9 3.364  pcre2                     x86_64 10.23-2.amzn2.0.2            amzn2-core 209 k
#9 3.364  perl                      x86_64 4:5.16.3-299.amzn2.0.1       amzn2-core 8.0 M
#9 3.364  perl-Carp                 noarch 1.26-244.amzn2               amzn2-core  19 k
#9 3.364  perl-Encode               x86_64 2.51-7.amzn2.0.2             amzn2-core 1.5 M
#9 3.364  perl-Error                noarch 1:0.17020-2.amzn2            amzn2-core  32 k
#9 3.364  perl-Exporter             noarch 5.68-3.amzn2                 amzn2-core  29 k
#9 3.364  perl-File-Path            noarch 2.09-2.amzn2                 amzn2-core  27 k
#9 3.364  perl-File-Temp            noarch 0.23.01-3.amzn2              amzn2-core  56 k
#9 3.364  perl-Filter               x86_64 1.49-3.amzn2.0.2             amzn2-core  76 k
#9 3.364  perl-Getopt-Long          noarch 2.40-3.amzn2                 amzn2-core  56 k
#9 3.364  perl-Git                  noarch 2.32.0-1.amzn2.0.1           amzn2-core  43 k
... skipping 88 lines ...
#9 8.786   Installing : 1:perl-Pod-Simple-3.28-4.amzn2.noarch                      34/88 
#9 8.824   Installing : perl-Getopt-Long-2.40-3.amzn2.noarch                       35/88 
#9 8.959   Installing : 4:perl-libs-5.16.3-299.amzn2.0.1.x86_64                    36/88 
#9 10.59   Installing : 4:perl-5.16.3-299.amzn2.0.1.x86_64                         37/88 
#9 10.67   Installing : perl-Thread-Queue-3.02-2.amzn2.noarch                      38/88 
#9 10.69   Installing : perl-TermReadKey-2.30-20.amzn2.0.2.x86_64                  39/88 
#9 10.72   Installing : 1:perl-Error-0.17020-2.amzn2.noarch                        40/88 
#9 10.75   Installing : fipscheck-lib-1.4.1-6.amzn2.0.2.x86_64                     41/88 
#9 10.79   Installing : fipscheck-1.4.1-6.amzn2.0.2.x86_64                         42/88 
#9 10.83   Installing : dwz-0.11-3.amzn2.0.3.x86_64                                43/88 
#9 10.86   Installing : 1:pkgconfig-0.27.1-4.amzn2.0.2.x86_64                      44/88 
#9 10.92   Installing : pcre2-10.23-2.amzn2.0.2.x86_64                             45/88 
#9 10.97   Installing : libsmartcols-2.30.2-2.amzn2.0.7.x86_64                     46/88 
... skipping 33 lines ...
#0 0.461 CGO_ENABLED=0 GOOS=linux GOARCH=amd64 go build -mod=vendor -ldflags "-X github.com/kubernetes-sigs/aws-efs-csi-driver/pkg/driver.driverVersion=v1.4.0 -X github.com/kubernetes-sigs/aws-efs-csi-driver/pkg/driver.gitCommit=c96d8c163a30dc968bd69d460d3cf7cab586c7e6 -X github.com/kubernetes-sigs/aws-efs-csi-driver/pkg/driver.buildDate=2022-06-25T07:34:47Z -X github.com/kubernetes-sigs/aws-efs-csi-driver/pkg/driver.efsClientSource=k8s" -o bin/aws-efs-csi-driver ./cmd/
#14 ...

#9 [linux-amazon 3/7] RUN if [ "github" = "yum" ];     then echo "Installing efs-utils from Amazon Linux 2 yum repo" &&          yum -y install amazon-efs-utils-1.31.1-1.amzn2.noarch;     else echo "Installing efs-utils from github using the latest git tag" &&          yum -y install git rpm-build make &&          git clone https://github.com/aws/efs-utils &&          cd efs-utils &&          git checkout $(git describe --tags $(git rev-list --tags --max-count=1)) &&          make rpm && yum -y install build/amazon-efs-utils*rpm &&          cd .. && rm -rf efs-utils &&          yum clean all;     fi
#9 15.55   Installing : 1:dbus-libs-1.10.24-7.amzn2.x86_64                         76/88 
#9 16.97   Installing : systemd-219-78.amzn2.0.18.x86_64                           77/88 
#9 17.45 Failed to get D-Bus connection: Operation not permitted
#9 17.47   Installing : elfutils-default-yama-scope-0.176-2.amzn2.noarch           78/88 
#9 17.62   Installing : 1:dbus-1.10.24-7.amzn2.x86_64                              79/88 
#9 17.70   Installing : elfutils-0.176-2.amzn2.x86_64                              80/88 
#9 17.87   Installing : openssh-7.4p1-22.amzn2.0.1.x86_64                          81/88 
#9 18.03   Installing : openssh-clients-7.4p1-22.amzn2.0.1.x86_64                  82/88 
#9 19.23   Installing : git-core-2.32.0-1.amzn2.0.1.x86_64                         83/88 
... skipping 55 lines ...
#9 21.07   Verifying  : perl-File-Temp-0.23.01-3.amzn2.noarch                      51/88 
#9 21.08   Verifying  : perl-srpm-macros-1-8.amzn2.0.1.noarch                      52/88 
#9 21.09   Verifying  : pam-1.1.8-23.amzn2.0.1.x86_64                              53/88 
#9 21.11   Verifying  : xz-5.2.2-1.amzn2.0.3.x86_64                                54/88 
#9 21.12   Verifying  : ustr-1.0.4-16.amzn2.0.3.x86_64                             55/88 
#9 21.13   Verifying  : less-458-9.amzn2.0.2.x86_64                                56/88 
#9 21.15   Verifying  : 1:perl-Error-0.17020-2.amzn2.noarch                        57/88 
#9 21.17   Verifying  : perl-Pod-Usage-1.63-3.amzn2.noarch                         58/88 
#9 21.17   Verifying  : unzip-6.0-43.amzn2.x86_64                                  59/88 
#9 21.19   Verifying  : 1:perl-parent-0.225-244.amzn2.0.1.noarch                   60/88 
#9 21.20   Verifying  : perl-Pod-Perldoc-3.20-4.amzn2.noarch                       61/88 
#9 21.21   Verifying  : 2:tar-1.26-35.amzn2.x86_64                                 62/88 
#9 21.23   Verifying  : zip-3.0-11.amzn2.0.2.x86_64                                63/88 
... skipping 69 lines ...
#9 21.63   pam.x86_64 0:1.1.8-23.amzn2.0.1                                               
#9 21.63   patch.x86_64 0:2.7.1-12.amzn2.0.2                                             
#9 21.63   pcre2.x86_64 0:10.23-2.amzn2.0.2                                              
#9 21.63   perl.x86_64 4:5.16.3-299.amzn2.0.1                                            
#9 21.63   perl-Carp.noarch 0:1.26-244.amzn2                                             
#9 21.63   perl-Encode.x86_64 0:2.51-7.amzn2.0.2                                         
#9 21.63   perl-Error.noarch 1:0.17020-2.amzn2                                           
#9 21.63   perl-Exporter.noarch 0:5.68-3.amzn2                                           
#9 21.63   perl-File-Path.noarch 0:2.09-2.amzn2                                          
#9 21.63   perl-File-Temp.noarch 0:0.23.01-3.amzn2                                       
#9 21.63   perl-Filter.x86_64 0:1.49-3.amzn2.0.2                                         
#9 21.63   perl-Getopt-Long.noarch 0:2.40-3.amzn2                                        
#9 21.63   perl-Git.noarch 0:2.32.0-1.amzn2.0.1                                          
... skipping 560 lines ...
|  . o   S .      |
|   o ... . .     |
|  .o+o.o. .      |
| . +***=..       |
|  ..=BE+.        |
+----[SHA256]-----+
Error: unable to describe control plane "test-cluster-15138-k8s-local": operation error EKS: DescribeCluster, https response error StatusCode: 404, RequestID: a80407d2-efb7-496f-9f6e-cd6fd907828c, ResourceNotFoundException: No cluster found for name: test-cluster-15138-k8s-local.
###
## Creating cluster test-cluster-15138-k8s-local with /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-15138.k8s.local.eksctl.yaml (dry run)
#
###
## Patching cluster test-cluster-15138-k8s-local with ./hack/eksctl-patch.yaml
#
... skipping 128 lines ...
Random Seed: 1656143635 - Will randomize all specs
Will run 190 specs

Running in parallel across 4 nodes

STEP: Creating EFS filesystem in region "us-west-2" for cluster "test-cluster-15138-k8s-local"
error getting kops node security group id: no security groups found with filters [{
    Name: "tag:Name",
    Values: ["nodes.test-cluster-15138-k8s-local"]
  }]
error getting kops node subnet ids: no subnets found with filters [{
    Name: "tag-key",
    Values: ["kubernetes.io/cluster/test-cluster-15138-k8s-local"]
  }]
STEP: Created EFS filesystem "fs-0daad606ce96cef4c" in region "us-west-2" for cluster "test-cluster-15138-k8s-local"


... skipping 129 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:228
    [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 281 lines ...
Jun 25 07:56:41.932: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jun 25 07:56:42.003: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.comcwrrd] to have phase Bound
Jun 25 07:56:42.067: INFO: PersistentVolumeClaim efs.csi.aws.comcwrrd found but phase is Pending instead of Bound.
Jun 25 07:56:44.134: INFO: PersistentVolumeClaim efs.csi.aws.comcwrrd found and phase=Bound (2.131330576s)
STEP: Creating pod pod-subpath-test-dynamicpv-qs76
STEP: Creating a pod to test subpath
Jun 25 07:56:44.392: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-qs76" in namespace "provisioning-5089" to be "Succeeded or Failed"
Jun 25 07:56:44.473: INFO: Pod "pod-subpath-test-dynamicpv-qs76": Phase="Pending", Reason="", readiness=false. Elapsed: 81.354798ms
Jun 25 07:56:46.539: INFO: Pod "pod-subpath-test-dynamicpv-qs76": Phase="Pending", Reason="", readiness=false. Elapsed: 2.147415172s
Jun 25 07:56:48.606: INFO: Pod "pod-subpath-test-dynamicpv-qs76": Phase="Pending", Reason="", readiness=false. Elapsed: 4.213502983s
Jun 25 07:56:50.672: INFO: Pod "pod-subpath-test-dynamicpv-qs76": Phase="Pending", Reason="", readiness=false. Elapsed: 6.28034652s
Jun 25 07:56:52.738: INFO: Pod "pod-subpath-test-dynamicpv-qs76": Phase="Pending", Reason="", readiness=false. Elapsed: 8.346123126s
Jun 25 07:56:54.841: INFO: Pod "pod-subpath-test-dynamicpv-qs76": Phase="Pending", Reason="", readiness=false. Elapsed: 10.448687997s
Jun 25 07:56:56.909: INFO: Pod "pod-subpath-test-dynamicpv-qs76": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.517269466s
STEP: Saw pod success
Jun 25 07:56:56.909: INFO: Pod "pod-subpath-test-dynamicpv-qs76" satisfied condition "Succeeded or Failed"
Jun 25 07:56:56.976: INFO: Trying to get logs from node ip-192-168-0-215.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-qs76 container test-container-volume-dynamicpv-qs76: <nil>
STEP: delete the pod
Jun 25 07:56:57.125: INFO: Waiting for pod pod-subpath-test-dynamicpv-qs76 to disappear
Jun 25 07:56:57.191: INFO: Pod pod-subpath-test-dynamicpv-qs76 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-qs76
Jun 25 07:56:57.191: INFO: Deleting pod "pod-subpath-test-dynamicpv-qs76" in namespace "provisioning-5089"
... skipping 45 lines ...
STEP: Binding the e2e-test-privileged-psp PodSecurityPolicy to the default service account in efs-7887
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:364
STEP: Creating efs pvc & pv
STEP: Creating pod to mount pvc "efs-7887" and run "mount && mount | grep /mnt/volume1 | grep 127.0.0.1"
Jun 25 07:56:36.134: INFO: Waiting up to 5m0s for pod "pvc-tester-r8nd5" in namespace "efs-7887" to be "Succeeded or Failed"
Jun 25 07:56:36.199: INFO: Pod "pvc-tester-r8nd5": Phase="Pending", Reason="", readiness=false. Elapsed: 64.942777ms
Jun 25 07:56:38.264: INFO: Pod "pvc-tester-r8nd5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.130282266s
Jun 25 07:56:40.331: INFO: Pod "pvc-tester-r8nd5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.197024652s
Jun 25 07:56:42.396: INFO: Pod "pvc-tester-r8nd5": Phase="Pending", Reason="", readiness=false. Elapsed: 6.262173546s
Jun 25 07:56:44.461: INFO: Pod "pvc-tester-r8nd5": Phase="Pending", Reason="", readiness=false. Elapsed: 8.327520512s
Jun 25 07:56:46.528: INFO: Pod "pvc-tester-r8nd5": Phase="Pending", Reason="", readiness=false. Elapsed: 10.393934747s
... skipping 3 lines ...
Jun 25 07:56:54.798: INFO: Pod "pvc-tester-r8nd5": Phase="Pending", Reason="", readiness=false. Elapsed: 18.664848091s
Jun 25 07:56:56.866: INFO: Pod "pvc-tester-r8nd5": Phase="Pending", Reason="", readiness=false. Elapsed: 20.732677272s
Jun 25 07:56:58.933: INFO: Pod "pvc-tester-r8nd5": Phase="Pending", Reason="", readiness=false. Elapsed: 22.799718878s
Jun 25 07:57:01.000: INFO: Pod "pvc-tester-r8nd5": Phase="Pending", Reason="", readiness=false. Elapsed: 24.865941141s
Jun 25 07:57:03.065: INFO: Pod "pvc-tester-r8nd5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.931307112s
STEP: Saw pod success
Jun 25 07:57:03.065: INFO: Pod "pvc-tester-r8nd5" satisfied condition "Succeeded or Failed"
Jun 25 07:57:03.137: INFO: pod "pvc-tester-r8nd5" logs:
 overlay on / type overlay (rw,relatime,lowerdir=/var/lib/docker/overlay2/l/TMZ27OL6BZ45YA5DDHLANBD344:/var/lib/docker/overlay2/l/4CDBHM4D6SVYEAPGGF2EY3TEDG,upperdir=/var/lib/docker/overlay2/ac5ea88089cd6e74ce24d8d3e4d98a5756bef537bb6964730960b9a4b7bb2168/diff,workdir=/var/lib/docker/overlay2/ac5ea88089cd6e74ce24d8d3e4d98a5756bef537bb6964730960b9a4b7bb2168/work)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev type tmpfs (rw,nosuid,size=65536k,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=666)
sysfs on /sys type sysfs (ro,nosuid,nodev,noexec,relatime)
... skipping 556 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:228
    [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 181 lines ...
STEP: Binding the e2e-test-privileged-psp PodSecurityPolicy to the default service account in efs-1445
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:235
STEP: Creating efs pvc & pv with no subpath
STEP: Creating pod to make subpaths /a and /b
Jun 25 07:56:41.096: INFO: Waiting up to 5m0s for pod "pvc-tester-zfm6b" in namespace "efs-1445" to be "Succeeded or Failed"
Jun 25 07:56:41.160: INFO: Pod "pvc-tester-zfm6b": Phase="Pending", Reason="", readiness=false. Elapsed: 63.872062ms
Jun 25 07:56:43.225: INFO: Pod "pvc-tester-zfm6b": Phase="Pending", Reason="", readiness=false. Elapsed: 2.128627278s
Jun 25 07:56:45.289: INFO: Pod "pvc-tester-zfm6b": Phase="Pending", Reason="", readiness=false. Elapsed: 4.1924539s
Jun 25 07:56:47.354: INFO: Pod "pvc-tester-zfm6b": Phase="Pending", Reason="", readiness=false. Elapsed: 6.257271055s
Jun 25 07:56:49.420: INFO: Pod "pvc-tester-zfm6b": Phase="Pending", Reason="", readiness=false. Elapsed: 8.323682124s
Jun 25 07:56:51.486: INFO: Pod "pvc-tester-zfm6b": Phase="Pending", Reason="", readiness=false. Elapsed: 10.389246817s
... skipping 6 lines ...
Jun 25 07:57:05.943: INFO: Pod "pvc-tester-zfm6b": Phase="Pending", Reason="", readiness=false. Elapsed: 24.846051083s
Jun 25 07:57:08.009: INFO: Pod "pvc-tester-zfm6b": Phase="Pending", Reason="", readiness=false. Elapsed: 26.912628484s
Jun 25 07:57:10.071: INFO: Pod "pvc-tester-zfm6b": Phase="Pending", Reason="", readiness=false. Elapsed: 28.974900633s
Jun 25 07:57:12.136: INFO: Pod "pvc-tester-zfm6b": Phase="Pending", Reason="", readiness=false. Elapsed: 31.039747205s
Jun 25 07:57:14.201: INFO: Pod "pvc-tester-zfm6b": Phase="Succeeded", Reason="", readiness=false. Elapsed: 33.104191527s
STEP: Saw pod success
Jun 25 07:57:14.201: INFO: Pod "pvc-tester-zfm6b" 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
Jun 25 07:57:26.893: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
... skipping 73 lines ...
Jun 25 07:57:13.372: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jun 25 07:57:13.446: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.comjfchf] to have phase Bound
Jun 25 07:57:13.515: INFO: PersistentVolumeClaim efs.csi.aws.comjfchf found but phase is Pending instead of Bound.
Jun 25 07:57:15.581: INFO: PersistentVolumeClaim efs.csi.aws.comjfchf found and phase=Bound (2.135538732s)
STEP: Creating pod pod-subpath-test-dynamicpv-7gd2
STEP: Creating a pod to test subpath
Jun 25 07:57:15.787: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-7gd2" in namespace "provisioning-9703" to be "Succeeded or Failed"
Jun 25 07:57:15.892: INFO: Pod "pod-subpath-test-dynamicpv-7gd2": Phase="Pending", Reason="", readiness=false. Elapsed: 104.383488ms
Jun 25 07:57:17.957: INFO: Pod "pod-subpath-test-dynamicpv-7gd2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.169170718s
Jun 25 07:57:20.024: INFO: Pod "pod-subpath-test-dynamicpv-7gd2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.236630413s
Jun 25 07:57:22.090: INFO: Pod "pod-subpath-test-dynamicpv-7gd2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.302186413s
STEP: Saw pod success
Jun 25 07:57:22.090: INFO: Pod "pod-subpath-test-dynamicpv-7gd2" satisfied condition "Succeeded or Failed"
Jun 25 07:57:22.156: INFO: Trying to get logs from node ip-192-168-0-215.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-7gd2 container test-container-subpath-dynamicpv-7gd2: <nil>
STEP: delete the pod
Jun 25 07:57:22.372: INFO: Waiting for pod pod-subpath-test-dynamicpv-7gd2 to disappear
Jun 25 07:57:22.439: INFO: Pod pod-subpath-test-dynamicpv-7gd2 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-7gd2
Jun 25 07:57:22.439: INFO: Deleting pod "pod-subpath-test-dynamicpv-7gd2" in namespace "provisioning-9703"
... skipping 155 lines ...
Jun 25 07:57:30.502: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jun 25 07:57:30.573: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.comn6vgc] to have phase Bound
Jun 25 07:57:30.640: INFO: PersistentVolumeClaim efs.csi.aws.comn6vgc found but phase is Pending instead of Bound.
Jun 25 07:57:32.707: INFO: PersistentVolumeClaim efs.csi.aws.comn6vgc found and phase=Bound (2.133531199s)
STEP: Creating pod pod-subpath-test-dynamicpv-pmzl
STEP: Creating a pod to test multi_subpath
Jun 25 07:57:32.956: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-pmzl" in namespace "provisioning-4783" to be "Succeeded or Failed"
Jun 25 07:57:33.020: INFO: Pod "pod-subpath-test-dynamicpv-pmzl": Phase="Pending", Reason="", readiness=false. Elapsed: 64.620875ms
Jun 25 07:57:35.087: INFO: Pod "pod-subpath-test-dynamicpv-pmzl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.130955814s
Jun 25 07:57:37.152: INFO: Pod "pod-subpath-test-dynamicpv-pmzl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.196259532s
Jun 25 07:57:39.219: INFO: Pod "pod-subpath-test-dynamicpv-pmzl": Phase="Pending", Reason="", readiness=false. Elapsed: 6.263265063s
Jun 25 07:57:41.284: INFO: Pod "pod-subpath-test-dynamicpv-pmzl": Phase="Pending", Reason="", readiness=false. Elapsed: 8.328488304s
Jun 25 07:57:43.351: INFO: Pod "pod-subpath-test-dynamicpv-pmzl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.395373484s
STEP: Saw pod success
Jun 25 07:57:43.351: INFO: Pod "pod-subpath-test-dynamicpv-pmzl" satisfied condition "Succeeded or Failed"
Jun 25 07:57:43.415: INFO: Trying to get logs from node ip-192-168-45-111.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-pmzl container test-container-subpath-dynamicpv-pmzl: <nil>
STEP: delete the pod
Jun 25 07:57:43.659: INFO: Waiting for pod pod-subpath-test-dynamicpv-pmzl to disappear
Jun 25 07:57:43.726: INFO: Pod pod-subpath-test-dynamicpv-pmzl no longer exists
STEP: Deleting pod
Jun 25 07:57:43.726: INFO: Deleting pod "pod-subpath-test-dynamicpv-pmzl" in namespace "provisioning-4783"
... skipping 47 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:228
    [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 63 lines ...
STEP: creating a claim
Jun 25 07:57:33.878: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jun 25 07:57:33.950: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.comktbvl] to have phase Bound
Jun 25 07:57:34.014: INFO: PersistentVolumeClaim efs.csi.aws.comktbvl found but phase is Pending instead of Bound.
Jun 25 07:57:36.081: INFO: PersistentVolumeClaim efs.csi.aws.comktbvl found and phase=Bound (2.130103756s)
STEP: Creating pod to format volume volume-prep-provisioning-4324
Jun 25 07:57:36.282: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-4324" in namespace "provisioning-4324" to be "Succeeded or Failed"
Jun 25 07:57:36.345: INFO: Pod "volume-prep-provisioning-4324": Phase="Pending", Reason="", readiness=false. Elapsed: 63.013307ms
Jun 25 07:57:38.410: INFO: Pod "volume-prep-provisioning-4324": Phase="Pending", Reason="", readiness=false. Elapsed: 2.127947994s
Jun 25 07:57:40.475: INFO: Pod "volume-prep-provisioning-4324": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.193108176s
STEP: Saw pod success
Jun 25 07:57:40.475: INFO: Pod "volume-prep-provisioning-4324" satisfied condition "Succeeded or Failed"
Jun 25 07:57:40.475: INFO: Deleting pod "volume-prep-provisioning-4324" in namespace "provisioning-4324"
Jun 25 07:57:40.554: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-4324" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-db9g
STEP: Checking for subpath error in container status
Jun 25 07:57:44.821: INFO: Deleting pod "pod-subpath-test-dynamicpv-db9g" in namespace "provisioning-4324"
Jun 25 07:57:44.892: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-db9g" to be fully deleted
STEP: Deleting pod
Jun 25 07:57:47.026: INFO: Deleting pod "pod-subpath-test-dynamicpv-db9g" in namespace "provisioning-4324"
STEP: Deleting pvc
Jun 25 07:57:47.090: INFO: Deleting PersistentVolumeClaim "efs.csi.aws.comktbvl"
... skipping 296 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:228
    [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 66 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:228
    [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 623 lines ...

      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
------------------------------
[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:221
[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 8 lines ...
  /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
Jun 25 07:58:01.692: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-15138.k8s.local.eksctl.kubeconfig
STEP: Building a namespace api object, basename provisioning
STEP: Binding the e2e-test-privileged-psp PodSecurityPolicy to the default service account in provisioning-2546
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
Jun 25 07:58:02.830: INFO: Creating resource for dynamic PV
Jun 25 07:58:02.830: 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
Jun 25 07:58:03.024: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jun 25 07:58:03.103: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.com4jqp9] to have phase Bound
Jun 25 07:58:03.166: INFO: PersistentVolumeClaim efs.csi.aws.com4jqp9 found but phase is Pending instead of Bound.
Jun 25 07:58:05.244: INFO: PersistentVolumeClaim efs.csi.aws.com4jqp9 found and phase=Bound (2.141756992s)
STEP: Creating pod pod-subpath-test-dynamicpv-z4tq
STEP: Checking for subpath error in container status
Jun 25 07:58:09.581: INFO: Deleting pod "pod-subpath-test-dynamicpv-z4tq" in namespace "provisioning-2546"
Jun 25 07:58:09.652: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-z4tq" to be fully deleted
STEP: Deleting pod
Jun 25 07:58:11.785: INFO: Deleting pod "pod-subpath-test-dynamicpv-z4tq" in namespace "provisioning-2546"
STEP: Deleting pvc
Jun 25 07:58:11.857: INFO: Deleting PersistentVolumeClaim "efs.csi.aws.com4jqp9"
... skipping 15 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:228
    [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
------------------------------
[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:221
[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 59 lines ...

      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
------------------------------
[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:221
[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 8 lines ...
  /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
Jun 25 07:58:18.490: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-15138.k8s.local.eksctl.kubeconfig
STEP: Building a namespace api object, basename provisioning
STEP: Binding the e2e-test-privileged-psp PodSecurityPolicy to the default service account in provisioning-1515
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
Jun 25 07:58:19.637: INFO: Creating resource for dynamic PV
Jun 25 07:58:19.637: 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
Jun 25 07:58:19.842: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jun 25 07:58:19.918: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.com92gzs] to have phase Bound
Jun 25 07:58:19.987: INFO: PersistentVolumeClaim efs.csi.aws.com92gzs found but phase is Pending instead of Bound.
Jun 25 07:58:22.056: INFO: PersistentVolumeClaim efs.csi.aws.com92gzs found and phase=Bound (2.138034526s)
STEP: Creating pod pod-subpath-test-dynamicpv-jpw2
STEP: Checking for subpath error in container status
Jun 25 07:58:26.409: INFO: Deleting pod "pod-subpath-test-dynamicpv-jpw2" in namespace "provisioning-1515"
Jun 25 07:58:26.485: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-jpw2" to be fully deleted
STEP: Deleting pod
Jun 25 07:58:28.635: INFO: Deleting pod "pod-subpath-test-dynamicpv-jpw2" in namespace "provisioning-1515"
STEP: Deleting pvc
Jun 25 07:58:28.704: INFO: Deleting PersistentVolumeClaim "efs.csi.aws.com92gzs"
... skipping 15 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:228
    [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
------------------------------
[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:221
[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 58 lines ...
Jun 25 07:58:01.233: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jun 25 07:58:01.305: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.comzvg5b] to have phase Bound
Jun 25 07:58:01.369: INFO: PersistentVolumeClaim efs.csi.aws.comzvg5b found but phase is Pending instead of Bound.
Jun 25 07:58:03.434: INFO: PersistentVolumeClaim efs.csi.aws.comzvg5b found and phase=Bound (2.12924612s)
STEP: Creating pod pod-subpath-test-dynamicpv-gpj4
STEP: Creating a pod to test atomic-volume-subpath
Jun 25 07:58:03.684: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-gpj4" in namespace "provisioning-9271" to be "Succeeded or Failed"
Jun 25 07:58:03.747: INFO: Pod "pod-subpath-test-dynamicpv-gpj4": Phase="Pending", Reason="", readiness=false. Elapsed: 63.007922ms
Jun 25 07:58:05.813: INFO: Pod "pod-subpath-test-dynamicpv-gpj4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.128383193s
Jun 25 07:58:07.878: INFO: Pod "pod-subpath-test-dynamicpv-gpj4": Phase="Running", Reason="", readiness=true. Elapsed: 4.193416251s
Jun 25 07:58:09.944: INFO: Pod "pod-subpath-test-dynamicpv-gpj4": Phase="Running", Reason="", readiness=true. Elapsed: 6.259947561s
Jun 25 07:58:12.009: INFO: Pod "pod-subpath-test-dynamicpv-gpj4": Phase="Running", Reason="", readiness=true. Elapsed: 8.325298436s
Jun 25 07:58:14.086: INFO: Pod "pod-subpath-test-dynamicpv-gpj4": Phase="Running", Reason="", readiness=true. Elapsed: 10.402178103s
... skipping 3 lines ...
Jun 25 07:58:22.351: INFO: Pod "pod-subpath-test-dynamicpv-gpj4": Phase="Running", Reason="", readiness=true. Elapsed: 18.666781809s
Jun 25 07:58:24.415: INFO: Pod "pod-subpath-test-dynamicpv-gpj4": Phase="Running", Reason="", readiness=true. Elapsed: 20.730854547s
Jun 25 07:58:26.484: INFO: Pod "pod-subpath-test-dynamicpv-gpj4": Phase="Running", Reason="", readiness=true. Elapsed: 22.799866057s
Jun 25 07:58:28.551: INFO: Pod "pod-subpath-test-dynamicpv-gpj4": Phase="Running", Reason="", readiness=false. Elapsed: 24.866382524s
Jun 25 07:58:30.616: INFO: Pod "pod-subpath-test-dynamicpv-gpj4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.932045982s
STEP: Saw pod success
Jun 25 07:58:30.616: INFO: Pod "pod-subpath-test-dynamicpv-gpj4" satisfied condition "Succeeded or Failed"
Jun 25 07:58:30.684: INFO: Trying to get logs from node ip-192-168-0-215.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-gpj4 container test-container-subpath-dynamicpv-gpj4: <nil>
STEP: delete the pod
Jun 25 07:58:30.887: INFO: Waiting for pod pod-subpath-test-dynamicpv-gpj4 to disappear
Jun 25 07:58:30.951: INFO: Pod pod-subpath-test-dynamicpv-gpj4 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-gpj4
Jun 25 07:58:30.951: INFO: Deleting pod "pod-subpath-test-dynamicpv-gpj4" in namespace "provisioning-9271"
... skipping 260 lines ...
Jun 25 07:58:21.564: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jun 25 07:58:21.632: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.comllcps] to have phase Bound
Jun 25 07:58:21.699: INFO: PersistentVolumeClaim efs.csi.aws.comllcps found but phase is Pending instead of Bound.
Jun 25 07:58:23.765: INFO: PersistentVolumeClaim efs.csi.aws.comllcps found and phase=Bound (2.133013764s)
STEP: Creating pod pod-subpath-test-dynamicpv-9ntn
STEP: Creating a pod to test subpath
Jun 25 07:58:23.970: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-9ntn" in namespace "provisioning-5575" to be "Succeeded or Failed"
Jun 25 07:58:24.072: INFO: Pod "pod-subpath-test-dynamicpv-9ntn": Phase="Pending", Reason="", readiness=false. Elapsed: 101.832515ms
Jun 25 07:58:26.136: INFO: Pod "pod-subpath-test-dynamicpv-9ntn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.165663432s
Jun 25 07:58:28.200: INFO: Pod "pod-subpath-test-dynamicpv-9ntn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.229057602s
Jun 25 07:58:30.262: INFO: Pod "pod-subpath-test-dynamicpv-9ntn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.291759368s
STEP: Saw pod success
Jun 25 07:58:30.262: INFO: Pod "pod-subpath-test-dynamicpv-9ntn" satisfied condition "Succeeded or Failed"
Jun 25 07:58:30.330: INFO: Trying to get logs from node ip-192-168-0-215.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-9ntn container test-container-subpath-dynamicpv-9ntn: <nil>
STEP: delete the pod
Jun 25 07:58:30.530: INFO: Waiting for pod pod-subpath-test-dynamicpv-9ntn to disappear
Jun 25 07:58:30.596: INFO: Pod pod-subpath-test-dynamicpv-9ntn no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-9ntn
Jun 25 07:58:30.596: INFO: Deleting pod "pod-subpath-test-dynamicpv-9ntn" in namespace "provisioning-5575"
STEP: Creating pod pod-subpath-test-dynamicpv-9ntn
STEP: Creating a pod to test subpath
Jun 25 07:58:30.754: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-9ntn" in namespace "provisioning-5575" to be "Succeeded or Failed"
Jun 25 07:58:30.821: INFO: Pod "pod-subpath-test-dynamicpv-9ntn": Phase="Pending", Reason="", readiness=false. Elapsed: 66.576271ms
Jun 25 07:58:32.887: INFO: Pod "pod-subpath-test-dynamicpv-9ntn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.132549197s
Jun 25 07:58:34.955: INFO: Pod "pod-subpath-test-dynamicpv-9ntn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.200936777s
STEP: Saw pod success
Jun 25 07:58:34.955: INFO: Pod "pod-subpath-test-dynamicpv-9ntn" satisfied condition "Succeeded or Failed"
Jun 25 07:58:35.020: INFO: Trying to get logs from node ip-192-168-0-215.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-9ntn container test-container-subpath-dynamicpv-9ntn: <nil>
STEP: delete the pod
Jun 25 07:58:35.222: INFO: Waiting for pod pod-subpath-test-dynamicpv-9ntn to disappear
Jun 25 07:58:35.284: INFO: Pod pod-subpath-test-dynamicpv-9ntn no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-9ntn
Jun 25 07:58:35.284: INFO: Deleting pod "pod-subpath-test-dynamicpv-9ntn" in namespace "provisioning-5575"
... skipping 40 lines ...
  /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
Jun 25 07:58:40.029: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-15138.k8s.local.eksctl.kubeconfig
STEP: Building a namespace api object, basename volumemode
STEP: Binding the e2e-test-privileged-psp PodSecurityPolicy to the default service account in volumemode-4384
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:296
Jun 25 07:58:40.971: 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
Jun 25 07:58:40.972: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-4384" 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:220
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:228
    [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:296

      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 244 lines ...
Jun 25 07:59:00.993: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jun 25 07:59:01.061: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.comd5qgx] to have phase Bound
Jun 25 07:59:01.125: INFO: PersistentVolumeClaim efs.csi.aws.comd5qgx found but phase is Pending instead of Bound.
Jun 25 07:59:03.192: INFO: PersistentVolumeClaim efs.csi.aws.comd5qgx found and phase=Bound (2.130496186s)
STEP: Creating pod exec-volume-test-dynamicpv-wjhs
STEP: Creating a pod to test exec-volume-test
Jun 25 07:59:03.391: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-wjhs" in namespace "volume-8154" to be "Succeeded or Failed"
Jun 25 07:59:03.460: INFO: Pod "exec-volume-test-dynamicpv-wjhs": Phase="Pending", Reason="", readiness=false. Elapsed: 68.959712ms
Jun 25 07:59:05.524: INFO: Pod "exec-volume-test-dynamicpv-wjhs": Phase="Pending", Reason="", readiness=false. Elapsed: 2.132927658s
Jun 25 07:59:07.591: INFO: Pod "exec-volume-test-dynamicpv-wjhs": Phase="Pending", Reason="", readiness=false. Elapsed: 4.200565831s
Jun 25 07:59:09.655: INFO: Pod "exec-volume-test-dynamicpv-wjhs": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.264792385s
STEP: Saw pod success
Jun 25 07:59:09.655: INFO: Pod "exec-volume-test-dynamicpv-wjhs" satisfied condition "Succeeded or Failed"
Jun 25 07:59:09.720: INFO: Trying to get logs from node ip-192-168-0-215.us-west-2.compute.internal pod exec-volume-test-dynamicpv-wjhs container exec-container-dynamicpv-wjhs: <nil>
STEP: delete the pod
Jun 25 07:59:09.925: INFO: Waiting for pod exec-volume-test-dynamicpv-wjhs to disappear
Jun 25 07:59:09.990: INFO: Pod exec-volume-test-dynamicpv-wjhs no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-wjhs
Jun 25 07:59:09.991: INFO: Deleting pod "exec-volume-test-dynamicpv-wjhs" in namespace "volume-8154"
... skipping 560 lines ...
  /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
Jun 25 07:59:27.275: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-15138.k8s.local.eksctl.kubeconfig
STEP: Building a namespace api object, basename volumemode
STEP: Binding the e2e-test-privileged-psp PodSecurityPolicy to the default service account in volumemode-8215
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:296
Jun 25 07:59:28.225: 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
Jun 25 07:59:28.226: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-8215" 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:220
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:228
    [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:296

      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 62 lines ...
Jun 25 07:59:30.918: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jun 25 07:59:30.987: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.comgcdf8] to have phase Bound
Jun 25 07:59:31.051: INFO: PersistentVolumeClaim efs.csi.aws.comgcdf8 found but phase is Pending instead of Bound.
Jun 25 07:59:33.118: INFO: PersistentVolumeClaim efs.csi.aws.comgcdf8 found and phase=Bound (2.131199531s)
STEP: Creating pod pod-subpath-test-dynamicpv-7t5f
STEP: Creating a pod to test subpath
Jun 25 07:59:33.331: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-7t5f" in namespace "provisioning-6499" to be "Succeeded or Failed"
Jun 25 07:59:33.398: INFO: Pod "pod-subpath-test-dynamicpv-7t5f": Phase="Pending", Reason="", readiness=false. Elapsed: 67.252725ms
Jun 25 07:59:35.464: INFO: Pod "pod-subpath-test-dynamicpv-7t5f": Phase="Pending", Reason="", readiness=false. Elapsed: 2.132734446s
Jun 25 07:59:37.530: INFO: Pod "pod-subpath-test-dynamicpv-7t5f": Phase="Pending", Reason="", readiness=false. Elapsed: 4.198943327s
Jun 25 07:59:39.595: INFO: Pod "pod-subpath-test-dynamicpv-7t5f": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.263933181s
STEP: Saw pod success
Jun 25 07:59:39.595: INFO: Pod "pod-subpath-test-dynamicpv-7t5f" satisfied condition "Succeeded or Failed"
Jun 25 07:59:39.657: INFO: Trying to get logs from node ip-192-168-45-111.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-7t5f container test-container-subpath-dynamicpv-7t5f: <nil>
STEP: delete the pod
Jun 25 07:59:39.857: INFO: Waiting for pod pod-subpath-test-dynamicpv-7t5f to disappear
Jun 25 07:59:39.922: INFO: Pod pod-subpath-test-dynamicpv-7t5f no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-7t5f
Jun 25 07:59:39.922: INFO: Deleting pod "pod-subpath-test-dynamicpv-7t5f" in namespace "provisioning-6499"
... skipping 117 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:228
    [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 456 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:228
    [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 21 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:228
    [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 55 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:228
    [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 347 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:228
    [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
------------------------------
[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:221
[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 8 lines ...
  /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
Jun 25 08:00:28.896: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-15138.k8s.local.eksctl.kubeconfig
STEP: Building a namespace api object, basename provisioning
STEP: Binding the e2e-test-privileged-psp PodSecurityPolicy to the default service account in provisioning-8961
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
Jun 25 08:00:30.039: INFO: Creating resource for dynamic PV
Jun 25 08:00:30.039: 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
Jun 25 08:00:30.225: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jun 25 08:00:30.296: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.comlq8ld] to have phase Bound
Jun 25 08:00:30.367: INFO: PersistentVolumeClaim efs.csi.aws.comlq8ld found but phase is Pending instead of Bound.
Jun 25 08:00:32.436: INFO: PersistentVolumeClaim efs.csi.aws.comlq8ld found and phase=Bound (2.13929544s)
STEP: Creating pod pod-subpath-test-dynamicpv-4jbz
STEP: Checking for subpath error in container status
Jun 25 08:00:36.843: INFO: Deleting pod "pod-subpath-test-dynamicpv-4jbz" in namespace "provisioning-8961"
Jun 25 08:00:36.922: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-4jbz" to be fully deleted
STEP: Deleting pod
Jun 25 08:00:39.055: INFO: Deleting pod "pod-subpath-test-dynamicpv-4jbz" in namespace "provisioning-8961"
STEP: Deleting pvc
Jun 25 08:00:39.128: INFO: Deleting PersistentVolumeClaim "efs.csi.aws.comlq8ld"
... skipping 15 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:228
    [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:221
[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 42 lines ...
  /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
Jun 25 08:00:46.938: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-15138.k8s.local.eksctl.kubeconfig
STEP: Building a namespace api object, basename volumemode
STEP: Binding the e2e-test-privileged-psp PodSecurityPolicy to the default service account in volumemode-1443
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:296
Jun 25 08:00:47.863: 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
Jun 25 08:00:47.864: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-1443" 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:220
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:228
    [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:296

      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 29 lines ...

      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
------------------------------
[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:221
[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 8 lines ...
  /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
Jun 25 08:00:39.852: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-15138.k8s.local.eksctl.kubeconfig
STEP: Building a namespace api object, basename provisioning
STEP: Binding the e2e-test-privileged-psp PodSecurityPolicy to the default service account in provisioning-5683
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
Jun 25 08:00:41.038: INFO: Creating resource for dynamic PV
Jun 25 08:00:41.038: 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
Jun 25 08:00:41.233: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jun 25 08:00:41.308: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.com2t225] to have phase Bound
Jun 25 08:00:41.378: INFO: PersistentVolumeClaim efs.csi.aws.com2t225 found but phase is Pending instead of Bound.
Jun 25 08:00:43.450: INFO: PersistentVolumeClaim efs.csi.aws.com2t225 found and phase=Bound (2.141223353s)
STEP: Creating pod pod-subpath-test-dynamicpv-6nlg
STEP: Checking for subpath error in container status
Jun 25 08:00:45.821: INFO: Deleting pod "pod-subpath-test-dynamicpv-6nlg" in namespace "provisioning-5683"
Jun 25 08:00:45.910: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-6nlg" to be fully deleted
STEP: Deleting pod
Jun 25 08:00:48.050: INFO: Deleting pod "pod-subpath-test-dynamicpv-6nlg" in namespace "provisioning-5683"
STEP: Deleting pvc
Jun 25 08:00:48.120: INFO: Deleting PersistentVolumeClaim "efs.csi.aws.com2t225"
... skipping 15 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:228
    [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
------------------------------
[efs-csi] EFS CSI [Driver: efs.csi.aws.com] [Testpattern: Pre-provisioned PV (default fs)] volumes 
  should allow exec of files on the volume
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:196

... skipping 31 lines ...
Jun 25 08:01:04.094: INFO: PersistentVolumeClaim pvc-bvdxp found but phase is Pending instead of Bound.
Jun 25 08:01:06.162: INFO: PersistentVolumeClaim pvc-bvdxp found and phase=Bound (14.540470184s)
Jun 25 08:01:06.162: INFO: Waiting up to 3m0s for PersistentVolume efs.csi.aws.com-52bv8 to have phase Bound
Jun 25 08:01:06.230: INFO: PersistentVolume efs.csi.aws.com-52bv8 found and phase=Bound (68.131849ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-zzjx
STEP: Creating a pod to test exec-volume-test
Jun 25 08:01:06.452: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-zzjx" in namespace "volume-580" to be "Succeeded or Failed"
Jun 25 08:01:06.517: INFO: Pod "exec-volume-test-preprovisionedpv-zzjx": Phase="Pending", Reason="", readiness=false. Elapsed: 65.725281ms
Jun 25 08:01:08.585: INFO: Pod "exec-volume-test-preprovisionedpv-zzjx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.133376773s
Jun 25 08:01:10.652: INFO: Pod "exec-volume-test-preprovisionedpv-zzjx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.200603705s
STEP: Saw pod success
Jun 25 08:01:10.652: INFO: Pod "exec-volume-test-preprovisionedpv-zzjx" satisfied condition "Succeeded or Failed"
Jun 25 08:01:10.719: INFO: Trying to get logs from node ip-192-168-0-215.us-west-2.compute.internal pod exec-volume-test-preprovisionedpv-zzjx container exec-container-preprovisionedpv-zzjx: <nil>
STEP: delete the pod
Jun 25 08:01:10.933: INFO: Waiting for pod exec-volume-test-preprovisionedpv-zzjx to disappear
Jun 25 08:01:11.001: INFO: Pod exec-volume-test-preprovisionedpv-zzjx no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-zzjx
Jun 25 08:01:11.001: INFO: Deleting pod "exec-volume-test-preprovisionedpv-zzjx" in namespace "volume-580"
... skipping 68 lines ...
STEP: Binding the e2e-test-privileged-psp PodSecurityPolicy to the default service account in efs-1942
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:373
STEP: Creating efs pvc & pv
STEP: Creating pod to mount pvc "efs-1942" and run "mount && mount | grep /mnt/volume1 | grep fs-0daad606ce96cef4c"
Jun 25 08:00:54.995: INFO: Waiting up to 5m0s for pod "pvc-tester-lmlv7" in namespace "efs-1942" to be "Succeeded or Failed"
Jun 25 08:00:55.060: INFO: Pod "pvc-tester-lmlv7": Phase="Pending", Reason="", readiness=false. Elapsed: 65.237757ms
Jun 25 08:00:57.128: INFO: Pod "pvc-tester-lmlv7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.133214309s
Jun 25 08:00:59.194: INFO: Pod "pvc-tester-lmlv7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.198982064s
Jun 25 08:01:01.261: INFO: Pod "pvc-tester-lmlv7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.266250607s
Jun 25 08:01:03.329: INFO: Pod "pvc-tester-lmlv7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.333814701s
Jun 25 08:01:05.397: INFO: Pod "pvc-tester-lmlv7": Phase="Pending", Reason="", readiness=false. Elapsed: 10.402018812s
... skipping 9 lines ...
Jun 25 08:01:26.071: INFO: Pod "pvc-tester-lmlv7": Phase="Pending", Reason="", readiness=false. Elapsed: 31.076273784s
Jun 25 08:01:28.136: INFO: Pod "pvc-tester-lmlv7": Phase="Pending", Reason="", readiness=false. Elapsed: 33.141275014s
Jun 25 08:01:30.202: INFO: Pod "pvc-tester-lmlv7": Phase="Pending", Reason="", readiness=false. Elapsed: 35.206649584s
Jun 25 08:01:32.270: INFO: Pod "pvc-tester-lmlv7": Phase="Pending", Reason="", readiness=false. Elapsed: 37.274478639s
Jun 25 08:01:34.343: INFO: Pod "pvc-tester-lmlv7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 39.348073944s
STEP: Saw pod success
Jun 25 08:01:34.343: INFO: Pod "pvc-tester-lmlv7" satisfied condition "Succeeded or Failed"
Jun 25 08:01:34.419: INFO: pod "pvc-tester-lmlv7" logs:
 overlay on / type overlay (rw,relatime,lowerdir=/var/lib/docker/overlay2/l/V42YLNUXNTQWHZSHSOPVUN6HBW:/var/lib/docker/overlay2/l/EWSEABMFRMSW76L2RIW44PQT2U,upperdir=/var/lib/docker/overlay2/5056294b4eb3c1c12fc4bb058d10ea6d7bbd8432e5085b1841004e5b2bc06d35/diff,workdir=/var/lib/docker/overlay2/5056294b4eb3c1c12fc4bb058d10ea6d7bbd8432e5085b1841004e5b2bc06d35/work)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev type tmpfs (rw,nosuid,size=65536k,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=666)
sysfs on /sys type sysfs (ro,nosuid,nodev,noexec,relatime)
... skipping 373 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:228
    [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 28 lines ...
Jun 25 08:01:45.186: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jun 25 08:01:45.260: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.com76tsv] to have phase Bound
Jun 25 08:01:45.326: INFO: PersistentVolumeClaim efs.csi.aws.com76tsv found but phase is Pending instead of Bound.
Jun 25 08:01:47.392: INFO: PersistentVolumeClaim efs.csi.aws.com76tsv found and phase=Bound (2.132370778s)
STEP: Creating pod pod-subpath-test-dynamicpv-r2jv
STEP: Creating a pod to test subpath
Jun 25 08:01:47.601: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-r2jv" in namespace "provisioning-9967" to be "Succeeded or Failed"
Jun 25 08:01:47.706: INFO: Pod "pod-subpath-test-dynamicpv-r2jv": Phase="Pending", Reason="", readiness=false. Elapsed: 104.59722ms
Jun 25 08:01:49.772: INFO: Pod "pod-subpath-test-dynamicpv-r2jv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.17114751s
Jun 25 08:01:51.839: INFO: Pod "pod-subpath-test-dynamicpv-r2jv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.237607377s
Jun 25 08:01:53.905: INFO: Pod "pod-subpath-test-dynamicpv-r2jv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.303852291s
STEP: Saw pod success
Jun 25 08:01:53.905: INFO: Pod "pod-subpath-test-dynamicpv-r2jv" satisfied condition "Succeeded or Failed"
Jun 25 08:01:53.969: INFO: Trying to get logs from node ip-192-168-73-224.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-r2jv container test-container-volume-dynamicpv-r2jv: <nil>
STEP: delete the pod
Jun 25 08:01:54.176: INFO: Waiting for pod pod-subpath-test-dynamicpv-r2jv to disappear
Jun 25 08:01:54.242: INFO: Pod pod-subpath-test-dynamicpv-r2jv no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-r2jv
Jun 25 08:01:54.243: INFO: Deleting pod "pod-subpath-test-dynamicpv-r2jv" in namespace "provisioning-9967"
... skipping 282 lines ...
Jun 25 08:02:04.584: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jun 25 08:02:04.658: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.com2lkpl] to have phase Bound
Jun 25 08:02:04.725: INFO: PersistentVolumeClaim efs.csi.aws.com2lkpl found but phase is Pending instead of Bound.
Jun 25 08:02:06.788: INFO: PersistentVolumeClaim efs.csi.aws.com2lkpl found and phase=Bound (2.130128843s)
STEP: Creating pod pod-subpath-test-dynamicpv-lxzq
STEP: Creating a pod to test subpath
Jun 25 08:02:07.038: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-lxzq" in namespace "provisioning-2885" to be "Succeeded or Failed"
Jun 25 08:02:07.102: INFO: Pod "pod-subpath-test-dynamicpv-lxzq": Phase="Pending", Reason="", readiness=false. Elapsed: 63.936368ms
Jun 25 08:02:09.167: INFO: Pod "pod-subpath-test-dynamicpv-lxzq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.129162505s
Jun 25 08:02:11.234: INFO: Pod "pod-subpath-test-dynamicpv-lxzq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.196284734s
Jun 25 08:02:13.301: INFO: Pod "pod-subpath-test-dynamicpv-lxzq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.263239287s
STEP: Saw pod success
Jun 25 08:02:13.301: INFO: Pod "pod-subpath-test-dynamicpv-lxzq" satisfied condition "Succeeded or Failed"
Jun 25 08:02:13.365: INFO: Trying to get logs from node ip-192-168-73-224.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-lxzq container test-container-subpath-dynamicpv-lxzq: <nil>
STEP: delete the pod
Jun 25 08:02:13.609: INFO: Waiting for pod pod-subpath-test-dynamicpv-lxzq to disappear
Jun 25 08:02:13.680: INFO: Pod pod-subpath-test-dynamicpv-lxzq no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-lxzq
Jun 25 08:02:13.680: INFO: Deleting pod "pod-subpath-test-dynamicpv-lxzq" in namespace "provisioning-2885"
... skipping 560 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:228
    [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 34 lines ...
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:234
    should continue reading/writing without hanging after the driver pod is restarted
    /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:270
------------------------------
[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:221
[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 8 lines ...
  /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
Jun 25 08:00:33.191: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-15138.k8s.local.eksctl.kubeconfig
STEP: Building a namespace api object, basename volumemode
STEP: Binding the e2e-test-privileged-psp PodSecurityPolicy to the default service account in volumemode-3919
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
Jun 25 08:00:34.673: INFO: Waiting for PV pv6vwcr to bind to PVC pvc-fndt2
Jun 25 08:00:34.673: INFO: Waiting up to timeout=3m0s for PersistentVolumeClaims [pvc-fndt2] to have phase Bound
Jun 25 08:00:34.739: INFO: PersistentVolumeClaim pvc-fndt2 found but phase is Pending instead of Bound.
... skipping 21 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:228
    [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:221
[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 445 lines ...
  /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
Jun 25 08:03:12.542: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-15138.k8s.local.eksctl.kubeconfig
STEP: Building a namespace api object, basename volumemode
STEP: Binding the e2e-test-privileged-psp PodSecurityPolicy to the default service account in volumemode-2573
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:296
Jun 25 08:03:13.517: 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
Jun 25 08:03:13.518: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-2573" 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:220
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:228
    [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:296

      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 136 lines ...
STEP: Binding the e2e-test-privileged-psp PodSecurityPolicy to the default service account in efs-4928
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:368
STEP: Creating efs pvc & pv
STEP: Creating pod to mount pvc "efs-4928" and run "mount && mount | grep /mnt/volume1 | grep 127.0.0.1"
Jun 25 08:03:15.132: INFO: Waiting up to 5m0s for pod "pvc-tester-b5bp9" in namespace "efs-4928" to be "Succeeded or Failed"
Jun 25 08:03:15.198: INFO: Pod "pvc-tester-b5bp9": Phase="Pending", Reason="", readiness=false. Elapsed: 66.269104ms
Jun 25 08:03:17.267: INFO: Pod "pvc-tester-b5bp9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.134902559s
Jun 25 08:03:19.332: INFO: Pod "pvc-tester-b5bp9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.200496057s
Jun 25 08:03:21.398: INFO: Pod "pvc-tester-b5bp9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.266263569s
Jun 25 08:03:23.468: INFO: Pod "pvc-tester-b5bp9": Phase="Pending", Reason="", readiness=false. Elapsed: 8.336043906s
Jun 25 08:03:25.536: INFO: Pod "pvc-tester-b5bp9": Phase="Pending", Reason="", readiness=false. Elapsed: 10.403844301s
Jun 25 08:03:27.602: INFO: Pod "pvc-tester-b5bp9": Phase="Pending", Reason="", readiness=false. Elapsed: 12.470293073s
Jun 25 08:03:29.669: INFO: Pod "pvc-tester-b5bp9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.537387816s
STEP: Saw pod success
Jun 25 08:03:29.669: INFO: Pod "pvc-tester-b5bp9" satisfied condition "Succeeded or Failed"
Jun 25 08:03:29.747: INFO: pod "pvc-tester-b5bp9" logs:
 overlay on / type overlay (rw,relatime,lowerdir=/var/lib/docker/overlay2/l/F4F6TQRW7RH4IUZ7MAKNOYQTCO:/var/lib/docker/overlay2/l/EWSEABMFRMSW76L2RIW44PQT2U,upperdir=/var/lib/docker/overlay2/316df1352f78a4f85cb1d4f10862819619831e80d37f698d8318382619abc5db/diff,workdir=/var/lib/docker/overlay2/316df1352f78a4f85cb1d4f10862819619831e80d37f698d8318382619abc5db/work)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev type tmpfs (rw,nosuid,size=65536k,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=666)
sysfs on /sys type sysfs (ro,nosuid,nodev,noexec,relatime)
... skipping 117 lines ...
    [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 not mount / map unused volumes in a pod [LinuxOnly]
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:351
------------------------------
[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:221
[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 8 lines ...
  /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
Jun 25 07:58:41.160: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-15138.k8s.local.eksctl.kubeconfig
STEP: Building a namespace api object, basename volumemode
STEP: Binding the e2e-test-privileged-psp PodSecurityPolicy to the default service account in volumemode-2818
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
Jun 25 08:03:42.749: INFO: Warning: did not get event about provisioing failed
STEP: Deleting pvc
Jun 25 08:03:42.881: INFO: Deleting PersistentVolumeClaim "pvc-cnnlt"
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
Jun 25 08:03:43.150: 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:220
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:228
    [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-0daad606ce96cef4c"
STEP: Deleted EFS filesystem "fs-0daad606ce96cef4c"


Ran 35 of 190 Specs in 537.782 seconds
SUCCESS! -- 35 Passed | 0 Failed | 0 Pending | 155 Skipped


Ginkgo ran 1 suite in 10m3.065529526s
Test Suite Passed
+ TEST_PASSED=0
+ set -e
... skipping 1154 lines ...
I0625 08:00:37.077177       1 node.go:224] NodeUnpublishVolume: unmounting /var/lib/kubelet/pods/dd660bf1-c634-486a-a699-beda661fb281/volumes/kubernetes.io~csi/pvc-c3dd9b76-d815-40cf-b2e7-6db70b7cbadd/mount
I0625 08:00:37.096571       1 node.go:229] NodeUnpublishVolume: /var/lib/kubelet/pods/dd660bf1-c634-486a-a699-beda661fb281/volumes/kubernetes.io~csi/pvc-c3dd9b76-d815-40cf-b2e7-6db70b7cbadd/mount unmounted
I0625 08:00:37.178453       1 node.go:287] NodeGetCapabilities: called with args 
I0625 08:00:37.278830       1 node.go:287] NodeGetCapabilities: called with args 
I0625 08:00:37.279764       1 node.go:287] NodeGetCapabilities: called with args 
I0625 08:00:37.280468       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-0daad606ce96cef4c" staging_target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pv6vwcr" target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pv6vwcr/bb574dfd-3296-4f2b-917b-be7583134262" volume_capability:<block:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > 
E0625 08:00:37.280521       1 driver.go:107] GRPC error: rpc error: code = InvalidArgument desc = Volume capability not supported: only filesystem volumes are supported
I0625 08:00:37.784513       1 node.go:287] NodeGetCapabilities: called with args 
I0625 08:00:37.786305       1 node.go:287] NodeGetCapabilities: called with args 
I0625 08:00:37.787004       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-0daad606ce96cef4c" staging_target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pv6vwcr" target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pv6vwcr/bb574dfd-3296-4f2b-917b-be7583134262" volume_capability:<block:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > 
E0625 08:00:37.787055       1 driver.go:107] GRPC error: rpc error: code = InvalidArgument desc = Volume capability not supported: only filesystem volumes are supported
I0625 08:00:38.793889       1 node.go:287] NodeGetCapabilities: called with args 
I0625 08:00:38.794595       1 node.go:287] NodeGetCapabilities: called with args 
I0625 08:00:38.795427       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-0daad606ce96cef4c" staging_target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pv6vwcr" target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pv6vwcr/bb574dfd-3296-4f2b-917b-be7583134262" volume_capability:<block:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > 
E0625 08:00:38.795487       1 driver.go:107] GRPC error: rpc error: code = InvalidArgument desc = Volume capability not supported: only filesystem volumes are supported
I0625 08:00:40.812017       1 node.go:287] NodeGetCapabilities: called with args 
I0625 08:00:40.814455       1 node.go:287] NodeGetCapabilities: called with args 
I0625 08:00:40.816541       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-0daad606ce96cef4c" staging_target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pv6vwcr" target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pv6vwcr/bb574dfd-3296-4f2b-917b-be7583134262" volume_capability:<block:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > 
E0625 08:00:40.816593       1 driver.go:107] GRPC error: rpc error: code = InvalidArgument desc = Volume capability not supported: only filesystem volumes are supported
I0625 08:00:44.850796       1 node.go:287] NodeGetCapabilities: called with args 
I0625 08:00:44.851827       1 node.go:287] NodeGetCapabilities: called with args 
I0625 08:00:44.852511       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-0daad606ce96cef4c" staging_target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pv6vwcr" target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pv6vwcr/bb574dfd-3296-4f2b-917b-be7583134262" volume_capability:<block:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > 
E0625 08:00:44.852554       1 driver.go:107] GRPC error: rpc error: code = InvalidArgument desc = Volume capability not supported: only filesystem volumes are supported
I0625 08:00:52.924893       1 node.go:287] NodeGetCapabilities: called with args 
I0625 08:00:52.926010       1 node.go:287] NodeGetCapabilities: called with args 
I0625 08:00:52.926596       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-0daad606ce96cef4c" staging_target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pv6vwcr" target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pv6vwcr/bb574dfd-3296-4f2b-917b-be7583134262" volume_capability:<block:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > 
E0625 08:00:52.926639       1 driver.go:107] GRPC error: rpc error: code = InvalidArgument desc = Volume capability not supported: only filesystem volumes are supported
I0625 08:01:00.428165       1 reaper.go:107] reaper: waited for process &{280 1 90 280 280 stunnel}
I0625 08:01:06.549121       1 node.go:287] NodeGetCapabilities: called with args 
I0625 08:01:06.550075       1 node.go:287] NodeGetCapabilities: called with args 
I0625 08:01:06.550728       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-0daad606ce96cef4c" target_path:"/var/lib/kubelet/pods/675669b6-03d1-4a53-a3e2-b64149dbfc98/volumes/kubernetes.io~csi/efs.csi.aws.com-52bv8/mount" volume_capability:<mount:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > 
I0625 08:01:06.550793       1 node.go:175] NodePublishVolume: creating dir /var/lib/kubelet/pods/675669b6-03d1-4a53-a3e2-b64149dbfc98/volumes/kubernetes.io~csi/efs.csi.aws.com-52bv8/mount
I0625 08:01:06.550837       1 node.go:180] NodePublishVolume: mounting fs-0daad606ce96cef4c:/ at /var/lib/kubelet/pods/675669b6-03d1-4a53-a3e2-b64149dbfc98/volumes/kubernetes.io~csi/efs.csi.aws.com-52bv8/mount with options [tls]
I0625 08:01:06.821594       1 node.go:185] NodePublishVolume: /var/lib/kubelet/pods/675669b6-03d1-4a53-a3e2-b64149dbfc98/volumes/kubernetes.io~csi/efs.csi.aws.com-52bv8/mount was mounted
I0625 08:01:06.851067       1 node.go:287] NodeGetCapabilities: called with args 
I0625 08:01:06.852047       1 node.go:287] NodeGetCapabilities: called with args 
I0625 08:01:06.852723       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-0daad606ce96cef4c" staging_target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pv6vwcr" target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pv6vwcr/bb574dfd-3296-4f2b-917b-be7583134262" volume_capability:<block:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > 
E0625 08:01:06.852783       1 driver.go:107] GRPC error: rpc error: code = InvalidArgument desc = Volume capability not supported: only filesystem volumes are supported
I0625 08:01:07.359381       1 node.go:287] NodeGetCapabilities: called with args 
I0625 08:01:07.360158       1 node.go:287] NodeGetCapabilities: called with args 
I0625 08:01:07.360917       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-0daad606ce96cef4c" staging_target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pv6vwcr" target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pv6vwcr/bb574dfd-3296-4f2b-917b-be7583134262" volume_capability:<block:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > 
E0625 08:01:07.360964       1 driver.go:107] GRPC error: rpc error: code = InvalidArgument desc = Volume capability not supported: only filesystem volumes are supported
I0625 08:01:08.369415       1 node.go:287] NodeGetCapabilities: called with args 
I0625 08:01:08.370509       1 node.go:287] NodeGetCapabilities: called with args 
I0625 08:01:08.371158       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-0daad606ce96cef4c" staging_target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pv6vwcr" target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pv6vwcr/bb574dfd-3296-4f2b-917b-be7583134262" volume_capability:<block:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > 
E0625 08:01:08.371208       1 driver.go:107] GRPC error: rpc error: code = InvalidArgument desc = Volume capability not supported: only filesystem volumes are supported
I0625 08:01:09.580784       1 node.go:200] NodeUnpublishVolume: called with args volume_id:"fs-0daad606ce96cef4c" target_path:"/var/lib/kubelet/pods/675669b6-03d1-4a53-a3e2-b64149dbfc98/volumes/kubernetes.io~csi/efs.csi.aws.com-52bv8/mount" 
I0625 08:01:09.582869       1 node.go:224] NodeUnpublishVolume: unmounting /var/lib/kubelet/pods/675669b6-03d1-4a53-a3e2-b64149dbfc98/volumes/kubernetes.io~csi/efs.csi.aws.com-52bv8/mount
I0625 08:01:09.599916       1 node.go:229] NodeUnpublishVolume: /var/lib/kubelet/pods/675669b6-03d1-4a53-a3e2-b64149dbfc98/volumes/kubernetes.io~csi/efs.csi.aws.com-52bv8/mount unmounted
I0625 08:01:09.682217       1 node.go:287] NodeGetCapabilities: called with args 
I0625 08:01:09.683302       1 node.go:287] NodeGetCapabilities: called with args 
I0625 08:01:09.684232       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-0daad606ce96cef4c" staging_target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pv6vwcr" target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pv6vwcr/bb574dfd-3296-4f2b-917b-be7583134262" volume_capability:<block:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > 
E0625 08:01:09.684292       1 driver.go:107] GRPC error: rpc error: code = InvalidArgument desc = Volume capability not supported: only filesystem volumes are supported
I0625 08:01:10.187203       1 node.go:287] NodeGetCapabilities: called with args 
I0625 08:01:10.188115       1 node.go:287] NodeGetCapabilities: called with args 
I0625 08:01:10.188941       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-0daad606ce96cef4c" staging_target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pv6vwcr" target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pv6vwcr/bb574dfd-3296-4f2b-917b-be7583134262" volume_capability:<block:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > 
E0625 08:01:10.188987       1 driver.go:107] GRPC error: rpc error: code = InvalidArgument desc = Volume capability not supported: only filesystem volumes are supported
I0625 08:01:11.197021       1 node.go:287] NodeGetCapabilities: called with args 
I0625 08:01:11.198127       1 node.go:287] NodeGetCapabilities: called with args 
I0625 08:01:11.198704       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-0daad606ce96cef4c" staging_target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pv6vwcr" target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pv6vwcr/bb574dfd-3296-4f2b-917b-be7583134262" volume_capability:<block:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > 
E0625 08:01:11.198760       1 driver.go:107] GRPC error: rpc error: code = InvalidArgument desc = Volume capability not supported: only filesystem volumes are supported
I0625 08:01:13.215291       1 node.go:287] NodeGetCapabilities: called with args 
I0625 08:01:13.216325       1 node.go:287] NodeGetCapabilities: called with args 
I0625 08:01:13.216874       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-0daad606ce96cef4c" staging_target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pv6vwcr" target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pv6vwcr/bb574dfd-3296-4f2b-917b-be7583134262" volume_capability:<block:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > 
E0625 08:01:13.216926       1 driver.go:107] GRPC error: rpc error: code = InvalidArgument desc = Volume capability not supported: only filesystem volumes are supported
I0625 08:01:17.253702       1 node.go:287] NodeGetCapabilities: called with args 
I0625 08:01:17.254591       1 node.go:287] NodeGetCapabilities: called with args 
I0625 08:01:17.255266       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-0daad606ce96cef4c" staging_target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pv6vwcr" target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pv6vwcr/bb574dfd-3296-4f2b-917b-be7583134262" volume_capability:<block:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > 
E0625 08:01:17.255311       1 driver.go:107] GRPC error: rpc error: code = InvalidArgument desc = Volume capability not supported: only filesystem volumes are supported
I0625 08:01:17.659690       1 node.go:287] NodeGetCapabilities: called with args 
I0625 08:01:17.664665       1 node.go:287] NodeGetCapabilities: called with args 
I0625 08:01:17.665370       1 node.go:287] NodeGetCapabilities: called with args 
I0625 08:01:17.666013       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-0daad606ce96cef4c::fsap-013a5d0aeaa1357c2" target_path:"/var/lib/kubelet/pods/1d25b42a-94ad-4594-9757-0cf5a512c341/volumes/kubernetes.io~csi/pvc-d8988e58-f6c5-445a-a7d3-0f6e13914807/mount" volume_capability:<mount:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > volume_context:<key:"storage.kubernetes.io/csiProvisionerIdentity" value:"1656143629735-8081-efs.csi.aws.com" > 
I0625 08:01:17.666079       1 node.go:175] NodePublishVolume: creating dir /var/lib/kubelet/pods/1d25b42a-94ad-4594-9757-0cf5a512c341/volumes/kubernetes.io~csi/pvc-d8988e58-f6c5-445a-a7d3-0f6e13914807/mount
I0625 08:01:17.666124       1 node.go:180] NodePublishVolume: mounting fs-0daad606ce96cef4c:/ at /var/lib/kubelet/pods/1d25b42a-94ad-4594-9757-0cf5a512c341/volumes/kubernetes.io~csi/pvc-d8988e58-f6c5-445a-a7d3-0f6e13914807/mount with options [accesspoint=fsap-013a5d0aeaa1357c2 tls]
I0625 08:01:17.954955       1 node.go:185] NodePublishVolume: /var/lib/kubelet/pods/1d25b42a-94ad-4594-9757-0cf5a512c341/volumes/kubernetes.io~csi/pvc-d8988e58-f6c5-445a-a7d3-0f6e13914807/mount was mounted
I0625 08:01:25.332134       1 node.go:287] NodeGetCapabilities: called with args 
I0625 08:01:25.333289       1 node.go:287] NodeGetCapabilities: called with args 
I0625 08:01:25.334003       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-0daad606ce96cef4c" staging_target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pv6vwcr" target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pv6vwcr/bb574dfd-3296-4f2b-917b-be7583134262" volume_capability:<block:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > 
E0625 08:01:25.334053       1 driver.go:107] GRPC error: rpc error: code = InvalidArgument desc = Volume capability not supported: only filesystem volumes are supported
I0625 08:01:31.392034       1 node.go:200] NodeUnpublishVolume: called with args volume_id:"fs-0daad606ce96cef4c::fsap-013a5d0aeaa1357c2" target_path:"/var/lib/kubelet/pods/1d25b42a-94ad-4594-9757-0cf5a512c341/volumes/kubernetes.io~csi/pvc-d8988e58-f6c5-445a-a7d3-0f6e13914807/mount" 
I0625 08:01:31.393626       1 node.go:224] NodeUnpublishVolume: unmounting /var/lib/kubelet/pods/1d25b42a-94ad-4594-9757-0cf5a512c341/volumes/kubernetes.io~csi/pvc-d8988e58-f6c5-445a-a7d3-0f6e13914807/mount
I0625 08:01:31.411520       1 node.go:229] NodeUnpublishVolume: /var/lib/kubelet/pods/1d25b42a-94ad-4594-9757-0cf5a512c341/volumes/kubernetes.io~csi/pvc-d8988e58-f6c5-445a-a7d3-0f6e13914807/mount unmounted
I0625 08:01:31.493745       1 node.go:287] NodeGetCapabilities: called with args 
I0625 08:01:39.513191       1 reaper.go:107] reaper: waited for process &{314 1 90 314 314 stunnel}
I0625 08:01:41.383440       1 node.go:287] NodeGetCapabilities: called with args 
I0625 08:01:41.384365       1 node.go:287] NodeGetCapabilities: called with args 
I0625 08:01:41.385002       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-0daad606ce96cef4c" staging_target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pv6vwcr" target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pv6vwcr/bb574dfd-3296-4f2b-917b-be7583134262" volume_capability:<block:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > 
E0625 08:01:41.385049       1 driver.go:107] GRPC error: rpc error: code = InvalidArgument desc = Volume capability not supported: only filesystem volumes are supported
I0625 08:02:13.480450       1 node.go:287] NodeGetCapabilities: called with args 
I0625 08:02:13.481416       1 node.go:287] NodeGetCapabilities: called with args 
I0625 08:02:13.482179       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-0daad606ce96cef4c" staging_target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pv6vwcr" target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pv6vwcr/bb574dfd-3296-4f2b-917b-be7583134262" volume_capability:<block:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > 
E0625 08:02:13.482239       1 driver.go:107] GRPC error: rpc error: code = InvalidArgument desc = Volume capability not supported: only filesystem volumes are supported
I0625 08:02:13.583388       1 reaper.go:107] reaper: waited for process &{331 1 90 331 331 stunnel}
I0625 08:02:24.606673       1 reaper.go:107] reaper: waited for process &{348 1 90 348 348 stunnel}
I0625 08:02:45.474056       1 node.go:287] NodeGetCapabilities: called with args 
I0625 08:02:45.490227       1 node.go:287] NodeGetCapabilities: called with args 
I0625 08:02:45.490823       1 node.go:287] NodeGetCapabilities: called with args 
I0625 08:02:45.491361       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-0daad606ce96cef4c::fsap-0a4419f988b5e0fa7" target_path:"/var/lib/kubelet/pods/1624f3d0-50a2-4f0c-b18d-cd35d2e6cb62/volumes/kubernetes.io~csi/pvc-c41d145a-767c-46fe-88b4-0b19b460e7a9/mount" volume_capability:<mount:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > volume_context:<key:"storage.kubernetes.io/csiProvisionerIdentity" value:"1656143629735-8081-efs.csi.aws.com" > 
... skipping 117 lines ...