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:36
Elapsed39m43s
Revision1def5970255c2fa4c9680f811451606a1818f7eb
Refs 714

No Test Failures!


Show 35 Passed Tests

Show 154 Skipped Tests

Error lines from build-log.txt

... skipping 239 lines ...
#9 2.706 --> Processing Dependency: libperl.so()(64bit) for package: 4:perl-5.16.3-299.amzn2.0.1.x86_64
#9 2.707 ---> Package perl-File-Temp.noarch 0:0.23.01-3.amzn2 will be installed
#9 2.712 ---> Package perl-Getopt-Long.noarch 0:2.40-3.amzn2 will be installed
#9 2.712 --> Processing Dependency: perl(Pod::Usage) >= 1.14 for package: perl-Getopt-Long-2.40-3.amzn2.noarch
#9 2.712 --> Processing Dependency: perl(Text::ParseWords) for package: perl-Getopt-Long-2.40-3.amzn2.noarch
#9 2.712 ---> Package perl-Git.noarch 0:2.32.0-1.amzn2.0.1 will be installed
#9 2.713 --> Processing Dependency: perl(Error) for package: perl-Git-2.32.0-1.amzn2.0.1.noarch
#9 2.714 ---> Package perl-PathTools.x86_64 0:3.40-5.amzn2.0.2 will be installed
#9 2.716 ---> Package perl-TermReadKey.x86_64 0:2.30-20.amzn2.0.2 will be installed
#9 2.717 ---> Package perl-Thread-Queue.noarch 0:3.02-2.amzn2 will be installed
#9 2.718 ---> Package perl-threads.x86_64 0:1.87-4.amzn2.0.2 will be installed
#9 2.720 ---> Package pkgconfig.x86_64 1:0.27.1-4.amzn2.0.2 will be installed
#9 2.722 ---> Package system-rpm-config.noarch 0:9.1.0-76.amzn2.0.14 will be installed
... skipping 15 lines ...
#9 2.784 --> Processing Dependency: openssh = 7.4p1-22.amzn2.0.1 for package: openssh-clients-7.4p1-22.amzn2.0.1.x86_64
#9 2.786 --> Processing Dependency: fipscheck-lib(x86-64) >= 1.3.0 for package: openssh-clients-7.4p1-22.amzn2.0.1.x86_64
#9 2.788 --> Processing Dependency: libfipscheck.so.1()(64bit) for package: openssh-clients-7.4p1-22.amzn2.0.1.x86_64
#9 2.788 --> Processing Dependency: libedit.so.0()(64bit) for package: openssh-clients-7.4p1-22.amzn2.0.1.x86_64
#9 2.790 ---> Package pcre2.x86_64 0:10.23-2.amzn2.0.2 will be installed
#9 2.792 ---> Package perl-Carp.noarch 0:1.26-244.amzn2 will be installed
#9 2.792 ---> Package perl-Error.noarch 1:0.17020-2.amzn2 will be installed
#9 2.793 ---> Package perl-Exporter.noarch 0:5.68-3.amzn2 will be installed
#9 2.793 ---> Package perl-File-Path.noarch 0:2.09-2.amzn2 will be installed
#9 2.794 ---> Package perl-Filter.x86_64 0:1.49-3.amzn2.0.2 will be installed
#9 2.796 ---> Package perl-Pod-Simple.noarch 1:3.28-4.amzn2 will be installed
#9 2.800 --> Processing Dependency: perl(Pod::Escapes) >= 1.04 for package: 1:perl-Pod-Simple-3.28-4.amzn2.noarch
#9 2.802 --> Processing Dependency: perl(Encode) for package: 1:perl-Pod-Simple-3.28-4.amzn2.noarch
... skipping 169 lines ...
#9 3.205  pam                       x86_64 1.1.8-23.amzn2.0.1           amzn2-core 715 k
#9 3.205  patch                     x86_64 2.7.1-12.amzn2.0.2           amzn2-core 110 k
#9 3.205  pcre2                     x86_64 10.23-2.amzn2.0.2            amzn2-core 209 k
#9 3.205  perl                      x86_64 4:5.16.3-299.amzn2.0.1       amzn2-core 8.0 M
#9 3.205  perl-Carp                 noarch 1.26-244.amzn2               amzn2-core  19 k
#9 3.205  perl-Encode               x86_64 2.51-7.amzn2.0.2             amzn2-core 1.5 M
#9 3.205  perl-Error                noarch 1:0.17020-2.amzn2            amzn2-core  32 k
#9 3.205  perl-Exporter             noarch 5.68-3.amzn2                 amzn2-core  29 k
#9 3.205  perl-File-Path            noarch 2.09-2.amzn2                 amzn2-core  27 k
#9 3.205  perl-File-Temp            noarch 0.23.01-3.amzn2              amzn2-core  56 k
#9 3.205  perl-Filter               x86_64 1.49-3.amzn2.0.2             amzn2-core  76 k
#9 3.205  perl-Getopt-Long          noarch 2.40-3.amzn2                 amzn2-core  56 k
#9 3.205  perl-Git                  noarch 2.32.0-1.amzn2.0.1           amzn2-core  43 k
... skipping 91 lines ...
#9 8.869   Installing : 1:perl-Pod-Simple-3.28-4.amzn2.noarch                      34/88 
#9 8.915   Installing : perl-Getopt-Long-2.40-3.amzn2.noarch                       35/88 
#9 9.054   Installing : 4:perl-libs-5.16.3-299.amzn2.0.1.x86_64                    36/88 
#9 10.75   Installing : 4:perl-5.16.3-299.amzn2.0.1.x86_64                         37/88 
#9 10.81   Installing : perl-Thread-Queue-3.02-2.amzn2.noarch                      38/88 
#9 10.85   Installing : perl-TermReadKey-2.30-20.amzn2.0.2.x86_64                  39/88 
#9 10.89   Installing : 1:perl-Error-0.17020-2.amzn2.noarch                        40/88 
#9 10.92   Installing : fipscheck-lib-1.4.1-6.amzn2.0.2.x86_64                     41/88 
#9 10.98   Installing : fipscheck-1.4.1-6.amzn2.0.2.x86_64                         42/88 
#9 11.02   Installing : dwz-0.11-3.amzn2.0.3.x86_64                                43/88 
#9 11.06   Installing : 1:pkgconfig-0.27.1-4.amzn2.0.2.x86_64                      44/88 
#9 11.15   Installing : pcre2-10.23-2.amzn2.0.2.x86_64                             45/88 
#9 11.21   Installing : libsmartcols-2.30.2-2.amzn2.0.7.x86_64                     46/88 
... skipping 33 lines ...
#0 0.360 CGO_ENABLED=0 GOOS=linux GOARCH=amd64 go build -mod=vendor -ldflags "-X github.com/kubernetes-sigs/aws-efs-csi-driver/pkg/driver.driverVersion=v1.4.0 -X github.com/kubernetes-sigs/aws-efs-csi-driver/pkg/driver.gitCommit=9ad0b28c649b53d89c597b3d1e6f35cab78963e7 -X github.com/kubernetes-sigs/aws-efs-csi-driver/pkg/driver.buildDate=2022-06-25T05:37:40Z -X github.com/kubernetes-sigs/aws-efs-csi-driver/pkg/driver.efsClientSource=k8s" -o bin/aws-efs-csi-driver ./cmd/
#14 ...

#9 [linux-amazon 3/7] RUN if [ "github" = "yum" ];     then echo "Installing efs-utils from Amazon Linux 2 yum repo" &&          yum -y install amazon-efs-utils-1.31.1-1.amzn2.noarch;     else echo "Installing efs-utils from github using the latest git tag" &&          yum -y install git rpm-build make &&          git clone https://github.com/aws/efs-utils &&          cd efs-utils &&          git checkout $(git describe --tags $(git rev-list --tags --max-count=1)) &&          make rpm && yum -y install build/amazon-efs-utils*rpm &&          cd .. && rm -rf efs-utils &&          yum clean all;     fi
#9 15.98   Installing : 1:dbus-libs-1.10.24-7.amzn2.x86_64                         76/88 
#9 17.47   Installing : systemd-219-78.amzn2.0.18.x86_64                           77/88 
#9 18.03 Failed to get D-Bus connection: Operation not permitted
#9 18.06   Installing : elfutils-default-yama-scope-0.176-2.amzn2.noarch           78/88 
#9 18.25   Installing : 1:dbus-1.10.24-7.amzn2.x86_64                              79/88 
#9 18.34   Installing : elfutils-0.176-2.amzn2.x86_64                              80/88 
#9 18.53   Installing : openssh-7.4p1-22.amzn2.0.1.x86_64                          81/88 
#9 18.71   Installing : openssh-clients-7.4p1-22.amzn2.0.1.x86_64                  82/88 
#9 19.92   Installing : git-core-2.32.0-1.amzn2.0.1.x86_64                         83/88 
... skipping 55 lines ...
#9 21.92   Verifying  : perl-File-Temp-0.23.01-3.amzn2.noarch                      51/88 
#9 21.94   Verifying  : perl-srpm-macros-1-8.amzn2.0.1.noarch                      52/88 
#9 21.95   Verifying  : pam-1.1.8-23.amzn2.0.1.x86_64                              53/88 
#9 21.97   Verifying  : xz-5.2.2-1.amzn2.0.3.x86_64                                54/88 
#9 21.98   Verifying  : ustr-1.0.4-16.amzn2.0.3.x86_64                             55/88 
#9 21.99   Verifying  : less-458-9.amzn2.0.2.x86_64                                56/88 
#9 22.01   Verifying  : 1:perl-Error-0.17020-2.amzn2.noarch                        57/88 
#9 22.02   Verifying  : perl-Pod-Usage-1.63-3.amzn2.noarch                         58/88 
#9 22.06   Verifying  : unzip-6.0-43.amzn2.x86_64                                  59/88 
#9 22.07   Verifying  : 1:perl-parent-0.225-244.amzn2.0.1.noarch                   60/88 
#9 22.09   Verifying  : perl-Pod-Perldoc-3.20-4.amzn2.noarch                       61/88 
#9 22.10   Verifying  : 2:tar-1.26-35.amzn2.x86_64                                 62/88 
#9 22.12   Verifying  : zip-3.0-11.amzn2.0.2.x86_64                                63/88 
... skipping 69 lines ...
#9 22.60   pam.x86_64 0:1.1.8-23.amzn2.0.1                                               
#9 22.60   patch.x86_64 0:2.7.1-12.amzn2.0.2                                             
#9 22.60   pcre2.x86_64 0:10.23-2.amzn2.0.2                                              
#9 22.60   perl.x86_64 4:5.16.3-299.amzn2.0.1                                            
#9 22.60   perl-Carp.noarch 0:1.26-244.amzn2                                             
#9 22.60   perl-Encode.x86_64 0:2.51-7.amzn2.0.2                                         
#9 22.60   perl-Error.noarch 1:0.17020-2.amzn2                                           
#9 22.60   perl-Exporter.noarch 0:5.68-3.amzn2                                           
#9 22.60   perl-File-Path.noarch 0:2.09-2.amzn2                                          
#9 22.60   perl-File-Temp.noarch 0:0.23.01-3.amzn2                                       
#9 22.60   perl-Filter.x86_64 0:1.49-3.amzn2.0.2                                         
#9 22.60   perl-Getopt-Long.noarch 0:2.40-3.amzn2                                        
#9 22.60   perl-Git.noarch 0:2.32.0-1.amzn2.0.1                                          
... skipping 558 lines ...
|.Xo +.= S +      |
|+ o*.X.+ = .     |
| ..+O B.. o      |
|  =  *.o..       |
| . ....oo        |
+----[SHA256]-----+
Error: unable to describe control plane "test-cluster-15278-k8s-local": operation error EKS: DescribeCluster, https response error StatusCode: 404, RequestID: a8259935-a899-4f93-aa0f-9cac036630a6, ResourceNotFoundException: No cluster found for name: test-cluster-15278-k8s-local.
###
## Creating cluster test-cluster-15278-k8s-local with /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-15278.k8s.local.eksctl.yaml (dry run)
#
###
## Patching cluster test-cluster-15278-k8s-local with ./hack/eksctl-patch.yaml
#
... skipping 127 lines ...
Random Seed: 1656136596 - Will randomize all specs
Will run 189 specs

Running in parallel across 4 nodes

STEP: Creating EFS filesystem in region "us-west-2" for cluster "test-cluster-15278-k8s-local"
error getting kops node security group id: no security groups found with filters [{
    Name: "tag:Name",
    Values: ["nodes.test-cluster-15278-k8s-local"]
  }]
error getting kops node subnet ids: no subnets found with filters [{
    Name: "tag-key",
    Values: ["kubernetes.io/cluster/test-cluster-15278-k8s-local"]
  }]
STEP: Created EFS filesystem "fs-0c7556f6e4e09d36e" in region "us-west-2" for cluster "test-cluster-15278-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:219
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath directory is outside the volume [Slow][LinuxOnly] [BeforeEach]
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:244
------------------------------
... skipping 46 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:59:31.500: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-15278.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-7189
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:59:32.467: 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:59:32.468: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-7189" for this suite.
... skipping 7 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227
    [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
    /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail to use a volume in a pod with mismatched mode [Slow] [It]
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go: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 21 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227
    [Testpattern: Inline-volume (default fs)] subPath
    /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly] [BeforeEach]
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

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

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:116
------------------------------
... skipping 147 lines ...
STEP: Binding the e2e-test-privileged-psp PodSecurityPolicy to the default service account in efs-1318
STEP: Waiting for a default service account to be provisioned in namespace
[It] should mount with option tls when encryptInTransit set true
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:367
STEP: Creating efs pvc & pv
STEP: Creating pod to mount pvc "efs-1318" and run "mount && mount | grep /mnt/volume1 | grep 127.0.0.1"
Jun 25 05:59:18.949: INFO: Waiting up to 5m0s for pod "pvc-tester-9t87v" in namespace "efs-1318" to be "Succeeded or Failed"
Jun 25 05:59:19.015: INFO: Pod "pvc-tester-9t87v": Phase="Pending", Reason="", readiness=false. Elapsed: 65.543274ms
Jun 25 05:59:21.083: INFO: Pod "pvc-tester-9t87v": Phase="Pending", Reason="", readiness=false. Elapsed: 2.134003794s
Jun 25 05:59:23.147: INFO: Pod "pvc-tester-9t87v": Phase="Pending", Reason="", readiness=false. Elapsed: 4.19777262s
Jun 25 05:59:25.213: INFO: Pod "pvc-tester-9t87v": Phase="Pending", Reason="", readiness=false. Elapsed: 6.263867413s
Jun 25 05:59:27.286: INFO: Pod "pvc-tester-9t87v": Phase="Pending", Reason="", readiness=false. Elapsed: 8.336845284s
Jun 25 05:59:29.360: INFO: Pod "pvc-tester-9t87v": Phase="Pending", Reason="", readiness=false. Elapsed: 10.410607857s
... skipping 2 lines ...
Jun 25 05:59:35.563: INFO: Pod "pvc-tester-9t87v": Phase="Pending", Reason="", readiness=false. Elapsed: 16.613960919s
Jun 25 05:59:37.628: INFO: Pod "pvc-tester-9t87v": Phase="Pending", Reason="", readiness=false. Elapsed: 18.678460684s
Jun 25 05:59:39.694: INFO: Pod "pvc-tester-9t87v": Phase="Pending", Reason="", readiness=false. Elapsed: 20.744822234s
Jun 25 05:59:41.762: INFO: Pod "pvc-tester-9t87v": Phase="Pending", Reason="", readiness=false. Elapsed: 22.813103596s
Jun 25 05:59:43.826: INFO: Pod "pvc-tester-9t87v": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.877045582s
STEP: Saw pod success
Jun 25 05:59:43.826: INFO: Pod "pvc-tester-9t87v" satisfied condition "Succeeded or Failed"
Jun 25 05:59:43.903: INFO: pod "pvc-tester-9t87v" logs:
 overlay on / type overlay (rw,relatime,lowerdir=/var/lib/docker/overlay2/l/QM7DY6U2IGNFHVSGZWM2WONB4V:/var/lib/docker/overlay2/l/UMIWSIQRUPPXE3L2RQKE55NOCS,upperdir=/var/lib/docker/overlay2/42a3c842ec5aa4ec94a29fdc05d335e0f1f2b2b34ec6c9ecd52d308961e30043/diff,workdir=/var/lib/docker/overlay2/42a3c842ec5aa4ec94a29fdc05d335e0f1f2b2b34ec6c9ecd52d308961e30043/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 69 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227
    [Testpattern: 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 11 lines ...
STEP: Binding the e2e-test-privileged-psp PodSecurityPolicy to the default service account in efs-1211
STEP: Waiting for a default service account to be provisioned in namespace
[It] should mount without option tls when encryptInTransit set false
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:372
STEP: Creating efs pvc & pv
STEP: Creating pod to mount pvc "efs-1211" and run "mount && mount | grep /mnt/volume1 | grep fs-0c7556f6e4e09d36e"
Jun 25 05:59:22.892: INFO: Waiting up to 5m0s for pod "pvc-tester-zl2ph" in namespace "efs-1211" to be "Succeeded or Failed"
Jun 25 05:59:22.957: INFO: Pod "pvc-tester-zl2ph": Phase="Pending", Reason="", readiness=false. Elapsed: 64.837854ms
Jun 25 05:59:25.024: INFO: Pod "pvc-tester-zl2ph": Phase="Pending", Reason="", readiness=false. Elapsed: 2.131461262s
Jun 25 05:59:27.091: INFO: Pod "pvc-tester-zl2ph": Phase="Pending", Reason="", readiness=false. Elapsed: 4.198713294s
Jun 25 05:59:29.155: INFO: Pod "pvc-tester-zl2ph": Phase="Pending", Reason="", readiness=false. Elapsed: 6.263381203s
Jun 25 05:59:31.223: INFO: Pod "pvc-tester-zl2ph": Phase="Pending", Reason="", readiness=false. Elapsed: 8.330632187s
Jun 25 05:59:33.288: INFO: Pod "pvc-tester-zl2ph": Phase="Pending", Reason="", readiness=false. Elapsed: 10.395547989s
... skipping 7 lines ...
Jun 25 05:59:49.827: INFO: Pod "pvc-tester-zl2ph": Phase="Pending", Reason="", readiness=false. Elapsed: 26.934857888s
Jun 25 05:59:51.894: INFO: Pod "pvc-tester-zl2ph": Phase="Pending", Reason="", readiness=false. Elapsed: 29.001523114s
Jun 25 05:59:53.968: INFO: Pod "pvc-tester-zl2ph": Phase="Pending", Reason="", readiness=false. Elapsed: 31.075657233s
Jun 25 05:59:56.036: INFO: Pod "pvc-tester-zl2ph": Phase="Pending", Reason="", readiness=false. Elapsed: 33.143502658s
Jun 25 05:59:58.102: INFO: Pod "pvc-tester-zl2ph": Phase="Succeeded", Reason="", readiness=false. Elapsed: 35.209660408s
STEP: Saw pod success
Jun 25 05:59:58.102: INFO: Pod "pvc-tester-zl2ph" satisfied condition "Succeeded or Failed"
Jun 25 05:59:58.223: INFO: pod "pvc-tester-zl2ph" logs:
 overlay on / type overlay (rw,relatime,lowerdir=/var/lib/docker/overlay2/l/A4REGBI6B2GYINNH5DBUYZL64L:/var/lib/docker/overlay2/l/4KOBX3KUI2LTU3AGLB7PO66EK3,upperdir=/var/lib/docker/overlay2/ce6747a042357b90924a48777726326d4ba26b82c23650cafed61a9b86ffd793/diff,workdir=/var/lib/docker/overlay2/ce6747a042357b90924a48777726326d4ba26b82c23650cafed61a9b86ffd793/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 143 lines ...
STEP: creating a claim
Jun 25 05:59:47.699: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jun 25 05:59:47.773: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.comcqn8v] to have phase Bound
Jun 25 05:59:47.839: INFO: PersistentVolumeClaim efs.csi.aws.comcqn8v found but phase is Pending instead of Bound.
Jun 25 05:59:49.907: INFO: PersistentVolumeClaim efs.csi.aws.comcqn8v found and phase=Bound (2.134284667s)
STEP: Creating pod to format volume volume-prep-provisioning-495
Jun 25 05:59:50.121: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-495" in namespace "provisioning-495" to be "Succeeded or Failed"
Jun 25 05:59:50.187: INFO: Pod "volume-prep-provisioning-495": Phase="Pending", Reason="", readiness=false. Elapsed: 66.099315ms
Jun 25 05:59:52.255: INFO: Pod "volume-prep-provisioning-495": Phase="Pending", Reason="", readiness=false. Elapsed: 2.134774765s
Jun 25 05:59:54.324: INFO: Pod "volume-prep-provisioning-495": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.202891076s
STEP: Saw pod success
Jun 25 05:59:54.324: INFO: Pod "volume-prep-provisioning-495" satisfied condition "Succeeded or Failed"
Jun 25 05:59:54.324: INFO: Deleting pod "volume-prep-provisioning-495" in namespace "provisioning-495"
Jun 25 05:59:54.459: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-495" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-lmv8
STEP: Checking for subpath error in container status
Jun 25 06:00:00.753: INFO: Deleting pod "pod-subpath-test-dynamicpv-lmv8" in namespace "provisioning-495"
Jun 25 06:00:00.831: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-lmv8" to be fully deleted
STEP: Deleting pod
Jun 25 06:00:02.966: INFO: Deleting pod "pod-subpath-test-dynamicpv-lmv8" in namespace "provisioning-495"
STEP: Deleting pvc
Jun 25 06:00:03.035: INFO: Deleting PersistentVolumeClaim "efs.csi.aws.comcqn8v"
... skipping 146 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 06:00:10.818: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-15278.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-5356
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 06:00:11.768: 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 06:00:11.768: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-5356" for this suite.
... skipping 7 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227
    [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
    /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail to use a volume in a pod with mismatched mode [Slow] [It]
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go: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 21 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly] [BeforeEach]
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

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

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:244
------------------------------
... skipping 457 lines ...
Jun 25 06:00:03.123: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jun 25 06:00:03.204: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.comrrxbz] to have phase Bound
Jun 25 06:00:03.273: INFO: PersistentVolumeClaim efs.csi.aws.comrrxbz found but phase is Pending instead of Bound.
Jun 25 06:00:05.336: INFO: PersistentVolumeClaim efs.csi.aws.comrrxbz found and phase=Bound (2.132519971s)
STEP: Creating pod pod-subpath-test-dynamicpv-r7zk
STEP: Creating a pod to test subpath
Jun 25 06:00:05.607: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-r7zk" in namespace "provisioning-1737" to be "Succeeded or Failed"
Jun 25 06:00:05.670: INFO: Pod "pod-subpath-test-dynamicpv-r7zk": Phase="Pending", Reason="", readiness=false. Elapsed: 62.968426ms
Jun 25 06:00:07.733: INFO: Pod "pod-subpath-test-dynamicpv-r7zk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.12507204s
Jun 25 06:00:09.796: INFO: Pod "pod-subpath-test-dynamicpv-r7zk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.188019762s
Jun 25 06:00:11.859: INFO: Pod "pod-subpath-test-dynamicpv-r7zk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.251761314s
STEP: Saw pod success
Jun 25 06:00:11.859: INFO: Pod "pod-subpath-test-dynamicpv-r7zk" satisfied condition "Succeeded or Failed"
Jun 25 06:00:11.923: INFO: Trying to get logs from node ip-192-168-0-82.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-r7zk container test-container-subpath-dynamicpv-r7zk: <nil>
STEP: delete the pod
Jun 25 06:00:12.119: INFO: Waiting for pod pod-subpath-test-dynamicpv-r7zk to disappear
Jun 25 06:00:12.183: INFO: Pod pod-subpath-test-dynamicpv-r7zk no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-r7zk
Jun 25 06:00:12.183: INFO: Deleting pod "pod-subpath-test-dynamicpv-r7zk" in namespace "provisioning-1737"
STEP: Creating pod pod-subpath-test-dynamicpv-r7zk
STEP: Creating a pod to test subpath
Jun 25 06:00:12.319: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-r7zk" in namespace "provisioning-1737" to be "Succeeded or Failed"
Jun 25 06:00:12.388: INFO: Pod "pod-subpath-test-dynamicpv-r7zk": Phase="Pending", Reason="", readiness=false. Elapsed: 69.05805ms
Jun 25 06:00:14.451: INFO: Pod "pod-subpath-test-dynamicpv-r7zk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.132592381s
Jun 25 06:00:16.521: INFO: Pod "pod-subpath-test-dynamicpv-r7zk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.202244136s
STEP: Saw pod success
Jun 25 06:00:16.521: INFO: Pod "pod-subpath-test-dynamicpv-r7zk" satisfied condition "Succeeded or Failed"
Jun 25 06:00:16.583: INFO: Trying to get logs from node ip-192-168-0-82.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-r7zk container test-container-subpath-dynamicpv-r7zk: <nil>
STEP: delete the pod
Jun 25 06:00:16.781: INFO: Waiting for pod pod-subpath-test-dynamicpv-r7zk to disappear
Jun 25 06:00:16.843: INFO: Pod pod-subpath-test-dynamicpv-r7zk no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-r7zk
Jun 25 06:00:16.843: INFO: Deleting pod "pod-subpath-test-dynamicpv-r7zk" in namespace "provisioning-1737"
... skipping 56 lines ...
Jun 25 06:00:18.298: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jun 25 06:00:18.375: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.comkxrpf] to have phase Bound
Jun 25 06:00:18.438: INFO: PersistentVolumeClaim efs.csi.aws.comkxrpf found but phase is Pending instead of Bound.
Jun 25 06:00:20.504: INFO: PersistentVolumeClaim efs.csi.aws.comkxrpf found and phase=Bound (2.129840928s)
STEP: Creating pod pod-subpath-test-dynamicpv-59pw
STEP: Creating a pod to test multi_subpath
Jun 25 06:00:20.713: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-59pw" in namespace "provisioning-1485" to be "Succeeded or Failed"
Jun 25 06:00:20.810: INFO: Pod "pod-subpath-test-dynamicpv-59pw": Phase="Pending", Reason="", readiness=false. Elapsed: 96.824427ms
Jun 25 06:00:22.875: INFO: Pod "pod-subpath-test-dynamicpv-59pw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.161593207s
Jun 25 06:00:24.942: INFO: Pod "pod-subpath-test-dynamicpv-59pw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.228595573s
STEP: Saw pod success
Jun 25 06:00:24.942: INFO: Pod "pod-subpath-test-dynamicpv-59pw" satisfied condition "Succeeded or Failed"
Jun 25 06:00:25.007: INFO: Trying to get logs from node ip-192-168-0-82.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-59pw container test-container-subpath-dynamicpv-59pw: <nil>
STEP: delete the pod
Jun 25 06:00:25.225: INFO: Waiting for pod pod-subpath-test-dynamicpv-59pw to disappear
Jun 25 06:00:25.312: INFO: Pod pod-subpath-test-dynamicpv-59pw no longer exists
STEP: Deleting pod
Jun 25 06:00:25.312: INFO: Deleting pod "pod-subpath-test-dynamicpv-59pw" in namespace "provisioning-1485"
... skipping 47 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227
    [Testpattern: Inline-volume (default fs)] subPath
    /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath directory is outside the volume [Slow][LinuxOnly] [BeforeEach]
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

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

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

[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 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 06:00:23.599: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-15278.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-4078
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 06:00:24.750: INFO: Creating resource for dynamic PV
Jun 25 06:00:24.750: 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 06:00:24.950: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jun 25 06:00:25.032: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.com7bdg7] to have phase Bound
Jun 25 06:00:25.103: INFO: PersistentVolumeClaim efs.csi.aws.com7bdg7 found but phase is Pending instead of Bound.
Jun 25 06:00:27.173: INFO: PersistentVolumeClaim efs.csi.aws.com7bdg7 found and phase=Bound (2.141623676s)
STEP: Creating pod pod-subpath-test-dynamicpv-hn7k
STEP: Checking for subpath error in container status
Jun 25 06:00:33.529: INFO: Deleting pod "pod-subpath-test-dynamicpv-hn7k" in namespace "provisioning-4078"
Jun 25 06:00:33.606: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-hn7k" to be fully deleted
STEP: Deleting pod
Jun 25 06:00:35.755: INFO: Deleting pod "pod-subpath-test-dynamicpv-hn7k" in namespace "provisioning-4078"
STEP: Deleting pvc
Jun 25 06:00:35.831: INFO: Deleting PersistentVolumeClaim "efs.csi.aws.com7bdg7"
... skipping 15 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227
    [Testpattern: Dynamic PV (default fs)] subPath
    /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly]
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 17 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath directory is outside the volume [Slow][LinuxOnly] [BeforeEach]
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

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

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 175 lines ...
Jun 25 06:00:34.613: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jun 25 06:00:34.687: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.com98rk6] to have phase Bound
Jun 25 06:00:34.753: INFO: PersistentVolumeClaim efs.csi.aws.com98rk6 found but phase is Pending instead of Bound.
Jun 25 06:00:36.820: INFO: PersistentVolumeClaim efs.csi.aws.com98rk6 found and phase=Bound (2.133055756s)
STEP: Creating pod pod-subpath-test-dynamicpv-zgkx
STEP: Creating a pod to test subpath
Jun 25 06:00:37.081: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-zgkx" in namespace "provisioning-2199" to be "Succeeded or Failed"
Jun 25 06:00:37.147: INFO: Pod "pod-subpath-test-dynamicpv-zgkx": Phase="Pending", Reason="", readiness=false. Elapsed: 66.393356ms
Jun 25 06:00:39.215: INFO: Pod "pod-subpath-test-dynamicpv-zgkx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.134221145s
Jun 25 06:00:41.280: INFO: Pod "pod-subpath-test-dynamicpv-zgkx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.199628997s
Jun 25 06:00:43.349: INFO: Pod "pod-subpath-test-dynamicpv-zgkx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.268327058s
STEP: Saw pod success
Jun 25 06:00:43.349: INFO: Pod "pod-subpath-test-dynamicpv-zgkx" satisfied condition "Succeeded or Failed"
Jun 25 06:00:43.416: INFO: Trying to get logs from node ip-192-168-85-247.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-zgkx container test-container-volume-dynamicpv-zgkx: <nil>
STEP: delete the pod
Jun 25 06:00:43.640: INFO: Waiting for pod pod-subpath-test-dynamicpv-zgkx to disappear
Jun 25 06:00:43.708: INFO: Pod pod-subpath-test-dynamicpv-zgkx no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-zgkx
Jun 25 06:00:43.708: INFO: Deleting pod "pod-subpath-test-dynamicpv-zgkx" in namespace "provisioning-2199"
... skipping 499 lines ...
Jun 25 06:00:51.789: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jun 25 06:00:51.862: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.comb7rhg] to have phase Bound
Jun 25 06:00:51.927: INFO: PersistentVolumeClaim efs.csi.aws.comb7rhg found but phase is Pending instead of Bound.
Jun 25 06:00:53.993: INFO: PersistentVolumeClaim efs.csi.aws.comb7rhg found and phase=Bound (2.130363938s)
STEP: Creating pod pod-subpath-test-dynamicpv-w89t
STEP: Creating a pod to test atomic-volume-subpath
Jun 25 06:00:54.246: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-w89t" in namespace "provisioning-156" to be "Succeeded or Failed"
Jun 25 06:00:54.310: INFO: Pod "pod-subpath-test-dynamicpv-w89t": Phase="Pending", Reason="", readiness=false. Elapsed: 64.331974ms
Jun 25 06:00:56.377: INFO: Pod "pod-subpath-test-dynamicpv-w89t": Phase="Pending", Reason="", readiness=false. Elapsed: 2.13140835s
Jun 25 06:00:58.442: INFO: Pod "pod-subpath-test-dynamicpv-w89t": Phase="Running", Reason="", readiness=true. Elapsed: 4.196723131s
Jun 25 06:01:00.508: INFO: Pod "pod-subpath-test-dynamicpv-w89t": Phase="Running", Reason="", readiness=true. Elapsed: 6.262083586s
Jun 25 06:01:02.582: INFO: Pod "pod-subpath-test-dynamicpv-w89t": Phase="Running", Reason="", readiness=true. Elapsed: 8.336792117s
Jun 25 06:01:04.649: INFO: Pod "pod-subpath-test-dynamicpv-w89t": Phase="Running", Reason="", readiness=true. Elapsed: 10.403470414s
... skipping 3 lines ...
Jun 25 06:01:12.916: INFO: Pod "pod-subpath-test-dynamicpv-w89t": Phase="Running", Reason="", readiness=true. Elapsed: 18.670642795s
Jun 25 06:01:14.982: INFO: Pod "pod-subpath-test-dynamicpv-w89t": Phase="Running", Reason="", readiness=true. Elapsed: 20.736852745s
Jun 25 06:01:17.048: INFO: Pod "pod-subpath-test-dynamicpv-w89t": Phase="Running", Reason="", readiness=true. Elapsed: 22.802206447s
Jun 25 06:01:19.115: INFO: Pod "pod-subpath-test-dynamicpv-w89t": Phase="Running", Reason="", readiness=false. Elapsed: 24.869220493s
Jun 25 06:01:21.182: INFO: Pod "pod-subpath-test-dynamicpv-w89t": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.936320075s
STEP: Saw pod success
Jun 25 06:01:21.182: INFO: Pod "pod-subpath-test-dynamicpv-w89t" satisfied condition "Succeeded or Failed"
Jun 25 06:01:21.246: INFO: Trying to get logs from node ip-192-168-85-247.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-w89t container test-container-subpath-dynamicpv-w89t: <nil>
STEP: delete the pod
Jun 25 06:01:21.464: INFO: Waiting for pod pod-subpath-test-dynamicpv-w89t to disappear
Jun 25 06:01:21.533: INFO: Pod pod-subpath-test-dynamicpv-w89t no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-w89t
Jun 25 06:01:21.533: INFO: Deleting pod "pod-subpath-test-dynamicpv-w89t" in namespace "provisioning-156"
... skipping 222 lines ...

    EKS does not allow featureGates so ReadWriteOncePod cannot be enabled

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

[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 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 06:01:20.639: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-15278.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-8553
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 06:01:21.813: INFO: Creating resource for dynamic PV
Jun 25 06:01:21.813: 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 06:01:22.023: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jun 25 06:01:22.096: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.comgknhw] to have phase Bound
Jun 25 06:01:22.163: INFO: PersistentVolumeClaim efs.csi.aws.comgknhw found but phase is Pending instead of Bound.
Jun 25 06:01:24.230: INFO: PersistentVolumeClaim efs.csi.aws.comgknhw found and phase=Bound (2.133650742s)
STEP: Creating pod pod-subpath-test-dynamicpv-z9fh
STEP: Checking for subpath error in container status
Jun 25 06:01:28.583: INFO: Deleting pod "pod-subpath-test-dynamicpv-z9fh" in namespace "provisioning-8553"
Jun 25 06:01:28.652: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-z9fh" to be fully deleted
STEP: Deleting pod
Jun 25 06:01:30.787: INFO: Deleting pod "pod-subpath-test-dynamicpv-z9fh" in namespace "provisioning-8553"
STEP: Deleting pvc
Jun 25 06:01:30.851: INFO: Deleting PersistentVolumeClaim "efs.csi.aws.comgknhw"
... skipping 15 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227
    [Testpattern: Dynamic PV (default fs)] subPath
    /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if non-existent subpath is outside the volume [Slow][LinuxOnly]
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 171 lines ...
Jun 25 06:01:42.296: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jun 25 06:01:42.368: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.com68kwm] to have phase Bound
Jun 25 06:01:42.433: INFO: PersistentVolumeClaim efs.csi.aws.com68kwm found but phase is Pending instead of Bound.
Jun 25 06:01:44.504: INFO: PersistentVolumeClaim efs.csi.aws.com68kwm found and phase=Bound (2.135635557s)
STEP: Creating pod pod-subpath-test-dynamicpv-552s
STEP: Creating a pod to test subpath
Jun 25 06:01:44.718: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-552s" in namespace "provisioning-1528" to be "Succeeded or Failed"
Jun 25 06:01:44.810: INFO: Pod "pod-subpath-test-dynamicpv-552s": Phase="Pending", Reason="", readiness=false. Elapsed: 91.67293ms
Jun 25 06:01:46.876: INFO: Pod "pod-subpath-test-dynamicpv-552s": Phase="Pending", Reason="", readiness=false. Elapsed: 2.157591387s
Jun 25 06:01:48.939: INFO: Pod "pod-subpath-test-dynamicpv-552s": Phase="Pending", Reason="", readiness=false. Elapsed: 4.221173662s
Jun 25 06:01:51.005: INFO: Pod "pod-subpath-test-dynamicpv-552s": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.286999368s
STEP: Saw pod success
Jun 25 06:01:51.005: INFO: Pod "pod-subpath-test-dynamicpv-552s" satisfied condition "Succeeded or Failed"
Jun 25 06:01:51.068: INFO: Trying to get logs from node ip-192-168-85-247.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-552s container test-container-subpath-dynamicpv-552s: <nil>
STEP: delete the pod
Jun 25 06:01:51.266: INFO: Waiting for pod pod-subpath-test-dynamicpv-552s to disappear
Jun 25 06:01:51.329: INFO: Pod pod-subpath-test-dynamicpv-552s no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-552s
Jun 25 06:01:51.329: INFO: Deleting pod "pod-subpath-test-dynamicpv-552s" in namespace "provisioning-1528"
... skipping 421 lines ...
Jun 25 06:02:06.330: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jun 25 06:02:06.406: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.comrmbqv] to have phase Bound
Jun 25 06:02:06.469: INFO: PersistentVolumeClaim efs.csi.aws.comrmbqv found but phase is Pending instead of Bound.
Jun 25 06:02:08.533: INFO: PersistentVolumeClaim efs.csi.aws.comrmbqv found and phase=Bound (2.12697645s)
STEP: Creating pod pod-subpath-test-dynamicpv-2xgj
STEP: Creating a pod to test subpath
Jun 25 06:02:08.790: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-2xgj" in namespace "provisioning-4384" to be "Succeeded or Failed"
Jun 25 06:02:08.855: INFO: Pod "pod-subpath-test-dynamicpv-2xgj": Phase="Pending", Reason="", readiness=false. Elapsed: 65.580023ms
Jun 25 06:02:10.919: INFO: Pod "pod-subpath-test-dynamicpv-2xgj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.129467553s
Jun 25 06:02:12.982: INFO: Pod "pod-subpath-test-dynamicpv-2xgj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.192790532s
Jun 25 06:02:15.047: INFO: Pod "pod-subpath-test-dynamicpv-2xgj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.257767352s
STEP: Saw pod success
Jun 25 06:02:15.047: INFO: Pod "pod-subpath-test-dynamicpv-2xgj" satisfied condition "Succeeded or Failed"
Jun 25 06:02:15.116: INFO: Trying to get logs from node ip-192-168-0-82.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-2xgj container test-container-subpath-dynamicpv-2xgj: <nil>
STEP: delete the pod
Jun 25 06:02:15.331: INFO: Waiting for pod pod-subpath-test-dynamicpv-2xgj to disappear
Jun 25 06:02:15.393: INFO: Pod pod-subpath-test-dynamicpv-2xgj no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-2xgj
Jun 25 06:02:15.393: INFO: Deleting pod "pod-subpath-test-dynamicpv-2xgj" in namespace "provisioning-4384"
... skipping 226 lines ...
Jun 25 06:02:12.407: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jun 25 06:02:12.484: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.com5kwh7] to have phase Bound
Jun 25 06:02:12.549: INFO: PersistentVolumeClaim efs.csi.aws.com5kwh7 found but phase is Pending instead of Bound.
Jun 25 06:02:14.615: INFO: PersistentVolumeClaim efs.csi.aws.com5kwh7 found and phase=Bound (2.130693019s)
STEP: Creating pod exec-volume-test-dynamicpv-dxwn
STEP: Creating a pod to test exec-volume-test
Jun 25 06:02:14.834: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-dxwn" in namespace "volume-8878" to be "Succeeded or Failed"
Jun 25 06:02:14.900: INFO: Pod "exec-volume-test-dynamicpv-dxwn": Phase="Pending", Reason="", readiness=false. Elapsed: 65.625035ms
Jun 25 06:02:16.969: INFO: Pod "exec-volume-test-dynamicpv-dxwn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.134723809s
Jun 25 06:02:19.037: INFO: Pod "exec-volume-test-dynamicpv-dxwn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.202685228s
Jun 25 06:02:21.112: INFO: Pod "exec-volume-test-dynamicpv-dxwn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.277711261s
STEP: Saw pod success
Jun 25 06:02:21.112: INFO: Pod "exec-volume-test-dynamicpv-dxwn" satisfied condition "Succeeded or Failed"
Jun 25 06:02:21.178: INFO: Trying to get logs from node ip-192-168-0-82.us-west-2.compute.internal pod exec-volume-test-dynamicpv-dxwn container exec-container-dynamicpv-dxwn: <nil>
STEP: delete the pod
Jun 25 06:02:21.384: INFO: Waiting for pod exec-volume-test-dynamicpv-dxwn to disappear
Jun 25 06:02:21.450: INFO: Pod exec-volume-test-dynamicpv-dxwn no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-dxwn
Jun 25 06:02:21.450: INFO: Deleting pod "exec-volume-test-dynamicpv-dxwn" in namespace "volume-8878"
... skipping 265 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 06:02:41.125: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-15278.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-7342
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 06:02:42.082: 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 06:02:42.083: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-7342" for this suite.
... skipping 7 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227
    [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
    /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail to use a volume in a pod with mismatched mode [Slow] [It]
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go: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 123 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if non-existent subpath is outside the volume [Slow][LinuxOnly] [BeforeEach]
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:244
------------------------------
... skipping 481 lines ...
Jun 25 06:03:13.358: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jun 25 06:03:13.434: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.com5xblx] to have phase Bound
Jun 25 06:03:13.500: INFO: PersistentVolumeClaim efs.csi.aws.com5xblx found but phase is Pending instead of Bound.
Jun 25 06:03:15.565: INFO: PersistentVolumeClaim efs.csi.aws.com5xblx found and phase=Bound (2.131412989s)
STEP: Creating pod pod-subpath-test-dynamicpv-jg9d
STEP: Creating a pod to test subpath
Jun 25 06:03:15.777: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-jg9d" in namespace "provisioning-9902" to be "Succeeded or Failed"
Jun 25 06:03:15.898: INFO: Pod "pod-subpath-test-dynamicpv-jg9d": Phase="Pending", Reason="", readiness=false. Elapsed: 120.304187ms
Jun 25 06:03:17.965: INFO: Pod "pod-subpath-test-dynamicpv-jg9d": Phase="Pending", Reason="", readiness=false. Elapsed: 2.187679909s
Jun 25 06:03:20.030: INFO: Pod "pod-subpath-test-dynamicpv-jg9d": Phase="Pending", Reason="", readiness=false. Elapsed: 4.253212162s
Jun 25 06:03:22.098: INFO: Pod "pod-subpath-test-dynamicpv-jg9d": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.320702002s
STEP: Saw pod success
Jun 25 06:03:22.098: INFO: Pod "pod-subpath-test-dynamicpv-jg9d" satisfied condition "Succeeded or Failed"
Jun 25 06:03:22.164: INFO: Trying to get logs from node ip-192-168-85-247.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-jg9d container test-container-volume-dynamicpv-jg9d: <nil>
STEP: delete the pod
Jun 25 06:03:22.406: INFO: Waiting for pod pod-subpath-test-dynamicpv-jg9d to disappear
Jun 25 06:03:22.472: INFO: Pod pod-subpath-test-dynamicpv-jg9d no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-jg9d
Jun 25 06:03:22.472: INFO: Deleting pod "pod-subpath-test-dynamicpv-jg9d" in namespace "provisioning-9902"
... skipping 956 lines ...
STEP: Binding the e2e-test-privileged-psp PodSecurityPolicy to the default service account in efs-376
STEP: Waiting for a default service account to be provisioned in namespace
[It] should mount with option tls when encryptInTransit unset
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:363
STEP: Creating efs pvc & pv
STEP: Creating pod to mount pvc "efs-376" and run "mount && mount | grep /mnt/volume1 | grep 127.0.0.1"
Jun 25 06:04:16.387: INFO: Waiting up to 5m0s for pod "pvc-tester-tw49c" in namespace "efs-376" to be "Succeeded or Failed"
Jun 25 06:04:16.455: INFO: Pod "pvc-tester-tw49c": Phase="Pending", Reason="", readiness=false. Elapsed: 67.388392ms
Jun 25 06:04:18.520: INFO: Pod "pvc-tester-tw49c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.132245678s
Jun 25 06:04:20.584: INFO: Pod "pvc-tester-tw49c": Phase="Pending", Reason="", readiness=false. Elapsed: 4.19675689s
Jun 25 06:04:22.649: INFO: Pod "pvc-tester-tw49c": Phase="Pending", Reason="", readiness=false. Elapsed: 6.261824068s
Jun 25 06:04:24.714: INFO: Pod "pvc-tester-tw49c": Phase="Pending", Reason="", readiness=false. Elapsed: 8.326848431s
Jun 25 06:04:26.780: INFO: Pod "pvc-tester-tw49c": Phase="Pending", Reason="", readiness=false. Elapsed: 10.392580781s
Jun 25 06:04:28.845: INFO: Pod "pvc-tester-tw49c": Phase="Pending", Reason="", readiness=false. Elapsed: 12.458122231s
Jun 25 06:04:30.911: INFO: Pod "pvc-tester-tw49c": Phase="Pending", Reason="", readiness=false. Elapsed: 14.523488805s
Jun 25 06:04:32.985: INFO: Pod "pvc-tester-tw49c": Phase="Pending", Reason="", readiness=false. Elapsed: 16.598035424s
Jun 25 06:04:35.053: INFO: Pod "pvc-tester-tw49c": Phase="Pending", Reason="", readiness=false. Elapsed: 18.665629462s
Jun 25 06:04:37.119: INFO: Pod "pvc-tester-tw49c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.732037253s
STEP: Saw pod success
Jun 25 06:04:37.119: INFO: Pod "pvc-tester-tw49c" satisfied condition "Succeeded or Failed"
Jun 25 06:04:37.198: INFO: pod "pvc-tester-tw49c" logs:
 overlay on / type overlay (rw,relatime,lowerdir=/var/lib/docker/overlay2/l/F5XSRBPS4UEVANQFFABDR7LUNP:/var/lib/docker/overlay2/l/4KOBX3KUI2LTU3AGLB7PO66EK3,upperdir=/var/lib/docker/overlay2/673e1a1221885381286b279f1107cf3889568678d30d2ee917194b56abb90484/diff,workdir=/var/lib/docker/overlay2/673e1a1221885381286b279f1107cf3889568678d30d2ee917194b56abb90484/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 469 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227
    [Testpattern: Inline-volume (default fs)] subPath
    /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if non-existent subpath is outside the volume [Slow][LinuxOnly] [BeforeEach]
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

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

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

[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 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 06:04:44.471: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-15278.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-8045
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 06:04:45.618: INFO: Creating resource for dynamic PV
Jun 25 06:04:45.618: 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 06:04:45.808: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jun 25 06:04:45.881: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.comp6gj5] to have phase Bound
Jun 25 06:04:45.953: INFO: PersistentVolumeClaim efs.csi.aws.comp6gj5 found but phase is Pending instead of Bound.
Jun 25 06:04:48.016: INFO: PersistentVolumeClaim efs.csi.aws.comp6gj5 found and phase=Bound (2.135303157s)
STEP: Creating pod pod-subpath-test-dynamicpv-jfv4
STEP: Checking for subpath error in container status
Jun 25 06:04:52.338: INFO: Deleting pod "pod-subpath-test-dynamicpv-jfv4" in namespace "provisioning-8045"
Jun 25 06:04:52.407: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-jfv4" to be fully deleted
STEP: Deleting pod
Jun 25 06:04:54.549: INFO: Deleting pod "pod-subpath-test-dynamicpv-jfv4" in namespace "provisioning-8045"
STEP: Deleting pvc
Jun 25 06:04:54.611: INFO: Deleting PersistentVolumeClaim "efs.csi.aws.comp6gj5"
... skipping 15 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227
    [Testpattern: Dynamic PV (default fs)] subPath
    /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath file is outside the volume [Slow][LinuxOnly]
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 25 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: Pre-provisioned PV (block volmode)] volumeMode 
  should fail to create pod by failing to mount volume [Slow]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:197

[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 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 06:02:52.612: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-15278.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-2019
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 06:02:54.060: INFO: Waiting for PV pvvpbrs to bind to PVC pvc-q5p8c
Jun 25 06:02:54.060: INFO: Waiting up to timeout=3m0s for PersistentVolumeClaims [pvc-q5p8c] to have phase Bound
Jun 25 06:02:54.125: INFO: PersistentVolumeClaim pvc-q5p8c found and phase=Bound (65.041135ms)
... skipping 20 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227
    [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
    /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail to create pod by failing to mount volume [Slow]
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:197
------------------------------
[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 272 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 06:05:06.045: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-15278.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-2930
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 06:05:06.945: 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 06:05:06.946: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-2930" for this suite.
... skipping 7 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227
    [Testpattern: Dynamic PV (block volmode)] volumeMode
    /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail to use a volume in a pod with mismatched mode [Slow] [It]
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go: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:219
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if non-existent subpath is outside the volume [Slow][LinuxOnly] [BeforeEach]
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

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

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

      Driver "efs.csi.aws.com" does not support cloning - skipping

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

[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 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 06:05:02.880: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-15278.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-565
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 06:05:04.016: INFO: Creating resource for dynamic PV
Jun 25 06:05:04.016: 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 06:05:04.220: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jun 25 06:05:04.293: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.com2bbbh] to have phase Bound
Jun 25 06:05:04.358: INFO: PersistentVolumeClaim efs.csi.aws.com2bbbh found but phase is Pending instead of Bound.
Jun 25 06:05:06.425: INFO: PersistentVolumeClaim efs.csi.aws.com2bbbh found and phase=Bound (2.131751396s)
STEP: Creating pod pod-subpath-test-dynamicpv-j97k
STEP: Checking for subpath error in container status
Jun 25 06:05:10.778: INFO: Deleting pod "pod-subpath-test-dynamicpv-j97k" in namespace "provisioning-565"
Jun 25 06:05:10.850: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-j97k" to be fully deleted
STEP: Deleting pod
Jun 25 06:05:12.982: INFO: Deleting pod "pod-subpath-test-dynamicpv-j97k" in namespace "provisioning-565"
STEP: Deleting pvc
Jun 25 06:05:13.050: INFO: Deleting PersistentVolumeClaim "efs.csi.aws.com2bbbh"
... skipping 15 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227
    [Testpattern: Dynamic PV (default fs)] subPath
    /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath directory is outside the volume [Slow][LinuxOnly]
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[efs-csi] EFS CSI [Driver: efs.csi.aws.com] [Testpattern: Dynamic PV (default fs)] subPath 
  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

... skipping 24 lines ...
Jun 25 06:05:20.039: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jun 25 06:05:20.114: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.comdd7vn] to have phase Bound
Jun 25 06:05:20.181: INFO: PersistentVolumeClaim efs.csi.aws.comdd7vn found but phase is Pending instead of Bound.
Jun 25 06:05:22.249: INFO: PersistentVolumeClaim efs.csi.aws.comdd7vn found and phase=Bound (2.134490874s)
STEP: Creating pod pod-subpath-test-dynamicpv-5l5s
STEP: Creating a pod to test subpath
Jun 25 06:05:22.464: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-5l5s" in namespace "provisioning-1053" to be "Succeeded or Failed"
Jun 25 06:05:22.575: INFO: Pod "pod-subpath-test-dynamicpv-5l5s": Phase="Pending", Reason="", readiness=false. Elapsed: 110.848522ms
Jun 25 06:05:24.642: INFO: Pod "pod-subpath-test-dynamicpv-5l5s": Phase="Pending", Reason="", readiness=false. Elapsed: 2.178298702s
Jun 25 06:05:26.711: INFO: Pod "pod-subpath-test-dynamicpv-5l5s": Phase="Pending", Reason="", readiness=false. Elapsed: 4.247373605s
Jun 25 06:05:28.779: INFO: Pod "pod-subpath-test-dynamicpv-5l5s": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.315650956s
STEP: Saw pod success
Jun 25 06:05:28.779: INFO: Pod "pod-subpath-test-dynamicpv-5l5s" satisfied condition "Succeeded or Failed"
Jun 25 06:05:28.847: INFO: Trying to get logs from node ip-192-168-0-82.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-5l5s container test-container-subpath-dynamicpv-5l5s: <nil>
STEP: delete the pod
Jun 25 06:05:29.062: INFO: Waiting for pod pod-subpath-test-dynamicpv-5l5s to disappear
Jun 25 06:05:29.128: INFO: Pod pod-subpath-test-dynamicpv-5l5s no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-5l5s
Jun 25 06:05:29.128: INFO: Deleting pod "pod-subpath-test-dynamicpv-5l5s" in namespace "provisioning-1053"
... skipping 95 lines ...
Jun 25 06:05:29.260: INFO: PersistentVolumeClaim pvc-r9sgj found but phase is Pending instead of Bound.
Jun 25 06:05:31.322: INFO: PersistentVolumeClaim pvc-r9sgj found and phase=Bound (10.381477853s)
Jun 25 06:05:31.323: INFO: Waiting up to 3m0s for PersistentVolume efs.csi.aws.com-wtw4r to have phase Bound
Jun 25 06:05:31.385: INFO: PersistentVolume efs.csi.aws.com-wtw4r found and phase=Bound (62.883079ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-tcdl
STEP: Creating a pod to test exec-volume-test
Jun 25 06:05:31.583: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-tcdl" in namespace "volume-6629" to be "Succeeded or Failed"
Jun 25 06:05:31.645: INFO: Pod "exec-volume-test-preprovisionedpv-tcdl": Phase="Pending", Reason="", readiness=false. Elapsed: 62.087447ms
Jun 25 06:05:33.709: INFO: Pod "exec-volume-test-preprovisionedpv-tcdl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.125620945s
Jun 25 06:05:35.774: INFO: Pod "exec-volume-test-preprovisionedpv-tcdl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.190482644s
STEP: Saw pod success
Jun 25 06:05:35.774: INFO: Pod "exec-volume-test-preprovisionedpv-tcdl" satisfied condition "Succeeded or Failed"
Jun 25 06:05:35.835: INFO: Trying to get logs from node ip-192-168-0-82.us-west-2.compute.internal pod exec-volume-test-preprovisionedpv-tcdl container exec-container-preprovisionedpv-tcdl: <nil>
STEP: delete the pod
Jun 25 06:05:36.034: INFO: Waiting for pod exec-volume-test-preprovisionedpv-tcdl to disappear
Jun 25 06:05:36.097: INFO: Pod exec-volume-test-preprovisionedpv-tcdl no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-tcdl
Jun 25 06:05:36.097: INFO: Deleting pod "exec-volume-test-preprovisionedpv-tcdl" in namespace "volume-6629"
... skipping 44 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227
    [Testpattern: Inline-volume (default fs)] subPath
    /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath file is outside the volume [Slow][LinuxOnly] [BeforeEach]
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

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

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:116
------------------------------
... skipping 461 lines ...
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:233
    should continue reading/writing without hanging after the driver pod is restarted
    /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:269
------------------------------
[efs-csi] EFS CSI [Driver: efs.csi.aws.com] [Testpattern: Dynamic PV (block volmode)] volumeMode 
  should fail in binding dynamic provisioned PV to PVC [Slow][LinuxOnly]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:258

[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 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 06:01:09.678: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-15278.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-6257
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 06:06:11.267: INFO: Warning: did not get event about provisioing failed
STEP: Deleting pvc
Jun 25 06:06:11.403: INFO: Deleting PersistentVolumeClaim "pvc-59sk8"
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 06:06:11.693: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
... skipping 8 lines ...
[efs-csi] EFS CSI
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219
  [Driver: efs.csi.aws.com]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227
    [Testpattern: Dynamic PV (block volmode)] volumeMode
    /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail in binding dynamic provisioned PV to PVC [Slow][LinuxOnly]
      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:258
------------------------------
[efs-csi] EFS CSI [Driver: efs.csi.aws.com] 
  should mount different paths on same volume on same node
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:234

... skipping 7 lines ...
STEP: Binding the e2e-test-privileged-psp PodSecurityPolicy to the default service account in efs-1393
STEP: Waiting for a default service account to be provisioned in namespace
[It] should mount different paths on same volume on same node
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:234
STEP: Creating efs pvc & pv with no subpath
STEP: Creating pod to make subpaths /a and /b
Jun 25 06:05:42.350: INFO: Waiting up to 5m0s for pod "pvc-tester-9v9xs" in namespace "efs-1393" to be "Succeeded or Failed"
Jun 25 06:05:42.414: INFO: Pod "pvc-tester-9v9xs": Phase="Pending", Reason="", readiness=false. Elapsed: 64.207409ms
Jun 25 06:05:44.479: INFO: Pod "pvc-tester-9v9xs": Phase="Pending", Reason="", readiness=false. Elapsed: 2.129283632s
Jun 25 06:05:46.549: INFO: Pod "pvc-tester-9v9xs": Phase="Pending", Reason="", readiness=false. Elapsed: 4.198555604s
Jun 25 06:05:48.617: INFO: Pod "pvc-tester-9v9xs": Phase="Pending", Reason="", readiness=false. Elapsed: 6.266883411s
Jun 25 06:05:50.682: INFO: Pod "pvc-tester-9v9xs": Phase="Pending", Reason="", readiness=false. Elapsed: 8.332108618s
Jun 25 06:05:52.754: INFO: Pod "pvc-tester-9v9xs": Phase="Pending", Reason="", readiness=false. Elapsed: 10.403931746s
... skipping 4 lines ...
Jun 25 06:06:03.088: INFO: Pod "pvc-tester-9v9xs": Phase="Pending", Reason="", readiness=false. Elapsed: 20.738205983s
Jun 25 06:06:05.153: INFO: Pod "pvc-tester-9v9xs": Phase="Pending", Reason="", readiness=false. Elapsed: 22.802766084s
Jun 25 06:06:07.218: INFO: Pod "pvc-tester-9v9xs": Phase="Pending", Reason="", readiness=false. Elapsed: 24.868149775s
Jun 25 06:06:09.285: INFO: Pod "pvc-tester-9v9xs": Phase="Pending", Reason="", readiness=false. Elapsed: 26.935065657s
Jun 25 06:06:11.351: INFO: Pod "pvc-tester-9v9xs": Phase="Succeeded", Reason="", readiness=false. Elapsed: 29.001038434s
STEP: Saw pod success
Jun 25 06:06:11.351: INFO: Pod "pvc-tester-9v9xs" 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 06:06:42.050: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
... skipping 10 lines ...
------------------------------
STEP: Deleting EFS filesystem "fs-0c7556f6e4e09d36e"
STEP: Deleted EFS filesystem "fs-0c7556f6e4e09d36e"


Ran 35 of 189 Specs in 552.621 seconds
SUCCESS! -- 35 Passed | 0 Failed | 0 Pending | 154 Skipped


Ginkgo ran 1 suite in 10m20.560443249s
Test Suite Passed
+ TEST_PASSED=0
+ set -e
... skipping 1152 lines ...
I0625 06:01:48.238814       1 reaper.go:107] reaper: waited for process &{67 1 90 67 67 stunnel}
I0625 06:02:09.279756       1 reaper.go:107] reaper: waited for process &{94 1 90 94 94 stunnel}
I0625 06:02:17.296105       1 reaper.go:107] reaper: waited for process &{111 1 90 111 111 stunnel}
I0625 06:02:54.528862       1 node.go:287] NodeGetCapabilities: called with args 
I0625 06:02:54.529926       1 node.go:287] NodeGetCapabilities: called with args 
I0625 06:02:54.543129       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-0c7556f6e4e09d36e" staging_target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pvvpbrs" target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pvvpbrs/3dc4089c-7769-4d82-9724-b0088539c025" volume_capability:<block:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > 
E0625 06:02:54.543189       1 driver.go:107] GRPC error: rpc error: code = InvalidArgument desc = Volume capability not supported: only filesystem volumes are supported
I0625 06:02:55.134908       1 node.go:287] NodeGetCapabilities: called with args 
I0625 06:02:55.135837       1 node.go:287] NodeGetCapabilities: called with args 
I0625 06:02:55.136617       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-0c7556f6e4e09d36e" staging_target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pvvpbrs" target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pvvpbrs/3dc4089c-7769-4d82-9724-b0088539c025" volume_capability:<block:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > 
E0625 06:02:55.136668       1 driver.go:107] GRPC error: rpc error: code = InvalidArgument desc = Volume capability not supported: only filesystem volumes are supported
I0625 06:02:56.144070       1 node.go:287] NodeGetCapabilities: called with args 
I0625 06:02:56.144753       1 node.go:287] NodeGetCapabilities: called with args 
I0625 06:02:56.145409       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-0c7556f6e4e09d36e" staging_target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pvvpbrs" target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pvvpbrs/3dc4089c-7769-4d82-9724-b0088539c025" volume_capability:<block:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > 
E0625 06:02:56.145460       1 driver.go:107] GRPC error: rpc error: code = InvalidArgument desc = Volume capability not supported: only filesystem volumes are supported
I0625 06:02:58.162027       1 node.go:287] NodeGetCapabilities: called with args 
I0625 06:02:58.162824       1 node.go:287] NodeGetCapabilities: called with args 
I0625 06:02:58.163483       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-0c7556f6e4e09d36e" staging_target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pvvpbrs" target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pvvpbrs/3dc4089c-7769-4d82-9724-b0088539c025" volume_capability:<block:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > 
E0625 06:02:58.163525       1 driver.go:107] GRPC error: rpc error: code = InvalidArgument desc = Volume capability not supported: only filesystem volumes are supported
I0625 06:03:02.198438       1 node.go:287] NodeGetCapabilities: called with args 
I0625 06:03:02.199225       1 node.go:287] NodeGetCapabilities: called with args 
I0625 06:03:02.201536       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-0c7556f6e4e09d36e" staging_target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pvvpbrs" target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pvvpbrs/3dc4089c-7769-4d82-9724-b0088539c025" volume_capability:<block:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > 
E0625 06:03:02.201586       1 driver.go:107] GRPC error: rpc error: code = InvalidArgument desc = Volume capability not supported: only filesystem volumes are supported
I0625 06:03:10.269263       1 node.go:287] NodeGetCapabilities: called with args 
I0625 06:03:10.270182       1 node.go:287] NodeGetCapabilities: called with args 
I0625 06:03:10.270668       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-0c7556f6e4e09d36e" staging_target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pvvpbrs" target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pvvpbrs/3dc4089c-7769-4d82-9724-b0088539c025" volume_capability:<block:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > 
E0625 06:03:10.270710       1 driver.go:107] GRPC error: rpc error: code = InvalidArgument desc = Volume capability not supported: only filesystem volumes are supported
I0625 06:03:26.308988       1 node.go:287] NodeGetCapabilities: called with args 
I0625 06:03:26.310008       1 node.go:287] NodeGetCapabilities: called with args 
I0625 06:03:26.310530       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-0c7556f6e4e09d36e" staging_target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pvvpbrs" target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pvvpbrs/3dc4089c-7769-4d82-9724-b0088539c025" volume_capability:<block:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > 
E0625 06:03:26.310578       1 driver.go:107] GRPC error: rpc error: code = InvalidArgument desc = Volume capability not supported: only filesystem volumes are supported
I0625 06:03:58.406267       1 node.go:287] NodeGetCapabilities: called with args 
I0625 06:03:58.407246       1 node.go:287] NodeGetCapabilities: called with args 
I0625 06:03:58.407789       1 node.go:54] NodePublishVolume: called with args volume_id:"fs-0c7556f6e4e09d36e" staging_target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pvvpbrs" target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pvvpbrs/3dc4089c-7769-4d82-9724-b0088539c025" volume_capability:<block:<> access_mode:<mode:SINGLE_NODE_MULTI_WRITER > > 
E0625 06:03:58.407836       1 driver.go:107] GRPC error: rpc error: code = InvalidArgument desc = Volume capability not supported: only filesystem volumes are supported
###
## Printing pod efs-csi-node-x6ln8 efs-plugin container logs
#
I0625 06:05:59.819267       1 config_dir.go:87] Creating symlink from '/etc/amazon/efs' to '/var/amazon/efs'
I0625 06:05:59.820477       1 metadata.go:63] getting MetadataService...
I0625 06:05:59.822378       1 metadata.go:68] retrieving metadata from EC2 metadata service
... skipping 46 lines ...
2022-06-25 06:07:15 [ℹ]  waiting for stack "eksctl-test-cluster-15278-k8s-local-nodegroup-ng-0156516e" to get deleted
2022-06-25 06:07:15 [ℹ]  waiting for CloudFormation stack "eksctl-test-cluster-15278-k8s-local-nodegroup-ng-0156516e"
2022-06-25 06:07:46 [ℹ]  waiting for CloudFormation stack "eksctl-test-cluster-15278-k8s-local-nodegroup-ng-0156516e"
2022-06-25 06:08:27 [ℹ]  waiting for CloudFormation stack "eksctl-test-cluster-15278-k8s-local-nodegroup-ng-0156516e"
2022-06-25 06:10:15 [ℹ]  waiting for CloudFormation stack "eksctl-test-cluster-15278-k8s-local-nodegroup-ng-0156516e"
2022-06-25 06:11:40 [ℹ]  waiting for CloudFormation stack "eksctl-test-cluster-15278-k8s-local-nodegroup-ng-0156516e"
{"component":"entrypoint","file":"k8s.io/test-infra/prow/entrypoint/run.go:169","func":"k8s.io/test-infra/prow/entrypoint.Options.ExecuteProcess","level":"error","msg":"Entrypoint received interrupt: terminated","severity":"error","time":"2022-06-25T06:12:36Z"}
++ early_exit_handler
++ '[' -n 177 ']'
++ kill -TERM 177
++ cleanup_dind
++ [[ true == \t\r\u\e ]]
++ echo 'Cleaning up after docker'
... skipping 5 lines ...