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

No Test Failures!


Error lines from build-log.txt

... skipping 489 lines ...
I0604 00:05:31.141436   11679 up.go:43] Cleaning up any leaked resources from previous cluster
I0604 00:05:31.141460   11679 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
I0604 00:05:31.155932   11685 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0604 00:05:31.156035   11685 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io" not found
W0604 00:05:31.705560   11679 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0604 00:05:31.705610   11679 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
I0604 00:05:31.723021   11695 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0604 00:05:31.723154   11695 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

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

I0604 00:06:00.130163   11679 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
I0604 00:06:00.146447   11730 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0604 00:06:00.146743   11730 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io

W0604 00:06:01.391944   11730 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
W0604 00:06:11.427648   11730 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
W0604 00:06:21.458723   11730 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
W0604 00:06:31.520497   11730 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
W0604 00:06:41.561182   11730 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
W0604 00:06:51.591497   11730 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
W0604 00:07:01.629246   11730 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
W0604 00:07:11.664097   11730 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
W0604 00:07:21.692872   11730 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
W0604 00:07:31.726775   11730 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
W0604 00:07:41.759257   11730 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
W0604 00:07:51.790289   11730 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
W0604 00:08:01.825319   11730 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
W0604 00:08:11.853363   11730 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
W0604 00:08:21.909200   11730 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
W0604 00:08:31.949470   11730 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
W0604 00:08:41.981703   11730 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
W0604 00:08:52.013951   11730 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
W0604 00:09:02.049576   11730 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
W0604 00:09:12.083374   11730 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
W0604 00:09:22.121543   11730 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
W0604 00:09:32.157356   11730 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
W0604 00:09:42.203763   11730 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
W0604 00:09:52.234641   11730 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
W0604 00:10:02.267421   11730 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
W0604 00:10:12.303010   11730 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
W0604 00:10:22.339890   11730 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
W0604 00:10:32.377917   11730 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
W0604 00:10:42.471001   11730 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
W0604 00:10:52.500912   11730 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
W0604 00:11:02.623125   11730 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
W0604 00:11:12.660836   11730 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
W0604 00:11:22.696541   11730 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
W0604 00:11:32.730343   11730 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
W0604 00:11:42.781600   11730 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
W0604 00:11:52.817287   11730 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
W0604 00:12:02.898099   11730 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
W0604 00:12:12.936915   11730 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
W0604 00:12:22.972148   11730 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
W0604 00:12:33.014315   11730 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
W0604 00:12:43.052717   11730 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
W0604 00:12:53.086483   11730 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
W0604 00:13:03.120871   11730 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 9 lines ...
Machine	i-0e8a7d1f42b2c7cf0					machine "i-0e8a7d1f42b2c7cf0" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-r2hj4	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-r2hj4" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-qpfmv	system-cluster-critical pod "cert-manager-webhook-7bbf67968-qpfmv" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-sc2ns		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-sc2ns" is pending
Pod	kube-system/coredns-f45c4bf76-rnpt5			system-cluster-critical pod "coredns-f45c4bf76-rnpt5" is pending

Validation Failed
W0604 00:13:15.809209   11730 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 19 lines ...
Pod	kube-system/coredns-f45c4bf76-rnpt5					system-cluster-critical pod "coredns-f45c4bf76-rnpt5" is pending
Pod	kube-system/ebs-csi-node-2pccz						system-node-critical pod "ebs-csi-node-2pccz" is pending
Pod	kube-system/ebs-csi-node-8wlds						system-node-critical pod "ebs-csi-node-8wlds" is pending
Pod	kube-system/ebs-csi-node-txcxz						system-node-critical pod "ebs-csi-node-txcxz" is pending
Pod	kube-system/kube-proxy-ip-172-20-58-183.eu-west-3.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-58-183.eu-west-3.compute.internal" is pending

Validation Failed
W0604 00:13:27.752233   11730 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 20 lines ...
Pod	kube-system/coredns-autoscaler-6f594f4c58-sc2ns		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-sc2ns" is pending
Pod	kube-system/coredns-f45c4bf76-rnpt5			system-cluster-critical pod "coredns-f45c4bf76-rnpt5" is pending
Pod	kube-system/ebs-csi-node-5ksgd				system-node-critical pod "ebs-csi-node-5ksgd" is pending
Pod	kube-system/ebs-csi-node-8wlds				system-node-critical pod "ebs-csi-node-8wlds" is pending
Pod	kube-system/ebs-csi-node-txcxz				system-node-critical pod "ebs-csi-node-txcxz" is pending

Validation Failed
W0604 00:13:39.672961   11730 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 13 lines ...
Pod	kube-system/calico-node-jm2zq				system-node-critical pod "calico-node-jm2zq" is not ready (calico-node)
Pod	kube-system/cert-manager-cainjector-74d69756d5-r2hj4	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-r2hj4" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-qpfmv	system-cluster-critical pod "cert-manager-webhook-7bbf67968-qpfmv" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-sc2ns		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-sc2ns" is pending
Pod	kube-system/coredns-f45c4bf76-rnpt5			system-cluster-critical pod "coredns-f45c4bf76-rnpt5" is pending

Validation Failed
W0604 00:13:51.547187   11730 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-g2mcs				system-node-critical pod "calico-node-g2mcs" is not ready (calico-node)
Pod	kube-system/cert-manager-webhook-7bbf67968-qpfmv	system-cluster-critical pod "cert-manager-webhook-7bbf67968-qpfmv" is not ready (cert-manager)

Validation Failed
W0604 00:14:03.477402   11730 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 294 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.skFUj8hNl/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.skFUj8hNl/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.skFUj8hNl/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.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Distro debian doesn't support ntfs -- skipping

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

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

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

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

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

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

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

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

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

      Distro debian doesn't support ntfs -- skipping

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.skFUj8hNl/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.skFUj8hNl/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.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 254 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  4 00:17:32.330: 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.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  4 00:17:33.514: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  4 00:17:33.514: INFO: Creating resource for dynamic PV
Jun  4 00:17:33.514: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-5503774gd
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  4 00:17:38.251: INFO: Deleting pod "pod-59aec717-e6dd-4a26-a6ce-742f9a42f8e2" in namespace "volumemode-5503"
Jun  4 00:17:38.365: INFO: Wait up to 5m0s for pod "pod-59aec717-e6dd-4a26-a6ce-742f9a42f8e2" to be fully deleted
STEP: Deleting pvc
Jun  4 00:17:48.781: INFO: Deleting PersistentVolumeClaim "awsm4skm"
Jun  4 00:17:48.885: INFO: Waiting up to 5m0s for PersistentVolume pvc-aa824a5c-9d99-4ddc-89fc-996ab840532f to get deleted
Jun  4 00:17:48.988: INFO: PersistentVolume pvc-aa824a5c-9d99-4ddc-89fc-996ab840532f found and phase=Released (103.296977ms)
... skipping 10 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.skFUj8hNl/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.skFUj8hNl/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
    /tmp/kops.skFUj8hNl/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.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] provisioning
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] provisioning
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 37 lines ...
Jun  4 00:17:31.372: INFO: Creating resource for dynamic PV
Jun  4 00:17:31.373: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-2989-e2e-scg44vt
STEP: creating a claim
STEP: Expanding non-expandable pvc
Jun  4 00:17:31.689: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun  4 00:17:31.906: INFO: Error updating pvc ebs.csi.aws.comjkpqp: PersistentVolumeClaim "ebs.csi.aws.comjkpqp" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2989-e2e-scg44vt",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun  4 00:18:02.343: INFO: Error updating pvc ebs.csi.aws.comjkpqp: PersistentVolumeClaim "ebs.csi.aws.comjkpqp" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 53 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  4 00:17:32.977: 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.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  4 00:17:34.162: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  4 00:17:34.162: INFO: Creating resource for dynamic PV
Jun  4 00:17:34.162: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-594179jht
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  4 00:17:42.898: INFO: Deleting pod "pod-e5aacac2-b8df-4ffe-a7e8-58f4df5c95be" in namespace "volumemode-5941"
Jun  4 00:17:43.003: INFO: Wait up to 5m0s for pod "pod-e5aacac2-b8df-4ffe-a7e8-58f4df5c95be" to be fully deleted
STEP: Deleting pvc
Jun  4 00:17:49.440: INFO: Deleting PersistentVolumeClaim "awsl8mcr"
Jun  4 00:17:49.548: INFO: Waiting up to 5m0s for PersistentVolume pvc-754f5d03-a0c8-41e0-9b66-8cebc7aee150 to get deleted
Jun  4 00:17:49.652: INFO: PersistentVolume pvc-754f5d03-a0c8-41e0-9b66-8cebc7aee150 found and phase=Released (103.905516ms)
... skipping 11 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.skFUj8hNl/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.skFUj8hNl/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (block volmode)] volumeMode
    /tmp/kops.skFUj8hNl/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.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] volume-expand
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] volume-expand
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 8 lines ...
Jun  4 00:17:33.957: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-4985pfr8v
STEP: creating a claim
Jun  4 00:17:34.060: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Jun  4 00:17:34.269: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun  4 00:17:34.473: INFO: Error updating pvc aws94d8m: PersistentVolumeClaim "aws94d8m" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4985pfr8v",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun  4 00:18:04.888: INFO: Error updating pvc aws94d8m: PersistentVolumeClaim "aws94d8m" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 135 lines ...
STEP: Deleting pod hostexec-ip-172-20-48-253.eu-west-3.compute.internal-wzmg7 in namespace volumemode-8127
Jun  4 00:17:51.873: INFO: Deleting pod "pod-21ffb936-6f41-401f-803f-1a0b0cdb6861" in namespace "volumemode-8127"
Jun  4 00:17:51.983: INFO: Wait up to 5m0s for pod "pod-21ffb936-6f41-401f-803f-1a0b0cdb6861" to be fully deleted
STEP: Deleting pv and pvc
Jun  4 00:18:00.192: INFO: Deleting PersistentVolumeClaim "pvc-pr79w"
Jun  4 00:18:00.297: INFO: Deleting PersistentVolume "aws-h59wn"
Jun  4 00:18:00.592: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0e83c1f868186481a", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e83c1f868186481a is currently attached to i-016cc349cc178e8d4
	status code: 400, request id: 2ba94b41-5329-4d7d-9750-a3a0d62eebdb
Jun  4 00:18:06.145: INFO: Successfully deleted PD "aws://eu-west-3a/vol-0e83c1f868186481a".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  4 00:18:06.145: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-8127" for this suite.
... skipping 215 lines ...
STEP: Creating a kubernetes client
Jun  4 00:17:29.417: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename provisioning
W0604 00:17:30.160231   25633 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Jun  4 00:17:30.160: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
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.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun  4 00:17:30.369: INFO: Creating resource for dynamic PV
Jun  4 00:17:30.369: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8859-e2e-sc2j2sq
STEP: creating a claim
Jun  4 00:17:30.474: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-48ls
STEP: Checking for subpath error in container status
Jun  4 00:17:49.000: INFO: Deleting pod "pod-subpath-test-dynamicpv-48ls" in namespace "provisioning-8859"
Jun  4 00:17:49.107: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-48ls" to be fully deleted
STEP: Deleting pod
Jun  4 00:17:59.329: INFO: Deleting pod "pod-subpath-test-dynamicpv-48ls" in namespace "provisioning-8859"
STEP: Deleting pvc
Jun  4 00:17:59.639: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com8xwpj"
... skipping 11 lines ...

• [SLOW TEST:46.160 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath file is outside the volume [Slow][LinuxOnly]
    /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 8 lines ...
Jun  4 00:17:34.420: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-738245q6j
STEP: creating a claim
Jun  4 00:17:34.525: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-mv86
STEP: Creating a pod to test subpath
Jun  4 00:17:34.844: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-mv86" in namespace "provisioning-7382" to be "Succeeded or Failed"
Jun  4 00:17:34.948: INFO: Pod "pod-subpath-test-dynamicpv-mv86": Phase="Pending", Reason="", readiness=false. Elapsed: 104.380426ms
Jun  4 00:17:37.053: INFO: Pod "pod-subpath-test-dynamicpv-mv86": Phase="Pending", Reason="", readiness=false. Elapsed: 2.209139659s
Jun  4 00:17:39.159: INFO: Pod "pod-subpath-test-dynamicpv-mv86": Phase="Pending", Reason="", readiness=false. Elapsed: 4.315265661s
Jun  4 00:17:41.268: INFO: Pod "pod-subpath-test-dynamicpv-mv86": Phase="Pending", Reason="", readiness=false. Elapsed: 6.424519376s
Jun  4 00:17:43.375: INFO: Pod "pod-subpath-test-dynamicpv-mv86": Phase="Pending", Reason="", readiness=false. Elapsed: 8.531097574s
Jun  4 00:17:45.480: INFO: Pod "pod-subpath-test-dynamicpv-mv86": Phase="Pending", Reason="", readiness=false. Elapsed: 10.636192958s
Jun  4 00:17:47.585: INFO: Pod "pod-subpath-test-dynamicpv-mv86": Phase="Pending", Reason="", readiness=false. Elapsed: 12.741508311s
Jun  4 00:17:49.692: INFO: Pod "pod-subpath-test-dynamicpv-mv86": Phase="Pending", Reason="", readiness=false. Elapsed: 14.848284922s
Jun  4 00:17:51.798: INFO: Pod "pod-subpath-test-dynamicpv-mv86": Phase="Pending", Reason="", readiness=false. Elapsed: 16.953853141s
Jun  4 00:17:53.904: INFO: Pod "pod-subpath-test-dynamicpv-mv86": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.059981813s
STEP: Saw pod success
Jun  4 00:17:53.904: INFO: Pod "pod-subpath-test-dynamicpv-mv86" satisfied condition "Succeeded or Failed"
Jun  4 00:17:54.011: INFO: Trying to get logs from node ip-172-20-35-212.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-mv86 container test-container-volume-dynamicpv-mv86: <nil>
STEP: delete the pod
Jun  4 00:17:54.252: INFO: Waiting for pod pod-subpath-test-dynamicpv-mv86 to disappear
Jun  4 00:17:54.356: INFO: Pod pod-subpath-test-dynamicpv-mv86 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-mv86
Jun  4 00:17:54.357: INFO: Deleting pod "pod-subpath-test-dynamicpv-mv86" in namespace "provisioning-7382"
... skipping 83 lines ...
STEP: Creating a kubernetes client
Jun  4 00:17:29.929: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename provisioning
W0604 00:17:31.715612   25758 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Jun  4 00:17:31.715: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
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.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun  4 00:17:31.921: INFO: Creating resource for dynamic PV
Jun  4 00:17:31.921: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3942-e2e-sc74tgh
STEP: creating a claim
Jun  4 00:17:32.026: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-bnrh
STEP: Checking for subpath error in container status
Jun  4 00:18:00.552: INFO: Deleting pod "pod-subpath-test-dynamicpv-bnrh" in namespace "provisioning-3942"
Jun  4 00:18:00.657: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-bnrh" to be fully deleted
STEP: Deleting pod
Jun  4 00:18:08.866: INFO: Deleting pod "pod-subpath-test-dynamicpv-bnrh" in namespace "provisioning-3942"
STEP: Deleting pvc
Jun  4 00:18:09.177: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comn52rc"
... skipping 10 lines ...

• [SLOW TEST:50.087 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.skFUj8hNl/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.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] volumes
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] volumes
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 7 lines ...
Jun  4 00:18:03.512: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-6159-e2e-scsb6h4
STEP: creating a claim
Jun  4 00:18:03.618: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-97bt
STEP: Creating a pod to test exec-volume-test
Jun  4 00:18:03.936: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-97bt" in namespace "volume-6159" to be "Succeeded or Failed"
Jun  4 00:18:04.040: INFO: Pod "exec-volume-test-dynamicpv-97bt": Phase="Pending", Reason="", readiness=false. Elapsed: 103.914714ms
Jun  4 00:18:06.145: INFO: Pod "exec-volume-test-dynamicpv-97bt": Phase="Pending", Reason="", readiness=false. Elapsed: 2.209398739s
Jun  4 00:18:08.251: INFO: Pod "exec-volume-test-dynamicpv-97bt": Phase="Pending", Reason="", readiness=false. Elapsed: 4.315538042s
Jun  4 00:18:10.357: INFO: Pod "exec-volume-test-dynamicpv-97bt": Phase="Pending", Reason="", readiness=false. Elapsed: 6.420869596s
Jun  4 00:18:12.461: INFO: Pod "exec-volume-test-dynamicpv-97bt": Phase="Pending", Reason="", readiness=false. Elapsed: 8.525646989s
Jun  4 00:18:14.568: INFO: Pod "exec-volume-test-dynamicpv-97bt": Phase="Pending", Reason="", readiness=false. Elapsed: 10.631906391s
Jun  4 00:18:16.673: INFO: Pod "exec-volume-test-dynamicpv-97bt": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.736993325s
STEP: Saw pod success
Jun  4 00:18:16.673: INFO: Pod "exec-volume-test-dynamicpv-97bt" satisfied condition "Succeeded or Failed"
Jun  4 00:18:16.777: INFO: Trying to get logs from node ip-172-20-41-105.eu-west-3.compute.internal pod exec-volume-test-dynamicpv-97bt container exec-container-dynamicpv-97bt: <nil>
STEP: delete the pod
Jun  4 00:18:16.999: INFO: Waiting for pod exec-volume-test-dynamicpv-97bt to disappear
Jun  4 00:18:17.111: INFO: Pod exec-volume-test-dynamicpv-97bt no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-97bt
Jun  4 00:18:17.111: INFO: Deleting pod "exec-volume-test-dynamicpv-97bt" in namespace "volume-6159"
... skipping 59 lines ...
Jun  4 00:18:08.462: INFO: PersistentVolumeClaim pvc-f6hw2 found but phase is Pending instead of Bound.
Jun  4 00:18:10.571: INFO: PersistentVolumeClaim pvc-f6hw2 found and phase=Bound (2.216420224s)
Jun  4 00:18:10.571: INFO: Waiting up to 3m0s for PersistentVolume aws-8qxzj to have phase Bound
Jun  4 00:18:10.676: INFO: PersistentVolume aws-8qxzj found and phase=Bound (104.577285ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-7lh7
STEP: Creating a pod to test exec-volume-test
Jun  4 00:18:10.990: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-7lh7" in namespace "volume-7539" to be "Succeeded or Failed"
Jun  4 00:18:11.094: INFO: Pod "exec-volume-test-preprovisionedpv-7lh7": Phase="Pending", Reason="", readiness=false. Elapsed: 103.836019ms
Jun  4 00:18:13.200: INFO: Pod "exec-volume-test-preprovisionedpv-7lh7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.209010662s
Jun  4 00:18:15.304: INFO: Pod "exec-volume-test-preprovisionedpv-7lh7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.313927969s
Jun  4 00:18:17.409: INFO: Pod "exec-volume-test-preprovisionedpv-7lh7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.418212814s
Jun  4 00:18:19.515: INFO: Pod "exec-volume-test-preprovisionedpv-7lh7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.524267967s
Jun  4 00:18:21.620: INFO: Pod "exec-volume-test-preprovisionedpv-7lh7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.629200347s
STEP: Saw pod success
Jun  4 00:18:21.620: INFO: Pod "exec-volume-test-preprovisionedpv-7lh7" satisfied condition "Succeeded or Failed"
Jun  4 00:18:21.724: INFO: Trying to get logs from node ip-172-20-41-105.eu-west-3.compute.internal pod exec-volume-test-preprovisionedpv-7lh7 container exec-container-preprovisionedpv-7lh7: <nil>
STEP: delete the pod
Jun  4 00:18:21.939: INFO: Waiting for pod exec-volume-test-preprovisionedpv-7lh7 to disappear
Jun  4 00:18:22.044: INFO: Pod exec-volume-test-preprovisionedpv-7lh7 no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-7lh7
Jun  4 00:18:22.044: INFO: Deleting pod "exec-volume-test-preprovisionedpv-7lh7" in namespace "volume-7539"
STEP: Deleting pv and pvc
Jun  4 00:18:22.147: INFO: Deleting PersistentVolumeClaim "pvc-f6hw2"
Jun  4 00:18:22.252: INFO: Deleting PersistentVolume "aws-8qxzj"
Jun  4 00:18:22.544: INFO: Couldn't delete PD "aws://eu-west-3a/vol-08d1697c28e3da8cc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08d1697c28e3da8cc is currently attached to i-04ffa1804ffe9827d
	status code: 400, request id: d7ea69d6-8d7d-4159-afe3-33610c6189fd
Jun  4 00:18:28.067: INFO: Couldn't delete PD "aws://eu-west-3a/vol-08d1697c28e3da8cc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08d1697c28e3da8cc is currently attached to i-04ffa1804ffe9827d
	status code: 400, request id: ac8bc4eb-d9da-4d31-ab5d-f196e10ed5ac
Jun  4 00:18:33.623: INFO: Successfully deleted PD "aws://eu-west-3a/vol-08d1697c28e3da8cc".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  4 00:18:33.623: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-7539" for this suite.
... skipping 323 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  4 00:18:15.578: 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.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun  4 00:18:16.103: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  4 00:18:16.103: INFO: Creating resource for dynamic PV
Jun  4 00:18:16.103: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7558tn99h
STEP: creating a claim
Jun  4 00:18:16.207: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-85mq
STEP: Checking for subpath error in container status
Jun  4 00:18:36.728: INFO: Deleting pod "pod-subpath-test-dynamicpv-85mq" in namespace "provisioning-7558"
Jun  4 00:18:36.833: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-85mq" to be fully deleted
STEP: Deleting pod
Jun  4 00:18:45.040: INFO: Deleting pod "pod-subpath-test-dynamicpv-85mq" in namespace "provisioning-7558"
STEP: Deleting pvc
Jun  4 00:18:45.353: INFO: Deleting PersistentVolumeClaim "awsgmgrn"
... skipping 13 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.skFUj8hNl/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.skFUj8hNl/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath directory is outside the volume [Slow][LinuxOnly]
      /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 68 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  4 00:18:15.733: 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.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun  4 00:18:16.257: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  4 00:18:16.257: INFO: Creating resource for dynamic PV
Jun  4 00:18:16.257: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2970dljrm
STEP: creating a claim
Jun  4 00:18:16.362: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-ttfr
STEP: Checking for subpath error in container status
Jun  4 00:18:38.890: INFO: Deleting pod "pod-subpath-test-dynamicpv-ttfr" in namespace "provisioning-2970"
Jun  4 00:18:39.005: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-ttfr" to be fully deleted
STEP: Deleting pod
Jun  4 00:18:49.215: INFO: Deleting pod "pod-subpath-test-dynamicpv-ttfr" in namespace "provisioning-2970"
STEP: Deleting pvc
Jun  4 00:18:49.529: INFO: Deleting PersistentVolumeClaim "aws4ngpj"
... skipping 14 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.skFUj8hNl/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.skFUj8hNl/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.skFUj8hNl/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.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volume-stress
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  4 00:19:10.477: INFO: Driver ebs.csi.aws.com doesn't specify stress test options -- skipping
[AfterEach] [Testpattern: Dynamic PV (block volmode)] volume-stress
... skipping 506 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  4 00:18:33.840: 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.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  4 00:18:34.359: INFO: Creating resource for dynamic PV
Jun  4 00:18:34.359: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-5872-e2e-sccjkdz
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  4 00:18:41.108: INFO: Deleting pod "pod-c5780d4c-e9db-4a35-83b3-5731177fa531" in namespace "volumemode-5872"
Jun  4 00:18:41.216: INFO: Wait up to 5m0s for pod "pod-c5780d4c-e9db-4a35-83b3-5731177fa531" to be fully deleted
STEP: Deleting pvc
Jun  4 00:18:49.634: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com8r7hc"
Jun  4 00:18:49.740: INFO: Waiting up to 5m0s for PersistentVolume pvc-b6b2d62b-b32a-4ecd-a53a-3074822981d2 to get deleted
Jun  4 00:18:49.844: INFO: PersistentVolume pvc-b6b2d62b-b32a-4ecd-a53a-3074822981d2 found and phase=Released (104.009045ms)
... skipping 12 lines ...

• [SLOW TEST:46.948 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.skFUj8hNl/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.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic Snapshot (retain policy)] snapshottable-stress[Feature:VolumeSnapshotDataSource]
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  4 00:19:20.790: INFO: Driver aws doesn't specify snapshot stress test options -- skipping
[AfterEach] [Testpattern: Dynamic Snapshot (retain policy)] snapshottable-stress[Feature:VolumeSnapshotDataSource]
... skipping 280 lines ...

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

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

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

    /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:92
------------------------------
... skipping 206 lines ...
Jun  4 00:19:32.053: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 121 lines ...
Jun  4 00:18:05.939: INFO: Creating resource for dynamic PV
Jun  4 00:18:05.939: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8698zwk4v
STEP: creating a claim
Jun  4 00:18:06.042: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-8698
Jun  4 00:18:06.352: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-8698" in namespace "provisioning-8698" to be "Succeeded or Failed"
Jun  4 00:18:06.455: INFO: Pod "volume-prep-provisioning-8698": Phase="Pending", Reason="", readiness=false. Elapsed: 103.118194ms
Jun  4 00:18:08.559: INFO: Pod "volume-prep-provisioning-8698": Phase="Pending", Reason="", readiness=false. Elapsed: 2.206849044s
Jun  4 00:18:10.666: INFO: Pod "volume-prep-provisioning-8698": Phase="Pending", Reason="", readiness=false. Elapsed: 4.313696595s
Jun  4 00:18:12.770: INFO: Pod "volume-prep-provisioning-8698": Phase="Pending", Reason="", readiness=false. Elapsed: 6.417675547s
Jun  4 00:18:14.878: INFO: Pod "volume-prep-provisioning-8698": Phase="Pending", Reason="", readiness=false. Elapsed: 8.525977178s
Jun  4 00:18:16.982: INFO: Pod "volume-prep-provisioning-8698": Phase="Pending", Reason="", readiness=false. Elapsed: 10.630049436s
Jun  4 00:18:19.084: INFO: Pod "volume-prep-provisioning-8698": Phase="Pending", Reason="", readiness=false. Elapsed: 12.731993919s
Jun  4 00:18:21.219: INFO: Pod "volume-prep-provisioning-8698": Phase="Pending", Reason="", readiness=false. Elapsed: 14.866959021s
Jun  4 00:18:23.325: INFO: Pod "volume-prep-provisioning-8698": Phase="Pending", Reason="", readiness=false. Elapsed: 16.972743714s
Jun  4 00:18:25.427: INFO: Pod "volume-prep-provisioning-8698": Phase="Pending", Reason="", readiness=false. Elapsed: 19.074658137s
Jun  4 00:18:27.530: INFO: Pod "volume-prep-provisioning-8698": Phase="Pending", Reason="", readiness=false. Elapsed: 21.177937444s
Jun  4 00:18:29.633: INFO: Pod "volume-prep-provisioning-8698": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.280302023s
STEP: Saw pod success
Jun  4 00:18:29.633: INFO: Pod "volume-prep-provisioning-8698" satisfied condition "Succeeded or Failed"
Jun  4 00:18:29.633: INFO: Deleting pod "volume-prep-provisioning-8698" in namespace "provisioning-8698"
Jun  4 00:18:29.740: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-8698" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-r9ht
STEP: Checking for subpath error in container status
Jun  4 00:19:36.148: INFO: Deleting pod "pod-subpath-test-dynamicpv-r9ht" in namespace "provisioning-8698"
Jun  4 00:19:36.258: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-r9ht" to be fully deleted
STEP: Deleting pod
Jun  4 00:19:36.371: INFO: Deleting pod "pod-subpath-test-dynamicpv-r9ht" in namespace "provisioning-8698"
STEP: Deleting pvc
Jun  4 00:19:36.679: INFO: Deleting PersistentVolumeClaim "awsj6bhk"
... skipping 32 lines ...
Jun  4 00:19:11.002: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8250-e2e-sc5m5tn
STEP: creating a claim
Jun  4 00:19:11.108: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-bx8h
STEP: Creating a pod to test subpath
Jun  4 00:19:11.437: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-bx8h" in namespace "provisioning-8250" to be "Succeeded or Failed"
Jun  4 00:19:11.541: INFO: Pod "pod-subpath-test-dynamicpv-bx8h": Phase="Pending", Reason="", readiness=false. Elapsed: 104.440272ms
Jun  4 00:19:13.646: INFO: Pod "pod-subpath-test-dynamicpv-bx8h": Phase="Pending", Reason="", readiness=false. Elapsed: 2.209681584s
Jun  4 00:19:15.772: INFO: Pod "pod-subpath-test-dynamicpv-bx8h": Phase="Pending", Reason="", readiness=false. Elapsed: 4.335431431s
Jun  4 00:19:17.878: INFO: Pod "pod-subpath-test-dynamicpv-bx8h": Phase="Pending", Reason="", readiness=false. Elapsed: 6.441504123s
Jun  4 00:19:19.984: INFO: Pod "pod-subpath-test-dynamicpv-bx8h": Phase="Pending", Reason="", readiness=false. Elapsed: 8.547591994s
Jun  4 00:19:22.089: INFO: Pod "pod-subpath-test-dynamicpv-bx8h": Phase="Pending", Reason="", readiness=false. Elapsed: 10.652194492s
Jun  4 00:19:24.194: INFO: Pod "pod-subpath-test-dynamicpv-bx8h": Phase="Pending", Reason="", readiness=false. Elapsed: 12.757669773s
Jun  4 00:19:26.312: INFO: Pod "pod-subpath-test-dynamicpv-bx8h": Phase="Pending", Reason="", readiness=false. Elapsed: 14.875582864s
Jun  4 00:19:28.418: INFO: Pod "pod-subpath-test-dynamicpv-bx8h": Phase="Pending", Reason="", readiness=false. Elapsed: 16.981379537s
Jun  4 00:19:30.523: INFO: Pod "pod-subpath-test-dynamicpv-bx8h": Phase="Pending", Reason="", readiness=false. Elapsed: 19.08640272s
Jun  4 00:19:32.633: INFO: Pod "pod-subpath-test-dynamicpv-bx8h": Phase="Pending", Reason="", readiness=false. Elapsed: 21.196069666s
Jun  4 00:19:34.738: INFO: Pod "pod-subpath-test-dynamicpv-bx8h": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.300864575s
STEP: Saw pod success
Jun  4 00:19:34.738: INFO: Pod "pod-subpath-test-dynamicpv-bx8h" satisfied condition "Succeeded or Failed"
Jun  4 00:19:34.842: INFO: Trying to get logs from node ip-172-20-48-253.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-bx8h container test-container-subpath-dynamicpv-bx8h: <nil>
STEP: delete the pod
Jun  4 00:19:35.066: INFO: Waiting for pod pod-subpath-test-dynamicpv-bx8h to disappear
Jun  4 00:19:35.170: INFO: Pod pod-subpath-test-dynamicpv-bx8h no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-bx8h
Jun  4 00:19:35.170: INFO: Deleting pod "pod-subpath-test-dynamicpv-bx8h" in namespace "provisioning-8250"
... skipping 158 lines ...
Jun  4 00:19:14.103: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-163-e2e-scc66gm
STEP: creating a claim
Jun  4 00:19:14.207: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-b692
STEP: Creating a pod to test multi_subpath
Jun  4 00:19:14.521: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-b692" in namespace "provisioning-163" to be "Succeeded or Failed"
Jun  4 00:19:14.625: INFO: Pod "pod-subpath-test-dynamicpv-b692": Phase="Pending", Reason="", readiness=false. Elapsed: 103.236797ms
Jun  4 00:19:16.729: INFO: Pod "pod-subpath-test-dynamicpv-b692": Phase="Pending", Reason="", readiness=false. Elapsed: 2.207040829s
Jun  4 00:19:18.833: INFO: Pod "pod-subpath-test-dynamicpv-b692": Phase="Pending", Reason="", readiness=false. Elapsed: 4.311119898s
Jun  4 00:19:20.937: INFO: Pod "pod-subpath-test-dynamicpv-b692": Phase="Pending", Reason="", readiness=false. Elapsed: 6.415247175s
Jun  4 00:19:23.042: INFO: Pod "pod-subpath-test-dynamicpv-b692": Phase="Pending", Reason="", readiness=false. Elapsed: 8.520232072s
Jun  4 00:19:25.147: INFO: Pod "pod-subpath-test-dynamicpv-b692": Phase="Pending", Reason="", readiness=false. Elapsed: 10.624988722s
Jun  4 00:19:27.251: INFO: Pod "pod-subpath-test-dynamicpv-b692": Phase="Pending", Reason="", readiness=false. Elapsed: 12.72950645s
Jun  4 00:19:29.355: INFO: Pod "pod-subpath-test-dynamicpv-b692": Phase="Pending", Reason="", readiness=false. Elapsed: 14.8334232s
Jun  4 00:19:31.484: INFO: Pod "pod-subpath-test-dynamicpv-b692": Phase="Pending", Reason="", readiness=false. Elapsed: 16.962897355s
Jun  4 00:19:33.590: INFO: Pod "pod-subpath-test-dynamicpv-b692": Phase="Pending", Reason="", readiness=false. Elapsed: 19.068611461s
Jun  4 00:19:35.698: INFO: Pod "pod-subpath-test-dynamicpv-b692": Phase="Pending", Reason="", readiness=false. Elapsed: 21.176260084s
Jun  4 00:19:37.813: INFO: Pod "pod-subpath-test-dynamicpv-b692": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.291810682s
STEP: Saw pod success
Jun  4 00:19:37.813: INFO: Pod "pod-subpath-test-dynamicpv-b692" satisfied condition "Succeeded or Failed"
Jun  4 00:19:37.917: INFO: Trying to get logs from node ip-172-20-48-253.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-b692 container test-container-subpath-dynamicpv-b692: <nil>
STEP: delete the pod
Jun  4 00:19:38.134: INFO: Waiting for pod pod-subpath-test-dynamicpv-b692 to disappear
Jun  4 00:19:38.238: INFO: Pod pod-subpath-test-dynamicpv-b692 no longer exists
STEP: Deleting pod
Jun  4 00:19:38.238: INFO: Deleting pod "pod-subpath-test-dynamicpv-b692" in namespace "provisioning-163"
... skipping 239 lines ...
Jun  4 00:17:31.171: INFO: Creating resource for dynamic PV
Jun  4 00:17:31.171: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-8264-e2e-scv5xlp
STEP: creating a claim
Jun  4 00:17:31.276: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun  4 00:17:31.600: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-jxckv" in namespace "snapshotting-8264" to be "Succeeded or Failed"
Jun  4 00:17:31.705: INFO: Pod "pvc-snapshottable-tester-jxckv": Phase="Pending", Reason="", readiness=false. Elapsed: 104.817567ms
Jun  4 00:17:33.809: INFO: Pod "pvc-snapshottable-tester-jxckv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.208952595s
Jun  4 00:17:35.917: INFO: Pod "pvc-snapshottable-tester-jxckv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.316451076s
Jun  4 00:17:38.021: INFO: Pod "pvc-snapshottable-tester-jxckv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.42091227s
Jun  4 00:17:40.126: INFO: Pod "pvc-snapshottable-tester-jxckv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.525925942s
Jun  4 00:17:42.231: INFO: Pod "pvc-snapshottable-tester-jxckv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.630692982s
... skipping 3 lines ...
Jun  4 00:17:50.652: INFO: Pod "pvc-snapshottable-tester-jxckv": Phase="Pending", Reason="", readiness=false. Elapsed: 19.051484132s
Jun  4 00:17:52.756: INFO: Pod "pvc-snapshottable-tester-jxckv": Phase="Pending", Reason="", readiness=false. Elapsed: 21.155949393s
Jun  4 00:17:54.862: INFO: Pod "pvc-snapshottable-tester-jxckv": Phase="Pending", Reason="", readiness=false. Elapsed: 23.261510187s
Jun  4 00:17:56.967: INFO: Pod "pvc-snapshottable-tester-jxckv": Phase="Pending", Reason="", readiness=false. Elapsed: 25.36662082s
Jun  4 00:17:59.073: INFO: Pod "pvc-snapshottable-tester-jxckv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 27.472458794s
STEP: Saw pod success
Jun  4 00:17:59.073: INFO: Pod "pvc-snapshottable-tester-jxckv" satisfied condition "Succeeded or Failed"
Jun  4 00:17:59.678: INFO: Pod pvc-snapshottable-tester-jxckv has the following logs: 
Jun  4 00:17:59.678: INFO: Deleting pod "pvc-snapshottable-tester-jxckv" in namespace "snapshotting-8264"
Jun  4 00:17:59.786: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-jxckv" to be fully deleted
Jun  4 00:17:59.890: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comwls5f] to have phase Bound
Jun  4 00:17:59.994: INFO: PersistentVolumeClaim ebs.csi.aws.comwls5f found and phase=Bound (104.169919ms)
STEP: [init] checking the claim
... skipping 37 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.skFUj8hNl/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  4 00:18:21.217: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-nbwc6" in namespace "snapshotting-8264" to be "Succeeded or Failed"
Jun  4 00:18:21.321: INFO: Pod "pvc-snapshottable-data-tester-nbwc6": Phase="Pending", Reason="", readiness=false. Elapsed: 104.193196ms
Jun  4 00:18:23.425: INFO: Pod "pvc-snapshottable-data-tester-nbwc6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.208639534s
Jun  4 00:18:25.530: INFO: Pod "pvc-snapshottable-data-tester-nbwc6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.313231565s
Jun  4 00:18:27.635: INFO: Pod "pvc-snapshottable-data-tester-nbwc6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.418045539s
Jun  4 00:18:29.744: INFO: Pod "pvc-snapshottable-data-tester-nbwc6": Phase="Pending", Reason="", readiness=false. Elapsed: 8.527116745s
Jun  4 00:18:31.851: INFO: Pod "pvc-snapshottable-data-tester-nbwc6": Phase="Pending", Reason="", readiness=false. Elapsed: 10.634447219s
Jun  4 00:18:33.956: INFO: Pod "pvc-snapshottable-data-tester-nbwc6": Phase="Pending", Reason="", readiness=false. Elapsed: 12.739146174s
Jun  4 00:18:36.061: INFO: Pod "pvc-snapshottable-data-tester-nbwc6": Phase="Pending", Reason="", readiness=false. Elapsed: 14.844205422s
Jun  4 00:18:38.189: INFO: Pod "pvc-snapshottable-data-tester-nbwc6": Phase="Pending", Reason="", readiness=false. Elapsed: 16.972479243s
Jun  4 00:18:40.294: INFO: Pod "pvc-snapshottable-data-tester-nbwc6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.077083669s
STEP: Saw pod success
Jun  4 00:18:40.294: INFO: Pod "pvc-snapshottable-data-tester-nbwc6" satisfied condition "Succeeded or Failed"
Jun  4 00:18:40.506: INFO: Pod pvc-snapshottable-data-tester-nbwc6 has the following logs: 
Jun  4 00:18:40.506: INFO: Deleting pod "pvc-snapshottable-data-tester-nbwc6" in namespace "snapshotting-8264"
Jun  4 00:18:40.617: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-nbwc6" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun  4 00:19:03.146: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-8264 exec restored-pvc-tester-lc2qz --namespace=snapshotting-8264 -- cat /mnt/test/data'
... skipping 130 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  4 00:19:22.829: 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.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun  4 00:19:23.353: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  4 00:19:23.353: INFO: Creating resource for dynamic PV
Jun  4 00:19:23.353: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3942zdk9l
STEP: creating a claim
Jun  4 00:19:23.464: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-npf8
STEP: Checking for subpath error in container status
Jun  4 00:19:35.991: INFO: Deleting pod "pod-subpath-test-dynamicpv-npf8" in namespace "provisioning-3942"
Jun  4 00:19:36.098: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-npf8" to be fully deleted
STEP: Deleting pod
Jun  4 00:19:50.309: INFO: Deleting pod "pod-subpath-test-dynamicpv-npf8" in namespace "provisioning-3942"
STEP: Deleting pvc
Jun  4 00:19:50.622: INFO: Deleting PersistentVolumeClaim "awsg2ntm"
... skipping 13 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.skFUj8hNl/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.skFUj8hNl/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath file is outside the volume [Slow][LinuxOnly]
      /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  4 00:20:06.467: INFO: Driver ebs.csi.aws.com doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
... skipping 1028 lines ...
Jun  4 00:20:10.583: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-8354-e2e-sc8nsp6
STEP: creating a claim
Jun  4 00:20:10.689: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Jun  4 00:20:10.899: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun  4 00:20:11.107: INFO: Error updating pvc ebs.csi.aws.com56f2n: PersistentVolumeClaim "ebs.csi.aws.com56f2n" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8354-e2e-sc8nsp6",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun  4 00:20:41.526: INFO: Error updating pvc ebs.csi.aws.com56f2n: PersistentVolumeClaim "ebs.csi.aws.com56f2n" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 40 lines ...
Jun  4 00:19:10.914: INFO: Creating resource for dynamic PV
Jun  4 00:19:10.914: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3341-e2e-scmcvhm
STEP: creating a claim
Jun  4 00:19:11.019: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-3341
Jun  4 00:19:11.334: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-3341" in namespace "provisioning-3341" to be "Succeeded or Failed"
Jun  4 00:19:11.438: INFO: Pod "volume-prep-provisioning-3341": Phase="Pending", Reason="", readiness=false. Elapsed: 103.494073ms
Jun  4 00:19:13.542: INFO: Pod "volume-prep-provisioning-3341": Phase="Pending", Reason="", readiness=false. Elapsed: 2.207992158s
Jun  4 00:19:15.647: INFO: Pod "volume-prep-provisioning-3341": Phase="Pending", Reason="", readiness=false. Elapsed: 4.313049858s
Jun  4 00:19:17.752: INFO: Pod "volume-prep-provisioning-3341": Phase="Pending", Reason="", readiness=false. Elapsed: 6.417789478s
Jun  4 00:19:19.857: INFO: Pod "volume-prep-provisioning-3341": Phase="Pending", Reason="", readiness=false. Elapsed: 8.522303041s
Jun  4 00:19:21.962: INFO: Pod "volume-prep-provisioning-3341": Phase="Pending", Reason="", readiness=false. Elapsed: 10.627103351s
Jun  4 00:19:24.065: INFO: Pod "volume-prep-provisioning-3341": Phase="Pending", Reason="", readiness=false. Elapsed: 12.730802526s
Jun  4 00:19:26.171: INFO: Pod "volume-prep-provisioning-3341": Phase="Pending", Reason="", readiness=false. Elapsed: 14.836677879s
Jun  4 00:19:28.275: INFO: Pod "volume-prep-provisioning-3341": Phase="Pending", Reason="", readiness=false. Elapsed: 16.940998812s
Jun  4 00:19:30.379: INFO: Pod "volume-prep-provisioning-3341": Phase="Pending", Reason="", readiness=false. Elapsed: 19.045040078s
Jun  4 00:19:32.483: INFO: Pod "volume-prep-provisioning-3341": Phase="Pending", Reason="", readiness=false. Elapsed: 21.148704027s
Jun  4 00:19:34.586: INFO: Pod "volume-prep-provisioning-3341": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.251773853s
STEP: Saw pod success
Jun  4 00:19:34.586: INFO: Pod "volume-prep-provisioning-3341" satisfied condition "Succeeded or Failed"
Jun  4 00:19:34.586: INFO: Deleting pod "volume-prep-provisioning-3341" in namespace "provisioning-3341"
Jun  4 00:19:34.696: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-3341" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-vgnp
STEP: Checking for subpath error in container status
Jun  4 00:20:11.116: INFO: Deleting pod "pod-subpath-test-dynamicpv-vgnp" in namespace "provisioning-3341"
Jun  4 00:20:11.226: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-vgnp" to be fully deleted
STEP: Deleting pod
Jun  4 00:20:11.331: INFO: Deleting pod "pod-subpath-test-dynamicpv-vgnp" in namespace "provisioning-3341"
STEP: Deleting pvc
Jun  4 00:20:11.642: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comb87pd"
... skipping 77 lines ...
Jun  4 00:19:55.046: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9168-e2e-scr76hv
STEP: creating a claim
Jun  4 00:19:55.150: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-nrcx
STEP: Creating a pod to test subpath
Jun  4 00:19:55.470: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-nrcx" in namespace "provisioning-9168" to be "Succeeded or Failed"
Jun  4 00:19:55.574: INFO: Pod "pod-subpath-test-dynamicpv-nrcx": Phase="Pending", Reason="", readiness=false. Elapsed: 104.148807ms
Jun  4 00:19:57.679: INFO: Pod "pod-subpath-test-dynamicpv-nrcx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.208941676s
Jun  4 00:19:59.784: INFO: Pod "pod-subpath-test-dynamicpv-nrcx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.314477813s
Jun  4 00:20:01.889: INFO: Pod "pod-subpath-test-dynamicpv-nrcx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.419494341s
Jun  4 00:20:03.994: INFO: Pod "pod-subpath-test-dynamicpv-nrcx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.523871883s
Jun  4 00:20:06.098: INFO: Pod "pod-subpath-test-dynamicpv-nrcx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.628104828s
Jun  4 00:20:08.204: INFO: Pod "pod-subpath-test-dynamicpv-nrcx": Phase="Pending", Reason="", readiness=false. Elapsed: 12.734422625s
Jun  4 00:20:10.309: INFO: Pod "pod-subpath-test-dynamicpv-nrcx": Phase="Pending", Reason="", readiness=false. Elapsed: 14.838939301s
Jun  4 00:20:12.413: INFO: Pod "pod-subpath-test-dynamicpv-nrcx": Phase="Pending", Reason="", readiness=false. Elapsed: 16.943600775s
Jun  4 00:20:14.521: INFO: Pod "pod-subpath-test-dynamicpv-nrcx": Phase="Pending", Reason="", readiness=false. Elapsed: 19.050817992s
Jun  4 00:20:16.626: INFO: Pod "pod-subpath-test-dynamicpv-nrcx": Phase="Pending", Reason="", readiness=false. Elapsed: 21.156294794s
Jun  4 00:20:18.733: INFO: Pod "pod-subpath-test-dynamicpv-nrcx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.263464137s
STEP: Saw pod success
Jun  4 00:20:18.733: INFO: Pod "pod-subpath-test-dynamicpv-nrcx" satisfied condition "Succeeded or Failed"
Jun  4 00:20:18.839: INFO: Trying to get logs from node ip-172-20-58-183.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-nrcx container test-container-subpath-dynamicpv-nrcx: <nil>
STEP: delete the pod
Jun  4 00:20:19.059: INFO: Waiting for pod pod-subpath-test-dynamicpv-nrcx to disappear
Jun  4 00:20:19.163: INFO: Pod pod-subpath-test-dynamicpv-nrcx no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-nrcx
Jun  4 00:20:19.163: INFO: Deleting pod "pod-subpath-test-dynamicpv-nrcx" in namespace "provisioning-9168"
... skipping 83 lines ...
Jun  4 00:19:56.140: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-2047-e2e-sct6r2h
STEP: creating a claim
Jun  4 00:19:56.245: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-xs8d
STEP: Creating a pod to test exec-volume-test
Jun  4 00:19:56.565: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-xs8d" in namespace "volume-2047" to be "Succeeded or Failed"
Jun  4 00:19:56.669: INFO: Pod "exec-volume-test-dynamicpv-xs8d": Phase="Pending", Reason="", readiness=false. Elapsed: 103.920109ms
Jun  4 00:19:58.774: INFO: Pod "exec-volume-test-dynamicpv-xs8d": Phase="Pending", Reason="", readiness=false. Elapsed: 2.209626839s
Jun  4 00:20:00.880: INFO: Pod "exec-volume-test-dynamicpv-xs8d": Phase="Pending", Reason="", readiness=false. Elapsed: 4.315804325s
Jun  4 00:20:02.986: INFO: Pod "exec-volume-test-dynamicpv-xs8d": Phase="Pending", Reason="", readiness=false. Elapsed: 6.421389912s
Jun  4 00:20:05.092: INFO: Pod "exec-volume-test-dynamicpv-xs8d": Phase="Pending", Reason="", readiness=false. Elapsed: 8.527232194s
Jun  4 00:20:07.197: INFO: Pod "exec-volume-test-dynamicpv-xs8d": Phase="Pending", Reason="", readiness=false. Elapsed: 10.632437171s
Jun  4 00:20:09.302: INFO: Pod "exec-volume-test-dynamicpv-xs8d": Phase="Pending", Reason="", readiness=false. Elapsed: 12.736905024s
Jun  4 00:20:11.412: INFO: Pod "exec-volume-test-dynamicpv-xs8d": Phase="Pending", Reason="", readiness=false. Elapsed: 14.847290355s
Jun  4 00:20:13.517: INFO: Pod "exec-volume-test-dynamicpv-xs8d": Phase="Pending", Reason="", readiness=false. Elapsed: 16.952866339s
Jun  4 00:20:15.622: INFO: Pod "exec-volume-test-dynamicpv-xs8d": Phase="Pending", Reason="", readiness=false. Elapsed: 19.057483469s
Jun  4 00:20:17.727: INFO: Pod "exec-volume-test-dynamicpv-xs8d": Phase="Pending", Reason="", readiness=false. Elapsed: 21.16234516s
Jun  4 00:20:19.833: INFO: Pod "exec-volume-test-dynamicpv-xs8d": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.268100553s
STEP: Saw pod success
Jun  4 00:20:19.833: INFO: Pod "exec-volume-test-dynamicpv-xs8d" satisfied condition "Succeeded or Failed"
Jun  4 00:20:19.939: INFO: Trying to get logs from node ip-172-20-41-105.eu-west-3.compute.internal pod exec-volume-test-dynamicpv-xs8d container exec-container-dynamicpv-xs8d: <nil>
STEP: delete the pod
Jun  4 00:20:20.162: INFO: Waiting for pod exec-volume-test-dynamicpv-xs8d to disappear
Jun  4 00:20:20.266: INFO: Pod exec-volume-test-dynamicpv-xs8d no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-xs8d
Jun  4 00:20:20.266: INFO: Deleting pod "exec-volume-test-dynamicpv-xs8d" in namespace "volume-2047"
... skipping 184 lines ...

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

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

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.skFUj8hNl/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.skFUj8hNl/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.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 126 lines ...
Jun  4 00:17:30.687: INFO: Creating resource for dynamic PV
Jun  4 00:17:30.687: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-9177-e2e-scbxbhn
STEP: creating a claim
Jun  4 00:17:30.797: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun  4 00:17:31.136: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-m88kq" in namespace "snapshotting-9177" to be "Succeeded or Failed"
Jun  4 00:17:31.240: INFO: Pod "pvc-snapshottable-tester-m88kq": Phase="Pending", Reason="", readiness=false. Elapsed: 103.978059ms
Jun  4 00:17:33.346: INFO: Pod "pvc-snapshottable-tester-m88kq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.209913997s
Jun  4 00:17:35.451: INFO: Pod "pvc-snapshottable-tester-m88kq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.315166269s
Jun  4 00:17:37.558: INFO: Pod "pvc-snapshottable-tester-m88kq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.421738744s
Jun  4 00:17:39.667: INFO: Pod "pvc-snapshottable-tester-m88kq": Phase="Pending", Reason="", readiness=false. Elapsed: 8.530652396s
Jun  4 00:17:41.771: INFO: Pod "pvc-snapshottable-tester-m88kq": Phase="Pending", Reason="", readiness=false. Elapsed: 10.634518253s
Jun  4 00:17:43.875: INFO: Pod "pvc-snapshottable-tester-m88kq": Phase="Pending", Reason="", readiness=false. Elapsed: 12.738783587s
Jun  4 00:17:45.981: INFO: Pod "pvc-snapshottable-tester-m88kq": Phase="Pending", Reason="", readiness=false. Elapsed: 14.844876374s
Jun  4 00:17:48.085: INFO: Pod "pvc-snapshottable-tester-m88kq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.948929485s
STEP: Saw pod success
Jun  4 00:17:48.085: INFO: Pod "pvc-snapshottable-tester-m88kq" satisfied condition "Succeeded or Failed"
Jun  4 00:17:48.300: INFO: Pod pvc-snapshottable-tester-m88kq has the following logs: 
Jun  4 00:17:48.300: INFO: Deleting pod "pvc-snapshottable-tester-m88kq" in namespace "snapshotting-9177"
Jun  4 00:17:48.423: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-m88kq" to be fully deleted
Jun  4 00:17:48.528: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comh96ll] to have phase Bound
Jun  4 00:17:48.631: INFO: PersistentVolumeClaim ebs.csi.aws.comh96ll found and phase=Bound (103.710624ms)
STEP: [init] checking the claim
... skipping 41 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.skFUj8hNl/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  4 00:18:18.215: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-wr7nl" in namespace "snapshotting-9177" to be "Succeeded or Failed"
Jun  4 00:18:18.319: INFO: Pod "pvc-snapshottable-data-tester-wr7nl": Phase="Pending", Reason="", readiness=false. Elapsed: 103.569363ms
Jun  4 00:18:20.422: INFO: Pod "pvc-snapshottable-data-tester-wr7nl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.207318855s
Jun  4 00:18:22.527: INFO: Pod "pvc-snapshottable-data-tester-wr7nl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.312248305s
Jun  4 00:18:24.631: INFO: Pod "pvc-snapshottable-data-tester-wr7nl": Phase="Pending", Reason="", readiness=false. Elapsed: 6.416045826s
Jun  4 00:18:26.736: INFO: Pod "pvc-snapshottable-data-tester-wr7nl": Phase="Pending", Reason="", readiness=false. Elapsed: 8.521144581s
Jun  4 00:18:28.840: INFO: Pod "pvc-snapshottable-data-tester-wr7nl": Phase="Pending", Reason="", readiness=false. Elapsed: 10.625008959s
Jun  4 00:18:30.945: INFO: Pod "pvc-snapshottable-data-tester-wr7nl": Phase="Pending", Reason="", readiness=false. Elapsed: 12.729652721s
Jun  4 00:18:33.048: INFO: Pod "pvc-snapshottable-data-tester-wr7nl": Phase="Pending", Reason="", readiness=false. Elapsed: 14.833266162s
Jun  4 00:18:35.153: INFO: Pod "pvc-snapshottable-data-tester-wr7nl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.937729835s
STEP: Saw pod success
Jun  4 00:18:35.153: INFO: Pod "pvc-snapshottable-data-tester-wr7nl" satisfied condition "Succeeded or Failed"
Jun  4 00:18:35.362: INFO: Pod pvc-snapshottable-data-tester-wr7nl has the following logs: 
Jun  4 00:18:35.362: INFO: Deleting pod "pvc-snapshottable-data-tester-wr7nl" in namespace "snapshotting-9177"
Jun  4 00:18:35.473: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-wr7nl" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun  4 00:19:51.993: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-9177 exec restored-pvc-tester-lcwx2 --namespace=snapshotting-9177 -- cat /mnt/test/data'
... skipping 31 lines ...
Jun  4 00:20:17.870: INFO: volumesnapshotcontents pre-provisioned-snapcontent-e32fdd5c-ba77-4fc8-a5df-729da1c2976e has been found and is not deleted
Jun  4 00:20:18.975: INFO: volumesnapshotcontents pre-provisioned-snapcontent-e32fdd5c-ba77-4fc8-a5df-729da1c2976e has been found and is not deleted
Jun  4 00:20:20.079: INFO: volumesnapshotcontents pre-provisioned-snapcontent-e32fdd5c-ba77-4fc8-a5df-729da1c2976e has been found and is not deleted
Jun  4 00:20:21.185: INFO: volumesnapshotcontents pre-provisioned-snapcontent-e32fdd5c-ba77-4fc8-a5df-729da1c2976e has been found and is not deleted
Jun  4 00:20:22.289: INFO: volumesnapshotcontents pre-provisioned-snapcontent-e32fdd5c-ba77-4fc8-a5df-729da1c2976e has been found and is not deleted
Jun  4 00:20:23.394: INFO: volumesnapshotcontents pre-provisioned-snapcontent-e32fdd5c-ba77-4fc8-a5df-729da1c2976e has been found and is not deleted
Jun  4 00:20:24.395: INFO: WaitUntil failed after reaching the timeout 30s
[AfterEach] volume snapshot controller
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:221
Jun  4 00:20:24.501: INFO: Pod restored-pvc-tester-lcwx2 has the following logs: 
Jun  4 00:20:24.501: INFO: Deleting pod "restored-pvc-tester-lcwx2" in namespace "snapshotting-9177"
Jun  4 00:20:24.606: INFO: Wait up to 5m0s for pod "restored-pvc-tester-lcwx2" to be fully deleted
Jun  4 00:21:08.816: INFO: deleting claim "snapshotting-9177"/"pvc-s7bs6"
... skipping 180 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  4 00:21:01.455: 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.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  4 00:21:01.990: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  4 00:21:02.756: INFO: Successfully created a new PD: "aws://eu-west-3a/vol-0949890314d064563".
Jun  4 00:21:02.756: INFO: Creating resource for pre-provisioned PV
Jun  4 00:21:02.756: INFO: Creating PVC and PV
... skipping 5 lines ...
Jun  4 00:21:07.358: INFO: PersistentVolumeClaim pvc-9frwv found but phase is Pending instead of Bound.
Jun  4 00:21:09.461: INFO: PersistentVolumeClaim pvc-9frwv found but phase is Pending instead of Bound.
Jun  4 00:21:11.566: INFO: PersistentVolumeClaim pvc-9frwv found and phase=Bound (8.521140251s)
Jun  4 00:21:11.566: INFO: Waiting up to 3m0s for PersistentVolume aws-xj2qr to have phase Bound
Jun  4 00:21:11.669: INFO: PersistentVolume aws-xj2qr found and phase=Bound (102.751727ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  4 00:21:14.291: INFO: Deleting pod "pod-51ef35cb-3a65-408b-a170-50c9613a4840" in namespace "volumemode-7943"
Jun  4 00:21:14.394: INFO: Wait up to 5m0s for pod "pod-51ef35cb-3a65-408b-a170-50c9613a4840" to be fully deleted
STEP: Deleting pv and pvc
Jun  4 00:21:18.601: INFO: Deleting PersistentVolumeClaim "pvc-9frwv"
Jun  4 00:21:18.706: INFO: Deleting PersistentVolume "aws-xj2qr"
Jun  4 00:21:19.009: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0949890314d064563", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0949890314d064563 is currently attached to i-0e8a7d1f42b2c7cf0
	status code: 400, request id: 696f387e-d6ab-44cb-9278-e70fd5d21ac2
Jun  4 00:21:24.574: INFO: Successfully deleted PD "aws://eu-west-3a/vol-0949890314d064563".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  4 00:21:24.574: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-7943" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.skFUj8hNl/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.skFUj8hNl/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
    /tmp/kops.skFUj8hNl/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.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  4 00:21:24.791: INFO: Distro debian doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
... skipping 4 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.skFUj8hNl/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.skFUj8hNl/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.skFUj8hNl/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.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 90 lines ...
Jun  4 00:20:38.150: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-564166hnl
STEP: creating a claim
Jun  4 00:20:38.255: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-p8xl
STEP: Creating a pod to test subpath
Jun  4 00:20:38.577: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-p8xl" in namespace "provisioning-5641" to be "Succeeded or Failed"
Jun  4 00:20:38.682: INFO: Pod "pod-subpath-test-dynamicpv-p8xl": Phase="Pending", Reason="", readiness=false. Elapsed: 104.172138ms
Jun  4 00:20:40.787: INFO: Pod "pod-subpath-test-dynamicpv-p8xl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.209167909s
Jun  4 00:20:42.892: INFO: Pod "pod-subpath-test-dynamicpv-p8xl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.314626606s
Jun  4 00:20:44.996: INFO: Pod "pod-subpath-test-dynamicpv-p8xl": Phase="Pending", Reason="", readiness=false. Elapsed: 6.419008664s
Jun  4 00:20:47.101: INFO: Pod "pod-subpath-test-dynamicpv-p8xl": Phase="Pending", Reason="", readiness=false. Elapsed: 8.523441276s
Jun  4 00:20:49.205: INFO: Pod "pod-subpath-test-dynamicpv-p8xl": Phase="Pending", Reason="", readiness=false. Elapsed: 10.628106539s
Jun  4 00:20:51.310: INFO: Pod "pod-subpath-test-dynamicpv-p8xl": Phase="Pending", Reason="", readiness=false. Elapsed: 12.732198265s
Jun  4 00:20:53.414: INFO: Pod "pod-subpath-test-dynamicpv-p8xl": Phase="Pending", Reason="", readiness=false. Elapsed: 14.836679238s
Jun  4 00:20:55.518: INFO: Pod "pod-subpath-test-dynamicpv-p8xl": Phase="Pending", Reason="", readiness=false. Elapsed: 16.941015305s
Jun  4 00:20:57.623: INFO: Pod "pod-subpath-test-dynamicpv-p8xl": Phase="Pending", Reason="", readiness=false. Elapsed: 19.045151419s
Jun  4 00:20:59.728: INFO: Pod "pod-subpath-test-dynamicpv-p8xl": Phase="Pending", Reason="", readiness=false. Elapsed: 21.150332478s
Jun  4 00:21:01.836: INFO: Pod "pod-subpath-test-dynamicpv-p8xl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.258879663s
STEP: Saw pod success
Jun  4 00:21:01.836: INFO: Pod "pod-subpath-test-dynamicpv-p8xl" satisfied condition "Succeeded or Failed"
Jun  4 00:21:01.954: INFO: Trying to get logs from node ip-172-20-48-253.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-p8xl container test-container-volume-dynamicpv-p8xl: <nil>
STEP: delete the pod
Jun  4 00:21:02.196: INFO: Waiting for pod pod-subpath-test-dynamicpv-p8xl to disappear
Jun  4 00:21:02.299: INFO: Pod pod-subpath-test-dynamicpv-p8xl no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-p8xl
Jun  4 00:21:02.300: INFO: Deleting pod "pod-subpath-test-dynamicpv-p8xl" in namespace "provisioning-5641"
... skipping 157 lines ...
Jun  4 00:21:19.865: INFO: Waiting for pod aws-client to disappear
Jun  4 00:21:19.974: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun  4 00:21:19.974: INFO: Deleting PersistentVolumeClaim "pvc-wt2n7"
Jun  4 00:21:20.085: INFO: Deleting PersistentVolume "aws-4n767"
Jun  4 00:21:20.900: INFO: Couldn't delete PD "aws://eu-west-3a/vol-02245cbce3b5cc9aa", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02245cbce3b5cc9aa is currently attached to i-04ffa1804ffe9827d
	status code: 400, request id: 4ad9c39d-0c40-4e15-90f0-9a5a8d0c2bd2
Jun  4 00:21:26.446: INFO: Couldn't delete PD "aws://eu-west-3a/vol-02245cbce3b5cc9aa", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02245cbce3b5cc9aa is currently attached to i-04ffa1804ffe9827d
	status code: 400, request id: fb094bd2-f392-4359-a89e-f2a7ba8e3f0a
Jun  4 00:21:31.996: INFO: Successfully deleted PD "aws://eu-west-3a/vol-02245cbce3b5cc9aa".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  4 00:21:31.996: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-2483" for this suite.
... skipping 270 lines ...
Jun  4 00:20:57.364: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-1322c276k
STEP: creating a claim
Jun  4 00:20:57.469: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-dlt4
STEP: Creating a pod to test exec-volume-test
Jun  4 00:20:57.786: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-dlt4" in namespace "volume-1322" to be "Succeeded or Failed"
Jun  4 00:20:57.892: INFO: Pod "exec-volume-test-dynamicpv-dlt4": Phase="Pending", Reason="", readiness=false. Elapsed: 106.772423ms
Jun  4 00:20:59.997: INFO: Pod "exec-volume-test-dynamicpv-dlt4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.211409827s
Jun  4 00:21:02.108: INFO: Pod "exec-volume-test-dynamicpv-dlt4": Phase="Pending", Reason="", readiness=false. Elapsed: 4.322624516s
Jun  4 00:21:04.214: INFO: Pod "exec-volume-test-dynamicpv-dlt4": Phase="Pending", Reason="", readiness=false. Elapsed: 6.428269437s
Jun  4 00:21:06.318: INFO: Pod "exec-volume-test-dynamicpv-dlt4": Phase="Pending", Reason="", readiness=false. Elapsed: 8.532843202s
Jun  4 00:21:08.423: INFO: Pod "exec-volume-test-dynamicpv-dlt4": Phase="Pending", Reason="", readiness=false. Elapsed: 10.637448786s
Jun  4 00:21:10.527: INFO: Pod "exec-volume-test-dynamicpv-dlt4": Phase="Pending", Reason="", readiness=false. Elapsed: 12.741580113s
Jun  4 00:21:12.633: INFO: Pod "exec-volume-test-dynamicpv-dlt4": Phase="Pending", Reason="", readiness=false. Elapsed: 14.846975899s
Jun  4 00:21:14.738: INFO: Pod "exec-volume-test-dynamicpv-dlt4": Phase="Pending", Reason="", readiness=false. Elapsed: 16.952402953s
Jun  4 00:21:16.845: INFO: Pod "exec-volume-test-dynamicpv-dlt4": Phase="Pending", Reason="", readiness=false. Elapsed: 19.059706984s
Jun  4 00:21:18.950: INFO: Pod "exec-volume-test-dynamicpv-dlt4": Phase="Pending", Reason="", readiness=false. Elapsed: 21.1644063s
Jun  4 00:21:21.055: INFO: Pod "exec-volume-test-dynamicpv-dlt4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.269397101s
STEP: Saw pod success
Jun  4 00:21:21.055: INFO: Pod "exec-volume-test-dynamicpv-dlt4" satisfied condition "Succeeded or Failed"
Jun  4 00:21:21.160: INFO: Trying to get logs from node ip-172-20-58-183.eu-west-3.compute.internal pod exec-volume-test-dynamicpv-dlt4 container exec-container-dynamicpv-dlt4: <nil>
STEP: delete the pod
Jun  4 00:21:21.388: INFO: Waiting for pod exec-volume-test-dynamicpv-dlt4 to disappear
Jun  4 00:21:21.492: INFO: Pod exec-volume-test-dynamicpv-dlt4 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-dlt4
Jun  4 00:21:21.492: INFO: Deleting pod "exec-volume-test-dynamicpv-dlt4" in namespace "volume-1322"
... skipping 176 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  4 00:21:15.647: 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.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  4 00:21:16.167: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  4 00:21:16.902: INFO: Successfully created a new PD: "aws://eu-west-3a/vol-080ce1094ca46c60b".
Jun  4 00:21:16.902: INFO: Creating resource for pre-provisioned PV
Jun  4 00:21:16.902: INFO: Creating PVC and PV
... skipping 5 lines ...
Jun  4 00:21:21.486: INFO: PersistentVolumeClaim pvc-b69h2 found but phase is Pending instead of Bound.
Jun  4 00:21:23.590: INFO: PersistentVolumeClaim pvc-b69h2 found but phase is Pending instead of Bound.
Jun  4 00:21:25.696: INFO: PersistentVolumeClaim pvc-b69h2 found and phase=Bound (8.521534199s)
Jun  4 00:21:25.696: INFO: Waiting up to 3m0s for PersistentVolume aws-kdl89 to have phase Bound
Jun  4 00:21:25.799: INFO: PersistentVolume aws-kdl89 found and phase=Bound (103.501716ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  4 00:21:28.428: INFO: Deleting pod "pod-81bd266e-ca7f-4cf7-ac47-447d6a5e51d3" in namespace "volumemode-6328"
Jun  4 00:21:28.538: INFO: Wait up to 5m0s for pod "pod-81bd266e-ca7f-4cf7-ac47-447d6a5e51d3" to be fully deleted
STEP: Deleting pv and pvc
Jun  4 00:21:38.748: INFO: Deleting PersistentVolumeClaim "pvc-b69h2"
Jun  4 00:21:38.861: INFO: Deleting PersistentVolume "aws-kdl89"
Jun  4 00:21:39.158: INFO: Couldn't delete PD "aws://eu-west-3a/vol-080ce1094ca46c60b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-080ce1094ca46c60b is currently attached to i-04ffa1804ffe9827d
	status code: 400, request id: c173d5fb-2fdb-4b4c-af9a-0e3796f26715
Jun  4 00:21:44.688: INFO: Couldn't delete PD "aws://eu-west-3a/vol-080ce1094ca46c60b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-080ce1094ca46c60b is currently attached to i-04ffa1804ffe9827d
	status code: 400, request id: 8ca66917-e160-4314-b48b-3b6a937e6d98
Jun  4 00:21:50.256: INFO: Successfully deleted PD "aws://eu-west-3a/vol-080ce1094ca46c60b".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  4 00:21:50.256: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-6328" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.skFUj8hNl/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.skFUj8hNl/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
    /tmp/kops.skFUj8hNl/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.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
SS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
... skipping 27 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.skFUj8hNl/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.skFUj8hNl/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.skFUj8hNl/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.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 90 lines ...
Jun  4 00:19:36.299: INFO: Creating resource for dynamic PV
Jun  4 00:19:36.299: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-6740-e2e-scb74jj
STEP: creating a claim
Jun  4 00:19:36.407: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun  4 00:19:36.720: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-kkmr5" in namespace "snapshotting-6740" to be "Succeeded or Failed"
Jun  4 00:19:36.822: INFO: Pod "pvc-snapshottable-tester-kkmr5": Phase="Pending", Reason="", readiness=false. Elapsed: 101.882572ms
Jun  4 00:19:38.924: INFO: Pod "pvc-snapshottable-tester-kkmr5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.204358834s
Jun  4 00:19:41.028: INFO: Pod "pvc-snapshottable-tester-kkmr5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.307712333s
Jun  4 00:19:43.133: INFO: Pod "pvc-snapshottable-tester-kkmr5": Phase="Pending", Reason="", readiness=false. Elapsed: 6.413511925s
Jun  4 00:19:45.236: INFO: Pod "pvc-snapshottable-tester-kkmr5": Phase="Pending", Reason="", readiness=false. Elapsed: 8.516135046s
Jun  4 00:19:47.338: INFO: Pod "pvc-snapshottable-tester-kkmr5": Phase="Pending", Reason="", readiness=false. Elapsed: 10.618298601s
Jun  4 00:19:49.442: INFO: Pod "pvc-snapshottable-tester-kkmr5": Phase="Pending", Reason="", readiness=false. Elapsed: 12.721777989s
Jun  4 00:19:51.544: INFO: Pod "pvc-snapshottable-tester-kkmr5": Phase="Pending", Reason="", readiness=false. Elapsed: 14.824545496s
Jun  4 00:19:53.648: INFO: Pod "pvc-snapshottable-tester-kkmr5": Phase="Pending", Reason="", readiness=false. Elapsed: 16.92787442s
Jun  4 00:19:55.751: INFO: Pod "pvc-snapshottable-tester-kkmr5": Phase="Pending", Reason="", readiness=false. Elapsed: 19.031201898s
Jun  4 00:19:57.854: INFO: Pod "pvc-snapshottable-tester-kkmr5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.134599688s
STEP: Saw pod success
Jun  4 00:19:57.854: INFO: Pod "pvc-snapshottable-tester-kkmr5" satisfied condition "Succeeded or Failed"
Jun  4 00:19:58.062: INFO: Pod pvc-snapshottable-tester-kkmr5 has the following logs: 
Jun  4 00:19:58.062: INFO: Deleting pod "pvc-snapshottable-tester-kkmr5" in namespace "snapshotting-6740"
Jun  4 00:19:58.179: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-kkmr5" to be fully deleted
Jun  4 00:19:58.288: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.com5fxkm] to have phase Bound
Jun  4 00:19:58.389: INFO: PersistentVolumeClaim ebs.csi.aws.com5fxkm found and phase=Bound (101.422235ms)
STEP: [init] checking the claim
... skipping 32 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.skFUj8hNl/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  4 00:20:45.825: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-szczx" in namespace "snapshotting-6740" to be "Succeeded or Failed"
Jun  4 00:20:45.926: INFO: Pod "pvc-snapshottable-data-tester-szczx": Phase="Pending", Reason="", readiness=false. Elapsed: 101.585022ms
Jun  4 00:20:48.034: INFO: Pod "pvc-snapshottable-data-tester-szczx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.209774686s
Jun  4 00:20:50.137: INFO: Pod "pvc-snapshottable-data-tester-szczx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.3119497s
Jun  4 00:20:52.239: INFO: Pod "pvc-snapshottable-data-tester-szczx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.414000306s
Jun  4 00:20:54.341: INFO: Pod "pvc-snapshottable-data-tester-szczx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.516863256s
Jun  4 00:20:56.444: INFO: Pod "pvc-snapshottable-data-tester-szczx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.619006983s
STEP: Saw pod success
Jun  4 00:20:56.444: INFO: Pod "pvc-snapshottable-data-tester-szczx" satisfied condition "Succeeded or Failed"
Jun  4 00:20:56.654: INFO: Pod pvc-snapshottable-data-tester-szczx has the following logs: 
Jun  4 00:20:56.654: INFO: Deleting pod "pvc-snapshottable-data-tester-szczx" in namespace "snapshotting-6740"
Jun  4 00:20:56.763: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-szczx" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun  4 00:21:19.277: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-6740 exec restored-pvc-tester-lgbs5 --namespace=snapshotting-6740 -- cat /mnt/test/data'
... skipping 255 lines ...
    /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:108
      
      /tmp/kops.skFUj8hNl/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.skFUj8hNl/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-6740 exec restored-pvc-tester-lgbs5 --namespace=snapshotting-6740 -- 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-6740 exec restored-pvc-tester-lgbs5 --namespace=snapshotting-6740 -- 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.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:602
------------------------------
[BeforeEach] [sig-storage] Volume Placement [Feature:vsphere]
... skipping 86 lines ...
Jun  4 00:21:17.871: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  4 00:21:18.762: INFO: Successfully created a new PD: "aws://eu-west-3a/vol-019eb3cf1744a1635".
Jun  4 00:21:18.762: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-7mcd
STEP: Creating a pod to test exec-volume-test
Jun  4 00:21:18.868: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-7mcd" in namespace "volume-9198" to be "Succeeded or Failed"
Jun  4 00:21:18.972: INFO: Pod "exec-volume-test-inlinevolume-7mcd": Phase="Pending", Reason="", readiness=false. Elapsed: 103.513863ms
Jun  4 00:21:21.075: INFO: Pod "exec-volume-test-inlinevolume-7mcd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.207081628s
Jun  4 00:21:23.186: INFO: Pod "exec-volume-test-inlinevolume-7mcd": Phase="Pending", Reason="", readiness=false. Elapsed: 4.318324853s
Jun  4 00:21:25.290: INFO: Pod "exec-volume-test-inlinevolume-7mcd": Phase="Pending", Reason="", readiness=false. Elapsed: 6.422329334s
Jun  4 00:21:27.400: INFO: Pod "exec-volume-test-inlinevolume-7mcd": Phase="Pending", Reason="", readiness=false. Elapsed: 8.532209416s
Jun  4 00:21:29.508: INFO: Pod "exec-volume-test-inlinevolume-7mcd": Phase="Pending", Reason="", readiness=false. Elapsed: 10.639957909s
... skipping 6 lines ...
Jun  4 00:21:44.244: INFO: Pod "exec-volume-test-inlinevolume-7mcd": Phase="Pending", Reason="", readiness=false. Elapsed: 25.375688561s
Jun  4 00:21:46.348: INFO: Pod "exec-volume-test-inlinevolume-7mcd": Phase="Pending", Reason="", readiness=false. Elapsed: 27.479836425s
Jun  4 00:21:48.457: INFO: Pod "exec-volume-test-inlinevolume-7mcd": Phase="Pending", Reason="", readiness=false. Elapsed: 29.588696061s
Jun  4 00:21:50.561: INFO: Pod "exec-volume-test-inlinevolume-7mcd": Phase="Pending", Reason="", readiness=false. Elapsed: 31.693444179s
Jun  4 00:21:52.667: INFO: Pod "exec-volume-test-inlinevolume-7mcd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 33.798881517s
STEP: Saw pod success
Jun  4 00:21:52.667: INFO: Pod "exec-volume-test-inlinevolume-7mcd" satisfied condition "Succeeded or Failed"
Jun  4 00:21:52.771: INFO: Trying to get logs from node ip-172-20-41-105.eu-west-3.compute.internal pod exec-volume-test-inlinevolume-7mcd container exec-container-inlinevolume-7mcd: <nil>
STEP: delete the pod
Jun  4 00:21:52.989: INFO: Waiting for pod exec-volume-test-inlinevolume-7mcd to disappear
Jun  4 00:21:53.093: INFO: Pod exec-volume-test-inlinevolume-7mcd no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-7mcd
Jun  4 00:21:53.093: INFO: Deleting pod "exec-volume-test-inlinevolume-7mcd" in namespace "volume-9198"
Jun  4 00:21:53.427: INFO: Couldn't delete PD "aws://eu-west-3a/vol-019eb3cf1744a1635", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-019eb3cf1744a1635 is currently attached to i-04ffa1804ffe9827d
	status code: 400, request id: 7384b971-fb00-4d69-aaff-2ab30bc922b3
Jun  4 00:21:59.004: INFO: Couldn't delete PD "aws://eu-west-3a/vol-019eb3cf1744a1635", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-019eb3cf1744a1635 is currently attached to i-04ffa1804ffe9827d
	status code: 400, request id: 96335930-efec-4b5f-8087-663dd2c11211
Jun  4 00:22:04.525: INFO: Couldn't delete PD "aws://eu-west-3a/vol-019eb3cf1744a1635", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-019eb3cf1744a1635 is currently attached to i-04ffa1804ffe9827d
	status code: 400, request id: 1179acae-429d-4064-b250-e7d9aee751b3
Jun  4 00:22:10.062: INFO: Couldn't delete PD "aws://eu-west-3a/vol-019eb3cf1744a1635", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-019eb3cf1744a1635 is currently attached to i-04ffa1804ffe9827d
	status code: 400, request id: e2a2a270-ee48-4fe8-934c-d3582e4338a7
Jun  4 00:22:15.625: INFO: Successfully deleted PD "aws://eu-west-3a/vol-019eb3cf1744a1635".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  4 00:22:15.625: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-9198" for this suite.
... skipping 156 lines ...
Jun  4 00:21:55.364: INFO: Pod aws-client still exists
Jun  4 00:21:57.260: INFO: Waiting for pod aws-client to disappear
Jun  4 00:21:57.363: INFO: Pod aws-client still exists
Jun  4 00:21:59.259: INFO: Waiting for pod aws-client to disappear
Jun  4 00:21:59.363: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun  4 00:21:59.875: INFO: Couldn't delete PD "aws://eu-west-3a/vol-014fe437bef8107f7", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-014fe437bef8107f7 is currently attached to i-016cc349cc178e8d4
	status code: 400, request id: 680c2750-ce2f-4856-8449-263ea511d90d
Jun  4 00:22:05.396: INFO: Couldn't delete PD "aws://eu-west-3a/vol-014fe437bef8107f7", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-014fe437bef8107f7 is currently attached to i-016cc349cc178e8d4
	status code: 400, request id: ba242fd9-e23d-4723-8737-7a9dcb386f2d
Jun  4 00:22:10.955: INFO: Couldn't delete PD "aws://eu-west-3a/vol-014fe437bef8107f7", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-014fe437bef8107f7 is currently attached to i-016cc349cc178e8d4
	status code: 400, request id: 355ad551-d75b-4b0f-82a1-bc1b1fe0c768
Jun  4 00:22:16.487: INFO: Successfully deleted PD "aws://eu-west-3a/vol-014fe437bef8107f7".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  4 00:22:16.487: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-4253" for this suite.
... skipping 364 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.skFUj8hNl/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.skFUj8hNl/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.skFUj8hNl/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.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 42 lines ...
Jun  4 00:21:25.318: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9436-e2e-sczvqz7
STEP: creating a claim
Jun  4 00:21:25.422: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-k5x5
STEP: Creating a pod to test subpath
Jun  4 00:21:25.738: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-k5x5" in namespace "provisioning-9436" to be "Succeeded or Failed"
Jun  4 00:21:25.873: INFO: Pod "pod-subpath-test-dynamicpv-k5x5": Phase="Pending", Reason="", readiness=false. Elapsed: 135.544319ms
Jun  4 00:21:27.977: INFO: Pod "pod-subpath-test-dynamicpv-k5x5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.239832501s
Jun  4 00:21:30.082: INFO: Pod "pod-subpath-test-dynamicpv-k5x5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.344417132s
Jun  4 00:21:32.187: INFO: Pod "pod-subpath-test-dynamicpv-k5x5": Phase="Pending", Reason="", readiness=false. Elapsed: 6.449384503s
Jun  4 00:21:34.292: INFO: Pod "pod-subpath-test-dynamicpv-k5x5": Phase="Pending", Reason="", readiness=false. Elapsed: 8.554158513s
Jun  4 00:21:36.396: INFO: Pod "pod-subpath-test-dynamicpv-k5x5": Phase="Pending", Reason="", readiness=false. Elapsed: 10.658483953s
Jun  4 00:21:38.506: INFO: Pod "pod-subpath-test-dynamicpv-k5x5": Phase="Pending", Reason="", readiness=false. Elapsed: 12.767973226s
Jun  4 00:21:40.609: INFO: Pod "pod-subpath-test-dynamicpv-k5x5": Phase="Pending", Reason="", readiness=false. Elapsed: 14.871516403s
Jun  4 00:21:42.714: INFO: Pod "pod-subpath-test-dynamicpv-k5x5": Phase="Pending", Reason="", readiness=false. Elapsed: 16.97596919s
Jun  4 00:21:44.817: INFO: Pod "pod-subpath-test-dynamicpv-k5x5": Phase="Pending", Reason="", readiness=false. Elapsed: 19.079614163s
Jun  4 00:21:46.922: INFO: Pod "pod-subpath-test-dynamicpv-k5x5": Phase="Pending", Reason="", readiness=false. Elapsed: 21.183922177s
Jun  4 00:21:49.026: INFO: Pod "pod-subpath-test-dynamicpv-k5x5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.288052712s
STEP: Saw pod success
Jun  4 00:21:49.026: INFO: Pod "pod-subpath-test-dynamicpv-k5x5" satisfied condition "Succeeded or Failed"
Jun  4 00:21:49.129: INFO: Trying to get logs from node ip-172-20-41-105.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-k5x5 container test-container-subpath-dynamicpv-k5x5: <nil>
STEP: delete the pod
Jun  4 00:21:49.349: INFO: Waiting for pod pod-subpath-test-dynamicpv-k5x5 to disappear
Jun  4 00:21:49.453: INFO: Pod pod-subpath-test-dynamicpv-k5x5 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-k5x5
Jun  4 00:21:49.453: INFO: Deleting pod "pod-subpath-test-dynamicpv-k5x5" in namespace "provisioning-9436"
... skipping 174 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.skFUj8hNl/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.skFUj8hNl/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.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 253 lines ...
Jun  4 00:21:46.050: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  4 00:21:46.782: INFO: Successfully created a new PD: "aws://eu-west-3a/vol-04788922fa802a32b".
Jun  4 00:21:46.782: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-wg25
STEP: Creating a pod to test exec-volume-test
Jun  4 00:21:46.890: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-wg25" in namespace "volume-2488" to be "Succeeded or Failed"
Jun  4 00:21:46.995: INFO: Pod "exec-volume-test-inlinevolume-wg25": Phase="Pending", Reason="", readiness=false. Elapsed: 105.009081ms
Jun  4 00:21:49.100: INFO: Pod "exec-volume-test-inlinevolume-wg25": Phase="Pending", Reason="", readiness=false. Elapsed: 2.210339218s
Jun  4 00:21:51.213: INFO: Pod "exec-volume-test-inlinevolume-wg25": Phase="Pending", Reason="", readiness=false. Elapsed: 4.322706766s
Jun  4 00:21:53.320: INFO: Pod "exec-volume-test-inlinevolume-wg25": Phase="Pending", Reason="", readiness=false. Elapsed: 6.430177106s
Jun  4 00:21:55.425: INFO: Pod "exec-volume-test-inlinevolume-wg25": Phase="Pending", Reason="", readiness=false. Elapsed: 8.535174997s
Jun  4 00:21:57.531: INFO: Pod "exec-volume-test-inlinevolume-wg25": Phase="Pending", Reason="", readiness=false. Elapsed: 10.640884914s
... skipping 6 lines ...
Jun  4 00:22:12.277: INFO: Pod "exec-volume-test-inlinevolume-wg25": Phase="Pending", Reason="", readiness=false. Elapsed: 25.387522735s
Jun  4 00:22:14.383: INFO: Pod "exec-volume-test-inlinevolume-wg25": Phase="Pending", Reason="", readiness=false. Elapsed: 27.493195102s
Jun  4 00:22:16.488: INFO: Pod "exec-volume-test-inlinevolume-wg25": Phase="Pending", Reason="", readiness=false. Elapsed: 29.597903099s
Jun  4 00:22:18.593: INFO: Pod "exec-volume-test-inlinevolume-wg25": Phase="Pending", Reason="", readiness=false. Elapsed: 31.702783148s
Jun  4 00:22:20.698: INFO: Pod "exec-volume-test-inlinevolume-wg25": Phase="Succeeded", Reason="", readiness=false. Elapsed: 33.807770304s
STEP: Saw pod success
Jun  4 00:22:20.698: INFO: Pod "exec-volume-test-inlinevolume-wg25" satisfied condition "Succeeded or Failed"
Jun  4 00:22:20.803: INFO: Trying to get logs from node ip-172-20-41-105.eu-west-3.compute.internal pod exec-volume-test-inlinevolume-wg25 container exec-container-inlinevolume-wg25: <nil>
STEP: delete the pod
Jun  4 00:22:21.030: INFO: Waiting for pod exec-volume-test-inlinevolume-wg25 to disappear
Jun  4 00:22:21.135: INFO: Pod exec-volume-test-inlinevolume-wg25 no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-wg25
Jun  4 00:22:21.135: INFO: Deleting pod "exec-volume-test-inlinevolume-wg25" in namespace "volume-2488"
Jun  4 00:22:21.466: INFO: Couldn't delete PD "aws://eu-west-3a/vol-04788922fa802a32b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04788922fa802a32b is currently attached to i-04ffa1804ffe9827d
	status code: 400, request id: df5de744-ff39-4228-8c60-1d319a9e48db
Jun  4 00:22:27.060: INFO: Couldn't delete PD "aws://eu-west-3a/vol-04788922fa802a32b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04788922fa802a32b is currently attached to i-04ffa1804ffe9827d
	status code: 400, request id: b4fc0fb7-75f9-4f40-befc-e8f130c6f8df
Jun  4 00:22:32.564: INFO: Couldn't delete PD "aws://eu-west-3a/vol-04788922fa802a32b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04788922fa802a32b is currently attached to i-04ffa1804ffe9827d
	status code: 400, request id: 4f533ef1-9c6a-4c73-8b34-edcf292db664
Jun  4 00:22:38.125: INFO: Successfully deleted PD "aws://eu-west-3a/vol-04788922fa802a32b".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  4 00:22:38.125: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-2488" for this suite.
... skipping 265 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.skFUj8hNl/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.skFUj8hNl/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.skFUj8hNl/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.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

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

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

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

    /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 84 lines ...
Jun  4 00:21:51.770: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2089-e2e-sc9m5xl
STEP: creating a claim
Jun  4 00:21:51.881: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-qf82
STEP: Creating a pod to test atomic-volume-subpath
Jun  4 00:21:52.203: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-qf82" in namespace "provisioning-2089" to be "Succeeded or Failed"
Jun  4 00:21:52.307: INFO: Pod "pod-subpath-test-dynamicpv-qf82": Phase="Pending", Reason="", readiness=false. Elapsed: 104.038482ms
Jun  4 00:21:54.412: INFO: Pod "pod-subpath-test-dynamicpv-qf82": Phase="Pending", Reason="", readiness=false. Elapsed: 2.20885297s
Jun  4 00:21:56.517: INFO: Pod "pod-subpath-test-dynamicpv-qf82": Phase="Pending", Reason="", readiness=false. Elapsed: 4.314019841s
Jun  4 00:21:58.622: INFO: Pod "pod-subpath-test-dynamicpv-qf82": Phase="Pending", Reason="", readiness=false. Elapsed: 6.418875405s
Jun  4 00:22:00.726: INFO: Pod "pod-subpath-test-dynamicpv-qf82": Phase="Pending", Reason="", readiness=false. Elapsed: 8.523166479s
Jun  4 00:22:02.830: INFO: Pod "pod-subpath-test-dynamicpv-qf82": Phase="Pending", Reason="", readiness=false. Elapsed: 10.627691701s
... skipping 11 lines ...
Jun  4 00:22:28.098: INFO: Pod "pod-subpath-test-dynamicpv-qf82": Phase="Running", Reason="", readiness=true. Elapsed: 35.895430305s
Jun  4 00:22:30.203: INFO: Pod "pod-subpath-test-dynamicpv-qf82": Phase="Running", Reason="", readiness=true. Elapsed: 38.000363068s
Jun  4 00:22:32.307: INFO: Pod "pod-subpath-test-dynamicpv-qf82": Phase="Running", Reason="", readiness=true. Elapsed: 40.104370509s
Jun  4 00:22:34.411: INFO: Pod "pod-subpath-test-dynamicpv-qf82": Phase="Running", Reason="", readiness=true. Elapsed: 42.208690619s
Jun  4 00:22:36.516: INFO: Pod "pod-subpath-test-dynamicpv-qf82": Phase="Succeeded", Reason="", readiness=false. Elapsed: 44.313811047s
STEP: Saw pod success
Jun  4 00:22:36.517: INFO: Pod "pod-subpath-test-dynamicpv-qf82" satisfied condition "Succeeded or Failed"
Jun  4 00:22:36.620: INFO: Trying to get logs from node ip-172-20-41-105.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-qf82 container test-container-subpath-dynamicpv-qf82: <nil>
STEP: delete the pod
Jun  4 00:22:36.834: INFO: Waiting for pod pod-subpath-test-dynamicpv-qf82 to disappear
Jun  4 00:22:36.938: INFO: Pod pod-subpath-test-dynamicpv-qf82 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-qf82
Jun  4 00:22:36.938: INFO: Deleting pod "pod-subpath-test-dynamicpv-qf82" in namespace "provisioning-2089"
... skipping 39 lines ...
Jun  4 00:22:53.930: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 537 lines ...
Jun  4 00:21:46.489: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-7947-e2e-scmcxq5      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-7947    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-7947-e2e-scmcxq5,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-7947    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-7947-e2e-scmcxq5,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-7947    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-7947-e2e-scmcxq5,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-7947-e2e-scmcxq5    b1f20b3f-c050-4384-b273-8858e4272790 9280 0 2021-06-04 00:21:46 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-04 00:21:46 +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-8wqx2 pvc- provisioning-7947  54d9e655-6fcb-413e-87f9-3709dc0570ab 9290 0 2021-06-04 00:21:46 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-04 00:21:46 +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-7947-e2e-scmcxq5,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-d87b83fe-876a-4067-87ed-cfb8040cedf0 in namespace provisioning-7947
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun  4 00:22:09.649: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-42tjq" in namespace "provisioning-7947" to be "Succeeded or Failed"
Jun  4 00:22:09.754: INFO: Pod "pvc-volume-tester-writer-42tjq": Phase="Pending", Reason="", readiness=false. Elapsed: 104.48768ms
Jun  4 00:22:11.860: INFO: Pod "pvc-volume-tester-writer-42tjq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.210370354s
Jun  4 00:22:13.965: INFO: Pod "pvc-volume-tester-writer-42tjq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.316199968s
Jun  4 00:22:16.070: INFO: Pod "pvc-volume-tester-writer-42tjq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.420737349s
Jun  4 00:22:18.175: INFO: Pod "pvc-volume-tester-writer-42tjq": Phase="Pending", Reason="", readiness=false. Elapsed: 8.525537354s
Jun  4 00:22:20.279: INFO: Pod "pvc-volume-tester-writer-42tjq": Phase="Pending", Reason="", readiness=false. Elapsed: 10.630165575s
... skipping 6 lines ...
Jun  4 00:22:35.017: INFO: Pod "pvc-volume-tester-writer-42tjq": Phase="Pending", Reason="", readiness=false. Elapsed: 25.367622981s
Jun  4 00:22:37.121: INFO: Pod "pvc-volume-tester-writer-42tjq": Phase="Pending", Reason="", readiness=false. Elapsed: 27.47231083s
Jun  4 00:22:39.227: INFO: Pod "pvc-volume-tester-writer-42tjq": Phase="Pending", Reason="", readiness=false. Elapsed: 29.577361312s
Jun  4 00:22:41.333: INFO: Pod "pvc-volume-tester-writer-42tjq": Phase="Pending", Reason="", readiness=false. Elapsed: 31.68357514s
Jun  4 00:22:43.438: INFO: Pod "pvc-volume-tester-writer-42tjq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 33.789124617s
STEP: Saw pod success
Jun  4 00:22:43.438: INFO: Pod "pvc-volume-tester-writer-42tjq" satisfied condition "Succeeded or Failed"
Jun  4 00:22:43.648: INFO: Pod pvc-volume-tester-writer-42tjq has the following logs: 
Jun  4 00:22:43.648: INFO: Deleting pod "pvc-volume-tester-writer-42tjq" in namespace "provisioning-7947"
Jun  4 00:22:43.767: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-42tjq" 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-48-253.eu-west-3.compute.internal"
Jun  4 00:22:44.187: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-s2hjh" in namespace "provisioning-7947" to be "Succeeded or Failed"
Jun  4 00:22:44.297: INFO: Pod "pvc-volume-tester-reader-s2hjh": Phase="Pending", Reason="", readiness=false. Elapsed: 109.476192ms
Jun  4 00:22:46.403: INFO: Pod "pvc-volume-tester-reader-s2hjh": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.215585104s
STEP: Saw pod success
Jun  4 00:22:46.403: INFO: Pod "pvc-volume-tester-reader-s2hjh" satisfied condition "Succeeded or Failed"
Jun  4 00:22:46.615: INFO: Pod pvc-volume-tester-reader-s2hjh has the following logs: hello world

Jun  4 00:22:46.615: INFO: Deleting pod "pvc-volume-tester-reader-s2hjh" in namespace "provisioning-7947"
Jun  4 00:22:46.724: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-s2hjh" to be fully deleted
Jun  4 00:22:46.830: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-8wqx2] to have phase Bound
Jun  4 00:22:46.934: INFO: PersistentVolumeClaim pvc-8wqx2 found and phase=Bound (103.922729ms)
... skipping 37 lines ...
Jun  4 00:21:32.748: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2244vnl52
STEP: creating a claim
Jun  4 00:21:32.854: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-p7mq
STEP: Creating a pod to test subpath
Jun  4 00:21:33.173: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-p7mq" in namespace "provisioning-2244" to be "Succeeded or Failed"
Jun  4 00:21:33.279: INFO: Pod "pod-subpath-test-dynamicpv-p7mq": Phase="Pending", Reason="", readiness=false. Elapsed: 105.23989ms
Jun  4 00:21:35.383: INFO: Pod "pod-subpath-test-dynamicpv-p7mq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.209830676s
Jun  4 00:21:37.488: INFO: Pod "pod-subpath-test-dynamicpv-p7mq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.314736205s
Jun  4 00:21:39.593: INFO: Pod "pod-subpath-test-dynamicpv-p7mq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.419734398s
Jun  4 00:21:41.699: INFO: Pod "pod-subpath-test-dynamicpv-p7mq": Phase="Pending", Reason="", readiness=false. Elapsed: 8.52535326s
Jun  4 00:21:43.804: INFO: Pod "pod-subpath-test-dynamicpv-p7mq": Phase="Pending", Reason="", readiness=false. Elapsed: 10.630023509s
Jun  4 00:21:45.909: INFO: Pod "pod-subpath-test-dynamicpv-p7mq": Phase="Pending", Reason="", readiness=false. Elapsed: 12.735906008s
Jun  4 00:21:48.014: INFO: Pod "pod-subpath-test-dynamicpv-p7mq": Phase="Pending", Reason="", readiness=false. Elapsed: 14.840755598s
Jun  4 00:21:50.120: INFO: Pod "pod-subpath-test-dynamicpv-p7mq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.946972721s
STEP: Saw pod success
Jun  4 00:21:50.121: INFO: Pod "pod-subpath-test-dynamicpv-p7mq" satisfied condition "Succeeded or Failed"
Jun  4 00:21:50.225: INFO: Trying to get logs from node ip-172-20-35-212.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-p7mq container test-container-subpath-dynamicpv-p7mq: <nil>
STEP: delete the pod
Jun  4 00:21:50.444: INFO: Waiting for pod pod-subpath-test-dynamicpv-p7mq to disappear
Jun  4 00:21:50.549: INFO: Pod pod-subpath-test-dynamicpv-p7mq no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-p7mq
Jun  4 00:21:50.549: INFO: Deleting pod "pod-subpath-test-dynamicpv-p7mq" in namespace "provisioning-2244"
STEP: Creating pod pod-subpath-test-dynamicpv-p7mq
STEP: Creating a pod to test subpath
Jun  4 00:21:50.760: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-p7mq" in namespace "provisioning-2244" to be "Succeeded or Failed"
Jun  4 00:21:50.866: INFO: Pod "pod-subpath-test-dynamicpv-p7mq": Phase="Pending", Reason="", readiness=false. Elapsed: 105.353537ms
Jun  4 00:21:52.972: INFO: Pod "pod-subpath-test-dynamicpv-p7mq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.211566771s
Jun  4 00:21:55.078: INFO: Pod "pod-subpath-test-dynamicpv-p7mq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.318146124s
Jun  4 00:21:57.184: INFO: Pod "pod-subpath-test-dynamicpv-p7mq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.423442104s
Jun  4 00:21:59.290: INFO: Pod "pod-subpath-test-dynamicpv-p7mq": Phase="Pending", Reason="", readiness=false. Elapsed: 8.529476559s
Jun  4 00:22:01.396: INFO: Pod "pod-subpath-test-dynamicpv-p7mq": Phase="Pending", Reason="", readiness=false. Elapsed: 10.635548428s
... skipping 14 lines ...
Jun  4 00:22:32.988: INFO: Pod "pod-subpath-test-dynamicpv-p7mq": Phase="Pending", Reason="", readiness=false. Elapsed: 42.227348459s
Jun  4 00:22:35.094: INFO: Pod "pod-subpath-test-dynamicpv-p7mq": Phase="Pending", Reason="", readiness=false. Elapsed: 44.333347931s
Jun  4 00:22:37.198: INFO: Pod "pod-subpath-test-dynamicpv-p7mq": Phase="Pending", Reason="", readiness=false. Elapsed: 46.438293157s
Jun  4 00:22:39.304: INFO: Pod "pod-subpath-test-dynamicpv-p7mq": Phase="Pending", Reason="", readiness=false. Elapsed: 48.544331214s
Jun  4 00:22:41.412: INFO: Pod "pod-subpath-test-dynamicpv-p7mq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 50.652256314s
STEP: Saw pod success
Jun  4 00:22:41.412: INFO: Pod "pod-subpath-test-dynamicpv-p7mq" satisfied condition "Succeeded or Failed"
Jun  4 00:22:41.522: INFO: Trying to get logs from node ip-172-20-35-212.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-p7mq container test-container-subpath-dynamicpv-p7mq: <nil>
STEP: delete the pod
Jun  4 00:22:41.739: INFO: Waiting for pod pod-subpath-test-dynamicpv-p7mq to disappear
Jun  4 00:22:41.845: INFO: Pod pod-subpath-test-dynamicpv-p7mq no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-p7mq
Jun  4 00:22:41.845: INFO: Deleting pod "pod-subpath-test-dynamicpv-p7mq" in namespace "provisioning-2244"
... skipping 153 lines ...
Jun  4 00:22:21.647: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6540-e2e-scrvk6z
STEP: creating a claim
Jun  4 00:22:21.754: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-q94c
STEP: Creating a pod to test subpath
Jun  4 00:22:22.068: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-q94c" in namespace "provisioning-6540" to be "Succeeded or Failed"
Jun  4 00:22:22.171: INFO: Pod "pod-subpath-test-dynamicpv-q94c": Phase="Pending", Reason="", readiness=false. Elapsed: 103.488188ms
Jun  4 00:22:24.275: INFO: Pod "pod-subpath-test-dynamicpv-q94c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.207487406s
Jun  4 00:22:26.388: INFO: Pod "pod-subpath-test-dynamicpv-q94c": Phase="Pending", Reason="", readiness=false. Elapsed: 4.31968982s
Jun  4 00:22:28.492: INFO: Pod "pod-subpath-test-dynamicpv-q94c": Phase="Pending", Reason="", readiness=false. Elapsed: 6.423789427s
Jun  4 00:22:30.601: INFO: Pod "pod-subpath-test-dynamicpv-q94c": Phase="Pending", Reason="", readiness=false. Elapsed: 8.533109153s
Jun  4 00:22:32.708: INFO: Pod "pod-subpath-test-dynamicpv-q94c": Phase="Pending", Reason="", readiness=false. Elapsed: 10.640014675s
Jun  4 00:22:34.812: INFO: Pod "pod-subpath-test-dynamicpv-q94c": Phase="Pending", Reason="", readiness=false. Elapsed: 12.744516169s
Jun  4 00:22:36.917: INFO: Pod "pod-subpath-test-dynamicpv-q94c": Phase="Pending", Reason="", readiness=false. Elapsed: 14.848868732s
Jun  4 00:22:39.022: INFO: Pod "pod-subpath-test-dynamicpv-q94c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.95431772s
STEP: Saw pod success
Jun  4 00:22:39.022: INFO: Pod "pod-subpath-test-dynamicpv-q94c" satisfied condition "Succeeded or Failed"
Jun  4 00:22:39.126: INFO: Trying to get logs from node ip-172-20-41-105.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-q94c container test-container-volume-dynamicpv-q94c: <nil>
STEP: delete the pod
Jun  4 00:22:39.342: INFO: Waiting for pod pod-subpath-test-dynamicpv-q94c to disappear
Jun  4 00:22:39.447: INFO: Pod pod-subpath-test-dynamicpv-q94c no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-q94c
Jun  4 00:22:39.448: INFO: Deleting pod "pod-subpath-test-dynamicpv-q94c" in namespace "provisioning-6540"
... skipping 514 lines ...
Jun  4 00:22:54.646: INFO: PersistentVolumeClaim pvc-5gphp found but phase is Pending instead of Bound.
Jun  4 00:22:56.750: INFO: PersistentVolumeClaim pvc-5gphp found and phase=Bound (8.517637672s)
Jun  4 00:22:56.750: INFO: Waiting up to 3m0s for PersistentVolume aws-z8v9r to have phase Bound
Jun  4 00:22:56.853: INFO: PersistentVolume aws-z8v9r found and phase=Bound (103.168939ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-bspg
STEP: Creating a pod to test exec-volume-test
Jun  4 00:22:57.164: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-bspg" in namespace "volume-3964" to be "Succeeded or Failed"
Jun  4 00:22:57.267: INFO: Pod "exec-volume-test-preprovisionedpv-bspg": Phase="Pending", Reason="", readiness=false. Elapsed: 103.018882ms
Jun  4 00:22:59.371: INFO: Pod "exec-volume-test-preprovisionedpv-bspg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.206717002s
Jun  4 00:23:01.475: INFO: Pod "exec-volume-test-preprovisionedpv-bspg": Phase="Pending", Reason="", readiness=false. Elapsed: 4.310492074s
Jun  4 00:23:03.584: INFO: Pod "exec-volume-test-preprovisionedpv-bspg": Phase="Pending", Reason="", readiness=false. Elapsed: 6.420477582s
Jun  4 00:23:05.688: INFO: Pod "exec-volume-test-preprovisionedpv-bspg": Phase="Pending", Reason="", readiness=false. Elapsed: 8.52422246s
Jun  4 00:23:07.826: INFO: Pod "exec-volume-test-preprovisionedpv-bspg": Phase="Pending", Reason="", readiness=false. Elapsed: 10.661643613s
Jun  4 00:23:09.929: INFO: Pod "exec-volume-test-preprovisionedpv-bspg": Phase="Pending", Reason="", readiness=false. Elapsed: 12.765257646s
Jun  4 00:23:12.033: INFO: Pod "exec-volume-test-preprovisionedpv-bspg": Phase="Pending", Reason="", readiness=false. Elapsed: 14.868712595s
Jun  4 00:23:14.137: INFO: Pod "exec-volume-test-preprovisionedpv-bspg": Phase="Pending", Reason="", readiness=false. Elapsed: 16.972573028s
Jun  4 00:23:16.242: INFO: Pod "exec-volume-test-preprovisionedpv-bspg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.077540345s
STEP: Saw pod success
Jun  4 00:23:16.242: INFO: Pod "exec-volume-test-preprovisionedpv-bspg" satisfied condition "Succeeded or Failed"
Jun  4 00:23:16.345: INFO: Trying to get logs from node ip-172-20-48-253.eu-west-3.compute.internal pod exec-volume-test-preprovisionedpv-bspg container exec-container-preprovisionedpv-bspg: <nil>
STEP: delete the pod
Jun  4 00:23:16.562: INFO: Waiting for pod exec-volume-test-preprovisionedpv-bspg to disappear
Jun  4 00:23:16.668: INFO: Pod exec-volume-test-preprovisionedpv-bspg no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-bspg
Jun  4 00:23:16.668: INFO: Deleting pod "exec-volume-test-preprovisionedpv-bspg" in namespace "volume-3964"
STEP: Deleting pv and pvc
Jun  4 00:23:16.771: INFO: Deleting PersistentVolumeClaim "pvc-5gphp"
Jun  4 00:23:16.877: INFO: Deleting PersistentVolume "aws-z8v9r"
Jun  4 00:23:17.179: INFO: Couldn't delete PD "aws://eu-west-3a/vol-03d31ba6587eb2413", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-03d31ba6587eb2413 is currently attached to i-016cc349cc178e8d4
	status code: 400, request id: acc0db63-4877-4154-a501-b2d33598bd65
Jun  4 00:23:22.691: INFO: Couldn't delete PD "aws://eu-west-3a/vol-03d31ba6587eb2413", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-03d31ba6587eb2413 is currently attached to i-016cc349cc178e8d4
	status code: 400, request id: 3cf13191-0438-4038-a36f-2b3550ae3433
Jun  4 00:23:28.239: INFO: Successfully deleted PD "aws://eu-west-3a/vol-03d31ba6587eb2413".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  4 00:23:28.239: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-3964" for this suite.
... skipping 52 lines ...
Jun  4 00:21:30.066: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-6438hmqcg      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-6438    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-6438hmqcg,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-6438    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-6438hmqcg,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-6438    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-6438hmqcg,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-6438hmqcg    31efe006-3abd-47c8-8d77-185cf4a610f7 8908 0 2021-06-04 00:21:30 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-04 00:21:30 +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-m2tz5 pvc- provisioning-6438  551ded63-e3eb-4edb-acc7-e4ea8160bd06 8909 0 2021-06-04 00:21:30 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-04 00:21:30 +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-6438hmqcg,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-23c1e4a3-7dbb-48d1-9226-766381f1e396 in namespace provisioning-6438
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun  4 00:21:53.228: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-88nsq" in namespace "provisioning-6438" to be "Succeeded or Failed"
Jun  4 00:21:53.337: INFO: Pod "pvc-volume-tester-writer-88nsq": Phase="Pending", Reason="", readiness=false. Elapsed: 108.988322ms
Jun  4 00:21:55.441: INFO: Pod "pvc-volume-tester-writer-88nsq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.212871484s
Jun  4 00:21:57.545: INFO: Pod "pvc-volume-tester-writer-88nsq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.316786174s
Jun  4 00:21:59.650: INFO: Pod "pvc-volume-tester-writer-88nsq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.422555261s
Jun  4 00:22:01.756: INFO: Pod "pvc-volume-tester-writer-88nsq": Phase="Pending", Reason="", readiness=false. Elapsed: 8.527922063s
Jun  4 00:22:03.861: INFO: Pod "pvc-volume-tester-writer-88nsq": Phase="Pending", Reason="", readiness=false. Elapsed: 10.633079002s
... skipping 22 lines ...
Jun  4 00:22:52.287: INFO: Pod "pvc-volume-tester-writer-88nsq": Phase="Pending", Reason="", readiness=false. Elapsed: 59.059002763s
Jun  4 00:22:54.392: INFO: Pod "pvc-volume-tester-writer-88nsq": Phase="Pending", Reason="", readiness=false. Elapsed: 1m1.163907955s
Jun  4 00:22:56.499: INFO: Pod "pvc-volume-tester-writer-88nsq": Phase="Pending", Reason="", readiness=false. Elapsed: 1m3.270986153s
Jun  4 00:22:58.608: INFO: Pod "pvc-volume-tester-writer-88nsq": Phase="Pending", Reason="", readiness=false. Elapsed: 1m5.379843163s
Jun  4 00:23:00.712: INFO: Pod "pvc-volume-tester-writer-88nsq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m7.484185085s
STEP: Saw pod success
Jun  4 00:23:00.712: INFO: Pod "pvc-volume-tester-writer-88nsq" satisfied condition "Succeeded or Failed"
Jun  4 00:23:00.923: INFO: Pod pvc-volume-tester-writer-88nsq has the following logs: 
Jun  4 00:23:00.923: INFO: Deleting pod "pvc-volume-tester-writer-88nsq" in namespace "provisioning-6438"
Jun  4 00:23:01.034: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-88nsq" 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-35-212.eu-west-3.compute.internal"
Jun  4 00:23:01.457: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-h7tft" in namespace "provisioning-6438" to be "Succeeded or Failed"
Jun  4 00:23:01.563: INFO: Pod "pvc-volume-tester-reader-h7tft": Phase="Pending", Reason="", readiness=false. Elapsed: 106.227605ms
Jun  4 00:23:03.667: INFO: Pod "pvc-volume-tester-reader-h7tft": Phase="Pending", Reason="", readiness=false. Elapsed: 2.210288653s
Jun  4 00:23:05.778: INFO: Pod "pvc-volume-tester-reader-h7tft": Phase="Pending", Reason="", readiness=false. Elapsed: 4.321792971s
Jun  4 00:23:07.886: INFO: Pod "pvc-volume-tester-reader-h7tft": Phase="Pending", Reason="", readiness=false. Elapsed: 6.42960071s
Jun  4 00:23:09.991: INFO: Pod "pvc-volume-tester-reader-h7tft": Phase="Pending", Reason="", readiness=false. Elapsed: 8.534561251s
Jun  4 00:23:12.096: INFO: Pod "pvc-volume-tester-reader-h7tft": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.63905107s
STEP: Saw pod success
Jun  4 00:23:12.096: INFO: Pod "pvc-volume-tester-reader-h7tft" satisfied condition "Succeeded or Failed"
Jun  4 00:23:12.306: INFO: Pod pvc-volume-tester-reader-h7tft has the following logs: hello world

Jun  4 00:23:12.306: INFO: Deleting pod "pvc-volume-tester-reader-h7tft" in namespace "provisioning-6438"
Jun  4 00:23:12.416: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-h7tft" to be fully deleted
Jun  4 00:23:12.519: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-m2tz5] to have phase Bound
Jun  4 00:23:12.622: INFO: PersistentVolumeClaim pvc-m2tz5 found and phase=Bound (103.40082ms)
... skipping 55 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.skFUj8hNl/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.skFUj8hNl/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.skFUj8hNl/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.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 76 lines ...
STEP: Deleting pod hostexec-ip-172-20-41-105.eu-west-3.compute.internal-ncqr2 in namespace volumemode-2221
Jun  4 00:23:18.617: INFO: Deleting pod "pod-80dd24d4-d1a8-43f9-9411-124ccb0be2b9" in namespace "volumemode-2221"
Jun  4 00:23:18.722: INFO: Wait up to 5m0s for pod "pod-80dd24d4-d1a8-43f9-9411-124ccb0be2b9" to be fully deleted
STEP: Deleting pv and pvc
Jun  4 00:23:28.929: INFO: Deleting PersistentVolumeClaim "pvc-lctdd"
Jun  4 00:23:29.035: INFO: Deleting PersistentVolume "aws-vvwm7"
Jun  4 00:23:29.340: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0a7402d344f75f654", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a7402d344f75f654 is currently attached to i-04ffa1804ffe9827d
	status code: 400, request id: e85b23fb-fcdc-4975-8a46-c30a8a17e10a
Jun  4 00:23:34.877: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0a7402d344f75f654", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a7402d344f75f654 is currently attached to i-04ffa1804ffe9827d
	status code: 400, request id: 9e8836d3-4121-4750-8d34-6756f0a5a7dd
Jun  4 00:23:40.402: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0a7402d344f75f654", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a7402d344f75f654 is currently attached to i-04ffa1804ffe9827d
	status code: 400, request id: 478cf260-ad62-45c9-aac0-bbf48faa7331
Jun  4 00:23:45.930: INFO: Successfully deleted PD "aws://eu-west-3a/vol-0a7402d344f75f654".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  4 00:23:45.930: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-2221" for this suite.
... skipping 43 lines ...
Jun  4 00:23:03.345: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8873rmnhx
STEP: creating a claim
Jun  4 00:23:03.451: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-nchp
STEP: Creating a pod to test subpath
Jun  4 00:23:03.768: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-nchp" in namespace "provisioning-8873" to be "Succeeded or Failed"
Jun  4 00:23:03.872: INFO: Pod "pod-subpath-test-dynamicpv-nchp": Phase="Pending", Reason="", readiness=false. Elapsed: 104.193853ms
Jun  4 00:23:05.977: INFO: Pod "pod-subpath-test-dynamicpv-nchp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.209753069s
Jun  4 00:23:08.083: INFO: Pod "pod-subpath-test-dynamicpv-nchp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.315309538s
Jun  4 00:23:10.189: INFO: Pod "pod-subpath-test-dynamicpv-nchp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.421046924s
Jun  4 00:23:12.295: INFO: Pod "pod-subpath-test-dynamicpv-nchp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.527180013s
Jun  4 00:23:14.401: INFO: Pod "pod-subpath-test-dynamicpv-nchp": Phase="Pending", Reason="", readiness=false. Elapsed: 10.633381246s
... skipping 2 lines ...
Jun  4 00:23:20.723: INFO: Pod "pod-subpath-test-dynamicpv-nchp": Phase="Pending", Reason="", readiness=false. Elapsed: 16.954758253s
Jun  4 00:23:22.827: INFO: Pod "pod-subpath-test-dynamicpv-nchp": Phase="Pending", Reason="", readiness=false. Elapsed: 19.059483849s
Jun  4 00:23:24.941: INFO: Pod "pod-subpath-test-dynamicpv-nchp": Phase="Pending", Reason="", readiness=false. Elapsed: 21.173232845s
Jun  4 00:23:27.046: INFO: Pod "pod-subpath-test-dynamicpv-nchp": Phase="Pending", Reason="", readiness=false. Elapsed: 23.278017722s
Jun  4 00:23:29.151: INFO: Pod "pod-subpath-test-dynamicpv-nchp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 25.383396734s
STEP: Saw pod success
Jun  4 00:23:29.151: INFO: Pod "pod-subpath-test-dynamicpv-nchp" satisfied condition "Succeeded or Failed"
Jun  4 00:23:29.256: INFO: Trying to get logs from node ip-172-20-58-183.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-nchp container test-container-subpath-dynamicpv-nchp: <nil>
STEP: delete the pod
Jun  4 00:23:30.067: INFO: Waiting for pod pod-subpath-test-dynamicpv-nchp to disappear
Jun  4 00:23:30.171: INFO: Pod pod-subpath-test-dynamicpv-nchp no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-nchp
Jun  4 00:23:30.171: INFO: Deleting pod "pod-subpath-test-dynamicpv-nchp" in namespace "provisioning-8873"
... skipping 332 lines ...
Jun  4 00:23:04.008: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4841546ns
STEP: creating a claim
Jun  4 00:23:04.113: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-7fdc
STEP: Creating a pod to test multi_subpath
Jun  4 00:23:04.430: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-7fdc" in namespace "provisioning-4841" to be "Succeeded or Failed"
Jun  4 00:23:04.534: INFO: Pod "pod-subpath-test-dynamicpv-7fdc": Phase="Pending", Reason="", readiness=false. Elapsed: 104.199588ms
Jun  4 00:23:06.639: INFO: Pod "pod-subpath-test-dynamicpv-7fdc": Phase="Pending", Reason="", readiness=false. Elapsed: 2.209287062s
Jun  4 00:23:08.744: INFO: Pod "pod-subpath-test-dynamicpv-7fdc": Phase="Pending", Reason="", readiness=false. Elapsed: 4.313575607s
Jun  4 00:23:10.851: INFO: Pod "pod-subpath-test-dynamicpv-7fdc": Phase="Pending", Reason="", readiness=false. Elapsed: 6.420756199s
Jun  4 00:23:12.956: INFO: Pod "pod-subpath-test-dynamicpv-7fdc": Phase="Pending", Reason="", readiness=false. Elapsed: 8.525563171s
Jun  4 00:23:15.060: INFO: Pod "pod-subpath-test-dynamicpv-7fdc": Phase="Pending", Reason="", readiness=false. Elapsed: 10.63036063s
Jun  4 00:23:17.165: INFO: Pod "pod-subpath-test-dynamicpv-7fdc": Phase="Pending", Reason="", readiness=false. Elapsed: 12.734686048s
Jun  4 00:23:19.270: INFO: Pod "pod-subpath-test-dynamicpv-7fdc": Phase="Pending", Reason="", readiness=false. Elapsed: 14.839469122s
Jun  4 00:23:21.375: INFO: Pod "pod-subpath-test-dynamicpv-7fdc": Phase="Pending", Reason="", readiness=false. Elapsed: 16.944485332s
Jun  4 00:23:23.480: INFO: Pod "pod-subpath-test-dynamicpv-7fdc": Phase="Pending", Reason="", readiness=false. Elapsed: 19.049960195s
Jun  4 00:23:25.586: INFO: Pod "pod-subpath-test-dynamicpv-7fdc": Phase="Pending", Reason="", readiness=false. Elapsed: 21.155483961s
Jun  4 00:23:27.690: INFO: Pod "pod-subpath-test-dynamicpv-7fdc": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.259559066s
STEP: Saw pod success
Jun  4 00:23:27.690: INFO: Pod "pod-subpath-test-dynamicpv-7fdc" satisfied condition "Succeeded or Failed"
Jun  4 00:23:27.793: INFO: Trying to get logs from node ip-172-20-48-253.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-7fdc container test-container-subpath-dynamicpv-7fdc: <nil>
STEP: delete the pod
Jun  4 00:23:28.015: INFO: Waiting for pod pod-subpath-test-dynamicpv-7fdc to disappear
Jun  4 00:23:28.118: INFO: Pod pod-subpath-test-dynamicpv-7fdc no longer exists
STEP: Deleting pod
Jun  4 00:23:28.118: INFO: Deleting pod "pod-subpath-test-dynamicpv-7fdc" in namespace "provisioning-4841"
... skipping 299 lines ...

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

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

    /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:92
------------------------------
... skipping 92 lines ...
Jun  4 00:22:38.879: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5693l88bs
STEP: creating a claim
Jun  4 00:22:38.984: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-xg58
STEP: Creating a pod to test atomic-volume-subpath
Jun  4 00:22:39.305: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-xg58" in namespace "provisioning-5693" to be "Succeeded or Failed"
Jun  4 00:22:39.409: INFO: Pod "pod-subpath-test-dynamicpv-xg58": Phase="Pending", Reason="", readiness=false. Elapsed: 104.445299ms
Jun  4 00:22:41.522: INFO: Pod "pod-subpath-test-dynamicpv-xg58": Phase="Pending", Reason="", readiness=false. Elapsed: 2.216956589s
Jun  4 00:22:43.628: INFO: Pod "pod-subpath-test-dynamicpv-xg58": Phase="Pending", Reason="", readiness=false. Elapsed: 4.322783582s
Jun  4 00:22:45.733: INFO: Pod "pod-subpath-test-dynamicpv-xg58": Phase="Pending", Reason="", readiness=false. Elapsed: 6.428515827s
Jun  4 00:22:47.838: INFO: Pod "pod-subpath-test-dynamicpv-xg58": Phase="Pending", Reason="", readiness=false. Elapsed: 8.533679126s
Jun  4 00:22:49.944: INFO: Pod "pod-subpath-test-dynamicpv-xg58": Phase="Pending", Reason="", readiness=false. Elapsed: 10.638952046s
... skipping 18 lines ...
Jun  4 00:23:29.953: INFO: Pod "pod-subpath-test-dynamicpv-xg58": Phase="Running", Reason="", readiness=true. Elapsed: 50.648566131s
Jun  4 00:23:32.058: INFO: Pod "pod-subpath-test-dynamicpv-xg58": Phase="Running", Reason="", readiness=true. Elapsed: 52.753664759s
Jun  4 00:23:34.169: INFO: Pod "pod-subpath-test-dynamicpv-xg58": Phase="Running", Reason="", readiness=true. Elapsed: 54.864387383s
Jun  4 00:23:36.275: INFO: Pod "pod-subpath-test-dynamicpv-xg58": Phase="Running", Reason="", readiness=true. Elapsed: 56.96981001s
Jun  4 00:23:38.380: INFO: Pod "pod-subpath-test-dynamicpv-xg58": Phase="Succeeded", Reason="", readiness=false. Elapsed: 59.075414135s
STEP: Saw pod success
Jun  4 00:23:38.380: INFO: Pod "pod-subpath-test-dynamicpv-xg58" satisfied condition "Succeeded or Failed"
Jun  4 00:23:38.485: INFO: Trying to get logs from node ip-172-20-58-183.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-xg58 container test-container-subpath-dynamicpv-xg58: <nil>
STEP: delete the pod
Jun  4 00:23:38.707: INFO: Waiting for pod pod-subpath-test-dynamicpv-xg58 to disappear
Jun  4 00:23:38.811: INFO: Pod pod-subpath-test-dynamicpv-xg58 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-xg58
Jun  4 00:23:38.811: INFO: Deleting pod "pod-subpath-test-dynamicpv-xg58" in namespace "provisioning-5693"
... skipping 131 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  4 00:23:24.399: 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.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  4 00:23:24.909: INFO: Creating resource for dynamic PV
Jun  4 00:23:24.909: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-9100-e2e-sc85brp
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  4 00:23:31.626: INFO: Deleting pod "pod-d2ae68cb-dfdc-45d7-adf3-abd061d93045" in namespace "volumemode-9100"
Jun  4 00:23:31.731: INFO: Wait up to 5m0s for pod "pod-d2ae68cb-dfdc-45d7-adf3-abd061d93045" to be fully deleted
STEP: Deleting pvc
Jun  4 00:23:40.140: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comc68g8"
Jun  4 00:23:40.246: INFO: Waiting up to 5m0s for PersistentVolume pvc-4d40248c-1abb-491e-9597-2b057a6cb898 to get deleted
Jun  4 00:23:40.348: INFO: PersistentVolume pvc-4d40248c-1abb-491e-9597-2b057a6cb898 found and phase=Released (101.61916ms)
... skipping 13 lines ...

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

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

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

      Distro debian doesn't support ntfs -- skipping

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

      Not enough topologies in cluster -- skipping

      /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 61 lines ...
Jun  4 00:23:39.047: INFO: PersistentVolumeClaim pvc-gg6j7 found but phase is Pending instead of Bound.
Jun  4 00:23:41.150: INFO: PersistentVolumeClaim pvc-gg6j7 found and phase=Bound (12.731040322s)
Jun  4 00:23:41.150: INFO: Waiting up to 3m0s for PersistentVolume aws-8scnv to have phase Bound
Jun  4 00:23:41.252: INFO: PersistentVolume aws-8scnv found and phase=Bound (101.942915ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-j2jj
STEP: Creating a pod to test exec-volume-test
Jun  4 00:23:41.561: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-j2jj" in namespace "volume-6229" to be "Succeeded or Failed"
Jun  4 00:23:41.663: INFO: Pod "exec-volume-test-preprovisionedpv-j2jj": Phase="Pending", Reason="", readiness=false. Elapsed: 101.624548ms
Jun  4 00:23:43.767: INFO: Pod "exec-volume-test-preprovisionedpv-j2jj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.205955094s
Jun  4 00:23:45.870: INFO: Pod "exec-volume-test-preprovisionedpv-j2jj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.308249558s
Jun  4 00:23:47.973: INFO: Pod "exec-volume-test-preprovisionedpv-j2jj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.412186001s
Jun  4 00:23:50.076: INFO: Pod "exec-volume-test-preprovisionedpv-j2jj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.514933388s
Jun  4 00:23:52.188: INFO: Pod "exec-volume-test-preprovisionedpv-j2jj": Phase="Pending", Reason="", readiness=false. Elapsed: 10.626546379s
Jun  4 00:23:54.290: INFO: Pod "exec-volume-test-preprovisionedpv-j2jj": Phase="Pending", Reason="", readiness=false. Elapsed: 12.72895784s
Jun  4 00:23:56.394: INFO: Pod "exec-volume-test-preprovisionedpv-j2jj": Phase="Pending", Reason="", readiness=false. Elapsed: 14.832566688s
Jun  4 00:23:58.505: INFO: Pod "exec-volume-test-preprovisionedpv-j2jj": Phase="Pending", Reason="", readiness=false. Elapsed: 16.943597273s
Jun  4 00:24:00.608: INFO: Pod "exec-volume-test-preprovisionedpv-j2jj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.046358769s
STEP: Saw pod success
Jun  4 00:24:00.608: INFO: Pod "exec-volume-test-preprovisionedpv-j2jj" satisfied condition "Succeeded or Failed"
Jun  4 00:24:00.709: INFO: Trying to get logs from node ip-172-20-35-212.eu-west-3.compute.internal pod exec-volume-test-preprovisionedpv-j2jj container exec-container-preprovisionedpv-j2jj: <nil>
STEP: delete the pod
Jun  4 00:24:00.930: INFO: Waiting for pod exec-volume-test-preprovisionedpv-j2jj to disappear
Jun  4 00:24:01.032: INFO: Pod exec-volume-test-preprovisionedpv-j2jj no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-j2jj
Jun  4 00:24:01.032: INFO: Deleting pod "exec-volume-test-preprovisionedpv-j2jj" in namespace "volume-6229"
STEP: Deleting pv and pvc
Jun  4 00:24:01.134: INFO: Deleting PersistentVolumeClaim "pvc-gg6j7"
Jun  4 00:24:01.238: INFO: Deleting PersistentVolume "aws-8scnv"
Jun  4 00:24:01.566: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0dffc0595af39c797", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0dffc0595af39c797 is currently attached to i-0e8a7d1f42b2c7cf0
	status code: 400, request id: c19f9e94-12ca-4e03-a08c-c662ccdfdd17
Jun  4 00:24:07.177: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0dffc0595af39c797", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0dffc0595af39c797 is currently attached to i-0e8a7d1f42b2c7cf0
	status code: 400, request id: 3ff1fc5e-ab98-4cd3-8427-40f168fc7a8b
Jun  4 00:24:12.738: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0dffc0595af39c797", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0dffc0595af39c797 is currently attached to i-0e8a7d1f42b2c7cf0
	status code: 400, request id: 9bc71586-7c1f-485e-a497-224c4e0d1815
Jun  4 00:24:18.310: INFO: Successfully deleted PD "aws://eu-west-3a/vol-0dffc0595af39c797".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  4 00:24:18.311: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-6229" for this suite.
... skipping 54 lines ...
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  4 00:24:18.525: 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.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Jun  4 00:24:19.142: INFO: found topology map[topology.kubernetes.io/zone:eu-west-3a]
Jun  4 00:24:19.142: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  4 00:24:19.142: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.skFUj8hNl/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.skFUj8hNl/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (delayed binding)] topology
    /tmp/kops.skFUj8hNl/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.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 211 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  4 00:23:46.144: 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.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun  4 00:23:46.666: INFO: Creating resource for dynamic PV
Jun  4 00:23:46.666: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9244-e2e-sc89mng
STEP: creating a claim
Jun  4 00:23:46.771: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-86pm
STEP: Checking for subpath error in container status
Jun  4 00:24:09.296: INFO: Deleting pod "pod-subpath-test-dynamicpv-86pm" in namespace "provisioning-9244"
Jun  4 00:24:09.409: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-86pm" to be fully deleted
STEP: Deleting pod
Jun  4 00:24:19.616: INFO: Deleting pod "pod-subpath-test-dynamicpv-86pm" in namespace "provisioning-9244"
STEP: Deleting pvc
Jun  4 00:24:19.925: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comgk8sr"
... skipping 10 lines ...

• [SLOW TEST:44.511 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath directory is outside the volume [Slow][LinuxOnly]
    /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volume-lifecycle-performance
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volume-lifecycle-performance
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumeperf.go:111
... skipping 32 lines ...
Jun  4 00:24:00.861: INFO: Creating resource for dynamic PV
Jun  4 00:24:00.861: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-9330cnnxl
STEP: creating a claim
STEP: Expanding non-expandable pvc
Jun  4 00:24:01.186: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun  4 00:24:01.395: INFO: Error updating pvc awsdm8cx: PersistentVolumeClaim "awsdm8cx" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-9330cnnxl",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 97 lines ...
Jun  4 00:24:20.397: INFO: Waiting for pod aws-client to disappear
Jun  4 00:24:20.501: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun  4 00:24:20.501: INFO: Deleting PersistentVolumeClaim "pvc-6zhv4"
Jun  4 00:24:20.607: INFO: Deleting PersistentVolume "aws-pw89j"
Jun  4 00:24:21.239: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0d949ffa8dd18dbdf", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d949ffa8dd18dbdf is currently attached to i-0c3cb1d6976e8c6ae
	status code: 400, request id: 17931192-eef7-41af-8228-612e13da0761
Jun  4 00:24:26.838: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0d949ffa8dd18dbdf", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d949ffa8dd18dbdf is currently attached to i-0c3cb1d6976e8c6ae
	status code: 400, request id: 211bb2c6-cfb2-40f9-95e8-308f4d94270e
Jun  4 00:24:32.409: INFO: Successfully deleted PD "aws://eu-west-3a/vol-0d949ffa8dd18dbdf".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumes
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  4 00:24:32.409: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-9995" for this suite.
... skipping 94 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.skFUj8hNl/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.skFUj8hNl/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.skFUj8hNl/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.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Driver supports dynamic provisioning, skipping InlineVolume pattern

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

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

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

    /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 207 lines ...
Jun  4 00:24:17.142: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-1599xdvh8
STEP: creating a claim
Jun  4 00:24:17.246: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-kzm7
STEP: Creating a pod to test exec-volume-test
Jun  4 00:24:17.565: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-kzm7" in namespace "volume-1599" to be "Succeeded or Failed"
Jun  4 00:24:17.669: INFO: Pod "exec-volume-test-dynamicpv-kzm7": Phase="Pending", Reason="", readiness=false. Elapsed: 103.834331ms
Jun  4 00:24:19.773: INFO: Pod "exec-volume-test-dynamicpv-kzm7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.207557677s
Jun  4 00:24:21.880: INFO: Pod "exec-volume-test-dynamicpv-kzm7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.314130515s
Jun  4 00:24:23.984: INFO: Pod "exec-volume-test-dynamicpv-kzm7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.418310925s
Jun  4 00:24:26.089: INFO: Pod "exec-volume-test-dynamicpv-kzm7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.523490975s
Jun  4 00:24:28.193: INFO: Pod "exec-volume-test-dynamicpv-kzm7": Phase="Pending", Reason="", readiness=false. Elapsed: 10.627369173s
Jun  4 00:24:30.298: INFO: Pod "exec-volume-test-dynamicpv-kzm7": Phase="Pending", Reason="", readiness=false. Elapsed: 12.73205348s
Jun  4 00:24:32.402: INFO: Pod "exec-volume-test-dynamicpv-kzm7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.836098352s
STEP: Saw pod success
Jun  4 00:24:32.402: INFO: Pod "exec-volume-test-dynamicpv-kzm7" satisfied condition "Succeeded or Failed"
Jun  4 00:24:32.505: INFO: Trying to get logs from node ip-172-20-48-253.eu-west-3.compute.internal pod exec-volume-test-dynamicpv-kzm7 container exec-container-dynamicpv-kzm7: <nil>
STEP: delete the pod
Jun  4 00:24:32.741: INFO: Waiting for pod exec-volume-test-dynamicpv-kzm7 to disappear
Jun  4 00:24:32.844: INFO: Pod exec-volume-test-dynamicpv-kzm7 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-kzm7
Jun  4 00:24:32.844: INFO: Deleting pod "exec-volume-test-dynamicpv-kzm7" in namespace "volume-1599"
... skipping 254 lines ...
Jun  4 00:24:05.815: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5272d7jdj
STEP: creating a claim
Jun  4 00:24:05.921: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-4zn2
STEP: Creating a pod to test subpath
Jun  4 00:24:06.242: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-4zn2" in namespace "provisioning-5272" to be "Succeeded or Failed"
Jun  4 00:24:06.347: INFO: Pod "pod-subpath-test-dynamicpv-4zn2": Phase="Pending", Reason="", readiness=false. Elapsed: 105.238868ms
Jun  4 00:24:08.453: INFO: Pod "pod-subpath-test-dynamicpv-4zn2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.211460842s
Jun  4 00:24:10.560: INFO: Pod "pod-subpath-test-dynamicpv-4zn2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.317722382s
Jun  4 00:24:12.665: INFO: Pod "pod-subpath-test-dynamicpv-4zn2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.422852174s
Jun  4 00:24:14.769: INFO: Pod "pod-subpath-test-dynamicpv-4zn2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.527601206s
Jun  4 00:24:16.875: INFO: Pod "pod-subpath-test-dynamicpv-4zn2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.633156081s
Jun  4 00:24:18.983: INFO: Pod "pod-subpath-test-dynamicpv-4zn2": Phase="Pending", Reason="", readiness=false. Elapsed: 12.741659335s
Jun  4 00:24:21.089: INFO: Pod "pod-subpath-test-dynamicpv-4zn2": Phase="Pending", Reason="", readiness=false. Elapsed: 14.846732001s
Jun  4 00:24:23.200: INFO: Pod "pod-subpath-test-dynamicpv-4zn2": Phase="Pending", Reason="", readiness=false. Elapsed: 16.958309226s
Jun  4 00:24:25.306: INFO: Pod "pod-subpath-test-dynamicpv-4zn2": Phase="Pending", Reason="", readiness=false. Elapsed: 19.064146799s
Jun  4 00:24:27.411: INFO: Pod "pod-subpath-test-dynamicpv-4zn2": Phase="Pending", Reason="", readiness=false. Elapsed: 21.169172444s
Jun  4 00:24:29.517: INFO: Pod "pod-subpath-test-dynamicpv-4zn2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.275059864s
STEP: Saw pod success
Jun  4 00:24:29.517: INFO: Pod "pod-subpath-test-dynamicpv-4zn2" satisfied condition "Succeeded or Failed"
Jun  4 00:24:29.622: INFO: Trying to get logs from node ip-172-20-48-253.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-4zn2 container test-container-subpath-dynamicpv-4zn2: <nil>
STEP: delete the pod
Jun  4 00:24:29.845: INFO: Waiting for pod pod-subpath-test-dynamicpv-4zn2 to disappear
Jun  4 00:24:29.949: INFO: Pod pod-subpath-test-dynamicpv-4zn2 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-4zn2
Jun  4 00:24:29.949: INFO: Deleting pod "pod-subpath-test-dynamicpv-4zn2" in namespace "provisioning-5272"
... skipping 1279 lines ...
Jun  4 00:25:10.967: INFO: Waiting for pod aws-client to disappear
Jun  4 00:25:11.071: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun  4 00:25:11.071: INFO: Deleting PersistentVolumeClaim "pvc-4dgsw"
Jun  4 00:25:11.177: INFO: Deleting PersistentVolume "aws-pjqrg"
Jun  4 00:25:11.853: INFO: Couldn't delete PD "aws://eu-west-3a/vol-017986ec77534c3d9", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-017986ec77534c3d9 is currently attached to i-04ffa1804ffe9827d
	status code: 400, request id: e168691a-fe7f-4891-b838-5b17a0287f6c
Jun  4 00:25:17.408: INFO: Couldn't delete PD "aws://eu-west-3a/vol-017986ec77534c3d9", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-017986ec77534c3d9 is currently attached to i-04ffa1804ffe9827d
	status code: 400, request id: 8329f916-e883-4729-9d0d-944e4b8269ef
Jun  4 00:25:22.954: INFO: Successfully deleted PD "aws://eu-west-3a/vol-017986ec77534c3d9".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  4 00:25:22.954: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-3271" for this suite.
... skipping 35 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  4 00:24:27.885: 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.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun  4 00:24:28.407: INFO: Creating resource for dynamic PV
Jun  4 00:24:28.407: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-533-e2e-sczjk7k
STEP: creating a claim
Jun  4 00:24:28.531: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-lvkq
STEP: Checking for subpath error in container status
Jun  4 00:24:45.063: INFO: Deleting pod "pod-subpath-test-dynamicpv-lvkq" in namespace "provisioning-533"
Jun  4 00:24:45.169: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-lvkq" to be fully deleted
STEP: Deleting pod
Jun  4 00:24:55.377: INFO: Deleting pod "pod-subpath-test-dynamicpv-lvkq" in namespace "provisioning-533"
STEP: Deleting pvc
Jun  4 00:24:55.688: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comh8pvj"
... skipping 15 lines ...

• [SLOW TEST:64.066 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.skFUj8hNl/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.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 6 lines ...
Jun  4 00:25:15.373: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  4 00:25:16.093: INFO: Successfully created a new PD: "aws://eu-west-3a/vol-0b071ef7580f3983c".
Jun  4 00:25:16.093: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-lmbc
STEP: Creating a pod to test exec-volume-test
Jun  4 00:25:16.201: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-lmbc" in namespace "volume-8230" to be "Succeeded or Failed"
Jun  4 00:25:16.306: INFO: Pod "exec-volume-test-inlinevolume-lmbc": Phase="Pending", Reason="", readiness=false. Elapsed: 104.852886ms
Jun  4 00:25:18.411: INFO: Pod "exec-volume-test-inlinevolume-lmbc": Phase="Pending", Reason="", readiness=false. Elapsed: 2.210532687s
Jun  4 00:25:20.526: INFO: Pod "exec-volume-test-inlinevolume-lmbc": Phase="Pending", Reason="", readiness=false. Elapsed: 4.324763098s
Jun  4 00:25:22.630: INFO: Pod "exec-volume-test-inlinevolume-lmbc": Phase="Pending", Reason="", readiness=false. Elapsed: 6.429253504s
Jun  4 00:25:24.735: INFO: Pod "exec-volume-test-inlinevolume-lmbc": Phase="Pending", Reason="", readiness=false. Elapsed: 8.534364273s
Jun  4 00:25:26.841: INFO: Pod "exec-volume-test-inlinevolume-lmbc": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.639922557s
STEP: Saw pod success
Jun  4 00:25:26.841: INFO: Pod "exec-volume-test-inlinevolume-lmbc" satisfied condition "Succeeded or Failed"
Jun  4 00:25:26.945: INFO: Trying to get logs from node ip-172-20-35-212.eu-west-3.compute.internal pod exec-volume-test-inlinevolume-lmbc container exec-container-inlinevolume-lmbc: <nil>
STEP: delete the pod
Jun  4 00:25:27.163: INFO: Waiting for pod exec-volume-test-inlinevolume-lmbc to disappear
Jun  4 00:25:27.267: INFO: Pod exec-volume-test-inlinevolume-lmbc no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-lmbc
Jun  4 00:25:27.267: INFO: Deleting pod "exec-volume-test-inlinevolume-lmbc" in namespace "volume-8230"
Jun  4 00:25:27.560: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0b071ef7580f3983c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0b071ef7580f3983c is currently attached to i-0e8a7d1f42b2c7cf0
	status code: 400, request id: 43c193df-1efb-493e-a2d8-e778ae442f42
Jun  4 00:25:33.148: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0b071ef7580f3983c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0b071ef7580f3983c is currently attached to i-0e8a7d1f42b2c7cf0
	status code: 400, request id: 9e2a602c-dfb2-4a2f-9abb-137e9357fa47
Jun  4 00:25:38.725: INFO: Successfully deleted PD "aws://eu-west-3a/vol-0b071ef7580f3983c".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  4 00:25:38.725: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8230" for this suite.
... skipping 23 lines ...
Jun  4 00:24:41.129: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1896-e2e-scqdzx8
STEP: creating a claim
Jun  4 00:24:41.235: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-db9q
STEP: Creating a pod to test subpath
Jun  4 00:24:41.554: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-db9q" in namespace "provisioning-1896" to be "Succeeded or Failed"
Jun  4 00:24:41.659: INFO: Pod "pod-subpath-test-dynamicpv-db9q": Phase="Pending", Reason="", readiness=false. Elapsed: 104.152737ms
Jun  4 00:24:43.764: INFO: Pod "pod-subpath-test-dynamicpv-db9q": Phase="Pending", Reason="", readiness=false. Elapsed: 2.209487775s
Jun  4 00:24:45.870: INFO: Pod "pod-subpath-test-dynamicpv-db9q": Phase="Pending", Reason="", readiness=false. Elapsed: 4.315209199s
Jun  4 00:24:47.976: INFO: Pod "pod-subpath-test-dynamicpv-db9q": Phase="Pending", Reason="", readiness=false. Elapsed: 6.421029806s
Jun  4 00:24:50.080: INFO: Pod "pod-subpath-test-dynamicpv-db9q": Phase="Pending", Reason="", readiness=false. Elapsed: 8.525640009s
Jun  4 00:24:52.189: INFO: Pod "pod-subpath-test-dynamicpv-db9q": Phase="Pending", Reason="", readiness=false. Elapsed: 10.634335164s
Jun  4 00:24:54.294: INFO: Pod "pod-subpath-test-dynamicpv-db9q": Phase="Pending", Reason="", readiness=false. Elapsed: 12.739330726s
Jun  4 00:24:56.398: INFO: Pod "pod-subpath-test-dynamicpv-db9q": Phase="Pending", Reason="", readiness=false. Elapsed: 14.843811009s
Jun  4 00:24:58.504: INFO: Pod "pod-subpath-test-dynamicpv-db9q": Phase="Pending", Reason="", readiness=false. Elapsed: 16.949938638s
Jun  4 00:25:00.609: INFO: Pod "pod-subpath-test-dynamicpv-db9q": Phase="Pending", Reason="", readiness=false. Elapsed: 19.05428522s
Jun  4 00:25:02.714: INFO: Pod "pod-subpath-test-dynamicpv-db9q": Phase="Pending", Reason="", readiness=false. Elapsed: 21.159031874s
Jun  4 00:25:04.819: INFO: Pod "pod-subpath-test-dynamicpv-db9q": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.264061785s
STEP: Saw pod success
Jun  4 00:25:04.819: INFO: Pod "pod-subpath-test-dynamicpv-db9q" satisfied condition "Succeeded or Failed"
Jun  4 00:25:04.926: INFO: Trying to get logs from node ip-172-20-58-183.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-db9q container test-container-volume-dynamicpv-db9q: <nil>
STEP: delete the pod
Jun  4 00:25:05.170: INFO: Waiting for pod pod-subpath-test-dynamicpv-db9q to disappear
Jun  4 00:25:05.274: INFO: Pod pod-subpath-test-dynamicpv-db9q no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-db9q
Jun  4 00:25:05.274: INFO: Deleting pod "pod-subpath-test-dynamicpv-db9q" in namespace "provisioning-1896"
... skipping 40 lines ...
Jun  4 00:24:38.394: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-22757j27p
STEP: creating a claim
Jun  4 00:24:38.502: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-rsp8
STEP: Creating a pod to test subpath
Jun  4 00:24:38.828: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-rsp8" in namespace "provisioning-2275" to be "Succeeded or Failed"
Jun  4 00:24:38.933: INFO: Pod "pod-subpath-test-dynamicpv-rsp8": Phase="Pending", Reason="", readiness=false. Elapsed: 104.351249ms
Jun  4 00:24:41.038: INFO: Pod "pod-subpath-test-dynamicpv-rsp8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.209767485s
Jun  4 00:24:43.149: INFO: Pod "pod-subpath-test-dynamicpv-rsp8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.321018148s
Jun  4 00:24:45.254: INFO: Pod "pod-subpath-test-dynamicpv-rsp8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.425745962s
Jun  4 00:24:47.359: INFO: Pod "pod-subpath-test-dynamicpv-rsp8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.530991928s
Jun  4 00:24:49.464: INFO: Pod "pod-subpath-test-dynamicpv-rsp8": Phase="Pending", Reason="", readiness=false. Elapsed: 10.636264641s
... skipping 9 lines ...
Jun  4 00:25:10.514: INFO: Pod "pod-subpath-test-dynamicpv-rsp8": Phase="Pending", Reason="", readiness=false. Elapsed: 31.686300455s
Jun  4 00:25:12.620: INFO: Pod "pod-subpath-test-dynamicpv-rsp8": Phase="Pending", Reason="", readiness=false. Elapsed: 33.791464502s
Jun  4 00:25:14.725: INFO: Pod "pod-subpath-test-dynamicpv-rsp8": Phase="Pending", Reason="", readiness=false. Elapsed: 35.896749581s
Jun  4 00:25:16.829: INFO: Pod "pod-subpath-test-dynamicpv-rsp8": Phase="Pending", Reason="", readiness=false. Elapsed: 38.00123039s
Jun  4 00:25:18.935: INFO: Pod "pod-subpath-test-dynamicpv-rsp8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 40.10698222s
STEP: Saw pod success
Jun  4 00:25:18.935: INFO: Pod "pod-subpath-test-dynamicpv-rsp8" satisfied condition "Succeeded or Failed"
Jun  4 00:25:19.041: INFO: Trying to get logs from node ip-172-20-48-253.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-rsp8 container test-container-subpath-dynamicpv-rsp8: <nil>
STEP: delete the pod
Jun  4 00:25:19.266: INFO: Waiting for pod pod-subpath-test-dynamicpv-rsp8 to disappear
Jun  4 00:25:19.370: INFO: Pod pod-subpath-test-dynamicpv-rsp8 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-rsp8
Jun  4 00:25:19.370: INFO: Deleting pod "pod-subpath-test-dynamicpv-rsp8" in namespace "provisioning-2275"
... skipping 161 lines ...
Jun  4 00:25:21.875: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-2989-e2e-scqbck4
STEP: creating a claim
Jun  4 00:25:21.979: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-clxw
STEP: Creating a pod to test exec-volume-test
Jun  4 00:25:22.293: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-clxw" in namespace "volume-2989" to be "Succeeded or Failed"
Jun  4 00:25:22.396: INFO: Pod "exec-volume-test-dynamicpv-clxw": Phase="Pending", Reason="", readiness=false. Elapsed: 103.320908ms
Jun  4 00:25:24.501: INFO: Pod "exec-volume-test-dynamicpv-clxw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.207922726s
Jun  4 00:25:26.605: INFO: Pod "exec-volume-test-dynamicpv-clxw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.311684327s
Jun  4 00:25:28.709: INFO: Pod "exec-volume-test-dynamicpv-clxw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.416081595s
Jun  4 00:25:30.814: INFO: Pod "exec-volume-test-dynamicpv-clxw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.520589971s
Jun  4 00:25:32.920: INFO: Pod "exec-volume-test-dynamicpv-clxw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.626790287s
STEP: Saw pod success
Jun  4 00:25:32.920: INFO: Pod "exec-volume-test-dynamicpv-clxw" satisfied condition "Succeeded or Failed"
Jun  4 00:25:33.023: INFO: Trying to get logs from node ip-172-20-48-253.eu-west-3.compute.internal pod exec-volume-test-dynamicpv-clxw container exec-container-dynamicpv-clxw: <nil>
STEP: delete the pod
Jun  4 00:25:33.241: INFO: Waiting for pod exec-volume-test-dynamicpv-clxw to disappear
Jun  4 00:25:33.348: INFO: Pod exec-volume-test-dynamicpv-clxw no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-clxw
Jun  4 00:25:33.348: INFO: Deleting pod "exec-volume-test-dynamicpv-clxw" in namespace "volume-2989"
... skipping 89 lines ...
Jun  4 00:25:40.068: INFO: Waiting for pod aws-client to disappear
Jun  4 00:25:40.172: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun  4 00:25:40.172: INFO: Deleting PersistentVolumeClaim "pvc-qbvxf"
Jun  4 00:25:40.277: INFO: Deleting PersistentVolume "aws-cxq42"
Jun  4 00:25:40.948: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0f1210da6da9c66ca", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f1210da6da9c66ca is currently attached to i-0c3cb1d6976e8c6ae
	status code: 400, request id: 42fb8cb5-d04c-430d-a749-029cb81065a8
Jun  4 00:25:46.486: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0f1210da6da9c66ca", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f1210da6da9c66ca is currently attached to i-0c3cb1d6976e8c6ae
	status code: 400, request id: ef4efbb0-e4e5-4d2d-a69f-2b79af03d6b1
Jun  4 00:25:52.060: INFO: Successfully deleted PD "aws://eu-west-3a/vol-0f1210da6da9c66ca".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  4 00:25:52.060: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-5480" for this suite.
... skipping 71 lines ...
Jun  4 00:25:36.735: INFO: Pod aws-client still exists
Jun  4 00:25:38.632: INFO: Waiting for pod aws-client to disappear
Jun  4 00:25:38.734: INFO: Pod aws-client still exists
Jun  4 00:25:40.633: INFO: Waiting for pod aws-client to disappear
Jun  4 00:25:40.736: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun  4 00:25:41.301: INFO: Couldn't delete PD "aws://eu-west-3a/vol-05d388ab59dd302f9", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05d388ab59dd302f9 is currently attached to i-04ffa1804ffe9827d
	status code: 400, request id: e5792a19-2ca6-4958-8c6f-7be958a7c5b3
Jun  4 00:25:46.870: INFO: Couldn't delete PD "aws://eu-west-3a/vol-05d388ab59dd302f9", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05d388ab59dd302f9 is currently attached to i-04ffa1804ffe9827d
	status code: 400, request id: fb64e9c1-da4f-4080-86e8-416d1f9c9817
Jun  4 00:25:52.406: INFO: Successfully deleted PD "aws://eu-west-3a/vol-05d388ab59dd302f9".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  4 00:25:52.406: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-5531" for this suite.
... skipping 157 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  4 00:24:54.117: 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.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun  4 00:24:54.636: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  4 00:24:54.636: INFO: Creating resource for dynamic PV
Jun  4 00:24:54.636: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3034xdzwm
STEP: creating a claim
Jun  4 00:24:54.740: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-6vwz
STEP: Checking for subpath error in container status
Jun  4 00:25:35.262: INFO: Deleting pod "pod-subpath-test-dynamicpv-6vwz" in namespace "provisioning-3034"
Jun  4 00:25:35.368: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-6vwz" to be fully deleted
STEP: Deleting pod
Jun  4 00:25:47.580: INFO: Deleting pod "pod-subpath-test-dynamicpv-6vwz" in namespace "provisioning-3034"
STEP: Deleting pvc
Jun  4 00:25:47.890: INFO: Deleting PersistentVolumeClaim "awsfb4mf"
... skipping 12 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.skFUj8hNl/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.skFUj8hNl/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.skFUj8hNl/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.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (xfs)][Slow] volumes
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (xfs)][Slow] volumes
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 8 lines ...
Jun  4 00:25:15.617: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-6851jlxlm
STEP: creating a claim
Jun  4 00:25:15.722: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-24jr
STEP: Creating a pod to test exec-volume-test
Jun  4 00:25:16.037: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-24jr" in namespace "volume-6851" to be "Succeeded or Failed"
Jun  4 00:25:16.143: INFO: Pod "exec-volume-test-dynamicpv-24jr": Phase="Pending", Reason="", readiness=false. Elapsed: 106.186537ms
Jun  4 00:25:18.248: INFO: Pod "exec-volume-test-dynamicpv-24jr": Phase="Pending", Reason="", readiness=false. Elapsed: 2.211325163s
Jun  4 00:25:20.352: INFO: Pod "exec-volume-test-dynamicpv-24jr": Phase="Pending", Reason="", readiness=false. Elapsed: 4.315541146s
Jun  4 00:25:22.459: INFO: Pod "exec-volume-test-dynamicpv-24jr": Phase="Pending", Reason="", readiness=false. Elapsed: 6.422833793s
Jun  4 00:25:24.563: INFO: Pod "exec-volume-test-dynamicpv-24jr": Phase="Pending", Reason="", readiness=false. Elapsed: 8.526512807s
Jun  4 00:25:26.668: INFO: Pod "exec-volume-test-dynamicpv-24jr": Phase="Pending", Reason="", readiness=false. Elapsed: 10.631756429s
Jun  4 00:25:28.773: INFO: Pod "exec-volume-test-dynamicpv-24jr": Phase="Pending", Reason="", readiness=false. Elapsed: 12.736108156s
Jun  4 00:25:30.877: INFO: Pod "exec-volume-test-dynamicpv-24jr": Phase="Pending", Reason="", readiness=false. Elapsed: 14.840480281s
Jun  4 00:25:32.981: INFO: Pod "exec-volume-test-dynamicpv-24jr": Phase="Pending", Reason="", readiness=false. Elapsed: 16.944721124s
Jun  4 00:25:35.086: INFO: Pod "exec-volume-test-dynamicpv-24jr": Phase="Pending", Reason="", readiness=false. Elapsed: 19.049566989s
Jun  4 00:25:37.190: INFO: Pod "exec-volume-test-dynamicpv-24jr": Phase="Pending", Reason="", readiness=false. Elapsed: 21.153690875s
Jun  4 00:25:39.295: INFO: Pod "exec-volume-test-dynamicpv-24jr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.258227161s
STEP: Saw pod success
Jun  4 00:25:39.295: INFO: Pod "exec-volume-test-dynamicpv-24jr" satisfied condition "Succeeded or Failed"
Jun  4 00:25:39.398: INFO: Trying to get logs from node ip-172-20-48-253.eu-west-3.compute.internal pod exec-volume-test-dynamicpv-24jr container exec-container-dynamicpv-24jr: <nil>
STEP: delete the pod
Jun  4 00:25:39.613: INFO: Waiting for pod exec-volume-test-dynamicpv-24jr to disappear
Jun  4 00:25:39.717: INFO: Pod exec-volume-test-dynamicpv-24jr no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-24jr
Jun  4 00:25:39.717: INFO: Deleting pod "exec-volume-test-dynamicpv-24jr" in namespace "volume-6851"
... skipping 156 lines ...
Jun  4 00:25:54.999: INFO: Pod aws-client still exists
Jun  4 00:25:56.895: INFO: Waiting for pod aws-client to disappear
Jun  4 00:25:57.000: INFO: Pod aws-client still exists
Jun  4 00:25:58.894: INFO: Waiting for pod aws-client to disappear
Jun  4 00:25:58.999: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun  4 00:25:59.515: INFO: Couldn't delete PD "aws://eu-west-3a/vol-03ebde5c6a2ae3b31", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-03ebde5c6a2ae3b31 is currently attached to i-04ffa1804ffe9827d
	status code: 400, request id: 9f6015a9-7b83-43db-98fc-5f9495fe432c
Jun  4 00:26:05.066: INFO: Successfully deleted PD "aws://eu-west-3a/vol-03ebde5c6a2ae3b31".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  4 00:26:05.066: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-5388" for this suite.
... skipping 331 lines ...
Jun  4 00:24:32.878: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5228-e2e-sc9vfft
STEP: creating a claim
Jun  4 00:24:32.991: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-k7ns
STEP: Creating a pod to test subpath
Jun  4 00:24:33.314: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-k7ns" in namespace "provisioning-5228" to be "Succeeded or Failed"
Jun  4 00:24:33.418: INFO: Pod "pod-subpath-test-dynamicpv-k7ns": Phase="Pending", Reason="", readiness=false. Elapsed: 103.870537ms
Jun  4 00:24:35.522: INFO: Pod "pod-subpath-test-dynamicpv-k7ns": Phase="Pending", Reason="", readiness=false. Elapsed: 2.208164695s
Jun  4 00:24:37.645: INFO: Pod "pod-subpath-test-dynamicpv-k7ns": Phase="Pending", Reason="", readiness=false. Elapsed: 4.331231487s
Jun  4 00:24:39.750: INFO: Pod "pod-subpath-test-dynamicpv-k7ns": Phase="Pending", Reason="", readiness=false. Elapsed: 6.436678119s
Jun  4 00:24:41.856: INFO: Pod "pod-subpath-test-dynamicpv-k7ns": Phase="Pending", Reason="", readiness=false. Elapsed: 8.542320688s
Jun  4 00:24:43.960: INFO: Pod "pod-subpath-test-dynamicpv-k7ns": Phase="Pending", Reason="", readiness=false. Elapsed: 10.646619611s
... skipping 9 lines ...
Jun  4 00:25:05.008: INFO: Pod "pod-subpath-test-dynamicpv-k7ns": Phase="Pending", Reason="", readiness=false. Elapsed: 31.693882554s
Jun  4 00:25:07.113: INFO: Pod "pod-subpath-test-dynamicpv-k7ns": Phase="Pending", Reason="", readiness=false. Elapsed: 33.799183507s
Jun  4 00:25:09.218: INFO: Pod "pod-subpath-test-dynamicpv-k7ns": Phase="Pending", Reason="", readiness=false. Elapsed: 35.904024121s
Jun  4 00:25:11.322: INFO: Pod "pod-subpath-test-dynamicpv-k7ns": Phase="Pending", Reason="", readiness=false. Elapsed: 38.008574676s
Jun  4 00:25:13.428: INFO: Pod "pod-subpath-test-dynamicpv-k7ns": Phase="Succeeded", Reason="", readiness=false. Elapsed: 40.113887172s
STEP: Saw pod success
Jun  4 00:25:13.428: INFO: Pod "pod-subpath-test-dynamicpv-k7ns" satisfied condition "Succeeded or Failed"
Jun  4 00:25:13.533: INFO: Trying to get logs from node ip-172-20-35-212.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-k7ns container test-container-subpath-dynamicpv-k7ns: <nil>
STEP: delete the pod
Jun  4 00:25:13.763: INFO: Waiting for pod pod-subpath-test-dynamicpv-k7ns to disappear
Jun  4 00:25:13.867: INFO: Pod pod-subpath-test-dynamicpv-k7ns no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-k7ns
Jun  4 00:25:13.867: INFO: Deleting pod "pod-subpath-test-dynamicpv-k7ns" in namespace "provisioning-5228"
STEP: Creating pod pod-subpath-test-dynamicpv-k7ns
STEP: Creating a pod to test subpath
Jun  4 00:25:14.079: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-k7ns" in namespace "provisioning-5228" to be "Succeeded or Failed"
Jun  4 00:25:14.183: INFO: Pod "pod-subpath-test-dynamicpv-k7ns": Phase="Pending", Reason="", readiness=false. Elapsed: 103.923218ms
Jun  4 00:25:16.288: INFO: Pod "pod-subpath-test-dynamicpv-k7ns": Phase="Pending", Reason="", readiness=false. Elapsed: 2.209009648s
Jun  4 00:25:18.393: INFO: Pod "pod-subpath-test-dynamicpv-k7ns": Phase="Pending", Reason="", readiness=false. Elapsed: 4.314140964s
Jun  4 00:25:20.498: INFO: Pod "pod-subpath-test-dynamicpv-k7ns": Phase="Pending", Reason="", readiness=false. Elapsed: 6.419148262s
Jun  4 00:25:22.604: INFO: Pod "pod-subpath-test-dynamicpv-k7ns": Phase="Pending", Reason="", readiness=false. Elapsed: 8.525235616s
Jun  4 00:25:24.709: INFO: Pod "pod-subpath-test-dynamicpv-k7ns": Phase="Pending", Reason="", readiness=false. Elapsed: 10.630700176s
... skipping 7 lines ...
Jun  4 00:25:41.550: INFO: Pod "pod-subpath-test-dynamicpv-k7ns": Phase="Pending", Reason="", readiness=false. Elapsed: 27.47152188s
Jun  4 00:25:43.655: INFO: Pod "pod-subpath-test-dynamicpv-k7ns": Phase="Pending", Reason="", readiness=false. Elapsed: 29.575920518s
Jun  4 00:25:45.759: INFO: Pod "pod-subpath-test-dynamicpv-k7ns": Phase="Pending", Reason="", readiness=false. Elapsed: 31.680536628s
Jun  4 00:25:47.864: INFO: Pod "pod-subpath-test-dynamicpv-k7ns": Phase="Pending", Reason="", readiness=false. Elapsed: 33.785131261s
Jun  4 00:25:49.969: INFO: Pod "pod-subpath-test-dynamicpv-k7ns": Phase="Succeeded", Reason="", readiness=false. Elapsed: 35.889830946s
STEP: Saw pod success
Jun  4 00:25:49.969: INFO: Pod "pod-subpath-test-dynamicpv-k7ns" satisfied condition "Succeeded or Failed"
Jun  4 00:25:50.072: INFO: Trying to get logs from node ip-172-20-58-183.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-k7ns container test-container-subpath-dynamicpv-k7ns: <nil>
STEP: delete the pod
Jun  4 00:25:50.289: INFO: Waiting for pod pod-subpath-test-dynamicpv-k7ns to disappear
Jun  4 00:25:50.392: INFO: Pod pod-subpath-test-dynamicpv-k7ns no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-k7ns
Jun  4 00:25:50.393: INFO: Deleting pod "pod-subpath-test-dynamicpv-k7ns" in namespace "provisioning-5228"
... skipping 489 lines ...
Jun  4 00:25:00.411: INFO: Creating resource for dynamic PV
Jun  4 00:25:00.411: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-5688-e2e-sc4xdxc
STEP: creating a claim
Jun  4 00:25:00.517: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun  4 00:25:00.836: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-47trw" in namespace "snapshotting-5688" to be "Succeeded or Failed"
Jun  4 00:25:00.940: INFO: Pod "pvc-snapshottable-tester-47trw": Phase="Pending", Reason="", readiness=false. Elapsed: 103.439798ms
Jun  4 00:25:03.048: INFO: Pod "pvc-snapshottable-tester-47trw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.211567398s
Jun  4 00:25:05.165: INFO: Pod "pvc-snapshottable-tester-47trw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.328708715s
Jun  4 00:25:07.272: INFO: Pod "pvc-snapshottable-tester-47trw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.435646613s
Jun  4 00:25:09.381: INFO: Pod "pvc-snapshottable-tester-47trw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.544360383s
Jun  4 00:25:11.486: INFO: Pod "pvc-snapshottable-tester-47trw": Phase="Pending", Reason="", readiness=false. Elapsed: 10.649101238s
Jun  4 00:25:13.590: INFO: Pod "pvc-snapshottable-tester-47trw": Phase="Pending", Reason="", readiness=false. Elapsed: 12.753528409s
Jun  4 00:25:15.695: INFO: Pod "pvc-snapshottable-tester-47trw": Phase="Pending", Reason="", readiness=false. Elapsed: 14.858379822s
Jun  4 00:25:17.800: INFO: Pod "pvc-snapshottable-tester-47trw": Phase="Pending", Reason="", readiness=false. Elapsed: 16.963050988s
Jun  4 00:25:19.905: INFO: Pod "pvc-snapshottable-tester-47trw": Phase="Pending", Reason="", readiness=false. Elapsed: 19.068623124s
Jun  4 00:25:22.010: INFO: Pod "pvc-snapshottable-tester-47trw": Phase="Pending", Reason="", readiness=false. Elapsed: 21.173316346s
Jun  4 00:25:24.114: INFO: Pod "pvc-snapshottable-tester-47trw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.277192262s
STEP: Saw pod success
Jun  4 00:25:24.114: INFO: Pod "pvc-snapshottable-tester-47trw" satisfied condition "Succeeded or Failed"
Jun  4 00:25:24.334: INFO: Pod pvc-snapshottable-tester-47trw has the following logs: 
Jun  4 00:25:24.334: INFO: Deleting pod "pvc-snapshottable-tester-47trw" in namespace "snapshotting-5688"
Jun  4 00:25:24.453: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-47trw" to be fully deleted
Jun  4 00:25:24.557: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comhqh4r] to have phase Bound
Jun  4 00:25:24.660: INFO: PersistentVolumeClaim ebs.csi.aws.comhqh4r found and phase=Bound (103.492834ms)
STEP: [init] checking the claim
... skipping 18 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.skFUj8hNl/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  4 00:25:42.670: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-qbqf4" in namespace "snapshotting-5688" to be "Succeeded or Failed"
Jun  4 00:25:42.776: INFO: Pod "pvc-snapshottable-data-tester-qbqf4": Phase="Pending", Reason="", readiness=false. Elapsed: 105.584386ms
Jun  4 00:25:44.880: INFO: Pod "pvc-snapshottable-data-tester-qbqf4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.209449926s
Jun  4 00:25:46.994: INFO: Pod "pvc-snapshottable-data-tester-qbqf4": Phase="Pending", Reason="", readiness=false. Elapsed: 4.323573793s
Jun  4 00:25:49.100: INFO: Pod "pvc-snapshottable-data-tester-qbqf4": Phase="Pending", Reason="", readiness=false. Elapsed: 6.43039899s
Jun  4 00:25:51.206: INFO: Pod "pvc-snapshottable-data-tester-qbqf4": Phase="Pending", Reason="", readiness=false. Elapsed: 8.536068163s
Jun  4 00:25:53.311: INFO: Pod "pvc-snapshottable-data-tester-qbqf4": Phase="Pending", Reason="", readiness=false. Elapsed: 10.640647142s
... skipping 6 lines ...
Jun  4 00:26:08.044: INFO: Pod "pvc-snapshottable-data-tester-qbqf4": Phase="Pending", Reason="", readiness=false. Elapsed: 25.374025246s
Jun  4 00:26:10.148: INFO: Pod "pvc-snapshottable-data-tester-qbqf4": Phase="Pending", Reason="", readiness=false. Elapsed: 27.47837082s
Jun  4 00:26:12.253: INFO: Pod "pvc-snapshottable-data-tester-qbqf4": Phase="Pending", Reason="", readiness=false. Elapsed: 29.582608182s
Jun  4 00:26:14.358: INFO: Pod "pvc-snapshottable-data-tester-qbqf4": Phase="Pending", Reason="", readiness=false. Elapsed: 31.68755773s
Jun  4 00:26:16.462: INFO: Pod "pvc-snapshottable-data-tester-qbqf4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 33.79210122s
STEP: Saw pod success
Jun  4 00:26:16.462: INFO: Pod "pvc-snapshottable-data-tester-qbqf4" satisfied condition "Succeeded or Failed"
Jun  4 00:26:16.675: INFO: Pod pvc-snapshottable-data-tester-qbqf4 has the following logs: 
Jun  4 00:26:16.675: INFO: Deleting pod "pvc-snapshottable-data-tester-qbqf4" in namespace "snapshotting-5688"
Jun  4 00:26:16.785: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-qbqf4" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun  4 00:26:39.324: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-5688 exec restored-pvc-tester-77qgd --namespace=snapshotting-5688 -- cat /mnt/test/data'
... skipping 31 lines ...
Jun  4 00:27:05.190: INFO: volumesnapshotcontents snapcontent-20d21469-f593-42b0-acf9-c3f19b44f595 has been found and is not deleted
Jun  4 00:27:06.295: INFO: volumesnapshotcontents snapcontent-20d21469-f593-42b0-acf9-c3f19b44f595 has been found and is not deleted
Jun  4 00:27:07.401: INFO: volumesnapshotcontents snapcontent-20d21469-f593-42b0-acf9-c3f19b44f595 has been found and is not deleted
Jun  4 00:27:08.507: INFO: volumesnapshotcontents snapcontent-20d21469-f593-42b0-acf9-c3f19b44f595 has been found and is not deleted
Jun  4 00:27:09.613: INFO: volumesnapshotcontents snapcontent-20d21469-f593-42b0-acf9-c3f19b44f595 has been found and is not deleted
Jun  4 00:27:10.718: INFO: volumesnapshotcontents snapcontent-20d21469-f593-42b0-acf9-c3f19b44f595 has been found and is not deleted
Jun  4 00:27:11.718: INFO: WaitUntil failed after reaching the timeout 30s
[AfterEach] volume snapshot controller
  /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:221
Jun  4 00:27:11.830: INFO: Pod restored-pvc-tester-77qgd has the following logs: 
Jun  4 00:27:11.830: INFO: Deleting pod "restored-pvc-tester-77qgd" in namespace "snapshotting-5688"
Jun  4 00:27:11.943: INFO: Wait up to 5m0s for pod "restored-pvc-tester-77qgd" to be fully deleted
Jun  4 00:27:50.151: INFO: deleting claim "snapshotting-5688"/"pvc-hqtqb"
... skipping 32 lines ...
        /tmp/kops.skFUj8hNl/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:243
------------------------------


Summarizing 1 Failure:

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

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


Ginkgo ran 1 suite in 11m49.69396152s
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
I0604 00:27:58.993063   26812 app.go:59] RunDir for this run: "/logs/artifacts/e58316c4-c4c7-11eb-b207-42879ebc49dd"
I0604 00:27:58.993337   26812 app.go:90] ID for this run: "e58316c4-c4c7-11eb-b207-42879ebc49dd"
I0604 00:27:58.993372   26812 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
I0604 00:27:59.021582   26818 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
... skipping 1487 lines ...