This job view page is being replaced by Spyglass soon. Check out the new job view.
PRvdhanan: instance metadata issue fix
ResultABORTED
Tests 0 failed / 57 succeeded
Started2021-04-28 22:32
Elapsed27m45s
Revision0b61573a4f63e9a3f5e80d9e90767ccc6b73b337
Refs 855

No Test Failures!


Show 57 Passed Tests

Show 428 Skipped Tests

Error lines from build-log.txt

... skipping 789 lines ...
## Validating cluster test-cluster-3296.k8s.local
#
Using cluster from kubectl context: test-cluster-3296.k8s.local

Validating cluster test-cluster-3296.k8s.local

W0428 22:35:48.760557    9284 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-3296-k8s-an0ebs-1034549979.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-3296-k8s-an0ebs-1034549979.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0428 22:35:59.480603    9284 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-3296-k8s-an0ebs-1034549979.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-3296-k8s-an0ebs-1034549979.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0428 22:36:09.518853    9284 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-3296-k8s-an0ebs-1034549979.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-3296-k8s-an0ebs-1034549979.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0428 22:36:19.566044    9284 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-3296-k8s-an0ebs-1034549979.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-3296-k8s-an0ebs-1034549979.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0428 22:36:29.626770    9284 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-3296-k8s-an0ebs-1034549979.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-3296-k8s-an0ebs-1034549979.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0428 22:36:50.311407    9284 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-3296-k8s-an0ebs-1034549979.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-3296-k8s-an0ebs-1034549979.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0428 22:37:11.984977    9284 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)
W0428 22:37:33.628740    9284 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)
W0428 22:37:55.375563    9284 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)
W0428 22:38:17.125596    9284 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)
W0428 22:38:38.766848    9284 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)
W0428 22:39:00.466524    9284 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	c4.large	3	3	us-west-2a

NODE STATUS
... skipping 4 lines ...
KIND	NAME						MESSAGE
Machine	i-02b84a42a045760ee				machine "i-02b84a42a045760ee" has not yet joined cluster
Machine	i-044e29225f045240b				machine "i-044e29225f045240b" has not yet joined cluster
Machine	i-0bc250bec81884296				machine "i-0bc250bec81884296" has not yet joined cluster
Node	ip-172-20-63-253.us-west-2.compute.internal	master "ip-172-20-63-253.us-west-2.compute.internal" is not ready

Validation Failed
W0428 22:39:12.037512    9284 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	c4.large	3	3	us-west-2a

... skipping 5 lines ...
KIND	NAME						MESSAGE
Machine	i-02b84a42a045760ee				machine "i-02b84a42a045760ee" has not yet joined cluster
Machine	i-044e29225f045240b				machine "i-044e29225f045240b" has not yet joined cluster
Machine	i-0bc250bec81884296				machine "i-0bc250bec81884296" has not yet joined cluster
Node	ip-172-20-63-253.us-west-2.compute.internal	master "ip-172-20-63-253.us-west-2.compute.internal" is not ready

Validation Failed
W0428 22:39:23.159522    9284 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	c4.large	3	3	us-west-2a

... skipping 9 lines ...
Pod	kube-system/coredns-5489b75945-szqsx						system-cluster-critical pod "coredns-5489b75945-szqsx" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-bh25f					system-cluster-critical pod "coredns-autoscaler-6f594f4c58-bh25f" is pending
Pod	kube-system/dns-controller-cd496f988-2p5ct					system-cluster-critical pod "dns-controller-cd496f988-2p5ct" is pending
Pod	kube-system/kops-controller-zmfw7						system-node-critical pod "kops-controller-zmfw7" is pending
Pod	kube-system/kube-controller-manager-ip-172-20-63-253.us-west-2.compute.internal	system-cluster-critical pod "kube-controller-manager-ip-172-20-63-253.us-west-2.compute.internal" is pending

Validation Failed
W0428 22:39:34.362308    9284 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	c4.large	3	3	us-west-2a

... skipping 8 lines ...
Machine	i-0bc250bec81884296				machine "i-0bc250bec81884296" has not yet joined cluster
Node	ip-172-20-63-253.us-west-2.compute.internal	master "ip-172-20-63-253.us-west-2.compute.internal" is missing kube-apiserver pod
Node	ip-172-20-63-253.us-west-2.compute.internal	master "ip-172-20-63-253.us-west-2.compute.internal" is missing kube-scheduler pod
Pod	kube-system/coredns-5489b75945-szqsx		system-cluster-critical pod "coredns-5489b75945-szqsx" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-bh25f	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-bh25f" is pending

Validation Failed
W0428 22:39:45.510305    9284 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	c4.large	3	3	us-west-2a

... skipping 8 lines ...
Machine	i-0bc250bec81884296				machine "i-0bc250bec81884296" has not yet joined cluster
Node	ip-172-20-63-253.us-west-2.compute.internal	master "ip-172-20-63-253.us-west-2.compute.internal" is missing kube-apiserver pod
Node	ip-172-20-63-253.us-west-2.compute.internal	master "ip-172-20-63-253.us-west-2.compute.internal" is missing kube-scheduler pod
Pod	kube-system/coredns-5489b75945-szqsx		system-cluster-critical pod "coredns-5489b75945-szqsx" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-bh25f	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-bh25f" is pending

Validation Failed
W0428 22:39:56.716668    9284 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	c4.large	3	3	us-west-2a

... skipping 8 lines ...
Machine	i-0bc250bec81884296				machine "i-0bc250bec81884296" has not yet joined cluster
Node	ip-172-20-63-253.us-west-2.compute.internal	master "ip-172-20-63-253.us-west-2.compute.internal" is missing kube-apiserver pod
Node	ip-172-20-63-253.us-west-2.compute.internal	master "ip-172-20-63-253.us-west-2.compute.internal" is missing kube-scheduler pod
Pod	kube-system/coredns-5489b75945-szqsx		system-cluster-critical pod "coredns-5489b75945-szqsx" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-bh25f	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-bh25f" is pending

Validation Failed
W0428 22:40:07.964518    9284 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	c4.large	3	3	us-west-2a

... skipping 8 lines ...
Machine	i-0bc250bec81884296				machine "i-0bc250bec81884296" has not yet joined cluster
Node	ip-172-20-63-253.us-west-2.compute.internal	master "ip-172-20-63-253.us-west-2.compute.internal" is missing kube-apiserver pod
Node	ip-172-20-63-253.us-west-2.compute.internal	master "ip-172-20-63-253.us-west-2.compute.internal" is missing kube-scheduler pod
Pod	kube-system/coredns-5489b75945-szqsx		system-cluster-critical pod "coredns-5489b75945-szqsx" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-bh25f	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-bh25f" is pending

Validation Failed
W0428 22:40:19.056535    9284 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	c4.large	3	3	us-west-2a

... skipping 7 lines ...
Machine	i-044e29225f045240b				machine "i-044e29225f045240b" has not yet joined cluster
Machine	i-0bc250bec81884296				machine "i-0bc250bec81884296" has not yet joined cluster
Node	ip-172-20-63-253.us-west-2.compute.internal	master "ip-172-20-63-253.us-west-2.compute.internal" is missing kube-apiserver pod
Pod	kube-system/coredns-5489b75945-szqsx		system-cluster-critical pod "coredns-5489b75945-szqsx" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-bh25f	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-bh25f" is pending

Validation Failed
W0428 22:40:30.422606    9284 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	c4.large	3	3	us-west-2a

... skipping 6 lines ...
Machine	i-02b84a42a045760ee				machine "i-02b84a42a045760ee" has not yet joined cluster
Machine	i-044e29225f045240b				machine "i-044e29225f045240b" has not yet joined cluster
Machine	i-0bc250bec81884296				machine "i-0bc250bec81884296" has not yet joined cluster
Pod	kube-system/coredns-5489b75945-szqsx		system-cluster-critical pod "coredns-5489b75945-szqsx" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-bh25f	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-bh25f" is pending

Validation Failed
W0428 22:40:41.585241    9284 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	c4.large	3	3	us-west-2a

... skipping 9 lines ...
Node	ip-172-20-36-68.us-west-2.compute.internal	node "ip-172-20-36-68.us-west-2.compute.internal" is not ready
Node	ip-172-20-51-186.us-west-2.compute.internal	node "ip-172-20-51-186.us-west-2.compute.internal" is not ready
Node	ip-172-20-58-60.us-west-2.compute.internal	node "ip-172-20-58-60.us-west-2.compute.internal" is not ready
Pod	kube-system/coredns-5489b75945-szqsx		system-cluster-critical pod "coredns-5489b75945-szqsx" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-bh25f	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-bh25f" is pending

Validation Failed
W0428 22:40:52.830129    9284 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	c4.large	3	3	us-west-2a

... skipping 9 lines ...
Node	ip-172-20-36-68.us-west-2.compute.internal	node "ip-172-20-36-68.us-west-2.compute.internal" is not ready
Node	ip-172-20-51-186.us-west-2.compute.internal	node "ip-172-20-51-186.us-west-2.compute.internal" is not ready
Node	ip-172-20-58-60.us-west-2.compute.internal	node "ip-172-20-58-60.us-west-2.compute.internal" is not ready
Pod	kube-system/coredns-5489b75945-szqsx		system-cluster-critical pod "coredns-5489b75945-szqsx" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-bh25f	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-bh25f" is pending

Validation Failed
W0428 22:41:04.021454    9284 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	c4.large	3	3	us-west-2a

... skipping 7 lines ...
VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/coredns-5489b75945-szqsx					system-cluster-critical pod "coredns-5489b75945-szqsx" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-bh25f				system-cluster-critical pod "coredns-autoscaler-6f594f4c58-bh25f" is pending
Pod	kube-system/kube-proxy-ip-172-20-36-68.us-west-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-36-68.us-west-2.compute.internal" is pending

Validation Failed
W0428 22:41:15.247195    9284 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	c4.large	3	3	us-west-2a

... skipping 7 lines ...
VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/coredns-5489b75945-88c7n					system-cluster-critical pod "coredns-5489b75945-88c7n" is pending
Pod	kube-system/coredns-5489b75945-szqsx					system-cluster-critical pod "coredns-5489b75945-szqsx" is pending
Pod	kube-system/kube-proxy-ip-172-20-58-60.us-west-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-58-60.us-west-2.compute.internal" is pending

Validation Failed
W0428 22:41:26.442918    9284 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	c4.large	3	3	us-west-2a

... skipping 282 lines ...
Apr 28 22:43:25.369: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1634-e2e-scmdjld
STEP: creating a claim
Apr 28 22:43:25.434: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-jpcv
STEP: Creating a pod to test atomic-volume-subpath
Apr 28 22:43:25.630: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-jpcv" in namespace "provisioning-1634" to be "Succeeded or Failed"
Apr 28 22:43:25.695: INFO: Pod "pod-subpath-test-dynamicpv-jpcv": Phase="Pending", Reason="", readiness=false. Elapsed: 65.499269ms
Apr 28 22:43:27.760: INFO: Pod "pod-subpath-test-dynamicpv-jpcv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.130205381s
Apr 28 22:43:29.824: INFO: Pod "pod-subpath-test-dynamicpv-jpcv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.194463097s
Apr 28 22:43:31.888: INFO: Pod "pod-subpath-test-dynamicpv-jpcv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.25822136s
Apr 28 22:43:33.953: INFO: Pod "pod-subpath-test-dynamicpv-jpcv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.322931493s
Apr 28 22:43:36.017: INFO: Pod "pod-subpath-test-dynamicpv-jpcv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.387663773s
... skipping 9 lines ...
Apr 28 22:43:56.668: INFO: Pod "pod-subpath-test-dynamicpv-jpcv": Phase="Running", Reason="", readiness=true. Elapsed: 31.038319264s
Apr 28 22:43:58.731: INFO: Pod "pod-subpath-test-dynamicpv-jpcv": Phase="Running", Reason="", readiness=true. Elapsed: 33.101564114s
Apr 28 22:44:00.795: INFO: Pod "pod-subpath-test-dynamicpv-jpcv": Phase="Running", Reason="", readiness=true. Elapsed: 35.165548657s
Apr 28 22:44:02.866: INFO: Pod "pod-subpath-test-dynamicpv-jpcv": Phase="Running", Reason="", readiness=true. Elapsed: 37.236067784s
Apr 28 22:44:04.930: INFO: Pod "pod-subpath-test-dynamicpv-jpcv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 39.300665698s
STEP: Saw pod success
Apr 28 22:44:04.930: INFO: Pod "pod-subpath-test-dynamicpv-jpcv" satisfied condition "Succeeded or Failed"
Apr 28 22:44:04.994: INFO: Trying to get logs from node ip-172-20-36-68.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-jpcv container test-container-subpath-dynamicpv-jpcv: <nil>
STEP: delete the pod
Apr 28 22:44:05.136: INFO: Waiting for pod pod-subpath-test-dynamicpv-jpcv to disappear
Apr 28 22:44:05.199: INFO: Pod pod-subpath-test-dynamicpv-jpcv no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-jpcv
Apr 28 22:44:05.199: INFO: Deleting pod "pod-subpath-test-dynamicpv-jpcv" in namespace "provisioning-1634"
... skipping 30 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (immediate binding)] topology
  /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 schedule a pod which has topologies that conflict with AllowedTopologies [BeforeEach]
    /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

    Driver "ebs.csi.aws.com" does not support topology - skipping

    /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:92
------------------------------
... skipping 168 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [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

    Driver ebs.csi.aws.com 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:121
------------------------------
... skipping 74 lines ...
Apr 28 22:44:01.603: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-468-e2e-sc8n2s9
STEP: creating a claim
Apr 28 22:44:01.666: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-wgvp
STEP: Creating a pod to test exec-volume-test
Apr 28 22:44:01.856: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-wgvp" in namespace "volume-468" to be "Succeeded or Failed"
Apr 28 22:44:01.919: INFO: Pod "exec-volume-test-dynamicpv-wgvp": Phase="Pending", Reason="", readiness=false. Elapsed: 62.159523ms
Apr 28 22:44:03.992: INFO: Pod "exec-volume-test-dynamicpv-wgvp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.135235288s
Apr 28 22:44:06.059: INFO: Pod "exec-volume-test-dynamicpv-wgvp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.202215846s
Apr 28 22:44:08.121: INFO: Pod "exec-volume-test-dynamicpv-wgvp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.264802298s
Apr 28 22:44:10.184: INFO: Pod "exec-volume-test-dynamicpv-wgvp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.327870978s
Apr 28 22:44:12.248: INFO: Pod "exec-volume-test-dynamicpv-wgvp": Phase="Pending", Reason="", readiness=false. Elapsed: 10.391204506s
Apr 28 22:44:14.311: INFO: Pod "exec-volume-test-dynamicpv-wgvp": Phase="Pending", Reason="", readiness=false. Elapsed: 12.454779828s
Apr 28 22:44:16.375: INFO: Pod "exec-volume-test-dynamicpv-wgvp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.518451961s
STEP: Saw pod success
Apr 28 22:44:16.375: INFO: Pod "exec-volume-test-dynamicpv-wgvp" satisfied condition "Succeeded or Failed"
Apr 28 22:44:16.437: INFO: Trying to get logs from node ip-172-20-36-68.us-west-2.compute.internal pod exec-volume-test-dynamicpv-wgvp container exec-container-dynamicpv-wgvp: <nil>
STEP: delete the pod
Apr 28 22:44:16.588: INFO: Waiting for pod exec-volume-test-dynamicpv-wgvp to disappear
Apr 28 22:44:16.650: INFO: Pod exec-volume-test-dynamicpv-wgvp no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-wgvp
Apr 28 22:44:16.651: INFO: Deleting pod "exec-volume-test-dynamicpv-wgvp" in namespace "volume-468"
... skipping 29 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [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 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 "ebs.csi.aws.com" does not support volume type "InlineVolume" - skipping

    /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 41 lines ...