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

No Test Failures!


Error lines from build-log.txt

... skipping 510 lines ...
I0611 08:12:13.002980   13829 up.go:43] Cleaning up any leaked resources from previous cluster
I0611 08:12:13.003006   13829 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
I0611 08:12:13.023606   13835 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0611 08:12:13.023822   13835 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io" not found
W0611 08:12:13.528076   13829 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0611 08:12:13.528122   13829 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
I0611 08:12:13.544040   13845 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0611 08:12:13.544135   13845 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io" not found
I0611 08:12:14.060253   13829 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/06/11 08:12:14 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
I0611 08:12:14.070390   13829 http.go:37] curl https://ip.jsb.workers.dev
I0611 08:12:14.199869   13829 up.go:144] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops create cluster --name e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --cloud aws --kubernetes-version 1.21.0 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --networking calico --override=cluster.spec.cloudConfig.awsEBSCSIDriver.enabled=true --override=cluster.spec.snapshotController.enabled=true --override=cluster.spec.certManager.enabled=true --admin-access 34.122.58.218/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-northeast-2a --master-size c5.large
I0611 08:12:14.215414   13860 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0611 08:12:14.215550   13860 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I0611 08:12:14.268768   13860 create_cluster.go:728] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0611 08:12:14.856138   13860 new_cluster.go:1039]  Cloud Provider ID = aws
... skipping 40 lines ...

I0611 08:12:45.036081   13829 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
I0611 08:12:45.052820   13881 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0611 08:12:45.052950   13881 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io

W0611 08:12:46.571779   13881 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
W0611 08:12:56.603579   13881 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
W0611 08:13:06.648265   13881 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
W0611 08:13:16.677549   13881 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
W0611 08:13:26.714049   13881 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
W0611 08:13:36.756098   13881 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
W0611 08:13:46.792460   13881 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
W0611 08:13:56.829263   13881 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
W0611 08:14:06.858942   13881 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
W0611 08:14:16.904594   13881 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
W0611 08:14:26.933483   13881 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
W0611 08:14:36.971042   13881 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
W0611 08:14:47.004571   13881 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
W0611 08:14:57.049995   13881 validate_cluster.go:221] (will retry): cluster not yet healthy
W0611 08:15:07.071913   13881 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
W0611 08:15:17.103446   13881 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
W0611 08:15:27.132549   13881 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
W0611 08:15:37.169236   13881 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
W0611 08:15:47.199193   13881 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
W0611 08:15:57.247573   13881 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
W0611 08:16:07.279273   13881 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
W0611 08:16:17.313212   13881 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
W0611 08:16:27.360055   13881 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
W0611 08:16:37.392543   13881 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
W0611 08:16:47.453812   13881 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
W0611 08:16:57.484896   13881 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
W0611 08:17:07.538390   13881 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
W0611 08:17:17.587686   13881 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
W0611 08:17:27.632880   13881 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
W0611 08:17:37.666175   13881 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
W0611 08:17:47.712366   13881 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 14 lines ...
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-dmpxz				system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-dmpxz" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-mv98g				system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-mv98g" is pending
Pod	kube-system/ebs-csi-node-95tx2						system-node-critical pod "ebs-csi-node-95tx2" is pending
Pod	kube-system/ebs-csi-node-jzqpq						system-node-critical pod "ebs-csi-node-jzqpq" is pending
Pod	kube-system/kube-proxy-ip-172-20-42-74.ap-northeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-42-74.ap-northeast-2.compute.internal" is pending

Validation Failed
W0611 08:18:01.402857   13881 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 25 lines ...
Pod	kube-system/ebs-csi-node-r2n9j						system-node-critical pod "ebs-csi-node-r2n9j" is pending
Pod	kube-system/kube-proxy-ip-172-20-32-106.ap-northeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-32-106.ap-northeast-2.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-42-74.ap-northeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-42-74.ap-northeast-2.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-46-76.ap-northeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-46-76.ap-northeast-2.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-52-245.ap-northeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-52-245.ap-northeast-2.compute.internal" is pending

Validation Failed
W0611 08:18:14.042819   13881 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 16 lines ...
Pod	kube-system/cert-manager-webhook-7bbf67968-nm4jm	system-cluster-critical pod "cert-manager-webhook-7bbf67968-nm4jm" is pending
Pod	kube-system/ebs-csi-node-bxfj2				system-node-critical pod "ebs-csi-node-bxfj2" is pending
Pod	kube-system/ebs-csi-node-f46pt				system-node-critical pod "ebs-csi-node-f46pt" is pending
Pod	kube-system/ebs-csi-node-jzqpq				system-node-critical pod "ebs-csi-node-jzqpq" is pending
Pod	kube-system/ebs-csi-node-r2n9j				system-node-critical pod "ebs-csi-node-r2n9j" is pending

Validation Failed
W0611 08:18:26.700005   13881 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 15 lines ...
Pod	kube-system/cert-manager-cainjector-74d69756d5-lmkqk	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-lmkqk" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-nm4jm	system-cluster-critical pod "cert-manager-webhook-7bbf67968-nm4jm" is pending
Pod	kube-system/ebs-csi-node-bxfj2				system-node-critical pod "ebs-csi-node-bxfj2" is pending
Pod	kube-system/ebs-csi-node-f46pt				system-node-critical pod "ebs-csi-node-f46pt" is pending
Pod	kube-system/ebs-csi-node-r2n9j				system-node-critical pod "ebs-csi-node-r2n9j" is pending

Validation Failed
W0611 08:18:39.320858   13881 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-node-dxswp				system-node-critical pod "calico-node-dxswp" is not ready (calico-node)
Pod	kube-system/cert-manager-cainjector-74d69756d5-lmkqk	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-lmkqk" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-nm4jm	system-cluster-critical pod "cert-manager-webhook-7bbf67968-nm4jm" is pending

Validation Failed
W0611 08:18:51.870724   13881 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 52 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-autoscaler-6f594f4c58-dvw2w	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-dvw2w" is pending
Pod	kube-system/coredns-f45c4bf76-rhsgb		system-cluster-critical pod "coredns-f45c4bf76-rhsgb" is pending

Validation Failed
W0611 08:19:42.484609   13881 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 307 lines ...

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

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

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

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

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.XbNMA0Bbv/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.XbNMA0Bbv/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.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 172 lines ...
STEP: Creating a kubernetes client
Jun 11 08:23:11.091: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename volumemode
W0611 08:23:13.185682   27992 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Jun 11 08:23:13.185: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
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.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 11 08:23:13.504: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 11 08:23:13.504: INFO: Creating resource for dynamic PV
Jun 11 08:23:13.504: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-876fpgrz
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 11 08:23:22.628: INFO: Deleting pod "pod-d4e6180e-7e71-4d0b-b0f7-cca1c505a396" in namespace "volumemode-876"
Jun 11 08:23:22.789: INFO: Wait up to 5m0s for pod "pod-d4e6180e-7e71-4d0b-b0f7-cca1c505a396" to be fully deleted
STEP: Deleting pvc
Jun 11 08:23:35.425: INFO: Deleting PersistentVolumeClaim "awscpsdn"
Jun 11 08:23:35.586: INFO: Waiting up to 5m0s for PersistentVolume pvc-e5063fb5-8ef1-455c-bcbc-9a758fd73340 to get deleted
Jun 11 08:23:35.745: INFO: PersistentVolume pvc-e5063fb5-8ef1-455c-bcbc-9a758fd73340 found and phase=Released (159.104528ms)
... skipping 9 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.XbNMA0Bbv/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.XbNMA0Bbv/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (block volmode)] volumeMode
    /tmp/kops.XbNMA0Bbv/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.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] volume-expand
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] volume-expand
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 10 lines ...
Jun 11 08:23:12.197: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-2285mf7s9
STEP: creating a claim
Jun 11 08:23:12.360: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Jun 11 08:23:12.687: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 11 08:23:13.025: INFO: Error updating pvc awsq5ckj: PersistentVolumeClaim "awsq5ckj" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2285mf7s9",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun 11 08:23:43.689: INFO: Error updating pvc awsq5ckj: PersistentVolumeClaim "awsq5ckj" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 62 lines ...
Jun 11 08:23:12.622: INFO: Creating resource for dynamic PV
Jun 11 08:23:12.622: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-10606g2zs
STEP: creating a claim
STEP: Expanding non-expandable pvc
Jun 11 08:23:13.121: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 11 08:23:13.456: INFO: Error updating pvc aws7kj9j: PersistentVolumeClaim "aws7kj9j" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-10606g2zs",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun 11 08:23:44.130: INFO: Error updating pvc aws7kj9j: PersistentVolumeClaim "aws7kj9j" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 53 lines ...
STEP: Creating a kubernetes client
Jun 11 08:23:10.954: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename provisioning
W0611 08:23:11.939869   27905 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Jun 11 08:23:11.939: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly]
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun 11 08:23:12.254: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 11 08:23:12.254: INFO: Creating resource for dynamic PV
Jun 11 08:23:12.254: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7292qz4w6
STEP: creating a claim
Jun 11 08:23:12.413: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-l6s2
STEP: Checking for subpath error in container status
Jun 11 08:23:35.214: INFO: Deleting pod "pod-subpath-test-dynamicpv-l6s2" in namespace "provisioning-7292"
Jun 11 08:23:35.373: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-l6s2" to be fully deleted
STEP: Deleting pod
Jun 11 08:23:43.691: INFO: Deleting pod "pod-subpath-test-dynamicpv-l6s2" in namespace "provisioning-7292"
STEP: Deleting pvc
Jun 11 08:23:44.196: INFO: Deleting PersistentVolumeClaim "awspgvzk"
... skipping 11 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.XbNMA0Bbv/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.XbNMA0Bbv/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.XbNMA0Bbv/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.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 156 lines ...
Jun 11 08:23:12.296: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 11 08:23:13.261: INFO: Successfully created a new PD: "aws://ap-northeast-2a/vol-0fcf1742410d85f1c".
Jun 11 08:23:13.261: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-5cxf
STEP: Creating a pod to test exec-volume-test
Jun 11 08:23:13.426: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-5cxf" in namespace "volume-2605" to be "Succeeded or Failed"
Jun 11 08:23:13.581: INFO: Pod "exec-volume-test-inlinevolume-5cxf": Phase="Pending", Reason="", readiness=false. Elapsed: 155.31372ms
Jun 11 08:23:15.741: INFO: Pod "exec-volume-test-inlinevolume-5cxf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.314962775s
Jun 11 08:23:17.904: INFO: Pod "exec-volume-test-inlinevolume-5cxf": Phase="Pending", Reason="", readiness=false. Elapsed: 4.478264978s
Jun 11 08:23:20.076: INFO: Pod "exec-volume-test-inlinevolume-5cxf": Phase="Pending", Reason="", readiness=false. Elapsed: 6.65011653s
Jun 11 08:23:22.232: INFO: Pod "exec-volume-test-inlinevolume-5cxf": Phase="Pending", Reason="", readiness=false. Elapsed: 8.806590709s
Jun 11 08:23:24.390: INFO: Pod "exec-volume-test-inlinevolume-5cxf": Phase="Pending", Reason="", readiness=false. Elapsed: 10.963971995s
Jun 11 08:23:26.546: INFO: Pod "exec-volume-test-inlinevolume-5cxf": Phase="Pending", Reason="", readiness=false. Elapsed: 13.120006886s
Jun 11 08:23:28.703: INFO: Pod "exec-volume-test-inlinevolume-5cxf": Phase="Pending", Reason="", readiness=false. Elapsed: 15.276634694s
Jun 11 08:23:30.858: INFO: Pod "exec-volume-test-inlinevolume-5cxf": Phase="Pending", Reason="", readiness=false. Elapsed: 17.432479776s
Jun 11 08:23:33.015: INFO: Pod "exec-volume-test-inlinevolume-5cxf": Phase="Pending", Reason="", readiness=false. Elapsed: 19.58888478s
Jun 11 08:23:35.170: INFO: Pod "exec-volume-test-inlinevolume-5cxf": Phase="Pending", Reason="", readiness=false. Elapsed: 21.744443308s
Jun 11 08:23:37.326: INFO: Pod "exec-volume-test-inlinevolume-5cxf": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.899851942s
STEP: Saw pod success
Jun 11 08:23:37.326: INFO: Pod "exec-volume-test-inlinevolume-5cxf" satisfied condition "Succeeded or Failed"
Jun 11 08:23:37.481: INFO: Trying to get logs from node ip-172-20-32-106.ap-northeast-2.compute.internal pod exec-volume-test-inlinevolume-5cxf container exec-container-inlinevolume-5cxf: <nil>
STEP: delete the pod
Jun 11 08:23:37.820: INFO: Waiting for pod exec-volume-test-inlinevolume-5cxf to disappear
Jun 11 08:23:37.976: INFO: Pod exec-volume-test-inlinevolume-5cxf no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-5cxf
Jun 11 08:23:37.976: INFO: Deleting pod "exec-volume-test-inlinevolume-5cxf" in namespace "volume-2605"
Jun 11 08:23:38.402: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0fcf1742410d85f1c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0fcf1742410d85f1c is currently attached to i-02cb721efd2472d6a
	status code: 400, request id: a72f62b9-b525-4d5f-8a10-e18f3b78b4cc
Jun 11 08:23:44.210: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0fcf1742410d85f1c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0fcf1742410d85f1c is currently attached to i-02cb721efd2472d6a
	status code: 400, request id: 246ccf40-10bf-441f-bdce-f64b6b49044c
Jun 11 08:23:49.939: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0fcf1742410d85f1c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0fcf1742410d85f1c is currently attached to i-02cb721efd2472d6a
	status code: 400, request id: 2d124a6e-90e1-44b4-82d8-b587d64b88e5
Jun 11 08:23:55.749: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0fcf1742410d85f1c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0fcf1742410d85f1c is currently attached to i-02cb721efd2472d6a
	status code: 400, request id: 252e31f5-c771-4daf-9503-286b416d9cd4
Jun 11 08:24:01.553: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-0fcf1742410d85f1c".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 08:24:01.553: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-2605" for this suite.
... skipping 117 lines ...
Jun 11 08:23:13.556: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-5314n8kl6
STEP: creating a claim
Jun 11 08:23:13.717: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-8jfw
STEP: Creating a pod to test exec-volume-test
Jun 11 08:23:14.233: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-8jfw" in namespace "volume-5314" to be "Succeeded or Failed"
Jun 11 08:23:14.392: INFO: Pod "exec-volume-test-dynamicpv-8jfw": Phase="Pending", Reason="", readiness=false. Elapsed: 159.43398ms
Jun 11 08:23:16.553: INFO: Pod "exec-volume-test-dynamicpv-8jfw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.319816394s
Jun 11 08:23:18.713: INFO: Pod "exec-volume-test-dynamicpv-8jfw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.479782278s
Jun 11 08:23:20.873: INFO: Pod "exec-volume-test-dynamicpv-8jfw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.640547095s
Jun 11 08:23:23.033: INFO: Pod "exec-volume-test-dynamicpv-8jfw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.800145884s
Jun 11 08:23:25.193: INFO: Pod "exec-volume-test-dynamicpv-8jfw": Phase="Pending", Reason="", readiness=false. Elapsed: 10.960637703s
... skipping 3 lines ...
Jun 11 08:23:33.834: INFO: Pod "exec-volume-test-dynamicpv-8jfw": Phase="Pending", Reason="", readiness=false. Elapsed: 19.601528132s
Jun 11 08:23:35.994: INFO: Pod "exec-volume-test-dynamicpv-8jfw": Phase="Pending", Reason="", readiness=false. Elapsed: 21.761596472s
Jun 11 08:23:38.154: INFO: Pod "exec-volume-test-dynamicpv-8jfw": Phase="Pending", Reason="", readiness=false. Elapsed: 23.921125258s
Jun 11 08:23:40.314: INFO: Pod "exec-volume-test-dynamicpv-8jfw": Phase="Pending", Reason="", readiness=false. Elapsed: 26.081103888s
Jun 11 08:23:42.475: INFO: Pod "exec-volume-test-dynamicpv-8jfw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 28.2419324s
STEP: Saw pod success
Jun 11 08:23:42.475: INFO: Pod "exec-volume-test-dynamicpv-8jfw" satisfied condition "Succeeded or Failed"
Jun 11 08:23:42.635: INFO: Trying to get logs from node ip-172-20-46-76.ap-northeast-2.compute.internal pod exec-volume-test-dynamicpv-8jfw container exec-container-dynamicpv-8jfw: <nil>
STEP: delete the pod
Jun 11 08:23:43.001: INFO: Waiting for pod exec-volume-test-dynamicpv-8jfw to disappear
Jun 11 08:23:43.160: INFO: Pod exec-volume-test-dynamicpv-8jfw no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-8jfw
Jun 11 08:23:43.160: INFO: Deleting pod "exec-volume-test-dynamicpv-8jfw" in namespace "volume-5314"
... skipping 38 lines ...
Jun 11 08:23:14.898: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4231-e2e-scbvbp5
STEP: creating a claim
Jun 11 08:23:15.059: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-2kpp
STEP: Creating a pod to test subpath
Jun 11 08:23:15.548: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-2kpp" in namespace "provisioning-4231" to be "Succeeded or Failed"
Jun 11 08:23:15.707: INFO: Pod "pod-subpath-test-dynamicpv-2kpp": Phase="Pending", Reason="", readiness=false. Elapsed: 158.938028ms
Jun 11 08:23:17.873: INFO: Pod "pod-subpath-test-dynamicpv-2kpp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.325309961s
Jun 11 08:23:20.073: INFO: Pod "pod-subpath-test-dynamicpv-2kpp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.52471926s
Jun 11 08:23:22.232: INFO: Pod "pod-subpath-test-dynamicpv-2kpp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.684644405s
Jun 11 08:23:24.394: INFO: Pod "pod-subpath-test-dynamicpv-2kpp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.84598898s
Jun 11 08:23:26.553: INFO: Pod "pod-subpath-test-dynamicpv-2kpp": Phase="Pending", Reason="", readiness=false. Elapsed: 11.005532943s
Jun 11 08:23:28.713: INFO: Pod "pod-subpath-test-dynamicpv-2kpp": Phase="Pending", Reason="", readiness=false. Elapsed: 13.164767725s
Jun 11 08:23:30.874: INFO: Pod "pod-subpath-test-dynamicpv-2kpp": Phase="Pending", Reason="", readiness=false. Elapsed: 15.325795148s
Jun 11 08:23:33.033: INFO: Pod "pod-subpath-test-dynamicpv-2kpp": Phase="Pending", Reason="", readiness=false. Elapsed: 17.484844593s
Jun 11 08:23:35.192: INFO: Pod "pod-subpath-test-dynamicpv-2kpp": Phase="Pending", Reason="", readiness=false. Elapsed: 19.644081985s
Jun 11 08:23:37.370: INFO: Pod "pod-subpath-test-dynamicpv-2kpp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.822142286s
STEP: Saw pod success
Jun 11 08:23:37.370: INFO: Pod "pod-subpath-test-dynamicpv-2kpp" satisfied condition "Succeeded or Failed"
Jun 11 08:23:37.529: INFO: Trying to get logs from node ip-172-20-32-106.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-2kpp container test-container-volume-dynamicpv-2kpp: <nil>
STEP: delete the pod
Jun 11 08:23:37.858: INFO: Waiting for pod pod-subpath-test-dynamicpv-2kpp to disappear
Jun 11 08:23:38.017: INFO: Pod pod-subpath-test-dynamicpv-2kpp no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-2kpp
Jun 11 08:23:38.017: INFO: Deleting pod "pod-subpath-test-dynamicpv-2kpp" in namespace "provisioning-4231"
... skipping 64 lines ...
Jun 11 08:23:14.125: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-2683-e2e-scj9t6b
STEP: creating a claim
Jun 11 08:23:14.290: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-phnh
STEP: Creating a pod to test exec-volume-test
Jun 11 08:23:14.783: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-phnh" in namespace "volume-2683" to be "Succeeded or Failed"
Jun 11 08:23:14.946: INFO: Pod "exec-volume-test-dynamicpv-phnh": Phase="Pending", Reason="", readiness=false. Elapsed: 162.961941ms
Jun 11 08:23:17.109: INFO: Pod "exec-volume-test-dynamicpv-phnh": Phase="Pending", Reason="", readiness=false. Elapsed: 2.326187447s
Jun 11 08:23:19.273: INFO: Pod "exec-volume-test-dynamicpv-phnh": Phase="Pending", Reason="", readiness=false. Elapsed: 4.489370871s
Jun 11 08:23:21.436: INFO: Pod "exec-volume-test-dynamicpv-phnh": Phase="Pending", Reason="", readiness=false. Elapsed: 6.652926343s
Jun 11 08:23:23.601: INFO: Pod "exec-volume-test-dynamicpv-phnh": Phase="Pending", Reason="", readiness=false. Elapsed: 8.817578231s
Jun 11 08:23:25.765: INFO: Pod "exec-volume-test-dynamicpv-phnh": Phase="Pending", Reason="", readiness=false. Elapsed: 10.981642626s
Jun 11 08:23:27.929: INFO: Pod "exec-volume-test-dynamicpv-phnh": Phase="Pending", Reason="", readiness=false. Elapsed: 13.145376355s
Jun 11 08:23:30.092: INFO: Pod "exec-volume-test-dynamicpv-phnh": Phase="Pending", Reason="", readiness=false. Elapsed: 15.309015702s
Jun 11 08:23:32.256: INFO: Pod "exec-volume-test-dynamicpv-phnh": Phase="Pending", Reason="", readiness=false. Elapsed: 17.472805407s
Jun 11 08:23:34.419: INFO: Pod "exec-volume-test-dynamicpv-phnh": Phase="Pending", Reason="", readiness=false. Elapsed: 19.636286207s
Jun 11 08:23:36.585: INFO: Pod "exec-volume-test-dynamicpv-phnh": Phase="Pending", Reason="", readiness=false. Elapsed: 21.802107729s
Jun 11 08:23:38.749: INFO: Pod "exec-volume-test-dynamicpv-phnh": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.965483566s
STEP: Saw pod success
Jun 11 08:23:38.749: INFO: Pod "exec-volume-test-dynamicpv-phnh" satisfied condition "Succeeded or Failed"
Jun 11 08:23:38.911: INFO: Trying to get logs from node ip-172-20-32-106.ap-northeast-2.compute.internal pod exec-volume-test-dynamicpv-phnh container exec-container-dynamicpv-phnh: <nil>
STEP: delete the pod
Jun 11 08:23:39.246: INFO: Waiting for pod exec-volume-test-dynamicpv-phnh to disappear
Jun 11 08:23:39.416: INFO: Pod exec-volume-test-dynamicpv-phnh no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-phnh
Jun 11 08:23:39.416: INFO: Deleting pod "exec-volume-test-dynamicpv-phnh" in namespace "volume-2683"
... skipping 34 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.XbNMA0Bbv/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.XbNMA0Bbv/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.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 13 lines ...
Jun 11 08:23:12.748: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2310-e2e-scz9mwv
STEP: creating a claim
Jun 11 08:23:12.911: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-dhn8
STEP: Creating a pod to test subpath
Jun 11 08:23:13.385: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-dhn8" in namespace "provisioning-2310" to be "Succeeded or Failed"
Jun 11 08:23:13.545: INFO: Pod "pod-subpath-test-dynamicpv-dhn8": Phase="Pending", Reason="", readiness=false. Elapsed: 159.62879ms
Jun 11 08:23:15.703: INFO: Pod "pod-subpath-test-dynamicpv-dhn8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.318053562s
Jun 11 08:23:17.862: INFO: Pod "pod-subpath-test-dynamicpv-dhn8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.477438324s
Jun 11 08:23:20.063: INFO: Pod "pod-subpath-test-dynamicpv-dhn8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.677522572s
Jun 11 08:23:22.220: INFO: Pod "pod-subpath-test-dynamicpv-dhn8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.835159497s
Jun 11 08:23:24.378: INFO: Pod "pod-subpath-test-dynamicpv-dhn8": Phase="Pending", Reason="", readiness=false. Elapsed: 10.992876239s
... skipping 2 lines ...
Jun 11 08:23:30.852: INFO: Pod "pod-subpath-test-dynamicpv-dhn8": Phase="Pending", Reason="", readiness=false. Elapsed: 17.467306747s
Jun 11 08:23:33.009: INFO: Pod "pod-subpath-test-dynamicpv-dhn8": Phase="Pending", Reason="", readiness=false. Elapsed: 19.624145347s
Jun 11 08:23:35.166: INFO: Pod "pod-subpath-test-dynamicpv-dhn8": Phase="Pending", Reason="", readiness=false. Elapsed: 21.78145626s
Jun 11 08:23:37.324: INFO: Pod "pod-subpath-test-dynamicpv-dhn8": Phase="Pending", Reason="", readiness=false. Elapsed: 23.938753354s
Jun 11 08:23:39.490: INFO: Pod "pod-subpath-test-dynamicpv-dhn8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.104658458s
STEP: Saw pod success
Jun 11 08:23:39.490: INFO: Pod "pod-subpath-test-dynamicpv-dhn8" satisfied condition "Succeeded or Failed"
Jun 11 08:23:39.648: INFO: Trying to get logs from node ip-172-20-52-245.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-dhn8 container test-container-subpath-dynamicpv-dhn8: <nil>
STEP: delete the pod
Jun 11 08:23:39.979: INFO: Waiting for pod pod-subpath-test-dynamicpv-dhn8 to disappear
Jun 11 08:23:40.135: INFO: Pod pod-subpath-test-dynamicpv-dhn8 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-dhn8
Jun 11 08:23:40.136: INFO: Deleting pod "pod-subpath-test-dynamicpv-dhn8" in namespace "provisioning-2310"
... skipping 87 lines ...
Jun 11 08:23:12.257: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7421-e2e-sc5d4ks
STEP: creating a claim
Jun 11 08:23:12.419: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-g5zt
STEP: Creating a pod to test subpath
Jun 11 08:23:12.904: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-g5zt" in namespace "provisioning-7421" to be "Succeeded or Failed"
Jun 11 08:23:13.068: INFO: Pod "pod-subpath-test-dynamicpv-g5zt": Phase="Pending", Reason="", readiness=false. Elapsed: 163.04134ms
Jun 11 08:23:15.229: INFO: Pod "pod-subpath-test-dynamicpv-g5zt": Phase="Pending", Reason="", readiness=false. Elapsed: 2.32456847s
Jun 11 08:23:17.391: INFO: Pod "pod-subpath-test-dynamicpv-g5zt": Phase="Pending", Reason="", readiness=false. Elapsed: 4.486228829s
Jun 11 08:23:19.553: INFO: Pod "pod-subpath-test-dynamicpv-g5zt": Phase="Pending", Reason="", readiness=false. Elapsed: 6.648050369s
Jun 11 08:23:21.719: INFO: Pod "pod-subpath-test-dynamicpv-g5zt": Phase="Pending", Reason="", readiness=false. Elapsed: 8.814488169s
Jun 11 08:23:23.880: INFO: Pod "pod-subpath-test-dynamicpv-g5zt": Phase="Pending", Reason="", readiness=false. Elapsed: 10.975690472s
... skipping 3 lines ...
Jun 11 08:23:32.531: INFO: Pod "pod-subpath-test-dynamicpv-g5zt": Phase="Pending", Reason="", readiness=false. Elapsed: 19.6261881s
Jun 11 08:23:34.692: INFO: Pod "pod-subpath-test-dynamicpv-g5zt": Phase="Pending", Reason="", readiness=false. Elapsed: 21.787241807s
Jun 11 08:23:36.856: INFO: Pod "pod-subpath-test-dynamicpv-g5zt": Phase="Pending", Reason="", readiness=false. Elapsed: 23.951471249s
Jun 11 08:23:39.017: INFO: Pod "pod-subpath-test-dynamicpv-g5zt": Phase="Pending", Reason="", readiness=false. Elapsed: 26.112932135s
Jun 11 08:23:41.179: INFO: Pod "pod-subpath-test-dynamicpv-g5zt": Phase="Succeeded", Reason="", readiness=false. Elapsed: 28.274289096s
STEP: Saw pod success
Jun 11 08:23:41.179: INFO: Pod "pod-subpath-test-dynamicpv-g5zt" satisfied condition "Succeeded or Failed"
Jun 11 08:23:41.339: INFO: Trying to get logs from node ip-172-20-46-76.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-g5zt container test-container-volume-dynamicpv-g5zt: <nil>
STEP: delete the pod
Jun 11 08:23:42.078: INFO: Waiting for pod pod-subpath-test-dynamicpv-g5zt to disappear
Jun 11 08:23:42.239: INFO: Pod pod-subpath-test-dynamicpv-g5zt no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-g5zt
Jun 11 08:23:42.239: INFO: Deleting pod "pod-subpath-test-dynamicpv-g5zt" in namespace "provisioning-7421"
... skipping 281 lines ...
Jun 11 08:23:13.707: INFO: Creating resource for dynamic PV
Jun 11 08:23:13.707: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4309g5d9p
STEP: creating a claim
Jun 11 08:23:13.867: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-4309
Jun 11 08:23:14.349: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-4309" in namespace "provisioning-4309" to be "Succeeded or Failed"
Jun 11 08:23:14.508: INFO: Pod "volume-prep-provisioning-4309": Phase="Pending", Reason="", readiness=false. Elapsed: 159.247605ms
Jun 11 08:23:16.675: INFO: Pod "volume-prep-provisioning-4309": Phase="Pending", Reason="", readiness=false. Elapsed: 2.32580983s
Jun 11 08:23:18.835: INFO: Pod "volume-prep-provisioning-4309": Phase="Pending", Reason="", readiness=false. Elapsed: 4.486681205s
Jun 11 08:23:20.995: INFO: Pod "volume-prep-provisioning-4309": Phase="Pending", Reason="", readiness=false. Elapsed: 6.64613792s
Jun 11 08:23:23.155: INFO: Pod "volume-prep-provisioning-4309": Phase="Pending", Reason="", readiness=false. Elapsed: 8.806460093s
Jun 11 08:23:25.316: INFO: Pod "volume-prep-provisioning-4309": Phase="Pending", Reason="", readiness=false. Elapsed: 10.966800626s
Jun 11 08:23:27.486: INFO: Pod "volume-prep-provisioning-4309": Phase="Pending", Reason="", readiness=false. Elapsed: 13.137049447s
Jun 11 08:23:29.645: INFO: Pod "volume-prep-provisioning-4309": Phase="Pending", Reason="", readiness=false. Elapsed: 15.296451995s
Jun 11 08:23:31.805: INFO: Pod "volume-prep-provisioning-4309": Phase="Pending", Reason="", readiness=false. Elapsed: 17.456624787s
Jun 11 08:23:33.966: INFO: Pod "volume-prep-provisioning-4309": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.617307463s
STEP: Saw pod success
Jun 11 08:23:33.966: INFO: Pod "volume-prep-provisioning-4309" satisfied condition "Succeeded or Failed"
Jun 11 08:23:33.966: INFO: Deleting pod "volume-prep-provisioning-4309" in namespace "provisioning-4309"
Jun 11 08:23:34.154: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-4309" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-mbx5
STEP: Checking for subpath error in container status
Jun 11 08:24:10.797: INFO: Deleting pod "pod-subpath-test-dynamicpv-mbx5" in namespace "provisioning-4309"
Jun 11 08:24:10.967: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-mbx5" to be fully deleted
STEP: Deleting pod
Jun 11 08:24:11.129: INFO: Deleting pod "pod-subpath-test-dynamicpv-mbx5" in namespace "provisioning-4309"
STEP: Deleting pvc
Jun 11 08:24:11.616: INFO: Deleting PersistentVolumeClaim "awsvc5zl"
... skipping 74 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.XbNMA0Bbv/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.XbNMA0Bbv/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.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 23 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 08:23:44.686: 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.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun 11 08:23:45.509: INFO: Creating resource for dynamic PV
Jun 11 08:23:45.509: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4383-e2e-scszzsq
STEP: creating a claim
Jun 11 08:23:45.673: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-6x8d
STEP: Checking for subpath error in container status
Jun 11 08:24:08.494: INFO: Deleting pod "pod-subpath-test-dynamicpv-6x8d" in namespace "provisioning-4383"
Jun 11 08:24:08.662: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-6x8d" to be fully deleted
STEP: Deleting pod
Jun 11 08:24:24.993: INFO: Deleting pod "pod-subpath-test-dynamicpv-6x8d" in namespace "provisioning-4383"
STEP: Deleting pvc
Jun 11 08:24:25.482: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comgwzlp"
... skipping 9 lines ...

• [SLOW TEST:46.789 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.XbNMA0Bbv/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.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [sig-storage] Zone Support [Feature:vsphere]
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 08:24:31.476: INFO: >>> kubeConfig: /root/.kube/config
... skipping 118 lines ...
Jun 11 08:23:12.799: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9768-e2e-scw7886
STEP: creating a claim
Jun 11 08:23:12.965: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-ktqq
STEP: Creating a pod to test atomic-volume-subpath
Jun 11 08:23:13.444: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-ktqq" in namespace "provisioning-9768" to be "Succeeded or Failed"
Jun 11 08:23:13.602: INFO: Pod "pod-subpath-test-dynamicpv-ktqq": Phase="Pending", Reason="", readiness=false. Elapsed: 157.470619ms
Jun 11 08:23:15.759: INFO: Pod "pod-subpath-test-dynamicpv-ktqq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.314931168s
Jun 11 08:23:17.920: INFO: Pod "pod-subpath-test-dynamicpv-ktqq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.475955866s
Jun 11 08:23:20.084: INFO: Pod "pod-subpath-test-dynamicpv-ktqq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.640023623s
Jun 11 08:23:22.242: INFO: Pod "pod-subpath-test-dynamicpv-ktqq": Phase="Pending", Reason="", readiness=false. Elapsed: 8.797854614s
Jun 11 08:23:24.400: INFO: Pod "pod-subpath-test-dynamicpv-ktqq": Phase="Pending", Reason="", readiness=false. Elapsed: 10.955777104s
... skipping 10 lines ...
Jun 11 08:23:48.171: INFO: Pod "pod-subpath-test-dynamicpv-ktqq": Phase="Running", Reason="", readiness=true. Elapsed: 34.726811575s
Jun 11 08:23:50.332: INFO: Pod "pod-subpath-test-dynamicpv-ktqq": Phase="Running", Reason="", readiness=true. Elapsed: 36.88719856s
Jun 11 08:23:52.491: INFO: Pod "pod-subpath-test-dynamicpv-ktqq": Phase="Running", Reason="", readiness=true. Elapsed: 39.046280009s
Jun 11 08:23:54.649: INFO: Pod "pod-subpath-test-dynamicpv-ktqq": Phase="Running", Reason="", readiness=true. Elapsed: 41.204556152s
Jun 11 08:23:56.809: INFO: Pod "pod-subpath-test-dynamicpv-ktqq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 43.364595418s
STEP: Saw pod success
Jun 11 08:23:56.809: INFO: Pod "pod-subpath-test-dynamicpv-ktqq" satisfied condition "Succeeded or Failed"
Jun 11 08:23:56.966: INFO: Trying to get logs from node ip-172-20-52-245.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-ktqq container test-container-subpath-dynamicpv-ktqq: <nil>
STEP: delete the pod
Jun 11 08:23:57.291: INFO: Waiting for pod pod-subpath-test-dynamicpv-ktqq to disappear
Jun 11 08:23:57.449: INFO: Pod pod-subpath-test-dynamicpv-ktqq no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-ktqq
Jun 11 08:23:57.449: INFO: Deleting pod "pod-subpath-test-dynamicpv-ktqq" in namespace "provisioning-9768"
... skipping 140 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 08:23:52.610: 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.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 11 08:23:53.390: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 11 08:23:53.390: INFO: Creating resource for dynamic PV
Jun 11 08:23:53.390: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-64009jznv
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 11 08:24:00.485: INFO: Deleting pod "pod-1a7e5024-0a74-489d-821b-07d91bad4080" in namespace "volumemode-6400"
Jun 11 08:24:00.647: INFO: Wait up to 5m0s for pod "pod-1a7e5024-0a74-489d-821b-07d91bad4080" to be fully deleted
STEP: Deleting pvc
Jun 11 08:24:05.270: INFO: Deleting PersistentVolumeClaim "awsb4lmw"
Jun 11 08:24:05.426: INFO: Waiting up to 5m0s for PersistentVolume pvc-dd42e6cc-9b8c-43f7-ba8a-9412793dd2d8 to get deleted
Jun 11 08:24:05.581: INFO: PersistentVolume pvc-dd42e6cc-9b8c-43f7-ba8a-9412793dd2d8 found and phase=Released (155.186815ms)
... skipping 14 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.XbNMA0Bbv/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.XbNMA0Bbv/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
    /tmp/kops.XbNMA0Bbv/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.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 11 08:24:37.002: INFO: Distro debian doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
... skipping 4 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.XbNMA0Bbv/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.XbNMA0Bbv/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.XbNMA0Bbv/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.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 159 lines ...
Jun 11 08:24:38.532: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 35 lines ...
Jun 11 08:24:07.440: INFO: Creating resource for dynamic PV
Jun 11 08:24:07.440: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-1121-e2e-sckznk9
STEP: creating a claim
STEP: Expanding non-expandable pvc
Jun 11 08:24:07.935: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 11 08:24:08.260: INFO: Error updating pvc ebs.csi.aws.comrmlb5: PersistentVolumeClaim "ebs.csi.aws.comrmlb5" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1121-e2e-sckznk9",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun 11 08:24:38.910: INFO: Error updating pvc ebs.csi.aws.comrmlb5: PersistentVolumeClaim "ebs.csi.aws.comrmlb5" is invalid: spec: Forbidden: spec is 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.XbNMA0Bbv/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.XbNMA0Bbv/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.XbNMA0Bbv/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.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Distro debian doesn't support ntfs -- skipping

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

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

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

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

    /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 62 lines ...
Jun 11 08:23:15.953: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-50206dmgt      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-5020    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-50206dmgt,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-5020    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-50206dmgt,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-5020    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-50206dmgt,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-50206dmgt    fd488dbd-7ac2-451c-9784-006596e902b4 2785 0 2021-06-11 08:23:16 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-11 08:23:16 +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-8r2lb pvc- provisioning-5020  396d3429-5ffd-496f-aa2d-4ae859bf9d91 2804 0 2021-06-11 08:23:16 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-11 08:23:16 +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-50206dmgt,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-e0d15e56-80f5-499f-8cd0-1fe8350da7ff in namespace provisioning-5020
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun 11 08:23:43.764: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-b55fb" in namespace "provisioning-5020" to be "Succeeded or Failed"
Jun 11 08:23:43.929: INFO: Pod "pvc-volume-tester-writer-b55fb": Phase="Pending", Reason="", readiness=false. Elapsed: 164.555213ms
Jun 11 08:23:46.092: INFO: Pod "pvc-volume-tester-writer-b55fb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.327300035s
Jun 11 08:23:48.255: INFO: Pod "pvc-volume-tester-writer-b55fb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.490852665s
Jun 11 08:23:50.419: INFO: Pod "pvc-volume-tester-writer-b55fb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.655047281s
Jun 11 08:23:52.583: INFO: Pod "pvc-volume-tester-writer-b55fb": Phase="Pending", Reason="", readiness=false. Elapsed: 8.818276657s
Jun 11 08:23:54.746: INFO: Pod "pvc-volume-tester-writer-b55fb": Phase="Pending", Reason="", readiness=false. Elapsed: 10.981654678s
... skipping 6 lines ...
Jun 11 08:24:09.903: INFO: Pod "pvc-volume-tester-writer-b55fb": Phase="Pending", Reason="", readiness=false. Elapsed: 26.138666796s
Jun 11 08:24:12.063: INFO: Pod "pvc-volume-tester-writer-b55fb": Phase="Pending", Reason="", readiness=false. Elapsed: 28.298567342s
Jun 11 08:24:14.224: INFO: Pod "pvc-volume-tester-writer-b55fb": Phase="Pending", Reason="", readiness=false. Elapsed: 30.459342238s
Jun 11 08:24:16.383: INFO: Pod "pvc-volume-tester-writer-b55fb": Phase="Pending", Reason="", readiness=false. Elapsed: 32.618886411s
Jun 11 08:24:18.544: INFO: Pod "pvc-volume-tester-writer-b55fb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.779630454s
STEP: Saw pod success
Jun 11 08:24:18.544: INFO: Pod "pvc-volume-tester-writer-b55fb" satisfied condition "Succeeded or Failed"
Jun 11 08:24:18.866: INFO: Pod pvc-volume-tester-writer-b55fb has the following logs: 
Jun 11 08:24:18.866: INFO: Deleting pod "pvc-volume-tester-writer-b55fb" in namespace "provisioning-5020"
Jun 11 08:24:19.033: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-b55fb" 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-32-106.ap-northeast-2.compute.internal"
Jun 11 08:24:19.678: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-cjm6s" in namespace "provisioning-5020" to be "Succeeded or Failed"
Jun 11 08:24:19.837: INFO: Pod "pvc-volume-tester-reader-cjm6s": Phase="Pending", Reason="", readiness=false. Elapsed: 159.478439ms
Jun 11 08:24:21.998: INFO: Pod "pvc-volume-tester-reader-cjm6s": Phase="Pending", Reason="", readiness=false. Elapsed: 2.320564703s
Jun 11 08:24:24.159: INFO: Pod "pvc-volume-tester-reader-cjm6s": Phase="Pending", Reason="", readiness=false. Elapsed: 4.480808085s
Jun 11 08:24:26.318: INFO: Pod "pvc-volume-tester-reader-cjm6s": Phase="Pending", Reason="", readiness=false. Elapsed: 6.640693464s
Jun 11 08:24:28.479: INFO: Pod "pvc-volume-tester-reader-cjm6s": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.800827136s
STEP: Saw pod success
Jun 11 08:24:28.479: INFO: Pod "pvc-volume-tester-reader-cjm6s" satisfied condition "Succeeded or Failed"
Jun 11 08:24:28.799: INFO: Pod pvc-volume-tester-reader-cjm6s has the following logs: hello world

Jun 11 08:24:28.799: INFO: Deleting pod "pvc-volume-tester-reader-cjm6s" in namespace "provisioning-5020"
Jun 11 08:24:28.965: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-cjm6s" to be fully deleted
Jun 11 08:24:29.125: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-8r2lb] to have phase Bound
Jun 11 08:24:29.284: INFO: PersistentVolumeClaim pvc-8r2lb found and phase=Bound (159.51128ms)
... skipping 201 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.XbNMA0Bbv/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.XbNMA0Bbv/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.XbNMA0Bbv/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.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 75 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 08:24:39.649: 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.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun 11 08:24:40.445: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 11 08:24:40.445: INFO: Creating resource for dynamic PV
Jun 11 08:24:40.445: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4121td7gq
STEP: creating a claim
Jun 11 08:24:40.604: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-xdzl
STEP: Checking for subpath error in container status
Jun 11 08:25:03.404: INFO: Deleting pod "pod-subpath-test-dynamicpv-xdzl" in namespace "provisioning-4121"
Jun 11 08:25:03.564: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-xdzl" to be fully deleted
STEP: Deleting pod
Jun 11 08:25:15.881: INFO: Deleting pod "pod-subpath-test-dynamicpv-xdzl" in namespace "provisioning-4121"
STEP: Deleting pvc
Jun 11 08:25:16.356: INFO: Deleting PersistentVolumeClaim "awsmwg8z"
... skipping 11 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.XbNMA0Bbv/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.XbNMA0Bbv/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.XbNMA0Bbv/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.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 11 08:25:22.351: INFO: Driver supports dynamic provisioning, skipping PreprovisionedPV pattern
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
... skipping 109 lines ...
Jun 11 08:25:15.315: INFO: Waiting for pod aws-client to disappear
Jun 11 08:25:15.473: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 11 08:25:15.473: INFO: Deleting PersistentVolumeClaim "pvc-98845"
Jun 11 08:25:15.632: INFO: Deleting PersistentVolume "aws-rrz56"
Jun 11 08:25:16.588: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0a1826b65945db722", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a1826b65945db722 is currently attached to i-0ea1ad87eb19c049d
	status code: 400, request id: f8667e78-7155-4c27-9c72-89eb50657240
Jun 11 08:25:22.384: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-0a1826b65945db722".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumes
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 08:25:22.384: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-9158" for this suite.
... skipping 100 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.XbNMA0Bbv/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.XbNMA0Bbv/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.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 103 lines ...
Jun 11 08:24:19.066: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3257m7z2z
STEP: creating a claim
Jun 11 08:24:19.232: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-mjxc
STEP: Creating a pod to test atomic-volume-subpath
Jun 11 08:24:19.737: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-mjxc" in namespace "provisioning-3257" to be "Succeeded or Failed"
Jun 11 08:24:19.902: INFO: Pod "pod-subpath-test-dynamicpv-mjxc": Phase="Pending", Reason="", readiness=false. Elapsed: 165.199823ms
Jun 11 08:24:22.070: INFO: Pod "pod-subpath-test-dynamicpv-mjxc": Phase="Pending", Reason="", readiness=false. Elapsed: 2.332470339s
Jun 11 08:24:24.243: INFO: Pod "pod-subpath-test-dynamicpv-mjxc": Phase="Pending", Reason="", readiness=false. Elapsed: 4.506051153s
Jun 11 08:24:26.410: INFO: Pod "pod-subpath-test-dynamicpv-mjxc": Phase="Pending", Reason="", readiness=false. Elapsed: 6.672389876s
Jun 11 08:24:28.576: INFO: Pod "pod-subpath-test-dynamicpv-mjxc": Phase="Pending", Reason="", readiness=false. Elapsed: 8.83912598s
Jun 11 08:24:30.743: INFO: Pod "pod-subpath-test-dynamicpv-mjxc": Phase="Pending", Reason="", readiness=false. Elapsed: 11.005860753s
... skipping 10 lines ...
Jun 11 08:24:54.588: INFO: Pod "pod-subpath-test-dynamicpv-mjxc": Phase="Running", Reason="", readiness=true. Elapsed: 34.850452922s
Jun 11 08:24:56.764: INFO: Pod "pod-subpath-test-dynamicpv-mjxc": Phase="Running", Reason="", readiness=true. Elapsed: 37.02721004s
Jun 11 08:24:58.930: INFO: Pod "pod-subpath-test-dynamicpv-mjxc": Phase="Running", Reason="", readiness=true. Elapsed: 39.192849555s
Jun 11 08:25:01.097: INFO: Pod "pod-subpath-test-dynamicpv-mjxc": Phase="Running", Reason="", readiness=true. Elapsed: 41.359439796s
Jun 11 08:25:03.263: INFO: Pod "pod-subpath-test-dynamicpv-mjxc": Phase="Succeeded", Reason="", readiness=false. Elapsed: 43.526231736s
STEP: Saw pod success
Jun 11 08:25:03.264: INFO: Pod "pod-subpath-test-dynamicpv-mjxc" satisfied condition "Succeeded or Failed"
Jun 11 08:25:03.429: INFO: Trying to get logs from node ip-172-20-42-74.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-mjxc container test-container-subpath-dynamicpv-mjxc: <nil>
STEP: delete the pod
Jun 11 08:25:03.771: INFO: Waiting for pod pod-subpath-test-dynamicpv-mjxc to disappear
Jun 11 08:25:03.936: INFO: Pod pod-subpath-test-dynamicpv-mjxc no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-mjxc
Jun 11 08:25:03.936: INFO: Deleting pod "pod-subpath-test-dynamicpv-mjxc" in namespace "provisioning-3257"
... skipping 111 lines ...
Jun 11 08:24:34.940: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-6585clbwl
STEP: creating a claim
Jun 11 08:24:35.099: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-66ss
STEP: Creating a pod to test exec-volume-test
Jun 11 08:24:35.578: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-66ss" in namespace "volume-6585" to be "Succeeded or Failed"
Jun 11 08:24:35.737: INFO: Pod "exec-volume-test-dynamicpv-66ss": Phase="Pending", Reason="", readiness=false. Elapsed: 158.7311ms
Jun 11 08:24:37.895: INFO: Pod "exec-volume-test-dynamicpv-66ss": Phase="Pending", Reason="", readiness=false. Elapsed: 2.317386928s
Jun 11 08:24:40.055: INFO: Pod "exec-volume-test-dynamicpv-66ss": Phase="Pending", Reason="", readiness=false. Elapsed: 4.477242033s
Jun 11 08:24:42.215: INFO: Pod "exec-volume-test-dynamicpv-66ss": Phase="Pending", Reason="", readiness=false. Elapsed: 6.637092793s
Jun 11 08:24:44.412: INFO: Pod "exec-volume-test-dynamicpv-66ss": Phase="Pending", Reason="", readiness=false. Elapsed: 8.833775244s
Jun 11 08:24:46.570: INFO: Pod "exec-volume-test-dynamicpv-66ss": Phase="Pending", Reason="", readiness=false. Elapsed: 10.992572781s
... skipping 10 lines ...
Jun 11 08:25:10.326: INFO: Pod "exec-volume-test-dynamicpv-66ss": Phase="Pending", Reason="", readiness=false. Elapsed: 34.748501841s
Jun 11 08:25:12.488: INFO: Pod "exec-volume-test-dynamicpv-66ss": Phase="Pending", Reason="", readiness=false. Elapsed: 36.909782418s
Jun 11 08:25:14.648: INFO: Pod "exec-volume-test-dynamicpv-66ss": Phase="Pending", Reason="", readiness=false. Elapsed: 39.070379683s
Jun 11 08:25:16.813: INFO: Pod "exec-volume-test-dynamicpv-66ss": Phase="Pending", Reason="", readiness=false. Elapsed: 41.235026197s
Jun 11 08:25:18.973: INFO: Pod "exec-volume-test-dynamicpv-66ss": Phase="Succeeded", Reason="", readiness=false. Elapsed: 43.394839486s
STEP: Saw pod success
Jun 11 08:25:18.973: INFO: Pod "exec-volume-test-dynamicpv-66ss" satisfied condition "Succeeded or Failed"
Jun 11 08:25:19.131: INFO: Trying to get logs from node ip-172-20-32-106.ap-northeast-2.compute.internal pod exec-volume-test-dynamicpv-66ss container exec-container-dynamicpv-66ss: <nil>
STEP: delete the pod
Jun 11 08:25:19.455: INFO: Waiting for pod exec-volume-test-dynamicpv-66ss to disappear
Jun 11 08:25:19.613: INFO: Pod exec-volume-test-dynamicpv-66ss no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-66ss
Jun 11 08:25:19.613: INFO: Deleting pod "exec-volume-test-dynamicpv-66ss" in namespace "volume-6585"
... skipping 308 lines ...
Jun 11 08:24:42.787: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4207-e2e-scl6z2b
STEP: creating a claim
Jun 11 08:24:42.946: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-dcb5
STEP: Creating a pod to test subpath
Jun 11 08:24:43.418: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-dcb5" in namespace "provisioning-4207" to be "Succeeded or Failed"
Jun 11 08:24:43.573: INFO: Pod "pod-subpath-test-dynamicpv-dcb5": Phase="Pending", Reason="", readiness=false. Elapsed: 155.384388ms
Jun 11 08:24:45.730: INFO: Pod "pod-subpath-test-dynamicpv-dcb5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.311947608s
Jun 11 08:24:47.886: INFO: Pod "pod-subpath-test-dynamicpv-dcb5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.467834445s
Jun 11 08:24:50.042: INFO: Pod "pod-subpath-test-dynamicpv-dcb5": Phase="Pending", Reason="", readiness=false. Elapsed: 6.623478263s
Jun 11 08:24:52.197: INFO: Pod "pod-subpath-test-dynamicpv-dcb5": Phase="Pending", Reason="", readiness=false. Elapsed: 8.778953812s
Jun 11 08:24:54.354: INFO: Pod "pod-subpath-test-dynamicpv-dcb5": Phase="Pending", Reason="", readiness=false. Elapsed: 10.935535802s
Jun 11 08:24:56.510: INFO: Pod "pod-subpath-test-dynamicpv-dcb5": Phase="Pending", Reason="", readiness=false. Elapsed: 13.091936054s
Jun 11 08:24:58.666: INFO: Pod "pod-subpath-test-dynamicpv-dcb5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 15.247978681s
STEP: Saw pod success
Jun 11 08:24:58.666: INFO: Pod "pod-subpath-test-dynamicpv-dcb5" satisfied condition "Succeeded or Failed"
Jun 11 08:24:58.821: INFO: Trying to get logs from node ip-172-20-52-245.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-dcb5 container test-container-subpath-dynamicpv-dcb5: <nil>
STEP: delete the pod
Jun 11 08:24:59.142: INFO: Waiting for pod pod-subpath-test-dynamicpv-dcb5 to disappear
Jun 11 08:24:59.297: INFO: Pod pod-subpath-test-dynamicpv-dcb5 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-dcb5
Jun 11 08:24:59.297: INFO: Deleting pod "pod-subpath-test-dynamicpv-dcb5" in namespace "provisioning-4207"
... skipping 39 lines ...
Jun 11 08:24:37.914: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-1390-e2e-sc7fmkv
STEP: creating a claim
Jun 11 08:24:38.070: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-rwh5
STEP: Creating a pod to test exec-volume-test
Jun 11 08:24:38.539: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-rwh5" in namespace "volume-1390" to be "Succeeded or Failed"
Jun 11 08:24:38.696: INFO: Pod "exec-volume-test-dynamicpv-rwh5": Phase="Pending", Reason="", readiness=false. Elapsed: 157.392946ms
Jun 11 08:24:40.852: INFO: Pod "exec-volume-test-dynamicpv-rwh5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.313343505s
Jun 11 08:24:43.008: INFO: Pod "exec-volume-test-dynamicpv-rwh5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.46853258s
Jun 11 08:24:45.163: INFO: Pod "exec-volume-test-dynamicpv-rwh5": Phase="Pending", Reason="", readiness=false. Elapsed: 6.623735427s
Jun 11 08:24:47.318: INFO: Pod "exec-volume-test-dynamicpv-rwh5": Phase="Pending", Reason="", readiness=false. Elapsed: 8.779105559s
Jun 11 08:24:49.475: INFO: Pod "exec-volume-test-dynamicpv-rwh5": Phase="Pending", Reason="", readiness=false. Elapsed: 10.935673992s
Jun 11 08:24:51.631: INFO: Pod "exec-volume-test-dynamicpv-rwh5": Phase="Pending", Reason="", readiness=false. Elapsed: 13.092353962s
Jun 11 08:24:53.788: INFO: Pod "exec-volume-test-dynamicpv-rwh5": Phase="Pending", Reason="", readiness=false. Elapsed: 15.248738975s
Jun 11 08:24:55.943: INFO: Pod "exec-volume-test-dynamicpv-rwh5": Phase="Pending", Reason="", readiness=false. Elapsed: 17.404103125s
Jun 11 08:24:58.099: INFO: Pod "exec-volume-test-dynamicpv-rwh5": Phase="Pending", Reason="", readiness=false. Elapsed: 19.559486635s
Jun 11 08:25:00.254: INFO: Pod "exec-volume-test-dynamicpv-rwh5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.714674369s
STEP: Saw pod success
Jun 11 08:25:00.254: INFO: Pod "exec-volume-test-dynamicpv-rwh5" satisfied condition "Succeeded or Failed"
Jun 11 08:25:00.409: INFO: Trying to get logs from node ip-172-20-46-76.ap-northeast-2.compute.internal pod exec-volume-test-dynamicpv-rwh5 container exec-container-dynamicpv-rwh5: <nil>
STEP: delete the pod
Jun 11 08:25:00.733: INFO: Waiting for pod exec-volume-test-dynamicpv-rwh5 to disappear
Jun 11 08:25:00.888: INFO: Pod exec-volume-test-dynamicpv-rwh5 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-rwh5
Jun 11 08:25:00.888: INFO: Deleting pod "exec-volume-test-dynamicpv-rwh5" in namespace "volume-1390"
... skipping 38 lines ...
Jun 11 08:24:37.784: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-7375-e2e-sczdwb9      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-7375    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-7375-e2e-sczdwb9,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-7375    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-7375-e2e-sczdwb9,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-7375    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-7375-e2e-sczdwb9,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-7375-e2e-sczdwb9    aa51467f-57c5-49f6-b4e6-2f5f48272a8d 4870 0 2021-06-11 08:24:38 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-11 08:24:38 +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-qtcmk pvc- provisioning-7375  4cf367f5-cdea-47e7-a944-5660c006fb73 4880 0 2021-06-11 08:24:38 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-11 08:24:38 +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-7375-e2e-sczdwb9,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-c746bd71-6ac9-4179-8e25-d44caf27b1a0 in namespace provisioning-7375
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun 11 08:24:49.500: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-bgmwq" in namespace "provisioning-7375" to be "Succeeded or Failed"
Jun 11 08:24:49.656: INFO: Pod "pvc-volume-tester-writer-bgmwq": Phase="Pending", Reason="", readiness=false. Elapsed: 155.669696ms
Jun 11 08:24:51.811: INFO: Pod "pvc-volume-tester-writer-bgmwq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.311324764s
Jun 11 08:24:53.968: INFO: Pod "pvc-volume-tester-writer-bgmwq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.467895037s
Jun 11 08:24:56.124: INFO: Pod "pvc-volume-tester-writer-bgmwq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.623971026s
Jun 11 08:24:58.280: INFO: Pod "pvc-volume-tester-writer-bgmwq": Phase="Pending", Reason="", readiness=false. Elapsed: 8.780490321s
Jun 11 08:25:00.437: INFO: Pod "pvc-volume-tester-writer-bgmwq": Phase="Pending", Reason="", readiness=false. Elapsed: 10.937051884s
Jun 11 08:25:02.594: INFO: Pod "pvc-volume-tester-writer-bgmwq": Phase="Pending", Reason="", readiness=false. Elapsed: 13.093799047s
Jun 11 08:25:04.750: INFO: Pod "pvc-volume-tester-writer-bgmwq": Phase="Pending", Reason="", readiness=false. Elapsed: 15.250044786s
Jun 11 08:25:06.906: INFO: Pod "pvc-volume-tester-writer-bgmwq": Phase="Pending", Reason="", readiness=false. Elapsed: 17.405830345s
Jun 11 08:25:09.062: INFO: Pod "pvc-volume-tester-writer-bgmwq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.561892273s
STEP: Saw pod success
Jun 11 08:25:09.062: INFO: Pod "pvc-volume-tester-writer-bgmwq" satisfied condition "Succeeded or Failed"
Jun 11 08:25:09.374: INFO: Pod pvc-volume-tester-writer-bgmwq has the following logs: 
Jun 11 08:25:09.374: INFO: Deleting pod "pvc-volume-tester-writer-bgmwq" in namespace "provisioning-7375"
Jun 11 08:25:09.536: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-bgmwq" 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-32-106.ap-northeast-2.compute.internal"
Jun 11 08:25:10.166: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-856sl" in namespace "provisioning-7375" to be "Succeeded or Failed"
Jun 11 08:25:10.321: INFO: Pod "pvc-volume-tester-reader-856sl": Phase="Pending", Reason="", readiness=false. Elapsed: 155.296727ms
Jun 11 08:25:12.477: INFO: Pod "pvc-volume-tester-reader-856sl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.310919951s
Jun 11 08:25:14.634: INFO: Pod "pvc-volume-tester-reader-856sl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.468009777s
Jun 11 08:25:16.796: INFO: Pod "pvc-volume-tester-reader-856sl": Phase="Pending", Reason="", readiness=false. Elapsed: 6.630144485s
Jun 11 08:25:18.953: INFO: Pod "pvc-volume-tester-reader-856sl": Phase="Running", Reason="", readiness=true. Elapsed: 8.787401719s
Jun 11 08:25:21.109: INFO: Pod "pvc-volume-tester-reader-856sl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.942971679s
STEP: Saw pod success
Jun 11 08:25:21.109: INFO: Pod "pvc-volume-tester-reader-856sl" satisfied condition "Succeeded or Failed"
Jun 11 08:25:21.421: INFO: Pod pvc-volume-tester-reader-856sl has the following logs: hello world

Jun 11 08:25:21.421: INFO: Deleting pod "pvc-volume-tester-reader-856sl" in namespace "provisioning-7375"
Jun 11 08:25:21.592: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-856sl" to be fully deleted
Jun 11 08:25:21.749: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-qtcmk] to have phase Bound
Jun 11 08:25:21.904: INFO: PersistentVolumeClaim pvc-qtcmk found and phase=Bound (155.238194ms)
... skipping 286 lines ...
Jun 11 08:24:40.565: INFO: Creating resource for dynamic PV
Jun 11 08:24:40.565: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9309-e2e-schjjjl
STEP: creating a claim
Jun 11 08:24:40.729: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-9309
Jun 11 08:24:41.218: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-9309" in namespace "provisioning-9309" to be "Succeeded or Failed"
Jun 11 08:24:41.380: INFO: Pod "volume-prep-provisioning-9309": Phase="Pending", Reason="", readiness=false. Elapsed: 162.529653ms
Jun 11 08:24:43.550: INFO: Pod "volume-prep-provisioning-9309": Phase="Pending", Reason="", readiness=false. Elapsed: 2.332539156s
Jun 11 08:24:45.712: INFO: Pod "volume-prep-provisioning-9309": Phase="Pending", Reason="", readiness=false. Elapsed: 4.494768948s
Jun 11 08:24:47.875: INFO: Pod "volume-prep-provisioning-9309": Phase="Pending", Reason="", readiness=false. Elapsed: 6.657156579s
Jun 11 08:24:50.037: INFO: Pod "volume-prep-provisioning-9309": Phase="Pending", Reason="", readiness=false. Elapsed: 8.819409567s
Jun 11 08:24:52.199: INFO: Pod "volume-prep-provisioning-9309": Phase="Pending", Reason="", readiness=false. Elapsed: 10.981279702s
Jun 11 08:24:54.362: INFO: Pod "volume-prep-provisioning-9309": Phase="Pending", Reason="", readiness=false. Elapsed: 13.144269024s
Jun 11 08:24:56.528: INFO: Pod "volume-prep-provisioning-9309": Phase="Succeeded", Reason="", readiness=false. Elapsed: 15.310084054s
STEP: Saw pod success
Jun 11 08:24:56.528: INFO: Pod "volume-prep-provisioning-9309" satisfied condition "Succeeded or Failed"
Jun 11 08:24:56.528: INFO: Deleting pod "volume-prep-provisioning-9309" in namespace "provisioning-9309"
Jun 11 08:24:56.706: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-9309" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-mjq5
STEP: Checking for subpath error in container status
Jun 11 08:25:31.362: INFO: Deleting pod "pod-subpath-test-dynamicpv-mjq5" in namespace "provisioning-9309"
Jun 11 08:25:31.538: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-mjq5" to be fully deleted
STEP: Deleting pod
Jun 11 08:25:31.702: INFO: Deleting pod "pod-subpath-test-dynamicpv-mjq5" in namespace "provisioning-9309"
STEP: Deleting pvc
Jun 11 08:25:32.187: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com72xbg"
... skipping 416 lines ...
Jun 11 08:25:32.605: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 11 08:25:33.556: INFO: Successfully created a new PD: "aws://ap-northeast-2a/vol-07650770982f39f57".
Jun 11 08:25:33.556: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-vzmp
STEP: Creating a pod to test exec-volume-test
Jun 11 08:25:33.714: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-vzmp" in namespace "volume-3946" to be "Succeeded or Failed"
Jun 11 08:25:33.870: INFO: Pod "exec-volume-test-inlinevolume-vzmp": Phase="Pending", Reason="", readiness=false. Elapsed: 155.976268ms
Jun 11 08:25:36.027: INFO: Pod "exec-volume-test-inlinevolume-vzmp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.313536949s
Jun 11 08:25:38.184: INFO: Pod "exec-volume-test-inlinevolume-vzmp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.470390147s
Jun 11 08:25:40.351: INFO: Pod "exec-volume-test-inlinevolume-vzmp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.637136761s
Jun 11 08:25:42.509: INFO: Pod "exec-volume-test-inlinevolume-vzmp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.795003016s
Jun 11 08:25:44.666: INFO: Pod "exec-volume-test-inlinevolume-vzmp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.952109501s
STEP: Saw pod success
Jun 11 08:25:44.666: INFO: Pod "exec-volume-test-inlinevolume-vzmp" satisfied condition "Succeeded or Failed"
Jun 11 08:25:44.822: INFO: Trying to get logs from node ip-172-20-46-76.ap-northeast-2.compute.internal pod exec-volume-test-inlinevolume-vzmp container exec-container-inlinevolume-vzmp: <nil>
STEP: delete the pod
Jun 11 08:25:45.142: INFO: Waiting for pod exec-volume-test-inlinevolume-vzmp to disappear
Jun 11 08:25:45.298: INFO: Pod exec-volume-test-inlinevolume-vzmp no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-vzmp
Jun 11 08:25:45.298: INFO: Deleting pod "exec-volume-test-inlinevolume-vzmp" in namespace "volume-3946"
Jun 11 08:25:45.789: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-07650770982f39f57", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07650770982f39f57 is currently attached to i-0e84919ee5c68a920
	status code: 400, request id: 3514cd82-f1fc-4b8c-a913-0071b612f147
Jun 11 08:25:51.524: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-07650770982f39f57", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07650770982f39f57 is currently attached to i-0e84919ee5c68a920
	status code: 400, request id: 45c18cf8-1230-49e7-88ca-da91dc8764e0
Jun 11 08:25:57.316: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-07650770982f39f57", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07650770982f39f57 is currently attached to i-0e84919ee5c68a920
	status code: 400, request id: 1ea84792-9ce2-4efd-a4b7-8ec42c4d129e
Jun 11 08:26:03.163: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-07650770982f39f57".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 08:26:03.163: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-3946" for this suite.
... skipping 33 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 08:25:23.841: 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.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 11 08:25:24.634: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 11 08:25:25.038: INFO: Successfully created a new PD: "aws://ap-northeast-2a/vol-0803c214520086d6e".
Jun 11 08:25:25.038: INFO: Creating resource for pre-provisioned PV
Jun 11 08:25:25.038: INFO: Creating PVC and PV
... skipping 6 lines ...
Jun 11 08:25:32.074: INFO: PersistentVolumeClaim pvc-gx64n found but phase is Pending instead of Bound.
Jun 11 08:25:34.232: INFO: PersistentVolumeClaim pvc-gx64n found but phase is Pending instead of Bound.
Jun 11 08:25:36.391: INFO: PersistentVolumeClaim pvc-gx64n found and phase=Bound (10.951602929s)
Jun 11 08:25:36.391: INFO: Waiting up to 3m0s for PersistentVolume aws-292z5 to have phase Bound
Jun 11 08:25:36.549: INFO: PersistentVolume aws-292z5 found and phase=Bound (157.569806ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 11 08:25:39.511: INFO: Deleting pod "pod-4544589d-6d66-48a4-90d7-745a07c81e65" in namespace "volumemode-4214"
Jun 11 08:25:39.670: INFO: Wait up to 5m0s for pod "pod-4544589d-6d66-48a4-90d7-745a07c81e65" to be fully deleted
STEP: Deleting pv and pvc
Jun 11 08:25:45.986: INFO: Deleting PersistentVolumeClaim "pvc-gx64n"
Jun 11 08:25:46.148: INFO: Deleting PersistentVolume "aws-292z5"
Jun 11 08:25:46.558: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0803c214520086d6e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0803c214520086d6e is currently attached to i-0ea1ad87eb19c049d
	status code: 400, request id: 1c8aa519-9dbf-492b-bdc0-d96ac20b3411
Jun 11 08:25:52.279: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0803c214520086d6e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0803c214520086d6e is currently attached to i-0ea1ad87eb19c049d
	status code: 400, request id: 6fd43c3c-b34e-4808-84ec-d6a8ae54288d
Jun 11 08:25:58.026: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0803c214520086d6e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0803c214520086d6e is currently attached to i-0ea1ad87eb19c049d
	status code: 400, request id: a09a2a1c-b712-4963-bc2d-8340b7a655cc
Jun 11 08:26:03.811: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-0803c214520086d6e".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 08:26:03.811: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-4214" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.XbNMA0Bbv/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.XbNMA0Bbv/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
    /tmp/kops.XbNMA0Bbv/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.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 11 08:26:04.130: INFO: Driver "ebs.csi.aws.com" does not support volume type "InlineVolume" - skipping
[AfterEach] [Testpattern: Inline-volume (default fs)] subPath
... skipping 2 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.XbNMA0Bbv/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.XbNMA0Bbv/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.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 445 lines ...
Jun 11 08:25:23.867: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-238gv7k8
STEP: creating a claim
Jun 11 08:25:24.035: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-dppf
STEP: Creating a pod to test subpath
Jun 11 08:25:24.513: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-dppf" in namespace "provisioning-238" to be "Succeeded or Failed"
Jun 11 08:25:24.671: INFO: Pod "pod-subpath-test-dynamicpv-dppf": Phase="Pending", Reason="", readiness=false. Elapsed: 157.962881ms
Jun 11 08:25:26.833: INFO: Pod "pod-subpath-test-dynamicpv-dppf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.319152217s
Jun 11 08:25:28.992: INFO: Pod "pod-subpath-test-dynamicpv-dppf": Phase="Pending", Reason="", readiness=false. Elapsed: 4.478162066s
Jun 11 08:25:31.152: INFO: Pod "pod-subpath-test-dynamicpv-dppf": Phase="Pending", Reason="", readiness=false. Elapsed: 6.638677588s
Jun 11 08:25:33.312: INFO: Pod "pod-subpath-test-dynamicpv-dppf": Phase="Pending", Reason="", readiness=false. Elapsed: 8.798458265s
Jun 11 08:25:35.473: INFO: Pod "pod-subpath-test-dynamicpv-dppf": Phase="Pending", Reason="", readiness=false. Elapsed: 10.95922937s
Jun 11 08:25:37.631: INFO: Pod "pod-subpath-test-dynamicpv-dppf": Phase="Pending", Reason="", readiness=false. Elapsed: 13.11756107s
Jun 11 08:25:39.789: INFO: Pod "pod-subpath-test-dynamicpv-dppf": Phase="Pending", Reason="", readiness=false. Elapsed: 15.275710927s
Jun 11 08:25:41.948: INFO: Pod "pod-subpath-test-dynamicpv-dppf": Phase="Succeeded", Reason="", readiness=false. Elapsed: 17.434354474s
STEP: Saw pod success
Jun 11 08:25:41.948: INFO: Pod "pod-subpath-test-dynamicpv-dppf" satisfied condition "Succeeded or Failed"
Jun 11 08:25:42.107: INFO: Trying to get logs from node ip-172-20-52-245.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-dppf container test-container-subpath-dynamicpv-dppf: <nil>
STEP: delete the pod
Jun 11 08:25:42.447: INFO: Waiting for pod pod-subpath-test-dynamicpv-dppf to disappear
Jun 11 08:25:42.606: INFO: Pod pod-subpath-test-dynamicpv-dppf no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-dppf
Jun 11 08:25:42.606: INFO: Deleting pod "pod-subpath-test-dynamicpv-dppf" in namespace "provisioning-238"
STEP: Creating pod pod-subpath-test-dynamicpv-dppf
STEP: Creating a pod to test subpath
Jun 11 08:25:42.930: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-dppf" in namespace "provisioning-238" to be "Succeeded or Failed"
Jun 11 08:25:43.090: INFO: Pod "pod-subpath-test-dynamicpv-dppf": Phase="Pending", Reason="", readiness=false. Elapsed: 159.386961ms
Jun 11 08:25:45.249: INFO: Pod "pod-subpath-test-dynamicpv-dppf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.319208156s
Jun 11 08:25:47.410: INFO: Pod "pod-subpath-test-dynamicpv-dppf": Phase="Pending", Reason="", readiness=false. Elapsed: 4.479582969s
Jun 11 08:25:49.569: INFO: Pod "pod-subpath-test-dynamicpv-dppf": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.639000869s
STEP: Saw pod success
Jun 11 08:25:49.569: INFO: Pod "pod-subpath-test-dynamicpv-dppf" satisfied condition "Succeeded or Failed"
Jun 11 08:25:49.728: INFO: Trying to get logs from node ip-172-20-52-245.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-dppf container test-container-subpath-dynamicpv-dppf: <nil>
STEP: delete the pod
Jun 11 08:25:50.054: INFO: Waiting for pod pod-subpath-test-dynamicpv-dppf to disappear
Jun 11 08:25:50.212: INFO: Pod pod-subpath-test-dynamicpv-dppf no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-dppf
Jun 11 08:25:50.212: INFO: Deleting pod "pod-subpath-test-dynamicpv-dppf" in namespace "provisioning-238"
... skipping 36 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.XbNMA0Bbv/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.XbNMA0Bbv/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.XbNMA0Bbv/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.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 94 lines ...
Jun 11 08:26:07.600: INFO: Pod aws-client still exists
Jun 11 08:26:09.440: INFO: Waiting for pod aws-client to disappear
Jun 11 08:26:09.602: INFO: Pod aws-client still exists
Jun 11 08:26:11.441: INFO: Waiting for pod aws-client to disappear
Jun 11 08:26:11.600: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun 11 08:26:12.359: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-04e202f31e64e8547", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04e202f31e64e8547 is currently attached to i-0e84919ee5c68a920
	status code: 400, request id: 4d259273-1394-4af2-8bda-e5c9089f0687
Jun 11 08:26:18.150: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-04e202f31e64e8547".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 08:26:18.150: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-9045" for this suite.
... skipping 204 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.XbNMA0Bbv/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.XbNMA0Bbv/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.XbNMA0Bbv/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.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Driver supports dynamic provisioning, skipping InlineVolume pattern

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.XbNMA0Bbv/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.XbNMA0Bbv/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.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 23 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 08:25:30.984: 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.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun 11 08:25:31.779: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 11 08:25:31.779: INFO: Creating resource for dynamic PV
Jun 11 08:25:31.779: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3713zrj87
STEP: creating a claim
Jun 11 08:25:31.940: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-ztdt
STEP: Checking for subpath error in container status
Jun 11 08:25:56.744: INFO: Deleting pod "pod-subpath-test-dynamicpv-ztdt" in namespace "provisioning-3713"
Jun 11 08:25:56.903: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-ztdt" to be fully deleted
STEP: Deleting pod
Jun 11 08:26:05.222: INFO: Deleting pod "pod-subpath-test-dynamicpv-ztdt" in namespace "provisioning-3713"
STEP: Deleting pvc
Jun 11 08:26:05.700: INFO: Deleting PersistentVolumeClaim "aws5xbk7"
... skipping 14 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.XbNMA0Bbv/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.XbNMA0Bbv/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath file is outside the volume [Slow][LinuxOnly]
      /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] volumeIO
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] volumeIO
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 230 lines ...
Jun 11 08:25:49.237: INFO: PersistentVolumeClaim pvc-t9xlw found but phase is Pending instead of Bound.
Jun 11 08:25:51.392: INFO: PersistentVolumeClaim pvc-t9xlw found and phase=Bound (8.775173333s)
Jun 11 08:25:51.392: INFO: Waiting up to 3m0s for PersistentVolume aws-gjrbg to have phase Bound
Jun 11 08:25:51.547: INFO: PersistentVolume aws-gjrbg found and phase=Bound (154.999013ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-8rsl
STEP: Creating a pod to test exec-volume-test
Jun 11 08:25:52.017: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-8rsl" in namespace "volume-7667" to be "Succeeded or Failed"
Jun 11 08:25:52.173: INFO: Pod "exec-volume-test-preprovisionedpv-8rsl": Phase="Pending", Reason="", readiness=false. Elapsed: 155.415005ms
Jun 11 08:25:54.328: INFO: Pod "exec-volume-test-preprovisionedpv-8rsl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.311043898s
Jun 11 08:25:56.488: INFO: Pod "exec-volume-test-preprovisionedpv-8rsl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.470326884s
Jun 11 08:25:58.644: INFO: Pod "exec-volume-test-preprovisionedpv-8rsl": Phase="Pending", Reason="", readiness=false. Elapsed: 6.62650088s
Jun 11 08:26:00.799: INFO: Pod "exec-volume-test-preprovisionedpv-8rsl": Phase="Pending", Reason="", readiness=false. Elapsed: 8.781960222s
Jun 11 08:26:02.956: INFO: Pod "exec-volume-test-preprovisionedpv-8rsl": Phase="Pending", Reason="", readiness=false. Elapsed: 10.938627454s
Jun 11 08:26:05.112: INFO: Pod "exec-volume-test-preprovisionedpv-8rsl": Phase="Pending", Reason="", readiness=false. Elapsed: 13.095128684s
Jun 11 08:26:07.268: INFO: Pod "exec-volume-test-preprovisionedpv-8rsl": Phase="Pending", Reason="", readiness=false. Elapsed: 15.250657664s
Jun 11 08:26:09.423: INFO: Pod "exec-volume-test-preprovisionedpv-8rsl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 17.406089919s
STEP: Saw pod success
Jun 11 08:26:09.423: INFO: Pod "exec-volume-test-preprovisionedpv-8rsl" satisfied condition "Succeeded or Failed"
Jun 11 08:26:09.579: INFO: Trying to get logs from node ip-172-20-46-76.ap-northeast-2.compute.internal pod exec-volume-test-preprovisionedpv-8rsl container exec-container-preprovisionedpv-8rsl: <nil>
STEP: delete the pod
Jun 11 08:26:09.897: INFO: Waiting for pod exec-volume-test-preprovisionedpv-8rsl to disappear
Jun 11 08:26:10.054: INFO: Pod exec-volume-test-preprovisionedpv-8rsl no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-8rsl
Jun 11 08:26:10.055: INFO: Deleting pod "exec-volume-test-preprovisionedpv-8rsl" in namespace "volume-7667"
STEP: Deleting pv and pvc
Jun 11 08:26:10.209: INFO: Deleting PersistentVolumeClaim "pvc-t9xlw"
Jun 11 08:26:10.365: INFO: Deleting PersistentVolume "aws-gjrbg"
Jun 11 08:26:10.839: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-046a01e323a5b30f2", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-046a01e323a5b30f2 is currently attached to i-0e84919ee5c68a920
	status code: 400, request id: 1bd19a05-2c93-48d2-82df-250ecc0479c6
Jun 11 08:26:16.670: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-046a01e323a5b30f2", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-046a01e323a5b30f2 is currently attached to i-0e84919ee5c68a920
	status code: 400, request id: 7bce57db-30c8-4b5a-bba0-00e76d970685
Jun 11 08:26:22.463: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-046a01e323a5b30f2", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-046a01e323a5b30f2 is currently attached to i-0e84919ee5c68a920
	status code: 400, request id: 7a52f9f1-cc54-42ef-8aa0-fa3e92094874
Jun 11 08:26:28.247: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-046a01e323a5b30f2", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-046a01e323a5b30f2 is currently attached to i-0e84919ee5c68a920
	status code: 400, request id: 0e38e43d-008b-49d5-9bc7-e1d72e68e63a
Jun 11 08:26:34.037: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-046a01e323a5b30f2".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 08:26:34.037: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-7667" for this suite.
... skipping 18 lines ...

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 10 lines ...
Jun 11 08:25:48.601: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 11 08:25:49.527: INFO: Successfully created a new PD: "aws://ap-northeast-2a/vol-02023f2d24176f740".
Jun 11 08:25:49.527: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-qfdz
STEP: Creating a pod to test exec-volume-test
Jun 11 08:25:49.691: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-qfdz" in namespace "volume-3761" to be "Succeeded or Failed"
Jun 11 08:25:49.849: INFO: Pod "exec-volume-test-inlinevolume-qfdz": Phase="Pending", Reason="", readiness=false. Elapsed: 158.035796ms
Jun 11 08:25:52.008: INFO: Pod "exec-volume-test-inlinevolume-qfdz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.317397262s
Jun 11 08:25:54.167: INFO: Pod "exec-volume-test-inlinevolume-qfdz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.476568977s
Jun 11 08:25:56.331: INFO: Pod "exec-volume-test-inlinevolume-qfdz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.640250527s
Jun 11 08:25:58.490: INFO: Pod "exec-volume-test-inlinevolume-qfdz": Phase="Pending", Reason="", readiness=false. Elapsed: 8.79961019s
Jun 11 08:26:00.649: INFO: Pod "exec-volume-test-inlinevolume-qfdz": Phase="Pending", Reason="", readiness=false. Elapsed: 10.958150462s
... skipping 8 lines ...
Jun 11 08:26:20.079: INFO: Pod "exec-volume-test-inlinevolume-qfdz": Phase="Pending", Reason="", readiness=false. Elapsed: 30.388584166s
Jun 11 08:26:22.240: INFO: Pod "exec-volume-test-inlinevolume-qfdz": Phase="Pending", Reason="", readiness=false. Elapsed: 32.549489988s
Jun 11 08:26:24.400: INFO: Pod "exec-volume-test-inlinevolume-qfdz": Phase="Pending", Reason="", readiness=false. Elapsed: 34.709317796s
Jun 11 08:26:26.558: INFO: Pod "exec-volume-test-inlinevolume-qfdz": Phase="Pending", Reason="", readiness=false. Elapsed: 36.867718928s
Jun 11 08:26:28.718: INFO: Pod "exec-volume-test-inlinevolume-qfdz": Phase="Succeeded", Reason="", readiness=false. Elapsed: 39.027480329s
STEP: Saw pod success
Jun 11 08:26:28.718: INFO: Pod "exec-volume-test-inlinevolume-qfdz" satisfied condition "Succeeded or Failed"
Jun 11 08:26:28.876: INFO: Trying to get logs from node ip-172-20-52-245.ap-northeast-2.compute.internal pod exec-volume-test-inlinevolume-qfdz container exec-container-inlinevolume-qfdz: <nil>
STEP: delete the pod
Jun 11 08:26:29.202: INFO: Waiting for pod exec-volume-test-inlinevolume-qfdz to disappear
Jun 11 08:26:29.360: INFO: Pod exec-volume-test-inlinevolume-qfdz no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-qfdz
Jun 11 08:26:29.360: INFO: Deleting pod "exec-volume-test-inlinevolume-qfdz" in namespace "volume-3761"
Jun 11 08:26:29.803: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-02023f2d24176f740", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02023f2d24176f740 is currently attached to i-0ea1ad87eb19c049d
	status code: 400, request id: e98f8852-6abe-4d42-86b0-129acc3373ed
Jun 11 08:26:35.572: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-02023f2d24176f740", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02023f2d24176f740 is currently attached to i-0ea1ad87eb19c049d
	status code: 400, request id: 82747383-7c71-4e5a-99ba-e0d16852a219
Jun 11 08:26:41.340: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-02023f2d24176f740", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02023f2d24176f740 is currently attached to i-0ea1ad87eb19c049d
	status code: 400, request id: d8ab3c92-20bd-40dd-a52a-29cbfe9734c0
Jun 11 08:26:47.128: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-02023f2d24176f740".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 08:26:47.128: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-3761" for this suite.
... skipping 242 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 08:26:22.991: 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.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun 11 08:26:23.789: INFO: Creating resource for dynamic PV
Jun 11 08:26:23.789: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-868-e2e-sc87gw4
STEP: creating a claim
Jun 11 08:26:23.950: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-qkfr
STEP: Checking for subpath error in container status
Jun 11 08:26:38.755: INFO: Deleting pod "pod-subpath-test-dynamicpv-qkfr" in namespace "provisioning-868"
Jun 11 08:26:38.915: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-qkfr" to be fully deleted
STEP: Deleting pod
Jun 11 08:26:45.235: INFO: Deleting pod "pod-subpath-test-dynamicpv-qkfr" in namespace "provisioning-868"
STEP: Deleting pvc
Jun 11 08:26:45.714: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comjv46t"
... skipping 10 lines ...

• [SLOW TEST:33.858 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath directory is outside the volume [Slow][LinuxOnly]
    /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 08:26:55.952: 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.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Jun 11 08:26:56.900: INFO: found topology map[topology.kubernetes.io/zone:ap-northeast-2a]
Jun 11 08:26:56.900: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 11 08:26:56.900: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.XbNMA0Bbv/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.XbNMA0Bbv/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (immediate binding)] topology
    /tmp/kops.XbNMA0Bbv/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.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 90 lines ...
Jun 11 08:26:51.463: INFO: Waiting for pod aws-client to disappear
Jun 11 08:26:51.620: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 11 08:26:51.620: INFO: Deleting PersistentVolumeClaim "pvc-8s9xz"
Jun 11 08:26:51.780: INFO: Deleting PersistentVolume "aws-mm4xr"
Jun 11 08:26:52.190: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-04ed82ea054f7b9bb", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04ed82ea054f7b9bb is currently attached to i-0e84919ee5c68a920
	status code: 400, request id: 9d8183d1-bba4-45a5-b0c0-ac12862acbfa
Jun 11 08:26:57.976: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-04ed82ea054f7b9bb".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 08:26:57.976: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-7870" for this suite.
... skipping 125 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 08:26:36.768: 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.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 11 08:26:37.561: INFO: Creating resource for dynamic PV
Jun 11 08:26:37.561: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-3319-e2e-scdrxfc
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 11 08:26:44.678: INFO: Deleting pod "pod-16baf0e3-0987-4c2c-a1ec-783a75cfc60f" in namespace "volumemode-3319"
Jun 11 08:26:44.838: INFO: Wait up to 5m0s for pod "pod-16baf0e3-0987-4c2c-a1ec-783a75cfc60f" to be fully deleted
STEP: Deleting pvc
Jun 11 08:26:55.474: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com6q64r"
Jun 11 08:26:55.637: INFO: Waiting up to 5m0s for PersistentVolume pvc-c3b9eff7-99b2-4a83-8aad-265b140d6b57 to get deleted
Jun 11 08:26:55.795: INFO: PersistentVolume pvc-c3b9eff7-99b2-4a83-8aad-265b140d6b57 found and phase=Released (158.153285ms)
... skipping 7 lines ...

• [SLOW TEST:24.675 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.XbNMA0Bbv/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.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 11 08:27:01.445: INFO: Driver ebs.csi.aws.com doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
... skipping 2 lines ...

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

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

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

      Not enough topologies in cluster -- skipping

      /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 270 lines ...
Jun 11 08:26:16.838: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-6620-e2e-schdrst
STEP: creating a claim
Jun 11 08:26:16.999: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-59nl
STEP: Creating a pod to test exec-volume-test
Jun 11 08:26:17.483: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-59nl" in namespace "volume-6620" to be "Succeeded or Failed"
Jun 11 08:26:17.643: INFO: Pod "exec-volume-test-dynamicpv-59nl": Phase="Pending", Reason="", readiness=false. Elapsed: 159.694376ms
Jun 11 08:26:19.802: INFO: Pod "exec-volume-test-dynamicpv-59nl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.319471554s
Jun 11 08:26:21.962: INFO: Pod "exec-volume-test-dynamicpv-59nl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.479362785s
Jun 11 08:26:24.127: INFO: Pod "exec-volume-test-dynamicpv-59nl": Phase="Pending", Reason="", readiness=false. Elapsed: 6.644102437s
Jun 11 08:26:26.296: INFO: Pod "exec-volume-test-dynamicpv-59nl": Phase="Pending", Reason="", readiness=false. Elapsed: 8.813410212s
Jun 11 08:26:28.457: INFO: Pod "exec-volume-test-dynamicpv-59nl": Phase="Pending", Reason="", readiness=false. Elapsed: 10.973703779s
Jun 11 08:26:30.617: INFO: Pod "exec-volume-test-dynamicpv-59nl": Phase="Pending", Reason="", readiness=false. Elapsed: 13.13391458s
Jun 11 08:26:32.782: INFO: Pod "exec-volume-test-dynamicpv-59nl": Phase="Pending", Reason="", readiness=false. Elapsed: 15.29862661s
Jun 11 08:26:34.942: INFO: Pod "exec-volume-test-dynamicpv-59nl": Phase="Pending", Reason="", readiness=false. Elapsed: 17.458656247s
Jun 11 08:26:37.102: INFO: Pod "exec-volume-test-dynamicpv-59nl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.619216086s
STEP: Saw pod success
Jun 11 08:26:37.102: INFO: Pod "exec-volume-test-dynamicpv-59nl" satisfied condition "Succeeded or Failed"
Jun 11 08:26:37.262: INFO: Trying to get logs from node ip-172-20-42-74.ap-northeast-2.compute.internal pod exec-volume-test-dynamicpv-59nl container exec-container-dynamicpv-59nl: <nil>
STEP: delete the pod
Jun 11 08:26:37.589: INFO: Waiting for pod exec-volume-test-dynamicpv-59nl to disappear
Jun 11 08:26:37.748: INFO: Pod exec-volume-test-dynamicpv-59nl no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-59nl
Jun 11 08:26:37.748: INFO: Deleting pod "exec-volume-test-dynamicpv-59nl" in namespace "volume-6620"
... skipping 186 lines ...
Jun 11 08:24:01.887: INFO: Creating resource for dynamic PV
Jun 11 08:24:01.887: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-6987-e2e-scrghpw
STEP: creating a claim
Jun 11 08:24:02.051: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 11 08:24:02.548: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-vvshr" in namespace "snapshotting-6987" to be "Succeeded or Failed"
Jun 11 08:24:02.711: INFO: Pod "pvc-snapshottable-tester-vvshr": Phase="Pending", Reason="", readiness=false. Elapsed: 163.577681ms
Jun 11 08:24:04.875: INFO: Pod "pvc-snapshottable-tester-vvshr": Phase="Pending", Reason="", readiness=false. Elapsed: 2.327601293s
Jun 11 08:24:07.039: INFO: Pod "pvc-snapshottable-tester-vvshr": Phase="Pending", Reason="", readiness=false. Elapsed: 4.491590587s
Jun 11 08:24:09.204: INFO: Pod "pvc-snapshottable-tester-vvshr": Phase="Pending", Reason="", readiness=false. Elapsed: 6.655811664s
Jun 11 08:24:11.368: INFO: Pod "pvc-snapshottable-tester-vvshr": Phase="Pending", Reason="", readiness=false. Elapsed: 8.820071488s
Jun 11 08:24:13.532: INFO: Pod "pvc-snapshottable-tester-vvshr": Phase="Pending", Reason="", readiness=false. Elapsed: 10.984270285s
... skipping 9 lines ...
Jun 11 08:24:35.207: INFO: Pod "pvc-snapshottable-tester-vvshr": Phase="Pending", Reason="", readiness=false. Elapsed: 32.658854405s
Jun 11 08:24:37.371: INFO: Pod "pvc-snapshottable-tester-vvshr": Phase="Pending", Reason="", readiness=false. Elapsed: 34.823151461s
Jun 11 08:24:39.536: INFO: Pod "pvc-snapshottable-tester-vvshr": Phase="Pending", Reason="", readiness=false. Elapsed: 36.987948765s
Jun 11 08:24:41.700: INFO: Pod "pvc-snapshottable-tester-vvshr": Phase="Pending", Reason="", readiness=false. Elapsed: 39.152101919s
Jun 11 08:24:43.864: INFO: Pod "pvc-snapshottable-tester-vvshr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 41.316555693s
STEP: Saw pod success
Jun 11 08:24:43.864: INFO: Pod "pvc-snapshottable-tester-vvshr" satisfied condition "Succeeded or Failed"
Jun 11 08:24:44.194: INFO: Pod pvc-snapshottable-tester-vvshr has the following logs: 
Jun 11 08:24:44.194: INFO: Deleting pod "pvc-snapshottable-tester-vvshr" in namespace "snapshotting-6987"
Jun 11 08:24:44.362: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-vvshr" to be fully deleted
Jun 11 08:24:44.526: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.com9p4ks] to have phase Bound
Jun 11 08:24:44.690: INFO: PersistentVolumeClaim ebs.csi.aws.com9p4ks found and phase=Bound (163.58851ms)
STEP: [init] checking the claim
... skipping 54 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.XbNMA0Bbv/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 11 08:25:44.496: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-kbgqs" in namespace "snapshotting-6987" to be "Succeeded or Failed"
Jun 11 08:25:44.661: INFO: Pod "pvc-snapshottable-data-tester-kbgqs": Phase="Pending", Reason="", readiness=false. Elapsed: 165.028856ms
Jun 11 08:25:46.826: INFO: Pod "pvc-snapshottable-data-tester-kbgqs": Phase="Pending", Reason="", readiness=false. Elapsed: 2.330266083s
Jun 11 08:25:48.993: INFO: Pod "pvc-snapshottable-data-tester-kbgqs": Phase="Pending", Reason="", readiness=false. Elapsed: 4.496570717s
Jun 11 08:25:51.160: INFO: Pod "pvc-snapshottable-data-tester-kbgqs": Phase="Pending", Reason="", readiness=false. Elapsed: 6.663952278s
Jun 11 08:25:53.324: INFO: Pod "pvc-snapshottable-data-tester-kbgqs": Phase="Pending", Reason="", readiness=false. Elapsed: 8.827658184s
Jun 11 08:25:55.491: INFO: Pod "pvc-snapshottable-data-tester-kbgqs": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.994660894s
STEP: Saw pod success
Jun 11 08:25:55.491: INFO: Pod "pvc-snapshottable-data-tester-kbgqs" satisfied condition "Succeeded or Failed"
Jun 11 08:25:55.819: INFO: Pod pvc-snapshottable-data-tester-kbgqs has the following logs: 
Jun 11 08:25:55.819: INFO: Deleting pod "pvc-snapshottable-data-tester-kbgqs" in namespace "snapshotting-6987"
Jun 11 08:25:55.991: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-kbgqs" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 11 08:26:34.861: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-6987 exec restored-pvc-tester-zblhv --namespace=snapshotting-6987 -- cat /mnt/test/data'
... skipping 113 lines ...
Jun 11 08:26:12.887: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5989-e2e-scdzlrf
STEP: creating a claim
Jun 11 08:26:13.054: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-qbrj
STEP: Creating a pod to test subpath
Jun 11 08:26:13.564: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-qbrj" in namespace "provisioning-5989" to be "Succeeded or Failed"
Jun 11 08:26:13.730: INFO: Pod "pod-subpath-test-dynamicpv-qbrj": Phase="Pending", Reason="", readiness=false. Elapsed: 165.597187ms
Jun 11 08:26:15.910: INFO: Pod "pod-subpath-test-dynamicpv-qbrj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.346474857s
Jun 11 08:26:18.076: INFO: Pod "pod-subpath-test-dynamicpv-qbrj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.512248619s
Jun 11 08:26:20.242: INFO: Pod "pod-subpath-test-dynamicpv-qbrj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.677731188s
Jun 11 08:26:22.407: INFO: Pod "pod-subpath-test-dynamicpv-qbrj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.843518222s
Jun 11 08:26:24.575: INFO: Pod "pod-subpath-test-dynamicpv-qbrj": Phase="Pending", Reason="", readiness=false. Elapsed: 11.01098687s
... skipping 2 lines ...
Jun 11 08:26:31.077: INFO: Pod "pod-subpath-test-dynamicpv-qbrj": Phase="Pending", Reason="", readiness=false. Elapsed: 17.512902694s
Jun 11 08:26:33.244: INFO: Pod "pod-subpath-test-dynamicpv-qbrj": Phase="Pending", Reason="", readiness=false. Elapsed: 19.679939015s
Jun 11 08:26:35.410: INFO: Pod "pod-subpath-test-dynamicpv-qbrj": Phase="Pending", Reason="", readiness=false. Elapsed: 21.845707277s
Jun 11 08:26:37.577: INFO: Pod "pod-subpath-test-dynamicpv-qbrj": Phase="Pending", Reason="", readiness=false. Elapsed: 24.012696286s
Jun 11 08:26:39.742: INFO: Pod "pod-subpath-test-dynamicpv-qbrj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.178301041s
STEP: Saw pod success
Jun 11 08:26:39.742: INFO: Pod "pod-subpath-test-dynamicpv-qbrj" satisfied condition "Succeeded or Failed"
Jun 11 08:26:39.907: INFO: Trying to get logs from node ip-172-20-46-76.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-qbrj container test-container-subpath-dynamicpv-qbrj: <nil>
STEP: delete the pod
Jun 11 08:26:40.246: INFO: Waiting for pod pod-subpath-test-dynamicpv-qbrj to disappear
Jun 11 08:26:40.413: INFO: Pod pod-subpath-test-dynamicpv-qbrj no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-qbrj
Jun 11 08:26:40.413: INFO: Deleting pod "pod-subpath-test-dynamicpv-qbrj" in namespace "provisioning-5989"
STEP: Creating pod pod-subpath-test-dynamicpv-qbrj
STEP: Creating a pod to test subpath
Jun 11 08:26:40.747: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-qbrj" in namespace "provisioning-5989" to be "Succeeded or Failed"
Jun 11 08:26:40.912: INFO: Pod "pod-subpath-test-dynamicpv-qbrj": Phase="Pending", Reason="", readiness=false. Elapsed: 165.667375ms
Jun 11 08:26:43.084: INFO: Pod "pod-subpath-test-dynamicpv-qbrj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.337546974s
Jun 11 08:26:45.251: INFO: Pod "pod-subpath-test-dynamicpv-qbrj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.503701591s
Jun 11 08:26:47.418: INFO: Pod "pod-subpath-test-dynamicpv-qbrj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.671000568s
Jun 11 08:26:49.584: INFO: Pod "pod-subpath-test-dynamicpv-qbrj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.837500445s
Jun 11 08:26:51.751: INFO: Pod "pod-subpath-test-dynamicpv-qbrj": Phase="Pending", Reason="", readiness=false. Elapsed: 11.004151686s
Jun 11 08:26:53.919: INFO: Pod "pod-subpath-test-dynamicpv-qbrj": Phase="Pending", Reason="", readiness=false. Elapsed: 13.171729169s
Jun 11 08:26:56.085: INFO: Pod "pod-subpath-test-dynamicpv-qbrj": Phase="Pending", Reason="", readiness=false. Elapsed: 15.338529077s
Jun 11 08:26:58.251: INFO: Pod "pod-subpath-test-dynamicpv-qbrj": Phase="Pending", Reason="", readiness=false. Elapsed: 17.504248097s
Jun 11 08:27:00.417: INFO: Pod "pod-subpath-test-dynamicpv-qbrj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.669829445s
STEP: Saw pod success
Jun 11 08:27:00.417: INFO: Pod "pod-subpath-test-dynamicpv-qbrj" satisfied condition "Succeeded or Failed"
Jun 11 08:27:00.582: INFO: Trying to get logs from node ip-172-20-46-76.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-qbrj container test-container-subpath-dynamicpv-qbrj: <nil>
STEP: delete the pod
Jun 11 08:27:00.923: INFO: Waiting for pod pod-subpath-test-dynamicpv-qbrj to disappear
Jun 11 08:27:01.088: INFO: Pod pod-subpath-test-dynamicpv-qbrj no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-qbrj
Jun 11 08:27:01.088: INFO: Deleting pod "pod-subpath-test-dynamicpv-qbrj" in namespace "provisioning-5989"
... skipping 68 lines ...
Jun 11 08:27:41.093: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 245 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 08:27:15.157: 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.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun 11 08:27:16.008: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 11 08:27:16.008: INFO: Creating resource for dynamic PV
Jun 11 08:27:16.008: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-54546dvvj
STEP: creating a claim
Jun 11 08:27:16.168: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-w5sb
STEP: Checking for subpath error in container status
Jun 11 08:27:32.981: INFO: Deleting pod "pod-subpath-test-dynamicpv-w5sb" in namespace "provisioning-5454"
Jun 11 08:27:33.147: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-w5sb" to be fully deleted
STEP: Deleting pod
Jun 11 08:27:39.466: INFO: Deleting pod "pod-subpath-test-dynamicpv-w5sb" in namespace "provisioning-5454"
STEP: Deleting pvc
Jun 11 08:27:39.944: INFO: Deleting PersistentVolumeClaim "awsvjm9p"
... skipping 12 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.XbNMA0Bbv/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.XbNMA0Bbv/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath directory is outside the volume [Slow][LinuxOnly]
      /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] volumes
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
... skipping 288 lines ...
Jun 11 08:27:19.328: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1924tzwlb
STEP: creating a claim
Jun 11 08:27:19.491: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-ld6c
STEP: Creating a pod to test subpath
Jun 11 08:27:19.982: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-ld6c" in namespace "provisioning-1924" to be "Succeeded or Failed"
Jun 11 08:27:20.144: INFO: Pod "pod-subpath-test-dynamicpv-ld6c": Phase="Pending", Reason="", readiness=false. Elapsed: 161.905242ms
Jun 11 08:27:22.309: INFO: Pod "pod-subpath-test-dynamicpv-ld6c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.32651118s
Jun 11 08:27:24.473: INFO: Pod "pod-subpath-test-dynamicpv-ld6c": Phase="Pending", Reason="", readiness=false. Elapsed: 4.4905828s
Jun 11 08:27:26.636: INFO: Pod "pod-subpath-test-dynamicpv-ld6c": Phase="Pending", Reason="", readiness=false. Elapsed: 6.654085387s
Jun 11 08:27:28.799: INFO: Pod "pod-subpath-test-dynamicpv-ld6c": Phase="Pending", Reason="", readiness=false. Elapsed: 8.81732493s
Jun 11 08:27:30.963: INFO: Pod "pod-subpath-test-dynamicpv-ld6c": Phase="Pending", Reason="", readiness=false. Elapsed: 10.980878417s
Jun 11 08:27:33.126: INFO: Pod "pod-subpath-test-dynamicpv-ld6c": Phase="Pending", Reason="", readiness=false. Elapsed: 13.143840284s
Jun 11 08:27:35.288: INFO: Pod "pod-subpath-test-dynamicpv-ld6c": Phase="Pending", Reason="", readiness=false. Elapsed: 15.306271097s
Jun 11 08:27:37.451: INFO: Pod "pod-subpath-test-dynamicpv-ld6c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 17.469305227s
STEP: Saw pod success
Jun 11 08:27:37.452: INFO: Pod "pod-subpath-test-dynamicpv-ld6c" satisfied condition "Succeeded or Failed"
Jun 11 08:27:37.613: INFO: Trying to get logs from node ip-172-20-46-76.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-ld6c container test-container-subpath-dynamicpv-ld6c: <nil>
STEP: delete the pod
Jun 11 08:27:37.949: INFO: Waiting for pod pod-subpath-test-dynamicpv-ld6c to disappear
Jun 11 08:27:38.111: INFO: Pod pod-subpath-test-dynamicpv-ld6c no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-ld6c
Jun 11 08:27:38.111: INFO: Deleting pod "pod-subpath-test-dynamicpv-ld6c" in namespace "provisioning-1924"
... skipping 107 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.XbNMA0Bbv/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.XbNMA0Bbv/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.XbNMA0Bbv/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.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

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

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 305 lines ...
Jun 11 08:27:12.316: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5096-e2e-sct5f2s
STEP: creating a claim
Jun 11 08:27:12.476: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-j58b
STEP: Creating a pod to test multi_subpath
Jun 11 08:27:12.960: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-j58b" in namespace "provisioning-5096" to be "Succeeded or Failed"
Jun 11 08:27:13.120: INFO: Pod "pod-subpath-test-dynamicpv-j58b": Phase="Pending", Reason="", readiness=false. Elapsed: 159.523093ms
Jun 11 08:27:15.285: INFO: Pod "pod-subpath-test-dynamicpv-j58b": Phase="Pending", Reason="", readiness=false. Elapsed: 2.324603122s
Jun 11 08:27:17.445: INFO: Pod "pod-subpath-test-dynamicpv-j58b": Phase="Pending", Reason="", readiness=false. Elapsed: 4.48537126s
Jun 11 08:27:19.606: INFO: Pod "pod-subpath-test-dynamicpv-j58b": Phase="Pending", Reason="", readiness=false. Elapsed: 6.645696132s
Jun 11 08:27:21.766: INFO: Pod "pod-subpath-test-dynamicpv-j58b": Phase="Pending", Reason="", readiness=false. Elapsed: 8.805917878s
Jun 11 08:27:23.927: INFO: Pod "pod-subpath-test-dynamicpv-j58b": Phase="Pending", Reason="", readiness=false. Elapsed: 10.966942848s
Jun 11 08:27:26.087: INFO: Pod "pod-subpath-test-dynamicpv-j58b": Phase="Pending", Reason="", readiness=false. Elapsed: 13.127037339s
Jun 11 08:27:28.247: INFO: Pod "pod-subpath-test-dynamicpv-j58b": Phase="Pending", Reason="", readiness=false. Elapsed: 15.286998552s
Jun 11 08:27:30.408: INFO: Pod "pod-subpath-test-dynamicpv-j58b": Phase="Succeeded", Reason="", readiness=false. Elapsed: 17.448142824s
STEP: Saw pod success
Jun 11 08:27:30.408: INFO: Pod "pod-subpath-test-dynamicpv-j58b" satisfied condition "Succeeded or Failed"
Jun 11 08:27:30.568: INFO: Trying to get logs from node ip-172-20-46-76.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-j58b container test-container-subpath-dynamicpv-j58b: <nil>
STEP: delete the pod
Jun 11 08:27:30.896: INFO: Waiting for pod pod-subpath-test-dynamicpv-j58b to disappear
Jun 11 08:27:31.055: INFO: Pod pod-subpath-test-dynamicpv-j58b no longer exists
STEP: Deleting pod
Jun 11 08:27:31.055: INFO: Deleting pod "pod-subpath-test-dynamicpv-j58b" in namespace "provisioning-5096"
... skipping 165 lines ...
Jun 11 08:27:47.978: INFO: PersistentVolumeClaim pvc-ltpzx found but phase is Pending instead of Bound.
Jun 11 08:27:50.137: INFO: PersistentVolumeClaim pvc-ltpzx found and phase=Bound (13.111733722s)
Jun 11 08:27:50.137: INFO: Waiting up to 3m0s for PersistentVolume aws-vqrbg to have phase Bound
Jun 11 08:27:50.295: INFO: PersistentVolume aws-vqrbg found and phase=Bound (157.641622ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-cf8w
STEP: Creating a pod to test exec-volume-test
Jun 11 08:27:50.771: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-cf8w" in namespace "volume-6829" to be "Succeeded or Failed"
Jun 11 08:27:50.928: INFO: Pod "exec-volume-test-preprovisionedpv-cf8w": Phase="Pending", Reason="", readiness=false. Elapsed: 157.893239ms
Jun 11 08:27:53.087: INFO: Pod "exec-volume-test-preprovisionedpv-cf8w": Phase="Pending", Reason="", readiness=false. Elapsed: 2.316457775s
Jun 11 08:27:55.247: INFO: Pod "exec-volume-test-preprovisionedpv-cf8w": Phase="Pending", Reason="", readiness=false. Elapsed: 4.476060592s
Jun 11 08:27:57.408: INFO: Pod "exec-volume-test-preprovisionedpv-cf8w": Phase="Pending", Reason="", readiness=false. Elapsed: 6.637322959s
Jun 11 08:27:59.566: INFO: Pod "exec-volume-test-preprovisionedpv-cf8w": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.795550832s
STEP: Saw pod success
Jun 11 08:27:59.566: INFO: Pod "exec-volume-test-preprovisionedpv-cf8w" satisfied condition "Succeeded or Failed"
Jun 11 08:27:59.724: INFO: Trying to get logs from node ip-172-20-52-245.ap-northeast-2.compute.internal pod exec-volume-test-preprovisionedpv-cf8w container exec-container-preprovisionedpv-cf8w: <nil>
STEP: delete the pod
Jun 11 08:28:00.059: INFO: Waiting for pod exec-volume-test-preprovisionedpv-cf8w to disappear
Jun 11 08:28:00.220: INFO: Pod exec-volume-test-preprovisionedpv-cf8w no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-cf8w
Jun 11 08:28:00.220: INFO: Deleting pod "exec-volume-test-preprovisionedpv-cf8w" in namespace "volume-6829"
STEP: Deleting pv and pvc
Jun 11 08:28:00.378: INFO: Deleting PersistentVolumeClaim "pvc-ltpzx"
Jun 11 08:28:00.537: INFO: Deleting PersistentVolume "aws-vqrbg"
Jun 11 08:28:00.974: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0be97a7c8bd7c0798", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0be97a7c8bd7c0798 is currently attached to i-0ea1ad87eb19c049d
	status code: 400, request id: 7883f811-207c-4fa1-bee0-c047a9b591e0
Jun 11 08:28:06.764: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0be97a7c8bd7c0798", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0be97a7c8bd7c0798 is currently attached to i-0ea1ad87eb19c049d
	status code: 400, request id: 42c1614f-d737-409f-acb3-3dc07b74d0d5
Jun 11 08:28:12.585: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-0be97a7c8bd7c0798".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 08:28:12.585: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-6829" for this suite.
... skipping 464 lines ...
Jun 11 08:27:41.921: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2897shqb9
STEP: creating a claim
Jun 11 08:27:42.087: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-c4xj
STEP: Creating a pod to test subpath
Jun 11 08:27:42.587: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-c4xj" in namespace "provisioning-2897" to be "Succeeded or Failed"
Jun 11 08:27:42.752: INFO: Pod "pod-subpath-test-dynamicpv-c4xj": Phase="Pending", Reason="", readiness=false. Elapsed: 165.142692ms
Jun 11 08:27:44.918: INFO: Pod "pod-subpath-test-dynamicpv-c4xj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.331189472s
Jun 11 08:27:47.085: INFO: Pod "pod-subpath-test-dynamicpv-c4xj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.497440196s
Jun 11 08:27:49.252: INFO: Pod "pod-subpath-test-dynamicpv-c4xj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.664444232s
Jun 11 08:27:51.418: INFO: Pod "pod-subpath-test-dynamicpv-c4xj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.830450673s
Jun 11 08:27:53.584: INFO: Pod "pod-subpath-test-dynamicpv-c4xj": Phase="Pending", Reason="", readiness=false. Elapsed: 10.996819092s
Jun 11 08:27:55.751: INFO: Pod "pod-subpath-test-dynamicpv-c4xj": Phase="Pending", Reason="", readiness=false. Elapsed: 13.163863753s
Jun 11 08:27:57.917: INFO: Pod "pod-subpath-test-dynamicpv-c4xj": Phase="Pending", Reason="", readiness=false. Elapsed: 15.330317401s
Jun 11 08:28:00.085: INFO: Pod "pod-subpath-test-dynamicpv-c4xj": Phase="Pending", Reason="", readiness=false. Elapsed: 17.497916652s
Jun 11 08:28:02.252: INFO: Pod "pod-subpath-test-dynamicpv-c4xj": Phase="Pending", Reason="", readiness=false. Elapsed: 19.664826178s
Jun 11 08:28:04.424: INFO: Pod "pod-subpath-test-dynamicpv-c4xj": Phase="Pending", Reason="", readiness=false. Elapsed: 21.836915574s
Jun 11 08:28:06.590: INFO: Pod "pod-subpath-test-dynamicpv-c4xj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.002503799s
STEP: Saw pod success
Jun 11 08:28:06.590: INFO: Pod "pod-subpath-test-dynamicpv-c4xj" satisfied condition "Succeeded or Failed"
Jun 11 08:28:06.756: INFO: Trying to get logs from node ip-172-20-32-106.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-c4xj container test-container-subpath-dynamicpv-c4xj: <nil>
STEP: delete the pod
Jun 11 08:28:07.095: INFO: Waiting for pod pod-subpath-test-dynamicpv-c4xj to disappear
Jun 11 08:28:07.261: INFO: Pod pod-subpath-test-dynamicpv-c4xj no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-c4xj
Jun 11 08:28:07.261: INFO: Deleting pod "pod-subpath-test-dynamicpv-c4xj" in namespace "provisioning-2897"
... skipping 261 lines ...
Jun 11 08:27:49.455: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9600xhtbd
STEP: creating a claim
Jun 11 08:27:49.611: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-7v7q
STEP: Creating a pod to test multi_subpath
Jun 11 08:27:50.085: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-7v7q" in namespace "provisioning-9600" to be "Succeeded or Failed"
Jun 11 08:27:50.242: INFO: Pod "pod-subpath-test-dynamicpv-7v7q": Phase="Pending", Reason="", readiness=false. Elapsed: 156.988033ms
Jun 11 08:27:52.398: INFO: Pod "pod-subpath-test-dynamicpv-7v7q": Phase="Pending", Reason="", readiness=false. Elapsed: 2.312988004s
Jun 11 08:27:54.566: INFO: Pod "pod-subpath-test-dynamicpv-7v7q": Phase="Pending", Reason="", readiness=false. Elapsed: 4.480617245s
Jun 11 08:27:56.728: INFO: Pod "pod-subpath-test-dynamicpv-7v7q": Phase="Pending", Reason="", readiness=false. Elapsed: 6.642420547s
Jun 11 08:27:58.884: INFO: Pod "pod-subpath-test-dynamicpv-7v7q": Phase="Pending", Reason="", readiness=false. Elapsed: 8.798932006s
Jun 11 08:28:01.041: INFO: Pod "pod-subpath-test-dynamicpv-7v7q": Phase="Pending", Reason="", readiness=false. Elapsed: 10.955712452s
Jun 11 08:28:03.199: INFO: Pod "pod-subpath-test-dynamicpv-7v7q": Phase="Pending", Reason="", readiness=false. Elapsed: 13.114128321s
Jun 11 08:28:05.356: INFO: Pod "pod-subpath-test-dynamicpv-7v7q": Phase="Pending", Reason="", readiness=false. Elapsed: 15.270518941s
Jun 11 08:28:07.513: INFO: Pod "pod-subpath-test-dynamicpv-7v7q": Phase="Pending", Reason="", readiness=false. Elapsed: 17.427432284s
Jun 11 08:28:09.669: INFO: Pod "pod-subpath-test-dynamicpv-7v7q": Phase="Pending", Reason="", readiness=false. Elapsed: 19.584077412s
Jun 11 08:28:11.827: INFO: Pod "pod-subpath-test-dynamicpv-7v7q": Phase="Pending", Reason="", readiness=false. Elapsed: 21.741282634s
Jun 11 08:28:13.983: INFO: Pod "pod-subpath-test-dynamicpv-7v7q": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.89774565s
STEP: Saw pod success
Jun 11 08:28:13.983: INFO: Pod "pod-subpath-test-dynamicpv-7v7q" satisfied condition "Succeeded or Failed"
Jun 11 08:28:14.139: INFO: Trying to get logs from node ip-172-20-32-106.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-7v7q container test-container-subpath-dynamicpv-7v7q: <nil>
STEP: delete the pod
Jun 11 08:28:14.458: INFO: Waiting for pod pod-subpath-test-dynamicpv-7v7q to disappear
Jun 11 08:28:14.614: INFO: Pod pod-subpath-test-dynamicpv-7v7q no longer exists
STEP: Deleting pod
Jun 11 08:28:14.614: INFO: Deleting pod "pod-subpath-test-dynamicpv-7v7q" in namespace "provisioning-9600"
... skipping 62 lines ...
STEP: Deleting pod hostexec-ip-172-20-52-245.ap-northeast-2.compute.internal-jn6pf in namespace volumemode-6196
Jun 11 08:28:14.392: INFO: Deleting pod "pod-b66b0073-9d48-4b97-89b2-fa51891086a0" in namespace "volumemode-6196"
Jun 11 08:28:14.561: INFO: Wait up to 5m0s for pod "pod-b66b0073-9d48-4b97-89b2-fa51891086a0" to be fully deleted
STEP: Deleting pv and pvc
Jun 11 08:28:24.890: INFO: Deleting PersistentVolumeClaim "pvc-n89zt"
Jun 11 08:28:25.053: INFO: Deleting PersistentVolume "aws-dkh4g"
Jun 11 08:28:25.606: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-01352e79eea0933c3", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01352e79eea0933c3 is currently attached to i-0ea1ad87eb19c049d
	status code: 400, request id: c0b8e166-e2c6-4c58-8e0d-8b6fda02720b
Jun 11 08:28:31.423: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-01352e79eea0933c3", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01352e79eea0933c3 is currently attached to i-0ea1ad87eb19c049d
	status code: 400, request id: 9088600d-336c-49d6-93b2-5218e7f9e1cd
Jun 11 08:28:37.190: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-01352e79eea0933c3".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 08:28:37.190: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-6196" for this suite.
... skipping 133 lines ...
Jun 11 08:27:43.261: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9682ldjqz
STEP: creating a claim
Jun 11 08:27:43.421: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-sjhj
STEP: Creating a pod to test subpath
Jun 11 08:27:43.900: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-sjhj" in namespace "provisioning-9682" to be "Succeeded or Failed"
Jun 11 08:27:44.058: INFO: Pod "pod-subpath-test-dynamicpv-sjhj": Phase="Pending", Reason="", readiness=false. Elapsed: 157.928263ms
Jun 11 08:27:46.219: INFO: Pod "pod-subpath-test-dynamicpv-sjhj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.318522825s
Jun 11 08:27:48.378: INFO: Pod "pod-subpath-test-dynamicpv-sjhj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.477426393s
Jun 11 08:27:50.537: INFO: Pod "pod-subpath-test-dynamicpv-sjhj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.636374481s
Jun 11 08:27:52.696: INFO: Pod "pod-subpath-test-dynamicpv-sjhj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.795263198s
Jun 11 08:27:54.854: INFO: Pod "pod-subpath-test-dynamicpv-sjhj": Phase="Pending", Reason="", readiness=false. Elapsed: 10.953761327s
... skipping 2 lines ...
Jun 11 08:28:01.331: INFO: Pod "pod-subpath-test-dynamicpv-sjhj": Phase="Pending", Reason="", readiness=false. Elapsed: 17.430609727s
Jun 11 08:28:03.495: INFO: Pod "pod-subpath-test-dynamicpv-sjhj": Phase="Pending", Reason="", readiness=false. Elapsed: 19.594133952s
Jun 11 08:28:05.653: INFO: Pod "pod-subpath-test-dynamicpv-sjhj": Phase="Pending", Reason="", readiness=false. Elapsed: 21.752723445s
Jun 11 08:28:07.813: INFO: Pod "pod-subpath-test-dynamicpv-sjhj": Phase="Pending", Reason="", readiness=false. Elapsed: 23.9124751s
Jun 11 08:28:09.971: INFO: Pod "pod-subpath-test-dynamicpv-sjhj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.07068724s
STEP: Saw pod success
Jun 11 08:28:09.971: INFO: Pod "pod-subpath-test-dynamicpv-sjhj" satisfied condition "Succeeded or Failed"
Jun 11 08:28:10.129: INFO: Trying to get logs from node ip-172-20-52-245.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-sjhj container test-container-subpath-dynamicpv-sjhj: <nil>
STEP: delete the pod
Jun 11 08:28:10.456: INFO: Waiting for pod pod-subpath-test-dynamicpv-sjhj to disappear
Jun 11 08:28:10.613: INFO: Pod pod-subpath-test-dynamicpv-sjhj no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-sjhj
Jun 11 08:28:10.613: INFO: Deleting pod "pod-subpath-test-dynamicpv-sjhj" in namespace "provisioning-9682"
... skipping 40 lines ...
Jun 11 08:28:13.897: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-1951-e2e-scg6k74
STEP: creating a claim
Jun 11 08:28:14.058: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Jun 11 08:28:14.380: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 11 08:28:14.701: INFO: Error updating pvc ebs.csi.aws.com5jj8h: PersistentVolumeClaim "ebs.csi.aws.com5jj8h" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1951-e2e-scg6k74",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun 11 08:28:45.341: INFO: Error updating pvc ebs.csi.aws.com5jj8h: PersistentVolumeClaim "ebs.csi.aws.com5jj8h" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 95 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 08:28:03.765: 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.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 11 08:28:04.543: INFO: Creating resource for dynamic PV
Jun 11 08:28:04.543: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-3314-e2e-scdmw6w
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 11 08:28:11.648: INFO: Deleting pod "pod-0153d81e-e064-403d-99eb-a50c11309b28" in namespace "volumemode-3314"
Jun 11 08:28:11.806: INFO: Wait up to 5m0s for pod "pod-0153d81e-e064-403d-99eb-a50c11309b28" to be fully deleted
STEP: Deleting pvc
Jun 11 08:28:14.441: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comn6lp6"
Jun 11 08:28:14.599: INFO: Waiting up to 5m0s for PersistentVolume pvc-4aa667ae-8244-4c15-9ba5-15a553446df4 to get deleted
Jun 11 08:28:14.756: INFO: PersistentVolume pvc-4aa667ae-8244-4c15-9ba5-15a553446df4 found and phase=Released (156.888796ms)
... skipping 13 lines ...

• [SLOW TEST:47.562 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.XbNMA0Bbv/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.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 11 08:28:51.329: INFO: Driver ebs.csi.aws.com doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning
... skipping 54 lines ...
Jun 11 08:28:32.585: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-52062hbzf
STEP: creating a claim
Jun 11 08:28:32.756: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-pjpx
STEP: Creating a pod to test subpath
Jun 11 08:28:33.254: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-pjpx" in namespace "provisioning-5206" to be "Succeeded or Failed"
Jun 11 08:28:33.421: INFO: Pod "pod-subpath-test-dynamicpv-pjpx": Phase="Pending", Reason="", readiness=false. Elapsed: 167.401641ms
Jun 11 08:28:35.587: INFO: Pod "pod-subpath-test-dynamicpv-pjpx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.333704449s
Jun 11 08:28:37.756: INFO: Pod "pod-subpath-test-dynamicpv-pjpx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.502375393s
Jun 11 08:28:39.923: INFO: Pod "pod-subpath-test-dynamicpv-pjpx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.669052385s
Jun 11 08:28:42.089: INFO: Pod "pod-subpath-test-dynamicpv-pjpx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.835648893s
Jun 11 08:28:44.255: INFO: Pod "pod-subpath-test-dynamicpv-pjpx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 11.001396983s
STEP: Saw pod success
Jun 11 08:28:44.255: INFO: Pod "pod-subpath-test-dynamicpv-pjpx" satisfied condition "Succeeded or Failed"
Jun 11 08:28:44.420: INFO: Trying to get logs from node ip-172-20-42-74.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-pjpx container test-container-volume-dynamicpv-pjpx: <nil>
STEP: delete the pod
Jun 11 08:28:44.805: INFO: Waiting for pod pod-subpath-test-dynamicpv-pjpx to disappear
Jun 11 08:28:44.970: INFO: Pod pod-subpath-test-dynamicpv-pjpx no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-pjpx
Jun 11 08:28:44.970: INFO: Deleting pod "pod-subpath-test-dynamicpv-pjpx" in namespace "provisioning-5206"
... skipping 97 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.003 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.XbNMA0Bbv/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.XbNMA0Bbv/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.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 530 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 08:28:09.508: 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.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun 11 08:28:10.322: INFO: Creating resource for dynamic PV
Jun 11 08:28:10.322: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3130-e2e-sc4wh5q
STEP: creating a claim
Jun 11 08:28:10.486: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-sq58
STEP: Checking for subpath error in container status
Jun 11 08:28:27.303: INFO: Deleting pod "pod-subpath-test-dynamicpv-sq58" in namespace "provisioning-3130"
Jun 11 08:28:27.471: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-sq58" to be fully deleted
STEP: Deleting pod
Jun 11 08:28:37.796: INFO: Deleting pod "pod-subpath-test-dynamicpv-sq58" in namespace "provisioning-3130"
STEP: Deleting pvc
Jun 11 08:28:38.283: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comw55xn"
... skipping 15 lines ...

• [SLOW TEST:65.782 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.XbNMA0Bbv/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.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow]
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 11 08:29:15.291: INFO: Driver "ebs.csi.aws.com" does not support volume type "PreprovisionedPV" - skipping
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow]
... skipping 46 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.XbNMA0Bbv/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.XbNMA0Bbv/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.XbNMA0Bbv/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.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.XbNMA0Bbv/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.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.XbNMA0Bbv/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.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

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

    /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:92
------------------------------
... skipping 60 lines ...
Jun 11 08:26:27.938: INFO: Creating resource for dynamic PV
Jun 11 08:26:27.938: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-701-e2e-scf9l8b
STEP: creating a claim
Jun 11 08:26:28.099: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 11 08:26:28.578: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-kckw2" in namespace "snapshotting-701" to be "Succeeded or Failed"
Jun 11 08:26:28.737: INFO: Pod "pvc-snapshottable-tester-kckw2": Phase="Pending", Reason="", readiness=false. Elapsed: 158.41856ms
Jun 11 08:26:30.897: INFO: Pod "pvc-snapshottable-tester-kckw2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.318991934s
Jun 11 08:26:33.058: INFO: Pod "pvc-snapshottable-tester-kckw2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.479462755s
Jun 11 08:26:35.218: INFO: Pod "pvc-snapshottable-tester-kckw2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.639295739s
Jun 11 08:26:37.377: INFO: Pod "pvc-snapshottable-tester-kckw2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.798349818s
Jun 11 08:26:39.537: INFO: Pod "pvc-snapshottable-tester-kckw2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.958301335s
Jun 11 08:26:41.695: INFO: Pod "pvc-snapshottable-tester-kckw2": Phase="Pending", Reason="", readiness=false. Elapsed: 13.117130975s
Jun 11 08:26:43.854: INFO: Pod "pvc-snapshottable-tester-kckw2": Phase="Pending", Reason="", readiness=false. Elapsed: 15.275914573s
Jun 11 08:26:46.014: INFO: Pod "pvc-snapshottable-tester-kckw2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 17.435516693s
STEP: Saw pod success
Jun 11 08:26:46.014: INFO: Pod "pvc-snapshottable-tester-kckw2" satisfied condition "Succeeded or Failed"
Jun 11 08:26:46.334: INFO: Pod pvc-snapshottable-tester-kckw2 has the following logs: 
Jun 11 08:26:46.334: INFO: Deleting pod "pvc-snapshottable-tester-kckw2" in namespace "snapshotting-701"
Jun 11 08:26:46.500: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-kckw2" to be fully deleted
Jun 11 08:26:46.663: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comftcj2] to have phase Bound
Jun 11 08:26:46.823: INFO: PersistentVolumeClaim ebs.csi.aws.comftcj2 found and phase=Bound (160.336699ms)
STEP: [init] checking the claim
... skipping 17 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.XbNMA0Bbv/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 11 08:27:03.714: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-s4ttf" in namespace "snapshotting-701" to be "Succeeded or Failed"
Jun 11 08:27:03.873: INFO: Pod "pvc-snapshottable-data-tester-s4ttf": Phase="Pending", Reason="", readiness=false. Elapsed: 159.113463ms
Jun 11 08:27:06.033: INFO: Pod "pvc-snapshottable-data-tester-s4ttf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.318817255s
Jun 11 08:27:08.192: INFO: Pod "pvc-snapshottable-data-tester-s4ttf": Phase="Pending", Reason="", readiness=false. Elapsed: 4.477860499s
Jun 11 08:27:10.353: INFO: Pod "pvc-snapshottable-data-tester-s4ttf": Phase="Pending", Reason="", readiness=false. Elapsed: 6.638451442s
Jun 11 08:27:12.512: INFO: Pod "pvc-snapshottable-data-tester-s4ttf": Phase="Pending", Reason="", readiness=false. Elapsed: 8.797504937s
Jun 11 08:27:14.671: INFO: Pod "pvc-snapshottable-data-tester-s4ttf": Phase="Pending", Reason="", readiness=false. Elapsed: 10.956986973s
Jun 11 08:27:16.832: INFO: Pod "pvc-snapshottable-data-tester-s4ttf": Phase="Pending", Reason="", readiness=false. Elapsed: 13.117389607s
Jun 11 08:27:18.990: INFO: Pod "pvc-snapshottable-data-tester-s4ttf": Phase="Pending", Reason="", readiness=false. Elapsed: 15.276276165s
Jun 11 08:27:21.150: INFO: Pod "pvc-snapshottable-data-tester-s4ttf": Phase="Succeeded", Reason="", readiness=false. Elapsed: 17.435344789s
STEP: Saw pod success
Jun 11 08:27:21.150: INFO: Pod "pvc-snapshottable-data-tester-s4ttf" satisfied condition "Succeeded or Failed"
Jun 11 08:27:21.469: INFO: Pod pvc-snapshottable-data-tester-s4ttf has the following logs: 
Jun 11 08:27:21.469: INFO: Deleting pod "pvc-snapshottable-data-tester-s4ttf" in namespace "snapshotting-701"
Jun 11 08:27:21.635: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-s4ttf" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 11 08:28:00.432: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-701 exec restored-pvc-tester-mnhx8 --namespace=snapshotting-701 -- cat /mnt/test/data'
... skipping 29 lines ...
Jun 11 08:28:25.935: INFO: volumesnapshotcontents snapcontent-75f55731-7fea-4d45-b331-34d3a5d1038d has been found and is not deleted
Jun 11 08:28:27.095: INFO: volumesnapshotcontents snapcontent-75f55731-7fea-4d45-b331-34d3a5d1038d has been found and is not deleted
Jun 11 08:28:28.258: INFO: volumesnapshotcontents snapcontent-75f55731-7fea-4d45-b331-34d3a5d1038d has been found and is not deleted
Jun 11 08:28:29.420: INFO: volumesnapshotcontents snapcontent-75f55731-7fea-4d45-b331-34d3a5d1038d has been found and is not deleted
Jun 11 08:28:30.581: INFO: volumesnapshotcontents snapcontent-75f55731-7fea-4d45-b331-34d3a5d1038d has been found and is not deleted
Jun 11 08:28:31.741: INFO: volumesnapshotcontents snapcontent-75f55731-7fea-4d45-b331-34d3a5d1038d has been found and is not deleted
Jun 11 08:28:32.741: INFO: WaitUntil failed after reaching the timeout 30s
[AfterEach] volume snapshot controller
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:221
Jun 11 08:28:32.902: INFO: Pod restored-pvc-tester-mnhx8 has the following logs: 
Jun 11 08:28:32.902: INFO: Deleting pod "restored-pvc-tester-mnhx8" in namespace "snapshotting-701"
Jun 11 08:28:33.061: INFO: Wait up to 5m0s for pod "restored-pvc-tester-mnhx8" to be fully deleted
Jun 11 08:29:13.382: INFO: deleting claim "snapshotting-701"/"pvc-zbmwk"
... skipping 44 lines ...
Jun 11 08:26:21.216: INFO: Creating resource for dynamic PV
Jun 11 08:26:21.216: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-803-e2e-sc9rmwt
STEP: creating a claim
Jun 11 08:26:21.376: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 11 08:26:21.861: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-ngwq8" in namespace "snapshotting-803" to be "Succeeded or Failed"
Jun 11 08:26:22.021: INFO: Pod "pvc-snapshottable-tester-ngwq8": Phase="Pending", Reason="", readiness=false. Elapsed: 159.39652ms
Jun 11 08:26:24.182: INFO: Pod "pvc-snapshottable-tester-ngwq8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.320565275s
Jun 11 08:26:26.342: INFO: Pod "pvc-snapshottable-tester-ngwq8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.480297337s
Jun 11 08:26:28.502: INFO: Pod "pvc-snapshottable-tester-ngwq8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.640843879s
Jun 11 08:26:30.663: INFO: Pod "pvc-snapshottable-tester-ngwq8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.801323611s
Jun 11 08:26:32.823: INFO: Pod "pvc-snapshottable-tester-ngwq8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.961937251s
STEP: Saw pod success
Jun 11 08:26:32.824: INFO: Pod "pvc-snapshottable-tester-ngwq8" satisfied condition "Succeeded or Failed"
Jun 11 08:26:33.155: INFO: Pod pvc-snapshottable-tester-ngwq8 has the following logs: 
Jun 11 08:26:33.155: INFO: Deleting pod "pvc-snapshottable-tester-ngwq8" in namespace "snapshotting-803"
Jun 11 08:26:33.321: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-ngwq8" to be fully deleted
Jun 11 08:26:33.481: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comb68v8] to have phase Bound
Jun 11 08:26:33.641: INFO: PersistentVolumeClaim ebs.csi.aws.comb68v8 found and phase=Bound (160.444956ms)
STEP: [init] checking the claim
... skipping 43 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.XbNMA0Bbv/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 11 08:27:09.440: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-4fpg2" in namespace "snapshotting-803" to be "Succeeded or Failed"
Jun 11 08:27:09.599: INFO: Pod "pvc-snapshottable-data-tester-4fpg2": Phase="Pending", Reason="", readiness=false. Elapsed: 159.135741ms
Jun 11 08:27:11.759: INFO: Pod "pvc-snapshottable-data-tester-4fpg2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.318889833s
Jun 11 08:27:13.919: INFO: Pod "pvc-snapshottable-data-tester-4fpg2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.479338145s
Jun 11 08:27:16.080: INFO: Pod "pvc-snapshottable-data-tester-4fpg2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.639484646s
Jun 11 08:27:18.241: INFO: Pod "pvc-snapshottable-data-tester-4fpg2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.800695653s
STEP: Saw pod success
Jun 11 08:27:18.241: INFO: Pod "pvc-snapshottable-data-tester-4fpg2" satisfied condition "Succeeded or Failed"
Jun 11 08:27:18.562: INFO: Pod pvc-snapshottable-data-tester-4fpg2 has the following logs: 
Jun 11 08:27:18.562: INFO: Deleting pod "pvc-snapshottable-data-tester-4fpg2" in namespace "snapshotting-803"
Jun 11 08:27:18.728: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-4fpg2" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 11 08:28:01.529: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-803 exec restored-pvc-tester-v7qgl --namespace=snapshotting-803 -- cat /mnt/test/data'
... skipping 29 lines ...
Jun 11 08:28:27.138: INFO: volumesnapshotcontents pre-provisioned-snapcontent-e2552653-1435-44f5-bafe-bf34f6708b4d has been found and is not deleted
Jun 11 08:28:28.298: INFO: volumesnapshotcontents pre-provisioned-snapcontent-e2552653-1435-44f5-bafe-bf34f6708b4d has been found and is not deleted
Jun 11 08:28:29.458: INFO: volumesnapshotcontents pre-provisioned-snapcontent-e2552653-1435-44f5-bafe-bf34f6708b4d has been found and is not deleted
Jun 11 08:28:30.619: INFO: volumesnapshotcontents pre-provisioned-snapcontent-e2552653-1435-44f5-bafe-bf34f6708b4d has been found and is not deleted
Jun 11 08:28:31.779: INFO: volumesnapshotcontents pre-provisioned-snapcontent-e2552653-1435-44f5-bafe-bf34f6708b4d has been found and is not deleted
Jun 11 08:28:32.939: INFO: volumesnapshotcontents pre-provisioned-snapcontent-e2552653-1435-44f5-bafe-bf34f6708b4d has been found and is not deleted
Jun 11 08:28:33.940: INFO: WaitUntil failed after reaching the timeout 30s
[AfterEach] volume snapshot controller
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:221
Jun 11 08:28:34.101: INFO: Pod restored-pvc-tester-v7qgl has the following logs: 
Jun 11 08:28:34.101: INFO: Deleting pod "restored-pvc-tester-v7qgl" in namespace "snapshotting-803"
Jun 11 08:28:34.262: INFO: Wait up to 5m0s for pod "restored-pvc-tester-v7qgl" to be fully deleted
Jun 11 08:29:14.581: INFO: deleting claim "snapshotting-803"/"pvc-rqfkh"
... skipping 131 lines ...
Jun 11 08:29:20.783: INFO: Waiting for pod aws-client to disappear
Jun 11 08:29:20.938: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 11 08:29:20.940: INFO: Deleting PersistentVolumeClaim "pvc-czhmj"
Jun 11 08:29:21.095: INFO: Deleting PersistentVolume "aws-f8zrm"
Jun 11 08:29:22.094: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-08d92404587595265", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08d92404587595265 is currently attached to i-0e84919ee5c68a920
	status code: 400, request id: aa77ff37-e2a7-4f30-8c5c-633c437018c5
Jun 11 08:29:27.903: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-08d92404587595265".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 08:29:27.903: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-742" for this suite.
... skipping 147 lines ...
Jun 11 08:29:23.968: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-45349hblp
STEP: creating a claim
Jun 11 08:29:24.127: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-h9bs
STEP: Creating a pod to test exec-volume-test
Jun 11 08:29:24.609: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-h9bs" in namespace "volume-4534" to be "Succeeded or Failed"
Jun 11 08:29:24.768: INFO: Pod "exec-volume-test-dynamicpv-h9bs": Phase="Pending", Reason="", readiness=false. Elapsed: 158.775511ms
Jun 11 08:29:26.931: INFO: Pod "exec-volume-test-dynamicpv-h9bs": Phase="Pending", Reason="", readiness=false. Elapsed: 2.321761449s
Jun 11 08:29:29.091: INFO: Pod "exec-volume-test-dynamicpv-h9bs": Phase="Pending", Reason="", readiness=false. Elapsed: 4.481723495s
Jun 11 08:29:31.250: INFO: Pod "exec-volume-test-dynamicpv-h9bs": Phase="Pending", Reason="", readiness=false. Elapsed: 6.640827696s
Jun 11 08:29:33.411: INFO: Pod "exec-volume-test-dynamicpv-h9bs": Phase="Pending", Reason="", readiness=false. Elapsed: 8.802168341s
Jun 11 08:29:35.571: INFO: Pod "exec-volume-test-dynamicpv-h9bs": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.961771185s
STEP: Saw pod success
Jun 11 08:29:35.571: INFO: Pod "exec-volume-test-dynamicpv-h9bs" satisfied condition "Succeeded or Failed"
Jun 11 08:29:35.730: INFO: Trying to get logs from node ip-172-20-46-76.ap-northeast-2.compute.internal pod exec-volume-test-dynamicpv-h9bs container exec-container-dynamicpv-h9bs: <nil>
STEP: delete the pod
Jun 11 08:29:36.063: INFO: Waiting for pod exec-volume-test-dynamicpv-h9bs to disappear
Jun 11 08:29:36.221: INFO: Pod exec-volume-test-dynamicpv-h9bs no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-h9bs
Jun 11 08:29:36.221: INFO: Deleting pod "exec-volume-test-dynamicpv-h9bs" in namespace "volume-4534"
... skipping 345 lines ...
Jun 11 08:29:44.456: INFO: Pod aws-client still exists
Jun 11 08:29:46.456: INFO: Waiting for pod aws-client to disappear
Jun 11 08:29:46.617: INFO: Pod aws-client still exists
Jun 11 08:29:48.456: INFO: Waiting for pod aws-client to disappear
Jun 11 08:29:48.616: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun 11 08:29:49.384: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-01538da967d821b1b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01538da967d821b1b is currently attached to i-02cb721efd2472d6a
	status code: 400, request id: 74d3fe26-2f18-4fee-b4d2-64958955a714
Jun 11 08:29:55.344: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-01538da967d821b1b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01538da967d821b1b is currently attached to i-02cb721efd2472d6a
	status code: 400, request id: 1eada208-b46b-4725-860a-2f29798fd25f
Jun 11 08:30:01.135: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-01538da967d821b1b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01538da967d821b1b is currently attached to i-02cb721efd2472d6a
	status code: 400, request id: 7f1565eb-ca17-4664-a748-4d18d6a01e7d
Jun 11 08:30:06.937: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-01538da967d821b1b".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 08:30:06.938: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-9169" for this suite.
... skipping 87 lines ...

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

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

    /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 154 lines ...
Jun 11 08:29:34.298: INFO: PersistentVolumeClaim pvc-dws67 found but phase is Pending instead of Bound.
Jun 11 08:29:36.454: INFO: PersistentVolumeClaim pvc-dws67 found and phase=Bound (6.623747965s)
Jun 11 08:29:36.454: INFO: Waiting up to 3m0s for PersistentVolume aws-5524q to have phase Bound
Jun 11 08:29:36.617: INFO: PersistentVolume aws-5524q found and phase=Bound (162.907311ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-gfwd
STEP: Creating a pod to test exec-volume-test
Jun 11 08:29:37.086: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-gfwd" in namespace "volume-5113" to be "Succeeded or Failed"
Jun 11 08:29:37.241: INFO: Pod "exec-volume-test-preprovisionedpv-gfwd": Phase="Pending", Reason="", readiness=false. Elapsed: 155.115925ms
Jun 11 08:29:39.397: INFO: Pod "exec-volume-test-preprovisionedpv-gfwd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.310663801s
Jun 11 08:29:41.553: INFO: Pod "exec-volume-test-preprovisionedpv-gfwd": Phase="Pending", Reason="", readiness=false. Elapsed: 4.466959436s
Jun 11 08:29:43.710: INFO: Pod "exec-volume-test-preprovisionedpv-gfwd": Phase="Pending", Reason="", readiness=false. Elapsed: 6.624064254s
Jun 11 08:29:45.866: INFO: Pod "exec-volume-test-preprovisionedpv-gfwd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.779475051s
STEP: Saw pod success
Jun 11 08:29:45.866: INFO: Pod "exec-volume-test-preprovisionedpv-gfwd" satisfied condition "Succeeded or Failed"
Jun 11 08:29:46.021: INFO: Trying to get logs from node ip-172-20-46-76.ap-northeast-2.compute.internal pod exec-volume-test-preprovisionedpv-gfwd container exec-container-preprovisionedpv-gfwd: <nil>
STEP: delete the pod
Jun 11 08:29:46.339: INFO: Waiting for pod exec-volume-test-preprovisionedpv-gfwd to disappear
Jun 11 08:29:46.495: INFO: Pod exec-volume-test-preprovisionedpv-gfwd no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-gfwd
Jun 11 08:29:46.495: INFO: Deleting pod "exec-volume-test-preprovisionedpv-gfwd" in namespace "volume-5113"
STEP: Deleting pv and pvc
Jun 11 08:29:46.651: INFO: Deleting PersistentVolumeClaim "pvc-dws67"
Jun 11 08:29:46.811: INFO: Deleting PersistentVolume "aws-5524q"
Jun 11 08:29:47.311: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0ffd895fd75b1faf0", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ffd895fd75b1faf0 is currently attached to i-0e84919ee5c68a920
	status code: 400, request id: 34cfca66-eff3-41a3-aaa0-30a65fe5a42a
Jun 11 08:29:53.057: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0ffd895fd75b1faf0", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ffd895fd75b1faf0 is currently attached to i-0e84919ee5c68a920
	status code: 400, request id: 29e800cc-557e-4ea3-84a6-17a1e330e756
Jun 11 08:29:58.865: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0ffd895fd75b1faf0", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ffd895fd75b1faf0 is currently attached to i-0e84919ee5c68a920
	status code: 400, request id: 9663ba60-5c6b-4899-8e96-3e152eb9c51e
Jun 11 08:30:04.638: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0ffd895fd75b1faf0", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ffd895fd75b1faf0 is currently attached to i-0e84919ee5c68a920
	status code: 400, request id: 22730658-efc4-4695-85d5-9b6cc25d3235
Jun 11 08:30:10.432: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-0ffd895fd75b1faf0".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 08:30:10.432: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-5113" for this suite.
... skipping 244 lines ...

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

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

    /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:92
------------------------------
... skipping 1081 lines ...
Jun 11 08:27:53.008: INFO: Creating resource for dynamic PV
Jun 11 08:27:53.008: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-5508-e2e-scb8cf6
STEP: creating a claim
Jun 11 08:27:53.169: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 11 08:27:53.655: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-txkx6" in namespace "snapshotting-5508" to be "Succeeded or Failed"
Jun 11 08:27:53.818: INFO: Pod "pvc-snapshottable-tester-txkx6": Phase="Pending", Reason="", readiness=false. Elapsed: 162.717375ms
Jun 11 08:27:55.979: INFO: Pod "pvc-snapshottable-tester-txkx6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.323511653s
Jun 11 08:27:58.139: INFO: Pod "pvc-snapshottable-tester-txkx6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.483410695s
Jun 11 08:28:00.300: INFO: Pod "pvc-snapshottable-tester-txkx6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.645249988s
Jun 11 08:28:02.461: INFO: Pod "pvc-snapshottable-tester-txkx6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.805972895s
STEP: Saw pod success
Jun 11 08:28:02.461: INFO: Pod "pvc-snapshottable-tester-txkx6" satisfied condition "Succeeded or Failed"
Jun 11 08:28:02.783: INFO: Pod pvc-snapshottable-tester-txkx6 has the following logs: 
Jun 11 08:28:02.783: INFO: Deleting pod "pvc-snapshottable-tester-txkx6" in namespace "snapshotting-5508"
Jun 11 08:28:02.951: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-txkx6" to be fully deleted
Jun 11 08:28:03.110: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comcpqcs] to have phase Bound
Jun 11 08:28:03.269: INFO: PersistentVolumeClaim ebs.csi.aws.comcpqcs found and phase=Bound (159.368013ms)
STEP: [init] checking the claim
... skipping 35 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.XbNMA0Bbv/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 11 08:28:59.085: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-nstvc" in namespace "snapshotting-5508" to be "Succeeded or Failed"
Jun 11 08:28:59.245: INFO: Pod "pvc-snapshottable-data-tester-nstvc": Phase="Pending", Reason="", readiness=false. Elapsed: 159.486203ms
Jun 11 08:29:01.404: INFO: Pod "pvc-snapshottable-data-tester-nstvc": Phase="Pending", Reason="", readiness=false. Elapsed: 2.319397864s
Jun 11 08:29:03.566: INFO: Pod "pvc-snapshottable-data-tester-nstvc": Phase="Pending", Reason="", readiness=false. Elapsed: 4.480459393s
Jun 11 08:29:05.725: INFO: Pod "pvc-snapshottable-data-tester-nstvc": Phase="Pending", Reason="", readiness=false. Elapsed: 6.640388244s
Jun 11 08:29:07.886: INFO: Pod "pvc-snapshottable-data-tester-nstvc": Phase="Pending", Reason="", readiness=false. Elapsed: 8.800477596s
Jun 11 08:29:10.045: INFO: Pod "pvc-snapshottable-data-tester-nstvc": Phase="Pending", Reason="", readiness=false. Elapsed: 10.960294999s
Jun 11 08:29:12.207: INFO: Pod "pvc-snapshottable-data-tester-nstvc": Phase="Pending", Reason="", readiness=false. Elapsed: 13.121918264s
Jun 11 08:29:14.367: INFO: Pod "pvc-snapshottable-data-tester-nstvc": Phase="Pending", Reason="", readiness=false. Elapsed: 15.282309744s
Jun 11 08:29:16.529: INFO: Pod "pvc-snapshottable-data-tester-nstvc": Phase="Pending", Reason="", readiness=false. Elapsed: 17.443545512s
Jun 11 08:29:18.713: INFO: Pod "pvc-snapshottable-data-tester-nstvc": Phase="Pending", Reason="", readiness=false. Elapsed: 19.628221064s
Jun 11 08:29:20.873: INFO: Pod "pvc-snapshottable-data-tester-nstvc": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.788074606s
STEP: Saw pod success
Jun 11 08:29:20.874: INFO: Pod "pvc-snapshottable-data-tester-nstvc" satisfied condition "Succeeded or Failed"
Jun 11 08:29:21.197: INFO: Pod pvc-snapshottable-data-tester-nstvc has the following logs: 
Jun 11 08:29:21.197: INFO: Deleting pod "pvc-snapshottable-data-tester-nstvc" in namespace "snapshotting-5508"
Jun 11 08:29:21.362: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-nstvc" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 11 08:30:00.163: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-5508 exec restored-pvc-tester-rvxgd --namespace=snapshotting-5508 -- cat /mnt/test/data'
... skipping 43 lines ...
Jun 11 08:30:54.020: INFO: At 2021-06-11 08:29:19 +0000 UTC - event for pvc-snapshottable-data-tester-nstvc: {kubelet ip-172-20-52-245.ap-northeast-2.compute.internal} Created: Created container volume-tester
Jun 11 08:30:54.020: INFO: At 2021-06-11 08:29:19 +0000 UTC - event for pvc-snapshottable-data-tester-nstvc: {kubelet ip-172-20-52-245.ap-northeast-2.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" already present on machine
Jun 11 08:30:54.020: INFO: At 2021-06-11 08:29:21 +0000 UTC - event for pvc-dfqbr: {persistentvolume-controller } WaitForFirstConsumer: waiting for first consumer to be created before binding
Jun 11 08:30:54.021: INFO: At 2021-06-11 08:29:21 +0000 UTC - event for pvc-dfqbr: {persistentvolume-controller } ExternalProvisioning: waiting for a volume to be created, either by external provisioner "ebs.csi.aws.com" or manually created by system administrator
Jun 11 08:30:54.021: INFO: At 2021-06-11 08:29:21 +0000 UTC - event for pvc-dfqbr: {ebs.csi.aws.com_ebs-csi-controller-7ffff4ddf5-dmpxz_0467b11b-ed9c-444a-979f-a6da430cfb7a } Provisioning: External provisioner is provisioning volume for claim "snapshotting-5508/pvc-dfqbr"
Jun 11 08:30:54.021: INFO: At 2021-06-11 08:29:25 +0000 UTC - event for pvc-dfqbr: {ebs.csi.aws.com_ebs-csi-controller-7ffff4ddf5-dmpxz_0467b11b-ed9c-444a-979f-a6da430cfb7a } ProvisioningSucceeded: Successfully provisioned volume pvc-1ca21764-ea58-4508-b711-f1a95b9db865
Jun 11 08:30:54.021: INFO: At 2021-06-11 08:29:43 +0000 UTC - event for restored-pvc-tester-rvxgd: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-1ca21764-ea58-4508-b711-f1a95b9db865" : rpc error: code = Internal desc = Could not attach volume "vol-0c26fa8cf6781c5e1" to node "i-0ea1ad87eb19c049d": attachment of disk "vol-0c26fa8cf6781c5e1" failed, expected device to be attached but was attaching
Jun 11 08:30:54.021: INFO: At 2021-06-11 08:29:49 +0000 UTC - event for restored-pvc-tester-rvxgd: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-1ca21764-ea58-4508-b711-f1a95b9db865" 
Jun 11 08:30:54.021: INFO: At 2021-06-11 08:29:58 +0000 UTC - event for restored-pvc-tester-rvxgd: {kubelet ip-172-20-52-245.ap-northeast-2.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" already present on machine
Jun 11 08:30:54.021: INFO: At 2021-06-11 08:29:58 +0000 UTC - event for restored-pvc-tester-rvxgd: {kubelet ip-172-20-52-245.ap-northeast-2.compute.internal} Created: Created container volume-tester
Jun 11 08:30:54.021: INFO: At 2021-06-11 08:29:58 +0000 UTC - event for restored-pvc-tester-rvxgd: {kubelet ip-172-20-52-245.ap-northeast-2.compute.internal} Started: Started container volume-tester
Jun 11 08:30:54.021: INFO: At 2021-06-11 08:30:02 +0000 UTC - event for restored-pvc-tester-rvxgd: {kubelet ip-172-20-52-245.ap-northeast-2.compute.internal} Killing: Stopping container volume-tester
Jun 11 08:30:54.181: INFO: POD  NODE  PHASE  GRACE  CONDITIONS
... skipping 208 lines ...
    /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:108
      
      /tmp/kops.XbNMA0Bbv/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.XbNMA0Bbv/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-5508 exec restored-pvc-tester-rvxgd --namespace=snapshotting-5508 -- 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-5508 exec restored-pvc-tester-rvxgd --namespace=snapshotting-5508 -- 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.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:602
------------------------------
[BeforeEach] [sig-storage] Zone Support [Feature:vsphere]
... skipping 459 lines ...
STEP: Deleting pod hostexec-ip-172-20-42-74.ap-northeast-2.compute.internal-bkv46 in namespace volumemode-4215
Jun 11 08:30:59.544: INFO: Deleting pod "pod-29943acd-eec9-443f-b13a-b0b9db7ff35d" in namespace "volumemode-4215"
Jun 11 08:30:59.713: INFO: Wait up to 5m0s for pod "pod-29943acd-eec9-443f-b13a-b0b9db7ff35d" to be fully deleted
STEP: Deleting pv and pvc
Jun 11 08:31:08.033: INFO: Deleting PersistentVolumeClaim "pvc-bpbsx"
Jun 11 08:31:08.193: INFO: Deleting PersistentVolume "aws-zfh4s"
Jun 11 08:31:08.621: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-07f6624385280e6d5", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07f6624385280e6d5 is currently attached to i-08d25eceed8edefec
	status code: 400, request id: a5729664-8d35-47b4-a0ae-d6dcf926d6a9
Jun 11 08:31:14.450: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-07f6624385280e6d5".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 08:31:14.450: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-4215" for this suite.
... skipping 288 lines ...
Jun 11 08:30:35.772: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7345skl6v
STEP: creating a claim
Jun 11 08:30:35.930: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-zlq4
STEP: Creating a pod to test subpath
Jun 11 08:30:36.412: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-zlq4" in namespace "provisioning-7345" to be "Succeeded or Failed"
Jun 11 08:30:36.582: INFO: Pod "pod-subpath-test-dynamicpv-zlq4": Phase="Pending", Reason="", readiness=false. Elapsed: 170.191064ms
Jun 11 08:30:38.741: INFO: Pod "pod-subpath-test-dynamicpv-zlq4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.328561131s
Jun 11 08:30:40.900: INFO: Pod "pod-subpath-test-dynamicpv-zlq4": Phase="Pending", Reason="", readiness=false. Elapsed: 4.487573305s
Jun 11 08:30:43.059: INFO: Pod "pod-subpath-test-dynamicpv-zlq4": Phase="Pending", Reason="", readiness=false. Elapsed: 6.647074997s
Jun 11 08:30:45.221: INFO: Pod "pod-subpath-test-dynamicpv-zlq4": Phase="Pending", Reason="", readiness=false. Elapsed: 8.808460976s
Jun 11 08:30:47.380: INFO: Pod "pod-subpath-test-dynamicpv-zlq4": Phase="Pending", Reason="", readiness=false. Elapsed: 10.967748221s
Jun 11 08:30:49.538: INFO: Pod "pod-subpath-test-dynamicpv-zlq4": Phase="Pending", Reason="", readiness=false. Elapsed: 13.126138908s
Jun 11 08:30:51.697: INFO: Pod "pod-subpath-test-dynamicpv-zlq4": Phase="Pending", Reason="", readiness=false. Elapsed: 15.285306609s
Jun 11 08:30:53.856: INFO: Pod "pod-subpath-test-dynamicpv-zlq4": Phase="Pending", Reason="", readiness=false. Elapsed: 17.443595582s
Jun 11 08:30:56.015: INFO: Pod "pod-subpath-test-dynamicpv-zlq4": Phase="Pending", Reason="", readiness=false. Elapsed: 19.602439648s
Jun 11 08:30:58.174: INFO: Pod "pod-subpath-test-dynamicpv-zlq4": Phase="Pending", Reason="", readiness=false. Elapsed: 21.761667782s
Jun 11 08:31:00.336: INFO: Pod "pod-subpath-test-dynamicpv-zlq4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.923902163s
STEP: Saw pod success
Jun 11 08:31:00.336: INFO: Pod "pod-subpath-test-dynamicpv-zlq4" satisfied condition "Succeeded or Failed"
Jun 11 08:31:00.494: INFO: Trying to get logs from node ip-172-20-46-76.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-zlq4 container test-container-volume-dynamicpv-zlq4: <nil>
STEP: delete the pod
Jun 11 08:31:00.831: INFO: Waiting for pod pod-subpath-test-dynamicpv-zlq4 to disappear
Jun 11 08:31:00.989: INFO: Pod pod-subpath-test-dynamicpv-zlq4 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-zlq4
Jun 11 08:31:00.989: INFO: Deleting pod "pod-subpath-test-dynamicpv-zlq4" in namespace "provisioning-7345"
... skipping 125 lines ...
Jun 11 08:30:46.378: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6238-e2e-sc7bp69
STEP: creating a claim
Jun 11 08:30:46.536: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-fj75
STEP: Creating a pod to test subpath
Jun 11 08:30:47.018: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-fj75" in namespace "provisioning-6238" to be "Succeeded or Failed"
Jun 11 08:30:47.175: INFO: Pod "pod-subpath-test-dynamicpv-fj75": Phase="Pending", Reason="", readiness=false. Elapsed: 157.16526ms
Jun 11 08:30:49.334: INFO: Pod "pod-subpath-test-dynamicpv-fj75": Phase="Pending", Reason="", readiness=false. Elapsed: 2.315996735s
Jun 11 08:30:51.494: INFO: Pod "pod-subpath-test-dynamicpv-fj75": Phase="Pending", Reason="", readiness=false. Elapsed: 4.475942046s
Jun 11 08:30:53.658: INFO: Pod "pod-subpath-test-dynamicpv-fj75": Phase="Pending", Reason="", readiness=false. Elapsed: 6.640121386s
Jun 11 08:30:55.816: INFO: Pod "pod-subpath-test-dynamicpv-fj75": Phase="Pending", Reason="", readiness=false. Elapsed: 8.797826697s
Jun 11 08:30:57.974: INFO: Pod "pod-subpath-test-dynamicpv-fj75": Phase="Pending", Reason="", readiness=false. Elapsed: 10.95585604s
Jun 11 08:31:00.132: INFO: Pod "pod-subpath-test-dynamicpv-fj75": Phase="Pending", Reason="", readiness=false. Elapsed: 13.114139907s
Jun 11 08:31:02.290: INFO: Pod "pod-subpath-test-dynamicpv-fj75": Phase="Succeeded", Reason="", readiness=false. Elapsed: 15.271485743s
STEP: Saw pod success
Jun 11 08:31:02.290: INFO: Pod "pod-subpath-test-dynamicpv-fj75" satisfied condition "Succeeded or Failed"
Jun 11 08:31:02.447: INFO: Trying to get logs from node ip-172-20-32-106.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-fj75 container test-container-subpath-dynamicpv-fj75: <nil>
STEP: delete the pod
Jun 11 08:31:02.772: INFO: Waiting for pod pod-subpath-test-dynamicpv-fj75 to disappear
Jun 11 08:31:02.929: INFO: Pod pod-subpath-test-dynamicpv-fj75 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-fj75
Jun 11 08:31:02.929: INFO: Deleting pod "pod-subpath-test-dynamicpv-fj75" in namespace "provisioning-6238"
... skipping 30 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 08:30:31.297: 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.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun 11 08:30:32.076: INFO: Creating resource for dynamic PV
Jun 11 08:30:32.076: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-311-e2e-schzd8k
STEP: creating a claim
Jun 11 08:30:32.233: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-wmxk
STEP: Checking for subpath error in container status
Jun 11 08:30:59.019: INFO: Deleting pod "pod-subpath-test-dynamicpv-wmxk" in namespace "provisioning-311"
Jun 11 08:30:59.176: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-wmxk" to be fully deleted
STEP: Deleting pod
Jun 11 08:31:05.491: INFO: Deleting pod "pod-subpath-test-dynamicpv-wmxk" in namespace "provisioning-311"
STEP: Deleting pvc
Jun 11 08:31:05.962: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com9ws9s"
... skipping 15 lines ...

• [SLOW TEST:71.550 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath file is outside the volume [Slow][LinuxOnly]
    /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 08:30:56.663: 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.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 11 08:30:57.479: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 11 08:30:58.420: INFO: Successfully created a new PD: "aws://ap-northeast-2a/vol-07a062454c37ea72d".
Jun 11 08:30:58.420: INFO: Creating resource for pre-provisioned PV
Jun 11 08:30:58.420: INFO: Creating PVC and PV
... skipping 4 lines ...
Jun 11 08:31:01.136: INFO: PersistentVolumeClaim pvc-ghh6g found but phase is Pending instead of Bound.
Jun 11 08:31:03.296: INFO: PersistentVolumeClaim pvc-ghh6g found but phase is Pending instead of Bound.
Jun 11 08:31:05.457: INFO: PersistentVolumeClaim pvc-ghh6g found and phase=Bound (6.640976503s)
Jun 11 08:31:05.457: INFO: Waiting up to 3m0s for PersistentVolume aws-6crrw to have phase Bound
Jun 11 08:31:05.617: INFO: PersistentVolume aws-6crrw found and phase=Bound (159.40293ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 11 08:31:08.580: INFO: Deleting pod "pod-adc60361-d496-4f5c-9442-ade05342159e" in namespace "volumemode-4919"
Jun 11 08:31:08.741: INFO: Wait up to 5m0s for pod "pod-adc60361-d496-4f5c-9442-ade05342159e" to be fully deleted
STEP: Deleting pv and pvc
Jun 11 08:31:15.062: INFO: Deleting PersistentVolumeClaim "pvc-ghh6g"
Jun 11 08:31:15.224: INFO: Deleting PersistentVolume "aws-6crrw"
Jun 11 08:31:15.687: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-07a062454c37ea72d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07a062454c37ea72d is currently attached to i-0ea1ad87eb19c049d
	status code: 400, request id: 79761956-dee0-4e8e-bb3e-36b431b9f171
Jun 11 08:31:21.444: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-07a062454c37ea72d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07a062454c37ea72d is currently attached to i-0ea1ad87eb19c049d
	status code: 400, request id: a9702853-6b30-4177-82c2-ae16629ea6a9
Jun 11 08:31:27.188: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-07a062454c37ea72d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07a062454c37ea72d is currently attached to i-0ea1ad87eb19c049d
	status code: 400, request id: 4470aa19-fb1a-4bf9-ad27-110dfd389d97
Jun 11 08:31:32.959: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-07a062454c37ea72d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07a062454c37ea72d is currently attached to i-0ea1ad87eb19c049d
	status code: 400, request id: 889d3908-b67e-429d-9557-a156313a71f7
Jun 11 08:31:38.781: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-07a062454c37ea72d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07a062454c37ea72d is currently attached to i-0ea1ad87eb19c049d
	status code: 400, request id: 6c395268-ea43-4ca9-9739-159646ece2c0
Jun 11 08:31:44.570: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-07a062454c37ea72d".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 08:31:44.570: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-4919" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.XbNMA0Bbv/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.XbNMA0Bbv/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
    /tmp/kops.XbNMA0Bbv/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.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] provisioning
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] provisioning
  /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 1046 lines ...
    /tmp/kops.XbNMA0Bbv/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/provisioning.go:200
------------------------------


Summarizing 1 Failure:

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

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


Ginkgo ran 1 suite in 11m19.839692494s
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
I0611 08:33:14.960659   29022 app.go:59] RunDir for this run: "/logs/artifacts/b3894ab2-ca8b-11eb-ab6f-62c732df09e9"
I0611 08:33:14.960870   29022 app.go:90] ID for this run: "b3894ab2-ca8b-11eb-ab6f-62c732df09e9"
I0611 08:33:14.960898   29022 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
I0611 08:33:14.975443   29028 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
... skipping 1459 lines ...