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

No Test Failures!


Error lines from build-log.txt

... skipping 493 lines ...
I0612 16:10:49.708469   11698 up.go:43] Cleaning up any leaked resources from previous cluster
I0612 16:10:49.708524   11698 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
I0612 16:10:49.734078   11704 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0612 16:10:49.735623   11704 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io" not found
W0612 16:10:50.279989   11698 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0612 16:10:50.280102   11698 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
I0612 16:10:50.313888   11715 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0612 16:10:50.314270   11715 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

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

I0612 16:11:21.853342   11698 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
I0612 16:11:21.889459   11750 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0612 16:11:21.889705   11750 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io

W0612 16:11:23.662739   11750 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
W0612 16:11:33.701320   11750 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
W0612 16:11:43.808836   11750 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
W0612 16:11:53.855031   11750 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
W0612 16:12:03.885649   11750 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
W0612 16:12:13.916691   11750 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
W0612 16:12:23.949393   11750 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
W0612 16:12:33.977928   11750 validate_cluster.go:221] (will retry): cluster not yet healthy
W0612 16:12:43.998369   11750 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
W0612 16:12:54.035697   11750 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
W0612 16:13:04.071846   11750 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
W0612 16:13:14.127308   11750 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
W0612 16:13:24.158250   11750 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
W0612 16:13:34.212645   11750 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
W0612 16:13:44.257617   11750 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
W0612 16:13:54.295111   11750 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
W0612 16:14:04.329684   11750 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
W0612 16:14:14.362860   11750 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
W0612 16:14:24.409948   11750 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
W0612 16:14:34.443717   11750 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
W0612 16:14:44.479884   11750 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
W0612 16:14:54.511320   11750 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
W0612 16:15:04.560555   11750 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
W0612 16:15:14.627431   11750 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
W0612 16:15:24.668796   11750 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
W0612 16:15:34.701087   11750 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
W0612 16:15:44.744555   11750 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
W0612 16:15:54.778467   11750 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
W0612 16:16:04.826698   11750 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
W0612 16:16:14.861660   11750 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
W0612 16:16:24.908680   11750 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
W0612 16:16:34.946980   11750 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/cert-manager-webhook-7bbf67968-s5vth	system-cluster-critical pod "cert-manager-webhook-7bbf67968-s5vth" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-fddbg		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fddbg" is pending
Pod	kube-system/coredns-f45c4bf76-hc2p4			system-cluster-critical pod "coredns-f45c4bf76-hc2p4" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-5dq2p		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-5dq2p" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-gddc8		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-gddc8" is pending

Validation Failed
W0612 16:16:48.534582   11750 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 12 lines ...
Pod	kube-system/cert-manager-webhook-7bbf67968-s5vth	system-cluster-critical pod "cert-manager-webhook-7bbf67968-s5vth" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-fddbg		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fddbg" is pending
Pod	kube-system/coredns-f45c4bf76-hc2p4			system-cluster-critical pod "coredns-f45c4bf76-hc2p4" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-5dq2p		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-5dq2p" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-gddc8		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-gddc8" is pending

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

... skipping 11 lines ...
Pod	kube-system/cert-manager-webhook-7bbf67968-s5vth	system-cluster-critical pod "cert-manager-webhook-7bbf67968-s5vth" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-fddbg		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fddbg" is pending
Pod	kube-system/coredns-f45c4bf76-hc2p4			system-cluster-critical pod "coredns-f45c4bf76-hc2p4" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-5dq2p		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-5dq2p" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-gddc8		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-gddc8" is pending

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

... skipping 9 lines ...
Machine	i-0b8568a53b87b0a6d					machine "i-0b8568a53b87b0a6d" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-d9g96	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-d9g96" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-s5vth	system-cluster-critical pod "cert-manager-webhook-7bbf67968-s5vth" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-fddbg		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fddbg" is pending
Pod	kube-system/coredns-f45c4bf76-hc2p4			system-cluster-critical pod "coredns-f45c4bf76-hc2p4" is pending

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

... skipping 9 lines ...
Machine	i-0b8568a53b87b0a6d					machine "i-0b8568a53b87b0a6d" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-d9g96	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-d9g96" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-s5vth	system-cluster-critical pod "cert-manager-webhook-7bbf67968-s5vth" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-fddbg		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fddbg" is pending
Pod	kube-system/coredns-f45c4bf76-hc2p4			system-cluster-critical pod "coredns-f45c4bf76-hc2p4" is pending

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

... skipping 9 lines ...
Machine	i-0b8568a53b87b0a6d					machine "i-0b8568a53b87b0a6d" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-d9g96	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-d9g96" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-s5vth	system-cluster-critical pod "cert-manager-webhook-7bbf67968-s5vth" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-fddbg		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fddbg" is pending
Pod	kube-system/coredns-f45c4bf76-hc2p4			system-cluster-critical pod "coredns-f45c4bf76-hc2p4" is pending

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

... skipping 9 lines ...
Machine	i-0b8568a53b87b0a6d					machine "i-0b8568a53b87b0a6d" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-d9g96	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-d9g96" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-s5vth	system-cluster-critical pod "cert-manager-webhook-7bbf67968-s5vth" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-fddbg		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fddbg" is pending
Pod	kube-system/coredns-f45c4bf76-hc2p4			system-cluster-critical pod "coredns-f45c4bf76-hc2p4" is pending

Validation Failed
W0612 16:18:04.485981   11750 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 19 lines ...
Pod	kube-system/ebs-csi-node-5qz8s						system-node-critical pod "ebs-csi-node-5qz8s" is pending
Pod	kube-system/ebs-csi-node-86vlh						system-node-critical pod "ebs-csi-node-86vlh" is pending
Pod	kube-system/ebs-csi-node-jgrgm						system-node-critical pod "ebs-csi-node-jgrgm" is pending
Pod	kube-system/ebs-csi-node-xl28r						system-node-critical pod "ebs-csi-node-xl28r" is pending
Pod	kube-system/kube-proxy-ip-172-20-62-8.ap-northeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-62-8.ap-northeast-2.compute.internal" is pending

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

... skipping 21 lines ...
Pod	kube-system/coredns-f45c4bf76-hc2p4			system-cluster-critical pod "coredns-f45c4bf76-hc2p4" is pending
Pod	kube-system/ebs-csi-node-5qz8s				system-node-critical pod "ebs-csi-node-5qz8s" is pending
Pod	kube-system/ebs-csi-node-86vlh				system-node-critical pod "ebs-csi-node-86vlh" is pending
Pod	kube-system/ebs-csi-node-jgrgm				system-node-critical pod "ebs-csi-node-jgrgm" is pending
Pod	kube-system/ebs-csi-node-xl28r				system-node-critical pod "ebs-csi-node-xl28r" is pending

Validation Failed
W0612 16:18:29.717571   11750 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 20 lines ...
Pod	kube-system/coredns-f45c4bf76-hc2p4			system-cluster-critical pod "coredns-f45c4bf76-hc2p4" is pending
Pod	kube-system/ebs-csi-node-5qz8s				system-node-critical pod "ebs-csi-node-5qz8s" is pending
Pod	kube-system/ebs-csi-node-86vlh				system-node-critical pod "ebs-csi-node-86vlh" is pending
Pod	kube-system/ebs-csi-node-jgrgm				system-node-critical pod "ebs-csi-node-jgrgm" is pending
Pod	kube-system/ebs-csi-node-xl28r				system-node-critical pod "ebs-csi-node-xl28r" is pending

Validation Failed
W0612 16:18:42.342273   11750 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/cert-manager-cainjector-74d69756d5-d9g96	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-d9g96" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-s5vth	system-cluster-critical pod "cert-manager-webhook-7bbf67968-s5vth" is pending
Pod	kube-system/coredns-f45c4bf76-hc2p4			system-cluster-critical pod "coredns-f45c4bf76-hc2p4" is pending
Pod	kube-system/coredns-f45c4bf76-zvsj6			system-cluster-critical pod "coredns-f45c4bf76-zvsj6" is pending
Pod	kube-system/ebs-csi-node-5qz8s				system-node-critical pod "ebs-csi-node-5qz8s" is pending

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

... skipping 9 lines ...
KIND	NAME							MESSAGE
Pod	kube-system/calico-node-247h7				system-node-critical pod "calico-node-247h7" is not ready (calico-node)
Pod	kube-system/calico-node-fct79				system-node-critical pod "calico-node-fct79" is not ready (calico-node)
Pod	kube-system/cert-manager-webhook-7bbf67968-s5vth	system-cluster-critical pod "cert-manager-webhook-7bbf67968-s5vth" is pending
Pod	kube-system/coredns-f45c4bf76-zvsj6			system-cluster-critical pod "coredns-f45c4bf76-zvsj6" is pending

Validation Failed
W0612 16:19:07.670431   11750 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 292 lines ...

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

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

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.oSPuir0e7/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.oSPuir0e7/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.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 162 lines ...
Jun 12 16:22:41.992: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

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

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

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 695 lines ...
Jun 12 16:22:42.187: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 12 16:22:43.227: INFO: Successfully created a new PD: "aws://ap-northeast-2a/vol-01ecae00070cda12b".
Jun 12 16:22:43.227: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-m59t
STEP: Creating a pod to test exec-volume-test
Jun 12 16:22:43.388: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-m59t" in namespace "volume-7434" to be "Succeeded or Failed"
Jun 12 16:22:43.545: INFO: Pod "exec-volume-test-inlinevolume-m59t": Phase="Pending", Reason="", readiness=false. Elapsed: 156.85401ms
Jun 12 16:22:45.704: INFO: Pod "exec-volume-test-inlinevolume-m59t": Phase="Pending", Reason="", readiness=false. Elapsed: 2.316659715s
Jun 12 16:22:47.862: INFO: Pod "exec-volume-test-inlinevolume-m59t": Phase="Pending", Reason="", readiness=false. Elapsed: 4.474643706s
Jun 12 16:22:50.020: INFO: Pod "exec-volume-test-inlinevolume-m59t": Phase="Pending", Reason="", readiness=false. Elapsed: 6.63209901s
Jun 12 16:22:52.176: INFO: Pod "exec-volume-test-inlinevolume-m59t": Phase="Pending", Reason="", readiness=false. Elapsed: 8.788759382s
Jun 12 16:22:54.334: INFO: Pod "exec-volume-test-inlinevolume-m59t": Phase="Pending", Reason="", readiness=false. Elapsed: 10.946345832s
Jun 12 16:22:56.493: INFO: Pod "exec-volume-test-inlinevolume-m59t": Phase="Pending", Reason="", readiness=false. Elapsed: 13.105055961s
Jun 12 16:22:58.650: INFO: Pod "exec-volume-test-inlinevolume-m59t": Phase="Succeeded", Reason="", readiness=false. Elapsed: 15.261973275s
STEP: Saw pod success
Jun 12 16:22:58.650: INFO: Pod "exec-volume-test-inlinevolume-m59t" satisfied condition "Succeeded or Failed"
Jun 12 16:22:58.806: INFO: Trying to get logs from node ip-172-20-40-134.ap-northeast-2.compute.internal pod exec-volume-test-inlinevolume-m59t container exec-container-inlinevolume-m59t: <nil>
STEP: delete the pod
Jun 12 16:22:59.142: INFO: Waiting for pod exec-volume-test-inlinevolume-m59t to disappear
Jun 12 16:22:59.300: INFO: Pod exec-volume-test-inlinevolume-m59t no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-m59t
Jun 12 16:22:59.300: INFO: Deleting pod "exec-volume-test-inlinevolume-m59t" in namespace "volume-7434"
Jun 12 16:22:59.725: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-01ecae00070cda12b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01ecae00070cda12b is currently attached to i-06646d8971fcf1ba1
	status code: 400, request id: f2156bc2-fe49-4e3a-907a-ac22b8f2b2cd
Jun 12 16:23:05.502: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-01ecae00070cda12b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01ecae00070cda12b is currently attached to i-06646d8971fcf1ba1
	status code: 400, request id: 89a63cdb-2143-4fa7-bedc-cca3c06179fa
Jun 12 16:23:11.230: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-01ecae00070cda12b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01ecae00070cda12b is currently attached to i-06646d8971fcf1ba1
	status code: 400, request id: 481cdf2b-507b-441d-b440-20ac1b3ec0fe
Jun 12 16:23:17.036: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-01ecae00070cda12b".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 16:23:17.036: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-7434" for this suite.
... skipping 23 lines ...
Jun 12 16:22:44.350: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5872-e2e-scrsc58
STEP: creating a claim
Jun 12 16:22:44.523: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-g6kf
STEP: Creating a pod to test multi_subpath
Jun 12 16:22:45.027: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-g6kf" in namespace "provisioning-5872" to be "Succeeded or Failed"
Jun 12 16:22:45.191: INFO: Pod "pod-subpath-test-dynamicpv-g6kf": Phase="Pending", Reason="", readiness=false. Elapsed: 164.297087ms
Jun 12 16:22:47.360: INFO: Pod "pod-subpath-test-dynamicpv-g6kf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.333079146s
Jun 12 16:22:49.524: INFO: Pod "pod-subpath-test-dynamicpv-g6kf": Phase="Pending", Reason="", readiness=false. Elapsed: 4.496756003s
Jun 12 16:22:51.692: INFO: Pod "pod-subpath-test-dynamicpv-g6kf": Phase="Pending", Reason="", readiness=false. Elapsed: 6.664543977s
Jun 12 16:22:53.863: INFO: Pod "pod-subpath-test-dynamicpv-g6kf": Phase="Pending", Reason="", readiness=false. Elapsed: 8.836355416s
Jun 12 16:22:56.027: INFO: Pod "pod-subpath-test-dynamicpv-g6kf": Phase="Pending", Reason="", readiness=false. Elapsed: 11.000437397s
Jun 12 16:22:58.192: INFO: Pod "pod-subpath-test-dynamicpv-g6kf": Phase="Pending", Reason="", readiness=false. Elapsed: 13.164716708s
Jun 12 16:23:00.356: INFO: Pod "pod-subpath-test-dynamicpv-g6kf": Phase="Pending", Reason="", readiness=false. Elapsed: 15.329297037s
Jun 12 16:23:02.521: INFO: Pod "pod-subpath-test-dynamicpv-g6kf": Phase="Pending", Reason="", readiness=false. Elapsed: 17.493931489s
Jun 12 16:23:04.685: INFO: Pod "pod-subpath-test-dynamicpv-g6kf": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.658433127s
STEP: Saw pod success
Jun 12 16:23:04.686: INFO: Pod "pod-subpath-test-dynamicpv-g6kf" satisfied condition "Succeeded or Failed"
Jun 12 16:23:04.855: INFO: Trying to get logs from node ip-172-20-49-72.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-g6kf container test-container-subpath-dynamicpv-g6kf: <nil>
STEP: delete the pod
Jun 12 16:23:05.196: INFO: Waiting for pod pod-subpath-test-dynamicpv-g6kf to disappear
Jun 12 16:23:05.362: INFO: Pod pod-subpath-test-dynamicpv-g6kf no longer exists
STEP: Deleting pod
Jun 12 16:23:05.362: INFO: Deleting pod "pod-subpath-test-dynamicpv-g6kf" in namespace "provisioning-5872"
... skipping 102 lines ...
Jun 12 16:22:48.068: INFO: PersistentVolumeClaim pvc-nsgx2 found but phase is Pending instead of Bound.
Jun 12 16:22:50.230: INFO: PersistentVolumeClaim pvc-nsgx2 found and phase=Bound (4.492426837s)
Jun 12 16:22:50.230: INFO: Waiting up to 3m0s for PersistentVolume aws-kvj7p to have phase Bound
Jun 12 16:22:50.399: INFO: PersistentVolume aws-kvj7p found and phase=Bound (168.460976ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-w8q7
STEP: Creating a pod to test exec-volume-test
Jun 12 16:22:50.900: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-w8q7" in namespace "volume-7169" to be "Succeeded or Failed"
Jun 12 16:22:51.062: INFO: Pod "exec-volume-test-preprovisionedpv-w8q7": Phase="Pending", Reason="", readiness=false. Elapsed: 161.821084ms
Jun 12 16:22:53.225: INFO: Pod "exec-volume-test-preprovisionedpv-w8q7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.324849602s
Jun 12 16:22:55.388: INFO: Pod "exec-volume-test-preprovisionedpv-w8q7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.487770294s
Jun 12 16:22:57.550: INFO: Pod "exec-volume-test-preprovisionedpv-w8q7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.650299646s
Jun 12 16:22:59.713: INFO: Pod "exec-volume-test-preprovisionedpv-w8q7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.813425548s
Jun 12 16:23:01.877: INFO: Pod "exec-volume-test-preprovisionedpv-w8q7": Phase="Pending", Reason="", readiness=false. Elapsed: 10.976805105s
Jun 12 16:23:04.039: INFO: Pod "exec-volume-test-preprovisionedpv-w8q7": Phase="Pending", Reason="", readiness=false. Elapsed: 13.139546074s
Jun 12 16:23:06.202: INFO: Pod "exec-volume-test-preprovisionedpv-w8q7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 15.302034952s
STEP: Saw pod success
Jun 12 16:23:06.202: INFO: Pod "exec-volume-test-preprovisionedpv-w8q7" satisfied condition "Succeeded or Failed"
Jun 12 16:23:06.368: INFO: Trying to get logs from node ip-172-20-62-8.ap-northeast-2.compute.internal pod exec-volume-test-preprovisionedpv-w8q7 container exec-container-preprovisionedpv-w8q7: <nil>
STEP: delete the pod
Jun 12 16:23:06.769: INFO: Waiting for pod exec-volume-test-preprovisionedpv-w8q7 to disappear
Jun 12 16:23:06.931: INFO: Pod exec-volume-test-preprovisionedpv-w8q7 no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-w8q7
Jun 12 16:23:06.931: INFO: Deleting pod "exec-volume-test-preprovisionedpv-w8q7" in namespace "volume-7169"
STEP: Deleting pv and pvc
Jun 12 16:23:07.093: INFO: Deleting PersistentVolumeClaim "pvc-nsgx2"
Jun 12 16:23:07.282: INFO: Deleting PersistentVolume "aws-kvj7p"
Jun 12 16:23:07.713: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0152b3e8553e227ec", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0152b3e8553e227ec is currently attached to i-0990652e4330c67ef
	status code: 400, request id: 18c95fce-8f97-40dc-b619-a62793d0f260
Jun 12 16:23:13.489: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0152b3e8553e227ec", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0152b3e8553e227ec is currently attached to i-0990652e4330c67ef
	status code: 400, request id: dcce0af8-2829-4b86-9283-c49c4f6ca1da
Jun 12 16:23:19.257: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0152b3e8553e227ec", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0152b3e8553e227ec is currently attached to i-0990652e4330c67ef
	status code: 400, request id: ecf903c0-4649-45c5-ac83-44c2666900f2
Jun 12 16:23:25.070: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-0152b3e8553e227ec".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 16:23:25.070: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-7169" for this suite.
... skipping 100 lines ...
Jun 12 16:22:45.034: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5236p7frl
STEP: creating a claim
Jun 12 16:22:45.192: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-cn9j
STEP: Creating a pod to test subpath
Jun 12 16:22:45.672: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-cn9j" in namespace "provisioning-5236" to be "Succeeded or Failed"
Jun 12 16:22:45.829: INFO: Pod "pod-subpath-test-dynamicpv-cn9j": Phase="Pending", Reason="", readiness=false. Elapsed: 157.481137ms
Jun 12 16:22:47.989: INFO: Pod "pod-subpath-test-dynamicpv-cn9j": Phase="Pending", Reason="", readiness=false. Elapsed: 2.316832584s
Jun 12 16:22:50.147: INFO: Pod "pod-subpath-test-dynamicpv-cn9j": Phase="Pending", Reason="", readiness=false. Elapsed: 4.475303887s
Jun 12 16:22:52.309: INFO: Pod "pod-subpath-test-dynamicpv-cn9j": Phase="Pending", Reason="", readiness=false. Elapsed: 6.636822233s
Jun 12 16:22:54.470: INFO: Pod "pod-subpath-test-dynamicpv-cn9j": Phase="Pending", Reason="", readiness=false. Elapsed: 8.798263345s
Jun 12 16:22:56.630: INFO: Pod "pod-subpath-test-dynamicpv-cn9j": Phase="Pending", Reason="", readiness=false. Elapsed: 10.957777454s
... skipping 3 lines ...
Jun 12 16:23:05.271: INFO: Pod "pod-subpath-test-dynamicpv-cn9j": Phase="Pending", Reason="", readiness=false. Elapsed: 19.598972984s
Jun 12 16:23:07.429: INFO: Pod "pod-subpath-test-dynamicpv-cn9j": Phase="Pending", Reason="", readiness=false. Elapsed: 21.756834668s
Jun 12 16:23:09.598: INFO: Pod "pod-subpath-test-dynamicpv-cn9j": Phase="Pending", Reason="", readiness=false. Elapsed: 23.925999577s
Jun 12 16:23:11.756: INFO: Pod "pod-subpath-test-dynamicpv-cn9j": Phase="Pending", Reason="", readiness=false. Elapsed: 26.084481584s
Jun 12 16:23:13.915: INFO: Pod "pod-subpath-test-dynamicpv-cn9j": Phase="Succeeded", Reason="", readiness=false. Elapsed: 28.243130634s
STEP: Saw pod success
Jun 12 16:23:13.915: INFO: Pod "pod-subpath-test-dynamicpv-cn9j" satisfied condition "Succeeded or Failed"
Jun 12 16:23:14.073: INFO: Trying to get logs from node ip-172-20-40-134.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-cn9j container test-container-subpath-dynamicpv-cn9j: <nil>
STEP: delete the pod
Jun 12 16:23:14.400: INFO: Waiting for pod pod-subpath-test-dynamicpv-cn9j to disappear
Jun 12 16:23:14.558: INFO: Pod pod-subpath-test-dynamicpv-cn9j no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-cn9j
Jun 12 16:23:14.558: INFO: Deleting pod "pod-subpath-test-dynamicpv-cn9j" in namespace "provisioning-5236"
... skipping 234 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.oSPuir0e7/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.oSPuir0e7/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.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 25 lines ...
STEP: Creating a kubernetes client
Jun 12 16:22:40.549: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename provisioning
W0612 16:22:42.582592   25816 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Jun 12 16:22:42.582: 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 directory is outside the volume [Slow][LinuxOnly]
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun 12 16:22:42.904: INFO: Creating resource for dynamic PV
Jun 12 16:22:42.904: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3372-e2e-scg9gh7
STEP: creating a claim
Jun 12 16:22:43.067: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-nnn5
STEP: Checking for subpath error in container status
Jun 12 16:23:09.882: INFO: Deleting pod "pod-subpath-test-dynamicpv-nnn5" in namespace "provisioning-3372"
Jun 12 16:23:10.044: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-nnn5" to be fully deleted
STEP: Deleting pod
Jun 12 16:23:20.368: INFO: Deleting pod "pod-subpath-test-dynamicpv-nnn5" in namespace "provisioning-3372"
STEP: Deleting pvc
Jun 12 16:23:20.852: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comb27wz"
... skipping 10 lines ...

• [SLOW TEST:51.600 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath directory is outside the volume [Slow][LinuxOnly]
    /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 12 16:22:41.998: 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.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun 12 16:22:43.589: INFO: Creating resource for dynamic PV
Jun 12 16:22:43.589: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9934-e2e-scfgvlj
STEP: creating a claim
Jun 12 16:22:43.753: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-twbw
STEP: Checking for subpath error in container status
Jun 12 16:23:10.564: INFO: Deleting pod "pod-subpath-test-dynamicpv-twbw" in namespace "provisioning-9934"
Jun 12 16:23:10.727: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-twbw" to be fully deleted
STEP: Deleting pod
Jun 12 16:23:17.051: INFO: Deleting pod "pod-subpath-test-dynamicpv-twbw" in namespace "provisioning-9934"
STEP: Deleting pvc
Jun 12 16:23:17.542: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com6r7rr"
... skipping 11 lines ...

• [SLOW TEST:52.006 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath file is outside the volume [Slow][LinuxOnly]
    /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 10 lines ...
Jun 12 16:22:41.624: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-78249trk9
STEP: creating a claim
Jun 12 16:22:41.784: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-lwf7
STEP: Creating a pod to test subpath
Jun 12 16:22:42.266: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-lwf7" in namespace "provisioning-7824" to be "Succeeded or Failed"
Jun 12 16:22:42.424: INFO: Pod "pod-subpath-test-dynamicpv-lwf7": Phase="Pending", Reason="", readiness=false. Elapsed: 157.893415ms
Jun 12 16:22:44.584: INFO: Pod "pod-subpath-test-dynamicpv-lwf7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.317742083s
Jun 12 16:22:46.743: INFO: Pod "pod-subpath-test-dynamicpv-lwf7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.476463794s
Jun 12 16:22:48.902: INFO: Pod "pod-subpath-test-dynamicpv-lwf7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.635696523s
Jun 12 16:22:51.060: INFO: Pod "pod-subpath-test-dynamicpv-lwf7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.794074643s
Jun 12 16:22:53.219: INFO: Pod "pod-subpath-test-dynamicpv-lwf7": Phase="Pending", Reason="", readiness=false. Elapsed: 10.953332874s
... skipping 3 lines ...
Jun 12 16:23:01.860: INFO: Pod "pod-subpath-test-dynamicpv-lwf7": Phase="Pending", Reason="", readiness=false. Elapsed: 19.594378504s
Jun 12 16:23:04.020: INFO: Pod "pod-subpath-test-dynamicpv-lwf7": Phase="Pending", Reason="", readiness=false. Elapsed: 21.753871262s
Jun 12 16:23:06.179: INFO: Pod "pod-subpath-test-dynamicpv-lwf7": Phase="Pending", Reason="", readiness=false. Elapsed: 23.912777927s
Jun 12 16:23:08.337: INFO: Pod "pod-subpath-test-dynamicpv-lwf7": Phase="Pending", Reason="", readiness=false. Elapsed: 26.071228338s
Jun 12 16:23:10.496: INFO: Pod "pod-subpath-test-dynamicpv-lwf7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 28.229869085s
STEP: Saw pod success
Jun 12 16:23:10.496: INFO: Pod "pod-subpath-test-dynamicpv-lwf7" satisfied condition "Succeeded or Failed"
Jun 12 16:23:10.654: INFO: Trying to get logs from node ip-172-20-33-213.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-lwf7 container test-container-subpath-dynamicpv-lwf7: <nil>
STEP: delete the pod
Jun 12 16:23:12.068: INFO: Waiting for pod pod-subpath-test-dynamicpv-lwf7 to disappear
Jun 12 16:23:12.226: INFO: Pod pod-subpath-test-dynamicpv-lwf7 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-lwf7
Jun 12 16:23:12.226: INFO: Deleting pod "pod-subpath-test-dynamicpv-lwf7" in namespace "provisioning-7824"
... skipping 35 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.oSPuir0e7/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.oSPuir0e7/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.oSPuir0e7/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.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 177 lines ...
Jun 12 16:22:41.688: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-8545-e2e-sc8d98x
STEP: creating a claim
Jun 12 16:22:41.852: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-7hsm
STEP: Creating a pod to test exec-volume-test
Jun 12 16:22:42.345: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-7hsm" in namespace "volume-8545" to be "Succeeded or Failed"
Jun 12 16:22:42.507: INFO: Pod "exec-volume-test-dynamicpv-7hsm": Phase="Pending", Reason="", readiness=false. Elapsed: 162.239705ms
Jun 12 16:22:44.670: INFO: Pod "exec-volume-test-dynamicpv-7hsm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.325575607s
Jun 12 16:22:46.834: INFO: Pod "exec-volume-test-dynamicpv-7hsm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.489413059s
Jun 12 16:22:48.998: INFO: Pod "exec-volume-test-dynamicpv-7hsm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.653395256s
Jun 12 16:22:51.162: INFO: Pod "exec-volume-test-dynamicpv-7hsm": Phase="Pending", Reason="", readiness=false. Elapsed: 8.817103535s
Jun 12 16:22:53.325: INFO: Pod "exec-volume-test-dynamicpv-7hsm": Phase="Pending", Reason="", readiness=false. Elapsed: 10.979914004s
... skipping 4 lines ...
Jun 12 16:23:04.141: INFO: Pod "exec-volume-test-dynamicpv-7hsm": Phase="Pending", Reason="", readiness=false. Elapsed: 21.79613358s
Jun 12 16:23:06.304: INFO: Pod "exec-volume-test-dynamicpv-7hsm": Phase="Pending", Reason="", readiness=false. Elapsed: 23.958706838s
Jun 12 16:23:08.466: INFO: Pod "exec-volume-test-dynamicpv-7hsm": Phase="Pending", Reason="", readiness=false. Elapsed: 26.121328388s
Jun 12 16:23:10.629: INFO: Pod "exec-volume-test-dynamicpv-7hsm": Phase="Pending", Reason="", readiness=false. Elapsed: 28.284329914s
Jun 12 16:23:12.793: INFO: Pod "exec-volume-test-dynamicpv-7hsm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 30.448060975s
STEP: Saw pod success
Jun 12 16:23:12.793: INFO: Pod "exec-volume-test-dynamicpv-7hsm" satisfied condition "Succeeded or Failed"
Jun 12 16:23:12.956: INFO: Trying to get logs from node ip-172-20-40-134.ap-northeast-2.compute.internal pod exec-volume-test-dynamicpv-7hsm container exec-container-dynamicpv-7hsm: <nil>
STEP: delete the pod
Jun 12 16:23:13.287: INFO: Waiting for pod exec-volume-test-dynamicpv-7hsm to disappear
Jun 12 16:23:13.449: INFO: Pod exec-volume-test-dynamicpv-7hsm no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-7hsm
Jun 12 16:23:13.450: INFO: Deleting pod "exec-volume-test-dynamicpv-7hsm" in namespace "volume-8545"
... skipping 232 lines ...
Jun 12 16:22:41.774: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4059nfbs2
STEP: creating a claim
Jun 12 16:22:41.936: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-srdw
STEP: Creating a pod to test atomic-volume-subpath
Jun 12 16:22:42.431: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-srdw" in namespace "provisioning-4059" to be "Succeeded or Failed"
Jun 12 16:22:42.592: INFO: Pod "pod-subpath-test-dynamicpv-srdw": Phase="Pending", Reason="", readiness=false. Elapsed: 161.369093ms
Jun 12 16:22:44.754: INFO: Pod "pod-subpath-test-dynamicpv-srdw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.323187738s
Jun 12 16:22:46.917: INFO: Pod "pod-subpath-test-dynamicpv-srdw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.486547376s
Jun 12 16:22:49.080: INFO: Pod "pod-subpath-test-dynamicpv-srdw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.649199042s
Jun 12 16:22:51.243: INFO: Pod "pod-subpath-test-dynamicpv-srdw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.812322773s
Jun 12 16:22:53.406: INFO: Pod "pod-subpath-test-dynamicpv-srdw": Phase="Pending", Reason="", readiness=false. Elapsed: 10.975241544s
... skipping 11 lines ...
Jun 12 16:23:19.361: INFO: Pod "pod-subpath-test-dynamicpv-srdw": Phase="Running", Reason="", readiness=true. Elapsed: 36.930160132s
Jun 12 16:23:21.524: INFO: Pod "pod-subpath-test-dynamicpv-srdw": Phase="Running", Reason="", readiness=true. Elapsed: 39.092855231s
Jun 12 16:23:23.686: INFO: Pod "pod-subpath-test-dynamicpv-srdw": Phase="Running", Reason="", readiness=true. Elapsed: 41.255787743s
Jun 12 16:23:25.849: INFO: Pod "pod-subpath-test-dynamicpv-srdw": Phase="Running", Reason="", readiness=true. Elapsed: 43.418457478s
Jun 12 16:23:28.012: INFO: Pod "pod-subpath-test-dynamicpv-srdw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 45.581195224s
STEP: Saw pod success
Jun 12 16:23:28.012: INFO: Pod "pod-subpath-test-dynamicpv-srdw" satisfied condition "Succeeded or Failed"
Jun 12 16:23:28.175: INFO: Trying to get logs from node ip-172-20-49-72.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-srdw container test-container-subpath-dynamicpv-srdw: <nil>
STEP: delete the pod
Jun 12 16:23:28.512: INFO: Waiting for pod pod-subpath-test-dynamicpv-srdw to disappear
Jun 12 16:23:28.674: INFO: Pod pod-subpath-test-dynamicpv-srdw no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-srdw
Jun 12 16:23:28.674: INFO: Deleting pod "pod-subpath-test-dynamicpv-srdw" in namespace "provisioning-4059"
... skipping 37 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.oSPuir0e7/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.oSPuir0e7/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.oSPuir0e7/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.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 41 lines ...
STEP: Deleting pod hostexec-ip-172-20-40-134.ap-northeast-2.compute.internal-sjr2x in namespace volumemode-3780
Jun 12 16:23:43.591: INFO: Deleting pod "pod-86abff3f-9222-4b9a-9ab4-e031ab1ebbe1" in namespace "volumemode-3780"
Jun 12 16:23:43.756: INFO: Wait up to 5m0s for pod "pod-86abff3f-9222-4b9a-9ab4-e031ab1ebbe1" to be fully deleted
STEP: Deleting pv and pvc
Jun 12 16:23:58.076: INFO: Deleting PersistentVolumeClaim "pvc-7nrwn"
Jun 12 16:23:58.238: INFO: Deleting PersistentVolume "aws-tgwx4"
Jun 12 16:23:58.663: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-079368a38dfa771df", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-079368a38dfa771df is currently attached to i-06646d8971fcf1ba1
	status code: 400, request id: 2ff20484-8619-4486-b1fd-e646e092f3ea
Jun 12 16:24:04.457: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-079368a38dfa771df".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 16:24:04.457: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-3780" for this suite.
... skipping 14 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 12 16:23:34.006: 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.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 12 16:23:34.811: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 12 16:23:34.811: INFO: Creating resource for dynamic PV
Jun 12 16:23:34.811: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-8983hpz6b
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 12 16:23:41.949: INFO: Deleting pod "pod-275b0167-fe44-4219-8188-53f6334f25ff" in namespace "volumemode-8983"
Jun 12 16:23:42.110: INFO: Wait up to 5m0s for pod "pod-275b0167-fe44-4219-8188-53f6334f25ff" to be fully deleted
STEP: Deleting pvc
Jun 12 16:23:48.755: INFO: Deleting PersistentVolumeClaim "awszfd9m"
Jun 12 16:23:48.921: INFO: Waiting up to 5m0s for PersistentVolume pvc-fe340c81-7658-4a6b-9626-3a32d461e556 to get deleted
Jun 12 16:23:49.080: INFO: PersistentVolume pvc-fe340c81-7658-4a6b-9626-3a32d461e556 found and phase=Released (159.891443ms)
... skipping 11 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.oSPuir0e7/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.oSPuir0e7/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
    /tmp/kops.oSPuir0e7/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.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 520 lines ...
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 12 16:24:25.318: 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.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Jun 12 16:24:26.270: INFO: found topology map[topology.kubernetes.io/zone:ap-northeast-2a]
Jun 12 16:24:26.270: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 12 16:24:26.270: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.oSPuir0e7/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.oSPuir0e7/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (immediate binding)] topology
    /tmp/kops.oSPuir0e7/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.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 2 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 12 16:24:15.627: 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.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 12 16:24:16.465: INFO: Creating resource for dynamic PV
Jun 12 16:24:16.465: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-2002-e2e-sc7l8cj
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 12 16:24:21.646: INFO: Deleting pod "pod-e4c1f122-2da8-49ef-9846-dea438a6bce5" in namespace "volumemode-2002"
Jun 12 16:24:21.816: INFO: Wait up to 5m0s for pod "pod-e4c1f122-2da8-49ef-9846-dea438a6bce5" to be fully deleted
STEP: Deleting pvc
Jun 12 16:24:28.486: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com4f9xd"
Jun 12 16:24:28.665: INFO: Waiting up to 5m0s for PersistentVolume pvc-a16b4322-325c-4518-aa4b-5f011cbc68cf to get deleted
Jun 12 16:24:28.832: INFO: PersistentVolume pvc-a16b4322-325c-4518-aa4b-5f011cbc68cf found and phase=Released (166.948294ms)
... skipping 7 lines ...

• [SLOW TEST:18.883 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.oSPuir0e7/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.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [sig-storage] Zone Support [Feature:vsphere]
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 12 16:24:34.511: INFO: >>> kubeConfig: /root/.kube/config
... skipping 69 lines ...

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 461 lines ...
Jun 12 16:22:45.345: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-63149vvtp      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-6314    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-63149vvtp,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-6314    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-63149vvtp,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-6314    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-63149vvtp,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-63149vvtp    f1b79eaa-5f25-4159-bf69-3b39d761df79 2739 0 2021-06-12 16:22:45 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-12 16:22:45 +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-62fpg pvc- provisioning-6314  29d1bf32-7ae8-47cb-92ae-cd4e343ad4a7 2757 0 2021-06-12 16:22:46 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-12 16:22:46 +0000 UTC FieldsV1 {"f:metadata":{"f:generateName":{}},"f:spec":{"f:accessModes":{},"f:resources":{"f:requests":{".":{},"f:storage":{}}},"f:storageClassName":{},"f:volumeMode":{}}}}]},Spec:PersistentVolumeClaimSpec{AccessModes:[ReadWriteOnce],Resources:ResourceRequirements{Limits:ResourceList{},Requests:ResourceList{storage: {{1073741824 0} {<nil>} 1Gi BinarySI},},},VolumeName:,Selector:nil,StorageClassName:*provisioning-63149vvtp,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-51948ce9-34bc-4591-8a47-179e80d7842d in namespace provisioning-6314
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun 12 16:23:17.131: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-n6k9x" in namespace "provisioning-6314" to be "Succeeded or Failed"
Jun 12 16:23:17.311: INFO: Pod "pvc-volume-tester-writer-n6k9x": Phase="Pending", Reason="", readiness=false. Elapsed: 179.088578ms
Jun 12 16:23:19.472: INFO: Pod "pvc-volume-tester-writer-n6k9x": Phase="Pending", Reason="", readiness=false. Elapsed: 2.340201453s
Jun 12 16:23:21.632: INFO: Pod "pvc-volume-tester-writer-n6k9x": Phase="Pending", Reason="", readiness=false. Elapsed: 4.500217292s
Jun 12 16:23:23.792: INFO: Pod "pvc-volume-tester-writer-n6k9x": Phase="Pending", Reason="", readiness=false. Elapsed: 6.660157099s
Jun 12 16:23:25.952: INFO: Pod "pvc-volume-tester-writer-n6k9x": Phase="Pending", Reason="", readiness=false. Elapsed: 8.820642883s
Jun 12 16:23:28.112: INFO: Pod "pvc-volume-tester-writer-n6k9x": Phase="Pending", Reason="", readiness=false. Elapsed: 10.980911834s
... skipping 21 lines ...
Jun 12 16:24:15.667: INFO: Pod "pvc-volume-tester-writer-n6k9x": Phase="Pending", Reason="", readiness=false. Elapsed: 58.535209414s
Jun 12 16:24:17.827: INFO: Pod "pvc-volume-tester-writer-n6k9x": Phase="Pending", Reason="", readiness=false. Elapsed: 1m0.695507926s
Jun 12 16:24:19.988: INFO: Pod "pvc-volume-tester-writer-n6k9x": Phase="Pending", Reason="", readiness=false. Elapsed: 1m2.856393448s
Jun 12 16:24:22.151: INFO: Pod "pvc-volume-tester-writer-n6k9x": Phase="Pending", Reason="", readiness=false. Elapsed: 1m5.019164513s
Jun 12 16:24:24.311: INFO: Pod "pvc-volume-tester-writer-n6k9x": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m7.179584968s
STEP: Saw pod success
Jun 12 16:24:24.311: INFO: Pod "pvc-volume-tester-writer-n6k9x" satisfied condition "Succeeded or Failed"
Jun 12 16:24:24.635: INFO: Pod pvc-volume-tester-writer-n6k9x has the following logs: 
Jun 12 16:24:24.635: INFO: Deleting pod "pvc-volume-tester-writer-n6k9x" in namespace "provisioning-6314"
Jun 12 16:24:24.806: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-n6k9x" 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-40-134.ap-northeast-2.compute.internal"
Jun 12 16:24:25.456: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-xnzff" in namespace "provisioning-6314" to be "Succeeded or Failed"
Jun 12 16:24:25.616: INFO: Pod "pvc-volume-tester-reader-xnzff": Phase="Pending", Reason="", readiness=false. Elapsed: 160.091955ms
Jun 12 16:24:27.777: INFO: Pod "pvc-volume-tester-reader-xnzff": Phase="Pending", Reason="", readiness=false. Elapsed: 2.32086517s
Jun 12 16:24:29.937: INFO: Pod "pvc-volume-tester-reader-xnzff": Phase="Pending", Reason="", readiness=false. Elapsed: 4.481066956s
Jun 12 16:24:32.098: INFO: Pod "pvc-volume-tester-reader-xnzff": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.64171815s
STEP: Saw pod success
Jun 12 16:24:32.098: INFO: Pod "pvc-volume-tester-reader-xnzff" satisfied condition "Succeeded or Failed"
Jun 12 16:24:32.418: INFO: Pod pvc-volume-tester-reader-xnzff has the following logs: hello world

Jun 12 16:24:32.419: INFO: Deleting pod "pvc-volume-tester-reader-xnzff" in namespace "provisioning-6314"
Jun 12 16:24:32.586: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-xnzff" to be fully deleted
Jun 12 16:24:32.747: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-62fpg] to have phase Bound
Jun 12 16:24:32.906: INFO: PersistentVolumeClaim pvc-62fpg found and phase=Bound (159.489226ms)
... skipping 843 lines ...
Jun 12 16:24:58.984: INFO: Waiting for pod aws-client to disappear
Jun 12 16:24:59.142: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 12 16:24:59.142: INFO: Deleting PersistentVolumeClaim "pvc-ds6dw"
Jun 12 16:24:59.302: INFO: Deleting PersistentVolume "aws-2b8r7"
Jun 12 16:24:59.707: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0740d5b3d1034ea7c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0740d5b3d1034ea7c is currently attached to i-07881bb3a1e18c480
	status code: 400, request id: 6d777c67-cfe6-4eaa-a9ea-41a3f1649b44
Jun 12 16:25:05.492: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0740d5b3d1034ea7c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0740d5b3d1034ea7c is currently attached to i-07881bb3a1e18c480
	status code: 400, request id: 18a64d61-69d4-4baf-811e-ff9ef8e20a78
Jun 12 16:25:11.281: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0740d5b3d1034ea7c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0740d5b3d1034ea7c is currently attached to i-07881bb3a1e18c480
	status code: 400, request id: dca986b7-60c1-4546-a8f1-5740c35b86fe
Jun 12 16:25:17.058: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-0740d5b3d1034ea7c".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumes
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 16:25:17.058: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8956" for this suite.
... skipping 131 lines ...
Jun 12 16:24:46.305: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-2285fkj4h
STEP: creating a claim
Jun 12 16:24:46.465: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Jun 12 16:24:46.785: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 12 16:24:47.109: INFO: Error updating pvc awsnvwv7: PersistentVolumeClaim "awsnvwv7" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2285fkj4h",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun 12 16:25:17.780: INFO: Error updating pvc awsnvwv7: PersistentVolumeClaim "awsnvwv7" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 492 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.oSPuir0e7/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.oSPuir0e7/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.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 107 lines ...
Jun 12 16:24:56.773: INFO: Creating resource for dynamic PV
Jun 12 16:24:56.773: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-55172vlpr
STEP: creating a claim
STEP: Expanding non-expandable pvc
Jun 12 16:24:57.259: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 12 16:24:57.580: INFO: Error updating pvc awspbj6m: PersistentVolumeClaim "awspbj6m" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-55172vlpr",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 300 lines ...
Jun 12 16:24:09.131: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1071-e2e-sc6x4gd
STEP: creating a claim
Jun 12 16:24:09.293: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-ws7p
STEP: Creating a pod to test subpath
Jun 12 16:24:09.778: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-ws7p" in namespace "provisioning-1071" to be "Succeeded or Failed"
Jun 12 16:24:09.938: INFO: Pod "pod-subpath-test-dynamicpv-ws7p": Phase="Pending", Reason="", readiness=false. Elapsed: 160.128978ms
Jun 12 16:24:12.098: INFO: Pod "pod-subpath-test-dynamicpv-ws7p": Phase="Pending", Reason="", readiness=false. Elapsed: 2.320411693s
Jun 12 16:24:14.258: INFO: Pod "pod-subpath-test-dynamicpv-ws7p": Phase="Pending", Reason="", readiness=false. Elapsed: 4.480295868s
Jun 12 16:24:16.423: INFO: Pod "pod-subpath-test-dynamicpv-ws7p": Phase="Pending", Reason="", readiness=false. Elapsed: 6.645002795s
Jun 12 16:24:18.583: INFO: Pod "pod-subpath-test-dynamicpv-ws7p": Phase="Pending", Reason="", readiness=false. Elapsed: 8.805130746s
Jun 12 16:24:20.743: INFO: Pod "pod-subpath-test-dynamicpv-ws7p": Phase="Pending", Reason="", readiness=false. Elapsed: 10.965055232s
... skipping 2 lines ...
Jun 12 16:24:27.238: INFO: Pod "pod-subpath-test-dynamicpv-ws7p": Phase="Pending", Reason="", readiness=false. Elapsed: 17.460806775s
Jun 12 16:24:29.399: INFO: Pod "pod-subpath-test-dynamicpv-ws7p": Phase="Pending", Reason="", readiness=false. Elapsed: 19.621094645s
Jun 12 16:24:31.560: INFO: Pod "pod-subpath-test-dynamicpv-ws7p": Phase="Pending", Reason="", readiness=false. Elapsed: 21.782046981s
Jun 12 16:24:33.720: INFO: Pod "pod-subpath-test-dynamicpv-ws7p": Phase="Pending", Reason="", readiness=false. Elapsed: 23.942007964s
Jun 12 16:24:35.882: INFO: Pod "pod-subpath-test-dynamicpv-ws7p": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.104219503s
STEP: Saw pod success
Jun 12 16:24:35.882: INFO: Pod "pod-subpath-test-dynamicpv-ws7p" satisfied condition "Succeeded or Failed"
Jun 12 16:24:36.042: INFO: Trying to get logs from node ip-172-20-40-134.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-ws7p container test-container-subpath-dynamicpv-ws7p: <nil>
STEP: delete the pod
Jun 12 16:24:36.374: INFO: Waiting for pod pod-subpath-test-dynamicpv-ws7p to disappear
Jun 12 16:24:36.535: INFO: Pod pod-subpath-test-dynamicpv-ws7p no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-ws7p
Jun 12 16:24:36.535: INFO: Deleting pod "pod-subpath-test-dynamicpv-ws7p" in namespace "provisioning-1071"
STEP: Creating pod pod-subpath-test-dynamicpv-ws7p
STEP: Creating a pod to test subpath
Jun 12 16:24:36.856: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-ws7p" in namespace "provisioning-1071" to be "Succeeded or Failed"
Jun 12 16:24:37.015: INFO: Pod "pod-subpath-test-dynamicpv-ws7p": Phase="Pending", Reason="", readiness=false. Elapsed: 159.295315ms
Jun 12 16:24:39.176: INFO: Pod "pod-subpath-test-dynamicpv-ws7p": Phase="Pending", Reason="", readiness=false. Elapsed: 2.319947978s
Jun 12 16:24:41.337: INFO: Pod "pod-subpath-test-dynamicpv-ws7p": Phase="Pending", Reason="", readiness=false. Elapsed: 4.481125188s
Jun 12 16:24:43.499: INFO: Pod "pod-subpath-test-dynamicpv-ws7p": Phase="Pending", Reason="", readiness=false. Elapsed: 6.642941333s
Jun 12 16:24:45.661: INFO: Pod "pod-subpath-test-dynamicpv-ws7p": Phase="Pending", Reason="", readiness=false. Elapsed: 8.804543407s
Jun 12 16:24:47.821: INFO: Pod "pod-subpath-test-dynamicpv-ws7p": Phase="Pending", Reason="", readiness=false. Elapsed: 10.964691887s
... skipping 6 lines ...
Jun 12 16:25:02.946: INFO: Pod "pod-subpath-test-dynamicpv-ws7p": Phase="Pending", Reason="", readiness=false. Elapsed: 26.089895885s
Jun 12 16:25:05.106: INFO: Pod "pod-subpath-test-dynamicpv-ws7p": Phase="Pending", Reason="", readiness=false. Elapsed: 28.25001838s
Jun 12 16:25:07.270: INFO: Pod "pod-subpath-test-dynamicpv-ws7p": Phase="Pending", Reason="", readiness=false. Elapsed: 30.413950349s
Jun 12 16:25:09.431: INFO: Pod "pod-subpath-test-dynamicpv-ws7p": Phase="Pending", Reason="", readiness=false. Elapsed: 32.574907966s
Jun 12 16:25:11.591: INFO: Pod "pod-subpath-test-dynamicpv-ws7p": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.734697931s
STEP: Saw pod success
Jun 12 16:25:11.591: INFO: Pod "pod-subpath-test-dynamicpv-ws7p" satisfied condition "Succeeded or Failed"
Jun 12 16:25:11.750: INFO: Trying to get logs from node ip-172-20-49-72.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-ws7p container test-container-subpath-dynamicpv-ws7p: <nil>
STEP: delete the pod
Jun 12 16:25:12.086: INFO: Waiting for pod pod-subpath-test-dynamicpv-ws7p to disappear
Jun 12 16:25:12.246: INFO: Pod pod-subpath-test-dynamicpv-ws7p no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-ws7p
Jun 12 16:25:12.246: INFO: Deleting pod "pod-subpath-test-dynamicpv-ws7p" in namespace "provisioning-1071"
... skipping 40 lines ...
Jun 12 16:24:50.984: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6910g8jrj
STEP: creating a claim
Jun 12 16:24:51.146: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-zp9m
STEP: Creating a pod to test subpath
Jun 12 16:24:51.638: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-zp9m" in namespace "provisioning-6910" to be "Succeeded or Failed"
Jun 12 16:24:51.800: INFO: Pod "pod-subpath-test-dynamicpv-zp9m": Phase="Pending", Reason="", readiness=false. Elapsed: 162.639105ms
Jun 12 16:24:53.963: INFO: Pod "pod-subpath-test-dynamicpv-zp9m": Phase="Pending", Reason="", readiness=false. Elapsed: 2.325332274s
Jun 12 16:24:56.126: INFO: Pod "pod-subpath-test-dynamicpv-zp9m": Phase="Pending", Reason="", readiness=false. Elapsed: 4.488246216s
Jun 12 16:24:58.292: INFO: Pod "pod-subpath-test-dynamicpv-zp9m": Phase="Pending", Reason="", readiness=false. Elapsed: 6.65463778s
Jun 12 16:25:00.456: INFO: Pod "pod-subpath-test-dynamicpv-zp9m": Phase="Pending", Reason="", readiness=false. Elapsed: 8.817857641s
Jun 12 16:25:02.618: INFO: Pod "pod-subpath-test-dynamicpv-zp9m": Phase="Pending", Reason="", readiness=false. Elapsed: 10.980634098s
... skipping 9 lines ...
Jun 12 16:25:24.282: INFO: Pod "pod-subpath-test-dynamicpv-zp9m": Phase="Pending", Reason="", readiness=false. Elapsed: 32.644160453s
Jun 12 16:25:26.445: INFO: Pod "pod-subpath-test-dynamicpv-zp9m": Phase="Pending", Reason="", readiness=false. Elapsed: 34.806913301s
Jun 12 16:25:28.616: INFO: Pod "pod-subpath-test-dynamicpv-zp9m": Phase="Pending", Reason="", readiness=false. Elapsed: 36.97767481s
Jun 12 16:25:30.783: INFO: Pod "pod-subpath-test-dynamicpv-zp9m": Phase="Pending", Reason="", readiness=false. Elapsed: 39.145587973s
Jun 12 16:25:32.946: INFO: Pod "pod-subpath-test-dynamicpv-zp9m": Phase="Succeeded", Reason="", readiness=false. Elapsed: 41.307966264s
STEP: Saw pod success
Jun 12 16:25:32.946: INFO: Pod "pod-subpath-test-dynamicpv-zp9m" satisfied condition "Succeeded or Failed"
Jun 12 16:25:33.108: INFO: Trying to get logs from node ip-172-20-40-134.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-zp9m container test-container-volume-dynamicpv-zp9m: <nil>
STEP: delete the pod
Jun 12 16:25:33.463: INFO: Waiting for pod pod-subpath-test-dynamicpv-zp9m to disappear
Jun 12 16:25:33.626: INFO: Pod pod-subpath-test-dynamicpv-zp9m no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-zp9m
Jun 12 16:25:33.626: INFO: Deleting pod "pod-subpath-test-dynamicpv-zp9m" in namespace "provisioning-6910"
... skipping 63 lines ...
Jun 12 16:24:54.923: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1459jxdgs
STEP: creating a claim
Jun 12 16:24:55.081: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-c8qm
STEP: Creating a pod to test subpath
Jun 12 16:24:55.556: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-c8qm" in namespace "provisioning-1459" to be "Succeeded or Failed"
Jun 12 16:24:55.734: INFO: Pod "pod-subpath-test-dynamicpv-c8qm": Phase="Pending", Reason="", readiness=false. Elapsed: 178.253324ms
Jun 12 16:24:57.891: INFO: Pod "pod-subpath-test-dynamicpv-c8qm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.335802806s
Jun 12 16:25:00.051: INFO: Pod "pod-subpath-test-dynamicpv-c8qm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.495481135s
Jun 12 16:25:02.209: INFO: Pod "pod-subpath-test-dynamicpv-c8qm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.65377259s
Jun 12 16:25:04.367: INFO: Pod "pod-subpath-test-dynamicpv-c8qm": Phase="Pending", Reason="", readiness=false. Elapsed: 8.811800335s
Jun 12 16:25:06.525: INFO: Pod "pod-subpath-test-dynamicpv-c8qm": Phase="Pending", Reason="", readiness=false. Elapsed: 10.968890589s
... skipping 9 lines ...
Jun 12 16:25:28.106: INFO: Pod "pod-subpath-test-dynamicpv-c8qm": Phase="Pending", Reason="", readiness=false. Elapsed: 32.550558189s
Jun 12 16:25:30.263: INFO: Pod "pod-subpath-test-dynamicpv-c8qm": Phase="Pending", Reason="", readiness=false. Elapsed: 34.707801045s
Jun 12 16:25:32.423: INFO: Pod "pod-subpath-test-dynamicpv-c8qm": Phase="Pending", Reason="", readiness=false. Elapsed: 36.867010289s
Jun 12 16:25:34.580: INFO: Pod "pod-subpath-test-dynamicpv-c8qm": Phase="Pending", Reason="", readiness=false. Elapsed: 39.024727829s
Jun 12 16:25:36.738: INFO: Pod "pod-subpath-test-dynamicpv-c8qm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 41.182325261s
STEP: Saw pod success
Jun 12 16:25:36.738: INFO: Pod "pod-subpath-test-dynamicpv-c8qm" satisfied condition "Succeeded or Failed"
Jun 12 16:25:36.895: INFO: Trying to get logs from node ip-172-20-40-134.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-c8qm container test-container-volume-dynamicpv-c8qm: <nil>
STEP: delete the pod
Jun 12 16:25:37.224: INFO: Waiting for pod pod-subpath-test-dynamicpv-c8qm to disappear
Jun 12 16:25:37.380: INFO: Pod pod-subpath-test-dynamicpv-c8qm no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-c8qm
Jun 12 16:25:37.380: INFO: Deleting pod "pod-subpath-test-dynamicpv-c8qm" in namespace "provisioning-1459"
... skipping 72 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.oSPuir0e7/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.oSPuir0e7/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.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 2 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 12 16:25:21.454: 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.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun 12 16:25:22.259: INFO: Creating resource for dynamic PV
Jun 12 16:25:22.259: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2096-e2e-sc2wg5m
STEP: creating a claim
Jun 12 16:25:22.436: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-p4t6
STEP: Checking for subpath error in container status
Jun 12 16:25:37.248: INFO: Deleting pod "pod-subpath-test-dynamicpv-p4t6" in namespace "provisioning-2096"
Jun 12 16:25:37.413: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-p4t6" to be fully deleted
STEP: Deleting pod
Jun 12 16:25:47.734: INFO: Deleting pod "pod-subpath-test-dynamicpv-p4t6" in namespace "provisioning-2096"
STEP: Deleting pvc
Jun 12 16:25:48.227: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com2dnz9"
... skipping 10 lines ...

• [SLOW TEST:37.909 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.oSPuir0e7/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.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [sig-storage] Zone Support [Feature:vsphere]
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 12 16:25:59.365: INFO: >>> kubeConfig: /root/.kube/config
... skipping 118 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.oSPuir0e7/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.oSPuir0e7/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.oSPuir0e7/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.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 183 lines ...
Jun 12 16:25:20.670: INFO: Creating resource for dynamic PV
Jun 12 16:25:20.670: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-469-e2e-scn7zn8
STEP: creating a claim
Jun 12 16:25:20.830: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-469
Jun 12 16:25:21.317: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-469" in namespace "provisioning-469" to be "Succeeded or Failed"
Jun 12 16:25:21.476: INFO: Pod "volume-prep-provisioning-469": Phase="Pending", Reason="", readiness=false. Elapsed: 159.182648ms
Jun 12 16:25:23.636: INFO: Pod "volume-prep-provisioning-469": Phase="Pending", Reason="", readiness=false. Elapsed: 2.31939509s
Jun 12 16:25:25.797: INFO: Pod "volume-prep-provisioning-469": Phase="Pending", Reason="", readiness=false. Elapsed: 4.48048475s
Jun 12 16:25:27.958: INFO: Pod "volume-prep-provisioning-469": Phase="Pending", Reason="", readiness=false. Elapsed: 6.640908224s
Jun 12 16:25:30.119: INFO: Pod "volume-prep-provisioning-469": Phase="Pending", Reason="", readiness=false. Elapsed: 8.802462098s
Jun 12 16:25:32.279: INFO: Pod "volume-prep-provisioning-469": Phase="Pending", Reason="", readiness=false. Elapsed: 10.96261368s
Jun 12 16:25:34.447: INFO: Pod "volume-prep-provisioning-469": Phase="Succeeded", Reason="", readiness=false. Elapsed: 13.130560917s
STEP: Saw pod success
Jun 12 16:25:34.447: INFO: Pod "volume-prep-provisioning-469" satisfied condition "Succeeded or Failed"
Jun 12 16:25:34.447: INFO: Deleting pod "volume-prep-provisioning-469" in namespace "provisioning-469"
Jun 12 16:25:34.622: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-469" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-7s7d
STEP: Checking for subpath error in container status
Jun 12 16:25:55.261: INFO: Deleting pod "pod-subpath-test-dynamicpv-7s7d" in namespace "provisioning-469"
Jun 12 16:25:55.425: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-7s7d" to be fully deleted
STEP: Deleting pod
Jun 12 16:25:55.585: INFO: Deleting pod "pod-subpath-test-dynamicpv-7s7d" in namespace "provisioning-469"
STEP: Deleting pvc
Jun 12 16:25:56.062: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comgq7zn"
... skipping 205 lines ...

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

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

    /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 179 lines ...
Jun 12 16:25:29.955: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1567-e2e-scqzn9h
STEP: creating a claim
Jun 12 16:25:30.120: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-d6f8
STEP: Creating a pod to test subpath
Jun 12 16:25:30.612: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-d6f8" in namespace "provisioning-1567" to be "Succeeded or Failed"
Jun 12 16:25:30.773: INFO: Pod "pod-subpath-test-dynamicpv-d6f8": Phase="Pending", Reason="", readiness=false. Elapsed: 160.740284ms
Jun 12 16:25:32.935: INFO: Pod "pod-subpath-test-dynamicpv-d6f8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.322005525s
Jun 12 16:25:35.095: INFO: Pod "pod-subpath-test-dynamicpv-d6f8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.482220782s
Jun 12 16:25:37.256: INFO: Pod "pod-subpath-test-dynamicpv-d6f8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.643162005s
Jun 12 16:25:39.417: INFO: Pod "pod-subpath-test-dynamicpv-d6f8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.804308873s
Jun 12 16:25:41.578: INFO: Pod "pod-subpath-test-dynamicpv-d6f8": Phase="Pending", Reason="", readiness=false. Elapsed: 10.965142433s
... skipping 4 lines ...
Jun 12 16:25:52.384: INFO: Pod "pod-subpath-test-dynamicpv-d6f8": Phase="Pending", Reason="", readiness=false. Elapsed: 21.771332085s
Jun 12 16:25:54.548: INFO: Pod "pod-subpath-test-dynamicpv-d6f8": Phase="Pending", Reason="", readiness=false. Elapsed: 23.935287472s
Jun 12 16:25:56.708: INFO: Pod "pod-subpath-test-dynamicpv-d6f8": Phase="Pending", Reason="", readiness=false. Elapsed: 26.095476583s
Jun 12 16:25:58.869: INFO: Pod "pod-subpath-test-dynamicpv-d6f8": Phase="Pending", Reason="", readiness=false. Elapsed: 28.256418705s
Jun 12 16:26:01.029: INFO: Pod "pod-subpath-test-dynamicpv-d6f8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 30.416690748s
STEP: Saw pod success
Jun 12 16:26:01.029: INFO: Pod "pod-subpath-test-dynamicpv-d6f8" satisfied condition "Succeeded or Failed"
Jun 12 16:26:01.186: INFO: Trying to get logs from node ip-172-20-40-134.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-d6f8 container test-container-volume-dynamicpv-d6f8: <nil>
STEP: delete the pod
Jun 12 16:26:01.516: INFO: Waiting for pod pod-subpath-test-dynamicpv-d6f8 to disappear
Jun 12 16:26:01.674: INFO: Pod pod-subpath-test-dynamicpv-d6f8 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-d6f8
Jun 12 16:26:01.674: INFO: Deleting pod "pod-subpath-test-dynamicpv-d6f8" in namespace "provisioning-1567"
... skipping 561 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.oSPuir0e7/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.oSPuir0e7/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.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 12 lines ...
Jun 12 16:26:02.934: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-795vsppl
STEP: creating a claim
Jun 12 16:26:03.092: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-42hh
STEP: Creating a pod to test multi_subpath
Jun 12 16:26:03.575: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-42hh" in namespace "provisioning-795" to be "Succeeded or Failed"
Jun 12 16:26:03.733: INFO: Pod "pod-subpath-test-dynamicpv-42hh": Phase="Pending", Reason="", readiness=false. Elapsed: 157.918407ms
Jun 12 16:26:05.890: INFO: Pod "pod-subpath-test-dynamicpv-42hh": Phase="Pending", Reason="", readiness=false. Elapsed: 2.315729675s
Jun 12 16:26:08.048: INFO: Pod "pod-subpath-test-dynamicpv-42hh": Phase="Pending", Reason="", readiness=false. Elapsed: 4.473741823s
Jun 12 16:26:10.207: INFO: Pod "pod-subpath-test-dynamicpv-42hh": Phase="Pending", Reason="", readiness=false. Elapsed: 6.632384347s
Jun 12 16:26:12.363: INFO: Pod "pod-subpath-test-dynamicpv-42hh": Phase="Pending", Reason="", readiness=false. Elapsed: 8.788585668s
Jun 12 16:26:14.521: INFO: Pod "pod-subpath-test-dynamicpv-42hh": Phase="Pending", Reason="", readiness=false. Elapsed: 10.946081471s
Jun 12 16:26:16.677: INFO: Pod "pod-subpath-test-dynamicpv-42hh": Phase="Pending", Reason="", readiness=false. Elapsed: 13.101889374s
Jun 12 16:26:18.832: INFO: Pod "pod-subpath-test-dynamicpv-42hh": Phase="Pending", Reason="", readiness=false. Elapsed: 15.257705816s
Jun 12 16:26:20.988: INFO: Pod "pod-subpath-test-dynamicpv-42hh": Phase="Pending", Reason="", readiness=false. Elapsed: 17.412893107s
Jun 12 16:26:23.143: INFO: Pod "pod-subpath-test-dynamicpv-42hh": Phase="Pending", Reason="", readiness=false. Elapsed: 19.56786746s
Jun 12 16:26:25.298: INFO: Pod "pod-subpath-test-dynamicpv-42hh": Phase="Pending", Reason="", readiness=false. Elapsed: 21.7234611s
Jun 12 16:26:27.455: INFO: Pod "pod-subpath-test-dynamicpv-42hh": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.880189818s
STEP: Saw pod success
Jun 12 16:26:27.455: INFO: Pod "pod-subpath-test-dynamicpv-42hh" satisfied condition "Succeeded or Failed"
Jun 12 16:26:27.609: INFO: Trying to get logs from node ip-172-20-33-213.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-42hh container test-container-subpath-dynamicpv-42hh: <nil>
STEP: delete the pod
Jun 12 16:26:27.928: INFO: Waiting for pod pod-subpath-test-dynamicpv-42hh to disappear
Jun 12 16:26:28.083: INFO: Pod pod-subpath-test-dynamicpv-42hh no longer exists
STEP: Deleting pod
Jun 12 16:26:28.083: INFO: Deleting pod "pod-subpath-test-dynamicpv-42hh" in namespace "provisioning-795"
... skipping 137 lines ...
Jun 12 16:25:55.071: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-1688bvgd
STEP: creating a claim
Jun 12 16:25:55.228: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-29rx
STEP: Creating a pod to test exec-volume-test
Jun 12 16:25:55.704: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-29rx" in namespace "volume-168" to be "Succeeded or Failed"
Jun 12 16:25:55.862: INFO: Pod "exec-volume-test-dynamicpv-29rx": Phase="Pending", Reason="", readiness=false. Elapsed: 157.868508ms
Jun 12 16:25:58.040: INFO: Pod "exec-volume-test-dynamicpv-29rx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.336135711s
Jun 12 16:26:00.198: INFO: Pod "exec-volume-test-dynamicpv-29rx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.493855814s
Jun 12 16:26:02.355: INFO: Pod "exec-volume-test-dynamicpv-29rx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.650649791s
Jun 12 16:26:04.517: INFO: Pod "exec-volume-test-dynamicpv-29rx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.813142689s
Jun 12 16:26:06.676: INFO: Pod "exec-volume-test-dynamicpv-29rx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.972255931s
Jun 12 16:26:08.836: INFO: Pod "exec-volume-test-dynamicpv-29rx": Phase="Pending", Reason="", readiness=false. Elapsed: 13.132324625s
Jun 12 16:26:10.995: INFO: Pod "exec-volume-test-dynamicpv-29rx": Phase="Pending", Reason="", readiness=false. Elapsed: 15.291382459s
Jun 12 16:26:13.155: INFO: Pod "exec-volume-test-dynamicpv-29rx": Phase="Pending", Reason="", readiness=false. Elapsed: 17.451287881s
Jun 12 16:26:15.315: INFO: Pod "exec-volume-test-dynamicpv-29rx": Phase="Pending", Reason="", readiness=false. Elapsed: 19.61061606s
Jun 12 16:26:17.474: INFO: Pod "exec-volume-test-dynamicpv-29rx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.770189734s
STEP: Saw pod success
Jun 12 16:26:17.474: INFO: Pod "exec-volume-test-dynamicpv-29rx" satisfied condition "Succeeded or Failed"
Jun 12 16:26:17.633: INFO: Trying to get logs from node ip-172-20-40-134.ap-northeast-2.compute.internal pod exec-volume-test-dynamicpv-29rx container exec-container-dynamicpv-29rx: <nil>
STEP: delete the pod
Jun 12 16:26:18.006: INFO: Waiting for pod exec-volume-test-dynamicpv-29rx to disappear
Jun 12 16:26:18.164: INFO: Pod exec-volume-test-dynamicpv-29rx no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-29rx
Jun 12 16:26:18.164: INFO: Deleting pod "exec-volume-test-dynamicpv-29rx" in namespace "volume-168"
... skipping 277 lines ...
Jun 12 16:26:24.353: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 12 16:26:25.273: INFO: Successfully created a new PD: "aws://ap-northeast-2a/vol-0248363f12931eb98".
Jun 12 16:26:25.273: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-rzst
STEP: Creating a pod to test exec-volume-test
Jun 12 16:26:25.443: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-rzst" in namespace "volume-5035" to be "Succeeded or Failed"
Jun 12 16:26:25.608: INFO: Pod "exec-volume-test-inlinevolume-rzst": Phase="Pending", Reason="", readiness=false. Elapsed: 164.446019ms
Jun 12 16:26:27.770: INFO: Pod "exec-volume-test-inlinevolume-rzst": Phase="Pending", Reason="", readiness=false. Elapsed: 2.326592853s
Jun 12 16:26:29.933: INFO: Pod "exec-volume-test-inlinevolume-rzst": Phase="Pending", Reason="", readiness=false. Elapsed: 4.489860376s
Jun 12 16:26:32.096: INFO: Pod "exec-volume-test-inlinevolume-rzst": Phase="Pending", Reason="", readiness=false. Elapsed: 6.652850873s
Jun 12 16:26:34.258: INFO: Pod "exec-volume-test-inlinevolume-rzst": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.814784155s
STEP: Saw pod success
Jun 12 16:26:34.258: INFO: Pod "exec-volume-test-inlinevolume-rzst" satisfied condition "Succeeded or Failed"
Jun 12 16:26:34.420: INFO: Trying to get logs from node ip-172-20-33-213.ap-northeast-2.compute.internal pod exec-volume-test-inlinevolume-rzst container exec-container-inlinevolume-rzst: <nil>
STEP: delete the pod
Jun 12 16:26:34.756: INFO: Waiting for pod exec-volume-test-inlinevolume-rzst to disappear
Jun 12 16:26:34.918: INFO: Pod exec-volume-test-inlinevolume-rzst no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-rzst
Jun 12 16:26:34.918: INFO: Deleting pod "exec-volume-test-inlinevolume-rzst" in namespace "volume-5035"
Jun 12 16:26:35.352: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0248363f12931eb98", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0248363f12931eb98 is currently attached to i-07881bb3a1e18c480
	status code: 400, request id: a988c1d1-e93e-4bcf-8e55-491cb7a84459
Jun 12 16:26:41.117: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0248363f12931eb98", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0248363f12931eb98 is currently attached to i-07881bb3a1e18c480
	status code: 400, request id: 4dc18d29-e490-4b5c-a1b2-9c7089854a0a
Jun 12 16:26:46.899: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-0248363f12931eb98".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 16:26:46.899: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-5035" for this suite.
... skipping 75 lines ...
Jun 12 16:26:34.409: INFO: Pod aws-client still exists
Jun 12 16:26:36.243: INFO: Waiting for pod aws-client to disappear
Jun 12 16:26:36.406: INFO: Pod aws-client still exists
Jun 12 16:26:38.242: INFO: Waiting for pod aws-client to disappear
Jun 12 16:26:38.406: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun 12 16:26:38.657: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-026df461301eb7893", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-026df461301eb7893 is currently attached to i-06646d8971fcf1ba1
	status code: 400, request id: 38868232-deaf-482a-87e4-edee33edd272
Jun 12 16:26:44.427: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-026df461301eb7893", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-026df461301eb7893 is currently attached to i-06646d8971fcf1ba1
	status code: 400, request id: b2605c49-7962-4258-9852-39e07f2100a9
Jun 12 16:26:50.209: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-026df461301eb7893".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 16:26:50.210: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-2234" for this suite.
... skipping 48 lines ...
Jun 12 16:26:15.383: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4632-e2e-scm2lmh
STEP: creating a claim
Jun 12 16:26:15.543: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-jbft
STEP: Creating a pod to test subpath
Jun 12 16:26:16.024: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-jbft" in namespace "provisioning-4632" to be "Succeeded or Failed"
Jun 12 16:26:16.182: INFO: Pod "pod-subpath-test-dynamicpv-jbft": Phase="Pending", Reason="", readiness=false. Elapsed: 158.108036ms
Jun 12 16:26:18.340: INFO: Pod "pod-subpath-test-dynamicpv-jbft": Phase="Pending", Reason="", readiness=false. Elapsed: 2.316608451s
Jun 12 16:26:20.499: INFO: Pod "pod-subpath-test-dynamicpv-jbft": Phase="Pending", Reason="", readiness=false. Elapsed: 4.475397886s
Jun 12 16:26:22.658: INFO: Pod "pod-subpath-test-dynamicpv-jbft": Phase="Pending", Reason="", readiness=false. Elapsed: 6.63441539s
Jun 12 16:26:24.817: INFO: Pod "pod-subpath-test-dynamicpv-jbft": Phase="Pending", Reason="", readiness=false. Elapsed: 8.793116964s
Jun 12 16:26:26.976: INFO: Pod "pod-subpath-test-dynamicpv-jbft": Phase="Pending", Reason="", readiness=false. Elapsed: 10.951878794s
Jun 12 16:26:29.134: INFO: Pod "pod-subpath-test-dynamicpv-jbft": Phase="Pending", Reason="", readiness=false. Elapsed: 13.110433258s
Jun 12 16:26:31.293: INFO: Pod "pod-subpath-test-dynamicpv-jbft": Phase="Pending", Reason="", readiness=false. Elapsed: 15.269030809s
Jun 12 16:26:33.452: INFO: Pod "pod-subpath-test-dynamicpv-jbft": Phase="Pending", Reason="", readiness=false. Elapsed: 17.428101668s
Jun 12 16:26:35.610: INFO: Pod "pod-subpath-test-dynamicpv-jbft": Phase="Pending", Reason="", readiness=false. Elapsed: 19.58669308s
Jun 12 16:26:37.770: INFO: Pod "pod-subpath-test-dynamicpv-jbft": Phase="Pending", Reason="", readiness=false. Elapsed: 21.746602336s
Jun 12 16:26:39.931: INFO: Pod "pod-subpath-test-dynamicpv-jbft": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.906904957s
STEP: Saw pod success
Jun 12 16:26:39.931: INFO: Pod "pod-subpath-test-dynamicpv-jbft" satisfied condition "Succeeded or Failed"
Jun 12 16:26:40.090: INFO: Trying to get logs from node ip-172-20-33-213.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-jbft container test-container-subpath-dynamicpv-jbft: <nil>
STEP: delete the pod
Jun 12 16:26:40.427: INFO: Waiting for pod pod-subpath-test-dynamicpv-jbft to disappear
Jun 12 16:26:40.586: INFO: Pod pod-subpath-test-dynamicpv-jbft no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-jbft
Jun 12 16:26:40.586: INFO: Deleting pod "pod-subpath-test-dynamicpv-jbft" in namespace "provisioning-4632"
... skipping 36 lines ...
Jun 12 16:25:50.630: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6569294xf
STEP: creating a claim
Jun 12 16:25:50.790: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-8hfn
STEP: Creating a pod to test subpath
Jun 12 16:25:51.273: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-8hfn" in namespace "provisioning-6569" to be "Succeeded or Failed"
Jun 12 16:25:51.433: INFO: Pod "pod-subpath-test-dynamicpv-8hfn": Phase="Pending", Reason="", readiness=false. Elapsed: 160.257596ms
Jun 12 16:25:53.593: INFO: Pod "pod-subpath-test-dynamicpv-8hfn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.320446905s
Jun 12 16:25:55.753: INFO: Pod "pod-subpath-test-dynamicpv-8hfn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.480574344s
Jun 12 16:25:57.921: INFO: Pod "pod-subpath-test-dynamicpv-8hfn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.648074702s
Jun 12 16:26:00.082: INFO: Pod "pod-subpath-test-dynamicpv-8hfn": Phase="Pending", Reason="", readiness=false. Elapsed: 8.809187628s
Jun 12 16:26:02.244: INFO: Pod "pod-subpath-test-dynamicpv-8hfn": Phase="Pending", Reason="", readiness=false. Elapsed: 10.971438006s
Jun 12 16:26:04.413: INFO: Pod "pod-subpath-test-dynamicpv-8hfn": Phase="Pending", Reason="", readiness=false. Elapsed: 13.140189069s
Jun 12 16:26:06.573: INFO: Pod "pod-subpath-test-dynamicpv-8hfn": Phase="Pending", Reason="", readiness=false. Elapsed: 15.30019138s
Jun 12 16:26:08.733: INFO: Pod "pod-subpath-test-dynamicpv-8hfn": Phase="Pending", Reason="", readiness=false. Elapsed: 17.46012632s
Jun 12 16:26:10.894: INFO: Pod "pod-subpath-test-dynamicpv-8hfn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.620921525s
STEP: Saw pod success
Jun 12 16:26:10.894: INFO: Pod "pod-subpath-test-dynamicpv-8hfn" satisfied condition "Succeeded or Failed"
Jun 12 16:26:11.053: INFO: Trying to get logs from node ip-172-20-62-8.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-8hfn container test-container-subpath-dynamicpv-8hfn: <nil>
STEP: delete the pod
Jun 12 16:26:11.390: INFO: Waiting for pod pod-subpath-test-dynamicpv-8hfn to disappear
Jun 12 16:26:11.549: INFO: Pod pod-subpath-test-dynamicpv-8hfn no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-8hfn
Jun 12 16:26:11.549: INFO: Deleting pod "pod-subpath-test-dynamicpv-8hfn" in namespace "provisioning-6569"
STEP: Creating pod pod-subpath-test-dynamicpv-8hfn
STEP: Creating a pod to test subpath
Jun 12 16:26:11.869: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-8hfn" in namespace "provisioning-6569" to be "Succeeded or Failed"
Jun 12 16:26:12.028: INFO: Pod "pod-subpath-test-dynamicpv-8hfn": Phase="Pending", Reason="", readiness=false. Elapsed: 159.324939ms
Jun 12 16:26:14.188: INFO: Pod "pod-subpath-test-dynamicpv-8hfn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.319059462s
Jun 12 16:26:16.348: INFO: Pod "pod-subpath-test-dynamicpv-8hfn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.479202828s
Jun 12 16:26:18.524: INFO: Pod "pod-subpath-test-dynamicpv-8hfn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.655352539s
Jun 12 16:26:20.684: INFO: Pod "pod-subpath-test-dynamicpv-8hfn": Phase="Pending", Reason="", readiness=false. Elapsed: 8.815214407s
Jun 12 16:26:22.845: INFO: Pod "pod-subpath-test-dynamicpv-8hfn": Phase="Pending", Reason="", readiness=false. Elapsed: 10.976119048s
... skipping 6 lines ...
Jun 12 16:26:37.966: INFO: Pod "pod-subpath-test-dynamicpv-8hfn": Phase="Pending", Reason="", readiness=false. Elapsed: 26.097318576s
Jun 12 16:26:40.127: INFO: Pod "pod-subpath-test-dynamicpv-8hfn": Phase="Pending", Reason="", readiness=false. Elapsed: 28.25882774s
Jun 12 16:26:42.288: INFO: Pod "pod-subpath-test-dynamicpv-8hfn": Phase="Pending", Reason="", readiness=false. Elapsed: 30.419570804s
Jun 12 16:26:44.450: INFO: Pod "pod-subpath-test-dynamicpv-8hfn": Phase="Pending", Reason="", readiness=false. Elapsed: 32.581821439s
Jun 12 16:26:46.610: INFO: Pod "pod-subpath-test-dynamicpv-8hfn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.741562498s
STEP: Saw pod success
Jun 12 16:26:46.610: INFO: Pod "pod-subpath-test-dynamicpv-8hfn" satisfied condition "Succeeded or Failed"
Jun 12 16:26:46.770: INFO: Trying to get logs from node ip-172-20-49-72.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-8hfn container test-container-subpath-dynamicpv-8hfn: <nil>
STEP: delete the pod
Jun 12 16:26:47.099: INFO: Waiting for pod pod-subpath-test-dynamicpv-8hfn to disappear
Jun 12 16:26:47.264: INFO: Pod pod-subpath-test-dynamicpv-8hfn no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-8hfn
Jun 12 16:26:47.264: INFO: Deleting pod "pod-subpath-test-dynamicpv-8hfn" in namespace "provisioning-6569"
... skipping 31 lines ...

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

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

    /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 69 lines ...
Jun 12 16:26:43.812: INFO: Pod aws-client still exists
Jun 12 16:26:45.649: INFO: Waiting for pod aws-client to disappear
Jun 12 16:26:45.812: INFO: Pod aws-client still exists
Jun 12 16:26:47.649: INFO: Waiting for pod aws-client to disappear
Jun 12 16:26:47.811: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun 12 16:26:48.106: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0deef2d6adabfe94c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0deef2d6adabfe94c is currently attached to i-0b8568a53b87b0a6d
	status code: 400, request id: ef088a11-7269-4188-8c8e-85e365548205
Jun 12 16:26:53.898: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0deef2d6adabfe94c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0deef2d6adabfe94c is currently attached to i-0b8568a53b87b0a6d
	status code: 400, request id: 86e0ed2f-04dc-495b-a000-33a65dffcd16
Jun 12 16:26:59.666: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-0deef2d6adabfe94c".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 16:26:59.666: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-6745" for this suite.
... skipping 22 lines ...
Jun 12 16:24:02.096: INFO: Creating resource for dynamic PV
Jun 12 16:24:02.096: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-4447-e2e-sch7jmf
STEP: creating a claim
Jun 12 16:24:02.259: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 12 16:24:02.752: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-j94dg" in namespace "snapshotting-4447" to be "Succeeded or Failed"
Jun 12 16:24:02.914: INFO: Pod "pvc-snapshottable-tester-j94dg": Phase="Pending", Reason="", readiness=false. Elapsed: 161.687457ms
Jun 12 16:24:05.076: INFO: Pod "pvc-snapshottable-tester-j94dg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.324032959s
Jun 12 16:24:07.240: INFO: Pod "pvc-snapshottable-tester-j94dg": Phase="Pending", Reason="", readiness=false. Elapsed: 4.487994673s
Jun 12 16:24:09.403: INFO: Pod "pvc-snapshottable-tester-j94dg": Phase="Pending", Reason="", readiness=false. Elapsed: 6.651207196s
Jun 12 16:24:11.570: INFO: Pod "pvc-snapshottable-tester-j94dg": Phase="Pending", Reason="", readiness=false. Elapsed: 8.818152134s
Jun 12 16:24:13.733: INFO: Pod "pvc-snapshottable-tester-j94dg": Phase="Pending", Reason="", readiness=false. Elapsed: 10.98037137s
Jun 12 16:24:15.895: INFO: Pod "pvc-snapshottable-tester-j94dg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 13.142336675s
STEP: Saw pod success
Jun 12 16:24:15.895: INFO: Pod "pvc-snapshottable-tester-j94dg" satisfied condition "Succeeded or Failed"
Jun 12 16:24:16.221: INFO: Pod pvc-snapshottable-tester-j94dg has the following logs: 
Jun 12 16:24:16.221: INFO: Deleting pod "pvc-snapshottable-tester-j94dg" in namespace "snapshotting-4447"
Jun 12 16:24:16.391: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-j94dg" to be fully deleted
Jun 12 16:24:16.557: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comm47gz] to have phase Bound
Jun 12 16:24:16.722: INFO: PersistentVolumeClaim ebs.csi.aws.comm47gz found and phase=Bound (165.043142ms)
STEP: [init] checking the claim
... skipping 30 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.oSPuir0e7/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 12 16:25:01.790: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-7kqgc" in namespace "snapshotting-4447" to be "Succeeded or Failed"
Jun 12 16:25:01.951: INFO: Pod "pvc-snapshottable-data-tester-7kqgc": Phase="Pending", Reason="", readiness=false. Elapsed: 161.879041ms
Jun 12 16:25:04.117: INFO: Pod "pvc-snapshottable-data-tester-7kqgc": Phase="Pending", Reason="", readiness=false. Elapsed: 2.32715054s
Jun 12 16:25:06.280: INFO: Pod "pvc-snapshottable-data-tester-7kqgc": Phase="Pending", Reason="", readiness=false. Elapsed: 4.490246579s
Jun 12 16:25:08.445: INFO: Pod "pvc-snapshottable-data-tester-7kqgc": Phase="Pending", Reason="", readiness=false. Elapsed: 6.655311521s
Jun 12 16:25:10.608: INFO: Pod "pvc-snapshottable-data-tester-7kqgc": Phase="Pending", Reason="", readiness=false. Elapsed: 8.818268069s
Jun 12 16:25:12.771: INFO: Pod "pvc-snapshottable-data-tester-7kqgc": Phase="Pending", Reason="", readiness=false. Elapsed: 10.981538669s
... skipping 9 lines ...
Jun 12 16:25:34.416: INFO: Pod "pvc-snapshottable-data-tester-7kqgc": Phase="Pending", Reason="", readiness=false. Elapsed: 32.626479778s
Jun 12 16:25:36.580: INFO: Pod "pvc-snapshottable-data-tester-7kqgc": Phase="Pending", Reason="", readiness=false. Elapsed: 34.790029325s
Jun 12 16:25:38.743: INFO: Pod "pvc-snapshottable-data-tester-7kqgc": Phase="Pending", Reason="", readiness=false. Elapsed: 36.95313241s
Jun 12 16:25:40.905: INFO: Pod "pvc-snapshottable-data-tester-7kqgc": Phase="Pending", Reason="", readiness=false. Elapsed: 39.115845956s
Jun 12 16:25:43.067: INFO: Pod "pvc-snapshottable-data-tester-7kqgc": Phase="Succeeded", Reason="", readiness=false. Elapsed: 41.277748864s
STEP: Saw pod success
Jun 12 16:25:43.067: INFO: Pod "pvc-snapshottable-data-tester-7kqgc" satisfied condition "Succeeded or Failed"
Jun 12 16:25:43.392: INFO: Pod pvc-snapshottable-data-tester-7kqgc has the following logs: 
Jun 12 16:25:43.392: INFO: Deleting pod "pvc-snapshottable-data-tester-7kqgc" in namespace "snapshotting-4447"
Jun 12 16:25:43.561: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-7kqgc" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 12 16:26:06.375: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-4447 exec restored-pvc-tester-qdmz5 --namespace=snapshotting-4447 -- cat /mnt/test/data'
... skipping 28 lines ...
STEP: Found 27 events.
Jun 12 16:26:58.426: INFO: At 2021-06-12 16:24:02 +0000 UTC - event for ebs.csi.aws.comm47gz: {persistentvolume-controller } WaitForFirstConsumer: waiting for first consumer to be created before binding
Jun 12 16:26:58.426: INFO: At 2021-06-12 16:24:02 +0000 UTC - event for ebs.csi.aws.comm47gz: {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 12 16:26:58.426: INFO: At 2021-06-12 16:24:02 +0000 UTC - event for ebs.csi.aws.comm47gz: {ebs.csi.aws.com_ebs-csi-controller-7ffff4ddf5-gddc8_2e2771ec-99ad-4a4c-845a-db5bcc2a1a49 } Provisioning: External provisioner is provisioning volume for claim "snapshotting-4447/ebs.csi.aws.comm47gz"
Jun 12 16:26:58.426: INFO: At 2021-06-12 16:24:06 +0000 UTC - event for ebs.csi.aws.comm47gz: {ebs.csi.aws.com_ebs-csi-controller-7ffff4ddf5-gddc8_2e2771ec-99ad-4a4c-845a-db5bcc2a1a49 } ProvisioningSucceeded: Successfully provisioned volume pvc-3a03df98-8669-4611-b4b4-3a0ec397c939
Jun 12 16:26:58.426: INFO: At 2021-06-12 16:24:06 +0000 UTC - event for pvc-snapshottable-tester-j94dg: {default-scheduler } Scheduled: Successfully assigned snapshotting-4447/pvc-snapshottable-tester-j94dg to ip-172-20-40-134.ap-northeast-2.compute.internal
Jun 12 16:26:58.426: INFO: At 2021-06-12 16:24:07 +0000 UTC - event for pvc-snapshottable-tester-j94dg: {kubelet ip-172-20-40-134.ap-northeast-2.compute.internal} FailedMount: MountVolume.SetUp failed for volume "kube-api-access-4bggh" : failed to sync configmap cache: timed out waiting for the condition
Jun 12 16:26:58.426: INFO: At 2021-06-12 16:24:11 +0000 UTC - event for pvc-snapshottable-tester-j94dg: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-3a03df98-8669-4611-b4b4-3a0ec397c939" 
Jun 12 16:26:58.426: INFO: At 2021-06-12 16:24:15 +0000 UTC - event for pvc-snapshottable-tester-j94dg: {kubelet ip-172-20-40-134.ap-northeast-2.compute.internal} Started: Started container volume-tester
Jun 12 16:26:58.426: INFO: At 2021-06-12 16:24:15 +0000 UTC - event for pvc-snapshottable-tester-j94dg: {kubelet ip-172-20-40-134.ap-northeast-2.compute.internal} Created: Created container volume-tester
Jun 12 16:26:58.426: INFO: At 2021-06-12 16:24:15 +0000 UTC - event for pvc-snapshottable-tester-j94dg: {kubelet ip-172-20-40-134.ap-northeast-2.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" already present on machine
Jun 12 16:26:58.426: INFO: At 2021-06-12 16:24:17 +0000 UTC - event for snapshot-4cgrj: {snapshot-controller } CreatingSnapshot: Waiting for a snapshot snapshotting-4447/snapshot-4cgrj to be created by the CSI driver.
Jun 12 16:26:58.426: INFO: At 2021-06-12 16:25:01 +0000 UTC - event for pvc-snapshottable-data-tester-7kqgc: {default-scheduler } Scheduled: Successfully assigned snapshotting-4447/pvc-snapshottable-data-tester-7kqgc to ip-172-20-40-134.ap-northeast-2.compute.internal
Jun 12 16:26:58.426: INFO: At 2021-06-12 16:25:21 +0000 UTC - event for pvc-snapshottable-data-tester-7kqgc: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-3a03df98-8669-4611-b4b4-3a0ec397c939" : rpc error: code = DeadlineExceeded desc = context deadline exceeded
Jun 12 16:26:58.426: INFO: At 2021-06-12 16:25:24 +0000 UTC - event for pvc-snapshottable-data-tester-7kqgc: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-3a03df98-8669-4611-b4b4-3a0ec397c939" 
Jun 12 16:26:58.426: INFO: At 2021-06-12 16:25:37 +0000 UTC - event for pvc-snapshottable-data-tester-7kqgc: {kubelet ip-172-20-40-134.ap-northeast-2.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" already present on machine
Jun 12 16:26:58.426: INFO: At 2021-06-12 16:25:37 +0000 UTC - event for pvc-snapshottable-data-tester-7kqgc: {kubelet ip-172-20-40-134.ap-northeast-2.compute.internal} Created: Created container volume-tester
Jun 12 16:26:58.426: INFO: At 2021-06-12 16:25:37 +0000 UTC - event for pvc-snapshottable-data-tester-7kqgc: {kubelet ip-172-20-40-134.ap-northeast-2.compute.internal} Started: Started container volume-tester
Jun 12 16:26:58.426: INFO: At 2021-06-12 16:25:43 +0000 UTC - event for pvc-qfbc4: {ebs.csi.aws.com_ebs-csi-controller-7ffff4ddf5-gddc8_2e2771ec-99ad-4a4c-845a-db5bcc2a1a49 } Provisioning: External provisioner is provisioning volume for claim "snapshotting-4447/pvc-qfbc4"
Jun 12 16:26:58.426: INFO: At 2021-06-12 16:25:43 +0000 UTC - event for pvc-qfbc4: {persistentvolume-controller } ExternalProvisioning: waiting for a volume to be created, either by external provisioner "ebs.csi.aws.com" or manually created by system administrator
... skipping 216 lines ...
    /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:108
      
      /tmp/kops.oSPuir0e7/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.oSPuir0e7/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-4447 exec restored-pvc-tester-qdmz5 --namespace=snapshotting-4447 -- 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-4447 exec restored-pvc-tester-qdmz5 --namespace=snapshotting-4447 -- 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.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:602
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow]
... skipping 262 lines ...
Jun 12 16:26:48.633: INFO: Waiting for pod aws-client to disappear
Jun 12 16:26:48.789: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 12 16:26:48.790: INFO: Deleting PersistentVolumeClaim "pvc-n2vml"
Jun 12 16:26:48.947: INFO: Deleting PersistentVolume "aws-tlng4"
Jun 12 16:26:49.878: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0ed3c660693418277", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ed3c660693418277 is currently attached to i-0b8568a53b87b0a6d
	status code: 400, request id: 8e7cf3cb-bea7-4eb1-ab00-3c78cce653bb
Jun 12 16:26:55.672: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0ed3c660693418277", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ed3c660693418277 is currently attached to i-0b8568a53b87b0a6d
	status code: 400, request id: 00ea142c-2794-4802-8873-f7331f9fcfbd
Jun 12 16:27:01.443: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0ed3c660693418277", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ed3c660693418277 is currently attached to i-0b8568a53b87b0a6d
	status code: 400, request id: 8761f874-c168-4f77-ab07-b77a37d8314f
Jun 12 16:27:07.232: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-0ed3c660693418277".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 16:27:07.232: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-948" for this suite.
... skipping 288 lines ...
Jun 12 16:26:46.048: INFO: Creating resource for dynamic PV
Jun 12 16:26:46.048: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-681bs22h
STEP: creating a claim
Jun 12 16:26:46.208: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-681
Jun 12 16:26:46.690: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-681" in namespace "provisioning-681" to be "Succeeded or Failed"
Jun 12 16:26:46.849: INFO: Pod "volume-prep-provisioning-681": Phase="Pending", Reason="", readiness=false. Elapsed: 158.459222ms
Jun 12 16:26:49.009: INFO: Pod "volume-prep-provisioning-681": Phase="Pending", Reason="", readiness=false. Elapsed: 2.319086921s
Jun 12 16:26:51.170: INFO: Pod "volume-prep-provisioning-681": Phase="Pending", Reason="", readiness=false. Elapsed: 4.480077971s
Jun 12 16:26:53.330: INFO: Pod "volume-prep-provisioning-681": Phase="Pending", Reason="", readiness=false. Elapsed: 6.640096925s
Jun 12 16:26:55.490: INFO: Pod "volume-prep-provisioning-681": Phase="Pending", Reason="", readiness=false. Elapsed: 8.799923575s
Jun 12 16:26:57.650: INFO: Pod "volume-prep-provisioning-681": Phase="Pending", Reason="", readiness=false. Elapsed: 10.960067118s
Jun 12 16:26:59.810: INFO: Pod "volume-prep-provisioning-681": Phase="Pending", Reason="", readiness=false. Elapsed: 13.120123579s
Jun 12 16:27:01.970: INFO: Pod "volume-prep-provisioning-681": Phase="Pending", Reason="", readiness=false. Elapsed: 15.2799852s
Jun 12 16:27:04.130: INFO: Pod "volume-prep-provisioning-681": Phase="Pending", Reason="", readiness=false. Elapsed: 17.439899702s
Jun 12 16:27:06.289: INFO: Pod "volume-prep-provisioning-681": Phase="Pending", Reason="", readiness=false. Elapsed: 19.598859354s
Jun 12 16:27:08.448: INFO: Pod "volume-prep-provisioning-681": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.758001608s
STEP: Saw pod success
Jun 12 16:27:08.448: INFO: Pod "volume-prep-provisioning-681" satisfied condition "Succeeded or Failed"
Jun 12 16:27:08.448: INFO: Deleting pod "volume-prep-provisioning-681" in namespace "provisioning-681"
Jun 12 16:27:08.618: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-681" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-zr98
STEP: Checking for subpath error in container status
Jun 12 16:27:11.254: INFO: Deleting pod "pod-subpath-test-dynamicpv-zr98" in namespace "provisioning-681"
Jun 12 16:27:11.420: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-zr98" to be fully deleted
STEP: Deleting pod
Jun 12 16:27:11.579: INFO: Deleting pod "pod-subpath-test-dynamicpv-zr98" in namespace "provisioning-681"
STEP: Deleting pvc
Jun 12 16:27:12.056: INFO: Deleting PersistentVolumeClaim "awsmvf4v"
... skipping 254 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.oSPuir0e7/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.oSPuir0e7/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.oSPuir0e7/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.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 264 lines ...
STEP: Deleting pod hostexec-ip-172-20-33-213.ap-northeast-2.compute.internal-dnws5 in namespace volumemode-710
Jun 12 16:27:13.478: INFO: Deleting pod "pod-d6839abd-2135-4972-b787-1e97a275cf5b" in namespace "volumemode-710"
Jun 12 16:27:13.646: INFO: Wait up to 5m0s for pod "pod-d6839abd-2135-4972-b787-1e97a275cf5b" to be fully deleted
STEP: Deleting pv and pvc
Jun 12 16:27:27.975: INFO: Deleting PersistentVolumeClaim "pvc-kc964"
Jun 12 16:27:28.140: INFO: Deleting PersistentVolume "aws-9jl5s"
Jun 12 16:27:28.594: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0f9b0cb3222085096", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f9b0cb3222085096 is currently attached to i-07881bb3a1e18c480
	status code: 400, request id: 73687458-31e8-44ec-a38c-2a3bd258077f
Jun 12 16:27:34.392: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-0f9b0cb3222085096".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 16:27:34.392: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-710" for this suite.
... skipping 517 lines ...
Jun 12 16:27:08.354: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1019-e2e-sc97pqq
STEP: creating a claim
Jun 12 16:27:08.512: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-62jw
STEP: Creating a pod to test subpath
Jun 12 16:27:08.988: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-62jw" in namespace "provisioning-1019" to be "Succeeded or Failed"
Jun 12 16:27:09.144: INFO: Pod "pod-subpath-test-dynamicpv-62jw": Phase="Pending", Reason="", readiness=false. Elapsed: 156.05015ms
Jun 12 16:27:11.302: INFO: Pod "pod-subpath-test-dynamicpv-62jw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.314606893s
Jun 12 16:27:13.459: INFO: Pod "pod-subpath-test-dynamicpv-62jw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.471613502s
Jun 12 16:27:15.616: INFO: Pod "pod-subpath-test-dynamicpv-62jw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.628133518s
Jun 12 16:27:17.772: INFO: Pod "pod-subpath-test-dynamicpv-62jw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.784714956s
Jun 12 16:27:19.930: INFO: Pod "pod-subpath-test-dynamicpv-62jw": Phase="Pending", Reason="", readiness=false. Elapsed: 10.94263979s
Jun 12 16:27:22.087: INFO: Pod "pod-subpath-test-dynamicpv-62jw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 13.099474164s
STEP: Saw pod success
Jun 12 16:27:22.087: INFO: Pod "pod-subpath-test-dynamicpv-62jw" satisfied condition "Succeeded or Failed"
Jun 12 16:27:22.244: INFO: Trying to get logs from node ip-172-20-62-8.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-62jw container test-container-subpath-dynamicpv-62jw: <nil>
STEP: delete the pod
Jun 12 16:27:22.570: INFO: Waiting for pod pod-subpath-test-dynamicpv-62jw to disappear
Jun 12 16:27:22.727: INFO: Pod pod-subpath-test-dynamicpv-62jw no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-62jw
Jun 12 16:27:22.727: INFO: Deleting pod "pod-subpath-test-dynamicpv-62jw" in namespace "provisioning-1019"
... skipping 60 lines ...
Jun 12 16:26:47.886: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2045-e2e-scc74jj
STEP: creating a claim
Jun 12 16:26:48.049: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-j82q
STEP: Creating a pod to test subpath
Jun 12 16:26:48.549: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-j82q" in namespace "provisioning-2045" to be "Succeeded or Failed"
Jun 12 16:26:48.710: INFO: Pod "pod-subpath-test-dynamicpv-j82q": Phase="Pending", Reason="", readiness=false. Elapsed: 161.08113ms
Jun 12 16:26:50.874: INFO: Pod "pod-subpath-test-dynamicpv-j82q": Phase="Pending", Reason="", readiness=false. Elapsed: 2.324705363s
Jun 12 16:26:53.036: INFO: Pod "pod-subpath-test-dynamicpv-j82q": Phase="Pending", Reason="", readiness=false. Elapsed: 4.486597479s
Jun 12 16:26:55.199: INFO: Pod "pod-subpath-test-dynamicpv-j82q": Phase="Pending", Reason="", readiness=false. Elapsed: 6.649383662s
Jun 12 16:26:57.360: INFO: Pod "pod-subpath-test-dynamicpv-j82q": Phase="Pending", Reason="", readiness=false. Elapsed: 8.811189406s
Jun 12 16:26:59.522: INFO: Pod "pod-subpath-test-dynamicpv-j82q": Phase="Pending", Reason="", readiness=false. Elapsed: 10.972882354s
Jun 12 16:27:01.684: INFO: Pod "pod-subpath-test-dynamicpv-j82q": Phase="Pending", Reason="", readiness=false. Elapsed: 13.13500923s
Jun 12 16:27:03.847: INFO: Pod "pod-subpath-test-dynamicpv-j82q": Phase="Succeeded", Reason="", readiness=false. Elapsed: 15.298307425s
STEP: Saw pod success
Jun 12 16:27:03.847: INFO: Pod "pod-subpath-test-dynamicpv-j82q" satisfied condition "Succeeded or Failed"
Jun 12 16:27:04.009: INFO: Trying to get logs from node ip-172-20-33-213.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-j82q container test-container-subpath-dynamicpv-j82q: <nil>
STEP: delete the pod
Jun 12 16:27:04.345: INFO: Waiting for pod pod-subpath-test-dynamicpv-j82q to disappear
Jun 12 16:27:04.507: INFO: Pod pod-subpath-test-dynamicpv-j82q no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-j82q
Jun 12 16:27:04.507: INFO: Deleting pod "pod-subpath-test-dynamicpv-j82q" in namespace "provisioning-2045"
... skipping 39 lines ...
Jun 12 16:27:00.810: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3980-e2e-scfbrg8
STEP: creating a claim
Jun 12 16:27:00.973: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-ppcj
STEP: Creating a pod to test subpath
Jun 12 16:27:01.464: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-ppcj" in namespace "provisioning-3980" to be "Succeeded or Failed"
Jun 12 16:27:01.626: INFO: Pod "pod-subpath-test-dynamicpv-ppcj": Phase="Pending", Reason="", readiness=false. Elapsed: 162.159898ms
Jun 12 16:27:03.790: INFO: Pod "pod-subpath-test-dynamicpv-ppcj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.325201601s
Jun 12 16:27:05.953: INFO: Pod "pod-subpath-test-dynamicpv-ppcj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.489095088s
Jun 12 16:27:08.117: INFO: Pod "pod-subpath-test-dynamicpv-ppcj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.652341254s
Jun 12 16:27:10.284: INFO: Pod "pod-subpath-test-dynamicpv-ppcj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.820014581s
Jun 12 16:27:12.451: INFO: Pod "pod-subpath-test-dynamicpv-ppcj": Phase="Pending", Reason="", readiness=false. Elapsed: 10.986563667s
Jun 12 16:27:14.615: INFO: Pod "pod-subpath-test-dynamicpv-ppcj": Phase="Pending", Reason="", readiness=false. Elapsed: 13.150945956s
Jun 12 16:27:16.779: INFO: Pod "pod-subpath-test-dynamicpv-ppcj": Phase="Pending", Reason="", readiness=false. Elapsed: 15.314930132s
Jun 12 16:27:18.945: INFO: Pod "pod-subpath-test-dynamicpv-ppcj": Phase="Pending", Reason="", readiness=false. Elapsed: 17.480717666s
Jun 12 16:27:21.108: INFO: Pod "pod-subpath-test-dynamicpv-ppcj": Phase="Pending", Reason="", readiness=false. Elapsed: 19.643993418s
Jun 12 16:27:23.271: INFO: Pod "pod-subpath-test-dynamicpv-ppcj": Phase="Pending", Reason="", readiness=false. Elapsed: 21.806551699s
Jun 12 16:27:25.434: INFO: Pod "pod-subpath-test-dynamicpv-ppcj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.969314248s
STEP: Saw pod success
Jun 12 16:27:25.434: INFO: Pod "pod-subpath-test-dynamicpv-ppcj" satisfied condition "Succeeded or Failed"
Jun 12 16:27:25.596: INFO: Trying to get logs from node ip-172-20-62-8.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-ppcj container test-container-volume-dynamicpv-ppcj: <nil>
STEP: delete the pod
Jun 12 16:27:25.932: INFO: Waiting for pod pod-subpath-test-dynamicpv-ppcj to disappear
Jun 12 16:27:26.093: INFO: Pod pod-subpath-test-dynamicpv-ppcj no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-ppcj
Jun 12 16:27:26.094: INFO: Deleting pod "pod-subpath-test-dynamicpv-ppcj" in namespace "provisioning-3980"
... skipping 117 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 12 16:26:57.499: 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.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun 12 16:26:58.310: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 12 16:26:58.310: INFO: Creating resource for dynamic PV
Jun 12 16:26:58.310: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8246np6rb
STEP: creating a claim
Jun 12 16:26:58.470: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-zm4v
STEP: Checking for subpath error in container status
Jun 12 16:27:41.271: INFO: Deleting pod "pod-subpath-test-dynamicpv-zm4v" in namespace "provisioning-8246"
Jun 12 16:27:41.431: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-zm4v" to be fully deleted
STEP: Deleting pod
Jun 12 16:27:55.750: INFO: Deleting pod "pod-subpath-test-dynamicpv-zm4v" in namespace "provisioning-8246"
STEP: Deleting pvc
Jun 12 16:27:56.224: INFO: Deleting PersistentVolumeClaim "awscfbsf"
... skipping 10 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.oSPuir0e7/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.oSPuir0e7/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.oSPuir0e7/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.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow]
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 12 16:27:57.026: INFO: Driver supports dynamic provisioning, skipping PreprovisionedPV pattern
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow]
... skipping 250 lines ...
Jun 12 16:24:36.544: INFO: Creating resource for dynamic PV
Jun 12 16:24:36.544: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-6776-e2e-sczncfm
STEP: creating a claim
Jun 12 16:24:36.711: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 12 16:24:37.215: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-ltr6f" in namespace "snapshotting-6776" to be "Succeeded or Failed"
Jun 12 16:24:37.382: INFO: Pod "pvc-snapshottable-tester-ltr6f": Phase="Pending", Reason="", readiness=false. Elapsed: 167.062243ms
Jun 12 16:24:39.554: INFO: Pod "pvc-snapshottable-tester-ltr6f": Phase="Pending", Reason="", readiness=false. Elapsed: 2.338786791s
Jun 12 16:24:41.726: INFO: Pod "pvc-snapshottable-tester-ltr6f": Phase="Pending", Reason="", readiness=false. Elapsed: 4.510300594s
Jun 12 16:24:43.900: INFO: Pod "pvc-snapshottable-tester-ltr6f": Phase="Pending", Reason="", readiness=false. Elapsed: 6.684965331s
Jun 12 16:24:46.069: INFO: Pod "pvc-snapshottable-tester-ltr6f": Phase="Pending", Reason="", readiness=false. Elapsed: 8.853365499s
Jun 12 16:24:48.238: INFO: Pod "pvc-snapshottable-tester-ltr6f": Phase="Pending", Reason="", readiness=false. Elapsed: 11.022258938s
... skipping 7 lines ...
Jun 12 16:25:05.586: INFO: Pod "pvc-snapshottable-tester-ltr6f": Phase="Pending", Reason="", readiness=false. Elapsed: 28.370653154s
Jun 12 16:25:07.761: INFO: Pod "pvc-snapshottable-tester-ltr6f": Phase="Pending", Reason="", readiness=false. Elapsed: 30.545647335s
Jun 12 16:25:09.929: INFO: Pod "pvc-snapshottable-tester-ltr6f": Phase="Pending", Reason="", readiness=false. Elapsed: 32.713670285s
Jun 12 16:25:12.097: INFO: Pod "pvc-snapshottable-tester-ltr6f": Phase="Pending", Reason="", readiness=false. Elapsed: 34.88140623s
Jun 12 16:25:14.265: INFO: Pod "pvc-snapshottable-tester-ltr6f": Phase="Succeeded", Reason="", readiness=false. Elapsed: 37.049944371s
STEP: Saw pod success
Jun 12 16:25:14.265: INFO: Pod "pvc-snapshottable-tester-ltr6f" satisfied condition "Succeeded or Failed"
Jun 12 16:25:14.608: INFO: Pod pvc-snapshottable-tester-ltr6f has the following logs: 
Jun 12 16:25:14.608: INFO: Deleting pod "pvc-snapshottable-tester-ltr6f" in namespace "snapshotting-6776"
Jun 12 16:25:14.782: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-ltr6f" to be fully deleted
Jun 12 16:25:14.949: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.combqgwm] to have phase Bound
Jun 12 16:25:15.116: INFO: PersistentVolumeClaim ebs.csi.aws.combqgwm found and phase=Bound (167.008363ms)
STEP: [init] checking the claim
... skipping 39 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.oSPuir0e7/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 12 16:26:19.904: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-kkckl" in namespace "snapshotting-6776" to be "Succeeded or Failed"
Jun 12 16:26:20.073: INFO: Pod "pvc-snapshottable-data-tester-kkckl": Phase="Pending", Reason="", readiness=false. Elapsed: 168.781918ms
Jun 12 16:26:22.240: INFO: Pod "pvc-snapshottable-data-tester-kkckl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.336228849s
Jun 12 16:26:24.408: INFO: Pod "pvc-snapshottable-data-tester-kkckl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.504429906s
Jun 12 16:26:26.576: INFO: Pod "pvc-snapshottable-data-tester-kkckl": Phase="Pending", Reason="", readiness=false. Elapsed: 6.67236931s
Jun 12 16:26:28.745: INFO: Pod "pvc-snapshottable-data-tester-kkckl": Phase="Pending", Reason="", readiness=false. Elapsed: 8.840998281s
Jun 12 16:26:30.915: INFO: Pod "pvc-snapshottable-data-tester-kkckl": Phase="Pending", Reason="", readiness=false. Elapsed: 11.011578666s
Jun 12 16:26:33.084: INFO: Pod "pvc-snapshottable-data-tester-kkckl": Phase="Pending", Reason="", readiness=false. Elapsed: 13.179847218s
Jun 12 16:26:35.251: INFO: Pod "pvc-snapshottable-data-tester-kkckl": Phase="Pending", Reason="", readiness=false. Elapsed: 15.347064497s
Jun 12 16:26:37.420: INFO: Pod "pvc-snapshottable-data-tester-kkckl": Phase="Pending", Reason="", readiness=false. Elapsed: 17.516192635s
Jun 12 16:26:39.589: INFO: Pod "pvc-snapshottable-data-tester-kkckl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.685453498s
STEP: Saw pod success
Jun 12 16:26:39.589: INFO: Pod "pvc-snapshottable-data-tester-kkckl" satisfied condition "Succeeded or Failed"
Jun 12 16:26:39.930: INFO: Pod pvc-snapshottable-data-tester-kkckl has the following logs: 
Jun 12 16:26:39.930: INFO: Deleting pod "pvc-snapshottable-data-tester-kkckl" in namespace "snapshotting-6776"
Jun 12 16:26:40.104: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-kkckl" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 12 16:27:02.951: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-6776 exec restored-pvc-tester-9dmfj --namespace=snapshotting-6776 -- cat /mnt/test/data'
... skipping 258 lines ...
    /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:108
      
      /tmp/kops.oSPuir0e7/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.oSPuir0e7/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-6776 exec restored-pvc-tester-9dmfj --namespace=snapshotting-6776 -- 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-6776 exec restored-pvc-tester-9dmfj --namespace=snapshotting-6776 -- 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.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:602
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] volumes
... skipping 30 lines ...
Jun 12 16:27:35.550: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7878fjwdq
STEP: creating a claim
Jun 12 16:27:35.714: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-t88d
STEP: Creating a pod to test subpath
Jun 12 16:27:36.213: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-t88d" in namespace "provisioning-7878" to be "Succeeded or Failed"
Jun 12 16:27:36.377: INFO: Pod "pod-subpath-test-dynamicpv-t88d": Phase="Pending", Reason="", readiness=false. Elapsed: 163.520719ms
Jun 12 16:27:38.542: INFO: Pod "pod-subpath-test-dynamicpv-t88d": Phase="Pending", Reason="", readiness=false. Elapsed: 2.328111493s
Jun 12 16:27:40.706: INFO: Pod "pod-subpath-test-dynamicpv-t88d": Phase="Pending", Reason="", readiness=false. Elapsed: 4.492177598s
Jun 12 16:27:42.871: INFO: Pod "pod-subpath-test-dynamicpv-t88d": Phase="Pending", Reason="", readiness=false. Elapsed: 6.65752892s
Jun 12 16:27:45.036: INFO: Pod "pod-subpath-test-dynamicpv-t88d": Phase="Pending", Reason="", readiness=false. Elapsed: 8.822566448s
Jun 12 16:27:47.200: INFO: Pod "pod-subpath-test-dynamicpv-t88d": Phase="Pending", Reason="", readiness=false. Elapsed: 10.986450414s
Jun 12 16:27:49.365: INFO: Pod "pod-subpath-test-dynamicpv-t88d": Phase="Pending", Reason="", readiness=false. Elapsed: 13.151278619s
Jun 12 16:27:51.531: INFO: Pod "pod-subpath-test-dynamicpv-t88d": Phase="Pending", Reason="", readiness=false. Elapsed: 15.317497486s
Jun 12 16:27:53.696: INFO: Pod "pod-subpath-test-dynamicpv-t88d": Phase="Succeeded", Reason="", readiness=false. Elapsed: 17.482705391s
STEP: Saw pod success
Jun 12 16:27:53.696: INFO: Pod "pod-subpath-test-dynamicpv-t88d" satisfied condition "Succeeded or Failed"
Jun 12 16:27:53.860: INFO: Trying to get logs from node ip-172-20-62-8.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-t88d container test-container-subpath-dynamicpv-t88d: <nil>
STEP: delete the pod
Jun 12 16:27:54.194: INFO: Waiting for pod pod-subpath-test-dynamicpv-t88d to disappear
Jun 12 16:27:54.361: INFO: Pod pod-subpath-test-dynamicpv-t88d no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-t88d
Jun 12 16:27:54.361: INFO: Deleting pod "pod-subpath-test-dynamicpv-t88d" in namespace "provisioning-7878"
... skipping 28 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 12 16:27:40.280: 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.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 12 16:27:41.077: INFO: Creating resource for dynamic PV
Jun 12 16:27:41.077: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-5613-e2e-scjgljt
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 12 16:27:48.198: INFO: Deleting pod "pod-85cb2a4f-a3d7-4b6f-af12-eabcbe4ee0af" in namespace "volumemode-5613"
Jun 12 16:27:48.366: INFO: Wait up to 5m0s for pod "pod-85cb2a4f-a3d7-4b6f-af12-eabcbe4ee0af" to be fully deleted
STEP: Deleting pvc
Jun 12 16:27:59.012: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comg86d6"
Jun 12 16:27:59.171: INFO: Waiting up to 5m0s for PersistentVolume pvc-2c1d0b0e-bbd1-45bc-a0d5-ab4116dcb827 to get deleted
Jun 12 16:27:59.329: INFO: PersistentVolume pvc-2c1d0b0e-bbd1-45bc-a0d5-ab4116dcb827 found and phase=Released (158.579146ms)
... skipping 9 lines ...

• [SLOW TEST:35.012 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.oSPuir0e7/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.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow]
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 12 16:28:15.293: INFO: Driver supports dynamic provisioning, skipping PreprovisionedPV pattern
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow]
... skipping 25 lines ...

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

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

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

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

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

    /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 27 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 12 16:27:38.382: 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.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun 12 16:27:39.195: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 12 16:27:39.195: INFO: Creating resource for dynamic PV
Jun 12 16:27:39.195: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7229q7v7v
STEP: creating a claim
Jun 12 16:27:39.357: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-vm4l
STEP: Checking for subpath error in container status
Jun 12 16:27:58.168: INFO: Deleting pod "pod-subpath-test-dynamicpv-vm4l" in namespace "provisioning-7229"
Jun 12 16:27:58.380: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-vm4l" to be fully deleted
STEP: Deleting pod
Jun 12 16:28:08.705: INFO: Deleting pod "pod-subpath-test-dynamicpv-vm4l" in namespace "provisioning-7229"
STEP: Deleting pvc
Jun 12 16:28:09.199: INFO: Deleting PersistentVolumeClaim "aws7xcx4"
... skipping 12 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.oSPuir0e7/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.oSPuir0e7/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.oSPuir0e7/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.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volume-stress
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 12 16:28:20.344: INFO: Driver ebs.csi.aws.com doesn't specify stress test options -- skipping
[AfterEach] [Testpattern: Dynamic PV (block volmode)] volume-stress
... skipping 139 lines ...
Jun 12 16:26:47.385: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9884-e2e-scwrqpg
STEP: creating a claim
Jun 12 16:26:47.545: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-9724
STEP: Creating a pod to test atomic-volume-subpath
Jun 12 16:26:48.025: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-9724" in namespace "provisioning-9884" to be "Succeeded or Failed"
Jun 12 16:26:48.191: INFO: Pod "pod-subpath-test-dynamicpv-9724": Phase="Pending", Reason="", readiness=false. Elapsed: 165.837457ms
Jun 12 16:26:50.369: INFO: Pod "pod-subpath-test-dynamicpv-9724": Phase="Pending", Reason="", readiness=false. Elapsed: 2.344248559s
Jun 12 16:26:52.529: INFO: Pod "pod-subpath-test-dynamicpv-9724": Phase="Pending", Reason="", readiness=false. Elapsed: 4.504513964s
Jun 12 16:26:54.689: INFO: Pod "pod-subpath-test-dynamicpv-9724": Phase="Pending", Reason="", readiness=false. Elapsed: 6.664067575s
Jun 12 16:26:56.848: INFO: Pod "pod-subpath-test-dynamicpv-9724": Phase="Pending", Reason="", readiness=false. Elapsed: 8.823438529s
Jun 12 16:26:59.007: INFO: Pod "pod-subpath-test-dynamicpv-9724": Phase="Pending", Reason="", readiness=false. Elapsed: 10.982640493s
... skipping 17 lines ...
Jun 12 16:27:37.912: INFO: Pod "pod-subpath-test-dynamicpv-9724": Phase="Running", Reason="", readiness=true. Elapsed: 49.887402771s
Jun 12 16:27:40.075: INFO: Pod "pod-subpath-test-dynamicpv-9724": Phase="Running", Reason="", readiness=true. Elapsed: 52.050465729s
Jun 12 16:27:42.237: INFO: Pod "pod-subpath-test-dynamicpv-9724": Phase="Running", Reason="", readiness=true. Elapsed: 54.212347765s
Jun 12 16:27:44.397: INFO: Pod "pod-subpath-test-dynamicpv-9724": Phase="Running", Reason="", readiness=true. Elapsed: 56.37235244s
Jun 12 16:27:46.556: INFO: Pod "pod-subpath-test-dynamicpv-9724": Phase="Succeeded", Reason="", readiness=false. Elapsed: 58.531617743s
STEP: Saw pod success
Jun 12 16:27:46.556: INFO: Pod "pod-subpath-test-dynamicpv-9724" satisfied condition "Succeeded or Failed"
Jun 12 16:27:46.716: INFO: Trying to get logs from node ip-172-20-49-72.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-9724 container test-container-subpath-dynamicpv-9724: <nil>
STEP: delete the pod
Jun 12 16:27:47.044: INFO: Waiting for pod pod-subpath-test-dynamicpv-9724 to disappear
Jun 12 16:27:47.202: INFO: Pod pod-subpath-test-dynamicpv-9724 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-9724
Jun 12 16:27:47.202: INFO: Deleting pod "pod-subpath-test-dynamicpv-9724" in namespace "provisioning-9884"
... skipping 99 lines ...
Jun 12 16:28:27.494: INFO: Waiting for pod aws-client to disappear
Jun 12 16:28:27.649: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 12 16:28:27.649: INFO: Deleting PersistentVolumeClaim "pvc-97bbk"
Jun 12 16:28:27.806: INFO: Deleting PersistentVolume "aws-v7zcc"
Jun 12 16:28:28.715: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-09ce9e66380d53468", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-09ce9e66380d53468 is currently attached to i-07881bb3a1e18c480
	status code: 400, request id: fcb642ca-3001-4cb5-828e-799bcc4042ff
Jun 12 16:28:34.514: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-09ce9e66380d53468".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 16:28:34.514: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-4232" for this suite.
... skipping 135 lines ...

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

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

    /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:92
------------------------------
... skipping 11 lines ...
Jun 12 16:27:58.944: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-9325-e2e-sct2x77
STEP: creating a claim
Jun 12 16:27:59.106: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-fhzp
STEP: Creating a pod to test exec-volume-test
Jun 12 16:27:59.583: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-fhzp" in namespace "volume-9325" to be "Succeeded or Failed"
Jun 12 16:27:59.741: INFO: Pod "exec-volume-test-dynamicpv-fhzp": Phase="Pending", Reason="", readiness=false. Elapsed: 157.960358ms
Jun 12 16:28:01.901: INFO: Pod "exec-volume-test-dynamicpv-fhzp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.317248909s
Jun 12 16:28:04.060: INFO: Pod "exec-volume-test-dynamicpv-fhzp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.476814345s
Jun 12 16:28:06.219: INFO: Pod "exec-volume-test-dynamicpv-fhzp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.635638982s
Jun 12 16:28:08.413: INFO: Pod "exec-volume-test-dynamicpv-fhzp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.829668282s
Jun 12 16:28:10.573: INFO: Pod "exec-volume-test-dynamicpv-fhzp": Phase="Pending", Reason="", readiness=false. Elapsed: 10.989219874s
... skipping 2 lines ...
Jun 12 16:28:17.054: INFO: Pod "exec-volume-test-dynamicpv-fhzp": Phase="Pending", Reason="", readiness=false. Elapsed: 17.470873749s
Jun 12 16:28:19.213: INFO: Pod "exec-volume-test-dynamicpv-fhzp": Phase="Pending", Reason="", readiness=false. Elapsed: 19.629278333s
Jun 12 16:28:21.373: INFO: Pod "exec-volume-test-dynamicpv-fhzp": Phase="Pending", Reason="", readiness=false. Elapsed: 21.78927551s
Jun 12 16:28:23.531: INFO: Pod "exec-volume-test-dynamicpv-fhzp": Phase="Pending", Reason="", readiness=false. Elapsed: 23.94771665s
Jun 12 16:28:25.689: INFO: Pod "exec-volume-test-dynamicpv-fhzp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.105721561s
STEP: Saw pod success
Jun 12 16:28:25.689: INFO: Pod "exec-volume-test-dynamicpv-fhzp" satisfied condition "Succeeded or Failed"
Jun 12 16:28:25.847: INFO: Trying to get logs from node ip-172-20-49-72.ap-northeast-2.compute.internal pod exec-volume-test-dynamicpv-fhzp container exec-container-dynamicpv-fhzp: <nil>
STEP: delete the pod
Jun 12 16:28:26.179: INFO: Waiting for pod exec-volume-test-dynamicpv-fhzp to disappear
Jun 12 16:28:26.337: INFO: Pod exec-volume-test-dynamicpv-fhzp no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-fhzp
Jun 12 16:28:26.337: INFO: Deleting pod "exec-volume-test-dynamicpv-fhzp" in namespace "volume-9325"
... skipping 28 lines ...

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

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 10 lines ...
Jun 12 16:28:19.447: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 12 16:28:20.394: INFO: Successfully created a new PD: "aws://ap-northeast-2a/vol-032c5558ad4e0d9a9".
Jun 12 16:28:20.394: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-ljmt
STEP: Creating a pod to test exec-volume-test
Jun 12 16:28:20.556: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-ljmt" in namespace "volume-7340" to be "Succeeded or Failed"
Jun 12 16:28:20.714: INFO: Pod "exec-volume-test-inlinevolume-ljmt": Phase="Pending", Reason="", readiness=false. Elapsed: 158.168915ms
Jun 12 16:28:22.874: INFO: Pod "exec-volume-test-inlinevolume-ljmt": Phase="Pending", Reason="", readiness=false. Elapsed: 2.317754016s
Jun 12 16:28:25.038: INFO: Pod "exec-volume-test-inlinevolume-ljmt": Phase="Pending", Reason="", readiness=false. Elapsed: 4.481655031s
Jun 12 16:28:27.197: INFO: Pod "exec-volume-test-inlinevolume-ljmt": Phase="Pending", Reason="", readiness=false. Elapsed: 6.641320099s
Jun 12 16:28:29.356: INFO: Pod "exec-volume-test-inlinevolume-ljmt": Phase="Pending", Reason="", readiness=false. Elapsed: 8.799894777s
Jun 12 16:28:31.515: INFO: Pod "exec-volume-test-inlinevolume-ljmt": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.958882537s
STEP: Saw pod success
Jun 12 16:28:31.515: INFO: Pod "exec-volume-test-inlinevolume-ljmt" satisfied condition "Succeeded or Failed"
Jun 12 16:28:31.676: INFO: Trying to get logs from node ip-172-20-62-8.ap-northeast-2.compute.internal pod exec-volume-test-inlinevolume-ljmt container exec-container-inlinevolume-ljmt: <nil>
STEP: delete the pod
Jun 12 16:28:32.004: INFO: Waiting for pod exec-volume-test-inlinevolume-ljmt to disappear
Jun 12 16:28:32.163: INFO: Pod exec-volume-test-inlinevolume-ljmt no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-ljmt
Jun 12 16:28:32.163: INFO: Deleting pod "exec-volume-test-inlinevolume-ljmt" in namespace "volume-7340"
Jun 12 16:28:32.565: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-032c5558ad4e0d9a9", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-032c5558ad4e0d9a9 is currently attached to i-0990652e4330c67ef
	status code: 400, request id: 79374ce4-e6e0-4502-aa14-4ac3d0091fcf
Jun 12 16:28:38.309: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-032c5558ad4e0d9a9", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-032c5558ad4e0d9a9 is currently attached to i-0990652e4330c67ef
	status code: 400, request id: 31f12b7b-3ff2-439b-bbe5-0135cf1f23bc
Jun 12 16:28:44.116: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-032c5558ad4e0d9a9".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 16:28:44.116: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-7340" for this suite.
... skipping 149 lines ...
Jun 12 16:28:45.600: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 294 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 12 16:28:45.455: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename volumemode
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail to use a volume in a pod with mismatched mode [Slow]
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 12 16:28:46.271: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 12 16:28:47.219: INFO: Successfully created a new PD: "aws://ap-northeast-2a/vol-0fc68bc52241b3c50".
Jun 12 16:28:47.219: INFO: Creating resource for pre-provisioned PV
Jun 12 16:28:47.219: INFO: Creating PVC and PV
... skipping 2 lines ...
Jun 12 16:28:47.627: INFO: Waiting up to timeout=3m0s for PersistentVolumeClaims [pvc-mr84z] to have phase Bound
Jun 12 16:28:47.791: INFO: PersistentVolumeClaim pvc-mr84z found but phase is Pending instead of Bound.
Jun 12 16:28:49.955: INFO: PersistentVolumeClaim pvc-mr84z found and phase=Bound (2.327976817s)
Jun 12 16:28:49.955: INFO: Waiting up to 3m0s for PersistentVolume aws-bv9sm to have phase Bound
Jun 12 16:28:50.117: INFO: PersistentVolume aws-bv9sm found and phase=Bound (162.129146ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 12 16:28:53.097: INFO: Deleting pod "pod-2fe1111c-84f5-43bb-bde1-af4dbc841c4f" in namespace "volumemode-7425"
Jun 12 16:28:53.264: INFO: Wait up to 5m0s for pod "pod-2fe1111c-84f5-43bb-bde1-af4dbc841c4f" to be fully deleted
STEP: Deleting pv and pvc
Jun 12 16:28:55.589: INFO: Deleting PersistentVolumeClaim "pvc-mr84z"
Jun 12 16:28:55.753: INFO: Deleting PersistentVolume "aws-bv9sm"
Jun 12 16:28:56.210: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-0fc68bc52241b3c50".
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.oSPuir0e7/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.oSPuir0e7/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
    /tmp/kops.oSPuir0e7/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.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 12 16:28:56.539: INFO: Driver supports dynamic provisioning, skipping PreprovisionedPV pattern
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
... skipping 54 lines ...
Jun 12 16:25:29.435: INFO: Creating resource for dynamic PV
Jun 12 16:25:29.435: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-6375-e2e-scjq6b6
STEP: creating a claim
Jun 12 16:25:29.595: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 12 16:25:30.079: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-hczj2" in namespace "snapshotting-6375" to be "Succeeded or Failed"
Jun 12 16:25:30.239: INFO: Pod "pvc-snapshottable-tester-hczj2": Phase="Pending", Reason="", readiness=false. Elapsed: 159.597803ms
Jun 12 16:25:32.399: INFO: Pod "pvc-snapshottable-tester-hczj2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.319393666s
Jun 12 16:25:34.559: INFO: Pod "pvc-snapshottable-tester-hczj2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.479491442s
Jun 12 16:25:36.719: INFO: Pod "pvc-snapshottable-tester-hczj2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.63947525s
Jun 12 16:25:38.878: INFO: Pod "pvc-snapshottable-tester-hczj2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.798532792s
Jun 12 16:25:41.037: INFO: Pod "pvc-snapshottable-tester-hczj2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.957365571s
Jun 12 16:25:43.196: INFO: Pod "pvc-snapshottable-tester-hczj2": Phase="Pending", Reason="", readiness=false. Elapsed: 13.117106353s
Jun 12 16:25:45.355: INFO: Pod "pvc-snapshottable-tester-hczj2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 15.276110534s
STEP: Saw pod success
Jun 12 16:25:45.356: INFO: Pod "pvc-snapshottable-tester-hczj2" satisfied condition "Succeeded or Failed"
Jun 12 16:25:45.675: INFO: Pod pvc-snapshottable-tester-hczj2 has the following logs: 
Jun 12 16:25:45.675: INFO: Deleting pod "pvc-snapshottable-tester-hczj2" in namespace "snapshotting-6375"
Jun 12 16:25:45.846: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-hczj2" to be fully deleted
Jun 12 16:25:46.005: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.com46xgc] to have phase Bound
Jun 12 16:25:46.164: INFO: PersistentVolumeClaim ebs.csi.aws.com46xgc found and phase=Bound (159.129681ms)
STEP: [init] checking the claim
... skipping 50 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.oSPuir0e7/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 12 16:26:37.088: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-g55fk" in namespace "snapshotting-6375" to be "Succeeded or Failed"
Jun 12 16:26:37.247: INFO: Pod "pvc-snapshottable-data-tester-g55fk": Phase="Pending", Reason="", readiness=false. Elapsed: 158.67618ms
Jun 12 16:26:39.407: INFO: Pod "pvc-snapshottable-data-tester-g55fk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.319258992s
Jun 12 16:26:41.567: INFO: Pod "pvc-snapshottable-data-tester-g55fk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.478895802s
Jun 12 16:26:43.727: INFO: Pod "pvc-snapshottable-data-tester-g55fk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.639152174s
Jun 12 16:26:45.887: INFO: Pod "pvc-snapshottable-data-tester-g55fk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.798712513s
Jun 12 16:26:48.047: INFO: Pod "pvc-snapshottable-data-tester-g55fk": Phase="Pending", Reason="", readiness=false. Elapsed: 10.959302064s
Jun 12 16:26:50.209: INFO: Pod "pvc-snapshottable-data-tester-g55fk": Phase="Pending", Reason="", readiness=false. Elapsed: 13.120834068s
Jun 12 16:26:52.369: INFO: Pod "pvc-snapshottable-data-tester-g55fk": Phase="Pending", Reason="", readiness=false. Elapsed: 15.280753409s
Jun 12 16:26:54.531: INFO: Pod "pvc-snapshottable-data-tester-g55fk": Phase="Pending", Reason="", readiness=false. Elapsed: 17.443294403s
Jun 12 16:26:56.690: INFO: Pod "pvc-snapshottable-data-tester-g55fk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.602416746s
STEP: Saw pod success
Jun 12 16:26:56.691: INFO: Pod "pvc-snapshottable-data-tester-g55fk" satisfied condition "Succeeded or Failed"
Jun 12 16:26:57.009: INFO: Pod pvc-snapshottable-data-tester-g55fk has the following logs: 
Jun 12 16:26:57.009: INFO: Deleting pod "pvc-snapshottable-data-tester-g55fk" in namespace "snapshotting-6375"
Jun 12 16:26:57.174: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-g55fk" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 12 16:27:35.971: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-6375 exec restored-pvc-tester-8v26l --namespace=snapshotting-6375 -- cat /mnt/test/data'
... skipping 29 lines ...
Jun 12 16:28:01.539: INFO: volumesnapshotcontents pre-provisioned-snapcontent-a3996e59-3c10-403f-bfc5-dd50db04c22e has been found and is not deleted
Jun 12 16:28:02.698: INFO: volumesnapshotcontents pre-provisioned-snapcontent-a3996e59-3c10-403f-bfc5-dd50db04c22e has been found and is not deleted
Jun 12 16:28:03.860: INFO: volumesnapshotcontents pre-provisioned-snapcontent-a3996e59-3c10-403f-bfc5-dd50db04c22e has been found and is not deleted
Jun 12 16:28:05.020: INFO: volumesnapshotcontents pre-provisioned-snapcontent-a3996e59-3c10-403f-bfc5-dd50db04c22e has been found and is not deleted
Jun 12 16:28:06.180: INFO: volumesnapshotcontents pre-provisioned-snapcontent-a3996e59-3c10-403f-bfc5-dd50db04c22e has been found and is not deleted
Jun 12 16:28:07.339: INFO: volumesnapshotcontents pre-provisioned-snapcontent-a3996e59-3c10-403f-bfc5-dd50db04c22e has been found and is not deleted
Jun 12 16:28:08.340: INFO: WaitUntil failed after reaching the timeout 30s
[AfterEach] volume snapshot controller
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:221
Jun 12 16:28:08.502: INFO: Pod restored-pvc-tester-8v26l has the following logs: 
Jun 12 16:28:08.502: INFO: Deleting pod "restored-pvc-tester-8v26l" in namespace "snapshotting-6375"
Jun 12 16:28:08.663: INFO: Wait up to 5m0s for pod "restored-pvc-tester-8v26l" to be fully deleted
Jun 12 16:28:48.990: INFO: deleting claim "snapshotting-6375"/"pvc-ldphg"
... skipping 177 lines ...
Jun 12 16:28:53.629: INFO: Pod aws-client still exists
Jun 12 16:28:55.467: INFO: Waiting for pod aws-client to disappear
Jun 12 16:28:55.629: INFO: Pod aws-client still exists
Jun 12 16:28:57.467: INFO: Waiting for pod aws-client to disappear
Jun 12 16:28:57.630: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun 12 16:28:58.412: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-06e8bb6ae822396eb", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-06e8bb6ae822396eb is currently attached to i-0b8568a53b87b0a6d
	status code: 400, request id: f45e12ff-faac-4fbb-b0a3-c84a9e0af008
Jun 12 16:29:04.194: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-06e8bb6ae822396eb".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 16:29:04.194: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-527" for this suite.
... skipping 35 lines ...
Jun 12 16:28:31.962: INFO: PersistentVolumeClaim pvc-wx2tl found but phase is Pending instead of Bound.
Jun 12 16:28:34.122: INFO: PersistentVolumeClaim pvc-wx2tl found and phase=Bound (13.125226726s)
Jun 12 16:28:34.122: INFO: Waiting up to 3m0s for PersistentVolume aws-2b866 to have phase Bound
Jun 12 16:28:34.281: INFO: PersistentVolume aws-2b866 found and phase=Bound (159.749347ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-h2w7
STEP: Creating a pod to test exec-volume-test
Jun 12 16:28:34.773: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-h2w7" in namespace "volume-6295" to be "Succeeded or Failed"
Jun 12 16:28:34.933: INFO: Pod "exec-volume-test-preprovisionedpv-h2w7": Phase="Pending", Reason="", readiness=false. Elapsed: 159.437434ms
Jun 12 16:28:37.092: INFO: Pod "exec-volume-test-preprovisionedpv-h2w7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.319029815s
Jun 12 16:28:39.252: INFO: Pod "exec-volume-test-preprovisionedpv-h2w7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.478779452s
Jun 12 16:28:41.412: INFO: Pod "exec-volume-test-preprovisionedpv-h2w7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.638515276s
Jun 12 16:28:43.572: INFO: Pod "exec-volume-test-preprovisionedpv-h2w7": Phase="Running", Reason="", readiness=true. Elapsed: 8.798426272s
Jun 12 16:28:45.735: INFO: Pod "exec-volume-test-preprovisionedpv-h2w7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.961088412s
STEP: Saw pod success
Jun 12 16:28:45.735: INFO: Pod "exec-volume-test-preprovisionedpv-h2w7" satisfied condition "Succeeded or Failed"
Jun 12 16:28:45.894: INFO: Trying to get logs from node ip-172-20-40-134.ap-northeast-2.compute.internal pod exec-volume-test-preprovisionedpv-h2w7 container exec-container-preprovisionedpv-h2w7: <nil>
STEP: delete the pod
Jun 12 16:28:46.222: INFO: Waiting for pod exec-volume-test-preprovisionedpv-h2w7 to disappear
Jun 12 16:28:46.382: INFO: Pod exec-volume-test-preprovisionedpv-h2w7 no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-h2w7
Jun 12 16:28:46.382: INFO: Deleting pod "exec-volume-test-preprovisionedpv-h2w7" in namespace "volume-6295"
STEP: Deleting pv and pvc
Jun 12 16:28:46.542: INFO: Deleting PersistentVolumeClaim "pvc-wx2tl"
Jun 12 16:28:46.704: INFO: Deleting PersistentVolume "aws-2b866"
Jun 12 16:28:47.123: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0dd367a36cc10726a", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0dd367a36cc10726a is currently attached to i-06646d8971fcf1ba1
	status code: 400, request id: a40f3da9-d4bf-4e34-8a48-8da3d2289ff4
Jun 12 16:28:52.921: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0dd367a36cc10726a", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0dd367a36cc10726a is currently attached to i-06646d8971fcf1ba1
	status code: 400, request id: a79b22cb-7971-47ab-929d-aad5c1214192
Jun 12 16:28:58.676: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0dd367a36cc10726a", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0dd367a36cc10726a is currently attached to i-06646d8971fcf1ba1
	status code: 400, request id: 3bd7e605-6903-410d-851e-ea53c00c44d0
Jun 12 16:29:04.547: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0dd367a36cc10726a", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0dd367a36cc10726a is currently attached to i-06646d8971fcf1ba1
	status code: 400, request id: 49230851-adc2-4472-91b3-45136ba04351
Jun 12 16:29:10.336: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-0dd367a36cc10726a".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 16:29:10.336: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-6295" for this suite.
... skipping 405 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 12 16:28:24.782: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename provisioning
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail if subpath directory is outside the volume [Slow][LinuxOnly]
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun 12 16:28:25.587: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 12 16:28:25.587: INFO: Creating resource for dynamic PV
Jun 12 16:28:25.587: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8661gd6mr
STEP: creating a claim
Jun 12 16:28:25.746: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-6gp6
STEP: Checking for subpath error in container status
Jun 12 16:28:50.546: INFO: Deleting pod "pod-subpath-test-dynamicpv-6gp6" in namespace "provisioning-8661"
Jun 12 16:28:50.710: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-6gp6" to be fully deleted
STEP: Deleting pod
Jun 12 16:28:59.028: INFO: Deleting pod "pod-subpath-test-dynamicpv-6gp6" in namespace "provisioning-8661"
STEP: Deleting pvc
Jun 12 16:28:59.507: INFO: Deleting PersistentVolumeClaim "awswvqt6"
... skipping 15 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.oSPuir0e7/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.oSPuir0e7/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath directory is outside the volume [Slow][LinuxOnly]
      /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 12 16:29:26.108: INFO: Driver supports dynamic provisioning, skipping PreprovisionedPV pattern
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
... skipping 144 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 12 16:28:46.229: 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.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 12 16:28:47.029: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 12 16:28:47.029: INFO: Creating resource for dynamic PV
Jun 12 16:28:47.029: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-88158txrm
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 12 16:28:54.158: INFO: Deleting pod "pod-bd2cf738-e2ea-4aaa-8fde-77e7837319fd" in namespace "volumemode-8815"
Jun 12 16:28:54.329: INFO: Wait up to 5m0s for pod "pod-bd2cf738-e2ea-4aaa-8fde-77e7837319fd" to be fully deleted
STEP: Deleting pvc
Jun 12 16:28:58.971: INFO: Deleting PersistentVolumeClaim "awsn9hf8"
Jun 12 16:28:59.133: INFO: Waiting up to 5m0s for PersistentVolume pvc-463e0706-353c-495d-9a12-b47a56c1471c to get deleted
Jun 12 16:28:59.293: INFO: PersistentVolume pvc-463e0706-353c-495d-9a12-b47a56c1471c found and phase=Released (160.336739ms)
... skipping 14 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.oSPuir0e7/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.oSPuir0e7/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (block volmode)] volumeMode
    /tmp/kops.oSPuir0e7/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.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
S
------------------------------
[BeforeEach] [sig-storage] Zone Support [Feature:vsphere]
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 112 lines ...
Jun 12 16:29:01.568: INFO: PersistentVolumeClaim pvc-7nv92 found but phase is Pending instead of Bound.
Jun 12 16:29:03.731: INFO: PersistentVolumeClaim pvc-7nv92 found and phase=Bound (2.325652943s)
Jun 12 16:29:03.731: INFO: Waiting up to 3m0s for PersistentVolume aws-6rtpd to have phase Bound
Jun 12 16:29:03.893: INFO: PersistentVolume aws-6rtpd found and phase=Bound (162.178657ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-sx5g
STEP: Creating a pod to test exec-volume-test
Jun 12 16:29:04.390: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-sx5g" in namespace "volume-2580" to be "Succeeded or Failed"
Jun 12 16:29:04.552: INFO: Pod "exec-volume-test-preprovisionedpv-sx5g": Phase="Pending", Reason="", readiness=false. Elapsed: 162.177445ms
Jun 12 16:29:06.717: INFO: Pod "exec-volume-test-preprovisionedpv-sx5g": Phase="Pending", Reason="", readiness=false. Elapsed: 2.326606405s
Jun 12 16:29:08.880: INFO: Pod "exec-volume-test-preprovisionedpv-sx5g": Phase="Pending", Reason="", readiness=false. Elapsed: 4.490221918s
Jun 12 16:29:11.044: INFO: Pod "exec-volume-test-preprovisionedpv-sx5g": Phase="Pending", Reason="", readiness=false. Elapsed: 6.653736015s
Jun 12 16:29:13.207: INFO: Pod "exec-volume-test-preprovisionedpv-sx5g": Phase="Pending", Reason="", readiness=false. Elapsed: 8.816508709s
Jun 12 16:29:15.374: INFO: Pod "exec-volume-test-preprovisionedpv-sx5g": Phase="Pending", Reason="", readiness=false. Elapsed: 10.983702119s
Jun 12 16:29:17.538: INFO: Pod "exec-volume-test-preprovisionedpv-sx5g": Phase="Pending", Reason="", readiness=false. Elapsed: 13.147340475s
Jun 12 16:29:19.700: INFO: Pod "exec-volume-test-preprovisionedpv-sx5g": Phase="Pending", Reason="", readiness=false. Elapsed: 15.309892441s
Jun 12 16:29:21.864: INFO: Pod "exec-volume-test-preprovisionedpv-sx5g": Phase="Pending", Reason="", readiness=false. Elapsed: 17.474110946s
Jun 12 16:29:24.027: INFO: Pod "exec-volume-test-preprovisionedpv-sx5g": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.636650246s
STEP: Saw pod success
Jun 12 16:29:24.027: INFO: Pod "exec-volume-test-preprovisionedpv-sx5g" satisfied condition "Succeeded or Failed"
Jun 12 16:29:24.190: INFO: Trying to get logs from node ip-172-20-62-8.ap-northeast-2.compute.internal pod exec-volume-test-preprovisionedpv-sx5g container exec-container-preprovisionedpv-sx5g: <nil>
STEP: delete the pod
Jun 12 16:29:24.529: INFO: Waiting for pod exec-volume-test-preprovisionedpv-sx5g to disappear
Jun 12 16:29:24.691: INFO: Pod exec-volume-test-preprovisionedpv-sx5g no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-sx5g
Jun 12 16:29:24.691: INFO: Deleting pod "exec-volume-test-preprovisionedpv-sx5g" in namespace "volume-2580"
STEP: Deleting pv and pvc
Jun 12 16:29:24.853: INFO: Deleting PersistentVolumeClaim "pvc-7nv92"
Jun 12 16:29:25.019: INFO: Deleting PersistentVolume "aws-6rtpd"
Jun 12 16:29:25.426: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0001706247c0e9f27", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0001706247c0e9f27 is currently attached to i-0990652e4330c67ef
	status code: 400, request id: 2df783da-3aed-4f7a-b549-51ffa3acf4c6
Jun 12 16:29:31.189: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0001706247c0e9f27", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0001706247c0e9f27 is currently attached to i-0990652e4330c67ef
	status code: 400, request id: eb555db1-a6da-4038-a386-793589d73c8c
Jun 12 16:29:36.977: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-0001706247c0e9f27".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 16:29:36.977: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-2580" for this suite.
... skipping 20 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.oSPuir0e7/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.oSPuir0e7/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.oSPuir0e7/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.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 33 lines ...
Jun 12 16:28:43.886: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-21845sgqh
STEP: creating a claim
Jun 12 16:28:44.046: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-cm8n
STEP: Creating a pod to test exec-volume-test
Jun 12 16:28:44.535: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-cm8n" in namespace "volume-2184" to be "Succeeded or Failed"
Jun 12 16:28:44.694: INFO: Pod "exec-volume-test-dynamicpv-cm8n": Phase="Pending", Reason="", readiness=false. Elapsed: 159.089504ms
Jun 12 16:28:46.853: INFO: Pod "exec-volume-test-dynamicpv-cm8n": Phase="Pending", Reason="", readiness=false. Elapsed: 2.317685436s
Jun 12 16:28:49.011: INFO: Pod "exec-volume-test-dynamicpv-cm8n": Phase="Pending", Reason="", readiness=false. Elapsed: 4.476473322s
Jun 12 16:28:51.172: INFO: Pod "exec-volume-test-dynamicpv-cm8n": Phase="Pending", Reason="", readiness=false. Elapsed: 6.637052131s
Jun 12 16:28:53.332: INFO: Pod "exec-volume-test-dynamicpv-cm8n": Phase="Pending", Reason="", readiness=false. Elapsed: 8.796571229s
Jun 12 16:28:55.490: INFO: Pod "exec-volume-test-dynamicpv-cm8n": Phase="Pending", Reason="", readiness=false. Elapsed: 10.955238779s
... skipping 8 lines ...
Jun 12 16:29:14.922: INFO: Pod "exec-volume-test-dynamicpv-cm8n": Phase="Pending", Reason="", readiness=false. Elapsed: 30.386699705s
Jun 12 16:29:17.080: INFO: Pod "exec-volume-test-dynamicpv-cm8n": Phase="Pending", Reason="", readiness=false. Elapsed: 32.545195563s
Jun 12 16:29:19.239: INFO: Pod "exec-volume-test-dynamicpv-cm8n": Phase="Pending", Reason="", readiness=false. Elapsed: 34.704106542s
Jun 12 16:29:21.401: INFO: Pod "exec-volume-test-dynamicpv-cm8n": Phase="Pending", Reason="", readiness=false. Elapsed: 36.8661229s
Jun 12 16:29:23.563: INFO: Pod "exec-volume-test-dynamicpv-cm8n": Phase="Succeeded", Reason="", readiness=false. Elapsed: 39.0278059s
STEP: Saw pod success
Jun 12 16:29:23.563: INFO: Pod "exec-volume-test-dynamicpv-cm8n" satisfied condition "Succeeded or Failed"
Jun 12 16:29:23.723: INFO: Trying to get logs from node ip-172-20-49-72.ap-northeast-2.compute.internal pod exec-volume-test-dynamicpv-cm8n container exec-container-dynamicpv-cm8n: <nil>
STEP: delete the pod
Jun 12 16:29:24.053: INFO: Waiting for pod exec-volume-test-dynamicpv-cm8n to disappear
Jun 12 16:29:24.213: INFO: Pod exec-volume-test-dynamicpv-cm8n no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-cm8n
Jun 12 16:29:24.213: INFO: Deleting pod "exec-volume-test-dynamicpv-cm8n" in namespace "volume-2184"
... skipping 113 lines ...

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

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

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 31 lines ...
Jun 12 16:28:35.618: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-9678-e2e-scfxjbn      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-9678    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-9678-e2e-scfxjbn,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-9678    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-9678-e2e-scfxjbn,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-9678    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-9678-e2e-scfxjbn,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-9678-e2e-scfxjbn    c8eb4605-e64f-437e-975b-572681916a18 12314 0 2021-06-12 16:28:35 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-12 16:28:35 +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-wh7gd pvc- provisioning-9678  8372ebfa-c624-49a1-9b05-6501ee8a238d 12319 0 2021-06-12 16:28:36 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-12 16:28:36 +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-9678-e2e-scfxjbn,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-f0e11a4e-0da3-4d86-93d7-80a2902fb768 in namespace provisioning-9678
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun 12 16:28:59.340: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-9gllw" in namespace "provisioning-9678" to be "Succeeded or Failed"
Jun 12 16:28:59.495: INFO: Pod "pvc-volume-tester-writer-9gllw": Phase="Pending", Reason="", readiness=false. Elapsed: 154.952467ms
Jun 12 16:29:01.652: INFO: Pod "pvc-volume-tester-writer-9gllw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.311935815s
STEP: Saw pod success
Jun 12 16:29:01.652: INFO: Pod "pvc-volume-tester-writer-9gllw" satisfied condition "Succeeded or Failed"
Jun 12 16:29:01.966: INFO: Pod pvc-volume-tester-writer-9gllw has the following logs: 
Jun 12 16:29:01.966: INFO: Deleting pod "pvc-volume-tester-writer-9gllw" in namespace "provisioning-9678"
Jun 12 16:29:02.128: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-9gllw" 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-40-134.ap-northeast-2.compute.internal"
Jun 12 16:29:02.758: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-8x2tr" in namespace "provisioning-9678" to be "Succeeded or Failed"
Jun 12 16:29:02.914: INFO: Pod "pvc-volume-tester-reader-8x2tr": Phase="Pending", Reason="", readiness=false. Elapsed: 155.256282ms
Jun 12 16:29:05.070: INFO: Pod "pvc-volume-tester-reader-8x2tr": Phase="Pending", Reason="", readiness=false. Elapsed: 2.311901262s
Jun 12 16:29:07.227: INFO: Pod "pvc-volume-tester-reader-8x2tr": Phase="Pending", Reason="", readiness=false. Elapsed: 4.468917405s
Jun 12 16:29:09.383: INFO: Pod "pvc-volume-tester-reader-8x2tr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.624486405s
STEP: Saw pod success
Jun 12 16:29:09.383: INFO: Pod "pvc-volume-tester-reader-8x2tr" satisfied condition "Succeeded or Failed"
Jun 12 16:29:09.711: INFO: Pod pvc-volume-tester-reader-8x2tr has the following logs: hello world

Jun 12 16:29:09.711: INFO: Deleting pod "pvc-volume-tester-reader-8x2tr" in namespace "provisioning-9678"
Jun 12 16:29:09.872: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-8x2tr" to be fully deleted
Jun 12 16:29:10.032: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-wh7gd] to have phase Bound
Jun 12 16:29:10.187: INFO: PersistentVolumeClaim pvc-wh7gd found and phase=Bound (155.328734ms)
... skipping 54 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 12 16:28:46.722: 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.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun 12 16:28:47.565: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 12 16:28:47.565: INFO: Creating resource for dynamic PV
Jun 12 16:28:47.566: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3999kjl2f
STEP: creating a claim
Jun 12 16:28:47.724: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-4tsf
STEP: Checking for subpath error in container status
Jun 12 16:29:28.527: INFO: Deleting pod "pod-subpath-test-dynamicpv-4tsf" in namespace "provisioning-3999"
Jun 12 16:29:28.705: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-4tsf" to be fully deleted
STEP: Deleting pod
Jun 12 16:29:39.019: INFO: Deleting pod "pod-subpath-test-dynamicpv-4tsf" in namespace "provisioning-3999"
STEP: Deleting pvc
Jun 12 16:29:39.493: INFO: Deleting PersistentVolumeClaim "awsxl9vr"
... skipping 12 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.oSPuir0e7/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.oSPuir0e7/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath file is outside the volume [Slow][LinuxOnly]
      /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 12 16:29:50.603: 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.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Jun 12 16:29:51.547: INFO: found topology map[topology.kubernetes.io/zone:ap-northeast-2a]
Jun 12 16:29:51.547: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 12 16:29:51.547: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.oSPuir0e7/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.oSPuir0e7/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (delayed binding)] topology
    /tmp/kops.oSPuir0e7/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.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 82 lines ...
Jun 12 16:29:24.891: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-1191-e2e-sc2nvpm
STEP: creating a claim
Jun 12 16:29:25.057: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Jun 12 16:29:25.387: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 12 16:29:25.721: INFO: Error updating pvc ebs.csi.aws.comg2b9z: PersistentVolumeClaim "ebs.csi.aws.comg2b9z" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1191-e2e-sc2nvpm",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun 12 16:29:56.381: INFO: Error updating pvc ebs.csi.aws.comg2b9z: PersistentVolumeClaim "ebs.csi.aws.comg2b9z" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 107 lines ...
Jun 12 16:29:47.640: INFO: Waiting for pod aws-client to disappear
Jun 12 16:29:47.806: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 12 16:29:47.807: INFO: Deleting PersistentVolumeClaim "pvc-qlj45"
Jun 12 16:29:47.974: INFO: Deleting PersistentVolume "aws-jt4m7"
Jun 12 16:29:48.951: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-058796876f95f648b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-058796876f95f648b is currently attached to i-0b8568a53b87b0a6d
	status code: 400, request id: 975e625e-86f0-43e9-8412-65652ca4dcab
Jun 12 16:29:54.818: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-058796876f95f648b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-058796876f95f648b is currently attached to i-0b8568a53b87b0a6d
	status code: 400, request id: 6a5676f9-3532-4335-95b7-2a11189d8a30
Jun 12 16:30:00.624: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-058796876f95f648b".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 16:30:00.625: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8958" for this suite.
... skipping 94 lines ...
Jun 12 16:29:33.762: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-2823-e2e-sc228qk
STEP: creating a claim
Jun 12 16:29:33.921: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-2v4z
STEP: Creating a pod to test exec-volume-test
Jun 12 16:29:34.397: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-2v4z" in namespace "volume-2823" to be "Succeeded or Failed"
Jun 12 16:29:34.562: INFO: Pod "exec-volume-test-dynamicpv-2v4z": Phase="Pending", Reason="", readiness=false. Elapsed: 165.012762ms
Jun 12 16:29:36.720: INFO: Pod "exec-volume-test-dynamicpv-2v4z": Phase="Pending", Reason="", readiness=false. Elapsed: 2.322535722s
Jun 12 16:29:38.878: INFO: Pod "exec-volume-test-dynamicpv-2v4z": Phase="Pending", Reason="", readiness=false. Elapsed: 4.481015849s
Jun 12 16:29:41.036: INFO: Pod "exec-volume-test-dynamicpv-2v4z": Phase="Pending", Reason="", readiness=false. Elapsed: 6.638653505s
Jun 12 16:29:43.200: INFO: Pod "exec-volume-test-dynamicpv-2v4z": Phase="Pending", Reason="", readiness=false. Elapsed: 8.80330225s
Jun 12 16:29:45.359: INFO: Pod "exec-volume-test-dynamicpv-2v4z": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.962229633s
STEP: Saw pod success
Jun 12 16:29:45.359: INFO: Pod "exec-volume-test-dynamicpv-2v4z" satisfied condition "Succeeded or Failed"
Jun 12 16:29:45.517: INFO: Trying to get logs from node ip-172-20-40-134.ap-northeast-2.compute.internal pod exec-volume-test-dynamicpv-2v4z container exec-container-dynamicpv-2v4z: <nil>
STEP: delete the pod
Jun 12 16:29:45.842: INFO: Waiting for pod exec-volume-test-dynamicpv-2v4z to disappear
Jun 12 16:29:46.007: INFO: Pod exec-volume-test-dynamicpv-2v4z no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-2v4z
Jun 12 16:29:46.007: INFO: Deleting pod "exec-volume-test-dynamicpv-2v4z" in namespace "volume-2823"
... skipping 92 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 12 16:29:16.943: 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.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun 12 16:29:17.733: INFO: Creating resource for dynamic PV
Jun 12 16:29:17.733: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5844-e2e-sccpb7d
STEP: creating a claim
Jun 12 16:29:17.892: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-g2cf
STEP: Checking for subpath error in container status
Jun 12 16:29:42.696: INFO: Deleting pod "pod-subpath-test-dynamicpv-g2cf" in namespace "provisioning-5844"
Jun 12 16:29:42.861: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-g2cf" to be fully deleted
STEP: Deleting pod
Jun 12 16:29:49.181: INFO: Deleting pod "pod-subpath-test-dynamicpv-g2cf" in namespace "provisioning-5844"
STEP: Deleting pvc
Jun 12 16:29:49.662: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comhssvx"
... skipping 11 lines ...

• [SLOW TEST:49.011 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.oSPuir0e7/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.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
... skipping 95 lines ...
Jun 12 16:29:38.126: INFO: Creating resource for dynamic PV
Jun 12 16:29:38.126: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-3792-e2e-scjplvh
STEP: creating a claim
STEP: Expanding non-expandable pvc
Jun 12 16:29:38.616: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 12 16:29:38.944: INFO: Error updating pvc ebs.csi.aws.comn6nzm: PersistentVolumeClaim "ebs.csi.aws.comn6nzm" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3792-e2e-scjplvh",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun 12 16:30:09.599: INFO: Error updating pvc ebs.csi.aws.comn6nzm: PersistentVolumeClaim "ebs.csi.aws.comn6nzm" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 155 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 12 16:29:46.726: 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.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 12 16:29:47.515: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 12 16:29:48.478: INFO: Successfully created a new PD: "aws://ap-northeast-2a/vol-02c9ab8eb547f3212".
Jun 12 16:29:48.478: INFO: Creating resource for pre-provisioned PV
Jun 12 16:29:48.478: INFO: Creating PVC and PV
... skipping 8 lines ...
Jun 12 16:29:59.837: INFO: PersistentVolumeClaim pvc-9tkbj found but phase is Pending instead of Bound.
Jun 12 16:30:01.995: INFO: PersistentVolumeClaim pvc-9tkbj found but phase is Pending instead of Bound.
Jun 12 16:30:04.152: INFO: PersistentVolumeClaim pvc-9tkbj found and phase=Bound (15.266707094s)
Jun 12 16:30:04.152: INFO: Waiting up to 3m0s for PersistentVolume aws-7rwjq to have phase Bound
Jun 12 16:30:04.310: INFO: PersistentVolume aws-7rwjq found and phase=Bound (158.12728ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 12 16:30:07.261: INFO: Deleting pod "pod-e21936ca-430f-4acb-b7c6-3c8ff33b2714" in namespace "volumemode-4811"
Jun 12 16:30:07.420: INFO: Wait up to 5m0s for pod "pod-e21936ca-430f-4acb-b7c6-3c8ff33b2714" to be fully deleted
STEP: Deleting pv and pvc
Jun 12 16:30:17.737: INFO: Deleting PersistentVolumeClaim "pvc-9tkbj"
Jun 12 16:30:17.896: INFO: Deleting PersistentVolume "aws-7rwjq"
Jun 12 16:30:18.369: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-02c9ab8eb547f3212".
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.oSPuir0e7/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.oSPuir0e7/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
    /tmp/kops.oSPuir0e7/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.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand
  /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 270 lines ...
Jun 12 16:27:15.463: INFO: Creating resource for dynamic PV
Jun 12 16:27:15.463: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-9994-e2e-scmt479
STEP: creating a claim
Jun 12 16:27:15.622: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 12 16:27:16.100: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-gn4ff" in namespace "snapshotting-9994" to be "Succeeded or Failed"
Jun 12 16:27:16.261: INFO: Pod "pvc-snapshottable-tester-gn4ff": Phase="Pending", Reason="", readiness=false. Elapsed: 160.632514ms
Jun 12 16:27:18.423: INFO: Pod "pvc-snapshottable-tester-gn4ff": Phase="Pending", Reason="", readiness=false. Elapsed: 2.322951219s
Jun 12 16:27:20.581: INFO: Pod "pvc-snapshottable-tester-gn4ff": Phase="Pending", Reason="", readiness=false. Elapsed: 4.48106532s
Jun 12 16:27:22.740: INFO: Pod "pvc-snapshottable-tester-gn4ff": Phase="Pending", Reason="", readiness=false. Elapsed: 6.640480555s
Jun 12 16:27:24.899: INFO: Pod "pvc-snapshottable-tester-gn4ff": Phase="Pending", Reason="", readiness=false. Elapsed: 8.799424441s
Jun 12 16:27:27.058: INFO: Pod "pvc-snapshottable-tester-gn4ff": Phase="Pending", Reason="", readiness=false. Elapsed: 10.957680233s
Jun 12 16:27:29.217: INFO: Pod "pvc-snapshottable-tester-gn4ff": Phase="Pending", Reason="", readiness=false. Elapsed: 13.116678175s
Jun 12 16:27:31.376: INFO: Pod "pvc-snapshottable-tester-gn4ff": Phase="Pending", Reason="", readiness=false. Elapsed: 15.275919347s
Jun 12 16:27:33.535: INFO: Pod "pvc-snapshottable-tester-gn4ff": Phase="Pending", Reason="", readiness=false. Elapsed: 17.4350861s
Jun 12 16:27:35.695: INFO: Pod "pvc-snapshottable-tester-gn4ff": Phase="Pending", Reason="", readiness=false. Elapsed: 19.594619323s
Jun 12 16:27:37.854: INFO: Pod "pvc-snapshottable-tester-gn4ff": Phase="Pending", Reason="", readiness=false. Elapsed: 21.753966679s
Jun 12 16:27:40.015: INFO: Pod "pvc-snapshottable-tester-gn4ff": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.9146461s
STEP: Saw pod success
Jun 12 16:27:40.015: INFO: Pod "pvc-snapshottable-tester-gn4ff" satisfied condition "Succeeded or Failed"
Jun 12 16:27:40.336: INFO: Pod pvc-snapshottable-tester-gn4ff has the following logs: 
Jun 12 16:27:40.336: INFO: Deleting pod "pvc-snapshottable-tester-gn4ff" in namespace "snapshotting-9994"
Jun 12 16:27:40.502: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-gn4ff" to be fully deleted
Jun 12 16:27:40.663: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comfcjhx] to have phase Bound
Jun 12 16:27:40.822: INFO: PersistentVolumeClaim ebs.csi.aws.comfcjhx found and phase=Bound (158.286094ms)
STEP: [init] checking the claim
... skipping 57 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.oSPuir0e7/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 12 16:28:46.905: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-zx96m" in namespace "snapshotting-9994" to be "Succeeded or Failed"
Jun 12 16:28:47.063: INFO: Pod "pvc-snapshottable-data-tester-zx96m": Phase="Pending", Reason="", readiness=false. Elapsed: 158.161236ms
Jun 12 16:28:49.222: INFO: Pod "pvc-snapshottable-data-tester-zx96m": Phase="Pending", Reason="", readiness=false. Elapsed: 2.317621695s
Jun 12 16:28:51.383: INFO: Pod "pvc-snapshottable-data-tester-zx96m": Phase="Pending", Reason="", readiness=false. Elapsed: 4.478118752s
Jun 12 16:28:53.542: INFO: Pod "pvc-snapshottable-data-tester-zx96m": Phase="Pending", Reason="", readiness=false. Elapsed: 6.637804178s
Jun 12 16:28:55.702: INFO: Pod "pvc-snapshottable-data-tester-zx96m": Phase="Pending", Reason="", readiness=false. Elapsed: 8.796961782s
Jun 12 16:28:57.863: INFO: Pod "pvc-snapshottable-data-tester-zx96m": Phase="Pending", Reason="", readiness=false. Elapsed: 10.957892969s
Jun 12 16:29:00.022: INFO: Pod "pvc-snapshottable-data-tester-zx96m": Phase="Pending", Reason="", readiness=false. Elapsed: 13.11713905s
Jun 12 16:29:02.181: INFO: Pod "pvc-snapshottable-data-tester-zx96m": Phase="Pending", Reason="", readiness=false. Elapsed: 15.276661691s
Jun 12 16:29:04.345: INFO: Pod "pvc-snapshottable-data-tester-zx96m": Phase="Pending", Reason="", readiness=false. Elapsed: 17.440528882s
Jun 12 16:29:06.505: INFO: Pod "pvc-snapshottable-data-tester-zx96m": Phase="Pending", Reason="", readiness=false. Elapsed: 19.599956535s
Jun 12 16:29:08.668: INFO: Pod "pvc-snapshottable-data-tester-zx96m": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.76351354s
STEP: Saw pod success
Jun 12 16:29:08.668: INFO: Pod "pvc-snapshottable-data-tester-zx96m" satisfied condition "Succeeded or Failed"
Jun 12 16:29:08.988: INFO: Pod pvc-snapshottable-data-tester-zx96m has the following logs: 
Jun 12 16:29:08.988: INFO: Deleting pod "pvc-snapshottable-data-tester-zx96m" in namespace "snapshotting-9994"
Jun 12 16:29:09.156: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-zx96m" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 12 16:29:47.952: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-9994 exec restored-pvc-tester-xc8f8 --namespace=snapshotting-9994 -- cat /mnt/test/data'
... skipping 183 lines ...
Jun 12 16:29:53.928: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-899357brq
STEP: creating a claim
Jun 12 16:29:54.086: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-7w7n
STEP: Creating a pod to test exec-volume-test
Jun 12 16:29:54.572: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-7w7n" in namespace "volume-8993" to be "Succeeded or Failed"
Jun 12 16:29:54.729: INFO: Pod "exec-volume-test-dynamicpv-7w7n": Phase="Pending", Reason="", readiness=false. Elapsed: 156.77299ms
Jun 12 16:29:56.885: INFO: Pod "exec-volume-test-dynamicpv-7w7n": Phase="Pending", Reason="", readiness=false. Elapsed: 2.313373512s
Jun 12 16:29:59.043: INFO: Pod "exec-volume-test-dynamicpv-7w7n": Phase="Pending", Reason="", readiness=false. Elapsed: 4.47123999s
Jun 12 16:30:01.200: INFO: Pod "exec-volume-test-dynamicpv-7w7n": Phase="Pending", Reason="", readiness=false. Elapsed: 6.62837956s
Jun 12 16:30:03.357: INFO: Pod "exec-volume-test-dynamicpv-7w7n": Phase="Pending", Reason="", readiness=false. Elapsed: 8.785407701s
Jun 12 16:30:05.514: INFO: Pod "exec-volume-test-dynamicpv-7w7n": Phase="Pending", Reason="", readiness=false. Elapsed: 10.942283664s
Jun 12 16:30:07.671: INFO: Pod "exec-volume-test-dynamicpv-7w7n": Phase="Pending", Reason="", readiness=false. Elapsed: 13.099267961s
Jun 12 16:30:09.829: INFO: Pod "exec-volume-test-dynamicpv-7w7n": Phase="Pending", Reason="", readiness=false. Elapsed: 15.25698228s
Jun 12 16:30:11.986: INFO: Pod "exec-volume-test-dynamicpv-7w7n": Phase="Pending", Reason="", readiness=false. Elapsed: 17.414220512s
Jun 12 16:30:14.150: INFO: Pod "exec-volume-test-dynamicpv-7w7n": Phase="Pending", Reason="", readiness=false. Elapsed: 19.577620766s
Jun 12 16:30:16.307: INFO: Pod "exec-volume-test-dynamicpv-7w7n": Phase="Pending", Reason="", readiness=false. Elapsed: 21.734734788s
Jun 12 16:30:18.464: INFO: Pod "exec-volume-test-dynamicpv-7w7n": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.891682489s
STEP: Saw pod success
Jun 12 16:30:18.464: INFO: Pod "exec-volume-test-dynamicpv-7w7n" satisfied condition "Succeeded or Failed"
Jun 12 16:30:18.620: INFO: Trying to get logs from node ip-172-20-49-72.ap-northeast-2.compute.internal pod exec-volume-test-dynamicpv-7w7n container exec-container-dynamicpv-7w7n: <nil>
STEP: delete the pod
Jun 12 16:30:18.951: INFO: Waiting for pod exec-volume-test-dynamicpv-7w7n to disappear
Jun 12 16:30:19.108: INFO: Pod exec-volume-test-dynamicpv-7w7n no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-7w7n
Jun 12 16:30:19.108: INFO: Deleting pod "exec-volume-test-dynamicpv-7w7n" in namespace "volume-8993"
... skipping 1017 lines ...
    /tmp/kops.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/ephemeral.go:173
------------------------------


Summarizing 2 Failures:

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

[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.oSPuir0e7/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:602

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


Ginkgo ran 1 suite in 10m58.684860681s
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
I0612 16:32:20.031548   26808 app.go:59] RunDir for this run: "/logs/artifacts/1096665f-cb98-11eb-ab6f-62c732df09e9"
I0612 16:32:20.031997   26808 app.go:90] ID for this run: "1096665f-cb98-11eb-ab6f-62c732df09e9"
I0612 16:32:20.032071   26808 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
I0612 16:32:20.050734   26814 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
... skipping 1547 lines ...