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

No Test Failures!


Error lines from build-log.txt

... skipping 497 lines ...
I0610 16:10:27.108697   12434 up.go:43] Cleaning up any leaked resources from previous cluster
I0610 16:10:27.108716   12434 dumplogs.go:38] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops toolbox dump --name e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ubuntu
I0610 16:10:27.129699   12440 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0610 16:10:27.129901   12440 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io" not found
W0610 16:10:27.772914   12434 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0610 16:10:27.772964   12434 down.go:48] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops delete cluster --name e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --yes
I0610 16:10:27.787892   12450 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0610 16:10:27.787992   12450 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io" not found
I0610 16:10:28.345136   12434 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/06/10 16:10:28 failed to get external ip from metadata service: http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip returned 404
I0610 16:10:28.354926   12434 http.go:37] curl https://ip.jsb.workers.dev
I0610 16:10:28.556471   12434 up.go:144] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops create cluster --name e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --cloud aws --kubernetes-version 1.21.0 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --networking calico --override=cluster.spec.cloudConfig.awsEBSCSIDriver.enabled=true --override=cluster.spec.snapshotController.enabled=true --override=cluster.spec.certManager.enabled=true --admin-access 34.67.170.7/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones eu-west-3a --master-size c5.large
I0610 16:10:28.570537   12464 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0610 16:10:28.570623   12464 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I0610 16:10:28.626456   12464 create_cluster.go:728] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0610 16:10:29.322044   12464 new_cluster.go:1039]  Cloud Provider ID = aws
... skipping 40 lines ...

I0610 16:10:57.314927   12434 up.go:181] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops validate cluster --name e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0610 16:10:57.331347   12484 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0610 16:10:57.331579   12484 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io

W0610 16:10:58.713794   12484 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
W0610 16:11:08.768423   12484 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0610 16:11:48.984338   12484 validate_cluster.go:221] (will retry): cluster not yet healthy
W0610 16:11:59.030707   12484 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
W0610 16:12:09.066474   12484 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
W0610 16:12:19.126502   12484 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0610 16:12:59.310930   12484 validate_cluster.go:221] (will retry): cluster not yet healthy
W0610 16:13:09.330347   12484 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0610 16:15:40.108629   12484 validate_cluster.go:221] (will retry): cluster not yet healthy
W0610 16:15:50.126612   12484 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0610 16:16:00.169472   12484 validate_cluster.go:221] (will retry): cluster not yet healthy
W0610 16:16:40.225957   12484 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 203.0.113.123:443: i/o timeout
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

NODE STATUS
... skipping 19 lines ...
Pod	kube-system/ebs-csi-node-2h9pl						system-node-critical pod "ebs-csi-node-2h9pl" is pending
Pod	kube-system/ebs-csi-node-945cs						system-node-critical pod "ebs-csi-node-945cs" is pending
Pod	kube-system/ebs-csi-node-hnpnj						system-node-critical pod "ebs-csi-node-hnpnj" is pending
Pod	kube-system/ebs-csi-node-q8x7j						system-node-critical pod "ebs-csi-node-q8x7j" is pending
Pod	kube-system/kube-proxy-ip-172-20-33-176.eu-west-3.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-33-176.eu-west-3.compute.internal" is pending

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

... skipping 17 lines ...
Pod	kube-system/cert-manager-cainjector-74d69756d5-cc8pg	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-cc8pg" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-txdmn	system-cluster-critical pod "cert-manager-webhook-7bbf67968-txdmn" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-whmjg		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-whmjg" is pending
Pod	kube-system/coredns-f45c4bf76-kbdzw			system-cluster-critical pod "coredns-f45c4bf76-kbdzw" is pending
Pod	kube-system/ebs-csi-node-945cs				system-node-critical pod "ebs-csi-node-945cs" is pending

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

... skipping 7 lines ...

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

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

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

      Distro debian doesn't support ntfs -- skipping

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.qtJkPBBMp/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.qtJkPBBMp/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.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 229 lines ...
STEP: Creating a kubernetes client
Jun 10 16:20:44.383: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename topology
W0610 16:20:45.672750   26485 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Jun 10 16:20:45.672: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail to schedule a pod which has topologies that conflict with AllowedTopologies
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Jun 10 16:20:46.125: INFO: found topology map[topology.kubernetes.io/zone:eu-west-3a]
Jun 10 16:20:46.125: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 10 16:20:46.125: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.qtJkPBBMp/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.qtJkPBBMp/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (immediate binding)] topology
    /tmp/kops.qtJkPBBMp/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.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

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

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

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

    /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 63 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 16:20:45.629: 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.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 10 16:20:47.898: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 10 16:20:48.683: INFO: Successfully created a new PD: "aws://eu-west-3a/vol-0656345e45b822f44".
Jun 10 16:20:48.683: INFO: Creating resource for pre-provisioned PV
Jun 10 16:20:48.683: INFO: Creating PVC and PV
... skipping 2 lines ...
Jun 10 16:20:48.979: INFO: Waiting up to timeout=3m0s for PersistentVolumeClaims [pvc-nxgs5] to have phase Bound
Jun 10 16:20:49.093: INFO: PersistentVolumeClaim pvc-nxgs5 found but phase is Pending instead of Bound.
Jun 10 16:20:51.206: INFO: PersistentVolumeClaim pvc-nxgs5 found and phase=Bound (2.226910991s)
Jun 10 16:20:51.206: INFO: Waiting up to 3m0s for PersistentVolume aws-b572v to have phase Bound
Jun 10 16:20:51.319: INFO: PersistentVolume aws-b572v found and phase=Bound (113.154268ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 10 16:20:54.008: INFO: Deleting pod "pod-fda2a9aa-0874-46bd-9275-59369628f251" in namespace "volumemode-3535"
Jun 10 16:20:54.125: INFO: Wait up to 5m0s for pod "pod-fda2a9aa-0874-46bd-9275-59369628f251" to be fully deleted
STEP: Deleting pv and pvc
Jun 10 16:21:00.355: INFO: Deleting PersistentVolumeClaim "pvc-nxgs5"
Jun 10 16:21:00.471: INFO: Deleting PersistentVolume "aws-b572v"
Jun 10 16:21:00.817: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0656345e45b822f44", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0656345e45b822f44 is currently attached to i-06d0c497d76e91d1f
	status code: 400, request id: 88cff9ef-a95b-4f67-9d2f-62e353b8dda0
Jun 10 16:21:06.425: INFO: Successfully deleted PD "aws://eu-west-3a/vol-0656345e45b822f44".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 10 16:21:06.425: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-3535" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.qtJkPBBMp/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.qtJkPBBMp/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
    /tmp/kops.qtJkPBBMp/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.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 10 16:21:06.657: INFO: Driver "ebs.csi.aws.com" does not support volume type "PreprovisionedPV" - skipping
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
... skipping 2 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.qtJkPBBMp/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.qtJkPBBMp/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.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 13 lines ...
Jun 10 16:20:45.221: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-2309-e2e-sc9cpsc
STEP: creating a claim
Jun 10 16:20:45.346: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Jun 10 16:20:45.579: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 10 16:20:45.811: INFO: Error updating pvc ebs.csi.aws.comcg66t: PersistentVolumeClaim "ebs.csi.aws.comcg66t" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2309-e2e-sc9cpsc",
  	... // 2 identical fields
  }

Jun 10 16:20:48.041: INFO: Error updating pvc ebs.csi.aws.comcg66t: PersistentVolumeClaim "ebs.csi.aws.comcg66t" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2309-e2e-sc9cpsc",
  	... // 2 identical fields
  }

Jun 10 16:20:50.040: INFO: Error updating pvc ebs.csi.aws.comcg66t: PersistentVolumeClaim "ebs.csi.aws.comcg66t" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2309-e2e-sc9cpsc",
  	... // 2 identical fields
  }

Jun 10 16:20:52.040: INFO: Error updating pvc ebs.csi.aws.comcg66t: PersistentVolumeClaim "ebs.csi.aws.comcg66t" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2309-e2e-sc9cpsc",
  	... // 2 identical fields
  }

Jun 10 16:20:54.042: INFO: Error updating pvc ebs.csi.aws.comcg66t: PersistentVolumeClaim "ebs.csi.aws.comcg66t" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2309-e2e-sc9cpsc",
  	... // 2 identical fields
  }

Jun 10 16:20:56.039: INFO: Error updating pvc ebs.csi.aws.comcg66t: PersistentVolumeClaim "ebs.csi.aws.comcg66t" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2309-e2e-sc9cpsc",
  	... // 2 identical fields
  }

Jun 10 16:20:58.055: INFO: Error updating pvc ebs.csi.aws.comcg66t: PersistentVolumeClaim "ebs.csi.aws.comcg66t" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2309-e2e-sc9cpsc",
  	... // 2 identical fields
  }

Jun 10 16:21:00.040: INFO: Error updating pvc ebs.csi.aws.comcg66t: PersistentVolumeClaim "ebs.csi.aws.comcg66t" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2309-e2e-sc9cpsc",
  	... // 2 identical fields
  }

Jun 10 16:21:02.041: INFO: Error updating pvc ebs.csi.aws.comcg66t: PersistentVolumeClaim "ebs.csi.aws.comcg66t" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2309-e2e-sc9cpsc",
  	... // 2 identical fields
  }

Jun 10 16:21:04.042: INFO: Error updating pvc ebs.csi.aws.comcg66t: PersistentVolumeClaim "ebs.csi.aws.comcg66t" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2309-e2e-sc9cpsc",
  	... // 2 identical fields
  }

Jun 10 16:21:06.040: INFO: Error updating pvc ebs.csi.aws.comcg66t: PersistentVolumeClaim "ebs.csi.aws.comcg66t" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2309-e2e-sc9cpsc",
  	... // 2 identical fields
  }

Jun 10 16:21:08.040: INFO: Error updating pvc ebs.csi.aws.comcg66t: PersistentVolumeClaim "ebs.csi.aws.comcg66t" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2309-e2e-sc9cpsc",
  	... // 2 identical fields
  }

Jun 10 16:21:10.038: INFO: Error updating pvc ebs.csi.aws.comcg66t: PersistentVolumeClaim "ebs.csi.aws.comcg66t" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2309-e2e-sc9cpsc",
  	... // 2 identical fields
  }

Jun 10 16:21:12.042: INFO: Error updating pvc ebs.csi.aws.comcg66t: PersistentVolumeClaim "ebs.csi.aws.comcg66t" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2309-e2e-sc9cpsc",
  	... // 2 identical fields
  }

Jun 10 16:21:14.040: INFO: Error updating pvc ebs.csi.aws.comcg66t: PersistentVolumeClaim "ebs.csi.aws.comcg66t" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2309-e2e-sc9cpsc",
  	... // 2 identical fields
  }

Jun 10 16:21:16.042: INFO: Error updating pvc ebs.csi.aws.comcg66t: PersistentVolumeClaim "ebs.csi.aws.comcg66t" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2309-e2e-sc9cpsc",
  	... // 2 identical fields
  }

Jun 10 16:21:16.315: INFO: Error updating pvc ebs.csi.aws.comcg66t: PersistentVolumeClaim "ebs.csi.aws.comcg66t" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 61 lines ...
Jun 10 16:20:45.248: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-3957bvcj6
STEP: creating a claim
Jun 10 16:20:45.362: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Jun 10 16:20:45.593: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 10 16:20:45.820: INFO: Error updating pvc aws2xgjd: PersistentVolumeClaim "aws2xgjd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3957bvcj6",
  	... // 2 identical fields
  }

Jun 10 16:20:48.048: INFO: Error updating pvc aws2xgjd: PersistentVolumeClaim "aws2xgjd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3957bvcj6",
  	... // 2 identical fields
  }

Jun 10 16:20:50.053: INFO: Error updating pvc aws2xgjd: PersistentVolumeClaim "aws2xgjd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3957bvcj6",
  	... // 2 identical fields
  }

Jun 10 16:20:52.048: INFO: Error updating pvc aws2xgjd: PersistentVolumeClaim "aws2xgjd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3957bvcj6",
  	... // 2 identical fields
  }

Jun 10 16:20:54.048: INFO: Error updating pvc aws2xgjd: PersistentVolumeClaim "aws2xgjd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3957bvcj6",
  	... // 2 identical fields
  }

Jun 10 16:20:56.050: INFO: Error updating pvc aws2xgjd: PersistentVolumeClaim "aws2xgjd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3957bvcj6",
  	... // 2 identical fields
  }

Jun 10 16:20:58.055: INFO: Error updating pvc aws2xgjd: PersistentVolumeClaim "aws2xgjd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3957bvcj6",
  	... // 2 identical fields
  }

Jun 10 16:21:00.048: INFO: Error updating pvc aws2xgjd: PersistentVolumeClaim "aws2xgjd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3957bvcj6",
  	... // 2 identical fields
  }

Jun 10 16:21:02.050: INFO: Error updating pvc aws2xgjd: PersistentVolumeClaim "aws2xgjd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3957bvcj6",
  	... // 2 identical fields
  }

Jun 10 16:21:04.049: INFO: Error updating pvc aws2xgjd: PersistentVolumeClaim "aws2xgjd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3957bvcj6",
  	... // 2 identical fields
  }

Jun 10 16:21:06.052: INFO: Error updating pvc aws2xgjd: PersistentVolumeClaim "aws2xgjd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3957bvcj6",
  	... // 2 identical fields
  }

Jun 10 16:21:08.049: INFO: Error updating pvc aws2xgjd: PersistentVolumeClaim "aws2xgjd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3957bvcj6",
  	... // 2 identical fields
  }

Jun 10 16:21:10.047: INFO: Error updating pvc aws2xgjd: PersistentVolumeClaim "aws2xgjd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3957bvcj6",
  	... // 2 identical fields
  }

Jun 10 16:21:12.049: INFO: Error updating pvc aws2xgjd: PersistentVolumeClaim "aws2xgjd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3957bvcj6",
  	... // 2 identical fields
  }

Jun 10 16:21:14.049: INFO: Error updating pvc aws2xgjd: PersistentVolumeClaim "aws2xgjd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3957bvcj6",
  	... // 2 identical fields
  }

Jun 10 16:21:16.050: INFO: Error updating pvc aws2xgjd: PersistentVolumeClaim "aws2xgjd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3957bvcj6",
  	... // 2 identical fields
  }

Jun 10 16:21:16.315: INFO: Error updating pvc aws2xgjd: PersistentVolumeClaim "aws2xgjd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 57 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.qtJkPBBMp/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.qtJkPBBMp/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.qtJkPBBMp/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.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 2 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 16:20:49.612: 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.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 10 16:20:50.190: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 10 16:20:50.190: INFO: Creating resource for dynamic PV
Jun 10 16:20:50.190: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-6115mml8f
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 10 16:20:59.005: INFO: Deleting pod "pod-192cdf4b-11c4-44d9-96ef-9f88b05b9be3" in namespace "volumemode-6115"
Jun 10 16:20:59.119: INFO: Wait up to 5m0s for pod "pod-192cdf4b-11c4-44d9-96ef-9f88b05b9be3" to be fully deleted
STEP: Deleting pvc
Jun 10 16:21:11.572: INFO: Deleting PersistentVolumeClaim "awskfktb"
Jun 10 16:21:11.686: INFO: Waiting up to 5m0s for PersistentVolume pvc-43b8d907-3730-4fc2-94cf-941471f403c7 to get deleted
Jun 10 16:21:11.803: INFO: PersistentVolume pvc-43b8d907-3730-4fc2-94cf-941471f403c7 found and phase=Released (116.302298ms)
... skipping 9 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.qtJkPBBMp/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.qtJkPBBMp/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (block volmode)] volumeMode
    /tmp/kops.qtJkPBBMp/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.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [sig-storage] Storage Policy Based Volume Provisioning [Feature:vsphere]
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 16:21:17.018: INFO: >>> kubeConfig: /root/.kube/config
... skipping 112 lines ...
Jun 10 16:20:47.348: INFO: Creating resource for dynamic PV
Jun 10 16:20:47.348: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-3901-e2e-sccrhzl
STEP: creating a claim
STEP: Expanding non-expandable pvc
Jun 10 16:20:47.692: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 10 16:20:47.919: INFO: Error updating pvc ebs.csi.aws.coml9gl9: PersistentVolumeClaim "ebs.csi.aws.coml9gl9" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3901-e2e-sccrhzl",
  	... // 2 identical fields
  }

Jun 10 16:20:50.153: INFO: Error updating pvc ebs.csi.aws.coml9gl9: PersistentVolumeClaim "ebs.csi.aws.coml9gl9" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3901-e2e-sccrhzl",
  	... // 2 identical fields
  }

Jun 10 16:20:52.150: INFO: Error updating pvc ebs.csi.aws.coml9gl9: PersistentVolumeClaim "ebs.csi.aws.coml9gl9" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3901-e2e-sccrhzl",
  	... // 2 identical fields
  }

Jun 10 16:20:54.153: INFO: Error updating pvc ebs.csi.aws.coml9gl9: PersistentVolumeClaim "ebs.csi.aws.coml9gl9" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3901-e2e-sccrhzl",
  	... // 2 identical fields
  }

Jun 10 16:20:56.146: INFO: Error updating pvc ebs.csi.aws.coml9gl9: PersistentVolumeClaim "ebs.csi.aws.coml9gl9" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3901-e2e-sccrhzl",
  	... // 2 identical fields
  }

Jun 10 16:20:58.147: INFO: Error updating pvc ebs.csi.aws.coml9gl9: PersistentVolumeClaim "ebs.csi.aws.coml9gl9" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3901-e2e-sccrhzl",
  	... // 2 identical fields
  }

Jun 10 16:21:00.151: INFO: Error updating pvc ebs.csi.aws.coml9gl9: PersistentVolumeClaim "ebs.csi.aws.coml9gl9" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3901-e2e-sccrhzl",
  	... // 2 identical fields
  }

Jun 10 16:21:02.158: INFO: Error updating pvc ebs.csi.aws.coml9gl9: PersistentVolumeClaim "ebs.csi.aws.coml9gl9" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3901-e2e-sccrhzl",
  	... // 2 identical fields
  }

Jun 10 16:21:04.154: INFO: Error updating pvc ebs.csi.aws.coml9gl9: PersistentVolumeClaim "ebs.csi.aws.coml9gl9" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3901-e2e-sccrhzl",
  	... // 2 identical fields
  }

Jun 10 16:21:06.150: INFO: Error updating pvc ebs.csi.aws.coml9gl9: PersistentVolumeClaim "ebs.csi.aws.coml9gl9" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3901-e2e-sccrhzl",
  	... // 2 identical fields
  }

Jun 10 16:21:08.147: INFO: Error updating pvc ebs.csi.aws.coml9gl9: PersistentVolumeClaim "ebs.csi.aws.coml9gl9" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3901-e2e-sccrhzl",
  	... // 2 identical fields
  }

Jun 10 16:21:10.147: INFO: Error updating pvc ebs.csi.aws.coml9gl9: PersistentVolumeClaim "ebs.csi.aws.coml9gl9" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3901-e2e-sccrhzl",
  	... // 2 identical fields
  }

Jun 10 16:21:12.147: INFO: Error updating pvc ebs.csi.aws.coml9gl9: PersistentVolumeClaim "ebs.csi.aws.coml9gl9" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3901-e2e-sccrhzl",
  	... // 2 identical fields
  }

Jun 10 16:21:14.145: INFO: Error updating pvc ebs.csi.aws.coml9gl9: PersistentVolumeClaim "ebs.csi.aws.coml9gl9" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3901-e2e-sccrhzl",
  	... // 2 identical fields
  }

Jun 10 16:21:16.149: INFO: Error updating pvc ebs.csi.aws.coml9gl9: PersistentVolumeClaim "ebs.csi.aws.coml9gl9" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3901-e2e-sccrhzl",
  	... // 2 identical fields
  }

Jun 10 16:21:18.147: INFO: Error updating pvc ebs.csi.aws.coml9gl9: PersistentVolumeClaim "ebs.csi.aws.coml9gl9" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3901-e2e-sccrhzl",
  	... // 2 identical fields
  }

Jun 10 16:21:18.373: INFO: Error updating pvc ebs.csi.aws.coml9gl9: PersistentVolumeClaim "ebs.csi.aws.coml9gl9" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 71 lines ...
Jun 10 16:20:45.846: INFO: Creating resource for dynamic PV
Jun 10 16:20:45.846: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-927-e2e-scdqhrb
STEP: creating a claim
Jun 10 16:20:45.962: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-927
Jun 10 16:20:46.303: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-927" in namespace "provisioning-927" to be "Succeeded or Failed"
Jun 10 16:20:46.417: INFO: Pod "volume-prep-provisioning-927": Phase="Pending", Reason="", readiness=false. Elapsed: 114.128652ms
Jun 10 16:20:48.531: INFO: Pod "volume-prep-provisioning-927": Phase="Pending", Reason="", readiness=false. Elapsed: 2.227693817s
Jun 10 16:20:50.659: INFO: Pod "volume-prep-provisioning-927": Phase="Pending", Reason="", readiness=false. Elapsed: 4.355751683s
Jun 10 16:20:52.775: INFO: Pod "volume-prep-provisioning-927": Phase="Pending", Reason="", readiness=false. Elapsed: 6.471665337s
Jun 10 16:20:54.897: INFO: Pod "volume-prep-provisioning-927": Phase="Pending", Reason="", readiness=false. Elapsed: 8.594190229s
Jun 10 16:20:57.011: INFO: Pod "volume-prep-provisioning-927": Phase="Pending", Reason="", readiness=false. Elapsed: 10.70781974s
Jun 10 16:20:59.124: INFO: Pod "volume-prep-provisioning-927": Phase="Pending", Reason="", readiness=false. Elapsed: 12.821065246s
Jun 10 16:21:01.239: INFO: Pod "volume-prep-provisioning-927": Phase="Pending", Reason="", readiness=false. Elapsed: 14.935914875s
Jun 10 16:21:03.353: INFO: Pod "volume-prep-provisioning-927": Phase="Succeeded", Reason="", readiness=false. Elapsed: 17.049941336s
STEP: Saw pod success
Jun 10 16:21:03.353: INFO: Pod "volume-prep-provisioning-927" satisfied condition "Succeeded or Failed"
Jun 10 16:21:03.353: INFO: Deleting pod "volume-prep-provisioning-927" in namespace "provisioning-927"
Jun 10 16:21:03.473: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-927" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-gsjl
STEP: Checking for subpath error in container status
Jun 10 16:21:13.926: INFO: Deleting pod "pod-subpath-test-dynamicpv-gsjl" in namespace "provisioning-927"
Jun 10 16:21:14.044: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-gsjl" to be fully deleted
STEP: Deleting pod
Jun 10 16:21:14.156: INFO: Deleting pod "pod-subpath-test-dynamicpv-gsjl" in namespace "provisioning-927"
STEP: Deleting pvc
Jun 10 16:21:14.495: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comdrlz2"
... skipping 53 lines ...
Jun 10 16:20:49.133: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3605g96l5
STEP: creating a claim
Jun 10 16:20:49.247: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-zwqr
STEP: Creating a pod to test subpath
Jun 10 16:20:49.588: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-zwqr" in namespace "provisioning-3605" to be "Succeeded or Failed"
Jun 10 16:20:49.701: INFO: Pod "pod-subpath-test-dynamicpv-zwqr": Phase="Pending", Reason="", readiness=false. Elapsed: 112.96296ms
Jun 10 16:20:51.815: INFO: Pod "pod-subpath-test-dynamicpv-zwqr": Phase="Pending", Reason="", readiness=false. Elapsed: 2.226355846s
Jun 10 16:20:53.929: INFO: Pod "pod-subpath-test-dynamicpv-zwqr": Phase="Pending", Reason="", readiness=false. Elapsed: 4.340947406s
Jun 10 16:20:56.045: INFO: Pod "pod-subpath-test-dynamicpv-zwqr": Phase="Pending", Reason="", readiness=false. Elapsed: 6.455996207s
Jun 10 16:20:58.158: INFO: Pod "pod-subpath-test-dynamicpv-zwqr": Phase="Pending", Reason="", readiness=false. Elapsed: 8.569761887s
Jun 10 16:21:00.272: INFO: Pod "pod-subpath-test-dynamicpv-zwqr": Phase="Pending", Reason="", readiness=false. Elapsed: 10.683809616s
... skipping 2 lines ...
Jun 10 16:21:06.613: INFO: Pod "pod-subpath-test-dynamicpv-zwqr": Phase="Pending", Reason="", readiness=false. Elapsed: 17.024286536s
Jun 10 16:21:08.727: INFO: Pod "pod-subpath-test-dynamicpv-zwqr": Phase="Pending", Reason="", readiness=false. Elapsed: 19.13806625s
Jun 10 16:21:10.847: INFO: Pod "pod-subpath-test-dynamicpv-zwqr": Phase="Pending", Reason="", readiness=false. Elapsed: 21.25867874s
Jun 10 16:21:12.962: INFO: Pod "pod-subpath-test-dynamicpv-zwqr": Phase="Pending", Reason="", readiness=false. Elapsed: 23.373289394s
Jun 10 16:21:15.079: INFO: Pod "pod-subpath-test-dynamicpv-zwqr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 25.490829936s
STEP: Saw pod success
Jun 10 16:21:15.079: INFO: Pod "pod-subpath-test-dynamicpv-zwqr" satisfied condition "Succeeded or Failed"
Jun 10 16:21:15.196: INFO: Trying to get logs from node ip-172-20-33-176.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-zwqr container test-container-subpath-dynamicpv-zwqr: <nil>
STEP: delete the pod
Jun 10 16:21:15.432: INFO: Waiting for pod pod-subpath-test-dynamicpv-zwqr to disappear
Jun 10 16:21:15.545: INFO: Pod pod-subpath-test-dynamicpv-zwqr no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-zwqr
Jun 10 16:21:15.545: INFO: Deleting pod "pod-subpath-test-dynamicpv-zwqr" in namespace "provisioning-3605"
... skipping 91 lines ...
Jun 10 16:20:50.501: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1633-e2e-sckmzzk
STEP: creating a claim
Jun 10 16:20:50.617: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-dmd6
STEP: Creating a pod to test atomic-volume-subpath
Jun 10 16:20:50.980: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-dmd6" in namespace "provisioning-1633" to be "Succeeded or Failed"
Jun 10 16:20:51.094: INFO: Pod "pod-subpath-test-dynamicpv-dmd6": Phase="Pending", Reason="", readiness=false. Elapsed: 113.285756ms
Jun 10 16:20:53.208: INFO: Pod "pod-subpath-test-dynamicpv-dmd6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.227825877s
Jun 10 16:20:55.328: INFO: Pod "pod-subpath-test-dynamicpv-dmd6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.347201888s
Jun 10 16:20:57.441: INFO: Pod "pod-subpath-test-dynamicpv-dmd6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.460984416s
Jun 10 16:20:59.555: INFO: Pod "pod-subpath-test-dynamicpv-dmd6": Phase="Pending", Reason="", readiness=false. Elapsed: 8.57465533s
Jun 10 16:21:01.670: INFO: Pod "pod-subpath-test-dynamicpv-dmd6": Phase="Pending", Reason="", readiness=false. Elapsed: 10.689689161s
... skipping 13 lines ...
Jun 10 16:21:31.280: INFO: Pod "pod-subpath-test-dynamicpv-dmd6": Phase="Running", Reason="", readiness=true. Elapsed: 40.299977266s
Jun 10 16:21:33.394: INFO: Pod "pod-subpath-test-dynamicpv-dmd6": Phase="Running", Reason="", readiness=true. Elapsed: 42.413853353s
Jun 10 16:21:35.509: INFO: Pod "pod-subpath-test-dynamicpv-dmd6": Phase="Running", Reason="", readiness=true. Elapsed: 44.528550491s
Jun 10 16:21:37.623: INFO: Pod "pod-subpath-test-dynamicpv-dmd6": Phase="Running", Reason="", readiness=true. Elapsed: 46.642980689s
Jun 10 16:21:39.740: INFO: Pod "pod-subpath-test-dynamicpv-dmd6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 48.759159267s
STEP: Saw pod success
Jun 10 16:21:39.740: INFO: Pod "pod-subpath-test-dynamicpv-dmd6" satisfied condition "Succeeded or Failed"
Jun 10 16:21:39.853: INFO: Trying to get logs from node ip-172-20-48-40.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-dmd6 container test-container-subpath-dynamicpv-dmd6: <nil>
STEP: delete the pod
Jun 10 16:21:40.095: INFO: Waiting for pod pod-subpath-test-dynamicpv-dmd6 to disappear
Jun 10 16:21:40.208: INFO: Pod pod-subpath-test-dynamicpv-dmd6 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-dmd6
Jun 10 16:21:40.208: INFO: Deleting pod "pod-subpath-test-dynamicpv-dmd6" in namespace "provisioning-1633"
... skipping 30 lines ...

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.qtJkPBBMp/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.qtJkPBBMp/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.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 644 lines ...
Jun 10 16:22:06.659: INFO: Waiting for pod aws-client to disappear
Jun 10 16:22:06.778: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 10 16:22:06.778: INFO: Deleting PersistentVolumeClaim "pvc-6jkvv"
Jun 10 16:22:06.898: INFO: Deleting PersistentVolume "aws-wj67x"
Jun 10 16:22:07.606: INFO: Couldn't delete PD "aws://eu-west-3a/vol-00c7327636d8c2725", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00c7327636d8c2725 is currently attached to i-06d0c497d76e91d1f
	status code: 400, request id: b846fc24-9f02-4c38-9f85-5a72265eb250
Jun 10 16:22:13.223: INFO: Couldn't delete PD "aws://eu-west-3a/vol-00c7327636d8c2725", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00c7327636d8c2725 is currently attached to i-06d0c497d76e91d1f
	status code: 400, request id: aa593cbf-0de7-4ae0-9d92-9daa3406f807
Jun 10 16:22:18.846: INFO: Successfully deleted PD "aws://eu-west-3a/vol-00c7327636d8c2725".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 10 16:22:18.847: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-6454" for this suite.
... skipping 147 lines ...
Jun 10 16:21:57.156: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-272jlwp7
STEP: creating a claim
Jun 10 16:21:57.270: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-xcqz
STEP: Creating a pod to test subpath
Jun 10 16:21:57.613: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-xcqz" in namespace "provisioning-272" to be "Succeeded or Failed"
Jun 10 16:21:57.727: INFO: Pod "pod-subpath-test-dynamicpv-xcqz": Phase="Pending", Reason="", readiness=false. Elapsed: 113.744034ms
Jun 10 16:21:59.841: INFO: Pod "pod-subpath-test-dynamicpv-xcqz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.228308913s
Jun 10 16:22:01.956: INFO: Pod "pod-subpath-test-dynamicpv-xcqz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.342739109s
Jun 10 16:22:04.070: INFO: Pod "pod-subpath-test-dynamicpv-xcqz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.457033107s
Jun 10 16:22:06.189: INFO: Pod "pod-subpath-test-dynamicpv-xcqz": Phase="Pending", Reason="", readiness=false. Elapsed: 8.575609996s
Jun 10 16:22:08.303: INFO: Pod "pod-subpath-test-dynamicpv-xcqz": Phase="Pending", Reason="", readiness=false. Elapsed: 10.689511104s
... skipping 3 lines ...
Jun 10 16:22:16.776: INFO: Pod "pod-subpath-test-dynamicpv-xcqz": Phase="Pending", Reason="", readiness=false. Elapsed: 19.16267989s
Jun 10 16:22:18.890: INFO: Pod "pod-subpath-test-dynamicpv-xcqz": Phase="Pending", Reason="", readiness=false. Elapsed: 21.276896417s
Jun 10 16:22:21.005: INFO: Pod "pod-subpath-test-dynamicpv-xcqz": Phase="Pending", Reason="", readiness=false. Elapsed: 23.392075421s
Jun 10 16:22:23.119: INFO: Pod "pod-subpath-test-dynamicpv-xcqz": Phase="Pending", Reason="", readiness=false. Elapsed: 25.505929542s
Jun 10 16:22:25.237: INFO: Pod "pod-subpath-test-dynamicpv-xcqz": Phase="Succeeded", Reason="", readiness=false. Elapsed: 27.6238096s
STEP: Saw pod success
Jun 10 16:22:25.237: INFO: Pod "pod-subpath-test-dynamicpv-xcqz" satisfied condition "Succeeded or Failed"
Jun 10 16:22:25.357: INFO: Trying to get logs from node ip-172-20-43-141.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-xcqz container test-container-volume-dynamicpv-xcqz: <nil>
STEP: delete the pod
Jun 10 16:22:25.599: INFO: Waiting for pod pod-subpath-test-dynamicpv-xcqz to disappear
Jun 10 16:22:25.713: INFO: Pod pod-subpath-test-dynamicpv-xcqz no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-xcqz
Jun 10 16:22:25.713: INFO: Deleting pod "pod-subpath-test-dynamicpv-xcqz" in namespace "provisioning-272"
... skipping 875 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 16:22:09.139: 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.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun 10 16:22:09.707: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 10 16:22:09.707: INFO: Creating resource for dynamic PV
Jun 10 16:22:09.707: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3975q8s5s
STEP: creating a claim
Jun 10 16:22:09.821: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-btwh
STEP: Checking for subpath error in container status
Jun 10 16:22:24.409: INFO: Deleting pod "pod-subpath-test-dynamicpv-btwh" in namespace "provisioning-3975"
Jun 10 16:22:24.523: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-btwh" to be fully deleted
STEP: Deleting pod
Jun 10 16:22:36.752: INFO: Deleting pod "pod-subpath-test-dynamicpv-btwh" in namespace "provisioning-3975"
STEP: Deleting pvc
Jun 10 16:22:37.093: INFO: Deleting PersistentVolumeClaim "awsnxzxz"
... skipping 13 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.qtJkPBBMp/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.qtJkPBBMp/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.qtJkPBBMp/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.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ext4)] volumes
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (ext4)] volumes
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 132 lines ...
Jun 10 16:22:13.090: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-476j74z5
STEP: creating a claim
Jun 10 16:22:13.206: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-xxhj
STEP: Creating a pod to test exec-volume-test
Jun 10 16:22:13.549: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-xxhj" in namespace "volume-476" to be "Succeeded or Failed"
Jun 10 16:22:13.663: INFO: Pod "exec-volume-test-dynamicpv-xxhj": Phase="Pending", Reason="", readiness=false. Elapsed: 113.715795ms
Jun 10 16:22:15.778: INFO: Pod "exec-volume-test-dynamicpv-xxhj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.228400664s
Jun 10 16:22:17.892: INFO: Pod "exec-volume-test-dynamicpv-xxhj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.342519069s
Jun 10 16:22:20.009: INFO: Pod "exec-volume-test-dynamicpv-xxhj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.459710132s
Jun 10 16:22:22.124: INFO: Pod "exec-volume-test-dynamicpv-xxhj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.575121743s
Jun 10 16:22:24.242: INFO: Pod "exec-volume-test-dynamicpv-xxhj": Phase="Pending", Reason="", readiness=false. Elapsed: 10.692202811s
Jun 10 16:22:26.356: INFO: Pod "exec-volume-test-dynamicpv-xxhj": Phase="Pending", Reason="", readiness=false. Elapsed: 12.806574762s
Jun 10 16:22:28.471: INFO: Pod "exec-volume-test-dynamicpv-xxhj": Phase="Pending", Reason="", readiness=false. Elapsed: 14.921496623s
Jun 10 16:22:30.586: INFO: Pod "exec-volume-test-dynamicpv-xxhj": Phase="Pending", Reason="", readiness=false. Elapsed: 17.036296263s
Jun 10 16:22:32.700: INFO: Pod "exec-volume-test-dynamicpv-xxhj": Phase="Pending", Reason="", readiness=false. Elapsed: 19.150794232s
Jun 10 16:22:34.815: INFO: Pod "exec-volume-test-dynamicpv-xxhj": Phase="Pending", Reason="", readiness=false. Elapsed: 21.26521647s
Jun 10 16:22:36.930: INFO: Pod "exec-volume-test-dynamicpv-xxhj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.380396859s
STEP: Saw pod success
Jun 10 16:22:36.930: INFO: Pod "exec-volume-test-dynamicpv-xxhj" satisfied condition "Succeeded or Failed"
Jun 10 16:22:37.044: INFO: Trying to get logs from node ip-172-20-33-176.eu-west-3.compute.internal pod exec-volume-test-dynamicpv-xxhj container exec-container-dynamicpv-xxhj: <nil>
STEP: delete the pod
Jun 10 16:22:37.280: INFO: Waiting for pod exec-volume-test-dynamicpv-xxhj to disappear
Jun 10 16:22:37.394: INFO: Pod exec-volume-test-dynamicpv-xxhj no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-xxhj
Jun 10 16:22:37.394: INFO: Deleting pod "exec-volume-test-dynamicpv-xxhj" in namespace "volume-476"
... skipping 76 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.qtJkPBBMp/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.qtJkPBBMp/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.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 784 lines ...
Jun 10 16:22:52.488: INFO: Pod aws-client still exists
Jun 10 16:22:54.374: INFO: Waiting for pod aws-client to disappear
Jun 10 16:22:54.488: INFO: Pod aws-client still exists
Jun 10 16:22:56.375: INFO: Waiting for pod aws-client to disappear
Jun 10 16:22:56.489: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun 10 16:22:57.101: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0fed69cb39283b448", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0fed69cb39283b448 is currently attached to i-06d0c497d76e91d1f
	status code: 400, request id: 442796ee-63a7-4ac6-ae6d-10edfc38578f
Jun 10 16:23:02.712: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0fed69cb39283b448", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0fed69cb39283b448 is currently attached to i-06d0c497d76e91d1f
	status code: 400, request id: 7920e36c-97ab-4ba6-8f94-4953d2fda5d9
Jun 10 16:23:08.337: INFO: Successfully deleted PD "aws://eu-west-3a/vol-0fed69cb39283b448".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 10 16:23:08.337: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-1046" for this suite.
... skipping 58 lines ...
Jun 10 16:22:49.678: INFO: PersistentVolumeClaim pvc-xk65j found but phase is Pending instead of Bound.
Jun 10 16:22:51.792: INFO: PersistentVolumeClaim pvc-xk65j found and phase=Bound (12.798058294s)
Jun 10 16:22:51.792: INFO: Waiting up to 3m0s for PersistentVolume aws-j7xkz to have phase Bound
Jun 10 16:22:51.905: INFO: PersistentVolume aws-j7xkz found and phase=Bound (113.371052ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-shrk
STEP: Creating a pod to test exec-volume-test
Jun 10 16:22:52.247: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-shrk" in namespace "volume-5981" to be "Succeeded or Failed"
Jun 10 16:22:52.361: INFO: Pod "exec-volume-test-preprovisionedpv-shrk": Phase="Pending", Reason="", readiness=false. Elapsed: 113.763342ms
Jun 10 16:22:54.475: INFO: Pod "exec-volume-test-preprovisionedpv-shrk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.228046168s
Jun 10 16:22:56.590: INFO: Pod "exec-volume-test-preprovisionedpv-shrk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.34316595s
Jun 10 16:22:58.710: INFO: Pod "exec-volume-test-preprovisionedpv-shrk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.462301809s
Jun 10 16:23:00.824: INFO: Pod "exec-volume-test-preprovisionedpv-shrk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.576406285s
Jun 10 16:23:02.939: INFO: Pod "exec-volume-test-preprovisionedpv-shrk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.691982404s
STEP: Saw pod success
Jun 10 16:23:02.939: INFO: Pod "exec-volume-test-preprovisionedpv-shrk" satisfied condition "Succeeded or Failed"
Jun 10 16:23:03.053: INFO: Trying to get logs from node ip-172-20-43-141.eu-west-3.compute.internal pod exec-volume-test-preprovisionedpv-shrk container exec-container-preprovisionedpv-shrk: <nil>
STEP: delete the pod
Jun 10 16:23:03.293: INFO: Waiting for pod exec-volume-test-preprovisionedpv-shrk to disappear
Jun 10 16:23:03.406: INFO: Pod exec-volume-test-preprovisionedpv-shrk no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-shrk
Jun 10 16:23:03.406: INFO: Deleting pod "exec-volume-test-preprovisionedpv-shrk" in namespace "volume-5981"
STEP: Deleting pv and pvc
Jun 10 16:23:03.520: INFO: Deleting PersistentVolumeClaim "pvc-xk65j"
Jun 10 16:23:03.634: INFO: Deleting PersistentVolume "aws-j7xkz"
Jun 10 16:23:04.018: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0e085dac47de959b6", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e085dac47de959b6 is currently attached to i-07d39bd358d68e328
	status code: 400, request id: 8b75b22c-a959-45f5-a94b-dcbbae295b4b
Jun 10 16:23:09.642: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0e085dac47de959b6", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e085dac47de959b6 is currently attached to i-07d39bd358d68e328
	status code: 400, request id: 4bf77797-04cd-4998-9a43-3c6c0bb767fa
Jun 10 16:23:15.245: INFO: Successfully deleted PD "aws://eu-west-3a/vol-0e085dac47de959b6".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 10 16:23:15.245: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-5981" for this suite.
... skipping 26 lines ...
Jun 10 16:20:45.210: INFO: Creating resource for dynamic PV
Jun 10 16:20:45.210: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-9420-e2e-sc4m2fz
STEP: creating a claim
Jun 10 16:20:45.325: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 10 16:20:45.666: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-xcwvb" in namespace "snapshotting-9420" to be "Succeeded or Failed"
Jun 10 16:20:45.782: INFO: Pod "pvc-snapshottable-tester-xcwvb": Phase="Pending", Reason="", readiness=false. Elapsed: 115.897905ms
Jun 10 16:20:47.912: INFO: Pod "pvc-snapshottable-tester-xcwvb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.245373593s
Jun 10 16:20:50.026: INFO: Pod "pvc-snapshottable-tester-xcwvb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.359311187s
Jun 10 16:20:52.141: INFO: Pod "pvc-snapshottable-tester-xcwvb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.474504854s
Jun 10 16:20:54.257: INFO: Pod "pvc-snapshottable-tester-xcwvb": Phase="Pending", Reason="", readiness=false. Elapsed: 8.5901001s
Jun 10 16:20:56.371: INFO: Pod "pvc-snapshottable-tester-xcwvb": Phase="Pending", Reason="", readiness=false. Elapsed: 10.704537452s
Jun 10 16:20:58.485: INFO: Pod "pvc-snapshottable-tester-xcwvb": Phase="Pending", Reason="", readiness=false. Elapsed: 12.818669678s
Jun 10 16:21:00.599: INFO: Pod "pvc-snapshottable-tester-xcwvb": Phase="Pending", Reason="", readiness=false. Elapsed: 14.932611835s
Jun 10 16:21:02.712: INFO: Pod "pvc-snapshottable-tester-xcwvb": Phase="Pending", Reason="", readiness=false. Elapsed: 17.045750199s
Jun 10 16:21:04.826: INFO: Pod "pvc-snapshottable-tester-xcwvb": Phase="Pending", Reason="", readiness=false. Elapsed: 19.159536356s
Jun 10 16:21:06.939: INFO: Pod "pvc-snapshottable-tester-xcwvb": Phase="Pending", Reason="", readiness=false. Elapsed: 21.272837938s
Jun 10 16:21:09.052: INFO: Pod "pvc-snapshottable-tester-xcwvb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.386039886s
STEP: Saw pod success
Jun 10 16:21:09.053: INFO: Pod "pvc-snapshottable-tester-xcwvb" satisfied condition "Succeeded or Failed"
Jun 10 16:21:09.322: INFO: Pod pvc-snapshottable-tester-xcwvb has the following logs: 
Jun 10 16:21:09.322: INFO: Deleting pod "pvc-snapshottable-tester-xcwvb" in namespace "snapshotting-9420"
Jun 10 16:21:09.441: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-xcwvb" to be fully deleted
Jun 10 16:21:09.553: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comrp5h6] to have phase Bound
Jun 10 16:21:09.667: INFO: PersistentVolumeClaim ebs.csi.aws.comrp5h6 found and phase=Bound (113.073856ms)
STEP: [init] checking the claim
... skipping 28 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:243
STEP: checking the snapshot
STEP: checking the SnapshotContent
STEP: Modifying source data test
STEP: modifying the data in the source PVC
Jun 10 16:21:48.983: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-zf8hc" in namespace "snapshotting-9420" to be "Succeeded or Failed"
Jun 10 16:21:49.096: INFO: Pod "pvc-snapshottable-data-tester-zf8hc": Phase="Pending", Reason="", readiness=false. Elapsed: 112.729197ms
Jun 10 16:21:51.209: INFO: Pod "pvc-snapshottable-data-tester-zf8hc": Phase="Pending", Reason="", readiness=false. Elapsed: 2.226115849s
Jun 10 16:21:53.323: INFO: Pod "pvc-snapshottable-data-tester-zf8hc": Phase="Pending", Reason="", readiness=false. Elapsed: 4.339906694s
Jun 10 16:21:55.437: INFO: Pod "pvc-snapshottable-data-tester-zf8hc": Phase="Pending", Reason="", readiness=false. Elapsed: 6.454202869s
Jun 10 16:21:57.551: INFO: Pod "pvc-snapshottable-data-tester-zf8hc": Phase="Pending", Reason="", readiness=false. Elapsed: 8.567722269s
Jun 10 16:21:59.664: INFO: Pod "pvc-snapshottable-data-tester-zf8hc": Phase="Pending", Reason="", readiness=false. Elapsed: 10.680744251s
Jun 10 16:22:01.777: INFO: Pod "pvc-snapshottable-data-tester-zf8hc": Phase="Pending", Reason="", readiness=false. Elapsed: 12.794239614s
Jun 10 16:22:03.891: INFO: Pod "pvc-snapshottable-data-tester-zf8hc": Phase="Pending", Reason="", readiness=false. Elapsed: 14.908259246s
Jun 10 16:22:06.006: INFO: Pod "pvc-snapshottable-data-tester-zf8hc": Phase="Pending", Reason="", readiness=false. Elapsed: 17.022658446s
Jun 10 16:22:08.119: INFO: Pod "pvc-snapshottable-data-tester-zf8hc": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.136106552s
STEP: Saw pod success
Jun 10 16:22:08.119: INFO: Pod "pvc-snapshottable-data-tester-zf8hc" satisfied condition "Succeeded or Failed"
Jun 10 16:22:08.348: INFO: Pod pvc-snapshottable-data-tester-zf8hc has the following logs: 
Jun 10 16:22:08.348: INFO: Deleting pod "pvc-snapshottable-data-tester-zf8hc" in namespace "snapshotting-9420"
Jun 10 16:22:08.469: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-zf8hc" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 10 16:22:23.042: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-9420 exec restored-pvc-tester-bj5cn --namespace=snapshotting-9420 -- cat /mnt/test/data'
... skipping 322 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 16:23:03.461: 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.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 10 16:23:04.038: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 10 16:23:04.038: INFO: Creating resource for dynamic PV
Jun 10 16:23:04.038: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-68939bsmf
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 10 16:23:10.835: INFO: Deleting pod "pod-2b707040-7e5e-4ba8-8e07-d62b3a81d849" in namespace "volumemode-6893"
Jun 10 16:23:10.950: INFO: Wait up to 5m0s for pod "pod-2b707040-7e5e-4ba8-8e07-d62b3a81d849" to be fully deleted
STEP: Deleting pvc
Jun 10 16:23:17.404: INFO: Deleting PersistentVolumeClaim "awsvtxrs"
Jun 10 16:23:17.519: INFO: Waiting up to 5m0s for PersistentVolume pvc-bc04bcc1-bde0-4039-a36d-dc11dc337177 to get deleted
Jun 10 16:23:17.635: INFO: PersistentVolume pvc-bc04bcc1-bde0-4039-a36d-dc11dc337177 found and phase=Released (115.958639ms)
... skipping 9 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.qtJkPBBMp/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.qtJkPBBMp/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
    /tmp/kops.qtJkPBBMp/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.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 16:22:54.333: 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.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun 10 16:22:54.899: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 10 16:22:54.899: INFO: Creating resource for dynamic PV
Jun 10 16:22:54.899: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9252c5fmc
STEP: creating a claim
Jun 10 16:22:55.014: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-z6pc
STEP: Checking for subpath error in container status
Jun 10 16:23:11.601: INFO: Deleting pod "pod-subpath-test-dynamicpv-z6pc" in namespace "provisioning-9252"
Jun 10 16:23:11.715: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-z6pc" to be fully deleted
STEP: Deleting pod
Jun 10 16:23:21.942: INFO: Deleting pod "pod-subpath-test-dynamicpv-z6pc" in namespace "provisioning-9252"
STEP: Deleting pvc
Jun 10 16:23:22.280: INFO: Deleting PersistentVolumeClaim "aws5kqzf"
... skipping 11 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.qtJkPBBMp/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.qtJkPBBMp/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath file is outside the volume [Slow][LinuxOnly]
      /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 10 16:23:27.964: INFO: Driver supports dynamic provisioning, skipping InlineVolume pattern
[AfterEach] [Testpattern: Inline-volume (default fs)] subPath
... skipping 29 lines ...
Jun 10 16:22:52.200: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-3875gz2zm
STEP: creating a claim
Jun 10 16:22:52.314: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-bnpj
STEP: Creating a pod to test exec-volume-test
Jun 10 16:22:52.660: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-bnpj" in namespace "volume-3875" to be "Succeeded or Failed"
Jun 10 16:22:52.774: INFO: Pod "exec-volume-test-dynamicpv-bnpj": Phase="Pending", Reason="", readiness=false. Elapsed: 113.479012ms
Jun 10 16:22:54.889: INFO: Pod "exec-volume-test-dynamicpv-bnpj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.228496695s
Jun 10 16:22:57.004: INFO: Pod "exec-volume-test-dynamicpv-bnpj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.343763224s
Jun 10 16:22:59.119: INFO: Pod "exec-volume-test-dynamicpv-bnpj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.459015189s
Jun 10 16:23:01.233: INFO: Pod "exec-volume-test-dynamicpv-bnpj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.572960613s
Jun 10 16:23:03.348: INFO: Pod "exec-volume-test-dynamicpv-bnpj": Phase="Pending", Reason="", readiness=false. Elapsed: 10.687891665s
Jun 10 16:23:05.465: INFO: Pod "exec-volume-test-dynamicpv-bnpj": Phase="Pending", Reason="", readiness=false. Elapsed: 12.805017427s
Jun 10 16:23:07.579: INFO: Pod "exec-volume-test-dynamicpv-bnpj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.919008821s
STEP: Saw pod success
Jun 10 16:23:07.579: INFO: Pod "exec-volume-test-dynamicpv-bnpj" satisfied condition "Succeeded or Failed"
Jun 10 16:23:07.694: INFO: Trying to get logs from node ip-172-20-43-141.eu-west-3.compute.internal pod exec-volume-test-dynamicpv-bnpj container exec-container-dynamicpv-bnpj: <nil>
STEP: delete the pod
Jun 10 16:23:07.934: INFO: Waiting for pod exec-volume-test-dynamicpv-bnpj to disappear
Jun 10 16:23:08.047: INFO: Pod exec-volume-test-dynamicpv-bnpj no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-bnpj
Jun 10 16:23:08.047: INFO: Deleting pod "exec-volume-test-dynamicpv-bnpj" in namespace "volume-3875"
... skipping 33 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.qtJkPBBMp/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.qtJkPBBMp/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.qtJkPBBMp/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.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 244 lines ...
Jun 10 16:22:43.244: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6946g4frp
STEP: creating a claim
Jun 10 16:22:43.358: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-4xf5
STEP: Creating a pod to test subpath
Jun 10 16:22:43.716: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-4xf5" in namespace "provisioning-6946" to be "Succeeded or Failed"
Jun 10 16:22:43.830: INFO: Pod "pod-subpath-test-dynamicpv-4xf5": Phase="Pending", Reason="", readiness=false. Elapsed: 113.456614ms
Jun 10 16:22:45.943: INFO: Pod "pod-subpath-test-dynamicpv-4xf5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.227040265s
Jun 10 16:22:48.058: INFO: Pod "pod-subpath-test-dynamicpv-4xf5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.341811138s
Jun 10 16:22:50.176: INFO: Pod "pod-subpath-test-dynamicpv-4xf5": Phase="Pending", Reason="", readiness=false. Elapsed: 6.459553543s
Jun 10 16:22:52.290: INFO: Pod "pod-subpath-test-dynamicpv-4xf5": Phase="Pending", Reason="", readiness=false. Elapsed: 8.574263671s
Jun 10 16:22:54.408: INFO: Pod "pod-subpath-test-dynamicpv-4xf5": Phase="Pending", Reason="", readiness=false. Elapsed: 10.69148486s
... skipping 2 lines ...
Jun 10 16:23:00.752: INFO: Pod "pod-subpath-test-dynamicpv-4xf5": Phase="Pending", Reason="", readiness=false. Elapsed: 17.035987517s
Jun 10 16:23:02.867: INFO: Pod "pod-subpath-test-dynamicpv-4xf5": Phase="Pending", Reason="", readiness=false. Elapsed: 19.150409734s
Jun 10 16:23:04.981: INFO: Pod "pod-subpath-test-dynamicpv-4xf5": Phase="Pending", Reason="", readiness=false. Elapsed: 21.264380865s
Jun 10 16:23:07.095: INFO: Pod "pod-subpath-test-dynamicpv-4xf5": Phase="Pending", Reason="", readiness=false. Elapsed: 23.379228678s
Jun 10 16:23:09.211: INFO: Pod "pod-subpath-test-dynamicpv-4xf5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 25.494331445s
STEP: Saw pod success
Jun 10 16:23:09.211: INFO: Pod "pod-subpath-test-dynamicpv-4xf5" satisfied condition "Succeeded or Failed"
Jun 10 16:23:09.325: INFO: Trying to get logs from node ip-172-20-48-40.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-4xf5 container test-container-subpath-dynamicpv-4xf5: <nil>
STEP: delete the pod
Jun 10 16:23:09.565: INFO: Waiting for pod pod-subpath-test-dynamicpv-4xf5 to disappear
Jun 10 16:23:09.678: INFO: Pod pod-subpath-test-dynamicpv-4xf5 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-4xf5
Jun 10 16:23:09.679: INFO: Deleting pod "pod-subpath-test-dynamicpv-4xf5" in namespace "provisioning-6946"
... skipping 74 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 16:23:07.599: 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.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun 10 16:23:08.169: INFO: Creating resource for dynamic PV
Jun 10 16:23:08.169: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2317-e2e-scgp26g
STEP: creating a claim
Jun 10 16:23:08.283: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-fw7l
STEP: Checking for subpath error in container status
Jun 10 16:23:22.875: INFO: Deleting pod "pod-subpath-test-dynamicpv-fw7l" in namespace "provisioning-2317"
Jun 10 16:23:22.999: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-fw7l" to be fully deleted
STEP: Deleting pod
Jun 10 16:23:29.227: INFO: Deleting pod "pod-subpath-test-dynamicpv-fw7l" in namespace "provisioning-2317"
STEP: Deleting pvc
Jun 10 16:23:29.567: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comsnltf"
... skipping 10 lines ...

• [SLOW TEST:32.767 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath file is outside the volume [Slow][LinuxOnly]
    /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volume-lifecycle-performance
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volume-lifecycle-performance
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumeperf.go:111
... skipping 84 lines ...
Jun 10 16:23:19.405: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6568wjz5
STEP: creating a claim
Jun 10 16:23:19.520: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-nk4z
STEP: Creating a pod to test subpath
Jun 10 16:23:19.866: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-nk4z" in namespace "provisioning-656" to be "Succeeded or Failed"
Jun 10 16:23:19.981: INFO: Pod "pod-subpath-test-dynamicpv-nk4z": Phase="Pending", Reason="", readiness=false. Elapsed: 114.153341ms
Jun 10 16:23:22.095: INFO: Pod "pod-subpath-test-dynamicpv-nk4z": Phase="Pending", Reason="", readiness=false. Elapsed: 2.228763242s
Jun 10 16:23:24.211: INFO: Pod "pod-subpath-test-dynamicpv-nk4z": Phase="Pending", Reason="", readiness=false. Elapsed: 4.344049128s
Jun 10 16:23:26.326: INFO: Pod "pod-subpath-test-dynamicpv-nk4z": Phase="Pending", Reason="", readiness=false. Elapsed: 6.45964773s
Jun 10 16:23:28.444: INFO: Pod "pod-subpath-test-dynamicpv-nk4z": Phase="Pending", Reason="", readiness=false. Elapsed: 8.577148312s
Jun 10 16:23:30.558: INFO: Pod "pod-subpath-test-dynamicpv-nk4z": Phase="Pending", Reason="", readiness=false. Elapsed: 10.691511263s
Jun 10 16:23:32.680: INFO: Pod "pod-subpath-test-dynamicpv-nk4z": Phase="Pending", Reason="", readiness=false. Elapsed: 12.813576s
Jun 10 16:23:34.795: INFO: Pod "pod-subpath-test-dynamicpv-nk4z": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.928621927s
STEP: Saw pod success
Jun 10 16:23:34.795: INFO: Pod "pod-subpath-test-dynamicpv-nk4z" satisfied condition "Succeeded or Failed"
Jun 10 16:23:34.909: INFO: Trying to get logs from node ip-172-20-48-40.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-nk4z container test-container-volume-dynamicpv-nk4z: <nil>
STEP: delete the pod
Jun 10 16:23:35.161: INFO: Waiting for pod pod-subpath-test-dynamicpv-nk4z to disappear
Jun 10 16:23:35.279: INFO: Pod pod-subpath-test-dynamicpv-nk4z no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-nk4z
Jun 10 16:23:35.279: INFO: Deleting pod "pod-subpath-test-dynamicpv-nk4z" in namespace "provisioning-656"
... skipping 839 lines ...
Jun 10 16:23:59.022: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 2 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 16:23:27.966: 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.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun 10 16:23:28.543: INFO: Creating resource for dynamic PV
Jun 10 16:23:28.543: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2995-e2e-scknl2f
STEP: creating a claim
Jun 10 16:23:28.657: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-9lxr
STEP: Checking for subpath error in container status
Jun 10 16:23:43.232: INFO: Deleting pod "pod-subpath-test-dynamicpv-9lxr" in namespace "provisioning-2995"
Jun 10 16:23:43.349: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-9lxr" to be fully deleted
STEP: Deleting pod
Jun 10 16:23:55.576: INFO: Deleting pod "pod-subpath-test-dynamicpv-9lxr" in namespace "provisioning-2995"
STEP: Deleting pvc
Jun 10 16:23:55.914: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com6k2c7"
... skipping 9 lines ...

• [SLOW TEST:33.637 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.qtJkPBBMp/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.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 10 16:24:01.605: INFO: Driver "ebs.csi.aws.com" does not support volume type "CSIInlineVolume" - skipping
[AfterEach] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral
... skipping 44 lines ...

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

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

    /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 55 lines ...
Jun 10 16:23:52.398: INFO: Pod aws-client still exists
Jun 10 16:23:54.285: INFO: Waiting for pod aws-client to disappear
Jun 10 16:23:54.402: INFO: Pod aws-client still exists
Jun 10 16:23:56.286: INFO: Waiting for pod aws-client to disappear
Jun 10 16:23:56.399: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun 10 16:23:56.609: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0dfa0d043dd27db44", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0dfa0d043dd27db44 is currently attached to i-00c993f7b0cfa18a6
	status code: 400, request id: 51bff064-f597-4e73-ab30-56eed1fe7dfd
Jun 10 16:24:02.230: INFO: Successfully deleted PD "aws://eu-west-3a/vol-0dfa0d043dd27db44".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 10 16:24:02.230: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-2770" for this suite.
... skipping 22 lines ...
Jun 10 16:21:19.621: INFO: Creating resource for dynamic PV
Jun 10 16:21:19.621: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-8456-e2e-sckqml4
STEP: creating a claim
Jun 10 16:21:19.735: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 10 16:21:20.076: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-5pvk7" in namespace "snapshotting-8456" to be "Succeeded or Failed"
Jun 10 16:21:20.189: INFO: Pod "pvc-snapshottable-tester-5pvk7": Phase="Pending", Reason="", readiness=false. Elapsed: 113.403573ms
Jun 10 16:21:22.304: INFO: Pod "pvc-snapshottable-tester-5pvk7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.228906902s
Jun 10 16:21:24.418: INFO: Pod "pvc-snapshottable-tester-5pvk7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.342809849s
Jun 10 16:21:26.533: INFO: Pod "pvc-snapshottable-tester-5pvk7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.45725357s
Jun 10 16:21:28.648: INFO: Pod "pvc-snapshottable-tester-5pvk7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.572317411s
Jun 10 16:21:30.761: INFO: Pod "pvc-snapshottable-tester-5pvk7": Phase="Pending", Reason="", readiness=false. Elapsed: 10.68534515s
Jun 10 16:21:32.879: INFO: Pod "pvc-snapshottable-tester-5pvk7": Phase="Pending", Reason="", readiness=false. Elapsed: 12.803647255s
Jun 10 16:21:34.993: INFO: Pod "pvc-snapshottable-tester-5pvk7": Phase="Pending", Reason="", readiness=false. Elapsed: 14.91782765s
Jun 10 16:21:37.107: INFO: Pod "pvc-snapshottable-tester-5pvk7": Phase="Pending", Reason="", readiness=false. Elapsed: 17.031323801s
Jun 10 16:21:39.221: INFO: Pod "pvc-snapshottable-tester-5pvk7": Phase="Pending", Reason="", readiness=false. Elapsed: 19.145130081s
Jun 10 16:21:41.335: INFO: Pod "pvc-snapshottable-tester-5pvk7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.259164534s
STEP: Saw pod success
Jun 10 16:21:41.335: INFO: Pod "pvc-snapshottable-tester-5pvk7" satisfied condition "Succeeded or Failed"
Jun 10 16:21:41.569: INFO: Pod pvc-snapshottable-tester-5pvk7 has the following logs: 
Jun 10 16:21:41.569: INFO: Deleting pod "pvc-snapshottable-tester-5pvk7" in namespace "snapshotting-8456"
Jun 10 16:21:41.689: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-5pvk7" to be fully deleted
Jun 10 16:21:41.802: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.coms4m64] to have phase Bound
Jun 10 16:21:41.915: INFO: PersistentVolumeClaim ebs.csi.aws.coms4m64 found and phase=Bound (112.627319ms)
STEP: [init] checking the claim
... skipping 50 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:243
STEP: checking the snapshot
STEP: checking the SnapshotContent
STEP: Modifying source data test
STEP: modifying the data in the source PVC
Jun 10 16:22:30.836: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-krpgh" in namespace "snapshotting-8456" to be "Succeeded or Failed"
Jun 10 16:22:30.948: INFO: Pod "pvc-snapshottable-data-tester-krpgh": Phase="Pending", Reason="", readiness=false. Elapsed: 112.391868ms
Jun 10 16:22:33.062: INFO: Pod "pvc-snapshottable-data-tester-krpgh": Phase="Pending", Reason="", readiness=false. Elapsed: 2.226596574s
Jun 10 16:22:35.180: INFO: Pod "pvc-snapshottable-data-tester-krpgh": Phase="Pending", Reason="", readiness=false. Elapsed: 4.344594191s
Jun 10 16:22:37.295: INFO: Pod "pvc-snapshottable-data-tester-krpgh": Phase="Pending", Reason="", readiness=false. Elapsed: 6.458776611s
Jun 10 16:22:39.408: INFO: Pod "pvc-snapshottable-data-tester-krpgh": Phase="Pending", Reason="", readiness=false. Elapsed: 8.57257156s
Jun 10 16:22:41.522: INFO: Pod "pvc-snapshottable-data-tester-krpgh": Phase="Pending", Reason="", readiness=false. Elapsed: 10.685737336s
... skipping 6 lines ...
Jun 10 16:22:56.324: INFO: Pod "pvc-snapshottable-data-tester-krpgh": Phase="Pending", Reason="", readiness=false. Elapsed: 25.487928726s
Jun 10 16:22:58.437: INFO: Pod "pvc-snapshottable-data-tester-krpgh": Phase="Pending", Reason="", readiness=false. Elapsed: 27.601695623s
Jun 10 16:23:00.560: INFO: Pod "pvc-snapshottable-data-tester-krpgh": Phase="Pending", Reason="", readiness=false. Elapsed: 29.724269268s
Jun 10 16:23:02.673: INFO: Pod "pvc-snapshottable-data-tester-krpgh": Phase="Pending", Reason="", readiness=false. Elapsed: 31.837468163s
Jun 10 16:23:04.786: INFO: Pod "pvc-snapshottable-data-tester-krpgh": Phase="Succeeded", Reason="", readiness=false. Elapsed: 33.950536468s
STEP: Saw pod success
Jun 10 16:23:04.786: INFO: Pod "pvc-snapshottable-data-tester-krpgh" satisfied condition "Succeeded or Failed"
Jun 10 16:23:05.013: INFO: Pod pvc-snapshottable-data-tester-krpgh has the following logs: 
Jun 10 16:23:05.013: INFO: Deleting pod "pvc-snapshottable-data-tester-krpgh" in namespace "snapshotting-8456"
Jun 10 16:23:05.149: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-krpgh" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 10 16:23:21.735: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-8456 exec restored-pvc-tester-pnfz9 --namespace=snapshotting-8456 -- cat /mnt/test/data'
... skipping 184 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 16:23:52.288: 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.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 10 16:23:52.854: INFO: Creating resource for dynamic PV
Jun 10 16:23:52.854: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-1729-e2e-schzlcj
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 10 16:23:59.650: INFO: Deleting pod "pod-095c80cf-e7d3-4f54-9a52-153c9a549691" in namespace "volumemode-1729"
Jun 10 16:23:59.766: INFO: Wait up to 5m0s for pod "pod-095c80cf-e7d3-4f54-9a52-153c9a549691" to be fully deleted
STEP: Deleting pvc
Jun 10 16:24:08.223: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.compjxxt"
Jun 10 16:24:08.337: INFO: Waiting up to 5m0s for PersistentVolume pvc-b276d19a-e888-4cd4-aafc-6d938b329034 to get deleted
Jun 10 16:24:08.450: INFO: PersistentVolume pvc-b276d19a-e888-4cd4-aafc-6d938b329034 found and phase=Released (112.984614ms)
... skipping 9 lines ...

• [SLOW TEST:31.850 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.qtJkPBBMp/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.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 10 16:24:24.141: INFO: Driver "ebs.csi.aws.com" does not support topology - skipping
[AfterEach] [Testpattern: Dynamic PV (immediate binding)] topology
... skipping 44 lines ...
Jun 10 16:23:47.126: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 10 16:23:47.886: INFO: Successfully created a new PD: "aws://eu-west-3a/vol-08bfa310dd71a28ab".
Jun 10 16:23:47.886: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-f647
STEP: Creating a pod to test exec-volume-test
Jun 10 16:23:48.003: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-f647" in namespace "volume-6634" to be "Succeeded or Failed"
Jun 10 16:23:48.117: INFO: Pod "exec-volume-test-inlinevolume-f647": Phase="Pending", Reason="", readiness=false. Elapsed: 114.355568ms
Jun 10 16:23:50.237: INFO: Pod "exec-volume-test-inlinevolume-f647": Phase="Pending", Reason="", readiness=false. Elapsed: 2.23380391s
Jun 10 16:23:52.360: INFO: Pod "exec-volume-test-inlinevolume-f647": Phase="Pending", Reason="", readiness=false. Elapsed: 4.357340842s
Jun 10 16:23:54.474: INFO: Pod "exec-volume-test-inlinevolume-f647": Phase="Pending", Reason="", readiness=false. Elapsed: 6.471734004s
Jun 10 16:23:56.590: INFO: Pod "exec-volume-test-inlinevolume-f647": Phase="Pending", Reason="", readiness=false. Elapsed: 8.587497657s
Jun 10 16:23:58.705: INFO: Pod "exec-volume-test-inlinevolume-f647": Phase="Pending", Reason="", readiness=false. Elapsed: 10.70195579s
Jun 10 16:24:00.820: INFO: Pod "exec-volume-test-inlinevolume-f647": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.817375713s
STEP: Saw pod success
Jun 10 16:24:00.820: INFO: Pod "exec-volume-test-inlinevolume-f647" satisfied condition "Succeeded or Failed"
Jun 10 16:24:00.934: INFO: Trying to get logs from node ip-172-20-34-48.eu-west-3.compute.internal pod exec-volume-test-inlinevolume-f647 container exec-container-inlinevolume-f647: <nil>
STEP: delete the pod
Jun 10 16:24:01.170: INFO: Waiting for pod exec-volume-test-inlinevolume-f647 to disappear
Jun 10 16:24:01.284: INFO: Pod exec-volume-test-inlinevolume-f647 no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-f647
Jun 10 16:24:01.284: INFO: Deleting pod "exec-volume-test-inlinevolume-f647" in namespace "volume-6634"
Jun 10 16:24:01.650: INFO: Couldn't delete PD "aws://eu-west-3a/vol-08bfa310dd71a28ab", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08bfa310dd71a28ab is currently attached to i-00c993f7b0cfa18a6
	status code: 400, request id: 9991d779-24fa-4443-b4a6-63d9bd259cae
Jun 10 16:24:07.231: INFO: Couldn't delete PD "aws://eu-west-3a/vol-08bfa310dd71a28ab", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08bfa310dd71a28ab is currently attached to i-00c993f7b0cfa18a6
	status code: 400, request id: 0fa15bd8-5677-4ff2-91d3-e4846c0dceca
Jun 10 16:24:12.832: INFO: Couldn't delete PD "aws://eu-west-3a/vol-08bfa310dd71a28ab", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08bfa310dd71a28ab is currently attached to i-00c993f7b0cfa18a6
	status code: 400, request id: f8787286-258e-43a5-bacf-cd94316963a2
Jun 10 16:24:18.416: INFO: Couldn't delete PD "aws://eu-west-3a/vol-08bfa310dd71a28ab", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08bfa310dd71a28ab is currently attached to i-00c993f7b0cfa18a6
	status code: 400, request id: 2e1e3106-8df8-4e2d-bc9a-6792d1817244
Jun 10 16:24:24.045: INFO: Successfully deleted PD "aws://eu-west-3a/vol-08bfa310dd71a28ab".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 10 16:24:24.045: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-6634" for this suite.
... skipping 394 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 16:23:31.878: 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.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun 10 16:23:32.448: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 10 16:23:32.448: INFO: Creating resource for dynamic PV
Jun 10 16:23:32.448: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-33362468s
STEP: creating a claim
Jun 10 16:23:32.562: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-j6fg
STEP: Checking for subpath error in container status
Jun 10 16:23:55.143: INFO: Deleting pod "pod-subpath-test-dynamicpv-j6fg" in namespace "provisioning-3336"
Jun 10 16:23:55.271: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-j6fg" to be fully deleted
STEP: Deleting pod
Jun 10 16:24:05.499: INFO: Deleting pod "pod-subpath-test-dynamicpv-j6fg" in namespace "provisioning-3336"
STEP: Deleting pvc
Jun 10 16:24:05.840: INFO: Deleting PersistentVolumeClaim "awssmdfk"
... skipping 15 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.qtJkPBBMp/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.qtJkPBBMp/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath directory is outside the volume [Slow][LinuxOnly]
      /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 10 16:24:31.989: INFO: Driver supports dynamic provisioning, skipping PreprovisionedPV pattern
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
... skipping 25 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.qtJkPBBMp/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.qtJkPBBMp/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.qtJkPBBMp/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.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Distro debian doesn't support ntfs -- skipping

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 223 lines ...
Jun 10 16:24:14.880: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 10 16:24:15.690: INFO: Successfully created a new PD: "aws://eu-west-3a/vol-0e7e3899d5c617a31".
Jun 10 16:24:15.690: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-sl5w
STEP: Creating a pod to test exec-volume-test
Jun 10 16:24:15.805: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-sl5w" in namespace "volume-3145" to be "Succeeded or Failed"
Jun 10 16:24:15.922: INFO: Pod "exec-volume-test-inlinevolume-sl5w": Phase="Pending", Reason="", readiness=false. Elapsed: 116.377323ms
Jun 10 16:24:18.036: INFO: Pod "exec-volume-test-inlinevolume-sl5w": Phase="Pending", Reason="", readiness=false. Elapsed: 2.230790441s
Jun 10 16:24:20.150: INFO: Pod "exec-volume-test-inlinevolume-sl5w": Phase="Pending", Reason="", readiness=false. Elapsed: 4.344797946s
Jun 10 16:24:22.265: INFO: Pod "exec-volume-test-inlinevolume-sl5w": Phase="Pending", Reason="", readiness=false. Elapsed: 6.459515608s
Jun 10 16:24:24.378: INFO: Pod "exec-volume-test-inlinevolume-sl5w": Phase="Pending", Reason="", readiness=false. Elapsed: 8.572780136s
Jun 10 16:24:26.491: INFO: Pod "exec-volume-test-inlinevolume-sl5w": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.68591403s
STEP: Saw pod success
Jun 10 16:24:26.492: INFO: Pod "exec-volume-test-inlinevolume-sl5w" satisfied condition "Succeeded or Failed"
Jun 10 16:24:26.605: INFO: Trying to get logs from node ip-172-20-43-141.eu-west-3.compute.internal pod exec-volume-test-inlinevolume-sl5w container exec-container-inlinevolume-sl5w: <nil>
STEP: delete the pod
Jun 10 16:24:26.843: INFO: Waiting for pod exec-volume-test-inlinevolume-sl5w to disappear
Jun 10 16:24:26.956: INFO: Pod exec-volume-test-inlinevolume-sl5w no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-sl5w
Jun 10 16:24:26.956: INFO: Deleting pod "exec-volume-test-inlinevolume-sl5w" in namespace "volume-3145"
Jun 10 16:24:27.272: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0e7e3899d5c617a31", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e7e3899d5c617a31 is currently attached to i-07d39bd358d68e328
	status code: 400, request id: 82f0655a-64fd-41a4-853c-995e871a0569
Jun 10 16:24:32.839: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0e7e3899d5c617a31", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e7e3899d5c617a31 is currently attached to i-07d39bd358d68e328
	status code: 400, request id: 2865f4cc-f70f-466b-980e-893169a32ecf
Jun 10 16:24:38.423: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0e7e3899d5c617a31", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e7e3899d5c617a31 is currently attached to i-07d39bd358d68e328
	status code: 400, request id: 8c5d68d1-1503-4f1a-98f6-339c458823b8
Jun 10 16:24:44.047: INFO: Successfully deleted PD "aws://eu-west-3a/vol-0e7e3899d5c617a31".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 10 16:24:44.047: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-3145" for this suite.
... skipping 92 lines ...
Jun 10 16:23:16.051: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4864-e2e-scpbgsx
STEP: creating a claim
Jun 10 16:23:16.165: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-mb9j
STEP: Creating a pod to test subpath
Jun 10 16:23:16.511: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-mb9j" in namespace "provisioning-4864" to be "Succeeded or Failed"
Jun 10 16:23:16.625: INFO: Pod "pod-subpath-test-dynamicpv-mb9j": Phase="Pending", Reason="", readiness=false. Elapsed: 113.976952ms
Jun 10 16:23:18.741: INFO: Pod "pod-subpath-test-dynamicpv-mb9j": Phase="Pending", Reason="", readiness=false. Elapsed: 2.230406716s
Jun 10 16:23:20.856: INFO: Pod "pod-subpath-test-dynamicpv-mb9j": Phase="Pending", Reason="", readiness=false. Elapsed: 4.345169105s
Jun 10 16:23:22.971: INFO: Pod "pod-subpath-test-dynamicpv-mb9j": Phase="Pending", Reason="", readiness=false. Elapsed: 6.460409735s
Jun 10 16:23:25.085: INFO: Pod "pod-subpath-test-dynamicpv-mb9j": Phase="Pending", Reason="", readiness=false. Elapsed: 8.574251029s
Jun 10 16:23:27.199: INFO: Pod "pod-subpath-test-dynamicpv-mb9j": Phase="Pending", Reason="", readiness=false. Elapsed: 10.688305078s
Jun 10 16:23:29.313: INFO: Pod "pod-subpath-test-dynamicpv-mb9j": Phase="Pending", Reason="", readiness=false. Elapsed: 12.802421544s
Jun 10 16:23:31.427: INFO: Pod "pod-subpath-test-dynamicpv-mb9j": Phase="Pending", Reason="", readiness=false. Elapsed: 14.916543167s
Jun 10 16:23:33.543: INFO: Pod "pod-subpath-test-dynamicpv-mb9j": Phase="Pending", Reason="", readiness=false. Elapsed: 17.031834913s
Jun 10 16:23:35.661: INFO: Pod "pod-subpath-test-dynamicpv-mb9j": Phase="Pending", Reason="", readiness=false. Elapsed: 19.150170082s
Jun 10 16:23:37.776: INFO: Pod "pod-subpath-test-dynamicpv-mb9j": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.265257815s
STEP: Saw pod success
Jun 10 16:23:37.776: INFO: Pod "pod-subpath-test-dynamicpv-mb9j" satisfied condition "Succeeded or Failed"
Jun 10 16:23:37.890: INFO: Trying to get logs from node ip-172-20-33-176.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-mb9j container test-container-subpath-dynamicpv-mb9j: <nil>
STEP: delete the pod
Jun 10 16:23:38.127: INFO: Waiting for pod pod-subpath-test-dynamicpv-mb9j to disappear
Jun 10 16:23:38.244: INFO: Pod pod-subpath-test-dynamicpv-mb9j no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-mb9j
Jun 10 16:23:38.244: INFO: Deleting pod "pod-subpath-test-dynamicpv-mb9j" in namespace "provisioning-4864"
... skipping 66 lines ...
Jun 10 16:24:02.184: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9760-e2e-sc59b9f
STEP: creating a claim
Jun 10 16:24:02.297: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-fz5r
STEP: Creating a pod to test subpath
Jun 10 16:24:02.641: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-fz5r" in namespace "provisioning-9760" to be "Succeeded or Failed"
Jun 10 16:24:02.754: INFO: Pod "pod-subpath-test-dynamicpv-fz5r": Phase="Pending", Reason="", readiness=false. Elapsed: 112.927659ms
Jun 10 16:24:04.869: INFO: Pod "pod-subpath-test-dynamicpv-fz5r": Phase="Pending", Reason="", readiness=false. Elapsed: 2.227275733s
Jun 10 16:24:06.983: INFO: Pod "pod-subpath-test-dynamicpv-fz5r": Phase="Pending", Reason="", readiness=false. Elapsed: 4.341672791s
Jun 10 16:24:09.097: INFO: Pod "pod-subpath-test-dynamicpv-fz5r": Phase="Pending", Reason="", readiness=false. Elapsed: 6.45513709s
Jun 10 16:24:11.210: INFO: Pod "pod-subpath-test-dynamicpv-fz5r": Phase="Pending", Reason="", readiness=false. Elapsed: 8.568554789s
Jun 10 16:24:13.324: INFO: Pod "pod-subpath-test-dynamicpv-fz5r": Phase="Pending", Reason="", readiness=false. Elapsed: 10.68198636s
Jun 10 16:24:15.437: INFO: Pod "pod-subpath-test-dynamicpv-fz5r": Phase="Pending", Reason="", readiness=false. Elapsed: 12.795422785s
Jun 10 16:24:17.551: INFO: Pod "pod-subpath-test-dynamicpv-fz5r": Phase="Pending", Reason="", readiness=false. Elapsed: 14.909407313s
Jun 10 16:24:19.666: INFO: Pod "pod-subpath-test-dynamicpv-fz5r": Phase="Pending", Reason="", readiness=false. Elapsed: 17.024142983s
Jun 10 16:24:21.781: INFO: Pod "pod-subpath-test-dynamicpv-fz5r": Phase="Pending", Reason="", readiness=false. Elapsed: 19.138982018s
Jun 10 16:24:23.895: INFO: Pod "pod-subpath-test-dynamicpv-fz5r": Phase="Pending", Reason="", readiness=false. Elapsed: 21.253030941s
Jun 10 16:24:26.009: INFO: Pod "pod-subpath-test-dynamicpv-fz5r": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.367166942s
STEP: Saw pod success
Jun 10 16:24:26.009: INFO: Pod "pod-subpath-test-dynamicpv-fz5r" satisfied condition "Succeeded or Failed"
Jun 10 16:24:26.122: INFO: Trying to get logs from node ip-172-20-48-40.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-fz5r container test-container-volume-dynamicpv-fz5r: <nil>
STEP: delete the pod
Jun 10 16:24:26.359: INFO: Waiting for pod pod-subpath-test-dynamicpv-fz5r to disappear
Jun 10 16:24:26.472: INFO: Pod pod-subpath-test-dynamicpv-fz5r no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-fz5r
Jun 10 16:24:26.472: INFO: Deleting pod "pod-subpath-test-dynamicpv-fz5r" in namespace "provisioning-9760"
... skipping 50 lines ...

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

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

    /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 113 lines ...
Jun 10 16:23:07.936: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-8191-e2e-sc7kzcb      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-8191    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-8191-e2e-sc7kzcb,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-8191    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-8191-e2e-sc7kzcb,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-8191    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-8191-e2e-sc7kzcb,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-8191-e2e-sc7kzcb    4fc36683-de7f-41ce-8a01-8ba0bd467cfc 6374 0 2021-06-10 16:23:08 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-10 16:23:08 +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-q9qzm pvc- provisioning-8191  7b6174ff-4cb1-425e-9ea9-5ab506797a3c 6392 0 2021-06-10 16:23:08 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-10 16:23:08 +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-8191-e2e-sc7kzcb,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-35a04c1e-2347-40fe-810a-77e73a5c7d9d in namespace provisioning-8191
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun 10 16:23:29.247: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-bldt7" in namespace "provisioning-8191" to be "Succeeded or Failed"
Jun 10 16:23:29.360: INFO: Pod "pvc-volume-tester-writer-bldt7": Phase="Pending", Reason="", readiness=false. Elapsed: 112.872569ms
Jun 10 16:23:31.474: INFO: Pod "pvc-volume-tester-writer-bldt7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.227621301s
Jun 10 16:23:33.589: INFO: Pod "pvc-volume-tester-writer-bldt7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.3422534s
Jun 10 16:23:35.708: INFO: Pod "pvc-volume-tester-writer-bldt7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.461009605s
Jun 10 16:23:37.831: INFO: Pod "pvc-volume-tester-writer-bldt7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.584635778s
Jun 10 16:23:39.946: INFO: Pod "pvc-volume-tester-writer-bldt7": Phase="Pending", Reason="", readiness=false. Elapsed: 10.699104067s
... skipping 22 lines ...
Jun 10 16:24:28.578: INFO: Pod "pvc-volume-tester-writer-bldt7": Phase="Pending", Reason="", readiness=false. Elapsed: 59.331657914s
Jun 10 16:24:30.697: INFO: Pod "pvc-volume-tester-writer-bldt7": Phase="Pending", Reason="", readiness=false. Elapsed: 1m1.450376015s
Jun 10 16:24:32.811: INFO: Pod "pvc-volume-tester-writer-bldt7": Phase="Pending", Reason="", readiness=false. Elapsed: 1m3.564082739s
Jun 10 16:24:34.926: INFO: Pod "pvc-volume-tester-writer-bldt7": Phase="Pending", Reason="", readiness=false. Elapsed: 1m5.679615204s
Jun 10 16:24:37.040: INFO: Pod "pvc-volume-tester-writer-bldt7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m7.793292315s
STEP: Saw pod success
Jun 10 16:24:37.040: INFO: Pod "pvc-volume-tester-writer-bldt7" satisfied condition "Succeeded or Failed"
Jun 10 16:24:37.268: INFO: Pod pvc-volume-tester-writer-bldt7 has the following logs: 
Jun 10 16:24:37.268: INFO: Deleting pod "pvc-volume-tester-writer-bldt7" in namespace "provisioning-8191"
Jun 10 16:24:37.387: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-bldt7" 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-33-176.eu-west-3.compute.internal"
Jun 10 16:24:37.845: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-brcnp" in namespace "provisioning-8191" to be "Succeeded or Failed"
Jun 10 16:24:37.978: INFO: Pod "pvc-volume-tester-reader-brcnp": Phase="Pending", Reason="", readiness=false. Elapsed: 132.3169ms
Jun 10 16:24:40.092: INFO: Pod "pvc-volume-tester-reader-brcnp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.246311224s
STEP: Saw pod success
Jun 10 16:24:40.092: INFO: Pod "pvc-volume-tester-reader-brcnp" satisfied condition "Succeeded or Failed"
Jun 10 16:24:40.337: INFO: Pod pvc-volume-tester-reader-brcnp has the following logs: hello world

Jun 10 16:24:40.337: INFO: Deleting pod "pvc-volume-tester-reader-brcnp" in namespace "provisioning-8191"
Jun 10 16:24:40.457: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-brcnp" to be fully deleted
Jun 10 16:24:40.572: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-q9qzm] to have phase Bound
Jun 10 16:24:40.685: INFO: PersistentVolumeClaim pvc-q9qzm found and phase=Bound (113.232924ms)
... skipping 135 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.qtJkPBBMp/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.qtJkPBBMp/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.qtJkPBBMp/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.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 32 lines ...
Jun 10 16:23:58.112: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6150-e2e-sctpqfb
STEP: creating a claim
Jun 10 16:23:58.225: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-65r2
STEP: Creating a pod to test subpath
Jun 10 16:23:58.583: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-65r2" in namespace "provisioning-6150" to be "Succeeded or Failed"
Jun 10 16:23:58.696: INFO: Pod "pod-subpath-test-dynamicpv-65r2": Phase="Pending", Reason="", readiness=false. Elapsed: 112.86631ms
Jun 10 16:24:00.810: INFO: Pod "pod-subpath-test-dynamicpv-65r2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.226903044s
Jun 10 16:24:02.924: INFO: Pod "pod-subpath-test-dynamicpv-65r2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.341218574s
Jun 10 16:24:05.038: INFO: Pod "pod-subpath-test-dynamicpv-65r2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.454547633s
Jun 10 16:24:07.152: INFO: Pod "pod-subpath-test-dynamicpv-65r2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.568971573s
Jun 10 16:24:09.266: INFO: Pod "pod-subpath-test-dynamicpv-65r2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.683117708s
... skipping 9 lines ...
Jun 10 16:24:30.411: INFO: Pod "pod-subpath-test-dynamicpv-65r2": Phase="Pending", Reason="", readiness=false. Elapsed: 31.828190398s
Jun 10 16:24:32.525: INFO: Pod "pod-subpath-test-dynamicpv-65r2": Phase="Pending", Reason="", readiness=false. Elapsed: 33.941322263s
Jun 10 16:24:34.638: INFO: Pod "pod-subpath-test-dynamicpv-65r2": Phase="Pending", Reason="", readiness=false. Elapsed: 36.054795584s
Jun 10 16:24:36.752: INFO: Pod "pod-subpath-test-dynamicpv-65r2": Phase="Pending", Reason="", readiness=false. Elapsed: 38.169003993s
Jun 10 16:24:38.867: INFO: Pod "pod-subpath-test-dynamicpv-65r2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 40.283462619s
STEP: Saw pod success
Jun 10 16:24:38.867: INFO: Pod "pod-subpath-test-dynamicpv-65r2" satisfied condition "Succeeded or Failed"
Jun 10 16:24:38.979: INFO: Trying to get logs from node ip-172-20-48-40.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-65r2 container test-container-volume-dynamicpv-65r2: <nil>
STEP: delete the pod
Jun 10 16:24:39.216: INFO: Waiting for pod pod-subpath-test-dynamicpv-65r2 to disappear
Jun 10 16:24:39.328: INFO: Pod pod-subpath-test-dynamicpv-65r2 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-65r2
Jun 10 16:24:39.328: INFO: Deleting pod "pod-subpath-test-dynamicpv-65r2" in namespace "provisioning-6150"
... skipping 65 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.qtJkPBBMp/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.qtJkPBBMp/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.qtJkPBBMp/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.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Driver supports dynamic provisioning, skipping InlineVolume pattern

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

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.qtJkPBBMp/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.qtJkPBBMp/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.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 300 lines ...
Jun 10 16:24:57.515: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-6060-e2e-scvp482
STEP: creating a claim
Jun 10 16:24:57.632: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-scx6
STEP: Creating a pod to test exec-volume-test
Jun 10 16:24:57.980: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-scx6" in namespace "volume-6060" to be "Succeeded or Failed"
Jun 10 16:24:58.094: INFO: Pod "exec-volume-test-dynamicpv-scx6": Phase="Pending", Reason="", readiness=false. Elapsed: 114.120417ms
Jun 10 16:25:00.209: INFO: Pod "exec-volume-test-dynamicpv-scx6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.228750605s
Jun 10 16:25:02.324: INFO: Pod "exec-volume-test-dynamicpv-scx6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.343695936s
Jun 10 16:25:04.438: INFO: Pod "exec-volume-test-dynamicpv-scx6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.457741329s
Jun 10 16:25:06.553: INFO: Pod "exec-volume-test-dynamicpv-scx6": Phase="Pending", Reason="", readiness=false. Elapsed: 8.57274574s
Jun 10 16:25:08.667: INFO: Pod "exec-volume-test-dynamicpv-scx6": Phase="Pending", Reason="", readiness=false. Elapsed: 10.687411436s
Jun 10 16:25:10.784: INFO: Pod "exec-volume-test-dynamicpv-scx6": Phase="Pending", Reason="", readiness=false. Elapsed: 12.80448399s
Jun 10 16:25:12.899: INFO: Pod "exec-volume-test-dynamicpv-scx6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.918802731s
STEP: Saw pod success
Jun 10 16:25:12.899: INFO: Pod "exec-volume-test-dynamicpv-scx6" satisfied condition "Succeeded or Failed"
Jun 10 16:25:13.012: INFO: Trying to get logs from node ip-172-20-48-40.eu-west-3.compute.internal pod exec-volume-test-dynamicpv-scx6 container exec-container-dynamicpv-scx6: <nil>
STEP: delete the pod
Jun 10 16:25:13.249: INFO: Waiting for pod exec-volume-test-dynamicpv-scx6 to disappear
Jun 10 16:25:13.362: INFO: Pod exec-volume-test-dynamicpv-scx6 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-scx6
Jun 10 16:25:13.362: INFO: Deleting pod "exec-volume-test-dynamicpv-scx6" in namespace "volume-6060"
... skipping 215 lines ...
Jun 10 16:23:59.595: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3994tvjc5
STEP: creating a claim
Jun 10 16:23:59.708: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-tcdv
STEP: Creating a pod to test subpath
Jun 10 16:24:00.063: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-tcdv" in namespace "provisioning-3994" to be "Succeeded or Failed"
Jun 10 16:24:00.176: INFO: Pod "pod-subpath-test-dynamicpv-tcdv": Phase="Pending", Reason="", readiness=false. Elapsed: 112.922665ms
Jun 10 16:24:02.290: INFO: Pod "pod-subpath-test-dynamicpv-tcdv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.226721098s
Jun 10 16:24:04.404: INFO: Pod "pod-subpath-test-dynamicpv-tcdv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.340360134s
Jun 10 16:24:06.517: INFO: Pod "pod-subpath-test-dynamicpv-tcdv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.453732117s
Jun 10 16:24:08.632: INFO: Pod "pod-subpath-test-dynamicpv-tcdv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.569093284s
Jun 10 16:24:10.746: INFO: Pod "pod-subpath-test-dynamicpv-tcdv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.683137899s
... skipping 9 lines ...
Jun 10 16:24:31.888: INFO: Pod "pod-subpath-test-dynamicpv-tcdv": Phase="Pending", Reason="", readiness=false. Elapsed: 31.824654424s
Jun 10 16:24:34.002: INFO: Pod "pod-subpath-test-dynamicpv-tcdv": Phase="Pending", Reason="", readiness=false. Elapsed: 33.938254827s
Jun 10 16:24:36.117: INFO: Pod "pod-subpath-test-dynamicpv-tcdv": Phase="Pending", Reason="", readiness=false. Elapsed: 36.053307272s
Jun 10 16:24:38.231: INFO: Pod "pod-subpath-test-dynamicpv-tcdv": Phase="Pending", Reason="", readiness=false. Elapsed: 38.167988684s
Jun 10 16:24:40.355: INFO: Pod "pod-subpath-test-dynamicpv-tcdv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 40.29135178s
STEP: Saw pod success
Jun 10 16:24:40.355: INFO: Pod "pod-subpath-test-dynamicpv-tcdv" satisfied condition "Succeeded or Failed"
Jun 10 16:24:40.470: INFO: Trying to get logs from node ip-172-20-43-141.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-tcdv container test-container-subpath-dynamicpv-tcdv: <nil>
STEP: delete the pod
Jun 10 16:24:40.709: INFO: Waiting for pod pod-subpath-test-dynamicpv-tcdv to disappear
Jun 10 16:24:40.822: INFO: Pod pod-subpath-test-dynamicpv-tcdv no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-tcdv
Jun 10 16:24:40.822: INFO: Deleting pod "pod-subpath-test-dynamicpv-tcdv" in namespace "provisioning-3994"
STEP: Creating pod pod-subpath-test-dynamicpv-tcdv
STEP: Creating a pod to test subpath
Jun 10 16:24:41.061: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-tcdv" in namespace "provisioning-3994" to be "Succeeded or Failed"
Jun 10 16:24:41.175: INFO: Pod "pod-subpath-test-dynamicpv-tcdv": Phase="Pending", Reason="", readiness=false. Elapsed: 113.291962ms
Jun 10 16:24:43.288: INFO: Pod "pod-subpath-test-dynamicpv-tcdv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.226536359s
Jun 10 16:24:45.402: INFO: Pod "pod-subpath-test-dynamicpv-tcdv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.34005725s
Jun 10 16:24:47.516: INFO: Pod "pod-subpath-test-dynamicpv-tcdv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.454644729s
Jun 10 16:24:49.630: INFO: Pod "pod-subpath-test-dynamicpv-tcdv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.568290729s
Jun 10 16:24:51.751: INFO: Pod "pod-subpath-test-dynamicpv-tcdv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.689279843s
... skipping 6 lines ...
Jun 10 16:25:06.551: INFO: Pod "pod-subpath-test-dynamicpv-tcdv": Phase="Pending", Reason="", readiness=false. Elapsed: 25.489836065s
Jun 10 16:25:08.665: INFO: Pod "pod-subpath-test-dynamicpv-tcdv": Phase="Pending", Reason="", readiness=false. Elapsed: 27.603558925s
Jun 10 16:25:10.784: INFO: Pod "pod-subpath-test-dynamicpv-tcdv": Phase="Pending", Reason="", readiness=false. Elapsed: 29.722336678s
Jun 10 16:25:12.898: INFO: Pod "pod-subpath-test-dynamicpv-tcdv": Phase="Pending", Reason="", readiness=false. Elapsed: 31.836603662s
Jun 10 16:25:15.011: INFO: Pod "pod-subpath-test-dynamicpv-tcdv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 33.949889549s
STEP: Saw pod success
Jun 10 16:25:15.011: INFO: Pod "pod-subpath-test-dynamicpv-tcdv" satisfied condition "Succeeded or Failed"
Jun 10 16:25:15.124: INFO: Trying to get logs from node ip-172-20-33-176.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-tcdv container test-container-subpath-dynamicpv-tcdv: <nil>
STEP: delete the pod
Jun 10 16:25:15.375: INFO: Waiting for pod pod-subpath-test-dynamicpv-tcdv to disappear
Jun 10 16:25:15.488: INFO: Pod pod-subpath-test-dynamicpv-tcdv no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-tcdv
Jun 10 16:25:15.488: INFO: Deleting pod "pod-subpath-test-dynamicpv-tcdv" in namespace "provisioning-3994"
... skipping 78 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.qtJkPBBMp/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.qtJkPBBMp/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.qtJkPBBMp/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.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 31 lines ...
Jun 10 16:24:48.545: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 10 16:24:49.303: INFO: Successfully created a new PD: "aws://eu-west-3a/vol-017ec2c9e61c5d7a5".
Jun 10 16:24:49.304: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-l7mz
STEP: Creating a pod to test exec-volume-test
Jun 10 16:24:49.421: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-l7mz" in namespace "volume-8364" to be "Succeeded or Failed"
Jun 10 16:24:49.534: INFO: Pod "exec-volume-test-inlinevolume-l7mz": Phase="Pending", Reason="", readiness=false. Elapsed: 112.688102ms
Jun 10 16:24:51.647: INFO: Pod "exec-volume-test-inlinevolume-l7mz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.226411332s
Jun 10 16:24:53.761: INFO: Pod "exec-volume-test-inlinevolume-l7mz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.340255033s
Jun 10 16:24:55.875: INFO: Pod "exec-volume-test-inlinevolume-l7mz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.453536479s
Jun 10 16:24:57.992: INFO: Pod "exec-volume-test-inlinevolume-l7mz": Phase="Pending", Reason="", readiness=false. Elapsed: 8.571243759s
Jun 10 16:25:00.106: INFO: Pod "exec-volume-test-inlinevolume-l7mz": Phase="Pending", Reason="", readiness=false. Elapsed: 10.684698455s
... skipping 6 lines ...
Jun 10 16:25:14.905: INFO: Pod "exec-volume-test-inlinevolume-l7mz": Phase="Pending", Reason="", readiness=false. Elapsed: 25.484296572s
Jun 10 16:25:17.020: INFO: Pod "exec-volume-test-inlinevolume-l7mz": Phase="Pending", Reason="", readiness=false. Elapsed: 27.598655325s
Jun 10 16:25:19.134: INFO: Pod "exec-volume-test-inlinevolume-l7mz": Phase="Pending", Reason="", readiness=false. Elapsed: 29.713011552s
Jun 10 16:25:21.248: INFO: Pod "exec-volume-test-inlinevolume-l7mz": Phase="Pending", Reason="", readiness=false. Elapsed: 31.82746509s
Jun 10 16:25:23.363: INFO: Pod "exec-volume-test-inlinevolume-l7mz": Phase="Succeeded", Reason="", readiness=false. Elapsed: 33.941700782s
STEP: Saw pod success
Jun 10 16:25:23.363: INFO: Pod "exec-volume-test-inlinevolume-l7mz" satisfied condition "Succeeded or Failed"
Jun 10 16:25:23.476: INFO: Trying to get logs from node ip-172-20-43-141.eu-west-3.compute.internal pod exec-volume-test-inlinevolume-l7mz container exec-container-inlinevolume-l7mz: <nil>
STEP: delete the pod
Jun 10 16:25:23.710: INFO: Waiting for pod exec-volume-test-inlinevolume-l7mz to disappear
Jun 10 16:25:23.826: INFO: Pod exec-volume-test-inlinevolume-l7mz no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-l7mz
Jun 10 16:25:23.826: INFO: Deleting pod "exec-volume-test-inlinevolume-l7mz" in namespace "volume-8364"
Jun 10 16:25:24.220: INFO: Couldn't delete PD "aws://eu-west-3a/vol-017ec2c9e61c5d7a5", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-017ec2c9e61c5d7a5 is currently attached to i-07d39bd358d68e328
	status code: 400, request id: 69fb6bba-2535-45bc-810c-f71de9ef0931
Jun 10 16:25:29.846: INFO: Couldn't delete PD "aws://eu-west-3a/vol-017ec2c9e61c5d7a5", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-017ec2c9e61c5d7a5 is currently attached to i-07d39bd358d68e328
	status code: 400, request id: 4b3433a0-ca32-4fe6-be65-77ae63ea7ced
Jun 10 16:25:35.460: INFO: Successfully deleted PD "aws://eu-west-3a/vol-017ec2c9e61c5d7a5".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 10 16:25:35.460: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8364" for this suite.
... skipping 310 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.qtJkPBBMp/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.qtJkPBBMp/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.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 149 lines ...
Jun 10 16:25:26.019: INFO: Pod aws-client still exists
Jun 10 16:25:27.905: INFO: Waiting for pod aws-client to disappear
Jun 10 16:25:28.019: INFO: Pod aws-client still exists
Jun 10 16:25:29.904: INFO: Waiting for pod aws-client to disappear
Jun 10 16:25:30.017: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun 10 16:25:30.216: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0a133cec4db987fb1", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a133cec4db987fb1 is currently attached to i-07d39bd358d68e328
	status code: 400, request id: 52906dde-4670-4210-a5c9-026649ee468f
Jun 10 16:25:35.783: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0a133cec4db987fb1", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a133cec4db987fb1 is currently attached to i-07d39bd358d68e328
	status code: 400, request id: ceb2adf9-aef6-44c0-aaf2-228f25dbcd5d
Jun 10 16:25:41.403: INFO: Successfully deleted PD "aws://eu-west-3a/vol-0a133cec4db987fb1".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 10 16:25:41.403: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-1451" for this suite.
... skipping 23 lines ...
Jun 10 16:24:45.259: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1929-e2e-sc8sktp
STEP: creating a claim
Jun 10 16:24:45.375: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-vh4c
STEP: Creating a pod to test subpath
Jun 10 16:24:45.723: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-vh4c" in namespace "provisioning-1929" to be "Succeeded or Failed"
Jun 10 16:24:45.837: INFO: Pod "pod-subpath-test-dynamicpv-vh4c": Phase="Pending", Reason="", readiness=false. Elapsed: 114.064803ms
Jun 10 16:24:47.954: INFO: Pod "pod-subpath-test-dynamicpv-vh4c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.23069953s
Jun 10 16:24:50.069: INFO: Pod "pod-subpath-test-dynamicpv-vh4c": Phase="Pending", Reason="", readiness=false. Elapsed: 4.345944119s
Jun 10 16:24:52.184: INFO: Pod "pod-subpath-test-dynamicpv-vh4c": Phase="Pending", Reason="", readiness=false. Elapsed: 6.460227319s
Jun 10 16:24:54.297: INFO: Pod "pod-subpath-test-dynamicpv-vh4c": Phase="Pending", Reason="", readiness=false. Elapsed: 8.574128457s
Jun 10 16:24:56.412: INFO: Pod "pod-subpath-test-dynamicpv-vh4c": Phase="Pending", Reason="", readiness=false. Elapsed: 10.688999215s
Jun 10 16:24:58.527: INFO: Pod "pod-subpath-test-dynamicpv-vh4c": Phase="Pending", Reason="", readiness=false. Elapsed: 12.803243938s
Jun 10 16:25:00.642: INFO: Pod "pod-subpath-test-dynamicpv-vh4c": Phase="Pending", Reason="", readiness=false. Elapsed: 14.918739732s
Jun 10 16:25:02.757: INFO: Pod "pod-subpath-test-dynamicpv-vh4c": Phase="Pending", Reason="", readiness=false. Elapsed: 17.033906729s
Jun 10 16:25:04.872: INFO: Pod "pod-subpath-test-dynamicpv-vh4c": Phase="Pending", Reason="", readiness=false. Elapsed: 19.148800207s
Jun 10 16:25:06.986: INFO: Pod "pod-subpath-test-dynamicpv-vh4c": Phase="Pending", Reason="", readiness=false. Elapsed: 21.262742101s
Jun 10 16:25:09.101: INFO: Pod "pod-subpath-test-dynamicpv-vh4c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.377643742s
STEP: Saw pod success
Jun 10 16:25:09.101: INFO: Pod "pod-subpath-test-dynamicpv-vh4c" satisfied condition "Succeeded or Failed"
Jun 10 16:25:09.214: INFO: Trying to get logs from node ip-172-20-33-176.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-vh4c container test-container-subpath-dynamicpv-vh4c: <nil>
STEP: delete the pod
Jun 10 16:25:09.450: INFO: Waiting for pod pod-subpath-test-dynamicpv-vh4c to disappear
Jun 10 16:25:09.563: INFO: Pod pod-subpath-test-dynamicpv-vh4c no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-vh4c
Jun 10 16:25:09.563: INFO: Deleting pod "pod-subpath-test-dynamicpv-vh4c" in namespace "provisioning-1929"
... skipping 253 lines ...
Jun 10 16:25:19.256: INFO: Creating resource for dynamic PV
Jun 10 16:25:19.256: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-701spzg8
STEP: creating a claim
STEP: Expanding non-expandable pvc
Jun 10 16:25:19.597: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 10 16:25:19.824: INFO: Error updating pvc awssbfhw: PersistentVolumeClaim "awssbfhw" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-701spzg8",
  	... // 2 identical fields
  }

Jun 10 16:25:22.052: INFO: Error updating pvc awssbfhw: PersistentVolumeClaim "awssbfhw" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-701spzg8",
  	... // 2 identical fields
  }

Jun 10 16:25:24.062: INFO: Error updating pvc awssbfhw: PersistentVolumeClaim "awssbfhw" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-701spzg8",
  	... // 2 identical fields
  }

Jun 10 16:25:26.051: INFO: Error updating pvc awssbfhw: PersistentVolumeClaim "awssbfhw" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-701spzg8",
  	... // 2 identical fields
  }

Jun 10 16:25:28.053: INFO: Error updating pvc awssbfhw: PersistentVolumeClaim "awssbfhw" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-701spzg8",
  	... // 2 identical fields
  }

Jun 10 16:25:30.053: INFO: Error updating pvc awssbfhw: PersistentVolumeClaim "awssbfhw" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-701spzg8",
  	... // 2 identical fields
  }

Jun 10 16:25:32.052: INFO: Error updating pvc awssbfhw: PersistentVolumeClaim "awssbfhw" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-701spzg8",
  	... // 2 identical fields
  }

Jun 10 16:25:34.051: INFO: Error updating pvc awssbfhw: PersistentVolumeClaim "awssbfhw" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-701spzg8",
  	... // 2 identical fields
  }

Jun 10 16:25:36.053: INFO: Error updating pvc awssbfhw: PersistentVolumeClaim "awssbfhw" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-701spzg8",
  	... // 2 identical fields
  }

Jun 10 16:25:38.054: INFO: Error updating pvc awssbfhw: PersistentVolumeClaim "awssbfhw" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-701spzg8",
  	... // 2 identical fields
  }

Jun 10 16:25:40.054: INFO: Error updating pvc awssbfhw: PersistentVolumeClaim "awssbfhw" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-701spzg8",
  	... // 2 identical fields
  }

Jun 10 16:25:42.054: INFO: Error updating pvc awssbfhw: PersistentVolumeClaim "awssbfhw" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-701spzg8",
  	... // 2 identical fields
  }

Jun 10 16:25:44.051: INFO: Error updating pvc awssbfhw: PersistentVolumeClaim "awssbfhw" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-701spzg8",
  	... // 2 identical fields
  }

Jun 10 16:25:46.051: INFO: Error updating pvc awssbfhw: PersistentVolumeClaim "awssbfhw" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-701spzg8",
  	... // 2 identical fields
  }

Jun 10 16:25:48.054: INFO: Error updating pvc awssbfhw: PersistentVolumeClaim "awssbfhw" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-701spzg8",
  	... // 2 identical fields
  }

Jun 10 16:25:50.057: INFO: Error updating pvc awssbfhw: PersistentVolumeClaim "awssbfhw" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-701spzg8",
  	... // 2 identical fields
  }

Jun 10 16:25:50.283: INFO: Error updating pvc awssbfhw: PersistentVolumeClaim "awssbfhw" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 43 lines ...
Jun 10 16:25:02.346: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-3370bjg8t      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-3370    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-3370bjg8t,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-3370    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-3370bjg8t,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-3370    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-3370bjg8t,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-3370bjg8t    8139d068-5b77-4a81-a17e-02b1b31cf939 9491 0 2021-06-10 16:25:02 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-10 16:25:02 +0000 UTC FieldsV1 {"f:mountOptions":{},"f:provisioner":{},"f:reclaimPolicy":{},"f:volumeBindingMode":{}}}]},Provisioner:kubernetes.io/aws-ebs,Parameters:map[string]string{},ReclaimPolicy:*Delete,MountOptions:[debug nouid32],AllowVolumeExpansion:nil,VolumeBindingMode:*WaitForFirstConsumer,AllowedTopologies:[]TopologySelectorTerm{},} claim=&PersistentVolumeClaim{ObjectMeta:{pvc-trbb6 pvc- provisioning-3370  a24c6915-2a48-4657-aa73-80df26785202 9494 0 2021-06-10 16:25:02 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-10 16:25:02 +0000 UTC FieldsV1 {"f:metadata":{"f:generateName":{}},"f:spec":{"f:accessModes":{},"f:resources":{"f:requests":{".":{},"f:storage":{}}},"f:storageClassName":{},"f:volumeMode":{}}}}]},Spec:PersistentVolumeClaimSpec{AccessModes:[ReadWriteOnce],Resources:ResourceRequirements{Limits:ResourceList{},Requests:ResourceList{storage: {{1073741824 0} {<nil>} 1Gi BinarySI},},},VolumeName:,Selector:nil,StorageClassName:*provisioning-3370bjg8t,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-44f65b0e-4c9e-4862-b69c-21f26c8e12b1 in namespace provisioning-3370
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun 10 16:25:25.610: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-s7dfm" in namespace "provisioning-3370" to be "Succeeded or Failed"
Jun 10 16:25:25.723: INFO: Pod "pvc-volume-tester-writer-s7dfm": Phase="Pending", Reason="", readiness=false. Elapsed: 113.351996ms
Jun 10 16:25:27.837: INFO: Pod "pvc-volume-tester-writer-s7dfm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.227247514s
STEP: Saw pod success
Jun 10 16:25:27.837: INFO: Pod "pvc-volume-tester-writer-s7dfm" satisfied condition "Succeeded or Failed"
Jun 10 16:25:28.067: INFO: Pod pvc-volume-tester-writer-s7dfm has the following logs: 
Jun 10 16:25:28.067: INFO: Deleting pod "pvc-volume-tester-writer-s7dfm" in namespace "provisioning-3370"
Jun 10 16:25:28.188: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-s7dfm" 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-34-48.eu-west-3.compute.internal"
Jun 10 16:25:28.643: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-vfmx7" in namespace "provisioning-3370" to be "Succeeded or Failed"
Jun 10 16:25:28.757: INFO: Pod "pvc-volume-tester-reader-vfmx7": Phase="Pending", Reason="", readiness=false. Elapsed: 113.576508ms
Jun 10 16:25:30.872: INFO: Pod "pvc-volume-tester-reader-vfmx7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.228231019s
STEP: Saw pod success
Jun 10 16:25:30.872: INFO: Pod "pvc-volume-tester-reader-vfmx7" satisfied condition "Succeeded or Failed"
Jun 10 16:25:31.110: INFO: Pod pvc-volume-tester-reader-vfmx7 has the following logs: hello world

Jun 10 16:25:31.110: INFO: Deleting pod "pvc-volume-tester-reader-vfmx7" in namespace "provisioning-3370"
Jun 10 16:25:31.238: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-vfmx7" to be fully deleted
Jun 10 16:25:31.355: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-trbb6] to have phase Bound
Jun 10 16:25:31.468: INFO: PersistentVolumeClaim pvc-trbb6 found and phase=Bound (113.508231ms)
... skipping 654 lines ...
Jun 10 16:25:31.812: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6769-e2e-scp6j4x
STEP: creating a claim
Jun 10 16:25:31.926: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-vcdv
STEP: Creating a pod to test subpath
Jun 10 16:25:32.270: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-vcdv" in namespace "provisioning-6769" to be "Succeeded or Failed"
Jun 10 16:25:32.384: INFO: Pod "pod-subpath-test-dynamicpv-vcdv": Phase="Pending", Reason="", readiness=false. Elapsed: 113.550877ms
Jun 10 16:25:34.497: INFO: Pod "pod-subpath-test-dynamicpv-vcdv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.227238669s
Jun 10 16:25:36.611: INFO: Pod "pod-subpath-test-dynamicpv-vcdv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.341274658s
Jun 10 16:25:38.726: INFO: Pod "pod-subpath-test-dynamicpv-vcdv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.45575273s
Jun 10 16:25:40.852: INFO: Pod "pod-subpath-test-dynamicpv-vcdv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.581637991s
Jun 10 16:25:42.970: INFO: Pod "pod-subpath-test-dynamicpv-vcdv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.699548489s
... skipping 2 lines ...
Jun 10 16:25:49.316: INFO: Pod "pod-subpath-test-dynamicpv-vcdv": Phase="Pending", Reason="", readiness=false. Elapsed: 17.046287175s
Jun 10 16:25:51.431: INFO: Pod "pod-subpath-test-dynamicpv-vcdv": Phase="Pending", Reason="", readiness=false. Elapsed: 19.160805829s
Jun 10 16:25:53.545: INFO: Pod "pod-subpath-test-dynamicpv-vcdv": Phase="Pending", Reason="", readiness=false. Elapsed: 21.275171989s
Jun 10 16:25:55.659: INFO: Pod "pod-subpath-test-dynamicpv-vcdv": Phase="Pending", Reason="", readiness=false. Elapsed: 23.38917565s
Jun 10 16:25:57.775: INFO: Pod "pod-subpath-test-dynamicpv-vcdv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 25.504536515s
STEP: Saw pod success
Jun 10 16:25:57.775: INFO: Pod "pod-subpath-test-dynamicpv-vcdv" satisfied condition "Succeeded or Failed"
Jun 10 16:25:57.889: INFO: Trying to get logs from node ip-172-20-43-141.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-vcdv container test-container-subpath-dynamicpv-vcdv: <nil>
STEP: delete the pod
Jun 10 16:25:58.125: INFO: Waiting for pod pod-subpath-test-dynamicpv-vcdv to disappear
Jun 10 16:25:58.238: INFO: Pod pod-subpath-test-dynamicpv-vcdv no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-vcdv
Jun 10 16:25:58.238: INFO: Deleting pod "pod-subpath-test-dynamicpv-vcdv" in namespace "provisioning-6769"
... skipping 55 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.qtJkPBBMp/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.qtJkPBBMp/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.qtJkPBBMp/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.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 102 lines ...
Jun 10 16:25:28.392: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3644vhrcx
STEP: creating a claim
Jun 10 16:25:28.505: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-l6x4
STEP: Creating a pod to test subpath
Jun 10 16:25:28.848: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-l6x4" in namespace "provisioning-3644" to be "Succeeded or Failed"
Jun 10 16:25:28.965: INFO: Pod "pod-subpath-test-dynamicpv-l6x4": Phase="Pending", Reason="", readiness=false. Elapsed: 116.408763ms
Jun 10 16:25:31.083: INFO: Pod "pod-subpath-test-dynamicpv-l6x4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.234079161s
Jun 10 16:25:33.196: INFO: Pod "pod-subpath-test-dynamicpv-l6x4": Phase="Pending", Reason="", readiness=false. Elapsed: 4.34771932s
Jun 10 16:25:35.313: INFO: Pod "pod-subpath-test-dynamicpv-l6x4": Phase="Pending", Reason="", readiness=false. Elapsed: 6.464180932s
Jun 10 16:25:37.426: INFO: Pod "pod-subpath-test-dynamicpv-l6x4": Phase="Pending", Reason="", readiness=false. Elapsed: 8.577768511s
Jun 10 16:25:39.541: INFO: Pod "pod-subpath-test-dynamicpv-l6x4": Phase="Pending", Reason="", readiness=false. Elapsed: 10.692378648s
Jun 10 16:25:41.655: INFO: Pod "pod-subpath-test-dynamicpv-l6x4": Phase="Pending", Reason="", readiness=false. Elapsed: 12.806021912s
Jun 10 16:25:43.770: INFO: Pod "pod-subpath-test-dynamicpv-l6x4": Phase="Pending", Reason="", readiness=false. Elapsed: 14.921065346s
Jun 10 16:25:45.884: INFO: Pod "pod-subpath-test-dynamicpv-l6x4": Phase="Pending", Reason="", readiness=false. Elapsed: 17.035201225s
Jun 10 16:25:47.999: INFO: Pod "pod-subpath-test-dynamicpv-l6x4": Phase="Pending", Reason="", readiness=false. Elapsed: 19.150413707s
Jun 10 16:25:50.113: INFO: Pod "pod-subpath-test-dynamicpv-l6x4": Phase="Pending", Reason="", readiness=false. Elapsed: 21.264711911s
Jun 10 16:25:52.227: INFO: Pod "pod-subpath-test-dynamicpv-l6x4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.37846649s
STEP: Saw pod success
Jun 10 16:25:52.227: INFO: Pod "pod-subpath-test-dynamicpv-l6x4" satisfied condition "Succeeded or Failed"
Jun 10 16:25:52.340: INFO: Trying to get logs from node ip-172-20-43-141.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-l6x4 container test-container-subpath-dynamicpv-l6x4: <nil>
STEP: delete the pod
Jun 10 16:25:52.573: INFO: Waiting for pod pod-subpath-test-dynamicpv-l6x4 to disappear
Jun 10 16:25:52.686: INFO: Pod pod-subpath-test-dynamicpv-l6x4 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-l6x4
Jun 10 16:25:52.686: INFO: Deleting pod "pod-subpath-test-dynamicpv-l6x4" in namespace "provisioning-3644"
... skipping 169 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 16:25:49.500: 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.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun 10 16:25:50.075: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 10 16:25:50.075: INFO: Creating resource for dynamic PV
Jun 10 16:25:50.075: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6444fngjw
STEP: creating a claim
Jun 10 16:25:50.190: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-h78b
STEP: Checking for subpath error in container status
Jun 10 16:26:06.758: INFO: Deleting pod "pod-subpath-test-dynamicpv-h78b" in namespace "provisioning-6444"
Jun 10 16:26:06.872: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-h78b" to be fully deleted
STEP: Deleting pod
Jun 10 16:26:17.100: INFO: Deleting pod "pod-subpath-test-dynamicpv-h78b" in namespace "provisioning-6444"
STEP: Deleting pvc
Jun 10 16:26:17.439: INFO: Deleting PersistentVolumeClaim "aws4rwkw"
... skipping 12 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.qtJkPBBMp/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.qtJkPBBMp/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.qtJkPBBMp/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.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow]
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 10 16:26:28.244: INFO: Driver supports dynamic provisioning, skipping PreprovisionedPV pattern
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow]
... skipping 178 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 16:26:14.625: 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.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 10 16:26:15.195: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 10 16:26:15.969: INFO: Successfully created a new PD: "aws://eu-west-3a/vol-0d06f9a10d9fc8553".
Jun 10 16:26:15.969: INFO: Creating resource for pre-provisioned PV
Jun 10 16:26:15.969: INFO: Creating PVC and PV
... skipping 3 lines ...
Jun 10 16:26:16.383: INFO: PersistentVolumeClaim pvc-mm5xq found but phase is Pending instead of Bound.
Jun 10 16:26:18.497: INFO: PersistentVolumeClaim pvc-mm5xq found but phase is Pending instead of Bound.
Jun 10 16:26:20.610: INFO: PersistentVolumeClaim pvc-mm5xq found and phase=Bound (4.340245917s)
Jun 10 16:26:20.611: INFO: Waiting up to 3m0s for PersistentVolume aws-rmjlr to have phase Bound
Jun 10 16:26:20.724: INFO: PersistentVolume aws-rmjlr found and phase=Bound (113.466474ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 10 16:26:23.408: INFO: Deleting pod "pod-d7193152-27f6-4f2e-93b0-5fc5dd68f101" in namespace "volumemode-7810"
Jun 10 16:26:23.525: INFO: Wait up to 5m0s for pod "pod-d7193152-27f6-4f2e-93b0-5fc5dd68f101" to be fully deleted
STEP: Deleting pv and pvc
Jun 10 16:26:33.753: INFO: Deleting PersistentVolumeClaim "pvc-mm5xq"
Jun 10 16:26:33.868: INFO: Deleting PersistentVolume "aws-rmjlr"
Jun 10 16:26:34.243: INFO: Successfully deleted PD "aws://eu-west-3a/vol-0d06f9a10d9fc8553".
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.qtJkPBBMp/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.qtJkPBBMp/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
    /tmp/kops.qtJkPBBMp/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.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 10 16:26:34.477: INFO: Driver supports dynamic provisioning, skipping PreprovisionedPV pattern
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
... skipping 19 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 16:25:32.418: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename provisioning
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly]
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun 10 16:25:32.983: INFO: Creating resource for dynamic PV
Jun 10 16:25:32.983: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8615-e2e-sc49kdd
STEP: creating a claim
Jun 10 16:25:33.097: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-6rdk
STEP: Checking for subpath error in container status
Jun 10 16:25:47.670: INFO: Deleting pod "pod-subpath-test-dynamicpv-6rdk" in namespace "provisioning-8615"
Jun 10 16:25:47.791: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-6rdk" to be fully deleted
STEP: Deleting pod
Jun 10 16:25:58.017: INFO: Deleting pod "pod-subpath-test-dynamicpv-6rdk" in namespace "provisioning-8615"
STEP: Deleting pvc
Jun 10 16:25:58.355: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comlhj79"
... skipping 15 lines ...

• [SLOW TEST:62.319 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.qtJkPBBMp/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.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 10 16:26:34.739: INFO: Driver supports dynamic provisioning, skipping PreprovisionedPV pattern
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
... skipping 88 lines ...
Jun 10 16:26:10.397: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-6739zxcbt
STEP: creating a claim
Jun 10 16:26:10.512: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-b8pz
STEP: Creating a pod to test exec-volume-test
Jun 10 16:26:10.852: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-b8pz" in namespace "volume-6739" to be "Succeeded or Failed"
Jun 10 16:26:10.965: INFO: Pod "exec-volume-test-dynamicpv-b8pz": Phase="Pending", Reason="", readiness=false. Elapsed: 112.691052ms
Jun 10 16:26:13.078: INFO: Pod "exec-volume-test-dynamicpv-b8pz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.225627669s
Jun 10 16:26:15.191: INFO: Pod "exec-volume-test-dynamicpv-b8pz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.339004816s
Jun 10 16:26:17.306: INFO: Pod "exec-volume-test-dynamicpv-b8pz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.453392262s
Jun 10 16:26:19.420: INFO: Pod "exec-volume-test-dynamicpv-b8pz": Phase="Pending", Reason="", readiness=false. Elapsed: 8.567568543s
Jun 10 16:26:21.534: INFO: Pod "exec-volume-test-dynamicpv-b8pz": Phase="Pending", Reason="", readiness=false. Elapsed: 10.681971536s
Jun 10 16:26:23.648: INFO: Pod "exec-volume-test-dynamicpv-b8pz": Phase="Pending", Reason="", readiness=false. Elapsed: 12.795524044s
Jun 10 16:26:25.763: INFO: Pod "exec-volume-test-dynamicpv-b8pz": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.910805038s
STEP: Saw pod success
Jun 10 16:26:25.763: INFO: Pod "exec-volume-test-dynamicpv-b8pz" satisfied condition "Succeeded or Failed"
Jun 10 16:26:25.879: INFO: Trying to get logs from node ip-172-20-43-141.eu-west-3.compute.internal pod exec-volume-test-dynamicpv-b8pz container exec-container-dynamicpv-b8pz: <nil>
STEP: delete the pod
Jun 10 16:26:26.113: INFO: Waiting for pod exec-volume-test-dynamicpv-b8pz to disappear
Jun 10 16:26:26.225: INFO: Pod exec-volume-test-dynamicpv-b8pz no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-b8pz
Jun 10 16:26:26.226: INFO: Deleting pod "exec-volume-test-dynamicpv-b8pz" in namespace "volume-6739"
... skipping 202 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.qtJkPBBMp/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.qtJkPBBMp/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.qtJkPBBMp/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.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 178 lines ...
Jun 10 16:25:36.288: INFO: Creating resource for dynamic PV
Jun 10 16:25:36.288: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7604mf6n5
STEP: creating a claim
Jun 10 16:25:36.402: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-7604
Jun 10 16:25:36.747: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-7604" in namespace "provisioning-7604" to be "Succeeded or Failed"
Jun 10 16:25:36.860: INFO: Pod "volume-prep-provisioning-7604": Phase="Pending", Reason="", readiness=false. Elapsed: 112.722329ms
Jun 10 16:25:38.974: INFO: Pod "volume-prep-provisioning-7604": Phase="Pending", Reason="", readiness=false. Elapsed: 2.226577688s
Jun 10 16:25:41.087: INFO: Pod "volume-prep-provisioning-7604": Phase="Pending", Reason="", readiness=false. Elapsed: 4.340245183s
Jun 10 16:25:43.202: INFO: Pod "volume-prep-provisioning-7604": Phase="Pending", Reason="", readiness=false. Elapsed: 6.454794788s
Jun 10 16:25:45.319: INFO: Pod "volume-prep-provisioning-7604": Phase="Pending", Reason="", readiness=false. Elapsed: 8.571302114s
Jun 10 16:25:47.434: INFO: Pod "volume-prep-provisioning-7604": Phase="Pending", Reason="", readiness=false. Elapsed: 10.686780779s
Jun 10 16:25:49.548: INFO: Pod "volume-prep-provisioning-7604": Phase="Pending", Reason="", readiness=false. Elapsed: 12.800814752s
Jun 10 16:25:51.662: INFO: Pod "volume-prep-provisioning-7604": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.914804258s
STEP: Saw pod success
Jun 10 16:25:51.662: INFO: Pod "volume-prep-provisioning-7604" satisfied condition "Succeeded or Failed"
Jun 10 16:25:51.662: INFO: Deleting pod "volume-prep-provisioning-7604" in namespace "provisioning-7604"
Jun 10 16:25:51.781: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-7604" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-pvpg
STEP: Checking for subpath error in container status
Jun 10 16:26:26.237: INFO: Deleting pod "pod-subpath-test-dynamicpv-pvpg" in namespace "provisioning-7604"
Jun 10 16:26:26.355: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-pvpg" to be fully deleted
STEP: Deleting pod
Jun 10 16:26:26.467: INFO: Deleting pod "pod-subpath-test-dynamicpv-pvpg" in namespace "provisioning-7604"
STEP: Deleting pvc
Jun 10 16:26:26.806: INFO: Deleting PersistentVolumeClaim "aws5kkpg"
... skipping 105 lines ...
Jun 10 16:25:39.064: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7844vsvfw
STEP: creating a claim
Jun 10 16:25:39.178: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-nv5d
STEP: Creating a pod to test multi_subpath
Jun 10 16:25:39.523: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-nv5d" in namespace "provisioning-7844" to be "Succeeded or Failed"
Jun 10 16:25:39.636: INFO: Pod "pod-subpath-test-dynamicpv-nv5d": Phase="Pending", Reason="", readiness=false. Elapsed: 113.568623ms
Jun 10 16:25:41.751: INFO: Pod "pod-subpath-test-dynamicpv-nv5d": Phase="Pending", Reason="", readiness=false. Elapsed: 2.227979961s
Jun 10 16:25:43.866: INFO: Pod "pod-subpath-test-dynamicpv-nv5d": Phase="Pending", Reason="", readiness=false. Elapsed: 4.342754106s
Jun 10 16:25:45.980: INFO: Pod "pod-subpath-test-dynamicpv-nv5d": Phase="Pending", Reason="", readiness=false. Elapsed: 6.457240856s
Jun 10 16:25:48.096: INFO: Pod "pod-subpath-test-dynamicpv-nv5d": Phase="Pending", Reason="", readiness=false. Elapsed: 8.572922727s
Jun 10 16:25:50.210: INFO: Pod "pod-subpath-test-dynamicpv-nv5d": Phase="Pending", Reason="", readiness=false. Elapsed: 10.687113788s
... skipping 8 lines ...
Jun 10 16:26:09.243: INFO: Pod "pod-subpath-test-dynamicpv-nv5d": Phase="Pending", Reason="", readiness=false. Elapsed: 29.720416611s
Jun 10 16:26:11.358: INFO: Pod "pod-subpath-test-dynamicpv-nv5d": Phase="Pending", Reason="", readiness=false. Elapsed: 31.835342689s
Jun 10 16:26:13.472: INFO: Pod "pod-subpath-test-dynamicpv-nv5d": Phase="Pending", Reason="", readiness=false. Elapsed: 33.94911885s
Jun 10 16:26:15.586: INFO: Pod "pod-subpath-test-dynamicpv-nv5d": Phase="Pending", Reason="", readiness=false. Elapsed: 36.062831423s
Jun 10 16:26:17.703: INFO: Pod "pod-subpath-test-dynamicpv-nv5d": Phase="Succeeded", Reason="", readiness=false. Elapsed: 38.179968527s
STEP: Saw pod success
Jun 10 16:26:17.703: INFO: Pod "pod-subpath-test-dynamicpv-nv5d" satisfied condition "Succeeded or Failed"
Jun 10 16:26:17.816: INFO: Trying to get logs from node ip-172-20-48-40.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-nv5d container test-container-subpath-dynamicpv-nv5d: <nil>
STEP: delete the pod
Jun 10 16:26:18.050: INFO: Waiting for pod pod-subpath-test-dynamicpv-nv5d to disappear
Jun 10 16:26:18.163: INFO: Pod pod-subpath-test-dynamicpv-nv5d no longer exists
STEP: Deleting pod
Jun 10 16:26:18.163: INFO: Deleting pod "pod-subpath-test-dynamicpv-nv5d" in namespace "provisioning-7844"
... skipping 37 lines ...
Jun 10 16:25:27.958: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4157-e2e-sckg62z
STEP: creating a claim
Jun 10 16:25:28.073: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-qmd4
STEP: Creating a pod to test multi_subpath
Jun 10 16:25:28.422: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-qmd4" in namespace "provisioning-4157" to be "Succeeded or Failed"
Jun 10 16:25:28.535: INFO: Pod "pod-subpath-test-dynamicpv-qmd4": Phase="Pending", Reason="", readiness=false. Elapsed: 113.455606ms
Jun 10 16:25:30.651: INFO: Pod "pod-subpath-test-dynamicpv-qmd4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.228881049s
Jun 10 16:25:32.766: INFO: Pod "pod-subpath-test-dynamicpv-qmd4": Phase="Pending", Reason="", readiness=false. Elapsed: 4.343761534s
Jun 10 16:25:34.880: INFO: Pod "pod-subpath-test-dynamicpv-qmd4": Phase="Pending", Reason="", readiness=false. Elapsed: 6.458294477s
Jun 10 16:25:36.997: INFO: Pod "pod-subpath-test-dynamicpv-qmd4": Phase="Pending", Reason="", readiness=false. Elapsed: 8.574924881s
Jun 10 16:25:39.112: INFO: Pod "pod-subpath-test-dynamicpv-qmd4": Phase="Pending", Reason="", readiness=false. Elapsed: 10.690262686s
... skipping 9 lines ...
Jun 10 16:26:00.264: INFO: Pod "pod-subpath-test-dynamicpv-qmd4": Phase="Pending", Reason="", readiness=false. Elapsed: 31.842083052s
Jun 10 16:26:02.378: INFO: Pod "pod-subpath-test-dynamicpv-qmd4": Phase="Pending", Reason="", readiness=false. Elapsed: 33.956427321s
Jun 10 16:26:04.493: INFO: Pod "pod-subpath-test-dynamicpv-qmd4": Phase="Pending", Reason="", readiness=false. Elapsed: 36.07135452s
Jun 10 16:26:06.608: INFO: Pod "pod-subpath-test-dynamicpv-qmd4": Phase="Pending", Reason="", readiness=false. Elapsed: 38.18585122s
Jun 10 16:26:08.723: INFO: Pod "pod-subpath-test-dynamicpv-qmd4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 40.301100954s
STEP: Saw pod success
Jun 10 16:26:08.723: INFO: Pod "pod-subpath-test-dynamicpv-qmd4" satisfied condition "Succeeded or Failed"
Jun 10 16:26:08.837: INFO: Trying to get logs from node ip-172-20-43-141.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-qmd4 container test-container-subpath-dynamicpv-qmd4: <nil>
STEP: delete the pod
Jun 10 16:26:09.076: INFO: Waiting for pod pod-subpath-test-dynamicpv-qmd4 to disappear
Jun 10 16:26:09.189: INFO: Pod pod-subpath-test-dynamicpv-qmd4 no longer exists
STEP: Deleting pod
Jun 10 16:26:09.189: INFO: Deleting pod "pod-subpath-test-dynamicpv-qmd4" in namespace "provisioning-4157"
... skipping 32 lines ...

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

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

    /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:92
------------------------------
... skipping 150 lines ...
Jun 10 16:25:51.434: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2321-e2e-scdd7df
STEP: creating a claim
Jun 10 16:25:51.558: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-kqb2
STEP: Creating a pod to test subpath
Jun 10 16:25:51.905: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-kqb2" in namespace "provisioning-2321" to be "Succeeded or Failed"
Jun 10 16:25:52.021: INFO: Pod "pod-subpath-test-dynamicpv-kqb2": Phase="Pending", Reason="", readiness=false. Elapsed: 115.437643ms
Jun 10 16:25:54.135: INFO: Pod "pod-subpath-test-dynamicpv-kqb2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.229381836s
Jun 10 16:25:56.248: INFO: Pod "pod-subpath-test-dynamicpv-kqb2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.342788901s
Jun 10 16:25:58.362: INFO: Pod "pod-subpath-test-dynamicpv-kqb2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.456412835s
Jun 10 16:26:00.475: INFO: Pod "pod-subpath-test-dynamicpv-kqb2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.569858301s
Jun 10 16:26:02.588: INFO: Pod "pod-subpath-test-dynamicpv-kqb2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.683155774s
Jun 10 16:26:04.702: INFO: Pod "pod-subpath-test-dynamicpv-kqb2": Phase="Pending", Reason="", readiness=false. Elapsed: 12.796689566s
Jun 10 16:26:06.815: INFO: Pod "pod-subpath-test-dynamicpv-kqb2": Phase="Pending", Reason="", readiness=false. Elapsed: 14.910151704s
Jun 10 16:26:08.952: INFO: Pod "pod-subpath-test-dynamicpv-kqb2": Phase="Pending", Reason="", readiness=false. Elapsed: 17.047221797s
Jun 10 16:26:11.067: INFO: Pod "pod-subpath-test-dynamicpv-kqb2": Phase="Pending", Reason="", readiness=false. Elapsed: 19.161661027s
Jun 10 16:26:13.181: INFO: Pod "pod-subpath-test-dynamicpv-kqb2": Phase="Pending", Reason="", readiness=false. Elapsed: 21.27587557s
Jun 10 16:26:15.296: INFO: Pod "pod-subpath-test-dynamicpv-kqb2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.390448678s
STEP: Saw pod success
Jun 10 16:26:15.296: INFO: Pod "pod-subpath-test-dynamicpv-kqb2" satisfied condition "Succeeded or Failed"
Jun 10 16:26:15.409: INFO: Trying to get logs from node ip-172-20-34-48.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-kqb2 container test-container-subpath-dynamicpv-kqb2: <nil>
STEP: delete the pod
Jun 10 16:26:15.642: INFO: Waiting for pod pod-subpath-test-dynamicpv-kqb2 to disappear
Jun 10 16:26:15.757: INFO: Pod pod-subpath-test-dynamicpv-kqb2 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-kqb2
Jun 10 16:26:15.757: INFO: Deleting pod "pod-subpath-test-dynamicpv-kqb2" in namespace "provisioning-2321"
STEP: Creating pod pod-subpath-test-dynamicpv-kqb2
STEP: Creating a pod to test subpath
Jun 10 16:26:15.984: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-kqb2" in namespace "provisioning-2321" to be "Succeeded or Failed"
Jun 10 16:26:16.097: INFO: Pod "pod-subpath-test-dynamicpv-kqb2": Phase="Pending", Reason="", readiness=false. Elapsed: 113.137439ms
Jun 10 16:26:18.210: INFO: Pod "pod-subpath-test-dynamicpv-kqb2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.226535317s
STEP: Saw pod success
Jun 10 16:26:18.210: INFO: Pod "pod-subpath-test-dynamicpv-kqb2" satisfied condition "Succeeded or Failed"
Jun 10 16:26:18.324: INFO: Trying to get logs from node ip-172-20-34-48.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-kqb2 container test-container-subpath-dynamicpv-kqb2: <nil>
STEP: delete the pod
Jun 10 16:26:18.559: INFO: Waiting for pod pod-subpath-test-dynamicpv-kqb2 to disappear
Jun 10 16:26:18.672: INFO: Pod pod-subpath-test-dynamicpv-kqb2 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-kqb2
Jun 10 16:26:18.672: INFO: Deleting pod "pod-subpath-test-dynamicpv-kqb2" in namespace "provisioning-2321"
... skipping 43 lines ...
Jun 10 16:26:56.303: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.qtJkPBBMp/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.qtJkPBBMp/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.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 51 lines ...
Jun 10 16:26:04.534: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-4464-e2e-sc89nv4
STEP: creating a claim
Jun 10 16:26:04.649: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-b2ch
STEP: Creating a pod to test exec-volume-test
Jun 10 16:26:04.993: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-b2ch" in namespace "volume-4464" to be "Succeeded or Failed"
Jun 10 16:26:05.107: INFO: Pod "exec-volume-test-dynamicpv-b2ch": Phase="Pending", Reason="", readiness=false. Elapsed: 113.993011ms
Jun 10 16:26:07.221: INFO: Pod "exec-volume-test-dynamicpv-b2ch": Phase="Pending", Reason="", readiness=false. Elapsed: 2.227668381s
Jun 10 16:26:09.334: INFO: Pod "exec-volume-test-dynamicpv-b2ch": Phase="Pending", Reason="", readiness=false. Elapsed: 4.341078637s
Jun 10 16:26:11.449: INFO: Pod "exec-volume-test-dynamicpv-b2ch": Phase="Pending", Reason="", readiness=false. Elapsed: 6.455519955s
Jun 10 16:26:13.563: INFO: Pod "exec-volume-test-dynamicpv-b2ch": Phase="Pending", Reason="", readiness=false. Elapsed: 8.569551989s
Jun 10 16:26:15.677: INFO: Pod "exec-volume-test-dynamicpv-b2ch": Phase="Pending", Reason="", readiness=false. Elapsed: 10.68403069s
Jun 10 16:26:17.791: INFO: Pod "exec-volume-test-dynamicpv-b2ch": Phase="Pending", Reason="", readiness=false. Elapsed: 12.797807274s
Jun 10 16:26:19.905: INFO: Pod "exec-volume-test-dynamicpv-b2ch": Phase="Pending", Reason="", readiness=false. Elapsed: 14.911759969s
Jun 10 16:26:22.019: INFO: Pod "exec-volume-test-dynamicpv-b2ch": Phase="Pending", Reason="", readiness=false. Elapsed: 17.025577399s
Jun 10 16:26:24.135: INFO: Pod "exec-volume-test-dynamicpv-b2ch": Phase="Pending", Reason="", readiness=false. Elapsed: 19.141882889s
Jun 10 16:26:26.249: INFO: Pod "exec-volume-test-dynamicpv-b2ch": Phase="Pending", Reason="", readiness=false. Elapsed: 21.255990843s
Jun 10 16:26:28.362: INFO: Pod "exec-volume-test-dynamicpv-b2ch": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.369156981s
STEP: Saw pod success
Jun 10 16:26:28.362: INFO: Pod "exec-volume-test-dynamicpv-b2ch" satisfied condition "Succeeded or Failed"
Jun 10 16:26:28.475: INFO: Trying to get logs from node ip-172-20-43-141.eu-west-3.compute.internal pod exec-volume-test-dynamicpv-b2ch container exec-container-dynamicpv-b2ch: <nil>
STEP: delete the pod
Jun 10 16:26:28.712: INFO: Waiting for pod exec-volume-test-dynamicpv-b2ch to disappear
Jun 10 16:26:28.824: INFO: Pod exec-volume-test-dynamicpv-b2ch no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-b2ch
Jun 10 16:26:28.824: INFO: Deleting pod "exec-volume-test-dynamicpv-b2ch" in namespace "volume-4464"
... skipping 303 lines ...

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

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

    /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 88 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 16:26:43.548: 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.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 10 16:26:44.122: INFO: Creating resource for dynamic PV
Jun 10 16:26:44.122: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-8360-e2e-sc2ln92
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 10 16:26:48.920: INFO: Deleting pod "pod-a6c22c2e-755c-423a-a7b6-9209299847c8" in namespace "volumemode-8360"
Jun 10 16:26:49.035: INFO: Wait up to 5m0s for pod "pod-a6c22c2e-755c-423a-a7b6-9209299847c8" to be fully deleted
STEP: Deleting pvc
Jun 10 16:26:57.489: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comm7qk4"
Jun 10 16:26:57.603: INFO: Waiting up to 5m0s for PersistentVolume pvc-197a1e81-b415-4006-aa24-11acf9963be8 to get deleted
Jun 10 16:26:57.715: INFO: PersistentVolume pvc-197a1e81-b415-4006-aa24-11acf9963be8 found and phase=Released (112.648558ms)
... skipping 9 lines ...

• [SLOW TEST:29.934 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.qtJkPBBMp/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.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
S
------------------------------
[BeforeEach] [sig-storage] Zone Support [Feature:vsphere]
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 31 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.qtJkPBBMp/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.qtJkPBBMp/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.qtJkPBBMp/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.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 176 lines ...
Jun 10 16:24:20.978: INFO: Creating resource for dynamic PV
Jun 10 16:24:20.978: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-4967-e2e-sctflvm
STEP: creating a claim
Jun 10 16:24:21.092: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 10 16:24:21.433: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-hg5xj" in namespace "snapshotting-4967" to be "Succeeded or Failed"
Jun 10 16:24:21.546: INFO: Pod "pvc-snapshottable-tester-hg5xj": Phase="Pending", Reason="", readiness=false. Elapsed: 112.625533ms
Jun 10 16:24:23.660: INFO: Pod "pvc-snapshottable-tester-hg5xj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.22618903s
Jun 10 16:24:25.775: INFO: Pod "pvc-snapshottable-tester-hg5xj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.341785368s
Jun 10 16:24:27.888: INFO: Pod "pvc-snapshottable-tester-hg5xj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.45489103s
Jun 10 16:24:30.002: INFO: Pod "pvc-snapshottable-tester-hg5xj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.568514043s
Jun 10 16:24:32.118: INFO: Pod "pvc-snapshottable-tester-hg5xj": Phase="Pending", Reason="", readiness=false. Elapsed: 10.684950046s
Jun 10 16:24:34.232: INFO: Pod "pvc-snapshottable-tester-hg5xj": Phase="Pending", Reason="", readiness=false. Elapsed: 12.798790268s
Jun 10 16:24:36.346: INFO: Pod "pvc-snapshottable-tester-hg5xj": Phase="Pending", Reason="", readiness=false. Elapsed: 14.912708067s
Jun 10 16:24:38.459: INFO: Pod "pvc-snapshottable-tester-hg5xj": Phase="Pending", Reason="", readiness=false. Elapsed: 17.025277884s
Jun 10 16:24:40.572: INFO: Pod "pvc-snapshottable-tester-hg5xj": Phase="Pending", Reason="", readiness=false. Elapsed: 19.138513293s
Jun 10 16:24:42.685: INFO: Pod "pvc-snapshottable-tester-hg5xj": Phase="Pending", Reason="", readiness=false. Elapsed: 21.251648145s
Jun 10 16:24:44.802: INFO: Pod "pvc-snapshottable-tester-hg5xj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.368750534s
STEP: Saw pod success
Jun 10 16:24:44.802: INFO: Pod "pvc-snapshottable-tester-hg5xj" satisfied condition "Succeeded or Failed"
Jun 10 16:24:45.028: INFO: Pod pvc-snapshottable-tester-hg5xj has the following logs: 
Jun 10 16:24:45.028: INFO: Deleting pod "pvc-snapshottable-tester-hg5xj" in namespace "snapshotting-4967"
Jun 10 16:24:45.147: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-hg5xj" to be fully deleted
Jun 10 16:24:45.262: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.commntkj] to have phase Bound
Jun 10 16:24:45.375: INFO: PersistentVolumeClaim ebs.csi.aws.commntkj found and phase=Bound (112.560903ms)
STEP: [init] checking the claim
... skipping 27 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:243
STEP: checking the snapshot
STEP: checking the SnapshotContent
STEP: Modifying source data test
STEP: modifying the data in the source PVC
Jun 10 16:25:22.567: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-f8s24" in namespace "snapshotting-4967" to be "Succeeded or Failed"
Jun 10 16:25:22.679: INFO: Pod "pvc-snapshottable-data-tester-f8s24": Phase="Pending", Reason="", readiness=false. Elapsed: 112.323208ms
Jun 10 16:25:24.793: INFO: Pod "pvc-snapshottable-data-tester-f8s24": Phase="Pending", Reason="", readiness=false. Elapsed: 2.226367628s
Jun 10 16:25:26.906: INFO: Pod "pvc-snapshottable-data-tester-f8s24": Phase="Pending", Reason="", readiness=false. Elapsed: 4.339211358s
Jun 10 16:25:29.020: INFO: Pod "pvc-snapshottable-data-tester-f8s24": Phase="Pending", Reason="", readiness=false. Elapsed: 6.452711416s
Jun 10 16:25:31.134: INFO: Pod "pvc-snapshottable-data-tester-f8s24": Phase="Pending", Reason="", readiness=false. Elapsed: 8.567066981s
Jun 10 16:25:33.247: INFO: Pod "pvc-snapshottable-data-tester-f8s24": Phase="Pending", Reason="", readiness=false. Elapsed: 10.679818383s
... skipping 7 lines ...
Jun 10 16:25:50.157: INFO: Pod "pvc-snapshottable-data-tester-f8s24": Phase="Pending", Reason="", readiness=false. Elapsed: 27.590076915s
Jun 10 16:25:52.270: INFO: Pod "pvc-snapshottable-data-tester-f8s24": Phase="Pending", Reason="", readiness=false. Elapsed: 29.703247727s
Jun 10 16:25:54.384: INFO: Pod "pvc-snapshottable-data-tester-f8s24": Phase="Pending", Reason="", readiness=false. Elapsed: 31.816458734s
Jun 10 16:25:56.498: INFO: Pod "pvc-snapshottable-data-tester-f8s24": Phase="Pending", Reason="", readiness=false. Elapsed: 33.930642s
Jun 10 16:25:58.610: INFO: Pod "pvc-snapshottable-data-tester-f8s24": Phase="Succeeded", Reason="", readiness=false. Elapsed: 36.043314501s
STEP: Saw pod success
Jun 10 16:25:58.610: INFO: Pod "pvc-snapshottable-data-tester-f8s24" satisfied condition "Succeeded or Failed"
Jun 10 16:25:58.843: INFO: Pod pvc-snapshottable-data-tester-f8s24 has the following logs: 
Jun 10 16:25:58.843: INFO: Deleting pod "pvc-snapshottable-data-tester-f8s24" in namespace "snapshotting-4967"
Jun 10 16:25:58.960: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-f8s24" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 10 16:26:09.529: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-4967 exec restored-pvc-tester-b44bp --namespace=snapshotting-4967 -- cat /mnt/test/data'
... skipping 30 lines ...
Jun 10 16:26:34.663: INFO: volumesnapshotcontents snapcontent-32dc67af-8afe-4cff-ac7f-b5f716825fd4 has been found and is not deleted
Jun 10 16:26:35.779: INFO: volumesnapshotcontents snapcontent-32dc67af-8afe-4cff-ac7f-b5f716825fd4 has been found and is not deleted
Jun 10 16:26:36.892: INFO: volumesnapshotcontents snapcontent-32dc67af-8afe-4cff-ac7f-b5f716825fd4 has been found and is not deleted
Jun 10 16:26:38.005: INFO: volumesnapshotcontents snapcontent-32dc67af-8afe-4cff-ac7f-b5f716825fd4 has been found and is not deleted
Jun 10 16:26:39.119: INFO: volumesnapshotcontents snapcontent-32dc67af-8afe-4cff-ac7f-b5f716825fd4 has been found and is not deleted
Jun 10 16:26:40.232: INFO: volumesnapshotcontents snapcontent-32dc67af-8afe-4cff-ac7f-b5f716825fd4 has been found and is not deleted
Jun 10 16:26:41.232: INFO: WaitUntil failed after reaching the timeout 30s
[AfterEach] volume snapshot controller
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:221
Jun 10 16:26:41.346: INFO: Pod restored-pvc-tester-b44bp has the following logs: 
Jun 10 16:26:41.346: INFO: Deleting pod "restored-pvc-tester-b44bp" in namespace "snapshotting-4967"
Jun 10 16:26:41.460: INFO: Wait up to 5m0s for pod "restored-pvc-tester-b44bp" to be fully deleted
Jun 10 16:27:17.686: INFO: deleting claim "snapshotting-4967"/"pvc-6t2k5"
... skipping 117 lines ...
Jun 10 16:26:50.404: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-1684-e2e-schvp56
STEP: creating a claim
Jun 10 16:26:50.528: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-f2h5
STEP: Creating a pod to test exec-volume-test
Jun 10 16:26:50.875: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-f2h5" in namespace "volume-1684" to be "Succeeded or Failed"
Jun 10 16:26:50.994: INFO: Pod "exec-volume-test-dynamicpv-f2h5": Phase="Pending", Reason="", readiness=false. Elapsed: 119.044546ms
Jun 10 16:26:53.110: INFO: Pod "exec-volume-test-dynamicpv-f2h5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.234516035s
Jun 10 16:26:55.231: INFO: Pod "exec-volume-test-dynamicpv-f2h5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.35597509s
Jun 10 16:26:57.347: INFO: Pod "exec-volume-test-dynamicpv-f2h5": Phase="Pending", Reason="", readiness=false. Elapsed: 6.471929994s
Jun 10 16:26:59.462: INFO: Pod "exec-volume-test-dynamicpv-f2h5": Phase="Pending", Reason="", readiness=false. Elapsed: 8.586545326s
Jun 10 16:27:01.578: INFO: Pod "exec-volume-test-dynamicpv-f2h5": Phase="Pending", Reason="", readiness=false. Elapsed: 10.702484056s
Jun 10 16:27:03.693: INFO: Pod "exec-volume-test-dynamicpv-f2h5": Phase="Pending", Reason="", readiness=false. Elapsed: 12.818116364s
Jun 10 16:27:05.809: INFO: Pod "exec-volume-test-dynamicpv-f2h5": Phase="Pending", Reason="", readiness=false. Elapsed: 14.933758414s
Jun 10 16:27:07.924: INFO: Pod "exec-volume-test-dynamicpv-f2h5": Phase="Pending", Reason="", readiness=false. Elapsed: 17.048620799s
Jun 10 16:27:10.038: INFO: Pod "exec-volume-test-dynamicpv-f2h5": Phase="Pending", Reason="", readiness=false. Elapsed: 19.163122152s
Jun 10 16:27:12.155: INFO: Pod "exec-volume-test-dynamicpv-f2h5": Phase="Pending", Reason="", readiness=false. Elapsed: 21.279946574s
Jun 10 16:27:14.270: INFO: Pod "exec-volume-test-dynamicpv-f2h5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.394459973s
STEP: Saw pod success
Jun 10 16:27:14.270: INFO: Pod "exec-volume-test-dynamicpv-f2h5" satisfied condition "Succeeded or Failed"
Jun 10 16:27:14.384: INFO: Trying to get logs from node ip-172-20-48-40.eu-west-3.compute.internal pod exec-volume-test-dynamicpv-f2h5 container exec-container-dynamicpv-f2h5: <nil>
STEP: delete the pod
Jun 10 16:27:14.898: INFO: Waiting for pod exec-volume-test-dynamicpv-f2h5 to disappear
Jun 10 16:27:15.016: INFO: Pod exec-volume-test-dynamicpv-f2h5 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-f2h5
Jun 10 16:27:15.016: INFO: Deleting pod "exec-volume-test-dynamicpv-f2h5" in namespace "volume-1684"
... skipping 114 lines ...

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

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

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.qtJkPBBMp/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.qtJkPBBMp/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.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 438 lines ...
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 16:27:45.239: 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.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Jun 10 16:27:45.923: INFO: found topology map[topology.kubernetes.io/zone:eu-west-3a]
Jun 10 16:27:45.923: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 10 16:27:45.923: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.qtJkPBBMp/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.qtJkPBBMp/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (delayed binding)] topology
    /tmp/kops.qtJkPBBMp/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.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 147 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 16:27:18.666: 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.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun 10 16:27:19.234: INFO: Creating resource for dynamic PV
Jun 10 16:27:19.234: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9907-e2e-scjlcgs
STEP: creating a claim
Jun 10 16:27:19.349: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-tzcf
STEP: Checking for subpath error in container status
Jun 10 16:27:33.926: INFO: Deleting pod "pod-subpath-test-dynamicpv-tzcf" in namespace "provisioning-9907"
Jun 10 16:27:34.047: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-tzcf" to be fully deleted
STEP: Deleting pod
Jun 10 16:27:44.274: INFO: Deleting pod "pod-subpath-test-dynamicpv-tzcf" in namespace "provisioning-9907"
STEP: Deleting pvc
Jun 10 16:27:44.613: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com8tcg5"
... skipping 11 lines ...

• [SLOW TEST:41.859 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath directory is outside the volume [Slow][LinuxOnly]
    /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 50 lines ...
Jun 10 16:25:04.507: INFO: Creating resource for dynamic PV
Jun 10 16:25:04.507: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-7218-e2e-scj65pg
STEP: creating a claim
Jun 10 16:25:04.621: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 10 16:25:04.965: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-nmtbw" in namespace "snapshotting-7218" to be "Succeeded or Failed"
Jun 10 16:25:05.084: INFO: Pod "pvc-snapshottable-tester-nmtbw": Phase="Pending", Reason="", readiness=false. Elapsed: 119.284217ms
Jun 10 16:25:07.199: INFO: Pod "pvc-snapshottable-tester-nmtbw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.233379824s
Jun 10 16:25:09.314: INFO: Pod "pvc-snapshottable-tester-nmtbw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.348705774s
Jun 10 16:25:11.428: INFO: Pod "pvc-snapshottable-tester-nmtbw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.463062839s
Jun 10 16:25:13.543: INFO: Pod "pvc-snapshottable-tester-nmtbw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.578167498s
Jun 10 16:25:15.658: INFO: Pod "pvc-snapshottable-tester-nmtbw": Phase="Pending", Reason="", readiness=false. Elapsed: 10.693027362s
Jun 10 16:25:17.773: INFO: Pod "pvc-snapshottable-tester-nmtbw": Phase="Pending", Reason="", readiness=false. Elapsed: 12.807615854s
Jun 10 16:25:19.886: INFO: Pod "pvc-snapshottable-tester-nmtbw": Phase="Pending", Reason="", readiness=false. Elapsed: 14.921086883s
Jun 10 16:25:22.005: INFO: Pod "pvc-snapshottable-tester-nmtbw": Phase="Pending", Reason="", readiness=false. Elapsed: 17.039584293s
Jun 10 16:25:24.119: INFO: Pod "pvc-snapshottable-tester-nmtbw": Phase="Pending", Reason="", readiness=false. Elapsed: 19.154056401s
Jun 10 16:25:26.234: INFO: Pod "pvc-snapshottable-tester-nmtbw": Phase="Pending", Reason="", readiness=false. Elapsed: 21.268653478s
Jun 10 16:25:28.350: INFO: Pod "pvc-snapshottable-tester-nmtbw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.384585341s
STEP: Saw pod success
Jun 10 16:25:28.350: INFO: Pod "pvc-snapshottable-tester-nmtbw" satisfied condition "Succeeded or Failed"
Jun 10 16:25:28.578: INFO: Pod pvc-snapshottable-tester-nmtbw has the following logs: 
Jun 10 16:25:28.578: INFO: Deleting pod "pvc-snapshottable-tester-nmtbw" in namespace "snapshotting-7218"
Jun 10 16:25:28.698: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-nmtbw" to be fully deleted
Jun 10 16:25:28.820: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comrd5vs] to have phase Bound
Jun 10 16:25:28.938: INFO: PersistentVolumeClaim ebs.csi.aws.comrd5vs found and phase=Bound (117.712691ms)
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.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:243
STEP: checking the snapshot
STEP: checking the SnapshotContent
STEP: Modifying source data test
STEP: modifying the data in the source PVC
Jun 10 16:26:11.540: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-nfxvp" in namespace "snapshotting-7218" to be "Succeeded or Failed"
Jun 10 16:26:11.653: INFO: Pod "pvc-snapshottable-data-tester-nfxvp": Phase="Pending", Reason="", readiness=false. Elapsed: 113.158104ms
Jun 10 16:26:13.767: INFO: Pod "pvc-snapshottable-data-tester-nfxvp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.227469395s
Jun 10 16:26:15.885: INFO: Pod "pvc-snapshottable-data-tester-nfxvp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.344656093s
Jun 10 16:26:17.999: INFO: Pod "pvc-snapshottable-data-tester-nfxvp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.458591956s
Jun 10 16:26:20.113: INFO: Pod "pvc-snapshottable-data-tester-nfxvp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.573097867s
Jun 10 16:26:22.228: INFO: Pod "pvc-snapshottable-data-tester-nfxvp": Phase="Pending", Reason="", readiness=false. Elapsed: 10.687530895s
Jun 10 16:26:24.346: INFO: Pod "pvc-snapshottable-data-tester-nfxvp": Phase="Pending", Reason="", readiness=false. Elapsed: 12.805789286s
Jun 10 16:26:26.460: INFO: Pod "pvc-snapshottable-data-tester-nfxvp": Phase="Pending", Reason="", readiness=false. Elapsed: 14.919825164s
Jun 10 16:26:28.574: INFO: Pod "pvc-snapshottable-data-tester-nfxvp": Phase="Pending", Reason="", readiness=false. Elapsed: 17.034102711s
Jun 10 16:26:30.688: INFO: Pod "pvc-snapshottable-data-tester-nfxvp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.14823929s
STEP: Saw pod success
Jun 10 16:26:30.688: INFO: Pod "pvc-snapshottable-data-tester-nfxvp" satisfied condition "Succeeded or Failed"
Jun 10 16:26:30.918: INFO: Pod pvc-snapshottable-data-tester-nfxvp has the following logs: 
Jun 10 16:26:30.918: INFO: Deleting pod "pvc-snapshottable-data-tester-nfxvp" in namespace "snapshotting-7218"
Jun 10 16:26:31.037: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-nfxvp" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 10 16:27:11.606: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-7218 exec restored-pvc-tester-w2gzc --namespace=snapshotting-7218 -- cat /mnt/test/data'
... skipping 43 lines ...
Jun 10 16:27:58.339: INFO: At 2021-06-10 16:26:28 +0000 UTC - event for pvc-snapshottable-data-tester-nfxvp: {kubelet ip-172-20-33-176.eu-west-3.compute.internal} Started: Started container volume-tester
Jun 10 16:27:58.339: INFO: At 2021-06-10 16:26:31 +0000 UTC - event for pvc-qkcbl: {persistentvolume-controller } WaitForFirstConsumer: waiting for first consumer to be created before binding
Jun 10 16:27:58.339: INFO: At 2021-06-10 16:26:31 +0000 UTC - event for pvc-qkcbl: {ebs.csi.aws.com_ebs-csi-controller-7ffff4ddf5-5fbnx_f06c148b-5567-45c9-9de5-ce177f72d7cf } Provisioning: External provisioner is provisioning volume for claim "snapshotting-7218/pvc-qkcbl"
Jun 10 16:27:58.339: INFO: At 2021-06-10 16:26:31 +0000 UTC - event for pvc-qkcbl: {persistentvolume-controller } ExternalProvisioning: waiting for a volume to be created, either by external provisioner "ebs.csi.aws.com" or manually created by system administrator
Jun 10 16:27:58.339: INFO: At 2021-06-10 16:26:34 +0000 UTC - event for pvc-qkcbl: {ebs.csi.aws.com_ebs-csi-controller-7ffff4ddf5-5fbnx_f06c148b-5567-45c9-9de5-ce177f72d7cf } ProvisioningSucceeded: Successfully provisioned volume pvc-0efd3ff9-e8a8-4bd3-a625-581e15836dee
Jun 10 16:27:58.339: INFO: At 2021-06-10 16:26:35 +0000 UTC - event for restored-pvc-tester-w2gzc: {default-scheduler } Scheduled: Successfully assigned snapshotting-7218/restored-pvc-tester-w2gzc to ip-172-20-43-141.eu-west-3.compute.internal
Jun 10 16:27:58.339: INFO: At 2021-06-10 16:26:50 +0000 UTC - event for restored-pvc-tester-w2gzc: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-0efd3ff9-e8a8-4bd3-a625-581e15836dee" : rpc error: code = DeadlineExceeded desc = context deadline exceeded
Jun 10 16:27:58.339: INFO: At 2021-06-10 16:26:51 +0000 UTC - event for restored-pvc-tester-w2gzc: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-0efd3ff9-e8a8-4bd3-a625-581e15836dee" 
Jun 10 16:27:58.339: INFO: At 2021-06-10 16:27:07 +0000 UTC - event for restored-pvc-tester-w2gzc: {kubelet ip-172-20-43-141.eu-west-3.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" already present on machine
Jun 10 16:27:58.339: INFO: At 2021-06-10 16:27:08 +0000 UTC - event for restored-pvc-tester-w2gzc: {kubelet ip-172-20-43-141.eu-west-3.compute.internal} Created: Created container volume-tester
Jun 10 16:27:58.339: INFO: At 2021-06-10 16:27:08 +0000 UTC - event for restored-pvc-tester-w2gzc: {kubelet ip-172-20-43-141.eu-west-3.compute.internal} Started: Started container volume-tester
Jun 10 16:27:58.339: INFO: At 2021-06-10 16:27:13 +0000 UTC - event for restored-pvc-tester-w2gzc: {kubelet ip-172-20-43-141.eu-west-3.compute.internal} Killing: Stopping container volume-tester
Jun 10 16:27:58.452: INFO: POD  NODE  PHASE  GRACE  CONDITIONS
... skipping 199 lines ...
    /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:108
      
      /tmp/kops.qtJkPBBMp/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.qtJkPBBMp/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-7218 exec restored-pvc-tester-w2gzc --namespace=snapshotting-7218 -- 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-7218 exec restored-pvc-tester-w2gzc --namespace=snapshotting-7218 -- 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.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:602
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
... skipping 11 lines ...
Jun 10 16:27:04.830: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8326xvbnw
STEP: creating a claim
Jun 10 16:27:04.943: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-wq6h
STEP: Creating a pod to test atomic-volume-subpath
Jun 10 16:27:05.291: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-wq6h" in namespace "provisioning-8326" to be "Succeeded or Failed"
Jun 10 16:27:05.404: INFO: Pod "pod-subpath-test-dynamicpv-wq6h": Phase="Pending", Reason="", readiness=false. Elapsed: 113.352941ms
Jun 10 16:27:07.518: INFO: Pod "pod-subpath-test-dynamicpv-wq6h": Phase="Pending", Reason="", readiness=false. Elapsed: 2.227319879s
Jun 10 16:27:09.632: INFO: Pod "pod-subpath-test-dynamicpv-wq6h": Phase="Pending", Reason="", readiness=false. Elapsed: 4.341183254s
Jun 10 16:27:11.746: INFO: Pod "pod-subpath-test-dynamicpv-wq6h": Phase="Pending", Reason="", readiness=false. Elapsed: 6.454716698s
Jun 10 16:27:13.860: INFO: Pod "pod-subpath-test-dynamicpv-wq6h": Phase="Pending", Reason="", readiness=false. Elapsed: 8.568875153s
Jun 10 16:27:15.973: INFO: Pod "pod-subpath-test-dynamicpv-wq6h": Phase="Pending", Reason="", readiness=false. Elapsed: 10.682159759s
... skipping 7 lines ...
Jun 10 16:27:32.891: INFO: Pod "pod-subpath-test-dynamicpv-wq6h": Phase="Running", Reason="", readiness=true. Elapsed: 27.600174918s
Jun 10 16:27:35.006: INFO: Pod "pod-subpath-test-dynamicpv-wq6h": Phase="Running", Reason="", readiness=true. Elapsed: 29.714576544s
Jun 10 16:27:37.120: INFO: Pod "pod-subpath-test-dynamicpv-wq6h": Phase="Running", Reason="", readiness=true. Elapsed: 31.828760071s
Jun 10 16:27:39.263: INFO: Pod "pod-subpath-test-dynamicpv-wq6h": Phase="Running", Reason="", readiness=true. Elapsed: 33.971830275s
Jun 10 16:27:41.377: INFO: Pod "pod-subpath-test-dynamicpv-wq6h": Phase="Succeeded", Reason="", readiness=false. Elapsed: 36.086022574s
STEP: Saw pod success
Jun 10 16:27:41.377: INFO: Pod "pod-subpath-test-dynamicpv-wq6h" satisfied condition "Succeeded or Failed"
Jun 10 16:27:41.490: INFO: Trying to get logs from node ip-172-20-34-48.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-wq6h container test-container-subpath-dynamicpv-wq6h: <nil>
STEP: delete the pod
Jun 10 16:27:41.728: INFO: Waiting for pod pod-subpath-test-dynamicpv-wq6h to disappear
Jun 10 16:27:41.841: INFO: Pod pod-subpath-test-dynamicpv-wq6h no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-wq6h
Jun 10 16:27:41.841: INFO: Deleting pod "pod-subpath-test-dynamicpv-wq6h" in namespace "provisioning-8326"
... skipping 612 lines ...
Jun 10 16:27:48.170: INFO: PersistentVolumeClaim pvc-rmts8 found but phase is Pending instead of Bound.
Jun 10 16:27:50.284: INFO: PersistentVolumeClaim pvc-rmts8 found and phase=Bound (12.797513552s)
Jun 10 16:27:50.284: INFO: Waiting up to 3m0s for PersistentVolume aws-48djt to have phase Bound
Jun 10 16:27:50.397: INFO: PersistentVolume aws-48djt found and phase=Bound (112.924115ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-jh26
STEP: Creating a pod to test exec-volume-test
Jun 10 16:27:50.740: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-jh26" in namespace "volume-8293" to be "Succeeded or Failed"
Jun 10 16:27:50.853: INFO: Pod "exec-volume-test-preprovisionedpv-jh26": Phase="Pending", Reason="", readiness=false. Elapsed: 112.99278ms
Jun 10 16:27:52.968: INFO: Pod "exec-volume-test-preprovisionedpv-jh26": Phase="Pending", Reason="", readiness=false. Elapsed: 2.2279048s
Jun 10 16:27:55.082: INFO: Pod "exec-volume-test-preprovisionedpv-jh26": Phase="Pending", Reason="", readiness=false. Elapsed: 4.341674395s
Jun 10 16:27:57.196: INFO: Pod "exec-volume-test-preprovisionedpv-jh26": Phase="Pending", Reason="", readiness=false. Elapsed: 6.456215029s
Jun 10 16:27:59.339: INFO: Pod "exec-volume-test-preprovisionedpv-jh26": Phase="Pending", Reason="", readiness=false. Elapsed: 8.598545759s
Jun 10 16:28:01.453: INFO: Pod "exec-volume-test-preprovisionedpv-jh26": Phase="Pending", Reason="", readiness=false. Elapsed: 10.712635663s
... skipping 6 lines ...
Jun 10 16:28:16.253: INFO: Pod "exec-volume-test-preprovisionedpv-jh26": Phase="Pending", Reason="", readiness=false. Elapsed: 25.512754507s
Jun 10 16:28:18.367: INFO: Pod "exec-volume-test-preprovisionedpv-jh26": Phase="Pending", Reason="", readiness=false. Elapsed: 27.627131554s
Jun 10 16:28:20.482: INFO: Pod "exec-volume-test-preprovisionedpv-jh26": Phase="Pending", Reason="", readiness=false. Elapsed: 29.741480599s
Jun 10 16:28:22.597: INFO: Pod "exec-volume-test-preprovisionedpv-jh26": Phase="Pending", Reason="", readiness=false. Elapsed: 31.856366472s
Jun 10 16:28:24.711: INFO: Pod "exec-volume-test-preprovisionedpv-jh26": Phase="Succeeded", Reason="", readiness=false. Elapsed: 33.970333155s
STEP: Saw pod success
Jun 10 16:28:24.711: INFO: Pod "exec-volume-test-preprovisionedpv-jh26" satisfied condition "Succeeded or Failed"
Jun 10 16:28:24.824: INFO: Trying to get logs from node ip-172-20-43-141.eu-west-3.compute.internal pod exec-volume-test-preprovisionedpv-jh26 container exec-container-preprovisionedpv-jh26: <nil>
STEP: delete the pod
Jun 10 16:28:25.057: INFO: Waiting for pod exec-volume-test-preprovisionedpv-jh26 to disappear
Jun 10 16:28:25.177: INFO: Pod exec-volume-test-preprovisionedpv-jh26 no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-jh26
Jun 10 16:28:25.177: INFO: Deleting pod "exec-volume-test-preprovisionedpv-jh26" in namespace "volume-8293"
STEP: Deleting pv and pvc
Jun 10 16:28:25.290: INFO: Deleting PersistentVolumeClaim "pvc-rmts8"
Jun 10 16:28:25.405: INFO: Deleting PersistentVolume "aws-48djt"
Jun 10 16:28:25.727: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0224abd4b7d3b7e74", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0224abd4b7d3b7e74 is currently attached to i-07d39bd358d68e328
	status code: 400, request id: df7c7ee0-7e01-4bb0-ada5-c280280e1db9
Jun 10 16:28:31.345: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0224abd4b7d3b7e74", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0224abd4b7d3b7e74 is currently attached to i-07d39bd358d68e328
	status code: 400, request id: 35fee81c-fa1b-40ed-873e-fe28b4dba39c
Jun 10 16:28:36.919: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0224abd4b7d3b7e74", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0224abd4b7d3b7e74 is currently attached to i-07d39bd358d68e328
	status code: 400, request id: 0851b239-f660-4f58-921d-8a68a1bc304f
Jun 10 16:28:42.560: INFO: Successfully deleted PD "aws://eu-west-3a/vol-0224abd4b7d3b7e74".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 10 16:28:42.560: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8293" for this suite.
... skipping 137 lines ...
Jun 10 16:28:38.987: INFO: Waiting for pod aws-client to disappear
Jun 10 16:28:39.100: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 10 16:28:39.100: INFO: Deleting PersistentVolumeClaim "pvc-kxgrp"
Jun 10 16:28:39.213: INFO: Deleting PersistentVolume "aws-kxx9f"
Jun 10 16:28:39.930: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0ddf0ffddd659bdbc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ddf0ffddd659bdbc is currently attached to i-07d39bd358d68e328
	status code: 400, request id: 23780247-ac23-42fc-a8f7-4a3b4ccb8d2d
Jun 10 16:28:45.508: INFO: Successfully deleted PD "aws://eu-west-3a/vol-0ddf0ffddd659bdbc".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumes
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 10 16:28:45.509: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-1787" for this suite.
... skipping 267 lines ...
Jun 10 16:27:48.203: INFO: PersistentVolumeClaim pvc-pvxmm found but phase is Pending instead of Bound.
Jun 10 16:27:50.316: INFO: PersistentVolumeClaim pvc-pvxmm found and phase=Bound (12.798042795s)
Jun 10 16:27:50.316: INFO: Waiting up to 3m0s for PersistentVolume aws-xm9wq to have phase Bound
Jun 10 16:27:50.428: INFO: PersistentVolume aws-xm9wq found and phase=Bound (112.335064ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-4jgx
STEP: Creating a pod to test exec-volume-test
Jun 10 16:27:50.769: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-4jgx" in namespace "volume-2253" to be "Succeeded or Failed"
Jun 10 16:27:50.882: INFO: Pod "exec-volume-test-preprovisionedpv-4jgx": Phase="Pending", Reason="", readiness=false. Elapsed: 112.402216ms
Jun 10 16:27:52.995: INFO: Pod "exec-volume-test-preprovisionedpv-4jgx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.226140408s
Jun 10 16:27:55.109: INFO: Pod "exec-volume-test-preprovisionedpv-4jgx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.340110442s
Jun 10 16:27:57.222: INFO: Pod "exec-volume-test-preprovisionedpv-4jgx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.453170863s
Jun 10 16:27:59.339: INFO: Pod "exec-volume-test-preprovisionedpv-4jgx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.570177491s
Jun 10 16:28:01.452: INFO: Pod "exec-volume-test-preprovisionedpv-4jgx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.682990152s
... skipping 22 lines ...
Jun 10 16:28:50.072: INFO: Pod "exec-volume-test-preprovisionedpv-4jgx": Phase="Pending", Reason="", readiness=false. Elapsed: 59.302900326s
Jun 10 16:28:52.185: INFO: Pod "exec-volume-test-preprovisionedpv-4jgx": Phase="Pending", Reason="", readiness=false. Elapsed: 1m1.416106756s
Jun 10 16:28:54.298: INFO: Pod "exec-volume-test-preprovisionedpv-4jgx": Phase="Pending", Reason="", readiness=false. Elapsed: 1m3.529305592s
Jun 10 16:28:56.411: INFO: Pod "exec-volume-test-preprovisionedpv-4jgx": Phase="Pending", Reason="", readiness=false. Elapsed: 1m5.642180261s
Jun 10 16:28:58.524: INFO: Pod "exec-volume-test-preprovisionedpv-4jgx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m7.754941495s
STEP: Saw pod success
Jun 10 16:28:58.524: INFO: Pod "exec-volume-test-preprovisionedpv-4jgx" satisfied condition "Succeeded or Failed"
Jun 10 16:28:58.637: INFO: Trying to get logs from node ip-172-20-43-141.eu-west-3.compute.internal pod exec-volume-test-preprovisionedpv-4jgx container exec-container-preprovisionedpv-4jgx: <nil>
STEP: delete the pod
Jun 10 16:28:58.869: INFO: Waiting for pod exec-volume-test-preprovisionedpv-4jgx to disappear
Jun 10 16:28:58.982: INFO: Pod exec-volume-test-preprovisionedpv-4jgx no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-4jgx
Jun 10 16:28:58.982: INFO: Deleting pod "exec-volume-test-preprovisionedpv-4jgx" in namespace "volume-2253"
STEP: Deleting pv and pvc
Jun 10 16:28:59.094: INFO: Deleting PersistentVolumeClaim "pvc-pvxmm"
Jun 10 16:28:59.208: INFO: Deleting PersistentVolume "aws-xm9wq"
Jun 10 16:28:59.908: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0a49bb247907821fa", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a49bb247907821fa is currently attached to i-07d39bd358d68e328
	status code: 400, request id: 9b701ee6-0af0-4d6e-b857-437d4190b864
Jun 10 16:29:05.506: INFO: Successfully deleted PD "aws://eu-west-3a/vol-0a49bb247907821fa".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 10 16:29:05.506: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-2253" for this suite.
... skipping 373 lines ...
      /tmp/kops.qtJkPBBMp/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/ephemeral.go:173
------------------------------


Summarizing 1 Failure:

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

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


Ginkgo ran 1 suite in 10m22.398898792s
Test Suite Failed
+ kops-finish
+ kubetest2 kops -v=2 --cloud-provider=aws --cluster-name=e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --admin-access= --kops-binary-path=/home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops --down
I0610 16:29:47.340097   27562 app.go:59] RunDir for this run: "/logs/artifacts/8e4abfb6-ca05-11eb-a09e-ca7f85cb5ec2"
I0610 16:29:47.340326   27562 app.go:90] ID for this run: "8e4abfb6-ca05-11eb-a09e-ca7f85cb5ec2"
I0610 16:29:47.340571   27562 dumplogs.go:38] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops toolbox dump --name e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ubuntu
I0610 16:29:47.368666   27568 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
... skipping 1463 lines ...