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

No Test Failures!


Error lines from build-log.txt

... skipping 511 lines ...
I0614 08:11:12.188220   16893 up.go:43] Cleaning up any leaked resources from previous cluster
I0614 08:11:12.188233   16893 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
I0614 08:11:12.208817   16899 featureflag.go:167] FeatureFlag "SpecOverrideFlag"=true
I0614 08:11:12.209239   16899 featureflag.go:167] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io" not found
W0614 08:11:12.806839   16893 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0614 08:11:12.806890   16893 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
I0614 08:11:12.817998   16909 featureflag.go:167] FeatureFlag "SpecOverrideFlag"=true
I0614 08:11:12.818147   16909 featureflag.go:167] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io" not found
I0614 08:11:13.427414   16893 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/06/14 08:11:13 failed to get external ip from metadata service: http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip returned 404
I0614 08:11:13.442423   16893 http.go:37] curl https://ip.jsb.workers.dev
I0614 08:11:13.600066   16893 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.226.160.164/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-northeast-2a --master-size c5.large
I0614 08:11:13.613056   16924 featureflag.go:167] FeatureFlag "SpecOverrideFlag"=true
I0614 08:11:13.613166   16924 featureflag.go:167] FeatureFlag "AlphaAllowGCE"=true
I0614 08:11:13.672482   16924 create_cluster.go:732] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0614 08:11:14.344596   16924 new_cluster.go:1054]  Cloud Provider ID = aws
... skipping 40 lines ...

I0614 08:11:45.607195   16893 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
I0614 08:11:45.639872   16945 featureflag.go:167] FeatureFlag "SpecOverrideFlag"=true
I0614 08:11:45.640070   16945 featureflag.go:167] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io

W0614 08:11:47.306038   16945 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
W0614 08:11:57.348163   16945 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
W0614 08:12:07.408910   16945 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
W0614 08:12:17.472338   16945 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
W0614 08:12:27.517554   16945 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
W0614 08:12:37.562327   16945 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
W0614 08:12:47.608807   16945 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
W0614 08:12:57.669480   16945 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
W0614 08:13:07.715321   16945 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
W0614 08:13:17.774751   16945 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
W0614 08:13:27.817826   16945 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
W0614 08:13:37.881594   16945 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
W0614 08:13:47.927764   16945 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
W0614 08:13:57.985451   16945 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
W0614 08:14:08.020045   16945 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
W0614 08:14:18.066222   16945 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
W0614 08:14:28.115038   16945 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
W0614 08:14:38.159283   16945 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
W0614 08:14:48.207720   16945 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
W0614 08:14:58.255841   16945 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
W0614 08:15:08.298779   16945 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
W0614 08:15:18.342011   16945 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
W0614 08:15:28.402654   16945 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
W0614 08:15:38.461846   16945 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
W0614 08:15:48.524769   16945 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
W0614 08:15:58.572321   16945 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
W0614 08:16:08.616279   16945 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
W0614 08:16:18.656883   16945 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
W0614 08:16:28.699964   16945 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
W0614 08:16:38.749055   16945 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
W0614 08:16:48.797257   16945 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-kndcl	system-cluster-critical pod "cert-manager-webhook-7bbf67968-kndcl" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-f226d		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-f226d" is pending
Pod	kube-system/coredns-f45c4bf76-8tmt2			system-cluster-critical pod "coredns-f45c4bf76-8tmt2" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-tfh4l		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-tfh4l" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-xqp2r		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-xqp2r" is pending

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

... skipping 13 lines ...
Pod	kube-system/cert-manager-webhook-7bbf67968-kndcl	system-cluster-critical pod "cert-manager-webhook-7bbf67968-kndcl" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-f226d		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-f226d" is pending
Pod	kube-system/coredns-f45c4bf76-8tmt2			system-cluster-critical pod "coredns-f45c4bf76-8tmt2" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-tfh4l		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-tfh4l" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-xqp2r		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-xqp2r" is pending

Validation Failed
W0614 08:17:15.098680   16945 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 27 lines ...
Pod	kube-system/ebs-csi-node-pjzxh						system-node-critical pod "ebs-csi-node-pjzxh" is pending
Pod	kube-system/kube-proxy-ip-172-20-32-95.ap-northeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-32-95.ap-northeast-2.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-33-97.ap-northeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-33-97.ap-northeast-2.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-48-27.ap-northeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-48-27.ap-northeast-2.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-60-197.ap-northeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-60-197.ap-northeast-2.compute.internal" is pending

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

... skipping 22 lines ...
Pod	kube-system/ebs-csi-node-5d7kt						system-node-critical pod "ebs-csi-node-5d7kt" is pending
Pod	kube-system/ebs-csi-node-692g5						system-node-critical pod "ebs-csi-node-692g5" is pending
Pod	kube-system/ebs-csi-node-7xrsf						system-node-critical pod "ebs-csi-node-7xrsf" is pending
Pod	kube-system/ebs-csi-node-pjzxh						system-node-critical pod "ebs-csi-node-pjzxh" is pending
Pod	kube-system/kube-proxy-ip-172-20-33-97.ap-northeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-33-97.ap-northeast-2.compute.internal" is pending

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

... skipping 18 lines ...
Pod	kube-system/coredns-autoscaler-6f594f4c58-f226d		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-f226d" is pending
Pod	kube-system/coredns-f45c4bf76-8tmt2			system-cluster-critical pod "coredns-f45c4bf76-8tmt2" is pending
Pod	kube-system/ebs-csi-node-5d7kt				system-node-critical pod "ebs-csi-node-5d7kt" is pending
Pod	kube-system/ebs-csi-node-692g5				system-node-critical pod "ebs-csi-node-692g5" is pending
Pod	kube-system/ebs-csi-node-7xrsf				system-node-critical pod "ebs-csi-node-7xrsf" is pending

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

... skipping 13 lines ...
Pod	kube-system/calico-node-xrjj4				system-node-critical pod "calico-node-xrjj4" is not ready (calico-node)
Pod	kube-system/cert-manager-cainjector-74d69756d5-7kbkh	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-7kbkh" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-kndcl	system-cluster-critical pod "cert-manager-webhook-7bbf67968-kndcl" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-f226d		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-f226d" is pending
Pod	kube-system/coredns-f45c4bf76-8tmt2			system-cluster-critical pod "coredns-f45c4bf76-8tmt2" is pending

Validation Failed
W0614 08:18:06.095075   16945 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 7 lines ...

VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/cert-manager-webhook-7bbf67968-kndcl	system-cluster-critical pod "cert-manager-webhook-7bbf67968-kndcl" is not ready (cert-manager)
Pod	kube-system/coredns-f45c4bf76-4tmnq			system-cluster-critical pod "coredns-f45c4bf76-4tmnq" is pending

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

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

      Distro debian doesn't support ntfs -- skipping

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

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

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

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

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

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

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

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

    /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 21 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 14 08:21:36.532: 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.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 14 08:21:38.507: INFO: Creating resource for dynamic PV
Jun 14 08:21:38.507: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-8421-e2e-scd9c89
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 14 08:21:45.629: INFO: Deleting pod "pod-38e2f0da-9cee-44ed-9276-640884aa80e3" in namespace "volumemode-8421"
Jun 14 08:21:45.793: INFO: Wait up to 5m0s for pod "pod-38e2f0da-9cee-44ed-9276-640884aa80e3" to be fully deleted
STEP: Deleting pvc
Jun 14 08:21:52.426: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comzrl8w"
Jun 14 08:21:52.584: INFO: Waiting up to 5m0s for PersistentVolume pvc-7610b663-453a-4844-ba6e-353e479a9d78 to get deleted
Jun 14 08:21:52.748: INFO: PersistentVolume pvc-7610b663-453a-4844-ba6e-353e479a9d78 found and phase=Released (163.685316ms)
... skipping 8 lines ...

• [SLOW TEST:27.014 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.zEGyQTPHP/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.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
S
------------------------------
[BeforeEach] [sig-storage] Zone Support [Feature:vsphere]
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 58 lines ...
STEP: Creating a kubernetes client
Jun 14 08:21:34.840: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename volumemode
W0614 08:21:37.453528   30977 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Jun 14 08:21:37.453: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail to use a volume in a pod with mismatched mode [Slow]
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 14 08:21:37.772: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 14 08:21:38.755: INFO: Successfully created a new PD: "aws://ap-northeast-2a/vol-04c570103388f0e90".
Jun 14 08:21:38.755: INFO: Creating resource for pre-provisioned PV
Jun 14 08:21:38.755: INFO: Creating PVC and PV
... skipping 4 lines ...
Jun 14 08:21:41.613: INFO: PersistentVolumeClaim pvc-q9z8c found but phase is Pending instead of Bound.
Jun 14 08:21:43.779: INFO: PersistentVolumeClaim pvc-q9z8c found but phase is Pending instead of Bound.
Jun 14 08:21:45.941: INFO: PersistentVolumeClaim pvc-q9z8c found and phase=Bound (6.652928164s)
Jun 14 08:21:45.941: INFO: Waiting up to 3m0s for PersistentVolume aws-j9slt to have phase Bound
Jun 14 08:21:46.102: INFO: PersistentVolume aws-j9slt found and phase=Bound (160.036368ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 14 08:21:49.068: INFO: Deleting pod "pod-f193220b-55f8-4e95-a9cd-6e7fb1aa1283" in namespace "volumemode-4181"
Jun 14 08:21:49.230: INFO: Wait up to 5m0s for pod "pod-f193220b-55f8-4e95-a9cd-6e7fb1aa1283" to be fully deleted
STEP: Deleting pv and pvc
Jun 14 08:21:53.551: INFO: Deleting PersistentVolumeClaim "pvc-q9z8c"
Jun 14 08:21:53.715: INFO: Deleting PersistentVolume "aws-j9slt"
Jun 14 08:21:54.187: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-04c570103388f0e90", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04c570103388f0e90 is currently attached to i-0d03fe0f2c0571cc7
	status code: 400, request id: 3965feb9-428f-42f5-8765-0418cef63199
Jun 14 08:21:59.971: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-04c570103388f0e90", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04c570103388f0e90 is currently attached to i-0d03fe0f2c0571cc7
	status code: 400, request id: 67776e0d-50e2-4f44-a44e-63d884c7cfdc
Jun 14 08:22:05.740: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-04c570103388f0e90", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04c570103388f0e90 is currently attached to i-0d03fe0f2c0571cc7
	status code: 400, request id: 436f92f9-726b-4a03-a73c-dcfb5c8184ab
Jun 14 08:22:11.533: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-04c570103388f0e90".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 14 08:22:11.533: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-4181" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.zEGyQTPHP/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.zEGyQTPHP/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
    /tmp/kops.zEGyQTPHP/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.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 105 lines ...
Jun 14 08:21:35.916: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6374-e2e-scvwrc4
STEP: creating a claim
Jun 14 08:21:36.077: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-r6ff
STEP: Creating a pod to test subpath
Jun 14 08:21:36.558: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-r6ff" in namespace "provisioning-6374" to be "Succeeded or Failed"
Jun 14 08:21:36.720: INFO: Pod "pod-subpath-test-dynamicpv-r6ff": Phase="Pending", Reason="", readiness=false. Elapsed: 162.085688ms
Jun 14 08:21:38.879: INFO: Pod "pod-subpath-test-dynamicpv-r6ff": Phase="Pending", Reason="", readiness=false. Elapsed: 2.321425094s
Jun 14 08:21:41.038: INFO: Pod "pod-subpath-test-dynamicpv-r6ff": Phase="Pending", Reason="", readiness=false. Elapsed: 4.480125823s
Jun 14 08:21:43.197: INFO: Pod "pod-subpath-test-dynamicpv-r6ff": Phase="Pending", Reason="", readiness=false. Elapsed: 6.639741428s
Jun 14 08:21:45.356: INFO: Pod "pod-subpath-test-dynamicpv-r6ff": Phase="Pending", Reason="", readiness=false. Elapsed: 8.798761922s
Jun 14 08:21:47.517: INFO: Pod "pod-subpath-test-dynamicpv-r6ff": Phase="Pending", Reason="", readiness=false. Elapsed: 10.959417848s
... skipping 2 lines ...
Jun 14 08:21:53.995: INFO: Pod "pod-subpath-test-dynamicpv-r6ff": Phase="Pending", Reason="", readiness=false. Elapsed: 17.437458805s
Jun 14 08:21:56.154: INFO: Pod "pod-subpath-test-dynamicpv-r6ff": Phase="Pending", Reason="", readiness=false. Elapsed: 19.596253591s
Jun 14 08:21:58.316: INFO: Pod "pod-subpath-test-dynamicpv-r6ff": Phase="Pending", Reason="", readiness=false. Elapsed: 21.758452685s
Jun 14 08:22:00.474: INFO: Pod "pod-subpath-test-dynamicpv-r6ff": Phase="Pending", Reason="", readiness=false. Elapsed: 23.916890849s
Jun 14 08:22:02.635: INFO: Pod "pod-subpath-test-dynamicpv-r6ff": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.077628281s
STEP: Saw pod success
Jun 14 08:22:02.635: INFO: Pod "pod-subpath-test-dynamicpv-r6ff" satisfied condition "Succeeded or Failed"
Jun 14 08:22:02.793: INFO: Trying to get logs from node ip-172-20-48-27.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-r6ff container test-container-volume-dynamicpv-r6ff: <nil>
STEP: delete the pod
Jun 14 08:22:03.132: INFO: Waiting for pod pod-subpath-test-dynamicpv-r6ff to disappear
Jun 14 08:22:03.290: INFO: Pod pod-subpath-test-dynamicpv-r6ff no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-r6ff
Jun 14 08:22:03.290: INFO: Deleting pod "pod-subpath-test-dynamicpv-r6ff" in namespace "provisioning-6374"
... skipping 169 lines ...
Jun 14 08:21:39.701: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-370-e2e-scqwgd7
STEP: creating a claim
Jun 14 08:21:39.864: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-kz65
STEP: Creating a pod to test subpath
Jun 14 08:21:40.365: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-kz65" in namespace "provisioning-370" to be "Succeeded or Failed"
Jun 14 08:21:40.526: INFO: Pod "pod-subpath-test-dynamicpv-kz65": Phase="Pending", Reason="", readiness=false. Elapsed: 161.499928ms
Jun 14 08:21:42.692: INFO: Pod "pod-subpath-test-dynamicpv-kz65": Phase="Pending", Reason="", readiness=false. Elapsed: 2.326837285s
Jun 14 08:21:44.855: INFO: Pod "pod-subpath-test-dynamicpv-kz65": Phase="Pending", Reason="", readiness=false. Elapsed: 4.489638448s
Jun 14 08:21:47.016: INFO: Pod "pod-subpath-test-dynamicpv-kz65": Phase="Pending", Reason="", readiness=false. Elapsed: 6.651156334s
Jun 14 08:21:49.178: INFO: Pod "pod-subpath-test-dynamicpv-kz65": Phase="Pending", Reason="", readiness=false. Elapsed: 8.81279169s
Jun 14 08:21:51.340: INFO: Pod "pod-subpath-test-dynamicpv-kz65": Phase="Pending", Reason="", readiness=false. Elapsed: 10.975191424s
... skipping 3 lines ...
Jun 14 08:21:59.992: INFO: Pod "pod-subpath-test-dynamicpv-kz65": Phase="Pending", Reason="", readiness=false. Elapsed: 19.627475945s
Jun 14 08:22:02.156: INFO: Pod "pod-subpath-test-dynamicpv-kz65": Phase="Pending", Reason="", readiness=false. Elapsed: 21.790770337s
Jun 14 08:22:04.319: INFO: Pod "pod-subpath-test-dynamicpv-kz65": Phase="Pending", Reason="", readiness=false. Elapsed: 23.9541154s
Jun 14 08:22:06.482: INFO: Pod "pod-subpath-test-dynamicpv-kz65": Phase="Pending", Reason="", readiness=false. Elapsed: 26.117153904s
Jun 14 08:22:08.645: INFO: Pod "pod-subpath-test-dynamicpv-kz65": Phase="Succeeded", Reason="", readiness=false. Elapsed: 28.28058702s
STEP: Saw pod success
Jun 14 08:22:08.646: INFO: Pod "pod-subpath-test-dynamicpv-kz65" satisfied condition "Succeeded or Failed"
Jun 14 08:22:08.807: INFO: Trying to get logs from node ip-172-20-60-197.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-kz65 container test-container-subpath-dynamicpv-kz65: <nil>
STEP: delete the pod
Jun 14 08:22:09.154: INFO: Waiting for pod pod-subpath-test-dynamicpv-kz65 to disappear
Jun 14 08:22:09.315: INFO: Pod pod-subpath-test-dynamicpv-kz65 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-kz65
Jun 14 08:22:09.315: INFO: Deleting pod "pod-subpath-test-dynamicpv-kz65" in namespace "provisioning-370"
... skipping 28 lines ...
STEP: Creating a kubernetes client
Jun 14 08:21:34.800: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename provisioning
W0614 08:21:36.864982   30954 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Jun 14 08:21:36.865: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail if non-existent subpath is outside the volume [Slow][LinuxOnly]
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun 14 08:21:37.185: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 14 08:21:37.185: INFO: Creating resource for dynamic PV
Jun 14 08:21:37.185: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-92556vqp7
STEP: creating a claim
Jun 14 08:21:37.348: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-7psg
STEP: Checking for subpath error in container status
Jun 14 08:22:08.169: INFO: Deleting pod "pod-subpath-test-dynamicpv-7psg" in namespace "provisioning-9255"
Jun 14 08:22:08.334: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-7psg" to be fully deleted
STEP: Deleting pod
Jun 14 08:22:12.660: INFO: Deleting pod "pod-subpath-test-dynamicpv-7psg" in namespace "provisioning-9255"
STEP: Deleting pvc
Jun 14 08:22:13.143: INFO: Deleting PersistentVolumeClaim "aws5rx4d"
... skipping 13 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.zEGyQTPHP/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.zEGyQTPHP/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.zEGyQTPHP/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.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)(allowExpansion)][Feature:Windows] volume-expand
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 14 08:22:29.608: INFO: Driver ebs.csi.aws.com doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)(allowExpansion)][Feature:Windows] volume-expand
... skipping 175 lines ...
Jun 14 08:21:39.337: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1830dqsmn
STEP: creating a claim
Jun 14 08:21:39.498: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-sr5b
STEP: Creating a pod to test subpath
Jun 14 08:21:39.993: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-sr5b" in namespace "provisioning-1830" to be "Succeeded or Failed"
Jun 14 08:21:40.154: INFO: Pod "pod-subpath-test-dynamicpv-sr5b": Phase="Pending", Reason="", readiness=false. Elapsed: 160.922018ms
Jun 14 08:21:42.315: INFO: Pod "pod-subpath-test-dynamicpv-sr5b": Phase="Pending", Reason="", readiness=false. Elapsed: 2.321406414s
Jun 14 08:21:44.476: INFO: Pod "pod-subpath-test-dynamicpv-sr5b": Phase="Pending", Reason="", readiness=false. Elapsed: 4.483067981s
Jun 14 08:21:46.646: INFO: Pod "pod-subpath-test-dynamicpv-sr5b": Phase="Pending", Reason="", readiness=false. Elapsed: 6.653009695s
Jun 14 08:21:48.808: INFO: Pod "pod-subpath-test-dynamicpv-sr5b": Phase="Pending", Reason="", readiness=false. Elapsed: 8.814338512s
Jun 14 08:21:50.968: INFO: Pod "pod-subpath-test-dynamicpv-sr5b": Phase="Pending", Reason="", readiness=false. Elapsed: 10.975241718s
... skipping 3 lines ...
Jun 14 08:21:59.614: INFO: Pod "pod-subpath-test-dynamicpv-sr5b": Phase="Pending", Reason="", readiness=false. Elapsed: 19.620431437s
Jun 14 08:22:01.775: INFO: Pod "pod-subpath-test-dynamicpv-sr5b": Phase="Pending", Reason="", readiness=false. Elapsed: 21.781810258s
Jun 14 08:22:03.937: INFO: Pod "pod-subpath-test-dynamicpv-sr5b": Phase="Pending", Reason="", readiness=false. Elapsed: 23.943265542s
Jun 14 08:22:06.098: INFO: Pod "pod-subpath-test-dynamicpv-sr5b": Phase="Pending", Reason="", readiness=false. Elapsed: 26.105131125s
Jun 14 08:22:08.266: INFO: Pod "pod-subpath-test-dynamicpv-sr5b": Phase="Succeeded", Reason="", readiness=false. Elapsed: 28.272518441s
STEP: Saw pod success
Jun 14 08:22:08.266: INFO: Pod "pod-subpath-test-dynamicpv-sr5b" satisfied condition "Succeeded or Failed"
Jun 14 08:22:08.426: INFO: Trying to get logs from node ip-172-20-32-95.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-sr5b container test-container-subpath-dynamicpv-sr5b: <nil>
STEP: delete the pod
Jun 14 08:22:08.755: INFO: Waiting for pod pod-subpath-test-dynamicpv-sr5b to disappear
Jun 14 08:22:08.915: INFO: Pod pod-subpath-test-dynamicpv-sr5b no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-sr5b
Jun 14 08:22:08.915: INFO: Deleting pod "pod-subpath-test-dynamicpv-sr5b" in namespace "provisioning-1830"
STEP: Creating pod pod-subpath-test-dynamicpv-sr5b
STEP: Creating a pod to test subpath
Jun 14 08:22:09.237: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-sr5b" in namespace "provisioning-1830" to be "Succeeded or Failed"
Jun 14 08:22:09.401: INFO: Pod "pod-subpath-test-dynamicpv-sr5b": Phase="Pending", Reason="", readiness=false. Elapsed: 163.872097ms
Jun 14 08:22:11.564: INFO: Pod "pod-subpath-test-dynamicpv-sr5b": Phase="Pending", Reason="", readiness=false. Elapsed: 2.326549151s
Jun 14 08:22:13.724: INFO: Pod "pod-subpath-test-dynamicpv-sr5b": Phase="Pending", Reason="", readiness=false. Elapsed: 4.486994178s
Jun 14 08:22:15.886: INFO: Pod "pod-subpath-test-dynamicpv-sr5b": Phase="Pending", Reason="", readiness=false. Elapsed: 6.648884416s
Jun 14 08:22:18.050: INFO: Pod "pod-subpath-test-dynamicpv-sr5b": Phase="Pending", Reason="", readiness=false. Elapsed: 8.812253722s
Jun 14 08:22:20.212: INFO: Pod "pod-subpath-test-dynamicpv-sr5b": Phase="Pending", Reason="", readiness=false. Elapsed: 10.974774041s
Jun 14 08:22:22.373: INFO: Pod "pod-subpath-test-dynamicpv-sr5b": Phase="Succeeded", Reason="", readiness=false. Elapsed: 13.135430049s
STEP: Saw pod success
Jun 14 08:22:22.373: INFO: Pod "pod-subpath-test-dynamicpv-sr5b" satisfied condition "Succeeded or Failed"
Jun 14 08:22:22.533: INFO: Trying to get logs from node ip-172-20-32-95.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-sr5b container test-container-subpath-dynamicpv-sr5b: <nil>
STEP: delete the pod
Jun 14 08:22:22.866: INFO: Waiting for pod pod-subpath-test-dynamicpv-sr5b to disappear
Jun 14 08:22:23.026: INFO: Pod pod-subpath-test-dynamicpv-sr5b no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-sr5b
Jun 14 08:22:23.026: INFO: Deleting pod "pod-subpath-test-dynamicpv-sr5b" in namespace "provisioning-1830"
... skipping 41 lines ...
Jun 14 08:21:35.893: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1145-e2e-sct54zw
STEP: creating a claim
Jun 14 08:21:36.052: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-cgf6
STEP: Creating a pod to test subpath
Jun 14 08:21:36.529: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-cgf6" in namespace "provisioning-1145" to be "Succeeded or Failed"
Jun 14 08:21:36.689: INFO: Pod "pod-subpath-test-dynamicpv-cgf6": Phase="Pending", Reason="", readiness=false. Elapsed: 160.248368ms
Jun 14 08:21:38.848: INFO: Pod "pod-subpath-test-dynamicpv-cgf6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.319037783s
Jun 14 08:21:41.007: INFO: Pod "pod-subpath-test-dynamicpv-cgf6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.478049051s
Jun 14 08:21:43.165: INFO: Pod "pod-subpath-test-dynamicpv-cgf6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.636088858s
Jun 14 08:21:45.324: INFO: Pod "pod-subpath-test-dynamicpv-cgf6": Phase="Pending", Reason="", readiness=false. Elapsed: 8.795231872s
Jun 14 08:21:47.482: INFO: Pod "pod-subpath-test-dynamicpv-cgf6": Phase="Pending", Reason="", readiness=false. Elapsed: 10.953347637s
... skipping 4 lines ...
Jun 14 08:21:58.276: INFO: Pod "pod-subpath-test-dynamicpv-cgf6": Phase="Pending", Reason="", readiness=false. Elapsed: 21.746658585s
Jun 14 08:22:00.433: INFO: Pod "pod-subpath-test-dynamicpv-cgf6": Phase="Pending", Reason="", readiness=false. Elapsed: 23.904529449s
Jun 14 08:22:02.593: INFO: Pod "pod-subpath-test-dynamicpv-cgf6": Phase="Pending", Reason="", readiness=false. Elapsed: 26.063879182s
Jun 14 08:22:04.751: INFO: Pod "pod-subpath-test-dynamicpv-cgf6": Phase="Pending", Reason="", readiness=false. Elapsed: 28.222528486s
Jun 14 08:22:06.910: INFO: Pod "pod-subpath-test-dynamicpv-cgf6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 30.381214658s
STEP: Saw pod success
Jun 14 08:22:06.910: INFO: Pod "pod-subpath-test-dynamicpv-cgf6" satisfied condition "Succeeded or Failed"
Jun 14 08:22:07.067: INFO: Trying to get logs from node ip-172-20-32-95.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-cgf6 container test-container-subpath-dynamicpv-cgf6: <nil>
STEP: delete the pod
Jun 14 08:22:07.756: INFO: Waiting for pod pod-subpath-test-dynamicpv-cgf6 to disappear
Jun 14 08:22:07.913: INFO: Pod pod-subpath-test-dynamicpv-cgf6 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-cgf6
Jun 14 08:22:07.913: INFO: Deleting pod "pod-subpath-test-dynamicpv-cgf6" in namespace "provisioning-1145"
STEP: Creating pod pod-subpath-test-dynamicpv-cgf6
STEP: Creating a pod to test subpath
Jun 14 08:22:08.233: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-cgf6" in namespace "provisioning-1145" to be "Succeeded or Failed"
Jun 14 08:22:08.392: INFO: Pod "pod-subpath-test-dynamicpv-cgf6": Phase="Pending", Reason="", readiness=false. Elapsed: 158.803157ms
Jun 14 08:22:10.556: INFO: Pod "pod-subpath-test-dynamicpv-cgf6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.322726384s
Jun 14 08:22:12.716: INFO: Pod "pod-subpath-test-dynamicpv-cgf6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.482270119s
Jun 14 08:22:14.874: INFO: Pod "pod-subpath-test-dynamicpv-cgf6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.641100998s
Jun 14 08:22:17.034: INFO: Pod "pod-subpath-test-dynamicpv-cgf6": Phase="Pending", Reason="", readiness=false. Elapsed: 8.800973613s
Jun 14 08:22:19.192: INFO: Pod "pod-subpath-test-dynamicpv-cgf6": Phase="Pending", Reason="", readiness=false. Elapsed: 10.95914046s
Jun 14 08:22:21.351: INFO: Pod "pod-subpath-test-dynamicpv-cgf6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 13.118089399s
STEP: Saw pod success
Jun 14 08:22:21.351: INFO: Pod "pod-subpath-test-dynamicpv-cgf6" satisfied condition "Succeeded or Failed"
Jun 14 08:22:21.508: INFO: Trying to get logs from node ip-172-20-32-95.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-cgf6 container test-container-subpath-dynamicpv-cgf6: <nil>
STEP: delete the pod
Jun 14 08:22:21.831: INFO: Waiting for pod pod-subpath-test-dynamicpv-cgf6 to disappear
Jun 14 08:22:21.988: INFO: Pod pod-subpath-test-dynamicpv-cgf6 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-cgf6
Jun 14 08:22:21.988: INFO: Deleting pod "pod-subpath-test-dynamicpv-cgf6" in namespace "provisioning-1145"
... skipping 99 lines ...
STEP: Creating a kubernetes client
Jun 14 08:21:34.639: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename provisioning
W0614 08:21:35.659717   30801 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Jun 14 08:21:35.659: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly]
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun 14 08:21:35.975: INFO: Creating resource for dynamic PV
Jun 14 08:21:35.975: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2381-e2e-sc2s62r
STEP: creating a claim
Jun 14 08:21:36.136: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-wrs7
STEP: Checking for subpath error in container status
Jun 14 08:22:10.938: INFO: Deleting pod "pod-subpath-test-dynamicpv-wrs7" in namespace "provisioning-2381"
Jun 14 08:22:11.100: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-wrs7" to be fully deleted
STEP: Deleting pod
Jun 14 08:22:23.421: INFO: Deleting pod "pod-subpath-test-dynamicpv-wrs7" in namespace "provisioning-2381"
STEP: Deleting pvc
Jun 14 08:22:23.896: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comz669l"
... skipping 15 lines ...

• [SLOW TEST:86.362 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.zEGyQTPHP/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.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 219 lines ...
STEP: Deleting pod hostexec-ip-172-20-33-97.ap-northeast-2.compute.internal-58gzq in namespace volumemode-2351
Jun 14 08:22:40.300: INFO: Deleting pod "pod-9dfe65c9-b692-48db-9b4a-414ebe6566c0" in namespace "volumemode-2351"
Jun 14 08:22:40.462: INFO: Wait up to 5m0s for pod "pod-9dfe65c9-b692-48db-9b4a-414ebe6566c0" to be fully deleted
STEP: Deleting pv and pvc
Jun 14 08:22:52.783: INFO: Deleting PersistentVolumeClaim "pvc-ctfhz"
Jun 14 08:22:52.945: INFO: Deleting PersistentVolume "aws-cwqvh"
Jun 14 08:22:53.356: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0151a4664289949d1", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0151a4664289949d1 is currently attached to i-0d03fe0f2c0571cc7
	status code: 400, request id: 2a20720f-8443-48cb-b786-46f42c518324
Jun 14 08:22:59.214: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0151a4664289949d1", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0151a4664289949d1 is currently attached to i-0d03fe0f2c0571cc7
	status code: 400, request id: 791523a9-f287-4981-824c-eb8b801ed7b5
Jun 14 08:23:05.038: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-0151a4664289949d1".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 14 08:23:05.038: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-2351" for this suite.
... skipping 290 lines ...
Jun 14 08:21:37.018: INFO: Creating resource for dynamic PV
Jun 14 08:21:37.018: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6922-e2e-scsws55
STEP: creating a claim
Jun 14 08:21:37.177: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-6922
Jun 14 08:21:37.668: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-6922" in namespace "provisioning-6922" to be "Succeeded or Failed"
Jun 14 08:21:37.826: INFO: Pod "volume-prep-provisioning-6922": Phase="Pending", Reason="", readiness=false. Elapsed: 158.069987ms
Jun 14 08:21:39.986: INFO: Pod "volume-prep-provisioning-6922": Phase="Pending", Reason="", readiness=false. Elapsed: 2.317875923s
Jun 14 08:21:42.145: INFO: Pod "volume-prep-provisioning-6922": Phase="Pending", Reason="", readiness=false. Elapsed: 4.477578681s
Jun 14 08:21:44.303: INFO: Pod "volume-prep-provisioning-6922": Phase="Pending", Reason="", readiness=false. Elapsed: 6.635575198s
Jun 14 08:21:46.463: INFO: Pod "volume-prep-provisioning-6922": Phase="Pending", Reason="", readiness=false. Elapsed: 8.795122123s
Jun 14 08:21:48.621: INFO: Pod "volume-prep-provisioning-6922": Phase="Pending", Reason="", readiness=false. Elapsed: 10.953214358s
Jun 14 08:21:50.780: INFO: Pod "volume-prep-provisioning-6922": Phase="Pending", Reason="", readiness=false. Elapsed: 13.112196384s
Jun 14 08:21:52.939: INFO: Pod "volume-prep-provisioning-6922": Phase="Pending", Reason="", readiness=false. Elapsed: 15.271399271s
Jun 14 08:21:55.097: INFO: Pod "volume-prep-provisioning-6922": Phase="Pending", Reason="", readiness=false. Elapsed: 17.429144876s
Jun 14 08:21:57.254: INFO: Pod "volume-prep-provisioning-6922": Phase="Pending", Reason="", readiness=false. Elapsed: 19.586742521s
Jun 14 08:21:59.412: INFO: Pod "volume-prep-provisioning-6922": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.744787785s
STEP: Saw pod success
Jun 14 08:21:59.413: INFO: Pod "volume-prep-provisioning-6922" satisfied condition "Succeeded or Failed"
Jun 14 08:21:59.413: INFO: Deleting pod "volume-prep-provisioning-6922" in namespace "provisioning-6922"
Jun 14 08:21:59.576: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-6922" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-csms
STEP: Checking for subpath error in container status
Jun 14 08:22:34.208: INFO: Deleting pod "pod-subpath-test-dynamicpv-csms" in namespace "provisioning-6922"
Jun 14 08:22:34.370: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-csms" to be fully deleted
STEP: Deleting pod
Jun 14 08:22:34.528: INFO: Deleting pod "pod-subpath-test-dynamicpv-csms" in namespace "provisioning-6922"
STEP: Deleting pvc
Jun 14 08:22:35.001: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comw47z4"
... skipping 353 lines ...

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

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

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

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

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

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

      Not enough topologies in cluster -- skipping

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun 14 08:23:56.775: INFO: Error updating pvc ebs.csi.aws.comj98s5: PersistentVolumeClaim "ebs.csi.aws.comj98s5" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 135 lines ...
Jun 14 08:22:59.150: INFO: PersistentVolumeClaim pvc-b2lkm found but phase is Pending instead of Bound.
Jun 14 08:23:01.312: INFO: PersistentVolumeClaim pvc-b2lkm found and phase=Bound (8.804662385s)
Jun 14 08:23:01.312: INFO: Waiting up to 3m0s for PersistentVolume aws-fj4xt to have phase Bound
Jun 14 08:23:01.472: INFO: PersistentVolume aws-fj4xt found and phase=Bound (159.937517ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-qkw8
STEP: Creating a pod to test exec-volume-test
Jun 14 08:23:01.958: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-qkw8" in namespace "volume-1605" to be "Succeeded or Failed"
Jun 14 08:23:02.118: INFO: Pod "exec-volume-test-preprovisionedpv-qkw8": Phase="Pending", Reason="", readiness=false. Elapsed: 160.085307ms
Jun 14 08:23:04.285: INFO: Pod "exec-volume-test-preprovisionedpv-qkw8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.326248532s
Jun 14 08:23:06.453: INFO: Pod "exec-volume-test-preprovisionedpv-qkw8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.494369311s
Jun 14 08:23:08.614: INFO: Pod "exec-volume-test-preprovisionedpv-qkw8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.655416073s
Jun 14 08:23:10.774: INFO: Pod "exec-volume-test-preprovisionedpv-qkw8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.81572731s
Jun 14 08:23:12.935: INFO: Pod "exec-volume-test-preprovisionedpv-qkw8": Phase="Pending", Reason="", readiness=false. Elapsed: 10.976994846s
... skipping 7 lines ...
Jun 14 08:23:30.231: INFO: Pod "exec-volume-test-preprovisionedpv-qkw8": Phase="Pending", Reason="", readiness=false. Elapsed: 28.272584857s
Jun 14 08:23:32.393: INFO: Pod "exec-volume-test-preprovisionedpv-qkw8": Phase="Pending", Reason="", readiness=false. Elapsed: 30.434336192s
Jun 14 08:23:34.553: INFO: Pod "exec-volume-test-preprovisionedpv-qkw8": Phase="Pending", Reason="", readiness=false. Elapsed: 32.594898698s
Jun 14 08:23:36.715: INFO: Pod "exec-volume-test-preprovisionedpv-qkw8": Phase="Pending", Reason="", readiness=false. Elapsed: 34.756704983s
Jun 14 08:23:38.877: INFO: Pod "exec-volume-test-preprovisionedpv-qkw8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 36.91860461s
STEP: Saw pod success
Jun 14 08:23:38.877: INFO: Pod "exec-volume-test-preprovisionedpv-qkw8" satisfied condition "Succeeded or Failed"
Jun 14 08:23:39.037: INFO: Trying to get logs from node ip-172-20-48-27.ap-northeast-2.compute.internal pod exec-volume-test-preprovisionedpv-qkw8 container exec-container-preprovisionedpv-qkw8: <nil>
STEP: delete the pod
Jun 14 08:23:39.365: INFO: Waiting for pod exec-volume-test-preprovisionedpv-qkw8 to disappear
Jun 14 08:23:39.525: INFO: Pod exec-volume-test-preprovisionedpv-qkw8 no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-qkw8
Jun 14 08:23:39.525: INFO: Deleting pod "exec-volume-test-preprovisionedpv-qkw8" in namespace "volume-1605"
STEP: Deleting pv and pvc
Jun 14 08:23:39.685: INFO: Deleting PersistentVolumeClaim "pvc-b2lkm"
Jun 14 08:23:39.846: INFO: Deleting PersistentVolume "aws-fj4xt"
Jun 14 08:23:40.278: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-04b4f591ce7aa480e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04b4f591ce7aa480e is currently attached to i-0bec054b8ebd8f3d8
	status code: 400, request id: d1d10b26-caf3-4718-b7d1-75df491d75d6
Jun 14 08:23:46.060: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-04b4f591ce7aa480e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04b4f591ce7aa480e is currently attached to i-0bec054b8ebd8f3d8
	status code: 400, request id: 68e08280-f421-4db8-a884-b9e6ddf0da05
Jun 14 08:23:51.843: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-04b4f591ce7aa480e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04b4f591ce7aa480e is currently attached to i-0bec054b8ebd8f3d8
	status code: 400, request id: 066a3aec-6bea-48af-9265-9c8d3ab186d9
Jun 14 08:23:57.641: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-04b4f591ce7aa480e".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 14 08:23:57.641: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-1605" for this suite.
... skipping 268 lines ...
Jun 14 08:21:38.911: INFO: Creating resource for dynamic PV
Jun 14 08:21:38.911: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-5380-e2e-sct2kcw
STEP: creating a claim
Jun 14 08:21:39.073: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 14 08:21:39.560: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-npvnq" in namespace "snapshotting-5380" to be "Succeeded or Failed"
Jun 14 08:21:39.720: INFO: Pod "pvc-snapshottable-tester-npvnq": Phase="Pending", Reason="", readiness=false. Elapsed: 160.583327ms
Jun 14 08:21:41.882: INFO: Pod "pvc-snapshottable-tester-npvnq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.321968384s
Jun 14 08:21:44.045: INFO: Pod "pvc-snapshottable-tester-npvnq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.48488012s
Jun 14 08:21:46.206: INFO: Pod "pvc-snapshottable-tester-npvnq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.645889745s
Jun 14 08:21:48.367: INFO: Pod "pvc-snapshottable-tester-npvnq": Phase="Pending", Reason="", readiness=false. Elapsed: 8.807092402s
Jun 14 08:21:50.530: INFO: Pod "pvc-snapshottable-tester-npvnq": Phase="Pending", Reason="", readiness=false. Elapsed: 10.970271217s
... skipping 4 lines ...
Jun 14 08:22:01.375: INFO: Pod "pvc-snapshottable-tester-npvnq": Phase="Pending", Reason="", readiness=false. Elapsed: 21.815240799s
Jun 14 08:22:03.537: INFO: Pod "pvc-snapshottable-tester-npvnq": Phase="Pending", Reason="", readiness=false. Elapsed: 23.977585011s
Jun 14 08:22:05.699: INFO: Pod "pvc-snapshottable-tester-npvnq": Phase="Pending", Reason="", readiness=false. Elapsed: 26.139078445s
Jun 14 08:22:07.861: INFO: Pod "pvc-snapshottable-tester-npvnq": Phase="Pending", Reason="", readiness=false. Elapsed: 28.301330441s
Jun 14 08:22:10.023: INFO: Pod "pvc-snapshottable-tester-npvnq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 30.463331908s
STEP: Saw pod success
Jun 14 08:22:10.023: INFO: Pod "pvc-snapshottable-tester-npvnq" satisfied condition "Succeeded or Failed"
Jun 14 08:22:10.370: INFO: Pod pvc-snapshottable-tester-npvnq has the following logs: 
Jun 14 08:22:10.370: INFO: Deleting pod "pvc-snapshottable-tester-npvnq" in namespace "snapshotting-5380"
Jun 14 08:22:10.540: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-npvnq" to be fully deleted
Jun 14 08:22:10.700: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comcbxt2] to have phase Bound
Jun 14 08:22:10.861: INFO: PersistentVolumeClaim ebs.csi.aws.comcbxt2 found and phase=Bound (160.885267ms)
STEP: [init] checking the claim
... skipping 38 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.zEGyQTPHP/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 14 08:22:35.888: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-j8sq8" in namespace "snapshotting-5380" to be "Succeeded or Failed"
Jun 14 08:22:36.049: INFO: Pod "pvc-snapshottable-data-tester-j8sq8": Phase="Pending", Reason="", readiness=false. Elapsed: 160.772076ms
Jun 14 08:22:38.211: INFO: Pod "pvc-snapshottable-data-tester-j8sq8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.322759433s
Jun 14 08:22:40.375: INFO: Pod "pvc-snapshottable-data-tester-j8sq8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.48685502s
Jun 14 08:22:42.536: INFO: Pod "pvc-snapshottable-data-tester-j8sq8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.648181295s
Jun 14 08:22:44.697: INFO: Pod "pvc-snapshottable-data-tester-j8sq8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.809398258s
Jun 14 08:22:46.860: INFO: Pod "pvc-snapshottable-data-tester-j8sq8": Phase="Pending", Reason="", readiness=false. Elapsed: 10.971719384s
Jun 14 08:22:49.021: INFO: Pod "pvc-snapshottable-data-tester-j8sq8": Phase="Pending", Reason="", readiness=false. Elapsed: 13.132959337s
Jun 14 08:22:51.183: INFO: Pod "pvc-snapshottable-data-tester-j8sq8": Phase="Pending", Reason="", readiness=false. Elapsed: 15.294892454s
Jun 14 08:22:53.345: INFO: Pod "pvc-snapshottable-data-tester-j8sq8": Phase="Pending", Reason="", readiness=false. Elapsed: 17.457352422s
Jun 14 08:22:55.510: INFO: Pod "pvc-snapshottable-data-tester-j8sq8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.622264627s
STEP: Saw pod success
Jun 14 08:22:55.510: INFO: Pod "pvc-snapshottable-data-tester-j8sq8" satisfied condition "Succeeded or Failed"
Jun 14 08:22:55.842: INFO: Pod pvc-snapshottable-data-tester-j8sq8 has the following logs: 
Jun 14 08:22:55.842: INFO: Deleting pod "pvc-snapshottable-data-tester-j8sq8" in namespace "snapshotting-5380"
Jun 14 08:22:56.009: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-j8sq8" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 14 08:23:10.819: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-5380 exec restored-pvc-tester-dspwb --namespace=snapshotting-5380 -- cat /mnt/test/data'
... skipping 170 lines ...
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 14 08:24:02.826: 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.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Jun 14 08:24:03.831: INFO: found topology map[topology.kubernetes.io/zone:ap-northeast-2a]
Jun 14 08:24:03.831: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 14 08:24:03.831: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.zEGyQTPHP/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.zEGyQTPHP/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (immediate binding)] topology
    /tmp/kops.zEGyQTPHP/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.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 152 lines ...
Jun 14 08:23:30.205: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6278x4hks
STEP: creating a claim
Jun 14 08:23:30.363: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-xwr8
STEP: Creating a pod to test subpath
Jun 14 08:23:30.849: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-xwr8" in namespace "provisioning-6278" to be "Succeeded or Failed"
Jun 14 08:23:31.007: INFO: Pod "pod-subpath-test-dynamicpv-xwr8": Phase="Pending", Reason="", readiness=false. Elapsed: 157.510978ms
Jun 14 08:23:33.164: INFO: Pod "pod-subpath-test-dynamicpv-xwr8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.315116333s
Jun 14 08:23:35.322: INFO: Pod "pod-subpath-test-dynamicpv-xwr8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.472801788s
Jun 14 08:23:37.479: INFO: Pod "pod-subpath-test-dynamicpv-xwr8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.630232903s
Jun 14 08:23:39.637: INFO: Pod "pod-subpath-test-dynamicpv-xwr8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.788167383s
Jun 14 08:23:41.796: INFO: Pod "pod-subpath-test-dynamicpv-xwr8": Phase="Pending", Reason="", readiness=false. Elapsed: 10.947340703s
Jun 14 08:23:43.954: INFO: Pod "pod-subpath-test-dynamicpv-xwr8": Phase="Pending", Reason="", readiness=false. Elapsed: 13.105385641s
Jun 14 08:23:46.118: INFO: Pod "pod-subpath-test-dynamicpv-xwr8": Phase="Pending", Reason="", readiness=false. Elapsed: 15.268845965s
Jun 14 08:23:48.276: INFO: Pod "pod-subpath-test-dynamicpv-xwr8": Phase="Pending", Reason="", readiness=false. Elapsed: 17.426743022s
Jun 14 08:23:50.434: INFO: Pod "pod-subpath-test-dynamicpv-xwr8": Phase="Pending", Reason="", readiness=false. Elapsed: 19.585332512s
Jun 14 08:23:52.592: INFO: Pod "pod-subpath-test-dynamicpv-xwr8": Phase="Pending", Reason="", readiness=false. Elapsed: 21.743048235s
Jun 14 08:23:54.751: INFO: Pod "pod-subpath-test-dynamicpv-xwr8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.901544144s
STEP: Saw pod success
Jun 14 08:23:54.751: INFO: Pod "pod-subpath-test-dynamicpv-xwr8" satisfied condition "Succeeded or Failed"
Jun 14 08:23:54.908: INFO: Trying to get logs from node ip-172-20-33-97.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-xwr8 container test-container-volume-dynamicpv-xwr8: <nil>
STEP: delete the pod
Jun 14 08:23:55.231: INFO: Waiting for pod pod-subpath-test-dynamicpv-xwr8 to disappear
Jun 14 08:23:55.389: INFO: Pod pod-subpath-test-dynamicpv-xwr8 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-xwr8
Jun 14 08:23:55.389: INFO: Deleting pod "pod-subpath-test-dynamicpv-xwr8" in namespace "provisioning-6278"
... skipping 123 lines ...
Jun 14 08:23:43.013: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-25038p2c5
STEP: creating a claim
Jun 14 08:23:43.174: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-d9zp
STEP: Creating a pod to test subpath
Jun 14 08:23:43.668: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-d9zp" in namespace "provisioning-2503" to be "Succeeded or Failed"
Jun 14 08:23:43.829: INFO: Pod "pod-subpath-test-dynamicpv-d9zp": Phase="Pending", Reason="", readiness=false. Elapsed: 160.469798ms
Jun 14 08:23:45.991: INFO: Pod "pod-subpath-test-dynamicpv-d9zp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.322830224s
Jun 14 08:23:48.153: INFO: Pod "pod-subpath-test-dynamicpv-d9zp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.48503556s
Jun 14 08:23:50.315: INFO: Pod "pod-subpath-test-dynamicpv-d9zp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.647086689s
Jun 14 08:23:52.477: INFO: Pod "pod-subpath-test-dynamicpv-d9zp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.809272622s
Jun 14 08:23:54.639: INFO: Pod "pod-subpath-test-dynamicpv-d9zp": Phase="Pending", Reason="", readiness=false. Elapsed: 10.97068196s
Jun 14 08:23:56.800: INFO: Pod "pod-subpath-test-dynamicpv-d9zp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 13.132059709s
STEP: Saw pod success
Jun 14 08:23:56.800: INFO: Pod "pod-subpath-test-dynamicpv-d9zp" satisfied condition "Succeeded or Failed"
Jun 14 08:23:56.962: INFO: Trying to get logs from node ip-172-20-60-197.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-d9zp container test-container-subpath-dynamicpv-d9zp: <nil>
STEP: delete the pod
Jun 14 08:23:57.290: INFO: Waiting for pod pod-subpath-test-dynamicpv-d9zp to disappear
Jun 14 08:23:57.451: INFO: Pod pod-subpath-test-dynamicpv-d9zp no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-d9zp
Jun 14 08:23:57.451: INFO: Deleting pod "pod-subpath-test-dynamicpv-d9zp" in namespace "provisioning-2503"
... skipping 38 lines ...
Jun 14 08:23:54.826: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3197-e2e-sc4zlcv
STEP: creating a claim
Jun 14 08:23:54.988: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-nx8s
STEP: Creating a pod to test multi_subpath
Jun 14 08:23:55.476: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-nx8s" in namespace "provisioning-3197" to be "Succeeded or Failed"
Jun 14 08:23:55.638: INFO: Pod "pod-subpath-test-dynamicpv-nx8s": Phase="Pending", Reason="", readiness=false. Elapsed: 161.780698ms
Jun 14 08:23:57.800: INFO: Pod "pod-subpath-test-dynamicpv-nx8s": Phase="Pending", Reason="", readiness=false. Elapsed: 2.323428012s
Jun 14 08:23:59.962: INFO: Pod "pod-subpath-test-dynamicpv-nx8s": Phase="Pending", Reason="", readiness=false. Elapsed: 4.485653605s
Jun 14 08:24:02.127: INFO: Pod "pod-subpath-test-dynamicpv-nx8s": Phase="Pending", Reason="", readiness=false. Elapsed: 6.651027394s
Jun 14 08:24:04.289: INFO: Pod "pod-subpath-test-dynamicpv-nx8s": Phase="Pending", Reason="", readiness=false. Elapsed: 8.813046331s
Jun 14 08:24:06.451: INFO: Pod "pod-subpath-test-dynamicpv-nx8s": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.974811896s
STEP: Saw pod success
Jun 14 08:24:06.451: INFO: Pod "pod-subpath-test-dynamicpv-nx8s" satisfied condition "Succeeded or Failed"
Jun 14 08:24:06.613: INFO: Trying to get logs from node ip-172-20-60-197.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-nx8s container test-container-subpath-dynamicpv-nx8s: <nil>
STEP: delete the pod
Jun 14 08:24:06.949: INFO: Waiting for pod pod-subpath-test-dynamicpv-nx8s to disappear
Jun 14 08:24:07.110: INFO: Pod pod-subpath-test-dynamicpv-nx8s no longer exists
STEP: Deleting pod
Jun 14 08:24:07.110: INFO: Deleting pod "pod-subpath-test-dynamicpv-nx8s" in namespace "provisioning-3197"
... skipping 268 lines ...
Jun 14 08:24:00.738: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8106r6m5n
STEP: creating a claim
Jun 14 08:24:00.900: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-8bm8
STEP: Creating a pod to test subpath
Jun 14 08:24:01.392: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-8bm8" in namespace "provisioning-8106" to be "Succeeded or Failed"
Jun 14 08:24:01.554: INFO: Pod "pod-subpath-test-dynamicpv-8bm8": Phase="Pending", Reason="", readiness=false. Elapsed: 161.752115ms
Jun 14 08:24:03.716: INFO: Pod "pod-subpath-test-dynamicpv-8bm8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.324105363s
Jun 14 08:24:05.878: INFO: Pod "pod-subpath-test-dynamicpv-8bm8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.486305909s
Jun 14 08:24:08.040: INFO: Pod "pod-subpath-test-dynamicpv-8bm8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.648363884s
Jun 14 08:24:10.207: INFO: Pod "pod-subpath-test-dynamicpv-8bm8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.814833341s
Jun 14 08:24:12.370: INFO: Pod "pod-subpath-test-dynamicpv-8bm8": Phase="Pending", Reason="", readiness=false. Elapsed: 10.977977826s
Jun 14 08:24:14.532: INFO: Pod "pod-subpath-test-dynamicpv-8bm8": Phase="Pending", Reason="", readiness=false. Elapsed: 13.140289381s
Jun 14 08:24:16.696: INFO: Pod "pod-subpath-test-dynamicpv-8bm8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 15.304032985s
STEP: Saw pod success
Jun 14 08:24:16.696: INFO: Pod "pod-subpath-test-dynamicpv-8bm8" satisfied condition "Succeeded or Failed"
Jun 14 08:24:16.859: INFO: Trying to get logs from node ip-172-20-48-27.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-8bm8 container test-container-volume-dynamicpv-8bm8: <nil>
STEP: delete the pod
Jun 14 08:24:17.203: INFO: Waiting for pod pod-subpath-test-dynamicpv-8bm8 to disappear
Jun 14 08:24:17.365: INFO: Pod pod-subpath-test-dynamicpv-8bm8 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-8bm8
Jun 14 08:24:17.365: INFO: Deleting pod "pod-subpath-test-dynamicpv-8bm8" in namespace "provisioning-8106"
... skipping 122 lines ...
Jun 14 08:23:58.773: INFO: Creating resource for dynamic PV
Jun 14 08:23:58.773: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-1784ttfpb
STEP: creating a claim
STEP: Expanding non-expandable pvc
Jun 14 08:23:59.260: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 14 08:23:59.580: INFO: Error updating pvc awsl2ht2: PersistentVolumeClaim "awsl2ht2" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1784ttfpb",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun 14 08:24:30.255: INFO: Error updating pvc awsl2ht2: PersistentVolumeClaim "awsl2ht2" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 42 lines ...
Jun 14 08:21:37.923: INFO: Creating resource for dynamic PV
Jun 14 08:21:37.923: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-7910-e2e-scrwtvk
STEP: creating a claim
Jun 14 08:21:38.084: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 14 08:21:38.569: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-f9p4k" in namespace "snapshotting-7910" to be "Succeeded or Failed"
Jun 14 08:21:38.729: INFO: Pod "pvc-snapshottable-tester-f9p4k": Phase="Pending", Reason="", readiness=false. Elapsed: 160.219387ms
Jun 14 08:21:40.889: INFO: Pod "pvc-snapshottable-tester-f9p4k": Phase="Pending", Reason="", readiness=false. Elapsed: 2.320493626s
Jun 14 08:21:43.051: INFO: Pod "pvc-snapshottable-tester-f9p4k": Phase="Pending", Reason="", readiness=false. Elapsed: 4.482022012s
Jun 14 08:21:45.216: INFO: Pod "pvc-snapshottable-tester-f9p4k": Phase="Pending", Reason="", readiness=false. Elapsed: 6.647513067s
Jun 14 08:21:47.384: INFO: Pod "pvc-snapshottable-tester-f9p4k": Phase="Pending", Reason="", readiness=false. Elapsed: 8.814829821s
Jun 14 08:21:49.544: INFO: Pod "pvc-snapshottable-tester-f9p4k": Phase="Pending", Reason="", readiness=false. Elapsed: 10.975673549s
Jun 14 08:21:51.708: INFO: Pod "pvc-snapshottable-tester-f9p4k": Phase="Pending", Reason="", readiness=false. Elapsed: 13.139317475s
Jun 14 08:21:53.870: INFO: Pod "pvc-snapshottable-tester-f9p4k": Phase="Pending", Reason="", readiness=false. Elapsed: 15.300951348s
Jun 14 08:21:56.032: INFO: Pod "pvc-snapshottable-tester-f9p4k": Phase="Succeeded", Reason="", readiness=false. Elapsed: 17.462805275s
STEP: Saw pod success
Jun 14 08:21:56.032: INFO: Pod "pvc-snapshottable-tester-f9p4k" satisfied condition "Succeeded or Failed"
Jun 14 08:21:56.601: INFO: Pod pvc-snapshottable-tester-f9p4k has the following logs: 
Jun 14 08:21:56.601: INFO: Deleting pod "pvc-snapshottable-tester-f9p4k" in namespace "snapshotting-7910"
Jun 14 08:21:56.769: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-f9p4k" to be fully deleted
Jun 14 08:21:56.929: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comv8njr] to have phase Bound
Jun 14 08:21:57.089: INFO: PersistentVolumeClaim ebs.csi.aws.comv8njr found and phase=Bound (160.067077ms)
STEP: [init] checking the claim
... skipping 27 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.zEGyQTPHP/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 14 08:22:35.619: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-kwbkz" in namespace "snapshotting-7910" to be "Succeeded or Failed"
Jun 14 08:22:35.779: INFO: Pod "pvc-snapshottable-data-tester-kwbkz": Phase="Pending", Reason="", readiness=false. Elapsed: 160.202837ms
Jun 14 08:22:37.941: INFO: Pod "pvc-snapshottable-data-tester-kwbkz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.321884262s
Jun 14 08:22:40.102: INFO: Pod "pvc-snapshottable-data-tester-kwbkz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.483398749s
Jun 14 08:22:42.263: INFO: Pod "pvc-snapshottable-data-tester-kwbkz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.643865264s
Jun 14 08:22:44.424: INFO: Pod "pvc-snapshottable-data-tester-kwbkz": Phase="Pending", Reason="", readiness=false. Elapsed: 8.805222429s
Jun 14 08:22:46.585: INFO: Pod "pvc-snapshottable-data-tester-kwbkz": Phase="Pending", Reason="", readiness=false. Elapsed: 10.966167794s
Jun 14 08:22:48.746: INFO: Pod "pvc-snapshottable-data-tester-kwbkz": Phase="Pending", Reason="", readiness=false. Elapsed: 13.127525927s
Jun 14 08:22:50.908: INFO: Pod "pvc-snapshottable-data-tester-kwbkz": Phase="Pending", Reason="", readiness=false. Elapsed: 15.289416064s
Jun 14 08:22:53.069: INFO: Pod "pvc-snapshottable-data-tester-kwbkz": Phase="Succeeded", Reason="", readiness=false. Elapsed: 17.450550343s
STEP: Saw pod success
Jun 14 08:22:53.069: INFO: Pod "pvc-snapshottable-data-tester-kwbkz" satisfied condition "Succeeded or Failed"
Jun 14 08:22:53.391: INFO: Pod pvc-snapshottable-data-tester-kwbkz has the following logs: 
Jun 14 08:22:53.392: INFO: Deleting pod "pvc-snapshottable-data-tester-kwbkz" in namespace "snapshotting-7910"
Jun 14 08:22:53.558: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-kwbkz" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 14 08:23:08.365: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-7910 exec restored-pvc-tester-zz7p7 --namespace=snapshotting-7910 -- cat /mnt/test/data'
... skipping 29 lines ...
Jun 14 08:23:33.910: INFO: volumesnapshotcontents snapcontent-1fa693bf-b501-48fb-830b-a8ac6a90f640 has been found and is not deleted
Jun 14 08:23:35.072: INFO: volumesnapshotcontents snapcontent-1fa693bf-b501-48fb-830b-a8ac6a90f640 has been found and is not deleted
Jun 14 08:23:36.233: INFO: volumesnapshotcontents snapcontent-1fa693bf-b501-48fb-830b-a8ac6a90f640 has been found and is not deleted
Jun 14 08:23:37.394: INFO: volumesnapshotcontents snapcontent-1fa693bf-b501-48fb-830b-a8ac6a90f640 has been found and is not deleted
Jun 14 08:23:38.555: INFO: volumesnapshotcontents snapcontent-1fa693bf-b501-48fb-830b-a8ac6a90f640 has been found and is not deleted
Jun 14 08:23:39.717: INFO: volumesnapshotcontents snapcontent-1fa693bf-b501-48fb-830b-a8ac6a90f640 has been found and is not deleted
Jun 14 08:23:40.717: INFO: WaitUntil failed after reaching the timeout 30s
[AfterEach] volume snapshot controller
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:221
Jun 14 08:23:40.879: INFO: Pod restored-pvc-tester-zz7p7 has the following logs: 
Jun 14 08:23:40.879: INFO: Deleting pod "restored-pvc-tester-zz7p7" in namespace "snapshotting-7910"
Jun 14 08:23:41.041: INFO: Wait up to 5m0s for pod "restored-pvc-tester-zz7p7" to be fully deleted
Jun 14 08:24:23.362: INFO: deleting claim "snapshotting-7910"/"pvc-snb6v"
... skipping 52 lines ...
Jun 14 08:23:59.896: INFO: PersistentVolumeClaim pvc-2vt9j found but phase is Pending instead of Bound.
Jun 14 08:24:02.055: INFO: PersistentVolumeClaim pvc-2vt9j found and phase=Bound (2.317311504s)
Jun 14 08:24:02.055: INFO: Waiting up to 3m0s for PersistentVolume aws-w7wmw to have phase Bound
Jun 14 08:24:02.213: INFO: PersistentVolume aws-w7wmw found and phase=Bound (157.567057ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-7zmc
STEP: Creating a pod to test exec-volume-test
Jun 14 08:24:02.685: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-7zmc" in namespace "volume-7432" to be "Succeeded or Failed"
Jun 14 08:24:02.842: INFO: Pod "exec-volume-test-preprovisionedpv-7zmc": Phase="Pending", Reason="", readiness=false. Elapsed: 157.464887ms
Jun 14 08:24:05.000: INFO: Pod "exec-volume-test-preprovisionedpv-7zmc": Phase="Pending", Reason="", readiness=false. Elapsed: 2.315592133s
Jun 14 08:24:07.160: INFO: Pod "exec-volume-test-preprovisionedpv-7zmc": Phase="Pending", Reason="", readiness=false. Elapsed: 4.475407169s
Jun 14 08:24:09.319: INFO: Pod "exec-volume-test-preprovisionedpv-7zmc": Phase="Pending", Reason="", readiness=false. Elapsed: 6.633809416s
Jun 14 08:24:11.476: INFO: Pod "exec-volume-test-preprovisionedpv-7zmc": Phase="Pending", Reason="", readiness=false. Elapsed: 8.791313461s
Jun 14 08:24:13.635: INFO: Pod "exec-volume-test-preprovisionedpv-7zmc": Phase="Pending", Reason="", readiness=false. Elapsed: 10.950081487s
Jun 14 08:24:15.795: INFO: Pod "exec-volume-test-preprovisionedpv-7zmc": Phase="Succeeded", Reason="", readiness=false. Elapsed: 13.110279622s
STEP: Saw pod success
Jun 14 08:24:15.795: INFO: Pod "exec-volume-test-preprovisionedpv-7zmc" satisfied condition "Succeeded or Failed"
Jun 14 08:24:15.954: INFO: Trying to get logs from node ip-172-20-33-97.ap-northeast-2.compute.internal pod exec-volume-test-preprovisionedpv-7zmc container exec-container-preprovisionedpv-7zmc: <nil>
STEP: delete the pod
Jun 14 08:24:16.280: INFO: Waiting for pod exec-volume-test-preprovisionedpv-7zmc to disappear
Jun 14 08:24:16.437: INFO: Pod exec-volume-test-preprovisionedpv-7zmc no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-7zmc
Jun 14 08:24:16.437: INFO: Deleting pod "exec-volume-test-preprovisionedpv-7zmc" in namespace "volume-7432"
STEP: Deleting pv and pvc
Jun 14 08:24:16.594: INFO: Deleting PersistentVolumeClaim "pvc-2vt9j"
Jun 14 08:24:16.752: INFO: Deleting PersistentVolume "aws-w7wmw"
Jun 14 08:24:17.179: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-02796edb59c59c418", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02796edb59c59c418 is currently attached to i-0d03fe0f2c0571cc7
	status code: 400, request id: 60c416b4-9d3a-4d19-8376-623d73b230be
Jun 14 08:24:22.968: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-02796edb59c59c418", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02796edb59c59c418 is currently attached to i-0d03fe0f2c0571cc7
	status code: 400, request id: d2bc5362-226c-4651-b40c-97264479b3b2
Jun 14 08:24:28.774: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-02796edb59c59c418", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02796edb59c59c418 is currently attached to i-0d03fe0f2c0571cc7
	status code: 400, request id: 4ff4e632-3a6a-4b30-a876-83a357de08fb
Jun 14 08:24:34.585: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-02796edb59c59c418", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02796edb59c59c418 is currently attached to i-0d03fe0f2c0571cc7
	status code: 400, request id: e065fe0f-516f-4eed-8c67-67df7e3ea080
Jun 14 08:24:40.393: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-02796edb59c59c418".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 14 08:24:40.393: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-7432" for this suite.
... skipping 253 lines ...
Jun 14 08:23:59.941: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9229qz455
STEP: creating a claim
Jun 14 08:24:00.097: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-9kr9
STEP: Creating a pod to test multi_subpath
Jun 14 08:24:00.585: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-9kr9" in namespace "provisioning-9229" to be "Succeeded or Failed"
Jun 14 08:24:00.740: INFO: Pod "pod-subpath-test-dynamicpv-9kr9": Phase="Pending", Reason="", readiness=false. Elapsed: 154.760838ms
Jun 14 08:24:02.896: INFO: Pod "pod-subpath-test-dynamicpv-9kr9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.310698665s
Jun 14 08:24:05.051: INFO: Pod "pod-subpath-test-dynamicpv-9kr9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.466194931s
Jun 14 08:24:07.208: INFO: Pod "pod-subpath-test-dynamicpv-9kr9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.622838497s
Jun 14 08:24:09.364: INFO: Pod "pod-subpath-test-dynamicpv-9kr9": Phase="Pending", Reason="", readiness=false. Elapsed: 8.778940853s
Jun 14 08:24:11.521: INFO: Pod "pod-subpath-test-dynamicpv-9kr9": Phase="Pending", Reason="", readiness=false. Elapsed: 10.935525039s
Jun 14 08:24:13.681: INFO: Pod "pod-subpath-test-dynamicpv-9kr9": Phase="Pending", Reason="", readiness=false. Elapsed: 13.095827245s
Jun 14 08:24:15.837: INFO: Pod "pod-subpath-test-dynamicpv-9kr9": Phase="Pending", Reason="", readiness=false. Elapsed: 15.251772299s
Jun 14 08:24:17.993: INFO: Pod "pod-subpath-test-dynamicpv-9kr9": Phase="Pending", Reason="", readiness=false. Elapsed: 17.407650735s
Jun 14 08:24:20.149: INFO: Pod "pod-subpath-test-dynamicpv-9kr9": Phase="Pending", Reason="", readiness=false. Elapsed: 19.563818931s
Jun 14 08:24:22.304: INFO: Pod "pod-subpath-test-dynamicpv-9kr9": Phase="Pending", Reason="", readiness=false. Elapsed: 21.719148635s
Jun 14 08:24:24.459: INFO: Pod "pod-subpath-test-dynamicpv-9kr9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.874170294s
STEP: Saw pod success
Jun 14 08:24:24.459: INFO: Pod "pod-subpath-test-dynamicpv-9kr9" satisfied condition "Succeeded or Failed"
Jun 14 08:24:24.614: INFO: Trying to get logs from node ip-172-20-60-197.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-9kr9 container test-container-subpath-dynamicpv-9kr9: <nil>
STEP: delete the pod
Jun 14 08:24:24.941: INFO: Waiting for pod pod-subpath-test-dynamicpv-9kr9 to disappear
Jun 14 08:24:25.096: INFO: Pod pod-subpath-test-dynamicpv-9kr9 no longer exists
STEP: Deleting pod
Jun 14 08:24:25.097: INFO: Deleting pod "pod-subpath-test-dynamicpv-9kr9" in namespace "provisioning-9229"
... skipping 40 lines ...
Jun 14 08:24:47.984: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 355 lines ...
Jun 14 08:24:05.125: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-83514x6lf
STEP: creating a claim
Jun 14 08:24:05.286: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-frfb
STEP: Creating a pod to test subpath
Jun 14 08:24:05.772: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-frfb" in namespace "provisioning-8351" to be "Succeeded or Failed"
Jun 14 08:24:05.933: INFO: Pod "pod-subpath-test-dynamicpv-frfb": Phase="Pending", Reason="", readiness=false. Elapsed: 160.721977ms
Jun 14 08:24:08.095: INFO: Pod "pod-subpath-test-dynamicpv-frfb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.323066631s
Jun 14 08:24:10.264: INFO: Pod "pod-subpath-test-dynamicpv-frfb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.49152953s
Jun 14 08:24:12.426: INFO: Pod "pod-subpath-test-dynamicpv-frfb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.653606794s
Jun 14 08:24:14.587: INFO: Pod "pod-subpath-test-dynamicpv-frfb": Phase="Pending", Reason="", readiness=false. Elapsed: 8.81483316s
Jun 14 08:24:16.749: INFO: Pod "pod-subpath-test-dynamicpv-frfb": Phase="Pending", Reason="", readiness=false. Elapsed: 10.976629403s
Jun 14 08:24:18.910: INFO: Pod "pod-subpath-test-dynamicpv-frfb": Phase="Pending", Reason="", readiness=false. Elapsed: 13.13805996s
Jun 14 08:24:21.071: INFO: Pod "pod-subpath-test-dynamicpv-frfb": Phase="Pending", Reason="", readiness=false. Elapsed: 15.299017154s
Jun 14 08:24:23.258: INFO: Pod "pod-subpath-test-dynamicpv-frfb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 17.485972212s
STEP: Saw pod success
Jun 14 08:24:23.258: INFO: Pod "pod-subpath-test-dynamicpv-frfb" satisfied condition "Succeeded or Failed"
Jun 14 08:24:23.419: INFO: Trying to get logs from node ip-172-20-60-197.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-frfb container test-container-subpath-dynamicpv-frfb: <nil>
STEP: delete the pod
Jun 14 08:24:23.783: INFO: Waiting for pod pod-subpath-test-dynamicpv-frfb to disappear
Jun 14 08:24:23.945: INFO: Pod pod-subpath-test-dynamicpv-frfb no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-frfb
Jun 14 08:24:23.946: INFO: Deleting pod "pod-subpath-test-dynamicpv-frfb" in namespace "provisioning-8351"
... skipping 30 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 14 08:24:33.304: 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.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 14 08:24:34.105: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 14 08:24:34.105: INFO: Creating resource for dynamic PV
Jun 14 08:24:34.105: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-4701swgf9
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 14 08:24:41.233: INFO: Deleting pod "pod-9941d892-587b-4e18-9526-3d9cdf73a9d0" in namespace "volumemode-4701"
Jun 14 08:24:41.396: INFO: Wait up to 5m0s for pod "pod-9941d892-587b-4e18-9526-3d9cdf73a9d0" to be fully deleted
STEP: Deleting pvc
Jun 14 08:24:52.037: INFO: Deleting PersistentVolumeClaim "aws7bp8c"
Jun 14 08:24:52.203: INFO: Waiting up to 5m0s for PersistentVolume pvc-69676888-1ece-4ac5-bafc-4e9dd9298d1f to get deleted
Jun 14 08:24:52.366: INFO: PersistentVolume pvc-69676888-1ece-4ac5-bafc-4e9dd9298d1f found and phase=Released (163.550095ms)
... skipping 10 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.zEGyQTPHP/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.zEGyQTPHP/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (block volmode)] volumeMode
    /tmp/kops.zEGyQTPHP/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.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
... skipping 50 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.zEGyQTPHP/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.zEGyQTPHP/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.zEGyQTPHP/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.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 179 lines ...
Jun 14 08:24:29.984: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-963-e2e-sc6w2zl
STEP: creating a claim
Jun 14 08:24:30.155: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-5w28
STEP: Creating a pod to test subpath
Jun 14 08:24:30.647: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-5w28" in namespace "provisioning-963" to be "Succeeded or Failed"
Jun 14 08:24:30.808: INFO: Pod "pod-subpath-test-dynamicpv-5w28": Phase="Pending", Reason="", readiness=false. Elapsed: 161.434607ms
Jun 14 08:24:32.970: INFO: Pod "pod-subpath-test-dynamicpv-5w28": Phase="Pending", Reason="", readiness=false. Elapsed: 2.323703365s
Jun 14 08:24:35.132: INFO: Pod "pod-subpath-test-dynamicpv-5w28": Phase="Pending", Reason="", readiness=false. Elapsed: 4.485672543s
Jun 14 08:24:37.295: INFO: Pod "pod-subpath-test-dynamicpv-5w28": Phase="Pending", Reason="", readiness=false. Elapsed: 6.64838652s
Jun 14 08:24:39.458: INFO: Pod "pod-subpath-test-dynamicpv-5w28": Phase="Pending", Reason="", readiness=false. Elapsed: 8.811523676s
Jun 14 08:24:41.621: INFO: Pod "pod-subpath-test-dynamicpv-5w28": Phase="Pending", Reason="", readiness=false. Elapsed: 10.974682674s
Jun 14 08:24:43.784: INFO: Pod "pod-subpath-test-dynamicpv-5w28": Phase="Succeeded", Reason="", readiness=false. Elapsed: 13.137336221s
STEP: Saw pod success
Jun 14 08:24:43.784: INFO: Pod "pod-subpath-test-dynamicpv-5w28" satisfied condition "Succeeded or Failed"
Jun 14 08:24:43.945: INFO: Trying to get logs from node ip-172-20-32-95.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-5w28 container test-container-subpath-dynamicpv-5w28: <nil>
STEP: delete the pod
Jun 14 08:24:44.281: INFO: Waiting for pod pod-subpath-test-dynamicpv-5w28 to disappear
Jun 14 08:24:44.442: INFO: Pod pod-subpath-test-dynamicpv-5w28 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-5w28
Jun 14 08:24:44.442: INFO: Deleting pod "pod-subpath-test-dynamicpv-5w28" in namespace "provisioning-963"
... skipping 259 lines ...
Jun 14 08:25:03.433: INFO: Waiting for pod aws-client to disappear
Jun 14 08:25:03.587: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 14 08:25:03.587: INFO: Deleting PersistentVolumeClaim "pvc-pl5s6"
Jun 14 08:25:03.742: INFO: Deleting PersistentVolume "aws-w4l5z"
Jun 14 08:25:04.205: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0981d9702dc495cea", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0981d9702dc495cea is currently attached to i-0d03fe0f2c0571cc7
	status code: 400, request id: 2f4d1e15-bbac-48cd-9663-8b368f1b6c0d
Jun 14 08:25:09.996: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-0981d9702dc495cea".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 14 08:25:09.996: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-9568" for this suite.
... skipping 163 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.zEGyQTPHP/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.zEGyQTPHP/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.zEGyQTPHP/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.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

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

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.zEGyQTPHP/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.zEGyQTPHP/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.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 12 lines ...
Jun 14 08:24:47.756: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-179d6r8n
STEP: creating a claim
Jun 14 08:24:47.912: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Jun 14 08:24:48.225: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 14 08:24:48.537: INFO: Error updating pvc awsk5tv6: PersistentVolumeClaim "awsk5tv6" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-179d6r8n",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun 14 08:25:19.161: INFO: Error updating pvc awsk5tv6: PersistentVolumeClaim "awsk5tv6" is invalid: spec: Forbidden: spec is 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.zEGyQTPHP/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.zEGyQTPHP/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.zEGyQTPHP/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.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 15 lines ...
Jun 14 08:25:21.076: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 54 lines ...
Jun 14 08:24:31.864: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-2376vbkws
STEP: creating a claim
Jun 14 08:24:32.031: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-l5b2
STEP: Creating a pod to test exec-volume-test
Jun 14 08:24:32.518: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-l5b2" in namespace "volume-2376" to be "Succeeded or Failed"
Jun 14 08:24:32.687: INFO: Pod "exec-volume-test-dynamicpv-l5b2": Phase="Pending", Reason="", readiness=false. Elapsed: 168.118038ms
Jun 14 08:24:34.847: INFO: Pod "exec-volume-test-dynamicpv-l5b2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.328864217s
Jun 14 08:24:37.009: INFO: Pod "exec-volume-test-dynamicpv-l5b2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.490500722s
Jun 14 08:24:39.169: INFO: Pod "exec-volume-test-dynamicpv-l5b2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.651008378s
Jun 14 08:24:41.330: INFO: Pod "exec-volume-test-dynamicpv-l5b2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.811670427s
Jun 14 08:24:43.491: INFO: Pod "exec-volume-test-dynamicpv-l5b2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.972545666s
... skipping 2 lines ...
Jun 14 08:24:49.975: INFO: Pod "exec-volume-test-dynamicpv-l5b2": Phase="Pending", Reason="", readiness=false. Elapsed: 17.45644577s
Jun 14 08:24:52.140: INFO: Pod "exec-volume-test-dynamicpv-l5b2": Phase="Pending", Reason="", readiness=false. Elapsed: 19.621101965s
Jun 14 08:24:54.304: INFO: Pod "exec-volume-test-dynamicpv-l5b2": Phase="Pending", Reason="", readiness=false. Elapsed: 21.78576498s
Jun 14 08:24:56.465: INFO: Pod "exec-volume-test-dynamicpv-l5b2": Phase="Pending", Reason="", readiness=false. Elapsed: 23.946634107s
Jun 14 08:24:58.627: INFO: Pod "exec-volume-test-dynamicpv-l5b2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.108569372s
STEP: Saw pod success
Jun 14 08:24:58.627: INFO: Pod "exec-volume-test-dynamicpv-l5b2" satisfied condition "Succeeded or Failed"
Jun 14 08:24:58.788: INFO: Trying to get logs from node ip-172-20-32-95.ap-northeast-2.compute.internal pod exec-volume-test-dynamicpv-l5b2 container exec-container-dynamicpv-l5b2: <nil>
STEP: delete the pod
Jun 14 08:24:59.116: INFO: Waiting for pod exec-volume-test-dynamicpv-l5b2 to disappear
Jun 14 08:24:59.276: INFO: Pod exec-volume-test-dynamicpv-l5b2 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-l5b2
Jun 14 08:24:59.276: INFO: Deleting pod "exec-volume-test-dynamicpv-l5b2" in namespace "volume-2376"
... skipping 198 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.zEGyQTPHP/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.zEGyQTPHP/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.zEGyQTPHP/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.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 61 lines ...
Jun 14 08:24:27.810: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2748-e2e-sc2mbp5
STEP: creating a claim
Jun 14 08:24:27.971: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-pd6k
STEP: Creating a pod to test subpath
Jun 14 08:24:28.451: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-pd6k" in namespace "provisioning-2748" to be "Succeeded or Failed"
Jun 14 08:24:28.610: INFO: Pod "pod-subpath-test-dynamicpv-pd6k": Phase="Pending", Reason="", readiness=false. Elapsed: 159.051716ms
Jun 14 08:24:30.773: INFO: Pod "pod-subpath-test-dynamicpv-pd6k": Phase="Pending", Reason="", readiness=false. Elapsed: 2.321671742s
Jun 14 08:24:32.933: INFO: Pod "pod-subpath-test-dynamicpv-pd6k": Phase="Pending", Reason="", readiness=false. Elapsed: 4.481682821s
Jun 14 08:24:35.093: INFO: Pod "pod-subpath-test-dynamicpv-pd6k": Phase="Pending", Reason="", readiness=false. Elapsed: 6.641505439s
Jun 14 08:24:37.253: INFO: Pod "pod-subpath-test-dynamicpv-pd6k": Phase="Pending", Reason="", readiness=false. Elapsed: 8.801785016s
Jun 14 08:24:39.413: INFO: Pod "pod-subpath-test-dynamicpv-pd6k": Phase="Pending", Reason="", readiness=false. Elapsed: 10.961356092s
Jun 14 08:24:41.574: INFO: Pod "pod-subpath-test-dynamicpv-pd6k": Phase="Pending", Reason="", readiness=false. Elapsed: 13.12255827s
Jun 14 08:24:43.734: INFO: Pod "pod-subpath-test-dynamicpv-pd6k": Phase="Pending", Reason="", readiness=false. Elapsed: 15.282870077s
Jun 14 08:24:45.896: INFO: Pod "pod-subpath-test-dynamicpv-pd6k": Phase="Pending", Reason="", readiness=false. Elapsed: 17.444375333s
Jun 14 08:24:48.056: INFO: Pod "pod-subpath-test-dynamicpv-pd6k": Phase="Pending", Reason="", readiness=false. Elapsed: 19.605068339s
Jun 14 08:24:50.220: INFO: Pod "pod-subpath-test-dynamicpv-pd6k": Phase="Pending", Reason="", readiness=false. Elapsed: 21.769072322s
Jun 14 08:24:52.380: INFO: Pod "pod-subpath-test-dynamicpv-pd6k": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.929209697s
STEP: Saw pod success
Jun 14 08:24:52.380: INFO: Pod "pod-subpath-test-dynamicpv-pd6k" satisfied condition "Succeeded or Failed"
Jun 14 08:24:52.539: INFO: Trying to get logs from node ip-172-20-60-197.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-pd6k container test-container-subpath-dynamicpv-pd6k: <nil>
STEP: delete the pod
Jun 14 08:24:52.865: INFO: Waiting for pod pod-subpath-test-dynamicpv-pd6k to disappear
Jun 14 08:24:53.025: INFO: Pod pod-subpath-test-dynamicpv-pd6k no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-pd6k
Jun 14 08:24:53.025: INFO: Deleting pod "pod-subpath-test-dynamicpv-pd6k" in namespace "provisioning-2748"
... skipping 84 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.zEGyQTPHP/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.zEGyQTPHP/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.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 21 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 14 08:24:50.620: 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.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun 14 08:24:51.407: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 14 08:24:51.407: INFO: Creating resource for dynamic PV
Jun 14 08:24:51.407: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2448mfqwm
STEP: creating a claim
Jun 14 08:24:51.564: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-sspf
STEP: Checking for subpath error in container status
Jun 14 08:25:16.375: INFO: Deleting pod "pod-subpath-test-dynamicpv-sspf" in namespace "provisioning-2448"
Jun 14 08:25:16.534: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-sspf" to be fully deleted
STEP: Deleting pod
Jun 14 08:25:22.851: INFO: Deleting pod "pod-subpath-test-dynamicpv-sspf" in namespace "provisioning-2448"
STEP: Deleting pvc
Jun 14 08:25:23.324: INFO: Deleting PersistentVolumeClaim "awsskzzg"
... skipping 12 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.zEGyQTPHP/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.zEGyQTPHP/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath directory is outside the volume [Slow][LinuxOnly]
      /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 123 lines ...
Jun 14 08:25:05.124: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8355-e2e-scdd9pl
STEP: creating a claim
Jun 14 08:25:05.287: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-gtdd
STEP: Creating a pod to test subpath
Jun 14 08:25:05.774: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-gtdd" in namespace "provisioning-8355" to be "Succeeded or Failed"
Jun 14 08:25:05.941: INFO: Pod "pod-subpath-test-dynamicpv-gtdd": Phase="Pending", Reason="", readiness=false. Elapsed: 166.661036ms
Jun 14 08:25:08.102: INFO: Pod "pod-subpath-test-dynamicpv-gtdd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.327406053s
Jun 14 08:25:10.265: INFO: Pod "pod-subpath-test-dynamicpv-gtdd": Phase="Pending", Reason="", readiness=false. Elapsed: 4.490078441s
Jun 14 08:25:12.426: INFO: Pod "pod-subpath-test-dynamicpv-gtdd": Phase="Pending", Reason="", readiness=false. Elapsed: 6.651579399s
Jun 14 08:25:14.588: INFO: Pod "pod-subpath-test-dynamicpv-gtdd": Phase="Pending", Reason="", readiness=false. Elapsed: 8.813343494s
Jun 14 08:25:16.750: INFO: Pod "pod-subpath-test-dynamicpv-gtdd": Phase="Pending", Reason="", readiness=false. Elapsed: 10.975461188s
Jun 14 08:25:18.913: INFO: Pod "pod-subpath-test-dynamicpv-gtdd": Phase="Pending", Reason="", readiness=false. Elapsed: 13.138702667s
Jun 14 08:25:21.076: INFO: Pod "pod-subpath-test-dynamicpv-gtdd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 15.301778485s
STEP: Saw pod success
Jun 14 08:25:21.076: INFO: Pod "pod-subpath-test-dynamicpv-gtdd" satisfied condition "Succeeded or Failed"
Jun 14 08:25:21.236: INFO: Trying to get logs from node ip-172-20-33-97.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-gtdd container test-container-volume-dynamicpv-gtdd: <nil>
STEP: delete the pod
Jun 14 08:25:21.569: INFO: Waiting for pod pod-subpath-test-dynamicpv-gtdd to disappear
Jun 14 08:25:21.729: INFO: Pod pod-subpath-test-dynamicpv-gtdd no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-gtdd
Jun 14 08:25:21.729: INFO: Deleting pod "pod-subpath-test-dynamicpv-gtdd" in namespace "provisioning-8355"
... skipping 36 lines ...
Jun 14 08:24:52.024: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9991rkbwg
STEP: creating a claim
Jun 14 08:24:52.187: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-wpgd
STEP: Creating a pod to test atomic-volume-subpath
Jun 14 08:24:52.677: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-wpgd" in namespace "provisioning-9991" to be "Succeeded or Failed"
Jun 14 08:24:52.837: INFO: Pod "pod-subpath-test-dynamicpv-wpgd": Phase="Pending", Reason="", readiness=false. Elapsed: 160.447056ms
Jun 14 08:24:54.998: INFO: Pod "pod-subpath-test-dynamicpv-wpgd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.321309403s
Jun 14 08:24:57.161: INFO: Pod "pod-subpath-test-dynamicpv-wpgd": Phase="Pending", Reason="", readiness=false. Elapsed: 4.483890078s
Jun 14 08:24:59.322: INFO: Pod "pod-subpath-test-dynamicpv-wpgd": Phase="Pending", Reason="", readiness=false. Elapsed: 6.644903957s
Jun 14 08:25:01.484: INFO: Pod "pod-subpath-test-dynamicpv-wpgd": Phase="Pending", Reason="", readiness=false. Elapsed: 8.807390254s
Jun 14 08:25:03.647: INFO: Pod "pod-subpath-test-dynamicpv-wpgd": Phase="Pending", Reason="", readiness=false. Elapsed: 10.969856269s
... skipping 6 lines ...
Jun 14 08:25:18.784: INFO: Pod "pod-subpath-test-dynamicpv-wpgd": Phase="Running", Reason="", readiness=true. Elapsed: 26.107158556s
Jun 14 08:25:20.945: INFO: Pod "pod-subpath-test-dynamicpv-wpgd": Phase="Running", Reason="", readiness=true. Elapsed: 28.268382044s
Jun 14 08:25:23.111: INFO: Pod "pod-subpath-test-dynamicpv-wpgd": Phase="Running", Reason="", readiness=true. Elapsed: 30.43394644s
Jun 14 08:25:25.277: INFO: Pod "pod-subpath-test-dynamicpv-wpgd": Phase="Running", Reason="", readiness=true. Elapsed: 32.600158559s
Jun 14 08:25:27.439: INFO: Pod "pod-subpath-test-dynamicpv-wpgd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.761977427s
STEP: Saw pod success
Jun 14 08:25:27.439: INFO: Pod "pod-subpath-test-dynamicpv-wpgd" satisfied condition "Succeeded or Failed"
Jun 14 08:25:27.600: INFO: Trying to get logs from node ip-172-20-60-197.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-wpgd container test-container-subpath-dynamicpv-wpgd: <nil>
STEP: delete the pod
Jun 14 08:25:27.928: INFO: Waiting for pod pod-subpath-test-dynamicpv-wpgd to disappear
Jun 14 08:25:28.089: INFO: Pod pod-subpath-test-dynamicpv-wpgd no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-wpgd
Jun 14 08:25:28.089: INFO: Deleting pod "pod-subpath-test-dynamicpv-wpgd" in namespace "provisioning-9991"
... skipping 37 lines ...
Jun 14 08:25:07.367: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-30444dmkr
STEP: creating a claim
Jun 14 08:25:07.529: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-r5cf
STEP: Creating a pod to test subpath
Jun 14 08:25:08.016: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-r5cf" in namespace "provisioning-3044" to be "Succeeded or Failed"
Jun 14 08:25:08.178: INFO: Pod "pod-subpath-test-dynamicpv-r5cf": Phase="Pending", Reason="", readiness=false. Elapsed: 161.513696ms
Jun 14 08:25:10.340: INFO: Pod "pod-subpath-test-dynamicpv-r5cf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.323448964s
Jun 14 08:25:12.502: INFO: Pod "pod-subpath-test-dynamicpv-r5cf": Phase="Pending", Reason="", readiness=false. Elapsed: 4.485897992s
Jun 14 08:25:14.665: INFO: Pod "pod-subpath-test-dynamicpv-r5cf": Phase="Pending", Reason="", readiness=false. Elapsed: 6.648899317s
Jun 14 08:25:16.828: INFO: Pod "pod-subpath-test-dynamicpv-r5cf": Phase="Pending", Reason="", readiness=false. Elapsed: 8.811963121s
Jun 14 08:25:18.991: INFO: Pod "pod-subpath-test-dynamicpv-r5cf": Phase="Pending", Reason="", readiness=false. Elapsed: 10.974794571s
Jun 14 08:25:21.153: INFO: Pod "pod-subpath-test-dynamicpv-r5cf": Phase="Pending", Reason="", readiness=false. Elapsed: 13.136951878s
Jun 14 08:25:23.317: INFO: Pod "pod-subpath-test-dynamicpv-r5cf": Phase="Succeeded", Reason="", readiness=false. Elapsed: 15.300469733s
STEP: Saw pod success
Jun 14 08:25:23.317: INFO: Pod "pod-subpath-test-dynamicpv-r5cf" satisfied condition "Succeeded or Failed"
Jun 14 08:25:23.482: INFO: Trying to get logs from node ip-172-20-48-27.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-r5cf container test-container-subpath-dynamicpv-r5cf: <nil>
STEP: delete the pod
Jun 14 08:25:23.814: INFO: Waiting for pod pod-subpath-test-dynamicpv-r5cf to disappear
Jun 14 08:25:23.976: INFO: Pod pod-subpath-test-dynamicpv-r5cf no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-r5cf
Jun 14 08:25:23.976: INFO: Deleting pod "pod-subpath-test-dynamicpv-r5cf" in namespace "provisioning-3044"
... skipping 62 lines ...
STEP: Deleting pod hostexec-ip-172-20-32-95.ap-northeast-2.compute.internal-zmv6f in namespace volumemode-2940
Jun 14 08:25:24.914: INFO: Deleting pod "pod-684e765e-d569-41d8-9f25-5d6b2f2224ad" in namespace "volumemode-2940"
Jun 14 08:25:25.078: INFO: Wait up to 5m0s for pod "pod-684e765e-d569-41d8-9f25-5d6b2f2224ad" to be fully deleted
STEP: Deleting pv and pvc
Jun 14 08:25:37.398: INFO: Deleting PersistentVolumeClaim "pvc-lf9fk"
Jun 14 08:25:37.558: INFO: Deleting PersistentVolume "aws-fp9wd"
Jun 14 08:25:38.025: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-037b4bc01650d569d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-037b4bc01650d569d is currently attached to i-0ad576b69e7030d31
	status code: 400, request id: 7882292f-28e4-4070-aa94-8e36016254f2
Jun 14 08:25:43.864: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-037b4bc01650d569d".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 14 08:25:43.864: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-2940" for this suite.
... skipping 119 lines ...
Jun 14 08:25:11.090: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-9458mnrdl
STEP: creating a claim
Jun 14 08:25:11.245: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-cqxs
STEP: Creating a pod to test exec-volume-test
Jun 14 08:25:11.713: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-cqxs" in namespace "volume-9458" to be "Succeeded or Failed"
Jun 14 08:25:11.867: INFO: Pod "exec-volume-test-dynamicpv-cqxs": Phase="Pending", Reason="", readiness=false. Elapsed: 154.536327ms
Jun 14 08:25:14.022: INFO: Pod "exec-volume-test-dynamicpv-cqxs": Phase="Pending", Reason="", readiness=false. Elapsed: 2.309243031s
Jun 14 08:25:16.178: INFO: Pod "exec-volume-test-dynamicpv-cqxs": Phase="Pending", Reason="", readiness=false. Elapsed: 4.465275757s
Jun 14 08:25:18.334: INFO: Pod "exec-volume-test-dynamicpv-cqxs": Phase="Pending", Reason="", readiness=false. Elapsed: 6.620590744s
Jun 14 08:25:20.489: INFO: Pod "exec-volume-test-dynamicpv-cqxs": Phase="Pending", Reason="", readiness=false. Elapsed: 8.776208302s
Jun 14 08:25:22.645: INFO: Pod "exec-volume-test-dynamicpv-cqxs": Phase="Pending", Reason="", readiness=false. Elapsed: 10.931976558s
... skipping 2 lines ...
Jun 14 08:25:29.112: INFO: Pod "exec-volume-test-dynamicpv-cqxs": Phase="Pending", Reason="", readiness=false. Elapsed: 17.398812937s
Jun 14 08:25:31.267: INFO: Pod "exec-volume-test-dynamicpv-cqxs": Phase="Pending", Reason="", readiness=false. Elapsed: 19.554477723s
Jun 14 08:25:33.423: INFO: Pod "exec-volume-test-dynamicpv-cqxs": Phase="Pending", Reason="", readiness=false. Elapsed: 21.71015937s
Jun 14 08:25:35.578: INFO: Pod "exec-volume-test-dynamicpv-cqxs": Phase="Pending", Reason="", readiness=false. Elapsed: 23.864937375s
Jun 14 08:25:37.732: INFO: Pod "exec-volume-test-dynamicpv-cqxs": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.019139993s
STEP: Saw pod success
Jun 14 08:25:37.732: INFO: Pod "exec-volume-test-dynamicpv-cqxs" satisfied condition "Succeeded or Failed"
Jun 14 08:25:37.887: INFO: Trying to get logs from node ip-172-20-60-197.ap-northeast-2.compute.internal pod exec-volume-test-dynamicpv-cqxs container exec-container-dynamicpv-cqxs: <nil>
STEP: delete the pod
Jun 14 08:25:38.203: INFO: Waiting for pod exec-volume-test-dynamicpv-cqxs to disappear
Jun 14 08:25:38.358: INFO: Pod exec-volume-test-dynamicpv-cqxs no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-cqxs
Jun 14 08:25:38.358: INFO: Deleting pod "exec-volume-test-dynamicpv-cqxs" in namespace "volume-9458"
... skipping 201 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 14 08:25:25.102: 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.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun 14 08:25:25.910: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 14 08:25:25.910: INFO: Creating resource for dynamic PV
Jun 14 08:25:25.910: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2c4jtg
STEP: creating a claim
Jun 14 08:25:26.071: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-6ck8
STEP: Checking for subpath error in container status
Jun 14 08:25:40.898: INFO: Deleting pod "pod-subpath-test-dynamicpv-6ck8" in namespace "provisioning-2"
Jun 14 08:25:41.063: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-6ck8" to be fully deleted
STEP: Deleting pod
Jun 14 08:25:53.389: INFO: Deleting pod "pod-subpath-test-dynamicpv-6ck8" in namespace "provisioning-2"
STEP: Deleting pvc
Jun 14 08:25:53.903: INFO: Deleting PersistentVolumeClaim "aws6wc7r"
... skipping 10 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.zEGyQTPHP/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.zEGyQTPHP/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.zEGyQTPHP/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.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] volumeIO
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 14 08:25:54.715: INFO: Driver "ebs.csi.aws.com" does not support volume type "InlineVolume" - skipping
[AfterEach] [Testpattern: Inline-volume (default fs)] volumeIO
... skipping 26 lines ...
Jun 14 08:25:12.325: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4581-e2e-sc67hjh
STEP: creating a claim
Jun 14 08:25:12.483: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-d2tw
STEP: Creating a pod to test atomic-volume-subpath
Jun 14 08:25:12.960: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-d2tw" in namespace "provisioning-4581" to be "Succeeded or Failed"
Jun 14 08:25:13.118: INFO: Pod "pod-subpath-test-dynamicpv-d2tw": Phase="Pending", Reason="", readiness=false. Elapsed: 157.608917ms
Jun 14 08:25:15.275: INFO: Pod "pod-subpath-test-dynamicpv-d2tw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.315049772s
Jun 14 08:25:17.434: INFO: Pod "pod-subpath-test-dynamicpv-d2tw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.473624867s
Jun 14 08:25:19.592: INFO: Pod "pod-subpath-test-dynamicpv-d2tw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.631978555s
Jun 14 08:25:21.751: INFO: Pod "pod-subpath-test-dynamicpv-d2tw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.790634321s
Jun 14 08:25:23.909: INFO: Pod "pod-subpath-test-dynamicpv-d2tw": Phase="Pending", Reason="", readiness=false. Elapsed: 10.948267418s
... skipping 5 lines ...
Jun 14 08:25:36.871: INFO: Pod "pod-subpath-test-dynamicpv-d2tw": Phase="Running", Reason="", readiness=true. Elapsed: 23.910732893s
Jun 14 08:25:39.029: INFO: Pod "pod-subpath-test-dynamicpv-d2tw": Phase="Running", Reason="", readiness=true. Elapsed: 26.069061601s
Jun 14 08:25:41.188: INFO: Pod "pod-subpath-test-dynamicpv-d2tw": Phase="Running", Reason="", readiness=true. Elapsed: 28.22755285s
Jun 14 08:25:43.346: INFO: Pod "pod-subpath-test-dynamicpv-d2tw": Phase="Running", Reason="", readiness=true. Elapsed: 30.385930678s
Jun 14 08:25:45.510: INFO: Pod "pod-subpath-test-dynamicpv-d2tw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 32.549811226s
STEP: Saw pod success
Jun 14 08:25:45.510: INFO: Pod "pod-subpath-test-dynamicpv-d2tw" satisfied condition "Succeeded or Failed"
Jun 14 08:25:45.686: INFO: Trying to get logs from node ip-172-20-48-27.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-d2tw container test-container-subpath-dynamicpv-d2tw: <nil>
STEP: delete the pod
Jun 14 08:25:46.019: INFO: Waiting for pod pod-subpath-test-dynamicpv-d2tw to disappear
Jun 14 08:25:46.175: INFO: Pod pod-subpath-test-dynamicpv-d2tw no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-d2tw
Jun 14 08:25:46.175: INFO: Deleting pod "pod-subpath-test-dynamicpv-d2tw" in namespace "provisioning-4581"
... skipping 32 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.zEGyQTPHP/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.zEGyQTPHP/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.zEGyQTPHP/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.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Distro debian doesn't support ntfs -- skipping

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.zEGyQTPHP/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.zEGyQTPHP/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.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 10 lines ...
Jun 14 08:24:05.879: INFO: Creating resource for dynamic PV
Jun 14 08:24:05.880: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-6091-e2e-scknpn4
STEP: creating a claim
Jun 14 08:24:06.035: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 14 08:24:06.507: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-pwrwc" in namespace "snapshotting-6091" to be "Succeeded or Failed"
Jun 14 08:24:06.662: INFO: Pod "pvc-snapshottable-tester-pwrwc": Phase="Pending", Reason="", readiness=false. Elapsed: 155.064926ms
Jun 14 08:24:08.818: INFO: Pod "pvc-snapshottable-tester-pwrwc": Phase="Pending", Reason="", readiness=false. Elapsed: 2.310822124s
Jun 14 08:24:10.975: INFO: Pod "pvc-snapshottable-tester-pwrwc": Phase="Pending", Reason="", readiness=false. Elapsed: 4.467438709s
Jun 14 08:24:13.131: INFO: Pod "pvc-snapshottable-tester-pwrwc": Phase="Pending", Reason="", readiness=false. Elapsed: 6.624009934s
Jun 14 08:24:15.287: INFO: Pod "pvc-snapshottable-tester-pwrwc": Phase="Pending", Reason="", readiness=false. Elapsed: 8.779907388s
Jun 14 08:24:17.443: INFO: Pod "pvc-snapshottable-tester-pwrwc": Phase="Pending", Reason="", readiness=false. Elapsed: 10.935698895s
Jun 14 08:24:19.604: INFO: Pod "pvc-snapshottable-tester-pwrwc": Phase="Pending", Reason="", readiness=false. Elapsed: 13.09629724s
Jun 14 08:24:21.760: INFO: Pod "pvc-snapshottable-tester-pwrwc": Phase="Pending", Reason="", readiness=false. Elapsed: 15.252373916s
Jun 14 08:24:23.917: INFO: Pod "pvc-snapshottable-tester-pwrwc": Phase="Pending", Reason="", readiness=false. Elapsed: 17.409120535s
Jun 14 08:24:26.073: INFO: Pod "pvc-snapshottable-tester-pwrwc": Phase="Pending", Reason="", readiness=false. Elapsed: 19.565341751s
Jun 14 08:24:28.228: INFO: Pod "pvc-snapshottable-tester-pwrwc": Phase="Pending", Reason="", readiness=false. Elapsed: 21.721064858s
Jun 14 08:24:30.384: INFO: Pod "pvc-snapshottable-tester-pwrwc": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.877089464s
STEP: Saw pod success
Jun 14 08:24:30.385: INFO: Pod "pvc-snapshottable-tester-pwrwc" satisfied condition "Succeeded or Failed"
Jun 14 08:24:30.700: INFO: Pod pvc-snapshottable-tester-pwrwc has the following logs: 
Jun 14 08:24:30.700: INFO: Deleting pod "pvc-snapshottable-tester-pwrwc" in namespace "snapshotting-6091"
Jun 14 08:24:30.860: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-pwrwc" to be fully deleted
Jun 14 08:24:31.015: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comvmqd6] to have phase Bound
Jun 14 08:24:31.171: INFO: PersistentVolumeClaim ebs.csi.aws.comvmqd6 found and phase=Bound (155.691387ms)
STEP: [init] checking the claim
... skipping 17 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.zEGyQTPHP/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 14 08:24:47.995: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-p2c2m" in namespace "snapshotting-6091" to be "Succeeded or Failed"
Jun 14 08:24:48.150: INFO: Pod "pvc-snapshottable-data-tester-p2c2m": Phase="Pending", Reason="", readiness=false. Elapsed: 155.452446ms
Jun 14 08:24:50.311: INFO: Pod "pvc-snapshottable-data-tester-p2c2m": Phase="Pending", Reason="", readiness=false. Elapsed: 2.316292051s
Jun 14 08:24:52.466: INFO: Pod "pvc-snapshottable-data-tester-p2c2m": Phase="Pending", Reason="", readiness=false. Elapsed: 4.471873526s
Jun 14 08:24:54.624: INFO: Pod "pvc-snapshottable-data-tester-p2c2m": Phase="Pending", Reason="", readiness=false. Elapsed: 6.629587383s
Jun 14 08:24:56.780: INFO: Pod "pvc-snapshottable-data-tester-p2c2m": Phase="Pending", Reason="", readiness=false. Elapsed: 8.785176119s
Jun 14 08:24:58.939: INFO: Pod "pvc-snapshottable-data-tester-p2c2m": Phase="Pending", Reason="", readiness=false. Elapsed: 10.943973524s
Jun 14 08:25:01.096: INFO: Pod "pvc-snapshottable-data-tester-p2c2m": Phase="Pending", Reason="", readiness=false. Elapsed: 13.101331974s
Jun 14 08:25:03.253: INFO: Pod "pvc-snapshottable-data-tester-p2c2m": Phase="Pending", Reason="", readiness=false. Elapsed: 15.258771499s
Jun 14 08:25:05.410: INFO: Pod "pvc-snapshottable-data-tester-p2c2m": Phase="Succeeded", Reason="", readiness=false. Elapsed: 17.415021385s
STEP: Saw pod success
Jun 14 08:25:05.410: INFO: Pod "pvc-snapshottable-data-tester-p2c2m" satisfied condition "Succeeded or Failed"
Jun 14 08:25:05.722: INFO: Pod pvc-snapshottable-data-tester-p2c2m has the following logs: 
Jun 14 08:25:05.722: INFO: Deleting pod "pvc-snapshottable-data-tester-p2c2m" in namespace "snapshotting-6091"
Jun 14 08:25:05.888: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-p2c2m" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 14 08:25:16.675: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-6091 exec restored-pvc-tester-55lqk --namespace=snapshotting-6091 -- cat /mnt/test/data'
... skipping 469 lines ...
Jun 14 08:24:50.993: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-4608-e2e-sczhkg2      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-4608    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-4608-e2e-sczhkg2,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-4608    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-4608-e2e-sczhkg2,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-4608    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-4608-e2e-sczhkg2,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-4608-e2e-sczhkg2    9953170e-2cba-46fc-a5be-373ad93a84b5 7425 0 2021-06-14 08:24:51 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-14 08:24:51 +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-c8jwg pvc- provisioning-4608  aff593bc-39c5-4b08-b0e2-75dc20d5a3bb 7435 0 2021-06-14 08:24:51 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-14 08:24:51 +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-4608-e2e-sczhkg2,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-3e5e3e47-7f41-4c59-a8dd-f4e1907d10b0 in namespace provisioning-4608
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun 14 08:25:06.776: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-8v5ck" in namespace "provisioning-4608" to be "Succeeded or Failed"
Jun 14 08:25:06.936: INFO: Pod "pvc-volume-tester-writer-8v5ck": Phase="Pending", Reason="", readiness=false. Elapsed: 160.553206ms
Jun 14 08:25:09.098: INFO: Pod "pvc-volume-tester-writer-8v5ck": Phase="Pending", Reason="", readiness=false. Elapsed: 2.322172832s
Jun 14 08:25:11.259: INFO: Pod "pvc-volume-tester-writer-8v5ck": Phase="Pending", Reason="", readiness=false. Elapsed: 4.483524082s
Jun 14 08:25:13.431: INFO: Pod "pvc-volume-tester-writer-8v5ck": Phase="Pending", Reason="", readiness=false. Elapsed: 6.655813158s
Jun 14 08:25:15.595: INFO: Pod "pvc-volume-tester-writer-8v5ck": Phase="Pending", Reason="", readiness=false. Elapsed: 8.819260822s
Jun 14 08:25:17.755: INFO: Pod "pvc-volume-tester-writer-8v5ck": Phase="Pending", Reason="", readiness=false. Elapsed: 10.979730198s
... skipping 6 lines ...
Jun 14 08:25:32.891: INFO: Pod "pvc-volume-tester-writer-8v5ck": Phase="Pending", Reason="", readiness=false. Elapsed: 26.115513383s
Jun 14 08:25:35.052: INFO: Pod "pvc-volume-tester-writer-8v5ck": Phase="Pending", Reason="", readiness=false. Elapsed: 28.275869547s
Jun 14 08:25:37.213: INFO: Pod "pvc-volume-tester-writer-8v5ck": Phase="Pending", Reason="", readiness=false. Elapsed: 30.437218485s
Jun 14 08:25:39.373: INFO: Pod "pvc-volume-tester-writer-8v5ck": Phase="Pending", Reason="", readiness=false. Elapsed: 32.597250603s
Jun 14 08:25:41.535: INFO: Pod "pvc-volume-tester-writer-8v5ck": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.759029871s
STEP: Saw pod success
Jun 14 08:25:41.535: INFO: Pod "pvc-volume-tester-writer-8v5ck" satisfied condition "Succeeded or Failed"
Jun 14 08:25:41.856: INFO: Pod pvc-volume-tester-writer-8v5ck has the following logs: 
Jun 14 08:25:41.856: INFO: Deleting pod "pvc-volume-tester-writer-8v5ck" in namespace "provisioning-4608"
Jun 14 08:25:42.025: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-8v5ck" to be fully deleted
STEP: checking the created volume has the correct mount options, is readable and retains data on the same node "ip-172-20-32-95.ap-northeast-2.compute.internal"
Jun 14 08:25:42.673: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-ffmhr" in namespace "provisioning-4608" to be "Succeeded or Failed"
Jun 14 08:25:42.832: INFO: Pod "pvc-volume-tester-reader-ffmhr": Phase="Pending", Reason="", readiness=false. Elapsed: 159.637475ms
Jun 14 08:25:45.013: INFO: Pod "pvc-volume-tester-reader-ffmhr": Phase="Pending", Reason="", readiness=false. Elapsed: 2.340065544s
Jun 14 08:25:47.173: INFO: Pod "pvc-volume-tester-reader-ffmhr": Phase="Pending", Reason="", readiness=false. Elapsed: 4.50055595s
Jun 14 08:25:49.335: INFO: Pod "pvc-volume-tester-reader-ffmhr": Phase="Pending", Reason="", readiness=false. Elapsed: 6.662458048s
Jun 14 08:25:51.496: INFO: Pod "pvc-volume-tester-reader-ffmhr": Phase="Pending", Reason="", readiness=false. Elapsed: 8.823330894s
Jun 14 08:25:53.659: INFO: Pod "pvc-volume-tester-reader-ffmhr": Phase="Pending", Reason="", readiness=false. Elapsed: 10.986649503s
Jun 14 08:25:55.819: INFO: Pod "pvc-volume-tester-reader-ffmhr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 13.14679569s
STEP: Saw pod success
Jun 14 08:25:55.819: INFO: Pod "pvc-volume-tester-reader-ffmhr" satisfied condition "Succeeded or Failed"
Jun 14 08:25:56.140: INFO: Pod pvc-volume-tester-reader-ffmhr has the following logs: hello world

Jun 14 08:25:56.140: INFO: Deleting pod "pvc-volume-tester-reader-ffmhr" in namespace "provisioning-4608"
Jun 14 08:25:56.306: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-ffmhr" to be fully deleted
Jun 14 08:25:56.466: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-c8jwg] to have phase Bound
Jun 14 08:25:56.626: INFO: PersistentVolumeClaim pvc-c8jwg found and phase=Bound (159.769195ms)
... skipping 60 lines ...

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.zEGyQTPHP/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.zEGyQTPHP/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.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 31 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 14 08:25:35.558: 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.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun 14 08:25:36.353: INFO: Creating resource for dynamic PV
Jun 14 08:25:36.353: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2393-e2e-scfj6kn
STEP: creating a claim
Jun 14 08:25:36.513: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-7wpb
STEP: Checking for subpath error in container status
Jun 14 08:25:57.308: INFO: Deleting pod "pod-subpath-test-dynamicpv-7wpb" in namespace "provisioning-2393"
Jun 14 08:25:57.469: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-7wpb" to be fully deleted
STEP: Deleting pod
Jun 14 08:26:05.784: INFO: Deleting pod "pod-subpath-test-dynamicpv-7wpb" in namespace "provisioning-2393"
STEP: Deleting pvc
Jun 14 08:26:06.259: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comtcwp6"
... skipping 15 lines ...

• [SLOW TEST:67.609 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath file is outside the volume [Slow][LinuxOnly]
    /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 14 08:26:43.171: INFO: Distro debian doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning
... skipping 86 lines ...
Jun 14 08:26:38.999: INFO: Pod aws-client still exists
Jun 14 08:26:40.840: INFO: Waiting for pod aws-client to disappear
Jun 14 08:26:41.000: INFO: Pod aws-client still exists
Jun 14 08:26:42.840: INFO: Waiting for pod aws-client to disappear
Jun 14 08:26:42.999: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun 14 08:26:43.840: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-01a0e422b9fe1fa6c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01a0e422b9fe1fa6c is currently attached to i-0d03fe0f2c0571cc7
	status code: 400, request id: f4fb1b8f-6b22-4113-be7b-ae3effb6d7ca
Jun 14 08:26:49.670: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-01a0e422b9fe1fa6c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01a0e422b9fe1fa6c is currently attached to i-0d03fe0f2c0571cc7
	status code: 400, request id: 8f593c63-29b1-41a8-bcc3-f42668a09420
Jun 14 08:26:55.497: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-01a0e422b9fe1fa6c".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 14 08:26:55.497: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-425" for this suite.
... skipping 221 lines ...
Jun 14 08:26:03.873: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-8664-e2e-scn5qjk
STEP: creating a claim
Jun 14 08:26:04.030: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-qxwk
STEP: Creating a pod to test exec-volume-test
Jun 14 08:26:04.506: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-qxwk" in namespace "volume-8664" to be "Succeeded or Failed"
Jun 14 08:26:04.663: INFO: Pod "exec-volume-test-dynamicpv-qxwk": Phase="Pending", Reason="", readiness=false. Elapsed: 157.066888ms
Jun 14 08:26:06.822: INFO: Pod "exec-volume-test-dynamicpv-qxwk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.315871945s
Jun 14 08:26:08.981: INFO: Pod "exec-volume-test-dynamicpv-qxwk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.474716866s
Jun 14 08:26:11.138: INFO: Pod "exec-volume-test-dynamicpv-qxwk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.632011105s
Jun 14 08:26:13.297: INFO: Pod "exec-volume-test-dynamicpv-qxwk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.790969381s
Jun 14 08:26:15.455: INFO: Pod "exec-volume-test-dynamicpv-qxwk": Phase="Pending", Reason="", readiness=false. Elapsed: 10.948636617s
Jun 14 08:26:17.614: INFO: Pod "exec-volume-test-dynamicpv-qxwk": Phase="Pending", Reason="", readiness=false. Elapsed: 13.107696774s
Jun 14 08:26:19.773: INFO: Pod "exec-volume-test-dynamicpv-qxwk": Phase="Pending", Reason="", readiness=false. Elapsed: 15.266437723s
Jun 14 08:26:21.930: INFO: Pod "exec-volume-test-dynamicpv-qxwk": Phase="Pending", Reason="", readiness=false. Elapsed: 17.423860559s
Jun 14 08:26:24.091: INFO: Pod "exec-volume-test-dynamicpv-qxwk": Phase="Pending", Reason="", readiness=false. Elapsed: 19.584604247s
Jun 14 08:26:26.249: INFO: Pod "exec-volume-test-dynamicpv-qxwk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.742835762s
STEP: Saw pod success
Jun 14 08:26:26.249: INFO: Pod "exec-volume-test-dynamicpv-qxwk" satisfied condition "Succeeded or Failed"
Jun 14 08:26:26.406: INFO: Trying to get logs from node ip-172-20-32-95.ap-northeast-2.compute.internal pod exec-volume-test-dynamicpv-qxwk container exec-container-dynamicpv-qxwk: <nil>
STEP: delete the pod
Jun 14 08:26:26.725: INFO: Waiting for pod exec-volume-test-dynamicpv-qxwk to disappear
Jun 14 08:26:26.882: INFO: Pod exec-volume-test-dynamicpv-qxwk no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-qxwk
Jun 14 08:26:26.882: INFO: Deleting pod "exec-volume-test-dynamicpv-qxwk" in namespace "volume-8664"
... skipping 133 lines ...
Jun 14 08:26:47.848: INFO: Pod aws-client still exists
Jun 14 08:26:49.687: INFO: Waiting for pod aws-client to disappear
Jun 14 08:26:49.848: INFO: Pod aws-client still exists
Jun 14 08:26:51.687: INFO: Waiting for pod aws-client to disappear
Jun 14 08:26:51.848: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun 14 08:26:52.609: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-050281b992c36a1f4", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-050281b992c36a1f4 is currently attached to i-03448625fa1301d2f
	status code: 400, request id: d3c2c70c-ed1a-49ed-9afe-aba828a11f74
Jun 14 08:26:58.411: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-050281b992c36a1f4", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-050281b992c36a1f4 is currently attached to i-03448625fa1301d2f
	status code: 400, request id: cca8bbd5-2b1c-4c77-ad4e-842d4b5472a4
Jun 14 08:27:04.276: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-050281b992c36a1f4".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 14 08:27:04.276: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-6676" for this suite.
... skipping 233 lines ...
Jun 14 08:27:06.081: INFO: Pod aws-client still exists
Jun 14 08:27:07.920: INFO: Waiting for pod aws-client to disappear
Jun 14 08:27:08.081: INFO: Pod aws-client still exists
Jun 14 08:27:09.920: INFO: Waiting for pod aws-client to disappear
Jun 14 08:27:10.080: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun 14 08:27:10.863: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-08cf020df1d3f82a5", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08cf020df1d3f82a5 is currently attached to i-0bec054b8ebd8f3d8
	status code: 400, request id: 6b07c802-3619-4330-a9d5-7d80c2f23605
Jun 14 08:27:16.695: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-08cf020df1d3f82a5".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 14 08:27:16.695: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-5903" for this suite.
... skipping 270 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.zEGyQTPHP/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.zEGyQTPHP/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.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 12 lines ...
Jun 14 08:26:32.759: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-86zvr77
STEP: creating a claim
Jun 14 08:26:32.917: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-596h
STEP: Creating a pod to test exec-volume-test
Jun 14 08:26:33.397: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-596h" in namespace "volume-86" to be "Succeeded or Failed"
Jun 14 08:26:33.555: INFO: Pod "exec-volume-test-dynamicpv-596h": Phase="Pending", Reason="", readiness=false. Elapsed: 158.027557ms
Jun 14 08:26:35.728: INFO: Pod "exec-volume-test-dynamicpv-596h": Phase="Pending", Reason="", readiness=false. Elapsed: 2.331218837s
Jun 14 08:26:37.887: INFO: Pod "exec-volume-test-dynamicpv-596h": Phase="Pending", Reason="", readiness=false. Elapsed: 4.490239511s
Jun 14 08:26:40.045: INFO: Pod "exec-volume-test-dynamicpv-596h": Phase="Pending", Reason="", readiness=false. Elapsed: 6.648794579s
Jun 14 08:26:42.204: INFO: Pod "exec-volume-test-dynamicpv-596h": Phase="Pending", Reason="", readiness=false. Elapsed: 8.807792026s
Jun 14 08:26:44.363: INFO: Pod "exec-volume-test-dynamicpv-596h": Phase="Pending", Reason="", readiness=false. Elapsed: 10.966004812s
Jun 14 08:26:46.522: INFO: Pod "exec-volume-test-dynamicpv-596h": Phase="Pending", Reason="", readiness=false. Elapsed: 13.125623161s
Jun 14 08:26:48.682: INFO: Pod "exec-volume-test-dynamicpv-596h": Phase="Pending", Reason="", readiness=false. Elapsed: 15.285002794s
Jun 14 08:26:50.841: INFO: Pod "exec-volume-test-dynamicpv-596h": Phase="Pending", Reason="", readiness=false. Elapsed: 17.44407864s
Jun 14 08:26:52.999: INFO: Pod "exec-volume-test-dynamicpv-596h": Phase="Pending", Reason="", readiness=false. Elapsed: 19.602518787s
Jun 14 08:26:55.158: INFO: Pod "exec-volume-test-dynamicpv-596h": Phase="Pending", Reason="", readiness=false. Elapsed: 21.760927058s
Jun 14 08:26:57.315: INFO: Pod "exec-volume-test-dynamicpv-596h": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.918834907s
STEP: Saw pod success
Jun 14 08:26:57.316: INFO: Pod "exec-volume-test-dynamicpv-596h" satisfied condition "Succeeded or Failed"
Jun 14 08:26:57.473: INFO: Trying to get logs from node ip-172-20-32-95.ap-northeast-2.compute.internal pod exec-volume-test-dynamicpv-596h container exec-container-dynamicpv-596h: <nil>
STEP: delete the pod
Jun 14 08:26:57.797: INFO: Waiting for pod exec-volume-test-dynamicpv-596h to disappear
Jun 14 08:26:57.954: INFO: Pod exec-volume-test-dynamicpv-596h no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-596h
Jun 14 08:26:57.954: INFO: Deleting pod "exec-volume-test-dynamicpv-596h" in namespace "volume-86"
... skipping 321 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 14 08:26:59.036: 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.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 14 08:26:59.813: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 14 08:26:59.813: INFO: Creating resource for dynamic PV
Jun 14 08:26:59.813: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-3195lqvc2
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 14 08:27:04.906: INFO: Deleting pod "pod-9fb77c7c-1975-46fe-bbe4-6feb6107a341" in namespace "volumemode-3195"
Jun 14 08:27:05.071: INFO: Wait up to 5m0s for pod "pod-9fb77c7c-1975-46fe-bbe4-6feb6107a341" to be fully deleted
STEP: Deleting pvc
Jun 14 08:27:11.692: INFO: Deleting PersistentVolumeClaim "aws2xvf9"
Jun 14 08:27:11.848: INFO: Waiting up to 5m0s for PersistentVolume pvc-20e4d464-99f9-4084-a1ae-4404e5293361 to get deleted
Jun 14 08:27:12.003: INFO: PersistentVolume pvc-20e4d464-99f9-4084-a1ae-4404e5293361 found and phase=Released (155.038057ms)
... skipping 11 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.zEGyQTPHP/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.zEGyQTPHP/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
    /tmp/kops.zEGyQTPHP/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.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
S
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
... skipping 57 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 14 08:26:38.668: 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.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 14 08:26:39.480: INFO: Creating resource for dynamic PV
Jun 14 08:26:39.480: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-5879-e2e-sc6mx6t
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 14 08:26:46.627: INFO: Deleting pod "pod-acd28d34-9c63-4ed4-a9b4-37b791f44686" in namespace "volumemode-5879"
Jun 14 08:26:46.792: INFO: Wait up to 5m0s for pod "pod-acd28d34-9c63-4ed4-a9b4-37b791f44686" to be fully deleted
STEP: Deleting pvc
Jun 14 08:26:51.440: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comgbsws"
Jun 14 08:26:51.604: INFO: Waiting up to 5m0s for PersistentVolume pvc-8e471795-a85f-4d70-b6f7-cdadb3a065c9 to get deleted
Jun 14 08:26:51.766: INFO: PersistentVolume pvc-8e471795-a85f-4d70-b6f7-cdadb3a065c9 found and phase=Released (162.138556ms)
... skipping 13 lines ...

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

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 897 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 14 08:27:30.734: 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.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun 14 08:27:31.548: INFO: Creating resource for dynamic PV
Jun 14 08:27:31.548: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3584-e2e-scb2wn8
STEP: creating a claim
Jun 14 08:27:31.711: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-vq48
STEP: Checking for subpath error in container status
Jun 14 08:27:46.525: INFO: Deleting pod "pod-subpath-test-dynamicpv-vq48" in namespace "provisioning-3584"
Jun 14 08:27:46.688: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-vq48" to be fully deleted
STEP: Deleting pod
Jun 14 08:28:01.013: INFO: Deleting pod "pod-subpath-test-dynamicpv-vq48" in namespace "provisioning-3584"
STEP: Deleting pvc
Jun 14 08:28:01.500: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com2chgt"
... skipping 9 lines ...

• [SLOW TEST:36.745 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath directory is outside the volume [Slow][LinuxOnly]
    /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 14 08:28:07.482: INFO: Driver "ebs.csi.aws.com" does not support volume type "PreprovisionedPV" - skipping
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
... skipping 2 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.zEGyQTPHP/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.zEGyQTPHP/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.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 150 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 14 08:27:13.636: 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.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 14 08:27:14.448: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 14 08:27:15.380: INFO: Successfully created a new PD: "aws://ap-northeast-2a/vol-00ec70aa332fc1720".
Jun 14 08:27:15.380: INFO: Creating resource for pre-provisioned PV
Jun 14 08:27:15.380: INFO: Creating PVC and PV
... skipping 8 lines ...
Jun 14 08:27:26.764: INFO: PersistentVolumeClaim pvc-ntp2x found but phase is Pending instead of Bound.
Jun 14 08:27:28.927: INFO: PersistentVolumeClaim pvc-ntp2x found but phase is Pending instead of Bound.
Jun 14 08:27:31.091: INFO: PersistentVolumeClaim pvc-ntp2x found and phase=Bound (15.314453648s)
Jun 14 08:27:31.091: INFO: Waiting up to 3m0s for PersistentVolume aws-qbqfc to have phase Bound
Jun 14 08:27:31.253: INFO: PersistentVolume aws-qbqfc found and phase=Bound (162.201717ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 14 08:27:34.230: INFO: Deleting pod "pod-04467f70-cb0c-41c0-9489-2ccc152d28c3" in namespace "volumemode-3179"
Jun 14 08:27:34.400: INFO: Wait up to 5m0s for pod "pod-04467f70-cb0c-41c0-9489-2ccc152d28c3" to be fully deleted
STEP: Deleting pv and pvc
Jun 14 08:27:46.727: INFO: Deleting PersistentVolumeClaim "pvc-ntp2x"
Jun 14 08:27:46.890: INFO: Deleting PersistentVolume "aws-qbqfc"
Jun 14 08:27:47.319: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-00ec70aa332fc1720", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00ec70aa332fc1720 is currently attached to i-0ad576b69e7030d31
	status code: 400, request id: 1b853e0a-9f65-4a08-9bfb-f4f44ae0df2a
Jun 14 08:27:53.126: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-00ec70aa332fc1720", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00ec70aa332fc1720 is currently attached to i-0ad576b69e7030d31
	status code: 400, request id: a95a821e-ba98-4b03-a267-f4f98eb0c848
Jun 14 08:27:58.935: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-00ec70aa332fc1720", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00ec70aa332fc1720 is currently attached to i-0ad576b69e7030d31
	status code: 400, request id: f5abdbc4-a8ce-492f-a543-71794b05f1b1
Jun 14 08:28:04.709: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-00ec70aa332fc1720", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00ec70aa332fc1720 is currently attached to i-0ad576b69e7030d31
	status code: 400, request id: 83e67f7e-4582-4c20-ab30-a7557a25cc85
Jun 14 08:28:10.477: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-00ec70aa332fc1720".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 14 08:28:10.477: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-3179" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.zEGyQTPHP/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.zEGyQTPHP/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
    /tmp/kops.zEGyQTPHP/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.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 226 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.zEGyQTPHP/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.zEGyQTPHP/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.zEGyQTPHP/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.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 89 lines ...
Jun 14 08:27:29.256: INFO: PersistentVolumeClaim pvc-tp5vz found but phase is Pending instead of Bound.
Jun 14 08:27:31.416: INFO: PersistentVolumeClaim pvc-tp5vz found and phase=Bound (6.632775962s)
Jun 14 08:27:31.416: INFO: Waiting up to 3m0s for PersistentVolume aws-x5hjt to have phase Bound
Jun 14 08:27:31.574: INFO: PersistentVolume aws-x5hjt found and phase=Bound (157.781569ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-p7dl
STEP: Creating a pod to test exec-volume-test
Jun 14 08:27:32.049: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-p7dl" in namespace "volume-6841" to be "Succeeded or Failed"
Jun 14 08:27:32.207: INFO: Pod "exec-volume-test-preprovisionedpv-p7dl": Phase="Pending", Reason="", readiness=false. Elapsed: 158.013907ms
Jun 14 08:27:34.365: INFO: Pod "exec-volume-test-preprovisionedpv-p7dl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.316055444s
Jun 14 08:27:36.522: INFO: Pod "exec-volume-test-preprovisionedpv-p7dl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.473775781s
Jun 14 08:27:38.681: INFO: Pod "exec-volume-test-preprovisionedpv-p7dl": Phase="Pending", Reason="", readiness=false. Elapsed: 6.63209052s
Jun 14 08:27:40.839: INFO: Pod "exec-volume-test-preprovisionedpv-p7dl": Phase="Pending", Reason="", readiness=false. Elapsed: 8.790905327s
Jun 14 08:27:42.998: INFO: Pod "exec-volume-test-preprovisionedpv-p7dl": Phase="Pending", Reason="", readiness=false. Elapsed: 10.949836591s
Jun 14 08:27:45.157: INFO: Pod "exec-volume-test-preprovisionedpv-p7dl": Phase="Pending", Reason="", readiness=false. Elapsed: 13.108142061s
Jun 14 08:27:47.315: INFO: Pod "exec-volume-test-preprovisionedpv-p7dl": Phase="Pending", Reason="", readiness=false. Elapsed: 15.266001961s
Jun 14 08:27:49.472: INFO: Pod "exec-volume-test-preprovisionedpv-p7dl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 17.423575003s
STEP: Saw pod success
Jun 14 08:27:49.472: INFO: Pod "exec-volume-test-preprovisionedpv-p7dl" satisfied condition "Succeeded or Failed"
Jun 14 08:27:49.629: INFO: Trying to get logs from node ip-172-20-60-197.ap-northeast-2.compute.internal pod exec-volume-test-preprovisionedpv-p7dl container exec-container-preprovisionedpv-p7dl: <nil>
STEP: delete the pod
Jun 14 08:27:49.952: INFO: Waiting for pod exec-volume-test-preprovisionedpv-p7dl to disappear
Jun 14 08:27:50.110: INFO: Pod exec-volume-test-preprovisionedpv-p7dl no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-p7dl
Jun 14 08:27:50.110: INFO: Deleting pod "exec-volume-test-preprovisionedpv-p7dl" in namespace "volume-6841"
STEP: Deleting pv and pvc
Jun 14 08:27:50.267: INFO: Deleting PersistentVolumeClaim "pvc-tp5vz"
Jun 14 08:27:50.425: INFO: Deleting PersistentVolume "aws-x5hjt"
Jun 14 08:27:50.848: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0813df65a9e6fef6e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0813df65a9e6fef6e is currently attached to i-03448625fa1301d2f
	status code: 400, request id: 08a0b493-d4ee-4204-bb96-26cca0f8a5bf
Jun 14 08:27:56.641: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0813df65a9e6fef6e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0813df65a9e6fef6e is currently attached to i-03448625fa1301d2f
	status code: 400, request id: 66fcf457-4dbf-4206-923d-758add92add1
Jun 14 08:28:02.454: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0813df65a9e6fef6e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0813df65a9e6fef6e is currently attached to i-03448625fa1301d2f
	status code: 400, request id: c664cdb8-6425-4cc7-b3e1-7379454a752f
Jun 14 08:28:08.268: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0813df65a9e6fef6e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0813df65a9e6fef6e is currently attached to i-03448625fa1301d2f
	status code: 400, request id: d483eef0-c0ee-4c96-b86a-1d7936f67bdf
Jun 14 08:28:14.024: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-0813df65a9e6fef6e".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 14 08:28:14.025: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-6841" for this suite.
... skipping 181 lines ...
Jun 14 08:27:21.164: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-557-e2e-scmlchb
STEP: creating a claim
Jun 14 08:27:21.326: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-pgb9
STEP: Creating a pod to test exec-volume-test
Jun 14 08:27:21.816: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-pgb9" in namespace "volume-557" to be "Succeeded or Failed"
Jun 14 08:27:21.977: INFO: Pod "exec-volume-test-dynamicpv-pgb9": Phase="Pending", Reason="", readiness=false. Elapsed: 161.378018ms
Jun 14 08:27:24.139: INFO: Pod "exec-volume-test-dynamicpv-pgb9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.322970465s
Jun 14 08:27:26.303: INFO: Pod "exec-volume-test-dynamicpv-pgb9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.487425528s
Jun 14 08:27:28.466: INFO: Pod "exec-volume-test-dynamicpv-pgb9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.649720416s
Jun 14 08:27:30.629: INFO: Pod "exec-volume-test-dynamicpv-pgb9": Phase="Pending", Reason="", readiness=false. Elapsed: 8.813217295s
Jun 14 08:27:32.791: INFO: Pod "exec-volume-test-dynamicpv-pgb9": Phase="Pending", Reason="", readiness=false. Elapsed: 10.974704607s
Jun 14 08:27:34.952: INFO: Pod "exec-volume-test-dynamicpv-pgb9": Phase="Pending", Reason="", readiness=false. Elapsed: 13.136302806s
Jun 14 08:27:37.114: INFO: Pod "exec-volume-test-dynamicpv-pgb9": Phase="Pending", Reason="", readiness=false. Elapsed: 15.298189472s
Jun 14 08:27:39.276: INFO: Pod "exec-volume-test-dynamicpv-pgb9": Phase="Pending", Reason="", readiness=false. Elapsed: 17.460099212s
Jun 14 08:27:41.438: INFO: Pod "exec-volume-test-dynamicpv-pgb9": Phase="Pending", Reason="", readiness=false. Elapsed: 19.621924138s
Jun 14 08:27:43.600: INFO: Pod "exec-volume-test-dynamicpv-pgb9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.78412814s
STEP: Saw pod success
Jun 14 08:27:43.600: INFO: Pod "exec-volume-test-dynamicpv-pgb9" satisfied condition "Succeeded or Failed"
Jun 14 08:27:43.760: INFO: Trying to get logs from node ip-172-20-33-97.ap-northeast-2.compute.internal pod exec-volume-test-dynamicpv-pgb9 container exec-container-dynamicpv-pgb9: <nil>
STEP: delete the pod
Jun 14 08:27:44.087: INFO: Waiting for pod exec-volume-test-dynamicpv-pgb9 to disappear
Jun 14 08:27:44.246: INFO: Pod exec-volume-test-dynamicpv-pgb9 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-pgb9
Jun 14 08:27:44.247: INFO: Deleting pod "exec-volume-test-dynamicpv-pgb9" in namespace "volume-557"
... skipping 195 lines ...
Jun 14 08:25:55.189: INFO: Creating resource for dynamic PV
Jun 14 08:25:55.189: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-9230-e2e-sc7crpn
STEP: creating a claim
Jun 14 08:25:55.350: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 14 08:25:55.831: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-4mx7j" in namespace "snapshotting-9230" to be "Succeeded or Failed"
Jun 14 08:25:55.989: INFO: Pod "pvc-snapshottable-tester-4mx7j": Phase="Pending", Reason="", readiness=false. Elapsed: 158.554746ms
Jun 14 08:25:58.149: INFO: Pod "pvc-snapshottable-tester-4mx7j": Phase="Pending", Reason="", readiness=false. Elapsed: 2.318047873s
Jun 14 08:26:00.308: INFO: Pod "pvc-snapshottable-tester-4mx7j": Phase="Pending", Reason="", readiness=false. Elapsed: 4.477825341s
Jun 14 08:26:02.465: INFO: Pod "pvc-snapshottable-tester-4mx7j": Phase="Pending", Reason="", readiness=false. Elapsed: 6.634734459s
Jun 14 08:26:04.622: INFO: Pod "pvc-snapshottable-tester-4mx7j": Phase="Pending", Reason="", readiness=false. Elapsed: 8.791302917s
Jun 14 08:26:06.780: INFO: Pod "pvc-snapshottable-tester-4mx7j": Phase="Pending", Reason="", readiness=false. Elapsed: 10.949203603s
Jun 14 08:26:08.938: INFO: Pod "pvc-snapshottable-tester-4mx7j": Phase="Succeeded", Reason="", readiness=false. Elapsed: 13.106968885s
STEP: Saw pod success
Jun 14 08:26:08.938: INFO: Pod "pvc-snapshottable-tester-4mx7j" satisfied condition "Succeeded or Failed"
Jun 14 08:26:09.252: INFO: Pod pvc-snapshottable-tester-4mx7j has the following logs: 
Jun 14 08:26:09.252: INFO: Deleting pod "pvc-snapshottable-tester-4mx7j" in namespace "snapshotting-9230"
Jun 14 08:26:09.417: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-4mx7j" to be fully deleted
Jun 14 08:26:09.573: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comfhpfn] to have phase Bound
Jun 14 08:26:09.729: INFO: PersistentVolumeClaim ebs.csi.aws.comfhpfn found and phase=Bound (156.082967ms)
STEP: [init] checking the claim
... skipping 44 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.zEGyQTPHP/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 14 08:26:47.584: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-8hkq7" in namespace "snapshotting-9230" to be "Succeeded or Failed"
Jun 14 08:26:47.741: INFO: Pod "pvc-snapshottable-data-tester-8hkq7": Phase="Pending", Reason="", readiness=false. Elapsed: 156.362157ms
Jun 14 08:26:49.898: INFO: Pod "pvc-snapshottable-data-tester-8hkq7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.313580705s
Jun 14 08:26:52.062: INFO: Pod "pvc-snapshottable-data-tester-8hkq7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.478078414s
Jun 14 08:26:54.220: INFO: Pod "pvc-snapshottable-data-tester-8hkq7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.635888563s
Jun 14 08:26:56.378: INFO: Pod "pvc-snapshottable-data-tester-8hkq7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.793802501s
Jun 14 08:26:58.535: INFO: Pod "pvc-snapshottable-data-tester-8hkq7": Phase="Pending", Reason="", readiness=false. Elapsed: 10.950844345s
Jun 14 08:27:00.692: INFO: Pod "pvc-snapshottable-data-tester-8hkq7": Phase="Pending", Reason="", readiness=false. Elapsed: 13.107795719s
Jun 14 08:27:02.849: INFO: Pod "pvc-snapshottable-data-tester-8hkq7": Phase="Pending", Reason="", readiness=false. Elapsed: 15.265076802s
Jun 14 08:27:05.006: INFO: Pod "pvc-snapshottable-data-tester-8hkq7": Phase="Pending", Reason="", readiness=false. Elapsed: 17.422218898s
Jun 14 08:27:07.163: INFO: Pod "pvc-snapshottable-data-tester-8hkq7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.579149309s
STEP: Saw pod success
Jun 14 08:27:07.163: INFO: Pod "pvc-snapshottable-data-tester-8hkq7" satisfied condition "Succeeded or Failed"
Jun 14 08:27:07.477: INFO: Pod pvc-snapshottable-data-tester-8hkq7 has the following logs: 
Jun 14 08:27:07.477: INFO: Deleting pod "pvc-snapshottable-data-tester-8hkq7" in namespace "snapshotting-9230"
Jun 14 08:27:07.642: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-8hkq7" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 14 08:27:30.427: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-9230 exec restored-pvc-tester-xqr6s --namespace=snapshotting-9230 -- cat /mnt/test/data'
... skipping 256 lines ...
    /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:108
      
      /tmp/kops.zEGyQTPHP/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.zEGyQTPHP/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-9230 exec restored-pvc-tester-xqr6s --namespace=snapshotting-9230 -- 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-9230 exec restored-pvc-tester-xqr6s --namespace=snapshotting-9230 -- 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.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:602
------------------------------
[BeforeEach] [sig-storage] Zone Support [Feature:vsphere]
... skipping 324 lines ...

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

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

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 10 lines ...
Jun 14 08:28:15.130: INFO: Creating resource for dynamic PV
Jun 14 08:28:15.130: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-2082-e2e-scg6h8g
STEP: creating a claim
STEP: Expanding non-expandable pvc
Jun 14 08:28:15.606: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 14 08:28:15.922: INFO: Error updating pvc ebs.csi.aws.com5pn9v: PersistentVolumeClaim "ebs.csi.aws.com5pn9v" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2082-e2e-scg6h8g",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun 14 08:28:46.557: INFO: Error updating pvc ebs.csi.aws.com5pn9v: PersistentVolumeClaim "ebs.csi.aws.com5pn9v" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 242 lines ...
Jun 14 08:28:22.096: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 14 08:28:23.093: INFO: Successfully created a new PD: "aws://ap-northeast-2a/vol-0fc298389a86c556f".
Jun 14 08:28:23.093: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-sc9r
STEP: Creating a pod to test exec-volume-test
Jun 14 08:28:23.256: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-sc9r" in namespace "volume-7919" to be "Succeeded or Failed"
Jun 14 08:28:23.417: INFO: Pod "exec-volume-test-inlinevolume-sc9r": Phase="Pending", Reason="", readiness=false. Elapsed: 160.892796ms
Jun 14 08:28:25.580: INFO: Pod "exec-volume-test-inlinevolume-sc9r": Phase="Pending", Reason="", readiness=false. Elapsed: 2.323149698s
Jun 14 08:28:27.741: INFO: Pod "exec-volume-test-inlinevolume-sc9r": Phase="Pending", Reason="", readiness=false. Elapsed: 4.484514554s
Jun 14 08:28:29.904: INFO: Pod "exec-volume-test-inlinevolume-sc9r": Phase="Pending", Reason="", readiness=false. Elapsed: 6.647860931s
Jun 14 08:28:32.066: INFO: Pod "exec-volume-test-inlinevolume-sc9r": Phase="Pending", Reason="", readiness=false. Elapsed: 8.80996624s
Jun 14 08:28:34.228: INFO: Pod "exec-volume-test-inlinevolume-sc9r": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.971789795s
STEP: Saw pod success
Jun 14 08:28:34.228: INFO: Pod "exec-volume-test-inlinevolume-sc9r" satisfied condition "Succeeded or Failed"
Jun 14 08:28:34.389: INFO: Trying to get logs from node ip-172-20-33-97.ap-northeast-2.compute.internal pod exec-volume-test-inlinevolume-sc9r container exec-container-inlinevolume-sc9r: <nil>
STEP: delete the pod
Jun 14 08:28:34.721: INFO: Waiting for pod exec-volume-test-inlinevolume-sc9r to disappear
Jun 14 08:28:34.882: INFO: Pod exec-volume-test-inlinevolume-sc9r no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-sc9r
Jun 14 08:28:34.882: INFO: Deleting pod "exec-volume-test-inlinevolume-sc9r" in namespace "volume-7919"
Jun 14 08:28:35.325: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0fc298389a86c556f", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0fc298389a86c556f is currently attached to i-0d03fe0f2c0571cc7
	status code: 400, request id: 70a118b3-474a-41d0-8d30-74463114b023
Jun 14 08:28:41.072: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0fc298389a86c556f", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0fc298389a86c556f is currently attached to i-0d03fe0f2c0571cc7
	status code: 400, request id: a66e15c4-b517-4cc4-88b0-75f83b155ff7
Jun 14 08:28:46.895: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0fc298389a86c556f", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0fc298389a86c556f is currently attached to i-0d03fe0f2c0571cc7
	status code: 400, request id: a31e5992-9f77-4289-b70f-7eff8c2f614f
Jun 14 08:28:52.767: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0fc298389a86c556f", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0fc298389a86c556f is currently attached to i-0d03fe0f2c0571cc7
	status code: 400, request id: 1662aa0f-1339-4768-8c1b-6eb883b7b087
Jun 14 08:28:58.539: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-0fc298389a86c556f".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 14 08:28:58.539: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-7919" for this suite.
... skipping 14 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 14 08:28:09.941: 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.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun 14 08:28:10.733: INFO: Creating resource for dynamic PV
Jun 14 08:28:10.733: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-697-e2e-scmcw8d
STEP: creating a claim
Jun 14 08:28:10.891: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-x4gc
STEP: Checking for subpath error in container status
Jun 14 08:28:33.688: INFO: Deleting pod "pod-subpath-test-dynamicpv-x4gc" in namespace "provisioning-697"
Jun 14 08:28:33.846: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-x4gc" to be fully deleted
STEP: Deleting pod
Jun 14 08:28:42.164: INFO: Deleting pod "pod-subpath-test-dynamicpv-x4gc" in namespace "provisioning-697"
STEP: Deleting pvc
Jun 14 08:28:42.637: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com6b8bk"
... skipping 11 lines ...

• [SLOW TEST:48.965 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.zEGyQTPHP/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.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow]
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 14 08:28:58.908: INFO: Driver supports dynamic provisioning, skipping PreprovisionedPV pattern
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow]
... skipping 211 lines ...

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

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

    /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 249 lines ...
Jun 14 08:28:30.229: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 14 08:28:31.289: INFO: Successfully created a new PD: "aws://ap-northeast-2a/vol-017cb2751844558d9".
Jun 14 08:28:31.289: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-w6dj
STEP: Creating a pod to test exec-volume-test
Jun 14 08:28:31.447: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-w6dj" in namespace "volume-712" to be "Succeeded or Failed"
Jun 14 08:28:31.604: INFO: Pod "exec-volume-test-inlinevolume-w6dj": Phase="Pending", Reason="", readiness=false. Elapsed: 156.506426ms
Jun 14 08:28:33.760: INFO: Pod "exec-volume-test-inlinevolume-w6dj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.313210622s
Jun 14 08:28:35.918: INFO: Pod "exec-volume-test-inlinevolume-w6dj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.470625588s
Jun 14 08:28:38.074: INFO: Pod "exec-volume-test-inlinevolume-w6dj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.627142339s
Jun 14 08:28:40.233: INFO: Pod "exec-volume-test-inlinevolume-w6dj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.785683663s
Jun 14 08:28:42.390: INFO: Pod "exec-volume-test-inlinevolume-w6dj": Phase="Pending", Reason="", readiness=false. Elapsed: 10.94283376s
Jun 14 08:28:44.547: INFO: Pod "exec-volume-test-inlinevolume-w6dj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 13.099641816s
STEP: Saw pod success
Jun 14 08:28:44.547: INFO: Pod "exec-volume-test-inlinevolume-w6dj" satisfied condition "Succeeded or Failed"
Jun 14 08:28:44.703: INFO: Trying to get logs from node ip-172-20-32-95.ap-northeast-2.compute.internal pod exec-volume-test-inlinevolume-w6dj container exec-container-inlinevolume-w6dj: <nil>
STEP: delete the pod
Jun 14 08:28:45.029: INFO: Waiting for pod exec-volume-test-inlinevolume-w6dj to disappear
Jun 14 08:28:45.185: INFO: Pod exec-volume-test-inlinevolume-w6dj no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-w6dj
Jun 14 08:28:45.185: INFO: Deleting pod "exec-volume-test-inlinevolume-w6dj" in namespace "volume-712"
Jun 14 08:28:45.647: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-017cb2751844558d9", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-017cb2751844558d9 is currently attached to i-0ad576b69e7030d31
	status code: 400, request id: 56e21894-0b88-449c-93f1-efec04fc6bbb
Jun 14 08:28:51.430: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-017cb2751844558d9", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-017cb2751844558d9 is currently attached to i-0ad576b69e7030d31
	status code: 400, request id: cdbd2591-d84d-4488-a38c-54f0086d6ea3
Jun 14 08:28:57.219: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-017cb2751844558d9", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-017cb2751844558d9 is currently attached to i-0ad576b69e7030d31
	status code: 400, request id: c9fc5769-53c0-448c-a1ae-11035e97a7f9
Jun 14 08:29:02.987: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-017cb2751844558d9".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 14 08:29:02.987: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-712" for this suite.
... skipping 205 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.zEGyQTPHP/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.zEGyQTPHP/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.zEGyQTPHP/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.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 120 lines ...
Jun 14 08:28:36.889: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 14 08:28:37.878: INFO: Successfully created a new PD: "aws://ap-northeast-2a/vol-0d7fc0ef442c8dd77".
Jun 14 08:28:37.878: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-rfvw
STEP: Creating a pod to test exec-volume-test
Jun 14 08:28:38.040: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-rfvw" in namespace "volume-6616" to be "Succeeded or Failed"
Jun 14 08:28:38.199: INFO: Pod "exec-volume-test-inlinevolume-rfvw": Phase="Pending", Reason="", readiness=false. Elapsed: 159.188678ms
Jun 14 08:28:40.361: INFO: Pod "exec-volume-test-inlinevolume-rfvw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.320924383s
Jun 14 08:28:42.522: INFO: Pod "exec-volume-test-inlinevolume-rfvw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.482551569s
Jun 14 08:28:44.687: INFO: Pod "exec-volume-test-inlinevolume-rfvw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.647146446s
Jun 14 08:28:46.846: INFO: Pod "exec-volume-test-inlinevolume-rfvw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.806679004s
Jun 14 08:28:49.006: INFO: Pod "exec-volume-test-inlinevolume-rfvw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.96659526s
STEP: Saw pod success
Jun 14 08:28:49.006: INFO: Pod "exec-volume-test-inlinevolume-rfvw" satisfied condition "Succeeded or Failed"
Jun 14 08:28:49.166: INFO: Trying to get logs from node ip-172-20-33-97.ap-northeast-2.compute.internal pod exec-volume-test-inlinevolume-rfvw container exec-container-inlinevolume-rfvw: <nil>
STEP: delete the pod
Jun 14 08:28:49.491: INFO: Waiting for pod exec-volume-test-inlinevolume-rfvw to disappear
Jun 14 08:28:49.650: INFO: Pod exec-volume-test-inlinevolume-rfvw no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-rfvw
Jun 14 08:28:49.650: INFO: Deleting pod "exec-volume-test-inlinevolume-rfvw" in namespace "volume-6616"
Jun 14 08:28:50.139: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0d7fc0ef442c8dd77", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d7fc0ef442c8dd77 is currently attached to i-0d03fe0f2c0571cc7
	status code: 400, request id: cc2a1580-d9cb-42cb-a228-7625d17385cd
Jun 14 08:28:55.978: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0d7fc0ef442c8dd77", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d7fc0ef442c8dd77 is currently attached to i-0d03fe0f2c0571cc7
	status code: 400, request id: 608e8096-80ba-4a80-b59f-a8ab7fc1f79b
Jun 14 08:29:01.780: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0d7fc0ef442c8dd77", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d7fc0ef442c8dd77 is currently attached to i-0d03fe0f2c0571cc7
	status code: 400, request id: 49ff9906-b377-49cc-b089-4bec48e51c4d
Jun 14 08:29:07.531: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0d7fc0ef442c8dd77", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d7fc0ef442c8dd77 is currently attached to i-0d03fe0f2c0571cc7
	status code: 400, request id: 797e29dd-896a-4ab5-a7b8-0db03f790116
Jun 14 08:29:13.343: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-0d7fc0ef442c8dd77".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 14 08:29:13.343: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-6616" for this suite.
... skipping 141 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 14 08:28:21.667: 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.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun 14 08:28:22.464: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 14 08:28:22.464: INFO: Creating resource for dynamic PV
Jun 14 08:28:22.464: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-739268zp4
STEP: creating a claim
Jun 14 08:28:22.624: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-6mdj
STEP: Checking for subpath error in container status
Jun 14 08:28:37.427: INFO: Deleting pod "pod-subpath-test-dynamicpv-6mdj" in namespace "provisioning-7392"
Jun 14 08:28:37.586: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-6mdj" to be fully deleted
STEP: Deleting pod
Jun 14 08:28:43.909: INFO: Deleting pod "pod-subpath-test-dynamicpv-6mdj" in namespace "provisioning-7392"
STEP: Deleting pvc
Jun 14 08:28:44.390: INFO: Deleting PersistentVolumeClaim "awsc2vn9"
... skipping 16 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.zEGyQTPHP/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.zEGyQTPHP/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath file is outside the volume [Slow][LinuxOnly]
      /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] volumeIO
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] volumeIO
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 119 lines ...
Jun 14 08:29:01.369: INFO: Waiting for pod aws-client to disappear
Jun 14 08:29:01.526: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 14 08:29:01.526: INFO: Deleting PersistentVolumeClaim "pvc-xfcwf"
Jun 14 08:29:01.686: INFO: Deleting PersistentVolume "aws-f5wgz"
Jun 14 08:29:02.610: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0c43b742152463d96", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c43b742152463d96 is currently attached to i-03448625fa1301d2f
	status code: 400, request id: 6b720164-4bdd-4f60-b6cb-4a9398dd9dc5
Jun 14 08:29:08.369: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0c43b742152463d96", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c43b742152463d96 is currently attached to i-03448625fa1301d2f
	status code: 400, request id: 32cbe88b-14f0-43cd-96b0-ba6151449288
Jun 14 08:29:14.184: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0c43b742152463d96", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c43b742152463d96 is currently attached to i-03448625fa1301d2f
	status code: 400, request id: eb8d01e9-3930-4684-adf8-1a99925e4208
Jun 14 08:29:19.986: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-0c43b742152463d96".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 14 08:29:19.986: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-2272" for this suite.
... skipping 91 lines ...
Jun 14 08:29:19.575: INFO: Waiting for pod aws-client to disappear
Jun 14 08:29:19.737: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 14 08:29:19.738: INFO: Deleting PersistentVolumeClaim "pvc-x5q4v"
Jun 14 08:29:19.901: INFO: Deleting PersistentVolume "aws-v7zrm"
Jun 14 08:29:20.833: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0d471415b095c821f", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d471415b095c821f is currently attached to i-0bec054b8ebd8f3d8
	status code: 400, request id: 278c7df6-14ab-4c52-8d3c-644e526953e0
Jun 14 08:29:26.645: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-0d471415b095c821f".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 14 08:29:26.645: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8991" for this suite.
... skipping 555 lines ...
Jun 14 08:29:09.380: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-9161-e2e-scvb7l4
STEP: creating a claim
Jun 14 08:29:09.541: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-hhnz
STEP: Creating a pod to test exec-volume-test
Jun 14 08:29:10.029: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-hhnz" in namespace "volume-9161" to be "Succeeded or Failed"
Jun 14 08:29:10.193: INFO: Pod "exec-volume-test-dynamicpv-hhnz": Phase="Pending", Reason="", readiness=false. Elapsed: 163.273029ms
Jun 14 08:29:12.356: INFO: Pod "exec-volume-test-dynamicpv-hhnz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.326549946s
Jun 14 08:29:14.516: INFO: Pod "exec-volume-test-dynamicpv-hhnz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.487159817s
Jun 14 08:29:16.678: INFO: Pod "exec-volume-test-dynamicpv-hhnz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.648402663s
Jun 14 08:29:18.841: INFO: Pod "exec-volume-test-dynamicpv-hhnz": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.812120083s
STEP: Saw pod success
Jun 14 08:29:18.841: INFO: Pod "exec-volume-test-dynamicpv-hhnz" satisfied condition "Succeeded or Failed"
Jun 14 08:29:19.002: INFO: Trying to get logs from node ip-172-20-32-95.ap-northeast-2.compute.internal pod exec-volume-test-dynamicpv-hhnz container exec-container-dynamicpv-hhnz: <nil>
STEP: delete the pod
Jun 14 08:29:19.336: INFO: Waiting for pod exec-volume-test-dynamicpv-hhnz to disappear
Jun 14 08:29:19.496: INFO: Pod exec-volume-test-dynamicpv-hhnz no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-hhnz
Jun 14 08:29:19.496: INFO: Deleting pod "exec-volume-test-dynamicpv-hhnz" in namespace "volume-9161"
... skipping 266 lines ...
Jun 14 08:30:07.251: INFO: Waiting for pod aws-client to disappear
Jun 14 08:30:07.412: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 14 08:30:07.412: INFO: Deleting PersistentVolumeClaim "pvc-fw2nn"
Jun 14 08:30:07.576: INFO: Deleting PersistentVolume "aws-zznww"
Jun 14 08:30:08.500: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-007dc7026b935a9ae", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-007dc7026b935a9ae is currently attached to i-0ad576b69e7030d31
	status code: 400, request id: 03422e95-a3bb-4718-91d3-7117b016427f
Jun 14 08:30:14.314: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-007dc7026b935a9ae".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumes
  /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 14 08:30:14.314: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-6249" for this suite.
... skipping 137 lines ...
Jun 14 08:28:14.264: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-5330qp9ht      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-5330    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-5330qp9ht,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-5330    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-5330qp9ht,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-5330    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-5330qp9ht,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-5330qp9ht    3ecae81f-4d32-45fe-af8a-d2b118ee774c 12892 0 2021-06-14 08:28:14 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-14 08:28:14 +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-4mh8z pvc- provisioning-5330  4c4f53fe-4a22-4bd9-9269-4e57d97236e3 12909 0 2021-06-14 08:28:15 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-14 08:28:14 +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-5330qp9ht,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-b6f16817-e7f0-4856-afb6-36871906f912 in namespace provisioning-5330
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun 14 08:28:38.052: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-5m8wx" in namespace "provisioning-5330" to be "Succeeded or Failed"
Jun 14 08:28:38.213: INFO: Pod "pvc-volume-tester-writer-5m8wx": Phase="Pending", Reason="", readiness=false. Elapsed: 160.876307ms
Jun 14 08:28:40.375: INFO: Pod "pvc-volume-tester-writer-5m8wx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.322645002s
Jun 14 08:28:42.537: INFO: Pod "pvc-volume-tester-writer-5m8wx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.484882119s
Jun 14 08:28:44.700: INFO: Pod "pvc-volume-tester-writer-5m8wx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.647252996s
Jun 14 08:28:46.862: INFO: Pod "pvc-volume-tester-writer-5m8wx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.809448603s
Jun 14 08:28:49.023: INFO: Pod "pvc-volume-tester-writer-5m8wx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.97089827s
... skipping 22 lines ...
Jun 14 08:29:38.771: INFO: Pod "pvc-volume-tester-writer-5m8wx": Phase="Pending", Reason="", readiness=false. Elapsed: 1m0.718720768s
Jun 14 08:29:40.932: INFO: Pod "pvc-volume-tester-writer-5m8wx": Phase="Pending", Reason="", readiness=false. Elapsed: 1m2.880154613s
Jun 14 08:29:43.095: INFO: Pod "pvc-volume-tester-writer-5m8wx": Phase="Pending", Reason="", readiness=false. Elapsed: 1m5.042827028s
Jun 14 08:29:45.257: INFO: Pod "pvc-volume-tester-writer-5m8wx": Phase="Pending", Reason="", readiness=false. Elapsed: 1m7.204895995s
Jun 14 08:29:47.420: INFO: Pod "pvc-volume-tester-writer-5m8wx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m9.367558404s
STEP: Saw pod success
Jun 14 08:29:47.420: INFO: Pod "pvc-volume-tester-writer-5m8wx" satisfied condition "Succeeded or Failed"
Jun 14 08:29:47.744: INFO: Pod pvc-volume-tester-writer-5m8wx has the following logs: 
Jun 14 08:29:47.744: INFO: Deleting pod "pvc-volume-tester-writer-5m8wx" in namespace "provisioning-5330"
Jun 14 08:29:47.911: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-5m8wx" 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-48-27.ap-northeast-2.compute.internal"
Jun 14 08:29:48.569: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-h2627" in namespace "provisioning-5330" to be "Succeeded or Failed"
Jun 14 08:29:48.730: INFO: Pod "pvc-volume-tester-reader-h2627": Phase="Pending", Reason="", readiness=false. Elapsed: 161.298038ms
Jun 14 08:29:50.892: INFO: Pod "pvc-volume-tester-reader-h2627": Phase="Pending", Reason="", readiness=false. Elapsed: 2.323319425s
Jun 14 08:29:53.054: INFO: Pod "pvc-volume-tester-reader-h2627": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.485028432s
STEP: Saw pod success
Jun 14 08:29:53.054: INFO: Pod "pvc-volume-tester-reader-h2627" satisfied condition "Succeeded or Failed"
Jun 14 08:29:53.379: INFO: Pod pvc-volume-tester-reader-h2627 has the following logs: hello world

Jun 14 08:29:53.379: INFO: Deleting pod "pvc-volume-tester-reader-h2627" in namespace "provisioning-5330"
Jun 14 08:29:53.547: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-h2627" to be fully deleted
Jun 14 08:29:53.707: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-4mh8z] to have phase Bound
Jun 14 08:29:53.869: INFO: PersistentVolumeClaim pvc-4mh8z found and phase=Bound (161.809438ms)
... skipping 39 lines ...
Jun 14 08:28:59.726: INFO: Creating resource for dynamic PV
Jun 14 08:28:59.726: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1235tz7p6
STEP: creating a claim
Jun 14 08:28:59.885: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-1235
Jun 14 08:29:00.365: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-1235" in namespace "provisioning-1235" to be "Succeeded or Failed"
Jun 14 08:29:00.525: INFO: Pod "volume-prep-provisioning-1235": Phase="Pending", Reason="", readiness=false. Elapsed: 159.772177ms
Jun 14 08:29:02.683: INFO: Pod "volume-prep-provisioning-1235": Phase="Pending", Reason="", readiness=false. Elapsed: 2.318683934s
Jun 14 08:29:04.845: INFO: Pod "volume-prep-provisioning-1235": Phase="Pending", Reason="", readiness=false. Elapsed: 4.48021343s
Jun 14 08:29:07.004: INFO: Pod "volume-prep-provisioning-1235": Phase="Pending", Reason="", readiness=false. Elapsed: 6.638823825s
Jun 14 08:29:09.162: INFO: Pod "volume-prep-provisioning-1235": Phase="Pending", Reason="", readiness=false. Elapsed: 8.797319506s
Jun 14 08:29:11.322: INFO: Pod "volume-prep-provisioning-1235": Phase="Pending", Reason="", readiness=false. Elapsed: 10.956712016s
Jun 14 08:29:13.479: INFO: Pod "volume-prep-provisioning-1235": Phase="Pending", Reason="", readiness=false. Elapsed: 13.114579273s
Jun 14 08:29:15.638: INFO: Pod "volume-prep-provisioning-1235": Phase="Pending", Reason="", readiness=false. Elapsed: 15.27273265s
Jun 14 08:29:17.797: INFO: Pod "volume-prep-provisioning-1235": Phase="Pending", Reason="", readiness=false. Elapsed: 17.43176073s
Jun 14 08:29:19.954: INFO: Pod "volume-prep-provisioning-1235": Phase="Pending", Reason="", readiness=false. Elapsed: 19.589318988s
Jun 14 08:29:22.115: INFO: Pod "volume-prep-provisioning-1235": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.749936938s
STEP: Saw pod success
Jun 14 08:29:22.115: INFO: Pod "volume-prep-provisioning-1235" satisfied condition "Succeeded or Failed"
Jun 14 08:29:22.115: INFO: Deleting pod "volume-prep-provisioning-1235" in namespace "provisioning-1235"
Jun 14 08:29:22.282: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-1235" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-f8p4
STEP: Checking for subpath error in container status
Jun 14 08:29:56.916: INFO: Deleting pod "pod-subpath-test-dynamicpv-f8p4" in namespace "provisioning-1235"
Jun 14 08:29:57.081: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-f8p4" to be fully deleted
STEP: Deleting pod
Jun 14 08:29:57.239: INFO: Deleting pod "pod-subpath-test-dynamicpv-f8p4" in namespace "provisioning-1235"
STEP: Deleting pvc
Jun 14 08:29:57.711: INFO: Deleting PersistentVolumeClaim "awspncxr"
... skipping 271 lines ...
      /tmp/kops.zEGyQTPHP/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/ephemeral.go:161
------------------------------


Summarizing 1 Failure:

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

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


Ginkgo ran 1 suite in 10m0.714874571s
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
I0614 08:30:32.534241   31973 app.go:59] RunDir for this run: "/logs/artifacts/583156fd-cce7-11eb-ab6f-62c732df09e9"
I0614 08:30:32.534405   31973 app.go:90] ID for this run: "583156fd-cce7-11eb-ab6f-62c732df09e9"
I0614 08:30:32.534429   31973 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
I0614 08:30:32.547025   31980 featureflag.go:167] FeatureFlag "SpecOverrideFlag"=true
... skipping 1445 lines ...