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

No Test Failures!


Error lines from build-log.txt

... skipping 518 lines ...
I0614 00:11:46.697701   16999 up.go:43] Cleaning up any leaked resources from previous cluster
I0614 00:11:46.697759   16999 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
I0614 00:11:46.712761   17005 featureflag.go:167] FeatureFlag "SpecOverrideFlag"=true
I0614 00:11:46.713598   17005 featureflag.go:167] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io" not found
W0614 00:11:47.194645   16999 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0614 00:11:47.194685   16999 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
I0614 00:11:47.211012   17015 featureflag.go:167] FeatureFlag "SpecOverrideFlag"=true
I0614 00:11:47.211098   17015 featureflag.go:167] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io" not found
I0614 00:11:47.725814   16999 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/06/14 00:11:47 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
I0614 00:11:47.733921   16999 http.go:37] curl https://ip.jsb.workers.dev
I0614 00:11:47.882175   16999 up.go:144] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops create cluster --name e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --cloud aws --kubernetes-version 1.21.0 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --networking calico --override=cluster.spec.cloudConfig.awsEBSCSIDriver.enabled=true --override=cluster.spec.snapshotController.enabled=true --override=cluster.spec.certManager.enabled=true --admin-access 35.223.168.202/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones eu-west-2a --master-size c5.large
I0614 00:11:47.896046   17032 featureflag.go:167] FeatureFlag "SpecOverrideFlag"=true
I0614 00:11:47.896127   17032 featureflag.go:167] FeatureFlag "AlphaAllowGCE"=true
I0614 00:11:47.941166   17032 create_cluster.go:732] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0614 00:11:48.544049   17032 new_cluster.go:1054]  Cloud Provider ID = aws
... skipping 40 lines ...

I0614 00:12:15.195155   16999 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
I0614 00:12:15.209444   17052 featureflag.go:167] FeatureFlag "SpecOverrideFlag"=true
I0614 00:12:15.209515   17052 featureflag.go:167] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

... skipping 9 lines ...
Machine	i-0e1bbe360340e9289					machine "i-0e1bbe360340e9289" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-kssm2	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-kssm2" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-zqxvq	system-cluster-critical pod "cert-manager-webhook-7bbf67968-zqxvq" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-9ccjg		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-9ccjg" is pending
Pod	kube-system/coredns-f45c4bf76-tvz2v			system-cluster-critical pod "coredns-f45c4bf76-tvz2v" is pending

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

... skipping 9 lines ...
Machine	i-0e1bbe360340e9289					machine "i-0e1bbe360340e9289" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-kssm2	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-kssm2" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-zqxvq	system-cluster-critical pod "cert-manager-webhook-7bbf67968-zqxvq" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-9ccjg		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-9ccjg" is pending
Pod	kube-system/coredns-f45c4bf76-tvz2v			system-cluster-critical pod "coredns-f45c4bf76-tvz2v" is pending

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

... skipping 9 lines ...
Machine	i-0e1bbe360340e9289					machine "i-0e1bbe360340e9289" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-kssm2	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-kssm2" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-zqxvq	system-cluster-critical pod "cert-manager-webhook-7bbf67968-zqxvq" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-9ccjg		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-9ccjg" is pending
Pod	kube-system/coredns-f45c4bf76-tvz2v			system-cluster-critical pod "coredns-f45c4bf76-tvz2v" is pending

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

... skipping 9 lines ...
Machine	i-0e1bbe360340e9289					machine "i-0e1bbe360340e9289" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-kssm2	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-kssm2" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-zqxvq	system-cluster-critical pod "cert-manager-webhook-7bbf67968-zqxvq" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-9ccjg		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-9ccjg" is pending
Pod	kube-system/coredns-f45c4bf76-tvz2v			system-cluster-critical pod "coredns-f45c4bf76-tvz2v" is pending

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

... skipping 9 lines ...
Machine	i-0e1bbe360340e9289					machine "i-0e1bbe360340e9289" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-kssm2	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-kssm2" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-zqxvq	system-cluster-critical pod "cert-manager-webhook-7bbf67968-zqxvq" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-9ccjg		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-9ccjg" is pending
Pod	kube-system/coredns-f45c4bf76-tvz2v			system-cluster-critical pod "coredns-f45c4bf76-tvz2v" is pending

Validation Failed
W0614 00:18:07.426908   17052 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 13 lines ...
Pod	kube-system/cert-manager-webhook-7bbf67968-zqxvq			system-cluster-critical pod "cert-manager-webhook-7bbf67968-zqxvq" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-9ccjg				system-cluster-critical pod "coredns-autoscaler-6f594f4c58-9ccjg" is pending
Pod	kube-system/coredns-f45c4bf76-tvz2v					system-cluster-critical pod "coredns-f45c4bf76-tvz2v" is pending
Pod	kube-system/ebs-csi-node-vhnbp						system-node-critical pod "ebs-csi-node-vhnbp" is pending
Pod	kube-system/kube-proxy-ip-172-20-37-60.eu-west-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-37-60.eu-west-2.compute.internal" is pending

Validation Failed
W0614 00:18:19.223354   17052 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 22 lines ...
Pod	kube-system/ebs-csi-node-fnkmk						system-node-critical pod "ebs-csi-node-fnkmk" is pending
Pod	kube-system/ebs-csi-node-mgdqk						system-node-critical pod "ebs-csi-node-mgdqk" is pending
Pod	kube-system/ebs-csi-node-pggw6						system-node-critical pod "ebs-csi-node-pggw6" is pending
Pod	kube-system/ebs-csi-node-vhnbp						system-node-critical pod "ebs-csi-node-vhnbp" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-37.eu-west-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-37.eu-west-2.compute.internal" is pending

Validation Failed
W0614 00:18:31.085732   17052 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 16 lines ...
Pod	kube-system/coredns-autoscaler-6f594f4c58-9ccjg		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-9ccjg" is pending
Pod	kube-system/coredns-f45c4bf76-tvz2v			system-cluster-critical pod "coredns-f45c4bf76-tvz2v" is pending
Pod	kube-system/ebs-csi-node-fnkmk				system-node-critical pod "ebs-csi-node-fnkmk" is pending
Pod	kube-system/ebs-csi-node-mgdqk				system-node-critical pod "ebs-csi-node-mgdqk" is pending
Pod	kube-system/ebs-csi-node-pggw6				system-node-critical pod "ebs-csi-node-pggw6" is pending

Validation Failed
W0614 00:18:42.874804   17052 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 12 lines ...
Pod	kube-system/calico-node-gg2lc				system-node-critical pod "calico-node-gg2lc" is not ready (calico-node)
Pod	kube-system/cert-manager-cainjector-74d69756d5-kssm2	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-kssm2" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-zqxvq	system-cluster-critical pod "cert-manager-webhook-7bbf67968-zqxvq" is pending
Pod	kube-system/coredns-f45c4bf76-gr4rq			system-cluster-critical pod "coredns-f45c4bf76-gr4rq" is pending
Pod	kube-system/coredns-f45c4bf76-tvz2v			system-cluster-critical pod "coredns-f45c4bf76-tvz2v" is pending

Validation Failed
W0614 00:18:54.666132   17052 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 250 lines ...

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

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

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

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

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

    /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 586 lines ...
STEP: Creating a kubernetes client
Jun 14 00:22:12.711: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename volumemode
W0614 00:22:13.817917   31083 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Jun 14 00:22:13.818: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail to use a volume in a pod with mismatched mode [Slow]
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 14 00:22:14.009: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 14 00:22:14.009: INFO: Creating resource for dynamic PV
Jun 14 00:22:14.009: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-843kqw97
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 14 00:22:26.689: INFO: Deleting pod "pod-f0b625e0-afeb-4611-8bbc-1e6790dea84d" in namespace "volumemode-843"
Jun 14 00:22:26.788: INFO: Wait up to 5m0s for pod "pod-f0b625e0-afeb-4611-8bbc-1e6790dea84d" to be fully deleted
STEP: Deleting pvc
Jun 14 00:22:31.175: INFO: Deleting PersistentVolumeClaim "aws4zg8z"
Jun 14 00:22:31.272: INFO: Waiting up to 5m0s for PersistentVolume pvc-077a0570-c01a-4c98-8d63-1f100e5517f6 to get deleted
Jun 14 00:22:31.368: INFO: PersistentVolume pvc-077a0570-c01a-4c98-8d63-1f100e5517f6 found and phase=Released (96.030352ms)
... skipping 10 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.FO5ImxMAG/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.FO5ImxMAG/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (block volmode)] volumeMode
    /tmp/kops.FO5ImxMAG/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.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow]
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 14 00:22:41.962: INFO: Driver "ebs.csi.aws.com" does not support volume type "PreprovisionedPV" - skipping
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow]
... skipping 28 lines ...
Jun 14 00:22:13.361: INFO: Creating resource for dynamic PV
Jun 14 00:22:13.361: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-71775vqxt
STEP: creating a claim
STEP: Expanding non-expandable pvc
Jun 14 00:22:13.654: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 14 00:22:13.852: INFO: Error updating pvc awsk84vs: PersistentVolumeClaim "awsk84vs" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-71775vqxt",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun 14 00:22:44.245: INFO: Error updating pvc awsk84vs: PersistentVolumeClaim "awsk84vs" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 42 lines ...
Jun 14 00:22:13.963: INFO: Creating resource for dynamic PV
Jun 14 00:22:13.963: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-2087-e2e-sccws7n
STEP: creating a claim
STEP: Expanding non-expandable pvc
Jun 14 00:22:14.252: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 14 00:22:14.444: INFO: Error updating pvc ebs.csi.aws.com2llgx: PersistentVolumeClaim "ebs.csi.aws.com2llgx" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2087-e2e-sccws7n",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun 14 00:22:44.830: INFO: Error updating pvc ebs.csi.aws.com2llgx: PersistentVolumeClaim "ebs.csi.aws.com2llgx" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 93 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 14 00:22:15.054: 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.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 14 00:22:16.163: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 14 00:22:16.163: INFO: Creating resource for dynamic PV
Jun 14 00:22:16.163: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-44327drq9
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 14 00:22:24.862: INFO: Deleting pod "pod-abb5f2df-96b2-40a6-8df6-cd3f9a33c401" in namespace "volumemode-4432"
Jun 14 00:22:24.959: INFO: Wait up to 5m0s for pod "pod-abb5f2df-96b2-40a6-8df6-cd3f9a33c401" to be fully deleted
STEP: Deleting pvc
Jun 14 00:22:31.346: INFO: Deleting PersistentVolumeClaim "awshnq5l"
Jun 14 00:22:31.443: INFO: Waiting up to 5m0s for PersistentVolume pvc-c5df7ed3-a559-4258-8bbe-98477434e8f4 to get deleted
Jun 14 00:22:31.540: INFO: PersistentVolume pvc-c5df7ed3-a559-4258-8bbe-98477434e8f4 found and phase=Released (96.385377ms)
... skipping 11 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.FO5ImxMAG/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.FO5ImxMAG/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
    /tmp/kops.FO5ImxMAG/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.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 97 lines ...
Jun 14 00:22:16.061: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-4984-e2e-sc2mzjj
STEP: creating a claim
Jun 14 00:22:16.162: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-w6rl
STEP: Creating a pod to test exec-volume-test
Jun 14 00:22:16.456: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-w6rl" in namespace "volume-4984" to be "Succeeded or Failed"
Jun 14 00:22:16.552: INFO: Pod "exec-volume-test-dynamicpv-w6rl": Phase="Pending", Reason="", readiness=false. Elapsed: 96.346951ms
Jun 14 00:22:18.652: INFO: Pod "exec-volume-test-dynamicpv-w6rl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.196408579s
Jun 14 00:22:20.754: INFO: Pod "exec-volume-test-dynamicpv-w6rl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.297742909s
Jun 14 00:22:22.851: INFO: Pod "exec-volume-test-dynamicpv-w6rl": Phase="Pending", Reason="", readiness=false. Elapsed: 6.394495442s
Jun 14 00:22:24.947: INFO: Pod "exec-volume-test-dynamicpv-w6rl": Phase="Pending", Reason="", readiness=false. Elapsed: 8.491336045s
Jun 14 00:22:27.045: INFO: Pod "exec-volume-test-dynamicpv-w6rl": Phase="Pending", Reason="", readiness=false. Elapsed: 10.589142353s
... skipping 5 lines ...
Jun 14 00:22:39.632: INFO: Pod "exec-volume-test-dynamicpv-w6rl": Phase="Pending", Reason="", readiness=false. Elapsed: 23.176311082s
Jun 14 00:22:41.731: INFO: Pod "exec-volume-test-dynamicpv-w6rl": Phase="Pending", Reason="", readiness=false. Elapsed: 25.275265954s
Jun 14 00:22:43.828: INFO: Pod "exec-volume-test-dynamicpv-w6rl": Phase="Pending", Reason="", readiness=false. Elapsed: 27.371755489s
Jun 14 00:22:45.925: INFO: Pod "exec-volume-test-dynamicpv-w6rl": Phase="Pending", Reason="", readiness=false. Elapsed: 29.468877551s
Jun 14 00:22:48.023: INFO: Pod "exec-volume-test-dynamicpv-w6rl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 31.566519337s
STEP: Saw pod success
Jun 14 00:22:48.023: INFO: Pod "exec-volume-test-dynamicpv-w6rl" satisfied condition "Succeeded or Failed"
Jun 14 00:22:48.120: INFO: Trying to get logs from node ip-172-20-60-182.eu-west-2.compute.internal pod exec-volume-test-dynamicpv-w6rl container exec-container-dynamicpv-w6rl: <nil>
STEP: delete the pod
Jun 14 00:22:49.133: INFO: Waiting for pod exec-volume-test-dynamicpv-w6rl to disappear
Jun 14 00:22:49.230: INFO: Pod exec-volume-test-dynamicpv-w6rl no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-w6rl
Jun 14 00:22:49.230: INFO: Deleting pod "exec-volume-test-dynamicpv-w6rl" in namespace "volume-4984"
... skipping 26 lines ...
STEP: Creating a kubernetes client
Jun 14 00:22:12.612: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename provisioning
W0614 00:22:13.222891   31014 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Jun 14 00:22:13.222: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
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.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun 14 00:22:13.412: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 14 00:22:13.412: INFO: Creating resource for dynamic PV
Jun 14 00:22:13.412: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-739bslfx
STEP: creating a claim
Jun 14 00:22:13.508: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-p8v8
STEP: Checking for subpath error in container status
Jun 14 00:22:49.995: INFO: Deleting pod "pod-subpath-test-dynamicpv-p8v8" in namespace "provisioning-739"
Jun 14 00:22:50.092: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-p8v8" to be fully deleted
STEP: Deleting pod
Jun 14 00:23:02.284: INFO: Deleting pod "pod-subpath-test-dynamicpv-p8v8" in namespace "provisioning-739"
STEP: Deleting pvc
Jun 14 00:23:02.570: INFO: Deleting PersistentVolumeClaim "awshvvfh"
... skipping 12 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.FO5ImxMAG/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.FO5ImxMAG/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.FO5ImxMAG/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.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] volume-stress
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 14 00:23:13.345: INFO: Driver aws doesn't specify stress test options -- skipping
[AfterEach] [Testpattern: Dynamic PV (default fs)] volume-stress
... skipping 29 lines ...
Jun 14 00:22:49.620: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-234298wg7
STEP: creating a claim
Jun 14 00:22:49.718: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Jun 14 00:22:49.920: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 14 00:22:50.119: INFO: Error updating pvc aws5qgc7: PersistentVolumeClaim "aws5qgc7" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-234298wg7",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun 14 00:23:20.516: INFO: Error updating pvc aws5qgc7: PersistentVolumeClaim "aws5qgc7" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 63 lines ...

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


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

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 113 lines ...
Jun 14 00:23:16.189: INFO: Pod aws-client still exists
Jun 14 00:23:18.092: INFO: Waiting for pod aws-client to disappear
Jun 14 00:23:18.188: INFO: Pod aws-client still exists
Jun 14 00:23:20.092: INFO: Waiting for pod aws-client to disappear
Jun 14 00:23:20.191: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun 14 00:23:20.424: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0938ea26cac16218d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0938ea26cac16218d is currently attached to i-02d9eae89c0612df4
	status code: 400, request id: 64874000-92f0-44c4-b981-0da9047e0dc0
Jun 14 00:23:25.941: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0938ea26cac16218d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0938ea26cac16218d is currently attached to i-02d9eae89c0612df4
	status code: 400, request id: 9a483f47-3745-4752-9336-2dd3c8db0fdc
Jun 14 00:23:31.492: INFO: Successfully deleted PD "aws://eu-west-2a/vol-0938ea26cac16218d".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 14 00:23:31.493: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-5598" for this suite.
... skipping 35 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 14 00:22:41.964: 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.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 14 00:22:42.449: INFO: Creating resource for dynamic PV
Jun 14 00:22:42.449: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-2787-e2e-scnfk65
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 14 00:22:49.133: INFO: Deleting pod "pod-67627541-b204-4eea-b18c-948b02587b7d" in namespace "volumemode-2787"
Jun 14 00:22:49.236: INFO: Wait up to 5m0s for pod "pod-67627541-b204-4eea-b18c-948b02587b7d" to be fully deleted
STEP: Deleting pvc
Jun 14 00:22:55.623: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com7xr9q"
Jun 14 00:22:55.720: INFO: Waiting up to 5m0s for PersistentVolume pvc-df5ef85e-4557-4584-85e4-0be1e0002831 to get deleted
Jun 14 00:22:55.816: INFO: PersistentVolume pvc-df5ef85e-4557-4584-85e4-0be1e0002831 found and phase=Released (96.089555ms)
... skipping 13 lines ...

• [SLOW TEST:49.843 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.FO5ImxMAG/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.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 14 00:23:31.809: INFO: Distro debian doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
... skipping 4 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.FO5ImxMAG/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.FO5ImxMAG/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.FO5ImxMAG/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.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Distro debian doesn't support ntfs -- skipping

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.FO5ImxMAG/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.FO5ImxMAG/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.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 56 lines ...
Jun 14 00:22:13.436: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-39654mj5z
STEP: creating a claim
Jun 14 00:22:13.532: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-4dvr
STEP: Creating a pod to test atomic-volume-subpath
Jun 14 00:22:13.824: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-4dvr" in namespace "provisioning-3965" to be "Succeeded or Failed"
Jun 14 00:22:13.921: INFO: Pod "pod-subpath-test-dynamicpv-4dvr": Phase="Pending", Reason="", readiness=false. Elapsed: 97.727938ms
Jun 14 00:22:16.018: INFO: Pod "pod-subpath-test-dynamicpv-4dvr": Phase="Pending", Reason="", readiness=false. Elapsed: 2.194505015s
Jun 14 00:22:18.116: INFO: Pod "pod-subpath-test-dynamicpv-4dvr": Phase="Pending", Reason="", readiness=false. Elapsed: 4.292249339s
Jun 14 00:22:20.214: INFO: Pod "pod-subpath-test-dynamicpv-4dvr": Phase="Pending", Reason="", readiness=false. Elapsed: 6.39080651s
Jun 14 00:22:22.311: INFO: Pod "pod-subpath-test-dynamicpv-4dvr": Phase="Pending", Reason="", readiness=false. Elapsed: 8.487477961s
Jun 14 00:22:24.415: INFO: Pod "pod-subpath-test-dynamicpv-4dvr": Phase="Pending", Reason="", readiness=false. Elapsed: 10.590988125s
... skipping 17 lines ...
Jun 14 00:23:02.171: INFO: Pod "pod-subpath-test-dynamicpv-4dvr": Phase="Running", Reason="", readiness=true. Elapsed: 48.347259698s
Jun 14 00:23:04.268: INFO: Pod "pod-subpath-test-dynamicpv-4dvr": Phase="Running", Reason="", readiness=true. Elapsed: 50.444627117s
Jun 14 00:23:06.365: INFO: Pod "pod-subpath-test-dynamicpv-4dvr": Phase="Running", Reason="", readiness=true. Elapsed: 52.541399s
Jun 14 00:23:08.462: INFO: Pod "pod-subpath-test-dynamicpv-4dvr": Phase="Running", Reason="", readiness=true. Elapsed: 54.638041345s
Jun 14 00:23:10.559: INFO: Pod "pod-subpath-test-dynamicpv-4dvr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 56.73578606s
STEP: Saw pod success
Jun 14 00:23:10.559: INFO: Pod "pod-subpath-test-dynamicpv-4dvr" satisfied condition "Succeeded or Failed"
Jun 14 00:23:10.656: INFO: Trying to get logs from node ip-172-20-60-182.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-4dvr container test-container-subpath-dynamicpv-4dvr: <nil>
STEP: delete the pod
Jun 14 00:23:10.858: INFO: Waiting for pod pod-subpath-test-dynamicpv-4dvr to disappear
Jun 14 00:23:10.954: INFO: Pod pod-subpath-test-dynamicpv-4dvr no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-4dvr
Jun 14 00:23:10.954: INFO: Deleting pod "pod-subpath-test-dynamicpv-4dvr" in namespace "provisioning-3965"
... skipping 54 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.FO5ImxMAG/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.FO5ImxMAG/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.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 34 lines ...
Jun 14 00:22:14.710: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-98cgf6r      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-98    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-98cgf6r,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-98    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-98cgf6r,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-98    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-98cgf6r,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-98cgf6r    a2c75127-952b-40a2-a9f4-0e4c9168b137 2462 0 2021-06-14 00:22:14 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-14 00:22:14 +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-lmkq9 pvc- provisioning-98  4aa2c25c-bbfe-42b6-ad15-edbbd08f1ba4 2482 0 2021-06-14 00:22:15 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-14 00:22:15 +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-98cgf6r,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-5daaf108-2a3b-4bbc-88f7-b61f69ffe2d8 in namespace provisioning-98
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun 14 00:22:39.792: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-z7l4t" in namespace "provisioning-98" to be "Succeeded or Failed"
Jun 14 00:22:39.899: INFO: Pod "pvc-volume-tester-writer-z7l4t": Phase="Pending", Reason="", readiness=false. Elapsed: 106.840514ms
Jun 14 00:22:41.998: INFO: Pod "pvc-volume-tester-writer-z7l4t": Phase="Pending", Reason="", readiness=false. Elapsed: 2.205934736s
Jun 14 00:22:44.097: INFO: Pod "pvc-volume-tester-writer-z7l4t": Phase="Pending", Reason="", readiness=false. Elapsed: 4.305031244s
Jun 14 00:22:46.196: INFO: Pod "pvc-volume-tester-writer-z7l4t": Phase="Pending", Reason="", readiness=false. Elapsed: 6.404339069s
Jun 14 00:22:48.295: INFO: Pod "pvc-volume-tester-writer-z7l4t": Phase="Pending", Reason="", readiness=false. Elapsed: 8.502782774s
Jun 14 00:22:50.395: INFO: Pod "pvc-volume-tester-writer-z7l4t": Phase="Pending", Reason="", readiness=false. Elapsed: 10.602983652s
... skipping 3 lines ...
Jun 14 00:22:58.790: INFO: Pod "pvc-volume-tester-writer-z7l4t": Phase="Pending", Reason="", readiness=false. Elapsed: 18.998372694s
Jun 14 00:23:00.889: INFO: Pod "pvc-volume-tester-writer-z7l4t": Phase="Pending", Reason="", readiness=false. Elapsed: 21.096952783s
Jun 14 00:23:02.986: INFO: Pod "pvc-volume-tester-writer-z7l4t": Phase="Pending", Reason="", readiness=false. Elapsed: 23.194565591s
Jun 14 00:23:05.084: INFO: Pod "pvc-volume-tester-writer-z7l4t": Phase="Pending", Reason="", readiness=false. Elapsed: 25.291840605s
Jun 14 00:23:07.181: INFO: Pod "pvc-volume-tester-writer-z7l4t": Phase="Succeeded", Reason="", readiness=false. Elapsed: 27.389452464s
STEP: Saw pod success
Jun 14 00:23:07.181: INFO: Pod "pvc-volume-tester-writer-z7l4t" satisfied condition "Succeeded or Failed"
Jun 14 00:23:07.378: INFO: Pod pvc-volume-tester-writer-z7l4t has the following logs: 
Jun 14 00:23:07.378: INFO: Deleting pod "pvc-volume-tester-writer-z7l4t" in namespace "provisioning-98"
Jun 14 00:23:07.482: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-z7l4t" 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-62-170.eu-west-2.compute.internal"
Jun 14 00:23:07.874: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-g7x8w" in namespace "provisioning-98" to be "Succeeded or Failed"
Jun 14 00:23:07.970: INFO: Pod "pvc-volume-tester-reader-g7x8w": Phase="Pending", Reason="", readiness=false. Elapsed: 96.78949ms
Jun 14 00:23:10.069: INFO: Pod "pvc-volume-tester-reader-g7x8w": Phase="Pending", Reason="", readiness=false. Elapsed: 2.195006693s
Jun 14 00:23:12.166: INFO: Pod "pvc-volume-tester-reader-g7x8w": Phase="Pending", Reason="", readiness=false. Elapsed: 4.292715457s
Jun 14 00:23:14.264: INFO: Pod "pvc-volume-tester-reader-g7x8w": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.389954597s
STEP: Saw pod success
Jun 14 00:23:14.264: INFO: Pod "pvc-volume-tester-reader-g7x8w" satisfied condition "Succeeded or Failed"
Jun 14 00:23:14.459: INFO: Pod pvc-volume-tester-reader-g7x8w has the following logs: hello world

Jun 14 00:23:14.459: INFO: Deleting pod "pvc-volume-tester-reader-g7x8w" in namespace "provisioning-98"
Jun 14 00:23:14.578: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-g7x8w" to be fully deleted
Jun 14 00:23:14.675: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-lmkq9] to have phase Bound
Jun 14 00:23:14.773: INFO: PersistentVolumeClaim pvc-lmkq9 found and phase=Bound (98.856436ms)
... skipping 55 lines ...

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

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

    /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 57 lines ...
Jun 14 00:23:20.750: INFO: Pod aws-client still exists
Jun 14 00:23:22.750: INFO: Waiting for pod aws-client to disappear
Jun 14 00:23:22.848: INFO: Pod aws-client still exists
Jun 14 00:23:24.750: INFO: Waiting for pod aws-client to disappear
Jun 14 00:23:24.848: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun 14 00:23:25.361: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0da403a7a4be9de8a", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0da403a7a4be9de8a is currently attached to i-02d9eae89c0612df4
	status code: 400, request id: 414840b1-c780-4e42-9b42-b23b33dcb7d8
Jun 14 00:23:30.902: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0da403a7a4be9de8a", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0da403a7a4be9de8a is currently attached to i-02d9eae89c0612df4
	status code: 400, request id: 7a04dd59-ffba-4ca3-a626-483807e92a77
Jun 14 00:23:36.405: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0da403a7a4be9de8a", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0da403a7a4be9de8a is currently attached to i-02d9eae89c0612df4
	status code: 400, request id: bba33ba7-8b45-4efd-81b0-584366b2a488
Jun 14 00:23:41.887: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0da403a7a4be9de8a", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0da403a7a4be9de8a is currently attached to i-02d9eae89c0612df4
	status code: 400, request id: 2027228e-c6c3-43f2-bd49-977e0d2404d4
Jun 14 00:23:47.397: INFO: Successfully deleted PD "aws://eu-west-2a/vol-0da403a7a4be9de8a".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 14 00:23:47.397: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-107" for this suite.
... skipping 105 lines ...

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 192 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 14 00:23:36.178: 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.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun 14 00:23:36.665: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 14 00:23:36.665: INFO: Creating resource for dynamic PV
Jun 14 00:23:36.665: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5151m7r9g
STEP: creating a claim
Jun 14 00:23:36.763: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-wbk6
STEP: Checking for subpath error in container status
Jun 14 00:24:01.266: INFO: Deleting pod "pod-subpath-test-dynamicpv-wbk6" in namespace "provisioning-5151"
Jun 14 00:24:01.364: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-wbk6" to be fully deleted
STEP: Deleting pod
Jun 14 00:24:11.558: INFO: Deleting pod "pod-subpath-test-dynamicpv-wbk6" in namespace "provisioning-5151"
STEP: Deleting pvc
Jun 14 00:24:11.849: INFO: Deleting PersistentVolumeClaim "awsnpqc7"
... skipping 13 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.FO5ImxMAG/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.FO5ImxMAG/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath file is outside the volume [Slow][LinuxOnly]
      /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (xfs)][Slow] volumes
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (xfs)][Slow] volumes
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 196 lines ...
Jun 14 00:24:07.462: INFO: Pod aws-client still exists
Jun 14 00:24:09.366: INFO: Waiting for pod aws-client to disappear
Jun 14 00:24:09.462: INFO: Pod aws-client still exists
Jun 14 00:24:11.367: INFO: Waiting for pod aws-client to disappear
Jun 14 00:24:11.463: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun 14 00:24:11.702: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0be2c2b99435e7c25", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0be2c2b99435e7c25 is currently attached to i-068ab7d6aa6e1db55
	status code: 400, request id: c4be37e3-421c-4bc2-bb3a-fc001d8e4420
Jun 14 00:24:17.237: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0be2c2b99435e7c25", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0be2c2b99435e7c25 is currently attached to i-068ab7d6aa6e1db55
	status code: 400, request id: 521fb411-08fa-4daa-aff9-3868850c5faa
Jun 14 00:24:22.749: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0be2c2b99435e7c25", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0be2c2b99435e7c25 is currently attached to i-068ab7d6aa6e1db55
	status code: 400, request id: a4536506-9ea1-4d40-80bb-b38579be3090
Jun 14 00:24:28.262: INFO: Successfully deleted PD "aws://eu-west-2a/vol-0be2c2b99435e7c25".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 14 00:24:28.262: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-2772" for this suite.
... skipping 37 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.FO5ImxMAG/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.FO5ImxMAG/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.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 166 lines ...
Jun 14 00:24:37.251: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 12 lines ...
Jun 14 00:23:22.189: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-433jwwkk
STEP: creating a claim
Jun 14 00:23:22.287: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-n4cw
STEP: Creating a pod to test exec-volume-test
Jun 14 00:23:22.588: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-n4cw" in namespace "volume-433" to be "Succeeded or Failed"
Jun 14 00:23:22.686: INFO: Pod "exec-volume-test-dynamicpv-n4cw": Phase="Pending", Reason="", readiness=false. Elapsed: 97.290569ms
Jun 14 00:23:24.784: INFO: Pod "exec-volume-test-dynamicpv-n4cw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.195593441s
Jun 14 00:23:26.882: INFO: Pod "exec-volume-test-dynamicpv-n4cw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.293824256s
Jun 14 00:23:28.980: INFO: Pod "exec-volume-test-dynamicpv-n4cw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.391490154s
Jun 14 00:23:31.078: INFO: Pod "exec-volume-test-dynamicpv-n4cw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.489815761s
Jun 14 00:23:33.176: INFO: Pod "exec-volume-test-dynamicpv-n4cw": Phase="Pending", Reason="", readiness=false. Elapsed: 10.588213582s
... skipping 8 lines ...
Jun 14 00:23:52.060: INFO: Pod "exec-volume-test-dynamicpv-n4cw": Phase="Pending", Reason="", readiness=false. Elapsed: 29.471594528s
Jun 14 00:23:54.158: INFO: Pod "exec-volume-test-dynamicpv-n4cw": Phase="Pending", Reason="", readiness=false. Elapsed: 31.569305792s
Jun 14 00:23:56.256: INFO: Pod "exec-volume-test-dynamicpv-n4cw": Phase="Pending", Reason="", readiness=false. Elapsed: 33.667895773s
Jun 14 00:23:58.355: INFO: Pod "exec-volume-test-dynamicpv-n4cw": Phase="Pending", Reason="", readiness=false. Elapsed: 35.766566412s
Jun 14 00:24:00.453: INFO: Pod "exec-volume-test-dynamicpv-n4cw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 37.865160411s
STEP: Saw pod success
Jun 14 00:24:00.453: INFO: Pod "exec-volume-test-dynamicpv-n4cw" satisfied condition "Succeeded or Failed"
Jun 14 00:24:00.551: INFO: Trying to get logs from node ip-172-20-60-182.eu-west-2.compute.internal pod exec-volume-test-dynamicpv-n4cw container exec-container-dynamicpv-n4cw: <nil>
STEP: delete the pod
Jun 14 00:24:00.753: INFO: Waiting for pod exec-volume-test-dynamicpv-n4cw to disappear
Jun 14 00:24:00.853: INFO: Pod exec-volume-test-dynamicpv-n4cw no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-n4cw
Jun 14 00:24:00.853: INFO: Deleting pod "exec-volume-test-dynamicpv-n4cw" in namespace "volume-433"
... skipping 293 lines ...
Jun 14 00:24:22.492: INFO: Waiting for pod aws-client to disappear
Jun 14 00:24:22.589: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 14 00:24:22.589: INFO: Deleting PersistentVolumeClaim "pvc-bgcmm"
Jun 14 00:24:22.685: INFO: Deleting PersistentVolume "aws-jjrg6"
Jun 14 00:24:23.310: INFO: Couldn't delete PD "aws://eu-west-2a/vol-08d907ffe97f81549", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08d907ffe97f81549 is currently attached to i-068ab7d6aa6e1db55
	status code: 400, request id: a8434abd-0fb0-46ff-a67a-7d5609bf8056
Jun 14 00:24:28.865: INFO: Couldn't delete PD "aws://eu-west-2a/vol-08d907ffe97f81549", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08d907ffe97f81549 is currently attached to i-068ab7d6aa6e1db55
	status code: 400, request id: 2398fee7-e25b-4f94-a268-a676cd536f36
Jun 14 00:24:34.440: INFO: Couldn't delete PD "aws://eu-west-2a/vol-08d907ffe97f81549", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08d907ffe97f81549 is currently attached to i-068ab7d6aa6e1db55
	status code: 400, request id: cbd58655-0fe8-4130-a537-e0eadfe9fb85
Jun 14 00:24:39.975: INFO: Couldn't delete PD "aws://eu-west-2a/vol-08d907ffe97f81549", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08d907ffe97f81549 is currently attached to i-068ab7d6aa6e1db55
	status code: 400, request id: 30d7f29b-e40c-411d-84d5-9d950e25b13f
Jun 14 00:24:45.631: INFO: Couldn't delete PD "aws://eu-west-2a/vol-08d907ffe97f81549", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08d907ffe97f81549 is currently attached to i-068ab7d6aa6e1db55
	status code: 400, request id: f60b7f5c-ccce-42ec-bc5e-d02d404c4dd5
Jun 14 00:24:51.169: INFO: Successfully deleted PD "aws://eu-west-2a/vol-08d907ffe97f81549".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 14 00:24:51.170: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-4777" for this suite.
... skipping 132 lines ...
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 14 00:24:51.368: 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.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Jun 14 00:24:51.948: INFO: found topology map[topology.kubernetes.io/zone:eu-west-2a]
Jun 14 00:24:51.948: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 14 00:24:51.948: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.FO5ImxMAG/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.FO5ImxMAG/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (delayed binding)] topology
    /tmp/kops.FO5ImxMAG/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.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 781 lines ...
Jun 14 00:23:32.988: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8971-e2e-sc2xstx
STEP: creating a claim
Jun 14 00:23:33.085: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-kjdg
STEP: Creating a pod to test subpath
Jun 14 00:23:33.377: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-kjdg" in namespace "provisioning-8971" to be "Succeeded or Failed"
Jun 14 00:23:33.473: INFO: Pod "pod-subpath-test-dynamicpv-kjdg": Phase="Pending", Reason="", readiness=false. Elapsed: 96.408446ms
Jun 14 00:23:35.570: INFO: Pod "pod-subpath-test-dynamicpv-kjdg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.192842462s
Jun 14 00:23:37.666: INFO: Pod "pod-subpath-test-dynamicpv-kjdg": Phase="Pending", Reason="", readiness=false. Elapsed: 4.289458352s
Jun 14 00:23:39.763: INFO: Pod "pod-subpath-test-dynamicpv-kjdg": Phase="Pending", Reason="", readiness=false. Elapsed: 6.385937517s
Jun 14 00:23:41.859: INFO: Pod "pod-subpath-test-dynamicpv-kjdg": Phase="Pending", Reason="", readiness=false. Elapsed: 8.482462308s
Jun 14 00:23:43.956: INFO: Pod "pod-subpath-test-dynamicpv-kjdg": Phase="Pending", Reason="", readiness=false. Elapsed: 10.579016837s
... skipping 3 lines ...
Jun 14 00:23:52.344: INFO: Pod "pod-subpath-test-dynamicpv-kjdg": Phase="Pending", Reason="", readiness=false. Elapsed: 18.967022164s
Jun 14 00:23:54.441: INFO: Pod "pod-subpath-test-dynamicpv-kjdg": Phase="Pending", Reason="", readiness=false. Elapsed: 21.064388177s
Jun 14 00:23:56.538: INFO: Pod "pod-subpath-test-dynamicpv-kjdg": Phase="Pending", Reason="", readiness=false. Elapsed: 23.161630815s
Jun 14 00:23:58.636: INFO: Pod "pod-subpath-test-dynamicpv-kjdg": Phase="Pending", Reason="", readiness=false. Elapsed: 25.258953176s
Jun 14 00:24:00.732: INFO: Pod "pod-subpath-test-dynamicpv-kjdg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 27.355765261s
STEP: Saw pod success
Jun 14 00:24:00.733: INFO: Pod "pod-subpath-test-dynamicpv-kjdg" satisfied condition "Succeeded or Failed"
Jun 14 00:24:00.833: INFO: Trying to get logs from node ip-172-20-34-37.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-kjdg container test-container-volume-dynamicpv-kjdg: <nil>
STEP: delete the pod
Jun 14 00:24:01.037: INFO: Waiting for pod pod-subpath-test-dynamicpv-kjdg to disappear
Jun 14 00:24:01.133: INFO: Pod pod-subpath-test-dynamicpv-kjdg no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-kjdg
Jun 14 00:24:01.133: INFO: Deleting pod "pod-subpath-test-dynamicpv-kjdg" in namespace "provisioning-8971"
... skipping 193 lines ...
Jun 14 00:24:42.922: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-3889rfvc4
STEP: creating a claim
Jun 14 00:24:43.020: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-ff4p
STEP: Creating a pod to test exec-volume-test
Jun 14 00:24:43.316: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-ff4p" in namespace "volume-3889" to be "Succeeded or Failed"
Jun 14 00:24:43.426: INFO: Pod "exec-volume-test-dynamicpv-ff4p": Phase="Pending", Reason="", readiness=false. Elapsed: 109.212617ms
Jun 14 00:24:45.524: INFO: Pod "exec-volume-test-dynamicpv-ff4p": Phase="Pending", Reason="", readiness=false. Elapsed: 2.207611811s
Jun 14 00:24:47.622: INFO: Pod "exec-volume-test-dynamicpv-ff4p": Phase="Pending", Reason="", readiness=false. Elapsed: 4.305300943s
Jun 14 00:24:49.719: INFO: Pod "exec-volume-test-dynamicpv-ff4p": Phase="Pending", Reason="", readiness=false. Elapsed: 6.402888579s
Jun 14 00:24:51.818: INFO: Pod "exec-volume-test-dynamicpv-ff4p": Phase="Pending", Reason="", readiness=false. Elapsed: 8.501291964s
Jun 14 00:24:53.916: INFO: Pod "exec-volume-test-dynamicpv-ff4p": Phase="Pending", Reason="", readiness=false. Elapsed: 10.599694264s
Jun 14 00:24:56.015: INFO: Pod "exec-volume-test-dynamicpv-ff4p": Phase="Pending", Reason="", readiness=false. Elapsed: 12.698404406s
Jun 14 00:24:58.112: INFO: Pod "exec-volume-test-dynamicpv-ff4p": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.795964147s
STEP: Saw pod success
Jun 14 00:24:58.113: INFO: Pod "exec-volume-test-dynamicpv-ff4p" satisfied condition "Succeeded or Failed"
Jun 14 00:24:58.210: INFO: Trying to get logs from node ip-172-20-62-170.eu-west-2.compute.internal pod exec-volume-test-dynamicpv-ff4p container exec-container-dynamicpv-ff4p: <nil>
STEP: delete the pod
Jun 14 00:24:58.413: INFO: Waiting for pod exec-volume-test-dynamicpv-ff4p to disappear
Jun 14 00:24:58.510: INFO: Pod exec-volume-test-dynamicpv-ff4p no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-ff4p
Jun 14 00:24:58.510: INFO: Deleting pod "exec-volume-test-dynamicpv-ff4p" in namespace "volume-3889"
... skipping 220 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 14 00:24:58.907: 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.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 14 00:24:59.391: INFO: Creating resource for dynamic PV
Jun 14 00:24:59.391: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-6310-e2e-scspxfq
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 14 00:25:06.080: INFO: Deleting pod "pod-7b9c617c-27ee-42bb-9875-5509276d2ade" in namespace "volumemode-6310"
Jun 14 00:25:06.178: INFO: Wait up to 5m0s for pod "pod-7b9c617c-27ee-42bb-9875-5509276d2ade" to be fully deleted
STEP: Deleting pvc
Jun 14 00:25:12.565: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comdnp92"
Jun 14 00:25:12.664: INFO: Waiting up to 5m0s for PersistentVolume pvc-921bc0ab-cf88-4fa1-8a0a-6cadad1a9737 to get deleted
Jun 14 00:25:12.760: INFO: PersistentVolume pvc-921bc0ab-cf88-4fa1-8a0a-6cadad1a9737 found and phase=Released (96.590627ms)
... skipping 8 lines ...

• [SLOW TEST:24.341 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.FO5ImxMAG/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.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 7 lines ...
Jun 14 00:23:46.737: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1108-e2e-scgrxw6
STEP: creating a claim
Jun 14 00:23:46.835: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-p2jg
STEP: Creating a pod to test subpath
Jun 14 00:23:47.128: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-p2jg" in namespace "provisioning-1108" to be "Succeeded or Failed"
Jun 14 00:23:47.225: INFO: Pod "pod-subpath-test-dynamicpv-p2jg": Phase="Pending", Reason="", readiness=false. Elapsed: 96.625752ms
Jun 14 00:23:49.322: INFO: Pod "pod-subpath-test-dynamicpv-p2jg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.193861526s
Jun 14 00:23:51.421: INFO: Pod "pod-subpath-test-dynamicpv-p2jg": Phase="Pending", Reason="", readiness=false. Elapsed: 4.292454234s
Jun 14 00:23:53.518: INFO: Pod "pod-subpath-test-dynamicpv-p2jg": Phase="Pending", Reason="", readiness=false. Elapsed: 6.389708391s
Jun 14 00:23:55.625: INFO: Pod "pod-subpath-test-dynamicpv-p2jg": Phase="Pending", Reason="", readiness=false. Elapsed: 8.496439944s
Jun 14 00:23:57.722: INFO: Pod "pod-subpath-test-dynamicpv-p2jg": Phase="Pending", Reason="", readiness=false. Elapsed: 10.593507829s
Jun 14 00:23:59.819: INFO: Pod "pod-subpath-test-dynamicpv-p2jg": Phase="Pending", Reason="", readiness=false. Elapsed: 12.690753097s
Jun 14 00:24:01.916: INFO: Pod "pod-subpath-test-dynamicpv-p2jg": Phase="Pending", Reason="", readiness=false. Elapsed: 14.78831594s
Jun 14 00:24:04.014: INFO: Pod "pod-subpath-test-dynamicpv-p2jg": Phase="Pending", Reason="", readiness=false. Elapsed: 16.885691928s
Jun 14 00:24:06.111: INFO: Pod "pod-subpath-test-dynamicpv-p2jg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.982806546s
STEP: Saw pod success
Jun 14 00:24:06.111: INFO: Pod "pod-subpath-test-dynamicpv-p2jg" satisfied condition "Succeeded or Failed"
Jun 14 00:24:06.208: INFO: Trying to get logs from node ip-172-20-37-60.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-p2jg container test-container-subpath-dynamicpv-p2jg: <nil>
STEP: delete the pod
Jun 14 00:24:06.412: INFO: Waiting for pod pod-subpath-test-dynamicpv-p2jg to disappear
Jun 14 00:24:06.509: INFO: Pod pod-subpath-test-dynamicpv-p2jg no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-p2jg
Jun 14 00:24:06.509: INFO: Deleting pod "pod-subpath-test-dynamicpv-p2jg" in namespace "provisioning-1108"
STEP: Creating pod pod-subpath-test-dynamicpv-p2jg
STEP: Creating a pod to test subpath
Jun 14 00:24:06.702: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-p2jg" in namespace "provisioning-1108" to be "Succeeded or Failed"
Jun 14 00:24:06.802: INFO: Pod "pod-subpath-test-dynamicpv-p2jg": Phase="Pending", Reason="", readiness=false. Elapsed: 99.285162ms
Jun 14 00:24:08.900: INFO: Pod "pod-subpath-test-dynamicpv-p2jg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.197031881s
Jun 14 00:24:10.997: INFO: Pod "pod-subpath-test-dynamicpv-p2jg": Phase="Pending", Reason="", readiness=false. Elapsed: 4.294960422s
Jun 14 00:24:13.096: INFO: Pod "pod-subpath-test-dynamicpv-p2jg": Phase="Pending", Reason="", readiness=false. Elapsed: 6.393263443s
Jun 14 00:24:15.194: INFO: Pod "pod-subpath-test-dynamicpv-p2jg": Phase="Pending", Reason="", readiness=false. Elapsed: 8.49141538s
Jun 14 00:24:17.291: INFO: Pod "pod-subpath-test-dynamicpv-p2jg": Phase="Pending", Reason="", readiness=false. Elapsed: 10.588543554s
... skipping 21 lines ...
Jun 14 00:25:03.443: INFO: Pod "pod-subpath-test-dynamicpv-p2jg": Phase="Pending", Reason="", readiness=false. Elapsed: 56.740125372s
Jun 14 00:25:05.540: INFO: Pod "pod-subpath-test-dynamicpv-p2jg": Phase="Pending", Reason="", readiness=false. Elapsed: 58.837186323s
Jun 14 00:25:07.637: INFO: Pod "pod-subpath-test-dynamicpv-p2jg": Phase="Pending", Reason="", readiness=false. Elapsed: 1m0.934464529s
Jun 14 00:25:09.735: INFO: Pod "pod-subpath-test-dynamicpv-p2jg": Phase="Pending", Reason="", readiness=false. Elapsed: 1m3.032234907s
Jun 14 00:25:11.833: INFO: Pod "pod-subpath-test-dynamicpv-p2jg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m5.130213871s
STEP: Saw pod success
Jun 14 00:25:11.833: INFO: Pod "pod-subpath-test-dynamicpv-p2jg" satisfied condition "Succeeded or Failed"
Jun 14 00:25:11.934: INFO: Trying to get logs from node ip-172-20-60-182.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-p2jg container test-container-subpath-dynamicpv-p2jg: <nil>
STEP: delete the pod
Jun 14 00:25:12.139: INFO: Waiting for pod pod-subpath-test-dynamicpv-p2jg to disappear
Jun 14 00:25:12.235: INFO: Pod pod-subpath-test-dynamicpv-p2jg no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-p2jg
Jun 14 00:25:12.235: INFO: Deleting pod "pod-subpath-test-dynamicpv-p2jg" in namespace "provisioning-1108"
... skipping 95 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.FO5ImxMAG/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.FO5ImxMAG/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.FO5ImxMAG/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.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 98 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 14 00:24:47.677: 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.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun 14 00:24:48.164: INFO: Creating resource for dynamic PV
Jun 14 00:24:48.164: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1561-e2e-sc5lknp
STEP: creating a claim
Jun 14 00:24:48.263: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-l6xz
STEP: Checking for subpath error in container status
Jun 14 00:25:04.775: INFO: Deleting pod "pod-subpath-test-dynamicpv-l6xz" in namespace "provisioning-1561"
Jun 14 00:25:04.888: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-l6xz" to be fully deleted
STEP: Deleting pod
Jun 14 00:25:19.082: INFO: Deleting pod "pod-subpath-test-dynamicpv-l6xz" in namespace "provisioning-1561"
STEP: Deleting pvc
Jun 14 00:25:19.378: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.compp5j5"
... skipping 10 lines ...

• [SLOW TEST:42.390 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.FO5ImxMAG/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.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [sig-storage] Volume Placement [Feature:vsphere]
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 14 00:25:30.068: INFO: >>> kubeConfig: /root/.kube/config
... skipping 98 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.FO5ImxMAG/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.FO5ImxMAG/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.FO5ImxMAG/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.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Distro debian doesn't support ntfs -- skipping

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

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.FO5ImxMAG/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.FO5ImxMAG/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.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 260 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 14 00:25:03.514: 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.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun 14 00:25:03.997: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 14 00:25:03.997: INFO: Creating resource for dynamic PV
Jun 14 00:25:03.997: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5427cklc5
STEP: creating a claim
Jun 14 00:25:04.095: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-6k26
STEP: Checking for subpath error in container status
Jun 14 00:25:20.585: INFO: Deleting pod "pod-subpath-test-dynamicpv-6k26" in namespace "provisioning-5427"
Jun 14 00:25:20.688: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-6k26" to be fully deleted
STEP: Deleting pod
Jun 14 00:25:30.883: INFO: Deleting pod "pod-subpath-test-dynamicpv-6k26" in namespace "provisioning-5427"
STEP: Deleting pvc
Jun 14 00:25:31.173: INFO: Deleting PersistentVolumeClaim "aws2j8mj"
... skipping 13 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.FO5ImxMAG/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.FO5ImxMAG/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.FO5ImxMAG/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.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 14 00:25:46.957: INFO: Driver supports dynamic provisioning, skipping PreprovisionedPV pattern
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
... skipping 227 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 14 00:25:09.490: 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.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun 14 00:25:09.979: INFO: Creating resource for dynamic PV
Jun 14 00:25:09.979: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3765-e2e-sc4d57n
STEP: creating a claim
Jun 14 00:25:10.078: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-vf82
STEP: Checking for subpath error in container status
Jun 14 00:25:30.572: INFO: Deleting pod "pod-subpath-test-dynamicpv-vf82" in namespace "provisioning-3765"
Jun 14 00:25:30.673: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-vf82" to be fully deleted
STEP: Deleting pod
Jun 14 00:25:38.878: INFO: Deleting pod "pod-subpath-test-dynamicpv-vf82" in namespace "provisioning-3765"
STEP: Deleting pvc
Jun 14 00:25:39.169: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comk6lmb"
... skipping 11 lines ...

• [SLOW TEST:45.465 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath file is outside the volume [Slow][LinuxOnly]
    /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] volumeIO
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 14 00:25:54.956: INFO: Driver "ebs.csi.aws.com" does not support volume type "PreprovisionedPV" - skipping
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumeIO
... skipping 66 lines ...
Jun 14 00:25:23.734: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-3525-e2e-sc7f298
STEP: creating a claim
Jun 14 00:25:23.831: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Jun 14 00:25:24.028: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 14 00:25:24.223: INFO: Error updating pvc ebs.csi.aws.comct956: PersistentVolumeClaim "ebs.csi.aws.comct956" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3525-e2e-sc7f298",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.FO5ImxMAG/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.FO5ImxMAG/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.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 112 lines ...
Jun 14 00:22:13.272: INFO: Creating resource for dynamic PV
Jun 14 00:22:13.272: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-9584-e2e-scnnb72
STEP: creating a claim
Jun 14 00:22:13.371: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 14 00:22:13.665: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-6b5gd" in namespace "snapshotting-9584" to be "Succeeded or Failed"
Jun 14 00:22:13.762: INFO: Pod "pvc-snapshottable-tester-6b5gd": Phase="Pending", Reason="", readiness=false. Elapsed: 96.963592ms
Jun 14 00:22:15.860: INFO: Pod "pvc-snapshottable-tester-6b5gd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.194188921s
Jun 14 00:22:17.957: INFO: Pod "pvc-snapshottable-tester-6b5gd": Phase="Pending", Reason="", readiness=false. Elapsed: 4.291713452s
Jun 14 00:22:20.055: INFO: Pod "pvc-snapshottable-tester-6b5gd": Phase="Pending", Reason="", readiness=false. Elapsed: 6.389429492s
Jun 14 00:22:22.154: INFO: Pod "pvc-snapshottable-tester-6b5gd": Phase="Pending", Reason="", readiness=false. Elapsed: 8.488692989s
Jun 14 00:22:24.252: INFO: Pod "pvc-snapshottable-tester-6b5gd": Phase="Pending", Reason="", readiness=false. Elapsed: 10.586347896s
... skipping 2 lines ...
Jun 14 00:22:30.548: INFO: Pod "pvc-snapshottable-tester-6b5gd": Phase="Pending", Reason="", readiness=false. Elapsed: 16.882412136s
Jun 14 00:22:32.645: INFO: Pod "pvc-snapshottable-tester-6b5gd": Phase="Pending", Reason="", readiness=false. Elapsed: 18.97984182s
Jun 14 00:22:34.743: INFO: Pod "pvc-snapshottable-tester-6b5gd": Phase="Pending", Reason="", readiness=false. Elapsed: 21.077670779s
Jun 14 00:22:36.841: INFO: Pod "pvc-snapshottable-tester-6b5gd": Phase="Pending", Reason="", readiness=false. Elapsed: 23.175860687s
Jun 14 00:22:38.939: INFO: Pod "pvc-snapshottable-tester-6b5gd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 25.273893504s
STEP: Saw pod success
Jun 14 00:22:38.939: INFO: Pod "pvc-snapshottable-tester-6b5gd" satisfied condition "Succeeded or Failed"
Jun 14 00:22:39.640: INFO: Pod pvc-snapshottable-tester-6b5gd has the following logs: 
Jun 14 00:22:39.641: INFO: Deleting pod "pvc-snapshottable-tester-6b5gd" in namespace "snapshotting-9584"
Jun 14 00:22:39.745: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-6b5gd" to be fully deleted
Jun 14 00:22:39.846: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comkhhjv] to have phase Bound
Jun 14 00:22:39.943: INFO: PersistentVolumeClaim ebs.csi.aws.comkhhjv found and phase=Bound (97.633304ms)
STEP: [init] checking the claim
... skipping 41 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.FO5ImxMAG/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 14 00:23:46.110: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-jqsrm" in namespace "snapshotting-9584" to be "Succeeded or Failed"
Jun 14 00:23:46.208: INFO: Pod "pvc-snapshottable-data-tester-jqsrm": Phase="Pending", Reason="", readiness=false. Elapsed: 97.853366ms
Jun 14 00:23:48.306: INFO: Pod "pvc-snapshottable-data-tester-jqsrm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.196133866s
Jun 14 00:23:50.406: INFO: Pod "pvc-snapshottable-data-tester-jqsrm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.29519619s
Jun 14 00:23:52.504: INFO: Pod "pvc-snapshottable-data-tester-jqsrm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.393299135s
Jun 14 00:23:54.603: INFO: Pod "pvc-snapshottable-data-tester-jqsrm": Phase="Pending", Reason="", readiness=false. Elapsed: 8.492578379s
Jun 14 00:23:56.701: INFO: Pod "pvc-snapshottable-data-tester-jqsrm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.591084019s
STEP: Saw pod success
Jun 14 00:23:56.701: INFO: Pod "pvc-snapshottable-data-tester-jqsrm" satisfied condition "Succeeded or Failed"
Jun 14 00:23:56.906: INFO: Pod pvc-snapshottable-data-tester-jqsrm has the following logs: 
Jun 14 00:23:56.906: INFO: Deleting pod "pvc-snapshottable-data-tester-jqsrm" in namespace "snapshotting-9584"
Jun 14 00:23:57.007: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-jqsrm" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 14 00:24:35.495: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-9584 exec restored-pvc-tester-skmmn --namespace=snapshotting-9584 -- cat /mnt/test/data'
... skipping 31 lines ...
Jun 14 00:25:01.112: INFO: volumesnapshotcontents snapcontent-cc8af085-5ff5-40b5-b482-fee2527c4bbe has been found and is not deleted
Jun 14 00:25:02.211: INFO: volumesnapshotcontents snapcontent-cc8af085-5ff5-40b5-b482-fee2527c4bbe has been found and is not deleted
Jun 14 00:25:03.312: INFO: volumesnapshotcontents snapcontent-cc8af085-5ff5-40b5-b482-fee2527c4bbe has been found and is not deleted
Jun 14 00:25:04.411: INFO: volumesnapshotcontents snapcontent-cc8af085-5ff5-40b5-b482-fee2527c4bbe has been found and is not deleted
Jun 14 00:25:05.509: INFO: volumesnapshotcontents snapcontent-cc8af085-5ff5-40b5-b482-fee2527c4bbe has been found and is not deleted
Jun 14 00:25:06.607: INFO: volumesnapshotcontents snapcontent-cc8af085-5ff5-40b5-b482-fee2527c4bbe has been found and is not deleted
Jun 14 00:25:07.608: INFO: WaitUntil failed after reaching the timeout 30s
[AfterEach] volume snapshot controller
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:221
Jun 14 00:25:07.718: INFO: Pod restored-pvc-tester-skmmn has the following logs: 
Jun 14 00:25:07.718: INFO: Deleting pod "restored-pvc-tester-skmmn" in namespace "snapshotting-9584"
Jun 14 00:25:07.817: INFO: Wait up to 5m0s for pod "restored-pvc-tester-skmmn" to be fully deleted
Jun 14 00:25:50.022: INFO: deleting claim "snapshotting-9584"/"pvc-4lcpf"
... skipping 294 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.FO5ImxMAG/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.FO5ImxMAG/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.FO5ImxMAG/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.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 424 lines ...
Jun 14 00:25:11.615: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 14 00:25:12.307: INFO: Successfully created a new PD: "aws://eu-west-2a/vol-0dc870f9522923bcc".
Jun 14 00:25:12.307: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-tfbm
STEP: Creating a pod to test exec-volume-test
Jun 14 00:25:12.406: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-tfbm" in namespace "volume-8125" to be "Succeeded or Failed"
Jun 14 00:25:12.502: INFO: Pod "exec-volume-test-inlinevolume-tfbm": Phase="Pending", Reason="", readiness=false. Elapsed: 96.499267ms
Jun 14 00:25:14.599: INFO: Pod "exec-volume-test-inlinevolume-tfbm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.193244267s
Jun 14 00:25:16.696: INFO: Pod "exec-volume-test-inlinevolume-tfbm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.290138529s
Jun 14 00:25:18.793: INFO: Pod "exec-volume-test-inlinevolume-tfbm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.386912914s
Jun 14 00:25:20.892: INFO: Pod "exec-volume-test-inlinevolume-tfbm": Phase="Pending", Reason="", readiness=false. Elapsed: 8.486195632s
Jun 14 00:25:22.988: INFO: Pod "exec-volume-test-inlinevolume-tfbm": Phase="Pending", Reason="", readiness=false. Elapsed: 10.582530312s
... skipping 7 lines ...
Jun 14 00:25:39.764: INFO: Pod "exec-volume-test-inlinevolume-tfbm": Phase="Pending", Reason="", readiness=false. Elapsed: 27.358089896s
Jun 14 00:25:41.861: INFO: Pod "exec-volume-test-inlinevolume-tfbm": Phase="Pending", Reason="", readiness=false. Elapsed: 29.455512366s
Jun 14 00:25:43.959: INFO: Pod "exec-volume-test-inlinevolume-tfbm": Phase="Pending", Reason="", readiness=false. Elapsed: 31.552936053s
Jun 14 00:25:46.055: INFO: Pod "exec-volume-test-inlinevolume-tfbm": Phase="Pending", Reason="", readiness=false. Elapsed: 33.649408535s
Jun 14 00:25:48.152: INFO: Pod "exec-volume-test-inlinevolume-tfbm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 35.746427155s
STEP: Saw pod success
Jun 14 00:25:48.152: INFO: Pod "exec-volume-test-inlinevolume-tfbm" satisfied condition "Succeeded or Failed"
Jun 14 00:25:48.252: INFO: Trying to get logs from node ip-172-20-37-60.eu-west-2.compute.internal pod exec-volume-test-inlinevolume-tfbm container exec-container-inlinevolume-tfbm: <nil>
STEP: delete the pod
Jun 14 00:25:48.455: INFO: Waiting for pod exec-volume-test-inlinevolume-tfbm to disappear
Jun 14 00:25:48.551: INFO: Pod exec-volume-test-inlinevolume-tfbm no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-tfbm
Jun 14 00:25:48.551: INFO: Deleting pod "exec-volume-test-inlinevolume-tfbm" in namespace "volume-8125"
Jun 14 00:25:48.897: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0dc870f9522923bcc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0dc870f9522923bcc is currently attached to i-00b65c838fd755bcb
	status code: 400, request id: 330ee286-580a-405c-866b-a963e05faeb2
Jun 14 00:25:54.454: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0dc870f9522923bcc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0dc870f9522923bcc is currently attached to i-00b65c838fd755bcb
	status code: 400, request id: a51042ad-3a7c-4ec2-b2e4-25c9bf414993
Jun 14 00:25:59.976: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0dc870f9522923bcc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0dc870f9522923bcc is currently attached to i-00b65c838fd755bcb
	status code: 400, request id: 6541a3f5-1d01-4a91-b90e-4c9f66b0ca17
Jun 14 00:26:05.483: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0dc870f9522923bcc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0dc870f9522923bcc is currently attached to i-00b65c838fd755bcb
	status code: 400, request id: d70b0360-8683-42f2-a906-67b5730fdae9
Jun 14 00:26:11.085: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0dc870f9522923bcc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0dc870f9522923bcc is currently attached to i-00b65c838fd755bcb
	status code: 400, request id: 8bee8861-8c88-4df7-8699-3d198fd477c9
Jun 14 00:26:16.613: INFO: Successfully deleted PD "aws://eu-west-2a/vol-0dc870f9522923bcc".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 14 00:26:16.613: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8125" for this suite.
... skipping 14 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 14 00:25:38.545: 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.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 14 00:25:39.038: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 14 00:25:39.727: INFO: Successfully created a new PD: "aws://eu-west-2a/vol-09b749f8a05c85d05".
Jun 14 00:25:39.727: INFO: Creating resource for pre-provisioned PV
Jun 14 00:25:39.727: INFO: Creating PVC and PV
... skipping 5 lines ...
Jun 14 00:25:44.287: INFO: PersistentVolumeClaim pvc-sq7zg found but phase is Pending instead of Bound.
Jun 14 00:25:46.386: INFO: PersistentVolumeClaim pvc-sq7zg found but phase is Pending instead of Bound.
Jun 14 00:25:48.485: INFO: PersistentVolumeClaim pvc-sq7zg found and phase=Bound (8.49801794s)
Jun 14 00:25:48.485: INFO: Waiting up to 3m0s for PersistentVolume aws-tf7wc to have phase Bound
Jun 14 00:25:48.583: INFO: PersistentVolume aws-tf7wc found and phase=Bound (97.870041ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 14 00:25:51.190: INFO: Deleting pod "pod-5a15718f-d008-43bb-b7b0-9926d04d8d99" in namespace "volumemode-7335"
Jun 14 00:25:51.293: INFO: Wait up to 5m0s for pod "pod-5a15718f-d008-43bb-b7b0-9926d04d8d99" to be fully deleted
STEP: Deleting pv and pvc
Jun 14 00:26:01.489: INFO: Deleting PersistentVolumeClaim "pvc-sq7zg"
Jun 14 00:26:01.591: INFO: Deleting PersistentVolume "aws-tf7wc"
Jun 14 00:26:01.914: INFO: Couldn't delete PD "aws://eu-west-2a/vol-09b749f8a05c85d05", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-09b749f8a05c85d05 is currently attached to i-068ab7d6aa6e1db55
	status code: 400, request id: 5a274e47-6524-436a-b844-fb8a5e51b985
Jun 14 00:26:07.413: INFO: Couldn't delete PD "aws://eu-west-2a/vol-09b749f8a05c85d05", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-09b749f8a05c85d05 is currently attached to i-068ab7d6aa6e1db55
	status code: 400, request id: 5196ae06-6522-4160-b2a8-fe4a8a2bcae3
Jun 14 00:26:12.966: INFO: Couldn't delete PD "aws://eu-west-2a/vol-09b749f8a05c85d05", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-09b749f8a05c85d05 is currently attached to i-068ab7d6aa6e1db55
	status code: 400, request id: 61d1eda8-5010-4349-a8a8-bd0f6b0eb96d
Jun 14 00:26:18.499: INFO: Couldn't delete PD "aws://eu-west-2a/vol-09b749f8a05c85d05", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-09b749f8a05c85d05 is currently attached to i-068ab7d6aa6e1db55
	status code: 400, request id: 87c39df2-85a2-4659-a915-8013e20a36f7
Jun 14 00:26:24.045: INFO: Successfully deleted PD "aws://eu-west-2a/vol-09b749f8a05c85d05".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 14 00:26:24.045: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-7335" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.FO5ImxMAG/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.FO5ImxMAG/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
    /tmp/kops.FO5ImxMAG/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.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 6 lines ...
Jun 14 00:25:48.164: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 14 00:25:48.799: INFO: Successfully created a new PD: "aws://eu-west-2a/vol-03aef9d8aee28352a".
Jun 14 00:25:48.800: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-z5p6
STEP: Creating a pod to test exec-volume-test
Jun 14 00:25:48.906: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-z5p6" in namespace "volume-7824" to be "Succeeded or Failed"
Jun 14 00:25:49.003: INFO: Pod "exec-volume-test-inlinevolume-z5p6": Phase="Pending", Reason="", readiness=false. Elapsed: 96.61107ms
Jun 14 00:25:51.101: INFO: Pod "exec-volume-test-inlinevolume-z5p6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.194286247s
Jun 14 00:25:53.198: INFO: Pod "exec-volume-test-inlinevolume-z5p6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.29194828s
Jun 14 00:25:55.296: INFO: Pod "exec-volume-test-inlinevolume-z5p6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.389880665s
Jun 14 00:25:57.394: INFO: Pod "exec-volume-test-inlinevolume-z5p6": Phase="Pending", Reason="", readiness=false. Elapsed: 8.487839526s
Jun 14 00:25:59.492: INFO: Pod "exec-volume-test-inlinevolume-z5p6": Phase="Pending", Reason="", readiness=false. Elapsed: 10.585692156s
Jun 14 00:26:01.591: INFO: Pod "exec-volume-test-inlinevolume-z5p6": Phase="Pending", Reason="", readiness=false. Elapsed: 12.684610746s
Jun 14 00:26:03.688: INFO: Pod "exec-volume-test-inlinevolume-z5p6": Phase="Pending", Reason="", readiness=false. Elapsed: 14.78199225s
Jun 14 00:26:05.787: INFO: Pod "exec-volume-test-inlinevolume-z5p6": Phase="Pending", Reason="", readiness=false. Elapsed: 16.880225465s
Jun 14 00:26:07.883: INFO: Pod "exec-volume-test-inlinevolume-z5p6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.977167958s
STEP: Saw pod success
Jun 14 00:26:07.884: INFO: Pod "exec-volume-test-inlinevolume-z5p6" satisfied condition "Succeeded or Failed"
Jun 14 00:26:07.980: INFO: Trying to get logs from node ip-172-20-37-60.eu-west-2.compute.internal pod exec-volume-test-inlinevolume-z5p6 container exec-container-inlinevolume-z5p6: <nil>
STEP: delete the pod
Jun 14 00:26:08.183: INFO: Waiting for pod exec-volume-test-inlinevolume-z5p6 to disappear
Jun 14 00:26:08.280: INFO: Pod exec-volume-test-inlinevolume-z5p6 no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-z5p6
Jun 14 00:26:08.280: INFO: Deleting pod "exec-volume-test-inlinevolume-z5p6" in namespace "volume-7824"
Jun 14 00:26:08.615: INFO: Couldn't delete PD "aws://eu-west-2a/vol-03aef9d8aee28352a", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-03aef9d8aee28352a is currently attached to i-00b65c838fd755bcb
	status code: 400, request id: 23f259a6-ce6f-45e2-a521-9305a4b6a9ad
Jun 14 00:26:14.153: INFO: Couldn't delete PD "aws://eu-west-2a/vol-03aef9d8aee28352a", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-03aef9d8aee28352a is currently attached to i-00b65c838fd755bcb
	status code: 400, request id: b92a2d00-7621-4e9d-8ea0-3391b3881ce9
Jun 14 00:26:19.715: INFO: Couldn't delete PD "aws://eu-west-2a/vol-03aef9d8aee28352a", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-03aef9d8aee28352a is currently attached to i-00b65c838fd755bcb
	status code: 400, request id: af3f0cd1-2ea9-41c4-874d-e5803046c7bd
Jun 14 00:26:25.323: INFO: Successfully deleted PD "aws://eu-west-2a/vol-03aef9d8aee28352a".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 14 00:26:25.323: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-7824" for this suite.
... skipping 204 lines ...
Jun 14 00:25:31.252: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-142w957n
STEP: creating a claim
Jun 14 00:25:31.350: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-f2nk
STEP: Creating a pod to test subpath
Jun 14 00:25:31.648: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-f2nk" in namespace "provisioning-142" to be "Succeeded or Failed"
Jun 14 00:25:31.745: INFO: Pod "pod-subpath-test-dynamicpv-f2nk": Phase="Pending", Reason="", readiness=false. Elapsed: 97.00497ms
Jun 14 00:25:33.845: INFO: Pod "pod-subpath-test-dynamicpv-f2nk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.196575299s
Jun 14 00:25:35.942: INFO: Pod "pod-subpath-test-dynamicpv-f2nk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.294301233s
Jun 14 00:25:38.040: INFO: Pod "pod-subpath-test-dynamicpv-f2nk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.3917452s
Jun 14 00:25:40.138: INFO: Pod "pod-subpath-test-dynamicpv-f2nk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.48951845s
Jun 14 00:25:42.236: INFO: Pod "pod-subpath-test-dynamicpv-f2nk": Phase="Pending", Reason="", readiness=false. Elapsed: 10.588058493s
... skipping 9 lines ...
Jun 14 00:26:03.224: INFO: Pod "pod-subpath-test-dynamicpv-f2nk": Phase="Pending", Reason="", readiness=false. Elapsed: 31.575754345s
Jun 14 00:26:05.322: INFO: Pod "pod-subpath-test-dynamicpv-f2nk": Phase="Pending", Reason="", readiness=false. Elapsed: 33.674182827s
Jun 14 00:26:07.425: INFO: Pod "pod-subpath-test-dynamicpv-f2nk": Phase="Pending", Reason="", readiness=false. Elapsed: 35.776543248s
Jun 14 00:26:09.522: INFO: Pod "pod-subpath-test-dynamicpv-f2nk": Phase="Pending", Reason="", readiness=false. Elapsed: 37.874238228s
Jun 14 00:26:11.619: INFO: Pod "pod-subpath-test-dynamicpv-f2nk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 39.971353274s
STEP: Saw pod success
Jun 14 00:26:11.620: INFO: Pod "pod-subpath-test-dynamicpv-f2nk" satisfied condition "Succeeded or Failed"
Jun 14 00:26:11.717: INFO: Trying to get logs from node ip-172-20-62-170.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-f2nk container test-container-volume-dynamicpv-f2nk: <nil>
STEP: delete the pod
Jun 14 00:26:11.930: INFO: Waiting for pod pod-subpath-test-dynamicpv-f2nk to disappear
Jun 14 00:26:12.026: INFO: Pod pod-subpath-test-dynamicpv-f2nk no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-f2nk
Jun 14 00:26:12.026: INFO: Deleting pod "pod-subpath-test-dynamicpv-f2nk" in namespace "provisioning-142"
... skipping 80 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.FO5ImxMAG/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.FO5ImxMAG/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.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 346 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 14 00:25:45.111: 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.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun 14 00:25:45.602: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 14 00:25:45.602: INFO: Creating resource for dynamic PV
Jun 14 00:25:45.602: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3324m8vnb
STEP: creating a claim
Jun 14 00:25:45.700: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-k4bj
STEP: Checking for subpath error in container status
Jun 14 00:26:26.198: INFO: Deleting pod "pod-subpath-test-dynamicpv-k4bj" in namespace "provisioning-3324"
Jun 14 00:26:26.300: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-k4bj" to be fully deleted
STEP: Deleting pod
Jun 14 00:26:38.497: INFO: Deleting pod "pod-subpath-test-dynamicpv-k4bj" in namespace "provisioning-3324"
STEP: Deleting pvc
Jun 14 00:26:38.791: INFO: Deleting PersistentVolumeClaim "awslzcg6"
... skipping 11 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.FO5ImxMAG/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.FO5ImxMAG/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath directory is outside the volume [Slow][LinuxOnly]
      /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 14 00:26:44.397: INFO: Driver ebs.csi.aws.com doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning
... skipping 396 lines ...
Jun 14 00:26:16.380: INFO: PersistentVolumeClaim pvc-25jz6 found but phase is Pending instead of Bound.
Jun 14 00:26:18.485: INFO: PersistentVolumeClaim pvc-25jz6 found and phase=Bound (10.593435339s)
Jun 14 00:26:18.485: INFO: Waiting up to 3m0s for PersistentVolume aws-8mfhw to have phase Bound
Jun 14 00:26:18.583: INFO: PersistentVolume aws-8mfhw found and phase=Bound (97.758635ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-wr8f
STEP: Creating a pod to test exec-volume-test
Jun 14 00:26:18.878: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-wr8f" in namespace "volume-7428" to be "Succeeded or Failed"
Jun 14 00:26:18.974: INFO: Pod "exec-volume-test-preprovisionedpv-wr8f": Phase="Pending", Reason="", readiness=false. Elapsed: 96.836546ms
Jun 14 00:26:21.072: INFO: Pod "exec-volume-test-preprovisionedpv-wr8f": Phase="Pending", Reason="", readiness=false. Elapsed: 2.194323348s
Jun 14 00:26:23.177: INFO: Pod "exec-volume-test-preprovisionedpv-wr8f": Phase="Pending", Reason="", readiness=false. Elapsed: 4.29941492s
Jun 14 00:26:25.276: INFO: Pod "exec-volume-test-preprovisionedpv-wr8f": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.398337328s
STEP: Saw pod success
Jun 14 00:26:25.276: INFO: Pod "exec-volume-test-preprovisionedpv-wr8f" satisfied condition "Succeeded or Failed"
Jun 14 00:26:25.375: INFO: Trying to get logs from node ip-172-20-34-37.eu-west-2.compute.internal pod exec-volume-test-preprovisionedpv-wr8f container exec-container-preprovisionedpv-wr8f: <nil>
STEP: delete the pod
Jun 14 00:26:25.577: INFO: Waiting for pod exec-volume-test-preprovisionedpv-wr8f to disappear
Jun 14 00:26:25.674: INFO: Pod exec-volume-test-preprovisionedpv-wr8f no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-wr8f
Jun 14 00:26:25.674: INFO: Deleting pod "exec-volume-test-preprovisionedpv-wr8f" in namespace "volume-7428"
STEP: Deleting pv and pvc
Jun 14 00:26:25.771: INFO: Deleting PersistentVolumeClaim "pvc-25jz6"
Jun 14 00:26:25.883: INFO: Deleting PersistentVolume "aws-8mfhw"
Jun 14 00:26:26.193: INFO: Couldn't delete PD "aws://eu-west-2a/vol-01eba446ec7f4f57f", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01eba446ec7f4f57f is currently attached to i-0e1bbe360340e9289
	status code: 400, request id: 7448612e-d33f-4920-891d-5407a87436c8
Jun 14 00:26:31.737: INFO: Couldn't delete PD "aws://eu-west-2a/vol-01eba446ec7f4f57f", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01eba446ec7f4f57f is currently attached to i-0e1bbe360340e9289
	status code: 400, request id: 52f70c1d-451e-4f95-aeda-f61c850507bc
Jun 14 00:26:37.230: INFO: Couldn't delete PD "aws://eu-west-2a/vol-01eba446ec7f4f57f", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01eba446ec7f4f57f is currently attached to i-0e1bbe360340e9289
	status code: 400, request id: 6996f3b3-77a9-4c45-bb70-db8aba2d758f
Jun 14 00:26:42.738: INFO: Couldn't delete PD "aws://eu-west-2a/vol-01eba446ec7f4f57f", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01eba446ec7f4f57f is currently attached to i-0e1bbe360340e9289
	status code: 400, request id: d0d14c26-e9cb-4278-b6b0-2815dca804da
Jun 14 00:26:48.277: INFO: Couldn't delete PD "aws://eu-west-2a/vol-01eba446ec7f4f57f", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01eba446ec7f4f57f is currently attached to i-0e1bbe360340e9289
	status code: 400, request id: a970788a-3ccc-4130-b5f2-a48077a875d2
Jun 14 00:26:53.784: INFO: Couldn't delete PD "aws://eu-west-2a/vol-01eba446ec7f4f57f", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01eba446ec7f4f57f is currently attached to i-0e1bbe360340e9289
	status code: 400, request id: 3e71aaca-3656-4e0c-b888-01211d1fba24
Jun 14 00:26:59.326: INFO: Successfully deleted PD "aws://eu-west-2a/vol-01eba446ec7f4f57f".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 14 00:26:59.326: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-7428" for this suite.
... skipping 117 lines ...
Jun 14 00:25:58.198: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-4179-e2e-scczsmh
STEP: creating a claim
Jun 14 00:25:58.296: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-ksqg
STEP: Creating a pod to test exec-volume-test
Jun 14 00:25:58.591: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-ksqg" in namespace "volume-4179" to be "Succeeded or Failed"
Jun 14 00:25:58.689: INFO: Pod "exec-volume-test-dynamicpv-ksqg": Phase="Pending", Reason="", readiness=false. Elapsed: 97.361037ms
Jun 14 00:26:00.787: INFO: Pod "exec-volume-test-dynamicpv-ksqg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.195473048s
Jun 14 00:26:02.885: INFO: Pod "exec-volume-test-dynamicpv-ksqg": Phase="Pending", Reason="", readiness=false. Elapsed: 4.293741394s
Jun 14 00:26:04.984: INFO: Pod "exec-volume-test-dynamicpv-ksqg": Phase="Pending", Reason="", readiness=false. Elapsed: 6.392197029s
Jun 14 00:26:07.082: INFO: Pod "exec-volume-test-dynamicpv-ksqg": Phase="Pending", Reason="", readiness=false. Elapsed: 8.490672745s
Jun 14 00:26:09.180: INFO: Pod "exec-volume-test-dynamicpv-ksqg": Phase="Pending", Reason="", readiness=false. Elapsed: 10.58814144s
... skipping 2 lines ...
Jun 14 00:26:15.474: INFO: Pod "exec-volume-test-dynamicpv-ksqg": Phase="Pending", Reason="", readiness=false. Elapsed: 16.88293596s
Jun 14 00:26:17.572: INFO: Pod "exec-volume-test-dynamicpv-ksqg": Phase="Pending", Reason="", readiness=false. Elapsed: 18.980423972s
Jun 14 00:26:19.670: INFO: Pod "exec-volume-test-dynamicpv-ksqg": Phase="Pending", Reason="", readiness=false. Elapsed: 21.078378426s
Jun 14 00:26:21.768: INFO: Pod "exec-volume-test-dynamicpv-ksqg": Phase="Pending", Reason="", readiness=false. Elapsed: 23.176206103s
Jun 14 00:26:23.867: INFO: Pod "exec-volume-test-dynamicpv-ksqg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 25.275265914s
STEP: Saw pod success
Jun 14 00:26:23.867: INFO: Pod "exec-volume-test-dynamicpv-ksqg" satisfied condition "Succeeded or Failed"
Jun 14 00:26:23.964: INFO: Trying to get logs from node ip-172-20-34-37.eu-west-2.compute.internal pod exec-volume-test-dynamicpv-ksqg container exec-container-dynamicpv-ksqg: <nil>
STEP: delete the pod
Jun 14 00:26:24.172: INFO: Waiting for pod exec-volume-test-dynamicpv-ksqg to disappear
Jun 14 00:26:24.269: INFO: Pod exec-volume-test-dynamicpv-ksqg no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-ksqg
Jun 14 00:26:24.269: INFO: Deleting pod "exec-volume-test-dynamicpv-ksqg" in namespace "volume-4179"
... skipping 221 lines ...
Jun 14 00:26:17.300: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4586hqdfv
STEP: creating a claim
Jun 14 00:26:17.398: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-jszj
STEP: Creating a pod to test subpath
Jun 14 00:26:17.689: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-jszj" in namespace "provisioning-4586" to be "Succeeded or Failed"
Jun 14 00:26:17.785: INFO: Pod "pod-subpath-test-dynamicpv-jszj": Phase="Pending", Reason="", readiness=false. Elapsed: 96.103213ms
Jun 14 00:26:19.882: INFO: Pod "pod-subpath-test-dynamicpv-jszj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.193065259s
Jun 14 00:26:21.980: INFO: Pod "pod-subpath-test-dynamicpv-jszj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.291038149s
Jun 14 00:26:24.078: INFO: Pod "pod-subpath-test-dynamicpv-jszj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.389213709s
Jun 14 00:26:26.175: INFO: Pod "pod-subpath-test-dynamicpv-jszj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.486606906s
Jun 14 00:26:28.272: INFO: Pod "pod-subpath-test-dynamicpv-jszj": Phase="Pending", Reason="", readiness=false. Elapsed: 10.583317587s
... skipping 2 lines ...
Jun 14 00:26:34.569: INFO: Pod "pod-subpath-test-dynamicpv-jszj": Phase="Pending", Reason="", readiness=false. Elapsed: 16.880501413s
Jun 14 00:26:36.666: INFO: Pod "pod-subpath-test-dynamicpv-jszj": Phase="Pending", Reason="", readiness=false. Elapsed: 18.977223516s
Jun 14 00:26:38.765: INFO: Pod "pod-subpath-test-dynamicpv-jszj": Phase="Pending", Reason="", readiness=false. Elapsed: 21.076569356s
Jun 14 00:26:40.863: INFO: Pod "pod-subpath-test-dynamicpv-jszj": Phase="Pending", Reason="", readiness=false. Elapsed: 23.174154783s
Jun 14 00:26:42.960: INFO: Pod "pod-subpath-test-dynamicpv-jszj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 25.271411567s
STEP: Saw pod success
Jun 14 00:26:42.960: INFO: Pod "pod-subpath-test-dynamicpv-jszj" satisfied condition "Succeeded or Failed"
Jun 14 00:26:43.056: INFO: Trying to get logs from node ip-172-20-60-182.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-jszj container test-container-subpath-dynamicpv-jszj: <nil>
STEP: delete the pod
Jun 14 00:26:43.261: INFO: Waiting for pod pod-subpath-test-dynamicpv-jszj to disappear
Jun 14 00:26:43.358: INFO: Pod pod-subpath-test-dynamicpv-jszj no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-jszj
Jun 14 00:26:43.358: INFO: Deleting pod "pod-subpath-test-dynamicpv-jszj" in namespace "provisioning-4586"
STEP: Creating pod pod-subpath-test-dynamicpv-jszj
STEP: Creating a pod to test subpath
Jun 14 00:26:43.551: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-jszj" in namespace "provisioning-4586" to be "Succeeded or Failed"
Jun 14 00:26:43.647: INFO: Pod "pod-subpath-test-dynamicpv-jszj": Phase="Pending", Reason="", readiness=false. Elapsed: 95.967104ms
Jun 14 00:26:45.744: INFO: Pod "pod-subpath-test-dynamicpv-jszj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.19274029s
Jun 14 00:26:47.840: INFO: Pod "pod-subpath-test-dynamicpv-jszj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.288924313s
Jun 14 00:26:49.936: INFO: Pod "pod-subpath-test-dynamicpv-jszj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.385678039s
Jun 14 00:26:52.038: INFO: Pod "pod-subpath-test-dynamicpv-jszj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.486937907s
Jun 14 00:26:54.135: INFO: Pod "pod-subpath-test-dynamicpv-jszj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.584232251s
STEP: Saw pod success
Jun 14 00:26:54.135: INFO: Pod "pod-subpath-test-dynamicpv-jszj" satisfied condition "Succeeded or Failed"
Jun 14 00:26:54.232: INFO: Trying to get logs from node ip-172-20-60-182.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-jszj container test-container-subpath-dynamicpv-jszj: <nil>
STEP: delete the pod
Jun 14 00:26:54.449: INFO: Waiting for pod pod-subpath-test-dynamicpv-jszj to disappear
Jun 14 00:26:54.545: INFO: Pod pod-subpath-test-dynamicpv-jszj no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-jszj
Jun 14 00:26:54.545: INFO: Deleting pod "pod-subpath-test-dynamicpv-jszj" in namespace "provisioning-4586"
... skipping 118 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.FO5ImxMAG/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.FO5ImxMAG/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.FO5ImxMAG/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.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 771 lines ...
Jun 14 00:23:43.011: INFO: Creating resource for dynamic PV
Jun 14 00:23:43.011: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-5211-e2e-sc6tzvg
STEP: creating a claim
Jun 14 00:23:43.109: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 14 00:23:43.402: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-xvjbg" in namespace "snapshotting-5211" to be "Succeeded or Failed"
Jun 14 00:23:43.500: INFO: Pod "pvc-snapshottable-tester-xvjbg": Phase="Pending", Reason="", readiness=false. Elapsed: 97.093635ms
Jun 14 00:23:45.596: INFO: Pod "pvc-snapshottable-tester-xvjbg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.193970841s
Jun 14 00:23:47.695: INFO: Pod "pvc-snapshottable-tester-xvjbg": Phase="Pending", Reason="", readiness=false. Elapsed: 4.292915224s
Jun 14 00:23:49.793: INFO: Pod "pvc-snapshottable-tester-xvjbg": Phase="Pending", Reason="", readiness=false. Elapsed: 6.390841146s
Jun 14 00:23:51.893: INFO: Pod "pvc-snapshottable-tester-xvjbg": Phase="Pending", Reason="", readiness=false. Elapsed: 8.490546809s
Jun 14 00:23:53.990: INFO: Pod "pvc-snapshottable-tester-xvjbg": Phase="Pending", Reason="", readiness=false. Elapsed: 10.587102686s
Jun 14 00:23:56.086: INFO: Pod "pvc-snapshottable-tester-xvjbg": Phase="Pending", Reason="", readiness=false. Elapsed: 12.68357592s
Jun 14 00:23:58.182: INFO: Pod "pvc-snapshottable-tester-xvjbg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.780009255s
STEP: Saw pod success
Jun 14 00:23:58.182: INFO: Pod "pvc-snapshottable-tester-xvjbg" satisfied condition "Succeeded or Failed"
Jun 14 00:23:58.382: INFO: Pod pvc-snapshottable-tester-xvjbg has the following logs: 
Jun 14 00:23:58.382: INFO: Deleting pod "pvc-snapshottable-tester-xvjbg" in namespace "snapshotting-5211"
Jun 14 00:23:58.484: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-xvjbg" to be fully deleted
Jun 14 00:23:58.580: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comjp6v2] to have phase Bound
Jun 14 00:23:58.676: INFO: PersistentVolumeClaim ebs.csi.aws.comjp6v2 found and phase=Bound (95.987742ms)
STEP: [init] checking the claim
... skipping 47 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.FO5ImxMAG/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 14 00:24:40.602: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-xhm9r" in namespace "snapshotting-5211" to be "Succeeded or Failed"
Jun 14 00:24:40.698: INFO: Pod "pvc-snapshottable-data-tester-xhm9r": Phase="Pending", Reason="", readiness=false. Elapsed: 96.163728ms
Jun 14 00:24:42.796: INFO: Pod "pvc-snapshottable-data-tester-xhm9r": Phase="Pending", Reason="", readiness=false. Elapsed: 2.193705709s
Jun 14 00:24:44.893: INFO: Pod "pvc-snapshottable-data-tester-xhm9r": Phase="Pending", Reason="", readiness=false. Elapsed: 4.290707655s
Jun 14 00:24:46.990: INFO: Pod "pvc-snapshottable-data-tester-xhm9r": Phase="Pending", Reason="", readiness=false. Elapsed: 6.388139704s
Jun 14 00:24:49.087: INFO: Pod "pvc-snapshottable-data-tester-xhm9r": Phase="Pending", Reason="", readiness=false. Elapsed: 8.484649487s
Jun 14 00:24:51.184: INFO: Pod "pvc-snapshottable-data-tester-xhm9r": Phase="Pending", Reason="", readiness=false. Elapsed: 10.582377366s
... skipping 21 lines ...
Jun 14 00:25:37.322: INFO: Pod "pvc-snapshottable-data-tester-xhm9r": Phase="Pending", Reason="", readiness=false. Elapsed: 56.719708414s
Jun 14 00:25:39.419: INFO: Pod "pvc-snapshottable-data-tester-xhm9r": Phase="Pending", Reason="", readiness=false. Elapsed: 58.817330046s
Jun 14 00:25:41.516: INFO: Pod "pvc-snapshottable-data-tester-xhm9r": Phase="Pending", Reason="", readiness=false. Elapsed: 1m0.914247477s
Jun 14 00:25:43.616: INFO: Pod "pvc-snapshottable-data-tester-xhm9r": Phase="Pending", Reason="", readiness=false. Elapsed: 1m3.013780691s
Jun 14 00:25:45.714: INFO: Pod "pvc-snapshottable-data-tester-xhm9r": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m5.111661527s
STEP: Saw pod success
Jun 14 00:25:45.714: INFO: Pod "pvc-snapshottable-data-tester-xhm9r" satisfied condition "Succeeded or Failed"
Jun 14 00:25:45.908: INFO: Pod pvc-snapshottable-data-tester-xhm9r has the following logs: 
Jun 14 00:25:45.908: INFO: Deleting pod "pvc-snapshottable-data-tester-xhm9r" in namespace "snapshotting-5211"
Jun 14 00:25:46.014: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-xhm9r" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 14 00:26:08.509: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-5211 exec restored-pvc-tester-btrp4 --namespace=snapshotting-5211 -- cat /mnt/test/data'
... skipping 31 lines ...
Jun 14 00:26:34.086: INFO: volumesnapshotcontents pre-provisioned-snapcontent-453600f8-31ab-4fb7-9f92-c42ac1e7423f has been found and is not deleted
Jun 14 00:26:35.185: INFO: volumesnapshotcontents pre-provisioned-snapcontent-453600f8-31ab-4fb7-9f92-c42ac1e7423f has been found and is not deleted
Jun 14 00:26:36.282: INFO: volumesnapshotcontents pre-provisioned-snapcontent-453600f8-31ab-4fb7-9f92-c42ac1e7423f has been found and is not deleted
Jun 14 00:26:37.380: INFO: volumesnapshotcontents pre-provisioned-snapcontent-453600f8-31ab-4fb7-9f92-c42ac1e7423f has been found and is not deleted
Jun 14 00:26:38.477: INFO: volumesnapshotcontents pre-provisioned-snapcontent-453600f8-31ab-4fb7-9f92-c42ac1e7423f has been found and is not deleted
Jun 14 00:26:39.574: INFO: volumesnapshotcontents pre-provisioned-snapcontent-453600f8-31ab-4fb7-9f92-c42ac1e7423f has been found and is not deleted
Jun 14 00:26:40.574: INFO: WaitUntil failed after reaching the timeout 30s
[AfterEach] volume snapshot controller
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:221
Jun 14 00:26:40.672: INFO: Pod restored-pvc-tester-btrp4 has the following logs: 
Jun 14 00:26:40.672: INFO: Deleting pod "restored-pvc-tester-btrp4" in namespace "snapshotting-5211"
Jun 14 00:26:40.769: INFO: Wait up to 5m0s for pod "restored-pvc-tester-btrp4" to be fully deleted
Jun 14 00:27:18.963: INFO: deleting claim "snapshotting-5211"/"pvc-p2kfp"
... skipping 194 lines ...
Jun 14 00:26:44.893: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-2186-e2e-sc95hkt
STEP: creating a claim
Jun 14 00:26:44.992: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-2j6k
STEP: Creating a pod to test exec-volume-test
Jun 14 00:26:45.289: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-2j6k" in namespace "volume-2186" to be "Succeeded or Failed"
Jun 14 00:26:45.396: INFO: Pod "exec-volume-test-dynamicpv-2j6k": Phase="Pending", Reason="", readiness=false. Elapsed: 106.476467ms
Jun 14 00:26:47.494: INFO: Pod "exec-volume-test-dynamicpv-2j6k": Phase="Pending", Reason="", readiness=false. Elapsed: 2.204886225s
Jun 14 00:26:49.596: INFO: Pod "exec-volume-test-dynamicpv-2j6k": Phase="Pending", Reason="", readiness=false. Elapsed: 4.306154557s
Jun 14 00:26:51.694: INFO: Pod "exec-volume-test-dynamicpv-2j6k": Phase="Pending", Reason="", readiness=false. Elapsed: 6.404513751s
Jun 14 00:26:53.797: INFO: Pod "exec-volume-test-dynamicpv-2j6k": Phase="Pending", Reason="", readiness=false. Elapsed: 8.507888751s
Jun 14 00:26:55.897: INFO: Pod "exec-volume-test-dynamicpv-2j6k": Phase="Pending", Reason="", readiness=false. Elapsed: 10.60740894s
Jun 14 00:26:57.995: INFO: Pod "exec-volume-test-dynamicpv-2j6k": Phase="Pending", Reason="", readiness=false. Elapsed: 12.705867007s
Jun 14 00:27:00.094: INFO: Pod "exec-volume-test-dynamicpv-2j6k": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.804572775s
STEP: Saw pod success
Jun 14 00:27:00.094: INFO: Pod "exec-volume-test-dynamicpv-2j6k" satisfied condition "Succeeded or Failed"
Jun 14 00:27:00.199: INFO: Trying to get logs from node ip-172-20-60-182.eu-west-2.compute.internal pod exec-volume-test-dynamicpv-2j6k container exec-container-dynamicpv-2j6k: <nil>
STEP: delete the pod
Jun 14 00:27:00.436: INFO: Waiting for pod exec-volume-test-dynamicpv-2j6k to disappear
Jun 14 00:27:00.534: INFO: Pod exec-volume-test-dynamicpv-2j6k no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-2j6k
Jun 14 00:27:00.534: INFO: Deleting pod "exec-volume-test-dynamicpv-2j6k" in namespace "volume-2186"
... skipping 103 lines ...
Jun 14 00:25:11.352: INFO: Creating resource for dynamic PV
Jun 14 00:25:11.352: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-6380-e2e-scknknv
STEP: creating a claim
Jun 14 00:25:11.450: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 14 00:25:11.744: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-kszz2" in namespace "snapshotting-6380" to be "Succeeded or Failed"
Jun 14 00:25:11.841: INFO: Pod "pvc-snapshottable-tester-kszz2": Phase="Pending", Reason="", readiness=false. Elapsed: 97.168326ms
Jun 14 00:25:13.939: INFO: Pod "pvc-snapshottable-tester-kszz2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.195032971s
Jun 14 00:25:16.037: INFO: Pod "pvc-snapshottable-tester-kszz2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.292841867s
Jun 14 00:25:18.134: INFO: Pod "pvc-snapshottable-tester-kszz2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.390581676s
Jun 14 00:25:20.233: INFO: Pod "pvc-snapshottable-tester-kszz2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.488677803s
Jun 14 00:25:22.332: INFO: Pod "pvc-snapshottable-tester-kszz2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.587802512s
... skipping 6 lines ...
Jun 14 00:25:37.020: INFO: Pod "pvc-snapshottable-tester-kszz2": Phase="Pending", Reason="", readiness=false. Elapsed: 25.275695521s
Jun 14 00:25:39.118: INFO: Pod "pvc-snapshottable-tester-kszz2": Phase="Pending", Reason="", readiness=false. Elapsed: 27.374191243s
Jun 14 00:25:41.216: INFO: Pod "pvc-snapshottable-tester-kszz2": Phase="Pending", Reason="", readiness=false. Elapsed: 29.471872936s
Jun 14 00:25:43.314: INFO: Pod "pvc-snapshottable-tester-kszz2": Phase="Pending", Reason="", readiness=false. Elapsed: 31.570169669s
Jun 14 00:25:45.412: INFO: Pod "pvc-snapshottable-tester-kszz2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 33.667653141s
STEP: Saw pod success
Jun 14 00:25:45.412: INFO: Pod "pvc-snapshottable-tester-kszz2" satisfied condition "Succeeded or Failed"
Jun 14 00:25:45.608: INFO: Pod pvc-snapshottable-tester-kszz2 has the following logs: 
Jun 14 00:25:45.608: INFO: Deleting pod "pvc-snapshottable-tester-kszz2" in namespace "snapshotting-6380"
Jun 14 00:25:45.711: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-kszz2" to be fully deleted
Jun 14 00:25:45.809: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comvkg8z] to have phase Bound
Jun 14 00:25:45.906: INFO: PersistentVolumeClaim ebs.csi.aws.comvkg8z found and phase=Bound (97.00737ms)
STEP: [init] checking the claim
... skipping 17 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.FO5ImxMAG/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 14 00:26:01.710: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-chgdm" in namespace "snapshotting-6380" to be "Succeeded or Failed"
Jun 14 00:26:01.807: INFO: Pod "pvc-snapshottable-data-tester-chgdm": Phase="Pending", Reason="", readiness=false. Elapsed: 97.4049ms
Jun 14 00:26:03.911: INFO: Pod "pvc-snapshottable-data-tester-chgdm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.201347313s
Jun 14 00:26:06.010: INFO: Pod "pvc-snapshottable-data-tester-chgdm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.299879181s
Jun 14 00:26:08.107: INFO: Pod "pvc-snapshottable-data-tester-chgdm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.397522715s
Jun 14 00:26:10.206: INFO: Pod "pvc-snapshottable-data-tester-chgdm": Phase="Pending", Reason="", readiness=false. Elapsed: 8.496232705s
Jun 14 00:26:12.305: INFO: Pod "pvc-snapshottable-data-tester-chgdm": Phase="Pending", Reason="", readiness=false. Elapsed: 10.595273993s
... skipping 6 lines ...
Jun 14 00:26:26.991: INFO: Pod "pvc-snapshottable-data-tester-chgdm": Phase="Pending", Reason="", readiness=false. Elapsed: 25.281474696s
Jun 14 00:26:29.089: INFO: Pod "pvc-snapshottable-data-tester-chgdm": Phase="Pending", Reason="", readiness=false. Elapsed: 27.37955902s
Jun 14 00:26:31.189: INFO: Pod "pvc-snapshottable-data-tester-chgdm": Phase="Pending", Reason="", readiness=false. Elapsed: 29.479262423s
Jun 14 00:26:33.287: INFO: Pod "pvc-snapshottable-data-tester-chgdm": Phase="Pending", Reason="", readiness=false. Elapsed: 31.576977874s
Jun 14 00:26:35.389: INFO: Pod "pvc-snapshottable-data-tester-chgdm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 33.679386413s
STEP: Saw pod success
Jun 14 00:26:35.389: INFO: Pod "pvc-snapshottable-data-tester-chgdm" satisfied condition "Succeeded or Failed"
Jun 14 00:26:35.590: INFO: Pod pvc-snapshottable-data-tester-chgdm has the following logs: 
Jun 14 00:26:35.590: INFO: Deleting pod "pvc-snapshottable-data-tester-chgdm" in namespace "snapshotting-6380"
Jun 14 00:26:35.694: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-chgdm" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 14 00:26:50.205: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-6380 exec restored-pvc-tester-8v6pr --namespace=snapshotting-6380 -- cat /mnt/test/data'
... skipping 49 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 14 00:27:00.322: 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.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun 14 00:27:00.842: INFO: Creating resource for dynamic PV
Jun 14 00:27:00.842: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3857-e2e-sccpwmk
STEP: creating a claim
Jun 14 00:27:00.944: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-gnrk
STEP: Checking for subpath error in container status
Jun 14 00:27:17.435: INFO: Deleting pod "pod-subpath-test-dynamicpv-gnrk" in namespace "provisioning-3857"
Jun 14 00:27:17.532: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-gnrk" to be fully deleted
STEP: Deleting pod
Jun 14 00:27:31.726: INFO: Deleting pod "pod-subpath-test-dynamicpv-gnrk" in namespace "provisioning-3857"
STEP: Deleting pvc
Jun 14 00:27:32.016: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com64t28"
... skipping 10 lines ...

• [SLOW TEST:42.374 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.FO5ImxMAG/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.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow]
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 14 00:27:42.699: INFO: Driver supports dynamic provisioning, skipping PreprovisionedPV pattern
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow]
... skipping 132 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.FO5ImxMAG/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.FO5ImxMAG/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.FO5ImxMAG/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.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 167 lines ...
Jun 14 00:26:03.416: INFO: Creating resource for dynamic PV
Jun 14 00:26:03.416: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-524-e2e-scjrhk4
STEP: creating a claim
Jun 14 00:26:03.514: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-524
Jun 14 00:26:03.807: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-524" in namespace "provisioning-524" to be "Succeeded or Failed"
Jun 14 00:26:03.904: INFO: Pod "volume-prep-provisioning-524": Phase="Pending", Reason="", readiness=false. Elapsed: 96.662967ms
Jun 14 00:26:06.001: INFO: Pod "volume-prep-provisioning-524": Phase="Pending", Reason="", readiness=false. Elapsed: 2.193771516s
Jun 14 00:26:08.098: INFO: Pod "volume-prep-provisioning-524": Phase="Pending", Reason="", readiness=false. Elapsed: 4.290814233s
Jun 14 00:26:10.196: INFO: Pod "volume-prep-provisioning-524": Phase="Pending", Reason="", readiness=false. Elapsed: 6.389073035s
Jun 14 00:26:12.294: INFO: Pod "volume-prep-provisioning-524": Phase="Pending", Reason="", readiness=false. Elapsed: 8.486705465s
Jun 14 00:26:14.392: INFO: Pod "volume-prep-provisioning-524": Phase="Pending", Reason="", readiness=false. Elapsed: 10.584933292s
Jun 14 00:26:16.490: INFO: Pod "volume-prep-provisioning-524": Phase="Pending", Reason="", readiness=false. Elapsed: 12.683237922s
Jun 14 00:26:18.588: INFO: Pod "volume-prep-provisioning-524": Phase="Pending", Reason="", readiness=false. Elapsed: 14.780607741s
Jun 14 00:26:20.687: INFO: Pod "volume-prep-provisioning-524": Phase="Pending", Reason="", readiness=false. Elapsed: 16.87977124s
Jun 14 00:26:22.784: INFO: Pod "volume-prep-provisioning-524": Phase="Pending", Reason="", readiness=false. Elapsed: 18.976807667s
Jun 14 00:26:24.881: INFO: Pod "volume-prep-provisioning-524": Phase="Pending", Reason="", readiness=false. Elapsed: 21.07385743s
Jun 14 00:26:26.980: INFO: Pod "volume-prep-provisioning-524": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.172474937s
STEP: Saw pod success
Jun 14 00:26:26.980: INFO: Pod "volume-prep-provisioning-524" satisfied condition "Succeeded or Failed"
Jun 14 00:26:26.980: INFO: Deleting pod "volume-prep-provisioning-524" in namespace "provisioning-524"
Jun 14 00:26:27.081: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-524" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-ph6f
STEP: Checking for subpath error in container status
Jun 14 00:27:33.471: INFO: Deleting pod "pod-subpath-test-dynamicpv-ph6f" in namespace "provisioning-524"
Jun 14 00:27:33.578: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-ph6f" to be fully deleted
STEP: Deleting pod
Jun 14 00:27:33.674: INFO: Deleting pod "pod-subpath-test-dynamicpv-ph6f" in namespace "provisioning-524"
STEP: Deleting pvc
Jun 14 00:27:33.965: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com7trb7"
... skipping 32 lines ...
Jun 14 00:27:23.351: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-29996kdqt
STEP: creating a claim
Jun 14 00:27:23.448: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-bpcj
STEP: Creating a pod to test subpath
Jun 14 00:27:23.743: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-bpcj" in namespace "provisioning-2999" to be "Succeeded or Failed"
Jun 14 00:27:23.840: INFO: Pod "pod-subpath-test-dynamicpv-bpcj": Phase="Pending", Reason="", readiness=false. Elapsed: 96.28251ms
Jun 14 00:27:25.936: INFO: Pod "pod-subpath-test-dynamicpv-bpcj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.192804765s
Jun 14 00:27:28.033: INFO: Pod "pod-subpath-test-dynamicpv-bpcj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.289529s
Jun 14 00:27:30.130: INFO: Pod "pod-subpath-test-dynamicpv-bpcj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.386198477s
Jun 14 00:27:32.227: INFO: Pod "pod-subpath-test-dynamicpv-bpcj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.483728573s
Jun 14 00:27:34.325: INFO: Pod "pod-subpath-test-dynamicpv-bpcj": Phase="Pending", Reason="", readiness=false. Elapsed: 10.581609169s
Jun 14 00:27:36.422: INFO: Pod "pod-subpath-test-dynamicpv-bpcj": Phase="Pending", Reason="", readiness=false. Elapsed: 12.678398446s
Jun 14 00:27:38.519: INFO: Pod "pod-subpath-test-dynamicpv-bpcj": Phase="Pending", Reason="", readiness=false. Elapsed: 14.77527103s
Jun 14 00:27:40.617: INFO: Pod "pod-subpath-test-dynamicpv-bpcj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.873355818s
STEP: Saw pod success
Jun 14 00:27:40.617: INFO: Pod "pod-subpath-test-dynamicpv-bpcj" satisfied condition "Succeeded or Failed"
Jun 14 00:27:40.713: INFO: Trying to get logs from node ip-172-20-62-170.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-bpcj container test-container-subpath-dynamicpv-bpcj: <nil>
STEP: delete the pod
Jun 14 00:27:40.936: INFO: Waiting for pod pod-subpath-test-dynamicpv-bpcj to disappear
Jun 14 00:27:41.032: INFO: Pod pod-subpath-test-dynamicpv-bpcj no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-bpcj
Jun 14 00:27:41.033: INFO: Deleting pod "pod-subpath-test-dynamicpv-bpcj" in namespace "provisioning-2999"
... skipping 97 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.FO5ImxMAG/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.FO5ImxMAG/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.FO5ImxMAG/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.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Driver supports dynamic provisioning, skipping InlineVolume pattern

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

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 111 lines ...
Jun 14 00:27:28.794: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7940-e2e-sc8x62k
STEP: creating a claim
Jun 14 00:27:28.891: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-gjwh
STEP: Creating a pod to test subpath
Jun 14 00:27:29.184: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-gjwh" in namespace "provisioning-7940" to be "Succeeded or Failed"
Jun 14 00:27:29.280: INFO: Pod "pod-subpath-test-dynamicpv-gjwh": Phase="Pending", Reason="", readiness=false. Elapsed: 96.134269ms
Jun 14 00:27:31.378: INFO: Pod "pod-subpath-test-dynamicpv-gjwh": Phase="Pending", Reason="", readiness=false. Elapsed: 2.194437388s
Jun 14 00:27:33.475: INFO: Pod "pod-subpath-test-dynamicpv-gjwh": Phase="Pending", Reason="", readiness=false. Elapsed: 4.291312198s
Jun 14 00:27:35.572: INFO: Pod "pod-subpath-test-dynamicpv-gjwh": Phase="Pending", Reason="", readiness=false. Elapsed: 6.388094224s
Jun 14 00:27:37.669: INFO: Pod "pod-subpath-test-dynamicpv-gjwh": Phase="Pending", Reason="", readiness=false. Elapsed: 8.484878043s
Jun 14 00:27:39.765: INFO: Pod "pod-subpath-test-dynamicpv-gjwh": Phase="Pending", Reason="", readiness=false. Elapsed: 10.581799763s
Jun 14 00:27:41.869: INFO: Pod "pod-subpath-test-dynamicpv-gjwh": Phase="Pending", Reason="", readiness=false. Elapsed: 12.685307792s
Jun 14 00:27:43.966: INFO: Pod "pod-subpath-test-dynamicpv-gjwh": Phase="Pending", Reason="", readiness=false. Elapsed: 14.782081748s
Jun 14 00:27:46.063: INFO: Pod "pod-subpath-test-dynamicpv-gjwh": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.879384778s
STEP: Saw pod success
Jun 14 00:27:46.063: INFO: Pod "pod-subpath-test-dynamicpv-gjwh" satisfied condition "Succeeded or Failed"
Jun 14 00:27:46.160: INFO: Trying to get logs from node ip-172-20-37-60.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-gjwh container test-container-subpath-dynamicpv-gjwh: <nil>
STEP: delete the pod
Jun 14 00:27:46.375: INFO: Waiting for pod pod-subpath-test-dynamicpv-gjwh to disappear
Jun 14 00:27:46.471: INFO: Pod pod-subpath-test-dynamicpv-gjwh no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-gjwh
Jun 14 00:27:46.471: INFO: Deleting pod "pod-subpath-test-dynamicpv-gjwh" in namespace "provisioning-7940"
... skipping 57 lines ...
Jun 14 00:27:27.470: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4166n88k2
STEP: creating a claim
Jun 14 00:27:27.567: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-gxf7
STEP: Creating a pod to test multi_subpath
Jun 14 00:27:27.862: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-gxf7" in namespace "provisioning-4166" to be "Succeeded or Failed"
Jun 14 00:27:27.959: INFO: Pod "pod-subpath-test-dynamicpv-gxf7": Phase="Pending", Reason="", readiness=false. Elapsed: 96.937084ms
Jun 14 00:27:30.056: INFO: Pod "pod-subpath-test-dynamicpv-gxf7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.19404937s
Jun 14 00:27:32.152: INFO: Pod "pod-subpath-test-dynamicpv-gxf7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.290870673s
Jun 14 00:27:34.249: INFO: Pod "pod-subpath-test-dynamicpv-gxf7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.387788805s
Jun 14 00:27:36.346: INFO: Pod "pod-subpath-test-dynamicpv-gxf7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.484599258s
Jun 14 00:27:38.444: INFO: Pod "pod-subpath-test-dynamicpv-gxf7": Phase="Pending", Reason="", readiness=false. Elapsed: 10.582285131s
... skipping 3 lines ...
Jun 14 00:27:46.833: INFO: Pod "pod-subpath-test-dynamicpv-gxf7": Phase="Pending", Reason="", readiness=false. Elapsed: 18.970996668s
Jun 14 00:27:48.930: INFO: Pod "pod-subpath-test-dynamicpv-gxf7": Phase="Pending", Reason="", readiness=false. Elapsed: 21.068754852s
Jun 14 00:27:51.027: INFO: Pod "pod-subpath-test-dynamicpv-gxf7": Phase="Pending", Reason="", readiness=false. Elapsed: 23.16531321s
Jun 14 00:27:53.129: INFO: Pod "pod-subpath-test-dynamicpv-gxf7": Phase="Pending", Reason="", readiness=false. Elapsed: 25.266967924s
Jun 14 00:27:55.227: INFO: Pod "pod-subpath-test-dynamicpv-gxf7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 27.364923853s
STEP: Saw pod success
Jun 14 00:27:55.227: INFO: Pod "pod-subpath-test-dynamicpv-gxf7" satisfied condition "Succeeded or Failed"
Jun 14 00:27:55.323: INFO: Trying to get logs from node ip-172-20-60-182.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-gxf7 container test-container-subpath-dynamicpv-gxf7: <nil>
STEP: delete the pod
Jun 14 00:27:55.935: INFO: Waiting for pod pod-subpath-test-dynamicpv-gxf7 to disappear
Jun 14 00:27:56.032: INFO: Pod pod-subpath-test-dynamicpv-gxf7 no longer exists
STEP: Deleting pod
Jun 14 00:27:56.032: INFO: Deleting pod "pod-subpath-test-dynamicpv-gxf7" in namespace "provisioning-4166"
... skipping 34 lines ...
Jun 14 00:27:13.417: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 14 00:27:13.762: INFO: Successfully created a new PD: "aws://eu-west-2a/vol-0c12a2bb056581e38".
Jun 14 00:27:13.762: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-k6h2
STEP: Creating a pod to test exec-volume-test
Jun 14 00:27:13.864: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-k6h2" in namespace "volume-1039" to be "Succeeded or Failed"
Jun 14 00:27:13.963: INFO: Pod "exec-volume-test-inlinevolume-k6h2": Phase="Pending", Reason="", readiness=false. Elapsed: 99.150496ms
Jun 14 00:27:16.060: INFO: Pod "exec-volume-test-inlinevolume-k6h2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.195789529s
Jun 14 00:27:18.157: INFO: Pod "exec-volume-test-inlinevolume-k6h2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.292474785s
Jun 14 00:27:20.256: INFO: Pod "exec-volume-test-inlinevolume-k6h2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.391725017s
Jun 14 00:27:22.353: INFO: Pod "exec-volume-test-inlinevolume-k6h2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.488414372s
Jun 14 00:27:24.450: INFO: Pod "exec-volume-test-inlinevolume-k6h2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.586023531s
... skipping 7 lines ...
Jun 14 00:27:41.231: INFO: Pod "exec-volume-test-inlinevolume-k6h2": Phase="Pending", Reason="", readiness=false. Elapsed: 27.36633964s
Jun 14 00:27:43.333: INFO: Pod "exec-volume-test-inlinevolume-k6h2": Phase="Pending", Reason="", readiness=false. Elapsed: 29.468763047s
Jun 14 00:27:45.432: INFO: Pod "exec-volume-test-inlinevolume-k6h2": Phase="Pending", Reason="", readiness=false. Elapsed: 31.567268605s
Jun 14 00:27:47.528: INFO: Pod "exec-volume-test-inlinevolume-k6h2": Phase="Pending", Reason="", readiness=false. Elapsed: 33.664084255s
Jun 14 00:27:49.625: INFO: Pod "exec-volume-test-inlinevolume-k6h2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 35.761203436s
STEP: Saw pod success
Jun 14 00:27:49.626: INFO: Pod "exec-volume-test-inlinevolume-k6h2" satisfied condition "Succeeded or Failed"
Jun 14 00:27:49.722: INFO: Trying to get logs from node ip-172-20-34-37.eu-west-2.compute.internal pod exec-volume-test-inlinevolume-k6h2 container exec-container-inlinevolume-k6h2: <nil>
STEP: delete the pod
Jun 14 00:27:49.922: INFO: Waiting for pod exec-volume-test-inlinevolume-k6h2 to disappear
Jun 14 00:27:50.019: INFO: Pod exec-volume-test-inlinevolume-k6h2 no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-k6h2
Jun 14 00:27:50.019: INFO: Deleting pod "exec-volume-test-inlinevolume-k6h2" in namespace "volume-1039"
Jun 14 00:27:50.336: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0c12a2bb056581e38", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c12a2bb056581e38 is currently attached to i-0e1bbe360340e9289
	status code: 400, request id: f3a50f87-9cb4-4fc6-af8c-144dd9ebb1e8
Jun 14 00:27:55.861: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0c12a2bb056581e38", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c12a2bb056581e38 is currently attached to i-0e1bbe360340e9289
	status code: 400, request id: e77fe2ff-b43c-440d-bef2-1ff66387b1fe
Jun 14 00:28:01.394: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0c12a2bb056581e38", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c12a2bb056581e38 is currently attached to i-0e1bbe360340e9289
	status code: 400, request id: b5cab32e-6dd9-462a-a11f-1a4600069dbf
Jun 14 00:28:06.900: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0c12a2bb056581e38", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c12a2bb056581e38 is currently attached to i-0e1bbe360340e9289
	status code: 400, request id: 7058472a-4d6b-44fb-ae50-c9600da5ff5b
Jun 14 00:28:12.446: INFO: Successfully deleted PD "aws://eu-west-2a/vol-0c12a2bb056581e38".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 14 00:28:12.446: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-1039" for this suite.
... skipping 220 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.FO5ImxMAG/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.FO5ImxMAG/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.FO5ImxMAG/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.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 99 lines ...
Jun 14 00:27:38.810: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8630-e2e-scxx9sm
STEP: creating a claim
Jun 14 00:27:38.911: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-469h
STEP: Creating a pod to test multi_subpath
Jun 14 00:27:39.223: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-469h" in namespace "provisioning-8630" to be "Succeeded or Failed"
Jun 14 00:27:39.322: INFO: Pod "pod-subpath-test-dynamicpv-469h": Phase="Pending", Reason="", readiness=false. Elapsed: 98.440273ms
Jun 14 00:27:41.419: INFO: Pod "pod-subpath-test-dynamicpv-469h": Phase="Pending", Reason="", readiness=false. Elapsed: 2.195939693s
Jun 14 00:27:43.518: INFO: Pod "pod-subpath-test-dynamicpv-469h": Phase="Pending", Reason="", readiness=false. Elapsed: 4.294326675s
Jun 14 00:27:45.620: INFO: Pod "pod-subpath-test-dynamicpv-469h": Phase="Pending", Reason="", readiness=false. Elapsed: 6.396565081s
Jun 14 00:27:47.720: INFO: Pod "pod-subpath-test-dynamicpv-469h": Phase="Pending", Reason="", readiness=false. Elapsed: 8.49673981s
Jun 14 00:27:49.818: INFO: Pod "pod-subpath-test-dynamicpv-469h": Phase="Pending", Reason="", readiness=false. Elapsed: 10.594427605s
Jun 14 00:27:51.916: INFO: Pod "pod-subpath-test-dynamicpv-469h": Phase="Pending", Reason="", readiness=false. Elapsed: 12.6927474s
Jun 14 00:27:54.014: INFO: Pod "pod-subpath-test-dynamicpv-469h": Phase="Pending", Reason="", readiness=false. Elapsed: 14.790563791s
Jun 14 00:27:56.111: INFO: Pod "pod-subpath-test-dynamicpv-469h": Phase="Pending", Reason="", readiness=false. Elapsed: 16.888093666s
Jun 14 00:27:58.215: INFO: Pod "pod-subpath-test-dynamicpv-469h": Phase="Pending", Reason="", readiness=false. Elapsed: 18.991128231s
Jun 14 00:28:00.315: INFO: Pod "pod-subpath-test-dynamicpv-469h": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.091933848s
STEP: Saw pod success
Jun 14 00:28:00.315: INFO: Pod "pod-subpath-test-dynamicpv-469h" satisfied condition "Succeeded or Failed"
Jun 14 00:28:00.414: INFO: Trying to get logs from node ip-172-20-60-182.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-469h container test-container-subpath-dynamicpv-469h: <nil>
STEP: delete the pod
Jun 14 00:28:00.620: INFO: Waiting for pod pod-subpath-test-dynamicpv-469h to disappear
Jun 14 00:28:00.718: INFO: Pod pod-subpath-test-dynamicpv-469h no longer exists
STEP: Deleting pod
Jun 14 00:28:00.718: INFO: Deleting pod "pod-subpath-test-dynamicpv-469h" in namespace "provisioning-8630"
... skipping 218 lines ...

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

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

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 99 lines ...
Jun 14 00:28:02.439: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-887-e2e-scwhbxt
STEP: creating a claim
Jun 14 00:28:02.536: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-rdtv
STEP: Creating a pod to test subpath
Jun 14 00:28:02.825: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-rdtv" in namespace "provisioning-887" to be "Succeeded or Failed"
Jun 14 00:28:02.921: INFO: Pod "pod-subpath-test-dynamicpv-rdtv": Phase="Pending", Reason="", readiness=false. Elapsed: 95.658723ms
Jun 14 00:28:05.017: INFO: Pod "pod-subpath-test-dynamicpv-rdtv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.191603157s
Jun 14 00:28:07.114: INFO: Pod "pod-subpath-test-dynamicpv-rdtv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.288593329s
Jun 14 00:28:09.209: INFO: Pod "pod-subpath-test-dynamicpv-rdtv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.384082156s
Jun 14 00:28:11.305: INFO: Pod "pod-subpath-test-dynamicpv-rdtv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.479611747s
Jun 14 00:28:13.400: INFO: Pod "pod-subpath-test-dynamicpv-rdtv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.575294303s
Jun 14 00:28:15.496: INFO: Pod "pod-subpath-test-dynamicpv-rdtv": Phase="Pending", Reason="", readiness=false. Elapsed: 12.671223124s
Jun 14 00:28:17.592: INFO: Pod "pod-subpath-test-dynamicpv-rdtv": Phase="Pending", Reason="", readiness=false. Elapsed: 14.766754111s
Jun 14 00:28:19.687: INFO: Pod "pod-subpath-test-dynamicpv-rdtv": Phase="Pending", Reason="", readiness=false. Elapsed: 16.862183394s
Jun 14 00:28:21.785: INFO: Pod "pod-subpath-test-dynamicpv-rdtv": Phase="Pending", Reason="", readiness=false. Elapsed: 18.959608831s
Jun 14 00:28:23.880: INFO: Pod "pod-subpath-test-dynamicpv-rdtv": Phase="Pending", Reason="", readiness=false. Elapsed: 21.055407255s
Jun 14 00:28:25.976: INFO: Pod "pod-subpath-test-dynamicpv-rdtv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.151355237s
STEP: Saw pod success
Jun 14 00:28:25.976: INFO: Pod "pod-subpath-test-dynamicpv-rdtv" satisfied condition "Succeeded or Failed"
Jun 14 00:28:26.074: INFO: Trying to get logs from node ip-172-20-34-37.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-rdtv container test-container-subpath-dynamicpv-rdtv: <nil>
STEP: delete the pod
Jun 14 00:28:26.275: INFO: Waiting for pod pod-subpath-test-dynamicpv-rdtv to disappear
Jun 14 00:28:26.370: INFO: Pod pod-subpath-test-dynamicpv-rdtv no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-rdtv
Jun 14 00:28:26.370: INFO: Deleting pod "pod-subpath-test-dynamicpv-rdtv" in namespace "provisioning-887"
... skipping 288 lines ...
Jun 14 00:28:13.273: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-797j7z5
STEP: creating a claim
Jun 14 00:28:13.371: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-lkmc
STEP: Creating a pod to test subpath
Jun 14 00:28:13.669: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-lkmc" in namespace "provisioning-79" to be "Succeeded or Failed"
Jun 14 00:28:13.765: INFO: Pod "pod-subpath-test-dynamicpv-lkmc": Phase="Pending", Reason="", readiness=false. Elapsed: 96.371082ms
Jun 14 00:28:15.862: INFO: Pod "pod-subpath-test-dynamicpv-lkmc": Phase="Pending", Reason="", readiness=false. Elapsed: 2.192960008s
Jun 14 00:28:17.959: INFO: Pod "pod-subpath-test-dynamicpv-lkmc": Phase="Pending", Reason="", readiness=false. Elapsed: 4.289939942s
Jun 14 00:28:20.055: INFO: Pod "pod-subpath-test-dynamicpv-lkmc": Phase="Pending", Reason="", readiness=false. Elapsed: 6.386453823s
Jun 14 00:28:22.152: INFO: Pod "pod-subpath-test-dynamicpv-lkmc": Phase="Pending", Reason="", readiness=false. Elapsed: 8.483863553s
Jun 14 00:28:24.250: INFO: Pod "pod-subpath-test-dynamicpv-lkmc": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.581483722s
STEP: Saw pod success
Jun 14 00:28:24.250: INFO: Pod "pod-subpath-test-dynamicpv-lkmc" satisfied condition "Succeeded or Failed"
Jun 14 00:28:24.346: INFO: Trying to get logs from node ip-172-20-34-37.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-lkmc container test-container-volume-dynamicpv-lkmc: <nil>
STEP: delete the pod
Jun 14 00:28:24.546: INFO: Waiting for pod pod-subpath-test-dynamicpv-lkmc to disappear
Jun 14 00:28:24.643: INFO: Pod pod-subpath-test-dynamicpv-lkmc no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-lkmc
Jun 14 00:28:24.643: INFO: Deleting pod "pod-subpath-test-dynamicpv-lkmc" in namespace "provisioning-79"
... skipping 198 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.FO5ImxMAG/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.FO5ImxMAG/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.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 122 lines ...
Jun 14 00:29:00.617: INFO: Waiting for pod aws-client to disappear
Jun 14 00:29:00.713: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 14 00:29:00.713: INFO: Deleting PersistentVolumeClaim "pvc-dbf44"
Jun 14 00:29:00.809: INFO: Deleting PersistentVolume "aws-4sjfh"
Jun 14 00:29:01.432: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0b361ebe842881ebc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0b361ebe842881ebc is currently attached to i-02d9eae89c0612df4
	status code: 400, request id: 943a4be0-8eb4-4409-bcd7-b026b074a0d7
Jun 14 00:29:06.964: INFO: Successfully deleted PD "aws://eu-west-2a/vol-0b361ebe842881ebc".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 14 00:29:06.965: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-2513" for this suite.
... skipping 14 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 14 00:28:16.404: 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.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun 14 00:28:16.889: INFO: Creating resource for dynamic PV
Jun 14 00:28:16.889: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8884-e2e-scqkj9k
STEP: creating a claim
Jun 14 00:28:16.987: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-g6qg
STEP: Checking for subpath error in container status
Jun 14 00:28:41.478: INFO: Deleting pod "pod-subpath-test-dynamicpv-g6qg" in namespace "provisioning-8884"
Jun 14 00:28:41.578: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-g6qg" to be fully deleted
STEP: Deleting pod
Jun 14 00:28:51.774: INFO: Deleting pod "pod-subpath-test-dynamicpv-g6qg" in namespace "provisioning-8884"
STEP: Deleting pvc
Jun 14 00:28:52.064: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comf7t7x"
... skipping 11 lines ...

• [SLOW TEST:51.457 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath directory is outside the volume [Slow][LinuxOnly]
    /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow]
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 14 00:29:07.862: INFO: Driver supports dynamic provisioning, skipping PreprovisionedPV pattern
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow]
... skipping 357 lines ...

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

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

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

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

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

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

      Not enough topologies in cluster -- skipping

      /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 120 lines ...
Jun 14 00:28:13.124: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-952-e2e-scpq9tw
STEP: creating a claim
Jun 14 00:28:13.222: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-cwr6
STEP: Creating a pod to test atomic-volume-subpath
Jun 14 00:28:13.515: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-cwr6" in namespace "provisioning-952" to be "Succeeded or Failed"
Jun 14 00:28:13.610: INFO: Pod "pod-subpath-test-dynamicpv-cwr6": Phase="Pending", Reason="", readiness=false. Elapsed: 95.664509ms
Jun 14 00:28:15.706: INFO: Pod "pod-subpath-test-dynamicpv-cwr6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.191825321s
Jun 14 00:28:17.806: INFO: Pod "pod-subpath-test-dynamicpv-cwr6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.291294662s
Jun 14 00:28:19.902: INFO: Pod "pod-subpath-test-dynamicpv-cwr6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.387569332s
Jun 14 00:28:21.999: INFO: Pod "pod-subpath-test-dynamicpv-cwr6": Phase="Pending", Reason="", readiness=false. Elapsed: 8.483921832s
Jun 14 00:28:24.095: INFO: Pod "pod-subpath-test-dynamicpv-cwr6": Phase="Pending", Reason="", readiness=false. Elapsed: 10.580098862s
... skipping 11 lines ...
Jun 14 00:28:49.263: INFO: Pod "pod-subpath-test-dynamicpv-cwr6": Phase="Running", Reason="", readiness=true. Elapsed: 35.748674672s
Jun 14 00:28:51.359: INFO: Pod "pod-subpath-test-dynamicpv-cwr6": Phase="Running", Reason="", readiness=true. Elapsed: 37.844743558s
Jun 14 00:28:53.456: INFO: Pod "pod-subpath-test-dynamicpv-cwr6": Phase="Running", Reason="", readiness=true. Elapsed: 39.941063484s
Jun 14 00:28:55.553: INFO: Pod "pod-subpath-test-dynamicpv-cwr6": Phase="Running", Reason="", readiness=true. Elapsed: 42.037889791s
Jun 14 00:28:57.649: INFO: Pod "pod-subpath-test-dynamicpv-cwr6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 44.134085596s
STEP: Saw pod success
Jun 14 00:28:57.649: INFO: Pod "pod-subpath-test-dynamicpv-cwr6" satisfied condition "Succeeded or Failed"
Jun 14 00:28:57.745: INFO: Trying to get logs from node ip-172-20-37-60.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-cwr6 container test-container-subpath-dynamicpv-cwr6: <nil>
STEP: delete the pod
Jun 14 00:28:57.958: INFO: Waiting for pod pod-subpath-test-dynamicpv-cwr6 to disappear
Jun 14 00:28:58.058: INFO: Pod pod-subpath-test-dynamicpv-cwr6 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-cwr6
Jun 14 00:28:58.058: INFO: Deleting pod "pod-subpath-test-dynamicpv-cwr6" in namespace "provisioning-952"
... skipping 124 lines ...
Jun 14 00:28:39.032: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-2666k9bxj
STEP: creating a claim
Jun 14 00:28:39.131: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-p44g
STEP: Creating a pod to test exec-volume-test
Jun 14 00:28:39.425: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-p44g" in namespace "volume-2666" to be "Succeeded or Failed"
Jun 14 00:28:39.521: INFO: Pod "exec-volume-test-dynamicpv-p44g": Phase="Pending", Reason="", readiness=false. Elapsed: 96.437442ms
Jun 14 00:28:41.619: INFO: Pod "exec-volume-test-dynamicpv-p44g": Phase="Pending", Reason="", readiness=false. Elapsed: 2.193819779s
Jun 14 00:28:43.719: INFO: Pod "exec-volume-test-dynamicpv-p44g": Phase="Pending", Reason="", readiness=false. Elapsed: 4.293937065s
Jun 14 00:28:45.816: INFO: Pod "exec-volume-test-dynamicpv-p44g": Phase="Pending", Reason="", readiness=false. Elapsed: 6.391088387s
Jun 14 00:28:47.914: INFO: Pod "exec-volume-test-dynamicpv-p44g": Phase="Pending", Reason="", readiness=false. Elapsed: 8.488577905s
Jun 14 00:28:50.014: INFO: Pod "exec-volume-test-dynamicpv-p44g": Phase="Pending", Reason="", readiness=false. Elapsed: 10.58875168s
... skipping 2 lines ...
Jun 14 00:28:56.306: INFO: Pod "exec-volume-test-dynamicpv-p44g": Phase="Pending", Reason="", readiness=false. Elapsed: 16.880840018s
Jun 14 00:28:58.403: INFO: Pod "exec-volume-test-dynamicpv-p44g": Phase="Pending", Reason="", readiness=false. Elapsed: 18.978424156s
Jun 14 00:29:00.500: INFO: Pod "exec-volume-test-dynamicpv-p44g": Phase="Pending", Reason="", readiness=false. Elapsed: 21.075434535s
Jun 14 00:29:02.597: INFO: Pod "exec-volume-test-dynamicpv-p44g": Phase="Pending", Reason="", readiness=false. Elapsed: 23.172304243s
Jun 14 00:29:04.694: INFO: Pod "exec-volume-test-dynamicpv-p44g": Phase="Succeeded", Reason="", readiness=false. Elapsed: 25.269028487s
STEP: Saw pod success
Jun 14 00:29:04.694: INFO: Pod "exec-volume-test-dynamicpv-p44g" satisfied condition "Succeeded or Failed"
Jun 14 00:29:04.791: INFO: Trying to get logs from node ip-172-20-34-37.eu-west-2.compute.internal pod exec-volume-test-dynamicpv-p44g container exec-container-dynamicpv-p44g: <nil>
STEP: delete the pod
Jun 14 00:29:04.996: INFO: Waiting for pod exec-volume-test-dynamicpv-p44g to disappear
Jun 14 00:29:05.093: INFO: Pod exec-volume-test-dynamicpv-p44g no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-p44g
Jun 14 00:29:05.093: INFO: Deleting pod "exec-volume-test-dynamicpv-p44g" in namespace "volume-2666"
... skipping 172 lines ...
Jun 14 00:29:02.837: INFO: PersistentVolumeClaim pvc-5g59j found but phase is Pending instead of Bound.
Jun 14 00:29:04.936: INFO: PersistentVolumeClaim pvc-5g59j found and phase=Bound (10.585624648s)
Jun 14 00:29:04.936: INFO: Waiting up to 3m0s for PersistentVolume aws-bjq8s to have phase Bound
Jun 14 00:29:05.033: INFO: PersistentVolume aws-bjq8s found and phase=Bound (96.576413ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-lhcj
STEP: Creating a pod to test exec-volume-test
Jun 14 00:29:05.323: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-lhcj" in namespace "volume-4062" to be "Succeeded or Failed"
Jun 14 00:29:05.421: INFO: Pod "exec-volume-test-preprovisionedpv-lhcj": Phase="Pending", Reason="", readiness=false. Elapsed: 98.202552ms
Jun 14 00:29:07.518: INFO: Pod "exec-volume-test-preprovisionedpv-lhcj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.195298083s
Jun 14 00:29:09.615: INFO: Pod "exec-volume-test-preprovisionedpv-lhcj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.292200634s
Jun 14 00:29:11.712: INFO: Pod "exec-volume-test-preprovisionedpv-lhcj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.389554643s
Jun 14 00:29:13.810: INFO: Pod "exec-volume-test-preprovisionedpv-lhcj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.487449898s
Jun 14 00:29:15.907: INFO: Pod "exec-volume-test-preprovisionedpv-lhcj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.584462602s
STEP: Saw pod success
Jun 14 00:29:15.907: INFO: Pod "exec-volume-test-preprovisionedpv-lhcj" satisfied condition "Succeeded or Failed"
Jun 14 00:29:16.004: INFO: Trying to get logs from node ip-172-20-34-37.eu-west-2.compute.internal pod exec-volume-test-preprovisionedpv-lhcj container exec-container-preprovisionedpv-lhcj: <nil>
STEP: delete the pod
Jun 14 00:29:16.206: INFO: Waiting for pod exec-volume-test-preprovisionedpv-lhcj to disappear
Jun 14 00:29:16.303: INFO: Pod exec-volume-test-preprovisionedpv-lhcj no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-lhcj
Jun 14 00:29:16.303: INFO: Deleting pod "exec-volume-test-preprovisionedpv-lhcj" in namespace "volume-4062"
STEP: Deleting pv and pvc
Jun 14 00:29:16.399: INFO: Deleting PersistentVolumeClaim "pvc-5g59j"
Jun 14 00:29:16.497: INFO: Deleting PersistentVolume "aws-bjq8s"
Jun 14 00:29:16.821: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0295a678765f58125", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0295a678765f58125 is currently attached to i-0e1bbe360340e9289
	status code: 400, request id: 288a8eb7-6492-46a0-9002-fd19c436f4b8
Jun 14 00:29:22.363: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0295a678765f58125", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0295a678765f58125 is currently attached to i-0e1bbe360340e9289
	status code: 400, request id: b7edbe93-a22e-481c-8bbd-64d04e0e0c17
Jun 14 00:29:27.865: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0295a678765f58125", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0295a678765f58125 is currently attached to i-0e1bbe360340e9289
	status code: 400, request id: 14032585-447f-49a4-ac06-136f4def46c1
Jun 14 00:29:33.437: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0295a678765f58125", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0295a678765f58125 is currently attached to i-0e1bbe360340e9289
	status code: 400, request id: 34dfa43a-698b-4145-beb8-1f08dd19a3ec
Jun 14 00:29:38.967: INFO: Successfully deleted PD "aws://eu-west-2a/vol-0295a678765f58125".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 14 00:29:38.967: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-4062" for this suite.
... skipping 23 lines ...
Jun 14 00:28:38.707: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8465-e2e-sc7dqk5
STEP: creating a claim
Jun 14 00:28:38.804: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-d88v
STEP: Creating a pod to test subpath
Jun 14 00:28:39.097: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-d88v" in namespace "provisioning-8465" to be "Succeeded or Failed"
Jun 14 00:28:39.194: INFO: Pod "pod-subpath-test-dynamicpv-d88v": Phase="Pending", Reason="", readiness=false. Elapsed: 96.531991ms
Jun 14 00:28:41.291: INFO: Pod "pod-subpath-test-dynamicpv-d88v": Phase="Pending", Reason="", readiness=false. Elapsed: 2.193475359s
Jun 14 00:28:43.388: INFO: Pod "pod-subpath-test-dynamicpv-d88v": Phase="Pending", Reason="", readiness=false. Elapsed: 4.290509764s
Jun 14 00:28:45.485: INFO: Pod "pod-subpath-test-dynamicpv-d88v": Phase="Pending", Reason="", readiness=false. Elapsed: 6.387831352s
Jun 14 00:28:47.582: INFO: Pod "pod-subpath-test-dynamicpv-d88v": Phase="Pending", Reason="", readiness=false. Elapsed: 8.485193785s
Jun 14 00:28:49.682: INFO: Pod "pod-subpath-test-dynamicpv-d88v": Phase="Pending", Reason="", readiness=false. Elapsed: 10.584421325s
... skipping 2 lines ...
Jun 14 00:28:55.974: INFO: Pod "pod-subpath-test-dynamicpv-d88v": Phase="Pending", Reason="", readiness=false. Elapsed: 16.876371362s
Jun 14 00:28:58.071: INFO: Pod "pod-subpath-test-dynamicpv-d88v": Phase="Pending", Reason="", readiness=false. Elapsed: 18.973538333s
Jun 14 00:29:00.171: INFO: Pod "pod-subpath-test-dynamicpv-d88v": Phase="Pending", Reason="", readiness=false. Elapsed: 21.07348095s
Jun 14 00:29:02.268: INFO: Pod "pod-subpath-test-dynamicpv-d88v": Phase="Pending", Reason="", readiness=false. Elapsed: 23.170381545s
Jun 14 00:29:04.365: INFO: Pod "pod-subpath-test-dynamicpv-d88v": Phase="Succeeded", Reason="", readiness=false. Elapsed: 25.268236705s
STEP: Saw pod success
Jun 14 00:29:04.366: INFO: Pod "pod-subpath-test-dynamicpv-d88v" satisfied condition "Succeeded or Failed"
Jun 14 00:29:04.462: INFO: Trying to get logs from node ip-172-20-62-170.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-d88v container test-container-subpath-dynamicpv-d88v: <nil>
STEP: delete the pod
Jun 14 00:29:04.664: INFO: Waiting for pod pod-subpath-test-dynamicpv-d88v to disappear
Jun 14 00:29:04.761: INFO: Pod pod-subpath-test-dynamicpv-d88v no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-d88v
Jun 14 00:29:04.761: INFO: Deleting pod "pod-subpath-test-dynamicpv-d88v" in namespace "provisioning-8465"
... skipping 401 lines ...
Jun 14 00:29:21.464: INFO: Waiting for pod aws-client to disappear
Jun 14 00:29:21.560: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 14 00:29:21.560: INFO: Deleting PersistentVolumeClaim "pvc-nmmn9"
Jun 14 00:29:21.660: INFO: Deleting PersistentVolume "aws-7qf4z"
Jun 14 00:29:22.268: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0cb68356e76fa221e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0cb68356e76fa221e is currently attached to i-068ab7d6aa6e1db55
	status code: 400, request id: 1ef8e2be-487a-48be-a974-f089290592c5
Jun 14 00:29:27.794: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0cb68356e76fa221e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0cb68356e76fa221e is currently attached to i-068ab7d6aa6e1db55
	status code: 400, request id: 982b1806-7cf0-4505-8dba-c42c05902f9a
Jun 14 00:29:33.295: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0cb68356e76fa221e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0cb68356e76fa221e is currently attached to i-068ab7d6aa6e1db55
	status code: 400, request id: 310b91e7-4b72-4b11-973f-db06eff16404
Jun 14 00:29:38.818: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0cb68356e76fa221e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0cb68356e76fa221e is currently attached to i-068ab7d6aa6e1db55
	status code: 400, request id: c7a1b86e-cefe-4536-a6f0-6187114c79e7
Jun 14 00:29:44.316: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0cb68356e76fa221e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0cb68356e76fa221e is currently attached to i-068ab7d6aa6e1db55
	status code: 400, request id: 16ee9154-c2f2-43f5-b772-68c78e4e271a
Jun 14 00:29:49.872: INFO: Successfully deleted PD "aws://eu-west-2a/vol-0cb68356e76fa221e".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 14 00:29:49.872: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-1187" for this suite.
... skipping 22 lines ...
Jun 14 00:27:52.592: INFO: Creating resource for dynamic PV
Jun 14 00:27:52.592: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-7366-e2e-scp6g4j
STEP: creating a claim
Jun 14 00:27:52.689: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 14 00:27:52.997: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-zhf5l" in namespace "snapshotting-7366" to be "Succeeded or Failed"
Jun 14 00:27:53.094: INFO: Pod "pvc-snapshottable-tester-zhf5l": Phase="Pending", Reason="", readiness=false. Elapsed: 96.371748ms
Jun 14 00:27:55.190: INFO: Pod "pvc-snapshottable-tester-zhf5l": Phase="Pending", Reason="", readiness=false. Elapsed: 2.193207634s
Jun 14 00:27:57.290: INFO: Pod "pvc-snapshottable-tester-zhf5l": Phase="Pending", Reason="", readiness=false. Elapsed: 4.29251681s
Jun 14 00:27:59.387: INFO: Pod "pvc-snapshottable-tester-zhf5l": Phase="Pending", Reason="", readiness=false. Elapsed: 6.389720779s
Jun 14 00:28:01.485: INFO: Pod "pvc-snapshottable-tester-zhf5l": Phase="Pending", Reason="", readiness=false. Elapsed: 8.487506525s
Jun 14 00:28:03.582: INFO: Pod "pvc-snapshottable-tester-zhf5l": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.584338669s
STEP: Saw pod success
Jun 14 00:28:03.582: INFO: Pod "pvc-snapshottable-tester-zhf5l" satisfied condition "Succeeded or Failed"
Jun 14 00:28:03.776: INFO: Pod pvc-snapshottable-tester-zhf5l has the following logs: 
Jun 14 00:28:03.776: INFO: Deleting pod "pvc-snapshottable-tester-zhf5l" in namespace "snapshotting-7366"
Jun 14 00:28:03.890: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-zhf5l" to be fully deleted
Jun 14 00:28:03.987: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comrwvdx] to have phase Bound
Jun 14 00:28:04.088: INFO: PersistentVolumeClaim ebs.csi.aws.comrwvdx found and phase=Bound (101.376648ms)
STEP: [init] checking the claim
... skipping 38 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.FO5ImxMAG/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 14 00:28:27.117: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-rvgt5" in namespace "snapshotting-7366" to be "Succeeded or Failed"
Jun 14 00:28:27.218: INFO: Pod "pvc-snapshottable-data-tester-rvgt5": Phase="Pending", Reason="", readiness=false. Elapsed: 100.80218ms
Jun 14 00:28:29.314: INFO: Pod "pvc-snapshottable-data-tester-rvgt5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.197268304s
Jun 14 00:28:31.412: INFO: Pod "pvc-snapshottable-data-tester-rvgt5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.294542477s
Jun 14 00:28:33.509: INFO: Pod "pvc-snapshottable-data-tester-rvgt5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.391981376s
STEP: Saw pod success
Jun 14 00:28:33.509: INFO: Pod "pvc-snapshottable-data-tester-rvgt5" satisfied condition "Succeeded or Failed"
Jun 14 00:28:33.704: INFO: Pod pvc-snapshottable-data-tester-rvgt5 has the following logs: 
Jun 14 00:28:33.704: INFO: Deleting pod "pvc-snapshottable-data-tester-rvgt5" in namespace "snapshotting-7366"
Jun 14 00:28:33.808: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-rvgt5" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 14 00:28:56.296: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-7366 exec restored-pvc-tester-4gk4l --namespace=snapshotting-7366 -- cat /mnt/test/data'
... skipping 255 lines ...
    /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:108
      
      /tmp/kops.FO5ImxMAG/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.FO5ImxMAG/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-7366 exec restored-pvc-tester-4gk4l --namespace=snapshotting-7366 -- 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-7366 exec restored-pvc-tester-4gk4l --namespace=snapshotting-7366 -- 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.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:602
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
... skipping 293 lines ...
Jun 14 00:29:17.770: INFO: PersistentVolumeClaim pvc-m2l5n found but phase is Pending instead of Bound.
Jun 14 00:29:19.867: INFO: PersistentVolumeClaim pvc-m2l5n found and phase=Bound (10.582338165s)
Jun 14 00:29:19.867: INFO: Waiting up to 3m0s for PersistentVolume aws-w8nmg to have phase Bound
Jun 14 00:29:19.964: INFO: PersistentVolume aws-w8nmg found and phase=Bound (96.851275ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-8xh7
STEP: Creating a pod to test exec-volume-test
Jun 14 00:29:20.262: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-8xh7" in namespace "volume-5379" to be "Succeeded or Failed"
Jun 14 00:29:20.360: INFO: Pod "exec-volume-test-preprovisionedpv-8xh7": Phase="Pending", Reason="", readiness=false. Elapsed: 97.084491ms
Jun 14 00:29:22.457: INFO: Pod "exec-volume-test-preprovisionedpv-8xh7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.194553346s
Jun 14 00:29:24.555: INFO: Pod "exec-volume-test-preprovisionedpv-8xh7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.292645246s
Jun 14 00:29:26.653: INFO: Pod "exec-volume-test-preprovisionedpv-8xh7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.390674271s
Jun 14 00:29:28.750: INFO: Pod "exec-volume-test-preprovisionedpv-8xh7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.487754159s
Jun 14 00:29:30.847: INFO: Pod "exec-volume-test-preprovisionedpv-8xh7": Phase="Pending", Reason="", readiness=false. Elapsed: 10.584957649s
Jun 14 00:29:32.945: INFO: Pod "exec-volume-test-preprovisionedpv-8xh7": Phase="Pending", Reason="", readiness=false. Elapsed: 12.682513932s
Jun 14 00:29:35.043: INFO: Pod "exec-volume-test-preprovisionedpv-8xh7": Phase="Pending", Reason="", readiness=false. Elapsed: 14.780550641s
Jun 14 00:29:37.140: INFO: Pod "exec-volume-test-preprovisionedpv-8xh7": Phase="Pending", Reason="", readiness=false. Elapsed: 16.877590057s
Jun 14 00:29:39.238: INFO: Pod "exec-volume-test-preprovisionedpv-8xh7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.975929088s
STEP: Saw pod success
Jun 14 00:29:39.238: INFO: Pod "exec-volume-test-preprovisionedpv-8xh7" satisfied condition "Succeeded or Failed"
Jun 14 00:29:39.335: INFO: Trying to get logs from node ip-172-20-37-60.eu-west-2.compute.internal pod exec-volume-test-preprovisionedpv-8xh7 container exec-container-preprovisionedpv-8xh7: <nil>
STEP: delete the pod
Jun 14 00:29:39.538: INFO: Waiting for pod exec-volume-test-preprovisionedpv-8xh7 to disappear
Jun 14 00:29:39.637: INFO: Pod exec-volume-test-preprovisionedpv-8xh7 no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-8xh7
Jun 14 00:29:39.637: INFO: Deleting pod "exec-volume-test-preprovisionedpv-8xh7" in namespace "volume-5379"
STEP: Deleting pv and pvc
Jun 14 00:29:39.733: INFO: Deleting PersistentVolumeClaim "pvc-m2l5n"
Jun 14 00:29:39.831: INFO: Deleting PersistentVolume "aws-w8nmg"
Jun 14 00:29:40.139: INFO: Couldn't delete PD "aws://eu-west-2a/vol-037f56ff215b69d36", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-037f56ff215b69d36 is currently attached to i-00b65c838fd755bcb
	status code: 400, request id: 082b360e-3d1a-484f-9fef-ae2abedacf21
Jun 14 00:29:45.818: INFO: Couldn't delete PD "aws://eu-west-2a/vol-037f56ff215b69d36", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-037f56ff215b69d36 is currently attached to i-00b65c838fd755bcb
	status code: 400, request id: 227d5d0e-2736-4d07-9b8a-5d3ffc097a84
Jun 14 00:29:51.349: INFO: Couldn't delete PD "aws://eu-west-2a/vol-037f56ff215b69d36", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-037f56ff215b69d36 is currently attached to i-00b65c838fd755bcb
	status code: 400, request id: 5bb346b7-391e-45f8-ba0b-b6c2804e8879
Jun 14 00:29:56.838: INFO: Couldn't delete PD "aws://eu-west-2a/vol-037f56ff215b69d36", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-037f56ff215b69d36 is currently attached to i-00b65c838fd755bcb
	status code: 400, request id: cb59bead-8512-4f8e-9d80-0ea9e28a6124
Jun 14 00:30:02.381: INFO: Successfully deleted PD "aws://eu-west-2a/vol-037f56ff215b69d36".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 14 00:30:02.381: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-5379" for this suite.
... skipping 81 lines ...
Jun 14 00:29:17.754: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6395h2h2c
STEP: creating a claim
Jun 14 00:29:17.851: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-6kqg
STEP: Creating a pod to test subpath
Jun 14 00:29:18.154: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-6kqg" in namespace "provisioning-6395" to be "Succeeded or Failed"
Jun 14 00:29:18.251: INFO: Pod "pod-subpath-test-dynamicpv-6kqg": Phase="Pending", Reason="", readiness=false. Elapsed: 96.642189ms
Jun 14 00:29:20.348: INFO: Pod "pod-subpath-test-dynamicpv-6kqg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.194359447s
Jun 14 00:29:22.449: INFO: Pod "pod-subpath-test-dynamicpv-6kqg": Phase="Pending", Reason="", readiness=false. Elapsed: 4.295007804s
Jun 14 00:29:24.546: INFO: Pod "pod-subpath-test-dynamicpv-6kqg": Phase="Pending", Reason="", readiness=false. Elapsed: 6.391584954s
Jun 14 00:29:26.643: INFO: Pod "pod-subpath-test-dynamicpv-6kqg": Phase="Pending", Reason="", readiness=false. Elapsed: 8.489012514s
Jun 14 00:29:28.740: INFO: Pod "pod-subpath-test-dynamicpv-6kqg": Phase="Pending", Reason="", readiness=false. Elapsed: 10.585872738s
Jun 14 00:29:30.837: INFO: Pod "pod-subpath-test-dynamicpv-6kqg": Phase="Pending", Reason="", readiness=false. Elapsed: 12.682935009s
Jun 14 00:29:32.934: INFO: Pod "pod-subpath-test-dynamicpv-6kqg": Phase="Pending", Reason="", readiness=false. Elapsed: 14.779849234s
Jun 14 00:29:35.032: INFO: Pod "pod-subpath-test-dynamicpv-6kqg": Phase="Pending", Reason="", readiness=false. Elapsed: 16.877635538s
Jun 14 00:29:37.129: INFO: Pod "pod-subpath-test-dynamicpv-6kqg": Phase="Pending", Reason="", readiness=false. Elapsed: 18.974764199s
Jun 14 00:29:39.226: INFO: Pod "pod-subpath-test-dynamicpv-6kqg": Phase="Pending", Reason="", readiness=false. Elapsed: 21.072047294s
Jun 14 00:29:41.322: INFO: Pod "pod-subpath-test-dynamicpv-6kqg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.168562886s
STEP: Saw pod success
Jun 14 00:29:41.323: INFO: Pod "pod-subpath-test-dynamicpv-6kqg" satisfied condition "Succeeded or Failed"
Jun 14 00:29:41.420: INFO: Trying to get logs from node ip-172-20-60-182.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-6kqg container test-container-subpath-dynamicpv-6kqg: <nil>
STEP: delete the pod
Jun 14 00:29:41.626: INFO: Waiting for pod pod-subpath-test-dynamicpv-6kqg to disappear
Jun 14 00:29:41.722: INFO: Pod pod-subpath-test-dynamicpv-6kqg no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-6kqg
Jun 14 00:29:41.722: INFO: Deleting pod "pod-subpath-test-dynamicpv-6kqg" in namespace "provisioning-6395"
... skipping 39 lines ...
Jun 14 00:29:01.641: INFO: Creating resource for dynamic PV
Jun 14 00:29:01.641: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4316c7x7p
STEP: creating a claim
Jun 14 00:29:01.741: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-4316
Jun 14 00:29:02.036: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-4316" in namespace "provisioning-4316" to be "Succeeded or Failed"
Jun 14 00:29:02.133: INFO: Pod "volume-prep-provisioning-4316": Phase="Pending", Reason="", readiness=false. Elapsed: 96.884158ms
Jun 14 00:29:04.230: INFO: Pod "volume-prep-provisioning-4316": Phase="Pending", Reason="", readiness=false. Elapsed: 2.194100589s
Jun 14 00:29:06.329: INFO: Pod "volume-prep-provisioning-4316": Phase="Pending", Reason="", readiness=false. Elapsed: 4.292409044s
Jun 14 00:29:08.427: INFO: Pod "volume-prep-provisioning-4316": Phase="Pending", Reason="", readiness=false. Elapsed: 6.390365101s
Jun 14 00:29:10.524: INFO: Pod "volume-prep-provisioning-4316": Phase="Pending", Reason="", readiness=false. Elapsed: 8.487926589s
Jun 14 00:29:12.622: INFO: Pod "volume-prep-provisioning-4316": Phase="Pending", Reason="", readiness=false. Elapsed: 10.585628756s
Jun 14 00:29:14.719: INFO: Pod "volume-prep-provisioning-4316": Phase="Pending", Reason="", readiness=false. Elapsed: 12.683092881s
Jun 14 00:29:16.818: INFO: Pod "volume-prep-provisioning-4316": Phase="Pending", Reason="", readiness=false. Elapsed: 14.781265012s
Jun 14 00:29:18.915: INFO: Pod "volume-prep-provisioning-4316": Phase="Pending", Reason="", readiness=false. Elapsed: 16.878824194s
Jun 14 00:29:21.013: INFO: Pod "volume-prep-provisioning-4316": Phase="Pending", Reason="", readiness=false. Elapsed: 18.976605867s
Jun 14 00:29:23.116: INFO: Pod "volume-prep-provisioning-4316": Phase="Pending", Reason="", readiness=false. Elapsed: 21.079404294s
Jun 14 00:29:25.214: INFO: Pod "volume-prep-provisioning-4316": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.17747802s
STEP: Saw pod success
Jun 14 00:29:25.214: INFO: Pod "volume-prep-provisioning-4316" satisfied condition "Succeeded or Failed"
Jun 14 00:29:25.214: INFO: Deleting pod "volume-prep-provisioning-4316" in namespace "provisioning-4316"
Jun 14 00:29:25.315: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-4316" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-26wz
STEP: Checking for subpath error in container status
Jun 14 00:29:59.715: INFO: Deleting pod "pod-subpath-test-dynamicpv-26wz" in namespace "provisioning-4316"
Jun 14 00:29:59.818: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-26wz" to be fully deleted
STEP: Deleting pod
Jun 14 00:29:59.915: INFO: Deleting pod "pod-subpath-test-dynamicpv-26wz" in namespace "provisioning-4316"
STEP: Deleting pvc
Jun 14 00:30:00.217: INFO: Deleting PersistentVolumeClaim "awskkbnk"
... skipping 131 lines ...
Jun 14 00:28:47.554: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-8211-e2e-scmknkc      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-8211    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-8211-e2e-scmknkc,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-8211    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-8211-e2e-scmknkc,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-8211    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-8211-e2e-scmknkc,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-8211-e2e-scmknkc    e1f2c2a4-76e1-446f-9aea-335591a26e29 12858 0 2021-06-14 00:28:47 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-14 00:28:47 +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-w4brf pvc- provisioning-8211  22c7203b-e5f8-412c-aeac-f64adfb60347 12863 0 2021-06-14 00:28:48 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-14 00:28:48 +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-8211-e2e-scmknkc,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-6fc56700-7bdb-498f-b509-924ed6a1e8d3 in namespace provisioning-8211
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun 14 00:29:02.622: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-szrjb" in namespace "provisioning-8211" to be "Succeeded or Failed"
Jun 14 00:29:02.718: INFO: Pod "pvc-volume-tester-writer-szrjb": Phase="Pending", Reason="", readiness=false. Elapsed: 96.334567ms
Jun 14 00:29:04.815: INFO: Pod "pvc-volume-tester-writer-szrjb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.192795369s
Jun 14 00:29:06.912: INFO: Pod "pvc-volume-tester-writer-szrjb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.290047504s
Jun 14 00:29:09.009: INFO: Pod "pvc-volume-tester-writer-szrjb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.386555759s
Jun 14 00:29:11.106: INFO: Pod "pvc-volume-tester-writer-szrjb": Phase="Pending", Reason="", readiness=false. Elapsed: 8.483668851s
Jun 14 00:29:13.203: INFO: Pod "pvc-volume-tester-writer-szrjb": Phase="Pending", Reason="", readiness=false. Elapsed: 10.580527026s
... skipping 6 lines ...
Jun 14 00:29:27.917: INFO: Pod "pvc-volume-tester-writer-szrjb": Phase="Pending", Reason="", readiness=false. Elapsed: 25.294432313s
Jun 14 00:29:30.013: INFO: Pod "pvc-volume-tester-writer-szrjb": Phase="Pending", Reason="", readiness=false. Elapsed: 27.390857546s
Jun 14 00:29:32.112: INFO: Pod "pvc-volume-tester-writer-szrjb": Phase="Pending", Reason="", readiness=false. Elapsed: 29.490326328s
Jun 14 00:29:34.210: INFO: Pod "pvc-volume-tester-writer-szrjb": Phase="Pending", Reason="", readiness=false. Elapsed: 31.587624219s
Jun 14 00:29:36.307: INFO: Pod "pvc-volume-tester-writer-szrjb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 33.685121308s
STEP: Saw pod success
Jun 14 00:29:36.307: INFO: Pod "pvc-volume-tester-writer-szrjb" satisfied condition "Succeeded or Failed"
Jun 14 00:29:36.509: INFO: Pod pvc-volume-tester-writer-szrjb has the following logs: 
Jun 14 00:29:36.509: INFO: Deleting pod "pvc-volume-tester-writer-szrjb" in namespace "provisioning-8211"
Jun 14 00:29:36.614: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-szrjb" 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-60-182.eu-west-2.compute.internal"
Jun 14 00:29:37.004: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-dx84l" in namespace "provisioning-8211" to be "Succeeded or Failed"
Jun 14 00:29:37.100: INFO: Pod "pvc-volume-tester-reader-dx84l": Phase="Pending", Reason="", readiness=false. Elapsed: 96.17333ms
Jun 14 00:29:39.197: INFO: Pod "pvc-volume-tester-reader-dx84l": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.192682483s
STEP: Saw pod success
Jun 14 00:29:39.197: INFO: Pod "pvc-volume-tester-reader-dx84l" satisfied condition "Succeeded or Failed"
Jun 14 00:29:39.390: INFO: Pod pvc-volume-tester-reader-dx84l has the following logs: hello world

Jun 14 00:29:39.390: INFO: Deleting pod "pvc-volume-tester-reader-dx84l" in namespace "provisioning-8211"
Jun 14 00:29:39.493: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-dx84l" to be fully deleted
Jun 14 00:29:39.589: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-w4brf] to have phase Bound
Jun 14 00:29:39.687: INFO: PersistentVolumeClaim pvc-w4brf found and phase=Bound (98.677585ms)
... skipping 128 lines ...
Jun 14 00:29:17.937: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6111-e2e-sc6l56h
STEP: creating a claim
Jun 14 00:29:18.037: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-pqqn
STEP: Creating a pod to test subpath
Jun 14 00:29:18.328: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-pqqn" in namespace "provisioning-6111" to be "Succeeded or Failed"
Jun 14 00:29:18.424: INFO: Pod "pod-subpath-test-dynamicpv-pqqn": Phase="Pending", Reason="", readiness=false. Elapsed: 95.554663ms
Jun 14 00:29:20.520: INFO: Pod "pod-subpath-test-dynamicpv-pqqn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.192314064s
Jun 14 00:29:22.617: INFO: Pod "pod-subpath-test-dynamicpv-pqqn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.288802443s
Jun 14 00:29:24.713: INFO: Pod "pod-subpath-test-dynamicpv-pqqn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.384640351s
Jun 14 00:29:26.810: INFO: Pod "pod-subpath-test-dynamicpv-pqqn": Phase="Pending", Reason="", readiness=false. Elapsed: 8.481719446s
Jun 14 00:29:28.907: INFO: Pod "pod-subpath-test-dynamicpv-pqqn": Phase="Pending", Reason="", readiness=false. Elapsed: 10.5791747s
... skipping 2 lines ...
Jun 14 00:29:35.201: INFO: Pod "pod-subpath-test-dynamicpv-pqqn": Phase="Pending", Reason="", readiness=false. Elapsed: 16.872536175s
Jun 14 00:29:37.297: INFO: Pod "pod-subpath-test-dynamicpv-pqqn": Phase="Pending", Reason="", readiness=false. Elapsed: 18.9686939s
Jun 14 00:29:39.394: INFO: Pod "pod-subpath-test-dynamicpv-pqqn": Phase="Pending", Reason="", readiness=false. Elapsed: 21.065532301s
Jun 14 00:29:41.492: INFO: Pod "pod-subpath-test-dynamicpv-pqqn": Phase="Pending", Reason="", readiness=false. Elapsed: 23.163708469s
Jun 14 00:29:43.588: INFO: Pod "pod-subpath-test-dynamicpv-pqqn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 25.259974344s
STEP: Saw pod success
Jun 14 00:29:43.588: INFO: Pod "pod-subpath-test-dynamicpv-pqqn" satisfied condition "Succeeded or Failed"
Jun 14 00:29:43.684: INFO: Trying to get logs from node ip-172-20-34-37.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-pqqn container test-container-volume-dynamicpv-pqqn: <nil>
STEP: delete the pod
Jun 14 00:29:43.882: INFO: Waiting for pod pod-subpath-test-dynamicpv-pqqn to disappear
Jun 14 00:29:43.978: INFO: Pod pod-subpath-test-dynamicpv-pqqn no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-pqqn
Jun 14 00:29:43.978: INFO: Deleting pod "pod-subpath-test-dynamicpv-pqqn" in namespace "provisioning-6111"
... skipping 71 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 14 00:29:50.075: 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.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 14 00:29:50.560: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 14 00:29:50.925: INFO: Successfully created a new PD: "aws://eu-west-2a/vol-09ba4b73df1138add".
Jun 14 00:29:50.925: INFO: Creating resource for pre-provisioned PV
Jun 14 00:29:50.925: INFO: Creating PVC and PV
... skipping 7 lines ...
Jun 14 00:29:59.667: INFO: PersistentVolumeClaim pvc-875wf found but phase is Pending instead of Bound.
Jun 14 00:30:01.765: INFO: PersistentVolumeClaim pvc-875wf found but phase is Pending instead of Bound.
Jun 14 00:30:03.863: INFO: PersistentVolumeClaim pvc-875wf found and phase=Bound (12.679082539s)
Jun 14 00:30:03.863: INFO: Waiting up to 3m0s for PersistentVolume aws-n96kq to have phase Bound
Jun 14 00:30:03.959: INFO: PersistentVolume aws-n96kq found and phase=Bound (96.406353ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 14 00:30:06.539: INFO: Deleting pod "pod-b991ed75-b78d-48a3-bd78-0545cbcfe564" in namespace "volumemode-3718"
Jun 14 00:30:06.637: INFO: Wait up to 5m0s for pod "pod-b991ed75-b78d-48a3-bd78-0545cbcfe564" to be fully deleted
STEP: Deleting pv and pvc
Jun 14 00:30:10.829: INFO: Deleting PersistentVolumeClaim "pvc-875wf"
Jun 14 00:30:10.926: INFO: Deleting PersistentVolume "aws-n96kq"
Jun 14 00:30:11.253: INFO: Couldn't delete PD "aws://eu-west-2a/vol-09ba4b73df1138add", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-09ba4b73df1138add is currently attached to i-068ab7d6aa6e1db55
	status code: 400, request id: 2d705180-1426-46d4-aa74-07deebc02618
Jun 14 00:30:16.770: INFO: Couldn't delete PD "aws://eu-west-2a/vol-09ba4b73df1138add", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-09ba4b73df1138add is currently attached to i-068ab7d6aa6e1db55
	status code: 400, request id: 671c6e2b-7c6f-4960-8b7b-d724d8e4721b
Jun 14 00:30:22.285: INFO: Couldn't delete PD "aws://eu-west-2a/vol-09ba4b73df1138add", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-09ba4b73df1138add is currently attached to i-068ab7d6aa6e1db55
	status code: 400, request id: ed97be9a-17fb-4503-9f12-08cbd0ec3f09
Jun 14 00:30:27.825: INFO: Couldn't delete PD "aws://eu-west-2a/vol-09ba4b73df1138add", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-09ba4b73df1138add is currently attached to i-068ab7d6aa6e1db55
	status code: 400, request id: 0ae15d6f-65e0-4de9-9a0d-3e878ef1496f
Jun 14 00:30:33.361: INFO: Successfully deleted PD "aws://eu-west-2a/vol-09ba4b73df1138add".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 14 00:30:33.361: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-3718" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.FO5ImxMAG/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.FO5ImxMAG/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
    /tmp/kops.FO5ImxMAG/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.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 230 lines ...
Jun 14 00:29:39.647: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-51192l22f
STEP: creating a claim
Jun 14 00:29:39.744: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-hndk
STEP: Creating a pod to test subpath
Jun 14 00:29:40.040: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-hndk" in namespace "provisioning-5119" to be "Succeeded or Failed"
Jun 14 00:29:40.137: INFO: Pod "pod-subpath-test-dynamicpv-hndk": Phase="Pending", Reason="", readiness=false. Elapsed: 96.619181ms
Jun 14 00:29:42.239: INFO: Pod "pod-subpath-test-dynamicpv-hndk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.19866512s
Jun 14 00:29:44.338: INFO: Pod "pod-subpath-test-dynamicpv-hndk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.297508396s
Jun 14 00:29:46.436: INFO: Pod "pod-subpath-test-dynamicpv-hndk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.396080796s
Jun 14 00:29:48.534: INFO: Pod "pod-subpath-test-dynamicpv-hndk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.493546729s
Jun 14 00:29:50.631: INFO: Pod "pod-subpath-test-dynamicpv-hndk": Phase="Pending", Reason="", readiness=false. Elapsed: 10.591088141s
... skipping 9 lines ...
Jun 14 00:30:11.608: INFO: Pod "pod-subpath-test-dynamicpv-hndk": Phase="Pending", Reason="", readiness=false. Elapsed: 31.567320113s
Jun 14 00:30:13.705: INFO: Pod "pod-subpath-test-dynamicpv-hndk": Phase="Pending", Reason="", readiness=false. Elapsed: 33.664989052s
Jun 14 00:30:15.802: INFO: Pod "pod-subpath-test-dynamicpv-hndk": Phase="Pending", Reason="", readiness=false. Elapsed: 35.762075538s
Jun 14 00:30:17.900: INFO: Pod "pod-subpath-test-dynamicpv-hndk": Phase="Pending", Reason="", readiness=false. Elapsed: 37.859926801s
Jun 14 00:30:19.998: INFO: Pod "pod-subpath-test-dynamicpv-hndk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 39.957739648s
STEP: Saw pod success
Jun 14 00:30:19.998: INFO: Pod "pod-subpath-test-dynamicpv-hndk" satisfied condition "Succeeded or Failed"
Jun 14 00:30:20.095: INFO: Trying to get logs from node ip-172-20-60-182.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-hndk container test-container-subpath-dynamicpv-hndk: <nil>
STEP: delete the pod
Jun 14 00:30:20.321: INFO: Waiting for pod pod-subpath-test-dynamicpv-hndk to disappear
Jun 14 00:30:20.418: INFO: Pod pod-subpath-test-dynamicpv-hndk no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-hndk
Jun 14 00:30:20.418: INFO: Deleting pod "pod-subpath-test-dynamicpv-hndk" in namespace "provisioning-5119"
... skipping 232 lines ...
Jun 14 00:31:11.649: INFO: Waiting for pod aws-client to disappear
Jun 14 00:31:11.746: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 14 00:31:11.747: INFO: Deleting PersistentVolumeClaim "pvc-znmzs"
Jun 14 00:31:11.845: INFO: Deleting PersistentVolume "aws-z6cmj"
Jun 14 00:31:12.435: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0fd24ae20607d9c72", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0fd24ae20607d9c72 is currently attached to i-02d9eae89c0612df4
	status code: 400, request id: 0ee2367e-f5bd-49fb-b7ce-e03cd0e0604b
Jun 14 00:31:17.988: INFO: Successfully deleted PD "aws://eu-west-2a/vol-0fd24ae20607d9c72".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumes
  /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 14 00:31:17.988: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-7211" for this suite.
... skipping 429 lines ...
    /tmp/kops.FO5ImxMAG/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volume_expand.go:174
------------------------------


Summarizing 1 Failure:

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

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


Ginkgo ran 1 suite in 13m14.078474192s
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
I0614 00:34:12.868088   32085 app.go:59] RunDir for this run: "/logs/artifacts/49dcce5e-cca4-11eb-ab6f-62c732df09e9"
I0614 00:34:12.868254   32085 app.go:90] ID for this run: "49dcce5e-cca4-11eb-ab6f-62c732df09e9"
I0614 00:34:12.868284   32085 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
I0614 00:34:12.884633   32091 featureflag.go:167] FeatureFlag "SpecOverrideFlag"=true
... skipping 1431 lines ...