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 / 58 succeeded
Started2022-06-20 19:42
Elapsed26m57s
Revision7a4d05ea4f51fbb5a4696361342a19cb373f2247
Refs 1282

No Test Failures!


Show 58 Passed Tests

Show 427 Skipped Tests

Error lines from build-log.txt

... skipping 459 lines ...
#8 [linux-amazon 2/3] RUN yum update -y &&     yum install ca-certificates e2fsprogs xfsprogs util-linux -y &&     yum clean all
#8 15.01   Installing : cryptsetup-libs-1.7.4-4.amzn2.x86_64                       24/32 
#8 15.09   Installing : elfutils-libs-0.176-2.amzn2.x86_64                         25/32 
#8 15.18   Installing : systemd-libs-219-78.amzn2.0.18.x86_64                      26/32 
#8 15.60   Installing : 1:dbus-libs-1.10.24-7.amzn2.x86_64                         27/32 
#8 18.47   Installing : systemd-219-78.amzn2.0.18.x86_64                           28/32 
#8 19.64 Failed to get D-Bus connection: Operation not permitted
#8 20.20   Installing : elfutils-default-yama-scope-0.176-2.amzn2.noarch           29/32 
#8 21.16   Installing : 1:dbus-1.10.24-7.amzn2.x86_64                              30/32 
#8 21.46   Installing : e2fsprogs-1.42.9-19.amzn2.x86_64                           31/32 
#8 22.70   Installing : xfsprogs-4.5.0-18.amzn2.0.1.x86_64                         32/32
#8 ...

... skipping 215 lines ...
## Validating cluster test-cluster-22366.k8s.local
#
Using cluster from kubectl context: test-cluster-22366.k8s.local

Validating cluster test-cluster-22366.k8s.local

W0620 19:45:31.210616    6390 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-22366-k8-e40q06-1639564469.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-22366-k8-e40q06-1639564469.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0620 19:45:41.259965    6390 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-22366-k8-e40q06-1639564469.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-22366-k8-e40q06-1639564469.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0620 19:45:51.300386    6390 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-22366-k8-e40q06-1639564469.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-22366-k8-e40q06-1639564469.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0620 19:46:01.332740    6390 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-22366-k8-e40q06-1639564469.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-22366-k8-e40q06-1639564469.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0620 19:46:11.371909    6390 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-22366-k8-e40q06-1639564469.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-22366-k8-e40q06-1639564469.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0620 19:46:21.405819    6390 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-22366-k8-e40q06-1639564469.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-22366-k8-e40q06-1639564469.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0620 19:46:31.438634    6390 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-22366-k8-e40q06-1639564469.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-22366-k8-e40q06-1639564469.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0620 19:46:41.478035    6390 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-22366-k8-e40q06-1639564469.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-22366-k8-e40q06-1639564469.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0620 19:47:03.145002    6390 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:24.704621    6390 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:46.257874    6390 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:48:07.897929    6390 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-02f3a192bda84b640				machine "i-02f3a192bda84b640" has not yet joined cluster
Machine	i-05b46804fe9927868				machine "i-05b46804fe9927868" has not yet joined cluster
Machine	i-0a2bbba77cd5df7c9				machine "i-0a2bbba77cd5df7c9" has not yet joined cluster
Node	ip-172-20-34-222.us-west-2.compute.internal	node "ip-172-20-34-222.us-west-2.compute.internal" of role "master" is not ready

Validation Failed
W0620 19:48:22.860585    6390 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 10 lines ...
Machine	i-0a2bbba77cd5df7c9				machine "i-0a2bbba77cd5df7c9" has not yet joined cluster
Node	ip-172-20-34-222.us-west-2.compute.internal	node "ip-172-20-34-222.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-8f5559c9b-57c7k		system-cluster-critical pod "coredns-8f5559c9b-57c7k" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-p8gjf	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-p8gjf" is pending
Pod	kube-system/dns-controller-5d59c585d8-9pl29	system-cluster-critical pod "dns-controller-5d59c585d8-9pl29" is pending

Validation Failed
W0620 19:48:35.152237    6390 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-34-222.us-west-2.compute.internal	master "ip-172-20-34-222.us-west-2.compute.internal" is missing kube-apiserver pod
Node	ip-172-20-34-222.us-west-2.compute.internal	master "ip-172-20-34-222.us-west-2.compute.internal" is missing kube-controller-manager pod
Node	ip-172-20-34-222.us-west-2.compute.internal	master "ip-172-20-34-222.us-west-2.compute.internal" is missing kube-scheduler pod
Pod	kube-system/coredns-8f5559c9b-57c7k		system-cluster-critical pod "coredns-8f5559c9b-57c7k" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-p8gjf	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-p8gjf" is pending

Validation Failed
W0620 19:48:47.271692    6390 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-34-222.us-west-2.compute.internal					master "ip-172-20-34-222.us-west-2.compute.internal" is missing kube-controller-manager pod
Node	ip-172-20-34-222.us-west-2.compute.internal					master "ip-172-20-34-222.us-west-2.compute.internal" is missing kube-scheduler pod
Pod	kube-system/coredns-8f5559c9b-57c7k						system-cluster-critical pod "coredns-8f5559c9b-57c7k" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-p8gjf					system-cluster-critical pod "coredns-autoscaler-6f594f4c58-p8gjf" is pending
Pod	kube-system/etcd-manager-events-ip-172-20-34-222.us-west-2.compute.internal	system-cluster-critical pod "etcd-manager-events-ip-172-20-34-222.us-west-2.compute.internal" is pending

Validation Failed
W0620 19:48:59.274237    6390 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 14 lines ...
Pod	kube-system/coredns-8f5559c9b-57c7k						system-cluster-critical pod "coredns-8f5559c9b-57c7k" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-p8gjf					system-cluster-critical pod "coredns-autoscaler-6f594f4c58-p8gjf" is pending
Pod	kube-system/kube-controller-manager-ip-172-20-34-222.us-west-2.compute.internal	system-cluster-critical pod "kube-controller-manager-ip-172-20-34-222.us-west-2.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-222.us-west-2.compute.internal		system-node-critical pod "kube-proxy-ip-172-20-34-222.us-west-2.compute.internal" is pending
Pod	kube-system/kube-scheduler-ip-172-20-34-222.us-west-2.compute.internal		system-cluster-critical pod "kube-scheduler-ip-172-20-34-222.us-west-2.compute.internal" is pending

Validation Failed
W0620 19:49:11.296246    6390 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 ...
Machine	i-02f3a192bda84b640				machine "i-02f3a192bda84b640" has not yet joined cluster
Machine	i-05b46804fe9927868				machine "i-05b46804fe9927868" has not yet joined cluster
Machine	i-0a2bbba77cd5df7c9				machine "i-0a2bbba77cd5df7c9" has not yet joined cluster
Pod	kube-system/coredns-8f5559c9b-57c7k		system-cluster-critical pod "coredns-8f5559c9b-57c7k" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-p8gjf	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-p8gjf" is pending

Validation Failed
W0620 19:49:23.484067    6390 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 ...
KIND	NAME						MESSAGE
Machine	i-0a2bbba77cd5df7c9				machine "i-0a2bbba77cd5df7c9" has not yet joined cluster
Node	ip-172-20-67-146.us-west-2.compute.internal	node "ip-172-20-67-146.us-west-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-8f5559c9b-57c7k		system-cluster-critical pod "coredns-8f5559c9b-57c7k" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-p8gjf	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-p8gjf" is pending

Validation Failed
W0620 19:49:35.567034    6390 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 ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Node	ip-172-20-67-146.us-west-2.compute.internal	node "ip-172-20-67-146.us-west-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-8f5559c9b-57c7k		system-cluster-critical pod "coredns-8f5559c9b-57c7k" is not ready (coredns)
Pod	kube-system/coredns-autoscaler-6f594f4c58-p8gjf	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-p8gjf" is pending

Validation Failed
W0620 19:49:47.704082    6390 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 7 lines ...
ip-172-20-67-146.us-west-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-8f5559c9b-mqsds	system-cluster-critical pod "coredns-8f5559c9b-mqsds" is pending

Validation Failed
W0620 19:49:59.724691    6390 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-mqsds					system-cluster-critical pod "coredns-8f5559c9b-mqsds" is pending
Pod	kube-system/kube-proxy-ip-172-20-109-122.us-west-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-109-122.us-west-2.compute.internal" is pending

Validation Failed
W0620 19:50:11.752620    6390 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 7 lines ...
ip-172-20-67-146.us-west-2.compute.internal	node	True

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

Validation Failed
W0620 19:50:23.819740    6390 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 126 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: 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 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" does not support volume type "PreprovisionedPV" - skipping

    /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:263
------------------------------
... skipping 8 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 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 "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:263
------------------------------
... skipping 54 lines ...

    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:263
------------------------------
External Storage [Driver: ebs.csi.aws.com] [Testpattern: Dynamic PV (immediate binding)] topology 
  should fail to schedule a pod which has topologies that conflict with AllowedTopologies
  /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

[BeforeEach] [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:51
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /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:40.165: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-22366.k8s.local.kops.kubeconfig
STEP: Building a namespace api object, basename topology
Jun 20 19:52:40.579: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail to schedule a pod which has topologies that conflict with AllowedTopologies
  /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Jun 20 19:52:40.831: INFO: found topology map[topology.ebs.csi.aws.com/zone:us-west-2c]
Jun 20 19:52:40.831: INFO: found topology map[topology.ebs.csi.aws.com/zone:us-west-2a]
Jun 20 19:52:40.832: INFO: Creating storage class object and pvc object for driver - sc: &StorageClass{ObjectMeta:{topology-5736-e2e-scsdz9n      0 0001-01-01 00:00:00 +0000 UTC <nil> <nil> map[] map[] [] []  []},Provisioner:ebs.csi.aws.com,Parameters:map[string]string{},ReclaimPolicy:nil,MountOptions:[],AllowVolumeExpansion:nil,VolumeBindingMode:*Immediate,AllowedTopologies:[]TopologySelectorTerm{{[{topology.ebs.csi.aws.com/zone [us-west-2a]}]},},}, pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- topology-5736    0 0001-01-01 00:00:00 +0000 UTC <nil> <nil> map[] map[] [] []  []},Spec:PersistentVolumeClaimSpec{AccessModes:[ReadWriteOnce],Resources:ResourceRequirements{Limits:ResourceList{},Requests:ResourceList{storage: {{1073741824 0} {<nil>} 1Gi BinarySI},},},VolumeName:,Selector:nil,StorageClassName:*topology-5736-e2e-scsdz9n,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating sc
STEP: Creating pvc
... skipping 33 lines ...
Jun 20 19:52:40.685: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3611-e2e-scgtkgb
STEP: creating a claim
Jun 20 19:52:40.748: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-4wj2
STEP: Creating a pod to test subpath
Jun 20 19:52:40.943: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-4wj2" in namespace "provisioning-3611" to be "Succeeded or Failed"
Jun 20 19:52:41.016: INFO: Pod "pod-subpath-test-dynamicpv-4wj2": Phase="Pending", Reason="", readiness=false. Elapsed: 72.40072ms
Jun 20 19:52:43.079: INFO: Pod "pod-subpath-test-dynamicpv-4wj2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.135506532s
Jun 20 19:52:45.141: INFO: Pod "pod-subpath-test-dynamicpv-4wj2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.197800719s
Jun 20 19:52:47.205: INFO: Pod "pod-subpath-test-dynamicpv-4wj2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.261792564s
Jun 20 19:52:49.269: INFO: Pod "pod-subpath-test-dynamicpv-4wj2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.326104903s
Jun 20 19:52:51.334: INFO: Pod "pod-subpath-test-dynamicpv-4wj2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.391048344s
Jun 20 19:52:53.397: INFO: Pod "pod-subpath-test-dynamicpv-4wj2": Phase="Pending", Reason="", readiness=false. Elapsed: 12.454240358s
Jun 20 19:52:55.460: INFO: Pod "pod-subpath-test-dynamicpv-4wj2": Phase="Pending", Reason="", readiness=false. Elapsed: 14.516984686s
Jun 20 19:52:57.523: INFO: Pod "pod-subpath-test-dynamicpv-4wj2": Phase="Pending", Reason="", readiness=false. Elapsed: 16.580188s
Jun 20 19:52:59.588: INFO: Pod "pod-subpath-test-dynamicpv-4wj2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.644674151s
STEP: Saw pod success
Jun 20 19:52:59.588: INFO: Pod "pod-subpath-test-dynamicpv-4wj2" satisfied condition "Succeeded or Failed"
Jun 20 19:52:59.651: INFO: Trying to get logs from node ip-172-20-55-123.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-4wj2 container test-container-volume-dynamicpv-4wj2: <nil>
STEP: delete the pod
Jun 20 19:52:59.964: INFO: Waiting for pod pod-subpath-test-dynamicpv-4wj2 to disappear
Jun 20 19:53:00.038: INFO: Pod pod-subpath-test-dynamicpv-4wj2 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-4wj2
Jun 20 19:53:00.038: INFO: Deleting pod "pod-subpath-test-dynamicpv-4wj2" in namespace "provisioning-3611"
... skipping 119 lines ...
Jun 20 19:53:19.649: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4328-e2e-scqx8jz
STEP: creating a claim
Jun 20 19:53:19.715: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-9n2l
STEP: Creating a pod to test subpath
Jun 20 19:53:19.914: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-9n2l" in namespace "provisioning-4328" to be "Succeeded or Failed"
Jun 20 19:53:19.979: INFO: Pod "pod-subpath-test-dynamicpv-9n2l": Phase="Pending", Reason="", readiness=false. Elapsed: 64.971878ms
Jun 20 19:53:22.045: INFO: Pod "pod-subpath-test-dynamicpv-9n2l": Phase="Pending", Reason="", readiness=false. Elapsed: 2.130358422s
Jun 20 19:53:24.110: INFO: Pod "pod-subpath-test-dynamicpv-9n2l": Phase="Pending", Reason="", readiness=false. Elapsed: 4.19569583s
Jun 20 19:53:26.176: INFO: Pod "pod-subpath-test-dynamicpv-9n2l": Phase="Pending", Reason="", readiness=false. Elapsed: 6.261938209s
Jun 20 19:53:28.251: INFO: Pod "pod-subpath-test-dynamicpv-9n2l": Phase="Pending", Reason="", readiness=false. Elapsed: 8.336906102s
Jun 20 19:53:30.316: INFO: Pod "pod-subpath-test-dynamicpv-9n2l": Phase="Pending", Reason="", readiness=false. Elapsed: 10.402070321s
Jun 20 19:53:32.383: INFO: Pod "pod-subpath-test-dynamicpv-9n2l": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.468264534s
STEP: Saw pod success
Jun 20 19:53:32.383: INFO: Pod "pod-subpath-test-dynamicpv-9n2l" satisfied condition "Succeeded or Failed"
Jun 20 19:53:32.447: INFO: Trying to get logs from node ip-172-20-55-123.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-9n2l container test-container-subpath-dynamicpv-9n2l: <nil>
STEP: delete the pod
Jun 20 19:53:32.592: INFO: Waiting for pod pod-subpath-test-dynamicpv-9n2l to disappear
Jun 20 19:53:32.656: INFO: Pod pod-subpath-test-dynamicpv-9n2l no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-9n2l
Jun 20 19:53:32.656: INFO: Deleting pod "pod-subpath-test-dynamicpv-9n2l" in namespace "provisioning-4328"
... skipping 25 lines ...