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

No Test Failures!


Error lines from build-log.txt

... skipping 493 lines ...
I0608 08:08:12.628267   11757 up.go:43] Cleaning up any leaked resources from previous cluster
I0608 08:08:12.628299   11757 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
I0608 08:08:12.643755   11763 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0608 08:08:12.643850   11763 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io" not found
W0608 08:08:13.193290   11757 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0608 08:08:13.193337   11757 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
I0608 08:08:13.210935   11774 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0608 08:08:13.211589   11774 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io" not found
I0608 08:08:13.767284   11757 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/06/08 08:08:13 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
I0608 08:08:13.779164   11757 http.go:37] curl https://ip.jsb.workers.dev
I0608 08:08:13.974507   11757 up.go:144] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops create cluster --name e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --cloud aws --kubernetes-version 1.21.0 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --networking calico --override=cluster.spec.cloudConfig.awsEBSCSIDriver.enabled=true --override=cluster.spec.snapshotController.enabled=true --override=cluster.spec.certManager.enabled=true --admin-access 35.184.235.34/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones us-east-1a --master-size c5.large
I0608 08:08:13.990895   11790 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0608 08:08:13.991654   11790 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I0608 08:08:14.040887   11790 create_cluster.go:728] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0608 08:08:14.639206   11790 new_cluster.go:1051]  Cloud Provider ID = aws
... skipping 40 lines ...

I0608 08:08:40.856194   11757 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
I0608 08:08:40.871170   11811 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0608 08:08:40.871380   11811 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io

W0608 08:08:42.173266   11811 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-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

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
W0608 08:08:52.232666   11811 validate_cluster.go:221] (will retry): cluster not yet healthy
W0608 08:09:02.296028   11811 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-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

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
W0608 08:09:12.338607   11811 validate_cluster.go:221] (will retry): cluster not yet healthy
W0608 08:09:22.375470   11811 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-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

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
W0608 08:09:32.420319   11811 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

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
W0608 08:09:42.465788   11811 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

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
W0608 08:09:52.512470   11811 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

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
W0608 08:10:02.566317   11811 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

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
W0608 08:10:12.624553   11811 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

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
W0608 08:10:22.660855   11811 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

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
W0608 08:10:32.723250   11811 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

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
W0608 08:10:42.766950   11811 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

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
W0608 08:10:52.825896   11811 validate_cluster.go:221] (will retry): cluster not yet healthy
W0608 08:11:02.848007   11811 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-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

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
W0608 08:11:12.904527   11811 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

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
W0608 08:11:22.951125   11811 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

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
W0608 08:11:32.991019   11811 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

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
W0608 08:11:43.035658   11811 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

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
W0608 08:11:53.080812   11811 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

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
W0608 08:12:03.137294   11811 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

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
W0608 08:12:13.197781   11811 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

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
W0608 08:12:23.258184   11811 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

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
W0608 08:12:33.317765   11811 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

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
W0608 08:12:43.355316   11811 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

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
W0608 08:12:53.391412   11811 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

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
W0608 08:13:03.446604   11811 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

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
W0608 08:13:13.491178   11811 validate_cluster.go:221] (will retry): cluster not yet healthy
W0608 08:13:23.537300   11811 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-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

NODE STATUS
... skipping 10 lines ...
Pod	kube-system/cert-manager-cainjector-74d69756d5-zzgz9			system-cluster-critical pod "cert-manager-cainjector-74d69756d5-zzgz9" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-fvgzz			system-cluster-critical pod "cert-manager-webhook-7bbf67968-fvgzz" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-26fbm				system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-26fbm" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-r5lbj				system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-r5lbj" is pending
Pod	kube-system/kube-controller-manager-ip-172-20-59-252.ec2.internal	system-cluster-critical pod "kube-controller-manager-ip-172-20-59-252.ec2.internal" is pending

Validation Failed
W0608 08:13:35.399177   11811 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 11 lines ...
Pod	kube-system/cert-manager-webhook-7bbf67968-fvgzz		system-cluster-critical pod "cert-manager-webhook-7bbf67968-fvgzz" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-b2pzk			system-cluster-critical pod "coredns-autoscaler-6f594f4c58-b2pzk" is pending
Pod	kube-system/coredns-f45c4bf76-r9ntb				system-cluster-critical pod "coredns-f45c4bf76-r9ntb" is pending
Pod	kube-system/etcd-manager-main-ip-172-20-59-252.ec2.internal	system-cluster-critical pod "etcd-manager-main-ip-172-20-59-252.ec2.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-59-252.ec2.internal		system-node-critical pod "kube-proxy-ip-172-20-59-252.ec2.internal" is pending

Validation Failed
W0608 08:13:46.562726   11811 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-08504c879d133e5a6					machine "i-08504c879d133e5a6" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-zzgz9	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-zzgz9" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-fvgzz	system-cluster-critical pod "cert-manager-webhook-7bbf67968-fvgzz" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-b2pzk		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-b2pzk" is pending
Pod	kube-system/coredns-f45c4bf76-r9ntb			system-cluster-critical pod "coredns-f45c4bf76-r9ntb" is pending

Validation Failed
W0608 08:13:58.832478   11811 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 17 lines ...
Pod	kube-system/coredns-autoscaler-6f594f4c58-b2pzk		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-b2pzk" is pending
Pod	kube-system/coredns-f45c4bf76-r9ntb			system-cluster-critical pod "coredns-f45c4bf76-r9ntb" is pending
Pod	kube-system/ebs-csi-node-2md82				system-node-critical pod "ebs-csi-node-2md82" is pending
Pod	kube-system/ebs-csi-node-mzpqh				system-node-critical pod "ebs-csi-node-mzpqh" is pending
Pod	kube-system/ebs-csi-node-ncxdq				system-node-critical pod "ebs-csi-node-ncxdq" is pending

Validation Failed
W0608 08:14:10.160680   11811 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 17 lines ...
Pod	kube-system/cert-manager-webhook-7bbf67968-fvgzz	system-cluster-critical pod "cert-manager-webhook-7bbf67968-fvgzz" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-b2pzk		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-b2pzk" is pending
Pod	kube-system/coredns-f45c4bf76-r9ntb			system-cluster-critical pod "coredns-f45c4bf76-r9ntb" is pending
Pod	kube-system/ebs-csi-node-7bmgt				system-node-critical pod "ebs-csi-node-7bmgt" is pending
Pod	kube-system/ebs-csi-node-ncxdq				system-node-critical pod "ebs-csi-node-ncxdq" is pending

Validation Failed
W0608 08:14:21.332977   11811 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 10 lines ...
Pod	kube-system/calico-node-57qpd		system-node-critical pod "calico-node-57qpd" is not ready (calico-node)
Pod	kube-system/calico-node-k44rz		system-node-critical pod "calico-node-k44rz" is not ready (calico-node)
Pod	kube-system/calico-node-nblgv		system-node-critical pod "calico-node-nblgv" is not ready (calico-node)
Pod	kube-system/calico-node-xmtp2		system-node-critical pod "calico-node-xmtp2" is not ready (calico-node)
Pod	kube-system/coredns-f45c4bf76-c8h8l	system-cluster-critical pod "coredns-f45c4bf76-c8h8l" is pending

Validation Failed
W0608 08:14:32.578294   11811 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 208 lines ...

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

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

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

      Not enough topologies in cluster -- skipping

      /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 343 lines ...
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  8 08:17:54.233: 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.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Jun  8 08:17:56.991: INFO: found topology map[topology.kubernetes.io/zone:us-east-1a]
Jun  8 08:17:56.991: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  8 08:17:56.991: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.YIoOihHZk/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.YIoOihHZk/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (immediate binding)] topology
    /tmp/kops.YIoOihHZk/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.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 191 lines ...
STEP: Deleting pod hostexec-ip-172-20-47-76.ec2.internal-xffz4 in namespace volumemode-8851
Jun  8 08:18:14.438: INFO: Deleting pod "pod-7a4e7cf5-2b45-4084-bf00-5b917a88c225" in namespace "volumemode-8851"
Jun  8 08:18:14.488: INFO: Wait up to 5m0s for pod "pod-7a4e7cf5-2b45-4084-bf00-5b917a88c225" to be fully deleted
STEP: Deleting pv and pvc
Jun  8 08:18:20.576: INFO: Deleting PersistentVolumeClaim "pvc-25nrv"
Jun  8 08:18:20.620: INFO: Deleting PersistentVolume "aws-pgnpc"
Jun  8 08:18:21.130: INFO: Couldn't delete PD "aws://us-east-1a/vol-083abc51fff12d593", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-083abc51fff12d593 is currently attached to i-05e5a3b84c6a72dab
	status code: 400, request id: 929cb20e-d586-46e4-a34f-2e545ac0267b
Jun  8 08:18:26.509: INFO: Successfully deleted PD "aws://us-east-1a/vol-083abc51fff12d593".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  8 08:18:26.509: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-8851" for this suite.
... skipping 25 lines ...
Jun  8 08:17:56.141: INFO: Creating resource for dynamic PV
Jun  8 08:17:56.141: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-2504s6jh2
STEP: creating a claim
STEP: Expanding non-expandable pvc
Jun  8 08:17:56.269: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun  8 08:17:56.367: INFO: Error updating pvc awsbbmsz: PersistentVolumeClaim "awsbbmsz" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2504s6jh2",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun  8 08:18:26.542: INFO: Error updating pvc awsbbmsz: PersistentVolumeClaim "awsbbmsz" is invalid: spec: Forbidden: spec is 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 ...
STEP: Creating a kubernetes client
Jun  8 08:17:53.378: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename provisioning
W0608 08:17:53.701266   25729 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Jun  8 08:17:53.701: 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.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun  8 08:17:53.794: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  8 08:17:53.794: INFO: Creating resource for dynamic PV
Jun  8 08:17:53.794: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-34565bjr4
STEP: creating a claim
Jun  8 08:17:53.849: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-jjnd
STEP: Checking for subpath error in container status
Jun  8 08:18:24.107: INFO: Deleting pod "pod-subpath-test-dynamicpv-jjnd" in namespace "provisioning-3456"
Jun  8 08:18:24.151: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-jjnd" to be fully deleted
STEP: Deleting pod
Jun  8 08:18:34.235: INFO: Deleting pod "pod-subpath-test-dynamicpv-jjnd" in namespace "provisioning-3456"
STEP: Deleting pvc
Jun  8 08:18:34.362: INFO: Deleting PersistentVolumeClaim "aws6jlps"
... skipping 12 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.YIoOihHZk/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.YIoOihHZk/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.YIoOihHZk/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.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow]
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  8 08:18:44.713: INFO: Driver supports dynamic provisioning, skipping PreprovisionedPV pattern
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow]
... skipping 29 lines ...
Jun  8 08:17:54.791: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  8 08:17:55.374: INFO: Successfully created a new PD: "aws://us-east-1a/vol-08850b00a19d12b2f".
Jun  8 08:17:55.374: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-l7w5
STEP: Creating a pod to test exec-volume-test
Jun  8 08:17:55.424: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-l7w5" in namespace "volume-8397" to be "Succeeded or Failed"
Jun  8 08:17:55.468: INFO: Pod "exec-volume-test-inlinevolume-l7w5": Phase="Pending", Reason="", readiness=false. Elapsed: 44.343215ms
Jun  8 08:17:57.510: INFO: Pod "exec-volume-test-inlinevolume-l7w5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.086658574s
Jun  8 08:17:59.558: INFO: Pod "exec-volume-test-inlinevolume-l7w5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.13423813s
Jun  8 08:18:01.601: INFO: Pod "exec-volume-test-inlinevolume-l7w5": Phase="Pending", Reason="", readiness=false. Elapsed: 6.177240325s
Jun  8 08:18:03.644: INFO: Pod "exec-volume-test-inlinevolume-l7w5": Phase="Pending", Reason="", readiness=false. Elapsed: 8.220355816s
Jun  8 08:18:05.688: INFO: Pod "exec-volume-test-inlinevolume-l7w5": Phase="Pending", Reason="", readiness=false. Elapsed: 10.264070832s
Jun  8 08:18:07.731: INFO: Pod "exec-volume-test-inlinevolume-l7w5": Phase="Pending", Reason="", readiness=false. Elapsed: 12.307253384s
Jun  8 08:18:09.773: INFO: Pod "exec-volume-test-inlinevolume-l7w5": Phase="Pending", Reason="", readiness=false. Elapsed: 14.349706444s
Jun  8 08:18:11.816: INFO: Pod "exec-volume-test-inlinevolume-l7w5": Phase="Pending", Reason="", readiness=false. Elapsed: 16.392399362s
Jun  8 08:18:13.859: INFO: Pod "exec-volume-test-inlinevolume-l7w5": Phase="Pending", Reason="", readiness=false. Elapsed: 18.435327976s
Jun  8 08:18:15.902: INFO: Pod "exec-volume-test-inlinevolume-l7w5": Phase="Pending", Reason="", readiness=false. Elapsed: 20.478385341s
Jun  8 08:18:17.945: INFO: Pod "exec-volume-test-inlinevolume-l7w5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.521358717s
STEP: Saw pod success
Jun  8 08:18:17.945: INFO: Pod "exec-volume-test-inlinevolume-l7w5" satisfied condition "Succeeded or Failed"
Jun  8 08:18:17.987: INFO: Trying to get logs from node ip-172-20-39-149.ec2.internal pod exec-volume-test-inlinevolume-l7w5 container exec-container-inlinevolume-l7w5: <nil>
STEP: delete the pod
Jun  8 08:18:18.688: INFO: Waiting for pod exec-volume-test-inlinevolume-l7w5 to disappear
Jun  8 08:18:18.730: INFO: Pod exec-volume-test-inlinevolume-l7w5 no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-l7w5
Jun  8 08:18:18.730: INFO: Deleting pod "exec-volume-test-inlinevolume-l7w5" in namespace "volume-8397"
Jun  8 08:18:19.046: INFO: Couldn't delete PD "aws://us-east-1a/vol-08850b00a19d12b2f", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08850b00a19d12b2f is currently attached to i-009378eb908db4e9b
	status code: 400, request id: 8de46f46-bd1c-46d1-b2c3-9cb8c5c91863
Jun  8 08:18:24.442: INFO: Couldn't delete PD "aws://us-east-1a/vol-08850b00a19d12b2f", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08850b00a19d12b2f is currently attached to i-009378eb908db4e9b
	status code: 400, request id: 77750fb6-b7df-4fec-83c7-7e1652ff3e20
Jun  8 08:18:29.805: INFO: Couldn't delete PD "aws://us-east-1a/vol-08850b00a19d12b2f", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08850b00a19d12b2f is currently attached to i-009378eb908db4e9b
	status code: 400, request id: 93f07724-cf21-4cc5-b2a0-923d50d23134
Jun  8 08:18:35.337: INFO: Couldn't delete PD "aws://us-east-1a/vol-08850b00a19d12b2f", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08850b00a19d12b2f is currently attached to i-009378eb908db4e9b
	status code: 400, request id: 58d05199-adf3-41bb-8a62-bc1ca4f22508
Jun  8 08:18:40.786: INFO: Couldn't delete PD "aws://us-east-1a/vol-08850b00a19d12b2f", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08850b00a19d12b2f is currently attached to i-009378eb908db4e9b
	status code: 400, request id: b9178e12-9882-469e-ad90-01fe87659f45
Jun  8 08:18:46.314: INFO: Successfully deleted PD "aws://us-east-1a/vol-08850b00a19d12b2f".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  8 08:18:46.315: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8397" for this suite.
... skipping 70 lines ...
Jun  8 08:18:01.924: INFO: PersistentVolumeClaim pvc-c6k9q found but phase is Pending instead of Bound.
Jun  8 08:18:03.967: INFO: PersistentVolumeClaim pvc-c6k9q found and phase=Bound (6.175355469s)
Jun  8 08:18:03.967: INFO: Waiting up to 3m0s for PersistentVolume aws-7hjfz to have phase Bound
Jun  8 08:18:04.010: INFO: PersistentVolume aws-7hjfz found and phase=Bound (42.504335ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-wj6z
STEP: Creating a pod to test exec-volume-test
Jun  8 08:18:04.143: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-wj6z" in namespace "volume-9401" to be "Succeeded or Failed"
Jun  8 08:18:04.186: INFO: Pod "exec-volume-test-preprovisionedpv-wj6z": Phase="Pending", Reason="", readiness=false. Elapsed: 42.83974ms
Jun  8 08:18:06.228: INFO: Pod "exec-volume-test-preprovisionedpv-wj6z": Phase="Pending", Reason="", readiness=false. Elapsed: 2.085259171s
Jun  8 08:18:08.272: INFO: Pod "exec-volume-test-preprovisionedpv-wj6z": Phase="Pending", Reason="", readiness=false. Elapsed: 4.128802079s
Jun  8 08:18:10.314: INFO: Pod "exec-volume-test-preprovisionedpv-wj6z": Phase="Pending", Reason="", readiness=false. Elapsed: 6.170920656s
Jun  8 08:18:12.356: INFO: Pod "exec-volume-test-preprovisionedpv-wj6z": Phase="Pending", Reason="", readiness=false. Elapsed: 8.213481175s
Jun  8 08:18:14.407: INFO: Pod "exec-volume-test-preprovisionedpv-wj6z": Phase="Pending", Reason="", readiness=false. Elapsed: 10.264311592s
Jun  8 08:18:16.450: INFO: Pod "exec-volume-test-preprovisionedpv-wj6z": Phase="Pending", Reason="", readiness=false. Elapsed: 12.307119207s
Jun  8 08:18:18.492: INFO: Pod "exec-volume-test-preprovisionedpv-wj6z": Phase="Pending", Reason="", readiness=false. Elapsed: 14.349422776s
Jun  8 08:18:20.537: INFO: Pod "exec-volume-test-preprovisionedpv-wj6z": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.394457663s
STEP: Saw pod success
Jun  8 08:18:20.537: INFO: Pod "exec-volume-test-preprovisionedpv-wj6z" satisfied condition "Succeeded or Failed"
Jun  8 08:18:20.579: INFO: Trying to get logs from node ip-172-20-58-151.ec2.internal pod exec-volume-test-preprovisionedpv-wj6z container exec-container-preprovisionedpv-wj6z: <nil>
STEP: delete the pod
Jun  8 08:18:21.354: INFO: Waiting for pod exec-volume-test-preprovisionedpv-wj6z to disappear
Jun  8 08:18:21.399: INFO: Pod exec-volume-test-preprovisionedpv-wj6z no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-wj6z
Jun  8 08:18:21.399: INFO: Deleting pod "exec-volume-test-preprovisionedpv-wj6z" in namespace "volume-9401"
STEP: Deleting pv and pvc
Jun  8 08:18:21.441: INFO: Deleting PersistentVolumeClaim "pvc-c6k9q"
Jun  8 08:18:21.487: INFO: Deleting PersistentVolume "aws-7hjfz"
Jun  8 08:18:21.734: INFO: Couldn't delete PD "aws://us-east-1a/vol-02c6905c0137810e4", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02c6905c0137810e4 is currently attached to i-07b0c6559cfd9ece1
	status code: 400, request id: f5af6282-e8bd-43fd-a387-512f9163dd86
Jun  8 08:18:27.125: INFO: Couldn't delete PD "aws://us-east-1a/vol-02c6905c0137810e4", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02c6905c0137810e4 is currently attached to i-07b0c6559cfd9ece1
	status code: 400, request id: 43272ae5-971d-4c54-8089-334ecca5c354
Jun  8 08:18:32.556: INFO: Couldn't delete PD "aws://us-east-1a/vol-02c6905c0137810e4", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02c6905c0137810e4 is currently attached to i-07b0c6559cfd9ece1
	status code: 400, request id: 48e7b3d8-f062-4688-bd97-522a3087d3bc
Jun  8 08:18:37.984: INFO: Couldn't delete PD "aws://us-east-1a/vol-02c6905c0137810e4", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02c6905c0137810e4 is currently attached to i-07b0c6559cfd9ece1
	status code: 400, request id: b73e606d-85b1-4016-8f2b-49e5553b0944
Jun  8 08:18:43.532: INFO: Couldn't delete PD "aws://us-east-1a/vol-02c6905c0137810e4", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02c6905c0137810e4 is currently attached to i-07b0c6559cfd9ece1
	status code: 400, request id: 09b0e1e7-71a6-4866-a3a5-1ef918235f47
Jun  8 08:18:48.998: INFO: Successfully deleted PD "aws://us-east-1a/vol-02c6905c0137810e4".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  8 08:18:48.998: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-9401" for this suite.
... skipping 278 lines ...
STEP: Creating a kubernetes client
Jun  8 08:17:53.258: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename provisioning
W0608 08:17:53.585785   25730 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Jun  8 08:17:53.585: 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.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun  8 08:17:53.669: INFO: Creating resource for dynamic PV
Jun  8 08:17:53.670: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3664-e2e-scfbbql
STEP: creating a claim
Jun  8 08:17:53.716: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-qfns
STEP: Checking for subpath error in container status
Jun  8 08:18:17.978: INFO: Deleting pod "pod-subpath-test-dynamicpv-qfns" in namespace "provisioning-3664"
Jun  8 08:18:18.021: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-qfns" to be fully deleted
STEP: Deleting pod
Jun  8 08:18:24.106: INFO: Deleting pod "pod-subpath-test-dynamicpv-qfns" in namespace "provisioning-3664"
STEP: Deleting pvc
Jun  8 08:18:24.232: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comml8mq"
... skipping 15 lines ...

• [SLOW TEST:66.532 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.YIoOihHZk/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.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 8 lines ...
Jun  8 08:17:57.901: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-12277pz6h
STEP: creating a claim
Jun  8 08:17:57.945: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-xlmn
STEP: Creating a pod to test subpath
Jun  8 08:17:58.079: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-xlmn" in namespace "provisioning-1227" to be "Succeeded or Failed"
Jun  8 08:17:58.122: INFO: Pod "pod-subpath-test-dynamicpv-xlmn": Phase="Pending", Reason="", readiness=false. Elapsed: 42.922562ms
Jun  8 08:18:00.166: INFO: Pod "pod-subpath-test-dynamicpv-xlmn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.086664396s
Jun  8 08:18:02.211: INFO: Pod "pod-subpath-test-dynamicpv-xlmn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.131782987s
Jun  8 08:18:04.256: INFO: Pod "pod-subpath-test-dynamicpv-xlmn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.176179477s
Jun  8 08:18:06.300: INFO: Pod "pod-subpath-test-dynamicpv-xlmn": Phase="Pending", Reason="", readiness=false. Elapsed: 8.220116018s
Jun  8 08:18:08.344: INFO: Pod "pod-subpath-test-dynamicpv-xlmn": Phase="Pending", Reason="", readiness=false. Elapsed: 10.264685023s
... skipping 3 lines ...
Jun  8 08:18:16.523: INFO: Pod "pod-subpath-test-dynamicpv-xlmn": Phase="Pending", Reason="", readiness=false. Elapsed: 18.443166046s
Jun  8 08:18:18.567: INFO: Pod "pod-subpath-test-dynamicpv-xlmn": Phase="Pending", Reason="", readiness=false. Elapsed: 20.487279049s
Jun  8 08:18:20.611: INFO: Pod "pod-subpath-test-dynamicpv-xlmn": Phase="Pending", Reason="", readiness=false. Elapsed: 22.531411173s
Jun  8 08:18:22.655: INFO: Pod "pod-subpath-test-dynamicpv-xlmn": Phase="Pending", Reason="", readiness=false. Elapsed: 24.575359799s
Jun  8 08:18:24.705: INFO: Pod "pod-subpath-test-dynamicpv-xlmn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.625770529s
STEP: Saw pod success
Jun  8 08:18:24.705: INFO: Pod "pod-subpath-test-dynamicpv-xlmn" satisfied condition "Succeeded or Failed"
Jun  8 08:18:24.749: INFO: Trying to get logs from node ip-172-20-58-151.ec2.internal pod pod-subpath-test-dynamicpv-xlmn container test-container-subpath-dynamicpv-xlmn: <nil>
STEP: delete the pod
Jun  8 08:18:24.848: INFO: Waiting for pod pod-subpath-test-dynamicpv-xlmn to disappear
Jun  8 08:18:24.891: INFO: Pod pod-subpath-test-dynamicpv-xlmn no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-xlmn
Jun  8 08:18:24.891: INFO: Deleting pod "pod-subpath-test-dynamicpv-xlmn" in namespace "provisioning-1227"
STEP: Creating pod pod-subpath-test-dynamicpv-xlmn
STEP: Creating a pod to test subpath
Jun  8 08:18:24.980: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-xlmn" in namespace "provisioning-1227" to be "Succeeded or Failed"
Jun  8 08:18:25.023: INFO: Pod "pod-subpath-test-dynamicpv-xlmn": Phase="Pending", Reason="", readiness=false. Elapsed: 43.008729ms
Jun  8 08:18:27.066: INFO: Pod "pod-subpath-test-dynamicpv-xlmn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.086285445s
Jun  8 08:18:29.111: INFO: Pod "pod-subpath-test-dynamicpv-xlmn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.130883541s
Jun  8 08:18:31.161: INFO: Pod "pod-subpath-test-dynamicpv-xlmn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.181264804s
Jun  8 08:18:33.208: INFO: Pod "pod-subpath-test-dynamicpv-xlmn": Phase="Pending", Reason="", readiness=false. Elapsed: 8.227649253s
Jun  8 08:18:35.252: INFO: Pod "pod-subpath-test-dynamicpv-xlmn": Phase="Pending", Reason="", readiness=false. Elapsed: 10.272376868s
Jun  8 08:18:37.296: INFO: Pod "pod-subpath-test-dynamicpv-xlmn": Phase="Pending", Reason="", readiness=false. Elapsed: 12.316425504s
Jun  8 08:18:39.341: INFO: Pod "pod-subpath-test-dynamicpv-xlmn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.361427875s
STEP: Saw pod success
Jun  8 08:18:39.342: INFO: Pod "pod-subpath-test-dynamicpv-xlmn" satisfied condition "Succeeded or Failed"
Jun  8 08:18:39.385: INFO: Trying to get logs from node ip-172-20-58-151.ec2.internal pod pod-subpath-test-dynamicpv-xlmn container test-container-subpath-dynamicpv-xlmn: <nil>
STEP: delete the pod
Jun  8 08:18:39.483: INFO: Waiting for pod pod-subpath-test-dynamicpv-xlmn to disappear
Jun  8 08:18:39.527: INFO: Pod pod-subpath-test-dynamicpv-xlmn no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-xlmn
Jun  8 08:18:39.527: INFO: Deleting pod "pod-subpath-test-dynamicpv-xlmn" in namespace "provisioning-1227"
... skipping 153 lines ...
Jun  8 08:18:48.213: INFO: Pod aws-client still exists
Jun  8 08:18:50.169: INFO: Waiting for pod aws-client to disappear
Jun  8 08:18:50.212: INFO: Pod aws-client still exists
Jun  8 08:18:52.169: INFO: Waiting for pod aws-client to disappear
Jun  8 08:18:52.212: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun  8 08:18:52.439: INFO: Couldn't delete PD "aws://us-east-1a/vol-0f81340c865a26c0c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f81340c865a26c0c is currently attached to i-05e5a3b84c6a72dab
	status code: 400, request id: 8e058e13-7559-45d2-99a3-454efc0177f3
Jun  8 08:18:57.801: INFO: Couldn't delete PD "aws://us-east-1a/vol-0f81340c865a26c0c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f81340c865a26c0c is currently attached to i-05e5a3b84c6a72dab
	status code: 400, request id: 9611163b-63fa-4449-8180-4d8eaaa83393
Jun  8 08:19:03.207: INFO: Successfully deleted PD "aws://us-east-1a/vol-0f81340c865a26c0c".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  8 08:19:03.207: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-1632" for this suite.
... skipping 18 lines ...

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

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

    /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:92
------------------------------
... skipping 61 lines ...
Jun  8 08:17:56.199: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1562-e2e-sckm4jp
STEP: creating a claim
Jun  8 08:17:56.242: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-xhmb
STEP: Creating a pod to test multi_subpath
Jun  8 08:17:56.378: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-xhmb" in namespace "provisioning-1562" to be "Succeeded or Failed"
Jun  8 08:17:56.423: INFO: Pod "pod-subpath-test-dynamicpv-xhmb": Phase="Pending", Reason="", readiness=false. Elapsed: 44.882571ms
Jun  8 08:17:58.466: INFO: Pod "pod-subpath-test-dynamicpv-xhmb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.087757515s
Jun  8 08:18:00.509: INFO: Pod "pod-subpath-test-dynamicpv-xhmb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.130360641s
Jun  8 08:18:02.553: INFO: Pod "pod-subpath-test-dynamicpv-xhmb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.174423316s
Jun  8 08:18:04.596: INFO: Pod "pod-subpath-test-dynamicpv-xhmb": Phase="Pending", Reason="", readiness=false. Elapsed: 8.217522181s
Jun  8 08:18:06.639: INFO: Pod "pod-subpath-test-dynamicpv-xhmb": Phase="Pending", Reason="", readiness=false. Elapsed: 10.261117107s
... skipping 6 lines ...
Jun  8 08:18:20.944: INFO: Pod "pod-subpath-test-dynamicpv-xhmb": Phase="Pending", Reason="", readiness=false. Elapsed: 24.565862482s
Jun  8 08:18:22.987: INFO: Pod "pod-subpath-test-dynamicpv-xhmb": Phase="Pending", Reason="", readiness=false. Elapsed: 26.609090844s
Jun  8 08:18:25.030: INFO: Pod "pod-subpath-test-dynamicpv-xhmb": Phase="Pending", Reason="", readiness=false. Elapsed: 28.651656655s
Jun  8 08:18:27.075: INFO: Pod "pod-subpath-test-dynamicpv-xhmb": Phase="Pending", Reason="", readiness=false. Elapsed: 30.696754235s
Jun  8 08:18:29.117: INFO: Pod "pod-subpath-test-dynamicpv-xhmb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 32.73915593s
STEP: Saw pod success
Jun  8 08:18:29.118: INFO: Pod "pod-subpath-test-dynamicpv-xhmb" satisfied condition "Succeeded or Failed"
Jun  8 08:18:29.160: INFO: Trying to get logs from node ip-172-20-58-151.ec2.internal pod pod-subpath-test-dynamicpv-xhmb container test-container-subpath-dynamicpv-xhmb: <nil>
STEP: delete the pod
Jun  8 08:18:29.253: INFO: Waiting for pod pod-subpath-test-dynamicpv-xhmb to disappear
Jun  8 08:18:29.312: INFO: Pod pod-subpath-test-dynamicpv-xhmb no longer exists
STEP: Deleting pod
Jun  8 08:18:29.312: INFO: Deleting pod "pod-subpath-test-dynamicpv-xhmb" in namespace "provisioning-1562"
... skipping 161 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.YIoOihHZk/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.YIoOihHZk/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.YIoOihHZk/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.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 79 lines ...
Jun  8 08:19:20.991: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 234 lines ...
Jun  8 08:18:44.928: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2346n7gvp
STEP: creating a claim
Jun  8 08:18:44.971: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-869h
STEP: Creating a pod to test multi_subpath
Jun  8 08:18:45.102: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-869h" in namespace "provisioning-2346" to be "Succeeded or Failed"
Jun  8 08:18:45.149: INFO: Pod "pod-subpath-test-dynamicpv-869h": Phase="Pending", Reason="", readiness=false. Elapsed: 47.650164ms
Jun  8 08:18:47.192: INFO: Pod "pod-subpath-test-dynamicpv-869h": Phase="Pending", Reason="", readiness=false. Elapsed: 2.090193974s
Jun  8 08:18:49.236: INFO: Pod "pod-subpath-test-dynamicpv-869h": Phase="Pending", Reason="", readiness=false. Elapsed: 4.133995916s
Jun  8 08:18:51.278: INFO: Pod "pod-subpath-test-dynamicpv-869h": Phase="Pending", Reason="", readiness=false. Elapsed: 6.176462849s
Jun  8 08:18:53.321: INFO: Pod "pod-subpath-test-dynamicpv-869h": Phase="Pending", Reason="", readiness=false. Elapsed: 8.219254549s
Jun  8 08:18:55.368: INFO: Pod "pod-subpath-test-dynamicpv-869h": Phase="Pending", Reason="", readiness=false. Elapsed: 10.266335707s
... skipping 3 lines ...
Jun  8 08:19:03.540: INFO: Pod "pod-subpath-test-dynamicpv-869h": Phase="Pending", Reason="", readiness=false. Elapsed: 18.438178412s
Jun  8 08:19:05.584: INFO: Pod "pod-subpath-test-dynamicpv-869h": Phase="Pending", Reason="", readiness=false. Elapsed: 20.482488825s
Jun  8 08:19:07.627: INFO: Pod "pod-subpath-test-dynamicpv-869h": Phase="Pending", Reason="", readiness=false. Elapsed: 22.525303733s
Jun  8 08:19:09.670: INFO: Pod "pod-subpath-test-dynamicpv-869h": Phase="Pending", Reason="", readiness=false. Elapsed: 24.568249569s
Jun  8 08:19:11.714: INFO: Pod "pod-subpath-test-dynamicpv-869h": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.612328294s
STEP: Saw pod success
Jun  8 08:19:11.714: INFO: Pod "pod-subpath-test-dynamicpv-869h" satisfied condition "Succeeded or Failed"
Jun  8 08:19:11.756: INFO: Trying to get logs from node ip-172-20-58-151.ec2.internal pod pod-subpath-test-dynamicpv-869h container test-container-subpath-dynamicpv-869h: <nil>
STEP: delete the pod
Jun  8 08:19:11.847: INFO: Waiting for pod pod-subpath-test-dynamicpv-869h to disappear
Jun  8 08:19:11.889: INFO: Pod pod-subpath-test-dynamicpv-869h no longer exists
STEP: Deleting pod
Jun  8 08:19:11.889: INFO: Deleting pod "pod-subpath-test-dynamicpv-869h" in namespace "provisioning-2346"
... skipping 63 lines ...
Jun  8 08:18:49.314: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4159hxs9k
STEP: creating a claim
Jun  8 08:18:49.359: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-5j77
STEP: Creating a pod to test subpath
Jun  8 08:18:49.491: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-5j77" in namespace "provisioning-4159" to be "Succeeded or Failed"
Jun  8 08:18:49.535: INFO: Pod "pod-subpath-test-dynamicpv-5j77": Phase="Pending", Reason="", readiness=false. Elapsed: 43.609168ms
Jun  8 08:18:51.578: INFO: Pod "pod-subpath-test-dynamicpv-5j77": Phase="Pending", Reason="", readiness=false. Elapsed: 2.086634083s
Jun  8 08:18:53.622: INFO: Pod "pod-subpath-test-dynamicpv-5j77": Phase="Pending", Reason="", readiness=false. Elapsed: 4.130285097s
Jun  8 08:18:55.665: INFO: Pod "pod-subpath-test-dynamicpv-5j77": Phase="Pending", Reason="", readiness=false. Elapsed: 6.173210795s
Jun  8 08:18:57.707: INFO: Pod "pod-subpath-test-dynamicpv-5j77": Phase="Pending", Reason="", readiness=false. Elapsed: 8.21564041s
Jun  8 08:18:59.751: INFO: Pod "pod-subpath-test-dynamicpv-5j77": Phase="Pending", Reason="", readiness=false. Elapsed: 10.259429772s
... skipping 6 lines ...
Jun  8 08:19:14.057: INFO: Pod "pod-subpath-test-dynamicpv-5j77": Phase="Pending", Reason="", readiness=false. Elapsed: 24.565837333s
Jun  8 08:19:16.100: INFO: Pod "pod-subpath-test-dynamicpv-5j77": Phase="Pending", Reason="", readiness=false. Elapsed: 26.608506546s
Jun  8 08:19:18.143: INFO: Pod "pod-subpath-test-dynamicpv-5j77": Phase="Pending", Reason="", readiness=false. Elapsed: 28.651644496s
Jun  8 08:19:20.185: INFO: Pod "pod-subpath-test-dynamicpv-5j77": Phase="Pending", Reason="", readiness=false. Elapsed: 30.694072845s
Jun  8 08:19:22.229: INFO: Pod "pod-subpath-test-dynamicpv-5j77": Phase="Succeeded", Reason="", readiness=false. Elapsed: 32.737675343s
STEP: Saw pod success
Jun  8 08:19:22.229: INFO: Pod "pod-subpath-test-dynamicpv-5j77" satisfied condition "Succeeded or Failed"
Jun  8 08:19:22.271: INFO: Trying to get logs from node ip-172-20-58-151.ec2.internal pod pod-subpath-test-dynamicpv-5j77 container test-container-volume-dynamicpv-5j77: <nil>
STEP: delete the pod
Jun  8 08:19:22.363: INFO: Waiting for pod pod-subpath-test-dynamicpv-5j77 to disappear
Jun  8 08:19:22.405: INFO: Pod pod-subpath-test-dynamicpv-5j77 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-5j77
Jun  8 08:19:22.405: INFO: Deleting pod "pod-subpath-test-dynamicpv-5j77" in namespace "provisioning-4159"
... skipping 238 lines ...
Jun  8 08:18:58.944: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7124-e2e-scqxxhj
STEP: creating a claim
Jun  8 08:18:58.989: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-wz7h
STEP: Creating a pod to test subpath
Jun  8 08:18:59.122: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-wz7h" in namespace "provisioning-7124" to be "Succeeded or Failed"
Jun  8 08:18:59.165: INFO: Pod "pod-subpath-test-dynamicpv-wz7h": Phase="Pending", Reason="", readiness=false. Elapsed: 42.749573ms
Jun  8 08:19:01.208: INFO: Pod "pod-subpath-test-dynamicpv-wz7h": Phase="Pending", Reason="", readiness=false. Elapsed: 2.086533467s
Jun  8 08:19:03.252: INFO: Pod "pod-subpath-test-dynamicpv-wz7h": Phase="Pending", Reason="", readiness=false. Elapsed: 4.130641104s
Jun  8 08:19:05.296: INFO: Pod "pod-subpath-test-dynamicpv-wz7h": Phase="Pending", Reason="", readiness=false. Elapsed: 6.174709667s
Jun  8 08:19:07.340: INFO: Pod "pod-subpath-test-dynamicpv-wz7h": Phase="Pending", Reason="", readiness=false. Elapsed: 8.218305963s
Jun  8 08:19:09.384: INFO: Pod "pod-subpath-test-dynamicpv-wz7h": Phase="Pending", Reason="", readiness=false. Elapsed: 10.262456498s
... skipping 5 lines ...
Jun  8 08:19:21.648: INFO: Pod "pod-subpath-test-dynamicpv-wz7h": Phase="Pending", Reason="", readiness=false. Elapsed: 22.526624752s
Jun  8 08:19:23.692: INFO: Pod "pod-subpath-test-dynamicpv-wz7h": Phase="Pending", Reason="", readiness=false. Elapsed: 24.570107251s
Jun  8 08:19:25.736: INFO: Pod "pod-subpath-test-dynamicpv-wz7h": Phase="Pending", Reason="", readiness=false. Elapsed: 26.614225629s
Jun  8 08:19:27.781: INFO: Pod "pod-subpath-test-dynamicpv-wz7h": Phase="Pending", Reason="", readiness=false. Elapsed: 28.658774342s
Jun  8 08:19:29.826: INFO: Pod "pod-subpath-test-dynamicpv-wz7h": Phase="Succeeded", Reason="", readiness=false. Elapsed: 30.704281031s
STEP: Saw pod success
Jun  8 08:19:29.826: INFO: Pod "pod-subpath-test-dynamicpv-wz7h" satisfied condition "Succeeded or Failed"
Jun  8 08:19:29.869: INFO: Trying to get logs from node ip-172-20-47-76.ec2.internal pod pod-subpath-test-dynamicpv-wz7h container test-container-subpath-dynamicpv-wz7h: <nil>
STEP: delete the pod
Jun  8 08:19:29.976: INFO: Waiting for pod pod-subpath-test-dynamicpv-wz7h to disappear
Jun  8 08:19:30.019: INFO: Pod pod-subpath-test-dynamicpv-wz7h no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-wz7h
Jun  8 08:19:30.019: INFO: Deleting pod "pod-subpath-test-dynamicpv-wz7h" in namespace "provisioning-7124"
... skipping 115 lines ...

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

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

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

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 90 lines ...
Jun  8 08:19:12.149: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4445m9dvl
STEP: creating a claim
Jun  8 08:19:12.193: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-xfdr
STEP: Creating a pod to test atomic-volume-subpath
Jun  8 08:19:12.360: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-xfdr" in namespace "provisioning-4445" to be "Succeeded or Failed"
Jun  8 08:19:12.402: INFO: Pod "pod-subpath-test-dynamicpv-xfdr": Phase="Pending", Reason="", readiness=false. Elapsed: 42.362412ms
Jun  8 08:19:14.446: INFO: Pod "pod-subpath-test-dynamicpv-xfdr": Phase="Pending", Reason="", readiness=false. Elapsed: 2.086202312s
Jun  8 08:19:16.490: INFO: Pod "pod-subpath-test-dynamicpv-xfdr": Phase="Pending", Reason="", readiness=false. Elapsed: 4.130033449s
Jun  8 08:19:18.533: INFO: Pod "pod-subpath-test-dynamicpv-xfdr": Phase="Pending", Reason="", readiness=false. Elapsed: 6.17347942s
Jun  8 08:19:20.577: INFO: Pod "pod-subpath-test-dynamicpv-xfdr": Phase="Pending", Reason="", readiness=false. Elapsed: 8.216856259s
Jun  8 08:19:22.623: INFO: Pod "pod-subpath-test-dynamicpv-xfdr": Phase="Pending", Reason="", readiness=false. Elapsed: 10.263491622s
... skipping 7 lines ...
Jun  8 08:19:38.973: INFO: Pod "pod-subpath-test-dynamicpv-xfdr": Phase="Running", Reason="", readiness=true. Elapsed: 26.613350031s
Jun  8 08:19:41.018: INFO: Pod "pod-subpath-test-dynamicpv-xfdr": Phase="Running", Reason="", readiness=true. Elapsed: 28.657687821s
Jun  8 08:19:43.065: INFO: Pod "pod-subpath-test-dynamicpv-xfdr": Phase="Running", Reason="", readiness=true. Elapsed: 30.705236157s
Jun  8 08:19:45.110: INFO: Pod "pod-subpath-test-dynamicpv-xfdr": Phase="Running", Reason="", readiness=true. Elapsed: 32.750497342s
Jun  8 08:19:47.154: INFO: Pod "pod-subpath-test-dynamicpv-xfdr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.794076482s
STEP: Saw pod success
Jun  8 08:19:47.154: INFO: Pod "pod-subpath-test-dynamicpv-xfdr" satisfied condition "Succeeded or Failed"
Jun  8 08:19:47.196: INFO: Trying to get logs from node ip-172-20-47-76.ec2.internal pod pod-subpath-test-dynamicpv-xfdr container test-container-subpath-dynamicpv-xfdr: <nil>
STEP: delete the pod
Jun  8 08:19:47.291: INFO: Waiting for pod pod-subpath-test-dynamicpv-xfdr to disappear
Jun  8 08:19:47.337: INFO: Pod pod-subpath-test-dynamicpv-xfdr no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-xfdr
Jun  8 08:19:47.337: INFO: Deleting pod "pod-subpath-test-dynamicpv-xfdr" in namespace "provisioning-4445"
... skipping 155 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  8 08:19:05.026: 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.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun  8 08:19:05.246: INFO: Creating resource for dynamic PV
Jun  8 08:19:05.246: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6637-e2e-scqshnq
STEP: creating a claim
Jun  8 08:19:05.291: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-lz59
STEP: Checking for subpath error in container status
Jun  8 08:19:25.515: INFO: Deleting pod "pod-subpath-test-dynamicpv-lz59" in namespace "provisioning-6637"
Jun  8 08:19:25.563: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-lz59" to be fully deleted
STEP: Deleting pod
Jun  8 08:19:29.648: INFO: Deleting pod "pod-subpath-test-dynamicpv-lz59" in namespace "provisioning-6637"
STEP: Deleting pvc
Jun  8 08:19:29.775: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comhf44p"
... skipping 15 lines ...

• [SLOW TEST:60.271 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath file is outside the volume [Slow][LinuxOnly]
    /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  8 08:20:05.299: INFO: Driver "ebs.csi.aws.com" does not support volume type "InlineVolume" - skipping
[AfterEach] [Testpattern: Inline-volume (default fs)] subPath
... skipping 2 lines ...

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

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

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

    /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 12 lines ...
Jun  8 08:19:39.046: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-2950w8bqh
STEP: creating a claim
Jun  8 08:19:39.088: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Jun  8 08:19:39.174: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun  8 08:19:39.260: INFO: Error updating pvc awsvzfk6: PersistentVolumeClaim "awsvzfk6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2950w8bqh",
  	... // 2 identical fields
  }

Jun  8 08:19:41.348: INFO: Error updating pvc awsvzfk6: PersistentVolumeClaim "awsvzfk6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2950w8bqh",
  	... // 2 identical fields
  }

Jun  8 08:19:43.347: INFO: Error updating pvc awsvzfk6: PersistentVolumeClaim "awsvzfk6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2950w8bqh",
  	... // 2 identical fields
  }

Jun  8 08:19:45.345: INFO: Error updating pvc awsvzfk6: PersistentVolumeClaim "awsvzfk6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2950w8bqh",
  	... // 2 identical fields
  }

Jun  8 08:19:47.346: INFO: Error updating pvc awsvzfk6: PersistentVolumeClaim "awsvzfk6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2950w8bqh",
  	... // 2 identical fields
  }

Jun  8 08:19:49.345: INFO: Error updating pvc awsvzfk6: PersistentVolumeClaim "awsvzfk6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2950w8bqh",
  	... // 2 identical fields
  }

Jun  8 08:19:51.350: INFO: Error updating pvc awsvzfk6: PersistentVolumeClaim "awsvzfk6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2950w8bqh",
  	... // 2 identical fields
  }

Jun  8 08:19:53.346: INFO: Error updating pvc awsvzfk6: PersistentVolumeClaim "awsvzfk6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2950w8bqh",
  	... // 2 identical fields
  }

Jun  8 08:19:55.345: INFO: Error updating pvc awsvzfk6: PersistentVolumeClaim "awsvzfk6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2950w8bqh",
  	... // 2 identical fields
  }

Jun  8 08:19:57.348: INFO: Error updating pvc awsvzfk6: PersistentVolumeClaim "awsvzfk6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2950w8bqh",
  	... // 2 identical fields
  }

Jun  8 08:19:59.346: INFO: Error updating pvc awsvzfk6: PersistentVolumeClaim "awsvzfk6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2950w8bqh",
  	... // 2 identical fields
  }

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

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

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

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

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

Jun  8 08:20:09.432: INFO: Error updating pvc awsvzfk6: PersistentVolumeClaim "awsvzfk6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 1236 lines ...
Jun  8 08:19:46.159: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7642-e2e-sc9599x
STEP: creating a claim
Jun  8 08:19:46.203: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-rvvp
STEP: Creating a pod to test subpath
Jun  8 08:19:46.334: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-rvvp" in namespace "provisioning-7642" to be "Succeeded or Failed"
Jun  8 08:19:46.379: INFO: Pod "pod-subpath-test-dynamicpv-rvvp": Phase="Pending", Reason="", readiness=false. Elapsed: 45.278236ms
Jun  8 08:19:48.423: INFO: Pod "pod-subpath-test-dynamicpv-rvvp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.088921709s
Jun  8 08:19:50.465: INFO: Pod "pod-subpath-test-dynamicpv-rvvp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.131490725s
Jun  8 08:19:52.508: INFO: Pod "pod-subpath-test-dynamicpv-rvvp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.174122959s
Jun  8 08:19:54.552: INFO: Pod "pod-subpath-test-dynamicpv-rvvp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.218774098s
Jun  8 08:19:56.596: INFO: Pod "pod-subpath-test-dynamicpv-rvvp": Phase="Pending", Reason="", readiness=false. Elapsed: 10.262504823s
Jun  8 08:19:58.639: INFO: Pod "pod-subpath-test-dynamicpv-rvvp": Phase="Pending", Reason="", readiness=false. Elapsed: 12.305373046s
Jun  8 08:20:00.682: INFO: Pod "pod-subpath-test-dynamicpv-rvvp": Phase="Pending", Reason="", readiness=false. Elapsed: 14.347993518s
Jun  8 08:20:02.726: INFO: Pod "pod-subpath-test-dynamicpv-rvvp": Phase="Pending", Reason="", readiness=false. Elapsed: 16.392166897s
Jun  8 08:20:04.769: INFO: Pod "pod-subpath-test-dynamicpv-rvvp": Phase="Pending", Reason="", readiness=false. Elapsed: 18.434960031s
Jun  8 08:20:06.812: INFO: Pod "pod-subpath-test-dynamicpv-rvvp": Phase="Pending", Reason="", readiness=false. Elapsed: 20.478618127s
Jun  8 08:20:08.855: INFO: Pod "pod-subpath-test-dynamicpv-rvvp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.521119471s
STEP: Saw pod success
Jun  8 08:20:08.855: INFO: Pod "pod-subpath-test-dynamicpv-rvvp" satisfied condition "Succeeded or Failed"
Jun  8 08:20:08.897: INFO: Trying to get logs from node ip-172-20-58-151.ec2.internal pod pod-subpath-test-dynamicpv-rvvp container test-container-subpath-dynamicpv-rvvp: <nil>
STEP: delete the pod
Jun  8 08:20:09.003: INFO: Waiting for pod pod-subpath-test-dynamicpv-rvvp to disappear
Jun  8 08:20:09.045: INFO: Pod pod-subpath-test-dynamicpv-rvvp no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-rvvp
Jun  8 08:20:09.045: INFO: Deleting pod "pod-subpath-test-dynamicpv-rvvp" in namespace "provisioning-7642"
... skipping 153 lines ...
Jun  8 08:20:12.813: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-4288z2fcm
STEP: creating a claim
Jun  8 08:20:12.856: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-bbnz
STEP: Creating a pod to test exec-volume-test
Jun  8 08:20:12.986: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-bbnz" in namespace "volume-4288" to be "Succeeded or Failed"
Jun  8 08:20:13.069: INFO: Pod "exec-volume-test-dynamicpv-bbnz": Phase="Pending", Reason="", readiness=false. Elapsed: 83.166242ms
Jun  8 08:20:15.117: INFO: Pod "exec-volume-test-dynamicpv-bbnz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.130651468s
Jun  8 08:20:17.162: INFO: Pod "exec-volume-test-dynamicpv-bbnz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.175286155s
Jun  8 08:20:19.206: INFO: Pod "exec-volume-test-dynamicpv-bbnz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.220162731s
Jun  8 08:20:21.252: INFO: Pod "exec-volume-test-dynamicpv-bbnz": Phase="Pending", Reason="", readiness=false. Elapsed: 8.265650993s
Jun  8 08:20:23.296: INFO: Pod "exec-volume-test-dynamicpv-bbnz": Phase="Pending", Reason="", readiness=false. Elapsed: 10.309313769s
Jun  8 08:20:25.340: INFO: Pod "exec-volume-test-dynamicpv-bbnz": Phase="Pending", Reason="", readiness=false. Elapsed: 12.353226511s
Jun  8 08:20:27.384: INFO: Pod "exec-volume-test-dynamicpv-bbnz": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.397637829s
STEP: Saw pod success
Jun  8 08:20:27.384: INFO: Pod "exec-volume-test-dynamicpv-bbnz" satisfied condition "Succeeded or Failed"
Jun  8 08:20:27.427: INFO: Trying to get logs from node ip-172-20-58-151.ec2.internal pod exec-volume-test-dynamicpv-bbnz container exec-container-dynamicpv-bbnz: <nil>
STEP: delete the pod
Jun  8 08:20:27.520: INFO: Waiting for pod exec-volume-test-dynamicpv-bbnz to disappear
Jun  8 08:20:27.562: INFO: Pod exec-volume-test-dynamicpv-bbnz no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-bbnz
Jun  8 08:20:27.562: INFO: Deleting pod "exec-volume-test-dynamicpv-bbnz" in namespace "volume-4288"
... skipping 35 lines ...
Jun  8 08:20:00.592: INFO: Creating resource for dynamic PV
Jun  8 08:20:00.592: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1657-e2e-sch5rfr
STEP: creating a claim
Jun  8 08:20:00.638: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-1657
Jun  8 08:20:00.771: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-1657" in namespace "provisioning-1657" to be "Succeeded or Failed"
Jun  8 08:20:00.816: INFO: Pod "volume-prep-provisioning-1657": Phase="Pending", Reason="", readiness=false. Elapsed: 45.201474ms
Jun  8 08:20:02.863: INFO: Pod "volume-prep-provisioning-1657": Phase="Pending", Reason="", readiness=false. Elapsed: 2.092016869s
Jun  8 08:20:04.908: INFO: Pod "volume-prep-provisioning-1657": Phase="Pending", Reason="", readiness=false. Elapsed: 4.136990399s
Jun  8 08:20:06.952: INFO: Pod "volume-prep-provisioning-1657": Phase="Pending", Reason="", readiness=false. Elapsed: 6.181591855s
Jun  8 08:20:09.002: INFO: Pod "volume-prep-provisioning-1657": Phase="Pending", Reason="", readiness=false. Elapsed: 8.231696589s
Jun  8 08:20:11.050: INFO: Pod "volume-prep-provisioning-1657": Phase="Pending", Reason="", readiness=false. Elapsed: 10.279132649s
Jun  8 08:20:13.095: INFO: Pod "volume-prep-provisioning-1657": Phase="Pending", Reason="", readiness=false. Elapsed: 12.324054476s
Jun  8 08:20:15.139: INFO: Pod "volume-prep-provisioning-1657": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.368648935s
STEP: Saw pod success
Jun  8 08:20:15.140: INFO: Pod "volume-prep-provisioning-1657" satisfied condition "Succeeded or Failed"
Jun  8 08:20:15.140: INFO: Deleting pod "volume-prep-provisioning-1657" in namespace "provisioning-1657"
Jun  8 08:20:15.186: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-1657" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-kpwj
STEP: Checking for subpath error in container status
Jun  8 08:20:19.365: INFO: Deleting pod "pod-subpath-test-dynamicpv-kpwj" in namespace "provisioning-1657"
Jun  8 08:20:19.414: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-kpwj" to be fully deleted
STEP: Deleting pod
Jun  8 08:20:19.457: INFO: Deleting pod "pod-subpath-test-dynamicpv-kpwj" in namespace "provisioning-1657"
STEP: Deleting pvc
Jun  8 08:20:19.590: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comj8t4r"
... skipping 210 lines ...
Jun  8 08:19:58.053: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4334-e2e-scdczjq
STEP: creating a claim
Jun  8 08:19:58.098: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-rvmr
STEP: Creating a pod to test atomic-volume-subpath
Jun  8 08:19:58.242: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-rvmr" in namespace "provisioning-4334" to be "Succeeded or Failed"
Jun  8 08:19:58.287: INFO: Pod "pod-subpath-test-dynamicpv-rvmr": Phase="Pending", Reason="", readiness=false. Elapsed: 45.264672ms
Jun  8 08:20:00.331: INFO: Pod "pod-subpath-test-dynamicpv-rvmr": Phase="Pending", Reason="", readiness=false. Elapsed: 2.088668817s
Jun  8 08:20:02.374: INFO: Pod "pod-subpath-test-dynamicpv-rvmr": Phase="Pending", Reason="", readiness=false. Elapsed: 4.131917804s
Jun  8 08:20:04.417: INFO: Pod "pod-subpath-test-dynamicpv-rvmr": Phase="Pending", Reason="", readiness=false. Elapsed: 6.175506588s
Jun  8 08:20:06.462: INFO: Pod "pod-subpath-test-dynamicpv-rvmr": Phase="Pending", Reason="", readiness=false. Elapsed: 8.219573026s
Jun  8 08:20:08.504: INFO: Pod "pod-subpath-test-dynamicpv-rvmr": Phase="Pending", Reason="", readiness=false. Elapsed: 10.262461337s
... skipping 11 lines ...
Jun  8 08:20:33.033: INFO: Pod "pod-subpath-test-dynamicpv-rvmr": Phase="Running", Reason="", readiness=true. Elapsed: 34.790617827s
Jun  8 08:20:35.076: INFO: Pod "pod-subpath-test-dynamicpv-rvmr": Phase="Running", Reason="", readiness=true. Elapsed: 36.833847632s
Jun  8 08:20:37.120: INFO: Pod "pod-subpath-test-dynamicpv-rvmr": Phase="Running", Reason="", readiness=true. Elapsed: 38.87793406s
Jun  8 08:20:39.163: INFO: Pod "pod-subpath-test-dynamicpv-rvmr": Phase="Running", Reason="", readiness=true. Elapsed: 40.921086976s
Jun  8 08:20:41.207: INFO: Pod "pod-subpath-test-dynamicpv-rvmr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 42.965459321s
STEP: Saw pod success
Jun  8 08:20:41.208: INFO: Pod "pod-subpath-test-dynamicpv-rvmr" satisfied condition "Succeeded or Failed"
Jun  8 08:20:41.250: INFO: Trying to get logs from node ip-172-20-39-149.ec2.internal pod pod-subpath-test-dynamicpv-rvmr container test-container-subpath-dynamicpv-rvmr: <nil>
STEP: delete the pod
Jun  8 08:20:41.343: INFO: Waiting for pod pod-subpath-test-dynamicpv-rvmr to disappear
Jun  8 08:20:41.386: INFO: Pod pod-subpath-test-dynamicpv-rvmr no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-rvmr
Jun  8 08:20:41.386: INFO: Deleting pod "pod-subpath-test-dynamicpv-rvmr" in namespace "provisioning-4334"
... skipping 190 lines ...
Jun  8 08:20:32.334: INFO: PersistentVolumeClaim pvc-vdp7f found but phase is Pending instead of Bound.
Jun  8 08:20:34.378: INFO: PersistentVolumeClaim pvc-vdp7f found and phase=Bound (4.127975047s)
Jun  8 08:20:34.378: INFO: Waiting up to 3m0s for PersistentVolume aws-xxx77 to have phase Bound
Jun  8 08:20:34.420: INFO: PersistentVolume aws-xxx77 found and phase=Bound (42.271827ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-jhmv
STEP: Creating a pod to test exec-volume-test
Jun  8 08:20:34.547: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-jhmv" in namespace "volume-8193" to be "Succeeded or Failed"
Jun  8 08:20:34.590: INFO: Pod "exec-volume-test-preprovisionedpv-jhmv": Phase="Pending", Reason="", readiness=false. Elapsed: 42.392601ms
Jun  8 08:20:36.633: INFO: Pod "exec-volume-test-preprovisionedpv-jhmv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.085810835s
Jun  8 08:20:38.676: INFO: Pod "exec-volume-test-preprovisionedpv-jhmv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.12838036s
Jun  8 08:20:40.719: INFO: Pod "exec-volume-test-preprovisionedpv-jhmv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.171852196s
Jun  8 08:20:42.762: INFO: Pod "exec-volume-test-preprovisionedpv-jhmv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.215257932s
Jun  8 08:20:44.808: INFO: Pod "exec-volume-test-preprovisionedpv-jhmv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.260911296s
... skipping 7 lines ...
Jun  8 08:21:01.153: INFO: Pod "exec-volume-test-preprovisionedpv-jhmv": Phase="Pending", Reason="", readiness=false. Elapsed: 26.605850369s
Jun  8 08:21:03.196: INFO: Pod "exec-volume-test-preprovisionedpv-jhmv": Phase="Pending", Reason="", readiness=false. Elapsed: 28.648807194s
Jun  8 08:21:05.242: INFO: Pod "exec-volume-test-preprovisionedpv-jhmv": Phase="Pending", Reason="", readiness=false. Elapsed: 30.695218335s
Jun  8 08:21:07.285: INFO: Pod "exec-volume-test-preprovisionedpv-jhmv": Phase="Pending", Reason="", readiness=false. Elapsed: 32.737933939s
Jun  8 08:21:09.328: INFO: Pod "exec-volume-test-preprovisionedpv-jhmv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.780453617s
STEP: Saw pod success
Jun  8 08:21:09.328: INFO: Pod "exec-volume-test-preprovisionedpv-jhmv" satisfied condition "Succeeded or Failed"
Jun  8 08:21:09.371: INFO: Trying to get logs from node ip-172-20-58-151.ec2.internal pod exec-volume-test-preprovisionedpv-jhmv container exec-container-preprovisionedpv-jhmv: <nil>
STEP: delete the pod
Jun  8 08:21:09.467: INFO: Waiting for pod exec-volume-test-preprovisionedpv-jhmv to disappear
Jun  8 08:21:09.509: INFO: Pod exec-volume-test-preprovisionedpv-jhmv no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-jhmv
Jun  8 08:21:09.509: INFO: Deleting pod "exec-volume-test-preprovisionedpv-jhmv" in namespace "volume-8193"
STEP: Deleting pv and pvc
Jun  8 08:21:09.551: INFO: Deleting PersistentVolumeClaim "pvc-vdp7f"
Jun  8 08:21:09.601: INFO: Deleting PersistentVolume "aws-xxx77"
Jun  8 08:21:09.901: INFO: Couldn't delete PD "aws://us-east-1a/vol-0b4a6990cc71b922b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0b4a6990cc71b922b is currently attached to i-07b0c6559cfd9ece1
	status code: 400, request id: 760f9603-6a83-41fd-8f5e-f9e942522ce2
Jun  8 08:21:15.415: INFO: Couldn't delete PD "aws://us-east-1a/vol-0b4a6990cc71b922b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0b4a6990cc71b922b is currently attached to i-07b0c6559cfd9ece1
	status code: 400, request id: 1eef1a11-bd74-4772-9e55-8961a9fb130f
Jun  8 08:21:20.851: INFO: Couldn't delete PD "aws://us-east-1a/vol-0b4a6990cc71b922b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0b4a6990cc71b922b is currently attached to i-07b0c6559cfd9ece1
	status code: 400, request id: f1f8e922-afba-42f1-b3e5-be8bd3cc8cfb
Jun  8 08:21:26.224: INFO: Successfully deleted PD "aws://us-east-1a/vol-0b4a6990cc71b922b".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  8 08:21:26.224: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8193" for this suite.
... skipping 135 lines ...
Jun  8 08:21:06.674: INFO: Pod aws-client still exists
Jun  8 08:21:08.630: INFO: Waiting for pod aws-client to disappear
Jun  8 08:21:08.672: INFO: Pod aws-client still exists
Jun  8 08:21:10.630: INFO: Waiting for pod aws-client to disappear
Jun  8 08:21:10.673: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun  8 08:21:11.098: INFO: Couldn't delete PD "aws://us-east-1a/vol-0e5d4661938a6eca2", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e5d4661938a6eca2 is currently attached to i-07b0c6559cfd9ece1
	status code: 400, request id: 1e09210b-79a3-433f-8dba-f637d822f7b3
Jun  8 08:21:16.507: INFO: Couldn't delete PD "aws://us-east-1a/vol-0e5d4661938a6eca2", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e5d4661938a6eca2 is currently attached to i-07b0c6559cfd9ece1
	status code: 400, request id: ee5371a8-8187-4078-bfec-7a5cb8760c89
Jun  8 08:21:21.939: INFO: Couldn't delete PD "aws://us-east-1a/vol-0e5d4661938a6eca2", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e5d4661938a6eca2 is currently attached to i-07b0c6559cfd9ece1
	status code: 400, request id: 0d81349a-4e1b-47ba-96d8-a24f052bcaeb
Jun  8 08:21:27.319: INFO: Successfully deleted PD "aws://us-east-1a/vol-0e5d4661938a6eca2".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  8 08:21:27.319: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-4264" for this suite.
... skipping 251 lines ...
Jun  8 08:20:45.334: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-9822-e2e-scjp7rf
STEP: creating a claim
Jun  8 08:20:45.378: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-vn68
STEP: Creating a pod to test exec-volume-test
Jun  8 08:20:45.507: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-vn68" in namespace "volume-9822" to be "Succeeded or Failed"
Jun  8 08:20:45.549: INFO: Pod "exec-volume-test-dynamicpv-vn68": Phase="Pending", Reason="", readiness=false. Elapsed: 41.881378ms
Jun  8 08:20:47.591: INFO: Pod "exec-volume-test-dynamicpv-vn68": Phase="Pending", Reason="", readiness=false. Elapsed: 2.084090161s
Jun  8 08:20:49.634: INFO: Pod "exec-volume-test-dynamicpv-vn68": Phase="Pending", Reason="", readiness=false. Elapsed: 4.126736768s
Jun  8 08:20:51.677: INFO: Pod "exec-volume-test-dynamicpv-vn68": Phase="Pending", Reason="", readiness=false. Elapsed: 6.169340102s
Jun  8 08:20:53.720: INFO: Pod "exec-volume-test-dynamicpv-vn68": Phase="Pending", Reason="", readiness=false. Elapsed: 8.212500382s
Jun  8 08:20:55.762: INFO: Pod "exec-volume-test-dynamicpv-vn68": Phase="Pending", Reason="", readiness=false. Elapsed: 10.254840623s
Jun  8 08:20:57.805: INFO: Pod "exec-volume-test-dynamicpv-vn68": Phase="Pending", Reason="", readiness=false. Elapsed: 12.298103963s
Jun  8 08:20:59.848: INFO: Pod "exec-volume-test-dynamicpv-vn68": Phase="Pending", Reason="", readiness=false. Elapsed: 14.34041817s
Jun  8 08:21:01.891: INFO: Pod "exec-volume-test-dynamicpv-vn68": Phase="Pending", Reason="", readiness=false. Elapsed: 16.384012576s
Jun  8 08:21:03.934: INFO: Pod "exec-volume-test-dynamicpv-vn68": Phase="Pending", Reason="", readiness=false. Elapsed: 18.426419913s
Jun  8 08:21:05.978: INFO: Pod "exec-volume-test-dynamicpv-vn68": Phase="Pending", Reason="", readiness=false. Elapsed: 20.470420765s
Jun  8 08:21:08.021: INFO: Pod "exec-volume-test-dynamicpv-vn68": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.51367385s
STEP: Saw pod success
Jun  8 08:21:08.021: INFO: Pod "exec-volume-test-dynamicpv-vn68" satisfied condition "Succeeded or Failed"
Jun  8 08:21:08.063: INFO: Trying to get logs from node ip-172-20-47-76.ec2.internal pod exec-volume-test-dynamicpv-vn68 container exec-container-dynamicpv-vn68: <nil>
STEP: delete the pod
Jun  8 08:21:08.154: INFO: Waiting for pod exec-volume-test-dynamicpv-vn68 to disappear
Jun  8 08:21:08.196: INFO: Pod exec-volume-test-dynamicpv-vn68 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-vn68
Jun  8 08:21:08.196: INFO: Deleting pod "exec-volume-test-dynamicpv-vn68" in namespace "volume-9822"
... skipping 99 lines ...
Jun  8 08:20:10.407: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3769-e2e-scdv5rl
STEP: creating a claim
Jun  8 08:20:10.451: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-gk6r
STEP: Creating a pod to test subpath
Jun  8 08:20:10.581: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-gk6r" in namespace "provisioning-3769" to be "Succeeded or Failed"
Jun  8 08:20:10.624: INFO: Pod "pod-subpath-test-dynamicpv-gk6r": Phase="Pending", Reason="", readiness=false. Elapsed: 42.538894ms
Jun  8 08:20:12.667: INFO: Pod "pod-subpath-test-dynamicpv-gk6r": Phase="Pending", Reason="", readiness=false. Elapsed: 2.085779524s
Jun  8 08:20:14.712: INFO: Pod "pod-subpath-test-dynamicpv-gk6r": Phase="Pending", Reason="", readiness=false. Elapsed: 4.130499527s
Jun  8 08:20:16.755: INFO: Pod "pod-subpath-test-dynamicpv-gk6r": Phase="Pending", Reason="", readiness=false. Elapsed: 6.174286878s
Jun  8 08:20:18.799: INFO: Pod "pod-subpath-test-dynamicpv-gk6r": Phase="Pending", Reason="", readiness=false. Elapsed: 8.217901568s
Jun  8 08:20:20.843: INFO: Pod "pod-subpath-test-dynamicpv-gk6r": Phase="Pending", Reason="", readiness=false. Elapsed: 10.261479102s
... skipping 11 lines ...
Jun  8 08:20:45.357: INFO: Pod "pod-subpath-test-dynamicpv-gk6r": Phase="Pending", Reason="", readiness=false. Elapsed: 34.775866257s
Jun  8 08:20:47.400: INFO: Pod "pod-subpath-test-dynamicpv-gk6r": Phase="Pending", Reason="", readiness=false. Elapsed: 36.818496706s
Jun  8 08:20:49.442: INFO: Pod "pod-subpath-test-dynamicpv-gk6r": Phase="Pending", Reason="", readiness=false. Elapsed: 38.861041696s
Jun  8 08:20:51.490: INFO: Pod "pod-subpath-test-dynamicpv-gk6r": Phase="Pending", Reason="", readiness=false. Elapsed: 40.909029756s
Jun  8 08:20:53.533: INFO: Pod "pod-subpath-test-dynamicpv-gk6r": Phase="Succeeded", Reason="", readiness=false. Elapsed: 42.951666866s
STEP: Saw pod success
Jun  8 08:20:53.533: INFO: Pod "pod-subpath-test-dynamicpv-gk6r" satisfied condition "Succeeded or Failed"
Jun  8 08:20:53.575: INFO: Trying to get logs from node ip-172-20-38-158.ec2.internal pod pod-subpath-test-dynamicpv-gk6r container test-container-volume-dynamicpv-gk6r: <nil>
STEP: delete the pod
Jun  8 08:20:53.667: INFO: Waiting for pod pod-subpath-test-dynamicpv-gk6r to disappear
Jun  8 08:20:53.709: INFO: Pod pod-subpath-test-dynamicpv-gk6r no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-gk6r
Jun  8 08:20:53.709: INFO: Deleting pod "pod-subpath-test-dynamicpv-gk6r" in namespace "provisioning-3769"
... skipping 76 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  8 08:20:21.586: 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.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  8 08:20:21.806: INFO: Creating resource for dynamic PV
Jun  8 08:20:21.806: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-9290-e2e-scsxtrx
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  8 08:20:28.113: INFO: Deleting pod "pod-c7a5a28e-cdfa-4f45-b737-21d2c9d10f72" in namespace "volumemode-9290"
Jun  8 08:20:28.158: INFO: Wait up to 5m0s for pod "pod-c7a5a28e-cdfa-4f45-b737-21d2c9d10f72" to be fully deleted
STEP: Deleting pvc
Jun  8 08:20:32.334: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comvrr7r"
Jun  8 08:20:32.378: INFO: Waiting up to 5m0s for PersistentVolume pvc-f821a2da-0b14-4c37-aebd-51b4ac5f36f3 to get deleted
Jun  8 08:20:32.421: INFO: PersistentVolume pvc-f821a2da-0b14-4c37-aebd-51b4ac5f36f3 found and phase=Released (42.683515ms)
... skipping 19 lines ...

• [SLOW TEST:76.561 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.YIoOihHZk/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.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ext4)] volumes
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (ext4)] volumes
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 7 lines ...
Jun  8 08:20:48.309: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-290-e2e-sc5qgq4
STEP: creating a claim
Jun  8 08:20:48.353: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-sxxp
STEP: Creating a pod to test exec-volume-test
Jun  8 08:20:48.488: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-sxxp" in namespace "volume-290" to be "Succeeded or Failed"
Jun  8 08:20:48.531: INFO: Pod "exec-volume-test-dynamicpv-sxxp": Phase="Pending", Reason="", readiness=false. Elapsed: 42.945055ms
Jun  8 08:20:50.575: INFO: Pod "exec-volume-test-dynamicpv-sxxp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.086404733s
Jun  8 08:20:52.620: INFO: Pod "exec-volume-test-dynamicpv-sxxp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.131924493s
Jun  8 08:20:54.664: INFO: Pod "exec-volume-test-dynamicpv-sxxp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.175424227s
Jun  8 08:20:56.708: INFO: Pod "exec-volume-test-dynamicpv-sxxp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.219609611s
Jun  8 08:20:58.752: INFO: Pod "exec-volume-test-dynamicpv-sxxp": Phase="Pending", Reason="", readiness=false. Elapsed: 10.263573277s
Jun  8 08:21:00.796: INFO: Pod "exec-volume-test-dynamicpv-sxxp": Phase="Pending", Reason="", readiness=false. Elapsed: 12.307880968s
Jun  8 08:21:02.840: INFO: Pod "exec-volume-test-dynamicpv-sxxp": Phase="Pending", Reason="", readiness=false. Elapsed: 14.352009806s
Jun  8 08:21:04.888: INFO: Pod "exec-volume-test-dynamicpv-sxxp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.399545622s
STEP: Saw pod success
Jun  8 08:21:04.888: INFO: Pod "exec-volume-test-dynamicpv-sxxp" satisfied condition "Succeeded or Failed"
Jun  8 08:21:04.931: INFO: Trying to get logs from node ip-172-20-38-158.ec2.internal pod exec-volume-test-dynamicpv-sxxp container exec-container-dynamicpv-sxxp: <nil>
STEP: delete the pod
Jun  8 08:21:05.023: INFO: Waiting for pod exec-volume-test-dynamicpv-sxxp to disappear
Jun  8 08:21:05.066: INFO: Pod exec-volume-test-dynamicpv-sxxp no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-sxxp
Jun  8 08:21:05.066: INFO: Deleting pod "exec-volume-test-dynamicpv-sxxp" in namespace "volume-290"
... skipping 68 lines ...
Jun  8 08:20:55.359: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5558-e2e-scl6gwh
STEP: creating a claim
Jun  8 08:20:55.404: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-jw6p
STEP: Creating a pod to test subpath
Jun  8 08:20:55.541: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-jw6p" in namespace "provisioning-5558" to be "Succeeded or Failed"
Jun  8 08:20:55.585: INFO: Pod "pod-subpath-test-dynamicpv-jw6p": Phase="Pending", Reason="", readiness=false. Elapsed: 43.501932ms
Jun  8 08:20:57.632: INFO: Pod "pod-subpath-test-dynamicpv-jw6p": Phase="Pending", Reason="", readiness=false. Elapsed: 2.090677061s
Jun  8 08:20:59.678: INFO: Pod "pod-subpath-test-dynamicpv-jw6p": Phase="Pending", Reason="", readiness=false. Elapsed: 4.136608486s
Jun  8 08:21:01.723: INFO: Pod "pod-subpath-test-dynamicpv-jw6p": Phase="Pending", Reason="", readiness=false. Elapsed: 6.182019884s
Jun  8 08:21:03.768: INFO: Pod "pod-subpath-test-dynamicpv-jw6p": Phase="Pending", Reason="", readiness=false. Elapsed: 8.226628726s
Jun  8 08:21:05.817: INFO: Pod "pod-subpath-test-dynamicpv-jw6p": Phase="Pending", Reason="", readiness=false. Elapsed: 10.276265222s
Jun  8 08:21:07.862: INFO: Pod "pod-subpath-test-dynamicpv-jw6p": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.320744898s
STEP: Saw pod success
Jun  8 08:21:07.862: INFO: Pod "pod-subpath-test-dynamicpv-jw6p" satisfied condition "Succeeded or Failed"
Jun  8 08:21:07.906: INFO: Trying to get logs from node ip-172-20-38-158.ec2.internal pod pod-subpath-test-dynamicpv-jw6p container test-container-subpath-dynamicpv-jw6p: <nil>
STEP: delete the pod
Jun  8 08:21:08.009: INFO: Waiting for pod pod-subpath-test-dynamicpv-jw6p to disappear
Jun  8 08:21:08.052: INFO: Pod pod-subpath-test-dynamicpv-jw6p no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-jw6p
Jun  8 08:21:08.053: INFO: Deleting pod "pod-subpath-test-dynamicpv-jw6p" in namespace "provisioning-5558"
... skipping 85 lines ...
Jun  8 08:21:44.078: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

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

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

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

    /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 136 lines ...
Jun  8 08:21:31.171: INFO: Waiting for pod aws-client to disappear
Jun  8 08:21:31.213: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun  8 08:21:31.213: INFO: Deleting PersistentVolumeClaim "pvc-dx6h9"
Jun  8 08:21:31.256: INFO: Deleting PersistentVolume "aws-gpcmq"
Jun  8 08:21:31.742: INFO: Couldn't delete PD "aws://us-east-1a/vol-0677b02f1c076494f", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0677b02f1c076494f is currently attached to i-05e5a3b84c6a72dab
	status code: 400, request id: d478f2f6-ef90-4f8f-ad9f-132bf197febc
Jun  8 08:21:37.211: INFO: Couldn't delete PD "aws://us-east-1a/vol-0677b02f1c076494f", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0677b02f1c076494f is currently attached to i-05e5a3b84c6a72dab
	status code: 400, request id: 1e68df3a-dec8-4ca2-9f5c-3ef7685804b6
Jun  8 08:21:42.714: INFO: Couldn't delete PD "aws://us-east-1a/vol-0677b02f1c076494f", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0677b02f1c076494f is currently attached to i-05e5a3b84c6a72dab
	status code: 400, request id: 21217f24-36df-41a4-b825-54280f55627a
Jun  8 08:21:48.128: INFO: Successfully deleted PD "aws://us-east-1a/vol-0677b02f1c076494f".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumes
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  8 08:21:48.128: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-9488" for this suite.
... skipping 45 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.YIoOihHZk/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.YIoOihHZk/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.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 213 lines ...
Jun  8 08:19:23.765: INFO: Creating resource for dynamic PV
Jun  8 08:19:23.765: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-9205-e2e-sc4nqsm
STEP: creating a claim
Jun  8 08:19:23.810: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun  8 08:19:23.948: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-sgbqd" in namespace "snapshotting-9205" to be "Succeeded or Failed"
Jun  8 08:19:23.991: INFO: Pod "pvc-snapshottable-tester-sgbqd": Phase="Pending", Reason="", readiness=false. Elapsed: 42.439896ms
Jun  8 08:19:26.036: INFO: Pod "pvc-snapshottable-tester-sgbqd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.087675092s
Jun  8 08:19:28.079: INFO: Pod "pvc-snapshottable-tester-sgbqd": Phase="Pending", Reason="", readiness=false. Elapsed: 4.13120896s
Jun  8 08:19:30.123: INFO: Pod "pvc-snapshottable-tester-sgbqd": Phase="Pending", Reason="", readiness=false. Elapsed: 6.175145452s
Jun  8 08:19:32.166: INFO: Pod "pvc-snapshottable-tester-sgbqd": Phase="Pending", Reason="", readiness=false. Elapsed: 8.217887437s
Jun  8 08:19:34.211: INFO: Pod "pvc-snapshottable-tester-sgbqd": Phase="Pending", Reason="", readiness=false. Elapsed: 10.262350482s
Jun  8 08:19:36.254: INFO: Pod "pvc-snapshottable-tester-sgbqd": Phase="Pending", Reason="", readiness=false. Elapsed: 12.305712808s
Jun  8 08:19:38.299: INFO: Pod "pvc-snapshottable-tester-sgbqd": Phase="Pending", Reason="", readiness=false. Elapsed: 14.350556571s
Jun  8 08:19:40.343: INFO: Pod "pvc-snapshottable-tester-sgbqd": Phase="Pending", Reason="", readiness=false. Elapsed: 16.394801529s
Jun  8 08:19:42.386: INFO: Pod "pvc-snapshottable-tester-sgbqd": Phase="Pending", Reason="", readiness=false. Elapsed: 18.437721598s
Jun  8 08:19:44.430: INFO: Pod "pvc-snapshottable-tester-sgbqd": Phase="Pending", Reason="", readiness=false. Elapsed: 20.481341809s
Jun  8 08:19:46.473: INFO: Pod "pvc-snapshottable-tester-sgbqd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.524808045s
STEP: Saw pod success
Jun  8 08:19:46.473: INFO: Pod "pvc-snapshottable-tester-sgbqd" satisfied condition "Succeeded or Failed"
Jun  8 08:19:46.561: INFO: Pod pvc-snapshottable-tester-sgbqd has the following logs: 
Jun  8 08:19:46.561: INFO: Deleting pod "pvc-snapshottable-tester-sgbqd" in namespace "snapshotting-9205"
Jun  8 08:19:46.608: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-sgbqd" to be fully deleted
Jun  8 08:19:46.652: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.com7dlw4] to have phase Bound
Jun  8 08:19:46.695: INFO: PersistentVolumeClaim ebs.csi.aws.com7dlw4 found and phase=Bound (42.78154ms)
STEP: [init] checking the claim
... skipping 45 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.YIoOihHZk/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  8 08:20:22.415: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-56mv2" in namespace "snapshotting-9205" to be "Succeeded or Failed"
Jun  8 08:20:22.457: INFO: Pod "pvc-snapshottable-data-tester-56mv2": Phase="Pending", Reason="", readiness=false. Elapsed: 42.573236ms
Jun  8 08:20:24.501: INFO: Pod "pvc-snapshottable-data-tester-56mv2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.085749434s
Jun  8 08:20:26.545: INFO: Pod "pvc-snapshottable-data-tester-56mv2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.129990311s
Jun  8 08:20:28.588: INFO: Pod "pvc-snapshottable-data-tester-56mv2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.172984231s
Jun  8 08:20:30.632: INFO: Pod "pvc-snapshottable-data-tester-56mv2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.217544824s
Jun  8 08:20:32.676: INFO: Pod "pvc-snapshottable-data-tester-56mv2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.260656162s
Jun  8 08:20:34.720: INFO: Pod "pvc-snapshottable-data-tester-56mv2": Phase="Pending", Reason="", readiness=false. Elapsed: 12.304638079s
Jun  8 08:20:36.763: INFO: Pod "pvc-snapshottable-data-tester-56mv2": Phase="Pending", Reason="", readiness=false. Elapsed: 14.348016434s
Jun  8 08:20:38.807: INFO: Pod "pvc-snapshottable-data-tester-56mv2": Phase="Pending", Reason="", readiness=false. Elapsed: 16.391646221s
Jun  8 08:20:40.851: INFO: Pod "pvc-snapshottable-data-tester-56mv2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.435676437s
STEP: Saw pod success
Jun  8 08:20:40.851: INFO: Pod "pvc-snapshottable-data-tester-56mv2" satisfied condition "Succeeded or Failed"
Jun  8 08:20:40.938: INFO: Pod pvc-snapshottable-data-tester-56mv2 has the following logs: 
Jun  8 08:20:40.938: INFO: Deleting pod "pvc-snapshottable-data-tester-56mv2" in namespace "snapshotting-9205"
Jun  8 08:20:40.985: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-56mv2" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun  8 08:21:03.202: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-9205 exec restored-pvc-tester-xlz99 --namespace=snapshotting-9205 -- cat /mnt/test/data'
... skipping 33 lines ...
Jun  8 08:21:49.725: INFO: At 2021-06-08 08:19:27 +0000 UTC - event for pvc-snapshottable-tester-sgbqd: {default-scheduler } Scheduled: Successfully assigned snapshotting-9205/pvc-snapshottable-tester-sgbqd to ip-172-20-39-149.ec2.internal
Jun  8 08:21:49.725: INFO: At 2021-06-08 08:19:36 +0000 UTC - event for pvc-snapshottable-tester-sgbqd: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-88acc389-3602-45ad-8b60-da6a3ade91a9" 
Jun  8 08:21:49.725: INFO: At 2021-06-08 08:19:44 +0000 UTC - event for pvc-snapshottable-tester-sgbqd: {kubelet ip-172-20-39-149.ec2.internal} Started: Started container volume-tester
Jun  8 08:21:49.725: INFO: At 2021-06-08 08:19:44 +0000 UTC - event for pvc-snapshottable-tester-sgbqd: {kubelet ip-172-20-39-149.ec2.internal} Created: Created container volume-tester
Jun  8 08:21:49.725: INFO: At 2021-06-08 08:19:44 +0000 UTC - event for pvc-snapshottable-tester-sgbqd: {kubelet ip-172-20-39-149.ec2.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" already present on machine
Jun  8 08:21:49.725: INFO: At 2021-06-08 08:19:46 +0000 UTC - event for snapshot-vr492: {snapshot-controller } CreatingSnapshot: Waiting for a snapshot snapshotting-9205/snapshot-vr492 to be created by the CSI driver.
Jun  8 08:21:49.725: INFO: At 2021-06-08 08:20:20 +0000 UTC - event for pre-provisioned-snapshot-f14bf506-ffec-4bdf-acbf-9d7cb8164cab: {snapshot-controller } SnapshotBindFailed: Snapshot failed to bind VolumeSnapshotContent, Operation cannot be fulfilled on volumesnapshotcontents.snapshot.storage.k8s.io "pre-provisioned-snapcontent-f14bf506-ffec-4bdf-acbf-9d7cb8164cab": the object has been modified; please apply your changes to the latest version and try again
Jun  8 08:21:49.725: INFO: At 2021-06-08 08:20:22 +0000 UTC - event for pvc-snapshottable-data-tester-56mv2: {default-scheduler } Scheduled: Successfully assigned snapshotting-9205/pvc-snapshottable-data-tester-56mv2 to ip-172-20-39-149.ec2.internal
Jun  8 08:21:49.725: INFO: At 2021-06-08 08:20:31 +0000 UTC - event for pvc-snapshottable-data-tester-56mv2: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-88acc389-3602-45ad-8b60-da6a3ade91a9" 
Jun  8 08:21:49.725: INFO: At 2021-06-08 08:20:39 +0000 UTC - event for pvc-snapshottable-data-tester-56mv2: {kubelet ip-172-20-39-149.ec2.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" already present on machine
Jun  8 08:21:49.725: INFO: At 2021-06-08 08:20:39 +0000 UTC - event for pvc-snapshottable-data-tester-56mv2: {kubelet ip-172-20-39-149.ec2.internal} Created: Created container volume-tester
Jun  8 08:21:49.725: INFO: At 2021-06-08 08:20:39 +0000 UTC - event for pvc-snapshottable-data-tester-56mv2: {kubelet ip-172-20-39-149.ec2.internal} Started: Started container volume-tester
Jun  8 08:21:49.725: INFO: At 2021-06-08 08:20:41 +0000 UTC - event for pvc-5qqfb: {persistentvolume-controller } ExternalProvisioning: waiting for a volume to be created, either by external provisioner "ebs.csi.aws.com" or manually created by system administrator
... skipping 217 lines ...
    /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:108
      
      /tmp/kops.YIoOihHZk/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.YIoOihHZk/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-9205 exec restored-pvc-tester-xlz99 --namespace=snapshotting-9205 -- 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-9205 exec restored-pvc-tester-xlz99 --namespace=snapshotting-9205 -- 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.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:602
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
... skipping 131 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.YIoOihHZk/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.YIoOihHZk/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.YIoOihHZk/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.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Distro debian doesn't support ntfs -- skipping

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.YIoOihHZk/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.YIoOihHZk/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.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 2 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  8 08:21:44.080: 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.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  8 08:21:44.299: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  8 08:21:44.910: INFO: Successfully created a new PD: "aws://us-east-1a/vol-00308af7dab7a52e5".
Jun  8 08:21:44.910: INFO: Creating resource for pre-provisioned PV
Jun  8 08:21:44.910: INFO: Creating PVC and PV
... skipping 3 lines ...
Jun  8 08:21:45.122: INFO: PersistentVolumeClaim pvc-9rc8c found but phase is Pending instead of Bound.
Jun  8 08:21:47.166: INFO: PersistentVolumeClaim pvc-9rc8c found but phase is Pending instead of Bound.
Jun  8 08:21:49.211: INFO: PersistentVolumeClaim pvc-9rc8c found and phase=Bound (4.133199954s)
Jun  8 08:21:49.211: INFO: Waiting up to 3m0s for PersistentVolume aws-d4sbr to have phase Bound
Jun  8 08:21:49.255: INFO: PersistentVolume aws-d4sbr found and phase=Bound (43.560224ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  8 08:21:51.519: INFO: Deleting pod "pod-7f634c6f-60ba-4cbc-aa5d-01d0ec35f13a" in namespace "volumemode-5387"
Jun  8 08:21:51.566: INFO: Wait up to 5m0s for pod "pod-7f634c6f-60ba-4cbc-aa5d-01d0ec35f13a" to be fully deleted
STEP: Deleting pv and pvc
Jun  8 08:22:01.654: INFO: Deleting PersistentVolumeClaim "pvc-9rc8c"
Jun  8 08:22:01.700: INFO: Deleting PersistentVolume "aws-d4sbr"
Jun  8 08:22:02.124: INFO: Couldn't delete PD "aws://us-east-1a/vol-00308af7dab7a52e5", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00308af7dab7a52e5 is currently attached to i-08504c879d133e5a6
	status code: 400, request id: 48b3e982-9955-42df-aea2-357058798af0
Jun  8 08:22:07.564: INFO: Couldn't delete PD "aws://us-east-1a/vol-00308af7dab7a52e5", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00308af7dab7a52e5 is currently attached to i-08504c879d133e5a6
	status code: 400, request id: 1ee7f1e5-b0c5-4583-9be2-5f6a16c2ec15
Jun  8 08:22:12.909: INFO: Successfully deleted PD "aws://us-east-1a/vol-00308af7dab7a52e5".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  8 08:22:12.909: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-5387" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.YIoOihHZk/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.YIoOihHZk/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
    /tmp/kops.YIoOihHZk/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.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  8 08:22:13.000: INFO: Driver ebs.csi.aws.com doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning
... skipping 17 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  8 08:21:29.027: 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.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  8 08:21:29.240: INFO: Creating resource for dynamic PV
Jun  8 08:21:29.240: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-8093-e2e-sc2l8z5
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  8 08:21:35.542: INFO: Deleting pod "pod-eff5464d-28cd-436d-bf54-983e69ae609e" in namespace "volumemode-8093"
Jun  8 08:21:35.588: INFO: Wait up to 5m0s for pod "pod-eff5464d-28cd-436d-bf54-983e69ae609e" to be fully deleted
STEP: Deleting pvc
Jun  8 08:21:41.760: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comg44mn"
Jun  8 08:21:41.803: INFO: Waiting up to 5m0s for PersistentVolume pvc-b03385bf-32f2-4e17-9803-45c3881803f4 to get deleted
Jun  8 08:21:41.849: INFO: PersistentVolume pvc-b03385bf-32f2-4e17-9803-45c3881803f4 found and phase=Released (45.986817ms)
... skipping 13 lines ...

• [SLOW TEST:48.264 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.YIoOihHZk/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.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 8 lines ...
Jun  8 08:21:48.434: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-167ljtpn
STEP: creating a claim
Jun  8 08:21:48.479: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-jmbz
STEP: Creating a pod to test subpath
Jun  8 08:21:48.617: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-jmbz" in namespace "provisioning-167" to be "Succeeded or Failed"
Jun  8 08:21:48.660: INFO: Pod "pod-subpath-test-dynamicpv-jmbz": Phase="Pending", Reason="", readiness=false. Elapsed: 42.620885ms
Jun  8 08:21:50.703: INFO: Pod "pod-subpath-test-dynamicpv-jmbz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.085780861s
Jun  8 08:21:52.755: INFO: Pod "pod-subpath-test-dynamicpv-jmbz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.137865793s
Jun  8 08:21:54.798: INFO: Pod "pod-subpath-test-dynamicpv-jmbz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.180523122s
Jun  8 08:21:56.840: INFO: Pod "pod-subpath-test-dynamicpv-jmbz": Phase="Pending", Reason="", readiness=false. Elapsed: 8.222843678s
Jun  8 08:21:58.884: INFO: Pod "pod-subpath-test-dynamicpv-jmbz": Phase="Pending", Reason="", readiness=false. Elapsed: 10.266735598s
Jun  8 08:22:00.928: INFO: Pod "pod-subpath-test-dynamicpv-jmbz": Phase="Pending", Reason="", readiness=false. Elapsed: 12.310316201s
Jun  8 08:22:02.971: INFO: Pod "pod-subpath-test-dynamicpv-jmbz": Phase="Pending", Reason="", readiness=false. Elapsed: 14.35332549s
Jun  8 08:22:05.013: INFO: Pod "pod-subpath-test-dynamicpv-jmbz": Phase="Pending", Reason="", readiness=false. Elapsed: 16.395665113s
Jun  8 08:22:07.055: INFO: Pod "pod-subpath-test-dynamicpv-jmbz": Phase="Pending", Reason="", readiness=false. Elapsed: 18.437998515s
Jun  8 08:22:09.101: INFO: Pod "pod-subpath-test-dynamicpv-jmbz": Phase="Pending", Reason="", readiness=false. Elapsed: 20.483529614s
Jun  8 08:22:11.143: INFO: Pod "pod-subpath-test-dynamicpv-jmbz": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.526037601s
STEP: Saw pod success
Jun  8 08:22:11.143: INFO: Pod "pod-subpath-test-dynamicpv-jmbz" satisfied condition "Succeeded or Failed"
Jun  8 08:22:11.185: INFO: Trying to get logs from node ip-172-20-58-151.ec2.internal pod pod-subpath-test-dynamicpv-jmbz container test-container-volume-dynamicpv-jmbz: <nil>
STEP: delete the pod
Jun  8 08:22:11.275: INFO: Waiting for pod pod-subpath-test-dynamicpv-jmbz to disappear
Jun  8 08:22:11.317: INFO: Pod pod-subpath-test-dynamicpv-jmbz no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-jmbz
Jun  8 08:22:11.317: INFO: Deleting pod "pod-subpath-test-dynamicpv-jmbz" in namespace "provisioning-167"
... skipping 405 lines ...
Jun  8 08:21:51.163: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-54925d8n7
STEP: creating a claim
Jun  8 08:21:51.206: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-dtzf
STEP: Creating a pod to test exec-volume-test
Jun  8 08:21:51.342: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-dtzf" in namespace "volume-5492" to be "Succeeded or Failed"
Jun  8 08:21:51.384: INFO: Pod "exec-volume-test-dynamicpv-dtzf": Phase="Pending", Reason="", readiness=false. Elapsed: 42.328883ms
Jun  8 08:21:53.430: INFO: Pod "exec-volume-test-dynamicpv-dtzf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.088432415s
Jun  8 08:21:55.473: INFO: Pod "exec-volume-test-dynamicpv-dtzf": Phase="Pending", Reason="", readiness=false. Elapsed: 4.131390784s
Jun  8 08:21:57.517: INFO: Pod "exec-volume-test-dynamicpv-dtzf": Phase="Pending", Reason="", readiness=false. Elapsed: 6.175292692s
Jun  8 08:21:59.560: INFO: Pod "exec-volume-test-dynamicpv-dtzf": Phase="Pending", Reason="", readiness=false. Elapsed: 8.217941306s
Jun  8 08:22:01.607: INFO: Pod "exec-volume-test-dynamicpv-dtzf": Phase="Pending", Reason="", readiness=false. Elapsed: 10.265285758s
Jun  8 08:22:03.650: INFO: Pod "exec-volume-test-dynamicpv-dtzf": Phase="Pending", Reason="", readiness=false. Elapsed: 12.30820789s
Jun  8 08:22:05.693: INFO: Pod "exec-volume-test-dynamicpv-dtzf": Phase="Pending", Reason="", readiness=false. Elapsed: 14.351112149s
Jun  8 08:22:07.737: INFO: Pod "exec-volume-test-dynamicpv-dtzf": Phase="Pending", Reason="", readiness=false. Elapsed: 16.394596877s
Jun  8 08:22:09.779: INFO: Pod "exec-volume-test-dynamicpv-dtzf": Phase="Pending", Reason="", readiness=false. Elapsed: 18.437230976s
Jun  8 08:22:11.822: INFO: Pod "exec-volume-test-dynamicpv-dtzf": Phase="Pending", Reason="", readiness=false. Elapsed: 20.479828286s
Jun  8 08:22:13.866: INFO: Pod "exec-volume-test-dynamicpv-dtzf": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.52410618s
STEP: Saw pod success
Jun  8 08:22:13.866: INFO: Pod "exec-volume-test-dynamicpv-dtzf" satisfied condition "Succeeded or Failed"
Jun  8 08:22:13.908: INFO: Trying to get logs from node ip-172-20-58-151.ec2.internal pod exec-volume-test-dynamicpv-dtzf container exec-container-dynamicpv-dtzf: <nil>
STEP: delete the pod
Jun  8 08:22:14.003: INFO: Waiting for pod exec-volume-test-dynamicpv-dtzf to disappear
Jun  8 08:22:14.046: INFO: Pod exec-volume-test-dynamicpv-dtzf no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-dtzf
Jun  8 08:22:14.046: INFO: Deleting pod "exec-volume-test-dynamicpv-dtzf" in namespace "volume-5492"
... skipping 53 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.YIoOihHZk/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.YIoOihHZk/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.YIoOihHZk/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.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 216 lines ...
Jun  8 08:21:53.610: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  8 08:21:54.344: INFO: Successfully created a new PD: "aws://us-east-1a/vol-032252c2802c352ba".
Jun  8 08:21:54.344: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-nrbw
STEP: Creating a pod to test exec-volume-test
Jun  8 08:21:54.390: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-nrbw" in namespace "volume-3000" to be "Succeeded or Failed"
Jun  8 08:21:54.433: INFO: Pod "exec-volume-test-inlinevolume-nrbw": Phase="Pending", Reason="", readiness=false. Elapsed: 42.708827ms
Jun  8 08:21:56.476: INFO: Pod "exec-volume-test-inlinevolume-nrbw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.086059491s
Jun  8 08:21:58.519: INFO: Pod "exec-volume-test-inlinevolume-nrbw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.12926389s
Jun  8 08:22:00.564: INFO: Pod "exec-volume-test-inlinevolume-nrbw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.173431101s
Jun  8 08:22:02.608: INFO: Pod "exec-volume-test-inlinevolume-nrbw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.217469362s
Jun  8 08:22:04.651: INFO: Pod "exec-volume-test-inlinevolume-nrbw": Phase="Pending", Reason="", readiness=false. Elapsed: 10.260634061s
... skipping 7 lines ...
Jun  8 08:22:21.002: INFO: Pod "exec-volume-test-inlinevolume-nrbw": Phase="Pending", Reason="", readiness=false. Elapsed: 26.611382897s
Jun  8 08:22:23.045: INFO: Pod "exec-volume-test-inlinevolume-nrbw": Phase="Pending", Reason="", readiness=false. Elapsed: 28.654535236s
Jun  8 08:22:25.088: INFO: Pod "exec-volume-test-inlinevolume-nrbw": Phase="Pending", Reason="", readiness=false. Elapsed: 30.697614003s
Jun  8 08:22:27.131: INFO: Pod "exec-volume-test-inlinevolume-nrbw": Phase="Pending", Reason="", readiness=false. Elapsed: 32.740658195s
Jun  8 08:22:29.174: INFO: Pod "exec-volume-test-inlinevolume-nrbw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.783779256s
STEP: Saw pod success
Jun  8 08:22:29.174: INFO: Pod "exec-volume-test-inlinevolume-nrbw" satisfied condition "Succeeded or Failed"
Jun  8 08:22:29.217: INFO: Trying to get logs from node ip-172-20-38-158.ec2.internal pod exec-volume-test-inlinevolume-nrbw container exec-container-inlinevolume-nrbw: <nil>
STEP: delete the pod
Jun  8 08:22:29.309: INFO: Waiting for pod exec-volume-test-inlinevolume-nrbw to disappear
Jun  8 08:22:29.352: INFO: Pod exec-volume-test-inlinevolume-nrbw no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-nrbw
Jun  8 08:22:29.352: INFO: Deleting pod "exec-volume-test-inlinevolume-nrbw" in namespace "volume-3000"
Jun  8 08:22:29.618: INFO: Couldn't delete PD "aws://us-east-1a/vol-032252c2802c352ba", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-032252c2802c352ba is currently attached to i-08504c879d133e5a6
	status code: 400, request id: e2ded645-581b-4368-aa1f-736f4bf6dc43
Jun  8 08:22:35.000: INFO: Couldn't delete PD "aws://us-east-1a/vol-032252c2802c352ba", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-032252c2802c352ba is currently attached to i-08504c879d133e5a6
	status code: 400, request id: 1850f012-01e0-4d85-8f63-a364149f31c3
Jun  8 08:22:40.427: INFO: Couldn't delete PD "aws://us-east-1a/vol-032252c2802c352ba", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-032252c2802c352ba is currently attached to i-08504c879d133e5a6
	status code: 400, request id: 6ccc9f34-7da8-4bbc-a563-a4514012e1e1
Jun  8 08:22:45.882: INFO: Successfully deleted PD "aws://us-east-1a/vol-032252c2802c352ba".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  8 08:22:45.882: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-3000" for this suite.
... skipping 271 lines ...

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

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

    /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 36 lines ...
Jun  8 08:21:48.554: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4228-e2e-scvlfsd
STEP: creating a claim
Jun  8 08:21:48.598: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-9j94
STEP: Creating a pod to test subpath
Jun  8 08:21:48.733: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-9j94" in namespace "provisioning-4228" to be "Succeeded or Failed"
Jun  8 08:21:48.779: INFO: Pod "pod-subpath-test-dynamicpv-9j94": Phase="Pending", Reason="", readiness=false. Elapsed: 45.893455ms
Jun  8 08:21:50.823: INFO: Pod "pod-subpath-test-dynamicpv-9j94": Phase="Pending", Reason="", readiness=false. Elapsed: 2.090637731s
Jun  8 08:21:52.878: INFO: Pod "pod-subpath-test-dynamicpv-9j94": Phase="Pending", Reason="", readiness=false. Elapsed: 4.145112355s
Jun  8 08:21:54.921: INFO: Pod "pod-subpath-test-dynamicpv-9j94": Phase="Pending", Reason="", readiness=false. Elapsed: 6.188512521s
Jun  8 08:21:56.965: INFO: Pod "pod-subpath-test-dynamicpv-9j94": Phase="Pending", Reason="", readiness=false. Elapsed: 8.232827248s
Jun  8 08:21:59.011: INFO: Pod "pod-subpath-test-dynamicpv-9j94": Phase="Pending", Reason="", readiness=false. Elapsed: 10.278543366s
... skipping 2 lines ...
Jun  8 08:22:05.144: INFO: Pod "pod-subpath-test-dynamicpv-9j94": Phase="Pending", Reason="", readiness=false. Elapsed: 16.411397368s
Jun  8 08:22:07.188: INFO: Pod "pod-subpath-test-dynamicpv-9j94": Phase="Pending", Reason="", readiness=false. Elapsed: 18.454957835s
Jun  8 08:22:09.232: INFO: Pod "pod-subpath-test-dynamicpv-9j94": Phase="Pending", Reason="", readiness=false. Elapsed: 20.499215609s
Jun  8 08:22:11.276: INFO: Pod "pod-subpath-test-dynamicpv-9j94": Phase="Pending", Reason="", readiness=false. Elapsed: 22.543686479s
Jun  8 08:22:13.326: INFO: Pod "pod-subpath-test-dynamicpv-9j94": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.593353878s
STEP: Saw pod success
Jun  8 08:22:13.326: INFO: Pod "pod-subpath-test-dynamicpv-9j94" satisfied condition "Succeeded or Failed"
Jun  8 08:22:13.375: INFO: Trying to get logs from node ip-172-20-39-149.ec2.internal pod pod-subpath-test-dynamicpv-9j94 container test-container-volume-dynamicpv-9j94: <nil>
STEP: delete the pod
Jun  8 08:22:13.477: INFO: Waiting for pod pod-subpath-test-dynamicpv-9j94 to disappear
Jun  8 08:22:13.519: INFO: Pod pod-subpath-test-dynamicpv-9j94 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-9j94
Jun  8 08:22:13.519: INFO: Deleting pod "pod-subpath-test-dynamicpv-9j94" in namespace "provisioning-4228"
... skipping 34 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.YIoOihHZk/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.YIoOihHZk/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.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 274 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  8 08:22:13.002: 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.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  8 08:22:13.220: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  8 08:22:13.220: INFO: Creating resource for dynamic PV
Jun  8 08:22:13.220: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-7501dhknn
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  8 08:22:19.548: INFO: Deleting pod "pod-b0a0da04-081d-4d5c-bf9e-55847c6f5e8f" in namespace "volumemode-7501"
Jun  8 08:22:19.593: INFO: Wait up to 5m0s for pod "pod-b0a0da04-081d-4d5c-bf9e-55847c6f5e8f" to be fully deleted
STEP: Deleting pvc
Jun  8 08:22:31.771: INFO: Deleting PersistentVolumeClaim "awskcp6g"
Jun  8 08:22:31.815: INFO: Waiting up to 5m0s for PersistentVolume pvc-c473fdef-db93-4935-b6ea-bae0ddfd88b6 to get deleted
Jun  8 08:22:31.858: INFO: PersistentVolume pvc-c473fdef-db93-4935-b6ea-bae0ddfd88b6 found and phase=Released (43.403283ms)
... skipping 12 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.YIoOihHZk/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.YIoOihHZk/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
    /tmp/kops.YIoOihHZk/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.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [sig-storage] Storage Policy Based Volume Provisioning [Feature:vsphere]
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  8 08:22:52.182: INFO: >>> kubeConfig: /root/.kube/config
... skipping 545 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.YIoOihHZk/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.YIoOihHZk/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.YIoOihHZk/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.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 96 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  8 08:22:32.199: 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.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  8 08:22:32.411: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  8 08:22:32.411: INFO: Creating resource for dynamic PV
Jun  8 08:22:32.411: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-9202tnzbk
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  8 08:22:38.710: INFO: Deleting pod "pod-e6f50211-f70c-48f7-bcea-794ccd6fa185" in namespace "volumemode-9202"
Jun  8 08:22:38.756: INFO: Wait up to 5m0s for pod "pod-e6f50211-f70c-48f7-bcea-794ccd6fa185" to be fully deleted
STEP: Deleting pvc
Jun  8 08:22:50.940: INFO: Deleting PersistentVolumeClaim "aws7x4lz"
Jun  8 08:22:50.989: INFO: Waiting up to 5m0s for PersistentVolume pvc-01498bf5-26e6-40ab-b9b7-a51e064e3724 to get deleted
Jun  8 08:22:51.032: INFO: PersistentVolume pvc-01498bf5-26e6-40ab-b9b7-a51e064e3724 found and phase=Released (42.746403ms)
... skipping 12 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.YIoOihHZk/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.YIoOihHZk/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (block volmode)] volumeMode
    /tmp/kops.YIoOihHZk/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.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  8 08:23:11.337: INFO: Driver "ebs.csi.aws.com" does not support volume type "InlineVolume" - skipping
[AfterEach] [Testpattern: Inline-volume (default fs)] subPath
... skipping 139 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  8 08:22:51.085: 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.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  8 08:22:51.308: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  8 08:22:51.927: INFO: Successfully created a new PD: "aws://us-east-1a/vol-0a6eb7d3151b3bf46".
Jun  8 08:22:51.927: INFO: Creating resource for pre-provisioned PV
Jun  8 08:22:51.927: INFO: Creating PVC and PV
... skipping 7 lines ...
Jun  8 08:23:00.320: INFO: PersistentVolumeClaim pvc-zl6qp found but phase is Pending instead of Bound.
Jun  8 08:23:02.364: INFO: PersistentVolumeClaim pvc-zl6qp found but phase is Pending instead of Bound.
Jun  8 08:23:04.408: INFO: PersistentVolumeClaim pvc-zl6qp found and phase=Bound (12.306828804s)
Jun  8 08:23:04.408: INFO: Waiting up to 3m0s for PersistentVolume aws-sbxz7 to have phase Bound
Jun  8 08:23:04.451: INFO: PersistentVolume aws-sbxz7 found and phase=Bound (42.756232ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  8 08:23:06.717: INFO: Deleting pod "pod-7c7b4b5b-6ae7-4a0d-ad46-a32b10c6e743" in namespace "volumemode-1404"
Jun  8 08:23:06.761: INFO: Wait up to 5m0s for pod "pod-7c7b4b5b-6ae7-4a0d-ad46-a32b10c6e743" to be fully deleted
STEP: Deleting pv and pvc
Jun  8 08:23:12.848: INFO: Deleting PersistentVolumeClaim "pvc-zl6qp"
Jun  8 08:23:12.892: INFO: Deleting PersistentVolume "aws-sbxz7"
Jun  8 08:23:13.221: INFO: Couldn't delete PD "aws://us-east-1a/vol-0a6eb7d3151b3bf46", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a6eb7d3151b3bf46 is currently attached to i-009378eb908db4e9b
	status code: 400, request id: df67f58d-9fe4-4c20-a132-86a22b3bf6f0
Jun  8 08:23:18.676: INFO: Couldn't delete PD "aws://us-east-1a/vol-0a6eb7d3151b3bf46", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a6eb7d3151b3bf46 is currently attached to i-009378eb908db4e9b
	status code: 400, request id: 4a7ed5d4-fb1a-4706-bac1-7ff4de60c4f0
Jun  8 08:23:24.198: INFO: Couldn't delete PD "aws://us-east-1a/vol-0a6eb7d3151b3bf46", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a6eb7d3151b3bf46 is currently attached to i-009378eb908db4e9b
	status code: 400, request id: 220c5111-f07a-4169-b58f-99aeaf079620
Jun  8 08:23:29.531: INFO: Successfully deleted PD "aws://us-east-1a/vol-0a6eb7d3151b3bf46".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  8 08:23:29.531: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-1404" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.YIoOihHZk/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.YIoOihHZk/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
    /tmp/kops.YIoOihHZk/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.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [sig-storage] Zone Support [Feature:vsphere]
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  8 08:23:29.620: INFO: >>> kubeConfig: /root/.kube/config
... skipping 216 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.YIoOihHZk/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.YIoOihHZk/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.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 217 lines ...
Jun  8 08:22:46.617: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1657xwsgx
STEP: creating a claim
Jun  8 08:22:46.665: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-4ckt
STEP: Creating a pod to test subpath
Jun  8 08:22:46.803: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-4ckt" in namespace "provisioning-1657" to be "Succeeded or Failed"
Jun  8 08:22:46.846: INFO: Pod "pod-subpath-test-dynamicpv-4ckt": Phase="Pending", Reason="", readiness=false. Elapsed: 43.028645ms
Jun  8 08:22:48.889: INFO: Pod "pod-subpath-test-dynamicpv-4ckt": Phase="Pending", Reason="", readiness=false. Elapsed: 2.086213371s
Jun  8 08:22:50.933: INFO: Pod "pod-subpath-test-dynamicpv-4ckt": Phase="Pending", Reason="", readiness=false. Elapsed: 4.130575757s
Jun  8 08:22:52.977: INFO: Pod "pod-subpath-test-dynamicpv-4ckt": Phase="Pending", Reason="", readiness=false. Elapsed: 6.174397231s
Jun  8 08:22:55.021: INFO: Pod "pod-subpath-test-dynamicpv-4ckt": Phase="Pending", Reason="", readiness=false. Elapsed: 8.217911444s
Jun  8 08:22:57.065: INFO: Pod "pod-subpath-test-dynamicpv-4ckt": Phase="Pending", Reason="", readiness=false. Elapsed: 10.26224994s
... skipping 2 lines ...
Jun  8 08:23:03.197: INFO: Pod "pod-subpath-test-dynamicpv-4ckt": Phase="Pending", Reason="", readiness=false. Elapsed: 16.394533022s
Jun  8 08:23:05.241: INFO: Pod "pod-subpath-test-dynamicpv-4ckt": Phase="Pending", Reason="", readiness=false. Elapsed: 18.438345155s
Jun  8 08:23:07.303: INFO: Pod "pod-subpath-test-dynamicpv-4ckt": Phase="Pending", Reason="", readiness=false. Elapsed: 20.500044013s
Jun  8 08:23:09.346: INFO: Pod "pod-subpath-test-dynamicpv-4ckt": Phase="Pending", Reason="", readiness=false. Elapsed: 22.543279474s
Jun  8 08:23:11.392: INFO: Pod "pod-subpath-test-dynamicpv-4ckt": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.589422149s
STEP: Saw pod success
Jun  8 08:23:11.392: INFO: Pod "pod-subpath-test-dynamicpv-4ckt" satisfied condition "Succeeded or Failed"
Jun  8 08:23:11.437: INFO: Trying to get logs from node ip-172-20-38-158.ec2.internal pod pod-subpath-test-dynamicpv-4ckt container test-container-subpath-dynamicpv-4ckt: <nil>
STEP: delete the pod
Jun  8 08:23:11.535: INFO: Waiting for pod pod-subpath-test-dynamicpv-4ckt to disappear
Jun  8 08:23:11.581: INFO: Pod pod-subpath-test-dynamicpv-4ckt no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-4ckt
Jun  8 08:23:11.581: INFO: Deleting pod "pod-subpath-test-dynamicpv-4ckt" in namespace "provisioning-1657"
... skipping 36 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.YIoOihHZk/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.YIoOihHZk/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.YIoOihHZk/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.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Distro debian doesn't support ntfs -- skipping

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 2 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  8 08:23:03.255: 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.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun  8 08:23:03.467: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  8 08:23:03.467: INFO: Creating resource for dynamic PV
Jun  8 08:23:03.467: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4780x2b67
STEP: creating a claim
Jun  8 08:23:03.509: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-m5vq
STEP: Checking for subpath error in container status
Jun  8 08:23:13.725: INFO: Deleting pod "pod-subpath-test-dynamicpv-m5vq" in namespace "provisioning-4780"
Jun  8 08:23:13.769: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-m5vq" to be fully deleted
STEP: Deleting pod
Jun  8 08:23:27.854: INFO: Deleting pod "pod-subpath-test-dynamicpv-m5vq" in namespace "provisioning-4780"
STEP: Deleting pvc
Jun  8 08:23:27.980: INFO: Deleting PersistentVolumeClaim "awsmm7fs"
... skipping 12 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.YIoOihHZk/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.YIoOihHZk/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath directory is outside the volume [Slow][LinuxOnly]
      /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ext3)] volumes
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  8 08:23:38.319: INFO: Driver aws doesn't support ext3 -- skipping
[AfterEach] [Testpattern: Dynamic PV (ext3)] volumes
... skipping 146 lines ...
Jun  8 08:22:49.444: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  8 08:22:49.972: INFO: Successfully created a new PD: "aws://us-east-1a/vol-09abeccfd9c0ee7c5".
Jun  8 08:22:49.972: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-6xzp
STEP: Creating a pod to test exec-volume-test
Jun  8 08:22:50.055: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-6xzp" in namespace "volume-1284" to be "Succeeded or Failed"
Jun  8 08:22:50.100: INFO: Pod "exec-volume-test-inlinevolume-6xzp": Phase="Pending", Reason="", readiness=false. Elapsed: 45.392056ms
Jun  8 08:22:52.144: INFO: Pod "exec-volume-test-inlinevolume-6xzp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.088744732s
Jun  8 08:22:54.188: INFO: Pod "exec-volume-test-inlinevolume-6xzp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.132645373s
Jun  8 08:22:56.232: INFO: Pod "exec-volume-test-inlinevolume-6xzp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.177184193s
Jun  8 08:22:58.277: INFO: Pod "exec-volume-test-inlinevolume-6xzp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.222024857s
Jun  8 08:23:00.321: INFO: Pod "exec-volume-test-inlinevolume-6xzp": Phase="Pending", Reason="", readiness=false. Elapsed: 10.265852052s
Jun  8 08:23:02.364: INFO: Pod "exec-volume-test-inlinevolume-6xzp": Phase="Pending", Reason="", readiness=false. Elapsed: 12.308947835s
Jun  8 08:23:04.408: INFO: Pod "exec-volume-test-inlinevolume-6xzp": Phase="Pending", Reason="", readiness=false. Elapsed: 14.353181279s
Jun  8 08:23:06.453: INFO: Pod "exec-volume-test-inlinevolume-6xzp": Phase="Pending", Reason="", readiness=false. Elapsed: 16.397924961s
Jun  8 08:23:08.497: INFO: Pod "exec-volume-test-inlinevolume-6xzp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.441941453s
STEP: Saw pod success
Jun  8 08:23:08.497: INFO: Pod "exec-volume-test-inlinevolume-6xzp" satisfied condition "Succeeded or Failed"
Jun  8 08:23:08.540: INFO: Trying to get logs from node ip-172-20-58-151.ec2.internal pod exec-volume-test-inlinevolume-6xzp container exec-container-inlinevolume-6xzp: <nil>
STEP: delete the pod
Jun  8 08:23:08.639: INFO: Waiting for pod exec-volume-test-inlinevolume-6xzp to disappear
Jun  8 08:23:08.682: INFO: Pod exec-volume-test-inlinevolume-6xzp no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-6xzp
Jun  8 08:23:08.682: INFO: Deleting pod "exec-volume-test-inlinevolume-6xzp" in namespace "volume-1284"
Jun  8 08:23:09.129: INFO: Couldn't delete PD "aws://us-east-1a/vol-09abeccfd9c0ee7c5", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-09abeccfd9c0ee7c5 is currently attached to i-07b0c6559cfd9ece1
	status code: 400, request id: 0f484a12-286d-4b8a-a314-32f97b6c3cd8
Jun  8 08:23:14.461: INFO: Couldn't delete PD "aws://us-east-1a/vol-09abeccfd9c0ee7c5", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-09abeccfd9c0ee7c5 is currently attached to i-07b0c6559cfd9ece1
	status code: 400, request id: 9d038d10-9af0-443d-8651-6b3986f4a839
Jun  8 08:23:19.914: INFO: Couldn't delete PD "aws://us-east-1a/vol-09abeccfd9c0ee7c5", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-09abeccfd9c0ee7c5 is currently attached to i-07b0c6559cfd9ece1
	status code: 400, request id: 39f2affd-c341-4346-b7ec-7169aea0158c
Jun  8 08:23:25.350: INFO: Couldn't delete PD "aws://us-east-1a/vol-09abeccfd9c0ee7c5", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-09abeccfd9c0ee7c5 is currently attached to i-07b0c6559cfd9ece1
	status code: 400, request id: 494070b2-0976-43da-8050-cc682b5a18f4
Jun  8 08:23:30.813: INFO: Couldn't delete PD "aws://us-east-1a/vol-09abeccfd9c0ee7c5", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-09abeccfd9c0ee7c5 is currently attached to i-07b0c6559cfd9ece1
	status code: 400, request id: 515a2817-dc28-4b4a-8d48-9704b2e05c1b
Jun  8 08:23:36.214: INFO: Couldn't delete PD "aws://us-east-1a/vol-09abeccfd9c0ee7c5", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-09abeccfd9c0ee7c5 is currently attached to i-07b0c6559cfd9ece1
	status code: 400, request id: 8818ee37-c99c-48a3-b016-403f3e5823a9
Jun  8 08:23:41.535: INFO: Successfully deleted PD "aws://us-east-1a/vol-09abeccfd9c0ee7c5".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  8 08:23:41.535: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-1284" for this suite.
... skipping 172 lines ...
Jun  8 08:21:41.278: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-6293-e2e-scjlhs5      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-6293    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-6293-e2e-scjlhs5,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-6293    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-6293-e2e-scjlhs5,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-6293    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-6293-e2e-scjlhs5,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-6293-e2e-scjlhs5    7ff0b6fd-1cb9-42ca-984d-271cf58de0b1 7893 0 2021-06-08 08:21:41 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-08 08:21:41 +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-n797d pvc- provisioning-6293  19665112-7987-4f0e-a00b-ddafc296bc63 7898 0 2021-06-08 08:21:41 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-08 08:21:41 +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-6293-e2e-scjlhs5,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-0b826464-3c8e-4058-8829-6ae351ec3baa in namespace provisioning-6293
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun  8 08:21:57.769: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-xvslr" in namespace "provisioning-6293" to be "Succeeded or Failed"
Jun  8 08:21:57.814: INFO: Pod "pvc-volume-tester-writer-xvslr": Phase="Pending", Reason="", readiness=false. Elapsed: 44.61804ms
Jun  8 08:21:59.858: INFO: Pod "pvc-volume-tester-writer-xvslr": Phase="Pending", Reason="", readiness=false. Elapsed: 2.089050654s
Jun  8 08:22:01.901: INFO: Pod "pvc-volume-tester-writer-xvslr": Phase="Pending", Reason="", readiness=false. Elapsed: 4.131916663s
Jun  8 08:22:03.944: INFO: Pod "pvc-volume-tester-writer-xvslr": Phase="Pending", Reason="", readiness=false. Elapsed: 6.175210682s
Jun  8 08:22:05.989: INFO: Pod "pvc-volume-tester-writer-xvslr": Phase="Pending", Reason="", readiness=false. Elapsed: 8.220139392s
Jun  8 08:22:08.033: INFO: Pod "pvc-volume-tester-writer-xvslr": Phase="Pending", Reason="", readiness=false. Elapsed: 10.26386174s
... skipping 23 lines ...
Jun  8 08:22:57.095: INFO: Pod "pvc-volume-tester-writer-xvslr": Phase="Pending", Reason="", readiness=false. Elapsed: 59.325707098s
Jun  8 08:22:59.139: INFO: Pod "pvc-volume-tester-writer-xvslr": Phase="Pending", Reason="", readiness=false. Elapsed: 1m1.369676265s
Jun  8 08:23:01.182: INFO: Pod "pvc-volume-tester-writer-xvslr": Phase="Pending", Reason="", readiness=false. Elapsed: 1m3.412811095s
Jun  8 08:23:03.227: INFO: Pod "pvc-volume-tester-writer-xvslr": Phase="Pending", Reason="", readiness=false. Elapsed: 1m5.457671121s
Jun  8 08:23:05.270: INFO: Pod "pvc-volume-tester-writer-xvslr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m7.500994257s
STEP: Saw pod success
Jun  8 08:23:05.270: INFO: Pod "pvc-volume-tester-writer-xvslr" satisfied condition "Succeeded or Failed"
Jun  8 08:23:05.358: INFO: Pod pvc-volume-tester-writer-xvslr has the following logs: 
Jun  8 08:23:05.358: INFO: Deleting pod "pvc-volume-tester-writer-xvslr" in namespace "provisioning-6293"
Jun  8 08:23:05.409: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-xvslr" 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-39-149.ec2.internal"
Jun  8 08:23:05.602: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-c886s" in namespace "provisioning-6293" to be "Succeeded or Failed"
Jun  8 08:23:05.645: INFO: Pod "pvc-volume-tester-reader-c886s": Phase="Pending", Reason="", readiness=false. Elapsed: 42.837976ms
Jun  8 08:23:07.690: INFO: Pod "pvc-volume-tester-reader-c886s": Phase="Pending", Reason="", readiness=false. Elapsed: 2.088518971s
Jun  8 08:23:09.734: INFO: Pod "pvc-volume-tester-reader-c886s": Phase="Pending", Reason="", readiness=false. Elapsed: 4.132387126s
Jun  8 08:23:11.778: INFO: Pod "pvc-volume-tester-reader-c886s": Phase="Pending", Reason="", readiness=false. Elapsed: 6.176427767s
Jun  8 08:23:13.822: INFO: Pod "pvc-volume-tester-reader-c886s": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.219698569s
STEP: Saw pod success
Jun  8 08:23:13.822: INFO: Pod "pvc-volume-tester-reader-c886s" satisfied condition "Succeeded or Failed"
Jun  8 08:23:13.914: INFO: Pod pvc-volume-tester-reader-c886s has the following logs: hello world

Jun  8 08:23:13.914: INFO: Deleting pod "pvc-volume-tester-reader-c886s" in namespace "provisioning-6293"
Jun  8 08:23:13.963: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-c886s" to be fully deleted
Jun  8 08:23:14.006: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-n797d] to have phase Bound
Jun  8 08:23:14.052: INFO: PersistentVolumeClaim pvc-n797d found and phase=Bound (45.663131ms)
... skipping 79 lines ...
Jun  8 08:23:02.272: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-493148m8r
STEP: creating a claim
Jun  8 08:23:02.315: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-hdlz
STEP: Creating a pod to test subpath
Jun  8 08:23:02.445: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-hdlz" in namespace "provisioning-4931" to be "Succeeded or Failed"
Jun  8 08:23:02.488: INFO: Pod "pod-subpath-test-dynamicpv-hdlz": Phase="Pending", Reason="", readiness=false. Elapsed: 43.007371ms
Jun  8 08:23:04.531: INFO: Pod "pod-subpath-test-dynamicpv-hdlz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.085675089s
Jun  8 08:23:06.574: INFO: Pod "pod-subpath-test-dynamicpv-hdlz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.129320938s
Jun  8 08:23:08.620: INFO: Pod "pod-subpath-test-dynamicpv-hdlz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.174751896s
Jun  8 08:23:10.662: INFO: Pod "pod-subpath-test-dynamicpv-hdlz": Phase="Pending", Reason="", readiness=false. Elapsed: 8.217293671s
Jun  8 08:23:12.706: INFO: Pod "pod-subpath-test-dynamicpv-hdlz": Phase="Pending", Reason="", readiness=false. Elapsed: 10.261353652s
... skipping 3 lines ...
Jun  8 08:23:20.878: INFO: Pod "pod-subpath-test-dynamicpv-hdlz": Phase="Pending", Reason="", readiness=false. Elapsed: 18.432738034s
Jun  8 08:23:22.921: INFO: Pod "pod-subpath-test-dynamicpv-hdlz": Phase="Pending", Reason="", readiness=false. Elapsed: 20.475681284s
Jun  8 08:23:24.964: INFO: Pod "pod-subpath-test-dynamicpv-hdlz": Phase="Pending", Reason="", readiness=false. Elapsed: 22.519254015s
Jun  8 08:23:27.007: INFO: Pod "pod-subpath-test-dynamicpv-hdlz": Phase="Pending", Reason="", readiness=false. Elapsed: 24.562143962s
Jun  8 08:23:29.050: INFO: Pod "pod-subpath-test-dynamicpv-hdlz": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.604887121s
STEP: Saw pod success
Jun  8 08:23:29.050: INFO: Pod "pod-subpath-test-dynamicpv-hdlz" satisfied condition "Succeeded or Failed"
Jun  8 08:23:29.092: INFO: Trying to get logs from node ip-172-20-39-149.ec2.internal pod pod-subpath-test-dynamicpv-hdlz container test-container-subpath-dynamicpv-hdlz: <nil>
STEP: delete the pod
Jun  8 08:23:29.188: INFO: Waiting for pod pod-subpath-test-dynamicpv-hdlz to disappear
Jun  8 08:23:29.230: INFO: Pod pod-subpath-test-dynamicpv-hdlz no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-hdlz
Jun  8 08:23:29.230: INFO: Deleting pod "pod-subpath-test-dynamicpv-hdlz" in namespace "provisioning-4931"
... skipping 35 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.YIoOihHZk/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.YIoOihHZk/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.YIoOihHZk/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.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

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

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

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

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.YIoOihHZk/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.YIoOihHZk/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.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 70 lines ...
Jun  8 08:22:51.992: INFO: Creating resource for dynamic PV
Jun  8 08:22:51.993: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6794kkd6j
STEP: creating a claim
Jun  8 08:22:52.036: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-6794
Jun  8 08:22:52.185: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-6794" in namespace "provisioning-6794" to be "Succeeded or Failed"
Jun  8 08:22:52.228: INFO: Pod "volume-prep-provisioning-6794": Phase="Pending", Reason="", readiness=false. Elapsed: 42.864724ms
Jun  8 08:22:54.271: INFO: Pod "volume-prep-provisioning-6794": Phase="Pending", Reason="", readiness=false. Elapsed: 2.085940267s
Jun  8 08:22:56.314: INFO: Pod "volume-prep-provisioning-6794": Phase="Pending", Reason="", readiness=false. Elapsed: 4.128890423s
Jun  8 08:22:58.359: INFO: Pod "volume-prep-provisioning-6794": Phase="Pending", Reason="", readiness=false. Elapsed: 6.173633479s
Jun  8 08:23:00.403: INFO: Pod "volume-prep-provisioning-6794": Phase="Pending", Reason="", readiness=false. Elapsed: 8.21776486s
Jun  8 08:23:02.451: INFO: Pod "volume-prep-provisioning-6794": Phase="Pending", Reason="", readiness=false. Elapsed: 10.266000047s
Jun  8 08:23:04.495: INFO: Pod "volume-prep-provisioning-6794": Phase="Pending", Reason="", readiness=false. Elapsed: 12.309275071s
Jun  8 08:23:06.537: INFO: Pod "volume-prep-provisioning-6794": Phase="Pending", Reason="", readiness=false. Elapsed: 14.351892989s
Jun  8 08:23:08.580: INFO: Pod "volume-prep-provisioning-6794": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.39449229s
STEP: Saw pod success
Jun  8 08:23:08.580: INFO: Pod "volume-prep-provisioning-6794" satisfied condition "Succeeded or Failed"
Jun  8 08:23:08.580: INFO: Deleting pod "volume-prep-provisioning-6794" in namespace "provisioning-6794"
Jun  8 08:23:08.626: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-6794" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-lftz
STEP: Checking for subpath error in container status
Jun  8 08:23:42.800: INFO: Deleting pod "pod-subpath-test-dynamicpv-lftz" in namespace "provisioning-6794"
Jun  8 08:23:42.849: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-lftz" to be fully deleted
STEP: Deleting pod
Jun  8 08:23:42.891: INFO: Deleting pod "pod-subpath-test-dynamicpv-lftz" in namespace "provisioning-6794"
STEP: Deleting pvc
Jun  8 08:23:43.017: INFO: Deleting PersistentVolumeClaim "awsw4hdz"
... skipping 358 lines ...
STEP: Deleting pod hostexec-ip-172-20-58-151.ec2.internal-x2c5b in namespace volumemode-1618
Jun  8 08:23:56.138: INFO: Deleting pod "pod-8737e503-1ca3-42e5-8ffe-5f11efbed850" in namespace "volumemode-1618"
Jun  8 08:23:56.186: INFO: Wait up to 5m0s for pod "pod-8737e503-1ca3-42e5-8ffe-5f11efbed850" to be fully deleted
STEP: Deleting pv and pvc
Jun  8 08:24:10.272: INFO: Deleting PersistentVolumeClaim "pvc-ft627"
Jun  8 08:24:10.316: INFO: Deleting PersistentVolume "aws-jk4bh"
Jun  8 08:24:10.582: INFO: Couldn't delete PD "aws://us-east-1a/vol-0c962834310477830", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c962834310477830 is currently attached to i-07b0c6559cfd9ece1
	status code: 400, request id: 8a64197f-7680-4d8c-85c0-5fa2e7dcfaec
Jun  8 08:24:15.962: INFO: Successfully deleted PD "aws://us-east-1a/vol-0c962834310477830".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  8 08:24:15.962: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-1618" for this suite.
... skipping 217 lines ...
Jun  8 08:24:00.673: INFO: Waiting for pod aws-client to disappear
Jun  8 08:24:00.716: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun  8 08:24:00.716: INFO: Deleting PersistentVolumeClaim "pvc-kx7zs"
Jun  8 08:24:00.759: INFO: Deleting PersistentVolume "aws-jfrs6"
Jun  8 08:24:01.059: INFO: Couldn't delete PD "aws://us-east-1a/vol-06a09bb534d0a965e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-06a09bb534d0a965e is currently attached to i-07b0c6559cfd9ece1
	status code: 400, request id: c8b0798d-d799-4351-81aa-aba0e8ed8afb
Jun  8 08:24:06.510: INFO: Couldn't delete PD "aws://us-east-1a/vol-06a09bb534d0a965e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-06a09bb534d0a965e is currently attached to i-07b0c6559cfd9ece1
	status code: 400, request id: 5484b4d3-1c0f-4349-ab97-6befd74211ac
Jun  8 08:24:11.861: INFO: Couldn't delete PD "aws://us-east-1a/vol-06a09bb534d0a965e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-06a09bb534d0a965e is currently attached to i-07b0c6559cfd9ece1
	status code: 400, request id: 783cfd6c-6edf-4744-800f-9633a22f0160
Jun  8 08:24:17.282: INFO: Successfully deleted PD "aws://us-east-1a/vol-06a09bb534d0a965e".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  8 08:24:17.282: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-4053" for this suite.
... skipping 184 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  8 08:23:41.626: 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.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun  8 08:23:41.841: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  8 08:23:41.841: INFO: Creating resource for dynamic PV
Jun  8 08:23:41.841: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9004946h7
STEP: creating a claim
Jun  8 08:23:41.886: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-7c88
STEP: Checking for subpath error in container status
Jun  8 08:23:58.106: INFO: Deleting pod "pod-subpath-test-dynamicpv-7c88" in namespace "provisioning-9004"
Jun  8 08:23:58.150: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-7c88" to be fully deleted
STEP: Deleting pod
Jun  8 08:24:12.237: INFO: Deleting pod "pod-subpath-test-dynamicpv-7c88" in namespace "provisioning-9004"
STEP: Deleting pvc
Jun  8 08:24:12.365: INFO: Deleting PersistentVolumeClaim "aws6kfhh"
... skipping 13 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.YIoOihHZk/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.YIoOihHZk/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.YIoOihHZk/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.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [sig-storage] vsphere statefulset [Feature:vsphere]
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  8 08:24:27.724: INFO: >>> kubeConfig: /root/.kube/config
... skipping 220 lines ...
Jun  8 08:23:36.969: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-4537xg2qk
STEP: creating a claim
Jun  8 08:23:37.012: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-8fns
STEP: Creating a pod to test exec-volume-test
Jun  8 08:23:37.142: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-8fns" in namespace "volume-4537" to be "Succeeded or Failed"
Jun  8 08:23:37.185: INFO: Pod "exec-volume-test-dynamicpv-8fns": Phase="Pending", Reason="", readiness=false. Elapsed: 42.527425ms
Jun  8 08:23:39.233: INFO: Pod "exec-volume-test-dynamicpv-8fns": Phase="Pending", Reason="", readiness=false. Elapsed: 2.090634651s
Jun  8 08:23:41.275: INFO: Pod "exec-volume-test-dynamicpv-8fns": Phase="Pending", Reason="", readiness=false. Elapsed: 4.133136526s
Jun  8 08:23:43.318: INFO: Pod "exec-volume-test-dynamicpv-8fns": Phase="Pending", Reason="", readiness=false. Elapsed: 6.176150492s
Jun  8 08:23:45.363: INFO: Pod "exec-volume-test-dynamicpv-8fns": Phase="Pending", Reason="", readiness=false. Elapsed: 8.220997113s
Jun  8 08:23:47.406: INFO: Pod "exec-volume-test-dynamicpv-8fns": Phase="Pending", Reason="", readiness=false. Elapsed: 10.264039444s
Jun  8 08:23:49.450: INFO: Pod "exec-volume-test-dynamicpv-8fns": Phase="Pending", Reason="", readiness=false. Elapsed: 12.307392194s
Jun  8 08:23:51.494: INFO: Pod "exec-volume-test-dynamicpv-8fns": Phase="Pending", Reason="", readiness=false. Elapsed: 14.352004949s
Jun  8 08:23:53.537: INFO: Pod "exec-volume-test-dynamicpv-8fns": Phase="Pending", Reason="", readiness=false. Elapsed: 16.395062013s
Jun  8 08:23:55.580: INFO: Pod "exec-volume-test-dynamicpv-8fns": Phase="Pending", Reason="", readiness=false. Elapsed: 18.438103918s
Jun  8 08:23:57.623: INFO: Pod "exec-volume-test-dynamicpv-8fns": Phase="Pending", Reason="", readiness=false. Elapsed: 20.48074815s
Jun  8 08:23:59.666: INFO: Pod "exec-volume-test-dynamicpv-8fns": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.523871419s
STEP: Saw pod success
Jun  8 08:23:59.666: INFO: Pod "exec-volume-test-dynamicpv-8fns" satisfied condition "Succeeded or Failed"
Jun  8 08:23:59.708: INFO: Trying to get logs from node ip-172-20-58-151.ec2.internal pod exec-volume-test-dynamicpv-8fns container exec-container-dynamicpv-8fns: <nil>
STEP: delete the pod
Jun  8 08:23:59.821: INFO: Waiting for pod exec-volume-test-dynamicpv-8fns to disappear
Jun  8 08:23:59.866: INFO: Pod exec-volume-test-dynamicpv-8fns no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-8fns
Jun  8 08:23:59.866: INFO: Deleting pod "exec-volume-test-dynamicpv-8fns" in namespace "volume-4537"
... skipping 162 lines ...
Jun  8 08:23:34.211: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-9920-e2e-scx2xcx
STEP: creating a claim
Jun  8 08:23:34.256: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-jbdr
STEP: Creating a pod to test exec-volume-test
Jun  8 08:23:34.391: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-jbdr" in namespace "volume-9920" to be "Succeeded or Failed"
Jun  8 08:23:34.433: INFO: Pod "exec-volume-test-dynamicpv-jbdr": Phase="Pending", Reason="", readiness=false. Elapsed: 41.911903ms
Jun  8 08:23:36.476: INFO: Pod "exec-volume-test-dynamicpv-jbdr": Phase="Pending", Reason="", readiness=false. Elapsed: 2.085143475s
Jun  8 08:23:38.520: INFO: Pod "exec-volume-test-dynamicpv-jbdr": Phase="Pending", Reason="", readiness=false. Elapsed: 4.129034416s
Jun  8 08:23:40.563: INFO: Pod "exec-volume-test-dynamicpv-jbdr": Phase="Pending", Reason="", readiness=false. Elapsed: 6.172611203s
Jun  8 08:23:42.606: INFO: Pod "exec-volume-test-dynamicpv-jbdr": Phase="Pending", Reason="", readiness=false. Elapsed: 8.215398138s
Jun  8 08:23:44.650: INFO: Pod "exec-volume-test-dynamicpv-jbdr": Phase="Pending", Reason="", readiness=false. Elapsed: 10.259044989s
Jun  8 08:23:46.694: INFO: Pod "exec-volume-test-dynamicpv-jbdr": Phase="Pending", Reason="", readiness=false. Elapsed: 12.303519098s
Jun  8 08:23:48.754: INFO: Pod "exec-volume-test-dynamicpv-jbdr": Phase="Pending", Reason="", readiness=false. Elapsed: 14.362851522s
Jun  8 08:23:50.796: INFO: Pod "exec-volume-test-dynamicpv-jbdr": Phase="Pending", Reason="", readiness=false. Elapsed: 16.405378123s
Jun  8 08:23:52.838: INFO: Pod "exec-volume-test-dynamicpv-jbdr": Phase="Pending", Reason="", readiness=false. Elapsed: 18.447607737s
Jun  8 08:23:54.881: INFO: Pod "exec-volume-test-dynamicpv-jbdr": Phase="Pending", Reason="", readiness=false. Elapsed: 20.490523988s
Jun  8 08:23:56.925: INFO: Pod "exec-volume-test-dynamicpv-jbdr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.534063555s
STEP: Saw pod success
Jun  8 08:23:56.925: INFO: Pod "exec-volume-test-dynamicpv-jbdr" satisfied condition "Succeeded or Failed"
Jun  8 08:23:56.967: INFO: Trying to get logs from node ip-172-20-39-149.ec2.internal pod exec-volume-test-dynamicpv-jbdr container exec-container-dynamicpv-jbdr: <nil>
STEP: delete the pod
Jun  8 08:23:57.057: INFO: Waiting for pod exec-volume-test-dynamicpv-jbdr to disappear
Jun  8 08:23:57.099: INFO: Pod exec-volume-test-dynamicpv-jbdr no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-jbdr
Jun  8 08:23:57.099: INFO: Deleting pod "exec-volume-test-dynamicpv-jbdr" in namespace "volume-9920"
... skipping 265 lines ...
Jun  8 08:23:50.296: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4065j7szm
STEP: creating a claim
Jun  8 08:23:50.339: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-lmfx
STEP: Creating a pod to test subpath
Jun  8 08:23:50.473: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-lmfx" in namespace "provisioning-4065" to be "Succeeded or Failed"
Jun  8 08:23:50.518: INFO: Pod "pod-subpath-test-dynamicpv-lmfx": Phase="Pending", Reason="", readiness=false. Elapsed: 44.73608ms
Jun  8 08:23:52.561: INFO: Pod "pod-subpath-test-dynamicpv-lmfx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.088027199s
Jun  8 08:23:54.605: INFO: Pod "pod-subpath-test-dynamicpv-lmfx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.131308115s
Jun  8 08:23:56.648: INFO: Pod "pod-subpath-test-dynamicpv-lmfx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.175073398s
Jun  8 08:23:58.692: INFO: Pod "pod-subpath-test-dynamicpv-lmfx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.218488777s
Jun  8 08:24:00.736: INFO: Pod "pod-subpath-test-dynamicpv-lmfx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.262741264s
... skipping 10 lines ...
Jun  8 08:24:23.226: INFO: Pod "pod-subpath-test-dynamicpv-lmfx": Phase="Pending", Reason="", readiness=false. Elapsed: 32.752502367s
Jun  8 08:24:25.270: INFO: Pod "pod-subpath-test-dynamicpv-lmfx": Phase="Pending", Reason="", readiness=false. Elapsed: 34.796795256s
Jun  8 08:24:27.314: INFO: Pod "pod-subpath-test-dynamicpv-lmfx": Phase="Pending", Reason="", readiness=false. Elapsed: 36.840099272s
Jun  8 08:24:29.357: INFO: Pod "pod-subpath-test-dynamicpv-lmfx": Phase="Pending", Reason="", readiness=false. Elapsed: 38.883465613s
Jun  8 08:24:31.400: INFO: Pod "pod-subpath-test-dynamicpv-lmfx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 40.92652511s
STEP: Saw pod success
Jun  8 08:24:31.400: INFO: Pod "pod-subpath-test-dynamicpv-lmfx" satisfied condition "Succeeded or Failed"
Jun  8 08:24:31.443: INFO: Trying to get logs from node ip-172-20-58-151.ec2.internal pod pod-subpath-test-dynamicpv-lmfx container test-container-subpath-dynamicpv-lmfx: <nil>
STEP: delete the pod
Jun  8 08:24:31.540: INFO: Waiting for pod pod-subpath-test-dynamicpv-lmfx to disappear
Jun  8 08:24:31.582: INFO: Pod pod-subpath-test-dynamicpv-lmfx no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-lmfx
Jun  8 08:24:31.582: INFO: Deleting pod "pod-subpath-test-dynamicpv-lmfx" in namespace "provisioning-4065"
... skipping 258 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  8 08:24:17.690: 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.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun  8 08:24:17.905: INFO: Creating resource for dynamic PV
Jun  8 08:24:17.906: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8342-e2e-sc2dktz
STEP: creating a claim
Jun  8 08:24:17.949: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-fcd9
STEP: Checking for subpath error in container status
Jun  8 08:24:42.169: INFO: Deleting pod "pod-subpath-test-dynamicpv-fcd9" in namespace "provisioning-8342"
Jun  8 08:24:42.215: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-fcd9" to be fully deleted
STEP: Deleting pod
Jun  8 08:24:54.302: INFO: Deleting pod "pod-subpath-test-dynamicpv-fcd9" in namespace "provisioning-8342"
STEP: Deleting pvc
Jun  8 08:24:54.432: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com6c2fl"
... skipping 12 lines ...

• [SLOW TEST:57.137 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.YIoOihHZk/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.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 52 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.YIoOihHZk/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.YIoOihHZk/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.YIoOihHZk/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.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 213 lines ...
Jun  8 08:25:11.823: INFO: Waiting for pod aws-client to disappear
Jun  8 08:25:11.865: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun  8 08:25:11.866: INFO: Deleting PersistentVolumeClaim "pvc-r2jpq"
Jun  8 08:25:11.910: INFO: Deleting PersistentVolume "aws-bnrlp"
Jun  8 08:25:12.364: INFO: Couldn't delete PD "aws://us-east-1a/vol-0cab853c70c7360ab", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0cab853c70c7360ab is currently attached to i-05e5a3b84c6a72dab
	status code: 400, request id: 38065bb2-e048-42cd-b250-40729bc941c8
Jun  8 08:25:17.733: INFO: Couldn't delete PD "aws://us-east-1a/vol-0cab853c70c7360ab", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0cab853c70c7360ab is currently attached to i-05e5a3b84c6a72dab
	status code: 400, request id: cd4c0be8-2403-4273-82fb-ab6c373c4b51
Jun  8 08:25:23.148: INFO: Successfully deleted PD "aws://us-east-1a/vol-0cab853c70c7360ab".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  8 08:25:23.148: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8382" for this suite.
... skipping 22 lines ...
Jun  8 08:22:47.121: INFO: Creating resource for dynamic PV
Jun  8 08:22:47.121: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-6351-e2e-scvqfsw
STEP: creating a claim
Jun  8 08:22:47.165: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun  8 08:22:47.297: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-99qmm" in namespace "snapshotting-6351" to be "Succeeded or Failed"
Jun  8 08:22:47.340: INFO: Pod "pvc-snapshottable-tester-99qmm": Phase="Pending", Reason="", readiness=false. Elapsed: 42.775614ms
Jun  8 08:22:49.383: INFO: Pod "pvc-snapshottable-tester-99qmm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.085848913s
Jun  8 08:22:51.428: INFO: Pod "pvc-snapshottable-tester-99qmm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.131251597s
Jun  8 08:22:53.471: INFO: Pod "pvc-snapshottable-tester-99qmm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.174569054s
Jun  8 08:22:55.520: INFO: Pod "pvc-snapshottable-tester-99qmm": Phase="Pending", Reason="", readiness=false. Elapsed: 8.222808204s
Jun  8 08:22:57.565: INFO: Pod "pvc-snapshottable-tester-99qmm": Phase="Pending", Reason="", readiness=false. Elapsed: 10.268427676s
Jun  8 08:22:59.610: INFO: Pod "pvc-snapshottable-tester-99qmm": Phase="Pending", Reason="", readiness=false. Elapsed: 12.312734348s
Jun  8 08:23:01.654: INFO: Pod "pvc-snapshottable-tester-99qmm": Phase="Pending", Reason="", readiness=false. Elapsed: 14.357533926s
Jun  8 08:23:03.697: INFO: Pod "pvc-snapshottable-tester-99qmm": Phase="Pending", Reason="", readiness=false. Elapsed: 16.40042604s
Jun  8 08:23:05.742: INFO: Pod "pvc-snapshottable-tester-99qmm": Phase="Pending", Reason="", readiness=false. Elapsed: 18.445380438s
Jun  8 08:23:07.787: INFO: Pod "pvc-snapshottable-tester-99qmm": Phase="Pending", Reason="", readiness=false. Elapsed: 20.489904795s
Jun  8 08:23:09.830: INFO: Pod "pvc-snapshottable-tester-99qmm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.533656657s
STEP: Saw pod success
Jun  8 08:23:09.831: INFO: Pod "pvc-snapshottable-tester-99qmm" satisfied condition "Succeeded or Failed"
Jun  8 08:23:09.926: INFO: Pod pvc-snapshottable-tester-99qmm has the following logs: 
Jun  8 08:23:09.927: INFO: Deleting pod "pvc-snapshottable-tester-99qmm" in namespace "snapshotting-6351"
Jun  8 08:23:09.974: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-99qmm" to be fully deleted
Jun  8 08:23:10.019: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comwhng2] to have phase Bound
Jun  8 08:23:10.062: INFO: PersistentVolumeClaim ebs.csi.aws.comwhng2 found and phase=Bound (42.791099ms)
STEP: [init] checking the claim
... skipping 54 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.YIoOihHZk/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  8 08:24:04.143: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-mbnw7" in namespace "snapshotting-6351" to be "Succeeded or Failed"
Jun  8 08:24:04.186: INFO: Pod "pvc-snapshottable-data-tester-mbnw7": Phase="Pending", Reason="", readiness=false. Elapsed: 43.085202ms
Jun  8 08:24:06.232: INFO: Pod "pvc-snapshottable-data-tester-mbnw7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.089491296s
Jun  8 08:24:08.277: INFO: Pod "pvc-snapshottable-data-tester-mbnw7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.133968606s
Jun  8 08:24:10.321: INFO: Pod "pvc-snapshottable-data-tester-mbnw7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.177707132s
Jun  8 08:24:12.364: INFO: Pod "pvc-snapshottable-data-tester-mbnw7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.220951693s
Jun  8 08:24:14.407: INFO: Pod "pvc-snapshottable-data-tester-mbnw7": Phase="Pending", Reason="", readiness=false. Elapsed: 10.264217984s
Jun  8 08:24:16.450: INFO: Pod "pvc-snapshottable-data-tester-mbnw7": Phase="Pending", Reason="", readiness=false. Elapsed: 12.307099009s
Jun  8 08:24:18.494: INFO: Pod "pvc-snapshottable-data-tester-mbnw7": Phase="Pending", Reason="", readiness=false. Elapsed: 14.351044119s
Jun  8 08:24:20.539: INFO: Pod "pvc-snapshottable-data-tester-mbnw7": Phase="Pending", Reason="", readiness=false. Elapsed: 16.396616411s
Jun  8 08:24:22.584: INFO: Pod "pvc-snapshottable-data-tester-mbnw7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.44138011s
STEP: Saw pod success
Jun  8 08:24:22.584: INFO: Pod "pvc-snapshottable-data-tester-mbnw7" satisfied condition "Succeeded or Failed"
Jun  8 08:24:22.671: INFO: Pod pvc-snapshottable-data-tester-mbnw7 has the following logs: 
Jun  8 08:24:22.671: INFO: Deleting pod "pvc-snapshottable-data-tester-mbnw7" in namespace "snapshotting-6351"
Jun  8 08:24:22.724: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-mbnw7" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun  8 08:24:34.943: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-6351 exec restored-pvc-tester-m44br --namespace=snapshotting-6351 -- cat /mnt/test/data'
... skipping 208 lines ...
Jun  8 08:25:16.363: INFO: Pod aws-client still exists
Jun  8 08:25:18.319: INFO: Waiting for pod aws-client to disappear
Jun  8 08:25:18.362: INFO: Pod aws-client still exists
Jun  8 08:25:20.320: INFO: Waiting for pod aws-client to disappear
Jun  8 08:25:20.362: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun  8 08:25:20.761: INFO: Couldn't delete PD "aws://us-east-1a/vol-0c341f9dbfb9feb19", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c341f9dbfb9feb19 is currently attached to i-08504c879d133e5a6
	status code: 400, request id: 60b5c498-56a1-4e6c-89c3-8f26874cc177
Jun  8 08:25:26.198: INFO: Couldn't delete PD "aws://us-east-1a/vol-0c341f9dbfb9feb19", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c341f9dbfb9feb19 is currently attached to i-08504c879d133e5a6
	status code: 400, request id: efe87dff-d8eb-46c5-9410-e1da07ecf68c
Jun  8 08:25:31.574: INFO: Successfully deleted PD "aws://us-east-1a/vol-0c341f9dbfb9feb19".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  8 08:25:31.574: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8966" for this suite.
... skipping 127 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.YIoOihHZk/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.YIoOihHZk/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.YIoOihHZk/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.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 11 lines ...
Jun  8 08:25:01.375: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-5706-e2e-sc789kd
STEP: creating a claim
Jun  8 08:25:01.418: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Jun  8 08:25:01.507: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun  8 08:25:01.592: INFO: Error updating pvc ebs.csi.aws.com97k9d: PersistentVolumeClaim "ebs.csi.aws.com97k9d" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5706-e2e-sc789kd",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun  8 08:25:31.766: INFO: Error updating pvc ebs.csi.aws.com97k9d: PersistentVolumeClaim "ebs.csi.aws.com97k9d" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 298 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  8 08:24:28.043: 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.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun  8 08:24:28.269: INFO: Creating resource for dynamic PV
Jun  8 08:24:28.269: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-375-e2e-scdqs9n
STEP: creating a claim
Jun  8 08:24:28.312: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-w9k2
STEP: Checking for subpath error in container status
Jun  8 08:24:52.537: INFO: Deleting pod "pod-subpath-test-dynamicpv-w9k2" in namespace "provisioning-375"
Jun  8 08:24:52.582: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-w9k2" to be fully deleted
STEP: Deleting pod
Jun  8 08:25:00.668: INFO: Deleting pod "pod-subpath-test-dynamicpv-w9k2" in namespace "provisioning-375"
STEP: Deleting pvc
Jun  8 08:25:00.796: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com5v9ff"
... skipping 15 lines ...

• [SLOW TEST:68.286 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath directory is outside the volume [Slow][LinuxOnly]
    /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)(allowExpansion)][Feature:Windows] volume-expand
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  8 08:25:36.331: INFO: Driver ebs.csi.aws.com doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)(allowExpansion)][Feature:Windows] volume-expand
... skipping 106 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.YIoOihHZk/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.YIoOihHZk/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.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 53 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  8 08:25:23.239: 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.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun  8 08:25:23.453: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  8 08:25:23.453: INFO: Creating resource for dynamic PV
Jun  8 08:25:23.453: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-64927tch9
STEP: creating a claim
Jun  8 08:25:23.496: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-ltrx
STEP: Checking for subpath error in container status
Jun  8 08:25:35.712: INFO: Deleting pod "pod-subpath-test-dynamicpv-ltrx" in namespace "provisioning-6492"
Jun  8 08:25:35.755: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-ltrx" to be fully deleted
STEP: Deleting pod
Jun  8 08:25:41.842: INFO: Deleting pod "pod-subpath-test-dynamicpv-ltrx" in namespace "provisioning-6492"
STEP: Deleting pvc
Jun  8 08:25:41.969: INFO: Deleting PersistentVolumeClaim "awsf6mlx"
... skipping 12 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.YIoOihHZk/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.YIoOihHZk/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath file is outside the volume [Slow][LinuxOnly]
      /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 79 lines ...
Jun  8 08:25:26.051: INFO: Creating resource for dynamic PV
Jun  8 08:25:26.051: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-2031-e2e-sc7hb6m
STEP: creating a claim
STEP: Expanding non-expandable pvc
Jun  8 08:25:26.192: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun  8 08:25:26.282: INFO: Error updating pvc ebs.csi.aws.com56p4q: PersistentVolumeClaim "ebs.csi.aws.com56p4q" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2031-e2e-sc7hb6m",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun  8 08:25:56.455: INFO: Error updating pvc ebs.csi.aws.com56p4q: PersistentVolumeClaim "ebs.csi.aws.com56p4q" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 275 lines ...
Jun  8 08:23:58.496: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-5271xnqmh      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-5271    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-5271xnqmh,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-5271    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-5271xnqmh,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-5271    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-5271xnqmh,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-5271xnqmh    4921d60f-c950-4ed1-ac3f-68024332c1f2 11552 0 2021-06-08 08:23:58 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-08 08:23:58 +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-v8wtr pvc- provisioning-5271  9201738d-286f-4a6c-a2d4-14f1be3c4e33 11554 0 2021-06-08 08:23:58 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-08 08:23:58 +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-5271xnqmh,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-475c205c-cddf-4bdf-bbab-167d10e43636 in namespace provisioning-5271
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun  8 08:24:12.969: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-nrh8w" in namespace "provisioning-5271" to be "Succeeded or Failed"
Jun  8 08:24:13.011: INFO: Pod "pvc-volume-tester-writer-nrh8w": Phase="Pending", Reason="", readiness=false. Elapsed: 41.909345ms
Jun  8 08:24:15.054: INFO: Pod "pvc-volume-tester-writer-nrh8w": Phase="Pending", Reason="", readiness=false. Elapsed: 2.084100636s
Jun  8 08:24:17.096: INFO: Pod "pvc-volume-tester-writer-nrh8w": Phase="Pending", Reason="", readiness=false. Elapsed: 4.12668434s
Jun  8 08:24:19.139: INFO: Pod "pvc-volume-tester-writer-nrh8w": Phase="Pending", Reason="", readiness=false. Elapsed: 6.169093447s
Jun  8 08:24:21.182: INFO: Pod "pvc-volume-tester-writer-nrh8w": Phase="Pending", Reason="", readiness=false. Elapsed: 8.212189148s
Jun  8 08:24:23.224: INFO: Pod "pvc-volume-tester-writer-nrh8w": Phase="Pending", Reason="", readiness=false. Elapsed: 10.254470277s
... skipping 23 lines ...
Jun  8 08:25:12.260: INFO: Pod "pvc-volume-tester-writer-nrh8w": Phase="Pending", Reason="", readiness=false. Elapsed: 59.29049656s
Jun  8 08:25:14.307: INFO: Pod "pvc-volume-tester-writer-nrh8w": Phase="Pending", Reason="", readiness=false. Elapsed: 1m1.337666946s
Jun  8 08:25:16.350: INFO: Pod "pvc-volume-tester-writer-nrh8w": Phase="Pending", Reason="", readiness=false. Elapsed: 1m3.380287936s
Jun  8 08:25:18.393: INFO: Pod "pvc-volume-tester-writer-nrh8w": Phase="Pending", Reason="", readiness=false. Elapsed: 1m5.423287759s
Jun  8 08:25:20.437: INFO: Pod "pvc-volume-tester-writer-nrh8w": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m7.467711823s
STEP: Saw pod success
Jun  8 08:25:20.437: INFO: Pod "pvc-volume-tester-writer-nrh8w" satisfied condition "Succeeded or Failed"
Jun  8 08:25:20.525: INFO: Pod pvc-volume-tester-writer-nrh8w has the following logs: 
Jun  8 08:25:20.525: INFO: Deleting pod "pvc-volume-tester-writer-nrh8w" in namespace "provisioning-5271"
Jun  8 08:25:20.578: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-nrh8w" 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-58-151.ec2.internal"
Jun  8 08:25:20.756: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-vjf9l" in namespace "provisioning-5271" to be "Succeeded or Failed"
Jun  8 08:25:20.798: INFO: Pod "pvc-volume-tester-reader-vjf9l": Phase="Pending", Reason="", readiness=false. Elapsed: 41.912716ms
Jun  8 08:25:22.841: INFO: Pod "pvc-volume-tester-reader-vjf9l": Phase="Pending", Reason="", readiness=false. Elapsed: 2.084396169s
Jun  8 08:25:24.883: INFO: Pod "pvc-volume-tester-reader-vjf9l": Phase="Pending", Reason="", readiness=false. Elapsed: 4.127002141s
Jun  8 08:25:26.926: INFO: Pod "pvc-volume-tester-reader-vjf9l": Phase="Pending", Reason="", readiness=false. Elapsed: 6.169488657s
Jun  8 08:25:28.969: INFO: Pod "pvc-volume-tester-reader-vjf9l": Phase="Pending", Reason="", readiness=false. Elapsed: 8.212158456s
Jun  8 08:25:31.012: INFO: Pod "pvc-volume-tester-reader-vjf9l": Phase="Pending", Reason="", readiness=false. Elapsed: 10.255888538s
Jun  8 08:25:33.056: INFO: Pod "pvc-volume-tester-reader-vjf9l": Phase="Pending", Reason="", readiness=false. Elapsed: 12.299446186s
Jun  8 08:25:35.099: INFO: Pod "pvc-volume-tester-reader-vjf9l": Phase="Pending", Reason="", readiness=false. Elapsed: 14.342488269s
Jun  8 08:25:37.145: INFO: Pod "pvc-volume-tester-reader-vjf9l": Phase="Pending", Reason="", readiness=false. Elapsed: 16.388285009s
Jun  8 08:25:39.188: INFO: Pod "pvc-volume-tester-reader-vjf9l": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.431569563s
STEP: Saw pod success
Jun  8 08:25:39.188: INFO: Pod "pvc-volume-tester-reader-vjf9l" satisfied condition "Succeeded or Failed"
Jun  8 08:25:39.274: INFO: Pod pvc-volume-tester-reader-vjf9l has the following logs: hello world

Jun  8 08:25:39.274: INFO: Deleting pod "pvc-volume-tester-reader-vjf9l" in namespace "provisioning-5271"
Jun  8 08:25:39.323: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-vjf9l" to be fully deleted
Jun  8 08:25:39.367: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-v8wtr] to have phase Bound
Jun  8 08:25:39.409: INFO: PersistentVolumeClaim pvc-v8wtr found and phase=Bound (41.823856ms)
... skipping 234 lines ...
Jun  8 08:25:47.556: INFO: PersistentVolumeClaim pvc-nb6w6 found but phase is Pending instead of Bound.
Jun  8 08:25:49.599: INFO: PersistentVolumeClaim pvc-nb6w6 found and phase=Bound (12.307934662s)
Jun  8 08:25:49.599: INFO: Waiting up to 3m0s for PersistentVolume aws-pwt29 to have phase Bound
Jun  8 08:25:49.642: INFO: PersistentVolume aws-pwt29 found and phase=Bound (42.836376ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-pvb4
STEP: Creating a pod to test exec-volume-test
Jun  8 08:25:49.773: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-pvb4" in namespace "volume-3893" to be "Succeeded or Failed"
Jun  8 08:25:49.816: INFO: Pod "exec-volume-test-preprovisionedpv-pvb4": Phase="Pending", Reason="", readiness=false. Elapsed: 42.796539ms
Jun  8 08:25:51.860: INFO: Pod "exec-volume-test-preprovisionedpv-pvb4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.086785069s
Jun  8 08:25:53.905: INFO: Pod "exec-volume-test-preprovisionedpv-pvb4": Phase="Pending", Reason="", readiness=false. Elapsed: 4.131715722s
Jun  8 08:25:55.950: INFO: Pod "exec-volume-test-preprovisionedpv-pvb4": Phase="Pending", Reason="", readiness=false. Elapsed: 6.176959836s
Jun  8 08:25:57.993: INFO: Pod "exec-volume-test-preprovisionedpv-pvb4": Phase="Pending", Reason="", readiness=false. Elapsed: 8.220461845s
Jun  8 08:26:00.038: INFO: Pod "exec-volume-test-preprovisionedpv-pvb4": Phase="Pending", Reason="", readiness=false. Elapsed: 10.264638406s
... skipping 7 lines ...
Jun  8 08:26:16.390: INFO: Pod "exec-volume-test-preprovisionedpv-pvb4": Phase="Pending", Reason="", readiness=false. Elapsed: 26.617529616s
Jun  8 08:26:18.436: INFO: Pod "exec-volume-test-preprovisionedpv-pvb4": Phase="Pending", Reason="", readiness=false. Elapsed: 28.662825255s
Jun  8 08:26:20.479: INFO: Pod "exec-volume-test-preprovisionedpv-pvb4": Phase="Pending", Reason="", readiness=false. Elapsed: 30.706362127s
Jun  8 08:26:22.524: INFO: Pod "exec-volume-test-preprovisionedpv-pvb4": Phase="Pending", Reason="", readiness=false. Elapsed: 32.750795352s
Jun  8 08:26:24.568: INFO: Pod "exec-volume-test-preprovisionedpv-pvb4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.795469403s
STEP: Saw pod success
Jun  8 08:26:24.568: INFO: Pod "exec-volume-test-preprovisionedpv-pvb4" satisfied condition "Succeeded or Failed"
Jun  8 08:26:24.612: INFO: Trying to get logs from node ip-172-20-58-151.ec2.internal pod exec-volume-test-preprovisionedpv-pvb4 container exec-container-preprovisionedpv-pvb4: <nil>
STEP: delete the pod
Jun  8 08:26:24.705: INFO: Waiting for pod exec-volume-test-preprovisionedpv-pvb4 to disappear
Jun  8 08:26:24.750: INFO: Pod exec-volume-test-preprovisionedpv-pvb4 no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-pvb4
Jun  8 08:26:24.750: INFO: Deleting pod "exec-volume-test-preprovisionedpv-pvb4" in namespace "volume-3893"
STEP: Deleting pv and pvc
Jun  8 08:26:24.792: INFO: Deleting PersistentVolumeClaim "pvc-nb6w6"
Jun  8 08:26:24.836: INFO: Deleting PersistentVolume "aws-pwt29"
Jun  8 08:26:25.119: INFO: Couldn't delete PD "aws://us-east-1a/vol-0f8b6f9113fa5a268", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f8b6f9113fa5a268 is currently attached to i-07b0c6559cfd9ece1
	status code: 400, request id: 291aa641-3b87-4663-b8a7-0ebf877d1ffa
Jun  8 08:26:30.492: INFO: Couldn't delete PD "aws://us-east-1a/vol-0f8b6f9113fa5a268", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f8b6f9113fa5a268 is currently attached to i-07b0c6559cfd9ece1
	status code: 400, request id: 866a8624-9544-46ee-b687-58841ab68a29
Jun  8 08:26:35.939: INFO: Couldn't delete PD "aws://us-east-1a/vol-0f8b6f9113fa5a268", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f8b6f9113fa5a268 is currently attached to i-07b0c6559cfd9ece1
	status code: 400, request id: aea6fbab-b4df-4a04-b2a9-4cace53de3d1
Jun  8 08:26:41.327: INFO: Successfully deleted PD "aws://us-east-1a/vol-0f8b6f9113fa5a268".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  8 08:26:41.328: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-3893" for this suite.
... skipping 207 lines ...
Jun  8 08:23:30.773: INFO: Creating resource for dynamic PV
Jun  8 08:23:30.773: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-4828-e2e-scmf8n2
STEP: creating a claim
Jun  8 08:23:30.818: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun  8 08:23:30.949: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-2rtrq" in namespace "snapshotting-4828" to be "Succeeded or Failed"
Jun  8 08:23:30.991: INFO: Pod "pvc-snapshottable-tester-2rtrq": Phase="Pending", Reason="", readiness=false. Elapsed: 42.792708ms
Jun  8 08:23:33.034: INFO: Pod "pvc-snapshottable-tester-2rtrq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.085754319s
Jun  8 08:23:35.079: INFO: Pod "pvc-snapshottable-tester-2rtrq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.130551404s
Jun  8 08:23:37.123: INFO: Pod "pvc-snapshottable-tester-2rtrq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.174193818s
Jun  8 08:23:39.168: INFO: Pod "pvc-snapshottable-tester-2rtrq": Phase="Pending", Reason="", readiness=false. Elapsed: 8.219455162s
Jun  8 08:23:41.212: INFO: Pod "pvc-snapshottable-tester-2rtrq": Phase="Pending", Reason="", readiness=false. Elapsed: 10.263428722s
Jun  8 08:23:43.255: INFO: Pod "pvc-snapshottable-tester-2rtrq": Phase="Pending", Reason="", readiness=false. Elapsed: 12.306660312s
Jun  8 08:23:45.302: INFO: Pod "pvc-snapshottable-tester-2rtrq": Phase="Pending", Reason="", readiness=false. Elapsed: 14.353127088s
Jun  8 08:23:47.348: INFO: Pod "pvc-snapshottable-tester-2rtrq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.399155779s
STEP: Saw pod success
Jun  8 08:23:47.348: INFO: Pod "pvc-snapshottable-tester-2rtrq" satisfied condition "Succeeded or Failed"
Jun  8 08:23:47.437: INFO: Pod pvc-snapshottable-tester-2rtrq has the following logs: 
Jun  8 08:23:47.437: INFO: Deleting pod "pvc-snapshottable-tester-2rtrq" in namespace "snapshotting-4828"
Jun  8 08:23:47.484: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-2rtrq" to be fully deleted
Jun  8 08:23:47.528: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.com8wtm6] to have phase Bound
Jun  8 08:23:47.572: INFO: PersistentVolumeClaim ebs.csi.aws.com8wtm6 found and phase=Bound (44.001391ms)
STEP: [init] checking the claim
... skipping 47 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.YIoOihHZk/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  8 08:25:03.689: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-dgrqq" in namespace "snapshotting-4828" to be "Succeeded or Failed"
Jun  8 08:25:03.732: INFO: Pod "pvc-snapshottable-data-tester-dgrqq": Phase="Pending", Reason="", readiness=false. Elapsed: 42.746389ms
Jun  8 08:25:05.775: INFO: Pod "pvc-snapshottable-data-tester-dgrqq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.086453208s
Jun  8 08:25:07.820: INFO: Pod "pvc-snapshottable-data-tester-dgrqq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.130766731s
Jun  8 08:25:09.863: INFO: Pod "pvc-snapshottable-data-tester-dgrqq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.174254284s
Jun  8 08:25:11.912: INFO: Pod "pvc-snapshottable-data-tester-dgrqq": Phase="Pending", Reason="", readiness=false. Elapsed: 8.222940909s
Jun  8 08:25:13.955: INFO: Pod "pvc-snapshottable-data-tester-dgrqq": Phase="Pending", Reason="", readiness=false. Elapsed: 10.265992842s
... skipping 7 lines ...
Jun  8 08:25:30.305: INFO: Pod "pvc-snapshottable-data-tester-dgrqq": Phase="Pending", Reason="", readiness=false. Elapsed: 26.615898119s
Jun  8 08:25:32.351: INFO: Pod "pvc-snapshottable-data-tester-dgrqq": Phase="Pending", Reason="", readiness=false. Elapsed: 28.661713955s
Jun  8 08:25:34.395: INFO: Pod "pvc-snapshottable-data-tester-dgrqq": Phase="Pending", Reason="", readiness=false. Elapsed: 30.70576256s
Jun  8 08:25:36.439: INFO: Pod "pvc-snapshottable-data-tester-dgrqq": Phase="Pending", Reason="", readiness=false. Elapsed: 32.75005055s
Jun  8 08:25:38.483: INFO: Pod "pvc-snapshottable-data-tester-dgrqq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.794398564s
STEP: Saw pod success
Jun  8 08:25:38.483: INFO: Pod "pvc-snapshottable-data-tester-dgrqq" satisfied condition "Succeeded or Failed"
Jun  8 08:25:38.583: INFO: Pod pvc-snapshottable-data-tester-dgrqq has the following logs: 
Jun  8 08:25:38.583: INFO: Deleting pod "pvc-snapshottable-data-tester-dgrqq" in namespace "snapshotting-4828"
Jun  8 08:25:38.630: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-dgrqq" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun  8 08:26:18.857: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-4828 exec restored-pvc-tester-h2dk9 --namespace=snapshotting-4828 -- cat /mnt/test/data'
... skipping 569 lines ...
Jun  8 08:25:33.136: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1755-e2e-scjkx5t
STEP: creating a claim
Jun  8 08:25:33.179: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-j74p
STEP: Creating a pod to test subpath
Jun  8 08:25:33.310: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-j74p" in namespace "provisioning-1755" to be "Succeeded or Failed"
Jun  8 08:25:33.353: INFO: Pod "pod-subpath-test-dynamicpv-j74p": Phase="Pending", Reason="", readiness=false. Elapsed: 42.607851ms
Jun  8 08:25:35.398: INFO: Pod "pod-subpath-test-dynamicpv-j74p": Phase="Pending", Reason="", readiness=false. Elapsed: 2.08783046s
Jun  8 08:25:37.442: INFO: Pod "pod-subpath-test-dynamicpv-j74p": Phase="Pending", Reason="", readiness=false. Elapsed: 4.132194915s
Jun  8 08:25:39.486: INFO: Pod "pod-subpath-test-dynamicpv-j74p": Phase="Pending", Reason="", readiness=false. Elapsed: 6.176102149s
Jun  8 08:25:41.530: INFO: Pod "pod-subpath-test-dynamicpv-j74p": Phase="Pending", Reason="", readiness=false. Elapsed: 8.220127387s
Jun  8 08:25:43.573: INFO: Pod "pod-subpath-test-dynamicpv-j74p": Phase="Pending", Reason="", readiness=false. Elapsed: 10.263061778s
Jun  8 08:25:45.619: INFO: Pod "pod-subpath-test-dynamicpv-j74p": Phase="Pending", Reason="", readiness=false. Elapsed: 12.308426714s
Jun  8 08:25:47.663: INFO: Pod "pod-subpath-test-dynamicpv-j74p": Phase="Pending", Reason="", readiness=false. Elapsed: 14.352521347s
Jun  8 08:25:49.706: INFO: Pod "pod-subpath-test-dynamicpv-j74p": Phase="Pending", Reason="", readiness=false. Elapsed: 16.396157332s
Jun  8 08:25:51.749: INFO: Pod "pod-subpath-test-dynamicpv-j74p": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.438938425s
STEP: Saw pod success
Jun  8 08:25:51.749: INFO: Pod "pod-subpath-test-dynamicpv-j74p" satisfied condition "Succeeded or Failed"
Jun  8 08:25:51.792: INFO: Trying to get logs from node ip-172-20-58-151.ec2.internal pod pod-subpath-test-dynamicpv-j74p container test-container-subpath-dynamicpv-j74p: <nil>
STEP: delete the pod
Jun  8 08:25:51.885: INFO: Waiting for pod pod-subpath-test-dynamicpv-j74p to disappear
Jun  8 08:25:51.927: INFO: Pod pod-subpath-test-dynamicpv-j74p no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-j74p
Jun  8 08:25:51.927: INFO: Deleting pod "pod-subpath-test-dynamicpv-j74p" in namespace "provisioning-1755"
STEP: Creating pod pod-subpath-test-dynamicpv-j74p
STEP: Creating a pod to test subpath
Jun  8 08:25:52.013: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-j74p" in namespace "provisioning-1755" to be "Succeeded or Failed"
Jun  8 08:25:52.055: INFO: Pod "pod-subpath-test-dynamicpv-j74p": Phase="Pending", Reason="", readiness=false. Elapsed: 42.269276ms
Jun  8 08:25:54.098: INFO: Pod "pod-subpath-test-dynamicpv-j74p": Phase="Pending", Reason="", readiness=false. Elapsed: 2.085428109s
Jun  8 08:25:56.142: INFO: Pod "pod-subpath-test-dynamicpv-j74p": Phase="Pending", Reason="", readiness=false. Elapsed: 4.129219635s
Jun  8 08:25:58.185: INFO: Pod "pod-subpath-test-dynamicpv-j74p": Phase="Pending", Reason="", readiness=false. Elapsed: 6.172612305s
Jun  8 08:26:00.228: INFO: Pod "pod-subpath-test-dynamicpv-j74p": Phase="Pending", Reason="", readiness=false. Elapsed: 8.215569365s
Jun  8 08:26:02.271: INFO: Pod "pod-subpath-test-dynamicpv-j74p": Phase="Pending", Reason="", readiness=false. Elapsed: 10.258444494s
... skipping 22 lines ...
Jun  8 08:26:49.270: INFO: Pod "pod-subpath-test-dynamicpv-j74p": Phase="Pending", Reason="", readiness=false. Elapsed: 57.257476472s
Jun  8 08:26:51.313: INFO: Pod "pod-subpath-test-dynamicpv-j74p": Phase="Pending", Reason="", readiness=false. Elapsed: 59.300500172s
Jun  8 08:26:53.356: INFO: Pod "pod-subpath-test-dynamicpv-j74p": Phase="Pending", Reason="", readiness=false. Elapsed: 1m1.343693154s
Jun  8 08:26:55.400: INFO: Pod "pod-subpath-test-dynamicpv-j74p": Phase="Pending", Reason="", readiness=false. Elapsed: 1m3.387167261s
Jun  8 08:26:57.444: INFO: Pod "pod-subpath-test-dynamicpv-j74p": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m5.430762021s
STEP: Saw pod success
Jun  8 08:26:57.444: INFO: Pod "pod-subpath-test-dynamicpv-j74p" satisfied condition "Succeeded or Failed"
Jun  8 08:26:57.486: INFO: Trying to get logs from node ip-172-20-38-158.ec2.internal pod pod-subpath-test-dynamicpv-j74p container test-container-subpath-dynamicpv-j74p: <nil>
STEP: delete the pod
Jun  8 08:26:57.581: INFO: Waiting for pod pod-subpath-test-dynamicpv-j74p to disappear
Jun  8 08:26:57.623: INFO: Pod pod-subpath-test-dynamicpv-j74p no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-j74p
Jun  8 08:26:57.624: INFO: Deleting pod "pod-subpath-test-dynamicpv-j74p" in namespace "provisioning-1755"
... skipping 38 lines ...
Jun  8 08:24:40.502: INFO: Creating resource for dynamic PV
Jun  8 08:24:40.502: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-263-e2e-sc2bbsm
STEP: creating a claim
Jun  8 08:24:40.545: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun  8 08:24:40.677: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-8czrp" in namespace "snapshotting-263" to be "Succeeded or Failed"
Jun  8 08:24:40.720: INFO: Pod "pvc-snapshottable-tester-8czrp": Phase="Pending", Reason="", readiness=false. Elapsed: 42.233412ms
Jun  8 08:24:42.764: INFO: Pod "pvc-snapshottable-tester-8czrp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.086312689s
Jun  8 08:24:44.807: INFO: Pod "pvc-snapshottable-tester-8czrp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.129520368s
Jun  8 08:24:46.851: INFO: Pod "pvc-snapshottable-tester-8czrp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.173518775s
Jun  8 08:24:48.894: INFO: Pod "pvc-snapshottable-tester-8czrp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.216245051s
Jun  8 08:24:50.936: INFO: Pod "pvc-snapshottable-tester-8czrp": Phase="Pending", Reason="", readiness=false. Elapsed: 10.258729327s
Jun  8 08:24:52.979: INFO: Pod "pvc-snapshottable-tester-8czrp": Phase="Pending", Reason="", readiness=false. Elapsed: 12.301452118s
Jun  8 08:24:55.022: INFO: Pod "pvc-snapshottable-tester-8czrp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.344427916s
STEP: Saw pod success
Jun  8 08:24:55.022: INFO: Pod "pvc-snapshottable-tester-8czrp" satisfied condition "Succeeded or Failed"
Jun  8 08:24:55.117: INFO: Pod pvc-snapshottable-tester-8czrp has the following logs: 
Jun  8 08:24:55.117: INFO: Deleting pod "pvc-snapshottable-tester-8czrp" in namespace "snapshotting-263"
Jun  8 08:24:55.167: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-8czrp" to be fully deleted
Jun  8 08:24:55.209: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.combmwnl] to have phase Bound
Jun  8 08:24:55.251: INFO: PersistentVolumeClaim ebs.csi.aws.combmwnl found and phase=Bound (41.954072ms)
STEP: [init] checking the claim
... skipping 39 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.YIoOihHZk/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  8 08:25:55.025: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-f9qxq" in namespace "snapshotting-263" to be "Succeeded or Failed"
Jun  8 08:25:55.068: INFO: Pod "pvc-snapshottable-data-tester-f9qxq": Phase="Pending", Reason="", readiness=false. Elapsed: 42.587804ms
Jun  8 08:25:57.112: INFO: Pod "pvc-snapshottable-data-tester-f9qxq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.087349962s
Jun  8 08:25:59.156: INFO: Pod "pvc-snapshottable-data-tester-f9qxq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.13108317s
Jun  8 08:26:01.199: INFO: Pod "pvc-snapshottable-data-tester-f9qxq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.173990901s
Jun  8 08:26:03.242: INFO: Pod "pvc-snapshottable-data-tester-f9qxq": Phase="Pending", Reason="", readiness=false. Elapsed: 8.217394986s
Jun  8 08:26:05.286: INFO: Pod "pvc-snapshottable-data-tester-f9qxq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.261499416s
STEP: Saw pod success
Jun  8 08:26:05.287: INFO: Pod "pvc-snapshottable-data-tester-f9qxq" satisfied condition "Succeeded or Failed"
Jun  8 08:26:05.373: INFO: Pod pvc-snapshottable-data-tester-f9qxq has the following logs: 
Jun  8 08:26:05.373: INFO: Deleting pod "pvc-snapshottable-data-tester-f9qxq" in namespace "snapshotting-263"
Jun  8 08:26:05.424: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-f9qxq" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun  8 08:26:27.643: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-263 exec restored-pvc-tester-x8zrn --namespace=snapshotting-263 -- cat /mnt/test/data'
... skipping 32 lines ...
Jun  8 08:26:52.415: INFO: volumesnapshotcontents snapcontent-f16df636-e468-443b-a2a5-94c29378615b has been found and is not deleted
Jun  8 08:26:53.459: INFO: volumesnapshotcontents snapcontent-f16df636-e468-443b-a2a5-94c29378615b has been found and is not deleted
Jun  8 08:26:54.502: INFO: volumesnapshotcontents snapcontent-f16df636-e468-443b-a2a5-94c29378615b has been found and is not deleted
Jun  8 08:26:55.545: INFO: volumesnapshotcontents snapcontent-f16df636-e468-443b-a2a5-94c29378615b has been found and is not deleted
Jun  8 08:26:56.589: INFO: volumesnapshotcontents snapcontent-f16df636-e468-443b-a2a5-94c29378615b has been found and is not deleted
Jun  8 08:26:57.632: INFO: volumesnapshotcontents snapcontent-f16df636-e468-443b-a2a5-94c29378615b has been found and is not deleted
Jun  8 08:26:58.632: INFO: WaitUntil failed after reaching the timeout 30s
[AfterEach] volume snapshot controller
  /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:221
Jun  8 08:26:58.677: INFO: Pod restored-pvc-tester-x8zrn has the following logs: 
Jun  8 08:26:58.677: INFO: Deleting pod "restored-pvc-tester-x8zrn" in namespace "snapshotting-263"
Jun  8 08:26:58.720: INFO: Wait up to 5m0s for pod "restored-pvc-tester-x8zrn" to be fully deleted
Jun  8 08:27:42.805: INFO: deleting claim "snapshotting-263"/"pvc-fxwvb"
... skipping 79 lines ...
      /tmp/kops.YIoOihHZk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volume_expand.go:246
------------------------------


Summarizing 1 Failure:

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

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


Ginkgo ran 1 suite in 15m24.226134057s
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
I0608 08:31:57.459278   26899 app.go:59] RunDir for this run: "/logs/artifacts/e7f4fd87-c82f-11eb-8f42-e213a67c471c"
I0608 08:31:57.459465   26899 app.go:90] ID for this run: "e7f4fd87-c82f-11eb-8f42-e213a67c471c"
I0608 08:31:57.459503   26899 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
I0608 08:31:57.475864   26905 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
... skipping 1457 lines ...