This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-06-10 08:05
Elapsed47m27s
Revisionmaster

No Test Failures!


Error lines from build-log.txt

... skipping 489 lines ...
I0610 08:10:04.787337   11674 up.go:43] Cleaning up any leaked resources from previous cluster
I0610 08:10:04.787351   11674 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
I0610 08:10:04.804068   11680 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0610 08:10:04.804168   11680 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io" not found
W0610 08:10:05.353748   11674 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0610 08:10:05.353793   11674 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
I0610 08:10:05.368514   11690 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0610 08:10:05.368605   11690 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io" not found
I0610 08:10:05.939024   11674 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/06/10 08:10:05 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
I0610 08:10:05.950500   11674 http.go:37] curl https://ip.jsb.workers.dev
I0610 08:10:06.120589   11674 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.184.77.158/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones eu-west-2a --master-size c5.large
I0610 08:10:06.134465   11704 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0610 08:10:06.134538   11704 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I0610 08:10:06.179355   11704 create_cluster.go:728] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0610 08:10:07.016788   11704 new_cluster.go:1039]  Cloud Provider ID = aws
... skipping 40 lines ...

I0610 08:10:34.980976   11674 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
I0610 08:10:34.994322   11724 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0610 08:10:34.994413   11724 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io

W0610 08:10:36.355487   11724 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-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0610 08:10:46.401594   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0610 08:10:56.443940   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0610 08:11:06.545934   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0610 08:11:16.614681   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0610 08:11:26.672685   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0610 08:11:36.734233   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0610 08:11:46.782516   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0610 08:11:56.859158   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0610 08:13:27.289720   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
W0610 08:13:37.312064   11724 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-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0610 08:13:47.353147   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
W0610 08:13:57.413436   11724 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-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0610 08:14:07.455028   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0610 08:14:17.502098   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0610 08:14:27.545483   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0610 08:14:37.589339   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0610 08:14:47.636189   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0610 08:14:57.673175   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0610 08:15:07.744184   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0610 08:15:17.837628   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 14 lines ...
Pod	kube-system/coredns-autoscaler-6f594f4c58-2ndkl					system-cluster-critical pod "coredns-autoscaler-6f594f4c58-2ndkl" is pending
Pod	kube-system/coredns-f45c4bf76-d69qd						system-cluster-critical pod "coredns-f45c4bf76-d69qd" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-2mvg7					system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-2mvg7" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-qp4bh					system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-qp4bh" is pending
Pod	kube-system/etcd-manager-main-ip-172-20-43-21.eu-west-2.compute.internal	system-cluster-critical pod "etcd-manager-main-ip-172-20-43-21.eu-west-2.compute.internal" is pending

Validation Failed
W0610 08:15:30.797193   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 13 lines ...
Pod	kube-system/cert-manager-webhook-7bbf67968-gpltt	system-cluster-critical pod "cert-manager-webhook-7bbf67968-gpltt" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-2ndkl		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-2ndkl" is pending
Pod	kube-system/coredns-f45c4bf76-d69qd			system-cluster-critical pod "coredns-f45c4bf76-d69qd" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-2mvg7		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-2mvg7" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-qp4bh		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-qp4bh" is pending

Validation Failed
W0610 08:15:42.927560   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 16 lines ...
Pod	kube-system/coredns-autoscaler-6f594f4c58-2ndkl					system-cluster-critical pod "coredns-autoscaler-6f594f4c58-2ndkl" is pending
Pod	kube-system/coredns-f45c4bf76-d69qd						system-cluster-critical pod "coredns-f45c4bf76-d69qd" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-2mvg7					system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-2mvg7" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-qp4bh					system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-qp4bh" is pending
Pod	kube-system/kube-controller-manager-ip-172-20-43-21.eu-west-2.compute.internal	system-cluster-critical pod "kube-controller-manager-ip-172-20-43-21.eu-west-2.compute.internal" is pending

Validation Failed
W0610 08:15:55.007100   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 16 lines ...
Pod	kube-system/coredns-autoscaler-6f594f4c58-2ndkl				system-cluster-critical pod "coredns-autoscaler-6f594f4c58-2ndkl" is pending
Pod	kube-system/coredns-f45c4bf76-d69qd					system-cluster-critical pod "coredns-f45c4bf76-d69qd" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-2mvg7				system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-2mvg7" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-qp4bh				system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-qp4bh" is pending
Pod	kube-system/kube-scheduler-ip-172-20-43-21.eu-west-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-43-21.eu-west-2.compute.internal" is pending

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

... skipping 12 lines ...
Pod	kube-system/cert-manager-webhook-7bbf67968-gpltt	system-cluster-critical pod "cert-manager-webhook-7bbf67968-gpltt" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-2ndkl		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-2ndkl" is pending
Pod	kube-system/coredns-f45c4bf76-d69qd			system-cluster-critical pod "coredns-f45c4bf76-d69qd" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-2mvg7		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-2mvg7" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-qp4bh		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-qp4bh" is pending

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

... skipping 23 lines ...
Pod	kube-system/ebs-csi-node-cwr99						system-node-critical pod "ebs-csi-node-cwr99" is pending
Pod	kube-system/ebs-csi-node-fndjg						system-node-critical pod "ebs-csi-node-fndjg" is pending
Pod	kube-system/kube-proxy-ip-172-20-36-68.eu-west-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-36-68.eu-west-2.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-45-65.eu-west-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-45-65.eu-west-2.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-58-127.eu-west-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-58-127.eu-west-2.compute.internal" is pending

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

... skipping 22 lines ...
Pod	kube-system/ebs-csi-node-45tcd						system-node-critical pod "ebs-csi-node-45tcd" is pending
Pod	kube-system/ebs-csi-node-cwr99						system-node-critical pod "ebs-csi-node-cwr99" is pending
Pod	kube-system/ebs-csi-node-fndjg						system-node-critical pod "ebs-csi-node-fndjg" is pending
Pod	kube-system/ebs-csi-node-zpv4x						system-node-critical pod "ebs-csi-node-zpv4x" is pending
Pod	kube-system/kube-proxy-ip-172-20-59-227.eu-west-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-59-227.eu-west-2.compute.internal" is pending

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

... skipping 14 lines ...
Pod	kube-system/calico-node-w9nvt				system-node-critical pod "calico-node-w9nvt" is not ready (calico-node)
Pod	kube-system/cert-manager-cainjector-74d69756d5-dcm5w	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-dcm5w" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-gpltt	system-cluster-critical pod "cert-manager-webhook-7bbf67968-gpltt" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-2ndkl		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-2ndkl" is pending
Pod	kube-system/coredns-f45c4bf76-d69qd			system-cluster-critical pod "coredns-f45c4bf76-d69qd" is pending

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

... skipping 9 lines ...
KIND	NAME						MESSAGE
Node	ip-172-20-59-227.eu-west-2.compute.internal	node "ip-172-20-59-227.eu-west-2.compute.internal" of role "node" is not ready
Pod	kube-system/calico-node-glhbh			system-node-critical pod "calico-node-glhbh" is not ready (calico-node)
Pod	kube-system/calico-node-qhncn			system-node-critical pod "calico-node-qhncn" is not ready (calico-node)
Pod	kube-system/calico-node-w9nvt			system-node-critical pod "calico-node-w9nvt" is not ready (calico-node)

Validation Failed
W0610 08:17:06.978428   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

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

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

      Distro debian doesn't support ntfs -- skipping

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

      Distro debian doesn't support ntfs -- skipping

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

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.Y1KozJqJu/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.Y1KozJqJu/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.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 182 lines ...
STEP: Creating a kubernetes client
Jun 10 08:20:27.618: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename volumemode
W0610 08:20:29.845693   25627 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Jun 10 08:20:29.845: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
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.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 10 08:20:30.058: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 10 08:20:30.058: INFO: Creating resource for dynamic PV
Jun 10 08:20:30.058: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-6649ghtgt
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 10 08:20:42.813: INFO: Deleting pod "pod-c9286320-8b88-4cee-ba01-0474a5171f1e" in namespace "volumemode-6649"
Jun 10 08:20:42.920: INFO: Wait up to 5m0s for pod "pod-c9286320-8b88-4cee-ba01-0474a5171f1e" to be fully deleted
STEP: Deleting pvc
Jun 10 08:20:47.347: INFO: Deleting PersistentVolumeClaim "aws65n8n"
Jun 10 08:20:47.461: INFO: Waiting up to 5m0s for PersistentVolume pvc-1995acdb-2162-4a05-9de3-c86f89472e90 to get deleted
Jun 10 08:20:47.568: INFO: PersistentVolume pvc-1995acdb-2162-4a05-9de3-c86f89472e90 found and phase=Released (106.618985ms)
... skipping 11 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Y1KozJqJu/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Y1KozJqJu/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (block volmode)] volumeMode
    /tmp/kops.Y1KozJqJu/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.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 158 lines ...
Jun 10 08:20:28.407: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-3890-e2e-sc45xc6
STEP: creating a claim
Jun 10 08:20:28.514: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-w758
STEP: Creating a pod to test exec-volume-test
Jun 10 08:20:28.843: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-w758" in namespace "volume-3890" to be "Succeeded or Failed"
Jun 10 08:20:28.948: INFO: Pod "exec-volume-test-dynamicpv-w758": Phase="Pending", Reason="", readiness=false. Elapsed: 104.934448ms
Jun 10 08:20:31.053: INFO: Pod "exec-volume-test-dynamicpv-w758": Phase="Pending", Reason="", readiness=false. Elapsed: 2.210052861s
Jun 10 08:20:33.160: INFO: Pod "exec-volume-test-dynamicpv-w758": Phase="Pending", Reason="", readiness=false. Elapsed: 4.316570061s
Jun 10 08:20:35.266: INFO: Pod "exec-volume-test-dynamicpv-w758": Phase="Pending", Reason="", readiness=false. Elapsed: 6.42248438s
Jun 10 08:20:37.376: INFO: Pod "exec-volume-test-dynamicpv-w758": Phase="Pending", Reason="", readiness=false. Elapsed: 8.532581745s
Jun 10 08:20:39.481: INFO: Pod "exec-volume-test-dynamicpv-w758": Phase="Pending", Reason="", readiness=false. Elapsed: 10.638156501s
... skipping 3 lines ...
Jun 10 08:20:47.909: INFO: Pod "exec-volume-test-dynamicpv-w758": Phase="Pending", Reason="", readiness=false. Elapsed: 19.065378545s
Jun 10 08:20:50.014: INFO: Pod "exec-volume-test-dynamicpv-w758": Phase="Pending", Reason="", readiness=false. Elapsed: 21.171130962s
Jun 10 08:20:52.120: INFO: Pod "exec-volume-test-dynamicpv-w758": Phase="Pending", Reason="", readiness=false. Elapsed: 23.277108873s
Jun 10 08:20:54.227: INFO: Pod "exec-volume-test-dynamicpv-w758": Phase="Pending", Reason="", readiness=false. Elapsed: 25.383859575s
Jun 10 08:20:56.338: INFO: Pod "exec-volume-test-dynamicpv-w758": Phase="Succeeded", Reason="", readiness=false. Elapsed: 27.495205401s
STEP: Saw pod success
Jun 10 08:20:56.338: INFO: Pod "exec-volume-test-dynamicpv-w758" satisfied condition "Succeeded or Failed"
Jun 10 08:20:56.444: INFO: Trying to get logs from node ip-172-20-45-65.eu-west-2.compute.internal pod exec-volume-test-dynamicpv-w758 container exec-container-dynamicpv-w758: <nil>
STEP: delete the pod
Jun 10 08:20:56.973: INFO: Waiting for pod exec-volume-test-dynamicpv-w758 to disappear
Jun 10 08:20:57.078: INFO: Pod exec-volume-test-dynamicpv-w758 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-w758
Jun 10 08:20:57.078: INFO: Deleting pod "exec-volume-test-dynamicpv-w758" in namespace "volume-3890"
... skipping 87 lines ...
Jun 10 08:20:28.433: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6996-e2e-scvnc89
STEP: creating a claim
Jun 10 08:20:28.549: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-gkd7
STEP: Creating a pod to test subpath
Jun 10 08:20:28.886: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-gkd7" in namespace "provisioning-6996" to be "Succeeded or Failed"
Jun 10 08:20:28.993: INFO: Pod "pod-subpath-test-dynamicpv-gkd7": Phase="Pending", Reason="", readiness=false. Elapsed: 106.474684ms
Jun 10 08:20:31.101: INFO: Pod "pod-subpath-test-dynamicpv-gkd7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.214091004s
Jun 10 08:20:33.208: INFO: Pod "pod-subpath-test-dynamicpv-gkd7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.321370276s
Jun 10 08:20:35.316: INFO: Pod "pod-subpath-test-dynamicpv-gkd7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.429875192s
Jun 10 08:20:37.424: INFO: Pod "pod-subpath-test-dynamicpv-gkd7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.537543307s
Jun 10 08:20:39.531: INFO: Pod "pod-subpath-test-dynamicpv-gkd7": Phase="Pending", Reason="", readiness=false. Elapsed: 10.644612206s
... skipping 4 lines ...
Jun 10 08:20:50.071: INFO: Pod "pod-subpath-test-dynamicpv-gkd7": Phase="Pending", Reason="", readiness=false. Elapsed: 21.184129298s
Jun 10 08:20:52.179: INFO: Pod "pod-subpath-test-dynamicpv-gkd7": Phase="Pending", Reason="", readiness=false. Elapsed: 23.292097678s
Jun 10 08:20:54.287: INFO: Pod "pod-subpath-test-dynamicpv-gkd7": Phase="Pending", Reason="", readiness=false. Elapsed: 25.400093176s
Jun 10 08:20:56.397: INFO: Pod "pod-subpath-test-dynamicpv-gkd7": Phase="Pending", Reason="", readiness=false. Elapsed: 27.510983475s
Jun 10 08:20:58.505: INFO: Pod "pod-subpath-test-dynamicpv-gkd7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 29.618762275s
STEP: Saw pod success
Jun 10 08:20:58.505: INFO: Pod "pod-subpath-test-dynamicpv-gkd7" satisfied condition "Succeeded or Failed"
Jun 10 08:20:58.613: INFO: Trying to get logs from node ip-172-20-36-68.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-gkd7 container test-container-subpath-dynamicpv-gkd7: <nil>
STEP: delete the pod
Jun 10 08:20:59.829: INFO: Waiting for pod pod-subpath-test-dynamicpv-gkd7 to disappear
Jun 10 08:20:59.936: INFO: Pod pod-subpath-test-dynamicpv-gkd7 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-gkd7
Jun 10 08:20:59.936: INFO: Deleting pod "pod-subpath-test-dynamicpv-gkd7" in namespace "provisioning-6996"
... skipping 36 lines ...
Jun 10 08:20:31.999: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-3062bnnn2
STEP: creating a claim
Jun 10 08:20:32.118: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-m29q
STEP: Creating a pod to test exec-volume-test
Jun 10 08:20:32.442: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-m29q" in namespace "volume-3062" to be "Succeeded or Failed"
Jun 10 08:20:32.548: INFO: Pod "exec-volume-test-dynamicpv-m29q": Phase="Pending", Reason="", readiness=false. Elapsed: 105.908218ms
Jun 10 08:20:34.655: INFO: Pod "exec-volume-test-dynamicpv-m29q": Phase="Pending", Reason="", readiness=false. Elapsed: 2.213486787s
Jun 10 08:20:36.762: INFO: Pod "exec-volume-test-dynamicpv-m29q": Phase="Pending", Reason="", readiness=false. Elapsed: 4.319805478s
Jun 10 08:20:38.875: INFO: Pod "exec-volume-test-dynamicpv-m29q": Phase="Pending", Reason="", readiness=false. Elapsed: 6.432840282s
Jun 10 08:20:40.981: INFO: Pod "exec-volume-test-dynamicpv-m29q": Phase="Pending", Reason="", readiness=false. Elapsed: 8.539531741s
Jun 10 08:20:43.088: INFO: Pod "exec-volume-test-dynamicpv-m29q": Phase="Pending", Reason="", readiness=false. Elapsed: 10.64583022s
... skipping 2 lines ...
Jun 10 08:20:49.410: INFO: Pod "exec-volume-test-dynamicpv-m29q": Phase="Pending", Reason="", readiness=false. Elapsed: 16.967938701s
Jun 10 08:20:51.516: INFO: Pod "exec-volume-test-dynamicpv-m29q": Phase="Pending", Reason="", readiness=false. Elapsed: 19.074593817s
Jun 10 08:20:53.623: INFO: Pod "exec-volume-test-dynamicpv-m29q": Phase="Pending", Reason="", readiness=false. Elapsed: 21.181189831s
Jun 10 08:20:55.732: INFO: Pod "exec-volume-test-dynamicpv-m29q": Phase="Pending", Reason="", readiness=false. Elapsed: 23.28965368s
Jun 10 08:20:57.838: INFO: Pod "exec-volume-test-dynamicpv-m29q": Phase="Succeeded", Reason="", readiness=false. Elapsed: 25.396121507s
STEP: Saw pod success
Jun 10 08:20:57.838: INFO: Pod "exec-volume-test-dynamicpv-m29q" satisfied condition "Succeeded or Failed"
Jun 10 08:20:57.944: INFO: Trying to get logs from node ip-172-20-45-65.eu-west-2.compute.internal pod exec-volume-test-dynamicpv-m29q container exec-container-dynamicpv-m29q: <nil>
STEP: delete the pod
Jun 10 08:20:58.166: INFO: Waiting for pod exec-volume-test-dynamicpv-m29q to disappear
Jun 10 08:20:58.277: INFO: Pod exec-volume-test-dynamicpv-m29q no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-m29q
Jun 10 08:20:58.277: INFO: Deleting pod "exec-volume-test-dynamicpv-m29q" in namespace "volume-3062"
... skipping 156 lines ...
Jun 10 08:20:29.508: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7529ttpn9
STEP: creating a claim
Jun 10 08:20:29.615: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-r64d
STEP: Creating a pod to test atomic-volume-subpath
Jun 10 08:20:29.936: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-r64d" in namespace "provisioning-7529" to be "Succeeded or Failed"
Jun 10 08:20:30.042: INFO: Pod "pod-subpath-test-dynamicpv-r64d": Phase="Pending", Reason="", readiness=false. Elapsed: 106.13939ms
Jun 10 08:20:32.153: INFO: Pod "pod-subpath-test-dynamicpv-r64d": Phase="Pending", Reason="", readiness=false. Elapsed: 2.217879263s
Jun 10 08:20:34.262: INFO: Pod "pod-subpath-test-dynamicpv-r64d": Phase="Pending", Reason="", readiness=false. Elapsed: 4.326139534s
Jun 10 08:20:36.369: INFO: Pod "pod-subpath-test-dynamicpv-r64d": Phase="Pending", Reason="", readiness=false. Elapsed: 6.432927637s
Jun 10 08:20:38.475: INFO: Pod "pod-subpath-test-dynamicpv-r64d": Phase="Pending", Reason="", readiness=false. Elapsed: 8.539632938s
Jun 10 08:20:40.582: INFO: Pod "pod-subpath-test-dynamicpv-r64d": Phase="Pending", Reason="", readiness=false. Elapsed: 10.645999522s
... skipping 10 lines ...
Jun 10 08:21:03.760: INFO: Pod "pod-subpath-test-dynamicpv-r64d": Phase="Running", Reason="", readiness=true. Elapsed: 33.824255709s
Jun 10 08:21:05.866: INFO: Pod "pod-subpath-test-dynamicpv-r64d": Phase="Running", Reason="", readiness=true. Elapsed: 35.930729931s
Jun 10 08:21:07.973: INFO: Pod "pod-subpath-test-dynamicpv-r64d": Phase="Running", Reason="", readiness=true. Elapsed: 38.037108728s
Jun 10 08:21:10.079: INFO: Pod "pod-subpath-test-dynamicpv-r64d": Phase="Running", Reason="", readiness=true. Elapsed: 40.143663515s
Jun 10 08:21:12.186: INFO: Pod "pod-subpath-test-dynamicpv-r64d": Phase="Succeeded", Reason="", readiness=false. Elapsed: 42.250740524s
STEP: Saw pod success
Jun 10 08:21:12.186: INFO: Pod "pod-subpath-test-dynamicpv-r64d" satisfied condition "Succeeded or Failed"
Jun 10 08:21:12.294: INFO: Trying to get logs from node ip-172-20-36-68.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-r64d container test-container-subpath-dynamicpv-r64d: <nil>
STEP: delete the pod
Jun 10 08:21:12.525: INFO: Waiting for pod pod-subpath-test-dynamicpv-r64d to disappear
Jun 10 08:21:12.631: INFO: Pod pod-subpath-test-dynamicpv-r64d no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-r64d
Jun 10 08:21:12.631: INFO: Deleting pod "pod-subpath-test-dynamicpv-r64d" in namespace "provisioning-7529"
... skipping 198 lines ...
Jun 10 08:20:29.660: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-7651xpbv9
STEP: creating a claim
Jun 10 08:20:29.768: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-tl82
STEP: Creating a pod to test exec-volume-test
Jun 10 08:20:30.095: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-tl82" in namespace "volume-7651" to be "Succeeded or Failed"
Jun 10 08:20:30.202: INFO: Pod "exec-volume-test-dynamicpv-tl82": Phase="Pending", Reason="", readiness=false. Elapsed: 106.932498ms
Jun 10 08:20:32.310: INFO: Pod "exec-volume-test-dynamicpv-tl82": Phase="Pending", Reason="", readiness=false. Elapsed: 2.21522699s
Jun 10 08:20:34.417: INFO: Pod "exec-volume-test-dynamicpv-tl82": Phase="Pending", Reason="", readiness=false. Elapsed: 4.322222978s
Jun 10 08:20:36.525: INFO: Pod "exec-volume-test-dynamicpv-tl82": Phase="Pending", Reason="", readiness=false. Elapsed: 6.430035972s
Jun 10 08:20:38.635: INFO: Pod "exec-volume-test-dynamicpv-tl82": Phase="Pending", Reason="", readiness=false. Elapsed: 8.539766837s
Jun 10 08:20:40.742: INFO: Pod "exec-volume-test-dynamicpv-tl82": Phase="Pending", Reason="", readiness=false. Elapsed: 10.646884459s
... skipping 5 lines ...
Jun 10 08:20:53.390: INFO: Pod "exec-volume-test-dynamicpv-tl82": Phase="Pending", Reason="", readiness=false. Elapsed: 23.294858699s
Jun 10 08:20:55.502: INFO: Pod "exec-volume-test-dynamicpv-tl82": Phase="Pending", Reason="", readiness=false. Elapsed: 25.406343614s
Jun 10 08:20:57.609: INFO: Pod "exec-volume-test-dynamicpv-tl82": Phase="Pending", Reason="", readiness=false. Elapsed: 27.513333313s
Jun 10 08:20:59.717: INFO: Pod "exec-volume-test-dynamicpv-tl82": Phase="Pending", Reason="", readiness=false. Elapsed: 29.621767067s
Jun 10 08:21:01.825: INFO: Pod "exec-volume-test-dynamicpv-tl82": Phase="Succeeded", Reason="", readiness=false. Elapsed: 31.729729236s
STEP: Saw pod success
Jun 10 08:21:01.825: INFO: Pod "exec-volume-test-dynamicpv-tl82" satisfied condition "Succeeded or Failed"
Jun 10 08:21:01.932: INFO: Trying to get logs from node ip-172-20-59-227.eu-west-2.compute.internal pod exec-volume-test-dynamicpv-tl82 container exec-container-dynamicpv-tl82: <nil>
STEP: delete the pod
Jun 10 08:21:02.168: INFO: Waiting for pod exec-volume-test-dynamicpv-tl82 to disappear
Jun 10 08:21:02.275: INFO: Pod exec-volume-test-dynamicpv-tl82 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-tl82
Jun 10 08:21:02.275: INFO: Deleting pod "exec-volume-test-dynamicpv-tl82" in namespace "volume-7651"
... skipping 134 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.Y1KozJqJu/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.Y1KozJqJu/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.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 102 lines ...
Jun 10 08:20:33.073: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4119-e2e-scqb82x
STEP: creating a claim
Jun 10 08:20:33.181: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-5q9d
STEP: Creating a pod to test multi_subpath
Jun 10 08:20:33.504: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-5q9d" in namespace "provisioning-4119" to be "Succeeded or Failed"
Jun 10 08:20:33.611: INFO: Pod "pod-subpath-test-dynamicpv-5q9d": Phase="Pending", Reason="", readiness=false. Elapsed: 106.902964ms
Jun 10 08:20:35.720: INFO: Pod "pod-subpath-test-dynamicpv-5q9d": Phase="Pending", Reason="", readiness=false. Elapsed: 2.216599225s
Jun 10 08:20:37.828: INFO: Pod "pod-subpath-test-dynamicpv-5q9d": Phase="Pending", Reason="", readiness=false. Elapsed: 4.324112096s
Jun 10 08:20:39.935: INFO: Pod "pod-subpath-test-dynamicpv-5q9d": Phase="Pending", Reason="", readiness=false. Elapsed: 6.431094401s
Jun 10 08:20:42.046: INFO: Pod "pod-subpath-test-dynamicpv-5q9d": Phase="Pending", Reason="", readiness=false. Elapsed: 8.54272772s
Jun 10 08:20:44.154: INFO: Pod "pod-subpath-test-dynamicpv-5q9d": Phase="Pending", Reason="", readiness=false. Elapsed: 10.650444854s
... skipping 5 lines ...
Jun 10 08:20:56.799: INFO: Pod "pod-subpath-test-dynamicpv-5q9d": Phase="Pending", Reason="", readiness=false. Elapsed: 23.29577504s
Jun 10 08:20:58.907: INFO: Pod "pod-subpath-test-dynamicpv-5q9d": Phase="Pending", Reason="", readiness=false. Elapsed: 25.403306527s
Jun 10 08:21:01.015: INFO: Pod "pod-subpath-test-dynamicpv-5q9d": Phase="Pending", Reason="", readiness=false. Elapsed: 27.511122994s
Jun 10 08:21:03.123: INFO: Pod "pod-subpath-test-dynamicpv-5q9d": Phase="Pending", Reason="", readiness=false. Elapsed: 29.619630558s
Jun 10 08:21:05.230: INFO: Pod "pod-subpath-test-dynamicpv-5q9d": Phase="Succeeded", Reason="", readiness=false. Elapsed: 31.725982628s
STEP: Saw pod success
Jun 10 08:21:05.230: INFO: Pod "pod-subpath-test-dynamicpv-5q9d" satisfied condition "Succeeded or Failed"
Jun 10 08:21:05.336: INFO: Trying to get logs from node ip-172-20-59-227.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-5q9d container test-container-subpath-dynamicpv-5q9d: <nil>
STEP: delete the pod
Jun 10 08:21:05.563: INFO: Waiting for pod pod-subpath-test-dynamicpv-5q9d to disappear
Jun 10 08:21:05.669: INFO: Pod pod-subpath-test-dynamicpv-5q9d no longer exists
STEP: Deleting pod
Jun 10 08:21:05.669: INFO: Deleting pod "pod-subpath-test-dynamicpv-5q9d" in namespace "provisioning-4119"
... skipping 34 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 08:21:43.815: 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.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 10 08:21:44.356: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 10 08:21:45.091: INFO: Successfully created a new PD: "aws://eu-west-2a/vol-0460bb28994b9ef8b".
Jun 10 08:21:45.091: INFO: Creating resource for pre-provisioned PV
Jun 10 08:21:45.091: INFO: Creating PVC and PV
... skipping 8 lines ...
Jun 10 08:21:56.031: INFO: PersistentVolumeClaim pvc-gtxdf found but phase is Pending instead of Bound.
Jun 10 08:21:58.139: INFO: PersistentVolumeClaim pvc-gtxdf found but phase is Pending instead of Bound.
Jun 10 08:22:00.251: INFO: PersistentVolumeClaim pvc-gtxdf found and phase=Bound (14.866195621s)
Jun 10 08:22:00.251: INFO: Waiting up to 3m0s for PersistentVolume aws-4wmv4 to have phase Bound
Jun 10 08:22:00.361: INFO: PersistentVolume aws-4wmv4 found and phase=Bound (109.555817ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 10 08:22:03.001: INFO: Deleting pod "pod-fa121280-393a-415d-87ed-a76a649e273e" in namespace "volumemode-8198"
Jun 10 08:22:03.108: INFO: Wait up to 5m0s for pod "pod-fa121280-393a-415d-87ed-a76a649e273e" to be fully deleted
STEP: Deleting pv and pvc
Jun 10 08:22:07.320: INFO: Deleting PersistentVolumeClaim "pvc-gtxdf"
Jun 10 08:22:07.427: INFO: Deleting PersistentVolume "aws-4wmv4"
Jun 10 08:22:07.746: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0460bb28994b9ef8b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0460bb28994b9ef8b is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: d4c88d74-489c-4bbd-b568-0a51ddb87ce0
Jun 10 08:22:13.343: INFO: Successfully deleted PD "aws://eu-west-2a/vol-0460bb28994b9ef8b".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 10 08:22:13.343: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-8198" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Y1KozJqJu/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Y1KozJqJu/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
    /tmp/kops.Y1KozJqJu/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.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [sig-storage] Storage Policy Based Volume Provisioning [Feature:vsphere]
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 08:22:13.560: INFO: >>> kubeConfig: /root/.kube/config
... skipping 240 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Y1KozJqJu/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Y1KozJqJu/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.Y1KozJqJu/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.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.Y1KozJqJu/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.Y1KozJqJu/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.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 195 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 08:22:20.256: 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.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 10 08:22:20.786: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 10 08:22:21.533: INFO: Successfully created a new PD: "aws://eu-west-2a/vol-0dd537322889e631c".
Jun 10 08:22:21.533: INFO: Creating resource for pre-provisioned PV
Jun 10 08:22:21.533: INFO: Creating PVC and PV
... skipping 5 lines ...
Jun 10 08:22:26.142: INFO: PersistentVolumeClaim pvc-s5skf found but phase is Pending instead of Bound.
Jun 10 08:22:28.249: INFO: PersistentVolumeClaim pvc-s5skf found but phase is Pending instead of Bound.
Jun 10 08:22:30.356: INFO: PersistentVolumeClaim pvc-s5skf found and phase=Bound (8.533046552s)
Jun 10 08:22:30.356: INFO: Waiting up to 3m0s for PersistentVolume aws-g4p9f to have phase Bound
Jun 10 08:22:30.502: INFO: PersistentVolume aws-g4p9f found and phase=Bound (146.085701ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 10 08:22:33.139: INFO: Deleting pod "pod-e7f2cb7f-96d9-46b6-a166-a77c3c8a19fa" in namespace "volumemode-4998"
Jun 10 08:22:33.245: INFO: Wait up to 5m0s for pod "pod-e7f2cb7f-96d9-46b6-a166-a77c3c8a19fa" to be fully deleted
STEP: Deleting pv and pvc
Jun 10 08:22:37.457: INFO: Deleting PersistentVolumeClaim "pvc-s5skf"
Jun 10 08:22:37.564: INFO: Deleting PersistentVolume "aws-g4p9f"
Jun 10 08:22:37.887: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0dd537322889e631c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0dd537322889e631c is currently attached to i-0ff665d16f07b5536
	status code: 400, request id: 250ac4ea-8698-4697-9b4d-d9b7f30725e1
Jun 10 08:22:43.503: INFO: Successfully deleted PD "aws://eu-west-2a/vol-0dd537322889e631c".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 10 08:22:43.503: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-4998" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Y1KozJqJu/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Y1KozJqJu/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
    /tmp/kops.Y1KozJqJu/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.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
S
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumes
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
... skipping 94 lines ...
Jun 10 08:22:15.596: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-209j4q5v
STEP: creating a claim
Jun 10 08:22:15.713: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Jun 10 08:22:15.929: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 10 08:22:16.145: INFO: Error updating pvc awslkptj: PersistentVolumeClaim "awslkptj" 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-209j4q5v",
  	... // 2 identical fields
  }

Jun 10 08:22:18.358: INFO: Error updating pvc awslkptj: PersistentVolumeClaim "awslkptj" 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-209j4q5v",
  	... // 2 identical fields
  }

Jun 10 08:22:20.362: INFO: Error updating pvc awslkptj: PersistentVolumeClaim "awslkptj" 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-209j4q5v",
  	... // 2 identical fields
  }

Jun 10 08:22:22.358: INFO: Error updating pvc awslkptj: PersistentVolumeClaim "awslkptj" 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-209j4q5v",
  	... // 2 identical fields
  }

Jun 10 08:22:24.364: INFO: Error updating pvc awslkptj: PersistentVolumeClaim "awslkptj" 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-209j4q5v",
  	... // 2 identical fields
  }

Jun 10 08:22:26.358: INFO: Error updating pvc awslkptj: PersistentVolumeClaim "awslkptj" 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-209j4q5v",
  	... // 2 identical fields
  }

Jun 10 08:22:28.358: INFO: Error updating pvc awslkptj: PersistentVolumeClaim "awslkptj" 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-209j4q5v",
  	... // 2 identical fields
  }

Jun 10 08:22:30.360: INFO: Error updating pvc awslkptj: PersistentVolumeClaim "awslkptj" 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-209j4q5v",
  	... // 2 identical fields
  }

Jun 10 08:22:32.359: INFO: Error updating pvc awslkptj: PersistentVolumeClaim "awslkptj" 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-209j4q5v",
  	... // 2 identical fields
  }

Jun 10 08:22:34.360: INFO: Error updating pvc awslkptj: PersistentVolumeClaim "awslkptj" 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-209j4q5v",
  	... // 2 identical fields
  }

Jun 10 08:22:36.361: INFO: Error updating pvc awslkptj: PersistentVolumeClaim "awslkptj" 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-209j4q5v",
  	... // 2 identical fields
  }

Jun 10 08:22:38.358: INFO: Error updating pvc awslkptj: PersistentVolumeClaim "awslkptj" 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-209j4q5v",
  	... // 2 identical fields
  }

Jun 10 08:22:40.359: INFO: Error updating pvc awslkptj: PersistentVolumeClaim "awslkptj" 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-209j4q5v",
  	... // 2 identical fields
  }

Jun 10 08:22:42.360: INFO: Error updating pvc awslkptj: PersistentVolumeClaim "awslkptj" 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-209j4q5v",
  	... // 2 identical fields
  }

Jun 10 08:22:44.359: INFO: Error updating pvc awslkptj: PersistentVolumeClaim "awslkptj" 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-209j4q5v",
  	... // 2 identical fields
  }

Jun 10 08:22:46.364: INFO: Error updating pvc awslkptj: PersistentVolumeClaim "awslkptj" 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-209j4q5v",
  	... // 2 identical fields
  }

Jun 10 08:22:46.579: INFO: Error updating pvc awslkptj: PersistentVolumeClaim "awslkptj" 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 190 lines ...
Jun 10 08:22:07.345: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6487m5sc4
STEP: creating a claim
Jun 10 08:22:07.451: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-vnp4
STEP: Creating a pod to test multi_subpath
Jun 10 08:22:07.774: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-vnp4" in namespace "provisioning-6487" to be "Succeeded or Failed"
Jun 10 08:22:07.879: INFO: Pod "pod-subpath-test-dynamicpv-vnp4": Phase="Pending", Reason="", readiness=false. Elapsed: 105.854812ms
Jun 10 08:22:09.988: INFO: Pod "pod-subpath-test-dynamicpv-vnp4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.213907266s
Jun 10 08:22:12.094: INFO: Pod "pod-subpath-test-dynamicpv-vnp4": Phase="Pending", Reason="", readiness=false. Elapsed: 4.320783085s
Jun 10 08:22:14.202: INFO: Pod "pod-subpath-test-dynamicpv-vnp4": Phase="Pending", Reason="", readiness=false. Elapsed: 6.428456372s
Jun 10 08:22:16.308: INFO: Pod "pod-subpath-test-dynamicpv-vnp4": Phase="Pending", Reason="", readiness=false. Elapsed: 8.534411836s
Jun 10 08:22:18.422: INFO: Pod "pod-subpath-test-dynamicpv-vnp4": Phase="Pending", Reason="", readiness=false. Elapsed: 10.648454242s
Jun 10 08:22:20.529: INFO: Pod "pod-subpath-test-dynamicpv-vnp4": Phase="Pending", Reason="", readiness=false. Elapsed: 12.755077397s
Jun 10 08:22:22.639: INFO: Pod "pod-subpath-test-dynamicpv-vnp4": Phase="Pending", Reason="", readiness=false. Elapsed: 14.865785674s
Jun 10 08:22:24.751: INFO: Pod "pod-subpath-test-dynamicpv-vnp4": Phase="Pending", Reason="", readiness=false. Elapsed: 16.977257724s
Jun 10 08:22:26.857: INFO: Pod "pod-subpath-test-dynamicpv-vnp4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.082918751s
STEP: Saw pod success
Jun 10 08:22:26.857: INFO: Pod "pod-subpath-test-dynamicpv-vnp4" satisfied condition "Succeeded or Failed"
Jun 10 08:22:26.962: INFO: Trying to get logs from node ip-172-20-59-227.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-vnp4 container test-container-subpath-dynamicpv-vnp4: <nil>
STEP: delete the pod
Jun 10 08:22:27.189: INFO: Waiting for pod pod-subpath-test-dynamicpv-vnp4 to disappear
Jun 10 08:22:27.295: INFO: Pod pod-subpath-test-dynamicpv-vnp4 no longer exists
STEP: Deleting pod
Jun 10 08:22:27.295: INFO: Deleting pod "pod-subpath-test-dynamicpv-vnp4" in namespace "provisioning-6487"
... skipping 1576 lines ...
Jun 10 08:22:44.260: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-5317-e2e-scsh2js
STEP: creating a claim
Jun 10 08:22:44.367: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Jun 10 08:22:44.581: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 10 08:22:44.794: INFO: Error updating pvc ebs.csi.aws.com9lxfk: PersistentVolumeClaim "ebs.csi.aws.com9lxfk" 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-5317-e2e-scsh2js",
  	... // 2 identical fields
  }

Jun 10 08:22:47.009: INFO: Error updating pvc ebs.csi.aws.com9lxfk: PersistentVolumeClaim "ebs.csi.aws.com9lxfk" 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-5317-e2e-scsh2js",
  	... // 2 identical fields
  }

Jun 10 08:22:49.011: INFO: Error updating pvc ebs.csi.aws.com9lxfk: PersistentVolumeClaim "ebs.csi.aws.com9lxfk" 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-5317-e2e-scsh2js",
  	... // 2 identical fields
  }

Jun 10 08:22:51.009: INFO: Error updating pvc ebs.csi.aws.com9lxfk: PersistentVolumeClaim "ebs.csi.aws.com9lxfk" 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-5317-e2e-scsh2js",
  	... // 2 identical fields
  }

Jun 10 08:22:53.011: INFO: Error updating pvc ebs.csi.aws.com9lxfk: PersistentVolumeClaim "ebs.csi.aws.com9lxfk" 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-5317-e2e-scsh2js",
  	... // 2 identical fields
  }

Jun 10 08:22:55.017: INFO: Error updating pvc ebs.csi.aws.com9lxfk: PersistentVolumeClaim "ebs.csi.aws.com9lxfk" 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-5317-e2e-scsh2js",
  	... // 2 identical fields
  }

Jun 10 08:22:57.012: INFO: Error updating pvc ebs.csi.aws.com9lxfk: PersistentVolumeClaim "ebs.csi.aws.com9lxfk" 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-5317-e2e-scsh2js",
  	... // 2 identical fields
  }

Jun 10 08:22:59.010: INFO: Error updating pvc ebs.csi.aws.com9lxfk: PersistentVolumeClaim "ebs.csi.aws.com9lxfk" 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-5317-e2e-scsh2js",
  	... // 2 identical fields
  }

Jun 10 08:23:01.009: INFO: Error updating pvc ebs.csi.aws.com9lxfk: PersistentVolumeClaim "ebs.csi.aws.com9lxfk" 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-5317-e2e-scsh2js",
  	... // 2 identical fields
  }

Jun 10 08:23:03.008: INFO: Error updating pvc ebs.csi.aws.com9lxfk: PersistentVolumeClaim "ebs.csi.aws.com9lxfk" 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-5317-e2e-scsh2js",
  	... // 2 identical fields
  }

Jun 10 08:23:05.008: INFO: Error updating pvc ebs.csi.aws.com9lxfk: PersistentVolumeClaim "ebs.csi.aws.com9lxfk" 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-5317-e2e-scsh2js",
  	... // 2 identical fields
  }

Jun 10 08:23:07.007: INFO: Error updating pvc ebs.csi.aws.com9lxfk: PersistentVolumeClaim "ebs.csi.aws.com9lxfk" 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-5317-e2e-scsh2js",
  	... // 2 identical fields
  }

Jun 10 08:23:09.009: INFO: Error updating pvc ebs.csi.aws.com9lxfk: PersistentVolumeClaim "ebs.csi.aws.com9lxfk" 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-5317-e2e-scsh2js",
  	... // 2 identical fields
  }

Jun 10 08:23:11.007: INFO: Error updating pvc ebs.csi.aws.com9lxfk: PersistentVolumeClaim "ebs.csi.aws.com9lxfk" 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-5317-e2e-scsh2js",
  	... // 2 identical fields
  }

Jun 10 08:23:13.008: INFO: Error updating pvc ebs.csi.aws.com9lxfk: PersistentVolumeClaim "ebs.csi.aws.com9lxfk" 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-5317-e2e-scsh2js",
  	... // 2 identical fields
  }

Jun 10 08:23:15.009: INFO: Error updating pvc ebs.csi.aws.com9lxfk: PersistentVolumeClaim "ebs.csi.aws.com9lxfk" 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-5317-e2e-scsh2js",
  	... // 2 identical fields
  }

Jun 10 08:23:15.224: INFO: Error updating pvc ebs.csi.aws.com9lxfk: PersistentVolumeClaim "ebs.csi.aws.com9lxfk" 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 39 lines ...
Jun 10 08:22:13.454: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6922-e2e-scw7xvm
STEP: creating a claim
Jun 10 08:22:13.560: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-zwjh
STEP: Creating a pod to test subpath
Jun 10 08:22:13.884: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-zwjh" in namespace "provisioning-6922" to be "Succeeded or Failed"
Jun 10 08:22:13.991: INFO: Pod "pod-subpath-test-dynamicpv-zwjh": Phase="Pending", Reason="", readiness=false. Elapsed: 106.321683ms
Jun 10 08:22:16.097: INFO: Pod "pod-subpath-test-dynamicpv-zwjh": Phase="Pending", Reason="", readiness=false. Elapsed: 2.213107663s
Jun 10 08:22:18.204: INFO: Pod "pod-subpath-test-dynamicpv-zwjh": Phase="Pending", Reason="", readiness=false. Elapsed: 4.319969058s
Jun 10 08:22:20.311: INFO: Pod "pod-subpath-test-dynamicpv-zwjh": Phase="Pending", Reason="", readiness=false. Elapsed: 6.426686035s
Jun 10 08:22:22.419: INFO: Pod "pod-subpath-test-dynamicpv-zwjh": Phase="Pending", Reason="", readiness=false. Elapsed: 8.53481149s
Jun 10 08:22:24.529: INFO: Pod "pod-subpath-test-dynamicpv-zwjh": Phase="Pending", Reason="", readiness=false. Elapsed: 10.644330866s
... skipping 2 lines ...
Jun 10 08:22:30.850: INFO: Pod "pod-subpath-test-dynamicpv-zwjh": Phase="Pending", Reason="", readiness=false. Elapsed: 16.965833461s
Jun 10 08:22:32.957: INFO: Pod "pod-subpath-test-dynamicpv-zwjh": Phase="Pending", Reason="", readiness=false. Elapsed: 19.073132977s
Jun 10 08:22:35.065: INFO: Pod "pod-subpath-test-dynamicpv-zwjh": Phase="Pending", Reason="", readiness=false. Elapsed: 21.180619996s
Jun 10 08:22:37.171: INFO: Pod "pod-subpath-test-dynamicpv-zwjh": Phase="Pending", Reason="", readiness=false. Elapsed: 23.287090496s
Jun 10 08:22:39.280: INFO: Pod "pod-subpath-test-dynamicpv-zwjh": Phase="Succeeded", Reason="", readiness=false. Elapsed: 25.395361187s
STEP: Saw pod success
Jun 10 08:22:39.280: INFO: Pod "pod-subpath-test-dynamicpv-zwjh" satisfied condition "Succeeded or Failed"
Jun 10 08:22:39.386: INFO: Trying to get logs from node ip-172-20-59-227.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-zwjh container test-container-volume-dynamicpv-zwjh: <nil>
STEP: delete the pod
Jun 10 08:22:39.610: INFO: Waiting for pod pod-subpath-test-dynamicpv-zwjh to disappear
Jun 10 08:22:39.715: INFO: Pod pod-subpath-test-dynamicpv-zwjh no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-zwjh
Jun 10 08:22:39.715: INFO: Deleting pod "pod-subpath-test-dynamicpv-zwjh" in namespace "provisioning-6922"
... skipping 30 lines ...
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 08:23:15.800: 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.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Jun 10 08:23:16.438: INFO: found topology map[topology.kubernetes.io/zone:eu-west-2a]
Jun 10 08:23:16.438: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 10 08:23:16.438: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Y1KozJqJu/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Y1KozJqJu/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (delayed binding)] topology
    /tmp/kops.Y1KozJqJu/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.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 10 lines ...
Jun 10 08:22:53.462: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 10 08:22:54.206: INFO: Successfully created a new PD: "aws://eu-west-2a/vol-07685e442db43ae43".
Jun 10 08:22:54.206: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-qs64
STEP: Creating a pod to test exec-volume-test
Jun 10 08:22:54.314: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-qs64" in namespace "volume-2796" to be "Succeeded or Failed"
Jun 10 08:22:54.420: INFO: Pod "exec-volume-test-inlinevolume-qs64": Phase="Pending", Reason="", readiness=false. Elapsed: 106.207364ms
Jun 10 08:22:56.526: INFO: Pod "exec-volume-test-inlinevolume-qs64": Phase="Pending", Reason="", readiness=false. Elapsed: 2.212081703s
Jun 10 08:22:58.634: INFO: Pod "exec-volume-test-inlinevolume-qs64": Phase="Pending", Reason="", readiness=false. Elapsed: 4.320345169s
Jun 10 08:23:00.741: INFO: Pod "exec-volume-test-inlinevolume-qs64": Phase="Pending", Reason="", readiness=false. Elapsed: 6.427073054s
Jun 10 08:23:02.847: INFO: Pod "exec-volume-test-inlinevolume-qs64": Phase="Pending", Reason="", readiness=false. Elapsed: 8.533254136s
Jun 10 08:23:04.953: INFO: Pod "exec-volume-test-inlinevolume-qs64": Phase="Pending", Reason="", readiness=false. Elapsed: 10.639729702s
Jun 10 08:23:07.064: INFO: Pod "exec-volume-test-inlinevolume-qs64": Phase="Pending", Reason="", readiness=false. Elapsed: 12.749846747s
Jun 10 08:23:09.171: INFO: Pod "exec-volume-test-inlinevolume-qs64": Phase="Pending", Reason="", readiness=false. Elapsed: 14.856866956s
Jun 10 08:23:11.278: INFO: Pod "exec-volume-test-inlinevolume-qs64": Phase="Pending", Reason="", readiness=false. Elapsed: 16.963847898s
Jun 10 08:23:13.385: INFO: Pod "exec-volume-test-inlinevolume-qs64": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.071079833s
STEP: Saw pod success
Jun 10 08:23:13.385: INFO: Pod "exec-volume-test-inlinevolume-qs64" satisfied condition "Succeeded or Failed"
Jun 10 08:23:13.491: INFO: Trying to get logs from node ip-172-20-45-65.eu-west-2.compute.internal pod exec-volume-test-inlinevolume-qs64 container exec-container-inlinevolume-qs64: <nil>
STEP: delete the pod
Jun 10 08:23:13.714: INFO: Waiting for pod exec-volume-test-inlinevolume-qs64 to disappear
Jun 10 08:23:13.821: INFO: Pod exec-volume-test-inlinevolume-qs64 no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-qs64
Jun 10 08:23:13.821: INFO: Deleting pod "exec-volume-test-inlinevolume-qs64" in namespace "volume-2796"
Jun 10 08:23:14.138: INFO: Couldn't delete PD "aws://eu-west-2a/vol-07685e442db43ae43", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07685e442db43ae43 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: 9e004b89-2271-4f3f-b51e-d3df35286c12
Jun 10 08:23:19.713: INFO: Couldn't delete PD "aws://eu-west-2a/vol-07685e442db43ae43", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07685e442db43ae43 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: 6660ded6-c05e-46a1-9ffc-b03598de1042
Jun 10 08:23:25.248: INFO: Successfully deleted PD "aws://eu-west-2a/vol-07685e442db43ae43".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 10 08:23:25.248: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-2796" for this suite.
... skipping 32 lines ...
Jun 10 08:22:43.846: INFO: PersistentVolumeClaim pvc-ww226 found but phase is Pending instead of Bound.
Jun 10 08:22:45.953: INFO: PersistentVolumeClaim pvc-ww226 found and phase=Bound (6.428816445s)
Jun 10 08:22:45.953: INFO: Waiting up to 3m0s for PersistentVolume aws-s8c5v to have phase Bound
Jun 10 08:22:46.061: INFO: PersistentVolume aws-s8c5v found and phase=Bound (107.976157ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-cjrg
STEP: Creating a pod to test exec-volume-test
Jun 10 08:22:46.396: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-cjrg" in namespace "volume-9279" to be "Succeeded or Failed"
Jun 10 08:22:46.504: INFO: Pod "exec-volume-test-preprovisionedpv-cjrg": Phase="Pending", Reason="", readiness=false. Elapsed: 108.474197ms
Jun 10 08:22:48.613: INFO: Pod "exec-volume-test-preprovisionedpv-cjrg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.216566427s
Jun 10 08:22:50.720: INFO: Pod "exec-volume-test-preprovisionedpv-cjrg": Phase="Pending", Reason="", readiness=false. Elapsed: 4.324234119s
Jun 10 08:22:52.832: INFO: Pod "exec-volume-test-preprovisionedpv-cjrg": Phase="Pending", Reason="", readiness=false. Elapsed: 6.436365007s
Jun 10 08:22:54.941: INFO: Pod "exec-volume-test-preprovisionedpv-cjrg": Phase="Pending", Reason="", readiness=false. Elapsed: 8.544586903s
Jun 10 08:22:57.048: INFO: Pod "exec-volume-test-preprovisionedpv-cjrg": Phase="Pending", Reason="", readiness=false. Elapsed: 10.651809592s
Jun 10 08:22:59.165: INFO: Pod "exec-volume-test-preprovisionedpv-cjrg": Phase="Pending", Reason="", readiness=false. Elapsed: 12.769470386s
Jun 10 08:23:01.273: INFO: Pod "exec-volume-test-preprovisionedpv-cjrg": Phase="Pending", Reason="", readiness=false. Elapsed: 14.876900316s
Jun 10 08:23:03.381: INFO: Pod "exec-volume-test-preprovisionedpv-cjrg": Phase="Pending", Reason="", readiness=false. Elapsed: 16.984732907s
Jun 10 08:23:05.488: INFO: Pod "exec-volume-test-preprovisionedpv-cjrg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.091972825s
STEP: Saw pod success
Jun 10 08:23:05.488: INFO: Pod "exec-volume-test-preprovisionedpv-cjrg" satisfied condition "Succeeded or Failed"
Jun 10 08:23:05.595: INFO: Trying to get logs from node ip-172-20-45-65.eu-west-2.compute.internal pod exec-volume-test-preprovisionedpv-cjrg container exec-container-preprovisionedpv-cjrg: <nil>
STEP: delete the pod
Jun 10 08:23:05.828: INFO: Waiting for pod exec-volume-test-preprovisionedpv-cjrg to disappear
Jun 10 08:23:05.935: INFO: Pod exec-volume-test-preprovisionedpv-cjrg no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-cjrg
Jun 10 08:23:05.935: INFO: Deleting pod "exec-volume-test-preprovisionedpv-cjrg" in namespace "volume-9279"
STEP: Deleting pv and pvc
Jun 10 08:23:06.041: INFO: Deleting PersistentVolumeClaim "pvc-ww226"
Jun 10 08:23:06.148: INFO: Deleting PersistentVolume "aws-s8c5v"
Jun 10 08:23:06.542: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0b2de630492883e88", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0b2de630492883e88 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: 7f06e749-05ad-4960-ba62-cdebd8ad9f22
Jun 10 08:23:12.139: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0b2de630492883e88", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0b2de630492883e88 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: 30b4bbc0-422e-4cda-b2a3-aeb3159e2f9f
Jun 10 08:23:17.700: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0b2de630492883e88", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0b2de630492883e88 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: a29c1a38-9a53-4db9-bfba-45aaf4f0ec84
Jun 10 08:23:23.274: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0b2de630492883e88", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0b2de630492883e88 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: cfc07a8b-c553-44e4-a3b6-11cdb89a3358
Jun 10 08:23:28.866: INFO: Successfully deleted PD "aws://eu-west-2a/vol-0b2de630492883e88".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 10 08:23:28.867: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-9279" for this suite.
... skipping 213 lines ...
STEP: Deleting pod hostexec-ip-172-20-36-68.eu-west-2.compute.internal-rvgtw in namespace volumemode-9465
Jun 10 08:23:07.576: INFO: Deleting pod "pod-01bd946a-e8a5-4393-afaa-f05adb80bde8" in namespace "volumemode-9465"
Jun 10 08:23:07.684: INFO: Wait up to 5m0s for pod "pod-01bd946a-e8a5-4393-afaa-f05adb80bde8" to be fully deleted
STEP: Deleting pv and pvc
Jun 10 08:23:17.898: INFO: Deleting PersistentVolumeClaim "pvc-jxxds"
Jun 10 08:23:18.006: INFO: Deleting PersistentVolume "aws-94rnm"
Jun 10 08:23:18.351: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0a194e62ff4bcd2fc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a194e62ff4bcd2fc is currently attached to i-0ff665d16f07b5536
	status code: 400, request id: a14b3fc4-2fd2-4c81-8d59-a67030fa9641
Jun 10 08:23:23.913: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0a194e62ff4bcd2fc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a194e62ff4bcd2fc is currently attached to i-0ff665d16f07b5536
	status code: 400, request id: c46c7a47-233c-43e1-b77d-bd7ea1099737
Jun 10 08:23:29.502: INFO: Successfully deleted PD "aws://eu-west-2a/vol-0a194e62ff4bcd2fc".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 10 08:23:29.502: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-9465" for this suite.
... skipping 325 lines ...
Jun 10 08:23:47.388: INFO: Waiting for pod aws-client to disappear
Jun 10 08:23:47.496: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 10 08:23:47.496: INFO: Deleting PersistentVolumeClaim "pvc-zcv6q"
Jun 10 08:23:47.604: INFO: Deleting PersistentVolume "aws-q7ff5"
Jun 10 08:23:48.299: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0b8cc6807650e89fc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0b8cc6807650e89fc is currently attached to i-0ff665d16f07b5536
	status code: 400, request id: a587eac0-09a7-42ca-b75b-49d885681a2e
Jun 10 08:23:53.907: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0b8cc6807650e89fc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0b8cc6807650e89fc is currently attached to i-0ff665d16f07b5536
	status code: 400, request id: e2d06634-ce46-4189-b2f2-1ba43000c44a
Jun 10 08:23:59.479: INFO: Successfully deleted PD "aws://eu-west-2a/vol-0b8cc6807650e89fc".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 10 08:23:59.479: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-3174" for this suite.
... skipping 279 lines ...
Jun 10 08:23:53.704: INFO: Pod aws-client still exists
Jun 10 08:23:55.598: INFO: Waiting for pod aws-client to disappear
Jun 10 08:23:55.704: INFO: Pod aws-client still exists
Jun 10 08:23:57.596: INFO: Waiting for pod aws-client to disappear
Jun 10 08:23:57.705: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun 10 08:23:58.264: INFO: Couldn't delete PD "aws://eu-west-2a/vol-00c19c6b94797c7cb", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00c19c6b94797c7cb is currently attached to i-0b68877733b8749cb
	status code: 400, request id: bc0a4f82-96a1-457c-bed7-d0540f40c936
Jun 10 08:24:03.793: INFO: Couldn't delete PD "aws://eu-west-2a/vol-00c19c6b94797c7cb", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00c19c6b94797c7cb is currently attached to i-0b68877733b8749cb
	status code: 400, request id: b9ca3098-b0f9-45d3-b00f-fd495404cb2e
Jun 10 08:24:09.398: INFO: Successfully deleted PD "aws://eu-west-2a/vol-00c19c6b94797c7cb".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 10 08:24:09.398: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-1122" for this suite.
... skipping 73 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 08:23:10.327: 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.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun 10 08:23:10.863: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 10 08:23:10.863: INFO: Creating resource for dynamic PV
Jun 10 08:23:10.863: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-16557ttsr
STEP: creating a claim
Jun 10 08:23:10.970: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-j2m6
STEP: Checking for subpath error in container status
Jun 10 08:23:35.512: INFO: Deleting pod "pod-subpath-test-dynamicpv-j2m6" in namespace "provisioning-1655"
Jun 10 08:23:35.620: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-j2m6" to be fully deleted
STEP: Deleting pod
Jun 10 08:23:45.835: INFO: Deleting pod "pod-subpath-test-dynamicpv-j2m6" in namespace "provisioning-1655"
STEP: Deleting pvc
Jun 10 08:23:46.154: INFO: Deleting PersistentVolumeClaim "awshp65p"
... skipping 15 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Y1KozJqJu/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Y1KozJqJu/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.Y1KozJqJu/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.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (ntfs)][Feature:Windows] volumes
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 10 08:24:12.235: INFO: Distro debian doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Pre-provisioned PV (ntfs)][Feature:Windows] volumes
... skipping 162 lines ...
Jun 10 08:23:30.015: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2113-e2e-scl2mcx
STEP: creating a claim
Jun 10 08:23:30.122: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-2z9t
STEP: Creating a pod to test subpath
Jun 10 08:23:30.446: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-2z9t" in namespace "provisioning-2113" to be "Succeeded or Failed"
Jun 10 08:23:30.553: INFO: Pod "pod-subpath-test-dynamicpv-2z9t": Phase="Pending", Reason="", readiness=false. Elapsed: 106.872423ms
Jun 10 08:23:32.659: INFO: Pod "pod-subpath-test-dynamicpv-2z9t": Phase="Pending", Reason="", readiness=false. Elapsed: 2.212476269s
Jun 10 08:23:34.775: INFO: Pod "pod-subpath-test-dynamicpv-2z9t": Phase="Pending", Reason="", readiness=false. Elapsed: 4.328817013s
Jun 10 08:23:36.883: INFO: Pod "pod-subpath-test-dynamicpv-2z9t": Phase="Pending", Reason="", readiness=false. Elapsed: 6.437194374s
Jun 10 08:23:38.991: INFO: Pod "pod-subpath-test-dynamicpv-2z9t": Phase="Pending", Reason="", readiness=false. Elapsed: 8.544351024s
Jun 10 08:23:41.097: INFO: Pod "pod-subpath-test-dynamicpv-2z9t": Phase="Pending", Reason="", readiness=false. Elapsed: 10.650806415s
... skipping 3 lines ...
Jun 10 08:23:49.522: INFO: Pod "pod-subpath-test-dynamicpv-2z9t": Phase="Pending", Reason="", readiness=false. Elapsed: 19.075626752s
Jun 10 08:23:51.631: INFO: Pod "pod-subpath-test-dynamicpv-2z9t": Phase="Pending", Reason="", readiness=false. Elapsed: 21.184658441s
Jun 10 08:23:53.737: INFO: Pod "pod-subpath-test-dynamicpv-2z9t": Phase="Pending", Reason="", readiness=false. Elapsed: 23.291192308s
Jun 10 08:23:55.844: INFO: Pod "pod-subpath-test-dynamicpv-2z9t": Phase="Pending", Reason="", readiness=false. Elapsed: 25.398111116s
Jun 10 08:23:57.952: INFO: Pod "pod-subpath-test-dynamicpv-2z9t": Phase="Succeeded", Reason="", readiness=false. Elapsed: 27.505623516s
STEP: Saw pod success
Jun 10 08:23:57.952: INFO: Pod "pod-subpath-test-dynamicpv-2z9t" satisfied condition "Succeeded or Failed"
Jun 10 08:23:58.057: INFO: Trying to get logs from node ip-172-20-58-127.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-2z9t container test-container-volume-dynamicpv-2z9t: <nil>
STEP: delete the pod
Jun 10 08:23:58.292: INFO: Waiting for pod pod-subpath-test-dynamicpv-2z9t to disappear
Jun 10 08:23:58.397: INFO: Pod pod-subpath-test-dynamicpv-2z9t no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-2z9t
Jun 10 08:23:58.398: INFO: Deleting pod "pod-subpath-test-dynamicpv-2z9t" in namespace "provisioning-2113"
... skipping 80 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Y1KozJqJu/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Y1KozJqJu/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.Y1KozJqJu/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.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 11 lines ...
Jun 10 08:22:49.877: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2835-e2e-sc9kkl2
STEP: creating a claim
Jun 10 08:22:49.993: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-7zxp
STEP: Creating a pod to test subpath
Jun 10 08:22:50.321: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-7zxp" in namespace "provisioning-2835" to be "Succeeded or Failed"
Jun 10 08:22:50.427: INFO: Pod "pod-subpath-test-dynamicpv-7zxp": Phase="Pending", Reason="", readiness=false. Elapsed: 106.014266ms
Jun 10 08:22:52.535: INFO: Pod "pod-subpath-test-dynamicpv-7zxp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.213136739s
Jun 10 08:22:54.643: INFO: Pod "pod-subpath-test-dynamicpv-7zxp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.32188395s
Jun 10 08:22:56.752: INFO: Pod "pod-subpath-test-dynamicpv-7zxp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.430211682s
Jun 10 08:22:58.861: INFO: Pod "pod-subpath-test-dynamicpv-7zxp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.539275433s
Jun 10 08:23:00.974: INFO: Pod "pod-subpath-test-dynamicpv-7zxp": Phase="Pending", Reason="", readiness=false. Elapsed: 10.652086224s
Jun 10 08:23:03.082: INFO: Pod "pod-subpath-test-dynamicpv-7zxp": Phase="Pending", Reason="", readiness=false. Elapsed: 12.760597779s
Jun 10 08:23:05.191: INFO: Pod "pod-subpath-test-dynamicpv-7zxp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.869607183s
STEP: Saw pod success
Jun 10 08:23:05.191: INFO: Pod "pod-subpath-test-dynamicpv-7zxp" satisfied condition "Succeeded or Failed"
Jun 10 08:23:05.297: INFO: Trying to get logs from node ip-172-20-59-227.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-7zxp container test-container-subpath-dynamicpv-7zxp: <nil>
STEP: delete the pod
Jun 10 08:23:05.535: INFO: Waiting for pod pod-subpath-test-dynamicpv-7zxp to disappear
Jun 10 08:23:05.641: INFO: Pod pod-subpath-test-dynamicpv-7zxp no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-7zxp
Jun 10 08:23:05.641: INFO: Deleting pod "pod-subpath-test-dynamicpv-7zxp" in namespace "provisioning-2835"
STEP: Creating pod pod-subpath-test-dynamicpv-7zxp
STEP: Creating a pod to test subpath
Jun 10 08:23:05.857: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-7zxp" in namespace "provisioning-2835" to be "Succeeded or Failed"
Jun 10 08:23:05.963: INFO: Pod "pod-subpath-test-dynamicpv-7zxp": Phase="Pending", Reason="", readiness=false. Elapsed: 105.735822ms
Jun 10 08:23:08.069: INFO: Pod "pod-subpath-test-dynamicpv-7zxp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.212060664s
Jun 10 08:23:10.175: INFO: Pod "pod-subpath-test-dynamicpv-7zxp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.318208298s
Jun 10 08:23:12.282: INFO: Pod "pod-subpath-test-dynamicpv-7zxp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.424847575s
Jun 10 08:23:14.388: INFO: Pod "pod-subpath-test-dynamicpv-7zxp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.531295248s
Jun 10 08:23:16.495: INFO: Pod "pod-subpath-test-dynamicpv-7zxp": Phase="Pending", Reason="", readiness=false. Elapsed: 10.638046818s
... skipping 6 lines ...
Jun 10 08:23:31.251: INFO: Pod "pod-subpath-test-dynamicpv-7zxp": Phase="Pending", Reason="", readiness=false. Elapsed: 25.394184854s
Jun 10 08:23:33.357: INFO: Pod "pod-subpath-test-dynamicpv-7zxp": Phase="Pending", Reason="", readiness=false. Elapsed: 27.500187636s
Jun 10 08:23:35.465: INFO: Pod "pod-subpath-test-dynamicpv-7zxp": Phase="Pending", Reason="", readiness=false. Elapsed: 29.608293877s
Jun 10 08:23:37.572: INFO: Pod "pod-subpath-test-dynamicpv-7zxp": Phase="Pending", Reason="", readiness=false. Elapsed: 31.71436091s
Jun 10 08:23:39.681: INFO: Pod "pod-subpath-test-dynamicpv-7zxp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 33.824190495s
STEP: Saw pod success
Jun 10 08:23:39.681: INFO: Pod "pod-subpath-test-dynamicpv-7zxp" satisfied condition "Succeeded or Failed"
Jun 10 08:23:39.790: INFO: Trying to get logs from node ip-172-20-45-65.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-7zxp container test-container-subpath-dynamicpv-7zxp: <nil>
STEP: delete the pod
Jun 10 08:23:40.020: INFO: Waiting for pod pod-subpath-test-dynamicpv-7zxp to disappear
Jun 10 08:23:40.132: INFO: Pod pod-subpath-test-dynamicpv-7zxp no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-7zxp
Jun 10 08:23:40.132: INFO: Deleting pod "pod-subpath-test-dynamicpv-7zxp" in namespace "provisioning-2835"
... skipping 268 lines ...
Jun 10 08:24:22.110: INFO: Pod aws-client still exists
Jun 10 08:24:24.004: INFO: Waiting for pod aws-client to disappear
Jun 10 08:24:24.112: INFO: Pod aws-client still exists
Jun 10 08:24:26.004: INFO: Waiting for pod aws-client to disappear
Jun 10 08:24:26.110: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun 10 08:24:26.704: INFO: Couldn't delete PD "aws://eu-west-2a/vol-07f2e28ba6bbaca76", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07f2e28ba6bbaca76 is currently attached to i-0ff665d16f07b5536
	status code: 400, request id: eb422c40-73cd-4fff-8a9d-0323a340945b
Jun 10 08:24:32.285: INFO: Successfully deleted PD "aws://eu-west-2a/vol-07f2e28ba6bbaca76".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 10 08:24:32.285: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8309" for this suite.
... skipping 209 lines ...
Jun 10 08:23:42.708: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-94187hzqj
STEP: creating a claim
Jun 10 08:23:42.816: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-f88s
STEP: Creating a pod to test subpath
Jun 10 08:23:43.148: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-f88s" in namespace "provisioning-9418" to be "Succeeded or Failed"
Jun 10 08:23:43.255: INFO: Pod "pod-subpath-test-dynamicpv-f88s": Phase="Pending", Reason="", readiness=false. Elapsed: 106.557769ms
Jun 10 08:23:45.363: INFO: Pod "pod-subpath-test-dynamicpv-f88s": Phase="Pending", Reason="", readiness=false. Elapsed: 2.21418371s
Jun 10 08:23:47.470: INFO: Pod "pod-subpath-test-dynamicpv-f88s": Phase="Pending", Reason="", readiness=false. Elapsed: 4.321352095s
Jun 10 08:23:49.577: INFO: Pod "pod-subpath-test-dynamicpv-f88s": Phase="Pending", Reason="", readiness=false. Elapsed: 6.428458646s
Jun 10 08:23:51.685: INFO: Pod "pod-subpath-test-dynamicpv-f88s": Phase="Pending", Reason="", readiness=false. Elapsed: 8.536479858s
Jun 10 08:23:53.793: INFO: Pod "pod-subpath-test-dynamicpv-f88s": Phase="Pending", Reason="", readiness=false. Elapsed: 10.644846523s
... skipping 2 lines ...
Jun 10 08:24:00.121: INFO: Pod "pod-subpath-test-dynamicpv-f88s": Phase="Pending", Reason="", readiness=false. Elapsed: 16.972477306s
Jun 10 08:24:02.229: INFO: Pod "pod-subpath-test-dynamicpv-f88s": Phase="Pending", Reason="", readiness=false. Elapsed: 19.080305498s
Jun 10 08:24:04.342: INFO: Pod "pod-subpath-test-dynamicpv-f88s": Phase="Pending", Reason="", readiness=false. Elapsed: 21.193119793s
Jun 10 08:24:06.450: INFO: Pod "pod-subpath-test-dynamicpv-f88s": Phase="Pending", Reason="", readiness=false. Elapsed: 23.301054606s
Jun 10 08:24:08.557: INFO: Pod "pod-subpath-test-dynamicpv-f88s": Phase="Succeeded", Reason="", readiness=false. Elapsed: 25.408092931s
STEP: Saw pod success
Jun 10 08:24:08.557: INFO: Pod "pod-subpath-test-dynamicpv-f88s" satisfied condition "Succeeded or Failed"
Jun 10 08:24:08.676: INFO: Trying to get logs from node ip-172-20-59-227.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-f88s container test-container-subpath-dynamicpv-f88s: <nil>
STEP: delete the pod
Jun 10 08:24:08.912: INFO: Waiting for pod pod-subpath-test-dynamicpv-f88s to disappear
Jun 10 08:24:09.019: INFO: Pod pod-subpath-test-dynamicpv-f88s no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-f88s
Jun 10 08:24:09.019: INFO: Deleting pod "pod-subpath-test-dynamicpv-f88s" in namespace "provisioning-9418"
STEP: Creating pod pod-subpath-test-dynamicpv-f88s
STEP: Creating a pod to test subpath
Jun 10 08:24:09.238: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-f88s" in namespace "provisioning-9418" to be "Succeeded or Failed"
Jun 10 08:24:09.346: INFO: Pod "pod-subpath-test-dynamicpv-f88s": Phase="Pending", Reason="", readiness=false. Elapsed: 107.436019ms
Jun 10 08:24:11.453: INFO: Pod "pod-subpath-test-dynamicpv-f88s": Phase="Pending", Reason="", readiness=false. Elapsed: 2.214504624s
Jun 10 08:24:13.562: INFO: Pod "pod-subpath-test-dynamicpv-f88s": Phase="Pending", Reason="", readiness=false. Elapsed: 4.323211373s
Jun 10 08:24:15.669: INFO: Pod "pod-subpath-test-dynamicpv-f88s": Phase="Pending", Reason="", readiness=false. Elapsed: 6.430234095s
Jun 10 08:24:17.776: INFO: Pod "pod-subpath-test-dynamicpv-f88s": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.537435863s
STEP: Saw pod success
Jun 10 08:24:17.776: INFO: Pod "pod-subpath-test-dynamicpv-f88s" satisfied condition "Succeeded or Failed"
Jun 10 08:24:17.883: INFO: Trying to get logs from node ip-172-20-59-227.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-f88s container test-container-subpath-dynamicpv-f88s: <nil>
STEP: delete the pod
Jun 10 08:24:18.105: INFO: Waiting for pod pod-subpath-test-dynamicpv-f88s to disappear
Jun 10 08:24:18.213: INFO: Pod pod-subpath-test-dynamicpv-f88s no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-f88s
Jun 10 08:24:18.213: INFO: Deleting pod "pod-subpath-test-dynamicpv-f88s" in namespace "provisioning-9418"
... skipping 140 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 08:23:59.698: 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.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun 10 08:24:00.229: INFO: Creating resource for dynamic PV
Jun 10 08:24:00.229: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7012-e2e-sc2wvf5
STEP: creating a claim
Jun 10 08:24:00.337: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-zvz6
STEP: Checking for subpath error in container status
Jun 10 08:24:20.910: INFO: Deleting pod "pod-subpath-test-dynamicpv-zvz6" in namespace "provisioning-7012"
Jun 10 08:24:21.020: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-zvz6" to be fully deleted
STEP: Deleting pod
Jun 10 08:24:31.234: INFO: Deleting pod "pod-subpath-test-dynamicpv-zvz6" in namespace "provisioning-7012"
STEP: Deleting pvc
Jun 10 08:24:31.552: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comfmt4c"
... skipping 11 lines ...

• [SLOW TEST:47.716 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath directory is outside the volume [Slow][LinuxOnly]
    /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow]
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 10 08:24:47.416: INFO: Driver supports dynamic provisioning, skipping PreprovisionedPV pattern
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow]
... skipping 102 lines ...
Jun 10 08:23:43.349: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-98065vv6m
STEP: creating a claim
Jun 10 08:23:43.456: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-j6dk
STEP: Creating a pod to test subpath
Jun 10 08:23:43.780: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-j6dk" in namespace "provisioning-9806" to be "Succeeded or Failed"
Jun 10 08:23:43.886: INFO: Pod "pod-subpath-test-dynamicpv-j6dk": Phase="Pending", Reason="", readiness=false. Elapsed: 106.624806ms
Jun 10 08:23:46.002: INFO: Pod "pod-subpath-test-dynamicpv-j6dk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.222345985s
Jun 10 08:23:48.110: INFO: Pod "pod-subpath-test-dynamicpv-j6dk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.330850425s
Jun 10 08:23:50.219: INFO: Pod "pod-subpath-test-dynamicpv-j6dk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.439192267s
Jun 10 08:23:52.326: INFO: Pod "pod-subpath-test-dynamicpv-j6dk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.545995732s
Jun 10 08:23:54.434: INFO: Pod "pod-subpath-test-dynamicpv-j6dk": Phase="Pending", Reason="", readiness=false. Elapsed: 10.654284033s
... skipping 9 lines ...
Jun 10 08:24:15.522: INFO: Pod "pod-subpath-test-dynamicpv-j6dk": Phase="Pending", Reason="", readiness=false. Elapsed: 31.742109452s
Jun 10 08:24:17.635: INFO: Pod "pod-subpath-test-dynamicpv-j6dk": Phase="Pending", Reason="", readiness=false. Elapsed: 33.854992758s
Jun 10 08:24:19.745: INFO: Pod "pod-subpath-test-dynamicpv-j6dk": Phase="Pending", Reason="", readiness=false. Elapsed: 35.965317308s
Jun 10 08:24:21.852: INFO: Pod "pod-subpath-test-dynamicpv-j6dk": Phase="Pending", Reason="", readiness=false. Elapsed: 38.072596963s
Jun 10 08:24:23.960: INFO: Pod "pod-subpath-test-dynamicpv-j6dk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 40.180788396s
STEP: Saw pod success
Jun 10 08:24:23.960: INFO: Pod "pod-subpath-test-dynamicpv-j6dk" satisfied condition "Succeeded or Failed"
Jun 10 08:24:24.067: INFO: Trying to get logs from node ip-172-20-45-65.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-j6dk container test-container-subpath-dynamicpv-j6dk: <nil>
STEP: delete the pod
Jun 10 08:24:24.297: INFO: Waiting for pod pod-subpath-test-dynamicpv-j6dk to disappear
Jun 10 08:24:24.404: INFO: Pod pod-subpath-test-dynamicpv-j6dk no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-j6dk
Jun 10 08:24:24.404: INFO: Deleting pod "pod-subpath-test-dynamicpv-j6dk" in namespace "provisioning-9806"
... skipping 102 lines ...
Jun 10 08:24:10.155: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-3028-e2e-scd4886
STEP: creating a claim
Jun 10 08:24:10.262: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-8x2c
STEP: Creating a pod to test exec-volume-test
Jun 10 08:24:10.586: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-8x2c" in namespace "volume-3028" to be "Succeeded or Failed"
Jun 10 08:24:10.693: INFO: Pod "exec-volume-test-dynamicpv-8x2c": Phase="Pending", Reason="", readiness=false. Elapsed: 106.929505ms
Jun 10 08:24:12.801: INFO: Pod "exec-volume-test-dynamicpv-8x2c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.214186863s
Jun 10 08:24:14.908: INFO: Pod "exec-volume-test-dynamicpv-8x2c": Phase="Pending", Reason="", readiness=false. Elapsed: 4.321564259s
Jun 10 08:24:17.014: INFO: Pod "exec-volume-test-dynamicpv-8x2c": Phase="Pending", Reason="", readiness=false. Elapsed: 6.427980277s
Jun 10 08:24:19.122: INFO: Pod "exec-volume-test-dynamicpv-8x2c": Phase="Pending", Reason="", readiness=false. Elapsed: 8.535713336s
Jun 10 08:24:21.230: INFO: Pod "exec-volume-test-dynamicpv-8x2c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.643276597s
STEP: Saw pod success
Jun 10 08:24:21.230: INFO: Pod "exec-volume-test-dynamicpv-8x2c" satisfied condition "Succeeded or Failed"
Jun 10 08:24:21.336: INFO: Trying to get logs from node ip-172-20-36-68.eu-west-2.compute.internal pod exec-volume-test-dynamicpv-8x2c container exec-container-dynamicpv-8x2c: <nil>
STEP: delete the pod
Jun 10 08:24:21.557: INFO: Waiting for pod exec-volume-test-dynamicpv-8x2c to disappear
Jun 10 08:24:21.663: INFO: Pod exec-volume-test-dynamicpv-8x2c no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-8x2c
Jun 10 08:24:21.663: INFO: Deleting pod "exec-volume-test-dynamicpv-8x2c" in namespace "volume-3028"
... skipping 47 lines ...
Jun 10 08:24:27.139: INFO: PersistentVolumeClaim pvc-9gq8z found but phase is Pending instead of Bound.
Jun 10 08:24:29.245: INFO: PersistentVolumeClaim pvc-9gq8z found and phase=Bound (8.531218009s)
Jun 10 08:24:29.245: INFO: Waiting up to 3m0s for PersistentVolume aws-rjwhj to have phase Bound
Jun 10 08:24:29.351: INFO: PersistentVolume aws-rjwhj found and phase=Bound (105.72936ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-n4rc
STEP: Creating a pod to test exec-volume-test
Jun 10 08:24:29.672: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-n4rc" in namespace "volume-1161" to be "Succeeded or Failed"
Jun 10 08:24:29.777: INFO: Pod "exec-volume-test-preprovisionedpv-n4rc": Phase="Pending", Reason="", readiness=false. Elapsed: 105.754674ms
Jun 10 08:24:31.884: INFO: Pod "exec-volume-test-preprovisionedpv-n4rc": Phase="Pending", Reason="", readiness=false. Elapsed: 2.212184912s
Jun 10 08:24:33.991: INFO: Pod "exec-volume-test-preprovisionedpv-n4rc": Phase="Pending", Reason="", readiness=false. Elapsed: 4.31972293s
Jun 10 08:24:36.098: INFO: Pod "exec-volume-test-preprovisionedpv-n4rc": Phase="Pending", Reason="", readiness=false. Elapsed: 6.426143789s
Jun 10 08:24:38.205: INFO: Pod "exec-volume-test-preprovisionedpv-n4rc": Phase="Pending", Reason="", readiness=false. Elapsed: 8.533337398s
Jun 10 08:24:40.312: INFO: Pod "exec-volume-test-preprovisionedpv-n4rc": Phase="Pending", Reason="", readiness=false. Elapsed: 10.639890994s
Jun 10 08:24:42.418: INFO: Pod "exec-volume-test-preprovisionedpv-n4rc": Phase="Pending", Reason="", readiness=false. Elapsed: 12.746356583s
Jun 10 08:24:44.525: INFO: Pod "exec-volume-test-preprovisionedpv-n4rc": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.853716102s
STEP: Saw pod success
Jun 10 08:24:44.525: INFO: Pod "exec-volume-test-preprovisionedpv-n4rc" satisfied condition "Succeeded or Failed"
Jun 10 08:24:44.631: INFO: Trying to get logs from node ip-172-20-58-127.eu-west-2.compute.internal pod exec-volume-test-preprovisionedpv-n4rc container exec-container-preprovisionedpv-n4rc: <nil>
STEP: delete the pod
Jun 10 08:24:44.851: INFO: Waiting for pod exec-volume-test-preprovisionedpv-n4rc to disappear
Jun 10 08:24:44.957: INFO: Pod exec-volume-test-preprovisionedpv-n4rc no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-n4rc
Jun 10 08:24:44.957: INFO: Deleting pod "exec-volume-test-preprovisionedpv-n4rc" in namespace "volume-1161"
STEP: Deleting pv and pvc
Jun 10 08:24:45.062: INFO: Deleting PersistentVolumeClaim "pvc-9gq8z"
Jun 10 08:24:45.169: INFO: Deleting PersistentVolume "aws-rjwhj"
Jun 10 08:24:45.496: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0dffb7096085d6029", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0dffb7096085d6029 is currently attached to i-02b09d2f0c0b0f80b
	status code: 400, request id: 895179a1-c9d3-4f95-a76d-f378725480a6
Jun 10 08:24:51.051: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0dffb7096085d6029", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0dffb7096085d6029 is currently attached to i-02b09d2f0c0b0f80b
	status code: 400, request id: e932647f-029e-423a-b316-be8ec0c2f542
Jun 10 08:24:56.630: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0dffb7096085d6029", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0dffb7096085d6029 is currently attached to i-02b09d2f0c0b0f80b
	status code: 400, request id: c838dc65-2289-48cf-815d-09cac92c481b
Jun 10 08:25:02.236: INFO: Successfully deleted PD "aws://eu-west-2a/vol-0dffb7096085d6029".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 10 08:25:02.236: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-1161" for this suite.
... skipping 18 lines ...

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

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

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

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

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

    /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:92
------------------------------
... skipping 89 lines ...

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

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

    /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 37 lines ...
Jun 10 08:24:33.060: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6204s8g49
STEP: creating a claim
Jun 10 08:24:33.175: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-7mst
STEP: Creating a pod to test subpath
Jun 10 08:24:33.501: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-7mst" in namespace "provisioning-6204" to be "Succeeded or Failed"
Jun 10 08:24:33.607: INFO: Pod "pod-subpath-test-dynamicpv-7mst": Phase="Pending", Reason="", readiness=false. Elapsed: 106.041641ms
Jun 10 08:24:35.714: INFO: Pod "pod-subpath-test-dynamicpv-7mst": Phase="Pending", Reason="", readiness=false. Elapsed: 2.213065471s
Jun 10 08:24:37.821: INFO: Pod "pod-subpath-test-dynamicpv-7mst": Phase="Pending", Reason="", readiness=false. Elapsed: 4.319580573s
Jun 10 08:24:39.931: INFO: Pod "pod-subpath-test-dynamicpv-7mst": Phase="Pending", Reason="", readiness=false. Elapsed: 6.429800429s
Jun 10 08:24:42.038: INFO: Pod "pod-subpath-test-dynamicpv-7mst": Phase="Pending", Reason="", readiness=false. Elapsed: 8.536867559s
Jun 10 08:24:44.144: INFO: Pod "pod-subpath-test-dynamicpv-7mst": Phase="Pending", Reason="", readiness=false. Elapsed: 10.643427015s
... skipping 3 lines ...
Jun 10 08:24:52.575: INFO: Pod "pod-subpath-test-dynamicpv-7mst": Phase="Pending", Reason="", readiness=false. Elapsed: 19.073758825s
Jun 10 08:24:54.682: INFO: Pod "pod-subpath-test-dynamicpv-7mst": Phase="Pending", Reason="", readiness=false. Elapsed: 21.181213804s
Jun 10 08:24:56.789: INFO: Pod "pod-subpath-test-dynamicpv-7mst": Phase="Pending", Reason="", readiness=false. Elapsed: 23.288133213s
Jun 10 08:24:58.898: INFO: Pod "pod-subpath-test-dynamicpv-7mst": Phase="Pending", Reason="", readiness=false. Elapsed: 25.397175509s
Jun 10 08:25:01.005: INFO: Pod "pod-subpath-test-dynamicpv-7mst": Phase="Succeeded", Reason="", readiness=false. Elapsed: 27.50435818s
STEP: Saw pod success
Jun 10 08:25:01.005: INFO: Pod "pod-subpath-test-dynamicpv-7mst" satisfied condition "Succeeded or Failed"
Jun 10 08:25:01.111: INFO: Trying to get logs from node ip-172-20-59-227.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-7mst container test-container-subpath-dynamicpv-7mst: <nil>
STEP: delete the pod
Jun 10 08:25:01.342: INFO: Waiting for pod pod-subpath-test-dynamicpv-7mst to disappear
Jun 10 08:25:01.447: INFO: Pod pod-subpath-test-dynamicpv-7mst no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-7mst
Jun 10 08:25:01.448: INFO: Deleting pod "pod-subpath-test-dynamicpv-7mst" in namespace "provisioning-6204"
... skipping 198 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 08:24:47.418: 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.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun 10 08:24:47.975: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 10 08:24:47.975: INFO: Creating resource for dynamic PV
Jun 10 08:24:47.975: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-827866xfr
STEP: creating a claim
Jun 10 08:24:48.084: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-dthn
STEP: Checking for subpath error in container status
Jun 10 08:25:12.623: INFO: Deleting pod "pod-subpath-test-dynamicpv-dthn" in namespace "provisioning-8278"
Jun 10 08:25:12.730: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-dthn" to be fully deleted
STEP: Deleting pod
Jun 10 08:25:24.942: INFO: Deleting pod "pod-subpath-test-dynamicpv-dthn" in namespace "provisioning-8278"
STEP: Deleting pvc
Jun 10 08:25:25.264: INFO: Deleting PersistentVolumeClaim "aws8fpfj"
... skipping 11 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Y1KozJqJu/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Y1KozJqJu/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath file is outside the volume [Slow][LinuxOnly]
      /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 10 08:25:30.911: INFO: Driver "ebs.csi.aws.com" does not support volume type "CSIInlineVolume" - skipping
[AfterEach] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral
... skipping 65 lines ...

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 212 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 08:24:47.358: 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.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 10 08:24:47.893: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 10 08:24:47.893: INFO: Creating resource for dynamic PV
Jun 10 08:24:47.893: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-8455rskns
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 10 08:24:52.637: INFO: Deleting pod "pod-1bc0112f-8f75-46b5-8a2a-fb1163238a45" in namespace "volumemode-8455"
Jun 10 08:24:52.744: INFO: Wait up to 5m0s for pod "pod-1bc0112f-8f75-46b5-8a2a-fb1163238a45" to be fully deleted
STEP: Deleting pvc
Jun 10 08:24:59.165: INFO: Deleting PersistentVolumeClaim "aws285l7"
Jun 10 08:24:59.271: INFO: Waiting up to 5m0s for PersistentVolume pvc-ebe4901c-7cc0-446c-ad5a-9f357ade0286 to get deleted
Jun 10 08:24:59.376: INFO: PersistentVolume pvc-ebe4901c-7cc0-446c-ad5a-9f357ade0286 found and phase=Released (104.539498ms)
... skipping 15 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Y1KozJqJu/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Y1KozJqJu/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
    /tmp/kops.Y1KozJqJu/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.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow]
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 10 08:25:35.433: INFO: Driver supports dynamic provisioning, skipping PreprovisionedPV pattern
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow]
... skipping 27 lines ...
Jun 10 08:25:02.987: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 10 08:25:03.361: INFO: Successfully created a new PD: "aws://eu-west-2a/vol-03fa4f28d5d389af7".
Jun 10 08:25:03.361: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-d2kc
STEP: Creating a pod to test exec-volume-test
Jun 10 08:25:03.482: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-d2kc" in namespace "volume-4755" to be "Succeeded or Failed"
Jun 10 08:25:03.592: INFO: Pod "exec-volume-test-inlinevolume-d2kc": Phase="Pending", Reason="", readiness=false. Elapsed: 110.359922ms
Jun 10 08:25:05.698: INFO: Pod "exec-volume-test-inlinevolume-d2kc": Phase="Pending", Reason="", readiness=false. Elapsed: 2.216797901s
Jun 10 08:25:07.805: INFO: Pod "exec-volume-test-inlinevolume-d2kc": Phase="Pending", Reason="", readiness=false. Elapsed: 4.322984138s
Jun 10 08:25:09.913: INFO: Pod "exec-volume-test-inlinevolume-d2kc": Phase="Pending", Reason="", readiness=false. Elapsed: 6.431780511s
Jun 10 08:25:12.025: INFO: Pod "exec-volume-test-inlinevolume-d2kc": Phase="Pending", Reason="", readiness=false. Elapsed: 8.543248763s
Jun 10 08:25:14.131: INFO: Pod "exec-volume-test-inlinevolume-d2kc": Phase="Pending", Reason="", readiness=false. Elapsed: 10.64953203s
Jun 10 08:25:16.238: INFO: Pod "exec-volume-test-inlinevolume-d2kc": Phase="Pending", Reason="", readiness=false. Elapsed: 12.756414166s
Jun 10 08:25:18.345: INFO: Pod "exec-volume-test-inlinevolume-d2kc": Phase="Pending", Reason="", readiness=false. Elapsed: 14.86334409s
Jun 10 08:25:20.452: INFO: Pod "exec-volume-test-inlinevolume-d2kc": Phase="Pending", Reason="", readiness=false. Elapsed: 16.970741671s
Jun 10 08:25:22.559: INFO: Pod "exec-volume-test-inlinevolume-d2kc": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.077128091s
STEP: Saw pod success
Jun 10 08:25:22.559: INFO: Pod "exec-volume-test-inlinevolume-d2kc" satisfied condition "Succeeded or Failed"
Jun 10 08:25:22.665: INFO: Trying to get logs from node ip-172-20-36-68.eu-west-2.compute.internal pod exec-volume-test-inlinevolume-d2kc container exec-container-inlinevolume-d2kc: <nil>
STEP: delete the pod
Jun 10 08:25:22.885: INFO: Waiting for pod exec-volume-test-inlinevolume-d2kc to disappear
Jun 10 08:25:22.991: INFO: Pod exec-volume-test-inlinevolume-d2kc no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-d2kc
Jun 10 08:25:22.991: INFO: Deleting pod "exec-volume-test-inlinevolume-d2kc" in namespace "volume-4755"
Jun 10 08:25:23.340: INFO: Couldn't delete PD "aws://eu-west-2a/vol-03fa4f28d5d389af7", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-03fa4f28d5d389af7 is currently attached to i-0ff665d16f07b5536
	status code: 400, request id: 827bfbbb-2345-48eb-8bc7-49f787676de2
Jun 10 08:25:29.891: INFO: Couldn't delete PD "aws://eu-west-2a/vol-03fa4f28d5d389af7", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-03fa4f28d5d389af7 is currently attached to i-0ff665d16f07b5536
	status code: 400, request id: e7f62481-e8bb-4577-9781-59aaa2829f5b
Jun 10 08:25:35.477: INFO: Successfully deleted PD "aws://eu-west-2a/vol-03fa4f28d5d389af7".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 10 08:25:35.477: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-4755" for this suite.
... skipping 260 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.Y1KozJqJu/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.Y1KozJqJu/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.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 101 lines ...
Jun 10 08:24:35.050: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2996-e2e-sccvnwb
STEP: creating a claim
Jun 10 08:24:35.158: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-xkpp
STEP: Creating a pod to test subpath
Jun 10 08:24:35.484: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-xkpp" in namespace "provisioning-2996" to be "Succeeded or Failed"
Jun 10 08:24:35.591: INFO: Pod "pod-subpath-test-dynamicpv-xkpp": Phase="Pending", Reason="", readiness=false. Elapsed: 106.820177ms
Jun 10 08:24:37.699: INFO: Pod "pod-subpath-test-dynamicpv-xkpp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.214994423s
Jun 10 08:24:39.806: INFO: Pod "pod-subpath-test-dynamicpv-xkpp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.322488991s
Jun 10 08:24:41.913: INFO: Pod "pod-subpath-test-dynamicpv-xkpp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.429566499s
Jun 10 08:24:44.021: INFO: Pod "pod-subpath-test-dynamicpv-xkpp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.537570954s
Jun 10 08:24:46.129: INFO: Pod "pod-subpath-test-dynamicpv-xkpp": Phase="Pending", Reason="", readiness=false. Elapsed: 10.645634283s
... skipping 2 lines ...
Jun 10 08:24:52.455: INFO: Pod "pod-subpath-test-dynamicpv-xkpp": Phase="Pending", Reason="", readiness=false. Elapsed: 16.971724182s
Jun 10 08:24:54.563: INFO: Pod "pod-subpath-test-dynamicpv-xkpp": Phase="Pending", Reason="", readiness=false. Elapsed: 19.079285577s
Jun 10 08:24:56.673: INFO: Pod "pod-subpath-test-dynamicpv-xkpp": Phase="Pending", Reason="", readiness=false. Elapsed: 21.188992814s
Jun 10 08:24:58.782: INFO: Pod "pod-subpath-test-dynamicpv-xkpp": Phase="Pending", Reason="", readiness=false. Elapsed: 23.298276305s
Jun 10 08:25:00.890: INFO: Pod "pod-subpath-test-dynamicpv-xkpp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 25.406698284s
STEP: Saw pod success
Jun 10 08:25:00.890: INFO: Pod "pod-subpath-test-dynamicpv-xkpp" satisfied condition "Succeeded or Failed"
Jun 10 08:25:00.998: INFO: Trying to get logs from node ip-172-20-45-65.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-xkpp container test-container-subpath-dynamicpv-xkpp: <nil>
STEP: delete the pod
Jun 10 08:25:01.225: INFO: Waiting for pod pod-subpath-test-dynamicpv-xkpp to disappear
Jun 10 08:25:01.332: INFO: Pod pod-subpath-test-dynamicpv-xkpp no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-xkpp
Jun 10 08:25:01.332: INFO: Deleting pod "pod-subpath-test-dynamicpv-xkpp" in namespace "provisioning-2996"
... skipping 222 lines ...
Jun 10 08:25:40.332: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 54 lines ...
Jun 10 08:23:53.991: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-5840-e2e-sc25m5t      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-5840    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-5840-e2e-sc25m5t,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-5840    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-5840-e2e-sc25m5t,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-5840    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-5840-e2e-sc25m5t,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-5840-e2e-sc25m5t    38783276-5482-4ac3-87c9-8669f1dcad39 7268 0 2021-06-10 08:23:54 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-10 08:23:54 +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-mrd49 pvc- provisioning-5840  06ad02eb-f060-469c-a18f-a711963a2291 7270 0 2021-06-10 08:23:54 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-10 08:23:54 +0000 UTC FieldsV1 {"f:metadata":{"f:generateName":{}},"f:spec":{"f:accessModes":{},"f:resources":{"f:requests":{".":{},"f:storage":{}}},"f:storageClassName":{},"f:volumeMode":{}}}}]},Spec:PersistentVolumeClaimSpec{AccessModes:[ReadWriteOnce],Resources:ResourceRequirements{Limits:ResourceList{},Requests:ResourceList{storage: {{1073741824 0} {<nil>} 1Gi BinarySI},},},VolumeName:,Selector:nil,StorageClassName:*provisioning-5840-e2e-sc25m5t,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-e4b277e7-d3b4-484b-ab0f-8b853caa9e25 in namespace provisioning-5840
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun 10 08:24:17.167: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-z6fmk" in namespace "provisioning-5840" to be "Succeeded or Failed"
Jun 10 08:24:17.276: INFO: Pod "pvc-volume-tester-writer-z6fmk": Phase="Pending", Reason="", readiness=false. Elapsed: 108.377846ms
Jun 10 08:24:19.383: INFO: Pod "pvc-volume-tester-writer-z6fmk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.215698627s
Jun 10 08:24:21.491: INFO: Pod "pvc-volume-tester-writer-z6fmk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.323842915s
Jun 10 08:24:23.600: INFO: Pod "pvc-volume-tester-writer-z6fmk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.43263269s
Jun 10 08:24:25.706: INFO: Pod "pvc-volume-tester-writer-z6fmk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.539020265s
Jun 10 08:24:27.812: INFO: Pod "pvc-volume-tester-writer-z6fmk": Phase="Pending", Reason="", readiness=false. Elapsed: 10.645304721s
... skipping 7 lines ...
Jun 10 08:24:44.676: INFO: Pod "pvc-volume-tester-writer-z6fmk": Phase="Pending", Reason="", readiness=false. Elapsed: 27.509181422s
Jun 10 08:24:46.783: INFO: Pod "pvc-volume-tester-writer-z6fmk": Phase="Pending", Reason="", readiness=false. Elapsed: 29.616150797s
Jun 10 08:24:48.891: INFO: Pod "pvc-volume-tester-writer-z6fmk": Phase="Pending", Reason="", readiness=false. Elapsed: 31.723394493s
Jun 10 08:24:51.016: INFO: Pod "pvc-volume-tester-writer-z6fmk": Phase="Pending", Reason="", readiness=false. Elapsed: 33.849272061s
Jun 10 08:24:53.124: INFO: Pod "pvc-volume-tester-writer-z6fmk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 35.956631439s
STEP: Saw pod success
Jun 10 08:24:53.124: INFO: Pod "pvc-volume-tester-writer-z6fmk" satisfied condition "Succeeded or Failed"
Jun 10 08:24:53.338: INFO: Pod pvc-volume-tester-writer-z6fmk has the following logs: 
Jun 10 08:24:53.338: INFO: Deleting pod "pvc-volume-tester-writer-z6fmk" in namespace "provisioning-5840"
Jun 10 08:24:53.451: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-z6fmk" 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-59-227.eu-west-2.compute.internal"
Jun 10 08:24:53.881: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-jthnh" in namespace "provisioning-5840" to be "Succeeded or Failed"
Jun 10 08:24:53.987: INFO: Pod "pvc-volume-tester-reader-jthnh": Phase="Pending", Reason="", readiness=false. Elapsed: 106.620613ms
Jun 10 08:24:56.098: INFO: Pod "pvc-volume-tester-reader-jthnh": Phase="Pending", Reason="", readiness=false. Elapsed: 2.216942599s
Jun 10 08:24:58.205: INFO: Pod "pvc-volume-tester-reader-jthnh": Phase="Pending", Reason="", readiness=false. Elapsed: 4.324171622s
Jun 10 08:25:00.311: INFO: Pod "pvc-volume-tester-reader-jthnh": Phase="Pending", Reason="", readiness=false. Elapsed: 6.430509243s
Jun 10 08:25:02.418: INFO: Pod "pvc-volume-tester-reader-jthnh": Phase="Pending", Reason="", readiness=false. Elapsed: 8.536945436s
Jun 10 08:25:04.525: INFO: Pod "pvc-volume-tester-reader-jthnh": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.643979148s
STEP: Saw pod success
Jun 10 08:25:04.525: INFO: Pod "pvc-volume-tester-reader-jthnh" satisfied condition "Succeeded or Failed"
Jun 10 08:25:04.738: INFO: Pod pvc-volume-tester-reader-jthnh has the following logs: hello world

Jun 10 08:25:04.738: INFO: Deleting pod "pvc-volume-tester-reader-jthnh" in namespace "provisioning-5840"
Jun 10 08:25:04.852: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-jthnh" to be fully deleted
Jun 10 08:25:04.958: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-mrd49] to have phase Bound
Jun 10 08:25:05.064: INFO: PersistentVolumeClaim pvc-mrd49 found and phase=Bound (105.932155ms)
... skipping 215 lines ...

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

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

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

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

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

    /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 26 lines ...
Jun 10 08:25:12.197: INFO: PersistentVolumeClaim pvc-h48hs found but phase is Pending instead of Bound.
Jun 10 08:25:14.304: INFO: PersistentVolumeClaim pvc-h48hs found and phase=Bound (14.854618312s)
Jun 10 08:25:14.305: INFO: Waiting up to 3m0s for PersistentVolume aws-52j8w to have phase Bound
Jun 10 08:25:14.411: INFO: PersistentVolume aws-52j8w found and phase=Bound (106.080788ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-5vx6
STEP: Creating a pod to test exec-volume-test
Jun 10 08:25:14.732: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-5vx6" in namespace "volume-4094" to be "Succeeded or Failed"
Jun 10 08:25:14.839: INFO: Pod "exec-volume-test-preprovisionedpv-5vx6": Phase="Pending", Reason="", readiness=false. Elapsed: 106.542088ms
Jun 10 08:25:16.946: INFO: Pod "exec-volume-test-preprovisionedpv-5vx6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.213306856s
Jun 10 08:25:19.055: INFO: Pod "exec-volume-test-preprovisionedpv-5vx6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.322203254s
Jun 10 08:25:21.164: INFO: Pod "exec-volume-test-preprovisionedpv-5vx6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.431611755s
Jun 10 08:25:23.271: INFO: Pod "exec-volume-test-preprovisionedpv-5vx6": Phase="Pending", Reason="", readiness=false. Elapsed: 8.538892173s
Jun 10 08:25:25.378: INFO: Pod "exec-volume-test-preprovisionedpv-5vx6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.64578092s
STEP: Saw pod success
Jun 10 08:25:25.378: INFO: Pod "exec-volume-test-preprovisionedpv-5vx6" satisfied condition "Succeeded or Failed"
Jun 10 08:25:25.484: INFO: Trying to get logs from node ip-172-20-36-68.eu-west-2.compute.internal pod exec-volume-test-preprovisionedpv-5vx6 container exec-container-preprovisionedpv-5vx6: <nil>
STEP: delete the pod
Jun 10 08:25:25.706: INFO: Waiting for pod exec-volume-test-preprovisionedpv-5vx6 to disappear
Jun 10 08:25:25.813: INFO: Pod exec-volume-test-preprovisionedpv-5vx6 no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-5vx6
Jun 10 08:25:25.813: INFO: Deleting pod "exec-volume-test-preprovisionedpv-5vx6" in namespace "volume-4094"
STEP: Deleting pv and pvc
Jun 10 08:25:25.919: INFO: Deleting PersistentVolumeClaim "pvc-h48hs"
Jun 10 08:25:26.028: INFO: Deleting PersistentVolume "aws-52j8w"
Jun 10 08:25:26.369: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0173e496d72db35d1", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0173e496d72db35d1 is currently attached to i-0ff665d16f07b5536
	status code: 400, request id: f1105ac9-661c-49f7-8fa8-91f0c50f91d4
Jun 10 08:25:31.983: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0173e496d72db35d1", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0173e496d72db35d1 is currently attached to i-0ff665d16f07b5536
	status code: 400, request id: 7e38f9c7-1f41-4511-a92b-39df3279d4ae
Jun 10 08:25:37.574: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0173e496d72db35d1", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0173e496d72db35d1 is currently attached to i-0ff665d16f07b5536
	status code: 400, request id: c80ac862-4213-4d44-b426-1d8a8dc3eb30
Jun 10 08:25:43.142: INFO: Successfully deleted PD "aws://eu-west-2a/vol-0173e496d72db35d1".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 10 08:25:43.142: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-4094" for this suite.
... skipping 154 lines ...
Jun 10 08:23:14.300: INFO: Creating resource for dynamic PV
Jun 10 08:23:14.300: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-4964-e2e-scqc2sp
STEP: creating a claim
Jun 10 08:23:14.407: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 10 08:23:14.731: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-kvt7j" in namespace "snapshotting-4964" to be "Succeeded or Failed"
Jun 10 08:23:14.838: INFO: Pod "pvc-snapshottable-tester-kvt7j": Phase="Pending", Reason="", readiness=false. Elapsed: 107.072416ms
Jun 10 08:23:16.945: INFO: Pod "pvc-snapshottable-tester-kvt7j": Phase="Pending", Reason="", readiness=false. Elapsed: 2.214052317s
Jun 10 08:23:19.054: INFO: Pod "pvc-snapshottable-tester-kvt7j": Phase="Pending", Reason="", readiness=false. Elapsed: 4.323057411s
Jun 10 08:23:21.163: INFO: Pod "pvc-snapshottable-tester-kvt7j": Phase="Pending", Reason="", readiness=false. Elapsed: 6.431960727s
Jun 10 08:23:23.270: INFO: Pod "pvc-snapshottable-tester-kvt7j": Phase="Pending", Reason="", readiness=false. Elapsed: 8.538528285s
Jun 10 08:23:25.378: INFO: Pod "pvc-snapshottable-tester-kvt7j": Phase="Pending", Reason="", readiness=false. Elapsed: 10.646603026s
Jun 10 08:23:27.484: INFO: Pod "pvc-snapshottable-tester-kvt7j": Phase="Pending", Reason="", readiness=false. Elapsed: 12.752963524s
Jun 10 08:23:29.592: INFO: Pod "pvc-snapshottable-tester-kvt7j": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.860486415s
STEP: Saw pod success
Jun 10 08:23:29.592: INFO: Pod "pvc-snapshottable-tester-kvt7j" satisfied condition "Succeeded or Failed"
Jun 10 08:23:29.806: INFO: Pod pvc-snapshottable-tester-kvt7j has the following logs: 
Jun 10 08:23:29.806: INFO: Deleting pod "pvc-snapshottable-tester-kvt7j" in namespace "snapshotting-4964"
Jun 10 08:23:29.926: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-kvt7j" to be fully deleted
Jun 10 08:23:30.032: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comgqlvn] to have phase Bound
Jun 10 08:23:30.138: INFO: PersistentVolumeClaim ebs.csi.aws.comgqlvn found and phase=Bound (106.081895ms)
STEP: [init] checking the claim
... skipping 36 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.Y1KozJqJu/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 10 08:24:26.216: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-srkg8" in namespace "snapshotting-4964" to be "Succeeded or Failed"
Jun 10 08:24:26.324: INFO: Pod "pvc-snapshottable-data-tester-srkg8": Phase="Pending", Reason="", readiness=false. Elapsed: 107.192253ms
Jun 10 08:24:28.477: INFO: Pod "pvc-snapshottable-data-tester-srkg8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.260160757s
Jun 10 08:24:30.584: INFO: Pod "pvc-snapshottable-data-tester-srkg8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.367747499s
Jun 10 08:24:32.691: INFO: Pod "pvc-snapshottable-data-tester-srkg8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.4747873s
Jun 10 08:24:34.799: INFO: Pod "pvc-snapshottable-data-tester-srkg8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.582032443s
Jun 10 08:24:36.905: INFO: Pod "pvc-snapshottable-data-tester-srkg8": Phase="Pending", Reason="", readiness=false. Elapsed: 10.688335649s
Jun 10 08:24:39.011: INFO: Pod "pvc-snapshottable-data-tester-srkg8": Phase="Pending", Reason="", readiness=false. Elapsed: 12.794789509s
Jun 10 08:24:41.118: INFO: Pod "pvc-snapshottable-data-tester-srkg8": Phase="Pending", Reason="", readiness=false. Elapsed: 14.901895721s
Jun 10 08:24:43.225: INFO: Pod "pvc-snapshottable-data-tester-srkg8": Phase="Pending", Reason="", readiness=false. Elapsed: 17.008942942s
Jun 10 08:24:45.334: INFO: Pod "pvc-snapshottable-data-tester-srkg8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.117179362s
STEP: Saw pod success
Jun 10 08:24:45.334: INFO: Pod "pvc-snapshottable-data-tester-srkg8" satisfied condition "Succeeded or Failed"
Jun 10 08:24:45.548: INFO: Pod pvc-snapshottable-data-tester-srkg8 has the following logs: 
Jun 10 08:24:45.548: INFO: Deleting pod "pvc-snapshottable-data-tester-srkg8" in namespace "snapshotting-4964"
Jun 10 08:24:45.662: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-srkg8" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 10 08:25:08.215: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-4964 exec restored-pvc-tester-6gdb4 --namespace=snapshotting-4964 -- cat /mnt/test/data'
... skipping 95 lines ...
Jun 10 08:23:16.966: INFO: Creating resource for dynamic PV
Jun 10 08:23:16.966: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-8157-e2e-scjpqps
STEP: creating a claim
Jun 10 08:23:17.073: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 10 08:23:17.395: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-7phnv" in namespace "snapshotting-8157" to be "Succeeded or Failed"
Jun 10 08:23:17.501: INFO: Pod "pvc-snapshottable-tester-7phnv": Phase="Pending", Reason="", readiness=false. Elapsed: 106.065778ms
Jun 10 08:23:19.608: INFO: Pod "pvc-snapshottable-tester-7phnv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.212626917s
Jun 10 08:23:21.717: INFO: Pod "pvc-snapshottable-tester-7phnv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.321706106s
Jun 10 08:23:23.824: INFO: Pod "pvc-snapshottable-tester-7phnv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.428308706s
Jun 10 08:23:25.930: INFO: Pod "pvc-snapshottable-tester-7phnv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.534705604s
Jun 10 08:23:28.037: INFO: Pod "pvc-snapshottable-tester-7phnv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.641624658s
Jun 10 08:23:30.146: INFO: Pod "pvc-snapshottable-tester-7phnv": Phase="Pending", Reason="", readiness=false. Elapsed: 12.750371853s
Jun 10 08:23:32.253: INFO: Pod "pvc-snapshottable-tester-7phnv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.857680543s
STEP: Saw pod success
Jun 10 08:23:32.253: INFO: Pod "pvc-snapshottable-tester-7phnv" satisfied condition "Succeeded or Failed"
Jun 10 08:23:32.475: INFO: Pod pvc-snapshottable-tester-7phnv has the following logs: 
Jun 10 08:23:32.475: INFO: Deleting pod "pvc-snapshottable-tester-7phnv" in namespace "snapshotting-8157"
Jun 10 08:23:32.589: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-7phnv" to be fully deleted
Jun 10 08:23:32.695: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.com7vcgd] to have phase Bound
Jun 10 08:23:32.801: INFO: PersistentVolumeClaim ebs.csi.aws.com7vcgd found and phase=Bound (106.089833ms)
STEP: [init] checking the claim
... skipping 52 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.Y1KozJqJu/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 10 08:24:25.674: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-g684j" in namespace "snapshotting-8157" to be "Succeeded or Failed"
Jun 10 08:24:25.784: INFO: Pod "pvc-snapshottable-data-tester-g684j": Phase="Pending", Reason="", readiness=false. Elapsed: 109.397623ms
Jun 10 08:24:27.890: INFO: Pod "pvc-snapshottable-data-tester-g684j": Phase="Pending", Reason="", readiness=false. Elapsed: 2.215917307s
Jun 10 08:24:29.997: INFO: Pod "pvc-snapshottable-data-tester-g684j": Phase="Pending", Reason="", readiness=false. Elapsed: 4.323122415s
Jun 10 08:24:32.105: INFO: Pod "pvc-snapshottable-data-tester-g684j": Phase="Pending", Reason="", readiness=false. Elapsed: 6.431079984s
Jun 10 08:24:34.212: INFO: Pod "pvc-snapshottable-data-tester-g684j": Phase="Pending", Reason="", readiness=false. Elapsed: 8.538074532s
Jun 10 08:24:36.318: INFO: Pod "pvc-snapshottable-data-tester-g684j": Phase="Pending", Reason="", readiness=false. Elapsed: 10.64428062s
Jun 10 08:24:38.425: INFO: Pod "pvc-snapshottable-data-tester-g684j": Phase="Pending", Reason="", readiness=false. Elapsed: 12.751048875s
Jun 10 08:24:40.532: INFO: Pod "pvc-snapshottable-data-tester-g684j": Phase="Pending", Reason="", readiness=false. Elapsed: 14.857907081s
Jun 10 08:24:42.640: INFO: Pod "pvc-snapshottable-data-tester-g684j": Phase="Pending", Reason="", readiness=false. Elapsed: 16.965446074s
Jun 10 08:24:44.746: INFO: Pod "pvc-snapshottable-data-tester-g684j": Phase="Pending", Reason="", readiness=false. Elapsed: 19.07169234s
Jun 10 08:24:46.852: INFO: Pod "pvc-snapshottable-data-tester-g684j": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.178233166s
STEP: Saw pod success
Jun 10 08:24:46.852: INFO: Pod "pvc-snapshottable-data-tester-g684j" satisfied condition "Succeeded or Failed"
Jun 10 08:24:47.067: INFO: Pod pvc-snapshottable-data-tester-g684j has the following logs: 
Jun 10 08:24:47.067: INFO: Deleting pod "pvc-snapshottable-data-tester-g684j" in namespace "snapshotting-8157"
Jun 10 08:24:47.179: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-g684j" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 10 08:25:09.751: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-8157 exec restored-pvc-tester-9cgv5 --namespace=snapshotting-8157 -- cat /mnt/test/data'
... skipping 284 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Y1KozJqJu/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Y1KozJqJu/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.Y1KozJqJu/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.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Driver supports dynamic provisioning, skipping InlineVolume pattern

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.Y1KozJqJu/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.Y1KozJqJu/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.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 35 lines ...
Jun 10 08:23:16.280: INFO: Creating resource for dynamic PV
Jun 10 08:23:16.280: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-4602-e2e-scbt5k7
STEP: creating a claim
Jun 10 08:23:16.388: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 10 08:23:16.711: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-cmlhr" in namespace "snapshotting-4602" to be "Succeeded or Failed"
Jun 10 08:23:16.818: INFO: Pod "pvc-snapshottable-tester-cmlhr": Phase="Pending", Reason="", readiness=false. Elapsed: 106.967781ms
Jun 10 08:23:18.926: INFO: Pod "pvc-snapshottable-tester-cmlhr": Phase="Pending", Reason="", readiness=false. Elapsed: 2.215175012s
Jun 10 08:23:21.034: INFO: Pod "pvc-snapshottable-tester-cmlhr": Phase="Pending", Reason="", readiness=false. Elapsed: 4.323642939s
Jun 10 08:23:23.143: INFO: Pod "pvc-snapshottable-tester-cmlhr": Phase="Pending", Reason="", readiness=false. Elapsed: 6.432015219s
Jun 10 08:23:25.251: INFO: Pod "pvc-snapshottable-tester-cmlhr": Phase="Pending", Reason="", readiness=false. Elapsed: 8.540249458s
Jun 10 08:23:27.358: INFO: Pod "pvc-snapshottable-tester-cmlhr": Phase="Pending", Reason="", readiness=false. Elapsed: 10.647065994s
Jun 10 08:23:29.466: INFO: Pod "pvc-snapshottable-tester-cmlhr": Phase="Pending", Reason="", readiness=false. Elapsed: 12.75522769s
Jun 10 08:23:31.573: INFO: Pod "pvc-snapshottable-tester-cmlhr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.862402131s
STEP: Saw pod success
Jun 10 08:23:31.573: INFO: Pod "pvc-snapshottable-tester-cmlhr" satisfied condition "Succeeded or Failed"
Jun 10 08:23:31.791: INFO: Pod pvc-snapshottable-tester-cmlhr has the following logs: 
Jun 10 08:23:31.791: INFO: Deleting pod "pvc-snapshottable-tester-cmlhr" in namespace "snapshotting-4602"
Jun 10 08:23:31.904: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-cmlhr" to be fully deleted
Jun 10 08:23:32.010: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.compfnj7] to have phase Bound
Jun 10 08:23:32.117: INFO: PersistentVolumeClaim ebs.csi.aws.compfnj7 found and phase=Bound (106.49869ms)
STEP: [init] checking the claim
... skipping 24 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.Y1KozJqJu/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 10 08:24:02.833: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-nsfbl" in namespace "snapshotting-4602" to be "Succeeded or Failed"
Jun 10 08:24:02.940: INFO: Pod "pvc-snapshottable-data-tester-nsfbl": Phase="Pending", Reason="", readiness=false. Elapsed: 106.997055ms
Jun 10 08:24:05.047: INFO: Pod "pvc-snapshottable-data-tester-nsfbl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.214086981s
Jun 10 08:24:07.154: INFO: Pod "pvc-snapshottable-data-tester-nsfbl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.321443475s
Jun 10 08:24:09.263: INFO: Pod "pvc-snapshottable-data-tester-nsfbl": Phase="Pending", Reason="", readiness=false. Elapsed: 6.429847161s
Jun 10 08:24:11.372: INFO: Pod "pvc-snapshottable-data-tester-nsfbl": Phase="Pending", Reason="", readiness=false. Elapsed: 8.538532676s
Jun 10 08:24:13.480: INFO: Pod "pvc-snapshottable-data-tester-nsfbl": Phase="Pending", Reason="", readiness=false. Elapsed: 10.646914753s
Jun 10 08:24:15.589: INFO: Pod "pvc-snapshottable-data-tester-nsfbl": Phase="Pending", Reason="", readiness=false. Elapsed: 12.75575915s
Jun 10 08:24:17.696: INFO: Pod "pvc-snapshottable-data-tester-nsfbl": Phase="Pending", Reason="", readiness=false. Elapsed: 14.863001755s
Jun 10 08:24:19.809: INFO: Pod "pvc-snapshottable-data-tester-nsfbl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.97599051s
STEP: Saw pod success
Jun 10 08:24:19.809: INFO: Pod "pvc-snapshottable-data-tester-nsfbl" satisfied condition "Succeeded or Failed"
Jun 10 08:24:20.029: INFO: Pod pvc-snapshottable-data-tester-nsfbl has the following logs: 
Jun 10 08:24:20.029: INFO: Deleting pod "pvc-snapshottable-data-tester-nsfbl" in namespace "snapshotting-4602"
Jun 10 08:24:20.144: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-nsfbl" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 10 08:24:44.684: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-4602 exec restored-pvc-tester-85l4h --namespace=snapshotting-4602 -- cat /mnt/test/data'
... skipping 31 lines ...
Jun 10 08:25:10.692: INFO: volumesnapshotcontents snapcontent-9718920a-3cc9-44c4-b40e-df33a75a9a48 has been found and is not deleted
Jun 10 08:25:11.800: INFO: volumesnapshotcontents snapcontent-9718920a-3cc9-44c4-b40e-df33a75a9a48 has been found and is not deleted
Jun 10 08:25:12.908: INFO: volumesnapshotcontents snapcontent-9718920a-3cc9-44c4-b40e-df33a75a9a48 has been found and is not deleted
Jun 10 08:25:14.015: INFO: volumesnapshotcontents snapcontent-9718920a-3cc9-44c4-b40e-df33a75a9a48 has been found and is not deleted
Jun 10 08:25:15.123: INFO: volumesnapshotcontents snapcontent-9718920a-3cc9-44c4-b40e-df33a75a9a48 has been found and is not deleted
Jun 10 08:25:16.232: INFO: volumesnapshotcontents snapcontent-9718920a-3cc9-44c4-b40e-df33a75a9a48 has been found and is not deleted
Jun 10 08:25:17.233: INFO: WaitUntil failed after reaching the timeout 30s
[AfterEach] volume snapshot controller
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:221
Jun 10 08:25:17.356: INFO: Pod restored-pvc-tester-85l4h has the following logs: 
Jun 10 08:25:17.356: INFO: Deleting pod "restored-pvc-tester-85l4h" in namespace "snapshotting-4602"
Jun 10 08:25:17.464: INFO: Wait up to 5m0s for pod "restored-pvc-tester-85l4h" to be fully deleted
Jun 10 08:25:49.678: INFO: deleting claim "snapshotting-4602"/"pvc-gl4n6"
... skipping 279 lines ...
Jun 10 08:25:28.485: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8429p8ndb
STEP: creating a claim
Jun 10 08:25:28.592: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-l6pb
STEP: Creating a pod to test subpath
Jun 10 08:25:28.919: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-l6pb" in namespace "provisioning-8429" to be "Succeeded or Failed"
Jun 10 08:25:29.026: INFO: Pod "pod-subpath-test-dynamicpv-l6pb": Phase="Pending", Reason="", readiness=false. Elapsed: 106.289618ms
Jun 10 08:25:31.161: INFO: Pod "pod-subpath-test-dynamicpv-l6pb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.24179461s
Jun 10 08:25:33.268: INFO: Pod "pod-subpath-test-dynamicpv-l6pb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.348389542s
Jun 10 08:25:35.374: INFO: Pod "pod-subpath-test-dynamicpv-l6pb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.454791565s
Jun 10 08:25:37.481: INFO: Pod "pod-subpath-test-dynamicpv-l6pb": Phase="Pending", Reason="", readiness=false. Elapsed: 8.56144362s
Jun 10 08:25:39.587: INFO: Pod "pod-subpath-test-dynamicpv-l6pb": Phase="Pending", Reason="", readiness=false. Elapsed: 10.668109989s
... skipping 2 lines ...
Jun 10 08:25:45.919: INFO: Pod "pod-subpath-test-dynamicpv-l6pb": Phase="Pending", Reason="", readiness=false. Elapsed: 17.000090995s
Jun 10 08:25:48.026: INFO: Pod "pod-subpath-test-dynamicpv-l6pb": Phase="Pending", Reason="", readiness=false. Elapsed: 19.106616308s
Jun 10 08:25:50.134: INFO: Pod "pod-subpath-test-dynamicpv-l6pb": Phase="Pending", Reason="", readiness=false. Elapsed: 21.21496078s
Jun 10 08:25:52.241: INFO: Pod "pod-subpath-test-dynamicpv-l6pb": Phase="Pending", Reason="", readiness=false. Elapsed: 23.322064519s
Jun 10 08:25:54.358: INFO: Pod "pod-subpath-test-dynamicpv-l6pb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 25.438840817s
STEP: Saw pod success
Jun 10 08:25:54.358: INFO: Pod "pod-subpath-test-dynamicpv-l6pb" satisfied condition "Succeeded or Failed"
Jun 10 08:25:54.464: INFO: Trying to get logs from node ip-172-20-36-68.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-l6pb container test-container-volume-dynamicpv-l6pb: <nil>
STEP: delete the pod
Jun 10 08:25:54.696: INFO: Waiting for pod pod-subpath-test-dynamicpv-l6pb to disappear
Jun 10 08:25:54.802: INFO: Pod pod-subpath-test-dynamicpv-l6pb no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-l6pb
Jun 10 08:25:54.802: INFO: Deleting pod "pod-subpath-test-dynamicpv-l6pb" in namespace "provisioning-8429"
... skipping 28 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 08:25:42.333: 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.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 10 08:25:42.868: INFO: Creating resource for dynamic PV
Jun 10 08:25:42.868: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-6443-e2e-scpc9lf
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 10 08:25:49.633: INFO: Deleting pod "pod-207ece6a-904e-4b3a-be2f-175dca58d193" in namespace "volumemode-6443"
Jun 10 08:25:49.740: INFO: Wait up to 5m0s for pod "pod-207ece6a-904e-4b3a-be2f-175dca58d193" to be fully deleted
STEP: Deleting pvc
Jun 10 08:25:56.168: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comrq2gr"
Jun 10 08:25:56.278: INFO: Waiting up to 5m0s for PersistentVolume pvc-d2e7bf65-03e2-40ab-823f-82a2aba6a6e2 to get deleted
Jun 10 08:25:56.385: INFO: PersistentVolume pvc-d2e7bf65-03e2-40ab-823f-82a2aba6a6e2 found and phase=Released (106.823556ms)
... skipping 9 lines ...

• [SLOW TEST:29.700 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.Y1KozJqJu/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.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [sig-storage] Zone Support [Feature:vsphere]
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 08:26:12.034: INFO: >>> kubeConfig: /root/.kube/config
... skipping 31 lines ...
Jun 10 08:23:13.129: INFO: Creating resource for dynamic PV
Jun 10 08:23:13.129: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-6340-e2e-scchfjg
STEP: creating a claim
Jun 10 08:23:13.235: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 10 08:23:13.553: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-g4wm2" in namespace "snapshotting-6340" to be "Succeeded or Failed"
Jun 10 08:23:13.658: INFO: Pod "pvc-snapshottable-tester-g4wm2": Phase="Pending", Reason="", readiness=false. Elapsed: 105.051851ms
Jun 10 08:23:15.764: INFO: Pod "pvc-snapshottable-tester-g4wm2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.211132867s
Jun 10 08:23:17.869: INFO: Pod "pvc-snapshottable-tester-g4wm2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.316616376s
Jun 10 08:23:19.975: INFO: Pod "pvc-snapshottable-tester-g4wm2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.422781484s
Jun 10 08:23:22.085: INFO: Pod "pvc-snapshottable-tester-g4wm2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.532784088s
Jun 10 08:23:24.192: INFO: Pod "pvc-snapshottable-tester-g4wm2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.639663889s
... skipping 2 lines ...
Jun 10 08:23:30.511: INFO: Pod "pvc-snapshottable-tester-g4wm2": Phase="Pending", Reason="", readiness=false. Elapsed: 16.958853907s
Jun 10 08:23:32.617: INFO: Pod "pvc-snapshottable-tester-g4wm2": Phase="Pending", Reason="", readiness=false. Elapsed: 19.064856709s
Jun 10 08:23:34.731: INFO: Pod "pvc-snapshottable-tester-g4wm2": Phase="Pending", Reason="", readiness=false. Elapsed: 21.17887151s
Jun 10 08:23:36.838: INFO: Pod "pvc-snapshottable-tester-g4wm2": Phase="Pending", Reason="", readiness=false. Elapsed: 23.285188324s
Jun 10 08:23:38.945: INFO: Pod "pvc-snapshottable-tester-g4wm2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 25.392516826s
STEP: Saw pod success
Jun 10 08:23:38.945: INFO: Pod "pvc-snapshottable-tester-g4wm2" satisfied condition "Succeeded or Failed"
Jun 10 08:23:39.170: INFO: Pod pvc-snapshottable-tester-g4wm2 has the following logs: 
Jun 10 08:23:39.170: INFO: Deleting pod "pvc-snapshottable-tester-g4wm2" in namespace "snapshotting-6340"
Jun 10 08:23:39.280: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-g4wm2" to be fully deleted
Jun 10 08:23:39.385: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comqnzj7] to have phase Bound
Jun 10 08:23:39.494: INFO: PersistentVolumeClaim ebs.csi.aws.comqnzj7 found and phase=Bound (108.910689ms)
STEP: [init] checking the claim
... skipping 48 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.Y1KozJqJu/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 10 08:24:23.888: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-5dv7t" in namespace "snapshotting-6340" to be "Succeeded or Failed"
Jun 10 08:24:23.994: INFO: Pod "pvc-snapshottable-data-tester-5dv7t": Phase="Pending", Reason="", readiness=false. Elapsed: 106.209674ms
Jun 10 08:24:26.100: INFO: Pod "pvc-snapshottable-data-tester-5dv7t": Phase="Pending", Reason="", readiness=false. Elapsed: 2.211897635s
Jun 10 08:24:28.207: INFO: Pod "pvc-snapshottable-data-tester-5dv7t": Phase="Pending", Reason="", readiness=false. Elapsed: 4.318766373s
Jun 10 08:24:30.313: INFO: Pod "pvc-snapshottable-data-tester-5dv7t": Phase="Pending", Reason="", readiness=false. Elapsed: 6.425320487s
Jun 10 08:24:32.420: INFO: Pod "pvc-snapshottable-data-tester-5dv7t": Phase="Pending", Reason="", readiness=false. Elapsed: 8.532151059s
Jun 10 08:24:34.526: INFO: Pod "pvc-snapshottable-data-tester-5dv7t": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.638261515s
STEP: Saw pod success
Jun 10 08:24:34.526: INFO: Pod "pvc-snapshottable-data-tester-5dv7t" satisfied condition "Succeeded or Failed"
Jun 10 08:24:34.744: INFO: Pod pvc-snapshottable-data-tester-5dv7t has the following logs: 
Jun 10 08:24:34.744: INFO: Deleting pod "pvc-snapshottable-data-tester-5dv7t" in namespace "snapshotting-6340"
Jun 10 08:24:34.854: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-5dv7t" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 10 08:24:57.395: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-6340 exec restored-pvc-tester-kff7g --namespace=snapshotting-6340 -- cat /mnt/test/data'
... skipping 31 lines ...
Jun 10 08:25:23.387: INFO: volumesnapshotcontents pre-provisioned-snapcontent-e1d96d7d-8a9c-46bf-9973-1c664df4e052 has been found and is not deleted
Jun 10 08:25:24.494: INFO: volumesnapshotcontents pre-provisioned-snapcontent-e1d96d7d-8a9c-46bf-9973-1c664df4e052 has been found and is not deleted
Jun 10 08:25:25.600: INFO: volumesnapshotcontents pre-provisioned-snapcontent-e1d96d7d-8a9c-46bf-9973-1c664df4e052 has been found and is not deleted
Jun 10 08:25:26.707: INFO: volumesnapshotcontents pre-provisioned-snapcontent-e1d96d7d-8a9c-46bf-9973-1c664df4e052 has been found and is not deleted
Jun 10 08:25:27.813: INFO: volumesnapshotcontents pre-provisioned-snapcontent-e1d96d7d-8a9c-46bf-9973-1c664df4e052 has been found and is not deleted
Jun 10 08:25:28.924: INFO: volumesnapshotcontents pre-provisioned-snapcontent-e1d96d7d-8a9c-46bf-9973-1c664df4e052 has been found and is not deleted
Jun 10 08:25:29.924: INFO: WaitUntil failed after reaching the timeout 30s
[AfterEach] volume snapshot controller
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:221
Jun 10 08:25:30.031: INFO: Pod restored-pvc-tester-kff7g has the following logs: 
Jun 10 08:25:30.031: INFO: Deleting pod "restored-pvc-tester-kff7g" in namespace "snapshotting-6340"
Jun 10 08:25:30.137: INFO: Wait up to 5m0s for pod "restored-pvc-tester-kff7g" to be fully deleted
Jun 10 08:26:06.349: INFO: deleting claim "snapshotting-6340"/"pvc-64dgd"
... skipping 681 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.Y1KozJqJu/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.Y1KozJqJu/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.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 163 lines ...
Jun 10 08:25:39.669: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-4591-e2e-scc5wtq
STEP: creating a claim
Jun 10 08:25:39.774: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-qqst
STEP: Creating a pod to test exec-volume-test
Jun 10 08:25:40.093: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-qqst" in namespace "volume-4591" to be "Succeeded or Failed"
Jun 10 08:25:40.197: INFO: Pod "exec-volume-test-dynamicpv-qqst": Phase="Pending", Reason="", readiness=false. Elapsed: 104.67512ms
Jun 10 08:25:42.303: INFO: Pod "exec-volume-test-dynamicpv-qqst": Phase="Pending", Reason="", readiness=false. Elapsed: 2.21050565s
Jun 10 08:25:44.410: INFO: Pod "exec-volume-test-dynamicpv-qqst": Phase="Pending", Reason="", readiness=false. Elapsed: 4.317485862s
Jun 10 08:25:46.515: INFO: Pod "exec-volume-test-dynamicpv-qqst": Phase="Pending", Reason="", readiness=false. Elapsed: 6.422187281s
Jun 10 08:25:48.627: INFO: Pod "exec-volume-test-dynamicpv-qqst": Phase="Pending", Reason="", readiness=false. Elapsed: 8.534628901s
Jun 10 08:25:50.732: INFO: Pod "exec-volume-test-dynamicpv-qqst": Phase="Pending", Reason="", readiness=false. Elapsed: 10.6396993s
Jun 10 08:25:52.837: INFO: Pod "exec-volume-test-dynamicpv-qqst": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.74473123s
STEP: Saw pod success
Jun 10 08:25:52.837: INFO: Pod "exec-volume-test-dynamicpv-qqst" satisfied condition "Succeeded or Failed"
Jun 10 08:25:52.942: INFO: Trying to get logs from node ip-172-20-59-227.eu-west-2.compute.internal pod exec-volume-test-dynamicpv-qqst container exec-container-dynamicpv-qqst: <nil>
STEP: delete the pod
Jun 10 08:25:53.157: INFO: Waiting for pod exec-volume-test-dynamicpv-qqst to disappear
Jun 10 08:25:53.262: INFO: Pod exec-volume-test-dynamicpv-qqst no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-qqst
Jun 10 08:25:53.262: INFO: Deleting pod "exec-volume-test-dynamicpv-qqst" in namespace "volume-4591"
... skipping 171 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 08:26:00.095: 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.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun 10 08:26:00.631: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 10 08:26:00.631: INFO: Creating resource for dynamic PV
Jun 10 08:26:00.631: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3332qpp65
STEP: creating a claim
Jun 10 08:26:00.738: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-pl42
STEP: Checking for subpath error in container status
Jun 10 08:26:41.279: INFO: Deleting pod "pod-subpath-test-dynamicpv-pl42" in namespace "provisioning-3332"
Jun 10 08:26:41.390: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-pl42" to be fully deleted
STEP: Deleting pod
Jun 10 08:26:47.603: INFO: Deleting pod "pod-subpath-test-dynamicpv-pl42" in namespace "provisioning-3332"
STEP: Deleting pvc
Jun 10 08:26:47.925: INFO: Deleting PersistentVolumeClaim "awsjdkrv"
... skipping 13 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Y1KozJqJu/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Y1KozJqJu/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath directory is outside the volume [Slow][LinuxOnly]
      /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 10 08:27:03.810: INFO: Driver ebs.csi.aws.com doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning
... skipping 44 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 08:26:11.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 non-existent subpath is outside the volume [Slow][LinuxOnly]
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun 10 08:26:11.635: INFO: Creating resource for dynamic PV
Jun 10 08:26:11.635: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9814-e2e-scpgh86
STEP: creating a claim
Jun 10 08:26:11.742: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-8pzv
STEP: Checking for subpath error in container status
Jun 10 08:26:52.275: INFO: Deleting pod "pod-subpath-test-dynamicpv-8pzv" in namespace "provisioning-9814"
Jun 10 08:26:52.385: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-8pzv" to be fully deleted
STEP: Deleting pod
Jun 10 08:27:04.599: INFO: Deleting pod "pod-subpath-test-dynamicpv-8pzv" in namespace "provisioning-9814"
STEP: Deleting pvc
Jun 10 08:27:04.920: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comlj542"
... skipping 9 lines ...

• [SLOW TEST:59.471 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.Y1KozJqJu/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.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 10 08:27:10.566: INFO: Driver supports dynamic provisioning, skipping InlineVolume pattern
[AfterEach] [Testpattern: Inline-volume (default fs)] subPath
... skipping 149 lines ...
Jun 10 08:26:15.694: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3814w2q5w
STEP: creating a claim
Jun 10 08:26:15.800: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-r97q
STEP: Creating a pod to test subpath
Jun 10 08:26:16.122: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-r97q" in namespace "provisioning-3814" to be "Succeeded or Failed"
Jun 10 08:26:16.228: INFO: Pod "pod-subpath-test-dynamicpv-r97q": Phase="Pending", Reason="", readiness=false. Elapsed: 105.393119ms
Jun 10 08:26:18.334: INFO: Pod "pod-subpath-test-dynamicpv-r97q": Phase="Pending", Reason="", readiness=false. Elapsed: 2.211379414s
Jun 10 08:26:20.441: INFO: Pod "pod-subpath-test-dynamicpv-r97q": Phase="Pending", Reason="", readiness=false. Elapsed: 4.319068594s
Jun 10 08:26:22.548: INFO: Pod "pod-subpath-test-dynamicpv-r97q": Phase="Pending", Reason="", readiness=false. Elapsed: 6.425540334s
Jun 10 08:26:24.654: INFO: Pod "pod-subpath-test-dynamicpv-r97q": Phase="Pending", Reason="", readiness=false. Elapsed: 8.531271909s
Jun 10 08:26:26.760: INFO: Pod "pod-subpath-test-dynamicpv-r97q": Phase="Pending", Reason="", readiness=false. Elapsed: 10.637962078s
... skipping 8 lines ...
Jun 10 08:26:45.719: INFO: Pod "pod-subpath-test-dynamicpv-r97q": Phase="Pending", Reason="", readiness=false. Elapsed: 29.596609618s
Jun 10 08:26:47.824: INFO: Pod "pod-subpath-test-dynamicpv-r97q": Phase="Pending", Reason="", readiness=false. Elapsed: 31.701990334s
Jun 10 08:26:49.931: INFO: Pod "pod-subpath-test-dynamicpv-r97q": Phase="Pending", Reason="", readiness=false. Elapsed: 33.809005688s
Jun 10 08:26:52.038: INFO: Pod "pod-subpath-test-dynamicpv-r97q": Phase="Pending", Reason="", readiness=false. Elapsed: 35.915187395s
Jun 10 08:26:54.146: INFO: Pod "pod-subpath-test-dynamicpv-r97q": Phase="Succeeded", Reason="", readiness=false. Elapsed: 38.023149594s
STEP: Saw pod success
Jun 10 08:26:54.146: INFO: Pod "pod-subpath-test-dynamicpv-r97q" satisfied condition "Succeeded or Failed"
Jun 10 08:26:54.254: INFO: Trying to get logs from node ip-172-20-45-65.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-r97q container test-container-volume-dynamicpv-r97q: <nil>
STEP: delete the pod
Jun 10 08:26:54.477: INFO: Waiting for pod pod-subpath-test-dynamicpv-r97q to disappear
Jun 10 08:26:54.583: INFO: Pod pod-subpath-test-dynamicpv-r97q no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-r97q
Jun 10 08:26:54.583: INFO: Deleting pod "pod-subpath-test-dynamicpv-r97q" in namespace "provisioning-3814"
... skipping 364 lines ...
Jun 10 08:27:10.326: INFO: Waiting for pod aws-client to disappear
Jun 10 08:27:10.433: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 10 08:27:10.433: INFO: Deleting PersistentVolumeClaim "pvc-9882w"
Jun 10 08:27:10.542: INFO: Deleting PersistentVolume "aws-lnsmn"
Jun 10 08:27:11.164: INFO: Couldn't delete PD "aws://eu-west-2a/vol-00d052ffd2290ccaf", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00d052ffd2290ccaf is currently attached to i-0b68877733b8749cb
	status code: 400, request id: ca7dfb39-7df5-42bb-86ca-c37632619836
Jun 10 08:27:16.735: INFO: Couldn't delete PD "aws://eu-west-2a/vol-00d052ffd2290ccaf", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00d052ffd2290ccaf is currently attached to i-0b68877733b8749cb
	status code: 400, request id: 5409f2a3-ed86-4ba5-901e-6cd2f884d5f2
Jun 10 08:27:22.304: INFO: Successfully deleted PD "aws://eu-west-2a/vol-00d052ffd2290ccaf".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 10 08:27:22.304: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8623" for this suite.
... skipping 72 lines ...

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

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

    /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:92
------------------------------
... skipping 56 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 08:26:58.714: 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.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun 10 08:26:59.246: INFO: Creating resource for dynamic PV
Jun 10 08:26:59.246: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7787-e2e-sc4rnzc
STEP: creating a claim
Jun 10 08:26:59.353: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-p8gx
STEP: Checking for subpath error in container status
Jun 10 08:27:09.887: INFO: Deleting pod "pod-subpath-test-dynamicpv-p8gx" in namespace "provisioning-7787"
Jun 10 08:27:09.995: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-p8gx" to be fully deleted
STEP: Deleting pod
Jun 10 08:27:16.208: INFO: Deleting pod "pod-subpath-test-dynamicpv-p8gx" in namespace "provisioning-7787"
STEP: Deleting pvc
Jun 10 08:27:16.530: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comv5c4n"
... skipping 10 lines ...

• [SLOW TEST:28.568 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.Y1KozJqJu/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.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 6 lines ...
Jun 10 08:26:50.984: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 10 08:26:51.760: INFO: Successfully created a new PD: "aws://eu-west-2a/vol-04c2ddc2b94b9bed8".
Jun 10 08:26:51.760: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-rsbz
STEP: Creating a pod to test exec-volume-test
Jun 10 08:26:51.869: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-rsbz" in namespace "volume-4413" to be "Succeeded or Failed"
Jun 10 08:26:51.974: INFO: Pod "exec-volume-test-inlinevolume-rsbz": Phase="Pending", Reason="", readiness=false. Elapsed: 104.925946ms
Jun 10 08:26:54.081: INFO: Pod "exec-volume-test-inlinevolume-rsbz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.212036146s
Jun 10 08:26:56.188: INFO: Pod "exec-volume-test-inlinevolume-rsbz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.318597996s
Jun 10 08:26:58.294: INFO: Pod "exec-volume-test-inlinevolume-rsbz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.42441526s
Jun 10 08:27:00.400: INFO: Pod "exec-volume-test-inlinevolume-rsbz": Phase="Pending", Reason="", readiness=false. Elapsed: 8.530989451s
Jun 10 08:27:02.506: INFO: Pod "exec-volume-test-inlinevolume-rsbz": Phase="Pending", Reason="", readiness=false. Elapsed: 10.636573853s
Jun 10 08:27:04.613: INFO: Pod "exec-volume-test-inlinevolume-rsbz": Phase="Pending", Reason="", readiness=false. Elapsed: 12.743265774s
Jun 10 08:27:06.720: INFO: Pod "exec-volume-test-inlinevolume-rsbz": Phase="Pending", Reason="", readiness=false. Elapsed: 14.850541347s
Jun 10 08:27:08.827: INFO: Pod "exec-volume-test-inlinevolume-rsbz": Phase="Pending", Reason="", readiness=false. Elapsed: 16.957845368s
Jun 10 08:27:10.934: INFO: Pod "exec-volume-test-inlinevolume-rsbz": Phase="Pending", Reason="", readiness=false. Elapsed: 19.064589102s
Jun 10 08:27:13.039: INFO: Pod "exec-volume-test-inlinevolume-rsbz": Phase="Pending", Reason="", readiness=false. Elapsed: 21.170133355s
Jun 10 08:27:15.161: INFO: Pod "exec-volume-test-inlinevolume-rsbz": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.292075195s
STEP: Saw pod success
Jun 10 08:27:15.161: INFO: Pod "exec-volume-test-inlinevolume-rsbz" satisfied condition "Succeeded or Failed"
Jun 10 08:27:15.268: INFO: Trying to get logs from node ip-172-20-59-227.eu-west-2.compute.internal pod exec-volume-test-inlinevolume-rsbz container exec-container-inlinevolume-rsbz: <nil>
STEP: delete the pod
Jun 10 08:27:16.063: INFO: Waiting for pod exec-volume-test-inlinevolume-rsbz to disappear
Jun 10 08:27:16.169: INFO: Pod exec-volume-test-inlinevolume-rsbz no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-rsbz
Jun 10 08:27:16.169: INFO: Deleting pod "exec-volume-test-inlinevolume-rsbz" in namespace "volume-4413"
Jun 10 08:27:16.542: INFO: Couldn't delete PD "aws://eu-west-2a/vol-04c2ddc2b94b9bed8", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04c2ddc2b94b9bed8 is currently attached to i-0b68877733b8749cb
	status code: 400, request id: 72c5ca5b-948b-4cf3-9f8d-7c1ec7d3e483
Jun 10 08:27:22.108: INFO: Couldn't delete PD "aws://eu-west-2a/vol-04c2ddc2b94b9bed8", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04c2ddc2b94b9bed8 is currently attached to i-0b68877733b8749cb
	status code: 400, request id: 21d64cf5-e0bb-4f35-9a5f-8dc8f1837e27
Jun 10 08:27:27.691: INFO: Successfully deleted PD "aws://eu-west-2a/vol-04c2ddc2b94b9bed8".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 10 08:27:27.691: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-4413" for this suite.
... skipping 184 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Y1KozJqJu/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Y1KozJqJu/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.Y1KozJqJu/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.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 71 lines ...
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 08:27:31.654: 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.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Jun 10 08:27:32.295: INFO: found topology map[topology.kubernetes.io/zone:eu-west-2a]
Jun 10 08:27:32.296: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 10 08:27:32.296: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Y1KozJqJu/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Y1KozJqJu/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (immediate binding)] topology
    /tmp/kops.Y1KozJqJu/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.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 11 lines ...
Jun 10 08:26:53.368: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9201-e2e-scj7q2f
STEP: creating a claim
Jun 10 08:26:53.476: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-5smv
STEP: Creating a pod to test subpath
Jun 10 08:26:53.809: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-5smv" in namespace "provisioning-9201" to be "Succeeded or Failed"
Jun 10 08:26:53.916: INFO: Pod "pod-subpath-test-dynamicpv-5smv": Phase="Pending", Reason="", readiness=false. Elapsed: 106.759251ms
Jun 10 08:26:56.024: INFO: Pod "pod-subpath-test-dynamicpv-5smv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.2148973s
Jun 10 08:26:58.132: INFO: Pod "pod-subpath-test-dynamicpv-5smv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.322547087s
Jun 10 08:27:00.239: INFO: Pod "pod-subpath-test-dynamicpv-5smv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.429879777s
Jun 10 08:27:02.347: INFO: Pod "pod-subpath-test-dynamicpv-5smv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.537919103s
Jun 10 08:27:04.456: INFO: Pod "pod-subpath-test-dynamicpv-5smv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.646826832s
Jun 10 08:27:06.563: INFO: Pod "pod-subpath-test-dynamicpv-5smv": Phase="Pending", Reason="", readiness=false. Elapsed: 12.75386665s
Jun 10 08:27:08.674: INFO: Pod "pod-subpath-test-dynamicpv-5smv": Phase="Pending", Reason="", readiness=false. Elapsed: 14.864882715s
Jun 10 08:27:10.782: INFO: Pod "pod-subpath-test-dynamicpv-5smv": Phase="Pending", Reason="", readiness=false. Elapsed: 16.972237989s
Jun 10 08:27:12.889: INFO: Pod "pod-subpath-test-dynamicpv-5smv": Phase="Pending", Reason="", readiness=false. Elapsed: 19.079331073s
Jun 10 08:27:14.997: INFO: Pod "pod-subpath-test-dynamicpv-5smv": Phase="Pending", Reason="", readiness=false. Elapsed: 21.187589439s
Jun 10 08:27:17.110: INFO: Pod "pod-subpath-test-dynamicpv-5smv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.300223119s
STEP: Saw pod success
Jun 10 08:27:17.110: INFO: Pod "pod-subpath-test-dynamicpv-5smv" satisfied condition "Succeeded or Failed"
Jun 10 08:27:17.216: INFO: Trying to get logs from node ip-172-20-36-68.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-5smv container test-container-subpath-dynamicpv-5smv: <nil>
STEP: delete the pod
Jun 10 08:27:17.443: INFO: Waiting for pod pod-subpath-test-dynamicpv-5smv to disappear
Jun 10 08:27:17.550: INFO: Pod pod-subpath-test-dynamicpv-5smv no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-5smv
Jun 10 08:27:17.550: INFO: Deleting pod "pod-subpath-test-dynamicpv-5smv" in namespace "provisioning-9201"
... skipping 57 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Y1KozJqJu/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Y1KozJqJu/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.Y1KozJqJu/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.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.Y1KozJqJu/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.Y1KozJqJu/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.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 71 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 08:27:16.754: 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.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun 10 08:27:17.284: INFO: Creating resource for dynamic PV
Jun 10 08:27:17.284: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9051-e2e-scr4qnz
STEP: creating a claim
Jun 10 08:27:17.395: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-rsc7
STEP: Checking for subpath error in container status
Jun 10 08:27:31.925: INFO: Deleting pod "pod-subpath-test-dynamicpv-rsc7" in namespace "provisioning-9051"
Jun 10 08:27:32.032: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-rsc7" to be fully deleted
STEP: Deleting pod
Jun 10 08:27:46.245: INFO: Deleting pod "pod-subpath-test-dynamicpv-rsc7" in namespace "provisioning-9051"
STEP: Deleting pvc
Jun 10 08:27:46.560: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com5nprj"
... skipping 9 lines ...

• [SLOW TEST:35.443 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath file is outside the volume [Slow][LinuxOnly]
    /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 177 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 08:27:27.284: 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.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun 10 08:27:27.818: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 10 08:27:27.818: INFO: Creating resource for dynamic PV
Jun 10 08:27:27.819: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-73838hq2n
STEP: creating a claim
Jun 10 08:27:27.927: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-qdjr
STEP: Checking for subpath error in container status
Jun 10 08:27:44.468: INFO: Deleting pod "pod-subpath-test-dynamicpv-qdjr" in namespace "provisioning-7383"
Jun 10 08:27:44.578: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-qdjr" to be fully deleted
STEP: Deleting pod
Jun 10 08:27:56.792: INFO: Deleting pod "pod-subpath-test-dynamicpv-qdjr" in namespace "provisioning-7383"
STEP: Deleting pvc
Jun 10 08:27:57.113: INFO: Deleting PersistentVolumeClaim "awsvjfmn"
... skipping 11 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Y1KozJqJu/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Y1KozJqJu/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.Y1KozJqJu/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.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 154 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Y1KozJqJu/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Y1KozJqJu/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.Y1KozJqJu/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.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 157 lines ...
Jun 10 08:27:58.937: INFO: Waiting for pod aws-client to disappear
Jun 10 08:27:59.043: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 10 08:27:59.043: INFO: Deleting PersistentVolumeClaim "pvc-sknfb"
Jun 10 08:27:59.149: INFO: Deleting PersistentVolume "aws-5pkg6"
Jun 10 08:27:59.820: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0f28035cdae183b40", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f28035cdae183b40 is currently attached to i-0b68877733b8749cb
	status code: 400, request id: cc71e366-ead8-444c-9574-4b0a93986832
Jun 10 08:28:05.377: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0f28035cdae183b40", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f28035cdae183b40 is currently attached to i-0b68877733b8749cb
	status code: 400, request id: 695a2806-5f1f-4275-9ce0-39bcea130aa8
Jun 10 08:28:10.972: INFO: Successfully deleted PD "aws://eu-west-2a/vol-0f28035cdae183b40".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumes
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 10 08:28:10.972: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-1155" for this suite.
... skipping 109 lines ...
Jun 10 08:27:52.727: INFO: Creating resource for dynamic PV
Jun 10 08:27:52.727: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-9131-e2e-scrl9hf
STEP: creating a claim
STEP: Expanding non-expandable pvc
Jun 10 08:27:53.045: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 10 08:27:53.257: INFO: Error updating pvc ebs.csi.aws.com5bcnx: PersistentVolumeClaim "ebs.csi.aws.com5bcnx" 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-9131-e2e-scrl9hf",
  	... // 2 identical fields
  }

Jun 10 08:27:55.468: INFO: Error updating pvc ebs.csi.aws.com5bcnx: PersistentVolumeClaim "ebs.csi.aws.com5bcnx" 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-9131-e2e-scrl9hf",
  	... // 2 identical fields
  }

Jun 10 08:27:57.488: INFO: Error updating pvc ebs.csi.aws.com5bcnx: PersistentVolumeClaim "ebs.csi.aws.com5bcnx" 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-9131-e2e-scrl9hf",
  	... // 2 identical fields
  }

Jun 10 08:27:59.469: INFO: Error updating pvc ebs.csi.aws.com5bcnx: PersistentVolumeClaim "ebs.csi.aws.com5bcnx" 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-9131-e2e-scrl9hf",
  	... // 2 identical fields
  }

Jun 10 08:28:01.471: INFO: Error updating pvc ebs.csi.aws.com5bcnx: PersistentVolumeClaim "ebs.csi.aws.com5bcnx" 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-9131-e2e-scrl9hf",
  	... // 2 identical fields
  }

Jun 10 08:28:03.468: INFO: Error updating pvc ebs.csi.aws.com5bcnx: PersistentVolumeClaim "ebs.csi.aws.com5bcnx" 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-9131-e2e-scrl9hf",
  	... // 2 identical fields
  }

Jun 10 08:28:05.468: INFO: Error updating pvc ebs.csi.aws.com5bcnx: PersistentVolumeClaim "ebs.csi.aws.com5bcnx" 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-9131-e2e-scrl9hf",
  	... // 2 identical fields
  }

Jun 10 08:28:07.469: INFO: Error updating pvc ebs.csi.aws.com5bcnx: PersistentVolumeClaim "ebs.csi.aws.com5bcnx" 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-9131-e2e-scrl9hf",
  	... // 2 identical fields
  }

Jun 10 08:28:09.469: INFO: Error updating pvc ebs.csi.aws.com5bcnx: PersistentVolumeClaim "ebs.csi.aws.com5bcnx" 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-9131-e2e-scrl9hf",
  	... // 2 identical fields
  }

Jun 10 08:28:11.469: INFO: Error updating pvc ebs.csi.aws.com5bcnx: PersistentVolumeClaim "ebs.csi.aws.com5bcnx" 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-9131-e2e-scrl9hf",
  	... // 2 identical fields
  }

Jun 10 08:28:13.470: INFO: Error updating pvc ebs.csi.aws.com5bcnx: PersistentVolumeClaim "ebs.csi.aws.com5bcnx" 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-9131-e2e-scrl9hf",
  	... // 2 identical fields
  }

Jun 10 08:28:15.470: INFO: Error updating pvc ebs.csi.aws.com5bcnx: PersistentVolumeClaim "ebs.csi.aws.com5bcnx" 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-9131-e2e-scrl9hf",
  	... // 2 identical fields
  }

Jun 10 08:28:17.470: INFO: Error updating pvc ebs.csi.aws.com5bcnx: PersistentVolumeClaim "ebs.csi.aws.com5bcnx" 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-9131-e2e-scrl9hf",
  	... // 2 identical fields
  }

Jun 10 08:28:19.470: INFO: Error updating pvc ebs.csi.aws.com5bcnx: PersistentVolumeClaim "ebs.csi.aws.com5bcnx" 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-9131-e2e-scrl9hf",
  	... // 2 identical fields
  }

Jun 10 08:28:21.470: INFO: Error updating pvc ebs.csi.aws.com5bcnx: PersistentVolumeClaim "ebs.csi.aws.com5bcnx" 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-9131-e2e-scrl9hf",
  	... // 2 identical fields
  }

Jun 10 08:28:23.472: INFO: Error updating pvc ebs.csi.aws.com5bcnx: PersistentVolumeClaim "ebs.csi.aws.com5bcnx" 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-9131-e2e-scrl9hf",
  	... // 2 identical fields
  }

Jun 10 08:28:23.683: INFO: Error updating pvc ebs.csi.aws.com5bcnx: PersistentVolumeClaim "ebs.csi.aws.com5bcnx" 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 81 lines ...
Jun 10 08:27:52.981: INFO: Creating resource for dynamic PV
Jun 10 08:27:52.981: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-6941zf9g9
STEP: creating a claim
STEP: Expanding non-expandable pvc
Jun 10 08:27:53.303: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 10 08:27:53.518: INFO: Error updating pvc awsxrm9c: PersistentVolumeClaim "awsxrm9c" 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-6941zf9g9",
  	... // 2 identical fields
  }

Jun 10 08:27:55.733: INFO: Error updating pvc awsxrm9c: PersistentVolumeClaim "awsxrm9c" 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-6941zf9g9",
  	... // 2 identical fields
  }

Jun 10 08:27:57.736: INFO: Error updating pvc awsxrm9c: PersistentVolumeClaim "awsxrm9c" 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-6941zf9g9",
  	... // 2 identical fields
  }

Jun 10 08:27:59.736: INFO: Error updating pvc awsxrm9c: PersistentVolumeClaim "awsxrm9c" 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-6941zf9g9",
  	... // 2 identical fields
  }

Jun 10 08:28:01.736: INFO: Error updating pvc awsxrm9c: PersistentVolumeClaim "awsxrm9c" 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-6941zf9g9",
  	... // 2 identical fields
  }

Jun 10 08:28:03.733: INFO: Error updating pvc awsxrm9c: PersistentVolumeClaim "awsxrm9c" 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-6941zf9g9",
  	... // 2 identical fields
  }

Jun 10 08:28:05.733: INFO: Error updating pvc awsxrm9c: PersistentVolumeClaim "awsxrm9c" 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-6941zf9g9",
  	... // 2 identical fields
  }

Jun 10 08:28:07.733: INFO: Error updating pvc awsxrm9c: PersistentVolumeClaim "awsxrm9c" 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-6941zf9g9",
  	... // 2 identical fields
  }

Jun 10 08:28:09.734: INFO: Error updating pvc awsxrm9c: PersistentVolumeClaim "awsxrm9c" 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-6941zf9g9",
  	... // 2 identical fields
  }

Jun 10 08:28:11.732: INFO: Error updating pvc awsxrm9c: PersistentVolumeClaim "awsxrm9c" 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-6941zf9g9",
  	... // 2 identical fields
  }

Jun 10 08:28:13.733: INFO: Error updating pvc awsxrm9c: PersistentVolumeClaim "awsxrm9c" 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-6941zf9g9",
  	... // 2 identical fields
  }

Jun 10 08:28:15.732: INFO: Error updating pvc awsxrm9c: PersistentVolumeClaim "awsxrm9c" 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-6941zf9g9",
  	... // 2 identical fields
  }

Jun 10 08:28:17.732: INFO: Error updating pvc awsxrm9c: PersistentVolumeClaim "awsxrm9c" 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-6941zf9g9",
  	... // 2 identical fields
  }

Jun 10 08:28:19.732: INFO: Error updating pvc awsxrm9c: PersistentVolumeClaim "awsxrm9c" 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-6941zf9g9",
  	... // 2 identical fields
  }

Jun 10 08:28:21.734: INFO: Error updating pvc awsxrm9c: PersistentVolumeClaim "awsxrm9c" 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-6941zf9g9",
  	... // 2 identical fields
  }

Jun 10 08:28:23.734: INFO: Error updating pvc awsxrm9c: PersistentVolumeClaim "awsxrm9c" 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-6941zf9g9",
  	... // 2 identical fields
  }

Jun 10 08:28:23.948: INFO: Error updating pvc awsxrm9c: PersistentVolumeClaim "awsxrm9c" 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 42 lines ...
Jun 10 08:27:47.338: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-8644lfjfh
STEP: creating a claim
Jun 10 08:27:47.444: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-mvwd
STEP: Creating a pod to test exec-volume-test
Jun 10 08:27:47.764: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-mvwd" in namespace "volume-8644" to be "Succeeded or Failed"
Jun 10 08:27:47.869: INFO: Pod "exec-volume-test-dynamicpv-mvwd": Phase="Pending", Reason="", readiness=false. Elapsed: 105.612094ms
Jun 10 08:27:49.979: INFO: Pod "exec-volume-test-dynamicpv-mvwd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.215689628s
Jun 10 08:27:52.086: INFO: Pod "exec-volume-test-dynamicpv-mvwd": Phase="Pending", Reason="", readiness=false. Elapsed: 4.322316058s
Jun 10 08:27:54.192: INFO: Pod "exec-volume-test-dynamicpv-mvwd": Phase="Pending", Reason="", readiness=false. Elapsed: 6.428837735s
Jun 10 08:27:56.298: INFO: Pod "exec-volume-test-dynamicpv-mvwd": Phase="Pending", Reason="", readiness=false. Elapsed: 8.534912266s
Jun 10 08:27:58.405: INFO: Pod "exec-volume-test-dynamicpv-mvwd": Phase="Pending", Reason="", readiness=false. Elapsed: 10.641623868s
Jun 10 08:28:00.512: INFO: Pod "exec-volume-test-dynamicpv-mvwd": Phase="Pending", Reason="", readiness=false. Elapsed: 12.748738979s
Jun 10 08:28:02.619: INFO: Pod "exec-volume-test-dynamicpv-mvwd": Phase="Pending", Reason="", readiness=false. Elapsed: 14.855760057s
Jun 10 08:28:04.726: INFO: Pod "exec-volume-test-dynamicpv-mvwd": Phase="Pending", Reason="", readiness=false. Elapsed: 16.962834358s
Jun 10 08:28:06.833: INFO: Pod "exec-volume-test-dynamicpv-mvwd": Phase="Pending", Reason="", readiness=false. Elapsed: 19.069646571s
Jun 10 08:28:08.941: INFO: Pod "exec-volume-test-dynamicpv-mvwd": Phase="Pending", Reason="", readiness=false. Elapsed: 21.177406245s
Jun 10 08:28:11.048: INFO: Pod "exec-volume-test-dynamicpv-mvwd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.284624796s
STEP: Saw pod success
Jun 10 08:28:11.048: INFO: Pod "exec-volume-test-dynamicpv-mvwd" satisfied condition "Succeeded or Failed"
Jun 10 08:28:11.155: INFO: Trying to get logs from node ip-172-20-36-68.eu-west-2.compute.internal pod exec-volume-test-dynamicpv-mvwd container exec-container-dynamicpv-mvwd: <nil>
STEP: delete the pod
Jun 10 08:28:11.377: INFO: Waiting for pod exec-volume-test-dynamicpv-mvwd to disappear
Jun 10 08:28:11.482: INFO: Pod exec-volume-test-dynamicpv-mvwd no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-mvwd
Jun 10 08:28:11.482: INFO: Deleting pod "exec-volume-test-dynamicpv-mvwd" in namespace "volume-8644"
... skipping 64 lines ...
Jun 10 08:28:29.172: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 11 lines ...
Jun 10 08:27:35.151: INFO: Creating resource for dynamic PV
Jun 10 08:27:35.151: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1786w8d2
STEP: creating a claim
Jun 10 08:27:35.259: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-178
Jun 10 08:27:35.582: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-178" in namespace "provisioning-178" to be "Succeeded or Failed"
Jun 10 08:27:35.692: INFO: Pod "volume-prep-provisioning-178": Phase="Pending", Reason="", readiness=false. Elapsed: 110.01814ms
Jun 10 08:27:37.800: INFO: Pod "volume-prep-provisioning-178": Phase="Pending", Reason="", readiness=false. Elapsed: 2.217723886s
Jun 10 08:27:39.907: INFO: Pod "volume-prep-provisioning-178": Phase="Pending", Reason="", readiness=false. Elapsed: 4.32503703s
Jun 10 08:27:42.015: INFO: Pod "volume-prep-provisioning-178": Phase="Pending", Reason="", readiness=false. Elapsed: 6.432889003s
Jun 10 08:27:44.122: INFO: Pod "volume-prep-provisioning-178": Phase="Pending", Reason="", readiness=false. Elapsed: 8.539757073s
Jun 10 08:27:46.231: INFO: Pod "volume-prep-provisioning-178": Phase="Pending", Reason="", readiness=false. Elapsed: 10.648775752s
Jun 10 08:27:48.338: INFO: Pod "volume-prep-provisioning-178": Phase="Pending", Reason="", readiness=false. Elapsed: 12.756163865s
Jun 10 08:27:50.452: INFO: Pod "volume-prep-provisioning-178": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.869364705s
STEP: Saw pod success
Jun 10 08:27:50.452: INFO: Pod "volume-prep-provisioning-178" satisfied condition "Succeeded or Failed"
Jun 10 08:27:50.452: INFO: Deleting pod "volume-prep-provisioning-178" in namespace "provisioning-178"
Jun 10 08:27:50.565: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-178" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-6vgp
STEP: Checking for subpath error in container status
Jun 10 08:28:10.995: INFO: Deleting pod "pod-subpath-test-dynamicpv-6vgp" in namespace "provisioning-178"
Jun 10 08:28:11.107: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-6vgp" to be fully deleted
STEP: Deleting pod
Jun 10 08:28:11.214: INFO: Deleting pod "pod-subpath-test-dynamicpv-6vgp" in namespace "provisioning-178"
STEP: Deleting pvc
Jun 10 08:28:11.533: INFO: Deleting PersistentVolumeClaim "awsrkhp9"
... skipping 175 lines ...
Jun 10 08:28:29.003: INFO: Pod aws-client still exists
Jun 10 08:28:30.896: INFO: Waiting for pod aws-client to disappear
Jun 10 08:28:31.003: INFO: Pod aws-client still exists
Jun 10 08:28:32.895: INFO: Waiting for pod aws-client to disappear
Jun 10 08:28:33.002: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun 10 08:28:33.565: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0fff8b3f8e352096d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0fff8b3f8e352096d is currently attached to i-0ff665d16f07b5536
	status code: 400, request id: 0818acab-dc27-4b44-b26d-ca2ac3309dd2
Jun 10 08:28:39.134: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0fff8b3f8e352096d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0fff8b3f8e352096d is currently attached to i-0ff665d16f07b5536
	status code: 400, request id: fd32474e-a89f-4182-bedd-7bdd1e59bb35
Jun 10 08:28:44.702: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0fff8b3f8e352096d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0fff8b3f8e352096d is currently attached to i-0ff665d16f07b5536
	status code: 400, request id: 6321a87d-d45e-4110-bd53-5099b2804538
Jun 10 08:28:50.250: INFO: Successfully deleted PD "aws://eu-west-2a/vol-0fff8b3f8e352096d".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 10 08:28:50.250: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-5748" for this suite.
... skipping 180 lines ...
Jun 10 08:27:00.895: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-121456rxk      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-1214    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-121456rxk,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-1214    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-121456rxk,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-1214    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-121456rxk,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-121456rxk    b3f7f041-df05-4547-a0b4-ced6cddc128e 11876 0 2021-06-10 08:27:01 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-10 08:27:01 +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-8xqp9 pvc- provisioning-1214  cdc10870-8572-4954-b556-b8786bf16478 11884 0 2021-06-10 08:27:01 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-10 08:27:01 +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-121456rxk,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-1829e3dc-15e0-4c59-aba6-97e1000138ca in namespace provisioning-1214
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun 10 08:27:18.089: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-bnkk4" in namespace "provisioning-1214" to be "Succeeded or Failed"
Jun 10 08:27:18.195: INFO: Pod "pvc-volume-tester-writer-bnkk4": Phase="Pending", Reason="", readiness=false. Elapsed: 105.993755ms
Jun 10 08:27:20.302: INFO: Pod "pvc-volume-tester-writer-bnkk4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.213326614s
Jun 10 08:27:22.409: INFO: Pod "pvc-volume-tester-writer-bnkk4": Phase="Pending", Reason="", readiness=false. Elapsed: 4.320057197s
Jun 10 08:27:24.516: INFO: Pod "pvc-volume-tester-writer-bnkk4": Phase="Pending", Reason="", readiness=false. Elapsed: 6.427304213s
Jun 10 08:27:26.623: INFO: Pod "pvc-volume-tester-writer-bnkk4": Phase="Pending", Reason="", readiness=false. Elapsed: 8.534080445s
Jun 10 08:27:28.732: INFO: Pod "pvc-volume-tester-writer-bnkk4": Phase="Pending", Reason="", readiness=false. Elapsed: 10.643422685s
... skipping 22 lines ...
Jun 10 08:28:17.203: INFO: Pod "pvc-volume-tester-writer-bnkk4": Phase="Pending", Reason="", readiness=false. Elapsed: 59.113824112s
Jun 10 08:28:19.310: INFO: Pod "pvc-volume-tester-writer-bnkk4": Phase="Pending", Reason="", readiness=false. Elapsed: 1m1.221341931s
Jun 10 08:28:21.418: INFO: Pod "pvc-volume-tester-writer-bnkk4": Phase="Pending", Reason="", readiness=false. Elapsed: 1m3.32855061s
Jun 10 08:28:23.524: INFO: Pod "pvc-volume-tester-writer-bnkk4": Phase="Pending", Reason="", readiness=false. Elapsed: 1m5.434912344s
Jun 10 08:28:25.635: INFO: Pod "pvc-volume-tester-writer-bnkk4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m7.545515874s
STEP: Saw pod success
Jun 10 08:28:25.635: INFO: Pod "pvc-volume-tester-writer-bnkk4" satisfied condition "Succeeded or Failed"
Jun 10 08:28:25.848: INFO: Pod pvc-volume-tester-writer-bnkk4 has the following logs: 
Jun 10 08:28:25.848: INFO: Deleting pod "pvc-volume-tester-writer-bnkk4" in namespace "provisioning-1214"
Jun 10 08:28:25.967: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-bnkk4" 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-36-68.eu-west-2.compute.internal"
Jun 10 08:28:26.397: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-fkj2f" in namespace "provisioning-1214" to be "Succeeded or Failed"
Jun 10 08:28:26.503: INFO: Pod "pvc-volume-tester-reader-fkj2f": Phase="Pending", Reason="", readiness=false. Elapsed: 105.985223ms
Jun 10 08:28:28.610: INFO: Pod "pvc-volume-tester-reader-fkj2f": Phase="Pending", Reason="", readiness=false. Elapsed: 2.212917048s
Jun 10 08:28:30.716: INFO: Pod "pvc-volume-tester-reader-fkj2f": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.319009344s
STEP: Saw pod success
Jun 10 08:28:30.716: INFO: Pod "pvc-volume-tester-reader-fkj2f" satisfied condition "Succeeded or Failed"
Jun 10 08:28:30.931: INFO: Pod pvc-volume-tester-reader-fkj2f has the following logs: hello world

Jun 10 08:28:30.931: INFO: Deleting pod "pvc-volume-tester-reader-fkj2f" in namespace "provisioning-1214"
Jun 10 08:28:31.042: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-fkj2f" to be fully deleted
Jun 10 08:28:31.148: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-8xqp9] to have phase Bound
Jun 10 08:28:31.254: INFO: PersistentVolumeClaim pvc-8xqp9 found and phase=Bound (105.753971ms)
... skipping 164 lines ...
Jun 10 08:28:25.030: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4099nmz98
STEP: creating a claim
Jun 10 08:28:25.138: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-tcv9
STEP: Creating a pod to test subpath
Jun 10 08:28:25.463: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-tcv9" in namespace "provisioning-4099" to be "Succeeded or Failed"
Jun 10 08:28:25.573: INFO: Pod "pod-subpath-test-dynamicpv-tcv9": Phase="Pending", Reason="", readiness=false. Elapsed: 109.777797ms
Jun 10 08:28:27.680: INFO: Pod "pod-subpath-test-dynamicpv-tcv9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.217300226s
Jun 10 08:28:29.788: INFO: Pod "pod-subpath-test-dynamicpv-tcv9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.32494646s
Jun 10 08:28:31.896: INFO: Pod "pod-subpath-test-dynamicpv-tcv9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.433561991s
Jun 10 08:28:34.003: INFO: Pod "pod-subpath-test-dynamicpv-tcv9": Phase="Pending", Reason="", readiness=false. Elapsed: 8.540496312s
Jun 10 08:28:36.111: INFO: Pod "pod-subpath-test-dynamicpv-tcv9": Phase="Pending", Reason="", readiness=false. Elapsed: 10.648509288s
Jun 10 08:28:38.218: INFO: Pod "pod-subpath-test-dynamicpv-tcv9": Phase="Pending", Reason="", readiness=false. Elapsed: 12.755359789s
Jun 10 08:28:40.326: INFO: Pod "pod-subpath-test-dynamicpv-tcv9": Phase="Pending", Reason="", readiness=false. Elapsed: 14.863248434s
Jun 10 08:28:42.439: INFO: Pod "pod-subpath-test-dynamicpv-tcv9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.976509057s
STEP: Saw pod success
Jun 10 08:28:42.439: INFO: Pod "pod-subpath-test-dynamicpv-tcv9" satisfied condition "Succeeded or Failed"
Jun 10 08:28:42.551: INFO: Trying to get logs from node ip-172-20-36-68.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-tcv9 container test-container-subpath-dynamicpv-tcv9: <nil>
STEP: delete the pod
Jun 10 08:28:42.789: INFO: Waiting for pod pod-subpath-test-dynamicpv-tcv9 to disappear
Jun 10 08:28:42.896: INFO: Pod pod-subpath-test-dynamicpv-tcv9 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-tcv9
Jun 10 08:28:42.896: INFO: Deleting pod "pod-subpath-test-dynamicpv-tcv9" in namespace "provisioning-4099"
... skipping 85 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 08:28:37.624: 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.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 10 08:28:38.158: INFO: Creating resource for dynamic PV
Jun 10 08:28:38.158: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-9777-e2e-sc9pmff
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 10 08:28:44.923: INFO: Deleting pod "pod-ae7fa668-ba34-40d7-9c52-d6b8d99ad242" in namespace "volumemode-9777"
Jun 10 08:28:45.033: INFO: Wait up to 5m0s for pod "pod-ae7fa668-ba34-40d7-9c52-d6b8d99ad242" to be fully deleted
STEP: Deleting pvc
Jun 10 08:28:55.461: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comdmb9r"
Jun 10 08:28:55.569: INFO: Waiting up to 5m0s for PersistentVolume pvc-4380b0dd-7976-4b65-8d72-5dc8f77ff1a7 to get deleted
Jun 10 08:28:55.680: INFO: PersistentVolume pvc-4380b0dd-7976-4b65-8d72-5dc8f77ff1a7 found and phase=Released (110.972277ms)
... skipping 9 lines ...

• [SLOW TEST:33.717 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.Y1KozJqJu/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.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 369 lines ...
Jun 10 08:25:36.978: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7372-e2e-scxv47j
STEP: creating a claim
Jun 10 08:25:37.086: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-66dz
STEP: Creating a pod to test atomic-volume-subpath
Jun 10 08:25:37.413: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-66dz" in namespace "provisioning-7372" to be "Succeeded or Failed"
Jun 10 08:25:37.520: INFO: Pod "pod-subpath-test-dynamicpv-66dz": Phase="Pending", Reason="", readiness=false. Elapsed: 106.324906ms
Jun 10 08:25:39.626: INFO: Pod "pod-subpath-test-dynamicpv-66dz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.212906004s
Jun 10 08:25:41.734: INFO: Pod "pod-subpath-test-dynamicpv-66dz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.320707487s
Jun 10 08:25:43.856: INFO: Pod "pod-subpath-test-dynamicpv-66dz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.443014399s
Jun 10 08:25:45.967: INFO: Pod "pod-subpath-test-dynamicpv-66dz": Phase="Pending", Reason="", readiness=false. Elapsed: 8.553721603s
Jun 10 08:25:48.073: INFO: Pod "pod-subpath-test-dynamicpv-66dz": Phase="Pending", Reason="", readiness=false. Elapsed: 10.65995757s
... skipping 123 lines ...
Jun 10 08:30:09.411: INFO: Pod "pod-subpath-test-dynamicpv-66dz": Phase="Running", Reason="", readiness=true. Elapsed: 4m31.997274046s
Jun 10 08:30:11.518: INFO: Pod "pod-subpath-test-dynamicpv-66dz": Phase="Running", Reason="", readiness=true. Elapsed: 4m34.104458372s
Jun 10 08:30:13.625: INFO: Pod "pod-subpath-test-dynamicpv-66dz": Phase="Running", Reason="", readiness=true. Elapsed: 4m36.21172344s
Jun 10 08:30:15.732: INFO: Pod "pod-subpath-test-dynamicpv-66dz": Phase="Running", Reason="", readiness=true. Elapsed: 4m38.318867552s
Jun 10 08:30:17.838: INFO: Pod "pod-subpath-test-dynamicpv-66dz": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4m40.425082858s
STEP: Saw pod success
Jun 10 08:30:17.840: INFO: Pod "pod-subpath-test-dynamicpv-66dz" satisfied condition "Succeeded or Failed"
Jun 10 08:30:17.946: INFO: Trying to get logs from node ip-172-20-58-127.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-66dz container test-container-subpath-dynamicpv-66dz: <nil>
STEP: delete the pod
Jun 10 08:30:18.188: INFO: Waiting for pod pod-subpath-test-dynamicpv-66dz to disappear
Jun 10 08:30:18.294: INFO: Pod pod-subpath-test-dynamicpv-66dz no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-66dz
Jun 10 08:30:18.294: INFO: Deleting pod "pod-subpath-test-dynamicpv-66dz" in namespace "provisioning-7372"
... skipping 83 lines ...
Jun 10 08:25:45.535: INFO: Creating resource for dynamic PV
Jun 10 08:25:45.535: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-451-e2e-sck8xqj
STEP: creating a claim
Jun 10 08:25:45.646: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-451
Jun 10 08:25:45.983: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-451" in namespace "provisioning-451" to be "Succeeded or Failed"
Jun 10 08:25:46.093: INFO: Pod "volume-prep-provisioning-451": Phase="Pending", Reason="", readiness=false. Elapsed: 109.431724ms
Jun 10 08:25:48.199: INFO: Pod "volume-prep-provisioning-451": Phase="Pending", Reason="", readiness=false. Elapsed: 2.215589475s
Jun 10 08:25:50.306: INFO: Pod "volume-prep-provisioning-451": Phase="Pending", Reason="", readiness=false. Elapsed: 4.322570253s
Jun 10 08:25:52.412: INFO: Pod "volume-prep-provisioning-451": Phase="Pending", Reason="", readiness=false. Elapsed: 6.428804142s
Jun 10 08:25:54.520: INFO: Pod "volume-prep-provisioning-451": Phase="Pending", Reason="", readiness=false. Elapsed: 8.536926355s
Jun 10 08:25:56.628: INFO: Pod "volume-prep-provisioning-451": Phase="Pending", Reason="", readiness=false. Elapsed: 10.644070703s
... skipping 112 lines ...
Jun 10 08:29:54.737: INFO: Pod "volume-prep-provisioning-451": Phase="Pending", Reason="", readiness=false. Elapsed: 4m8.753479769s
Jun 10 08:29:56.844: INFO: Pod "volume-prep-provisioning-451": Phase="Pending", Reason="", readiness=false. Elapsed: 4m10.860864971s
Jun 10 08:29:58.951: INFO: Pod "volume-prep-provisioning-451": Phase="Pending", Reason="", readiness=false. Elapsed: 4m12.968019402s
Jun 10 08:30:01.058: INFO: Pod "volume-prep-provisioning-451": Phase="Pending", Reason="", readiness=false. Elapsed: 4m15.074224189s
Jun 10 08:30:03.164: INFO: Pod "volume-prep-provisioning-451": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4m17.180713245s
STEP: Saw pod success
Jun 10 08:30:03.164: INFO: Pod "volume-prep-provisioning-451" satisfied condition "Succeeded or Failed"
Jun 10 08:30:03.164: INFO: Deleting pod "volume-prep-provisioning-451" in namespace "provisioning-451"
Jun 10 08:30:03.278: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-451" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-4w6m
STEP: Checking for subpath error in container status
Jun 10 08:30:37.706: INFO: Deleting pod "pod-subpath-test-dynamicpv-4w6m" in namespace "provisioning-451"
Jun 10 08:30:37.819: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-4w6m" to be fully deleted
STEP: Deleting pod
Jun 10 08:30:37.925: INFO: Deleting pod "pod-subpath-test-dynamicpv-4w6m" in namespace "provisioning-451"
STEP: Deleting pvc
Jun 10 08:30:38.242: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comjbbfg"
... skipping 42 lines ...
Jun 10 08:30:41.778: INFO: Waiting for pod aws-injector to disappear
Jun 10 08:30:41.885: INFO: Pod aws-injector still exists
Jun 10 08:30:43.886: INFO: Waiting for pod aws-injector to disappear
Jun 10 08:30:43.993: INFO: Pod aws-injector still exists
Jun 10 08:30:45.886: INFO: Waiting for pod aws-injector to disappear
Jun 10 08:30:45.993: INFO: Pod aws-injector no longer exists
Jun 10 08:30:45.993: FAIL: Failed to create injector pod: timed out waiting for the condition

Full Stack Trace
k8s.io/kubernetes/test/e2e/storage/testsuites.(*volumesTestSuite).DefineTests.func3()
	/tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:186 +0x3ff
github.com/kubernetes-sigs/aws-ebs-csi-driver/tests/e2e-kubernetes.TestEBSCSI(0xc000103380)
	/tmp/kops.Y1KozJqJu/tests/e2e-kubernetes/e2e_test.go:82 +0x1a9
... skipping 18 lines ...
STEP: Found 10 events.
Jun 10 08:31:12.175: INFO: At 2021-06-10 08:25:41 +0000 UTC - event for aws4bnth: {persistentvolume-controller } WaitForFirstConsumer: waiting for first consumer to be created before binding
Jun 10 08:31:12.175: INFO: At 2021-06-10 08:25:41 +0000 UTC - event for aws4bnth: {persistentvolume-controller } ExternalProvisioning: waiting for a volume to be created, either by external provisioner "ebs.csi.aws.com" or manually created by system administrator
Jun 10 08:31:12.175: INFO: At 2021-06-10 08:25:41 +0000 UTC - event for aws4bnth: {ebs.csi.aws.com_ebs-csi-controller-7ffff4ddf5-qp4bh_a1519ff1-2283-4360-b0e7-39e8f74b5462 } Provisioning: External provisioner is provisioning volume for claim "volume-1750/aws4bnth"
Jun 10 08:31:12.175: INFO: At 2021-06-10 08:25:44 +0000 UTC - event for aws4bnth: {ebs.csi.aws.com_ebs-csi-controller-7ffff4ddf5-qp4bh_a1519ff1-2283-4360-b0e7-39e8f74b5462 } ProvisioningSucceeded: Successfully provisioned volume pvc-bd1c244b-15cc-4135-b18f-1456520f1ee6
Jun 10 08:31:12.175: INFO: At 2021-06-10 08:25:45 +0000 UTC - event for aws-injector: {default-scheduler } Scheduled: Successfully assigned volume-1750/aws-injector to ip-172-20-58-127.eu-west-2.compute.internal
Jun 10 08:31:12.175: INFO: At 2021-06-10 08:26:00 +0000 UTC - event for aws-injector: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-bd1c244b-15cc-4135-b18f-1456520f1ee6" : rpc error: code = DeadlineExceeded desc = context deadline exceeded
Jun 10 08:31:12.175: INFO: At 2021-06-10 08:26:10 +0000 UTC - event for aws-injector: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-bd1c244b-15cc-4135-b18f-1456520f1ee6" : rpc error: code = Internal desc = Could not attach volume "vol-0b002b969c890c247" to node "i-02b09d2f0c0b0f80b": attachment of disk "vol-0b002b969c890c247" failed, expected device to be attached but was attaching
Jun 10 08:31:12.175: INFO: At 2021-06-10 08:27:48 +0000 UTC - event for aws-injector: {kubelet ip-172-20-58-127.eu-west-2.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[aws-volume-0], unattached volumes=[kube-api-access-x9hrm aws-volume-0]: timed out waiting for the condition
Jun 10 08:31:12.175: INFO: At 2021-06-10 08:30:06 +0000 UTC - event for aws-injector: {kubelet ip-172-20-58-127.eu-west-2.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[aws-volume-0], unattached volumes=[aws-volume-0 kube-api-access-x9hrm]: timed out waiting for the condition
Jun 10 08:31:12.175: INFO: At 2021-06-10 08:30:15 +0000 UTC - event for aws-injector: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-bd1c244b-15cc-4135-b18f-1456520f1ee6" 
Jun 10 08:31:12.286: INFO: POD  NODE  PHASE  GRACE  CONDITIONS
Jun 10 08:31:12.286: INFO: 
Jun 10 08:31:12.393: INFO: 
... skipping 167 lines ...
  /tmp/kops.Y1KozJqJu/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (xfs)][Slow] volumes
    /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should store data [It]
      /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:159

      Jun 10 08:30:45.993: Failed to create injector pod: timed out waiting for the condition

      /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:186
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
... skipping 395 lines ...
  [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should concurrently access the single volume from pods on the same node [LinuxOnly] [It]
    /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/multivolume.go:312

    while cleanup resource
    Unexpected error:
        <errors.aggregate | len:1, cap:1>: [
            [
                {
                    error: {
                        cause: {
                            s: "PersistentVolume pvc-8abe53d9-f8a6-407f-a5d8-90c0c082f4e3 still exists within 5m0s",
                        },
                        msg: "Persistent Volume pvc-8abe53d9-f8a6-407f-a5d8-90c0c082f4e3 not deleted by dynamic provisioner",
                    },
                    stack: [0x1bf1fa5, 0x200c2c8, 0x200e63a, 0x77cd83, 0x77c99c, 0x77bf67, 0x77fe6f, 0x77f512, 0x7857b1, 0x7852c7, 0x784ab7, 0x7870a6, 0x788f38, 0x788c8d, 0x21c72c9, 0x52610f, 0x474721],
... skipping 114 lines ...
Jun 10 08:33:31.007: INFO: At 2021-06-10 08:25:30 +0000 UTC - event for pod-dc9efff4-12bd-43c2-b0e5-8488d584192b: {kubelet ip-172-20-58-127.eu-west-2.compute.internal} Created: Created container write-pod
Jun 10 08:33:31.007: INFO: At 2021-06-10 08:25:30 +0000 UTC - event for pod-dc9efff4-12bd-43c2-b0e5-8488d584192b: {kubelet ip-172-20-58-127.eu-west-2.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" already present on machine
Jun 10 08:33:31.007: INFO: At 2021-06-10 08:25:33 +0000 UTC - event for pod-dc9efff4-12bd-43c2-b0e5-8488d584192b: {kubelet ip-172-20-58-127.eu-west-2.compute.internal} Killing: Stopping container write-pod
Jun 10 08:33:31.007: INFO: At 2021-06-10 08:25:47 +0000 UTC - event for ebs.csi.aws.comx29hc: {volume_expand } ExternalExpanding: Ignoring the PVC: didn't find a plugin capable of expanding the volume; waiting for an external controller to process this PVC.
Jun 10 08:33:31.007: INFO: At 2021-06-10 08:25:47 +0000 UTC - event for ebs.csi.aws.comx29hc: {external-resizer ebs.csi.aws.com } Resizing: External resizer is resizing volume pvc-e5c1301a-bdcb-4991-9053-f3c67e361742
Jun 10 08:33:31.007: INFO: At 2021-06-10 08:25:48 +0000 UTC - event for ebs.csi.aws.comx29hc: {external-resizer ebs.csi.aws.com } Resizing: External resizer is resizing volume pvc-e5c1301a-bdcb-4991-9053-f3c67e361742
Jun 10 08:33:31.007: INFO: At 2021-06-10 08:25:57 +0000 UTC - event for ebs.csi.aws.comx29hc: {external-resizer ebs.csi.aws.com } VolumeResizeFailed: resize volume "pvc-e5c1301a-bdcb-4991-9053-f3c67e361742" by resizer "ebs.csi.aws.com" failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
Jun 10 08:33:31.007: INFO: At 2021-06-10 08:25:58 +0000 UTC - event for ebs.csi.aws.comx29hc: {external-resizer ebs.csi.aws.com } FileSystemResizeRequired: Require file system resize of volume on node
Jun 10 08:33:31.007: INFO: At 2021-06-10 08:25:58 +0000 UTC - event for ebs.csi.aws.comx29hc: {external-resizer ebs.csi.aws.com } VolumeResizeFailed: Mark PVC "volume-expand-5566/ebs.csi.aws.comx29hc" as file system resize required failed: can't patch status of  PVC volume-expand-5566/ebs.csi.aws.comx29hc with Operation cannot be fulfilled on persistentvolumeclaims "ebs.csi.aws.comx29hc": the object has been modified; please apply your changes to the latest version and try again
Jun 10 08:33:31.007: INFO: At 2021-06-10 08:25:58 +0000 UTC - event for ebs.csi.aws.comx29hc: {external-resizer ebs.csi.aws.com } VolumeResizeFailed: resize volume "pvc-e5c1301a-bdcb-4991-9053-f3c67e361742" by resizer "ebs.csi.aws.com" failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
Jun 10 08:33:31.007: INFO: At 2021-06-10 08:25:59 +0000 UTC - event for pod-501d4529-5719-4d21-8339-5434b2d244de: {default-scheduler } Scheduled: Successfully assigned volume-expand-5566/pod-501d4529-5719-4d21-8339-5434b2d244de to ip-172-20-45-65.eu-west-2.compute.internal
Jun 10 08:33:31.007: INFO: At 2021-06-10 08:25:59 +0000 UTC - event for pod-501d4529-5719-4d21-8339-5434b2d244de: {attachdetach-controller } FailedAttachVolume: Multi-Attach error for volume "pvc-e5c1301a-bdcb-4991-9053-f3c67e361742" Volume is already exclusively attached to one node and can't be attached to another
Jun 10 08:33:31.007: INFO: At 2021-06-10 08:27:44 +0000 UTC - event for pod-501d4529-5719-4d21-8339-5434b2d244de: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-e5c1301a-bdcb-4991-9053-f3c67e361742" 
Jun 10 08:33:31.007: INFO: At 2021-06-10 08:28:02 +0000 UTC - event for pod-501d4529-5719-4d21-8339-5434b2d244de: {kubelet ip-172-20-45-65.eu-west-2.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume1], unattached volumes=[volume1 kube-api-access-kqv65]: timed out waiting for the condition
Jun 10 08:33:31.007: INFO: At 2021-06-10 08:28:08 +0000 UTC - event for ebs.csi.aws.comx29hc: {kubelet ip-172-20-45-65.eu-west-2.compute.internal} FileSystemResizeSuccessful: MountVolume.NodeExpandVolume succeeded for volume "pvc-e5c1301a-bdcb-4991-9053-f3c67e361742" 
Jun 10 08:33:31.007: INFO: At 2021-06-10 08:28:08 +0000 UTC - event for pod-501d4529-5719-4d21-8339-5434b2d244de: {kubelet ip-172-20-45-65.eu-west-2.compute.internal} FileSystemResizeSuccessful: MountVolume.NodeExpandVolume succeeded for volume "pvc-e5c1301a-bdcb-4991-9053-f3c67e361742" 
Jun 10 08:33:31.007: INFO: At 2021-06-10 08:28:16 +0000 UTC - event for pod-501d4529-5719-4d21-8339-5434b2d244de: {kubelet ip-172-20-45-65.eu-west-2.compute.internal} Created: Created container write-pod
Jun 10 08:33:31.007: INFO: At 2021-06-10 08:28:16 +0000 UTC - event for pod-501d4529-5719-4d21-8339-5434b2d244de: {kubelet ip-172-20-45-65.eu-west-2.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" already present on machine
... skipping 171 lines ...
  [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    Verify if offline PVC expansion works [It]
    /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volume_expand.go:174

    while cleaning up resource
    Unexpected error:
        <errors.aggregate | len:1, cap:1>: [
            [
                {
                    error: {
                        cause: {
                            s: "PersistentVolume pvc-e5c1301a-bdcb-4991-9053-f3c67e361742 still exists within 5m0s",
                        },
                        msg: "Persistent Volume pvc-e5c1301a-bdcb-4991-9053-f3c67e361742 not deleted by dynamic provisioner",
                    },
                    stack: [0x1bf1fa5, 0x2021990, 0x2023577, 0x77cd83, 0x77c99c, 0x77bf67, 0x77fe6f, 0x77f512, 0x7857b1, 0x7852c7, 0x784ab7, 0x7870a6, 0x788f38, 0x788c8d, 0x21c72c9, 0x52610f, 0x474721],
... skipping 92 lines ...
Jun 10 08:28:46.554: INFO: Waiting for pod aws-client to disappear
Jun 10 08:28:46.659: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 10 08:28:46.660: INFO: Deleting PersistentVolumeClaim "pvc-h44b8"
Jun 10 08:28:46.767: INFO: Deleting PersistentVolume "aws-k7ctg"
Jun 10 08:28:47.429: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: 2137ec49-77d3-4b09-951d-3a34fd194bb9
Jun 10 08:28:53.081: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: 03780101-140f-4078-86aa-ed13e3a0192f
Jun 10 08:28:58.614: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: c177b5a0-ca33-4c8c-b6f3-5ffd0ed262a0
Jun 10 08:29:04.219: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: 10576fb4-3da6-4f33-af58-187767192d0e
Jun 10 08:29:09.789: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: a487c0f3-b0f7-42c3-8d25-a1bfaaa86eef
Jun 10 08:29:15.423: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: 13bb2ccd-ebac-4f17-a4a9-aa237698a4dd
Jun 10 08:29:21.010: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: f5078709-b31c-40a1-bd97-1f8efb20c8b3
Jun 10 08:29:26.559: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: 91de7805-3e80-42bc-8259-efc08fbfc02a
Jun 10 08:29:32.148: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: 688e990a-f084-41e7-acdf-2c7855cc412b
Jun 10 08:29:37.719: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: 3d0cd74d-2e35-431e-990d-9851122afaf5
Jun 10 08:29:43.285: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: 786f211c-30fc-4a5e-93e5-d4ca8487a790
Jun 10 08:29:48.862: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: 3e667ac5-7adf-4b67-8eac-1cb921a1db13
Jun 10 08:29:54.440: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: f02dc98c-0a15-4763-813f-d706f38f772b
Jun 10 08:30:00.000: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: 5c7cb504-db2f-4fb0-85cf-c9b063945ed6
Jun 10 08:30:05.576: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: b36956b6-3e0a-480c-83bd-345a10ca51e0
Jun 10 08:30:11.159: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: 15e9d720-7ef3-40f7-93ed-2e8059fc6969
Jun 10 08:30:16.707: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: 16c4622f-cceb-4d78-9e0d-e691f08f7edc
Jun 10 08:30:22.281: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: 913e8980-b391-4fd9-a25e-5620ed931a94
Jun 10 08:30:27.848: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: 37e95207-0bdf-4137-8933-7c4be8a8c946
Jun 10 08:30:33.402: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: acc51b51-a3fb-4ebb-b769-16c20fbe1631
Jun 10 08:30:38.967: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: ba3ec80a-3d75-4c05-b2fa-99cf26e768cd
Jun 10 08:30:44.538: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: f30e7d43-a23e-459c-bb95-cd05c6c0ffaf
Jun 10 08:30:50.125: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: 0fa147ed-0489-41fd-a197-b79aaac02ed0
Jun 10 08:30:55.724: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: cd9ea99e-f81d-47ce-ab62-225d0233c488
Jun 10 08:31:01.302: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: a3bd2a9c-ae29-4852-a70d-eb3c2b569c60
Jun 10 08:31:06.885: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: b2219935-4fe4-43bc-b1e1-2b425058f5ab
Jun 10 08:31:12.466: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: 5d96a233-dfc1-4d71-a86f-8ad7b2621b9c
Jun 10 08:31:18.049: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: 40517295-830f-44f5-8e43-9531ed92c3cb
Jun 10 08:31:23.638: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: 51b1b46d-90a2-47f4-a976-921686130954
Jun 10 08:31:29.214: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: 93739e03-f521-4c40-85a3-7b85010b74c7
Jun 10 08:31:34.744: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: ebacc662-29fc-46ca-8adb-c2c85f5018bb
Jun 10 08:31:40.324: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: f8a2969a-4407-4771-a839-12732b97b97e
Jun 10 08:31:45.883: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: e239e358-d82d-4c5f-b57b-623369d0c951
Jun 10 08:31:51.471: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: d72d30a0-5ba8-4dfb-af94-bafd6ffe9ef9
Jun 10 08:31:57.026: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: 4ac62864-2fa5-41c9-94a0-9f184d2bea86
Jun 10 08:32:02.872: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: 2449ecb7-c954-4547-8be7-1b4b86fa7744
Jun 10 08:32:08.433: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: 361bc1ee-bf00-4632-a73e-52124c482d54
Jun 10 08:32:13.998: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: 8a7bc27f-0655-45dd-ba12-19e380ed118c
Jun 10 08:32:19.557: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: 691af240-ee58-4136-8cb1-ab3e15bbb512
Jun 10 08:32:25.133: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: a34a209f-ecb5-4253-bfc3-c37ba26a3c55
Jun 10 08:32:30.715: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: b9d0809a-9c73-4565-b32e-cd79a5a60eb0
Jun 10 08:32:36.279: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: 8b4b1a82-cd1f-4f10-a686-5716baed989e
Jun 10 08:32:41.872: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: 14698088-25b2-4512-8adb-582c7bfface9
Jun 10 08:32:47.435: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: cf79cd0f-ba54-4246-a802-ce44b7856827
Jun 10 08:32:53.010: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: 9543b793-48e7-4d95-99fd-09b56aa8e47e
Jun 10 08:32:58.551: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: 79329378-9447-437a-b54a-a436025fc406
Jun 10 08:33:04.144: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: b79a8776-b48f-477d-8cbe-7447ee24ff95
Jun 10 08:33:09.827: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: f3a748b9-b04b-4713-820f-6c52b82ea7c4
Jun 10 08:33:15.418: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: db4c61ac-61ea-4d7f-bdb5-b100b1758e2b
Jun 10 08:33:20.952: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: cd5f1e61-19d0-4cdc-947c-509556619083
Jun 10 08:33:26.513: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: 6a54ce73-e2c2-4279-891c-d93cbddb1cf2
Jun 10 08:33:32.092: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: ed04e838-c37c-4494-96ac-505be1231516
Jun 10 08:33:37.633: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: 82de1784-1a29-47f4-94e4-26824a2e1b92
Jun 10 08:33:43.227: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0d64531294ae98403", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d64531294ae98403 is currently attached to i-0d8ae5695f91bc782
	status code: 400, request id: 7e52a38f-de7c-4e39-ac74-02d6da056bf3
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 10 08:33:48.229: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-7316" for this suite.

... skipping 240 lines ...
Jun 10 08:33:32.668: INFO: Waiting for pod aws-injector to disappear
Jun 10 08:33:32.774: INFO: Pod aws-injector still exists
Jun 10 08:33:34.668: INFO: Waiting for pod aws-injector to disappear
Jun 10 08:33:34.774: INFO: Pod aws-injector still exists
Jun 10 08:33:36.668: INFO: Waiting for pod aws-injector to disappear
Jun 10 08:33:36.774: INFO: Pod aws-injector no longer exists
Jun 10 08:33:36.774: FAIL: Failed to create injector pod: timed out waiting for the condition

Full Stack Trace
k8s.io/kubernetes/test/e2e/storage/testsuites.(*volumesTestSuite).DefineTests.func3()
	/tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:186 +0x3ff
github.com/kubernetes-sigs/aws-ebs-csi-driver/tests/e2e-kubernetes.TestEBSCSI(0xc0004a8900)
	/tmp/kops.Y1KozJqJu/tests/e2e-kubernetes/e2e_test.go:82 +0x1a9
... skipping 71 lines ...
STEP: Found 11 events.
Jun 10 08:38:38.654: INFO: At 2021-06-10 08:28:29 +0000 UTC - event for awshqblm: {persistentvolume-controller } WaitForFirstConsumer: waiting for first consumer to be created before binding
Jun 10 08:38:38.654: INFO: At 2021-06-10 08:28:30 +0000 UTC - event for awshqblm: {persistentvolume-controller } ExternalProvisioning: waiting for a volume to be created, either by external provisioner "ebs.csi.aws.com" or manually created by system administrator
Jun 10 08:38:38.654: INFO: At 2021-06-10 08:28:30 +0000 UTC - event for awshqblm: {ebs.csi.aws.com_ebs-csi-controller-7ffff4ddf5-qp4bh_a1519ff1-2283-4360-b0e7-39e8f74b5462 } Provisioning: External provisioner is provisioning volume for claim "volume-4069/awshqblm"
Jun 10 08:38:38.654: INFO: At 2021-06-10 08:28:33 +0000 UTC - event for awshqblm: {ebs.csi.aws.com_ebs-csi-controller-7ffff4ddf5-qp4bh_a1519ff1-2283-4360-b0e7-39e8f74b5462 } ProvisioningSucceeded: Successfully provisioned volume pvc-c6b62648-5c41-48ad-ab8b-6086150769c1
Jun 10 08:38:38.654: INFO: At 2021-06-10 08:28:34 +0000 UTC - event for aws-injector: {default-scheduler } Scheduled: Successfully assigned volume-4069/aws-injector to ip-172-20-45-65.eu-west-2.compute.internal
Jun 10 08:38:38.654: INFO: At 2021-06-10 08:28:49 +0000 UTC - event for aws-injector: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-c6b62648-5c41-48ad-ab8b-6086150769c1" : rpc error: code = DeadlineExceeded desc = context deadline exceeded
Jun 10 08:38:38.654: INFO: At 2021-06-10 08:28:54 +0000 UTC - event for aws-injector: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-c6b62648-5c41-48ad-ab8b-6086150769c1" : rpc error: code = Internal desc = Could not attach volume "vol-05496ea5398745f54" to node "i-0d8ae5695f91bc782": attachment of disk "vol-05496ea5398745f54" failed, expected device to be attached but was attaching
Jun 10 08:38:38.654: INFO: At 2021-06-10 08:29:57 +0000 UTC - event for aws-injector: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-c6b62648-5c41-48ad-ab8b-6086150769c1" 
Jun 10 08:38:38.654: INFO: At 2021-06-10 08:30:37 +0000 UTC - event for aws-injector: {kubelet ip-172-20-45-65.eu-west-2.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[aws-volume-0], unattached volumes=[aws-volume-0 kube-api-access-6wwbw]: timed out waiting for the condition
Jun 10 08:38:38.654: INFO: At 2021-06-10 08:30:42 +0000 UTC - event for aws-injector: {kubelet ip-172-20-45-65.eu-west-2.compute.internal} FailedMount: MountVolume.MountDevice failed for volume "pvc-c6b62648-5c41-48ad-ab8b-6086150769c1" : rpc error: code = Internal desc = Failed to find device path /dev/xvdbi. nvme path "/dev/disk/by-id/nvme-Amazon_Elastic_Block_Store_vol05496ea5398745f54" not found
Jun 10 08:38:38.654: INFO: At 2021-06-10 08:35:08 +0000 UTC - event for aws-injector: {kubelet ip-172-20-45-65.eu-west-2.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[aws-volume-0 kube-api-access-6wwbw], unattached volumes=[aws-volume-0 kube-api-access-6wwbw]: timed out waiting for the condition
Jun 10 08:38:38.760: INFO: POD  NODE  PHASE  GRACE  CONDITIONS
Jun 10 08:38:38.760: INFO: 
Jun 10 08:38:38.867: INFO: 
Logging node info for node ip-172-20-36-68.eu-west-2.compute.internal
Jun 10 08:38:38.973: INFO: Node Info: &Node{ObjectMeta:{ip-172-20-36-68.eu-west-2.compute.internal    6d4429c4-26c9-461a-8d88-3e206f1c413a 16874 0 2021-06-10 08:16:25 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:t3.medium beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:eu-west-2 failure-domain.beta.kubernetes.io/zone:eu-west-2a kops.k8s.io/instancegroup:nodes-eu-west-2a kubernetes.io/arch:amd64 kubernetes.io/hostname:ip-172-20-36-68.eu-west-2.compute.internal kubernetes.io/os:linux kubernetes.io/role:node node-role.kubernetes.io/node: node.kubernetes.io/instance-type:t3.medium topology.ebs.csi.aws.com/zone:eu-west-2a topology.kubernetes.io/region:eu-west-2 topology.kubernetes.io/zone:eu-west-2a] map[csi.volume.kubernetes.io/nodeid:{"ebs.csi.aws.com":"i-0ff665d16f07b5536"} node.alpha.kubernetes.io/ttl:0 projectcalico.org/IPv4Address:172.20.36.68/19 projectcalico.org/IPv4IPIPTunnelAddr:100.110.11.128 volumes.kubernetes.io/controller-managed-attach-detach:true] [] []  [{kops-controller Update v1 2021-06-10 08:16:25 +0000 UTC FieldsV1 {"f:metadata":{"f:labels":{"f:kops.k8s.io/instancegroup":{},"f:kubernetes.io/role":{},"f:node-role.kubernetes.io/node":{}}}}} {calico-node Update v1 2021-06-10 08:16:49 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4IPIPTunnelAddr":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}}} {kube-controller-manager Update v1 2021-06-10 08:27:53 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"100.96.3.0/24\"":{}}}}} {kubelet Update v1 2021-06-10 08:30:46 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:csi.volume.kubernetes.io/nodeid":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.ebs.csi.aws.com/zone":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}},"f:status":{"f:allocatable":{"f:ephemeral-storage":{}},"f:capacity":{"f:ephemeral-storage":{}},"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}}}]},Spec:NodeSpec{PodCIDR:100.96.3.0/24,DoNotUseExternalID:,ProviderID:aws:///eu-west-2a/i-0ff665d16f07b5536,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[100.96.3.0/24],},Status:NodeStatus{Capacity:ResourceList{cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{49895047168 0} {<nil>}  BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{4064759808 0} {<nil>} 3969492Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{44905542377 0} {<nil>} 44905542377 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{3959902208 0} {<nil>} 3867092Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2021-06-10 08:16:49 +0000 UTC,LastTransitionTime:2021-06-10 08:16:49 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2021-06-10 08:35:46 +0000 UTC,LastTransitionTime:2021-06-10 08:16:25 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2021-06-10 08:35:46 +0000 UTC,LastTransitionTime:2021-06-10 08:16:25 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2021-06-10 08:35:46 +0000 UTC,LastTransitionTime:2021-06-10 08:16:25 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2021-06-10 08:35:46 +0000 UTC,LastTransitionTime:2021-06-10 08:16:45 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:172.20.36.68,},NodeAddress{Type:ExternalIP,Address:18.135.15.19,},NodeAddress{Type:Hostname,Address:ip-172-20-36-68.eu-west-2.compute.internal,},NodeAddress{Type:InternalDNS,Address:ip-172-20-36-68.eu-west-2.compute.internal,},NodeAddress{Type:ExternalDNS,Address:ec2-18-135-15-19.eu-west-2.compute.amazonaws.com,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:ec26c357102e3b4d605ff5b8782aaf2c,SystemUUID:ec26c357-102e-3b4d-605f-f5b8782aaf2c,BootID:210f7d47-97e9-4cb3-adef-04b969239602,KernelVersion:5.4.0-1045-aws,OSImage:Ubuntu 20.04.2 LTS,ContainerRuntimeVersion:containerd://1.4.6,KubeletVersion:v1.21.0,KubeProxyVersion:v1.21.0,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[k8s.gcr.io/provider-aws/aws-ebs-csi-driver@sha256:a0294bf95fd94eabdc9b313b6c16232019a8707c711c031a2f99ab1f919560bd k8s.gcr.io/provider-aws/aws-ebs-csi-driver:v1.0.0],SizeBytes:67079979,},ContainerImage{Names:[docker.io/calico/node@sha256:bc4a631d553b38fdc169ea4cb8027fa894a656e80d68d513359a4b9d46836b55 docker.io/calico/node:v3.19.1],SizeBytes:58671776,},ContainerImage{Names:[k8s.gcr.io/kube-proxy@sha256:326199e7a5232bf7531a3058e9811c925b07085f33fa882558cc4e89379b9109 k8s.gcr.io/kube-proxy:v1.21.0],SizeBytes:50134170,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/agnhost@sha256:8bd76a6a7778e203b61e18e5ee85b1faf52e6a30eb07e445a165ab90fe9633e3 k8s.gcr.io/e2e-test-images/agnhost:2.31],SizeBytes:49692421,},ContainerImage{Names:[docker.io/calico/cni@sha256:f301171be0add870152483fcce71b28cafb8e910f61ff003032e9b1053b062c4 docker.io/calico/cni:v3.19.1],SizeBytes:48338203,},ContainerImage{Names:[k8s.gcr.io/build-image/debian-iptables@sha256:abe8cef9e116f2d5ec1175c386e33841ff3386779138b425af876384b0fd7ccb k8s.gcr.io/build-image/debian-iptables:buster-v1.5.0],SizeBytes:38088315,},ContainerImage{Names:[k8s.gcr.io/sig-storage/snapshot-validation-webhook@sha256:931a753e6428914f5393e3bba5f250f952c57dc2e9ddd16c37593a8f02b6715e k8s.gcr.io/sig-storage/snapshot-validation-webhook:v4.1.1],SizeBytes:18566421,},ContainerImage{Names:[k8s.gcr.io/cpa/cluster-proportional-autoscaler@sha256:67640771ad9fc56f109d5b01e020f0c858e7c890bb0eb15ba0ebd325df3285e7 k8s.gcr.io/cpa/cluster-proportional-autoscaler:1.8.3],SizeBytes:15191740,},ContainerImage{Names:[docker.io/coredns/coredns@sha256:642ff9910da6ea9a8624b0234eef52af9ca75ecbec474c5507cb096bdfbae4e5 docker.io/coredns/coredns:1.8.3],SizeBytes:12893350,},ContainerImage{Names:[docker.io/calico/pod2daemon-flexvol@sha256:bcac7dc4f1301b062d91a177a52d13716907636975c44131fb8350e7f851c944 docker.io/calico/pod2daemon-flexvol:v3.19.1],SizeBytes:9328155,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-node-driver-registrar@sha256:a61d309da54641db41fb8f35718f744e9f730d4d0384f8c4b186ddc9f06cbd5f k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.1.0],SizeBytes:9068367,},ContainerImage{Names:[k8s.gcr.io/sig-storage/livenessprobe@sha256:48da0e4ed7238ad461ea05f68c25921783c37b315f21a5c5a2780157a6460994 k8s.gcr.io/sig-storage/livenessprobe:v2.2.0],SizeBytes:8279778,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/nginx@sha256:503b7abb89e57383eba61cc8a9cb0b495ea575c516108f7d972a6ff6e1ab3c9b k8s.gcr.io/e2e-test-images/nginx:1.14-1],SizeBytes:6979365,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/busybox@sha256:39e1e963e5310e9c313bad51523be012ede7b35bb9316517d19089a010356592 k8s.gcr.io/e2e-test-images/busybox:1.29-1],SizeBytes:732746,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:927d98197ec1141a368550822d18fa1c60bdae27b78b0c004f705f548c07814f k8s.gcr.io/pause:3.2],SizeBytes:299513,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},}
... skipping 159 lines ...
  /tmp/kops.Y1KozJqJu/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] volumes
    /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should store data [It]
      /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:159

      Jun 10 08:33:36.774: Failed to create injector pod: timed out waiting for the condition

      /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:186
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand
  /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand
... skipping 104 lines ...
Jun 10 08:43:29.049: INFO: At 2021-06-10 08:27:57 +0000 UTC - event for pod-3f210468-b750-47bb-8169-a6ba26399df7: {kubelet ip-172-20-36-68.eu-west-2.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" already present on machine
Jun 10 08:43:29.049: INFO: At 2021-06-10 08:27:59 +0000 UTC - event for pod-3f210468-b750-47bb-8169-a6ba26399df7: {kubelet ip-172-20-36-68.eu-west-2.compute.internal} Killing: Stopping container write-pod
Jun 10 08:43:29.049: INFO: At 2021-06-10 08:28:07 +0000 UTC - event for aws9ltw7: {external-resizer ebs.csi.aws.com } Resizing: External resizer is resizing volume pvc-4f2a9ee9-be19-47c5-8dea-0f6171a6939d
Jun 10 08:43:29.049: INFO: At 2021-06-10 08:28:07 +0000 UTC - event for aws9ltw7: {volume_expand } ExternalExpanding: CSI migration enabled for kubernetes.io/aws-ebs; waiting for external resizer to expand the pvc
Jun 10 08:43:29.049: INFO: At 2021-06-10 08:28:08 +0000 UTC - event for aws9ltw7: {external-resizer ebs.csi.aws.com } Resizing: External resizer is resizing volume pvc-4f2a9ee9-be19-47c5-8dea-0f6171a6939d
Jun 10 08:43:29.049: INFO: At 2021-06-10 08:28:14 +0000 UTC - event for aws9ltw7: {external-resizer ebs.csi.aws.com } FileSystemResizeRequired: Require file system resize of volume on node
Jun 10 08:43:29.049: INFO: At 2021-06-10 08:28:14 +0000 UTC - event for aws9ltw7: {external-resizer ebs.csi.aws.com } VolumeResizeFailed: Mark PVC "volume-expand-5392/aws9ltw7" as file system resize required failed: can't patch status of  PVC volume-expand-5392/aws9ltw7 with Operation cannot be fulfilled on persistentvolumeclaims "aws9ltw7": the object has been modified; please apply your changes to the latest version and try again
Jun 10 08:43:29.049: INFO: At 2021-06-10 08:28:16 +0000 UTC - event for pod-95ba7a23-c954-4848-a10f-0e0d072d782f: {default-scheduler } Scheduled: Successfully assigned volume-expand-5392/pod-95ba7a23-c954-4848-a10f-0e0d072d782f to ip-172-20-45-65.eu-west-2.compute.internal
Jun 10 08:43:29.049: INFO: At 2021-06-10 08:28:31 +0000 UTC - event for pod-95ba7a23-c954-4848-a10f-0e0d072d782f: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-4f2a9ee9-be19-47c5-8dea-0f6171a6939d" : rpc error: code = Internal desc = Could not attach volume "vol-0542144b35d1e1887" to node "i-0d8ae5695f91bc782": attachment of disk "vol-0542144b35d1e1887" failed, expected device to be attached but was attaching
Jun 10 08:43:29.049: INFO: At 2021-06-10 08:29:06 +0000 UTC - event for pod-95ba7a23-c954-4848-a10f-0e0d072d782f: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-4f2a9ee9-be19-47c5-8dea-0f6171a6939d" 
Jun 10 08:43:29.049: INFO: At 2021-06-10 08:29:20 +0000 UTC - event for pod-95ba7a23-c954-4848-a10f-0e0d072d782f: {kubelet ip-172-20-45-65.eu-west-2.compute.internal} FailedMount: MountVolume.MountDevice failed for volume "pvc-4f2a9ee9-be19-47c5-8dea-0f6171a6939d" : rpc error: code = Internal desc = Failed to find device path /dev/xvdbh. nvme path "/dev/disk/by-id/nvme-Amazon_Elastic_Block_Store_vol0542144b35d1e1887" not found
Jun 10 08:43:29.049: INFO: At 2021-06-10 08:30:19 +0000 UTC - event for pod-95ba7a23-c954-4848-a10f-0e0d072d782f: {kubelet ip-172-20-45-65.eu-west-2.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume1], unattached volumes=[volume1 kube-api-access-m7mk4]: timed out waiting for the condition
Jun 10 08:43:29.049: INFO: At 2021-06-10 08:32:34 +0000 UTC - event for pod-95ba7a23-c954-4848-a10f-0e0d072d782f: {kubelet ip-172-20-45-65.eu-west-2.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume1], unattached volumes=[kube-api-access-m7mk4 volume1]: timed out waiting for the condition
Jun 10 08:43:29.049: INFO: At 2021-06-10 08:39:28 +0000 UTC - event for pod-95ba7a23-c954-4848-a10f-0e0d072d782f: {kubelet ip-172-20-45-65.eu-west-2.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume1 kube-api-access-m7mk4], unattached volumes=[volume1 kube-api-access-m7mk4]: timed out waiting for the condition
Jun 10 08:43:29.156: INFO: POD  NODE  PHASE  GRACE  CONDITIONS
Jun 10 08:43:29.156: INFO: 
Jun 10 08:43:29.265: INFO: 
... skipping 162 lines ...
    [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand
    /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      Verify if offline PVC expansion works [It]
      /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volume_expand.go:174

      while recreating pod for resizing
      Unexpected error:
          <*errors.errorString | 0xc000eb4c70>: {
              s: "pod \"pod-95ba7a23-c954-4848-a10f-0e0d072d782f\" is not Running: timed out waiting for the condition",
          }
          pod "pod-95ba7a23-c954-4848-a10f-0e0d072d782f" is not Running: timed out waiting for the condition
      occurred

... skipping 158 lines ...
Jun 10 08:43:39.796: INFO: At 2021-06-10 08:28:25 +0000 UTC - event for awsf784w: {ebs.csi.aws.com_ebs-csi-controller-7ffff4ddf5-qp4bh_a1519ff1-2283-4360-b0e7-39e8f74b5462 } Provisioning: External provisioner is provisioning volume for claim "multivolume-4507/awsf784w"
Jun 10 08:43:39.796: INFO: At 2021-06-10 08:28:25 +0000 UTC - event for awsf784w: {persistentvolume-controller } WaitForFirstConsumer: waiting for first consumer to be created before binding
Jun 10 08:43:39.796: INFO: At 2021-06-10 08:28:25 +0000 UTC - event for awsf784w: {persistentvolume-controller } ExternalProvisioning: waiting for a volume to be created, either by external provisioner "ebs.csi.aws.com" or manually created by system administrator
Jun 10 08:43:39.796: INFO: At 2021-06-10 08:28:28 +0000 UTC - event for aws78rd6: {ebs.csi.aws.com_ebs-csi-controller-7ffff4ddf5-qp4bh_a1519ff1-2283-4360-b0e7-39e8f74b5462 } ProvisioningSucceeded: Successfully provisioned volume pvc-f82e6d10-c231-4e20-a5bd-b9764d647ffa
Jun 10 08:43:39.796: INFO: At 2021-06-10 08:28:28 +0000 UTC - event for awsf784w: {ebs.csi.aws.com_ebs-csi-controller-7ffff4ddf5-qp4bh_a1519ff1-2283-4360-b0e7-39e8f74b5462 } ProvisioningSucceeded: Successfully provisioned volume pvc-4f4ab74e-bd88-4d90-abfd-b23a759f22d2
Jun 10 08:43:39.796: INFO: At 2021-06-10 08:28:29 +0000 UTC - event for pod-a6123290-fb5d-4555-b35a-f401dba20fa7: {default-scheduler } Scheduled: Successfully assigned multivolume-4507/pod-a6123290-fb5d-4555-b35a-f401dba20fa7 to ip-172-20-45-65.eu-west-2.compute.internal
Jun 10 08:43:39.796: INFO: At 2021-06-10 08:28:45 +0000 UTC - event for pod-a6123290-fb5d-4555-b35a-f401dba20fa7: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-4f4ab74e-bd88-4d90-abfd-b23a759f22d2" : rpc error: code = DeadlineExceeded desc = context deadline exceeded
Jun 10 08:43:39.796: INFO: At 2021-06-10 08:28:45 +0000 UTC - event for pod-a6123290-fb5d-4555-b35a-f401dba20fa7: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-f82e6d10-c231-4e20-a5bd-b9764d647ffa" : rpc error: code = DeadlineExceeded desc = context deadline exceeded
Jun 10 08:43:39.796: INFO: At 2021-06-10 08:28:46 +0000 UTC - event for pod-a6123290-fb5d-4555-b35a-f401dba20fa7: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-4f4ab74e-bd88-4d90-abfd-b23a759f22d2" : rpc error: code = Internal desc = Could not attach volume "vol-065159f908754b212" to node "i-0d8ae5695f91bc782": attachment of disk "vol-065159f908754b212" failed, expected device to be attached but was attaching
Jun 10 08:43:39.796: INFO: At 2021-06-10 08:28:46 +0000 UTC - event for pod-a6123290-fb5d-4555-b35a-f401dba20fa7: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-f82e6d10-c231-4e20-a5bd-b9764d647ffa" : rpc error: code = Internal desc = Could not attach volume "vol-0ce7a2e2155657a0b" to node "i-0d8ae5695f91bc782": attachment of disk "vol-0ce7a2e2155657a0b" failed, expected device to be attached but was attaching
Jun 10 08:43:39.796: INFO: At 2021-06-10 08:29:53 +0000 UTC - event for pod-a6123290-fb5d-4555-b35a-f401dba20fa7: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-f82e6d10-c231-4e20-a5bd-b9764d647ffa" 
Jun 10 08:43:39.796: INFO: At 2021-06-10 08:30:32 +0000 UTC - event for pod-a6123290-fb5d-4555-b35a-f401dba20fa7: {kubelet ip-172-20-45-65.eu-west-2.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume1 volume2], unattached volumes=[kube-api-access-56b55 volume1 volume2]: timed out waiting for the condition
Jun 10 08:43:39.796: INFO: At 2021-06-10 08:30:37 +0000 UTC - event for pod-a6123290-fb5d-4555-b35a-f401dba20fa7: {kubelet ip-172-20-45-65.eu-west-2.compute.internal} FailedMapVolume: MapVolume.MapPodDevice failed for volume "pvc-f82e6d10-c231-4e20-a5bd-b9764d647ffa" : rpc error: code = Internal desc = Failed to find device path /dev/xvdbb. nvme path "/dev/disk/by-id/nvme-Amazon_Elastic_Block_Store_vol0ce7a2e2155657a0b" not found
Jun 10 08:43:39.796: INFO: At 2021-06-10 08:30:57 +0000 UTC - event for pod-a6123290-fb5d-4555-b35a-f401dba20fa7: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-4f4ab74e-bd88-4d90-abfd-b23a759f22d2" 
Jun 10 08:43:39.796: INFO: At 2021-06-10 08:32:40 +0000 UTC - event for pod-a6123290-fb5d-4555-b35a-f401dba20fa7: {kubelet ip-172-20-45-65.eu-west-2.compute.internal} FailedMapVolume: MapVolume.MapPodDevice failed for volume "pvc-4f4ab74e-bd88-4d90-abfd-b23a759f22d2" : rpc error: code = Internal desc = Failed to find device path /dev/xvdbd. nvme path "/dev/disk/by-id/nvme-Amazon_Elastic_Block_Store_vol065159f908754b212" not found
Jun 10 08:43:39.796: INFO: At 2021-06-10 08:35:07 +0000 UTC - event for pod-a6123290-fb5d-4555-b35a-f401dba20fa7: {kubelet ip-172-20-45-65.eu-west-2.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[kube-api-access-56b55 volume1 volume2], unattached volumes=[kube-api-access-56b55 volume1 volume2]: timed out waiting for the condition
Jun 10 08:43:39.901: INFO: POD  NODE  PHASE  GRACE  CONDITIONS
Jun 10 08:43:39.901: INFO: 
Jun 10 08:43:40.007: INFO: 
Logging node info for node ip-172-20-36-68.eu-west-2.compute.internal
Jun 10 08:43:40.113: INFO: Node Info: &Node{ObjectMeta:{ip-172-20-36-68.eu-west-2.compute.internal    6d4429c4-26c9-461a-8d88-3e206f1c413a 18158 0 2021-06-10 08:16:25 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:t3.medium beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:eu-west-2 failure-domain.beta.kubernetes.io/zone:eu-west-2a kops.k8s.io/instancegroup:nodes-eu-west-2a kubernetes.io/arch:amd64 kubernetes.io/hostname:ip-172-20-36-68.eu-west-2.compute.internal kubernetes.io/os:linux kubernetes.io/role:node node-role.kubernetes.io/node: node.kubernetes.io/instance-type:t3.medium topology.ebs.csi.aws.com/zone:eu-west-2a topology.kubernetes.io/region:eu-west-2 topology.kubernetes.io/zone:eu-west-2a] map[csi.volume.kubernetes.io/nodeid:{"ebs.csi.aws.com":"i-0ff665d16f07b5536"} node.alpha.kubernetes.io/ttl:0 projectcalico.org/IPv4Address:172.20.36.68/19 projectcalico.org/IPv4IPIPTunnelAddr:100.110.11.128 volumes.kubernetes.io/controller-managed-attach-detach:true] [] []  [{kops-controller Update v1 2021-06-10 08:16:25 +0000 UTC FieldsV1 {"f:metadata":{"f:labels":{"f:kops.k8s.io/instancegroup":{},"f:kubernetes.io/role":{},"f:node-role.kubernetes.io/node":{}}}}} {calico-node Update v1 2021-06-10 08:16:49 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4IPIPTunnelAddr":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}}} {kube-controller-manager Update v1 2021-06-10 08:27:53 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"100.96.3.0/24\"":{}}}}} {kubelet Update v1 2021-06-10 08:30:46 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:csi.volume.kubernetes.io/nodeid":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.ebs.csi.aws.com/zone":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}},"f:status":{"f:allocatable":{"f:ephemeral-storage":{}},"f:capacity":{"f:ephemeral-storage":{}},"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}}}]},Spec:NodeSpec{PodCIDR:100.96.3.0/24,DoNotUseExternalID:,ProviderID:aws:///eu-west-2a/i-0ff665d16f07b5536,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[100.96.3.0/24],},Status:NodeStatus{Capacity:ResourceList{cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{49895047168 0} {<nil>}  BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{4064759808 0} {<nil>} 3969492Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{44905542377 0} {<nil>} 44905542377 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{3959902208 0} {<nil>} 3867092Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2021-06-10 08:16:49 +0000 UTC,LastTransitionTime:2021-06-10 08:16:49 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2021-06-10 08:40:46 +0000 UTC,LastTransitionTime:2021-06-10 08:16:25 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2021-06-10 08:40:46 +0000 UTC,LastTransitionTime:2021-06-10 08:16:25 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2021-06-10 08:40:46 +0000 UTC,LastTransitionTime:2021-06-10 08:16:25 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2021-06-10 08:40:46 +0000 UTC,LastTransitionTime:2021-06-10 08:16:45 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:172.20.36.68,},NodeAddress{Type:ExternalIP,Address:18.135.15.19,},NodeAddress{Type:Hostname,Address:ip-172-20-36-68.eu-west-2.compute.internal,},NodeAddress{Type:InternalDNS,Address:ip-172-20-36-68.eu-west-2.compute.internal,},NodeAddress{Type:ExternalDNS,Address:ec2-18-135-15-19.eu-west-2.compute.amazonaws.com,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:ec26c357102e3b4d605ff5b8782aaf2c,SystemUUID:ec26c357-102e-3b4d-605f-f5b8782aaf2c,BootID:210f7d47-97e9-4cb3-adef-04b969239602,KernelVersion:5.4.0-1045-aws,OSImage:Ubuntu 20.04.2 LTS,ContainerRuntimeVersion:containerd://1.4.6,KubeletVersion:v1.21.0,KubeProxyVersion:v1.21.0,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[k8s.gcr.io/provider-aws/aws-ebs-csi-driver@sha256:a0294bf95fd94eabdc9b313b6c16232019a8707c711c031a2f99ab1f919560bd k8s.gcr.io/provider-aws/aws-ebs-csi-driver:v1.0.0],SizeBytes:67079979,},ContainerImage{Names:[docker.io/calico/node@sha256:bc4a631d553b38fdc169ea4cb8027fa894a656e80d68d513359a4b9d46836b55 docker.io/calico/node:v3.19.1],SizeBytes:58671776,},ContainerImage{Names:[k8s.gcr.io/kube-proxy@sha256:326199e7a5232bf7531a3058e9811c925b07085f33fa882558cc4e89379b9109 k8s.gcr.io/kube-proxy:v1.21.0],SizeBytes:50134170,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/agnhost@sha256:8bd76a6a7778e203b61e18e5ee85b1faf52e6a30eb07e445a165ab90fe9633e3 k8s.gcr.io/e2e-test-images/agnhost:2.31],SizeBytes:49692421,},ContainerImage{Names:[docker.io/calico/cni@sha256:f301171be0add870152483fcce71b28cafb8e910f61ff003032e9b1053b062c4 docker.io/calico/cni:v3.19.1],SizeBytes:48338203,},ContainerImage{Names:[k8s.gcr.io/build-image/debian-iptables@sha256:abe8cef9e116f2d5ec1175c386e33841ff3386779138b425af876384b0fd7ccb k8s.gcr.io/build-image/debian-iptables:buster-v1.5.0],SizeBytes:38088315,},ContainerImage{Names:[k8s.gcr.io/sig-storage/snapshot-validation-webhook@sha256:931a753e6428914f5393e3bba5f250f952c57dc2e9ddd16c37593a8f02b6715e k8s.gcr.io/sig-storage/snapshot-validation-webhook:v4.1.1],SizeBytes:18566421,},ContainerImage{Names:[k8s.gcr.io/cpa/cluster-proportional-autoscaler@sha256:67640771ad9fc56f109d5b01e020f0c858e7c890bb0eb15ba0ebd325df3285e7 k8s.gcr.io/cpa/cluster-proportional-autoscaler:1.8.3],SizeBytes:15191740,},ContainerImage{Names:[docker.io/coredns/coredns@sha256:642ff9910da6ea9a8624b0234eef52af9ca75ecbec474c5507cb096bdfbae4e5 docker.io/coredns/coredns:1.8.3],SizeBytes:12893350,},ContainerImage{Names:[docker.io/calico/pod2daemon-flexvol@sha256:bcac7dc4f1301b062d91a177a52d13716907636975c44131fb8350e7f851c944 docker.io/calico/pod2daemon-flexvol:v3.19.1],SizeBytes:9328155,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-node-driver-registrar@sha256:a61d309da54641db41fb8f35718f744e9f730d4d0384f8c4b186ddc9f06cbd5f k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.1.0],SizeBytes:9068367,},ContainerImage{Names:[k8s.gcr.io/sig-storage/livenessprobe@sha256:48da0e4ed7238ad461ea05f68c25921783c37b315f21a5c5a2780157a6460994 k8s.gcr.io/sig-storage/livenessprobe:v2.2.0],SizeBytes:8279778,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/nginx@sha256:503b7abb89e57383eba61cc8a9cb0b495ea575c516108f7d972a6ff6e1ab3c9b k8s.gcr.io/e2e-test-images/nginx:1.14-1],SizeBytes:6979365,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/busybox@sha256:39e1e963e5310e9c313bad51523be012ede7b35bb9316517d19089a010356592 k8s.gcr.io/e2e-test-images/busybox:1.29-1],SizeBytes:732746,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:927d98197ec1141a368550822d18fa1c60bdae27b78b0c004f705f548c07814f k8s.gcr.io/pause:3.2],SizeBytes:299513,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},}
... skipping 159 lines ...
  /tmp/kops.Y1KozJqJu/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
    /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should access to two volumes with the same volume mode and retain data across pod recreation on different node [LinuxOnly] [It]
      /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/multivolume.go:164

      Unexpected error:
          <*errors.errorString | 0xc0003fa5a0>: {
              s: "pod \"pod-a6123290-fb5d-4555-b35a-f401dba20fa7\" is not Running: timed out waiting for the condition",
          }
          pod "pod-a6123290-fb5d-4555-b35a-f401dba20fa7" is not Running: timed out waiting for the condition
      occurred

      /tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/multivolume.go:419
------------------------------


Summarizing 6 Failures:

[Fail] [ebs-csi-migration] EBS CSI Migration [Driver: aws] [Testpattern: Dynamic PV (xfs)][Slow] volumes [It] should store data 
/tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:186

[Fail] External Storage [Driver: ebs.csi.aws.com] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] [It] should concurrently access the single volume from pods on the same node [LinuxOnly] 
/tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/multivolume.go:125

[Fail] External Storage [Driver: ebs.csi.aws.com] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand [It] Verify if offline PVC expansion works 
/tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volume_expand.go:152

[Fail] [ebs-csi-migration] EBS CSI Migration [Driver: aws] [Testpattern: Dynamic PV (default fs)] volumes [It] should store data 
/tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:186

[Fail] [ebs-csi-migration] EBS CSI Migration [Driver: aws] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand [It] Verify if offline PVC expansion works 
/tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volume_expand.go:236

[Fail] [ebs-csi-migration] EBS CSI Migration [Driver: aws] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] [It] should access to two volumes with the same volume mode and retain data across pod recreation on different node [LinuxOnly] 
/tmp/kops.Y1KozJqJu/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/multivolume.go:419

Ran 141 of 485 Specs in 1397.050 seconds
FAIL! -- 135 Passed | 6 Failed | 0 Pending | 344 Skipped


Ginkgo ran 1 suite in 24m30.994837618s
Test Suite Failed
+ kops-finish
+ kubetest2 kops -v=2 --cloud-provider=aws --cluster-name=e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --admin-access= --kops-binary-path=/home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops --down
I0610 08:43:44.280356   26638 app.go:59] RunDir for this run: "/logs/artifacts/800d8ac3-c9c2-11eb-a09e-ca7f85cb5ec2"
I0610 08:43:44.280508   26638 app.go:90] ID for this run: "800d8ac3-c9c2-11eb-a09e-ca7f85cb5ec2"
I0610 08:43:44.280537   26638 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
I0610 08:43:44.296656   26644 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
... skipping 2615 lines ...