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

No Test Failures!


Error lines from build-log.txt

... skipping 490 lines ...
I0606 16:06:36.718110   11776 up.go:43] Cleaning up any leaked resources from previous cluster
I0606 16:06:36.718132   11776 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
I0606 16:06:36.731547   11782 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0606 16:06:36.731626   11782 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io" not found
W0606 16:06:37.215505   11776 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0606 16:06:37.215548   11776 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
I0606 16:06:37.229089   11793 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0606 16:06:37.229176   11793 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io" not found
I0606 16:06:37.722045   11776 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/06/06 16:06:37 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
I0606 16:06:37.736329   11776 http.go:37] curl https://ip.jsb.workers.dev
I0606 16:06:37.875885   11776 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.224.171.180/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones sa-east-1a --master-size c5.large
I0606 16:06:37.889463   11807 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0606 16:06:37.889535   11807 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I0606 16:06:37.931816   11807 create_cluster.go:728] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0606 16:06:38.501205   11807 new_cluster.go:1051]  Cloud Provider ID = aws
... skipping 38 lines ...

I0606 16:07:16.243746   11776 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
I0606 16:07:16.259764   11828 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0606 16:07:16.259854   11828 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io

W0606 16:07:17.729195   11828 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-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-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
W0606 16:07:27.760870   11828 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-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
W0606 16:07:37.806939   11828 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-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
W0606 16:07:47.838452   11828 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-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
W0606 16:07:57.869785   11828 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-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
W0606 16:08:07.901605   11828 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-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
W0606 16:08:17.931739   11828 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-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
W0606 16:08:27.975118   11828 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-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
W0606 16:08:38.017963   11828 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-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
W0606 16:08:48.062861   11828 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-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
W0606 16:08:58.094494   11828 validate_cluster.go:221] (will retry): cluster not yet healthy
W0606 16:09:08.123556   11828 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-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-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
W0606 16:09:18.171196   11828 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-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
W0606 16:09:28.203486   11828 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-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
W0606 16:09:38.248875   11828 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-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
W0606 16:09:48.285759   11828 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-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
W0606 16:09:58.341742   11828 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-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
W0606 16:10:08.388205   11828 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-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
W0606 16:10:18.438748   11828 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-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
W0606 16:10:28.526009   11828 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-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
W0606 16:10:38.575184   11828 validate_cluster.go:221] (will retry): cluster not yet healthy
W0606 16:10:48.596577   11828 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-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-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
W0606 16:10:58.623469   11828 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-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
W0606 16:11:08.655017   11828 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-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
W0606 16:11:18.683233   11828 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-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
W0606 16:11:28.720143   11828 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-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
W0606 16:11:38.748664   11828 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-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
W0606 16:11:48.779665   11828 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-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
W0606 16:11:58.810404   11828 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-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
W0606 16:12:08.840652   11828 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-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
W0606 16:12:18.869797   11828 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-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
W0606 16:12:28.899493   11828 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 14 lines ...
Pod	kube-system/cert-manager-cainjector-74d69756d5-fk8bg	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-fk8bg" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-whrcj	system-cluster-critical pod "cert-manager-webhook-7bbf67968-whrcj" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-hh87t		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-hh87t" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-zqzh7		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-zqzh7" is pending
Pod	kube-system/ebs-csi-node-926tl				system-node-critical pod "ebs-csi-node-926tl" is pending

Validation Failed
W0606 16:12:42.480257   11828 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 20 lines ...
Pod	kube-system/ebs-csi-node-2bng8						system-node-critical pod "ebs-csi-node-2bng8" is pending
Pod	kube-system/ebs-csi-node-qp2mx						system-node-critical pod "ebs-csi-node-qp2mx" is pending
Pod	kube-system/ebs-csi-node-rv5pb						system-node-critical pod "ebs-csi-node-rv5pb" is pending
Pod	kube-system/kube-proxy-ip-172-20-59-101.sa-east-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-59-101.sa-east-1.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-59-46.sa-east-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-59-46.sa-east-1.compute.internal" is pending

Validation Failed
W0606 16:12:54.974381   11828 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 27 lines ...
Pod	kube-system/ebs-csi-node-qp2mx						system-node-critical pod "ebs-csi-node-qp2mx" is pending
Pod	kube-system/ebs-csi-node-rv5pb						system-node-critical pod "ebs-csi-node-rv5pb" is pending
Pod	kube-system/kube-proxy-ip-172-20-44-71.sa-east-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-44-71.sa-east-1.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-59-101.sa-east-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-59-101.sa-east-1.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-62-27.sa-east-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-62-27.sa-east-1.compute.internal" is pending

Validation Failed
W0606 16:13:07.377902   11828 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 21 lines ...
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-zqzh7		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-zqzh7" is pending
Pod	kube-system/ebs-csi-node-2bng8				system-node-critical pod "ebs-csi-node-2bng8" is pending
Pod	kube-system/ebs-csi-node-c7f7s				system-node-critical pod "ebs-csi-node-c7f7s" is pending
Pod	kube-system/ebs-csi-node-qp2mx				system-node-critical pod "ebs-csi-node-qp2mx" is pending
Pod	kube-system/ebs-csi-node-rv5pb				system-node-critical pod "ebs-csi-node-rv5pb" is pending

Validation Failed
W0606 16:13:19.804737   11828 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 16 lines ...
Pod	kube-system/coredns-autoscaler-6f594f4c58-5wx6b		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-5wx6b" is pending
Pod	kube-system/coredns-f45c4bf76-qq9g5			system-cluster-critical pod "coredns-f45c4bf76-qq9g5" is pending
Pod	kube-system/ebs-csi-node-c7f7s				system-node-critical pod "ebs-csi-node-c7f7s" is pending
Pod	kube-system/ebs-csi-node-qp2mx				system-node-critical pod "ebs-csi-node-qp2mx" is pending
Pod	kube-system/ebs-csi-node-rv5pb				system-node-critical pod "ebs-csi-node-rv5pb" is pending

Validation Failed
W0606 16:13:32.713419   11828 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 12 lines ...
Pod	kube-system/calico-node-pwk9g				system-node-critical pod "calico-node-pwk9g" is not ready (calico-node)
Pod	kube-system/calico-node-x4ttp				system-node-critical pod "calico-node-x4ttp" is not ready (calico-node)
Pod	kube-system/cert-manager-cainjector-74d69756d5-fk8bg	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-fk8bg" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-whrcj	system-cluster-critical pod "cert-manager-webhook-7bbf67968-whrcj" is not ready (cert-manager)
Pod	kube-system/coredns-autoscaler-6f594f4c58-5wx6b		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-5wx6b" is pending

Validation Failed
W0606 16:13:45.148073   11828 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 303 lines ...

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

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 401 lines ...

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.42NGBlObb/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.42NGBlObb/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.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 27 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  6 16:18:44.669: 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.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  6 16:18:45.809: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  6 16:18:46.807: INFO: Successfully created a new PD: "aws://sa-east-1a/vol-0a68e04468bb1cb76".
Jun  6 16:18:46.807: INFO: Creating resource for pre-provisioned PV
Jun  6 16:18:46.807: INFO: Creating PVC and PV
... skipping 7 lines ...
Jun  6 16:18:55.912: INFO: PersistentVolumeClaim pvc-ccppz found but phase is Pending instead of Bound.
Jun  6 16:18:58.058: INFO: PersistentVolumeClaim pvc-ccppz found but phase is Pending instead of Bound.
Jun  6 16:19:00.204: INFO: PersistentVolumeClaim pvc-ccppz found and phase=Bound (13.024528088s)
Jun  6 16:19:00.204: INFO: Waiting up to 3m0s for PersistentVolume aws-hxk9v to have phase Bound
Jun  6 16:19:00.349: INFO: PersistentVolume aws-hxk9v found and phase=Bound (145.263334ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  6 16:19:03.234: INFO: Deleting pod "pod-dda3dd06-39b1-4a47-bc6e-3e0960803fab" in namespace "volumemode-2193"
Jun  6 16:19:03.380: INFO: Wait up to 5m0s for pod "pod-dda3dd06-39b1-4a47-bc6e-3e0960803fab" to be fully deleted
STEP: Deleting pv and pvc
Jun  6 16:19:15.672: INFO: Deleting PersistentVolumeClaim "pvc-ccppz"
Jun  6 16:19:15.821: INFO: Deleting PersistentVolume "aws-hxk9v"
Jun  6 16:19:16.254: INFO: Successfully deleted PD "aws://sa-east-1a/vol-0a68e04468bb1cb76".
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.42NGBlObb/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.42NGBlObb/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
    /tmp/kops.42NGBlObb/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.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] provisioning
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] provisioning
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 41 lines ...
Jun  6 16:18:43.550: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6738w5bf6
STEP: creating a claim
Jun  6 16:18:43.697: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-7l92
STEP: Creating a pod to test subpath
Jun  6 16:18:44.161: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-7l92" in namespace "provisioning-6738" to be "Succeeded or Failed"
Jun  6 16:18:44.308: INFO: Pod "pod-subpath-test-dynamicpv-7l92": Phase="Pending", Reason="", readiness=false. Elapsed: 146.431297ms
Jun  6 16:18:46.457: INFO: Pod "pod-subpath-test-dynamicpv-7l92": Phase="Pending", Reason="", readiness=false. Elapsed: 2.29606989s
Jun  6 16:18:48.609: INFO: Pod "pod-subpath-test-dynamicpv-7l92": Phase="Pending", Reason="", readiness=false. Elapsed: 4.447752141s
Jun  6 16:18:50.768: INFO: Pod "pod-subpath-test-dynamicpv-7l92": Phase="Pending", Reason="", readiness=false. Elapsed: 6.606985378s
Jun  6 16:18:52.916: INFO: Pod "pod-subpath-test-dynamicpv-7l92": Phase="Pending", Reason="", readiness=false. Elapsed: 8.75500753s
Jun  6 16:18:55.064: INFO: Pod "pod-subpath-test-dynamicpv-7l92": Phase="Pending", Reason="", readiness=false. Elapsed: 10.902516762s
... skipping 2 lines ...
Jun  6 16:19:01.506: INFO: Pod "pod-subpath-test-dynamicpv-7l92": Phase="Pending", Reason="", readiness=false. Elapsed: 17.344571013s
Jun  6 16:19:03.655: INFO: Pod "pod-subpath-test-dynamicpv-7l92": Phase="Pending", Reason="", readiness=false. Elapsed: 19.494193463s
Jun  6 16:19:05.804: INFO: Pod "pod-subpath-test-dynamicpv-7l92": Phase="Pending", Reason="", readiness=false. Elapsed: 21.642857287s
Jun  6 16:19:07.952: INFO: Pod "pod-subpath-test-dynamicpv-7l92": Phase="Pending", Reason="", readiness=false. Elapsed: 23.790319051s
Jun  6 16:19:10.099: INFO: Pod "pod-subpath-test-dynamicpv-7l92": Phase="Succeeded", Reason="", readiness=false. Elapsed: 25.937794675s
STEP: Saw pod success
Jun  6 16:19:10.099: INFO: Pod "pod-subpath-test-dynamicpv-7l92" satisfied condition "Succeeded or Failed"
Jun  6 16:19:10.249: INFO: Trying to get logs from node ip-172-20-59-46.sa-east-1.compute.internal pod pod-subpath-test-dynamicpv-7l92 container test-container-subpath-dynamicpv-7l92: <nil>
STEP: delete the pod
Jun  6 16:19:10.559: INFO: Waiting for pod pod-subpath-test-dynamicpv-7l92 to disappear
Jun  6 16:19:10.705: INFO: Pod pod-subpath-test-dynamicpv-7l92 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-7l92
Jun  6 16:19:10.705: INFO: Deleting pod "pod-subpath-test-dynamicpv-7l92" in namespace "provisioning-6738"
... skipping 122 lines ...
Jun  6 16:18:45.197: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-45955dgvc
STEP: creating a claim
Jun  6 16:18:45.345: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-dkzl
STEP: Creating a pod to test subpath
Jun  6 16:18:45.812: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-dkzl" in namespace "provisioning-4595" to be "Succeeded or Failed"
Jun  6 16:18:45.959: INFO: Pod "pod-subpath-test-dynamicpv-dkzl": Phase="Pending", Reason="", readiness=false. Elapsed: 146.186321ms
Jun  6 16:18:48.125: INFO: Pod "pod-subpath-test-dynamicpv-dkzl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.312751187s
Jun  6 16:18:50.278: INFO: Pod "pod-subpath-test-dynamicpv-dkzl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.465808935s
Jun  6 16:18:52.427: INFO: Pod "pod-subpath-test-dynamicpv-dkzl": Phase="Pending", Reason="", readiness=false. Elapsed: 6.614914086s
Jun  6 16:18:54.575: INFO: Pod "pod-subpath-test-dynamicpv-dkzl": Phase="Pending", Reason="", readiness=false. Elapsed: 8.762204149s
Jun  6 16:18:56.721: INFO: Pod "pod-subpath-test-dynamicpv-dkzl": Phase="Pending", Reason="", readiness=false. Elapsed: 10.908957315s
Jun  6 16:18:58.868: INFO: Pod "pod-subpath-test-dynamicpv-dkzl": Phase="Pending", Reason="", readiness=false. Elapsed: 13.055529572s
Jun  6 16:19:01.020: INFO: Pod "pod-subpath-test-dynamicpv-dkzl": Phase="Pending", Reason="", readiness=false. Elapsed: 15.20800978s
Jun  6 16:19:03.167: INFO: Pod "pod-subpath-test-dynamicpv-dkzl": Phase="Pending", Reason="", readiness=false. Elapsed: 17.355014608s
Jun  6 16:19:05.317: INFO: Pod "pod-subpath-test-dynamicpv-dkzl": Phase="Pending", Reason="", readiness=false. Elapsed: 19.504883724s
Jun  6 16:19:07.464: INFO: Pod "pod-subpath-test-dynamicpv-dkzl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.652073296s
STEP: Saw pod success
Jun  6 16:19:07.464: INFO: Pod "pod-subpath-test-dynamicpv-dkzl" satisfied condition "Succeeded or Failed"
Jun  6 16:19:07.613: INFO: Trying to get logs from node ip-172-20-59-46.sa-east-1.compute.internal pod pod-subpath-test-dynamicpv-dkzl container test-container-volume-dynamicpv-dkzl: <nil>
STEP: delete the pod
Jun  6 16:19:07.921: INFO: Waiting for pod pod-subpath-test-dynamicpv-dkzl to disappear
Jun  6 16:19:08.072: INFO: Pod pod-subpath-test-dynamicpv-dkzl no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-dkzl
Jun  6 16:19:08.072: INFO: Deleting pod "pod-subpath-test-dynamicpv-dkzl" in namespace "provisioning-4595"
... skipping 33 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.42NGBlObb/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.42NGBlObb/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.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 25 lines ...
STEP: Creating a kubernetes client
Jun  6 16:18:41.105: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename provisioning
W0606 16:18:42.050099   25521 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Jun  6 16:18:42.050: 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.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun  6 16:18:42.336: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  6 16:18:42.336: INFO: Creating resource for dynamic PV
Jun  6 16:18:42.336: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6318lvwdb
STEP: creating a claim
Jun  6 16:18:42.485: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-cb2f
STEP: Checking for subpath error in container status
Jun  6 16:19:09.217: INFO: Deleting pod "pod-subpath-test-dynamicpv-cb2f" in namespace "provisioning-6318"
Jun  6 16:19:09.373: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-cb2f" to be fully deleted
STEP: Deleting pod
Jun  6 16:19:15.669: INFO: Deleting pod "pod-subpath-test-dynamicpv-cb2f" in namespace "provisioning-6318"
STEP: Deleting pvc
Jun  6 16:19:16.120: INFO: Deleting PersistentVolumeClaim "awslkqhk"
... skipping 13 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.42NGBlObb/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.42NGBlObb/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.42NGBlObb/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.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  6 16:19:32.435: INFO: Driver "ebs.csi.aws.com" does not support volume type "InlineVolume" - skipping
[AfterEach] [Testpattern: Inline-volume (default fs)] subPath
... skipping 47 lines ...
Jun  6 16:18:42.161: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4555-e2e-sc75q88
STEP: creating a claim
Jun  6 16:18:42.309: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-q74j
STEP: Creating a pod to test subpath
Jun  6 16:18:42.757: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-q74j" in namespace "provisioning-4555" to be "Succeeded or Failed"
Jun  6 16:18:42.909: INFO: Pod "pod-subpath-test-dynamicpv-q74j": Phase="Pending", Reason="", readiness=false. Elapsed: 151.917477ms
Jun  6 16:18:45.057: INFO: Pod "pod-subpath-test-dynamicpv-q74j": Phase="Pending", Reason="", readiness=false. Elapsed: 2.299673771s
Jun  6 16:18:47.205: INFO: Pod "pod-subpath-test-dynamicpv-q74j": Phase="Pending", Reason="", readiness=false. Elapsed: 4.447831978s
Jun  6 16:18:49.352: INFO: Pod "pod-subpath-test-dynamicpv-q74j": Phase="Pending", Reason="", readiness=false. Elapsed: 6.594850656s
Jun  6 16:18:51.498: INFO: Pod "pod-subpath-test-dynamicpv-q74j": Phase="Pending", Reason="", readiness=false. Elapsed: 8.741081749s
Jun  6 16:18:53.643: INFO: Pod "pod-subpath-test-dynamicpv-q74j": Phase="Pending", Reason="", readiness=false. Elapsed: 10.885990941s
... skipping 7 lines ...
Jun  6 16:19:10.818: INFO: Pod "pod-subpath-test-dynamicpv-q74j": Phase="Pending", Reason="", readiness=false. Elapsed: 28.061038271s
Jun  6 16:19:12.967: INFO: Pod "pod-subpath-test-dynamicpv-q74j": Phase="Pending", Reason="", readiness=false. Elapsed: 30.210087379s
Jun  6 16:19:15.113: INFO: Pod "pod-subpath-test-dynamicpv-q74j": Phase="Pending", Reason="", readiness=false. Elapsed: 32.355546813s
Jun  6 16:19:17.258: INFO: Pod "pod-subpath-test-dynamicpv-q74j": Phase="Pending", Reason="", readiness=false. Elapsed: 34.501062143s
Jun  6 16:19:19.406: INFO: Pod "pod-subpath-test-dynamicpv-q74j": Phase="Succeeded", Reason="", readiness=false. Elapsed: 36.648318148s
STEP: Saw pod success
Jun  6 16:19:19.406: INFO: Pod "pod-subpath-test-dynamicpv-q74j" satisfied condition "Succeeded or Failed"
Jun  6 16:19:19.553: INFO: Trying to get logs from node ip-172-20-62-27.sa-east-1.compute.internal pod pod-subpath-test-dynamicpv-q74j container test-container-subpath-dynamicpv-q74j: <nil>
STEP: delete the pod
Jun  6 16:19:19.856: INFO: Waiting for pod pod-subpath-test-dynamicpv-q74j to disappear
Jun  6 16:19:20.000: INFO: Pod pod-subpath-test-dynamicpv-q74j no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-q74j
Jun  6 16:19:20.000: INFO: Deleting pod "pod-subpath-test-dynamicpv-q74j" in namespace "provisioning-4555"
... skipping 154 lines ...
Jun  6 16:18:43.889: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-1780-e2e-sccd6m5
STEP: creating a claim
Jun  6 16:18:44.041: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-4pbj
STEP: Creating a pod to test exec-volume-test
Jun  6 16:18:44.485: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-4pbj" in namespace "volume-1780" to be "Succeeded or Failed"
Jun  6 16:18:44.630: INFO: Pod "exec-volume-test-dynamicpv-4pbj": Phase="Pending", Reason="", readiness=false. Elapsed: 145.003226ms
Jun  6 16:18:46.777: INFO: Pod "exec-volume-test-dynamicpv-4pbj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.291428681s
Jun  6 16:18:48.925: INFO: Pod "exec-volume-test-dynamicpv-4pbj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.440009633s
Jun  6 16:18:51.070: INFO: Pod "exec-volume-test-dynamicpv-4pbj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.584433755s
Jun  6 16:18:53.214: INFO: Pod "exec-volume-test-dynamicpv-4pbj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.728498588s
Jun  6 16:18:55.362: INFO: Pod "exec-volume-test-dynamicpv-4pbj": Phase="Pending", Reason="", readiness=false. Elapsed: 10.876996641s
Jun  6 16:18:57.507: INFO: Pod "exec-volume-test-dynamicpv-4pbj": Phase="Pending", Reason="", readiness=false. Elapsed: 13.022156196s
Jun  6 16:18:59.652: INFO: Pod "exec-volume-test-dynamicpv-4pbj": Phase="Pending", Reason="", readiness=false. Elapsed: 15.166784731s
Jun  6 16:19:01.797: INFO: Pod "exec-volume-test-dynamicpv-4pbj": Phase="Pending", Reason="", readiness=false. Elapsed: 17.311364438s
Jun  6 16:19:03.941: INFO: Pod "exec-volume-test-dynamicpv-4pbj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.455547859s
STEP: Saw pod success
Jun  6 16:19:03.941: INFO: Pod "exec-volume-test-dynamicpv-4pbj" satisfied condition "Succeeded or Failed"
Jun  6 16:19:04.085: INFO: Trying to get logs from node ip-172-20-59-101.sa-east-1.compute.internal pod exec-volume-test-dynamicpv-4pbj container exec-container-dynamicpv-4pbj: <nil>
STEP: delete the pod
Jun  6 16:19:04.393: INFO: Waiting for pod exec-volume-test-dynamicpv-4pbj to disappear
Jun  6 16:19:04.537: INFO: Pod exec-volume-test-dynamicpv-4pbj no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-4pbj
Jun  6 16:19:04.537: INFO: Deleting pod "exec-volume-test-dynamicpv-4pbj" in namespace "volume-1780"
... skipping 104 lines ...
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  6 16:19:41.994: 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.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Jun  6 16:19:42.877: INFO: found topology map[topology.kubernetes.io/zone:sa-east-1a]
Jun  6 16:19:42.877: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  6 16:19:42.877: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.42NGBlObb/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.42NGBlObb/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (immediate binding)] topology
    /tmp/kops.42NGBlObb/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.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 14 lines ...
Jun  6 16:18:42.619: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1242nqbhl
STEP: creating a claim
Jun  6 16:18:42.766: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-tzpt
STEP: Creating a pod to test multi_subpath
Jun  6 16:18:43.217: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-tzpt" in namespace "provisioning-1242" to be "Succeeded or Failed"
Jun  6 16:18:43.362: INFO: Pod "pod-subpath-test-dynamicpv-tzpt": Phase="Pending", Reason="", readiness=false. Elapsed: 144.979962ms
Jun  6 16:18:45.513: INFO: Pod "pod-subpath-test-dynamicpv-tzpt": Phase="Pending", Reason="", readiness=false. Elapsed: 2.295615077s
Jun  6 16:18:47.659: INFO: Pod "pod-subpath-test-dynamicpv-tzpt": Phase="Pending", Reason="", readiness=false. Elapsed: 4.442172765s
Jun  6 16:18:49.806: INFO: Pod "pod-subpath-test-dynamicpv-tzpt": Phase="Pending", Reason="", readiness=false. Elapsed: 6.58883042s
Jun  6 16:18:51.956: INFO: Pod "pod-subpath-test-dynamicpv-tzpt": Phase="Pending", Reason="", readiness=false. Elapsed: 8.738270934s
Jun  6 16:18:54.102: INFO: Pod "pod-subpath-test-dynamicpv-tzpt": Phase="Pending", Reason="", readiness=false. Elapsed: 10.884400139s
... skipping 7 lines ...
Jun  6 16:19:11.296: INFO: Pod "pod-subpath-test-dynamicpv-tzpt": Phase="Pending", Reason="", readiness=false. Elapsed: 28.078944241s
Jun  6 16:19:13.448: INFO: Pod "pod-subpath-test-dynamicpv-tzpt": Phase="Pending", Reason="", readiness=false. Elapsed: 30.23038098s
Jun  6 16:19:15.593: INFO: Pod "pod-subpath-test-dynamicpv-tzpt": Phase="Pending", Reason="", readiness=false. Elapsed: 32.375890145s
Jun  6 16:19:17.745: INFO: Pod "pod-subpath-test-dynamicpv-tzpt": Phase="Pending", Reason="", readiness=false. Elapsed: 34.527894667s
Jun  6 16:19:19.897: INFO: Pod "pod-subpath-test-dynamicpv-tzpt": Phase="Succeeded", Reason="", readiness=false. Elapsed: 36.679901939s
STEP: Saw pod success
Jun  6 16:19:19.897: INFO: Pod "pod-subpath-test-dynamicpv-tzpt" satisfied condition "Succeeded or Failed"
Jun  6 16:19:20.044: INFO: Trying to get logs from node ip-172-20-62-27.sa-east-1.compute.internal pod pod-subpath-test-dynamicpv-tzpt container test-container-subpath-dynamicpv-tzpt: <nil>
STEP: delete the pod
Jun  6 16:19:20.344: INFO: Waiting for pod pod-subpath-test-dynamicpv-tzpt to disappear
Jun  6 16:19:20.489: INFO: Pod pod-subpath-test-dynamicpv-tzpt no longer exists
STEP: Deleting pod
Jun  6 16:19:20.489: INFO: Deleting pod "pod-subpath-test-dynamicpv-tzpt" in namespace "provisioning-1242"
... skipping 58 lines ...
Jun  6 16:18:42.853: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9675-e2e-scjxpbg
STEP: creating a claim
Jun  6 16:18:43.005: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-bgp6
STEP: Creating a pod to test subpath
Jun  6 16:18:43.445: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-bgp6" in namespace "provisioning-9675" to be "Succeeded or Failed"
Jun  6 16:18:43.589: INFO: Pod "pod-subpath-test-dynamicpv-bgp6": Phase="Pending", Reason="", readiness=false. Elapsed: 143.65424ms
Jun  6 16:18:45.737: INFO: Pod "pod-subpath-test-dynamicpv-bgp6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.291971499s
Jun  6 16:18:47.884: INFO: Pod "pod-subpath-test-dynamicpv-bgp6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.438536011s
Jun  6 16:18:50.033: INFO: Pod "pod-subpath-test-dynamicpv-bgp6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.587811106s
Jun  6 16:18:52.178: INFO: Pod "pod-subpath-test-dynamicpv-bgp6": Phase="Pending", Reason="", readiness=false. Elapsed: 8.732992423s
Jun  6 16:18:54.323: INFO: Pod "pod-subpath-test-dynamicpv-bgp6": Phase="Pending", Reason="", readiness=false. Elapsed: 10.877686005s
Jun  6 16:18:56.467: INFO: Pod "pod-subpath-test-dynamicpv-bgp6": Phase="Pending", Reason="", readiness=false. Elapsed: 13.021731156s
Jun  6 16:18:58.611: INFO: Pod "pod-subpath-test-dynamicpv-bgp6": Phase="Pending", Reason="", readiness=false. Elapsed: 15.166017195s
Jun  6 16:19:00.762: INFO: Pod "pod-subpath-test-dynamicpv-bgp6": Phase="Pending", Reason="", readiness=false. Elapsed: 17.317071504s
Jun  6 16:19:02.907: INFO: Pod "pod-subpath-test-dynamicpv-bgp6": Phase="Pending", Reason="", readiness=false. Elapsed: 19.461484829s
Jun  6 16:19:05.053: INFO: Pod "pod-subpath-test-dynamicpv-bgp6": Phase="Pending", Reason="", readiness=false. Elapsed: 21.608078011s
Jun  6 16:19:07.198: INFO: Pod "pod-subpath-test-dynamicpv-bgp6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.753059869s
STEP: Saw pod success
Jun  6 16:19:07.198: INFO: Pod "pod-subpath-test-dynamicpv-bgp6" satisfied condition "Succeeded or Failed"
Jun  6 16:19:07.342: INFO: Trying to get logs from node ip-172-20-59-46.sa-east-1.compute.internal pod pod-subpath-test-dynamicpv-bgp6 container test-container-subpath-dynamicpv-bgp6: <nil>
STEP: delete the pod
Jun  6 16:19:07.659: INFO: Waiting for pod pod-subpath-test-dynamicpv-bgp6 to disappear
Jun  6 16:19:07.805: INFO: Pod pod-subpath-test-dynamicpv-bgp6 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-bgp6
Jun  6 16:19:07.805: INFO: Deleting pod "pod-subpath-test-dynamicpv-bgp6" in namespace "provisioning-9675"
STEP: Creating pod pod-subpath-test-dynamicpv-bgp6
STEP: Creating a pod to test subpath
Jun  6 16:19:08.095: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-bgp6" in namespace "provisioning-9675" to be "Succeeded or Failed"
Jun  6 16:19:08.240: INFO: Pod "pod-subpath-test-dynamicpv-bgp6": Phase="Pending", Reason="", readiness=false. Elapsed: 144.189354ms
Jun  6 16:19:10.386: INFO: Pod "pod-subpath-test-dynamicpv-bgp6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.290397082s
Jun  6 16:19:12.531: INFO: Pod "pod-subpath-test-dynamicpv-bgp6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.43542688s
STEP: Saw pod success
Jun  6 16:19:12.531: INFO: Pod "pod-subpath-test-dynamicpv-bgp6" satisfied condition "Succeeded or Failed"
Jun  6 16:19:12.676: INFO: Trying to get logs from node ip-172-20-59-46.sa-east-1.compute.internal pod pod-subpath-test-dynamicpv-bgp6 container test-container-subpath-dynamicpv-bgp6: <nil>
STEP: delete the pod
Jun  6 16:19:12.970: INFO: Waiting for pod pod-subpath-test-dynamicpv-bgp6 to disappear
Jun  6 16:19:13.114: INFO: Pod pod-subpath-test-dynamicpv-bgp6 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-bgp6
Jun  6 16:19:13.114: INFO: Deleting pod "pod-subpath-test-dynamicpv-bgp6" in namespace "provisioning-9675"
... skipping 39 lines ...
Jun  6 16:18:45.753: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-4005-e2e-scfg84w
STEP: creating a claim
Jun  6 16:18:45.901: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-42vv
STEP: Creating a pod to test exec-volume-test
Jun  6 16:18:46.345: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-42vv" in namespace "volume-4005" to be "Succeeded or Failed"
Jun  6 16:18:46.491: INFO: Pod "exec-volume-test-dynamicpv-42vv": Phase="Pending", Reason="", readiness=false. Elapsed: 145.882096ms
Jun  6 16:18:48.641: INFO: Pod "exec-volume-test-dynamicpv-42vv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.295359194s
Jun  6 16:18:50.791: INFO: Pod "exec-volume-test-dynamicpv-42vv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.44521459s
Jun  6 16:18:52.936: INFO: Pod "exec-volume-test-dynamicpv-42vv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.590870992s
Jun  6 16:18:55.083: INFO: Pod "exec-volume-test-dynamicpv-42vv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.737243145s
Jun  6 16:18:57.228: INFO: Pod "exec-volume-test-dynamicpv-42vv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.883010628s
... skipping 3 lines ...
Jun  6 16:19:05.821: INFO: Pod "exec-volume-test-dynamicpv-42vv": Phase="Pending", Reason="", readiness=false. Elapsed: 19.475732227s
Jun  6 16:19:07.971: INFO: Pod "exec-volume-test-dynamicpv-42vv": Phase="Pending", Reason="", readiness=false. Elapsed: 21.625835488s
Jun  6 16:19:10.121: INFO: Pod "exec-volume-test-dynamicpv-42vv": Phase="Pending", Reason="", readiness=false. Elapsed: 23.775852256s
Jun  6 16:19:12.268: INFO: Pod "exec-volume-test-dynamicpv-42vv": Phase="Pending", Reason="", readiness=false. Elapsed: 25.922746361s
Jun  6 16:19:14.416: INFO: Pod "exec-volume-test-dynamicpv-42vv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 28.071076755s
STEP: Saw pod success
Jun  6 16:19:14.416: INFO: Pod "exec-volume-test-dynamicpv-42vv" satisfied condition "Succeeded or Failed"
Jun  6 16:19:14.565: INFO: Trying to get logs from node ip-172-20-44-71.sa-east-1.compute.internal pod exec-volume-test-dynamicpv-42vv container exec-container-dynamicpv-42vv: <nil>
STEP: delete the pod
Jun  6 16:19:15.201: INFO: Waiting for pod exec-volume-test-dynamicpv-42vv to disappear
Jun  6 16:19:15.348: INFO: Pod exec-volume-test-dynamicpv-42vv no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-42vv
Jun  6 16:19:15.348: INFO: Deleting pod "exec-volume-test-dynamicpv-42vv" in namespace "volume-4005"
... skipping 47 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  6 16:19:17.587: 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.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  6 16:19:18.319: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  6 16:19:18.319: INFO: Creating resource for dynamic PV
Jun  6 16:19:18.319: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-2878vh6zl
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  6 16:19:25.345: INFO: Deleting pod "pod-0bab16c6-d0fe-48d5-91c1-e69b0e581462" in namespace "volumemode-2878"
Jun  6 16:19:25.503: INFO: Wait up to 5m0s for pod "pod-0bab16c6-d0fe-48d5-91c1-e69b0e581462" to be fully deleted
STEP: Deleting pvc
Jun  6 16:19:34.085: INFO: Deleting PersistentVolumeClaim "aws29cj4"
Jun  6 16:19:34.232: INFO: Waiting up to 5m0s for PersistentVolume pvc-c8e5197f-0ab7-4a4b-85fd-08ca66dddb80 to get deleted
Jun  6 16:19:34.377: INFO: PersistentVolume pvc-c8e5197f-0ab7-4a4b-85fd-08ca66dddb80 found and phase=Released (145.330253ms)
... skipping 12 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.42NGBlObb/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.42NGBlObb/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (block volmode)] volumeMode
    /tmp/kops.42NGBlObb/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.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] volume-expand
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  6 16:19:55.422: INFO: Driver ebs.csi.aws.com doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] volume-expand
... skipping 287 lines ...
Jun  6 16:19:59.963: INFO: Pod aws-client still exists
Jun  6 16:20:01.816: INFO: Waiting for pod aws-client to disappear
Jun  6 16:20:01.962: INFO: Pod aws-client still exists
Jun  6 16:20:03.816: INFO: Waiting for pod aws-client to disappear
Jun  6 16:20:03.964: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun  6 16:20:04.740: INFO: Couldn't delete PD "aws://sa-east-1a/vol-0914bb04379147f0c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0914bb04379147f0c is currently attached to i-0497bb511a26d2153
	status code: 400, request id: a928b9ac-d2f8-4ed0-b483-e57c42093557
Jun  6 16:20:10.573: INFO: Couldn't delete PD "aws://sa-east-1a/vol-0914bb04379147f0c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0914bb04379147f0c is currently attached to i-0497bb511a26d2153
	status code: 400, request id: cfef6b77-d3c7-4aa6-9c0c-58cbfa3ce56d
Jun  6 16:20:16.381: INFO: Successfully deleted PD "aws://sa-east-1a/vol-0914bb04379147f0c".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  6 16:20:16.381: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-1951" for this suite.
... skipping 62 lines ...
Jun  6 16:19:48.267: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  6 16:19:49.303: INFO: Successfully created a new PD: "aws://sa-east-1a/vol-090c8219f4887fe04".
Jun  6 16:19:49.303: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-gwwn
STEP: Creating a pod to test exec-volume-test
Jun  6 16:19:49.451: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-gwwn" in namespace "volume-703" to be "Succeeded or Failed"
Jun  6 16:19:49.596: INFO: Pod "exec-volume-test-inlinevolume-gwwn": Phase="Pending", Reason="", readiness=false. Elapsed: 144.862351ms
Jun  6 16:19:51.742: INFO: Pod "exec-volume-test-inlinevolume-gwwn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.291092083s
Jun  6 16:19:53.889: INFO: Pod "exec-volume-test-inlinevolume-gwwn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.437989075s
Jun  6 16:19:56.035: INFO: Pod "exec-volume-test-inlinevolume-gwwn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.583550257s
Jun  6 16:19:58.181: INFO: Pod "exec-volume-test-inlinevolume-gwwn": Phase="Pending", Reason="", readiness=false. Elapsed: 8.729318932s
Jun  6 16:20:00.329: INFO: Pod "exec-volume-test-inlinevolume-gwwn": Phase="Pending", Reason="", readiness=false. Elapsed: 10.877225224s
Jun  6 16:20:02.476: INFO: Pod "exec-volume-test-inlinevolume-gwwn": Phase="Pending", Reason="", readiness=false. Elapsed: 13.024480405s
Jun  6 16:20:04.622: INFO: Pod "exec-volume-test-inlinevolume-gwwn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 15.170524247s
STEP: Saw pod success
Jun  6 16:20:04.622: INFO: Pod "exec-volume-test-inlinevolume-gwwn" satisfied condition "Succeeded or Failed"
Jun  6 16:20:04.766: INFO: Trying to get logs from node ip-172-20-62-27.sa-east-1.compute.internal pod exec-volume-test-inlinevolume-gwwn container exec-container-inlinevolume-gwwn: <nil>
STEP: delete the pod
Jun  6 16:20:05.064: INFO: Waiting for pod exec-volume-test-inlinevolume-gwwn to disappear
Jun  6 16:20:05.209: INFO: Pod exec-volume-test-inlinevolume-gwwn no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-gwwn
Jun  6 16:20:05.209: INFO: Deleting pod "exec-volume-test-inlinevolume-gwwn" in namespace "volume-703"
Jun  6 16:20:05.620: INFO: Couldn't delete PD "aws://sa-east-1a/vol-090c8219f4887fe04", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-090c8219f4887fe04 is currently attached to i-0f6cb2f6c0ee35ab2
	status code: 400, request id: eff92105-f735-47f2-985d-3d47a48e3718
Jun  6 16:20:11.378: INFO: Couldn't delete PD "aws://sa-east-1a/vol-090c8219f4887fe04", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-090c8219f4887fe04 is currently attached to i-0f6cb2f6c0ee35ab2
	status code: 400, request id: 4f994416-4b48-4877-994a-2bb12bd95bf7
Jun  6 16:20:17.167: INFO: Successfully deleted PD "aws://sa-east-1a/vol-090c8219f4887fe04".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  6 16:20:17.167: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-703" for this suite.
... skipping 271 lines ...

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

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

    /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 565 lines ...
Jun  6 16:19:58.528: INFO: PersistentVolumeClaim pvc-gb5rs found but phase is Pending instead of Bound.
Jun  6 16:20:00.674: INFO: PersistentVolumeClaim pvc-gb5rs found and phase=Bound (15.174394154s)
Jun  6 16:20:00.674: INFO: Waiting up to 3m0s for PersistentVolume aws-fd5kp to have phase Bound
Jun  6 16:20:00.823: INFO: PersistentVolume aws-fd5kp found and phase=Bound (148.85335ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-b79s
STEP: Creating a pod to test exec-volume-test
Jun  6 16:20:01.265: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-b79s" in namespace "volume-4809" to be "Succeeded or Failed"
Jun  6 16:20:01.412: INFO: Pod "exec-volume-test-preprovisionedpv-b79s": Phase="Pending", Reason="", readiness=false. Elapsed: 146.299546ms
Jun  6 16:20:03.559: INFO: Pod "exec-volume-test-preprovisionedpv-b79s": Phase="Pending", Reason="", readiness=false. Elapsed: 2.294157731s
Jun  6 16:20:05.706: INFO: Pod "exec-volume-test-preprovisionedpv-b79s": Phase="Pending", Reason="", readiness=false. Elapsed: 4.440582489s
Jun  6 16:20:07.852: INFO: Pod "exec-volume-test-preprovisionedpv-b79s": Phase="Pending", Reason="", readiness=false. Elapsed: 6.586774371s
Jun  6 16:20:09.999: INFO: Pod "exec-volume-test-preprovisionedpv-b79s": Phase="Pending", Reason="", readiness=false. Elapsed: 8.733739571s
Jun  6 16:20:12.146: INFO: Pod "exec-volume-test-preprovisionedpv-b79s": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.881090574s
STEP: Saw pod success
Jun  6 16:20:12.146: INFO: Pod "exec-volume-test-preprovisionedpv-b79s" satisfied condition "Succeeded or Failed"
Jun  6 16:20:12.293: INFO: Trying to get logs from node ip-172-20-62-27.sa-east-1.compute.internal pod exec-volume-test-preprovisionedpv-b79s container exec-container-preprovisionedpv-b79s: <nil>
STEP: delete the pod
Jun  6 16:20:12.596: INFO: Waiting for pod exec-volume-test-preprovisionedpv-b79s to disappear
Jun  6 16:20:12.742: INFO: Pod exec-volume-test-preprovisionedpv-b79s no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-b79s
Jun  6 16:20:12.742: INFO: Deleting pod "exec-volume-test-preprovisionedpv-b79s" in namespace "volume-4809"
STEP: Deleting pv and pvc
Jun  6 16:20:12.888: INFO: Deleting PersistentVolumeClaim "pvc-gb5rs"
Jun  6 16:20:13.035: INFO: Deleting PersistentVolume "aws-fd5kp"
Jun  6 16:20:13.480: INFO: Couldn't delete PD "aws://sa-east-1a/vol-05267ee2913f1e3d8", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05267ee2913f1e3d8 is currently attached to i-0f6cb2f6c0ee35ab2
	status code: 400, request id: c42d4ddd-c7ab-4283-bdea-2c8642b66a9f
Jun  6 16:20:19.273: INFO: Couldn't delete PD "aws://sa-east-1a/vol-05267ee2913f1e3d8", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05267ee2913f1e3d8 is currently attached to i-0f6cb2f6c0ee35ab2
	status code: 400, request id: de2b4ee8-15d5-4a02-9d62-fa0be19ce5c9
Jun  6 16:20:25.065: INFO: Couldn't delete PD "aws://sa-east-1a/vol-05267ee2913f1e3d8", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05267ee2913f1e3d8 is currently attached to i-0f6cb2f6c0ee35ab2
	status code: 400, request id: ee8f8702-ea56-4a38-97f1-b162c4df04a2
Jun  6 16:20:30.904: INFO: Couldn't delete PD "aws://sa-east-1a/vol-05267ee2913f1e3d8", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05267ee2913f1e3d8 is currently attached to i-0f6cb2f6c0ee35ab2
	status code: 400, request id: 8f515a07-0bba-482a-ba51-8ce33a3a8860
Jun  6 16:20:36.759: INFO: Successfully deleted PD "aws://sa-east-1a/vol-05267ee2913f1e3d8".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  6 16:20:36.759: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-4809" for this suite.
... skipping 126 lines ...
Jun  6 16:20:24.715: INFO: Waiting for pod aws-client to disappear
Jun  6 16:20:24.861: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun  6 16:20:24.861: INFO: Deleting PersistentVolumeClaim "pvc-rsxq6"
Jun  6 16:20:25.008: INFO: Deleting PersistentVolume "aws-kqcrm"
Jun  6 16:20:25.929: INFO: Couldn't delete PD "aws://sa-east-1a/vol-0ac53401db7ea904b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ac53401db7ea904b is currently attached to i-05aa00177fdae2cd1
	status code: 400, request id: 9616ac28-eff9-4bd3-971a-299ede3f7a38
Jun  6 16:20:31.700: INFO: Couldn't delete PD "aws://sa-east-1a/vol-0ac53401db7ea904b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ac53401db7ea904b is currently attached to i-05aa00177fdae2cd1
	status code: 400, request id: 2e6f6d9a-4640-414b-8ed7-6bd01a2f548e
Jun  6 16:20:37.533: INFO: Successfully deleted PD "aws://sa-east-1a/vol-0ac53401db7ea904b".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  6 16:20:37.533: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-9459" for this suite.
... skipping 345 lines ...
Jun  6 16:18:48.079: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-3771c5bbs      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-3771    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-3771c5bbs,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-3771    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-3771c5bbs,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-3771    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-3771c5bbs,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-3771c5bbs    83a2b1ca-3268-424d-9142-e20f0e2bf58d 2915 0 2021-06-06 16:18:48 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-06 16:18:48 +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-7dm9v pvc- provisioning-3771  5528ba48-b652-4e98-9766-a8a3202515dc 2948 0 2021-06-06 16:18:48 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-06 16:18:48 +0000 UTC FieldsV1 {"f:metadata":{"f:generateName":{}},"f:spec":{"f:accessModes":{},"f:resources":{"f:requests":{".":{},"f:storage":{}}},"f:storageClassName":{},"f:volumeMode":{}}}}]},Spec:PersistentVolumeClaimSpec{AccessModes:[ReadWriteOnce],Resources:ResourceRequirements{Limits:ResourceList{},Requests:ResourceList{storage: {{1073741824 0} {<nil>} 1Gi BinarySI},},},VolumeName:,Selector:nil,StorageClassName:*provisioning-3771c5bbs,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-48dab3ab-bcb2-4111-9304-82cf2ac9be7a in namespace provisioning-3771
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun  6 16:19:11.721: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-mphsd" in namespace "provisioning-3771" to be "Succeeded or Failed"
Jun  6 16:19:11.868: INFO: Pod "pvc-volume-tester-writer-mphsd": Phase="Pending", Reason="", readiness=false. Elapsed: 146.456072ms
Jun  6 16:19:14.017: INFO: Pod "pvc-volume-tester-writer-mphsd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.296139457s
Jun  6 16:19:16.165: INFO: Pod "pvc-volume-tester-writer-mphsd": Phase="Pending", Reason="", readiness=false. Elapsed: 4.444000836s
Jun  6 16:19:18.317: INFO: Pod "pvc-volume-tester-writer-mphsd": Phase="Pending", Reason="", readiness=false. Elapsed: 6.596041389s
Jun  6 16:19:20.465: INFO: Pod "pvc-volume-tester-writer-mphsd": Phase="Pending", Reason="", readiness=false. Elapsed: 8.743936303s
Jun  6 16:19:22.612: INFO: Pod "pvc-volume-tester-writer-mphsd": Phase="Pending", Reason="", readiness=false. Elapsed: 10.89037874s
... skipping 21 lines ...
Jun  6 16:20:09.857: INFO: Pod "pvc-volume-tester-writer-mphsd": Phase="Pending", Reason="", readiness=false. Elapsed: 58.135330571s
Jun  6 16:20:12.002: INFO: Pod "pvc-volume-tester-writer-mphsd": Phase="Pending", Reason="", readiness=false. Elapsed: 1m0.281141384s
Jun  6 16:20:14.149: INFO: Pod "pvc-volume-tester-writer-mphsd": Phase="Pending", Reason="", readiness=false. Elapsed: 1m2.428154815s
Jun  6 16:20:16.295: INFO: Pod "pvc-volume-tester-writer-mphsd": Phase="Pending", Reason="", readiness=false. Elapsed: 1m4.573576112s
Jun  6 16:20:18.441: INFO: Pod "pvc-volume-tester-writer-mphsd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m6.719738373s
STEP: Saw pod success
Jun  6 16:20:18.441: INFO: Pod "pvc-volume-tester-writer-mphsd" satisfied condition "Succeeded or Failed"
Jun  6 16:20:18.738: INFO: Pod pvc-volume-tester-writer-mphsd has the following logs: 
Jun  6 16:20:18.738: INFO: Deleting pod "pvc-volume-tester-writer-mphsd" in namespace "provisioning-3771"
Jun  6 16:20:18.892: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-mphsd" 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-59-46.sa-east-1.compute.internal"
Jun  6 16:20:19.478: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-ht56m" in namespace "provisioning-3771" to be "Succeeded or Failed"
Jun  6 16:20:19.624: INFO: Pod "pvc-volume-tester-reader-ht56m": Phase="Pending", Reason="", readiness=false. Elapsed: 145.067723ms
Jun  6 16:20:21.770: INFO: Pod "pvc-volume-tester-reader-ht56m": Phase="Pending", Reason="", readiness=false. Elapsed: 2.291706402s
Jun  6 16:20:23.917: INFO: Pod "pvc-volume-tester-reader-ht56m": Phase="Pending", Reason="", readiness=false. Elapsed: 4.438108546s
Jun  6 16:20:26.063: INFO: Pod "pvc-volume-tester-reader-ht56m": Phase="Pending", Reason="", readiness=false. Elapsed: 6.584058104s
Jun  6 16:20:28.208: INFO: Pod "pvc-volume-tester-reader-ht56m": Phase="Pending", Reason="", readiness=false. Elapsed: 8.729958488s
Jun  6 16:20:30.355: INFO: Pod "pvc-volume-tester-reader-ht56m": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.876457089s
STEP: Saw pod success
Jun  6 16:20:30.355: INFO: Pod "pvc-volume-tester-reader-ht56m" satisfied condition "Succeeded or Failed"
Jun  6 16:20:30.648: INFO: Pod pvc-volume-tester-reader-ht56m has the following logs: hello world

Jun  6 16:20:30.648: INFO: Deleting pod "pvc-volume-tester-reader-ht56m" in namespace "provisioning-3771"
Jun  6 16:20:30.802: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-ht56m" to be fully deleted
Jun  6 16:20:30.948: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-7dm9v] to have phase Bound
Jun  6 16:20:31.093: INFO: PersistentVolumeClaim pvc-7dm9v found and phase=Bound (145.369368ms)
... skipping 141 lines ...
Jun  6 16:20:32.278: INFO: Creating resource for dynamic PV
Jun  6 16:20:32.278: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-1528-e2e-sc7qchf
STEP: creating a claim
STEP: Expanding non-expandable pvc
Jun  6 16:20:32.714: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun  6 16:20:33.030: INFO: Error updating pvc ebs.csi.aws.comnvcb9: PersistentVolumeClaim "ebs.csi.aws.comnvcb9" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1528-e2e-sc7qchf",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun  6 16:21:03.611: INFO: Error updating pvc ebs.csi.aws.comnvcb9: PersistentVolumeClaim "ebs.csi.aws.comnvcb9" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 53 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  6 16:20:16.824: 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.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun  6 16:20:17.554: INFO: Creating resource for dynamic PV
Jun  6 16:20:17.554: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-398-e2e-scfsv5d
STEP: creating a claim
Jun  6 16:20:17.700: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-tg2w
STEP: Checking for subpath error in container status
Jun  6 16:20:40.431: INFO: Deleting pod "pod-subpath-test-dynamicpv-tg2w" in namespace "provisioning-398"
Jun  6 16:20:40.577: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-tg2w" to be fully deleted
STEP: Deleting pod
Jun  6 16:20:48.867: INFO: Deleting pod "pod-subpath-test-dynamicpv-tg2w" in namespace "provisioning-398"
STEP: Deleting pvc
Jun  6 16:20:49.303: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comtgzsp"
... skipping 11 lines ...

• [SLOW TEST:48.654 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath file is outside the volume [Slow][LinuxOnly]
    /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [sig-storage] PersistentVolumes [Feature:vsphere][Feature:ReclaimPolicy]
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  6 16:21:04.342: INFO: >>> kubeConfig: /root/.kube/config
... skipping 59 lines ...
Jun  6 16:20:38.706: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-330-e2e-sccrfgd
STEP: creating a claim
Jun  6 16:20:38.853: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Jun  6 16:20:39.145: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun  6 16:20:39.436: INFO: Error updating pvc ebs.csi.aws.comqbrl5: PersistentVolumeClaim "ebs.csi.aws.comqbrl5" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-330-e2e-sccrfgd",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun  6 16:21:10.035: INFO: Error updating pvc ebs.csi.aws.comqbrl5: PersistentVolumeClaim "ebs.csi.aws.comqbrl5" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 38 lines ...
Jun  6 16:20:53.584: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  6 16:20:54.572: INFO: Successfully created a new PD: "aws://sa-east-1a/vol-098d357953eff1c96".
Jun  6 16:20:54.572: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-xptq
STEP: Creating a pod to test exec-volume-test
Jun  6 16:20:54.720: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-xptq" in namespace "volume-982" to be "Succeeded or Failed"
Jun  6 16:20:54.866: INFO: Pod "exec-volume-test-inlinevolume-xptq": Phase="Pending", Reason="", readiness=false. Elapsed: 145.63299ms
Jun  6 16:20:57.012: INFO: Pod "exec-volume-test-inlinevolume-xptq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.292237229s
Jun  6 16:20:59.159: INFO: Pod "exec-volume-test-inlinevolume-xptq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.438864541s
Jun  6 16:21:01.305: INFO: Pod "exec-volume-test-inlinevolume-xptq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.585208713s
Jun  6 16:21:03.451: INFO: Pod "exec-volume-test-inlinevolume-xptq": Phase="Pending", Reason="", readiness=false. Elapsed: 8.731254542s
Jun  6 16:21:05.597: INFO: Pod "exec-volume-test-inlinevolume-xptq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.876764008s
STEP: Saw pod success
Jun  6 16:21:05.597: INFO: Pod "exec-volume-test-inlinevolume-xptq" satisfied condition "Succeeded or Failed"
Jun  6 16:21:05.742: INFO: Trying to get logs from node ip-172-20-62-27.sa-east-1.compute.internal pod exec-volume-test-inlinevolume-xptq container exec-container-inlinevolume-xptq: <nil>
STEP: delete the pod
Jun  6 16:21:06.040: INFO: Waiting for pod exec-volume-test-inlinevolume-xptq to disappear
Jun  6 16:21:06.185: INFO: Pod exec-volume-test-inlinevolume-xptq no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-xptq
Jun  6 16:21:06.185: INFO: Deleting pod "exec-volume-test-inlinevolume-xptq" in namespace "volume-982"
Jun  6 16:21:06.601: INFO: Couldn't delete PD "aws://sa-east-1a/vol-098d357953eff1c96", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-098d357953eff1c96 is currently attached to i-0f6cb2f6c0ee35ab2
	status code: 400, request id: 517a784b-346d-4885-8667-cea9dc9cc8f7
Jun  6 16:21:12.466: INFO: Couldn't delete PD "aws://sa-east-1a/vol-098d357953eff1c96", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-098d357953eff1c96 is currently attached to i-0f6cb2f6c0ee35ab2
	status code: 400, request id: 385510fd-61ab-4bae-b57f-c7e9c5787b59
Jun  6 16:21:18.267: INFO: Successfully deleted PD "aws://sa-east-1a/vol-098d357953eff1c96".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  6 16:21:18.267: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-982" for this suite.
... skipping 23 lines ...
Jun  6 16:20:46.945: INFO: Creating resource for dynamic PV
Jun  6 16:20:46.945: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-5968hb89r
STEP: creating a claim
STEP: Expanding non-expandable pvc
Jun  6 16:20:47.383: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun  6 16:20:47.675: INFO: Error updating pvc awsbrzzg: PersistentVolumeClaim "awsbrzzg" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5968hb89r",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 111 lines ...
Jun  6 16:21:25.190: INFO: Waiting for pod aws-client to disappear
Jun  6 16:21:25.340: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun  6 16:21:25.340: INFO: Deleting PersistentVolumeClaim "pvc-p9wm9"
Jun  6 16:21:25.495: INFO: Deleting PersistentVolume "aws-mpw2z"
Jun  6 16:21:26.421: INFO: Couldn't delete PD "aws://sa-east-1a/vol-08a0144417fad0c52", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08a0144417fad0c52 is currently attached to i-0497bb511a26d2153
	status code: 400, request id: f3caf8fb-b510-4d36-bb04-fefa4e8abc7e
Jun  6 16:21:32.263: INFO: Successfully deleted PD "aws://sa-east-1a/vol-08a0144417fad0c52".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumes
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  6 16:21:32.263: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-3252" for this suite.
... skipping 33 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  6 16:20:57.620: 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.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  6 16:20:58.349: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  6 16:20:59.357: INFO: Successfully created a new PD: "aws://sa-east-1a/vol-0be6a52e6323df493".
Jun  6 16:20:59.357: INFO: Creating resource for pre-provisioned PV
Jun  6 16:20:59.357: INFO: Creating PVC and PV
... skipping 8 lines ...
Jun  6 16:21:10.615: INFO: PersistentVolumeClaim pvc-lnx6w found but phase is Pending instead of Bound.
Jun  6 16:21:12.760: INFO: PersistentVolumeClaim pvc-lnx6w found but phase is Pending instead of Bound.
Jun  6 16:21:14.907: INFO: PersistentVolumeClaim pvc-lnx6w found and phase=Bound (15.16855375s)
Jun  6 16:21:14.907: INFO: Waiting up to 3m0s for PersistentVolume aws-lc8bw to have phase Bound
Jun  6 16:21:15.053: INFO: PersistentVolume aws-lc8bw found and phase=Bound (145.566434ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  6 16:21:17.940: INFO: Deleting pod "pod-bfc61eca-5da2-4458-84c6-9721c434a948" in namespace "volumemode-3533"
Jun  6 16:21:18.089: INFO: Wait up to 5m0s for pod "pod-bfc61eca-5da2-4458-84c6-9721c434a948" to be fully deleted
STEP: Deleting pv and pvc
Jun  6 16:21:24.382: INFO: Deleting PersistentVolumeClaim "pvc-lnx6w"
Jun  6 16:21:24.528: INFO: Deleting PersistentVolume "aws-lc8bw"
Jun  6 16:21:25.033: INFO: Couldn't delete PD "aws://sa-east-1a/vol-0be6a52e6323df493", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0be6a52e6323df493 is currently attached to i-0497bb511a26d2153
	status code: 400, request id: 87c5fada-0b44-41d4-b4cc-bfc33af8c92c
Jun  6 16:21:30.906: INFO: Couldn't delete PD "aws://sa-east-1a/vol-0be6a52e6323df493", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0be6a52e6323df493 is currently attached to i-0497bb511a26d2153
	status code: 400, request id: 5abfd107-0aae-4e64-af8c-3be235878589
Jun  6 16:21:36.657: INFO: Successfully deleted PD "aws://sa-east-1a/vol-0be6a52e6323df493".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  6 16:21:36.657: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-3533" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.42NGBlObb/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.42NGBlObb/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
    /tmp/kops.42NGBlObb/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.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 7 lines ...
Jun  6 16:20:32.732: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3315-e2e-scz6zpm
STEP: creating a claim
Jun  6 16:20:32.878: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-s77k
STEP: Creating a pod to test subpath
Jun  6 16:20:33.316: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-s77k" in namespace "provisioning-3315" to be "Succeeded or Failed"
Jun  6 16:20:33.463: INFO: Pod "pod-subpath-test-dynamicpv-s77k": Phase="Pending", Reason="", readiness=false. Elapsed: 146.723177ms
Jun  6 16:20:35.608: INFO: Pod "pod-subpath-test-dynamicpv-s77k": Phase="Pending", Reason="", readiness=false. Elapsed: 2.292120782s
Jun  6 16:20:37.754: INFO: Pod "pod-subpath-test-dynamicpv-s77k": Phase="Pending", Reason="", readiness=false. Elapsed: 4.438233527s
Jun  6 16:20:39.901: INFO: Pod "pod-subpath-test-dynamicpv-s77k": Phase="Pending", Reason="", readiness=false. Elapsed: 6.585344308s
Jun  6 16:20:42.047: INFO: Pod "pod-subpath-test-dynamicpv-s77k": Phase="Pending", Reason="", readiness=false. Elapsed: 8.730475036s
Jun  6 16:20:44.192: INFO: Pod "pod-subpath-test-dynamicpv-s77k": Phase="Pending", Reason="", readiness=false. Elapsed: 10.876366283s
... skipping 4 lines ...
Jun  6 16:20:54.923: INFO: Pod "pod-subpath-test-dynamicpv-s77k": Phase="Pending", Reason="", readiness=false. Elapsed: 21.60726749s
Jun  6 16:20:57.070: INFO: Pod "pod-subpath-test-dynamicpv-s77k": Phase="Pending", Reason="", readiness=false. Elapsed: 23.75351842s
Jun  6 16:20:59.216: INFO: Pod "pod-subpath-test-dynamicpv-s77k": Phase="Pending", Reason="", readiness=false. Elapsed: 25.899964985s
Jun  6 16:21:01.361: INFO: Pod "pod-subpath-test-dynamicpv-s77k": Phase="Pending", Reason="", readiness=false. Elapsed: 28.045143803s
Jun  6 16:21:03.506: INFO: Pod "pod-subpath-test-dynamicpv-s77k": Phase="Succeeded", Reason="", readiness=false. Elapsed: 30.190321502s
STEP: Saw pod success
Jun  6 16:21:03.506: INFO: Pod "pod-subpath-test-dynamicpv-s77k" satisfied condition "Succeeded or Failed"
Jun  6 16:21:03.653: INFO: Trying to get logs from node ip-172-20-59-101.sa-east-1.compute.internal pod pod-subpath-test-dynamicpv-s77k container test-container-subpath-dynamicpv-s77k: <nil>
STEP: delete the pod
Jun  6 16:21:03.961: INFO: Waiting for pod pod-subpath-test-dynamicpv-s77k to disappear
Jun  6 16:21:04.106: INFO: Pod pod-subpath-test-dynamicpv-s77k no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-s77k
Jun  6 16:21:04.106: INFO: Deleting pod "pod-subpath-test-dynamicpv-s77k" in namespace "provisioning-3315"
... skipping 346 lines ...
Jun  6 16:21:06.210: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-5681r6fk8
STEP: creating a claim
Jun  6 16:21:06.355: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-8dn7
STEP: Creating a pod to test exec-volume-test
Jun  6 16:21:06.795: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-8dn7" in namespace "volume-5681" to be "Succeeded or Failed"
Jun  6 16:21:06.940: INFO: Pod "exec-volume-test-dynamicpv-8dn7": Phase="Pending", Reason="", readiness=false. Elapsed: 145.062556ms
Jun  6 16:21:09.086: INFO: Pod "exec-volume-test-dynamicpv-8dn7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.290900566s
Jun  6 16:21:11.232: INFO: Pod "exec-volume-test-dynamicpv-8dn7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.437258203s
Jun  6 16:21:13.378: INFO: Pod "exec-volume-test-dynamicpv-8dn7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.583150652s
Jun  6 16:21:15.530: INFO: Pod "exec-volume-test-dynamicpv-8dn7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.734785378s
Jun  6 16:21:17.676: INFO: Pod "exec-volume-test-dynamicpv-8dn7": Phase="Pending", Reason="", readiness=false. Elapsed: 10.880619457s
Jun  6 16:21:19.843: INFO: Pod "exec-volume-test-dynamicpv-8dn7": Phase="Pending", Reason="", readiness=false. Elapsed: 13.047767051s
Jun  6 16:21:21.989: INFO: Pod "exec-volume-test-dynamicpv-8dn7": Phase="Pending", Reason="", readiness=false. Elapsed: 15.19432974s
Jun  6 16:21:24.140: INFO: Pod "exec-volume-test-dynamicpv-8dn7": Phase="Pending", Reason="", readiness=false. Elapsed: 17.344682839s
Jun  6 16:21:26.286: INFO: Pod "exec-volume-test-dynamicpv-8dn7": Phase="Pending", Reason="", readiness=false. Elapsed: 19.491490619s
Jun  6 16:21:28.432: INFO: Pod "exec-volume-test-dynamicpv-8dn7": Phase="Running", Reason="", readiness=true. Elapsed: 21.637467909s
Jun  6 16:21:30.579: INFO: Pod "exec-volume-test-dynamicpv-8dn7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.784433619s
STEP: Saw pod success
Jun  6 16:21:30.579: INFO: Pod "exec-volume-test-dynamicpv-8dn7" satisfied condition "Succeeded or Failed"
Jun  6 16:21:30.724: INFO: Trying to get logs from node ip-172-20-62-27.sa-east-1.compute.internal pod exec-volume-test-dynamicpv-8dn7 container exec-container-dynamicpv-8dn7: <nil>
STEP: delete the pod
Jun  6 16:21:31.024: INFO: Waiting for pod exec-volume-test-dynamicpv-8dn7 to disappear
Jun  6 16:21:31.169: INFO: Pod exec-volume-test-dynamicpv-8dn7 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-8dn7
Jun  6 16:21:31.169: INFO: Deleting pod "exec-volume-test-dynamicpv-8dn7" in namespace "volume-5681"
... skipping 31 lines ...

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

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 102 lines ...
Jun  6 16:21:20.315: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5135xwsp7
STEP: creating a claim
Jun  6 16:21:20.461: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-gb85
STEP: Creating a pod to test subpath
Jun  6 16:21:20.901: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-gb85" in namespace "provisioning-5135" to be "Succeeded or Failed"
Jun  6 16:21:21.047: INFO: Pod "pod-subpath-test-dynamicpv-gb85": Phase="Pending", Reason="", readiness=false. Elapsed: 146.036631ms
Jun  6 16:21:23.194: INFO: Pod "pod-subpath-test-dynamicpv-gb85": Phase="Pending", Reason="", readiness=false. Elapsed: 2.293016617s
Jun  6 16:21:25.341: INFO: Pod "pod-subpath-test-dynamicpv-gb85": Phase="Pending", Reason="", readiness=false. Elapsed: 4.440558981s
Jun  6 16:21:27.503: INFO: Pod "pod-subpath-test-dynamicpv-gb85": Phase="Pending", Reason="", readiness=false. Elapsed: 6.602050087s
Jun  6 16:21:29.649: INFO: Pod "pod-subpath-test-dynamicpv-gb85": Phase="Pending", Reason="", readiness=false. Elapsed: 8.747777168s
Jun  6 16:21:31.794: INFO: Pod "pod-subpath-test-dynamicpv-gb85": Phase="Pending", Reason="", readiness=false. Elapsed: 10.893378463s
Jun  6 16:21:33.940: INFO: Pod "pod-subpath-test-dynamicpv-gb85": Phase="Pending", Reason="", readiness=false. Elapsed: 13.03921248s
Jun  6 16:21:36.088: INFO: Pod "pod-subpath-test-dynamicpv-gb85": Phase="Pending", Reason="", readiness=false. Elapsed: 15.186955584s
Jun  6 16:21:38.234: INFO: Pod "pod-subpath-test-dynamicpv-gb85": Phase="Pending", Reason="", readiness=false. Elapsed: 17.333535297s
Jun  6 16:21:40.381: INFO: Pod "pod-subpath-test-dynamicpv-gb85": Phase="Pending", Reason="", readiness=false. Elapsed: 19.479653746s
Jun  6 16:21:42.527: INFO: Pod "pod-subpath-test-dynamicpv-gb85": Phase="Pending", Reason="", readiness=false. Elapsed: 21.625681561s
Jun  6 16:21:44.673: INFO: Pod "pod-subpath-test-dynamicpv-gb85": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.771970061s
STEP: Saw pod success
Jun  6 16:21:44.673: INFO: Pod "pod-subpath-test-dynamicpv-gb85" satisfied condition "Succeeded or Failed"
Jun  6 16:21:44.818: INFO: Trying to get logs from node ip-172-20-62-27.sa-east-1.compute.internal pod pod-subpath-test-dynamicpv-gb85 container test-container-subpath-dynamicpv-gb85: <nil>
STEP: delete the pod
Jun  6 16:21:45.118: INFO: Waiting for pod pod-subpath-test-dynamicpv-gb85 to disappear
Jun  6 16:21:45.263: INFO: Pod pod-subpath-test-dynamicpv-gb85 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-gb85
Jun  6 16:21:45.263: INFO: Deleting pod "pod-subpath-test-dynamicpv-gb85" in namespace "provisioning-5135"
... skipping 303 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.42NGBlObb/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.42NGBlObb/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.42NGBlObb/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.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 175 lines ...
Jun  6 16:21:42.818: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-4363ll8qm
STEP: creating a claim
Jun  6 16:21:42.963: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-rbk8
STEP: Creating a pod to test exec-volume-test
Jun  6 16:21:43.404: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-rbk8" in namespace "volume-4363" to be "Succeeded or Failed"
Jun  6 16:21:43.549: INFO: Pod "exec-volume-test-dynamicpv-rbk8": Phase="Pending", Reason="", readiness=false. Elapsed: 145.304878ms
Jun  6 16:21:45.697: INFO: Pod "exec-volume-test-dynamicpv-rbk8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.293843906s
Jun  6 16:21:47.843: INFO: Pod "exec-volume-test-dynamicpv-rbk8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.43919065s
Jun  6 16:21:49.989: INFO: Pod "exec-volume-test-dynamicpv-rbk8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.585408611s
Jun  6 16:21:52.136: INFO: Pod "exec-volume-test-dynamicpv-rbk8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.73205078s
Jun  6 16:21:54.281: INFO: Pod "exec-volume-test-dynamicpv-rbk8": Phase="Pending", Reason="", readiness=false. Elapsed: 10.877518762s
Jun  6 16:21:56.428: INFO: Pod "exec-volume-test-dynamicpv-rbk8": Phase="Pending", Reason="", readiness=false. Elapsed: 13.024772269s
Jun  6 16:21:58.575: INFO: Pod "exec-volume-test-dynamicpv-rbk8": Phase="Pending", Reason="", readiness=false. Elapsed: 15.171529076s
Jun  6 16:22:00.721: INFO: Pod "exec-volume-test-dynamicpv-rbk8": Phase="Pending", Reason="", readiness=false. Elapsed: 17.317356418s
Jun  6 16:22:02.868: INFO: Pod "exec-volume-test-dynamicpv-rbk8": Phase="Pending", Reason="", readiness=false. Elapsed: 19.464007896s
Jun  6 16:22:05.014: INFO: Pod "exec-volume-test-dynamicpv-rbk8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.610396575s
STEP: Saw pod success
Jun  6 16:22:05.014: INFO: Pod "exec-volume-test-dynamicpv-rbk8" satisfied condition "Succeeded or Failed"
Jun  6 16:22:05.159: INFO: Trying to get logs from node ip-172-20-44-71.sa-east-1.compute.internal pod exec-volume-test-dynamicpv-rbk8 container exec-container-dynamicpv-rbk8: <nil>
STEP: delete the pod
Jun  6 16:22:05.469: INFO: Waiting for pod exec-volume-test-dynamicpv-rbk8 to disappear
Jun  6 16:22:05.614: INFO: Pod exec-volume-test-dynamicpv-rbk8 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-rbk8
Jun  6 16:22:05.614: INFO: Deleting pod "exec-volume-test-dynamicpv-rbk8" in namespace "volume-4363"
... skipping 157 lines ...
Jun  6 16:21:58.737: INFO: PersistentVolumeClaim pvc-vbrw7 found but phase is Pending instead of Bound.
Jun  6 16:22:00.884: INFO: PersistentVolumeClaim pvc-vbrw7 found and phase=Bound (2.293166609s)
Jun  6 16:22:00.884: INFO: Waiting up to 3m0s for PersistentVolume aws-s6r7x to have phase Bound
Jun  6 16:22:01.031: INFO: PersistentVolume aws-s6r7x found and phase=Bound (146.44582ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-nmvk
STEP: Creating a pod to test exec-volume-test
Jun  6 16:22:01.473: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-nmvk" in namespace "volume-1781" to be "Succeeded or Failed"
Jun  6 16:22:01.619: INFO: Pod "exec-volume-test-preprovisionedpv-nmvk": Phase="Pending", Reason="", readiness=false. Elapsed: 146.230526ms
Jun  6 16:22:03.766: INFO: Pod "exec-volume-test-preprovisionedpv-nmvk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.29285386s
Jun  6 16:22:05.912: INFO: Pod "exec-volume-test-preprovisionedpv-nmvk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.439366443s
Jun  6 16:22:08.059: INFO: Pod "exec-volume-test-preprovisionedpv-nmvk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.586551309s
Jun  6 16:22:10.207: INFO: Pod "exec-volume-test-preprovisionedpv-nmvk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.734218952s
Jun  6 16:22:12.354: INFO: Pod "exec-volume-test-preprovisionedpv-nmvk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.881129215s
STEP: Saw pod success
Jun  6 16:22:12.354: INFO: Pod "exec-volume-test-preprovisionedpv-nmvk" satisfied condition "Succeeded or Failed"
Jun  6 16:22:12.502: INFO: Trying to get logs from node ip-172-20-59-101.sa-east-1.compute.internal pod exec-volume-test-preprovisionedpv-nmvk container exec-container-preprovisionedpv-nmvk: <nil>
STEP: delete the pod
Jun  6 16:22:12.805: INFO: Waiting for pod exec-volume-test-preprovisionedpv-nmvk to disappear
Jun  6 16:22:12.951: INFO: Pod exec-volume-test-preprovisionedpv-nmvk no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-nmvk
Jun  6 16:22:12.951: INFO: Deleting pod "exec-volume-test-preprovisionedpv-nmvk" in namespace "volume-1781"
STEP: Deleting pv and pvc
Jun  6 16:22:13.098: INFO: Deleting PersistentVolumeClaim "pvc-vbrw7"
Jun  6 16:22:13.246: INFO: Deleting PersistentVolume "aws-s6r7x"
Jun  6 16:22:13.672: INFO: Couldn't delete PD "aws://sa-east-1a/vol-0cbc1ada6300fd2b2", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0cbc1ada6300fd2b2 is currently attached to i-05aa00177fdae2cd1
	status code: 400, request id: 0f187b65-8433-4139-b7e3-dc8a202f093f
Jun  6 16:22:19.536: INFO: Couldn't delete PD "aws://sa-east-1a/vol-0cbc1ada6300fd2b2", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0cbc1ada6300fd2b2 is currently attached to i-05aa00177fdae2cd1
	status code: 400, request id: c05917aa-c835-41ab-8fe6-9adc9da1bb53
Jun  6 16:22:25.354: INFO: Couldn't delete PD "aws://sa-east-1a/vol-0cbc1ada6300fd2b2", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0cbc1ada6300fd2b2 is currently attached to i-05aa00177fdae2cd1
	status code: 400, request id: b224c9d9-b2c8-4ee4-bcc1-a1fbb9502ddd
Jun  6 16:22:31.243: INFO: Successfully deleted PD "aws://sa-east-1a/vol-0cbc1ada6300fd2b2".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  6 16:22:31.244: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-1781" for this suite.
... skipping 185 lines ...
Jun  6 16:21:43.196: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5150wjdpc
STEP: creating a claim
Jun  6 16:21:43.342: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-g2d4
STEP: Creating a pod to test subpath
Jun  6 16:21:43.787: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-g2d4" in namespace "provisioning-5150" to be "Succeeded or Failed"
Jun  6 16:21:43.932: INFO: Pod "pod-subpath-test-dynamicpv-g2d4": Phase="Pending", Reason="", readiness=false. Elapsed: 144.605458ms
Jun  6 16:21:46.092: INFO: Pod "pod-subpath-test-dynamicpv-g2d4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.304749736s
Jun  6 16:21:48.238: INFO: Pod "pod-subpath-test-dynamicpv-g2d4": Phase="Pending", Reason="", readiness=false. Elapsed: 4.450433011s
Jun  6 16:21:50.384: INFO: Pod "pod-subpath-test-dynamicpv-g2d4": Phase="Pending", Reason="", readiness=false. Elapsed: 6.596618022s
Jun  6 16:21:52.530: INFO: Pod "pod-subpath-test-dynamicpv-g2d4": Phase="Pending", Reason="", readiness=false. Elapsed: 8.743082456s
Jun  6 16:21:54.675: INFO: Pod "pod-subpath-test-dynamicpv-g2d4": Phase="Pending", Reason="", readiness=false. Elapsed: 10.888036584s
Jun  6 16:21:56.821: INFO: Pod "pod-subpath-test-dynamicpv-g2d4": Phase="Pending", Reason="", readiness=false. Elapsed: 13.033295891s
Jun  6 16:21:58.981: INFO: Pod "pod-subpath-test-dynamicpv-g2d4": Phase="Pending", Reason="", readiness=false. Elapsed: 15.193465171s
Jun  6 16:22:01.126: INFO: Pod "pod-subpath-test-dynamicpv-g2d4": Phase="Pending", Reason="", readiness=false. Elapsed: 17.338872194s
Jun  6 16:22:03.272: INFO: Pod "pod-subpath-test-dynamicpv-g2d4": Phase="Pending", Reason="", readiness=false. Elapsed: 19.484133524s
Jun  6 16:22:05.422: INFO: Pod "pod-subpath-test-dynamicpv-g2d4": Phase="Pending", Reason="", readiness=false. Elapsed: 21.634115745s
Jun  6 16:22:07.568: INFO: Pod "pod-subpath-test-dynamicpv-g2d4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.780610585s
STEP: Saw pod success
Jun  6 16:22:07.568: INFO: Pod "pod-subpath-test-dynamicpv-g2d4" satisfied condition "Succeeded or Failed"
Jun  6 16:22:07.713: INFO: Trying to get logs from node ip-172-20-62-27.sa-east-1.compute.internal pod pod-subpath-test-dynamicpv-g2d4 container test-container-volume-dynamicpv-g2d4: <nil>
STEP: delete the pod
Jun  6 16:22:08.017: INFO: Waiting for pod pod-subpath-test-dynamicpv-g2d4 to disappear
Jun  6 16:22:08.162: INFO: Pod pod-subpath-test-dynamicpv-g2d4 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-g2d4
Jun  6 16:22:08.162: INFO: Deleting pod "pod-subpath-test-dynamicpv-g2d4" in namespace "provisioning-5150"
... skipping 108 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.42NGBlObb/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.42NGBlObb/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.42NGBlObb/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.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 48 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  6 16:22:00.990: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename provisioning
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly]
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun  6 16:22:01.713: INFO: Creating resource for dynamic PV
Jun  6 16:22:01.713: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7030-e2e-scr87cz
STEP: creating a claim
Jun  6 16:22:01.859: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-rbwv
STEP: Checking for subpath error in container status
Jun  6 16:22:18.590: INFO: Deleting pod "pod-subpath-test-dynamicpv-rbwv" in namespace "provisioning-7030"
Jun  6 16:22:18.736: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-rbwv" to be fully deleted
STEP: Deleting pod
Jun  6 16:22:31.026: INFO: Deleting pod "pod-subpath-test-dynamicpv-rbwv" in namespace "provisioning-7030"
STEP: Deleting pvc
Jun  6 16:22:31.461: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comnbgff"
... skipping 10 lines ...

• [SLOW TEST:41.493 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.42NGBlObb/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.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  6 16:22:42.485: INFO: Driver "ebs.csi.aws.com" does not support volume type "InlineVolume" - skipping
[AfterEach] [Testpattern: Inline-volume (default fs)] subPath
... skipping 418 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  6 16:22:21.844: 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.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  6 16:22:22.580: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  6 16:22:22.580: INFO: Creating resource for dynamic PV
Jun  6 16:22:22.580: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-45287bqlh
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  6 16:22:29.609: INFO: Deleting pod "pod-44a94212-25cc-4ce9-947d-7c87ca8cff51" in namespace "volumemode-4528"
Jun  6 16:22:29.757: INFO: Wait up to 5m0s for pod "pod-44a94212-25cc-4ce9-947d-7c87ca8cff51" to be fully deleted
STEP: Deleting pvc
Jun  6 16:22:36.343: INFO: Deleting PersistentVolumeClaim "awsz9hjc"
Jun  6 16:22:36.490: INFO: Waiting up to 5m0s for PersistentVolume pvc-e21f0481-4c18-49aa-9f40-2e6020652dc3 to get deleted
Jun  6 16:22:36.636: INFO: PersistentVolume pvc-e21f0481-4c18-49aa-9f40-2e6020652dc3 found and phase=Released (146.29359ms)
... skipping 11 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.42NGBlObb/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.42NGBlObb/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
    /tmp/kops.42NGBlObb/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.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  6 16:22:52.530: INFO: Driver ebs.csi.aws.com doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
... skipping 2 lines ...

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

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

    /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 11 lines ...
Jun  6 16:21:33.298: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2317-e2e-sc7ctln
STEP: creating a claim
Jun  6 16:21:33.446: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-9xgc
STEP: Creating a pod to test subpath
Jun  6 16:21:33.892: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-9xgc" in namespace "provisioning-2317" to be "Succeeded or Failed"
Jun  6 16:21:34.038: INFO: Pod "pod-subpath-test-dynamicpv-9xgc": Phase="Pending", Reason="", readiness=false. Elapsed: 146.186716ms
Jun  6 16:21:36.185: INFO: Pod "pod-subpath-test-dynamicpv-9xgc": Phase="Pending", Reason="", readiness=false. Elapsed: 2.29266254s
Jun  6 16:21:38.332: INFO: Pod "pod-subpath-test-dynamicpv-9xgc": Phase="Pending", Reason="", readiness=false. Elapsed: 4.439626889s
Jun  6 16:21:40.478: INFO: Pod "pod-subpath-test-dynamicpv-9xgc": Phase="Pending", Reason="", readiness=false. Elapsed: 6.585999136s
Jun  6 16:21:42.627: INFO: Pod "pod-subpath-test-dynamicpv-9xgc": Phase="Pending", Reason="", readiness=false. Elapsed: 8.735190925s
Jun  6 16:21:44.774: INFO: Pod "pod-subpath-test-dynamicpv-9xgc": Phase="Pending", Reason="", readiness=false. Elapsed: 10.882224469s
... skipping 9 lines ...
Jun  6 16:22:06.276: INFO: Pod "pod-subpath-test-dynamicpv-9xgc": Phase="Pending", Reason="", readiness=false. Elapsed: 32.383868033s
Jun  6 16:22:08.423: INFO: Pod "pod-subpath-test-dynamicpv-9xgc": Phase="Pending", Reason="", readiness=false. Elapsed: 34.531422088s
Jun  6 16:22:10.570: INFO: Pod "pod-subpath-test-dynamicpv-9xgc": Phase="Pending", Reason="", readiness=false. Elapsed: 36.678379312s
Jun  6 16:22:12.718: INFO: Pod "pod-subpath-test-dynamicpv-9xgc": Phase="Pending", Reason="", readiness=false. Elapsed: 38.826081029s
Jun  6 16:22:14.866: INFO: Pod "pod-subpath-test-dynamicpv-9xgc": Phase="Succeeded", Reason="", readiness=false. Elapsed: 40.97372427s
STEP: Saw pod success
Jun  6 16:22:14.866: INFO: Pod "pod-subpath-test-dynamicpv-9xgc" satisfied condition "Succeeded or Failed"
Jun  6 16:22:15.012: INFO: Trying to get logs from node ip-172-20-59-101.sa-east-1.compute.internal pod pod-subpath-test-dynamicpv-9xgc container test-container-volume-dynamicpv-9xgc: <nil>
STEP: delete the pod
Jun  6 16:22:15.317: INFO: Waiting for pod pod-subpath-test-dynamicpv-9xgc to disappear
Jun  6 16:22:15.465: INFO: Pod pod-subpath-test-dynamicpv-9xgc no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-9xgc
Jun  6 16:22:15.465: INFO: Deleting pod "pod-subpath-test-dynamicpv-9xgc" in namespace "provisioning-2317"
... skipping 178 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.42NGBlObb/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.42NGBlObb/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.42NGBlObb/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.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 111 lines ...
Jun  6 16:22:54.895: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 266 lines ...
Jun  6 16:22:35.947: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  6 16:22:36.889: INFO: Successfully created a new PD: "aws://sa-east-1a/vol-06af6d80fb2c2b207".
Jun  6 16:22:36.889: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-hvrs
STEP: Creating a pod to test exec-volume-test
Jun  6 16:22:37.039: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-hvrs" in namespace "volume-2382" to be "Succeeded or Failed"
Jun  6 16:22:37.184: INFO: Pod "exec-volume-test-inlinevolume-hvrs": Phase="Pending", Reason="", readiness=false. Elapsed: 145.005956ms
Jun  6 16:22:39.330: INFO: Pod "exec-volume-test-inlinevolume-hvrs": Phase="Pending", Reason="", readiness=false. Elapsed: 2.290416318s
Jun  6 16:22:41.475: INFO: Pod "exec-volume-test-inlinevolume-hvrs": Phase="Pending", Reason="", readiness=false. Elapsed: 4.43548842s
Jun  6 16:22:43.622: INFO: Pod "exec-volume-test-inlinevolume-hvrs": Phase="Pending", Reason="", readiness=false. Elapsed: 6.582087749s
Jun  6 16:22:45.767: INFO: Pod "exec-volume-test-inlinevolume-hvrs": Phase="Pending", Reason="", readiness=false. Elapsed: 8.727521894s
Jun  6 16:22:47.912: INFO: Pod "exec-volume-test-inlinevolume-hvrs": Phase="Pending", Reason="", readiness=false. Elapsed: 10.873030377s
Jun  6 16:22:50.059: INFO: Pod "exec-volume-test-inlinevolume-hvrs": Phase="Pending", Reason="", readiness=false. Elapsed: 13.01945386s
Jun  6 16:22:52.204: INFO: Pod "exec-volume-test-inlinevolume-hvrs": Phase="Succeeded", Reason="", readiness=false. Elapsed: 15.164835488s
STEP: Saw pod success
Jun  6 16:22:52.204: INFO: Pod "exec-volume-test-inlinevolume-hvrs" satisfied condition "Succeeded or Failed"
Jun  6 16:22:52.349: INFO: Trying to get logs from node ip-172-20-59-46.sa-east-1.compute.internal pod exec-volume-test-inlinevolume-hvrs container exec-container-inlinevolume-hvrs: <nil>
STEP: delete the pod
Jun  6 16:22:52.675: INFO: Waiting for pod exec-volume-test-inlinevolume-hvrs to disappear
Jun  6 16:22:52.822: INFO: Pod exec-volume-test-inlinevolume-hvrs no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-hvrs
Jun  6 16:22:52.822: INFO: Deleting pod "exec-volume-test-inlinevolume-hvrs" in namespace "volume-2382"
Jun  6 16:22:53.236: INFO: Couldn't delete PD "aws://sa-east-1a/vol-06af6d80fb2c2b207", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-06af6d80fb2c2b207 is currently attached to i-0497bb511a26d2153
	status code: 400, request id: be28e29e-9091-4bdf-87b0-921e1c9fcdbf
Jun  6 16:22:58.992: INFO: Couldn't delete PD "aws://sa-east-1a/vol-06af6d80fb2c2b207", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-06af6d80fb2c2b207 is currently attached to i-0497bb511a26d2153
	status code: 400, request id: 018253a4-cd43-479a-bdeb-dbfeca42eb3e
Jun  6 16:23:04.792: INFO: Successfully deleted PD "aws://sa-east-1a/vol-06af6d80fb2c2b207".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  6 16:23:04.792: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-2382" for this suite.
... skipping 269 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  6 16:21:36.951: 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.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun  6 16:21:37.679: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  6 16:21:37.679: INFO: Creating resource for dynamic PV
Jun  6 16:21:37.679: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1127fxr48
STEP: creating a claim
Jun  6 16:21:37.824: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-g667
STEP: Checking for subpath error in container status
Jun  6 16:22:50.557: INFO: Deleting pod "pod-subpath-test-dynamicpv-g667" in namespace "provisioning-1127"
Jun  6 16:22:50.707: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-g667" to be fully deleted
STEP: Deleting pod
Jun  6 16:23:04.998: INFO: Deleting pod "pod-subpath-test-dynamicpv-g667" in namespace "provisioning-1127"
STEP: Deleting pvc
Jun  6 16:23:05.438: INFO: Deleting PersistentVolumeClaim "awsdbs48"
... skipping 11 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.42NGBlObb/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.42NGBlObb/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath file is outside the volume [Slow][LinuxOnly]
      /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 136 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.42NGBlObb/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.42NGBlObb/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.42NGBlObb/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.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 11 lines ...
Jun  6 16:21:54.702: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4008-e2e-scxg7l7
STEP: creating a claim
Jun  6 16:21:54.850: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-66f9
STEP: Creating a pod to test atomic-volume-subpath
Jun  6 16:21:55.290: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-66f9" in namespace "provisioning-4008" to be "Succeeded or Failed"
Jun  6 16:21:55.437: INFO: Pod "pod-subpath-test-dynamicpv-66f9": Phase="Pending", Reason="", readiness=false. Elapsed: 147.642117ms
Jun  6 16:21:57.583: INFO: Pod "pod-subpath-test-dynamicpv-66f9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.293435092s
Jun  6 16:21:59.737: INFO: Pod "pod-subpath-test-dynamicpv-66f9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.447438681s
Jun  6 16:22:01.883: INFO: Pod "pod-subpath-test-dynamicpv-66f9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.59325477s
Jun  6 16:22:04.029: INFO: Pod "pod-subpath-test-dynamicpv-66f9": Phase="Pending", Reason="", readiness=false. Elapsed: 8.739162653s
Jun  6 16:22:06.183: INFO: Pod "pod-subpath-test-dynamicpv-66f9": Phase="Pending", Reason="", readiness=false. Elapsed: 10.893150273s
... skipping 10 lines ...
Jun  6 16:22:29.792: INFO: Pod "pod-subpath-test-dynamicpv-66f9": Phase="Running", Reason="", readiness=true. Elapsed: 34.501915295s
Jun  6 16:22:31.939: INFO: Pod "pod-subpath-test-dynamicpv-66f9": Phase="Running", Reason="", readiness=true. Elapsed: 36.649610662s
Jun  6 16:22:34.087: INFO: Pod "pod-subpath-test-dynamicpv-66f9": Phase="Running", Reason="", readiness=true. Elapsed: 38.796897554s
Jun  6 16:22:36.232: INFO: Pod "pod-subpath-test-dynamicpv-66f9": Phase="Running", Reason="", readiness=true. Elapsed: 40.942656777s
Jun  6 16:22:38.379: INFO: Pod "pod-subpath-test-dynamicpv-66f9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 43.089048622s
STEP: Saw pod success
Jun  6 16:22:38.379: INFO: Pod "pod-subpath-test-dynamicpv-66f9" satisfied condition "Succeeded or Failed"
Jun  6 16:22:38.524: INFO: Trying to get logs from node ip-172-20-59-46.sa-east-1.compute.internal pod pod-subpath-test-dynamicpv-66f9 container test-container-subpath-dynamicpv-66f9: <nil>
STEP: delete the pod
Jun  6 16:22:38.830: INFO: Waiting for pod pod-subpath-test-dynamicpv-66f9 to disappear
Jun  6 16:22:38.975: INFO: Pod pod-subpath-test-dynamicpv-66f9 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-66f9
Jun  6 16:22:38.975: INFO: Deleting pod "pod-subpath-test-dynamicpv-66f9" in namespace "provisioning-4008"
... skipping 221 lines ...
Jun  6 16:23:22.898: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 293 lines ...
Jun  6 16:22:35.386: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3033-e2e-scrxkc2
STEP: creating a claim
Jun  6 16:22:35.534: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-jcrh
STEP: Creating a pod to test multi_subpath
Jun  6 16:22:35.979: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-jcrh" in namespace "provisioning-3033" to be "Succeeded or Failed"
Jun  6 16:22:36.125: INFO: Pod "pod-subpath-test-dynamicpv-jcrh": Phase="Pending", Reason="", readiness=false. Elapsed: 146.330529ms
Jun  6 16:22:38.274: INFO: Pod "pod-subpath-test-dynamicpv-jcrh": Phase="Pending", Reason="", readiness=false. Elapsed: 2.294633415s
Jun  6 16:22:40.424: INFO: Pod "pod-subpath-test-dynamicpv-jcrh": Phase="Pending", Reason="", readiness=false. Elapsed: 4.445180995s
Jun  6 16:22:42.571: INFO: Pod "pod-subpath-test-dynamicpv-jcrh": Phase="Pending", Reason="", readiness=false. Elapsed: 6.592068282s
Jun  6 16:22:44.717: INFO: Pod "pod-subpath-test-dynamicpv-jcrh": Phase="Pending", Reason="", readiness=false. Elapsed: 8.738348335s
Jun  6 16:22:46.864: INFO: Pod "pod-subpath-test-dynamicpv-jcrh": Phase="Pending", Reason="", readiness=false. Elapsed: 10.884632014s
Jun  6 16:22:49.010: INFO: Pod "pod-subpath-test-dynamicpv-jcrh": Phase="Pending", Reason="", readiness=false. Elapsed: 13.031111575s
Jun  6 16:22:51.157: INFO: Pod "pod-subpath-test-dynamicpv-jcrh": Phase="Pending", Reason="", readiness=false. Elapsed: 15.17825723s
Jun  6 16:22:53.305: INFO: Pod "pod-subpath-test-dynamicpv-jcrh": Phase="Pending", Reason="", readiness=false. Elapsed: 17.325582902s
Jun  6 16:22:55.455: INFO: Pod "pod-subpath-test-dynamicpv-jcrh": Phase="Pending", Reason="", readiness=false. Elapsed: 19.476348851s
Jun  6 16:22:57.602: INFO: Pod "pod-subpath-test-dynamicpv-jcrh": Phase="Pending", Reason="", readiness=false. Elapsed: 21.623193326s
Jun  6 16:22:59.751: INFO: Pod "pod-subpath-test-dynamicpv-jcrh": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.771495027s
STEP: Saw pod success
Jun  6 16:22:59.751: INFO: Pod "pod-subpath-test-dynamicpv-jcrh" satisfied condition "Succeeded or Failed"
Jun  6 16:22:59.896: INFO: Trying to get logs from node ip-172-20-62-27.sa-east-1.compute.internal pod pod-subpath-test-dynamicpv-jcrh container test-container-subpath-dynamicpv-jcrh: <nil>
STEP: delete the pod
Jun  6 16:23:00.213: INFO: Waiting for pod pod-subpath-test-dynamicpv-jcrh to disappear
Jun  6 16:23:00.361: INFO: Pod pod-subpath-test-dynamicpv-jcrh no longer exists
STEP: Deleting pod
Jun  6 16:23:00.361: INFO: Deleting pod "pod-subpath-test-dynamicpv-jcrh" in namespace "provisioning-3033"
... skipping 278 lines ...
STEP: Deleting pod hostexec-ip-172-20-59-46.sa-east-1.compute.internal-5gdvh in namespace volumemode-4702
Jun  6 16:23:24.740: INFO: Deleting pod "pod-aa3ea763-89b0-4f7e-abc7-1e70d306bc57" in namespace "volumemode-4702"
Jun  6 16:23:24.887: INFO: Wait up to 5m0s for pod "pod-aa3ea763-89b0-4f7e-abc7-1e70d306bc57" to be fully deleted
STEP: Deleting pv and pvc
Jun  6 16:23:35.179: INFO: Deleting PersistentVolumeClaim "pvc-p9zk7"
Jun  6 16:23:35.326: INFO: Deleting PersistentVolume "aws-cc6l7"
Jun  6 16:23:35.798: INFO: Couldn't delete PD "aws://sa-east-1a/vol-0304b23eb31d4acd9", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0304b23eb31d4acd9 is currently attached to i-0497bb511a26d2153
	status code: 400, request id: 066fdb4f-9a6f-4c2f-a40a-2b32aa80e5d3
Jun  6 16:23:41.612: INFO: Successfully deleted PD "aws://sa-east-1a/vol-0304b23eb31d4acd9".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  6 16:23:41.612: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-4702" for this suite.
... skipping 37 lines ...

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

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

    /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:92
------------------------------
... skipping 57 lines ...
Jun  6 16:22:44.250: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2441-e2e-scpt9qz
STEP: creating a claim
Jun  6 16:22:44.397: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-sz2b
STEP: Creating a pod to test subpath
Jun  6 16:22:44.838: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-sz2b" in namespace "provisioning-2441" to be "Succeeded or Failed"
Jun  6 16:22:44.983: INFO: Pod "pod-subpath-test-dynamicpv-sz2b": Phase="Pending", Reason="", readiness=false. Elapsed: 145.269802ms
Jun  6 16:22:47.129: INFO: Pod "pod-subpath-test-dynamicpv-sz2b": Phase="Pending", Reason="", readiness=false. Elapsed: 2.291032907s
Jun  6 16:22:49.275: INFO: Pod "pod-subpath-test-dynamicpv-sz2b": Phase="Pending", Reason="", readiness=false. Elapsed: 4.437221181s
Jun  6 16:22:51.421: INFO: Pod "pod-subpath-test-dynamicpv-sz2b": Phase="Pending", Reason="", readiness=false. Elapsed: 6.583455651s
Jun  6 16:22:53.566: INFO: Pod "pod-subpath-test-dynamicpv-sz2b": Phase="Pending", Reason="", readiness=false. Elapsed: 8.728174355s
Jun  6 16:22:55.712: INFO: Pod "pod-subpath-test-dynamicpv-sz2b": Phase="Pending", Reason="", readiness=false. Elapsed: 10.874094675s
Jun  6 16:22:57.866: INFO: Pod "pod-subpath-test-dynamicpv-sz2b": Phase="Pending", Reason="", readiness=false. Elapsed: 13.028070665s
Jun  6 16:23:00.013: INFO: Pod "pod-subpath-test-dynamicpv-sz2b": Phase="Pending", Reason="", readiness=false. Elapsed: 15.175396393s
Jun  6 16:23:02.159: INFO: Pod "pod-subpath-test-dynamicpv-sz2b": Phase="Pending", Reason="", readiness=false. Elapsed: 17.321496679s
Jun  6 16:23:04.305: INFO: Pod "pod-subpath-test-dynamicpv-sz2b": Phase="Pending", Reason="", readiness=false. Elapsed: 19.467135674s
Jun  6 16:23:06.449: INFO: Pod "pod-subpath-test-dynamicpv-sz2b": Phase="Pending", Reason="", readiness=false. Elapsed: 21.61168446s
Jun  6 16:23:08.595: INFO: Pod "pod-subpath-test-dynamicpv-sz2b": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.757012008s
STEP: Saw pod success
Jun  6 16:23:08.595: INFO: Pod "pod-subpath-test-dynamicpv-sz2b" satisfied condition "Succeeded or Failed"
Jun  6 16:23:08.739: INFO: Trying to get logs from node ip-172-20-62-27.sa-east-1.compute.internal pod pod-subpath-test-dynamicpv-sz2b container test-container-subpath-dynamicpv-sz2b: <nil>
STEP: delete the pod
Jun  6 16:23:09.038: INFO: Waiting for pod pod-subpath-test-dynamicpv-sz2b to disappear
Jun  6 16:23:09.182: INFO: Pod pod-subpath-test-dynamicpv-sz2b no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-sz2b
Jun  6 16:23:09.182: INFO: Deleting pod "pod-subpath-test-dynamicpv-sz2b" in namespace "provisioning-2441"
... skipping 34 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.42NGBlObb/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.42NGBlObb/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.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 213 lines ...
Jun  6 16:22:54.630: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9767jl7sd
STEP: creating a claim
Jun  6 16:22:54.778: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-dhcw
STEP: Creating a pod to test subpath
Jun  6 16:22:55.224: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-dhcw" in namespace "provisioning-9767" to be "Succeeded or Failed"
Jun  6 16:22:55.371: INFO: Pod "pod-subpath-test-dynamicpv-dhcw": Phase="Pending", Reason="", readiness=false. Elapsed: 147.229887ms
Jun  6 16:22:57.518: INFO: Pod "pod-subpath-test-dynamicpv-dhcw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.294272971s
Jun  6 16:22:59.666: INFO: Pod "pod-subpath-test-dynamicpv-dhcw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.441654967s
Jun  6 16:23:01.813: INFO: Pod "pod-subpath-test-dynamicpv-dhcw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.588946338s
Jun  6 16:23:03.960: INFO: Pod "pod-subpath-test-dynamicpv-dhcw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.736125984s
Jun  6 16:23:06.106: INFO: Pod "pod-subpath-test-dynamicpv-dhcw": Phase="Pending", Reason="", readiness=false. Elapsed: 10.882175664s
... skipping 9 lines ...
Jun  6 16:23:27.579: INFO: Pod "pod-subpath-test-dynamicpv-dhcw": Phase="Pending", Reason="", readiness=false. Elapsed: 32.354731247s
Jun  6 16:23:29.726: INFO: Pod "pod-subpath-test-dynamicpv-dhcw": Phase="Pending", Reason="", readiness=false. Elapsed: 34.501615831s
Jun  6 16:23:31.873: INFO: Pod "pod-subpath-test-dynamicpv-dhcw": Phase="Pending", Reason="", readiness=false. Elapsed: 36.648873789s
Jun  6 16:23:34.022: INFO: Pod "pod-subpath-test-dynamicpv-dhcw": Phase="Pending", Reason="", readiness=false. Elapsed: 38.798233488s
Jun  6 16:23:36.170: INFO: Pod "pod-subpath-test-dynamicpv-dhcw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 40.945841403s
STEP: Saw pod success
Jun  6 16:23:36.170: INFO: Pod "pod-subpath-test-dynamicpv-dhcw" satisfied condition "Succeeded or Failed"
Jun  6 16:23:36.316: INFO: Trying to get logs from node ip-172-20-44-71.sa-east-1.compute.internal pod pod-subpath-test-dynamicpv-dhcw container test-container-subpath-dynamicpv-dhcw: <nil>
STEP: delete the pod
Jun  6 16:23:36.617: INFO: Waiting for pod pod-subpath-test-dynamicpv-dhcw to disappear
Jun  6 16:23:36.763: INFO: Pod pod-subpath-test-dynamicpv-dhcw no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-dhcw
Jun  6 16:23:36.763: INFO: Deleting pod "pod-subpath-test-dynamicpv-dhcw" in namespace "provisioning-9767"
... skipping 149 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  6 16:23:23.030: 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.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun  6 16:23:23.749: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  6 16:23:23.749: INFO: Creating resource for dynamic PV
Jun  6 16:23:23.750: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-35594fj2k
STEP: creating a claim
Jun  6 16:23:23.897: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-4fg7
STEP: Checking for subpath error in container status
Jun  6 16:23:42.639: INFO: Deleting pod "pod-subpath-test-dynamicpv-4fg7" in namespace "provisioning-3559"
Jun  6 16:23:42.790: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-4fg7" to be fully deleted
STEP: Deleting pod
Jun  6 16:23:55.081: INFO: Deleting pod "pod-subpath-test-dynamicpv-4fg7" in namespace "provisioning-3559"
STEP: Deleting pvc
Jun  6 16:23:55.514: INFO: Deleting PersistentVolumeClaim "awspcd2m"
... skipping 12 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.42NGBlObb/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.42NGBlObb/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.42NGBlObb/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.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 7 lines ...
Jun  6 16:22:55.629: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5855-e2e-scptqjr
STEP: creating a claim
Jun  6 16:22:55.785: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-r2jz
STEP: Creating a pod to test subpath
Jun  6 16:22:56.229: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-r2jz" in namespace "provisioning-5855" to be "Succeeded or Failed"
Jun  6 16:22:56.375: INFO: Pod "pod-subpath-test-dynamicpv-r2jz": Phase="Pending", Reason="", readiness=false. Elapsed: 146.199396ms
Jun  6 16:22:58.523: INFO: Pod "pod-subpath-test-dynamicpv-r2jz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.293991402s
Jun  6 16:23:00.670: INFO: Pod "pod-subpath-test-dynamicpv-r2jz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.441171561s
Jun  6 16:23:02.817: INFO: Pod "pod-subpath-test-dynamicpv-r2jz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.587632801s
Jun  6 16:23:04.964: INFO: Pod "pod-subpath-test-dynamicpv-r2jz": Phase="Pending", Reason="", readiness=false. Elapsed: 8.73491553s
Jun  6 16:23:07.116: INFO: Pod "pod-subpath-test-dynamicpv-r2jz": Phase="Pending", Reason="", readiness=false. Elapsed: 10.886676118s
... skipping 10 lines ...
Jun  6 16:23:30.743: INFO: Pod "pod-subpath-test-dynamicpv-r2jz": Phase="Pending", Reason="", readiness=false. Elapsed: 34.513986027s
Jun  6 16:23:32.891: INFO: Pod "pod-subpath-test-dynamicpv-r2jz": Phase="Pending", Reason="", readiness=false. Elapsed: 36.66220148s
Jun  6 16:23:35.039: INFO: Pod "pod-subpath-test-dynamicpv-r2jz": Phase="Pending", Reason="", readiness=false. Elapsed: 38.809611663s
Jun  6 16:23:37.186: INFO: Pod "pod-subpath-test-dynamicpv-r2jz": Phase="Pending", Reason="", readiness=false. Elapsed: 40.956483677s
Jun  6 16:23:39.333: INFO: Pod "pod-subpath-test-dynamicpv-r2jz": Phase="Succeeded", Reason="", readiness=false. Elapsed: 43.103528682s
STEP: Saw pod success
Jun  6 16:23:39.333: INFO: Pod "pod-subpath-test-dynamicpv-r2jz" satisfied condition "Succeeded or Failed"
Jun  6 16:23:39.480: INFO: Trying to get logs from node ip-172-20-44-71.sa-east-1.compute.internal pod pod-subpath-test-dynamicpv-r2jz container test-container-volume-dynamicpv-r2jz: <nil>
STEP: delete the pod
Jun  6 16:23:39.778: INFO: Waiting for pod pod-subpath-test-dynamicpv-r2jz to disappear
Jun  6 16:23:39.924: INFO: Pod pod-subpath-test-dynamicpv-r2jz no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-r2jz
Jun  6 16:23:39.924: INFO: Deleting pod "pod-subpath-test-dynamicpv-r2jz" in namespace "provisioning-5855"
... skipping 705 lines ...

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

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 334 lines ...

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

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

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

    /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 41 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.42NGBlObb/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.42NGBlObb/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.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 185 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  6 16:24:42.028: 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.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  6 16:24:42.755: INFO: Creating resource for dynamic PV
Jun  6 16:24:42.755: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-3596-e2e-sclbbc6
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  6 16:24:49.791: INFO: Deleting pod "pod-a5be0ba7-41a7-4fd9-8791-3435e7a0c4e5" in namespace "volumemode-3596"
Jun  6 16:24:49.938: INFO: Wait up to 5m0s for pod "pod-a5be0ba7-41a7-4fd9-8791-3435e7a0c4e5" to be fully deleted
STEP: Deleting pvc
Jun  6 16:24:58.519: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comrpctt"
Jun  6 16:24:58.665: INFO: Waiting up to 5m0s for PersistentVolume pvc-822f55be-1e07-454d-a082-498451f22c29 to get deleted
Jun  6 16:24:58.810: INFO: PersistentVolume pvc-822f55be-1e07-454d-a082-498451f22c29 found and phase=Released (145.066545ms)
... skipping 8 lines ...

• [SLOW TEST:27.525 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.42NGBlObb/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.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  6 16:25:09.555: INFO: Driver ebs.csi.aws.com doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
... skipping 247 lines ...
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  6 16:25:18.713: 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.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Jun  6 16:25:19.598: INFO: found topology map[topology.kubernetes.io/zone:sa-east-1a]
Jun  6 16:25:19.599: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  6 16:25:19.599: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.42NGBlObb/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.42NGBlObb/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (delayed binding)] topology
    /tmp/kops.42NGBlObb/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.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 235 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  6 16:24:59.272: 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.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  6 16:24:59.997: INFO: Creating resource for dynamic PV
Jun  6 16:24:59.997: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-5488-e2e-scl5c4g
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  6 16:25:07.021: INFO: Deleting pod "pod-fc1b96e3-ea15-4fd0-b487-a43e76ece38a" in namespace "volumemode-5488"
Jun  6 16:25:07.166: INFO: Wait up to 5m0s for pod "pod-fc1b96e3-ea15-4fd0-b487-a43e76ece38a" to be fully deleted
STEP: Deleting pvc
Jun  6 16:25:15.757: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comj6jxx"
Jun  6 16:25:15.902: INFO: Waiting up to 5m0s for PersistentVolume pvc-cc117779-3f82-445d-a0fb-3731279c7258 to get deleted
Jun  6 16:25:16.049: INFO: PersistentVolume pvc-cc117779-3f82-445d-a0fb-3731279c7258 found and phase=Released (147.170881ms)
... skipping 8 lines ...

• [SLOW TEST:27.516 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.42NGBlObb/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.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  6 16:25:26.789: INFO: Driver "ebs.csi.aws.com" does not support topology - skipping
[AfterEach] [Testpattern: Dynamic PV (immediate binding)] topology
... skipping 2 lines ...

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

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

    /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:92
------------------------------
... skipping 350 lines ...
Jun  6 16:23:28.837: INFO: Creating resource for dynamic PV
Jun  6 16:23:28.837: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-9579-e2e-sctc9zv
STEP: creating a claim
Jun  6 16:23:28.982: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun  6 16:23:29.422: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-4449x" in namespace "snapshotting-9579" to be "Succeeded or Failed"
Jun  6 16:23:29.566: INFO: Pod "pvc-snapshottable-tester-4449x": Phase="Pending", Reason="", readiness=false. Elapsed: 144.036697ms
Jun  6 16:23:31.710: INFO: Pod "pvc-snapshottable-tester-4449x": Phase="Pending", Reason="", readiness=false. Elapsed: 2.288415015s
Jun  6 16:23:33.855: INFO: Pod "pvc-snapshottable-tester-4449x": Phase="Pending", Reason="", readiness=false. Elapsed: 4.432951968s
Jun  6 16:23:36.000: INFO: Pod "pvc-snapshottable-tester-4449x": Phase="Pending", Reason="", readiness=false. Elapsed: 6.578386853s
Jun  6 16:23:38.146: INFO: Pod "pvc-snapshottable-tester-4449x": Phase="Pending", Reason="", readiness=false. Elapsed: 8.723723108s
Jun  6 16:23:40.290: INFO: Pod "pvc-snapshottable-tester-4449x": Phase="Pending", Reason="", readiness=false. Elapsed: 10.867976918s
Jun  6 16:23:42.441: INFO: Pod "pvc-snapshottable-tester-4449x": Phase="Pending", Reason="", readiness=false. Elapsed: 13.01888864s
Jun  6 16:23:44.587: INFO: Pod "pvc-snapshottable-tester-4449x": Phase="Pending", Reason="", readiness=false. Elapsed: 15.165101801s
Jun  6 16:23:46.732: INFO: Pod "pvc-snapshottable-tester-4449x": Phase="Pending", Reason="", readiness=false. Elapsed: 17.310107804s
Jun  6 16:23:48.879: INFO: Pod "pvc-snapshottable-tester-4449x": Phase="Pending", Reason="", readiness=false. Elapsed: 19.457013265s
Jun  6 16:23:51.026: INFO: Pod "pvc-snapshottable-tester-4449x": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.603549084s
STEP: Saw pod success
Jun  6 16:23:51.026: INFO: Pod "pvc-snapshottable-tester-4449x" satisfied condition "Succeeded or Failed"
Jun  6 16:23:51.316: INFO: Pod pvc-snapshottable-tester-4449x has the following logs: 
Jun  6 16:23:51.316: INFO: Deleting pod "pvc-snapshottable-tester-4449x" in namespace "snapshotting-9579"
Jun  6 16:23:51.466: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-4449x" to be fully deleted
Jun  6 16:23:51.611: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comcczrw] to have phase Bound
Jun  6 16:23:51.756: INFO: PersistentVolumeClaim ebs.csi.aws.comcczrw found and phase=Bound (144.08374ms)
STEP: [init] checking the claim
... skipping 18 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.42NGBlObb/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  6 16:24:10.526: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-qbk8b" in namespace "snapshotting-9579" to be "Succeeded or Failed"
Jun  6 16:24:10.670: INFO: Pod "pvc-snapshottable-data-tester-qbk8b": Phase="Pending", Reason="", readiness=false. Elapsed: 143.885413ms
Jun  6 16:24:12.814: INFO: Pod "pvc-snapshottable-data-tester-qbk8b": Phase="Pending", Reason="", readiness=false. Elapsed: 2.288459085s
Jun  6 16:24:14.963: INFO: Pod "pvc-snapshottable-data-tester-qbk8b": Phase="Pending", Reason="", readiness=false. Elapsed: 4.437260126s
Jun  6 16:24:17.108: INFO: Pod "pvc-snapshottable-data-tester-qbk8b": Phase="Pending", Reason="", readiness=false. Elapsed: 6.582063156s
Jun  6 16:24:19.252: INFO: Pod "pvc-snapshottable-data-tester-qbk8b": Phase="Pending", Reason="", readiness=false. Elapsed: 8.726235961s
Jun  6 16:24:21.396: INFO: Pod "pvc-snapshottable-data-tester-qbk8b": Phase="Pending", Reason="", readiness=false. Elapsed: 10.870060595s
Jun  6 16:24:23.541: INFO: Pod "pvc-snapshottable-data-tester-qbk8b": Phase="Succeeded", Reason="", readiness=false. Elapsed: 13.015477681s
STEP: Saw pod success
Jun  6 16:24:23.541: INFO: Pod "pvc-snapshottable-data-tester-qbk8b" satisfied condition "Succeeded or Failed"
Jun  6 16:24:23.834: INFO: Pod pvc-snapshottable-data-tester-qbk8b has the following logs: 
Jun  6 16:24:23.834: INFO: Deleting pod "pvc-snapshottable-data-tester-qbk8b" in namespace "snapshotting-9579"
Jun  6 16:24:23.988: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-qbk8b" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun  6 16:24:46.724: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-9579 exec restored-pvc-tester-7dksm --namespace=snapshotting-9579 -- cat /mnt/test/data'
... skipping 253 lines ...
    /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:108
      
      /tmp/kops.42NGBlObb/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.42NGBlObb/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-9579 exec restored-pvc-tester-7dksm --namespace=snapshotting-9579 -- 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-9579 exec restored-pvc-tester-7dksm --namespace=snapshotting-9579 -- 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.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:602
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] provisioning
... skipping 275 lines ...

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

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

    /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 11 lines ...
Jun  6 16:25:16.797: INFO: Creating resource for dynamic PV
Jun  6 16:25:16.797: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8052hbgxj
STEP: creating a claim
Jun  6 16:25:16.945: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-8052
Jun  6 16:25:17.386: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-8052" in namespace "provisioning-8052" to be "Succeeded or Failed"
Jun  6 16:25:17.536: INFO: Pod "volume-prep-provisioning-8052": Phase="Pending", Reason="", readiness=false. Elapsed: 149.800209ms
Jun  6 16:25:19.683: INFO: Pod "volume-prep-provisioning-8052": Phase="Pending", Reason="", readiness=false. Elapsed: 2.296100318s
Jun  6 16:25:21.833: INFO: Pod "volume-prep-provisioning-8052": Phase="Pending", Reason="", readiness=false. Elapsed: 4.446748962s
Jun  6 16:25:23.980: INFO: Pod "volume-prep-provisioning-8052": Phase="Pending", Reason="", readiness=false. Elapsed: 6.594042736s
Jun  6 16:25:26.129: INFO: Pod "volume-prep-provisioning-8052": Phase="Pending", Reason="", readiness=false. Elapsed: 8.74268925s
Jun  6 16:25:28.275: INFO: Pod "volume-prep-provisioning-8052": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.888752668s
STEP: Saw pod success
Jun  6 16:25:28.275: INFO: Pod "volume-prep-provisioning-8052" satisfied condition "Succeeded or Failed"
Jun  6 16:25:28.275: INFO: Deleting pod "volume-prep-provisioning-8052" in namespace "provisioning-8052"
Jun  6 16:25:28.427: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-8052" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-zwmj
STEP: Checking for subpath error in container status
Jun  6 16:25:33.015: INFO: Deleting pod "pod-subpath-test-dynamicpv-zwmj" in namespace "provisioning-8052"
Jun  6 16:25:33.166: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-zwmj" to be fully deleted
STEP: Deleting pod
Jun  6 16:25:33.312: INFO: Deleting pod "pod-subpath-test-dynamicpv-zwmj" in namespace "provisioning-8052"
STEP: Deleting pvc
Jun  6 16:25:33.751: INFO: Deleting PersistentVolumeClaim "awspsmnc"
... skipping 247 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  6 16:25:06.030: 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.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun  6 16:25:06.761: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  6 16:25:06.761: INFO: Creating resource for dynamic PV
Jun  6 16:25:06.761: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4227v8ql2
STEP: creating a claim
Jun  6 16:25:06.908: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-gc8g
STEP: Checking for subpath error in container status
Jun  6 16:25:25.651: INFO: Deleting pod "pod-subpath-test-dynamicpv-gc8g" in namespace "provisioning-4227"
Jun  6 16:25:25.796: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-gc8g" to be fully deleted
STEP: Deleting pod
Jun  6 16:25:34.084: INFO: Deleting pod "pod-subpath-test-dynamicpv-gc8g" in namespace "provisioning-4227"
STEP: Deleting pvc
Jun  6 16:25:34.527: INFO: Deleting PersistentVolumeClaim "aws5t8pv"
... skipping 17 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.42NGBlObb/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.42NGBlObb/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath directory is outside the volume [Slow][LinuxOnly]
      /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  6 16:26:11.378: INFO: Distro debian doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
... skipping 4 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.42NGBlObb/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.42NGBlObb/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.42NGBlObb/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.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 129 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  6 16:25:22.160: 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.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun  6 16:25:22.896: INFO: Creating resource for dynamic PV
Jun  6 16:25:22.896: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1862-e2e-sc2pw26
STEP: creating a claim
Jun  6 16:25:23.043: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-khmn
STEP: Checking for subpath error in container status
Jun  6 16:25:47.788: INFO: Deleting pod "pod-subpath-test-dynamicpv-khmn" in namespace "provisioning-1862"
Jun  6 16:25:47.939: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-khmn" to be fully deleted
STEP: Deleting pod
Jun  6 16:26:00.238: INFO: Deleting pod "pod-subpath-test-dynamicpv-khmn" in namespace "provisioning-1862"
STEP: Deleting pvc
Jun  6 16:26:00.677: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comtk44b"
... skipping 10 lines ...

• [SLOW TEST:49.564 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.42NGBlObb/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.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [sig-storage] Zone Support [Feature:vsphere]
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  6 16:26:11.726: INFO: >>> kubeConfig: /root/.kube/config
... skipping 131 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.42NGBlObb/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.42NGBlObb/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.42NGBlObb/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.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 177 lines ...
Jun  6 16:26:00.320: INFO: Pod aws-client still exists
Jun  6 16:26:02.174: INFO: Waiting for pod aws-client to disappear
Jun  6 16:26:02.322: INFO: Pod aws-client still exists
Jun  6 16:26:04.173: INFO: Waiting for pod aws-client to disappear
Jun  6 16:26:04.317: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun  6 16:26:05.159: INFO: Couldn't delete PD "aws://sa-east-1a/vol-0b14a483022baf8cc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0b14a483022baf8cc is currently attached to i-0497bb511a26d2153
	status code: 400, request id: a85f41e3-b0a0-4293-a796-1f778bd6c297
Jun  6 16:26:11.085: INFO: Couldn't delete PD "aws://sa-east-1a/vol-0b14a483022baf8cc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0b14a483022baf8cc is currently attached to i-0497bb511a26d2153
	status code: 400, request id: 5c38b255-b360-4bcb-bd2a-7e3fafc5df1a
Jun  6 16:26:16.837: INFO: Successfully deleted PD "aws://sa-east-1a/vol-0b14a483022baf8cc".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  6 16:26:16.837: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-5981" for this suite.
... skipping 24 lines ...
Jun  6 16:24:48.315: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-9902-e2e-scd649q      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-9902    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-9902-e2e-scd649q,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-9902    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-9902-e2e-scd649q,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-9902    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-9902-e2e-scd649q,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-9902-e2e-scd649q    b82e0d3f-0b8e-450c-9906-8410ac4f5eb3 11905 0 2021-06-06 16:24:48 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-06 16:24:48 +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-mnw5w pvc- provisioning-9902  264c5cbb-a7e4-4992-98db-62fb3125c3da 11918 0 2021-06-06 16:24:48 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-06 16:24:48 +0000 UTC FieldsV1 {"f:metadata":{"f:generateName":{}},"f:spec":{"f:accessModes":{},"f:resources":{"f:requests":{".":{},"f:storage":{}}},"f:storageClassName":{},"f:volumeMode":{}}}}]},Spec:PersistentVolumeClaimSpec{AccessModes:[ReadWriteOnce],Resources:ResourceRequirements{Limits:ResourceList{},Requests:ResourceList{storage: {{1073741824 0} {<nil>} 1Gi BinarySI},},},VolumeName:,Selector:nil,StorageClassName:*provisioning-9902-e2e-scd649q,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-7e99cebd-87e8-403b-a37a-1447e435148f in namespace provisioning-9902
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun  6 16:24:59.940: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-z97nm" in namespace "provisioning-9902" to be "Succeeded or Failed"
Jun  6 16:25:00.085: INFO: Pod "pvc-volume-tester-writer-z97nm": Phase="Pending", Reason="", readiness=false. Elapsed: 144.952937ms
Jun  6 16:25:02.229: INFO: Pod "pvc-volume-tester-writer-z97nm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.288772654s
Jun  6 16:25:04.374: INFO: Pod "pvc-volume-tester-writer-z97nm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.433668338s
Jun  6 16:25:06.525: INFO: Pod "pvc-volume-tester-writer-z97nm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.58436186s
Jun  6 16:25:08.669: INFO: Pod "pvc-volume-tester-writer-z97nm": Phase="Pending", Reason="", readiness=false. Elapsed: 8.728945582s
Jun  6 16:25:10.815: INFO: Pod "pvc-volume-tester-writer-z97nm": Phase="Pending", Reason="", readiness=false. Elapsed: 10.874513389s
... skipping 6 lines ...
Jun  6 16:25:25.834: INFO: Pod "pvc-volume-tester-writer-z97nm": Phase="Pending", Reason="", readiness=false. Elapsed: 25.893978542s
Jun  6 16:25:27.980: INFO: Pod "pvc-volume-tester-writer-z97nm": Phase="Pending", Reason="", readiness=false. Elapsed: 28.039311603s
Jun  6 16:25:30.127: INFO: Pod "pvc-volume-tester-writer-z97nm": Phase="Pending", Reason="", readiness=false. Elapsed: 30.186324852s
Jun  6 16:25:32.272: INFO: Pod "pvc-volume-tester-writer-z97nm": Phase="Pending", Reason="", readiness=false. Elapsed: 32.331520421s
Jun  6 16:25:34.418: INFO: Pod "pvc-volume-tester-writer-z97nm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.477784064s
STEP: Saw pod success
Jun  6 16:25:34.418: INFO: Pod "pvc-volume-tester-writer-z97nm" satisfied condition "Succeeded or Failed"
Jun  6 16:25:34.708: INFO: Pod pvc-volume-tester-writer-z97nm has the following logs: 
Jun  6 16:25:34.708: INFO: Deleting pod "pvc-volume-tester-writer-z97nm" in namespace "provisioning-9902"
Jun  6 16:25:34.859: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-z97nm" to be fully deleted
STEP: checking the created volume has the correct mount options, is readable and retains data on the same node "ip-172-20-62-27.sa-east-1.compute.internal"
Jun  6 16:25:35.443: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-h8wdp" in namespace "provisioning-9902" to be "Succeeded or Failed"
Jun  6 16:25:35.589: INFO: Pod "pvc-volume-tester-reader-h8wdp": Phase="Pending", Reason="", readiness=false. Elapsed: 146.639413ms
Jun  6 16:25:37.735: INFO: Pod "pvc-volume-tester-reader-h8wdp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.292040137s
Jun  6 16:25:39.879: INFO: Pod "pvc-volume-tester-reader-h8wdp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.43647594s
STEP: Saw pod success
Jun  6 16:25:39.879: INFO: Pod "pvc-volume-tester-reader-h8wdp" satisfied condition "Succeeded or Failed"
Jun  6 16:25:40.169: INFO: Pod pvc-volume-tester-reader-h8wdp has the following logs: hello world

Jun  6 16:25:40.169: INFO: Deleting pod "pvc-volume-tester-reader-h8wdp" in namespace "provisioning-9902"
Jun  6 16:25:40.319: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-h8wdp" to be fully deleted
Jun  6 16:25:40.462: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-mnw5w] to have phase Bound
Jun  6 16:25:40.606: INFO: PersistentVolumeClaim pvc-mnw5w found and phase=Bound (143.708258ms)
... skipping 391 lines ...
Jun  6 16:25:58.196: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-82647grdl
STEP: creating a claim
Jun  6 16:25:58.341: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Jun  6 16:25:58.638: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun  6 16:25:58.930: INFO: Error updating pvc awsbl8lv: PersistentVolumeClaim "awsbl8lv" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-82647grdl",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun  6 16:26:29.518: INFO: Error updating pvc awsbl8lv: PersistentVolumeClaim "awsbl8lv" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 304 lines ...
STEP: Deleting pod hostexec-ip-172-20-59-46.sa-east-1.compute.internal-l7vph in namespace volumemode-4938
Jun  6 16:26:10.378: INFO: Deleting pod "pod-d45456b9-fd66-45ce-9134-02a82b0336bf" in namespace "volumemode-4938"
Jun  6 16:26:10.529: INFO: Wait up to 5m0s for pod "pod-d45456b9-fd66-45ce-9134-02a82b0336bf" to be fully deleted
STEP: Deleting pv and pvc
Jun  6 16:26:24.823: INFO: Deleting PersistentVolumeClaim "pvc-q4xzb"
Jun  6 16:26:24.970: INFO: Deleting PersistentVolume "aws-npwqg"
Jun  6 16:26:25.407: INFO: Couldn't delete PD "aws://sa-east-1a/vol-02bdcfe7f225b59b4", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02bdcfe7f225b59b4 is currently attached to i-0497bb511a26d2153
	status code: 400, request id: 9ed95d9b-baec-4232-a345-fa830985c657
Jun  6 16:26:31.243: INFO: Couldn't delete PD "aws://sa-east-1a/vol-02bdcfe7f225b59b4", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02bdcfe7f225b59b4 is currently attached to i-0497bb511a26d2153
	status code: 400, request id: 9270ed55-b1f7-4ec8-8918-b78c6d2fd0ea
Jun  6 16:26:37.037: INFO: Successfully deleted PD "aws://sa-east-1a/vol-02bdcfe7f225b59b4".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  6 16:26:37.037: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-4938" for this suite.
... skipping 24 lines ...
Jun  6 16:25:46.567: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2775dr8p6
STEP: creating a claim
Jun  6 16:25:46.713: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-b47b
STEP: Creating a pod to test atomic-volume-subpath
Jun  6 16:25:47.154: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-b47b" in namespace "provisioning-2775" to be "Succeeded or Failed"
Jun  6 16:25:47.299: INFO: Pod "pod-subpath-test-dynamicpv-b47b": Phase="Pending", Reason="", readiness=false. Elapsed: 145.172217ms
Jun  6 16:25:49.445: INFO: Pod "pod-subpath-test-dynamicpv-b47b": Phase="Pending", Reason="", readiness=false. Elapsed: 2.291125858s
Jun  6 16:25:51.591: INFO: Pod "pod-subpath-test-dynamicpv-b47b": Phase="Pending", Reason="", readiness=false. Elapsed: 4.437166231s
Jun  6 16:25:53.737: INFO: Pod "pod-subpath-test-dynamicpv-b47b": Phase="Pending", Reason="", readiness=false. Elapsed: 6.583043976s
Jun  6 16:25:55.884: INFO: Pod "pod-subpath-test-dynamicpv-b47b": Phase="Pending", Reason="", readiness=false. Elapsed: 8.729650416s
Jun  6 16:25:58.030: INFO: Pod "pod-subpath-test-dynamicpv-b47b": Phase="Pending", Reason="", readiness=false. Elapsed: 10.875774408s
... skipping 6 lines ...
Jun  6 16:26:13.056: INFO: Pod "pod-subpath-test-dynamicpv-b47b": Phase="Running", Reason="", readiness=true. Elapsed: 25.902104709s
Jun  6 16:26:15.203: INFO: Pod "pod-subpath-test-dynamicpv-b47b": Phase="Running", Reason="", readiness=true. Elapsed: 28.048802777s
Jun  6 16:26:17.351: INFO: Pod "pod-subpath-test-dynamicpv-b47b": Phase="Running", Reason="", readiness=true. Elapsed: 30.197327392s
Jun  6 16:26:19.497: INFO: Pod "pod-subpath-test-dynamicpv-b47b": Phase="Running", Reason="", readiness=true. Elapsed: 32.34304304s
Jun  6 16:26:21.643: INFO: Pod "pod-subpath-test-dynamicpv-b47b": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.488852095s
STEP: Saw pod success
Jun  6 16:26:21.643: INFO: Pod "pod-subpath-test-dynamicpv-b47b" satisfied condition "Succeeded or Failed"
Jun  6 16:26:21.789: INFO: Trying to get logs from node ip-172-20-59-101.sa-east-1.compute.internal pod pod-subpath-test-dynamicpv-b47b container test-container-subpath-dynamicpv-b47b: <nil>
STEP: delete the pod
Jun  6 16:26:22.086: INFO: Waiting for pod pod-subpath-test-dynamicpv-b47b to disappear
Jun  6 16:26:22.232: INFO: Pod pod-subpath-test-dynamicpv-b47b no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-b47b
Jun  6 16:26:22.232: INFO: Deleting pod "pod-subpath-test-dynamicpv-b47b" in namespace "provisioning-2775"
... skipping 28 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  6 16:25:38.976: 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.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun  6 16:25:39.694: INFO: Creating resource for dynamic PV
Jun  6 16:25:39.694: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3722-e2e-sck9xdz
STEP: creating a claim
Jun  6 16:25:39.840: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-hpf6
STEP: Checking for subpath error in container status
Jun  6 16:26:18.565: INFO: Deleting pod "pod-subpath-test-dynamicpv-hpf6" in namespace "provisioning-3722"
Jun  6 16:26:18.710: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-hpf6" to be fully deleted
STEP: Deleting pod
Jun  6 16:26:28.998: INFO: Deleting pod "pod-subpath-test-dynamicpv-hpf6" in namespace "provisioning-3722"
STEP: Deleting pvc
Jun  6 16:26:29.431: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comfvw9z"
... skipping 11 lines ...

• [SLOW TEST:66.626 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath directory is outside the volume [Slow][LinuxOnly]
    /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 169 lines ...
Jun  6 16:25:41.883: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4757fsd7
STEP: creating a claim
Jun  6 16:25:42.037: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-26n8
STEP: Creating a pod to test subpath
Jun  6 16:25:42.480: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-26n8" in namespace "provisioning-475" to be "Succeeded or Failed"
Jun  6 16:25:42.624: INFO: Pod "pod-subpath-test-dynamicpv-26n8": Phase="Pending", Reason="", readiness=false. Elapsed: 144.013443ms
Jun  6 16:25:44.769: INFO: Pod "pod-subpath-test-dynamicpv-26n8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.289068778s
Jun  6 16:25:46.914: INFO: Pod "pod-subpath-test-dynamicpv-26n8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.43430985s
Jun  6 16:25:49.063: INFO: Pod "pod-subpath-test-dynamicpv-26n8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.58277937s
Jun  6 16:25:51.208: INFO: Pod "pod-subpath-test-dynamicpv-26n8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.728344394s
Jun  6 16:25:53.353: INFO: Pod "pod-subpath-test-dynamicpv-26n8": Phase="Pending", Reason="", readiness=false. Elapsed: 10.87321493s
Jun  6 16:25:55.500: INFO: Pod "pod-subpath-test-dynamicpv-26n8": Phase="Pending", Reason="", readiness=false. Elapsed: 13.019608153s
Jun  6 16:25:57.645: INFO: Pod "pod-subpath-test-dynamicpv-26n8": Phase="Pending", Reason="", readiness=false. Elapsed: 15.164943358s
Jun  6 16:25:59.790: INFO: Pod "pod-subpath-test-dynamicpv-26n8": Phase="Pending", Reason="", readiness=false. Elapsed: 17.310258196s
Jun  6 16:26:01.940: INFO: Pod "pod-subpath-test-dynamicpv-26n8": Phase="Pending", Reason="", readiness=false. Elapsed: 19.459507769s
Jun  6 16:26:04.084: INFO: Pod "pod-subpath-test-dynamicpv-26n8": Phase="Pending", Reason="", readiness=false. Elapsed: 21.603986518s
Jun  6 16:26:06.229: INFO: Pod "pod-subpath-test-dynamicpv-26n8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.748569886s
STEP: Saw pod success
Jun  6 16:26:06.229: INFO: Pod "pod-subpath-test-dynamicpv-26n8" satisfied condition "Succeeded or Failed"
Jun  6 16:26:06.376: INFO: Trying to get logs from node ip-172-20-44-71.sa-east-1.compute.internal pod pod-subpath-test-dynamicpv-26n8 container test-container-subpath-dynamicpv-26n8: <nil>
STEP: delete the pod
Jun  6 16:26:06.681: INFO: Waiting for pod pod-subpath-test-dynamicpv-26n8 to disappear
Jun  6 16:26:06.825: INFO: Pod pod-subpath-test-dynamicpv-26n8 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-26n8
Jun  6 16:26:06.825: INFO: Deleting pod "pod-subpath-test-dynamicpv-26n8" in namespace "provisioning-475"
STEP: Creating pod pod-subpath-test-dynamicpv-26n8
STEP: Creating a pod to test subpath
Jun  6 16:26:07.114: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-26n8" in namespace "provisioning-475" to be "Succeeded or Failed"
Jun  6 16:26:07.258: INFO: Pod "pod-subpath-test-dynamicpv-26n8": Phase="Pending", Reason="", readiness=false. Elapsed: 144.405198ms
Jun  6 16:26:09.404: INFO: Pod "pod-subpath-test-dynamicpv-26n8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.290126291s
Jun  6 16:26:11.551: INFO: Pod "pod-subpath-test-dynamicpv-26n8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.436992917s
Jun  6 16:26:13.695: INFO: Pod "pod-subpath-test-dynamicpv-26n8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.58170255s
Jun  6 16:26:15.841: INFO: Pod "pod-subpath-test-dynamicpv-26n8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.727686628s
Jun  6 16:26:17.988: INFO: Pod "pod-subpath-test-dynamicpv-26n8": Phase="Pending", Reason="", readiness=false. Elapsed: 10.873962505s
... skipping 6 lines ...
Jun  6 16:26:33.005: INFO: Pod "pod-subpath-test-dynamicpv-26n8": Phase="Pending", Reason="", readiness=false. Elapsed: 25.891536782s
Jun  6 16:26:35.150: INFO: Pod "pod-subpath-test-dynamicpv-26n8": Phase="Pending", Reason="", readiness=false. Elapsed: 28.036630046s
Jun  6 16:26:37.295: INFO: Pod "pod-subpath-test-dynamicpv-26n8": Phase="Pending", Reason="", readiness=false. Elapsed: 30.181609498s
Jun  6 16:26:39.440: INFO: Pod "pod-subpath-test-dynamicpv-26n8": Phase="Pending", Reason="", readiness=false. Elapsed: 32.326235619s
Jun  6 16:26:41.585: INFO: Pod "pod-subpath-test-dynamicpv-26n8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.471161406s
STEP: Saw pod success
Jun  6 16:26:41.585: INFO: Pod "pod-subpath-test-dynamicpv-26n8" satisfied condition "Succeeded or Failed"
Jun  6 16:26:41.729: INFO: Trying to get logs from node ip-172-20-59-46.sa-east-1.compute.internal pod pod-subpath-test-dynamicpv-26n8 container test-container-subpath-dynamicpv-26n8: <nil>
STEP: delete the pod
Jun  6 16:26:42.053: INFO: Waiting for pod pod-subpath-test-dynamicpv-26n8 to disappear
Jun  6 16:26:42.200: INFO: Pod pod-subpath-test-dynamicpv-26n8 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-26n8
Jun  6 16:26:42.200: INFO: Deleting pod "pod-subpath-test-dynamicpv-26n8" in namespace "provisioning-475"
... skipping 48 lines ...
Jun  6 16:26:28.430: INFO: PersistentVolumeClaim pvc-vf9bh found but phase is Pending instead of Bound.
Jun  6 16:26:30.574: INFO: PersistentVolumeClaim pvc-vf9bh found and phase=Bound (10.865580333s)
Jun  6 16:26:30.574: INFO: Waiting up to 3m0s for PersistentVolume aws-lx6kn to have phase Bound
Jun  6 16:26:30.718: INFO: PersistentVolume aws-lx6kn found and phase=Bound (143.844186ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-vmg8
STEP: Creating a pod to test exec-volume-test
Jun  6 16:26:31.164: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-vmg8" in namespace "volume-4438" to be "Succeeded or Failed"
Jun  6 16:26:31.309: INFO: Pod "exec-volume-test-preprovisionedpv-vmg8": Phase="Pending", Reason="", readiness=false. Elapsed: 144.632044ms
Jun  6 16:26:33.454: INFO: Pod "exec-volume-test-preprovisionedpv-vmg8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.289366694s
Jun  6 16:26:35.601: INFO: Pod "exec-volume-test-preprovisionedpv-vmg8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.437071784s
Jun  6 16:26:37.745: INFO: Pod "exec-volume-test-preprovisionedpv-vmg8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.581215146s
Jun  6 16:26:39.890: INFO: Pod "exec-volume-test-preprovisionedpv-vmg8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.725920118s
Jun  6 16:26:42.053: INFO: Pod "exec-volume-test-preprovisionedpv-vmg8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.888316457s
STEP: Saw pod success
Jun  6 16:26:42.053: INFO: Pod "exec-volume-test-preprovisionedpv-vmg8" satisfied condition "Succeeded or Failed"
Jun  6 16:26:42.197: INFO: Trying to get logs from node ip-172-20-59-46.sa-east-1.compute.internal pod exec-volume-test-preprovisionedpv-vmg8 container exec-container-preprovisionedpv-vmg8: <nil>
STEP: delete the pod
Jun  6 16:26:42.499: INFO: Waiting for pod exec-volume-test-preprovisionedpv-vmg8 to disappear
Jun  6 16:26:42.643: INFO: Pod exec-volume-test-preprovisionedpv-vmg8 no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-vmg8
Jun  6 16:26:42.643: INFO: Deleting pod "exec-volume-test-preprovisionedpv-vmg8" in namespace "volume-4438"
STEP: Deleting pv and pvc
Jun  6 16:26:42.792: INFO: Deleting PersistentVolumeClaim "pvc-vf9bh"
Jun  6 16:26:42.938: INFO: Deleting PersistentVolume "aws-lx6kn"
Jun  6 16:26:43.380: INFO: Couldn't delete PD "aws://sa-east-1a/vol-0195c94664d38c6fa", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0195c94664d38c6fa is currently attached to i-0497bb511a26d2153
	status code: 400, request id: 53bd5dd0-92ff-4248-9b09-3216d7d8c6b2
Jun  6 16:26:49.231: INFO: Couldn't delete PD "aws://sa-east-1a/vol-0195c94664d38c6fa", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0195c94664d38c6fa is currently attached to i-0497bb511a26d2153
	status code: 400, request id: 3fbc3614-8382-412e-8574-1dd344e6e718
Jun  6 16:26:55.083: INFO: Couldn't delete PD "aws://sa-east-1a/vol-0195c94664d38c6fa", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0195c94664d38c6fa is currently attached to i-0497bb511a26d2153
	status code: 400, request id: 30216c3a-0955-41ea-8eb4-a14e7947853c
Jun  6 16:27:00.946: INFO: Successfully deleted PD "aws://sa-east-1a/vol-0195c94664d38c6fa".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  6 16:27:00.946: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-4438" for this suite.
... skipping 24 lines ...
Jun  6 16:26:21.832: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-7246g5pt6
STEP: creating a claim
Jun  6 16:26:21.978: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-k9rv
STEP: Creating a pod to test exec-volume-test
Jun  6 16:26:22.424: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-k9rv" in namespace "volume-7246" to be "Succeeded or Failed"
Jun  6 16:26:22.570: INFO: Pod "exec-volume-test-dynamicpv-k9rv": Phase="Pending", Reason="", readiness=false. Elapsed: 145.535729ms
Jun  6 16:26:24.716: INFO: Pod "exec-volume-test-dynamicpv-k9rv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.291368991s
Jun  6 16:26:26.862: INFO: Pod "exec-volume-test-dynamicpv-k9rv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.437875109s
Jun  6 16:26:29.009: INFO: Pod "exec-volume-test-dynamicpv-k9rv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.584519056s
Jun  6 16:26:31.170: INFO: Pod "exec-volume-test-dynamicpv-k9rv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.745018169s
Jun  6 16:26:33.315: INFO: Pod "exec-volume-test-dynamicpv-k9rv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.890782824s
Jun  6 16:26:35.466: INFO: Pod "exec-volume-test-dynamicpv-k9rv": Phase="Pending", Reason="", readiness=false. Elapsed: 13.041583497s
Jun  6 16:26:37.613: INFO: Pod "exec-volume-test-dynamicpv-k9rv": Phase="Pending", Reason="", readiness=false. Elapsed: 15.188923749s
Jun  6 16:26:39.759: INFO: Pod "exec-volume-test-dynamicpv-k9rv": Phase="Pending", Reason="", readiness=false. Elapsed: 17.334678603s
Jun  6 16:26:41.906: INFO: Pod "exec-volume-test-dynamicpv-k9rv": Phase="Pending", Reason="", readiness=false. Elapsed: 19.481470586s
Jun  6 16:26:44.053: INFO: Pod "exec-volume-test-dynamicpv-k9rv": Phase="Pending", Reason="", readiness=false. Elapsed: 21.628306297s
Jun  6 16:26:46.199: INFO: Pod "exec-volume-test-dynamicpv-k9rv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.774324986s
STEP: Saw pod success
Jun  6 16:26:46.199: INFO: Pod "exec-volume-test-dynamicpv-k9rv" satisfied condition "Succeeded or Failed"
Jun  6 16:26:46.344: INFO: Trying to get logs from node ip-172-20-59-101.sa-east-1.compute.internal pod exec-volume-test-dynamicpv-k9rv container exec-container-dynamicpv-k9rv: <nil>
STEP: delete the pod
Jun  6 16:26:46.653: INFO: Waiting for pod exec-volume-test-dynamicpv-k9rv to disappear
Jun  6 16:26:46.798: INFO: Pod exec-volume-test-dynamicpv-k9rv no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-k9rv
Jun  6 16:26:46.798: INFO: Deleting pod "exec-volume-test-dynamicpv-k9rv" in namespace "volume-7246"
... skipping 34 lines ...
Jun  6 16:24:45.081: INFO: Creating resource for dynamic PV
Jun  6 16:24:45.081: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-239-e2e-scrpkjf
STEP: creating a claim
Jun  6 16:24:45.226: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun  6 16:24:45.667: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-9959n" in namespace "snapshotting-239" to be "Succeeded or Failed"
Jun  6 16:24:45.811: INFO: Pod "pvc-snapshottable-tester-9959n": Phase="Pending", Reason="", readiness=false. Elapsed: 144.192219ms
Jun  6 16:24:47.959: INFO: Pod "pvc-snapshottable-tester-9959n": Phase="Pending", Reason="", readiness=false. Elapsed: 2.291329714s
Jun  6 16:24:50.108: INFO: Pod "pvc-snapshottable-tester-9959n": Phase="Pending", Reason="", readiness=false. Elapsed: 4.440352065s
Jun  6 16:24:52.252: INFO: Pod "pvc-snapshottable-tester-9959n": Phase="Pending", Reason="", readiness=false. Elapsed: 6.584660931s
Jun  6 16:24:54.396: INFO: Pod "pvc-snapshottable-tester-9959n": Phase="Pending", Reason="", readiness=false. Elapsed: 8.72887236s
Jun  6 16:24:56.541: INFO: Pod "pvc-snapshottable-tester-9959n": Phase="Pending", Reason="", readiness=false. Elapsed: 10.873862694s
Jun  6 16:24:58.686: INFO: Pod "pvc-snapshottable-tester-9959n": Phase="Pending", Reason="", readiness=false. Elapsed: 13.018310366s
Jun  6 16:25:00.830: INFO: Pod "pvc-snapshottable-tester-9959n": Phase="Pending", Reason="", readiness=false. Elapsed: 15.162436843s
Jun  6 16:25:02.974: INFO: Pod "pvc-snapshottable-tester-9959n": Phase="Pending", Reason="", readiness=false. Elapsed: 17.306662585s
Jun  6 16:25:05.121: INFO: Pod "pvc-snapshottable-tester-9959n": Phase="Pending", Reason="", readiness=false. Elapsed: 19.453808711s
Jun  6 16:25:07.266: INFO: Pod "pvc-snapshottable-tester-9959n": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.598623602s
STEP: Saw pod success
Jun  6 16:25:07.266: INFO: Pod "pvc-snapshottable-tester-9959n" satisfied condition "Succeeded or Failed"
Jun  6 16:25:07.561: INFO: Pod pvc-snapshottable-tester-9959n has the following logs: 
Jun  6 16:25:07.561: INFO: Deleting pod "pvc-snapshottable-tester-9959n" in namespace "snapshotting-239"
Jun  6 16:25:07.710: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-9959n" to be fully deleted
Jun  6 16:25:07.861: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comn8gzt] to have phase Bound
Jun  6 16:25:08.005: INFO: PersistentVolumeClaim ebs.csi.aws.comn8gzt found and phase=Bound (143.94158ms)
STEP: [init] checking the claim
... skipping 25 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.42NGBlObb/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  6 16:25:41.815: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-gzpc9" in namespace "snapshotting-239" to be "Succeeded or Failed"
Jun  6 16:25:41.959: INFO: Pod "pvc-snapshottable-data-tester-gzpc9": Phase="Pending", Reason="", readiness=false. Elapsed: 144.169935ms
Jun  6 16:25:44.104: INFO: Pod "pvc-snapshottable-data-tester-gzpc9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.288986904s
Jun  6 16:25:46.250: INFO: Pod "pvc-snapshottable-data-tester-gzpc9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.434903839s
Jun  6 16:25:48.395: INFO: Pod "pvc-snapshottable-data-tester-gzpc9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.580257564s
Jun  6 16:25:50.540: INFO: Pod "pvc-snapshottable-data-tester-gzpc9": Phase="Pending", Reason="", readiness=false. Elapsed: 8.72461534s
Jun  6 16:25:52.690: INFO: Pod "pvc-snapshottable-data-tester-gzpc9": Phase="Pending", Reason="", readiness=false. Elapsed: 10.875150434s
Jun  6 16:25:54.839: INFO: Pod "pvc-snapshottable-data-tester-gzpc9": Phase="Pending", Reason="", readiness=false. Elapsed: 13.023763487s
Jun  6 16:25:56.984: INFO: Pod "pvc-snapshottable-data-tester-gzpc9": Phase="Pending", Reason="", readiness=false. Elapsed: 15.169317172s
Jun  6 16:25:59.142: INFO: Pod "pvc-snapshottable-data-tester-gzpc9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 17.326941008s
STEP: Saw pod success
Jun  6 16:25:59.153: INFO: Pod "pvc-snapshottable-data-tester-gzpc9" satisfied condition "Succeeded or Failed"
Jun  6 16:25:59.493: INFO: Pod pvc-snapshottable-data-tester-gzpc9 has the following logs: 
Jun  6 16:25:59.493: INFO: Deleting pod "pvc-snapshottable-data-tester-gzpc9" in namespace "snapshotting-239"
Jun  6 16:25:59.646: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-gzpc9" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun  6 16:26:14.375: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-239 exec restored-pvc-tester-jxdnh --namespace=snapshotting-239 -- cat /mnt/test/data'
... skipping 49 lines ...
Jun  6 16:27:06.156: INFO: At 2021-06-06 16:26:04 +0000 UTC - event for restored-pvc-tester-jxdnh: {default-scheduler } Scheduled: Successfully assigned snapshotting-239/restored-pvc-tester-jxdnh to ip-172-20-59-101.sa-east-1.compute.internal
Jun  6 16:27:06.156: INFO: At 2021-06-06 16:26:08 +0000 UTC - event for restored-pvc-tester-jxdnh: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-5ab9fb44-672d-42c8-b777-94cb457fc794" 
Jun  6 16:27:06.156: INFO: At 2021-06-06 16:26:12 +0000 UTC - event for restored-pvc-tester-jxdnh: {kubelet ip-172-20-59-101.sa-east-1.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" already present on machine
Jun  6 16:27:06.156: INFO: At 2021-06-06 16:26:12 +0000 UTC - event for restored-pvc-tester-jxdnh: {kubelet ip-172-20-59-101.sa-east-1.compute.internal} Created: Created container volume-tester
Jun  6 16:27:06.156: INFO: At 2021-06-06 16:26:12 +0000 UTC - event for restored-pvc-tester-jxdnh: {kubelet ip-172-20-59-101.sa-east-1.compute.internal} Started: Started container volume-tester
Jun  6 16:27:06.156: INFO: At 2021-06-06 16:26:16 +0000 UTC - event for restored-pvc-tester-jxdnh: {kubelet ip-172-20-59-101.sa-east-1.compute.internal} Killing: Stopping container volume-tester
Jun  6 16:27:06.156: INFO: At 2021-06-06 16:26:55 +0000 UTC - event for snapshot-cc8b8: {snapshot-controller } SnapshotFinalizerError: Failed to check and update snapshot: snapshot controller failed to update snapshotting-239/snapshot-cc8b8 on API server: Operation cannot be fulfilled on volumesnapshots.snapshot.storage.k8s.io "snapshot-cc8b8": the object has been modified; please apply your changes to the latest version and try again
Jun  6 16:27:06.300: INFO: POD  NODE  PHASE  GRACE  CONDITIONS
Jun  6 16:27:06.300: INFO: 
Jun  6 16:27:06.446: INFO: 
Logging node info for node ip-172-20-44-71.sa-east-1.compute.internal
Jun  6 16:27:06.599: INFO: Node Info: &Node{ObjectMeta:{ip-172-20-44-71.sa-east-1.compute.internal    f0fa0243-18ec-4316-9e00-a755f15cabf2 15373 0 2021-06-06 16:12:53 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:t3.medium beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:sa-east-1 failure-domain.beta.kubernetes.io/zone:sa-east-1a kops.k8s.io/instancegroup:nodes-sa-east-1a kubernetes.io/arch:amd64 kubernetes.io/hostname:ip-172-20-44-71.sa-east-1.compute.internal kubernetes.io/os:linux kubernetes.io/role:node node-role.kubernetes.io/node: node.kubernetes.io/instance-type:t3.medium topology.ebs.csi.aws.com/zone:sa-east-1a topology.kubernetes.io/region:sa-east-1 topology.kubernetes.io/zone:sa-east-1a] map[csi.volume.kubernetes.io/nodeid:{"ebs.csi.aws.com":"i-0916f9968c5759d93"} node.alpha.kubernetes.io/ttl:0 projectcalico.org/IPv4Address:172.20.44.71/19 projectcalico.org/IPv4IPIPTunnelAddr:100.114.91.128 volumes.kubernetes.io/controller-managed-attach-detach:true] [] []  [{kops-controller Update v1 2021-06-06 16:12:53 +0000 UTC FieldsV1 {"f:metadata":{"f:labels":{"f:kops.k8s.io/instancegroup":{},"f:kubernetes.io/role":{},"f:node-role.kubernetes.io/node":{}}}}} {calico-node Update v1 2021-06-06 16:13:30 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4IPIPTunnelAddr":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}}} {kubelet Update v1 2021-06-06 16:18:53 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:csi.volume.kubernetes.io/nodeid":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.ebs.csi.aws.com/zone":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}},"f:status":{"f:allocatable":{"f:ephemeral-storage":{}},"f:capacity":{"f:ephemeral-storage":{}},"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{},"f:volumesInUse":{}}}} {kube-controller-manager Update v1 2021-06-06 16:26:45 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"100.96.2.0/24\"":{}}},"f:status":{"f:volumesAttached":{}}}}]},Spec:NodeSpec{PodCIDR:100.96.2.0/24,DoNotUseExternalID:,ProviderID:aws:///sa-east-1a/i-0916f9968c5759d93,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[100.96.2.0/24],},Status:NodeStatus{Capacity:ResourceList{cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{49895047168 0} {<nil>}  BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{4064751616 0} {<nil>} 3969484Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{44905542377 0} {<nil>} 44905542377 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{3959894016 0} {<nil>} 3867084Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2021-06-06 16:13:30 +0000 UTC,LastTransitionTime:2021-06-06 16:13:30 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2021-06-06 16:27:04 +0000 UTC,LastTransitionTime:2021-06-06 16:12:53 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2021-06-06 16:27:04 +0000 UTC,LastTransitionTime:2021-06-06 16:12:53 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2021-06-06 16:27:04 +0000 UTC,LastTransitionTime:2021-06-06 16:12:53 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2021-06-06 16:27:04 +0000 UTC,LastTransitionTime:2021-06-06 16:13:13 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:172.20.44.71,},NodeAddress{Type:ExternalIP,Address:54.233.223.193,},NodeAddress{Type:Hostname,Address:ip-172-20-44-71.sa-east-1.compute.internal,},NodeAddress{Type:InternalDNS,Address:ip-172-20-44-71.sa-east-1.compute.internal,},NodeAddress{Type:ExternalDNS,Address:ec2-54-233-223-193.sa-east-1.compute.amazonaws.com,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:ec242195d0a8d5edb5d61dee0e4150b8,SystemUUID:ec242195-d0a8-d5ed-b5d6-1dee0e4150b8,BootID:973519b5-3776-4f91-ba4a-306c280e7bcd,KernelVersion:5.4.0-1045-aws,OSImage:Ubuntu 20.04.2 LTS,ContainerRuntimeVersion:containerd://1.4.6,KubeletVersion:v1.21.0,KubeProxyVersion:v1.21.0,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[k8s.gcr.io/provider-aws/aws-ebs-csi-driver@sha256:a0294bf95fd94eabdc9b313b6c16232019a8707c711c031a2f99ab1f919560bd k8s.gcr.io/provider-aws/aws-ebs-csi-driver:v1.0.0],SizeBytes:67079979,},ContainerImage{Names:[docker.io/calico/node@sha256:bc4a631d553b38fdc169ea4cb8027fa894a656e80d68d513359a4b9d46836b55 docker.io/calico/node:v3.19.1],SizeBytes:58671776,},ContainerImage{Names:[k8s.gcr.io/kube-proxy@sha256:326199e7a5232bf7531a3058e9811c925b07085f33fa882558cc4e89379b9109 k8s.gcr.io/kube-proxy:v1.21.0],SizeBytes:50134170,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/agnhost@sha256:8bd76a6a7778e203b61e18e5ee85b1faf52e6a30eb07e445a165ab90fe9633e3 k8s.gcr.io/e2e-test-images/agnhost:2.31],SizeBytes:49692421,},ContainerImage{Names:[docker.io/calico/cni@sha256:f301171be0add870152483fcce71b28cafb8e910f61ff003032e9b1053b062c4 docker.io/calico/cni:v3.19.1],SizeBytes:48338203,},ContainerImage{Names:[k8s.gcr.io/build-image/debian-iptables@sha256:abe8cef9e116f2d5ec1175c386e33841ff3386779138b425af876384b0fd7ccb k8s.gcr.io/build-image/debian-iptables:buster-v1.5.0],SizeBytes:38088315,},ContainerImage{Names:[quay.io/jetstack/cert-manager-webhook@sha256:41eacd93a30b566b780a6ae525b2547d2a87f1ec5f067fc02840a220aeb0c3f7 quay.io/jetstack/cert-manager-webhook:v1.3.1],SizeBytes:19734169,},ContainerImage{Names:[k8s.gcr.io/cpa/cluster-proportional-autoscaler@sha256:67640771ad9fc56f109d5b01e020f0c858e7c890bb0eb15ba0ebd325df3285e7 k8s.gcr.io/cpa/cluster-proportional-autoscaler:1.8.3],SizeBytes:15191740,},ContainerImage{Names:[docker.io/calico/pod2daemon-flexvol@sha256:bcac7dc4f1301b062d91a177a52d13716907636975c44131fb8350e7f851c944 docker.io/calico/pod2daemon-flexvol:v3.19.1],SizeBytes:9328155,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-node-driver-registrar@sha256:a61d309da54641db41fb8f35718f744e9f730d4d0384f8c4b186ddc9f06cbd5f k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.1.0],SizeBytes:9068367,},ContainerImage{Names:[k8s.gcr.io/sig-storage/livenessprobe@sha256:48da0e4ed7238ad461ea05f68c25921783c37b315f21a5c5a2780157a6460994 k8s.gcr.io/sig-storage/livenessprobe:v2.2.0],SizeBytes:8279778,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/nginx@sha256:503b7abb89e57383eba61cc8a9cb0b495ea575c516108f7d972a6ff6e1ab3c9b k8s.gcr.io/e2e-test-images/nginx:1.14-1],SizeBytes:6979365,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/busybox@sha256:39e1e963e5310e9c313bad51523be012ede7b35bb9316517d19089a010356592 k8s.gcr.io/e2e-test-images/busybox:1.29-1],SizeBytes:732746,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:927d98197ec1141a368550822d18fa1c60bdae27b78b0c004f705f548c07814f k8s.gcr.io/pause:3.2],SizeBytes:299513,},},VolumesInUse:[kubernetes.io/csi/ebs.csi.aws.com^vol-0a537a87c2d4d9f86],VolumesAttached:[]AttachedVolume{AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-0a537a87c2d4d9f86,DevicePath:,},},Config:nil,},}
Jun  6 16:27:06.599: INFO: 
... skipping 172 lines ...
    /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:108
      
      /tmp/kops.42NGBlObb/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.42NGBlObb/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-239 exec restored-pvc-tester-jxdnh --namespace=snapshotting-239 -- 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-239 exec restored-pvc-tester-jxdnh --namespace=snapshotting-239 -- 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.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:602
------------------------------
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral
... skipping 51 lines ...
Jun  6 16:26:22.823: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-8286-e2e-sc88pcw
STEP: creating a claim
Jun  6 16:26:22.969: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-vkxc
STEP: Creating a pod to test exec-volume-test
Jun  6 16:26:23.407: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-vkxc" in namespace "volume-8286" to be "Succeeded or Failed"
Jun  6 16:26:23.552: INFO: Pod "exec-volume-test-dynamicpv-vkxc": Phase="Pending", Reason="", readiness=false. Elapsed: 144.879028ms
Jun  6 16:26:25.697: INFO: Pod "exec-volume-test-dynamicpv-vkxc": Phase="Pending", Reason="", readiness=false. Elapsed: 2.289353334s
Jun  6 16:26:27.843: INFO: Pod "exec-volume-test-dynamicpv-vkxc": Phase="Pending", Reason="", readiness=false. Elapsed: 4.434969185s
Jun  6 16:26:29.989: INFO: Pod "exec-volume-test-dynamicpv-vkxc": Phase="Pending", Reason="", readiness=false. Elapsed: 6.581250876s
Jun  6 16:26:32.134: INFO: Pod "exec-volume-test-dynamicpv-vkxc": Phase="Pending", Reason="", readiness=false. Elapsed: 8.72596401s
Jun  6 16:26:34.278: INFO: Pod "exec-volume-test-dynamicpv-vkxc": Phase="Pending", Reason="", readiness=false. Elapsed: 10.870049114s
Jun  6 16:26:36.422: INFO: Pod "exec-volume-test-dynamicpv-vkxc": Phase="Pending", Reason="", readiness=false. Elapsed: 13.014574155s
Jun  6 16:26:38.566: INFO: Pod "exec-volume-test-dynamicpv-vkxc": Phase="Succeeded", Reason="", readiness=false. Elapsed: 15.158586929s
STEP: Saw pod success
Jun  6 16:26:38.566: INFO: Pod "exec-volume-test-dynamicpv-vkxc" satisfied condition "Succeeded or Failed"
Jun  6 16:26:38.710: INFO: Trying to get logs from node ip-172-20-62-27.sa-east-1.compute.internal pod exec-volume-test-dynamicpv-vkxc container exec-container-dynamicpv-vkxc: <nil>
STEP: delete the pod
Jun  6 16:26:39.009: INFO: Waiting for pod exec-volume-test-dynamicpv-vkxc to disappear
Jun  6 16:26:39.153: INFO: Pod exec-volume-test-dynamicpv-vkxc no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-vkxc
Jun  6 16:26:39.153: INFO: Deleting pod "exec-volume-test-dynamicpv-vkxc" in namespace "volume-8286"
... skipping 162 lines ...
Jun  6 16:25:38.773: INFO: Creating resource for dynamic PV
Jun  6 16:25:38.773: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6560-e2e-scstjfm
STEP: creating a claim
Jun  6 16:25:38.919: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-6560
Jun  6 16:25:39.353: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-6560" in namespace "provisioning-6560" to be "Succeeded or Failed"
Jun  6 16:25:39.497: INFO: Pod "volume-prep-provisioning-6560": Phase="Pending", Reason="", readiness=false. Elapsed: 143.813752ms
Jun  6 16:25:41.648: INFO: Pod "volume-prep-provisioning-6560": Phase="Pending", Reason="", readiness=false. Elapsed: 2.294625463s
Jun  6 16:25:43.792: INFO: Pod "volume-prep-provisioning-6560": Phase="Pending", Reason="", readiness=false. Elapsed: 4.438084739s
Jun  6 16:25:45.938: INFO: Pod "volume-prep-provisioning-6560": Phase="Pending", Reason="", readiness=false. Elapsed: 6.584892029s
Jun  6 16:25:48.084: INFO: Pod "volume-prep-provisioning-6560": Phase="Pending", Reason="", readiness=false. Elapsed: 8.730175745s
Jun  6 16:25:50.228: INFO: Pod "volume-prep-provisioning-6560": Phase="Pending", Reason="", readiness=false. Elapsed: 10.874907488s
... skipping 8 lines ...
Jun  6 16:26:09.542: INFO: Pod "volume-prep-provisioning-6560": Phase="Pending", Reason="", readiness=false. Elapsed: 30.188081572s
Jun  6 16:26:11.701: INFO: Pod "volume-prep-provisioning-6560": Phase="Pending", Reason="", readiness=false. Elapsed: 32.34790782s
Jun  6 16:26:13.845: INFO: Pod "volume-prep-provisioning-6560": Phase="Pending", Reason="", readiness=false. Elapsed: 34.491814829s
Jun  6 16:26:15.992: INFO: Pod "volume-prep-provisioning-6560": Phase="Pending", Reason="", readiness=false. Elapsed: 36.638074032s
Jun  6 16:26:18.136: INFO: Pod "volume-prep-provisioning-6560": Phase="Succeeded", Reason="", readiness=false. Elapsed: 38.782222357s
STEP: Saw pod success
Jun  6 16:26:18.136: INFO: Pod "volume-prep-provisioning-6560" satisfied condition "Succeeded or Failed"
Jun  6 16:26:18.136: INFO: Deleting pod "volume-prep-provisioning-6560" in namespace "provisioning-6560"
Jun  6 16:26:18.285: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-6560" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-ffvm
STEP: Checking for subpath error in container status
Jun  6 16:26:52.865: INFO: Deleting pod "pod-subpath-test-dynamicpv-ffvm" in namespace "provisioning-6560"
Jun  6 16:26:53.015: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-ffvm" to be fully deleted
STEP: Deleting pod
Jun  6 16:26:53.159: INFO: Deleting pod "pod-subpath-test-dynamicpv-ffvm" in namespace "provisioning-6560"
STEP: Deleting pvc
Jun  6 16:26:53.589: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com7xxb7"
... skipping 401 lines ...
Jun  6 16:25:21.599: INFO: Creating resource for dynamic PV
Jun  6 16:25:21.599: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-1681-e2e-sczkm5r
STEP: creating a claim
Jun  6 16:25:21.745: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun  6 16:25:22.182: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-4dcqx" in namespace "snapshotting-1681" to be "Succeeded or Failed"
Jun  6 16:25:22.330: INFO: Pod "pvc-snapshottable-tester-4dcqx": Phase="Pending", Reason="", readiness=false. Elapsed: 147.178255ms
Jun  6 16:25:24.478: INFO: Pod "pvc-snapshottable-tester-4dcqx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.295689825s
Jun  6 16:25:26.624: INFO: Pod "pvc-snapshottable-tester-4dcqx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.441395932s
Jun  6 16:25:28.773: INFO: Pod "pvc-snapshottable-tester-4dcqx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.590715544s
Jun  6 16:25:30.920: INFO: Pod "pvc-snapshottable-tester-4dcqx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.73776775s
Jun  6 16:25:33.071: INFO: Pod "pvc-snapshottable-tester-4dcqx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.888892757s
Jun  6 16:25:35.219: INFO: Pod "pvc-snapshottable-tester-4dcqx": Phase="Pending", Reason="", readiness=false. Elapsed: 13.036377936s
Jun  6 16:25:37.365: INFO: Pod "pvc-snapshottable-tester-4dcqx": Phase="Pending", Reason="", readiness=false. Elapsed: 15.182476394s
Jun  6 16:25:39.512: INFO: Pod "pvc-snapshottable-tester-4dcqx": Phase="Pending", Reason="", readiness=false. Elapsed: 17.329478837s
Jun  6 16:25:41.666: INFO: Pod "pvc-snapshottable-tester-4dcqx": Phase="Pending", Reason="", readiness=false. Elapsed: 19.483679156s
Jun  6 16:25:43.811: INFO: Pod "pvc-snapshottable-tester-4dcqx": Phase="Pending", Reason="", readiness=false. Elapsed: 21.628975907s
Jun  6 16:25:45.957: INFO: Pod "pvc-snapshottable-tester-4dcqx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.774903092s
STEP: Saw pod success
Jun  6 16:25:45.957: INFO: Pod "pvc-snapshottable-tester-4dcqx" satisfied condition "Succeeded or Failed"
Jun  6 16:25:46.253: INFO: Pod pvc-snapshottable-tester-4dcqx has the following logs: 
Jun  6 16:25:46.253: INFO: Deleting pod "pvc-snapshottable-tester-4dcqx" in namespace "snapshotting-1681"
Jun  6 16:25:46.405: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-4dcqx" to be fully deleted
Jun  6 16:25:46.550: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comchxt4] to have phase Bound
Jun  6 16:25:46.694: INFO: PersistentVolumeClaim ebs.csi.aws.comchxt4 found and phase=Bound (144.387897ms)
STEP: [init] checking the claim
... skipping 42 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.42NGBlObb/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  6 16:26:19.859: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-2l9g6" in namespace "snapshotting-1681" to be "Succeeded or Failed"
Jun  6 16:26:20.008: INFO: Pod "pvc-snapshottable-data-tester-2l9g6": Phase="Pending", Reason="", readiness=false. Elapsed: 148.8911ms
Jun  6 16:26:22.156: INFO: Pod "pvc-snapshottable-data-tester-2l9g6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.297304021s
Jun  6 16:26:24.304: INFO: Pod "pvc-snapshottable-data-tester-2l9g6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.445370177s
Jun  6 16:26:26.450: INFO: Pod "pvc-snapshottable-data-tester-2l9g6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.590892682s
Jun  6 16:26:28.595: INFO: Pod "pvc-snapshottable-data-tester-2l9g6": Phase="Pending", Reason="", readiness=false. Elapsed: 8.736301793s
Jun  6 16:26:30.741: INFO: Pod "pvc-snapshottable-data-tester-2l9g6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.881660892s
STEP: Saw pod success
Jun  6 16:26:30.741: INFO: Pod "pvc-snapshottable-data-tester-2l9g6" satisfied condition "Succeeded or Failed"
Jun  6 16:26:31.033: INFO: Pod pvc-snapshottable-data-tester-2l9g6 has the following logs: 
Jun  6 16:26:31.033: INFO: Deleting pod "pvc-snapshottable-data-tester-2l9g6" in namespace "snapshotting-1681"
Jun  6 16:26:31.199: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-2l9g6" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun  6 16:26:53.926: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-1681 exec restored-pvc-tester-fbs5x --namespace=snapshotting-1681 -- cat /mnt/test/data'
... skipping 30 lines ...
Jun  6 16:27:20.125: INFO: volumesnapshotcontents pre-provisioned-snapcontent-ea33afac-e370-474d-ad7a-a7517be413da has been found and is not deleted
Jun  6 16:27:21.273: INFO: volumesnapshotcontents pre-provisioned-snapcontent-ea33afac-e370-474d-ad7a-a7517be413da has been found and is not deleted
Jun  6 16:27:22.421: INFO: volumesnapshotcontents pre-provisioned-snapcontent-ea33afac-e370-474d-ad7a-a7517be413da has been found and is not deleted
Jun  6 16:27:23.569: INFO: volumesnapshotcontents pre-provisioned-snapcontent-ea33afac-e370-474d-ad7a-a7517be413da has been found and is not deleted
Jun  6 16:27:24.717: INFO: volumesnapshotcontents pre-provisioned-snapcontent-ea33afac-e370-474d-ad7a-a7517be413da has been found and is not deleted
Jun  6 16:27:25.869: INFO: volumesnapshotcontents pre-provisioned-snapcontent-ea33afac-e370-474d-ad7a-a7517be413da has been found and is not deleted
Jun  6 16:27:26.869: INFO: WaitUntil failed after reaching the timeout 30s
[AfterEach] volume snapshot controller
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:221
Jun  6 16:27:27.016: INFO: Pod restored-pvc-tester-fbs5x has the following logs: 
Jun  6 16:27:27.016: INFO: Deleting pod "restored-pvc-tester-fbs5x" in namespace "snapshotting-1681"
Jun  6 16:27:27.162: INFO: Wait up to 5m0s for pod "restored-pvc-tester-fbs5x" to be fully deleted
Jun  6 16:28:05.456: INFO: deleting claim "snapshotting-1681"/"pvc-28xfd"
... skipping 91 lines ...
Jun  6 16:27:59.577: INFO: Pod aws-client still exists
Jun  6 16:28:01.579: INFO: Waiting for pod aws-client to disappear
Jun  6 16:28:01.725: INFO: Pod aws-client still exists
Jun  6 16:28:03.578: INFO: Waiting for pod aws-client to disappear
Jun  6 16:28:03.722: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun  6 16:28:04.554: INFO: Couldn't delete PD "aws://sa-east-1a/vol-08577b3dfe9ad14cc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08577b3dfe9ad14cc is currently attached to i-0497bb511a26d2153
	status code: 400, request id: 0fda6419-0f65-45ce-a463-9e4af44e317d
Jun  6 16:28:10.634: INFO: Couldn't delete PD "aws://sa-east-1a/vol-08577b3dfe9ad14cc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08577b3dfe9ad14cc is currently attached to i-0497bb511a26d2153
	status code: 400, request id: 9a1d712f-0e1e-400e-8bed-46b659ec8b2e
Jun  6 16:28:16.567: INFO: Successfully deleted PD "aws://sa-east-1a/vol-08577b3dfe9ad14cc".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  6 16:28:16.567: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-4401" for this suite.
... skipping 147 lines ...
Jun  6 16:26:18.544: INFO: Creating resource for dynamic PV
Jun  6 16:26:18.544: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-8174-e2e-scszjlw
STEP: creating a claim
Jun  6 16:26:18.689: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun  6 16:26:19.133: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-slltt" in namespace "snapshotting-8174" to be "Succeeded or Failed"
Jun  6 16:26:19.277: INFO: Pod "pvc-snapshottable-tester-slltt": Phase="Pending", Reason="", readiness=false. Elapsed: 144.035501ms
Jun  6 16:26:21.423: INFO: Pod "pvc-snapshottable-tester-slltt": Phase="Pending", Reason="", readiness=false. Elapsed: 2.289948726s
Jun  6 16:26:23.568: INFO: Pod "pvc-snapshottable-tester-slltt": Phase="Pending", Reason="", readiness=false. Elapsed: 4.435028814s
Jun  6 16:26:25.713: INFO: Pod "pvc-snapshottable-tester-slltt": Phase="Pending", Reason="", readiness=false. Elapsed: 6.580137659s
Jun  6 16:26:27.858: INFO: Pod "pvc-snapshottable-tester-slltt": Phase="Pending", Reason="", readiness=false. Elapsed: 8.724957646s
Jun  6 16:26:30.005: INFO: Pod "pvc-snapshottable-tester-slltt": Phase="Pending", Reason="", readiness=false. Elapsed: 10.871644396s
Jun  6 16:26:32.149: INFO: Pod "pvc-snapshottable-tester-slltt": Phase="Pending", Reason="", readiness=false. Elapsed: 13.015775965s
Jun  6 16:26:34.294: INFO: Pod "pvc-snapshottable-tester-slltt": Phase="Pending", Reason="", readiness=false. Elapsed: 15.160594101s
Jun  6 16:26:36.438: INFO: Pod "pvc-snapshottable-tester-slltt": Phase="Pending", Reason="", readiness=false. Elapsed: 17.305260533s
Jun  6 16:26:38.583: INFO: Pod "pvc-snapshottable-tester-slltt": Phase="Pending", Reason="", readiness=false. Elapsed: 19.450180889s
Jun  6 16:26:40.727: INFO: Pod "pvc-snapshottable-tester-slltt": Phase="Pending", Reason="", readiness=false. Elapsed: 21.59415425s
Jun  6 16:26:42.872: INFO: Pod "pvc-snapshottable-tester-slltt": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.739354841s
STEP: Saw pod success
Jun  6 16:26:42.872: INFO: Pod "pvc-snapshottable-tester-slltt" satisfied condition "Succeeded or Failed"
Jun  6 16:26:43.162: INFO: Pod pvc-snapshottable-tester-slltt has the following logs: 
Jun  6 16:26:43.162: INFO: Deleting pod "pvc-snapshottable-tester-slltt" in namespace "snapshotting-8174"
Jun  6 16:26:43.311: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-slltt" to be fully deleted
Jun  6 16:26:43.454: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.com9dhkf] to have phase Bound
Jun  6 16:26:43.599: INFO: PersistentVolumeClaim ebs.csi.aws.com9dhkf found and phase=Bound (144.085316ms)
STEP: [init] checking the claim
... skipping 53 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.42NGBlObb/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  6 16:27:40.315: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-4qtpp" in namespace "snapshotting-8174" to be "Succeeded or Failed"
Jun  6 16:27:40.461: INFO: Pod "pvc-snapshottable-data-tester-4qtpp": Phase="Pending", Reason="", readiness=false. Elapsed: 145.709048ms
Jun  6 16:27:42.606: INFO: Pod "pvc-snapshottable-data-tester-4qtpp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.29080113s
Jun  6 16:27:44.751: INFO: Pod "pvc-snapshottable-data-tester-4qtpp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.435724758s
Jun  6 16:27:46.897: INFO: Pod "pvc-snapshottable-data-tester-4qtpp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.581207176s
Jun  6 16:27:49.042: INFO: Pod "pvc-snapshottable-data-tester-4qtpp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.726391935s
Jun  6 16:27:51.188: INFO: Pod "pvc-snapshottable-data-tester-4qtpp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.872226855s
STEP: Saw pod success
Jun  6 16:27:51.188: INFO: Pod "pvc-snapshottable-data-tester-4qtpp" satisfied condition "Succeeded or Failed"
Jun  6 16:27:51.478: INFO: Pod pvc-snapshottable-data-tester-4qtpp has the following logs: 
Jun  6 16:27:51.479: INFO: Deleting pod "pvc-snapshottable-data-tester-4qtpp" in namespace "snapshotting-8174"
Jun  6 16:27:51.631: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-4qtpp" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun  6 16:28:02.362: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-8174 exec restored-pvc-tester-5mtt7 --namespace=snapshotting-8174 -- cat /mnt/test/data'
... skipping 45 lines ...
        /tmp/kops.42NGBlObb/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:243
------------------------------


Summarizing 2 Failures:

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

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

Ran 141 of 485 Specs in 613.279 seconds
FAIL! -- 139 Passed | 2 Failed | 0 Pending | 344 Skipped


Ginkgo ran 1 suite in 12m53.782091869s
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
I0606 16:28:54.268314   26672 app.go:59] RunDir for this run: "/logs/artifacts/8542e6d1-c6e0-11eb-a95e-22b332769ebd"
I0606 16:28:54.270841   26672 app.go:90] ID for this run: "8542e6d1-c6e0-11eb-a95e-22b332769ebd"
I0606 16:28:54.271733   26672 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
I0606 16:28:54.315785   26678 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
... skipping 1479 lines ...