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

No Test Failures!


Error lines from build-log.txt

... skipping 490 lines ...
I0612 08:10:30.914736   11679 up.go:43] Cleaning up any leaked resources from previous cluster
I0612 08:10:30.914750   11679 dumplogs.go:38] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops toolbox dump --name e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ubuntu
I0612 08:10:30.932124   11685 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0612 08:10:30.932207   11685 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io" not found
W0612 08:10:31.454252   11679 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0612 08:10:31.454307   11679 down.go:48] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops delete cluster --name e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --yes
I0612 08:10:31.467104   11695 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0612 08:10:31.467173   11695 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io" not found
I0612 08:10:31.934242   11679 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/06/12 08:10:31 failed to get external ip from metadata service: http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip returned 404
I0612 08:10:31.943470   11679 http.go:37] curl https://ip.jsb.workers.dev
I0612 08:10:32.074411   11679 up.go:144] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops create cluster --name e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --cloud aws --kubernetes-version 1.21.0 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --networking calico --override=cluster.spec.cloudConfig.awsEBSCSIDriver.enabled=true --override=cluster.spec.snapshotController.enabled=true --override=cluster.spec.certManager.enabled=true --admin-access 34.67.40.150/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-northeast-2a --master-size c5.large
I0612 08:10:32.088491   11708 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0612 08:10:32.088573   11708 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I0612 08:10:32.132931   11708 create_cluster.go:728] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0612 08:10:32.777927   11708 new_cluster.go:1039]  Cloud Provider ID = aws
... skipping 40 lines ...

I0612 08:11:03.022740   11679 up.go:181] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops validate cluster --name e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0612 08:11:03.036672   11729 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0612 08:11:03.036754   11729 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io

W0612 08:11:04.544955   11729 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0612 08:16:35.731870   11729 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/coredns-autoscaler-6f594f4c58-h69cv		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-h69cv" is pending
Pod	kube-system/coredns-f45c4bf76-z8d6s			system-cluster-critical pod "coredns-f45c4bf76-z8d6s" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-kgscn		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-kgscn" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-wt7vk		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-wt7vk" is pending
Pod	kube-system/kops-controller-6fpws			system-node-critical pod "kops-controller-6fpws" is pending

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

... skipping 11 lines ...
Pod	kube-system/cert-manager-webhook-7bbf67968-blf75	system-cluster-critical pod "cert-manager-webhook-7bbf67968-blf75" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-h69cv		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-h69cv" is pending
Pod	kube-system/coredns-f45c4bf76-z8d6s			system-cluster-critical pod "coredns-f45c4bf76-z8d6s" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-kgscn		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-kgscn" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-wt7vk		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-wt7vk" is pending

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

... skipping 19 lines ...
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-wt7vk				system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-wt7vk" is pending
Pod	kube-system/ebs-csi-node-dfc7t						system-node-critical pod "ebs-csi-node-dfc7t" is pending
Pod	kube-system/ebs-csi-node-lb6kt						system-node-critical pod "ebs-csi-node-lb6kt" is pending
Pod	kube-system/kube-proxy-ip-172-20-33-120.ap-northeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-33-120.ap-northeast-2.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-46-122.ap-northeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-46-122.ap-northeast-2.compute.internal" is pending

Validation Failed
W0612 08:17:14.389258   11729 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 24 lines ...
Pod	kube-system/ebs-csi-node-k8z4h						system-node-critical pod "ebs-csi-node-k8z4h" is pending
Pod	kube-system/ebs-csi-node-lb6kt						system-node-critical pod "ebs-csi-node-lb6kt" is pending
Pod	kube-system/kube-proxy-ip-172-20-33-120.ap-northeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-33-120.ap-northeast-2.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-55-5.ap-northeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-55-5.ap-northeast-2.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-58-164.ap-northeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-58-164.ap-northeast-2.compute.internal" is pending

Validation Failed
W0612 08:17:27.063540   11729 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-h69cv		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-h69cv" is pending
Pod	kube-system/coredns-f45c4bf76-z8d6s			system-cluster-critical pod "coredns-f45c4bf76-z8d6s" is pending
Pod	kube-system/ebs-csi-node-76p9p				system-node-critical pod "ebs-csi-node-76p9p" is pending
Pod	kube-system/ebs-csi-node-k8z4h				system-node-critical pod "ebs-csi-node-k8z4h" is pending
Pod	kube-system/ebs-csi-node-lb6kt				system-node-critical pod "ebs-csi-node-lb6kt" is pending

Validation Failed
W0612 08:17:39.642347   11729 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-blf75	system-cluster-critical pod "cert-manager-webhook-7bbf67968-blf75" is pending
Pod	kube-system/coredns-f45c4bf76-z8d6s			system-cluster-critical pod "coredns-f45c4bf76-z8d6s" is pending
Pod	kube-system/coredns-f45c4bf76-znhbw			system-cluster-critical pod "coredns-f45c4bf76-znhbw" is pending
Pod	kube-system/ebs-csi-node-76p9p				system-node-critical pod "ebs-csi-node-76p9p" is pending
Pod	kube-system/ebs-csi-node-k8z4h				system-node-critical pod "ebs-csi-node-k8z4h" is pending

Validation Failed
W0612 08:17:52.280569   11729 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 10 lines ...
Pod	kube-system/calico-node-c9n9t				system-node-critical pod "calico-node-c9n9t" is not ready (calico-node)
Pod	kube-system/cert-manager-cainjector-74d69756d5-fmm8j	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-fmm8j" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-blf75	system-cluster-critical pod "cert-manager-webhook-7bbf67968-blf75" is not ready (cert-manager)
Pod	kube-system/coredns-f45c4bf76-z8d6s			system-cluster-critical pod "coredns-f45c4bf76-z8d6s" is pending
Pod	kube-system/coredns-f45c4bf76-znhbw			system-cluster-critical pod "coredns-f45c4bf76-znhbw" is pending

Validation Failed
W0612 08:18:04.852667   11729 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 502 lines ...

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

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

    /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 477 lines ...
STEP: Creating a kubernetes client
Jun 12 08:21:27.411: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename topology
W0612 08:21:30.184586   25768 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Jun 12 08:21:30.184: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Jun 12 08:21:30.810: INFO: found topology map[topology.kubernetes.io/zone:ap-northeast-2a]
Jun 12 08:21:30.810: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 12 08:21:30.810: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.rbyVcryct/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.rbyVcryct/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (immediate binding)] topology
    /tmp/kops.rbyVcryct/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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 167 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.rbyVcryct/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.rbyVcryct/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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 42 lines ...
STEP: Creating a kubernetes client
Jun 12 08:21:27.103: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename volumemode
W0612 08:21:28.134723   25647 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Jun 12 08:21:28.134: 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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 12 08:21:28.457: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 12 08:21:28.457: INFO: Creating resource for dynamic PV
Jun 12 08:21:28.457: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-5781hpbfs
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 12 08:21:37.598: INFO: Deleting pod "pod-21dd568d-79f4-4108-91ca-9388e16af42a" in namespace "volumemode-5781"
Jun 12 08:21:37.767: INFO: Wait up to 5m0s for pod "pod-21dd568d-79f4-4108-91ca-9388e16af42a" to be fully deleted
STEP: Deleting pvc
Jun 12 08:21:44.428: INFO: Deleting PersistentVolumeClaim "awsch8xm"
Jun 12 08:21:44.623: INFO: Waiting up to 5m0s for PersistentVolume pvc-92c6b641-b597-47c0-8106-69bd4af6496b to get deleted
Jun 12 08:21:44.785: INFO: PersistentVolume pvc-92c6b641-b597-47c0-8106-69bd4af6496b found and phase=Released (161.889969ms)
... skipping 10 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.rbyVcryct/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.rbyVcryct/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (block volmode)] volumeMode
    /tmp/kops.rbyVcryct/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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 12 08:21:55.766: INFO: Driver "ebs.csi.aws.com" does not support volume type "InlineVolume" - skipping
[AfterEach] [Testpattern: Inline-volume (default fs)] subPath
... skipping 86 lines ...
STEP: Creating a kubernetes client
Jun 12 08:21:27.340: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename volumemode
W0612 08:21:28.686114   25719 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Jun 12 08:21:28.686: 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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 12 08:21:28.999: INFO: Creating resource for dynamic PV
Jun 12 08:21:28.999: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-6701-e2e-sc5pq59
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 12 08:21:38.111: INFO: Deleting pod "pod-bb76e497-4358-47c9-a4bb-d086d1663cb0" in namespace "volumemode-6701"
Jun 12 08:21:38.271: INFO: Wait up to 5m0s for pod "pod-bb76e497-4358-47c9-a4bb-d086d1663cb0" to be fully deleted
STEP: Deleting pvc
Jun 12 08:21:50.906: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comxqd98"
Jun 12 08:21:51.063: INFO: Waiting up to 5m0s for PersistentVolume pvc-7134eaf4-1214-48a8-97d7-366dc782f071 to get deleted
Jun 12 08:21:51.221: INFO: PersistentVolume pvc-7134eaf4-1214-48a8-97d7-366dc782f071 found and phase=Released (156.9888ms)
... skipping 7 lines ...

• [SLOW TEST:29.688 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.rbyVcryct/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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] volume-expand
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] volume-expand
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 10 lines ...
Jun 12 08:21:28.405: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-4406l2m8v
STEP: creating a claim
Jun 12 08:21:28.563: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Jun 12 08:21:28.884: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 12 08:21:29.222: INFO: Error updating pvc awst9cn4: PersistentVolumeClaim "awst9cn4" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4406l2m8v",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun 12 08:21:59.856: INFO: Error updating pvc awst9cn4: PersistentVolumeClaim "awst9cn4" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 43 lines ...
Jun 12 08:21:29.096: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-3712-e2e-sclf4g5
STEP: creating a claim
Jun 12 08:21:29.261: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-pmpx
STEP: Creating a pod to test exec-volume-test
Jun 12 08:21:29.734: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-pmpx" in namespace "volume-3712" to be "Succeeded or Failed"
Jun 12 08:21:29.891: INFO: Pod "exec-volume-test-dynamicpv-pmpx": Phase="Pending", Reason="", readiness=false. Elapsed: 156.184034ms
Jun 12 08:21:32.048: INFO: Pod "exec-volume-test-dynamicpv-pmpx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.313652378s
Jun 12 08:21:34.206: INFO: Pod "exec-volume-test-dynamicpv-pmpx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.471635928s
Jun 12 08:21:36.367: INFO: Pod "exec-volume-test-dynamicpv-pmpx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.632620062s
Jun 12 08:21:38.524: INFO: Pod "exec-volume-test-dynamicpv-pmpx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.7898195s
Jun 12 08:21:40.683: INFO: Pod "exec-volume-test-dynamicpv-pmpx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.948091462s
Jun 12 08:21:42.840: INFO: Pod "exec-volume-test-dynamicpv-pmpx": Phase="Pending", Reason="", readiness=false. Elapsed: 13.105135968s
Jun 12 08:21:44.997: INFO: Pod "exec-volume-test-dynamicpv-pmpx": Phase="Pending", Reason="", readiness=false. Elapsed: 15.262011088s
Jun 12 08:21:47.154: INFO: Pod "exec-volume-test-dynamicpv-pmpx": Phase="Pending", Reason="", readiness=false. Elapsed: 17.4198875s
Jun 12 08:21:49.312: INFO: Pod "exec-volume-test-dynamicpv-pmpx": Phase="Pending", Reason="", readiness=false. Elapsed: 19.57792063s
Jun 12 08:21:51.469: INFO: Pod "exec-volume-test-dynamicpv-pmpx": Phase="Pending", Reason="", readiness=false. Elapsed: 21.734445964s
Jun 12 08:21:53.626: INFO: Pod "exec-volume-test-dynamicpv-pmpx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.89146681s
STEP: Saw pod success
Jun 12 08:21:53.626: INFO: Pod "exec-volume-test-dynamicpv-pmpx" satisfied condition "Succeeded or Failed"
Jun 12 08:21:53.783: INFO: Trying to get logs from node ip-172-20-55-5.ap-northeast-2.compute.internal pod exec-volume-test-dynamicpv-pmpx container exec-container-dynamicpv-pmpx: <nil>
STEP: delete the pod
Jun 12 08:21:54.122: INFO: Waiting for pod exec-volume-test-dynamicpv-pmpx to disappear
Jun 12 08:21:54.278: INFO: Pod exec-volume-test-dynamicpv-pmpx no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-pmpx
Jun 12 08:21:54.278: INFO: Deleting pod "exec-volume-test-dynamicpv-pmpx" in namespace "volume-3712"
... skipping 26 lines ...
STEP: Creating a kubernetes client
Jun 12 08:21:27.346: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename provisioning
W0612 08:21:29.343578   25591 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Jun 12 08:21:29.343: 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 file is outside the volume [Slow][LinuxOnly]
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun 12 08:21:29.660: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 12 08:21:29.660: INFO: Creating resource for dynamic PV
Jun 12 08:21:29.660: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2874zbszh
STEP: creating a claim
Jun 12 08:21:29.819: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-r4zl
STEP: Checking for subpath error in container status
Jun 12 08:22:04.621: INFO: Deleting pod "pod-subpath-test-dynamicpv-r4zl" in namespace "provisioning-2874"
Jun 12 08:22:04.784: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-r4zl" to be fully deleted
STEP: Deleting pod
Jun 12 08:22:15.102: INFO: Deleting pod "pod-subpath-test-dynamicpv-r4zl" in namespace "provisioning-2874"
STEP: Deleting pvc
Jun 12 08:22:15.580: INFO: Deleting PersistentVolumeClaim "aws56wc4"
... skipping 10 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.rbyVcryct/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.rbyVcryct/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath file is outside the volume [Slow][LinuxOnly]
      /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 12 08:21:29.556: 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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun 12 08:21:31.098: INFO: Creating resource for dynamic PV
Jun 12 08:21:31.098: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8210-e2e-sc75fv9
STEP: creating a claim
Jun 12 08:21:31.259: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-6878
STEP: Checking for subpath error in container status
Jun 12 08:21:56.066: INFO: Deleting pod "pod-subpath-test-dynamicpv-6878" in namespace "provisioning-8210"
Jun 12 08:21:56.234: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-6878" to be fully deleted
STEP: Deleting pod
Jun 12 08:22:02.554: INFO: Deleting pod "pod-subpath-test-dynamicpv-6878" in namespace "provisioning-8210"
STEP: Deleting pvc
Jun 12 08:22:03.034: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com4qsjm"
... skipping 11 lines ...

• [SLOW TEST:49.759 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath file is outside the volume [Slow][LinuxOnly]
    /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 12 08:22:19.317: INFO: Driver "ebs.csi.aws.com" does not support volume type "InlineVolume" - skipping
[AfterEach] [Testpattern: Inline-volume (default fs)] subPath
... skipping 2 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.rbyVcryct/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.rbyVcryct/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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 194 lines ...
Jun 12 08:21:32.943: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3386rxwqj
STEP: creating a claim
Jun 12 08:21:33.104: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-mbvv
STEP: Creating a pod to test subpath
Jun 12 08:21:33.593: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-mbvv" in namespace "provisioning-3386" to be "Succeeded or Failed"
Jun 12 08:21:33.755: INFO: Pod "pod-subpath-test-dynamicpv-mbvv": Phase="Pending", Reason="", readiness=false. Elapsed: 162.46084ms
Jun 12 08:21:35.917: INFO: Pod "pod-subpath-test-dynamicpv-mbvv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.324339373s
Jun 12 08:21:38.078: INFO: Pod "pod-subpath-test-dynamicpv-mbvv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.485755461s
Jun 12 08:21:40.241: INFO: Pod "pod-subpath-test-dynamicpv-mbvv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.648091845s
Jun 12 08:21:42.402: INFO: Pod "pod-subpath-test-dynamicpv-mbvv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.809702932s
Jun 12 08:21:44.565: INFO: Pod "pod-subpath-test-dynamicpv-mbvv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.97208423s
... skipping 3 lines ...
Jun 12 08:21:53.215: INFO: Pod "pod-subpath-test-dynamicpv-mbvv": Phase="Pending", Reason="", readiness=false. Elapsed: 19.621925187s
Jun 12 08:21:55.377: INFO: Pod "pod-subpath-test-dynamicpv-mbvv": Phase="Pending", Reason="", readiness=false. Elapsed: 21.784311926s
Jun 12 08:21:57.539: INFO: Pod "pod-subpath-test-dynamicpv-mbvv": Phase="Pending", Reason="", readiness=false. Elapsed: 23.945969806s
Jun 12 08:21:59.701: INFO: Pod "pod-subpath-test-dynamicpv-mbvv": Phase="Pending", Reason="", readiness=false. Elapsed: 26.108546385s
Jun 12 08:22:01.862: INFO: Pod "pod-subpath-test-dynamicpv-mbvv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 28.269830249s
STEP: Saw pod success
Jun 12 08:22:01.862: INFO: Pod "pod-subpath-test-dynamicpv-mbvv" satisfied condition "Succeeded or Failed"
Jun 12 08:22:02.029: INFO: Trying to get logs from node ip-172-20-46-122.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-mbvv container test-container-subpath-dynamicpv-mbvv: <nil>
STEP: delete the pod
Jun 12 08:22:02.369: INFO: Waiting for pod pod-subpath-test-dynamicpv-mbvv to disappear
Jun 12 08:22:02.532: INFO: Pod pod-subpath-test-dynamicpv-mbvv no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-mbvv
Jun 12 08:22:02.532: INFO: Deleting pod "pod-subpath-test-dynamicpv-mbvv" in namespace "provisioning-3386"
... skipping 52 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 12 08:21:57.030: 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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 12 08:21:57.818: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 12 08:21:58.792: INFO: Successfully created a new PD: "aws://ap-northeast-2a/vol-0d9bb87b21b191914".
Jun 12 08:21:58.793: INFO: Creating resource for pre-provisioned PV
Jun 12 08:21:58.793: INFO: Creating PVC and PV
... skipping 5 lines ...
Jun 12 08:22:03.673: INFO: PersistentVolumeClaim pvc-dgdp8 found but phase is Pending instead of Bound.
Jun 12 08:22:05.833: INFO: PersistentVolumeClaim pvc-dgdp8 found but phase is Pending instead of Bound.
Jun 12 08:22:07.992: INFO: PersistentVolumeClaim pvc-dgdp8 found and phase=Bound (8.792584111s)
Jun 12 08:22:07.992: INFO: Waiting up to 3m0s for PersistentVolume aws-pjz5h to have phase Bound
Jun 12 08:22:08.149: INFO: PersistentVolume aws-pjz5h found and phase=Bound (157.459621ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 12 08:22:11.099: INFO: Deleting pod "pod-87374b30-b238-4fc9-b820-c82acaae00b8" in namespace "volumemode-184"
Jun 12 08:22:11.259: INFO: Wait up to 5m0s for pod "pod-87374b30-b238-4fc9-b820-c82acaae00b8" to be fully deleted
STEP: Deleting pv and pvc
Jun 12 08:22:19.574: INFO: Deleting PersistentVolumeClaim "pvc-dgdp8"
Jun 12 08:22:19.732: INFO: Deleting PersistentVolume "aws-pjz5h"
Jun 12 08:22:20.160: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0d9bb87b21b191914", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d9bb87b21b191914 is currently attached to i-045954f58307d9775
	status code: 400, request id: 18907066-3252-45b5-a965-6d558c2a1147
Jun 12 08:22:25.926: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0d9bb87b21b191914", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d9bb87b21b191914 is currently attached to i-045954f58307d9775
	status code: 400, request id: 836b5433-a517-46ba-a4d8-0829a711ffbd
Jun 12 08:22:31.734: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-0d9bb87b21b191914".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 08:22:31.734: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-184" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.rbyVcryct/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.rbyVcryct/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
    /tmp/kops.rbyVcryct/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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 9 lines ...
Jun 12 08:21:29.860: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6906-e2e-sc29qlq
STEP: creating a claim
Jun 12 08:21:30.023: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-zv27
STEP: Creating a pod to test subpath
Jun 12 08:21:30.510: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-zv27" in namespace "provisioning-6906" to be "Succeeded or Failed"
Jun 12 08:21:30.670: INFO: Pod "pod-subpath-test-dynamicpv-zv27": Phase="Pending", Reason="", readiness=false. Elapsed: 160.474886ms
Jun 12 08:21:32.832: INFO: Pod "pod-subpath-test-dynamicpv-zv27": Phase="Pending", Reason="", readiness=false. Elapsed: 2.321833587s
Jun 12 08:21:34.993: INFO: Pod "pod-subpath-test-dynamicpv-zv27": Phase="Pending", Reason="", readiness=false. Elapsed: 4.482903529s
Jun 12 08:21:37.155: INFO: Pod "pod-subpath-test-dynamicpv-zv27": Phase="Pending", Reason="", readiness=false. Elapsed: 6.644795661s
Jun 12 08:21:39.316: INFO: Pod "pod-subpath-test-dynamicpv-zv27": Phase="Pending", Reason="", readiness=false. Elapsed: 8.805615454s
Jun 12 08:21:41.478: INFO: Pod "pod-subpath-test-dynamicpv-zv27": Phase="Pending", Reason="", readiness=false. Elapsed: 10.96755092s
Jun 12 08:21:43.640: INFO: Pod "pod-subpath-test-dynamicpv-zv27": Phase="Pending", Reason="", readiness=false. Elapsed: 13.129496286s
Jun 12 08:21:45.801: INFO: Pod "pod-subpath-test-dynamicpv-zv27": Phase="Pending", Reason="", readiness=false. Elapsed: 15.29147443s
Jun 12 08:21:47.962: INFO: Pod "pod-subpath-test-dynamicpv-zv27": Phase="Pending", Reason="", readiness=false. Elapsed: 17.45238855s
Jun 12 08:21:50.123: INFO: Pod "pod-subpath-test-dynamicpv-zv27": Phase="Pending", Reason="", readiness=false. Elapsed: 19.613246702s
Jun 12 08:21:52.284: INFO: Pod "pod-subpath-test-dynamicpv-zv27": Phase="Pending", Reason="", readiness=false. Elapsed: 21.774230207s
Jun 12 08:21:54.446: INFO: Pod "pod-subpath-test-dynamicpv-zv27": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.935670996s
STEP: Saw pod success
Jun 12 08:21:54.446: INFO: Pod "pod-subpath-test-dynamicpv-zv27" satisfied condition "Succeeded or Failed"
Jun 12 08:21:54.606: INFO: Trying to get logs from node ip-172-20-58-164.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-zv27 container test-container-volume-dynamicpv-zv27: <nil>
STEP: delete the pod
Jun 12 08:21:54.943: INFO: Waiting for pod pod-subpath-test-dynamicpv-zv27 to disappear
Jun 12 08:21:55.103: INFO: Pod pod-subpath-test-dynamicpv-zv27 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-zv27
Jun 12 08:21:55.103: INFO: Deleting pod "pod-subpath-test-dynamicpv-zv27" in namespace "provisioning-6906"
... skipping 233 lines ...
Jun 12 08:21:28.574: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4789jghgc
STEP: creating a claim
Jun 12 08:21:28.733: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-f52b
STEP: Creating a pod to test subpath
Jun 12 08:21:29.221: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-f52b" in namespace "provisioning-4789" to be "Succeeded or Failed"
Jun 12 08:21:29.379: INFO: Pod "pod-subpath-test-dynamicpv-f52b": Phase="Pending", Reason="", readiness=false. Elapsed: 158.364998ms
Jun 12 08:21:31.539: INFO: Pod "pod-subpath-test-dynamicpv-f52b": Phase="Pending", Reason="", readiness=false. Elapsed: 2.318002221s
Jun 12 08:21:33.699: INFO: Pod "pod-subpath-test-dynamicpv-f52b": Phase="Pending", Reason="", readiness=false. Elapsed: 4.478103592s
Jun 12 08:21:35.859: INFO: Pod "pod-subpath-test-dynamicpv-f52b": Phase="Pending", Reason="", readiness=false. Elapsed: 6.637887138s
Jun 12 08:21:38.019: INFO: Pod "pod-subpath-test-dynamicpv-f52b": Phase="Pending", Reason="", readiness=false. Elapsed: 8.797687583s
Jun 12 08:21:40.178: INFO: Pod "pod-subpath-test-dynamicpv-f52b": Phase="Pending", Reason="", readiness=false. Elapsed: 10.957092968s
... skipping 5 lines ...
Jun 12 08:21:53.137: INFO: Pod "pod-subpath-test-dynamicpv-f52b": Phase="Pending", Reason="", readiness=false. Elapsed: 23.915777123s
Jun 12 08:21:55.297: INFO: Pod "pod-subpath-test-dynamicpv-f52b": Phase="Pending", Reason="", readiness=false. Elapsed: 26.07596056s
Jun 12 08:21:57.457: INFO: Pod "pod-subpath-test-dynamicpv-f52b": Phase="Pending", Reason="", readiness=false. Elapsed: 28.235885655s
Jun 12 08:21:59.616: INFO: Pod "pod-subpath-test-dynamicpv-f52b": Phase="Pending", Reason="", readiness=false. Elapsed: 30.394595849s
Jun 12 08:22:01.775: INFO: Pod "pod-subpath-test-dynamicpv-f52b": Phase="Succeeded", Reason="", readiness=false. Elapsed: 32.554102706s
STEP: Saw pod success
Jun 12 08:22:01.775: INFO: Pod "pod-subpath-test-dynamicpv-f52b" satisfied condition "Succeeded or Failed"
Jun 12 08:22:01.935: INFO: Trying to get logs from node ip-172-20-55-5.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-f52b container test-container-subpath-dynamicpv-f52b: <nil>
STEP: delete the pod
Jun 12 08:22:02.260: INFO: Waiting for pod pod-subpath-test-dynamicpv-f52b to disappear
Jun 12 08:22:02.419: INFO: Pod pod-subpath-test-dynamicpv-f52b no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-f52b
Jun 12 08:22:02.419: INFO: Deleting pod "pod-subpath-test-dynamicpv-f52b" in namespace "provisioning-4789"
... skipping 86 lines ...
Jun 12 08:22:35.390: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.rbyVcryct/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.rbyVcryct/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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 13 lines ...
Jun 12 08:21:28.540: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-1720-e2e-sctkh8l
STEP: creating a claim
Jun 12 08:21:28.696: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-6njd
STEP: Creating a pod to test exec-volume-test
Jun 12 08:21:29.166: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-6njd" in namespace "volume-1720" to be "Succeeded or Failed"
Jun 12 08:21:29.323: INFO: Pod "exec-volume-test-dynamicpv-6njd": Phase="Pending", Reason="", readiness=false. Elapsed: 156.866739ms
Jun 12 08:21:31.480: INFO: Pod "exec-volume-test-dynamicpv-6njd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.314548948s
Jun 12 08:21:33.636: INFO: Pod "exec-volume-test-dynamicpv-6njd": Phase="Pending", Reason="", readiness=false. Elapsed: 4.470240357s
Jun 12 08:21:35.794: INFO: Pod "exec-volume-test-dynamicpv-6njd": Phase="Pending", Reason="", readiness=false. Elapsed: 6.628172856s
Jun 12 08:21:37.949: INFO: Pod "exec-volume-test-dynamicpv-6njd": Phase="Pending", Reason="", readiness=false. Elapsed: 8.783182009s
Jun 12 08:21:40.105: INFO: Pod "exec-volume-test-dynamicpv-6njd": Phase="Pending", Reason="", readiness=false. Elapsed: 10.939522606s
... skipping 5 lines ...
Jun 12 08:21:53.078: INFO: Pod "exec-volume-test-dynamicpv-6njd": Phase="Pending", Reason="", readiness=false. Elapsed: 23.912536218s
Jun 12 08:21:55.234: INFO: Pod "exec-volume-test-dynamicpv-6njd": Phase="Pending", Reason="", readiness=false. Elapsed: 26.068468236s
Jun 12 08:21:57.389: INFO: Pod "exec-volume-test-dynamicpv-6njd": Phase="Pending", Reason="", readiness=false. Elapsed: 28.223735489s
Jun 12 08:21:59.544: INFO: Pod "exec-volume-test-dynamicpv-6njd": Phase="Pending", Reason="", readiness=false. Elapsed: 30.378078692s
Jun 12 08:22:01.699: INFO: Pod "exec-volume-test-dynamicpv-6njd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 32.533693874s
STEP: Saw pod success
Jun 12 08:22:01.700: INFO: Pod "exec-volume-test-dynamicpv-6njd" satisfied condition "Succeeded or Failed"
Jun 12 08:22:01.854: INFO: Trying to get logs from node ip-172-20-55-5.ap-northeast-2.compute.internal pod exec-volume-test-dynamicpv-6njd container exec-container-dynamicpv-6njd: <nil>
STEP: delete the pod
Jun 12 08:22:02.186: INFO: Waiting for pod exec-volume-test-dynamicpv-6njd to disappear
Jun 12 08:22:02.340: INFO: Pod exec-volume-test-dynamicpv-6njd no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-6njd
Jun 12 08:22:02.340: INFO: Deleting pod "exec-volume-test-dynamicpv-6njd" in namespace "volume-1720"
... skipping 39 lines ...
Jun 12 08:21:30.411: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5387-e2e-scwljft
STEP: creating a claim
Jun 12 08:21:30.572: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-jtdq
STEP: Creating a pod to test subpath
Jun 12 08:21:31.059: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-jtdq" in namespace "provisioning-5387" to be "Succeeded or Failed"
Jun 12 08:21:31.219: INFO: Pod "pod-subpath-test-dynamicpv-jtdq": Phase="Pending", Reason="", readiness=false. Elapsed: 160.74349ms
Jun 12 08:21:33.384: INFO: Pod "pod-subpath-test-dynamicpv-jtdq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.324946365s
Jun 12 08:21:35.545: INFO: Pod "pod-subpath-test-dynamicpv-jtdq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.486414716s
Jun 12 08:21:37.711: INFO: Pod "pod-subpath-test-dynamicpv-jtdq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.652403798s
Jun 12 08:21:39.908: INFO: Pod "pod-subpath-test-dynamicpv-jtdq": Phase="Pending", Reason="", readiness=false. Elapsed: 8.849739537s
Jun 12 08:21:42.070: INFO: Pod "pod-subpath-test-dynamicpv-jtdq": Phase="Pending", Reason="", readiness=false. Elapsed: 11.011009823s
... skipping 4 lines ...
Jun 12 08:21:52.878: INFO: Pod "pod-subpath-test-dynamicpv-jtdq": Phase="Pending", Reason="", readiness=false. Elapsed: 21.819460697s
Jun 12 08:21:55.039: INFO: Pod "pod-subpath-test-dynamicpv-jtdq": Phase="Pending", Reason="", readiness=false. Elapsed: 23.980709131s
Jun 12 08:21:57.203: INFO: Pod "pod-subpath-test-dynamicpv-jtdq": Phase="Pending", Reason="", readiness=false. Elapsed: 26.144161975s
Jun 12 08:21:59.365: INFO: Pod "pod-subpath-test-dynamicpv-jtdq": Phase="Pending", Reason="", readiness=false. Elapsed: 28.306408373s
Jun 12 08:22:01.526: INFO: Pod "pod-subpath-test-dynamicpv-jtdq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 30.467055867s
STEP: Saw pod success
Jun 12 08:22:01.526: INFO: Pod "pod-subpath-test-dynamicpv-jtdq" satisfied condition "Succeeded or Failed"
Jun 12 08:22:01.687: INFO: Trying to get logs from node ip-172-20-55-5.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-jtdq container test-container-subpath-dynamicpv-jtdq: <nil>
STEP: delete the pod
Jun 12 08:22:02.023: INFO: Waiting for pod pod-subpath-test-dynamicpv-jtdq to disappear
Jun 12 08:22:02.190: INFO: Pod pod-subpath-test-dynamicpv-jtdq no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-jtdq
Jun 12 08:22:02.190: INFO: Deleting pod "pod-subpath-test-dynamicpv-jtdq" in namespace "provisioning-5387"
... skipping 343 lines ...
Jun 12 08:22:05.785: INFO: PersistentVolumeClaim pvc-fggf2 found but phase is Pending instead of Bound.
Jun 12 08:22:07.948: INFO: PersistentVolumeClaim pvc-fggf2 found and phase=Bound (8.81584187s)
Jun 12 08:22:07.949: INFO: Waiting up to 3m0s for PersistentVolume aws-fhgxl to have phase Bound
Jun 12 08:22:08.111: INFO: PersistentVolume aws-fhgxl found and phase=Bound (161.983869ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-nk7x
STEP: Creating a pod to test exec-volume-test
Jun 12 08:22:08.605: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-nk7x" in namespace "volume-8642" to be "Succeeded or Failed"
Jun 12 08:22:08.767: INFO: Pod "exec-volume-test-preprovisionedpv-nk7x": Phase="Pending", Reason="", readiness=false. Elapsed: 162.426447ms
Jun 12 08:22:10.930: INFO: Pod "exec-volume-test-preprovisionedpv-nk7x": Phase="Pending", Reason="", readiness=false. Elapsed: 2.324934471s
Jun 12 08:22:13.093: INFO: Pod "exec-volume-test-preprovisionedpv-nk7x": Phase="Pending", Reason="", readiness=false. Elapsed: 4.488172258s
Jun 12 08:22:15.255: INFO: Pod "exec-volume-test-preprovisionedpv-nk7x": Phase="Pending", Reason="", readiness=false. Elapsed: 6.650534754s
Jun 12 08:22:17.418: INFO: Pod "exec-volume-test-preprovisionedpv-nk7x": Phase="Pending", Reason="", readiness=false. Elapsed: 8.813014378s
Jun 12 08:22:19.580: INFO: Pod "exec-volume-test-preprovisionedpv-nk7x": Phase="Pending", Reason="", readiness=false. Elapsed: 10.975261709s
Jun 12 08:22:21.745: INFO: Pod "exec-volume-test-preprovisionedpv-nk7x": Phase="Pending", Reason="", readiness=false. Elapsed: 13.140120419s
Jun 12 08:22:23.907: INFO: Pod "exec-volume-test-preprovisionedpv-nk7x": Phase="Pending", Reason="", readiness=false. Elapsed: 15.302447792s
Jun 12 08:22:26.070: INFO: Pod "exec-volume-test-preprovisionedpv-nk7x": Phase="Pending", Reason="", readiness=false. Elapsed: 17.465067818s
Jun 12 08:22:28.232: INFO: Pod "exec-volume-test-preprovisionedpv-nk7x": Phase="Pending", Reason="", readiness=false. Elapsed: 19.627447065s
Jun 12 08:22:30.395: INFO: Pod "exec-volume-test-preprovisionedpv-nk7x": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.789735896s
STEP: Saw pod success
Jun 12 08:22:30.395: INFO: Pod "exec-volume-test-preprovisionedpv-nk7x" satisfied condition "Succeeded or Failed"
Jun 12 08:22:30.557: INFO: Trying to get logs from node ip-172-20-58-164.ap-northeast-2.compute.internal pod exec-volume-test-preprovisionedpv-nk7x container exec-container-preprovisionedpv-nk7x: <nil>
STEP: delete the pod
Jun 12 08:22:30.896: INFO: Waiting for pod exec-volume-test-preprovisionedpv-nk7x to disappear
Jun 12 08:22:31.058: INFO: Pod exec-volume-test-preprovisionedpv-nk7x no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-nk7x
Jun 12 08:22:31.058: INFO: Deleting pod "exec-volume-test-preprovisionedpv-nk7x" in namespace "volume-8642"
STEP: Deleting pv and pvc
Jun 12 08:22:31.220: INFO: Deleting PersistentVolumeClaim "pvc-fggf2"
Jun 12 08:22:31.383: INFO: Deleting PersistentVolume "aws-fhgxl"
Jun 12 08:22:31.951: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-07990d233da62c803", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07990d233da62c803 is currently attached to i-045954f58307d9775
	status code: 400, request id: 8696d385-cf50-41fe-b2c2-38c0a954cd55
Jun 12 08:22:37.735: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-07990d233da62c803", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07990d233da62c803 is currently attached to i-045954f58307d9775
	status code: 400, request id: 8bcff8f4-2785-4316-a305-f3499e0c298c
Jun 12 08:22:43.524: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-07990d233da62c803", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07990d233da62c803 is currently attached to i-045954f58307d9775
	status code: 400, request id: 0e434b41-7b81-46fa-be2c-2f6a1f6a460a
Jun 12 08:22:49.300: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-07990d233da62c803", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07990d233da62c803 is currently attached to i-045954f58307d9775
	status code: 400, request id: 21241287-91ee-476a-9382-355b7a4a494e
Jun 12 08:22:55.109: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-07990d233da62c803".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 08:22:55.109: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8642" for this suite.
... skipping 64 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.rbyVcryct/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.rbyVcryct/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.rbyVcryct/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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 65 lines ...
Jun 12 08:21:32.071: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9335-e2e-scjnvpm
STEP: creating a claim
Jun 12 08:21:32.230: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-sbp7
STEP: Creating a pod to test subpath
Jun 12 08:21:32.709: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-sbp7" in namespace "provisioning-9335" to be "Succeeded or Failed"
Jun 12 08:21:32.866: INFO: Pod "pod-subpath-test-dynamicpv-sbp7": Phase="Pending", Reason="", readiness=false. Elapsed: 156.368808ms
Jun 12 08:21:35.022: INFO: Pod "pod-subpath-test-dynamicpv-sbp7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.313118561s
Jun 12 08:21:37.180: INFO: Pod "pod-subpath-test-dynamicpv-sbp7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.470482524s
Jun 12 08:21:39.337: INFO: Pod "pod-subpath-test-dynamicpv-sbp7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.627965148s
Jun 12 08:21:41.495: INFO: Pod "pod-subpath-test-dynamicpv-sbp7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.785447771s
Jun 12 08:21:43.655: INFO: Pod "pod-subpath-test-dynamicpv-sbp7": Phase="Pending", Reason="", readiness=false. Elapsed: 10.946251243s
... skipping 4 lines ...
Jun 12 08:21:54.441: INFO: Pod "pod-subpath-test-dynamicpv-sbp7": Phase="Pending", Reason="", readiness=false. Elapsed: 21.732315518s
Jun 12 08:21:56.606: INFO: Pod "pod-subpath-test-dynamicpv-sbp7": Phase="Pending", Reason="", readiness=false. Elapsed: 23.896800947s
Jun 12 08:21:58.763: INFO: Pod "pod-subpath-test-dynamicpv-sbp7": Phase="Pending", Reason="", readiness=false. Elapsed: 26.053508258s
Jun 12 08:22:00.921: INFO: Pod "pod-subpath-test-dynamicpv-sbp7": Phase="Pending", Reason="", readiness=false. Elapsed: 28.211807014s
Jun 12 08:22:03.077: INFO: Pod "pod-subpath-test-dynamicpv-sbp7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 30.368167618s
STEP: Saw pod success
Jun 12 08:22:03.077: INFO: Pod "pod-subpath-test-dynamicpv-sbp7" satisfied condition "Succeeded or Failed"
Jun 12 08:22:03.245: INFO: Trying to get logs from node ip-172-20-33-120.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-sbp7 container test-container-subpath-dynamicpv-sbp7: <nil>
STEP: delete the pod
Jun 12 08:22:03.567: INFO: Waiting for pod pod-subpath-test-dynamicpv-sbp7 to disappear
Jun 12 08:22:03.724: INFO: Pod pod-subpath-test-dynamicpv-sbp7 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-sbp7
Jun 12 08:22:03.724: INFO: Deleting pod "pod-subpath-test-dynamicpv-sbp7" in namespace "provisioning-9335"
STEP: Creating pod pod-subpath-test-dynamicpv-sbp7
STEP: Creating a pod to test subpath
Jun 12 08:22:04.052: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-sbp7" in namespace "provisioning-9335" to be "Succeeded or Failed"
Jun 12 08:22:04.209: INFO: Pod "pod-subpath-test-dynamicpv-sbp7": Phase="Pending", Reason="", readiness=false. Elapsed: 156.942583ms
Jun 12 08:22:06.371: INFO: Pod "pod-subpath-test-dynamicpv-sbp7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.319047687s
Jun 12 08:22:08.528: INFO: Pod "pod-subpath-test-dynamicpv-sbp7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.476363092s
Jun 12 08:22:10.685: INFO: Pod "pod-subpath-test-dynamicpv-sbp7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.633794361s
Jun 12 08:22:12.842: INFO: Pod "pod-subpath-test-dynamicpv-sbp7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.790743285s
Jun 12 08:22:14.999: INFO: Pod "pod-subpath-test-dynamicpv-sbp7": Phase="Pending", Reason="", readiness=false. Elapsed: 10.947362293s
... skipping 7 lines ...
Jun 12 08:22:32.273: INFO: Pod "pod-subpath-test-dynamicpv-sbp7": Phase="Pending", Reason="", readiness=false. Elapsed: 28.220906675s
Jun 12 08:22:34.429: INFO: Pod "pod-subpath-test-dynamicpv-sbp7": Phase="Pending", Reason="", readiness=false. Elapsed: 30.377165146s
Jun 12 08:22:36.585: INFO: Pod "pod-subpath-test-dynamicpv-sbp7": Phase="Pending", Reason="", readiness=false. Elapsed: 32.533487033s
Jun 12 08:22:38.742: INFO: Pod "pod-subpath-test-dynamicpv-sbp7": Phase="Pending", Reason="", readiness=false. Elapsed: 34.690093963s
Jun 12 08:22:40.902: INFO: Pod "pod-subpath-test-dynamicpv-sbp7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 36.849896692s
STEP: Saw pod success
Jun 12 08:22:40.902: INFO: Pod "pod-subpath-test-dynamicpv-sbp7" satisfied condition "Succeeded or Failed"
Jun 12 08:22:41.058: INFO: Trying to get logs from node ip-172-20-55-5.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-sbp7 container test-container-subpath-dynamicpv-sbp7: <nil>
STEP: delete the pod
Jun 12 08:22:41.385: INFO: Waiting for pod pod-subpath-test-dynamicpv-sbp7 to disappear
Jun 12 08:22:41.541: INFO: Pod pod-subpath-test-dynamicpv-sbp7 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-sbp7
Jun 12 08:22:41.541: INFO: Deleting pod "pod-subpath-test-dynamicpv-sbp7" in namespace "provisioning-9335"
... skipping 75 lines ...
Jun 12 08:21:31.400: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-62832cj45      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-6283    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-62832cj45,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-6283    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-62832cj45,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-6283    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-62832cj45,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-62832cj45    0faa3322-f423-4105-9311-082d97ae6397 2514 0 2021-06-12 08:21:31 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-12 08:21:31 +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-r7bkz pvc- provisioning-6283  eddd638f-5c6b-4249-9277-ee922d8a3ba3 2530 0 2021-06-12 08:21:32 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-12 08:21:32 +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-62832cj45,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-48b10d26-12ee-4fe0-b5bc-c5f8ced01104 in namespace provisioning-6283
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun 12 08:21:59.165: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-hnq25" in namespace "provisioning-6283" to be "Succeeded or Failed"
Jun 12 08:21:59.324: INFO: Pod "pvc-volume-tester-writer-hnq25": Phase="Pending", Reason="", readiness=false. Elapsed: 159.45796ms
Jun 12 08:22:01.484: INFO: Pod "pvc-volume-tester-writer-hnq25": Phase="Pending", Reason="", readiness=false. Elapsed: 2.319172482s
Jun 12 08:22:03.645: INFO: Pod "pvc-volume-tester-writer-hnq25": Phase="Pending", Reason="", readiness=false. Elapsed: 4.480216419s
Jun 12 08:22:05.805: INFO: Pod "pvc-volume-tester-writer-hnq25": Phase="Pending", Reason="", readiness=false. Elapsed: 6.639964155s
Jun 12 08:22:07.965: INFO: Pod "pvc-volume-tester-writer-hnq25": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.80000508s
STEP: Saw pod success
Jun 12 08:22:07.965: INFO: Pod "pvc-volume-tester-writer-hnq25" satisfied condition "Succeeded or Failed"
Jun 12 08:22:08.285: INFO: Pod pvc-volume-tester-writer-hnq25 has the following logs: 
Jun 12 08:22:08.285: INFO: Deleting pod "pvc-volume-tester-writer-hnq25" in namespace "provisioning-6283"
Jun 12 08:22:08.453: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-hnq25" 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-58-164.ap-northeast-2.compute.internal"
Jun 12 08:22:09.101: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-h2qbz" in namespace "provisioning-6283" to be "Succeeded or Failed"
Jun 12 08:22:09.260: INFO: Pod "pvc-volume-tester-reader-h2qbz": Phase="Pending", Reason="", readiness=false. Elapsed: 159.721023ms
Jun 12 08:22:11.423: INFO: Pod "pvc-volume-tester-reader-h2qbz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.322040462s
Jun 12 08:22:13.582: INFO: Pod "pvc-volume-tester-reader-h2qbz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.481583404s
Jun 12 08:22:15.747: INFO: Pod "pvc-volume-tester-reader-h2qbz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.645875619s
Jun 12 08:22:17.907: INFO: Pod "pvc-volume-tester-reader-h2qbz": Phase="Pending", Reason="", readiness=false. Elapsed: 8.80632175s
Jun 12 08:22:20.068: INFO: Pod "pvc-volume-tester-reader-h2qbz": Phase="Pending", Reason="", readiness=false. Elapsed: 10.96687061s
Jun 12 08:22:22.227: INFO: Pod "pvc-volume-tester-reader-h2qbz": Phase="Pending", Reason="", readiness=false. Elapsed: 13.126807003s
Jun 12 08:22:24.390: INFO: Pod "pvc-volume-tester-reader-h2qbz": Phase="Pending", Reason="", readiness=false. Elapsed: 15.289104315s
Jun 12 08:22:26.554: INFO: Pod "pvc-volume-tester-reader-h2qbz": Phase="Pending", Reason="", readiness=false. Elapsed: 17.453452096s
Jun 12 08:22:28.716: INFO: Pod "pvc-volume-tester-reader-h2qbz": Phase="Pending", Reason="", readiness=false. Elapsed: 19.615548254s
Jun 12 08:22:30.877: INFO: Pod "pvc-volume-tester-reader-h2qbz": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.776343692s
STEP: Saw pod success
Jun 12 08:22:30.877: INFO: Pod "pvc-volume-tester-reader-h2qbz" satisfied condition "Succeeded or Failed"
Jun 12 08:22:31.198: INFO: Pod pvc-volume-tester-reader-h2qbz has the following logs: hello world

Jun 12 08:22:31.198: INFO: Deleting pod "pvc-volume-tester-reader-h2qbz" in namespace "provisioning-6283"
Jun 12 08:22:31.367: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-h2qbz" to be fully deleted
Jun 12 08:22:31.529: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-r7bkz] to have phase Bound
Jun 12 08:22:31.689: INFO: PersistentVolumeClaim pvc-r7bkz found and phase=Bound (159.410241ms)
... skipping 224 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.rbyVcryct/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.rbyVcryct/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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 69 lines ...
Jun 12 08:22:21.063: INFO: PersistentVolumeClaim pvc-n9mpw found but phase is Pending instead of Bound.
Jun 12 08:22:23.222: INFO: PersistentVolumeClaim pvc-n9mpw found and phase=Bound (4.477115809s)
Jun 12 08:22:23.223: INFO: Waiting up to 3m0s for PersistentVolume aws-w8b79 to have phase Bound
Jun 12 08:22:23.381: INFO: PersistentVolume aws-w8b79 found and phase=Bound (158.72105ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-w25t
STEP: Creating a pod to test exec-volume-test
Jun 12 08:22:23.859: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-w25t" in namespace "volume-585" to be "Succeeded or Failed"
Jun 12 08:22:24.018: INFO: Pod "exec-volume-test-preprovisionedpv-w25t": Phase="Pending", Reason="", readiness=false. Elapsed: 158.769016ms
Jun 12 08:22:26.178: INFO: Pod "exec-volume-test-preprovisionedpv-w25t": Phase="Pending", Reason="", readiness=false. Elapsed: 2.3188318s
Jun 12 08:22:28.337: INFO: Pod "exec-volume-test-preprovisionedpv-w25t": Phase="Pending", Reason="", readiness=false. Elapsed: 4.478043826s
Jun 12 08:22:30.497: INFO: Pod "exec-volume-test-preprovisionedpv-w25t": Phase="Pending", Reason="", readiness=false. Elapsed: 6.638159956s
Jun 12 08:22:32.656: INFO: Pod "exec-volume-test-preprovisionedpv-w25t": Phase="Pending", Reason="", readiness=false. Elapsed: 8.797474388s
Jun 12 08:22:34.817: INFO: Pod "exec-volume-test-preprovisionedpv-w25t": Phase="Pending", Reason="", readiness=false. Elapsed: 10.95793755s
Jun 12 08:22:36.977: INFO: Pod "exec-volume-test-preprovisionedpv-w25t": Phase="Pending", Reason="", readiness=false. Elapsed: 13.118182055s
Jun 12 08:22:39.137: INFO: Pod "exec-volume-test-preprovisionedpv-w25t": Phase="Pending", Reason="", readiness=false. Elapsed: 15.277652741s
Jun 12 08:22:41.310: INFO: Pod "exec-volume-test-preprovisionedpv-w25t": Phase="Pending", Reason="", readiness=false. Elapsed: 17.450910645s
Jun 12 08:22:43.470: INFO: Pod "exec-volume-test-preprovisionedpv-w25t": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.610794718s
STEP: Saw pod success
Jun 12 08:22:43.470: INFO: Pod "exec-volume-test-preprovisionedpv-w25t" satisfied condition "Succeeded or Failed"
Jun 12 08:22:43.629: INFO: Trying to get logs from node ip-172-20-58-164.ap-northeast-2.compute.internal pod exec-volume-test-preprovisionedpv-w25t container exec-container-preprovisionedpv-w25t: <nil>
STEP: delete the pod
Jun 12 08:22:43.957: INFO: Waiting for pod exec-volume-test-preprovisionedpv-w25t to disappear
Jun 12 08:22:44.116: INFO: Pod exec-volume-test-preprovisionedpv-w25t no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-w25t
Jun 12 08:22:44.116: INFO: Deleting pod "exec-volume-test-preprovisionedpv-w25t" in namespace "volume-585"
STEP: Deleting pv and pvc
Jun 12 08:22:44.275: INFO: Deleting PersistentVolumeClaim "pvc-n9mpw"
Jun 12 08:22:44.435: INFO: Deleting PersistentVolume "aws-w8b79"
Jun 12 08:22:44.840: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-00659c1a426b8ea7e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00659c1a426b8ea7e is currently attached to i-045954f58307d9775
	status code: 400, request id: 6d62c90d-ecb4-457a-a08d-846e7d1f90ac
Jun 12 08:22:50.639: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-00659c1a426b8ea7e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00659c1a426b8ea7e is currently attached to i-045954f58307d9775
	status code: 400, request id: 7724c2bf-e9ac-43eb-afdb-8211fd3dd9f6
Jun 12 08:22:56.435: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-00659c1a426b8ea7e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00659c1a426b8ea7e is currently attached to i-045954f58307d9775
	status code: 400, request id: 3a919401-5763-4b8d-9633-69c17757a9a7
Jun 12 08:23:02.233: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-00659c1a426b8ea7e".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 08:23:02.233: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-585" for this suite.
... skipping 326 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.rbyVcryct/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.rbyVcryct/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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 108 lines ...
Jun 12 08:22:22.441: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-19826pq7g
STEP: creating a claim
Jun 12 08:22:22.599: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-9rrk
STEP: Creating a pod to test subpath
Jun 12 08:22:23.076: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-9rrk" in namespace "provisioning-1982" to be "Succeeded or Failed"
Jun 12 08:22:23.234: INFO: Pod "pod-subpath-test-dynamicpv-9rrk": Phase="Pending", Reason="", readiness=false. Elapsed: 157.646429ms
Jun 12 08:22:25.393: INFO: Pod "pod-subpath-test-dynamicpv-9rrk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.316418738s
Jun 12 08:22:27.552: INFO: Pod "pod-subpath-test-dynamicpv-9rrk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.475899791s
Jun 12 08:22:29.712: INFO: Pod "pod-subpath-test-dynamicpv-9rrk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.636281157s
Jun 12 08:22:31.876: INFO: Pod "pod-subpath-test-dynamicpv-9rrk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.799503567s
Jun 12 08:22:34.034: INFO: Pod "pod-subpath-test-dynamicpv-9rrk": Phase="Pending", Reason="", readiness=false. Elapsed: 10.957955866s
Jun 12 08:22:36.194: INFO: Pod "pod-subpath-test-dynamicpv-9rrk": Phase="Pending", Reason="", readiness=false. Elapsed: 13.117374824s
Jun 12 08:22:38.352: INFO: Pod "pod-subpath-test-dynamicpv-9rrk": Phase="Pending", Reason="", readiness=false. Elapsed: 15.276077998s
Jun 12 08:22:40.510: INFO: Pod "pod-subpath-test-dynamicpv-9rrk": Phase="Pending", Reason="", readiness=false. Elapsed: 17.434065883s
Jun 12 08:22:42.669: INFO: Pod "pod-subpath-test-dynamicpv-9rrk": Phase="Pending", Reason="", readiness=false. Elapsed: 19.593138128s
Jun 12 08:22:44.829: INFO: Pod "pod-subpath-test-dynamicpv-9rrk": Phase="Pending", Reason="", readiness=false. Elapsed: 21.75237635s
Jun 12 08:22:46.987: INFO: Pod "pod-subpath-test-dynamicpv-9rrk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.91070899s
STEP: Saw pod success
Jun 12 08:22:46.987: INFO: Pod "pod-subpath-test-dynamicpv-9rrk" satisfied condition "Succeeded or Failed"
Jun 12 08:22:47.145: INFO: Trying to get logs from node ip-172-20-58-164.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-9rrk container test-container-subpath-dynamicpv-9rrk: <nil>
STEP: delete the pod
Jun 12 08:22:47.468: INFO: Waiting for pod pod-subpath-test-dynamicpv-9rrk to disappear
Jun 12 08:22:47.626: INFO: Pod pod-subpath-test-dynamicpv-9rrk no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-9rrk
Jun 12 08:22:47.626: INFO: Deleting pod "pod-subpath-test-dynamicpv-9rrk" in namespace "provisioning-1982"
... skipping 239 lines ...
Jun 12 08:22:41.906: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6929-e2e-scl29hv
STEP: creating a claim
Jun 12 08:22:42.068: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-mldr
STEP: Creating a pod to test subpath
Jun 12 08:22:42.554: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-mldr" in namespace "provisioning-6929" to be "Succeeded or Failed"
Jun 12 08:22:42.715: INFO: Pod "pod-subpath-test-dynamicpv-mldr": Phase="Pending", Reason="", readiness=false. Elapsed: 160.925038ms
Jun 12 08:22:44.876: INFO: Pod "pod-subpath-test-dynamicpv-mldr": Phase="Pending", Reason="", readiness=false. Elapsed: 2.322593106s
Jun 12 08:22:47.038: INFO: Pod "pod-subpath-test-dynamicpv-mldr": Phase="Pending", Reason="", readiness=false. Elapsed: 4.484490592s
Jun 12 08:22:49.199: INFO: Pod "pod-subpath-test-dynamicpv-mldr": Phase="Pending", Reason="", readiness=false. Elapsed: 6.645366815s
Jun 12 08:22:51.361: INFO: Pod "pod-subpath-test-dynamicpv-mldr": Phase="Pending", Reason="", readiness=false. Elapsed: 8.806603446s
Jun 12 08:22:53.521: INFO: Pod "pod-subpath-test-dynamicpv-mldr": Phase="Pending", Reason="", readiness=false. Elapsed: 10.967546048s
... skipping 2 lines ...
Jun 12 08:23:00.009: INFO: Pod "pod-subpath-test-dynamicpv-mldr": Phase="Pending", Reason="", readiness=false. Elapsed: 17.455055631s
Jun 12 08:23:02.171: INFO: Pod "pod-subpath-test-dynamicpv-mldr": Phase="Pending", Reason="", readiness=false. Elapsed: 19.61668306s
Jun 12 08:23:04.332: INFO: Pod "pod-subpath-test-dynamicpv-mldr": Phase="Pending", Reason="", readiness=false. Elapsed: 21.778186654s
Jun 12 08:23:06.495: INFO: Pod "pod-subpath-test-dynamicpv-mldr": Phase="Pending", Reason="", readiness=false. Elapsed: 23.940970046s
Jun 12 08:23:08.657: INFO: Pod "pod-subpath-test-dynamicpv-mldr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.103089738s
STEP: Saw pod success
Jun 12 08:23:08.657: INFO: Pod "pod-subpath-test-dynamicpv-mldr" satisfied condition "Succeeded or Failed"
Jun 12 08:23:08.818: INFO: Trying to get logs from node ip-172-20-58-164.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-mldr container test-container-subpath-dynamicpv-mldr: <nil>
STEP: delete the pod
Jun 12 08:23:09.147: INFO: Waiting for pod pod-subpath-test-dynamicpv-mldr to disappear
Jun 12 08:23:09.307: INFO: Pod pod-subpath-test-dynamicpv-mldr no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-mldr
Jun 12 08:23:09.307: INFO: Deleting pod "pod-subpath-test-dynamicpv-mldr" in namespace "provisioning-6929"
... skipping 49 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.rbyVcryct/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.rbyVcryct/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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 140 lines ...
Jun 12 08:22:01.602: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 12 08:22:02.588: INFO: Successfully created a new PD: "aws://ap-northeast-2a/vol-002ca2d95d8186c3c".
Jun 12 08:22:02.588: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-zn2v
STEP: Creating a pod to test exec-volume-test
Jun 12 08:22:02.749: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-zn2v" in namespace "volume-2060" to be "Succeeded or Failed"
Jun 12 08:22:02.909: INFO: Pod "exec-volume-test-inlinevolume-zn2v": Phase="Pending", Reason="", readiness=false. Elapsed: 160.01704ms
Jun 12 08:22:05.068: INFO: Pod "exec-volume-test-inlinevolume-zn2v": Phase="Pending", Reason="", readiness=false. Elapsed: 2.318845546s
Jun 12 08:22:07.226: INFO: Pod "exec-volume-test-inlinevolume-zn2v": Phase="Pending", Reason="", readiness=false. Elapsed: 4.476902074s
Jun 12 08:22:09.385: INFO: Pod "exec-volume-test-inlinevolume-zn2v": Phase="Pending", Reason="", readiness=false. Elapsed: 6.635172053s
Jun 12 08:22:11.543: INFO: Pod "exec-volume-test-inlinevolume-zn2v": Phase="Pending", Reason="", readiness=false. Elapsed: 8.793504218s
Jun 12 08:22:13.701: INFO: Pod "exec-volume-test-inlinevolume-zn2v": Phase="Pending", Reason="", readiness=false. Elapsed: 10.951617934s
... skipping 21 lines ...
Jun 12 08:23:01.190: INFO: Pod "exec-volume-test-inlinevolume-zn2v": Phase="Pending", Reason="", readiness=false. Elapsed: 58.44072122s
Jun 12 08:23:03.349: INFO: Pod "exec-volume-test-inlinevolume-zn2v": Phase="Pending", Reason="", readiness=false. Elapsed: 1m0.599917823s
Jun 12 08:23:05.507: INFO: Pod "exec-volume-test-inlinevolume-zn2v": Phase="Pending", Reason="", readiness=false. Elapsed: 1m2.757748953s
Jun 12 08:23:07.668: INFO: Pod "exec-volume-test-inlinevolume-zn2v": Phase="Pending", Reason="", readiness=false. Elapsed: 1m4.918270265s
Jun 12 08:23:09.827: INFO: Pod "exec-volume-test-inlinevolume-zn2v": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m7.077378178s
STEP: Saw pod success
Jun 12 08:23:09.827: INFO: Pod "exec-volume-test-inlinevolume-zn2v" satisfied condition "Succeeded or Failed"
Jun 12 08:23:09.985: INFO: Trying to get logs from node ip-172-20-55-5.ap-northeast-2.compute.internal pod exec-volume-test-inlinevolume-zn2v container exec-container-inlinevolume-zn2v: <nil>
STEP: delete the pod
Jun 12 08:23:10.311: INFO: Waiting for pod exec-volume-test-inlinevolume-zn2v to disappear
Jun 12 08:23:10.468: INFO: Pod exec-volume-test-inlinevolume-zn2v no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-zn2v
Jun 12 08:23:10.468: INFO: Deleting pod "exec-volume-test-inlinevolume-zn2v" in namespace "volume-2060"
Jun 12 08:23:11.456: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-002ca2d95d8186c3c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-002ca2d95d8186c3c is currently attached to i-0282c044eee72f443
	status code: 400, request id: 0f84b052-efac-4c31-8ed8-4c29f240cbe3
Jun 12 08:23:17.241: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-002ca2d95d8186c3c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-002ca2d95d8186c3c is currently attached to i-0282c044eee72f443
	status code: 400, request id: ef9f8696-0dfa-445b-8472-5ed05dcf11b4
Jun 12 08:23:23.024: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-002ca2d95d8186c3c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-002ca2d95d8186c3c is currently attached to i-0282c044eee72f443
	status code: 400, request id: 90fe8afd-4736-4feb-b4a5-08b0776a798f
Jun 12 08:23:28.823: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-002ca2d95d8186c3c".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 08:23:28.823: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-2060" for this suite.
... skipping 24 lines ...
Jun 12 08:23:03.351: INFO: Creating resource for dynamic PV
Jun 12 08:23:03.351: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-5867-e2e-scf7kl6
STEP: creating a claim
STEP: Expanding non-expandable pvc
Jun 12 08:23:03.839: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 12 08:23:04.160: INFO: Error updating pvc ebs.csi.aws.commt4zm: PersistentVolumeClaim "ebs.csi.aws.commt4zm" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5867-e2e-scf7kl6",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun 12 08:23:34.801: INFO: Error updating pvc ebs.csi.aws.commt4zm: PersistentVolumeClaim "ebs.csi.aws.commt4zm" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 32 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 12 08:22:48.546: 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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun 12 08:22:49.348: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 12 08:22:49.348: INFO: Creating resource for dynamic PV
Jun 12 08:22:49.348: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-42522bsh5
STEP: creating a claim
Jun 12 08:22:49.512: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-lrdz
STEP: Checking for subpath error in container status
Jun 12 08:23:16.321: INFO: Deleting pod "pod-subpath-test-dynamicpv-lrdz" in namespace "provisioning-4252"
Jun 12 08:23:16.492: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-lrdz" to be fully deleted
STEP: Deleting pod
Jun 12 08:23:28.813: INFO: Deleting pod "pod-subpath-test-dynamicpv-lrdz" in namespace "provisioning-4252"
STEP: Deleting pvc
Jun 12 08:23:29.300: INFO: Deleting PersistentVolumeClaim "aws8llps"
... skipping 13 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.rbyVcryct/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.rbyVcryct/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.rbyVcryct/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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] capacity
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 12 08:23:45.602: INFO: Driver ebs.csi.aws.com doesn't publish storage capacity -- skipping
[AfterEach] [Testpattern: Dynamic PV (default fs)] capacity
... skipping 124 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.rbyVcryct/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.rbyVcryct/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.rbyVcryct/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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 435 lines ...
Jun 12 08:23:39.921: INFO: Waiting for pod aws-client to disappear
Jun 12 08:23:40.080: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 12 08:23:40.080: INFO: Deleting PersistentVolumeClaim "pvc-hj8kd"
Jun 12 08:23:40.240: INFO: Deleting PersistentVolume "aws-68jgh"
Jun 12 08:23:41.176: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0837126ab4447dc92", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0837126ab4447dc92 is currently attached to i-0bbfca73506739cca
	status code: 400, request id: 7acadeec-2c35-46b7-b98f-78f688abd42a
Jun 12 08:23:46.934: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0837126ab4447dc92", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0837126ab4447dc92 is currently attached to i-0bbfca73506739cca
	status code: 400, request id: 3bdbc797-c5a7-4362-bdb8-826b70f4a303
Jun 12 08:23:52.694: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0837126ab4447dc92", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0837126ab4447dc92 is currently attached to i-0bbfca73506739cca
	status code: 400, request id: 8bbb9808-682b-4132-99a4-d77984b4bdf5
Jun 12 08:23:58.525: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0837126ab4447dc92", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0837126ab4447dc92 is currently attached to i-0bbfca73506739cca
	status code: 400, request id: bbba828c-1ef8-4392-8c4b-1ccc8db051de
Jun 12 08:24:04.428: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-0837126ab4447dc92".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumes
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 08:24:04.428: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-3138" for this suite.
... skipping 20 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.rbyVcryct/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.rbyVcryct/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.rbyVcryct/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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 29 lines ...
Jun 12 08:23:23.549: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 12 08:23:24.537: INFO: Successfully created a new PD: "aws://ap-northeast-2a/vol-00667d651a743781d".
Jun 12 08:23:24.537: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-l2gq
STEP: Creating a pod to test exec-volume-test
Jun 12 08:23:24.693: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-l2gq" in namespace "volume-2406" to be "Succeeded or Failed"
Jun 12 08:23:24.848: INFO: Pod "exec-volume-test-inlinevolume-l2gq": Phase="Pending", Reason="", readiness=false. Elapsed: 154.129491ms
Jun 12 08:23:27.003: INFO: Pod "exec-volume-test-inlinevolume-l2gq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.309589389s
Jun 12 08:23:29.157: INFO: Pod "exec-volume-test-inlinevolume-l2gq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.463952989s
Jun 12 08:23:31.313: INFO: Pod "exec-volume-test-inlinevolume-l2gq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.619233438s
Jun 12 08:23:33.468: INFO: Pod "exec-volume-test-inlinevolume-l2gq": Phase="Pending", Reason="", readiness=false. Elapsed: 8.774111603s
Jun 12 08:23:35.624: INFO: Pod "exec-volume-test-inlinevolume-l2gq": Phase="Pending", Reason="", readiness=false. Elapsed: 10.930976297s
Jun 12 08:23:37.780: INFO: Pod "exec-volume-test-inlinevolume-l2gq": Phase="Pending", Reason="", readiness=false. Elapsed: 13.086255108s
Jun 12 08:23:39.934: INFO: Pod "exec-volume-test-inlinevolume-l2gq": Phase="Pending", Reason="", readiness=false. Elapsed: 15.240502788s
Jun 12 08:23:42.089: INFO: Pod "exec-volume-test-inlinevolume-l2gq": Phase="Pending", Reason="", readiness=false. Elapsed: 17.395894838s
Jun 12 08:23:44.245: INFO: Pod "exec-volume-test-inlinevolume-l2gq": Phase="Pending", Reason="", readiness=false. Elapsed: 19.551249679s
Jun 12 08:23:46.400: INFO: Pod "exec-volume-test-inlinevolume-l2gq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.706713117s
STEP: Saw pod success
Jun 12 08:23:46.400: INFO: Pod "exec-volume-test-inlinevolume-l2gq" satisfied condition "Succeeded or Failed"
Jun 12 08:23:46.555: INFO: Trying to get logs from node ip-172-20-33-120.ap-northeast-2.compute.internal pod exec-volume-test-inlinevolume-l2gq container exec-container-inlinevolume-l2gq: <nil>
STEP: delete the pod
Jun 12 08:23:46.882: INFO: Waiting for pod exec-volume-test-inlinevolume-l2gq to disappear
Jun 12 08:23:47.036: INFO: Pod exec-volume-test-inlinevolume-l2gq no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-l2gq
Jun 12 08:23:47.036: INFO: Deleting pod "exec-volume-test-inlinevolume-l2gq" in namespace "volume-2406"
Jun 12 08:23:47.437: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-00667d651a743781d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00667d651a743781d is currently attached to i-0ba3e9a7fe85e3ae4
	status code: 400, request id: c336615b-2701-44f6-aecd-4f56e3187c2e
Jun 12 08:23:53.182: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-00667d651a743781d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00667d651a743781d is currently attached to i-0ba3e9a7fe85e3ae4
	status code: 400, request id: 9d19fa27-d701-4277-8ab3-fc194d2f4466
Jun 12 08:23:58.924: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-00667d651a743781d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00667d651a743781d is currently attached to i-0ba3e9a7fe85e3ae4
	status code: 400, request id: 5146f2b3-c715-4078-a4f2-b0b84e8a90c5
Jun 12 08:24:04.735: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-00667d651a743781d".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 08:24:04.735: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-2406" for this suite.
... skipping 24 lines ...
Jun 12 08:23:02.799: INFO: Creating resource for dynamic PV
Jun 12 08:23:02.799: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-139-e2e-scj7fr5
STEP: creating a claim
Jun 12 08:23:02.961: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-139
Jun 12 08:23:03.445: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-139" in namespace "provisioning-139" to be "Succeeded or Failed"
Jun 12 08:23:03.603: INFO: Pod "volume-prep-provisioning-139": Phase="Pending", Reason="", readiness=false. Elapsed: 157.423566ms
Jun 12 08:23:05.760: INFO: Pod "volume-prep-provisioning-139": Phase="Pending", Reason="", readiness=false. Elapsed: 2.314616438s
Jun 12 08:23:07.918: INFO: Pod "volume-prep-provisioning-139": Phase="Pending", Reason="", readiness=false. Elapsed: 4.472190072s
Jun 12 08:23:10.076: INFO: Pod "volume-prep-provisioning-139": Phase="Pending", Reason="", readiness=false. Elapsed: 6.630514537s
Jun 12 08:23:12.233: INFO: Pod "volume-prep-provisioning-139": Phase="Pending", Reason="", readiness=false. Elapsed: 8.787639425s
Jun 12 08:23:14.392: INFO: Pod "volume-prep-provisioning-139": Phase="Pending", Reason="", readiness=false. Elapsed: 10.946906497s
Jun 12 08:23:16.554: INFO: Pod "volume-prep-provisioning-139": Phase="Pending", Reason="", readiness=false. Elapsed: 13.108761429s
Jun 12 08:23:18.713: INFO: Pod "volume-prep-provisioning-139": Phase="Pending", Reason="", readiness=false. Elapsed: 15.267211055s
Jun 12 08:23:20.871: INFO: Pod "volume-prep-provisioning-139": Phase="Pending", Reason="", readiness=false. Elapsed: 17.425600163s
Jun 12 08:23:23.030: INFO: Pod "volume-prep-provisioning-139": Phase="Pending", Reason="", readiness=false. Elapsed: 19.584911439s
Jun 12 08:23:25.191: INFO: Pod "volume-prep-provisioning-139": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.745230528s
STEP: Saw pod success
Jun 12 08:23:25.191: INFO: Pod "volume-prep-provisioning-139" satisfied condition "Succeeded or Failed"
Jun 12 08:23:25.191: INFO: Deleting pod "volume-prep-provisioning-139" in namespace "provisioning-139"
Jun 12 08:23:25.358: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-139" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-64gl
STEP: Checking for subpath error in container status
Jun 12 08:23:27.993: INFO: Deleting pod "pod-subpath-test-dynamicpv-64gl" in namespace "provisioning-139"
Jun 12 08:23:28.162: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-64gl" to be fully deleted
STEP: Deleting pod
Jun 12 08:23:28.320: INFO: Deleting pod "pod-subpath-test-dynamicpv-64gl" in namespace "provisioning-139"
STEP: Deleting pvc
Jun 12 08:23:28.791: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comdvshv"
... skipping 103 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.rbyVcryct/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.rbyVcryct/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.rbyVcryct/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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Driver supports dynamic provisioning, skipping InlineVolume pattern

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

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 949 lines ...
Jun 12 08:24:05.323: INFO: Waiting for pod aws-client to disappear
Jun 12 08:24:05.482: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 12 08:24:05.482: INFO: Deleting PersistentVolumeClaim "pvc-l4kjk"
Jun 12 08:24:05.647: INFO: Deleting PersistentVolume "aws-dqzhm"
Jun 12 08:24:06.111: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-08fca0eb8e0bc8f55", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08fca0eb8e0bc8f55 is currently attached to i-0ba3e9a7fe85e3ae4
	status code: 400, request id: 1b70441f-0a8f-4733-a1d9-3bb1aff34a24
Jun 12 08:24:11.907: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-08fca0eb8e0bc8f55", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08fca0eb8e0bc8f55 is currently attached to i-0ba3e9a7fe85e3ae4
	status code: 400, request id: ab08ab3b-0631-44dc-ab4d-16c33136c957
Jun 12 08:24:17.762: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-08fca0eb8e0bc8f55", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08fca0eb8e0bc8f55 is currently attached to i-0ba3e9a7fe85e3ae4
	status code: 400, request id: 5882f2d8-63dc-4540-a7cc-1b5546fde944
Jun 12 08:24:23.543: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-08fca0eb8e0bc8f55".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 08:24:23.543: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-6748" for this suite.
... skipping 66 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.rbyVcryct/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.rbyVcryct/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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 162 lines ...
Jun 12 08:24:03.438: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4001xr9h9
STEP: creating a claim
Jun 12 08:24:03.601: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-sqvv
STEP: Creating a pod to test subpath
Jun 12 08:24:04.092: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-sqvv" in namespace "provisioning-4001" to be "Succeeded or Failed"
Jun 12 08:24:04.254: INFO: Pod "pod-subpath-test-dynamicpv-sqvv": Phase="Pending", Reason="", readiness=false. Elapsed: 162.411134ms
Jun 12 08:24:06.423: INFO: Pod "pod-subpath-test-dynamicpv-sqvv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.331425304s
Jun 12 08:24:08.586: INFO: Pod "pod-subpath-test-dynamicpv-sqvv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.494426407s
Jun 12 08:24:10.752: INFO: Pod "pod-subpath-test-dynamicpv-sqvv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.659917566s
Jun 12 08:24:12.915: INFO: Pod "pod-subpath-test-dynamicpv-sqvv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.823636118s
Jun 12 08:24:15.078: INFO: Pod "pod-subpath-test-dynamicpv-sqvv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.986462644s
Jun 12 08:24:17.243: INFO: Pod "pod-subpath-test-dynamicpv-sqvv": Phase="Pending", Reason="", readiness=false. Elapsed: 13.151435525s
Jun 12 08:24:19.409: INFO: Pod "pod-subpath-test-dynamicpv-sqvv": Phase="Pending", Reason="", readiness=false. Elapsed: 15.317101743s
Jun 12 08:24:21.572: INFO: Pod "pod-subpath-test-dynamicpv-sqvv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 17.480089719s
STEP: Saw pod success
Jun 12 08:24:21.572: INFO: Pod "pod-subpath-test-dynamicpv-sqvv" satisfied condition "Succeeded or Failed"
Jun 12 08:24:21.736: INFO: Trying to get logs from node ip-172-20-55-5.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-sqvv container test-container-volume-dynamicpv-sqvv: <nil>
STEP: delete the pod
Jun 12 08:24:22.073: INFO: Waiting for pod pod-subpath-test-dynamicpv-sqvv to disappear
Jun 12 08:24:22.242: INFO: Pod pod-subpath-test-dynamicpv-sqvv no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-sqvv
Jun 12 08:24:22.242: INFO: Deleting pod "pod-subpath-test-dynamicpv-sqvv" in namespace "provisioning-4001"
... skipping 89 lines ...

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

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

    /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 120 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 12 08:24:08.332: 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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun 12 08:24:09.105: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 12 08:24:09.105: INFO: Creating resource for dynamic PV
Jun 12 08:24:09.105: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7249v6f2
STEP: creating a claim
Jun 12 08:24:09.263: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-bxqt
STEP: Checking for subpath error in container status
Jun 12 08:24:26.039: INFO: Deleting pod "pod-subpath-test-dynamicpv-bxqt" in namespace "provisioning-724"
Jun 12 08:24:26.197: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-bxqt" to be fully deleted
STEP: Deleting pod
Jun 12 08:24:36.506: INFO: Deleting pod "pod-subpath-test-dynamicpv-bxqt" in namespace "provisioning-724"
STEP: Deleting pvc
Jun 12 08:24:36.967: INFO: Deleting PersistentVolumeClaim "aws7j8ml"
... skipping 13 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.rbyVcryct/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.rbyVcryct/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath directory is outside the volume [Slow][LinuxOnly]
      /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 8 lines ...
Jun 12 08:24:09.381: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-90794w725
STEP: creating a claim
Jun 12 08:24:09.542: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-z5fv
STEP: Creating a pod to test subpath
Jun 12 08:24:10.043: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-z5fv" in namespace "provisioning-9079" to be "Succeeded or Failed"
Jun 12 08:24:10.204: INFO: Pod "pod-subpath-test-dynamicpv-z5fv": Phase="Pending", Reason="", readiness=false. Elapsed: 161.257414ms
Jun 12 08:24:12.367: INFO: Pod "pod-subpath-test-dynamicpv-z5fv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.323734492s
Jun 12 08:24:14.531: INFO: Pod "pod-subpath-test-dynamicpv-z5fv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.488478034s
Jun 12 08:24:16.711: INFO: Pod "pod-subpath-test-dynamicpv-z5fv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.667573521s
Jun 12 08:24:18.878: INFO: Pod "pod-subpath-test-dynamicpv-z5fv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.834611176s
Jun 12 08:24:21.041: INFO: Pod "pod-subpath-test-dynamicpv-z5fv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.998532464s
Jun 12 08:24:23.203: INFO: Pod "pod-subpath-test-dynamicpv-z5fv": Phase="Pending", Reason="", readiness=false. Elapsed: 13.159815407s
Jun 12 08:24:25.366: INFO: Pod "pod-subpath-test-dynamicpv-z5fv": Phase="Pending", Reason="", readiness=false. Elapsed: 15.323176986s
Jun 12 08:24:27.527: INFO: Pod "pod-subpath-test-dynamicpv-z5fv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 17.484257697s
STEP: Saw pod success
Jun 12 08:24:27.527: INFO: Pod "pod-subpath-test-dynamicpv-z5fv" satisfied condition "Succeeded or Failed"
Jun 12 08:24:27.689: INFO: Trying to get logs from node ip-172-20-46-122.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-z5fv container test-container-volume-dynamicpv-z5fv: <nil>
STEP: delete the pod
Jun 12 08:24:28.041: INFO: Waiting for pod pod-subpath-test-dynamicpv-z5fv to disappear
Jun 12 08:24:28.202: INFO: Pod pod-subpath-test-dynamicpv-z5fv no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-z5fv
Jun 12 08:24:28.202: INFO: Deleting pod "pod-subpath-test-dynamicpv-z5fv" in namespace "provisioning-9079"
... skipping 61 lines ...
Jun 12 08:24:17.588: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2944lnxcl
STEP: creating a claim
Jun 12 08:24:17.747: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-7h8k
STEP: Creating a pod to test multi_subpath
Jun 12 08:24:18.250: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-7h8k" in namespace "provisioning-2944" to be "Succeeded or Failed"
Jun 12 08:24:18.408: INFO: Pod "pod-subpath-test-dynamicpv-7h8k": Phase="Pending", Reason="", readiness=false. Elapsed: 158.847284ms
Jun 12 08:24:20.568: INFO: Pod "pod-subpath-test-dynamicpv-7h8k": Phase="Pending", Reason="", readiness=false. Elapsed: 2.317949553s
Jun 12 08:24:22.730: INFO: Pod "pod-subpath-test-dynamicpv-7h8k": Phase="Pending", Reason="", readiness=false. Elapsed: 4.480212156s
Jun 12 08:24:24.890: INFO: Pod "pod-subpath-test-dynamicpv-7h8k": Phase="Pending", Reason="", readiness=false. Elapsed: 6.640283648s
Jun 12 08:24:27.050: INFO: Pod "pod-subpath-test-dynamicpv-7h8k": Phase="Pending", Reason="", readiness=false. Elapsed: 8.800435586s
Jun 12 08:24:29.210: INFO: Pod "pod-subpath-test-dynamicpv-7h8k": Phase="Pending", Reason="", readiness=false. Elapsed: 10.959927782s
Jun 12 08:24:31.370: INFO: Pod "pod-subpath-test-dynamicpv-7h8k": Phase="Pending", Reason="", readiness=false. Elapsed: 13.120315282s
Jun 12 08:24:33.530: INFO: Pod "pod-subpath-test-dynamicpv-7h8k": Phase="Succeeded", Reason="", readiness=false. Elapsed: 15.280224595s
STEP: Saw pod success
Jun 12 08:24:33.530: INFO: Pod "pod-subpath-test-dynamicpv-7h8k" satisfied condition "Succeeded or Failed"
Jun 12 08:24:33.688: INFO: Trying to get logs from node ip-172-20-58-164.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-7h8k container test-container-subpath-dynamicpv-7h8k: <nil>
STEP: delete the pod
Jun 12 08:24:34.015: INFO: Waiting for pod pod-subpath-test-dynamicpv-7h8k to disappear
Jun 12 08:24:34.173: INFO: Pod pod-subpath-test-dynamicpv-7h8k no longer exists
STEP: Deleting pod
Jun 12 08:24:34.174: INFO: Deleting pod "pod-subpath-test-dynamicpv-7h8k" in namespace "provisioning-2944"
... skipping 71 lines ...

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

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

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

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 470 lines ...
Jun 12 08:24:35.683: INFO: PersistentVolumeClaim pvc-dtjjv found but phase is Pending instead of Bound.
Jun 12 08:24:37.845: INFO: PersistentVolumeClaim pvc-dtjjv found and phase=Bound (13.128292818s)
Jun 12 08:24:37.845: INFO: Waiting up to 3m0s for PersistentVolume aws-kwvnl to have phase Bound
Jun 12 08:24:38.006: INFO: PersistentVolume aws-kwvnl found and phase=Bound (160.951236ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-6qv2
STEP: Creating a pod to test exec-volume-test
Jun 12 08:24:38.489: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-6qv2" in namespace "volume-6074" to be "Succeeded or Failed"
Jun 12 08:24:38.649: INFO: Pod "exec-volume-test-preprovisionedpv-6qv2": Phase="Pending", Reason="", readiness=false. Elapsed: 160.68206ms
Jun 12 08:24:40.810: INFO: Pod "exec-volume-test-preprovisionedpv-6qv2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.321515938s
Jun 12 08:24:42.971: INFO: Pod "exec-volume-test-preprovisionedpv-6qv2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.482859006s
Jun 12 08:24:45.133: INFO: Pod "exec-volume-test-preprovisionedpv-6qv2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.644416294s
Jun 12 08:24:47.294: INFO: Pod "exec-volume-test-preprovisionedpv-6qv2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.805486307s
Jun 12 08:24:49.455: INFO: Pod "exec-volume-test-preprovisionedpv-6qv2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.966519059s
Jun 12 08:24:51.616: INFO: Pod "exec-volume-test-preprovisionedpv-6qv2": Phase="Pending", Reason="", readiness=false. Elapsed: 13.127411945s
Jun 12 08:24:53.778: INFO: Pod "exec-volume-test-preprovisionedpv-6qv2": Phase="Pending", Reason="", readiness=false. Elapsed: 15.289803249s
Jun 12 08:24:55.940: INFO: Pod "exec-volume-test-preprovisionedpv-6qv2": Phase="Pending", Reason="", readiness=false. Elapsed: 17.45156012s
Jun 12 08:24:58.102: INFO: Pod "exec-volume-test-preprovisionedpv-6qv2": Phase="Pending", Reason="", readiness=false. Elapsed: 19.612969478s
Jun 12 08:25:00.263: INFO: Pod "exec-volume-test-preprovisionedpv-6qv2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.773899017s
STEP: Saw pod success
Jun 12 08:25:00.263: INFO: Pod "exec-volume-test-preprovisionedpv-6qv2" satisfied condition "Succeeded or Failed"
Jun 12 08:25:00.423: INFO: Trying to get logs from node ip-172-20-46-122.ap-northeast-2.compute.internal pod exec-volume-test-preprovisionedpv-6qv2 container exec-container-preprovisionedpv-6qv2: <nil>
STEP: delete the pod
Jun 12 08:25:00.774: INFO: Waiting for pod exec-volume-test-preprovisionedpv-6qv2 to disappear
Jun 12 08:25:00.934: INFO: Pod exec-volume-test-preprovisionedpv-6qv2 no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-6qv2
Jun 12 08:25:00.935: INFO: Deleting pod "exec-volume-test-preprovisionedpv-6qv2" in namespace "volume-6074"
STEP: Deleting pv and pvc
Jun 12 08:25:01.095: INFO: Deleting PersistentVolumeClaim "pvc-dtjjv"
Jun 12 08:25:01.260: INFO: Deleting PersistentVolume "aws-kwvnl"
Jun 12 08:25:01.730: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0e4e666f32721f575", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e4e666f32721f575 is currently attached to i-0bbfca73506739cca
	status code: 400, request id: f09ac16f-7163-469f-a3b6-f4df5e2bd790
Jun 12 08:25:07.532: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0e4e666f32721f575", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e4e666f32721f575 is currently attached to i-0bbfca73506739cca
	status code: 400, request id: e98422d0-6d26-4dd7-9cbf-295cd2925983
Jun 12 08:25:13.291: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0e4e666f32721f575", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e4e666f32721f575 is currently attached to i-0bbfca73506739cca
	status code: 400, request id: f95b9bce-efa1-40c6-b699-e069b41bfc3d
Jun 12 08:25:19.066: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0e4e666f32721f575", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e4e666f32721f575 is currently attached to i-0bbfca73506739cca
	status code: 400, request id: 2f8aa41e-5619-48e2-abe3-fb1f6b0d1dc6
Jun 12 08:25:24.863: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-0e4e666f32721f575".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 08:25:24.863: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-6074" for this suite.
... skipping 23 lines ...
Jun 12 08:23:46.460: INFO: Creating resource for dynamic PV
Jun 12 08:23:46.460: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7862qlkks
STEP: creating a claim
Jun 12 08:23:46.618: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-7862
Jun 12 08:23:47.110: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-7862" in namespace "provisioning-7862" to be "Succeeded or Failed"
Jun 12 08:23:47.268: INFO: Pod "volume-prep-provisioning-7862": Phase="Pending", Reason="", readiness=false. Elapsed: 157.338366ms
Jun 12 08:23:49.425: INFO: Pod "volume-prep-provisioning-7862": Phase="Pending", Reason="", readiness=false. Elapsed: 2.314982145s
Jun 12 08:23:51.583: INFO: Pod "volume-prep-provisioning-7862": Phase="Pending", Reason="", readiness=false. Elapsed: 4.472643681s
Jun 12 08:23:53.741: INFO: Pod "volume-prep-provisioning-7862": Phase="Pending", Reason="", readiness=false. Elapsed: 6.630903508s
Jun 12 08:23:55.900: INFO: Pod "volume-prep-provisioning-7862": Phase="Pending", Reason="", readiness=false. Elapsed: 8.789351893s
Jun 12 08:23:58.058: INFO: Pod "volume-prep-provisioning-7862": Phase="Pending", Reason="", readiness=false. Elapsed: 10.948022339s
... skipping 8 lines ...
Jun 12 08:24:17.482: INFO: Pod "volume-prep-provisioning-7862": Phase="Pending", Reason="", readiness=false. Elapsed: 30.371587102s
Jun 12 08:24:19.639: INFO: Pod "volume-prep-provisioning-7862": Phase="Pending", Reason="", readiness=false. Elapsed: 32.529179294s
Jun 12 08:24:21.799: INFO: Pod "volume-prep-provisioning-7862": Phase="Pending", Reason="", readiness=false. Elapsed: 34.688306834s
Jun 12 08:24:23.956: INFO: Pod "volume-prep-provisioning-7862": Phase="Pending", Reason="", readiness=false. Elapsed: 36.845910232s
Jun 12 08:24:26.118: INFO: Pod "volume-prep-provisioning-7862": Phase="Succeeded", Reason="", readiness=false. Elapsed: 39.007775505s
STEP: Saw pod success
Jun 12 08:24:26.118: INFO: Pod "volume-prep-provisioning-7862" satisfied condition "Succeeded or Failed"
Jun 12 08:24:26.118: INFO: Deleting pod "volume-prep-provisioning-7862" in namespace "provisioning-7862"
Jun 12 08:24:26.301: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-7862" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-fznh
STEP: Checking for subpath error in container status
Jun 12 08:25:02.954: INFO: Deleting pod "pod-subpath-test-dynamicpv-fznh" in namespace "provisioning-7862"
Jun 12 08:25:03.120: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-fznh" to be fully deleted
STEP: Deleting pod
Jun 12 08:25:03.277: INFO: Deleting pod "pod-subpath-test-dynamicpv-fznh" in namespace "provisioning-7862"
STEP: Deleting pvc
Jun 12 08:25:03.749: INFO: Deleting PersistentVolumeClaim "awsxb2lc"
... skipping 77 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.rbyVcryct/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.rbyVcryct/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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 12 lines ...
Jun 12 08:24:57.346: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-745925twl
STEP: creating a claim
Jun 12 08:24:57.504: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-xz84
STEP: Creating a pod to test exec-volume-test
Jun 12 08:24:57.979: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-xz84" in namespace "volume-7459" to be "Succeeded or Failed"
Jun 12 08:24:58.136: INFO: Pod "exec-volume-test-dynamicpv-xz84": Phase="Pending", Reason="", readiness=false. Elapsed: 156.616448ms
Jun 12 08:25:00.292: INFO: Pod "exec-volume-test-dynamicpv-xz84": Phase="Pending", Reason="", readiness=false. Elapsed: 2.312818501s
Jun 12 08:25:02.449: INFO: Pod "exec-volume-test-dynamicpv-xz84": Phase="Pending", Reason="", readiness=false. Elapsed: 4.469935219s
Jun 12 08:25:04.606: INFO: Pod "exec-volume-test-dynamicpv-xz84": Phase="Pending", Reason="", readiness=false. Elapsed: 6.626670652s
Jun 12 08:25:06.763: INFO: Pod "exec-volume-test-dynamicpv-xz84": Phase="Pending", Reason="", readiness=false. Elapsed: 8.783561955s
Jun 12 08:25:08.920: INFO: Pod "exec-volume-test-dynamicpv-xz84": Phase="Pending", Reason="", readiness=false. Elapsed: 10.941134822s
Jun 12 08:25:11.077: INFO: Pod "exec-volume-test-dynamicpv-xz84": Phase="Pending", Reason="", readiness=false. Elapsed: 13.097507972s
Jun 12 08:25:13.233: INFO: Pod "exec-volume-test-dynamicpv-xz84": Phase="Pending", Reason="", readiness=false. Elapsed: 15.254188905s
Jun 12 08:25:15.389: INFO: Pod "exec-volume-test-dynamicpv-xz84": Phase="Pending", Reason="", readiness=false. Elapsed: 17.410438227s
Jun 12 08:25:17.547: INFO: Pod "exec-volume-test-dynamicpv-xz84": Phase="Pending", Reason="", readiness=false. Elapsed: 19.567855157s
Jun 12 08:25:19.703: INFO: Pod "exec-volume-test-dynamicpv-xz84": Phase="Pending", Reason="", readiness=false. Elapsed: 21.724297831s
Jun 12 08:25:21.861: INFO: Pod "exec-volume-test-dynamicpv-xz84": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.882275775s
STEP: Saw pod success
Jun 12 08:25:21.861: INFO: Pod "exec-volume-test-dynamicpv-xz84" satisfied condition "Succeeded or Failed"
Jun 12 08:25:22.018: INFO: Trying to get logs from node ip-172-20-58-164.ap-northeast-2.compute.internal pod exec-volume-test-dynamicpv-xz84 container exec-container-dynamicpv-xz84: <nil>
STEP: delete the pod
Jun 12 08:25:22.338: INFO: Waiting for pod exec-volume-test-dynamicpv-xz84 to disappear
Jun 12 08:25:22.495: INFO: Pod exec-volume-test-dynamicpv-xz84 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-xz84
Jun 12 08:25:22.495: INFO: Deleting pod "exec-volume-test-dynamicpv-xz84" in namespace "volume-7459"
... skipping 177 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 12 08:24:50.226: 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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun 12 08:24:51.025: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 12 08:24:51.025: INFO: Creating resource for dynamic PV
Jun 12 08:24:51.025: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-907vfcds
STEP: creating a claim
Jun 12 08:24:51.185: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-9r2w
STEP: Checking for subpath error in container status
Jun 12 08:25:15.994: INFO: Deleting pod "pod-subpath-test-dynamicpv-9r2w" in namespace "provisioning-907"
Jun 12 08:25:16.157: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-9r2w" to be fully deleted
STEP: Deleting pod
Jun 12 08:25:30.476: INFO: Deleting pod "pod-subpath-test-dynamicpv-9r2w" in namespace "provisioning-907"
STEP: Deleting pvc
Jun 12 08:25:30.963: INFO: Deleting PersistentVolumeClaim "awsg9tj8"
... skipping 12 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.rbyVcryct/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.rbyVcryct/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.rbyVcryct/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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow]
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 12 08:25:42.095: INFO: Driver "ebs.csi.aws.com" does not support volume type "PreprovisionedPV" - skipping
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow]
... skipping 47 lines ...
Jun 12 08:24:25.794: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9732-e2e-sclvm7g
STEP: creating a claim
Jun 12 08:24:25.955: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-fh76
STEP: Creating a pod to test multi_subpath
Jun 12 08:24:26.438: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-fh76" in namespace "provisioning-9732" to be "Succeeded or Failed"
Jun 12 08:24:26.602: INFO: Pod "pod-subpath-test-dynamicpv-fh76": Phase="Pending", Reason="", readiness=false. Elapsed: 163.837944ms
Jun 12 08:24:28.764: INFO: Pod "pod-subpath-test-dynamicpv-fh76": Phase="Pending", Reason="", readiness=false. Elapsed: 2.325290796s
Jun 12 08:24:30.924: INFO: Pod "pod-subpath-test-dynamicpv-fh76": Phase="Pending", Reason="", readiness=false. Elapsed: 4.48535523s
Jun 12 08:24:33.084: INFO: Pod "pod-subpath-test-dynamicpv-fh76": Phase="Pending", Reason="", readiness=false. Elapsed: 6.645339381s
Jun 12 08:24:35.244: INFO: Pod "pod-subpath-test-dynamicpv-fh76": Phase="Pending", Reason="", readiness=false. Elapsed: 8.805491808s
Jun 12 08:24:37.404: INFO: Pod "pod-subpath-test-dynamicpv-fh76": Phase="Pending", Reason="", readiness=false. Elapsed: 10.965776763s
... skipping 8 lines ...
Jun 12 08:24:56.852: INFO: Pod "pod-subpath-test-dynamicpv-fh76": Phase="Pending", Reason="", readiness=false. Elapsed: 30.413629194s
Jun 12 08:24:59.014: INFO: Pod "pod-subpath-test-dynamicpv-fh76": Phase="Pending", Reason="", readiness=false. Elapsed: 32.575378742s
Jun 12 08:25:01.178: INFO: Pod "pod-subpath-test-dynamicpv-fh76": Phase="Pending", Reason="", readiness=false. Elapsed: 34.740053422s
Jun 12 08:25:03.340: INFO: Pod "pod-subpath-test-dynamicpv-fh76": Phase="Pending", Reason="", readiness=false. Elapsed: 36.901571376s
Jun 12 08:25:05.500: INFO: Pod "pod-subpath-test-dynamicpv-fh76": Phase="Succeeded", Reason="", readiness=false. Elapsed: 39.06205483s
STEP: Saw pod success
Jun 12 08:25:05.501: INFO: Pod "pod-subpath-test-dynamicpv-fh76" satisfied condition "Succeeded or Failed"
Jun 12 08:25:05.660: INFO: Trying to get logs from node ip-172-20-46-122.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-fh76 container test-container-subpath-dynamicpv-fh76: <nil>
STEP: delete the pod
Jun 12 08:25:05.989: INFO: Waiting for pod pod-subpath-test-dynamicpv-fh76 to disappear
Jun 12 08:25:06.151: INFO: Pod pod-subpath-test-dynamicpv-fh76 no longer exists
STEP: Deleting pod
Jun 12 08:25:06.151: INFO: Deleting pod "pod-subpath-test-dynamicpv-fh76" in namespace "provisioning-9732"
... skipping 38 lines ...
Jun 12 08:24:26.305: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3924s54f5
STEP: creating a claim
Jun 12 08:24:26.472: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-vbdv
STEP: Creating a pod to test atomic-volume-subpath
Jun 12 08:24:26.950: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-vbdv" in namespace "provisioning-3924" to be "Succeeded or Failed"
Jun 12 08:24:27.109: INFO: Pod "pod-subpath-test-dynamicpv-vbdv": Phase="Pending", Reason="", readiness=false. Elapsed: 159.288224ms
Jun 12 08:24:29.267: INFO: Pod "pod-subpath-test-dynamicpv-vbdv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.317098647s
Jun 12 08:24:31.425: INFO: Pod "pod-subpath-test-dynamicpv-vbdv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.474855625s
Jun 12 08:24:33.582: INFO: Pod "pod-subpath-test-dynamicpv-vbdv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.632704892s
Jun 12 08:24:35.740: INFO: Pod "pod-subpath-test-dynamicpv-vbdv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.790614072s
Jun 12 08:24:37.902: INFO: Pod "pod-subpath-test-dynamicpv-vbdv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.952527513s
... skipping 18 lines ...
Jun 12 08:25:18.917: INFO: Pod "pod-subpath-test-dynamicpv-vbdv": Phase="Running", Reason="", readiness=true. Elapsed: 51.967137723s
Jun 12 08:25:21.075: INFO: Pod "pod-subpath-test-dynamicpv-vbdv": Phase="Running", Reason="", readiness=true. Elapsed: 54.12484557s
Jun 12 08:25:23.233: INFO: Pod "pod-subpath-test-dynamicpv-vbdv": Phase="Running", Reason="", readiness=true. Elapsed: 56.282798446s
Jun 12 08:25:25.391: INFO: Pod "pod-subpath-test-dynamicpv-vbdv": Phase="Running", Reason="", readiness=true. Elapsed: 58.441358165s
Jun 12 08:25:27.549: INFO: Pod "pod-subpath-test-dynamicpv-vbdv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m0.59910601s
STEP: Saw pod success
Jun 12 08:25:27.549: INFO: Pod "pod-subpath-test-dynamicpv-vbdv" satisfied condition "Succeeded or Failed"
Jun 12 08:25:27.707: INFO: Trying to get logs from node ip-172-20-46-122.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-vbdv container test-container-subpath-dynamicpv-vbdv: <nil>
STEP: delete the pod
Jun 12 08:25:28.053: INFO: Waiting for pod pod-subpath-test-dynamicpv-vbdv to disappear
Jun 12 08:25:28.210: INFO: Pod pod-subpath-test-dynamicpv-vbdv no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-vbdv
Jun 12 08:25:28.210: INFO: Deleting pod "pod-subpath-test-dynamicpv-vbdv" in namespace "provisioning-3924"
... skipping 91 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 12 08:24:55.485: 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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 12 08:24:56.291: INFO: Creating resource for dynamic PV
Jun 12 08:24:56.291: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-4385-e2e-sc24d57
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 12 08:25:01.425: INFO: Deleting pod "pod-1b3825fc-13f1-45a7-8662-6d89ff88ab7d" in namespace "volumemode-4385"
Jun 12 08:25:01.587: INFO: Wait up to 5m0s for pod "pod-1b3825fc-13f1-45a7-8662-6d89ff88ab7d" to be fully deleted
STEP: Deleting pvc
Jun 12 08:25:12.236: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comw7r89"
Jun 12 08:25:12.399: INFO: Waiting up to 5m0s for PersistentVolume pvc-e6abbdb0-a133-455d-843e-5f1b50739019 to get deleted
Jun 12 08:25:12.560: INFO: PersistentVolume pvc-e6abbdb0-a133-455d-843e-5f1b50739019 found and phase=Released (161.065242ms)
... skipping 13 lines ...

• [SLOW TEST:53.704 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.rbyVcryct/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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 207 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 12 08:24:56.629: 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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun 12 08:24:57.416: INFO: Creating resource for dynamic PV
Jun 12 08:24:57.416: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9600-e2e-scvqtsd
STEP: creating a claim
Jun 12 08:24:57.578: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-vrk2
STEP: Checking for subpath error in container status
Jun 12 08:25:42.372: INFO: Deleting pod "pod-subpath-test-dynamicpv-vrk2" in namespace "provisioning-9600"
Jun 12 08:25:42.533: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-vrk2" to be fully deleted
STEP: Deleting pod
Jun 12 08:25:46.848: INFO: Deleting pod "pod-subpath-test-dynamicpv-vrk2" in namespace "provisioning-9600"
STEP: Deleting pvc
Jun 12 08:25:47.320: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comn65gm"
... skipping 11 lines ...

• [SLOW TEST:66.960 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath directory is outside the volume [Slow][LinuxOnly]
    /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)(allowExpansion)] volume-expand
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (block volmode)(allowExpansion)] volume-expand
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 181 lines ...
STEP: Deleting pod hostexec-ip-172-20-55-5.ap-northeast-2.compute.internal-nvlwx in namespace volumemode-6102
Jun 12 08:25:50.954: INFO: Deleting pod "pod-7a6fa98e-2617-45f0-ade0-e4bb73e83778" in namespace "volumemode-6102"
Jun 12 08:25:51.117: INFO: Wait up to 5m0s for pod "pod-7a6fa98e-2617-45f0-ade0-e4bb73e83778" to be fully deleted
STEP: Deleting pv and pvc
Jun 12 08:26:01.438: INFO: Deleting PersistentVolumeClaim "pvc-qs25h"
Jun 12 08:26:01.601: INFO: Deleting PersistentVolume "aws-wtdwp"
Jun 12 08:26:02.022: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-07810050a111dd807", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07810050a111dd807 is currently attached to i-0282c044eee72f443
	status code: 400, request id: 4aa4c4e5-09de-4ff6-b7dc-2b8a66379711
Jun 12 08:26:07.806: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-07810050a111dd807".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 08:26:07.806: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-6102" for this suite.
... skipping 199 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.rbyVcryct/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.rbyVcryct/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.rbyVcryct/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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 213 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 12 08:25:23.888: 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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun 12 08:25:24.691: INFO: Creating resource for dynamic PV
Jun 12 08:25:24.691: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7207-e2e-sckpp85
STEP: creating a claim
Jun 12 08:25:24.853: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-rrz6
STEP: Checking for subpath error in container status
Jun 12 08:25:49.668: INFO: Deleting pod "pod-subpath-test-dynamicpv-rrz6" in namespace "provisioning-7207"
Jun 12 08:25:49.833: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-rrz6" to be fully deleted
STEP: Deleting pod
Jun 12 08:26:00.154: INFO: Deleting pod "pod-subpath-test-dynamicpv-rrz6" in namespace "provisioning-7207"
STEP: Deleting pvc
Jun 12 08:26:00.640: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comdf5dg"
... skipping 11 lines ...

• [SLOW TEST:53.048 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.rbyVcryct/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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 12 08:26:16.938: INFO: Distro debian doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
... skipping 46 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.rbyVcryct/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.rbyVcryct/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.rbyVcryct/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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 11 lines ...
Jun 12 08:25:25.719: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7808-e2e-sc9qnx6
STEP: creating a claim
Jun 12 08:25:25.877: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-thcw
STEP: Creating a pod to test subpath
Jun 12 08:25:26.355: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-thcw" in namespace "provisioning-7808" to be "Succeeded or Failed"
Jun 12 08:25:26.513: INFO: Pod "pod-subpath-test-dynamicpv-thcw": Phase="Pending", Reason="", readiness=false. Elapsed: 157.40869ms
Jun 12 08:25:28.676: INFO: Pod "pod-subpath-test-dynamicpv-thcw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.320438192s
Jun 12 08:25:30.835: INFO: Pod "pod-subpath-test-dynamicpv-thcw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.480068156s
Jun 12 08:25:32.993: INFO: Pod "pod-subpath-test-dynamicpv-thcw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.63813439s
Jun 12 08:25:35.155: INFO: Pod "pod-subpath-test-dynamicpv-thcw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.799911576s
Jun 12 08:25:37.313: INFO: Pod "pod-subpath-test-dynamicpv-thcw": Phase="Pending", Reason="", readiness=false. Elapsed: 10.957622076s
Jun 12 08:25:39.471: INFO: Pod "pod-subpath-test-dynamicpv-thcw": Phase="Pending", Reason="", readiness=false. Elapsed: 13.116169272s
Jun 12 08:25:41.630: INFO: Pod "pod-subpath-test-dynamicpv-thcw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 15.274557506s
STEP: Saw pod success
Jun 12 08:25:41.630: INFO: Pod "pod-subpath-test-dynamicpv-thcw" satisfied condition "Succeeded or Failed"
Jun 12 08:25:41.788: INFO: Trying to get logs from node ip-172-20-33-120.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-thcw container test-container-volume-dynamicpv-thcw: <nil>
STEP: delete the pod
Jun 12 08:25:42.116: INFO: Waiting for pod pod-subpath-test-dynamicpv-thcw to disappear
Jun 12 08:25:42.273: INFO: Pod pod-subpath-test-dynamicpv-thcw no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-thcw
Jun 12 08:25:42.273: INFO: Deleting pod "pod-subpath-test-dynamicpv-thcw" in namespace "provisioning-7808"
... skipping 171 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.rbyVcryct/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.rbyVcryct/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.rbyVcryct/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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 122 lines ...
Jun 12 08:25:40.011: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-480-e2e-sc6hlsv
STEP: creating a claim
Jun 12 08:25:40.168: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-dphf
STEP: Creating a pod to test exec-volume-test
Jun 12 08:25:40.640: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-dphf" in namespace "volume-480" to be "Succeeded or Failed"
Jun 12 08:25:40.796: INFO: Pod "exec-volume-test-dynamicpv-dphf": Phase="Pending", Reason="", readiness=false. Elapsed: 156.037853ms
Jun 12 08:25:42.953: INFO: Pod "exec-volume-test-dynamicpv-dphf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.312835126s
Jun 12 08:25:45.109: INFO: Pod "exec-volume-test-dynamicpv-dphf": Phase="Pending", Reason="", readiness=false. Elapsed: 4.469616629s
Jun 12 08:25:47.271: INFO: Pod "exec-volume-test-dynamicpv-dphf": Phase="Pending", Reason="", readiness=false. Elapsed: 6.631617023s
Jun 12 08:25:49.428: INFO: Pod "exec-volume-test-dynamicpv-dphf": Phase="Pending", Reason="", readiness=false. Elapsed: 8.788221961s
Jun 12 08:25:51.585: INFO: Pod "exec-volume-test-dynamicpv-dphf": Phase="Pending", Reason="", readiness=false. Elapsed: 10.945468462s
Jun 12 08:25:53.742: INFO: Pod "exec-volume-test-dynamicpv-dphf": Phase="Pending", Reason="", readiness=false. Elapsed: 13.102612405s
Jun 12 08:25:55.903: INFO: Pod "exec-volume-test-dynamicpv-dphf": Phase="Succeeded", Reason="", readiness=false. Elapsed: 15.26271453s
STEP: Saw pod success
Jun 12 08:25:55.903: INFO: Pod "exec-volume-test-dynamicpv-dphf" satisfied condition "Succeeded or Failed"
Jun 12 08:25:56.059: INFO: Trying to get logs from node ip-172-20-58-164.ap-northeast-2.compute.internal pod exec-volume-test-dynamicpv-dphf container exec-container-dynamicpv-dphf: <nil>
STEP: delete the pod
Jun 12 08:25:56.391: INFO: Waiting for pod exec-volume-test-dynamicpv-dphf to disappear
Jun 12 08:25:56.553: INFO: Pod exec-volume-test-dynamicpv-dphf no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-dphf
Jun 12 08:25:56.553: INFO: Deleting pod "exec-volume-test-dynamicpv-dphf" in namespace "volume-480"
... skipping 159 lines ...
Jun 12 08:26:00.268: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4146-e2e-scndf8g
STEP: creating a claim
Jun 12 08:26:00.423: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-rj86
STEP: Creating a pod to test subpath
Jun 12 08:26:00.896: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-rj86" in namespace "provisioning-4146" to be "Succeeded or Failed"
Jun 12 08:26:01.051: INFO: Pod "pod-subpath-test-dynamicpv-rj86": Phase="Pending", Reason="", readiness=false. Elapsed: 155.541289ms
Jun 12 08:26:03.206: INFO: Pod "pod-subpath-test-dynamicpv-rj86": Phase="Pending", Reason="", readiness=false. Elapsed: 2.310636266s
Jun 12 08:26:05.361: INFO: Pod "pod-subpath-test-dynamicpv-rj86": Phase="Pending", Reason="", readiness=false. Elapsed: 4.465298711s
Jun 12 08:26:07.516: INFO: Pod "pod-subpath-test-dynamicpv-rj86": Phase="Pending", Reason="", readiness=false. Elapsed: 6.620208374s
Jun 12 08:26:09.671: INFO: Pod "pod-subpath-test-dynamicpv-rj86": Phase="Pending", Reason="", readiness=false. Elapsed: 8.774815599s
Jun 12 08:26:11.826: INFO: Pod "pod-subpath-test-dynamicpv-rj86": Phase="Pending", Reason="", readiness=false. Elapsed: 10.930605811s
Jun 12 08:26:13.981: INFO: Pod "pod-subpath-test-dynamicpv-rj86": Phase="Pending", Reason="", readiness=false. Elapsed: 13.085602104s
Jun 12 08:26:16.141: INFO: Pod "pod-subpath-test-dynamicpv-rj86": Phase="Pending", Reason="", readiness=false. Elapsed: 15.245517094s
Jun 12 08:26:18.296: INFO: Pod "pod-subpath-test-dynamicpv-rj86": Phase="Pending", Reason="", readiness=false. Elapsed: 17.400151126s
Jun 12 08:26:20.451: INFO: Pod "pod-subpath-test-dynamicpv-rj86": Phase="Pending", Reason="", readiness=false. Elapsed: 19.555774714s
Jun 12 08:26:22.607: INFO: Pod "pod-subpath-test-dynamicpv-rj86": Phase="Pending", Reason="", readiness=false. Elapsed: 21.711342549s
Jun 12 08:26:24.763: INFO: Pod "pod-subpath-test-dynamicpv-rj86": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.866876177s
STEP: Saw pod success
Jun 12 08:26:24.763: INFO: Pod "pod-subpath-test-dynamicpv-rj86" satisfied condition "Succeeded or Failed"
Jun 12 08:26:24.918: INFO: Trying to get logs from node ip-172-20-55-5.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-rj86 container test-container-subpath-dynamicpv-rj86: <nil>
STEP: delete the pod
Jun 12 08:26:25.238: INFO: Waiting for pod pod-subpath-test-dynamicpv-rj86 to disappear
Jun 12 08:26:25.392: INFO: Pod pod-subpath-test-dynamicpv-rj86 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-rj86
Jun 12 08:26:25.392: INFO: Deleting pod "pod-subpath-test-dynamicpv-rj86" in namespace "provisioning-4146"
... skipping 26 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 12 08:26:27.037: 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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 12 08:26:27.832: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 12 08:26:27.832: INFO: Creating resource for dynamic PV
Jun 12 08:26:27.832: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-36519whsj
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 12 08:26:34.951: INFO: Deleting pod "pod-a25b5801-9262-43b2-a4c8-ce38ada480d7" in namespace "volumemode-3651"
Jun 12 08:26:35.114: INFO: Wait up to 5m0s for pod "pod-a25b5801-9262-43b2-a4c8-ce38ada480d7" to be fully deleted
STEP: Deleting pvc
Jun 12 08:26:39.748: INFO: Deleting PersistentVolumeClaim "awsh9f6g"
Jun 12 08:26:39.911: INFO: Waiting up to 5m0s for PersistentVolume pvc-5c326f9d-6bb6-4779-b020-91f7eed76299 to get deleted
Jun 12 08:26:40.069: INFO: PersistentVolume pvc-5c326f9d-6bb6-4779-b020-91f7eed76299 found and phase=Released (158.542234ms)
... skipping 9 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.rbyVcryct/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.rbyVcryct/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
    /tmp/kops.rbyVcryct/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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)(allowExpansion)][Feature:Windows] volume-expand
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 12 08:26:45.713: INFO: Distro debian doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)(allowExpansion)][Feature:Windows] volume-expand
... skipping 548 lines ...
Jun 12 08:26:58.183: INFO: Waiting for pod aws-client to disappear
Jun 12 08:26:58.341: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 12 08:26:58.341: INFO: Deleting PersistentVolumeClaim "pvc-ls4r7"
Jun 12 08:26:58.501: INFO: Deleting PersistentVolume "aws-tq296"
Jun 12 08:26:59.496: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-094db89821d67821d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-094db89821d67821d is currently attached to i-0bbfca73506739cca
	status code: 400, request id: 5c8bec4d-1afe-4dc8-bca8-691922e20e38
Jun 12 08:27:05.305: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-094db89821d67821d".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 08:27:05.305: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8745" for this suite.
... skipping 18 lines ...

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

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

    /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:92
------------------------------
... skipping 14 lines ...
Jun 12 08:25:49.996: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-2135wzf8c
STEP: creating a claim
Jun 12 08:25:50.158: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-c22q
STEP: Creating a pod to test exec-volume-test
Jun 12 08:25:50.647: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-c22q" in namespace "volume-2135" to be "Succeeded or Failed"
Jun 12 08:25:50.808: INFO: Pod "exec-volume-test-dynamicpv-c22q": Phase="Pending", Reason="", readiness=false. Elapsed: 160.54111ms
Jun 12 08:25:52.969: INFO: Pod "exec-volume-test-dynamicpv-c22q": Phase="Pending", Reason="", readiness=false. Elapsed: 2.321603307s
Jun 12 08:25:55.130: INFO: Pod "exec-volume-test-dynamicpv-c22q": Phase="Pending", Reason="", readiness=false. Elapsed: 4.482742052s
Jun 12 08:25:57.291: INFO: Pod "exec-volume-test-dynamicpv-c22q": Phase="Pending", Reason="", readiness=false. Elapsed: 6.643772708s
Jun 12 08:25:59.452: INFO: Pod "exec-volume-test-dynamicpv-c22q": Phase="Pending", Reason="", readiness=false. Elapsed: 8.804829435s
Jun 12 08:26:01.615: INFO: Pod "exec-volume-test-dynamicpv-c22q": Phase="Pending", Reason="", readiness=false. Elapsed: 10.968082526s
... skipping 8 lines ...
Jun 12 08:26:21.069: INFO: Pod "exec-volume-test-dynamicpv-c22q": Phase="Pending", Reason="", readiness=false. Elapsed: 30.422007115s
Jun 12 08:26:23.231: INFO: Pod "exec-volume-test-dynamicpv-c22q": Phase="Pending", Reason="", readiness=false. Elapsed: 32.584203395s
Jun 12 08:26:25.394: INFO: Pod "exec-volume-test-dynamicpv-c22q": Phase="Pending", Reason="", readiness=false. Elapsed: 34.746360978s
Jun 12 08:26:27.556: INFO: Pod "exec-volume-test-dynamicpv-c22q": Phase="Pending", Reason="", readiness=false. Elapsed: 36.908343491s
Jun 12 08:26:29.717: INFO: Pod "exec-volume-test-dynamicpv-c22q": Phase="Succeeded", Reason="", readiness=false. Elapsed: 39.069553658s
STEP: Saw pod success
Jun 12 08:26:29.717: INFO: Pod "exec-volume-test-dynamicpv-c22q" satisfied condition "Succeeded or Failed"
Jun 12 08:26:29.878: INFO: Trying to get logs from node ip-172-20-58-164.ap-northeast-2.compute.internal pod exec-volume-test-dynamicpv-c22q container exec-container-dynamicpv-c22q: <nil>
STEP: delete the pod
Jun 12 08:26:30.206: INFO: Waiting for pod exec-volume-test-dynamicpv-c22q to disappear
Jun 12 08:26:30.367: INFO: Pod exec-volume-test-dynamicpv-c22q no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-c22q
Jun 12 08:26:30.367: INFO: Deleting pod "exec-volume-test-dynamicpv-c22q" in namespace "volume-2135"
... skipping 68 lines ...
Jun 12 08:27:10.084: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 133 lines ...
Jun 12 08:26:10.071: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3480-e2e-scc9pt5
STEP: creating a claim
Jun 12 08:26:10.232: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-fhpp
STEP: Creating a pod to test atomic-volume-subpath
Jun 12 08:26:10.717: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-fhpp" in namespace "provisioning-3480" to be "Succeeded or Failed"
Jun 12 08:26:10.877: INFO: Pod "pod-subpath-test-dynamicpv-fhpp": Phase="Pending", Reason="", readiness=false. Elapsed: 160.458815ms
Jun 12 08:26:13.038: INFO: Pod "pod-subpath-test-dynamicpv-fhpp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.321594642s
Jun 12 08:26:15.199: INFO: Pod "pod-subpath-test-dynamicpv-fhpp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.482688851s
Jun 12 08:26:17.360: INFO: Pod "pod-subpath-test-dynamicpv-fhpp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.643508073s
Jun 12 08:26:19.522: INFO: Pod "pod-subpath-test-dynamicpv-fhpp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.804919236s
Jun 12 08:26:21.683: INFO: Pod "pod-subpath-test-dynamicpv-fhpp": Phase="Running", Reason="", readiness=true. Elapsed: 10.966391819s
... skipping 5 lines ...
Jun 12 08:26:34.652: INFO: Pod "pod-subpath-test-dynamicpv-fhpp": Phase="Running", Reason="", readiness=true. Elapsed: 23.934724108s
Jun 12 08:26:36.813: INFO: Pod "pod-subpath-test-dynamicpv-fhpp": Phase="Running", Reason="", readiness=true. Elapsed: 26.096279668s
Jun 12 08:26:38.975: INFO: Pod "pod-subpath-test-dynamicpv-fhpp": Phase="Running", Reason="", readiness=true. Elapsed: 28.258149312s
Jun 12 08:26:41.136: INFO: Pod "pod-subpath-test-dynamicpv-fhpp": Phase="Running", Reason="", readiness=true. Elapsed: 30.419328139s
Jun 12 08:26:43.298: INFO: Pod "pod-subpath-test-dynamicpv-fhpp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 32.581138316s
STEP: Saw pod success
Jun 12 08:26:43.298: INFO: Pod "pod-subpath-test-dynamicpv-fhpp" satisfied condition "Succeeded or Failed"
Jun 12 08:26:43.458: INFO: Trying to get logs from node ip-172-20-46-122.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-fhpp container test-container-subpath-dynamicpv-fhpp: <nil>
STEP: delete the pod
Jun 12 08:26:43.792: INFO: Waiting for pod pod-subpath-test-dynamicpv-fhpp to disappear
Jun 12 08:26:43.952: INFO: Pod pod-subpath-test-dynamicpv-fhpp no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-fhpp
Jun 12 08:26:43.952: INFO: Deleting pod "pod-subpath-test-dynamicpv-fhpp" in namespace "provisioning-3480"
... skipping 250 lines ...

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

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

    /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 230 lines ...
Jun 12 08:26:49.186: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 12 08:26:50.198: INFO: Successfully created a new PD: "aws://ap-northeast-2a/vol-0538076d8c4c10bdd".
Jun 12 08:26:50.198: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-px4b
STEP: Creating a pod to test exec-volume-test
Jun 12 08:26:50.358: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-px4b" in namespace "volume-9271" to be "Succeeded or Failed"
Jun 12 08:26:50.515: INFO: Pod "exec-volume-test-inlinevolume-px4b": Phase="Pending", Reason="", readiness=false. Elapsed: 156.836889ms
Jun 12 08:26:52.672: INFO: Pod "exec-volume-test-inlinevolume-px4b": Phase="Pending", Reason="", readiness=false. Elapsed: 2.31454299s
Jun 12 08:26:54.832: INFO: Pod "exec-volume-test-inlinevolume-px4b": Phase="Pending", Reason="", readiness=false. Elapsed: 4.474422571s
Jun 12 08:26:56.990: INFO: Pod "exec-volume-test-inlinevolume-px4b": Phase="Pending", Reason="", readiness=false. Elapsed: 6.632583892s
Jun 12 08:26:59.148: INFO: Pod "exec-volume-test-inlinevolume-px4b": Phase="Pending", Reason="", readiness=false. Elapsed: 8.790767147s
Jun 12 08:27:01.306: INFO: Pod "exec-volume-test-inlinevolume-px4b": Phase="Pending", Reason="", readiness=false. Elapsed: 10.948253586s
Jun 12 08:27:03.464: INFO: Pod "exec-volume-test-inlinevolume-px4b": Phase="Pending", Reason="", readiness=false. Elapsed: 13.10616132s
Jun 12 08:27:05.622: INFO: Pod "exec-volume-test-inlinevolume-px4b": Phase="Pending", Reason="", readiness=false. Elapsed: 15.263877286s
Jun 12 08:27:07.780: INFO: Pod "exec-volume-test-inlinevolume-px4b": Phase="Pending", Reason="", readiness=false. Elapsed: 17.42248008s
Jun 12 08:27:09.939: INFO: Pod "exec-volume-test-inlinevolume-px4b": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.581169374s
STEP: Saw pod success
Jun 12 08:27:09.939: INFO: Pod "exec-volume-test-inlinevolume-px4b" satisfied condition "Succeeded or Failed"
Jun 12 08:27:10.096: INFO: Trying to get logs from node ip-172-20-46-122.ap-northeast-2.compute.internal pod exec-volume-test-inlinevolume-px4b container exec-container-inlinevolume-px4b: <nil>
STEP: delete the pod
Jun 12 08:27:10.835: INFO: Waiting for pod exec-volume-test-inlinevolume-px4b to disappear
Jun 12 08:27:11.007: INFO: Pod exec-volume-test-inlinevolume-px4b no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-px4b
Jun 12 08:27:11.007: INFO: Deleting pod "exec-volume-test-inlinevolume-px4b" in namespace "volume-9271"
Jun 12 08:27:11.417: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0538076d8c4c10bdd", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0538076d8c4c10bdd is currently attached to i-0bbfca73506739cca
	status code: 400, request id: 74646f0b-e800-4f9a-a676-869cff011f05
Jun 12 08:27:17.254: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0538076d8c4c10bdd", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0538076d8c4c10bdd is currently attached to i-0bbfca73506739cca
	status code: 400, request id: 698bb9d2-1f41-4867-b019-f7836ef28dc9
Jun 12 08:27:23.005: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0538076d8c4c10bdd", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0538076d8c4c10bdd is currently attached to i-0bbfca73506739cca
	status code: 400, request id: c202e7c3-462c-46dc-925d-5ea05203c4ec
Jun 12 08:27:28.772: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0538076d8c4c10bdd", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0538076d8c4c10bdd is currently attached to i-0bbfca73506739cca
	status code: 400, request id: e3657f98-ab6d-4b38-9323-e334a92bdfc9
Jun 12 08:27:34.523: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0538076d8c4c10bdd", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0538076d8c4c10bdd is currently attached to i-0bbfca73506739cca
	status code: 400, request id: 1cc29eb3-af6a-43f4-b5d4-e32cab1d0f1e
Jun 12 08:27:40.309: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-0538076d8c4c10bdd".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 08:27:40.309: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-9271" for this suite.
... skipping 569 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 12 08:26:50.689: 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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun 12 08:26:51.499: INFO: Creating resource for dynamic PV
Jun 12 08:26:51.499: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-980-e2e-scqk2k7
STEP: creating a claim
Jun 12 08:26:51.663: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-4sjf
STEP: Checking for subpath error in container status
Jun 12 08:27:08.482: INFO: Deleting pod "pod-subpath-test-dynamicpv-4sjf" in namespace "provisioning-980"
Jun 12 08:27:08.646: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-4sjf" to be fully deleted
STEP: Deleting pod
Jun 12 08:27:18.971: INFO: Deleting pod "pod-subpath-test-dynamicpv-4sjf" in namespace "provisioning-980"
STEP: Deleting pvc
Jun 12 08:27:19.454: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comgp98x"
... skipping 15 lines ...

• [SLOW TEST:65.728 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.rbyVcryct/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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 31 lines ...
STEP: Deleting pod hostexec-ip-172-20-55-5.ap-northeast-2.compute.internal-hkhwr in namespace volumemode-7572
Jun 12 08:27:46.079: INFO: Deleting pod "pod-dd649692-13f7-4162-b788-768dec461529" in namespace "volumemode-7572"
Jun 12 08:27:46.253: INFO: Wait up to 5m0s for pod "pod-dd649692-13f7-4162-b788-768dec461529" to be fully deleted
STEP: Deleting pv and pvc
Jun 12 08:27:50.567: INFO: Deleting PersistentVolumeClaim "pvc-pn5wc"
Jun 12 08:27:50.722: INFO: Deleting PersistentVolume "aws-v55sm"
Jun 12 08:27:51.143: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0b4089ae44c91a653", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0b4089ae44c91a653 is currently attached to i-0282c044eee72f443
	status code: 400, request id: 9dcfd38b-0e10-447a-a808-565f6da6e53f
Jun 12 08:27:56.961: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-0b4089ae44c91a653".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 08:27:56.961: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-7572" for this suite.
... skipping 89 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.rbyVcryct/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.rbyVcryct/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.rbyVcryct/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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

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

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

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

    /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 92 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 12 08:27:42.475: 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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 12 08:27:43.261: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 12 08:27:44.226: INFO: Successfully created a new PD: "aws://ap-northeast-2a/vol-0737357dc4a91ff54".
Jun 12 08:27:44.226: INFO: Creating resource for pre-provisioned PV
Jun 12 08:27:44.226: INFO: Creating PVC and PV
... skipping 5 lines ...
Jun 12 08:27:49.089: INFO: PersistentVolumeClaim pvc-4bzth found but phase is Pending instead of Bound.
Jun 12 08:27:51.248: INFO: PersistentVolumeClaim pvc-4bzth found but phase is Pending instead of Bound.
Jun 12 08:27:53.406: INFO: PersistentVolumeClaim pvc-4bzth found and phase=Bound (8.787758776s)
Jun 12 08:27:53.406: INFO: Waiting up to 3m0s for PersistentVolume aws-gwhj7 to have phase Bound
Jun 12 08:27:53.563: INFO: PersistentVolume aws-gwhj7 found and phase=Bound (157.028856ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 12 08:27:54.349: INFO: Deleting pod "pod-24f96c15-26f1-484d-b030-e517be1f19df" in namespace "volumemode-4063"
Jun 12 08:27:54.509: INFO: Wait up to 5m0s for pod "pod-24f96c15-26f1-484d-b030-e517be1f19df" to be fully deleted
STEP: Deleting pv and pvc
Jun 12 08:27:58.824: INFO: Deleting PersistentVolumeClaim "pvc-4bzth"
Jun 12 08:27:58.982: INFO: Deleting PersistentVolume "aws-gwhj7"
Jun 12 08:27:59.390: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0737357dc4a91ff54", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0737357dc4a91ff54 is currently attached to i-045954f58307d9775
	status code: 400, request id: c9f728d9-b085-4b87-a002-6c9985a6e230
Jun 12 08:28:05.164: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-0737357dc4a91ff54".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 08:28:05.164: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-4063" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.rbyVcryct/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.rbyVcryct/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
    /tmp/kops.rbyVcryct/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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] volume-expand
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 12 08:28:05.488: INFO: Distro debian doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] volume-expand
... skipping 44 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.rbyVcryct/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.rbyVcryct/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.rbyVcryct/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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 12 lines ...
Jun 12 08:27:41.419: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-4750qf7tm
STEP: creating a claim
Jun 12 08:27:41.577: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-wrpr
STEP: Creating a pod to test exec-volume-test
Jun 12 08:27:42.052: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-wrpr" in namespace "volume-4750" to be "Succeeded or Failed"
Jun 12 08:27:42.209: INFO: Pod "exec-volume-test-dynamicpv-wrpr": Phase="Pending", Reason="", readiness=false. Elapsed: 157.220332ms
Jun 12 08:27:44.366: INFO: Pod "exec-volume-test-dynamicpv-wrpr": Phase="Pending", Reason="", readiness=false. Elapsed: 2.314639013s
Jun 12 08:27:46.527: INFO: Pod "exec-volume-test-dynamicpv-wrpr": Phase="Pending", Reason="", readiness=false. Elapsed: 4.474705325s
Jun 12 08:27:48.684: INFO: Pod "exec-volume-test-dynamicpv-wrpr": Phase="Pending", Reason="", readiness=false. Elapsed: 6.632318769s
Jun 12 08:27:50.843: INFO: Pod "exec-volume-test-dynamicpv-wrpr": Phase="Pending", Reason="", readiness=false. Elapsed: 8.791245298s
Jun 12 08:27:53.001: INFO: Pod "exec-volume-test-dynamicpv-wrpr": Phase="Pending", Reason="", readiness=false. Elapsed: 10.949607181s
Jun 12 08:27:55.159: INFO: Pod "exec-volume-test-dynamicpv-wrpr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 13.107211345s
STEP: Saw pod success
Jun 12 08:27:55.159: INFO: Pod "exec-volume-test-dynamicpv-wrpr" satisfied condition "Succeeded or Failed"
Jun 12 08:27:55.317: INFO: Trying to get logs from node ip-172-20-46-122.ap-northeast-2.compute.internal pod exec-volume-test-dynamicpv-wrpr container exec-container-dynamicpv-wrpr: <nil>
STEP: delete the pod
Jun 12 08:27:55.643: INFO: Waiting for pod exec-volume-test-dynamicpv-wrpr to disappear
Jun 12 08:27:55.801: INFO: Pod exec-volume-test-dynamicpv-wrpr no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-wrpr
Jun 12 08:27:55.801: INFO: Deleting pod "exec-volume-test-dynamicpv-wrpr" in namespace "volume-4750"
... skipping 155 lines ...
Jun 12 08:25:42.899: INFO: Creating resource for dynamic PV
Jun 12 08:25:42.899: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-5494-e2e-sctb8sj
STEP: creating a claim
Jun 12 08:25:43.060: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 12 08:25:43.541: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-2qx4l" in namespace "snapshotting-5494" to be "Succeeded or Failed"
Jun 12 08:25:43.701: INFO: Pod "pvc-snapshottable-tester-2qx4l": Phase="Pending", Reason="", readiness=false. Elapsed: 159.638968ms
Jun 12 08:25:45.861: INFO: Pod "pvc-snapshottable-tester-2qx4l": Phase="Pending", Reason="", readiness=false. Elapsed: 2.319832738s
Jun 12 08:25:48.021: INFO: Pod "pvc-snapshottable-tester-2qx4l": Phase="Pending", Reason="", readiness=false. Elapsed: 4.479473451s
Jun 12 08:25:50.181: INFO: Pod "pvc-snapshottable-tester-2qx4l": Phase="Pending", Reason="", readiness=false. Elapsed: 6.639716284s
Jun 12 08:25:52.341: INFO: Pod "pvc-snapshottable-tester-2qx4l": Phase="Pending", Reason="", readiness=false. Elapsed: 8.799541237s
Jun 12 08:25:54.502: INFO: Pod "pvc-snapshottable-tester-2qx4l": Phase="Pending", Reason="", readiness=false. Elapsed: 10.960720382s
... skipping 7 lines ...
Jun 12 08:26:11.784: INFO: Pod "pvc-snapshottable-tester-2qx4l": Phase="Pending", Reason="", readiness=false. Elapsed: 28.24301094s
Jun 12 08:26:13.945: INFO: Pod "pvc-snapshottable-tester-2qx4l": Phase="Pending", Reason="", readiness=false. Elapsed: 30.403833433s
Jun 12 08:26:16.105: INFO: Pod "pvc-snapshottable-tester-2qx4l": Phase="Pending", Reason="", readiness=false. Elapsed: 32.564122438s
Jun 12 08:26:18.270: INFO: Pod "pvc-snapshottable-tester-2qx4l": Phase="Pending", Reason="", readiness=false. Elapsed: 34.728969535s
Jun 12 08:26:20.433: INFO: Pod "pvc-snapshottable-tester-2qx4l": Phase="Succeeded", Reason="", readiness=false. Elapsed: 36.891935274s
STEP: Saw pod success
Jun 12 08:26:20.433: INFO: Pod "pvc-snapshottable-tester-2qx4l" satisfied condition "Succeeded or Failed"
Jun 12 08:26:20.761: INFO: Pod pvc-snapshottable-tester-2qx4l has the following logs: 
Jun 12 08:26:20.761: INFO: Deleting pod "pvc-snapshottable-tester-2qx4l" in namespace "snapshotting-5494"
Jun 12 08:26:20.932: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-2qx4l" to be fully deleted
Jun 12 08:26:21.093: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comms7xk] to have phase Bound
Jun 12 08:26:21.255: INFO: PersistentVolumeClaim ebs.csi.aws.comms7xk found and phase=Bound (161.568568ms)
STEP: [init] checking the claim
... skipping 15 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:243
STEP: checking the snapshot
STEP: checking the SnapshotContent
STEP: Modifying source data test
STEP: modifying the data in the source PVC
Jun 12 08:26:33.867: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-g4spt" in namespace "snapshotting-5494" to be "Succeeded or Failed"
Jun 12 08:26:34.029: INFO: Pod "pvc-snapshottable-data-tester-g4spt": Phase="Pending", Reason="", readiness=false. Elapsed: 161.6755ms
Jun 12 08:26:36.195: INFO: Pod "pvc-snapshottable-data-tester-g4spt": Phase="Pending", Reason="", readiness=false. Elapsed: 2.327180267s
Jun 12 08:26:38.358: INFO: Pod "pvc-snapshottable-data-tester-g4spt": Phase="Pending", Reason="", readiness=false. Elapsed: 4.490465231s
Jun 12 08:26:40.521: INFO: Pod "pvc-snapshottable-data-tester-g4spt": Phase="Pending", Reason="", readiness=false. Elapsed: 6.65349143s
Jun 12 08:26:42.683: INFO: Pod "pvc-snapshottable-data-tester-g4spt": Phase="Pending", Reason="", readiness=false. Elapsed: 8.815502317s
Jun 12 08:26:44.849: INFO: Pod "pvc-snapshottable-data-tester-g4spt": Phase="Pending", Reason="", readiness=false. Elapsed: 10.981476286s
Jun 12 08:26:47.012: INFO: Pod "pvc-snapshottable-data-tester-g4spt": Phase="Pending", Reason="", readiness=false. Elapsed: 13.144267054s
Jun 12 08:26:49.174: INFO: Pod "pvc-snapshottable-data-tester-g4spt": Phase="Pending", Reason="", readiness=false. Elapsed: 15.306497037s
Jun 12 08:26:51.337: INFO: Pod "pvc-snapshottable-data-tester-g4spt": Phase="Succeeded", Reason="", readiness=false. Elapsed: 17.469456546s
STEP: Saw pod success
Jun 12 08:26:51.337: INFO: Pod "pvc-snapshottable-data-tester-g4spt" satisfied condition "Succeeded or Failed"
Jun 12 08:26:51.665: INFO: Pod pvc-snapshottable-data-tester-g4spt has the following logs: 
Jun 12 08:26:51.665: INFO: Deleting pod "pvc-snapshottable-data-tester-g4spt" in namespace "snapshotting-5494"
Jun 12 08:26:51.837: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-g4spt" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 12 08:27:14.655: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-5494 exec restored-pvc-tester-vj8rr --namespace=snapshotting-5494 -- cat /mnt/test/data'
... skipping 29 lines ...
STEP: Found 27 events.
Jun 12 08:28:02.893: INFO: At 2021-06-12 08:25:43 +0000 UTC - event for ebs.csi.aws.comms7xk: {persistentvolume-controller } ExternalProvisioning: waiting for a volume to be created, either by external provisioner "ebs.csi.aws.com" or manually created by system administrator
Jun 12 08:28:02.893: INFO: At 2021-06-12 08:25:43 +0000 UTC - event for ebs.csi.aws.comms7xk: {ebs.csi.aws.com_ebs-csi-controller-7ffff4ddf5-wt7vk_0c48e742-b0b6-4a80-8253-ed2d3f11a914 } Provisioning: External provisioner is provisioning volume for claim "snapshotting-5494/ebs.csi.aws.comms7xk"
Jun 12 08:28:02.893: INFO: At 2021-06-12 08:25:43 +0000 UTC - event for ebs.csi.aws.comms7xk: {persistentvolume-controller } WaitForFirstConsumer: waiting for first consumer to be created before binding
Jun 12 08:28:02.893: INFO: At 2021-06-12 08:25:46 +0000 UTC - event for ebs.csi.aws.comms7xk: {ebs.csi.aws.com_ebs-csi-controller-7ffff4ddf5-wt7vk_0c48e742-b0b6-4a80-8253-ed2d3f11a914 } ProvisioningSucceeded: Successfully provisioned volume pvc-d9ea072e-538b-4039-9d9e-f6abe1df86fa
Jun 12 08:28:02.893: INFO: At 2021-06-12 08:25:47 +0000 UTC - event for pvc-snapshottable-tester-2qx4l: {default-scheduler } Scheduled: Successfully assigned snapshotting-5494/pvc-snapshottable-tester-2qx4l to ip-172-20-33-120.ap-northeast-2.compute.internal
Jun 12 08:28:02.893: INFO: At 2021-06-12 08:26:03 +0000 UTC - event for pvc-snapshottable-tester-2qx4l: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-d9ea072e-538b-4039-9d9e-f6abe1df86fa" : rpc error: code = DeadlineExceeded desc = context deadline exceeded
Jun 12 08:28:02.893: INFO: At 2021-06-12 08:26:05 +0000 UTC - event for pvc-snapshottable-tester-2qx4l: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-d9ea072e-538b-4039-9d9e-f6abe1df86fa" 
Jun 12 08:28:02.893: INFO: At 2021-06-12 08:26:19 +0000 UTC - event for pvc-snapshottable-tester-2qx4l: {kubelet ip-172-20-33-120.ap-northeast-2.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" already present on machine
Jun 12 08:28:02.893: INFO: At 2021-06-12 08:26:19 +0000 UTC - event for pvc-snapshottable-tester-2qx4l: {kubelet ip-172-20-33-120.ap-northeast-2.compute.internal} Created: Created container volume-tester
Jun 12 08:28:02.893: INFO: At 2021-06-12 08:26:20 +0000 UTC - event for pvc-snapshottable-tester-2qx4l: {kubelet ip-172-20-33-120.ap-northeast-2.compute.internal} Started: Started container volume-tester
Jun 12 08:28:02.893: INFO: At 2021-06-12 08:26:22 +0000 UTC - event for snapshot-zk8s6: {snapshot-controller } CreatingSnapshot: Waiting for a snapshot snapshotting-5494/snapshot-zk8s6 to be created by the CSI driver.
Jun 12 08:28:02.893: INFO: At 2021-06-12 08:26:33 +0000 UTC - event for pvc-snapshottable-data-tester-g4spt: {default-scheduler } Scheduled: Successfully assigned snapshotting-5494/pvc-snapshottable-data-tester-g4spt to ip-172-20-58-164.ap-northeast-2.compute.internal
... skipping 8 lines ...
Jun 12 08:28:02.893: INFO: At 2021-06-12 08:26:56 +0000 UTC - event for restored-pvc-tester-vj8rr: {default-scheduler } Scheduled: Successfully assigned snapshotting-5494/restored-pvc-tester-vj8rr to ip-172-20-55-5.ap-northeast-2.compute.internal
Jun 12 08:28:02.893: INFO: At 2021-06-12 08:27:04 +0000 UTC - event for restored-pvc-tester-vj8rr: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-ffcaf00c-ed45-431b-8c75-69bc53ef1463" 
Jun 12 08:28:02.893: INFO: At 2021-06-12 08:27:12 +0000 UTC - event for restored-pvc-tester-vj8rr: {kubelet ip-172-20-55-5.ap-northeast-2.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" already present on machine
Jun 12 08:28:02.893: INFO: At 2021-06-12 08:27:12 +0000 UTC - event for restored-pvc-tester-vj8rr: {kubelet ip-172-20-55-5.ap-northeast-2.compute.internal} Created: Created container volume-tester
Jun 12 08:28:02.893: INFO: At 2021-06-12 08:27:13 +0000 UTC - event for restored-pvc-tester-vj8rr: {kubelet ip-172-20-55-5.ap-northeast-2.compute.internal} Started: Started container volume-tester
Jun 12 08:28:02.893: INFO: At 2021-06-12 08:27:16 +0000 UTC - event for restored-pvc-tester-vj8rr: {kubelet ip-172-20-55-5.ap-northeast-2.compute.internal} Killing: Stopping container volume-tester
Jun 12 08:28:02.893: INFO: At 2021-06-12 08:27:52 +0000 UTC - event for snapshot-zk8s6: {snapshot-controller } SnapshotFinalizerError: Failed to check and update snapshot: snapshot controller failed to update snapshotting-5494/snapshot-zk8s6 on API server: Operation cannot be fulfilled on volumesnapshots.snapshot.storage.k8s.io "snapshot-zk8s6": the object has been modified; please apply your changes to the latest version and try again
Jun 12 08:28:03.055: INFO: POD  NODE  PHASE  GRACE  CONDITIONS
Jun 12 08:28:03.055: INFO: 
Jun 12 08:28:03.218: INFO: 
Logging node info for node ip-172-20-33-120.ap-northeast-2.compute.internal
Jun 12 08:28:03.380: INFO: Node Info: &Node{ObjectMeta:{ip-172-20-33-120.ap-northeast-2.compute.internal    a9b78e8c-fd2d-401d-a236-12ea01f82c8d 12639 0 2021-06-12 08:17:04 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:t3.medium beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:ap-northeast-2 failure-domain.beta.kubernetes.io/zone:ap-northeast-2a kops.k8s.io/instancegroup:nodes-ap-northeast-2a kubernetes.io/arch:amd64 kubernetes.io/hostname:ip-172-20-33-120.ap-northeast-2.compute.internal kubernetes.io/os:linux kubernetes.io/role:node node-role.kubernetes.io/node: node.kubernetes.io/instance-type:t3.medium topology.ebs.csi.aws.com/zone:ap-northeast-2a topology.kubernetes.io/region:ap-northeast-2 topology.kubernetes.io/zone:ap-northeast-2a] map[csi.volume.kubernetes.io/nodeid:{"ebs.csi.aws.com":"i-0ba3e9a7fe85e3ae4"} node.alpha.kubernetes.io/ttl:0 projectcalico.org/IPv4Address:172.20.33.120/19 projectcalico.org/IPv4IPIPTunnelAddr:100.123.250.192 volumes.kubernetes.io/controller-managed-attach-detach:true] [] []  [{kops-controller Update v1 2021-06-12 08:17:04 +0000 UTC FieldsV1 {"f:metadata":{"f:labels":{"f:kops.k8s.io/instancegroup":{},"f:kubernetes.io/role":{},"f:node-role.kubernetes.io/node":{}}}}} {calico-node Update v1 2021-06-12 08:17:43 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4IPIPTunnelAddr":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}}} {kubelet Update v1 2021-06-12 08:25:55 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:csi.volume.kubernetes.io/nodeid":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.ebs.csi.aws.com/zone":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}},"f:status":{"f:allocatable":{"f:ephemeral-storage":{}},"f:capacity":{"f:ephemeral-storage":{}},"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{},"f:volumesInUse":{}}}} {kube-controller-manager Update v1 2021-06-12 08:26:05 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"100.96.1.0/24\"":{}}},"f:status":{"f:volumesAttached":{}}}}]},Spec:NodeSpec{PodCIDR:100.96.1.0/24,DoNotUseExternalID:,ProviderID:aws:///ap-northeast-2a/i-0ba3e9a7fe85e3ae4,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[100.96.1.0/24],},Status:NodeStatus{Capacity:ResourceList{cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{49895047168 0} {<nil>}  BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{4064751616 0} {<nil>} 3969484Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{44905542377 0} {<nil>} 44905542377 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{3959894016 0} {<nil>} 3867084Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2021-06-12 08:17:43 +0000 UTC,LastTransitionTime:2021-06-12 08:17:43 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2021-06-12 08:27:55 +0000 UTC,LastTransitionTime:2021-06-12 08:17:04 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2021-06-12 08:27:55 +0000 UTC,LastTransitionTime:2021-06-12 08:17:04 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2021-06-12 08:27:55 +0000 UTC,LastTransitionTime:2021-06-12 08:17:04 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2021-06-12 08:27:55 +0000 UTC,LastTransitionTime:2021-06-12 08:17:24 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:172.20.33.120,},NodeAddress{Type:ExternalIP,Address:13.125.3.65,},NodeAddress{Type:Hostname,Address:ip-172-20-33-120.ap-northeast-2.compute.internal,},NodeAddress{Type:InternalDNS,Address:ip-172-20-33-120.ap-northeast-2.compute.internal,},NodeAddress{Type:ExternalDNS,Address:ec2-13-125-3-65.ap-northeast-2.compute.amazonaws.com,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:ec2ca076f9da89b9b68e98207f68e4be,SystemUUID:ec2ca076-f9da-89b9-b68e-98207f68e4be,BootID:a8389a08-700f-4860-8610-2cc4b1a67aae,KernelVersion:5.4.0-1045-aws,OSImage:Ubuntu 20.04.2 LTS,ContainerRuntimeVersion:containerd://1.4.6,KubeletVersion:v1.21.0,KubeProxyVersion:v1.21.0,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[k8s.gcr.io/provider-aws/aws-ebs-csi-driver@sha256:a0294bf95fd94eabdc9b313b6c16232019a8707c711c031a2f99ab1f919560bd k8s.gcr.io/provider-aws/aws-ebs-csi-driver:v1.0.0],SizeBytes:67079979,},ContainerImage{Names:[docker.io/calico/node@sha256:bc4a631d553b38fdc169ea4cb8027fa894a656e80d68d513359a4b9d46836b55 docker.io/calico/node:v3.19.1],SizeBytes:58671776,},ContainerImage{Names:[k8s.gcr.io/kube-proxy@sha256:326199e7a5232bf7531a3058e9811c925b07085f33fa882558cc4e89379b9109 k8s.gcr.io/kube-proxy:v1.21.0],SizeBytes:50134170,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/agnhost@sha256:8bd76a6a7778e203b61e18e5ee85b1faf52e6a30eb07e445a165ab90fe9633e3 k8s.gcr.io/e2e-test-images/agnhost:2.31],SizeBytes:49692421,},ContainerImage{Names:[docker.io/calico/cni@sha256:f301171be0add870152483fcce71b28cafb8e910f61ff003032e9b1053b062c4 docker.io/calico/cni:v3.19.1],SizeBytes:48338203,},ContainerImage{Names:[k8s.gcr.io/build-image/debian-iptables@sha256:abe8cef9e116f2d5ec1175c386e33841ff3386779138b425af876384b0fd7ccb k8s.gcr.io/build-image/debian-iptables:buster-v1.5.0],SizeBytes:38088315,},ContainerImage{Names:[quay.io/jetstack/cert-manager-webhook@sha256:41eacd93a30b566b780a6ae525b2547d2a87f1ec5f067fc02840a220aeb0c3f7 quay.io/jetstack/cert-manager-webhook:v1.3.1],SizeBytes:19734169,},ContainerImage{Names:[quay.io/jetstack/cert-manager-cainjector@sha256:51c0df411b66aa175e9fc6840f3135d55b52c3781d0b3d4aa10862066d460193 quay.io/jetstack/cert-manager-cainjector:v1.3.1],SizeBytes:19215137,},ContainerImage{Names:[k8s.gcr.io/sig-storage/snapshot-validation-webhook@sha256:931a753e6428914f5393e3bba5f250f952c57dc2e9ddd16c37593a8f02b6715e k8s.gcr.io/sig-storage/snapshot-validation-webhook:v4.1.1],SizeBytes:18566421,},ContainerImage{Names:[docker.io/calico/pod2daemon-flexvol@sha256:bcac7dc4f1301b062d91a177a52d13716907636975c44131fb8350e7f851c944 docker.io/calico/pod2daemon-flexvol:v3.19.1],SizeBytes:9328155,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-node-driver-registrar@sha256:a61d309da54641db41fb8f35718f744e9f730d4d0384f8c4b186ddc9f06cbd5f k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.1.0],SizeBytes:9068367,},ContainerImage{Names:[k8s.gcr.io/sig-storage/livenessprobe@sha256:48da0e4ed7238ad461ea05f68c25921783c37b315f21a5c5a2780157a6460994 k8s.gcr.io/sig-storage/livenessprobe:v2.2.0],SizeBytes:8279778,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/nginx@sha256:503b7abb89e57383eba61cc8a9cb0b495ea575c516108f7d972a6ff6e1ab3c9b k8s.gcr.io/e2e-test-images/nginx:1.14-1],SizeBytes:6979365,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/busybox@sha256:39e1e963e5310e9c313bad51523be012ede7b35bb9316517d19089a010356592 k8s.gcr.io/e2e-test-images/busybox:1.29-1],SizeBytes:732746,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:927d98197ec1141a368550822d18fa1c60bdae27b78b0c004f705f548c07814f k8s.gcr.io/pause:3.2],SizeBytes:299513,},},VolumesInUse:[kubernetes.io/csi/ebs.csi.aws.com^vol-04b315cb02ac3762e kubernetes.io/csi/ebs.csi.aws.com^vol-097a39103f87b9810 kubernetes.io/csi/ebs.csi.aws.com^vol-0bae86d0fa737b7ac],VolumesAttached:[]AttachedVolume{AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-097a39103f87b9810,DevicePath:,},AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-04b315cb02ac3762e,DevicePath:,},AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-0bae86d0fa737b7ac,DevicePath:,},},Config:nil,},}
Jun 12 08:28:03.380: INFO: 
... skipping 200 lines ...
    /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:108
      
      /tmp/kops.rbyVcryct/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.rbyVcryct/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-5494 exec restored-pvc-tester-vj8rr --namespace=snapshotting-5494 -- 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-5494 exec restored-pvc-tester-vj8rr --namespace=snapshotting-5494 -- 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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:602
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
... skipping 417 lines ...
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 12 08:28:23.740: 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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Jun 12 08:28:24.708: INFO: found topology map[topology.kubernetes.io/zone:ap-northeast-2a]
Jun 12 08:28:24.708: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 12 08:28:24.708: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.rbyVcryct/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.rbyVcryct/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (delayed binding)] topology
    /tmp/kops.rbyVcryct/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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 30 lines ...
Jun 12 08:27:53.306: INFO: Creating resource for dynamic PV
Jun 12 08:27:53.306: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-2819cjd4r
STEP: creating a claim
STEP: Expanding non-expandable pvc
Jun 12 08:27:53.790: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 12 08:27:54.113: INFO: Error updating pvc awstjfbm: PersistentVolumeClaim "awstjfbm" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2819cjd4r",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun 12 08:28:24.761: INFO: Error updating pvc awstjfbm: PersistentVolumeClaim "awstjfbm" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 210 lines ...
Jun 12 08:28:05.149: INFO: Pod aws-client still exists
Jun 12 08:28:06.992: INFO: Waiting for pod aws-client to disappear
Jun 12 08:28:07.149: INFO: Pod aws-client still exists
Jun 12 08:28:08.992: INFO: Waiting for pod aws-client to disappear
Jun 12 08:28:09.150: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun 12 08:28:09.907: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0a48cdb2f59d6d36d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a48cdb2f59d6d36d is currently attached to i-045954f58307d9775
	status code: 400, request id: e0e49db7-b92f-43a7-b850-31d3b221fe7e
Jun 12 08:28:15.736: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0a48cdb2f59d6d36d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a48cdb2f59d6d36d is currently attached to i-045954f58307d9775
	status code: 400, request id: 6998afb2-bfd2-43e1-bcce-0a12993d3fe3
Jun 12 08:28:21.502: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-0a48cdb2f59d6d36d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a48cdb2f59d6d36d is currently attached to i-045954f58307d9775
	status code: 400, request id: d170c078-5ada-49db-8ef8-66177e7d9dc6
Jun 12 08:28:27.259: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-0a48cdb2f59d6d36d".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 08:28:27.259: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-3996" for this suite.
... skipping 41 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.rbyVcryct/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.rbyVcryct/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.rbyVcryct/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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 230 lines ...
Jun 12 08:28:01.341: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-5762-e2e-schfs92      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-5762    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-5762-e2e-schfs92,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-5762    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-5762-e2e-schfs92,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-5762    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-5762-e2e-schfs92,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-5762-e2e-schfs92    fa98ed29-f89f-4377-8226-ee764b00c9ab 12847 0 2021-06-12 08:28:01 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-12 08:28:01 +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-cqjjg pvc- provisioning-5762  d7d10d59-8fa6-4056-bdc5-496109a9b552 12869 0 2021-06-12 08:28:02 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-12 08:28:02 +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-5762-e2e-schfs92,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-d4700657-6db8-40af-8bbf-6bb6e3d41e51 in namespace provisioning-5762
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun 12 08:28:13.063: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-7mp6q" in namespace "provisioning-5762" to be "Succeeded or Failed"
Jun 12 08:28:13.217: INFO: Pod "pvc-volume-tester-writer-7mp6q": Phase="Pending", Reason="", readiness=false. Elapsed: 153.713963ms
Jun 12 08:28:15.371: INFO: Pod "pvc-volume-tester-writer-7mp6q": Phase="Pending", Reason="", readiness=false. Elapsed: 2.308154533s
Jun 12 08:28:17.525: INFO: Pod "pvc-volume-tester-writer-7mp6q": Phase="Pending", Reason="", readiness=false. Elapsed: 4.462498368s
Jun 12 08:28:19.679: INFO: Pod "pvc-volume-tester-writer-7mp6q": Phase="Pending", Reason="", readiness=false. Elapsed: 6.616515943s
Jun 12 08:28:21.835: INFO: Pod "pvc-volume-tester-writer-7mp6q": Phase="Pending", Reason="", readiness=false. Elapsed: 8.772083028s
Jun 12 08:28:23.989: INFO: Pod "pvc-volume-tester-writer-7mp6q": Phase="Pending", Reason="", readiness=false. Elapsed: 10.926351961s
Jun 12 08:28:26.144: INFO: Pod "pvc-volume-tester-writer-7mp6q": Phase="Pending", Reason="", readiness=false. Elapsed: 13.081346816s
Jun 12 08:28:28.305: INFO: Pod "pvc-volume-tester-writer-7mp6q": Phase="Pending", Reason="", readiness=false. Elapsed: 15.24183589s
Jun 12 08:28:30.460: INFO: Pod "pvc-volume-tester-writer-7mp6q": Phase="Pending", Reason="", readiness=false. Elapsed: 17.396574975s
Jun 12 08:28:32.614: INFO: Pod "pvc-volume-tester-writer-7mp6q": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.551488821s
STEP: Saw pod success
Jun 12 08:28:32.614: INFO: Pod "pvc-volume-tester-writer-7mp6q" satisfied condition "Succeeded or Failed"
Jun 12 08:28:32.924: INFO: Pod pvc-volume-tester-writer-7mp6q has the following logs: 
Jun 12 08:28:32.924: INFO: Deleting pod "pvc-volume-tester-writer-7mp6q" in namespace "provisioning-5762"
Jun 12 08:28:33.104: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-7mp6q" 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-55-5.ap-northeast-2.compute.internal"
Jun 12 08:28:33.722: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-9hprz" in namespace "provisioning-5762" to be "Succeeded or Failed"
Jun 12 08:28:33.876: INFO: Pod "pvc-volume-tester-reader-9hprz": Phase="Pending", Reason="", readiness=false. Elapsed: 153.746008ms
Jun 12 08:28:36.031: INFO: Pod "pvc-volume-tester-reader-9hprz": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.308563054s
STEP: Saw pod success
Jun 12 08:28:36.031: INFO: Pod "pvc-volume-tester-reader-9hprz" satisfied condition "Succeeded or Failed"
Jun 12 08:28:36.347: INFO: Pod pvc-volume-tester-reader-9hprz has the following logs: hello world

Jun 12 08:28:36.347: INFO: Deleting pod "pvc-volume-tester-reader-9hprz" in namespace "provisioning-5762"
Jun 12 08:28:36.510: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-9hprz" to be fully deleted
Jun 12 08:28:36.664: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-cqjjg] to have phase Bound
Jun 12 08:28:36.818: INFO: PersistentVolumeClaim pvc-cqjjg found and phase=Bound (153.617728ms)
... skipping 80 lines ...
Jun 12 08:28:24.073: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-8330-e2e-scfxgwf
STEP: creating a claim
Jun 12 08:28:24.235: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Jun 12 08:28:24.557: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 12 08:28:24.878: INFO: Error updating pvc ebs.csi.aws.comllk6k: PersistentVolumeClaim "ebs.csi.aws.comllk6k" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8330-e2e-scfxgwf",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun 12 08:28:55.522: INFO: Error updating pvc ebs.csi.aws.comllk6k: PersistentVolumeClaim "ebs.csi.aws.comllk6k" is invalid: spec: Forbidden: spec is 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 ...
Jun 12 08:27:47.970: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3336js7kp
STEP: creating a claim
Jun 12 08:27:48.128: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-z9wm
STEP: Creating a pod to test subpath
Jun 12 08:27:48.607: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-z9wm" in namespace "provisioning-3336" to be "Succeeded or Failed"
Jun 12 08:27:48.765: INFO: Pod "pod-subpath-test-dynamicpv-z9wm": Phase="Pending", Reason="", readiness=false. Elapsed: 158.131158ms
Jun 12 08:27:50.925: INFO: Pod "pod-subpath-test-dynamicpv-z9wm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.317967117s
Jun 12 08:27:53.083: INFO: Pod "pod-subpath-test-dynamicpv-z9wm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.476000501s
Jun 12 08:27:55.250: INFO: Pod "pod-subpath-test-dynamicpv-z9wm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.642858315s
Jun 12 08:27:57.407: INFO: Pod "pod-subpath-test-dynamicpv-z9wm": Phase="Pending", Reason="", readiness=false. Elapsed: 8.800546925s
Jun 12 08:27:59.565: INFO: Pod "pod-subpath-test-dynamicpv-z9wm": Phase="Pending", Reason="", readiness=false. Elapsed: 10.958531798s
Jun 12 08:28:01.725: INFO: Pod "pod-subpath-test-dynamicpv-z9wm": Phase="Pending", Reason="", readiness=false. Elapsed: 13.117978924s
Jun 12 08:28:03.889: INFO: Pod "pod-subpath-test-dynamicpv-z9wm": Phase="Pending", Reason="", readiness=false. Elapsed: 15.282148377s
Jun 12 08:28:06.046: INFO: Pod "pod-subpath-test-dynamicpv-z9wm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 17.439693909s
STEP: Saw pod success
Jun 12 08:28:06.046: INFO: Pod "pod-subpath-test-dynamicpv-z9wm" satisfied condition "Succeeded or Failed"
Jun 12 08:28:06.206: INFO: Trying to get logs from node ip-172-20-58-164.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-z9wm container test-container-subpath-dynamicpv-z9wm: <nil>
STEP: delete the pod
Jun 12 08:28:06.554: INFO: Waiting for pod pod-subpath-test-dynamicpv-z9wm to disappear
Jun 12 08:28:06.713: INFO: Pod pod-subpath-test-dynamicpv-z9wm no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-z9wm
Jun 12 08:28:06.713: INFO: Deleting pod "pod-subpath-test-dynamicpv-z9wm" in namespace "provisioning-3336"
STEP: Creating pod pod-subpath-test-dynamicpv-z9wm
STEP: Creating a pod to test subpath
Jun 12 08:28:07.030: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-z9wm" in namespace "provisioning-3336" to be "Succeeded or Failed"
Jun 12 08:28:07.187: INFO: Pod "pod-subpath-test-dynamicpv-z9wm": Phase="Pending", Reason="", readiness=false. Elapsed: 157.327982ms
Jun 12 08:28:09.345: INFO: Pod "pod-subpath-test-dynamicpv-z9wm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.314953327s
Jun 12 08:28:11.503: INFO: Pod "pod-subpath-test-dynamicpv-z9wm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.472745673s
Jun 12 08:28:13.660: INFO: Pod "pod-subpath-test-dynamicpv-z9wm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.630431543s
Jun 12 08:28:15.818: INFO: Pod "pod-subpath-test-dynamicpv-z9wm": Phase="Pending", Reason="", readiness=false. Elapsed: 8.787958818s
Jun 12 08:28:17.976: INFO: Pod "pod-subpath-test-dynamicpv-z9wm": Phase="Pending", Reason="", readiness=false. Elapsed: 10.945903539s
... skipping 7 lines ...
Jun 12 08:28:35.245: INFO: Pod "pod-subpath-test-dynamicpv-z9wm": Phase="Pending", Reason="", readiness=false. Elapsed: 28.215297907s
Jun 12 08:28:37.403: INFO: Pod "pod-subpath-test-dynamicpv-z9wm": Phase="Pending", Reason="", readiness=false. Elapsed: 30.373078654s
Jun 12 08:28:39.563: INFO: Pod "pod-subpath-test-dynamicpv-z9wm": Phase="Pending", Reason="", readiness=false. Elapsed: 32.533120713s
Jun 12 08:28:41.722: INFO: Pod "pod-subpath-test-dynamicpv-z9wm": Phase="Pending", Reason="", readiness=false. Elapsed: 34.691641233s
Jun 12 08:28:43.880: INFO: Pod "pod-subpath-test-dynamicpv-z9wm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 36.850484023s
STEP: Saw pod success
Jun 12 08:28:43.880: INFO: Pod "pod-subpath-test-dynamicpv-z9wm" satisfied condition "Succeeded or Failed"
Jun 12 08:28:44.038: INFO: Trying to get logs from node ip-172-20-46-122.ap-northeast-2.compute.internal pod pod-subpath-test-dynamicpv-z9wm container test-container-subpath-dynamicpv-z9wm: <nil>
STEP: delete the pod
Jun 12 08:28:44.361: INFO: Waiting for pod pod-subpath-test-dynamicpv-z9wm to disappear
Jun 12 08:28:44.518: INFO: Pod pod-subpath-test-dynamicpv-z9wm no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-z9wm
Jun 12 08:28:44.518: INFO: Deleting pod "pod-subpath-test-dynamicpv-z9wm" in namespace "provisioning-3336"
... skipping 269 lines ...
Jun 12 08:27:13.489: INFO: Creating resource for dynamic PV
Jun 12 08:27:13.490: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-948-e2e-scdzhs2
STEP: creating a claim
Jun 12 08:27:13.645: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 12 08:27:14.117: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-vljjw" in namespace "snapshotting-948" to be "Succeeded or Failed"
Jun 12 08:27:14.272: INFO: Pod "pvc-snapshottable-tester-vljjw": Phase="Pending", Reason="", readiness=false. Elapsed: 154.220999ms
Jun 12 08:27:16.427: INFO: Pod "pvc-snapshottable-tester-vljjw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.309958887s
Jun 12 08:27:18.584: INFO: Pod "pvc-snapshottable-tester-vljjw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.466650799s
Jun 12 08:27:20.738: INFO: Pod "pvc-snapshottable-tester-vljjw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.621010826s
Jun 12 08:27:22.893: INFO: Pod "pvc-snapshottable-tester-vljjw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.775804881s
Jun 12 08:27:25.048: INFO: Pod "pvc-snapshottable-tester-vljjw": Phase="Pending", Reason="", readiness=false. Elapsed: 10.930183176s
Jun 12 08:27:27.203: INFO: Pod "pvc-snapshottable-tester-vljjw": Phase="Pending", Reason="", readiness=false. Elapsed: 13.08559393s
Jun 12 08:27:29.358: INFO: Pod "pvc-snapshottable-tester-vljjw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 15.240226598s
STEP: Saw pod success
Jun 12 08:27:29.358: INFO: Pod "pvc-snapshottable-tester-vljjw" satisfied condition "Succeeded or Failed"
Jun 12 08:27:29.670: INFO: Pod pvc-snapshottable-tester-vljjw has the following logs: 
Jun 12 08:27:29.671: INFO: Deleting pod "pvc-snapshottable-tester-vljjw" in namespace "snapshotting-948"
Jun 12 08:27:29.830: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-vljjw" to be fully deleted
Jun 12 08:27:29.984: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comwptbw] to have phase Bound
Jun 12 08:27:30.138: INFO: PersistentVolumeClaim ebs.csi.aws.comwptbw found and phase=Bound (153.938548ms)
STEP: [init] checking the claim
... skipping 19 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:243
STEP: checking the snapshot
STEP: checking the SnapshotContent
STEP: Modifying source data test
STEP: modifying the data in the source PVC
Jun 12 08:27:51.287: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-gklz7" in namespace "snapshotting-948" to be "Succeeded or Failed"
Jun 12 08:27:51.441: INFO: Pod "pvc-snapshottable-data-tester-gklz7": Phase="Pending", Reason="", readiness=false. Elapsed: 154.203801ms
Jun 12 08:27:53.596: INFO: Pod "pvc-snapshottable-data-tester-gklz7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.308786732s
Jun 12 08:27:55.752: INFO: Pod "pvc-snapshottable-data-tester-gklz7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.464347686s
Jun 12 08:27:57.906: INFO: Pod "pvc-snapshottable-data-tester-gklz7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.618855502s
Jun 12 08:28:00.062: INFO: Pod "pvc-snapshottable-data-tester-gklz7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.774544175s
Jun 12 08:28:02.216: INFO: Pod "pvc-snapshottable-data-tester-gklz7": Phase="Pending", Reason="", readiness=false. Elapsed: 10.928756859s
Jun 12 08:28:04.372: INFO: Pod "pvc-snapshottable-data-tester-gklz7": Phase="Pending", Reason="", readiness=false. Elapsed: 13.084273168s
Jun 12 08:28:06.526: INFO: Pod "pvc-snapshottable-data-tester-gklz7": Phase="Pending", Reason="", readiness=false. Elapsed: 15.2385423s
Jun 12 08:28:08.683: INFO: Pod "pvc-snapshottable-data-tester-gklz7": Phase="Pending", Reason="", readiness=false. Elapsed: 17.395341474s
Jun 12 08:28:10.837: INFO: Pod "pvc-snapshottable-data-tester-gklz7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.549848685s
STEP: Saw pod success
Jun 12 08:28:10.837: INFO: Pod "pvc-snapshottable-data-tester-gklz7" satisfied condition "Succeeded or Failed"
Jun 12 08:28:11.149: INFO: Pod pvc-snapshottable-data-tester-gklz7 has the following logs: 
Jun 12 08:28:11.149: INFO: Deleting pod "pvc-snapshottable-data-tester-gklz7" in namespace "snapshotting-948"
Jun 12 08:28:11.316: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-gklz7" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 12 08:28:26.094: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-948 exec restored-pvc-tester-jf7fc --namespace=snapshotting-948 -- cat /mnt/test/data'
... skipping 117 lines ...
Jun 12 08:26:46.513: INFO: Creating resource for dynamic PV
Jun 12 08:26:46.513: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-3001-e2e-scntz8w
STEP: creating a claim
Jun 12 08:26:46.680: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 12 08:26:47.161: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-6c9ph" in namespace "snapshotting-3001" to be "Succeeded or Failed"
Jun 12 08:26:47.320: INFO: Pod "pvc-snapshottable-tester-6c9ph": Phase="Pending", Reason="", readiness=false. Elapsed: 159.38132ms
Jun 12 08:26:49.481: INFO: Pod "pvc-snapshottable-tester-6c9ph": Phase="Pending", Reason="", readiness=false. Elapsed: 2.32008364s
Jun 12 08:26:51.642: INFO: Pod "pvc-snapshottable-tester-6c9ph": Phase="Pending", Reason="", readiness=false. Elapsed: 4.481404641s
Jun 12 08:26:53.801: INFO: Pod "pvc-snapshottable-tester-6c9ph": Phase="Pending", Reason="", readiness=false. Elapsed: 6.640474306s
Jun 12 08:26:55.960: INFO: Pod "pvc-snapshottable-tester-6c9ph": Phase="Pending", Reason="", readiness=false. Elapsed: 8.799499196s
Jun 12 08:26:58.121: INFO: Pod "pvc-snapshottable-tester-6c9ph": Phase="Pending", Reason="", readiness=false. Elapsed: 10.960502272s
Jun 12 08:27:00.281: INFO: Pod "pvc-snapshottable-tester-6c9ph": Phase="Pending", Reason="", readiness=false. Elapsed: 13.119961338s
Jun 12 08:27:02.440: INFO: Pod "pvc-snapshottable-tester-6c9ph": Phase="Pending", Reason="", readiness=false. Elapsed: 15.27927424s
Jun 12 08:27:04.599: INFO: Pod "pvc-snapshottable-tester-6c9ph": Phase="Pending", Reason="", readiness=false. Elapsed: 17.438647821s
Jun 12 08:27:06.759: INFO: Pod "pvc-snapshottable-tester-6c9ph": Phase="Pending", Reason="", readiness=false. Elapsed: 19.598038168s
Jun 12 08:27:08.919: INFO: Pod "pvc-snapshottable-tester-6c9ph": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.758200217s
STEP: Saw pod success
Jun 12 08:27:08.919: INFO: Pod "pvc-snapshottable-tester-6c9ph" satisfied condition "Succeeded or Failed"
Jun 12 08:27:09.238: INFO: Pod pvc-snapshottable-tester-6c9ph has the following logs: 
Jun 12 08:27:09.238: INFO: Deleting pod "pvc-snapshottable-tester-6c9ph" in namespace "snapshotting-3001"
Jun 12 08:27:09.403: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-6c9ph" to be fully deleted
Jun 12 08:27:09.562: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comp6zj7] to have phase Bound
Jun 12 08:27:09.720: INFO: PersistentVolumeClaim ebs.csi.aws.comp6zj7 found and phase=Bound (158.50514ms)
STEP: [init] checking the claim
... skipping 45 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:243
STEP: checking the snapshot
STEP: checking the SnapshotContent
STEP: Modifying source data test
STEP: modifying the data in the source PVC
Jun 12 08:27:49.833: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-zrf5n" in namespace "snapshotting-3001" to be "Succeeded or Failed"
Jun 12 08:27:49.992: INFO: Pod "pvc-snapshottable-data-tester-zrf5n": Phase="Pending", Reason="", readiness=false. Elapsed: 158.800729ms
Jun 12 08:27:52.151: INFO: Pod "pvc-snapshottable-data-tester-zrf5n": Phase="Pending", Reason="", readiness=false. Elapsed: 2.317896895s
Jun 12 08:27:54.310: INFO: Pod "pvc-snapshottable-data-tester-zrf5n": Phase="Pending", Reason="", readiness=false. Elapsed: 4.476780811s
Jun 12 08:27:56.470: INFO: Pod "pvc-snapshottable-data-tester-zrf5n": Phase="Pending", Reason="", readiness=false. Elapsed: 6.637276963s
Jun 12 08:27:58.631: INFO: Pod "pvc-snapshottable-data-tester-zrf5n": Phase="Pending", Reason="", readiness=false. Elapsed: 8.797617189s
Jun 12 08:28:00.790: INFO: Pod "pvc-snapshottable-data-tester-zrf5n": Phase="Pending", Reason="", readiness=false. Elapsed: 10.956651009s
Jun 12 08:28:02.949: INFO: Pod "pvc-snapshottable-data-tester-zrf5n": Phase="Pending", Reason="", readiness=false. Elapsed: 13.116011008s
Jun 12 08:28:05.109: INFO: Pod "pvc-snapshottable-data-tester-zrf5n": Phase="Pending", Reason="", readiness=false. Elapsed: 15.27632811s
Jun 12 08:28:07.274: INFO: Pod "pvc-snapshottable-data-tester-zrf5n": Phase="Succeeded", Reason="", readiness=false. Elapsed: 17.441410732s
STEP: Saw pod success
Jun 12 08:28:07.274: INFO: Pod "pvc-snapshottable-data-tester-zrf5n" satisfied condition "Succeeded or Failed"
Jun 12 08:28:07.594: INFO: Pod pvc-snapshottable-data-tester-zrf5n has the following logs: 
Jun 12 08:28:07.594: INFO: Deleting pod "pvc-snapshottable-data-tester-zrf5n" in namespace "snapshotting-3001"
Jun 12 08:28:07.758: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-zrf5n" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 12 08:28:32.562: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-3001 exec restored-pvc-tester-6b8jn --namespace=snapshotting-3001 -- cat /mnt/test/data'
... skipping 248 lines ...
    /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:108
      
      /tmp/kops.rbyVcryct/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.rbyVcryct/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-3001 exec restored-pvc-tester-6b8jn --namespace=snapshotting-3001 -- 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-3001 exec restored-pvc-tester-6b8jn --namespace=snapshotting-3001 -- 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.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:602
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
... skipping 776 lines ...
Jun 12 08:29:40.098: INFO: Waiting for pod aws-client to disappear
Jun 12 08:29:40.260: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 12 08:29:40.260: INFO: Deleting PersistentVolumeClaim "pvc-r4wf2"
Jun 12 08:29:40.422: INFO: Deleting PersistentVolume "aws-8jn92"
Jun 12 08:29:41.337: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-015220eae5b02bc70", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-015220eae5b02bc70 is currently attached to i-0bbfca73506739cca
	status code: 400, request id: 2f676a1f-9416-4f13-8974-dcc43b007ccc
Jun 12 08:29:47.095: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-015220eae5b02bc70", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-015220eae5b02bc70 is currently attached to i-0bbfca73506739cca
	status code: 400, request id: 1a167b87-58c6-47be-be16-5b930992dc27
Jun 12 08:29:52.861: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-015220eae5b02bc70", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-015220eae5b02bc70 is currently attached to i-0bbfca73506739cca
	status code: 400, request id: ad710428-b8b4-4ac3-ae91-7336d008ad50
Jun 12 08:29:58.662: INFO: Couldn't delete PD "aws://ap-northeast-2a/vol-015220eae5b02bc70", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-015220eae5b02bc70 is currently attached to i-0bbfca73506739cca
	status code: 400, request id: 0e00a7a0-cb10-4e96-a208-e39dc6f35c0e
Jun 12 08:30:04.457: INFO: Successfully deleted PD "aws://ap-northeast-2a/vol-015220eae5b02bc70".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 12 08:30:04.458: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-1445" for this suite.
... skipping 22 lines ...
Jun 12 08:27:22.346: INFO: Creating resource for dynamic PV
Jun 12 08:27:22.346: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-3202-e2e-scx2w8r
STEP: creating a claim
Jun 12 08:27:22.508: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 12 08:27:22.994: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-26sd4" in namespace "snapshotting-3202" to be "Succeeded or Failed"
Jun 12 08:27:23.154: INFO: Pod "pvc-snapshottable-tester-26sd4": Phase="Pending", Reason="", readiness=false. Elapsed: 160.332156ms
Jun 12 08:27:25.315: INFO: Pod "pvc-snapshottable-tester-26sd4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.321321754s
Jun 12 08:27:27.476: INFO: Pod "pvc-snapshottable-tester-26sd4": Phase="Pending", Reason="", readiness=false. Elapsed: 4.482017548s
Jun 12 08:27:29.637: INFO: Pod "pvc-snapshottable-tester-26sd4": Phase="Pending", Reason="", readiness=false. Elapsed: 6.642976589s
Jun 12 08:27:31.798: INFO: Pod "pvc-snapshottable-tester-26sd4": Phase="Pending", Reason="", readiness=false. Elapsed: 8.804030781s
Jun 12 08:27:33.959: INFO: Pod "pvc-snapshottable-tester-26sd4": Phase="Pending", Reason="", readiness=false. Elapsed: 10.965492374s
Jun 12 08:27:36.120: INFO: Pod "pvc-snapshottable-tester-26sd4": Phase="Pending", Reason="", readiness=false. Elapsed: 13.126330306s
Jun 12 08:27:38.282: INFO: Pod "pvc-snapshottable-tester-26sd4": Phase="Pending", Reason="", readiness=false. Elapsed: 15.287643476s
Jun 12 08:27:40.443: INFO: Pod "pvc-snapshottable-tester-26sd4": Phase="Pending", Reason="", readiness=false. Elapsed: 17.44920193s
Jun 12 08:27:42.604: INFO: Pod "pvc-snapshottable-tester-26sd4": Phase="Pending", Reason="", readiness=false. Elapsed: 19.609838528s
Jun 12 08:27:44.765: INFO: Pod "pvc-snapshottable-tester-26sd4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.770887899s
STEP: Saw pod success
Jun 12 08:27:44.765: INFO: Pod "pvc-snapshottable-tester-26sd4" satisfied condition "Succeeded or Failed"
Jun 12 08:27:45.090: INFO: Pod pvc-snapshottable-tester-26sd4 has the following logs: 
Jun 12 08:27:45.090: INFO: Deleting pod "pvc-snapshottable-tester-26sd4" in namespace "snapshotting-3202"
Jun 12 08:27:45.256: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-26sd4" to be fully deleted
Jun 12 08:27:45.416: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.com9mpwc] to have phase Bound
Jun 12 08:27:45.577: INFO: PersistentVolumeClaim ebs.csi.aws.com9mpwc found and phase=Bound (160.585336ms)
STEP: [init] checking the claim
... skipping 49 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:243
STEP: checking the snapshot
STEP: checking the SnapshotContent
STEP: Modifying source data test
STEP: modifying the data in the source PVC
Jun 12 08:28:34.426: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-gg89p" in namespace "snapshotting-3202" to be "Succeeded or Failed"
Jun 12 08:28:34.586: INFO: Pod "pvc-snapshottable-data-tester-gg89p": Phase="Pending", Reason="", readiness=false. Elapsed: 160.287871ms
Jun 12 08:28:36.748: INFO: Pod "pvc-snapshottable-data-tester-gg89p": Phase="Pending", Reason="", readiness=false. Elapsed: 2.32171051s
Jun 12 08:28:38.914: INFO: Pod "pvc-snapshottable-data-tester-gg89p": Phase="Pending", Reason="", readiness=false. Elapsed: 4.488018847s
Jun 12 08:28:41.075: INFO: Pod "pvc-snapshottable-data-tester-gg89p": Phase="Pending", Reason="", readiness=false. Elapsed: 6.648603093s
Jun 12 08:28:43.236: INFO: Pod "pvc-snapshottable-data-tester-gg89p": Phase="Pending", Reason="", readiness=false. Elapsed: 8.809545033s
Jun 12 08:28:45.397: INFO: Pod "pvc-snapshottable-data-tester-gg89p": Phase="Pending", Reason="", readiness=false. Elapsed: 10.970933975s
Jun 12 08:28:47.559: INFO: Pod "pvc-snapshottable-data-tester-gg89p": Phase="Succeeded", Reason="", readiness=false. Elapsed: 13.132719541s
STEP: Saw pod success
Jun 12 08:28:47.559: INFO: Pod "pvc-snapshottable-data-tester-gg89p" satisfied condition "Succeeded or Failed"
Jun 12 08:28:47.882: INFO: Pod pvc-snapshottable-data-tester-gg89p has the following logs: 
Jun 12 08:28:47.882: INFO: Deleting pod "pvc-snapshottable-data-tester-gg89p" in namespace "snapshotting-3202"
Jun 12 08:28:48.049: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-gg89p" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 12 08:29:12.854: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-3202 exec restored-pvc-tester-rtwrq --namespace=snapshotting-3202 -- cat /mnt/test/data'
... skipping 593 lines ...
    /tmp/kops.rbyVcryct/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/multivolume.go:164
------------------------------


Summarizing 2 Failures:

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

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

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


Ginkgo ran 1 suite in 10m56.137706805s
Test Suite Failed
+ kops-finish
+ kubetest2 kops -v=2 --cloud-provider=aws --cluster-name=e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --admin-access= --kops-binary-path=/home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops --down
I0612 08:31:13.482734   26735 app.go:59] RunDir for this run: "/logs/artifacts/02458300-cb55-11eb-ab6f-62c732df09e9"
I0612 08:31:13.483015   26735 app.go:90] ID for this run: "02458300-cb55-11eb-ab6f-62c732df09e9"
I0612 08:31:13.483170   26735 dumplogs.go:38] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops toolbox dump --name e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ubuntu
I0612 08:31:13.498465   26741 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
... skipping 1445 lines ...