This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-06-13 00:06
Elapsed30m40s
Revisionmaster

No Test Failures!


Error lines from build-log.txt

... skipping 524 lines ...
I0613 00:13:48.123218   17139 up.go:43] Cleaning up any leaked resources from previous cluster
I0613 00:13:48.123234   17139 dumplogs.go:38] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops toolbox dump --name e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ubuntu
I0613 00:13:48.139352   17145 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0613 00:13:48.139479   17145 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io" not found
W0613 00:13:48.677828   17139 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0613 00:13:48.677912   17139 down.go:48] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops delete cluster --name e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --yes
I0613 00:13:48.692860   17155 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0613 00:13:48.692969   17155 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io" not found
I0613 00:13:49.185388   17139 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/06/13 00:13:49 failed to get external ip from metadata service: http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip returned 404
I0613 00:13:49.197762   17139 http.go:37] curl https://ip.jsb.workers.dev
I0613 00:13:49.347978   17139 up.go:144] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops create cluster --name e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --cloud aws --kubernetes-version 1.21.0 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --networking calico --override=cluster.spec.cloudConfig.awsEBSCSIDriver.enabled=true --override=cluster.spec.snapshotController.enabled=true --override=cluster.spec.certManager.enabled=true --admin-access 34.69.21.147/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones us-east-2a --master-size c5.large
I0613 00:13:49.365968   17170 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0613 00:13:49.366111   17170 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I0613 00:13:49.414954   17170 create_cluster.go:728] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0613 00:13:49.908554   17170 new_cluster.go:1039]  Cloud Provider ID = aws
... skipping 40 lines ...

I0613 00:14:14.218082   17139 up.go:181] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops validate cluster --name e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0613 00:14:14.235422   17191 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0613 00:14:14.235718   17191 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io

W0613 00:14:15.200967   17191 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0613 00:14:25.252023   17191 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0613 00:14:35.286208   17191 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0613 00:14:45.333550   17191 validate_cluster.go:221] (will retry): cluster not yet healthy
W0613 00:14:55.353612   17191 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0613 00:15:05.384713   17191 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0613 00:15:15.419410   17191 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0613 00:15:25.450833   17191 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0613 00:15:35.482211   17191 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0613 00:15:45.519181   17191 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0613 00:15:55.550742   17191 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0613 00:16:05.582669   17191 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0613 00:16:15.619561   17191 validate_cluster.go:221] (will retry): cluster not yet healthy
W0613 00:16:25.654843   17191 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0613 00:16:35.686937   17191 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0613 00:16:45.717304   17191 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0613 00:16:55.766762   17191 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0613 00:17:05.836698   17191 validate_cluster.go:221] (will retry): cluster not yet healthy
W0613 00:17:15.856545   17191 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0613 00:17:25.888567   17191 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0613 00:17:35.921371   17191 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0613 00:17:45.953414   17191 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 18 lines ...
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-km6rs				system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-km6rs" is pending
Pod	kube-system/ebs-csi-node-5clmd						system-node-critical pod "ebs-csi-node-5clmd" is pending
Pod	kube-system/ebs-csi-node-5dm8q						system-node-critical pod "ebs-csi-node-5dm8q" is pending
Pod	kube-system/kube-proxy-ip-172-20-32-240.us-east-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-32-240.us-east-2.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-44-97.us-east-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-44-97.us-east-2.compute.internal" is pending

Validation Failed
W0613 00:17:57.166836   17191 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 20 lines ...
Pod	kube-system/ebs-csi-node-5dm8q						system-node-critical pod "ebs-csi-node-5dm8q" is pending
Pod	kube-system/ebs-csi-node-jgmbp						system-node-critical pod "ebs-csi-node-jgmbp" is pending
Pod	kube-system/ebs-csi-node-qwj2x						system-node-critical pod "ebs-csi-node-qwj2x" is pending
Pod	kube-system/kube-proxy-ip-172-20-56-187.us-east-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-56-187.us-east-2.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-58-40.us-east-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-58-40.us-east-2.compute.internal" is pending

Validation Failed
W0613 00:18:08.079653   17191 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 14 lines ...
Pod	kube-system/calico-node-lfgbc			system-node-critical pod "calico-node-lfgbc" is pending
Pod	kube-system/calico-node-mcbcz			system-node-critical pod "calico-node-mcbcz" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-dlrr4	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-dlrr4" is pending
Pod	kube-system/coredns-f45c4bf76-gwljs		system-cluster-critical pod "coredns-f45c4bf76-gwljs" is pending
Pod	kube-system/ebs-csi-node-jgmbp			system-node-critical pod "ebs-csi-node-jgmbp" is pending

Validation Failed
W0613 00:18:19.028067   17191 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME				MESSAGE
Pod	kube-system/calico-node-8phn7	system-node-critical pod "calico-node-8phn7" is not ready (calico-node)
Pod	kube-system/calico-node-lfgbc	system-node-critical pod "calico-node-lfgbc" is not ready (calico-node)
Pod	kube-system/calico-node-mcbcz	system-node-critical pod "calico-node-mcbcz" is not ready (calico-node)

Validation Failed
W0613 00:18:29.941916   17191 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 269 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if non-existent subpath is outside the volume [Slow][LinuxOnly] [BeforeEach]
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

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

    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 277 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.8OXTe6tDm/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.8OXTe6tDm/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly] [BeforeEach]
      /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 190 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath directory is outside the volume [Slow][LinuxOnly] [BeforeEach]
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

    Driver "ebs.csi.aws.com" does not support volume type "PreprovisionedPV" - skipping

    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 63 lines ...
Jun 13 00:22:24.963: INFO: AfterEach: Cleaning up test resources


S [SKIPPING] in Spec Setup (BeforeEach) [0.966 seconds]
[sig-storage] PersistentVolumes:vsphere [Feature:vsphere]
/tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/utils/framework.go:23
  should test that deleting a PVC before the pod does not cause pod deletion to fail on vsphere volume detach [BeforeEach]
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:148

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 390 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 13 00:22:24.395: INFO: >>> kubeConfig: /root/.kube/config
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]
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 13 00:22:27.038: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 13 00:22:27.623: INFO: Successfully created a new PD: "aws://us-east-2a/vol-0d7130918db2f6bfb".
Jun 13 00:22:27.623: INFO: Creating resource for pre-provisioned PV
Jun 13 00:22:27.623: INFO: Creating PVC and PV
... skipping 8 lines ...
Jun 13 00:22:37.937: INFO: PersistentVolumeClaim pvc-pbq6q found but phase is Pending instead of Bound.
Jun 13 00:22:39.968: INFO: PersistentVolumeClaim pvc-pbq6q found but phase is Pending instead of Bound.
Jun 13 00:22:41.999: INFO: PersistentVolumeClaim pvc-pbq6q found and phase=Bound (14.251060839s)
Jun 13 00:22:41.999: INFO: Waiting up to 3m0s for PersistentVolume aws-rpqm6 to have phase Bound
Jun 13 00:22:42.029: INFO: PersistentVolume aws-rpqm6 found and phase=Bound (30.055611ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 13 00:22:44.221: INFO: Deleting pod "pod-b7e7e979-e200-400a-a6be-d3cd1f80df91" in namespace "volumemode-9647"
Jun 13 00:22:44.253: INFO: Wait up to 5m0s for pod "pod-b7e7e979-e200-400a-a6be-d3cd1f80df91" to be fully deleted
STEP: Deleting pv and pvc
Jun 13 00:22:54.316: INFO: Deleting PersistentVolumeClaim "pvc-pbq6q"
Jun 13 00:22:54.346: INFO: Deleting PersistentVolume "aws-rpqm6"
Jun 13 00:22:54.485: INFO: Couldn't delete PD "aws://us-east-2a/vol-0d7130918db2f6bfb", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d7130918db2f6bfb is currently attached to i-008e8334048ae093c
	status code: 400, request id: 05fd2fbb-4a93-4508-bfb0-1c4f651f5683
Jun 13 00:22:59.731: INFO: Couldn't delete PD "aws://us-east-2a/vol-0d7130918db2f6bfb", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d7130918db2f6bfb is currently attached to i-008e8334048ae093c
	status code: 400, request id: 66d09e02-beef-4c0a-8475-49f4067dcc91
Jun 13 00:23:04.996: INFO: Couldn't delete PD "aws://us-east-2a/vol-0d7130918db2f6bfb", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d7130918db2f6bfb is currently attached to i-008e8334048ae093c
	status code: 400, request id: e01a9f01-7e3f-4012-b2b0-aab761dfdc39
Jun 13 00:23:10.300: INFO: Successfully deleted PD "aws://us-east-2a/vol-0d7130918db2f6bfb".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 13 00:23:10.300: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-9647" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.8OXTe6tDm/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.8OXTe6tDm/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail to use a volume in a pod with mismatched mode [Slow]
      /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 10 lines ...
Jun 13 00:22:25.022: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2047l47j7
STEP: creating a claim
Jun 13 00:22:25.053: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-w99h
STEP: Creating a pod to test subpath
Jun 13 00:22:25.149: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-w99h" in namespace "provisioning-2047" to be "Succeeded or Failed"
Jun 13 00:22:25.181: INFO: Pod "pod-subpath-test-dynamicpv-w99h": Phase="Pending", Reason="", readiness=false. Elapsed: 31.514239ms
Jun 13 00:22:27.213: INFO: Pod "pod-subpath-test-dynamicpv-w99h": Phase="Pending", Reason="", readiness=false. Elapsed: 2.063232693s
Jun 13 00:22:29.245: INFO: Pod "pod-subpath-test-dynamicpv-w99h": Phase="Pending", Reason="", readiness=false. Elapsed: 4.095512893s
Jun 13 00:22:31.278: INFO: Pod "pod-subpath-test-dynamicpv-w99h": Phase="Pending", Reason="", readiness=false. Elapsed: 6.128105874s
Jun 13 00:22:33.310: INFO: Pod "pod-subpath-test-dynamicpv-w99h": Phase="Pending", Reason="", readiness=false. Elapsed: 8.160393439s
Jun 13 00:22:35.343: INFO: Pod "pod-subpath-test-dynamicpv-w99h": Phase="Pending", Reason="", readiness=false. Elapsed: 10.193755396s
... skipping 6 lines ...
Jun 13 00:22:49.571: INFO: Pod "pod-subpath-test-dynamicpv-w99h": Phase="Pending", Reason="", readiness=false. Elapsed: 24.421615775s
Jun 13 00:22:51.603: INFO: Pod "pod-subpath-test-dynamicpv-w99h": Phase="Pending", Reason="", readiness=false. Elapsed: 26.453289175s
Jun 13 00:22:53.636: INFO: Pod "pod-subpath-test-dynamicpv-w99h": Phase="Pending", Reason="", readiness=false. Elapsed: 28.486208789s
Jun 13 00:22:55.675: INFO: Pod "pod-subpath-test-dynamicpv-w99h": Phase="Pending", Reason="", readiness=false. Elapsed: 30.525423073s
Jun 13 00:22:57.708: INFO: Pod "pod-subpath-test-dynamicpv-w99h": Phase="Succeeded", Reason="", readiness=false. Elapsed: 32.557987042s
STEP: Saw pod success
Jun 13 00:22:57.708: INFO: Pod "pod-subpath-test-dynamicpv-w99h" satisfied condition "Succeeded or Failed"
Jun 13 00:22:57.743: INFO: Trying to get logs from node ip-172-20-56-187.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-w99h container test-container-subpath-dynamicpv-w99h: <nil>
STEP: delete the pod
Jun 13 00:22:57.818: INFO: Waiting for pod pod-subpath-test-dynamicpv-w99h to disappear
Jun 13 00:22:57.849: INFO: Pod pod-subpath-test-dynamicpv-w99h no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-w99h
Jun 13 00:22:57.849: INFO: Deleting pod "pod-subpath-test-dynamicpv-w99h" in namespace "provisioning-2047"
... skipping 47 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 13 00:22:24.338: INFO: >>> kubeConfig: /root/.kube/config
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]
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 13 00:22:26.687: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 13 00:22:26.688: INFO: Creating resource for dynamic PV
Jun 13 00:22:26.688: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-8266fvn7v
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 13 00:22:38.905: INFO: Deleting pod "pod-9f7ac443-79e7-4a4e-a4b0-95e42c071b45" in namespace "volumemode-8266"
Jun 13 00:22:38.939: INFO: Wait up to 5m0s for pod "pod-9f7ac443-79e7-4a4e-a4b0-95e42c071b45" to be fully deleted
STEP: Deleting pvc
Jun 13 00:22:43.057: INFO: Deleting PersistentVolumeClaim "awsxkh2n"
Jun 13 00:22:43.087: INFO: Waiting up to 5m0s for PersistentVolume pvc-9f89c2b1-f514-4a6e-88b8-5cf8c4875af7 to get deleted
Jun 13 00:22:43.117: INFO: PersistentVolume pvc-9f89c2b1-f514-4a6e-88b8-5cf8c4875af7 found and phase=Released (29.830318ms)
... skipping 15 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.8OXTe6tDm/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.8OXTe6tDm/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (block volmode)] volumeMode
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail to use a volume in a pod with mismatched mode [Slow]
      /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow]
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 13 00:23:18.460: INFO: Driver supports dynamic provisioning, skipping PreprovisionedPV pattern
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow]
... skipping 23 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.002 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath directory is outside the volume [Slow][LinuxOnly] [BeforeEach]
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

    Driver "ebs.csi.aws.com" does not support volume type "InlineVolume" - skipping

    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 152 lines ...
Jun 13 00:22:25.968: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3011xrtkv
STEP: creating a claim
Jun 13 00:22:26.005: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-94c4
STEP: Creating a pod to test subpath
Jun 13 00:22:26.104: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-94c4" in namespace "provisioning-3011" to be "Succeeded or Failed"
Jun 13 00:22:26.134: INFO: Pod "pod-subpath-test-dynamicpv-94c4": Phase="Pending", Reason="", readiness=false. Elapsed: 30.470525ms
Jun 13 00:22:28.166: INFO: Pod "pod-subpath-test-dynamicpv-94c4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061919516s
Jun 13 00:22:30.199: INFO: Pod "pod-subpath-test-dynamicpv-94c4": Phase="Pending", Reason="", readiness=false. Elapsed: 4.095705691s
Jun 13 00:22:32.232: INFO: Pod "pod-subpath-test-dynamicpv-94c4": Phase="Pending", Reason="", readiness=false. Elapsed: 6.128301261s
Jun 13 00:22:34.264: INFO: Pod "pod-subpath-test-dynamicpv-94c4": Phase="Pending", Reason="", readiness=false. Elapsed: 8.160024752s
Jun 13 00:22:36.296: INFO: Pod "pod-subpath-test-dynamicpv-94c4": Phase="Pending", Reason="", readiness=false. Elapsed: 10.192148912s
... skipping 5 lines ...
Jun 13 00:22:48.493: INFO: Pod "pod-subpath-test-dynamicpv-94c4": Phase="Pending", Reason="", readiness=false. Elapsed: 22.389141709s
Jun 13 00:22:50.525: INFO: Pod "pod-subpath-test-dynamicpv-94c4": Phase="Pending", Reason="", readiness=false. Elapsed: 24.421107634s
Jun 13 00:22:52.557: INFO: Pod "pod-subpath-test-dynamicpv-94c4": Phase="Pending", Reason="", readiness=false. Elapsed: 26.453834144s
Jun 13 00:22:54.589: INFO: Pod "pod-subpath-test-dynamicpv-94c4": Phase="Pending", Reason="", readiness=false. Elapsed: 28.484893113s
Jun 13 00:22:56.619: INFO: Pod "pod-subpath-test-dynamicpv-94c4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 30.515799102s
STEP: Saw pod success
Jun 13 00:22:56.620: INFO: Pod "pod-subpath-test-dynamicpv-94c4" satisfied condition "Succeeded or Failed"
Jun 13 00:22:56.650: INFO: Trying to get logs from node ip-172-20-58-40.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-94c4 container test-container-volume-dynamicpv-94c4: <nil>
STEP: delete the pod
Jun 13 00:22:56.720: INFO: Waiting for pod pod-subpath-test-dynamicpv-94c4 to disappear
Jun 13 00:22:56.751: INFO: Pod pod-subpath-test-dynamicpv-94c4 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-94c4
Jun 13 00:22:56.751: INFO: Deleting pod "pod-subpath-test-dynamicpv-94c4" in namespace "provisioning-3011"
... skipping 126 lines ...
Jun 13 00:22:24.267: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2026-e2e-sc2nlp5
STEP: creating a claim
Jun 13 00:22:24.304: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-qncx
STEP: Creating a pod to test subpath
Jun 13 00:22:24.433: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-qncx" in namespace "provisioning-2026" to be "Succeeded or Failed"
Jun 13 00:22:24.469: INFO: Pod "pod-subpath-test-dynamicpv-qncx": Phase="Pending", Reason="", readiness=false. Elapsed: 36.119922ms
Jun 13 00:22:26.501: INFO: Pod "pod-subpath-test-dynamicpv-qncx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.068402405s
Jun 13 00:22:28.533: INFO: Pod "pod-subpath-test-dynamicpv-qncx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.100652809s
Jun 13 00:22:30.566: INFO: Pod "pod-subpath-test-dynamicpv-qncx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.133304278s
Jun 13 00:22:32.604: INFO: Pod "pod-subpath-test-dynamicpv-qncx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.170870475s
Jun 13 00:22:34.635: INFO: Pod "pod-subpath-test-dynamicpv-qncx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.20218039s
... skipping 5 lines ...
Jun 13 00:22:46.830: INFO: Pod "pod-subpath-test-dynamicpv-qncx": Phase="Pending", Reason="", readiness=false. Elapsed: 22.39718426s
Jun 13 00:22:48.864: INFO: Pod "pod-subpath-test-dynamicpv-qncx": Phase="Pending", Reason="", readiness=false. Elapsed: 24.430801625s
Jun 13 00:22:50.895: INFO: Pod "pod-subpath-test-dynamicpv-qncx": Phase="Pending", Reason="", readiness=false. Elapsed: 26.462180629s
Jun 13 00:22:52.930: INFO: Pod "pod-subpath-test-dynamicpv-qncx": Phase="Pending", Reason="", readiness=false. Elapsed: 28.496808481s
Jun 13 00:22:54.962: INFO: Pod "pod-subpath-test-dynamicpv-qncx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 30.528884546s
STEP: Saw pod success
Jun 13 00:22:54.962: INFO: Pod "pod-subpath-test-dynamicpv-qncx" satisfied condition "Succeeded or Failed"
Jun 13 00:22:54.993: INFO: Trying to get logs from node ip-172-20-44-97.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-qncx container test-container-volume-dynamicpv-qncx: <nil>
STEP: delete the pod
Jun 13 00:22:55.098: INFO: Waiting for pod pod-subpath-test-dynamicpv-qncx to disappear
Jun 13 00:22:55.128: INFO: Pod pod-subpath-test-dynamicpv-qncx no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-qncx
Jun 13 00:22:55.128: INFO: Deleting pod "pod-subpath-test-dynamicpv-qncx" in namespace "provisioning-2026"
... skipping 41 lines ...
Jun 13 00:22:25.567: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-267-e2e-scqrtrx
STEP: creating a claim
Jun 13 00:22:25.598: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-5cfk
STEP: Creating a pod to test exec-volume-test
Jun 13 00:22:25.699: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-5cfk" in namespace "volume-267" to be "Succeeded or Failed"
Jun 13 00:22:25.728: INFO: Pod "exec-volume-test-dynamicpv-5cfk": Phase="Pending", Reason="", readiness=false. Elapsed: 29.318127ms
Jun 13 00:22:27.759: INFO: Pod "exec-volume-test-dynamicpv-5cfk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.059832516s
Jun 13 00:22:29.791: INFO: Pod "exec-volume-test-dynamicpv-5cfk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.091974823s
Jun 13 00:22:31.823: INFO: Pod "exec-volume-test-dynamicpv-5cfk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.123747065s
Jun 13 00:22:33.853: INFO: Pod "exec-volume-test-dynamicpv-5cfk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.154364541s
Jun 13 00:22:35.885: INFO: Pod "exec-volume-test-dynamicpv-5cfk": Phase="Pending", Reason="", readiness=false. Elapsed: 10.18612653s
... skipping 5 lines ...
Jun 13 00:22:48.069: INFO: Pod "exec-volume-test-dynamicpv-5cfk": Phase="Pending", Reason="", readiness=false. Elapsed: 22.370310661s
Jun 13 00:22:50.100: INFO: Pod "exec-volume-test-dynamicpv-5cfk": Phase="Pending", Reason="", readiness=false. Elapsed: 24.40114477s
Jun 13 00:22:52.131: INFO: Pod "exec-volume-test-dynamicpv-5cfk": Phase="Pending", Reason="", readiness=false. Elapsed: 26.432482161s
Jun 13 00:22:54.161: INFO: Pod "exec-volume-test-dynamicpv-5cfk": Phase="Pending", Reason="", readiness=false. Elapsed: 28.462246403s
Jun 13 00:22:56.192: INFO: Pod "exec-volume-test-dynamicpv-5cfk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 30.492683539s
STEP: Saw pod success
Jun 13 00:22:56.192: INFO: Pod "exec-volume-test-dynamicpv-5cfk" satisfied condition "Succeeded or Failed"
Jun 13 00:22:56.222: INFO: Trying to get logs from node ip-172-20-58-40.us-east-2.compute.internal pod exec-volume-test-dynamicpv-5cfk container exec-container-dynamicpv-5cfk: <nil>
STEP: delete the pod
Jun 13 00:22:56.288: INFO: Waiting for pod exec-volume-test-dynamicpv-5cfk to disappear
Jun 13 00:22:56.317: INFO: Pod exec-volume-test-dynamicpv-5cfk no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-5cfk
Jun 13 00:22:56.318: INFO: Deleting pod "exec-volume-test-dynamicpv-5cfk" in namespace "volume-267"
... skipping 63 lines ...
Jun 13 00:22:24.503: INFO: Creating resource for dynamic PV
Jun 13 00:22:24.503: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5836-e2e-scqbfck
STEP: creating a claim
Jun 13 00:22:24.535: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-5836
Jun 13 00:22:24.633: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-5836" in namespace "provisioning-5836" to be "Succeeded or Failed"
Jun 13 00:22:24.664: INFO: Pod "volume-prep-provisioning-5836": Phase="Pending", Reason="", readiness=false. Elapsed: 30.638175ms
Jun 13 00:22:26.695: INFO: Pod "volume-prep-provisioning-5836": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061766991s
Jun 13 00:22:28.727: INFO: Pod "volume-prep-provisioning-5836": Phase="Pending", Reason="", readiness=false. Elapsed: 4.093890138s
Jun 13 00:22:30.759: INFO: Pod "volume-prep-provisioning-5836": Phase="Pending", Reason="", readiness=false. Elapsed: 6.126230489s
Jun 13 00:22:32.791: INFO: Pod "volume-prep-provisioning-5836": Phase="Pending", Reason="", readiness=false. Elapsed: 8.158111231s
Jun 13 00:22:34.824: INFO: Pod "volume-prep-provisioning-5836": Phase="Pending", Reason="", readiness=false. Elapsed: 10.191311532s
Jun 13 00:22:36.856: INFO: Pod "volume-prep-provisioning-5836": Phase="Pending", Reason="", readiness=false. Elapsed: 12.223014157s
Jun 13 00:22:38.893: INFO: Pod "volume-prep-provisioning-5836": Phase="Pending", Reason="", readiness=false. Elapsed: 14.260198367s
Jun 13 00:22:40.926: INFO: Pod "volume-prep-provisioning-5836": Phase="Pending", Reason="", readiness=false. Elapsed: 16.293225716s
Jun 13 00:22:42.959: INFO: Pod "volume-prep-provisioning-5836": Phase="Pending", Reason="", readiness=false. Elapsed: 18.325685039s
Jun 13 00:22:44.990: INFO: Pod "volume-prep-provisioning-5836": Phase="Pending", Reason="", readiness=false. Elapsed: 20.357082892s
Jun 13 00:22:47.021: INFO: Pod "volume-prep-provisioning-5836": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.388299773s
STEP: Saw pod success
Jun 13 00:22:47.021: INFO: Pod "volume-prep-provisioning-5836" satisfied condition "Succeeded or Failed"
Jun 13 00:22:47.021: INFO: Deleting pod "volume-prep-provisioning-5836" in namespace "provisioning-5836"
Jun 13 00:22:47.060: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-5836" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-csxn
STEP: Checking for subpath error in container status
Jun 13 00:22:57.187: INFO: Deleting pod "pod-subpath-test-dynamicpv-csxn" in namespace "provisioning-5836"
Jun 13 00:22:57.225: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-csxn" to be fully deleted
STEP: Deleting pod
Jun 13 00:22:57.255: INFO: Deleting pod "pod-subpath-test-dynamicpv-csxn" in namespace "provisioning-5836"
STEP: Deleting pvc
Jun 13 00:22:57.347: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comg2jdb"
... skipping 170 lines ...
Jun 13 00:22:24.147: INFO: Creating resource for dynamic PV
Jun 13 00:22:24.147: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5863glf9x
STEP: creating a claim
Jun 13 00:22:24.194: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-5863
Jun 13 00:22:24.310: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-5863" in namespace "provisioning-5863" to be "Succeeded or Failed"
Jun 13 00:22:24.340: INFO: Pod "volume-prep-provisioning-5863": Phase="Pending", Reason="", readiness=false. Elapsed: 30.244231ms
Jun 13 00:22:26.372: INFO: Pod "volume-prep-provisioning-5863": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061420766s
Jun 13 00:22:28.403: INFO: Pod "volume-prep-provisioning-5863": Phase="Pending", Reason="", readiness=false. Elapsed: 4.092770566s
Jun 13 00:22:30.435: INFO: Pod "volume-prep-provisioning-5863": Phase="Pending", Reason="", readiness=false. Elapsed: 6.125273226s
Jun 13 00:22:32.467: INFO: Pod "volume-prep-provisioning-5863": Phase="Pending", Reason="", readiness=false. Elapsed: 8.157258328s
Jun 13 00:22:34.500: INFO: Pod "volume-prep-provisioning-5863": Phase="Pending", Reason="", readiness=false. Elapsed: 10.189620252s
... skipping 2 lines ...
Jun 13 00:22:40.600: INFO: Pod "volume-prep-provisioning-5863": Phase="Pending", Reason="", readiness=false. Elapsed: 16.289789658s
Jun 13 00:22:42.631: INFO: Pod "volume-prep-provisioning-5863": Phase="Pending", Reason="", readiness=false. Elapsed: 18.321089952s
Jun 13 00:22:44.663: INFO: Pod "volume-prep-provisioning-5863": Phase="Pending", Reason="", readiness=false. Elapsed: 20.352383853s
Jun 13 00:22:46.695: INFO: Pod "volume-prep-provisioning-5863": Phase="Pending", Reason="", readiness=false. Elapsed: 22.384757775s
Jun 13 00:22:48.727: INFO: Pod "volume-prep-provisioning-5863": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.417098727s
STEP: Saw pod success
Jun 13 00:22:48.727: INFO: Pod "volume-prep-provisioning-5863" satisfied condition "Succeeded or Failed"
Jun 13 00:22:48.727: INFO: Deleting pod "volume-prep-provisioning-5863" in namespace "provisioning-5863"
Jun 13 00:22:48.761: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-5863" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-p4sn
STEP: Checking for subpath error in container status
Jun 13 00:23:10.884: INFO: Deleting pod "pod-subpath-test-dynamicpv-p4sn" in namespace "provisioning-5863"
Jun 13 00:23:10.921: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-p4sn" to be fully deleted
STEP: Deleting pod
Jun 13 00:23:10.951: INFO: Deleting pod "pod-subpath-test-dynamicpv-p4sn" in namespace "provisioning-5863"
STEP: Deleting pvc
Jun 13 00:23:11.042: INFO: Deleting PersistentVolumeClaim "awspvsjf"
... skipping 38 lines ...
Jun 13 00:22:24.817: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1516b4wgc
STEP: creating a claim
Jun 13 00:22:24.851: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-2hrv
STEP: Creating a pod to test subpath
Jun 13 00:22:24.944: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-2hrv" in namespace "provisioning-1516" to be "Succeeded or Failed"
Jun 13 00:22:24.976: INFO: Pod "pod-subpath-test-dynamicpv-2hrv": Phase="Pending", Reason="", readiness=false. Elapsed: 31.708721ms
Jun 13 00:22:27.006: INFO: Pod "pod-subpath-test-dynamicpv-2hrv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.06177914s
Jun 13 00:22:29.037: INFO: Pod "pod-subpath-test-dynamicpv-2hrv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.092999957s
Jun 13 00:22:31.069: INFO: Pod "pod-subpath-test-dynamicpv-2hrv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.125149811s
Jun 13 00:22:33.101: INFO: Pod "pod-subpath-test-dynamicpv-2hrv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.156843415s
Jun 13 00:22:35.133: INFO: Pod "pod-subpath-test-dynamicpv-2hrv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.188750081s
... skipping 5 lines ...
Jun 13 00:22:47.320: INFO: Pod "pod-subpath-test-dynamicpv-2hrv": Phase="Pending", Reason="", readiness=false. Elapsed: 22.3760055s
Jun 13 00:22:49.351: INFO: Pod "pod-subpath-test-dynamicpv-2hrv": Phase="Pending", Reason="", readiness=false. Elapsed: 24.406624427s
Jun 13 00:22:51.384: INFO: Pod "pod-subpath-test-dynamicpv-2hrv": Phase="Pending", Reason="", readiness=false. Elapsed: 26.43975909s
Jun 13 00:22:53.416: INFO: Pod "pod-subpath-test-dynamicpv-2hrv": Phase="Pending", Reason="", readiness=false. Elapsed: 28.471498844s
Jun 13 00:22:55.447: INFO: Pod "pod-subpath-test-dynamicpv-2hrv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 30.50276275s
STEP: Saw pod success
Jun 13 00:22:55.447: INFO: Pod "pod-subpath-test-dynamicpv-2hrv" satisfied condition "Succeeded or Failed"
Jun 13 00:22:55.482: INFO: Trying to get logs from node ip-172-20-32-240.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-2hrv container test-container-subpath-dynamicpv-2hrv: <nil>
STEP: delete the pod
Jun 13 00:22:56.020: INFO: Waiting for pod pod-subpath-test-dynamicpv-2hrv to disappear
Jun 13 00:22:56.050: INFO: Pod pod-subpath-test-dynamicpv-2hrv no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-2hrv
Jun 13 00:22:56.050: INFO: Deleting pod "pod-subpath-test-dynamicpv-2hrv" in namespace "provisioning-1516"
... skipping 39 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.8OXTe6tDm/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.8OXTe6tDm/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if non-existent subpath is outside the volume [Slow][LinuxOnly] [BeforeEach]
      /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 728 lines ...
Jun 13 00:23:45.732: INFO: Waiting for pod aws-client to disappear
Jun 13 00:23:45.762: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 13 00:23:45.762: INFO: Deleting PersistentVolumeClaim "pvc-5t5jw"
Jun 13 00:23:45.795: INFO: Deleting PersistentVolume "aws-gljpc"
Jun 13 00:23:46.064: INFO: Couldn't delete PD "aws://us-east-2a/vol-0950d3837a9b758b3", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0950d3837a9b758b3 is currently attached to i-008e8334048ae093c
	status code: 400, request id: 4ba061c1-7ad0-4678-a2bb-ccbe54fd3360
Jun 13 00:23:51.313: INFO: Couldn't delete PD "aws://us-east-2a/vol-0950d3837a9b758b3", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0950d3837a9b758b3 is currently attached to i-008e8334048ae093c
	status code: 400, request id: 17c7c701-66c5-4755-aee7-4a3c614b38a7
Jun 13 00:23:56.558: INFO: Couldn't delete PD "aws://us-east-2a/vol-0950d3837a9b758b3", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0950d3837a9b758b3 is currently attached to i-008e8334048ae093c
	status code: 400, request id: 7c365133-08b3-47a1-a4cd-a2febac32af3
Jun 13 00:24:01.791: INFO: Couldn't delete PD "aws://us-east-2a/vol-0950d3837a9b758b3", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0950d3837a9b758b3 is currently attached to i-008e8334048ae093c
	status code: 400, request id: 779ef114-3524-43f1-ab33-a86b1ad7de39
Jun 13 00:24:07.043: INFO: Successfully deleted PD "aws://us-east-2a/vol-0950d3837a9b758b3".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 13 00:24:07.043: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-9523" for this suite.
... skipping 22 lines ...
Jun 13 00:22:28.036: INFO: Creating resource for dynamic PV
Jun 13 00:22:28.036: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-7858-e2e-sc94bsz
STEP: creating a claim
Jun 13 00:22:28.067: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 13 00:22:28.162: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-h4vpc" in namespace "snapshotting-7858" to be "Succeeded or Failed"
Jun 13 00:22:28.192: INFO: Pod "pvc-snapshottable-tester-h4vpc": Phase="Pending", Reason="", readiness=false. Elapsed: 30.201865ms
Jun 13 00:22:30.224: INFO: Pod "pvc-snapshottable-tester-h4vpc": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061264967s
Jun 13 00:22:32.262: INFO: Pod "pvc-snapshottable-tester-h4vpc": Phase="Pending", Reason="", readiness=false. Elapsed: 4.099697046s
Jun 13 00:22:34.294: INFO: Pod "pvc-snapshottable-tester-h4vpc": Phase="Pending", Reason="", readiness=false. Elapsed: 6.131637914s
Jun 13 00:22:36.327: INFO: Pod "pvc-snapshottable-tester-h4vpc": Phase="Pending", Reason="", readiness=false. Elapsed: 8.165063959s
Jun 13 00:22:38.361: INFO: Pod "pvc-snapshottable-tester-h4vpc": Phase="Pending", Reason="", readiness=false. Elapsed: 10.198646889s
Jun 13 00:22:40.391: INFO: Pod "pvc-snapshottable-tester-h4vpc": Phase="Pending", Reason="", readiness=false. Elapsed: 12.229167181s
Jun 13 00:22:42.424: INFO: Pod "pvc-snapshottable-tester-h4vpc": Phase="Pending", Reason="", readiness=false. Elapsed: 14.261558176s
Jun 13 00:22:44.455: INFO: Pod "pvc-snapshottable-tester-h4vpc": Phase="Pending", Reason="", readiness=false. Elapsed: 16.292617035s
Jun 13 00:22:46.487: INFO: Pod "pvc-snapshottable-tester-h4vpc": Phase="Pending", Reason="", readiness=false. Elapsed: 18.324361997s
Jun 13 00:22:48.518: INFO: Pod "pvc-snapshottable-tester-h4vpc": Phase="Pending", Reason="", readiness=false. Elapsed: 20.355900851s
Jun 13 00:22:50.550: INFO: Pod "pvc-snapshottable-tester-h4vpc": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.388106567s
STEP: Saw pod success
Jun 13 00:22:50.551: INFO: Pod "pvc-snapshottable-tester-h4vpc" satisfied condition "Succeeded or Failed"
Jun 13 00:22:51.337: INFO: Pod pvc-snapshottable-tester-h4vpc has the following logs: 
Jun 13 00:22:51.337: INFO: Deleting pod "pvc-snapshottable-tester-h4vpc" in namespace "snapshotting-7858"
Jun 13 00:22:51.373: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-h4vpc" to be fully deleted
Jun 13 00:22:51.405: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comtbwwk] to have phase Bound
Jun 13 00:22:51.435: INFO: PersistentVolumeClaim ebs.csi.aws.comtbwwk found and phase=Bound (30.077568ms)
STEP: [init] checking the claim
... skipping 13 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:243
STEP: checking the snapshot
STEP: checking the SnapshotContent
STEP: Modifying source data test
STEP: modifying the data in the source PVC
Jun 13 00:22:57.900: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-8dwxg" in namespace "snapshotting-7858" to be "Succeeded or Failed"
Jun 13 00:22:57.931: INFO: Pod "pvc-snapshottable-data-tester-8dwxg": Phase="Pending", Reason="", readiness=false. Elapsed: 30.951847ms
Jun 13 00:22:59.968: INFO: Pod "pvc-snapshottable-data-tester-8dwxg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.068393497s
Jun 13 00:23:01.999: INFO: Pod "pvc-snapshottable-data-tester-8dwxg": Phase="Pending", Reason="", readiness=false. Elapsed: 4.099338976s
Jun 13 00:23:04.030: INFO: Pod "pvc-snapshottable-data-tester-8dwxg": Phase="Pending", Reason="", readiness=false. Elapsed: 6.130205799s
Jun 13 00:23:06.062: INFO: Pod "pvc-snapshottable-data-tester-8dwxg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.161969057s
STEP: Saw pod success
Jun 13 00:23:06.062: INFO: Pod "pvc-snapshottable-data-tester-8dwxg" satisfied condition "Succeeded or Failed"
Jun 13 00:23:06.123: INFO: Pod pvc-snapshottable-data-tester-8dwxg has the following logs: 
Jun 13 00:23:06.123: INFO: Deleting pod "pvc-snapshottable-data-tester-8dwxg" in namespace "snapshotting-7858"
Jun 13 00:23:06.159: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-8dwxg" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 13 00:23:20.314: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-7858 exec restored-pvc-tester-lh2dw --namespace=snapshotting-7858 -- cat /mnt/test/data'
... skipping 71 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 13 00:23:36.406: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename provisioning
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail if non-existent subpath is outside the volume [Slow][LinuxOnly]
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun 13 00:23:36.562: INFO: Creating resource for dynamic PV
Jun 13 00:23:36.562: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3432-e2e-scp9pj4
STEP: creating a claim
Jun 13 00:23:36.594: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-j72q
STEP: Checking for subpath error in container status
Jun 13 00:23:46.755: INFO: Deleting pod "pod-subpath-test-dynamicpv-j72q" in namespace "provisioning-3432"
Jun 13 00:23:46.787: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-j72q" to be fully deleted
STEP: Deleting pod
Jun 13 00:23:58.851: INFO: Deleting pod "pod-subpath-test-dynamicpv-j72q" in namespace "provisioning-3432"
STEP: Deleting pvc
Jun 13 00:23:58.942: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comcgj48"
... skipping 10 lines ...

• [SLOW TEST:32.767 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if non-existent subpath is outside the volume [Slow][LinuxOnly]
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)(allowExpansion)] volume-expand
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (block volmode)(allowExpansion)] volume-expand
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 60 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.8OXTe6tDm/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.8OXTe6tDm/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath file is outside the volume [Slow][LinuxOnly] [BeforeEach]
      /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 12 lines ...
Jun 13 00:23:13.440: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-93046pz75
STEP: creating a claim
Jun 13 00:23:13.473: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-rdjj
STEP: Creating a pod to test exec-volume-test
Jun 13 00:23:13.568: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-rdjj" in namespace "volume-9304" to be "Succeeded or Failed"
Jun 13 00:23:13.599: INFO: Pod "exec-volume-test-dynamicpv-rdjj": Phase="Pending", Reason="", readiness=false. Elapsed: 30.821321ms
Jun 13 00:23:15.632: INFO: Pod "exec-volume-test-dynamicpv-rdjj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.063252963s
Jun 13 00:23:17.664: INFO: Pod "exec-volume-test-dynamicpv-rdjj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.095734885s
Jun 13 00:23:19.697: INFO: Pod "exec-volume-test-dynamicpv-rdjj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.128373698s
Jun 13 00:23:21.729: INFO: Pod "exec-volume-test-dynamicpv-rdjj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.161141864s
Jun 13 00:23:23.763: INFO: Pod "exec-volume-test-dynamicpv-rdjj": Phase="Pending", Reason="", readiness=false. Elapsed: 10.195218676s
... skipping 10 lines ...
Jun 13 00:23:46.121: INFO: Pod "exec-volume-test-dynamicpv-rdjj": Phase="Pending", Reason="", readiness=false. Elapsed: 32.552414831s
Jun 13 00:23:48.152: INFO: Pod "exec-volume-test-dynamicpv-rdjj": Phase="Pending", Reason="", readiness=false. Elapsed: 34.584134323s
Jun 13 00:23:50.183: INFO: Pod "exec-volume-test-dynamicpv-rdjj": Phase="Pending", Reason="", readiness=false. Elapsed: 36.615166477s
Jun 13 00:23:52.215: INFO: Pod "exec-volume-test-dynamicpv-rdjj": Phase="Pending", Reason="", readiness=false. Elapsed: 38.646682259s
Jun 13 00:23:54.249: INFO: Pod "exec-volume-test-dynamicpv-rdjj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 40.681100495s
STEP: Saw pod success
Jun 13 00:23:54.250: INFO: Pod "exec-volume-test-dynamicpv-rdjj" satisfied condition "Succeeded or Failed"
Jun 13 00:23:54.281: INFO: Trying to get logs from node ip-172-20-44-97.us-east-2.compute.internal pod exec-volume-test-dynamicpv-rdjj container exec-container-dynamicpv-rdjj: <nil>
STEP: delete the pod
Jun 13 00:23:54.351: INFO: Waiting for pod exec-volume-test-dynamicpv-rdjj to disappear
Jun 13 00:23:54.382: INFO: Pod exec-volume-test-dynamicpv-rdjj no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-rdjj
Jun 13 00:23:54.382: INFO: Deleting pod "exec-volume-test-dynamicpv-rdjj" in namespace "volume-9304"
... skipping 31 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath directory is outside the volume [Slow][LinuxOnly] [BeforeEach]
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

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

    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 8 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.8OXTe6tDm/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.8OXTe6tDm/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath directory is outside the volume [Slow][LinuxOnly] [BeforeEach]
      /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 57 lines ...
Jun 13 00:23:10.522: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5655-e2e-sc5zsh2
STEP: creating a claim
Jun 13 00:23:10.555: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-pthn
STEP: Creating a pod to test subpath
Jun 13 00:23:10.661: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-pthn" in namespace "provisioning-5655" to be "Succeeded or Failed"
Jun 13 00:23:10.692: INFO: Pod "pod-subpath-test-dynamicpv-pthn": Phase="Pending", Reason="", readiness=false. Elapsed: 30.973579ms
Jun 13 00:23:12.723: INFO: Pod "pod-subpath-test-dynamicpv-pthn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062450787s
Jun 13 00:23:14.754: INFO: Pod "pod-subpath-test-dynamicpv-pthn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.093145608s
Jun 13 00:23:16.788: INFO: Pod "pod-subpath-test-dynamicpv-pthn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.126999662s
Jun 13 00:23:18.820: INFO: Pod "pod-subpath-test-dynamicpv-pthn": Phase="Pending", Reason="", readiness=false. Elapsed: 8.159657272s
Jun 13 00:23:20.851: INFO: Pod "pod-subpath-test-dynamicpv-pthn": Phase="Pending", Reason="", readiness=false. Elapsed: 10.190592852s
... skipping 12 lines ...
Jun 13 00:23:47.285: INFO: Pod "pod-subpath-test-dynamicpv-pthn": Phase="Pending", Reason="", readiness=false. Elapsed: 36.624117657s
Jun 13 00:23:49.316: INFO: Pod "pod-subpath-test-dynamicpv-pthn": Phase="Pending", Reason="", readiness=false. Elapsed: 38.654950329s
Jun 13 00:23:51.346: INFO: Pod "pod-subpath-test-dynamicpv-pthn": Phase="Pending", Reason="", readiness=false. Elapsed: 40.68572348s
Jun 13 00:23:53.378: INFO: Pod "pod-subpath-test-dynamicpv-pthn": Phase="Pending", Reason="", readiness=false. Elapsed: 42.717257512s
Jun 13 00:23:55.409: INFO: Pod "pod-subpath-test-dynamicpv-pthn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 44.747913961s
STEP: Saw pod success
Jun 13 00:23:55.409: INFO: Pod "pod-subpath-test-dynamicpv-pthn" satisfied condition "Succeeded or Failed"
Jun 13 00:23:55.439: INFO: Trying to get logs from node ip-172-20-58-40.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-pthn container test-container-subpath-dynamicpv-pthn: <nil>
STEP: delete the pod
Jun 13 00:23:55.513: INFO: Waiting for pod pod-subpath-test-dynamicpv-pthn to disappear
Jun 13 00:23:55.543: INFO: Pod pod-subpath-test-dynamicpv-pthn no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-pthn
Jun 13 00:23:55.543: INFO: Deleting pod "pod-subpath-test-dynamicpv-pthn" in namespace "provisioning-5655"
... skipping 31 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.002 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.8OXTe6tDm/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]
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

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

    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:92
------------------------------
... skipping 50 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 13 00:23:18.929: INFO: >>> kubeConfig: /root/.kube/config
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 with backstepping is outside the volume [Slow][LinuxOnly]
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun 13 00:23:19.084: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 13 00:23:19.084: INFO: Creating resource for dynamic PV
Jun 13 00:23:19.084: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7768dbw9b
STEP: creating a claim
Jun 13 00:23:19.114: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-rrks
STEP: Checking for subpath error in container status
Jun 13 00:23:59.268: INFO: Deleting pod "pod-subpath-test-dynamicpv-rrks" in namespace "provisioning-7768"
Jun 13 00:23:59.298: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-rrks" to be fully deleted
STEP: Deleting pod
Jun 13 00:24:11.359: INFO: Deleting pod "pod-subpath-test-dynamicpv-rrks" in namespace "provisioning-7768"
STEP: Deleting pvc
Jun 13 00:24:11.445: INFO: Deleting PersistentVolumeClaim "awsw6dgs"
... skipping 11 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.8OXTe6tDm/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.8OXTe6tDm/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly]
      /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 9 lines ...
Jun 13 00:22:24.166: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1482-e2e-scwlgnk
STEP: creating a claim
Jun 13 00:22:24.200: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-4l9j
STEP: Creating a pod to test atomic-volume-subpath
Jun 13 00:22:24.321: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-4l9j" in namespace "provisioning-1482" to be "Succeeded or Failed"
Jun 13 00:22:24.352: INFO: Pod "pod-subpath-test-dynamicpv-4l9j": Phase="Pending", Reason="", readiness=false. Elapsed: 30.782569ms
Jun 13 00:22:26.384: INFO: Pod "pod-subpath-test-dynamicpv-4l9j": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062712661s
Jun 13 00:22:28.415: INFO: Pod "pod-subpath-test-dynamicpv-4l9j": Phase="Pending", Reason="", readiness=false. Elapsed: 4.093520515s
Jun 13 00:22:30.449: INFO: Pod "pod-subpath-test-dynamicpv-4l9j": Phase="Pending", Reason="", readiness=false. Elapsed: 6.127744508s
Jun 13 00:22:32.482: INFO: Pod "pod-subpath-test-dynamicpv-4l9j": Phase="Pending", Reason="", readiness=false. Elapsed: 8.160316284s
Jun 13 00:22:34.514: INFO: Pod "pod-subpath-test-dynamicpv-4l9j": Phase="Pending", Reason="", readiness=false. Elapsed: 10.192548952s
... skipping 13 lines ...
Jun 13 00:23:02.983: INFO: Pod "pod-subpath-test-dynamicpv-4l9j": Phase="Running", Reason="", readiness=true. Elapsed: 38.661409805s
Jun 13 00:23:05.015: INFO: Pod "pod-subpath-test-dynamicpv-4l9j": Phase="Running", Reason="", readiness=true. Elapsed: 40.693500263s
Jun 13 00:23:07.048: INFO: Pod "pod-subpath-test-dynamicpv-4l9j": Phase="Running", Reason="", readiness=true. Elapsed: 42.726273389s
Jun 13 00:23:09.082: INFO: Pod "pod-subpath-test-dynamicpv-4l9j": Phase="Running", Reason="", readiness=true. Elapsed: 44.760363969s
Jun 13 00:23:11.113: INFO: Pod "pod-subpath-test-dynamicpv-4l9j": Phase="Succeeded", Reason="", readiness=false. Elapsed: 46.791830237s
STEP: Saw pod success
Jun 13 00:23:11.113: INFO: Pod "pod-subpath-test-dynamicpv-4l9j" satisfied condition "Succeeded or Failed"
Jun 13 00:23:11.145: INFO: Trying to get logs from node ip-172-20-58-40.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-4l9j container test-container-subpath-dynamicpv-4l9j: <nil>
STEP: delete the pod
Jun 13 00:23:11.214: INFO: Waiting for pod pod-subpath-test-dynamicpv-4l9j to disappear
Jun 13 00:23:11.245: INFO: Pod pod-subpath-test-dynamicpv-4l9j no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-4l9j
Jun 13 00:23:11.245: INFO: Deleting pod "pod-subpath-test-dynamicpv-4l9j" in namespace "provisioning-1482"
... skipping 47 lines ...
Jun 13 00:22:24.288: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9699-e2e-sclt7sr
STEP: creating a claim
Jun 13 00:22:24.326: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-2n8j
STEP: Creating a pod to test subpath
Jun 13 00:22:24.443: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-2n8j" in namespace "provisioning-9699" to be "Succeeded or Failed"
Jun 13 00:22:24.472: INFO: Pod "pod-subpath-test-dynamicpv-2n8j": Phase="Pending", Reason="", readiness=false. Elapsed: 29.739384ms
Jun 13 00:22:26.503: INFO: Pod "pod-subpath-test-dynamicpv-2n8j": Phase="Pending", Reason="", readiness=false. Elapsed: 2.060537062s
Jun 13 00:22:28.534: INFO: Pod "pod-subpath-test-dynamicpv-2n8j": Phase="Pending", Reason="", readiness=false. Elapsed: 4.090901755s
Jun 13 00:22:30.564: INFO: Pod "pod-subpath-test-dynamicpv-2n8j": Phase="Pending", Reason="", readiness=false. Elapsed: 6.121661294s
Jun 13 00:22:32.597: INFO: Pod "pod-subpath-test-dynamicpv-2n8j": Phase="Pending", Reason="", readiness=false. Elapsed: 8.154728644s
Jun 13 00:22:34.629: INFO: Pod "pod-subpath-test-dynamicpv-2n8j": Phase="Pending", Reason="", readiness=false. Elapsed: 10.186106181s
... skipping 5 lines ...
Jun 13 00:22:46.814: INFO: Pod "pod-subpath-test-dynamicpv-2n8j": Phase="Pending", Reason="", readiness=false. Elapsed: 22.371686706s
Jun 13 00:22:48.852: INFO: Pod "pod-subpath-test-dynamicpv-2n8j": Phase="Pending", Reason="", readiness=false. Elapsed: 24.408878968s
Jun 13 00:22:50.882: INFO: Pod "pod-subpath-test-dynamicpv-2n8j": Phase="Pending", Reason="", readiness=false. Elapsed: 26.439800782s
Jun 13 00:22:52.920: INFO: Pod "pod-subpath-test-dynamicpv-2n8j": Phase="Pending", Reason="", readiness=false. Elapsed: 28.477416559s
Jun 13 00:22:54.951: INFO: Pod "pod-subpath-test-dynamicpv-2n8j": Phase="Succeeded", Reason="", readiness=false. Elapsed: 30.508487341s
STEP: Saw pod success
Jun 13 00:22:54.951: INFO: Pod "pod-subpath-test-dynamicpv-2n8j" satisfied condition "Succeeded or Failed"
Jun 13 00:22:54.981: INFO: Trying to get logs from node ip-172-20-56-187.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-2n8j container test-container-subpath-dynamicpv-2n8j: <nil>
STEP: delete the pod
Jun 13 00:22:55.365: INFO: Waiting for pod pod-subpath-test-dynamicpv-2n8j to disappear
Jun 13 00:22:55.394: INFO: Pod pod-subpath-test-dynamicpv-2n8j no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-2n8j
Jun 13 00:22:55.394: INFO: Deleting pod "pod-subpath-test-dynamicpv-2n8j" in namespace "provisioning-9699"
STEP: Creating pod pod-subpath-test-dynamicpv-2n8j
STEP: Creating a pod to test subpath
Jun 13 00:22:55.459: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-2n8j" in namespace "provisioning-9699" to be "Succeeded or Failed"
Jun 13 00:22:55.497: INFO: Pod "pod-subpath-test-dynamicpv-2n8j": Phase="Pending", Reason="", readiness=false. Elapsed: 37.620437ms
Jun 13 00:22:57.527: INFO: Pod "pod-subpath-test-dynamicpv-2n8j": Phase="Pending", Reason="", readiness=false. Elapsed: 2.067745762s
Jun 13 00:22:59.558: INFO: Pod "pod-subpath-test-dynamicpv-2n8j": Phase="Pending", Reason="", readiness=false. Elapsed: 4.09883942s
Jun 13 00:23:01.589: INFO: Pod "pod-subpath-test-dynamicpv-2n8j": Phase="Pending", Reason="", readiness=false. Elapsed: 6.129756603s
Jun 13 00:23:03.619: INFO: Pod "pod-subpath-test-dynamicpv-2n8j": Phase="Pending", Reason="", readiness=false. Elapsed: 8.159982839s
Jun 13 00:23:05.651: INFO: Pod "pod-subpath-test-dynamicpv-2n8j": Phase="Pending", Reason="", readiness=false. Elapsed: 10.191232577s
... skipping 23 lines ...
Jun 13 00:23:54.407: INFO: Pod "pod-subpath-test-dynamicpv-2n8j": Phase="Pending", Reason="", readiness=false. Elapsed: 58.947971156s
Jun 13 00:23:56.441: INFO: Pod "pod-subpath-test-dynamicpv-2n8j": Phase="Pending", Reason="", readiness=false. Elapsed: 1m0.981067313s
Jun 13 00:23:58.471: INFO: Pod "pod-subpath-test-dynamicpv-2n8j": Phase="Pending", Reason="", readiness=false. Elapsed: 1m3.011254077s
Jun 13 00:24:00.502: INFO: Pod "pod-subpath-test-dynamicpv-2n8j": Phase="Pending", Reason="", readiness=false. Elapsed: 1m5.042577435s
Jun 13 00:24:02.532: INFO: Pod "pod-subpath-test-dynamicpv-2n8j": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m7.072597914s
STEP: Saw pod success
Jun 13 00:24:02.532: INFO: Pod "pod-subpath-test-dynamicpv-2n8j" satisfied condition "Succeeded or Failed"
Jun 13 00:24:02.561: INFO: Trying to get logs from node ip-172-20-58-40.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-2n8j container test-container-subpath-dynamicpv-2n8j: <nil>
STEP: delete the pod
Jun 13 00:24:02.627: INFO: Waiting for pod pod-subpath-test-dynamicpv-2n8j to disappear
Jun 13 00:24:02.658: INFO: Pod pod-subpath-test-dynamicpv-2n8j no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-2n8j
Jun 13 00:24:02.658: INFO: Deleting pod "pod-subpath-test-dynamicpv-2n8j" in namespace "provisioning-9699"
... skipping 31 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail to use a volume in a pod with mismatched mode [Slow] [BeforeEach]
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296

    Driver "ebs.csi.aws.com" does not support volume type "PreprovisionedPV" - skipping

    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 177 lines ...
Jun 13 00:23:58.801: INFO: Creating resource for dynamic PV
Jun 13 00:23:58.801: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-1538-e2e-scqnz45
STEP: creating a claim
STEP: Expanding non-expandable pvc
Jun 13 00:23:58.893: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 13 00:23:58.958: INFO: Error updating pvc ebs.csi.aws.comk7z8j: PersistentVolumeClaim "ebs.csi.aws.comk7z8j" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1538-e2e-scqnz45",
  	... // 2 identical fields
  }

Jun 13 00:24:01.019: INFO: Error updating pvc ebs.csi.aws.comk7z8j: PersistentVolumeClaim "ebs.csi.aws.comk7z8j" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1538-e2e-scqnz45",
  	... // 2 identical fields
  }

Jun 13 00:24:03.023: INFO: Error updating pvc ebs.csi.aws.comk7z8j: PersistentVolumeClaim "ebs.csi.aws.comk7z8j" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1538-e2e-scqnz45",
  	... // 2 identical fields
  }

Jun 13 00:24:05.019: INFO: Error updating pvc ebs.csi.aws.comk7z8j: PersistentVolumeClaim "ebs.csi.aws.comk7z8j" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1538-e2e-scqnz45",
  	... // 2 identical fields
  }

Jun 13 00:24:07.018: INFO: Error updating pvc ebs.csi.aws.comk7z8j: PersistentVolumeClaim "ebs.csi.aws.comk7z8j" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1538-e2e-scqnz45",
  	... // 2 identical fields
  }

Jun 13 00:24:09.021: INFO: Error updating pvc ebs.csi.aws.comk7z8j: PersistentVolumeClaim "ebs.csi.aws.comk7z8j" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1538-e2e-scqnz45",
  	... // 2 identical fields
  }

Jun 13 00:24:11.018: INFO: Error updating pvc ebs.csi.aws.comk7z8j: PersistentVolumeClaim "ebs.csi.aws.comk7z8j" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1538-e2e-scqnz45",
  	... // 2 identical fields
  }

Jun 13 00:24:13.018: INFO: Error updating pvc ebs.csi.aws.comk7z8j: PersistentVolumeClaim "ebs.csi.aws.comk7z8j" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1538-e2e-scqnz45",
  	... // 2 identical fields
  }

Jun 13 00:24:15.017: INFO: Error updating pvc ebs.csi.aws.comk7z8j: PersistentVolumeClaim "ebs.csi.aws.comk7z8j" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1538-e2e-scqnz45",
  	... // 2 identical fields
  }

Jun 13 00:24:17.017: INFO: Error updating pvc ebs.csi.aws.comk7z8j: PersistentVolumeClaim "ebs.csi.aws.comk7z8j" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1538-e2e-scqnz45",
  	... // 2 identical fields
  }

Jun 13 00:24:19.019: INFO: Error updating pvc ebs.csi.aws.comk7z8j: PersistentVolumeClaim "ebs.csi.aws.comk7z8j" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1538-e2e-scqnz45",
  	... // 2 identical fields
  }

Jun 13 00:24:21.021: INFO: Error updating pvc ebs.csi.aws.comk7z8j: PersistentVolumeClaim "ebs.csi.aws.comk7z8j" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1538-e2e-scqnz45",
  	... // 2 identical fields
  }

Jun 13 00:24:23.021: INFO: Error updating pvc ebs.csi.aws.comk7z8j: PersistentVolumeClaim "ebs.csi.aws.comk7z8j" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1538-e2e-scqnz45",
  	... // 2 identical fields
  }

Jun 13 00:24:25.018: INFO: Error updating pvc ebs.csi.aws.comk7z8j: PersistentVolumeClaim "ebs.csi.aws.comk7z8j" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1538-e2e-scqnz45",
  	... // 2 identical fields
  }

Jun 13 00:24:27.019: INFO: Error updating pvc ebs.csi.aws.comk7z8j: PersistentVolumeClaim "ebs.csi.aws.comk7z8j" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1538-e2e-scqnz45",
  	... // 2 identical fields
  }

Jun 13 00:24:29.019: INFO: Error updating pvc ebs.csi.aws.comk7z8j: PersistentVolumeClaim "ebs.csi.aws.comk7z8j" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1538-e2e-scqnz45",
  	... // 2 identical fields
  }

Jun 13 00:24:29.083: INFO: Error updating pvc ebs.csi.aws.comk7z8j: PersistentVolumeClaim "ebs.csi.aws.comk7z8j" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 260 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.8OXTe6tDm/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.8OXTe6tDm/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if non-existent subpath is outside the volume [Slow][LinuxOnly] [BeforeEach]
      /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 32 lines ...
Jun 13 00:24:04.961: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9769-e2e-scnxz8j
STEP: creating a claim
Jun 13 00:24:04.991: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-vbtd
STEP: Creating a pod to test subpath
Jun 13 00:24:05.086: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-vbtd" in namespace "provisioning-9769" to be "Succeeded or Failed"
Jun 13 00:24:05.117: INFO: Pod "pod-subpath-test-dynamicpv-vbtd": Phase="Pending", Reason="", readiness=false. Elapsed: 30.445803ms
Jun 13 00:24:07.148: INFO: Pod "pod-subpath-test-dynamicpv-vbtd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061627864s
Jun 13 00:24:09.180: INFO: Pod "pod-subpath-test-dynamicpv-vbtd": Phase="Pending", Reason="", readiness=false. Elapsed: 4.093714268s
Jun 13 00:24:11.211: INFO: Pod "pod-subpath-test-dynamicpv-vbtd": Phase="Pending", Reason="", readiness=false. Elapsed: 6.125167577s
Jun 13 00:24:13.242: INFO: Pod "pod-subpath-test-dynamicpv-vbtd": Phase="Pending", Reason="", readiness=false. Elapsed: 8.156061798s
Jun 13 00:24:15.274: INFO: Pod "pod-subpath-test-dynamicpv-vbtd": Phase="Pending", Reason="", readiness=false. Elapsed: 10.187565327s
Jun 13 00:24:17.306: INFO: Pod "pod-subpath-test-dynamicpv-vbtd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.219284108s
STEP: Saw pod success
Jun 13 00:24:17.306: INFO: Pod "pod-subpath-test-dynamicpv-vbtd" satisfied condition "Succeeded or Failed"
Jun 13 00:24:17.336: INFO: Trying to get logs from node ip-172-20-58-40.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-vbtd container test-container-subpath-dynamicpv-vbtd: <nil>
STEP: delete the pod
Jun 13 00:24:17.404: INFO: Waiting for pod pod-subpath-test-dynamicpv-vbtd to disappear
Jun 13 00:24:17.434: INFO: Pod pod-subpath-test-dynamicpv-vbtd no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-vbtd
Jun 13 00:24:17.434: INFO: Deleting pod "pod-subpath-test-dynamicpv-vbtd" in namespace "provisioning-9769"
... skipping 224 lines ...
Jun 13 00:24:18.874: INFO: Pod aws-client still exists
Jun 13 00:24:20.844: INFO: Waiting for pod aws-client to disappear
Jun 13 00:24:20.875: INFO: Pod aws-client still exists
Jun 13 00:24:22.843: INFO: Waiting for pod aws-client to disappear
Jun 13 00:24:22.873: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun 13 00:24:22.972: INFO: Couldn't delete PD "aws://us-east-2a/vol-06e31661b97d6a3e2", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-06e31661b97d6a3e2 is currently attached to i-0574f3206292b3a18
	status code: 400, request id: 1b640c59-ddde-4f64-adbc-7461d6852f2d
Jun 13 00:24:28.232: INFO: Couldn't delete PD "aws://us-east-2a/vol-06e31661b97d6a3e2", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-06e31661b97d6a3e2 is currently attached to i-0574f3206292b3a18
	status code: 400, request id: 66fb18f2-c75a-46ec-b3c7-3b06054db29e
Jun 13 00:24:33.522: INFO: Couldn't delete PD "aws://us-east-2a/vol-06e31661b97d6a3e2", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-06e31661b97d6a3e2 is currently attached to i-0574f3206292b3a18
	status code: 400, request id: 3e7b9361-d9d5-42a3-af8b-fd2f879166c0
Jun 13 00:24:38.779: INFO: Successfully deleted PD "aws://us-east-2a/vol-06e31661b97d6a3e2".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 13 00:24:38.779: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-2560" for this suite.
... skipping 349 lines ...
Jun 13 00:24:09.913: INFO: PersistentVolumeClaim pvc-tkwrh found but phase is Pending instead of Bound.
Jun 13 00:24:11.944: INFO: PersistentVolumeClaim pvc-tkwrh found and phase=Bound (8.153805923s)
Jun 13 00:24:11.944: INFO: Waiting up to 3m0s for PersistentVolume aws-csscw to have phase Bound
Jun 13 00:24:11.975: INFO: PersistentVolume aws-csscw found and phase=Bound (30.781164ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-s4fl
STEP: Creating a pod to test exec-volume-test
Jun 13 00:24:12.066: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-s4fl" in namespace "volume-6157" to be "Succeeded or Failed"
Jun 13 00:24:12.099: INFO: Pod "exec-volume-test-preprovisionedpv-s4fl": Phase="Pending", Reason="", readiness=false. Elapsed: 33.51233ms
Jun 13 00:24:14.130: INFO: Pod "exec-volume-test-preprovisionedpv-s4fl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.064566804s
Jun 13 00:24:16.176: INFO: Pod "exec-volume-test-preprovisionedpv-s4fl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.109989898s
Jun 13 00:24:18.217: INFO: Pod "exec-volume-test-preprovisionedpv-s4fl": Phase="Pending", Reason="", readiness=false. Elapsed: 6.150619932s
Jun 13 00:24:20.248: INFO: Pod "exec-volume-test-preprovisionedpv-s4fl": Phase="Pending", Reason="", readiness=false. Elapsed: 8.182471398s
Jun 13 00:24:22.279: INFO: Pod "exec-volume-test-preprovisionedpv-s4fl": Phase="Pending", Reason="", readiness=false. Elapsed: 10.213406316s
Jun 13 00:24:24.310: INFO: Pod "exec-volume-test-preprovisionedpv-s4fl": Phase="Pending", Reason="", readiness=false. Elapsed: 12.244546521s
Jun 13 00:24:26.342: INFO: Pod "exec-volume-test-preprovisionedpv-s4fl": Phase="Pending", Reason="", readiness=false. Elapsed: 14.276228738s
Jun 13 00:24:28.375: INFO: Pod "exec-volume-test-preprovisionedpv-s4fl": Phase="Pending", Reason="", readiness=false. Elapsed: 16.309036655s
Jun 13 00:24:30.405: INFO: Pod "exec-volume-test-preprovisionedpv-s4fl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.339367052s
STEP: Saw pod success
Jun 13 00:24:30.405: INFO: Pod "exec-volume-test-preprovisionedpv-s4fl" satisfied condition "Succeeded or Failed"
Jun 13 00:24:30.435: INFO: Trying to get logs from node ip-172-20-58-40.us-east-2.compute.internal pod exec-volume-test-preprovisionedpv-s4fl container exec-container-preprovisionedpv-s4fl: <nil>
STEP: delete the pod
Jun 13 00:24:30.501: INFO: Waiting for pod exec-volume-test-preprovisionedpv-s4fl to disappear
Jun 13 00:24:30.531: INFO: Pod exec-volume-test-preprovisionedpv-s4fl no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-s4fl
Jun 13 00:24:30.531: INFO: Deleting pod "exec-volume-test-preprovisionedpv-s4fl" in namespace "volume-6157"
STEP: Deleting pv and pvc
Jun 13 00:24:30.561: INFO: Deleting PersistentVolumeClaim "pvc-tkwrh"
Jun 13 00:24:30.592: INFO: Deleting PersistentVolume "aws-csscw"
Jun 13 00:24:30.764: INFO: Couldn't delete PD "aws://us-east-2a/vol-0606b0362e3058d4c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0606b0362e3058d4c is currently attached to i-0574f3206292b3a18
	status code: 400, request id: 0c8dbe54-856f-4b80-a65e-ef51e35ddd5a
Jun 13 00:24:36.029: INFO: Couldn't delete PD "aws://us-east-2a/vol-0606b0362e3058d4c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0606b0362e3058d4c is currently attached to i-0574f3206292b3a18
	status code: 400, request id: d0444da2-0222-46b4-8dbb-84f30fce8d75
Jun 13 00:24:41.266: INFO: Couldn't delete PD "aws://us-east-2a/vol-0606b0362e3058d4c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0606b0362e3058d4c is currently attached to i-0574f3206292b3a18
	status code: 400, request id: f8cc0f24-d88f-4b90-8ba0-143d25d7716a
Jun 13 00:24:46.475: INFO: Couldn't delete PD "aws://us-east-2a/vol-0606b0362e3058d4c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0606b0362e3058d4c is currently attached to i-0574f3206292b3a18
	status code: 400, request id: 714bfde5-24ec-4cd7-8d34-16a6d7d46a1c
Jun 13 00:24:51.750: INFO: Successfully deleted PD "aws://us-east-2a/vol-0606b0362e3058d4c".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 13 00:24:51.750: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-6157" for this suite.
... skipping 106 lines ...
Jun 13 00:24:09.738: INFO: PersistentVolumeClaim pvc-qmlqm found but phase is Pending instead of Bound.
Jun 13 00:24:11.771: INFO: PersistentVolumeClaim pvc-qmlqm found and phase=Bound (4.097026889s)
Jun 13 00:24:11.771: INFO: Waiting up to 3m0s for PersistentVolume aws-wkpnt to have phase Bound
Jun 13 00:24:11.802: INFO: PersistentVolume aws-wkpnt found and phase=Bound (30.018335ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-7gwp
STEP: Creating a pod to test exec-volume-test
Jun 13 00:24:11.896: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-7gwp" in namespace "volume-2421" to be "Succeeded or Failed"
Jun 13 00:24:11.926: INFO: Pod "exec-volume-test-preprovisionedpv-7gwp": Phase="Pending", Reason="", readiness=false. Elapsed: 30.339866ms
Jun 13 00:24:13.958: INFO: Pod "exec-volume-test-preprovisionedpv-7gwp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062373772s
Jun 13 00:24:15.994: INFO: Pod "exec-volume-test-preprovisionedpv-7gwp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.09882691s
Jun 13 00:24:18.026: INFO: Pod "exec-volume-test-preprovisionedpv-7gwp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.130381835s
Jun 13 00:24:20.059: INFO: Pod "exec-volume-test-preprovisionedpv-7gwp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.163213231s
Jun 13 00:24:22.091: INFO: Pod "exec-volume-test-preprovisionedpv-7gwp": Phase="Pending", Reason="", readiness=false. Elapsed: 10.195168278s
Jun 13 00:24:24.122: INFO: Pod "exec-volume-test-preprovisionedpv-7gwp": Phase="Pending", Reason="", readiness=false. Elapsed: 12.226880808s
Jun 13 00:24:26.154: INFO: Pod "exec-volume-test-preprovisionedpv-7gwp": Phase="Pending", Reason="", readiness=false. Elapsed: 14.257969427s
Jun 13 00:24:28.184: INFO: Pod "exec-volume-test-preprovisionedpv-7gwp": Phase="Pending", Reason="", readiness=false. Elapsed: 16.288801782s
Jun 13 00:24:30.216: INFO: Pod "exec-volume-test-preprovisionedpv-7gwp": Phase="Pending", Reason="", readiness=false. Elapsed: 18.320697479s
Jun 13 00:24:32.249: INFO: Pod "exec-volume-test-preprovisionedpv-7gwp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.353433393s
STEP: Saw pod success
Jun 13 00:24:32.249: INFO: Pod "exec-volume-test-preprovisionedpv-7gwp" satisfied condition "Succeeded or Failed"
Jun 13 00:24:32.279: INFO: Trying to get logs from node ip-172-20-56-187.us-east-2.compute.internal pod exec-volume-test-preprovisionedpv-7gwp container exec-container-preprovisionedpv-7gwp: <nil>
STEP: delete the pod
Jun 13 00:24:32.349: INFO: Waiting for pod exec-volume-test-preprovisionedpv-7gwp to disappear
Jun 13 00:24:32.379: INFO: Pod exec-volume-test-preprovisionedpv-7gwp no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-7gwp
Jun 13 00:24:32.379: INFO: Deleting pod "exec-volume-test-preprovisionedpv-7gwp" in namespace "volume-2421"
STEP: Deleting pv and pvc
Jun 13 00:24:32.410: INFO: Deleting PersistentVolumeClaim "pvc-qmlqm"
Jun 13 00:24:32.443: INFO: Deleting PersistentVolume "aws-wkpnt"
Jun 13 00:24:32.604: INFO: Couldn't delete PD "aws://us-east-2a/vol-0934d812c86d544ad", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0934d812c86d544ad is currently attached to i-087a70388fa5a089c
	status code: 400, request id: 63cd8d49-ff6d-459c-8bcf-0e95d3b7ea65
Jun 13 00:24:37.903: INFO: Couldn't delete PD "aws://us-east-2a/vol-0934d812c86d544ad", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0934d812c86d544ad is currently attached to i-087a70388fa5a089c
	status code: 400, request id: 64aed021-b105-4585-a733-31f4d0df1b32
Jun 13 00:24:43.099: INFO: Couldn't delete PD "aws://us-east-2a/vol-0934d812c86d544ad", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0934d812c86d544ad is currently attached to i-087a70388fa5a089c
	status code: 400, request id: c9546d2e-211f-48f1-a75a-24d49892bacd
Jun 13 00:24:48.334: INFO: Couldn't delete PD "aws://us-east-2a/vol-0934d812c86d544ad", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0934d812c86d544ad is currently attached to i-087a70388fa5a089c
	status code: 400, request id: c12df7d8-9943-4bf6-8684-27a1cb5b8fcd
Jun 13 00:24:53.599: INFO: Successfully deleted PD "aws://us-east-2a/vol-0934d812c86d544ad".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 13 00:24:53.599: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-2421" for this suite.
... skipping 163 lines ...
Jun 13 00:24:16.388: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-3417rm778
STEP: creating a claim
Jun 13 00:24:16.419: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-wd68
STEP: Creating a pod to test exec-volume-test
Jun 13 00:24:16.515: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-wd68" in namespace "volume-3417" to be "Succeeded or Failed"
Jun 13 00:24:16.545: INFO: Pod "exec-volume-test-dynamicpv-wd68": Phase="Pending", Reason="", readiness=false. Elapsed: 30.079584ms
Jun 13 00:24:18.577: INFO: Pod "exec-volume-test-dynamicpv-wd68": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062300903s
Jun 13 00:24:20.609: INFO: Pod "exec-volume-test-dynamicpv-wd68": Phase="Pending", Reason="", readiness=false. Elapsed: 4.093901235s
Jun 13 00:24:22.640: INFO: Pod "exec-volume-test-dynamicpv-wd68": Phase="Pending", Reason="", readiness=false. Elapsed: 6.125178949s
Jun 13 00:24:24.675: INFO: Pod "exec-volume-test-dynamicpv-wd68": Phase="Running", Reason="", readiness=true. Elapsed: 8.160207195s
Jun 13 00:24:26.707: INFO: Pod "exec-volume-test-dynamicpv-wd68": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.191735125s
STEP: Saw pod success
Jun 13 00:24:26.707: INFO: Pod "exec-volume-test-dynamicpv-wd68" satisfied condition "Succeeded or Failed"
Jun 13 00:24:26.737: INFO: Trying to get logs from node ip-172-20-58-40.us-east-2.compute.internal pod exec-volume-test-dynamicpv-wd68 container exec-container-dynamicpv-wd68: <nil>
STEP: delete the pod
Jun 13 00:24:26.804: INFO: Waiting for pod exec-volume-test-dynamicpv-wd68 to disappear
Jun 13 00:24:26.834: INFO: Pod exec-volume-test-dynamicpv-wd68 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-wd68
Jun 13 00:24:26.834: INFO: Deleting pod "exec-volume-test-dynamicpv-wd68" in namespace "volume-3417"
... skipping 34 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly] [BeforeEach]
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

    Driver "ebs.csi.aws.com" does not support volume type "PreprovisionedPV" - skipping

    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 6 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath file is outside the volume [Slow][LinuxOnly] [BeforeEach]
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

    Driver "ebs.csi.aws.com" does not support volume type "InlineVolume" - skipping

    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 157 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.8OXTe6tDm/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]
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

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

    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:92
------------------------------
... skipping 259 lines ...
STEP: Deleting pod hostexec-ip-172-20-44-97.us-east-2.compute.internal-zglxh in namespace volumemode-9313
Jun 13 00:24:47.487: INFO: Deleting pod "pod-72d4861e-4823-447e-8bf7-0ada5d1d8f78" in namespace "volumemode-9313"
Jun 13 00:24:47.518: INFO: Wait up to 5m0s for pod "pod-72d4861e-4823-447e-8bf7-0ada5d1d8f78" to be fully deleted
STEP: Deleting pv and pvc
Jun 13 00:25:03.578: INFO: Deleting PersistentVolumeClaim "pvc-skmkm"
Jun 13 00:25:03.608: INFO: Deleting PersistentVolume "aws-chtzb"
Jun 13 00:25:03.805: INFO: Couldn't delete PD "aws://us-east-2a/vol-0e29673014db5b988", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e29673014db5b988 is currently attached to i-008e8334048ae093c
	status code: 400, request id: 8ebafd10-7385-4fb5-9bb8-0fc5fb05d254
Jun 13 00:25:09.072: INFO: Couldn't delete PD "aws://us-east-2a/vol-0e29673014db5b988", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e29673014db5b988 is currently attached to i-008e8334048ae093c
	status code: 400, request id: b4024a59-b585-4f84-a764-bddf532262b6
Jun 13 00:25:14.320: INFO: Successfully deleted PD "aws://us-east-2a/vol-0e29673014db5b988".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 13 00:25:14.320: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-9313" for this suite.
... skipping 96 lines ...
Jun 13 00:24:43.806: INFO: Waiting for pod aws-client to disappear
Jun 13 00:24:43.836: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 13 00:24:43.836: INFO: Deleting PersistentVolumeClaim "pvc-4nnk8"
Jun 13 00:24:43.883: INFO: Deleting PersistentVolume "aws-2t4kd"
Jun 13 00:24:44.170: INFO: Couldn't delete PD "aws://us-east-2a/vol-02e6d23687b97da61", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02e6d23687b97da61 is currently attached to i-014c8052d1f18bb5f
	status code: 400, request id: 6c0b535a-d1b8-42bc-b02d-1f6eebb8ee18
Jun 13 00:24:49.397: INFO: Couldn't delete PD "aws://us-east-2a/vol-02e6d23687b97da61", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02e6d23687b97da61 is currently attached to i-014c8052d1f18bb5f
	status code: 400, request id: 1c216f19-c90e-4b5d-8df0-c8ce94208034
Jun 13 00:24:54.693: INFO: Couldn't delete PD "aws://us-east-2a/vol-02e6d23687b97da61", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02e6d23687b97da61 is currently attached to i-014c8052d1f18bb5f
	status code: 400, request id: 8e633c41-bdbc-458f-a5ec-968f88339f32
Jun 13 00:24:59.929: INFO: Couldn't delete PD "aws://us-east-2a/vol-02e6d23687b97da61", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02e6d23687b97da61 is currently attached to i-014c8052d1f18bb5f
	status code: 400, request id: ae530546-a13f-43e0-93df-23a650757332
Jun 13 00:25:05.183: INFO: Couldn't delete PD "aws://us-east-2a/vol-02e6d23687b97da61", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02e6d23687b97da61 is currently attached to i-014c8052d1f18bb5f
	status code: 400, request id: 87415e15-31cd-407b-a017-12cc36c1ff78
Jun 13 00:25:10.398: INFO: Couldn't delete PD "aws://us-east-2a/vol-02e6d23687b97da61", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02e6d23687b97da61 is currently attached to i-014c8052d1f18bb5f
	status code: 400, request id: 57923e3d-066a-496f-8eb6-9d9e2bf739fd
Jun 13 00:25:15.678: INFO: Successfully deleted PD "aws://us-east-2a/vol-02e6d23687b97da61".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 13 00:25:15.678: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-5048" for this suite.
... skipping 66 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail to use a volume in a pod with mismatched mode [Slow] [BeforeEach]
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296

    Driver "ebs.csi.aws.com" does not support volume type "PreprovisionedPV" - skipping

    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 48 lines ...
Jun 13 00:24:24.224: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 13 00:24:24.727: INFO: Successfully created a new PD: "aws://us-east-2a/vol-07e5f1037a636daa0".
Jun 13 00:24:24.727: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-wqh7
STEP: Creating a pod to test exec-volume-test
Jun 13 00:24:24.760: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-wqh7" in namespace "volume-250" to be "Succeeded or Failed"
Jun 13 00:24:24.789: INFO: Pod "exec-volume-test-inlinevolume-wqh7": Phase="Pending", Reason="", readiness=false. Elapsed: 29.013034ms
Jun 13 00:24:26.820: INFO: Pod "exec-volume-test-inlinevolume-wqh7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.059860756s
Jun 13 00:24:28.851: INFO: Pod "exec-volume-test-inlinevolume-wqh7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.090491381s
Jun 13 00:24:30.881: INFO: Pod "exec-volume-test-inlinevolume-wqh7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.12080494s
Jun 13 00:24:32.911: INFO: Pod "exec-volume-test-inlinevolume-wqh7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.150592773s
Jun 13 00:24:34.940: INFO: Pod "exec-volume-test-inlinevolume-wqh7": Phase="Pending", Reason="", readiness=false. Elapsed: 10.180089519s
Jun 13 00:24:36.970: INFO: Pod "exec-volume-test-inlinevolume-wqh7": Phase="Pending", Reason="", readiness=false. Elapsed: 12.210113646s
Jun 13 00:24:39.000: INFO: Pod "exec-volume-test-inlinevolume-wqh7": Phase="Pending", Reason="", readiness=false. Elapsed: 14.240157646s
Jun 13 00:24:41.030: INFO: Pod "exec-volume-test-inlinevolume-wqh7": Phase="Pending", Reason="", readiness=false. Elapsed: 16.269813239s
Jun 13 00:24:43.060: INFO: Pod "exec-volume-test-inlinevolume-wqh7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.299372343s
STEP: Saw pod success
Jun 13 00:24:43.060: INFO: Pod "exec-volume-test-inlinevolume-wqh7" satisfied condition "Succeeded or Failed"
Jun 13 00:24:43.097: INFO: Trying to get logs from node ip-172-20-44-97.us-east-2.compute.internal pod exec-volume-test-inlinevolume-wqh7 container exec-container-inlinevolume-wqh7: <nil>
STEP: delete the pod
Jun 13 00:24:43.175: INFO: Waiting for pod exec-volume-test-inlinevolume-wqh7 to disappear
Jun 13 00:24:43.204: INFO: Pod exec-volume-test-inlinevolume-wqh7 no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-wqh7
Jun 13 00:24:43.204: INFO: Deleting pod "exec-volume-test-inlinevolume-wqh7" in namespace "volume-250"
Jun 13 00:24:43.352: INFO: Couldn't delete PD "aws://us-east-2a/vol-07e5f1037a636daa0", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07e5f1037a636daa0 is currently attached to i-008e8334048ae093c
	status code: 400, request id: 2fd1f448-aedb-4039-bd7f-74c084bd0979
Jun 13 00:24:48.591: INFO: Couldn't delete PD "aws://us-east-2a/vol-07e5f1037a636daa0", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07e5f1037a636daa0 is currently attached to i-008e8334048ae093c
	status code: 400, request id: 308eb8ec-9091-4356-8394-8694f997d5b8
Jun 13 00:24:53.865: INFO: Couldn't delete PD "aws://us-east-2a/vol-07e5f1037a636daa0", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07e5f1037a636daa0 is currently attached to i-008e8334048ae093c
	status code: 400, request id: 367b1f48-3bd4-499a-97a6-f06cf8163981
Jun 13 00:24:59.108: INFO: Couldn't delete PD "aws://us-east-2a/vol-07e5f1037a636daa0", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07e5f1037a636daa0 is currently attached to i-008e8334048ae093c
	status code: 400, request id: 6dc74b91-6df4-4d62-bb6a-863de8d74bbe
Jun 13 00:25:04.366: INFO: Couldn't delete PD "aws://us-east-2a/vol-07e5f1037a636daa0", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07e5f1037a636daa0 is currently attached to i-008e8334048ae093c
	status code: 400, request id: 28d86319-5c20-45b7-8f03-cb7fed9cbafc
Jun 13 00:25:09.606: INFO: Couldn't delete PD "aws://us-east-2a/vol-07e5f1037a636daa0", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07e5f1037a636daa0 is currently attached to i-008e8334048ae093c
	status code: 400, request id: 5dceba79-554f-4ac1-baab-ae6843b21629
Jun 13 00:25:14.822: INFO: Couldn't delete PD "aws://us-east-2a/vol-07e5f1037a636daa0", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07e5f1037a636daa0 is currently attached to i-008e8334048ae093c
	status code: 400, request id: a029ff1a-9072-44ba-a077-a5685737ab2d
Jun 13 00:25:20.097: INFO: Successfully deleted PD "aws://us-east-2a/vol-07e5f1037a636daa0".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 13 00:25:20.097: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-250" for this suite.
... skipping 20 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.8OXTe6tDm/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.8OXTe6tDm/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly] [BeforeEach]
      /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 11 lines ...
Jun 13 00:24:53.822: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-2038-e2e-scwwrtw
STEP: creating a claim
Jun 13 00:24:53.854: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Jun 13 00:24:53.916: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 13 00:24:53.977: INFO: Error updating pvc ebs.csi.aws.comwlh2c: PersistentVolumeClaim "ebs.csi.aws.comwlh2c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2038-e2e-scwwrtw",
  	... // 2 identical fields
  }

Jun 13 00:24:56.039: INFO: Error updating pvc ebs.csi.aws.comwlh2c: PersistentVolumeClaim "ebs.csi.aws.comwlh2c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2038-e2e-scwwrtw",
  	... // 2 identical fields
  }

Jun 13 00:24:58.039: INFO: Error updating pvc ebs.csi.aws.comwlh2c: PersistentVolumeClaim "ebs.csi.aws.comwlh2c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2038-e2e-scwwrtw",
  	... // 2 identical fields
  }

Jun 13 00:25:00.039: INFO: Error updating pvc ebs.csi.aws.comwlh2c: PersistentVolumeClaim "ebs.csi.aws.comwlh2c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2038-e2e-scwwrtw",
  	... // 2 identical fields
  }

Jun 13 00:25:02.044: INFO: Error updating pvc ebs.csi.aws.comwlh2c: PersistentVolumeClaim "ebs.csi.aws.comwlh2c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2038-e2e-scwwrtw",
  	... // 2 identical fields
  }

Jun 13 00:25:04.040: INFO: Error updating pvc ebs.csi.aws.comwlh2c: PersistentVolumeClaim "ebs.csi.aws.comwlh2c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2038-e2e-scwwrtw",
  	... // 2 identical fields
  }

Jun 13 00:25:06.039: INFO: Error updating pvc ebs.csi.aws.comwlh2c: PersistentVolumeClaim "ebs.csi.aws.comwlh2c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2038-e2e-scwwrtw",
  	... // 2 identical fields
  }

Jun 13 00:25:08.038: INFO: Error updating pvc ebs.csi.aws.comwlh2c: PersistentVolumeClaim "ebs.csi.aws.comwlh2c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2038-e2e-scwwrtw",
  	... // 2 identical fields
  }

Jun 13 00:25:10.040: INFO: Error updating pvc ebs.csi.aws.comwlh2c: PersistentVolumeClaim "ebs.csi.aws.comwlh2c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2038-e2e-scwwrtw",
  	... // 2 identical fields
  }

Jun 13 00:25:12.039: INFO: Error updating pvc ebs.csi.aws.comwlh2c: PersistentVolumeClaim "ebs.csi.aws.comwlh2c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2038-e2e-scwwrtw",
  	... // 2 identical fields
  }

Jun 13 00:25:14.040: INFO: Error updating pvc ebs.csi.aws.comwlh2c: PersistentVolumeClaim "ebs.csi.aws.comwlh2c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2038-e2e-scwwrtw",
  	... // 2 identical fields
  }

Jun 13 00:25:16.040: INFO: Error updating pvc ebs.csi.aws.comwlh2c: PersistentVolumeClaim "ebs.csi.aws.comwlh2c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2038-e2e-scwwrtw",
  	... // 2 identical fields
  }

Jun 13 00:25:18.038: INFO: Error updating pvc ebs.csi.aws.comwlh2c: PersistentVolumeClaim "ebs.csi.aws.comwlh2c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2038-e2e-scwwrtw",
  	... // 2 identical fields
  }

Jun 13 00:25:20.047: INFO: Error updating pvc ebs.csi.aws.comwlh2c: PersistentVolumeClaim "ebs.csi.aws.comwlh2c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2038-e2e-scwwrtw",
  	... // 2 identical fields
  }

Jun 13 00:25:22.040: INFO: Error updating pvc ebs.csi.aws.comwlh2c: PersistentVolumeClaim "ebs.csi.aws.comwlh2c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2038-e2e-scwwrtw",
  	... // 2 identical fields
  }

Jun 13 00:25:24.040: INFO: Error updating pvc ebs.csi.aws.comwlh2c: PersistentVolumeClaim "ebs.csi.aws.comwlh2c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2038-e2e-scwwrtw",
  	... // 2 identical fields
  }

Jun 13 00:25:24.102: INFO: Error updating pvc ebs.csi.aws.comwlh2c: PersistentVolumeClaim "ebs.csi.aws.comwlh2c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 120 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly] [BeforeEach]
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

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

    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 191 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 13 00:25:02.534: INFO: >>> kubeConfig: /root/.kube/config
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]
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun 13 00:25:02.684: INFO: Creating resource for dynamic PV
Jun 13 00:25:02.684: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6258-e2e-scx7wnn
STEP: creating a claim
Jun 13 00:25:02.715: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-9g7d
STEP: Checking for subpath error in container status
Jun 13 00:25:18.868: INFO: Deleting pod "pod-subpath-test-dynamicpv-9g7d" in namespace "provisioning-6258"
Jun 13 00:25:18.898: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-9g7d" to be fully deleted
STEP: Deleting pod
Jun 13 00:25:28.958: INFO: Deleting pod "pod-subpath-test-dynamicpv-9g7d" in namespace "provisioning-6258"
STEP: Deleting pvc
Jun 13 00:25:29.050: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com5dfxm"
... skipping 12 lines ...

• [SLOW TEST:46.793 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath directory is outside the volume [Slow][LinuxOnly]
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 18 lines ...
Jun 13 00:25:24.692: INFO: PersistentVolumeClaim pvc-q5tgw found but phase is Pending instead of Bound.
Jun 13 00:25:26.723: INFO: PersistentVolumeClaim pvc-q5tgw found and phase=Bound (10.188540075s)
Jun 13 00:25:26.723: INFO: Waiting up to 3m0s for PersistentVolume aws-mwlzk to have phase Bound
Jun 13 00:25:26.754: INFO: PersistentVolume aws-mwlzk found and phase=Bound (30.344331ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-fgkb
STEP: Creating a pod to test exec-volume-test
Jun 13 00:25:26.845: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-fgkb" in namespace "volume-443" to be "Succeeded or Failed"
Jun 13 00:25:26.876: INFO: Pod "exec-volume-test-preprovisionedpv-fgkb": Phase="Pending", Reason="", readiness=false. Elapsed: 30.394523ms
Jun 13 00:25:28.907: INFO: Pod "exec-volume-test-preprovisionedpv-fgkb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061355089s
Jun 13 00:25:30.938: INFO: Pod "exec-volume-test-preprovisionedpv-fgkb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.092606923s
Jun 13 00:25:32.970: INFO: Pod "exec-volume-test-preprovisionedpv-fgkb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.124847494s
Jun 13 00:25:35.001: INFO: Pod "exec-volume-test-preprovisionedpv-fgkb": Phase="Pending", Reason="", readiness=false. Elapsed: 8.155805471s
Jun 13 00:25:37.032: INFO: Pod "exec-volume-test-preprovisionedpv-fgkb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.186641915s
STEP: Saw pod success
Jun 13 00:25:37.032: INFO: Pod "exec-volume-test-preprovisionedpv-fgkb" satisfied condition "Succeeded or Failed"
Jun 13 00:25:37.063: INFO: Trying to get logs from node ip-172-20-56-187.us-east-2.compute.internal pod exec-volume-test-preprovisionedpv-fgkb container exec-container-preprovisionedpv-fgkb: <nil>
STEP: delete the pod
Jun 13 00:25:37.132: INFO: Waiting for pod exec-volume-test-preprovisionedpv-fgkb to disappear
Jun 13 00:25:37.162: INFO: Pod exec-volume-test-preprovisionedpv-fgkb no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-fgkb
Jun 13 00:25:37.162: INFO: Deleting pod "exec-volume-test-preprovisionedpv-fgkb" in namespace "volume-443"
STEP: Deleting pv and pvc
Jun 13 00:25:37.193: INFO: Deleting PersistentVolumeClaim "pvc-q5tgw"
Jun 13 00:25:37.223: INFO: Deleting PersistentVolume "aws-mwlzk"
Jun 13 00:25:37.408: INFO: Couldn't delete PD "aws://us-east-2a/vol-007e8df685de31311", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-007e8df685de31311 is currently attached to i-087a70388fa5a089c
	status code: 400, request id: 4469f0d9-c68f-4183-b458-794d9b132222
Jun 13 00:25:42.775: INFO: Couldn't delete PD "aws://us-east-2a/vol-007e8df685de31311", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-007e8df685de31311 is currently attached to i-087a70388fa5a089c
	status code: 400, request id: 13b10860-e57b-4b02-acf0-02c4876b9e1d
Jun 13 00:25:48.059: INFO: Couldn't delete PD "aws://us-east-2a/vol-007e8df685de31311", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-007e8df685de31311 is currently attached to i-087a70388fa5a089c
	status code: 400, request id: c31dc882-c802-46e2-b8db-7768ccd208dd
Jun 13 00:25:53.321: INFO: Successfully deleted PD "aws://us-east-2a/vol-007e8df685de31311".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 13 00:25:53.321: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-443" for this suite.
... skipping 551 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly] [BeforeEach]
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

    Driver "ebs.csi.aws.com" does not support volume type "InlineVolume" - skipping

    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 129 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 13 00:24:51.080: INFO: >>> kubeConfig: /root/.kube/config
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 with backstepping is outside the volume [Slow][LinuxOnly]
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun 13 00:24:51.232: INFO: Creating resource for dynamic PV
Jun 13 00:24:51.232: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8687-e2e-sc5j92f
STEP: creating a claim
Jun 13 00:24:51.262: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-bkm5
STEP: Checking for subpath error in container status
Jun 13 00:25:31.421: INFO: Deleting pod "pod-subpath-test-dynamicpv-bkm5" in namespace "provisioning-8687"
Jun 13 00:25:31.456: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-bkm5" to be fully deleted
STEP: Deleting pod
Jun 13 00:25:43.523: INFO: Deleting pod "pod-subpath-test-dynamicpv-bkm5" in namespace "provisioning-8687"
STEP: Deleting pvc
Jun 13 00:25:43.614: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comcqnmr"
... skipping 12 lines ...

• [SLOW TEST:72.813 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly]
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [sig-storage] Zone Support [Feature:vsphere]
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 13 00:26:03.895: INFO: >>> kubeConfig: /root/.kube/config
... skipping 136 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if non-existent subpath is outside the volume [Slow][LinuxOnly] [BeforeEach]
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

    Driver "ebs.csi.aws.com" does not support volume type "InlineVolume" - skipping

    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 90 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 13 00:25:48.378: INFO: >>> kubeConfig: /root/.kube/config
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]
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 13 00:25:48.524: INFO: Creating resource for dynamic PV
Jun 13 00:25:48.524: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-6905-e2e-sckfsb8
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 13 00:25:54.734: INFO: Deleting pod "pod-97aea3ea-3e25-4a3a-8a0a-4f6a0ebbe6e9" in namespace "volumemode-6905"
Jun 13 00:25:54.764: INFO: Wait up to 5m0s for pod "pod-97aea3ea-3e25-4a3a-8a0a-4f6a0ebbe6e9" to be fully deleted
STEP: Deleting pvc
Jun 13 00:26:04.884: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comjp5cc"
Jun 13 00:26:04.914: INFO: Waiting up to 5m0s for PersistentVolume pvc-58980f4d-7e62-4244-8557-7e850b88a096 to get deleted
Jun 13 00:26:04.943: INFO: PersistentVolume pvc-58980f4d-7e62-4244-8557-7e850b88a096 found and phase=Released (28.995597ms)
... skipping 7 lines ...

• [SLOW TEST:21.689 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail to use a volume in a pod with mismatched mode [Slow]
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 13 00:26:10.069: INFO: Driver "ebs.csi.aws.com" does not support topology - skipping
[AfterEach] [Testpattern: Dynamic PV (delayed binding)] topology
... skipping 449 lines ...
Jun 13 00:26:03.716: INFO: Waiting for pod aws-client to disappear
Jun 13 00:26:03.746: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 13 00:26:03.746: INFO: Deleting PersistentVolumeClaim "pvc-5td6j"
Jun 13 00:26:03.776: INFO: Deleting PersistentVolume "aws-pbfb7"
Jun 13 00:26:04.123: INFO: Couldn't delete PD "aws://us-east-2a/vol-0d4d474d9ec99900a", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d4d474d9ec99900a is currently attached to i-008e8334048ae093c
	status code: 400, request id: 44d73eed-100a-4f76-a992-ca16350a7b2f
Jun 13 00:26:09.452: INFO: Couldn't delete PD "aws://us-east-2a/vol-0d4d474d9ec99900a", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d4d474d9ec99900a is currently attached to i-008e8334048ae093c
	status code: 400, request id: b79170a0-d14b-4276-b59c-33c24a711953
Jun 13 00:26:14.725: INFO: Couldn't delete PD "aws://us-east-2a/vol-0d4d474d9ec99900a", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d4d474d9ec99900a is currently attached to i-008e8334048ae093c
	status code: 400, request id: ad3d6069-d9cf-469d-bce8-c5fd8faf4fb4
Jun 13 00:26:20.101: INFO: Successfully deleted PD "aws://us-east-2a/vol-0d4d474d9ec99900a".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumes
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 13 00:26:20.101: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-1729" for this suite.
... skipping 134 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 13 00:25:54.812: INFO: >>> kubeConfig: /root/.kube/config
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]
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun 13 00:25:54.968: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 13 00:25:54.968: INFO: Creating resource for dynamic PV
Jun 13 00:25:54.968: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2649dp5z6
STEP: creating a claim
Jun 13 00:25:55.000: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-vxsp
STEP: Checking for subpath error in container status
Jun 13 00:26:11.169: INFO: Deleting pod "pod-subpath-test-dynamicpv-vxsp" in namespace "provisioning-2649"
Jun 13 00:26:11.201: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-vxsp" to be fully deleted
STEP: Deleting pod
Jun 13 00:26:23.270: INFO: Deleting pod "pod-subpath-test-dynamicpv-vxsp" in namespace "provisioning-2649"
STEP: Deleting pvc
Jun 13 00:26:23.364: INFO: Deleting PersistentVolumeClaim "awsnpmw4"
... skipping 11 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.8OXTe6tDm/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.8OXTe6tDm/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath directory is outside the volume [Slow][LinuxOnly]
      /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 850 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 13 00:26:20.172: INFO: >>> kubeConfig: /root/.kube/config
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 file is outside the volume [Slow][LinuxOnly]
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun 13 00:26:20.323: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 13 00:26:20.324: INFO: Creating resource for dynamic PV
Jun 13 00:26:20.324: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-795897hbh
STEP: creating a claim
Jun 13 00:26:20.354: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-kl5s
STEP: Checking for subpath error in container status
Jun 13 00:26:44.514: INFO: Deleting pod "pod-subpath-test-dynamicpv-kl5s" in namespace "provisioning-7958"
Jun 13 00:26:44.556: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-kl5s" to be fully deleted
STEP: Deleting pod
Jun 13 00:26:54.616: INFO: Deleting pod "pod-subpath-test-dynamicpv-kl5s" in namespace "provisioning-7958"
STEP: Deleting pvc
Jun 13 00:26:54.707: INFO: Deleting PersistentVolumeClaim "awsdkfwd"
... skipping 14 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.8OXTe6tDm/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.8OXTe6tDm/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath file is outside the volume [Slow][LinuxOnly]
      /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Inline-volume (ext3)] volumes
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 13 00:27:15.001: INFO: Driver aws doesn't support ext3 -- skipping
[AfterEach] [Testpattern: Inline-volume (ext3)] volumes
... skipping 551 lines ...
Jun 13 00:27:19.021: INFO: Pod aws-client still exists
Jun 13 00:27:20.990: INFO: Waiting for pod aws-client to disappear
Jun 13 00:27:21.027: INFO: Pod aws-client still exists
Jun 13 00:27:22.990: INFO: Waiting for pod aws-client to disappear
Jun 13 00:27:23.020: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun 13 00:27:23.267: INFO: Couldn't delete PD "aws://us-east-2a/vol-013efce42902c7bdb", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-013efce42902c7bdb is currently attached to i-0574f3206292b3a18
	status code: 400, request id: 49ba07d7-32de-42c5-ba1f-16fab8802018
Jun 13 00:27:28.520: INFO: Successfully deleted PD "aws://us-east-2a/vol-013efce42902c7bdb".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 13 00:27:28.520: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-9791" for this suite.
... skipping 467 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.8OXTe6tDm/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.8OXTe6tDm/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath file is outside the volume [Slow][LinuxOnly] [BeforeEach]
      /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 744 lines ...
Jun 13 00:27:43.382: INFO: AfterEach: Cleaning up test resources


S [SKIPPING] in Spec Setup (BeforeEach) [0.226 seconds]
[sig-storage] PersistentVolumes:vsphere [Feature:vsphere]
/tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/utils/framework.go:23
  should test that deleting the PV before the pod does not cause pod deletion to fail on vsphere volume detach [BeforeEach]
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:164

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 60 lines ...
Jun 13 00:27:14.101: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-34187wjcr
STEP: creating a claim
Jun 13 00:27:14.132: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-vhmm
STEP: Creating a pod to test exec-volume-test
Jun 13 00:27:14.224: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-vhmm" in namespace "volume-3418" to be "Succeeded or Failed"
Jun 13 00:27:14.253: INFO: Pod "exec-volume-test-dynamicpv-vhmm": Phase="Pending", Reason="", readiness=false. Elapsed: 29.187884ms
Jun 13 00:27:16.283: INFO: Pod "exec-volume-test-dynamicpv-vhmm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.059098109s
Jun 13 00:27:18.321: INFO: Pod "exec-volume-test-dynamicpv-vhmm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.096601296s
Jun 13 00:27:20.353: INFO: Pod "exec-volume-test-dynamicpv-vhmm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.129364834s
Jun 13 00:27:22.383: INFO: Pod "exec-volume-test-dynamicpv-vhmm": Phase="Pending", Reason="", readiness=false. Elapsed: 8.159446602s
Jun 13 00:27:24.414: INFO: Pod "exec-volume-test-dynamicpv-vhmm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.18953334s
STEP: Saw pod success
Jun 13 00:27:24.414: INFO: Pod "exec-volume-test-dynamicpv-vhmm" satisfied condition "Succeeded or Failed"
Jun 13 00:27:24.443: INFO: Trying to get logs from node ip-172-20-58-40.us-east-2.compute.internal pod exec-volume-test-dynamicpv-vhmm container exec-container-dynamicpv-vhmm: <nil>
STEP: delete the pod
Jun 13 00:27:24.511: INFO: Waiting for pod exec-volume-test-dynamicpv-vhmm to disappear
Jun 13 00:27:24.541: INFO: Pod exec-volume-test-dynamicpv-vhmm no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-vhmm
Jun 13 00:27:24.541: INFO: Deleting pod "exec-volume-test-dynamicpv-vhmm" in namespace "volume-3418"
... skipping 64 lines ...
STEP: Deleting pod hostexec-ip-172-20-44-97.us-east-2.compute.internal-kgmlr in namespace volumemode-3311
Jun 13 00:27:31.383: INFO: Deleting pod "pod-0728977e-f513-49d1-8285-60a3e6ad305b" in namespace "volumemode-3311"
Jun 13 00:27:31.415: INFO: Wait up to 5m0s for pod "pod-0728977e-f513-49d1-8285-60a3e6ad305b" to be fully deleted
STEP: Deleting pv and pvc
Jun 13 00:27:43.475: INFO: Deleting PersistentVolumeClaim "pvc-9fg8p"
Jun 13 00:27:43.507: INFO: Deleting PersistentVolume "aws-g2gd6"
Jun 13 00:27:43.659: INFO: Couldn't delete PD "aws://us-east-2a/vol-0ecb74dabf78614fd", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ecb74dabf78614fd is currently attached to i-008e8334048ae093c
	status code: 400, request id: 8a724247-d354-4370-b4cb-4e1e4a0cb6de
Jun 13 00:27:48.921: INFO: Couldn't delete PD "aws://us-east-2a/vol-0ecb74dabf78614fd", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ecb74dabf78614fd is currently attached to i-008e8334048ae093c
	status code: 400, request id: ab6bdff4-ff4a-458d-8943-e2b668054f53
Jun 13 00:27:54.228: INFO: Successfully deleted PD "aws://us-east-2a/vol-0ecb74dabf78614fd".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 13 00:27:54.228: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-3311" for this suite.
... skipping 20 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.8OXTe6tDm/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.8OXTe6tDm/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath file is outside the volume [Slow][LinuxOnly] [BeforeEach]
      /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 180 lines ...
Jun 13 00:26:17.442: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-4549vzhz6      0 0001-01-01 00:00:00 +0000 UTC <nil> <nil> map[] map[] [] []  []},Provisioner:kubernetes.io/aws-ebs,Parameters:map[string]string{},ReclaimPolicy:nil,MountOptions:[],AllowVolumeExpansion:nil,VolumeBindingMode:*WaitForFirstConsumer,AllowedTopologies:[]TopologySelectorTerm{},}, pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-4549    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:*provisioning-4549vzhz6,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-4549    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:*provisioning-4549vzhz6,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-4549    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:*provisioning-4549vzhz6,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-4549vzhz6    d5b067ea-9996-4b1e-ab77-45ea295cb8f4 8497 0 2021-06-13 00:26:17 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-13 00:26:17 +0000 UTC FieldsV1 {"f:mountOptions":{},"f:provisioner":{},"f:reclaimPolicy":{},"f:volumeBindingMode":{}}}]},Provisioner:kubernetes.io/aws-ebs,Parameters:map[string]string{},ReclaimPolicy:*Delete,MountOptions:[debug nouid32],AllowVolumeExpansion:nil,VolumeBindingMode:*WaitForFirstConsumer,AllowedTopologies:[]TopologySelectorTerm{},} claim=&PersistentVolumeClaim{ObjectMeta:{pvc-k4jvl pvc- provisioning-4549  bd066ac2-0316-4669-beb1-e8a339540fff 8501 0 2021-06-13 00:26:17 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-13 00:26:17 +0000 UTC FieldsV1 {"f:metadata":{"f:generateName":{}},"f:spec":{"f:accessModes":{},"f:resources":{"f:requests":{".":{},"f:storage":{}}},"f:storageClassName":{},"f:volumeMode":{}}}}]},Spec:PersistentVolumeClaimSpec{AccessModes:[ReadWriteOnce],Resources:ResourceRequirements{Limits:ResourceList{},Requests:ResourceList{storage: {{1073741824 0} {<nil>} 1Gi BinarySI},},},VolumeName:,Selector:nil,StorageClassName:*provisioning-4549vzhz6,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-38e16f0b-3ca4-4308-97bd-bac459477b91 in namespace provisioning-4549
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun 13 00:26:31.811: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-6npxk" in namespace "provisioning-4549" to be "Succeeded or Failed"
Jun 13 00:26:31.840: INFO: Pod "pvc-volume-tester-writer-6npxk": Phase="Pending", Reason="", readiness=false. Elapsed: 29.260739ms
Jun 13 00:26:33.870: INFO: Pod "pvc-volume-tester-writer-6npxk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.058922533s
Jun 13 00:26:35.899: INFO: Pod "pvc-volume-tester-writer-6npxk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.088631743s
Jun 13 00:26:37.929: INFO: Pod "pvc-volume-tester-writer-6npxk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.118449381s
Jun 13 00:26:39.960: INFO: Pod "pvc-volume-tester-writer-6npxk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.149006274s
Jun 13 00:26:41.989: INFO: Pod "pvc-volume-tester-writer-6npxk": Phase="Pending", Reason="", readiness=false. Elapsed: 10.178632712s
... skipping 24 lines ...
Jun 13 00:27:32.770: INFO: Pod "pvc-volume-tester-writer-6npxk": Phase="Pending", Reason="", readiness=false. Elapsed: 1m0.95973117s
Jun 13 00:27:34.801: INFO: Pod "pvc-volume-tester-writer-6npxk": Phase="Pending", Reason="", readiness=false. Elapsed: 1m2.990205765s
Jun 13 00:27:36.831: INFO: Pod "pvc-volume-tester-writer-6npxk": Phase="Pending", Reason="", readiness=false. Elapsed: 1m5.02020541s
Jun 13 00:27:38.861: INFO: Pod "pvc-volume-tester-writer-6npxk": Phase="Pending", Reason="", readiness=false. Elapsed: 1m7.050343861s
Jun 13 00:27:40.892: INFO: Pod "pvc-volume-tester-writer-6npxk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m9.080958259s
STEP: Saw pod success
Jun 13 00:27:40.892: INFO: Pod "pvc-volume-tester-writer-6npxk" satisfied condition "Succeeded or Failed"
Jun 13 00:27:40.951: INFO: Pod pvc-volume-tester-writer-6npxk has the following logs: 
Jun 13 00:27:40.952: INFO: Deleting pod "pvc-volume-tester-writer-6npxk" in namespace "provisioning-4549"
Jun 13 00:27:40.991: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-6npxk" to be fully deleted
STEP: checking the created volume has the correct mount options, is readable and retains data on the same node "ip-172-20-56-187.us-east-2.compute.internal"
Jun 13 00:27:41.159: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-vmmhf" in namespace "provisioning-4549" to be "Succeeded or Failed"
Jun 13 00:27:41.193: INFO: Pod "pvc-volume-tester-reader-vmmhf": Phase="Pending", Reason="", readiness=false. Elapsed: 34.566963ms
Jun 13 00:27:43.225: INFO: Pod "pvc-volume-tester-reader-vmmhf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.066327731s
Jun 13 00:27:45.255: INFO: Pod "pvc-volume-tester-reader-vmmhf": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.096162877s
STEP: Saw pod success
Jun 13 00:27:45.255: INFO: Pod "pvc-volume-tester-reader-vmmhf" satisfied condition "Succeeded or Failed"
Jun 13 00:27:45.317: INFO: Pod pvc-volume-tester-reader-vmmhf has the following logs: hello world

Jun 13 00:27:45.317: INFO: Deleting pod "pvc-volume-tester-reader-vmmhf" in namespace "provisioning-4549"
Jun 13 00:27:45.352: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-vmmhf" to be fully deleted
Jun 13 00:27:45.381: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-k4jvl] to have phase Bound
Jun 13 00:27:45.410: INFO: PersistentVolumeClaim pvc-k4jvl found and phase=Bound (29.257711ms)
... skipping 157 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 13 00:27:14.686: INFO: >>> kubeConfig: /root/.kube/config
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 file is outside the volume [Slow][LinuxOnly]
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun 13 00:27:14.834: INFO: Creating resource for dynamic PV
Jun 13 00:27:14.834: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5607-e2e-scxpwj4
STEP: creating a claim
Jun 13 00:27:14.864: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-nnlv
STEP: Checking for subpath error in container status
Jun 13 00:27:39.016: INFO: Deleting pod "pod-subpath-test-dynamicpv-nnlv" in namespace "provisioning-5607"
Jun 13 00:27:39.046: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-nnlv" to be fully deleted
STEP: Deleting pod
Jun 13 00:27:51.106: INFO: Deleting pod "pod-subpath-test-dynamicpv-nnlv" in namespace "provisioning-5607"
STEP: Deleting pvc
Jun 13 00:27:51.202: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comtpgz7"
... skipping 10 lines ...

• [SLOW TEST:46.745 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath file is outside the volume [Slow][LinuxOnly]
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 7 lines ...
Jun 13 00:27:15.718: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6634-e2e-scm2kf5
STEP: creating a claim
Jun 13 00:27:15.752: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-tqm8
STEP: Creating a pod to test multi_subpath
Jun 13 00:27:15.846: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-tqm8" in namespace "provisioning-6634" to be "Succeeded or Failed"
Jun 13 00:27:15.877: INFO: Pod "pod-subpath-test-dynamicpv-tqm8": Phase="Pending", Reason="", readiness=false. Elapsed: 30.298789ms
Jun 13 00:27:17.908: INFO: Pod "pod-subpath-test-dynamicpv-tqm8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061391049s
Jun 13 00:27:19.940: INFO: Pod "pod-subpath-test-dynamicpv-tqm8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.093286542s
Jun 13 00:27:21.971: INFO: Pod "pod-subpath-test-dynamicpv-tqm8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.124462858s
Jun 13 00:27:24.002: INFO: Pod "pod-subpath-test-dynamicpv-tqm8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.155273046s
Jun 13 00:27:26.034: INFO: Pod "pod-subpath-test-dynamicpv-tqm8": Phase="Pending", Reason="", readiness=false. Elapsed: 10.188092894s
Jun 13 00:27:28.066: INFO: Pod "pod-subpath-test-dynamicpv-tqm8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.219888495s
STEP: Saw pod success
Jun 13 00:27:28.066: INFO: Pod "pod-subpath-test-dynamicpv-tqm8" satisfied condition "Succeeded or Failed"
Jun 13 00:27:28.096: INFO: Trying to get logs from node ip-172-20-44-97.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-tqm8 container test-container-subpath-dynamicpv-tqm8: <nil>
STEP: delete the pod
Jun 13 00:27:28.168: INFO: Waiting for pod pod-subpath-test-dynamicpv-tqm8 to disappear
Jun 13 00:27:28.198: INFO: Pod pod-subpath-test-dynamicpv-tqm8 no longer exists
STEP: Deleting pod
Jun 13 00:27:28.198: INFO: Deleting pod "pod-subpath-test-dynamicpv-tqm8" in namespace "provisioning-6634"
... skipping 92 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.8OXTe6tDm/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.8OXTe6tDm/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly] [BeforeEach]
      /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 248 lines ...
Jun 13 00:26:03.902: INFO: Creating resource for dynamic PV
Jun 13 00:26:03.902: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-6488-e2e-scbsdj5
STEP: creating a claim
Jun 13 00:26:03.934: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 13 00:26:04.028: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-8xvnk" in namespace "snapshotting-6488" to be "Succeeded or Failed"
Jun 13 00:26:04.058: INFO: Pod "pvc-snapshottable-tester-8xvnk": Phase="Pending", Reason="", readiness=false. Elapsed: 30.192368ms
Jun 13 00:26:06.089: INFO: Pod "pvc-snapshottable-tester-8xvnk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.060715536s
Jun 13 00:26:08.119: INFO: Pod "pvc-snapshottable-tester-8xvnk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.091220879s
Jun 13 00:26:10.151: INFO: Pod "pvc-snapshottable-tester-8xvnk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.123138835s
Jun 13 00:26:12.181: INFO: Pod "pvc-snapshottable-tester-8xvnk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.153501342s
Jun 13 00:26:14.213: INFO: Pod "pvc-snapshottable-tester-8xvnk": Phase="Pending", Reason="", readiness=false. Elapsed: 10.184900406s
Jun 13 00:26:16.243: INFO: Pod "pvc-snapshottable-tester-8xvnk": Phase="Pending", Reason="", readiness=false. Elapsed: 12.215122501s
Jun 13 00:26:18.273: INFO: Pod "pvc-snapshottable-tester-8xvnk": Phase="Pending", Reason="", readiness=false. Elapsed: 14.245431311s
Jun 13 00:26:20.305: INFO: Pod "pvc-snapshottable-tester-8xvnk": Phase="Pending", Reason="", readiness=false. Elapsed: 16.27685142s
Jun 13 00:26:22.336: INFO: Pod "pvc-snapshottable-tester-8xvnk": Phase="Pending", Reason="", readiness=false. Elapsed: 18.308349968s
Jun 13 00:26:24.367: INFO: Pod "pvc-snapshottable-tester-8xvnk": Phase="Pending", Reason="", readiness=false. Elapsed: 20.338928967s
Jun 13 00:26:26.399: INFO: Pod "pvc-snapshottable-tester-8xvnk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.37063549s
STEP: Saw pod success
Jun 13 00:26:26.399: INFO: Pod "pvc-snapshottable-tester-8xvnk" satisfied condition "Succeeded or Failed"
Jun 13 00:26:26.469: INFO: Pod pvc-snapshottable-tester-8xvnk has the following logs: 
Jun 13 00:26:26.469: INFO: Deleting pod "pvc-snapshottable-tester-8xvnk" in namespace "snapshotting-6488"
Jun 13 00:26:26.517: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-8xvnk" to be fully deleted
Jun 13 00:26:26.548: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comkm5ks] to have phase Bound
Jun 13 00:26:26.579: INFO: PersistentVolumeClaim ebs.csi.aws.comkm5ks found and phase=Bound (30.364749ms)
STEP: [init] checking the claim
... skipping 50 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:243
STEP: checking the snapshot
STEP: checking the SnapshotContent
STEP: Modifying source data test
STEP: modifying the data in the source PVC
Jun 13 00:27:11.968: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-fsrxz" in namespace "snapshotting-6488" to be "Succeeded or Failed"
Jun 13 00:27:11.998: INFO: Pod "pvc-snapshottable-data-tester-fsrxz": Phase="Pending", Reason="", readiness=false. Elapsed: 30.049651ms
Jun 13 00:27:14.030: INFO: Pod "pvc-snapshottable-data-tester-fsrxz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061166709s
Jun 13 00:27:16.060: INFO: Pod "pvc-snapshottable-data-tester-fsrxz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.092007271s
Jun 13 00:27:18.091: INFO: Pod "pvc-snapshottable-data-tester-fsrxz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.122948553s
Jun 13 00:27:20.129: INFO: Pod "pvc-snapshottable-data-tester-fsrxz": Phase="Pending", Reason="", readiness=false. Elapsed: 8.161122323s
Jun 13 00:27:22.161: INFO: Pod "pvc-snapshottable-data-tester-fsrxz": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.192243162s
STEP: Saw pod success
Jun 13 00:27:22.161: INFO: Pod "pvc-snapshottable-data-tester-fsrxz" satisfied condition "Succeeded or Failed"
Jun 13 00:27:22.224: INFO: Pod pvc-snapshottable-data-tester-fsrxz has the following logs: 
Jun 13 00:27:22.224: INFO: Deleting pod "pvc-snapshottable-data-tester-fsrxz" in namespace "snapshotting-6488"
Jun 13 00:27:22.259: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-fsrxz" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 13 00:27:36.413: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-6488 exec restored-pvc-tester-vllnb --namespace=snapshotting-6488 -- cat /mnt/test/data'
... skipping 35 lines ...
Jun 13 00:28:18.550: INFO: At 2021-06-13 00:26:07 +0000 UTC - event for ebs.csi.aws.comkm5ks: {ebs.csi.aws.com_ebs-csi-controller-7ffff4ddf5-9z8vf_caef6610-de69-4e6d-9661-f85ceb515401 } ProvisioningSucceeded: Successfully provisioned volume pvc-8f372c8a-2161-4a59-a6d6-72b3d55ce137
Jun 13 00:28:18.550: INFO: At 2021-06-13 00:26:19 +0000 UTC - event for pvc-snapshottable-tester-8xvnk: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-8f372c8a-2161-4a59-a6d6-72b3d55ce137" 
Jun 13 00:28:18.550: INFO: At 2021-06-13 00:26:24 +0000 UTC - event for pvc-snapshottable-tester-8xvnk: {kubelet ip-172-20-44-97.us-east-2.compute.internal} Started: Started container volume-tester
Jun 13 00:28:18.550: INFO: At 2021-06-13 00:26:24 +0000 UTC - event for pvc-snapshottable-tester-8xvnk: {kubelet ip-172-20-44-97.us-east-2.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" already present on machine
Jun 13 00:28:18.550: INFO: At 2021-06-13 00:26:24 +0000 UTC - event for pvc-snapshottable-tester-8xvnk: {kubelet ip-172-20-44-97.us-east-2.compute.internal} Created: Created container volume-tester
Jun 13 00:28:18.550: INFO: At 2021-06-13 00:26:26 +0000 UTC - event for snapshot-dxx7w: {snapshot-controller } CreatingSnapshot: Waiting for a snapshot snapshotting-6488/snapshot-dxx7w to be created by the CSI driver.
Jun 13 00:28:18.550: INFO: At 2021-06-13 00:27:10 +0000 UTC - event for pre-provisioned-snapshot-cd9af5f9-d568-42cf-8ac6-298dae3beb57: {snapshot-controller } SnapshotFinalizerError: Failed to check and update snapshot: snapshot controller failed to update snapshotting-6488/pre-provisioned-snapshot-cd9af5f9-d568-42cf-8ac6-298dae3beb57 on API server: Operation cannot be fulfilled on volumesnapshots.snapshot.storage.k8s.io "pre-provisioned-snapshot-cd9af5f9-d568-42cf-8ac6-298dae3beb57": the object has been modified; please apply your changes to the latest version and try again
Jun 13 00:28:18.551: INFO: At 2021-06-13 00:27:15 +0000 UTC - event for pvc-snapshottable-data-tester-fsrxz: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-8f372c8a-2161-4a59-a6d6-72b3d55ce137" 
Jun 13 00:28:18.551: INFO: At 2021-06-13 00:27:20 +0000 UTC - event for pvc-snapshottable-data-tester-fsrxz: {kubelet ip-172-20-44-97.us-east-2.compute.internal} Created: Created container volume-tester
Jun 13 00:28:18.551: INFO: At 2021-06-13 00:27:20 +0000 UTC - event for pvc-snapshottable-data-tester-fsrxz: {kubelet ip-172-20-44-97.us-east-2.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" already present on machine
Jun 13 00:28:18.551: INFO: At 2021-06-13 00:27:20 +0000 UTC - event for pvc-snapshottable-data-tester-fsrxz: {kubelet ip-172-20-44-97.us-east-2.compute.internal} Started: Started container volume-tester
Jun 13 00:28:18.551: INFO: At 2021-06-13 00:27:22 +0000 UTC - event for pvc-w8qgb: {ebs.csi.aws.com_ebs-csi-controller-7ffff4ddf5-9z8vf_caef6610-de69-4e6d-9661-f85ceb515401 } Provisioning: External provisioner is provisioning volume for claim "snapshotting-6488/pvc-w8qgb"
Jun 13 00:28:18.551: INFO: At 2021-06-13 00:27:22 +0000 UTC - event for pvc-w8qgb: {persistentvolume-controller } ExternalProvisioning: waiting for a volume to be created, either by external provisioner "ebs.csi.aws.com" or manually created by system administrator
... skipping 214 lines ...
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:108
      
      /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:225
        should check snapshot fields, check restore correctly works after modifying source data, check deletion [It]
        /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:243

        Unexpected error:
            <exec.CodeExitError>: {
                Err: {
                    s: "error running /usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-6488 exec restored-pvc-tester-vllnb --namespace=snapshotting-6488 -- cat /mnt/test/data:\nCommand stdout:\n\nstderr:\ncat: can't open '/mnt/test/data': No such file or directory\ncommand terminated with exit code 1\n\nerror:\nexit status 1",
                },
                Code: 1,
            }
            error running /usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-6488 exec restored-pvc-tester-vllnb --namespace=snapshotting-6488 -- cat /mnt/test/data:
            Command stdout:
            
            stderr:
            cat: can't open '/mnt/test/data': No such file or directory
            command terminated with exit code 1
            
            error:
            exit status 1
        occurred

        /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:602
------------------------------
[BeforeEach] [sig-storage] vsphere cloud provider stress [Feature:vsphere]
... skipping 36 lines ...
Jun 13 00:27:50.085: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8196fhc8s
STEP: creating a claim
Jun 13 00:27:50.114: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-6gc5
STEP: Creating a pod to test multi_subpath
Jun 13 00:27:50.206: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-6gc5" in namespace "provisioning-8196" to be "Succeeded or Failed"
Jun 13 00:27:50.235: INFO: Pod "pod-subpath-test-dynamicpv-6gc5": Phase="Pending", Reason="", readiness=false. Elapsed: 29.117261ms
Jun 13 00:27:52.265: INFO: Pod "pod-subpath-test-dynamicpv-6gc5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.058630433s
Jun 13 00:27:54.294: INFO: Pod "pod-subpath-test-dynamicpv-6gc5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.088175118s
Jun 13 00:27:56.324: INFO: Pod "pod-subpath-test-dynamicpv-6gc5": Phase="Pending", Reason="", readiness=false. Elapsed: 6.118301749s
Jun 13 00:27:58.355: INFO: Pod "pod-subpath-test-dynamicpv-6gc5": Phase="Pending", Reason="", readiness=false. Elapsed: 8.148795015s
Jun 13 00:28:00.385: INFO: Pod "pod-subpath-test-dynamicpv-6gc5": Phase="Pending", Reason="", readiness=false. Elapsed: 10.178657957s
... skipping 5 lines ...
Jun 13 00:28:12.567: INFO: Pod "pod-subpath-test-dynamicpv-6gc5": Phase="Pending", Reason="", readiness=false. Elapsed: 22.361045021s
Jun 13 00:28:14.597: INFO: Pod "pod-subpath-test-dynamicpv-6gc5": Phase="Pending", Reason="", readiness=false. Elapsed: 24.390770794s
Jun 13 00:28:16.627: INFO: Pod "pod-subpath-test-dynamicpv-6gc5": Phase="Pending", Reason="", readiness=false. Elapsed: 26.420809948s
Jun 13 00:28:18.659: INFO: Pod "pod-subpath-test-dynamicpv-6gc5": Phase="Pending", Reason="", readiness=false. Elapsed: 28.453215208s
Jun 13 00:28:20.689: INFO: Pod "pod-subpath-test-dynamicpv-6gc5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 30.483244088s
STEP: Saw pod success
Jun 13 00:28:20.690: INFO: Pod "pod-subpath-test-dynamicpv-6gc5" satisfied condition "Succeeded or Failed"
Jun 13 00:28:20.719: INFO: Trying to get logs from node ip-172-20-32-240.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-6gc5 container test-container-subpath-dynamicpv-6gc5: <nil>
STEP: delete the pod
Jun 13 00:28:20.791: INFO: Waiting for pod pod-subpath-test-dynamicpv-6gc5 to disappear
Jun 13 00:28:20.821: INFO: Pod pod-subpath-test-dynamicpv-6gc5 no longer exists
STEP: Deleting pod
Jun 13 00:28:20.821: INFO: Deleting pod "pod-subpath-test-dynamicpv-6gc5" in namespace "provisioning-8196"
... skipping 363 lines ...
Jun 13 00:27:30.194: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1463gqwwk
STEP: creating a claim
Jun 13 00:27:30.225: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-lczb
STEP: Creating a pod to test subpath
Jun 13 00:27:30.321: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-lczb" in namespace "provisioning-1463" to be "Succeeded or Failed"
Jun 13 00:27:30.351: INFO: Pod "pod-subpath-test-dynamicpv-lczb": Phase="Pending", Reason="", readiness=false. Elapsed: 30.541991ms
Jun 13 00:27:32.383: INFO: Pod "pod-subpath-test-dynamicpv-lczb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062238322s
Jun 13 00:27:34.414: INFO: Pod "pod-subpath-test-dynamicpv-lczb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.093083372s
Jun 13 00:27:36.447: INFO: Pod "pod-subpath-test-dynamicpv-lczb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.126116722s
Jun 13 00:27:38.478: INFO: Pod "pod-subpath-test-dynamicpv-lczb": Phase="Pending", Reason="", readiness=false. Elapsed: 8.156837178s
Jun 13 00:27:40.510: INFO: Pod "pod-subpath-test-dynamicpv-lczb": Phase="Pending", Reason="", readiness=false. Elapsed: 10.188804118s
... skipping 10 lines ...
Jun 13 00:28:02.856: INFO: Pod "pod-subpath-test-dynamicpv-lczb": Phase="Pending", Reason="", readiness=false. Elapsed: 32.535446327s
Jun 13 00:28:04.887: INFO: Pod "pod-subpath-test-dynamicpv-lczb": Phase="Pending", Reason="", readiness=false. Elapsed: 34.566489217s
Jun 13 00:28:06.918: INFO: Pod "pod-subpath-test-dynamicpv-lczb": Phase="Pending", Reason="", readiness=false. Elapsed: 36.597098604s
Jun 13 00:28:08.949: INFO: Pod "pod-subpath-test-dynamicpv-lczb": Phase="Pending", Reason="", readiness=false. Elapsed: 38.628604749s
Jun 13 00:28:10.981: INFO: Pod "pod-subpath-test-dynamicpv-lczb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 40.660399142s
STEP: Saw pod success
Jun 13 00:28:10.981: INFO: Pod "pod-subpath-test-dynamicpv-lczb" satisfied condition "Succeeded or Failed"
Jun 13 00:28:11.011: INFO: Trying to get logs from node ip-172-20-58-40.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-lczb container test-container-subpath-dynamicpv-lczb: <nil>
STEP: delete the pod
Jun 13 00:28:11.090: INFO: Waiting for pod pod-subpath-test-dynamicpv-lczb to disappear
Jun 13 00:28:11.119: INFO: Pod pod-subpath-test-dynamicpv-lczb no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-lczb
Jun 13 00:28:11.120: INFO: Deleting pod "pod-subpath-test-dynamicpv-lczb" in namespace "provisioning-1463"
STEP: Creating pod pod-subpath-test-dynamicpv-lczb
STEP: Creating a pod to test subpath
Jun 13 00:28:11.262: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-lczb" in namespace "provisioning-1463" to be "Succeeded or Failed"
Jun 13 00:28:11.303: INFO: Pod "pod-subpath-test-dynamicpv-lczb": Phase="Pending", Reason="", readiness=false. Elapsed: 40.326702ms
Jun 13 00:28:13.335: INFO: Pod "pod-subpath-test-dynamicpv-lczb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.072515175s
Jun 13 00:28:15.367: INFO: Pod "pod-subpath-test-dynamicpv-lczb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.104577007s
Jun 13 00:28:17.398: INFO: Pod "pod-subpath-test-dynamicpv-lczb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.135775454s
STEP: Saw pod success
Jun 13 00:28:17.398: INFO: Pod "pod-subpath-test-dynamicpv-lczb" satisfied condition "Succeeded or Failed"
Jun 13 00:28:17.431: INFO: Trying to get logs from node ip-172-20-58-40.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-lczb container test-container-subpath-dynamicpv-lczb: <nil>
STEP: delete the pod
Jun 13 00:28:17.497: INFO: Waiting for pod pod-subpath-test-dynamicpv-lczb to disappear
Jun 13 00:28:17.527: INFO: Pod pod-subpath-test-dynamicpv-lczb no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-lczb
Jun 13 00:28:17.527: INFO: Deleting pod "pod-subpath-test-dynamicpv-lczb" in namespace "provisioning-1463"
... skipping 121 lines ...
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 13 00:28:38.172: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename topology
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
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Jun 13 00:28:38.355: INFO: found topology map[topology.kubernetes.io/zone:us-east-2a]
Jun 13 00:28:38.355: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 13 00:28:38.355: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.8OXTe6tDm/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.8OXTe6tDm/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (immediate binding)] topology
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail to schedule a pod which has topologies that conflict with AllowedTopologies [It]
      /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 54 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.8OXTe6tDm/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.8OXTe6tDm/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath directory is outside the volume [Slow][LinuxOnly] [BeforeEach]
      /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 662 lines ...
Jun 13 00:27:54.672: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-930-e2e-scwb4h2
STEP: creating a claim
Jun 13 00:27:54.703: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-pl9w
STEP: Creating a pod to test subpath
Jun 13 00:27:54.796: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-pl9w" in namespace "provisioning-930" to be "Succeeded or Failed"
Jun 13 00:27:54.825: INFO: Pod "pod-subpath-test-dynamicpv-pl9w": Phase="Pending", Reason="", readiness=false. Elapsed: 29.495024ms
Jun 13 00:27:56.856: INFO: Pod "pod-subpath-test-dynamicpv-pl9w": Phase="Pending", Reason="", readiness=false. Elapsed: 2.059865689s
Jun 13 00:27:58.887: INFO: Pod "pod-subpath-test-dynamicpv-pl9w": Phase="Pending", Reason="", readiness=false. Elapsed: 4.091218454s
Jun 13 00:28:00.921: INFO: Pod "pod-subpath-test-dynamicpv-pl9w": Phase="Pending", Reason="", readiness=false. Elapsed: 6.125319354s
Jun 13 00:28:02.951: INFO: Pod "pod-subpath-test-dynamicpv-pl9w": Phase="Pending", Reason="", readiness=false. Elapsed: 8.155527784s
Jun 13 00:28:04.982: INFO: Pod "pod-subpath-test-dynamicpv-pl9w": Phase="Pending", Reason="", readiness=false. Elapsed: 10.185835238s
Jun 13 00:28:07.013: INFO: Pod "pod-subpath-test-dynamicpv-pl9w": Phase="Pending", Reason="", readiness=false. Elapsed: 12.217128841s
Jun 13 00:28:09.043: INFO: Pod "pod-subpath-test-dynamicpv-pl9w": Phase="Pending", Reason="", readiness=false. Elapsed: 14.247677336s
Jun 13 00:28:11.074: INFO: Pod "pod-subpath-test-dynamicpv-pl9w": Phase="Pending", Reason="", readiness=false. Elapsed: 16.278095192s
Jun 13 00:28:13.104: INFO: Pod "pod-subpath-test-dynamicpv-pl9w": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.308650456s
STEP: Saw pod success
Jun 13 00:28:13.104: INFO: Pod "pod-subpath-test-dynamicpv-pl9w" satisfied condition "Succeeded or Failed"
Jun 13 00:28:13.134: INFO: Trying to get logs from node ip-172-20-32-240.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-pl9w container test-container-subpath-dynamicpv-pl9w: <nil>
STEP: delete the pod
Jun 13 00:28:14.082: INFO: Waiting for pod pod-subpath-test-dynamicpv-pl9w to disappear
Jun 13 00:28:14.111: INFO: Pod pod-subpath-test-dynamicpv-pl9w no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-pl9w
Jun 13 00:28:14.111: INFO: Deleting pod "pod-subpath-test-dynamicpv-pl9w" in namespace "provisioning-930"
... skipping 148 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.8OXTe6tDm/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.8OXTe6tDm/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if non-existent subpath is outside the volume [Slow][LinuxOnly] [BeforeEach]
      /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 47 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 13 00:28:31.801: INFO: >>> kubeConfig: /root/.kube/config
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]
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 13 00:28:31.953: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 13 00:28:32.396: INFO: Successfully created a new PD: "aws://us-east-2a/vol-0bcf93af4ad5c67ce".
Jun 13 00:28:32.397: INFO: Creating resource for pre-provisioned PV
Jun 13 00:28:32.397: INFO: Creating PVC and PV
... skipping 5 lines ...
Jun 13 00:28:36.628: INFO: PersistentVolumeClaim pvc-n587x found but phase is Pending instead of Bound.
Jun 13 00:28:38.659: INFO: PersistentVolumeClaim pvc-n587x found but phase is Pending instead of Bound.
Jun 13 00:28:40.691: INFO: PersistentVolumeClaim pvc-n587x found and phase=Bound (8.156101283s)
Jun 13 00:28:40.691: INFO: Waiting up to 3m0s for PersistentVolume aws-47r9g to have phase Bound
Jun 13 00:28:40.722: INFO: PersistentVolume aws-47r9g found and phase=Bound (30.999141ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 13 00:28:42.910: INFO: Deleting pod "pod-34861b74-139e-4587-b218-e05d6963cf2b" in namespace "volumemode-6036"
Jun 13 00:28:42.949: INFO: Wait up to 5m0s for pod "pod-34861b74-139e-4587-b218-e05d6963cf2b" to be fully deleted
STEP: Deleting pv and pvc
Jun 13 00:28:53.015: INFO: Deleting PersistentVolumeClaim "pvc-n587x"
Jun 13 00:28:53.045: INFO: Deleting PersistentVolume "aws-47r9g"
Jun 13 00:28:53.231: INFO: Couldn't delete PD "aws://us-east-2a/vol-0bcf93af4ad5c67ce", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0bcf93af4ad5c67ce is currently attached to i-008e8334048ae093c
	status code: 400, request id: 9b1f512b-cee3-4c7f-8b37-0ae7446d9031
Jun 13 00:28:58.514: INFO: Successfully deleted PD "aws://us-east-2a/vol-0bcf93af4ad5c67ce".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 13 00:28:58.514: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-6036" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.8OXTe6tDm/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.8OXTe6tDm/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail to use a volume in a pod with mismatched mode [Slow]
      /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volume-expand
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volume-expand
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 7 lines ...
Jun 13 00:28:38.167: INFO: Creating resource for dynamic PV
Jun 13 00:28:38.167: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-3243ks6d9
STEP: creating a claim
STEP: Expanding non-expandable pvc
Jun 13 00:28:38.259: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 13 00:28:38.320: INFO: Error updating pvc awsfmd4c: PersistentVolumeClaim "awsfmd4c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3243ks6d9",
  	... // 2 identical fields
  }

Jun 13 00:28:40.381: INFO: Error updating pvc awsfmd4c: PersistentVolumeClaim "awsfmd4c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3243ks6d9",
  	... // 2 identical fields
  }

Jun 13 00:28:42.384: INFO: Error updating pvc awsfmd4c: PersistentVolumeClaim "awsfmd4c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3243ks6d9",
  	... // 2 identical fields
  }

Jun 13 00:28:44.381: INFO: Error updating pvc awsfmd4c: PersistentVolumeClaim "awsfmd4c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3243ks6d9",
  	... // 2 identical fields
  }

Jun 13 00:28:46.382: INFO: Error updating pvc awsfmd4c: PersistentVolumeClaim "awsfmd4c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3243ks6d9",
  	... // 2 identical fields
  }

Jun 13 00:28:48.382: INFO: Error updating pvc awsfmd4c: PersistentVolumeClaim "awsfmd4c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3243ks6d9",
  	... // 2 identical fields
  }

Jun 13 00:28:50.382: INFO: Error updating pvc awsfmd4c: PersistentVolumeClaim "awsfmd4c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3243ks6d9",
  	... // 2 identical fields
  }

Jun 13 00:28:52.381: INFO: Error updating pvc awsfmd4c: PersistentVolumeClaim "awsfmd4c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3243ks6d9",
  	... // 2 identical fields
  }

Jun 13 00:28:54.381: INFO: Error updating pvc awsfmd4c: PersistentVolumeClaim "awsfmd4c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3243ks6d9",
  	... // 2 identical fields
  }

Jun 13 00:28:56.381: INFO: Error updating pvc awsfmd4c: PersistentVolumeClaim "awsfmd4c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3243ks6d9",
  	... // 2 identical fields
  }

Jun 13 00:28:58.381: INFO: Error updating pvc awsfmd4c: PersistentVolumeClaim "awsfmd4c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3243ks6d9",
  	... // 2 identical fields
  }

Jun 13 00:29:00.382: INFO: Error updating pvc awsfmd4c: PersistentVolumeClaim "awsfmd4c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3243ks6d9",
  	... // 2 identical fields
  }

Jun 13 00:29:02.381: INFO: Error updating pvc awsfmd4c: PersistentVolumeClaim "awsfmd4c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3243ks6d9",
  	... // 2 identical fields
  }

Jun 13 00:29:04.382: INFO: Error updating pvc awsfmd4c: PersistentVolumeClaim "awsfmd4c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3243ks6d9",
  	... // 2 identical fields
  }

Jun 13 00:29:06.381: INFO: Error updating pvc awsfmd4c: PersistentVolumeClaim "awsfmd4c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3243ks6d9",
  	... // 2 identical fields
  }

Jun 13 00:29:08.383: INFO: Error updating pvc awsfmd4c: PersistentVolumeClaim "awsfmd4c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3243ks6d9",
  	... // 2 identical fields
  }

Jun 13 00:29:08.443: INFO: Error updating pvc awsfmd4c: PersistentVolumeClaim "awsfmd4c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 144 lines ...
Jun 13 00:28:40.697: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-7657t7svs
STEP: creating a claim
Jun 13 00:28:40.727: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Jun 13 00:28:40.789: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 13 00:28:40.857: INFO: Error updating pvc awsfdcj6: PersistentVolumeClaim "awsfdcj6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-7657t7svs",
  	... // 2 identical fields
  }

Jun 13 00:28:42.937: INFO: Error updating pvc awsfdcj6: PersistentVolumeClaim "awsfdcj6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-7657t7svs",
  	... // 2 identical fields
  }

Jun 13 00:28:44.920: INFO: Error updating pvc awsfdcj6: PersistentVolumeClaim "awsfdcj6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-7657t7svs",
  	... // 2 identical fields
  }

Jun 13 00:28:46.920: INFO: Error updating pvc awsfdcj6: PersistentVolumeClaim "awsfdcj6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-7657t7svs",
  	... // 2 identical fields
  }

Jun 13 00:28:48.920: INFO: Error updating pvc awsfdcj6: PersistentVolumeClaim "awsfdcj6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-7657t7svs",
  	... // 2 identical fields
  }

Jun 13 00:28:50.920: INFO: Error updating pvc awsfdcj6: PersistentVolumeClaim "awsfdcj6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-7657t7svs",
  	... // 2 identical fields
  }

Jun 13 00:28:52.920: INFO: Error updating pvc awsfdcj6: PersistentVolumeClaim "awsfdcj6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-7657t7svs",
  	... // 2 identical fields
  }

Jun 13 00:28:54.921: INFO: Error updating pvc awsfdcj6: PersistentVolumeClaim "awsfdcj6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-7657t7svs",
  	... // 2 identical fields
  }

Jun 13 00:28:56.919: INFO: Error updating pvc awsfdcj6: PersistentVolumeClaim "awsfdcj6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-7657t7svs",
  	... // 2 identical fields
  }

Jun 13 00:28:58.919: INFO: Error updating pvc awsfdcj6: PersistentVolumeClaim "awsfdcj6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-7657t7svs",
  	... // 2 identical fields
  }

Jun 13 00:29:00.919: INFO: Error updating pvc awsfdcj6: PersistentVolumeClaim "awsfdcj6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-7657t7svs",
  	... // 2 identical fields
  }

Jun 13 00:29:02.919: INFO: Error updating pvc awsfdcj6: PersistentVolumeClaim "awsfdcj6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-7657t7svs",
  	... // 2 identical fields
  }

Jun 13 00:29:04.921: INFO: Error updating pvc awsfdcj6: PersistentVolumeClaim "awsfdcj6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-7657t7svs",
  	... // 2 identical fields
  }

Jun 13 00:29:06.919: INFO: Error updating pvc awsfdcj6: PersistentVolumeClaim "awsfdcj6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-7657t7svs",
  	... // 2 identical fields
  }

Jun 13 00:29:08.919: INFO: Error updating pvc awsfdcj6: PersistentVolumeClaim "awsfdcj6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-7657t7svs",
  	... // 2 identical fields
  }

Jun 13 00:29:10.922: INFO: Error updating pvc awsfdcj6: PersistentVolumeClaim "awsfdcj6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-7657t7svs",
  	... // 2 identical fields
  }

Jun 13 00:29:10.984: INFO: Error updating pvc awsfdcj6: PersistentVolumeClaim "awsfdcj6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 32 lines ...
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 13 00:29:11.148: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename topology
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
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Jun 13 00:29:11.347: INFO: found topology map[topology.kubernetes.io/zone:us-east-2a]
Jun 13 00:29:11.347: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 13 00:29:11.347: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.8OXTe6tDm/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.8OXTe6tDm/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (delayed binding)] topology
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail to schedule a pod which has topologies that conflict with AllowedTopologies [It]
      /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 27 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath file is outside the volume [Slow][LinuxOnly] [BeforeEach]
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

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

    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 160 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.8OXTe6tDm/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.8OXTe6tDm/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath directory is outside the volume [Slow][LinuxOnly] [BeforeEach]
      /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 6 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if non-existent subpath is outside the volume [Slow][LinuxOnly] [BeforeEach]
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

    Driver "ebs.csi.aws.com" does not support volume type "PreprovisionedPV" - skipping

    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 63 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 13 00:28:58.577: INFO: >>> kubeConfig: /root/.kube/config
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]
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 13 00:28:58.724: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 13 00:28:58.724: INFO: Creating resource for dynamic PV
Jun 13 00:28:58.724: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-1304d5b6g
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 13 00:29:04.944: INFO: Deleting pod "pod-0fb42a2d-3416-4704-be47-05f1a5b645e5" in namespace "volumemode-1304"
Jun 13 00:29:04.976: INFO: Wait up to 5m0s for pod "pod-0fb42a2d-3416-4704-be47-05f1a5b645e5" to be fully deleted
STEP: Deleting pvc
Jun 13 00:29:13.113: INFO: Deleting PersistentVolumeClaim "aws8qm4w"
Jun 13 00:29:13.143: INFO: Waiting up to 5m0s for PersistentVolume pvc-d2e684a1-6287-4c8c-865f-7629aa1d1999 to get deleted
Jun 13 00:29:13.173: INFO: PersistentVolume pvc-d2e684a1-6287-4c8c-865f-7629aa1d1999 found and phase=Released (29.646884ms)
... skipping 9 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.8OXTe6tDm/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.8OXTe6tDm/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail to use a volume in a pod with mismatched mode [Slow]
      /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
S
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned Snapshot (retain policy)] snapshottable[Feature:VolumeSnapshotDataSource]
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
... skipping 33 lines ...
Jun 13 00:26:17.816: INFO: Creating resource for dynamic PV
Jun 13 00:26:17.816: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-3098-e2e-sc8dqpm
STEP: creating a claim
Jun 13 00:26:17.848: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 13 00:26:17.944: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-6bptn" in namespace "snapshotting-3098" to be "Succeeded or Failed"
Jun 13 00:26:17.975: INFO: Pod "pvc-snapshottable-tester-6bptn": Phase="Pending", Reason="", readiness=false. Elapsed: 30.635033ms
Jun 13 00:26:20.005: INFO: Pod "pvc-snapshottable-tester-6bptn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.06118445s
Jun 13 00:26:22.037: INFO: Pod "pvc-snapshottable-tester-6bptn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.092379185s
Jun 13 00:26:24.069: INFO: Pod "pvc-snapshottable-tester-6bptn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.124730314s
Jun 13 00:26:26.103: INFO: Pod "pvc-snapshottable-tester-6bptn": Phase="Pending", Reason="", readiness=false. Elapsed: 8.158736029s
Jun 13 00:26:28.134: INFO: Pod "pvc-snapshottable-tester-6bptn": Phase="Pending", Reason="", readiness=false. Elapsed: 10.189666264s
Jun 13 00:26:30.168: INFO: Pod "pvc-snapshottable-tester-6bptn": Phase="Pending", Reason="", readiness=false. Elapsed: 12.223206106s
Jun 13 00:26:32.199: INFO: Pod "pvc-snapshottable-tester-6bptn": Phase="Pending", Reason="", readiness=false. Elapsed: 14.254433645s
Jun 13 00:26:34.231: INFO: Pod "pvc-snapshottable-tester-6bptn": Phase="Pending", Reason="", readiness=false. Elapsed: 16.286476338s
Jun 13 00:26:36.262: INFO: Pod "pvc-snapshottable-tester-6bptn": Phase="Pending", Reason="", readiness=false. Elapsed: 18.317410585s
Jun 13 00:26:38.293: INFO: Pod "pvc-snapshottable-tester-6bptn": Phase="Pending", Reason="", readiness=false. Elapsed: 20.348488351s
Jun 13 00:26:40.325: INFO: Pod "pvc-snapshottable-tester-6bptn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.380482386s
STEP: Saw pod success
Jun 13 00:26:40.325: INFO: Pod "pvc-snapshottable-tester-6bptn" satisfied condition "Succeeded or Failed"
Jun 13 00:26:40.387: INFO: Pod pvc-snapshottable-tester-6bptn has the following logs: 
Jun 13 00:26:40.387: INFO: Deleting pod "pvc-snapshottable-tester-6bptn" in namespace "snapshotting-3098"
Jun 13 00:26:40.423: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-6bptn" to be fully deleted
Jun 13 00:26:40.453: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comgmnpr] to have phase Bound
Jun 13 00:26:40.483: INFO: PersistentVolumeClaim ebs.csi.aws.comgmnpr found and phase=Bound (30.281099ms)
STEP: [init] checking the claim
... skipping 42 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:243
STEP: checking the snapshot
STEP: checking the SnapshotContent
STEP: Modifying source data test
STEP: modifying the data in the source PVC
Jun 13 00:27:09.638: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-ms857" in namespace "snapshotting-3098" to be "Succeeded or Failed"
Jun 13 00:27:09.668: INFO: Pod "pvc-snapshottable-data-tester-ms857": Phase="Pending", Reason="", readiness=false. Elapsed: 30.308111ms
Jun 13 00:27:11.700: INFO: Pod "pvc-snapshottable-data-tester-ms857": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062374229s
Jun 13 00:27:13.732: INFO: Pod "pvc-snapshottable-data-tester-ms857": Phase="Pending", Reason="", readiness=false. Elapsed: 4.093833515s
Jun 13 00:27:15.763: INFO: Pod "pvc-snapshottable-data-tester-ms857": Phase="Pending", Reason="", readiness=false. Elapsed: 6.125468683s
Jun 13 00:27:17.795: INFO: Pod "pvc-snapshottable-data-tester-ms857": Phase="Pending", Reason="", readiness=false. Elapsed: 8.157262878s
Jun 13 00:27:19.826: INFO: Pod "pvc-snapshottable-data-tester-ms857": Phase="Pending", Reason="", readiness=false. Elapsed: 10.188116736s
Jun 13 00:27:21.857: INFO: Pod "pvc-snapshottable-data-tester-ms857": Phase="Pending", Reason="", readiness=false. Elapsed: 12.219728026s
Jun 13 00:27:23.889: INFO: Pod "pvc-snapshottable-data-tester-ms857": Phase="Pending", Reason="", readiness=false. Elapsed: 14.251054996s
Jun 13 00:27:25.921: INFO: Pod "pvc-snapshottable-data-tester-ms857": Phase="Pending", Reason="", readiness=false. Elapsed: 16.283386041s
Jun 13 00:27:27.952: INFO: Pod "pvc-snapshottable-data-tester-ms857": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.314175589s
STEP: Saw pod success
Jun 13 00:27:27.952: INFO: Pod "pvc-snapshottable-data-tester-ms857" satisfied condition "Succeeded or Failed"
Jun 13 00:27:28.015: INFO: Pod pvc-snapshottable-data-tester-ms857 has the following logs: 
Jun 13 00:27:28.015: INFO: Deleting pod "pvc-snapshottable-data-tester-ms857" in namespace "snapshotting-3098"
Jun 13 00:27:28.054: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-ms857" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 13 00:28:06.209: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-3098 exec restored-pvc-tester-f6mlj --namespace=snapshotting-3098 -- cat /mnt/test/data'
... skipping 33 lines ...
Jun 13 00:28:31.636: INFO: volumesnapshotcontents pre-provisioned-snapcontent-4fc467f9-4538-4505-97e9-216851fd811f has been found and is not deleted
Jun 13 00:28:32.667: INFO: volumesnapshotcontents pre-provisioned-snapcontent-4fc467f9-4538-4505-97e9-216851fd811f has been found and is not deleted
Jun 13 00:28:33.699: INFO: volumesnapshotcontents pre-provisioned-snapcontent-4fc467f9-4538-4505-97e9-216851fd811f has been found and is not deleted
Jun 13 00:28:34.731: INFO: volumesnapshotcontents pre-provisioned-snapcontent-4fc467f9-4538-4505-97e9-216851fd811f has been found and is not deleted
Jun 13 00:28:35.763: INFO: volumesnapshotcontents pre-provisioned-snapcontent-4fc467f9-4538-4505-97e9-216851fd811f has been found and is not deleted
Jun 13 00:28:36.795: INFO: volumesnapshotcontents pre-provisioned-snapcontent-4fc467f9-4538-4505-97e9-216851fd811f has been found and is not deleted
Jun 13 00:28:37.796: INFO: WaitUntil failed after reaching the timeout 30s
[AfterEach] volume snapshot controller
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:221
Jun 13 00:28:37.829: INFO: Pod restored-pvc-tester-f6mlj has the following logs: 
Jun 13 00:28:37.829: INFO: Deleting pod "restored-pvc-tester-f6mlj" in namespace "snapshotting-3098"
Jun 13 00:28:37.860: INFO: Wait up to 5m0s for pod "restored-pvc-tester-f6mlj" to be fully deleted
Jun 13 00:29:11.923: INFO: deleting claim "snapshotting-3098"/"pvc-n8kj8"
... skipping 134 lines ...
Jun 13 00:28:47.344: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 13 00:28:47.786: INFO: Successfully created a new PD: "aws://us-east-2a/vol-0e61c1b3bfb43c0d4".
Jun 13 00:28:47.787: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-bv2j
STEP: Creating a pod to test exec-volume-test
Jun 13 00:28:47.817: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-bv2j" in namespace "volume-2579" to be "Succeeded or Failed"
Jun 13 00:28:47.846: INFO: Pod "exec-volume-test-inlinevolume-bv2j": Phase="Pending", Reason="", readiness=false. Elapsed: 28.747599ms
Jun 13 00:28:49.875: INFO: Pod "exec-volume-test-inlinevolume-bv2j": Phase="Pending", Reason="", readiness=false. Elapsed: 2.057833036s
Jun 13 00:28:51.905: INFO: Pod "exec-volume-test-inlinevolume-bv2j": Phase="Pending", Reason="", readiness=false. Elapsed: 4.088404895s
Jun 13 00:28:53.935: INFO: Pod "exec-volume-test-inlinevolume-bv2j": Phase="Pending", Reason="", readiness=false. Elapsed: 6.11771927s
Jun 13 00:28:55.965: INFO: Pod "exec-volume-test-inlinevolume-bv2j": Phase="Pending", Reason="", readiness=false. Elapsed: 8.147870777s
Jun 13 00:28:57.996: INFO: Pod "exec-volume-test-inlinevolume-bv2j": Phase="Pending", Reason="", readiness=false. Elapsed: 10.178572948s
Jun 13 00:29:00.026: INFO: Pod "exec-volume-test-inlinevolume-bv2j": Phase="Pending", Reason="", readiness=false. Elapsed: 12.208697286s
Jun 13 00:29:02.059: INFO: Pod "exec-volume-test-inlinevolume-bv2j": Phase="Pending", Reason="", readiness=false. Elapsed: 14.241823133s
Jun 13 00:29:04.089: INFO: Pod "exec-volume-test-inlinevolume-bv2j": Phase="Pending", Reason="", readiness=false. Elapsed: 16.271881593s
Jun 13 00:29:06.127: INFO: Pod "exec-volume-test-inlinevolume-bv2j": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.310279229s
STEP: Saw pod success
Jun 13 00:29:06.127: INFO: Pod "exec-volume-test-inlinevolume-bv2j" satisfied condition "Succeeded or Failed"
Jun 13 00:29:06.156: INFO: Trying to get logs from node ip-172-20-44-97.us-east-2.compute.internal pod exec-volume-test-inlinevolume-bv2j container exec-container-inlinevolume-bv2j: <nil>
STEP: delete the pod
Jun 13 00:29:06.223: INFO: Waiting for pod exec-volume-test-inlinevolume-bv2j to disappear
Jun 13 00:29:06.256: INFO: Pod exec-volume-test-inlinevolume-bv2j no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-bv2j
Jun 13 00:29:06.256: INFO: Deleting pod "exec-volume-test-inlinevolume-bv2j" in namespace "volume-2579"
Jun 13 00:29:06.410: INFO: Couldn't delete PD "aws://us-east-2a/vol-0e61c1b3bfb43c0d4", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e61c1b3bfb43c0d4 is currently attached to i-008e8334048ae093c
	status code: 400, request id: 61f4acf5-bcf9-4125-9404-1d8e7ff24e91
Jun 13 00:29:11.649: INFO: Couldn't delete PD "aws://us-east-2a/vol-0e61c1b3bfb43c0d4", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e61c1b3bfb43c0d4 is currently attached to i-008e8334048ae093c
	status code: 400, request id: 62db4512-8b39-4cfb-a5ff-073d57dadb67
Jun 13 00:29:16.898: INFO: Couldn't delete PD "aws://us-east-2a/vol-0e61c1b3bfb43c0d4", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e61c1b3bfb43c0d4 is currently attached to i-008e8334048ae093c
	status code: 400, request id: a4df5887-830e-4cea-b326-bfc63f582dab
Jun 13 00:29:22.156: INFO: Successfully deleted PD "aws://us-east-2a/vol-0e61c1b3bfb43c0d4".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 13 00:29:22.156: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-2579" for this suite.
... skipping 14 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 13 00:28:01.434: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename provisioning
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail if non-existent subpath is outside the volume [Slow][LinuxOnly]
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun 13 00:28:01.584: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 13 00:28:01.584: INFO: Creating resource for dynamic PV
Jun 13 00:28:01.584: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5333mnxjk
STEP: creating a claim
Jun 13 00:28:01.615: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-xwt8
STEP: Checking for subpath error in container status
Jun 13 00:28:41.789: INFO: Deleting pod "pod-subpath-test-dynamicpv-xwt8" in namespace "provisioning-5333"
Jun 13 00:28:41.825: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-xwt8" to be fully deleted
STEP: Deleting pod
Jun 13 00:28:51.886: INFO: Deleting pod "pod-subpath-test-dynamicpv-xwt8" in namespace "provisioning-5333"
STEP: Deleting pvc
Jun 13 00:28:51.973: INFO: Deleting PersistentVolumeClaim "awsjjflp"
... skipping 16 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.8OXTe6tDm/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.8OXTe6tDm/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if non-existent subpath is outside the volume [Slow][LinuxOnly]
      /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 13 00:29:22.325: INFO: Driver "ebs.csi.aws.com" does not support volume type "InlineVolume" - skipping
[AfterEach] [Testpattern: Inline-volume (default fs)] subPath
... skipping 92 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 13 00:28:54.850: INFO: >>> kubeConfig: /root/.kube/config
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]
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 13 00:28:55.003: INFO: Creating resource for dynamic PV
Jun 13 00:28:55.003: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-8738-e2e-sclzt2b
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 13 00:29:01.223: INFO: Deleting pod "pod-ad41f307-3b12-4778-acec-30efd271ad87" in namespace "volumemode-8738"
Jun 13 00:29:01.255: INFO: Wait up to 5m0s for pod "pod-ad41f307-3b12-4778-acec-30efd271ad87" to be fully deleted
STEP: Deleting pvc
Jun 13 00:29:13.377: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comsjm7j"
Jun 13 00:29:13.409: INFO: Waiting up to 5m0s for PersistentVolume pvc-1cb67346-2adf-409d-8291-b09e65521453 to get deleted
Jun 13 00:29:13.442: INFO: PersistentVolume pvc-1cb67346-2adf-409d-8291-b09e65521453 found and phase=Bound (33.44933ms)
... skipping 8 lines ...

• [SLOW TEST:28.750 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail to use a volume in a pod with mismatched mode [Slow]
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 107 lines ...
Jun 13 00:28:39.216: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4605bxvbb
STEP: creating a claim
Jun 13 00:28:39.246: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-jqzx
STEP: Creating a pod to test subpath
Jun 13 00:28:39.335: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-jqzx" in namespace "provisioning-4605" to be "Succeeded or Failed"
Jun 13 00:28:39.363: INFO: Pod "pod-subpath-test-dynamicpv-jqzx": Phase="Pending", Reason="", readiness=false. Elapsed: 28.726775ms
Jun 13 00:28:41.396: INFO: Pod "pod-subpath-test-dynamicpv-jqzx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061737871s
Jun 13 00:28:43.427: INFO: Pod "pod-subpath-test-dynamicpv-jqzx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.092466803s
Jun 13 00:28:45.458: INFO: Pod "pod-subpath-test-dynamicpv-jqzx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.123228875s
Jun 13 00:28:47.488: INFO: Pod "pod-subpath-test-dynamicpv-jqzx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.153522558s
Jun 13 00:28:49.524: INFO: Pod "pod-subpath-test-dynamicpv-jqzx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.189708298s
Jun 13 00:28:51.554: INFO: Pod "pod-subpath-test-dynamicpv-jqzx": Phase="Pending", Reason="", readiness=false. Elapsed: 12.21974602s
Jun 13 00:28:53.584: INFO: Pod "pod-subpath-test-dynamicpv-jqzx": Phase="Pending", Reason="", readiness=false. Elapsed: 14.249362597s
Jun 13 00:28:55.614: INFO: Pod "pod-subpath-test-dynamicpv-jqzx": Phase="Pending", Reason="", readiness=false. Elapsed: 16.279016506s
Jun 13 00:28:57.646: INFO: Pod "pod-subpath-test-dynamicpv-jqzx": Phase="Pending", Reason="", readiness=false. Elapsed: 18.311786655s
Jun 13 00:28:59.676: INFO: Pod "pod-subpath-test-dynamicpv-jqzx": Phase="Pending", Reason="", readiness=false. Elapsed: 20.341558395s
Jun 13 00:29:01.705: INFO: Pod "pod-subpath-test-dynamicpv-jqzx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.370636005s
STEP: Saw pod success
Jun 13 00:29:01.705: INFO: Pod "pod-subpath-test-dynamicpv-jqzx" satisfied condition "Succeeded or Failed"
Jun 13 00:29:01.738: INFO: Trying to get logs from node ip-172-20-44-97.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-jqzx container test-container-subpath-dynamicpv-jqzx: <nil>
STEP: delete the pod
Jun 13 00:29:01.809: INFO: Waiting for pod pod-subpath-test-dynamicpv-jqzx to disappear
Jun 13 00:29:01.837: INFO: Pod pod-subpath-test-dynamicpv-jqzx no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-jqzx
Jun 13 00:29:01.837: INFO: Deleting pod "pod-subpath-test-dynamicpv-jqzx" in namespace "provisioning-4605"
... skipping 255 lines ...
Jun 13 00:27:15.157: INFO: Creating resource for dynamic PV
Jun 13 00:27:15.157: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-2456-e2e-sc4l7tt
STEP: creating a claim
Jun 13 00:27:15.189: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 13 00:27:15.282: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-mr58k" in namespace "snapshotting-2456" to be "Succeeded or Failed"
Jun 13 00:27:15.313: INFO: Pod "pvc-snapshottable-tester-mr58k": Phase="Pending", Reason="", readiness=false. Elapsed: 30.210192ms
Jun 13 00:27:17.343: INFO: Pod "pvc-snapshottable-tester-mr58k": Phase="Pending", Reason="", readiness=false. Elapsed: 2.06102033s
Jun 13 00:27:19.374: INFO: Pod "pvc-snapshottable-tester-mr58k": Phase="Pending", Reason="", readiness=false. Elapsed: 4.091936288s
Jun 13 00:27:21.407: INFO: Pod "pvc-snapshottable-tester-mr58k": Phase="Pending", Reason="", readiness=false. Elapsed: 6.125108245s
Jun 13 00:27:23.439: INFO: Pod "pvc-snapshottable-tester-mr58k": Phase="Pending", Reason="", readiness=false. Elapsed: 8.156234583s
Jun 13 00:27:25.470: INFO: Pod "pvc-snapshottable-tester-mr58k": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.187144049s
STEP: Saw pod success
Jun 13 00:27:25.470: INFO: Pod "pvc-snapshottable-tester-mr58k" satisfied condition "Succeeded or Failed"
Jun 13 00:27:25.532: INFO: Pod pvc-snapshottable-tester-mr58k has the following logs: 
Jun 13 00:27:25.532: INFO: Deleting pod "pvc-snapshottable-tester-mr58k" in namespace "snapshotting-2456"
Jun 13 00:27:25.567: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-mr58k" to be fully deleted
Jun 13 00:27:25.597: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comcjwnk] to have phase Bound
Jun 13 00:27:25.628: INFO: PersistentVolumeClaim ebs.csi.aws.comcjwnk found and phase=Bound (30.752545ms)
STEP: [init] checking the claim
... skipping 32 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:243
STEP: checking the snapshot
STEP: checking the SnapshotContent
STEP: Modifying source data test
STEP: modifying the data in the source PVC
Jun 13 00:28:10.704: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-2khhb" in namespace "snapshotting-2456" to be "Succeeded or Failed"
Jun 13 00:28:10.735: INFO: Pod "pvc-snapshottable-data-tester-2khhb": Phase="Pending", Reason="", readiness=false. Elapsed: 30.888633ms
Jun 13 00:28:12.765: INFO: Pod "pvc-snapshottable-data-tester-2khhb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061331377s
Jun 13 00:28:14.798: INFO: Pod "pvc-snapshottable-data-tester-2khhb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.094429841s
Jun 13 00:28:16.829: INFO: Pod "pvc-snapshottable-data-tester-2khhb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.124822997s
Jun 13 00:28:18.860: INFO: Pod "pvc-snapshottable-data-tester-2khhb": Phase="Pending", Reason="", readiness=false. Elapsed: 8.156324199s
Jun 13 00:28:20.892: INFO: Pod "pvc-snapshottable-data-tester-2khhb": Phase="Pending", Reason="", readiness=false. Elapsed: 10.187994234s
Jun 13 00:28:22.924: INFO: Pod "pvc-snapshottable-data-tester-2khhb": Phase="Pending", Reason="", readiness=false. Elapsed: 12.220326639s
Jun 13 00:28:24.958: INFO: Pod "pvc-snapshottable-data-tester-2khhb": Phase="Pending", Reason="", readiness=false. Elapsed: 14.254254032s
Jun 13 00:28:26.990: INFO: Pod "pvc-snapshottable-data-tester-2khhb": Phase="Pending", Reason="", readiness=false. Elapsed: 16.286124274s
Jun 13 00:28:29.022: INFO: Pod "pvc-snapshottable-data-tester-2khhb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.317502724s
STEP: Saw pod success
Jun 13 00:28:29.022: INFO: Pod "pvc-snapshottable-data-tester-2khhb" satisfied condition "Succeeded or Failed"
Jun 13 00:28:29.084: INFO: Pod pvc-snapshottable-data-tester-2khhb has the following logs: 
Jun 13 00:28:29.084: INFO: Deleting pod "pvc-snapshottable-data-tester-2khhb" in namespace "snapshotting-2456"
Jun 13 00:28:29.120: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-2khhb" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 13 00:28:51.273: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-2456 exec restored-pvc-tester-58jlp --namespace=snapshotting-2456 -- cat /mnt/test/data'
... skipping 266 lines ...
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:108
      
      /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:225
        should check snapshot fields, check restore correctly works after modifying source data, check deletion [It]
        /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:243

        Unexpected error:
            <exec.CodeExitError>: {
                Err: {
                    s: "error running /usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-2456 exec restored-pvc-tester-58jlp --namespace=snapshotting-2456 -- cat /mnt/test/data:\nCommand stdout:\n\nstderr:\ncat: can't open '/mnt/test/data': No such file or directory\ncommand terminated with exit code 1\n\nerror:\nexit status 1",
                },
                Code: 1,
            }
            error running /usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-2456 exec restored-pvc-tester-58jlp --namespace=snapshotting-2456 -- cat /mnt/test/data:
            Command stdout:
            
            stderr:
            cat: can't open '/mnt/test/data': No such file or directory
            command terminated with exit code 1
            
            error:
            exit status 1
        occurred

        /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:602
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volume-stress
... skipping 74 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath file is outside the volume [Slow][LinuxOnly] [BeforeEach]
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

    Driver "ebs.csi.aws.com" does not support volume type "PreprovisionedPV" - skipping

    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 12 lines ...
Jun 13 00:27:33.705: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-1024-e2e-sc2gb8b      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:*WaitForFirstConsumer,AllowedTopologies:[]TopologySelectorTerm{},}, pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-1024    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:*provisioning-1024-e2e-sc2gb8b,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-1024    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:*provisioning-1024-e2e-sc2gb8b,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-1024    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:*provisioning-1024-e2e-sc2gb8b,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-1024-e2e-sc2gb8b    096ecf52-29a2-4573-aed2-4fcae753275e 10622 0 2021-06-13 00:27:33 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-13 00:27:33 +0000 UTC FieldsV1 {"f:mountOptions":{},"f:provisioner":{},"f:reclaimPolicy":{},"f:volumeBindingMode":{}}}]},Provisioner:ebs.csi.aws.com,Parameters:map[string]string{},ReclaimPolicy:*Delete,MountOptions:[dirsync],AllowVolumeExpansion:nil,VolumeBindingMode:*WaitForFirstConsumer,AllowedTopologies:[]TopologySelectorTerm{},} claim=&PersistentVolumeClaim{ObjectMeta:{pvc-ls22w pvc- provisioning-1024  436684d2-4029-491f-abf0-3f739b114984 10625 0 2021-06-13 00:27:33 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-13 00:27:33 +0000 UTC FieldsV1 {"f:metadata":{"f:generateName":{}},"f:spec":{"f:accessModes":{},"f:resources":{"f:requests":{".":{},"f:storage":{}}},"f:storageClassName":{},"f:volumeMode":{}}}}]},Spec:PersistentVolumeClaimSpec{AccessModes:[ReadWriteOnce],Resources:ResourceRequirements{Limits:ResourceList{},Requests:ResourceList{storage: {{1073741824 0} {<nil>} 1Gi BinarySI},},},VolumeName:,Selector:nil,StorageClassName:*provisioning-1024-e2e-sc2gb8b,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-54c69f1f-51c4-4997-8b6e-5fcabf3458a9 in namespace provisioning-1024
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun 13 00:27:56.042: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-tckkk" in namespace "provisioning-1024" to be "Succeeded or Failed"
Jun 13 00:27:56.071: INFO: Pod "pvc-volume-tester-writer-tckkk": Phase="Pending", Reason="", readiness=false. Elapsed: 29.164388ms
Jun 13 00:27:58.104: INFO: Pod "pvc-volume-tester-writer-tckkk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062023127s
Jun 13 00:28:00.135: INFO: Pod "pvc-volume-tester-writer-tckkk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.092780885s
Jun 13 00:28:02.165: INFO: Pod "pvc-volume-tester-writer-tckkk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.122588931s
Jun 13 00:28:04.195: INFO: Pod "pvc-volume-tester-writer-tckkk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.153189414s
Jun 13 00:28:06.226: INFO: Pod "pvc-volume-tester-writer-tckkk": Phase="Pending", Reason="", readiness=false. Elapsed: 10.183427407s
... skipping 23 lines ...
Jun 13 00:28:54.949: INFO: Pod "pvc-volume-tester-writer-tckkk": Phase="Pending", Reason="", readiness=false. Elapsed: 58.906567845s
Jun 13 00:28:56.979: INFO: Pod "pvc-volume-tester-writer-tckkk": Phase="Pending", Reason="", readiness=false. Elapsed: 1m0.937059842s
Jun 13 00:28:59.009: INFO: Pod "pvc-volume-tester-writer-tckkk": Phase="Pending", Reason="", readiness=false. Elapsed: 1m2.966521776s
Jun 13 00:29:01.039: INFO: Pod "pvc-volume-tester-writer-tckkk": Phase="Pending", Reason="", readiness=false. Elapsed: 1m4.997130505s
Jun 13 00:29:03.069: INFO: Pod "pvc-volume-tester-writer-tckkk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m7.026413499s
STEP: Saw pod success
Jun 13 00:29:03.069: INFO: Pod "pvc-volume-tester-writer-tckkk" satisfied condition "Succeeded or Failed"
Jun 13 00:29:03.128: INFO: Pod pvc-volume-tester-writer-tckkk has the following logs: 
Jun 13 00:29:03.128: INFO: Deleting pod "pvc-volume-tester-writer-tckkk" in namespace "provisioning-1024"
Jun 13 00:29:03.162: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-tckkk" to be fully deleted
STEP: checking the created volume has the correct mount options, is readable and retains data on the same node "ip-172-20-56-187.us-east-2.compute.internal"
Jun 13 00:29:03.282: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-bqp7m" in namespace "provisioning-1024" to be "Succeeded or Failed"
Jun 13 00:29:03.311: INFO: Pod "pvc-volume-tester-reader-bqp7m": Phase="Pending", Reason="", readiness=false. Elapsed: 29.347335ms
Jun 13 00:29:05.341: INFO: Pod "pvc-volume-tester-reader-bqp7m": Phase="Pending", Reason="", readiness=false. Elapsed: 2.058956297s
Jun 13 00:29:07.370: INFO: Pod "pvc-volume-tester-reader-bqp7m": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.088498966s
STEP: Saw pod success
Jun 13 00:29:07.371: INFO: Pod "pvc-volume-tester-reader-bqp7m" satisfied condition "Succeeded or Failed"
Jun 13 00:29:07.430: INFO: Pod pvc-volume-tester-reader-bqp7m has the following logs: hello world

Jun 13 00:29:07.430: INFO: Deleting pod "pvc-volume-tester-reader-bqp7m" in namespace "provisioning-1024"
Jun 13 00:29:07.466: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-bqp7m" to be fully deleted
Jun 13 00:29:07.495: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-ls22w] to have phase Bound
Jun 13 00:29:07.524: INFO: PersistentVolumeClaim pvc-ls22w found and phase=Bound (28.769814ms)
... skipping 156 lines ...
Jun 13 00:29:33.792: INFO: Waiting for pod aws-client to disappear
Jun 13 00:29:33.822: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 13 00:29:33.822: INFO: Deleting PersistentVolumeClaim "pvc-b4fmw"
Jun 13 00:29:33.855: INFO: Deleting PersistentVolume "aws-k55qz"
Jun 13 00:29:34.154: INFO: Couldn't delete PD "aws://us-east-2a/vol-0f93579f7fdded1ae", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f93579f7fdded1ae is currently attached to i-014c8052d1f18bb5f
	status code: 400, request id: 55728ed3-f6d7-42d3-9ce7-82f7e8562401
Jun 13 00:29:39.412: INFO: Couldn't delete PD "aws://us-east-2a/vol-0f93579f7fdded1ae", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f93579f7fdded1ae is currently attached to i-014c8052d1f18bb5f
	status code: 400, request id: e0448760-616d-4a4d-8b05-842f0314e279
Jun 13 00:29:44.688: INFO: Successfully deleted PD "aws://us-east-2a/vol-0f93579f7fdded1ae".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 13 00:29:44.689: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-9760" for this suite.
... skipping 24 lines ...
Jun 13 00:28:49.779: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-62949xrcj
STEP: creating a claim
Jun 13 00:28:49.809: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-w7qn
STEP: Creating a pod to test atomic-volume-subpath
Jun 13 00:28:49.902: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-w7qn" in namespace "provisioning-6294" to be "Succeeded or Failed"
Jun 13 00:28:49.931: INFO: Pod "pod-subpath-test-dynamicpv-w7qn": Phase="Pending", Reason="", readiness=false. Elapsed: 29.743279ms
Jun 13 00:28:51.962: INFO: Pod "pod-subpath-test-dynamicpv-w7qn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.060719495s
Jun 13 00:28:53.994: INFO: Pod "pod-subpath-test-dynamicpv-w7qn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.092583265s
Jun 13 00:28:56.024: INFO: Pod "pod-subpath-test-dynamicpv-w7qn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.122702128s
Jun 13 00:28:58.054: INFO: Pod "pod-subpath-test-dynamicpv-w7qn": Phase="Pending", Reason="", readiness=false. Elapsed: 8.152594448s
Jun 13 00:29:00.087: INFO: Pod "pod-subpath-test-dynamicpv-w7qn": Phase="Pending", Reason="", readiness=false. Elapsed: 10.185253861s
... skipping 12 lines ...
Jun 13 00:29:26.493: INFO: Pod "pod-subpath-test-dynamicpv-w7qn": Phase="Running", Reason="", readiness=true. Elapsed: 36.591666117s
Jun 13 00:29:28.523: INFO: Pod "pod-subpath-test-dynamicpv-w7qn": Phase="Running", Reason="", readiness=true. Elapsed: 38.621711133s
Jun 13 00:29:30.554: INFO: Pod "pod-subpath-test-dynamicpv-w7qn": Phase="Running", Reason="", readiness=true. Elapsed: 40.652771875s
Jun 13 00:29:32.586: INFO: Pod "pod-subpath-test-dynamicpv-w7qn": Phase="Running", Reason="", readiness=true. Elapsed: 42.684213017s
Jun 13 00:29:34.617: INFO: Pod "pod-subpath-test-dynamicpv-w7qn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 44.715548361s
STEP: Saw pod success
Jun 13 00:29:34.617: INFO: Pod "pod-subpath-test-dynamicpv-w7qn" satisfied condition "Succeeded or Failed"
Jun 13 00:29:34.647: INFO: Trying to get logs from node ip-172-20-58-40.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-w7qn container test-container-subpath-dynamicpv-w7qn: <nil>
STEP: delete the pod
Jun 13 00:29:34.714: INFO: Waiting for pod pod-subpath-test-dynamicpv-w7qn to disappear
Jun 13 00:29:34.743: INFO: Pod pod-subpath-test-dynamicpv-w7qn no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-w7qn
Jun 13 00:29:34.743: INFO: Deleting pod "pod-subpath-test-dynamicpv-w7qn" in namespace "provisioning-6294"
... skipping 37 lines ...
Jun 13 00:29:22.998: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5216-e2e-sc5kj8k
STEP: creating a claim
Jun 13 00:29:23.033: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-9gzh
STEP: Creating a pod to test subpath
Jun 13 00:29:23.126: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-9gzh" in namespace "provisioning-5216" to be "Succeeded or Failed"
Jun 13 00:29:23.154: INFO: Pod "pod-subpath-test-dynamicpv-9gzh": Phase="Pending", Reason="", readiness=false. Elapsed: 28.573115ms
Jun 13 00:29:25.187: INFO: Pod "pod-subpath-test-dynamicpv-9gzh": Phase="Pending", Reason="", readiness=false. Elapsed: 2.06104663s
Jun 13 00:29:27.217: INFO: Pod "pod-subpath-test-dynamicpv-9gzh": Phase="Pending", Reason="", readiness=false. Elapsed: 4.091470464s
Jun 13 00:29:29.248: INFO: Pod "pod-subpath-test-dynamicpv-9gzh": Phase="Pending", Reason="", readiness=false. Elapsed: 6.122038439s
Jun 13 00:29:31.279: INFO: Pod "pod-subpath-test-dynamicpv-9gzh": Phase="Pending", Reason="", readiness=false. Elapsed: 8.15309825s
Jun 13 00:29:33.310: INFO: Pod "pod-subpath-test-dynamicpv-9gzh": Phase="Pending", Reason="", readiness=false. Elapsed: 10.184028532s
Jun 13 00:29:35.339: INFO: Pod "pod-subpath-test-dynamicpv-9gzh": Phase="Pending", Reason="", readiness=false. Elapsed: 12.21302422s
Jun 13 00:29:37.375: INFO: Pod "pod-subpath-test-dynamicpv-9gzh": Phase="Pending", Reason="", readiness=false. Elapsed: 14.249463451s
Jun 13 00:29:39.404: INFO: Pod "pod-subpath-test-dynamicpv-9gzh": Phase="Pending", Reason="", readiness=false. Elapsed: 16.278502373s
Jun 13 00:29:41.443: INFO: Pod "pod-subpath-test-dynamicpv-9gzh": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.317140997s
STEP: Saw pod success
Jun 13 00:29:41.443: INFO: Pod "pod-subpath-test-dynamicpv-9gzh" satisfied condition "Succeeded or Failed"
Jun 13 00:29:41.473: INFO: Trying to get logs from node ip-172-20-44-97.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-9gzh container test-container-volume-dynamicpv-9gzh: <nil>
STEP: delete the pod
Jun 13 00:29:41.571: INFO: Waiting for pod pod-subpath-test-dynamicpv-9gzh to disappear
Jun 13 00:29:41.600: INFO: Pod pod-subpath-test-dynamicpv-9gzh no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-9gzh
Jun 13 00:29:41.600: INFO: Deleting pod "pod-subpath-test-dynamicpv-9gzh" in namespace "provisioning-5216"
... skipping 35 lines ...
Jun 13 00:28:39.070: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 13 00:28:39.493: INFO: Successfully created a new PD: "aws://us-east-2a/vol-0ba063861cbd1a043".
Jun 13 00:28:39.493: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-p7gg
STEP: Creating a pod to test exec-volume-test
Jun 13 00:28:39.526: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-p7gg" in namespace "volume-9623" to be "Succeeded or Failed"
Jun 13 00:28:39.556: INFO: Pod "exec-volume-test-inlinevolume-p7gg": Phase="Pending", Reason="", readiness=false. Elapsed: 29.963807ms
Jun 13 00:28:41.587: INFO: Pod "exec-volume-test-inlinevolume-p7gg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061197429s
Jun 13 00:28:43.620: INFO: Pod "exec-volume-test-inlinevolume-p7gg": Phase="Pending", Reason="", readiness=false. Elapsed: 4.093994289s
Jun 13 00:28:45.656: INFO: Pod "exec-volume-test-inlinevolume-p7gg": Phase="Pending", Reason="", readiness=false. Elapsed: 6.12981254s
Jun 13 00:28:47.687: INFO: Pod "exec-volume-test-inlinevolume-p7gg": Phase="Pending", Reason="", readiness=false. Elapsed: 8.161080706s
Jun 13 00:28:49.719: INFO: Pod "exec-volume-test-inlinevolume-p7gg": Phase="Pending", Reason="", readiness=false. Elapsed: 10.192829735s
... skipping 24 lines ...
Jun 13 00:29:40.518: INFO: Pod "exec-volume-test-inlinevolume-p7gg": Phase="Pending", Reason="", readiness=false. Elapsed: 1m0.99206099s
Jun 13 00:29:42.549: INFO: Pod "exec-volume-test-inlinevolume-p7gg": Phase="Pending", Reason="", readiness=false. Elapsed: 1m3.023115882s
Jun 13 00:29:44.580: INFO: Pod "exec-volume-test-inlinevolume-p7gg": Phase="Pending", Reason="", readiness=false. Elapsed: 1m5.054499223s
Jun 13 00:29:46.614: INFO: Pod "exec-volume-test-inlinevolume-p7gg": Phase="Pending", Reason="", readiness=false. Elapsed: 1m7.088321172s
Jun 13 00:29:48.644: INFO: Pod "exec-volume-test-inlinevolume-p7gg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m9.118566136s
STEP: Saw pod success
Jun 13 00:29:48.644: INFO: Pod "exec-volume-test-inlinevolume-p7gg" satisfied condition "Succeeded or Failed"
Jun 13 00:29:48.675: INFO: Trying to get logs from node ip-172-20-32-240.us-east-2.compute.internal pod exec-volume-test-inlinevolume-p7gg container exec-container-inlinevolume-p7gg: <nil>
STEP: delete the pod
Jun 13 00:29:48.746: INFO: Waiting for pod exec-volume-test-inlinevolume-p7gg to disappear
Jun 13 00:29:48.776: INFO: Pod exec-volume-test-inlinevolume-p7gg no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-p7gg
Jun 13 00:29:48.776: INFO: Deleting pod "exec-volume-test-inlinevolume-p7gg" in namespace "volume-9623"
Jun 13 00:29:49.050: INFO: Couldn't delete PD "aws://us-east-2a/vol-0ba063861cbd1a043", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ba063861cbd1a043 is currently attached to i-014c8052d1f18bb5f
	status code: 400, request id: c68093bf-749d-4a3c-9686-00620effc47f
Jun 13 00:29:54.301: INFO: Couldn't delete PD "aws://us-east-2a/vol-0ba063861cbd1a043", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ba063861cbd1a043 is currently attached to i-014c8052d1f18bb5f
	status code: 400, request id: 24c959db-9256-4b69-b472-f568f49def7a
Jun 13 00:29:59.553: INFO: Couldn't delete PD "aws://us-east-2a/vol-0ba063861cbd1a043", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ba063861cbd1a043 is currently attached to i-014c8052d1f18bb5f
	status code: 400, request id: a50b09b4-8b4a-484c-b956-c6be629d8bb8
Jun 13 00:30:04.830: INFO: Successfully deleted PD "aws://us-east-2a/vol-0ba063861cbd1a043".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 13 00:30:04.830: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-9623" for this suite.
... skipping 111 lines ...
Jun 13 00:29:22.477: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-9875-e2e-scjmlzm
STEP: creating a claim
Jun 13 00:29:22.507: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-j4kq
STEP: Creating a pod to test exec-volume-test
Jun 13 00:29:22.596: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-j4kq" in namespace "volume-9875" to be "Succeeded or Failed"
Jun 13 00:29:22.627: INFO: Pod "exec-volume-test-dynamicpv-j4kq": Phase="Pending", Reason="", readiness=false. Elapsed: 30.170519ms
Jun 13 00:29:24.657: INFO: Pod "exec-volume-test-dynamicpv-j4kq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.060891937s
Jun 13 00:29:26.688: INFO: Pod "exec-volume-test-dynamicpv-j4kq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.091390233s
Jun 13 00:29:28.719: INFO: Pod "exec-volume-test-dynamicpv-j4kq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.122018134s
Jun 13 00:29:30.749: INFO: Pod "exec-volume-test-dynamicpv-j4kq": Phase="Pending", Reason="", readiness=false. Elapsed: 8.152880831s
Jun 13 00:29:32.779: INFO: Pod "exec-volume-test-dynamicpv-j4kq": Phase="Pending", Reason="", readiness=false. Elapsed: 10.182415201s
Jun 13 00:29:34.808: INFO: Pod "exec-volume-test-dynamicpv-j4kq": Phase="Pending", Reason="", readiness=false. Elapsed: 12.21169335s
Jun 13 00:29:36.838: INFO: Pod "exec-volume-test-dynamicpv-j4kq": Phase="Pending", Reason="", readiness=false. Elapsed: 14.241346608s
Jun 13 00:29:38.868: INFO: Pod "exec-volume-test-dynamicpv-j4kq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.271265995s
STEP: Saw pod success
Jun 13 00:29:38.868: INFO: Pod "exec-volume-test-dynamicpv-j4kq" satisfied condition "Succeeded or Failed"
Jun 13 00:29:38.897: INFO: Trying to get logs from node ip-172-20-58-40.us-east-2.compute.internal pod exec-volume-test-dynamicpv-j4kq container exec-container-dynamicpv-j4kq: <nil>
STEP: delete the pod
Jun 13 00:29:38.961: INFO: Waiting for pod exec-volume-test-dynamicpv-j4kq to disappear
Jun 13 00:29:38.991: INFO: Pod exec-volume-test-dynamicpv-j4kq no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-j4kq
Jun 13 00:29:38.991: INFO: Deleting pod "exec-volume-test-dynamicpv-j4kq" in namespace "volume-9875"
... skipping 38 lines ...
Jun 13 00:29:25.384: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3272kqkbn
STEP: creating a claim
Jun 13 00:29:25.414: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-9277
STEP: Creating a pod to test subpath
Jun 13 00:29:25.520: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-9277" in namespace "provisioning-3272" to be "Succeeded or Failed"
Jun 13 00:29:25.550: INFO: Pod "pod-subpath-test-dynamicpv-9277": Phase="Pending", Reason="", readiness=false. Elapsed: 29.89281ms
Jun 13 00:29:27.581: INFO: Pod "pod-subpath-test-dynamicpv-9277": Phase="Pending", Reason="", readiness=false. Elapsed: 2.060951934s
Jun 13 00:29:29.611: INFO: Pod "pod-subpath-test-dynamicpv-9277": Phase="Pending", Reason="", readiness=false. Elapsed: 4.09137993s
Jun 13 00:29:31.646: INFO: Pod "pod-subpath-test-dynamicpv-9277": Phase="Pending", Reason="", readiness=false. Elapsed: 6.12576163s
Jun 13 00:29:33.676: INFO: Pod "pod-subpath-test-dynamicpv-9277": Phase="Pending", Reason="", readiness=false. Elapsed: 8.155974124s
Jun 13 00:29:35.711: INFO: Pod "pod-subpath-test-dynamicpv-9277": Phase="Pending", Reason="", readiness=false. Elapsed: 10.191679819s
Jun 13 00:29:37.742: INFO: Pod "pod-subpath-test-dynamicpv-9277": Phase="Pending", Reason="", readiness=false. Elapsed: 12.22190206s
Jun 13 00:29:39.773: INFO: Pod "pod-subpath-test-dynamicpv-9277": Phase="Pending", Reason="", readiness=false. Elapsed: 14.253214579s
Jun 13 00:29:41.817: INFO: Pod "pod-subpath-test-dynamicpv-9277": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.296910968s
STEP: Saw pod success
Jun 13 00:29:41.817: INFO: Pod "pod-subpath-test-dynamicpv-9277" satisfied condition "Succeeded or Failed"
Jun 13 00:29:41.847: INFO: Trying to get logs from node ip-172-20-56-187.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-9277 container test-container-volume-dynamicpv-9277: <nil>
STEP: delete the pod
Jun 13 00:29:41.918: INFO: Waiting for pod pod-subpath-test-dynamicpv-9277 to disappear
Jun 13 00:29:41.947: INFO: Pod pod-subpath-test-dynamicpv-9277 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-9277
Jun 13 00:29:41.948: INFO: Deleting pod "pod-subpath-test-dynamicpv-9277" in namespace "provisioning-3272"
... skipping 402 lines ...
Jun 13 00:29:41.863: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-6556-e2e-scxsllx
STEP: creating a claim
Jun 13 00:29:41.895: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-2qzj
STEP: Creating a pod to test exec-volume-test
Jun 13 00:29:41.991: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-2qzj" in namespace "volume-6556" to be "Succeeded or Failed"
Jun 13 00:29:42.021: INFO: Pod "exec-volume-test-dynamicpv-2qzj": Phase="Pending", Reason="", readiness=false. Elapsed: 29.955756ms
Jun 13 00:29:44.052: INFO: Pod "exec-volume-test-dynamicpv-2qzj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.060816916s
Jun 13 00:29:46.083: INFO: Pod "exec-volume-test-dynamicpv-2qzj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.09222003s
Jun 13 00:29:48.114: INFO: Pod "exec-volume-test-dynamicpv-2qzj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.12329703s
Jun 13 00:29:50.146: INFO: Pod "exec-volume-test-dynamicpv-2qzj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.154577442s
Jun 13 00:29:52.176: INFO: Pod "exec-volume-test-dynamicpv-2qzj": Phase="Pending", Reason="", readiness=false. Elapsed: 10.185171072s
Jun 13 00:29:54.207: INFO: Pod "exec-volume-test-dynamicpv-2qzj": Phase="Pending", Reason="", readiness=false. Elapsed: 12.215760202s
Jun 13 00:29:56.239: INFO: Pod "exec-volume-test-dynamicpv-2qzj": Phase="Pending", Reason="", readiness=false. Elapsed: 14.247627301s
Jun 13 00:29:58.270: INFO: Pod "exec-volume-test-dynamicpv-2qzj": Phase="Pending", Reason="", readiness=false. Elapsed: 16.278595452s
Jun 13 00:30:00.300: INFO: Pod "exec-volume-test-dynamicpv-2qzj": Phase="Pending", Reason="", readiness=false. Elapsed: 18.309354998s
Jun 13 00:30:02.333: INFO: Pod "exec-volume-test-dynamicpv-2qzj": Phase="Pending", Reason="", readiness=false. Elapsed: 20.34177919s
Jun 13 00:30:04.364: INFO: Pod "exec-volume-test-dynamicpv-2qzj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.373313448s
STEP: Saw pod success
Jun 13 00:30:04.364: INFO: Pod "exec-volume-test-dynamicpv-2qzj" satisfied condition "Succeeded or Failed"
Jun 13 00:30:04.396: INFO: Trying to get logs from node ip-172-20-56-187.us-east-2.compute.internal pod exec-volume-test-dynamicpv-2qzj container exec-container-dynamicpv-2qzj: <nil>
STEP: delete the pod
Jun 13 00:30:04.469: INFO: Waiting for pod exec-volume-test-dynamicpv-2qzj to disappear
Jun 13 00:30:04.499: INFO: Pod exec-volume-test-dynamicpv-2qzj no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-2qzj
Jun 13 00:30:04.499: INFO: Deleting pod "exec-volume-test-dynamicpv-2qzj" in namespace "volume-6556"
... skipping 149 lines ...
Jun 13 00:30:40.090: INFO: Pod aws-client still exists
Jun 13 00:30:42.061: INFO: Waiting for pod aws-client to disappear
Jun 13 00:30:42.092: INFO: Pod aws-client still exists
Jun 13 00:30:44.060: INFO: Waiting for pod aws-client to disappear
Jun 13 00:30:44.090: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun 13 00:30:44.307: INFO: Couldn't delete PD "aws://us-east-2a/vol-08e0dc1d19361962f", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08e0dc1d19361962f is currently attached to i-008e8334048ae093c
	status code: 400, request id: 8f229cc2-b0be-4553-b097-340ac84f8f87
Jun 13 00:30:49.559: INFO: Successfully deleted PD "aws://us-east-2a/vol-08e0dc1d19361962f".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 13 00:30:49.559: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-4623" for this suite.
... skipping 863 lines ...
    /tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volume_expand.go:174
------------------------------


Summarizing 2 Failures:

[Fail] External Storage [Driver: ebs.csi.aws.com] [Testpattern: Pre-provisioned Snapshot (delete policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller  [It] should check snapshot fields, check restore correctly works after modifying source data, check deletion 
/tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:602

[Fail] External Storage [Driver: ebs.csi.aws.com] [Testpattern: Dynamic Snapshot (retain policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller  [It] should check snapshot fields, check restore correctly works after modifying source data, check deletion 
/tmp/kops.8OXTe6tDm/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:602

Ran 141 of 485 Specs in 653.191 seconds
FAIL! -- 139 Passed | 2 Failed | 0 Pending | 344 Skipped


Ginkgo ran 1 suite in 12m50.363661231s
Test Suite Failed
+ kops-finish
+ kubetest2 kops -v=2 --cloud-provider=aws --cluster-name=e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --admin-access= --kops-binary-path=/home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops --down
I0613 00:33:16.980058   32378 app.go:59] RunDir for this run: "/logs/artifacts/1ef2fd0c-cbdb-11eb-ab6f-62c732df09e9"
I0613 00:33:16.980336   32378 app.go:90] ID for this run: "1ef2fd0c-cbdb-11eb-ab6f-62c732df09e9"
I0613 00:33:16.980407   32378 dumplogs.go:38] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops toolbox dump --name e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ubuntu
I0613 00:33:17.006595   32384 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
... skipping 1469 lines ...