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 08:02
Elapsed30m36s
Revisionmaster

No Test Failures!


Error lines from build-log.txt

... skipping 488 lines ...
I0606 08:07:52.891241   11673 up.go:43] Cleaning up any leaked resources from previous cluster
I0606 08:07:52.891261   11673 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 08:07:52.906198   11680 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0606 08:07:52.907023   11680 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io" not found
W0606 08:07:53.414598   11673 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0606 08:07:53.414634   11673 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 08:07:53.430262   11690 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0606 08:07:53.430353   11690 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 08:07:53.904337   11673 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/06/06 08:07:53 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 08:07:53.916993   11673 http.go:37] curl https://ip.jsb.workers.dev
I0606 08:07:54.155856   11673 up.go:144] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops create cluster --name e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --cloud aws --kubernetes-version 1.21.0 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --networking calico --override=cluster.spec.cloudConfig.awsEBSCSIDriver.enabled=true --override=cluster.spec.snapshotController.enabled=true --override=cluster.spec.certManager.enabled=true --admin-access 35.184.235.34/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-northeast-2a --master-size c5.large
I0606 08:07:54.170783   11704 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0606 08:07:54.171771   11704 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I0606 08:07:54.221041   11704 create_cluster.go:728] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0606 08:07:54.741440   11704 new_cluster.go:1051]  Cloud Provider ID = aws
... skipping 40 lines ...

I0606 08:08:25.727070   11673 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 08:08:25.740907   11724 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0606 08:08:25.740988   11724 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io

W0606 08:08:27.217748   11724 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-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0606 08:08:37.249191   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0606 08:08:47.286566   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0606 08:08:57.332806   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0606 08:09:07.364531   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0606 08:09:17.397978   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
W0606 08:09:27.428204   11724 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-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0606 08:09:37.476354   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0606 08:09:47.526713   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0606 08:09:57.559169   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
W0606 08:10:07.593010   11724 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-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0606 08:10:17.625885   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0606 08:10:27.659500   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
W0606 08:10:37.679651   11724 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-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0606 08:10:47.717258   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0606 08:10:57.745308   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0606 08:11:07.775579   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0606 08:11:17.823397   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0606 08:11:27.867075   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0606 08:11:37.901161   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0606 08:11:47.936691   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0606 08:11:57.983372   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0606 08:12:08.028291   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
W0606 08:12:18.057789   11724 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-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0606 08:12:28.091704   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0606 08:12:38.121593   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0606 08:12:48.157226   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0606 08:12:58.193078   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0606 08:13:08.223139   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0606 08:13:18.260820   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0606 08:13:28.294512   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0606 08:13:38.326351   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0606 08:13:48.377359   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0606 08:13:58.415323   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0606 08:14:08.448143   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0606 08:14:18.477901   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0606 08:14:28.513148   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 11 lines ...
Pod	kube-system/cert-manager-cainjector-74d69756d5-6b4l2	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-6b4l2" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-pqkrx	system-cluster-critical pod "cert-manager-webhook-7bbf67968-pqkrx" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-tb9ks		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-tb9ks" is pending
Pod	kube-system/coredns-f45c4bf76-lhfn5			system-cluster-critical pod "coredns-f45c4bf76-lhfn5" is pending
Pod	kube-system/ebs-csi-node-wg2g2				system-node-critical pod "ebs-csi-node-wg2g2" is pending

Validation Failed
W0606 08:14:42.254650   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 21 lines ...
Pod	kube-system/ebs-csi-node-llnfc						system-node-critical pod "ebs-csi-node-llnfc" is pending
Pod	kube-system/ebs-csi-node-wg2g2						system-node-critical pod "ebs-csi-node-wg2g2" is pending
Pod	kube-system/kube-proxy-ip-172-20-40-222.ap-northeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-40-222.ap-northeast-2.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-47-232.ap-northeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-47-232.ap-northeast-2.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-53-171.ap-northeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-53-171.ap-northeast-2.compute.internal" is pending

Validation Failed
W0606 08:14:54.854408   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 22 lines ...
Pod	kube-system/ebs-csi-node-2gsn7						system-node-critical pod "ebs-csi-node-2gsn7" is pending
Pod	kube-system/ebs-csi-node-6ngtz						system-node-critical pod "ebs-csi-node-6ngtz" is pending
Pod	kube-system/ebs-csi-node-llnfc						system-node-critical pod "ebs-csi-node-llnfc" is pending
Pod	kube-system/ebs-csi-node-wg2g2						system-node-critical pod "ebs-csi-node-wg2g2" is pending
Pod	kube-system/kube-proxy-ip-172-20-33-48.ap-northeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-33-48.ap-northeast-2.compute.internal" is pending

Validation Failed
W0606 08:15:07.567548   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 18 lines ...
Pod	kube-system/coredns-f45c4bf76-lhfn5					system-cluster-critical pod "coredns-f45c4bf76-lhfn5" is pending
Pod	kube-system/ebs-csi-node-2gsn7						system-node-critical pod "ebs-csi-node-2gsn7" is pending
Pod	kube-system/ebs-csi-node-6ngtz						system-node-critical pod "ebs-csi-node-6ngtz" is pending
Pod	kube-system/ebs-csi-node-llnfc						system-node-critical pod "ebs-csi-node-llnfc" is pending
Pod	kube-system/kube-proxy-ip-172-20-33-48.ap-northeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-33-48.ap-northeast-2.compute.internal" is pending

Validation Failed
W0606 08:15:20.172146   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 13 lines ...
Pod	kube-system/calico-node-hvtqf				system-node-critical pod "calico-node-hvtqf" is not ready (calico-node)
Pod	kube-system/cert-manager-cainjector-74d69756d5-6b4l2	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-6b4l2" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-pqkrx	system-cluster-critical pod "cert-manager-webhook-7bbf67968-pqkrx" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-tb9ks		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-tb9ks" is pending
Pod	kube-system/ebs-csi-node-6ngtz				system-node-critical pod "ebs-csi-node-6ngtz" is pending

Validation Failed
W0606 08:15:32.761498   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 9 lines ...
KIND	NAME							MESSAGE
Pod	kube-system/calico-node-7fb5h				system-node-critical pod "calico-node-7fb5h" is not ready (calico-node)
Pod	kube-system/calico-node-7mwmk				system-node-critical pod "calico-node-7mwmk" is not ready (calico-node)
Pod	kube-system/calico-node-d2zxq				system-node-critical pod "calico-node-d2zxq" is not ready (calico-node)
Pod	kube-system/cert-manager-webhook-7bbf67968-pqkrx	system-cluster-critical pod "cert-manager-webhook-7bbf67968-pqkrx" is not ready (cert-manager)

Validation Failed
W0606 08:15:45.350269   11724 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

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

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

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 455 lines ...
Jun  6 08:19:19.223: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 253 lines ...
Jun  6 08:19:21.125: INFO: PersistentVolumeClaim pvc-hphcx found but phase is Pending instead of Bound.
Jun  6 08:19:23.288: INFO: PersistentVolumeClaim pvc-hphcx found and phase=Bound (4.491023645s)
Jun  6 08:19:23.288: INFO: Waiting up to 3m0s for PersistentVolume aws-m256b to have phase Bound
Jun  6 08:19:23.454: INFO: PersistentVolume aws-m256b found and phase=Bound (165.564894ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-rgz2
STEP: Creating a pod to test exec-volume-test
Jun  6 08:19:23.945: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-rgz2" in namespace "volume-8624" to be "Succeeded or Failed"
Jun  6 08:19:24.107: INFO: Pod "exec-volume-test-preprovisionedpv-rgz2": Phase="Pending", Reason="", readiness=false. Elapsed: 162.19803ms
Jun  6 08:19:26.269: INFO: Pod "exec-volume-test-preprovisionedpv-rgz2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.324782157s
Jun  6 08:19:28.435: INFO: Pod "exec-volume-test-preprovisionedpv-rgz2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.490178242s
Jun  6 08:19:30.598: INFO: Pod "exec-volume-test-preprovisionedpv-rgz2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.653192646s
Jun  6 08:19:32.760: INFO: Pod "exec-volume-test-preprovisionedpv-rgz2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.81516754s
Jun  6 08:19:34.921: INFO: Pod "exec-volume-test-preprovisionedpv-rgz2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.976903971s
Jun  6 08:19:37.085: INFO: Pod "exec-volume-test-preprovisionedpv-rgz2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 13.140313543s
STEP: Saw pod success
Jun  6 08:19:37.085: INFO: Pod "exec-volume-test-preprovisionedpv-rgz2" satisfied condition "Succeeded or Failed"
Jun  6 08:19:37.253: INFO: Trying to get logs from node ip-172-20-53-171.ap-northeast-2.compute.internal pod exec-volume-test-preprovisionedpv-rgz2 container exec-container-preprovisionedpv-rgz2: <nil>
STEP: delete the pod
Jun  6 08:19:37.605: INFO: Waiting for pod exec-volume-test-preprovisionedpv-rgz2 to disappear
Jun  6 08:19:37.768: INFO: Pod exec-volume-test-preprovisionedpv-rgz2 no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-rgz2
Jun  6 08:19:37.768: INFO: Deleting pod "exec-volume-test-preprovisionedpv-rgz2" in namespace "volume-8624"
STEP: Deleting pv and pvc
Jun  6 08:19:37.930: INFO: Deleting PersistentVolumeClaim "pvc-hphcx"
Jun  6 08:19:38.092: INFO: Deleting PersistentVolume "aws-m256b"
Jun  6 08:19:38.543: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-06c3fdc85cc6f850c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-06c3fdc85cc6f850c is currently attached to i-037bcb7083139f8fd
	status code: 400, request id: f03b856b-07c7-465e-bb33-4524f95b7365
Jun  6 08:19:44.337: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-06c3fdc85cc6f850c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-06c3fdc85cc6f850c is currently attached to i-037bcb7083139f8fd
	status code: 400, request id: e92ddd90-0f87-4576-a31b-e4b2e9eda424
Jun  6 08:19:50.122: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-06c3fdc85cc6f850c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-06c3fdc85cc6f850c is currently attached to i-037bcb7083139f8fd
	status code: 400, request id: 93cb6bca-eeaa-4efc-9457-0be910dba615
Jun  6 08:19:55.916: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-06c3fdc85cc6f850c".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  6 08:19:55.916: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8624" for this suite.
... skipping 114 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  6 08:19:19.959: 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.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun  6 08:19:20.738: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  6 08:19:20.738: INFO: Creating resource for dynamic PV
Jun  6 08:19:20.738: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-955ss7pg
STEP: creating a claim
Jun  6 08:19:20.897: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-dpjx
STEP: Checking for subpath error in container status
Jun  6 08:19:41.684: INFO: Deleting pod "pod-subpath-test-dynamicpv-dpjx" in namespace "provisioning-955"
Jun  6 08:19:41.847: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-dpjx" to be fully deleted
STEP: Deleting pod
Jun  6 08:19:54.157: INFO: Deleting pod "pod-subpath-test-dynamicpv-dpjx" in namespace "provisioning-955"
STEP: Deleting pvc
Jun  6 08:19:54.621: INFO: Deleting PersistentVolumeClaim "awskx4sh"
... skipping 11 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Q9ZXkT72D/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Q9ZXkT72D/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath directory is outside the volume [Slow][LinuxOnly]
      /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 9 lines ...
Jun  6 08:19:18.319: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-765-e2e-scqfhc2
STEP: creating a claim
Jun  6 08:19:18.480: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-htdg
STEP: Creating a pod to test subpath
Jun  6 08:19:18.957: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-htdg" in namespace "provisioning-765" to be "Succeeded or Failed"
Jun  6 08:19:19.114: INFO: Pod "pod-subpath-test-dynamicpv-htdg": Phase="Pending", Reason="", readiness=false. Elapsed: 157.432465ms
Jun  6 08:19:21.273: INFO: Pod "pod-subpath-test-dynamicpv-htdg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.315854873s
Jun  6 08:19:23.431: INFO: Pod "pod-subpath-test-dynamicpv-htdg": Phase="Pending", Reason="", readiness=false. Elapsed: 4.473817536s
Jun  6 08:19:25.592: INFO: Pod "pod-subpath-test-dynamicpv-htdg": Phase="Pending", Reason="", readiness=false. Elapsed: 6.634820046s
Jun  6 08:19:27.751: INFO: Pod "pod-subpath-test-dynamicpv-htdg": Phase="Pending", Reason="", readiness=false. Elapsed: 8.794248773s
Jun  6 08:19:29.909: INFO: Pod "pod-subpath-test-dynamicpv-htdg": Phase="Pending", Reason="", readiness=false. Elapsed: 10.952280752s
... skipping 2 lines ...
Jun  6 08:19:36.388: INFO: Pod "pod-subpath-test-dynamicpv-htdg": Phase="Pending", Reason="", readiness=false. Elapsed: 17.431200898s
Jun  6 08:19:38.549: INFO: Pod "pod-subpath-test-dynamicpv-htdg": Phase="Pending", Reason="", readiness=false. Elapsed: 19.592022626s
Jun  6 08:19:40.708: INFO: Pod "pod-subpath-test-dynamicpv-htdg": Phase="Pending", Reason="", readiness=false. Elapsed: 21.751163123s
Jun  6 08:19:42.866: INFO: Pod "pod-subpath-test-dynamicpv-htdg": Phase="Pending", Reason="", readiness=false. Elapsed: 23.909026101s
Jun  6 08:19:45.024: INFO: Pod "pod-subpath-test-dynamicpv-htdg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.06747482s
STEP: Saw pod success
Jun  6 08:19:45.024: INFO: Pod "pod-subpath-test-dynamicpv-htdg" satisfied condition "Succeeded or Failed"
Jun  6 08:19:45.182: INFO: Trying to get logs from node ip-172-20-53-171.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-htdg container test-container-subpath-dynamicpv-htdg: <nil>
STEP: delete the pod
Jun  6 08:19:45.512: INFO: Waiting for pod pod-subpath-test-dynamicpv-htdg to disappear
Jun  6 08:19:45.670: INFO: Pod pod-subpath-test-dynamicpv-htdg no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-htdg
Jun  6 08:19:45.670: INFO: Deleting pod "pod-subpath-test-dynamicpv-htdg" in namespace "provisioning-765"
... skipping 30 lines ...

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

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

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.Q9ZXkT72D/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.Q9ZXkT72D/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.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 32 lines ...
Jun  6 08:19:17.153: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-725-e2e-sccnzrk
STEP: creating a claim
Jun  6 08:19:17.312: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-8w2t
STEP: Creating a pod to test subpath
Jun  6 08:19:17.789: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-8w2t" in namespace "provisioning-725" to be "Succeeded or Failed"
Jun  6 08:19:17.946: INFO: Pod "pod-subpath-test-dynamicpv-8w2t": Phase="Pending", Reason="", readiness=false. Elapsed: 157.524964ms
Jun  6 08:19:20.105: INFO: Pod "pod-subpath-test-dynamicpv-8w2t": Phase="Pending", Reason="", readiness=false. Elapsed: 2.316548405s
Jun  6 08:19:22.264: INFO: Pod "pod-subpath-test-dynamicpv-8w2t": Phase="Pending", Reason="", readiness=false. Elapsed: 4.475329795s
Jun  6 08:19:24.422: INFO: Pod "pod-subpath-test-dynamicpv-8w2t": Phase="Pending", Reason="", readiness=false. Elapsed: 6.633336955s
Jun  6 08:19:26.580: INFO: Pod "pod-subpath-test-dynamicpv-8w2t": Phase="Pending", Reason="", readiness=false. Elapsed: 8.791251159s
Jun  6 08:19:28.742: INFO: Pod "pod-subpath-test-dynamicpv-8w2t": Phase="Pending", Reason="", readiness=false. Elapsed: 10.953059251s
... skipping 3 lines ...
Jun  6 08:19:37.385: INFO: Pod "pod-subpath-test-dynamicpv-8w2t": Phase="Pending", Reason="", readiness=false. Elapsed: 19.596120821s
Jun  6 08:19:39.542: INFO: Pod "pod-subpath-test-dynamicpv-8w2t": Phase="Pending", Reason="", readiness=false. Elapsed: 21.75347423s
Jun  6 08:19:41.700: INFO: Pod "pod-subpath-test-dynamicpv-8w2t": Phase="Pending", Reason="", readiness=false. Elapsed: 23.911138731s
Jun  6 08:19:43.860: INFO: Pod "pod-subpath-test-dynamicpv-8w2t": Phase="Pending", Reason="", readiness=false. Elapsed: 26.071090288s
Jun  6 08:19:46.017: INFO: Pod "pod-subpath-test-dynamicpv-8w2t": Phase="Succeeded", Reason="", readiness=false. Elapsed: 28.228655014s
STEP: Saw pod success
Jun  6 08:19:46.018: INFO: Pod "pod-subpath-test-dynamicpv-8w2t" satisfied condition "Succeeded or Failed"
Jun  6 08:19:46.175: INFO: Trying to get logs from node ip-172-20-33-48.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-8w2t container test-container-subpath-dynamicpv-8w2t: <nil>
STEP: delete the pod
Jun  6 08:19:47.684: INFO: Waiting for pod pod-subpath-test-dynamicpv-8w2t to disappear
Jun  6 08:19:47.841: INFO: Pod pod-subpath-test-dynamicpv-8w2t no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-8w2t
Jun  6 08:19:47.841: INFO: Deleting pod "pod-subpath-test-dynamicpv-8w2t" in namespace "provisioning-725"
... skipping 35 lines ...
Jun  6 08:19:19.896: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7425-e2e-sc2wdsk
STEP: creating a claim
Jun  6 08:19:20.055: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-k2zm
STEP: Creating a pod to test subpath
Jun  6 08:19:20.537: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-k2zm" in namespace "provisioning-7425" to be "Succeeded or Failed"
Jun  6 08:19:20.695: INFO: Pod "pod-subpath-test-dynamicpv-k2zm": Phase="Pending", Reason="", readiness=false. Elapsed: 158.300576ms
Jun  6 08:19:22.858: INFO: Pod "pod-subpath-test-dynamicpv-k2zm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.321264722s
Jun  6 08:19:25.019: INFO: Pod "pod-subpath-test-dynamicpv-k2zm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.481605791s
Jun  6 08:19:27.178: INFO: Pod "pod-subpath-test-dynamicpv-k2zm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.641251679s
Jun  6 08:19:29.337: INFO: Pod "pod-subpath-test-dynamicpv-k2zm": Phase="Pending", Reason="", readiness=false. Elapsed: 8.799563709s
Jun  6 08:19:31.494: INFO: Pod "pod-subpath-test-dynamicpv-k2zm": Phase="Pending", Reason="", readiness=false. Elapsed: 10.957372088s
... skipping 3 lines ...
Jun  6 08:19:40.138: INFO: Pod "pod-subpath-test-dynamicpv-k2zm": Phase="Pending", Reason="", readiness=false. Elapsed: 19.60047913s
Jun  6 08:19:42.296: INFO: Pod "pod-subpath-test-dynamicpv-k2zm": Phase="Pending", Reason="", readiness=false. Elapsed: 21.759103915s
Jun  6 08:19:44.455: INFO: Pod "pod-subpath-test-dynamicpv-k2zm": Phase="Pending", Reason="", readiness=false. Elapsed: 23.91820312s
Jun  6 08:19:46.613: INFO: Pod "pod-subpath-test-dynamicpv-k2zm": Phase="Pending", Reason="", readiness=false. Elapsed: 26.076078414s
Jun  6 08:19:48.775: INFO: Pod "pod-subpath-test-dynamicpv-k2zm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 28.237801873s
STEP: Saw pod success
Jun  6 08:19:48.775: INFO: Pod "pod-subpath-test-dynamicpv-k2zm" satisfied condition "Succeeded or Failed"
Jun  6 08:19:48.932: INFO: Trying to get logs from node ip-172-20-47-232.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-k2zm container test-container-subpath-dynamicpv-k2zm: <nil>
STEP: delete the pod
Jun  6 08:19:49.553: INFO: Waiting for pod pod-subpath-test-dynamicpv-k2zm to disappear
Jun  6 08:19:49.710: INFO: Pod pod-subpath-test-dynamicpv-k2zm no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-k2zm
Jun  6 08:19:49.710: INFO: Deleting pod "pod-subpath-test-dynamicpv-k2zm" in namespace "provisioning-7425"
... skipping 77 lines ...
Jun  6 08:19:17.186: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-9453-e2e-sc7q6sf
STEP: creating a claim
Jun  6 08:19:17.346: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-pmlq
STEP: Creating a pod to test exec-volume-test
Jun  6 08:19:17.826: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-pmlq" in namespace "volume-9453" to be "Succeeded or Failed"
Jun  6 08:19:18.002: INFO: Pod "exec-volume-test-dynamicpv-pmlq": Phase="Pending", Reason="", readiness=false. Elapsed: 175.384801ms
Jun  6 08:19:20.161: INFO: Pod "exec-volume-test-dynamicpv-pmlq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.334890865s
Jun  6 08:19:22.321: INFO: Pod "exec-volume-test-dynamicpv-pmlq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.495125441s
Jun  6 08:19:24.480: INFO: Pod "exec-volume-test-dynamicpv-pmlq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.654281137s
Jun  6 08:19:26.639: INFO: Pod "exec-volume-test-dynamicpv-pmlq": Phase="Pending", Reason="", readiness=false. Elapsed: 8.813271203s
Jun  6 08:19:28.799: INFO: Pod "exec-volume-test-dynamicpv-pmlq": Phase="Pending", Reason="", readiness=false. Elapsed: 10.973260216s
Jun  6 08:19:30.960: INFO: Pod "exec-volume-test-dynamicpv-pmlq": Phase="Pending", Reason="", readiness=false. Elapsed: 13.133463293s
Jun  6 08:19:33.120: INFO: Pod "exec-volume-test-dynamicpv-pmlq": Phase="Pending", Reason="", readiness=false. Elapsed: 15.293831809s
Jun  6 08:19:35.280: INFO: Pod "exec-volume-test-dynamicpv-pmlq": Phase="Pending", Reason="", readiness=false. Elapsed: 17.453720827s
Jun  6 08:19:37.440: INFO: Pod "exec-volume-test-dynamicpv-pmlq": Phase="Pending", Reason="", readiness=false. Elapsed: 19.614059505s
Jun  6 08:19:39.599: INFO: Pod "exec-volume-test-dynamicpv-pmlq": Phase="Pending", Reason="", readiness=false. Elapsed: 21.772851535s
Jun  6 08:19:41.758: INFO: Pod "exec-volume-test-dynamicpv-pmlq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.93197136s
STEP: Saw pod success
Jun  6 08:19:41.758: INFO: Pod "exec-volume-test-dynamicpv-pmlq" satisfied condition "Succeeded or Failed"
Jun  6 08:19:41.922: INFO: Trying to get logs from node ip-172-20-40-222.ap-northeast-2.compute.internal pod exec-volume-test-dynamicpv-pmlq container exec-container-dynamicpv-pmlq: <nil>
STEP: delete the pod
Jun  6 08:19:42.265: INFO: Waiting for pod exec-volume-test-dynamicpv-pmlq to disappear
Jun  6 08:19:42.424: INFO: Pod exec-volume-test-dynamicpv-pmlq no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-pmlq
Jun  6 08:19:42.424: INFO: Deleting pod "exec-volume-test-dynamicpv-pmlq" in namespace "volume-9453"
... skipping 80 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Q9ZXkT72D/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Q9ZXkT72D/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.Q9ZXkT72D/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.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 23 lines ...
STEP: Creating a kubernetes client
Jun  6 08:19:16.041: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename provisioning
W0606 08:19:17.006742   25624 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Jun  6 08:19:17.006: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail if non-existent subpath is outside the volume [Slow][LinuxOnly]
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun  6 08:19:17.320: INFO: Creating resource for dynamic PV
Jun  6 08:19:17.320: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5710-e2e-sc25kln
STEP: creating a claim
Jun  6 08:19:17.479: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-gg7d
STEP: Checking for subpath error in container status
Jun  6 08:19:52.277: INFO: Deleting pod "pod-subpath-test-dynamicpv-gg7d" in namespace "provisioning-5710"
Jun  6 08:19:52.436: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-gg7d" to be fully deleted
STEP: Deleting pod
Jun  6 08:19:58.752: INFO: Deleting pod "pod-subpath-test-dynamicpv-gg7d" in namespace "provisioning-5710"
STEP: Deleting pvc
Jun  6 08:19:59.224: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comsnbq5"
... skipping 15 lines ...

• [SLOW TEST:80.248 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.Q9ZXkT72D/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.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] volumes
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] volumes
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 258 lines ...
Jun  6 08:19:20.213: INFO: Creating resource for dynamic PV
Jun  6 08:19:20.213: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4164-e2e-sc6sgkv
STEP: creating a claim
Jun  6 08:19:20.379: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-4164
Jun  6 08:19:20.878: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-4164" in namespace "provisioning-4164" to be "Succeeded or Failed"
Jun  6 08:19:21.067: INFO: Pod "volume-prep-provisioning-4164": Phase="Pending", Reason="", readiness=false. Elapsed: 188.901613ms
Jun  6 08:19:23.233: INFO: Pod "volume-prep-provisioning-4164": Phase="Pending", Reason="", readiness=false. Elapsed: 2.355013823s
Jun  6 08:19:25.399: INFO: Pod "volume-prep-provisioning-4164": Phase="Pending", Reason="", readiness=false. Elapsed: 4.521054268s
Jun  6 08:19:27.566: INFO: Pod "volume-prep-provisioning-4164": Phase="Pending", Reason="", readiness=false. Elapsed: 6.687477448s
Jun  6 08:19:29.731: INFO: Pod "volume-prep-provisioning-4164": Phase="Pending", Reason="", readiness=false. Elapsed: 8.852497617s
Jun  6 08:19:31.900: INFO: Pod "volume-prep-provisioning-4164": Phase="Pending", Reason="", readiness=false. Elapsed: 11.022085296s
Jun  6 08:19:34.065: INFO: Pod "volume-prep-provisioning-4164": Phase="Pending", Reason="", readiness=false. Elapsed: 13.186949619s
Jun  6 08:19:36.233: INFO: Pod "volume-prep-provisioning-4164": Phase="Succeeded", Reason="", readiness=false. Elapsed: 15.35512839s
STEP: Saw pod success
Jun  6 08:19:36.233: INFO: Pod "volume-prep-provisioning-4164" satisfied condition "Succeeded or Failed"
Jun  6 08:19:36.233: INFO: Deleting pod "volume-prep-provisioning-4164" in namespace "provisioning-4164"
Jun  6 08:19:36.404: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-4164" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-ft7g
STEP: Checking for subpath error in container status
Jun  6 08:20:01.062: INFO: Deleting pod "pod-subpath-test-dynamicpv-ft7g" in namespace "provisioning-4164"
Jun  6 08:20:01.233: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-ft7g" to be fully deleted
STEP: Deleting pod
Jun  6 08:20:01.396: INFO: Deleting pod "pod-subpath-test-dynamicpv-ft7g" in namespace "provisioning-4164"
STEP: Deleting pvc
Jun  6 08:20:01.891: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comvrzx2"
... skipping 36 lines ...
Jun  6 08:19:59.502: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2225dvplf
STEP: creating a claim
Jun  6 08:19:59.665: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-r4hz
STEP: Creating a pod to test subpath
Jun  6 08:20:00.153: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-r4hz" in namespace "provisioning-2225" to be "Succeeded or Failed"
Jun  6 08:20:00.315: INFO: Pod "pod-subpath-test-dynamicpv-r4hz": Phase="Pending", Reason="", readiness=false. Elapsed: 161.598993ms
Jun  6 08:20:02.477: INFO: Pod "pod-subpath-test-dynamicpv-r4hz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.323422276s
Jun  6 08:20:04.639: INFO: Pod "pod-subpath-test-dynamicpv-r4hz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.485633513s
Jun  6 08:20:06.801: INFO: Pod "pod-subpath-test-dynamicpv-r4hz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.647638893s
Jun  6 08:20:08.963: INFO: Pod "pod-subpath-test-dynamicpv-r4hz": Phase="Pending", Reason="", readiness=false. Elapsed: 8.8098774s
Jun  6 08:20:11.127: INFO: Pod "pod-subpath-test-dynamicpv-r4hz": Phase="Pending", Reason="", readiness=false. Elapsed: 10.973323545s
Jun  6 08:20:13.289: INFO: Pod "pod-subpath-test-dynamicpv-r4hz": Phase="Pending", Reason="", readiness=false. Elapsed: 13.136217636s
Jun  6 08:20:15.453: INFO: Pod "pod-subpath-test-dynamicpv-r4hz": Phase="Pending", Reason="", readiness=false. Elapsed: 15.299332487s
Jun  6 08:20:17.620: INFO: Pod "pod-subpath-test-dynamicpv-r4hz": Phase="Pending", Reason="", readiness=false. Elapsed: 17.466432824s
Jun  6 08:20:19.783: INFO: Pod "pod-subpath-test-dynamicpv-r4hz": Phase="Pending", Reason="", readiness=false. Elapsed: 19.63013565s
Jun  6 08:20:21.946: INFO: Pod "pod-subpath-test-dynamicpv-r4hz": Phase="Pending", Reason="", readiness=false. Elapsed: 21.792402213s
Jun  6 08:20:24.107: INFO: Pod "pod-subpath-test-dynamicpv-r4hz": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.954154569s
STEP: Saw pod success
Jun  6 08:20:24.107: INFO: Pod "pod-subpath-test-dynamicpv-r4hz" satisfied condition "Succeeded or Failed"
Jun  6 08:20:24.269: INFO: Trying to get logs from node ip-172-20-53-171.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-r4hz container test-container-volume-dynamicpv-r4hz: <nil>
STEP: delete the pod
Jun  6 08:20:24.600: INFO: Waiting for pod pod-subpath-test-dynamicpv-r4hz to disappear
Jun  6 08:20:24.762: INFO: Pod pod-subpath-test-dynamicpv-r4hz no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-r4hz
Jun  6 08:20:24.762: INFO: Deleting pod "pod-subpath-test-dynamicpv-r4hz" in namespace "provisioning-2225"
... skipping 40 lines ...
Jun  6 08:19:18.533: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-4-e2e-sc7xslr      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-4    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-4-e2e-sc7xslr,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-4    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-4-e2e-sc7xslr,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-4    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-4-e2e-sc7xslr,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-4-e2e-sc7xslr    11ab7594-055a-4ad2-8806-0860a8ddc9fc 2658 0 2021-06-06 08:19:18 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-06 08:19:18 +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-j9l6w pvc- provisioning-4  da41a514-7b11-4a0a-bf60-13749d6aef1e 2680 0 2021-06-06 08:19:19 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-06 08:19:19 +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-4-e2e-sc7xslr,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-8bafae3e-b9d6-4603-8d90-4aa4ce74c5cf in namespace provisioning-4
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun  6 08:19:38.271: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-4qgbb" in namespace "provisioning-4" to be "Succeeded or Failed"
Jun  6 08:19:38.427: INFO: Pod "pvc-volume-tester-writer-4qgbb": Phase="Pending", Reason="", readiness=false. Elapsed: 156.273835ms
Jun  6 08:19:40.584: INFO: Pod "pvc-volume-tester-writer-4qgbb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.313470435s
Jun  6 08:19:42.741: INFO: Pod "pvc-volume-tester-writer-4qgbb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.470543853s
Jun  6 08:19:44.898: INFO: Pod "pvc-volume-tester-writer-4qgbb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.626910422s
Jun  6 08:19:47.057: INFO: Pod "pvc-volume-tester-writer-4qgbb": Phase="Pending", Reason="", readiness=false. Elapsed: 8.785793307s
Jun  6 08:19:49.214: INFO: Pod "pvc-volume-tester-writer-4qgbb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.942844197s
STEP: Saw pod success
Jun  6 08:19:49.214: INFO: Pod "pvc-volume-tester-writer-4qgbb" satisfied condition "Succeeded or Failed"
Jun  6 08:19:49.533: INFO: Pod pvc-volume-tester-writer-4qgbb has the following logs: 
Jun  6 08:19:49.533: INFO: Deleting pod "pvc-volume-tester-writer-4qgbb" in namespace "provisioning-4"
Jun  6 08:19:49.695: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-4qgbb" to be fully deleted
STEP: checking the created volume has the correct mount options, is readable and retains data on the same node "ip-172-20-33-48.ap-northeast-2.compute.internal"
Jun  6 08:19:50.329: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-vkz5f" in namespace "provisioning-4" to be "Succeeded or Failed"
Jun  6 08:19:50.485: INFO: Pod "pvc-volume-tester-reader-vkz5f": Phase="Pending", Reason="", readiness=false. Elapsed: 156.534798ms
Jun  6 08:19:52.642: INFO: Pod "pvc-volume-tester-reader-vkz5f": Phase="Pending", Reason="", readiness=false. Elapsed: 2.313480169s
Jun  6 08:19:54.799: INFO: Pod "pvc-volume-tester-reader-vkz5f": Phase="Pending", Reason="", readiness=false. Elapsed: 4.470501509s
Jun  6 08:19:56.956: INFO: Pod "pvc-volume-tester-reader-vkz5f": Phase="Pending", Reason="", readiness=false. Elapsed: 6.627531434s
Jun  6 08:19:59.117: INFO: Pod "pvc-volume-tester-reader-vkz5f": Phase="Pending", Reason="", readiness=false. Elapsed: 8.788080518s
Jun  6 08:20:01.276: INFO: Pod "pvc-volume-tester-reader-vkz5f": Phase="Pending", Reason="", readiness=false. Elapsed: 10.947550525s
Jun  6 08:20:03.434: INFO: Pod "pvc-volume-tester-reader-vkz5f": Phase="Pending", Reason="", readiness=false. Elapsed: 13.105116922s
Jun  6 08:20:05.591: INFO: Pod "pvc-volume-tester-reader-vkz5f": Phase="Succeeded", Reason="", readiness=false. Elapsed: 15.262327085s
STEP: Saw pod success
Jun  6 08:20:05.591: INFO: Pod "pvc-volume-tester-reader-vkz5f" satisfied condition "Succeeded or Failed"
Jun  6 08:20:05.908: INFO: Pod pvc-volume-tester-reader-vkz5f has the following logs: hello world

Jun  6 08:20:05.908: INFO: Deleting pod "pvc-volume-tester-reader-vkz5f" in namespace "provisioning-4"
Jun  6 08:20:06.074: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-vkz5f" to be fully deleted
Jun  6 08:20:06.230: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-j9l6w] to have phase Bound
Jun  6 08:20:06.388: INFO: PersistentVolumeClaim pvc-j9l6w found and phase=Bound (157.851638ms)
... skipping 35 lines ...

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

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

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

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

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

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

    /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 375 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  6 08:20:21.119: 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.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  6 08:20:21.918: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  6 08:20:21.918: INFO: Creating resource for dynamic PV
Jun  6 08:20:21.918: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-634926rjk
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  6 08:20:29.043: INFO: Deleting pod "pod-5dcafc2e-3946-40c9-921c-4c3d40f85538" in namespace "volumemode-6349"
Jun  6 08:20:29.206: INFO: Wait up to 5m0s for pod "pod-5dcafc2e-3946-40c9-921c-4c3d40f85538" to be fully deleted
STEP: Deleting pvc
Jun  6 08:20:39.842: INFO: Deleting PersistentVolumeClaim "awscqxmc"
Jun  6 08:20:40.002: INFO: Waiting up to 5m0s for PersistentVolume pvc-7e379102-1134-4644-9719-0e6f8222382a to get deleted
Jun  6 08:20:40.161: INFO: PersistentVolume pvc-7e379102-1134-4644-9719-0e6f8222382a found and phase=Released (158.64529ms)
... skipping 10 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Q9ZXkT72D/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Q9ZXkT72D/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (block volmode)] volumeMode
    /tmp/kops.Q9ZXkT72D/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.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] provisioning
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] provisioning
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 631 lines ...
Jun  6 08:20:56.326: INFO: Pod aws-client still exists
Jun  6 08:20:58.164: INFO: Waiting for pod aws-client to disappear
Jun  6 08:20:58.326: INFO: Pod aws-client still exists
Jun  6 08:21:00.164: INFO: Waiting for pod aws-client to disappear
Jun  6 08:21:00.326: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun  6 08:21:01.079: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-05dfc4d589989096a", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05dfc4d589989096a is currently attached to i-0a4f9cf0993c78da0
	status code: 400, request id: 284b6530-2ba0-43c8-a21c-d65e87ce40f5
Jun  6 08:21:06.868: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-05dfc4d589989096a".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  6 08:21:06.868: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-190" for this suite.
... skipping 138 lines ...
Jun  6 08:20:51.187: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  6 08:20:52.166: INFO: Successfully created a new PD: "aws://ap-northeast-2a/vol-0811898377ac0f848".
Jun  6 08:20:52.166: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-fcxm
STEP: Creating a pod to test exec-volume-test
Jun  6 08:20:52.327: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-fcxm" in namespace "volume-5706" to be "Succeeded or Failed"
Jun  6 08:20:52.489: INFO: Pod "exec-volume-test-inlinevolume-fcxm": Phase="Pending", Reason="", readiness=false. Elapsed: 161.712055ms
Jun  6 08:20:54.648: INFO: Pod "exec-volume-test-inlinevolume-fcxm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.320695046s
Jun  6 08:20:56.808: INFO: Pod "exec-volume-test-inlinevolume-fcxm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.480424412s
Jun  6 08:20:58.968: INFO: Pod "exec-volume-test-inlinevolume-fcxm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.640364839s
Jun  6 08:21:01.127: INFO: Pod "exec-volume-test-inlinevolume-fcxm": Phase="Pending", Reason="", readiness=false. Elapsed: 8.799749564s
Jun  6 08:21:03.290: INFO: Pod "exec-volume-test-inlinevolume-fcxm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.962822428s
STEP: Saw pod success
Jun  6 08:21:03.290: INFO: Pod "exec-volume-test-inlinevolume-fcxm" satisfied condition "Succeeded or Failed"
Jun  6 08:21:03.449: INFO: Trying to get logs from node ip-172-20-53-171.ap-northeast-2.compute.internal pod exec-volume-test-inlinevolume-fcxm container exec-container-inlinevolume-fcxm: <nil>
STEP: delete the pod
Jun  6 08:21:03.780: INFO: Waiting for pod exec-volume-test-inlinevolume-fcxm to disappear
Jun  6 08:21:03.941: INFO: Pod exec-volume-test-inlinevolume-fcxm no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-fcxm
Jun  6 08:21:03.941: INFO: Deleting pod "exec-volume-test-inlinevolume-fcxm" in namespace "volume-5706"
Jun  6 08:21:04.379: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0811898377ac0f848", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0811898377ac0f848 is currently attached to i-037bcb7083139f8fd
	status code: 400, request id: d2cb4982-a880-42c6-9642-222c7621178e
Jun  6 08:21:10.129: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0811898377ac0f848", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0811898377ac0f848 is currently attached to i-037bcb7083139f8fd
	status code: 400, request id: 9878f6c3-0a56-4a87-bd86-5f3aa3d3f603
Jun  6 08:21:15.900: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0811898377ac0f848", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0811898377ac0f848 is currently attached to i-037bcb7083139f8fd
	status code: 400, request id: f06729bb-c53c-4a2e-99fe-ab06dd2aed96
Jun  6 08:21:21.685: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-0811898377ac0f848".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  6 08:21:21.685: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-5706" for this suite.
... skipping 570 lines ...

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

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

    /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:92
------------------------------
... skipping 2 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  6 08:20:48.379: 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.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun  6 08:20:49.180: INFO: Creating resource for dynamic PV
Jun  6 08:20:49.180: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2868-e2e-scvp4kz
STEP: creating a claim
Jun  6 08:20:49.340: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-4xq9
STEP: Checking for subpath error in container status
Jun  6 08:21:06.130: INFO: Deleting pod "pod-subpath-test-dynamicpv-4xq9" in namespace "provisioning-2868"
Jun  6 08:21:06.288: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-4xq9" to be fully deleted
STEP: Deleting pod
Jun  6 08:21:16.602: INFO: Deleting pod "pod-subpath-test-dynamicpv-4xq9" in namespace "provisioning-2868"
STEP: Deleting pvc
Jun  6 08:21:17.081: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com485q5"
... skipping 11 lines ...

• [SLOW TEST:44.972 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath directory is outside the volume [Slow][LinuxOnly]
    /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  6 08:21:33.353: INFO: Distro debian doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
... skipping 346 lines ...
Jun  6 08:20:47.716: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-6028pgbpw
STEP: creating a claim
Jun  6 08:20:47.881: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-vxdc
STEP: Creating a pod to test exec-volume-test
Jun  6 08:20:48.385: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-vxdc" in namespace "volume-6028" to be "Succeeded or Failed"
Jun  6 08:20:48.557: INFO: Pod "exec-volume-test-dynamicpv-vxdc": Phase="Pending", Reason="", readiness=false. Elapsed: 172.375977ms
Jun  6 08:20:50.722: INFO: Pod "exec-volume-test-dynamicpv-vxdc": Phase="Pending", Reason="", readiness=false. Elapsed: 2.337162047s
Jun  6 08:20:52.888: INFO: Pod "exec-volume-test-dynamicpv-vxdc": Phase="Pending", Reason="", readiness=false. Elapsed: 4.502867911s
Jun  6 08:20:55.052: INFO: Pod "exec-volume-test-dynamicpv-vxdc": Phase="Pending", Reason="", readiness=false. Elapsed: 6.667451506s
Jun  6 08:20:57.219: INFO: Pod "exec-volume-test-dynamicpv-vxdc": Phase="Pending", Reason="", readiness=false. Elapsed: 8.833926965s
Jun  6 08:20:59.384: INFO: Pod "exec-volume-test-dynamicpv-vxdc": Phase="Pending", Reason="", readiness=false. Elapsed: 10.999189299s
... skipping 3 lines ...
Jun  6 08:21:08.057: INFO: Pod "exec-volume-test-dynamicpv-vxdc": Phase="Pending", Reason="", readiness=false. Elapsed: 19.672209958s
Jun  6 08:21:10.221: INFO: Pod "exec-volume-test-dynamicpv-vxdc": Phase="Pending", Reason="", readiness=false. Elapsed: 21.836464917s
Jun  6 08:21:12.387: INFO: Pod "exec-volume-test-dynamicpv-vxdc": Phase="Pending", Reason="", readiness=false. Elapsed: 24.002007345s
Jun  6 08:21:14.553: INFO: Pod "exec-volume-test-dynamicpv-vxdc": Phase="Pending", Reason="", readiness=false. Elapsed: 26.167542703s
Jun  6 08:21:16.720: INFO: Pod "exec-volume-test-dynamicpv-vxdc": Phase="Succeeded", Reason="", readiness=false. Elapsed: 28.334964268s
STEP: Saw pod success
Jun  6 08:21:16.720: INFO: Pod "exec-volume-test-dynamicpv-vxdc" satisfied condition "Succeeded or Failed"
Jun  6 08:21:16.886: INFO: Trying to get logs from node ip-172-20-33-48.ap-northeast-2.compute.internal pod exec-volume-test-dynamicpv-vxdc container exec-container-dynamicpv-vxdc: <nil>
STEP: delete the pod
Jun  6 08:21:17.227: INFO: Waiting for pod exec-volume-test-dynamicpv-vxdc to disappear
Jun  6 08:21:17.392: INFO: Pod exec-volume-test-dynamicpv-vxdc no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-vxdc
Jun  6 08:21:17.392: INFO: Deleting pod "exec-volume-test-dynamicpv-vxdc" in namespace "volume-6028"
... skipping 361 lines ...
Jun  6 08:21:25.856: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  6 08:21:26.822: INFO: Successfully created a new PD: "aws://ap-northeast-2a/vol-00ac774a8afbd72d7".
Jun  6 08:21:26.822: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-wk48
STEP: Creating a pod to test exec-volume-test
Jun  6 08:21:26.980: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-wk48" in namespace "volume-9508" to be "Succeeded or Failed"
Jun  6 08:21:27.137: INFO: Pod "exec-volume-test-inlinevolume-wk48": Phase="Pending", Reason="", readiness=false. Elapsed: 157.16593ms
Jun  6 08:21:29.295: INFO: Pod "exec-volume-test-inlinevolume-wk48": Phase="Pending", Reason="", readiness=false. Elapsed: 2.314534755s
Jun  6 08:21:31.451: INFO: Pod "exec-volume-test-inlinevolume-wk48": Phase="Pending", Reason="", readiness=false. Elapsed: 4.471450669s
Jun  6 08:21:33.608: INFO: Pod "exec-volume-test-inlinevolume-wk48": Phase="Pending", Reason="", readiness=false. Elapsed: 6.627916754s
Jun  6 08:21:35.765: INFO: Pod "exec-volume-test-inlinevolume-wk48": Phase="Pending", Reason="", readiness=false. Elapsed: 8.785083061s
Jun  6 08:21:37.922: INFO: Pod "exec-volume-test-inlinevolume-wk48": Phase="Pending", Reason="", readiness=false. Elapsed: 10.941562796s
Jun  6 08:21:40.079: INFO: Pod "exec-volume-test-inlinevolume-wk48": Phase="Pending", Reason="", readiness=false. Elapsed: 13.099418541s
Jun  6 08:21:42.236: INFO: Pod "exec-volume-test-inlinevolume-wk48": Phase="Pending", Reason="", readiness=false. Elapsed: 15.255893419s
Jun  6 08:21:44.392: INFO: Pod "exec-volume-test-inlinevolume-wk48": Phase="Pending", Reason="", readiness=false. Elapsed: 17.412307036s
Jun  6 08:21:46.549: INFO: Pod "exec-volume-test-inlinevolume-wk48": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.568865036s
STEP: Saw pod success
Jun  6 08:21:46.549: INFO: Pod "exec-volume-test-inlinevolume-wk48" satisfied condition "Succeeded or Failed"
Jun  6 08:21:46.708: INFO: Trying to get logs from node ip-172-20-40-222.ap-northeast-2.compute.internal pod exec-volume-test-inlinevolume-wk48 container exec-container-inlinevolume-wk48: <nil>
STEP: delete the pod
Jun  6 08:21:47.030: INFO: Waiting for pod exec-volume-test-inlinevolume-wk48 to disappear
Jun  6 08:21:47.200: INFO: Pod exec-volume-test-inlinevolume-wk48 no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-wk48
Jun  6 08:21:47.200: INFO: Deleting pod "exec-volume-test-inlinevolume-wk48" in namespace "volume-9508"
Jun  6 08:21:47.659: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-00ac774a8afbd72d7", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00ac774a8afbd72d7 is currently attached to i-0d09dc59d79b0c8d5
	status code: 400, request id: bcffcfbb-b80e-4614-83d4-5a13e1958044
Jun  6 08:21:53.421: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-00ac774a8afbd72d7", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00ac774a8afbd72d7 is currently attached to i-0d09dc59d79b0c8d5
	status code: 400, request id: 3dac830d-913d-41da-9c96-895a271f129b
Jun  6 08:21:59.204: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-00ac774a8afbd72d7".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  6 08:21:59.204: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-9508" for this suite.
... skipping 162 lines ...

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

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 35 lines ...
Jun  6 08:21:34.139: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-13146672g
STEP: creating a claim
Jun  6 08:21:34.300: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-glrm
STEP: Creating a pod to test exec-volume-test
Jun  6 08:21:34.773: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-glrm" in namespace "volume-1314" to be "Succeeded or Failed"
Jun  6 08:21:34.933: INFO: Pod "exec-volume-test-dynamicpv-glrm": Phase="Pending", Reason="", readiness=false. Elapsed: 160.067951ms
Jun  6 08:21:37.097: INFO: Pod "exec-volume-test-dynamicpv-glrm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.323332725s
Jun  6 08:21:39.254: INFO: Pod "exec-volume-test-dynamicpv-glrm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.480804085s
Jun  6 08:21:41.411: INFO: Pod "exec-volume-test-dynamicpv-glrm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.637921043s
Jun  6 08:21:43.571: INFO: Pod "exec-volume-test-dynamicpv-glrm": Phase="Pending", Reason="", readiness=false. Elapsed: 8.797563976s
Jun  6 08:21:45.729: INFO: Pod "exec-volume-test-dynamicpv-glrm": Phase="Pending", Reason="", readiness=false. Elapsed: 10.955660099s
... skipping 2 lines ...
Jun  6 08:21:52.201: INFO: Pod "exec-volume-test-dynamicpv-glrm": Phase="Pending", Reason="", readiness=false. Elapsed: 17.427271314s
Jun  6 08:21:54.358: INFO: Pod "exec-volume-test-dynamicpv-glrm": Phase="Pending", Reason="", readiness=false. Elapsed: 19.585201393s
Jun  6 08:21:56.515: INFO: Pod "exec-volume-test-dynamicpv-glrm": Phase="Pending", Reason="", readiness=false. Elapsed: 21.741967779s
Jun  6 08:21:58.672: INFO: Pod "exec-volume-test-dynamicpv-glrm": Phase="Pending", Reason="", readiness=false. Elapsed: 23.898620616s
Jun  6 08:22:00.829: INFO: Pod "exec-volume-test-dynamicpv-glrm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.055917675s
STEP: Saw pod success
Jun  6 08:22:00.829: INFO: Pod "exec-volume-test-dynamicpv-glrm" satisfied condition "Succeeded or Failed"
Jun  6 08:22:00.989: INFO: Trying to get logs from node ip-172-20-47-232.ap-northeast-2.compute.internal pod exec-volume-test-dynamicpv-glrm container exec-container-dynamicpv-glrm: <nil>
STEP: delete the pod
Jun  6 08:22:01.324: INFO: Waiting for pod exec-volume-test-dynamicpv-glrm to disappear
Jun  6 08:22:01.480: INFO: Pod exec-volume-test-dynamicpv-glrm no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-glrm
Jun  6 08:22:01.480: INFO: Deleting pod "exec-volume-test-dynamicpv-glrm" in namespace "volume-1314"
... skipping 35 lines ...
Jun  6 08:21:09.316: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9634dpp28
STEP: creating a claim
Jun  6 08:21:09.479: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-kdjj
STEP: Creating a pod to test subpath
Jun  6 08:21:09.967: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-kdjj" in namespace "provisioning-9634" to be "Succeeded or Failed"
Jun  6 08:21:10.129: INFO: Pod "pod-subpath-test-dynamicpv-kdjj": Phase="Pending", Reason="", readiness=false. Elapsed: 161.752416ms
Jun  6 08:21:12.292: INFO: Pod "pod-subpath-test-dynamicpv-kdjj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.32465007s
Jun  6 08:21:14.456: INFO: Pod "pod-subpath-test-dynamicpv-kdjj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.488460786s
Jun  6 08:21:16.620: INFO: Pod "pod-subpath-test-dynamicpv-kdjj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.652377744s
Jun  6 08:21:18.783: INFO: Pod "pod-subpath-test-dynamicpv-kdjj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.815277202s
Jun  6 08:21:20.947: INFO: Pod "pod-subpath-test-dynamicpv-kdjj": Phase="Pending", Reason="", readiness=false. Elapsed: 10.979758647s
... skipping 5 lines ...
Jun  6 08:21:33.933: INFO: Pod "pod-subpath-test-dynamicpv-kdjj": Phase="Pending", Reason="", readiness=false. Elapsed: 23.965495532s
Jun  6 08:21:36.096: INFO: Pod "pod-subpath-test-dynamicpv-kdjj": Phase="Pending", Reason="", readiness=false. Elapsed: 26.128164043s
Jun  6 08:21:38.259: INFO: Pod "pod-subpath-test-dynamicpv-kdjj": Phase="Pending", Reason="", readiness=false. Elapsed: 28.29160424s
Jun  6 08:21:40.422: INFO: Pod "pod-subpath-test-dynamicpv-kdjj": Phase="Pending", Reason="", readiness=false. Elapsed: 30.454374235s
Jun  6 08:21:42.585: INFO: Pod "pod-subpath-test-dynamicpv-kdjj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 32.617497174s
STEP: Saw pod success
Jun  6 08:21:42.585: INFO: Pod "pod-subpath-test-dynamicpv-kdjj" satisfied condition "Succeeded or Failed"
Jun  6 08:21:42.747: INFO: Trying to get logs from node ip-172-20-33-48.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-kdjj container test-container-subpath-dynamicpv-kdjj: <nil>
STEP: delete the pod
Jun  6 08:21:43.080: INFO: Waiting for pod pod-subpath-test-dynamicpv-kdjj to disappear
Jun  6 08:21:43.242: INFO: Pod pod-subpath-test-dynamicpv-kdjj no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-kdjj
Jun  6 08:21:43.242: INFO: Deleting pod "pod-subpath-test-dynamicpv-kdjj" in namespace "provisioning-9634"
... skipping 58 lines ...
Jun  6 08:19:21.150: INFO: Creating resource for dynamic PV
Jun  6 08:19:21.150: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-8687-e2e-scmvld6
STEP: creating a claim
Jun  6 08:19:21.314: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun  6 08:19:21.801: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-f2cr6" in namespace "snapshotting-8687" to be "Succeeded or Failed"
Jun  6 08:19:21.961: INFO: Pod "pvc-snapshottable-tester-f2cr6": Phase="Pending", Reason="", readiness=false. Elapsed: 160.43964ms
Jun  6 08:19:24.122: INFO: Pod "pvc-snapshottable-tester-f2cr6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.321265017s
Jun  6 08:19:26.282: INFO: Pod "pvc-snapshottable-tester-f2cr6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.481789006s
Jun  6 08:19:28.449: INFO: Pod "pvc-snapshottable-tester-f2cr6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.64786799s
Jun  6 08:19:30.611: INFO: Pod "pvc-snapshottable-tester-f2cr6": Phase="Pending", Reason="", readiness=false. Elapsed: 8.810654937s
Jun  6 08:19:32.772: INFO: Pod "pvc-snapshottable-tester-f2cr6": Phase="Pending", Reason="", readiness=false. Elapsed: 10.97131205s
Jun  6 08:19:34.933: INFO: Pod "pvc-snapshottable-tester-f2cr6": Phase="Pending", Reason="", readiness=false. Elapsed: 13.132381594s
Jun  6 08:19:37.098: INFO: Pod "pvc-snapshottable-tester-f2cr6": Phase="Pending", Reason="", readiness=false. Elapsed: 15.297418635s
Jun  6 08:19:39.265: INFO: Pod "pvc-snapshottable-tester-f2cr6": Phase="Pending", Reason="", readiness=false. Elapsed: 17.464215731s
Jun  6 08:19:41.427: INFO: Pod "pvc-snapshottable-tester-f2cr6": Phase="Pending", Reason="", readiness=false. Elapsed: 19.626043856s
Jun  6 08:19:43.588: INFO: Pod "pvc-snapshottable-tester-f2cr6": Phase="Pending", Reason="", readiness=false. Elapsed: 21.786888481s
Jun  6 08:19:45.750: INFO: Pod "pvc-snapshottable-tester-f2cr6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.949635845s
STEP: Saw pod success
Jun  6 08:19:45.750: INFO: Pod "pvc-snapshottable-tester-f2cr6" satisfied condition "Succeeded or Failed"
Jun  6 08:19:46.858: INFO: Pod pvc-snapshottable-tester-f2cr6 has the following logs: 
Jun  6 08:19:46.858: INFO: Deleting pod "pvc-snapshottable-tester-f2cr6" in namespace "snapshotting-8687"
Jun  6 08:19:47.026: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-f2cr6" to be fully deleted
Jun  6 08:19:47.193: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.com7rwhx] to have phase Bound
Jun  6 08:19:47.354: INFO: PersistentVolumeClaim ebs.csi.aws.com7rwhx found and phase=Bound (160.319763ms)
STEP: [init] checking the claim
... skipping 30 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.Q9ZXkT72D/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 08:20:32.434: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-k94x2" in namespace "snapshotting-8687" to be "Succeeded or Failed"
Jun  6 08:20:32.595: INFO: Pod "pvc-snapshottable-data-tester-k94x2": Phase="Pending", Reason="", readiness=false. Elapsed: 161.005451ms
Jun  6 08:20:34.756: INFO: Pod "pvc-snapshottable-data-tester-k94x2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.322401278s
Jun  6 08:20:36.917: INFO: Pod "pvc-snapshottable-data-tester-k94x2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.483369984s
Jun  6 08:20:39.078: INFO: Pod "pvc-snapshottable-data-tester-k94x2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.643886561s
Jun  6 08:20:41.240: INFO: Pod "pvc-snapshottable-data-tester-k94x2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.806202528s
Jun  6 08:20:43.402: INFO: Pod "pvc-snapshottable-data-tester-k94x2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.968278753s
... skipping 6 lines ...
Jun  6 08:20:58.543: INFO: Pod "pvc-snapshottable-data-tester-k94x2": Phase="Pending", Reason="", readiness=false. Elapsed: 26.109215808s
Jun  6 08:21:00.704: INFO: Pod "pvc-snapshottable-data-tester-k94x2": Phase="Pending", Reason="", readiness=false. Elapsed: 28.270190675s
Jun  6 08:21:02.865: INFO: Pod "pvc-snapshottable-data-tester-k94x2": Phase="Pending", Reason="", readiness=false. Elapsed: 30.431523753s
Jun  6 08:21:05.027: INFO: Pod "pvc-snapshottable-data-tester-k94x2": Phase="Pending", Reason="", readiness=false. Elapsed: 32.592859771s
Jun  6 08:21:07.190: INFO: Pod "pvc-snapshottable-data-tester-k94x2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.756633212s
STEP: Saw pod success
Jun  6 08:21:07.190: INFO: Pod "pvc-snapshottable-data-tester-k94x2" satisfied condition "Succeeded or Failed"
Jun  6 08:21:07.514: INFO: Pod pvc-snapshottable-data-tester-k94x2 has the following logs: 
Jun  6 08:21:07.514: INFO: Deleting pod "pvc-snapshottable-data-tester-k94x2" in namespace "snapshotting-8687"
Jun  6 08:21:07.689: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-k94x2" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun  6 08:21:30.502: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-8687 exec restored-pvc-tester-l65ln --namespace=snapshotting-8687 -- cat /mnt/test/data'
... skipping 342 lines ...
Jun  6 08:22:19.164: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

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

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 68 lines ...
Jun  6 08:21:51.228: INFO: PersistentVolumeClaim pvc-sf58m found but phase is Pending instead of Bound.
Jun  6 08:21:53.394: INFO: PersistentVolumeClaim pvc-sf58m found and phase=Bound (6.660255964s)
Jun  6 08:21:53.394: INFO: Waiting up to 3m0s for PersistentVolume aws-kktzj to have phase Bound
Jun  6 08:21:53.558: INFO: PersistentVolume aws-kktzj found and phase=Bound (164.223861ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-kjtc
STEP: Creating a pod to test exec-volume-test
Jun  6 08:21:54.055: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-kjtc" in namespace "volume-6422" to be "Succeeded or Failed"
Jun  6 08:21:54.220: INFO: Pod "exec-volume-test-preprovisionedpv-kjtc": Phase="Pending", Reason="", readiness=false. Elapsed: 164.349803ms
Jun  6 08:21:56.386: INFO: Pod "exec-volume-test-preprovisionedpv-kjtc": Phase="Pending", Reason="", readiness=false. Elapsed: 2.330525557s
Jun  6 08:21:58.551: INFO: Pod "exec-volume-test-preprovisionedpv-kjtc": Phase="Pending", Reason="", readiness=false. Elapsed: 4.49547707s
Jun  6 08:22:00.716: INFO: Pod "exec-volume-test-preprovisionedpv-kjtc": Phase="Pending", Reason="", readiness=false. Elapsed: 6.660690942s
Jun  6 08:22:02.881: INFO: Pod "exec-volume-test-preprovisionedpv-kjtc": Phase="Pending", Reason="", readiness=false. Elapsed: 8.825179717s
Jun  6 08:22:05.046: INFO: Pod "exec-volume-test-preprovisionedpv-kjtc": Phase="Pending", Reason="", readiness=false. Elapsed: 10.990639935s
Jun  6 08:22:07.212: INFO: Pod "exec-volume-test-preprovisionedpv-kjtc": Phase="Pending", Reason="", readiness=false. Elapsed: 13.156789266s
Jun  6 08:22:09.378: INFO: Pod "exec-volume-test-preprovisionedpv-kjtc": Phase="Pending", Reason="", readiness=false. Elapsed: 15.322566701s
Jun  6 08:22:11.546: INFO: Pod "exec-volume-test-preprovisionedpv-kjtc": Phase="Pending", Reason="", readiness=false. Elapsed: 17.491121004s
Jun  6 08:22:13.712: INFO: Pod "exec-volume-test-preprovisionedpv-kjtc": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.656252503s
STEP: Saw pod success
Jun  6 08:22:13.712: INFO: Pod "exec-volume-test-preprovisionedpv-kjtc" satisfied condition "Succeeded or Failed"
Jun  6 08:22:13.876: INFO: Trying to get logs from node ip-172-20-47-232.ap-northeast-2.compute.internal pod exec-volume-test-preprovisionedpv-kjtc container exec-container-preprovisionedpv-kjtc: <nil>
STEP: delete the pod
Jun  6 08:22:14.215: INFO: Waiting for pod exec-volume-test-preprovisionedpv-kjtc to disappear
Jun  6 08:22:14.379: INFO: Pod exec-volume-test-preprovisionedpv-kjtc no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-kjtc
Jun  6 08:22:14.379: INFO: Deleting pod "exec-volume-test-preprovisionedpv-kjtc" in namespace "volume-6422"
STEP: Deleting pv and pvc
Jun  6 08:22:14.543: INFO: Deleting PersistentVolumeClaim "pvc-sf58m"
Jun  6 08:22:14.711: INFO: Deleting PersistentVolume "aws-kktzj"
Jun  6 08:22:15.188: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-074ce3de20d602c81", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-074ce3de20d602c81 is currently attached to i-06d23c6e41a438965
	status code: 400, request id: 46359ddc-2ff4-4921-b7e4-27856abf6fe1
Jun  6 08:22:20.952: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-074ce3de20d602c81", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-074ce3de20d602c81 is currently attached to i-06d23c6e41a438965
	status code: 400, request id: 7b73727a-1b7e-48c7-91d5-f265bc7a7767
Jun  6 08:22:26.716: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-074ce3de20d602c81", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-074ce3de20d602c81 is currently attached to i-06d23c6e41a438965
	status code: 400, request id: 6a6c4711-9573-4ed8-a86f-cbe63d486dae
Jun  6 08:22:32.490: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-074ce3de20d602c81".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  6 08:22:32.490: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-6422" for this suite.
... skipping 138 lines ...

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

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

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

    /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 36 lines ...
STEP: Deleting pod hostexec-ip-172-20-33-48.ap-northeast-2.compute.internal-s2hzm in namespace volumemode-9892
Jun  6 08:22:16.813: INFO: Deleting pod "pod-5506c54d-8ea3-413e-851e-33a7725c8ed5" in namespace "volumemode-9892"
Jun  6 08:22:16.973: INFO: Wait up to 5m0s for pod "pod-5506c54d-8ea3-413e-851e-33a7725c8ed5" to be fully deleted
STEP: Deleting pv and pvc
Jun  6 08:22:23.294: INFO: Deleting PersistentVolumeClaim "pvc-9th6s"
Jun  6 08:22:23.460: INFO: Deleting PersistentVolume "aws-6ghhp"
Jun  6 08:22:23.889: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0dd8fd736c8c110ef", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0dd8fd736c8c110ef is currently attached to i-0a4f9cf0993c78da0
	status code: 400, request id: 45ebf354-671e-4736-8fee-71181549ac92
Jun  6 08:22:29.660: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0dd8fd736c8c110ef", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0dd8fd736c8c110ef is currently attached to i-0a4f9cf0993c78da0
	status code: 400, request id: e3bac316-e283-4d60-a64d-0c680e4ce247
Jun  6 08:22:35.426: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0dd8fd736c8c110ef", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0dd8fd736c8c110ef is currently attached to i-0a4f9cf0993c78da0
	status code: 400, request id: 62730be6-b25c-4703-8856-7980e9456399
Jun  6 08:22:41.227: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-0dd8fd736c8c110ef".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  6 08:22:41.228: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-9892" for this suite.
... skipping 73 lines ...
Jun  6 08:21:40.987: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3081-e2e-scxq9wc
STEP: creating a claim
Jun  6 08:21:41.149: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-t4kg
STEP: Creating a pod to test subpath
Jun  6 08:21:41.634: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-t4kg" in namespace "provisioning-3081" to be "Succeeded or Failed"
Jun  6 08:21:41.796: INFO: Pod "pod-subpath-test-dynamicpv-t4kg": Phase="Pending", Reason="", readiness=false. Elapsed: 162.318306ms
Jun  6 08:21:43.957: INFO: Pod "pod-subpath-test-dynamicpv-t4kg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.32280763s
Jun  6 08:21:46.188: INFO: Pod "pod-subpath-test-dynamicpv-t4kg": Phase="Pending", Reason="", readiness=false. Elapsed: 4.553973887s
Jun  6 08:21:48.349: INFO: Pod "pod-subpath-test-dynamicpv-t4kg": Phase="Pending", Reason="", readiness=false. Elapsed: 6.715148639s
Jun  6 08:21:50.511: INFO: Pod "pod-subpath-test-dynamicpv-t4kg": Phase="Pending", Reason="", readiness=false. Elapsed: 8.876407483s
Jun  6 08:21:52.672: INFO: Pod "pod-subpath-test-dynamicpv-t4kg": Phase="Pending", Reason="", readiness=false. Elapsed: 11.038085188s
Jun  6 08:21:54.833: INFO: Pod "pod-subpath-test-dynamicpv-t4kg": Phase="Pending", Reason="", readiness=false. Elapsed: 13.198755914s
Jun  6 08:21:56.995: INFO: Pod "pod-subpath-test-dynamicpv-t4kg": Phase="Pending", Reason="", readiness=false. Elapsed: 15.360345634s
Jun  6 08:21:59.156: INFO: Pod "pod-subpath-test-dynamicpv-t4kg": Phase="Pending", Reason="", readiness=false. Elapsed: 17.521938127s
Jun  6 08:22:01.320: INFO: Pod "pod-subpath-test-dynamicpv-t4kg": Phase="Pending", Reason="", readiness=false. Elapsed: 19.685401011s
Jun  6 08:22:03.481: INFO: Pod "pod-subpath-test-dynamicpv-t4kg": Phase="Pending", Reason="", readiness=false. Elapsed: 21.847065553s
Jun  6 08:22:05.645: INFO: Pod "pod-subpath-test-dynamicpv-t4kg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.011290274s
STEP: Saw pod success
Jun  6 08:22:05.646: INFO: Pod "pod-subpath-test-dynamicpv-t4kg" satisfied condition "Succeeded or Failed"
Jun  6 08:22:05.806: INFO: Trying to get logs from node ip-172-20-40-222.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-t4kg container test-container-volume-dynamicpv-t4kg: <nil>
STEP: delete the pod
Jun  6 08:22:06.159: INFO: Waiting for pod pod-subpath-test-dynamicpv-t4kg to disappear
Jun  6 08:22:06.318: INFO: Pod pod-subpath-test-dynamicpv-t4kg no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-t4kg
Jun  6 08:22:06.319: INFO: Deleting pod "pod-subpath-test-dynamicpv-t4kg" in namespace "provisioning-3081"
... skipping 150 lines ...
Jun  6 08:21:52.483: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2662-e2e-scwckr2
STEP: creating a claim
Jun  6 08:21:52.644: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-7gqk
STEP: Creating a pod to test subpath
Jun  6 08:21:53.129: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-7gqk" in namespace "provisioning-2662" to be "Succeeded or Failed"
Jun  6 08:21:53.289: INFO: Pod "pod-subpath-test-dynamicpv-7gqk": Phase="Pending", Reason="", readiness=false. Elapsed: 160.110979ms
Jun  6 08:21:55.451: INFO: Pod "pod-subpath-test-dynamicpv-7gqk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.32189899s
Jun  6 08:21:57.611: INFO: Pod "pod-subpath-test-dynamicpv-7gqk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.482782061s
Jun  6 08:21:59.773: INFO: Pod "pod-subpath-test-dynamicpv-7gqk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.644395737s
Jun  6 08:22:01.935: INFO: Pod "pod-subpath-test-dynamicpv-7gqk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.806080421s
Jun  6 08:22:04.095: INFO: Pod "pod-subpath-test-dynamicpv-7gqk": Phase="Pending", Reason="", readiness=false. Elapsed: 10.966521042s
Jun  6 08:22:06.256: INFO: Pod "pod-subpath-test-dynamicpv-7gqk": Phase="Pending", Reason="", readiness=false. Elapsed: 13.127168564s
Jun  6 08:22:08.416: INFO: Pod "pod-subpath-test-dynamicpv-7gqk": Phase="Pending", Reason="", readiness=false. Elapsed: 15.287384567s
Jun  6 08:22:10.577: INFO: Pod "pod-subpath-test-dynamicpv-7gqk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 17.448220587s
STEP: Saw pod success
Jun  6 08:22:10.577: INFO: Pod "pod-subpath-test-dynamicpv-7gqk" satisfied condition "Succeeded or Failed"
Jun  6 08:22:10.737: INFO: Trying to get logs from node ip-172-20-53-171.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-7gqk container test-container-subpath-dynamicpv-7gqk: <nil>
STEP: delete the pod
Jun  6 08:22:11.072: INFO: Waiting for pod pod-subpath-test-dynamicpv-7gqk to disappear
Jun  6 08:22:11.232: INFO: Pod pod-subpath-test-dynamicpv-7gqk no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-7gqk
Jun  6 08:22:11.232: INFO: Deleting pod "pod-subpath-test-dynamicpv-7gqk" in namespace "provisioning-2662"
STEP: Creating pod pod-subpath-test-dynamicpv-7gqk
STEP: Creating a pod to test subpath
Jun  6 08:22:11.558: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-7gqk" in namespace "provisioning-2662" to be "Succeeded or Failed"
Jun  6 08:22:11.719: INFO: Pod "pod-subpath-test-dynamicpv-7gqk": Phase="Pending", Reason="", readiness=false. Elapsed: 160.481689ms
Jun  6 08:22:13.879: INFO: Pod "pod-subpath-test-dynamicpv-7gqk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.320967093s
Jun  6 08:22:16.040: INFO: Pod "pod-subpath-test-dynamicpv-7gqk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.482292459s
Jun  6 08:22:18.203: INFO: Pod "pod-subpath-test-dynamicpv-7gqk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.644905458s
Jun  6 08:22:20.364: INFO: Pod "pod-subpath-test-dynamicpv-7gqk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.805926083s
Jun  6 08:22:22.526: INFO: Pod "pod-subpath-test-dynamicpv-7gqk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.968328521s
STEP: Saw pod success
Jun  6 08:22:22.527: INFO: Pod "pod-subpath-test-dynamicpv-7gqk" satisfied condition "Succeeded or Failed"
Jun  6 08:22:22.687: INFO: Trying to get logs from node ip-172-20-53-171.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-7gqk container test-container-subpath-dynamicpv-7gqk: <nil>
STEP: delete the pod
Jun  6 08:22:23.018: INFO: Waiting for pod pod-subpath-test-dynamicpv-7gqk to disappear
Jun  6 08:22:23.182: INFO: Pod pod-subpath-test-dynamicpv-7gqk no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-7gqk
Jun  6 08:22:23.182: INFO: Deleting pod "pod-subpath-test-dynamicpv-7gqk" in namespace "provisioning-2662"
... skipping 224 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.Q9ZXkT72D/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.Q9ZXkT72D/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.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 48 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  6 08:22:21.455: 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.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun  6 08:22:22.284: INFO: Creating resource for dynamic PV
Jun  6 08:22:22.284: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3568-e2e-scctwl6
STEP: creating a claim
Jun  6 08:22:22.448: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-zgdd
STEP: Checking for subpath error in container status
Jun  6 08:22:35.264: INFO: Deleting pod "pod-subpath-test-dynamicpv-zgdd" in namespace "provisioning-3568"
Jun  6 08:22:35.427: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-zgdd" to be fully deleted
STEP: Deleting pod
Jun  6 08:22:45.751: INFO: Deleting pod "pod-subpath-test-dynamicpv-zgdd" in namespace "provisioning-3568"
STEP: Deleting pvc
Jun  6 08:22:46.236: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com5pp6n"
... skipping 11 lines ...

• [SLOW TEST:41.103 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.Q9ZXkT72D/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.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  6 08:23:02.560: INFO: Driver aws doesn't support CSIInlineVolume -- skipping
[AfterEach] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral
... skipping 142 lines ...
STEP: Deleting pod hostexec-ip-172-20-33-48.ap-northeast-2.compute.internal-xfw9p in namespace volumemode-8770
Jun  6 08:22:46.013: INFO: Deleting pod "pod-be8d96de-4bb4-4364-b521-eee65ada2a35" in namespace "volumemode-8770"
Jun  6 08:22:46.180: INFO: Wait up to 5m0s for pod "pod-be8d96de-4bb4-4364-b521-eee65ada2a35" to be fully deleted
STEP: Deleting pv and pvc
Jun  6 08:22:58.510: INFO: Deleting PersistentVolumeClaim "pvc-96dmg"
Jun  6 08:22:58.676: INFO: Deleting PersistentVolume "aws-v6n6p"
Jun  6 08:22:59.105: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-043a2191a8fd30d63", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-043a2191a8fd30d63 is currently attached to i-0a4f9cf0993c78da0
	status code: 400, request id: 63ec9fa4-0287-4f4d-9c42-c100aa9c549c
Jun  6 08:23:04.900: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-043a2191a8fd30d63".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  6 08:23:04.901: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-8770" for this suite.
... skipping 18 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.Q9ZXkT72D/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.Q9ZXkT72D/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.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 628 lines ...
Jun  6 08:22:59.841: INFO: Waiting for pod aws-client to disappear
Jun  6 08:23:00.001: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun  6 08:23:00.001: INFO: Deleting PersistentVolumeClaim "pvc-5mlzg"
Jun  6 08:23:00.163: INFO: Deleting PersistentVolume "aws-2hnjz"
Jun  6 08:23:01.175: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-031b6473e5f7714cf", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-031b6473e5f7714cf is currently attached to i-0d09dc59d79b0c8d5
	status code: 400, request id: 40e39ad9-c91d-4f19-bab5-3fd46f583e33
Jun  6 08:23:06.934: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-031b6473e5f7714cf", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-031b6473e5f7714cf is currently attached to i-0d09dc59d79b0c8d5
	status code: 400, request id: 7da09ffd-3519-4341-b956-de94ed9c1687
Jun  6 08:23:12.738: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-031b6473e5f7714cf".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumes
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  6 08:23:12.738: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-4963" for this suite.
... skipping 172 lines ...
Jun  6 08:21:37.190: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-4757gt8f8      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-4757    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-4757gt8f8,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-4757    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-4757gt8f8,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-4757    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-4757gt8f8,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-4757gt8f8    61c7872b-2787-4d1b-9e45-f66d0318c04c 6445 0 2021-06-06 08:21:37 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-06 08:21:37 +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-282zz pvc- provisioning-4757  5c612be1-3689-41b2-912a-e84ea55a9ef5 6464 0 2021-06-06 08:21:37 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-06 08:21:37 +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-4757gt8f8,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-fbf654af-7c49-4782-b0fd-845c59c7c1c3 in namespace provisioning-4757
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun  6 08:22:16.961: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-tpw4d" in namespace "provisioning-4757" to be "Succeeded or Failed"
Jun  6 08:22:17.120: INFO: Pod "pvc-volume-tester-writer-tpw4d": Phase="Pending", Reason="", readiness=false. Elapsed: 158.725855ms
Jun  6 08:22:19.279: INFO: Pod "pvc-volume-tester-writer-tpw4d": Phase="Pending", Reason="", readiness=false. Elapsed: 2.317304397s
Jun  6 08:22:21.436: INFO: Pod "pvc-volume-tester-writer-tpw4d": Phase="Pending", Reason="", readiness=false. Elapsed: 4.474708159s
Jun  6 08:22:23.594: INFO: Pod "pvc-volume-tester-writer-tpw4d": Phase="Pending", Reason="", readiness=false. Elapsed: 6.632707429s
Jun  6 08:22:25.753: INFO: Pod "pvc-volume-tester-writer-tpw4d": Phase="Pending", Reason="", readiness=false. Elapsed: 8.791403015s
Jun  6 08:22:27.911: INFO: Pod "pvc-volume-tester-writer-tpw4d": Phase="Pending", Reason="", readiness=false. Elapsed: 10.949791626s
... skipping 8 lines ...
Jun  6 08:22:47.337: INFO: Pod "pvc-volume-tester-writer-tpw4d": Phase="Pending", Reason="", readiness=false. Elapsed: 30.376027612s
Jun  6 08:22:49.497: INFO: Pod "pvc-volume-tester-writer-tpw4d": Phase="Pending", Reason="", readiness=false. Elapsed: 32.535514789s
Jun  6 08:22:51.655: INFO: Pod "pvc-volume-tester-writer-tpw4d": Phase="Pending", Reason="", readiness=false. Elapsed: 34.693491553s
Jun  6 08:22:53.814: INFO: Pod "pvc-volume-tester-writer-tpw4d": Phase="Pending", Reason="", readiness=false. Elapsed: 36.852986936s
Jun  6 08:22:55.975: INFO: Pod "pvc-volume-tester-writer-tpw4d": Phase="Succeeded", Reason="", readiness=false. Elapsed: 39.01396348s
STEP: Saw pod success
Jun  6 08:22:55.975: INFO: Pod "pvc-volume-tester-writer-tpw4d" satisfied condition "Succeeded or Failed"
Jun  6 08:22:56.291: INFO: Pod pvc-volume-tester-writer-tpw4d has the following logs: 
Jun  6 08:22:56.292: INFO: Deleting pod "pvc-volume-tester-writer-tpw4d" in namespace "provisioning-4757"
Jun  6 08:22:56.456: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-tpw4d" to be fully deleted
STEP: checking the created volume has the correct mount options, is readable and retains data on the same node "ip-172-20-33-48.ap-northeast-2.compute.internal"
Jun  6 08:22:57.106: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-g6x8l" in namespace "provisioning-4757" to be "Succeeded or Failed"
Jun  6 08:22:57.264: INFO: Pod "pvc-volume-tester-reader-g6x8l": Phase="Pending", Reason="", readiness=false. Elapsed: 158.110568ms
Jun  6 08:22:59.422: INFO: Pod "pvc-volume-tester-reader-g6x8l": Phase="Pending", Reason="", readiness=false. Elapsed: 2.315778411s
Jun  6 08:23:01.579: INFO: Pod "pvc-volume-tester-reader-g6x8l": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.473161746s
STEP: Saw pod success
Jun  6 08:23:01.579: INFO: Pod "pvc-volume-tester-reader-g6x8l" satisfied condition "Succeeded or Failed"
Jun  6 08:23:01.897: INFO: Pod pvc-volume-tester-reader-g6x8l has the following logs: hello world

Jun  6 08:23:01.897: INFO: Deleting pod "pvc-volume-tester-reader-g6x8l" in namespace "provisioning-4757"
Jun  6 08:23:02.061: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-g6x8l" to be fully deleted
Jun  6 08:23:02.219: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-282zz] to have phase Bound
Jun  6 08:23:02.376: INFO: PersistentVolumeClaim pvc-282zz found and phase=Bound (157.284844ms)
... skipping 200 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Q9ZXkT72D/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Q9ZXkT72D/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.Q9ZXkT72D/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.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 123 lines ...
Jun  6 08:20:39.699: INFO: Creating resource for dynamic PV
Jun  6 08:20:39.699: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-8837-e2e-scz87h5
STEP: creating a claim
Jun  6 08:20:39.863: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun  6 08:20:40.357: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-zpb7w" in namespace "snapshotting-8837" to be "Succeeded or Failed"
Jun  6 08:20:40.521: INFO: Pod "pvc-snapshottable-tester-zpb7w": Phase="Pending", Reason="", readiness=false. Elapsed: 163.584325ms
Jun  6 08:20:42.686: INFO: Pod "pvc-snapshottable-tester-zpb7w": Phase="Pending", Reason="", readiness=false. Elapsed: 2.328742076s
Jun  6 08:20:44.853: INFO: Pod "pvc-snapshottable-tester-zpb7w": Phase="Pending", Reason="", readiness=false. Elapsed: 4.495077758s
Jun  6 08:20:47.018: INFO: Pod "pvc-snapshottable-tester-zpb7w": Phase="Pending", Reason="", readiness=false. Elapsed: 6.66012957s
Jun  6 08:20:49.184: INFO: Pod "pvc-snapshottable-tester-zpb7w": Phase="Pending", Reason="", readiness=false. Elapsed: 8.826402138s
Jun  6 08:20:51.359: INFO: Pod "pvc-snapshottable-tester-zpb7w": Phase="Pending", Reason="", readiness=false. Elapsed: 11.001879285s
Jun  6 08:20:53.528: INFO: Pod "pvc-snapshottable-tester-zpb7w": Phase="Pending", Reason="", readiness=false. Elapsed: 13.170372713s
Jun  6 08:20:55.693: INFO: Pod "pvc-snapshottable-tester-zpb7w": Phase="Pending", Reason="", readiness=false. Elapsed: 15.335451645s
Jun  6 08:20:57.858: INFO: Pod "pvc-snapshottable-tester-zpb7w": Phase="Pending", Reason="", readiness=false. Elapsed: 17.500339176s
Jun  6 08:21:00.022: INFO: Pod "pvc-snapshottable-tester-zpb7w": Phase="Pending", Reason="", readiness=false. Elapsed: 19.664681241s
Jun  6 08:21:02.187: INFO: Pod "pvc-snapshottable-tester-zpb7w": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.829138122s
STEP: Saw pod success
Jun  6 08:21:02.187: INFO: Pod "pvc-snapshottable-tester-zpb7w" satisfied condition "Succeeded or Failed"
Jun  6 08:21:02.516: INFO: Pod pvc-snapshottable-tester-zpb7w has the following logs: 
Jun  6 08:21:02.516: INFO: Deleting pod "pvc-snapshottable-tester-zpb7w" in namespace "snapshotting-8837"
Jun  6 08:21:02.693: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-zpb7w" to be fully deleted
Jun  6 08:21:02.859: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comwg996] to have phase Bound
Jun  6 08:21:03.022: INFO: PersistentVolumeClaim ebs.csi.aws.comwg996 found and phase=Bound (163.151541ms)
STEP: [init] checking the claim
... skipping 19 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.Q9ZXkT72D/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 08:21:24.333: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-ntgqw" in namespace "snapshotting-8837" to be "Succeeded or Failed"
Jun  6 08:21:24.497: INFO: Pod "pvc-snapshottable-data-tester-ntgqw": Phase="Pending", Reason="", readiness=false. Elapsed: 164.224186ms
Jun  6 08:21:26.662: INFO: Pod "pvc-snapshottable-data-tester-ntgqw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.329108453s
Jun  6 08:21:28.850: INFO: Pod "pvc-snapshottable-data-tester-ntgqw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.517672285s
Jun  6 08:21:31.018: INFO: Pod "pvc-snapshottable-data-tester-ntgqw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.685600751s
Jun  6 08:21:33.183: INFO: Pod "pvc-snapshottable-data-tester-ntgqw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.850628568s
Jun  6 08:21:35.347: INFO: Pod "pvc-snapshottable-data-tester-ntgqw": Phase="Pending", Reason="", readiness=false. Elapsed: 11.014638282s
Jun  6 08:21:37.515: INFO: Pod "pvc-snapshottable-data-tester-ntgqw": Phase="Pending", Reason="", readiness=false. Elapsed: 13.182234096s
Jun  6 08:21:39.680: INFO: Pod "pvc-snapshottable-data-tester-ntgqw": Phase="Pending", Reason="", readiness=false. Elapsed: 15.347021605s
Jun  6 08:21:41.847: INFO: Pod "pvc-snapshottable-data-tester-ntgqw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 17.513873335s
STEP: Saw pod success
Jun  6 08:21:41.847: INFO: Pod "pvc-snapshottable-data-tester-ntgqw" satisfied condition "Succeeded or Failed"
Jun  6 08:21:42.178: INFO: Pod pvc-snapshottable-data-tester-ntgqw has the following logs: 
Jun  6 08:21:42.178: INFO: Deleting pod "pvc-snapshottable-data-tester-ntgqw" in namespace "snapshotting-8837"
Jun  6 08:21:42.351: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-ntgqw" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun  6 08:22:05.173: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-8837 exec restored-pvc-tester-6jmlh --namespace=snapshotting-8837 -- cat /mnt/test/data'
... skipping 29 lines ...
Jun  6 08:22:30.801: INFO: volumesnapshotcontents snapcontent-7f32f3c7-62fb-4c0b-bff9-5a62ea3cda4c has been found and is not deleted
Jun  6 08:22:31.965: INFO: volumesnapshotcontents snapcontent-7f32f3c7-62fb-4c0b-bff9-5a62ea3cda4c has been found and is not deleted
Jun  6 08:22:33.129: INFO: volumesnapshotcontents snapcontent-7f32f3c7-62fb-4c0b-bff9-5a62ea3cda4c has been found and is not deleted
Jun  6 08:22:34.294: INFO: volumesnapshotcontents snapcontent-7f32f3c7-62fb-4c0b-bff9-5a62ea3cda4c has been found and is not deleted
Jun  6 08:22:35.459: INFO: volumesnapshotcontents snapcontent-7f32f3c7-62fb-4c0b-bff9-5a62ea3cda4c has been found and is not deleted
Jun  6 08:22:36.623: INFO: volumesnapshotcontents snapcontent-7f32f3c7-62fb-4c0b-bff9-5a62ea3cda4c has been found and is not deleted
Jun  6 08:22:37.623: INFO: WaitUntil failed after reaching the timeout 30s
[AfterEach] volume snapshot controller
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:221
Jun  6 08:22:37.789: INFO: Pod restored-pvc-tester-6jmlh has the following logs: 
Jun  6 08:22:37.789: INFO: Deleting pod "restored-pvc-tester-6jmlh" in namespace "snapshotting-8837"
Jun  6 08:22:37.956: INFO: Wait up to 5m0s for pod "restored-pvc-tester-6jmlh" to be fully deleted
Jun  6 08:23:22.295: INFO: deleting claim "snapshotting-8837"/"pvc-zwv2c"
... skipping 229 lines ...
Jun  6 08:22:39.562: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9280-e2e-scgjhj7
STEP: creating a claim
Jun  6 08:22:39.719: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-cbq2
STEP: Creating a pod to test subpath
Jun  6 08:22:40.206: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-cbq2" in namespace "provisioning-9280" to be "Succeeded or Failed"
Jun  6 08:22:40.363: INFO: Pod "pod-subpath-test-dynamicpv-cbq2": Phase="Pending", Reason="", readiness=false. Elapsed: 156.48441ms
Jun  6 08:22:42.520: INFO: Pod "pod-subpath-test-dynamicpv-cbq2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.313369215s
Jun  6 08:22:44.681: INFO: Pod "pod-subpath-test-dynamicpv-cbq2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.474433443s
Jun  6 08:22:46.838: INFO: Pod "pod-subpath-test-dynamicpv-cbq2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.631966238s
Jun  6 08:22:48.996: INFO: Pod "pod-subpath-test-dynamicpv-cbq2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.789589419s
Jun  6 08:22:51.154: INFO: Pod "pod-subpath-test-dynamicpv-cbq2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.947100591s
Jun  6 08:22:53.313: INFO: Pod "pod-subpath-test-dynamicpv-cbq2": Phase="Pending", Reason="", readiness=false. Elapsed: 13.106147428s
Jun  6 08:22:55.470: INFO: Pod "pod-subpath-test-dynamicpv-cbq2": Phase="Pending", Reason="", readiness=false. Elapsed: 15.26334091s
Jun  6 08:22:57.627: INFO: Pod "pod-subpath-test-dynamicpv-cbq2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 17.420779015s
STEP: Saw pod success
Jun  6 08:22:57.627: INFO: Pod "pod-subpath-test-dynamicpv-cbq2" satisfied condition "Succeeded or Failed"
Jun  6 08:22:57.784: INFO: Trying to get logs from node ip-172-20-40-222.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-cbq2 container test-container-volume-dynamicpv-cbq2: <nil>
STEP: delete the pod
Jun  6 08:22:58.109: INFO: Waiting for pod pod-subpath-test-dynamicpv-cbq2 to disappear
Jun  6 08:22:58.265: INFO: Pod pod-subpath-test-dynamicpv-cbq2 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-cbq2
Jun  6 08:22:58.265: INFO: Deleting pod "pod-subpath-test-dynamicpv-cbq2" in namespace "provisioning-9280"
... skipping 40 lines ...
Jun  6 08:23:02.719: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6313nlccc
STEP: creating a claim
Jun  6 08:23:02.881: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-bx4m
STEP: Creating a pod to test subpath
Jun  6 08:23:03.369: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-bx4m" in namespace "provisioning-6313" to be "Succeeded or Failed"
Jun  6 08:23:03.529: INFO: Pod "pod-subpath-test-dynamicpv-bx4m": Phase="Pending", Reason="", readiness=false. Elapsed: 160.521379ms
Jun  6 08:23:05.690: INFO: Pod "pod-subpath-test-dynamicpv-bx4m": Phase="Pending", Reason="", readiness=false. Elapsed: 2.321088987s
Jun  6 08:23:07.857: INFO: Pod "pod-subpath-test-dynamicpv-bx4m": Phase="Pending", Reason="", readiness=false. Elapsed: 4.488460286s
Jun  6 08:23:10.022: INFO: Pod "pod-subpath-test-dynamicpv-bx4m": Phase="Pending", Reason="", readiness=false. Elapsed: 6.653059125s
Jun  6 08:23:12.184: INFO: Pod "pod-subpath-test-dynamicpv-bx4m": Phase="Pending", Reason="", readiness=false. Elapsed: 8.815512968s
Jun  6 08:23:14.345: INFO: Pod "pod-subpath-test-dynamicpv-bx4m": Phase="Pending", Reason="", readiness=false. Elapsed: 10.976324981s
Jun  6 08:23:16.507: INFO: Pod "pod-subpath-test-dynamicpv-bx4m": Phase="Pending", Reason="", readiness=false. Elapsed: 13.13788383s
Jun  6 08:23:18.668: INFO: Pod "pod-subpath-test-dynamicpv-bx4m": Phase="Pending", Reason="", readiness=false. Elapsed: 15.29953081s
Jun  6 08:23:20.829: INFO: Pod "pod-subpath-test-dynamicpv-bx4m": Phase="Pending", Reason="", readiness=false. Elapsed: 17.460305913s
Jun  6 08:23:22.991: INFO: Pod "pod-subpath-test-dynamicpv-bx4m": Phase="Pending", Reason="", readiness=false. Elapsed: 19.622087977s
Jun  6 08:23:25.153: INFO: Pod "pod-subpath-test-dynamicpv-bx4m": Phase="Pending", Reason="", readiness=false. Elapsed: 21.783841815s
Jun  6 08:23:27.316: INFO: Pod "pod-subpath-test-dynamicpv-bx4m": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.947423064s
STEP: Saw pod success
Jun  6 08:23:27.316: INFO: Pod "pod-subpath-test-dynamicpv-bx4m" satisfied condition "Succeeded or Failed"
Jun  6 08:23:27.477: INFO: Trying to get logs from node ip-172-20-40-222.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-bx4m container test-container-subpath-dynamicpv-bx4m: <nil>
STEP: delete the pod
Jun  6 08:23:27.812: INFO: Waiting for pod pod-subpath-test-dynamicpv-bx4m to disappear
Jun  6 08:23:27.973: INFO: Pod pod-subpath-test-dynamicpv-bx4m no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-bx4m
Jun  6 08:23:27.973: INFO: Deleting pod "pod-subpath-test-dynamicpv-bx4m" in namespace "provisioning-6313"
... skipping 347 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  6 08:23:07.782: 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.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun  6 08:23:08.580: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  6 08:23:08.580: INFO: Creating resource for dynamic PV
Jun  6 08:23:08.580: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-84466dx9x
STEP: creating a claim
Jun  6 08:23:08.738: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-r2tg
STEP: Checking for subpath error in container status
Jun  6 08:23:33.544: INFO: Deleting pod "pod-subpath-test-dynamicpv-r2tg" in namespace "provisioning-8446"
Jun  6 08:23:33.703: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-r2tg" to be fully deleted
STEP: Deleting pod
Jun  6 08:23:38.026: INFO: Deleting pod "pod-subpath-test-dynamicpv-r2tg" in namespace "provisioning-8446"
STEP: Deleting pvc
Jun  6 08:23:38.500: INFO: Deleting PersistentVolumeClaim "awshp25d"
... skipping 13 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Q9ZXkT72D/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Q9ZXkT72D/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.Q9ZXkT72D/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.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
... skipping 6 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Q9ZXkT72D/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Q9ZXkT72D/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.Q9ZXkT72D/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.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 33 lines ...
Jun  6 08:23:08.425: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-36187t5qf
STEP: creating a claim
Jun  6 08:23:08.601: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-x5ws
STEP: Creating a pod to test subpath
Jun  6 08:23:09.096: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-x5ws" in namespace "provisioning-3618" to be "Succeeded or Failed"
Jun  6 08:23:09.261: INFO: Pod "pod-subpath-test-dynamicpv-x5ws": Phase="Pending", Reason="", readiness=false. Elapsed: 164.402005ms
Jun  6 08:23:11.428: INFO: Pod "pod-subpath-test-dynamicpv-x5ws": Phase="Pending", Reason="", readiness=false. Elapsed: 2.331445075s
Jun  6 08:23:13.593: INFO: Pod "pod-subpath-test-dynamicpv-x5ws": Phase="Pending", Reason="", readiness=false. Elapsed: 4.49645832s
Jun  6 08:23:15.759: INFO: Pod "pod-subpath-test-dynamicpv-x5ws": Phase="Pending", Reason="", readiness=false. Elapsed: 6.66211518s
Jun  6 08:23:17.924: INFO: Pod "pod-subpath-test-dynamicpv-x5ws": Phase="Pending", Reason="", readiness=false. Elapsed: 8.827128248s
Jun  6 08:23:20.089: INFO: Pod "pod-subpath-test-dynamicpv-x5ws": Phase="Pending", Reason="", readiness=false. Elapsed: 10.992833285s
Jun  6 08:23:22.254: INFO: Pod "pod-subpath-test-dynamicpv-x5ws": Phase="Pending", Reason="", readiness=false. Elapsed: 13.157845708s
Jun  6 08:23:24.419: INFO: Pod "pod-subpath-test-dynamicpv-x5ws": Phase="Pending", Reason="", readiness=false. Elapsed: 15.322573408s
Jun  6 08:23:26.584: INFO: Pod "pod-subpath-test-dynamicpv-x5ws": Phase="Pending", Reason="", readiness=false. Elapsed: 17.487246585s
Jun  6 08:23:28.748: INFO: Pod "pod-subpath-test-dynamicpv-x5ws": Phase="Pending", Reason="", readiness=false. Elapsed: 19.651605703s
Jun  6 08:23:30.914: INFO: Pod "pod-subpath-test-dynamicpv-x5ws": Phase="Pending", Reason="", readiness=false. Elapsed: 21.817069208s
Jun  6 08:23:33.084: INFO: Pod "pod-subpath-test-dynamicpv-x5ws": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.987906283s
STEP: Saw pod success
Jun  6 08:23:33.084: INFO: Pod "pod-subpath-test-dynamicpv-x5ws" satisfied condition "Succeeded or Failed"
Jun  6 08:23:33.249: INFO: Trying to get logs from node ip-172-20-33-48.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-x5ws container test-container-volume-dynamicpv-x5ws: <nil>
STEP: delete the pod
Jun  6 08:23:33.592: INFO: Waiting for pod pod-subpath-test-dynamicpv-x5ws to disappear
Jun  6 08:23:33.757: INFO: Pod pod-subpath-test-dynamicpv-x5ws no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-x5ws
Jun  6 08:23:33.757: INFO: Deleting pod "pod-subpath-test-dynamicpv-x5ws" in namespace "provisioning-3618"
... skipping 39 lines ...
Jun  6 08:23:08.643: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-511kp2kq
STEP: creating a claim
Jun  6 08:23:08.813: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-69bv
STEP: Creating a pod to test multi_subpath
Jun  6 08:23:09.307: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-69bv" in namespace "provisioning-511" to be "Succeeded or Failed"
Jun  6 08:23:09.472: INFO: Pod "pod-subpath-test-dynamicpv-69bv": Phase="Pending", Reason="", readiness=false. Elapsed: 164.84201ms
Jun  6 08:23:11.657: INFO: Pod "pod-subpath-test-dynamicpv-69bv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.349062722s
Jun  6 08:23:13.822: INFO: Pod "pod-subpath-test-dynamicpv-69bv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.514477823s
Jun  6 08:23:15.987: INFO: Pod "pod-subpath-test-dynamicpv-69bv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.679529143s
Jun  6 08:23:18.153: INFO: Pod "pod-subpath-test-dynamicpv-69bv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.845133594s
Jun  6 08:23:20.318: INFO: Pod "pod-subpath-test-dynamicpv-69bv": Phase="Pending", Reason="", readiness=false. Elapsed: 11.010578939s
Jun  6 08:23:22.483: INFO: Pod "pod-subpath-test-dynamicpv-69bv": Phase="Pending", Reason="", readiness=false. Elapsed: 13.175144099s
Jun  6 08:23:24.648: INFO: Pod "pod-subpath-test-dynamicpv-69bv": Phase="Pending", Reason="", readiness=false. Elapsed: 15.340075272s
Jun  6 08:23:26.816: INFO: Pod "pod-subpath-test-dynamicpv-69bv": Phase="Pending", Reason="", readiness=false. Elapsed: 17.508798535s
Jun  6 08:23:28.982: INFO: Pod "pod-subpath-test-dynamicpv-69bv": Phase="Pending", Reason="", readiness=false. Elapsed: 19.674235033s
Jun  6 08:23:31.146: INFO: Pod "pod-subpath-test-dynamicpv-69bv": Phase="Pending", Reason="", readiness=false. Elapsed: 21.83842854s
Jun  6 08:23:33.310: INFO: Pod "pod-subpath-test-dynamicpv-69bv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.002361418s
STEP: Saw pod success
Jun  6 08:23:33.310: INFO: Pod "pod-subpath-test-dynamicpv-69bv" satisfied condition "Succeeded or Failed"
Jun  6 08:23:33.474: INFO: Trying to get logs from node ip-172-20-53-171.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-69bv container test-container-subpath-dynamicpv-69bv: <nil>
STEP: delete the pod
Jun  6 08:23:33.814: INFO: Waiting for pod pod-subpath-test-dynamicpv-69bv to disappear
Jun  6 08:23:33.980: INFO: Pod pod-subpath-test-dynamicpv-69bv no longer exists
STEP: Deleting pod
Jun  6 08:23:33.980: INFO: Deleting pod "pod-subpath-test-dynamicpv-69bv" in namespace "provisioning-511"
... skipping 90 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  6 08:23:29.978: 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.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  6 08:23:30.761: INFO: Creating resource for dynamic PV
Jun  6 08:23:30.761: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-4262-e2e-scrbgw7
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  6 08:23:37.876: INFO: Deleting pod "pod-2f246794-2094-4c47-b6d0-c3aed7be8bf3" in namespace "volumemode-4262"
Jun  6 08:23:38.037: INFO: Wait up to 5m0s for pod "pod-2f246794-2094-4c47-b6d0-c3aed7be8bf3" to be fully deleted
STEP: Deleting pvc
Jun  6 08:23:48.663: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comf2bln"
Jun  6 08:23:48.828: INFO: Waiting up to 5m0s for PersistentVolume pvc-67066cf8-fbdc-42e9-ad57-2ca81933db9c to get deleted
Jun  6 08:23:48.984: INFO: PersistentVolume pvc-67066cf8-fbdc-42e9-ad57-2ca81933db9c found and phase=Released (156.811321ms)
... skipping 8 lines ...

• [SLOW TEST:29.798 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.Q9ZXkT72D/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.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] provisioning
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] provisioning
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 179 lines ...
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  6 08:24:05.166: 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.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Jun  6 08:24:06.104: INFO: found topology map[topology.kubernetes.io/zone:ap-northeast-2a]
Jun  6 08:24:06.104: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  6 08:24:06.104: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Q9ZXkT72D/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Q9ZXkT72D/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (immediate binding)] topology
    /tmp/kops.Q9ZXkT72D/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.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 11 lines ...
Jun  6 08:23:40.728: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-6700-e2e-sc758sh
STEP: creating a claim
Jun  6 08:23:40.884: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-xhlj
STEP: Creating a pod to test exec-volume-test
Jun  6 08:23:41.353: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-xhlj" in namespace "volume-6700" to be "Succeeded or Failed"
Jun  6 08:23:41.508: INFO: Pod "exec-volume-test-dynamicpv-xhlj": Phase="Pending", Reason="", readiness=false. Elapsed: 154.596218ms
Jun  6 08:23:43.663: INFO: Pod "exec-volume-test-dynamicpv-xhlj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.309572119s
Jun  6 08:23:45.818: INFO: Pod "exec-volume-test-dynamicpv-xhlj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.464949335s
Jun  6 08:23:47.974: INFO: Pod "exec-volume-test-dynamicpv-xhlj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.62078968s
Jun  6 08:23:50.130: INFO: Pod "exec-volume-test-dynamicpv-xhlj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.776551505s
Jun  6 08:23:52.286: INFO: Pod "exec-volume-test-dynamicpv-xhlj": Phase="Pending", Reason="", readiness=false. Elapsed: 10.933297551s
Jun  6 08:23:54.443: INFO: Pod "exec-volume-test-dynamicpv-xhlj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 13.089739978s
STEP: Saw pod success
Jun  6 08:23:54.443: INFO: Pod "exec-volume-test-dynamicpv-xhlj" satisfied condition "Succeeded or Failed"
Jun  6 08:23:54.598: INFO: Trying to get logs from node ip-172-20-53-171.ap-northeast-2.compute.internal pod exec-volume-test-dynamicpv-xhlj container exec-container-dynamicpv-xhlj: <nil>
STEP: delete the pod
Jun  6 08:23:54.914: INFO: Waiting for pod exec-volume-test-dynamicpv-xhlj to disappear
Jun  6 08:23:55.068: INFO: Pod exec-volume-test-dynamicpv-xhlj no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-xhlj
Jun  6 08:23:55.068: INFO: Deleting pod "exec-volume-test-dynamicpv-xhlj" in namespace "volume-6700"
... skipping 137 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Q9ZXkT72D/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Q9ZXkT72D/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.Q9ZXkT72D/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.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Driver supports dynamic provisioning, skipping InlineVolume pattern

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 86 lines ...
Jun  6 08:24:07.681: INFO: Waiting for pod aws-client to disappear
Jun  6 08:24:07.860: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun  6 08:24:07.860: INFO: Deleting PersistentVolumeClaim "pvc-99tjn"
Jun  6 08:24:08.023: INFO: Deleting PersistentVolume "aws-hp7fx"
Jun  6 08:24:08.986: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0903b19ab16767d2c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0903b19ab16767d2c is currently attached to i-0a4f9cf0993c78da0
	status code: 400, request id: 6e19d0c3-36c6-40de-9743-d62cb563efa7
Jun  6 08:24:14.871: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-0903b19ab16767d2c".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  6 08:24:14.871: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-3679" for this suite.
... skipping 164 lines ...
Jun  6 08:22:44.709: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6149-e2e-scjhj6s
STEP: creating a claim
Jun  6 08:22:44.870: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-7hzw
STEP: Creating a pod to test multi_subpath
Jun  6 08:22:45.355: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-7hzw" in namespace "provisioning-6149" to be "Succeeded or Failed"
Jun  6 08:22:45.524: INFO: Pod "pod-subpath-test-dynamicpv-7hzw": Phase="Pending", Reason="", readiness=false. Elapsed: 169.094528ms
Jun  6 08:22:47.689: INFO: Pod "pod-subpath-test-dynamicpv-7hzw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.333954315s
Jun  6 08:22:49.851: INFO: Pod "pod-subpath-test-dynamicpv-7hzw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.4960096s
Jun  6 08:22:52.012: INFO: Pod "pod-subpath-test-dynamicpv-7hzw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.656596787s
Jun  6 08:22:54.172: INFO: Pod "pod-subpath-test-dynamicpv-7hzw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.81745102s
Jun  6 08:22:56.334: INFO: Pod "pod-subpath-test-dynamicpv-7hzw": Phase="Pending", Reason="", readiness=false. Elapsed: 10.978568363s
... skipping 2 lines ...
Jun  6 08:23:02.827: INFO: Pod "pod-subpath-test-dynamicpv-7hzw": Phase="Pending", Reason="", readiness=false. Elapsed: 17.472064565s
Jun  6 08:23:04.989: INFO: Pod "pod-subpath-test-dynamicpv-7hzw": Phase="Pending", Reason="", readiness=false. Elapsed: 19.63389751s
Jun  6 08:23:07.154: INFO: Pod "pod-subpath-test-dynamicpv-7hzw": Phase="Pending", Reason="", readiness=false. Elapsed: 21.799044517s
Jun  6 08:23:09.318: INFO: Pod "pod-subpath-test-dynamicpv-7hzw": Phase="Pending", Reason="", readiness=false. Elapsed: 23.96309127s
Jun  6 08:23:11.480: INFO: Pod "pod-subpath-test-dynamicpv-7hzw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.124786677s
STEP: Saw pod success
Jun  6 08:23:11.480: INFO: Pod "pod-subpath-test-dynamicpv-7hzw" satisfied condition "Succeeded or Failed"
Jun  6 08:23:11.653: INFO: Trying to get logs from node ip-172-20-47-232.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-7hzw container test-container-subpath-dynamicpv-7hzw: <nil>
STEP: delete the pod
Jun  6 08:23:11.990: INFO: Waiting for pod pod-subpath-test-dynamicpv-7hzw to disappear
Jun  6 08:23:12.151: INFO: Pod pod-subpath-test-dynamicpv-7hzw no longer exists
STEP: Deleting pod
Jun  6 08:23:12.151: INFO: Deleting pod "pod-subpath-test-dynamicpv-7hzw" in namespace "provisioning-6149"
... skipping 467 lines ...
Jun  6 08:23:32.939: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6779d4qbs
STEP: creating a claim
Jun  6 08:23:33.107: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-h945
STEP: Creating a pod to test subpath
Jun  6 08:23:33.603: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-h945" in namespace "provisioning-6779" to be "Succeeded or Failed"
Jun  6 08:23:33.766: INFO: Pod "pod-subpath-test-dynamicpv-h945": Phase="Pending", Reason="", readiness=false. Elapsed: 163.40248ms
Jun  6 08:23:35.930: INFO: Pod "pod-subpath-test-dynamicpv-h945": Phase="Pending", Reason="", readiness=false. Elapsed: 2.327330627s
Jun  6 08:23:38.100: INFO: Pod "pod-subpath-test-dynamicpv-h945": Phase="Pending", Reason="", readiness=false. Elapsed: 4.497176531s
Jun  6 08:23:40.265: INFO: Pod "pod-subpath-test-dynamicpv-h945": Phase="Pending", Reason="", readiness=false. Elapsed: 6.661724174s
Jun  6 08:23:42.429: INFO: Pod "pod-subpath-test-dynamicpv-h945": Phase="Pending", Reason="", readiness=false. Elapsed: 8.825839412s
Jun  6 08:23:44.593: INFO: Pod "pod-subpath-test-dynamicpv-h945": Phase="Pending", Reason="", readiness=false. Elapsed: 10.989598092s
Jun  6 08:23:46.756: INFO: Pod "pod-subpath-test-dynamicpv-h945": Phase="Pending", Reason="", readiness=false. Elapsed: 13.153210963s
Jun  6 08:23:48.921: INFO: Pod "pod-subpath-test-dynamicpv-h945": Phase="Pending", Reason="", readiness=false. Elapsed: 15.318358218s
Jun  6 08:23:51.086: INFO: Pod "pod-subpath-test-dynamicpv-h945": Phase="Pending", Reason="", readiness=false. Elapsed: 17.48345494s
Jun  6 08:23:53.251: INFO: Pod "pod-subpath-test-dynamicpv-h945": Phase="Pending", Reason="", readiness=false. Elapsed: 19.647521134s
Jun  6 08:23:55.415: INFO: Pod "pod-subpath-test-dynamicpv-h945": Phase="Pending", Reason="", readiness=false. Elapsed: 21.811851562s
Jun  6 08:23:57.580: INFO: Pod "pod-subpath-test-dynamicpv-h945": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.976544911s
STEP: Saw pod success
Jun  6 08:23:57.580: INFO: Pod "pod-subpath-test-dynamicpv-h945" satisfied condition "Succeeded or Failed"
Jun  6 08:23:57.743: INFO: Trying to get logs from node ip-172-20-33-48.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-h945 container test-container-subpath-dynamicpv-h945: <nil>
STEP: delete the pod
Jun  6 08:23:58.097: INFO: Waiting for pod pod-subpath-test-dynamicpv-h945 to disappear
Jun  6 08:23:58.260: INFO: Pod pod-subpath-test-dynamicpv-h945 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-h945
Jun  6 08:23:58.261: INFO: Deleting pod "pod-subpath-test-dynamicpv-h945" in namespace "provisioning-6779"
... skipping 31 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  6 08:23:55.972: 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.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  6 08:23:56.793: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  6 08:23:57.775: INFO: Successfully created a new PD: "aws://ap-northeast-2a/vol-071802f6af63624e5".
Jun  6 08:23:57.775: INFO: Creating resource for pre-provisioned PV
Jun  6 08:23:57.775: INFO: Creating PVC and PV
... skipping 5 lines ...
Jun  6 08:24:02.682: INFO: PersistentVolumeClaim pvc-th8j6 found but phase is Pending instead of Bound.
Jun  6 08:24:04.846: INFO: PersistentVolumeClaim pvc-th8j6 found but phase is Pending instead of Bound.
Jun  6 08:24:07.011: INFO: PersistentVolumeClaim pvc-th8j6 found and phase=Bound (8.823186924s)
Jun  6 08:24:07.011: INFO: Waiting up to 3m0s for PersistentVolume aws-zgtpq to have phase Bound
Jun  6 08:24:07.179: INFO: PersistentVolume aws-zgtpq found and phase=Bound (168.007183ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  6 08:24:10.206: INFO: Deleting pod "pod-8a6822aa-c902-467e-93d9-b8fd01a5af02" in namespace "volumemode-8738"
Jun  6 08:24:10.374: INFO: Wait up to 5m0s for pod "pod-8a6822aa-c902-467e-93d9-b8fd01a5af02" to be fully deleted
STEP: Deleting pv and pvc
Jun  6 08:24:18.705: INFO: Deleting PersistentVolumeClaim "pvc-th8j6"
Jun  6 08:24:18.873: INFO: Deleting PersistentVolume "aws-zgtpq"
Jun  6 08:24:19.301: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-071802f6af63624e5", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-071802f6af63624e5 is currently attached to i-0a4f9cf0993c78da0
	status code: 400, request id: 61c564bd-d3dc-47ec-b725-414cd934d366
Jun  6 08:24:25.052: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-071802f6af63624e5", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-071802f6af63624e5 is currently attached to i-0a4f9cf0993c78da0
	status code: 400, request id: a9f604b6-b7f1-43f6-b81e-852cc0ee1ff4
Jun  6 08:24:30.844: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-071802f6af63624e5".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  6 08:24:30.844: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-8738" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Q9ZXkT72D/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Q9ZXkT72D/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
    /tmp/kops.Q9ZXkT72D/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.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 7 lines ...
Jun  6 08:23:16.651: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-492-e2e-sc54c42
STEP: creating a claim
Jun  6 08:23:16.810: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-czch
STEP: Creating a pod to test atomic-volume-subpath
Jun  6 08:23:17.290: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-czch" in namespace "provisioning-492" to be "Succeeded or Failed"
Jun  6 08:23:17.449: INFO: Pod "pod-subpath-test-dynamicpv-czch": Phase="Pending", Reason="", readiness=false. Elapsed: 158.512653ms
Jun  6 08:23:19.609: INFO: Pod "pod-subpath-test-dynamicpv-czch": Phase="Pending", Reason="", readiness=false. Elapsed: 2.31903408s
Jun  6 08:23:21.769: INFO: Pod "pod-subpath-test-dynamicpv-czch": Phase="Pending", Reason="", readiness=false. Elapsed: 4.478290119s
Jun  6 08:23:23.928: INFO: Pod "pod-subpath-test-dynamicpv-czch": Phase="Pending", Reason="", readiness=false. Elapsed: 6.637550206s
Jun  6 08:23:26.088: INFO: Pod "pod-subpath-test-dynamicpv-czch": Phase="Pending", Reason="", readiness=false. Elapsed: 8.797781427s
Jun  6 08:23:28.247: INFO: Pod "pod-subpath-test-dynamicpv-czch": Phase="Pending", Reason="", readiness=false. Elapsed: 10.956637233s
... skipping 17 lines ...
Jun  6 08:24:07.107: INFO: Pod "pod-subpath-test-dynamicpv-czch": Phase="Running", Reason="", readiness=true. Elapsed: 49.817142337s
Jun  6 08:24:09.265: INFO: Pod "pod-subpath-test-dynamicpv-czch": Phase="Running", Reason="", readiness=true. Elapsed: 51.97465093s
Jun  6 08:24:11.424: INFO: Pod "pod-subpath-test-dynamicpv-czch": Phase="Running", Reason="", readiness=true. Elapsed: 54.13341086s
Jun  6 08:24:13.580: INFO: Pod "pod-subpath-test-dynamicpv-czch": Phase="Running", Reason="", readiness=true. Elapsed: 56.289854565s
Jun  6 08:24:15.739: INFO: Pod "pod-subpath-test-dynamicpv-czch": Phase="Succeeded", Reason="", readiness=false. Elapsed: 58.448363152s
STEP: Saw pod success
Jun  6 08:24:15.739: INFO: Pod "pod-subpath-test-dynamicpv-czch" satisfied condition "Succeeded or Failed"
Jun  6 08:24:15.895: INFO: Trying to get logs from node ip-172-20-47-232.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-czch container test-container-subpath-dynamicpv-czch: <nil>
STEP: delete the pod
Jun  6 08:24:16.217: INFO: Waiting for pod pod-subpath-test-dynamicpv-czch to disappear
Jun  6 08:24:16.376: INFO: Pod pod-subpath-test-dynamicpv-czch no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-czch
Jun  6 08:24:16.376: INFO: Deleting pod "pod-subpath-test-dynamicpv-czch" in namespace "provisioning-492"
... skipping 70 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  6 08:24:06.578: 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.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  6 08:24:07.359: INFO: Creating resource for dynamic PV
Jun  6 08:24:07.359: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-7515-e2e-scb4r9k
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  6 08:24:12.500: INFO: Deleting pod "pod-7d7585bb-4d5f-45c7-9b49-d168c4de32c7" in namespace "volumemode-7515"
Jun  6 08:24:12.664: INFO: Wait up to 5m0s for pod "pod-7d7585bb-4d5f-45c7-9b49-d168c4de32c7" to be fully deleted
STEP: Deleting pvc
Jun  6 08:24:19.292: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comwf5jq"
Jun  6 08:24:19.449: INFO: Waiting up to 5m0s for PersistentVolume pvc-46934377-1e6c-4cf2-a4e1-5fd49e54aabf to get deleted
Jun  6 08:24:19.606: INFO: PersistentVolume pvc-46934377-1e6c-4cf2-a4e1-5fd49e54aabf found and phase=Released (156.326026ms)
... skipping 9 lines ...

• [SLOW TEST:28.975 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.Q9ZXkT72D/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.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  6 08:24:35.555: INFO: Distro debian doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
... skipping 182 lines ...
Jun  6 08:23:35.306: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9822f2j58
STEP: creating a claim
Jun  6 08:23:35.469: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-n4qk
STEP: Creating a pod to test atomic-volume-subpath
Jun  6 08:23:35.954: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-n4qk" in namespace "provisioning-9822" to be "Succeeded or Failed"
Jun  6 08:23:36.115: INFO: Pod "pod-subpath-test-dynamicpv-n4qk": Phase="Pending", Reason="", readiness=false. Elapsed: 160.894524ms
Jun  6 08:23:38.276: INFO: Pod "pod-subpath-test-dynamicpv-n4qk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.322152789s
Jun  6 08:23:40.438: INFO: Pod "pod-subpath-test-dynamicpv-n4qk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.484020733s
Jun  6 08:23:42.599: INFO: Pod "pod-subpath-test-dynamicpv-n4qk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.645029316s
Jun  6 08:23:44.764: INFO: Pod "pod-subpath-test-dynamicpv-n4qk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.810212693s
Jun  6 08:23:46.926: INFO: Pod "pod-subpath-test-dynamicpv-n4qk": Phase="Pending", Reason="", readiness=false. Elapsed: 10.972468801s
... skipping 10 lines ...
Jun  6 08:24:10.708: INFO: Pod "pod-subpath-test-dynamicpv-n4qk": Phase="Running", Reason="", readiness=true. Elapsed: 34.754715015s
Jun  6 08:24:12.869: INFO: Pod "pod-subpath-test-dynamicpv-n4qk": Phase="Running", Reason="", readiness=true. Elapsed: 36.915747068s
Jun  6 08:24:15.030: INFO: Pod "pod-subpath-test-dynamicpv-n4qk": Phase="Running", Reason="", readiness=true. Elapsed: 39.076294741s
Jun  6 08:24:17.197: INFO: Pod "pod-subpath-test-dynamicpv-n4qk": Phase="Running", Reason="", readiness=true. Elapsed: 41.243568382s
Jun  6 08:24:19.359: INFO: Pod "pod-subpath-test-dynamicpv-n4qk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 43.405256238s
STEP: Saw pod success
Jun  6 08:24:19.359: INFO: Pod "pod-subpath-test-dynamicpv-n4qk" satisfied condition "Succeeded or Failed"
Jun  6 08:24:19.520: INFO: Trying to get logs from node ip-172-20-33-48.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-n4qk container test-container-subpath-dynamicpv-n4qk: <nil>
STEP: delete the pod
Jun  6 08:24:19.856: INFO: Waiting for pod pod-subpath-test-dynamicpv-n4qk to disappear
Jun  6 08:24:20.016: INFO: Pod pod-subpath-test-dynamicpv-n4qk no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-n4qk
Jun  6 08:24:20.016: INFO: Deleting pod "pod-subpath-test-dynamicpv-n4qk" in namespace "provisioning-9822"
... skipping 549 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  6 08:24:17.466: 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.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  6 08:24:18.274: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  6 08:24:18.274: INFO: Creating resource for dynamic PV
Jun  6 08:24:18.274: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-1996r9zwb
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  6 08:24:23.404: INFO: Deleting pod "pod-24b99cbb-fdf9-493e-931e-b57cb571a41b" in namespace "volumemode-1996"
Jun  6 08:24:23.565: INFO: Wait up to 5m0s for pod "pod-24b99cbb-fdf9-493e-931e-b57cb571a41b" to be fully deleted
STEP: Deleting pvc
Jun  6 08:24:28.212: INFO: Deleting PersistentVolumeClaim "awsm698h"
Jun  6 08:24:28.373: INFO: Waiting up to 5m0s for PersistentVolume pvc-29196b54-ebd8-487e-a523-468c176868e5 to get deleted
Jun  6 08:24:28.533: INFO: PersistentVolume pvc-29196b54-ebd8-487e-a523-468c176868e5 found and phase=Released (160.257925ms)
... skipping 13 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Q9ZXkT72D/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Q9ZXkT72D/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
    /tmp/kops.Q9ZXkT72D/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.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] capacity
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  6 08:24:54.842: INFO: Driver ebs.csi.aws.com doesn't publish storage capacity -- skipping
[AfterEach] [Testpattern: Dynamic PV (default fs)] capacity
... skipping 26 lines ...
Jun  6 08:24:22.702: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-2708-e2e-sc6dlfr
STEP: creating a claim
Jun  6 08:24:22.863: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Jun  6 08:24:23.181: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun  6 08:24:23.517: INFO: Error updating pvc ebs.csi.aws.comzcpdl: PersistentVolumeClaim "ebs.csi.aws.comzcpdl" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2708-e2e-sc6dlfr",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun  6 08:24:54.163: INFO: Error updating pvc ebs.csi.aws.comzcpdl: PersistentVolumeClaim "ebs.csi.aws.comzcpdl" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 36 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Q9ZXkT72D/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Q9ZXkT72D/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.Q9ZXkT72D/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.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Distro debian doesn't support ntfs -- skipping

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.Q9ZXkT72D/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.Q9ZXkT72D/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.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 173 lines ...
Jun  6 08:24:22.265: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-1376wgt6v
STEP: creating a claim
Jun  6 08:24:22.425: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-9kbf
STEP: Creating a pod to test exec-volume-test
Jun  6 08:24:22.910: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-9kbf" in namespace "volume-1376" to be "Succeeded or Failed"
Jun  6 08:24:23.068: INFO: Pod "exec-volume-test-dynamicpv-9kbf": Phase="Pending", Reason="", readiness=false. Elapsed: 158.525521ms
Jun  6 08:24:25.227: INFO: Pod "exec-volume-test-dynamicpv-9kbf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.317199045s
Jun  6 08:24:27.387: INFO: Pod "exec-volume-test-dynamicpv-9kbf": Phase="Pending", Reason="", readiness=false. Elapsed: 4.477554662s
Jun  6 08:24:29.547: INFO: Pod "exec-volume-test-dynamicpv-9kbf": Phase="Pending", Reason="", readiness=false. Elapsed: 6.636859632s
Jun  6 08:24:31.706: INFO: Pod "exec-volume-test-dynamicpv-9kbf": Phase="Pending", Reason="", readiness=false. Elapsed: 8.796167671s
Jun  6 08:24:33.866: INFO: Pod "exec-volume-test-dynamicpv-9kbf": Phase="Pending", Reason="", readiness=false. Elapsed: 10.956356181s
Jun  6 08:24:36.031: INFO: Pod "exec-volume-test-dynamicpv-9kbf": Phase="Pending", Reason="", readiness=false. Elapsed: 13.121720196s
Jun  6 08:24:38.192: INFO: Pod "exec-volume-test-dynamicpv-9kbf": Phase="Pending", Reason="", readiness=false. Elapsed: 15.282338922s
Jun  6 08:24:40.351: INFO: Pod "exec-volume-test-dynamicpv-9kbf": Phase="Pending", Reason="", readiness=false. Elapsed: 17.441659399s
Jun  6 08:24:42.511: INFO: Pod "exec-volume-test-dynamicpv-9kbf": Phase="Pending", Reason="", readiness=false. Elapsed: 19.60158959s
Jun  6 08:24:44.671: INFO: Pod "exec-volume-test-dynamicpv-9kbf": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.760936686s
STEP: Saw pod success
Jun  6 08:24:44.671: INFO: Pod "exec-volume-test-dynamicpv-9kbf" satisfied condition "Succeeded or Failed"
Jun  6 08:24:44.829: INFO: Trying to get logs from node ip-172-20-53-171.ap-northeast-2.compute.internal pod exec-volume-test-dynamicpv-9kbf container exec-container-dynamicpv-9kbf: <nil>
STEP: delete the pod
Jun  6 08:24:45.203: INFO: Waiting for pod exec-volume-test-dynamicpv-9kbf to disappear
Jun  6 08:24:45.362: INFO: Pod exec-volume-test-dynamicpv-9kbf no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-9kbf
Jun  6 08:24:45.362: INFO: Deleting pod "exec-volume-test-dynamicpv-9kbf" in namespace "volume-1376"
... skipping 53 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Q9ZXkT72D/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Q9ZXkT72D/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.Q9ZXkT72D/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.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 59 lines ...
Jun  6 08:24:54.098: INFO: Pod aws-client still exists
Jun  6 08:24:55.937: INFO: Waiting for pod aws-client to disappear
Jun  6 08:24:56.097: INFO: Pod aws-client still exists
Jun  6 08:24:57.938: INFO: Waiting for pod aws-client to disappear
Jun  6 08:24:58.100: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun  6 08:24:58.877: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-00ac21d97591035fd", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00ac21d97591035fd is currently attached to i-0a4f9cf0993c78da0
	status code: 400, request id: c6728c94-7bfe-4f9c-92ae-98b16877b28b
Jun  6 08:25:04.646: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-00ac21d97591035fd".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  6 08:25:04.646: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-4956" for this suite.
... skipping 58 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  6 08:24:33.287: 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.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun  6 08:24:34.067: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  6 08:24:34.067: INFO: Creating resource for dynamic PV
Jun  6 08:24:34.067: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4573lgmlh
STEP: creating a claim
Jun  6 08:24:34.225: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-gjdr
STEP: Checking for subpath error in container status
Jun  6 08:24:53.011: INFO: Deleting pod "pod-subpath-test-dynamicpv-gjdr" in namespace "provisioning-4573"
Jun  6 08:24:53.169: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-gjdr" to be fully deleted
STEP: Deleting pod
Jun  6 08:25:03.481: INFO: Deleting pod "pod-subpath-test-dynamicpv-gjdr" in namespace "provisioning-4573"
STEP: Deleting pvc
Jun  6 08:25:03.949: INFO: Deleting PersistentVolumeClaim "aws877tz"
... skipping 11 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Q9ZXkT72D/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Q9ZXkT72D/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.Q9ZXkT72D/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.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volume-expand
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volume-expand
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 6 lines ...
Jun  6 08:24:38.845: INFO: Creating resource for dynamic PV
Jun  6 08:24:38.845: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-3800-e2e-sczlpt5
STEP: creating a claim
STEP: Expanding non-expandable pvc
Jun  6 08:24:39.334: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun  6 08:24:39.658: INFO: Error updating pvc ebs.csi.aws.com2p8f9: PersistentVolumeClaim "ebs.csi.aws.com2p8f9" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3800-e2e-sczlpt5",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 30 lines ...
Jun  6 08:24:55.796: INFO: Creating resource for dynamic PV
Jun  6 08:24:55.796: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-4982zlcbl
STEP: creating a claim
STEP: Expanding non-expandable pvc
Jun  6 08:24:56.280: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun  6 08:24:56.595: INFO: Error updating pvc aws2fsmh: PersistentVolumeClaim "aws2fsmh" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4982zlcbl",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun  6 08:25:27.228: INFO: Error updating pvc aws2fsmh: PersistentVolumeClaim "aws2fsmh" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 32 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  6 08:25:00.446: 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.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  6 08:25:01.239: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  6 08:25:02.231: INFO: Successfully created a new PD: "aws://ap-northeast-2a/vol-0f6b71528cac6162c".
Jun  6 08:25:02.231: INFO: Creating resource for pre-provisioned PV
Jun  6 08:25:02.231: INFO: Creating PVC and PV
... skipping 3 lines ...
Jun  6 08:25:02.787: INFO: PersistentVolumeClaim pvc-8gkjw found but phase is Pending instead of Bound.
Jun  6 08:25:04.943: INFO: PersistentVolumeClaim pvc-8gkjw found but phase is Pending instead of Bound.
Jun  6 08:25:07.098: INFO: PersistentVolumeClaim pvc-8gkjw found and phase=Bound (4.465036853s)
Jun  6 08:25:07.098: INFO: Waiting up to 3m0s for PersistentVolume aws-lrj8w to have phase Bound
Jun  6 08:25:07.255: INFO: PersistentVolume aws-lrj8w found and phase=Bound (156.923338ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  6 08:25:10.201: INFO: Deleting pod "pod-ec4bcda8-209a-44ae-a142-ab7e2336fce3" in namespace "volumemode-7145"
Jun  6 08:25:10.356: INFO: Wait up to 5m0s for pod "pod-ec4bcda8-209a-44ae-a142-ab7e2336fce3" to be fully deleted
STEP: Deleting pv and pvc
Jun  6 08:25:18.666: INFO: Deleting PersistentVolumeClaim "pvc-8gkjw"
Jun  6 08:25:18.821: INFO: Deleting PersistentVolume "aws-lrj8w"
Jun  6 08:25:19.231: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0f6b71528cac6162c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f6b71528cac6162c is currently attached to i-0a4f9cf0993c78da0
	status code: 400, request id: 399b4955-337c-4347-be7f-cbbceb1d85b0
Jun  6 08:25:25.018: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0f6b71528cac6162c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f6b71528cac6162c is currently attached to i-0a4f9cf0993c78da0
	status code: 400, request id: a3b1afe2-9fa5-4c66-ba98-5b0f0d1e3254
Jun  6 08:25:30.817: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-0f6b71528cac6162c".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  6 08:25:30.817: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-7145" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Q9ZXkT72D/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Q9ZXkT72D/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
    /tmp/kops.Q9ZXkT72D/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.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Inline-volume (ext3)] volumes
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  6 08:25:31.134: INFO: Driver aws doesn't support ext3 -- skipping
[AfterEach] [Testpattern: Inline-volume (ext3)] volumes
... skipping 69 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Q9ZXkT72D/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Q9ZXkT72D/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.Q9ZXkT72D/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.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 148 lines ...
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  6 08:25:34.356: 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.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Jun  6 08:25:35.309: INFO: found topology map[topology.kubernetes.io/zone:ap-northeast-2a]
Jun  6 08:25:35.309: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  6 08:25:35.309: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Q9ZXkT72D/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Q9ZXkT72D/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (delayed binding)] topology
    /tmp/kops.Q9ZXkT72D/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.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 106 lines ...
Jun  6 08:24:31.573: INFO: Creating resource for dynamic PV
Jun  6 08:24:31.573: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4890w6xnp
STEP: creating a claim
Jun  6 08:24:31.737: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-4890
Jun  6 08:24:32.238: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-4890" in namespace "provisioning-4890" to be "Succeeded or Failed"
Jun  6 08:24:32.402: INFO: Pod "volume-prep-provisioning-4890": Phase="Pending", Reason="", readiness=false. Elapsed: 163.366801ms
Jun  6 08:24:34.567: INFO: Pod "volume-prep-provisioning-4890": Phase="Pending", Reason="", readiness=false. Elapsed: 2.328321797s
Jun  6 08:24:36.730: INFO: Pod "volume-prep-provisioning-4890": Phase="Pending", Reason="", readiness=false. Elapsed: 4.491773872s
Jun  6 08:24:38.895: INFO: Pod "volume-prep-provisioning-4890": Phase="Pending", Reason="", readiness=false. Elapsed: 6.656458013s
Jun  6 08:24:41.058: INFO: Pod "volume-prep-provisioning-4890": Phase="Pending", Reason="", readiness=false. Elapsed: 8.82008952s
Jun  6 08:24:43.228: INFO: Pod "volume-prep-provisioning-4890": Phase="Pending", Reason="", readiness=false. Elapsed: 10.989203869s
Jun  6 08:24:45.391: INFO: Pod "volume-prep-provisioning-4890": Phase="Pending", Reason="", readiness=false. Elapsed: 13.153016817s
Jun  6 08:24:47.555: INFO: Pod "volume-prep-provisioning-4890": Phase="Pending", Reason="", readiness=false. Elapsed: 15.316943627s
Jun  6 08:24:49.719: INFO: Pod "volume-prep-provisioning-4890": Phase="Succeeded", Reason="", readiness=false. Elapsed: 17.480957618s
STEP: Saw pod success
Jun  6 08:24:49.719: INFO: Pod "volume-prep-provisioning-4890" satisfied condition "Succeeded or Failed"
Jun  6 08:24:49.719: INFO: Deleting pod "volume-prep-provisioning-4890" in namespace "provisioning-4890"
Jun  6 08:24:49.891: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-4890" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-dkcp
STEP: Checking for subpath error in container status
Jun  6 08:25:24.554: INFO: Deleting pod "pod-subpath-test-dynamicpv-dkcp" in namespace "provisioning-4890"
Jun  6 08:25:24.723: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-dkcp" to be fully deleted
STEP: Deleting pod
Jun  6 08:25:24.887: INFO: Deleting pod "pod-subpath-test-dynamicpv-dkcp" in namespace "provisioning-4890"
STEP: Deleting pvc
Jun  6 08:25:25.379: INFO: Deleting PersistentVolumeClaim "awsrmxvx"
... skipping 292 lines ...
Jun  6 08:25:11.939: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-7643-e2e-scpc8lv
STEP: creating a claim
Jun  6 08:25:12.107: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-tsxp
STEP: Creating a pod to test exec-volume-test
Jun  6 08:25:12.596: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-tsxp" in namespace "volume-7643" to be "Succeeded or Failed"
Jun  6 08:25:12.757: INFO: Pod "exec-volume-test-dynamicpv-tsxp": Phase="Pending", Reason="", readiness=false. Elapsed: 161.431931ms
Jun  6 08:25:14.923: INFO: Pod "exec-volume-test-dynamicpv-tsxp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.327347941s
Jun  6 08:25:17.096: INFO: Pod "exec-volume-test-dynamicpv-tsxp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.500407666s
Jun  6 08:25:19.261: INFO: Pod "exec-volume-test-dynamicpv-tsxp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.665578275s
Jun  6 08:25:21.423: INFO: Pod "exec-volume-test-dynamicpv-tsxp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.827550288s
Jun  6 08:25:23.586: INFO: Pod "exec-volume-test-dynamicpv-tsxp": Phase="Pending", Reason="", readiness=false. Elapsed: 10.989988421s
Jun  6 08:25:25.750: INFO: Pod "exec-volume-test-dynamicpv-tsxp": Phase="Pending", Reason="", readiness=false. Elapsed: 13.15444221s
Jun  6 08:25:27.912: INFO: Pod "exec-volume-test-dynamicpv-tsxp": Phase="Pending", Reason="", readiness=false. Elapsed: 15.316480007s
Jun  6 08:25:30.075: INFO: Pod "exec-volume-test-dynamicpv-tsxp": Phase="Pending", Reason="", readiness=false. Elapsed: 17.479202481s
Jun  6 08:25:32.237: INFO: Pod "exec-volume-test-dynamicpv-tsxp": Phase="Pending", Reason="", readiness=false. Elapsed: 19.641047147s
Jun  6 08:25:34.399: INFO: Pod "exec-volume-test-dynamicpv-tsxp": Phase="Pending", Reason="", readiness=false. Elapsed: 21.803445113s
Jun  6 08:25:36.561: INFO: Pod "exec-volume-test-dynamicpv-tsxp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.965248653s
STEP: Saw pod success
Jun  6 08:25:36.561: INFO: Pod "exec-volume-test-dynamicpv-tsxp" satisfied condition "Succeeded or Failed"
Jun  6 08:25:36.723: INFO: Trying to get logs from node ip-172-20-47-232.ap-northeast-2.compute.internal pod exec-volume-test-dynamicpv-tsxp container exec-container-dynamicpv-tsxp: <nil>
STEP: delete the pod
Jun  6 08:25:37.056: INFO: Waiting for pod exec-volume-test-dynamicpv-tsxp to disappear
Jun  6 08:25:37.224: INFO: Pod exec-volume-test-dynamicpv-tsxp no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-tsxp
Jun  6 08:25:37.224: INFO: Deleting pod "exec-volume-test-dynamicpv-tsxp" in namespace "volume-7643"
... skipping 207 lines ...
Jun  6 08:25:55.246: INFO: Pod aws-client still exists
Jun  6 08:25:57.084: INFO: Waiting for pod aws-client to disappear
Jun  6 08:25:57.248: INFO: Pod aws-client still exists
Jun  6 08:25:59.083: INFO: Waiting for pod aws-client to disappear
Jun  6 08:25:59.243: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun  6 08:26:00.035: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-06b72149ce26f8dc1", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-06b72149ce26f8dc1 is currently attached to i-0d09dc59d79b0c8d5
	status code: 400, request id: a88b7f5d-1ba0-4984-9e8f-ec2de4a4f2e3
Jun  6 08:26:05.826: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-06b72149ce26f8dc1".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  6 08:26:05.826: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-7668" for this suite.
... skipping 14 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  6 08:25:32.228: 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.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun  6 08:25:33.002: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  6 08:25:33.002: INFO: Creating resource for dynamic PV
Jun  6 08:25:33.002: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-38777t7q2
STEP: creating a claim
Jun  6 08:25:33.157: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-zmj8
STEP: Checking for subpath error in container status
Jun  6 08:25:45.940: INFO: Deleting pod "pod-subpath-test-dynamicpv-zmj8" in namespace "provisioning-3877"
Jun  6 08:25:46.097: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-zmj8" to be fully deleted
STEP: Deleting pod
Jun  6 08:26:00.407: INFO: Deleting pod "pod-subpath-test-dynamicpv-zmj8" in namespace "provisioning-3877"
STEP: Deleting pvc
Jun  6 08:26:00.872: INFO: Deleting PersistentVolumeClaim "aws2cfb9"
... skipping 11 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Q9ZXkT72D/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Q9ZXkT72D/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath file is outside the volume [Slow][LinuxOnly]
      /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow]
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  6 08:26:06.814: INFO: Driver "ebs.csi.aws.com" does not support volume type "PreprovisionedPV" - skipping
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow]
... skipping 136 lines ...
Jun  6 08:25:27.758: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  6 08:25:28.792: INFO: Successfully created a new PD: "aws://ap-northeast-2a/vol-05d2dd9fd447d3e8a".
Jun  6 08:25:28.792: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-2vr4
STEP: Creating a pod to test exec-volume-test
Jun  6 08:25:28.955: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-2vr4" in namespace "volume-9873" to be "Succeeded or Failed"
Jun  6 08:25:29.113: INFO: Pod "exec-volume-test-inlinevolume-2vr4": Phase="Pending", Reason="", readiness=false. Elapsed: 157.395503ms
Jun  6 08:25:31.271: INFO: Pod "exec-volume-test-inlinevolume-2vr4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.315727815s
Jun  6 08:25:33.430: INFO: Pod "exec-volume-test-inlinevolume-2vr4": Phase="Pending", Reason="", readiness=false. Elapsed: 4.474017751s
Jun  6 08:25:35.587: INFO: Pod "exec-volume-test-inlinevolume-2vr4": Phase="Pending", Reason="", readiness=false. Elapsed: 6.631812646s
Jun  6 08:25:37.745: INFO: Pod "exec-volume-test-inlinevolume-2vr4": Phase="Pending", Reason="", readiness=false. Elapsed: 8.789370607s
Jun  6 08:25:39.902: INFO: Pod "exec-volume-test-inlinevolume-2vr4": Phase="Pending", Reason="", readiness=false. Elapsed: 10.946806342s
Jun  6 08:25:42.061: INFO: Pod "exec-volume-test-inlinevolume-2vr4": Phase="Pending", Reason="", readiness=false. Elapsed: 13.105397952s
Jun  6 08:25:44.219: INFO: Pod "exec-volume-test-inlinevolume-2vr4": Phase="Pending", Reason="", readiness=false. Elapsed: 15.263564625s
Jun  6 08:25:46.377: INFO: Pod "exec-volume-test-inlinevolume-2vr4": Phase="Pending", Reason="", readiness=false. Elapsed: 17.421132501s
Jun  6 08:25:48.534: INFO: Pod "exec-volume-test-inlinevolume-2vr4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.578458865s
STEP: Saw pod success
Jun  6 08:25:48.534: INFO: Pod "exec-volume-test-inlinevolume-2vr4" satisfied condition "Succeeded or Failed"
Jun  6 08:25:48.692: INFO: Trying to get logs from node ip-172-20-33-48.ap-northeast-2.compute.internal pod exec-volume-test-inlinevolume-2vr4 container exec-container-inlinevolume-2vr4: <nil>
STEP: delete the pod
Jun  6 08:25:49.025: INFO: Waiting for pod exec-volume-test-inlinevolume-2vr4 to disappear
Jun  6 08:25:49.182: INFO: Pod exec-volume-test-inlinevolume-2vr4 no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-2vr4
Jun  6 08:25:49.182: INFO: Deleting pod "exec-volume-test-inlinevolume-2vr4" in namespace "volume-9873"
Jun  6 08:25:49.590: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-05d2dd9fd447d3e8a", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05d2dd9fd447d3e8a is currently attached to i-0a4f9cf0993c78da0
	status code: 400, request id: 6ac4f6d8-f2ba-4e87-ba46-e72201e55ee3
Jun  6 08:25:55.339: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-05d2dd9fd447d3e8a", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05d2dd9fd447d3e8a is currently attached to i-0a4f9cf0993c78da0
	status code: 400, request id: eeb670c7-f298-4ccf-8749-c03e4a9cdb5c
Jun  6 08:26:01.166: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-05d2dd9fd447d3e8a", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05d2dd9fd447d3e8a is currently attached to i-0a4f9cf0993c78da0
	status code: 400, request id: 2b4a33c6-1e01-471b-a85d-6b5fb0a8afb2
Jun  6 08:26:06.981: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-05d2dd9fd447d3e8a".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  6 08:26:06.981: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-9873" for this suite.
... skipping 145 lines ...
Jun  6 08:25:42.525: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-488bbjpc
STEP: creating a claim
Jun  6 08:25:42.689: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Jun  6 08:25:43.018: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun  6 08:25:43.349: INFO: Error updating pvc awsgznvz: PersistentVolumeClaim "awsgznvz" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-488bbjpc",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun  6 08:26:14.015: INFO: Error updating pvc awsgznvz: PersistentVolumeClaim "awsgznvz" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 431 lines ...
Jun  6 08:24:57.987: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-73952p6pb
STEP: creating a claim
Jun  6 08:24:58.146: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-vlk2
STEP: Creating a pod to test subpath
Jun  6 08:24:58.627: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-vlk2" in namespace "provisioning-7395" to be "Succeeded or Failed"
Jun  6 08:24:58.785: INFO: Pod "pod-subpath-test-dynamicpv-vlk2": Phase="Pending", Reason="", readiness=false. Elapsed: 158.309024ms
Jun  6 08:25:00.954: INFO: Pod "pod-subpath-test-dynamicpv-vlk2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.327216303s
Jun  6 08:25:03.116: INFO: Pod "pod-subpath-test-dynamicpv-vlk2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.488969271s
Jun  6 08:25:05.275: INFO: Pod "pod-subpath-test-dynamicpv-vlk2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.64811501s
Jun  6 08:25:07.434: INFO: Pod "pod-subpath-test-dynamicpv-vlk2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.806897548s
Jun  6 08:25:09.592: INFO: Pod "pod-subpath-test-dynamicpv-vlk2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.965600494s
Jun  6 08:25:11.751: INFO: Pod "pod-subpath-test-dynamicpv-vlk2": Phase="Pending", Reason="", readiness=false. Elapsed: 13.124003343s
Jun  6 08:25:13.909: INFO: Pod "pod-subpath-test-dynamicpv-vlk2": Phase="Pending", Reason="", readiness=false. Elapsed: 15.282413446s
Jun  6 08:25:16.068: INFO: Pod "pod-subpath-test-dynamicpv-vlk2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 17.441460888s
STEP: Saw pod success
Jun  6 08:25:16.068: INFO: Pod "pod-subpath-test-dynamicpv-vlk2" satisfied condition "Succeeded or Failed"
Jun  6 08:25:16.226: INFO: Trying to get logs from node ip-172-20-33-48.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-vlk2 container test-container-subpath-dynamicpv-vlk2: <nil>
STEP: delete the pod
Jun  6 08:25:16.563: INFO: Waiting for pod pod-subpath-test-dynamicpv-vlk2 to disappear
Jun  6 08:25:16.721: INFO: Pod pod-subpath-test-dynamicpv-vlk2 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-vlk2
Jun  6 08:25:16.721: INFO: Deleting pod "pod-subpath-test-dynamicpv-vlk2" in namespace "provisioning-7395"
STEP: Creating pod pod-subpath-test-dynamicpv-vlk2
STEP: Creating a pod to test subpath
Jun  6 08:25:17.038: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-vlk2" in namespace "provisioning-7395" to be "Succeeded or Failed"
Jun  6 08:25:17.198: INFO: Pod "pod-subpath-test-dynamicpv-vlk2": Phase="Pending", Reason="", readiness=false. Elapsed: 159.476466ms
Jun  6 08:25:19.356: INFO: Pod "pod-subpath-test-dynamicpv-vlk2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.317721363s
Jun  6 08:25:21.515: INFO: Pod "pod-subpath-test-dynamicpv-vlk2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.476315349s
Jun  6 08:25:23.674: INFO: Pod "pod-subpath-test-dynamicpv-vlk2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.635891738s
Jun  6 08:25:25.832: INFO: Pod "pod-subpath-test-dynamicpv-vlk2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.794230423s
Jun  6 08:25:27.994: INFO: Pod "pod-subpath-test-dynamicpv-vlk2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.956212201s
... skipping 6 lines ...
Jun  6 08:25:43.108: INFO: Pod "pod-subpath-test-dynamicpv-vlk2": Phase="Pending", Reason="", readiness=false. Elapsed: 26.070014021s
Jun  6 08:25:45.266: INFO: Pod "pod-subpath-test-dynamicpv-vlk2": Phase="Pending", Reason="", readiness=false. Elapsed: 28.228172546s
Jun  6 08:25:47.424: INFO: Pod "pod-subpath-test-dynamicpv-vlk2": Phase="Pending", Reason="", readiness=false. Elapsed: 30.385982211s
Jun  6 08:25:49.584: INFO: Pod "pod-subpath-test-dynamicpv-vlk2": Phase="Pending", Reason="", readiness=false. Elapsed: 32.545498544s
Jun  6 08:25:51.743: INFO: Pod "pod-subpath-test-dynamicpv-vlk2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.704704119s
STEP: Saw pod success
Jun  6 08:25:51.743: INFO: Pod "pod-subpath-test-dynamicpv-vlk2" satisfied condition "Succeeded or Failed"
Jun  6 08:25:51.901: INFO: Trying to get logs from node ip-172-20-47-232.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-vlk2 container test-container-subpath-dynamicpv-vlk2: <nil>
STEP: delete the pod
Jun  6 08:25:52.225: INFO: Waiting for pod pod-subpath-test-dynamicpv-vlk2 to disappear
Jun  6 08:25:52.383: INFO: Pod pod-subpath-test-dynamicpv-vlk2 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-vlk2
Jun  6 08:25:52.383: INFO: Deleting pod "pod-subpath-test-dynamicpv-vlk2" in namespace "provisioning-7395"
... skipping 381 lines ...
Jun  6 08:25:51.643: INFO: PersistentVolumeClaim pvc-b4htv found but phase is Pending instead of Bound.
Jun  6 08:25:53.813: INFO: PersistentVolumeClaim pvc-b4htv found and phase=Bound (6.667787098s)
Jun  6 08:25:53.813: INFO: Waiting up to 3m0s for PersistentVolume aws-j5dxs to have phase Bound
Jun  6 08:25:53.977: INFO: PersistentVolume aws-j5dxs found and phase=Bound (163.926656ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-w4cl
STEP: Creating a pod to test exec-volume-test
Jun  6 08:25:54.472: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-w4cl" in namespace "volume-6225" to be "Succeeded or Failed"
Jun  6 08:25:54.636: INFO: Pod "exec-volume-test-preprovisionedpv-w4cl": Phase="Pending", Reason="", readiness=false. Elapsed: 164.123325ms
Jun  6 08:25:56.802: INFO: Pod "exec-volume-test-preprovisionedpv-w4cl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.33046813s
Jun  6 08:25:58.975: INFO: Pod "exec-volume-test-preprovisionedpv-w4cl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.502980768s
Jun  6 08:26:01.139: INFO: Pod "exec-volume-test-preprovisionedpv-w4cl": Phase="Pending", Reason="", readiness=false. Elapsed: 6.667367407s
Jun  6 08:26:03.304: INFO: Pod "exec-volume-test-preprovisionedpv-w4cl": Phase="Pending", Reason="", readiness=false. Elapsed: 8.831909917s
Jun  6 08:26:05.469: INFO: Pod "exec-volume-test-preprovisionedpv-w4cl": Phase="Pending", Reason="", readiness=false. Elapsed: 10.997197238s
Jun  6 08:26:07.634: INFO: Pod "exec-volume-test-preprovisionedpv-w4cl": Phase="Pending", Reason="", readiness=false. Elapsed: 13.162168138s
Jun  6 08:26:09.799: INFO: Pod "exec-volume-test-preprovisionedpv-w4cl": Phase="Pending", Reason="", readiness=false. Elapsed: 15.327228389s
Jun  6 08:26:11.968: INFO: Pod "exec-volume-test-preprovisionedpv-w4cl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 17.496108854s
STEP: Saw pod success
Jun  6 08:26:11.968: INFO: Pod "exec-volume-test-preprovisionedpv-w4cl" satisfied condition "Succeeded or Failed"
Jun  6 08:26:12.134: INFO: Trying to get logs from node ip-172-20-47-232.ap-northeast-2.compute.internal pod exec-volume-test-preprovisionedpv-w4cl container exec-container-preprovisionedpv-w4cl: <nil>
STEP: delete the pod
Jun  6 08:26:12.477: INFO: Waiting for pod exec-volume-test-preprovisionedpv-w4cl to disappear
Jun  6 08:26:12.641: INFO: Pod exec-volume-test-preprovisionedpv-w4cl no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-w4cl
Jun  6 08:26:12.641: INFO: Deleting pod "exec-volume-test-preprovisionedpv-w4cl" in namespace "volume-6225"
STEP: Deleting pv and pvc
Jun  6 08:26:12.805: INFO: Deleting PersistentVolumeClaim "pvc-b4htv"
Jun  6 08:26:12.973: INFO: Deleting PersistentVolume "aws-j5dxs"
Jun  6 08:26:13.444: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-04ce545ea7c9af694", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04ce545ea7c9af694 is currently attached to i-06d23c6e41a438965
	status code: 400, request id: 59698099-b078-43e4-86be-6b6a4ff84277
Jun  6 08:26:19.241: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-04ce545ea7c9af694", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04ce545ea7c9af694 is currently attached to i-06d23c6e41a438965
	status code: 400, request id: b01fd2e5-fda1-4ae2-ab01-23ded6a3bebc
Jun  6 08:26:25.032: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-04ce545ea7c9af694", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04ce545ea7c9af694 is currently attached to i-06d23c6e41a438965
	status code: 400, request id: 41d512d0-274d-4d10-99de-b45a79b83a88
Jun  6 08:26:30.796: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-04ce545ea7c9af694".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  6 08:26:30.796: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-6225" for this suite.
... skipping 80 lines ...
Jun  6 08:26:39.458: INFO: Waiting for pod aws-client to disappear
Jun  6 08:26:39.620: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun  6 08:26:39.620: INFO: Deleting PersistentVolumeClaim "pvc-j2df6"
Jun  6 08:26:39.784: INFO: Deleting PersistentVolume "aws-rbjnh"
Jun  6 08:26:40.741: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-08e0752295ad9ae54", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08e0752295ad9ae54 is currently attached to i-037bcb7083139f8fd
	status code: 400, request id: 3dc94888-b807-4c4b-aab5-9506b94ef0a3
Jun  6 08:26:46.519: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-08e0752295ad9ae54".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  6 08:26:46.519: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-2809" for this suite.
... skipping 236 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  6 08:26:09.573: 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.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun  6 08:26:10.377: INFO: Creating resource for dynamic PV
Jun  6 08:26:10.377: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1278-e2e-scf4t9l
STEP: creating a claim
Jun  6 08:26:10.538: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-2wj6
STEP: Checking for subpath error in container status
Jun  6 08:26:35.344: INFO: Deleting pod "pod-subpath-test-dynamicpv-2wj6" in namespace "provisioning-1278"
Jun  6 08:26:35.506: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-2wj6" to be fully deleted
STEP: Deleting pod
Jun  6 08:26:43.827: INFO: Deleting pod "pod-subpath-test-dynamicpv-2wj6" in namespace "provisioning-1278"
STEP: Deleting pvc
Jun  6 08:26:44.312: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comfb4rz"
... skipping 11 lines ...

• [SLOW TEST:51.042 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath file is outside the volume [Slow][LinuxOnly]
    /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 704 lines ...
Jun  6 08:24:55.648: INFO: Creating resource for dynamic PV
Jun  6 08:24:55.648: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-1756-e2e-sc6vb5r
STEP: creating a claim
Jun  6 08:24:55.809: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun  6 08:24:56.296: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-2knts" in namespace "snapshotting-1756" to be "Succeeded or Failed"
Jun  6 08:24:56.457: INFO: Pod "pvc-snapshottable-tester-2knts": Phase="Pending", Reason="", readiness=false. Elapsed: 160.756163ms
Jun  6 08:24:58.618: INFO: Pod "pvc-snapshottable-tester-2knts": Phase="Pending", Reason="", readiness=false. Elapsed: 2.321437324s
Jun  6 08:25:00.780: INFO: Pod "pvc-snapshottable-tester-2knts": Phase="Pending", Reason="", readiness=false. Elapsed: 4.483350028s
Jun  6 08:25:02.948: INFO: Pod "pvc-snapshottable-tester-2knts": Phase="Pending", Reason="", readiness=false. Elapsed: 6.651440356s
Jun  6 08:25:05.112: INFO: Pod "pvc-snapshottable-tester-2knts": Phase="Pending", Reason="", readiness=false. Elapsed: 8.815656883s
Jun  6 08:25:07.279: INFO: Pod "pvc-snapshottable-tester-2knts": Phase="Pending", Reason="", readiness=false. Elapsed: 10.982199292s
Jun  6 08:25:09.439: INFO: Pod "pvc-snapshottable-tester-2knts": Phase="Pending", Reason="", readiness=false. Elapsed: 13.142453181s
Jun  6 08:25:11.600: INFO: Pod "pvc-snapshottable-tester-2knts": Phase="Pending", Reason="", readiness=false. Elapsed: 15.303595181s
Jun  6 08:25:13.760: INFO: Pod "pvc-snapshottable-tester-2knts": Phase="Pending", Reason="", readiness=false. Elapsed: 17.463928642s
Jun  6 08:25:15.921: INFO: Pod "pvc-snapshottable-tester-2knts": Phase="Pending", Reason="", readiness=false. Elapsed: 19.624521315s
Jun  6 08:25:18.082: INFO: Pod "pvc-snapshottable-tester-2knts": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.785182068s
STEP: Saw pod success
Jun  6 08:25:18.082: INFO: Pod "pvc-snapshottable-tester-2knts" satisfied condition "Succeeded or Failed"
Jun  6 08:25:18.419: INFO: Pod pvc-snapshottable-tester-2knts has the following logs: 
Jun  6 08:25:18.419: INFO: Deleting pod "pvc-snapshottable-tester-2knts" in namespace "snapshotting-1756"
Jun  6 08:25:18.607: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-2knts" to be fully deleted
Jun  6 08:25:18.768: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.com4bvps] to have phase Bound
Jun  6 08:25:18.928: INFO: PersistentVolumeClaim ebs.csi.aws.com4bvps found and phase=Bound (160.455432ms)
STEP: [init] checking the claim
... skipping 51 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.Q9ZXkT72D/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 08:26:12.058: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-2ttln" in namespace "snapshotting-1756" to be "Succeeded or Failed"
Jun  6 08:26:12.220: INFO: Pod "pvc-snapshottable-data-tester-2ttln": Phase="Pending", Reason="", readiness=false. Elapsed: 161.8516ms
Jun  6 08:26:14.380: INFO: Pod "pvc-snapshottable-data-tester-2ttln": Phase="Pending", Reason="", readiness=false. Elapsed: 2.322586041s
Jun  6 08:26:16.542: INFO: Pod "pvc-snapshottable-data-tester-2ttln": Phase="Pending", Reason="", readiness=false. Elapsed: 4.483757859s
Jun  6 08:26:18.704: INFO: Pod "pvc-snapshottable-data-tester-2ttln": Phase="Pending", Reason="", readiness=false. Elapsed: 6.645824585s
Jun  6 08:26:20.865: INFO: Pod "pvc-snapshottable-data-tester-2ttln": Phase="Pending", Reason="", readiness=false. Elapsed: 8.807256089s
Jun  6 08:26:23.026: INFO: Pod "pvc-snapshottable-data-tester-2ttln": Phase="Pending", Reason="", readiness=false. Elapsed: 10.968470026s
... skipping 6 lines ...
Jun  6 08:26:38.173: INFO: Pod "pvc-snapshottable-data-tester-2ttln": Phase="Pending", Reason="", readiness=false. Elapsed: 26.115299543s
Jun  6 08:26:40.334: INFO: Pod "pvc-snapshottable-data-tester-2ttln": Phase="Pending", Reason="", readiness=false. Elapsed: 28.275965908s
Jun  6 08:26:42.498: INFO: Pod "pvc-snapshottable-data-tester-2ttln": Phase="Pending", Reason="", readiness=false. Elapsed: 30.440567682s
Jun  6 08:26:44.661: INFO: Pod "pvc-snapshottable-data-tester-2ttln": Phase="Pending", Reason="", readiness=false. Elapsed: 32.603617776s
Jun  6 08:26:46.823: INFO: Pod "pvc-snapshottable-data-tester-2ttln": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.765296452s
STEP: Saw pod success
Jun  6 08:26:46.823: INFO: Pod "pvc-snapshottable-data-tester-2ttln" satisfied condition "Succeeded or Failed"
Jun  6 08:26:47.146: INFO: Pod pvc-snapshottable-data-tester-2ttln has the following logs: 
Jun  6 08:26:47.146: INFO: Deleting pod "pvc-snapshottable-data-tester-2ttln" in namespace "snapshotting-1756"
Jun  6 08:26:47.314: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-2ttln" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun  6 08:26:58.126: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-1756 exec restored-pvc-tester-c7l2n --namespace=snapshotting-1756 -- cat /mnt/test/data'
... skipping 35 lines ...
Jun  6 08:27:51.995: INFO: At 2021-06-06 08:24:59 +0000 UTC - event for ebs.csi.aws.com4bvps: {ebs.csi.aws.com_ebs-csi-controller-7ffff4ddf5-j92lc_69bee2e3-2b35-4c00-9fcb-a394ed74016c } ProvisioningSucceeded: Successfully provisioned volume pvc-abaf0759-f6c0-419e-9a8c-7d371645718b
Jun  6 08:27:51.995: INFO: At 2021-06-06 08:25:14 +0000 UTC - event for pvc-snapshottable-tester-2knts: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-abaf0759-f6c0-419e-9a8c-7d371645718b" 
Jun  6 08:27:51.995: INFO: At 2021-06-06 08:25:16 +0000 UTC - event for pvc-snapshottable-tester-2knts: {kubelet ip-172-20-40-222.ap-northeast-2.compute.internal} Started: Started container volume-tester
Jun  6 08:27:51.995: INFO: At 2021-06-06 08:25:16 +0000 UTC - event for pvc-snapshottable-tester-2knts: {kubelet ip-172-20-40-222.ap-northeast-2.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" already present on machine
Jun  6 08:27:51.995: INFO: At 2021-06-06 08:25:16 +0000 UTC - event for pvc-snapshottable-tester-2knts: {kubelet ip-172-20-40-222.ap-northeast-2.compute.internal} Created: Created container volume-tester
Jun  6 08:27:51.995: INFO: At 2021-06-06 08:25:19 +0000 UTC - event for snapshot-xvtsh: {snapshot-controller } CreatingSnapshot: Waiting for a snapshot snapshotting-1756/snapshot-xvtsh to be created by the CSI driver.
Jun  6 08:27:51.995: INFO: At 2021-06-06 08:26:10 +0000 UTC - event for pre-provisioned-snapshot-024a6dfc-d93e-4738-9d99-477a38447be4: {snapshot-controller } SnapshotFinalizerError: Failed to check and update snapshot: snapshot controller failed to update snapshotting-1756/pre-provisioned-snapshot-024a6dfc-d93e-4738-9d99-477a38447be4 on API server: Operation cannot be fulfilled on volumesnapshots.snapshot.storage.k8s.io "pre-provisioned-snapshot-024a6dfc-d93e-4738-9d99-477a38447be4": the object has been modified; please apply your changes to the latest version and try again
Jun  6 08:27:51.995: INFO: At 2021-06-06 08:26:29 +0000 UTC - event for pvc-snapshottable-data-tester-2ttln: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-abaf0759-f6c0-419e-9a8c-7d371645718b" 
Jun  6 08:27:51.995: INFO: At 2021-06-06 08:26:44 +0000 UTC - event for pvc-snapshottable-data-tester-2ttln: {kubelet ip-172-20-47-232.ap-northeast-2.compute.internal} Created: Created container volume-tester
Jun  6 08:27:51.995: INFO: At 2021-06-06 08:26:44 +0000 UTC - event for pvc-snapshottable-data-tester-2ttln: {kubelet ip-172-20-47-232.ap-northeast-2.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" already present on machine
Jun  6 08:27:51.995: INFO: At 2021-06-06 08:26:44 +0000 UTC - event for pvc-snapshottable-data-tester-2ttln: {kubelet ip-172-20-47-232.ap-northeast-2.compute.internal} Started: Started container volume-tester
Jun  6 08:27:51.995: INFO: At 2021-06-06 08:26:47 +0000 UTC - event for pvc-vxbff: {ebs.csi.aws.com_ebs-csi-controller-7ffff4ddf5-j92lc_69bee2e3-2b35-4c00-9fcb-a394ed74016c } Provisioning: External provisioner is provisioning volume for claim "snapshotting-1756/pvc-vxbff"
Jun  6 08:27:51.995: INFO: At 2021-06-06 08:26:47 +0000 UTC - event for pvc-vxbff: {persistentvolume-controller } ExternalProvisioning: waiting for a volume to be created, either by external provisioner "ebs.csi.aws.com" or manually created by system administrator
... skipping 179 lines ...
    /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:108
      
      /tmp/kops.Q9ZXkT72D/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.Q9ZXkT72D/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-1756 exec restored-pvc-tester-c7l2n --namespace=snapshotting-1756 -- 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-1756 exec restored-pvc-tester-c7l2n --namespace=snapshotting-1756 -- 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.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:602
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
... skipping 186 lines ...
Jun  6 08:25:40.380: INFO: Creating resource for dynamic PV
Jun  6 08:25:40.380: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-2231-e2e-scwts47
STEP: creating a claim
Jun  6 08:25:40.544: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun  6 08:25:41.037: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-kw52j" in namespace "snapshotting-2231" to be "Succeeded or Failed"
Jun  6 08:25:41.199: INFO: Pod "pvc-snapshottable-tester-kw52j": Phase="Pending", Reason="", readiness=false. Elapsed: 161.247799ms
Jun  6 08:25:43.359: INFO: Pod "pvc-snapshottable-tester-kw52j": Phase="Pending", Reason="", readiness=false. Elapsed: 2.321363295s
Jun  6 08:25:45.520: INFO: Pod "pvc-snapshottable-tester-kw52j": Phase="Pending", Reason="", readiness=false. Elapsed: 4.482217546s
Jun  6 08:25:47.681: INFO: Pod "pvc-snapshottable-tester-kw52j": Phase="Pending", Reason="", readiness=false. Elapsed: 6.64351163s
Jun  6 08:25:49.842: INFO: Pod "pvc-snapshottable-tester-kw52j": Phase="Pending", Reason="", readiness=false. Elapsed: 8.804232759s
Jun  6 08:25:52.003: INFO: Pod "pvc-snapshottable-tester-kw52j": Phase="Pending", Reason="", readiness=false. Elapsed: 10.965720738s
Jun  6 08:25:54.164: INFO: Pod "pvc-snapshottable-tester-kw52j": Phase="Pending", Reason="", readiness=false. Elapsed: 13.126487231s
Jun  6 08:25:56.325: INFO: Pod "pvc-snapshottable-tester-kw52j": Phase="Succeeded", Reason="", readiness=false. Elapsed: 15.288174019s
STEP: Saw pod success
Jun  6 08:25:56.326: INFO: Pod "pvc-snapshottable-tester-kw52j" satisfied condition "Succeeded or Failed"
Jun  6 08:25:56.649: INFO: Pod pvc-snapshottable-tester-kw52j has the following logs: 
Jun  6 08:25:56.649: INFO: Deleting pod "pvc-snapshottable-tester-kw52j" in namespace "snapshotting-2231"
Jun  6 08:25:56.821: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-kw52j" to be fully deleted
Jun  6 08:25:56.983: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comdr92q] to have phase Bound
Jun  6 08:25:57.143: INFO: PersistentVolumeClaim ebs.csi.aws.comdr92q found and phase=Bound (160.300555ms)
STEP: [init] checking the claim
... skipping 37 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.Q9ZXkT72D/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 08:26:20.016: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-zjjk6" in namespace "snapshotting-2231" to be "Succeeded or Failed"
Jun  6 08:26:20.176: INFO: Pod "pvc-snapshottable-data-tester-zjjk6": Phase="Pending", Reason="", readiness=false. Elapsed: 159.907081ms
Jun  6 08:26:22.347: INFO: Pod "pvc-snapshottable-data-tester-zjjk6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.330853284s
Jun  6 08:26:24.507: INFO: Pod "pvc-snapshottable-data-tester-zjjk6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.491430643s
Jun  6 08:26:26.671: INFO: Pod "pvc-snapshottable-data-tester-zjjk6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.655407454s
Jun  6 08:26:28.832: INFO: Pod "pvc-snapshottable-data-tester-zjjk6": Phase="Pending", Reason="", readiness=false. Elapsed: 8.816705332s
Jun  6 08:26:30.993: INFO: Pod "pvc-snapshottable-data-tester-zjjk6": Phase="Pending", Reason="", readiness=false. Elapsed: 10.977041542s
Jun  6 08:26:33.153: INFO: Pod "pvc-snapshottable-data-tester-zjjk6": Phase="Pending", Reason="", readiness=false. Elapsed: 13.137529475s
Jun  6 08:26:35.316: INFO: Pod "pvc-snapshottable-data-tester-zjjk6": Phase="Pending", Reason="", readiness=false. Elapsed: 15.299872351s
Jun  6 08:26:37.477: INFO: Pod "pvc-snapshottable-data-tester-zjjk6": Phase="Pending", Reason="", readiness=false. Elapsed: 17.461462498s
Jun  6 08:26:39.638: INFO: Pod "pvc-snapshottable-data-tester-zjjk6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.622108014s
STEP: Saw pod success
Jun  6 08:26:39.638: INFO: Pod "pvc-snapshottable-data-tester-zjjk6" satisfied condition "Succeeded or Failed"
Jun  6 08:26:39.961: INFO: Pod pvc-snapshottable-data-tester-zjjk6 has the following logs: 
Jun  6 08:26:39.961: INFO: Deleting pod "pvc-snapshottable-data-tester-zjjk6" in namespace "snapshotting-2231"
Jun  6 08:26:40.130: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-zjjk6" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun  6 08:27:02.935: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-2231 exec restored-pvc-tester-ntjqg --namespace=snapshotting-2231 -- cat /mnt/test/data'
... skipping 29 lines ...
Jun  6 08:27:28.446: INFO: volumesnapshotcontents pre-provisioned-snapcontent-f8c0ad97-74cd-4fb6-999a-cb65992eacb3 has been found and is not deleted
Jun  6 08:27:29.609: INFO: volumesnapshotcontents pre-provisioned-snapcontent-f8c0ad97-74cd-4fb6-999a-cb65992eacb3 has been found and is not deleted
Jun  6 08:27:30.770: INFO: volumesnapshotcontents pre-provisioned-snapcontent-f8c0ad97-74cd-4fb6-999a-cb65992eacb3 has been found and is not deleted
Jun  6 08:27:31.932: INFO: volumesnapshotcontents pre-provisioned-snapcontent-f8c0ad97-74cd-4fb6-999a-cb65992eacb3 has been found and is not deleted
Jun  6 08:27:33.093: INFO: volumesnapshotcontents pre-provisioned-snapcontent-f8c0ad97-74cd-4fb6-999a-cb65992eacb3 has been found and is not deleted
Jun  6 08:27:34.255: INFO: volumesnapshotcontents pre-provisioned-snapcontent-f8c0ad97-74cd-4fb6-999a-cb65992eacb3 has been found and is not deleted
Jun  6 08:27:35.255: INFO: WaitUntil failed after reaching the timeout 30s
[AfterEach] volume snapshot controller
  /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:221
Jun  6 08:27:35.422: INFO: Pod restored-pvc-tester-ntjqg has the following logs: 
Jun  6 08:27:35.422: INFO: Deleting pod "restored-pvc-tester-ntjqg" in namespace "snapshotting-2231"
Jun  6 08:27:35.583: INFO: Wait up to 5m0s for pod "restored-pvc-tester-ntjqg" to be fully deleted
Jun  6 08:28:09.905: INFO: deleting claim "snapshotting-2231"/"pvc-4r8ls"
... skipping 155 lines ...
      /tmp/kops.Q9ZXkT72D/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/multivolume.go:134
------------------------------


Summarizing 1 Failure:

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

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


Ginkgo ran 1 suite in 10m17.50953367s
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 08:28:15.796414   26781 app.go:59] RunDir for this run: "/logs/artifacts/76f1d5fb-c69d-11eb-a95e-22b332769ebd"
I0606 08:28:15.796581   26781 app.go:90] ID for this run: "76f1d5fb-c69d-11eb-a95e-22b332769ebd"
I0606 08:28:15.796607   26781 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 08:28:15.812885   26787 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
... skipping 1479 lines ...