This job view page is being replaced by Spyglass soon. Check out the new job view.
PRtorredil: Prepare for release v1.7.0
ResultABORTED
Tests 0 failed / 69 succeeded
Started2022-06-20 19:42
Elapsed26m6s
Revision7a4d05ea4f51fbb5a4696361342a19cb373f2247
Refs 1282

No Test Failures!


Show 69 Passed Tests

Show 416 Skipped Tests

Error lines from build-log.txt

... skipping 428 lines ...
#9 [builder 2/4] WORKDIR /go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver
#9 ...

#8 [linux-amazon 2/3] RUN yum update -y &&     yum install ca-certificates e2fsprogs xfsprogs util-linux -y &&     yum clean all
#8 14.56   Installing : 1:dbus-libs-1.10.24-7.amzn2.x86_64                         27/32 
#8 15.63   Installing : systemd-219-78.amzn2.0.18.x86_64                           28/32 
#8 16.49 Failed to get D-Bus connection: Operation not permitted
#8 16.76   Installing : elfutils-default-yama-scope-0.176-2.amzn2.noarch           29/32 
#8 17.25   Installing : 1:dbus-1.10.24-7.amzn2.x86_64                              30/32 
#8 17.72   Installing : e2fsprogs-1.42.9-19.amzn2.x86_64                           31/32 
#8 18.44   Installing : xfsprogs-4.5.0-18.amzn2.0.1.x86_64                         32/32 
#8 19.64   Verifying  : libfdisk-2.30.2-2.amzn2.0.7.x86_64                          1/32 
#8 19.71   Verifying  : gzip-1.5-10.amzn2.0.1.x86_64                                2/32 
... skipping 216 lines ...
## Validating cluster test-cluster-10232.k8s.local
#
Using cluster from kubectl context: test-cluster-10232.k8s.local

Validating cluster test-cluster-10232.k8s.local

W0620 19:44:35.975310    6271 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-10232-k8-dml7f6-2015379490.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-10232-k8-dml7f6-2015379490.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0620 19:44:46.011252    6271 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-10232-k8-dml7f6-2015379490.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-10232-k8-dml7f6-2015379490.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0620 19:44:56.045699    6271 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-10232-k8-dml7f6-2015379490.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-10232-k8-dml7f6-2015379490.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0620 19:45:06.091332    6271 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-10232-k8-dml7f6-2015379490.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-10232-k8-dml7f6-2015379490.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0620 19:45:16.123904    6271 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-10232-k8-dml7f6-2015379490.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-10232-k8-dml7f6-2015379490.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0620 19:45:26.180335    6271 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-10232-k8-dml7f6-2015379490.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-10232-k8-dml7f6-2015379490.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0620 19:45:36.219324    6271 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-10232-k8-dml7f6-2015379490.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-10232-k8-dml7f6-2015379490.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0620 19:45:46.253351    6271 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-10232-k8-dml7f6-2015379490.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-10232-k8-dml7f6-2015379490.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0620 19:45:56.286959    6271 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-10232-k8-dml7f6-2015379490.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-10232-k8-dml7f6-2015379490.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0620 19:46:06.341030    6271 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-10232-k8-dml7f6-2015379490.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-10232-k8-dml7f6-2015379490.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0620 19:46:25.685025    6271 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-10232-k8-dml7f6-2015379490.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-10232-k8-dml7f6-2015379490.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0620 19:46:48.367451    6271 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: an error on the server ("") has prevented the request from succeeding (get nodes)
W0620 19:47:09.948856    6271 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: an error on the server ("") has prevented the request from succeeding (get nodes)
W0620 19:47:31.535412    6271 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: an error on the server ("") has prevented the request from succeeding (get nodes)
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	t3.medium	1	1	us-west-2a
nodes-us-west-2a	Node	c5.large	1	1	us-west-2a
nodes-us-west-2b	Node	c5.large	1	1	us-west-2b
nodes-us-west-2c	Node	c5.large	1	1	us-west-2c
... skipping 6 lines ...
KIND	NAME						MESSAGE
Machine	i-022cea00ea59a6d0c				machine "i-022cea00ea59a6d0c" has not yet joined cluster
Machine	i-06d3b870fb962660f				machine "i-06d3b870fb962660f" has not yet joined cluster
Machine	i-0f810c6872e4c8a1c				machine "i-0f810c6872e4c8a1c" has not yet joined cluster
Node	ip-172-20-40-170.us-west-2.compute.internal	node "ip-172-20-40-170.us-west-2.compute.internal" of role "master" is not ready

Validation Failed
W0620 19:47:47.718286    6271 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	t3.medium	1	1	us-west-2a
nodes-us-west-2a	Node	c5.large	1	1	us-west-2a
nodes-us-west-2b	Node	c5.large	1	1	us-west-2b
... skipping 12 lines ...
Node	ip-172-20-40-170.us-west-2.compute.internal	master "ip-172-20-40-170.us-west-2.compute.internal" is missing kube-controller-manager pod
Node	ip-172-20-40-170.us-west-2.compute.internal	master "ip-172-20-40-170.us-west-2.compute.internal" is missing kube-scheduler pod
Pod	kube-system/coredns-8f5559c9b-qlk76		system-cluster-critical pod "coredns-8f5559c9b-qlk76" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-b6j5v	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-b6j5v" is pending
Pod	kube-system/kops-controller-fhtrc		system-node-critical pod "kops-controller-fhtrc" is pending

Validation Failed
W0620 19:48:00.230319    6271 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	t3.medium	1	1	us-west-2a
nodes-us-west-2a	Node	c5.large	1	1	us-west-2a
nodes-us-west-2b	Node	c5.large	1	1	us-west-2b
... skipping 11 lines ...
Node	ip-172-20-40-170.us-west-2.compute.internal	master "ip-172-20-40-170.us-west-2.compute.internal" is missing kube-apiserver pod
Node	ip-172-20-40-170.us-west-2.compute.internal	master "ip-172-20-40-170.us-west-2.compute.internal" is missing kube-controller-manager pod
Node	ip-172-20-40-170.us-west-2.compute.internal	master "ip-172-20-40-170.us-west-2.compute.internal" is missing kube-scheduler pod
Pod	kube-system/coredns-8f5559c9b-qlk76		system-cluster-critical pod "coredns-8f5559c9b-qlk76" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-b6j5v	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-b6j5v" is pending

Validation Failed
W0620 19:48:12.397884    6271 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	t3.medium	1	1	us-west-2a
nodes-us-west-2a	Node	c5.large	1	1	us-west-2a
nodes-us-west-2b	Node	c5.large	1	1	us-west-2b
... skipping 9 lines ...
Machine	i-06d3b870fb962660f				machine "i-06d3b870fb962660f" has not yet joined cluster
Machine	i-0f810c6872e4c8a1c				machine "i-0f810c6872e4c8a1c" has not yet joined cluster
Node	ip-172-20-40-170.us-west-2.compute.internal	master "ip-172-20-40-170.us-west-2.compute.internal" is missing kube-scheduler pod
Pod	kube-system/coredns-8f5559c9b-qlk76		system-cluster-critical pod "coredns-8f5559c9b-qlk76" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-b6j5v	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-b6j5v" is pending

Validation Failed
W0620 19:48:25.018133    6271 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	t3.medium	1	1	us-west-2a
nodes-us-west-2a	Node	c5.large	1	1	us-west-2a
nodes-us-west-2b	Node	c5.large	1	1	us-west-2b
... skipping 13 lines ...
Node	ip-172-20-59-7.us-west-2.compute.internal				node "ip-172-20-59-7.us-west-2.compute.internal" of role "node" is not ready
Node	ip-172-20-92-245.us-west-2.compute.internal				node "ip-172-20-92-245.us-west-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-8f5559c9b-qlk76					system-cluster-critical pod "coredns-8f5559c9b-qlk76" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-b6j5v				system-cluster-critical pod "coredns-autoscaler-6f594f4c58-b6j5v" is pending
Pod	kube-system/kube-scheduler-ip-172-20-40-170.us-west-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-40-170.us-west-2.compute.internal" is pending

Validation Failed
W0620 19:48:37.289778    6271 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	t3.medium	1	1	us-west-2a
nodes-us-west-2a	Node	c5.large	1	1	us-west-2a
nodes-us-west-2b	Node	c5.large	1	1	us-west-2b
... skipping 8 lines ...

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-8f5559c9b-ppzlm	system-cluster-critical pod "coredns-8f5559c9b-ppzlm" is pending
Pod	kube-system/coredns-8f5559c9b-qlk76	system-cluster-critical pod "coredns-8f5559c9b-qlk76" is not ready (coredns)

Validation Failed
W0620 19:48:49.406377    6271 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	t3.medium	1	1	us-west-2a
nodes-us-west-2a	Node	c5.large	1	1	us-west-2a
nodes-us-west-2b	Node	c5.large	1	1	us-west-2b
... skipping 88 lines ...
[ebs-csi-migration] EBS CSI Migration
/home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-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-ebs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Distro debian doesn't support ntfs -- skipping

      /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 104 lines ...
[ebs-csi-migration] EBS CSI Migration
/home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-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-ebs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:236
------------------------------
... skipping 128 lines ...
Jun 20 19:51:03.360: INFO: PersistentVolumeClaim pvc-xj7jl found but phase is Pending instead of Bound.
Jun 20 19:51:05.425: INFO: PersistentVolumeClaim pvc-xj7jl found and phase=Bound (14.531508091s)
Jun 20 19:51:05.425: INFO: Waiting up to 3m0s for PersistentVolume aws-q5k45 to have phase Bound
Jun 20 19:51:05.490: INFO: PersistentVolume aws-q5k45 found and phase=Bound (64.66432ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-92hl
STEP: Creating a pod to test exec-volume-test
Jun 20 19:51:05.694: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-92hl" in namespace "volume-6425" to be "Succeeded or Failed"
Jun 20 19:51:05.759: INFO: Pod "exec-volume-test-preprovisionedpv-92hl": Phase="Pending", Reason="", readiness=false. Elapsed: 64.597594ms
Jun 20 19:51:07.825: INFO: Pod "exec-volume-test-preprovisionedpv-92hl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.130871455s
Jun 20 19:51:09.893: INFO: Pod "exec-volume-test-preprovisionedpv-92hl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.198565751s
Jun 20 19:51:11.963: INFO: Pod "exec-volume-test-preprovisionedpv-92hl": Phase="Pending", Reason="", readiness=false. Elapsed: 6.268539942s
Jun 20 19:51:14.028: INFO: Pod "exec-volume-test-preprovisionedpv-92hl": Phase="Pending", Reason="", readiness=false. Elapsed: 8.334083802s
Jun 20 19:51:16.094: INFO: Pod "exec-volume-test-preprovisionedpv-92hl": Phase="Pending", Reason="", readiness=false. Elapsed: 10.399966616s
Jun 20 19:51:18.166: INFO: Pod "exec-volume-test-preprovisionedpv-92hl": Phase="Pending", Reason="", readiness=false. Elapsed: 12.472083673s
Jun 20 19:51:20.232: INFO: Pod "exec-volume-test-preprovisionedpv-92hl": Phase="Pending", Reason="", readiness=false. Elapsed: 14.537510768s
Jun 20 19:51:22.297: INFO: Pod "exec-volume-test-preprovisionedpv-92hl": Phase="Pending", Reason="", readiness=false. Elapsed: 16.6028643s
Jun 20 19:51:24.362: INFO: Pod "exec-volume-test-preprovisionedpv-92hl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.668363991s
STEP: Saw pod success
Jun 20 19:51:24.363: INFO: Pod "exec-volume-test-preprovisionedpv-92hl" satisfied condition "Succeeded or Failed"
Jun 20 19:51:24.427: INFO: Trying to get logs from node ip-172-20-59-7.us-west-2.compute.internal pod exec-volume-test-preprovisionedpv-92hl container exec-container-preprovisionedpv-92hl: <nil>
STEP: delete the pod
Jun 20 19:51:24.584: INFO: Waiting for pod exec-volume-test-preprovisionedpv-92hl to disappear
Jun 20 19:51:24.649: INFO: Pod exec-volume-test-preprovisionedpv-92hl no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-92hl
Jun 20 19:51:24.649: INFO: Deleting pod "exec-volume-test-preprovisionedpv-92hl" in namespace "volume-6425"
STEP: Deleting pv and pvc
Jun 20 19:51:24.713: INFO: Deleting PersistentVolumeClaim "pvc-xj7jl"
Jun 20 19:51:24.779: INFO: Deleting PersistentVolume "aws-q5k45"
Jun 20 19:51:24.992: INFO: Couldn't delete PD "aws://us-west-2a/vol-05dfb9c429642f0e3", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05dfb9c429642f0e3 is currently attached to i-0f810c6872e4c8a1c
	status code: 400, request id: d4a862cd-3bf7-41f0-8a49-189adcdb0083
Jun 20 19:51:30.344: INFO: Couldn't delete PD "aws://us-west-2a/vol-05dfb9c429642f0e3", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05dfb9c429642f0e3 is currently attached to i-0f810c6872e4c8a1c
	status code: 400, request id: c1af09fe-c646-45c8-aefd-79cf1307953c
Jun 20 19:51:35.702: INFO: Couldn't delete PD "aws://us-west-2a/vol-05dfb9c429642f0e3", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05dfb9c429642f0e3 is currently attached to i-0f810c6872e4c8a1c
	status code: 400, request id: 2ca86160-059a-4d52-8fe3-75d8a550b70b
Jun 20 19:51:41.079: INFO: Couldn't delete PD "aws://us-west-2a/vol-05dfb9c429642f0e3", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05dfb9c429642f0e3 is currently attached to i-0f810c6872e4c8a1c
	status code: 400, request id: 0c378a26-6fbf-4e05-8035-a3cddd7da487
Jun 20 19:51:46.508: INFO: Successfully deleted PD "aws://us-west-2a/vol-05dfb9c429642f0e3".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 20 19:51:46.509: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-6425" for this suite.
... skipping 206 lines ...

          Driver "aws" does not support snapshots - skipping

          /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:94
------------------------------
[ebs-csi-migration] EBS CSI Migration [Driver: aws] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode 
  should fail to use a volume in a pod with mismatched mode [Slow]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:297

[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 20 19:51:44.938: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-10232.k8s.local.kops.kubeconfig
STEP: Building a namespace api object, basename volumemode
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail to use a volume in a pod with mismatched mode [Slow]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:297
Jun 20 19:51:45.249: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 20 19:51:45.249: INFO: Creating resource for dynamic PV
Jun 20 19:51:45.249: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-6870vwctg
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 20 19:51:51.693: INFO: Deleting pod "pod-02425db8-3ddd-4531-8760-1de0d4b39af8" in namespace "volumemode-6870"
Jun 20 19:51:51.756: INFO: Wait up to 5m0s for pod "pod-02425db8-3ddd-4531-8760-1de0d4b39af8" to be fully deleted
STEP: Deleting pvc
Jun 20 19:52:02.011: INFO: Deleting PersistentVolumeClaim "awsh2wlq"
Jun 20 19:52:02.077: INFO: Waiting up to 5m0s for PersistentVolume pvc-7a4a9507-0f2a-4b43-88df-0ffaffaa570f to get deleted
Jun 20 19:52:02.141: INFO: PersistentVolume pvc-7a4a9507-0f2a-4b43-88df-0ffaffaa570f found and phase=Released (63.653457ms)
... skipping 9 lines ...
[ebs-csi-migration] EBS CSI Migration
/home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
    /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-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]
      /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:297
------------------------------
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral
  /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral
  /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 97 lines ...
Jun 20 19:51:46.198: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 20 19:51:46.770: INFO: Successfully created a new PD: "aws://us-west-2a/vol-087efb9a113d843cf".
Jun 20 19:51:46.770: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-2xjj
STEP: Creating a pod to test exec-volume-test
Jun 20 19:51:46.838: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-2xjj" in namespace "volume-3148" to be "Succeeded or Failed"
Jun 20 19:51:46.902: INFO: Pod "exec-volume-test-inlinevolume-2xjj": Phase="Pending", Reason="", readiness=false. Elapsed: 64.169404ms
Jun 20 19:51:48.967: INFO: Pod "exec-volume-test-inlinevolume-2xjj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.129429067s
Jun 20 19:51:51.032: INFO: Pod "exec-volume-test-inlinevolume-2xjj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.193720725s
Jun 20 19:51:53.096: INFO: Pod "exec-volume-test-inlinevolume-2xjj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.258174347s
Jun 20 19:51:55.162: INFO: Pod "exec-volume-test-inlinevolume-2xjj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.323898075s
Jun 20 19:51:57.226: INFO: Pod "exec-volume-test-inlinevolume-2xjj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.388207407s
STEP: Saw pod success
Jun 20 19:51:57.226: INFO: Pod "exec-volume-test-inlinevolume-2xjj" satisfied condition "Succeeded or Failed"
Jun 20 19:51:57.290: INFO: Trying to get logs from node ip-172-20-59-7.us-west-2.compute.internal pod exec-volume-test-inlinevolume-2xjj container exec-container-inlinevolume-2xjj: <nil>
STEP: delete the pod
Jun 20 19:51:57.426: INFO: Waiting for pod exec-volume-test-inlinevolume-2xjj to disappear
Jun 20 19:51:57.490: INFO: Pod exec-volume-test-inlinevolume-2xjj no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-2xjj
Jun 20 19:51:57.490: INFO: Deleting pod "exec-volume-test-inlinevolume-2xjj" in namespace "volume-3148"
Jun 20 19:51:57.704: INFO: Couldn't delete PD "aws://us-west-2a/vol-087efb9a113d843cf", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-087efb9a113d843cf is currently attached to i-0f810c6872e4c8a1c
	status code: 400, request id: 7c3b793d-02f2-48b3-8fa9-b60d9c415007
Jun 20 19:52:03.055: INFO: Couldn't delete PD "aws://us-west-2a/vol-087efb9a113d843cf", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-087efb9a113d843cf is currently attached to i-0f810c6872e4c8a1c
	status code: 400, request id: 73ef2b53-3520-42b6-871d-d673dfc45cd8
Jun 20 19:52:08.415: INFO: Couldn't delete PD "aws://us-west-2a/vol-087efb9a113d843cf", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-087efb9a113d843cf is currently attached to i-0f810c6872e4c8a1c
	status code: 400, request id: cab61da6-6a1d-4a66-a3f9-329767d262b5
Jun 20 19:52:13.882: INFO: Successfully deleted PD "aws://us-west-2a/vol-087efb9a113d843cf".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 20 19:52:13.882: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-3148" for this suite.
... skipping 89 lines ...
[ebs-csi-migration] EBS CSI Migration
/home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-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-ebs-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-ebs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:236
------------------------------
... skipping 68 lines ...
Jun 20 19:52:02.850: INFO: PersistentVolumeClaim pvc-rr4gg found but phase is Pending instead of Bound.
Jun 20 19:52:04.911: INFO: PersistentVolumeClaim pvc-rr4gg found and phase=Bound (6.244221838s)
Jun 20 19:52:04.911: INFO: Waiting up to 3m0s for PersistentVolume aws-brkj7 to have phase Bound
Jun 20 19:52:04.975: INFO: PersistentVolume aws-brkj7 found and phase=Bound (63.609342ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-ttvm
STEP: Creating a pod to test exec-volume-test
Jun 20 19:52:05.158: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-ttvm" in namespace "volume-7192" to be "Succeeded or Failed"
Jun 20 19:52:05.218: INFO: Pod "exec-volume-test-preprovisionedpv-ttvm": Phase="Pending", Reason="", readiness=false. Elapsed: 60.32517ms
Jun 20 19:52:07.279: INFO: Pod "exec-volume-test-preprovisionedpv-ttvm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.12118801s
Jun 20 19:52:09.341: INFO: Pod "exec-volume-test-preprovisionedpv-ttvm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.18346328s
Jun 20 19:52:11.403: INFO: Pod "exec-volume-test-preprovisionedpv-ttvm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.245197194s
Jun 20 19:52:13.463: INFO: Pod "exec-volume-test-preprovisionedpv-ttvm": Phase="Pending", Reason="", readiness=false. Elapsed: 8.305689129s
Jun 20 19:52:15.525: INFO: Pod "exec-volume-test-preprovisionedpv-ttvm": Phase="Pending", Reason="", readiness=false. Elapsed: 10.367164096s
Jun 20 19:52:17.586: INFO: Pod "exec-volume-test-preprovisionedpv-ttvm": Phase="Pending", Reason="", readiness=false. Elapsed: 12.427967477s
Jun 20 19:52:19.648: INFO: Pod "exec-volume-test-preprovisionedpv-ttvm": Phase="Pending", Reason="", readiness=false. Elapsed: 14.490695741s
Jun 20 19:52:21.711: INFO: Pod "exec-volume-test-preprovisionedpv-ttvm": Phase="Pending", Reason="", readiness=false. Elapsed: 16.553171647s
Jun 20 19:52:23.773: INFO: Pod "exec-volume-test-preprovisionedpv-ttvm": Phase="Running", Reason="", readiness=true. Elapsed: 18.615185445s
Jun 20 19:52:25.835: INFO: Pod "exec-volume-test-preprovisionedpv-ttvm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.677408958s
STEP: Saw pod success
Jun 20 19:52:25.835: INFO: Pod "exec-volume-test-preprovisionedpv-ttvm" satisfied condition "Succeeded or Failed"
Jun 20 19:52:25.896: INFO: Trying to get logs from node ip-172-20-59-7.us-west-2.compute.internal pod exec-volume-test-preprovisionedpv-ttvm container exec-container-preprovisionedpv-ttvm: <nil>
STEP: delete the pod
Jun 20 19:52:26.026: INFO: Waiting for pod exec-volume-test-preprovisionedpv-ttvm to disappear
Jun 20 19:52:26.086: INFO: Pod exec-volume-test-preprovisionedpv-ttvm no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-ttvm
Jun 20 19:52:26.086: INFO: Deleting pod "exec-volume-test-preprovisionedpv-ttvm" in namespace "volume-7192"
STEP: Deleting pv and pvc
Jun 20 19:52:26.148: INFO: Deleting PersistentVolumeClaim "pvc-rr4gg"
Jun 20 19:52:26.213: INFO: Deleting PersistentVolume "aws-brkj7"
Jun 20 19:52:26.442: INFO: Couldn't delete PD "aws://us-west-2a/vol-02351ad95140392de", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02351ad95140392de is currently attached to i-0f810c6872e4c8a1c
	status code: 400, request id: 3b8c8f00-4714-4909-9964-bab14a3eb158
Jun 20 19:52:31.874: INFO: Successfully deleted PD "aws://us-west-2a/vol-02351ad95140392de".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 20 19:52:31.874: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-7192" for this suite.
... skipping 40 lines ...

      /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/multivolume.go:255
------------------------------
SSSS
------------------------------
[ebs-csi-migration] EBS CSI Migration [Driver: aws] [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-ebs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 20 19:52:08.376: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-10232.k8s.local.kops.kubeconfig
STEP: Building a namespace api object, basename provisioning
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail if subpath directory is outside the volume [Slow][LinuxOnly]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun 20 19:52:08.705: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 20 19:52:08.705: INFO: Creating resource for dynamic PV
Jun 20 19:52:08.705: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-823489wgp
STEP: creating a claim
Jun 20 19:52:08.771: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-tdtc
STEP: Checking for subpath error in container status
Jun 20 19:52:21.116: INFO: Deleting pod "pod-subpath-test-dynamicpv-tdtc" in namespace "provisioning-8234"
Jun 20 19:52:21.197: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-tdtc" to be fully deleted
STEP: Deleting pod
Jun 20 19:52:31.321: INFO: Deleting pod "pod-subpath-test-dynamicpv-tdtc" in namespace "provisioning-8234"
STEP: Deleting pvc
Jun 20 19:52:31.506: INFO: Deleting PersistentVolumeClaim "awsv69fk"
... skipping 12 lines ...
[ebs-csi-migration] EBS CSI Migration
/home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-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-ebs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 20 19:52:41.969: INFO: Driver supports dynamic provisioning, skipping PreprovisionedPV pattern
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow]
... skipping 108 lines ...
[ebs-csi-migration] EBS CSI Migration
/home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-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-ebs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Distro debian doesn't support ntfs -- skipping

      /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 117 lines ...
[ebs-csi-migration] EBS CSI Migration
/home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-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-ebs-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-ebs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:236
------------------------------
... skipping 131 lines ...
Jun 20 19:52:33.311: INFO: PersistentVolumeClaim pvc-2cqpn found but phase is Pending instead of Bound.
Jun 20 19:52:35.372: INFO: PersistentVolumeClaim pvc-2cqpn found and phase=Bound (2.12195947s)
Jun 20 19:52:35.372: INFO: Waiting up to 3m0s for PersistentVolume aws-wrmt4 to have phase Bound
Jun 20 19:52:35.433: INFO: PersistentVolume aws-wrmt4 found and phase=Bound (60.479346ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-plbl
STEP: Creating a pod to test exec-volume-test
Jun 20 19:52:35.616: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-plbl" in namespace "volume-145" to be "Succeeded or Failed"
Jun 20 19:52:35.677: INFO: Pod "exec-volume-test-preprovisionedpv-plbl": Phase="Pending", Reason="", readiness=false. Elapsed: 61.077134ms
Jun 20 19:52:37.738: INFO: Pod "exec-volume-test-preprovisionedpv-plbl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.121781708s
Jun 20 19:52:39.800: INFO: Pod "exec-volume-test-preprovisionedpv-plbl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.183933746s
Jun 20 19:52:41.861: INFO: Pod "exec-volume-test-preprovisionedpv-plbl": Phase="Pending", Reason="", readiness=false. Elapsed: 6.245301069s
Jun 20 19:52:43.923: INFO: Pod "exec-volume-test-preprovisionedpv-plbl": Phase="Pending", Reason="", readiness=false. Elapsed: 8.307373901s
Jun 20 19:52:45.985: INFO: Pod "exec-volume-test-preprovisionedpv-plbl": Phase="Pending", Reason="", readiness=false. Elapsed: 10.369231299s
Jun 20 19:52:48.048: INFO: Pod "exec-volume-test-preprovisionedpv-plbl": Phase="Pending", Reason="", readiness=false. Elapsed: 12.432056085s
Jun 20 19:52:50.110: INFO: Pod "exec-volume-test-preprovisionedpv-plbl": Phase="Pending", Reason="", readiness=false. Elapsed: 14.494135127s
Jun 20 19:52:52.171: INFO: Pod "exec-volume-test-preprovisionedpv-plbl": Phase="Pending", Reason="", readiness=false. Elapsed: 16.555410129s
Jun 20 19:52:54.233: INFO: Pod "exec-volume-test-preprovisionedpv-plbl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.616853718s
STEP: Saw pod success
Jun 20 19:52:54.233: INFO: Pod "exec-volume-test-preprovisionedpv-plbl" satisfied condition "Succeeded or Failed"
Jun 20 19:52:54.293: INFO: Trying to get logs from node ip-172-20-59-7.us-west-2.compute.internal pod exec-volume-test-preprovisionedpv-plbl container exec-container-preprovisionedpv-plbl: <nil>
STEP: delete the pod
Jun 20 19:52:54.424: INFO: Waiting for pod exec-volume-test-preprovisionedpv-plbl to disappear
Jun 20 19:52:54.484: INFO: Pod exec-volume-test-preprovisionedpv-plbl no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-plbl
Jun 20 19:52:54.484: INFO: Deleting pod "exec-volume-test-preprovisionedpv-plbl" in namespace "volume-145"
STEP: Deleting pv and pvc
Jun 20 19:52:54.545: INFO: Deleting PersistentVolumeClaim "pvc-2cqpn"
Jun 20 19:52:54.609: INFO: Deleting PersistentVolume "aws-wrmt4"
Jun 20 19:52:54.820: INFO: Couldn't delete PD "aws://us-west-2a/vol-044ca7bd15386dd10", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-044ca7bd15386dd10 is currently attached to i-0f810c6872e4c8a1c
	status code: 400, request id: b51d4007-5daa-446b-b31c-ccb6ddf2631e
Jun 20 19:53:00.220: INFO: Couldn't delete PD "aws://us-west-2a/vol-044ca7bd15386dd10", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-044ca7bd15386dd10 is currently attached to i-0f810c6872e4c8a1c
	status code: 400, request id: 59edc794-4eb7-4e86-901d-8bdbf3dfd21c
Jun 20 19:53:05.737: INFO: Successfully deleted PD "aws://us-west-2a/vol-044ca7bd15386dd10".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 20 19:53:05.737: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-145" for this suite.
... skipping 22 lines ...
[ebs-csi-migration] EBS CSI Migration
/home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-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-ebs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Distro debian doesn't support ntfs -- skipping

      /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 39 lines ...
Jun 20 19:52:42.287: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3537gmljv
STEP: creating a claim
Jun 20 19:52:42.354: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-v4j9
STEP: Creating a pod to test subpath
Jun 20 19:52:42.553: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-v4j9" in namespace "provisioning-3537" to be "Succeeded or Failed"
Jun 20 19:52:42.617: INFO: Pod "pod-subpath-test-dynamicpv-v4j9": Phase="Pending", Reason="", readiness=false. Elapsed: 63.652104ms
Jun 20 19:52:44.680: INFO: Pod "pod-subpath-test-dynamicpv-v4j9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.126203571s
Jun 20 19:52:46.744: INFO: Pod "pod-subpath-test-dynamicpv-v4j9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.190708752s
Jun 20 19:52:48.808: INFO: Pod "pod-subpath-test-dynamicpv-v4j9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.254212499s
Jun 20 19:52:50.876: INFO: Pod "pod-subpath-test-dynamicpv-v4j9": Phase="Pending", Reason="", readiness=false. Elapsed: 8.322152043s
Jun 20 19:52:52.940: INFO: Pod "pod-subpath-test-dynamicpv-v4j9": Phase="Pending", Reason="", readiness=false. Elapsed: 10.386341918s
Jun 20 19:52:55.006: INFO: Pod "pod-subpath-test-dynamicpv-v4j9": Phase="Pending", Reason="", readiness=false. Elapsed: 12.452170943s
Jun 20 19:52:57.070: INFO: Pod "pod-subpath-test-dynamicpv-v4j9": Phase="Pending", Reason="", readiness=false. Elapsed: 14.516231567s
Jun 20 19:52:59.134: INFO: Pod "pod-subpath-test-dynamicpv-v4j9": Phase="Pending", Reason="", readiness=false. Elapsed: 16.580560755s
Jun 20 19:53:01.199: INFO: Pod "pod-subpath-test-dynamicpv-v4j9": Phase="Pending", Reason="", readiness=false. Elapsed: 18.645301414s
Jun 20 19:53:03.262: INFO: Pod "pod-subpath-test-dynamicpv-v4j9": Phase="Pending", Reason="", readiness=false. Elapsed: 20.708692661s
Jun 20 19:53:05.325: INFO: Pod "pod-subpath-test-dynamicpv-v4j9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.771799998s
STEP: Saw pod success
Jun 20 19:53:05.325: INFO: Pod "pod-subpath-test-dynamicpv-v4j9" satisfied condition "Succeeded or Failed"
Jun 20 19:53:05.387: INFO: Trying to get logs from node ip-172-20-59-7.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-v4j9 container test-container-subpath-dynamicpv-v4j9: <nil>
STEP: delete the pod
Jun 20 19:53:05.519: INFO: Waiting for pod pod-subpath-test-dynamicpv-v4j9 to disappear
Jun 20 19:53:05.581: INFO: Pod pod-subpath-test-dynamicpv-v4j9 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-v4j9
Jun 20 19:53:05.581: INFO: Deleting pod "pod-subpath-test-dynamicpv-v4j9" in namespace "provisioning-3537"
... skipping 282 lines ...