This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-06-07 00:02
Elapsed30m41s
Revisionmaster

No Test Failures!


Error lines from build-log.txt

... skipping 509 lines ...
I0607 00:07:45.483581   15327 up.go:43] Cleaning up any leaked resources from previous cluster
I0607 00:07:45.483591   15327 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
I0607 00:07:45.498732   15333 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0607 00:07:45.499350   15333 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io" not found
W0607 00:07:46.020484   15327 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0607 00:07:46.020547   15327 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
I0607 00:07:46.034654   15343 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0607 00:07:46.034737   15343 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io" not found
I0607 00:07:46.522191   15327 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/06/07 00:07:46 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
I0607 00:07:46.534280   15327 http.go:37] curl https://ip.jsb.workers.dev
I0607 00:07:46.677051   15327 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.71.166.216/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones us-west-2a --master-size c5.large
I0607 00:07:46.692441   15357 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0607 00:07:46.692822   15357 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I0607 00:07:46.737435   15357 create_cluster.go:728] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0607 00:07:47.319395   15357 new_cluster.go:1051]  Cloud Provider ID = aws
... skipping 40 lines ...

I0607 00:08:13.830972   15327 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
I0607 00:08:13.846239   15378 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0607 00:08:13.846324   15378 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io

W0607 00:08:14.967676   15378 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-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-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
W0607 00:08:25.002873   15378 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-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
W0607 00:08:35.046061   15378 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-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
W0607 00:08:45.080765   15378 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-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
W0607 00:08:55.126929   15378 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-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
W0607 00:09:05.164376   15378 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-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
W0607 00:09:15.208301   15378 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-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
W0607 00:09:25.243391   15378 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-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
W0607 00:09:35.351258   15378 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-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
W0607 00:09:45.406989   15378 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-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
W0607 00:09:55.569879   15378 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-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
W0607 00:10:05.601065   15378 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-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
W0607 00:10:15.633523   15378 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-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
W0607 00:10:25.672693   15378 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-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
W0607 00:10:35.705223   15378 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-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
W0607 00:10:45.740513   15378 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-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
W0607 00:10:55.777770   15378 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-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
W0607 00:11:05.807548   15378 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-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
W0607 00:11:15.840897   15378 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-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
W0607 00:11:25.878507   15378 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-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
W0607 00:11:35.925553   15378 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-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
W0607 00:11:45.961656   15378 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-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
W0607 00:11:55.993580   15378 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-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
W0607 00:12:06.026987   15378 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-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
W0607 00:12:16.073453   15378 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-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
W0607 00:12:26.103777   15378 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-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
W0607 00:12:36.152933   15378 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-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
W0607 00:12:46.207659   15378 validate_cluster.go:221] (will retry): cluster not yet healthy
W0607 00:12:56.227854   15378 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-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-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
W0607 00:13:06.256836   15378 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-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
W0607 00:13:16.298227   15378 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-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
W0607 00:13:26.330497   15378 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-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
W0607 00:13:36.363743   15378 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-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
W0607 00:13:46.407233   15378 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-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
W0607 00:13:56.439472   15378 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-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
W0607 00:14:06.501252   15378 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-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
W0607 00:14:16.534912   15378 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-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
W0607 00:14:26.569070   15378 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 7 lines ...
Machine	i-09e0e7c964e660c26					machine "i-09e0e7c964e660c26" has not yet joined cluster
Machine	i-0b83558ad417b9266					machine "i-0b83558ad417b9266" has not yet joined cluster
Machine	i-0ec9cfc7096a1018a					machine "i-0ec9cfc7096a1018a" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-h9vhh	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-h9vhh" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-67297	system-cluster-critical pod "cert-manager-webhook-7bbf67968-67297" is pending

Validation Failed
W0607 00:14:38.663239   15378 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 18 lines ...
Pod	kube-system/ebs-csi-node-fzcjg						system-node-critical pod "ebs-csi-node-fzcjg" is pending
Pod	kube-system/ebs-csi-node-tmjs5						system-node-critical pod "ebs-csi-node-tmjs5" is pending
Pod	kube-system/ebs-csi-node-xcjnj						system-node-critical pod "ebs-csi-node-xcjnj" is pending
Pod	kube-system/kube-proxy-ip-172-20-38-247.us-west-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-38-247.us-west-2.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-63-204.us-west-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-63-204.us-west-2.compute.internal" is pending

Validation Failed
W0607 00:14:50.243302   15378 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 17 lines ...
Pod	kube-system/cert-manager-webhook-7bbf67968-67297			system-cluster-critical pod "cert-manager-webhook-7bbf67968-67297" is pending
Pod	kube-system/ebs-csi-node-jlztt						system-node-critical pod "ebs-csi-node-jlztt" is pending
Pod	kube-system/ebs-csi-node-tmjs5						system-node-critical pod "ebs-csi-node-tmjs5" is pending
Pod	kube-system/ebs-csi-node-xcjnj						system-node-critical pod "ebs-csi-node-xcjnj" is pending
Pod	kube-system/kube-proxy-ip-172-20-63-224.us-west-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-63-224.us-west-2.compute.internal" is pending

Validation Failed
W0607 00:15:01.801085   15378 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 12 lines ...
Pod	kube-system/calico-node-h7wn8				system-node-critical pod "calico-node-h7wn8" is not ready (calico-node)
Pod	kube-system/calico-node-l9xqf				system-node-critical pod "calico-node-l9xqf" is pending
Pod	kube-system/cert-manager-cainjector-74d69756d5-h9vhh	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-h9vhh" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-67297	system-cluster-critical pod "cert-manager-webhook-7bbf67968-67297" is pending
Pod	kube-system/ebs-csi-node-jlztt				system-node-critical pod "ebs-csi-node-jlztt" is pending

Validation Failed
W0607 00:15:13.154483   15378 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 11 lines ...
Pod	kube-system/calico-node-h7wn8				system-node-critical pod "calico-node-h7wn8" is not ready (calico-node)
Pod	kube-system/calico-node-l9xqf				system-node-critical pod "calico-node-l9xqf" is not ready (calico-node)
Pod	kube-system/cert-manager-cainjector-74d69756d5-h9vhh	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-h9vhh" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-67297	system-cluster-critical pod "cert-manager-webhook-7bbf67968-67297" is not ready (cert-manager)
Pod	kube-system/coredns-f45c4bf76-gm7qz			system-cluster-critical pod "coredns-f45c4bf76-gm7qz" is pending

Validation Failed
W0607 00:15:24.465464   15378 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 309 lines ...

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

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

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

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

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

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

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

      Distro debian doesn't support ntfs -- skipping

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

      Not enough topologies in cluster -- skipping

      /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 227 lines ...
Jun  7 00:18:41.096: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-3438sg8ms
STEP: creating a claim
Jun  7 00:18:41.158: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Jun  7 00:18:41.286: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun  7 00:18:41.418: INFO: Error updating pvc awsmcz4b: PersistentVolumeClaim "awsmcz4b" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3438sg8ms",
  	... // 2 identical fields
  }

Jun  7 00:18:43.547: INFO: Error updating pvc awsmcz4b: PersistentVolumeClaim "awsmcz4b" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3438sg8ms",
  	... // 2 identical fields
  }

Jun  7 00:18:45.543: INFO: Error updating pvc awsmcz4b: PersistentVolumeClaim "awsmcz4b" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3438sg8ms",
  	... // 2 identical fields
  }

Jun  7 00:18:47.543: INFO: Error updating pvc awsmcz4b: PersistentVolumeClaim "awsmcz4b" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3438sg8ms",
  	... // 2 identical fields
  }

Jun  7 00:18:49.544: INFO: Error updating pvc awsmcz4b: PersistentVolumeClaim "awsmcz4b" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3438sg8ms",
  	... // 2 identical fields
  }

Jun  7 00:18:51.548: INFO: Error updating pvc awsmcz4b: PersistentVolumeClaim "awsmcz4b" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3438sg8ms",
  	... // 2 identical fields
  }

Jun  7 00:18:53.543: INFO: Error updating pvc awsmcz4b: PersistentVolumeClaim "awsmcz4b" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3438sg8ms",
  	... // 2 identical fields
  }

Jun  7 00:18:55.543: INFO: Error updating pvc awsmcz4b: PersistentVolumeClaim "awsmcz4b" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3438sg8ms",
  	... // 2 identical fields
  }

Jun  7 00:18:57.543: INFO: Error updating pvc awsmcz4b: PersistentVolumeClaim "awsmcz4b" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3438sg8ms",
  	... // 2 identical fields
  }

Jun  7 00:18:59.545: INFO: Error updating pvc awsmcz4b: PersistentVolumeClaim "awsmcz4b" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3438sg8ms",
  	... // 2 identical fields
  }

Jun  7 00:19:01.548: INFO: Error updating pvc awsmcz4b: PersistentVolumeClaim "awsmcz4b" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3438sg8ms",
  	... // 2 identical fields
  }

Jun  7 00:19:03.543: INFO: Error updating pvc awsmcz4b: PersistentVolumeClaim "awsmcz4b" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3438sg8ms",
  	... // 2 identical fields
  }

Jun  7 00:19:05.544: INFO: Error updating pvc awsmcz4b: PersistentVolumeClaim "awsmcz4b" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3438sg8ms",
  	... // 2 identical fields
  }

Jun  7 00:19:07.545: INFO: Error updating pvc awsmcz4b: PersistentVolumeClaim "awsmcz4b" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3438sg8ms",
  	... // 2 identical fields
  }

Jun  7 00:19:09.545: INFO: Error updating pvc awsmcz4b: PersistentVolumeClaim "awsmcz4b" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3438sg8ms",
  	... // 2 identical fields
  }

Jun  7 00:19:11.547: INFO: Error updating pvc awsmcz4b: PersistentVolumeClaim "awsmcz4b" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3438sg8ms",
  	... // 2 identical fields
  }

Jun  7 00:19:11.673: INFO: Error updating pvc awsmcz4b: PersistentVolumeClaim "awsmcz4b" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 68 lines ...
Jun  7 00:18:41.822: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-8119-e2e-scbkxwn
STEP: creating a claim
Jun  7 00:18:41.895: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Jun  7 00:18:42.028: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun  7 00:18:42.156: INFO: Error updating pvc ebs.csi.aws.com9mpqd: PersistentVolumeClaim "ebs.csi.aws.com9mpqd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8119-e2e-scbkxwn",
  	... // 2 identical fields
  }

Jun  7 00:18:44.287: INFO: Error updating pvc ebs.csi.aws.com9mpqd: PersistentVolumeClaim "ebs.csi.aws.com9mpqd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8119-e2e-scbkxwn",
  	... // 2 identical fields
  }

Jun  7 00:18:46.303: INFO: Error updating pvc ebs.csi.aws.com9mpqd: PersistentVolumeClaim "ebs.csi.aws.com9mpqd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8119-e2e-scbkxwn",
  	... // 2 identical fields
  }

Jun  7 00:18:48.288: INFO: Error updating pvc ebs.csi.aws.com9mpqd: PersistentVolumeClaim "ebs.csi.aws.com9mpqd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8119-e2e-scbkxwn",
  	... // 2 identical fields
  }

Jun  7 00:18:50.287: INFO: Error updating pvc ebs.csi.aws.com9mpqd: PersistentVolumeClaim "ebs.csi.aws.com9mpqd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8119-e2e-scbkxwn",
  	... // 2 identical fields
  }

Jun  7 00:18:52.286: INFO: Error updating pvc ebs.csi.aws.com9mpqd: PersistentVolumeClaim "ebs.csi.aws.com9mpqd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8119-e2e-scbkxwn",
  	... // 2 identical fields
  }

Jun  7 00:18:54.286: INFO: Error updating pvc ebs.csi.aws.com9mpqd: PersistentVolumeClaim "ebs.csi.aws.com9mpqd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8119-e2e-scbkxwn",
  	... // 2 identical fields
  }

Jun  7 00:18:56.285: INFO: Error updating pvc ebs.csi.aws.com9mpqd: PersistentVolumeClaim "ebs.csi.aws.com9mpqd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8119-e2e-scbkxwn",
  	... // 2 identical fields
  }

Jun  7 00:18:58.291: INFO: Error updating pvc ebs.csi.aws.com9mpqd: PersistentVolumeClaim "ebs.csi.aws.com9mpqd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8119-e2e-scbkxwn",
  	... // 2 identical fields
  }

Jun  7 00:19:00.285: INFO: Error updating pvc ebs.csi.aws.com9mpqd: PersistentVolumeClaim "ebs.csi.aws.com9mpqd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8119-e2e-scbkxwn",
  	... // 2 identical fields
  }

Jun  7 00:19:02.286: INFO: Error updating pvc ebs.csi.aws.com9mpqd: PersistentVolumeClaim "ebs.csi.aws.com9mpqd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8119-e2e-scbkxwn",
  	... // 2 identical fields
  }

Jun  7 00:19:04.285: INFO: Error updating pvc ebs.csi.aws.com9mpqd: PersistentVolumeClaim "ebs.csi.aws.com9mpqd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8119-e2e-scbkxwn",
  	... // 2 identical fields
  }

Jun  7 00:19:06.285: INFO: Error updating pvc ebs.csi.aws.com9mpqd: PersistentVolumeClaim "ebs.csi.aws.com9mpqd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8119-e2e-scbkxwn",
  	... // 2 identical fields
  }

Jun  7 00:19:08.286: INFO: Error updating pvc ebs.csi.aws.com9mpqd: PersistentVolumeClaim "ebs.csi.aws.com9mpqd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8119-e2e-scbkxwn",
  	... // 2 identical fields
  }

Jun  7 00:19:10.286: INFO: Error updating pvc ebs.csi.aws.com9mpqd: PersistentVolumeClaim "ebs.csi.aws.com9mpqd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8119-e2e-scbkxwn",
  	... // 2 identical fields
  }

Jun  7 00:19:12.287: INFO: Error updating pvc ebs.csi.aws.com9mpqd: PersistentVolumeClaim "ebs.csi.aws.com9mpqd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8119-e2e-scbkxwn",
  	... // 2 identical fields
  }

Jun  7 00:19:12.418: INFO: Error updating pvc ebs.csi.aws.com9mpqd: PersistentVolumeClaim "ebs.csi.aws.com9mpqd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 65 lines ...
STEP: Creating a kubernetes client
Jun  7 00:18:40.420: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename provisioning
W0607 00:18:40.883423   29256 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Jun  7 00:18:40.883: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail if subpath directory is outside the volume [Slow][LinuxOnly]
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun  7 00:18:41.008: INFO: Creating resource for dynamic PV
Jun  7 00:18:41.008: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4870-e2e-scr588n
STEP: creating a claim
Jun  7 00:18:41.073: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-m477
STEP: Checking for subpath error in container status
Jun  7 00:19:01.391: INFO: Deleting pod "pod-subpath-test-dynamicpv-m477" in namespace "provisioning-4870"
Jun  7 00:19:01.455: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-m477" to be fully deleted
STEP: Deleting pod
Jun  7 00:19:11.581: INFO: Deleting pod "pod-subpath-test-dynamicpv-m477" in namespace "provisioning-4870"
STEP: Deleting pvc
Jun  7 00:19:11.769: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comnt6lp"
... skipping 9 lines ...

• [SLOW TEST:36.824 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath directory is outside the volume [Slow][LinuxOnly]
    /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  7 00:19:17.246: INFO: Driver ebs.csi.aws.com doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
... skipping 2 lines ...

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

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

    /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 4 lines ...
STEP: Creating a kubernetes client
Jun  7 00:18:40.496: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename provisioning
W0607 00:18:40.956298   29337 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Jun  7 00:18:40.956: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly]
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun  7 00:18:41.081: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  7 00:18:41.081: INFO: Creating resource for dynamic PV
Jun  7 00:18:41.081: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1682jfngh
STEP: creating a claim
Jun  7 00:18:41.144: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-r54t
STEP: Checking for subpath error in container status
Jun  7 00:18:59.470: INFO: Deleting pod "pod-subpath-test-dynamicpv-r54t" in namespace "provisioning-1682"
Jun  7 00:18:59.534: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-r54t" to be fully deleted
STEP: Deleting pod
Jun  7 00:19:11.662: INFO: Deleting pod "pod-subpath-test-dynamicpv-r54t" in namespace "provisioning-1682"
STEP: Deleting pvc
Jun  7 00:19:11.850: INFO: Deleting PersistentVolumeClaim "awsv9rnd"
... skipping 12 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.r42VbgPIn/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.r42VbgPIn/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.r42VbgPIn/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.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [sig-storage] Storage Policy Based Volume Provisioning [Feature:vsphere]
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  7 00:19:22.393: INFO: >>> kubeConfig: /root/.kube/config
... skipping 52 lines ...
Jun  7 00:18:43.250: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1576bzr5s
STEP: creating a claim
Jun  7 00:18:43.311: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-jzrl
STEP: Creating a pod to test subpath
Jun  7 00:18:43.495: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-jzrl" in namespace "provisioning-1576" to be "Succeeded or Failed"
Jun  7 00:18:43.556: INFO: Pod "pod-subpath-test-dynamicpv-jzrl": Phase="Pending", Reason="", readiness=false. Elapsed: 60.476224ms
Jun  7 00:18:45.617: INFO: Pod "pod-subpath-test-dynamicpv-jzrl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.121394651s
Jun  7 00:18:47.683: INFO: Pod "pod-subpath-test-dynamicpv-jzrl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.187499159s
Jun  7 00:18:49.750: INFO: Pod "pod-subpath-test-dynamicpv-jzrl": Phase="Pending", Reason="", readiness=false. Elapsed: 6.254235406s
Jun  7 00:18:51.811: INFO: Pod "pod-subpath-test-dynamicpv-jzrl": Phase="Pending", Reason="", readiness=false. Elapsed: 8.315224065s
Jun  7 00:18:53.873: INFO: Pod "pod-subpath-test-dynamicpv-jzrl": Phase="Pending", Reason="", readiness=false. Elapsed: 10.377361333s
Jun  7 00:18:55.935: INFO: Pod "pod-subpath-test-dynamicpv-jzrl": Phase="Pending", Reason="", readiness=false. Elapsed: 12.439223313s
Jun  7 00:18:57.997: INFO: Pod "pod-subpath-test-dynamicpv-jzrl": Phase="Pending", Reason="", readiness=false. Elapsed: 14.501737334s
Jun  7 00:19:00.058: INFO: Pod "pod-subpath-test-dynamicpv-jzrl": Phase="Pending", Reason="", readiness=false. Elapsed: 16.562733716s
Jun  7 00:19:02.120: INFO: Pod "pod-subpath-test-dynamicpv-jzrl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.624883576s
STEP: Saw pod success
Jun  7 00:19:02.120: INFO: Pod "pod-subpath-test-dynamicpv-jzrl" satisfied condition "Succeeded or Failed"
Jun  7 00:19:02.181: INFO: Trying to get logs from node ip-172-20-38-247.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-jzrl container test-container-subpath-dynamicpv-jzrl: <nil>
STEP: delete the pod
Jun  7 00:19:03.233: INFO: Waiting for pod pod-subpath-test-dynamicpv-jzrl to disappear
Jun  7 00:19:03.293: INFO: Pod pod-subpath-test-dynamicpv-jzrl no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-jzrl
Jun  7 00:19:03.293: INFO: Deleting pod "pod-subpath-test-dynamicpv-jzrl" in namespace "provisioning-1576"
... skipping 234 lines ...
Jun  7 00:18:43.160: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7389wcpn6
STEP: creating a claim
Jun  7 00:18:43.221: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-pdgk
STEP: Creating a pod to test multi_subpath
Jun  7 00:18:43.410: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-pdgk" in namespace "provisioning-7389" to be "Succeeded or Failed"
Jun  7 00:18:43.472: INFO: Pod "pod-subpath-test-dynamicpv-pdgk": Phase="Pending", Reason="", readiness=false. Elapsed: 62.160271ms
Jun  7 00:18:45.533: INFO: Pod "pod-subpath-test-dynamicpv-pdgk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.122719122s
Jun  7 00:18:47.595: INFO: Pod "pod-subpath-test-dynamicpv-pdgk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.185013534s
Jun  7 00:18:49.658: INFO: Pod "pod-subpath-test-dynamicpv-pdgk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.247792169s
Jun  7 00:18:51.723: INFO: Pod "pod-subpath-test-dynamicpv-pdgk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.312930176s
Jun  7 00:18:53.785: INFO: Pod "pod-subpath-test-dynamicpv-pdgk": Phase="Pending", Reason="", readiness=false. Elapsed: 10.374611518s
... skipping 4 lines ...
Jun  7 00:19:04.091: INFO: Pod "pod-subpath-test-dynamicpv-pdgk": Phase="Pending", Reason="", readiness=false. Elapsed: 20.680763765s
Jun  7 00:19:06.152: INFO: Pod "pod-subpath-test-dynamicpv-pdgk": Phase="Pending", Reason="", readiness=false. Elapsed: 22.74156868s
Jun  7 00:19:08.213: INFO: Pod "pod-subpath-test-dynamicpv-pdgk": Phase="Pending", Reason="", readiness=false. Elapsed: 24.802559657s
Jun  7 00:19:10.274: INFO: Pod "pod-subpath-test-dynamicpv-pdgk": Phase="Pending", Reason="", readiness=false. Elapsed: 26.864167434s
Jun  7 00:19:12.336: INFO: Pod "pod-subpath-test-dynamicpv-pdgk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 28.925663839s
STEP: Saw pod success
Jun  7 00:19:12.336: INFO: Pod "pod-subpath-test-dynamicpv-pdgk" satisfied condition "Succeeded or Failed"
Jun  7 00:19:12.396: INFO: Trying to get logs from node ip-172-20-63-204.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-pdgk container test-container-subpath-dynamicpv-pdgk: <nil>
STEP: delete the pod
Jun  7 00:19:12.777: INFO: Waiting for pod pod-subpath-test-dynamicpv-pdgk to disappear
Jun  7 00:19:12.838: INFO: Pod pod-subpath-test-dynamicpv-pdgk no longer exists
STEP: Deleting pod
Jun  7 00:19:12.838: INFO: Deleting pod "pod-subpath-test-dynamicpv-pdgk" in namespace "provisioning-7389"
... skipping 71 lines ...
Jun  7 00:18:51.800: INFO: PersistentVolumeClaim pvc-4dw89 found but phase is Pending instead of Bound.
Jun  7 00:18:53.860: INFO: PersistentVolumeClaim pvc-4dw89 found and phase=Bound (6.2532496s)
Jun  7 00:18:53.860: INFO: Waiting up to 3m0s for PersistentVolume aws-qklsw to have phase Bound
Jun  7 00:18:53.919: INFO: PersistentVolume aws-qklsw found and phase=Bound (58.824671ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-df4v
STEP: Creating a pod to test exec-volume-test
Jun  7 00:18:54.101: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-df4v" in namespace "volume-7411" to be "Succeeded or Failed"
Jun  7 00:18:54.159: INFO: Pod "exec-volume-test-preprovisionedpv-df4v": Phase="Pending", Reason="", readiness=false. Elapsed: 58.705097ms
Jun  7 00:18:56.219: INFO: Pod "exec-volume-test-preprovisionedpv-df4v": Phase="Pending", Reason="", readiness=false. Elapsed: 2.118132793s
Jun  7 00:18:58.278: INFO: Pod "exec-volume-test-preprovisionedpv-df4v": Phase="Pending", Reason="", readiness=false. Elapsed: 4.17774599s
Jun  7 00:19:00.339: INFO: Pod "exec-volume-test-preprovisionedpv-df4v": Phase="Pending", Reason="", readiness=false. Elapsed: 6.237945435s
Jun  7 00:19:02.398: INFO: Pod "exec-volume-test-preprovisionedpv-df4v": Phase="Pending", Reason="", readiness=false. Elapsed: 8.297100789s
Jun  7 00:19:04.457: INFO: Pod "exec-volume-test-preprovisionedpv-df4v": Phase="Pending", Reason="", readiness=false. Elapsed: 10.356246483s
Jun  7 00:19:06.516: INFO: Pod "exec-volume-test-preprovisionedpv-df4v": Phase="Pending", Reason="", readiness=false. Elapsed: 12.415411844s
Jun  7 00:19:08.582: INFO: Pod "exec-volume-test-preprovisionedpv-df4v": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.481060478s
STEP: Saw pod success
Jun  7 00:19:08.582: INFO: Pod "exec-volume-test-preprovisionedpv-df4v" satisfied condition "Succeeded or Failed"
Jun  7 00:19:08.642: INFO: Trying to get logs from node ip-172-20-38-247.us-west-2.compute.internal pod exec-volume-test-preprovisionedpv-df4v container exec-container-preprovisionedpv-df4v: <nil>
STEP: delete the pod
Jun  7 00:19:08.770: INFO: Waiting for pod exec-volume-test-preprovisionedpv-df4v to disappear
Jun  7 00:19:08.829: INFO: Pod exec-volume-test-preprovisionedpv-df4v no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-df4v
Jun  7 00:19:08.829: INFO: Deleting pod "exec-volume-test-preprovisionedpv-df4v" in namespace "volume-7411"
STEP: Deleting pv and pvc
Jun  7 00:19:08.889: INFO: Deleting PersistentVolumeClaim "pvc-4dw89"
Jun  7 00:19:08.950: INFO: Deleting PersistentVolume "aws-qklsw"
Jun  7 00:19:09.219: INFO: Couldn't delete PD "aws://us-west-2a/vol-00cad6bc8572f2f3f", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00cad6bc8572f2f3f is currently attached to i-0b83558ad417b9266
	status code: 400, request id: 9f7dcc45-1567-4352-aff7-0e4d96bfa3ad
Jun  7 00:19:14.662: INFO: Couldn't delete PD "aws://us-west-2a/vol-00cad6bc8572f2f3f", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00cad6bc8572f2f3f is currently attached to i-0b83558ad417b9266
	status code: 400, request id: fe2c5a26-a453-499f-aba1-a3eb13c0f598
Jun  7 00:19:20.120: INFO: Couldn't delete PD "aws://us-west-2a/vol-00cad6bc8572f2f3f", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00cad6bc8572f2f3f is currently attached to i-0b83558ad417b9266
	status code: 400, request id: fbf0d0b5-df8f-4c22-863e-169c8ab54bfd
Jun  7 00:19:25.526: INFO: Couldn't delete PD "aws://us-west-2a/vol-00cad6bc8572f2f3f", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00cad6bc8572f2f3f is currently attached to i-0b83558ad417b9266
	status code: 400, request id: a0da26e7-d71f-4985-a59e-22b35393b7dd
Jun  7 00:19:30.950: INFO: Successfully deleted PD "aws://us-west-2a/vol-00cad6bc8572f2f3f".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  7 00:19:30.950: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-7411" for this suite.
... skipping 24 lines ...
Jun  7 00:18:43.552: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-7470r587n
STEP: creating a claim
Jun  7 00:18:43.614: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-jljt
STEP: Creating a pod to test exec-volume-test
Jun  7 00:18:43.809: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-jljt" in namespace "volume-7470" to be "Succeeded or Failed"
Jun  7 00:18:43.870: INFO: Pod "exec-volume-test-dynamicpv-jljt": Phase="Pending", Reason="", readiness=false. Elapsed: 61.842192ms
Jun  7 00:18:45.934: INFO: Pod "exec-volume-test-dynamicpv-jljt": Phase="Pending", Reason="", readiness=false. Elapsed: 2.125207988s
Jun  7 00:18:47.997: INFO: Pod "exec-volume-test-dynamicpv-jljt": Phase="Pending", Reason="", readiness=false. Elapsed: 4.188557385s
Jun  7 00:18:50.060: INFO: Pod "exec-volume-test-dynamicpv-jljt": Phase="Pending", Reason="", readiness=false. Elapsed: 6.251527268s
Jun  7 00:18:52.123: INFO: Pod "exec-volume-test-dynamicpv-jljt": Phase="Pending", Reason="", readiness=false. Elapsed: 8.314409693s
Jun  7 00:18:54.185: INFO: Pod "exec-volume-test-dynamicpv-jljt": Phase="Pending", Reason="", readiness=false. Elapsed: 10.376588688s
... skipping 4 lines ...
Jun  7 00:19:04.501: INFO: Pod "exec-volume-test-dynamicpv-jljt": Phase="Pending", Reason="", readiness=false. Elapsed: 20.692495517s
Jun  7 00:19:06.564: INFO: Pod "exec-volume-test-dynamicpv-jljt": Phase="Pending", Reason="", readiness=false. Elapsed: 22.755843618s
Jun  7 00:19:08.638: INFO: Pod "exec-volume-test-dynamicpv-jljt": Phase="Pending", Reason="", readiness=false. Elapsed: 24.829108596s
Jun  7 00:19:10.702: INFO: Pod "exec-volume-test-dynamicpv-jljt": Phase="Pending", Reason="", readiness=false. Elapsed: 26.892907974s
Jun  7 00:19:12.765: INFO: Pod "exec-volume-test-dynamicpv-jljt": Phase="Succeeded", Reason="", readiness=false. Elapsed: 28.956222474s
STEP: Saw pod success
Jun  7 00:19:12.765: INFO: Pod "exec-volume-test-dynamicpv-jljt" satisfied condition "Succeeded or Failed"
Jun  7 00:19:12.827: INFO: Trying to get logs from node ip-172-20-63-204.us-west-2.compute.internal pod exec-volume-test-dynamicpv-jljt container exec-container-dynamicpv-jljt: <nil>
STEP: delete the pod
Jun  7 00:19:12.962: INFO: Waiting for pod exec-volume-test-dynamicpv-jljt to disappear
Jun  7 00:19:13.024: INFO: Pod exec-volume-test-dynamicpv-jljt no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-jljt
Jun  7 00:19:13.024: INFO: Deleting pod "exec-volume-test-dynamicpv-jljt" in namespace "volume-7470"
... skipping 200 lines ...

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

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

    /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 12 lines ...
Jun  7 00:18:44.893: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1712vhthb
STEP: creating a claim
Jun  7 00:18:44.952: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-5b4r
STEP: Creating a pod to test atomic-volume-subpath
Jun  7 00:18:45.135: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-5b4r" in namespace "provisioning-1712" to be "Succeeded or Failed"
Jun  7 00:18:45.194: INFO: Pod "pod-subpath-test-dynamicpv-5b4r": Phase="Pending", Reason="", readiness=false. Elapsed: 58.556155ms
Jun  7 00:18:47.252: INFO: Pod "pod-subpath-test-dynamicpv-5b4r": Phase="Pending", Reason="", readiness=false. Elapsed: 2.117447165s
Jun  7 00:18:49.315: INFO: Pod "pod-subpath-test-dynamicpv-5b4r": Phase="Pending", Reason="", readiness=false. Elapsed: 4.179995455s
Jun  7 00:18:51.376: INFO: Pod "pod-subpath-test-dynamicpv-5b4r": Phase="Pending", Reason="", readiness=false. Elapsed: 6.240526169s
Jun  7 00:18:53.436: INFO: Pod "pod-subpath-test-dynamicpv-5b4r": Phase="Pending", Reason="", readiness=false. Elapsed: 8.301000711s
Jun  7 00:18:55.495: INFO: Pod "pod-subpath-test-dynamicpv-5b4r": Phase="Pending", Reason="", readiness=false. Elapsed: 10.360464203s
... skipping 9 lines ...
Jun  7 00:19:16.097: INFO: Pod "pod-subpath-test-dynamicpv-5b4r": Phase="Running", Reason="", readiness=true. Elapsed: 30.961881493s
Jun  7 00:19:18.157: INFO: Pod "pod-subpath-test-dynamicpv-5b4r": Phase="Running", Reason="", readiness=true. Elapsed: 33.021815651s
Jun  7 00:19:20.218: INFO: Pod "pod-subpath-test-dynamicpv-5b4r": Phase="Running", Reason="", readiness=true. Elapsed: 35.082637321s
Jun  7 00:19:22.277: INFO: Pod "pod-subpath-test-dynamicpv-5b4r": Phase="Running", Reason="", readiness=true. Elapsed: 37.141679657s
Jun  7 00:19:24.336: INFO: Pod "pod-subpath-test-dynamicpv-5b4r": Phase="Succeeded", Reason="", readiness=false. Elapsed: 39.200875209s
STEP: Saw pod success
Jun  7 00:19:24.336: INFO: Pod "pod-subpath-test-dynamicpv-5b4r" satisfied condition "Succeeded or Failed"
Jun  7 00:19:24.394: INFO: Trying to get logs from node ip-172-20-63-204.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-5b4r container test-container-subpath-dynamicpv-5b4r: <nil>
STEP: delete the pod
Jun  7 00:19:24.522: INFO: Waiting for pod pod-subpath-test-dynamicpv-5b4r to disappear
Jun  7 00:19:24.581: INFO: Pod pod-subpath-test-dynamicpv-5b4r no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-5b4r
Jun  7 00:19:24.581: INFO: Deleting pod "pod-subpath-test-dynamicpv-5b4r" in namespace "provisioning-1712"
... skipping 209 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  7 00:19:12.058: 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.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun  7 00:19:12.368: INFO: Creating resource for dynamic PV
Jun  7 00:19:12.368: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4601-e2e-sc5gj9x
STEP: creating a claim
Jun  7 00:19:12.432: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-b7ht
STEP: Checking for subpath error in container status
Jun  7 00:19:24.746: INFO: Deleting pod "pod-subpath-test-dynamicpv-b7ht" in namespace "provisioning-4601"
Jun  7 00:19:24.810: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-b7ht" to be fully deleted
STEP: Deleting pod
Jun  7 00:19:38.936: INFO: Deleting pod "pod-subpath-test-dynamicpv-b7ht" in namespace "provisioning-4601"
STEP: Deleting pvc
Jun  7 00:19:39.121: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comgxh7v"
... skipping 11 lines ...

• [SLOW TEST:42.579 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.r42VbgPIn/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.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  7 00:19:54.639: INFO: Driver "ebs.csi.aws.com" does not support volume type "PreprovisionedPV" - skipping
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
... skipping 263 lines ...
Jun  7 00:19:23.163: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  7 00:19:23.767: INFO: Successfully created a new PD: "aws://us-west-2a/vol-019204ee34c5ad936".
Jun  7 00:19:23.767: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-rhrx
STEP: Creating a pod to test exec-volume-test
Jun  7 00:19:23.837: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-rhrx" in namespace "volume-4923" to be "Succeeded or Failed"
Jun  7 00:19:23.900: INFO: Pod "exec-volume-test-inlinevolume-rhrx": Phase="Pending", Reason="", readiness=false. Elapsed: 62.671402ms
Jun  7 00:19:25.963: INFO: Pod "exec-volume-test-inlinevolume-rhrx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.125872883s
Jun  7 00:19:28.026: INFO: Pod "exec-volume-test-inlinevolume-rhrx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.188942824s
Jun  7 00:19:30.090: INFO: Pod "exec-volume-test-inlinevolume-rhrx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.253035346s
Jun  7 00:19:32.153: INFO: Pod "exec-volume-test-inlinevolume-rhrx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.3164893s
Jun  7 00:19:34.218: INFO: Pod "exec-volume-test-inlinevolume-rhrx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.380593904s
Jun  7 00:19:36.281: INFO: Pod "exec-volume-test-inlinevolume-rhrx": Phase="Pending", Reason="", readiness=false. Elapsed: 12.444162814s
Jun  7 00:19:38.345: INFO: Pod "exec-volume-test-inlinevolume-rhrx": Phase="Pending", Reason="", readiness=false. Elapsed: 14.507972937s
Jun  7 00:19:40.419: INFO: Pod "exec-volume-test-inlinevolume-rhrx": Phase="Pending", Reason="", readiness=false. Elapsed: 16.582366621s
Jun  7 00:19:42.483: INFO: Pod "exec-volume-test-inlinevolume-rhrx": Phase="Pending", Reason="", readiness=false. Elapsed: 18.645757383s
Jun  7 00:19:44.548: INFO: Pod "exec-volume-test-inlinevolume-rhrx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.710628139s
STEP: Saw pod success
Jun  7 00:19:44.548: INFO: Pod "exec-volume-test-inlinevolume-rhrx" satisfied condition "Succeeded or Failed"
Jun  7 00:19:44.611: INFO: Trying to get logs from node ip-172-20-63-224.us-west-2.compute.internal pod exec-volume-test-inlinevolume-rhrx container exec-container-inlinevolume-rhrx: <nil>
STEP: delete the pod
Jun  7 00:19:44.747: INFO: Waiting for pod exec-volume-test-inlinevolume-rhrx to disappear
Jun  7 00:19:44.810: INFO: Pod exec-volume-test-inlinevolume-rhrx no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-rhrx
Jun  7 00:19:44.810: INFO: Deleting pod "exec-volume-test-inlinevolume-rhrx" in namespace "volume-4923"
Jun  7 00:19:45.084: INFO: Couldn't delete PD "aws://us-west-2a/vol-019204ee34c5ad936", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-019204ee34c5ad936 is currently attached to i-0ec9cfc7096a1018a
	status code: 400, request id: ab3d9a24-ea83-4bb7-807b-f3545ecf1e42
Jun  7 00:19:50.540: INFO: Couldn't delete PD "aws://us-west-2a/vol-019204ee34c5ad936", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-019204ee34c5ad936 is currently attached to i-0ec9cfc7096a1018a
	status code: 400, request id: 8b9bb060-8b3e-4eec-b7ca-1be7ea528993
Jun  7 00:19:55.979: INFO: Couldn't delete PD "aws://us-west-2a/vol-019204ee34c5ad936", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-019204ee34c5ad936 is currently attached to i-0ec9cfc7096a1018a
	status code: 400, request id: b7df6010-b73c-4119-9ec0-9379f2666443
Jun  7 00:20:01.421: INFO: Couldn't delete PD "aws://us-west-2a/vol-019204ee34c5ad936", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-019204ee34c5ad936 is currently attached to i-0ec9cfc7096a1018a
	status code: 400, request id: 5ffc33b0-67dc-40b2-b4cc-7ce9a96fdad4
Jun  7 00:20:06.815: INFO: Successfully deleted PD "aws://us-west-2a/vol-019204ee34c5ad936".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  7 00:20:06.815: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-4923" for this suite.
... skipping 95 lines ...
Jun  7 00:20:02.636: INFO: Waiting for pod aws-client to disappear
Jun  7 00:20:02.697: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun  7 00:20:02.697: INFO: Deleting PersistentVolumeClaim "pvc-fqdkh"
Jun  7 00:20:02.759: INFO: Deleting PersistentVolume "aws-w7gfw"
Jun  7 00:20:03.228: INFO: Couldn't delete PD "aws://us-west-2a/vol-0de20f999ee362121", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0de20f999ee362121 is currently attached to i-0b83558ad417b9266
	status code: 400, request id: 4e9485c5-1d33-4ef3-aa12-0e204ef772c7
Jun  7 00:20:08.657: INFO: Successfully deleted PD "aws://us-west-2a/vol-0de20f999ee362121".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  7 00:20:08.657: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-5161" for this suite.
... skipping 22 lines ...
Jun  7 00:19:17.563: INFO: Creating resource for dynamic PV
Jun  7 00:19:17.563: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5037-e2e-sckx4lf
STEP: creating a claim
Jun  7 00:19:17.627: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-5037
Jun  7 00:19:17.824: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-5037" in namespace "provisioning-5037" to be "Succeeded or Failed"
Jun  7 00:19:17.890: INFO: Pod "volume-prep-provisioning-5037": Phase="Pending", Reason="", readiness=false. Elapsed: 65.921193ms
Jun  7 00:19:19.953: INFO: Pod "volume-prep-provisioning-5037": Phase="Pending", Reason="", readiness=false. Elapsed: 2.128937742s
Jun  7 00:19:22.017: INFO: Pod "volume-prep-provisioning-5037": Phase="Pending", Reason="", readiness=false. Elapsed: 4.192605027s
Jun  7 00:19:24.081: INFO: Pod "volume-prep-provisioning-5037": Phase="Pending", Reason="", readiness=false. Elapsed: 6.256020769s
Jun  7 00:19:26.143: INFO: Pod "volume-prep-provisioning-5037": Phase="Pending", Reason="", readiness=false. Elapsed: 8.318878703s
Jun  7 00:19:28.206: INFO: Pod "volume-prep-provisioning-5037": Phase="Pending", Reason="", readiness=false. Elapsed: 10.381908997s
Jun  7 00:19:30.270: INFO: Pod "volume-prep-provisioning-5037": Phase="Pending", Reason="", readiness=false. Elapsed: 12.445744126s
Jun  7 00:19:32.335: INFO: Pod "volume-prep-provisioning-5037": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.510117312s
STEP: Saw pod success
Jun  7 00:19:32.335: INFO: Pod "volume-prep-provisioning-5037" satisfied condition "Succeeded or Failed"
Jun  7 00:19:32.335: INFO: Deleting pod "volume-prep-provisioning-5037" in namespace "provisioning-5037"
Jun  7 00:19:32.404: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-5037" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-jxdl
STEP: Checking for subpath error in container status
Jun  7 00:19:38.658: INFO: Deleting pod "pod-subpath-test-dynamicpv-jxdl" in namespace "provisioning-5037"
Jun  7 00:19:38.727: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-jxdl" to be fully deleted
STEP: Deleting pod
Jun  7 00:19:38.789: INFO: Deleting pod "pod-subpath-test-dynamicpv-jxdl" in namespace "provisioning-5037"
STEP: Deleting pvc
Jun  7 00:19:38.977: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comjm62g"
... skipping 192 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.r42VbgPIn/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.r42VbgPIn/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.r42VbgPIn/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.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 100 lines ...
Jun  7 00:19:42.578: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-928-e2e-sc6qdjp
STEP: creating a claim
Jun  7 00:19:42.643: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-ccwj
STEP: Creating a pod to test subpath
Jun  7 00:19:42.836: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-ccwj" in namespace "provisioning-928" to be "Succeeded or Failed"
Jun  7 00:19:42.898: INFO: Pod "pod-subpath-test-dynamicpv-ccwj": Phase="Pending", Reason="", readiness=false. Elapsed: 61.942442ms
Jun  7 00:19:44.960: INFO: Pod "pod-subpath-test-dynamicpv-ccwj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.124467625s
Jun  7 00:19:47.022: INFO: Pod "pod-subpath-test-dynamicpv-ccwj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.186750774s
Jun  7 00:19:49.085: INFO: Pod "pod-subpath-test-dynamicpv-ccwj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.249298178s
Jun  7 00:19:51.150: INFO: Pod "pod-subpath-test-dynamicpv-ccwj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.313880905s
Jun  7 00:19:53.213: INFO: Pod "pod-subpath-test-dynamicpv-ccwj": Phase="Pending", Reason="", readiness=false. Elapsed: 10.377764092s
Jun  7 00:19:55.276: INFO: Pod "pod-subpath-test-dynamicpv-ccwj": Phase="Pending", Reason="", readiness=false. Elapsed: 12.439885565s
Jun  7 00:19:57.338: INFO: Pod "pod-subpath-test-dynamicpv-ccwj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.50261054s
STEP: Saw pod success
Jun  7 00:19:57.338: INFO: Pod "pod-subpath-test-dynamicpv-ccwj" satisfied condition "Succeeded or Failed"
Jun  7 00:19:57.400: INFO: Trying to get logs from node ip-172-20-40-22.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-ccwj container test-container-subpath-dynamicpv-ccwj: <nil>
STEP: delete the pod
Jun  7 00:19:57.542: INFO: Waiting for pod pod-subpath-test-dynamicpv-ccwj to disappear
Jun  7 00:19:57.610: INFO: Pod pod-subpath-test-dynamicpv-ccwj no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-ccwj
Jun  7 00:19:57.610: INFO: Deleting pod "pod-subpath-test-dynamicpv-ccwj" in namespace "provisioning-928"
STEP: Creating pod pod-subpath-test-dynamicpv-ccwj
STEP: Creating a pod to test subpath
Jun  7 00:19:57.740: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-ccwj" in namespace "provisioning-928" to be "Succeeded or Failed"
Jun  7 00:19:57.808: INFO: Pod "pod-subpath-test-dynamicpv-ccwj": Phase="Pending", Reason="", readiness=false. Elapsed: 67.980391ms
Jun  7 00:19:59.871: INFO: Pod "pod-subpath-test-dynamicpv-ccwj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.13083517s
Jun  7 00:20:01.933: INFO: Pod "pod-subpath-test-dynamicpv-ccwj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.193364604s
Jun  7 00:20:03.997: INFO: Pod "pod-subpath-test-dynamicpv-ccwj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.256651504s
STEP: Saw pod success
Jun  7 00:20:03.997: INFO: Pod "pod-subpath-test-dynamicpv-ccwj" satisfied condition "Succeeded or Failed"
Jun  7 00:20:04.059: INFO: Trying to get logs from node ip-172-20-40-22.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-ccwj container test-container-subpath-dynamicpv-ccwj: <nil>
STEP: delete the pod
Jun  7 00:20:04.196: INFO: Waiting for pod pod-subpath-test-dynamicpv-ccwj to disappear
Jun  7 00:20:04.260: INFO: Pod pod-subpath-test-dynamicpv-ccwj no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-ccwj
Jun  7 00:20:04.260: INFO: Deleting pod "pod-subpath-test-dynamicpv-ccwj" in namespace "provisioning-928"
... skipping 186 lines ...
Jun  7 00:19:38.354: INFO: PersistentVolumeClaim pvc-fnz2g found but phase is Pending instead of Bound.
Jun  7 00:19:40.425: INFO: PersistentVolumeClaim pvc-fnz2g found and phase=Bound (14.532579557s)
Jun  7 00:19:40.425: INFO: Waiting up to 3m0s for PersistentVolume aws-xgcbp to have phase Bound
Jun  7 00:19:40.490: INFO: PersistentVolume aws-xgcbp found and phase=Bound (65.584005ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-p6nv
STEP: Creating a pod to test exec-volume-test
Jun  7 00:19:40.691: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-p6nv" in namespace "volume-8156" to be "Succeeded or Failed"
Jun  7 00:19:40.762: INFO: Pod "exec-volume-test-preprovisionedpv-p6nv": Phase="Pending", Reason="", readiness=false. Elapsed: 70.811765ms
Jun  7 00:19:42.828: INFO: Pod "exec-volume-test-preprovisionedpv-p6nv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.136696121s
Jun  7 00:19:44.894: INFO: Pod "exec-volume-test-preprovisionedpv-p6nv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.203358768s
Jun  7 00:19:46.961: INFO: Pod "exec-volume-test-preprovisionedpv-p6nv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.2697817s
Jun  7 00:19:49.029: INFO: Pod "exec-volume-test-preprovisionedpv-p6nv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.338590579s
Jun  7 00:19:51.098: INFO: Pod "exec-volume-test-preprovisionedpv-p6nv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.407553586s
Jun  7 00:19:53.166: INFO: Pod "exec-volume-test-preprovisionedpv-p6nv": Phase="Pending", Reason="", readiness=false. Elapsed: 12.475029573s
Jun  7 00:19:55.231: INFO: Pod "exec-volume-test-preprovisionedpv-p6nv": Phase="Pending", Reason="", readiness=false. Elapsed: 14.540551125s
Jun  7 00:19:57.298: INFO: Pod "exec-volume-test-preprovisionedpv-p6nv": Phase="Pending", Reason="", readiness=false. Elapsed: 16.606686635s
Jun  7 00:19:59.363: INFO: Pod "exec-volume-test-preprovisionedpv-p6nv": Phase="Pending", Reason="", readiness=false. Elapsed: 18.672152681s
Jun  7 00:20:01.430: INFO: Pod "exec-volume-test-preprovisionedpv-p6nv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.738835048s
STEP: Saw pod success
Jun  7 00:20:01.430: INFO: Pod "exec-volume-test-preprovisionedpv-p6nv" satisfied condition "Succeeded or Failed"
Jun  7 00:20:01.495: INFO: Trying to get logs from node ip-172-20-40-22.us-west-2.compute.internal pod exec-volume-test-preprovisionedpv-p6nv container exec-container-preprovisionedpv-p6nv: <nil>
STEP: delete the pod
Jun  7 00:20:01.650: INFO: Waiting for pod exec-volume-test-preprovisionedpv-p6nv to disappear
Jun  7 00:20:01.716: INFO: Pod exec-volume-test-preprovisionedpv-p6nv no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-p6nv
Jun  7 00:20:01.716: INFO: Deleting pod "exec-volume-test-preprovisionedpv-p6nv" in namespace "volume-8156"
STEP: Deleting pv and pvc
Jun  7 00:20:01.782: INFO: Deleting PersistentVolumeClaim "pvc-fnz2g"
Jun  7 00:20:01.849: INFO: Deleting PersistentVolume "aws-xgcbp"
Jun  7 00:20:02.183: INFO: Couldn't delete PD "aws://us-west-2a/vol-0853409aa673c3a74", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0853409aa673c3a74 is currently attached to i-0335d6a9c2531bdc9
	status code: 400, request id: 44f5a091-6edc-43e7-94bd-044f9d65ea6a
Jun  7 00:20:07.614: INFO: Couldn't delete PD "aws://us-west-2a/vol-0853409aa673c3a74", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0853409aa673c3a74 is currently attached to i-0335d6a9c2531bdc9
	status code: 400, request id: 53a5a312-6d70-4c16-9dba-d8f1d4ee9d00
Jun  7 00:20:13.029: INFO: Couldn't delete PD "aws://us-west-2a/vol-0853409aa673c3a74", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0853409aa673c3a74 is currently attached to i-0335d6a9c2531bdc9
	status code: 400, request id: 0dc472ca-d802-493e-b31f-9ed559a04455
Jun  7 00:20:18.427: INFO: Couldn't delete PD "aws://us-west-2a/vol-0853409aa673c3a74", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0853409aa673c3a74 is currently attached to i-0335d6a9c2531bdc9
	status code: 400, request id: 8f5c4ae9-c520-4dd8-91c8-c6e0918eecd2
Jun  7 00:20:23.924: INFO: Successfully deleted PD "aws://us-west-2a/vol-0853409aa673c3a74".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  7 00:20:23.924: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8156" for this suite.
... skipping 437 lines ...

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

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 322 lines ...
Jun  7 00:20:57.881: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 54 lines ...
Jun  7 00:20:17.241: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6725bw58k
STEP: creating a claim
Jun  7 00:20:17.304: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-2jbb
STEP: Creating a pod to test subpath
Jun  7 00:20:17.499: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-2jbb" in namespace "provisioning-6725" to be "Succeeded or Failed"
Jun  7 00:20:17.562: INFO: Pod "pod-subpath-test-dynamicpv-2jbb": Phase="Pending", Reason="", readiness=false. Elapsed: 62.428026ms
Jun  7 00:20:19.625: INFO: Pod "pod-subpath-test-dynamicpv-2jbb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.125181747s
Jun  7 00:20:21.687: INFO: Pod "pod-subpath-test-dynamicpv-2jbb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.187894534s
Jun  7 00:20:23.750: INFO: Pod "pod-subpath-test-dynamicpv-2jbb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.25012022s
Jun  7 00:20:25.812: INFO: Pod "pod-subpath-test-dynamicpv-2jbb": Phase="Pending", Reason="", readiness=false. Elapsed: 8.312517538s
Jun  7 00:20:27.876: INFO: Pod "pod-subpath-test-dynamicpv-2jbb": Phase="Pending", Reason="", readiness=false. Elapsed: 10.376974918s
... skipping 2 lines ...
Jun  7 00:20:34.067: INFO: Pod "pod-subpath-test-dynamicpv-2jbb": Phase="Pending", Reason="", readiness=false. Elapsed: 16.567358343s
Jun  7 00:20:36.134: INFO: Pod "pod-subpath-test-dynamicpv-2jbb": Phase="Pending", Reason="", readiness=false. Elapsed: 18.63420832s
Jun  7 00:20:38.197: INFO: Pod "pod-subpath-test-dynamicpv-2jbb": Phase="Pending", Reason="", readiness=false. Elapsed: 20.697724839s
Jun  7 00:20:40.261: INFO: Pod "pod-subpath-test-dynamicpv-2jbb": Phase="Pending", Reason="", readiness=false. Elapsed: 22.761624461s
Jun  7 00:20:42.324: INFO: Pod "pod-subpath-test-dynamicpv-2jbb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.824239977s
STEP: Saw pod success
Jun  7 00:20:42.324: INFO: Pod "pod-subpath-test-dynamicpv-2jbb" satisfied condition "Succeeded or Failed"
Jun  7 00:20:42.386: INFO: Trying to get logs from node ip-172-20-63-204.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-2jbb container test-container-subpath-dynamicpv-2jbb: <nil>
STEP: delete the pod
Jun  7 00:20:42.520: INFO: Waiting for pod pod-subpath-test-dynamicpv-2jbb to disappear
Jun  7 00:20:42.582: INFO: Pod pod-subpath-test-dynamicpv-2jbb no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-2jbb
Jun  7 00:20:42.582: INFO: Deleting pod "pod-subpath-test-dynamicpv-2jbb" in namespace "provisioning-6725"
... skipping 110 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  7 00:20:08.783: 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.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun  7 00:20:09.087: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  7 00:20:09.087: INFO: Creating resource for dynamic PV
Jun  7 00:20:09.087: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3386xsbxs
STEP: creating a claim
Jun  7 00:20:09.148: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-d2q7
STEP: Checking for subpath error in container status
Jun  7 00:20:33.462: INFO: Deleting pod "pod-subpath-test-dynamicpv-d2q7" in namespace "provisioning-3386"
Jun  7 00:20:33.527: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-d2q7" to be fully deleted
STEP: Deleting pod
Jun  7 00:20:43.649: INFO: Deleting pod "pod-subpath-test-dynamicpv-d2q7" in namespace "provisioning-3386"
STEP: Deleting pvc
Jun  7 00:20:43.830: INFO: Deleting PersistentVolumeClaim "aws527b2"
... skipping 13 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.r42VbgPIn/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.r42VbgPIn/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath file is outside the volume [Slow][LinuxOnly]
      /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  7 00:20:24.060: 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.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun  7 00:20:24.391: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  7 00:20:24.391: INFO: Creating resource for dynamic PV
Jun  7 00:20:24.391: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7241c6v5k
STEP: creating a claim
Jun  7 00:20:24.457: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-7qwm
STEP: Checking for subpath error in container status
Jun  7 00:20:40.789: INFO: Deleting pod "pod-subpath-test-dynamicpv-7qwm" in namespace "provisioning-7241"
Jun  7 00:20:40.888: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-7qwm" to be fully deleted
STEP: Deleting pod
Jun  7 00:20:51.024: INFO: Deleting pod "pod-subpath-test-dynamicpv-7qwm" in namespace "provisioning-7241"
STEP: Deleting pvc
Jun  7 00:20:51.220: INFO: Deleting PersistentVolumeClaim "awsr7wbp"
... skipping 12 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.r42VbgPIn/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.r42VbgPIn/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.r42VbgPIn/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.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  7 00:21:01.686: 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.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.r42VbgPIn/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.r42VbgPIn/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.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 194 lines ...

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

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

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.r42VbgPIn/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.r42VbgPIn/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.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 53 lines ...
Jun  7 00:20:18.870: INFO: Creating resource for dynamic PV
Jun  7 00:20:18.870: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9075486xx
STEP: creating a claim
Jun  7 00:20:18.930: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-9075
Jun  7 00:20:19.110: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-9075" in namespace "provisioning-9075" to be "Succeeded or Failed"
Jun  7 00:20:19.170: INFO: Pod "volume-prep-provisioning-9075": Phase="Pending", Reason="", readiness=false. Elapsed: 59.149906ms
Jun  7 00:20:21.229: INFO: Pod "volume-prep-provisioning-9075": Phase="Pending", Reason="", readiness=false. Elapsed: 2.118989779s
Jun  7 00:20:23.291: INFO: Pod "volume-prep-provisioning-9075": Phase="Pending", Reason="", readiness=false. Elapsed: 4.181020205s
Jun  7 00:20:25.352: INFO: Pod "volume-prep-provisioning-9075": Phase="Pending", Reason="", readiness=false. Elapsed: 6.241476436s
Jun  7 00:20:27.411: INFO: Pod "volume-prep-provisioning-9075": Phase="Pending", Reason="", readiness=false. Elapsed: 8.30097209s
Jun  7 00:20:29.479: INFO: Pod "volume-prep-provisioning-9075": Phase="Pending", Reason="", readiness=false. Elapsed: 10.36812974s
Jun  7 00:20:31.538: INFO: Pod "volume-prep-provisioning-9075": Phase="Pending", Reason="", readiness=false. Elapsed: 12.427448648s
Jun  7 00:20:33.598: INFO: Pod "volume-prep-provisioning-9075": Phase="Pending", Reason="", readiness=false. Elapsed: 14.487733674s
Jun  7 00:20:35.658: INFO: Pod "volume-prep-provisioning-9075": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.547243039s
STEP: Saw pod success
Jun  7 00:20:35.658: INFO: Pod "volume-prep-provisioning-9075" satisfied condition "Succeeded or Failed"
Jun  7 00:20:35.658: INFO: Deleting pod "volume-prep-provisioning-9075" in namespace "provisioning-9075"
Jun  7 00:20:35.724: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-9075" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-dxg7
STEP: Checking for subpath error in container status
Jun  7 00:20:45.974: INFO: Deleting pod "pod-subpath-test-dynamicpv-dxg7" in namespace "provisioning-9075"
Jun  7 00:20:46.035: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-dxg7" to be fully deleted
STEP: Deleting pod
Jun  7 00:20:46.094: INFO: Deleting pod "pod-subpath-test-dynamicpv-dxg7" in namespace "provisioning-9075"
STEP: Deleting pvc
Jun  7 00:20:46.270: INFO: Deleting PersistentVolumeClaim "aws2nfds"
... skipping 216 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.r42VbgPIn/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.r42VbgPIn/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.r42VbgPIn/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.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Distro debian doesn't support ntfs -- skipping

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

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 221 lines ...
Jun  7 00:21:18.529: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

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

Jun  7 00:21:18.684: INFO: Error updating pvc ebs.csi.aws.comxp7k7: PersistentVolumeClaim "ebs.csi.aws.comxp7k7" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4122-e2e-scnzwn2",
  	... // 2 identical fields
  }

Jun  7 00:21:20.689: INFO: Error updating pvc ebs.csi.aws.comxp7k7: PersistentVolumeClaim "ebs.csi.aws.comxp7k7" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4122-e2e-scnzwn2",
  	... // 2 identical fields
  }

Jun  7 00:21:22.684: INFO: Error updating pvc ebs.csi.aws.comxp7k7: PersistentVolumeClaim "ebs.csi.aws.comxp7k7" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4122-e2e-scnzwn2",
  	... // 2 identical fields
  }

Jun  7 00:21:24.687: INFO: Error updating pvc ebs.csi.aws.comxp7k7: PersistentVolumeClaim "ebs.csi.aws.comxp7k7" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4122-e2e-scnzwn2",
  	... // 2 identical fields
  }

Jun  7 00:21:26.685: INFO: Error updating pvc ebs.csi.aws.comxp7k7: PersistentVolumeClaim "ebs.csi.aws.comxp7k7" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4122-e2e-scnzwn2",
  	... // 2 identical fields
  }

Jun  7 00:21:28.686: INFO: Error updating pvc ebs.csi.aws.comxp7k7: PersistentVolumeClaim "ebs.csi.aws.comxp7k7" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4122-e2e-scnzwn2",
  	... // 2 identical fields
  }

Jun  7 00:21:30.688: INFO: Error updating pvc ebs.csi.aws.comxp7k7: PersistentVolumeClaim "ebs.csi.aws.comxp7k7" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4122-e2e-scnzwn2",
  	... // 2 identical fields
  }

Jun  7 00:21:32.685: INFO: Error updating pvc ebs.csi.aws.comxp7k7: PersistentVolumeClaim "ebs.csi.aws.comxp7k7" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4122-e2e-scnzwn2",
  	... // 2 identical fields
  }

Jun  7 00:21:34.687: INFO: Error updating pvc ebs.csi.aws.comxp7k7: PersistentVolumeClaim "ebs.csi.aws.comxp7k7" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4122-e2e-scnzwn2",
  	... // 2 identical fields
  }

Jun  7 00:21:36.690: INFO: Error updating pvc ebs.csi.aws.comxp7k7: PersistentVolumeClaim "ebs.csi.aws.comxp7k7" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4122-e2e-scnzwn2",
  	... // 2 identical fields
  }

Jun  7 00:21:38.685: INFO: Error updating pvc ebs.csi.aws.comxp7k7: PersistentVolumeClaim "ebs.csi.aws.comxp7k7" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4122-e2e-scnzwn2",
  	... // 2 identical fields
  }

Jun  7 00:21:40.691: INFO: Error updating pvc ebs.csi.aws.comxp7k7: PersistentVolumeClaim "ebs.csi.aws.comxp7k7" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4122-e2e-scnzwn2",
  	... // 2 identical fields
  }

Jun  7 00:21:42.684: INFO: Error updating pvc ebs.csi.aws.comxp7k7: PersistentVolumeClaim "ebs.csi.aws.comxp7k7" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4122-e2e-scnzwn2",
  	... // 2 identical fields
  }

Jun  7 00:21:44.684: INFO: Error updating pvc ebs.csi.aws.comxp7k7: PersistentVolumeClaim "ebs.csi.aws.comxp7k7" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4122-e2e-scnzwn2",
  	... // 2 identical fields
  }

Jun  7 00:21:46.689: INFO: Error updating pvc ebs.csi.aws.comxp7k7: PersistentVolumeClaim "ebs.csi.aws.comxp7k7" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4122-e2e-scnzwn2",
  	... // 2 identical fields
  }

Jun  7 00:21:46.810: INFO: Error updating pvc ebs.csi.aws.comxp7k7: PersistentVolumeClaim "ebs.csi.aws.comxp7k7" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 38 lines ...
Jun  7 00:21:07.128: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  7 00:21:07.681: INFO: Successfully created a new PD: "aws://us-west-2a/vol-0e7cbfaeabb6ff373".
Jun  7 00:21:07.682: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-h8kk
STEP: Creating a pod to test exec-volume-test
Jun  7 00:21:07.744: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-h8kk" in namespace "volume-5724" to be "Succeeded or Failed"
Jun  7 00:21:07.804: INFO: Pod "exec-volume-test-inlinevolume-h8kk": Phase="Pending", Reason="", readiness=false. Elapsed: 59.527199ms
Jun  7 00:21:09.864: INFO: Pod "exec-volume-test-inlinevolume-h8kk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.119235649s
Jun  7 00:21:11.924: INFO: Pod "exec-volume-test-inlinevolume-h8kk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.179274094s
Jun  7 00:21:13.983: INFO: Pod "exec-volume-test-inlinevolume-h8kk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.239050194s
Jun  7 00:21:16.043: INFO: Pod "exec-volume-test-inlinevolume-h8kk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.298935095s
Jun  7 00:21:18.105: INFO: Pod "exec-volume-test-inlinevolume-h8kk": Phase="Pending", Reason="", readiness=false. Elapsed: 10.360365144s
Jun  7 00:21:20.167: INFO: Pod "exec-volume-test-inlinevolume-h8kk": Phase="Pending", Reason="", readiness=false. Elapsed: 12.422260529s
Jun  7 00:21:22.227: INFO: Pod "exec-volume-test-inlinevolume-h8kk": Phase="Pending", Reason="", readiness=false. Elapsed: 14.482858411s
Jun  7 00:21:24.289: INFO: Pod "exec-volume-test-inlinevolume-h8kk": Phase="Pending", Reason="", readiness=false. Elapsed: 16.544247147s
Jun  7 00:21:26.348: INFO: Pod "exec-volume-test-inlinevolume-h8kk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.603475486s
STEP: Saw pod success
Jun  7 00:21:26.348: INFO: Pod "exec-volume-test-inlinevolume-h8kk" satisfied condition "Succeeded or Failed"
Jun  7 00:21:26.411: INFO: Trying to get logs from node ip-172-20-63-204.us-west-2.compute.internal pod exec-volume-test-inlinevolume-h8kk container exec-container-inlinevolume-h8kk: <nil>
STEP: delete the pod
Jun  7 00:21:26.537: INFO: Waiting for pod exec-volume-test-inlinevolume-h8kk to disappear
Jun  7 00:21:26.596: INFO: Pod exec-volume-test-inlinevolume-h8kk no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-h8kk
Jun  7 00:21:26.596: INFO: Deleting pod "exec-volume-test-inlinevolume-h8kk" in namespace "volume-5724"
Jun  7 00:21:26.849: INFO: Couldn't delete PD "aws://us-west-2a/vol-0e7cbfaeabb6ff373", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e7cbfaeabb6ff373 is currently attached to i-09e0e7c964e660c26
	status code: 400, request id: ee3d7a52-75d9-482a-9c2d-29587ed1d54e
Jun  7 00:21:32.299: INFO: Couldn't delete PD "aws://us-west-2a/vol-0e7cbfaeabb6ff373", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e7cbfaeabb6ff373 is currently attached to i-09e0e7c964e660c26
	status code: 400, request id: 63a2daa0-fe5e-43d9-82d6-16f0499fa746
Jun  7 00:21:37.992: INFO: Couldn't delete PD "aws://us-west-2a/vol-0e7cbfaeabb6ff373", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e7cbfaeabb6ff373 is currently attached to i-09e0e7c964e660c26
	status code: 400, request id: f3cbb734-4522-4261-876c-fb6b9aa93ca3
Jun  7 00:21:43.433: INFO: Couldn't delete PD "aws://us-west-2a/vol-0e7cbfaeabb6ff373", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e7cbfaeabb6ff373 is currently attached to i-09e0e7c964e660c26
	status code: 400, request id: f672dee2-f009-47fd-b49a-0ee633bc8b43
Jun  7 00:21:48.851: INFO: Successfully deleted PD "aws://us-west-2a/vol-0e7cbfaeabb6ff373".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  7 00:21:48.851: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-5724" for this suite.
... skipping 23 lines ...
Jun  7 00:20:58.202: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-519-e2e-scdm7w7
STEP: creating a claim
Jun  7 00:20:58.264: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-nk6m
STEP: Creating a pod to test exec-volume-test
Jun  7 00:20:58.452: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-nk6m" in namespace "volume-519" to be "Succeeded or Failed"
Jun  7 00:20:58.513: INFO: Pod "exec-volume-test-dynamicpv-nk6m": Phase="Pending", Reason="", readiness=false. Elapsed: 61.355405ms
Jun  7 00:21:00.575: INFO: Pod "exec-volume-test-dynamicpv-nk6m": Phase="Pending", Reason="", readiness=false. Elapsed: 2.123071949s
Jun  7 00:21:02.636: INFO: Pod "exec-volume-test-dynamicpv-nk6m": Phase="Pending", Reason="", readiness=false. Elapsed: 4.184797687s
Jun  7 00:21:04.699: INFO: Pod "exec-volume-test-dynamicpv-nk6m": Phase="Pending", Reason="", readiness=false. Elapsed: 6.247326041s
Jun  7 00:21:06.762: INFO: Pod "exec-volume-test-dynamicpv-nk6m": Phase="Pending", Reason="", readiness=false. Elapsed: 8.310247067s
Jun  7 00:21:08.823: INFO: Pod "exec-volume-test-dynamicpv-nk6m": Phase="Pending", Reason="", readiness=false. Elapsed: 10.371812767s
... skipping 9 lines ...
Jun  7 00:21:29.446: INFO: Pod "exec-volume-test-dynamicpv-nk6m": Phase="Pending", Reason="", readiness=false. Elapsed: 30.994109685s
Jun  7 00:21:31.507: INFO: Pod "exec-volume-test-dynamicpv-nk6m": Phase="Pending", Reason="", readiness=false. Elapsed: 33.055259892s
Jun  7 00:21:33.569: INFO: Pod "exec-volume-test-dynamicpv-nk6m": Phase="Pending", Reason="", readiness=false. Elapsed: 35.117455795s
Jun  7 00:21:35.630: INFO: Pod "exec-volume-test-dynamicpv-nk6m": Phase="Pending", Reason="", readiness=false. Elapsed: 37.178689506s
Jun  7 00:21:37.693: INFO: Pod "exec-volume-test-dynamicpv-nk6m": Phase="Succeeded", Reason="", readiness=false. Elapsed: 39.241259245s
STEP: Saw pod success
Jun  7 00:21:37.693: INFO: Pod "exec-volume-test-dynamicpv-nk6m" satisfied condition "Succeeded or Failed"
Jun  7 00:21:37.754: INFO: Trying to get logs from node ip-172-20-38-247.us-west-2.compute.internal pod exec-volume-test-dynamicpv-nk6m container exec-container-dynamicpv-nk6m: <nil>
STEP: delete the pod
Jun  7 00:21:37.885: INFO: Waiting for pod exec-volume-test-dynamicpv-nk6m to disappear
Jun  7 00:21:37.946: INFO: Pod exec-volume-test-dynamicpv-nk6m no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-nk6m
Jun  7 00:21:37.946: INFO: Deleting pod "exec-volume-test-dynamicpv-nk6m" in namespace "volume-519"
... skipping 55 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  7 00:21:06.623: 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.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun  7 00:21:06.955: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  7 00:21:06.955: INFO: Creating resource for dynamic PV
Jun  7 00:21:06.955: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8485qz2vc
STEP: creating a claim
Jun  7 00:21:07.018: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-nmx5
STEP: Checking for subpath error in container status
Jun  7 00:21:31.337: INFO: Deleting pod "pod-subpath-test-dynamicpv-nmx5" in namespace "provisioning-8485"
Jun  7 00:21:31.404: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-nmx5" to be fully deleted
STEP: Deleting pod
Jun  7 00:21:41.534: INFO: Deleting pod "pod-subpath-test-dynamicpv-nmx5" in namespace "provisioning-8485"
STEP: Deleting pvc
Jun  7 00:21:41.729: INFO: Deleting PersistentVolumeClaim "aws7zlbm"
... skipping 13 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.r42VbgPIn/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.r42VbgPIn/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath directory is outside the volume [Slow][LinuxOnly]
      /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  7 00:21:57.249: INFO: Driver supports dynamic provisioning, skipping PreprovisionedPV pattern
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
... skipping 171 lines ...
STEP: Deleting pod hostexec-ip-172-20-63-204.us-west-2.compute.internal-25ks8 in namespace volumemode-205
Jun  7 00:21:45.725: INFO: Deleting pod "pod-25a29ae7-02f7-4a1a-93a7-d208dd8297f7" in namespace "volumemode-205"
Jun  7 00:21:45.787: INFO: Wait up to 5m0s for pod "pod-25a29ae7-02f7-4a1a-93a7-d208dd8297f7" to be fully deleted
STEP: Deleting pv and pvc
Jun  7 00:21:57.908: INFO: Deleting PersistentVolumeClaim "pvc-5xm7p"
Jun  7 00:21:57.970: INFO: Deleting PersistentVolume "aws-flpkv"
Jun  7 00:21:58.246: INFO: Couldn't delete PD "aws://us-west-2a/vol-0afcdba45b013830e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0afcdba45b013830e is currently attached to i-09e0e7c964e660c26
	status code: 400, request id: 9fa20d31-acf5-4c6a-9983-f52c28463f1f
Jun  7 00:22:03.659: INFO: Successfully deleted PD "aws://us-west-2a/vol-0afcdba45b013830e".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  7 00:22:03.659: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-205" for this suite.
... skipping 276 lines ...
Jun  7 00:21:17.315: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4367-e2e-sct55pk
STEP: creating a claim
Jun  7 00:21:17.377: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-dcsb
STEP: Creating a pod to test subpath
Jun  7 00:21:17.567: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-dcsb" in namespace "provisioning-4367" to be "Succeeded or Failed"
Jun  7 00:21:17.629: INFO: Pod "pod-subpath-test-dynamicpv-dcsb": Phase="Pending", Reason="", readiness=false. Elapsed: 61.310106ms
Jun  7 00:21:19.691: INFO: Pod "pod-subpath-test-dynamicpv-dcsb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.123088843s
Jun  7 00:21:21.753: INFO: Pod "pod-subpath-test-dynamicpv-dcsb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.185599961s
Jun  7 00:21:23.814: INFO: Pod "pod-subpath-test-dynamicpv-dcsb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.246849172s
Jun  7 00:21:25.876: INFO: Pod "pod-subpath-test-dynamicpv-dcsb": Phase="Pending", Reason="", readiness=false. Elapsed: 8.308075419s
Jun  7 00:21:27.938: INFO: Pod "pod-subpath-test-dynamicpv-dcsb": Phase="Pending", Reason="", readiness=false. Elapsed: 10.370624546s
Jun  7 00:21:30.000: INFO: Pod "pod-subpath-test-dynamicpv-dcsb": Phase="Pending", Reason="", readiness=false. Elapsed: 12.432421547s
Jun  7 00:21:32.061: INFO: Pod "pod-subpath-test-dynamicpv-dcsb": Phase="Pending", Reason="", readiness=false. Elapsed: 14.493825369s
Jun  7 00:21:34.124: INFO: Pod "pod-subpath-test-dynamicpv-dcsb": Phase="Pending", Reason="", readiness=false. Elapsed: 16.556114183s
Jun  7 00:21:36.185: INFO: Pod "pod-subpath-test-dynamicpv-dcsb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.617555465s
STEP: Saw pod success
Jun  7 00:21:36.185: INFO: Pod "pod-subpath-test-dynamicpv-dcsb" satisfied condition "Succeeded or Failed"
Jun  7 00:21:36.247: INFO: Trying to get logs from node ip-172-20-63-204.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-dcsb container test-container-subpath-dynamicpv-dcsb: <nil>
STEP: delete the pod
Jun  7 00:21:36.381: INFO: Waiting for pod pod-subpath-test-dynamicpv-dcsb to disappear
Jun  7 00:21:36.441: INFO: Pod pod-subpath-test-dynamicpv-dcsb no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-dcsb
Jun  7 00:21:36.441: INFO: Deleting pod "pod-subpath-test-dynamicpv-dcsb" in namespace "provisioning-4367"
... skipping 30 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  7 00:21:41.309: 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.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  7 00:21:41.623: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  7 00:21:42.242: INFO: Successfully created a new PD: "aws://us-west-2a/vol-006cbec5a9d681650".
Jun  7 00:21:42.242: INFO: Creating resource for pre-provisioned PV
Jun  7 00:21:42.243: INFO: Creating PVC and PV
... skipping 7 lines ...
Jun  7 00:21:50.811: INFO: PersistentVolumeClaim pvc-8t9s8 found but phase is Pending instead of Bound.
Jun  7 00:21:52.876: INFO: PersistentVolumeClaim pvc-8t9s8 found but phase is Pending instead of Bound.
Jun  7 00:21:54.939: INFO: PersistentVolumeClaim pvc-8t9s8 found and phase=Bound (12.444769564s)
Jun  7 00:21:54.939: INFO: Waiting up to 3m0s for PersistentVolume aws-69rxc to have phase Bound
Jun  7 00:21:55.019: INFO: PersistentVolume aws-69rxc found and phase=Bound (80.41839ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  7 00:21:57.412: INFO: Deleting pod "pod-6ce92b42-85ce-4eee-a3fd-52ec9a45d57c" in namespace "volumemode-7393"
Jun  7 00:21:57.476: INFO: Wait up to 5m0s for pod "pod-6ce92b42-85ce-4eee-a3fd-52ec9a45d57c" to be fully deleted
STEP: Deleting pv and pvc
Jun  7 00:22:07.607: INFO: Deleting PersistentVolumeClaim "pvc-8t9s8"
Jun  7 00:22:07.670: INFO: Deleting PersistentVolume "aws-69rxc"
Jun  7 00:22:07.957: INFO: Couldn't delete PD "aws://us-west-2a/vol-006cbec5a9d681650", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-006cbec5a9d681650 is currently attached to i-09e0e7c964e660c26
	status code: 400, request id: 3110390e-acfc-4186-a52f-6ccd067dc6e1
Jun  7 00:22:13.400: INFO: Successfully deleted PD "aws://us-west-2a/vol-006cbec5a9d681650".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  7 00:22:13.401: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-7393" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.r42VbgPIn/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.r42VbgPIn/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
    /tmp/kops.r42VbgPIn/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.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  7 00:21:47.126: 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.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  7 00:21:47.429: INFO: Creating resource for dynamic PV
Jun  7 00:21:47.429: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-1313-e2e-scdm8lg
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  7 00:21:53.871: INFO: Deleting pod "pod-db2ba4a8-88a1-4ee5-bc87-5bf6a192b397" in namespace "volumemode-1313"
Jun  7 00:21:53.935: INFO: Wait up to 5m0s for pod "pod-db2ba4a8-88a1-4ee5-bc87-5bf6a192b397" to be fully deleted
STEP: Deleting pvc
Jun  7 00:21:58.183: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comwrjl9"
Jun  7 00:21:58.244: INFO: Waiting up to 5m0s for PersistentVolume pvc-4ebdbae6-9ab3-40e3-8f05-f5fa6e6333c6 to get deleted
Jun  7 00:21:58.305: INFO: PersistentVolume pvc-4ebdbae6-9ab3-40e3-8f05-f5fa6e6333c6 found and phase=Released (60.434758ms)
... skipping 9 lines ...

• [SLOW TEST:26.563 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.r42VbgPIn/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.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [sig-storage] Zone Support [Feature:vsphere]
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  7 00:22:13.533: INFO: >>> kubeConfig: /root/.kube/config
... skipping 170 lines ...
Jun  7 00:20:20.335: INFO: Creating resource for dynamic PV
Jun  7 00:20:20.335: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-1831-e2e-sch5rv5
STEP: creating a claim
Jun  7 00:20:20.398: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun  7 00:20:20.598: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-nhwd5" in namespace "snapshotting-1831" to be "Succeeded or Failed"
Jun  7 00:20:20.663: INFO: Pod "pvc-snapshottable-tester-nhwd5": Phase="Pending", Reason="", readiness=false. Elapsed: 65.362044ms
Jun  7 00:20:22.726: INFO: Pod "pvc-snapshottable-tester-nhwd5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.128246572s
Jun  7 00:20:24.793: INFO: Pod "pvc-snapshottable-tester-nhwd5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.195588072s
Jun  7 00:20:26.856: INFO: Pod "pvc-snapshottable-tester-nhwd5": Phase="Pending", Reason="", readiness=false. Elapsed: 6.258415101s
Jun  7 00:20:28.936: INFO: Pod "pvc-snapshottable-tester-nhwd5": Phase="Pending", Reason="", readiness=false. Elapsed: 8.338448409s
Jun  7 00:20:30.999: INFO: Pod "pvc-snapshottable-tester-nhwd5": Phase="Pending", Reason="", readiness=false. Elapsed: 10.401591541s
Jun  7 00:20:33.063: INFO: Pod "pvc-snapshottable-tester-nhwd5": Phase="Pending", Reason="", readiness=false. Elapsed: 12.46504428s
Jun  7 00:20:35.125: INFO: Pod "pvc-snapshottable-tester-nhwd5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.527295079s
STEP: Saw pod success
Jun  7 00:20:35.125: INFO: Pod "pvc-snapshottable-tester-nhwd5" satisfied condition "Succeeded or Failed"
Jun  7 00:20:35.250: INFO: Pod pvc-snapshottable-tester-nhwd5 has the following logs: 
Jun  7 00:20:35.250: INFO: Deleting pod "pvc-snapshottable-tester-nhwd5" in namespace "snapshotting-1831"
Jun  7 00:20:35.324: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-nhwd5" to be fully deleted
Jun  7 00:20:35.386: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comgxsj2] to have phase Bound
Jun  7 00:20:35.449: INFO: PersistentVolumeClaim ebs.csi.aws.comgxsj2 found and phase=Bound (62.739575ms)
STEP: [init] checking the claim
... skipping 25 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.r42VbgPIn/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  7 00:21:07.097: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-5d56p" in namespace "snapshotting-1831" to be "Succeeded or Failed"
Jun  7 00:21:07.162: INFO: Pod "pvc-snapshottable-data-tester-5d56p": Phase="Pending", Reason="", readiness=false. Elapsed: 64.23195ms
Jun  7 00:21:09.224: INFO: Pod "pvc-snapshottable-data-tester-5d56p": Phase="Pending", Reason="", readiness=false. Elapsed: 2.126452417s
Jun  7 00:21:11.287: INFO: Pod "pvc-snapshottable-data-tester-5d56p": Phase="Pending", Reason="", readiness=false. Elapsed: 4.189745857s
Jun  7 00:21:13.351: INFO: Pod "pvc-snapshottable-data-tester-5d56p": Phase="Pending", Reason="", readiness=false. Elapsed: 6.2533296s
Jun  7 00:21:15.413: INFO: Pod "pvc-snapshottable-data-tester-5d56p": Phase="Pending", Reason="", readiness=false. Elapsed: 8.315555156s
Jun  7 00:21:17.477: INFO: Pod "pvc-snapshottable-data-tester-5d56p": Phase="Pending", Reason="", readiness=false. Elapsed: 10.379863513s
Jun  7 00:21:19.546: INFO: Pod "pvc-snapshottable-data-tester-5d56p": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.448406259s
STEP: Saw pod success
Jun  7 00:21:19.546: INFO: Pod "pvc-snapshottable-data-tester-5d56p" satisfied condition "Succeeded or Failed"
Jun  7 00:21:19.675: INFO: Pod pvc-snapshottable-data-tester-5d56p has the following logs: 
Jun  7 00:21:19.675: INFO: Deleting pod "pvc-snapshottable-data-tester-5d56p" in namespace "snapshotting-1831"
Jun  7 00:21:19.746: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-5d56p" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun  7 00:21:30.056: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-1831 exec restored-pvc-tester-hgf7t --namespace=snapshotting-1831 -- cat /mnt/test/data'
... skipping 48 lines ...
Jun  7 00:22:13.064: INFO: At 2021-06-07 00:21:23 +0000 UTC - event for restored-pvc-tester-hgf7t: {default-scheduler } Scheduled: Successfully assigned snapshotting-1831/restored-pvc-tester-hgf7t to ip-172-20-63-204.us-west-2.compute.internal
Jun  7 00:22:13.064: INFO: At 2021-06-07 00:21:26 +0000 UTC - event for restored-pvc-tester-hgf7t: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-6a5114b3-bb3d-421b-b06a-ee5fc0e33e74" 
Jun  7 00:22:13.064: INFO: At 2021-06-07 00:21:28 +0000 UTC - event for restored-pvc-tester-hgf7t: {kubelet ip-172-20-63-204.us-west-2.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" already present on machine
Jun  7 00:22:13.064: INFO: At 2021-06-07 00:21:28 +0000 UTC - event for restored-pvc-tester-hgf7t: {kubelet ip-172-20-63-204.us-west-2.compute.internal} Created: Created container volume-tester
Jun  7 00:22:13.064: INFO: At 2021-06-07 00:21:28 +0000 UTC - event for restored-pvc-tester-hgf7t: {kubelet ip-172-20-63-204.us-west-2.compute.internal} Started: Started container volume-tester
Jun  7 00:22:13.064: INFO: At 2021-06-07 00:21:31 +0000 UTC - event for restored-pvc-tester-hgf7t: {kubelet ip-172-20-63-204.us-west-2.compute.internal} Killing: Stopping container volume-tester
Jun  7 00:22:13.064: INFO: At 2021-06-07 00:22:07 +0000 UTC - event for snapshot-72pv9: {snapshot-controller } SnapshotContentObjectDeleteError: Failed to delete snapshot content API object
Jun  7 00:22:13.064: INFO: At 2021-06-07 00:22:07 +0000 UTC - event for snapshot-72pv9: {snapshot-controller } GetSnapshotClassFailed: Failed to get snapshot class with error volumesnapshotclass.snapshot.storage.k8s.io "snapshotting-1831-vscjshvw" not found
Jun  7 00:22:13.125: INFO: POD  NODE  PHASE  GRACE  CONDITIONS
Jun  7 00:22:13.125: INFO: 
Jun  7 00:22:13.188: INFO: 
Logging node info for node ip-172-20-38-247.us-west-2.compute.internal
Jun  7 00:22:13.250: INFO: Node Info: &Node{ObjectMeta:{ip-172-20-38-247.us-west-2.compute.internal    1fdcc0f1-7f6b-42c1-91c9-fdbecf2c6fb3 8261 0 2021-06-07 00:14:40 +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:us-west-2 failure-domain.beta.kubernetes.io/zone:us-west-2a kops.k8s.io/instancegroup:nodes-us-west-2a kubernetes.io/arch:amd64 kubernetes.io/hostname:ip-172-20-38-247.us-west-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:us-west-2a topology.kubernetes.io/region:us-west-2 topology.kubernetes.io/zone:us-west-2a] map[csi.volume.kubernetes.io/nodeid:{"ebs.csi.aws.com":"i-0b83558ad417b9266"} node.alpha.kubernetes.io/ttl:0 projectcalico.org/IPv4Address:172.20.38.247/19 projectcalico.org/IPv4IPIPTunnelAddr:100.127.128.128 volumes.kubernetes.io/controller-managed-attach-detach:true] [] []  [{kops-controller Update v1 2021-06-07 00:14:40 +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-07 00:15:03 +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-07 00:18:50 +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-07 00:18:51 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"100.96.2.0/24\"":{}}},"f:status":{"f:volumesAttached":{}}}}]},Spec:NodeSpec{PodCIDR:100.96.2.0/24,DoNotUseExternalID:,ProviderID:aws:///us-west-2a/i-0b83558ad417b9266,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[100.96.2.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-07 00:15:03 +0000 UTC,LastTransitionTime:2021-06-07 00:15:03 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2021-06-07 00:22:10 +0000 UTC,LastTransitionTime:2021-06-07 00:14:40 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2021-06-07 00:22:10 +0000 UTC,LastTransitionTime:2021-06-07 00:14:40 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2021-06-07 00:22:10 +0000 UTC,LastTransitionTime:2021-06-07 00:14:40 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2021-06-07 00:22:10 +0000 UTC,LastTransitionTime:2021-06-07 00:15:00 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:172.20.38.247,},NodeAddress{Type:ExternalIP,Address:35.166.123.1,},NodeAddress{Type:Hostname,Address:ip-172-20-38-247.us-west-2.compute.internal,},NodeAddress{Type:InternalDNS,Address:ip-172-20-38-247.us-west-2.compute.internal,},NodeAddress{Type:ExternalDNS,Address:ec2-35-166-123-1.us-west-2.compute.amazonaws.com,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:ec20c8ce43fb0735106d5d0a85fb36fb,SystemUUID:ec20c8ce-43fb-0735-106d-5d0a85fb36fb,BootID:9c24fd7d-118a-4192-8225-1b722de3baf3,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-cainjector@sha256:51c0df411b66aa175e9fc6840f3135d55b52c3781d0b3d4aa10862066d460193 quay.io/jetstack/cert-manager-cainjector:v1.3.1],SizeBytes:19215137,},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-063319f6b367fc773 kubernetes.io/csi/ebs.csi.aws.com^vol-097dc0082e2ed002c kubernetes.io/csi/ebs.csi.aws.com^vol-0a89387ed5aeb1a05],VolumesAttached:[]AttachedVolume{AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-0a89387ed5aeb1a05,DevicePath:,},AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-063319f6b367fc773,DevicePath:,},},Config:nil,},}
Jun  7 00:22:13.250: INFO: 
... skipping 188 lines ...
    /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:108
      
      /tmp/kops.r42VbgPIn/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.r42VbgPIn/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-1831 exec restored-pvc-tester-hgf7t --namespace=snapshotting-1831 -- 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-1831 exec restored-pvc-tester-hgf7t --namespace=snapshotting-1831 -- 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.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:602
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] volumes
... skipping 74 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  7 00:22:01.663: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename volumemode
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail to use a volume in a pod with mismatched mode [Slow]
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  7 00:22:01.970: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  7 00:22:01.970: INFO: Creating resource for dynamic PV
Jun  7 00:22:01.970: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-2912d2bqg
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  7 00:22:08.403: INFO: Deleting pod "pod-4f5f6fe4-de8b-48ef-8ff4-bffac047e372" in namespace "volumemode-2912"
Jun  7 00:22:08.466: INFO: Wait up to 5m0s for pod "pod-4f5f6fe4-de8b-48ef-8ff4-bffac047e372" to be fully deleted
STEP: Deleting pvc
Jun  7 00:22:12.708: INFO: Deleting PersistentVolumeClaim "awsckrtd"
Jun  7 00:22:12.770: INFO: Waiting up to 5m0s for PersistentVolume pvc-7d344257-60c8-4a84-a0cf-e58e0adcae07 to get deleted
Jun  7 00:22:12.833: INFO: PersistentVolume pvc-7d344257-60c8-4a84-a0cf-e58e0adcae07 found and phase=Released (63.686734ms)
... skipping 10 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.r42VbgPIn/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.r42VbgPIn/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
    /tmp/kops.r42VbgPIn/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.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 907 lines ...
Jun  7 00:22:25.108: INFO: Waiting for pod aws-client to disappear
Jun  7 00:22:25.171: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun  7 00:22:25.171: INFO: Deleting PersistentVolumeClaim "pvc-5mgww"
Jun  7 00:22:25.235: INFO: Deleting PersistentVolume "aws-vrtzr"
Jun  7 00:22:25.526: INFO: Couldn't delete PD "aws://us-west-2a/vol-0d9184674d1053394", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d9184674d1053394 is currently attached to i-0ec9cfc7096a1018a
	status code: 400, request id: e96e67cd-5b80-4262-b501-13954d8f2c2b
Jun  7 00:22:30.955: INFO: Couldn't delete PD "aws://us-west-2a/vol-0d9184674d1053394", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d9184674d1053394 is currently attached to i-0ec9cfc7096a1018a
	status code: 400, request id: b86de96e-46c1-4266-aeef-ef43c6b3cdab
Jun  7 00:22:36.400: INFO: Couldn't delete PD "aws://us-west-2a/vol-0d9184674d1053394", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d9184674d1053394 is currently attached to i-0ec9cfc7096a1018a
	status code: 400, request id: 42020935-34c4-41ad-b935-1a79bdd210a3
Jun  7 00:22:41.780: INFO: Successfully deleted PD "aws://us-west-2a/vol-0d9184674d1053394".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  7 00:22:41.780: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-6600" for this suite.
... skipping 64 lines ...

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

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

    /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 52 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  7 00:22:12.450: 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.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun  7 00:22:12.760: INFO: Creating resource for dynamic PV
Jun  7 00:22:12.760: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8465-e2e-sckfltp
STEP: creating a claim
Jun  7 00:22:12.834: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-sn97
STEP: Checking for subpath error in container status
Jun  7 00:22:35.145: INFO: Deleting pod "pod-subpath-test-dynamicpv-sn97" in namespace "provisioning-8465"
Jun  7 00:22:35.221: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-sn97" to be fully deleted
STEP: Deleting pod
Jun  7 00:22:51.347: INFO: Deleting pod "pod-subpath-test-dynamicpv-sn97" in namespace "provisioning-8465"
STEP: Deleting pvc
Jun  7 00:22:51.529: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comft5rj"
... skipping 9 lines ...

• [SLOW TEST:44.452 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath file is outside the volume [Slow][LinuxOnly]
    /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [sig-storage] Zone Support [Feature:vsphere]
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  7 00:22:56.904: INFO: >>> kubeConfig: /root/.kube/config
... skipping 29 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.r42VbgPIn/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.r42VbgPIn/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.r42VbgPIn/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.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.r42VbgPIn/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.r42VbgPIn/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.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 42 lines ...
Jun  7 00:20:35.689: INFO: Creating resource for dynamic PV
Jun  7 00:20:35.689: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-901-e2e-sclx72w
STEP: creating a claim
Jun  7 00:20:35.752: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun  7 00:20:35.944: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-jpc2z" in namespace "snapshotting-901" to be "Succeeded or Failed"
Jun  7 00:20:36.005: INFO: Pod "pvc-snapshottable-tester-jpc2z": Phase="Pending", Reason="", readiness=false. Elapsed: 60.428098ms
Jun  7 00:20:38.066: INFO: Pod "pvc-snapshottable-tester-jpc2z": Phase="Pending", Reason="", readiness=false. Elapsed: 2.121514972s
Jun  7 00:20:40.127: INFO: Pod "pvc-snapshottable-tester-jpc2z": Phase="Pending", Reason="", readiness=false. Elapsed: 4.182763854s
Jun  7 00:20:42.200: INFO: Pod "pvc-snapshottable-tester-jpc2z": Phase="Pending", Reason="", readiness=false. Elapsed: 6.255963133s
Jun  7 00:20:44.261: INFO: Pod "pvc-snapshottable-tester-jpc2z": Phase="Pending", Reason="", readiness=false. Elapsed: 8.317216396s
Jun  7 00:20:46.324: INFO: Pod "pvc-snapshottable-tester-jpc2z": Phase="Pending", Reason="", readiness=false. Elapsed: 10.379615205s
... skipping 2 lines ...
Jun  7 00:20:52.511: INFO: Pod "pvc-snapshottable-tester-jpc2z": Phase="Pending", Reason="", readiness=false. Elapsed: 16.567093742s
Jun  7 00:20:54.573: INFO: Pod "pvc-snapshottable-tester-jpc2z": Phase="Pending", Reason="", readiness=false. Elapsed: 18.628919308s
Jun  7 00:20:56.635: INFO: Pod "pvc-snapshottable-tester-jpc2z": Phase="Pending", Reason="", readiness=false. Elapsed: 20.690547448s
Jun  7 00:20:58.697: INFO: Pod "pvc-snapshottable-tester-jpc2z": Phase="Pending", Reason="", readiness=false. Elapsed: 22.752872651s
Jun  7 00:21:00.758: INFO: Pod "pvc-snapshottable-tester-jpc2z": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.814003581s
STEP: Saw pod success
Jun  7 00:21:00.758: INFO: Pod "pvc-snapshottable-tester-jpc2z" satisfied condition "Succeeded or Failed"
Jun  7 00:21:00.880: INFO: Pod pvc-snapshottable-tester-jpc2z has the following logs: 
Jun  7 00:21:00.880: INFO: Deleting pod "pvc-snapshottable-tester-jpc2z" in namespace "snapshotting-901"
Jun  7 00:21:00.946: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-jpc2z" to be fully deleted
Jun  7 00:21:01.007: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.compfqg6] to have phase Bound
Jun  7 00:21:01.067: INFO: PersistentVolumeClaim ebs.csi.aws.compfqg6 found and phase=Bound (60.517449ms)
STEP: [init] checking the claim
... skipping 37 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.r42VbgPIn/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  7 00:21:20.936: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-wrg8r" in namespace "snapshotting-901" to be "Succeeded or Failed"
Jun  7 00:21:20.998: INFO: Pod "pvc-snapshottable-data-tester-wrg8r": Phase="Pending", Reason="", readiness=false. Elapsed: 61.913581ms
Jun  7 00:21:23.059: INFO: Pod "pvc-snapshottable-data-tester-wrg8r": Phase="Pending", Reason="", readiness=false. Elapsed: 2.123140582s
Jun  7 00:21:25.123: INFO: Pod "pvc-snapshottable-data-tester-wrg8r": Phase="Pending", Reason="", readiness=false. Elapsed: 4.18695968s
Jun  7 00:21:27.185: INFO: Pod "pvc-snapshottable-data-tester-wrg8r": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.248718638s
STEP: Saw pod success
Jun  7 00:21:27.185: INFO: Pod "pvc-snapshottable-data-tester-wrg8r" satisfied condition "Succeeded or Failed"
Jun  7 00:21:27.311: INFO: Pod pvc-snapshottable-data-tester-wrg8r has the following logs: 
Jun  7 00:21:27.311: INFO: Deleting pod "pvc-snapshottable-data-tester-wrg8r" in namespace "snapshotting-901"
Jun  7 00:21:27.378: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-wrg8r" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun  7 00:21:41.693: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-901 exec restored-pvc-tester-n8tlx --namespace=snapshotting-901 -- cat /mnt/test/data'
... skipping 32 lines ...
Jun  7 00:22:07.121: INFO: volumesnapshotcontents pre-provisioned-snapcontent-be41084d-66d8-4550-99ba-8c300b2c60ec has been found and is not deleted
Jun  7 00:22:08.182: INFO: volumesnapshotcontents pre-provisioned-snapcontent-be41084d-66d8-4550-99ba-8c300b2c60ec has been found and is not deleted
Jun  7 00:22:09.243: INFO: volumesnapshotcontents pre-provisioned-snapcontent-be41084d-66d8-4550-99ba-8c300b2c60ec has been found and is not deleted
Jun  7 00:22:10.306: INFO: volumesnapshotcontents pre-provisioned-snapcontent-be41084d-66d8-4550-99ba-8c300b2c60ec has been found and is not deleted
Jun  7 00:22:11.367: INFO: volumesnapshotcontents pre-provisioned-snapcontent-be41084d-66d8-4550-99ba-8c300b2c60ec has been found and is not deleted
Jun  7 00:22:12.428: INFO: volumesnapshotcontents pre-provisioned-snapcontent-be41084d-66d8-4550-99ba-8c300b2c60ec has been found and is not deleted
Jun  7 00:22:13.428: INFO: WaitUntil failed after reaching the timeout 30s
[AfterEach] volume snapshot controller
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:221
Jun  7 00:22:13.491: INFO: Pod restored-pvc-tester-n8tlx has the following logs: 
Jun  7 00:22:13.491: INFO: Deleting pod "restored-pvc-tester-n8tlx" in namespace "snapshotting-901"
Jun  7 00:22:13.556: INFO: Wait up to 5m0s for pod "restored-pvc-tester-n8tlx" to be fully deleted
Jun  7 00:22:57.681: INFO: deleting claim "snapshotting-901"/"pvc-spqsk"
... skipping 40 lines ...

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

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

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

      Not enough topologies in cluster -- skipping

      /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 35 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  7 00:22:31.225: 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.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  7 00:22:31.536: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  7 00:22:31.536: INFO: Creating resource for dynamic PV
Jun  7 00:22:31.536: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-9823nj8nl
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  7 00:22:39.979: INFO: Deleting pod "pod-af721b3b-f800-4954-86c0-ddd39cb6b652" in namespace "volumemode-9823"
Jun  7 00:22:40.046: INFO: Wait up to 5m0s for pod "pod-af721b3b-f800-4954-86c0-ddd39cb6b652" to be fully deleted
STEP: Deleting pvc
Jun  7 00:22:44.299: INFO: Deleting PersistentVolumeClaim "awsfnkx7"
Jun  7 00:22:44.363: INFO: Waiting up to 5m0s for PersistentVolume pvc-77a6ee23-513e-4e99-979a-56afa85d1970 to get deleted
Jun  7 00:22:44.426: INFO: PersistentVolume pvc-77a6ee23-513e-4e99-979a-56afa85d1970 found and phase=Released (63.166501ms)
... skipping 13 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.r42VbgPIn/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.r42VbgPIn/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (block volmode)] volumeMode
    /tmp/kops.r42VbgPIn/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.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Inline-volume (ntfs)][Feature:Windows] volumes
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  7 00:23:09.947: INFO: Distro debian doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Inline-volume (ntfs)][Feature:Windows] volumes
... skipping 214 lines ...
Jun  7 00:23:04.868: INFO: Pod aws-client still exists
Jun  7 00:23:06.806: INFO: Waiting for pod aws-client to disappear
Jun  7 00:23:06.866: INFO: Pod aws-client still exists
Jun  7 00:23:08.807: INFO: Waiting for pod aws-client to disappear
Jun  7 00:23:08.868: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun  7 00:23:09.128: INFO: Couldn't delete PD "aws://us-west-2a/vol-0af8df584bd930d26", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0af8df584bd930d26 is currently attached to i-09e0e7c964e660c26
	status code: 400, request id: 484f628b-44fd-4b66-b591-b68ad21f078b
Jun  7 00:23:14.566: INFO: Couldn't delete PD "aws://us-west-2a/vol-0af8df584bd930d26", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0af8df584bd930d26 is currently attached to i-09e0e7c964e660c26
	status code: 400, request id: 4dc7398b-727c-4c1d-b9da-a6b650bf4294
Jun  7 00:23:19.964: INFO: Successfully deleted PD "aws://us-west-2a/vol-0af8df584bd930d26".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  7 00:23:19.964: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-7511" for this suite.
... skipping 307 lines ...
Jun  7 00:22:33.259: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8032-e2e-schm5d4
STEP: creating a claim
Jun  7 00:22:33.322: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-gtk9
STEP: Creating a pod to test subpath
Jun  7 00:22:33.510: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-gtk9" in namespace "provisioning-8032" to be "Succeeded or Failed"
Jun  7 00:22:33.571: INFO: Pod "pod-subpath-test-dynamicpv-gtk9": Phase="Pending", Reason="", readiness=false. Elapsed: 61.091678ms
Jun  7 00:22:35.632: INFO: Pod "pod-subpath-test-dynamicpv-gtk9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.122178764s
Jun  7 00:22:37.704: INFO: Pod "pod-subpath-test-dynamicpv-gtk9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.193715236s
Jun  7 00:22:39.765: INFO: Pod "pod-subpath-test-dynamicpv-gtk9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.254955912s
Jun  7 00:22:41.826: INFO: Pod "pod-subpath-test-dynamicpv-gtk9": Phase="Pending", Reason="", readiness=false. Elapsed: 8.316145421s
Jun  7 00:22:43.888: INFO: Pod "pod-subpath-test-dynamicpv-gtk9": Phase="Pending", Reason="", readiness=false. Elapsed: 10.378252579s
Jun  7 00:22:45.950: INFO: Pod "pod-subpath-test-dynamicpv-gtk9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.439976302s
STEP: Saw pod success
Jun  7 00:22:45.950: INFO: Pod "pod-subpath-test-dynamicpv-gtk9" satisfied condition "Succeeded or Failed"
Jun  7 00:22:46.016: INFO: Trying to get logs from node ip-172-20-38-247.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-gtk9 container test-container-subpath-dynamicpv-gtk9: <nil>
STEP: delete the pod
Jun  7 00:22:46.159: INFO: Waiting for pod pod-subpath-test-dynamicpv-gtk9 to disappear
Jun  7 00:22:46.220: INFO: Pod pod-subpath-test-dynamicpv-gtk9 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-gtk9
Jun  7 00:22:46.220: INFO: Deleting pod "pod-subpath-test-dynamicpv-gtk9" in namespace "provisioning-8032"
... skipping 269 lines ...

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

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

    /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:92
------------------------------
... skipping 88 lines ...
Jun  7 00:22:36.294: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4150-e2e-sc55mck
STEP: creating a claim
Jun  7 00:22:36.359: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-2w9m
STEP: Creating a pod to test subpath
Jun  7 00:22:36.553: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-2w9m" in namespace "provisioning-4150" to be "Succeeded or Failed"
Jun  7 00:22:36.617: INFO: Pod "pod-subpath-test-dynamicpv-2w9m": Phase="Pending", Reason="", readiness=false. Elapsed: 63.693029ms
Jun  7 00:22:38.681: INFO: Pod "pod-subpath-test-dynamicpv-2w9m": Phase="Pending", Reason="", readiness=false. Elapsed: 2.128099016s
Jun  7 00:22:40.752: INFO: Pod "pod-subpath-test-dynamicpv-2w9m": Phase="Pending", Reason="", readiness=false. Elapsed: 4.198996636s
Jun  7 00:22:42.816: INFO: Pod "pod-subpath-test-dynamicpv-2w9m": Phase="Pending", Reason="", readiness=false. Elapsed: 6.263562305s
Jun  7 00:22:44.881: INFO: Pod "pod-subpath-test-dynamicpv-2w9m": Phase="Pending", Reason="", readiness=false. Elapsed: 8.327975223s
Jun  7 00:22:46.950: INFO: Pod "pod-subpath-test-dynamicpv-2w9m": Phase="Pending", Reason="", readiness=false. Elapsed: 10.397503372s
Jun  7 00:22:49.014: INFO: Pod "pod-subpath-test-dynamicpv-2w9m": Phase="Pending", Reason="", readiness=false. Elapsed: 12.461539773s
Jun  7 00:22:51.079: INFO: Pod "pod-subpath-test-dynamicpv-2w9m": Phase="Pending", Reason="", readiness=false. Elapsed: 14.525723877s
Jun  7 00:22:53.142: INFO: Pod "pod-subpath-test-dynamicpv-2w9m": Phase="Pending", Reason="", readiness=false. Elapsed: 16.589514041s
Jun  7 00:22:55.206: INFO: Pod "pod-subpath-test-dynamicpv-2w9m": Phase="Pending", Reason="", readiness=false. Elapsed: 18.653240189s
Jun  7 00:22:57.270: INFO: Pod "pod-subpath-test-dynamicpv-2w9m": Phase="Pending", Reason="", readiness=false. Elapsed: 20.717302878s
Jun  7 00:22:59.334: INFO: Pod "pod-subpath-test-dynamicpv-2w9m": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.781056137s
STEP: Saw pod success
Jun  7 00:22:59.334: INFO: Pod "pod-subpath-test-dynamicpv-2w9m" satisfied condition "Succeeded or Failed"
Jun  7 00:22:59.397: INFO: Trying to get logs from node ip-172-20-40-22.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-2w9m container test-container-subpath-dynamicpv-2w9m: <nil>
STEP: delete the pod
Jun  7 00:22:59.532: INFO: Waiting for pod pod-subpath-test-dynamicpv-2w9m to disappear
Jun  7 00:22:59.595: INFO: Pod pod-subpath-test-dynamicpv-2w9m no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-2w9m
Jun  7 00:22:59.595: INFO: Deleting pod "pod-subpath-test-dynamicpv-2w9m" in namespace "provisioning-4150"
... skipping 186 lines ...
Jun  7 00:23:28.332: INFO: Pod aws-client still exists
Jun  7 00:23:30.271: INFO: Waiting for pod aws-client to disappear
Jun  7 00:23:30.330: INFO: Pod aws-client still exists
Jun  7 00:23:32.271: INFO: Waiting for pod aws-client to disappear
Jun  7 00:23:32.330: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun  7 00:23:32.740: INFO: Couldn't delete PD "aws://us-west-2a/vol-0232ca059c3e00a8a", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0232ca059c3e00a8a is currently attached to i-0b83558ad417b9266
	status code: 400, request id: 6ab3144e-13ac-45ca-84b0-1b3519e11af0
Jun  7 00:23:38.127: INFO: Successfully deleted PD "aws://us-west-2a/vol-0232ca059c3e00a8a".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  7 00:23:38.128: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-2170" for this suite.
... skipping 39 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.r42VbgPIn/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.r42VbgPIn/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.r42VbgPIn/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.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 745 lines ...
Jun  7 00:23:06.915: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-6140-e2e-scbgrpq
STEP: creating a claim
Jun  7 00:23:06.976: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-5jcn
STEP: Creating a pod to test exec-volume-test
Jun  7 00:23:07.160: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-5jcn" in namespace "volume-6140" to be "Succeeded or Failed"
Jun  7 00:23:07.220: INFO: Pod "exec-volume-test-dynamicpv-5jcn": Phase="Pending", Reason="", readiness=false. Elapsed: 60.721182ms
Jun  7 00:23:09.282: INFO: Pod "exec-volume-test-dynamicpv-5jcn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.122442002s
Jun  7 00:23:11.344: INFO: Pod "exec-volume-test-dynamicpv-5jcn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.184377273s
Jun  7 00:23:13.407: INFO: Pod "exec-volume-test-dynamicpv-5jcn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.247013502s
Jun  7 00:23:15.468: INFO: Pod "exec-volume-test-dynamicpv-5jcn": Phase="Pending", Reason="", readiness=false. Elapsed: 8.308794588s
Jun  7 00:23:17.536: INFO: Pod "exec-volume-test-dynamicpv-5jcn": Phase="Pending", Reason="", readiness=false. Elapsed: 10.376479952s
Jun  7 00:23:19.597: INFO: Pod "exec-volume-test-dynamicpv-5jcn": Phase="Pending", Reason="", readiness=false. Elapsed: 12.43731738s
Jun  7 00:23:21.657: INFO: Pod "exec-volume-test-dynamicpv-5jcn": Phase="Pending", Reason="", readiness=false. Elapsed: 14.497879872s
Jun  7 00:23:23.720: INFO: Pod "exec-volume-test-dynamicpv-5jcn": Phase="Pending", Reason="", readiness=false. Elapsed: 16.560456508s
Jun  7 00:23:25.782: INFO: Pod "exec-volume-test-dynamicpv-5jcn": Phase="Pending", Reason="", readiness=false. Elapsed: 18.622771936s
Jun  7 00:23:27.846: INFO: Pod "exec-volume-test-dynamicpv-5jcn": Phase="Pending", Reason="", readiness=false. Elapsed: 20.686450542s
Jun  7 00:23:29.907: INFO: Pod "exec-volume-test-dynamicpv-5jcn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.747382832s
STEP: Saw pod success
Jun  7 00:23:29.907: INFO: Pod "exec-volume-test-dynamicpv-5jcn" satisfied condition "Succeeded or Failed"
Jun  7 00:23:29.969: INFO: Trying to get logs from node ip-172-20-40-22.us-west-2.compute.internal pod exec-volume-test-dynamicpv-5jcn container exec-container-dynamicpv-5jcn: <nil>
STEP: delete the pod
Jun  7 00:23:30.098: INFO: Waiting for pod exec-volume-test-dynamicpv-5jcn to disappear
Jun  7 00:23:30.159: INFO: Pod exec-volume-test-dynamicpv-5jcn no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-5jcn
Jun  7 00:23:30.159: INFO: Deleting pod "exec-volume-test-dynamicpv-5jcn" in namespace "volume-6140"
... skipping 44 lines ...
Jun  7 00:23:37.255: INFO: PersistentVolumeClaim pvc-7rmv7 found but phase is Pending instead of Bound.
Jun  7 00:23:39.319: INFO: PersistentVolumeClaim pvc-7rmv7 found and phase=Bound (2.12700994s)
Jun  7 00:23:39.319: INFO: Waiting up to 3m0s for PersistentVolume aws-lhtrc to have phase Bound
Jun  7 00:23:39.383: INFO: PersistentVolume aws-lhtrc found and phase=Bound (63.472814ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-v86h
STEP: Creating a pod to test exec-volume-test
Jun  7 00:23:39.575: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-v86h" in namespace "volume-9898" to be "Succeeded or Failed"
Jun  7 00:23:39.639: INFO: Pod "exec-volume-test-preprovisionedpv-v86h": Phase="Pending", Reason="", readiness=false. Elapsed: 63.410383ms
Jun  7 00:23:41.703: INFO: Pod "exec-volume-test-preprovisionedpv-v86h": Phase="Pending", Reason="", readiness=false. Elapsed: 2.127789364s
Jun  7 00:23:43.767: INFO: Pod "exec-volume-test-preprovisionedpv-v86h": Phase="Pending", Reason="", readiness=false. Elapsed: 4.191955363s
Jun  7 00:23:45.832: INFO: Pod "exec-volume-test-preprovisionedpv-v86h": Phase="Pending", Reason="", readiness=false. Elapsed: 6.256905154s
Jun  7 00:23:47.897: INFO: Pod "exec-volume-test-preprovisionedpv-v86h": Phase="Pending", Reason="", readiness=false. Elapsed: 8.321483121s
Jun  7 00:23:49.961: INFO: Pod "exec-volume-test-preprovisionedpv-v86h": Phase="Pending", Reason="", readiness=false. Elapsed: 10.385264287s
Jun  7 00:23:52.024: INFO: Pod "exec-volume-test-preprovisionedpv-v86h": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.449208085s
STEP: Saw pod success
Jun  7 00:23:52.025: INFO: Pod "exec-volume-test-preprovisionedpv-v86h" satisfied condition "Succeeded or Failed"
Jun  7 00:23:52.088: INFO: Trying to get logs from node ip-172-20-63-224.us-west-2.compute.internal pod exec-volume-test-preprovisionedpv-v86h container exec-container-preprovisionedpv-v86h: <nil>
STEP: delete the pod
Jun  7 00:23:52.224: INFO: Waiting for pod exec-volume-test-preprovisionedpv-v86h to disappear
Jun  7 00:23:52.287: INFO: Pod exec-volume-test-preprovisionedpv-v86h no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-v86h
Jun  7 00:23:52.287: INFO: Deleting pod "exec-volume-test-preprovisionedpv-v86h" in namespace "volume-9898"
STEP: Deleting pv and pvc
Jun  7 00:23:52.351: INFO: Deleting PersistentVolumeClaim "pvc-7rmv7"
Jun  7 00:23:52.415: INFO: Deleting PersistentVolume "aws-lhtrc"
Jun  7 00:23:52.717: INFO: Couldn't delete PD "aws://us-west-2a/vol-02f404ec30006c256", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02f404ec30006c256 is currently attached to i-0ec9cfc7096a1018a
	status code: 400, request id: be88bad5-109a-4087-ae5f-86cb778807d7
Jun  7 00:23:58.128: INFO: Couldn't delete PD "aws://us-west-2a/vol-02f404ec30006c256", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02f404ec30006c256 is currently attached to i-0ec9cfc7096a1018a
	status code: 400, request id: d18258f9-1fb5-4b0b-acc5-32fd45979742
Jun  7 00:24:03.532: INFO: Couldn't delete PD "aws://us-west-2a/vol-02f404ec30006c256", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02f404ec30006c256 is currently attached to i-0ec9cfc7096a1018a
	status code: 400, request id: 6afec6da-2b0c-4266-8909-ec3649588054
Jun  7 00:24:08.947: INFO: Successfully deleted PD "aws://us-west-2a/vol-02f404ec30006c256".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  7 00:24:08.947: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-9898" for this suite.
... skipping 465 lines ...
Jun  7 00:23:38.567: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-8158wxmpx
STEP: creating a claim
Jun  7 00:23:38.626: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-nsl8
STEP: Creating a pod to test exec-volume-test
Jun  7 00:23:38.811: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-nsl8" in namespace "volume-8158" to be "Succeeded or Failed"
Jun  7 00:23:38.870: INFO: Pod "exec-volume-test-dynamicpv-nsl8": Phase="Pending", Reason="", readiness=false. Elapsed: 58.430107ms
Jun  7 00:23:40.931: INFO: Pod "exec-volume-test-dynamicpv-nsl8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.119896994s
Jun  7 00:23:42.990: INFO: Pod "exec-volume-test-dynamicpv-nsl8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.17882793s
Jun  7 00:23:45.050: INFO: Pod "exec-volume-test-dynamicpv-nsl8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.238705051s
Jun  7 00:23:47.109: INFO: Pod "exec-volume-test-dynamicpv-nsl8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.298079049s
Jun  7 00:23:49.169: INFO: Pod "exec-volume-test-dynamicpv-nsl8": Phase="Pending", Reason="", readiness=false. Elapsed: 10.357526202s
Jun  7 00:23:51.230: INFO: Pod "exec-volume-test-dynamicpv-nsl8": Phase="Pending", Reason="", readiness=false. Elapsed: 12.418253244s
Jun  7 00:23:53.290: INFO: Pod "exec-volume-test-dynamicpv-nsl8": Phase="Pending", Reason="", readiness=false. Elapsed: 14.478283061s
Jun  7 00:23:55.348: INFO: Pod "exec-volume-test-dynamicpv-nsl8": Phase="Pending", Reason="", readiness=false. Elapsed: 16.537161527s
Jun  7 00:23:57.409: INFO: Pod "exec-volume-test-dynamicpv-nsl8": Phase="Pending", Reason="", readiness=false. Elapsed: 18.597670115s
Jun  7 00:23:59.472: INFO: Pod "exec-volume-test-dynamicpv-nsl8": Phase="Pending", Reason="", readiness=false. Elapsed: 20.660796272s
Jun  7 00:24:01.531: INFO: Pod "exec-volume-test-dynamicpv-nsl8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.719948805s
STEP: Saw pod success
Jun  7 00:24:01.531: INFO: Pod "exec-volume-test-dynamicpv-nsl8" satisfied condition "Succeeded or Failed"
Jun  7 00:24:01.596: INFO: Trying to get logs from node ip-172-20-38-247.us-west-2.compute.internal pod exec-volume-test-dynamicpv-nsl8 container exec-container-dynamicpv-nsl8: <nil>
STEP: delete the pod
Jun  7 00:24:01.723: INFO: Waiting for pod exec-volume-test-dynamicpv-nsl8 to disappear
Jun  7 00:24:01.781: INFO: Pod exec-volume-test-dynamicpv-nsl8 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-nsl8
Jun  7 00:24:01.781: INFO: Deleting pod "exec-volume-test-dynamicpv-nsl8" in namespace "volume-8158"
... skipping 38 lines ...
Jun  7 00:23:52.140: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-9827m5279
STEP: creating a claim
Jun  7 00:23:52.203: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-m6w9
STEP: Creating a pod to test exec-volume-test
Jun  7 00:23:52.399: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-m6w9" in namespace "volume-9827" to be "Succeeded or Failed"
Jun  7 00:23:52.462: INFO: Pod "exec-volume-test-dynamicpv-m6w9": Phase="Pending", Reason="", readiness=false. Elapsed: 62.993534ms
Jun  7 00:23:54.526: INFO: Pod "exec-volume-test-dynamicpv-m6w9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.126938046s
Jun  7 00:23:56.590: INFO: Pod "exec-volume-test-dynamicpv-m6w9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.19128804s
Jun  7 00:23:58.655: INFO: Pod "exec-volume-test-dynamicpv-m6w9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.255900688s
Jun  7 00:24:00.720: INFO: Pod "exec-volume-test-dynamicpv-m6w9": Phase="Pending", Reason="", readiness=false. Elapsed: 8.320753569s
Jun  7 00:24:02.785: INFO: Pod "exec-volume-test-dynamicpv-m6w9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.385637928s
STEP: Saw pod success
Jun  7 00:24:02.785: INFO: Pod "exec-volume-test-dynamicpv-m6w9" satisfied condition "Succeeded or Failed"
Jun  7 00:24:02.862: INFO: Trying to get logs from node ip-172-20-63-204.us-west-2.compute.internal pod exec-volume-test-dynamicpv-m6w9 container exec-container-dynamicpv-m6w9: <nil>
STEP: delete the pod
Jun  7 00:24:02.997: INFO: Waiting for pod exec-volume-test-dynamicpv-m6w9 to disappear
Jun  7 00:24:03.060: INFO: Pod exec-volume-test-dynamicpv-m6w9 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-m6w9
Jun  7 00:24:03.060: INFO: Deleting pod "exec-volume-test-dynamicpv-m6w9" in namespace "volume-9827"
... skipping 82 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.r42VbgPIn/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.r42VbgPIn/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.r42VbgPIn/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.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Driver supports dynamic provisioning, skipping InlineVolume pattern

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 219 lines ...
Jun  7 00:23:59.816: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-20709d9tn
STEP: creating a claim
Jun  7 00:23:59.880: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-2zrv
STEP: Creating a pod to test subpath
Jun  7 00:24:00.076: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-2zrv" in namespace "provisioning-2070" to be "Succeeded or Failed"
Jun  7 00:24:00.140: INFO: Pod "pod-subpath-test-dynamicpv-2zrv": Phase="Pending", Reason="", readiness=false. Elapsed: 63.902608ms
Jun  7 00:24:02.205: INFO: Pod "pod-subpath-test-dynamicpv-2zrv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.128352283s
Jun  7 00:24:04.269: INFO: Pod "pod-subpath-test-dynamicpv-2zrv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.19249968s
Jun  7 00:24:06.334: INFO: Pod "pod-subpath-test-dynamicpv-2zrv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.257855734s
Jun  7 00:24:08.399: INFO: Pod "pod-subpath-test-dynamicpv-2zrv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.32309657s
Jun  7 00:24:10.463: INFO: Pod "pod-subpath-test-dynamicpv-2zrv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.386973903s
... skipping 2 lines ...
Jun  7 00:24:16.664: INFO: Pod "pod-subpath-test-dynamicpv-2zrv": Phase="Pending", Reason="", readiness=false. Elapsed: 16.587715306s
Jun  7 00:24:18.728: INFO: Pod "pod-subpath-test-dynamicpv-2zrv": Phase="Pending", Reason="", readiness=false. Elapsed: 18.651587396s
Jun  7 00:24:20.792: INFO: Pod "pod-subpath-test-dynamicpv-2zrv": Phase="Pending", Reason="", readiness=false. Elapsed: 20.716059245s
Jun  7 00:24:22.856: INFO: Pod "pod-subpath-test-dynamicpv-2zrv": Phase="Pending", Reason="", readiness=false. Elapsed: 22.779886938s
Jun  7 00:24:24.920: INFO: Pod "pod-subpath-test-dynamicpv-2zrv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.844136945s
STEP: Saw pod success
Jun  7 00:24:24.920: INFO: Pod "pod-subpath-test-dynamicpv-2zrv" satisfied condition "Succeeded or Failed"
Jun  7 00:24:24.984: INFO: Trying to get logs from node ip-172-20-63-204.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-2zrv container test-container-subpath-dynamicpv-2zrv: <nil>
STEP: delete the pod
Jun  7 00:24:25.120: INFO: Waiting for pod pod-subpath-test-dynamicpv-2zrv to disappear
Jun  7 00:24:25.183: INFO: Pod pod-subpath-test-dynamicpv-2zrv no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-2zrv
Jun  7 00:24:25.183: INFO: Deleting pod "pod-subpath-test-dynamicpv-2zrv" in namespace "provisioning-2070"
STEP: Creating pod pod-subpath-test-dynamicpv-2zrv
STEP: Creating a pod to test subpath
Jun  7 00:24:25.311: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-2zrv" in namespace "provisioning-2070" to be "Succeeded or Failed"
Jun  7 00:24:25.375: INFO: Pod "pod-subpath-test-dynamicpv-2zrv": Phase="Pending", Reason="", readiness=false. Elapsed: 63.770565ms
Jun  7 00:24:27.440: INFO: Pod "pod-subpath-test-dynamicpv-2zrv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.128626603s
Jun  7 00:24:29.504: INFO: Pod "pod-subpath-test-dynamicpv-2zrv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.192629728s
Jun  7 00:24:31.568: INFO: Pod "pod-subpath-test-dynamicpv-2zrv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.256563999s
STEP: Saw pod success
Jun  7 00:24:31.568: INFO: Pod "pod-subpath-test-dynamicpv-2zrv" satisfied condition "Succeeded or Failed"
Jun  7 00:24:31.633: INFO: Trying to get logs from node ip-172-20-63-204.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-2zrv container test-container-subpath-dynamicpv-2zrv: <nil>
STEP: delete the pod
Jun  7 00:24:31.771: INFO: Waiting for pod pod-subpath-test-dynamicpv-2zrv to disappear
Jun  7 00:24:31.834: INFO: Pod pod-subpath-test-dynamicpv-2zrv no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-2zrv
Jun  7 00:24:31.834: INFO: Deleting pod "pod-subpath-test-dynamicpv-2zrv" in namespace "provisioning-2070"
... skipping 393 lines ...
Jun  7 00:22:31.191: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-7863-e2e-sc9gzbc      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-7863    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-7863-e2e-sc9gzbc,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-7863    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-7863-e2e-sc9gzbc,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-7863    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-7863-e2e-sc9gzbc,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-7863-e2e-sc9gzbc    eb08eb7d-ecfb-4f63-8ea9-bc1530d9a9c5 8930 0 2021-06-07 00:22:31 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-07 00:22:31 +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-qwl6k pvc- provisioning-7863  3243a95b-e6a1-4362-a6b0-b71703060adc 8937 0 2021-06-07 00:22:31 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-07 00:22:31 +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-7863-e2e-sc9gzbc,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-6a863d1d-c4dc-4ff9-8b8d-e848e4e4b6f8 in namespace provisioning-7863
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun  7 00:23:09.902: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-lgm7m" in namespace "provisioning-7863" to be "Succeeded or Failed"
Jun  7 00:23:09.967: INFO: Pod "pvc-volume-tester-writer-lgm7m": Phase="Pending", Reason="", readiness=false. Elapsed: 65.220477ms
Jun  7 00:23:12.032: INFO: Pod "pvc-volume-tester-writer-lgm7m": Phase="Pending", Reason="", readiness=false. Elapsed: 2.130004822s
Jun  7 00:23:14.096: INFO: Pod "pvc-volume-tester-writer-lgm7m": Phase="Pending", Reason="", readiness=false. Elapsed: 4.194140124s
Jun  7 00:23:16.159: INFO: Pod "pvc-volume-tester-writer-lgm7m": Phase="Pending", Reason="", readiness=false. Elapsed: 6.257426272s
Jun  7 00:23:18.223: INFO: Pod "pvc-volume-tester-writer-lgm7m": Phase="Pending", Reason="", readiness=false. Elapsed: 8.32085354s
Jun  7 00:23:20.286: INFO: Pod "pvc-volume-tester-writer-lgm7m": Phase="Pending", Reason="", readiness=false. Elapsed: 10.383893309s
... skipping 7 lines ...
Jun  7 00:23:36.799: INFO: Pod "pvc-volume-tester-writer-lgm7m": Phase="Pending", Reason="", readiness=false. Elapsed: 26.89715615s
Jun  7 00:23:38.862: INFO: Pod "pvc-volume-tester-writer-lgm7m": Phase="Pending", Reason="", readiness=false. Elapsed: 28.960218178s
Jun  7 00:23:40.927: INFO: Pod "pvc-volume-tester-writer-lgm7m": Phase="Pending", Reason="", readiness=false. Elapsed: 31.024784706s
Jun  7 00:23:42.991: INFO: Pod "pvc-volume-tester-writer-lgm7m": Phase="Running", Reason="", readiness=true. Elapsed: 33.088922167s
Jun  7 00:23:45.054: INFO: Pod "pvc-volume-tester-writer-lgm7m": Phase="Succeeded", Reason="", readiness=false. Elapsed: 35.151899893s
STEP: Saw pod success
Jun  7 00:23:45.054: INFO: Pod "pvc-volume-tester-writer-lgm7m" satisfied condition "Succeeded or Failed"
Jun  7 00:23:45.184: INFO: Pod pvc-volume-tester-writer-lgm7m has the following logs: 
Jun  7 00:23:45.184: INFO: Deleting pod "pvc-volume-tester-writer-lgm7m" in namespace "provisioning-7863"
Jun  7 00:23:45.254: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-lgm7m" 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-63-204.us-west-2.compute.internal"
Jun  7 00:23:45.514: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-f25h7" in namespace "provisioning-7863" to be "Succeeded or Failed"
Jun  7 00:23:45.576: INFO: Pod "pvc-volume-tester-reader-f25h7": Phase="Pending", Reason="", readiness=false. Elapsed: 62.772631ms
Jun  7 00:23:47.641: INFO: Pod "pvc-volume-tester-reader-f25h7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.127477432s
STEP: Saw pod success
Jun  7 00:23:47.641: INFO: Pod "pvc-volume-tester-reader-f25h7" satisfied condition "Succeeded or Failed"
Jun  7 00:23:47.770: INFO: Pod pvc-volume-tester-reader-f25h7 has the following logs: hello world

Jun  7 00:23:47.770: INFO: Deleting pod "pvc-volume-tester-reader-f25h7" in namespace "provisioning-7863"
Jun  7 00:23:47.838: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-f25h7" to be fully deleted
Jun  7 00:23:47.901: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-qwl6k] to have phase Bound
Jun  7 00:23:47.964: INFO: PersistentVolumeClaim pvc-qwl6k found and phase=Bound (63.020813ms)
... skipping 319 lines ...
Jun  7 00:24:14.017: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9027xtg69
STEP: creating a claim
Jun  7 00:24:14.078: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-925t
STEP: Creating a pod to test subpath
Jun  7 00:24:14.270: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-925t" in namespace "provisioning-9027" to be "Succeeded or Failed"
Jun  7 00:24:14.331: INFO: Pod "pod-subpath-test-dynamicpv-925t": Phase="Pending", Reason="", readiness=false. Elapsed: 60.650389ms
Jun  7 00:24:16.393: INFO: Pod "pod-subpath-test-dynamicpv-925t": Phase="Pending", Reason="", readiness=false. Elapsed: 2.122379882s
Jun  7 00:24:18.455: INFO: Pod "pod-subpath-test-dynamicpv-925t": Phase="Pending", Reason="", readiness=false. Elapsed: 4.184458699s
Jun  7 00:24:20.517: INFO: Pod "pod-subpath-test-dynamicpv-925t": Phase="Pending", Reason="", readiness=false. Elapsed: 6.246977701s
Jun  7 00:24:22.578: INFO: Pod "pod-subpath-test-dynamicpv-925t": Phase="Pending", Reason="", readiness=false. Elapsed: 8.307879569s
Jun  7 00:24:24.639: INFO: Pod "pod-subpath-test-dynamicpv-925t": Phase="Pending", Reason="", readiness=false. Elapsed: 10.368969476s
... skipping 4 lines ...
Jun  7 00:24:34.946: INFO: Pod "pod-subpath-test-dynamicpv-925t": Phase="Pending", Reason="", readiness=false. Elapsed: 20.675166222s
Jun  7 00:24:37.006: INFO: Pod "pod-subpath-test-dynamicpv-925t": Phase="Pending", Reason="", readiness=false. Elapsed: 22.73598162s
Jun  7 00:24:39.068: INFO: Pod "pod-subpath-test-dynamicpv-925t": Phase="Pending", Reason="", readiness=false. Elapsed: 24.79795271s
Jun  7 00:24:41.130: INFO: Pod "pod-subpath-test-dynamicpv-925t": Phase="Pending", Reason="", readiness=false. Elapsed: 26.859178051s
Jun  7 00:24:43.191: INFO: Pod "pod-subpath-test-dynamicpv-925t": Phase="Succeeded", Reason="", readiness=false. Elapsed: 28.920109209s
STEP: Saw pod success
Jun  7 00:24:43.191: INFO: Pod "pod-subpath-test-dynamicpv-925t" satisfied condition "Succeeded or Failed"
Jun  7 00:24:43.251: INFO: Trying to get logs from node ip-172-20-63-224.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-925t container test-container-subpath-dynamicpv-925t: <nil>
STEP: delete the pod
Jun  7 00:24:43.405: INFO: Waiting for pod pod-subpath-test-dynamicpv-925t to disappear
Jun  7 00:24:43.466: INFO: Pod pod-subpath-test-dynamicpv-925t no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-925t
Jun  7 00:24:43.466: INFO: Deleting pod "pod-subpath-test-dynamicpv-925t" in namespace "provisioning-9027"
... skipping 255 lines ...
Jun  7 00:22:58.107: INFO: Creating resource for dynamic PV
Jun  7 00:22:58.107: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-5071-e2e-scxtphn
STEP: creating a claim
Jun  7 00:22:58.169: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun  7 00:22:58.354: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-dzs4z" in namespace "snapshotting-5071" to be "Succeeded or Failed"
Jun  7 00:22:58.416: INFO: Pod "pvc-snapshottable-tester-dzs4z": Phase="Pending", Reason="", readiness=false. Elapsed: 61.905479ms
Jun  7 00:23:00.478: INFO: Pod "pvc-snapshottable-tester-dzs4z": Phase="Pending", Reason="", readiness=false. Elapsed: 2.123888264s
Jun  7 00:23:02.540: INFO: Pod "pvc-snapshottable-tester-dzs4z": Phase="Pending", Reason="", readiness=false. Elapsed: 4.185475923s
Jun  7 00:23:04.606: INFO: Pod "pvc-snapshottable-tester-dzs4z": Phase="Pending", Reason="", readiness=false. Elapsed: 6.252073341s
Jun  7 00:23:06.669: INFO: Pod "pvc-snapshottable-tester-dzs4z": Phase="Pending", Reason="", readiness=false. Elapsed: 8.314712693s
Jun  7 00:23:08.731: INFO: Pod "pvc-snapshottable-tester-dzs4z": Phase="Pending", Reason="", readiness=false. Elapsed: 10.377400184s
Jun  7 00:23:10.798: INFO: Pod "pvc-snapshottable-tester-dzs4z": Phase="Pending", Reason="", readiness=false. Elapsed: 12.443645897s
Jun  7 00:23:12.860: INFO: Pod "pvc-snapshottable-tester-dzs4z": Phase="Pending", Reason="", readiness=false. Elapsed: 14.505766555s
Jun  7 00:23:14.923: INFO: Pod "pvc-snapshottable-tester-dzs4z": Phase="Pending", Reason="", readiness=false. Elapsed: 16.56862658s
Jun  7 00:23:16.984: INFO: Pod "pvc-snapshottable-tester-dzs4z": Phase="Pending", Reason="", readiness=false. Elapsed: 18.630000494s
Jun  7 00:23:19.047: INFO: Pod "pvc-snapshottable-tester-dzs4z": Phase="Pending", Reason="", readiness=false. Elapsed: 20.692715849s
Jun  7 00:23:21.110: INFO: Pod "pvc-snapshottable-tester-dzs4z": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.755966645s
STEP: Saw pod success
Jun  7 00:23:21.110: INFO: Pod "pvc-snapshottable-tester-dzs4z" satisfied condition "Succeeded or Failed"
Jun  7 00:23:21.234: INFO: Pod pvc-snapshottable-tester-dzs4z has the following logs: 
Jun  7 00:23:21.234: INFO: Deleting pod "pvc-snapshottable-tester-dzs4z" in namespace "snapshotting-5071"
Jun  7 00:23:21.313: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-dzs4z" to be fully deleted
Jun  7 00:23:21.374: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comp5mhd] to have phase Bound
Jun  7 00:23:21.437: INFO: PersistentVolumeClaim ebs.csi.aws.comp5mhd found and phase=Bound (63.258557ms)
STEP: [init] checking the claim
... skipping 20 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.r42VbgPIn/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  7 00:23:42.760: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-5csrs" in namespace "snapshotting-5071" to be "Succeeded or Failed"
Jun  7 00:23:42.824: INFO: Pod "pvc-snapshottable-data-tester-5csrs": Phase="Pending", Reason="", readiness=false. Elapsed: 64.28351ms
Jun  7 00:23:44.886: INFO: Pod "pvc-snapshottable-data-tester-5csrs": Phase="Pending", Reason="", readiness=false. Elapsed: 2.126014132s
Jun  7 00:23:46.948: INFO: Pod "pvc-snapshottable-data-tester-5csrs": Phase="Pending", Reason="", readiness=false. Elapsed: 4.188150664s
Jun  7 00:23:49.010: INFO: Pod "pvc-snapshottable-data-tester-5csrs": Phase="Pending", Reason="", readiness=false. Elapsed: 6.249676754s
Jun  7 00:23:51.073: INFO: Pod "pvc-snapshottable-data-tester-5csrs": Phase="Pending", Reason="", readiness=false. Elapsed: 8.313134921s
Jun  7 00:23:53.135: INFO: Pod "pvc-snapshottable-data-tester-5csrs": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.374594474s
STEP: Saw pod success
Jun  7 00:23:53.135: INFO: Pod "pvc-snapshottable-data-tester-5csrs" satisfied condition "Succeeded or Failed"
Jun  7 00:23:53.259: INFO: Pod pvc-snapshottable-data-tester-5csrs has the following logs: 
Jun  7 00:23:53.259: INFO: Deleting pod "pvc-snapshottable-data-tester-5csrs" in namespace "snapshotting-5071"
Jun  7 00:23:53.326: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-5csrs" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun  7 00:24:07.638: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-5071 exec restored-pvc-tester-wjj4t --namespace=snapshotting-5071 -- cat /mnt/test/data'
... skipping 248 lines ...
    /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:108
      
      /tmp/kops.r42VbgPIn/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.r42VbgPIn/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-5071 exec restored-pvc-tester-wjj4t --namespace=snapshotting-5071 -- 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-5071 exec restored-pvc-tester-wjj4t --namespace=snapshotting-5071 -- 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.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:602
------------------------------
[BeforeEach] [Testpattern: Inline-volume (ext3)] volumes
... skipping 125 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  7 00:24:06.101: 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.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun  7 00:24:06.403: INFO: Creating resource for dynamic PV
Jun  7 00:24:06.403: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8557-e2e-scq2dkq
STEP: creating a claim
Jun  7 00:24:06.466: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-8n88
STEP: Checking for subpath error in container status
Jun  7 00:24:30.775: INFO: Deleting pod "pod-subpath-test-dynamicpv-8n88" in namespace "provisioning-8557"
Jun  7 00:24:30.839: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-8n88" to be fully deleted
STEP: Deleting pod
Jun  7 00:24:40.966: INFO: Deleting pod "pod-subpath-test-dynamicpv-8n88" in namespace "provisioning-8557"
STEP: Deleting pvc
Jun  7 00:24:41.148: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.commmkrb"
... skipping 15 lines ...

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 59 lines ...
Jun  7 00:24:47.968: INFO: Creating resource for dynamic PV
Jun  7 00:24:47.968: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-867hgwlk
STEP: creating a claim
STEP: Expanding non-expandable pvc
Jun  7 00:24:48.169: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun  7 00:24:48.298: INFO: Error updating pvc aws9l7p4: PersistentVolumeClaim "aws9l7p4" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-867hgwlk",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun  7 00:25:18.556: INFO: Error updating pvc aws9l7p4: PersistentVolumeClaim "aws9l7p4" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 231 lines ...
Jun  7 00:24:27.880: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5725-e2e-sc5zjc2
STEP: creating a claim
Jun  7 00:24:27.941: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-smfd
STEP: Creating a pod to test multi_subpath
Jun  7 00:24:28.121: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-smfd" in namespace "provisioning-5725" to be "Succeeded or Failed"
Jun  7 00:24:28.180: INFO: Pod "pod-subpath-test-dynamicpv-smfd": Phase="Pending", Reason="", readiness=false. Elapsed: 58.745907ms
Jun  7 00:24:30.244: INFO: Pod "pod-subpath-test-dynamicpv-smfd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.123062181s
Jun  7 00:24:32.311: INFO: Pod "pod-subpath-test-dynamicpv-smfd": Phase="Pending", Reason="", readiness=false. Elapsed: 4.189720379s
Jun  7 00:24:34.371: INFO: Pod "pod-subpath-test-dynamicpv-smfd": Phase="Pending", Reason="", readiness=false. Elapsed: 6.249236913s
Jun  7 00:24:36.430: INFO: Pod "pod-subpath-test-dynamicpv-smfd": Phase="Pending", Reason="", readiness=false. Elapsed: 8.308400531s
Jun  7 00:24:38.489: INFO: Pod "pod-subpath-test-dynamicpv-smfd": Phase="Pending", Reason="", readiness=false. Elapsed: 10.367945164s
Jun  7 00:24:40.551: INFO: Pod "pod-subpath-test-dynamicpv-smfd": Phase="Pending", Reason="", readiness=false. Elapsed: 12.429824513s
Jun  7 00:24:42.610: INFO: Pod "pod-subpath-test-dynamicpv-smfd": Phase="Pending", Reason="", readiness=false. Elapsed: 14.488818282s
Jun  7 00:24:44.670: INFO: Pod "pod-subpath-test-dynamicpv-smfd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.549054468s
STEP: Saw pod success
Jun  7 00:24:44.670: INFO: Pod "pod-subpath-test-dynamicpv-smfd" satisfied condition "Succeeded or Failed"
Jun  7 00:24:44.729: INFO: Trying to get logs from node ip-172-20-63-204.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-smfd container test-container-subpath-dynamicpv-smfd: <nil>
STEP: delete the pod
Jun  7 00:24:44.856: INFO: Waiting for pod pod-subpath-test-dynamicpv-smfd to disappear
Jun  7 00:24:44.914: INFO: Pod pod-subpath-test-dynamicpv-smfd no longer exists
STEP: Deleting pod
Jun  7 00:24:44.914: INFO: Deleting pod "pod-subpath-test-dynamicpv-smfd" in namespace "provisioning-5725"
... skipping 446 lines ...
Jun  7 00:25:11.306: INFO: Waiting for pod aws-client to disappear
Jun  7 00:25:11.373: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun  7 00:25:11.373: INFO: Deleting PersistentVolumeClaim "pvc-9bq7v"
Jun  7 00:25:11.438: INFO: Deleting PersistentVolume "aws-cknvt"
Jun  7 00:25:11.907: INFO: Couldn't delete PD "aws://us-west-2a/vol-005059bc0a8d224ad", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-005059bc0a8d224ad is currently attached to i-0335d6a9c2531bdc9
	status code: 400, request id: da4bb096-055e-4cce-b9a8-af091a22462c
Jun  7 00:25:17.319: INFO: Couldn't delete PD "aws://us-west-2a/vol-005059bc0a8d224ad", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-005059bc0a8d224ad is currently attached to i-0335d6a9c2531bdc9
	status code: 400, request id: ca5f6321-ac1d-4deb-b84f-fef1f98f8b41
Jun  7 00:25:23.009: INFO: Successfully deleted PD "aws://us-west-2a/vol-005059bc0a8d224ad".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  7 00:25:23.009: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8341" for this suite.
... skipping 340 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  7 00:25:20.680: 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.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  7 00:25:20.995: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  7 00:25:21.627: INFO: Successfully created a new PD: "aws://us-west-2a/vol-0a2727f62110687e6".
Jun  7 00:25:21.627: INFO: Creating resource for pre-provisioned PV
Jun  7 00:25:21.627: INFO: Creating PVC and PV
... skipping 2 lines ...
Jun  7 00:25:21.841: INFO: Waiting up to timeout=3m0s for PersistentVolumeClaims [pvc-x7vz7] to have phase Bound
Jun  7 00:25:21.914: INFO: PersistentVolumeClaim pvc-x7vz7 found but phase is Pending instead of Bound.
Jun  7 00:25:23.977: INFO: PersistentVolumeClaim pvc-x7vz7 found and phase=Bound (2.136009731s)
Jun  7 00:25:23.977: INFO: Waiting up to 3m0s for PersistentVolume aws-dh2qq to have phase Bound
Jun  7 00:25:24.039: INFO: PersistentVolume aws-dh2qq found and phase=Bound (61.890955ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  7 00:25:26.413: INFO: Deleting pod "pod-c441e4a7-51c2-476e-8f31-192276370270" in namespace "volumemode-9551"
Jun  7 00:25:26.479: INFO: Wait up to 5m0s for pod "pod-c441e4a7-51c2-476e-8f31-192276370270" to be fully deleted
STEP: Deleting pv and pvc
Jun  7 00:25:30.604: INFO: Deleting PersistentVolumeClaim "pvc-x7vz7"
Jun  7 00:25:30.680: INFO: Deleting PersistentVolume "aws-dh2qq"
Jun  7 00:25:30.932: INFO: Couldn't delete PD "aws://us-west-2a/vol-0a2727f62110687e6", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a2727f62110687e6 is currently attached to i-0335d6a9c2531bdc9
	status code: 400, request id: 4d08e677-669a-49b9-bc77-0ff873066a83
Jun  7 00:25:36.378: INFO: Successfully deleted PD "aws://us-west-2a/vol-0a2727f62110687e6".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  7 00:25:36.378: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-9551" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.r42VbgPIn/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.r42VbgPIn/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
    /tmp/kops.r42VbgPIn/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.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  7 00:25:36.509: INFO: Driver "ebs.csi.aws.com" does not support volume type "InlineVolume" - skipping
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
... skipping 253 lines ...
Jun  7 00:24:29.671: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-25208d8wz
STEP: creating a claim
Jun  7 00:24:29.735: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-rkdr
STEP: Creating a pod to test subpath
Jun  7 00:24:29.928: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-rkdr" in namespace "provisioning-2520" to be "Succeeded or Failed"
Jun  7 00:24:29.991: INFO: Pod "pod-subpath-test-dynamicpv-rkdr": Phase="Pending", Reason="", readiness=false. Elapsed: 62.939593ms
Jun  7 00:24:32.055: INFO: Pod "pod-subpath-test-dynamicpv-rkdr": Phase="Pending", Reason="", readiness=false. Elapsed: 2.126496478s
Jun  7 00:24:34.118: INFO: Pod "pod-subpath-test-dynamicpv-rkdr": Phase="Pending", Reason="", readiness=false. Elapsed: 4.189631644s
Jun  7 00:24:36.182: INFO: Pod "pod-subpath-test-dynamicpv-rkdr": Phase="Pending", Reason="", readiness=false. Elapsed: 6.253821209s
Jun  7 00:24:38.251: INFO: Pod "pod-subpath-test-dynamicpv-rkdr": Phase="Pending", Reason="", readiness=false. Elapsed: 8.322226066s
Jun  7 00:24:40.315: INFO: Pod "pod-subpath-test-dynamicpv-rkdr": Phase="Pending", Reason="", readiness=false. Elapsed: 10.386306203s
... skipping 2 lines ...
Jun  7 00:24:46.505: INFO: Pod "pod-subpath-test-dynamicpv-rkdr": Phase="Pending", Reason="", readiness=false. Elapsed: 16.57694154s
Jun  7 00:24:48.569: INFO: Pod "pod-subpath-test-dynamicpv-rkdr": Phase="Pending", Reason="", readiness=false. Elapsed: 18.64074698s
Jun  7 00:24:50.647: INFO: Pod "pod-subpath-test-dynamicpv-rkdr": Phase="Pending", Reason="", readiness=false. Elapsed: 20.718986842s
Jun  7 00:24:52.711: INFO: Pod "pod-subpath-test-dynamicpv-rkdr": Phase="Pending", Reason="", readiness=false. Elapsed: 22.782826571s
Jun  7 00:24:54.777: INFO: Pod "pod-subpath-test-dynamicpv-rkdr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.848750798s
STEP: Saw pod success
Jun  7 00:24:54.777: INFO: Pod "pod-subpath-test-dynamicpv-rkdr" satisfied condition "Succeeded or Failed"
Jun  7 00:24:54.840: INFO: Trying to get logs from node ip-172-20-63-224.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-rkdr container test-container-volume-dynamicpv-rkdr: <nil>
STEP: delete the pod
Jun  7 00:24:54.977: INFO: Waiting for pod pod-subpath-test-dynamicpv-rkdr to disappear
Jun  7 00:24:55.040: INFO: Pod pod-subpath-test-dynamicpv-rkdr no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-rkdr
Jun  7 00:24:55.040: INFO: Deleting pod "pod-subpath-test-dynamicpv-rkdr" in namespace "provisioning-2520"
... skipping 42 lines ...
Jun  7 00:24:51.973: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  7 00:24:52.547: INFO: Successfully created a new PD: "aws://us-west-2a/vol-00decc88ec29c5f01".
Jun  7 00:24:52.548: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-wjbs
STEP: Creating a pod to test exec-volume-test
Jun  7 00:24:52.612: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-wjbs" in namespace "volume-9320" to be "Succeeded or Failed"
Jun  7 00:24:52.673: INFO: Pod "exec-volume-test-inlinevolume-wjbs": Phase="Pending", Reason="", readiness=false. Elapsed: 60.845351ms
Jun  7 00:24:54.735: INFO: Pod "exec-volume-test-inlinevolume-wjbs": Phase="Pending", Reason="", readiness=false. Elapsed: 2.123274181s
Jun  7 00:24:56.796: INFO: Pod "exec-volume-test-inlinevolume-wjbs": Phase="Pending", Reason="", readiness=false. Elapsed: 4.184709518s
Jun  7 00:24:58.858: INFO: Pod "exec-volume-test-inlinevolume-wjbs": Phase="Pending", Reason="", readiness=false. Elapsed: 6.246002336s
Jun  7 00:25:00.924: INFO: Pod "exec-volume-test-inlinevolume-wjbs": Phase="Pending", Reason="", readiness=false. Elapsed: 8.312018979s
Jun  7 00:25:02.986: INFO: Pod "exec-volume-test-inlinevolume-wjbs": Phase="Pending", Reason="", readiness=false. Elapsed: 10.374676717s
... skipping 7 lines ...
Jun  7 00:25:19.492: INFO: Pod "exec-volume-test-inlinevolume-wjbs": Phase="Pending", Reason="", readiness=false. Elapsed: 26.87997579s
Jun  7 00:25:21.553: INFO: Pod "exec-volume-test-inlinevolume-wjbs": Phase="Pending", Reason="", readiness=false. Elapsed: 28.941780451s
Jun  7 00:25:23.614: INFO: Pod "exec-volume-test-inlinevolume-wjbs": Phase="Pending", Reason="", readiness=false. Elapsed: 31.002798403s
Jun  7 00:25:25.680: INFO: Pod "exec-volume-test-inlinevolume-wjbs": Phase="Pending", Reason="", readiness=false. Elapsed: 33.0681018s
Jun  7 00:25:27.741: INFO: Pod "exec-volume-test-inlinevolume-wjbs": Phase="Succeeded", Reason="", readiness=false. Elapsed: 35.129592819s
STEP: Saw pod success
Jun  7 00:25:27.741: INFO: Pod "exec-volume-test-inlinevolume-wjbs" satisfied condition "Succeeded or Failed"
Jun  7 00:25:27.802: INFO: Trying to get logs from node ip-172-20-38-247.us-west-2.compute.internal pod exec-volume-test-inlinevolume-wjbs container exec-container-inlinevolume-wjbs: <nil>
STEP: delete the pod
Jun  7 00:25:27.963: INFO: Waiting for pod exec-volume-test-inlinevolume-wjbs to disappear
Jun  7 00:25:28.024: INFO: Pod exec-volume-test-inlinevolume-wjbs no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-wjbs
Jun  7 00:25:28.024: INFO: Deleting pod "exec-volume-test-inlinevolume-wjbs" in namespace "volume-9320"
Jun  7 00:25:28.287: INFO: Couldn't delete PD "aws://us-west-2a/vol-00decc88ec29c5f01", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00decc88ec29c5f01 is currently attached to i-0b83558ad417b9266
	status code: 400, request id: bd8d2f9f-e3ee-46da-bd1c-9967c1d7c120
Jun  7 00:25:33.714: INFO: Couldn't delete PD "aws://us-west-2a/vol-00decc88ec29c5f01", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00decc88ec29c5f01 is currently attached to i-0b83558ad417b9266
	status code: 400, request id: 8599841d-47d8-41d5-90ba-b04c06c3da62
Jun  7 00:25:39.112: INFO: Couldn't delete PD "aws://us-west-2a/vol-00decc88ec29c5f01", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00decc88ec29c5f01 is currently attached to i-0b83558ad417b9266
	status code: 400, request id: 0306597c-5d5a-47ff-9394-44c121cb36ce
Jun  7 00:25:44.556: INFO: Successfully deleted PD "aws://us-west-2a/vol-00decc88ec29c5f01".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  7 00:25:44.556: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-9320" for this suite.
... skipping 48 lines ...
STEP: Deleting pod hostexec-ip-172-20-63-224.us-west-2.compute.internal-rv6p8 in namespace volumemode-9471
Jun  7 00:25:15.265: INFO: Deleting pod "pod-bed46976-0379-4300-ad8c-3a251c1b2762" in namespace "volumemode-9471"
Jun  7 00:25:15.332: INFO: Wait up to 5m0s for pod "pod-bed46976-0379-4300-ad8c-3a251c1b2762" to be fully deleted
STEP: Deleting pv and pvc
Jun  7 00:25:25.456: INFO: Deleting PersistentVolumeClaim "pvc-jgk62"
Jun  7 00:25:25.520: INFO: Deleting PersistentVolume "aws-f8rcb"
Jun  7 00:25:25.764: INFO: Couldn't delete PD "aws://us-west-2a/vol-031ac0c05c5733644", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-031ac0c05c5733644 is currently attached to i-0ec9cfc7096a1018a
	status code: 400, request id: 0ced0479-1eb5-49f5-86e9-e7d4f9fb6b3c
Jun  7 00:25:31.213: INFO: Couldn't delete PD "aws://us-west-2a/vol-031ac0c05c5733644", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-031ac0c05c5733644 is currently attached to i-0ec9cfc7096a1018a
	status code: 400, request id: 8c203486-dc5a-402c-9190-8807da63fa61
Jun  7 00:25:36.683: INFO: Couldn't delete PD "aws://us-west-2a/vol-031ac0c05c5733644", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-031ac0c05c5733644 is currently attached to i-0ec9cfc7096a1018a
	status code: 400, request id: 6baef12a-b8f7-44c3-90df-c8ac22848030
Jun  7 00:25:42.107: INFO: Couldn't delete PD "aws://us-west-2a/vol-031ac0c05c5733644", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-031ac0c05c5733644 is currently attached to i-0ec9cfc7096a1018a
	status code: 400, request id: 3c2b8c20-632c-4dde-a671-fb076f7b7a78
Jun  7 00:25:47.514: INFO: Successfully deleted PD "aws://us-west-2a/vol-031ac0c05c5733644".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  7 00:25:47.514: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-9471" for this suite.
... skipping 14 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  7 00:24:58.826: 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.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  7 00:24:59.143: INFO: Creating resource for dynamic PV
Jun  7 00:24:59.143: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-9170-e2e-sc48btv
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  7 00:25:05.595: INFO: Deleting pod "pod-40793920-8dd9-49a8-93e1-4acbc7acb835" in namespace "volumemode-9170"
Jun  7 00:25:05.658: INFO: Wait up to 5m0s for pod "pod-40793920-8dd9-49a8-93e1-4acbc7acb835" to be fully deleted
STEP: Deleting pvc
Jun  7 00:25:13.907: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comwvgj4"
Jun  7 00:25:13.973: INFO: Waiting up to 5m0s for PersistentVolume pvc-21c91571-d6ee-4c3d-94a0-12e549f2e5da to get deleted
Jun  7 00:25:14.036: INFO: PersistentVolume pvc-21c91571-d6ee-4c3d-94a0-12e549f2e5da found and phase=Released (62.631344ms)
... skipping 13 lines ...

• [SLOW TEST:50.839 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.r42VbgPIn/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.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 8 lines ...
Jun  7 00:24:48.829: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1092gq69z
STEP: creating a claim
Jun  7 00:24:48.891: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-zm6c
STEP: Creating a pod to test subpath
Jun  7 00:24:49.076: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-zm6c" in namespace "provisioning-1092" to be "Succeeded or Failed"
Jun  7 00:24:49.138: INFO: Pod "pod-subpath-test-dynamicpv-zm6c": Phase="Pending", Reason="", readiness=false. Elapsed: 61.134912ms
Jun  7 00:24:51.199: INFO: Pod "pod-subpath-test-dynamicpv-zm6c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.122571643s
Jun  7 00:24:53.266: INFO: Pod "pod-subpath-test-dynamicpv-zm6c": Phase="Pending", Reason="", readiness=false. Elapsed: 4.189362757s
Jun  7 00:24:55.329: INFO: Pod "pod-subpath-test-dynamicpv-zm6c": Phase="Pending", Reason="", readiness=false. Elapsed: 6.25254634s
Jun  7 00:24:57.390: INFO: Pod "pod-subpath-test-dynamicpv-zm6c": Phase="Pending", Reason="", readiness=false. Elapsed: 8.313819861s
Jun  7 00:24:59.453: INFO: Pod "pod-subpath-test-dynamicpv-zm6c": Phase="Pending", Reason="", readiness=false. Elapsed: 10.376574392s
... skipping 9 lines ...
Jun  7 00:25:20.073: INFO: Pod "pod-subpath-test-dynamicpv-zm6c": Phase="Pending", Reason="", readiness=false. Elapsed: 30.996439444s
Jun  7 00:25:22.134: INFO: Pod "pod-subpath-test-dynamicpv-zm6c": Phase="Pending", Reason="", readiness=false. Elapsed: 33.057198459s
Jun  7 00:25:24.197: INFO: Pod "pod-subpath-test-dynamicpv-zm6c": Phase="Pending", Reason="", readiness=false. Elapsed: 35.120860429s
Jun  7 00:25:26.258: INFO: Pod "pod-subpath-test-dynamicpv-zm6c": Phase="Pending", Reason="", readiness=false. Elapsed: 37.18167565s
Jun  7 00:25:28.333: INFO: Pod "pod-subpath-test-dynamicpv-zm6c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 39.256312362s
STEP: Saw pod success
Jun  7 00:25:28.333: INFO: Pod "pod-subpath-test-dynamicpv-zm6c" satisfied condition "Succeeded or Failed"
Jun  7 00:25:28.399: INFO: Trying to get logs from node ip-172-20-63-204.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-zm6c container test-container-volume-dynamicpv-zm6c: <nil>
STEP: delete the pod
Jun  7 00:25:28.543: INFO: Waiting for pod pod-subpath-test-dynamicpv-zm6c to disappear
Jun  7 00:25:28.608: INFO: Pod pod-subpath-test-dynamicpv-zm6c no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-zm6c
Jun  7 00:25:28.609: INFO: Deleting pod "pod-subpath-test-dynamicpv-zm6c" in namespace "provisioning-1092"
... skipping 39 lines ...
Jun  7 00:24:56.471: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7810-e2e-scbscrm
STEP: creating a claim
Jun  7 00:24:56.535: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-szfx
STEP: Creating a pod to test subpath
Jun  7 00:24:56.737: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-szfx" in namespace "provisioning-7810" to be "Succeeded or Failed"
Jun  7 00:24:56.801: INFO: Pod "pod-subpath-test-dynamicpv-szfx": Phase="Pending", Reason="", readiness=false. Elapsed: 63.712121ms
Jun  7 00:24:58.865: INFO: Pod "pod-subpath-test-dynamicpv-szfx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.127124459s
Jun  7 00:25:00.928: INFO: Pod "pod-subpath-test-dynamicpv-szfx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.190717368s
Jun  7 00:25:02.991: INFO: Pod "pod-subpath-test-dynamicpv-szfx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.253926908s
Jun  7 00:25:05.055: INFO: Pod "pod-subpath-test-dynamicpv-szfx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.317205869s
Jun  7 00:25:07.117: INFO: Pod "pod-subpath-test-dynamicpv-szfx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.379612525s
Jun  7 00:25:09.183: INFO: Pod "pod-subpath-test-dynamicpv-szfx": Phase="Pending", Reason="", readiness=false. Elapsed: 12.445430777s
Jun  7 00:25:11.246: INFO: Pod "pod-subpath-test-dynamicpv-szfx": Phase="Pending", Reason="", readiness=false. Elapsed: 14.508244619s
Jun  7 00:25:13.308: INFO: Pod "pod-subpath-test-dynamicpv-szfx": Phase="Pending", Reason="", readiness=false. Elapsed: 16.570666324s
Jun  7 00:25:15.371: INFO: Pod "pod-subpath-test-dynamicpv-szfx": Phase="Pending", Reason="", readiness=false. Elapsed: 18.633900192s
Jun  7 00:25:17.435: INFO: Pod "pod-subpath-test-dynamicpv-szfx": Phase="Pending", Reason="", readiness=false. Elapsed: 20.697080332s
Jun  7 00:25:19.497: INFO: Pod "pod-subpath-test-dynamicpv-szfx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.759337485s
STEP: Saw pod success
Jun  7 00:25:19.497: INFO: Pod "pod-subpath-test-dynamicpv-szfx" satisfied condition "Succeeded or Failed"
Jun  7 00:25:19.559: INFO: Trying to get logs from node ip-172-20-40-22.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-szfx container test-container-volume-dynamicpv-szfx: <nil>
STEP: delete the pod
Jun  7 00:25:19.695: INFO: Waiting for pod pod-subpath-test-dynamicpv-szfx to disappear
Jun  7 00:25:19.758: INFO: Pod pod-subpath-test-dynamicpv-szfx no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-szfx
Jun  7 00:25:19.758: INFO: Deleting pod "pod-subpath-test-dynamicpv-szfx" in namespace "provisioning-7810"
... skipping 41 lines ...
Jun  7 00:24:10.317: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-4291k7dv2      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-4291    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-4291k7dv2,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-4291    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-4291k7dv2,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-4291    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-4291k7dv2,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-4291k7dv2    45255f0d-ef8c-43be-b52c-ac56742cea90 11741 0 2021-06-07 00:24:10 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-07 00:24:10 +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-n7lsv pvc- provisioning-4291  f3ce138a-6b31-4db9-a6d6-1644f4281410 11750 0 2021-06-07 00:24:10 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-07 00:24:10 +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-4291k7dv2,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-d684fdca-56f2-4c9d-a3ad-531fd0601da7 in namespace provisioning-4291
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun  7 00:24:33.061: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-vns26" in namespace "provisioning-4291" to be "Succeeded or Failed"
Jun  7 00:24:33.124: INFO: Pod "pvc-volume-tester-writer-vns26": Phase="Pending", Reason="", readiness=false. Elapsed: 63.676781ms
Jun  7 00:24:35.189: INFO: Pod "pvc-volume-tester-writer-vns26": Phase="Pending", Reason="", readiness=false. Elapsed: 2.128777531s
Jun  7 00:24:37.253: INFO: Pod "pvc-volume-tester-writer-vns26": Phase="Pending", Reason="", readiness=false. Elapsed: 4.19281429s
Jun  7 00:24:39.317: INFO: Pod "pvc-volume-tester-writer-vns26": Phase="Pending", Reason="", readiness=false. Elapsed: 6.256789207s
Jun  7 00:24:41.382: INFO: Pod "pvc-volume-tester-writer-vns26": Phase="Pending", Reason="", readiness=false. Elapsed: 8.321748359s
Jun  7 00:24:43.447: INFO: Pod "pvc-volume-tester-writer-vns26": Phase="Pending", Reason="", readiness=false. Elapsed: 10.386487084s
... skipping 22 lines ...
Jun  7 00:25:30.943: INFO: Pod "pvc-volume-tester-writer-vns26": Phase="Pending", Reason="", readiness=false. Elapsed: 57.881851176s
Jun  7 00:25:33.008: INFO: Pod "pvc-volume-tester-writer-vns26": Phase="Pending", Reason="", readiness=false. Elapsed: 59.947235009s
Jun  7 00:25:35.072: INFO: Pod "pvc-volume-tester-writer-vns26": Phase="Pending", Reason="", readiness=false. Elapsed: 1m2.011687239s
Jun  7 00:25:37.137: INFO: Pod "pvc-volume-tester-writer-vns26": Phase="Pending", Reason="", readiness=false. Elapsed: 1m4.076734176s
Jun  7 00:25:39.202: INFO: Pod "pvc-volume-tester-writer-vns26": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m6.141054115s
STEP: Saw pod success
Jun  7 00:25:39.202: INFO: Pod "pvc-volume-tester-writer-vns26" satisfied condition "Succeeded or Failed"
Jun  7 00:25:39.332: INFO: Pod pvc-volume-tester-writer-vns26 has the following logs: 
Jun  7 00:25:39.332: INFO: Deleting pod "pvc-volume-tester-writer-vns26" in namespace "provisioning-4291"
Jun  7 00:25:39.404: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-vns26" 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-63-204.us-west-2.compute.internal"
Jun  7 00:25:39.663: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-hwbgk" in namespace "provisioning-4291" to be "Succeeded or Failed"
Jun  7 00:25:39.733: INFO: Pod "pvc-volume-tester-reader-hwbgk": Phase="Pending", Reason="", readiness=false. Elapsed: 70.518763ms
Jun  7 00:25:41.798: INFO: Pod "pvc-volume-tester-reader-hwbgk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.135269033s
STEP: Saw pod success
Jun  7 00:25:41.798: INFO: Pod "pvc-volume-tester-reader-hwbgk" satisfied condition "Succeeded or Failed"
Jun  7 00:25:41.933: INFO: Pod pvc-volume-tester-reader-hwbgk has the following logs: hello world

Jun  7 00:25:41.933: INFO: Deleting pod "pvc-volume-tester-reader-hwbgk" in namespace "provisioning-4291"
Jun  7 00:25:42.002: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-hwbgk" to be fully deleted
Jun  7 00:25:42.065: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-n7lsv] to have phase Bound
Jun  7 00:25:42.129: INFO: PersistentVolumeClaim pvc-n7lsv found and phase=Bound (63.324338ms)
... skipping 261 lines ...
Jun  7 00:25:24.070: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1026-e2e-scmrn9r
STEP: creating a claim
Jun  7 00:25:24.132: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-2mdc
STEP: Creating a pod to test subpath
Jun  7 00:25:24.313: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-2mdc" in namespace "provisioning-1026" to be "Succeeded or Failed"
Jun  7 00:25:24.373: INFO: Pod "pod-subpath-test-dynamicpv-2mdc": Phase="Pending", Reason="", readiness=false. Elapsed: 59.537454ms
Jun  7 00:25:26.433: INFO: Pod "pod-subpath-test-dynamicpv-2mdc": Phase="Pending", Reason="", readiness=false. Elapsed: 2.120077994s
Jun  7 00:25:28.498: INFO: Pod "pod-subpath-test-dynamicpv-2mdc": Phase="Pending", Reason="", readiness=false. Elapsed: 4.184654599s
Jun  7 00:25:30.559: INFO: Pod "pod-subpath-test-dynamicpv-2mdc": Phase="Pending", Reason="", readiness=false. Elapsed: 6.245950515s
Jun  7 00:25:32.620: INFO: Pod "pod-subpath-test-dynamicpv-2mdc": Phase="Pending", Reason="", readiness=false. Elapsed: 8.306391552s
Jun  7 00:25:34.680: INFO: Pod "pod-subpath-test-dynamicpv-2mdc": Phase="Pending", Reason="", readiness=false. Elapsed: 10.366924911s
Jun  7 00:25:36.741: INFO: Pod "pod-subpath-test-dynamicpv-2mdc": Phase="Pending", Reason="", readiness=false. Elapsed: 12.427687796s
Jun  7 00:25:38.803: INFO: Pod "pod-subpath-test-dynamicpv-2mdc": Phase="Pending", Reason="", readiness=false. Elapsed: 14.489162981s
Jun  7 00:25:40.867: INFO: Pod "pod-subpath-test-dynamicpv-2mdc": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.553975128s
STEP: Saw pod success
Jun  7 00:25:40.867: INFO: Pod "pod-subpath-test-dynamicpv-2mdc" satisfied condition "Succeeded or Failed"
Jun  7 00:25:40.935: INFO: Trying to get logs from node ip-172-20-38-247.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-2mdc container test-container-volume-dynamicpv-2mdc: <nil>
STEP: delete the pod
Jun  7 00:25:41.061: INFO: Waiting for pod pod-subpath-test-dynamicpv-2mdc to disappear
Jun  7 00:25:41.121: INFO: Pod pod-subpath-test-dynamicpv-2mdc no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-2mdc
Jun  7 00:25:41.122: INFO: Deleting pod "pod-subpath-test-dynamicpv-2mdc" in namespace "provisioning-1026"
... skipping 39 lines ...
Jun  7 00:24:59.513: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6813-e2e-sc7tjjs
STEP: creating a claim
Jun  7 00:24:59.576: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-fzvh
STEP: Creating a pod to test atomic-volume-subpath
Jun  7 00:24:59.767: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-fzvh" in namespace "provisioning-6813" to be "Succeeded or Failed"
Jun  7 00:24:59.828: INFO: Pod "pod-subpath-test-dynamicpv-fzvh": Phase="Pending", Reason="", readiness=false. Elapsed: 61.547506ms
Jun  7 00:25:01.890: INFO: Pod "pod-subpath-test-dynamicpv-fzvh": Phase="Pending", Reason="", readiness=false. Elapsed: 2.122661917s
Jun  7 00:25:03.951: INFO: Pod "pod-subpath-test-dynamicpv-fzvh": Phase="Pending", Reason="", readiness=false. Elapsed: 4.183582042s
Jun  7 00:25:06.012: INFO: Pod "pod-subpath-test-dynamicpv-fzvh": Phase="Pending", Reason="", readiness=false. Elapsed: 6.245283674s
Jun  7 00:25:08.074: INFO: Pod "pod-subpath-test-dynamicpv-fzvh": Phase="Pending", Reason="", readiness=false. Elapsed: 8.30658956s
Jun  7 00:25:10.135: INFO: Pod "pod-subpath-test-dynamicpv-fzvh": Phase="Pending", Reason="", readiness=false. Elapsed: 10.367722759s
... skipping 11 lines ...
Jun  7 00:25:34.882: INFO: Pod "pod-subpath-test-dynamicpv-fzvh": Phase="Running", Reason="", readiness=true. Elapsed: 35.115139685s
Jun  7 00:25:36.947: INFO: Pod "pod-subpath-test-dynamicpv-fzvh": Phase="Running", Reason="", readiness=true. Elapsed: 37.179901158s
Jun  7 00:25:39.009: INFO: Pod "pod-subpath-test-dynamicpv-fzvh": Phase="Running", Reason="", readiness=true. Elapsed: 39.242452876s
Jun  7 00:25:41.076: INFO: Pod "pod-subpath-test-dynamicpv-fzvh": Phase="Running", Reason="", readiness=true. Elapsed: 41.309096224s
Jun  7 00:25:43.139: INFO: Pod "pod-subpath-test-dynamicpv-fzvh": Phase="Succeeded", Reason="", readiness=false. Elapsed: 43.371607897s
STEP: Saw pod success
Jun  7 00:25:43.139: INFO: Pod "pod-subpath-test-dynamicpv-fzvh" satisfied condition "Succeeded or Failed"
Jun  7 00:25:43.203: INFO: Trying to get logs from node ip-172-20-38-247.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-fzvh container test-container-subpath-dynamicpv-fzvh: <nil>
STEP: delete the pod
Jun  7 00:25:43.343: INFO: Waiting for pod pod-subpath-test-dynamicpv-fzvh to disappear
Jun  7 00:25:43.404: INFO: Pod pod-subpath-test-dynamicpv-fzvh no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-fzvh
Jun  7 00:25:43.404: INFO: Deleting pod "pod-subpath-test-dynamicpv-fzvh" in namespace "provisioning-6813"
... skipping 93 lines ...
Jun  7 00:25:21.112: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-6244-e2e-sc6nwc9
STEP: creating a claim
Jun  7 00:25:21.172: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-2bdn
STEP: Creating a pod to test exec-volume-test
Jun  7 00:25:21.352: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-2bdn" in namespace "volume-6244" to be "Succeeded or Failed"
Jun  7 00:25:21.411: INFO: Pod "exec-volume-test-dynamicpv-2bdn": Phase="Pending", Reason="", readiness=false. Elapsed: 58.541178ms
Jun  7 00:25:23.471: INFO: Pod "exec-volume-test-dynamicpv-2bdn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.119472832s
Jun  7 00:25:25.532: INFO: Pod "exec-volume-test-dynamicpv-2bdn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.179521064s
Jun  7 00:25:27.594: INFO: Pod "exec-volume-test-dynamicpv-2bdn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.242427396s
Jun  7 00:25:29.656: INFO: Pod "exec-volume-test-dynamicpv-2bdn": Phase="Pending", Reason="", readiness=false. Elapsed: 8.303557174s
Jun  7 00:25:31.718: INFO: Pod "exec-volume-test-dynamicpv-2bdn": Phase="Pending", Reason="", readiness=false. Elapsed: 10.36555224s
... skipping 9 lines ...
Jun  7 00:25:52.321: INFO: Pod "exec-volume-test-dynamicpv-2bdn": Phase="Pending", Reason="", readiness=false. Elapsed: 30.969173571s
Jun  7 00:25:54.380: INFO: Pod "exec-volume-test-dynamicpv-2bdn": Phase="Pending", Reason="", readiness=false. Elapsed: 33.028060122s
Jun  7 00:25:56.439: INFO: Pod "exec-volume-test-dynamicpv-2bdn": Phase="Pending", Reason="", readiness=false. Elapsed: 35.086901314s
Jun  7 00:25:58.498: INFO: Pod "exec-volume-test-dynamicpv-2bdn": Phase="Pending", Reason="", readiness=false. Elapsed: 37.146440911s
Jun  7 00:26:00.559: INFO: Pod "exec-volume-test-dynamicpv-2bdn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 39.207338112s
STEP: Saw pod success
Jun  7 00:26:00.559: INFO: Pod "exec-volume-test-dynamicpv-2bdn" satisfied condition "Succeeded or Failed"
Jun  7 00:26:00.618: INFO: Trying to get logs from node ip-172-20-63-224.us-west-2.compute.internal pod exec-volume-test-dynamicpv-2bdn container exec-container-dynamicpv-2bdn: <nil>
STEP: delete the pod
Jun  7 00:26:00.746: INFO: Waiting for pod exec-volume-test-dynamicpv-2bdn to disappear
Jun  7 00:26:00.807: INFO: Pod exec-volume-test-dynamicpv-2bdn no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-2bdn
Jun  7 00:26:00.807: INFO: Deleting pod "exec-volume-test-dynamicpv-2bdn" in namespace "volume-6244"
... skipping 641 lines ...
Jun  7 00:27:15.188: INFO: Waiting for pod aws-client to disappear
Jun  7 00:27:15.247: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun  7 00:27:15.247: INFO: Deleting PersistentVolumeClaim "pvc-l4mq2"
Jun  7 00:27:15.306: INFO: Deleting PersistentVolume "aws-snfp9"
Jun  7 00:27:15.753: INFO: Couldn't delete PD "aws://us-west-2a/vol-0656e1863909244d6", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0656e1863909244d6 is currently attached to i-0ec9cfc7096a1018a
	status code: 400, request id: 7305831f-7d6c-455f-b59a-fb206e7ca3b3
Jun  7 00:27:21.166: INFO: Successfully deleted PD "aws://us-west-2a/vol-0656e1863909244d6".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumes
  /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  7 00:27:21.166: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-2296" for this suite.
... skipping 83 lines ...
Jun  7 00:25:24.733: INFO: Creating resource for dynamic PV
Jun  7 00:25:24.733: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-7620-e2e-scczdk7
STEP: creating a claim
Jun  7 00:25:24.796: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun  7 00:25:24.984: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-gx82j" in namespace "snapshotting-7620" to be "Succeeded or Failed"
Jun  7 00:25:25.048: INFO: Pod "pvc-snapshottable-tester-gx82j": Phase="Pending", Reason="", readiness=false. Elapsed: 63.807202ms
Jun  7 00:25:27.112: INFO: Pod "pvc-snapshottable-tester-gx82j": Phase="Pending", Reason="", readiness=false. Elapsed: 2.127393568s
Jun  7 00:25:29.175: INFO: Pod "pvc-snapshottable-tester-gx82j": Phase="Pending", Reason="", readiness=false. Elapsed: 4.190075256s
Jun  7 00:25:31.238: INFO: Pod "pvc-snapshottable-tester-gx82j": Phase="Pending", Reason="", readiness=false. Elapsed: 6.253501476s
Jun  7 00:25:33.301: INFO: Pod "pvc-snapshottable-tester-gx82j": Phase="Pending", Reason="", readiness=false. Elapsed: 8.316160693s
Jun  7 00:25:35.363: INFO: Pod "pvc-snapshottable-tester-gx82j": Phase="Pending", Reason="", readiness=false. Elapsed: 10.378641228s
... skipping 2 lines ...
Jun  7 00:25:41.567: INFO: Pod "pvc-snapshottable-tester-gx82j": Phase="Pending", Reason="", readiness=false. Elapsed: 16.582593436s
Jun  7 00:25:43.630: INFO: Pod "pvc-snapshottable-tester-gx82j": Phase="Pending", Reason="", readiness=false. Elapsed: 18.645676591s
Jun  7 00:25:45.693: INFO: Pod "pvc-snapshottable-tester-gx82j": Phase="Pending", Reason="", readiness=false. Elapsed: 20.70822211s
Jun  7 00:25:47.755: INFO: Pod "pvc-snapshottable-tester-gx82j": Phase="Pending", Reason="", readiness=false. Elapsed: 22.770439436s
Jun  7 00:25:49.822: INFO: Pod "pvc-snapshottable-tester-gx82j": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.837412561s
STEP: Saw pod success
Jun  7 00:25:49.822: INFO: Pod "pvc-snapshottable-tester-gx82j" satisfied condition "Succeeded or Failed"
Jun  7 00:25:49.947: INFO: Pod pvc-snapshottable-tester-gx82j has the following logs: 
Jun  7 00:25:49.947: INFO: Deleting pod "pvc-snapshottable-tester-gx82j" in namespace "snapshotting-7620"
Jun  7 00:25:50.014: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-gx82j" to be fully deleted
Jun  7 00:25:50.076: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.commvfld] to have phase Bound
Jun  7 00:25:50.138: INFO: PersistentVolumeClaim ebs.csi.aws.commvfld found and phase=Bound (61.828097ms)
STEP: [init] checking the claim
... skipping 44 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.r42VbgPIn/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  7 00:26:24.514: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-f6dd2" in namespace "snapshotting-7620" to be "Succeeded or Failed"
Jun  7 00:26:24.577: INFO: Pod "pvc-snapshottable-data-tester-f6dd2": Phase="Pending", Reason="", readiness=false. Elapsed: 62.565514ms
Jun  7 00:26:26.641: INFO: Pod "pvc-snapshottable-data-tester-f6dd2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.126454292s
Jun  7 00:26:28.704: INFO: Pod "pvc-snapshottable-data-tester-f6dd2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.189645912s
Jun  7 00:26:30.767: INFO: Pod "pvc-snapshottable-data-tester-f6dd2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.252597664s
Jun  7 00:26:32.831: INFO: Pod "pvc-snapshottable-data-tester-f6dd2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.316329456s
Jun  7 00:26:34.895: INFO: Pod "pvc-snapshottable-data-tester-f6dd2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.380125537s
STEP: Saw pod success
Jun  7 00:26:34.895: INFO: Pod "pvc-snapshottable-data-tester-f6dd2" satisfied condition "Succeeded or Failed"
Jun  7 00:26:35.021: INFO: Pod pvc-snapshottable-data-tester-f6dd2 has the following logs: 
Jun  7 00:26:35.021: INFO: Deleting pod "pvc-snapshottable-data-tester-f6dd2" in namespace "snapshotting-7620"
Jun  7 00:26:35.090: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-f6dd2" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun  7 00:26:45.403: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-7620 exec restored-pvc-tester-74dnv --namespace=snapshotting-7620 -- cat /mnt/test/data'
... skipping 219 lines ...
    /tmp/kops.r42VbgPIn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/ephemeral.go:173
------------------------------


Summarizing 2 Failures:

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

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

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


Ginkgo ran 1 suite in 10m43.064479191s
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
I0607 00:28:08.330343   30437 app.go:59] RunDir for this run: "/logs/artifacts/939a2107-c723-11eb-a95e-22b332769ebd"
I0607 00:28:08.330538   30437 app.go:90] ID for this run: "939a2107-c723-11eb-a95e-22b332769ebd"
I0607 00:28:08.330569   30437 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
I0607 00:28:08.347596   30443 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
... skipping 1587 lines ...