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 05:01
Elapsed38m48s
Revisiondb098fee5045474bb8654fca27552e1538f10b0e
Refs 714

No Test Failures!


Show 35 Passed Tests

Show 155 Skipped Tests

Error lines from build-log.txt

... skipping 234 lines ...
#9 2.757 --> Processing Dependency: libperl.so()(64bit) for package: 4:perl-5.16.3-299.amzn2.0.1.x86_64
#9 2.758 ---> Package perl-File-Temp.noarch 0:0.23.01-3.amzn2 will be installed
#9 2.760 ---> Package perl-Getopt-Long.noarch 0:2.40-3.amzn2 will be installed
#9 2.761 --> Processing Dependency: perl(Pod::Usage) >= 1.14 for package: perl-Getopt-Long-2.40-3.amzn2.noarch
#9 2.762 --> Processing Dependency: perl(Text::ParseWords) for package: perl-Getopt-Long-2.40-3.amzn2.noarch
#9 2.762 ---> Package perl-Git.noarch 0:2.32.0-1.amzn2.0.1 will be installed
#9 2.764 --> Processing Dependency: perl(Error) for package: perl-Git-2.32.0-1.amzn2.0.1.noarch
#9 2.765 ---> Package perl-PathTools.x86_64 0:3.40-5.amzn2.0.2 will be installed
#9 2.766 ---> Package perl-TermReadKey.x86_64 0:2.30-20.amzn2.0.2 will be installed
#9 2.767 ---> Package perl-Thread-Queue.noarch 0:3.02-2.amzn2 will be installed
#9 2.768 ---> Package perl-threads.x86_64 0:1.87-4.amzn2.0.2 will be installed
#9 2.769 ---> Package pkgconfig.x86_64 1:0.27.1-4.amzn2.0.2 will be installed
#9 2.772 ---> Package system-rpm-config.noarch 0:9.1.0-76.amzn2.0.14 will be installed
... skipping 15 lines ...
#9 2.835 --> Processing Dependency: openssh = 7.4p1-22.amzn2.0.1 for package: openssh-clients-7.4p1-22.amzn2.0.1.x86_64
#9 2.837 --> Processing Dependency: fipscheck-lib(x86-64) >= 1.3.0 for package: openssh-clients-7.4p1-22.amzn2.0.1.x86_64
#9 2.839 --> Processing Dependency: libfipscheck.so.1()(64bit) for package: openssh-clients-7.4p1-22.amzn2.0.1.x86_64
#9 2.839 --> Processing Dependency: libedit.so.0()(64bit) for package: openssh-clients-7.4p1-22.amzn2.0.1.x86_64
#9 2.841 ---> Package pcre2.x86_64 0:10.23-2.amzn2.0.2 will be installed
#9 2.842 ---> Package perl-Carp.noarch 0:1.26-244.amzn2 will be installed
#9 2.843 ---> Package perl-Error.noarch 1:0.17020-2.amzn2 will be installed
#9 2.844 ---> Package perl-Exporter.noarch 0:5.68-3.amzn2 will be installed
#9 2.844 ---> Package perl-File-Path.noarch 0:2.09-2.amzn2 will be installed
#9 2.845 ---> Package perl-Filter.x86_64 0:1.49-3.amzn2.0.2 will be installed
#9 2.847 ---> Package perl-Pod-Simple.noarch 1:3.28-4.amzn2 will be installed
#9 2.850 --> Processing Dependency: perl(Pod::Escapes) >= 1.04 for package: 1:perl-Pod-Simple-3.28-4.amzn2.noarch
#9 2.853 --> Processing Dependency: perl(Encode) for package: 1:perl-Pod-Simple-3.28-4.amzn2.noarch
... skipping 175 lines ...
#9 3.289  pam                       x86_64 1.1.8-23.amzn2.0.1           amzn2-core 715 k
#9 3.289  patch                     x86_64 2.7.1-12.amzn2.0.2           amzn2-core 110 k
#9 3.289  pcre2                     x86_64 10.23-2.amzn2.0.2            amzn2-core 209 k
#9 3.289  perl                      x86_64 4:5.16.3-299.amzn2.0.1       amzn2-core 8.0 M
#9 3.289  perl-Carp                 noarch 1.26-244.amzn2               amzn2-core  19 k
#9 3.289  perl-Encode               x86_64 2.51-7.amzn2.0.2             amzn2-core 1.5 M
#9 3.289  perl-Error                noarch 1:0.17020-2.amzn2            amzn2-core  32 k
#9 3.289  perl-Exporter             noarch 5.68-3.amzn2                 amzn2-core  29 k
#9 3.289  perl-File-Path            noarch 2.09-2.amzn2                 amzn2-core  27 k
#9 3.289  perl-File-Temp            noarch 0.23.01-3.amzn2              amzn2-core  56 k
#9 3.289  perl-Filter               x86_64 1.49-3.amzn2.0.2             amzn2-core  76 k
#9 3.289  perl-Getopt-Long          noarch 2.40-3.amzn2                 amzn2-core  56 k
#9 3.289  perl-Git                  noarch 2.32.0-1.amzn2.0.1           amzn2-core  43 k
... skipping 95 lines ...
#9 9.360   Installing : 1:perl-Pod-Simple-3.28-4.amzn2.noarch                      34/88 
#9 9.405   Installing : perl-Getopt-Long-2.40-3.amzn2.noarch                       35/88 
#9 9.547   Installing : 4:perl-libs-5.16.3-299.amzn2.0.1.x86_64                    36/88 
#9 11.18   Installing : 4:perl-5.16.3-299.amzn2.0.1.x86_64                         37/88 
#9 11.26   Installing : perl-Thread-Queue-3.02-2.amzn2.noarch                      38/88 
#9 11.30   Installing : perl-TermReadKey-2.30-20.amzn2.0.2.x86_64                  39/88 
#9 11.34   Installing : 1:perl-Error-0.17020-2.amzn2.noarch                        40/88 
#9 11.37   Installing : fipscheck-lib-1.4.1-6.amzn2.0.2.x86_64                     41/88 
#9 11.42   Installing : fipscheck-1.4.1-6.amzn2.0.2.x86_64                         42/88 
#9 11.46   Installing : dwz-0.11-3.amzn2.0.3.x86_64                                43/88 
#9 11.50   Installing : 1:pkgconfig-0.27.1-4.amzn2.0.2.x86_64                      44/88 
#9 11.58   Installing : pcre2-10.23-2.amzn2.0.2.x86_64                             45/88 
#9 11.65   Installing : libsmartcols-2.30.2-2.amzn2.0.7.x86_64                     46/88 
... skipping 25 lines ...
#9 16.09   Installing : 7:device-mapper-libs-1.02.170-6.amzn2.5.x86_64             72/88 
#9 16.20   Installing : cryptsetup-libs-1.7.4-4.amzn2.x86_64                       73/88 
#9 16.30   Installing : elfutils-libs-0.176-2.amzn2.x86_64                         74/88 
#9 16.42   Installing : systemd-libs-219-78.amzn2.0.18.x86_64                      75/88 
#9 16.51   Installing : 1:dbus-libs-1.10.24-7.amzn2.x86_64                         76/88 
#9 18.02   Installing : systemd-219-78.amzn2.0.18.x86_64                           77/88 
#9 18.58 Failed to get D-Bus connection: Operation not permitted
#9 18.61   Installing : elfutils-default-yama-scope-0.176-2.amzn2.noarch           78/88 
#9 18.81   Installing : 1:dbus-1.10.24-7.amzn2.x86_64                              79/88 
#9 18.90   Installing : elfutils-0.176-2.amzn2.x86_64                              80/88 
#9 19.09   Installing : openssh-7.4p1-22.amzn2.0.1.x86_64                          81/88 
#9 19.27   Installing : openssh-clients-7.4p1-22.amzn2.0.1.x86_64                  82/88 
#9 20.54   Installing : git-core-2.32.0-1.amzn2.0.1.x86_64                         83/88 
... skipping 55 lines ...
#9 22.73   Verifying  : perl-File-Temp-0.23.01-3.amzn2.noarch                      51/88 
#9 22.75   Verifying  : perl-srpm-macros-1-8.amzn2.0.1.noarch                      52/88 
#9 22.77   Verifying  : pam-1.1.8-23.amzn2.0.1.x86_64                              53/88 
#9 22.80   Verifying  : xz-5.2.2-1.amzn2.0.3.x86_64                                54/88 
#9 22.82   Verifying  : ustr-1.0.4-16.amzn2.0.3.x86_64                             55/88 
#9 22.83   Verifying  : less-458-9.amzn2.0.2.x86_64                                56/88 
#9 22.85   Verifying  : 1:perl-Error-0.17020-2.amzn2.noarch                        57/88 
#9 22.87   Verifying  : perl-Pod-Usage-1.63-3.amzn2.noarch                         58/88 
#9 22.89   Verifying  : unzip-6.0-43.amzn2.x86_64                                  59/88 
#9 22.91   Verifying  : 1:perl-parent-0.225-244.amzn2.0.1.noarch                   60/88 
#9 22.95   Verifying  : perl-Pod-Perldoc-3.20-4.amzn2.noarch                       61/88 
#9 22.97   Verifying  : 2:tar-1.26-35.amzn2.x86_64                                 62/88 
#9 22.99   Verifying  : zip-3.0-11.amzn2.0.2.x86_64                                63/88 
... skipping 69 lines ...
#9 23.65   pam.x86_64 0:1.1.8-23.amzn2.0.1                                               
#9 23.65   patch.x86_64 0:2.7.1-12.amzn2.0.2                                             
#9 23.65   pcre2.x86_64 0:10.23-2.amzn2.0.2                                              
#9 23.65   perl.x86_64 4:5.16.3-299.amzn2.0.1                                            
#9 23.65   perl-Carp.noarch 0:1.26-244.amzn2                                             
#9 23.65   perl-Encode.x86_64 0:2.51-7.amzn2.0.2                                         
#9 23.65   perl-Error.noarch 1:0.17020-2.amzn2                                           
#9 23.65   perl-Exporter.noarch 0:5.68-3.amzn2                                           
#9 23.65   perl-File-Path.noarch 0:2.09-2.amzn2                                          
#9 23.65   perl-File-Temp.noarch 0:0.23.01-3.amzn2                                       
#9 23.65   perl-Filter.x86_64 0:1.49-3.amzn2.0.2                                         
#9 23.66   perl-Getopt-Long.noarch 0:2.40-3.amzn2                                        
#9 23.66   perl-Git.noarch 0:2.32.0-1.amzn2.0.1                                          
... skipping 559 lines ...
|        S.... +..|
|          o +++ o|
|          .+.X =o|
|          .+B *.O|
|          .oo==*+|
+----[SHA256]-----+
Error: unable to describe control plane "test-cluster-11979-k8s-local": operation error EKS: DescribeCluster, https response error StatusCode: 404, RequestID: 706ed582-a756-4ce7-8f13-78dc95f56906, ResourceNotFoundException: No cluster found for name: test-cluster-11979-k8s-local.
###
## Creating cluster test-cluster-11979-k8s-local with /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-11979.k8s.local.eksctl.yaml (dry run)
#
###
## Patching cluster test-cluster-11979-k8s-local with ./hack/eksctl-patch.yaml
#
... skipping 126 lines ...
Random Seed: 1656134432 - 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-11979-k8s-local"
error getting kops node security group id: no security groups found with filters [{
    Name: "tag:Name",
    Values: ["nodes.test-cluster-11979-k8s-local"]
  }]
error getting kops node subnet ids: no subnets found with filters [{
    Name: "tag-key",
    Values: ["kubernetes.io/cluster/test-cluster-11979-k8s-local"]
  }]
STEP: Created EFS filesystem "fs-033ceb336e5e13716" in region "us-west-2" for cluster "test-cluster-11979-k8s-local"


... skipping 246 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
------------------------------
... skipping 62 lines ...
Jun 25 05:23:17.420: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jun 25 05:23:17.490: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.comdvnm4] to have phase Bound
Jun 25 05:23:17.553: INFO: PersistentVolumeClaim efs.csi.aws.comdvnm4 found but phase is Pending instead of Bound.
Jun 25 05:23:19.617: INFO: PersistentVolumeClaim efs.csi.aws.comdvnm4 found and phase=Bound (2.127162686s)
STEP: Creating pod pod-subpath-test-dynamicpv-76sp
STEP: Creating a pod to test subpath
Jun 25 05:23:19.861: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-76sp" in namespace "provisioning-495" to be "Succeeded or Failed"
Jun 25 05:23:19.927: INFO: Pod "pod-subpath-test-dynamicpv-76sp": Phase="Pending", Reason="", readiness=false. Elapsed: 65.883244ms
Jun 25 05:23:21.992: INFO: Pod "pod-subpath-test-dynamicpv-76sp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.130901999s
Jun 25 05:23:24.056: INFO: Pod "pod-subpath-test-dynamicpv-76sp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.195073928s
Jun 25 05:23:26.120: INFO: Pod "pod-subpath-test-dynamicpv-76sp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.259415286s
Jun 25 05:23:28.184: INFO: Pod "pod-subpath-test-dynamicpv-76sp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.323094994s
Jun 25 05:23:30.247: INFO: Pod "pod-subpath-test-dynamicpv-76sp": Phase="Pending", Reason="", readiness=false. Elapsed: 10.38666772s
Jun 25 05:23:32.311: INFO: Pod "pod-subpath-test-dynamicpv-76sp": Phase="Pending", Reason="", readiness=false. Elapsed: 12.449788624s
Jun 25 05:23:34.376: INFO: Pod "pod-subpath-test-dynamicpv-76sp": Phase="Pending", Reason="", readiness=false. Elapsed: 14.515627551s
Jun 25 05:23:36.480: INFO: Pod "pod-subpath-test-dynamicpv-76sp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.618773816s
STEP: Saw pod success
Jun 25 05:23:36.480: INFO: Pod "pod-subpath-test-dynamicpv-76sp" satisfied condition "Succeeded or Failed"
Jun 25 05:23:36.541: INFO: Trying to get logs from node ip-192-168-34-49.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-76sp container test-container-volume-dynamicpv-76sp: <nil>
STEP: delete the pod
Jun 25 05:23:36.699: INFO: Waiting for pod pod-subpath-test-dynamicpv-76sp to disappear
Jun 25 05:23:36.761: INFO: Pod pod-subpath-test-dynamicpv-76sp no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-76sp
Jun 25 05:23:36.761: INFO: Deleting pod "pod-subpath-test-dynamicpv-76sp" in namespace "provisioning-495"
... skipping 98 lines ...
Jun 25 05:23:15.309: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jun 25 05:23:15.392: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.com7s6j8] to have phase Bound
Jun 25 05:23:15.457: INFO: PersistentVolumeClaim efs.csi.aws.com7s6j8 found but phase is Pending instead of Bound.
Jun 25 05:23:17.523: INFO: PersistentVolumeClaim efs.csi.aws.com7s6j8 found and phase=Bound (2.130564191s)
STEP: Creating pod pod-subpath-test-dynamicpv-q8kn
STEP: Creating a pod to test subpath
Jun 25 05:23:17.781: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-q8kn" in namespace "provisioning-4425" to be "Succeeded or Failed"
Jun 25 05:23:17.863: INFO: Pod "pod-subpath-test-dynamicpv-q8kn": Phase="Pending", Reason="", readiness=false. Elapsed: 81.406607ms
Jun 25 05:23:19.931: INFO: Pod "pod-subpath-test-dynamicpv-q8kn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.149288492s
Jun 25 05:23:22.009: INFO: Pod "pod-subpath-test-dynamicpv-q8kn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.227504789s
Jun 25 05:23:24.076: INFO: Pod "pod-subpath-test-dynamicpv-q8kn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.29468305s
Jun 25 05:23:26.142: INFO: Pod "pod-subpath-test-dynamicpv-q8kn": Phase="Pending", Reason="", readiness=false. Elapsed: 8.36020971s
Jun 25 05:23:28.207: INFO: Pod "pod-subpath-test-dynamicpv-q8kn": Phase="Pending", Reason="", readiness=false. Elapsed: 10.42541152s
Jun 25 05:23:30.278: INFO: Pod "pod-subpath-test-dynamicpv-q8kn": Phase="Pending", Reason="", readiness=false. Elapsed: 12.497102969s
Jun 25 05:23:32.345: INFO: Pod "pod-subpath-test-dynamicpv-q8kn": Phase="Pending", Reason="", readiness=false. Elapsed: 14.563912094s
Jun 25 05:23:34.412: INFO: Pod "pod-subpath-test-dynamicpv-q8kn": Phase="Pending", Reason="", readiness=false. Elapsed: 16.630656058s
Jun 25 05:23:36.478: INFO: Pod "pod-subpath-test-dynamicpv-q8kn": Phase="Pending", Reason="", readiness=false. Elapsed: 18.696869001s
Jun 25 05:23:38.544: INFO: Pod "pod-subpath-test-dynamicpv-q8kn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.762380717s
STEP: Saw pod success
Jun 25 05:23:38.544: INFO: Pod "pod-subpath-test-dynamicpv-q8kn" satisfied condition "Succeeded or Failed"
Jun 25 05:23:38.610: INFO: Trying to get logs from node ip-192-168-1-5.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-q8kn container test-container-volume-dynamicpv-q8kn: <nil>
STEP: delete the pod
Jun 25 05:23:38.817: INFO: Waiting for pod pod-subpath-test-dynamicpv-q8kn to disappear
Jun 25 05:23:38.882: INFO: Pod pod-subpath-test-dynamicpv-q8kn no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-q8kn
Jun 25 05:23:38.882: INFO: Deleting pod "pod-subpath-test-dynamicpv-q8kn" in namespace "provisioning-4425"
... skipping 126 lines ...
Jun 25 05:23:22.005: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jun 25 05:23:22.080: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.comr2rqh] to have phase Bound
Jun 25 05:23:22.146: INFO: PersistentVolumeClaim efs.csi.aws.comr2rqh found but phase is Pending instead of Bound.
Jun 25 05:23:24.213: INFO: PersistentVolumeClaim efs.csi.aws.comr2rqh found and phase=Bound (2.133418512s)
STEP: Creating pod pod-subpath-test-dynamicpv-n6zz
STEP: Creating a pod to test atomic-volume-subpath
Jun 25 05:23:24.417: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-n6zz" in namespace "provisioning-2888" to be "Succeeded or Failed"
Jun 25 05:23:24.482: INFO: Pod "pod-subpath-test-dynamicpv-n6zz": Phase="Pending", Reason="", readiness=false. Elapsed: 65.328561ms
Jun 25 05:23:26.549: INFO: Pod "pod-subpath-test-dynamicpv-n6zz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.131996871s
Jun 25 05:23:28.615: INFO: Pod "pod-subpath-test-dynamicpv-n6zz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.198371418s
Jun 25 05:23:30.683: INFO: Pod "pod-subpath-test-dynamicpv-n6zz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.265506075s
Jun 25 05:23:32.749: INFO: Pod "pod-subpath-test-dynamicpv-n6zz": Phase="Pending", Reason="", readiness=false. Elapsed: 8.331943307s
Jun 25 05:23:34.815: INFO: Pod "pod-subpath-test-dynamicpv-n6zz": Phase="Running", Reason="", readiness=true. Elapsed: 10.398343361s
... skipping 6 lines ...
Jun 25 05:23:49.280: INFO: Pod "pod-subpath-test-dynamicpv-n6zz": Phase="Running", Reason="", readiness=true. Elapsed: 24.862753055s
Jun 25 05:23:51.347: INFO: Pod "pod-subpath-test-dynamicpv-n6zz": Phase="Running", Reason="", readiness=true. Elapsed: 26.929567039s
Jun 25 05:23:53.417: INFO: Pod "pod-subpath-test-dynamicpv-n6zz": Phase="Running", Reason="", readiness=true. Elapsed: 28.999856424s
Jun 25 05:23:55.483: INFO: Pod "pod-subpath-test-dynamicpv-n6zz": Phase="Running", Reason="", readiness=false. Elapsed: 31.065831712s
Jun 25 05:23:57.550: INFO: Pod "pod-subpath-test-dynamicpv-n6zz": Phase="Succeeded", Reason="", readiness=false. Elapsed: 33.133153444s
STEP: Saw pod success
Jun 25 05:23:57.550: INFO: Pod "pod-subpath-test-dynamicpv-n6zz" satisfied condition "Succeeded or Failed"
Jun 25 05:23:57.615: INFO: Trying to get logs from node ip-192-168-86-17.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-n6zz container test-container-subpath-dynamicpv-n6zz: <nil>
STEP: delete the pod
Jun 25 05:23:57.765: INFO: Waiting for pod pod-subpath-test-dynamicpv-n6zz to disappear
Jun 25 05:23:57.829: INFO: Pod pod-subpath-test-dynamicpv-n6zz no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-n6zz
Jun 25 05:23:57.829: INFO: Deleting pod "pod-subpath-test-dynamicpv-n6zz" in namespace "provisioning-2888"
... skipping 23 lines ...
    [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 support file as subpath [LinuxOnly]
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:230
------------------------------
[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 05:23:47.897: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-11979.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-8287
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 05:23:49.037: INFO: Creating resource for dynamic PV
Jun 25 05:23:49.037: 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 05:23:49.226: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jun 25 05:23:49.297: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.comb2crv] to have phase Bound
Jun 25 05:23:49.360: INFO: PersistentVolumeClaim efs.csi.aws.comb2crv found but phase is Pending instead of Bound.
Jun 25 05:23:51.425: INFO: PersistentVolumeClaim efs.csi.aws.comb2crv found and phase=Bound (2.128393521s)
STEP: Creating pod pod-subpath-test-dynamicpv-2fpn
STEP: Checking for subpath error in container status
Jun 25 05:23:55.760: INFO: Deleting pod "pod-subpath-test-dynamicpv-2fpn" in namespace "provisioning-8287"
Jun 25 05:23:55.831: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-2fpn" to be fully deleted
STEP: Deleting pod
Jun 25 05:23:57.963: INFO: Deleting pod "pod-subpath-test-dynamicpv-2fpn" in namespace "provisioning-8287"
STEP: Deleting pvc
Jun 25 05:23:58.027: INFO: Deleting PersistentVolumeClaim "efs.csi.aws.comb2crv"
... 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 92 lines ...
Jun 25 05:23:46.013: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jun 25 05:23:46.087: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.comn7rvt] to have phase Bound
Jun 25 05:23:46.153: INFO: PersistentVolumeClaim efs.csi.aws.comn7rvt found but phase is Pending instead of Bound.
Jun 25 05:23:48.217: INFO: PersistentVolumeClaim efs.csi.aws.comn7rvt found and phase=Bound (2.130043184s)
STEP: Creating pod pod-subpath-test-dynamicpv-8488
STEP: Creating a pod to test subpath
Jun 25 05:23:48.472: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-8488" in namespace "provisioning-5356" to be "Succeeded or Failed"
Jun 25 05:23:48.537: INFO: Pod "pod-subpath-test-dynamicpv-8488": Phase="Pending", Reason="", readiness=false. Elapsed: 64.112818ms
Jun 25 05:23:50.603: INFO: Pod "pod-subpath-test-dynamicpv-8488": Phase="Pending", Reason="", readiness=false. Elapsed: 2.130321643s
Jun 25 05:23:52.668: INFO: Pod "pod-subpath-test-dynamicpv-8488": Phase="Pending", Reason="", readiness=false. Elapsed: 4.195295516s
Jun 25 05:23:54.734: INFO: Pod "pod-subpath-test-dynamicpv-8488": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.261133074s
STEP: Saw pod success
Jun 25 05:23:54.734: INFO: Pod "pod-subpath-test-dynamicpv-8488" satisfied condition "Succeeded or Failed"
Jun 25 05:23:54.798: INFO: Trying to get logs from node ip-192-168-1-5.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-8488 container test-container-subpath-dynamicpv-8488: <nil>
STEP: delete the pod
Jun 25 05:23:55.001: INFO: Waiting for pod pod-subpath-test-dynamicpv-8488 to disappear
Jun 25 05:23:55.064: INFO: Pod pod-subpath-test-dynamicpv-8488 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-8488
Jun 25 05:23:55.064: INFO: Deleting pod "pod-subpath-test-dynamicpv-8488" in namespace "provisioning-5356"
STEP: Creating pod pod-subpath-test-dynamicpv-8488
STEP: Creating a pod to test subpath
Jun 25 05:23:55.202: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-8488" in namespace "provisioning-5356" to be "Succeeded or Failed"
Jun 25 05:23:55.265: INFO: Pod "pod-subpath-test-dynamicpv-8488": Phase="Pending", Reason="", readiness=false. Elapsed: 63.506662ms
Jun 25 05:23:57.330: INFO: Pod "pod-subpath-test-dynamicpv-8488": Phase="Pending", Reason="", readiness=false. Elapsed: 2.127890549s
Jun 25 05:23:59.395: INFO: Pod "pod-subpath-test-dynamicpv-8488": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.19291885s
STEP: Saw pod success
Jun 25 05:23:59.395: INFO: Pod "pod-subpath-test-dynamicpv-8488" satisfied condition "Succeeded or Failed"
Jun 25 05:23:59.461: INFO: Trying to get logs from node ip-192-168-1-5.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-8488 container test-container-subpath-dynamicpv-8488: <nil>
STEP: delete the pod
Jun 25 05:23:59.611: INFO: Waiting for pod pod-subpath-test-dynamicpv-8488 to disappear
Jun 25 05:23:59.676: INFO: Pod pod-subpath-test-dynamicpv-8488 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-8488
Jun 25 05:23:59.676: INFO: Deleting pod "pod-subpath-test-dynamicpv-8488" in namespace "provisioning-5356"
... skipping 219 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 710 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 05:24:57.413: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-11979.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-6121
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 05:24:58.365: 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 05:24:58.365: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-6121" 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 96 lines ...
Jun 25 05:24:48.558: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jun 25 05:24:48.628: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.comrzldg] to have phase Bound
Jun 25 05:24:48.693: INFO: PersistentVolumeClaim efs.csi.aws.comrzldg found but phase is Pending instead of Bound.
Jun 25 05:24:50.759: INFO: PersistentVolumeClaim efs.csi.aws.comrzldg found and phase=Bound (2.13073761s)
STEP: Creating pod pod-subpath-test-dynamicpv-6hzq
STEP: Creating a pod to test multi_subpath
Jun 25 05:24:50.984: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-6hzq" in namespace "provisioning-9002" to be "Succeeded or Failed"
Jun 25 05:24:51.078: INFO: Pod "pod-subpath-test-dynamicpv-6hzq": Phase="Pending", Reason="", readiness=false. Elapsed: 93.330586ms
Jun 25 05:24:53.159: INFO: Pod "pod-subpath-test-dynamicpv-6hzq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.174693267s
Jun 25 05:24:55.225: INFO: Pod "pod-subpath-test-dynamicpv-6hzq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.241179201s
Jun 25 05:24:57.292: INFO: Pod "pod-subpath-test-dynamicpv-6hzq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.307595789s
STEP: Saw pod success
Jun 25 05:24:57.292: INFO: Pod "pod-subpath-test-dynamicpv-6hzq" satisfied condition "Succeeded or Failed"
Jun 25 05:24:57.357: INFO: Trying to get logs from node ip-192-168-1-5.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-6hzq container test-container-subpath-dynamicpv-6hzq: <nil>
STEP: delete the pod
Jun 25 05:24:57.507: INFO: Waiting for pod pod-subpath-test-dynamicpv-6hzq to disappear
Jun 25 05:24:57.575: INFO: Pod pod-subpath-test-dynamicpv-6hzq no longer exists
STEP: Deleting pod
Jun 25 05:24:57.575: INFO: Deleting pod "pod-subpath-test-dynamicpv-6hzq" in namespace "provisioning-9002"
... skipping 57 lines ...
Jun 25 05:25:09.726: INFO: PersistentVolumeClaim pvc-dscnm found but phase is Pending instead of Bound.
Jun 25 05:25:11.791: INFO: PersistentVolumeClaim pvc-dscnm found and phase=Bound (6.258652573s)
Jun 25 05:25:11.791: INFO: Waiting up to 3m0s for PersistentVolume efs.csi.aws.com-7zqc8 to have phase Bound
Jun 25 05:25:11.854: INFO: PersistentVolume efs.csi.aws.com-7zqc8 found and phase=Bound (62.549617ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-fdrb
STEP: Creating a pod to test exec-volume-test
Jun 25 05:25:12.054: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-fdrb" in namespace "volume-1137" to be "Succeeded or Failed"
Jun 25 05:25:12.116: INFO: Pod "exec-volume-test-preprovisionedpv-fdrb": Phase="Pending", Reason="", readiness=false. Elapsed: 62.616725ms
Jun 25 05:25:14.180: INFO: Pod "exec-volume-test-preprovisionedpv-fdrb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.12674421s
Jun 25 05:25:16.246: INFO: Pod "exec-volume-test-preprovisionedpv-fdrb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.192033838s
Jun 25 05:25:18.310: INFO: Pod "exec-volume-test-preprovisionedpv-fdrb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.256382198s
STEP: Saw pod success
Jun 25 05:25:18.310: INFO: Pod "exec-volume-test-preprovisionedpv-fdrb" satisfied condition "Succeeded or Failed"
Jun 25 05:25:18.373: INFO: Trying to get logs from node ip-192-168-1-5.us-west-2.compute.internal pod exec-volume-test-preprovisionedpv-fdrb container exec-container-preprovisionedpv-fdrb: <nil>
STEP: delete the pod
Jun 25 05:25:18.567: INFO: Waiting for pod exec-volume-test-preprovisionedpv-fdrb to disappear
Jun 25 05:25:18.629: INFO: Pod exec-volume-test-preprovisionedpv-fdrb no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-fdrb
Jun 25 05:25:18.629: INFO: Deleting pod "exec-volume-test-preprovisionedpv-fdrb" in namespace "volume-1137"
... skipping 34 lines ...
STEP: Binding the e2e-test-privileged-psp PodSecurityPolicy to the default service account in efs-2451
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 05:24:27.295: INFO: Waiting up to 5m0s for pod "pvc-tester-w4z75" in namespace "efs-2451" to be "Succeeded or Failed"
Jun 25 05:24:27.361: INFO: Pod "pvc-tester-w4z75": Phase="Pending", Reason="", readiness=false. Elapsed: 66.612411ms
Jun 25 05:24:29.431: INFO: Pod "pvc-tester-w4z75": Phase="Pending", Reason="", readiness=false. Elapsed: 2.13605426s
Jun 25 05:24:31.497: INFO: Pod "pvc-tester-w4z75": Phase="Pending", Reason="", readiness=false. Elapsed: 4.202472398s
Jun 25 05:24:33.564: INFO: Pod "pvc-tester-w4z75": Phase="Pending", Reason="", readiness=false. Elapsed: 6.26978025s
Jun 25 05:24:35.632: INFO: Pod "pvc-tester-w4z75": Phase="Pending", Reason="", readiness=false. Elapsed: 8.336889048s
Jun 25 05:24:37.699: INFO: Pod "pvc-tester-w4z75": Phase="Pending", Reason="", readiness=false. Elapsed: 10.403823037s
... skipping 8 lines ...
Jun 25 05:24:56.330: INFO: Pod "pvc-tester-w4z75": Phase="Pending", Reason="", readiness=false. Elapsed: 29.035544411s
Jun 25 05:24:58.397: INFO: Pod "pvc-tester-w4z75": Phase="Pending", Reason="", readiness=false. Elapsed: 31.102234058s
Jun 25 05:25:00.466: INFO: Pod "pvc-tester-w4z75": Phase="Pending", Reason="", readiness=false. Elapsed: 33.171405729s
Jun 25 05:25:02.534: INFO: Pod "pvc-tester-w4z75": Phase="Pending", Reason="", readiness=false. Elapsed: 35.23923202s
Jun 25 05:25:04.602: INFO: Pod "pvc-tester-w4z75": Phase="Succeeded", Reason="", readiness=false. Elapsed: 37.307172806s
STEP: Saw pod success
Jun 25 05:25:04.602: INFO: Pod "pvc-tester-w4z75" 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 05:25:19.322: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
... skipping 287 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 416 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 97 lines ...

      Driver efs.csi.aws.com doesn't support ext4 -- 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 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 05:25:50.500: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-11979.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-4208
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 05:25:51.634: INFO: Creating resource for dynamic PV
Jun 25 05:25:51.634: 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 05:25:51.840: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jun 25 05:25:51.912: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.com4wgrd] to have phase Bound
Jun 25 05:25:51.976: INFO: PersistentVolumeClaim efs.csi.aws.com4wgrd found but phase is Pending instead of Bound.
Jun 25 05:25:54.042: INFO: PersistentVolumeClaim efs.csi.aws.com4wgrd found and phase=Bound (2.130016172s)
STEP: Creating pod pod-subpath-test-dynamicpv-p9jz
STEP: Checking for subpath error in container status
Jun 25 05:25:58.381: INFO: Deleting pod "pod-subpath-test-dynamicpv-p9jz" in namespace "provisioning-4208"
Jun 25 05:25:58.453: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-p9jz" to be fully deleted
STEP: Deleting pod
Jun 25 05:26:00.585: INFO: Deleting pod "pod-subpath-test-dynamicpv-p9jz" in namespace "provisioning-4208"
STEP: Deleting pvc
Jun 25 05:26:00.653: INFO: Deleting PersistentVolumeClaim "efs.csi.aws.com4wgrd"
... 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
------------------------------
[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 05:26:07.266: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-11979.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-4415
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 05:26:08.454: INFO: Creating resource for dynamic PV
Jun 25 05:26:08.454: 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 05:26:08.644: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jun 25 05:26:08.715: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.combrrn6] to have phase Bound
Jun 25 05:26:08.782: INFO: PersistentVolumeClaim efs.csi.aws.combrrn6 found but phase is Pending instead of Bound.
Jun 25 05:26:10.849: INFO: PersistentVolumeClaim efs.csi.aws.combrrn6 found and phase=Bound (2.133026648s)
STEP: Creating pod pod-subpath-test-dynamicpv-kfnl
STEP: Checking for subpath error in container status
Jun 25 05:26:15.194: INFO: Deleting pod "pod-subpath-test-dynamicpv-kfnl" in namespace "provisioning-4415"
Jun 25 05:26:15.269: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-kfnl" to be fully deleted
STEP: Deleting pod
Jun 25 05:26:17.400: INFO: Deleting pod "pod-subpath-test-dynamicpv-kfnl" in namespace "provisioning-4415"
STEP: Deleting pvc
Jun 25 05:26:17.466: INFO: Deleting PersistentVolumeClaim "efs.csi.aws.combrrn6"
... 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 51 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 116 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 05:26:29.916: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-11979.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-9103
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 05:26:30.852: 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 05:26:30.853: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-9103" 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 358 lines ...
Jun 25 05:27:21.093: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jun 25 05:27:21.166: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.compxwt7] to have phase Bound
Jun 25 05:27:21.230: INFO: PersistentVolumeClaim efs.csi.aws.compxwt7 found but phase is Pending instead of Bound.
Jun 25 05:27:23.294: INFO: PersistentVolumeClaim efs.csi.aws.compxwt7 found and phase=Bound (2.128308209s)
STEP: Creating pod exec-volume-test-dynamicpv-7j4r
STEP: Creating a pod to test exec-volume-test
Jun 25 05:27:23.507: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-7j4r" in namespace "volume-1181" to be "Succeeded or Failed"
Jun 25 05:27:23.572: INFO: Pod "exec-volume-test-dynamicpv-7j4r": Phase="Pending", Reason="", readiness=false. Elapsed: 64.700701ms
Jun 25 05:27:25.636: INFO: Pod "exec-volume-test-dynamicpv-7j4r": Phase="Running", Reason="", readiness=true. Elapsed: 2.129010677s
Jun 25 05:27:27.700: INFO: Pod "exec-volume-test-dynamicpv-7j4r": Phase="Running", Reason="", readiness=false. Elapsed: 4.193241713s
Jun 25 05:27:29.766: INFO: Pod "exec-volume-test-dynamicpv-7j4r": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.258491777s
STEP: Saw pod success
Jun 25 05:27:29.766: INFO: Pod "exec-volume-test-dynamicpv-7j4r" satisfied condition "Succeeded or Failed"
Jun 25 05:27:29.829: INFO: Trying to get logs from node ip-192-168-1-5.us-west-2.compute.internal pod exec-volume-test-dynamicpv-7j4r container exec-container-dynamicpv-7j4r: <nil>
STEP: delete the pod
Jun 25 05:27:30.029: INFO: Waiting for pod exec-volume-test-dynamicpv-7j4r to disappear
Jun 25 05:27:30.092: INFO: Pod exec-volume-test-dynamicpv-7j4r no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-7j4r
Jun 25 05:27:30.092: INFO: Deleting pod "exec-volume-test-dynamicpv-7j4r" in namespace "volume-1181"
... 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: 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 293 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 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: 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 05:25:36.028: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-11979.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-5753
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 05:25:37.475: INFO: Waiting for PV pvjp2tb to bind to PVC pvc-lqwfv
Jun 25 05:25:37.475: INFO: Waiting up to timeout=3m0s for PersistentVolumeClaims [pvc-lqwfv] to have phase Bound
Jun 25 05:25:37.538: INFO: PersistentVolumeClaim pvc-lqwfv found and phase=Bound (63.225252ms)
... skipping 20 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 41 lines ...
STEP: Binding the e2e-test-privileged-psp PodSecurityPolicy to the default service account in efs-7726
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-7726" and run "mount && mount | grep /mnt/volume1 | grep 127.0.0.1"
Jun 25 05:27:40.290: INFO: Waiting up to 5m0s for pod "pvc-tester-5zv8t" in namespace "efs-7726" to be "Succeeded or Failed"
Jun 25 05:27:40.354: INFO: Pod "pvc-tester-5zv8t": Phase="Pending", Reason="", readiness=false. Elapsed: 63.646458ms
Jun 25 05:27:42.419: INFO: Pod "pvc-tester-5zv8t": Phase="Pending", Reason="", readiness=false. Elapsed: 2.128947319s
Jun 25 05:27:44.483: INFO: Pod "pvc-tester-5zv8t": Phase="Pending", Reason="", readiness=false. Elapsed: 4.192831121s
Jun 25 05:27:46.556: INFO: Pod "pvc-tester-5zv8t": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.265778731s
STEP: Saw pod success
Jun 25 05:27:46.556: INFO: Pod "pvc-tester-5zv8t" satisfied condition "Succeeded or Failed"
Jun 25 05:27:46.639: INFO: pod "pvc-tester-5zv8t" logs:
 overlay on / type overlay (rw,relatime,lowerdir=/var/lib/docker/overlay2/l/N2K3PNFPXVG2QAHUKW3DRQYRCT:/var/lib/docker/overlay2/l/UPJYWUSTJFBNPMDDC6N66JDGIP,upperdir=/var/lib/docker/overlay2/c69610fee6e37d41f1fb8d11780de5582b559d673005e28036c0f18f159cae6d/diff,workdir=/var/lib/docker/overlay2/c69610fee6e37d41f1fb8d11780de5582b559d673005e28036c0f18f159cae6d/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 257 lines ...
Jun 25 05:27:47.302: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jun 25 05:27:47.376: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.comzjt6p] to have phase Bound
Jun 25 05:27:47.441: INFO: PersistentVolumeClaim efs.csi.aws.comzjt6p found but phase is Pending instead of Bound.
Jun 25 05:27:49.506: INFO: PersistentVolumeClaim efs.csi.aws.comzjt6p found and phase=Bound (2.130051377s)
STEP: Creating pod pod-subpath-test-dynamicpv-bnp5
STEP: Creating a pod to test subpath
Jun 25 05:27:49.760: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-bnp5" in namespace "provisioning-8721" to be "Succeeded or Failed"
Jun 25 05:27:49.824: INFO: Pod "pod-subpath-test-dynamicpv-bnp5": Phase="Pending", Reason="", readiness=false. Elapsed: 63.673642ms
Jun 25 05:27:51.928: INFO: Pod "pod-subpath-test-dynamicpv-bnp5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.167804094s
Jun 25 05:27:53.997: INFO: Pod "pod-subpath-test-dynamicpv-bnp5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.237339958s
Jun 25 05:27:56.067: INFO: Pod "pod-subpath-test-dynamicpv-bnp5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.306917592s
STEP: Saw pod success
Jun 25 05:27:56.067: INFO: Pod "pod-subpath-test-dynamicpv-bnp5" satisfied condition "Succeeded or Failed"
Jun 25 05:27:56.132: INFO: Trying to get logs from node ip-192-168-1-5.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-bnp5 container test-container-subpath-dynamicpv-bnp5: <nil>
STEP: delete the pod
Jun 25 05:27:56.347: INFO: Waiting for pod pod-subpath-test-dynamicpv-bnp5 to disappear
Jun 25 05:27:56.413: INFO: Pod pod-subpath-test-dynamicpv-bnp5 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-bnp5
Jun 25 05:27:56.413: INFO: Deleting pod "pod-subpath-test-dynamicpv-bnp5" in namespace "provisioning-8721"
... skipping 124 lines ...
Jun 25 05:27:50.289: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jun 25 05:27:50.357: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.comcj2kn] to have phase Bound
Jun 25 05:27:50.419: INFO: PersistentVolumeClaim efs.csi.aws.comcj2kn found but phase is Pending instead of Bound.
Jun 25 05:27:52.504: INFO: PersistentVolumeClaim efs.csi.aws.comcj2kn found and phase=Bound (2.146134506s)
STEP: Creating pod pod-subpath-test-dynamicpv-rxdp
STEP: Creating a pod to test subpath
Jun 25 05:27:52.766: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-rxdp" in namespace "provisioning-3749" to be "Succeeded or Failed"
Jun 25 05:27:52.828: INFO: Pod "pod-subpath-test-dynamicpv-rxdp": Phase="Pending", Reason="", readiness=false. Elapsed: 62.483943ms
Jun 25 05:27:54.890: INFO: Pod "pod-subpath-test-dynamicpv-rxdp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.124447007s
Jun 25 05:27:56.953: INFO: Pod "pod-subpath-test-dynamicpv-rxdp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.187407655s
Jun 25 05:27:59.021: INFO: Pod "pod-subpath-test-dynamicpv-rxdp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.255491469s
STEP: Saw pod success
Jun 25 05:27:59.021: INFO: Pod "pod-subpath-test-dynamicpv-rxdp" satisfied condition "Succeeded or Failed"
Jun 25 05:27:59.084: INFO: Trying to get logs from node ip-192-168-1-5.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-rxdp container test-container-subpath-dynamicpv-rxdp: <nil>
STEP: delete the pod
Jun 25 05:27:59.285: INFO: Waiting for pod pod-subpath-test-dynamicpv-rxdp to disappear
Jun 25 05:27:59.347: INFO: Pod pod-subpath-test-dynamicpv-rxdp no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-rxdp
Jun 25 05:27:59.347: INFO: Deleting pod "pod-subpath-test-dynamicpv-rxdp" in namespace "provisioning-3749"
... skipping 159 lines ...

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

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/multivolume.go:82
------------------------------
[efs-csi] EFS CSI [Driver: efs.csi.aws.com] [Testpattern: Dynamic PV (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 05:23:19.150: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-11979.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-5089
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 05:28:20.801: INFO: Warning: did not get event about provisioing failed
STEP: Deleting pvc
Jun 25 05:28:20.932: INFO: Deleting PersistentVolumeClaim "pvc-kr4th"
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 05:28:21.226: 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
------------------------------
[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 75 lines ...
STEP: Binding the e2e-test-privileged-psp PodSecurityPolicy to the default service account in efs-2246
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-2246" and run "mount && mount | grep /mnt/volume1 | grep fs-033ceb336e5e13716"
Jun 25 05:27:53.518: INFO: Waiting up to 5m0s for pod "pvc-tester-d88cv" in namespace "efs-2246" to be "Succeeded or Failed"
Jun 25 05:27:53.587: INFO: Pod "pvc-tester-d88cv": Phase="Pending", Reason="", readiness=false. Elapsed: 68.57969ms
Jun 25 05:27:55.656: INFO: Pod "pvc-tester-d88cv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.138384631s
Jun 25 05:27:57.727: INFO: Pod "pvc-tester-d88cv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.209232394s
Jun 25 05:27:59.797: INFO: Pod "pvc-tester-d88cv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.27916816s
Jun 25 05:28:01.868: INFO: Pod "pvc-tester-d88cv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.349865181s
Jun 25 05:28:03.939: INFO: Pod "pvc-tester-d88cv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.42139926s
... skipping 5 lines ...
Jun 25 05:28:16.374: INFO: Pod "pvc-tester-d88cv": Phase="Pending", Reason="", readiness=false. Elapsed: 22.855553139s
Jun 25 05:28:18.444: INFO: Pod "pvc-tester-d88cv": Phase="Pending", Reason="", readiness=false. Elapsed: 24.925974627s
Jun 25 05:28:20.514: INFO: Pod "pvc-tester-d88cv": Phase="Pending", Reason="", readiness=false. Elapsed: 26.995441329s
Jun 25 05:28:22.582: INFO: Pod "pvc-tester-d88cv": Phase="Pending", Reason="", readiness=false. Elapsed: 29.063999137s
Jun 25 05:28:24.651: INFO: Pod "pvc-tester-d88cv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 31.133366458s
STEP: Saw pod success
Jun 25 05:28:24.651: INFO: Pod "pvc-tester-d88cv" satisfied condition "Succeeded or Failed"
Jun 25 05:28:24.734: INFO: pod "pvc-tester-d88cv" logs:
 overlay on / type overlay (rw,relatime,lowerdir=/var/lib/docker/overlay2/l/JSBDNONGNOUDYHU7UIONYJQGDL:/var/lib/docker/overlay2/l/CC3O4WPDVOXZBREUGA2TLWFHZZ,upperdir=/var/lib/docker/overlay2/23b53f6473e8ab77b28f8888972bbdd0acace8c4a68c129a86a46a86d9ff74d8/diff,workdir=/var/lib/docker/overlay2/23b53f6473e8ab77b28f8888972bbdd0acace8c4a68c129a86a46a86d9ff74d8/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 325 lines ...
Jun 25 05:28:30.646: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jun 25 05:28:30.730: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.com4vqtw] to have phase Bound
Jun 25 05:28:30.796: INFO: PersistentVolumeClaim efs.csi.aws.com4vqtw found but phase is Pending instead of Bound.
Jun 25 05:28:32.863: INFO: PersistentVolumeClaim efs.csi.aws.com4vqtw found and phase=Bound (2.132972143s)
STEP: Creating pod pod-subpath-test-dynamicpv-jh4z
STEP: Creating a pod to test subpath
Jun 25 05:28:33.085: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-jh4z" in namespace "provisioning-1988" to be "Succeeded or Failed"
Jun 25 05:28:33.153: INFO: Pod "pod-subpath-test-dynamicpv-jh4z": Phase="Pending", Reason="", readiness=false. Elapsed: 67.154641ms
Jun 25 05:28:35.220: INFO: Pod "pod-subpath-test-dynamicpv-jh4z": Phase="Pending", Reason="", readiness=false. Elapsed: 2.134070885s
Jun 25 05:28:37.287: INFO: Pod "pod-subpath-test-dynamicpv-jh4z": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.201434001s
STEP: Saw pod success
Jun 25 05:28:37.287: INFO: Pod "pod-subpath-test-dynamicpv-jh4z" satisfied condition "Succeeded or Failed"
Jun 25 05:28:37.353: INFO: Trying to get logs from node ip-192-168-86-17.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-jh4z container test-container-subpath-dynamicpv-jh4z: <nil>
STEP: delete the pod
Jun 25 05:28:37.515: INFO: Waiting for pod pod-subpath-test-dynamicpv-jh4z to disappear
Jun 25 05:28:37.580: INFO: Pod pod-subpath-test-dynamicpv-jh4z no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-jh4z
Jun 25 05:28:37.580: INFO: Deleting pod "pod-subpath-test-dynamicpv-jh4z" in namespace "provisioning-1988"
... skipping 23 lines ...
    [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 support existing single file [LinuxOnly]
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:219
------------------------------
[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 05:28:30.701: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-11979.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-9703
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 05:28:31.882: INFO: Creating resource for dynamic PV
Jun 25 05:28:31.883: 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 05:28:32.082: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jun 25 05:28:32.157: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.comt2snl] to have phase Bound
Jun 25 05:28:32.225: INFO: PersistentVolumeClaim efs.csi.aws.comt2snl found but phase is Pending instead of Bound.
Jun 25 05:28:34.293: INFO: PersistentVolumeClaim efs.csi.aws.comt2snl found and phase=Bound (2.135535739s)
STEP: Creating pod pod-subpath-test-dynamicpv-fg9q
STEP: Checking for subpath error in container status
Jun 25 05:28:38.637: INFO: Deleting pod "pod-subpath-test-dynamicpv-fg9q" in namespace "provisioning-9703"
Jun 25 05:28:38.711: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-fg9q" to be fully deleted
STEP: Deleting pod
Jun 25 05:28:40.845: INFO: Deleting pod "pod-subpath-test-dynamicpv-fg9q" in namespace "provisioning-9703"
STEP: Deleting pvc
Jun 25 05:28:40.914: INFO: Deleting PersistentVolumeClaim "efs.csi.aws.comt2snl"
... 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
------------------------------
[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 51 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 201 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 435 lines ...
STEP: creating a claim
Jun 25 05:28:45.716: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jun 25 05:28:45.791: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.comq6fqd] to have phase Bound
Jun 25 05:28:45.859: INFO: PersistentVolumeClaim efs.csi.aws.comq6fqd found but phase is Pending instead of Bound.
Jun 25 05:28:47.927: INFO: PersistentVolumeClaim efs.csi.aws.comq6fqd found and phase=Bound (2.136197186s)
STEP: Creating pod to format volume volume-prep-provisioning-8523
Jun 25 05:28:48.136: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-8523" in namespace "provisioning-8523" to be "Succeeded or Failed"
Jun 25 05:28:48.204: INFO: Pod "volume-prep-provisioning-8523": Phase="Pending", Reason="", readiness=false. Elapsed: 68.618993ms
Jun 25 05:28:50.273: INFO: Pod "volume-prep-provisioning-8523": Phase="Pending", Reason="", readiness=false. Elapsed: 2.137149042s
Jun 25 05:28:52.339: INFO: Pod "volume-prep-provisioning-8523": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.203556598s
STEP: Saw pod success
Jun 25 05:28:52.339: INFO: Pod "volume-prep-provisioning-8523" satisfied condition "Succeeded or Failed"
Jun 25 05:28:52.339: INFO: Deleting pod "volume-prep-provisioning-8523" in namespace "provisioning-8523"
Jun 25 05:28:52.419: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-8523" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-flng
STEP: Checking for subpath error in container status
Jun 25 05:28:54.692: INFO: Deleting pod "pod-subpath-test-dynamicpv-flng" in namespace "provisioning-8523"
Jun 25 05:28:54.826: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-flng" to be fully deleted
STEP: Deleting pod
Jun 25 05:28:56.964: INFO: Deleting pod "pod-subpath-test-dynamicpv-flng" in namespace "provisioning-8523"
STEP: Deleting pvc
Jun 25 05:28:57.028: INFO: Deleting PersistentVolumeClaim "efs.csi.aws.comq6fqd"
... skipping 81 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 05:29:03.680: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-11979.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-1002
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 05:29:04.600: 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 05:29:04.601: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-1002" 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 191 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 241 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 114 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 05:29:19.479: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-11979.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-9739
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 05:29:20.349: 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 05:29:20.349: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-9739" 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 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: 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 511 lines ...
STEP: Binding the e2e-test-privileged-psp PodSecurityPolicy to the default service account in efs-5427
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-5427" and run "mount && mount | grep /mnt/volume1 | grep 127.0.0.1"
Jun 25 05:29:08.462: INFO: Waiting up to 5m0s for pod "pvc-tester-5hkhg" in namespace "efs-5427" to be "Succeeded or Failed"
Jun 25 05:29:08.527: INFO: Pod "pvc-tester-5hkhg": Phase="Pending", Reason="", readiness=false. Elapsed: 65.207075ms
Jun 25 05:29:10.593: INFO: Pod "pvc-tester-5hkhg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.131328161s
Jun 25 05:29:12.660: INFO: Pod "pvc-tester-5hkhg": Phase="Pending", Reason="", readiness=false. Elapsed: 4.198863081s
Jun 25 05:29:14.726: INFO: Pod "pvc-tester-5hkhg": Phase="Pending", Reason="", readiness=false. Elapsed: 6.264368s
Jun 25 05:29:16.793: INFO: Pod "pvc-tester-5hkhg": Phase="Pending", Reason="", readiness=false. Elapsed: 8.331158283s
Jun 25 05:29:18.865: INFO: Pod "pvc-tester-5hkhg": Phase="Pending", Reason="", readiness=false. Elapsed: 10.403189719s
... skipping 6 lines ...
Jun 25 05:29:33.334: INFO: Pod "pvc-tester-5hkhg": Phase="Pending", Reason="", readiness=false. Elapsed: 24.872599129s
Jun 25 05:29:35.399: INFO: Pod "pvc-tester-5hkhg": Phase="Pending", Reason="", readiness=false. Elapsed: 26.937320271s
Jun 25 05:29:37.466: INFO: Pod "pvc-tester-5hkhg": Phase="Pending", Reason="", readiness=false. Elapsed: 29.00418114s
Jun 25 05:29:39.532: INFO: Pod "pvc-tester-5hkhg": Phase="Pending", Reason="", readiness=false. Elapsed: 31.070152974s
Jun 25 05:29:41.601: INFO: Pod "pvc-tester-5hkhg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 33.13893197s
STEP: Saw pod success
Jun 25 05:29:41.601: INFO: Pod "pvc-tester-5hkhg" satisfied condition "Succeeded or Failed"
Jun 25 05:29:41.672: INFO: pod "pvc-tester-5hkhg" logs:
 overlay on / type overlay (rw,relatime,lowerdir=/var/lib/docker/overlay2/l/V6L5NEKJ7DC6YGMKK6KFPAJCAX:/var/lib/docker/overlay2/l/CC3O4WPDVOXZBREUGA2TLWFHZZ,upperdir=/var/lib/docker/overlay2/46461049b4655c255223bbd83f070e214188eda0ff1d2a53d2e79aade0d5e833/diff,workdir=/var/lib/docker/overlay2/46461049b4655c255223bbd83f070e214188eda0ff1d2a53d2e79aade0d5e833/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 594 lines ...
------------------------------
STEP: Deleting EFS filesystem "fs-033ceb336e5e13716"
STEP: Deleted EFS filesystem "fs-033ceb336e5e13716"


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


Ginkgo ran 1 suite in 10m6.563057775s
Test Suite Passed
+ TEST_PASSED=0
+ set -e
... skipping 757 lines ...
I0625 05:23:20.026916       1 node.go:287] NodeGetCapabilities: called with args 
I0625 05:23:20.033811       1 node.go:287] NodeGetCapabilities: called with args 
I0625 05:23:20.034420       1 node.go:287] NodeGetCapabilities: called with args 
I0625 05:23:20.035375       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-033ceb336e5e13716::fsap-0458bd5373e8f313f" target_path:"/var/lib/kubelet/pods/c9378a49-716c-4ec5-8dcf-bb9964974666/volumes/kubernetes.io~csi/pvc-84542f17-72a1-4b27-9944-8249ad5e1e6e/mount" volume_capability:<mount:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > volume_context:<key:"storage.kubernetes.io/csiProvisionerIdentity" value:"1656134427254-8081-efs.csi.aws.com" > 
I0625 05:23:20.035864       1 node.go:175] NodePublishVolume: creating dir /var/lib/kubelet/pods/c9378a49-716c-4ec5-8dcf-bb9964974666/volumes/kubernetes.io~csi/pvc-84542f17-72a1-4b27-9944-8249ad5e1e6e/mount
I0625 05:23:20.035910       1 node.go:180] NodePublishVolume: mounting fs-033ceb336e5e13716:/ at /var/lib/kubelet/pods/c9378a49-716c-4ec5-8dcf-bb9964974666/volumes/kubernetes.io~csi/pvc-84542f17-72a1-4b27-9944-8249ad5e1e6e/mount with options [accesspoint=fsap-0458bd5373e8f313f tls]
E0625 05:23:20.426421       1 mount_linux.go:184] Mount failed: exit status 1
Mounting command: mount
Mounting arguments: -t efs -o accesspoint=fsap-0458bd5373e8f313f,tls fs-033ceb336e5e13716:/ /var/lib/kubelet/pods/c9378a49-716c-4ec5-8dcf-bb9964974666/volumes/kubernetes.io~csi/pvc-84542f17-72a1-4b27-9944-8249ad5e1e6e/mount
Output: Failed to resolve "fs-033ceb336e5e13716.efs.us-west-2.amazonaws.com". The file system mount target ip address cannot be found, please pass mount target ip address via mount options. 
User: arn:aws:sts::607362164682:assumed-role/eksctl-test-cluster-11979-k8s-loc-NodeInstanceRole-DG66K3FIGXKE/i-03e43110acf72ea4e is not authorized to perform: elasticfilesystem:DescribeMountTargets on the specified resource

E0625 05:23:20.426659       1 driver.go:107] GRPC error: rpc error: code = Internal desc = Could not mount "fs-033ceb336e5e13716:/" at "/var/lib/kubelet/pods/c9378a49-716c-4ec5-8dcf-bb9964974666/volumes/kubernetes.io~csi/pvc-84542f17-72a1-4b27-9944-8249ad5e1e6e/mount": mount failed: exit status 1
Mounting command: mount
Mounting arguments: -t efs -o accesspoint=fsap-0458bd5373e8f313f,tls fs-033ceb336e5e13716:/ /var/lib/kubelet/pods/c9378a49-716c-4ec5-8dcf-bb9964974666/volumes/kubernetes.io~csi/pvc-84542f17-72a1-4b27-9944-8249ad5e1e6e/mount
Output: Failed to resolve "fs-033ceb336e5e13716.efs.us-west-2.amazonaws.com". The file system mount target ip address cannot be found, please pass mount target ip address via mount options. 
User: arn:aws:sts::607362164682:assumed-role/eksctl-test-cluster-11979-k8s-loc-NodeInstanceRole-DG66K3FIGXKE/i-03e43110acf72ea4e is not authorized to perform: elasticfilesystem:DescribeMountTargets on the specified resource
I0625 05:23:20.932930       1 node.go:287] NodeGetCapabilities: called with args 
I0625 05:23:20.933570       1 node.go:287] NodeGetCapabilities: called with args 
I0625 05:23:20.934056       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-033ceb336e5e13716::fsap-0458bd5373e8f313f" target_path:"/var/lib/kubelet/pods/c9378a49-716c-4ec5-8dcf-bb9964974666/volumes/kubernetes.io~csi/pvc-84542f17-72a1-4b27-9944-8249ad5e1e6e/mount" volume_capability:<mount:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > volume_context:<key:"storage.kubernetes.io/csiProvisionerIdentity" value:"1656134427254-8081-efs.csi.aws.com" > 
I0625 05:23:20.934112       1 node.go:175] NodePublishVolume: creating dir /var/lib/kubelet/pods/c9378a49-716c-4ec5-8dcf-bb9964974666/volumes/kubernetes.io~csi/pvc-84542f17-72a1-4b27-9944-8249ad5e1e6e/mount
I0625 05:23:20.934163       1 node.go:180] NodePublishVolume: mounting fs-033ceb336e5e13716:/ at /var/lib/kubelet/pods/c9378a49-716c-4ec5-8dcf-bb9964974666/volumes/kubernetes.io~csi/pvc-84542f17-72a1-4b27-9944-8249ad5e1e6e/mount with options [accesspoint=fsap-0458bd5373e8f313f tls]
E0625 05:23:21.273399       1 mount_linux.go:184] Mount failed: exit status 1
Mounting command: mount
Mounting arguments: -t efs -o accesspoint=fsap-0458bd5373e8f313f,tls fs-033ceb336e5e13716:/ /var/lib/kubelet/pods/c9378a49-716c-4ec5-8dcf-bb9964974666/volumes/kubernetes.io~csi/pvc-84542f17-72a1-4b27-9944-8249ad5e1e6e/mount
Output: Failed to resolve "fs-033ceb336e5e13716.efs.us-west-2.amazonaws.com". The file system mount target ip address cannot be found, please pass mount target ip address via mount options. 
User: arn:aws:sts::607362164682:assumed-role/eksctl-test-cluster-11979-k8s-loc-NodeInstanceRole-DG66K3FIGXKE/i-03e43110acf72ea4e is not authorized to perform: elasticfilesystem:DescribeMountTargets on the specified resource

E0625 05:23:21.273560       1 driver.go:107] GRPC error: rpc error: code = Internal desc = Could not mount "fs-033ceb336e5e13716:/" at "/var/lib/kubelet/pods/c9378a49-716c-4ec5-8dcf-bb9964974666/volumes/kubernetes.io~csi/pvc-84542f17-72a1-4b27-9944-8249ad5e1e6e/mount": mount failed: exit status 1
Mounting command: mount
Mounting arguments: -t efs -o accesspoint=fsap-0458bd5373e8f313f,tls fs-033ceb336e5e13716:/ /var/lib/kubelet/pods/c9378a49-716c-4ec5-8dcf-bb9964974666/volumes/kubernetes.io~csi/pvc-84542f17-72a1-4b27-9944-8249ad5e1e6e/mount
Output: Failed to resolve "fs-033ceb336e5e13716.efs.us-west-2.amazonaws.com". The file system mount target ip address cannot be found, please pass mount target ip address via mount options. 
User: arn:aws:sts::607362164682:assumed-role/eksctl-test-cluster-11979-k8s-loc-NodeInstanceRole-DG66K3FIGXKE/i-03e43110acf72ea4e is not authorized to perform: elasticfilesystem:DescribeMountTargets on the specified resource
I0625 05:23:22.340975       1 node.go:287] NodeGetCapabilities: called with args 
I0625 05:23:22.341555       1 node.go:287] NodeGetCapabilities: called with args 
I0625 05:23:22.342145       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-033ceb336e5e13716::fsap-0458bd5373e8f313f" target_path:"/var/lib/kubelet/pods/c9378a49-716c-4ec5-8dcf-bb9964974666/volumes/kubernetes.io~csi/pvc-84542f17-72a1-4b27-9944-8249ad5e1e6e/mount" volume_capability:<mount:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > volume_context:<key:"storage.kubernetes.io/csiProvisionerIdentity" value:"1656134427254-8081-efs.csi.aws.com" > 
I0625 05:23:22.342198       1 node.go:175] NodePublishVolume: creating dir /var/lib/kubelet/pods/c9378a49-716c-4ec5-8dcf-bb9964974666/volumes/kubernetes.io~csi/pvc-84542f17-72a1-4b27-9944-8249ad5e1e6e/mount
I0625 05:23:22.342246       1 node.go:180] NodePublishVolume: mounting fs-033ceb336e5e13716:/ at /var/lib/kubelet/pods/c9378a49-716c-4ec5-8dcf-bb9964974666/volumes/kubernetes.io~csi/pvc-84542f17-72a1-4b27-9944-8249ad5e1e6e/mount with options [accesspoint=fsap-0458bd5373e8f313f tls]
E0625 05:23:22.667595       1 mount_linux.go:184] Mount failed: exit status 1
Mounting command: mount
Mounting arguments: -t efs -o accesspoint=fsap-0458bd5373e8f313f,tls fs-033ceb336e5e13716:/ /var/lib/kubelet/pods/c9378a49-716c-4ec5-8dcf-bb9964974666/volumes/kubernetes.io~csi/pvc-84542f17-72a1-4b27-9944-8249ad5e1e6e/mount
Output: Failed to resolve "fs-033ceb336e5e13716.efs.us-west-2.amazonaws.com". The file system mount target ip address cannot be found, please pass mount target ip address via mount options. 
User: arn:aws:sts::607362164682:assumed-role/eksctl-test-cluster-11979-k8s-loc-NodeInstanceRole-DG66K3FIGXKE/i-03e43110acf72ea4e is not authorized to perform: elasticfilesystem:DescribeMountTargets on the specified resource

E0625 05:23:22.667903       1 driver.go:107] GRPC error: rpc error: code = Internal desc = Could not mount "fs-033ceb336e5e13716:/" at "/var/lib/kubelet/pods/c9378a49-716c-4ec5-8dcf-bb9964974666/volumes/kubernetes.io~csi/pvc-84542f17-72a1-4b27-9944-8249ad5e1e6e/mount": mount failed: exit status 1
Mounting command: mount
Mounting arguments: -t efs -o accesspoint=fsap-0458bd5373e8f313f,tls fs-033ceb336e5e13716:/ /var/lib/kubelet/pods/c9378a49-716c-4ec5-8dcf-bb9964974666/volumes/kubernetes.io~csi/pvc-84542f17-72a1-4b27-9944-8249ad5e1e6e/mount
Output: Failed to resolve "fs-033ceb336e5e13716.efs.us-west-2.amazonaws.com". The file system mount target ip address cannot be found, please pass mount target ip address via mount options. 
User: arn:aws:sts::607362164682:assumed-role/eksctl-test-cluster-11979-k8s-loc-NodeInstanceRole-DG66K3FIGXKE/i-03e43110acf72ea4e is not authorized to perform: elasticfilesystem:DescribeMountTargets on the specified resource
I0625 05:23:24.755827       1 node.go:287] NodeGetCapabilities: called with args 
I0625 05:23:24.756624       1 node.go:287] NodeGetCapabilities: called with args 
I0625 05:23:24.757127       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-033ceb336e5e13716::fsap-0458bd5373e8f313f" target_path:"/var/lib/kubelet/pods/c9378a49-716c-4ec5-8dcf-bb9964974666/volumes/kubernetes.io~csi/pvc-84542f17-72a1-4b27-9944-8249ad5e1e6e/mount" volume_capability:<mount:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > volume_context:<key:"storage.kubernetes.io/csiProvisionerIdentity" value:"1656134427254-8081-efs.csi.aws.com" > 
I0625 05:23:24.757179       1 node.go:175] NodePublishVolume: creating dir /var/lib/kubelet/pods/c9378a49-716c-4ec5-8dcf-bb9964974666/volumes/kubernetes.io~csi/pvc-84542f17-72a1-4b27-9944-8249ad5e1e6e/mount
I0625 05:23:24.757228       1 node.go:180] NodePublishVolume: mounting fs-033ceb336e5e13716:/ at /var/lib/kubelet/pods/c9378a49-716c-4ec5-8dcf-bb9964974666/volumes/kubernetes.io~csi/pvc-84542f17-72a1-4b27-9944-8249ad5e1e6e/mount with options [accesspoint=fsap-0458bd5373e8f313f tls]
E0625 05:23:25.075593       1 mount_linux.go:184] Mount failed: exit status 1
Mounting command: mount
Mounting arguments: -t efs -o accesspoint=fsap-0458bd5373e8f313f,tls fs-033ceb336e5e13716:/ /var/lib/kubelet/pods/c9378a49-716c-4ec5-8dcf-bb9964974666/volumes/kubernetes.io~csi/pvc-84542f17-72a1-4b27-9944-8249ad5e1e6e/mount
Output: Failed to resolve "fs-033ceb336e5e13716.efs.us-west-2.amazonaws.com". The file system mount target ip address cannot be found, please pass mount target ip address via mount options. 
User: arn:aws:sts::607362164682:assumed-role/eksctl-test-cluster-11979-k8s-loc-NodeInstanceRole-DG66K3FIGXKE/i-03e43110acf72ea4e is not authorized to perform: elasticfilesystem:DescribeMountTargets on the specified resource

E0625 05:23:25.075876       1 driver.go:107] GRPC error: rpc error: code = Internal desc = Could not mount "fs-033ceb336e5e13716:/" at "/var/lib/kubelet/pods/c9378a49-716c-4ec5-8dcf-bb9964974666/volumes/kubernetes.io~csi/pvc-84542f17-72a1-4b27-9944-8249ad5e1e6e/mount": mount failed: exit status 1
Mounting command: mount
Mounting arguments: -t efs -o accesspoint=fsap-0458bd5373e8f313f,tls fs-033ceb336e5e13716:/ /var/lib/kubelet/pods/c9378a49-716c-4ec5-8dcf-bb9964974666/volumes/kubernetes.io~csi/pvc-84542f17-72a1-4b27-9944-8249ad5e1e6e/mount
Output: Failed to resolve "fs-033ceb336e5e13716.efs.us-west-2.amazonaws.com". The file system mount target ip address cannot be found, please pass mount target ip address via mount options. 
User: arn:aws:sts::607362164682:assumed-role/eksctl-test-cluster-11979-k8s-loc-NodeInstanceRole-DG66K3FIGXKE/i-03e43110acf72ea4e is not authorized to perform: elasticfilesystem:DescribeMountTargets on the specified resource
I0625 05:23:29.080168       1 node.go:287] NodeGetCapabilities: called with args 
I0625 05:23:29.080763       1 node.go:287] NodeGetCapabilities: called with args 
I0625 05:23:29.081443       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-033ceb336e5e13716::fsap-0458bd5373e8f313f" target_path:"/var/lib/kubelet/pods/c9378a49-716c-4ec5-8dcf-bb9964974666/volumes/kubernetes.io~csi/pvc-84542f17-72a1-4b27-9944-8249ad5e1e6e/mount" volume_capability:<mount:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > volume_context:<key:"storage.kubernetes.io/csiProvisionerIdentity" value:"1656134427254-8081-efs.csi.aws.com" > 
I0625 05:23:29.081498       1 node.go:175] NodePublishVolume: creating dir /var/lib/kubelet/pods/c9378a49-716c-4ec5-8dcf-bb9964974666/volumes/kubernetes.io~csi/pvc-84542f17-72a1-4b27-9944-8249ad5e1e6e/mount
I0625 05:23:29.081546       1 node.go:180] NodePublishVolume: mounting fs-033ceb336e5e13716:/ at /var/lib/kubelet/pods/c9378a49-716c-4ec5-8dcf-bb9964974666/volumes/kubernetes.io~csi/pvc-84542f17-72a1-4b27-9944-8249ad5e1e6e/mount with options [accesspoint=fsap-0458bd5373e8f313f tls]
... skipping 295 lines ...
I0625 05:25:37.608154       1 driver.go:128] Starting reaper
I0625 05:25:37.608252       1 driver.go:131] Listening for connections on address: &net.UnixAddr{Name:"/csi/csi.sock", Net:"unix"}
I0625 05:25:38.686644       1 node.go:303] NodeGetInfo: called with args 
I0625 05:25:39.068441       1 node.go:287] NodeGetCapabilities: called with args 
I0625 05:25:39.069676       1 node.go:287] NodeGetCapabilities: called with args 
I0625 05:25:39.070662       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-033ceb336e5e13716" staging_target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pvjp2tb" target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pvjp2tb/5ce33e5e-1ff1-460d-8505-bc916be42771" volume_capability:<block:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > 
E0625 05:25:39.070737       1 driver.go:107] GRPC error: rpc error: code = InvalidArgument desc = Volume capability not supported: only filesystem volumes are supported
I0625 05:25:40.079718       1 node.go:287] NodeGetCapabilities: called with args 
I0625 05:25:40.080721       1 node.go:287] NodeGetCapabilities: called with args 
I0625 05:25:40.081410       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-033ceb336e5e13716" staging_target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pvjp2tb" target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pvjp2tb/5ce33e5e-1ff1-460d-8505-bc916be42771" volume_capability:<block:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > 
E0625 05:25:40.081462       1 driver.go:107] GRPC error: rpc error: code = InvalidArgument desc = Volume capability not supported: only filesystem volumes are supported
I0625 05:25:42.095600       1 node.go:287] NodeGetCapabilities: called with args 
I0625 05:25:42.096754       1 node.go:287] NodeGetCapabilities: called with args 
I0625 05:25:42.097553       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-033ceb336e5e13716" staging_target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pvjp2tb" target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pvjp2tb/5ce33e5e-1ff1-460d-8505-bc916be42771" volume_capability:<block:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > 
E0625 05:25:42.097623       1 driver.go:107] GRPC error: rpc error: code = InvalidArgument desc = Volume capability not supported: only filesystem volumes are supported
I0625 05:25:44.821782       1 node.go:200] NodeUnpublishVolume: called with args volume_id:"fs-033ceb336e5e13716" target_path:"/var/lib/kubelet/pods/c9387b50-a83d-4ce4-8fa0-3010383e3ff5/volumes/kubernetes.io~csi/efs-1563/mount" 
I0625 05:25:44.823789       1 node.go:224] NodeUnpublishVolume: unmounting /var/lib/kubelet/pods/c9387b50-a83d-4ce4-8fa0-3010383e3ff5/volumes/kubernetes.io~csi/efs-1563/mount
I0625 05:25:44.836956       1 node.go:229] NodeUnpublishVolume: /var/lib/kubelet/pods/c9387b50-a83d-4ce4-8fa0-3010383e3ff5/volumes/kubernetes.io~csi/efs-1563/mount unmounted
I0625 05:25:44.922653       1 node.go:287] NodeGetCapabilities: called with args 
I0625 05:25:44.923907       1 node.go:287] NodeGetCapabilities: called with args 
I0625 05:25:44.924620       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-033ceb336e5e13716" staging_target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pvjp2tb" target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pvjp2tb/5ce33e5e-1ff1-460d-8505-bc916be42771" volume_capability:<block:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > 
E0625 05:25:44.924664       1 driver.go:107] GRPC error: rpc error: code = InvalidArgument desc = Volume capability not supported: only filesystem volumes are supported
I0625 05:25:45.427171       1 node.go:287] NodeGetCapabilities: called with args 
I0625 05:25:45.428215       1 node.go:287] NodeGetCapabilities: called with args 
I0625 05:25:45.428912       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-033ceb336e5e13716" staging_target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pvjp2tb" target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pvjp2tb/5ce33e5e-1ff1-460d-8505-bc916be42771" volume_capability:<block:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > 
E0625 05:25:45.428976       1 driver.go:107] GRPC error: rpc error: code = InvalidArgument desc = Volume capability not supported: only filesystem volumes are supported
I0625 05:25:46.436705       1 node.go:287] NodeGetCapabilities: called with args 
I0625 05:25:46.437846       1 node.go:287] NodeGetCapabilities: called with args 
I0625 05:25:46.438453       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-033ceb336e5e13716" staging_target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pvjp2tb" target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pvjp2tb/5ce33e5e-1ff1-460d-8505-bc916be42771" volume_capability:<block:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > 
E0625 05:25:46.438499       1 driver.go:107] GRPC error: rpc error: code = InvalidArgument desc = Volume capability not supported: only filesystem volumes are supported
I0625 05:25:48.454648       1 node.go:287] NodeGetCapabilities: called with args 
I0625 05:25:48.455518       1 node.go:287] NodeGetCapabilities: called with args 
I0625 05:25:48.456195       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-033ceb336e5e13716" staging_target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pvjp2tb" target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pvjp2tb/5ce33e5e-1ff1-460d-8505-bc916be42771" volume_capability:<block:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > 
E0625 05:25:48.456240       1 driver.go:107] GRPC error: rpc error: code = InvalidArgument desc = Volume capability not supported: only filesystem volumes are supported
I0625 05:25:52.490336       1 node.go:287] NodeGetCapabilities: called with args 
I0625 05:25:52.491156       1 node.go:287] NodeGetCapabilities: called with args 
I0625 05:25:52.492026       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-033ceb336e5e13716" staging_target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pvjp2tb" target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pvjp2tb/5ce33e5e-1ff1-460d-8505-bc916be42771" volume_capability:<block:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > 
E0625 05:25:52.492092       1 driver.go:107] GRPC error: rpc error: code = InvalidArgument desc = Volume capability not supported: only filesystem volumes are supported
I0625 05:25:54.406605       1 node.go:287] NodeGetCapabilities: called with args 
I0625 05:25:54.414079       1 node.go:287] NodeGetCapabilities: called with args 
I0625 05:25:54.414651       1 node.go:287] NodeGetCapabilities: called with args 
I0625 05:25:54.415468       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-033ceb336e5e13716::fsap-06f63a3f9d87305ca" target_path:"/var/lib/kubelet/pods/e2ca228d-d7a1-4223-a32f-87a42d816564/volumes/kubernetes.io~csi/pvc-d9c232f4-55c5-47bf-8540-0fda90aab63e/mount" volume_capability:<mount:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > volume_context:<key:"storage.kubernetes.io/csiProvisionerIdentity" value:"1656134427254-8081-efs.csi.aws.com" > 
I0625 05:25:54.415533       1 node.go:175] NodePublishVolume: creating dir /var/lib/kubelet/pods/e2ca228d-d7a1-4223-a32f-87a42d816564/volumes/kubernetes.io~csi/pvc-d9c232f4-55c5-47bf-8540-0fda90aab63e/mount
I0625 05:25:54.415576       1 node.go:180] NodePublishVolume: mounting fs-033ceb336e5e13716:/ at /var/lib/kubelet/pods/e2ca228d-d7a1-4223-a32f-87a42d816564/volumes/kubernetes.io~csi/pvc-d9c232f4-55c5-47bf-8540-0fda90aab63e/mount with options [accesspoint=fsap-06f63a3f9d87305ca tls]
... skipping 3 lines ...
I0625 05:25:58.548680       1 node.go:224] NodeUnpublishVolume: unmounting /var/lib/kubelet/pods/e2ca228d-d7a1-4223-a32f-87a42d816564/volumes/kubernetes.io~csi/pvc-d9c232f4-55c5-47bf-8540-0fda90aab63e/mount
I0625 05:25:58.561631       1 node.go:229] NodeUnpublishVolume: /var/lib/kubelet/pods/e2ca228d-d7a1-4223-a32f-87a42d816564/volumes/kubernetes.io~csi/pvc-d9c232f4-55c5-47bf-8540-0fda90aab63e/mount unmounted
I0625 05:25:58.651293       1 node.go:287] NodeGetCapabilities: called with args 
I0625 05:26:00.569192       1 node.go:287] NodeGetCapabilities: called with args 
I0625 05:26:00.570441       1 node.go:287] NodeGetCapabilities: called with args 
I0625 05:26:00.571282       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-033ceb336e5e13716" staging_target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pvjp2tb" target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pvjp2tb/5ce33e5e-1ff1-460d-8505-bc916be42771" volume_capability:<block:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > 
E0625 05:26:00.571333       1 driver.go:107] GRPC error: rpc error: code = InvalidArgument desc = Volume capability not supported: only filesystem volumes are supported
I0625 05:26:11.271447       1 node.go:287] NodeGetCapabilities: called with args 
I0625 05:26:11.278560       1 node.go:287] NodeGetCapabilities: called with args 
I0625 05:26:11.279194       1 node.go:287] NodeGetCapabilities: called with args 
I0625 05:26:11.279785       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-033ceb336e5e13716::fsap-060bd9e49b3a8df90" target_path:"/var/lib/kubelet/pods/26743cf1-fa9d-4dc0-b1d0-d603e596d7ef/volumes/kubernetes.io~csi/pvc-13dd33ad-1d56-4e27-806f-23f3cc9feb28/mount" volume_capability:<mount:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > volume_context:<key:"storage.kubernetes.io/csiProvisionerIdentity" value:"1656134427254-8081-efs.csi.aws.com" > 
I0625 05:26:11.279859       1 node.go:175] NodePublishVolume: creating dir /var/lib/kubelet/pods/26743cf1-fa9d-4dc0-b1d0-d603e596d7ef/volumes/kubernetes.io~csi/pvc-13dd33ad-1d56-4e27-806f-23f3cc9feb28/mount
I0625 05:26:11.279907       1 node.go:180] NodePublishVolume: mounting fs-033ceb336e5e13716:/ at /var/lib/kubelet/pods/26743cf1-fa9d-4dc0-b1d0-d603e596d7ef/volumes/kubernetes.io~csi/pvc-13dd33ad-1d56-4e27-806f-23f3cc9feb28/mount with options [accesspoint=fsap-060bd9e49b3a8df90 tls]
... skipping 2 lines ...
I0625 05:26:15.516181       1 node.go:224] NodeUnpublishVolume: unmounting /var/lib/kubelet/pods/26743cf1-fa9d-4dc0-b1d0-d603e596d7ef/volumes/kubernetes.io~csi/pvc-13dd33ad-1d56-4e27-806f-23f3cc9feb28/mount
I0625 05:26:15.537125       1 node.go:229] NodeUnpublishVolume: /var/lib/kubelet/pods/26743cf1-fa9d-4dc0-b1d0-d603e596d7ef/volumes/kubernetes.io~csi/pvc-13dd33ad-1d56-4e27-806f-23f3cc9feb28/mount unmounted
I0625 05:26:15.617334       1 node.go:287] NodeGetCapabilities: called with args 
I0625 05:26:16.627650       1 node.go:287] NodeGetCapabilities: called with args 
I0625 05:26:16.628566       1 node.go:287] NodeGetCapabilities: called with args 
I0625 05:26:16.629292       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-033ceb336e5e13716" staging_target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pvjp2tb" target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pvjp2tb/5ce33e5e-1ff1-460d-8505-bc916be42771" volume_capability:<block:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > 
E0625 05:26:16.629346       1 driver.go:107] GRPC error: rpc error: code = InvalidArgument desc = Volume capability not supported: only filesystem volumes are supported
I0625 05:26:36.115567       1 node.go:287] NodeGetCapabilities: called with args 
I0625 05:26:36.122818       1 node.go:287] NodeGetCapabilities: called with args 
I0625 05:26:36.123542       1 node.go:287] NodeGetCapabilities: called with args 
I0625 05:26:36.124197       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-033ceb336e5e13716::fsap-04414a8e2a4d67494" target_path:"/var/lib/kubelet/pods/6a64a566-240d-4735-98c7-aa84efbb3d58/volumes/kubernetes.io~csi/pvc-cd652b9b-fc31-4024-9b99-4d29d567044d/mount" volume_capability:<mount:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > volume_context:<key:"storage.kubernetes.io/csiProvisionerIdentity" value:"1656134427254-8081-efs.csi.aws.com" > 
I0625 05:26:36.124269       1 node.go:175] NodePublishVolume: creating dir /var/lib/kubelet/pods/6a64a566-240d-4735-98c7-aa84efbb3d58/volumes/kubernetes.io~csi/pvc-cd652b9b-fc31-4024-9b99-4d29d567044d/mount
I0625 05:26:36.124316       1 node.go:180] NodePublishVolume: mounting fs-033ceb336e5e13716:/ at /var/lib/kubelet/pods/6a64a566-240d-4735-98c7-aa84efbb3d58/volumes/kubernetes.io~csi/pvc-cd652b9b-fc31-4024-9b99-4d29d567044d/mount with options [accesspoint=fsap-04414a8e2a4d67494 tls]
I0625 05:26:36.405562       1 node.go:185] NodePublishVolume: /var/lib/kubelet/pods/6a64a566-240d-4735-98c7-aa84efbb3d58/volumes/kubernetes.io~csi/pvc-cd652b9b-fc31-4024-9b99-4d29d567044d/mount was mounted
I0625 05:26:48.731673       1 node.go:287] NodeGetCapabilities: called with args 
I0625 05:26:48.732415       1 node.go:287] NodeGetCapabilities: called with args 
I0625 05:26:48.733093       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-033ceb336e5e13716" staging_target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pvjp2tb" target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pvjp2tb/5ce33e5e-1ff1-460d-8505-bc916be42771" volume_capability:<block:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > 
E0625 05:26:48.733144       1 driver.go:107] GRPC error: rpc error: code = InvalidArgument desc = Volume capability not supported: only filesystem volumes are supported
I0625 05:26:49.841166       1 node.go:200] NodeUnpublishVolume: called with args volume_id:"fs-033ceb336e5e13716::fsap-04414a8e2a4d67494" target_path:"/var/lib/kubelet/pods/6a64a566-240d-4735-98c7-aa84efbb3d58/volumes/kubernetes.io~csi/pvc-cd652b9b-fc31-4024-9b99-4d29d567044d/mount" 
I0625 05:26:49.843337       1 node.go:224] NodeUnpublishVolume: unmounting /var/lib/kubelet/pods/6a64a566-240d-4735-98c7-aa84efbb3d58/volumes/kubernetes.io~csi/pvc-cd652b9b-fc31-4024-9b99-4d29d567044d/mount
I0625 05:26:49.869084       1 node.go:229] NodeUnpublishVolume: /var/lib/kubelet/pods/6a64a566-240d-4735-98c7-aa84efbb3d58/volumes/kubernetes.io~csi/pvc-cd652b9b-fc31-4024-9b99-4d29d567044d/mount unmounted
I0625 05:26:49.943574       1 node.go:287] NodeGetCapabilities: called with args 
I0625 05:27:00.934262       1 reaper.go:107] reaper: waited for process &{32 1 90 32 32 stunnel}
I0625 05:27:17.970987       1 reaper.go:107] reaper: waited for process &{49 1 90 49 49 stunnel}
... skipping 151 lines ...