This job view page is being replaced by Spyglass soon. Check out the new job view.
PRleakingtapan: Fix the bug by passing fstype correctly
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2019-08-11 18:42
Elapsed40m4s
Revision80768719389f822d9d722d6deed4f5c46715f8e2
Refs 335

No Test Failures!


Error lines from build-log.txt

... skipping 1123 lines ...

Using cluster from kubectl context: test-cluster-15103.k8s.local

Validating cluster test-cluster-15103.k8s.local


unexpected error during validation: error listing nodes: Get https://api-test-cluster-15103-k8-th20ah-1955623755.us-west-2.elb.amazonaws.com/api/v1/nodes: dial tcp: lookup api-test-cluster-15103-k8-th20ah-1955623755.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
Waiting cluster to be created
Using cluster from kubectl context: test-cluster-15103.k8s.local

Validating cluster test-cluster-15103.k8s.local


unexpected error during validation: error listing nodes: Get https://api-test-cluster-15103-k8-th20ah-1955623755.us-west-2.elb.amazonaws.com/api/v1/nodes: dial tcp: lookup api-test-cluster-15103-k8-th20ah-1955623755.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
Waiting cluster to be created
Using cluster from kubectl context: test-cluster-15103.k8s.local

Validating cluster test-cluster-15103.k8s.local


unexpected error during validation: error listing nodes: Get https://api-test-cluster-15103-k8-th20ah-1955623755.us-west-2.elb.amazonaws.com/api/v1/nodes: dial tcp: lookup api-test-cluster-15103-k8-th20ah-1955623755.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
Waiting cluster to be created
Using cluster from kubectl context: test-cluster-15103.k8s.local

Validating cluster test-cluster-15103.k8s.local


unexpected error during validation: error listing nodes: Get https://api-test-cluster-15103-k8-th20ah-1955623755.us-west-2.elb.amazonaws.com/api/v1/nodes: EOF
Waiting cluster to be created
Using cluster from kubectl context: test-cluster-15103.k8s.local

Validating cluster test-cluster-15103.k8s.local


unexpected error during validation: error listing nodes: Get https://api-test-cluster-15103-k8-th20ah-1955623755.us-west-2.elb.amazonaws.com/api/v1/nodes: EOF
Waiting cluster to be created
Using cluster from kubectl context: test-cluster-15103.k8s.local

Validating cluster test-cluster-15103.k8s.local


unexpected error during validation: error listing nodes: Get https://api-test-cluster-15103-k8-th20ah-1955623755.us-west-2.elb.amazonaws.com/api/v1/nodes: EOF
Waiting cluster to be created
Using cluster from kubectl context: test-cluster-15103.k8s.local

Validating cluster test-cluster-15103.k8s.local


unexpected error during validation: error listing nodes: Get https://api-test-cluster-15103-k8-th20ah-1955623755.us-west-2.elb.amazonaws.com/api/v1/nodes: EOF
Waiting cluster to be created
Using cluster from kubectl context: test-cluster-15103.k8s.local

Validating cluster test-cluster-15103.k8s.local


unexpected error during validation: error listing nodes: Get https://api-test-cluster-15103-k8-th20ah-1955623755.us-west-2.elb.amazonaws.com/api/v1/nodes: EOF
Waiting cluster to be created
Using cluster from kubectl context: test-cluster-15103.k8s.local

Validating cluster test-cluster-15103.k8s.local


unexpected error during validation: error listing nodes: Get https://api-test-cluster-15103-k8-th20ah-1955623755.us-west-2.elb.amazonaws.com/api/v1/nodes: EOF
Waiting cluster to be created
Using cluster from kubectl context: test-cluster-15103.k8s.local

Validating cluster test-cluster-15103.k8s.local


unexpected error during validation: error listing nodes: Get https://api-test-cluster-15103-k8-th20ah-1955623755.us-west-2.elb.amazonaws.com/api/v1/nodes: EOF
Waiting cluster to be created
Using cluster from kubectl context: test-cluster-15103.k8s.local

Validating cluster test-cluster-15103.k8s.local

INSTANCE GROUPS
... skipping 8 lines ...
KIND	NAME			MESSAGE
Machine	i-02ef43eedde06be7d	machine "i-02ef43eedde06be7d" has not yet joined cluster
Machine	i-037fe40f4f5357526	machine "i-037fe40f4f5357526" has not yet joined cluster
Machine	i-09b1ac9d1338689d3	machine "i-09b1ac9d1338689d3" has not yet joined cluster
Machine	i-0e4310d5787d49ca1	machine "i-0e4310d5787d49ca1" has not yet joined cluster

Validation Failed
Waiting cluster to be created
Using cluster from kubectl context: test-cluster-15103.k8s.local

Validating cluster test-cluster-15103.k8s.local

INSTANCE GROUPS
... skipping 12 lines ...
Machine	i-0e4310d5787d49ca1								machine "i-0e4310d5787d49ca1" has not yet joined cluster
Pod	kube-system/kube-apiserver-ip-172-20-57-73.us-west-2.compute.internal		kube-system pod "kube-apiserver-ip-172-20-57-73.us-west-2.compute.internal" is pending
Pod	kube-system/kube-controller-manager-ip-172-20-57-73.us-west-2.compute.internal	kube-system pod "kube-controller-manager-ip-172-20-57-73.us-west-2.compute.internal" is pending
Pod	kube-system/kube-dns-autoscaler-6567f59ccb-gfc7c				kube-system pod "kube-dns-autoscaler-6567f59ccb-gfc7c" is pending
Pod	kube-system/kube-dns-bdf859cdc-z5kxq						kube-system pod "kube-dns-bdf859cdc-z5kxq" is pending

Validation Failed
Waiting cluster to be created
Using cluster from kubectl context: test-cluster-15103.k8s.local

Validating cluster test-cluster-15103.k8s.local

INSTANCE GROUPS
... skipping 563 lines ...

Tiller (the Helm server-side component) has been installed into your Kubernetes Cluster.

Please note: by default, Tiller is deployed with an insecure 'allow unauthenticated users' policy.
To prevent this, run `helm init` with the --tiller-tls-verify flag.
For more information on securing your installation see: https://docs.helm.sh/using_helm/#securing-your-helm-installation
error: timed out waiting for the condition on deployments/tiller-deploy
NAME                                                                 READY   STATUS    RESTARTS   AGE
dns-controller-67d566c9b4-sdsk8                                      1/1     Running   0          14m
etcd-manager-events-ip-172-20-57-73.us-west-2.compute.internal       1/1     Running   0          14m
etcd-manager-main-ip-172-20-57-73.us-west-2.compute.internal         1/1     Running   0          13m
kube-apiserver-ip-172-20-57-73.us-west-2.compute.internal            1/1     Running   2          13m
kube-controller-manager-ip-172-20-57-73.us-west-2.compute.internal   1/1     Running   0          14m
... skipping 428 lines ...
  /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/tests/e2e/dynamic_provisioning.go:509
STEP: setting up the StorageClass
STEP: creating a StorageClass 
STEP: setting up the PVC and PV
STEP: creating a PVC
STEP: deploying the pod
STEP: checking that the pods command exits with no error
Aug 11 19:06:27.673: INFO: Waiting up to 15m0s for pod "ebs-volume-tester-8sxpc" in namespace "e2e-tests-ebs-sfkfp" to be "success or failure"
Aug 11 19:06:27.728: INFO: Pod "ebs-volume-tester-8sxpc": Phase="Pending", Reason="", readiness=false. Elapsed: 54.427572ms
Aug 11 19:06:29.783: INFO: Pod "ebs-volume-tester-8sxpc": Phase="Pending", Reason="", readiness=false. Elapsed: 2.109927321s
Aug 11 19:06:31.859: INFO: Pod "ebs-volume-tester-8sxpc": Phase="Pending", Reason="", readiness=false. Elapsed: 4.185695503s
Aug 11 19:06:33.915: INFO: Pod "ebs-volume-tester-8sxpc": Phase="Pending", Reason="", readiness=false. Elapsed: 6.241968081s
Aug 11 19:06:35.971: INFO: Pod "ebs-volume-tester-8sxpc": Phase="Pending", Reason="", readiness=false. Elapsed: 8.297973735s
... skipping 427 lines ...
Aug 11 19:21:17.132: INFO: Pod "ebs-volume-tester-8sxpc": Phase="Pending", Reason="", readiness=false. Elapsed: 14m49.458433413s
Aug 11 19:21:19.189: INFO: Pod "ebs-volume-tester-8sxpc": Phase="Pending", Reason="", readiness=false. Elapsed: 14m51.515430425s
Aug 11 19:21:21.246: INFO: Pod "ebs-volume-tester-8sxpc": Phase="Pending", Reason="", readiness=false. Elapsed: 14m53.572573742s
Aug 11 19:21:23.303: INFO: Pod "ebs-volume-tester-8sxpc": Phase="Pending", Reason="", readiness=false. Elapsed: 14m55.6299151s
Aug 11 19:21:25.360: INFO: Pod "ebs-volume-tester-8sxpc": Phase="Pending", Reason="", readiness=false. Elapsed: 14m57.686972526s
Aug 11 19:21:27.418: INFO: Pod "ebs-volume-tester-8sxpc": Phase="Pending", Reason="", readiness=false. Elapsed: 14m59.74402286s
Aug 11 19:21:29.418: INFO: Unexpected error occurred: Gave up after waiting 15m0s for pod "ebs-volume-tester-8sxpc" to be "success or failure"
Aug 11 19:21:29.419: INFO: deleting Pod "e2e-tests-ebs-sfkfp"/"ebs-volume-tester-8sxpc"
Aug 11 19:21:29.476: INFO: Pod ebs-volume-tester-8sxpc has the following logs: 
STEP: Deleting pod ebs-volume-tester-8sxpc in namespace e2e-tests-ebs-sfkfp
Aug 11 19:21:29.544: INFO: deleting PVC "e2e-tests-ebs-sfkfp"/"pvc-sxcfg"
Aug 11 19:21:29.544: INFO: Deleting PersistentVolumeClaim "pvc-sxcfg"
Aug 11 19:21:29.602: INFO: deleting StorageClass e2e-tests-ebs-sfkfp-ebs.csi.aws.com-dynamic-sc-wm8hr
[AfterEach] [ebs-csi-e2e] [multi-az] Dynamic Provisioning
  /home/prow/go/pkg/mod/k8s.io/kubernetes@v1.13.1/test/e2e/framework/framework.go:154
STEP: Collecting events from namespace "e2e-tests-ebs-sfkfp".
STEP: Found 8 events.
Aug 11 19:21:29.747: INFO: At 2019-08-11 19:06:27 +0000 UTC - event for pvc-sxcfg: {ebs.csi.aws.com_ebs-csi-controller-0_b665eaa0-bc6a-11e9-8965-de75c15fbd33 } Provisioning: External provisioner is provisioning volume for claim "e2e-tests-ebs-sfkfp/pvc-sxcfg"
Aug 11 19:21:29.748: INFO: At 2019-08-11 19:06:27 +0000 UTC - event for pvc-sxcfg: {ebs.csi.aws.com_ebs-csi-controller-0_b665eaa0-bc6a-11e9-8965-de75c15fbd33 } ProvisioningFailed: failed to provision volume with StorageClass "e2e-tests-ebs-sfkfp-ebs.csi.aws.com-dynamic-sc-wm8hr": failed to strip CSI Parameters of prefixed keys: found unknown parameter key "csi.storage.k8s.io/fsType" with reserved namespace csi.storage.k8s.io/
Aug 11 19:21:29.748: INFO: At 2019-08-11 19:06:27 +0000 UTC - event for pvc-sxcfg: {persistentvolume-controller } WaitForFirstConsumer: waiting for first consumer to be created before binding
Aug 11 19:21:29.748: INFO: At 2019-08-11 19:06:27 +0000 UTC - event for pvc-sxcfg: {persistentvolume-controller } ExternalProvisioning: waiting for a volume to be created, either by external provisioner "ebs.csi.aws.com" or manually created by system administrator
Aug 11 19:21:29.748: INFO: At 2019-08-11 19:16:27 +0000 UTC - event for ebs-volume-tester-8sxpc: {default-scheduler } FailedScheduling: timed out waiting for the condition
Aug 11 19:21:29.748: INFO: At 2019-08-11 19:16:29 +0000 UTC - event for ebs-volume-tester-8sxpc: {default-scheduler } FailedScheduling: AssumePod failed: pod 1ed72242-bc6b-11e9-8c3f-028fc9448458 is in the cache, so can't be assumed
Aug 11 19:21:29.748: INFO: At 2019-08-11 19:21:29 +0000 UTC - event for ebs-volume-tester-8sxpc: {default-scheduler } FailedScheduling: skip schedule deleting pod: e2e-tests-ebs-sfkfp/ebs-volume-tester-8sxpc
Aug 11 19:21:29.748: INFO: At 2019-08-11 19:21:29 +0000 UTC - event for ebs-volume-tester-8sxpc: {default-scheduler } FailedScheduling: pod "e2e-tests-ebs-sfkfp/ebs-volume-tester-8sxpc" does not exist any more
Aug 11 19:21:29.921: INFO: POD                                                                 NODE                                         PHASE    GRACE  CONDITIONS
Aug 11 19:21:29.921: INFO: ebs-volume-tester-rkwq7                                                                                          Pending         [{PodScheduled False 0001-01-01 00:00:00 +0000 UTC 2019-08-11 19:16:27 +0000 UTC SchedulerError pod 1f0ba16e-bc6b-11e9-8c3f-028fc9448458 is in the cache, so can't be assumed}]
Aug 11 19:21:29.921: INFO: dns-controller-67d566c9b4-sdsk8                                     ip-172-20-57-73.us-west-2.compute.internal   Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2019-08-11 18:48:52 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2019-08-11 18:49:04 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2019-08-11 18:49:04 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2019-08-11 18:48:52 +0000 UTC  }]
Aug 11 19:21:29.921: INFO: ebs-csi-controller-0                                                ip-172-20-109-7.us-west-2.compute.internal   Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2019-08-11 19:03:14 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2019-08-11 19:03:54 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2019-08-11 19:03:54 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2019-08-11 19:03:14 +0000 UTC  }]
... skipping 106 lines ...
• Failure [915.079 seconds]
[ebs-csi-e2e] [multi-az] Dynamic Provisioning
/home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/tests/e2e/dynamic_provisioning.go:467
  [env] should allow for topology aware volume with specified zone in allowedTopologies [It]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/tests/e2e/dynamic_provisioning.go:509

  Expected error:
      <*errors.errorString | 0xc0004a5fb0>: {
          s: "Gave up after waiting 15m0s for pod \"ebs-volume-tester-8sxpc\" to be \"success or failure\"",
      }
      Gave up after waiting 15m0s for pod "ebs-volume-tester-8sxpc" to be "success or failure"
  not to have occurred

... skipping 16 lines ...
  /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/tests/e2e/dynamic_provisioning.go:482
STEP: setting up the StorageClass
STEP: creating a StorageClass 
STEP: setting up the PVC and PV
STEP: creating a PVC
STEP: deploying the pod
STEP: checking that the pods command exits with no error
Aug 11 19:06:28.009: INFO: Waiting up to 15m0s for pod "ebs-volume-tester-rkwq7" in namespace "e2e-tests-ebs-z6ckw" to be "success or failure"
Aug 11 19:06:28.083: INFO: Pod "ebs-volume-tester-rkwq7": Phase="Pending", Reason="", readiness=false. Elapsed: 73.868009ms
Aug 11 19:06:30.148: INFO: Pod "ebs-volume-tester-rkwq7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.138951821s
Aug 11 19:06:32.207: INFO: Pod "ebs-volume-tester-rkwq7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.197938776s
Aug 11 19:06:34.269: INFO: Pod "ebs-volume-tester-rkwq7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.259160601s
Aug 11 19:06:36.327: INFO: Pod "ebs-volume-tester-rkwq7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.317968246s
... skipping 427 lines ...
Aug 11 19:21:17.549: INFO: Pod "ebs-volume-tester-rkwq7": Phase="Pending", Reason="", readiness=false. Elapsed: 14m49.539905663s
Aug 11 19:21:19.607: INFO: Pod "ebs-volume-tester-rkwq7": Phase="Pending", Reason="", readiness=false. Elapsed: 14m51.597638308s
Aug 11 19:21:21.665: INFO: Pod "ebs-volume-tester-rkwq7": Phase="Pending", Reason="", readiness=false. Elapsed: 14m53.655100844s
Aug 11 19:21:23.722: INFO: Pod "ebs-volume-tester-rkwq7": Phase="Pending", Reason="", readiness=false. Elapsed: 14m55.712584455s
Aug 11 19:21:25.780: INFO: Pod "ebs-volume-tester-rkwq7": Phase="Pending", Reason="", readiness=false. Elapsed: 14m57.770130165s
Aug 11 19:21:27.837: INFO: Pod "ebs-volume-tester-rkwq7": Phase="Pending", Reason="", readiness=false. Elapsed: 14m59.827560839s
Aug 11 19:21:29.837: INFO: Unexpected error occurred: Gave up after waiting 15m0s for pod "ebs-volume-tester-rkwq7" to be "success or failure"
Aug 11 19:21:29.838: INFO: deleting Pod "e2e-tests-ebs-z6ckw"/"ebs-volume-tester-rkwq7"
Aug 11 19:21:29.896: INFO: Pod ebs-volume-tester-rkwq7 has the following logs: 
STEP: Deleting pod ebs-volume-tester-rkwq7 in namespace e2e-tests-ebs-z6ckw
Aug 11 19:21:29.969: INFO: deleting PVC "e2e-tests-ebs-z6ckw"/"pvc-fzsn4"
Aug 11 19:21:29.969: INFO: Deleting PersistentVolumeClaim "pvc-fzsn4"
Aug 11 19:21:30.030: INFO: deleting StorageClass e2e-tests-ebs-z6ckw-ebs.csi.aws.com-dynamic-sc-cjknc
[AfterEach] [ebs-csi-e2e] [multi-az] Dynamic Provisioning
  /home/prow/go/pkg/mod/k8s.io/kubernetes@v1.13.1/test/e2e/framework/framework.go:154
STEP: Collecting events from namespace "e2e-tests-ebs-z6ckw".
STEP: Found 8 events.
Aug 11 19:21:30.158: INFO: At 2019-08-11 19:06:27 +0000 UTC - event for pvc-fzsn4: {persistentvolume-controller } WaitForFirstConsumer: waiting for first consumer to be created before binding
Aug 11 19:21:30.159: INFO: At 2019-08-11 19:06:28 +0000 UTC - event for pvc-fzsn4: {ebs.csi.aws.com_ebs-csi-controller-0_b665eaa0-bc6a-11e9-8965-de75c15fbd33 } Provisioning: External provisioner is provisioning volume for claim "e2e-tests-ebs-z6ckw/pvc-fzsn4"
Aug 11 19:21:30.159: INFO: At 2019-08-11 19:06:28 +0000 UTC - event for pvc-fzsn4: {ebs.csi.aws.com_ebs-csi-controller-0_b665eaa0-bc6a-11e9-8965-de75c15fbd33 } ProvisioningFailed: failed to provision volume with StorageClass "e2e-tests-ebs-z6ckw-ebs.csi.aws.com-dynamic-sc-cjknc": failed to strip CSI Parameters of prefixed keys: found unknown parameter key "csi.storage.k8s.io/fsType" with reserved namespace csi.storage.k8s.io/
Aug 11 19:21:30.159: INFO: At 2019-08-11 19:06:28 +0000 UTC - event for pvc-fzsn4: {persistentvolume-controller } ExternalProvisioning: waiting for a volume to be created, either by external provisioner "ebs.csi.aws.com" or manually created by system administrator
Aug 11 19:21:30.159: INFO: At 2019-08-11 19:16:27 +0000 UTC - event for ebs-volume-tester-rkwq7: {default-scheduler } FailedScheduling: timed out waiting for the condition
Aug 11 19:21:30.159: INFO: At 2019-08-11 19:17:42 +0000 UTC - event for ebs-volume-tester-rkwq7: {default-scheduler } FailedScheduling: AssumePod failed: pod 1f0ba16e-bc6b-11e9-8c3f-028fc9448458 is in the cache, so can't be assumed
Aug 11 19:21:30.159: INFO: At 2019-08-11 19:21:29 +0000 UTC - event for ebs-volume-tester-rkwq7: {default-scheduler } FailedScheduling: skip schedule deleting pod: e2e-tests-ebs-z6ckw/ebs-volume-tester-rkwq7
Aug 11 19:21:30.159: INFO: At 2019-08-11 19:21:30 +0000 UTC - event for ebs-volume-tester-rkwq7: {default-scheduler } FailedScheduling: pod "e2e-tests-ebs-z6ckw/ebs-volume-tester-rkwq7" does not exist any more
Aug 11 19:21:30.388: INFO: POD                                                                 NODE                                         PHASE    GRACE  CONDITIONS
Aug 11 19:21:30.388: INFO: dns-controller-67d566c9b4-sdsk8                                     ip-172-20-57-73.us-west-2.compute.internal   Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2019-08-11 18:48:52 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2019-08-11 18:49:04 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2019-08-11 18:49:04 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2019-08-11 18:48:52 +0000 UTC  }]
Aug 11 19:21:30.389: INFO: ebs-csi-controller-0                                                ip-172-20-109-7.us-west-2.compute.internal   Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2019-08-11 19:03:14 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2019-08-11 19:03:54 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2019-08-11 19:03:54 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2019-08-11 19:03:14 +0000 UTC  }]
Aug 11 19:21:30.389: INFO: ebs-csi-node-jkhxt                                                  ip-172-20-79-60.us-west-2.compute.internal   Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2019-08-11 19:03:14 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2019-08-11 19:03:31 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2019-08-11 19:03:31 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2019-08-11 19:03:13 +0000 UTC  }]
... skipping 105 lines ...
• Failure [915.257 seconds]
[ebs-csi-e2e] [multi-az] Dynamic Provisioning
/home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/tests/e2e/dynamic_provisioning.go:467
  should allow for topology aware volume scheduling [It]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/tests/e2e/dynamic_provisioning.go:482

  Expected error:
      <*errors.errorString | 0xc000282450>: {
          s: "Gave up after waiting 15m0s for pod \"ebs-volume-tester-rkwq7\" to be \"success or failure\"",
      }
      Gave up after waiting 15m0s for pod "ebs-volume-tester-rkwq7" to be "success or failure"
  not to have occurred

  /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/tests/e2e/testsuites/testsuites.go:509
------------------------------


Summarizing 2 Failures:

[Fail] [ebs-csi-e2e] [multi-az] Dynamic Provisioning [It] [env] should allow for topology aware volume with specified zone in allowedTopologies 
/home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/tests/e2e/testsuites/testsuites.go:509

[Fail] [ebs-csi-e2e] [multi-az] Dynamic Provisioning [It] should allow for topology aware volume scheduling 
/home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/tests/e2e/testsuites/testsuites.go:509

Ran 2 of 37 Specs in 915.595 seconds
FAIL! -- 0 Passed | 2 Failed | 0 Pending | 35 Skipped


Ginkgo ran 1 suite in 17m40.313051816s
Test Suite Failed
Removing driver
release "aws-ebs-csi-driver" deleted
Deleting cluster test-cluster-15103
TYPE			NAME											ID
autoscaling-config	master-us-west-2a.masters.test-cluster-15103.k8s.local-20190811184312			master-us-west-2a.masters.test-cluster-15103.k8s.local-20190811184312
autoscaling-config	nodes.test-cluster-15103.k8s.local-20190811184312					nodes.test-cluster-15103.k8s.local-20190811184312
... skipping 138 lines ...
route-table:rtb-00bd7a4bca1ad034f	ok
vpc:vpc-0dda249b8269c7570	ok
dhcp-options:dopt-0ccc6c2251034450c	ok
Deleted kubectl config for test-cluster-15103.k8s.local

Deleted cluster: "test-cluster-15103.k8s.local"
Makefile:53: recipe for target 'test-e2e-multi-az' failed
make: *** [test-e2e-multi-az] Error 1
+ EXIT_VALUE=2
+ set +o xtrace
Cleaning up after docker in docker.
================================================================================
[Barnacle] 2019/08/11 19:22:49 Cleaning up Docker data root...
[Barnacle] 2019/08/11 19:22:49 Removing all containers.
... skipping 25 lines ...