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

No Test Failures!


Error lines from build-log.txt

... skipping 488 lines ...
I0611 00:09:43.355913   11677 up.go:43] Cleaning up any leaked resources from previous cluster
I0611 00:09:43.355932   11677 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
I0611 00:09:43.369375   11683 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0611 00:09:43.369579   11683 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io" not found
W0611 00:09:43.950416   11677 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0611 00:09:43.950478   11677 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
I0611 00:09:43.964368   11694 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0611 00:09:43.964455   11694 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io" not found
I0611 00:09:44.567385   11677 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/06/11 00:09:44 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
I0611 00:09:44.577618   11677 http.go:37] curl https://ip.jsb.workers.dev
I0611 00:09:44.809037   11677 up.go:144] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops create cluster --name e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --cloud aws --kubernetes-version 1.21.0 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --networking calico --override=cluster.spec.cloudConfig.awsEBSCSIDriver.enabled=true --override=cluster.spec.snapshotController.enabled=true --override=cluster.spec.certManager.enabled=true --admin-access 34.123.6.164/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones eu-west-3a --master-size c5.large
I0611 00:09:44.824628   11709 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0611 00:09:44.825286   11709 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I0611 00:09:44.869726   11709 create_cluster.go:728] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0611 00:09:45.487743   11709 new_cluster.go:1039]  Cloud Provider ID = aws
... skipping 40 lines ...

I0611 00:10:14.082112   11677 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
I0611 00:10:14.098438   11729 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0611 00:10:14.098649   11729 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io

W0611 00:10:15.483596   11729 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
W0611 00:10:25.528819   11729 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-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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
W0611 00:13:06.295080   11729 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0611 00:13:16.338989   11729 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0611 00:13:26.400726   11729 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0611 00:13:36.446324   11729 validate_cluster.go:221] (will retry): cluster not yet healthy
W0611 00:13:46.497154   11729 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-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0611 00:13:56.541530   11729 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0611 00:14:06.586234   11729 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0611 00:14:16.647321   11729 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0611 00:14:26.706649   11729 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0611 00:14:36.750230   11729 validate_cluster.go:221] (will retry): cluster not yet healthy
W0611 00:14:46.812055   11729 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-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0611 00:14:56.869873   11729 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0611 00:15:06.928304   11729 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0611 00:15:16.986059   11729 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0611 00:15:27.041993   11729 validate_cluster.go:221] (will retry): cluster not yet healthy
W0611 00:16:07.088950   11729 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 203.0.113.123:443: i/o timeout
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

NODE STATUS
... skipping 12 lines ...
Pod	kube-system/calico-node-qchtd				system-node-critical pod "calico-node-qchtd" is not ready (calico-node)
Pod	kube-system/cert-manager-cainjector-74d69756d5-9f42m	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-9f42m" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-h6zn2	system-cluster-critical pod "cert-manager-webhook-7bbf67968-h6zn2" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-fv7r5		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fv7r5" is pending
Pod	kube-system/coredns-f45c4bf76-6h4hq			system-cluster-critical pod "coredns-f45c4bf76-6h4hq" is pending

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

... skipping 6 lines ...
ip-172-20-55-69.eu-west-3.compute.internal	node	True

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

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

... skipping 119 lines ...

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
W0611 00:18:18.612540   11729 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 404 lines ...
Jun 11 00:22:03.112: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

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

      Not enough topologies in cluster -- skipping

      /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 6 lines ...

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

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

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

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 250 lines ...
Jun 11 00:22:06.217: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

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

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

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

    /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 162 lines ...
Jun 11 00:22:06.779: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-2559bm5sr
STEP: creating a claim
Jun 11 00:22:06.894: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Jun 11 00:22:07.124: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 11 00:22:07.358: INFO: Error updating pvc awsgctv6: PersistentVolumeClaim "awsgctv6" is invalid: spec: Forbidden: spec is 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-2559bm5sr",
  	... // 2 identical fields
  }

Jun 11 00:22:09.600: INFO: Error updating pvc awsgctv6: PersistentVolumeClaim "awsgctv6" is invalid: spec: Forbidden: spec is 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-2559bm5sr",
  	... // 2 identical fields
  }

Jun 11 00:22:11.587: INFO: Error updating pvc awsgctv6: PersistentVolumeClaim "awsgctv6" is invalid: spec: Forbidden: spec is 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-2559bm5sr",
  	... // 2 identical fields
  }

Jun 11 00:22:13.597: INFO: Error updating pvc awsgctv6: PersistentVolumeClaim "awsgctv6" is invalid: spec: Forbidden: spec is 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-2559bm5sr",
  	... // 2 identical fields
  }

Jun 11 00:22:15.591: INFO: Error updating pvc awsgctv6: PersistentVolumeClaim "awsgctv6" is invalid: spec: Forbidden: spec is 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-2559bm5sr",
  	... // 2 identical fields
  }

Jun 11 00:22:17.587: INFO: Error updating pvc awsgctv6: PersistentVolumeClaim "awsgctv6" is invalid: spec: Forbidden: spec is 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-2559bm5sr",
  	... // 2 identical fields
  }

Jun 11 00:22:19.593: INFO: Error updating pvc awsgctv6: PersistentVolumeClaim "awsgctv6" is invalid: spec: Forbidden: spec is 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-2559bm5sr",
  	... // 2 identical fields
  }

Jun 11 00:22:21.587: INFO: Error updating pvc awsgctv6: PersistentVolumeClaim "awsgctv6" is invalid: spec: Forbidden: spec is 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-2559bm5sr",
  	... // 2 identical fields
  }

Jun 11 00:22:23.588: INFO: Error updating pvc awsgctv6: PersistentVolumeClaim "awsgctv6" is invalid: spec: Forbidden: spec is 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-2559bm5sr",
  	... // 2 identical fields
  }

Jun 11 00:22:25.587: INFO: Error updating pvc awsgctv6: PersistentVolumeClaim "awsgctv6" is invalid: spec: Forbidden: spec is 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-2559bm5sr",
  	... // 2 identical fields
  }

Jun 11 00:22:27.587: INFO: Error updating pvc awsgctv6: PersistentVolumeClaim "awsgctv6" is invalid: spec: Forbidden: spec is 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-2559bm5sr",
  	... // 2 identical fields
  }

Jun 11 00:22:29.587: INFO: Error updating pvc awsgctv6: PersistentVolumeClaim "awsgctv6" is invalid: spec: Forbidden: spec is 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-2559bm5sr",
  	... // 2 identical fields
  }

Jun 11 00:22:31.588: INFO: Error updating pvc awsgctv6: PersistentVolumeClaim "awsgctv6" is invalid: spec: Forbidden: spec is 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-2559bm5sr",
  	... // 2 identical fields
  }

Jun 11 00:22:33.599: INFO: Error updating pvc awsgctv6: PersistentVolumeClaim "awsgctv6" is invalid: spec: Forbidden: spec is 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-2559bm5sr",
  	... // 2 identical fields
  }

Jun 11 00:22:35.587: INFO: Error updating pvc awsgctv6: PersistentVolumeClaim "awsgctv6" is invalid: spec: Forbidden: spec is 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-2559bm5sr",
  	... // 2 identical fields
  }

Jun 11 00:22:37.589: INFO: Error updating pvc awsgctv6: PersistentVolumeClaim "awsgctv6" is invalid: spec: Forbidden: spec is 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-2559bm5sr",
  	... // 2 identical fields
  }

Jun 11 00:22:37.818: INFO: Error updating pvc awsgctv6: PersistentVolumeClaim "awsgctv6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 255 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.PCf2odPVy/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.PCf2odPVy/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.PCf2odPVy/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.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Distro debian doesn't support ntfs -- skipping

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.PCf2odPVy/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.PCf2odPVy/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.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 50 lines ...
Jun 11 00:22:16.207: INFO: PersistentVolumeClaim pvc-b42zt found but phase is Pending instead of Bound.
Jun 11 00:22:18.322: INFO: PersistentVolumeClaim pvc-b42zt found and phase=Bound (12.802417603s)
Jun 11 00:22:18.322: INFO: Waiting up to 3m0s for PersistentVolume aws-vxxlg to have phase Bound
Jun 11 00:22:18.436: INFO: PersistentVolume aws-vxxlg found and phase=Bound (114.01728ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-v4lz
STEP: Creating a pod to test exec-volume-test
Jun 11 00:22:18.778: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-v4lz" in namespace "volume-6513" to be "Succeeded or Failed"
Jun 11 00:22:18.895: INFO: Pod "exec-volume-test-preprovisionedpv-v4lz": Phase="Pending", Reason="", readiness=false. Elapsed: 116.993868ms
Jun 11 00:22:21.013: INFO: Pod "exec-volume-test-preprovisionedpv-v4lz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.234633054s
Jun 11 00:22:23.129: INFO: Pod "exec-volume-test-preprovisionedpv-v4lz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.350756306s
Jun 11 00:22:25.244: INFO: Pod "exec-volume-test-preprovisionedpv-v4lz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.465930456s
Jun 11 00:22:27.359: INFO: Pod "exec-volume-test-preprovisionedpv-v4lz": Phase="Pending", Reason="", readiness=false. Elapsed: 8.58067938s
Jun 11 00:22:29.473: INFO: Pod "exec-volume-test-preprovisionedpv-v4lz": Phase="Pending", Reason="", readiness=false. Elapsed: 10.695033388s
... skipping 2 lines ...
Jun 11 00:22:35.817: INFO: Pod "exec-volume-test-preprovisionedpv-v4lz": Phase="Pending", Reason="", readiness=false. Elapsed: 17.039587737s
Jun 11 00:22:37.932: INFO: Pod "exec-volume-test-preprovisionedpv-v4lz": Phase="Pending", Reason="", readiness=false. Elapsed: 19.154589098s
Jun 11 00:22:40.047: INFO: Pod "exec-volume-test-preprovisionedpv-v4lz": Phase="Pending", Reason="", readiness=false. Elapsed: 21.268671131s
Jun 11 00:22:42.161: INFO: Pod "exec-volume-test-preprovisionedpv-v4lz": Phase="Pending", Reason="", readiness=false. Elapsed: 23.383572959s
Jun 11 00:22:44.277: INFO: Pod "exec-volume-test-preprovisionedpv-v4lz": Phase="Succeeded", Reason="", readiness=false. Elapsed: 25.499453306s
STEP: Saw pod success
Jun 11 00:22:44.278: INFO: Pod "exec-volume-test-preprovisionedpv-v4lz" satisfied condition "Succeeded or Failed"
Jun 11 00:22:44.391: INFO: Trying to get logs from node ip-172-20-45-141.eu-west-3.compute.internal pod exec-volume-test-preprovisionedpv-v4lz container exec-container-preprovisionedpv-v4lz: <nil>
STEP: delete the pod
Jun 11 00:22:45.176: INFO: Waiting for pod exec-volume-test-preprovisionedpv-v4lz to disappear
Jun 11 00:22:45.289: INFO: Pod exec-volume-test-preprovisionedpv-v4lz no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-v4lz
Jun 11 00:22:45.289: INFO: Deleting pod "exec-volume-test-preprovisionedpv-v4lz" in namespace "volume-6513"
STEP: Deleting pv and pvc
Jun 11 00:22:45.403: INFO: Deleting PersistentVolumeClaim "pvc-b42zt"
Jun 11 00:22:45.518: INFO: Deleting PersistentVolume "aws-vxxlg"
Jun 11 00:22:45.848: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0d42778b9c5453472", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d42778b9c5453472 is currently attached to i-048a05b12d63ed4b1
	status code: 400, request id: a0ee064a-1968-4040-a612-78f52ec1e469
Jun 11 00:22:51.418: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0d42778b9c5453472", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d42778b9c5453472 is currently attached to i-048a05b12d63ed4b1
	status code: 400, request id: 95a7302a-8166-4e6f-8287-94244528693b
Jun 11 00:22:57.020: INFO: Successfully deleted PD "aws://eu-west-3a/vol-0d42778b9c5453472".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 00:22:57.020: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-6513" for this suite.
... skipping 57 lines ...
Jun 11 00:22:02.850: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-697352d42
STEP: creating a claim
Jun 11 00:22:02.964: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-zqjx
STEP: Creating a pod to test subpath
Jun 11 00:22:03.314: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-zqjx" in namespace "provisioning-6973" to be "Succeeded or Failed"
Jun 11 00:22:03.435: INFO: Pod "pod-subpath-test-dynamicpv-zqjx": Phase="Pending", Reason="", readiness=false. Elapsed: 120.966524ms
Jun 11 00:22:05.548: INFO: Pod "pod-subpath-test-dynamicpv-zqjx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.234003794s
Jun 11 00:22:07.661: INFO: Pod "pod-subpath-test-dynamicpv-zqjx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.347489519s
Jun 11 00:22:09.777: INFO: Pod "pod-subpath-test-dynamicpv-zqjx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.463698588s
Jun 11 00:22:11.892: INFO: Pod "pod-subpath-test-dynamicpv-zqjx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.578453149s
Jun 11 00:22:14.007: INFO: Pod "pod-subpath-test-dynamicpv-zqjx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.693672517s
... skipping 8 lines ...
Jun 11 00:22:33.042: INFO: Pod "pod-subpath-test-dynamicpv-zqjx": Phase="Pending", Reason="", readiness=false. Elapsed: 29.728127704s
Jun 11 00:22:35.159: INFO: Pod "pod-subpath-test-dynamicpv-zqjx": Phase="Pending", Reason="", readiness=false. Elapsed: 31.845457441s
Jun 11 00:22:37.273: INFO: Pod "pod-subpath-test-dynamicpv-zqjx": Phase="Pending", Reason="", readiness=false. Elapsed: 33.959897658s
Jun 11 00:22:39.391: INFO: Pod "pod-subpath-test-dynamicpv-zqjx": Phase="Pending", Reason="", readiness=false. Elapsed: 36.077279329s
Jun 11 00:22:41.505: INFO: Pod "pod-subpath-test-dynamicpv-zqjx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 38.191579639s
STEP: Saw pod success
Jun 11 00:22:41.505: INFO: Pod "pod-subpath-test-dynamicpv-zqjx" satisfied condition "Succeeded or Failed"
Jun 11 00:22:41.619: INFO: Trying to get logs from node ip-172-20-42-226.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-zqjx container test-container-subpath-dynamicpv-zqjx: <nil>
STEP: delete the pod
Jun 11 00:22:41.859: INFO: Waiting for pod pod-subpath-test-dynamicpv-zqjx to disappear
Jun 11 00:22:41.971: INFO: Pod pod-subpath-test-dynamicpv-zqjx no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-zqjx
Jun 11 00:22:41.972: INFO: Deleting pod "pod-subpath-test-dynamicpv-zqjx" in namespace "provisioning-6973"
... skipping 74 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 00:22:06.676: 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.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun 11 00:22:07.540: INFO: Creating resource for dynamic PV
Jun 11 00:22:07.540: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9447-e2e-scd2x54
STEP: creating a claim
Jun 11 00:22:07.656: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-sw79
STEP: Checking for subpath error in container status
Jun 11 00:22:46.236: INFO: Deleting pod "pod-subpath-test-dynamicpv-sw79" in namespace "provisioning-9447"
Jun 11 00:22:46.351: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-sw79" to be fully deleted
STEP: Deleting pod
Jun 11 00:22:56.579: INFO: Deleting pod "pod-subpath-test-dynamicpv-sw79" in namespace "provisioning-9447"
STEP: Deleting pvc
Jun 11 00:22:56.954: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comm77zf"
... skipping 9 lines ...

• [SLOW TEST:55.999 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath file is outside the volume [Slow][LinuxOnly]
    /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 11 00:23:02.676: INFO: Driver "ebs.csi.aws.com" does not support volume type "InlineVolume" - skipping
[AfterEach] [Testpattern: Inline-volume (default fs)] subPath
... skipping 59 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 00:22:06.221: 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.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun 11 00:22:07.488: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 11 00:22:07.488: INFO: Creating resource for dynamic PV
Jun 11 00:22:07.488: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5903vs2kf
STEP: creating a claim
Jun 11 00:22:07.601: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-4zcr
STEP: Checking for subpath error in container status
Jun 11 00:22:32.171: INFO: Deleting pod "pod-subpath-test-dynamicpv-4zcr" in namespace "provisioning-5903"
Jun 11 00:22:32.285: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-4zcr" to be fully deleted
STEP: Deleting pod
Jun 11 00:22:46.511: INFO: Deleting pod "pod-subpath-test-dynamicpv-4zcr" in namespace "provisioning-5903"
STEP: Deleting pvc
Jun 11 00:22:46.849: INFO: Deleting PersistentVolumeClaim "awsvwxmr"
... skipping 13 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.PCf2odPVy/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.PCf2odPVy/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.PCf2odPVy/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.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Inline-volume (ext3)] volumes
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 11 00:23:02.772: INFO: Driver aws doesn't support ext3 -- skipping
[AfterEach] [Testpattern: Inline-volume (ext3)] volumes
... skipping 38 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 00:22:07.970: 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.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun 11 00:22:08.547: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 11 00:22:08.547: INFO: Creating resource for dynamic PV
Jun 11 00:22:08.547: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6051bgmdm
STEP: creating a claim
Jun 11 00:22:08.675: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-9vsk
STEP: Checking for subpath error in container status
Jun 11 00:22:37.312: INFO: Deleting pod "pod-subpath-test-dynamicpv-9vsk" in namespace "provisioning-6051"
Jun 11 00:22:37.427: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-9vsk" to be fully deleted
STEP: Deleting pod
Jun 11 00:22:47.654: INFO: Deleting pod "pod-subpath-test-dynamicpv-9vsk" in namespace "provisioning-6051"
STEP: Deleting pvc
Jun 11 00:22:47.995: INFO: Deleting PersistentVolumeClaim "awszsk54"
... skipping 13 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.PCf2odPVy/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.PCf2odPVy/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.PCf2odPVy/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.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [sig-storage] Zone Support [Feature:vsphere]
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 00:23:03.921: INFO: >>> kubeConfig: /root/.kube/config
... skipping 78 lines ...
Jun 11 00:22:05.442: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-27089l58s
STEP: creating a claim
Jun 11 00:22:05.556: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-frnw
STEP: Creating a pod to test subpath
Jun 11 00:22:05.913: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-frnw" in namespace "provisioning-2708" to be "Succeeded or Failed"
Jun 11 00:22:06.027: INFO: Pod "pod-subpath-test-dynamicpv-frnw": Phase="Pending", Reason="", readiness=false. Elapsed: 113.533864ms
Jun 11 00:22:08.142: INFO: Pod "pod-subpath-test-dynamicpv-frnw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.228311074s
Jun 11 00:22:10.258: INFO: Pod "pod-subpath-test-dynamicpv-frnw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.344129063s
Jun 11 00:22:12.374: INFO: Pod "pod-subpath-test-dynamicpv-frnw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.460177338s
Jun 11 00:22:14.488: INFO: Pod "pod-subpath-test-dynamicpv-frnw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.574593605s
Jun 11 00:22:16.604: INFO: Pod "pod-subpath-test-dynamicpv-frnw": Phase="Pending", Reason="", readiness=false. Elapsed: 10.690554653s
... skipping 8 lines ...
Jun 11 00:22:35.647: INFO: Pod "pod-subpath-test-dynamicpv-frnw": Phase="Pending", Reason="", readiness=false. Elapsed: 29.733230496s
Jun 11 00:22:37.763: INFO: Pod "pod-subpath-test-dynamicpv-frnw": Phase="Pending", Reason="", readiness=false. Elapsed: 31.849248186s
Jun 11 00:22:39.877: INFO: Pod "pod-subpath-test-dynamicpv-frnw": Phase="Pending", Reason="", readiness=false. Elapsed: 33.963225283s
Jun 11 00:22:41.991: INFO: Pod "pod-subpath-test-dynamicpv-frnw": Phase="Pending", Reason="", readiness=false. Elapsed: 36.077235892s
Jun 11 00:22:44.105: INFO: Pod "pod-subpath-test-dynamicpv-frnw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 38.191877708s
STEP: Saw pod success
Jun 11 00:22:44.106: INFO: Pod "pod-subpath-test-dynamicpv-frnw" satisfied condition "Succeeded or Failed"
Jun 11 00:22:44.220: INFO: Trying to get logs from node ip-172-20-45-141.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-frnw container test-container-subpath-dynamicpv-frnw: <nil>
STEP: delete the pod
Jun 11 00:22:44.777: INFO: Waiting for pod pod-subpath-test-dynamicpv-frnw to disappear
Jun 11 00:22:44.891: INFO: Pod pod-subpath-test-dynamicpv-frnw no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-frnw
Jun 11 00:22:44.891: INFO: Deleting pod "pod-subpath-test-dynamicpv-frnw" in namespace "provisioning-2708"
STEP: Creating pod pod-subpath-test-dynamicpv-frnw
STEP: Creating a pod to test subpath
Jun 11 00:22:45.122: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-frnw" in namespace "provisioning-2708" to be "Succeeded or Failed"
Jun 11 00:22:45.236: INFO: Pod "pod-subpath-test-dynamicpv-frnw": Phase="Pending", Reason="", readiness=false. Elapsed: 113.622029ms
Jun 11 00:22:47.355: INFO: Pod "pod-subpath-test-dynamicpv-frnw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.232971363s
Jun 11 00:22:49.469: INFO: Pod "pod-subpath-test-dynamicpv-frnw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.346769866s
Jun 11 00:22:51.583: INFO: Pod "pod-subpath-test-dynamicpv-frnw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.460839192s
Jun 11 00:22:53.697: INFO: Pod "pod-subpath-test-dynamicpv-frnw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.57441418s
STEP: Saw pod success
Jun 11 00:22:53.697: INFO: Pod "pod-subpath-test-dynamicpv-frnw" satisfied condition "Succeeded or Failed"
Jun 11 00:22:53.810: INFO: Trying to get logs from node ip-172-20-45-141.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-frnw container test-container-subpath-dynamicpv-frnw: <nil>
STEP: delete the pod
Jun 11 00:22:54.046: INFO: Waiting for pod pod-subpath-test-dynamicpv-frnw to disappear
Jun 11 00:22:54.159: INFO: Pod pod-subpath-test-dynamicpv-frnw no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-frnw
Jun 11 00:22:54.159: INFO: Deleting pod "pod-subpath-test-dynamicpv-frnw" in namespace "provisioning-2708"
... skipping 385 lines ...
Jun 11 00:23:28.844: INFO: Waiting for pod aws-client to disappear
Jun 11 00:23:28.957: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 11 00:23:28.957: INFO: Deleting PersistentVolumeClaim "pvc-58p85"
Jun 11 00:23:29.071: INFO: Deleting PersistentVolume "aws-btfdv"
Jun 11 00:23:29.764: INFO: Couldn't delete PD "aws://eu-west-3a/vol-02d3a332c45ae772d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02d3a332c45ae772d is currently attached to i-0fcdea48570ae258b
	status code: 400, request id: 1cf8db66-c3e6-48a7-b330-1c4b8158fe56
Jun 11 00:23:35.355: INFO: Couldn't delete PD "aws://eu-west-3a/vol-02d3a332c45ae772d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02d3a332c45ae772d is currently attached to i-0fcdea48570ae258b
	status code: 400, request id: 072cd515-7ce9-46a6-9263-d748d8250185
Jun 11 00:23:40.966: INFO: Successfully deleted PD "aws://eu-west-3a/vol-02d3a332c45ae772d".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 00:23:40.967: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-850" for this suite.
... skipping 18 lines ...

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

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

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

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

    /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:92
------------------------------
... skipping 245 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 00:23:20.781: 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.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun 11 00:23:21.353: INFO: Creating resource for dynamic PV
Jun 11 00:23:21.353: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-784-e2e-scxfggg
STEP: creating a claim
Jun 11 00:23:21.473: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-wvzc
STEP: Checking for subpath error in container status
Jun 11 00:23:32.052: INFO: Deleting pod "pod-subpath-test-dynamicpv-wvzc" in namespace "provisioning-784"
Jun 11 00:23:32.168: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-wvzc" to be fully deleted
STEP: Deleting pod
Jun 11 00:23:44.401: INFO: Deleting pod "pod-subpath-test-dynamicpv-wvzc" in namespace "provisioning-784"
STEP: Deleting pvc
Jun 11 00:23:44.748: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comb6kgp"
... skipping 10 lines ...

• [SLOW TEST:34.785 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath directory is outside the volume [Slow][LinuxOnly]
    /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 11 00:23:55.568: INFO: Distro debian doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
... skipping 442 lines ...
Jun 11 00:22:38.975: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1323-e2e-scfqwz7
STEP: creating a claim
Jun 11 00:22:39.091: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-qr87
STEP: Creating a pod to test subpath
Jun 11 00:22:39.441: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-qr87" in namespace "provisioning-1323" to be "Succeeded or Failed"
Jun 11 00:22:39.555: INFO: Pod "pod-subpath-test-dynamicpv-qr87": Phase="Pending", Reason="", readiness=false. Elapsed: 113.767538ms
Jun 11 00:22:41.669: INFO: Pod "pod-subpath-test-dynamicpv-qr87": Phase="Pending", Reason="", readiness=false. Elapsed: 2.227885481s
Jun 11 00:22:43.783: INFO: Pod "pod-subpath-test-dynamicpv-qr87": Phase="Pending", Reason="", readiness=false. Elapsed: 4.34172725s
Jun 11 00:22:45.898: INFO: Pod "pod-subpath-test-dynamicpv-qr87": Phase="Pending", Reason="", readiness=false. Elapsed: 6.45663796s
Jun 11 00:22:48.014: INFO: Pod "pod-subpath-test-dynamicpv-qr87": Phase="Pending", Reason="", readiness=false. Elapsed: 8.57234687s
Jun 11 00:22:50.130: INFO: Pod "pod-subpath-test-dynamicpv-qr87": Phase="Pending", Reason="", readiness=false. Elapsed: 10.688267276s
... skipping 2 lines ...
Jun 11 00:22:56.473: INFO: Pod "pod-subpath-test-dynamicpv-qr87": Phase="Pending", Reason="", readiness=false. Elapsed: 17.031395292s
Jun 11 00:22:58.589: INFO: Pod "pod-subpath-test-dynamicpv-qr87": Phase="Pending", Reason="", readiness=false. Elapsed: 19.147567224s
Jun 11 00:23:00.706: INFO: Pod "pod-subpath-test-dynamicpv-qr87": Phase="Pending", Reason="", readiness=false. Elapsed: 21.264523645s
Jun 11 00:23:02.820: INFO: Pod "pod-subpath-test-dynamicpv-qr87": Phase="Pending", Reason="", readiness=false. Elapsed: 23.378446117s
Jun 11 00:23:04.934: INFO: Pod "pod-subpath-test-dynamicpv-qr87": Phase="Succeeded", Reason="", readiness=false. Elapsed: 25.492581356s
STEP: Saw pod success
Jun 11 00:23:04.934: INFO: Pod "pod-subpath-test-dynamicpv-qr87" satisfied condition "Succeeded or Failed"
Jun 11 00:23:05.048: INFO: Trying to get logs from node ip-172-20-55-69.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-qr87 container test-container-subpath-dynamicpv-qr87: <nil>
STEP: delete the pod
Jun 11 00:23:05.282: INFO: Waiting for pod pod-subpath-test-dynamicpv-qr87 to disappear
Jun 11 00:23:05.395: INFO: Pod pod-subpath-test-dynamicpv-qr87 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-qr87
Jun 11 00:23:05.395: INFO: Deleting pod "pod-subpath-test-dynamicpv-qr87" in namespace "provisioning-1323"
STEP: Creating pod pod-subpath-test-dynamicpv-qr87
STEP: Creating a pod to test subpath
Jun 11 00:23:05.627: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-qr87" in namespace "provisioning-1323" to be "Succeeded or Failed"
Jun 11 00:23:05.740: INFO: Pod "pod-subpath-test-dynamicpv-qr87": Phase="Pending", Reason="", readiness=false. Elapsed: 113.453489ms
Jun 11 00:23:07.857: INFO: Pod "pod-subpath-test-dynamicpv-qr87": Phase="Pending", Reason="", readiness=false. Elapsed: 2.230410778s
Jun 11 00:23:09.973: INFO: Pod "pod-subpath-test-dynamicpv-qr87": Phase="Pending", Reason="", readiness=false. Elapsed: 4.346308382s
Jun 11 00:23:12.087: INFO: Pod "pod-subpath-test-dynamicpv-qr87": Phase="Pending", Reason="", readiness=false. Elapsed: 6.460381858s
Jun 11 00:23:14.202: INFO: Pod "pod-subpath-test-dynamicpv-qr87": Phase="Pending", Reason="", readiness=false. Elapsed: 8.575296665s
Jun 11 00:23:16.317: INFO: Pod "pod-subpath-test-dynamicpv-qr87": Phase="Pending", Reason="", readiness=false. Elapsed: 10.690268675s
... skipping 6 lines ...
Jun 11 00:23:31.121: INFO: Pod "pod-subpath-test-dynamicpv-qr87": Phase="Pending", Reason="", readiness=false. Elapsed: 25.494080855s
Jun 11 00:23:33.236: INFO: Pod "pod-subpath-test-dynamicpv-qr87": Phase="Pending", Reason="", readiness=false. Elapsed: 27.609196258s
Jun 11 00:23:35.350: INFO: Pod "pod-subpath-test-dynamicpv-qr87": Phase="Pending", Reason="", readiness=false. Elapsed: 29.723294816s
Jun 11 00:23:37.464: INFO: Pod "pod-subpath-test-dynamicpv-qr87": Phase="Pending", Reason="", readiness=false. Elapsed: 31.837343765s
Jun 11 00:23:39.578: INFO: Pod "pod-subpath-test-dynamicpv-qr87": Phase="Succeeded", Reason="", readiness=false. Elapsed: 33.951679375s
STEP: Saw pod success
Jun 11 00:23:39.578: INFO: Pod "pod-subpath-test-dynamicpv-qr87" satisfied condition "Succeeded or Failed"
Jun 11 00:23:39.692: INFO: Trying to get logs from node ip-172-20-45-141.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-qr87 container test-container-subpath-dynamicpv-qr87: <nil>
STEP: delete the pod
Jun 11 00:23:39.939: INFO: Waiting for pod pod-subpath-test-dynamicpv-qr87 to disappear
Jun 11 00:23:40.052: INFO: Pod pod-subpath-test-dynamicpv-qr87 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-qr87
Jun 11 00:23:40.052: INFO: Deleting pod "pod-subpath-test-dynamicpv-qr87" in namespace "provisioning-1323"
... skipping 59 lines ...
Jun 11 00:22:03.854: INFO: Creating resource for dynamic PV
Jun 11 00:22:03.854: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8340-e2e-scc7h9g
STEP: creating a claim
Jun 11 00:22:03.970: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-8340
Jun 11 00:22:04.315: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-8340" in namespace "provisioning-8340" to be "Succeeded or Failed"
Jun 11 00:22:04.429: INFO: Pod "volume-prep-provisioning-8340": Phase="Pending", Reason="", readiness=false. Elapsed: 113.879233ms
Jun 11 00:22:06.552: INFO: Pod "volume-prep-provisioning-8340": Phase="Pending", Reason="", readiness=false. Elapsed: 2.237184441s
Jun 11 00:22:08.680: INFO: Pod "volume-prep-provisioning-8340": Phase="Pending", Reason="", readiness=false. Elapsed: 4.365005589s
Jun 11 00:22:10.794: INFO: Pod "volume-prep-provisioning-8340": Phase="Pending", Reason="", readiness=false. Elapsed: 6.479026801s
Jun 11 00:22:12.908: INFO: Pod "volume-prep-provisioning-8340": Phase="Pending", Reason="", readiness=false. Elapsed: 8.592971259s
Jun 11 00:22:15.022: INFO: Pod "volume-prep-provisioning-8340": Phase="Pending", Reason="", readiness=false. Elapsed: 10.707249533s
... skipping 3 lines ...
Jun 11 00:22:23.496: INFO: Pod "volume-prep-provisioning-8340": Phase="Pending", Reason="", readiness=false. Elapsed: 19.181024874s
Jun 11 00:22:25.611: INFO: Pod "volume-prep-provisioning-8340": Phase="Pending", Reason="", readiness=false. Elapsed: 21.295701535s
Jun 11 00:22:27.727: INFO: Pod "volume-prep-provisioning-8340": Phase="Pending", Reason="", readiness=false. Elapsed: 23.411989122s
Jun 11 00:22:29.845: INFO: Pod "volume-prep-provisioning-8340": Phase="Pending", Reason="", readiness=false. Elapsed: 25.529714801s
Jun 11 00:22:31.960: INFO: Pod "volume-prep-provisioning-8340": Phase="Succeeded", Reason="", readiness=false. Elapsed: 27.644949108s
STEP: Saw pod success
Jun 11 00:22:31.960: INFO: Pod "volume-prep-provisioning-8340" satisfied condition "Succeeded or Failed"
Jun 11 00:22:31.960: INFO: Deleting pod "volume-prep-provisioning-8340" in namespace "provisioning-8340"
Jun 11 00:22:32.081: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-8340" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-8tmp
STEP: Checking for subpath error in container status
Jun 11 00:23:40.537: INFO: Deleting pod "pod-subpath-test-dynamicpv-8tmp" in namespace "provisioning-8340"
Jun 11 00:23:40.666: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-8tmp" to be fully deleted
STEP: Deleting pod
Jun 11 00:23:40.780: INFO: Deleting pod "pod-subpath-test-dynamicpv-8tmp" in namespace "provisioning-8340"
STEP: Deleting pvc
Jun 11 00:23:41.151: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comr48wc"
... skipping 319 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.PCf2odPVy/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.PCf2odPVy/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.PCf2odPVy/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.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 19 lines ...
Jun 11 00:23:45.468: INFO: PersistentVolumeClaim pvc-w9lrd found but phase is Pending instead of Bound.
Jun 11 00:23:47.582: INFO: PersistentVolumeClaim pvc-w9lrd found and phase=Bound (4.342547742s)
Jun 11 00:23:47.582: INFO: Waiting up to 3m0s for PersistentVolume aws-kp66c to have phase Bound
Jun 11 00:23:47.695: INFO: PersistentVolume aws-kp66c found and phase=Bound (112.935777ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-27sw
STEP: Creating a pod to test exec-volume-test
Jun 11 00:23:48.035: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-27sw" in namespace "volume-8951" to be "Succeeded or Failed"
Jun 11 00:23:48.148: INFO: Pod "exec-volume-test-preprovisionedpv-27sw": Phase="Pending", Reason="", readiness=false. Elapsed: 113.230893ms
Jun 11 00:23:50.262: INFO: Pod "exec-volume-test-preprovisionedpv-27sw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.226674492s
Jun 11 00:23:52.375: INFO: Pod "exec-volume-test-preprovisionedpv-27sw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.340404804s
Jun 11 00:23:54.489: INFO: Pod "exec-volume-test-preprovisionedpv-27sw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.4536741s
Jun 11 00:23:56.603: INFO: Pod "exec-volume-test-preprovisionedpv-27sw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.568290345s
Jun 11 00:23:58.717: INFO: Pod "exec-volume-test-preprovisionedpv-27sw": Phase="Pending", Reason="", readiness=false. Elapsed: 10.681928949s
Jun 11 00:24:00.831: INFO: Pod "exec-volume-test-preprovisionedpv-27sw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.795940966s
STEP: Saw pod success
Jun 11 00:24:00.831: INFO: Pod "exec-volume-test-preprovisionedpv-27sw" satisfied condition "Succeeded or Failed"
Jun 11 00:24:00.944: INFO: Trying to get logs from node ip-172-20-47-248.eu-west-3.compute.internal pod exec-volume-test-preprovisionedpv-27sw container exec-container-preprovisionedpv-27sw: <nil>
STEP: delete the pod
Jun 11 00:24:01.182: INFO: Waiting for pod exec-volume-test-preprovisionedpv-27sw to disappear
Jun 11 00:24:01.298: INFO: Pod exec-volume-test-preprovisionedpv-27sw no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-27sw
Jun 11 00:24:01.298: INFO: Deleting pod "exec-volume-test-preprovisionedpv-27sw" in namespace "volume-8951"
STEP: Deleting pv and pvc
Jun 11 00:24:01.412: INFO: Deleting PersistentVolumeClaim "pvc-w9lrd"
Jun 11 00:24:01.526: INFO: Deleting PersistentVolume "aws-kp66c"
Jun 11 00:24:01.854: INFO: Couldn't delete PD "aws://eu-west-3a/vol-00e4df0a8a4e2e35e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00e4df0a8a4e2e35e is currently attached to i-00014b5ed56029a5c
	status code: 400, request id: 28c81c3d-041e-4adb-9a12-f0d4eefc036e
Jun 11 00:24:07.441: INFO: Couldn't delete PD "aws://eu-west-3a/vol-00e4df0a8a4e2e35e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00e4df0a8a4e2e35e is currently attached to i-00014b5ed56029a5c
	status code: 400, request id: 353fbf98-77a4-4bd4-ab67-ad63726497d4
Jun 11 00:24:13.050: INFO: Couldn't delete PD "aws://eu-west-3a/vol-00e4df0a8a4e2e35e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00e4df0a8a4e2e35e is currently attached to i-00014b5ed56029a5c
	status code: 400, request id: 80bb6b10-0c5c-4f5b-a29a-fe20972016c9
Jun 11 00:24:18.639: INFO: Couldn't delete PD "aws://eu-west-3a/vol-00e4df0a8a4e2e35e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00e4df0a8a4e2e35e is currently attached to i-00014b5ed56029a5c
	status code: 400, request id: 1e0cd2ed-254b-4059-bccc-33d25b6cc7f6
Jun 11 00:24:24.224: INFO: Successfully deleted PD "aws://eu-west-3a/vol-00e4df0a8a4e2e35e".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 00:24:24.225: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8951" for this suite.
... skipping 176 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.PCf2odPVy/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.PCf2odPVy/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.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 242 lines ...
Jun 11 00:24:31.471: INFO: Waiting for pod aws-client to disappear
Jun 11 00:24:31.584: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 11 00:24:31.584: INFO: Deleting PersistentVolumeClaim "pvc-bq4mk"
Jun 11 00:24:31.698: INFO: Deleting PersistentVolume "aws-rjhkd"
Jun 11 00:24:32.405: INFO: Couldn't delete PD "aws://eu-west-3a/vol-01608a22fab0170c9", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01608a22fab0170c9 is currently attached to i-00014b5ed56029a5c
	status code: 400, request id: 9e9618c8-463d-4cab-ad61-bd9863b9817a
Jun 11 00:24:38.028: INFO: Successfully deleted PD "aws://eu-west-3a/vol-01608a22fab0170c9".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 00:24:38.028: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-340" for this suite.
... skipping 501 lines ...
Jun 11 00:24:08.500: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-99096cjlh
STEP: creating a claim
Jun 11 00:24:08.617: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-pg67
STEP: Creating a pod to test subpath
Jun 11 00:24:08.959: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-pg67" in namespace "provisioning-9909" to be "Succeeded or Failed"
Jun 11 00:24:09.072: INFO: Pod "pod-subpath-test-dynamicpv-pg67": Phase="Pending", Reason="", readiness=false. Elapsed: 112.556957ms
Jun 11 00:24:11.185: INFO: Pod "pod-subpath-test-dynamicpv-pg67": Phase="Pending", Reason="", readiness=false. Elapsed: 2.225728702s
Jun 11 00:24:13.299: INFO: Pod "pod-subpath-test-dynamicpv-pg67": Phase="Pending", Reason="", readiness=false. Elapsed: 4.339162199s
Jun 11 00:24:15.412: INFO: Pod "pod-subpath-test-dynamicpv-pg67": Phase="Pending", Reason="", readiness=false. Elapsed: 6.452609833s
Jun 11 00:24:17.525: INFO: Pod "pod-subpath-test-dynamicpv-pg67": Phase="Pending", Reason="", readiness=false. Elapsed: 8.566006008s
Jun 11 00:24:19.639: INFO: Pod "pod-subpath-test-dynamicpv-pg67": Phase="Pending", Reason="", readiness=false. Elapsed: 10.679620727s
... skipping 2 lines ...
Jun 11 00:24:25.979: INFO: Pod "pod-subpath-test-dynamicpv-pg67": Phase="Pending", Reason="", readiness=false. Elapsed: 17.019271903s
Jun 11 00:24:28.092: INFO: Pod "pod-subpath-test-dynamicpv-pg67": Phase="Pending", Reason="", readiness=false. Elapsed: 19.132655521s
Jun 11 00:24:30.207: INFO: Pod "pod-subpath-test-dynamicpv-pg67": Phase="Pending", Reason="", readiness=false. Elapsed: 21.24715426s
Jun 11 00:24:32.320: INFO: Pod "pod-subpath-test-dynamicpv-pg67": Phase="Pending", Reason="", readiness=false. Elapsed: 23.360108556s
Jun 11 00:24:34.434: INFO: Pod "pod-subpath-test-dynamicpv-pg67": Phase="Succeeded", Reason="", readiness=false. Elapsed: 25.474388905s
STEP: Saw pod success
Jun 11 00:24:34.434: INFO: Pod "pod-subpath-test-dynamicpv-pg67" satisfied condition "Succeeded or Failed"
Jun 11 00:24:34.547: INFO: Trying to get logs from node ip-172-20-55-69.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-pg67 container test-container-subpath-dynamicpv-pg67: <nil>
STEP: delete the pod
Jun 11 00:24:34.786: INFO: Waiting for pod pod-subpath-test-dynamicpv-pg67 to disappear
Jun 11 00:24:34.899: INFO: Pod pod-subpath-test-dynamicpv-pg67 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-pg67
Jun 11 00:24:34.899: INFO: Deleting pod "pod-subpath-test-dynamicpv-pg67" in namespace "provisioning-9909"
... skipping 258 lines ...
Jun 11 00:24:49.229: INFO: Waiting for pod aws-client to disappear
Jun 11 00:24:49.342: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 11 00:24:49.342: INFO: Deleting PersistentVolumeClaim "pvc-gpdcv"
Jun 11 00:24:49.456: INFO: Deleting PersistentVolume "aws-87gw9"
Jun 11 00:24:50.247: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0a2ab1c7708d042c2", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a2ab1c7708d042c2 is currently attached to i-0690821a57784e40a
	status code: 400, request id: 87f6f945-ab11-4338-a5b6-465cbaaf1f5b
Jun 11 00:24:55.841: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0a2ab1c7708d042c2", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a2ab1c7708d042c2 is currently attached to i-0690821a57784e40a
	status code: 400, request id: 4b2ced53-53ed-4d6a-a859-75953eecfad4
Jun 11 00:25:01.534: INFO: Successfully deleted PD "aws://eu-west-3a/vol-0a2ab1c7708d042c2".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumes
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 00:25:01.534: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-7834" for this suite.
... skipping 250 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.PCf2odPVy/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.PCf2odPVy/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.PCf2odPVy/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.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Distro debian doesn't support ntfs -- skipping

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.PCf2odPVy/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.PCf2odPVy/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.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 101 lines ...
Jun 11 00:24:17.480: INFO: Creating resource for dynamic PV
Jun 11 00:24:17.480: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-11338ngf8
STEP: creating a claim
Jun 11 00:24:17.594: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-1133
Jun 11 00:24:17.952: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-1133" in namespace "provisioning-1133" to be "Succeeded or Failed"
Jun 11 00:24:18.065: INFO: Pod "volume-prep-provisioning-1133": Phase="Pending", Reason="", readiness=false. Elapsed: 113.58722ms
Jun 11 00:24:20.181: INFO: Pod "volume-prep-provisioning-1133": Phase="Pending", Reason="", readiness=false. Elapsed: 2.22940796s
Jun 11 00:24:22.296: INFO: Pod "volume-prep-provisioning-1133": Phase="Pending", Reason="", readiness=false. Elapsed: 4.344314656s
Jun 11 00:24:24.409: INFO: Pod "volume-prep-provisioning-1133": Phase="Pending", Reason="", readiness=false. Elapsed: 6.457366065s
Jun 11 00:24:26.522: INFO: Pod "volume-prep-provisioning-1133": Phase="Pending", Reason="", readiness=false. Elapsed: 8.570056762s
Jun 11 00:24:28.635: INFO: Pod "volume-prep-provisioning-1133": Phase="Pending", Reason="", readiness=false. Elapsed: 10.683220959s
... skipping 2 lines ...
Jun 11 00:24:34.984: INFO: Pod "volume-prep-provisioning-1133": Phase="Pending", Reason="", readiness=false. Elapsed: 17.032155039s
Jun 11 00:24:37.097: INFO: Pod "volume-prep-provisioning-1133": Phase="Pending", Reason="", readiness=false. Elapsed: 19.145555841s
Jun 11 00:24:39.211: INFO: Pod "volume-prep-provisioning-1133": Phase="Pending", Reason="", readiness=false. Elapsed: 21.259089054s
Jun 11 00:24:41.325: INFO: Pod "volume-prep-provisioning-1133": Phase="Pending", Reason="", readiness=false. Elapsed: 23.37321841s
Jun 11 00:24:43.443: INFO: Pod "volume-prep-provisioning-1133": Phase="Succeeded", Reason="", readiness=false. Elapsed: 25.491453681s
STEP: Saw pod success
Jun 11 00:24:43.443: INFO: Pod "volume-prep-provisioning-1133" satisfied condition "Succeeded or Failed"
Jun 11 00:24:43.443: INFO: Deleting pod "volume-prep-provisioning-1133" in namespace "provisioning-1133"
Jun 11 00:24:43.575: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-1133" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-v7vs
STEP: Checking for subpath error in container status
Jun 11 00:24:56.032: INFO: Deleting pod "pod-subpath-test-dynamicpv-v7vs" in namespace "provisioning-1133"
Jun 11 00:24:56.150: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-v7vs" to be fully deleted
STEP: Deleting pod
Jun 11 00:24:56.266: INFO: Deleting pod "pod-subpath-test-dynamicpv-v7vs" in namespace "provisioning-1133"
STEP: Deleting pvc
Jun 11 00:24:56.605: INFO: Deleting PersistentVolumeClaim "awsjbqfq"
... skipping 219 lines ...
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 00:25:13.961: 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.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Jun 11 00:25:14.646: INFO: found topology map[topology.kubernetes.io/zone:eu-west-3a]
Jun 11 00:25:14.646: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 11 00:25:14.646: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.PCf2odPVy/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.PCf2odPVy/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (delayed binding)] topology
    /tmp/kops.PCf2odPVy/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.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 39 lines ...

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

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

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

    /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 23 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 00:24:31.943: 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.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 11 00:24:32.505: INFO: Creating resource for dynamic PV
Jun 11 00:24:32.505: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-5640-e2e-scvplst
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 11 00:24:39.303: INFO: Deleting pod "pod-39314f37-7026-40c8-9601-edf4aab23aae" in namespace "volumemode-5640"
Jun 11 00:24:39.417: INFO: Wait up to 5m0s for pod "pod-39314f37-7026-40c8-9601-edf4aab23aae" to be fully deleted
STEP: Deleting pvc
Jun 11 00:24:47.867: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com2jflq"
Jun 11 00:24:47.984: INFO: Waiting up to 5m0s for PersistentVolume pvc-e3cd6339-7540-483d-af13-5b4b25b37d5c to get deleted
Jun 11 00:24:48.096: INFO: PersistentVolume pvc-e3cd6339-7540-483d-af13-5b4b25b37d5c found and phase=Released (111.969106ms)
... skipping 13 lines ...

• [SLOW TEST:52.298 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.PCf2odPVy/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.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [sig-storage] Zone Support [Feature:vsphere]
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 00:25:24.243: INFO: >>> kubeConfig: /root/.kube/config
... skipping 76 lines ...
Jun 11 00:24:26.630: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4663-e2e-sc825jv
STEP: creating a claim
Jun 11 00:24:26.746: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-6zfb
STEP: Creating a pod to test subpath
Jun 11 00:24:27.089: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-6zfb" in namespace "provisioning-4663" to be "Succeeded or Failed"
Jun 11 00:24:27.205: INFO: Pod "pod-subpath-test-dynamicpv-6zfb": Phase="Pending", Reason="", readiness=false. Elapsed: 116.040897ms
Jun 11 00:24:29.319: INFO: Pod "pod-subpath-test-dynamicpv-6zfb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.230172294s
Jun 11 00:24:31.437: INFO: Pod "pod-subpath-test-dynamicpv-6zfb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.347323939s
Jun 11 00:24:33.568: INFO: Pod "pod-subpath-test-dynamicpv-6zfb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.47854945s
Jun 11 00:24:35.682: INFO: Pod "pod-subpath-test-dynamicpv-6zfb": Phase="Pending", Reason="", readiness=false. Elapsed: 8.592685692s
Jun 11 00:24:37.795: INFO: Pod "pod-subpath-test-dynamicpv-6zfb": Phase="Pending", Reason="", readiness=false. Elapsed: 10.706051482s
Jun 11 00:24:39.909: INFO: Pod "pod-subpath-test-dynamicpv-6zfb": Phase="Pending", Reason="", readiness=false. Elapsed: 12.819379777s
Jun 11 00:24:42.024: INFO: Pod "pod-subpath-test-dynamicpv-6zfb": Phase="Pending", Reason="", readiness=false. Elapsed: 14.934592506s
Jun 11 00:24:44.141: INFO: Pod "pod-subpath-test-dynamicpv-6zfb": Phase="Pending", Reason="", readiness=false. Elapsed: 17.051683158s
Jun 11 00:24:46.258: INFO: Pod "pod-subpath-test-dynamicpv-6zfb": Phase="Pending", Reason="", readiness=false. Elapsed: 19.169131287s
Jun 11 00:24:48.373: INFO: Pod "pod-subpath-test-dynamicpv-6zfb": Phase="Pending", Reason="", readiness=false. Elapsed: 21.284044301s
Jun 11 00:24:50.490: INFO: Pod "pod-subpath-test-dynamicpv-6zfb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.400388667s
STEP: Saw pod success
Jun 11 00:24:50.490: INFO: Pod "pod-subpath-test-dynamicpv-6zfb" satisfied condition "Succeeded or Failed"
Jun 11 00:24:50.603: INFO: Trying to get logs from node ip-172-20-55-69.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-6zfb container test-container-subpath-dynamicpv-6zfb: <nil>
STEP: delete the pod
Jun 11 00:24:50.844: INFO: Waiting for pod pod-subpath-test-dynamicpv-6zfb to disappear
Jun 11 00:24:50.957: INFO: Pod pod-subpath-test-dynamicpv-6zfb no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-6zfb
Jun 11 00:24:50.957: INFO: Deleting pod "pod-subpath-test-dynamicpv-6zfb" in namespace "provisioning-4663"
... skipping 171 lines ...
Jun 11 00:23:56.144: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-9818-e2e-scbnfqq      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-9818    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-9818-e2e-scbnfqq,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-9818    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-9818-e2e-scbnfqq,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-9818    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-9818-e2e-scbnfqq,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-9818-e2e-scbnfqq    d0bde2f0-f1cd-4586-a430-13d9e54a63fc 5837 0 2021-06-11 00:23:56 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-11 00:23:56 +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-c8zcg pvc- provisioning-9818  976104c8-1430-45c9-bfc6-23dee7977be7 5841 0 2021-06-11 00:23:56 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-11 00:23:56 +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-9818-e2e-scbnfqq,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-c7d993d9-000b-454e-9151-7e92d12b339b in namespace provisioning-9818
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun 11 00:24:35.420: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-tghpc" in namespace "provisioning-9818" to be "Succeeded or Failed"
Jun 11 00:24:35.534: INFO: Pod "pvc-volume-tester-writer-tghpc": Phase="Pending", Reason="", readiness=false. Elapsed: 113.572564ms
Jun 11 00:24:37.648: INFO: Pod "pvc-volume-tester-writer-tghpc": Phase="Pending", Reason="", readiness=false. Elapsed: 2.227604214s
Jun 11 00:24:39.762: INFO: Pod "pvc-volume-tester-writer-tghpc": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.341504749s
STEP: Saw pod success
Jun 11 00:24:39.762: INFO: Pod "pvc-volume-tester-writer-tghpc" satisfied condition "Succeeded or Failed"
Jun 11 00:24:39.991: INFO: Pod pvc-volume-tester-writer-tghpc has the following logs: 
Jun 11 00:24:39.991: INFO: Deleting pod "pvc-volume-tester-writer-tghpc" in namespace "provisioning-9818"
Jun 11 00:24:40.113: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-tghpc" 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-47-248.eu-west-3.compute.internal"
Jun 11 00:24:40.570: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-wlr7p" in namespace "provisioning-9818" to be "Succeeded or Failed"
Jun 11 00:24:40.683: INFO: Pod "pvc-volume-tester-reader-wlr7p": Phase="Pending", Reason="", readiness=false. Elapsed: 113.237721ms
Jun 11 00:24:42.797: INFO: Pod "pvc-volume-tester-reader-wlr7p": Phase="Pending", Reason="", readiness=false. Elapsed: 2.227219309s
Jun 11 00:24:44.911: INFO: Pod "pvc-volume-tester-reader-wlr7p": Phase="Pending", Reason="", readiness=false. Elapsed: 4.341262968s
Jun 11 00:24:47.025: INFO: Pod "pvc-volume-tester-reader-wlr7p": Phase="Pending", Reason="", readiness=false. Elapsed: 6.455082045s
Jun 11 00:24:49.139: INFO: Pod "pvc-volume-tester-reader-wlr7p": Phase="Pending", Reason="", readiness=false. Elapsed: 8.569101174s
Jun 11 00:24:51.253: INFO: Pod "pvc-volume-tester-reader-wlr7p": Phase="Pending", Reason="", readiness=false. Elapsed: 10.682796211s
Jun 11 00:24:53.375: INFO: Pod "pvc-volume-tester-reader-wlr7p": Phase="Pending", Reason="", readiness=false. Elapsed: 12.804500616s
Jun 11 00:24:55.488: INFO: Pod "pvc-volume-tester-reader-wlr7p": Phase="Pending", Reason="", readiness=false. Elapsed: 14.918055574s
Jun 11 00:24:57.602: INFO: Pod "pvc-volume-tester-reader-wlr7p": Phase="Pending", Reason="", readiness=false. Elapsed: 17.032037747s
Jun 11 00:24:59.717: INFO: Pod "pvc-volume-tester-reader-wlr7p": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.146933764s
STEP: Saw pod success
Jun 11 00:24:59.717: INFO: Pod "pvc-volume-tester-reader-wlr7p" satisfied condition "Succeeded or Failed"
Jun 11 00:24:59.947: INFO: Pod pvc-volume-tester-reader-wlr7p has the following logs: hello world

Jun 11 00:24:59.947: INFO: Deleting pod "pvc-volume-tester-reader-wlr7p" in namespace "provisioning-9818"
Jun 11 00:25:00.067: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-wlr7p" to be fully deleted
Jun 11 00:25:00.182: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-c8zcg] to have phase Bound
Jun 11 00:25:00.296: INFO: PersistentVolumeClaim pvc-c8zcg found and phase=Bound (113.584334ms)
... skipping 112 lines ...
Jun 11 00:24:49.236: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-814-e2e-sc7rnj9
STEP: creating a claim
Jun 11 00:24:49.352: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-5f99
STEP: Creating a pod to test subpath
Jun 11 00:24:49.703: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-5f99" in namespace "provisioning-814" to be "Succeeded or Failed"
Jun 11 00:24:49.817: INFO: Pod "pod-subpath-test-dynamicpv-5f99": Phase="Pending", Reason="", readiness=false. Elapsed: 113.688956ms
Jun 11 00:24:51.931: INFO: Pod "pod-subpath-test-dynamicpv-5f99": Phase="Pending", Reason="", readiness=false. Elapsed: 2.227789805s
Jun 11 00:24:54.045: INFO: Pod "pod-subpath-test-dynamicpv-5f99": Phase="Pending", Reason="", readiness=false. Elapsed: 4.34198865s
Jun 11 00:24:56.159: INFO: Pod "pod-subpath-test-dynamicpv-5f99": Phase="Pending", Reason="", readiness=false. Elapsed: 6.456244145s
Jun 11 00:24:58.273: INFO: Pod "pod-subpath-test-dynamicpv-5f99": Phase="Pending", Reason="", readiness=false. Elapsed: 8.570244915s
Jun 11 00:25:00.388: INFO: Pod "pod-subpath-test-dynamicpv-5f99": Phase="Pending", Reason="", readiness=false. Elapsed: 10.684851229s
Jun 11 00:25:02.502: INFO: Pod "pod-subpath-test-dynamicpv-5f99": Phase="Pending", Reason="", readiness=false. Elapsed: 12.79937704s
Jun 11 00:25:04.617: INFO: Pod "pod-subpath-test-dynamicpv-5f99": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.913447132s
STEP: Saw pod success
Jun 11 00:25:04.617: INFO: Pod "pod-subpath-test-dynamicpv-5f99" satisfied condition "Succeeded or Failed"
Jun 11 00:25:04.730: INFO: Trying to get logs from node ip-172-20-47-248.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-5f99 container test-container-volume-dynamicpv-5f99: <nil>
STEP: delete the pod
Jun 11 00:25:04.968: INFO: Waiting for pod pod-subpath-test-dynamicpv-5f99 to disappear
Jun 11 00:25:05.082: INFO: Pod pod-subpath-test-dynamicpv-5f99 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-5f99
Jun 11 00:25:05.082: INFO: Deleting pod "pod-subpath-test-dynamicpv-5f99" in namespace "provisioning-814"
... skipping 362 lines ...
Jun 11 00:25:28.383: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-7951-e2e-sck6fb2
STEP: creating a claim
Jun 11 00:25:28.498: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-44db
STEP: Creating a pod to test exec-volume-test
Jun 11 00:25:28.842: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-44db" in namespace "volume-7951" to be "Succeeded or Failed"
Jun 11 00:25:28.955: INFO: Pod "exec-volume-test-dynamicpv-44db": Phase="Pending", Reason="", readiness=false. Elapsed: 113.039312ms
Jun 11 00:25:31.078: INFO: Pod "exec-volume-test-dynamicpv-44db": Phase="Pending", Reason="", readiness=false. Elapsed: 2.235686749s
Jun 11 00:25:33.191: INFO: Pod "exec-volume-test-dynamicpv-44db": Phase="Pending", Reason="", readiness=false. Elapsed: 4.349358302s
Jun 11 00:25:35.307: INFO: Pod "exec-volume-test-dynamicpv-44db": Phase="Pending", Reason="", readiness=false. Elapsed: 6.464737884s
Jun 11 00:25:37.420: INFO: Pod "exec-volume-test-dynamicpv-44db": Phase="Pending", Reason="", readiness=false. Elapsed: 8.578372838s
Jun 11 00:25:39.543: INFO: Pod "exec-volume-test-dynamicpv-44db": Phase="Pending", Reason="", readiness=false. Elapsed: 10.700613114s
Jun 11 00:25:41.657: INFO: Pod "exec-volume-test-dynamicpv-44db": Phase="Pending", Reason="", readiness=false. Elapsed: 12.814824317s
Jun 11 00:25:43.771: INFO: Pod "exec-volume-test-dynamicpv-44db": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.929314994s
STEP: Saw pod success
Jun 11 00:25:43.771: INFO: Pod "exec-volume-test-dynamicpv-44db" satisfied condition "Succeeded or Failed"
Jun 11 00:25:43.884: INFO: Trying to get logs from node ip-172-20-42-226.eu-west-3.compute.internal pod exec-volume-test-dynamicpv-44db container exec-container-dynamicpv-44db: <nil>
STEP: delete the pod
Jun 11 00:25:44.117: INFO: Waiting for pod exec-volume-test-dynamicpv-44db to disappear
Jun 11 00:25:44.230: INFO: Pod exec-volume-test-dynamicpv-44db no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-44db
Jun 11 00:25:44.230: INFO: Deleting pod "exec-volume-test-dynamicpv-44db" in namespace "volume-7951"
... skipping 266 lines ...
Jun 11 00:25:47.101: INFO: Pod aws-client still exists
Jun 11 00:25:48.986: INFO: Waiting for pod aws-client to disappear
Jun 11 00:25:49.099: INFO: Pod aws-client still exists
Jun 11 00:25:50.987: INFO: Waiting for pod aws-client to disappear
Jun 11 00:25:51.104: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun 11 00:25:51.695: INFO: Couldn't delete PD "aws://eu-west-3a/vol-07a18d40cc646af55", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07a18d40cc646af55 is currently attached to i-00014b5ed56029a5c
	status code: 400, request id: ddac1817-0a8c-4968-9c49-0e65c19658e5
Jun 11 00:25:57.355: INFO: Couldn't delete PD "aws://eu-west-3a/vol-07a18d40cc646af55", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07a18d40cc646af55 is currently attached to i-00014b5ed56029a5c
	status code: 400, request id: aa6b9d9a-7ddf-4c7d-a1e3-d23093b7b686
Jun 11 00:26:02.976: INFO: Successfully deleted PD "aws://eu-west-3a/vol-07a18d40cc646af55".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 00:26:02.976: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-6880" for this suite.
... skipping 45 lines ...
Jun 11 00:25:28.859: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 11 00:25:29.668: INFO: Successfully created a new PD: "aws://eu-west-3a/vol-043c9e42df61bb989".
Jun 11 00:25:29.668: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-jmjw
STEP: Creating a pod to test exec-volume-test
Jun 11 00:25:29.784: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-jmjw" in namespace "volume-5726" to be "Succeeded or Failed"
Jun 11 00:25:29.897: INFO: Pod "exec-volume-test-inlinevolume-jmjw": Phase="Pending", Reason="", readiness=false. Elapsed: 112.77192ms
Jun 11 00:25:32.011: INFO: Pod "exec-volume-test-inlinevolume-jmjw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.226875788s
Jun 11 00:25:34.124: INFO: Pod "exec-volume-test-inlinevolume-jmjw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.339924522s
Jun 11 00:25:36.237: INFO: Pod "exec-volume-test-inlinevolume-jmjw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.452913913s
Jun 11 00:25:38.355: INFO: Pod "exec-volume-test-inlinevolume-jmjw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.571448707s
Jun 11 00:25:40.469: INFO: Pod "exec-volume-test-inlinevolume-jmjw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.685069036s
STEP: Saw pod success
Jun 11 00:25:40.469: INFO: Pod "exec-volume-test-inlinevolume-jmjw" satisfied condition "Succeeded or Failed"
Jun 11 00:25:40.583: INFO: Trying to get logs from node ip-172-20-55-69.eu-west-3.compute.internal pod exec-volume-test-inlinevolume-jmjw container exec-container-inlinevolume-jmjw: <nil>
STEP: delete the pod
Jun 11 00:25:40.816: INFO: Waiting for pod exec-volume-test-inlinevolume-jmjw to disappear
Jun 11 00:25:40.929: INFO: Pod exec-volume-test-inlinevolume-jmjw no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-jmjw
Jun 11 00:25:40.929: INFO: Deleting pod "exec-volume-test-inlinevolume-jmjw" in namespace "volume-5726"
Jun 11 00:25:41.240: INFO: Couldn't delete PD "aws://eu-west-3a/vol-043c9e42df61bb989", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-043c9e42df61bb989 is currently attached to i-0fcdea48570ae258b
	status code: 400, request id: e4dd5137-9a31-4ada-81fb-08385abdbd24
Jun 11 00:25:46.839: INFO: Couldn't delete PD "aws://eu-west-3a/vol-043c9e42df61bb989", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-043c9e42df61bb989 is currently attached to i-0fcdea48570ae258b
	status code: 400, request id: f4ffffb8-3744-403c-a6fd-8ca160cf1d78
Jun 11 00:25:52.437: INFO: Couldn't delete PD "aws://eu-west-3a/vol-043c9e42df61bb989", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-043c9e42df61bb989 is currently attached to i-0fcdea48570ae258b
	status code: 400, request id: d20ab203-a61c-44b9-8ee9-7984a4404856
Jun 11 00:25:58.083: INFO: Couldn't delete PD "aws://eu-west-3a/vol-043c9e42df61bb989", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-043c9e42df61bb989 is currently attached to i-0fcdea48570ae258b
	status code: 400, request id: 97ce2af7-9d94-4289-8123-7f2f648967c4
Jun 11 00:26:03.708: INFO: Successfully deleted PD "aws://eu-west-3a/vol-043c9e42df61bb989".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 00:26:03.708: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-5726" for this suite.
... skipping 163 lines ...
Jun 11 00:25:57.155: INFO: Waiting for pod aws-client to disappear
Jun 11 00:25:57.269: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 11 00:25:57.269: INFO: Deleting PersistentVolumeClaim "pvc-8msk7"
Jun 11 00:25:57.406: INFO: Deleting PersistentVolume "aws-sng2p"
Jun 11 00:25:58.157: INFO: Couldn't delete PD "aws://eu-west-3a/vol-02ec3b0bec36d3278", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02ec3b0bec36d3278 is currently attached to i-048a05b12d63ed4b1
	status code: 400, request id: 80e7cf9d-a022-49f5-bb4c-331752aa8d8f
Jun 11 00:26:03.773: INFO: Couldn't delete PD "aws://eu-west-3a/vol-02ec3b0bec36d3278", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02ec3b0bec36d3278 is currently attached to i-048a05b12d63ed4b1
	status code: 400, request id: c7e2c31e-69cd-4f7a-bea0-be8a5f103d8a
Jun 11 00:26:09.430: INFO: Successfully deleted PD "aws://eu-west-3a/vol-02ec3b0bec36d3278".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 00:26:09.430: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-5957" for this suite.
... skipping 356 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.PCf2odPVy/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.PCf2odPVy/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.PCf2odPVy/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.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 76 lines ...
Jun 11 00:25:26.394: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-5037-e2e-scvdrbp
STEP: creating a claim
Jun 11 00:25:26.508: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-x7gm
STEP: Creating a pod to test exec-volume-test
Jun 11 00:25:26.848: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-x7gm" in namespace "volume-5037" to be "Succeeded or Failed"
Jun 11 00:25:26.960: INFO: Pod "exec-volume-test-dynamicpv-x7gm": Phase="Pending", Reason="", readiness=false. Elapsed: 112.170969ms
Jun 11 00:25:29.072: INFO: Pod "exec-volume-test-dynamicpv-x7gm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.224265604s
Jun 11 00:25:31.188: INFO: Pod "exec-volume-test-dynamicpv-x7gm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.339889327s
Jun 11 00:25:33.305: INFO: Pod "exec-volume-test-dynamicpv-x7gm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.457022988s
Jun 11 00:25:35.419: INFO: Pod "exec-volume-test-dynamicpv-x7gm": Phase="Pending", Reason="", readiness=false. Elapsed: 8.570578285s
Jun 11 00:25:37.532: INFO: Pod "exec-volume-test-dynamicpv-x7gm": Phase="Pending", Reason="", readiness=false. Elapsed: 10.683491425s
Jun 11 00:25:39.644: INFO: Pod "exec-volume-test-dynamicpv-x7gm": Phase="Pending", Reason="", readiness=false. Elapsed: 12.796128758s
Jun 11 00:25:41.758: INFO: Pod "exec-volume-test-dynamicpv-x7gm": Phase="Pending", Reason="", readiness=false. Elapsed: 14.909753076s
Jun 11 00:25:43.872: INFO: Pod "exec-volume-test-dynamicpv-x7gm": Phase="Pending", Reason="", readiness=false. Elapsed: 17.023556671s
Jun 11 00:25:45.984: INFO: Pod "exec-volume-test-dynamicpv-x7gm": Phase="Pending", Reason="", readiness=false. Elapsed: 19.136253721s
Jun 11 00:25:48.097: INFO: Pod "exec-volume-test-dynamicpv-x7gm": Phase="Pending", Reason="", readiness=false. Elapsed: 21.24880315s
Jun 11 00:25:50.209: INFO: Pod "exec-volume-test-dynamicpv-x7gm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.361154521s
STEP: Saw pod success
Jun 11 00:25:50.209: INFO: Pod "exec-volume-test-dynamicpv-x7gm" satisfied condition "Succeeded or Failed"
Jun 11 00:25:50.322: INFO: Trying to get logs from node ip-172-20-47-248.eu-west-3.compute.internal pod exec-volume-test-dynamicpv-x7gm container exec-container-dynamicpv-x7gm: <nil>
STEP: delete the pod
Jun 11 00:25:50.554: INFO: Waiting for pod exec-volume-test-dynamicpv-x7gm to disappear
Jun 11 00:25:50.666: INFO: Pod exec-volume-test-dynamicpv-x7gm no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-x7gm
Jun 11 00:25:50.667: INFO: Deleting pod "exec-volume-test-dynamicpv-x7gm" in namespace "volume-5037"
... skipping 36 lines ...
Jun 11 00:23:03.251: INFO: Creating resource for dynamic PV
Jun 11 00:23:03.251: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-4757-e2e-scz7qjx
STEP: creating a claim
Jun 11 00:23:03.372: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 11 00:23:03.766: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-mq2qt" in namespace "snapshotting-4757" to be "Succeeded or Failed"
Jun 11 00:23:03.880: INFO: Pod "pvc-snapshottable-tester-mq2qt": Phase="Pending", Reason="", readiness=false. Elapsed: 113.478461ms
Jun 11 00:23:05.998: INFO: Pod "pvc-snapshottable-tester-mq2qt": Phase="Pending", Reason="", readiness=false. Elapsed: 2.231524614s
Jun 11 00:23:08.113: INFO: Pod "pvc-snapshottable-tester-mq2qt": Phase="Pending", Reason="", readiness=false. Elapsed: 4.346795516s
Jun 11 00:23:10.228: INFO: Pod "pvc-snapshottable-tester-mq2qt": Phase="Pending", Reason="", readiness=false. Elapsed: 6.4618824s
Jun 11 00:23:12.343: INFO: Pod "pvc-snapshottable-tester-mq2qt": Phase="Pending", Reason="", readiness=false. Elapsed: 8.576783042s
Jun 11 00:23:14.457: INFO: Pod "pvc-snapshottable-tester-mq2qt": Phase="Pending", Reason="", readiness=false. Elapsed: 10.69097078s
Jun 11 00:23:16.572: INFO: Pod "pvc-snapshottable-tester-mq2qt": Phase="Pending", Reason="", readiness=false. Elapsed: 12.806137862s
Jun 11 00:23:18.688: INFO: Pod "pvc-snapshottable-tester-mq2qt": Phase="Pending", Reason="", readiness=false. Elapsed: 14.921692016s
Jun 11 00:23:20.803: INFO: Pod "pvc-snapshottable-tester-mq2qt": Phase="Pending", Reason="", readiness=false. Elapsed: 17.036218233s
Jun 11 00:23:22.917: INFO: Pod "pvc-snapshottable-tester-mq2qt": Phase="Pending", Reason="", readiness=false. Elapsed: 19.150295066s
Jun 11 00:23:25.032: INFO: Pod "pvc-snapshottable-tester-mq2qt": Phase="Running", Reason="", readiness=true. Elapsed: 21.265267919s
Jun 11 00:23:27.146: INFO: Pod "pvc-snapshottable-tester-mq2qt": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.380090971s
STEP: Saw pod success
Jun 11 00:23:27.146: INFO: Pod "pvc-snapshottable-tester-mq2qt" satisfied condition "Succeeded or Failed"
Jun 11 00:23:27.387: INFO: Pod pvc-snapshottable-tester-mq2qt has the following logs: 
Jun 11 00:23:27.388: INFO: Deleting pod "pvc-snapshottable-tester-mq2qt" in namespace "snapshotting-4757"
Jun 11 00:23:27.508: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-mq2qt" to be fully deleted
Jun 11 00:23:27.622: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.com9c4fl] to have phase Bound
Jun 11 00:23:27.735: INFO: PersistentVolumeClaim ebs.csi.aws.com9c4fl found and phase=Bound (113.706803ms)
STEP: [init] checking the claim
... skipping 50 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.PCf2odPVy/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 11 00:24:16.742: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-4w7s8" in namespace "snapshotting-4757" to be "Succeeded or Failed"
Jun 11 00:24:16.856: INFO: Pod "pvc-snapshottable-data-tester-4w7s8": Phase="Pending", Reason="", readiness=false. Elapsed: 113.678475ms
Jun 11 00:24:18.971: INFO: Pod "pvc-snapshottable-data-tester-4w7s8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.228600869s
Jun 11 00:24:21.085: INFO: Pod "pvc-snapshottable-data-tester-4w7s8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.343197974s
Jun 11 00:24:23.200: INFO: Pod "pvc-snapshottable-data-tester-4w7s8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.457990592s
Jun 11 00:24:25.317: INFO: Pod "pvc-snapshottable-data-tester-4w7s8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.574754063s
Jun 11 00:24:27.434: INFO: Pod "pvc-snapshottable-data-tester-4w7s8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.692218321s
STEP: Saw pod success
Jun 11 00:24:27.434: INFO: Pod "pvc-snapshottable-data-tester-4w7s8" satisfied condition "Succeeded or Failed"
Jun 11 00:24:27.663: INFO: Pod pvc-snapshottable-data-tester-4w7s8 has the following logs: 
Jun 11 00:24:27.663: INFO: Deleting pod "pvc-snapshottable-data-tester-4w7s8" in namespace "snapshotting-4757"
Jun 11 00:24:27.783: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-4w7s8" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 11 00:25:06.357: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-4757 exec restored-pvc-tester-cdjf7 --namespace=snapshotting-4757 -- cat /mnt/test/data'
... skipping 30 lines ...
Jun 11 00:25:31.429: INFO: volumesnapshotcontents pre-provisioned-snapcontent-68bf491e-0cbd-417f-a0c6-a757798eddfa has been found and is not deleted
Jun 11 00:25:32.543: INFO: volumesnapshotcontents pre-provisioned-snapcontent-68bf491e-0cbd-417f-a0c6-a757798eddfa has been found and is not deleted
Jun 11 00:25:33.659: INFO: volumesnapshotcontents pre-provisioned-snapcontent-68bf491e-0cbd-417f-a0c6-a757798eddfa has been found and is not deleted
Jun 11 00:25:34.774: INFO: volumesnapshotcontents pre-provisioned-snapcontent-68bf491e-0cbd-417f-a0c6-a757798eddfa has been found and is not deleted
Jun 11 00:25:35.889: INFO: volumesnapshotcontents pre-provisioned-snapcontent-68bf491e-0cbd-417f-a0c6-a757798eddfa has been found and is not deleted
Jun 11 00:25:37.004: INFO: volumesnapshotcontents pre-provisioned-snapcontent-68bf491e-0cbd-417f-a0c6-a757798eddfa has been found and is not deleted
Jun 11 00:25:38.004: INFO: WaitUntil failed after reaching the timeout 30s
[AfterEach] volume snapshot controller
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:221
Jun 11 00:25:38.121: INFO: Pod restored-pvc-tester-cdjf7 has the following logs: 
Jun 11 00:25:38.121: INFO: Deleting pod "restored-pvc-tester-cdjf7" in namespace "snapshotting-4757"
Jun 11 00:25:38.247: INFO: Wait up to 5m0s for pod "restored-pvc-tester-cdjf7" to be fully deleted
Jun 11 00:26:18.483: INFO: deleting claim "snapshotting-4757"/"pvc-dsshv"
... skipping 414 lines ...
Jun 11 00:26:03.403: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-7788-e2e-schng6r
STEP: creating a claim
Jun 11 00:26:03.519: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Jun 11 00:26:03.746: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 11 00:26:03.973: INFO: Error updating pvc ebs.csi.aws.compcnqh: PersistentVolumeClaim "ebs.csi.aws.compcnqh" is invalid: spec: Forbidden: spec is 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-7788-e2e-schng6r",
  	... // 2 identical fields
  }

Jun 11 00:26:06.200: INFO: Error updating pvc ebs.csi.aws.compcnqh: PersistentVolumeClaim "ebs.csi.aws.compcnqh" is invalid: spec: Forbidden: spec is 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-7788-e2e-schng6r",
  	... // 2 identical fields
  }

Jun 11 00:26:08.200: INFO: Error updating pvc ebs.csi.aws.compcnqh: PersistentVolumeClaim "ebs.csi.aws.compcnqh" is invalid: spec: Forbidden: spec is 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-7788-e2e-schng6r",
  	... // 2 identical fields
  }

Jun 11 00:26:10.199: INFO: Error updating pvc ebs.csi.aws.compcnqh: PersistentVolumeClaim "ebs.csi.aws.compcnqh" is invalid: spec: Forbidden: spec is 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-7788-e2e-schng6r",
  	... // 2 identical fields
  }

Jun 11 00:26:12.201: INFO: Error updating pvc ebs.csi.aws.compcnqh: PersistentVolumeClaim "ebs.csi.aws.compcnqh" is invalid: spec: Forbidden: spec is 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-7788-e2e-schng6r",
  	... // 2 identical fields
  }

Jun 11 00:26:14.200: INFO: Error updating pvc ebs.csi.aws.compcnqh: PersistentVolumeClaim "ebs.csi.aws.compcnqh" is invalid: spec: Forbidden: spec is 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-7788-e2e-schng6r",
  	... // 2 identical fields
  }

Jun 11 00:26:16.201: INFO: Error updating pvc ebs.csi.aws.compcnqh: PersistentVolumeClaim "ebs.csi.aws.compcnqh" is invalid: spec: Forbidden: spec is 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-7788-e2e-schng6r",
  	... // 2 identical fields
  }

Jun 11 00:26:18.207: INFO: Error updating pvc ebs.csi.aws.compcnqh: PersistentVolumeClaim "ebs.csi.aws.compcnqh" is invalid: spec: Forbidden: spec is 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-7788-e2e-schng6r",
  	... // 2 identical fields
  }

Jun 11 00:26:20.208: INFO: Error updating pvc ebs.csi.aws.compcnqh: PersistentVolumeClaim "ebs.csi.aws.compcnqh" is invalid: spec: Forbidden: spec is 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-7788-e2e-schng6r",
  	... // 2 identical fields
  }

Jun 11 00:26:22.201: INFO: Error updating pvc ebs.csi.aws.compcnqh: PersistentVolumeClaim "ebs.csi.aws.compcnqh" is invalid: spec: Forbidden: spec is 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-7788-e2e-schng6r",
  	... // 2 identical fields
  }

Jun 11 00:26:24.204: INFO: Error updating pvc ebs.csi.aws.compcnqh: PersistentVolumeClaim "ebs.csi.aws.compcnqh" is invalid: spec: Forbidden: spec is 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-7788-e2e-schng6r",
  	... // 2 identical fields
  }

Jun 11 00:26:26.202: INFO: Error updating pvc ebs.csi.aws.compcnqh: PersistentVolumeClaim "ebs.csi.aws.compcnqh" is invalid: spec: Forbidden: spec is 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-7788-e2e-schng6r",
  	... // 2 identical fields
  }

Jun 11 00:26:28.199: INFO: Error updating pvc ebs.csi.aws.compcnqh: PersistentVolumeClaim "ebs.csi.aws.compcnqh" is invalid: spec: Forbidden: spec is 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-7788-e2e-schng6r",
  	... // 2 identical fields
  }

Jun 11 00:26:30.203: INFO: Error updating pvc ebs.csi.aws.compcnqh: PersistentVolumeClaim "ebs.csi.aws.compcnqh" is invalid: spec: Forbidden: spec is 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-7788-e2e-schng6r",
  	... // 2 identical fields
  }

Jun 11 00:26:32.199: INFO: Error updating pvc ebs.csi.aws.compcnqh: PersistentVolumeClaim "ebs.csi.aws.compcnqh" is invalid: spec: Forbidden: spec is 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-7788-e2e-schng6r",
  	... // 2 identical fields
  }

Jun 11 00:26:34.203: INFO: Error updating pvc ebs.csi.aws.compcnqh: PersistentVolumeClaim "ebs.csi.aws.compcnqh" is invalid: spec: Forbidden: spec is 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-7788-e2e-schng6r",
  	... // 2 identical fields
  }

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.PCf2odPVy/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.PCf2odPVy/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.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 87 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 00:26:21.959: 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.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 11 00:26:22.527: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 11 00:26:23.270: INFO: Successfully created a new PD: "aws://eu-west-3a/vol-02b05c58b544ab83e".
Jun 11 00:26:23.270: INFO: Creating resource for pre-provisioned PV
Jun 11 00:26:23.270: INFO: Creating PVC and PV
... skipping 5 lines ...
Jun 11 00:26:27.905: INFO: PersistentVolumeClaim pvc-cmxl2 found but phase is Pending instead of Bound.
Jun 11 00:26:30.019: INFO: PersistentVolumeClaim pvc-cmxl2 found but phase is Pending instead of Bound.
Jun 11 00:26:32.132: INFO: PersistentVolumeClaim pvc-cmxl2 found and phase=Bound (8.568744438s)
Jun 11 00:26:32.132: INFO: Waiting up to 3m0s for PersistentVolume aws-svwv2 to have phase Bound
Jun 11 00:26:32.245: INFO: PersistentVolume aws-svwv2 found and phase=Bound (112.684229ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 11 00:26:34.933: INFO: Deleting pod "pod-9532c017-f6a2-4a53-901b-d23313b50e18" in namespace "volumemode-6928"
Jun 11 00:26:35.049: INFO: Wait up to 5m0s for pod "pod-9532c017-f6a2-4a53-901b-d23313b50e18" to be fully deleted
STEP: Deleting pv and pvc
Jun 11 00:26:41.276: INFO: Deleting PersistentVolumeClaim "pvc-cmxl2"
Jun 11 00:26:41.391: INFO: Deleting PersistentVolume "aws-svwv2"
Jun 11 00:26:41.732: INFO: Successfully deleted PD "aws://eu-west-3a/vol-02b05c58b544ab83e".
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.PCf2odPVy/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.PCf2odPVy/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
    /tmp/kops.PCf2odPVy/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.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 11 00:26:41.963: INFO: Distro debian doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
... skipping 106 lines ...
Jun 11 00:26:04.510: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8788m6jrn
STEP: creating a claim
Jun 11 00:26:04.624: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-p4pt
STEP: Creating a pod to test multi_subpath
Jun 11 00:26:04.966: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-p4pt" in namespace "provisioning-8788" to be "Succeeded or Failed"
Jun 11 00:26:05.080: INFO: Pod "pod-subpath-test-dynamicpv-p4pt": Phase="Pending", Reason="", readiness=false. Elapsed: 112.997597ms
Jun 11 00:26:07.197: INFO: Pod "pod-subpath-test-dynamicpv-p4pt": Phase="Pending", Reason="", readiness=false. Elapsed: 2.23020532s
Jun 11 00:26:09.310: INFO: Pod "pod-subpath-test-dynamicpv-p4pt": Phase="Pending", Reason="", readiness=false. Elapsed: 4.343106304s
Jun 11 00:26:11.423: INFO: Pod "pod-subpath-test-dynamicpv-p4pt": Phase="Pending", Reason="", readiness=false. Elapsed: 6.456762067s
Jun 11 00:26:13.539: INFO: Pod "pod-subpath-test-dynamicpv-p4pt": Phase="Pending", Reason="", readiness=false. Elapsed: 8.572303097s
Jun 11 00:26:15.657: INFO: Pod "pod-subpath-test-dynamicpv-p4pt": Phase="Pending", Reason="", readiness=false. Elapsed: 10.690029754s
Jun 11 00:26:17.770: INFO: Pod "pod-subpath-test-dynamicpv-p4pt": Phase="Pending", Reason="", readiness=false. Elapsed: 12.803249375s
Jun 11 00:26:19.884: INFO: Pod "pod-subpath-test-dynamicpv-p4pt": Phase="Pending", Reason="", readiness=false. Elapsed: 14.917598861s
Jun 11 00:26:21.999: INFO: Pod "pod-subpath-test-dynamicpv-p4pt": Phase="Succeeded", Reason="", readiness=false. Elapsed: 17.032564138s
STEP: Saw pod success
Jun 11 00:26:21.999: INFO: Pod "pod-subpath-test-dynamicpv-p4pt" satisfied condition "Succeeded or Failed"
Jun 11 00:26:22.112: INFO: Trying to get logs from node ip-172-20-45-141.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-p4pt container test-container-subpath-dynamicpv-p4pt: <nil>
STEP: delete the pod
Jun 11 00:26:22.351: INFO: Waiting for pod pod-subpath-test-dynamicpv-p4pt to disappear
Jun 11 00:26:22.463: INFO: Pod pod-subpath-test-dynamicpv-p4pt no longer exists
STEP: Deleting pod
Jun 11 00:26:22.463: INFO: Deleting pod "pod-subpath-test-dynamicpv-p4pt" in namespace "provisioning-8788"
... skipping 31 lines ...

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

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

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

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

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 2 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 00:26:19.842: 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.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 11 00:26:20.414: INFO: Creating resource for dynamic PV
Jun 11 00:26:20.414: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-9946-e2e-sct9cc7
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 11 00:26:27.220: INFO: Deleting pod "pod-33c1f5c4-890d-4211-93de-9f5ee85d5227" in namespace "volumemode-9946"
Jun 11 00:26:27.337: INFO: Wait up to 5m0s for pod "pod-33c1f5c4-890d-4211-93de-9f5ee85d5227" to be fully deleted
STEP: Deleting pvc
Jun 11 00:26:39.795: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.commvhdr"
Jun 11 00:26:39.917: INFO: Waiting up to 5m0s for PersistentVolume pvc-0eec024c-4627-4bce-a368-4ed9fc3e9763 to get deleted
Jun 11 00:26:40.032: INFO: PersistentVolume pvc-0eec024c-4627-4bce-a368-4ed9fc3e9763 found and phase=Released (114.70544ms)
... skipping 7 lines ...

• [SLOW TEST:25.655 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.PCf2odPVy/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.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
SS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 00:26:00.492: 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.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 11 00:26:01.058: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 11 00:26:01.750: INFO: Successfully created a new PD: "aws://eu-west-3a/vol-0234171418243df43".
Jun 11 00:26:01.750: INFO: Creating resource for pre-provisioned PV
Jun 11 00:26:01.750: INFO: Creating PVC and PV
... skipping 9 lines ...
Jun 11 00:26:14.863: INFO: PersistentVolumeClaim pvc-wjbdl found but phase is Pending instead of Bound.
Jun 11 00:26:16.978: INFO: PersistentVolumeClaim pvc-wjbdl found but phase is Pending instead of Bound.
Jun 11 00:26:19.091: INFO: PersistentVolumeClaim pvc-wjbdl found and phase=Bound (17.027188405s)
Jun 11 00:26:19.091: INFO: Waiting up to 3m0s for PersistentVolume aws-q55jc to have phase Bound
Jun 11 00:26:19.204: INFO: PersistentVolume aws-q55jc found and phase=Bound (113.07505ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 11 00:26:21.885: INFO: Deleting pod "pod-0620f296-3b75-42b4-aad7-2c9e7ff86727" in namespace "volumemode-1771"
Jun 11 00:26:22.001: INFO: Wait up to 5m0s for pod "pod-0620f296-3b75-42b4-aad7-2c9e7ff86727" to be fully deleted
STEP: Deleting pv and pvc
Jun 11 00:26:28.227: INFO: Deleting PersistentVolumeClaim "pvc-wjbdl"
Jun 11 00:26:28.341: INFO: Deleting PersistentVolume "aws-q55jc"
Jun 11 00:26:28.679: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0234171418243df43", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0234171418243df43 is currently attached to i-048a05b12d63ed4b1
	status code: 400, request id: cb51d7ab-8a66-4aaf-baae-44f51b6a6406
Jun 11 00:26:34.270: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0234171418243df43", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0234171418243df43 is currently attached to i-048a05b12d63ed4b1
	status code: 400, request id: 9e4af78f-9c76-4d60-aac7-207b59bda129
Jun 11 00:26:39.856: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0234171418243df43", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0234171418243df43 is currently attached to i-048a05b12d63ed4b1
	status code: 400, request id: 78f17b10-048d-459d-96b0-1f13df1c80e1
Jun 11 00:26:45.471: INFO: Successfully deleted PD "aws://eu-west-3a/vol-0234171418243df43".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 00:26:45.471: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-1771" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.PCf2odPVy/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.PCf2odPVy/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
    /tmp/kops.PCf2odPVy/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.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 11 00:26:45.708: INFO: Driver supports dynamic provisioning, skipping PreprovisionedPV pattern
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
... skipping 52 lines ...
Jun 11 00:24:16.815: INFO: Creating resource for dynamic PV
Jun 11 00:24:16.816: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-3104-e2e-sc7xxj9
STEP: creating a claim
Jun 11 00:24:16.929: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 11 00:24:17.274: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-jd65r" in namespace "snapshotting-3104" to be "Succeeded or Failed"
Jun 11 00:24:17.386: INFO: Pod "pvc-snapshottable-tester-jd65r": Phase="Pending", Reason="", readiness=false. Elapsed: 112.506812ms
Jun 11 00:24:19.500: INFO: Pod "pvc-snapshottable-tester-jd65r": Phase="Pending", Reason="", readiness=false. Elapsed: 2.226097286s
Jun 11 00:24:21.630: INFO: Pod "pvc-snapshottable-tester-jd65r": Phase="Pending", Reason="", readiness=false. Elapsed: 4.356240041s
Jun 11 00:24:23.747: INFO: Pod "pvc-snapshottable-tester-jd65r": Phase="Pending", Reason="", readiness=false. Elapsed: 6.47348667s
Jun 11 00:24:25.860: INFO: Pod "pvc-snapshottable-tester-jd65r": Phase="Pending", Reason="", readiness=false. Elapsed: 8.586778348s
Jun 11 00:24:27.974: INFO: Pod "pvc-snapshottable-tester-jd65r": Phase="Pending", Reason="", readiness=false. Elapsed: 10.699983192s
Jun 11 00:24:30.088: INFO: Pod "pvc-snapshottable-tester-jd65r": Phase="Pending", Reason="", readiness=false. Elapsed: 12.814299733s
Jun 11 00:24:32.202: INFO: Pod "pvc-snapshottable-tester-jd65r": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.927911521s
STEP: Saw pod success
Jun 11 00:24:32.202: INFO: Pod "pvc-snapshottable-tester-jd65r" satisfied condition "Succeeded or Failed"
Jun 11 00:24:32.429: INFO: Pod pvc-snapshottable-tester-jd65r has the following logs: 
Jun 11 00:24:32.429: INFO: Deleting pod "pvc-snapshottable-tester-jd65r" in namespace "snapshotting-3104"
Jun 11 00:24:32.548: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-jd65r" to be fully deleted
Jun 11 00:24:32.661: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comrsw28] to have phase Bound
Jun 11 00:24:32.773: INFO: PersistentVolumeClaim ebs.csi.aws.comrsw28 found and phase=Bound (112.670179ms)
STEP: [init] checking the claim
... skipping 55 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.PCf2odPVy/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 11 00:25:32.263: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-78zhj" in namespace "snapshotting-3104" to be "Succeeded or Failed"
Jun 11 00:25:32.379: INFO: Pod "pvc-snapshottable-data-tester-78zhj": Phase="Pending", Reason="", readiness=false. Elapsed: 115.846962ms
Jun 11 00:25:34.492: INFO: Pod "pvc-snapshottable-data-tester-78zhj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.229260548s
Jun 11 00:25:36.604: INFO: Pod "pvc-snapshottable-data-tester-78zhj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.341314498s
Jun 11 00:25:38.718: INFO: Pod "pvc-snapshottable-data-tester-78zhj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.454695224s
Jun 11 00:25:40.830: INFO: Pod "pvc-snapshottable-data-tester-78zhj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.567292787s
Jun 11 00:25:42.944: INFO: Pod "pvc-snapshottable-data-tester-78zhj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.681129249s
STEP: Saw pod success
Jun 11 00:25:42.944: INFO: Pod "pvc-snapshottable-data-tester-78zhj" satisfied condition "Succeeded or Failed"
Jun 11 00:25:43.177: INFO: Pod pvc-snapshottable-data-tester-78zhj has the following logs: 
Jun 11 00:25:43.177: INFO: Deleting pod "pvc-snapshottable-data-tester-78zhj" in namespace "snapshotting-3104"
Jun 11 00:25:43.294: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-78zhj" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 11 00:25:57.866: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-3104 exec restored-pvc-tester-lz4p8 --namespace=snapshotting-3104 -- cat /mnt/test/data'
... skipping 228 lines ...
Jun 11 00:25:38.579: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-22559q8v2
STEP: creating a claim
Jun 11 00:25:38.694: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-w84n
STEP: Creating a pod to test atomic-volume-subpath
Jun 11 00:25:39.039: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-w84n" in namespace "provisioning-2255" to be "Succeeded or Failed"
Jun 11 00:25:39.152: INFO: Pod "pod-subpath-test-dynamicpv-w84n": Phase="Pending", Reason="", readiness=false. Elapsed: 112.937369ms
Jun 11 00:25:41.266: INFO: Pod "pod-subpath-test-dynamicpv-w84n": Phase="Pending", Reason="", readiness=false. Elapsed: 2.226794487s
Jun 11 00:25:43.380: INFO: Pod "pod-subpath-test-dynamicpv-w84n": Phase="Pending", Reason="", readiness=false. Elapsed: 4.340559962s
Jun 11 00:25:45.497: INFO: Pod "pod-subpath-test-dynamicpv-w84n": Phase="Pending", Reason="", readiness=false. Elapsed: 6.457632846s
Jun 11 00:25:47.610: INFO: Pod "pod-subpath-test-dynamicpv-w84n": Phase="Pending", Reason="", readiness=false. Elapsed: 8.571254485s
Jun 11 00:25:49.725: INFO: Pod "pod-subpath-test-dynamicpv-w84n": Phase="Pending", Reason="", readiness=false. Elapsed: 10.685670908s
... skipping 11 lines ...
Jun 11 00:26:15.101: INFO: Pod "pod-subpath-test-dynamicpv-w84n": Phase="Running", Reason="", readiness=true. Elapsed: 36.061805956s
Jun 11 00:26:17.214: INFO: Pod "pod-subpath-test-dynamicpv-w84n": Phase="Running", Reason="", readiness=true. Elapsed: 38.17526622s
Jun 11 00:26:19.330: INFO: Pod "pod-subpath-test-dynamicpv-w84n": Phase="Running", Reason="", readiness=true. Elapsed: 40.29122286s
Jun 11 00:26:21.446: INFO: Pod "pod-subpath-test-dynamicpv-w84n": Phase="Running", Reason="", readiness=true. Elapsed: 42.406534974s
Jun 11 00:26:23.561: INFO: Pod "pod-subpath-test-dynamicpv-w84n": Phase="Succeeded", Reason="", readiness=false. Elapsed: 44.521838043s
STEP: Saw pod success
Jun 11 00:26:23.561: INFO: Pod "pod-subpath-test-dynamicpv-w84n" satisfied condition "Succeeded or Failed"
Jun 11 00:26:23.674: INFO: Trying to get logs from node ip-172-20-42-226.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-w84n container test-container-subpath-dynamicpv-w84n: <nil>
STEP: delete the pod
Jun 11 00:26:23.916: INFO: Waiting for pod pod-subpath-test-dynamicpv-w84n to disappear
Jun 11 00:26:24.031: INFO: Pod pod-subpath-test-dynamicpv-w84n no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-w84n
Jun 11 00:26:24.031: INFO: Deleting pod "pod-subpath-test-dynamicpv-w84n" in namespace "provisioning-2255"
... skipping 133 lines ...
Jun 11 00:26:44.455: INFO: Pod aws-client still exists
Jun 11 00:26:46.342: INFO: Waiting for pod aws-client to disappear
Jun 11 00:26:46.456: INFO: Pod aws-client still exists
Jun 11 00:26:48.343: INFO: Waiting for pod aws-client to disappear
Jun 11 00:26:48.457: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun 11 00:26:49.066: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0ef96babec26b11f2", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ef96babec26b11f2 is currently attached to i-0690821a57784e40a
	status code: 400, request id: 8fbaf74e-a308-4412-a158-8bde8c6b7978
Jun 11 00:26:54.690: INFO: Successfully deleted PD "aws://eu-west-3a/vol-0ef96babec26b11f2".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 00:26:54.691: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-7086" for this suite.
... skipping 128 lines ...
Jun 11 00:26:11.836: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6014-e2e-scshfxt
STEP: creating a claim
Jun 11 00:26:11.950: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-swck
STEP: Creating a pod to test subpath
Jun 11 00:26:12.298: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-swck" in namespace "provisioning-6014" to be "Succeeded or Failed"
Jun 11 00:26:12.412: INFO: Pod "pod-subpath-test-dynamicpv-swck": Phase="Pending", Reason="", readiness=false. Elapsed: 114.647239ms
Jun 11 00:26:14.529: INFO: Pod "pod-subpath-test-dynamicpv-swck": Phase="Pending", Reason="", readiness=false. Elapsed: 2.230852607s
Jun 11 00:26:16.644: INFO: Pod "pod-subpath-test-dynamicpv-swck": Phase="Pending", Reason="", readiness=false. Elapsed: 4.346218778s
Jun 11 00:26:18.758: INFO: Pod "pod-subpath-test-dynamicpv-swck": Phase="Pending", Reason="", readiness=false. Elapsed: 6.460440211s
Jun 11 00:26:20.873: INFO: Pod "pod-subpath-test-dynamicpv-swck": Phase="Pending", Reason="", readiness=false. Elapsed: 8.575225713s
Jun 11 00:26:22.987: INFO: Pod "pod-subpath-test-dynamicpv-swck": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.68957391s
STEP: Saw pod success
Jun 11 00:26:22.987: INFO: Pod "pod-subpath-test-dynamicpv-swck" satisfied condition "Succeeded or Failed"
Jun 11 00:26:23.101: INFO: Trying to get logs from node ip-172-20-42-226.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-swck container test-container-subpath-dynamicpv-swck: <nil>
STEP: delete the pod
Jun 11 00:26:23.340: INFO: Waiting for pod pod-subpath-test-dynamicpv-swck to disappear
Jun 11 00:26:23.455: INFO: Pod pod-subpath-test-dynamicpv-swck no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-swck
Jun 11 00:26:23.455: INFO: Deleting pod "pod-subpath-test-dynamicpv-swck" in namespace "provisioning-6014"
... skipping 211 lines ...
Jun 11 00:25:02.356: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-3078vcvq4      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-3078    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-3078vcvq4,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-3078    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-3078vcvq4,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-3078    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-3078vcvq4,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-3078vcvq4    2a968064-12e7-4168-83ad-adab06005c41 7656 0 2021-06-11 00:25:02 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-11 00:25:02 +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-5c9kx pvc- provisioning-3078  381e4700-363a-4393-ba08-229b398c9b9f 7658 0 2021-06-11 00:25:02 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-11 00:25:02 +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-3078vcvq4,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-28d7c277-6675-4854-bcf5-f70b470da829 in namespace provisioning-3078
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun 11 00:25:17.610: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-jpw5j" in namespace "provisioning-3078" to be "Succeeded or Failed"
Jun 11 00:25:17.724: INFO: Pod "pvc-volume-tester-writer-jpw5j": Phase="Pending", Reason="", readiness=false. Elapsed: 113.815647ms
Jun 11 00:25:19.837: INFO: Pod "pvc-volume-tester-writer-jpw5j": Phase="Pending", Reason="", readiness=false. Elapsed: 2.226765991s
Jun 11 00:25:21.951: INFO: Pod "pvc-volume-tester-writer-jpw5j": Phase="Pending", Reason="", readiness=false. Elapsed: 4.340416392s
Jun 11 00:25:24.064: INFO: Pod "pvc-volume-tester-writer-jpw5j": Phase="Pending", Reason="", readiness=false. Elapsed: 6.453724606s
Jun 11 00:25:26.178: INFO: Pod "pvc-volume-tester-writer-jpw5j": Phase="Pending", Reason="", readiness=false. Elapsed: 8.567799619s
Jun 11 00:25:28.292: INFO: Pod "pvc-volume-tester-writer-jpw5j": Phase="Pending", Reason="", readiness=false. Elapsed: 10.681232401s
... skipping 22 lines ...
Jun 11 00:26:16.958: INFO: Pod "pvc-volume-tester-writer-jpw5j": Phase="Pending", Reason="", readiness=false. Elapsed: 59.347805035s
Jun 11 00:26:19.074: INFO: Pod "pvc-volume-tester-writer-jpw5j": Phase="Pending", Reason="", readiness=false. Elapsed: 1m1.463697689s
Jun 11 00:26:21.188: INFO: Pod "pvc-volume-tester-writer-jpw5j": Phase="Pending", Reason="", readiness=false. Elapsed: 1m3.577460642s
Jun 11 00:26:23.302: INFO: Pod "pvc-volume-tester-writer-jpw5j": Phase="Pending", Reason="", readiness=false. Elapsed: 1m5.69179095s
Jun 11 00:26:25.416: INFO: Pod "pvc-volume-tester-writer-jpw5j": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m7.806030406s
STEP: Saw pod success
Jun 11 00:26:25.416: INFO: Pod "pvc-volume-tester-writer-jpw5j" satisfied condition "Succeeded or Failed"
Jun 11 00:26:25.648: INFO: Pod pvc-volume-tester-writer-jpw5j has the following logs: 
Jun 11 00:26:25.648: INFO: Deleting pod "pvc-volume-tester-writer-jpw5j" in namespace "provisioning-3078"
Jun 11 00:26:25.765: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-jpw5j" 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-47-248.eu-west-3.compute.internal"
Jun 11 00:26:26.220: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-vmh4w" in namespace "provisioning-3078" to be "Succeeded or Failed"
Jun 11 00:26:26.333: INFO: Pod "pvc-volume-tester-reader-vmh4w": Phase="Pending", Reason="", readiness=false. Elapsed: 112.705034ms
Jun 11 00:26:28.448: INFO: Pod "pvc-volume-tester-reader-vmh4w": Phase="Pending", Reason="", readiness=false. Elapsed: 2.227402132s
Jun 11 00:26:30.562: INFO: Pod "pvc-volume-tester-reader-vmh4w": Phase="Pending", Reason="", readiness=false. Elapsed: 4.341607763s
Jun 11 00:26:32.676: INFO: Pod "pvc-volume-tester-reader-vmh4w": Phase="Pending", Reason="", readiness=false. Elapsed: 6.455741704s
Jun 11 00:26:34.791: INFO: Pod "pvc-volume-tester-reader-vmh4w": Phase="Pending", Reason="", readiness=false. Elapsed: 8.570546166s
Jun 11 00:26:36.905: INFO: Pod "pvc-volume-tester-reader-vmh4w": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.684377043s
STEP: Saw pod success
Jun 11 00:26:36.905: INFO: Pod "pvc-volume-tester-reader-vmh4w" satisfied condition "Succeeded or Failed"
Jun 11 00:26:37.132: INFO: Pod pvc-volume-tester-reader-vmh4w has the following logs: hello world

Jun 11 00:26:37.132: INFO: Deleting pod "pvc-volume-tester-reader-vmh4w" in namespace "provisioning-3078"
Jun 11 00:26:37.250: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-vmh4w" to be fully deleted
Jun 11 00:26:37.363: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-5c9kx] to have phase Bound
Jun 11 00:26:37.476: INFO: PersistentVolumeClaim pvc-5c9kx found and phase=Bound (112.699768ms)
... skipping 388 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.PCf2odPVy/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.PCf2odPVy/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.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 2 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 00:27:01.132: 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.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 11 00:27:01.707: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 11 00:27:01.707: INFO: Creating resource for dynamic PV
Jun 11 00:27:01.707: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-454z5l2l
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 11 00:27:06.508: INFO: Deleting pod "pod-b6013764-47f9-4be0-b71c-9eb7628007ad" in namespace "volumemode-454"
Jun 11 00:27:06.625: INFO: Wait up to 5m0s for pod "pod-b6013764-47f9-4be0-b71c-9eb7628007ad" to be fully deleted
STEP: Deleting pvc
Jun 11 00:27:17.080: INFO: Deleting PersistentVolumeClaim "awsggm9j"
Jun 11 00:27:17.201: INFO: Waiting up to 5m0s for PersistentVolume pvc-921166a4-6ad8-4efb-8bba-15680e514568 to get deleted
Jun 11 00:27:17.315: INFO: PersistentVolume pvc-921166a4-6ad8-4efb-8bba-15680e514568 found and phase=Released (113.59531ms)
... skipping 9 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.PCf2odPVy/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.PCf2odPVy/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (block volmode)] volumeMode
    /tmp/kops.PCf2odPVy/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.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [sig-storage] Zone Support [Feature:vsphere]
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 00:27:22.775: INFO: >>> kubeConfig: /root/.kube/config
... skipping 75 lines ...
Jun 11 00:27:03.778: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-14967949r
STEP: creating a claim
Jun 11 00:27:03.893: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-ndp8
STEP: Creating a pod to test exec-volume-test
Jun 11 00:27:04.238: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-ndp8" in namespace "volume-1496" to be "Succeeded or Failed"
Jun 11 00:27:04.352: INFO: Pod "exec-volume-test-dynamicpv-ndp8": Phase="Pending", Reason="", readiness=false. Elapsed: 114.001323ms
Jun 11 00:27:06.468: INFO: Pod "exec-volume-test-dynamicpv-ndp8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.229195047s
Jun 11 00:27:08.582: INFO: Pod "exec-volume-test-dynamicpv-ndp8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.343792096s
Jun 11 00:27:10.708: INFO: Pod "exec-volume-test-dynamicpv-ndp8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.469542558s
Jun 11 00:27:12.824: INFO: Pod "exec-volume-test-dynamicpv-ndp8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.585518651s
Jun 11 00:27:14.941: INFO: Pod "exec-volume-test-dynamicpv-ndp8": Phase="Pending", Reason="", readiness=false. Elapsed: 10.702741641s
Jun 11 00:27:17.056: INFO: Pod "exec-volume-test-dynamicpv-ndp8": Phase="Pending", Reason="", readiness=false. Elapsed: 12.817375217s
Jun 11 00:27:19.170: INFO: Pod "exec-volume-test-dynamicpv-ndp8": Phase="Pending", Reason="", readiness=false. Elapsed: 14.931878965s
Jun 11 00:27:21.288: INFO: Pod "exec-volume-test-dynamicpv-ndp8": Phase="Pending", Reason="", readiness=false. Elapsed: 17.049593217s
Jun 11 00:27:23.409: INFO: Pod "exec-volume-test-dynamicpv-ndp8": Phase="Pending", Reason="", readiness=false. Elapsed: 19.17043189s
Jun 11 00:27:25.528: INFO: Pod "exec-volume-test-dynamicpv-ndp8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.289287544s
STEP: Saw pod success
Jun 11 00:27:25.528: INFO: Pod "exec-volume-test-dynamicpv-ndp8" satisfied condition "Succeeded or Failed"
Jun 11 00:27:25.642: INFO: Trying to get logs from node ip-172-20-55-69.eu-west-3.compute.internal pod exec-volume-test-dynamicpv-ndp8 container exec-container-dynamicpv-ndp8: <nil>
STEP: delete the pod
Jun 11 00:27:25.881: INFO: Waiting for pod exec-volume-test-dynamicpv-ndp8 to disappear
Jun 11 00:27:25.996: INFO: Pod exec-volume-test-dynamicpv-ndp8 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-ndp8
Jun 11 00:27:25.996: INFO: Deleting pod "exec-volume-test-dynamicpv-ndp8" in namespace "volume-1496"
... skipping 28 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.PCf2odPVy/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.PCf2odPVy/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.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 64 lines ...
Jun 11 00:26:52.809: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9972k64t8
STEP: creating a claim
Jun 11 00:26:52.925: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-blnp
STEP: Creating a pod to test subpath
Jun 11 00:26:53.270: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-blnp" in namespace "provisioning-9972" to be "Succeeded or Failed"
Jun 11 00:26:53.383: INFO: Pod "pod-subpath-test-dynamicpv-blnp": Phase="Pending", Reason="", readiness=false. Elapsed: 113.118743ms
Jun 11 00:26:55.496: INFO: Pod "pod-subpath-test-dynamicpv-blnp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.226624835s
Jun 11 00:26:57.620: INFO: Pod "pod-subpath-test-dynamicpv-blnp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.349783653s
Jun 11 00:26:59.734: INFO: Pod "pod-subpath-test-dynamicpv-blnp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.463870132s
Jun 11 00:27:01.847: INFO: Pod "pod-subpath-test-dynamicpv-blnp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.577489574s
Jun 11 00:27:03.961: INFO: Pod "pod-subpath-test-dynamicpv-blnp": Phase="Pending", Reason="", readiness=false. Elapsed: 10.69091647s
Jun 11 00:27:06.075: INFO: Pod "pod-subpath-test-dynamicpv-blnp": Phase="Pending", Reason="", readiness=false. Elapsed: 12.804746934s
Jun 11 00:27:08.189: INFO: Pod "pod-subpath-test-dynamicpv-blnp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.919600005s
STEP: Saw pod success
Jun 11 00:27:08.189: INFO: Pod "pod-subpath-test-dynamicpv-blnp" satisfied condition "Succeeded or Failed"
Jun 11 00:27:08.307: INFO: Trying to get logs from node ip-172-20-42-226.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-blnp container test-container-subpath-dynamicpv-blnp: <nil>
STEP: delete the pod
Jun 11 00:27:08.569: INFO: Waiting for pod pod-subpath-test-dynamicpv-blnp to disappear
Jun 11 00:27:08.686: INFO: Pod pod-subpath-test-dynamicpv-blnp no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-blnp
Jun 11 00:27:08.687: INFO: Deleting pod "pod-subpath-test-dynamicpv-blnp" in namespace "provisioning-9972"
... skipping 72 lines ...
Jun 11 00:26:59.944: INFO: PersistentVolumeClaim pvc-92lvs found but phase is Pending instead of Bound.
Jun 11 00:27:02.060: INFO: PersistentVolumeClaim pvc-92lvs found and phase=Bound (14.925363479s)
Jun 11 00:27:02.060: INFO: Waiting up to 3m0s for PersistentVolume aws-jdch4 to have phase Bound
Jun 11 00:27:02.175: INFO: PersistentVolume aws-jdch4 found and phase=Bound (114.607954ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-jvrj
STEP: Creating a pod to test exec-volume-test
Jun 11 00:27:02.530: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-jvrj" in namespace "volume-7835" to be "Succeeded or Failed"
Jun 11 00:27:02.645: INFO: Pod "exec-volume-test-preprovisionedpv-jvrj": Phase="Pending", Reason="", readiness=false. Elapsed: 114.926771ms
Jun 11 00:27:04.761: INFO: Pod "exec-volume-test-preprovisionedpv-jvrj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.230484021s
Jun 11 00:27:06.876: INFO: Pod "exec-volume-test-preprovisionedpv-jvrj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.346286807s
Jun 11 00:27:08.992: INFO: Pod "exec-volume-test-preprovisionedpv-jvrj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.461917634s
Jun 11 00:27:11.106: INFO: Pod "exec-volume-test-preprovisionedpv-jvrj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.576241125s
Jun 11 00:27:13.222: INFO: Pod "exec-volume-test-preprovisionedpv-jvrj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.691651745s
STEP: Saw pod success
Jun 11 00:27:13.222: INFO: Pod "exec-volume-test-preprovisionedpv-jvrj" satisfied condition "Succeeded or Failed"
Jun 11 00:27:13.338: INFO: Trying to get logs from node ip-172-20-42-226.eu-west-3.compute.internal pod exec-volume-test-preprovisionedpv-jvrj container exec-container-preprovisionedpv-jvrj: <nil>
STEP: delete the pod
Jun 11 00:27:13.580: INFO: Waiting for pod exec-volume-test-preprovisionedpv-jvrj to disappear
Jun 11 00:27:13.695: INFO: Pod exec-volume-test-preprovisionedpv-jvrj no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-jvrj
Jun 11 00:27:13.695: INFO: Deleting pod "exec-volume-test-preprovisionedpv-jvrj" in namespace "volume-7835"
STEP: Deleting pv and pvc
Jun 11 00:27:13.809: INFO: Deleting PersistentVolumeClaim "pvc-92lvs"
Jun 11 00:27:13.924: INFO: Deleting PersistentVolume "aws-jdch4"
Jun 11 00:27:14.250: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0f682437862bed9c5", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f682437862bed9c5 is currently attached to i-0690821a57784e40a
	status code: 400, request id: f92e2a09-b700-4ee9-b7cc-51eb16f3ca8d
Jun 11 00:27:19.870: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0f682437862bed9c5", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f682437862bed9c5 is currently attached to i-0690821a57784e40a
	status code: 400, request id: ec97c2f9-864f-4090-b2f2-24dbcad99075
Jun 11 00:27:25.442: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0f682437862bed9c5", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f682437862bed9c5 is currently attached to i-0690821a57784e40a
	status code: 400, request id: 918c18f6-4c2d-42e5-9df5-9e523b492484
Jun 11 00:27:31.025: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0f682437862bed9c5", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f682437862bed9c5 is currently attached to i-0690821a57784e40a
	status code: 400, request id: 52ba7d98-97c2-46e8-b8e0-e4af83bab44a
Jun 11 00:27:36.569: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0f682437862bed9c5", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f682437862bed9c5 is currently attached to i-0690821a57784e40a
	status code: 400, request id: c0304260-87c5-4a90-9c5c-847a5109eacf
Jun 11 00:27:42.174: INFO: Successfully deleted PD "aws://eu-west-3a/vol-0f682437862bed9c5".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 00:27:42.174: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-7835" for this suite.
... skipping 48 lines ...
Jun 11 00:26:46.279: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8574-e2e-scmxsrf
STEP: creating a claim
Jun 11 00:26:46.394: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-mcrf
STEP: Creating a pod to test subpath
Jun 11 00:26:46.738: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-mcrf" in namespace "provisioning-8574" to be "Succeeded or Failed"
Jun 11 00:26:46.851: INFO: Pod "pod-subpath-test-dynamicpv-mcrf": Phase="Pending", Reason="", readiness=false. Elapsed: 113.151802ms
Jun 11 00:26:48.966: INFO: Pod "pod-subpath-test-dynamicpv-mcrf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.228099559s
Jun 11 00:26:51.080: INFO: Pod "pod-subpath-test-dynamicpv-mcrf": Phase="Pending", Reason="", readiness=false. Elapsed: 4.342022894s
Jun 11 00:26:53.195: INFO: Pod "pod-subpath-test-dynamicpv-mcrf": Phase="Pending", Reason="", readiness=false. Elapsed: 6.457216512s
Jun 11 00:26:55.309: INFO: Pod "pod-subpath-test-dynamicpv-mcrf": Phase="Pending", Reason="", readiness=false. Elapsed: 8.570917763s
Jun 11 00:26:57.422: INFO: Pod "pod-subpath-test-dynamicpv-mcrf": Phase="Pending", Reason="", readiness=false. Elapsed: 10.68443106s
Jun 11 00:26:59.537: INFO: Pod "pod-subpath-test-dynamicpv-mcrf": Phase="Pending", Reason="", readiness=false. Elapsed: 12.799235957s
Jun 11 00:27:01.651: INFO: Pod "pod-subpath-test-dynamicpv-mcrf": Phase="Pending", Reason="", readiness=false. Elapsed: 14.913014408s
Jun 11 00:27:03.764: INFO: Pod "pod-subpath-test-dynamicpv-mcrf": Phase="Pending", Reason="", readiness=false. Elapsed: 17.026248681s
Jun 11 00:27:05.878: INFO: Pod "pod-subpath-test-dynamicpv-mcrf": Phase="Pending", Reason="", readiness=false. Elapsed: 19.139957976s
Jun 11 00:27:07.991: INFO: Pod "pod-subpath-test-dynamicpv-mcrf": Phase="Pending", Reason="", readiness=false. Elapsed: 21.253620371s
Jun 11 00:27:10.106: INFO: Pod "pod-subpath-test-dynamicpv-mcrf": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.367987001s
STEP: Saw pod success
Jun 11 00:27:10.106: INFO: Pod "pod-subpath-test-dynamicpv-mcrf" satisfied condition "Succeeded or Failed"
Jun 11 00:27:10.219: INFO: Trying to get logs from node ip-172-20-47-248.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-mcrf container test-container-subpath-dynamicpv-mcrf: <nil>
STEP: delete the pod
Jun 11 00:27:10.464: INFO: Waiting for pod pod-subpath-test-dynamicpv-mcrf to disappear
Jun 11 00:27:10.577: INFO: Pod pod-subpath-test-dynamicpv-mcrf no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-mcrf
Jun 11 00:27:10.577: INFO: Deleting pod "pod-subpath-test-dynamicpv-mcrf" in namespace "provisioning-8574"
... skipping 457 lines ...
Jun 11 00:27:07.535: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-6869knvbc
STEP: creating a claim
Jun 11 00:27:07.658: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-2r5c
STEP: Creating a pod to test exec-volume-test
Jun 11 00:27:08.000: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-2r5c" in namespace "volume-6869" to be "Succeeded or Failed"
Jun 11 00:27:08.114: INFO: Pod "exec-volume-test-dynamicpv-2r5c": Phase="Pending", Reason="", readiness=false. Elapsed: 114.091392ms
Jun 11 00:27:10.227: INFO: Pod "exec-volume-test-dynamicpv-2r5c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.22730166s
Jun 11 00:27:12.341: INFO: Pod "exec-volume-test-dynamicpv-2r5c": Phase="Pending", Reason="", readiness=false. Elapsed: 4.340729634s
Jun 11 00:27:14.454: INFO: Pod "exec-volume-test-dynamicpv-2r5c": Phase="Pending", Reason="", readiness=false. Elapsed: 6.454352634s
Jun 11 00:27:16.567: INFO: Pod "exec-volume-test-dynamicpv-2r5c": Phase="Pending", Reason="", readiness=false. Elapsed: 8.567395052s
Jun 11 00:27:18.680: INFO: Pod "exec-volume-test-dynamicpv-2r5c": Phase="Pending", Reason="", readiness=false. Elapsed: 10.680675813s
... skipping 2 lines ...
Jun 11 00:27:25.021: INFO: Pod "exec-volume-test-dynamicpv-2r5c": Phase="Pending", Reason="", readiness=false. Elapsed: 17.020849733s
Jun 11 00:27:27.137: INFO: Pod "exec-volume-test-dynamicpv-2r5c": Phase="Pending", Reason="", readiness=false. Elapsed: 19.136716766s
Jun 11 00:27:29.251: INFO: Pod "exec-volume-test-dynamicpv-2r5c": Phase="Pending", Reason="", readiness=false. Elapsed: 21.250732282s
Jun 11 00:27:31.364: INFO: Pod "exec-volume-test-dynamicpv-2r5c": Phase="Pending", Reason="", readiness=false. Elapsed: 23.363805559s
Jun 11 00:27:33.479: INFO: Pod "exec-volume-test-dynamicpv-2r5c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 25.478949251s
STEP: Saw pod success
Jun 11 00:27:33.479: INFO: Pod "exec-volume-test-dynamicpv-2r5c" satisfied condition "Succeeded or Failed"
Jun 11 00:27:33.592: INFO: Trying to get logs from node ip-172-20-42-226.eu-west-3.compute.internal pod exec-volume-test-dynamicpv-2r5c container exec-container-dynamicpv-2r5c: <nil>
STEP: delete the pod
Jun 11 00:27:33.825: INFO: Waiting for pod exec-volume-test-dynamicpv-2r5c to disappear
Jun 11 00:27:33.937: INFO: Pod exec-volume-test-dynamicpv-2r5c no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-2r5c
Jun 11 00:27:33.938: INFO: Deleting pod "exec-volume-test-dynamicpv-2r5c" in namespace "volume-6869"
... skipping 95 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 00:27:40.418: 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.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 11 00:27:40.985: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 11 00:27:40.985: INFO: Creating resource for dynamic PV
Jun 11 00:27:40.985: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-34074fr2m
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 11 00:27:47.802: INFO: Deleting pod "pod-7ebd2bab-a564-4815-ae43-366b8141a517" in namespace "volumemode-3407"
Jun 11 00:27:47.933: INFO: Wait up to 5m0s for pod "pod-7ebd2bab-a564-4815-ae43-366b8141a517" to be fully deleted
STEP: Deleting pvc
Jun 11 00:27:58.387: INFO: Deleting PersistentVolumeClaim "awsq9fmw"
Jun 11 00:27:58.503: INFO: Waiting up to 5m0s for PersistentVolume pvc-126a9605-16cf-484a-94b0-ffc25017b361 to get deleted
Jun 11 00:27:58.616: INFO: PersistentVolume pvc-126a9605-16cf-484a-94b0-ffc25017b361 found and phase=Released (113.005125ms)
... skipping 10 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.PCf2odPVy/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.PCf2odPVy/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
    /tmp/kops.PCf2odPVy/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.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 11 00:28:09.196: INFO: Distro debian doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning
... skipping 107 lines ...
Jun 11 00:25:42.496: INFO: Creating resource for dynamic PV
Jun 11 00:25:42.497: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-8531-e2e-scz4g5s
STEP: creating a claim
Jun 11 00:25:42.611: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 11 00:25:42.962: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-qzz9v" in namespace "snapshotting-8531" to be "Succeeded or Failed"
Jun 11 00:25:43.076: INFO: Pod "pvc-snapshottable-tester-qzz9v": Phase="Pending", Reason="", readiness=false. Elapsed: 113.824933ms
Jun 11 00:25:45.192: INFO: Pod "pvc-snapshottable-tester-qzz9v": Phase="Pending", Reason="", readiness=false. Elapsed: 2.230102681s
Jun 11 00:25:47.308: INFO: Pod "pvc-snapshottable-tester-qzz9v": Phase="Pending", Reason="", readiness=false. Elapsed: 4.346150945s
Jun 11 00:25:49.423: INFO: Pod "pvc-snapshottable-tester-qzz9v": Phase="Pending", Reason="", readiness=false. Elapsed: 6.4601781s
Jun 11 00:25:51.537: INFO: Pod "pvc-snapshottable-tester-qzz9v": Phase="Pending", Reason="", readiness=false. Elapsed: 8.574381225s
Jun 11 00:25:53.653: INFO: Pod "pvc-snapshottable-tester-qzz9v": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.691073915s
STEP: Saw pod success
Jun 11 00:25:53.653: INFO: Pod "pvc-snapshottable-tester-qzz9v" satisfied condition "Succeeded or Failed"
Jun 11 00:25:53.883: INFO: Pod pvc-snapshottable-tester-qzz9v has the following logs: 
Jun 11 00:25:53.883: INFO: Deleting pod "pvc-snapshottable-tester-qzz9v" in namespace "snapshotting-8531"
Jun 11 00:25:54.003: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-qzz9v" to be fully deleted
Jun 11 00:25:54.117: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.com5hwhb] to have phase Bound
Jun 11 00:25:54.231: INFO: PersistentVolumeClaim ebs.csi.aws.com5hwhb found and phase=Bound (114.072038ms)
STEP: [init] checking the claim
... skipping 34 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.PCf2odPVy/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 11 00:26:46.271: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-j6gzg" in namespace "snapshotting-8531" to be "Succeeded or Failed"
Jun 11 00:26:46.384: INFO: Pod "pvc-snapshottable-data-tester-j6gzg": Phase="Pending", Reason="", readiness=false. Elapsed: 113.469631ms
Jun 11 00:26:48.500: INFO: Pod "pvc-snapshottable-data-tester-j6gzg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.229722716s
Jun 11 00:26:50.616: INFO: Pod "pvc-snapshottable-data-tester-j6gzg": Phase="Pending", Reason="", readiness=false. Elapsed: 4.345837926s
Jun 11 00:26:52.732: INFO: Pod "pvc-snapshottable-data-tester-j6gzg": Phase="Pending", Reason="", readiness=false. Elapsed: 6.461214392s
Jun 11 00:26:54.854: INFO: Pod "pvc-snapshottable-data-tester-j6gzg": Phase="Pending", Reason="", readiness=false. Elapsed: 8.582953285s
Jun 11 00:26:56.972: INFO: Pod "pvc-snapshottable-data-tester-j6gzg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.701294527s
STEP: Saw pod success
Jun 11 00:26:56.972: INFO: Pod "pvc-snapshottable-data-tester-j6gzg" satisfied condition "Succeeded or Failed"
Jun 11 00:26:57.201: INFO: Pod pvc-snapshottable-data-tester-j6gzg has the following logs: 
Jun 11 00:26:57.201: INFO: Deleting pod "pvc-snapshottable-data-tester-j6gzg" in namespace "snapshotting-8531"
Jun 11 00:26:57.323: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-j6gzg" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 11 00:27:11.897: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-8531 exec restored-pvc-tester-g5vpg --namespace=snapshotting-8531 -- cat /mnt/test/data'
... skipping 259 lines ...
    /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:108
      
      /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:225
        should check snapshot fields, check restore correctly works after modifying source data, check deletion [It]
        /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:243

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

        /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:602
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
... skipping 230 lines ...
Jun 11 00:27:48.799: INFO: Creating resource for dynamic PV
Jun 11 00:27:48.799: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-7570kbmtx
STEP: creating a claim
STEP: Expanding non-expandable pvc
Jun 11 00:27:49.140: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 11 00:27:49.367: INFO: Error updating pvc awsrjb26: PersistentVolumeClaim "awsrjb26" is invalid: spec: Forbidden: spec is 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-7570kbmtx",
  	... // 2 identical fields
  }

Jun 11 00:27:51.595: INFO: Error updating pvc awsrjb26: PersistentVolumeClaim "awsrjb26" is invalid: spec: Forbidden: spec is 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-7570kbmtx",
  	... // 2 identical fields
  }

Jun 11 00:27:53.623: INFO: Error updating pvc awsrjb26: PersistentVolumeClaim "awsrjb26" is invalid: spec: Forbidden: spec is 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-7570kbmtx",
  	... // 2 identical fields
  }

Jun 11 00:27:55.596: INFO: Error updating pvc awsrjb26: PersistentVolumeClaim "awsrjb26" is invalid: spec: Forbidden: spec is 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-7570kbmtx",
  	... // 2 identical fields
  }

Jun 11 00:27:57.595: INFO: Error updating pvc awsrjb26: PersistentVolumeClaim "awsrjb26" is invalid: spec: Forbidden: spec is 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-7570kbmtx",
  	... // 2 identical fields
  }

Jun 11 00:27:59.595: INFO: Error updating pvc awsrjb26: PersistentVolumeClaim "awsrjb26" is invalid: spec: Forbidden: spec is 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-7570kbmtx",
  	... // 2 identical fields
  }

Jun 11 00:28:01.598: INFO: Error updating pvc awsrjb26: PersistentVolumeClaim "awsrjb26" is invalid: spec: Forbidden: spec is 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-7570kbmtx",
  	... // 2 identical fields
  }

Jun 11 00:28:03.601: INFO: Error updating pvc awsrjb26: PersistentVolumeClaim "awsrjb26" is invalid: spec: Forbidden: spec is 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-7570kbmtx",
  	... // 2 identical fields
  }

Jun 11 00:28:05.606: INFO: Error updating pvc awsrjb26: PersistentVolumeClaim "awsrjb26" is invalid: spec: Forbidden: spec is 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-7570kbmtx",
  	... // 2 identical fields
  }

Jun 11 00:28:07.594: INFO: Error updating pvc awsrjb26: PersistentVolumeClaim "awsrjb26" is invalid: spec: Forbidden: spec is 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-7570kbmtx",
  	... // 2 identical fields
  }

Jun 11 00:28:09.597: INFO: Error updating pvc awsrjb26: PersistentVolumeClaim "awsrjb26" is invalid: spec: Forbidden: spec is 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-7570kbmtx",
  	... // 2 identical fields
  }

Jun 11 00:28:11.595: INFO: Error updating pvc awsrjb26: PersistentVolumeClaim "awsrjb26" is invalid: spec: Forbidden: spec is 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-7570kbmtx",
  	... // 2 identical fields
  }

Jun 11 00:28:13.610: INFO: Error updating pvc awsrjb26: PersistentVolumeClaim "awsrjb26" is invalid: spec: Forbidden: spec is 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-7570kbmtx",
  	... // 2 identical fields
  }

Jun 11 00:28:15.596: INFO: Error updating pvc awsrjb26: PersistentVolumeClaim "awsrjb26" is invalid: spec: Forbidden: spec is 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-7570kbmtx",
  	... // 2 identical fields
  }

Jun 11 00:28:17.595: INFO: Error updating pvc awsrjb26: PersistentVolumeClaim "awsrjb26" is invalid: spec: Forbidden: spec is 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-7570kbmtx",
  	... // 2 identical fields
  }

Jun 11 00:28:19.597: INFO: Error updating pvc awsrjb26: PersistentVolumeClaim "awsrjb26" is invalid: spec: Forbidden: spec is 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-7570kbmtx",
  	... // 2 identical fields
  }

Jun 11 00:28:19.824: INFO: Error updating pvc awsrjb26: PersistentVolumeClaim "awsrjb26" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 40 lines ...
Jun 11 00:27:56.531: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 11 00:27:57.253: INFO: Successfully created a new PD: "aws://eu-west-3a/vol-04e191b3c17af787a".
Jun 11 00:27:57.253: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-h97k
STEP: Creating a pod to test exec-volume-test
Jun 11 00:27:57.368: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-h97k" in namespace "volume-1027" to be "Succeeded or Failed"
Jun 11 00:27:57.482: INFO: Pod "exec-volume-test-inlinevolume-h97k": Phase="Pending", Reason="", readiness=false. Elapsed: 113.575558ms
Jun 11 00:27:59.597: INFO: Pod "exec-volume-test-inlinevolume-h97k": Phase="Pending", Reason="", readiness=false. Elapsed: 2.22818694s
Jun 11 00:28:01.710: INFO: Pod "exec-volume-test-inlinevolume-h97k": Phase="Pending", Reason="", readiness=false. Elapsed: 4.34187958s
Jun 11 00:28:03.826: INFO: Pod "exec-volume-test-inlinevolume-h97k": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.457775696s
STEP: Saw pod success
Jun 11 00:28:03.826: INFO: Pod "exec-volume-test-inlinevolume-h97k" satisfied condition "Succeeded or Failed"
Jun 11 00:28:03.940: INFO: Trying to get logs from node ip-172-20-47-248.eu-west-3.compute.internal pod exec-volume-test-inlinevolume-h97k container exec-container-inlinevolume-h97k: <nil>
STEP: delete the pod
Jun 11 00:28:04.184: INFO: Waiting for pod exec-volume-test-inlinevolume-h97k to disappear
Jun 11 00:28:04.298: INFO: Pod exec-volume-test-inlinevolume-h97k no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-h97k
Jun 11 00:28:04.298: INFO: Deleting pod "exec-volume-test-inlinevolume-h97k" in namespace "volume-1027"
Jun 11 00:28:04.654: INFO: Couldn't delete PD "aws://eu-west-3a/vol-04e191b3c17af787a", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04e191b3c17af787a is currently attached to i-00014b5ed56029a5c
	status code: 400, request id: 7fc11195-6691-4605-9521-6299f54e8ab9
Jun 11 00:28:10.224: INFO: Couldn't delete PD "aws://eu-west-3a/vol-04e191b3c17af787a", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04e191b3c17af787a is currently attached to i-00014b5ed56029a5c
	status code: 400, request id: 4536dc07-4fce-4d2e-98cf-403e696e49d4
Jun 11 00:28:15.798: INFO: Couldn't delete PD "aws://eu-west-3a/vol-04e191b3c17af787a", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04e191b3c17af787a is currently attached to i-00014b5ed56029a5c
	status code: 400, request id: 3443cfbc-5691-4931-8990-fab83517ea9d
Jun 11 00:28:21.390: INFO: Successfully deleted PD "aws://eu-west-3a/vol-04e191b3c17af787a".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 00:28:21.390: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-1027" for this suite.
... skipping 131 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.PCf2odPVy/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.PCf2odPVy/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.PCf2odPVy/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.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

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

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

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

    /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:92
------------------------------
... skipping 260 lines ...
Jun 11 00:27:48.179: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2415-e2e-scdd7wt
STEP: creating a claim
Jun 11 00:27:48.293: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-ttcl
STEP: Creating a pod to test subpath
Jun 11 00:27:48.637: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-ttcl" in namespace "provisioning-2415" to be "Succeeded or Failed"
Jun 11 00:27:48.750: INFO: Pod "pod-subpath-test-dynamicpv-ttcl": Phase="Pending", Reason="", readiness=false. Elapsed: 113.174854ms
Jun 11 00:27:50.864: INFO: Pod "pod-subpath-test-dynamicpv-ttcl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.227276467s
Jun 11 00:27:52.978: INFO: Pod "pod-subpath-test-dynamicpv-ttcl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.340868885s
Jun 11 00:27:55.091: INFO: Pod "pod-subpath-test-dynamicpv-ttcl": Phase="Pending", Reason="", readiness=false. Elapsed: 6.454779008s
Jun 11 00:27:57.206: INFO: Pod "pod-subpath-test-dynamicpv-ttcl": Phase="Pending", Reason="", readiness=false. Elapsed: 8.569327553s
Jun 11 00:27:59.320: INFO: Pod "pod-subpath-test-dynamicpv-ttcl": Phase="Pending", Reason="", readiness=false. Elapsed: 10.683551848s
Jun 11 00:28:01.434: INFO: Pod "pod-subpath-test-dynamicpv-ttcl": Phase="Pending", Reason="", readiness=false. Elapsed: 12.797351297s
Jun 11 00:28:03.554: INFO: Pod "pod-subpath-test-dynamicpv-ttcl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.917012877s
STEP: Saw pod success
Jun 11 00:28:03.554: INFO: Pod "pod-subpath-test-dynamicpv-ttcl" satisfied condition "Succeeded or Failed"
Jun 11 00:28:03.669: INFO: Trying to get logs from node ip-172-20-55-69.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-ttcl container test-container-volume-dynamicpv-ttcl: <nil>
STEP: delete the pod
Jun 11 00:28:03.910: INFO: Waiting for pod pod-subpath-test-dynamicpv-ttcl to disappear
Jun 11 00:28:04.023: INFO: Pod pod-subpath-test-dynamicpv-ttcl no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-ttcl
Jun 11 00:28:04.023: INFO: Deleting pod "pod-subpath-test-dynamicpv-ttcl" in namespace "provisioning-2415"
... skipping 257 lines ...
Jun 11 00:28:09.773: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2513-e2e-scdjf5g
STEP: creating a claim
Jun 11 00:28:09.888: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-7zrs
STEP: Creating a pod to test multi_subpath
Jun 11 00:28:10.232: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-7zrs" in namespace "provisioning-2513" to be "Succeeded or Failed"
Jun 11 00:28:10.345: INFO: Pod "pod-subpath-test-dynamicpv-7zrs": Phase="Pending", Reason="", readiness=false. Elapsed: 113.01858ms
Jun 11 00:28:12.459: INFO: Pod "pod-subpath-test-dynamicpv-7zrs": Phase="Pending", Reason="", readiness=false. Elapsed: 2.227183795s
Jun 11 00:28:14.580: INFO: Pod "pod-subpath-test-dynamicpv-7zrs": Phase="Pending", Reason="", readiness=false. Elapsed: 4.348150518s
Jun 11 00:28:16.693: INFO: Pod "pod-subpath-test-dynamicpv-7zrs": Phase="Pending", Reason="", readiness=false. Elapsed: 6.461888003s
Jun 11 00:28:18.807: INFO: Pod "pod-subpath-test-dynamicpv-7zrs": Phase="Pending", Reason="", readiness=false. Elapsed: 8.575427671s
Jun 11 00:28:20.923: INFO: Pod "pod-subpath-test-dynamicpv-7zrs": Phase="Pending", Reason="", readiness=false. Elapsed: 10.691139313s
Jun 11 00:28:23.040: INFO: Pod "pod-subpath-test-dynamicpv-7zrs": Phase="Pending", Reason="", readiness=false. Elapsed: 12.808628105s
Jun 11 00:28:25.154: INFO: Pod "pod-subpath-test-dynamicpv-7zrs": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.922542734s
STEP: Saw pod success
Jun 11 00:28:25.154: INFO: Pod "pod-subpath-test-dynamicpv-7zrs" satisfied condition "Succeeded or Failed"
Jun 11 00:28:25.267: INFO: Trying to get logs from node ip-172-20-55-69.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-7zrs container test-container-subpath-dynamicpv-7zrs: <nil>
STEP: delete the pod
Jun 11 00:28:25.505: INFO: Waiting for pod pod-subpath-test-dynamicpv-7zrs to disappear
Jun 11 00:28:25.617: INFO: Pod pod-subpath-test-dynamicpv-7zrs no longer exists
STEP: Deleting pod
Jun 11 00:28:25.617: INFO: Deleting pod "pod-subpath-test-dynamicpv-7zrs" in namespace "provisioning-2513"
... skipping 28 lines ...

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 108 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 00:28:12.140: 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.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun 11 00:28:12.703: INFO: Creating resource for dynamic PV
Jun 11 00:28:12.703: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9486-e2e-sc8g5cw
STEP: creating a claim
Jun 11 00:28:12.817: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-lgzv
STEP: Checking for subpath error in container status
Jun 11 00:28:29.388: INFO: Deleting pod "pod-subpath-test-dynamicpv-lgzv" in namespace "provisioning-9486"
Jun 11 00:28:29.502: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-lgzv" to be fully deleted
STEP: Deleting pod
Jun 11 00:28:41.727: INFO: Deleting pod "pod-subpath-test-dynamicpv-lgzv" in namespace "provisioning-9486"
STEP: Deleting pvc
Jun 11 00:28:42.068: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com4k5x9"
... skipping 9 lines ...

• [SLOW TEST:35.622 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.PCf2odPVy/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.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (ntfs)][Feature:Windows] volumes
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 11 00:28:47.764: INFO: Distro debian doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Pre-provisioned PV (ntfs)][Feature:Windows] volumes
... skipping 293 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 00:28:20.405: 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.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun 11 00:28:20.977: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 11 00:28:20.977: INFO: Creating resource for dynamic PV
Jun 11 00:28:20.977: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5397zwnlz
STEP: creating a claim
Jun 11 00:28:21.090: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-ddgw
STEP: Checking for subpath error in container status
Jun 11 00:28:31.670: INFO: Deleting pod "pod-subpath-test-dynamicpv-ddgw" in namespace "provisioning-5397"
Jun 11 00:28:31.788: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-ddgw" to be fully deleted
STEP: Deleting pod
Jun 11 00:28:44.017: INFO: Deleting pod "pod-subpath-test-dynamicpv-ddgw" in namespace "provisioning-5397"
STEP: Deleting pvc
Jun 11 00:28:44.360: INFO: Deleting PersistentVolumeClaim "awss5kc5"
... skipping 12 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.PCf2odPVy/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.PCf2odPVy/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath file is outside the volume [Slow][LinuxOnly]
      /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 230 lines ...
Jun 11 00:26:24.340: INFO: Creating resource for dynamic PV
Jun 11 00:26:24.340: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-1617-e2e-sc6wsjq
STEP: creating a claim
Jun 11 00:26:24.455: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 11 00:26:24.802: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-j95wq" in namespace "snapshotting-1617" to be "Succeeded or Failed"
Jun 11 00:26:24.915: INFO: Pod "pvc-snapshottable-tester-j95wq": Phase="Pending", Reason="", readiness=false. Elapsed: 113.0265ms
Jun 11 00:26:27.028: INFO: Pod "pvc-snapshottable-tester-j95wq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.226405244s
Jun 11 00:26:29.142: INFO: Pod "pvc-snapshottable-tester-j95wq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.339835894s
Jun 11 00:26:31.257: INFO: Pod "pvc-snapshottable-tester-j95wq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.454827681s
Jun 11 00:26:33.378: INFO: Pod "pvc-snapshottable-tester-j95wq": Phase="Pending", Reason="", readiness=false. Elapsed: 8.575958634s
Jun 11 00:26:35.492: INFO: Pod "pvc-snapshottable-tester-j95wq": Phase="Pending", Reason="", readiness=false. Elapsed: 10.690333471s
... skipping 10 lines ...
Jun 11 00:26:58.749: INFO: Pod "pvc-snapshottable-tester-j95wq": Phase="Pending", Reason="", readiness=false. Elapsed: 33.947418895s
Jun 11 00:27:00.866: INFO: Pod "pvc-snapshottable-tester-j95wq": Phase="Pending", Reason="", readiness=false. Elapsed: 36.063546075s
Jun 11 00:27:02.979: INFO: Pod "pvc-snapshottable-tester-j95wq": Phase="Pending", Reason="", readiness=false. Elapsed: 38.176832595s
Jun 11 00:27:05.093: INFO: Pod "pvc-snapshottable-tester-j95wq": Phase="Pending", Reason="", readiness=false. Elapsed: 40.290439121s
Jun 11 00:27:07.206: INFO: Pod "pvc-snapshottable-tester-j95wq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 42.404088021s
STEP: Saw pod success
Jun 11 00:27:07.206: INFO: Pod "pvc-snapshottable-tester-j95wq" satisfied condition "Succeeded or Failed"
Jun 11 00:27:07.434: INFO: Pod pvc-snapshottable-tester-j95wq has the following logs: 
Jun 11 00:27:07.434: INFO: Deleting pod "pvc-snapshottable-tester-j95wq" in namespace "snapshotting-1617"
Jun 11 00:27:07.552: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-j95wq" to be fully deleted
Jun 11 00:27:07.668: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.com26rhg] to have phase Bound
Jun 11 00:27:07.780: INFO: PersistentVolumeClaim ebs.csi.aws.com26rhg found and phase=Bound (112.597366ms)
STEP: [init] checking the claim
... skipping 27 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.PCf2odPVy/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 11 00:27:44.998: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-5vv2v" in namespace "snapshotting-1617" to be "Succeeded or Failed"
Jun 11 00:27:45.111: INFO: Pod "pvc-snapshottable-data-tester-5vv2v": Phase="Pending", Reason="", readiness=false. Elapsed: 113.646794ms
Jun 11 00:27:47.225: INFO: Pod "pvc-snapshottable-data-tester-5vv2v": Phase="Pending", Reason="", readiness=false. Elapsed: 2.227107601s
Jun 11 00:27:49.338: INFO: Pod "pvc-snapshottable-data-tester-5vv2v": Phase="Pending", Reason="", readiness=false. Elapsed: 4.340573286s
Jun 11 00:27:51.453: INFO: Pod "pvc-snapshottable-data-tester-5vv2v": Phase="Pending", Reason="", readiness=false. Elapsed: 6.455062228s
Jun 11 00:27:53.568: INFO: Pod "pvc-snapshottable-data-tester-5vv2v": Phase="Pending", Reason="", readiness=false. Elapsed: 8.570075509s
Jun 11 00:27:55.682: INFO: Pod "pvc-snapshottable-data-tester-5vv2v": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.683753723s
STEP: Saw pod success
Jun 11 00:27:55.682: INFO: Pod "pvc-snapshottable-data-tester-5vv2v" satisfied condition "Succeeded or Failed"
Jun 11 00:27:55.912: INFO: Pod pvc-snapshottable-data-tester-5vv2v has the following logs: 
Jun 11 00:27:55.912: INFO: Deleting pod "pvc-snapshottable-data-tester-5vv2v" in namespace "snapshotting-1617"
Jun 11 00:27:56.034: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-5vv2v" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 11 00:28:18.611: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-1617 exec restored-pvc-tester-x7hm2 --namespace=snapshotting-1617 -- cat /mnt/test/data'
... skipping 176 lines ...
Jun 11 00:28:30.630: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-48594t5f9
STEP: creating a claim
Jun 11 00:28:30.743: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-b9gz
STEP: Creating a pod to test exec-volume-test
Jun 11 00:28:31.090: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-b9gz" in namespace "volume-4859" to be "Succeeded or Failed"
Jun 11 00:28:31.204: INFO: Pod "exec-volume-test-dynamicpv-b9gz": Phase="Pending", Reason="", readiness=false. Elapsed: 113.494192ms
Jun 11 00:28:33.328: INFO: Pod "exec-volume-test-dynamicpv-b9gz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.237260779s
Jun 11 00:28:35.442: INFO: Pod "exec-volume-test-dynamicpv-b9gz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.351478311s
Jun 11 00:28:37.557: INFO: Pod "exec-volume-test-dynamicpv-b9gz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.466373256s
Jun 11 00:28:39.672: INFO: Pod "exec-volume-test-dynamicpv-b9gz": Phase="Pending", Reason="", readiness=false. Elapsed: 8.581742239s
Jun 11 00:28:41.786: INFO: Pod "exec-volume-test-dynamicpv-b9gz": Phase="Pending", Reason="", readiness=false. Elapsed: 10.695201883s
Jun 11 00:28:43.903: INFO: Pod "exec-volume-test-dynamicpv-b9gz": Phase="Pending", Reason="", readiness=false. Elapsed: 12.812440771s
Jun 11 00:28:46.018: INFO: Pod "exec-volume-test-dynamicpv-b9gz": Phase="Pending", Reason="", readiness=false. Elapsed: 14.92736409s
Jun 11 00:28:48.132: INFO: Pod "exec-volume-test-dynamicpv-b9gz": Phase="Pending", Reason="", readiness=false. Elapsed: 17.041797339s
Jun 11 00:28:50.246: INFO: Pod "exec-volume-test-dynamicpv-b9gz": Phase="Pending", Reason="", readiness=false. Elapsed: 19.155880388s
Jun 11 00:28:52.361: INFO: Pod "exec-volume-test-dynamicpv-b9gz": Phase="Pending", Reason="", readiness=false. Elapsed: 21.270421305s
Jun 11 00:28:54.476: INFO: Pod "exec-volume-test-dynamicpv-b9gz": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.385252111s
STEP: Saw pod success
Jun 11 00:28:54.476: INFO: Pod "exec-volume-test-dynamicpv-b9gz" satisfied condition "Succeeded or Failed"
Jun 11 00:28:54.589: INFO: Trying to get logs from node ip-172-20-45-141.eu-west-3.compute.internal pod exec-volume-test-dynamicpv-b9gz container exec-container-dynamicpv-b9gz: <nil>
STEP: delete the pod
Jun 11 00:28:54.825: INFO: Waiting for pod exec-volume-test-dynamicpv-b9gz to disappear
Jun 11 00:28:54.945: INFO: Pod exec-volume-test-dynamicpv-b9gz no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-b9gz
Jun 11 00:28:54.945: INFO: Deleting pod "exec-volume-test-dynamicpv-b9gz" in namespace "volume-4859"
... skipping 172 lines ...
Jun 11 00:28:42.719: INFO: Creating resource for dynamic PV
Jun 11 00:28:42.719: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-6104-e2e-scr8qd4
STEP: creating a claim
STEP: Expanding non-expandable pvc
Jun 11 00:28:43.071: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 11 00:28:43.310: INFO: Error updating pvc ebs.csi.aws.commgtkv: PersistentVolumeClaim "ebs.csi.aws.commgtkv" is invalid: spec: Forbidden: spec is 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-6104-e2e-scr8qd4",
  	... // 2 identical fields
  }

Jun 11 00:28:45.538: INFO: Error updating pvc ebs.csi.aws.commgtkv: PersistentVolumeClaim "ebs.csi.aws.commgtkv" is invalid: spec: Forbidden: spec is 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-6104-e2e-scr8qd4",
  	... // 2 identical fields
  }

Jun 11 00:28:47.544: INFO: Error updating pvc ebs.csi.aws.commgtkv: PersistentVolumeClaim "ebs.csi.aws.commgtkv" is invalid: spec: Forbidden: spec is 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-6104-e2e-scr8qd4",
  	... // 2 identical fields
  }

Jun 11 00:28:49.537: INFO: Error updating pvc ebs.csi.aws.commgtkv: PersistentVolumeClaim "ebs.csi.aws.commgtkv" is invalid: spec: Forbidden: spec is 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-6104-e2e-scr8qd4",
  	... // 2 identical fields
  }

Jun 11 00:28:51.537: INFO: Error updating pvc ebs.csi.aws.commgtkv: PersistentVolumeClaim "ebs.csi.aws.commgtkv" is invalid: spec: Forbidden: spec is 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-6104-e2e-scr8qd4",
  	... // 2 identical fields
  }

Jun 11 00:28:53.546: INFO: Error updating pvc ebs.csi.aws.commgtkv: PersistentVolumeClaim "ebs.csi.aws.commgtkv" is invalid: spec: Forbidden: spec is 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-6104-e2e-scr8qd4",
  	... // 2 identical fields
  }

Jun 11 00:28:55.537: INFO: Error updating pvc ebs.csi.aws.commgtkv: PersistentVolumeClaim "ebs.csi.aws.commgtkv" is invalid: spec: Forbidden: spec is 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-6104-e2e-scr8qd4",
  	... // 2 identical fields
  }

Jun 11 00:28:57.537: INFO: Error updating pvc ebs.csi.aws.commgtkv: PersistentVolumeClaim "ebs.csi.aws.commgtkv" is invalid: spec: Forbidden: spec is 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-6104-e2e-scr8qd4",
  	... // 2 identical fields
  }

Jun 11 00:28:59.538: INFO: Error updating pvc ebs.csi.aws.commgtkv: PersistentVolumeClaim "ebs.csi.aws.commgtkv" is invalid: spec: Forbidden: spec is 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-6104-e2e-scr8qd4",
  	... // 2 identical fields
  }

Jun 11 00:29:01.540: INFO: Error updating pvc ebs.csi.aws.commgtkv: PersistentVolumeClaim "ebs.csi.aws.commgtkv" is invalid: spec: Forbidden: spec is 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-6104-e2e-scr8qd4",
  	... // 2 identical fields
  }

Jun 11 00:29:03.543: INFO: Error updating pvc ebs.csi.aws.commgtkv: PersistentVolumeClaim "ebs.csi.aws.commgtkv" is invalid: spec: Forbidden: spec is 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-6104-e2e-scr8qd4",
  	... // 2 identical fields
  }

Jun 11 00:29:05.538: INFO: Error updating pvc ebs.csi.aws.commgtkv: PersistentVolumeClaim "ebs.csi.aws.commgtkv" is invalid: spec: Forbidden: spec is 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-6104-e2e-scr8qd4",
  	... // 2 identical fields
  }

Jun 11 00:29:07.538: INFO: Error updating pvc ebs.csi.aws.commgtkv: PersistentVolumeClaim "ebs.csi.aws.commgtkv" is invalid: spec: Forbidden: spec is 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-6104-e2e-scr8qd4",
  	... // 2 identical fields
  }

Jun 11 00:29:09.538: INFO: Error updating pvc ebs.csi.aws.commgtkv: PersistentVolumeClaim "ebs.csi.aws.commgtkv" is invalid: spec: Forbidden: spec is 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-6104-e2e-scr8qd4",
  	... // 2 identical fields
  }

Jun 11 00:29:11.537: INFO: Error updating pvc ebs.csi.aws.commgtkv: PersistentVolumeClaim "ebs.csi.aws.commgtkv" is invalid: spec: Forbidden: spec is 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-6104-e2e-scr8qd4",
  	... // 2 identical fields
  }

Jun 11 00:29:13.543: INFO: Error updating pvc ebs.csi.aws.commgtkv: PersistentVolumeClaim "ebs.csi.aws.commgtkv" is invalid: spec: Forbidden: spec is 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-6104-e2e-scr8qd4",
  	... // 2 identical fields
  }

Jun 11 00:29:13.769: INFO: Error updating pvc ebs.csi.aws.commgtkv: PersistentVolumeClaim "ebs.csi.aws.commgtkv" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 207 lines ...
Jun 11 00:28:34.033: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5047f7c4l
STEP: creating a claim
Jun 11 00:28:34.146: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-4fm7
STEP: Creating a pod to test subpath
Jun 11 00:28:34.493: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-4fm7" in namespace "provisioning-5047" to be "Succeeded or Failed"
Jun 11 00:28:34.606: INFO: Pod "pod-subpath-test-dynamicpv-4fm7": Phase="Pending", Reason="", readiness=false. Elapsed: 112.845665ms
Jun 11 00:28:36.721: INFO: Pod "pod-subpath-test-dynamicpv-4fm7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.227763596s
Jun 11 00:28:38.835: INFO: Pod "pod-subpath-test-dynamicpv-4fm7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.341762487s
Jun 11 00:28:40.949: INFO: Pod "pod-subpath-test-dynamicpv-4fm7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.4556888s
Jun 11 00:28:43.065: INFO: Pod "pod-subpath-test-dynamicpv-4fm7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.572053572s
Jun 11 00:28:45.178: INFO: Pod "pod-subpath-test-dynamicpv-4fm7": Phase="Pending", Reason="", readiness=false. Elapsed: 10.685304749s
Jun 11 00:28:47.293: INFO: Pod "pod-subpath-test-dynamicpv-4fm7": Phase="Pending", Reason="", readiness=false. Elapsed: 12.800274291s
Jun 11 00:28:49.407: INFO: Pod "pod-subpath-test-dynamicpv-4fm7": Phase="Pending", Reason="", readiness=false. Elapsed: 14.913839519s
Jun 11 00:28:51.520: INFO: Pod "pod-subpath-test-dynamicpv-4fm7": Phase="Pending", Reason="", readiness=false. Elapsed: 17.027022339s
Jun 11 00:28:53.633: INFO: Pod "pod-subpath-test-dynamicpv-4fm7": Phase="Pending", Reason="", readiness=false. Elapsed: 19.14023682s
Jun 11 00:28:55.747: INFO: Pod "pod-subpath-test-dynamicpv-4fm7": Phase="Pending", Reason="", readiness=false. Elapsed: 21.254246422s
Jun 11 00:28:57.861: INFO: Pod "pod-subpath-test-dynamicpv-4fm7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.367369207s
STEP: Saw pod success
Jun 11 00:28:57.861: INFO: Pod "pod-subpath-test-dynamicpv-4fm7" satisfied condition "Succeeded or Failed"
Jun 11 00:28:57.974: INFO: Trying to get logs from node ip-172-20-55-69.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-4fm7 container test-container-volume-dynamicpv-4fm7: <nil>
STEP: delete the pod
Jun 11 00:28:58.214: INFO: Waiting for pod pod-subpath-test-dynamicpv-4fm7 to disappear
Jun 11 00:28:58.327: INFO: Pod pod-subpath-test-dynamicpv-4fm7 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-4fm7
Jun 11 00:28:58.327: INFO: Deleting pod "pod-subpath-test-dynamicpv-4fm7" in namespace "provisioning-5047"
... skipping 40 lines ...
Jun 11 00:28:48.359: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2687wdwjf
STEP: creating a claim
Jun 11 00:28:48.474: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-4jx7
STEP: Creating a pod to test subpath
Jun 11 00:28:48.823: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-4jx7" in namespace "provisioning-2687" to be "Succeeded or Failed"
Jun 11 00:28:48.936: INFO: Pod "pod-subpath-test-dynamicpv-4jx7": Phase="Pending", Reason="", readiness=false. Elapsed: 112.642557ms
Jun 11 00:28:51.049: INFO: Pod "pod-subpath-test-dynamicpv-4jx7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.225825783s
Jun 11 00:28:53.162: INFO: Pod "pod-subpath-test-dynamicpv-4jx7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.3390709s
Jun 11 00:28:55.276: INFO: Pod "pod-subpath-test-dynamicpv-4jx7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.452876949s
Jun 11 00:28:57.390: INFO: Pod "pod-subpath-test-dynamicpv-4jx7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.567094197s
Jun 11 00:28:59.504: INFO: Pod "pod-subpath-test-dynamicpv-4jx7": Phase="Pending", Reason="", readiness=false. Elapsed: 10.680753481s
Jun 11 00:29:01.616: INFO: Pod "pod-subpath-test-dynamicpv-4jx7": Phase="Pending", Reason="", readiness=false. Elapsed: 12.793276018s
Jun 11 00:29:03.730: INFO: Pod "pod-subpath-test-dynamicpv-4jx7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.907045545s
STEP: Saw pod success
Jun 11 00:29:03.730: INFO: Pod "pod-subpath-test-dynamicpv-4jx7" satisfied condition "Succeeded or Failed"
Jun 11 00:29:03.843: INFO: Trying to get logs from node ip-172-20-55-69.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-4jx7 container test-container-volume-dynamicpv-4jx7: <nil>
STEP: delete the pod
Jun 11 00:29:04.081: INFO: Waiting for pod pod-subpath-test-dynamicpv-4jx7 to disappear
Jun 11 00:29:04.193: INFO: Pod pod-subpath-test-dynamicpv-4jx7 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-4jx7
Jun 11 00:29:04.193: INFO: Deleting pod "pod-subpath-test-dynamicpv-4jx7" in namespace "provisioning-2687"
... skipping 65 lines ...
STEP: Deleting pod hostexec-ip-172-20-55-69.eu-west-3.compute.internal-h24gl in namespace volumemode-8969
Jun 11 00:29:10.456: INFO: Deleting pod "pod-b466221b-bd1e-474c-80e4-a1b43b53f74e" in namespace "volumemode-8969"
Jun 11 00:29:10.573: INFO: Wait up to 5m0s for pod "pod-b466221b-bd1e-474c-80e4-a1b43b53f74e" to be fully deleted
STEP: Deleting pv and pvc
Jun 11 00:29:16.802: INFO: Deleting PersistentVolumeClaim "pvc-r7g66"
Jun 11 00:29:16.917: INFO: Deleting PersistentVolume "aws-qx6gr"
Jun 11 00:29:17.242: INFO: Couldn't delete PD "aws://eu-west-3a/vol-06ce83ff125bbd9f0", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-06ce83ff125bbd9f0 is currently attached to i-0fcdea48570ae258b
	status code: 400, request id: 6d168c55-81ea-485a-a098-a6820297e767
Jun 11 00:29:22.822: INFO: Couldn't delete PD "aws://eu-west-3a/vol-06ce83ff125bbd9f0", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-06ce83ff125bbd9f0 is currently attached to i-0fcdea48570ae258b
	status code: 400, request id: b06e8208-315a-40f2-95ce-dc2d64862f39
Jun 11 00:29:28.391: INFO: Couldn't delete PD "aws://eu-west-3a/vol-06ce83ff125bbd9f0", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-06ce83ff125bbd9f0 is currently attached to i-0fcdea48570ae258b
	status code: 400, request id: e01c064f-695f-46d3-8936-a8d8cef41672
Jun 11 00:29:33.990: INFO: Successfully deleted PD "aws://eu-west-3a/vol-06ce83ff125bbd9f0".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 00:29:33.990: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-8969" for this suite.
... skipping 22 lines ...
Jun 11 00:29:03.834: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 11 00:29:04.574: INFO: Successfully created a new PD: "aws://eu-west-3a/vol-0c3b15b428537eda9".
Jun 11 00:29:04.574: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-gbck
STEP: Creating a pod to test exec-volume-test
Jun 11 00:29:04.693: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-gbck" in namespace "volume-1355" to be "Succeeded or Failed"
Jun 11 00:29:04.810: INFO: Pod "exec-volume-test-inlinevolume-gbck": Phase="Pending", Reason="", readiness=false. Elapsed: 116.490894ms
Jun 11 00:29:06.924: INFO: Pod "exec-volume-test-inlinevolume-gbck": Phase="Pending", Reason="", readiness=false. Elapsed: 2.230539674s
Jun 11 00:29:09.039: INFO: Pod "exec-volume-test-inlinevolume-gbck": Phase="Pending", Reason="", readiness=false. Elapsed: 4.34504269s
Jun 11 00:29:11.156: INFO: Pod "exec-volume-test-inlinevolume-gbck": Phase="Pending", Reason="", readiness=false. Elapsed: 6.462668981s
Jun 11 00:29:13.270: INFO: Pod "exec-volume-test-inlinevolume-gbck": Phase="Pending", Reason="", readiness=false. Elapsed: 8.576842826s
Jun 11 00:29:15.388: INFO: Pod "exec-volume-test-inlinevolume-gbck": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.694487865s
STEP: Saw pod success
Jun 11 00:29:15.388: INFO: Pod "exec-volume-test-inlinevolume-gbck" satisfied condition "Succeeded or Failed"
Jun 11 00:29:15.501: INFO: Trying to get logs from node ip-172-20-55-69.eu-west-3.compute.internal pod exec-volume-test-inlinevolume-gbck container exec-container-inlinevolume-gbck: <nil>
STEP: delete the pod
Jun 11 00:29:15.739: INFO: Waiting for pod exec-volume-test-inlinevolume-gbck to disappear
Jun 11 00:29:15.852: INFO: Pod exec-volume-test-inlinevolume-gbck no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-gbck
Jun 11 00:29:15.852: INFO: Deleting pod "exec-volume-test-inlinevolume-gbck" in namespace "volume-1355"
Jun 11 00:29:16.215: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0c3b15b428537eda9", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c3b15b428537eda9 is currently attached to i-0fcdea48570ae258b
	status code: 400, request id: 193a6353-e3e6-4028-94ac-89318c2f5976
Jun 11 00:29:21.797: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0c3b15b428537eda9", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c3b15b428537eda9 is currently attached to i-0fcdea48570ae258b
	status code: 400, request id: d4f660ce-b949-4d81-a00b-12201650f554
Jun 11 00:29:27.369: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0c3b15b428537eda9", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c3b15b428537eda9 is currently attached to i-0fcdea48570ae258b
	status code: 400, request id: e6bdf5d5-7be3-429c-b145-64ce4299b3a0
Jun 11 00:29:32.950: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0c3b15b428537eda9", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c3b15b428537eda9 is currently attached to i-0fcdea48570ae258b
	status code: 400, request id: f54deedf-2bfa-4747-9de0-cb43207f82f0
Jun 11 00:29:38.527: INFO: Successfully deleted PD "aws://eu-west-3a/vol-0c3b15b428537eda9".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 00:29:38.527: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-1355" for this suite.
... skipping 23 lines ...
Jun 11 00:29:06.672: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-6756-e2e-scqb8t2
STEP: creating a claim
Jun 11 00:29:06.787: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-4k8r
STEP: Creating a pod to test exec-volume-test
Jun 11 00:29:07.131: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-4k8r" in namespace "volume-6756" to be "Succeeded or Failed"
Jun 11 00:29:07.245: INFO: Pod "exec-volume-test-dynamicpv-4k8r": Phase="Pending", Reason="", readiness=false. Elapsed: 113.408082ms
Jun 11 00:29:09.360: INFO: Pod "exec-volume-test-dynamicpv-4k8r": Phase="Pending", Reason="", readiness=false. Elapsed: 2.228541143s
Jun 11 00:29:11.474: INFO: Pod "exec-volume-test-dynamicpv-4k8r": Phase="Pending", Reason="", readiness=false. Elapsed: 4.342355832s
Jun 11 00:29:13.588: INFO: Pod "exec-volume-test-dynamicpv-4k8r": Phase="Pending", Reason="", readiness=false. Elapsed: 6.456609561s
Jun 11 00:29:15.702: INFO: Pod "exec-volume-test-dynamicpv-4k8r": Phase="Pending", Reason="", readiness=false. Elapsed: 8.570705643s
Jun 11 00:29:17.816: INFO: Pod "exec-volume-test-dynamicpv-4k8r": Phase="Pending", Reason="", readiness=false. Elapsed: 10.684562246s
Jun 11 00:29:19.930: INFO: Pod "exec-volume-test-dynamicpv-4k8r": Phase="Pending", Reason="", readiness=false. Elapsed: 12.798674823s
Jun 11 00:29:22.044: INFO: Pod "exec-volume-test-dynamicpv-4k8r": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.913004874s
STEP: Saw pod success
Jun 11 00:29:22.044: INFO: Pod "exec-volume-test-dynamicpv-4k8r" satisfied condition "Succeeded or Failed"
Jun 11 00:29:22.158: INFO: Trying to get logs from node ip-172-20-45-141.eu-west-3.compute.internal pod exec-volume-test-dynamicpv-4k8r container exec-container-dynamicpv-4k8r: <nil>
STEP: delete the pod
Jun 11 00:29:22.397: INFO: Waiting for pod exec-volume-test-dynamicpv-4k8r to disappear
Jun 11 00:29:22.510: INFO: Pod exec-volume-test-dynamicpv-4k8r no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-4k8r
Jun 11 00:29:22.510: INFO: Deleting pod "exec-volume-test-dynamicpv-4k8r" in namespace "volume-6756"
... skipping 351 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 00:28:59.703: 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.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun 11 00:29:00.265: INFO: Creating resource for dynamic PV
Jun 11 00:29:00.265: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5014-e2e-sc2vw56
STEP: creating a claim
Jun 11 00:29:00.379: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-gk4b
STEP: Checking for subpath error in container status
Jun 11 00:29:10.950: INFO: Deleting pod "pod-subpath-test-dynamicpv-gk4b" in namespace "provisioning-5014"
Jun 11 00:29:11.066: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-gk4b" to be fully deleted
STEP: Deleting pod
Jun 11 00:29:17.292: INFO: Deleting pod "pod-subpath-test-dynamicpv-gk4b" in namespace "provisioning-5014"
STEP: Deleting pvc
Jun 11 00:29:17.630: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com2t65z"
... skipping 15 lines ...

• [SLOW TEST:54.312 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.PCf2odPVy/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.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 42 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 00:29:04.114: 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.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun 11 00:29:04.677: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 11 00:29:04.677: INFO: Creating resource for dynamic PV
Jun 11 00:29:04.677: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8416pzdkj
STEP: creating a claim
Jun 11 00:29:04.791: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-5nxf
STEP: Checking for subpath error in container status
Jun 11 00:29:27.367: INFO: Deleting pod "pod-subpath-test-dynamicpv-5nxf" in namespace "provisioning-8416"
Jun 11 00:29:27.485: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-5nxf" to be fully deleted
STEP: Deleting pod
Jun 11 00:29:39.715: INFO: Deleting pod "pod-subpath-test-dynamicpv-5nxf" in namespace "provisioning-8416"
STEP: Deleting pvc
Jun 11 00:29:40.056: INFO: Deleting PersistentVolumeClaim "aws8jg4w"
... skipping 13 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.PCf2odPVy/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.PCf2odPVy/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath directory is outside the volume [Slow][LinuxOnly]
      /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 7 lines ...
Jun 11 00:28:50.468: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6659-e2e-scwqkf7
STEP: creating a claim
Jun 11 00:28:50.583: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-kjdp
STEP: Creating a pod to test atomic-volume-subpath
Jun 11 00:28:50.927: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-kjdp" in namespace "provisioning-6659" to be "Succeeded or Failed"
Jun 11 00:28:51.040: INFO: Pod "pod-subpath-test-dynamicpv-kjdp": Phase="Pending", Reason="", readiness=false. Elapsed: 113.48648ms
Jun 11 00:28:53.155: INFO: Pod "pod-subpath-test-dynamicpv-kjdp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.227867273s
Jun 11 00:28:55.270: INFO: Pod "pod-subpath-test-dynamicpv-kjdp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.343243527s
Jun 11 00:28:57.386: INFO: Pod "pod-subpath-test-dynamicpv-kjdp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.458747137s
Jun 11 00:28:59.500: INFO: Pod "pod-subpath-test-dynamicpv-kjdp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.573044808s
Jun 11 00:29:01.614: INFO: Pod "pod-subpath-test-dynamicpv-kjdp": Phase="Pending", Reason="", readiness=false. Elapsed: 10.687105505s
... skipping 7 lines ...
Jun 11 00:29:18.532: INFO: Pod "pod-subpath-test-dynamicpv-kjdp": Phase="Running", Reason="", readiness=true. Elapsed: 27.605299027s
Jun 11 00:29:20.647: INFO: Pod "pod-subpath-test-dynamicpv-kjdp": Phase="Running", Reason="", readiness=true. Elapsed: 29.720063743s
Jun 11 00:29:22.761: INFO: Pod "pod-subpath-test-dynamicpv-kjdp": Phase="Running", Reason="", readiness=true. Elapsed: 31.834145255s
Jun 11 00:29:24.876: INFO: Pod "pod-subpath-test-dynamicpv-kjdp": Phase="Running", Reason="", readiness=true. Elapsed: 33.948882902s
Jun 11 00:29:26.991: INFO: Pod "pod-subpath-test-dynamicpv-kjdp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 36.063621667s
STEP: Saw pod success
Jun 11 00:29:26.991: INFO: Pod "pod-subpath-test-dynamicpv-kjdp" satisfied condition "Succeeded or Failed"
Jun 11 00:29:27.104: INFO: Trying to get logs from node ip-172-20-47-248.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-kjdp container test-container-subpath-dynamicpv-kjdp: <nil>
STEP: delete the pod
Jun 11 00:29:27.337: INFO: Waiting for pod pod-subpath-test-dynamicpv-kjdp to disappear
Jun 11 00:29:27.451: INFO: Pod pod-subpath-test-dynamicpv-kjdp no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-kjdp
Jun 11 00:29:27.455: INFO: Deleting pod "pod-subpath-test-dynamicpv-kjdp" in namespace "provisioning-6659"
... skipping 235 lines ...
Jun 11 00:29:52.426: INFO: Pod aws-client still exists
Jun 11 00:29:54.313: INFO: Waiting for pod aws-client to disappear
Jun 11 00:29:54.427: INFO: Pod aws-client still exists
Jun 11 00:29:56.314: INFO: Waiting for pod aws-client to disappear
Jun 11 00:29:56.429: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun 11 00:29:57.003: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0b04b7ca99114850b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0b04b7ca99114850b is currently attached to i-0fcdea48570ae258b
	status code: 400, request id: 0c738f93-8242-44c1-900e-5ffa9e85c372
Jun 11 00:30:02.599: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0b04b7ca99114850b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0b04b7ca99114850b is currently attached to i-0fcdea48570ae258b
	status code: 400, request id: f3aa2c6a-cbf1-41c7-85a4-e50aa8fb7f3f
Jun 11 00:30:08.188: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0b04b7ca99114850b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0b04b7ca99114850b is currently attached to i-0fcdea48570ae258b
	status code: 400, request id: cfb9b83f-47c6-4631-9f0e-ac7b4b6f1088
Jun 11 00:30:13.800: INFO: Successfully deleted PD "aws://eu-west-3a/vol-0b04b7ca99114850b".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 00:30:13.800: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-114" for this suite.
... skipping 650 lines ...
    /tmp/kops.PCf2odPVy/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/provisioning.go:200
------------------------------


Summarizing 1 Failure:

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

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


Ginkgo ran 1 suite in 10m47.611698604s
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
I0611 00:31:13.789340   26826 app.go:59] RunDir for this run: "/logs/artifacts/a535d597-ca48-11eb-ab6f-62c732df09e9"
I0611 00:31:13.789501   26826 app.go:90] ID for this run: "a535d597-ca48-11eb-ab6f-62c732df09e9"
I0611 00:31:13.802598   26826 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
I0611 00:31:13.819819   26832 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
... skipping 1479 lines ...