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

No Test Failures!


Error lines from build-log.txt

... skipping 492 lines ...
I0612 00:13:50.223278   11763 up.go:43] Cleaning up any leaked resources from previous cluster
I0612 00:13:50.223294   11763 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
I0612 00:13:50.238456   11770 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0612 00:13:50.238566   11770 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io" not found
W0612 00:13:50.715046   11763 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0612 00:13:50.715220   11763 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
I0612 00:13:50.731617   11781 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0612 00:13:50.731719   11781 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io" not found
I0612 00:13:51.196854   11763 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/06/12 00:13:51 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
I0612 00:13:51.205592   11763 http.go:37] curl https://ip.jsb.workers.dev
I0612 00:13:51.341172   11763 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 35.223.168.202/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones us-east-2a --master-size c5.large
I0612 00:13:51.357683   11795 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0612 00:13:51.358474   11795 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I0612 00:13:51.401401   11795 create_cluster.go:728] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0612 00:13:51.871563   11795 new_cluster.go:1039]  Cloud Provider ID = aws
... skipping 40 lines ...

I0612 00:14:15.969527   11763 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
I0612 00:14:15.985005   11816 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0612 00:14:15.985388   11816 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io

W0612 00:14:16.958366   11816 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
W0612 00:14:26.989023   11816 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
W0612 00:14:37.019064   11816 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
W0612 00:14:47.090753   11816 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
W0612 00:14:57.136018   11816 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
W0612 00:15:07.167798   11816 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
W0612 00:15:17.201881   11816 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
W0612 00:15:27.233138   11816 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
W0612 00:15:37.264495   11816 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
W0612 00:15:47.297129   11816 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
W0612 00:15:57.340067   11816 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
W0612 00:16:07.374349   11816 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
W0612 00:16:17.407882   11816 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
W0612 00:16:27.436652   11816 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
W0612 00:16:37.482606   11816 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
W0612 00:16:47.512571   11816 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
W0612 00:16:57.545657   11816 validate_cluster.go:221] (will retry): cluster not yet healthy
W0612 00:17:07.583291   11816 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
W0612 00:17:17.612233   11816 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
W0612 00:17:27.642405   11816 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
W0612 00:17:37.670464   11816 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
W0612 00:17:47.717303   11816 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
W0612 00:17:57.760225   11816 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
W0612 00:18:07.808128   11816 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
W0612 00:18:17.846799   11816 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
W0612 00:18:27.892511   11816 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
W0612 00:18:37.922248   11816 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
W0612 00:18:47.958835   11816 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
W0612 00:18:57.986398   11816 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
W0612 00:19:08.019877   11816 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
W0612 00:19:18.055747   11816 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
W0612 00:19:28.085339   11816 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
W0612 00:19:38.144148   11816 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
W0612 00:19:48.176268   11816 validate_cluster.go:221] (will retry): cluster not yet healthy
W0612 00:20:28.205862   11816 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 203.0.113.123:443: i/o timeout
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
... skipping 6 lines ...

VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-node-xm54m				system-node-critical pod "calico-node-xm54m" is not ready (calico-node)
Pod	kube-system/cert-manager-webhook-7bbf67968-cd7wq	system-cluster-critical pod "cert-manager-webhook-7bbf67968-cd7wq" is not ready (cert-manager)

Validation Failed
W0612 00:20:39.524758   11816 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 271 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.mVCl1cIaj/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.mVCl1cIaj/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.mVCl1cIaj/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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 204 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.mVCl1cIaj/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.mVCl1cIaj/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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 8 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.mVCl1cIaj/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.mVCl1cIaj/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.mVCl1cIaj/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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 362 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.mVCl1cIaj/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.mVCl1cIaj/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.mVCl1cIaj/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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 120 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.mVCl1cIaj/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.mVCl1cIaj/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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 12 lines ...
Jun 12 00:23:53.803: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 12 00:23:54.244: INFO: Successfully created a new PD: "aws://us-east-2a/vol-0cfb0551b9f9e44d2".
Jun 12 00:23:54.244: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-xn5k
STEP: Creating a pod to test exec-volume-test
Jun 12 00:23:54.279: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-xn5k" in namespace "volume-57" to be "Succeeded or Failed"
Jun 12 00:23:54.309: INFO: Pod "exec-volume-test-inlinevolume-xn5k": Phase="Pending", Reason="", readiness=false. Elapsed: 30.005153ms
Jun 12 00:23:56.340: INFO: Pod "exec-volume-test-inlinevolume-xn5k": Phase="Pending", Reason="", readiness=false. Elapsed: 2.060759819s
Jun 12 00:23:58.371: INFO: Pod "exec-volume-test-inlinevolume-xn5k": Phase="Pending", Reason="", readiness=false. Elapsed: 4.092452945s
Jun 12 00:24:00.403: INFO: Pod "exec-volume-test-inlinevolume-xn5k": Phase="Pending", Reason="", readiness=false. Elapsed: 6.124017968s
Jun 12 00:24:02.434: INFO: Pod "exec-volume-test-inlinevolume-xn5k": Phase="Pending", Reason="", readiness=false. Elapsed: 8.154946254s
Jun 12 00:24:04.465: INFO: Pod "exec-volume-test-inlinevolume-xn5k": Phase="Pending", Reason="", readiness=false. Elapsed: 10.18571009s
Jun 12 00:24:06.496: INFO: Pod "exec-volume-test-inlinevolume-xn5k": Phase="Pending", Reason="", readiness=false. Elapsed: 12.217382162s
Jun 12 00:24:08.527: INFO: Pod "exec-volume-test-inlinevolume-xn5k": Phase="Pending", Reason="", readiness=false. Elapsed: 14.248076394s
Jun 12 00:24:10.558: INFO: Pod "exec-volume-test-inlinevolume-xn5k": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.278788617s
STEP: Saw pod success
Jun 12 00:24:10.558: INFO: Pod "exec-volume-test-inlinevolume-xn5k" satisfied condition "Succeeded or Failed"
Jun 12 00:24:10.588: INFO: Trying to get logs from node ip-172-20-36-179.us-east-2.compute.internal pod exec-volume-test-inlinevolume-xn5k container exec-container-inlinevolume-xn5k: <nil>
STEP: delete the pod
Jun 12 00:24:11.354: INFO: Waiting for pod exec-volume-test-inlinevolume-xn5k to disappear
Jun 12 00:24:11.384: INFO: Pod exec-volume-test-inlinevolume-xn5k no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-xn5k
Jun 12 00:24:11.384: INFO: Deleting pod "exec-volume-test-inlinevolume-xn5k" in namespace "volume-57"
Jun 12 00:24:11.536: INFO: Couldn't delete PD "aws://us-east-2a/vol-0cfb0551b9f9e44d2", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0cfb0551b9f9e44d2 is currently attached to i-040c2d8c38b7aa7c4
	status code: 400, request id: 07384132-2486-44a1-b347-7c6a52af8cdd
Jun 12 00:24:16.774: INFO: Couldn't delete PD "aws://us-east-2a/vol-0cfb0551b9f9e44d2", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0cfb0551b9f9e44d2 is currently attached to i-040c2d8c38b7aa7c4
	status code: 400, request id: ef45d6f1-08f8-418a-8915-8b44784a6914
Jun 12 00:24:22.019: INFO: Couldn't delete PD "aws://us-east-2a/vol-0cfb0551b9f9e44d2", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0cfb0551b9f9e44d2 is currently attached to i-040c2d8c38b7aa7c4
	status code: 400, request id: 15c3dcb3-49c4-42e1-a4a7-33a2e7a3e7bc
Jun 12 00:24:27.289: INFO: Successfully deleted PD "aws://us-east-2a/vol-0cfb0551b9f9e44d2".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 00:24:27.289: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-57" for this suite.
... skipping 18 lines ...

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

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

    /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:92
------------------------------
... skipping 2 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 12 00:23:53.663: 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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 12 00:23:54.848: INFO: Creating resource for dynamic PV
Jun 12 00:23:54.848: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-5069-e2e-sc9vgn6
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 12 00:24:03.065: INFO: Deleting pod "pod-82984fd9-ba7e-4b19-ae27-bb876575bdcf" in namespace "volumemode-5069"
Jun 12 00:24:03.098: INFO: Wait up to 5m0s for pod "pod-82984fd9-ba7e-4b19-ae27-bb876575bdcf" to be fully deleted
STEP: Deleting pvc
Jun 12 00:24:13.216: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comps46s"
Jun 12 00:24:13.252: INFO: Waiting up to 5m0s for PersistentVolume pvc-4f5c6b6e-6046-45d1-b474-456a8b2812dd to get deleted
Jun 12 00:24:13.284: INFO: PersistentVolume pvc-4f5c6b6e-6046-45d1-b474-456a8b2812dd found and phase=Released (32.05212ms)
... skipping 10 lines ...

• [SLOW TEST:39.837 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.mVCl1cIaj/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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 38 lines ...
STEP: Deleting pod hostexec-ip-172-20-36-179.us-east-2.compute.internal-dlnz8 in namespace volumemode-4506
Jun 12 00:24:19.906: INFO: Deleting pod "pod-0131f813-9667-4ac6-b2be-404d3d61a83b" in namespace "volumemode-4506"
Jun 12 00:24:19.942: INFO: Wait up to 5m0s for pod "pod-0131f813-9667-4ac6-b2be-404d3d61a83b" to be fully deleted
STEP: Deleting pv and pvc
Jun 12 00:24:28.002: INFO: Deleting PersistentVolumeClaim "pvc-vtp7r"
Jun 12 00:24:28.033: INFO: Deleting PersistentVolume "aws-5p8sv"
Jun 12 00:24:28.190: INFO: Couldn't delete PD "aws://us-east-2a/vol-0ff692328647becbd", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ff692328647becbd is currently attached to i-040c2d8c38b7aa7c4
	status code: 400, request id: ddcfa03b-2f1f-49c0-928a-1b259db6601e
Jun 12 00:24:33.468: INFO: Successfully deleted PD "aws://us-east-2a/vol-0ff692328647becbd".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 00:24:33.468: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-4506" for this suite.
... skipping 71 lines ...
Jun 12 00:24:33.778: INFO: AfterEach: Cleaning up test resources


S [SKIPPING] in Spec Setup (BeforeEach) [0.217 seconds]
[sig-storage] PersistentVolumes:vsphere [Feature:vsphere]
/tmp/kops.mVCl1cIaj/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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:148

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 13 lines ...
Jun 12 00:23:55.615: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4813-e2e-sc7f8b2
STEP: creating a claim
Jun 12 00:23:55.646: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-nsmk
STEP: Creating a pod to test subpath
Jun 12 00:23:55.742: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-nsmk" in namespace "provisioning-4813" to be "Succeeded or Failed"
Jun 12 00:23:55.772: INFO: Pod "pod-subpath-test-dynamicpv-nsmk": Phase="Pending", Reason="", readiness=false. Elapsed: 30.091793ms
Jun 12 00:23:57.804: INFO: Pod "pod-subpath-test-dynamicpv-nsmk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.06169767s
Jun 12 00:23:59.837: INFO: Pod "pod-subpath-test-dynamicpv-nsmk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.095124437s
Jun 12 00:24:01.870: INFO: Pod "pod-subpath-test-dynamicpv-nsmk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.127790251s
Jun 12 00:24:03.901: INFO: Pod "pod-subpath-test-dynamicpv-nsmk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.15826966s
Jun 12 00:24:05.931: INFO: Pod "pod-subpath-test-dynamicpv-nsmk": Phase="Pending", Reason="", readiness=false. Elapsed: 10.188994875s
Jun 12 00:24:07.962: INFO: Pod "pod-subpath-test-dynamicpv-nsmk": Phase="Pending", Reason="", readiness=false. Elapsed: 12.219341196s
Jun 12 00:24:09.993: INFO: Pod "pod-subpath-test-dynamicpv-nsmk": Phase="Pending", Reason="", readiness=false. Elapsed: 14.250743049s
Jun 12 00:24:12.024: INFO: Pod "pod-subpath-test-dynamicpv-nsmk": Phase="Pending", Reason="", readiness=false. Elapsed: 16.281390691s
Jun 12 00:24:14.055: INFO: Pod "pod-subpath-test-dynamicpv-nsmk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.312594048s
STEP: Saw pod success
Jun 12 00:24:14.055: INFO: Pod "pod-subpath-test-dynamicpv-nsmk" satisfied condition "Succeeded or Failed"
Jun 12 00:24:14.085: INFO: Trying to get logs from node ip-172-20-56-193.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-nsmk container test-container-volume-dynamicpv-nsmk: <nil>
STEP: delete the pod
Jun 12 00:24:14.177: INFO: Waiting for pod pod-subpath-test-dynamicpv-nsmk to disappear
Jun 12 00:24:14.207: INFO: Pod pod-subpath-test-dynamicpv-nsmk no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-nsmk
Jun 12 00:24:14.207: INFO: Deleting pod "pod-subpath-test-dynamicpv-nsmk" in namespace "provisioning-4813"
... skipping 275 lines ...
Jun 12 00:23:56.012: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-6194-e2e-sctswcd
STEP: creating a claim
Jun 12 00:23:56.043: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-2rvl
STEP: Creating a pod to test exec-volume-test
Jun 12 00:23:56.142: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-2rvl" in namespace "volume-6194" to be "Succeeded or Failed"
Jun 12 00:23:56.174: INFO: Pod "exec-volume-test-dynamicpv-2rvl": Phase="Pending", Reason="", readiness=false. Elapsed: 31.601737ms
Jun 12 00:23:58.203: INFO: Pod "exec-volume-test-dynamicpv-2rvl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061159213s
Jun 12 00:24:00.233: INFO: Pod "exec-volume-test-dynamicpv-2rvl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.090928333s
Jun 12 00:24:02.263: INFO: Pod "exec-volume-test-dynamicpv-2rvl": Phase="Pending", Reason="", readiness=false. Elapsed: 6.120771542s
Jun 12 00:24:04.294: INFO: Pod "exec-volume-test-dynamicpv-2rvl": Phase="Pending", Reason="", readiness=false. Elapsed: 8.151216578s
Jun 12 00:24:06.323: INFO: Pod "exec-volume-test-dynamicpv-2rvl": Phase="Pending", Reason="", readiness=false. Elapsed: 10.180889784s
Jun 12 00:24:08.353: INFO: Pod "exec-volume-test-dynamicpv-2rvl": Phase="Pending", Reason="", readiness=false. Elapsed: 12.210592457s
Jun 12 00:24:10.383: INFO: Pod "exec-volume-test-dynamicpv-2rvl": Phase="Pending", Reason="", readiness=false. Elapsed: 14.240440182s
Jun 12 00:24:12.413: INFO: Pod "exec-volume-test-dynamicpv-2rvl": Phase="Pending", Reason="", readiness=false. Elapsed: 16.270606431s
Jun 12 00:24:14.443: INFO: Pod "exec-volume-test-dynamicpv-2rvl": Phase="Pending", Reason="", readiness=false. Elapsed: 18.300489814s
Jun 12 00:24:16.473: INFO: Pod "exec-volume-test-dynamicpv-2rvl": Phase="Pending", Reason="", readiness=false. Elapsed: 20.330504171s
Jun 12 00:24:18.509: INFO: Pod "exec-volume-test-dynamicpv-2rvl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.366573987s
STEP: Saw pod success
Jun 12 00:24:18.509: INFO: Pod "exec-volume-test-dynamicpv-2rvl" satisfied condition "Succeeded or Failed"
Jun 12 00:24:18.538: INFO: Trying to get logs from node ip-172-20-54-191.us-east-2.compute.internal pod exec-volume-test-dynamicpv-2rvl container exec-container-dynamicpv-2rvl: <nil>
STEP: delete the pod
Jun 12 00:24:18.613: INFO: Waiting for pod exec-volume-test-dynamicpv-2rvl to disappear
Jun 12 00:24:18.642: INFO: Pod exec-volume-test-dynamicpv-2rvl no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-2rvl
Jun 12 00:24:18.642: INFO: Deleting pod "exec-volume-test-dynamicpv-2rvl" in namespace "volume-6194"
... skipping 119 lines ...
Jun 12 00:23:56.789: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8422zdnmc
STEP: creating a claim
Jun 12 00:23:56.821: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-x89m
STEP: Creating a pod to test multi_subpath
Jun 12 00:23:56.916: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-x89m" in namespace "provisioning-8422" to be "Succeeded or Failed"
Jun 12 00:23:56.947: INFO: Pod "pod-subpath-test-dynamicpv-x89m": Phase="Pending", Reason="", readiness=false. Elapsed: 30.429143ms
Jun 12 00:23:58.979: INFO: Pod "pod-subpath-test-dynamicpv-x89m": Phase="Pending", Reason="", readiness=false. Elapsed: 2.063209168s
Jun 12 00:24:01.011: INFO: Pod "pod-subpath-test-dynamicpv-x89m": Phase="Pending", Reason="", readiness=false. Elapsed: 4.094778011s
Jun 12 00:24:03.043: INFO: Pod "pod-subpath-test-dynamicpv-x89m": Phase="Pending", Reason="", readiness=false. Elapsed: 6.126403163s
Jun 12 00:24:05.074: INFO: Pod "pod-subpath-test-dynamicpv-x89m": Phase="Pending", Reason="", readiness=false. Elapsed: 8.157859451s
Jun 12 00:24:07.106: INFO: Pod "pod-subpath-test-dynamicpv-x89m": Phase="Pending", Reason="", readiness=false. Elapsed: 10.189528128s
Jun 12 00:24:09.137: INFO: Pod "pod-subpath-test-dynamicpv-x89m": Phase="Pending", Reason="", readiness=false. Elapsed: 12.220911985s
Jun 12 00:24:11.169: INFO: Pod "pod-subpath-test-dynamicpv-x89m": Phase="Pending", Reason="", readiness=false. Elapsed: 14.25287172s
Jun 12 00:24:13.200: INFO: Pod "pod-subpath-test-dynamicpv-x89m": Phase="Pending", Reason="", readiness=false. Elapsed: 16.28382292s
Jun 12 00:24:15.232: INFO: Pod "pod-subpath-test-dynamicpv-x89m": Phase="Pending", Reason="", readiness=false. Elapsed: 18.315602976s
Jun 12 00:24:17.263: INFO: Pod "pod-subpath-test-dynamicpv-x89m": Phase="Pending", Reason="", readiness=false. Elapsed: 20.346904565s
Jun 12 00:24:19.301: INFO: Pod "pod-subpath-test-dynamicpv-x89m": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.384429393s
STEP: Saw pod success
Jun 12 00:24:19.301: INFO: Pod "pod-subpath-test-dynamicpv-x89m" satisfied condition "Succeeded or Failed"
Jun 12 00:24:19.337: INFO: Trying to get logs from node ip-172-20-36-179.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-x89m container test-container-subpath-dynamicpv-x89m: <nil>
STEP: delete the pod
Jun 12 00:24:19.421: INFO: Waiting for pod pod-subpath-test-dynamicpv-x89m to disappear
Jun 12 00:24:19.453: INFO: Pod pod-subpath-test-dynamicpv-x89m no longer exists
STEP: Deleting pod
Jun 12 00:24:19.453: INFO: Deleting pod "pod-subpath-test-dynamicpv-x89m" in namespace "provisioning-8422"
... skipping 134 lines ...
Jun 12 00:23:56.035: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5777-e2e-sck7dm9
STEP: creating a claim
Jun 12 00:23:56.067: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-4ttz
STEP: Creating a pod to test multi_subpath
Jun 12 00:23:56.162: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-4ttz" in namespace "provisioning-5777" to be "Succeeded or Failed"
Jun 12 00:23:56.192: INFO: Pod "pod-subpath-test-dynamicpv-4ttz": Phase="Pending", Reason="", readiness=false. Elapsed: 29.486203ms
Jun 12 00:23:58.223: INFO: Pod "pod-subpath-test-dynamicpv-4ttz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.060746258s
Jun 12 00:24:00.254: INFO: Pod "pod-subpath-test-dynamicpv-4ttz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.091851487s
Jun 12 00:24:02.286: INFO: Pod "pod-subpath-test-dynamicpv-4ttz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.123186436s
Jun 12 00:24:04.317: INFO: Pod "pod-subpath-test-dynamicpv-4ttz": Phase="Pending", Reason="", readiness=false. Elapsed: 8.154207648s
Jun 12 00:24:06.348: INFO: Pod "pod-subpath-test-dynamicpv-4ttz": Phase="Pending", Reason="", readiness=false. Elapsed: 10.185518725s
... skipping 6 lines ...
Jun 12 00:24:20.565: INFO: Pod "pod-subpath-test-dynamicpv-4ttz": Phase="Pending", Reason="", readiness=false. Elapsed: 24.402009312s
Jun 12 00:24:22.595: INFO: Pod "pod-subpath-test-dynamicpv-4ttz": Phase="Pending", Reason="", readiness=false. Elapsed: 26.432908371s
Jun 12 00:24:24.626: INFO: Pod "pod-subpath-test-dynamicpv-4ttz": Phase="Pending", Reason="", readiness=false. Elapsed: 28.463472846s
Jun 12 00:24:26.657: INFO: Pod "pod-subpath-test-dynamicpv-4ttz": Phase="Pending", Reason="", readiness=false. Elapsed: 30.494197444s
Jun 12 00:24:28.687: INFO: Pod "pod-subpath-test-dynamicpv-4ttz": Phase="Succeeded", Reason="", readiness=false. Elapsed: 32.524664265s
STEP: Saw pod success
Jun 12 00:24:28.687: INFO: Pod "pod-subpath-test-dynamicpv-4ttz" satisfied condition "Succeeded or Failed"
Jun 12 00:24:28.717: INFO: Trying to get logs from node ip-172-20-56-132.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-4ttz container test-container-subpath-dynamicpv-4ttz: <nil>
STEP: delete the pod
Jun 12 00:24:28.789: INFO: Waiting for pod pod-subpath-test-dynamicpv-4ttz to disappear
Jun 12 00:24:28.819: INFO: Pod pod-subpath-test-dynamicpv-4ttz no longer exists
STEP: Deleting pod
Jun 12 00:24:28.819: INFO: Deleting pod "pod-subpath-test-dynamicpv-4ttz" in namespace "provisioning-5777"
... skipping 100 lines ...
Jun 12 00:23:54.117: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-5767n6rmd
STEP: creating a claim
Jun 12 00:23:54.147: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-rzm8
STEP: Creating a pod to test exec-volume-test
Jun 12 00:23:54.240: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-rzm8" in namespace "volume-5767" to be "Succeeded or Failed"
Jun 12 00:23:54.270: INFO: Pod "exec-volume-test-dynamicpv-rzm8": Phase="Pending", Reason="", readiness=false. Elapsed: 29.997779ms
Jun 12 00:23:56.301: INFO: Pod "exec-volume-test-dynamicpv-rzm8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061025808s
Jun 12 00:23:58.333: INFO: Pod "exec-volume-test-dynamicpv-rzm8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.092972449s
Jun 12 00:24:00.365: INFO: Pod "exec-volume-test-dynamicpv-rzm8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.124801478s
Jun 12 00:24:02.397: INFO: Pod "exec-volume-test-dynamicpv-rzm8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.156731083s
Jun 12 00:24:04.427: INFO: Pod "exec-volume-test-dynamicpv-rzm8": Phase="Pending", Reason="", readiness=false. Elapsed: 10.187286419s
... skipping 6 lines ...
Jun 12 00:24:18.650: INFO: Pod "exec-volume-test-dynamicpv-rzm8": Phase="Pending", Reason="", readiness=false. Elapsed: 24.40999568s
Jun 12 00:24:20.682: INFO: Pod "exec-volume-test-dynamicpv-rzm8": Phase="Pending", Reason="", readiness=false. Elapsed: 26.441706061s
Jun 12 00:24:22.713: INFO: Pod "exec-volume-test-dynamicpv-rzm8": Phase="Pending", Reason="", readiness=false. Elapsed: 28.472726578s
Jun 12 00:24:24.743: INFO: Pod "exec-volume-test-dynamicpv-rzm8": Phase="Pending", Reason="", readiness=false. Elapsed: 30.502970352s
Jun 12 00:24:26.774: INFO: Pod "exec-volume-test-dynamicpv-rzm8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 32.533875808s
STEP: Saw pod success
Jun 12 00:24:26.774: INFO: Pod "exec-volume-test-dynamicpv-rzm8" satisfied condition "Succeeded or Failed"
Jun 12 00:24:26.811: INFO: Trying to get logs from node ip-172-20-56-193.us-east-2.compute.internal pod exec-volume-test-dynamicpv-rzm8 container exec-container-dynamicpv-rzm8: <nil>
STEP: delete the pod
Jun 12 00:24:26.879: INFO: Waiting for pod exec-volume-test-dynamicpv-rzm8 to disappear
Jun 12 00:24:26.913: INFO: Pod exec-volume-test-dynamicpv-rzm8 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-rzm8
Jun 12 00:24:26.913: INFO: Deleting pod "exec-volume-test-dynamicpv-rzm8" in namespace "volume-5767"
... skipping 55 lines ...
STEP: Creating a kubernetes client
Jun 12 00:23:53.175: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename provisioning
W0612 00:23:53.399047   25683 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Jun 12 00:23:53.399: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun 12 00:23:53.458: INFO: Creating resource for dynamic PV
Jun 12 00:23:53.459: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4979-e2e-schjt6p
STEP: creating a claim
Jun 12 00:23:53.493: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-8lrz
STEP: Checking for subpath error in container status
Jun 12 00:24:21.665: INFO: Deleting pod "pod-subpath-test-dynamicpv-8lrz" in namespace "provisioning-4979"
Jun 12 00:24:21.701: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-8lrz" to be fully deleted
STEP: Deleting pod
Jun 12 00:24:33.765: INFO: Deleting pod "pod-subpath-test-dynamicpv-8lrz" in namespace "provisioning-4979"
STEP: Deleting pvc
Jun 12 00:24:33.859: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comjj9sw"
... skipping 12 lines ...

• [SLOW TEST:61.012 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath directory is outside the volume [Slow][LinuxOnly]
    /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 542 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.mVCl1cIaj/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.mVCl1cIaj/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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 269 lines ...
Jun 12 00:24:39.426: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 12 00:24:39.830: INFO: Successfully created a new PD: "aws://us-east-2a/vol-039e3d12ec7c90794".
Jun 12 00:24:39.830: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-vv4r
STEP: Creating a pod to test exec-volume-test
Jun 12 00:24:39.868: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-vv4r" in namespace "volume-6225" to be "Succeeded or Failed"
Jun 12 00:24:39.922: INFO: Pod "exec-volume-test-inlinevolume-vv4r": Phase="Pending", Reason="", readiness=false. Elapsed: 54.43509ms
Jun 12 00:24:41.952: INFO: Pod "exec-volume-test-inlinevolume-vv4r": Phase="Pending", Reason="", readiness=false. Elapsed: 2.084582665s
Jun 12 00:24:43.986: INFO: Pod "exec-volume-test-inlinevolume-vv4r": Phase="Pending", Reason="", readiness=false. Elapsed: 4.118082809s
Jun 12 00:24:46.017: INFO: Pod "exec-volume-test-inlinevolume-vv4r": Phase="Pending", Reason="", readiness=false. Elapsed: 6.149032838s
Jun 12 00:24:48.046: INFO: Pod "exec-volume-test-inlinevolume-vv4r": Phase="Pending", Reason="", readiness=false. Elapsed: 8.17870669s
Jun 12 00:24:50.077: INFO: Pod "exec-volume-test-inlinevolume-vv4r": Phase="Pending", Reason="", readiness=false. Elapsed: 10.209701304s
... skipping 7 lines ...
Jun 12 00:25:06.341: INFO: Pod "exec-volume-test-inlinevolume-vv4r": Phase="Pending", Reason="", readiness=false. Elapsed: 26.473722336s
Jun 12 00:25:08.371: INFO: Pod "exec-volume-test-inlinevolume-vv4r": Phase="Pending", Reason="", readiness=false. Elapsed: 28.503283535s
Jun 12 00:25:10.402: INFO: Pod "exec-volume-test-inlinevolume-vv4r": Phase="Pending", Reason="", readiness=false. Elapsed: 30.533963485s
Jun 12 00:25:12.432: INFO: Pod "exec-volume-test-inlinevolume-vv4r": Phase="Pending", Reason="", readiness=false. Elapsed: 32.563955449s
Jun 12 00:25:14.462: INFO: Pod "exec-volume-test-inlinevolume-vv4r": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.594004128s
STEP: Saw pod success
Jun 12 00:25:14.462: INFO: Pod "exec-volume-test-inlinevolume-vv4r" satisfied condition "Succeeded or Failed"
Jun 12 00:25:14.491: INFO: Trying to get logs from node ip-172-20-54-191.us-east-2.compute.internal pod exec-volume-test-inlinevolume-vv4r container exec-container-inlinevolume-vv4r: <nil>
STEP: delete the pod
Jun 12 00:25:14.556: INFO: Waiting for pod exec-volume-test-inlinevolume-vv4r to disappear
Jun 12 00:25:14.586: INFO: Pod exec-volume-test-inlinevolume-vv4r no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-vv4r
Jun 12 00:25:14.586: INFO: Deleting pod "exec-volume-test-inlinevolume-vv4r" in namespace "volume-6225"
Jun 12 00:25:14.761: INFO: Couldn't delete PD "aws://us-east-2a/vol-039e3d12ec7c90794", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-039e3d12ec7c90794 is currently attached to i-04c4a604524f7b63b
	status code: 400, request id: fa8d6910-63eb-4012-95e1-041ced4fb850
Jun 12 00:25:20.032: INFO: Couldn't delete PD "aws://us-east-2a/vol-039e3d12ec7c90794", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-039e3d12ec7c90794 is currently attached to i-04c4a604524f7b63b
	status code: 400, request id: e81205bd-442b-4668-98ab-5da33183f615
Jun 12 00:25:25.295: INFO: Couldn't delete PD "aws://us-east-2a/vol-039e3d12ec7c90794", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-039e3d12ec7c90794 is currently attached to i-04c4a604524f7b63b
	status code: 400, request id: 5044a1b6-979f-4da5-b832-fe19102318b3
Jun 12 00:25:30.540: INFO: Successfully deleted PD "aws://us-east-2a/vol-039e3d12ec7c90794".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 00:25:30.540: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-6225" for this suite.
... skipping 131 lines ...

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

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

    /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:92
------------------------------
... skipping 52 lines ...
Jun 12 00:23:54.469: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3035nllrc
STEP: creating a claim
Jun 12 00:23:54.500: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-n6td
STEP: Creating a pod to test subpath
Jun 12 00:23:54.596: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-n6td" in namespace "provisioning-3035" to be "Succeeded or Failed"
Jun 12 00:23:54.627: INFO: Pod "pod-subpath-test-dynamicpv-n6td": Phase="Pending", Reason="", readiness=false. Elapsed: 31.135363ms
Jun 12 00:23:56.659: INFO: Pod "pod-subpath-test-dynamicpv-n6td": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062535371s
Jun 12 00:23:58.690: INFO: Pod "pod-subpath-test-dynamicpv-n6td": Phase="Pending", Reason="", readiness=false. Elapsed: 4.094128373s
Jun 12 00:24:00.723: INFO: Pod "pod-subpath-test-dynamicpv-n6td": Phase="Pending", Reason="", readiness=false. Elapsed: 6.126459989s
Jun 12 00:24:02.755: INFO: Pod "pod-subpath-test-dynamicpv-n6td": Phase="Pending", Reason="", readiness=false. Elapsed: 8.159275924s
Jun 12 00:24:04.789: INFO: Pod "pod-subpath-test-dynamicpv-n6td": Phase="Pending", Reason="", readiness=false. Elapsed: 10.192738563s
... skipping 6 lines ...
Jun 12 00:24:19.016: INFO: Pod "pod-subpath-test-dynamicpv-n6td": Phase="Pending", Reason="", readiness=false. Elapsed: 24.420315842s
Jun 12 00:24:21.049: INFO: Pod "pod-subpath-test-dynamicpv-n6td": Phase="Pending", Reason="", readiness=false. Elapsed: 26.452799751s
Jun 12 00:24:23.081: INFO: Pod "pod-subpath-test-dynamicpv-n6td": Phase="Pending", Reason="", readiness=false. Elapsed: 28.485006541s
Jun 12 00:24:25.113: INFO: Pod "pod-subpath-test-dynamicpv-n6td": Phase="Pending", Reason="", readiness=false. Elapsed: 30.516347974s
Jun 12 00:24:27.144: INFO: Pod "pod-subpath-test-dynamicpv-n6td": Phase="Succeeded", Reason="", readiness=false. Elapsed: 32.548221895s
STEP: Saw pod success
Jun 12 00:24:27.144: INFO: Pod "pod-subpath-test-dynamicpv-n6td" satisfied condition "Succeeded or Failed"
Jun 12 00:24:27.175: INFO: Trying to get logs from node ip-172-20-54-191.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-n6td container test-container-subpath-dynamicpv-n6td: <nil>
STEP: delete the pod
Jun 12 00:24:27.248: INFO: Waiting for pod pod-subpath-test-dynamicpv-n6td to disappear
Jun 12 00:24:27.279: INFO: Pod pod-subpath-test-dynamicpv-n6td no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-n6td
Jun 12 00:24:27.279: INFO: Deleting pod "pod-subpath-test-dynamicpv-n6td" in namespace "provisioning-3035"
STEP: Creating pod pod-subpath-test-dynamicpv-n6td
STEP: Creating a pod to test subpath
Jun 12 00:24:27.348: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-n6td" in namespace "provisioning-3035" to be "Succeeded or Failed"
Jun 12 00:24:27.378: INFO: Pod "pod-subpath-test-dynamicpv-n6td": Phase="Pending", Reason="", readiness=false. Elapsed: 30.478812ms
Jun 12 00:24:29.410: INFO: Pod "pod-subpath-test-dynamicpv-n6td": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062312949s
Jun 12 00:24:31.443: INFO: Pod "pod-subpath-test-dynamicpv-n6td": Phase="Pending", Reason="", readiness=false. Elapsed: 4.094890781s
Jun 12 00:24:33.474: INFO: Pod "pod-subpath-test-dynamicpv-n6td": Phase="Pending", Reason="", readiness=false. Elapsed: 6.126135251s
Jun 12 00:24:35.506: INFO: Pod "pod-subpath-test-dynamicpv-n6td": Phase="Pending", Reason="", readiness=false. Elapsed: 8.158324907s
Jun 12 00:24:37.538: INFO: Pod "pod-subpath-test-dynamicpv-n6td": Phase="Pending", Reason="", readiness=false. Elapsed: 10.190349821s
... skipping 24 lines ...
Jun 12 00:25:28.347: INFO: Pod "pod-subpath-test-dynamicpv-n6td": Phase="Pending", Reason="", readiness=false. Elapsed: 1m0.998999619s
Jun 12 00:25:30.379: INFO: Pod "pod-subpath-test-dynamicpv-n6td": Phase="Pending", Reason="", readiness=false. Elapsed: 1m3.030787252s
Jun 12 00:25:32.413: INFO: Pod "pod-subpath-test-dynamicpv-n6td": Phase="Pending", Reason="", readiness=false. Elapsed: 1m5.064752281s
Jun 12 00:25:34.444: INFO: Pod "pod-subpath-test-dynamicpv-n6td": Phase="Pending", Reason="", readiness=false. Elapsed: 1m7.096055134s
Jun 12 00:25:36.476: INFO: Pod "pod-subpath-test-dynamicpv-n6td": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m9.128342413s
STEP: Saw pod success
Jun 12 00:25:36.476: INFO: Pod "pod-subpath-test-dynamicpv-n6td" satisfied condition "Succeeded or Failed"
Jun 12 00:25:36.507: INFO: Trying to get logs from node ip-172-20-56-193.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-n6td container test-container-subpath-dynamicpv-n6td: <nil>
STEP: delete the pod
Jun 12 00:25:36.585: INFO: Waiting for pod pod-subpath-test-dynamicpv-n6td to disappear
Jun 12 00:25:36.616: INFO: Pod pod-subpath-test-dynamicpv-n6td no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-n6td
Jun 12 00:25:36.616: INFO: Deleting pod "pod-subpath-test-dynamicpv-n6td" in namespace "provisioning-3035"
... skipping 68 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 12 00:25:30.828: 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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 12 00:25:30.976: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 12 00:25:30.976: INFO: Creating resource for dynamic PV
Jun 12 00:25:30.976: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-1133h7799
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 12 00:25:37.214: INFO: Deleting pod "pod-56821092-d2a1-4ff4-b934-29cfa113b5af" in namespace "volumemode-1133"
Jun 12 00:25:37.254: INFO: Wait up to 5m0s for pod "pod-56821092-d2a1-4ff4-b934-29cfa113b5af" to be fully deleted
STEP: Deleting pvc
Jun 12 00:25:47.376: INFO: Deleting PersistentVolumeClaim "aws4tfgh"
Jun 12 00:25:47.406: INFO: Waiting up to 5m0s for PersistentVolume pvc-63ae3185-21f7-42ca-8877-248a467ee5d2 to get deleted
Jun 12 00:25:47.435: INFO: PersistentVolume pvc-63ae3185-21f7-42ca-8877-248a467ee5d2 found and phase=Released (28.814436ms)
... skipping 9 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.mVCl1cIaj/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.mVCl1cIaj/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (block volmode)] volumeMode
    /tmp/kops.mVCl1cIaj/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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 615 lines ...
Jun 12 00:25:48.899: INFO: Pod aws-client still exists
Jun 12 00:25:50.869: INFO: Waiting for pod aws-client to disappear
Jun 12 00:25:50.899: INFO: Pod aws-client still exists
Jun 12 00:25:52.870: INFO: Waiting for pod aws-client to disappear
Jun 12 00:25:52.900: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun 12 00:25:53.190: INFO: Couldn't delete PD "aws://us-east-2a/vol-06a2d3feacf575d88", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-06a2d3feacf575d88 is currently attached to i-08052264bd3923f8c
	status code: 400, request id: 35fa6243-1809-4e10-8e52-644967b07602
Jun 12 00:25:58.431: INFO: Couldn't delete PD "aws://us-east-2a/vol-06a2d3feacf575d88", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-06a2d3feacf575d88 is currently attached to i-08052264bd3923f8c
	status code: 400, request id: 1234a775-e25e-4169-9d9a-fc4d55129f2b
Jun 12 00:26:03.669: INFO: Couldn't delete PD "aws://us-east-2a/vol-06a2d3feacf575d88", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-06a2d3feacf575d88 is currently attached to i-08052264bd3923f8c
	status code: 400, request id: 08281f30-fb0e-4c81-955c-6c841508f3c4
Jun 12 00:26:08.926: INFO: Couldn't delete PD "aws://us-east-2a/vol-06a2d3feacf575d88", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-06a2d3feacf575d88 is currently attached to i-08052264bd3923f8c
	status code: 400, request id: 8cd89518-0441-4a41-ad90-318a7a4f3a37
Jun 12 00:26:14.216: INFO: Successfully deleted PD "aws://us-east-2a/vol-06a2d3feacf575d88".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 00:26:14.216: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-3497" for this suite.
... skipping 95 lines ...
Jun 12 00:25:52.200: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-1805k4s5l
STEP: creating a claim
Jun 12 00:25:52.234: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-bzjv
STEP: Creating a pod to test exec-volume-test
Jun 12 00:25:52.335: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-bzjv" in namespace "volume-1805" to be "Succeeded or Failed"
Jun 12 00:25:52.366: INFO: Pod "exec-volume-test-dynamicpv-bzjv": Phase="Pending", Reason="", readiness=false. Elapsed: 30.935533ms
Jun 12 00:25:54.398: INFO: Pod "exec-volume-test-dynamicpv-bzjv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062718403s
Jun 12 00:25:56.430: INFO: Pod "exec-volume-test-dynamicpv-bzjv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.095389824s
Jun 12 00:25:58.462: INFO: Pod "exec-volume-test-dynamicpv-bzjv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.127271624s
Jun 12 00:26:00.493: INFO: Pod "exec-volume-test-dynamicpv-bzjv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.158627882s
Jun 12 00:26:02.526: INFO: Pod "exec-volume-test-dynamicpv-bzjv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.191096841s
Jun 12 00:26:04.558: INFO: Pod "exec-volume-test-dynamicpv-bzjv": Phase="Pending", Reason="", readiness=false. Elapsed: 12.223109163s
Jun 12 00:26:06.597: INFO: Pod "exec-volume-test-dynamicpv-bzjv": Phase="Pending", Reason="", readiness=false. Elapsed: 14.261688467s
Jun 12 00:26:08.632: INFO: Pod "exec-volume-test-dynamicpv-bzjv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.297262093s
STEP: Saw pod success
Jun 12 00:26:08.632: INFO: Pod "exec-volume-test-dynamicpv-bzjv" satisfied condition "Succeeded or Failed"
Jun 12 00:26:08.664: INFO: Trying to get logs from node ip-172-20-56-132.us-east-2.compute.internal pod exec-volume-test-dynamicpv-bzjv container exec-container-dynamicpv-bzjv: <nil>
STEP: delete the pod
Jun 12 00:26:08.744: INFO: Waiting for pod exec-volume-test-dynamicpv-bzjv to disappear
Jun 12 00:26:08.778: INFO: Pod exec-volume-test-dynamicpv-bzjv no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-bzjv
Jun 12 00:26:08.778: INFO: Deleting pod "exec-volume-test-dynamicpv-bzjv" in namespace "volume-1805"
... skipping 283 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.mVCl1cIaj/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.mVCl1cIaj/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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 355 lines ...
Jun 12 00:26:28.333: INFO: AfterEach: Cleaning up test resources


S [SKIPPING] in Spec Setup (BeforeEach) [0.219 seconds]
[sig-storage] PersistentVolumes:vsphere [Feature:vsphere]
/tmp/kops.mVCl1cIaj/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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:164

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 29 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.mVCl1cIaj/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.mVCl1cIaj/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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 350 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.mVCl1cIaj/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.mVCl1cIaj/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.mVCl1cIaj/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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 108 lines ...
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 12 00:26:38.555: 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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Jun 12 00:26:38.741: INFO: found topology map[topology.kubernetes.io/zone:us-east-2a]
Jun 12 00:26:38.741: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 12 00:26:38.741: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.mVCl1cIaj/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.mVCl1cIaj/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (immediate binding)] topology
    /tmp/kops.mVCl1cIaj/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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 15 lines ...
Jun 12 00:23:53.859: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-2836ds2j5      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-2836    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-2836ds2j5,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-2836    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-2836ds2j5,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-2836    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-2836ds2j5,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-2836ds2j5    c567a4a8-7a65-4cd2-9448-5677c202bce8 2187 0 2021-06-12 00:23:53 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-12 00:23:53 +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-2kzlh pvc- provisioning-2836  2ab0212d-d213-4abf-b993-6a2f9f7703f6 2206 0 2021-06-12 00:23:54 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-12 00:23:54 +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-2836ds2j5,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-f454bd53-b202-4c5a-9d19-d625ace4d329 in namespace provisioning-2836
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun 12 00:24:28.227: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-grhlh" in namespace "provisioning-2836" to be "Succeeded or Failed"
Jun 12 00:24:28.258: INFO: Pod "pvc-volume-tester-writer-grhlh": Phase="Pending", Reason="", readiness=false. Elapsed: 30.948087ms
Jun 12 00:24:30.289: INFO: Pod "pvc-volume-tester-writer-grhlh": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062041724s
Jun 12 00:24:32.320: INFO: Pod "pvc-volume-tester-writer-grhlh": Phase="Pending", Reason="", readiness=false. Elapsed: 4.093296675s
Jun 12 00:24:34.352: INFO: Pod "pvc-volume-tester-writer-grhlh": Phase="Pending", Reason="", readiness=false. Elapsed: 6.125091731s
Jun 12 00:24:36.384: INFO: Pod "pvc-volume-tester-writer-grhlh": Phase="Pending", Reason="", readiness=false. Elapsed: 8.157343929s
Jun 12 00:24:38.415: INFO: Pod "pvc-volume-tester-writer-grhlh": Phase="Pending", Reason="", readiness=false. Elapsed: 10.188112013s
... skipping 26 lines ...
Jun 12 00:25:33.311: INFO: Pod "pvc-volume-tester-writer-grhlh": Phase="Pending", Reason="", readiness=false. Elapsed: 1m5.083775169s
Jun 12 00:25:35.342: INFO: Pod "pvc-volume-tester-writer-grhlh": Phase="Pending", Reason="", readiness=false. Elapsed: 1m7.114760169s
Jun 12 00:25:37.373: INFO: Pod "pvc-volume-tester-writer-grhlh": Phase="Pending", Reason="", readiness=false. Elapsed: 1m9.146151353s
Jun 12 00:25:39.404: INFO: Pod "pvc-volume-tester-writer-grhlh": Phase="Pending", Reason="", readiness=false. Elapsed: 1m11.177286595s
Jun 12 00:25:41.436: INFO: Pod "pvc-volume-tester-writer-grhlh": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m13.208821689s
STEP: Saw pod success
Jun 12 00:25:41.436: INFO: Pod "pvc-volume-tester-writer-grhlh" satisfied condition "Succeeded or Failed"
Jun 12 00:25:41.499: INFO: Pod pvc-volume-tester-writer-grhlh has the following logs: 
Jun 12 00:25:41.499: INFO: Deleting pod "pvc-volume-tester-writer-grhlh" in namespace "provisioning-2836"
Jun 12 00:25:41.536: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-grhlh" 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-193.us-east-2.compute.internal"
Jun 12 00:25:41.667: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-7hqk5" in namespace "provisioning-2836" to be "Succeeded or Failed"
Jun 12 00:25:41.699: INFO: Pod "pvc-volume-tester-reader-7hqk5": Phase="Pending", Reason="", readiness=false. Elapsed: 30.830897ms
Jun 12 00:25:43.731: INFO: Pod "pvc-volume-tester-reader-7hqk5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.063195081s
Jun 12 00:25:45.764: INFO: Pod "pvc-volume-tester-reader-7hqk5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.095483072s
Jun 12 00:25:47.795: INFO: Pod "pvc-volume-tester-reader-7hqk5": Phase="Pending", Reason="", readiness=false. Elapsed: 6.127273157s
Jun 12 00:25:49.830: INFO: Pod "pvc-volume-tester-reader-7hqk5": Phase="Pending", Reason="", readiness=false. Elapsed: 8.162416431s
Jun 12 00:25:51.863: INFO: Pod "pvc-volume-tester-reader-7hqk5": Phase="Pending", Reason="", readiness=false. Elapsed: 10.194441036s
... skipping 8 lines ...
Jun 12 00:26:10.151: INFO: Pod "pvc-volume-tester-reader-7hqk5": Phase="Pending", Reason="", readiness=false. Elapsed: 28.483058231s
Jun 12 00:26:12.184: INFO: Pod "pvc-volume-tester-reader-7hqk5": Phase="Pending", Reason="", readiness=false. Elapsed: 30.516383345s
Jun 12 00:26:14.216: INFO: Pod "pvc-volume-tester-reader-7hqk5": Phase="Pending", Reason="", readiness=false. Elapsed: 32.547809074s
Jun 12 00:26:16.248: INFO: Pod "pvc-volume-tester-reader-7hqk5": Phase="Pending", Reason="", readiness=false. Elapsed: 34.580243109s
Jun 12 00:26:18.279: INFO: Pod "pvc-volume-tester-reader-7hqk5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 36.611212554s
STEP: Saw pod success
Jun 12 00:26:18.279: INFO: Pod "pvc-volume-tester-reader-7hqk5" satisfied condition "Succeeded or Failed"
Jun 12 00:26:18.343: INFO: Pod pvc-volume-tester-reader-7hqk5 has the following logs: hello world

Jun 12 00:26:18.343: INFO: Deleting pod "pvc-volume-tester-reader-7hqk5" in namespace "provisioning-2836"
Jun 12 00:26:18.380: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-7hqk5" to be fully deleted
Jun 12 00:26:18.410: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-2kzlh] to have phase Bound
Jun 12 00:26:18.441: INFO: PersistentVolumeClaim pvc-2kzlh found and phase=Bound (30.978951ms)
... skipping 41 lines ...
Jun 12 00:26:19.250: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4977wfsdr
STEP: creating a claim
Jun 12 00:26:19.281: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-rnnk
STEP: Creating a pod to test subpath
Jun 12 00:26:19.384: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-rnnk" in namespace "provisioning-4977" to be "Succeeded or Failed"
Jun 12 00:26:19.419: INFO: Pod "pod-subpath-test-dynamicpv-rnnk": Phase="Pending", Reason="", readiness=false. Elapsed: 34.538161ms
Jun 12 00:26:21.458: INFO: Pod "pod-subpath-test-dynamicpv-rnnk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.073334278s
Jun 12 00:26:23.491: INFO: Pod "pod-subpath-test-dynamicpv-rnnk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.106154185s
Jun 12 00:26:25.522: INFO: Pod "pod-subpath-test-dynamicpv-rnnk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.137516034s
Jun 12 00:26:27.554: INFO: Pod "pod-subpath-test-dynamicpv-rnnk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.169854123s
Jun 12 00:26:29.587: INFO: Pod "pod-subpath-test-dynamicpv-rnnk": Phase="Pending", Reason="", readiness=false. Elapsed: 10.202206295s
Jun 12 00:26:31.618: INFO: Pod "pod-subpath-test-dynamicpv-rnnk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.233514066s
STEP: Saw pod success
Jun 12 00:26:31.618: INFO: Pod "pod-subpath-test-dynamicpv-rnnk" satisfied condition "Succeeded or Failed"
Jun 12 00:26:31.649: INFO: Trying to get logs from node ip-172-20-36-179.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-rnnk container test-container-subpath-dynamicpv-rnnk: <nil>
STEP: delete the pod
Jun 12 00:26:31.739: INFO: Waiting for pod pod-subpath-test-dynamicpv-rnnk to disappear
Jun 12 00:26:31.770: INFO: Pod pod-subpath-test-dynamicpv-rnnk no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-rnnk
Jun 12 00:26:31.770: INFO: Deleting pod "pod-subpath-test-dynamicpv-rnnk" in namespace "provisioning-4977"
... skipping 410 lines ...
Jun 12 00:26:09.179: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-4789-e2e-scdjjmt
STEP: creating a claim
Jun 12 00:26:09.211: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-mbs9
STEP: Creating a pod to test exec-volume-test
Jun 12 00:26:09.307: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-mbs9" in namespace "volume-4789" to be "Succeeded or Failed"
Jun 12 00:26:09.338: INFO: Pod "exec-volume-test-dynamicpv-mbs9": Phase="Pending", Reason="", readiness=false. Elapsed: 30.56629ms
Jun 12 00:26:11.369: INFO: Pod "exec-volume-test-dynamicpv-mbs9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061807415s
Jun 12 00:26:13.400: INFO: Pod "exec-volume-test-dynamicpv-mbs9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.092790527s
Jun 12 00:26:15.433: INFO: Pod "exec-volume-test-dynamicpv-mbs9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.125434734s
Jun 12 00:26:17.469: INFO: Pod "exec-volume-test-dynamicpv-mbs9": Phase="Pending", Reason="", readiness=false. Elapsed: 8.161334804s
Jun 12 00:26:19.500: INFO: Pod "exec-volume-test-dynamicpv-mbs9": Phase="Pending", Reason="", readiness=false. Elapsed: 10.192464998s
... skipping 3 lines ...
Jun 12 00:26:27.637: INFO: Pod "exec-volume-test-dynamicpv-mbs9": Phase="Pending", Reason="", readiness=false. Elapsed: 18.329920199s
Jun 12 00:26:29.668: INFO: Pod "exec-volume-test-dynamicpv-mbs9": Phase="Pending", Reason="", readiness=false. Elapsed: 20.360833807s
Jun 12 00:26:31.699: INFO: Pod "exec-volume-test-dynamicpv-mbs9": Phase="Pending", Reason="", readiness=false. Elapsed: 22.391652695s
Jun 12 00:26:33.731: INFO: Pod "exec-volume-test-dynamicpv-mbs9": Phase="Pending", Reason="", readiness=false. Elapsed: 24.423471986s
Jun 12 00:26:35.762: INFO: Pod "exec-volume-test-dynamicpv-mbs9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.454344329s
STEP: Saw pod success
Jun 12 00:26:35.762: INFO: Pod "exec-volume-test-dynamicpv-mbs9" satisfied condition "Succeeded or Failed"
Jun 12 00:26:35.792: INFO: Trying to get logs from node ip-172-20-54-191.us-east-2.compute.internal pod exec-volume-test-dynamicpv-mbs9 container exec-container-dynamicpv-mbs9: <nil>
STEP: delete the pod
Jun 12 00:26:35.862: INFO: Waiting for pod exec-volume-test-dynamicpv-mbs9 to disappear
Jun 12 00:26:35.892: INFO: Pod exec-volume-test-dynamicpv-mbs9 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-mbs9
Jun 12 00:26:35.892: INFO: Deleting pod "exec-volume-test-dynamicpv-mbs9" in namespace "volume-4789"
... skipping 788 lines ...
Jun 12 00:26:38.996: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-9781-e2e-scczpcx
STEP: creating a claim
Jun 12 00:26:39.027: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Jun 12 00:26:39.095: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 12 00:26:39.165: INFO: Error updating pvc ebs.csi.aws.comgbksn: PersistentVolumeClaim "ebs.csi.aws.comgbksn" 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-9781-e2e-scczpcx",
  	... // 2 identical fields
  }

Jun 12 00:26:41.228: INFO: Error updating pvc ebs.csi.aws.comgbksn: PersistentVolumeClaim "ebs.csi.aws.comgbksn" 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-9781-e2e-scczpcx",
  	... // 2 identical fields
  }

Jun 12 00:26:43.228: INFO: Error updating pvc ebs.csi.aws.comgbksn: PersistentVolumeClaim "ebs.csi.aws.comgbksn" 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-9781-e2e-scczpcx",
  	... // 2 identical fields
  }

Jun 12 00:26:45.251: INFO: Error updating pvc ebs.csi.aws.comgbksn: PersistentVolumeClaim "ebs.csi.aws.comgbksn" 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-9781-e2e-scczpcx",
  	... // 2 identical fields
  }

Jun 12 00:26:47.228: INFO: Error updating pvc ebs.csi.aws.comgbksn: PersistentVolumeClaim "ebs.csi.aws.comgbksn" 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-9781-e2e-scczpcx",
  	... // 2 identical fields
  }

Jun 12 00:26:49.228: INFO: Error updating pvc ebs.csi.aws.comgbksn: PersistentVolumeClaim "ebs.csi.aws.comgbksn" 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-9781-e2e-scczpcx",
  	... // 2 identical fields
  }

Jun 12 00:26:51.228: INFO: Error updating pvc ebs.csi.aws.comgbksn: PersistentVolumeClaim "ebs.csi.aws.comgbksn" 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-9781-e2e-scczpcx",
  	... // 2 identical fields
  }

Jun 12 00:26:53.228: INFO: Error updating pvc ebs.csi.aws.comgbksn: PersistentVolumeClaim "ebs.csi.aws.comgbksn" 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-9781-e2e-scczpcx",
  	... // 2 identical fields
  }

Jun 12 00:26:55.228: INFO: Error updating pvc ebs.csi.aws.comgbksn: PersistentVolumeClaim "ebs.csi.aws.comgbksn" 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-9781-e2e-scczpcx",
  	... // 2 identical fields
  }

Jun 12 00:26:57.257: INFO: Error updating pvc ebs.csi.aws.comgbksn: PersistentVolumeClaim "ebs.csi.aws.comgbksn" 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-9781-e2e-scczpcx",
  	... // 2 identical fields
  }

Jun 12 00:26:59.261: INFO: Error updating pvc ebs.csi.aws.comgbksn: PersistentVolumeClaim "ebs.csi.aws.comgbksn" 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-9781-e2e-scczpcx",
  	... // 2 identical fields
  }

Jun 12 00:27:01.228: INFO: Error updating pvc ebs.csi.aws.comgbksn: PersistentVolumeClaim "ebs.csi.aws.comgbksn" 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-9781-e2e-scczpcx",
  	... // 2 identical fields
  }

Jun 12 00:27:03.228: INFO: Error updating pvc ebs.csi.aws.comgbksn: PersistentVolumeClaim "ebs.csi.aws.comgbksn" 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-9781-e2e-scczpcx",
  	... // 2 identical fields
  }

Jun 12 00:27:05.233: INFO: Error updating pvc ebs.csi.aws.comgbksn: PersistentVolumeClaim "ebs.csi.aws.comgbksn" 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-9781-e2e-scczpcx",
  	... // 2 identical fields
  }

Jun 12 00:27:07.231: INFO: Error updating pvc ebs.csi.aws.comgbksn: PersistentVolumeClaim "ebs.csi.aws.comgbksn" 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-9781-e2e-scczpcx",
  	... // 2 identical fields
  }

Jun 12 00:27:09.230: INFO: Error updating pvc ebs.csi.aws.comgbksn: PersistentVolumeClaim "ebs.csi.aws.comgbksn" 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-9781-e2e-scczpcx",
  	... // 2 identical fields
  }

Jun 12 00:27:09.292: INFO: Error updating pvc ebs.csi.aws.comgbksn: PersistentVolumeClaim "ebs.csi.aws.comgbksn" 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 40 lines ...
Jun 12 00:26:48.770: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-2340pvnx9
STEP: creating a claim
Jun 12 00:26:48.800: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Jun 12 00:26:48.862: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 12 00:26:48.930: INFO: Error updating pvc awsn8f8j: PersistentVolumeClaim "awsn8f8j" 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-2340pvnx9",
  	... // 2 identical fields
  }

Jun 12 00:26:50.995: INFO: Error updating pvc awsn8f8j: PersistentVolumeClaim "awsn8f8j" 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-2340pvnx9",
  	... // 2 identical fields
  }

Jun 12 00:26:52.991: INFO: Error updating pvc awsn8f8j: PersistentVolumeClaim "awsn8f8j" 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-2340pvnx9",
  	... // 2 identical fields
  }

Jun 12 00:26:54.993: INFO: Error updating pvc awsn8f8j: PersistentVolumeClaim "awsn8f8j" 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-2340pvnx9",
  	... // 2 identical fields
  }

Jun 12 00:26:56.994: INFO: Error updating pvc awsn8f8j: PersistentVolumeClaim "awsn8f8j" 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-2340pvnx9",
  	... // 2 identical fields
  }

Jun 12 00:26:58.995: INFO: Error updating pvc awsn8f8j: PersistentVolumeClaim "awsn8f8j" 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-2340pvnx9",
  	... // 2 identical fields
  }

Jun 12 00:27:00.992: INFO: Error updating pvc awsn8f8j: PersistentVolumeClaim "awsn8f8j" 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-2340pvnx9",
  	... // 2 identical fields
  }

Jun 12 00:27:02.995: INFO: Error updating pvc awsn8f8j: PersistentVolumeClaim "awsn8f8j" 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-2340pvnx9",
  	... // 2 identical fields
  }

Jun 12 00:27:04.992: INFO: Error updating pvc awsn8f8j: PersistentVolumeClaim "awsn8f8j" 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-2340pvnx9",
  	... // 2 identical fields
  }

Jun 12 00:27:06.996: INFO: Error updating pvc awsn8f8j: PersistentVolumeClaim "awsn8f8j" 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-2340pvnx9",
  	... // 2 identical fields
  }

Jun 12 00:27:08.993: INFO: Error updating pvc awsn8f8j: PersistentVolumeClaim "awsn8f8j" 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-2340pvnx9",
  	... // 2 identical fields
  }

Jun 12 00:27:10.991: INFO: Error updating pvc awsn8f8j: PersistentVolumeClaim "awsn8f8j" 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-2340pvnx9",
  	... // 2 identical fields
  }

Jun 12 00:27:12.991: INFO: Error updating pvc awsn8f8j: PersistentVolumeClaim "awsn8f8j" 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-2340pvnx9",
  	... // 2 identical fields
  }

Jun 12 00:27:14.990: INFO: Error updating pvc awsn8f8j: PersistentVolumeClaim "awsn8f8j" 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-2340pvnx9",
  	... // 2 identical fields
  }

Jun 12 00:27:16.992: INFO: Error updating pvc awsn8f8j: PersistentVolumeClaim "awsn8f8j" 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-2340pvnx9",
  	... // 2 identical fields
  }

Jun 12 00:27:18.992: INFO: Error updating pvc awsn8f8j: PersistentVolumeClaim "awsn8f8j" 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-2340pvnx9",
  	... // 2 identical fields
  }

Jun 12 00:27:19.057: INFO: Error updating pvc awsn8f8j: PersistentVolumeClaim "awsn8f8j" 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 140 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.mVCl1cIaj/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.mVCl1cIaj/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.mVCl1cIaj/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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 179 lines ...
Jun 12 00:26:33.255: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1901q54mt
STEP: creating a claim
Jun 12 00:26:33.290: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-gngw
STEP: Creating a pod to test subpath
Jun 12 00:26:33.426: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-gngw" in namespace "provisioning-1901" to be "Succeeded or Failed"
Jun 12 00:26:33.465: INFO: Pod "pod-subpath-test-dynamicpv-gngw": Phase="Pending", Reason="", readiness=false. Elapsed: 39.039983ms
Jun 12 00:26:35.496: INFO: Pod "pod-subpath-test-dynamicpv-gngw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.070884229s
Jun 12 00:26:37.535: INFO: Pod "pod-subpath-test-dynamicpv-gngw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.109297798s
Jun 12 00:26:39.565: INFO: Pod "pod-subpath-test-dynamicpv-gngw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.139539442s
Jun 12 00:26:41.597: INFO: Pod "pod-subpath-test-dynamicpv-gngw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.171054043s
Jun 12 00:26:43.628: INFO: Pod "pod-subpath-test-dynamicpv-gngw": Phase="Pending", Reason="", readiness=false. Elapsed: 10.202153705s
... skipping 2 lines ...
Jun 12 00:26:49.723: INFO: Pod "pod-subpath-test-dynamicpv-gngw": Phase="Pending", Reason="", readiness=false. Elapsed: 16.297258287s
Jun 12 00:26:51.754: INFO: Pod "pod-subpath-test-dynamicpv-gngw": Phase="Pending", Reason="", readiness=false. Elapsed: 18.328760888s
Jun 12 00:26:53.788: INFO: Pod "pod-subpath-test-dynamicpv-gngw": Phase="Pending", Reason="", readiness=false. Elapsed: 20.361930259s
Jun 12 00:26:55.822: INFO: Pod "pod-subpath-test-dynamicpv-gngw": Phase="Pending", Reason="", readiness=false. Elapsed: 22.396242248s
Jun 12 00:26:57.853: INFO: Pod "pod-subpath-test-dynamicpv-gngw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.427085098s
STEP: Saw pod success
Jun 12 00:26:57.853: INFO: Pod "pod-subpath-test-dynamicpv-gngw" satisfied condition "Succeeded or Failed"
Jun 12 00:26:57.884: INFO: Trying to get logs from node ip-172-20-36-179.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-gngw container test-container-subpath-dynamicpv-gngw: <nil>
STEP: delete the pod
Jun 12 00:26:57.953: INFO: Waiting for pod pod-subpath-test-dynamicpv-gngw to disappear
Jun 12 00:26:57.983: INFO: Pod pod-subpath-test-dynamicpv-gngw no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-gngw
Jun 12 00:26:57.983: INFO: Deleting pod "pod-subpath-test-dynamicpv-gngw" in namespace "provisioning-1901"
... skipping 224 lines ...
Jun 12 00:27:41.673: INFO: Waiting for pod aws-client to disappear
Jun 12 00:27:41.703: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 12 00:27:41.703: INFO: Deleting PersistentVolumeClaim "pvc-k52zb"
Jun 12 00:27:41.735: INFO: Deleting PersistentVolume "aws-2v9nl"
Jun 12 00:27:41.885: INFO: Couldn't delete PD "aws://us-east-2a/vol-013578b4770adba93", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-013578b4770adba93 is currently attached to i-08052264bd3923f8c
	status code: 400, request id: d33aee54-c84e-42c5-8d73-91aa1fff07ce
Jun 12 00:27:47.154: INFO: Successfully deleted PD "aws://us-east-2a/vol-013578b4770adba93".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 00:27:47.154: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-7138" for this suite.
... skipping 280 lines ...
Jun 12 00:27:41.972: INFO: Waiting for pod aws-client to disappear
Jun 12 00:27:42.002: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 12 00:27:42.002: INFO: Deleting PersistentVolumeClaim "pvc-q4x8q"
Jun 12 00:27:42.032: INFO: Deleting PersistentVolume "aws-9v7kp"
Jun 12 00:27:42.335: INFO: Couldn't delete PD "aws://us-east-2a/vol-0f01d52869d8a5f4b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f01d52869d8a5f4b is currently attached to i-01d52253ff2bb51c3
	status code: 400, request id: db9852bb-3d1c-416d-ba4b-0c4414d32093
Jun 12 00:27:47.566: INFO: Couldn't delete PD "aws://us-east-2a/vol-0f01d52869d8a5f4b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f01d52869d8a5f4b is currently attached to i-01d52253ff2bb51c3
	status code: 400, request id: 5f46b403-f042-4918-8966-2e558f257b90
Jun 12 00:27:52.826: INFO: Couldn't delete PD "aws://us-east-2a/vol-0f01d52869d8a5f4b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f01d52869d8a5f4b is currently attached to i-01d52253ff2bb51c3
	status code: 400, request id: 6340eb38-eca3-4c38-8561-0c1d4bd981e4
Jun 12 00:27:58.095: INFO: Successfully deleted PD "aws://us-east-2a/vol-0f01d52869d8a5f4b".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 00:27:58.095: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-3395" for this suite.
... skipping 266 lines ...
Jun 12 00:25:48.825: INFO: Creating resource for dynamic PV
Jun 12 00:25:48.825: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-5322-e2e-sc9j2jf
STEP: creating a claim
Jun 12 00:25:48.859: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 12 00:25:48.957: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-w88rt" in namespace "snapshotting-5322" to be "Succeeded or Failed"
Jun 12 00:25:48.987: INFO: Pod "pvc-snapshottable-tester-w88rt": Phase="Pending", Reason="", readiness=false. Elapsed: 30.144761ms
Jun 12 00:25:51.018: INFO: Pod "pvc-snapshottable-tester-w88rt": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061464017s
Jun 12 00:25:53.050: INFO: Pod "pvc-snapshottable-tester-w88rt": Phase="Pending", Reason="", readiness=false. Elapsed: 4.093525787s
Jun 12 00:25:55.083: INFO: Pod "pvc-snapshottable-tester-w88rt": Phase="Pending", Reason="", readiness=false. Elapsed: 6.125693091s
Jun 12 00:25:57.118: INFO: Pod "pvc-snapshottable-tester-w88rt": Phase="Pending", Reason="", readiness=false. Elapsed: 8.16066642s
Jun 12 00:25:59.148: INFO: Pod "pvc-snapshottable-tester-w88rt": Phase="Pending", Reason="", readiness=false. Elapsed: 10.191344441s
Jun 12 00:26:01.179: INFO: Pod "pvc-snapshottable-tester-w88rt": Phase="Pending", Reason="", readiness=false. Elapsed: 12.222319216s
Jun 12 00:26:03.211: INFO: Pod "pvc-snapshottable-tester-w88rt": Phase="Pending", Reason="", readiness=false. Elapsed: 14.254123859s
Jun 12 00:26:05.242: INFO: Pod "pvc-snapshottable-tester-w88rt": Phase="Pending", Reason="", readiness=false. Elapsed: 16.285052062s
Jun 12 00:26:07.273: INFO: Pod "pvc-snapshottable-tester-w88rt": Phase="Pending", Reason="", readiness=false. Elapsed: 18.316085986s
Jun 12 00:26:09.304: INFO: Pod "pvc-snapshottable-tester-w88rt": Phase="Pending", Reason="", readiness=false. Elapsed: 20.346851595s
Jun 12 00:26:11.334: INFO: Pod "pvc-snapshottable-tester-w88rt": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.377558086s
STEP: Saw pod success
Jun 12 00:26:11.334: INFO: Pod "pvc-snapshottable-tester-w88rt" satisfied condition "Succeeded or Failed"
Jun 12 00:26:11.410: INFO: Pod pvc-snapshottable-tester-w88rt has the following logs: 
Jun 12 00:26:11.410: INFO: Deleting pod "pvc-snapshottable-tester-w88rt" in namespace "snapshotting-5322"
Jun 12 00:26:11.448: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-w88rt" to be fully deleted
Jun 12 00:26:11.492: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comg8rxc] to have phase Bound
Jun 12 00:26:11.523: INFO: PersistentVolumeClaim ebs.csi.aws.comg8rxc found and phase=Bound (30.259945ms)
STEP: [init] checking the claim
... skipping 51 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.mVCl1cIaj/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 12 00:26:58.948: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-qdbb2" in namespace "snapshotting-5322" to be "Succeeded or Failed"
Jun 12 00:26:58.983: INFO: Pod "pvc-snapshottable-data-tester-qdbb2": Phase="Pending", Reason="", readiness=false. Elapsed: 35.181845ms
Jun 12 00:27:01.014: INFO: Pod "pvc-snapshottable-data-tester-qdbb2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.06617559s
Jun 12 00:27:03.044: INFO: Pod "pvc-snapshottable-data-tester-qdbb2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.096615413s
Jun 12 00:27:05.076: INFO: Pod "pvc-snapshottable-data-tester-qdbb2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.127925217s
Jun 12 00:27:07.106: INFO: Pod "pvc-snapshottable-data-tester-qdbb2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.158571218s
STEP: Saw pod success
Jun 12 00:27:07.106: INFO: Pod "pvc-snapshottable-data-tester-qdbb2" satisfied condition "Succeeded or Failed"
Jun 12 00:27:07.183: INFO: Pod pvc-snapshottable-data-tester-qdbb2 has the following logs: 
Jun 12 00:27:07.183: INFO: Deleting pod "pvc-snapshottable-data-tester-qdbb2" in namespace "snapshotting-5322"
Jun 12 00:27:07.219: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-qdbb2" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 12 00:27:23.375: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-5322 exec restored-pvc-tester-d6gvv --namespace=snapshotting-5322 -- cat /mnt/test/data'
... skipping 34 lines ...
Jun 12 00:28:11.539: INFO: At 2021-06-12 00:25:52 +0000 UTC - event for pvc-snapshottable-tester-w88rt: {default-scheduler } Scheduled: Successfully assigned snapshotting-5322/pvc-snapshottable-tester-w88rt to ip-172-20-54-191.us-east-2.compute.internal
Jun 12 00:28:11.539: INFO: At 2021-06-12 00:26:07 +0000 UTC - event for pvc-snapshottable-tester-w88rt: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-e5706ead-2243-4214-91c8-4c25bf152f13" 
Jun 12 00:28:11.539: INFO: At 2021-06-12 00:26:09 +0000 UTC - event for pvc-snapshottable-tester-w88rt: {kubelet ip-172-20-54-191.us-east-2.compute.internal} Started: Started container volume-tester
Jun 12 00:28:11.539: INFO: At 2021-06-12 00:26:09 +0000 UTC - event for pvc-snapshottable-tester-w88rt: {kubelet ip-172-20-54-191.us-east-2.compute.internal} Created: Created container volume-tester
Jun 12 00:28:11.539: INFO: At 2021-06-12 00:26:09 +0000 UTC - event for pvc-snapshottable-tester-w88rt: {kubelet ip-172-20-54-191.us-east-2.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" already present on machine
Jun 12 00:28:11.539: INFO: At 2021-06-12 00:26:11 +0000 UTC - event for snapshot-sz6zr: {snapshot-controller } CreatingSnapshot: Waiting for a snapshot snapshotting-5322/snapshot-sz6zr to be created by the CSI driver.
Jun 12 00:28:11.539: INFO: At 2021-06-12 00:26:56 +0000 UTC - event for pre-provisioned-snapshot-9507966d-e77b-4316-907c-dc8099d4749b: {snapshot-controller } SnapshotBindFailed: Snapshot failed to bind VolumeSnapshotContent, Operation cannot be fulfilled on volumesnapshotcontents.snapshot.storage.k8s.io "pre-provisioned-snapcontent-9507966d-e77b-4316-907c-dc8099d4749b": the object has been modified; please apply your changes to the latest version and try again
Jun 12 00:28:11.539: INFO: At 2021-06-12 00:26:58 +0000 UTC - event for pvc-snapshottable-data-tester-qdbb2: {default-scheduler } Scheduled: Successfully assigned snapshotting-5322/pvc-snapshottable-data-tester-qdbb2 to ip-172-20-56-193.us-east-2.compute.internal
Jun 12 00:28:11.539: INFO: At 2021-06-12 00:27:01 +0000 UTC - event for pvc-snapshottable-data-tester-qdbb2: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-e5706ead-2243-4214-91c8-4c25bf152f13" 
Jun 12 00:28:11.539: INFO: At 2021-06-12 00:27:04 +0000 UTC - event for pvc-snapshottable-data-tester-qdbb2: {kubelet ip-172-20-56-193.us-east-2.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" already present on machine
Jun 12 00:28:11.539: INFO: At 2021-06-12 00:27:05 +0000 UTC - event for pvc-snapshottable-data-tester-qdbb2: {kubelet ip-172-20-56-193.us-east-2.compute.internal} Started: Started container volume-tester
Jun 12 00:28:11.539: INFO: At 2021-06-12 00:27:05 +0000 UTC - event for pvc-snapshottable-data-tester-qdbb2: {kubelet ip-172-20-56-193.us-east-2.compute.internal} Created: Created container volume-tester
Jun 12 00:28:11.539: INFO: At 2021-06-12 00:27:07 +0000 UTC - event for pvc-rzv8r: {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 3 lines ...
Jun 12 00:28:11.539: INFO: At 2021-06-12 00:27:11 +0000 UTC - event for restored-pvc-tester-d6gvv: {default-scheduler } Scheduled: Successfully assigned snapshotting-5322/restored-pvc-tester-d6gvv to ip-172-20-56-193.us-east-2.compute.internal
Jun 12 00:28:11.539: INFO: At 2021-06-12 00:27:17 +0000 UTC - event for restored-pvc-tester-d6gvv: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-08ed7a32-ae58-41af-81f3-6ed9749fee8f" 
Jun 12 00:28:11.539: INFO: At 2021-06-12 00:27:20 +0000 UTC - event for restored-pvc-tester-d6gvv: {kubelet ip-172-20-56-193.us-east-2.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" already present on machine
Jun 12 00:28:11.539: INFO: At 2021-06-12 00:27:20 +0000 UTC - event for restored-pvc-tester-d6gvv: {kubelet ip-172-20-56-193.us-east-2.compute.internal} Created: Created container volume-tester
Jun 12 00:28:11.539: INFO: At 2021-06-12 00:27:20 +0000 UTC - event for restored-pvc-tester-d6gvv: {kubelet ip-172-20-56-193.us-east-2.compute.internal} Started: Started container volume-tester
Jun 12 00:28:11.539: INFO: At 2021-06-12 00:27:23 +0000 UTC - event for restored-pvc-tester-d6gvv: {kubelet ip-172-20-56-193.us-east-2.compute.internal} Killing: Stopping container volume-tester
Jun 12 00:28:11.539: INFO: At 2021-06-12 00:28:02 +0000 UTC - event for pre-provisioned-snapshot-9507966d-e77b-4316-907c-dc8099d4749b: {snapshot-controller } SnapshotFinalizerError: Failed to check and update snapshot: snapshot controller failed to update snapshotting-5322/pre-provisioned-snapshot-9507966d-e77b-4316-907c-dc8099d4749b on API server: Operation cannot be fulfilled on volumesnapshots.snapshot.storage.k8s.io "pre-provisioned-snapshot-9507966d-e77b-4316-907c-dc8099d4749b": the object has been modified; please apply your changes to the latest version and try again
Jun 12 00:28:11.569: INFO: POD  NODE  PHASE  GRACE  CONDITIONS
Jun 12 00:28:11.569: INFO: 
Jun 12 00:28:11.601: INFO: 
Logging node info for node ip-172-20-36-179.us-east-2.compute.internal
Jun 12 00:28:11.631: INFO: Node Info: &Node{ObjectMeta:{ip-172-20-36-179.us-east-2.compute.internal    9f633b9f-574a-4ac7-9ff6-afab9d444c32 8428 0 2021-06-12 00:20:06 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:t3.medium beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:us-east-2 failure-domain.beta.kubernetes.io/zone:us-east-2a kops.k8s.io/instancegroup:nodes-us-east-2a kubernetes.io/arch:amd64 kubernetes.io/hostname:ip-172-20-36-179.us-east-2.compute.internal kubernetes.io/os:linux kubernetes.io/role:node node-role.kubernetes.io/node: node.kubernetes.io/instance-type:t3.medium topology.ebs.csi.aws.com/zone:us-east-2a topology.kubernetes.io/region:us-east-2 topology.kubernetes.io/zone:us-east-2a] map[csi.volume.kubernetes.io/nodeid:{"ebs.csi.aws.com":"i-040c2d8c38b7aa7c4"} node.alpha.kubernetes.io/ttl:0 projectcalico.org/IPv4Address:172.20.36.179/19 projectcalico.org/IPv4IPIPTunnelAddr:100.107.175.128 volumes.kubernetes.io/controller-managed-attach-detach:true] [] []  [{kops-controller Update v1 2021-06-12 00:20:06 +0000 UTC FieldsV1 {"f:metadata":{"f:labels":{"f:kops.k8s.io/instancegroup":{},"f:kubernetes.io/role":{},"f:node-role.kubernetes.io/node":{}}}}} {calico-node Update v1 2021-06-12 00:20:28 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4IPIPTunnelAddr":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}}} {kubelet Update v1 2021-06-12 00:23:56 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:csi.volume.kubernetes.io/nodeid":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.ebs.csi.aws.com/zone":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}},"f:status":{"f:allocatable":{"f:ephemeral-storage":{}},"f:capacity":{"f:ephemeral-storage":{}},"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{},"f:volumesInUse":{}}}} {kube-controller-manager Update v1 2021-06-12 00:23:59 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"100.96.3.0/24\"":{}}},"f:status":{"f:volumesAttached":{}}}}]},Spec:NodeSpec{PodCIDR:100.96.3.0/24,DoNotUseExternalID:,ProviderID:aws:///us-east-2a/i-040c2d8c38b7aa7c4,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[100.96.3.0/24],},Status:NodeStatus{Capacity:ResourceList{cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{49895047168 0} {<nil>}  BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{4064759808 0} {<nil>} 3969492Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{44905542377 0} {<nil>} 44905542377 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{3959902208 0} {<nil>} 3867092Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2021-06-12 00:20:28 +0000 UTC,LastTransitionTime:2021-06-12 00:20:28 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2021-06-12 00:27:36 +0000 UTC,LastTransitionTime:2021-06-12 00:20:06 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2021-06-12 00:27:36 +0000 UTC,LastTransitionTime:2021-06-12 00:20:06 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2021-06-12 00:27:36 +0000 UTC,LastTransitionTime:2021-06-12 00:20:06 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2021-06-12 00:27:36 +0000 UTC,LastTransitionTime:2021-06-12 00:20:26 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:172.20.36.179,},NodeAddress{Type:ExternalIP,Address:18.217.176.214,},NodeAddress{Type:Hostname,Address:ip-172-20-36-179.us-east-2.compute.internal,},NodeAddress{Type:InternalDNS,Address:ip-172-20-36-179.us-east-2.compute.internal,},NodeAddress{Type:ExternalDNS,Address:ec2-18-217-176-214.us-east-2.compute.amazonaws.com,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:ec2be45265cb8f9520c337b76bd395f5,SystemUUID:ec2be452-65cb-8f95-20c3-37b76bd395f5,BootID:3f036e13-0b81-4818-9b41-d55c9680853d,KernelVersion:5.4.0-1045-aws,OSImage:Ubuntu 20.04.2 LTS,ContainerRuntimeVersion:containerd://1.4.6,KubeletVersion:v1.21.0,KubeProxyVersion:v1.21.0,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[k8s.gcr.io/provider-aws/aws-ebs-csi-driver@sha256:a0294bf95fd94eabdc9b313b6c16232019a8707c711c031a2f99ab1f919560bd k8s.gcr.io/provider-aws/aws-ebs-csi-driver:v1.0.0],SizeBytes:67079979,},ContainerImage{Names:[docker.io/calico/node@sha256:bc4a631d553b38fdc169ea4cb8027fa894a656e80d68d513359a4b9d46836b55 docker.io/calico/node:v3.19.1],SizeBytes:58671776,},ContainerImage{Names:[k8s.gcr.io/kube-proxy@sha256:326199e7a5232bf7531a3058e9811c925b07085f33fa882558cc4e89379b9109 k8s.gcr.io/kube-proxy:v1.21.0],SizeBytes:50134170,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/agnhost@sha256:8bd76a6a7778e203b61e18e5ee85b1faf52e6a30eb07e445a165ab90fe9633e3 k8s.gcr.io/e2e-test-images/agnhost:2.31],SizeBytes:49692421,},ContainerImage{Names:[docker.io/calico/cni@sha256:f301171be0add870152483fcce71b28cafb8e910f61ff003032e9b1053b062c4 docker.io/calico/cni:v3.19.1],SizeBytes:48338203,},ContainerImage{Names:[docker.io/calico/pod2daemon-flexvol@sha256:bcac7dc4f1301b062d91a177a52d13716907636975c44131fb8350e7f851c944 docker.io/calico/pod2daemon-flexvol:v3.19.1],SizeBytes:9328155,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-node-driver-registrar@sha256:a61d309da54641db41fb8f35718f744e9f730d4d0384f8c4b186ddc9f06cbd5f k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.1.0],SizeBytes:9068367,},ContainerImage{Names:[k8s.gcr.io/sig-storage/livenessprobe@sha256:48da0e4ed7238ad461ea05f68c25921783c37b315f21a5c5a2780157a6460994 k8s.gcr.io/sig-storage/livenessprobe:v2.2.0],SizeBytes:8279778,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/nginx@sha256:503b7abb89e57383eba61cc8a9cb0b495ea575c516108f7d972a6ff6e1ab3c9b k8s.gcr.io/e2e-test-images/nginx:1.14-1],SizeBytes:6979365,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/busybox@sha256:39e1e963e5310e9c313bad51523be012ede7b35bb9316517d19089a010356592 k8s.gcr.io/e2e-test-images/busybox:1.29-1],SizeBytes:732746,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:927d98197ec1141a368550822d18fa1c60bdae27b78b0c004f705f548c07814f k8s.gcr.io/pause:3.2],SizeBytes:299513,},},VolumesInUse:[kubernetes.io/csi/ebs.csi.aws.com^vol-04e85460a89a9bd56 kubernetes.io/csi/ebs.csi.aws.com^vol-090480c11b136db41 kubernetes.io/csi/ebs.csi.aws.com^vol-0b1cca5c0b989392f kubernetes.io/csi/ebs.csi.aws.com^vol-0cdea25826b546599 kubernetes.io/csi/ebs.csi.aws.com^vol-0fd36f822f76070e5],VolumesAttached:[]AttachedVolume{AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-0b1cca5c0b989392f,DevicePath:,},AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-0fd36f822f76070e5,DevicePath:,},AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-0cdea25826b546599,DevicePath:,},AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-090480c11b136db41,DevicePath:,},AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-04e85460a89a9bd56,DevicePath:,},},Config:nil,},}
Jun 12 00:28:11.631: INFO: 
... skipping 200 lines ...
    /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:108
      
      /tmp/kops.mVCl1cIaj/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.mVCl1cIaj/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-5322 exec restored-pvc-tester-d6gvv --namespace=snapshotting-5322 -- 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-5322 exec restored-pvc-tester-d6gvv --namespace=snapshotting-5322 -- 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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:602
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow]
... skipping 78 lines ...
STEP: Deleting pod hostexec-ip-172-20-54-191.us-east-2.compute.internal-7x4kt in namespace volumemode-6011
Jun 12 00:27:46.752: INFO: Deleting pod "pod-391d693a-c280-48c5-8e9a-c0213b301901" in namespace "volumemode-6011"
Jun 12 00:27:46.786: INFO: Wait up to 5m0s for pod "pod-391d693a-c280-48c5-8e9a-c0213b301901" to be fully deleted
STEP: Deleting pv and pvc
Jun 12 00:27:58.853: INFO: Deleting PersistentVolumeClaim "pvc-6rfvg"
Jun 12 00:27:58.884: INFO: Deleting PersistentVolume "aws-tgbdh"
Jun 12 00:27:59.034: INFO: Couldn't delete PD "aws://us-east-2a/vol-0cbf242992bc779f6", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0cbf242992bc779f6 is currently attached to i-04c4a604524f7b63b
	status code: 400, request id: 6a503669-1e3d-4231-80b2-e169df7a93e7
Jun 12 00:28:04.267: INFO: Couldn't delete PD "aws://us-east-2a/vol-0cbf242992bc779f6", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0cbf242992bc779f6 is currently attached to i-04c4a604524f7b63b
	status code: 400, request id: 271f74c7-3f8c-4c4c-9197-0932569fa37d
Jun 12 00:28:09.670: INFO: Couldn't delete PD "aws://us-east-2a/vol-0cbf242992bc779f6", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0cbf242992bc779f6 is currently attached to i-04c4a604524f7b63b
	status code: 400, request id: 84a80650-decc-4ec9-a33c-f09091260f29
Jun 12 00:28:14.991: INFO: Successfully deleted PD "aws://us-east-2a/vol-0cbf242992bc779f6".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 00:28:14.991: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-6011" for this suite.
... skipping 34 lines ...
Jun 12 00:27:18.418: INFO: PersistentVolumeClaim pvc-d5qsd found but phase is Pending instead of Bound.
Jun 12 00:27:20.450: INFO: PersistentVolumeClaim pvc-d5qsd found and phase=Bound (10.191225435s)
Jun 12 00:27:20.450: INFO: Waiting up to 3m0s for PersistentVolume aws-hghjn to have phase Bound
Jun 12 00:27:20.480: INFO: PersistentVolume aws-hghjn found and phase=Bound (30.587525ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-blxd
STEP: Creating a pod to test exec-volume-test
Jun 12 00:27:20.575: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-blxd" in namespace "volume-9098" to be "Succeeded or Failed"
Jun 12 00:27:20.606: INFO: Pod "exec-volume-test-preprovisionedpv-blxd": Phase="Pending", Reason="", readiness=false. Elapsed: 30.816691ms
Jun 12 00:27:22.638: INFO: Pod "exec-volume-test-preprovisionedpv-blxd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.063164439s
Jun 12 00:27:24.670: INFO: Pod "exec-volume-test-preprovisionedpv-blxd": Phase="Pending", Reason="", readiness=false. Elapsed: 4.094994326s
Jun 12 00:27:26.702: INFO: Pod "exec-volume-test-preprovisionedpv-blxd": Phase="Pending", Reason="", readiness=false. Elapsed: 6.127186568s
Jun 12 00:27:28.734: INFO: Pod "exec-volume-test-preprovisionedpv-blxd": Phase="Pending", Reason="", readiness=false. Elapsed: 8.158781904s
Jun 12 00:27:30.765: INFO: Pod "exec-volume-test-preprovisionedpv-blxd": Phase="Pending", Reason="", readiness=false. Elapsed: 10.189808923s
... skipping 7 lines ...
Jun 12 00:27:47.021: INFO: Pod "exec-volume-test-preprovisionedpv-blxd": Phase="Pending", Reason="", readiness=false. Elapsed: 26.446077187s
Jun 12 00:27:49.053: INFO: Pod "exec-volume-test-preprovisionedpv-blxd": Phase="Pending", Reason="", readiness=false. Elapsed: 28.477636264s
Jun 12 00:27:51.086: INFO: Pod "exec-volume-test-preprovisionedpv-blxd": Phase="Pending", Reason="", readiness=false. Elapsed: 30.510474046s
Jun 12 00:27:53.119: INFO: Pod "exec-volume-test-preprovisionedpv-blxd": Phase="Pending", Reason="", readiness=false. Elapsed: 32.543397812s
Jun 12 00:27:55.151: INFO: Pod "exec-volume-test-preprovisionedpv-blxd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.575487813s
STEP: Saw pod success
Jun 12 00:27:55.151: INFO: Pod "exec-volume-test-preprovisionedpv-blxd" satisfied condition "Succeeded or Failed"
Jun 12 00:27:55.182: INFO: Trying to get logs from node ip-172-20-56-193.us-east-2.compute.internal pod exec-volume-test-preprovisionedpv-blxd container exec-container-preprovisionedpv-blxd: <nil>
STEP: delete the pod
Jun 12 00:27:55.252: INFO: Waiting for pod exec-volume-test-preprovisionedpv-blxd to disappear
Jun 12 00:27:55.283: INFO: Pod exec-volume-test-preprovisionedpv-blxd no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-blxd
Jun 12 00:27:55.283: INFO: Deleting pod "exec-volume-test-preprovisionedpv-blxd" in namespace "volume-9098"
STEP: Deleting pv and pvc
Jun 12 00:27:55.313: INFO: Deleting PersistentVolumeClaim "pvc-d5qsd"
Jun 12 00:27:55.345: INFO: Deleting PersistentVolume "aws-hghjn"
Jun 12 00:27:55.516: INFO: Couldn't delete PD "aws://us-east-2a/vol-01d4242801fe18487", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01d4242801fe18487 is currently attached to i-08052264bd3923f8c
	status code: 400, request id: a2ca64ce-9ab0-4195-bc39-1cda9a70f7a2
Jun 12 00:28:00.748: INFO: Couldn't delete PD "aws://us-east-2a/vol-01d4242801fe18487", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01d4242801fe18487 is currently attached to i-08052264bd3923f8c
	status code: 400, request id: 7fb1bae2-7bbc-42a7-938b-3d7ebe95d3d2
Jun 12 00:28:05.989: INFO: Couldn't delete PD "aws://us-east-2a/vol-01d4242801fe18487", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01d4242801fe18487 is currently attached to i-08052264bd3923f8c
	status code: 400, request id: 8baed4aa-31a4-4152-9363-e32756c07c90
Jun 12 00:28:11.236: INFO: Couldn't delete PD "aws://us-east-2a/vol-01d4242801fe18487", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01d4242801fe18487 is currently attached to i-08052264bd3923f8c
	status code: 400, request id: cdf89392-78f9-4bfa-9ccc-450f96208f33
Jun 12 00:28:16.508: INFO: Successfully deleted PD "aws://us-east-2a/vol-01d4242801fe18487".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 00:28:16.508: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-9098" for this suite.
... skipping 236 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  /tmp/kops.mVCl1cIaj/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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

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

    /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 105 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 12 00:27:47.222: 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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 12 00:27:47.377: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 12 00:27:47.732: INFO: Successfully created a new PD: "aws://us-east-2a/vol-060b434a53e4de3e4".
Jun 12 00:27:47.732: INFO: Creating resource for pre-provisioned PV
Jun 12 00:27:47.732: INFO: Creating PVC and PV
... skipping 3 lines ...
Jun 12 00:27:47.889: INFO: PersistentVolumeClaim pvc-cpcs6 found but phase is Pending instead of Bound.
Jun 12 00:27:49.920: INFO: PersistentVolumeClaim pvc-cpcs6 found but phase is Pending instead of Bound.
Jun 12 00:27:51.952: INFO: PersistentVolumeClaim pvc-cpcs6 found and phase=Bound (4.092001649s)
Jun 12 00:27:51.952: INFO: Waiting up to 3m0s for PersistentVolume aws-wk6zd to have phase Bound
Jun 12 00:27:51.981: INFO: PersistentVolume aws-wk6zd found and phase=Bound (29.453444ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 12 00:27:54.163: INFO: Deleting pod "pod-71d4da84-bbc4-46a8-a39f-815dafe5e381" in namespace "volumemode-1376"
Jun 12 00:27:54.195: INFO: Wait up to 5m0s for pod "pod-71d4da84-bbc4-46a8-a39f-815dafe5e381" to be fully deleted
STEP: Deleting pv and pvc
Jun 12 00:27:58.272: INFO: Deleting PersistentVolumeClaim "pvc-cpcs6"
Jun 12 00:27:58.303: INFO: Deleting PersistentVolume "aws-wk6zd"
Jun 12 00:27:58.455: INFO: Couldn't delete PD "aws://us-east-2a/vol-060b434a53e4de3e4", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-060b434a53e4de3e4 is currently attached to i-04c4a604524f7b63b
	status code: 400, request id: 51532bf9-a017-4548-ba8a-cb9e5446e659
Jun 12 00:28:03.688: INFO: Couldn't delete PD "aws://us-east-2a/vol-060b434a53e4de3e4", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-060b434a53e4de3e4 is currently attached to i-04c4a604524f7b63b
	status code: 400, request id: c45009da-46ec-4faa-b1ec-6a87b08d0d97
Jun 12 00:28:08.934: INFO: Couldn't delete PD "aws://us-east-2a/vol-060b434a53e4de3e4", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-060b434a53e4de3e4 is currently attached to i-04c4a604524f7b63b
	status code: 400, request id: d5dc349f-b607-4d5f-a5f9-2fec703af19a
Jun 12 00:28:14.185: INFO: Couldn't delete PD "aws://us-east-2a/vol-060b434a53e4de3e4", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-060b434a53e4de3e4 is currently attached to i-04c4a604524f7b63b
	status code: 400, request id: ed53f7f6-380d-4424-8717-bffad1946da3
Jun 12 00:28:19.429: INFO: Couldn't delete PD "aws://us-east-2a/vol-060b434a53e4de3e4", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-060b434a53e4de3e4 is currently attached to i-04c4a604524f7b63b
	status code: 400, request id: c8ea58ed-d653-4eba-aa03-7411a10ce975
Jun 12 00:28:24.693: INFO: Couldn't delete PD "aws://us-east-2a/vol-060b434a53e4de3e4", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-060b434a53e4de3e4 is currently attached to i-04c4a604524f7b63b
	status code: 400, request id: 69ed86bc-e52b-416a-a56c-676b7a0e91c0
Jun 12 00:28:29.934: INFO: Couldn't delete PD "aws://us-east-2a/vol-060b434a53e4de3e4", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-060b434a53e4de3e4 is currently attached to i-04c4a604524f7b63b
	status code: 400, request id: 6a0ba951-e696-4dae-b188-b7d4ffb79d13
Jun 12 00:28:35.182: INFO: Successfully deleted PD "aws://us-east-2a/vol-060b434a53e4de3e4".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 00:28:35.182: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-1376" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.mVCl1cIaj/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.mVCl1cIaj/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
    /tmp/kops.mVCl1cIaj/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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 105 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.mVCl1cIaj/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.mVCl1cIaj/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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 29 lines ...
Jun 12 00:26:09.686: INFO: Creating resource for dynamic PV
Jun 12 00:26:09.686: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-6153-e2e-scq75wd
STEP: creating a claim
Jun 12 00:26:09.718: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 12 00:26:09.818: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-pwwcj" in namespace "snapshotting-6153" to be "Succeeded or Failed"
Jun 12 00:26:09.849: INFO: Pod "pvc-snapshottable-tester-pwwcj": Phase="Pending", Reason="", readiness=false. Elapsed: 30.436352ms
Jun 12 00:26:11.879: INFO: Pod "pvc-snapshottable-tester-pwwcj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.060927007s
Jun 12 00:26:13.910: INFO: Pod "pvc-snapshottable-tester-pwwcj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.091656073s
Jun 12 00:26:15.942: INFO: Pod "pvc-snapshottable-tester-pwwcj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.12370702s
Jun 12 00:26:17.973: INFO: Pod "pvc-snapshottable-tester-pwwcj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.154503199s
Jun 12 00:26:20.012: INFO: Pod "pvc-snapshottable-tester-pwwcj": Phase="Pending", Reason="", readiness=false. Elapsed: 10.193700072s
Jun 12 00:26:22.044: INFO: Pod "pvc-snapshottable-tester-pwwcj": Phase="Pending", Reason="", readiness=false. Elapsed: 12.226232368s
Jun 12 00:26:24.078: INFO: Pod "pvc-snapshottable-tester-pwwcj": Phase="Pending", Reason="", readiness=false. Elapsed: 14.260091735s
Jun 12 00:26:26.112: INFO: Pod "pvc-snapshottable-tester-pwwcj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.293333259s
STEP: Saw pod success
Jun 12 00:26:26.112: INFO: Pod "pvc-snapshottable-tester-pwwcj" satisfied condition "Succeeded or Failed"
Jun 12 00:26:26.174: INFO: Pod pvc-snapshottable-tester-pwwcj has the following logs: 
Jun 12 00:26:26.174: INFO: Deleting pod "pvc-snapshottable-tester-pwwcj" in namespace "snapshotting-6153"
Jun 12 00:26:26.211: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-pwwcj" to be fully deleted
Jun 12 00:26:26.241: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comtz8vs] to have phase Bound
Jun 12 00:26:26.271: INFO: PersistentVolumeClaim ebs.csi.aws.comtz8vs found and phase=Bound (29.994123ms)
STEP: [init] checking the claim
... skipping 44 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.mVCl1cIaj/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 12 00:26:59.501: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-72js7" in namespace "snapshotting-6153" to be "Succeeded or Failed"
Jun 12 00:26:59.532: INFO: Pod "pvc-snapshottable-data-tester-72js7": Phase="Pending", Reason="", readiness=false. Elapsed: 30.661013ms
Jun 12 00:27:01.564: INFO: Pod "pvc-snapshottable-data-tester-72js7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062957594s
Jun 12 00:27:03.595: INFO: Pod "pvc-snapshottable-data-tester-72js7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.093358345s
Jun 12 00:27:05.627: INFO: Pod "pvc-snapshottable-data-tester-72js7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.125281662s
Jun 12 00:27:07.657: INFO: Pod "pvc-snapshottable-data-tester-72js7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.155618887s
Jun 12 00:27:09.688: INFO: Pod "pvc-snapshottable-data-tester-72js7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.186200615s
STEP: Saw pod success
Jun 12 00:27:09.688: INFO: Pod "pvc-snapshottable-data-tester-72js7" satisfied condition "Succeeded or Failed"
Jun 12 00:27:09.750: INFO: Pod pvc-snapshottable-data-tester-72js7 has the following logs: 
Jun 12 00:27:09.750: INFO: Deleting pod "pvc-snapshottable-data-tester-72js7" in namespace "snapshotting-6153"
Jun 12 00:27:09.789: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-72js7" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 12 00:27:49.962: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-6153 exec restored-pvc-tester-c8kr4 --namespace=snapshotting-6153 -- cat /mnt/test/data'
... skipping 167 lines ...
Jun 12 00:28:19.693: INFO: PersistentVolumeClaim pvc-db7pf found but phase is Pending instead of Bound.
Jun 12 00:28:21.724: INFO: PersistentVolumeClaim pvc-db7pf found and phase=Bound (6.122941172s)
Jun 12 00:28:21.724: INFO: Waiting up to 3m0s for PersistentVolume aws-rvlt2 to have phase Bound
Jun 12 00:28:21.754: INFO: PersistentVolume aws-rvlt2 found and phase=Bound (29.972257ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-6dc8
STEP: Creating a pod to test exec-volume-test
Jun 12 00:28:21.846: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-6dc8" in namespace "volume-2189" to be "Succeeded or Failed"
Jun 12 00:28:21.876: INFO: Pod "exec-volume-test-preprovisionedpv-6dc8": Phase="Pending", Reason="", readiness=false. Elapsed: 29.903959ms
Jun 12 00:28:23.907: INFO: Pod "exec-volume-test-preprovisionedpv-6dc8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.060614452s
Jun 12 00:28:25.937: INFO: Pod "exec-volume-test-preprovisionedpv-6dc8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.091085831s
Jun 12 00:28:27.968: INFO: Pod "exec-volume-test-preprovisionedpv-6dc8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.121511091s
Jun 12 00:28:29.999: INFO: Pod "exec-volume-test-preprovisionedpv-6dc8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.153227933s
Jun 12 00:28:32.030: INFO: Pod "exec-volume-test-preprovisionedpv-6dc8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.183880048s
STEP: Saw pod success
Jun 12 00:28:32.030: INFO: Pod "exec-volume-test-preprovisionedpv-6dc8" satisfied condition "Succeeded or Failed"
Jun 12 00:28:32.060: INFO: Trying to get logs from node ip-172-20-36-179.us-east-2.compute.internal pod exec-volume-test-preprovisionedpv-6dc8 container exec-container-preprovisionedpv-6dc8: <nil>
STEP: delete the pod
Jun 12 00:28:32.129: INFO: Waiting for pod exec-volume-test-preprovisionedpv-6dc8 to disappear
Jun 12 00:28:32.160: INFO: Pod exec-volume-test-preprovisionedpv-6dc8 no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-6dc8
Jun 12 00:28:32.160: INFO: Deleting pod "exec-volume-test-preprovisionedpv-6dc8" in namespace "volume-2189"
STEP: Deleting pv and pvc
Jun 12 00:28:32.189: INFO: Deleting PersistentVolumeClaim "pvc-db7pf"
Jun 12 00:28:32.221: INFO: Deleting PersistentVolume "aws-rvlt2"
Jun 12 00:28:32.406: INFO: Couldn't delete PD "aws://us-east-2a/vol-0219bcae8dc686ad3", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0219bcae8dc686ad3 is currently attached to i-040c2d8c38b7aa7c4
	status code: 400, request id: 9d846433-6ae2-494d-b94b-16a4f8d1b890
Jun 12 00:28:37.635: INFO: Couldn't delete PD "aws://us-east-2a/vol-0219bcae8dc686ad3", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0219bcae8dc686ad3 is currently attached to i-040c2d8c38b7aa7c4
	status code: 400, request id: 39288ca4-5559-4c6f-a15e-939d5be189b0
Jun 12 00:28:42.964: INFO: Successfully deleted PD "aws://us-east-2a/vol-0219bcae8dc686ad3".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 00:28:42.964: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-2189" for this suite.
... skipping 473 lines ...
Jun 12 00:28:41.972: INFO: Waiting for pod aws-client to disappear
Jun 12 00:28:42.006: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 12 00:28:42.006: INFO: Deleting PersistentVolumeClaim "pvc-pjcvf"
Jun 12 00:28:42.037: INFO: Deleting PersistentVolume "aws-bhqgj"
Jun 12 00:28:42.209: INFO: Couldn't delete PD "aws://us-east-2a/vol-0f5dc8f2af7b842dd", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f5dc8f2af7b842dd is currently attached to i-08052264bd3923f8c
	status code: 400, request id: 8c062885-3ed8-42a2-9cfd-4bbe3758b041
Jun 12 00:28:47.477: INFO: Couldn't delete PD "aws://us-east-2a/vol-0f5dc8f2af7b842dd", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f5dc8f2af7b842dd is currently attached to i-08052264bd3923f8c
	status code: 400, request id: 61aecd45-5118-4d67-bafc-e2b625310c7a
Jun 12 00:28:52.753: INFO: Successfully deleted PD "aws://us-east-2a/vol-0f5dc8f2af7b842dd".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumes
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 00:28:52.753: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-5267" for this suite.
... skipping 342 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  /tmp/kops.mVCl1cIaj/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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

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

    /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 2 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 12 00:28:52.824: 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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 12 00:28:52.974: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 12 00:28:52.974: INFO: Creating resource for dynamic PV
Jun 12 00:28:52.974: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-37702j2t6
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 12 00:28:59.212: INFO: Deleting pod "pod-554e2ee5-4b7f-448e-82bb-2024fa75f17c" in namespace "volumemode-3770"
Jun 12 00:28:59.253: INFO: Wait up to 5m0s for pod "pod-554e2ee5-4b7f-448e-82bb-2024fa75f17c" to be fully deleted
STEP: Deleting pvc
Jun 12 00:29:03.377: INFO: Deleting PersistentVolumeClaim "aws79zfb"
Jun 12 00:29:03.409: INFO: Waiting up to 5m0s for PersistentVolume pvc-1293a824-996c-4e2f-bda0-18a7a178d701 to get deleted
Jun 12 00:29:03.440: INFO: PersistentVolume pvc-1293a824-996c-4e2f-bda0-18a7a178d701 found and phase=Released (30.603942ms)
... skipping 10 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.mVCl1cIaj/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.mVCl1cIaj/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
    /tmp/kops.mVCl1cIaj/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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 12 00:29:13.603: INFO: Driver ebs.csi.aws.com doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
... skipping 2 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  /tmp/kops.mVCl1cIaj/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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

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

    /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 132 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.mVCl1cIaj/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.mVCl1cIaj/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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 29 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.mVCl1cIaj/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.mVCl1cIaj/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.mVCl1cIaj/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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 162 lines ...
Jun 12 00:28:44.381: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-7522r2gff
STEP: creating a claim
Jun 12 00:28:44.412: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-n6p6
STEP: Creating a pod to test exec-volume-test
Jun 12 00:28:44.502: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-n6p6" in namespace "volume-7522" to be "Succeeded or Failed"
Jun 12 00:28:44.531: INFO: Pod "exec-volume-test-dynamicpv-n6p6": Phase="Pending", Reason="", readiness=false. Elapsed: 29.103759ms
Jun 12 00:28:46.561: INFO: Pod "exec-volume-test-dynamicpv-n6p6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.058706496s
Jun 12 00:28:48.591: INFO: Pod "exec-volume-test-dynamicpv-n6p6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.088624506s
Jun 12 00:28:50.621: INFO: Pod "exec-volume-test-dynamicpv-n6p6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.119213545s
Jun 12 00:28:52.652: INFO: Pod "exec-volume-test-dynamicpv-n6p6": Phase="Pending", Reason="", readiness=false. Elapsed: 8.14962516s
Jun 12 00:28:54.683: INFO: Pod "exec-volume-test-dynamicpv-n6p6": Phase="Pending", Reason="", readiness=false. Elapsed: 10.180607628s
Jun 12 00:28:56.713: INFO: Pod "exec-volume-test-dynamicpv-n6p6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.211179177s
STEP: Saw pod success
Jun 12 00:28:56.713: INFO: Pod "exec-volume-test-dynamicpv-n6p6" satisfied condition "Succeeded or Failed"
Jun 12 00:28:56.743: INFO: Trying to get logs from node ip-172-20-56-193.us-east-2.compute.internal pod exec-volume-test-dynamicpv-n6p6 container exec-container-dynamicpv-n6p6: <nil>
STEP: delete the pod
Jun 12 00:28:56.810: INFO: Waiting for pod exec-volume-test-dynamicpv-n6p6 to disappear
Jun 12 00:28:56.839: INFO: Pod exec-volume-test-dynamicpv-n6p6 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-n6p6
Jun 12 00:28:56.839: INFO: Deleting pod "exec-volume-test-dynamicpv-n6p6" in namespace "volume-7522"
... skipping 215 lines ...
Jun 12 00:27:23.539: INFO: Creating resource for dynamic PV
Jun 12 00:27:23.539: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-2036-e2e-scntn7k
STEP: creating a claim
Jun 12 00:27:23.571: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 12 00:27:23.660: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-25l2c" in namespace "snapshotting-2036" to be "Succeeded or Failed"
Jun 12 00:27:23.689: INFO: Pod "pvc-snapshottable-tester-25l2c": Phase="Pending", Reason="", readiness=false. Elapsed: 29.13722ms
Jun 12 00:27:25.719: INFO: Pod "pvc-snapshottable-tester-25l2c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.05937754s
Jun 12 00:27:27.749: INFO: Pod "pvc-snapshottable-tester-25l2c": Phase="Pending", Reason="", readiness=false. Elapsed: 4.089087193s
Jun 12 00:27:29.778: INFO: Pod "pvc-snapshottable-tester-25l2c": Phase="Pending", Reason="", readiness=false. Elapsed: 6.11837015s
Jun 12 00:27:31.808: INFO: Pod "pvc-snapshottable-tester-25l2c": Phase="Pending", Reason="", readiness=false. Elapsed: 8.147643228s
Jun 12 00:27:33.837: INFO: Pod "pvc-snapshottable-tester-25l2c": Phase="Pending", Reason="", readiness=false. Elapsed: 10.177283491s
Jun 12 00:27:35.867: INFO: Pod "pvc-snapshottable-tester-25l2c": Phase="Pending", Reason="", readiness=false. Elapsed: 12.206746508s
Jun 12 00:27:37.902: INFO: Pod "pvc-snapshottable-tester-25l2c": Phase="Pending", Reason="", readiness=false. Elapsed: 14.242588643s
Jun 12 00:27:39.934: INFO: Pod "pvc-snapshottable-tester-25l2c": Phase="Pending", Reason="", readiness=false. Elapsed: 16.273900318s
Jun 12 00:27:41.964: INFO: Pod "pvc-snapshottable-tester-25l2c": Phase="Pending", Reason="", readiness=false. Elapsed: 18.304231701s
Jun 12 00:27:43.994: INFO: Pod "pvc-snapshottable-tester-25l2c": Phase="Pending", Reason="", readiness=false. Elapsed: 20.333680308s
Jun 12 00:27:46.023: INFO: Pod "pvc-snapshottable-tester-25l2c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.363588593s
STEP: Saw pod success
Jun 12 00:27:46.024: INFO: Pod "pvc-snapshottable-tester-25l2c" satisfied condition "Succeeded or Failed"
Jun 12 00:27:46.085: INFO: Pod pvc-snapshottable-tester-25l2c has the following logs: 
Jun 12 00:27:46.085: INFO: Deleting pod "pvc-snapshottable-tester-25l2c" in namespace "snapshotting-2036"
Jun 12 00:27:46.123: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-25l2c" to be fully deleted
Jun 12 00:27:46.153: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.com2vnww] to have phase Bound
Jun 12 00:27:46.182: INFO: PersistentVolumeClaim ebs.csi.aws.com2vnww found and phase=Bound (29.424676ms)
STEP: [init] checking the claim
... skipping 23 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.mVCl1cIaj/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 12 00:28:12.919: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-r5hd4" in namespace "snapshotting-2036" to be "Succeeded or Failed"
Jun 12 00:28:12.948: INFO: Pod "pvc-snapshottable-data-tester-r5hd4": Phase="Pending", Reason="", readiness=false. Elapsed: 28.937038ms
Jun 12 00:28:14.977: INFO: Pod "pvc-snapshottable-data-tester-r5hd4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.058240421s
Jun 12 00:28:17.007: INFO: Pod "pvc-snapshottable-data-tester-r5hd4": Phase="Pending", Reason="", readiness=false. Elapsed: 4.088018628s
Jun 12 00:28:19.037: INFO: Pod "pvc-snapshottable-data-tester-r5hd4": Phase="Pending", Reason="", readiness=false. Elapsed: 6.118007655s
Jun 12 00:28:21.068: INFO: Pod "pvc-snapshottable-data-tester-r5hd4": Phase="Pending", Reason="", readiness=false. Elapsed: 8.149344182s
Jun 12 00:28:23.098: INFO: Pod "pvc-snapshottable-data-tester-r5hd4": Phase="Pending", Reason="", readiness=false. Elapsed: 10.179478835s
Jun 12 00:28:25.129: INFO: Pod "pvc-snapshottable-data-tester-r5hd4": Phase="Pending", Reason="", readiness=false. Elapsed: 12.210201347s
Jun 12 00:28:27.160: INFO: Pod "pvc-snapshottable-data-tester-r5hd4": Phase="Pending", Reason="", readiness=false. Elapsed: 14.241414258s
Jun 12 00:28:29.190: INFO: Pod "pvc-snapshottable-data-tester-r5hd4": Phase="Pending", Reason="", readiness=false. Elapsed: 16.271101564s
Jun 12 00:28:31.221: INFO: Pod "pvc-snapshottable-data-tester-r5hd4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.301991853s
STEP: Saw pod success
Jun 12 00:28:31.221: INFO: Pod "pvc-snapshottable-data-tester-r5hd4" satisfied condition "Succeeded or Failed"
Jun 12 00:28:31.281: INFO: Pod pvc-snapshottable-data-tester-r5hd4 has the following logs: 
Jun 12 00:28:31.281: INFO: Deleting pod "pvc-snapshottable-data-tester-r5hd4" in namespace "snapshotting-2036"
Jun 12 00:28:31.316: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-r5hd4" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 12 00:28:41.467: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-2036 exec restored-pvc-tester-xr97b --namespace=snapshotting-2036 -- cat /mnt/test/data'
... skipping 255 lines ...
    /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:108
      
      /tmp/kops.mVCl1cIaj/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.mVCl1cIaj/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-2036 exec restored-pvc-tester-xr97b --namespace=snapshotting-2036 -- 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-2036 exec restored-pvc-tester-xr97b --namespace=snapshotting-2036 -- 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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:602
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
... skipping 198 lines ...
Jun 12 00:29:18.487: INFO: Pod aws-client still exists
Jun 12 00:29:20.454: INFO: Waiting for pod aws-client to disappear
Jun 12 00:29:20.485: INFO: Pod aws-client still exists
Jun 12 00:29:22.454: INFO: Waiting for pod aws-client to disappear
Jun 12 00:29:22.485: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun 12 00:29:22.739: INFO: Couldn't delete PD "aws://us-east-2a/vol-085646e763bcbd0dc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-085646e763bcbd0dc is currently attached to i-08052264bd3923f8c
	status code: 400, request id: eb5859fd-52b8-435e-a6dd-c8fa016c9b61
Jun 12 00:29:28.012: INFO: Couldn't delete PD "aws://us-east-2a/vol-085646e763bcbd0dc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-085646e763bcbd0dc is currently attached to i-08052264bd3923f8c
	status code: 400, request id: e783683d-2a0f-4e54-b115-74f3387b16e9
Jun 12 00:29:33.292: INFO: Successfully deleted PD "aws://us-east-2a/vol-085646e763bcbd0dc".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 00:29:33.292: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-7023" for this suite.
... skipping 196 lines ...
Jun 12 00:28:28.207: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5198-e2e-scrxpj2
STEP: creating a claim
Jun 12 00:28:28.249: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-9jkj
STEP: Creating a pod to test atomic-volume-subpath
Jun 12 00:28:28.342: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-9jkj" in namespace "provisioning-5198" to be "Succeeded or Failed"
Jun 12 00:28:28.372: INFO: Pod "pod-subpath-test-dynamicpv-9jkj": Phase="Pending", Reason="", readiness=false. Elapsed: 29.545369ms
Jun 12 00:28:30.402: INFO: Pod "pod-subpath-test-dynamicpv-9jkj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.059822695s
Jun 12 00:28:32.438: INFO: Pod "pod-subpath-test-dynamicpv-9jkj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.095273594s
Jun 12 00:28:34.468: INFO: Pod "pod-subpath-test-dynamicpv-9jkj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.125413018s
Jun 12 00:28:36.499: INFO: Pod "pod-subpath-test-dynamicpv-9jkj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.156940289s
Jun 12 00:28:38.530: INFO: Pod "pod-subpath-test-dynamicpv-9jkj": Phase="Pending", Reason="", readiness=false. Elapsed: 10.18742881s
... skipping 11 lines ...
Jun 12 00:29:02.903: INFO: Pod "pod-subpath-test-dynamicpv-9jkj": Phase="Running", Reason="", readiness=true. Elapsed: 34.560810252s
Jun 12 00:29:04.933: INFO: Pod "pod-subpath-test-dynamicpv-9jkj": Phase="Running", Reason="", readiness=true. Elapsed: 36.590956616s
Jun 12 00:29:06.964: INFO: Pod "pod-subpath-test-dynamicpv-9jkj": Phase="Running", Reason="", readiness=true. Elapsed: 38.621334872s
Jun 12 00:29:08.995: INFO: Pod "pod-subpath-test-dynamicpv-9jkj": Phase="Running", Reason="", readiness=true. Elapsed: 40.652081137s
Jun 12 00:29:11.026: INFO: Pod "pod-subpath-test-dynamicpv-9jkj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 42.683141989s
STEP: Saw pod success
Jun 12 00:29:11.026: INFO: Pod "pod-subpath-test-dynamicpv-9jkj" satisfied condition "Succeeded or Failed"
Jun 12 00:29:11.064: INFO: Trying to get logs from node ip-172-20-56-193.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-9jkj container test-container-subpath-dynamicpv-9jkj: <nil>
STEP: delete the pod
Jun 12 00:29:11.134: INFO: Waiting for pod pod-subpath-test-dynamicpv-9jkj to disappear
Jun 12 00:29:11.163: INFO: Pod pod-subpath-test-dynamicpv-9jkj no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-9jkj
Jun 12 00:29:11.163: INFO: Deleting pod "pod-subpath-test-dynamicpv-9jkj" in namespace "provisioning-5198"
... skipping 229 lines ...
Jun 12 00:29:22.388: INFO: Creating resource for dynamic PV
Jun 12 00:29:22.388: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-3155fxkqr
STEP: creating a claim
STEP: Expanding non-expandable pvc
Jun 12 00:29:22.479: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 12 00:29:22.539: INFO: Error updating pvc awsfp9kd: PersistentVolumeClaim "awsfp9kd" 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-3155fxkqr",
  	... // 2 identical fields
  }

Jun 12 00:29:24.599: INFO: Error updating pvc awsfp9kd: PersistentVolumeClaim "awsfp9kd" 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-3155fxkqr",
  	... // 2 identical fields
  }

Jun 12 00:29:26.599: INFO: Error updating pvc awsfp9kd: PersistentVolumeClaim "awsfp9kd" 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-3155fxkqr",
  	... // 2 identical fields
  }

Jun 12 00:29:28.598: INFO: Error updating pvc awsfp9kd: PersistentVolumeClaim "awsfp9kd" 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-3155fxkqr",
  	... // 2 identical fields
  }

Jun 12 00:29:30.600: INFO: Error updating pvc awsfp9kd: PersistentVolumeClaim "awsfp9kd" 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-3155fxkqr",
  	... // 2 identical fields
  }

Jun 12 00:29:32.601: INFO: Error updating pvc awsfp9kd: PersistentVolumeClaim "awsfp9kd" 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-3155fxkqr",
  	... // 2 identical fields
  }

Jun 12 00:29:34.599: INFO: Error updating pvc awsfp9kd: PersistentVolumeClaim "awsfp9kd" 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-3155fxkqr",
  	... // 2 identical fields
  }

Jun 12 00:29:36.602: INFO: Error updating pvc awsfp9kd: PersistentVolumeClaim "awsfp9kd" 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-3155fxkqr",
  	... // 2 identical fields
  }

Jun 12 00:29:38.603: INFO: Error updating pvc awsfp9kd: PersistentVolumeClaim "awsfp9kd" 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-3155fxkqr",
  	... // 2 identical fields
  }

Jun 12 00:29:40.602: INFO: Error updating pvc awsfp9kd: PersistentVolumeClaim "awsfp9kd" 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-3155fxkqr",
  	... // 2 identical fields
  }

Jun 12 00:29:42.601: INFO: Error updating pvc awsfp9kd: PersistentVolumeClaim "awsfp9kd" 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-3155fxkqr",
  	... // 2 identical fields
  }

Jun 12 00:29:44.600: INFO: Error updating pvc awsfp9kd: PersistentVolumeClaim "awsfp9kd" 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-3155fxkqr",
  	... // 2 identical fields
  }

Jun 12 00:29:46.601: INFO: Error updating pvc awsfp9kd: PersistentVolumeClaim "awsfp9kd" 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-3155fxkqr",
  	... // 2 identical fields
  }

Jun 12 00:29:48.607: INFO: Error updating pvc awsfp9kd: PersistentVolumeClaim "awsfp9kd" 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-3155fxkqr",
  	... // 2 identical fields
  }

Jun 12 00:29:50.606: INFO: Error updating pvc awsfp9kd: PersistentVolumeClaim "awsfp9kd" 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-3155fxkqr",
  	... // 2 identical fields
  }

Jun 12 00:29:52.602: INFO: Error updating pvc awsfp9kd: PersistentVolumeClaim "awsfp9kd" 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-3155fxkqr",
  	... // 2 identical fields
  }

Jun 12 00:29:52.663: INFO: Error updating pvc awsfp9kd: PersistentVolumeClaim "awsfp9kd" 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 88 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 12 00:28:17.067: 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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun 12 00:28:17.227: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 12 00:28:17.227: INFO: Creating resource for dynamic PV
Jun 12 00:28:17.227: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9588j66m5
STEP: creating a claim
Jun 12 00:28:17.257: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-nf4r
STEP: Checking for subpath error in container status
Jun 12 00:29:33.418: INFO: Deleting pod "pod-subpath-test-dynamicpv-nf4r" in namespace "provisioning-9588"
Jun 12 00:29:33.449: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-nf4r" to be fully deleted
STEP: Deleting pod
Jun 12 00:29:45.508: INFO: Deleting pod "pod-subpath-test-dynamicpv-nf4r" in namespace "provisioning-9588"
STEP: Deleting pvc
Jun 12 00:29:45.608: INFO: Deleting PersistentVolumeClaim "awsj2wmb"
... skipping 12 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.mVCl1cIaj/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.mVCl1cIaj/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.mVCl1cIaj/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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 12 00:29:55.828: INFO: Driver aws doesn't support CSIInlineVolume -- skipping
[AfterEach] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral
... skipping 187 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.mVCl1cIaj/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.mVCl1cIaj/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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 25 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  /tmp/kops.mVCl1cIaj/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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

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

    /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 101 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.mVCl1cIaj/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.mVCl1cIaj/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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 128 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.mVCl1cIaj/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.mVCl1cIaj/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.mVCl1cIaj/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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 172 lines ...
Jun 12 00:29:33.811: INFO: PersistentVolumeClaim pvc-hv225 found but phase is Pending instead of Bound.
Jun 12 00:29:35.844: INFO: PersistentVolumeClaim pvc-hv225 found and phase=Bound (10.190006391s)
Jun 12 00:29:35.844: INFO: Waiting up to 3m0s for PersistentVolume aws-qk7r9 to have phase Bound
Jun 12 00:29:35.874: INFO: PersistentVolume aws-qk7r9 found and phase=Bound (29.92286ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-q9vp
STEP: Creating a pod to test exec-volume-test
Jun 12 00:29:35.965: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-q9vp" in namespace "volume-6491" to be "Succeeded or Failed"
Jun 12 00:29:35.995: INFO: Pod "exec-volume-test-preprovisionedpv-q9vp": Phase="Pending", Reason="", readiness=false. Elapsed: 30.689503ms
Jun 12 00:29:38.036: INFO: Pod "exec-volume-test-preprovisionedpv-q9vp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.071062722s
Jun 12 00:29:40.067: INFO: Pod "exec-volume-test-preprovisionedpv-q9vp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.102265604s
Jun 12 00:29:42.098: INFO: Pod "exec-volume-test-preprovisionedpv-q9vp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.133421746s
Jun 12 00:29:44.135: INFO: Pod "exec-volume-test-preprovisionedpv-q9vp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.170316266s
Jun 12 00:29:46.167: INFO: Pod "exec-volume-test-preprovisionedpv-q9vp": Phase="Pending", Reason="", readiness=false. Elapsed: 10.202218657s
Jun 12 00:29:48.199: INFO: Pod "exec-volume-test-preprovisionedpv-q9vp": Phase="Pending", Reason="", readiness=false. Elapsed: 12.233981485s
Jun 12 00:29:50.229: INFO: Pod "exec-volume-test-preprovisionedpv-q9vp": Phase="Pending", Reason="", readiness=false. Elapsed: 14.264689329s
Jun 12 00:29:52.261: INFO: Pod "exec-volume-test-preprovisionedpv-q9vp": Phase="Pending", Reason="", readiness=false. Elapsed: 16.296207874s
Jun 12 00:29:54.291: INFO: Pod "exec-volume-test-preprovisionedpv-q9vp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.326617189s
STEP: Saw pod success
Jun 12 00:29:54.291: INFO: Pod "exec-volume-test-preprovisionedpv-q9vp" satisfied condition "Succeeded or Failed"
Jun 12 00:29:54.327: INFO: Trying to get logs from node ip-172-20-56-193.us-east-2.compute.internal pod exec-volume-test-preprovisionedpv-q9vp container exec-container-preprovisionedpv-q9vp: <nil>
STEP: delete the pod
Jun 12 00:29:54.401: INFO: Waiting for pod exec-volume-test-preprovisionedpv-q9vp to disappear
Jun 12 00:29:54.431: INFO: Pod exec-volume-test-preprovisionedpv-q9vp no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-q9vp
Jun 12 00:29:54.431: INFO: Deleting pod "exec-volume-test-preprovisionedpv-q9vp" in namespace "volume-6491"
STEP: Deleting pv and pvc
Jun 12 00:29:54.461: INFO: Deleting PersistentVolumeClaim "pvc-hv225"
Jun 12 00:29:54.492: INFO: Deleting PersistentVolume "aws-qk7r9"
Jun 12 00:29:54.688: INFO: Couldn't delete PD "aws://us-east-2a/vol-0ed42bddb01e59844", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ed42bddb01e59844 is currently attached to i-08052264bd3923f8c
	status code: 400, request id: 113b8b06-b7ca-4664-84f4-b38e0385727c
Jun 12 00:29:59.981: INFO: Couldn't delete PD "aws://us-east-2a/vol-0ed42bddb01e59844", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ed42bddb01e59844 is currently attached to i-08052264bd3923f8c
	status code: 400, request id: 284c64f9-a605-401a-b150-53f76505403d
Jun 12 00:30:05.289: INFO: Couldn't delete PD "aws://us-east-2a/vol-0ed42bddb01e59844", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ed42bddb01e59844 is currently attached to i-08052264bd3923f8c
	status code: 400, request id: 00c35eed-afad-47aa-adc7-3cddffd66e1a
Jun 12 00:30:10.533: INFO: Couldn't delete PD "aws://us-east-2a/vol-0ed42bddb01e59844", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ed42bddb01e59844 is currently attached to i-08052264bd3923f8c
	status code: 400, request id: 1d2311b3-dfe3-4d08-9e89-16179dfeb53c
Jun 12 00:30:15.811: INFO: Successfully deleted PD "aws://us-east-2a/vol-0ed42bddb01e59844".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 00:30:15.811: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-6491" for this suite.
... skipping 23 lines ...
Jun 12 00:28:55.612: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4629-e2e-scch7tj
STEP: creating a claim
Jun 12 00:28:55.643: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-pmzp
STEP: Creating a pod to test subpath
Jun 12 00:28:55.739: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-pmzp" in namespace "provisioning-4629" to be "Succeeded or Failed"
Jun 12 00:28:55.770: INFO: Pod "pod-subpath-test-dynamicpv-pmzp": Phase="Pending", Reason="", readiness=false. Elapsed: 30.608539ms
Jun 12 00:28:57.801: INFO: Pod "pod-subpath-test-dynamicpv-pmzp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061978359s
Jun 12 00:28:59.833: INFO: Pod "pod-subpath-test-dynamicpv-pmzp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.094423891s
Jun 12 00:29:01.865: INFO: Pod "pod-subpath-test-dynamicpv-pmzp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.125874047s
Jun 12 00:29:03.896: INFO: Pod "pod-subpath-test-dynamicpv-pmzp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.157386404s
Jun 12 00:29:05.929: INFO: Pod "pod-subpath-test-dynamicpv-pmzp": Phase="Pending", Reason="", readiness=false. Elapsed: 10.189911206s
... skipping 3 lines ...
Jun 12 00:29:14.065: INFO: Pod "pod-subpath-test-dynamicpv-pmzp": Phase="Pending", Reason="", readiness=false. Elapsed: 18.326256787s
Jun 12 00:29:16.097: INFO: Pod "pod-subpath-test-dynamicpv-pmzp": Phase="Pending", Reason="", readiness=false. Elapsed: 20.357527218s
Jun 12 00:29:18.128: INFO: Pod "pod-subpath-test-dynamicpv-pmzp": Phase="Pending", Reason="", readiness=false. Elapsed: 22.388957801s
Jun 12 00:29:20.162: INFO: Pod "pod-subpath-test-dynamicpv-pmzp": Phase="Pending", Reason="", readiness=false. Elapsed: 24.423228086s
Jun 12 00:29:22.195: INFO: Pod "pod-subpath-test-dynamicpv-pmzp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.455567135s
STEP: Saw pod success
Jun 12 00:29:22.195: INFO: Pod "pod-subpath-test-dynamicpv-pmzp" satisfied condition "Succeeded or Failed"
Jun 12 00:29:22.225: INFO: Trying to get logs from node ip-172-20-54-191.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-pmzp container test-container-subpath-dynamicpv-pmzp: <nil>
STEP: delete the pod
Jun 12 00:29:22.298: INFO: Waiting for pod pod-subpath-test-dynamicpv-pmzp to disappear
Jun 12 00:29:22.330: INFO: Pod pod-subpath-test-dynamicpv-pmzp no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-pmzp
Jun 12 00:29:22.330: INFO: Deleting pod "pod-subpath-test-dynamicpv-pmzp" in namespace "provisioning-4629"
STEP: Creating pod pod-subpath-test-dynamicpv-pmzp
STEP: Creating a pod to test subpath
Jun 12 00:29:22.392: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-pmzp" in namespace "provisioning-4629" to be "Succeeded or Failed"
Jun 12 00:29:22.422: INFO: Pod "pod-subpath-test-dynamicpv-pmzp": Phase="Pending", Reason="", readiness=false. Elapsed: 30.76364ms
Jun 12 00:29:24.454: INFO: Pod "pod-subpath-test-dynamicpv-pmzp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062370189s
Jun 12 00:29:26.485: INFO: Pod "pod-subpath-test-dynamicpv-pmzp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.09353043s
Jun 12 00:29:28.517: INFO: Pod "pod-subpath-test-dynamicpv-pmzp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.124855083s
Jun 12 00:29:30.549: INFO: Pod "pod-subpath-test-dynamicpv-pmzp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.157007006s
Jun 12 00:29:32.581: INFO: Pod "pod-subpath-test-dynamicpv-pmzp": Phase="Pending", Reason="", readiness=false. Elapsed: 10.189561095s
... skipping 7 lines ...
Jun 12 00:29:48.837: INFO: Pod "pod-subpath-test-dynamicpv-pmzp": Phase="Pending", Reason="", readiness=false. Elapsed: 26.445753262s
Jun 12 00:29:50.869: INFO: Pod "pod-subpath-test-dynamicpv-pmzp": Phase="Pending", Reason="", readiness=false. Elapsed: 28.477770647s
Jun 12 00:29:52.901: INFO: Pod "pod-subpath-test-dynamicpv-pmzp": Phase="Pending", Reason="", readiness=false. Elapsed: 30.509481848s
Jun 12 00:29:54.933: INFO: Pod "pod-subpath-test-dynamicpv-pmzp": Phase="Pending", Reason="", readiness=false. Elapsed: 32.540933538s
Jun 12 00:29:56.965: INFO: Pod "pod-subpath-test-dynamicpv-pmzp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.57324235s
STEP: Saw pod success
Jun 12 00:29:56.965: INFO: Pod "pod-subpath-test-dynamicpv-pmzp" satisfied condition "Succeeded or Failed"
Jun 12 00:29:56.998: INFO: Trying to get logs from node ip-172-20-36-179.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-pmzp container test-container-subpath-dynamicpv-pmzp: <nil>
STEP: delete the pod
Jun 12 00:29:57.068: INFO: Waiting for pod pod-subpath-test-dynamicpv-pmzp to disappear
Jun 12 00:29:57.099: INFO: Pod pod-subpath-test-dynamicpv-pmzp no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-pmzp
Jun 12 00:29:57.099: INFO: Deleting pod "pod-subpath-test-dynamicpv-pmzp" in namespace "provisioning-4629"
... skipping 253 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 12 00:29:18.650: 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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun 12 00:29:18.814: INFO: Creating resource for dynamic PV
Jun 12 00:29:18.815: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9929-e2e-sctwhct
STEP: creating a claim
Jun 12 00:29:18.844: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-vr9x
STEP: Checking for subpath error in container status
Jun 12 00:29:34.993: INFO: Deleting pod "pod-subpath-test-dynamicpv-vr9x" in namespace "provisioning-9929"
Jun 12 00:29:35.023: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-vr9x" to be fully deleted
STEP: Deleting pod
Jun 12 00:29:47.083: INFO: Deleting pod "pod-subpath-test-dynamicpv-vr9x" in namespace "provisioning-9929"
STEP: Deleting pvc
Jun 12 00:29:47.172: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.coml46s5"
... skipping 15 lines ...

• [SLOW TEST:63.911 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath file is outside the volume [Slow][LinuxOnly]
    /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 12 00:30:22.563: INFO: Driver supports dynamic provisioning, skipping InlineVolume pattern
[AfterEach] [Testpattern: Inline-volume (default fs)] subPath
... skipping 4 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.mVCl1cIaj/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.mVCl1cIaj/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.mVCl1cIaj/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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 85 lines ...
Jun 12 00:28:38.432: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6296-e2e-sc9pzlv
STEP: creating a claim
Jun 12 00:28:38.462: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-rzx2
STEP: Creating a pod to test subpath
Jun 12 00:28:38.555: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-rzx2" in namespace "provisioning-6296" to be "Succeeded or Failed"
Jun 12 00:28:38.589: INFO: Pod "pod-subpath-test-dynamicpv-rzx2": Phase="Pending", Reason="", readiness=false. Elapsed: 33.974556ms
Jun 12 00:28:40.618: INFO: Pod "pod-subpath-test-dynamicpv-rzx2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.063421171s
Jun 12 00:28:42.647: INFO: Pod "pod-subpath-test-dynamicpv-rzx2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.092447639s
Jun 12 00:28:44.677: INFO: Pod "pod-subpath-test-dynamicpv-rzx2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.12190244s
Jun 12 00:28:46.707: INFO: Pod "pod-subpath-test-dynamicpv-rzx2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.152043695s
Jun 12 00:28:48.741: INFO: Pod "pod-subpath-test-dynamicpv-rzx2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.185958493s
... skipping 10 lines ...
Jun 12 00:29:11.069: INFO: Pod "pod-subpath-test-dynamicpv-rzx2": Phase="Pending", Reason="", readiness=false. Elapsed: 32.514181274s
Jun 12 00:29:13.099: INFO: Pod "pod-subpath-test-dynamicpv-rzx2": Phase="Pending", Reason="", readiness=false. Elapsed: 34.544599759s
Jun 12 00:29:15.133: INFO: Pod "pod-subpath-test-dynamicpv-rzx2": Phase="Pending", Reason="", readiness=false. Elapsed: 36.578723659s
Jun 12 00:29:17.163: INFO: Pod "pod-subpath-test-dynamicpv-rzx2": Phase="Pending", Reason="", readiness=false. Elapsed: 38.607867658s
Jun 12 00:29:19.193: INFO: Pod "pod-subpath-test-dynamicpv-rzx2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 40.638684957s
STEP: Saw pod success
Jun 12 00:29:19.193: INFO: Pod "pod-subpath-test-dynamicpv-rzx2" satisfied condition "Succeeded or Failed"
Jun 12 00:29:19.222: INFO: Trying to get logs from node ip-172-20-54-191.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-rzx2 container test-container-volume-dynamicpv-rzx2: <nil>
STEP: delete the pod
Jun 12 00:29:19.868: INFO: Waiting for pod pod-subpath-test-dynamicpv-rzx2 to disappear
Jun 12 00:29:19.897: INFO: Pod pod-subpath-test-dynamicpv-rzx2 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-rzx2
Jun 12 00:29:19.897: INFO: Deleting pod "pod-subpath-test-dynamicpv-rzx2" in namespace "provisioning-6296"
... skipping 45 lines ...
Jun 12 00:29:27.702: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-7756-e2e-sc4sgdm
STEP: creating a claim
Jun 12 00:29:27.732: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-x5r8
STEP: Creating a pod to test exec-volume-test
Jun 12 00:29:27.828: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-x5r8" in namespace "volume-7756" to be "Succeeded or Failed"
Jun 12 00:29:27.857: INFO: Pod "exec-volume-test-dynamicpv-x5r8": Phase="Pending", Reason="", readiness=false. Elapsed: 29.412161ms
Jun 12 00:29:29.888: INFO: Pod "exec-volume-test-dynamicpv-x5r8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.060075885s
Jun 12 00:29:31.917: INFO: Pod "exec-volume-test-dynamicpv-x5r8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.089445747s
Jun 12 00:29:33.948: INFO: Pod "exec-volume-test-dynamicpv-x5r8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.120002935s
Jun 12 00:29:35.981: INFO: Pod "exec-volume-test-dynamicpv-x5r8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.153364226s
Jun 12 00:29:38.011: INFO: Pod "exec-volume-test-dynamicpv-x5r8": Phase="Pending", Reason="", readiness=false. Elapsed: 10.183266529s
... skipping 2 lines ...
Jun 12 00:29:44.101: INFO: Pod "exec-volume-test-dynamicpv-x5r8": Phase="Pending", Reason="", readiness=false. Elapsed: 16.273242566s
Jun 12 00:29:46.131: INFO: Pod "exec-volume-test-dynamicpv-x5r8": Phase="Pending", Reason="", readiness=false. Elapsed: 18.30302352s
Jun 12 00:29:48.161: INFO: Pod "exec-volume-test-dynamicpv-x5r8": Phase="Pending", Reason="", readiness=false. Elapsed: 20.333401421s
Jun 12 00:29:50.191: INFO: Pod "exec-volume-test-dynamicpv-x5r8": Phase="Pending", Reason="", readiness=false. Elapsed: 22.363265918s
Jun 12 00:29:52.239: INFO: Pod "exec-volume-test-dynamicpv-x5r8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.411690429s
STEP: Saw pod success
Jun 12 00:29:52.239: INFO: Pod "exec-volume-test-dynamicpv-x5r8" satisfied condition "Succeeded or Failed"
Jun 12 00:29:52.268: INFO: Trying to get logs from node ip-172-20-54-191.us-east-2.compute.internal pod exec-volume-test-dynamicpv-x5r8 container exec-container-dynamicpv-x5r8: <nil>
STEP: delete the pod
Jun 12 00:29:52.338: INFO: Waiting for pod exec-volume-test-dynamicpv-x5r8 to disappear
Jun 12 00:29:52.368: INFO: Pod exec-volume-test-dynamicpv-x5r8 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-x5r8
Jun 12 00:29:52.368: INFO: Deleting pod "exec-volume-test-dynamicpv-x5r8" in namespace "volume-7756"
... skipping 58 lines ...
Jun 12 00:29:47.454: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1760-e2e-sczrr87
STEP: creating a claim
Jun 12 00:29:47.485: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-swsz
STEP: Creating a pod to test subpath
Jun 12 00:29:47.587: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-swsz" in namespace "provisioning-1760" to be "Succeeded or Failed"
Jun 12 00:29:47.617: INFO: Pod "pod-subpath-test-dynamicpv-swsz": Phase="Pending", Reason="", readiness=false. Elapsed: 30.071432ms
Jun 12 00:29:49.648: INFO: Pod "pod-subpath-test-dynamicpv-swsz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.060410615s
Jun 12 00:29:51.680: INFO: Pod "pod-subpath-test-dynamicpv-swsz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.093050941s
Jun 12 00:29:53.710: INFO: Pod "pod-subpath-test-dynamicpv-swsz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.12314101s
Jun 12 00:29:55.742: INFO: Pod "pod-subpath-test-dynamicpv-swsz": Phase="Pending", Reason="", readiness=false. Elapsed: 8.155276873s
Jun 12 00:29:57.772: INFO: Pod "pod-subpath-test-dynamicpv-swsz": Phase="Pending", Reason="", readiness=false. Elapsed: 10.18501529s
Jun 12 00:29:59.804: INFO: Pod "pod-subpath-test-dynamicpv-swsz": Phase="Pending", Reason="", readiness=false. Elapsed: 12.217180265s
Jun 12 00:30:01.835: INFO: Pod "pod-subpath-test-dynamicpv-swsz": Phase="Pending", Reason="", readiness=false. Elapsed: 14.24773482s
Jun 12 00:30:03.866: INFO: Pod "pod-subpath-test-dynamicpv-swsz": Phase="Pending", Reason="", readiness=false. Elapsed: 16.278690841s
Jun 12 00:30:05.896: INFO: Pod "pod-subpath-test-dynamicpv-swsz": Phase="Pending", Reason="", readiness=false. Elapsed: 18.309144597s
Jun 12 00:30:07.927: INFO: Pod "pod-subpath-test-dynamicpv-swsz": Phase="Pending", Reason="", readiness=false. Elapsed: 20.339737354s
Jun 12 00:30:09.965: INFO: Pod "pod-subpath-test-dynamicpv-swsz": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.378103232s
STEP: Saw pod success
Jun 12 00:30:09.965: INFO: Pod "pod-subpath-test-dynamicpv-swsz" satisfied condition "Succeeded or Failed"
Jun 12 00:30:09.995: INFO: Trying to get logs from node ip-172-20-36-179.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-swsz container test-container-subpath-dynamicpv-swsz: <nil>
STEP: delete the pod
Jun 12 00:30:10.080: INFO: Waiting for pod pod-subpath-test-dynamicpv-swsz to disappear
Jun 12 00:30:10.115: INFO: Pod pod-subpath-test-dynamicpv-swsz no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-swsz
Jun 12 00:30:10.115: INFO: Deleting pod "pod-subpath-test-dynamicpv-swsz" in namespace "provisioning-1760"
... skipping 52 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.mVCl1cIaj/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.mVCl1cIaj/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.mVCl1cIaj/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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 29 lines ...
Jun 12 00:29:55.983: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 12 00:29:56.358: INFO: Successfully created a new PD: "aws://us-east-2a/vol-0a1b8c3a65a9842e8".
Jun 12 00:29:56.359: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-6s5c
STEP: Creating a pod to test exec-volume-test
Jun 12 00:29:56.390: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-6s5c" in namespace "volume-1822" to be "Succeeded or Failed"
Jun 12 00:29:56.419: INFO: Pod "exec-volume-test-inlinevolume-6s5c": Phase="Pending", Reason="", readiness=false. Elapsed: 28.996929ms
Jun 12 00:29:58.449: INFO: Pod "exec-volume-test-inlinevolume-6s5c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.058956274s
Jun 12 00:30:00.480: INFO: Pod "exec-volume-test-inlinevolume-6s5c": Phase="Pending", Reason="", readiness=false. Elapsed: 4.09004464s
Jun 12 00:30:02.510: INFO: Pod "exec-volume-test-inlinevolume-6s5c": Phase="Pending", Reason="", readiness=false. Elapsed: 6.119979281s
Jun 12 00:30:04.540: INFO: Pod "exec-volume-test-inlinevolume-6s5c": Phase="Pending", Reason="", readiness=false. Elapsed: 8.149627423s
Jun 12 00:30:06.570: INFO: Pod "exec-volume-test-inlinevolume-6s5c": Phase="Pending", Reason="", readiness=false. Elapsed: 10.179460164s
Jun 12 00:30:08.599: INFO: Pod "exec-volume-test-inlinevolume-6s5c": Phase="Pending", Reason="", readiness=false. Elapsed: 12.209038859s
Jun 12 00:30:10.640: INFO: Pod "exec-volume-test-inlinevolume-6s5c": Phase="Pending", Reason="", readiness=false. Elapsed: 14.249766307s
Jun 12 00:30:12.670: INFO: Pod "exec-volume-test-inlinevolume-6s5c": Phase="Pending", Reason="", readiness=false. Elapsed: 16.279650786s
Jun 12 00:30:14.701: INFO: Pod "exec-volume-test-inlinevolume-6s5c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.310468264s
STEP: Saw pod success
Jun 12 00:30:14.701: INFO: Pod "exec-volume-test-inlinevolume-6s5c" satisfied condition "Succeeded or Failed"
Jun 12 00:30:14.731: INFO: Trying to get logs from node ip-172-20-56-193.us-east-2.compute.internal pod exec-volume-test-inlinevolume-6s5c container exec-container-inlinevolume-6s5c: <nil>
STEP: delete the pod
Jun 12 00:30:14.802: INFO: Waiting for pod exec-volume-test-inlinevolume-6s5c to disappear
Jun 12 00:30:14.831: INFO: Pod exec-volume-test-inlinevolume-6s5c no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-6s5c
Jun 12 00:30:14.831: INFO: Deleting pod "exec-volume-test-inlinevolume-6s5c" in namespace "volume-1822"
Jun 12 00:30:14.985: INFO: Couldn't delete PD "aws://us-east-2a/vol-0a1b8c3a65a9842e8", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a1b8c3a65a9842e8 is currently attached to i-08052264bd3923f8c
	status code: 400, request id: 810851df-06fe-4f31-8b7d-40aa027058dc
Jun 12 00:30:20.240: INFO: Couldn't delete PD "aws://us-east-2a/vol-0a1b8c3a65a9842e8", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a1b8c3a65a9842e8 is currently attached to i-08052264bd3923f8c
	status code: 400, request id: bc22304b-b98a-41a9-9f1a-5c80f0423347
Jun 12 00:30:25.487: INFO: Couldn't delete PD "aws://us-east-2a/vol-0a1b8c3a65a9842e8", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a1b8c3a65a9842e8 is currently attached to i-08052264bd3923f8c
	status code: 400, request id: d59babbb-b724-4396-9951-d73c31593180
Jun 12 00:30:30.746: INFO: Successfully deleted PD "aws://us-east-2a/vol-0a1b8c3a65a9842e8".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 00:30:30.746: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-1822" for this suite.
... skipping 114 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.mVCl1cIaj/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.mVCl1cIaj/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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 127 lines ...
Jun 12 00:28:35.397: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-1860-e2e-scn724n      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-1860    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-1860-e2e-scn724n,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-1860    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-1860-e2e-scn724n,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-1860    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-1860-e2e-scn724n,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-1860-e2e-scn724n    bac096c5-2dbd-4533-9ea0-ea051e3b3cc1 9472 0 2021-06-12 00:28:35 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-12 00:28:35 +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-df6tq pvc- provisioning-1860  2c01cb71-826c-47cb-80e0-475bb3015abd 9476 0 2021-06-12 00:28:35 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-12 00:28:35 +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-1860-e2e-scn724n,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-f2f8d69d-90b4-4fcf-b358-f79031d3d37c in namespace provisioning-1860
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun 12 00:28:49.736: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-m9rzz" in namespace "provisioning-1860" to be "Succeeded or Failed"
Jun 12 00:28:49.765: INFO: Pod "pvc-volume-tester-writer-m9rzz": Phase="Pending", Reason="", readiness=false. Elapsed: 29.502731ms
Jun 12 00:28:51.795: INFO: Pod "pvc-volume-tester-writer-m9rzz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.059794524s
Jun 12 00:28:53.826: INFO: Pod "pvc-volume-tester-writer-m9rzz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.090446228s
Jun 12 00:28:55.857: INFO: Pod "pvc-volume-tester-writer-m9rzz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.121650293s
Jun 12 00:28:57.888: INFO: Pod "pvc-volume-tester-writer-m9rzz": Phase="Pending", Reason="", readiness=false. Elapsed: 8.152677827s
Jun 12 00:28:59.923: INFO: Pod "pvc-volume-tester-writer-m9rzz": Phase="Pending", Reason="", readiness=false. Elapsed: 10.187074176s
... skipping 7 lines ...
Jun 12 00:29:16.165: INFO: Pod "pvc-volume-tester-writer-m9rzz": Phase="Pending", Reason="", readiness=false. Elapsed: 26.42944233s
Jun 12 00:29:18.197: INFO: Pod "pvc-volume-tester-writer-m9rzz": Phase="Pending", Reason="", readiness=false. Elapsed: 28.46106625s
Jun 12 00:29:20.228: INFO: Pod "pvc-volume-tester-writer-m9rzz": Phase="Pending", Reason="", readiness=false. Elapsed: 30.491929392s
Jun 12 00:29:22.258: INFO: Pod "pvc-volume-tester-writer-m9rzz": Phase="Pending", Reason="", readiness=false. Elapsed: 32.522220211s
Jun 12 00:29:24.289: INFO: Pod "pvc-volume-tester-writer-m9rzz": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.553284528s
STEP: Saw pod success
Jun 12 00:29:24.289: INFO: Pod "pvc-volume-tester-writer-m9rzz" satisfied condition "Succeeded or Failed"
Jun 12 00:29:24.350: INFO: Pod pvc-volume-tester-writer-m9rzz has the following logs: 
Jun 12 00:29:24.350: INFO: Deleting pod "pvc-volume-tester-writer-m9rzz" in namespace "provisioning-1860"
Jun 12 00:29:24.385: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-m9rzz" 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-54-191.us-east-2.compute.internal"
Jun 12 00:29:24.512: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-zmng8" in namespace "provisioning-1860" to be "Succeeded or Failed"
Jun 12 00:29:24.542: INFO: Pod "pvc-volume-tester-reader-zmng8": Phase="Pending", Reason="", readiness=false. Elapsed: 29.856591ms
Jun 12 00:29:26.571: INFO: Pod "pvc-volume-tester-reader-zmng8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.059714937s
Jun 12 00:29:28.601: INFO: Pod "pvc-volume-tester-reader-zmng8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.089459013s
Jun 12 00:29:30.631: INFO: Pod "pvc-volume-tester-reader-zmng8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.119648178s
STEP: Saw pod success
Jun 12 00:29:30.631: INFO: Pod "pvc-volume-tester-reader-zmng8" satisfied condition "Succeeded or Failed"
Jun 12 00:29:30.692: INFO: Pod pvc-volume-tester-reader-zmng8 has the following logs: hello world

Jun 12 00:29:30.692: INFO: Deleting pod "pvc-volume-tester-reader-zmng8" in namespace "provisioning-1860"
Jun 12 00:29:30.728: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-zmng8" to be fully deleted
Jun 12 00:29:30.758: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-df6tq] to have phase Bound
Jun 12 00:29:30.787: INFO: PersistentVolumeClaim pvc-df6tq found and phase=Bound (29.424262ms)
... skipping 240 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 12 00:30:22.788: 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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 12 00:30:22.932: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 12 00:30:23.342: INFO: Successfully created a new PD: "aws://us-east-2a/vol-08707c326d0baca82".
Jun 12 00:30:23.342: INFO: Creating resource for pre-provisioned PV
Jun 12 00:30:23.342: INFO: Creating PVC and PV
... skipping 7 lines ...
Jun 12 00:30:31.635: INFO: PersistentVolumeClaim pvc-256rn found but phase is Pending instead of Bound.
Jun 12 00:30:33.664: INFO: PersistentVolumeClaim pvc-256rn found but phase is Pending instead of Bound.
Jun 12 00:30:35.696: INFO: PersistentVolumeClaim pvc-256rn found and phase=Bound (12.21174791s)
Jun 12 00:30:35.696: INFO: Waiting up to 3m0s for PersistentVolume aws-6mkcd to have phase Bound
Jun 12 00:30:35.726: INFO: PersistentVolume aws-6mkcd found and phase=Bound (29.86831ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 12 00:30:37.908: INFO: Deleting pod "pod-99cbba98-a4cb-472d-ac15-80bd569f7ce6" in namespace "volumemode-4087"
Jun 12 00:30:37.949: INFO: Wait up to 5m0s for pod "pod-99cbba98-a4cb-472d-ac15-80bd569f7ce6" to be fully deleted
STEP: Deleting pv and pvc
Jun 12 00:30:42.014: INFO: Deleting PersistentVolumeClaim "pvc-256rn"
Jun 12 00:30:42.046: INFO: Deleting PersistentVolume "aws-6mkcd"
Jun 12 00:30:42.328: INFO: Couldn't delete PD "aws://us-east-2a/vol-08707c326d0baca82", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08707c326d0baca82 is currently attached to i-04c4a604524f7b63b
	status code: 400, request id: f283ce33-7868-4e73-b50a-5cfc1f4977d1
Jun 12 00:30:47.577: INFO: Couldn't delete PD "aws://us-east-2a/vol-08707c326d0baca82", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08707c326d0baca82 is currently attached to i-04c4a604524f7b63b
	status code: 400, request id: b3a5503c-0a0d-4928-8d18-2556da8a0731
Jun 12 00:30:52.838: INFO: Successfully deleted PD "aws://us-east-2a/vol-08707c326d0baca82".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 00:30:52.839: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-4087" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.mVCl1cIaj/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.mVCl1cIaj/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
    /tmp/kops.mVCl1cIaj/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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 12 00:30:52.903: INFO: Driver "ebs.csi.aws.com" does not support volume type "CSIInlineVolume" - skipping
[AfterEach] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral
... skipping 23 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.mVCl1cIaj/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.mVCl1cIaj/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.mVCl1cIaj/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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 124 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 12 00:29:33.593: 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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 12 00:29:33.759: INFO: Creating resource for dynamic PV
Jun 12 00:29:33.759: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-890-e2e-scgkhvq
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 12 00:29:39.993: INFO: Deleting pod "pod-228e1d80-57ae-4bcd-a638-f91b69a5ba86" in namespace "volumemode-890"
Jun 12 00:29:40.025: INFO: Wait up to 5m0s for pod "pod-228e1d80-57ae-4bcd-a638-f91b69a5ba86" to be fully deleted
STEP: Deleting pvc
Jun 12 00:29:48.149: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com822sk"
Jun 12 00:29:48.181: INFO: Waiting up to 5m0s for PersistentVolume pvc-74460534-9adc-474b-b103-58aeef973060 to get deleted
Jun 12 00:29:48.212: INFO: PersistentVolume pvc-74460534-9adc-474b-b103-58aeef973060 found and phase=Released (30.612863ms)
... skipping 19 lines ...

• [SLOW TEST:80.142 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.mVCl1cIaj/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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 12 00:30:53.737: INFO: Driver supports dynamic provisioning, skipping PreprovisionedPV pattern
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
... skipping 178 lines ...
Jun 12 00:30:36.618: INFO: Creating resource for dynamic PV
Jun 12 00:30:36.618: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-1439-e2e-scpg6vl
STEP: creating a claim
STEP: Expanding non-expandable pvc
Jun 12 00:30:36.717: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 12 00:30:36.779: INFO: Error updating pvc ebs.csi.aws.comftgrd: PersistentVolumeClaim "ebs.csi.aws.comftgrd" 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-1439-e2e-scpg6vl",
  	... // 2 identical fields
  }

Jun 12 00:30:38.841: INFO: Error updating pvc ebs.csi.aws.comftgrd: PersistentVolumeClaim "ebs.csi.aws.comftgrd" 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-1439-e2e-scpg6vl",
  	... // 2 identical fields
  }

Jun 12 00:30:40.840: INFO: Error updating pvc ebs.csi.aws.comftgrd: PersistentVolumeClaim "ebs.csi.aws.comftgrd" 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-1439-e2e-scpg6vl",
  	... // 2 identical fields
  }

Jun 12 00:30:42.841: INFO: Error updating pvc ebs.csi.aws.comftgrd: PersistentVolumeClaim "ebs.csi.aws.comftgrd" 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-1439-e2e-scpg6vl",
  	... // 2 identical fields
  }

Jun 12 00:30:44.843: INFO: Error updating pvc ebs.csi.aws.comftgrd: PersistentVolumeClaim "ebs.csi.aws.comftgrd" 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-1439-e2e-scpg6vl",
  	... // 2 identical fields
  }

Jun 12 00:30:46.849: INFO: Error updating pvc ebs.csi.aws.comftgrd: PersistentVolumeClaim "ebs.csi.aws.comftgrd" 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-1439-e2e-scpg6vl",
  	... // 2 identical fields
  }

Jun 12 00:30:48.840: INFO: Error updating pvc ebs.csi.aws.comftgrd: PersistentVolumeClaim "ebs.csi.aws.comftgrd" 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-1439-e2e-scpg6vl",
  	... // 2 identical fields
  }

Jun 12 00:30:50.840: INFO: Error updating pvc ebs.csi.aws.comftgrd: PersistentVolumeClaim "ebs.csi.aws.comftgrd" 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-1439-e2e-scpg6vl",
  	... // 2 identical fields
  }

Jun 12 00:30:52.840: INFO: Error updating pvc ebs.csi.aws.comftgrd: PersistentVolumeClaim "ebs.csi.aws.comftgrd" 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-1439-e2e-scpg6vl",
  	... // 2 identical fields
  }

Jun 12 00:30:54.842: INFO: Error updating pvc ebs.csi.aws.comftgrd: PersistentVolumeClaim "ebs.csi.aws.comftgrd" 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-1439-e2e-scpg6vl",
  	... // 2 identical fields
  }

Jun 12 00:30:56.841: INFO: Error updating pvc ebs.csi.aws.comftgrd: PersistentVolumeClaim "ebs.csi.aws.comftgrd" 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-1439-e2e-scpg6vl",
  	... // 2 identical fields
  }

Jun 12 00:30:58.847: INFO: Error updating pvc ebs.csi.aws.comftgrd: PersistentVolumeClaim "ebs.csi.aws.comftgrd" 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-1439-e2e-scpg6vl",
  	... // 2 identical fields
  }

Jun 12 00:31:00.840: INFO: Error updating pvc ebs.csi.aws.comftgrd: PersistentVolumeClaim "ebs.csi.aws.comftgrd" 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-1439-e2e-scpg6vl",
  	... // 2 identical fields
  }

Jun 12 00:31:02.840: INFO: Error updating pvc ebs.csi.aws.comftgrd: PersistentVolumeClaim "ebs.csi.aws.comftgrd" 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-1439-e2e-scpg6vl",
  	... // 2 identical fields
  }

Jun 12 00:31:04.840: INFO: Error updating pvc ebs.csi.aws.comftgrd: PersistentVolumeClaim "ebs.csi.aws.comftgrd" 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-1439-e2e-scpg6vl",
  	... // 2 identical fields
  }

Jun 12 00:31:06.848: INFO: Error updating pvc ebs.csi.aws.comftgrd: PersistentVolumeClaim "ebs.csi.aws.comftgrd" 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-1439-e2e-scpg6vl",
  	... // 2 identical fields
  }

Jun 12 00:31:06.911: INFO: Error updating pvc ebs.csi.aws.comftgrd: PersistentVolumeClaim "ebs.csi.aws.comftgrd" 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 111 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.mVCl1cIaj/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.mVCl1cIaj/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.mVCl1cIaj/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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 839 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 12 00:30:51.082: 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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun 12 00:30:51.237: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 12 00:30:51.237: INFO: Creating resource for dynamic PV
Jun 12 00:30:51.237: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-27572gjr6
STEP: creating a claim
Jun 12 00:30:51.268: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-dzjg
STEP: Checking for subpath error in container status
Jun 12 00:31:03.429: INFO: Deleting pod "pod-subpath-test-dynamicpv-dzjg" in namespace "provisioning-2757"
Jun 12 00:31:03.464: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-dzjg" to be fully deleted
STEP: Deleting pod
Jun 12 00:31:15.524: INFO: Deleting pod "pod-subpath-test-dynamicpv-dzjg" in namespace "provisioning-2757"
STEP: Deleting pvc
Jun 12 00:31:15.614: INFO: Deleting PersistentVolumeClaim "awsb7xmh"
... skipping 11 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.mVCl1cIaj/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.mVCl1cIaj/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.mVCl1cIaj/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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 12 00:31:20.812: INFO: Driver supports dynamic provisioning, skipping PreprovisionedPV pattern
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
... skipping 4 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.mVCl1cIaj/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.mVCl1cIaj/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.mVCl1cIaj/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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 12 lines ...
Jun 12 00:30:54.152: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-677w6m94
STEP: creating a claim
Jun 12 00:30:54.183: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-lm8g
STEP: Creating a pod to test subpath
Jun 12 00:30:54.282: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-lm8g" in namespace "provisioning-677" to be "Succeeded or Failed"
Jun 12 00:30:54.313: INFO: Pod "pod-subpath-test-dynamicpv-lm8g": Phase="Pending", Reason="", readiness=false. Elapsed: 30.744722ms
Jun 12 00:30:56.347: INFO: Pod "pod-subpath-test-dynamicpv-lm8g": Phase="Pending", Reason="", readiness=false. Elapsed: 2.065363635s
Jun 12 00:30:58.379: INFO: Pod "pod-subpath-test-dynamicpv-lm8g": Phase="Pending", Reason="", readiness=false. Elapsed: 4.097486129s
Jun 12 00:31:00.413: INFO: Pod "pod-subpath-test-dynamicpv-lm8g": Phase="Pending", Reason="", readiness=false. Elapsed: 6.130668964s
Jun 12 00:31:02.448: INFO: Pod "pod-subpath-test-dynamicpv-lm8g": Phase="Pending", Reason="", readiness=false. Elapsed: 8.16648084s
Jun 12 00:31:04.479: INFO: Pod "pod-subpath-test-dynamicpv-lm8g": Phase="Pending", Reason="", readiness=false. Elapsed: 10.197560377s
Jun 12 00:31:06.511: INFO: Pod "pod-subpath-test-dynamicpv-lm8g": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.228944253s
STEP: Saw pod success
Jun 12 00:31:06.511: INFO: Pod "pod-subpath-test-dynamicpv-lm8g" satisfied condition "Succeeded or Failed"
Jun 12 00:31:06.541: INFO: Trying to get logs from node ip-172-20-56-132.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-lm8g container test-container-subpath-dynamicpv-lm8g: <nil>
STEP: delete the pod
Jun 12 00:31:06.648: INFO: Waiting for pod pod-subpath-test-dynamicpv-lm8g to disappear
Jun 12 00:31:06.685: INFO: Pod pod-subpath-test-dynamicpv-lm8g no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-lm8g
Jun 12 00:31:06.685: INFO: Deleting pod "pod-subpath-test-dynamicpv-lm8g" in namespace "provisioning-677"
... skipping 160 lines ...
Jun 12 00:29:59.165: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1466pgr8f
STEP: creating a claim
Jun 12 00:29:59.195: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-7lr2
STEP: Creating a pod to test atomic-volume-subpath
Jun 12 00:29:59.288: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-7lr2" in namespace "provisioning-1466" to be "Succeeded or Failed"
Jun 12 00:29:59.323: INFO: Pod "pod-subpath-test-dynamicpv-7lr2": Phase="Pending", Reason="", readiness=false. Elapsed: 34.9646ms
Jun 12 00:30:01.353: INFO: Pod "pod-subpath-test-dynamicpv-7lr2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.065330701s
Jun 12 00:30:03.384: INFO: Pod "pod-subpath-test-dynamicpv-7lr2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.095800458s
Jun 12 00:30:05.414: INFO: Pod "pod-subpath-test-dynamicpv-7lr2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.126113087s
Jun 12 00:30:07.445: INFO: Pod "pod-subpath-test-dynamicpv-7lr2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.156810735s
Jun 12 00:30:09.477: INFO: Pod "pod-subpath-test-dynamicpv-7lr2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.188668314s
... skipping 19 lines ...
Jun 12 00:30:50.123: INFO: Pod "pod-subpath-test-dynamicpv-7lr2": Phase="Running", Reason="", readiness=true. Elapsed: 50.834551918s
Jun 12 00:30:52.155: INFO: Pod "pod-subpath-test-dynamicpv-7lr2": Phase="Running", Reason="", readiness=true. Elapsed: 52.866564591s
Jun 12 00:30:54.185: INFO: Pod "pod-subpath-test-dynamicpv-7lr2": Phase="Running", Reason="", readiness=true. Elapsed: 54.897392908s
Jun 12 00:30:56.217: INFO: Pod "pod-subpath-test-dynamicpv-7lr2": Phase="Running", Reason="", readiness=true. Elapsed: 56.928486699s
Jun 12 00:30:58.248: INFO: Pod "pod-subpath-test-dynamicpv-7lr2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 58.959587651s
STEP: Saw pod success
Jun 12 00:30:58.248: INFO: Pod "pod-subpath-test-dynamicpv-7lr2" satisfied condition "Succeeded or Failed"
Jun 12 00:30:58.282: INFO: Trying to get logs from node ip-172-20-56-193.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-7lr2 container test-container-subpath-dynamicpv-7lr2: <nil>
STEP: delete the pod
Jun 12 00:30:58.359: INFO: Waiting for pod pod-subpath-test-dynamicpv-7lr2 to disappear
Jun 12 00:30:58.391: INFO: Pod pod-subpath-test-dynamicpv-7lr2 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-7lr2
Jun 12 00:30:58.391: INFO: Deleting pod "pod-subpath-test-dynamicpv-7lr2" in namespace "provisioning-1466"
... skipping 49 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 12 00:30:52.910: 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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun 12 00:30:53.062: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 12 00:30:53.062: INFO: Creating resource for dynamic PV
Jun 12 00:30:53.064: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6043vrr5l
STEP: creating a claim
Jun 12 00:30:53.094: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-7lwk
STEP: Checking for subpath error in container status
Jun 12 00:31:07.246: INFO: Deleting pod "pod-subpath-test-dynamicpv-7lwk" in namespace "provisioning-6043"
Jun 12 00:31:07.282: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-7lwk" to be fully deleted
STEP: Deleting pod
Jun 12 00:31:17.343: INFO: Deleting pod "pod-subpath-test-dynamicpv-7lwk" in namespace "provisioning-6043"
STEP: Deleting pvc
Jun 12 00:31:17.429: INFO: Deleting PersistentVolumeClaim "awssznlp"
... skipping 12 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.mVCl1cIaj/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.mVCl1cIaj/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath file is outside the volume [Slow][LinuxOnly]
      /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] provisioning
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] provisioning
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 196 lines ...
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 12 00:31:28.091: 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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Jun 12 00:31:28.272: INFO: found topology map[topology.kubernetes.io/zone:us-east-2a]
Jun 12 00:31:28.272: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 12 00:31:28.272: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.mVCl1cIaj/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.mVCl1cIaj/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (delayed binding)] topology
    /tmp/kops.mVCl1cIaj/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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 161 lines ...
Jun 12 00:30:13.435: INFO: Creating resource for dynamic PV
Jun 12 00:30:13.435: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9736-e2e-sc27txh
STEP: creating a claim
Jun 12 00:30:13.467: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-9736
Jun 12 00:30:13.561: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-9736" in namespace "provisioning-9736" to be "Succeeded or Failed"
Jun 12 00:30:13.591: INFO: Pod "volume-prep-provisioning-9736": Phase="Pending", Reason="", readiness=false. Elapsed: 29.716854ms
Jun 12 00:30:15.622: INFO: Pod "volume-prep-provisioning-9736": Phase="Pending", Reason="", readiness=false. Elapsed: 2.060538813s
Jun 12 00:30:17.656: INFO: Pod "volume-prep-provisioning-9736": Phase="Pending", Reason="", readiness=false. Elapsed: 4.094331478s
Jun 12 00:30:19.688: INFO: Pod "volume-prep-provisioning-9736": Phase="Pending", Reason="", readiness=false. Elapsed: 6.126244665s
Jun 12 00:30:21.726: INFO: Pod "volume-prep-provisioning-9736": Phase="Pending", Reason="", readiness=false. Elapsed: 8.164302765s
Jun 12 00:30:23.756: INFO: Pod "volume-prep-provisioning-9736": Phase="Pending", Reason="", readiness=false. Elapsed: 10.194527621s
Jun 12 00:30:25.787: INFO: Pod "volume-prep-provisioning-9736": Phase="Pending", Reason="", readiness=false. Elapsed: 12.225545402s
Jun 12 00:30:27.820: INFO: Pod "volume-prep-provisioning-9736": Phase="Pending", Reason="", readiness=false. Elapsed: 14.259052834s
Jun 12 00:30:29.851: INFO: Pod "volume-prep-provisioning-9736": Phase="Pending", Reason="", readiness=false. Elapsed: 16.289499384s
Jun 12 00:30:31.882: INFO: Pod "volume-prep-provisioning-9736": Phase="Pending", Reason="", readiness=false. Elapsed: 18.320404735s
Jun 12 00:30:33.913: INFO: Pod "volume-prep-provisioning-9736": Phase="Pending", Reason="", readiness=false. Elapsed: 20.352001684s
Jun 12 00:30:35.945: INFO: Pod "volume-prep-provisioning-9736": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.383562497s
STEP: Saw pod success
Jun 12 00:30:35.945: INFO: Pod "volume-prep-provisioning-9736" satisfied condition "Succeeded or Failed"
Jun 12 00:30:35.945: INFO: Deleting pod "volume-prep-provisioning-9736" in namespace "provisioning-9736"
Jun 12 00:30:35.980: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-9736" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-29gr
STEP: Checking for subpath error in container status
Jun 12 00:30:56.107: INFO: Deleting pod "pod-subpath-test-dynamicpv-29gr" in namespace "provisioning-9736"
Jun 12 00:30:56.143: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-29gr" to be fully deleted
STEP: Deleting pod
Jun 12 00:30:56.173: INFO: Deleting pod "pod-subpath-test-dynamicpv-29gr" in namespace "provisioning-9736"
STEP: Deleting pvc
Jun 12 00:30:56.263: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comxzpzc"
... skipping 141 lines ...
Jun 12 00:31:08.138: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5971hm6wl
STEP: creating a claim
Jun 12 00:31:08.168: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-qgpn
STEP: Creating a pod to test subpath
Jun 12 00:31:08.260: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-qgpn" in namespace "provisioning-5971" to be "Succeeded or Failed"
Jun 12 00:31:08.290: INFO: Pod "pod-subpath-test-dynamicpv-qgpn": Phase="Pending", Reason="", readiness=false. Elapsed: 29.824708ms
Jun 12 00:31:10.323: INFO: Pod "pod-subpath-test-dynamicpv-qgpn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062431378s
Jun 12 00:31:12.358: INFO: Pod "pod-subpath-test-dynamicpv-qgpn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.097521742s
Jun 12 00:31:14.389: INFO: Pod "pod-subpath-test-dynamicpv-qgpn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.128498333s
Jun 12 00:31:16.420: INFO: Pod "pod-subpath-test-dynamicpv-qgpn": Phase="Pending", Reason="", readiness=false. Elapsed: 8.159610024s
Jun 12 00:31:18.451: INFO: Pod "pod-subpath-test-dynamicpv-qgpn": Phase="Pending", Reason="", readiness=false. Elapsed: 10.190988952s
Jun 12 00:31:20.488: INFO: Pod "pod-subpath-test-dynamicpv-qgpn": Phase="Pending", Reason="", readiness=false. Elapsed: 12.227388958s
Jun 12 00:31:22.520: INFO: Pod "pod-subpath-test-dynamicpv-qgpn": Phase="Pending", Reason="", readiness=false. Elapsed: 14.259207107s
Jun 12 00:31:24.550: INFO: Pod "pod-subpath-test-dynamicpv-qgpn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.289522679s
STEP: Saw pod success
Jun 12 00:31:24.550: INFO: Pod "pod-subpath-test-dynamicpv-qgpn" satisfied condition "Succeeded or Failed"
Jun 12 00:31:24.580: INFO: Trying to get logs from node ip-172-20-36-179.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-qgpn container test-container-volume-dynamicpv-qgpn: <nil>
STEP: delete the pod
Jun 12 00:31:24.651: INFO: Waiting for pod pod-subpath-test-dynamicpv-qgpn to disappear
Jun 12 00:31:24.680: INFO: Pod pod-subpath-test-dynamicpv-qgpn no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-qgpn
Jun 12 00:31:24.680: INFO: Deleting pod "pod-subpath-test-dynamicpv-qgpn" in namespace "provisioning-5971"
... skipping 114 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 12 00:31:18.556: 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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun 12 00:31:18.709: INFO: Creating resource for dynamic PV
Jun 12 00:31:18.709: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9238-e2e-scfm7pb
STEP: creating a claim
Jun 12 00:31:18.740: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-ft6p
STEP: Checking for subpath error in container status
Jun 12 00:31:34.895: INFO: Deleting pod "pod-subpath-test-dynamicpv-ft6p" in namespace "provisioning-9238"
Jun 12 00:31:34.927: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-ft6p" to be fully deleted
STEP: Deleting pod
Jun 12 00:31:46.988: INFO: Deleting pod "pod-subpath-test-dynamicpv-ft6p" in namespace "provisioning-9238"
STEP: Deleting pvc
Jun 12 00:31:47.079: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.commvp8z"
... skipping 9 lines ...

• [SLOW TEST:33.711 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.mVCl1cIaj/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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 130 lines ...
Jun 12 00:31:16.027: INFO: Creating resource for dynamic PV
Jun 12 00:31:16.027: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6772c7w45
STEP: creating a claim
Jun 12 00:31:16.058: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-6772
Jun 12 00:31:16.154: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-6772" in namespace "provisioning-6772" to be "Succeeded or Failed"
Jun 12 00:31:16.190: INFO: Pod "volume-prep-provisioning-6772": Phase="Pending", Reason="", readiness=false. Elapsed: 35.562611ms
Jun 12 00:31:18.221: INFO: Pod "volume-prep-provisioning-6772": Phase="Pending", Reason="", readiness=false. Elapsed: 2.06612577s
Jun 12 00:31:20.253: INFO: Pod "volume-prep-provisioning-6772": Phase="Pending", Reason="", readiness=false. Elapsed: 4.098205659s
Jun 12 00:31:22.284: INFO: Pod "volume-prep-provisioning-6772": Phase="Pending", Reason="", readiness=false. Elapsed: 6.12952487s
Jun 12 00:31:24.316: INFO: Pod "volume-prep-provisioning-6772": Phase="Pending", Reason="", readiness=false. Elapsed: 8.16178727s
Jun 12 00:31:26.348: INFO: Pod "volume-prep-provisioning-6772": Phase="Pending", Reason="", readiness=false. Elapsed: 10.193825635s
Jun 12 00:31:28.387: INFO: Pod "volume-prep-provisioning-6772": Phase="Pending", Reason="", readiness=false. Elapsed: 12.232421246s
Jun 12 00:31:30.419: INFO: Pod "volume-prep-provisioning-6772": Phase="Pending", Reason="", readiness=false. Elapsed: 14.264162322s
Jun 12 00:31:32.449: INFO: Pod "volume-prep-provisioning-6772": Phase="Pending", Reason="", readiness=false. Elapsed: 16.294898571s
Jun 12 00:31:34.481: INFO: Pod "volume-prep-provisioning-6772": Phase="Pending", Reason="", readiness=false. Elapsed: 18.326398116s
Jun 12 00:31:36.511: INFO: Pod "volume-prep-provisioning-6772": Phase="Pending", Reason="", readiness=false. Elapsed: 20.356683967s
Jun 12 00:31:38.546: INFO: Pod "volume-prep-provisioning-6772": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.391900865s
STEP: Saw pod success
Jun 12 00:31:38.546: INFO: Pod "volume-prep-provisioning-6772" satisfied condition "Succeeded or Failed"
Jun 12 00:31:38.546: INFO: Deleting pod "volume-prep-provisioning-6772" in namespace "provisioning-6772"
Jun 12 00:31:38.583: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-6772" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-w4lk
STEP: Checking for subpath error in container status
Jun 12 00:31:40.706: INFO: Deleting pod "pod-subpath-test-dynamicpv-w4lk" in namespace "provisioning-6772"
Jun 12 00:31:40.744: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-w4lk" to be fully deleted
STEP: Deleting pod
Jun 12 00:31:40.774: INFO: Deleting pod "pod-subpath-test-dynamicpv-w4lk" in namespace "provisioning-6772"
STEP: Deleting pvc
Jun 12 00:31:40.864: INFO: Deleting PersistentVolumeClaim "awsnmfqj"
... skipping 93 lines ...
Jun 12 00:31:37.891: INFO: Pod aws-client still exists
Jun 12 00:31:39.859: INFO: Waiting for pod aws-client to disappear
Jun 12 00:31:39.891: INFO: Pod aws-client still exists
Jun 12 00:31:41.859: INFO: Waiting for pod aws-client to disappear
Jun 12 00:31:41.890: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun 12 00:31:42.156: INFO: Couldn't delete PD "aws://us-east-2a/vol-048b8d06780f701c7", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-048b8d06780f701c7 is currently attached to i-08052264bd3923f8c
	status code: 400, request id: d512fb6f-350b-451c-9fc5-8b1c3ef60b26
Jun 12 00:31:47.418: INFO: Couldn't delete PD "aws://us-east-2a/vol-048b8d06780f701c7", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-048b8d06780f701c7 is currently attached to i-08052264bd3923f8c
	status code: 400, request id: 8b43f672-557e-460e-841d-d3187ef4fbaf
Jun 12 00:31:52.662: INFO: Couldn't delete PD "aws://us-east-2a/vol-048b8d06780f701c7", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-048b8d06780f701c7 is currently attached to i-08052264bd3923f8c
	status code: 400, request id: 2e48bd2a-ae73-45f8-8574-ab16f1080219
Jun 12 00:31:57.908: INFO: Successfully deleted PD "aws://us-east-2a/vol-048b8d06780f701c7".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 00:31:57.908: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-4510" for this suite.
... skipping 108 lines ...
Jun 12 00:30:58.297: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4204hnbqb
STEP: creating a claim
Jun 12 00:30:58.328: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-7m8q
STEP: Creating a pod to test subpath
Jun 12 00:30:58.427: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-7m8q" in namespace "provisioning-4204" to be "Succeeded or Failed"
Jun 12 00:30:58.461: INFO: Pod "pod-subpath-test-dynamicpv-7m8q": Phase="Pending", Reason="", readiness=false. Elapsed: 33.792222ms
Jun 12 00:31:00.492: INFO: Pod "pod-subpath-test-dynamicpv-7m8q": Phase="Pending", Reason="", readiness=false. Elapsed: 2.064775229s
Jun 12 00:31:02.521: INFO: Pod "pod-subpath-test-dynamicpv-7m8q": Phase="Pending", Reason="", readiness=false. Elapsed: 4.094383271s
Jun 12 00:31:04.554: INFO: Pod "pod-subpath-test-dynamicpv-7m8q": Phase="Pending", Reason="", readiness=false. Elapsed: 6.126924677s
Jun 12 00:31:06.585: INFO: Pod "pod-subpath-test-dynamicpv-7m8q": Phase="Pending", Reason="", readiness=false. Elapsed: 8.157745362s
Jun 12 00:31:08.615: INFO: Pod "pod-subpath-test-dynamicpv-7m8q": Phase="Pending", Reason="", readiness=false. Elapsed: 10.188338273s
... skipping 3 lines ...
Jun 12 00:31:16.737: INFO: Pod "pod-subpath-test-dynamicpv-7m8q": Phase="Pending", Reason="", readiness=false. Elapsed: 18.31042138s
Jun 12 00:31:18.768: INFO: Pod "pod-subpath-test-dynamicpv-7m8q": Phase="Pending", Reason="", readiness=false. Elapsed: 20.340539758s
Jun 12 00:31:20.798: INFO: Pod "pod-subpath-test-dynamicpv-7m8q": Phase="Pending", Reason="", readiness=false. Elapsed: 22.371354975s
Jun 12 00:31:22.829: INFO: Pod "pod-subpath-test-dynamicpv-7m8q": Phase="Pending", Reason="", readiness=false. Elapsed: 24.402483313s
Jun 12 00:31:24.861: INFO: Pod "pod-subpath-test-dynamicpv-7m8q": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.434052061s
STEP: Saw pod success
Jun 12 00:31:24.861: INFO: Pod "pod-subpath-test-dynamicpv-7m8q" satisfied condition "Succeeded or Failed"
Jun 12 00:31:24.891: INFO: Trying to get logs from node ip-172-20-54-191.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-7m8q container test-container-volume-dynamicpv-7m8q: <nil>
STEP: delete the pod
Jun 12 00:31:24.963: INFO: Waiting for pod pod-subpath-test-dynamicpv-7m8q to disappear
Jun 12 00:31:24.992: INFO: Pod pod-subpath-test-dynamicpv-7m8q no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-7m8q
Jun 12 00:31:24.992: INFO: Deleting pod "pod-subpath-test-dynamicpv-7m8q" in namespace "provisioning-4204"
... skipping 142 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 12 00:30:58.552: 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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun 12 00:30:58.708: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 12 00:30:58.708: INFO: Creating resource for dynamic PV
Jun 12 00:30:58.708: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-24586xw7s
STEP: creating a claim
Jun 12 00:30:58.739: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-bf6r
STEP: Checking for subpath error in container status
Jun 12 00:31:40.904: INFO: Deleting pod "pod-subpath-test-dynamicpv-bf6r" in namespace "provisioning-2458"
Jun 12 00:31:40.935: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-bf6r" to be fully deleted
STEP: Deleting pod
Jun 12 00:31:50.996: INFO: Deleting pod "pod-subpath-test-dynamicpv-bf6r" in namespace "provisioning-2458"
STEP: Deleting pvc
Jun 12 00:31:51.090: INFO: Deleting PersistentVolumeClaim "awsh84kq"
... skipping 14 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.mVCl1cIaj/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.mVCl1cIaj/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath directory is outside the volume [Slow][LinuxOnly]
      /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 12 00:31:22.320: 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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun 12 00:31:22.476: INFO: Creating resource for dynamic PV
Jun 12 00:31:22.476: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7121-e2e-sc5rzkn
STEP: creating a claim
Jun 12 00:31:22.508: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-6xg4
STEP: Checking for subpath error in container status
Jun 12 00:31:40.674: INFO: Deleting pod "pod-subpath-test-dynamicpv-6xg4" in namespace "provisioning-7121"
Jun 12 00:31:40.707: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-6xg4" to be fully deleted
STEP: Deleting pod
Jun 12 00:31:52.769: INFO: Deleting pod "pod-subpath-test-dynamicpv-6xg4" in namespace "provisioning-7121"
STEP: Deleting pvc
Jun 12 00:31:52.862: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comtqzhm"
... skipping 12 lines ...

• [SLOW TEST:50.826 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.mVCl1cIaj/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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 7 lines ...
Jun 12 00:31:28.520: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4454-e2e-scwnwxg
STEP: creating a claim
Jun 12 00:31:28.550: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-pgkf
STEP: Creating a pod to test subpath
Jun 12 00:31:28.643: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-pgkf" in namespace "provisioning-4454" to be "Succeeded or Failed"
Jun 12 00:31:28.673: INFO: Pod "pod-subpath-test-dynamicpv-pgkf": Phase="Pending", Reason="", readiness=false. Elapsed: 29.802847ms
Jun 12 00:31:30.704: INFO: Pod "pod-subpath-test-dynamicpv-pgkf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061072655s
Jun 12 00:31:32.734: INFO: Pod "pod-subpath-test-dynamicpv-pgkf": Phase="Pending", Reason="", readiness=false. Elapsed: 4.091265548s
Jun 12 00:31:34.765: INFO: Pod "pod-subpath-test-dynamicpv-pgkf": Phase="Pending", Reason="", readiness=false. Elapsed: 6.12252942s
Jun 12 00:31:36.798: INFO: Pod "pod-subpath-test-dynamicpv-pgkf": Phase="Pending", Reason="", readiness=false. Elapsed: 8.154929427s
Jun 12 00:31:38.828: INFO: Pod "pod-subpath-test-dynamicpv-pgkf": Phase="Pending", Reason="", readiness=false. Elapsed: 10.185286704s
... skipping 2 lines ...
Jun 12 00:31:44.919: INFO: Pod "pod-subpath-test-dynamicpv-pgkf": Phase="Pending", Reason="", readiness=false. Elapsed: 16.276231894s
Jun 12 00:31:46.950: INFO: Pod "pod-subpath-test-dynamicpv-pgkf": Phase="Pending", Reason="", readiness=false. Elapsed: 18.307375178s
Jun 12 00:31:48.983: INFO: Pod "pod-subpath-test-dynamicpv-pgkf": Phase="Pending", Reason="", readiness=false. Elapsed: 20.340089534s
Jun 12 00:31:51.013: INFO: Pod "pod-subpath-test-dynamicpv-pgkf": Phase="Pending", Reason="", readiness=false. Elapsed: 22.369954192s
Jun 12 00:31:53.043: INFO: Pod "pod-subpath-test-dynamicpv-pgkf": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.399696242s
STEP: Saw pod success
Jun 12 00:31:53.043: INFO: Pod "pod-subpath-test-dynamicpv-pgkf" satisfied condition "Succeeded or Failed"
Jun 12 00:31:53.072: INFO: Trying to get logs from node ip-172-20-36-179.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-pgkf container test-container-subpath-dynamicpv-pgkf: <nil>
STEP: delete the pod
Jun 12 00:31:53.140: INFO: Waiting for pod pod-subpath-test-dynamicpv-pgkf to disappear
Jun 12 00:31:53.169: INFO: Pod pod-subpath-test-dynamicpv-pgkf no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-pgkf
Jun 12 00:31:53.169: INFO: Deleting pod "pod-subpath-test-dynamicpv-pgkf" in namespace "provisioning-4454"
... skipping 36 lines ...
Jun 12 00:31:14.191: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5097-e2e-scb2t5h
STEP: creating a claim
Jun 12 00:31:14.222: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-26d6
STEP: Creating a pod to test subpath
Jun 12 00:31:14.313: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-26d6" in namespace "provisioning-5097" to be "Succeeded or Failed"
Jun 12 00:31:14.342: INFO: Pod "pod-subpath-test-dynamicpv-26d6": Phase="Pending", Reason="", readiness=false. Elapsed: 29.288689ms
Jun 12 00:31:16.413: INFO: Pod "pod-subpath-test-dynamicpv-26d6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.100267984s
Jun 12 00:31:18.445: INFO: Pod "pod-subpath-test-dynamicpv-26d6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.131516697s
Jun 12 00:31:20.475: INFO: Pod "pod-subpath-test-dynamicpv-26d6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.161707979s
Jun 12 00:31:22.507: INFO: Pod "pod-subpath-test-dynamicpv-26d6": Phase="Pending", Reason="", readiness=false. Elapsed: 8.193813558s
Jun 12 00:31:24.539: INFO: Pod "pod-subpath-test-dynamicpv-26d6": Phase="Pending", Reason="", readiness=false. Elapsed: 10.225443281s
... skipping 2 lines ...
Jun 12 00:31:30.630: INFO: Pod "pod-subpath-test-dynamicpv-26d6": Phase="Pending", Reason="", readiness=false. Elapsed: 16.316478317s
Jun 12 00:31:32.666: INFO: Pod "pod-subpath-test-dynamicpv-26d6": Phase="Pending", Reason="", readiness=false. Elapsed: 18.353192472s
Jun 12 00:31:34.697: INFO: Pod "pod-subpath-test-dynamicpv-26d6": Phase="Pending", Reason="", readiness=false. Elapsed: 20.384106485s
Jun 12 00:31:36.736: INFO: Pod "pod-subpath-test-dynamicpv-26d6": Phase="Pending", Reason="", readiness=false. Elapsed: 22.423047131s
Jun 12 00:31:38.766: INFO: Pod "pod-subpath-test-dynamicpv-26d6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.453078003s
STEP: Saw pod success
Jun 12 00:31:38.766: INFO: Pod "pod-subpath-test-dynamicpv-26d6" satisfied condition "Succeeded or Failed"
Jun 12 00:31:38.796: INFO: Trying to get logs from node ip-172-20-54-191.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-26d6 container test-container-subpath-dynamicpv-26d6: <nil>
STEP: delete the pod
Jun 12 00:31:38.868: INFO: Waiting for pod pod-subpath-test-dynamicpv-26d6 to disappear
Jun 12 00:31:38.898: INFO: Pod pod-subpath-test-dynamicpv-26d6 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-26d6
Jun 12 00:31:38.898: INFO: Deleting pod "pod-subpath-test-dynamicpv-26d6" in namespace "provisioning-5097"
... skipping 550 lines ...
Jun 12 00:30:30.669: INFO: Creating resource for dynamic PV
Jun 12 00:30:30.669: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-3034-e2e-scqtl6w
STEP: creating a claim
Jun 12 00:30:30.700: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 12 00:30:30.796: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-7npf9" in namespace "snapshotting-3034" to be "Succeeded or Failed"
Jun 12 00:30:30.826: INFO: Pod "pvc-snapshottable-tester-7npf9": Phase="Pending", Reason="", readiness=false. Elapsed: 29.754847ms
Jun 12 00:30:32.857: INFO: Pod "pvc-snapshottable-tester-7npf9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061054346s
Jun 12 00:30:34.887: INFO: Pod "pvc-snapshottable-tester-7npf9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.091054389s
Jun 12 00:30:36.917: INFO: Pod "pvc-snapshottable-tester-7npf9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.120941106s
Jun 12 00:30:38.947: INFO: Pod "pvc-snapshottable-tester-7npf9": Phase="Pending", Reason="", readiness=false. Elapsed: 8.151036641s
Jun 12 00:30:40.978: INFO: Pod "pvc-snapshottable-tester-7npf9": Phase="Pending", Reason="", readiness=false. Elapsed: 10.182445898s
Jun 12 00:30:43.008: INFO: Pod "pvc-snapshottable-tester-7npf9": Phase="Pending", Reason="", readiness=false. Elapsed: 12.212680607s
Jun 12 00:30:45.039: INFO: Pod "pvc-snapshottable-tester-7npf9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.243101784s
STEP: Saw pod success
Jun 12 00:30:45.039: INFO: Pod "pvc-snapshottable-tester-7npf9" satisfied condition "Succeeded or Failed"
Jun 12 00:30:45.100: INFO: Pod pvc-snapshottable-tester-7npf9 has the following logs: 
Jun 12 00:30:45.100: INFO: Deleting pod "pvc-snapshottable-tester-7npf9" in namespace "snapshotting-3034"
Jun 12 00:30:45.135: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-7npf9" to be fully deleted
Jun 12 00:30:45.165: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.com5lxdd] to have phase Bound
Jun 12 00:30:45.194: INFO: PersistentVolumeClaim ebs.csi.aws.com5lxdd found and phase=Bound (29.579389ms)
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.mVCl1cIaj/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 12 00:31:30.231: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-mbpwq" in namespace "snapshotting-3034" to be "Succeeded or Failed"
Jun 12 00:31:30.261: INFO: Pod "pvc-snapshottable-data-tester-mbpwq": Phase="Pending", Reason="", readiness=false. Elapsed: 29.687558ms
Jun 12 00:31:32.292: INFO: Pod "pvc-snapshottable-data-tester-mbpwq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.060659213s
Jun 12 00:31:34.322: INFO: Pod "pvc-snapshottable-data-tester-mbpwq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.091091189s
Jun 12 00:31:36.354: INFO: Pod "pvc-snapshottable-data-tester-mbpwq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.122551715s
Jun 12 00:31:38.384: INFO: Pod "pvc-snapshottable-data-tester-mbpwq": Phase="Pending", Reason="", readiness=false. Elapsed: 8.153082773s
Jun 12 00:31:40.415: INFO: Pod "pvc-snapshottable-data-tester-mbpwq": Phase="Pending", Reason="", readiness=false. Elapsed: 10.184121943s
... skipping 7 lines ...
Jun 12 00:31:56.687: INFO: Pod "pvc-snapshottable-data-tester-mbpwq": Phase="Pending", Reason="", readiness=false. Elapsed: 26.455959001s
Jun 12 00:31:58.718: INFO: Pod "pvc-snapshottable-data-tester-mbpwq": Phase="Pending", Reason="", readiness=false. Elapsed: 28.486578559s
Jun 12 00:32:00.749: INFO: Pod "pvc-snapshottable-data-tester-mbpwq": Phase="Pending", Reason="", readiness=false. Elapsed: 30.517568338s
Jun 12 00:32:02.779: INFO: Pod "pvc-snapshottable-data-tester-mbpwq": Phase="Pending", Reason="", readiness=false. Elapsed: 32.548271208s
Jun 12 00:32:04.810: INFO: Pod "pvc-snapshottable-data-tester-mbpwq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.578754205s
STEP: Saw pod success
Jun 12 00:32:04.810: INFO: Pod "pvc-snapshottable-data-tester-mbpwq" satisfied condition "Succeeded or Failed"
Jun 12 00:32:04.871: INFO: Pod pvc-snapshottable-data-tester-mbpwq has the following logs: 
Jun 12 00:32:04.871: INFO: Deleting pod "pvc-snapshottable-data-tester-mbpwq" in namespace "snapshotting-3034"
Jun 12 00:32:04.908: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-mbpwq" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 12 00:32:27.064: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-3034 exec restored-pvc-tester-7rbnx --namespace=snapshotting-3034 -- cat /mnt/test/data'
... skipping 33 lines ...
Jun 12 00:32:52.405: INFO: volumesnapshotcontents snapcontent-e529df39-733d-4a4e-8ab5-5ebaa1e176c3 has been found and is not deleted
Jun 12 00:32:53.437: INFO: volumesnapshotcontents snapcontent-e529df39-733d-4a4e-8ab5-5ebaa1e176c3 has been found and is not deleted
Jun 12 00:32:54.467: INFO: volumesnapshotcontents snapcontent-e529df39-733d-4a4e-8ab5-5ebaa1e176c3 has been found and is not deleted
Jun 12 00:32:55.498: INFO: volumesnapshotcontents snapcontent-e529df39-733d-4a4e-8ab5-5ebaa1e176c3 has been found and is not deleted
Jun 12 00:32:56.530: INFO: volumesnapshotcontents snapcontent-e529df39-733d-4a4e-8ab5-5ebaa1e176c3 has been found and is not deleted
Jun 12 00:32:57.560: INFO: volumesnapshotcontents snapcontent-e529df39-733d-4a4e-8ab5-5ebaa1e176c3 has been found and is not deleted
Jun 12 00:32:58.561: INFO: WaitUntil failed after reaching the timeout 30s
[AfterEach] volume snapshot controller
  /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:221
Jun 12 00:32:58.593: INFO: Pod restored-pvc-tester-7rbnx has the following logs: 
Jun 12 00:32:58.593: INFO: Deleting pod "restored-pvc-tester-7rbnx" in namespace "snapshotting-3034"
Jun 12 00:32:58.624: INFO: Wait up to 5m0s for pod "restored-pvc-tester-7rbnx" to be fully deleted
Jun 12 00:33:38.684: INFO: deleting claim "snapshotting-3034"/"pvc-mv2ss"
... skipping 32 lines ...
        /tmp/kops.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:243
------------------------------


Summarizing 2 Failures:

[Fail] External Storage [Driver: ebs.csi.aws.com] [Testpattern: Pre-provisioned 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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:602

[Fail] External Storage [Driver: ebs.csi.aws.com] [Testpattern: Dynamic 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.mVCl1cIaj/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:602

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


Ginkgo ran 1 suite in 11m10.027515876s
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
I0612 00:33:46.257255   26815 app.go:59] RunDir for this run: "/logs/artifacts/f3fa1ea7-cb11-11eb-ab6f-62c732df09e9"
I0612 00:33:46.257417   26815 app.go:90] ID for this run: "f3fa1ea7-cb11-11eb-ab6f-62c732df09e9"
I0612 00:33:46.257475   26815 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
I0612 00:33:46.272538   26821 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
... skipping 1505 lines ...