This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-06-01 15:59
Elapsed32m36s
Revisionmaster

No Test Failures!


Error lines from build-log.txt

... skipping 492 lines ...
I0601 16:06:41.563585   14198 up.go:43] Cleaning up any leaked resources from previous cluster
I0601 16:06:41.563625   14198 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
I0601 16:06:41.582156   14204 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0601 16:06:41.582262   14204 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io" not found
W0601 16:06:42.115019   14198 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0601 16:06:42.115066   14198 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
I0601 16:06:42.134279   14215 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0601 16:06:42.134398   14215 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io" not found
I0601 16:06:42.682736   14198 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/06/01 16:06:42 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
I0601 16:06:42.692687   14198 http.go:37] curl https://ip.jsb.workers.dev
I0601 16:06:42.833624   14198 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.202.82.155/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones eu-west-1a --master-size c5.large
I0601 16:06:42.849693   14230 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0601 16:06:42.849801   14230 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I0601 16:06:42.911104   14230 create_cluster.go:728] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0601 16:06:43.409408   14230 new_cluster.go:1022]  Cloud Provider ID = aws
... skipping 40 lines ...

I0601 16:07:10.858811   14198 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
I0601 16:07:10.875305   14250 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0601 16:07:10.875485   14250 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io

W0601 16:07:12.364302   14250 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-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W0601 16:07:22.413442   14250 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W0601 16:07:32.446650   14250 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W0601 16:07:42.495103   14250 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W0601 16:07:52.534583   14250 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W0601 16:08:02.589047   14250 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W0601 16:08:12.620113   14250 validate_cluster.go:221] (will retry): cluster not yet healthy
W0601 16:08:22.650401   14250 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-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W0601 16:08:32.698691   14250 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W0601 16:08:42.729323   14250 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W0601 16:08:52.788869   14250 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W0601 16:09:02.825421   14250 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W0601 16:09:12.857298   14250 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W0601 16:09:22.901844   14250 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W0601 16:09:32.946766   14250 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W0601 16:09:42.979880   14250 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W0601 16:09:53.067021   14250 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W0601 16:10:03.102373   14250 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W0601 16:10:13.136795   14250 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W0601 16:10:23.230740   14250 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W0601 16:10:33.266073   14250 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W0601 16:10:43.316104   14250 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W0601 16:10:53.351574   14250 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W0601 16:11:03.389907   14250 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W0601 16:11:13.424223   14250 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W0601 16:11:23.470878   14250 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W0601 16:11:33.507257   14250 validate_cluster.go:221] (will retry): cluster not yet healthy
W0601 16:11:43.527678   14250 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-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W0601 16:11:53.562738   14250 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W0601 16:12:03.623935   14250 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W0601 16:12:13.673347   14250 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 13 lines ...
Pod	kube-system/cert-manager-webhook-7bbf67968-28t9x			system-cluster-critical pod "cert-manager-webhook-7bbf67968-28t9x" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-g6lt5				system-cluster-critical pod "coredns-autoscaler-6f594f4c58-g6lt5" is pending
Pod	kube-system/coredns-f45c4bf76-jjksz					system-cluster-critical pod "coredns-f45c4bf76-jjksz" is pending
Pod	kube-system/ebs-csi-node-kng7x						system-node-critical pod "ebs-csi-node-kng7x" is pending
Pod	kube-system/kube-proxy-ip-172-20-57-211.eu-west-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-57-211.eu-west-1.compute.internal" is pending

Validation Failed
W0601 16:12:26.492566   14250 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 22 lines ...
Pod	kube-system/ebs-csi-node-cttwf						system-node-critical pod "ebs-csi-node-cttwf" is pending
Pod	kube-system/ebs-csi-node-dnm5d						system-node-critical pod "ebs-csi-node-dnm5d" is pending
Pod	kube-system/ebs-csi-node-kng7x						system-node-critical pod "ebs-csi-node-kng7x" is pending
Pod	kube-system/ebs-csi-node-zvqcb						system-node-critical pod "ebs-csi-node-zvqcb" is pending
Pod	kube-system/kube-proxy-ip-172-20-46-125.eu-west-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-46-125.eu-west-1.compute.internal" is pending

Validation Failed
W0601 16:12:38.438148   14250 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 16 lines ...
Pod	kube-system/coredns-autoscaler-6f594f4c58-g6lt5				system-cluster-critical pod "coredns-autoscaler-6f594f4c58-g6lt5" is pending
Pod	kube-system/coredns-f45c4bf76-jjksz					system-cluster-critical pod "coredns-f45c4bf76-jjksz" is pending
Pod	kube-system/ebs-csi-node-cttwf						system-node-critical pod "ebs-csi-node-cttwf" is pending
Pod	kube-system/ebs-csi-node-zvqcb						system-node-critical pod "ebs-csi-node-zvqcb" is pending
Pod	kube-system/kube-proxy-ip-172-20-46-125.eu-west-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-46-125.eu-west-1.compute.internal" is pending

Validation Failed
W0601 16:12:50.390929   14250 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-node-x8vfj				system-node-critical pod "calico-node-x8vfj" is not ready (calico-node)
Pod	kube-system/cert-manager-webhook-7bbf67968-28t9x	system-cluster-critical pod "cert-manager-webhook-7bbf67968-28t9x" is not ready (cert-manager)
Pod	kube-system/coredns-autoscaler-6f594f4c58-g6lt5		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-g6lt5" is pending

Validation Failed
W0601 16:13:02.354288   14250 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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

      Distro debian doesn't support ntfs -- skipping

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.qpMXPyqcf/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.qpMXPyqcf/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.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 128 lines ...

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 214 lines ...
STEP: Creating a kubernetes client
Jun  1 16:17:52.938: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename topology
W0601 16:17:53.628928   28093 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Jun  1 16:17:53.629: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail to schedule a pod which has topologies that conflict with AllowedTopologies
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Jun  1 16:17:54.046: INFO: found topology map[topology.kubernetes.io/zone:eu-west-1a]
Jun  1 16:17:54.047: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  1 16:17:54.047: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.qpMXPyqcf/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.qpMXPyqcf/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (immediate binding)] topology
    /tmp/kops.qpMXPyqcf/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.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 309 lines ...
Jun  1 16:17:53.724: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-3018-e2e-schpq6c
STEP: creating a claim
Jun  1 16:17:53.833: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Jun  1 16:17:54.050: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun  1 16:17:54.285: INFO: Error updating pvc ebs.csi.aws.com9rp2w: PersistentVolumeClaim "ebs.csi.aws.com9rp2w" 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-3018-e2e-schpq6c",
  	... // 2 identical fields
  }

Jun  1 16:17:56.501: INFO: Error updating pvc ebs.csi.aws.com9rp2w: PersistentVolumeClaim "ebs.csi.aws.com9rp2w" 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-3018-e2e-schpq6c",
  	... // 2 identical fields
  }

Jun  1 16:17:58.499: INFO: Error updating pvc ebs.csi.aws.com9rp2w: PersistentVolumeClaim "ebs.csi.aws.com9rp2w" 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-3018-e2e-schpq6c",
  	... // 2 identical fields
  }

Jun  1 16:18:00.500: INFO: Error updating pvc ebs.csi.aws.com9rp2w: PersistentVolumeClaim "ebs.csi.aws.com9rp2w" 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-3018-e2e-schpq6c",
  	... // 2 identical fields
  }

Jun  1 16:18:02.501: INFO: Error updating pvc ebs.csi.aws.com9rp2w: PersistentVolumeClaim "ebs.csi.aws.com9rp2w" 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-3018-e2e-schpq6c",
  	... // 2 identical fields
  }

Jun  1 16:18:04.503: INFO: Error updating pvc ebs.csi.aws.com9rp2w: PersistentVolumeClaim "ebs.csi.aws.com9rp2w" 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-3018-e2e-schpq6c",
  	... // 2 identical fields
  }

Jun  1 16:18:06.500: INFO: Error updating pvc ebs.csi.aws.com9rp2w: PersistentVolumeClaim "ebs.csi.aws.com9rp2w" 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-3018-e2e-schpq6c",
  	... // 2 identical fields
  }

Jun  1 16:18:08.500: INFO: Error updating pvc ebs.csi.aws.com9rp2w: PersistentVolumeClaim "ebs.csi.aws.com9rp2w" 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-3018-e2e-schpq6c",
  	... // 2 identical fields
  }

Jun  1 16:18:10.501: INFO: Error updating pvc ebs.csi.aws.com9rp2w: PersistentVolumeClaim "ebs.csi.aws.com9rp2w" 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-3018-e2e-schpq6c",
  	... // 2 identical fields
  }

Jun  1 16:18:12.499: INFO: Error updating pvc ebs.csi.aws.com9rp2w: PersistentVolumeClaim "ebs.csi.aws.com9rp2w" 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-3018-e2e-schpq6c",
  	... // 2 identical fields
  }

Jun  1 16:18:14.501: INFO: Error updating pvc ebs.csi.aws.com9rp2w: PersistentVolumeClaim "ebs.csi.aws.com9rp2w" 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-3018-e2e-schpq6c",
  	... // 2 identical fields
  }

Jun  1 16:18:16.502: INFO: Error updating pvc ebs.csi.aws.com9rp2w: PersistentVolumeClaim "ebs.csi.aws.com9rp2w" 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-3018-e2e-schpq6c",
  	... // 2 identical fields
  }

Jun  1 16:18:18.500: INFO: Error updating pvc ebs.csi.aws.com9rp2w: PersistentVolumeClaim "ebs.csi.aws.com9rp2w" 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-3018-e2e-schpq6c",
  	... // 2 identical fields
  }

Jun  1 16:18:20.499: INFO: Error updating pvc ebs.csi.aws.com9rp2w: PersistentVolumeClaim "ebs.csi.aws.com9rp2w" 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-3018-e2e-schpq6c",
  	... // 2 identical fields
  }

Jun  1 16:18:22.500: INFO: Error updating pvc ebs.csi.aws.com9rp2w: PersistentVolumeClaim "ebs.csi.aws.com9rp2w" 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-3018-e2e-schpq6c",
  	... // 2 identical fields
  }

Jun  1 16:18:24.500: INFO: Error updating pvc ebs.csi.aws.com9rp2w: PersistentVolumeClaim "ebs.csi.aws.com9rp2w" 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-3018-e2e-schpq6c",
  	... // 2 identical fields
  }

Jun  1 16:18:24.714: INFO: Error updating pvc ebs.csi.aws.com9rp2w: PersistentVolumeClaim "ebs.csi.aws.com9rp2w" 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 53 lines ...

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

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

    /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 4 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  1 16:17:55.537: 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.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  1 16:17:57.158: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  1 16:17:57.158: INFO: Creating resource for dynamic PV
Jun  1 16:17:57.158: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-186626mn7
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  1 16:18:07.909: INFO: Deleting pod "pod-6fef2f1c-28d9-4308-9078-80edaeaf41ed" in namespace "volumemode-1866"
Jun  1 16:18:08.017: INFO: Wait up to 5m0s for pod "pod-6fef2f1c-28d9-4308-9078-80edaeaf41ed" to be fully deleted
STEP: Deleting pvc
Jun  1 16:18:18.443: INFO: Deleting PersistentVolumeClaim "aws4mc5s"
Jun  1 16:18:18.550: INFO: Waiting up to 5m0s for PersistentVolume pvc-57af74a8-1f6c-49d2-88fa-d95be2bf7c82 to get deleted
Jun  1 16:18:18.657: INFO: PersistentVolume pvc-57af74a8-1f6c-49d2-88fa-d95be2bf7c82 found and phase=Released (106.476691ms)
... skipping 10 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.qpMXPyqcf/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.qpMXPyqcf/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (block volmode)] volumeMode
    /tmp/kops.qpMXPyqcf/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.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 126 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.qpMXPyqcf/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.qpMXPyqcf/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.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 25 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  1 16:17:55.397: 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.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun  1 16:17:57.109: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  1 16:17:57.109: INFO: Creating resource for dynamic PV
Jun  1 16:17:57.109: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-59359j2vw
STEP: creating a claim
Jun  1 16:17:57.218: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-kbdd
STEP: Checking for subpath error in container status
Jun  1 16:18:15.765: INFO: Deleting pod "pod-subpath-test-dynamicpv-kbdd" in namespace "provisioning-5935"
Jun  1 16:18:15.874: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-kbdd" to be fully deleted
STEP: Deleting pod
Jun  1 16:18:26.089: INFO: Deleting pod "pod-subpath-test-dynamicpv-kbdd" in namespace "provisioning-5935"
STEP: Deleting pvc
Jun  1 16:18:26.411: INFO: Deleting PersistentVolumeClaim "awszhjnp"
... skipping 11 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.qpMXPyqcf/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.qpMXPyqcf/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath directory is outside the volume [Slow][LinuxOnly]
      /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (ext3)] volumes
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  1 16:18:32.068: INFO: Driver "ebs.csi.aws.com" does not support volume type "PreprovisionedPV" - skipping
[AfterEach] [Testpattern: Pre-provisioned PV (ext3)] volumes
... skipping 319 lines ...
Jun  1 16:17:55.818: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1248-e2e-sc6gx8t
STEP: creating a claim
Jun  1 16:17:55.926: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-lhn8
STEP: Creating a pod to test multi_subpath
Jun  1 16:17:56.250: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-lhn8" in namespace "provisioning-1248" to be "Succeeded or Failed"
Jun  1 16:17:56.362: INFO: Pod "pod-subpath-test-dynamicpv-lhn8": Phase="Pending", Reason="", readiness=false. Elapsed: 111.628106ms
Jun  1 16:17:58.468: INFO: Pod "pod-subpath-test-dynamicpv-lhn8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.217776662s
Jun  1 16:18:00.576: INFO: Pod "pod-subpath-test-dynamicpv-lhn8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.325203497s
Jun  1 16:18:02.683: INFO: Pod "pod-subpath-test-dynamicpv-lhn8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.432172588s
Jun  1 16:18:04.790: INFO: Pod "pod-subpath-test-dynamicpv-lhn8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.539417325s
Jun  1 16:18:06.896: INFO: Pod "pod-subpath-test-dynamicpv-lhn8": Phase="Pending", Reason="", readiness=false. Elapsed: 10.645518215s
... skipping 2 lines ...
Jun  1 16:18:13.216: INFO: Pod "pod-subpath-test-dynamicpv-lhn8": Phase="Pending", Reason="", readiness=false. Elapsed: 16.965009281s
Jun  1 16:18:15.325: INFO: Pod "pod-subpath-test-dynamicpv-lhn8": Phase="Pending", Reason="", readiness=false. Elapsed: 19.074031105s
Jun  1 16:18:17.433: INFO: Pod "pod-subpath-test-dynamicpv-lhn8": Phase="Pending", Reason="", readiness=false. Elapsed: 21.182959343s
Jun  1 16:18:19.541: INFO: Pod "pod-subpath-test-dynamicpv-lhn8": Phase="Pending", Reason="", readiness=false. Elapsed: 23.290123686s
Jun  1 16:18:21.646: INFO: Pod "pod-subpath-test-dynamicpv-lhn8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 25.395963489s
STEP: Saw pod success
Jun  1 16:18:21.647: INFO: Pod "pod-subpath-test-dynamicpv-lhn8" satisfied condition "Succeeded or Failed"
Jun  1 16:18:21.752: INFO: Trying to get logs from node ip-172-20-57-30.eu-west-1.compute.internal pod pod-subpath-test-dynamicpv-lhn8 container test-container-subpath-dynamicpv-lhn8: <nil>
STEP: delete the pod
Jun  1 16:18:22.737: INFO: Waiting for pod pod-subpath-test-dynamicpv-lhn8 to disappear
Jun  1 16:18:22.842: INFO: Pod pod-subpath-test-dynamicpv-lhn8 no longer exists
STEP: Deleting pod
Jun  1 16:18:22.843: INFO: Deleting pod "pod-subpath-test-dynamicpv-lhn8" in namespace "provisioning-1248"
... skipping 74 lines ...
Jun  1 16:17:57.059: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1946pv7s2
STEP: creating a claim
Jun  1 16:17:57.166: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-kbxh
STEP: Creating a pod to test subpath
Jun  1 16:17:57.490: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-kbxh" in namespace "provisioning-1946" to be "Succeeded or Failed"
Jun  1 16:17:57.600: INFO: Pod "pod-subpath-test-dynamicpv-kbxh": Phase="Pending", Reason="", readiness=false. Elapsed: 109.977262ms
Jun  1 16:17:59.712: INFO: Pod "pod-subpath-test-dynamicpv-kbxh": Phase="Pending", Reason="", readiness=false. Elapsed: 2.222488227s
Jun  1 16:18:01.822: INFO: Pod "pod-subpath-test-dynamicpv-kbxh": Phase="Pending", Reason="", readiness=false. Elapsed: 4.332545084s
Jun  1 16:18:03.931: INFO: Pod "pod-subpath-test-dynamicpv-kbxh": Phase="Pending", Reason="", readiness=false. Elapsed: 6.44188604s
Jun  1 16:18:06.059: INFO: Pod "pod-subpath-test-dynamicpv-kbxh": Phase="Pending", Reason="", readiness=false. Elapsed: 8.569229037s
Jun  1 16:18:08.166: INFO: Pod "pod-subpath-test-dynamicpv-kbxh": Phase="Pending", Reason="", readiness=false. Elapsed: 10.676592914s
... skipping 2 lines ...
Jun  1 16:18:14.491: INFO: Pod "pod-subpath-test-dynamicpv-kbxh": Phase="Pending", Reason="", readiness=false. Elapsed: 17.001859787s
Jun  1 16:18:16.600: INFO: Pod "pod-subpath-test-dynamicpv-kbxh": Phase="Pending", Reason="", readiness=false. Elapsed: 19.110321589s
Jun  1 16:18:18.708: INFO: Pod "pod-subpath-test-dynamicpv-kbxh": Phase="Pending", Reason="", readiness=false. Elapsed: 21.218476748s
Jun  1 16:18:20.816: INFO: Pod "pod-subpath-test-dynamicpv-kbxh": Phase="Pending", Reason="", readiness=false. Elapsed: 23.326539027s
Jun  1 16:18:22.924: INFO: Pod "pod-subpath-test-dynamicpv-kbxh": Phase="Succeeded", Reason="", readiness=false. Elapsed: 25.434836134s
STEP: Saw pod success
Jun  1 16:18:22.925: INFO: Pod "pod-subpath-test-dynamicpv-kbxh" satisfied condition "Succeeded or Failed"
Jun  1 16:18:23.031: INFO: Trying to get logs from node ip-172-20-57-30.eu-west-1.compute.internal pod pod-subpath-test-dynamicpv-kbxh container test-container-subpath-dynamicpv-kbxh: <nil>
STEP: delete the pod
Jun  1 16:18:23.256: INFO: Waiting for pod pod-subpath-test-dynamicpv-kbxh to disappear
Jun  1 16:18:23.363: INFO: Pod pod-subpath-test-dynamicpv-kbxh no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-kbxh
Jun  1 16:18:23.363: INFO: Deleting pod "pod-subpath-test-dynamicpv-kbxh" in namespace "provisioning-1946"
... skipping 322 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  1 16:18:37.913: 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.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  1 16:18:38.444: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  1 16:18:39.274: INFO: Successfully created a new PD: "aws://eu-west-1a/vol-055cce82067f48589".
Jun  1 16:18:39.274: INFO: Creating resource for pre-provisioned PV
Jun  1 16:18:39.274: INFO: Creating PVC and PV
... skipping 5 lines ...
Jun  1 16:18:43.872: INFO: PersistentVolumeClaim pvc-q5667 found but phase is Pending instead of Bound.
Jun  1 16:18:45.977: INFO: PersistentVolumeClaim pvc-q5667 found but phase is Pending instead of Bound.
Jun  1 16:18:48.084: INFO: PersistentVolumeClaim pvc-q5667 found and phase=Bound (8.529514207s)
Jun  1 16:18:48.084: INFO: Waiting up to 3m0s for PersistentVolume aws-4g7lf to have phase Bound
Jun  1 16:18:48.189: INFO: PersistentVolume aws-4g7lf found and phase=Bound (105.029904ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  1 16:18:48.715: INFO: Deleting pod "pod-04656b2e-bdc2-417d-88b1-4e6f6cafbecf" in namespace "volumemode-8252"
Jun  1 16:18:48.821: INFO: Wait up to 5m0s for pod "pod-04656b2e-bdc2-417d-88b1-4e6f6cafbecf" to be fully deleted
STEP: Deleting pv and pvc
Jun  1 16:18:59.035: INFO: Deleting PersistentVolumeClaim "pvc-q5667"
Jun  1 16:18:59.142: INFO: Deleting PersistentVolume "aws-4g7lf"
Jun  1 16:18:59.448: INFO: Couldn't delete PD "aws://eu-west-1a/vol-055cce82067f48589", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-055cce82067f48589 is currently attached to i-01c79fe7421f52304
	status code: 400, request id: 570b54d8-c062-4a68-95e2-3ad7c86322d7
Jun  1 16:19:05.161: INFO: Couldn't delete PD "aws://eu-west-1a/vol-055cce82067f48589", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-055cce82067f48589 is currently attached to i-01c79fe7421f52304
	status code: 400, request id: 3c12fd62-1c0c-43af-92e9-dfcc976ade30
Jun  1 16:19:10.768: INFO: Successfully deleted PD "aws://eu-west-1a/vol-055cce82067f48589".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  1 16:19:10.768: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-8252" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.qpMXPyqcf/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.qpMXPyqcf/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
    /tmp/kops.qpMXPyqcf/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.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] volume-expand
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  1 16:19:10.981: INFO: Distro debian doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] volume-expand
... skipping 241 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.qpMXPyqcf/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.qpMXPyqcf/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.qpMXPyqcf/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.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 231 lines ...
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  1 16:19:13.189: 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.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Jun  1 16:19:13.830: INFO: found topology map[topology.kubernetes.io/zone:eu-west-1a]
Jun  1 16:19:13.830: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  1 16:19:13.830: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.qpMXPyqcf/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.qpMXPyqcf/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (delayed binding)] topology
    /tmp/kops.qpMXPyqcf/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.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 54 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.qpMXPyqcf/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.qpMXPyqcf/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.qpMXPyqcf/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.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 214 lines ...

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

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

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

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 73 lines ...
Jun  1 16:19:15.803: INFO: Pod aws-client still exists
Jun  1 16:19:17.695: INFO: Waiting for pod aws-client to disappear
Jun  1 16:19:17.803: INFO: Pod aws-client still exists
Jun  1 16:19:19.695: INFO: Waiting for pod aws-client to disappear
Jun  1 16:19:19.803: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun  1 16:19:20.571: INFO: Couldn't delete PD "aws://eu-west-1a/vol-010123c3a12aaf7c5", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-010123c3a12aaf7c5 is currently attached to i-0e6e8cb92e7778059
	status code: 400, request id: 69a4aacf-8b4b-45d5-b0d2-82339a35c217
Jun  1 16:19:26.180: INFO: Couldn't delete PD "aws://eu-west-1a/vol-010123c3a12aaf7c5", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-010123c3a12aaf7c5 is currently attached to i-0e6e8cb92e7778059
	status code: 400, request id: 81b32c83-907e-4062-8dcb-28d4515c41de
Jun  1 16:19:31.812: INFO: Couldn't delete PD "aws://eu-west-1a/vol-010123c3a12aaf7c5", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-010123c3a12aaf7c5 is currently attached to i-0e6e8cb92e7778059
	status code: 400, request id: e5bd4767-590a-4558-ac6c-1bb5eaa086ba
Jun  1 16:19:37.532: INFO: Couldn't delete PD "aws://eu-west-1a/vol-010123c3a12aaf7c5", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-010123c3a12aaf7c5 is currently attached to i-0e6e8cb92e7778059
	status code: 400, request id: 81d81804-4634-4469-84d4-c8e9714533f6
Jun  1 16:19:43.170: INFO: Successfully deleted PD "aws://eu-west-1a/vol-010123c3a12aaf7c5".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  1 16:19:43.170: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-1768" for this suite.
... skipping 389 lines ...

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

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

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

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 24 lines ...
Jun  1 16:18:47.308: INFO: PersistentVolumeClaim pvc-xbrb5 found but phase is Pending instead of Bound.
Jun  1 16:18:49.414: INFO: PersistentVolumeClaim pvc-xbrb5 found and phase=Bound (14.849459009s)
Jun  1 16:18:49.414: INFO: Waiting up to 3m0s for PersistentVolume aws-629lf to have phase Bound
Jun  1 16:18:49.520: INFO: PersistentVolume aws-629lf found and phase=Bound (105.343344ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-rxph
STEP: Creating a pod to test exec-volume-test
Jun  1 16:18:49.838: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-rxph" in namespace "volume-4629" to be "Succeeded or Failed"
Jun  1 16:18:49.944: INFO: Pod "exec-volume-test-preprovisionedpv-rxph": Phase="Pending", Reason="", readiness=false. Elapsed: 105.603127ms
Jun  1 16:18:52.051: INFO: Pod "exec-volume-test-preprovisionedpv-rxph": Phase="Pending", Reason="", readiness=false. Elapsed: 2.212490903s
Jun  1 16:18:54.158: INFO: Pod "exec-volume-test-preprovisionedpv-rxph": Phase="Pending", Reason="", readiness=false. Elapsed: 4.319621965s
Jun  1 16:18:56.264: INFO: Pod "exec-volume-test-preprovisionedpv-rxph": Phase="Pending", Reason="", readiness=false. Elapsed: 6.425889896s
Jun  1 16:18:58.371: INFO: Pod "exec-volume-test-preprovisionedpv-rxph": Phase="Pending", Reason="", readiness=false. Elapsed: 8.532312622s
Jun  1 16:19:00.478: INFO: Pod "exec-volume-test-preprovisionedpv-rxph": Phase="Pending", Reason="", readiness=false. Elapsed: 10.639203705s
Jun  1 16:19:02.585: INFO: Pod "exec-volume-test-preprovisionedpv-rxph": Phase="Pending", Reason="", readiness=false. Elapsed: 12.746113512s
Jun  1 16:19:04.691: INFO: Pod "exec-volume-test-preprovisionedpv-rxph": Phase="Pending", Reason="", readiness=false. Elapsed: 14.852375152s
Jun  1 16:19:06.796: INFO: Pod "exec-volume-test-preprovisionedpv-rxph": Phase="Pending", Reason="", readiness=false. Elapsed: 16.95793797s
Jun  1 16:19:08.903: INFO: Pod "exec-volume-test-preprovisionedpv-rxph": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.064055613s
STEP: Saw pod success
Jun  1 16:19:08.903: INFO: Pod "exec-volume-test-preprovisionedpv-rxph" satisfied condition "Succeeded or Failed"
Jun  1 16:19:09.008: INFO: Trying to get logs from node ip-172-20-57-30.eu-west-1.compute.internal pod exec-volume-test-preprovisionedpv-rxph container exec-container-preprovisionedpv-rxph: <nil>
STEP: delete the pod
Jun  1 16:19:09.260: INFO: Waiting for pod exec-volume-test-preprovisionedpv-rxph to disappear
Jun  1 16:19:09.366: INFO: Pod exec-volume-test-preprovisionedpv-rxph no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-rxph
Jun  1 16:19:09.366: INFO: Deleting pod "exec-volume-test-preprovisionedpv-rxph" in namespace "volume-4629"
STEP: Deleting pv and pvc
Jun  1 16:19:09.471: INFO: Deleting PersistentVolumeClaim "pvc-xbrb5"
Jun  1 16:19:09.581: INFO: Deleting PersistentVolume "aws-629lf"
Jun  1 16:19:09.905: INFO: Couldn't delete PD "aws://eu-west-1a/vol-0f1b7b72851018209", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f1b7b72851018209 is currently attached to i-0e6e8cb92e7778059
	status code: 400, request id: 52e7ea8f-dbbf-40d9-b94f-82b673e99d56
Jun  1 16:19:15.533: INFO: Couldn't delete PD "aws://eu-west-1a/vol-0f1b7b72851018209", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f1b7b72851018209 is currently attached to i-0e6e8cb92e7778059
	status code: 400, request id: 65ef9c83-ea90-432d-aa76-b5d0fbd4cd40
Jun  1 16:19:21.201: INFO: Couldn't delete PD "aws://eu-west-1a/vol-0f1b7b72851018209", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f1b7b72851018209 is currently attached to i-0e6e8cb92e7778059
	status code: 400, request id: 31ac920f-eaa9-4d37-bc2d-d79ec0c06dae
Jun  1 16:19:26.760: INFO: Couldn't delete PD "aws://eu-west-1a/vol-0f1b7b72851018209", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f1b7b72851018209 is currently attached to i-0e6e8cb92e7778059
	status code: 400, request id: 5a3f6f38-29fc-485a-99f7-397dc1b3167c
Jun  1 16:19:32.297: INFO: Couldn't delete PD "aws://eu-west-1a/vol-0f1b7b72851018209", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f1b7b72851018209 is currently attached to i-0e6e8cb92e7778059
	status code: 400, request id: f24e8d01-f168-4f31-9fec-5db994d63ead
Jun  1 16:19:37.890: INFO: Couldn't delete PD "aws://eu-west-1a/vol-0f1b7b72851018209", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f1b7b72851018209 is currently attached to i-0e6e8cb92e7778059
	status code: 400, request id: 90810343-6697-43cd-9cbc-576efb58155f
Jun  1 16:19:43.539: INFO: Couldn't delete PD "aws://eu-west-1a/vol-0f1b7b72851018209", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f1b7b72851018209 is currently attached to i-0e6e8cb92e7778059
	status code: 400, request id: 6e4d9ad5-4df8-4bae-ba27-75bf5e60b204
Jun  1 16:19:49.189: INFO: Couldn't delete PD "aws://eu-west-1a/vol-0f1b7b72851018209", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f1b7b72851018209 is currently attached to i-0e6e8cb92e7778059
	status code: 400, request id: 7ace53bd-6eeb-40c9-b13d-1a36bca59920
Jun  1 16:19:54.876: INFO: Couldn't delete PD "aws://eu-west-1a/vol-0f1b7b72851018209", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f1b7b72851018209 is currently attached to i-0e6e8cb92e7778059
	status code: 400, request id: 0a9c7850-9095-4ea7-a7e6-617f99281d7e
Jun  1 16:20:00.526: INFO: Successfully deleted PD "aws://eu-west-1a/vol-0f1b7b72851018209".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  1 16:20:00.526: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-4629" for this suite.
... skipping 18 lines ...

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

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

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.qpMXPyqcf/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.qpMXPyqcf/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.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 100 lines ...
Jun  1 16:19:57.846: INFO: Waiting for pod aws-client to disappear
Jun  1 16:19:57.952: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun  1 16:19:57.952: INFO: Deleting PersistentVolumeClaim "pvc-tsvgj"
Jun  1 16:19:58.059: INFO: Deleting PersistentVolume "aws-nhsf9"
Jun  1 16:19:58.798: INFO: Couldn't delete PD "aws://eu-west-1a/vol-04a0436ab2bb1f642", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04a0436ab2bb1f642 is currently attached to i-01c79fe7421f52304
	status code: 400, request id: 586151e6-fa27-461c-9984-1f63a17f1428
Jun  1 16:20:04.422: INFO: Couldn't delete PD "aws://eu-west-1a/vol-04a0436ab2bb1f642", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04a0436ab2bb1f642 is currently attached to i-01c79fe7421f52304
	status code: 400, request id: be83a6d0-0f5a-43c2-b74c-4f3c9bfb1c69
Jun  1 16:20:09.989: INFO: Couldn't delete PD "aws://eu-west-1a/vol-04a0436ab2bb1f642", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04a0436ab2bb1f642 is currently attached to i-01c79fe7421f52304
	status code: 400, request id: 859077d0-1a59-4c41-a176-61eb770477e1
Jun  1 16:20:15.608: INFO: Couldn't delete PD "aws://eu-west-1a/vol-04a0436ab2bb1f642", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04a0436ab2bb1f642 is currently attached to i-01c79fe7421f52304
	status code: 400, request id: 4f20a5b3-bb1a-4160-bcb4-9656b52baa1a
Jun  1 16:20:21.171: INFO: Successfully deleted PD "aws://eu-west-1a/vol-04a0436ab2bb1f642".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  1 16:20:21.171: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-6718" for this suite.
... skipping 87 lines ...
Jun  1 16:19:12.996: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4601nl2ml
STEP: creating a claim
Jun  1 16:19:13.104: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-d6s7
STEP: Creating a pod to test atomic-volume-subpath
Jun  1 16:19:13.424: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-d6s7" in namespace "provisioning-4601" to be "Succeeded or Failed"
Jun  1 16:19:13.530: INFO: Pod "pod-subpath-test-dynamicpv-d6s7": Phase="Pending", Reason="", readiness=false. Elapsed: 105.823778ms
Jun  1 16:19:15.636: INFO: Pod "pod-subpath-test-dynamicpv-d6s7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.212061568s
Jun  1 16:19:17.744: INFO: Pod "pod-subpath-test-dynamicpv-d6s7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.319538434s
Jun  1 16:19:19.850: INFO: Pod "pod-subpath-test-dynamicpv-d6s7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.425597607s
Jun  1 16:19:21.956: INFO: Pod "pod-subpath-test-dynamicpv-d6s7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.532223015s
Jun  1 16:19:24.063: INFO: Pod "pod-subpath-test-dynamicpv-d6s7": Phase="Pending", Reason="", readiness=false. Elapsed: 10.638559382s
... skipping 11 lines ...
Jun  1 16:19:49.346: INFO: Pod "pod-subpath-test-dynamicpv-d6s7": Phase="Running", Reason="", readiness=true. Elapsed: 35.921957841s
Jun  1 16:19:51.452: INFO: Pod "pod-subpath-test-dynamicpv-d6s7": Phase="Running", Reason="", readiness=true. Elapsed: 38.027629305s
Jun  1 16:19:53.557: INFO: Pod "pod-subpath-test-dynamicpv-d6s7": Phase="Running", Reason="", readiness=true. Elapsed: 40.132935235s
Jun  1 16:19:55.664: INFO: Pod "pod-subpath-test-dynamicpv-d6s7": Phase="Running", Reason="", readiness=true. Elapsed: 42.239255843s
Jun  1 16:19:57.770: INFO: Pod "pod-subpath-test-dynamicpv-d6s7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 44.34545578s
STEP: Saw pod success
Jun  1 16:19:57.770: INFO: Pod "pod-subpath-test-dynamicpv-d6s7" satisfied condition "Succeeded or Failed"
Jun  1 16:19:57.875: INFO: Trying to get logs from node ip-172-20-57-30.eu-west-1.compute.internal pod pod-subpath-test-dynamicpv-d6s7 container test-container-subpath-dynamicpv-d6s7: <nil>
STEP: delete the pod
Jun  1 16:19:58.099: INFO: Waiting for pod pod-subpath-test-dynamicpv-d6s7 to disappear
Jun  1 16:19:58.204: INFO: Pod pod-subpath-test-dynamicpv-d6s7 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-d6s7
Jun  1 16:19:58.204: INFO: Deleting pod "pod-subpath-test-dynamicpv-d6s7" in namespace "provisioning-4601"
... skipping 475 lines ...
Jun  1 16:19:37.994: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2570zwxlm
STEP: creating a claim
Jun  1 16:19:38.106: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-nwfl
STEP: Creating a pod to test subpath
Jun  1 16:19:38.431: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-nwfl" in namespace "provisioning-2570" to be "Succeeded or Failed"
Jun  1 16:19:38.539: INFO: Pod "pod-subpath-test-dynamicpv-nwfl": Phase="Pending", Reason="", readiness=false. Elapsed: 107.661165ms
Jun  1 16:19:40.648: INFO: Pod "pod-subpath-test-dynamicpv-nwfl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.21616981s
Jun  1 16:19:42.756: INFO: Pod "pod-subpath-test-dynamicpv-nwfl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.324956776s
Jun  1 16:19:44.865: INFO: Pod "pod-subpath-test-dynamicpv-nwfl": Phase="Pending", Reason="", readiness=false. Elapsed: 6.433525s
Jun  1 16:19:46.973: INFO: Pod "pod-subpath-test-dynamicpv-nwfl": Phase="Pending", Reason="", readiness=false. Elapsed: 8.541086894s
Jun  1 16:19:49.081: INFO: Pod "pod-subpath-test-dynamicpv-nwfl": Phase="Pending", Reason="", readiness=false. Elapsed: 10.649701813s
... skipping 10 lines ...
Jun  1 16:20:12.276: INFO: Pod "pod-subpath-test-dynamicpv-nwfl": Phase="Pending", Reason="", readiness=false. Elapsed: 33.844782698s
Jun  1 16:20:14.385: INFO: Pod "pod-subpath-test-dynamicpv-nwfl": Phase="Pending", Reason="", readiness=false. Elapsed: 35.953364557s
Jun  1 16:20:16.494: INFO: Pod "pod-subpath-test-dynamicpv-nwfl": Phase="Pending", Reason="", readiness=false. Elapsed: 38.062311414s
Jun  1 16:20:18.602: INFO: Pod "pod-subpath-test-dynamicpv-nwfl": Phase="Pending", Reason="", readiness=false. Elapsed: 40.170706247s
Jun  1 16:20:20.710: INFO: Pod "pod-subpath-test-dynamicpv-nwfl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 42.278370113s
STEP: Saw pod success
Jun  1 16:20:20.710: INFO: Pod "pod-subpath-test-dynamicpv-nwfl" satisfied condition "Succeeded or Failed"
Jun  1 16:20:20.817: INFO: Trying to get logs from node ip-172-20-46-125.eu-west-1.compute.internal pod pod-subpath-test-dynamicpv-nwfl container test-container-subpath-dynamicpv-nwfl: <nil>
STEP: delete the pod
Jun  1 16:20:21.042: INFO: Waiting for pod pod-subpath-test-dynamicpv-nwfl to disappear
Jun  1 16:20:21.149: INFO: Pod pod-subpath-test-dynamicpv-nwfl no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-nwfl
Jun  1 16:20:21.149: INFO: Deleting pod "pod-subpath-test-dynamicpv-nwfl" in namespace "provisioning-2570"
STEP: Creating pod pod-subpath-test-dynamicpv-nwfl
STEP: Creating a pod to test subpath
Jun  1 16:20:21.366: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-nwfl" in namespace "provisioning-2570" to be "Succeeded or Failed"
Jun  1 16:20:21.473: INFO: Pod "pod-subpath-test-dynamicpv-nwfl": Phase="Pending", Reason="", readiness=false. Elapsed: 107.271006ms
Jun  1 16:20:23.581: INFO: Pod "pod-subpath-test-dynamicpv-nwfl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.214645017s
STEP: Saw pod success
Jun  1 16:20:23.581: INFO: Pod "pod-subpath-test-dynamicpv-nwfl" satisfied condition "Succeeded or Failed"
Jun  1 16:20:23.688: INFO: Trying to get logs from node ip-172-20-46-125.eu-west-1.compute.internal pod pod-subpath-test-dynamicpv-nwfl container test-container-subpath-dynamicpv-nwfl: <nil>
STEP: delete the pod
Jun  1 16:20:23.925: INFO: Waiting for pod pod-subpath-test-dynamicpv-nwfl to disappear
Jun  1 16:20:24.033: INFO: Pod pod-subpath-test-dynamicpv-nwfl no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-nwfl
Jun  1 16:20:24.033: INFO: Deleting pod "pod-subpath-test-dynamicpv-nwfl" in namespace "provisioning-2570"
... skipping 57 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  1 16:19:54.444: 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.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  1 16:19:54.969: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  1 16:19:55.877: INFO: Successfully created a new PD: "aws://eu-west-1a/vol-0fc6529630e0eed1b".
Jun  1 16:19:55.877: INFO: Creating resource for pre-provisioned PV
Jun  1 16:19:55.877: INFO: Creating PVC and PV
... skipping 5 lines ...
Jun  1 16:20:00.496: INFO: PersistentVolumeClaim pvc-vdkgc found but phase is Pending instead of Bound.
Jun  1 16:20:02.601: INFO: PersistentVolumeClaim pvc-vdkgc found but phase is Pending instead of Bound.
Jun  1 16:20:04.708: INFO: PersistentVolumeClaim pvc-vdkgc found and phase=Bound (8.534750508s)
Jun  1 16:20:04.708: INFO: Waiting up to 3m0s for PersistentVolume aws-96br9 to have phase Bound
Jun  1 16:20:04.813: INFO: PersistentVolume aws-96br9 found and phase=Bound (104.888412ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  1 16:20:07.449: INFO: Deleting pod "pod-2794a27f-5a8b-4634-93da-8f48e573773b" in namespace "volumemode-9687"
Jun  1 16:20:07.554: INFO: Wait up to 5m0s for pod "pod-2794a27f-5a8b-4634-93da-8f48e573773b" to be fully deleted
STEP: Deleting pv and pvc
Jun  1 16:20:17.764: INFO: Deleting PersistentVolumeClaim "pvc-vdkgc"
Jun  1 16:20:17.871: INFO: Deleting PersistentVolume "aws-96br9"
Jun  1 16:20:18.184: INFO: Couldn't delete PD "aws://eu-west-1a/vol-0fc6529630e0eed1b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0fc6529630e0eed1b is currently attached to i-01c79fe7421f52304
	status code: 400, request id: cf801dca-d8d0-48c6-a701-4bda3295f5b7
Jun  1 16:20:23.782: INFO: Couldn't delete PD "aws://eu-west-1a/vol-0fc6529630e0eed1b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0fc6529630e0eed1b is currently attached to i-01c79fe7421f52304
	status code: 400, request id: 888cc774-16c6-4726-8869-fe0b738e5a4c
Jun  1 16:20:29.321: INFO: Couldn't delete PD "aws://eu-west-1a/vol-0fc6529630e0eed1b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0fc6529630e0eed1b is currently attached to i-01c79fe7421f52304
	status code: 400, request id: daac8ccb-9583-4fe7-ac7a-d0831d5486ed
Jun  1 16:20:34.955: INFO: Couldn't delete PD "aws://eu-west-1a/vol-0fc6529630e0eed1b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0fc6529630e0eed1b is currently attached to i-01c79fe7421f52304
	status code: 400, request id: db56d27f-c008-48e8-aad7-e7d53758cf41
Jun  1 16:20:40.586: INFO: Successfully deleted PD "aws://eu-west-1a/vol-0fc6529630e0eed1b".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  1 16:20:40.586: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-9687" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.qpMXPyqcf/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.qpMXPyqcf/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
    /tmp/kops.qpMXPyqcf/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.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 146 lines ...

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 307 lines ...
Jun  1 16:19:55.968: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-3062-e2e-scm4sdx
STEP: creating a claim
Jun  1 16:19:56.075: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-bzwk
STEP: Creating a pod to test exec-volume-test
Jun  1 16:19:56.403: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-bzwk" in namespace "volume-3062" to be "Succeeded or Failed"
Jun  1 16:19:56.508: INFO: Pod "exec-volume-test-dynamicpv-bzwk": Phase="Pending", Reason="", readiness=false. Elapsed: 104.856517ms
Jun  1 16:19:58.618: INFO: Pod "exec-volume-test-dynamicpv-bzwk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.214743873s
Jun  1 16:20:00.723: INFO: Pod "exec-volume-test-dynamicpv-bzwk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.319835068s
Jun  1 16:20:02.828: INFO: Pod "exec-volume-test-dynamicpv-bzwk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.425496313s
Jun  1 16:20:04.934: INFO: Pod "exec-volume-test-dynamicpv-bzwk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.530989196s
Jun  1 16:20:07.039: INFO: Pod "exec-volume-test-dynamicpv-bzwk": Phase="Pending", Reason="", readiness=false. Elapsed: 10.636175374s
... skipping 2 lines ...
Jun  1 16:20:13.354: INFO: Pod "exec-volume-test-dynamicpv-bzwk": Phase="Pending", Reason="", readiness=false. Elapsed: 16.95111003s
Jun  1 16:20:15.460: INFO: Pod "exec-volume-test-dynamicpv-bzwk": Phase="Pending", Reason="", readiness=false. Elapsed: 19.057320544s
Jun  1 16:20:17.565: INFO: Pod "exec-volume-test-dynamicpv-bzwk": Phase="Pending", Reason="", readiness=false. Elapsed: 21.162158277s
Jun  1 16:20:19.671: INFO: Pod "exec-volume-test-dynamicpv-bzwk": Phase="Pending", Reason="", readiness=false. Elapsed: 23.267751638s
Jun  1 16:20:21.776: INFO: Pod "exec-volume-test-dynamicpv-bzwk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 25.372881003s
STEP: Saw pod success
Jun  1 16:20:21.776: INFO: Pod "exec-volume-test-dynamicpv-bzwk" satisfied condition "Succeeded or Failed"
Jun  1 16:20:21.880: INFO: Trying to get logs from node ip-172-20-46-125.eu-west-1.compute.internal pod exec-volume-test-dynamicpv-bzwk container exec-container-dynamicpv-bzwk: <nil>
STEP: delete the pod
Jun  1 16:20:22.099: INFO: Waiting for pod exec-volume-test-dynamicpv-bzwk to disappear
Jun  1 16:20:22.203: INFO: Pod exec-volume-test-dynamicpv-bzwk no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-bzwk
Jun  1 16:20:22.203: INFO: Deleting pod "exec-volume-test-dynamicpv-bzwk" in namespace "volume-3062"
... skipping 743 lines ...
Jun  1 16:20:41.328: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-1234-e2e-schpgjf
STEP: creating a claim
Jun  1 16:20:41.434: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-s996
STEP: Creating a pod to test exec-volume-test
Jun  1 16:20:41.754: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-s996" in namespace "volume-1234" to be "Succeeded or Failed"
Jun  1 16:20:41.859: INFO: Pod "exec-volume-test-dynamicpv-s996": Phase="Pending", Reason="", readiness=false. Elapsed: 104.640366ms
Jun  1 16:20:43.964: INFO: Pod "exec-volume-test-dynamicpv-s996": Phase="Pending", Reason="", readiness=false. Elapsed: 2.210052618s
Jun  1 16:20:46.071: INFO: Pod "exec-volume-test-dynamicpv-s996": Phase="Pending", Reason="", readiness=false. Elapsed: 4.316840788s
Jun  1 16:20:48.176: INFO: Pod "exec-volume-test-dynamicpv-s996": Phase="Pending", Reason="", readiness=false. Elapsed: 6.421857672s
Jun  1 16:20:50.282: INFO: Pod "exec-volume-test-dynamicpv-s996": Phase="Pending", Reason="", readiness=false. Elapsed: 8.527990434s
Jun  1 16:20:52.388: INFO: Pod "exec-volume-test-dynamicpv-s996": Phase="Pending", Reason="", readiness=false. Elapsed: 10.633974216s
Jun  1 16:20:54.495: INFO: Pod "exec-volume-test-dynamicpv-s996": Phase="Pending", Reason="", readiness=false. Elapsed: 12.740650215s
Jun  1 16:20:56.601: INFO: Pod "exec-volume-test-dynamicpv-s996": Phase="Pending", Reason="", readiness=false. Elapsed: 14.846810497s
Jun  1 16:20:58.706: INFO: Pod "exec-volume-test-dynamicpv-s996": Phase="Pending", Reason="", readiness=false. Elapsed: 16.951905137s
Jun  1 16:21:00.811: INFO: Pod "exec-volume-test-dynamicpv-s996": Phase="Pending", Reason="", readiness=false. Elapsed: 19.056986578s
Jun  1 16:21:02.917: INFO: Pod "exec-volume-test-dynamicpv-s996": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.162656356s
STEP: Saw pod success
Jun  1 16:21:02.917: INFO: Pod "exec-volume-test-dynamicpv-s996" satisfied condition "Succeeded or Failed"
Jun  1 16:21:03.031: INFO: Trying to get logs from node ip-172-20-46-125.eu-west-1.compute.internal pod exec-volume-test-dynamicpv-s996 container exec-container-dynamicpv-s996: <nil>
STEP: delete the pod
Jun  1 16:21:03.261: INFO: Waiting for pod exec-volume-test-dynamicpv-s996 to disappear
Jun  1 16:21:03.366: INFO: Pod exec-volume-test-dynamicpv-s996 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-s996
Jun  1 16:21:03.366: INFO: Deleting pod "exec-volume-test-dynamicpv-s996" in namespace "volume-1234"
... skipping 148 lines ...
Jun  1 16:18:39.659: INFO: Creating resource for dynamic PV
Jun  1 16:18:39.659: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-7576-e2e-scf9f6l
STEP: creating a claim
Jun  1 16:18:39.765: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun  1 16:18:40.088: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-48znm" in namespace "snapshotting-7576" to be "Succeeded or Failed"
Jun  1 16:18:40.194: INFO: Pod "pvc-snapshottable-tester-48znm": Phase="Pending", Reason="", readiness=false. Elapsed: 105.796743ms
Jun  1 16:18:42.301: INFO: Pod "pvc-snapshottable-tester-48znm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.212471966s
Jun  1 16:18:44.407: INFO: Pod "pvc-snapshottable-tester-48znm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.318722785s
Jun  1 16:18:46.513: INFO: Pod "pvc-snapshottable-tester-48znm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.425259573s
Jun  1 16:18:48.620: INFO: Pod "pvc-snapshottable-tester-48znm": Phase="Pending", Reason="", readiness=false. Elapsed: 8.531851362s
Jun  1 16:18:50.726: INFO: Pod "pvc-snapshottable-tester-48znm": Phase="Pending", Reason="", readiness=false. Elapsed: 10.63789034s
Jun  1 16:18:52.833: INFO: Pod "pvc-snapshottable-tester-48znm": Phase="Pending", Reason="", readiness=false. Elapsed: 12.74485806s
Jun  1 16:18:54.940: INFO: Pod "pvc-snapshottable-tester-48znm": Phase="Pending", Reason="", readiness=false. Elapsed: 14.851837363s
Jun  1 16:18:57.048: INFO: Pod "pvc-snapshottable-tester-48znm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.959577464s
STEP: Saw pod success
Jun  1 16:18:57.048: INFO: Pod "pvc-snapshottable-tester-48znm" satisfied condition "Succeeded or Failed"
Jun  1 16:18:58.197: INFO: Pod pvc-snapshottable-tester-48znm has the following logs: 
Jun  1 16:18:58.197: INFO: Deleting pod "pvc-snapshottable-tester-48znm" in namespace "snapshotting-7576"
Jun  1 16:18:58.310: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-48znm" to be fully deleted
Jun  1 16:18:58.415: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comzc9lj] to have phase Bound
Jun  1 16:18:58.521: INFO: PersistentVolumeClaim ebs.csi.aws.comzc9lj found and phase=Bound (105.840427ms)
STEP: [init] checking the claim
... skipping 29 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.qpMXPyqcf/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  1 16:19:39.782: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-8b2gn" in namespace "snapshotting-7576" to be "Succeeded or Failed"
Jun  1 16:19:39.890: INFO: Pod "pvc-snapshottable-data-tester-8b2gn": Phase="Pending", Reason="", readiness=false. Elapsed: 108.582429ms
Jun  1 16:19:41.996: INFO: Pod "pvc-snapshottable-data-tester-8b2gn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.21437101s
Jun  1 16:19:44.110: INFO: Pod "pvc-snapshottable-data-tester-8b2gn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.328184019s
Jun  1 16:19:46.217: INFO: Pod "pvc-snapshottable-data-tester-8b2gn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.435142552s
Jun  1 16:19:48.324: INFO: Pod "pvc-snapshottable-data-tester-8b2gn": Phase="Pending", Reason="", readiness=false. Elapsed: 8.542059515s
Jun  1 16:19:50.431: INFO: Pod "pvc-snapshottable-data-tester-8b2gn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.649138771s
STEP: Saw pod success
Jun  1 16:19:50.431: INFO: Pod "pvc-snapshottable-data-tester-8b2gn" satisfied condition "Succeeded or Failed"
Jun  1 16:19:51.033: INFO: Pod pvc-snapshottable-data-tester-8b2gn has the following logs: 
Jun  1 16:19:51.033: INFO: Deleting pod "pvc-snapshottable-data-tester-8b2gn" in namespace "snapshotting-7576"
Jun  1 16:19:51.145: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-8b2gn" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun  1 16:20:03.676: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-7576 exec restored-pvc-tester-z58fl --namespace=snapshotting-7576 -- cat /mnt/test/data'
... skipping 31 lines ...
Jun  1 16:20:29.619: INFO: volumesnapshotcontents snapcontent-97368543-5f92-4498-ac72-0f0860a2951d has been found and is not deleted
Jun  1 16:20:30.725: INFO: volumesnapshotcontents snapcontent-97368543-5f92-4498-ac72-0f0860a2951d has been found and is not deleted
Jun  1 16:20:31.832: INFO: volumesnapshotcontents snapcontent-97368543-5f92-4498-ac72-0f0860a2951d has been found and is not deleted
Jun  1 16:20:32.938: INFO: volumesnapshotcontents snapcontent-97368543-5f92-4498-ac72-0f0860a2951d has been found and is not deleted
Jun  1 16:20:34.047: INFO: volumesnapshotcontents snapcontent-97368543-5f92-4498-ac72-0f0860a2951d has been found and is not deleted
Jun  1 16:20:35.153: INFO: volumesnapshotcontents snapcontent-97368543-5f92-4498-ac72-0f0860a2951d has been found and is not deleted
Jun  1 16:20:36.153: INFO: WaitUntil failed after reaching the timeout 30s
[AfterEach] volume snapshot controller
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:221
Jun  1 16:20:36.262: INFO: Pod restored-pvc-tester-z58fl has the following logs: 
Jun  1 16:20:36.262: INFO: Deleting pod "restored-pvc-tester-z58fl" in namespace "snapshotting-7576"
Jun  1 16:20:36.369: INFO: Wait up to 5m0s for pod "restored-pvc-tester-z58fl" to be fully deleted
Jun  1 16:21:18.584: INFO: deleting claim "snapshotting-7576"/"pvc-ng2wq"
... skipping 67 lines ...
Jun  1 16:20:54.019: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3642ldt69
STEP: creating a claim
Jun  1 16:20:54.125: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-xv6h
STEP: Creating a pod to test subpath
Jun  1 16:20:54.445: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-xv6h" in namespace "provisioning-3642" to be "Succeeded or Failed"
Jun  1 16:20:54.550: INFO: Pod "pod-subpath-test-dynamicpv-xv6h": Phase="Pending", Reason="", readiness=false. Elapsed: 105.596153ms
Jun  1 16:20:56.656: INFO: Pod "pod-subpath-test-dynamicpv-xv6h": Phase="Pending", Reason="", readiness=false. Elapsed: 2.211632203s
Jun  1 16:20:58.763: INFO: Pod "pod-subpath-test-dynamicpv-xv6h": Phase="Pending", Reason="", readiness=false. Elapsed: 4.318012816s
Jun  1 16:21:00.869: INFO: Pod "pod-subpath-test-dynamicpv-xv6h": Phase="Pending", Reason="", readiness=false. Elapsed: 6.424321518s
Jun  1 16:21:02.975: INFO: Pod "pod-subpath-test-dynamicpv-xv6h": Phase="Pending", Reason="", readiness=false. Elapsed: 8.530193297s
Jun  1 16:21:05.081: INFO: Pod "pod-subpath-test-dynamicpv-xv6h": Phase="Pending", Reason="", readiness=false. Elapsed: 10.636045476s
Jun  1 16:21:07.188: INFO: Pod "pod-subpath-test-dynamicpv-xv6h": Phase="Pending", Reason="", readiness=false. Elapsed: 12.74283637s
Jun  1 16:21:09.294: INFO: Pod "pod-subpath-test-dynamicpv-xv6h": Phase="Pending", Reason="", readiness=false. Elapsed: 14.848975703s
Jun  1 16:21:11.400: INFO: Pod "pod-subpath-test-dynamicpv-xv6h": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.955272216s
STEP: Saw pod success
Jun  1 16:21:11.400: INFO: Pod "pod-subpath-test-dynamicpv-xv6h" satisfied condition "Succeeded or Failed"
Jun  1 16:21:11.506: INFO: Trying to get logs from node ip-172-20-46-125.eu-west-1.compute.internal pod pod-subpath-test-dynamicpv-xv6h container test-container-volume-dynamicpv-xv6h: <nil>
STEP: delete the pod
Jun  1 16:21:11.729: INFO: Waiting for pod pod-subpath-test-dynamicpv-xv6h to disappear
Jun  1 16:21:11.834: INFO: Pod pod-subpath-test-dynamicpv-xv6h no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-xv6h
Jun  1 16:21:11.834: INFO: Deleting pod "pod-subpath-test-dynamicpv-xv6h" in namespace "provisioning-3642"
... skipping 59 lines ...
Jun  1 16:20:52.905: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-592-e2e-sc4jcsg
STEP: creating a claim
Jun  1 16:20:53.010: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-ndb8
STEP: Creating a pod to test atomic-volume-subpath
Jun  1 16:20:53.328: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-ndb8" in namespace "provisioning-592" to be "Succeeded or Failed"
Jun  1 16:20:53.432: INFO: Pod "pod-subpath-test-dynamicpv-ndb8": Phase="Pending", Reason="", readiness=false. Elapsed: 104.634391ms
Jun  1 16:20:55.538: INFO: Pod "pod-subpath-test-dynamicpv-ndb8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.210005631s
Jun  1 16:20:57.643: INFO: Pod "pod-subpath-test-dynamicpv-ndb8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.3155214s
Jun  1 16:20:59.749: INFO: Pod "pod-subpath-test-dynamicpv-ndb8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.421527409s
Jun  1 16:21:01.854: INFO: Pod "pod-subpath-test-dynamicpv-ndb8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.526640056s
Jun  1 16:21:03.968: INFO: Pod "pod-subpath-test-dynamicpv-ndb8": Phase="Running", Reason="", readiness=true. Elapsed: 10.639881926s
... skipping 5 lines ...
Jun  1 16:21:16.603: INFO: Pod "pod-subpath-test-dynamicpv-ndb8": Phase="Running", Reason="", readiness=true. Elapsed: 23.275757159s
Jun  1 16:21:18.709: INFO: Pod "pod-subpath-test-dynamicpv-ndb8": Phase="Running", Reason="", readiness=true. Elapsed: 25.381109883s
Jun  1 16:21:20.814: INFO: Pod "pod-subpath-test-dynamicpv-ndb8": Phase="Running", Reason="", readiness=true. Elapsed: 27.486368804s
Jun  1 16:21:22.919: INFO: Pod "pod-subpath-test-dynamicpv-ndb8": Phase="Running", Reason="", readiness=true. Elapsed: 29.591338035s
Jun  1 16:21:25.025: INFO: Pod "pod-subpath-test-dynamicpv-ndb8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 31.697086167s
STEP: Saw pod success
Jun  1 16:21:25.025: INFO: Pod "pod-subpath-test-dynamicpv-ndb8" satisfied condition "Succeeded or Failed"
Jun  1 16:21:25.129: INFO: Trying to get logs from node ip-172-20-60-88.eu-west-1.compute.internal pod pod-subpath-test-dynamicpv-ndb8 container test-container-subpath-dynamicpv-ndb8: <nil>
STEP: delete the pod
Jun  1 16:21:25.354: INFO: Waiting for pod pod-subpath-test-dynamicpv-ndb8 to disappear
Jun  1 16:21:25.459: INFO: Pod pod-subpath-test-dynamicpv-ndb8 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-ndb8
Jun  1 16:21:25.459: INFO: Deleting pod "pod-subpath-test-dynamicpv-ndb8" in namespace "provisioning-592"
... skipping 75 lines ...
Jun  1 16:20:40.864: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-699-e2e-scrtvwm
STEP: creating a claim
Jun  1 16:20:40.973: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-6qzs
STEP: Creating a pod to test subpath
Jun  1 16:20:41.297: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-6qzs" in namespace "provisioning-699" to be "Succeeded or Failed"
Jun  1 16:20:41.405: INFO: Pod "pod-subpath-test-dynamicpv-6qzs": Phase="Pending", Reason="", readiness=false. Elapsed: 107.494222ms
Jun  1 16:20:43.513: INFO: Pod "pod-subpath-test-dynamicpv-6qzs": Phase="Pending", Reason="", readiness=false. Elapsed: 2.215528332s
Jun  1 16:20:45.626: INFO: Pod "pod-subpath-test-dynamicpv-6qzs": Phase="Pending", Reason="", readiness=false. Elapsed: 4.328828476s
Jun  1 16:20:47.735: INFO: Pod "pod-subpath-test-dynamicpv-6qzs": Phase="Pending", Reason="", readiness=false. Elapsed: 6.437486075s
Jun  1 16:20:49.842: INFO: Pod "pod-subpath-test-dynamicpv-6qzs": Phase="Pending", Reason="", readiness=false. Elapsed: 8.545050886s
Jun  1 16:20:51.950: INFO: Pod "pod-subpath-test-dynamicpv-6qzs": Phase="Pending", Reason="", readiness=false. Elapsed: 10.652487306s
Jun  1 16:20:54.061: INFO: Pod "pod-subpath-test-dynamicpv-6qzs": Phase="Pending", Reason="", readiness=false. Elapsed: 12.763389941s
Jun  1 16:20:56.168: INFO: Pod "pod-subpath-test-dynamicpv-6qzs": Phase="Pending", Reason="", readiness=false. Elapsed: 14.871042433s
Jun  1 16:20:58.276: INFO: Pod "pod-subpath-test-dynamicpv-6qzs": Phase="Pending", Reason="", readiness=false. Elapsed: 16.978479635s
Jun  1 16:21:00.385: INFO: Pod "pod-subpath-test-dynamicpv-6qzs": Phase="Pending", Reason="", readiness=false. Elapsed: 19.087713279s
Jun  1 16:21:02.493: INFO: Pod "pod-subpath-test-dynamicpv-6qzs": Phase="Pending", Reason="", readiness=false. Elapsed: 21.195668346s
Jun  1 16:21:04.606: INFO: Pod "pod-subpath-test-dynamicpv-6qzs": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.308903226s
STEP: Saw pod success
Jun  1 16:21:04.606: INFO: Pod "pod-subpath-test-dynamicpv-6qzs" satisfied condition "Succeeded or Failed"
Jun  1 16:21:04.714: INFO: Trying to get logs from node ip-172-20-57-211.eu-west-1.compute.internal pod pod-subpath-test-dynamicpv-6qzs container test-container-volume-dynamicpv-6qzs: <nil>
STEP: delete the pod
Jun  1 16:21:04.993: INFO: Waiting for pod pod-subpath-test-dynamicpv-6qzs to disappear
Jun  1 16:21:05.100: INFO: Pod pod-subpath-test-dynamicpv-6qzs no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-6qzs
Jun  1 16:21:05.100: INFO: Deleting pod "pod-subpath-test-dynamicpv-6qzs" in namespace "provisioning-699"
... skipping 109 lines ...
Jun  1 16:21:29.541: INFO: Waiting for pod aws-client to disappear
Jun  1 16:21:29.679: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun  1 16:21:29.679: INFO: Deleting PersistentVolumeClaim "pvc-wb7l4"
Jun  1 16:21:29.787: INFO: Deleting PersistentVolume "aws-67r45"
Jun  1 16:21:30.636: INFO: Couldn't delete PD "aws://eu-west-1a/vol-096daae9d57cef951", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-096daae9d57cef951 is currently attached to i-0e6e8cb92e7778059
	status code: 400, request id: e98a5390-a64e-4915-9906-ffe4a9825ecb
Jun  1 16:21:36.246: INFO: Couldn't delete PD "aws://eu-west-1a/vol-096daae9d57cef951", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-096daae9d57cef951 is currently attached to i-0e6e8cb92e7778059
	status code: 400, request id: f0db943b-1f97-45c3-9890-75c3692eba3b
Jun  1 16:21:42.001: INFO: Successfully deleted PD "aws://eu-west-1a/vol-096daae9d57cef951".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  1 16:21:42.001: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-6208" for this suite.
... skipping 96 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  1 16:20:39.823: 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.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun  1 16:20:40.357: INFO: Creating resource for dynamic PV
Jun  1 16:20:40.357: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9022-e2e-scbmzwb
STEP: creating a claim
Jun  1 16:20:40.465: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-lw2b
STEP: Checking for subpath error in container status
Jun  1 16:21:21.005: INFO: Deleting pod "pod-subpath-test-dynamicpv-lw2b" in namespace "provisioning-9022"
Jun  1 16:21:21.115: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-lw2b" to be fully deleted
STEP: Deleting pod
Jun  1 16:21:29.330: INFO: Deleting pod "pod-subpath-test-dynamicpv-lw2b" in namespace "provisioning-9022"
STEP: Deleting pvc
Jun  1 16:21:29.679: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comgnfj7"
... skipping 11 lines ...

• [SLOW TEST:65.738 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.qpMXPyqcf/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.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (ext3)] volumes
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  1 16:21:45.564: INFO: Driver aws doesn't support ext3 -- skipping
[AfterEach] [Testpattern: Pre-provisioned PV (ext3)] volumes
... skipping 29 lines ...
Jun  1 16:21:00.847: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-2642v24vd
STEP: creating a claim
Jun  1 16:21:00.954: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-qrlq
STEP: Creating a pod to test exec-volume-test
Jun  1 16:21:01.271: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-qrlq" in namespace "volume-2642" to be "Succeeded or Failed"
Jun  1 16:21:01.375: INFO: Pod "exec-volume-test-dynamicpv-qrlq": Phase="Pending", Reason="", readiness=false. Elapsed: 104.532612ms
Jun  1 16:21:03.480: INFO: Pod "exec-volume-test-dynamicpv-qrlq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.209546227s
Jun  1 16:21:05.589: INFO: Pod "exec-volume-test-dynamicpv-qrlq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.317867493s
Jun  1 16:21:07.695: INFO: Pod "exec-volume-test-dynamicpv-qrlq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.423791811s
Jun  1 16:21:09.801: INFO: Pod "exec-volume-test-dynamicpv-qrlq": Phase="Pending", Reason="", readiness=false. Elapsed: 8.530090204s
Jun  1 16:21:11.907: INFO: Pod "exec-volume-test-dynamicpv-qrlq": Phase="Pending", Reason="", readiness=false. Elapsed: 10.635990438s
... skipping 2 lines ...
Jun  1 16:21:18.228: INFO: Pod "exec-volume-test-dynamicpv-qrlq": Phase="Pending", Reason="", readiness=false. Elapsed: 16.95729131s
Jun  1 16:21:20.333: INFO: Pod "exec-volume-test-dynamicpv-qrlq": Phase="Pending", Reason="", readiness=false. Elapsed: 19.062292777s
Jun  1 16:21:22.439: INFO: Pod "exec-volume-test-dynamicpv-qrlq": Phase="Pending", Reason="", readiness=false. Elapsed: 21.168339101s
Jun  1 16:21:24.548: INFO: Pod "exec-volume-test-dynamicpv-qrlq": Phase="Pending", Reason="", readiness=false. Elapsed: 23.277373485s
Jun  1 16:21:26.654: INFO: Pod "exec-volume-test-dynamicpv-qrlq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 25.382913235s
STEP: Saw pod success
Jun  1 16:21:26.654: INFO: Pod "exec-volume-test-dynamicpv-qrlq" satisfied condition "Succeeded or Failed"
Jun  1 16:21:26.759: INFO: Trying to get logs from node ip-172-20-60-88.eu-west-1.compute.internal pod exec-volume-test-dynamicpv-qrlq container exec-container-dynamicpv-qrlq: <nil>
STEP: delete the pod
Jun  1 16:21:26.981: INFO: Waiting for pod exec-volume-test-dynamicpv-qrlq to disappear
Jun  1 16:21:27.086: INFO: Pod exec-volume-test-dynamicpv-qrlq no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-qrlq
Jun  1 16:21:27.086: INFO: Deleting pod "exec-volume-test-dynamicpv-qrlq" in namespace "volume-2642"
... skipping 206 lines ...
Jun  1 16:19:13.027: INFO: Creating resource for dynamic PV
Jun  1 16:19:13.027: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-8186-e2e-scrkgmn
STEP: creating a claim
Jun  1 16:19:13.134: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun  1 16:19:13.458: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-gqrmg" in namespace "snapshotting-8186" to be "Succeeded or Failed"
Jun  1 16:19:13.567: INFO: Pod "pvc-snapshottable-tester-gqrmg": Phase="Pending", Reason="", readiness=false. Elapsed: 108.88344ms
Jun  1 16:19:15.677: INFO: Pod "pvc-snapshottable-tester-gqrmg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.218511338s
Jun  1 16:19:17.785: INFO: Pod "pvc-snapshottable-tester-gqrmg": Phase="Pending", Reason="", readiness=false. Elapsed: 4.326317777s
Jun  1 16:19:19.892: INFO: Pod "pvc-snapshottable-tester-gqrmg": Phase="Pending", Reason="", readiness=false. Elapsed: 6.433406511s
Jun  1 16:19:21.999: INFO: Pod "pvc-snapshottable-tester-gqrmg": Phase="Pending", Reason="", readiness=false. Elapsed: 8.540270013s
Jun  1 16:19:24.114: INFO: Pod "pvc-snapshottable-tester-gqrmg": Phase="Pending", Reason="", readiness=false. Elapsed: 10.655623543s
Jun  1 16:19:26.221: INFO: Pod "pvc-snapshottable-tester-gqrmg": Phase="Pending", Reason="", readiness=false. Elapsed: 12.762418298s
Jun  1 16:19:28.328: INFO: Pod "pvc-snapshottable-tester-gqrmg": Phase="Pending", Reason="", readiness=false. Elapsed: 14.869394429s
Jun  1 16:19:30.437: INFO: Pod "pvc-snapshottable-tester-gqrmg": Phase="Pending", Reason="", readiness=false. Elapsed: 16.978504349s
Jun  1 16:19:32.545: INFO: Pod "pvc-snapshottable-tester-gqrmg": Phase="Pending", Reason="", readiness=false. Elapsed: 19.086947894s
Jun  1 16:19:34.654: INFO: Pod "pvc-snapshottable-tester-gqrmg": Phase="Pending", Reason="", readiness=false. Elapsed: 21.195734458s
Jun  1 16:19:36.761: INFO: Pod "pvc-snapshottable-tester-gqrmg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.303023637s
STEP: Saw pod success
Jun  1 16:19:36.761: INFO: Pod "pvc-snapshottable-tester-gqrmg" satisfied condition "Succeeded or Failed"
Jun  1 16:19:36.976: INFO: Pod pvc-snapshottable-tester-gqrmg has the following logs: 
Jun  1 16:19:36.976: INFO: Deleting pod "pvc-snapshottable-tester-gqrmg" in namespace "snapshotting-8186"
Jun  1 16:19:37.088: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-gqrmg" to be fully deleted
Jun  1 16:19:37.195: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comppsvp] to have phase Bound
Jun  1 16:19:37.303: INFO: PersistentVolumeClaim ebs.csi.aws.comppsvp found and phase=Bound (107.633923ms)
STEP: [init] checking the claim
... skipping 18 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.qpMXPyqcf/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  1 16:19:55.352: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-kcthm" in namespace "snapshotting-8186" to be "Succeeded or Failed"
Jun  1 16:19:55.463: INFO: Pod "pvc-snapshottable-data-tester-kcthm": Phase="Pending", Reason="", readiness=false. Elapsed: 110.60701ms
Jun  1 16:19:57.571: INFO: Pod "pvc-snapshottable-data-tester-kcthm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.219239344s
Jun  1 16:19:59.679: INFO: Pod "pvc-snapshottable-data-tester-kcthm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.327157737s
Jun  1 16:20:01.787: INFO: Pod "pvc-snapshottable-data-tester-kcthm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.434562151s
Jun  1 16:20:03.895: INFO: Pod "pvc-snapshottable-data-tester-kcthm": Phase="Pending", Reason="", readiness=false. Elapsed: 8.543054227s
Jun  1 16:20:06.003: INFO: Pod "pvc-snapshottable-data-tester-kcthm": Phase="Pending", Reason="", readiness=false. Elapsed: 10.651040016s
... skipping 21 lines ...
Jun  1 16:20:52.375: INFO: Pod "pvc-snapshottable-data-tester-kcthm": Phase="Pending", Reason="", readiness=false. Elapsed: 57.023206556s
Jun  1 16:20:54.482: INFO: Pod "pvc-snapshottable-data-tester-kcthm": Phase="Pending", Reason="", readiness=false. Elapsed: 59.13001114s
Jun  1 16:20:56.590: INFO: Pod "pvc-snapshottable-data-tester-kcthm": Phase="Pending", Reason="", readiness=false. Elapsed: 1m1.23790985s
Jun  1 16:20:58.697: INFO: Pod "pvc-snapshottable-data-tester-kcthm": Phase="Pending", Reason="", readiness=false. Elapsed: 1m3.345125879s
Jun  1 16:21:00.811: INFO: Pod "pvc-snapshottable-data-tester-kcthm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m5.458723338s
STEP: Saw pod success
Jun  1 16:21:00.811: INFO: Pod "pvc-snapshottable-data-tester-kcthm" satisfied condition "Succeeded or Failed"
Jun  1 16:21:01.025: INFO: Pod pvc-snapshottable-data-tester-kcthm has the following logs: 
Jun  1 16:21:01.025: INFO: Deleting pod "pvc-snapshottable-data-tester-kcthm" in namespace "snapshotting-8186"
Jun  1 16:21:01.141: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-kcthm" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun  1 16:21:11.680: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-8186 exec restored-pvc-tester-gg6tl --namespace=snapshotting-8186 -- cat /mnt/test/data'
... skipping 59 lines ...
Jun  1 16:21:25.419: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-3474xhvfw
STEP: creating a claim
Jun  1 16:21:25.525: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Jun  1 16:21:25.747: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun  1 16:21:25.956: INFO: Error updating pvc aws74w8s: PersistentVolumeClaim "aws74w8s" 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-3474xhvfw",
  	... // 2 identical fields
  }

Jun  1 16:21:28.166: INFO: Error updating pvc aws74w8s: PersistentVolumeClaim "aws74w8s" 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-3474xhvfw",
  	... // 2 identical fields
  }

Jun  1 16:21:30.175: INFO: Error updating pvc aws74w8s: PersistentVolumeClaim "aws74w8s" 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-3474xhvfw",
  	... // 2 identical fields
  }

Jun  1 16:21:32.168: INFO: Error updating pvc aws74w8s: PersistentVolumeClaim "aws74w8s" 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-3474xhvfw",
  	... // 2 identical fields
  }

Jun  1 16:21:34.170: INFO: Error updating pvc aws74w8s: PersistentVolumeClaim "aws74w8s" 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-3474xhvfw",
  	... // 2 identical fields
  }

Jun  1 16:21:36.166: INFO: Error updating pvc aws74w8s: PersistentVolumeClaim "aws74w8s" 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-3474xhvfw",
  	... // 2 identical fields
  }

Jun  1 16:21:38.166: INFO: Error updating pvc aws74w8s: PersistentVolumeClaim "aws74w8s" 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-3474xhvfw",
  	... // 2 identical fields
  }

Jun  1 16:21:40.166: INFO: Error updating pvc aws74w8s: PersistentVolumeClaim "aws74w8s" 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-3474xhvfw",
  	... // 2 identical fields
  }

Jun  1 16:21:42.166: INFO: Error updating pvc aws74w8s: PersistentVolumeClaim "aws74w8s" 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-3474xhvfw",
  	... // 2 identical fields
  }

Jun  1 16:21:44.169: INFO: Error updating pvc aws74w8s: PersistentVolumeClaim "aws74w8s" 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-3474xhvfw",
  	... // 2 identical fields
  }

Jun  1 16:21:46.166: INFO: Error updating pvc aws74w8s: PersistentVolumeClaim "aws74w8s" 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-3474xhvfw",
  	... // 2 identical fields
  }

Jun  1 16:21:48.167: INFO: Error updating pvc aws74w8s: PersistentVolumeClaim "aws74w8s" 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-3474xhvfw",
  	... // 2 identical fields
  }

Jun  1 16:21:50.169: INFO: Error updating pvc aws74w8s: PersistentVolumeClaim "aws74w8s" 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-3474xhvfw",
  	... // 2 identical fields
  }

Jun  1 16:21:52.168: INFO: Error updating pvc aws74w8s: PersistentVolumeClaim "aws74w8s" 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-3474xhvfw",
  	... // 2 identical fields
  }

Jun  1 16:21:54.169: INFO: Error updating pvc aws74w8s: PersistentVolumeClaim "aws74w8s" 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-3474xhvfw",
  	... // 2 identical fields
  }

Jun  1 16:21:56.171: INFO: Error updating pvc aws74w8s: PersistentVolumeClaim "aws74w8s" 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-3474xhvfw",
  	... // 2 identical fields
  }

Jun  1 16:21:56.380: INFO: Error updating pvc aws74w8s: PersistentVolumeClaim "aws74w8s" 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 308 lines ...
Jun  1 16:21:59.689: INFO: Waiting for pod aws-client to disappear
Jun  1 16:21:59.798: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun  1 16:21:59.798: INFO: Deleting PersistentVolumeClaim "pvc-jc726"
Jun  1 16:21:59.904: INFO: Deleting PersistentVolume "aws-q27lt"
Jun  1 16:22:00.623: INFO: Couldn't delete PD "aws://eu-west-1a/vol-0dfc759c3aec7c4c5", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0dfc759c3aec7c4c5 is currently attached to i-0e6e8cb92e7778059
	status code: 400, request id: f1b87f90-9377-4318-9427-1ec76ac5f13d
Jun  1 16:22:06.253: INFO: Successfully deleted PD "aws://eu-west-1a/vol-0dfc759c3aec7c4c5".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  1 16:22:06.253: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8357" for this suite.
... skipping 22 lines ...
Jun  1 16:21:06.293: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  1 16:21:07.194: INFO: Successfully created a new PD: "aws://eu-west-1a/vol-0fd83f4065d1d35a3".
Jun  1 16:21:07.194: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-cslk
STEP: Creating a pod to test exec-volume-test
Jun  1 16:21:07.304: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-cslk" in namespace "volume-3519" to be "Succeeded or Failed"
Jun  1 16:21:07.410: INFO: Pod "exec-volume-test-inlinevolume-cslk": Phase="Pending", Reason="", readiness=false. Elapsed: 106.547119ms
Jun  1 16:21:09.518: INFO: Pod "exec-volume-test-inlinevolume-cslk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.214674778s
Jun  1 16:21:11.625: INFO: Pod "exec-volume-test-inlinevolume-cslk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.321429548s
Jun  1 16:21:13.732: INFO: Pod "exec-volume-test-inlinevolume-cslk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.428337928s
Jun  1 16:21:15.842: INFO: Pod "exec-volume-test-inlinevolume-cslk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.538576458s
Jun  1 16:21:17.949: INFO: Pod "exec-volume-test-inlinevolume-cslk": Phase="Pending", Reason="", readiness=false. Elapsed: 10.645454565s
... skipping 7 lines ...
Jun  1 16:21:34.817: INFO: Pod "exec-volume-test-inlinevolume-cslk": Phase="Pending", Reason="", readiness=false. Elapsed: 27.513673367s
Jun  1 16:21:36.924: INFO: Pod "exec-volume-test-inlinevolume-cslk": Phase="Pending", Reason="", readiness=false. Elapsed: 29.620429809s
Jun  1 16:21:39.032: INFO: Pod "exec-volume-test-inlinevolume-cslk": Phase="Pending", Reason="", readiness=false. Elapsed: 31.728498644s
Jun  1 16:21:41.139: INFO: Pod "exec-volume-test-inlinevolume-cslk": Phase="Pending", Reason="", readiness=false. Elapsed: 33.835553823s
Jun  1 16:21:43.246: INFO: Pod "exec-volume-test-inlinevolume-cslk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 35.942548091s
STEP: Saw pod success
Jun  1 16:21:43.246: INFO: Pod "exec-volume-test-inlinevolume-cslk" satisfied condition "Succeeded or Failed"
Jun  1 16:21:43.353: INFO: Trying to get logs from node ip-172-20-57-211.eu-west-1.compute.internal pod exec-volume-test-inlinevolume-cslk container exec-container-inlinevolume-cslk: <nil>
STEP: delete the pod
Jun  1 16:21:43.574: INFO: Waiting for pod exec-volume-test-inlinevolume-cslk to disappear
Jun  1 16:21:43.681: INFO: Pod exec-volume-test-inlinevolume-cslk no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-cslk
Jun  1 16:21:43.681: INFO: Deleting pod "exec-volume-test-inlinevolume-cslk" in namespace "volume-3519"
Jun  1 16:21:44.015: INFO: Couldn't delete PD "aws://eu-west-1a/vol-0fd83f4065d1d35a3", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0fd83f4065d1d35a3 is currently attached to i-029b919ec39ba6f76
	status code: 400, request id: c208a845-75e4-4c80-8117-f50299a50455
Jun  1 16:21:49.547: INFO: Couldn't delete PD "aws://eu-west-1a/vol-0fd83f4065d1d35a3", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0fd83f4065d1d35a3 is currently attached to i-029b919ec39ba6f76
	status code: 400, request id: 7b156449-6ba9-4652-84e2-51479825b9e0
Jun  1 16:21:55.176: INFO: Couldn't delete PD "aws://eu-west-1a/vol-0fd83f4065d1d35a3", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0fd83f4065d1d35a3 is currently attached to i-029b919ec39ba6f76
	status code: 400, request id: 5ae08bb2-79ca-406e-914f-c56154ddae80
Jun  1 16:22:00.754: INFO: Couldn't delete PD "aws://eu-west-1a/vol-0fd83f4065d1d35a3", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0fd83f4065d1d35a3 is currently attached to i-029b919ec39ba6f76
	status code: 400, request id: 4eab3132-ce7a-4c7c-a54b-a03f20542df4
Jun  1 16:22:06.379: INFO: Successfully deleted PD "aws://eu-west-1a/vol-0fd83f4065d1d35a3".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  1 16:22:06.379: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-3519" for this suite.
... skipping 265 lines ...
Jun  1 16:21:00.110: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-2182hjf6f      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-2182    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-2182hjf6f,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-2182    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-2182hjf6f,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-2182    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-2182hjf6f,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-2182hjf6f    3c4f6541-a0ea-4831-bbba-970b136950cb 7569 0 2021-06-01 16:21:00 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-01 16:21:00 +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-bsz97 pvc- provisioning-2182  18f1341f-8926-48a6-9a44-feb26d69590e 7580 0 2021-06-01 16:21:00 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-01 16:21:00 +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-2182hjf6f,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-22f8ab1b-ce43-4626-af5d-8c261efb5b46 in namespace provisioning-2182
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun  1 16:21:13.300: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-jh8fn" in namespace "provisioning-2182" to be "Succeeded or Failed"
Jun  1 16:21:13.406: INFO: Pod "pvc-volume-tester-writer-jh8fn": Phase="Pending", Reason="", readiness=false. Elapsed: 105.98598ms
Jun  1 16:21:15.513: INFO: Pod "pvc-volume-tester-writer-jh8fn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.212834967s
Jun  1 16:21:17.620: INFO: Pod "pvc-volume-tester-writer-jh8fn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.319991188s
Jun  1 16:21:19.728: INFO: Pod "pvc-volume-tester-writer-jh8fn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.427583951s
Jun  1 16:21:21.835: INFO: Pod "pvc-volume-tester-writer-jh8fn": Phase="Pending", Reason="", readiness=false. Elapsed: 8.535366954s
Jun  1 16:21:23.942: INFO: Pod "pvc-volume-tester-writer-jh8fn": Phase="Pending", Reason="", readiness=false. Elapsed: 10.642141037s
... skipping 6 lines ...
Jun  1 16:21:38.698: INFO: Pod "pvc-volume-tester-writer-jh8fn": Phase="Pending", Reason="", readiness=false. Elapsed: 25.398253558s
Jun  1 16:21:40.806: INFO: Pod "pvc-volume-tester-writer-jh8fn": Phase="Pending", Reason="", readiness=false. Elapsed: 27.505830411s
Jun  1 16:21:42.912: INFO: Pod "pvc-volume-tester-writer-jh8fn": Phase="Pending", Reason="", readiness=false. Elapsed: 29.612424751s
Jun  1 16:21:45.020: INFO: Pod "pvc-volume-tester-writer-jh8fn": Phase="Pending", Reason="", readiness=false. Elapsed: 31.720360657s
Jun  1 16:21:47.164: INFO: Pod "pvc-volume-tester-writer-jh8fn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 33.863850752s
STEP: Saw pod success
Jun  1 16:21:47.164: INFO: Pod "pvc-volume-tester-writer-jh8fn" satisfied condition "Succeeded or Failed"
Jun  1 16:21:47.382: INFO: Pod pvc-volume-tester-writer-jh8fn has the following logs: 
Jun  1 16:21:47.382: INFO: Deleting pod "pvc-volume-tester-writer-jh8fn" in namespace "provisioning-2182"
Jun  1 16:21:47.497: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-jh8fn" 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-46-125.eu-west-1.compute.internal"
Jun  1 16:21:47.944: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-gk89x" in namespace "provisioning-2182" to be "Succeeded or Failed"
Jun  1 16:21:48.051: INFO: Pod "pvc-volume-tester-reader-gk89x": Phase="Pending", Reason="", readiness=false. Elapsed: 107.150746ms
Jun  1 16:21:50.158: INFO: Pod "pvc-volume-tester-reader-gk89x": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.214552046s
STEP: Saw pod success
Jun  1 16:21:50.158: INFO: Pod "pvc-volume-tester-reader-gk89x" satisfied condition "Succeeded or Failed"
Jun  1 16:21:50.372: INFO: Pod pvc-volume-tester-reader-gk89x has the following logs: hello world

Jun  1 16:21:50.372: INFO: Deleting pod "pvc-volume-tester-reader-gk89x" in namespace "provisioning-2182"
Jun  1 16:21:50.511: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-gk89x" to be fully deleted
Jun  1 16:21:50.619: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-bsz97] to have phase Bound
Jun  1 16:21:50.729: INFO: PersistentVolumeClaim pvc-bsz97 found and phase=Bound (110.909779ms)
... skipping 81 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  1 16:21:48.363: 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.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  1 16:21:48.887: INFO: Creating resource for dynamic PV
Jun  1 16:21:48.887: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-9629-e2e-scpv7zz
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  1 16:21:55.623: INFO: Deleting pod "pod-87ad0de7-78f3-4cb6-9030-3386e6633ddd" in namespace "volumemode-9629"
Jun  1 16:21:55.737: INFO: Wait up to 5m0s for pod "pod-87ad0de7-78f3-4cb6-9030-3386e6633ddd" to be fully deleted
STEP: Deleting pvc
Jun  1 16:22:08.157: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comz5tmc"
Jun  1 16:22:08.262: INFO: Waiting up to 5m0s for PersistentVolume pvc-2913a4da-dbae-4131-ba7f-388d17cd3240 to get deleted
Jun  1 16:22:08.366: INFO: PersistentVolume pvc-2913a4da-dbae-4131-ba7f-388d17cd3240 found and phase=Released (104.409184ms)
... skipping 9 lines ...

• [SLOW TEST:35.643 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.qpMXPyqcf/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.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (xfs)][Slow] volumes
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (xfs)][Slow] volumes
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 8 lines ...
Jun  1 16:22:01.479: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-2484672tn
STEP: creating a claim
Jun  1 16:22:01.586: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-k26j
STEP: Creating a pod to test exec-volume-test
Jun  1 16:22:01.910: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-k26j" in namespace "volume-2484" to be "Succeeded or Failed"
Jun  1 16:22:02.015: INFO: Pod "exec-volume-test-dynamicpv-k26j": Phase="Pending", Reason="", readiness=false. Elapsed: 105.217406ms
Jun  1 16:22:04.122: INFO: Pod "exec-volume-test-dynamicpv-k26j": Phase="Pending", Reason="", readiness=false. Elapsed: 2.211885795s
Jun  1 16:22:06.228: INFO: Pod "exec-volume-test-dynamicpv-k26j": Phase="Pending", Reason="", readiness=false. Elapsed: 4.318526064s
Jun  1 16:22:08.334: INFO: Pod "exec-volume-test-dynamicpv-k26j": Phase="Pending", Reason="", readiness=false. Elapsed: 6.424504052s
Jun  1 16:22:10.440: INFO: Pod "exec-volume-test-dynamicpv-k26j": Phase="Pending", Reason="", readiness=false. Elapsed: 8.52985491s
Jun  1 16:22:12.547: INFO: Pod "exec-volume-test-dynamicpv-k26j": Phase="Pending", Reason="", readiness=false. Elapsed: 10.637663862s
Jun  1 16:22:14.653: INFO: Pod "exec-volume-test-dynamicpv-k26j": Phase="Pending", Reason="", readiness=false. Elapsed: 12.743684139s
Jun  1 16:22:16.758: INFO: Pod "exec-volume-test-dynamicpv-k26j": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.848460431s
STEP: Saw pod success
Jun  1 16:22:16.758: INFO: Pod "exec-volume-test-dynamicpv-k26j" satisfied condition "Succeeded or Failed"
Jun  1 16:22:16.863: INFO: Trying to get logs from node ip-172-20-57-30.eu-west-1.compute.internal pod exec-volume-test-dynamicpv-k26j container exec-container-dynamicpv-k26j: <nil>
STEP: delete the pod
Jun  1 16:22:17.087: INFO: Waiting for pod exec-volume-test-dynamicpv-k26j to disappear
Jun  1 16:22:17.192: INFO: Pod exec-volume-test-dynamicpv-k26j no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-k26j
Jun  1 16:22:17.192: INFO: Deleting pod "exec-volume-test-dynamicpv-k26j" in namespace "volume-2484"
... skipping 94 lines ...
Jun  1 16:21:43.010: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-27485drkz
STEP: creating a claim
Jun  1 16:21:43.115: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-462j
STEP: Creating a pod to test multi_subpath
Jun  1 16:21:43.433: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-462j" in namespace "provisioning-2748" to be "Succeeded or Failed"
Jun  1 16:21:43.538: INFO: Pod "pod-subpath-test-dynamicpv-462j": Phase="Pending", Reason="", readiness=false. Elapsed: 104.960156ms
Jun  1 16:21:45.643: INFO: Pod "pod-subpath-test-dynamicpv-462j": Phase="Pending", Reason="", readiness=false. Elapsed: 2.210092011s
Jun  1 16:21:47.756: INFO: Pod "pod-subpath-test-dynamicpv-462j": Phase="Pending", Reason="", readiness=false. Elapsed: 4.322622484s
Jun  1 16:21:49.861: INFO: Pod "pod-subpath-test-dynamicpv-462j": Phase="Pending", Reason="", readiness=false. Elapsed: 6.42764045s
Jun  1 16:21:51.966: INFO: Pod "pod-subpath-test-dynamicpv-462j": Phase="Pending", Reason="", readiness=false. Elapsed: 8.5326778s
Jun  1 16:21:54.073: INFO: Pod "pod-subpath-test-dynamicpv-462j": Phase="Pending", Reason="", readiness=false. Elapsed: 10.640230599s
Jun  1 16:21:56.178: INFO: Pod "pod-subpath-test-dynamicpv-462j": Phase="Pending", Reason="", readiness=false. Elapsed: 12.745240229s
Jun  1 16:21:58.287: INFO: Pod "pod-subpath-test-dynamicpv-462j": Phase="Pending", Reason="", readiness=false. Elapsed: 14.854173519s
Jun  1 16:22:00.392: INFO: Pod "pod-subpath-test-dynamicpv-462j": Phase="Pending", Reason="", readiness=false. Elapsed: 16.959336984s
Jun  1 16:22:02.498: INFO: Pod "pod-subpath-test-dynamicpv-462j": Phase="Pending", Reason="", readiness=false. Elapsed: 19.065007093s
Jun  1 16:22:04.604: INFO: Pod "pod-subpath-test-dynamicpv-462j": Phase="Pending", Reason="", readiness=false. Elapsed: 21.171419796s
Jun  1 16:22:06.715: INFO: Pod "pod-subpath-test-dynamicpv-462j": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.282163208s
STEP: Saw pod success
Jun  1 16:22:06.715: INFO: Pod "pod-subpath-test-dynamicpv-462j" satisfied condition "Succeeded or Failed"
Jun  1 16:22:06.820: INFO: Trying to get logs from node ip-172-20-57-211.eu-west-1.compute.internal pod pod-subpath-test-dynamicpv-462j container test-container-subpath-dynamicpv-462j: <nil>
STEP: delete the pod
Jun  1 16:22:07.036: INFO: Waiting for pod pod-subpath-test-dynamicpv-462j to disappear
Jun  1 16:22:07.140: INFO: Pod pod-subpath-test-dynamicpv-462j no longer exists
STEP: Deleting pod
Jun  1 16:22:07.140: INFO: Deleting pod "pod-subpath-test-dynamicpv-462j" in namespace "provisioning-2748"
... skipping 168 lines ...
Jun  1 16:22:02.932: INFO: Waiting up to timeout=3m0s for PersistentVolumeClaims [pvc-kclrc] to have phase Bound
Jun  1 16:22:03.038: INFO: PersistentVolumeClaim pvc-kclrc found and phase=Bound (105.940574ms)
Jun  1 16:22:03.038: INFO: Waiting up to 3m0s for PersistentVolume aws-qxttv to have phase Bound
Jun  1 16:22:03.144: INFO: PersistentVolume aws-qxttv found and phase=Bound (106.105027ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-fhwj
STEP: Creating a pod to test exec-volume-test
Jun  1 16:22:03.464: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-fhwj" in namespace "volume-4503" to be "Succeeded or Failed"
Jun  1 16:22:03.574: INFO: Pod "exec-volume-test-preprovisionedpv-fhwj": Phase="Pending", Reason="", readiness=false. Elapsed: 110.621245ms
Jun  1 16:22:05.682: INFO: Pod "exec-volume-test-preprovisionedpv-fhwj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.217994228s
Jun  1 16:22:07.788: INFO: Pod "exec-volume-test-preprovisionedpv-fhwj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.324730146s
Jun  1 16:22:09.895: INFO: Pod "exec-volume-test-preprovisionedpv-fhwj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.431426177s
Jun  1 16:22:12.002: INFO: Pod "exec-volume-test-preprovisionedpv-fhwj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.538561754s
Jun  1 16:22:14.110: INFO: Pod "exec-volume-test-preprovisionedpv-fhwj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.646141525s
STEP: Saw pod success
Jun  1 16:22:14.110: INFO: Pod "exec-volume-test-preprovisionedpv-fhwj" satisfied condition "Succeeded or Failed"
Jun  1 16:22:14.218: INFO: Trying to get logs from node ip-172-20-57-211.eu-west-1.compute.internal pod exec-volume-test-preprovisionedpv-fhwj container exec-container-preprovisionedpv-fhwj: <nil>
STEP: delete the pod
Jun  1 16:22:14.437: INFO: Waiting for pod exec-volume-test-preprovisionedpv-fhwj to disappear
Jun  1 16:22:14.544: INFO: Pod exec-volume-test-preprovisionedpv-fhwj no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-fhwj
Jun  1 16:22:14.544: INFO: Deleting pod "exec-volume-test-preprovisionedpv-fhwj" in namespace "volume-4503"
STEP: Deleting pv and pvc
Jun  1 16:22:14.650: INFO: Deleting PersistentVolumeClaim "pvc-kclrc"
Jun  1 16:22:14.757: INFO: Deleting PersistentVolume "aws-qxttv"
Jun  1 16:22:15.062: INFO: Couldn't delete PD "aws://eu-west-1a/vol-01d100fb934477d3b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01d100fb934477d3b is currently attached to i-029b919ec39ba6f76
	status code: 400, request id: 24d25bd2-4be6-4c7f-a8ef-3e57c1d18b1f
Jun  1 16:22:20.696: INFO: Couldn't delete PD "aws://eu-west-1a/vol-01d100fb934477d3b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01d100fb934477d3b is currently attached to i-029b919ec39ba6f76
	status code: 400, request id: 33862e53-8d09-4387-8d20-bc91d1c9d7cf
Jun  1 16:22:26.236: INFO: Couldn't delete PD "aws://eu-west-1a/vol-01d100fb934477d3b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01d100fb934477d3b is currently attached to i-029b919ec39ba6f76
	status code: 400, request id: 97aff301-05ea-428f-b5e3-ca1db6030212
Jun  1 16:22:31.948: INFO: Couldn't delete PD "aws://eu-west-1a/vol-01d100fb934477d3b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01d100fb934477d3b is currently attached to i-029b919ec39ba6f76
	status code: 400, request id: 93fa8011-349d-4461-99f1-35357e9a08e8
Jun  1 16:22:37.571: INFO: Successfully deleted PD "aws://eu-west-1a/vol-01d100fb934477d3b".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  1 16:22:37.571: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-4503" for this suite.
... skipping 263 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.qpMXPyqcf/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.qpMXPyqcf/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.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 61 lines ...
Jun  1 16:22:22.863: INFO: Pod aws-client still exists
Jun  1 16:22:24.760: INFO: Waiting for pod aws-client to disappear
Jun  1 16:22:24.865: INFO: Pod aws-client still exists
Jun  1 16:22:26.760: INFO: Waiting for pod aws-client to disappear
Jun  1 16:22:26.865: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun  1 16:22:27.522: INFO: Couldn't delete PD "aws://eu-west-1a/vol-043682bffedba92bd", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-043682bffedba92bd is currently attached to i-085543c8bd3777646
	status code: 400, request id: a136b103-db32-464c-9536-de4647e89e20
Jun  1 16:22:33.142: INFO: Couldn't delete PD "aws://eu-west-1a/vol-043682bffedba92bd", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-043682bffedba92bd is currently attached to i-085543c8bd3777646
	status code: 400, request id: 9c123df4-0500-4f0c-8ed4-564041194666
Jun  1 16:22:38.757: INFO: Couldn't delete PD "aws://eu-west-1a/vol-043682bffedba92bd", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-043682bffedba92bd is currently attached to i-085543c8bd3777646
	status code: 400, request id: 63446683-6551-4895-9c84-793a02847c69
Jun  1 16:22:44.431: INFO: Successfully deleted PD "aws://eu-west-1a/vol-043682bffedba92bd".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  1 16:22:44.432: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-6183" for this suite.
... skipping 260 lines ...
Jun  1 16:22:07.134: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  1 16:22:07.502: INFO: Successfully created a new PD: "aws://eu-west-1a/vol-0c714a878ccd66b45".
Jun  1 16:22:07.502: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-bpk6
STEP: Creating a pod to test exec-volume-test
Jun  1 16:22:07.611: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-bpk6" in namespace "volume-2395" to be "Succeeded or Failed"
Jun  1 16:22:07.718: INFO: Pod "exec-volume-test-inlinevolume-bpk6": Phase="Pending", Reason="", readiness=false. Elapsed: 106.878544ms
Jun  1 16:22:09.841: INFO: Pod "exec-volume-test-inlinevolume-bpk6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.229852686s
Jun  1 16:22:11.948: INFO: Pod "exec-volume-test-inlinevolume-bpk6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.337121453s
Jun  1 16:22:14.058: INFO: Pod "exec-volume-test-inlinevolume-bpk6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.44714049s
Jun  1 16:22:16.165: INFO: Pod "exec-volume-test-inlinevolume-bpk6": Phase="Pending", Reason="", readiness=false. Elapsed: 8.553701258s
Jun  1 16:22:18.272: INFO: Pod "exec-volume-test-inlinevolume-bpk6": Phase="Pending", Reason="", readiness=false. Elapsed: 10.660550736s
Jun  1 16:22:20.379: INFO: Pod "exec-volume-test-inlinevolume-bpk6": Phase="Pending", Reason="", readiness=false. Elapsed: 12.767517486s
Jun  1 16:22:22.486: INFO: Pod "exec-volume-test-inlinevolume-bpk6": Phase="Pending", Reason="", readiness=false. Elapsed: 14.875157546s
Jun  1 16:22:24.594: INFO: Pod "exec-volume-test-inlinevolume-bpk6": Phase="Pending", Reason="", readiness=false. Elapsed: 16.982383208s
Jun  1 16:22:26.701: INFO: Pod "exec-volume-test-inlinevolume-bpk6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.089380183s
STEP: Saw pod success
Jun  1 16:22:26.701: INFO: Pod "exec-volume-test-inlinevolume-bpk6" satisfied condition "Succeeded or Failed"
Jun  1 16:22:26.807: INFO: Trying to get logs from node ip-172-20-60-88.eu-west-1.compute.internal pod exec-volume-test-inlinevolume-bpk6 container exec-container-inlinevolume-bpk6: <nil>
STEP: delete the pod
Jun  1 16:22:27.030: INFO: Waiting for pod exec-volume-test-inlinevolume-bpk6 to disappear
Jun  1 16:22:27.136: INFO: Pod exec-volume-test-inlinevolume-bpk6 no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-bpk6
Jun  1 16:22:27.136: INFO: Deleting pod "exec-volume-test-inlinevolume-bpk6" in namespace "volume-2395"
Jun  1 16:22:27.446: INFO: Couldn't delete PD "aws://eu-west-1a/vol-0c714a878ccd66b45", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c714a878ccd66b45 is currently attached to i-01c79fe7421f52304
	status code: 400, request id: 1d1df950-56f6-4145-85d8-4e38b57b552d
Jun  1 16:22:33.037: INFO: Couldn't delete PD "aws://eu-west-1a/vol-0c714a878ccd66b45", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c714a878ccd66b45 is currently attached to i-01c79fe7421f52304
	status code: 400, request id: 2fa7bf43-82fe-46af-ab2a-d45b360bd728
Jun  1 16:22:38.678: INFO: Couldn't delete PD "aws://eu-west-1a/vol-0c714a878ccd66b45", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c714a878ccd66b45 is currently attached to i-01c79fe7421f52304
	status code: 400, request id: f902f147-34dd-4cde-a2f5-77293fdfd7f3
Jun  1 16:22:44.325: INFO: Couldn't delete PD "aws://eu-west-1a/vol-0c714a878ccd66b45", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c714a878ccd66b45 is currently attached to i-01c79fe7421f52304
	status code: 400, request id: d6b86af1-fcd9-438b-9e6f-d75f6a9eacf5
Jun  1 16:22:49.938: INFO: Successfully deleted PD "aws://eu-west-1a/vol-0c714a878ccd66b45".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  1 16:22:49.938: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-2395" for this suite.
... skipping 46 lines ...
Jun  1 16:22:50.760: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 169 lines ...
Jun  1 16:22:28.796: INFO: Creating resource for dynamic PV
Jun  1 16:22:28.796: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-5623-e2e-sc58hw4
STEP: creating a claim
STEP: Expanding non-expandable pvc
Jun  1 16:22:29.114: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun  1 16:22:29.326: INFO: Error updating pvc ebs.csi.aws.comvdvts: PersistentVolumeClaim "ebs.csi.aws.comvdvts" 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-5623-e2e-sc58hw4",
  	... // 2 identical fields
  }

Jun  1 16:22:31.546: INFO: Error updating pvc ebs.csi.aws.comvdvts: PersistentVolumeClaim "ebs.csi.aws.comvdvts" 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-5623-e2e-sc58hw4",
  	... // 2 identical fields
  }

Jun  1 16:22:33.549: INFO: Error updating pvc ebs.csi.aws.comvdvts: PersistentVolumeClaim "ebs.csi.aws.comvdvts" 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-5623-e2e-sc58hw4",
  	... // 2 identical fields
  }

Jun  1 16:22:35.537: INFO: Error updating pvc ebs.csi.aws.comvdvts: PersistentVolumeClaim "ebs.csi.aws.comvdvts" 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-5623-e2e-sc58hw4",
  	... // 2 identical fields
  }

Jun  1 16:22:37.539: INFO: Error updating pvc ebs.csi.aws.comvdvts: PersistentVolumeClaim "ebs.csi.aws.comvdvts" 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-5623-e2e-sc58hw4",
  	... // 2 identical fields
  }

Jun  1 16:22:39.538: INFO: Error updating pvc ebs.csi.aws.comvdvts: PersistentVolumeClaim "ebs.csi.aws.comvdvts" 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-5623-e2e-sc58hw4",
  	... // 2 identical fields
  }

Jun  1 16:22:41.539: INFO: Error updating pvc ebs.csi.aws.comvdvts: PersistentVolumeClaim "ebs.csi.aws.comvdvts" 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-5623-e2e-sc58hw4",
  	... // 2 identical fields
  }

Jun  1 16:22:43.541: INFO: Error updating pvc ebs.csi.aws.comvdvts: PersistentVolumeClaim "ebs.csi.aws.comvdvts" 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-5623-e2e-sc58hw4",
  	... // 2 identical fields
  }

Jun  1 16:22:45.537: INFO: Error updating pvc ebs.csi.aws.comvdvts: PersistentVolumeClaim "ebs.csi.aws.comvdvts" 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-5623-e2e-sc58hw4",
  	... // 2 identical fields
  }

Jun  1 16:22:47.541: INFO: Error updating pvc ebs.csi.aws.comvdvts: PersistentVolumeClaim "ebs.csi.aws.comvdvts" 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-5623-e2e-sc58hw4",
  	... // 2 identical fields
  }

Jun  1 16:22:49.541: INFO: Error updating pvc ebs.csi.aws.comvdvts: PersistentVolumeClaim "ebs.csi.aws.comvdvts" 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-5623-e2e-sc58hw4",
  	... // 2 identical fields
  }

Jun  1 16:22:51.540: INFO: Error updating pvc ebs.csi.aws.comvdvts: PersistentVolumeClaim "ebs.csi.aws.comvdvts" 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-5623-e2e-sc58hw4",
  	... // 2 identical fields
  }

Jun  1 16:22:53.537: INFO: Error updating pvc ebs.csi.aws.comvdvts: PersistentVolumeClaim "ebs.csi.aws.comvdvts" 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-5623-e2e-sc58hw4",
  	... // 2 identical fields
  }

Jun  1 16:22:55.540: INFO: Error updating pvc ebs.csi.aws.comvdvts: PersistentVolumeClaim "ebs.csi.aws.comvdvts" 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-5623-e2e-sc58hw4",
  	... // 2 identical fields
  }

Jun  1 16:22:57.538: INFO: Error updating pvc ebs.csi.aws.comvdvts: PersistentVolumeClaim "ebs.csi.aws.comvdvts" 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-5623-e2e-sc58hw4",
  	... // 2 identical fields
  }

Jun  1 16:22:59.538: INFO: Error updating pvc ebs.csi.aws.comvdvts: PersistentVolumeClaim "ebs.csi.aws.comvdvts" 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-5623-e2e-sc58hw4",
  	... // 2 identical fields
  }

Jun  1 16:22:59.749: INFO: Error updating pvc ebs.csi.aws.comvdvts: PersistentVolumeClaim "ebs.csi.aws.comvdvts" 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 266 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.qpMXPyqcf/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.qpMXPyqcf/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.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 48 lines ...
Jun  1 16:22:18.420: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  1 16:22:19.219: INFO: Successfully created a new PD: "aws://eu-west-1a/vol-0cf0b553af68dfd99".
Jun  1 16:22:19.219: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-pvcl
STEP: Creating a pod to test exec-volume-test
Jun  1 16:22:19.327: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-pvcl" in namespace "volume-1844" to be "Succeeded or Failed"
Jun  1 16:22:19.433: INFO: Pod "exec-volume-test-inlinevolume-pvcl": Phase="Pending", Reason="", readiness=false. Elapsed: 105.965182ms
Jun  1 16:22:21.543: INFO: Pod "exec-volume-test-inlinevolume-pvcl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.215725241s
Jun  1 16:22:23.650: INFO: Pod "exec-volume-test-inlinevolume-pvcl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.322784043s
Jun  1 16:22:25.764: INFO: Pod "exec-volume-test-inlinevolume-pvcl": Phase="Pending", Reason="", readiness=false. Elapsed: 6.436029218s
Jun  1 16:22:27.875: INFO: Pod "exec-volume-test-inlinevolume-pvcl": Phase="Pending", Reason="", readiness=false. Elapsed: 8.547185039s
Jun  1 16:22:29.982: INFO: Pod "exec-volume-test-inlinevolume-pvcl": Phase="Pending", Reason="", readiness=false. Elapsed: 10.654566905s
Jun  1 16:22:32.090: INFO: Pod "exec-volume-test-inlinevolume-pvcl": Phase="Pending", Reason="", readiness=false. Elapsed: 12.762294161s
Jun  1 16:22:34.197: INFO: Pod "exec-volume-test-inlinevolume-pvcl": Phase="Pending", Reason="", readiness=false. Elapsed: 14.86976586s
Jun  1 16:22:36.304: INFO: Pod "exec-volume-test-inlinevolume-pvcl": Phase="Running", Reason="", readiness=true. Elapsed: 16.976310813s
Jun  1 16:22:38.410: INFO: Pod "exec-volume-test-inlinevolume-pvcl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.08295285s
STEP: Saw pod success
Jun  1 16:22:38.411: INFO: Pod "exec-volume-test-inlinevolume-pvcl" satisfied condition "Succeeded or Failed"
Jun  1 16:22:38.518: INFO: Trying to get logs from node ip-172-20-57-30.eu-west-1.compute.internal pod exec-volume-test-inlinevolume-pvcl container exec-container-inlinevolume-pvcl: <nil>
STEP: delete the pod
Jun  1 16:22:38.765: INFO: Waiting for pod exec-volume-test-inlinevolume-pvcl to disappear
Jun  1 16:22:38.871: INFO: Pod exec-volume-test-inlinevolume-pvcl no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-pvcl
Jun  1 16:22:38.871: INFO: Deleting pod "exec-volume-test-inlinevolume-pvcl" in namespace "volume-1844"
Jun  1 16:22:39.183: INFO: Couldn't delete PD "aws://eu-west-1a/vol-0cf0b553af68dfd99", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0cf0b553af68dfd99 is currently attached to i-0e6e8cb92e7778059
	status code: 400, request id: 4043adae-89bb-4d34-a062-8e13f6902816
Jun  1 16:22:44.721: INFO: Couldn't delete PD "aws://eu-west-1a/vol-0cf0b553af68dfd99", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0cf0b553af68dfd99 is currently attached to i-0e6e8cb92e7778059
	status code: 400, request id: e815fed1-8c89-422c-9a4c-6d9eeeb663c4
Jun  1 16:22:50.298: INFO: Couldn't delete PD "aws://eu-west-1a/vol-0cf0b553af68dfd99", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0cf0b553af68dfd99 is currently attached to i-0e6e8cb92e7778059
	status code: 400, request id: d6a3a6c1-1514-4501-8654-945a12e61c49
Jun  1 16:22:55.947: INFO: Couldn't delete PD "aws://eu-west-1a/vol-0cf0b553af68dfd99", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0cf0b553af68dfd99 is currently attached to i-0e6e8cb92e7778059
	status code: 400, request id: eb5a7808-30d5-4b67-af83-870620bf9b0f
Jun  1 16:23:01.570: INFO: Successfully deleted PD "aws://eu-west-1a/vol-0cf0b553af68dfd99".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  1 16:23:01.570: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-1844" for this suite.
... skipping 56 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  1 16:21:55.094: 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.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun  1 16:21:55.629: INFO: Creating resource for dynamic PV
Jun  1 16:21:55.629: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5549-e2e-scgxznw
STEP: creating a claim
Jun  1 16:21:55.741: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-wk67
STEP: Checking for subpath error in container status
Jun  1 16:22:20.279: INFO: Deleting pod "pod-subpath-test-dynamicpv-wk67" in namespace "provisioning-5549"
Jun  1 16:22:20.386: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-wk67" to be fully deleted
STEP: Deleting pod
Jun  1 16:22:26.598: INFO: Deleting pod "pod-subpath-test-dynamicpv-wk67" in namespace "provisioning-5549"
STEP: Deleting pvc
Jun  1 16:22:26.915: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comwjrzc"
... skipping 15 lines ...

• [SLOW TEST:68.114 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath file is outside the volume [Slow][LinuxOnly]
    /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  1 16:23:03.210: 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.qpMXPyqcf/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.qpMXPyqcf/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.qpMXPyqcf/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.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 182 lines ...
Jun  1 16:22:56.534: INFO: Waiting for pod aws-client to disappear
Jun  1 16:22:56.642: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun  1 16:22:56.642: INFO: Deleting PersistentVolumeClaim "pvc-vmfvn"
Jun  1 16:22:56.749: INFO: Deleting PersistentVolume "aws-hwfhq"
Jun  1 16:22:57.492: INFO: Couldn't delete PD "aws://eu-west-1a/vol-0bdeb72f62ffe43be", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0bdeb72f62ffe43be is currently attached to i-085543c8bd3777646
	status code: 400, request id: c9a35a8b-6cfc-48ed-8df9-f17082c3eddc
Jun  1 16:23:03.084: INFO: Couldn't delete PD "aws://eu-west-1a/vol-0bdeb72f62ffe43be", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0bdeb72f62ffe43be is currently attached to i-085543c8bd3777646
	status code: 400, request id: 31910060-0960-4ac3-bfd2-b86d383e450d
Jun  1 16:23:08.749: INFO: Couldn't delete PD "aws://eu-west-1a/vol-0bdeb72f62ffe43be", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0bdeb72f62ffe43be is currently attached to i-085543c8bd3777646
	status code: 400, request id: bf12c526-bb3f-4e3c-a06a-4b49f455f45b
Jun  1 16:23:14.390: INFO: Successfully deleted PD "aws://eu-west-1a/vol-0bdeb72f62ffe43be".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumes
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  1 16:23:14.391: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-587" for this suite.
... skipping 116 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  1 16:22:39.317: 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.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun  1 16:22:39.851: INFO: Creating resource for dynamic PV
Jun  1 16:22:39.852: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4425-e2e-scrwqpr
STEP: creating a claim
Jun  1 16:22:39.961: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-4n5q
STEP: Checking for subpath error in container status
Jun  1 16:22:54.500: INFO: Deleting pod "pod-subpath-test-dynamicpv-4n5q" in namespace "provisioning-4425"
Jun  1 16:22:54.608: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-4n5q" to be fully deleted
STEP: Deleting pod
Jun  1 16:23:06.824: INFO: Deleting pod "pod-subpath-test-dynamicpv-4n5q" in namespace "provisioning-4425"
STEP: Deleting pvc
Jun  1 16:23:07.149: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comr4wxl"
... skipping 10 lines ...

• [SLOW TEST:38.589 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath directory is outside the volume [Slow][LinuxOnly]
    /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  1 16:23:17.908: INFO: Driver "ebs.csi.aws.com" does not support volume type "PreprovisionedPV" - skipping
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
... skipping 319 lines ...
Jun  1 16:22:28.944: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2313-e2e-sctr946
STEP: creating a claim
Jun  1 16:22:29.050: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-2zvg
STEP: Creating a pod to test subpath
Jun  1 16:22:29.367: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-2zvg" in namespace "provisioning-2313" to be "Succeeded or Failed"
Jun  1 16:22:29.472: INFO: Pod "pod-subpath-test-dynamicpv-2zvg": Phase="Pending", Reason="", readiness=false. Elapsed: 104.612705ms
Jun  1 16:22:31.577: INFO: Pod "pod-subpath-test-dynamicpv-2zvg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.210030545s
Jun  1 16:22:33.683: INFO: Pod "pod-subpath-test-dynamicpv-2zvg": Phase="Pending", Reason="", readiness=false. Elapsed: 4.315932491s
Jun  1 16:22:35.802: INFO: Pod "pod-subpath-test-dynamicpv-2zvg": Phase="Pending", Reason="", readiness=false. Elapsed: 6.434853712s
Jun  1 16:22:37.908: INFO: Pod "pod-subpath-test-dynamicpv-2zvg": Phase="Pending", Reason="", readiness=false. Elapsed: 8.541386377s
Jun  1 16:22:40.015: INFO: Pod "pod-subpath-test-dynamicpv-2zvg": Phase="Pending", Reason="", readiness=false. Elapsed: 10.648093057s
... skipping 2 lines ...
Jun  1 16:22:46.334: INFO: Pod "pod-subpath-test-dynamicpv-2zvg": Phase="Pending", Reason="", readiness=false. Elapsed: 16.967200265s
Jun  1 16:22:48.439: INFO: Pod "pod-subpath-test-dynamicpv-2zvg": Phase="Pending", Reason="", readiness=false. Elapsed: 19.072055655s
Jun  1 16:22:50.546: INFO: Pod "pod-subpath-test-dynamicpv-2zvg": Phase="Pending", Reason="", readiness=false. Elapsed: 21.178624339s
Jun  1 16:22:52.651: INFO: Pod "pod-subpath-test-dynamicpv-2zvg": Phase="Pending", Reason="", readiness=false. Elapsed: 23.283774486s
Jun  1 16:22:54.761: INFO: Pod "pod-subpath-test-dynamicpv-2zvg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 25.394501415s
STEP: Saw pod success
Jun  1 16:22:54.762: INFO: Pod "pod-subpath-test-dynamicpv-2zvg" satisfied condition "Succeeded or Failed"
Jun  1 16:22:54.883: INFO: Trying to get logs from node ip-172-20-46-125.eu-west-1.compute.internal pod pod-subpath-test-dynamicpv-2zvg container test-container-volume-dynamicpv-2zvg: <nil>
STEP: delete the pod
Jun  1 16:22:55.107: INFO: Waiting for pod pod-subpath-test-dynamicpv-2zvg to disappear
Jun  1 16:22:55.214: INFO: Pod pod-subpath-test-dynamicpv-2zvg no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-2zvg
Jun  1 16:22:55.214: INFO: Deleting pod "pod-subpath-test-dynamicpv-2zvg" in namespace "provisioning-2313"
... skipping 329 lines ...
Jun  1 16:22:57.130: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2894-e2e-sc4p8bv
STEP: creating a claim
Jun  1 16:22:57.239: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-zljj
STEP: Creating a pod to test subpath
Jun  1 16:22:57.567: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-zljj" in namespace "provisioning-2894" to be "Succeeded or Failed"
Jun  1 16:22:57.678: INFO: Pod "pod-subpath-test-dynamicpv-zljj": Phase="Pending", Reason="", readiness=false. Elapsed: 110.63851ms
Jun  1 16:22:59.785: INFO: Pod "pod-subpath-test-dynamicpv-zljj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.217581405s
Jun  1 16:23:01.892: INFO: Pod "pod-subpath-test-dynamicpv-zljj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.324993525s
Jun  1 16:23:04.007: INFO: Pod "pod-subpath-test-dynamicpv-zljj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.439848122s
Jun  1 16:23:06.115: INFO: Pod "pod-subpath-test-dynamicpv-zljj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.547906675s
Jun  1 16:23:08.228: INFO: Pod "pod-subpath-test-dynamicpv-zljj": Phase="Pending", Reason="", readiness=false. Elapsed: 10.660544903s
... skipping 2 lines ...
Jun  1 16:23:14.554: INFO: Pod "pod-subpath-test-dynamicpv-zljj": Phase="Pending", Reason="", readiness=false. Elapsed: 16.987327141s
Jun  1 16:23:16.662: INFO: Pod "pod-subpath-test-dynamicpv-zljj": Phase="Pending", Reason="", readiness=false. Elapsed: 19.094848032s
Jun  1 16:23:18.769: INFO: Pod "pod-subpath-test-dynamicpv-zljj": Phase="Pending", Reason="", readiness=false. Elapsed: 21.202329081s
Jun  1 16:23:20.877: INFO: Pod "pod-subpath-test-dynamicpv-zljj": Phase="Pending", Reason="", readiness=false. Elapsed: 23.309647316s
Jun  1 16:23:22.986: INFO: Pod "pod-subpath-test-dynamicpv-zljj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 25.41924336s
STEP: Saw pod success
Jun  1 16:23:22.986: INFO: Pod "pod-subpath-test-dynamicpv-zljj" satisfied condition "Succeeded or Failed"
Jun  1 16:23:23.093: INFO: Trying to get logs from node ip-172-20-46-125.eu-west-1.compute.internal pod pod-subpath-test-dynamicpv-zljj container test-container-subpath-dynamicpv-zljj: <nil>
STEP: delete the pod
Jun  1 16:23:23.317: INFO: Waiting for pod pod-subpath-test-dynamicpv-zljj to disappear
Jun  1 16:23:23.423: INFO: Pod pod-subpath-test-dynamicpv-zljj no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-zljj
Jun  1 16:23:23.423: INFO: Deleting pod "pod-subpath-test-dynamicpv-zljj" in namespace "provisioning-2894"
... skipping 35 lines ...
Jun  1 16:22:24.545: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-478-e2e-scc4n76
STEP: creating a claim
Jun  1 16:22:24.658: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-k9f9
STEP: Creating a pod to test exec-volume-test
Jun  1 16:22:24.975: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-k9f9" in namespace "volume-478" to be "Succeeded or Failed"
Jun  1 16:22:25.080: INFO: Pod "exec-volume-test-dynamicpv-k9f9": Phase="Pending", Reason="", readiness=false. Elapsed: 104.904862ms
Jun  1 16:22:27.187: INFO: Pod "exec-volume-test-dynamicpv-k9f9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.21113275s
Jun  1 16:22:29.292: INFO: Pod "exec-volume-test-dynamicpv-k9f9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.316021323s
Jun  1 16:22:31.397: INFO: Pod "exec-volume-test-dynamicpv-k9f9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.421819202s
Jun  1 16:22:33.505: INFO: Pod "exec-volume-test-dynamicpv-k9f9": Phase="Pending", Reason="", readiness=false. Elapsed: 8.529725527s
Jun  1 16:22:35.611: INFO: Pod "exec-volume-test-dynamicpv-k9f9": Phase="Pending", Reason="", readiness=false. Elapsed: 10.635301673s
... skipping 8 lines ...
Jun  1 16:22:54.569: INFO: Pod "exec-volume-test-dynamicpv-k9f9": Phase="Pending", Reason="", readiness=false. Elapsed: 29.593130737s
Jun  1 16:22:56.675: INFO: Pod "exec-volume-test-dynamicpv-k9f9": Phase="Pending", Reason="", readiness=false. Elapsed: 31.699164254s
Jun  1 16:22:58.780: INFO: Pod "exec-volume-test-dynamicpv-k9f9": Phase="Pending", Reason="", readiness=false. Elapsed: 33.804995302s
Jun  1 16:23:00.885: INFO: Pod "exec-volume-test-dynamicpv-k9f9": Phase="Pending", Reason="", readiness=false. Elapsed: 35.909839319s
Jun  1 16:23:02.991: INFO: Pod "exec-volume-test-dynamicpv-k9f9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 38.015368973s
STEP: Saw pod success
Jun  1 16:23:02.991: INFO: Pod "exec-volume-test-dynamicpv-k9f9" satisfied condition "Succeeded or Failed"
Jun  1 16:23:03.106: INFO: Trying to get logs from node ip-172-20-57-30.eu-west-1.compute.internal pod exec-volume-test-dynamicpv-k9f9 container exec-container-dynamicpv-k9f9: <nil>
STEP: delete the pod
Jun  1 16:23:03.332: INFO: Waiting for pod exec-volume-test-dynamicpv-k9f9 to disappear
Jun  1 16:23:03.436: INFO: Pod exec-volume-test-dynamicpv-k9f9 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-k9f9
Jun  1 16:23:03.436: INFO: Deleting pod "exec-volume-test-dynamicpv-k9f9" in namespace "volume-478"
... skipping 32 lines ...

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

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

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

    /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 217 lines ...
Jun  1 16:23:12.377: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-89442d2sd
STEP: creating a claim
Jun  1 16:23:12.483: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-v52k
STEP: Creating a pod to test exec-volume-test
Jun  1 16:23:12.805: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-v52k" in namespace "volume-8944" to be "Succeeded or Failed"
Jun  1 16:23:12.911: INFO: Pod "exec-volume-test-dynamicpv-v52k": Phase="Pending", Reason="", readiness=false. Elapsed: 106.441928ms
Jun  1 16:23:15.018: INFO: Pod "exec-volume-test-dynamicpv-v52k": Phase="Pending", Reason="", readiness=false. Elapsed: 2.212748079s
Jun  1 16:23:17.123: INFO: Pod "exec-volume-test-dynamicpv-v52k": Phase="Pending", Reason="", readiness=false. Elapsed: 4.318513155s
Jun  1 16:23:19.230: INFO: Pod "exec-volume-test-dynamicpv-v52k": Phase="Pending", Reason="", readiness=false. Elapsed: 6.425467912s
Jun  1 16:23:21.336: INFO: Pod "exec-volume-test-dynamicpv-v52k": Phase="Pending", Reason="", readiness=false. Elapsed: 8.531506917s
Jun  1 16:23:23.442: INFO: Pod "exec-volume-test-dynamicpv-v52k": Phase="Pending", Reason="", readiness=false. Elapsed: 10.637318561s
Jun  1 16:23:25.549: INFO: Pod "exec-volume-test-dynamicpv-v52k": Phase="Running", Reason="", readiness=true. Elapsed: 12.744422577s
Jun  1 16:23:27.656: INFO: Pod "exec-volume-test-dynamicpv-v52k": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.851042834s
STEP: Saw pod success
Jun  1 16:23:27.656: INFO: Pod "exec-volume-test-dynamicpv-v52k" satisfied condition "Succeeded or Failed"
Jun  1 16:23:27.762: INFO: Trying to get logs from node ip-172-20-57-211.eu-west-1.compute.internal pod exec-volume-test-dynamicpv-v52k container exec-container-dynamicpv-v52k: <nil>
STEP: delete the pod
Jun  1 16:23:27.981: INFO: Waiting for pod exec-volume-test-dynamicpv-v52k to disappear
Jun  1 16:23:28.087: INFO: Pod exec-volume-test-dynamicpv-v52k no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-v52k
Jun  1 16:23:28.087: INFO: Deleting pod "exec-volume-test-dynamicpv-v52k" in namespace "volume-8944"
... skipping 185 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  1 16:23:25.549: 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.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  1 16:23:26.078: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  1 16:23:26.078: INFO: Creating resource for dynamic PV
Jun  1 16:23:26.078: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-956446cn5
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  1 16:23:32.821: INFO: Deleting pod "pod-bc4c22f9-a649-4300-9bdd-93be0dc7cb5a" in namespace "volumemode-9564"
Jun  1 16:23:32.927: INFO: Wait up to 5m0s for pod "pod-bc4c22f9-a649-4300-9bdd-93be0dc7cb5a" to be fully deleted
STEP: Deleting pvc
Jun  1 16:23:47.347: INFO: Deleting PersistentVolumeClaim "awsqft7x"
Jun  1 16:23:47.457: INFO: Waiting up to 5m0s for PersistentVolume pvc-caa85249-b009-45bd-bad3-9e8b71ffeb21 to get deleted
Jun  1 16:23:47.562: INFO: PersistentVolume pvc-caa85249-b009-45bd-bad3-9e8b71ffeb21 found and phase=Released (104.786897ms)
... skipping 9 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.qpMXPyqcf/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.qpMXPyqcf/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
    /tmp/kops.qpMXPyqcf/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.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 7 lines ...
Jun  1 16:23:01.551: INFO: Creating resource for dynamic PV
Jun  1 16:23:01.551: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3226lz2c5
STEP: creating a claim
Jun  1 16:23:01.658: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-3226
Jun  1 16:23:01.978: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-3226" in namespace "provisioning-3226" to be "Succeeded or Failed"
Jun  1 16:23:02.084: INFO: Pod "volume-prep-provisioning-3226": Phase="Pending", Reason="", readiness=false. Elapsed: 105.34901ms
Jun  1 16:23:04.190: INFO: Pod "volume-prep-provisioning-3226": Phase="Pending", Reason="", readiness=false. Elapsed: 2.211881338s
Jun  1 16:23:06.297: INFO: Pod "volume-prep-provisioning-3226": Phase="Pending", Reason="", readiness=false. Elapsed: 4.318654164s
Jun  1 16:23:08.403: INFO: Pod "volume-prep-provisioning-3226": Phase="Pending", Reason="", readiness=false. Elapsed: 6.424551757s
Jun  1 16:23:10.509: INFO: Pod "volume-prep-provisioning-3226": Phase="Pending", Reason="", readiness=false. Elapsed: 8.530785214s
Jun  1 16:23:12.615: INFO: Pod "volume-prep-provisioning-3226": Phase="Pending", Reason="", readiness=false. Elapsed: 10.636401532s
Jun  1 16:23:14.724: INFO: Pod "volume-prep-provisioning-3226": Phase="Pending", Reason="", readiness=false. Elapsed: 12.745835827s
Jun  1 16:23:16.834: INFO: Pod "volume-prep-provisioning-3226": Phase="Pending", Reason="", readiness=false. Elapsed: 14.855246598s
Jun  1 16:23:18.940: INFO: Pod "volume-prep-provisioning-3226": Phase="Pending", Reason="", readiness=false. Elapsed: 16.961401039s
Jun  1 16:23:21.046: INFO: Pod "volume-prep-provisioning-3226": Phase="Pending", Reason="", readiness=false. Elapsed: 19.067279011s
Jun  1 16:23:23.152: INFO: Pod "volume-prep-provisioning-3226": Phase="Pending", Reason="", readiness=false. Elapsed: 21.174079742s
Jun  1 16:23:25.260: INFO: Pod "volume-prep-provisioning-3226": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.28192369s
STEP: Saw pod success
Jun  1 16:23:25.260: INFO: Pod "volume-prep-provisioning-3226" satisfied condition "Succeeded or Failed"
Jun  1 16:23:25.260: INFO: Deleting pod "volume-prep-provisioning-3226" in namespace "provisioning-3226"
Jun  1 16:23:25.372: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-3226" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-92lk
STEP: Checking for subpath error in container status
Jun  1 16:23:27.794: INFO: Deleting pod "pod-subpath-test-dynamicpv-92lk" in namespace "provisioning-3226"
Jun  1 16:23:27.906: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-92lk" to be fully deleted
STEP: Deleting pod
Jun  1 16:23:28.010: INFO: Deleting pod "pod-subpath-test-dynamicpv-92lk" in namespace "provisioning-3226"
STEP: Deleting pvc
Jun  1 16:23:28.325: INFO: Deleting PersistentVolumeClaim "awsspq9n"
... skipping 32 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.qpMXPyqcf/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.qpMXPyqcf/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.qpMXPyqcf/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.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 517 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  1 16:23:39.589: 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.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun  1 16:23:40.118: INFO: Creating resource for dynamic PV
Jun  1 16:23:40.118: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4078-e2e-sc2lpkv
STEP: creating a claim
Jun  1 16:23:40.270: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-b4kg
STEP: Checking for subpath error in container status
Jun  1 16:23:54.810: INFO: Deleting pod "pod-subpath-test-dynamicpv-b4kg" in namespace "provisioning-4078"
Jun  1 16:23:54.920: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-b4kg" to be fully deleted
STEP: Deleting pod
Jun  1 16:24:07.131: INFO: Deleting pod "pod-subpath-test-dynamicpv-b4kg" in namespace "provisioning-4078"
STEP: Deleting pvc
Jun  1 16:24:07.453: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com6rbxt"
... skipping 11 lines ...

• [SLOW TEST:43.732 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.qpMXPyqcf/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.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 8 lines ...
Jun  1 16:23:03.751: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4110zsxgc
STEP: creating a claim
Jun  1 16:23:03.860: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-w7x9
STEP: Creating a pod to test subpath
Jun  1 16:23:04.187: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-w7x9" in namespace "provisioning-4110" to be "Succeeded or Failed"
Jun  1 16:23:04.293: INFO: Pod "pod-subpath-test-dynamicpv-w7x9": Phase="Pending", Reason="", readiness=false. Elapsed: 105.872989ms
Jun  1 16:23:06.410: INFO: Pod "pod-subpath-test-dynamicpv-w7x9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.223340294s
Jun  1 16:23:08.520: INFO: Pod "pod-subpath-test-dynamicpv-w7x9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.332796195s
Jun  1 16:23:10.627: INFO: Pod "pod-subpath-test-dynamicpv-w7x9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.440342151s
Jun  1 16:23:12.733: INFO: Pod "pod-subpath-test-dynamicpv-w7x9": Phase="Pending", Reason="", readiness=false. Elapsed: 8.54653304s
Jun  1 16:23:14.840: INFO: Pod "pod-subpath-test-dynamicpv-w7x9": Phase="Pending", Reason="", readiness=false. Elapsed: 10.653127185s
... skipping 10 lines ...
Jun  1 16:23:38.027: INFO: Pod "pod-subpath-test-dynamicpv-w7x9": Phase="Pending", Reason="", readiness=false. Elapsed: 33.840214842s
Jun  1 16:23:40.134: INFO: Pod "pod-subpath-test-dynamicpv-w7x9": Phase="Pending", Reason="", readiness=false. Elapsed: 35.946631477s
Jun  1 16:23:42.240: INFO: Pod "pod-subpath-test-dynamicpv-w7x9": Phase="Pending", Reason="", readiness=false. Elapsed: 38.053042538s
Jun  1 16:23:44.346: INFO: Pod "pod-subpath-test-dynamicpv-w7x9": Phase="Pending", Reason="", readiness=false. Elapsed: 40.159159556s
Jun  1 16:23:46.452: INFO: Pod "pod-subpath-test-dynamicpv-w7x9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 42.265460139s
STEP: Saw pod success
Jun  1 16:23:46.452: INFO: Pod "pod-subpath-test-dynamicpv-w7x9" satisfied condition "Succeeded or Failed"
Jun  1 16:23:46.561: INFO: Trying to get logs from node ip-172-20-57-30.eu-west-1.compute.internal pod pod-subpath-test-dynamicpv-w7x9 container test-container-subpath-dynamicpv-w7x9: <nil>
STEP: delete the pod
Jun  1 16:23:46.788: INFO: Waiting for pod pod-subpath-test-dynamicpv-w7x9 to disappear
Jun  1 16:23:46.894: INFO: Pod pod-subpath-test-dynamicpv-w7x9 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-w7x9
Jun  1 16:23:46.894: INFO: Deleting pod "pod-subpath-test-dynamicpv-w7x9" in namespace "provisioning-4110"
... skipping 41 lines ...
Jun  1 16:23:53.521: INFO: Creating resource for dynamic PV
Jun  1 16:23:53.521: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-2524fkdr5
STEP: creating a claim
STEP: Expanding non-expandable pvc
Jun  1 16:23:53.838: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun  1 16:23:54.064: INFO: Error updating pvc awsrz8xh: PersistentVolumeClaim "awsrz8xh" 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-2524fkdr5",
  	... // 2 identical fields
  }

Jun  1 16:23:56.278: INFO: Error updating pvc awsrz8xh: PersistentVolumeClaim "awsrz8xh" 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-2524fkdr5",
  	... // 2 identical fields
  }

Jun  1 16:23:58.277: INFO: Error updating pvc awsrz8xh: PersistentVolumeClaim "awsrz8xh" 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-2524fkdr5",
  	... // 2 identical fields
  }

Jun  1 16:24:00.282: INFO: Error updating pvc awsrz8xh: PersistentVolumeClaim "awsrz8xh" 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-2524fkdr5",
  	... // 2 identical fields
  }

Jun  1 16:24:02.278: INFO: Error updating pvc awsrz8xh: PersistentVolumeClaim "awsrz8xh" 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-2524fkdr5",
  	... // 2 identical fields
  }

Jun  1 16:24:04.278: INFO: Error updating pvc awsrz8xh: PersistentVolumeClaim "awsrz8xh" 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-2524fkdr5",
  	... // 2 identical fields
  }

Jun  1 16:24:06.275: INFO: Error updating pvc awsrz8xh: PersistentVolumeClaim "awsrz8xh" 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-2524fkdr5",
  	... // 2 identical fields
  }

Jun  1 16:24:08.275: INFO: Error updating pvc awsrz8xh: PersistentVolumeClaim "awsrz8xh" 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-2524fkdr5",
  	... // 2 identical fields
  }

Jun  1 16:24:10.276: INFO: Error updating pvc awsrz8xh: PersistentVolumeClaim "awsrz8xh" 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-2524fkdr5",
  	... // 2 identical fields
  }

Jun  1 16:24:12.279: INFO: Error updating pvc awsrz8xh: PersistentVolumeClaim "awsrz8xh" 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-2524fkdr5",
  	... // 2 identical fields
  }

Jun  1 16:24:14.275: INFO: Error updating pvc awsrz8xh: PersistentVolumeClaim "awsrz8xh" 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-2524fkdr5",
  	... // 2 identical fields
  }

Jun  1 16:24:16.275: INFO: Error updating pvc awsrz8xh: PersistentVolumeClaim "awsrz8xh" 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-2524fkdr5",
  	... // 2 identical fields
  }

Jun  1 16:24:18.277: INFO: Error updating pvc awsrz8xh: PersistentVolumeClaim "awsrz8xh" 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-2524fkdr5",
  	... // 2 identical fields
  }

Jun  1 16:24:20.275: INFO: Error updating pvc awsrz8xh: PersistentVolumeClaim "awsrz8xh" 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-2524fkdr5",
  	... // 2 identical fields
  }

Jun  1 16:24:22.276: INFO: Error updating pvc awsrz8xh: PersistentVolumeClaim "awsrz8xh" 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-2524fkdr5",
  	... // 2 identical fields
  }

Jun  1 16:24:24.277: INFO: Error updating pvc awsrz8xh: PersistentVolumeClaim "awsrz8xh" 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-2524fkdr5",
  	... // 2 identical fields
  }

Jun  1 16:24:24.487: INFO: Error updating pvc awsrz8xh: PersistentVolumeClaim "awsrz8xh" 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 117 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  1 16:23:43.309: 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.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun  1 16:23:43.844: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  1 16:23:43.844: INFO: Creating resource for dynamic PV
Jun  1 16:23:43.844: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4904xzd4r
STEP: creating a claim
Jun  1 16:23:43.957: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-8zcb
STEP: Checking for subpath error in container status
Jun  1 16:24:00.498: INFO: Deleting pod "pod-subpath-test-dynamicpv-8zcb" in namespace "provisioning-4904"
Jun  1 16:24:00.605: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-8zcb" to be fully deleted
STEP: Deleting pod
Jun  1 16:24:06.816: INFO: Deleting pod "pod-subpath-test-dynamicpv-8zcb" in namespace "provisioning-4904"
STEP: Deleting pvc
Jun  1 16:24:07.132: INFO: Deleting PersistentVolumeClaim "awsbjzpv"
... skipping 14 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.qpMXPyqcf/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.qpMXPyqcf/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.qpMXPyqcf/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.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (ntfs)][Feature:Windows] volumes
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  1 16:24:28.091: INFO: Distro debian doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Pre-provisioned PV (ntfs)][Feature:Windows] volumes
... skipping 115 lines ...
Jun  1 16:21:43.505: INFO: Creating resource for dynamic PV
Jun  1 16:21:43.505: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-8533-e2e-scbpjzs
STEP: creating a claim
Jun  1 16:21:43.612: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun  1 16:21:43.936: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-nvcqp" in namespace "snapshotting-8533" to be "Succeeded or Failed"
Jun  1 16:21:44.043: INFO: Pod "pvc-snapshottable-tester-nvcqp": Phase="Pending", Reason="", readiness=false. Elapsed: 106.86192ms
Jun  1 16:21:46.150: INFO: Pod "pvc-snapshottable-tester-nvcqp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.213498337s
Jun  1 16:21:48.257: INFO: Pod "pvc-snapshottable-tester-nvcqp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.320442626s
Jun  1 16:21:50.364: INFO: Pod "pvc-snapshottable-tester-nvcqp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.428068184s
Jun  1 16:21:52.471: INFO: Pod "pvc-snapshottable-tester-nvcqp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.534902663s
Jun  1 16:21:54.579: INFO: Pod "pvc-snapshottable-tester-nvcqp": Phase="Pending", Reason="", readiness=false. Elapsed: 10.642301302s
... skipping 8 lines ...
Jun  1 16:22:13.544: INFO: Pod "pvc-snapshottable-tester-nvcqp": Phase="Pending", Reason="", readiness=false. Elapsed: 29.608202638s
Jun  1 16:22:15.651: INFO: Pod "pvc-snapshottable-tester-nvcqp": Phase="Pending", Reason="", readiness=false. Elapsed: 31.714928702s
Jun  1 16:22:17.758: INFO: Pod "pvc-snapshottable-tester-nvcqp": Phase="Pending", Reason="", readiness=false. Elapsed: 33.821901249s
Jun  1 16:22:19.878: INFO: Pod "pvc-snapshottable-tester-nvcqp": Phase="Pending", Reason="", readiness=false. Elapsed: 35.941738487s
Jun  1 16:22:21.985: INFO: Pod "pvc-snapshottable-tester-nvcqp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 38.048558462s
STEP: Saw pod success
Jun  1 16:22:21.985: INFO: Pod "pvc-snapshottable-tester-nvcqp" satisfied condition "Succeeded or Failed"
Jun  1 16:22:22.202: INFO: Pod pvc-snapshottable-tester-nvcqp has the following logs: 
Jun  1 16:22:22.202: INFO: Deleting pod "pvc-snapshottable-tester-nvcqp" in namespace "snapshotting-8533"
Jun  1 16:22:22.319: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-nvcqp" to be fully deleted
Jun  1 16:22:22.425: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comzlwfv] to have phase Bound
Jun  1 16:22:22.532: INFO: PersistentVolumeClaim ebs.csi.aws.comzlwfv found and phase=Bound (106.278971ms)
STEP: [init] checking the claim
... skipping 49 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.qpMXPyqcf/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  1 16:23:09.124: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-jccsd" in namespace "snapshotting-8533" to be "Succeeded or Failed"
Jun  1 16:23:09.235: INFO: Pod "pvc-snapshottable-data-tester-jccsd": Phase="Pending", Reason="", readiness=false. Elapsed: 110.486664ms
Jun  1 16:23:11.342: INFO: Pod "pvc-snapshottable-data-tester-jccsd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.217948168s
Jun  1 16:23:13.449: INFO: Pod "pvc-snapshottable-data-tester-jccsd": Phase="Pending", Reason="", readiness=false. Elapsed: 4.324494706s
Jun  1 16:23:15.556: INFO: Pod "pvc-snapshottable-data-tester-jccsd": Phase="Pending", Reason="", readiness=false. Elapsed: 6.431856072s
Jun  1 16:23:17.663: INFO: Pod "pvc-snapshottable-data-tester-jccsd": Phase="Pending", Reason="", readiness=false. Elapsed: 8.538562134s
Jun  1 16:23:19.772: INFO: Pod "pvc-snapshottable-data-tester-jccsd": Phase="Pending", Reason="", readiness=false. Elapsed: 10.647246339s
Jun  1 16:23:21.880: INFO: Pod "pvc-snapshottable-data-tester-jccsd": Phase="Pending", Reason="", readiness=false. Elapsed: 12.755210475s
Jun  1 16:23:24.035: INFO: Pod "pvc-snapshottable-data-tester-jccsd": Phase="Pending", Reason="", readiness=false. Elapsed: 14.91025744s
Jun  1 16:23:26.141: INFO: Pod "pvc-snapshottable-data-tester-jccsd": Phase="Pending", Reason="", readiness=false. Elapsed: 17.01679385s
Jun  1 16:23:28.248: INFO: Pod "pvc-snapshottable-data-tester-jccsd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.123551824s
STEP: Saw pod success
Jun  1 16:23:28.248: INFO: Pod "pvc-snapshottable-data-tester-jccsd" satisfied condition "Succeeded or Failed"
Jun  1 16:23:28.462: INFO: Pod pvc-snapshottable-data-tester-jccsd has the following logs: 
Jun  1 16:23:28.462: INFO: Deleting pod "pvc-snapshottable-data-tester-jccsd" in namespace "snapshotting-8533"
Jun  1 16:23:28.574: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-jccsd" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun  1 16:23:43.109: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-8533 exec restored-pvc-tester-84kgw --namespace=snapshotting-8533 -- cat /mnt/test/data'
... skipping 255 lines ...
    /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:108
      
      /tmp/kops.qpMXPyqcf/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.qpMXPyqcf/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-8533 exec restored-pvc-tester-84kgw --namespace=snapshotting-8533 -- 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-8533 exec restored-pvc-tester-84kgw --namespace=snapshotting-8533 -- 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.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:602
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
... skipping 10 lines ...
Jun  1 16:23:32.454: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5496-e2e-sclcqmp
STEP: creating a claim
Jun  1 16:23:32.561: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-vwdw
STEP: Creating a pod to test subpath
Jun  1 16:23:32.883: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-vwdw" in namespace "provisioning-5496" to be "Succeeded or Failed"
Jun  1 16:23:32.988: INFO: Pod "pod-subpath-test-dynamicpv-vwdw": Phase="Pending", Reason="", readiness=false. Elapsed: 104.482152ms
Jun  1 16:23:35.096: INFO: Pod "pod-subpath-test-dynamicpv-vwdw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.212982373s
Jun  1 16:23:37.206: INFO: Pod "pod-subpath-test-dynamicpv-vwdw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.322961298s
Jun  1 16:23:39.311: INFO: Pod "pod-subpath-test-dynamicpv-vwdw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.427815973s
Jun  1 16:23:41.417: INFO: Pod "pod-subpath-test-dynamicpv-vwdw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.533824832s
Jun  1 16:23:43.523: INFO: Pod "pod-subpath-test-dynamicpv-vwdw": Phase="Pending", Reason="", readiness=false. Elapsed: 10.63940383s
Jun  1 16:23:45.630: INFO: Pod "pod-subpath-test-dynamicpv-vwdw": Phase="Pending", Reason="", readiness=false. Elapsed: 12.746581052s
Jun  1 16:23:47.736: INFO: Pod "pod-subpath-test-dynamicpv-vwdw": Phase="Pending", Reason="", readiness=false. Elapsed: 14.852423531s
Jun  1 16:23:49.842: INFO: Pod "pod-subpath-test-dynamicpv-vwdw": Phase="Pending", Reason="", readiness=false. Elapsed: 16.95853544s
Jun  1 16:23:51.948: INFO: Pod "pod-subpath-test-dynamicpv-vwdw": Phase="Pending", Reason="", readiness=false. Elapsed: 19.064687853s
Jun  1 16:23:54.078: INFO: Pod "pod-subpath-test-dynamicpv-vwdw": Phase="Pending", Reason="", readiness=false. Elapsed: 21.194311834s
Jun  1 16:23:56.183: INFO: Pod "pod-subpath-test-dynamicpv-vwdw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.299216769s
STEP: Saw pod success
Jun  1 16:23:56.183: INFO: Pod "pod-subpath-test-dynamicpv-vwdw" satisfied condition "Succeeded or Failed"
Jun  1 16:23:56.287: INFO: Trying to get logs from node ip-172-20-46-125.eu-west-1.compute.internal pod pod-subpath-test-dynamicpv-vwdw container test-container-subpath-dynamicpv-vwdw: <nil>
STEP: delete the pod
Jun  1 16:23:56.523: INFO: Waiting for pod pod-subpath-test-dynamicpv-vwdw to disappear
Jun  1 16:23:56.627: INFO: Pod pod-subpath-test-dynamicpv-vwdw no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-vwdw
Jun  1 16:23:56.627: INFO: Deleting pod "pod-subpath-test-dynamicpv-vwdw" in namespace "provisioning-5496"
... skipping 379 lines ...
Jun  1 16:23:43.532: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-4620-e2e-sctwhzw      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-4620    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-4620-e2e-sctwhzw,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-4620    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-4620-e2e-sctwhzw,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-4620    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-4620-e2e-sctwhzw,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-4620-e2e-sctwhzw    e62c01ea-6922-40fb-8a31-91fab89fd164 12124 0 2021-06-01 16:23:43 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-01 16:23:43 +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-d7wdb pvc- provisioning-4620  0b9606a7-8e03-4726-99d7-294bae3da781 12134 0 2021-06-01 16:23:44 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-01 16:23:44 +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-4620-e2e-sctwhzw,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-ed12a5c3-7100-450c-aada-6081c095363c in namespace provisioning-4620
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun  1 16:23:58.704: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-56x27" in namespace "provisioning-4620" to be "Succeeded or Failed"
Jun  1 16:23:58.808: INFO: Pod "pvc-volume-tester-writer-56x27": Phase="Pending", Reason="", readiness=false. Elapsed: 104.442381ms
Jun  1 16:24:00.919: INFO: Pod "pvc-volume-tester-writer-56x27": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.214729769s
STEP: Saw pod success
Jun  1 16:24:00.919: INFO: Pod "pvc-volume-tester-writer-56x27" satisfied condition "Succeeded or Failed"
Jun  1 16:24:01.137: INFO: Pod pvc-volume-tester-writer-56x27 has the following logs: 
Jun  1 16:24:01.137: INFO: Deleting pod "pvc-volume-tester-writer-56x27" in namespace "provisioning-4620"
Jun  1 16:24:01.250: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-56x27" 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-57-211.eu-west-1.compute.internal"
Jun  1 16:24:01.671: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-5lc75" in namespace "provisioning-4620" to be "Succeeded or Failed"
Jun  1 16:24:01.775: INFO: Pod "pvc-volume-tester-reader-5lc75": Phase="Pending", Reason="", readiness=false. Elapsed: 104.7352ms
Jun  1 16:24:03.881: INFO: Pod "pvc-volume-tester-reader-5lc75": Phase="Pending", Reason="", readiness=false. Elapsed: 2.20994234s
Jun  1 16:24:05.987: INFO: Pod "pvc-volume-tester-reader-5lc75": Phase="Pending", Reason="", readiness=false. Elapsed: 4.315994714s
Jun  1 16:24:08.092: INFO: Pod "pvc-volume-tester-reader-5lc75": Phase="Pending", Reason="", readiness=false. Elapsed: 6.421334292s
Jun  1 16:24:10.197: INFO: Pod "pvc-volume-tester-reader-5lc75": Phase="Pending", Reason="", readiness=false. Elapsed: 8.526136199s
Jun  1 16:24:12.302: INFO: Pod "pvc-volume-tester-reader-5lc75": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.631413995s
STEP: Saw pod success
Jun  1 16:24:12.302: INFO: Pod "pvc-volume-tester-reader-5lc75" satisfied condition "Succeeded or Failed"
Jun  1 16:24:12.517: INFO: Pod pvc-volume-tester-reader-5lc75 has the following logs: hello world

Jun  1 16:24:12.517: INFO: Deleting pod "pvc-volume-tester-reader-5lc75" in namespace "provisioning-4620"
Jun  1 16:24:12.629: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-5lc75" to be fully deleted
Jun  1 16:24:12.733: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-d7wdb] to have phase Bound
Jun  1 16:24:12.838: INFO: PersistentVolumeClaim pvc-d7wdb found and phase=Bound (104.504617ms)
... skipping 35 lines ...

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

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

    /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 87 lines ...
STEP: Deleting pod hostexec-ip-172-20-60-88.eu-west-1.compute.internal-5grsn in namespace volumemode-7138
Jun  1 16:24:41.463: INFO: Deleting pod "pod-22a964e0-f118-4e09-bdd5-60916c6ca61b" in namespace "volumemode-7138"
Jun  1 16:24:41.569: INFO: Wait up to 5m0s for pod "pod-22a964e0-f118-4e09-bdd5-60916c6ca61b" to be fully deleted
STEP: Deleting pv and pvc
Jun  1 16:24:47.781: INFO: Deleting PersistentVolumeClaim "pvc-mtdkb"
Jun  1 16:24:47.889: INFO: Deleting PersistentVolume "aws-g9hxh"
Jun  1 16:24:48.201: INFO: Couldn't delete PD "aws://eu-west-1a/vol-0a6b6db953a513275", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a6b6db953a513275 is currently attached to i-01c79fe7421f52304
	status code: 400, request id: 2bb87d49-3b0c-46f8-be09-16b0566b052d
Jun  1 16:24:53.861: INFO: Successfully deleted PD "aws://eu-west-1a/vol-0a6b6db953a513275".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  1 16:24:53.861: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-7138" for this suite.
... skipping 135 lines ...
Jun  1 16:24:55.611: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 136 lines ...
Jun  1 16:24:43.847: INFO: Pod aws-client still exists
Jun  1 16:24:45.739: INFO: Waiting for pod aws-client to disappear
Jun  1 16:24:45.846: INFO: Pod aws-client still exists
Jun  1 16:24:47.740: INFO: Waiting for pod aws-client to disappear
Jun  1 16:24:47.846: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun  1 16:24:48.441: INFO: Couldn't delete PD "aws://eu-west-1a/vol-07e11682c2336f3c2", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07e11682c2336f3c2 is currently attached to i-0e6e8cb92e7778059
	status code: 400, request id: 5a269d28-61a3-4f58-9a69-8ee4a04c2875
Jun  1 16:24:54.247: INFO: Couldn't delete PD "aws://eu-west-1a/vol-07e11682c2336f3c2", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07e11682c2336f3c2 is currently attached to i-0e6e8cb92e7778059
	status code: 400, request id: e0975e70-0cc7-4930-8139-5ae3878c66a6
Jun  1 16:24:59.997: INFO: Successfully deleted PD "aws://eu-west-1a/vol-07e11682c2336f3c2".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  1 16:24:59.997: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-2525" for this suite.
... skipping 37 lines ...

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 336 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  1 16:24:23.323: 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.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun  1 16:24:23.853: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  1 16:24:23.853: INFO: Creating resource for dynamic PV
Jun  1 16:24:23.854: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-73937l2tl
STEP: creating a claim
Jun  1 16:24:23.974: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-fjmj
STEP: Checking for subpath error in container status
Jun  1 16:24:48.512: INFO: Deleting pod "pod-subpath-test-dynamicpv-fjmj" in namespace "provisioning-7393"
Jun  1 16:24:48.624: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-fjmj" to be fully deleted
STEP: Deleting pod
Jun  1 16:24:58.835: INFO: Deleting pod "pod-subpath-test-dynamicpv-fjmj" in namespace "provisioning-7393"
STEP: Deleting pvc
Jun  1 16:24:59.153: INFO: Deleting PersistentVolumeClaim "aws6gf7r"
... skipping 13 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.qpMXPyqcf/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.qpMXPyqcf/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.qpMXPyqcf/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.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [sig-storage] Volume Disk Format [Feature:vsphere]
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  1 16:25:15.018: INFO: >>> kubeConfig: /root/.kube/config
... skipping 303 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.qpMXPyqcf/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.qpMXPyqcf/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.qpMXPyqcf/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.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 285 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.qpMXPyqcf/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.qpMXPyqcf/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.qpMXPyqcf/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.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 12 lines ...
Jun  1 16:24:44.455: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-25775q5l2
STEP: creating a claim
Jun  1 16:24:44.564: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-htrs
STEP: Creating a pod to test subpath
Jun  1 16:24:44.888: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-htrs" in namespace "provisioning-2577" to be "Succeeded or Failed"
Jun  1 16:24:44.995: INFO: Pod "pod-subpath-test-dynamicpv-htrs": Phase="Pending", Reason="", readiness=false. Elapsed: 107.16371ms
Jun  1 16:24:47.103: INFO: Pod "pod-subpath-test-dynamicpv-htrs": Phase="Pending", Reason="", readiness=false. Elapsed: 2.214874375s
Jun  1 16:24:49.210: INFO: Pod "pod-subpath-test-dynamicpv-htrs": Phase="Pending", Reason="", readiness=false. Elapsed: 4.322243915s
Jun  1 16:24:51.318: INFO: Pod "pod-subpath-test-dynamicpv-htrs": Phase="Pending", Reason="", readiness=false. Elapsed: 6.430146492s
Jun  1 16:24:53.426: INFO: Pod "pod-subpath-test-dynamicpv-htrs": Phase="Pending", Reason="", readiness=false. Elapsed: 8.538245184s
Jun  1 16:24:55.540: INFO: Pod "pod-subpath-test-dynamicpv-htrs": Phase="Pending", Reason="", readiness=false. Elapsed: 10.652039947s
Jun  1 16:24:57.651: INFO: Pod "pod-subpath-test-dynamicpv-htrs": Phase="Pending", Reason="", readiness=false. Elapsed: 12.762561642s
Jun  1 16:24:59.759: INFO: Pod "pod-subpath-test-dynamicpv-htrs": Phase="Pending", Reason="", readiness=false. Elapsed: 14.871421179s
Jun  1 16:25:01.868: INFO: Pod "pod-subpath-test-dynamicpv-htrs": Phase="Pending", Reason="", readiness=false. Elapsed: 16.979995025s
Jun  1 16:25:03.976: INFO: Pod "pod-subpath-test-dynamicpv-htrs": Phase="Pending", Reason="", readiness=false. Elapsed: 19.087567497s
Jun  1 16:25:06.083: INFO: Pod "pod-subpath-test-dynamicpv-htrs": Phase="Pending", Reason="", readiness=false. Elapsed: 21.194584235s
Jun  1 16:25:08.190: INFO: Pod "pod-subpath-test-dynamicpv-htrs": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.301879s
STEP: Saw pod success
Jun  1 16:25:08.190: INFO: Pod "pod-subpath-test-dynamicpv-htrs" satisfied condition "Succeeded or Failed"
Jun  1 16:25:08.297: INFO: Trying to get logs from node ip-172-20-57-30.eu-west-1.compute.internal pod pod-subpath-test-dynamicpv-htrs container test-container-volume-dynamicpv-htrs: <nil>
STEP: delete the pod
Jun  1 16:25:08.519: INFO: Waiting for pod pod-subpath-test-dynamicpv-htrs to disappear
Jun  1 16:25:08.626: INFO: Pod pod-subpath-test-dynamicpv-htrs no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-htrs
Jun  1 16:25:08.626: INFO: Deleting pod "pod-subpath-test-dynamicpv-htrs" in namespace "provisioning-2577"
... skipping 34 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.qpMXPyqcf/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.qpMXPyqcf/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.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 117 lines ...
Jun  1 16:24:50.707: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1074-e2e-sck7tb8
STEP: creating a claim
Jun  1 16:24:50.814: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-snsc
STEP: Creating a pod to test subpath
Jun  1 16:24:51.137: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-snsc" in namespace "provisioning-1074" to be "Succeeded or Failed"
Jun  1 16:24:51.242: INFO: Pod "pod-subpath-test-dynamicpv-snsc": Phase="Pending", Reason="", readiness=false. Elapsed: 104.891757ms
Jun  1 16:24:53.347: INFO: Pod "pod-subpath-test-dynamicpv-snsc": Phase="Pending", Reason="", readiness=false. Elapsed: 2.209995386s
Jun  1 16:24:55.453: INFO: Pod "pod-subpath-test-dynamicpv-snsc": Phase="Pending", Reason="", readiness=false. Elapsed: 4.315558666s
Jun  1 16:24:57.559: INFO: Pod "pod-subpath-test-dynamicpv-snsc": Phase="Pending", Reason="", readiness=false. Elapsed: 6.421657642s
Jun  1 16:24:59.665: INFO: Pod "pod-subpath-test-dynamicpv-snsc": Phase="Pending", Reason="", readiness=false. Elapsed: 8.527686308s
Jun  1 16:25:01.772: INFO: Pod "pod-subpath-test-dynamicpv-snsc": Phase="Pending", Reason="", readiness=false. Elapsed: 10.634221847s
Jun  1 16:25:03.877: INFO: Pod "pod-subpath-test-dynamicpv-snsc": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.739440516s
STEP: Saw pod success
Jun  1 16:25:03.877: INFO: Pod "pod-subpath-test-dynamicpv-snsc" satisfied condition "Succeeded or Failed"
Jun  1 16:25:03.982: INFO: Trying to get logs from node ip-172-20-60-88.eu-west-1.compute.internal pod pod-subpath-test-dynamicpv-snsc container test-container-subpath-dynamicpv-snsc: <nil>
STEP: delete the pod
Jun  1 16:25:04.209: INFO: Waiting for pod pod-subpath-test-dynamicpv-snsc to disappear
Jun  1 16:25:04.314: INFO: Pod pod-subpath-test-dynamicpv-snsc no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-snsc
Jun  1 16:25:04.314: INFO: Deleting pod "pod-subpath-test-dynamicpv-snsc" in namespace "provisioning-1074"
... skipping 399 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  1 16:25:25.448: 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.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun  1 16:25:25.986: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  1 16:25:25.986: INFO: Creating resource for dynamic PV
Jun  1 16:25:25.986: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-77372nx2x
STEP: creating a claim
Jun  1 16:25:26.097: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-p4p2
STEP: Checking for subpath error in container status
Jun  1 16:25:42.643: INFO: Deleting pod "pod-subpath-test-dynamicpv-p4p2" in namespace "provisioning-7737"
Jun  1 16:25:42.751: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-p4p2" to be fully deleted
STEP: Deleting pod
Jun  1 16:25:56.966: INFO: Deleting pod "pod-subpath-test-dynamicpv-p4p2" in namespace "provisioning-7737"
STEP: Deleting pvc
Jun  1 16:25:57.289: INFO: Deleting PersistentVolumeClaim "aws6968x"
... skipping 11 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.qpMXPyqcf/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.qpMXPyqcf/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath file is outside the volume [Slow][LinuxOnly]
      /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 14 lines ...
Jun  1 16:25:17.553: INFO: PersistentVolumeClaim pvc-fcflk found but phase is Pending instead of Bound.
Jun  1 16:25:19.661: INFO: PersistentVolumeClaim pvc-fcflk found and phase=Bound (2.213712479s)
Jun  1 16:25:19.661: INFO: Waiting up to 3m0s for PersistentVolume aws-65nv9 to have phase Bound
Jun  1 16:25:19.767: INFO: PersistentVolume aws-65nv9 found and phase=Bound (105.864675ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-jfz7
STEP: Creating a pod to test exec-volume-test
Jun  1 16:25:20.093: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-jfz7" in namespace "volume-2468" to be "Succeeded or Failed"
Jun  1 16:25:20.199: INFO: Pod "exec-volume-test-preprovisionedpv-jfz7": Phase="Pending", Reason="", readiness=false. Elapsed: 106.741299ms
Jun  1 16:25:22.306: INFO: Pod "exec-volume-test-preprovisionedpv-jfz7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.212964956s
Jun  1 16:25:24.412: INFO: Pod "exec-volume-test-preprovisionedpv-jfz7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.319139281s
Jun  1 16:25:26.518: INFO: Pod "exec-volume-test-preprovisionedpv-jfz7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.425009655s
Jun  1 16:25:28.624: INFO: Pod "exec-volume-test-preprovisionedpv-jfz7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.531419348s
Jun  1 16:25:30.731: INFO: Pod "exec-volume-test-preprovisionedpv-jfz7": Phase="Pending", Reason="", readiness=false. Elapsed: 10.638714133s
Jun  1 16:25:32.838: INFO: Pod "exec-volume-test-preprovisionedpv-jfz7": Phase="Pending", Reason="", readiness=false. Elapsed: 12.745668835s
Jun  1 16:25:34.945: INFO: Pod "exec-volume-test-preprovisionedpv-jfz7": Phase="Pending", Reason="", readiness=false. Elapsed: 14.852703449s
Jun  1 16:25:37.051: INFO: Pod "exec-volume-test-preprovisionedpv-jfz7": Phase="Pending", Reason="", readiness=false. Elapsed: 16.958545546s
Jun  1 16:25:39.158: INFO: Pod "exec-volume-test-preprovisionedpv-jfz7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.065608844s
STEP: Saw pod success
Jun  1 16:25:39.158: INFO: Pod "exec-volume-test-preprovisionedpv-jfz7" satisfied condition "Succeeded or Failed"
Jun  1 16:25:39.264: INFO: Trying to get logs from node ip-172-20-57-30.eu-west-1.compute.internal pod exec-volume-test-preprovisionedpv-jfz7 container exec-container-preprovisionedpv-jfz7: <nil>
STEP: delete the pod
Jun  1 16:25:39.496: INFO: Waiting for pod exec-volume-test-preprovisionedpv-jfz7 to disappear
Jun  1 16:25:39.602: INFO: Pod exec-volume-test-preprovisionedpv-jfz7 no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-jfz7
Jun  1 16:25:39.602: INFO: Deleting pod "exec-volume-test-preprovisionedpv-jfz7" in namespace "volume-2468"
STEP: Deleting pv and pvc
Jun  1 16:25:39.709: INFO: Deleting PersistentVolumeClaim "pvc-fcflk"
Jun  1 16:25:39.816: INFO: Deleting PersistentVolume "aws-65nv9"
Jun  1 16:25:40.125: INFO: Couldn't delete PD "aws://eu-west-1a/vol-0937974d6d1805548", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0937974d6d1805548 is currently attached to i-0e6e8cb92e7778059
	status code: 400, request id: bb12ba5c-f704-4928-84a8-7e7e88bf7d5c
Jun  1 16:25:45.801: INFO: Couldn't delete PD "aws://eu-west-1a/vol-0937974d6d1805548", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0937974d6d1805548 is currently attached to i-0e6e8cb92e7778059
	status code: 400, request id: 09beaccf-d73a-4f14-8aa9-b9ea15e81aff
Jun  1 16:25:51.535: INFO: Couldn't delete PD "aws://eu-west-1a/vol-0937974d6d1805548", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0937974d6d1805548 is currently attached to i-0e6e8cb92e7778059
	status code: 400, request id: 0d11f870-d81b-4423-843b-88b017472208
Jun  1 16:25:57.154: INFO: Couldn't delete PD "aws://eu-west-1a/vol-0937974d6d1805548", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0937974d6d1805548 is currently attached to i-0e6e8cb92e7778059
	status code: 400, request id: 6771cf70-14fb-455b-b975-cde89cc882b4
Jun  1 16:26:02.862: INFO: Successfully deleted PD "aws://eu-west-1a/vol-0937974d6d1805548".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  1 16:26:02.862: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-2468" for this suite.
... skipping 14 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  1 16:25:14.577: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename volumemode
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail to use a volume in a pod with mismatched mode [Slow]
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  1 16:25:15.114: INFO: Creating resource for dynamic PV
Jun  1 16:25:15.114: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-177-e2e-scqtsf7
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  1 16:25:19.870: INFO: Deleting pod "pod-c9d95def-b514-4277-bf6b-e7286bfb98b6" in namespace "volumemode-177"
Jun  1 16:25:19.976: INFO: Wait up to 5m0s for pod "pod-c9d95def-b514-4277-bf6b-e7286bfb98b6" to be fully deleted
STEP: Deleting pvc
Jun  1 16:25:28.402: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comnk8ms"
Jun  1 16:25:28.511: INFO: Waiting up to 5m0s for PersistentVolume pvc-ea279531-12c9-4ec2-9250-65c1637eea63 to get deleted
Jun  1 16:25:28.617: INFO: PersistentVolume pvc-ea279531-12c9-4ec2-9250-65c1637eea63 found and phase=Released (106.108538ms)
... skipping 13 lines ...

• [SLOW TEST:50.114 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.qpMXPyqcf/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.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (xfs)][Slow] volumes
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (xfs)][Slow] volumes
  /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 190 lines ...
Jun  1 16:25:17.560: INFO: Creating resource for dynamic PV
Jun  1 16:25:17.560: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8119-e2e-sc7d6ns
STEP: creating a claim
Jun  1 16:25:17.664: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-8119
Jun  1 16:25:17.978: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-8119" in namespace "provisioning-8119" to be "Succeeded or Failed"
Jun  1 16:25:18.083: INFO: Pod "volume-prep-provisioning-8119": Phase="Pending", Reason="", readiness=false. Elapsed: 104.053672ms
Jun  1 16:25:20.189: INFO: Pod "volume-prep-provisioning-8119": Phase="Pending", Reason="", readiness=false. Elapsed: 2.210790448s
Jun  1 16:25:22.294: INFO: Pod "volume-prep-provisioning-8119": Phase="Pending", Reason="", readiness=false. Elapsed: 4.3158491s
Jun  1 16:25:24.399: INFO: Pod "volume-prep-provisioning-8119": Phase="Pending", Reason="", readiness=false. Elapsed: 6.420443429s
Jun  1 16:25:26.504: INFO: Pod "volume-prep-provisioning-8119": Phase="Pending", Reason="", readiness=false. Elapsed: 8.525810928s
Jun  1 16:25:28.610: INFO: Pod "volume-prep-provisioning-8119": Phase="Pending", Reason="", readiness=false. Elapsed: 10.631498993s
Jun  1 16:25:30.716: INFO: Pod "volume-prep-provisioning-8119": Phase="Pending", Reason="", readiness=false. Elapsed: 12.737813222s
Jun  1 16:25:32.822: INFO: Pod "volume-prep-provisioning-8119": Phase="Pending", Reason="", readiness=false. Elapsed: 14.843310492s
Jun  1 16:25:34.932: INFO: Pod "volume-prep-provisioning-8119": Phase="Pending", Reason="", readiness=false. Elapsed: 16.953301995s
Jun  1 16:25:37.036: INFO: Pod "volume-prep-provisioning-8119": Phase="Pending", Reason="", readiness=false. Elapsed: 19.057473996s
Jun  1 16:25:39.140: INFO: Pod "volume-prep-provisioning-8119": Phase="Pending", Reason="", readiness=false. Elapsed: 21.161729696s
Jun  1 16:25:41.246: INFO: Pod "volume-prep-provisioning-8119": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.267526208s
STEP: Saw pod success
Jun  1 16:25:41.246: INFO: Pod "volume-prep-provisioning-8119" satisfied condition "Succeeded or Failed"
Jun  1 16:25:41.246: INFO: Deleting pod "volume-prep-provisioning-8119" in namespace "provisioning-8119"
Jun  1 16:25:41.358: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-8119" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-tbgj
STEP: Checking for subpath error in container status
Jun  1 16:25:45.776: INFO: Deleting pod "pod-subpath-test-dynamicpv-tbgj" in namespace "provisioning-8119"
Jun  1 16:25:45.890: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-tbgj" to be fully deleted
STEP: Deleting pod
Jun  1 16:25:45.994: INFO: Deleting pod "pod-subpath-test-dynamicpv-tbgj" in namespace "provisioning-8119"
STEP: Deleting pvc
Jun  1 16:25:46.309: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comwrdgl"
... skipping 36 lines ...
Jun  1 16:25:33.291: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4173qrdr6
STEP: creating a claim
Jun  1 16:25:33.398: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-44gc
STEP: Creating a pod to test subpath
Jun  1 16:25:33.723: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-44gc" in namespace "provisioning-4173" to be "Succeeded or Failed"
Jun  1 16:25:33.828: INFO: Pod "pod-subpath-test-dynamicpv-44gc": Phase="Pending", Reason="", readiness=false. Elapsed: 105.553158ms
Jun  1 16:25:35.934: INFO: Pod "pod-subpath-test-dynamicpv-44gc": Phase="Pending", Reason="", readiness=false. Elapsed: 2.211399105s
Jun  1 16:25:38.041: INFO: Pod "pod-subpath-test-dynamicpv-44gc": Phase="Pending", Reason="", readiness=false. Elapsed: 4.318396898s
Jun  1 16:25:40.151: INFO: Pod "pod-subpath-test-dynamicpv-44gc": Phase="Pending", Reason="", readiness=false. Elapsed: 6.428263772s
Jun  1 16:25:42.257: INFO: Pod "pod-subpath-test-dynamicpv-44gc": Phase="Pending", Reason="", readiness=false. Elapsed: 8.534074736s
Jun  1 16:25:44.364: INFO: Pod "pod-subpath-test-dynamicpv-44gc": Phase="Pending", Reason="", readiness=false. Elapsed: 10.64165008s
Jun  1 16:25:46.471: INFO: Pod "pod-subpath-test-dynamicpv-44gc": Phase="Pending", Reason="", readiness=false. Elapsed: 12.74851611s
Jun  1 16:25:48.577: INFO: Pod "pod-subpath-test-dynamicpv-44gc": Phase="Pending", Reason="", readiness=false. Elapsed: 14.854706954s
Jun  1 16:25:50.684: INFO: Pod "pod-subpath-test-dynamicpv-44gc": Phase="Pending", Reason="", readiness=false. Elapsed: 16.961338001s
Jun  1 16:25:52.790: INFO: Pod "pod-subpath-test-dynamicpv-44gc": Phase="Pending", Reason="", readiness=false. Elapsed: 19.067450773s
Jun  1 16:25:54.897: INFO: Pod "pod-subpath-test-dynamicpv-44gc": Phase="Pending", Reason="", readiness=false. Elapsed: 21.174576001s
Jun  1 16:25:57.004: INFO: Pod "pod-subpath-test-dynamicpv-44gc": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.281330011s
STEP: Saw pod success
Jun  1 16:25:57.004: INFO: Pod "pod-subpath-test-dynamicpv-44gc" satisfied condition "Succeeded or Failed"
Jun  1 16:25:57.111: INFO: Trying to get logs from node ip-172-20-57-30.eu-west-1.compute.internal pod pod-subpath-test-dynamicpv-44gc container test-container-subpath-dynamicpv-44gc: <nil>
STEP: delete the pod
Jun  1 16:25:57.330: INFO: Waiting for pod pod-subpath-test-dynamicpv-44gc to disappear
Jun  1 16:25:57.436: INFO: Pod pod-subpath-test-dynamicpv-44gc no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-44gc
Jun  1 16:25:57.436: INFO: Deleting pod "pod-subpath-test-dynamicpv-44gc" in namespace "provisioning-4173"
... skipping 198 lines ...
Jun  1 16:25:00.762: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7325-e2e-scw6mh2
STEP: creating a claim
Jun  1 16:25:00.872: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-8wg7
STEP: Creating a pod to test subpath
Jun  1 16:25:01.215: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-8wg7" in namespace "provisioning-7325" to be "Succeeded or Failed"
Jun  1 16:25:01.323: INFO: Pod "pod-subpath-test-dynamicpv-8wg7": Phase="Pending", Reason="", readiness=false. Elapsed: 107.555594ms
Jun  1 16:25:03.430: INFO: Pod "pod-subpath-test-dynamicpv-8wg7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.214685512s
Jun  1 16:25:05.537: INFO: Pod "pod-subpath-test-dynamicpv-8wg7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.321807785s
Jun  1 16:25:07.644: INFO: Pod "pod-subpath-test-dynamicpv-8wg7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.42877968s
Jun  1 16:25:09.751: INFO: Pod "pod-subpath-test-dynamicpv-8wg7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.536344325s
Jun  1 16:25:11.858: INFO: Pod "pod-subpath-test-dynamicpv-8wg7": Phase="Pending", Reason="", readiness=false. Elapsed: 10.643372527s
Jun  1 16:25:13.973: INFO: Pod "pod-subpath-test-dynamicpv-8wg7": Phase="Pending", Reason="", readiness=false. Elapsed: 12.758486993s
Jun  1 16:25:16.080: INFO: Pod "pod-subpath-test-dynamicpv-8wg7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.864923981s
STEP: Saw pod success
Jun  1 16:25:16.080: INFO: Pod "pod-subpath-test-dynamicpv-8wg7" satisfied condition "Succeeded or Failed"
Jun  1 16:25:16.186: INFO: Trying to get logs from node ip-172-20-57-30.eu-west-1.compute.internal pod pod-subpath-test-dynamicpv-8wg7 container test-container-subpath-dynamicpv-8wg7: <nil>
STEP: delete the pod
Jun  1 16:25:16.411: INFO: Waiting for pod pod-subpath-test-dynamicpv-8wg7 to disappear
Jun  1 16:25:16.517: INFO: Pod pod-subpath-test-dynamicpv-8wg7 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-8wg7
Jun  1 16:25:16.517: INFO: Deleting pod "pod-subpath-test-dynamicpv-8wg7" in namespace "provisioning-7325"
STEP: Creating pod pod-subpath-test-dynamicpv-8wg7
STEP: Creating a pod to test subpath
Jun  1 16:25:16.760: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-8wg7" in namespace "provisioning-7325" to be "Succeeded or Failed"
Jun  1 16:25:16.910: INFO: Pod "pod-subpath-test-dynamicpv-8wg7": Phase="Pending", Reason="", readiness=false. Elapsed: 150.575144ms
Jun  1 16:25:19.018: INFO: Pod "pod-subpath-test-dynamicpv-8wg7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.258120828s
Jun  1 16:25:21.125: INFO: Pod "pod-subpath-test-dynamicpv-8wg7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.365560895s
Jun  1 16:25:23.234: INFO: Pod "pod-subpath-test-dynamicpv-8wg7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.474305304s
Jun  1 16:25:25.342: INFO: Pod "pod-subpath-test-dynamicpv-8wg7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.581946058s
Jun  1 16:25:27.449: INFO: Pod "pod-subpath-test-dynamicpv-8wg7": Phase="Pending", Reason="", readiness=false. Elapsed: 10.689647128s
... skipping 6 lines ...
Jun  1 16:25:42.205: INFO: Pod "pod-subpath-test-dynamicpv-8wg7": Phase="Pending", Reason="", readiness=false. Elapsed: 25.444984872s
Jun  1 16:25:44.311: INFO: Pod "pod-subpath-test-dynamicpv-8wg7": Phase="Pending", Reason="", readiness=false. Elapsed: 27.55182659s
Jun  1 16:25:46.418: INFO: Pod "pod-subpath-test-dynamicpv-8wg7": Phase="Pending", Reason="", readiness=false. Elapsed: 29.658652285s
Jun  1 16:25:48.525: INFO: Pod "pod-subpath-test-dynamicpv-8wg7": Phase="Pending", Reason="", readiness=false. Elapsed: 31.765146181s
Jun  1 16:25:50.632: INFO: Pod "pod-subpath-test-dynamicpv-8wg7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 33.872103678s
STEP: Saw pod success
Jun  1 16:25:50.632: INFO: Pod "pod-subpath-test-dynamicpv-8wg7" satisfied condition "Succeeded or Failed"
Jun  1 16:25:50.738: INFO: Trying to get logs from node ip-172-20-46-125.eu-west-1.compute.internal pod pod-subpath-test-dynamicpv-8wg7 container test-container-subpath-dynamicpv-8wg7: <nil>
STEP: delete the pod
Jun  1 16:25:50.963: INFO: Waiting for pod pod-subpath-test-dynamicpv-8wg7 to disappear
Jun  1 16:25:51.069: INFO: Pod pod-subpath-test-dynamicpv-8wg7 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-8wg7
Jun  1 16:25:51.069: INFO: Deleting pod "pod-subpath-test-dynamicpv-8wg7" in namespace "provisioning-7325"
... skipping 85 lines ...
Jun  1 16:23:56.287: INFO: Creating resource for dynamic PV
Jun  1 16:23:56.287: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-7592-e2e-scrdtzt
STEP: creating a claim
Jun  1 16:23:56.397: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun  1 16:23:56.728: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-w96bd" in namespace "snapshotting-7592" to be "Succeeded or Failed"
Jun  1 16:23:56.835: INFO: Pod "pvc-snapshottable-tester-w96bd": Phase="Pending", Reason="", readiness=false. Elapsed: 107.562912ms
Jun  1 16:23:58.941: INFO: Pod "pvc-snapshottable-tester-w96bd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.213581869s
Jun  1 16:24:01.063: INFO: Pod "pvc-snapshottable-tester-w96bd": Phase="Pending", Reason="", readiness=false. Elapsed: 4.335567381s
Jun  1 16:24:03.170: INFO: Pod "pvc-snapshottable-tester-w96bd": Phase="Pending", Reason="", readiness=false. Elapsed: 6.441870192s
Jun  1 16:24:05.275: INFO: Pod "pvc-snapshottable-tester-w96bd": Phase="Pending", Reason="", readiness=false. Elapsed: 8.54760348s
Jun  1 16:24:07.380: INFO: Pod "pvc-snapshottable-tester-w96bd": Phase="Pending", Reason="", readiness=false. Elapsed: 10.652585445s
Jun  1 16:24:09.486: INFO: Pod "pvc-snapshottable-tester-w96bd": Phase="Pending", Reason="", readiness=false. Elapsed: 12.758279578s
Jun  1 16:24:11.594: INFO: Pod "pvc-snapshottable-tester-w96bd": Phase="Pending", Reason="", readiness=false. Elapsed: 14.86651784s
Jun  1 16:24:13.700: INFO: Pod "pvc-snapshottable-tester-w96bd": Phase="Pending", Reason="", readiness=false. Elapsed: 16.971813693s
Jun  1 16:24:15.805: INFO: Pod "pvc-snapshottable-tester-w96bd": Phase="Pending", Reason="", readiness=false. Elapsed: 19.07725161s
Jun  1 16:24:17.915: INFO: Pod "pvc-snapshottable-tester-w96bd": Phase="Pending", Reason="", readiness=false. Elapsed: 21.186981643s
Jun  1 16:24:20.029: INFO: Pod "pvc-snapshottable-tester-w96bd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.301538773s
STEP: Saw pod success
Jun  1 16:24:20.029: INFO: Pod "pvc-snapshottable-tester-w96bd" satisfied condition "Succeeded or Failed"
Jun  1 16:24:20.242: INFO: Pod pvc-snapshottable-tester-w96bd has the following logs: 
Jun  1 16:24:20.242: INFO: Deleting pod "pvc-snapshottable-tester-w96bd" in namespace "snapshotting-7592"
Jun  1 16:24:20.373: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-w96bd" to be fully deleted
Jun  1 16:24:20.495: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comczpfd] to have phase Bound
Jun  1 16:24:20.599: INFO: PersistentVolumeClaim ebs.csi.aws.comczpfd found and phase=Bound (104.673223ms)
STEP: [init] checking the claim
... skipping 57 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.qpMXPyqcf/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  1 16:25:23.920: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-bw2lk" in namespace "snapshotting-7592" to be "Succeeded or Failed"
Jun  1 16:25:24.025: INFO: Pod "pvc-snapshottable-data-tester-bw2lk": Phase="Pending", Reason="", readiness=false. Elapsed: 104.700579ms
Jun  1 16:25:26.130: INFO: Pod "pvc-snapshottable-data-tester-bw2lk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.209990988s
Jun  1 16:25:28.236: INFO: Pod "pvc-snapshottable-data-tester-bw2lk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.316033393s
Jun  1 16:25:30.342: INFO: Pod "pvc-snapshottable-data-tester-bw2lk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.422276223s
Jun  1 16:25:32.448: INFO: Pod "pvc-snapshottable-data-tester-bw2lk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.528448417s
Jun  1 16:25:34.555: INFO: Pod "pvc-snapshottable-data-tester-bw2lk": Phase="Pending", Reason="", readiness=false. Elapsed: 10.634707194s
Jun  1 16:25:36.660: INFO: Pod "pvc-snapshottable-data-tester-bw2lk": Phase="Pending", Reason="", readiness=false. Elapsed: 12.739716044s
Jun  1 16:25:38.766: INFO: Pod "pvc-snapshottable-data-tester-bw2lk": Phase="Pending", Reason="", readiness=false. Elapsed: 14.84583028s
Jun  1 16:25:40.873: INFO: Pod "pvc-snapshottable-data-tester-bw2lk": Phase="Pending", Reason="", readiness=false. Elapsed: 16.952893783s
Jun  1 16:25:42.979: INFO: Pod "pvc-snapshottable-data-tester-bw2lk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.05922037s
STEP: Saw pod success
Jun  1 16:25:42.979: INFO: Pod "pvc-snapshottable-data-tester-bw2lk" satisfied condition "Succeeded or Failed"
Jun  1 16:25:43.190: INFO: Pod pvc-snapshottable-data-tester-bw2lk has the following logs: 
Jun  1 16:25:43.190: INFO: Deleting pod "pvc-snapshottable-data-tester-bw2lk" in namespace "snapshotting-7592"
Jun  1 16:25:43.302: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-bw2lk" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun  1 16:25:57.831: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-7592 exec restored-pvc-tester-kgcsq --namespace=snapshotting-7592 -- cat /mnt/test/data'
... skipping 220 lines ...
      /tmp/kops.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:320
------------------------------


Summarizing 1 Failure:

[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.qpMXPyqcf/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:602

Ran 141 of 485 Specs in 590.227 seconds
FAIL! -- 140 Passed | 1 Failed | 0 Pending | 344 Skipped


Ginkgo ran 1 suite in 12m34.712434937s
Test Suite Failed
I0601 16:27:43.102809   29249 app.go:59] RunDir for this run: "/logs/artifacts/5000eaeb-c2f2-11eb-82a3-e65d1f537deb"
I0601 16:27:43.102983   29249 app.go:90] ID for this run: "5000eaeb-c2f2-11eb-82a3-e65d1f537deb"
I0601 16:27:43.103004   29249 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
I0601 16:27:43.118450   29255 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0601 16:27:43.118533   29255 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
2021/06/01 16:27:53 Dumping node ip-172-20-46-125.eu-west-1.compute.internal
... skipping 1519 lines ...