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

No Test Failures!


Error lines from build-log.txt

... skipping 489 lines ...
I0603 16:04:25.957412   11705 up.go:43] Cleaning up any leaked resources from previous cluster
I0603 16:04:25.957442   11705 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
I0603 16:04:25.973442   11711 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0603 16:04:25.973536   11711 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io" not found
W0603 16:04:26.491164   11705 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0603 16:04:26.491308   11705 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
I0603 16:04:26.508536   11721 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0603 16:04:26.508664   11721 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io" not found
I0603 16:04:27.016671   11705 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/06/03 16:04:27 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
I0603 16:04:27.032835   11705 http.go:37] curl https://ip.jsb.workers.dev
I0603 16:04:27.169134   11705 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.143.117/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones us-west-1a --master-size c5.large
I0603 16:04:27.184817   11737 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0603 16:04:27.184915   11737 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I0603 16:04:27.230878   11737 create_cluster.go:728] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0603 16:04:27.729122   11737 new_cluster.go:1022]  Cloud Provider ID = aws
... skipping 40 lines ...

I0603 16:04:53.223082   11705 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
I0603 16:04:53.239863   11758 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0603 16:04:53.240576   11758 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io

W0603 16:04:54.469292   11758 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-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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
W0603 16:05:04.505976   11758 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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
W0603 16:05:14.545216   11758 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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
W0603 16:05:24.576846   11758 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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
W0603 16:05:34.613289   11758 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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
W0603 16:05:44.676181   11758 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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
W0603 16:05:54.716178   11758 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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
W0603 16:06:04.750831   11758 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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
W0603 16:06:14.788803   11758 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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
W0603 16:06:24.821003   11758 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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
W0603 16:06:34.853272   11758 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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
W0603 16:06:44.885274   11758 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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
W0603 16:06:54.930912   11758 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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
W0603 16:07:04.962431   11758 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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
W0603 16:07:15.008004   11758 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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
W0603 16:07:25.040193   11758 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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
W0603 16:07:35.073808   11758 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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
W0603 16:07:45.132343   11758 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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
W0603 16:07:55.165397   11758 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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
W0603 16:08:05.205485   11758 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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
W0603 16:08:15.240530   11758 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0fa3526e84537dbe0					machine "i-0fa3526e84537dbe0" has not yet joined cluster
Pod	kube-system/calico-kube-controllers-78d6f96c7b-h7sm6	system-cluster-critical pod "calico-kube-controllers-78d6f96c7b-h7sm6" is pending
Pod	kube-system/calico-node-gtzrp				system-node-critical pod "calico-node-gtzrp" is not ready (calico-node)
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-2tqdp		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-2tqdp" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-zj8n4		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-zj8n4" is pending

Validation Failed
W0603 16:08:26.980092   11758 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 8 lines ...
Machine	i-0bc50fa72c0564cf8					machine "i-0bc50fa72c0564cf8" has not yet joined cluster
Machine	i-0fa3526e84537dbe0					machine "i-0fa3526e84537dbe0" has not yet joined cluster
Pod	kube-system/calico-kube-controllers-78d6f96c7b-h7sm6	system-cluster-critical pod "calico-kube-controllers-78d6f96c7b-h7sm6" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-2tqdp		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-2tqdp" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-zj8n4		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-zj8n4" is pending

Validation Failed
W0603 16:08:38.229701   11758 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
KIND	NAME			MESSAGE
Machine	i-05d143d647948db9b	machine "i-05d143d647948db9b" has not yet joined cluster
Machine	i-087802f1a3468fa04	machine "i-087802f1a3468fa04" has not yet joined cluster
Machine	i-0bc50fa72c0564cf8	machine "i-0bc50fa72c0564cf8" has not yet joined cluster
Machine	i-0fa3526e84537dbe0	machine "i-0fa3526e84537dbe0" has not yet joined cluster

Validation Failed
W0603 16:08:49.417211   11758 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 8 lines ...
Machine	i-0bc50fa72c0564cf8				machine "i-0bc50fa72c0564cf8" has not yet joined cluster
Machine	i-0fa3526e84537dbe0				machine "i-0fa3526e84537dbe0" has not yet joined cluster
Pod	kube-system/coredns-autoscaler-6f594f4c58-s82xt	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-s82xt" is pending
Pod	kube-system/coredns-f45c4bf76-998sn		system-cluster-critical pod "coredns-f45c4bf76-998sn" is pending
Pod	kube-system/kops-controller-4dt8j		system-node-critical pod "kops-controller-4dt8j" is pending

Validation Failed
W0603 16:09:00.684300   11758 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 10 lines ...
Pod	kube-system/cert-manager-5d46c5dc5b-rqn77		system-cluster-critical pod "cert-manager-5d46c5dc5b-rqn77" is pending
Pod	kube-system/cert-manager-cainjector-74d69756d5-4h8rx	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-4h8rx" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-pclg6	system-cluster-critical pod "cert-manager-webhook-7bbf67968-pclg6" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-s82xt		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-s82xt" is pending
Pod	kube-system/coredns-f45c4bf76-998sn			system-cluster-critical pod "coredns-f45c4bf76-998sn" is pending

Validation Failed
W0603 16:09:11.878009   11758 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 17 lines ...
Pod	kube-system/coredns-f45c4bf76-998sn					system-cluster-critical pod "coredns-f45c4bf76-998sn" is pending
Pod	kube-system/ebs-csi-node-7blzf						system-node-critical pod "ebs-csi-node-7blzf" is pending
Pod	kube-system/ebs-csi-node-tcp8q						system-node-critical pod "ebs-csi-node-tcp8q" is pending
Pod	kube-system/kube-proxy-ip-172-20-56-152.us-west-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-56-152.us-west-1.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-61-108.us-west-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-61-108.us-west-1.compute.internal" is pending

Validation Failed
W0603 16:09:23.068350   11758 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 23 lines ...
Pod	kube-system/ebs-csi-node-lg54z						system-node-critical pod "ebs-csi-node-lg54z" is pending
Pod	kube-system/ebs-csi-node-nvzjx						system-node-critical pod "ebs-csi-node-nvzjx" is pending
Pod	kube-system/ebs-csi-node-tcp8q						system-node-critical pod "ebs-csi-node-tcp8q" is pending
Pod	kube-system/kube-proxy-ip-172-20-32-159.us-west-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-32-159.us-west-1.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-54-51.us-west-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-54-51.us-west-1.compute.internal" is pending

Validation Failed
W0603 16:09:34.352850   11758 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 17 lines ...
Pod	kube-system/cert-manager-webhook-7bbf67968-pclg6	system-cluster-critical pod "cert-manager-webhook-7bbf67968-pclg6" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-s82xt		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-s82xt" is pending
Pod	kube-system/coredns-f45c4bf76-998sn			system-cluster-critical pod "coredns-f45c4bf76-998sn" is pending
Pod	kube-system/ebs-csi-node-lg54z				system-node-critical pod "ebs-csi-node-lg54z" is pending
Pod	kube-system/ebs-csi-node-nvzjx				system-node-critical pod "ebs-csi-node-nvzjx" is pending

Validation Failed
W0603 16:09:45.546708   11758 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 12 lines ...
Pod	kube-system/cert-manager-cainjector-74d69756d5-4h8rx	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-4h8rx" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-pclg6	system-cluster-critical pod "cert-manager-webhook-7bbf67968-pclg6" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-s82xt		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-s82xt" is pending
Pod	kube-system/coredns-f45c4bf76-998sn			system-cluster-critical pod "coredns-f45c4bf76-998sn" is pending
Pod	kube-system/ebs-csi-node-nvzjx				system-node-critical pod "ebs-csi-node-nvzjx" is pending

Validation Failed
W0603 16:09:56.754885   11758 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME				MESSAGE
Pod	kube-system/calico-node-8tv9d	system-node-critical pod "calico-node-8tv9d" is not ready (calico-node)
Pod	kube-system/calico-node-qnjgw	system-node-critical pod "calico-node-qnjgw" is not ready (calico-node)

Validation Failed
W0603 16:10:07.972353   11758 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

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

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

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

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

      Distro debian doesn't support ntfs -- skipping

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.asTGBjoOr/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.asTGBjoOr/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.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 4 lines ...
STEP: Creating a kubernetes client
Jun  3 16:13:20.929: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename volumemode
W0603 16:13:21.301200   25655 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Jun  3 16:13:21.301: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail to use a volume in a pod with mismatched mode [Slow]
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  3 16:13:21.402: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  3 16:13:21.402: INFO: Creating resource for dynamic PV
Jun  3 16:13:21.402: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-9761x5d2t
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  3 16:13:31.784: INFO: Deleting pod "pod-694a0d78-dc88-4f71-b95e-b5c99c29e06b" in namespace "volumemode-9761"
Jun  3 16:13:31.836: INFO: Wait up to 5m0s for pod "pod-694a0d78-dc88-4f71-b95e-b5c99c29e06b" to be fully deleted
STEP: Deleting pvc
Jun  3 16:13:42.042: INFO: Deleting PersistentVolumeClaim "aws7wchl"
Jun  3 16:13:42.093: INFO: Waiting up to 5m0s for PersistentVolume pvc-c809b599-6765-4ffc-a145-602d35f282a3 to get deleted
Jun  3 16:13:42.145: INFO: PersistentVolume pvc-c809b599-6765-4ffc-a145-602d35f282a3 found and phase=Released (51.011703ms)
... skipping 9 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.asTGBjoOr/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.asTGBjoOr/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
    /tmp/kops.asTGBjoOr/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.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (ext3)] volumes
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  3 16:13:47.404: INFO: Driver "ebs.csi.aws.com" does not support volume type "PreprovisionedPV" - skipping
[AfterEach] [Testpattern: Pre-provisioned PV (ext3)] volumes
... skipping 113 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.asTGBjoOr/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.asTGBjoOr/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.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 46 lines ...
STEP: Creating a kubernetes client
Jun  3 16:13:21.009: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename volumemode
W0603 16:13:21.946222   25801 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Jun  3 16:13:21.946: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail to use a volume in a pod with mismatched mode [Slow]
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  3 16:13:22.049: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  3 16:13:22.049: INFO: Creating resource for dynamic PV
Jun  3 16:13:22.049: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-6165rfdxj
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  3 16:13:34.419: INFO: Deleting pod "pod-79a872ff-b3f0-4014-ac12-3e68ad94bdde" in namespace "volumemode-6165"
Jun  3 16:13:34.471: INFO: Wait up to 5m0s for pod "pod-79a872ff-b3f0-4014-ac12-3e68ad94bdde" to be fully deleted
STEP: Deleting pvc
Jun  3 16:13:42.679: INFO: Deleting PersistentVolumeClaim "aws6tpdk"
Jun  3 16:13:42.732: INFO: Waiting up to 5m0s for PersistentVolume pvc-6781e84d-975d-4cfd-a436-c2c41c10c7b0 to get deleted
Jun  3 16:13:42.783: INFO: PersistentVolume pvc-6781e84d-975d-4cfd-a436-c2c41c10c7b0 found and phase=Released (51.707611ms)
... skipping 9 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.asTGBjoOr/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.asTGBjoOr/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (block volmode)] volumeMode
    /tmp/kops.asTGBjoOr/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.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 217 lines ...
STEP: Creating a kubernetes client
Jun  3 16:13:20.716: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename volumemode
W0603 16:13:21.070674   25657 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Jun  3 16:13:21.070: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail to use a volume in a pod with mismatched mode [Slow]
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  3 16:13:21.176: INFO: Creating resource for dynamic PV
Jun  3 16:13:21.176: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-1696-e2e-sclxjn6
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  3 16:13:29.567: INFO: Deleting pod "pod-a6c5aefe-78d6-4a50-b62e-21b06c586d2d" in namespace "volumemode-1696"
Jun  3 16:13:29.619: INFO: Wait up to 5m0s for pod "pod-a6c5aefe-78d6-4a50-b62e-21b06c586d2d" to be fully deleted
STEP: Deleting pvc
Jun  3 16:13:35.822: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com4xkq6"
Jun  3 16:13:35.873: INFO: Waiting up to 5m0s for PersistentVolume pvc-805b0962-d438-43c0-92d2-86e8a3fd5a57 to get deleted
Jun  3 16:13:35.923: INFO: PersistentVolume pvc-805b0962-d438-43c0-92d2-86e8a3fd5a57 found and phase=Released (50.579676ms)
... skipping 9 lines ...

• [SLOW TEST:30.576 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.asTGBjoOr/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.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  3 16:13:20.957: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename volumemode
W0603 16:13:21.326715   25737 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Jun  3 16:13:21.326: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail to use a volume in a pod with mismatched mode [Slow]
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  3 16:13:21.429: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  3 16:13:21.976: INFO: Successfully created a new PD: "aws://us-west-1a/vol-065f03acec41e6f97".
Jun  3 16:13:21.976: INFO: Creating resource for pre-provisioned PV
Jun  3 16:13:21.976: INFO: Creating PVC and PV
... skipping 5 lines ...
Jun  3 16:13:26.481: INFO: PersistentVolumeClaim pvc-lrb97 found but phase is Pending instead of Bound.
Jun  3 16:13:28.533: INFO: PersistentVolumeClaim pvc-lrb97 found but phase is Pending instead of Bound.
Jun  3 16:13:30.585: INFO: PersistentVolumeClaim pvc-lrb97 found and phase=Bound (8.259057108s)
Jun  3 16:13:30.586: INFO: Waiting up to 3m0s for PersistentVolume aws-dbthm to have phase Bound
Jun  3 16:13:30.636: INFO: PersistentVolume aws-dbthm found and phase=Bound (50.795334ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  3 16:13:32.954: INFO: Deleting pod "pod-7a65b276-4535-4432-88e6-fd6b7745f1e5" in namespace "volumemode-6984"
Jun  3 16:13:33.023: INFO: Wait up to 5m0s for pod "pod-7a65b276-4535-4432-88e6-fd6b7745f1e5" to be fully deleted
STEP: Deleting pv and pvc
Jun  3 16:13:43.128: INFO: Deleting PersistentVolumeClaim "pvc-lrb97"
Jun  3 16:13:43.180: INFO: Deleting PersistentVolume "aws-dbthm"
Jun  3 16:13:43.388: INFO: Couldn't delete PD "aws://us-west-1a/vol-065f03acec41e6f97", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-065f03acec41e6f97 is currently attached to i-0bc50fa72c0564cf8
	status code: 400, request id: f4ad312e-20d5-4f7d-a28c-f907c5d153d9
Jun  3 16:13:48.706: INFO: Couldn't delete PD "aws://us-west-1a/vol-065f03acec41e6f97", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-065f03acec41e6f97 is currently attached to i-0bc50fa72c0564cf8
	status code: 400, request id: 2d5eea95-7347-4e57-9779-8b5f724d4a8c
Jun  3 16:13:54.084: INFO: Successfully deleted PD "aws://us-west-1a/vol-065f03acec41e6f97".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  3 16:13:54.085: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-6984" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.asTGBjoOr/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.asTGBjoOr/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
    /tmp/kops.asTGBjoOr/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.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic Snapshot (delete policy)] snapshottable-stress[Feature:VolumeSnapshotDataSource]
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  3 16:13:54.247: INFO: Driver aws doesn't specify snapshot stress test options -- skipping
[AfterEach] [Testpattern: Dynamic Snapshot (delete policy)] snapshottable-stress[Feature:VolumeSnapshotDataSource]
... skipping 28 lines ...
Jun  3 16:13:24.294: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-3566-e2e-scrgdgk
STEP: creating a claim
Jun  3 16:13:24.347: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Jun  3 16:13:24.450: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun  3 16:13:24.563: INFO: Error updating pvc ebs.csi.aws.comsr2jm: PersistentVolumeClaim "ebs.csi.aws.comsr2jm" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3566-e2e-scrgdgk",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun  3 16:13:54.816: INFO: Error updating pvc ebs.csi.aws.comsr2jm: PersistentVolumeClaim "ebs.csi.aws.comsr2jm" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 34 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.asTGBjoOr/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.asTGBjoOr/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.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 54 lines ...
Jun  3 16:13:21.650: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-9447mz5xs
STEP: creating a claim
Jun  3 16:13:21.702: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-qnpv
STEP: Creating a pod to test exec-volume-test
Jun  3 16:13:21.861: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-qnpv" in namespace "volume-9447" to be "Succeeded or Failed"
Jun  3 16:13:21.912: INFO: Pod "exec-volume-test-dynamicpv-qnpv": Phase="Pending", Reason="", readiness=false. Elapsed: 51.110285ms
Jun  3 16:13:23.964: INFO: Pod "exec-volume-test-dynamicpv-qnpv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.10324163s
Jun  3 16:13:26.021: INFO: Pod "exec-volume-test-dynamicpv-qnpv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.159650733s
Jun  3 16:13:28.073: INFO: Pod "exec-volume-test-dynamicpv-qnpv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.212162642s
Jun  3 16:13:30.125: INFO: Pod "exec-volume-test-dynamicpv-qnpv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.264203401s
Jun  3 16:13:32.177: INFO: Pod "exec-volume-test-dynamicpv-qnpv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.316303224s
Jun  3 16:13:34.230: INFO: Pod "exec-volume-test-dynamicpv-qnpv": Phase="Pending", Reason="", readiness=false. Elapsed: 12.368806856s
Jun  3 16:13:36.282: INFO: Pod "exec-volume-test-dynamicpv-qnpv": Phase="Pending", Reason="", readiness=false. Elapsed: 14.421053769s
Jun  3 16:13:38.335: INFO: Pod "exec-volume-test-dynamicpv-qnpv": Phase="Pending", Reason="", readiness=false. Elapsed: 16.473903338s
Jun  3 16:13:40.386: INFO: Pod "exec-volume-test-dynamicpv-qnpv": Phase="Pending", Reason="", readiness=false. Elapsed: 18.525593068s
Jun  3 16:13:42.439: INFO: Pod "exec-volume-test-dynamicpv-qnpv": Phase="Pending", Reason="", readiness=false. Elapsed: 20.578271744s
Jun  3 16:13:44.491: INFO: Pod "exec-volume-test-dynamicpv-qnpv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.630014996s
STEP: Saw pod success
Jun  3 16:13:44.491: INFO: Pod "exec-volume-test-dynamicpv-qnpv" satisfied condition "Succeeded or Failed"
Jun  3 16:13:44.542: INFO: Trying to get logs from node ip-172-20-56-152.us-west-1.compute.internal pod exec-volume-test-dynamicpv-qnpv container exec-container-dynamicpv-qnpv: <nil>
STEP: delete the pod
Jun  3 16:13:44.651: INFO: Waiting for pod exec-volume-test-dynamicpv-qnpv to disappear
Jun  3 16:13:44.702: INFO: Pod exec-volume-test-dynamicpv-qnpv no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-qnpv
Jun  3 16:13:44.702: INFO: Deleting pod "exec-volume-test-dynamicpv-qnpv" in namespace "volume-9447"
... skipping 113 lines ...
Jun  3 16:13:29.317: INFO: PersistentVolumeClaim pvc-ttlrw found but phase is Pending instead of Bound.
Jun  3 16:13:31.369: INFO: PersistentVolumeClaim pvc-ttlrw found and phase=Bound (8.259243451s)
Jun  3 16:13:31.369: INFO: Waiting up to 3m0s for PersistentVolume aws-b98zg to have phase Bound
Jun  3 16:13:31.422: INFO: PersistentVolume aws-b98zg found and phase=Bound (52.572456ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-dbcc
STEP: Creating a pod to test exec-volume-test
Jun  3 16:13:31.578: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-dbcc" in namespace "volume-1602" to be "Succeeded or Failed"
Jun  3 16:13:31.629: INFO: Pod "exec-volume-test-preprovisionedpv-dbcc": Phase="Pending", Reason="", readiness=false. Elapsed: 51.053717ms
Jun  3 16:13:33.681: INFO: Pod "exec-volume-test-preprovisionedpv-dbcc": Phase="Pending", Reason="", readiness=false. Elapsed: 2.10347838s
Jun  3 16:13:35.733: INFO: Pod "exec-volume-test-preprovisionedpv-dbcc": Phase="Pending", Reason="", readiness=false. Elapsed: 4.15487596s
Jun  3 16:13:37.785: INFO: Pod "exec-volume-test-preprovisionedpv-dbcc": Phase="Pending", Reason="", readiness=false. Elapsed: 6.20741623s
Jun  3 16:13:39.837: INFO: Pod "exec-volume-test-preprovisionedpv-dbcc": Phase="Pending", Reason="", readiness=false. Elapsed: 8.259190356s
Jun  3 16:13:41.889: INFO: Pod "exec-volume-test-preprovisionedpv-dbcc": Phase="Pending", Reason="", readiness=false. Elapsed: 10.310939217s
Jun  3 16:13:43.942: INFO: Pod "exec-volume-test-preprovisionedpv-dbcc": Phase="Pending", Reason="", readiness=false. Elapsed: 12.364196438s
Jun  3 16:13:45.994: INFO: Pod "exec-volume-test-preprovisionedpv-dbcc": Phase="Pending", Reason="", readiness=false. Elapsed: 14.416218798s
Jun  3 16:13:48.046: INFO: Pod "exec-volume-test-preprovisionedpv-dbcc": Phase="Pending", Reason="", readiness=false. Elapsed: 16.467699288s
Jun  3 16:13:50.100: INFO: Pod "exec-volume-test-preprovisionedpv-dbcc": Phase="Pending", Reason="", readiness=false. Elapsed: 18.521975347s
Jun  3 16:13:52.152: INFO: Pod "exec-volume-test-preprovisionedpv-dbcc": Phase="Pending", Reason="", readiness=false. Elapsed: 20.574615916s
Jun  3 16:13:54.204: INFO: Pod "exec-volume-test-preprovisionedpv-dbcc": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.626278603s
STEP: Saw pod success
Jun  3 16:13:54.204: INFO: Pod "exec-volume-test-preprovisionedpv-dbcc" satisfied condition "Succeeded or Failed"
Jun  3 16:13:54.256: INFO: Trying to get logs from node ip-172-20-56-152.us-west-1.compute.internal pod exec-volume-test-preprovisionedpv-dbcc container exec-container-preprovisionedpv-dbcc: <nil>
STEP: delete the pod
Jun  3 16:13:54.368: INFO: Waiting for pod exec-volume-test-preprovisionedpv-dbcc to disappear
Jun  3 16:13:54.420: INFO: Pod exec-volume-test-preprovisionedpv-dbcc no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-dbcc
Jun  3 16:13:54.420: INFO: Deleting pod "exec-volume-test-preprovisionedpv-dbcc" in namespace "volume-1602"
STEP: Deleting pv and pvc
Jun  3 16:13:54.471: INFO: Deleting PersistentVolumeClaim "pvc-ttlrw"
Jun  3 16:13:54.523: INFO: Deleting PersistentVolume "aws-b98zg"
Jun  3 16:13:54.751: INFO: Couldn't delete PD "aws://us-west-1a/vol-004c48fa1f9bf4be7", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-004c48fa1f9bf4be7 is currently attached to i-05d143d647948db9b
	status code: 400, request id: 466edfc4-a72e-4293-9cab-358b1d8a5726
Jun  3 16:14:00.157: INFO: Couldn't delete PD "aws://us-west-1a/vol-004c48fa1f9bf4be7", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-004c48fa1f9bf4be7 is currently attached to i-05d143d647948db9b
	status code: 400, request id: 33ca42df-fdc5-4bbd-b9fd-323f8e1a4175
Jun  3 16:14:05.524: INFO: Couldn't delete PD "aws://us-west-1a/vol-004c48fa1f9bf4be7", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-004c48fa1f9bf4be7 is currently attached to i-05d143d647948db9b
	status code: 400, request id: 85c5f733-efd6-4c9e-b179-9c6102f0ab44
Jun  3 16:14:10.879: INFO: Successfully deleted PD "aws://us-west-1a/vol-004c48fa1f9bf4be7".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  3 16:14:10.879: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-1602" for this suite.
... skipping 45 lines ...
Jun  3 16:13:23.151: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9470k8nmq
STEP: creating a claim
Jun  3 16:13:23.203: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-dxpl
STEP: Creating a pod to test subpath
Jun  3 16:13:23.370: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-dxpl" in namespace "provisioning-9470" to be "Succeeded or Failed"
Jun  3 16:13:23.421: INFO: Pod "pod-subpath-test-dynamicpv-dxpl": Phase="Pending", Reason="", readiness=false. Elapsed: 51.062461ms
Jun  3 16:13:25.474: INFO: Pod "pod-subpath-test-dynamicpv-dxpl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.103911125s
Jun  3 16:13:27.531: INFO: Pod "pod-subpath-test-dynamicpv-dxpl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.160226711s
Jun  3 16:13:29.585: INFO: Pod "pod-subpath-test-dynamicpv-dxpl": Phase="Pending", Reason="", readiness=false. Elapsed: 6.214693697s
Jun  3 16:13:31.637: INFO: Pod "pod-subpath-test-dynamicpv-dxpl": Phase="Pending", Reason="", readiness=false. Elapsed: 8.266263167s
Jun  3 16:13:33.689: INFO: Pod "pod-subpath-test-dynamicpv-dxpl": Phase="Pending", Reason="", readiness=false. Elapsed: 10.318542675s
... skipping 5 lines ...
Jun  3 16:13:46.008: INFO: Pod "pod-subpath-test-dynamicpv-dxpl": Phase="Pending", Reason="", readiness=false. Elapsed: 22.637559683s
Jun  3 16:13:48.060: INFO: Pod "pod-subpath-test-dynamicpv-dxpl": Phase="Pending", Reason="", readiness=false. Elapsed: 24.689734101s
Jun  3 16:13:50.112: INFO: Pod "pod-subpath-test-dynamicpv-dxpl": Phase="Pending", Reason="", readiness=false. Elapsed: 26.741335847s
Jun  3 16:13:52.167: INFO: Pod "pod-subpath-test-dynamicpv-dxpl": Phase="Pending", Reason="", readiness=false. Elapsed: 28.796604826s
Jun  3 16:13:54.220: INFO: Pod "pod-subpath-test-dynamicpv-dxpl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 30.849687466s
STEP: Saw pod success
Jun  3 16:13:54.220: INFO: Pod "pod-subpath-test-dynamicpv-dxpl" satisfied condition "Succeeded or Failed"
Jun  3 16:13:54.272: INFO: Trying to get logs from node ip-172-20-32-159.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-dxpl container test-container-subpath-dynamicpv-dxpl: <nil>
STEP: delete the pod
Jun  3 16:13:54.393: INFO: Waiting for pod pod-subpath-test-dynamicpv-dxpl to disappear
Jun  3 16:13:54.444: INFO: Pod pod-subpath-test-dynamicpv-dxpl no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-dxpl
Jun  3 16:13:54.444: INFO: Deleting pod "pod-subpath-test-dynamicpv-dxpl" in namespace "provisioning-9470"
... skipping 32 lines ...
STEP: Creating a kubernetes client
Jun  3 16:13:21.062: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename provisioning
W0603 16:13:22.696628   25815 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Jun  3 16:13:22.696: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail if subpath file is outside the volume [Slow][LinuxOnly]
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun  3 16:13:22.799: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  3 16:13:22.799: INFO: Creating resource for dynamic PV
Jun  3 16:13:22.799: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-781jwtnk
STEP: creating a claim
Jun  3 16:13:22.852: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-5fb8
STEP: Checking for subpath error in container status
Jun  3 16:13:53.132: INFO: Deleting pod "pod-subpath-test-dynamicpv-5fb8" in namespace "provisioning-781"
Jun  3 16:13:53.192: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-5fb8" to be fully deleted
STEP: Deleting pod
Jun  3 16:14:01.302: INFO: Deleting pod "pod-subpath-test-dynamicpv-5fb8" in namespace "provisioning-781"
STEP: Deleting pvc
Jun  3 16:14:01.459: INFO: Deleting PersistentVolumeClaim "awsnlz8t"
... skipping 14 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.asTGBjoOr/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.asTGBjoOr/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath file is outside the volume [Slow][LinuxOnly]
      /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  3 16:14:21.999: INFO: Driver supports dynamic provisioning, skipping PreprovisionedPV pattern
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
... skipping 190 lines ...
Jun  3 16:13:24.562: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-4302-e2e-scfldmv
STEP: creating a claim
Jun  3 16:13:24.615: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-2zmr
STEP: Creating a pod to test exec-volume-test
Jun  3 16:13:24.774: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-2zmr" in namespace "volume-4302" to be "Succeeded or Failed"
Jun  3 16:13:24.828: INFO: Pod "exec-volume-test-dynamicpv-2zmr": Phase="Pending", Reason="", readiness=false. Elapsed: 53.366032ms
Jun  3 16:13:26.879: INFO: Pod "exec-volume-test-dynamicpv-2zmr": Phase="Pending", Reason="", readiness=false. Elapsed: 2.105153125s
Jun  3 16:13:28.931: INFO: Pod "exec-volume-test-dynamicpv-2zmr": Phase="Pending", Reason="", readiness=false. Elapsed: 4.156552401s
Jun  3 16:13:30.982: INFO: Pod "exec-volume-test-dynamicpv-2zmr": Phase="Pending", Reason="", readiness=false. Elapsed: 6.208218878s
Jun  3 16:13:33.034: INFO: Pod "exec-volume-test-dynamicpv-2zmr": Phase="Pending", Reason="", readiness=false. Elapsed: 8.259532276s
Jun  3 16:13:35.086: INFO: Pod "exec-volume-test-dynamicpv-2zmr": Phase="Pending", Reason="", readiness=false. Elapsed: 10.312044365s
... skipping 5 lines ...
Jun  3 16:13:47.398: INFO: Pod "exec-volume-test-dynamicpv-2zmr": Phase="Pending", Reason="", readiness=false. Elapsed: 22.623988187s
Jun  3 16:13:49.450: INFO: Pod "exec-volume-test-dynamicpv-2zmr": Phase="Pending", Reason="", readiness=false. Elapsed: 24.675958208s
Jun  3 16:13:51.504: INFO: Pod "exec-volume-test-dynamicpv-2zmr": Phase="Pending", Reason="", readiness=false. Elapsed: 26.729975825s
Jun  3 16:13:53.565: INFO: Pod "exec-volume-test-dynamicpv-2zmr": Phase="Pending", Reason="", readiness=false. Elapsed: 28.790369858s
Jun  3 16:13:55.617: INFO: Pod "exec-volume-test-dynamicpv-2zmr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 30.842668239s
STEP: Saw pod success
Jun  3 16:13:55.617: INFO: Pod "exec-volume-test-dynamicpv-2zmr" satisfied condition "Succeeded or Failed"
Jun  3 16:13:55.668: INFO: Trying to get logs from node ip-172-20-54-51.us-west-1.compute.internal pod exec-volume-test-dynamicpv-2zmr container exec-container-dynamicpv-2zmr: <nil>
STEP: delete the pod
Jun  3 16:13:56.493: INFO: Waiting for pod exec-volume-test-dynamicpv-2zmr to disappear
Jun  3 16:13:56.544: INFO: Pod exec-volume-test-dynamicpv-2zmr no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-2zmr
Jun  3 16:13:56.544: INFO: Deleting pod "exec-volume-test-dynamicpv-2zmr" in namespace "volume-4302"
... skipping 152 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.asTGBjoOr/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.asTGBjoOr/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.asTGBjoOr/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.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 643 lines ...
Jun  3 16:14:22.642: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6268dgzvg
STEP: creating a claim
Jun  3 16:14:22.696: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-xd6w
STEP: Creating a pod to test subpath
Jun  3 16:14:22.856: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-xd6w" in namespace "provisioning-6268" to be "Succeeded or Failed"
Jun  3 16:14:22.908: INFO: Pod "pod-subpath-test-dynamicpv-xd6w": Phase="Pending", Reason="", readiness=false. Elapsed: 52.103608ms
Jun  3 16:14:24.962: INFO: Pod "pod-subpath-test-dynamicpv-xd6w": Phase="Pending", Reason="", readiness=false. Elapsed: 2.106037376s
Jun  3 16:14:27.016: INFO: Pod "pod-subpath-test-dynamicpv-xd6w": Phase="Pending", Reason="", readiness=false. Elapsed: 4.159286694s
Jun  3 16:14:29.069: INFO: Pod "pod-subpath-test-dynamicpv-xd6w": Phase="Pending", Reason="", readiness=false. Elapsed: 6.212907997s
Jun  3 16:14:31.122: INFO: Pod "pod-subpath-test-dynamicpv-xd6w": Phase="Pending", Reason="", readiness=false. Elapsed: 8.265856692s
Jun  3 16:14:33.176: INFO: Pod "pod-subpath-test-dynamicpv-xd6w": Phase="Pending", Reason="", readiness=false. Elapsed: 10.319819001s
... skipping 3 lines ...
Jun  3 16:14:41.387: INFO: Pod "pod-subpath-test-dynamicpv-xd6w": Phase="Pending", Reason="", readiness=false. Elapsed: 18.530488685s
Jun  3 16:14:43.441: INFO: Pod "pod-subpath-test-dynamicpv-xd6w": Phase="Pending", Reason="", readiness=false. Elapsed: 20.5844496s
Jun  3 16:14:45.495: INFO: Pod "pod-subpath-test-dynamicpv-xd6w": Phase="Pending", Reason="", readiness=false. Elapsed: 22.638304186s
Jun  3 16:14:47.547: INFO: Pod "pod-subpath-test-dynamicpv-xd6w": Phase="Pending", Reason="", readiness=false. Elapsed: 24.690860455s
Jun  3 16:14:49.600: INFO: Pod "pod-subpath-test-dynamicpv-xd6w": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.743313945s
STEP: Saw pod success
Jun  3 16:14:49.600: INFO: Pod "pod-subpath-test-dynamicpv-xd6w" satisfied condition "Succeeded or Failed"
Jun  3 16:14:49.652: INFO: Trying to get logs from node ip-172-20-61-108.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-xd6w container test-container-volume-dynamicpv-xd6w: <nil>
STEP: delete the pod
Jun  3 16:14:49.774: INFO: Waiting for pod pod-subpath-test-dynamicpv-xd6w to disappear
Jun  3 16:14:49.828: INFO: Pod pod-subpath-test-dynamicpv-xd6w no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-xd6w
Jun  3 16:14:49.828: INFO: Deleting pod "pod-subpath-test-dynamicpv-xd6w" in namespace "provisioning-6268"
... skipping 171 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  3 16:14:29.683: 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.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun  3 16:14:29.942: INFO: Creating resource for dynamic PV
Jun  3 16:14:29.942: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-717-e2e-sc62824
STEP: creating a claim
Jun  3 16:14:29.995: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-j4mn
STEP: Checking for subpath error in container status
Jun  3 16:14:46.255: INFO: Deleting pod "pod-subpath-test-dynamicpv-j4mn" in namespace "provisioning-717"
Jun  3 16:14:46.311: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-j4mn" to be fully deleted
STEP: Deleting pod
Jun  3 16:14:58.414: INFO: Deleting pod "pod-subpath-test-dynamicpv-j4mn" in namespace "provisioning-717"
STEP: Deleting pvc
Jun  3 16:14:58.567: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com2zs28"
... skipping 9 lines ...

• [SLOW TEST:34.198 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath directory is outside the volume [Slow][LinuxOnly]
    /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 7 lines ...
Jun  3 16:14:20.532: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1775-e2e-scttwb8
STEP: creating a claim
Jun  3 16:14:20.585: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-d2pj
STEP: Creating a pod to test multi_subpath
Jun  3 16:14:20.744: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-d2pj" in namespace "provisioning-1775" to be "Succeeded or Failed"
Jun  3 16:14:20.795: INFO: Pod "pod-subpath-test-dynamicpv-d2pj": Phase="Pending", Reason="", readiness=false. Elapsed: 51.011871ms
Jun  3 16:14:22.846: INFO: Pod "pod-subpath-test-dynamicpv-d2pj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.102730805s
Jun  3 16:14:24.899: INFO: Pod "pod-subpath-test-dynamicpv-d2pj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.155404759s
Jun  3 16:14:26.950: INFO: Pod "pod-subpath-test-dynamicpv-d2pj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.206913488s
Jun  3 16:14:29.008: INFO: Pod "pod-subpath-test-dynamicpv-d2pj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.264052141s
Jun  3 16:14:31.059: INFO: Pod "pod-subpath-test-dynamicpv-d2pj": Phase="Pending", Reason="", readiness=false. Elapsed: 10.315812127s
... skipping 4 lines ...
Jun  3 16:14:41.321: INFO: Pod "pod-subpath-test-dynamicpv-d2pj": Phase="Pending", Reason="", readiness=false. Elapsed: 20.577007566s
Jun  3 16:14:43.376: INFO: Pod "pod-subpath-test-dynamicpv-d2pj": Phase="Pending", Reason="", readiness=false. Elapsed: 22.631951944s
Jun  3 16:14:45.428: INFO: Pod "pod-subpath-test-dynamicpv-d2pj": Phase="Pending", Reason="", readiness=false. Elapsed: 24.684502822s
Jun  3 16:14:47.481: INFO: Pod "pod-subpath-test-dynamicpv-d2pj": Phase="Pending", Reason="", readiness=false. Elapsed: 26.737099708s
Jun  3 16:14:49.532: INFO: Pod "pod-subpath-test-dynamicpv-d2pj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 28.788846209s
STEP: Saw pod success
Jun  3 16:14:49.532: INFO: Pod "pod-subpath-test-dynamicpv-d2pj" satisfied condition "Succeeded or Failed"
Jun  3 16:14:49.584: INFO: Trying to get logs from node ip-172-20-54-51.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-d2pj container test-container-subpath-dynamicpv-d2pj: <nil>
STEP: delete the pod
Jun  3 16:14:49.698: INFO: Waiting for pod pod-subpath-test-dynamicpv-d2pj to disappear
Jun  3 16:14:49.749: INFO: Pod pod-subpath-test-dynamicpv-d2pj no longer exists
STEP: Deleting pod
Jun  3 16:14:49.749: INFO: Deleting pod "pod-subpath-test-dynamicpv-d2pj" in namespace "provisioning-1775"
... skipping 177 lines ...
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  3 16:15:07.130: 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.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Jun  3 16:15:07.439: INFO: found topology map[topology.kubernetes.io/zone:us-west-1a]
Jun  3 16:15:07.440: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  3 16:15:07.440: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.asTGBjoOr/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.asTGBjoOr/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (immediate binding)] topology
    /tmp/kops.asTGBjoOr/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.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 12 lines ...
Jun  3 16:14:32.598: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-70686bjdk
STEP: creating a claim
Jun  3 16:14:32.651: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-qnmh
STEP: Creating a pod to test multi_subpath
Jun  3 16:14:32.809: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-qnmh" in namespace "provisioning-7068" to be "Succeeded or Failed"
Jun  3 16:14:32.860: INFO: Pod "pod-subpath-test-dynamicpv-qnmh": Phase="Pending", Reason="", readiness=false. Elapsed: 51.351384ms
Jun  3 16:14:34.916: INFO: Pod "pod-subpath-test-dynamicpv-qnmh": Phase="Pending", Reason="", readiness=false. Elapsed: 2.106510835s
Jun  3 16:14:36.967: INFO: Pod "pod-subpath-test-dynamicpv-qnmh": Phase="Pending", Reason="", readiness=false. Elapsed: 4.15813153s
Jun  3 16:14:39.019: INFO: Pod "pod-subpath-test-dynamicpv-qnmh": Phase="Pending", Reason="", readiness=false. Elapsed: 6.210245346s
Jun  3 16:14:41.071: INFO: Pod "pod-subpath-test-dynamicpv-qnmh": Phase="Pending", Reason="", readiness=false. Elapsed: 8.262026485s
Jun  3 16:14:43.124: INFO: Pod "pod-subpath-test-dynamicpv-qnmh": Phase="Pending", Reason="", readiness=false. Elapsed: 10.314964907s
... skipping 2 lines ...
Jun  3 16:14:49.282: INFO: Pod "pod-subpath-test-dynamicpv-qnmh": Phase="Pending", Reason="", readiness=false. Elapsed: 16.472811336s
Jun  3 16:14:51.333: INFO: Pod "pod-subpath-test-dynamicpv-qnmh": Phase="Pending", Reason="", readiness=false. Elapsed: 18.524335202s
Jun  3 16:14:53.385: INFO: Pod "pod-subpath-test-dynamicpv-qnmh": Phase="Pending", Reason="", readiness=false. Elapsed: 20.576472479s
Jun  3 16:14:55.438: INFO: Pod "pod-subpath-test-dynamicpv-qnmh": Phase="Pending", Reason="", readiness=false. Elapsed: 22.628747111s
Jun  3 16:14:57.489: INFO: Pod "pod-subpath-test-dynamicpv-qnmh": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.680228156s
STEP: Saw pod success
Jun  3 16:14:57.489: INFO: Pod "pod-subpath-test-dynamicpv-qnmh" satisfied condition "Succeeded or Failed"
Jun  3 16:14:57.541: INFO: Trying to get logs from node ip-172-20-32-159.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-qnmh container test-container-subpath-dynamicpv-qnmh: <nil>
STEP: delete the pod
Jun  3 16:14:57.658: INFO: Waiting for pod pod-subpath-test-dynamicpv-qnmh to disappear
Jun  3 16:14:57.709: INFO: Pod pod-subpath-test-dynamicpv-qnmh no longer exists
STEP: Deleting pod
Jun  3 16:14:57.709: INFO: Deleting pod "pod-subpath-test-dynamicpv-qnmh" in namespace "provisioning-7068"
... skipping 116 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.asTGBjoOr/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.asTGBjoOr/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.asTGBjoOr/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.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 249 lines ...
Jun  3 16:14:44.524: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3667-e2e-scvrjdm
STEP: creating a claim
Jun  3 16:14:44.576: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-gxwm
STEP: Creating a pod to test subpath
Jun  3 16:14:44.734: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-gxwm" in namespace "provisioning-3667" to be "Succeeded or Failed"
Jun  3 16:14:44.785: INFO: Pod "pod-subpath-test-dynamicpv-gxwm": Phase="Pending", Reason="", readiness=false. Elapsed: 51.237063ms
Jun  3 16:14:46.837: INFO: Pod "pod-subpath-test-dynamicpv-gxwm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.103246794s
Jun  3 16:14:48.889: INFO: Pod "pod-subpath-test-dynamicpv-gxwm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.154876047s
Jun  3 16:14:50.941: INFO: Pod "pod-subpath-test-dynamicpv-gxwm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.207122328s
Jun  3 16:14:53.002: INFO: Pod "pod-subpath-test-dynamicpv-gxwm": Phase="Pending", Reason="", readiness=false. Elapsed: 8.268796069s
Jun  3 16:14:55.056: INFO: Pod "pod-subpath-test-dynamicpv-gxwm": Phase="Pending", Reason="", readiness=false. Elapsed: 10.32205898s
Jun  3 16:14:57.107: INFO: Pod "pod-subpath-test-dynamicpv-gxwm": Phase="Pending", Reason="", readiness=false. Elapsed: 12.373780677s
Jun  3 16:14:59.171: INFO: Pod "pod-subpath-test-dynamicpv-gxwm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.436942499s
STEP: Saw pod success
Jun  3 16:14:59.171: INFO: Pod "pod-subpath-test-dynamicpv-gxwm" satisfied condition "Succeeded or Failed"
Jun  3 16:14:59.236: INFO: Trying to get logs from node ip-172-20-61-108.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-gxwm container test-container-subpath-dynamicpv-gxwm: <nil>
STEP: delete the pod
Jun  3 16:14:59.348: INFO: Waiting for pod pod-subpath-test-dynamicpv-gxwm to disappear
Jun  3 16:14:59.412: INFO: Pod pod-subpath-test-dynamicpv-gxwm no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-gxwm
Jun  3 16:14:59.412: INFO: Deleting pod "pod-subpath-test-dynamicpv-gxwm" in namespace "provisioning-3667"
... skipping 104 lines ...
Jun  3 16:13:55.371: INFO: Creating resource for dynamic PV
Jun  3 16:13:55.371: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3057pstfs
STEP: creating a claim
Jun  3 16:13:55.423: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-3057
Jun  3 16:13:55.582: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-3057" in namespace "provisioning-3057" to be "Succeeded or Failed"
Jun  3 16:13:55.633: INFO: Pod "volume-prep-provisioning-3057": Phase="Pending", Reason="", readiness=false. Elapsed: 51.121972ms
Jun  3 16:13:57.685: INFO: Pod "volume-prep-provisioning-3057": Phase="Pending", Reason="", readiness=false. Elapsed: 2.102708039s
Jun  3 16:13:59.738: INFO: Pod "volume-prep-provisioning-3057": Phase="Pending", Reason="", readiness=false. Elapsed: 4.15544068s
Jun  3 16:14:01.790: INFO: Pod "volume-prep-provisioning-3057": Phase="Pending", Reason="", readiness=false. Elapsed: 6.207984817s
Jun  3 16:14:03.842: INFO: Pod "volume-prep-provisioning-3057": Phase="Pending", Reason="", readiness=false. Elapsed: 8.259549305s
Jun  3 16:14:05.894: INFO: Pod "volume-prep-provisioning-3057": Phase="Pending", Reason="", readiness=false. Elapsed: 10.311192856s
... skipping 10 lines ...
Jun  3 16:14:28.471: INFO: Pod "volume-prep-provisioning-3057": Phase="Pending", Reason="", readiness=false. Elapsed: 32.888437775s
Jun  3 16:14:30.522: INFO: Pod "volume-prep-provisioning-3057": Phase="Pending", Reason="", readiness=false. Elapsed: 34.939920568s
Jun  3 16:14:32.576: INFO: Pod "volume-prep-provisioning-3057": Phase="Pending", Reason="", readiness=false. Elapsed: 36.993613949s
Jun  3 16:14:34.629: INFO: Pod "volume-prep-provisioning-3057": Phase="Pending", Reason="", readiness=false. Elapsed: 39.046226256s
Jun  3 16:14:36.680: INFO: Pod "volume-prep-provisioning-3057": Phase="Succeeded", Reason="", readiness=false. Elapsed: 41.09773694s
STEP: Saw pod success
Jun  3 16:14:36.680: INFO: Pod "volume-prep-provisioning-3057" satisfied condition "Succeeded or Failed"
Jun  3 16:14:36.680: INFO: Deleting pod "volume-prep-provisioning-3057" in namespace "provisioning-3057"
Jun  3 16:14:36.737: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-3057" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-pv2g
STEP: Checking for subpath error in container status
Jun  3 16:14:54.957: INFO: Deleting pod "pod-subpath-test-dynamicpv-pv2g" in namespace "provisioning-3057"
Jun  3 16:14:55.025: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-pv2g" to be fully deleted
STEP: Deleting pod
Jun  3 16:14:55.079: INFO: Deleting pod "pod-subpath-test-dynamicpv-pv2g" in namespace "provisioning-3057"
STEP: Deleting pvc
Jun  3 16:14:55.233: INFO: Deleting PersistentVolumeClaim "awsrvskh"
... skipping 141 lines ...
Jun  3 16:14:54.988: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1514gj527
STEP: creating a claim
Jun  3 16:14:55.041: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-89tq
STEP: Creating a pod to test subpath
Jun  3 16:14:55.200: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-89tq" in namespace "provisioning-1514" to be "Succeeded or Failed"
Jun  3 16:14:55.250: INFO: Pod "pod-subpath-test-dynamicpv-89tq": Phase="Pending", Reason="", readiness=false. Elapsed: 49.910313ms
Jun  3 16:14:57.301: INFO: Pod "pod-subpath-test-dynamicpv-89tq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.100873163s
Jun  3 16:14:59.352: INFO: Pod "pod-subpath-test-dynamicpv-89tq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.15215363s
Jun  3 16:15:01.403: INFO: Pod "pod-subpath-test-dynamicpv-89tq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.202722835s
Jun  3 16:15:03.453: INFO: Pod "pod-subpath-test-dynamicpv-89tq": Phase="Pending", Reason="", readiness=false. Elapsed: 8.2529342s
Jun  3 16:15:05.504: INFO: Pod "pod-subpath-test-dynamicpv-89tq": Phase="Pending", Reason="", readiness=false. Elapsed: 10.303688402s
Jun  3 16:15:07.555: INFO: Pod "pod-subpath-test-dynamicpv-89tq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.355121216s
STEP: Saw pod success
Jun  3 16:15:07.555: INFO: Pod "pod-subpath-test-dynamicpv-89tq" satisfied condition "Succeeded or Failed"
Jun  3 16:15:07.605: INFO: Trying to get logs from node ip-172-20-32-159.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-89tq container test-container-volume-dynamicpv-89tq: <nil>
STEP: delete the pod
Jun  3 16:15:07.722: INFO: Waiting for pod pod-subpath-test-dynamicpv-89tq to disappear
Jun  3 16:15:07.772: INFO: Pod pod-subpath-test-dynamicpv-89tq no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-89tq
Jun  3 16:15:07.772: INFO: Deleting pod "pod-subpath-test-dynamicpv-89tq" in namespace "provisioning-1514"
... skipping 471 lines ...
Jun  3 16:13:21.376: INFO: Creating resource for dynamic PV
Jun  3 16:13:21.376: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-5205-e2e-scf6pd6
STEP: creating a claim
Jun  3 16:13:21.433: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun  3 16:13:21.596: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-tvtbg" in namespace "snapshotting-5205" to be "Succeeded or Failed"
Jun  3 16:13:21.647: INFO: Pod "pvc-snapshottable-tester-tvtbg": Phase="Pending", Reason="", readiness=false. Elapsed: 51.028958ms
Jun  3 16:13:23.699: INFO: Pod "pvc-snapshottable-tester-tvtbg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.102845079s
Jun  3 16:13:25.750: INFO: Pod "pvc-snapshottable-tester-tvtbg": Phase="Pending", Reason="", readiness=false. Elapsed: 4.154468825s
Jun  3 16:13:27.802: INFO: Pod "pvc-snapshottable-tester-tvtbg": Phase="Pending", Reason="", readiness=false. Elapsed: 6.206333339s
Jun  3 16:13:29.854: INFO: Pod "pvc-snapshottable-tester-tvtbg": Phase="Pending", Reason="", readiness=false. Elapsed: 8.258447678s
Jun  3 16:13:31.909: INFO: Pod "pvc-snapshottable-tester-tvtbg": Phase="Pending", Reason="", readiness=false. Elapsed: 10.313222879s
Jun  3 16:13:33.961: INFO: Pod "pvc-snapshottable-tester-tvtbg": Phase="Pending", Reason="", readiness=false. Elapsed: 12.365523958s
Jun  3 16:13:36.013: INFO: Pod "pvc-snapshottable-tester-tvtbg": Phase="Pending", Reason="", readiness=false. Elapsed: 14.417241876s
Jun  3 16:13:38.066: INFO: Pod "pvc-snapshottable-tester-tvtbg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.469653809s
STEP: Saw pod success
Jun  3 16:13:38.066: INFO: Pod "pvc-snapshottable-tester-tvtbg" satisfied condition "Succeeded or Failed"
Jun  3 16:13:38.187: INFO: Pod pvc-snapshottable-tester-tvtbg has the following logs: 
Jun  3 16:13:38.187: INFO: Deleting pod "pvc-snapshottable-tester-tvtbg" in namespace "snapshotting-5205"
Jun  3 16:13:38.248: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-tvtbg" to be fully deleted
Jun  3 16:13:38.299: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comm6hpf] to have phase Bound
Jun  3 16:13:38.350: INFO: PersistentVolumeClaim ebs.csi.aws.comm6hpf found and phase=Bound (50.937932ms)
STEP: [init] checking the claim
... skipping 41 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.asTGBjoOr/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  3 16:14:42.570: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-cfpp6" in namespace "snapshotting-5205" to be "Succeeded or Failed"
Jun  3 16:14:42.623: INFO: Pod "pvc-snapshottable-data-tester-cfpp6": Phase="Pending", Reason="", readiness=false. Elapsed: 52.02828ms
Jun  3 16:14:44.675: INFO: Pod "pvc-snapshottable-data-tester-cfpp6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.104464615s
Jun  3 16:14:46.727: INFO: Pod "pvc-snapshottable-data-tester-cfpp6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.156035308s
Jun  3 16:14:48.782: INFO: Pod "pvc-snapshottable-data-tester-cfpp6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.211901695s
STEP: Saw pod success
Jun  3 16:14:48.782: INFO: Pod "pvc-snapshottable-data-tester-cfpp6" satisfied condition "Succeeded or Failed"
Jun  3 16:14:48.889: INFO: Pod pvc-snapshottable-data-tester-cfpp6 has the following logs: 
Jun  3 16:14:48.889: INFO: Deleting pod "pvc-snapshottable-data-tester-cfpp6" in namespace "snapshotting-5205"
Jun  3 16:14:48.956: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-cfpp6" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun  3 16:15:03.227: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-5205 exec restored-pvc-tester-l86jh --namespace=snapshotting-5205 -- cat /mnt/test/data'
... skipping 256 lines ...
    /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:108
      
      /tmp/kops.asTGBjoOr/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.asTGBjoOr/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-5205 exec restored-pvc-tester-l86jh --namespace=snapshotting-5205 -- 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-5205 exec restored-pvc-tester-l86jh --namespace=snapshotting-5205 -- 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.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:602
------------------------------
[BeforeEach] [sig-storage] Zone Support [Feature:vsphere]
... skipping 135 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.asTGBjoOr/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.asTGBjoOr/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.asTGBjoOr/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.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 139 lines ...
Jun  3 16:14:44.194: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4603cmwmp
STEP: creating a claim
Jun  3 16:14:44.247: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-fkx6
STEP: Creating a pod to test subpath
Jun  3 16:14:44.404: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-fkx6" in namespace "provisioning-4603" to be "Succeeded or Failed"
Jun  3 16:14:44.455: INFO: Pod "pod-subpath-test-dynamicpv-fkx6": Phase="Pending", Reason="", readiness=false. Elapsed: 51.03043ms
Jun  3 16:14:46.507: INFO: Pod "pod-subpath-test-dynamicpv-fkx6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.102675306s
Jun  3 16:14:48.559: INFO: Pod "pod-subpath-test-dynamicpv-fkx6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.155086902s
Jun  3 16:14:50.611: INFO: Pod "pod-subpath-test-dynamicpv-fkx6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.206814395s
Jun  3 16:14:52.663: INFO: Pod "pod-subpath-test-dynamicpv-fkx6": Phase="Pending", Reason="", readiness=false. Elapsed: 8.258651757s
Jun  3 16:14:54.717: INFO: Pod "pod-subpath-test-dynamicpv-fkx6": Phase="Pending", Reason="", readiness=false. Elapsed: 10.312233626s
Jun  3 16:14:56.769: INFO: Pod "pod-subpath-test-dynamicpv-fkx6": Phase="Pending", Reason="", readiness=false. Elapsed: 12.364164448s
Jun  3 16:14:58.822: INFO: Pod "pod-subpath-test-dynamicpv-fkx6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.417288731s
STEP: Saw pod success
Jun  3 16:14:58.822: INFO: Pod "pod-subpath-test-dynamicpv-fkx6" satisfied condition "Succeeded or Failed"
Jun  3 16:14:58.873: INFO: Trying to get logs from node ip-172-20-61-108.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-fkx6 container test-container-subpath-dynamicpv-fkx6: <nil>
STEP: delete the pod
Jun  3 16:14:58.987: INFO: Waiting for pod pod-subpath-test-dynamicpv-fkx6 to disappear
Jun  3 16:14:59.052: INFO: Pod pod-subpath-test-dynamicpv-fkx6 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-fkx6
Jun  3 16:14:59.052: INFO: Deleting pod "pod-subpath-test-dynamicpv-fkx6" in namespace "provisioning-4603"
STEP: Creating pod pod-subpath-test-dynamicpv-fkx6
STEP: Creating a pod to test subpath
Jun  3 16:14:59.163: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-fkx6" in namespace "provisioning-4603" to be "Succeeded or Failed"
Jun  3 16:14:59.234: INFO: Pod "pod-subpath-test-dynamicpv-fkx6": Phase="Pending", Reason="", readiness=false. Elapsed: 71.15703ms
Jun  3 16:15:01.287: INFO: Pod "pod-subpath-test-dynamicpv-fkx6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.123715228s
Jun  3 16:15:03.339: INFO: Pod "pod-subpath-test-dynamicpv-fkx6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.176453471s
Jun  3 16:15:05.391: INFO: Pod "pod-subpath-test-dynamicpv-fkx6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.228262551s
Jun  3 16:15:07.444: INFO: Pod "pod-subpath-test-dynamicpv-fkx6": Phase="Pending", Reason="", readiness=false. Elapsed: 8.280782403s
Jun  3 16:15:09.495: INFO: Pod "pod-subpath-test-dynamicpv-fkx6": Phase="Pending", Reason="", readiness=false. Elapsed: 10.33234686s
... skipping 7 lines ...
Jun  3 16:15:25.913: INFO: Pod "pod-subpath-test-dynamicpv-fkx6": Phase="Pending", Reason="", readiness=false. Elapsed: 26.749791621s
Jun  3 16:15:27.965: INFO: Pod "pod-subpath-test-dynamicpv-fkx6": Phase="Pending", Reason="", readiness=false. Elapsed: 28.802435204s
Jun  3 16:15:30.018: INFO: Pod "pod-subpath-test-dynamicpv-fkx6": Phase="Pending", Reason="", readiness=false. Elapsed: 30.855214521s
Jun  3 16:15:32.070: INFO: Pod "pod-subpath-test-dynamicpv-fkx6": Phase="Pending", Reason="", readiness=false. Elapsed: 32.907634091s
Jun  3 16:15:34.123: INFO: Pod "pod-subpath-test-dynamicpv-fkx6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.960238358s
STEP: Saw pod success
Jun  3 16:15:34.123: INFO: Pod "pod-subpath-test-dynamicpv-fkx6" satisfied condition "Succeeded or Failed"
Jun  3 16:15:34.175: INFO: Trying to get logs from node ip-172-20-54-51.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-fkx6 container test-container-subpath-dynamicpv-fkx6: <nil>
STEP: delete the pod
Jun  3 16:15:34.285: INFO: Waiting for pod pod-subpath-test-dynamicpv-fkx6 to disappear
Jun  3 16:15:34.336: INFO: Pod pod-subpath-test-dynamicpv-fkx6 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-fkx6
Jun  3 16:15:34.336: INFO: Deleting pod "pod-subpath-test-dynamicpv-fkx6" in namespace "provisioning-4603"
... skipping 101 lines ...
Jun  3 16:15:43.734: INFO: Waiting for pod aws-client to disappear
Jun  3 16:15:43.786: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun  3 16:15:43.786: INFO: Deleting PersistentVolumeClaim "pvc-brdlz"
Jun  3 16:15:43.838: INFO: Deleting PersistentVolume "aws-q6kdf"
Jun  3 16:15:44.206: INFO: Couldn't delete PD "aws://us-west-1a/vol-0a487195cb1288532", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a487195cb1288532 is currently attached to i-087802f1a3468fa04
	status code: 400, request id: db6879a2-054e-4a8c-a961-be55f0a44215
Jun  3 16:15:49.609: INFO: Couldn't delete PD "aws://us-west-1a/vol-0a487195cb1288532", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a487195cb1288532 is currently attached to i-087802f1a3468fa04
	status code: 400, request id: edafc724-8ad2-4e8b-9954-409e807e9b68
Jun  3 16:15:54.979: INFO: Successfully deleted PD "aws://us-west-1a/vol-0a487195cb1288532".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  3 16:15:54.980: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-2002" for this suite.
... skipping 85 lines ...

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

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

    /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:92
------------------------------
... skipping 169 lines ...
Jun  3 16:15:05.974: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-85408vhv9
STEP: creating a claim
Jun  3 16:15:06.026: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-7x68
STEP: Creating a pod to test atomic-volume-subpath
Jun  3 16:15:06.183: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-7x68" in namespace "provisioning-8540" to be "Succeeded or Failed"
Jun  3 16:15:06.234: INFO: Pod "pod-subpath-test-dynamicpv-7x68": Phase="Pending", Reason="", readiness=false. Elapsed: 51.292708ms
Jun  3 16:15:08.286: INFO: Pod "pod-subpath-test-dynamicpv-7x68": Phase="Pending", Reason="", readiness=false. Elapsed: 2.102795577s
Jun  3 16:15:10.337: INFO: Pod "pod-subpath-test-dynamicpv-7x68": Phase="Pending", Reason="", readiness=false. Elapsed: 4.154297202s
Jun  3 16:15:12.391: INFO: Pod "pod-subpath-test-dynamicpv-7x68": Phase="Pending", Reason="", readiness=false. Elapsed: 6.208042339s
Jun  3 16:15:14.444: INFO: Pod "pod-subpath-test-dynamicpv-7x68": Phase="Pending", Reason="", readiness=false. Elapsed: 8.260727406s
Jun  3 16:15:16.496: INFO: Pod "pod-subpath-test-dynamicpv-7x68": Phase="Pending", Reason="", readiness=false. Elapsed: 10.312774542s
... skipping 9 lines ...
Jun  3 16:15:37.032: INFO: Pod "pod-subpath-test-dynamicpv-7x68": Phase="Running", Reason="", readiness=true. Elapsed: 30.848793958s
Jun  3 16:15:39.089: INFO: Pod "pod-subpath-test-dynamicpv-7x68": Phase="Running", Reason="", readiness=true. Elapsed: 32.906594756s
Jun  3 16:15:41.143: INFO: Pod "pod-subpath-test-dynamicpv-7x68": Phase="Running", Reason="", readiness=true. Elapsed: 34.959767331s
Jun  3 16:15:43.199: INFO: Pod "pod-subpath-test-dynamicpv-7x68": Phase="Running", Reason="", readiness=true. Elapsed: 37.016303292s
Jun  3 16:15:45.253: INFO: Pod "pod-subpath-test-dynamicpv-7x68": Phase="Succeeded", Reason="", readiness=false. Elapsed: 39.069726301s
STEP: Saw pod success
Jun  3 16:15:45.253: INFO: Pod "pod-subpath-test-dynamicpv-7x68" satisfied condition "Succeeded or Failed"
Jun  3 16:15:45.304: INFO: Trying to get logs from node ip-172-20-56-152.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-7x68 container test-container-subpath-dynamicpv-7x68: <nil>
STEP: delete the pod
Jun  3 16:15:45.418: INFO: Waiting for pod pod-subpath-test-dynamicpv-7x68 to disappear
Jun  3 16:15:45.469: INFO: Pod pod-subpath-test-dynamicpv-7x68 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-7x68
Jun  3 16:15:45.469: INFO: Deleting pod "pod-subpath-test-dynamicpv-7x68" in namespace "provisioning-8540"
... skipping 321 lines ...
Jun  3 16:15:20.130: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1090-e2e-scb478g
STEP: creating a claim
Jun  3 16:15:20.183: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-82cj
STEP: Creating a pod to test subpath
Jun  3 16:15:20.341: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-82cj" in namespace "provisioning-1090" to be "Succeeded or Failed"
Jun  3 16:15:20.392: INFO: Pod "pod-subpath-test-dynamicpv-82cj": Phase="Pending", Reason="", readiness=false. Elapsed: 50.907814ms
Jun  3 16:15:22.445: INFO: Pod "pod-subpath-test-dynamicpv-82cj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.103531436s
Jun  3 16:15:24.497: INFO: Pod "pod-subpath-test-dynamicpv-82cj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.15549769s
Jun  3 16:15:26.548: INFO: Pod "pod-subpath-test-dynamicpv-82cj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.206817572s
Jun  3 16:15:28.600: INFO: Pod "pod-subpath-test-dynamicpv-82cj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.258342898s
Jun  3 16:15:30.652: INFO: Pod "pod-subpath-test-dynamicpv-82cj": Phase="Pending", Reason="", readiness=false. Elapsed: 10.310639759s
Jun  3 16:15:32.705: INFO: Pod "pod-subpath-test-dynamicpv-82cj": Phase="Pending", Reason="", readiness=false. Elapsed: 12.363245455s
Jun  3 16:15:34.757: INFO: Pod "pod-subpath-test-dynamicpv-82cj": Phase="Pending", Reason="", readiness=false. Elapsed: 14.415840339s
Jun  3 16:15:36.809: INFO: Pod "pod-subpath-test-dynamicpv-82cj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.467462499s
STEP: Saw pod success
Jun  3 16:15:36.809: INFO: Pod "pod-subpath-test-dynamicpv-82cj" satisfied condition "Succeeded or Failed"
Jun  3 16:15:36.868: INFO: Trying to get logs from node ip-172-20-61-108.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-82cj container test-container-subpath-dynamicpv-82cj: <nil>
STEP: delete the pod
Jun  3 16:15:36.978: INFO: Waiting for pod pod-subpath-test-dynamicpv-82cj to disappear
Jun  3 16:15:37.029: INFO: Pod pod-subpath-test-dynamicpv-82cj no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-82cj
Jun  3 16:15:37.029: INFO: Deleting pod "pod-subpath-test-dynamicpv-82cj" in namespace "provisioning-1090"
... skipping 39 lines ...
Jun  3 16:15:04.140: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-28-e2e-scmgmp9
STEP: creating a claim
Jun  3 16:15:04.192: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-568c
STEP: Creating a pod to test subpath
Jun  3 16:15:04.349: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-568c" in namespace "provisioning-28" to be "Succeeded or Failed"
Jun  3 16:15:04.400: INFO: Pod "pod-subpath-test-dynamicpv-568c": Phase="Pending", Reason="", readiness=false. Elapsed: 51.060844ms
Jun  3 16:15:06.452: INFO: Pod "pod-subpath-test-dynamicpv-568c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.103246013s
Jun  3 16:15:08.505: INFO: Pod "pod-subpath-test-dynamicpv-568c": Phase="Pending", Reason="", readiness=false. Elapsed: 4.155947004s
Jun  3 16:15:10.557: INFO: Pod "pod-subpath-test-dynamicpv-568c": Phase="Pending", Reason="", readiness=false. Elapsed: 6.20746186s
Jun  3 16:15:12.618: INFO: Pod "pod-subpath-test-dynamicpv-568c": Phase="Pending", Reason="", readiness=false. Elapsed: 8.268547977s
Jun  3 16:15:14.669: INFO: Pod "pod-subpath-test-dynamicpv-568c": Phase="Pending", Reason="", readiness=false. Elapsed: 10.320110142s
... skipping 9 lines ...
Jun  3 16:15:35.217: INFO: Pod "pod-subpath-test-dynamicpv-568c": Phase="Pending", Reason="", readiness=false. Elapsed: 30.86806409s
Jun  3 16:15:37.269: INFO: Pod "pod-subpath-test-dynamicpv-568c": Phase="Pending", Reason="", readiness=false. Elapsed: 32.919663098s
Jun  3 16:15:39.321: INFO: Pod "pod-subpath-test-dynamicpv-568c": Phase="Pending", Reason="", readiness=false. Elapsed: 34.97181281s
Jun  3 16:15:41.373: INFO: Pod "pod-subpath-test-dynamicpv-568c": Phase="Pending", Reason="", readiness=false. Elapsed: 37.024243169s
Jun  3 16:15:43.426: INFO: Pod "pod-subpath-test-dynamicpv-568c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 39.076727142s
STEP: Saw pod success
Jun  3 16:15:43.426: INFO: Pod "pod-subpath-test-dynamicpv-568c" satisfied condition "Succeeded or Failed"
Jun  3 16:15:43.480: INFO: Trying to get logs from node ip-172-20-54-51.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-568c container test-container-volume-dynamicpv-568c: <nil>
STEP: delete the pod
Jun  3 16:15:43.591: INFO: Waiting for pod pod-subpath-test-dynamicpv-568c to disappear
Jun  3 16:15:43.642: INFO: Pod pod-subpath-test-dynamicpv-568c no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-568c
Jun  3 16:15:43.642: INFO: Deleting pod "pod-subpath-test-dynamicpv-568c" in namespace "provisioning-28"
... skipping 168 lines ...
Jun  3 16:15:50.596: INFO: Creating resource for dynamic PV
Jun  3 16:15:50.596: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-1613-e2e-scg5njr
STEP: creating a claim
STEP: Expanding non-expandable pvc
Jun  3 16:15:50.753: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun  3 16:15:50.857: INFO: Error updating pvc ebs.csi.aws.combnt76: PersistentVolumeClaim "ebs.csi.aws.combnt76" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1613-e2e-scg5njr",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun  3 16:16:21.068: INFO: Error updating pvc ebs.csi.aws.combnt76: PersistentVolumeClaim "ebs.csi.aws.combnt76" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 310 lines ...

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.asTGBjoOr/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.asTGBjoOr/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.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 219 lines ...
Jun  3 16:15:59.439: INFO: PersistentVolumeClaim pvc-686s9 found but phase is Pending instead of Bound.
Jun  3 16:16:01.491: INFO: PersistentVolumeClaim pvc-686s9 found and phase=Bound (6.212897081s)
Jun  3 16:16:01.491: INFO: Waiting up to 3m0s for PersistentVolume aws-gk94m to have phase Bound
Jun  3 16:16:01.546: INFO: PersistentVolume aws-gk94m found and phase=Bound (54.283703ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-vrzv
STEP: Creating a pod to test exec-volume-test
Jun  3 16:16:01.701: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-vrzv" in namespace "volume-6016" to be "Succeeded or Failed"
Jun  3 16:16:01.752: INFO: Pod "exec-volume-test-preprovisionedpv-vrzv": Phase="Pending", Reason="", readiness=false. Elapsed: 50.857908ms
Jun  3 16:16:03.804: INFO: Pod "exec-volume-test-preprovisionedpv-vrzv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.102420391s
Jun  3 16:16:05.856: INFO: Pod "exec-volume-test-preprovisionedpv-vrzv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.15455537s
Jun  3 16:16:07.907: INFO: Pod "exec-volume-test-preprovisionedpv-vrzv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.206284843s
Jun  3 16:16:09.960: INFO: Pod "exec-volume-test-preprovisionedpv-vrzv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.258835867s
Jun  3 16:16:12.011: INFO: Pod "exec-volume-test-preprovisionedpv-vrzv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.310312212s
STEP: Saw pod success
Jun  3 16:16:12.012: INFO: Pod "exec-volume-test-preprovisionedpv-vrzv" satisfied condition "Succeeded or Failed"
Jun  3 16:16:12.063: INFO: Trying to get logs from node ip-172-20-56-152.us-west-1.compute.internal pod exec-volume-test-preprovisionedpv-vrzv container exec-container-preprovisionedpv-vrzv: <nil>
STEP: delete the pod
Jun  3 16:16:12.176: INFO: Waiting for pod exec-volume-test-preprovisionedpv-vrzv to disappear
Jun  3 16:16:12.227: INFO: Pod exec-volume-test-preprovisionedpv-vrzv no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-vrzv
Jun  3 16:16:12.227: INFO: Deleting pod "exec-volume-test-preprovisionedpv-vrzv" in namespace "volume-6016"
STEP: Deleting pv and pvc
Jun  3 16:16:12.278: INFO: Deleting PersistentVolumeClaim "pvc-686s9"
Jun  3 16:16:12.333: INFO: Deleting PersistentVolume "aws-gk94m"
Jun  3 16:16:12.591: INFO: Couldn't delete PD "aws://us-west-1a/vol-04523b40370507e51", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04523b40370507e51 is currently attached to i-05d143d647948db9b
	status code: 400, request id: 1ce24355-9410-4e65-91a8-2d01b0ea3392
Jun  3 16:16:17.902: INFO: Couldn't delete PD "aws://us-west-1a/vol-04523b40370507e51", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04523b40370507e51 is currently attached to i-05d143d647948db9b
	status code: 400, request id: c66357e3-6d3a-4bf1-b700-64bd5111d303
Jun  3 16:16:23.273: INFO: Couldn't delete PD "aws://us-west-1a/vol-04523b40370507e51", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04523b40370507e51 is currently attached to i-05d143d647948db9b
	status code: 400, request id: 0f7ed056-468e-4ac4-86a4-6f36579aaa7c
Jun  3 16:16:28.637: INFO: Successfully deleted PD "aws://us-west-1a/vol-04523b40370507e51".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  3 16:16:28.637: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-6016" for this suite.
... skipping 87 lines ...
Jun  3 16:16:31.392: INFO: Waiting for pod aws-client to disappear
Jun  3 16:16:31.443: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun  3 16:16:31.443: INFO: Deleting PersistentVolumeClaim "pvc-nh4z4"
Jun  3 16:16:31.496: INFO: Deleting PersistentVolume "aws-v65m6"
Jun  3 16:16:31.701: INFO: Couldn't delete PD "aws://us-west-1a/vol-05bf1e5b02429a6df", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05bf1e5b02429a6df is currently attached to i-0bc50fa72c0564cf8
	status code: 400, request id: 9cf9b485-91cd-4d6c-9861-cca0fff7b185
Jun  3 16:16:37.083: INFO: Successfully deleted PD "aws://us-west-1a/vol-05bf1e5b02429a6df".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  3 16:16:37.083: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-7567" for this suite.
... skipping 83 lines ...
Jun  3 16:13:24.146: INFO: Creating resource for dynamic PV
Jun  3 16:13:24.147: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-9292-e2e-scmsvbg
STEP: creating a claim
Jun  3 16:13:24.200: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun  3 16:13:24.365: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-95mft" in namespace "snapshotting-9292" to be "Succeeded or Failed"
Jun  3 16:13:24.417: INFO: Pod "pvc-snapshottable-tester-95mft": Phase="Pending", Reason="", readiness=false. Elapsed: 51.811909ms
Jun  3 16:13:26.469: INFO: Pod "pvc-snapshottable-tester-95mft": Phase="Pending", Reason="", readiness=false. Elapsed: 2.104411713s
Jun  3 16:13:28.523: INFO: Pod "pvc-snapshottable-tester-95mft": Phase="Pending", Reason="", readiness=false. Elapsed: 4.158304862s
Jun  3 16:13:30.577: INFO: Pod "pvc-snapshottable-tester-95mft": Phase="Pending", Reason="", readiness=false. Elapsed: 6.212001411s
Jun  3 16:13:32.629: INFO: Pod "pvc-snapshottable-tester-95mft": Phase="Pending", Reason="", readiness=false. Elapsed: 8.264222953s
Jun  3 16:13:34.684: INFO: Pod "pvc-snapshottable-tester-95mft": Phase="Pending", Reason="", readiness=false. Elapsed: 10.31873558s
... skipping 3 lines ...
Jun  3 16:13:42.899: INFO: Pod "pvc-snapshottable-tester-95mft": Phase="Pending", Reason="", readiness=false. Elapsed: 18.534059923s
Jun  3 16:13:44.953: INFO: Pod "pvc-snapshottable-tester-95mft": Phase="Pending", Reason="", readiness=false. Elapsed: 20.588298332s
Jun  3 16:13:47.007: INFO: Pod "pvc-snapshottable-tester-95mft": Phase="Pending", Reason="", readiness=false. Elapsed: 22.641606632s
Jun  3 16:13:49.060: INFO: Pod "pvc-snapshottable-tester-95mft": Phase="Pending", Reason="", readiness=false. Elapsed: 24.694617748s
Jun  3 16:13:51.114: INFO: Pod "pvc-snapshottable-tester-95mft": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.748677808s
STEP: Saw pod success
Jun  3 16:13:51.114: INFO: Pod "pvc-snapshottable-tester-95mft" satisfied condition "Succeeded or Failed"
Jun  3 16:13:51.229: INFO: Pod pvc-snapshottable-tester-95mft has the following logs: 
Jun  3 16:13:51.229: INFO: Deleting pod "pvc-snapshottable-tester-95mft" in namespace "snapshotting-9292"
Jun  3 16:13:51.284: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-95mft" to be fully deleted
Jun  3 16:13:51.336: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comzww9q] to have phase Bound
Jun  3 16:13:51.388: INFO: PersistentVolumeClaim ebs.csi.aws.comzww9q found and phase=Bound (51.818159ms)
STEP: [init] checking the claim
... skipping 40 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.asTGBjoOr/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  3 16:14:53.596: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-b5kd2" in namespace "snapshotting-9292" to be "Succeeded or Failed"
Jun  3 16:14:53.648: INFO: Pod "pvc-snapshottable-data-tester-b5kd2": Phase="Pending", Reason="", readiness=false. Elapsed: 51.834016ms
Jun  3 16:14:55.701: INFO: Pod "pvc-snapshottable-data-tester-b5kd2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.105258068s
Jun  3 16:14:57.755: INFO: Pod "pvc-snapshottable-data-tester-b5kd2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.158700352s
Jun  3 16:14:59.807: INFO: Pod "pvc-snapshottable-data-tester-b5kd2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.210927023s
Jun  3 16:15:01.866: INFO: Pod "pvc-snapshottable-data-tester-b5kd2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.26979985s
Jun  3 16:15:03.918: INFO: Pod "pvc-snapshottable-data-tester-b5kd2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.322243509s
Jun  3 16:15:05.972: INFO: Pod "pvc-snapshottable-data-tester-b5kd2": Phase="Pending", Reason="", readiness=false. Elapsed: 12.376230961s
Jun  3 16:15:08.024: INFO: Pod "pvc-snapshottable-data-tester-b5kd2": Phase="Pending", Reason="", readiness=false. Elapsed: 14.428362741s
Jun  3 16:15:10.078: INFO: Pod "pvc-snapshottable-data-tester-b5kd2": Phase="Pending", Reason="", readiness=false. Elapsed: 16.481600463s
Jun  3 16:15:12.131: INFO: Pod "pvc-snapshottable-data-tester-b5kd2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.534920821s
STEP: Saw pod success
Jun  3 16:15:12.131: INFO: Pod "pvc-snapshottable-data-tester-b5kd2" satisfied condition "Succeeded or Failed"
Jun  3 16:15:12.239: INFO: Pod pvc-snapshottable-data-tester-b5kd2 has the following logs: 
Jun  3 16:15:12.239: INFO: Deleting pod "pvc-snapshottable-data-tester-b5kd2" in namespace "snapshotting-9292"
Jun  3 16:15:12.295: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-b5kd2" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun  3 16:15:50.559: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-9292 exec restored-pvc-tester-wmtt8 --namespace=snapshotting-9292 -- cat /mnt/test/data'
... skipping 265 lines ...
Jun  3 16:16:22.335: INFO: Creating resource for dynamic PV
Jun  3 16:16:22.335: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-96539lwx8
STEP: creating a claim
STEP: Expanding non-expandable pvc
Jun  3 16:16:22.493: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun  3 16:16:22.597: INFO: Error updating pvc awscfxnc: PersistentVolumeClaim "awscfxnc" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-96539lwx8",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:92
------------------------------
... skipping 58 lines ...
Jun  3 16:16:19.745: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-5453zfzg9
STEP: creating a claim
Jun  3 16:16:19.797: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-6ldw
STEP: Creating a pod to test exec-volume-test
Jun  3 16:16:19.955: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-6ldw" in namespace "volume-5453" to be "Succeeded or Failed"
Jun  3 16:16:20.009: INFO: Pod "exec-volume-test-dynamicpv-6ldw": Phase="Pending", Reason="", readiness=false. Elapsed: 53.596474ms
Jun  3 16:16:22.061: INFO: Pod "exec-volume-test-dynamicpv-6ldw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.105989337s
Jun  3 16:16:24.113: INFO: Pod "exec-volume-test-dynamicpv-6ldw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.158313981s
Jun  3 16:16:26.165: INFO: Pod "exec-volume-test-dynamicpv-6ldw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.209997164s
Jun  3 16:16:28.217: INFO: Pod "exec-volume-test-dynamicpv-6ldw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.262420652s
Jun  3 16:16:30.270: INFO: Pod "exec-volume-test-dynamicpv-6ldw": Phase="Pending", Reason="", readiness=false. Elapsed: 10.315368909s
Jun  3 16:16:32.323: INFO: Pod "exec-volume-test-dynamicpv-6ldw": Phase="Pending", Reason="", readiness=false. Elapsed: 12.36763545s
Jun  3 16:16:34.375: INFO: Pod "exec-volume-test-dynamicpv-6ldw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.42006073s
STEP: Saw pod success
Jun  3 16:16:34.377: INFO: Pod "exec-volume-test-dynamicpv-6ldw" satisfied condition "Succeeded or Failed"
Jun  3 16:16:34.428: INFO: Trying to get logs from node ip-172-20-56-152.us-west-1.compute.internal pod exec-volume-test-dynamicpv-6ldw container exec-container-dynamicpv-6ldw: <nil>
STEP: delete the pod
Jun  3 16:16:34.536: INFO: Waiting for pod exec-volume-test-dynamicpv-6ldw to disappear
Jun  3 16:16:34.587: INFO: Pod exec-volume-test-dynamicpv-6ldw no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-6ldw
Jun  3 16:16:34.587: INFO: Deleting pod "exec-volume-test-dynamicpv-6ldw" in namespace "volume-5453"
... skipping 31 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.asTGBjoOr/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.asTGBjoOr/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.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 232 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  3 16:16:25.095: 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.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  3 16:16:25.357: INFO: Creating resource for dynamic PV
Jun  3 16:16:25.357: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-8779-e2e-sc7v9vb
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  3 16:16:31.726: INFO: Deleting pod "pod-255a35f6-4115-4c8d-8949-9019aff40179" in namespace "volumemode-8779"
Jun  3 16:16:31.778: INFO: Wait up to 5m0s for pod "pod-255a35f6-4115-4c8d-8949-9019aff40179" to be fully deleted
STEP: Deleting pvc
Jun  3 16:16:41.986: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comlbbmk"
Jun  3 16:16:42.043: INFO: Waiting up to 5m0s for PersistentVolume pvc-6153bc39-3faa-4ca4-8a90-7f40d96a0649 to get deleted
Jun  3 16:16:42.099: INFO: PersistentVolume pvc-6153bc39-3faa-4ca4-8a90-7f40d96a0649 found and phase=Released (56.217943ms)
... skipping 10 lines ...

• [SLOW TEST:37.388 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.asTGBjoOr/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.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 586 lines ...
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  3 16:17:20.302: 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.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Jun  3 16:17:20.612: INFO: found topology map[topology.kubernetes.io/zone:us-west-1a]
Jun  3 16:17:20.612: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  3 16:17:20.612: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.asTGBjoOr/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.asTGBjoOr/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (delayed binding)] topology
    /tmp/kops.asTGBjoOr/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.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.asTGBjoOr/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.asTGBjoOr/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.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 56 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  3 16:16:38.588: 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.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun  3 16:16:38.847: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  3 16:16:38.847: INFO: Creating resource for dynamic PV
Jun  3 16:16:38.847: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2126d4rjv
STEP: creating a claim
Jun  3 16:16:38.899: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-z6b5
STEP: Checking for subpath error in container status
Jun  3 16:17:01.160: INFO: Deleting pod "pod-subpath-test-dynamicpv-z6b5" in namespace "provisioning-2126"
Jun  3 16:17:01.213: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-z6b5" to be fully deleted
STEP: Deleting pod
Jun  3 16:17:13.317: INFO: Deleting pod "pod-subpath-test-dynamicpv-z6b5" in namespace "provisioning-2126"
STEP: Deleting pvc
Jun  3 16:17:13.473: INFO: Deleting PersistentVolumeClaim "aws4znz4"
... skipping 13 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.asTGBjoOr/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.asTGBjoOr/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.asTGBjoOr/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.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [sig-storage] Zone Support [Feature:vsphere]
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  3 16:17:28.904: INFO: >>> kubeConfig: /root/.kube/config
... skipping 77 lines ...
Jun  3 16:16:29.011: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  3 16:16:29.315: INFO: Successfully created a new PD: "aws://us-west-1a/vol-0df86bcd645cd7062".
Jun  3 16:16:29.315: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-6gpz
STEP: Creating a pod to test exec-volume-test
Jun  3 16:16:29.370: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-6gpz" in namespace "volume-763" to be "Succeeded or Failed"
Jun  3 16:16:29.422: INFO: Pod "exec-volume-test-inlinevolume-6gpz": Phase="Pending", Reason="", readiness=false. Elapsed: 52.660708ms
Jun  3 16:16:31.475: INFO: Pod "exec-volume-test-inlinevolume-6gpz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.104850665s
Jun  3 16:16:33.527: INFO: Pod "exec-volume-test-inlinevolume-6gpz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.156891536s
Jun  3 16:16:35.578: INFO: Pod "exec-volume-test-inlinevolume-6gpz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.208520381s
Jun  3 16:16:37.630: INFO: Pod "exec-volume-test-inlinevolume-6gpz": Phase="Pending", Reason="", readiness=false. Elapsed: 8.260198385s
Jun  3 16:16:39.682: INFO: Pod "exec-volume-test-inlinevolume-6gpz": Phase="Pending", Reason="", readiness=false. Elapsed: 10.312639778s
... skipping 7 lines ...
Jun  3 16:16:56.107: INFO: Pod "exec-volume-test-inlinevolume-6gpz": Phase="Pending", Reason="", readiness=false. Elapsed: 26.737417887s
Jun  3 16:16:58.160: INFO: Pod "exec-volume-test-inlinevolume-6gpz": Phase="Pending", Reason="", readiness=false. Elapsed: 28.790342357s
Jun  3 16:17:00.215: INFO: Pod "exec-volume-test-inlinevolume-6gpz": Phase="Pending", Reason="", readiness=false. Elapsed: 30.845337469s
Jun  3 16:17:02.267: INFO: Pod "exec-volume-test-inlinevolume-6gpz": Phase="Pending", Reason="", readiness=false. Elapsed: 32.896996408s
Jun  3 16:17:04.318: INFO: Pod "exec-volume-test-inlinevolume-6gpz": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.948539609s
STEP: Saw pod success
Jun  3 16:17:04.318: INFO: Pod "exec-volume-test-inlinevolume-6gpz" satisfied condition "Succeeded or Failed"
Jun  3 16:17:04.370: INFO: Trying to get logs from node ip-172-20-54-51.us-west-1.compute.internal pod exec-volume-test-inlinevolume-6gpz container exec-container-inlinevolume-6gpz: <nil>
STEP: delete the pod
Jun  3 16:17:04.479: INFO: Waiting for pod exec-volume-test-inlinevolume-6gpz to disappear
Jun  3 16:17:04.530: INFO: Pod exec-volume-test-inlinevolume-6gpz no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-6gpz
Jun  3 16:17:04.530: INFO: Deleting pod "exec-volume-test-inlinevolume-6gpz" in namespace "volume-763"
Jun  3 16:17:04.728: INFO: Couldn't delete PD "aws://us-west-1a/vol-0df86bcd645cd7062", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0df86bcd645cd7062 is currently attached to i-087802f1a3468fa04
	status code: 400, request id: 2b8ac22b-b30d-4d98-9b25-b9f384b28343
Jun  3 16:17:10.075: INFO: Couldn't delete PD "aws://us-west-1a/vol-0df86bcd645cd7062", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0df86bcd645cd7062 is currently attached to i-087802f1a3468fa04
	status code: 400, request id: 86091ef4-2aa0-4067-988b-eda9079e78bf
Jun  3 16:17:15.415: INFO: Couldn't delete PD "aws://us-west-1a/vol-0df86bcd645cd7062", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0df86bcd645cd7062 is currently attached to i-087802f1a3468fa04
	status code: 400, request id: a65399b6-6cba-47af-ac78-aff3d4c3d9fe
Jun  3 16:17:20.758: INFO: Couldn't delete PD "aws://us-west-1a/vol-0df86bcd645cd7062", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0df86bcd645cd7062 is currently attached to i-087802f1a3468fa04
	status code: 400, request id: 99376167-2763-45e4-986b-8ee8f1314cfe
Jun  3 16:17:26.076: INFO: Couldn't delete PD "aws://us-west-1a/vol-0df86bcd645cd7062", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0df86bcd645cd7062 is currently attached to i-087802f1a3468fa04
	status code: 400, request id: 1d6fd43b-b7b0-4546-a515-592cb4032bb4
Jun  3 16:17:31.454: INFO: Successfully deleted PD "aws://us-west-1a/vol-0df86bcd645cd7062".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  3 16:17:31.454: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-763" for this suite.
... skipping 20 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.asTGBjoOr/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.asTGBjoOr/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.asTGBjoOr/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.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Driver supports dynamic provisioning, skipping InlineVolume pattern

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

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

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

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

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 61 lines ...
Jun  3 16:17:36.594: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 390 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  3 16:17:03.996: 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.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  3 16:17:04.259: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  3 16:17:04.766: INFO: Successfully created a new PD: "aws://us-west-1a/vol-01778a025b0d6589e".
Jun  3 16:17:04.766: INFO: Creating resource for pre-provisioned PV
Jun  3 16:17:04.766: INFO: Creating PVC and PV
... skipping 7 lines ...
Jun  3 16:17:13.237: INFO: PersistentVolumeClaim pvc-n5spt found but phase is Pending instead of Bound.
Jun  3 16:17:15.291: INFO: PersistentVolumeClaim pvc-n5spt found but phase is Pending instead of Bound.
Jun  3 16:17:17.343: INFO: PersistentVolumeClaim pvc-n5spt found and phase=Bound (12.398060666s)
Jun  3 16:17:17.343: INFO: Waiting up to 3m0s for PersistentVolume aws-md7dc to have phase Bound
Jun  3 16:17:17.397: INFO: PersistentVolume aws-md7dc found and phase=Bound (53.799024ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  3 16:17:19.709: INFO: Deleting pod "pod-4704ef3c-3815-4a74-b6f7-6fa9c8918c7a" in namespace "volumemode-7149"
Jun  3 16:17:19.761: INFO: Wait up to 5m0s for pod "pod-4704ef3c-3815-4a74-b6f7-6fa9c8918c7a" to be fully deleted
STEP: Deleting pv and pvc
Jun  3 16:17:21.864: INFO: Deleting PersistentVolumeClaim "pvc-n5spt"
Jun  3 16:17:21.916: INFO: Deleting PersistentVolume "aws-md7dc"
Jun  3 16:17:22.134: INFO: Couldn't delete PD "aws://us-west-1a/vol-01778a025b0d6589e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01778a025b0d6589e is currently attached to i-0fa3526e84537dbe0
	status code: 400, request id: b9ded49b-884e-494d-8388-e09edff35bb2
Jun  3 16:17:27.537: INFO: Couldn't delete PD "aws://us-west-1a/vol-01778a025b0d6589e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01778a025b0d6589e is currently attached to i-0fa3526e84537dbe0
	status code: 400, request id: fc532665-e8f5-4e34-9619-b8f980d696fb
Jun  3 16:17:32.892: INFO: Couldn't delete PD "aws://us-west-1a/vol-01778a025b0d6589e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01778a025b0d6589e is currently attached to i-0fa3526e84537dbe0
	status code: 400, request id: f828d245-16f9-4b18-bb06-396ac3b9d7a6
Jun  3 16:17:38.300: INFO: Couldn't delete PD "aws://us-west-1a/vol-01778a025b0d6589e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01778a025b0d6589e is currently attached to i-0fa3526e84537dbe0
	status code: 400, request id: 5dd64150-bcd2-4e5a-81e6-e2850cc577ef
Jun  3 16:17:43.630: INFO: Couldn't delete PD "aws://us-west-1a/vol-01778a025b0d6589e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01778a025b0d6589e is currently attached to i-0fa3526e84537dbe0
	status code: 400, request id: 09a44184-be68-4eca-8c5a-7aea45c4c79e
Jun  3 16:17:49.022: INFO: Couldn't delete PD "aws://us-west-1a/vol-01778a025b0d6589e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01778a025b0d6589e is currently attached to i-0fa3526e84537dbe0
	status code: 400, request id: e17189b2-683e-48b0-bb70-810ea7d32c5e
Jun  3 16:17:54.388: INFO: Successfully deleted PD "aws://us-west-1a/vol-01778a025b0d6589e".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  3 16:17:54.388: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-7149" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.asTGBjoOr/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.asTGBjoOr/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
    /tmp/kops.asTGBjoOr/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.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 372 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.asTGBjoOr/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.asTGBjoOr/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.asTGBjoOr/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.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 68 lines ...
Jun  3 16:16:59.430: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2303-e2e-scwd84j
STEP: creating a claim
Jun  3 16:16:59.491: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-s567
STEP: Creating a pod to test atomic-volume-subpath
Jun  3 16:16:59.654: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-s567" in namespace "provisioning-2303" to be "Succeeded or Failed"
Jun  3 16:16:59.706: INFO: Pod "pod-subpath-test-dynamicpv-s567": Phase="Pending", Reason="", readiness=false. Elapsed: 51.783589ms
Jun  3 16:17:01.758: INFO: Pod "pod-subpath-test-dynamicpv-s567": Phase="Pending", Reason="", readiness=false. Elapsed: 2.104095507s
Jun  3 16:17:03.812: INFO: Pod "pod-subpath-test-dynamicpv-s567": Phase="Pending", Reason="", readiness=false. Elapsed: 4.157705907s
Jun  3 16:17:05.864: INFO: Pod "pod-subpath-test-dynamicpv-s567": Phase="Pending", Reason="", readiness=false. Elapsed: 6.210112242s
Jun  3 16:17:07.916: INFO: Pod "pod-subpath-test-dynamicpv-s567": Phase="Pending", Reason="", readiness=false. Elapsed: 8.262348888s
Jun  3 16:17:09.972: INFO: Pod "pod-subpath-test-dynamicpv-s567": Phase="Pending", Reason="", readiness=false. Elapsed: 10.317971964s
... skipping 7 lines ...
Jun  3 16:17:26.392: INFO: Pod "pod-subpath-test-dynamicpv-s567": Phase="Running", Reason="", readiness=true. Elapsed: 26.737832322s
Jun  3 16:17:28.444: INFO: Pod "pod-subpath-test-dynamicpv-s567": Phase="Running", Reason="", readiness=true. Elapsed: 28.789664442s
Jun  3 16:17:30.496: INFO: Pod "pod-subpath-test-dynamicpv-s567": Phase="Running", Reason="", readiness=true. Elapsed: 30.84210748s
Jun  3 16:17:32.548: INFO: Pod "pod-subpath-test-dynamicpv-s567": Phase="Running", Reason="", readiness=true. Elapsed: 32.893955267s
Jun  3 16:17:34.602: INFO: Pod "pod-subpath-test-dynamicpv-s567": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.947600622s
STEP: Saw pod success
Jun  3 16:17:34.604: INFO: Pod "pod-subpath-test-dynamicpv-s567" satisfied condition "Succeeded or Failed"
Jun  3 16:17:34.659: INFO: Trying to get logs from node ip-172-20-56-152.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-s567 container test-container-subpath-dynamicpv-s567: <nil>
STEP: delete the pod
Jun  3 16:17:34.776: INFO: Waiting for pod pod-subpath-test-dynamicpv-s567 to disappear
Jun  3 16:17:34.832: INFO: Pod pod-subpath-test-dynamicpv-s567 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-s567
Jun  3 16:17:34.832: INFO: Deleting pod "pod-subpath-test-dynamicpv-s567" in namespace "provisioning-2303"
... skipping 36 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.asTGBjoOr/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.asTGBjoOr/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.asTGBjoOr/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.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.asTGBjoOr/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.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.asTGBjoOr/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.asTGBjoOr/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.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 62 lines ...
Jun  3 16:17:31.829: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-19004wq9z
STEP: creating a claim
Jun  3 16:17:31.884: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-kxvf
STEP: Creating a pod to test subpath
Jun  3 16:17:32.044: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-kxvf" in namespace "provisioning-1900" to be "Succeeded or Failed"
Jun  3 16:17:32.099: INFO: Pod "pod-subpath-test-dynamicpv-kxvf": Phase="Pending", Reason="", readiness=false. Elapsed: 55.499118ms
Jun  3 16:17:34.152: INFO: Pod "pod-subpath-test-dynamicpv-kxvf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.107951897s
Jun  3 16:17:36.204: INFO: Pod "pod-subpath-test-dynamicpv-kxvf": Phase="Pending", Reason="", readiness=false. Elapsed: 4.159791721s
Jun  3 16:17:38.257: INFO: Pod "pod-subpath-test-dynamicpv-kxvf": Phase="Pending", Reason="", readiness=false. Elapsed: 6.2130754s
Jun  3 16:17:40.310: INFO: Pod "pod-subpath-test-dynamicpv-kxvf": Phase="Pending", Reason="", readiness=false. Elapsed: 8.265549456s
Jun  3 16:17:42.362: INFO: Pod "pod-subpath-test-dynamicpv-kxvf": Phase="Pending", Reason="", readiness=false. Elapsed: 10.317833224s
... skipping 2 lines ...
Jun  3 16:17:48.519: INFO: Pod "pod-subpath-test-dynamicpv-kxvf": Phase="Pending", Reason="", readiness=false. Elapsed: 16.475462826s
Jun  3 16:17:50.572: INFO: Pod "pod-subpath-test-dynamicpv-kxvf": Phase="Pending", Reason="", readiness=false. Elapsed: 18.52777058s
Jun  3 16:17:52.624: INFO: Pod "pod-subpath-test-dynamicpv-kxvf": Phase="Pending", Reason="", readiness=false. Elapsed: 20.579902883s
Jun  3 16:17:54.676: INFO: Pod "pod-subpath-test-dynamicpv-kxvf": Phase="Pending", Reason="", readiness=false. Elapsed: 22.632420415s
Jun  3 16:17:56.729: INFO: Pod "pod-subpath-test-dynamicpv-kxvf": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.684956556s
STEP: Saw pod success
Jun  3 16:17:56.729: INFO: Pod "pod-subpath-test-dynamicpv-kxvf" satisfied condition "Succeeded or Failed"
Jun  3 16:17:56.781: INFO: Trying to get logs from node ip-172-20-61-108.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-kxvf container test-container-subpath-dynamicpv-kxvf: <nil>
STEP: delete the pod
Jun  3 16:17:56.902: INFO: Waiting for pod pod-subpath-test-dynamicpv-kxvf to disappear
Jun  3 16:17:56.954: INFO: Pod pod-subpath-test-dynamicpv-kxvf no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-kxvf
Jun  3 16:17:56.954: INFO: Deleting pod "pod-subpath-test-dynamicpv-kxvf" in namespace "provisioning-1900"
... skipping 39 lines ...
Jun  3 16:16:53.341: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-9783zkhnc      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-9783    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-9783zkhnc,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-9783    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-9783zkhnc,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-9783    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-9783zkhnc,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-9783zkhnc    de1e11a0-aa2e-4781-a2a5-7d3c2e362910 8245 0 2021-06-03 16:16:53 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-03 16:16:53 +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-24hz7 pvc- provisioning-9783  5d697767-3746-4b46-882c-60fadc9503e3 8249 0 2021-06-03 16:16:53 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-03 16:16:53 +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-9783zkhnc,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-5642deac-9bb7-428b-935a-381ca743753c in namespace provisioning-9783
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun  3 16:17:07.933: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-ghxh9" in namespace "provisioning-9783" to be "Succeeded or Failed"
Jun  3 16:17:07.985: INFO: Pod "pvc-volume-tester-writer-ghxh9": Phase="Pending", Reason="", readiness=false. Elapsed: 51.857938ms
Jun  3 16:17:10.038: INFO: Pod "pvc-volume-tester-writer-ghxh9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.1046676s
Jun  3 16:17:12.091: INFO: Pod "pvc-volume-tester-writer-ghxh9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.158096122s
Jun  3 16:17:14.144: INFO: Pod "pvc-volume-tester-writer-ghxh9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.211472516s
Jun  3 16:17:16.197: INFO: Pod "pvc-volume-tester-writer-ghxh9": Phase="Pending", Reason="", readiness=false. Elapsed: 8.264480278s
Jun  3 16:17:18.249: INFO: Pod "pvc-volume-tester-writer-ghxh9": Phase="Pending", Reason="", readiness=false. Elapsed: 10.316328629s
... skipping 7 lines ...
Jun  3 16:17:34.672: INFO: Pod "pvc-volume-tester-writer-ghxh9": Phase="Pending", Reason="", readiness=false. Elapsed: 26.738592002s
Jun  3 16:17:36.724: INFO: Pod "pvc-volume-tester-writer-ghxh9": Phase="Pending", Reason="", readiness=false. Elapsed: 28.790921484s
Jun  3 16:17:38.776: INFO: Pod "pvc-volume-tester-writer-ghxh9": Phase="Pending", Reason="", readiness=false. Elapsed: 30.843509593s
Jun  3 16:17:40.829: INFO: Pod "pvc-volume-tester-writer-ghxh9": Phase="Pending", Reason="", readiness=false. Elapsed: 32.895591132s
Jun  3 16:17:42.882: INFO: Pod "pvc-volume-tester-writer-ghxh9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.949418559s
STEP: Saw pod success
Jun  3 16:17:42.882: INFO: Pod "pvc-volume-tester-writer-ghxh9" satisfied condition "Succeeded or Failed"
Jun  3 16:17:42.988: INFO: Pod pvc-volume-tester-writer-ghxh9 has the following logs: 
Jun  3 16:17:42.988: INFO: Deleting pod "pvc-volume-tester-writer-ghxh9" in namespace "provisioning-9783"
Jun  3 16:17:43.044: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-ghxh9" 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-54-51.us-west-1.compute.internal"
Jun  3 16:17:43.256: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-mtf96" in namespace "provisioning-9783" to be "Succeeded or Failed"
Jun  3 16:17:43.308: INFO: Pod "pvc-volume-tester-reader-mtf96": Phase="Pending", Reason="", readiness=false. Elapsed: 51.590621ms
Jun  3 16:17:45.361: INFO: Pod "pvc-volume-tester-reader-mtf96": Phase="Pending", Reason="", readiness=false. Elapsed: 2.104680405s
Jun  3 16:17:47.414: INFO: Pod "pvc-volume-tester-reader-mtf96": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.157202533s
STEP: Saw pod success
Jun  3 16:17:47.414: INFO: Pod "pvc-volume-tester-reader-mtf96" satisfied condition "Succeeded or Failed"
Jun  3 16:17:47.532: INFO: Pod pvc-volume-tester-reader-mtf96 has the following logs: hello world

Jun  3 16:17:47.532: INFO: Deleting pod "pvc-volume-tester-reader-mtf96" in namespace "provisioning-9783"
Jun  3 16:17:47.589: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-mtf96" to be fully deleted
Jun  3 16:17:47.641: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-24hz7] to have phase Bound
Jun  3 16:17:47.693: INFO: PersistentVolumeClaim pvc-24hz7 found and phase=Bound (51.614954ms)
... skipping 50 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  3 16:17:25.497: 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.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun  3 16:17:25.769: INFO: Creating resource for dynamic PV
Jun  3 16:17:25.769: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4215-e2e-sc4lnkn
STEP: creating a claim
Jun  3 16:17:25.822: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-7k7h
STEP: Checking for subpath error in container status
Jun  3 16:17:50.087: INFO: Deleting pod "pod-subpath-test-dynamicpv-7k7h" in namespace "provisioning-4215"
Jun  3 16:17:50.139: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-7k7h" to be fully deleted
STEP: Deleting pod
Jun  3 16:18:04.242: INFO: Deleting pod "pod-subpath-test-dynamicpv-7k7h" in namespace "provisioning-4215"
STEP: Deleting pvc
Jun  3 16:18:04.396: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comxb84z"
... skipping 10 lines ...

• [SLOW TEST:49.280 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath file is outside the volume [Slow][LinuxOnly]
    /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  3 16:18:14.779: INFO: Driver "ebs.csi.aws.com" does not support volume type "InlineVolume" - skipping
[AfterEach] [Testpattern: Inline-volume (default fs)] subPath
... skipping 37 lines ...
Jun  3 16:17:30.407: INFO: PersistentVolumeClaim pvc-fnr76 found but phase is Pending instead of Bound.
Jun  3 16:17:32.459: INFO: PersistentVolumeClaim pvc-fnr76 found and phase=Bound (10.31690549s)
Jun  3 16:17:32.459: INFO: Waiting up to 3m0s for PersistentVolume aws-pxt8b to have phase Bound
Jun  3 16:17:32.510: INFO: PersistentVolume aws-pxt8b found and phase=Bound (51.262788ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-5ppk
STEP: Creating a pod to test exec-volume-test
Jun  3 16:17:32.667: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-5ppk" in namespace "volume-395" to be "Succeeded or Failed"
Jun  3 16:17:32.718: INFO: Pod "exec-volume-test-preprovisionedpv-5ppk": Phase="Pending", Reason="", readiness=false. Elapsed: 51.220288ms
Jun  3 16:17:34.775: INFO: Pod "exec-volume-test-preprovisionedpv-5ppk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.107790121s
Jun  3 16:17:36.827: INFO: Pod "exec-volume-test-preprovisionedpv-5ppk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.160620097s
Jun  3 16:17:38.881: INFO: Pod "exec-volume-test-preprovisionedpv-5ppk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.213904035s
Jun  3 16:17:40.937: INFO: Pod "exec-volume-test-preprovisionedpv-5ppk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.270118819s
Jun  3 16:17:42.988: INFO: Pod "exec-volume-test-preprovisionedpv-5ppk": Phase="Pending", Reason="", readiness=false. Elapsed: 10.321536778s
Jun  3 16:17:45.040: INFO: Pod "exec-volume-test-preprovisionedpv-5ppk": Phase="Pending", Reason="", readiness=false. Elapsed: 12.37332017s
Jun  3 16:17:47.092: INFO: Pod "exec-volume-test-preprovisionedpv-5ppk": Phase="Pending", Reason="", readiness=false. Elapsed: 14.425084426s
Jun  3 16:17:49.144: INFO: Pod "exec-volume-test-preprovisionedpv-5ppk": Phase="Pending", Reason="", readiness=false. Elapsed: 16.476902356s
Jun  3 16:17:51.195: INFO: Pod "exec-volume-test-preprovisionedpv-5ppk": Phase="Pending", Reason="", readiness=false. Elapsed: 18.528646274s
Jun  3 16:17:53.256: INFO: Pod "exec-volume-test-preprovisionedpv-5ppk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.589634462s
STEP: Saw pod success
Jun  3 16:17:53.256: INFO: Pod "exec-volume-test-preprovisionedpv-5ppk" satisfied condition "Succeeded or Failed"
Jun  3 16:17:53.308: INFO: Trying to get logs from node ip-172-20-61-108.us-west-1.compute.internal pod exec-volume-test-preprovisionedpv-5ppk container exec-container-preprovisionedpv-5ppk: <nil>
STEP: delete the pod
Jun  3 16:17:53.419: INFO: Waiting for pod exec-volume-test-preprovisionedpv-5ppk to disappear
Jun  3 16:17:53.470: INFO: Pod exec-volume-test-preprovisionedpv-5ppk no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-5ppk
Jun  3 16:17:53.470: INFO: Deleting pod "exec-volume-test-preprovisionedpv-5ppk" in namespace "volume-395"
STEP: Deleting pv and pvc
Jun  3 16:17:53.524: INFO: Deleting PersistentVolumeClaim "pvc-fnr76"
Jun  3 16:17:53.576: INFO: Deleting PersistentVolume "aws-pxt8b"
Jun  3 16:17:53.789: INFO: Couldn't delete PD "aws://us-west-1a/vol-0eac86762a01af269", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0eac86762a01af269 is currently attached to i-0bc50fa72c0564cf8
	status code: 400, request id: 1abfdcb7-53ab-40bf-b486-0e343cbeb230
Jun  3 16:17:59.185: INFO: Couldn't delete PD "aws://us-west-1a/vol-0eac86762a01af269", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0eac86762a01af269 is currently attached to i-0bc50fa72c0564cf8
	status code: 400, request id: ea8ce579-4f5a-4fe1-a1e1-2bc547aa037b
Jun  3 16:18:04.559: INFO: Couldn't delete PD "aws://us-west-1a/vol-0eac86762a01af269", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0eac86762a01af269 is currently attached to i-0bc50fa72c0564cf8
	status code: 400, request id: 1d05fba7-8141-4f83-b2f7-6363fd53ad98
Jun  3 16:18:09.927: INFO: Couldn't delete PD "aws://us-west-1a/vol-0eac86762a01af269", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0eac86762a01af269 is currently attached to i-0bc50fa72c0564cf8
	status code: 400, request id: a6801cfa-104d-4350-9207-9442b15adb6b
Jun  3 16:18:15.312: INFO: Successfully deleted PD "aws://us-west-1a/vol-0eac86762a01af269".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  3 16:18:15.312: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-395" for this suite.
... skipping 117 lines ...
Jun  3 16:18:30.224: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 243 lines ...
Jun  3 16:18:16.079: INFO: Pod aws-client still exists
Jun  3 16:18:18.028: INFO: Waiting for pod aws-client to disappear
Jun  3 16:18:18.079: INFO: Pod aws-client still exists
Jun  3 16:18:20.028: INFO: Waiting for pod aws-client to disappear
Jun  3 16:18:20.079: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun  3 16:18:20.427: INFO: Couldn't delete PD "aws://us-west-1a/vol-04f5410537440143c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04f5410537440143c is currently attached to i-05d143d647948db9b
	status code: 400, request id: 17c5e2af-ff1e-4f1d-aa07-98638546de0f
Jun  3 16:18:25.772: INFO: Couldn't delete PD "aws://us-west-1a/vol-04f5410537440143c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04f5410537440143c is currently attached to i-05d143d647948db9b
	status code: 400, request id: 5843aafe-d84a-4c41-bb40-e4a9caef7eab
Jun  3 16:18:31.154: INFO: Couldn't delete PD "aws://us-west-1a/vol-04f5410537440143c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04f5410537440143c is currently attached to i-05d143d647948db9b
	status code: 400, request id: 3d72713b-7ef5-418c-a71a-0b423247a5a7
Jun  3 16:18:36.543: INFO: Successfully deleted PD "aws://us-west-1a/vol-04f5410537440143c".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  3 16:18:36.544: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-4009" for this suite.
... skipping 110 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  3 16:17:54.496: 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.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun  3 16:17:54.754: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  3 16:17:54.754: INFO: Creating resource for dynamic PV
Jun  3 16:17:54.754: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5879866r7
STEP: creating a claim
Jun  3 16:17:54.806: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-qwzf
STEP: Checking for subpath error in container status
Jun  3 16:18:21.079: INFO: Deleting pod "pod-subpath-test-dynamicpv-qwzf" in namespace "provisioning-5879"
Jun  3 16:18:21.134: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-qwzf" to be fully deleted
STEP: Deleting pod
Jun  3 16:18:33.236: INFO: Deleting pod "pod-subpath-test-dynamicpv-qwzf" in namespace "provisioning-5879"
STEP: Deleting pvc
Jun  3 16:18:33.394: INFO: Deleting PersistentVolumeClaim "awsc2n2q"
... skipping 12 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.asTGBjoOr/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.asTGBjoOr/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.asTGBjoOr/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.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 95 lines ...
Jun  3 16:17:39.808: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5340-e2e-sc57dkw
STEP: creating a claim
Jun  3 16:17:39.860: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-pl9z
STEP: Creating a pod to test subpath
Jun  3 16:17:40.015: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-pl9z" in namespace "provisioning-5340" to be "Succeeded or Failed"
Jun  3 16:17:40.065: INFO: Pod "pod-subpath-test-dynamicpv-pl9z": Phase="Pending", Reason="", readiness=false. Elapsed: 50.127792ms
Jun  3 16:17:42.116: INFO: Pod "pod-subpath-test-dynamicpv-pl9z": Phase="Pending", Reason="", readiness=false. Elapsed: 2.101036687s
Jun  3 16:17:44.167: INFO: Pod "pod-subpath-test-dynamicpv-pl9z": Phase="Pending", Reason="", readiness=false. Elapsed: 4.152499148s
Jun  3 16:17:46.218: INFO: Pod "pod-subpath-test-dynamicpv-pl9z": Phase="Pending", Reason="", readiness=false. Elapsed: 6.20359169s
Jun  3 16:17:48.270: INFO: Pod "pod-subpath-test-dynamicpv-pl9z": Phase="Pending", Reason="", readiness=false. Elapsed: 8.254907294s
Jun  3 16:17:50.321: INFO: Pod "pod-subpath-test-dynamicpv-pl9z": Phase="Pending", Reason="", readiness=false. Elapsed: 10.306115958s
... skipping 3 lines ...
Jun  3 16:17:58.526: INFO: Pod "pod-subpath-test-dynamicpv-pl9z": Phase="Pending", Reason="", readiness=false. Elapsed: 18.510836169s
Jun  3 16:18:00.576: INFO: Pod "pod-subpath-test-dynamicpv-pl9z": Phase="Pending", Reason="", readiness=false. Elapsed: 20.561433329s
Jun  3 16:18:02.627: INFO: Pod "pod-subpath-test-dynamicpv-pl9z": Phase="Pending", Reason="", readiness=false. Elapsed: 22.612201399s
Jun  3 16:18:04.677: INFO: Pod "pod-subpath-test-dynamicpv-pl9z": Phase="Pending", Reason="", readiness=false. Elapsed: 24.662641609s
Jun  3 16:18:06.728: INFO: Pod "pod-subpath-test-dynamicpv-pl9z": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.713683616s
STEP: Saw pod success
Jun  3 16:18:06.728: INFO: Pod "pod-subpath-test-dynamicpv-pl9z" satisfied condition "Succeeded or Failed"
Jun  3 16:18:06.779: INFO: Trying to get logs from node ip-172-20-32-159.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-pl9z container test-container-subpath-dynamicpv-pl9z: <nil>
STEP: delete the pod
Jun  3 16:18:06.896: INFO: Waiting for pod pod-subpath-test-dynamicpv-pl9z to disappear
Jun  3 16:18:06.946: INFO: Pod pod-subpath-test-dynamicpv-pl9z no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-pl9z
Jun  3 16:18:06.946: INFO: Deleting pod "pod-subpath-test-dynamicpv-pl9z" in namespace "provisioning-5340"
STEP: Creating pod pod-subpath-test-dynamicpv-pl9z
STEP: Creating a pod to test subpath
Jun  3 16:18:07.048: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-pl9z" in namespace "provisioning-5340" to be "Succeeded or Failed"
Jun  3 16:18:07.098: INFO: Pod "pod-subpath-test-dynamicpv-pl9z": Phase="Pending", Reason="", readiness=false. Elapsed: 50.275573ms
Jun  3 16:18:09.150: INFO: Pod "pod-subpath-test-dynamicpv-pl9z": Phase="Pending", Reason="", readiness=false. Elapsed: 2.10203796s
Jun  3 16:18:11.201: INFO: Pod "pod-subpath-test-dynamicpv-pl9z": Phase="Pending", Reason="", readiness=false. Elapsed: 4.153336896s
Jun  3 16:18:13.252: INFO: Pod "pod-subpath-test-dynamicpv-pl9z": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.204276438s
STEP: Saw pod success
Jun  3 16:18:13.252: INFO: Pod "pod-subpath-test-dynamicpv-pl9z" satisfied condition "Succeeded or Failed"
Jun  3 16:18:13.305: INFO: Trying to get logs from node ip-172-20-32-159.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-pl9z container test-container-subpath-dynamicpv-pl9z: <nil>
STEP: delete the pod
Jun  3 16:18:13.414: INFO: Waiting for pod pod-subpath-test-dynamicpv-pl9z to disappear
Jun  3 16:18:13.466: INFO: Pod pod-subpath-test-dynamicpv-pl9z no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-pl9z
Jun  3 16:18:13.466: INFO: Deleting pod "pod-subpath-test-dynamicpv-pl9z" in namespace "provisioning-5340"
... skipping 334 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  3 16:18:15.424: 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.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun  3 16:18:15.682: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  3 16:18:15.682: INFO: Creating resource for dynamic PV
Jun  3 16:18:15.682: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9604bhfqq
STEP: creating a claim
Jun  3 16:18:15.735: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-nzfk
STEP: Checking for subpath error in container status
Jun  3 16:18:30.007: INFO: Deleting pod "pod-subpath-test-dynamicpv-nzfk" in namespace "provisioning-9604"
Jun  3 16:18:30.061: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-nzfk" to be fully deleted
STEP: Deleting pod
Jun  3 16:18:42.165: INFO: Deleting pod "pod-subpath-test-dynamicpv-nzfk" in namespace "provisioning-9604"
STEP: Deleting pvc
Jun  3 16:18:42.322: INFO: Deleting PersistentVolumeClaim "aws786zq"
... skipping 13 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.asTGBjoOr/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.asTGBjoOr/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath directory is outside the volume [Slow][LinuxOnly]
      /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned Snapshot (delete policy)] snapshottable[Feature:VolumeSnapshotDataSource]
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Pre-provisioned Snapshot (delete policy)] snapshottable[Feature:VolumeSnapshotDataSource]
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 6 lines ...
Jun  3 16:16:39.674: INFO: Creating resource for dynamic PV
Jun  3 16:16:39.674: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-5248-e2e-scm7k7w
STEP: creating a claim
Jun  3 16:16:39.727: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun  3 16:16:39.889: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-gbw62" in namespace "snapshotting-5248" to be "Succeeded or Failed"
Jun  3 16:16:39.941: INFO: Pod "pvc-snapshottable-tester-gbw62": Phase="Pending", Reason="", readiness=false. Elapsed: 52.064022ms
Jun  3 16:16:41.993: INFO: Pod "pvc-snapshottable-tester-gbw62": Phase="Pending", Reason="", readiness=false. Elapsed: 2.104237119s
Jun  3 16:16:44.046: INFO: Pod "pvc-snapshottable-tester-gbw62": Phase="Pending", Reason="", readiness=false. Elapsed: 4.156757934s
Jun  3 16:16:46.100: INFO: Pod "pvc-snapshottable-tester-gbw62": Phase="Pending", Reason="", readiness=false. Elapsed: 6.211457908s
Jun  3 16:16:48.154: INFO: Pod "pvc-snapshottable-tester-gbw62": Phase="Pending", Reason="", readiness=false. Elapsed: 8.265386444s
Jun  3 16:16:50.207: INFO: Pod "pvc-snapshottable-tester-gbw62": Phase="Pending", Reason="", readiness=false. Elapsed: 10.318452104s
Jun  3 16:16:52.261: INFO: Pod "pvc-snapshottable-tester-gbw62": Phase="Pending", Reason="", readiness=false. Elapsed: 12.371897804s
Jun  3 16:16:54.314: INFO: Pod "pvc-snapshottable-tester-gbw62": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.425414041s
STEP: Saw pod success
Jun  3 16:16:54.315: INFO: Pod "pvc-snapshottable-tester-gbw62" satisfied condition "Succeeded or Failed"
Jun  3 16:16:54.422: INFO: Pod pvc-snapshottable-tester-gbw62 has the following logs: 
Jun  3 16:16:54.422: INFO: Deleting pod "pvc-snapshottable-tester-gbw62" in namespace "snapshotting-5248"
Jun  3 16:16:54.494: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-gbw62" to be fully deleted
Jun  3 16:16:54.546: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comvtrkj] to have phase Bound
Jun  3 16:16:54.597: INFO: PersistentVolumeClaim ebs.csi.aws.comvtrkj found and phase=Bound (51.728263ms)
STEP: [init] checking the claim
... skipping 39 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.asTGBjoOr/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  3 16:17:18.390: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-pqls7" in namespace "snapshotting-5248" to be "Succeeded or Failed"
Jun  3 16:17:18.443: INFO: Pod "pvc-snapshottable-data-tester-pqls7": Phase="Pending", Reason="", readiness=false. Elapsed: 53.024017ms
Jun  3 16:17:20.496: INFO: Pod "pvc-snapshottable-data-tester-pqls7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.106044513s
Jun  3 16:17:22.550: INFO: Pod "pvc-snapshottable-data-tester-pqls7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.160010306s
Jun  3 16:17:24.604: INFO: Pod "pvc-snapshottable-data-tester-pqls7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.213359477s
Jun  3 16:17:26.657: INFO: Pod "pvc-snapshottable-data-tester-pqls7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.266852558s
Jun  3 16:17:28.711: INFO: Pod "pvc-snapshottable-data-tester-pqls7": Phase="Pending", Reason="", readiness=false. Elapsed: 10.320597752s
... skipping 7 lines ...
Jun  3 16:17:45.152: INFO: Pod "pvc-snapshottable-data-tester-pqls7": Phase="Pending", Reason="", readiness=false. Elapsed: 26.761678344s
Jun  3 16:17:47.205: INFO: Pod "pvc-snapshottable-data-tester-pqls7": Phase="Pending", Reason="", readiness=false. Elapsed: 28.814348831s
Jun  3 16:17:49.258: INFO: Pod "pvc-snapshottable-data-tester-pqls7": Phase="Pending", Reason="", readiness=false. Elapsed: 30.867489652s
Jun  3 16:17:51.310: INFO: Pod "pvc-snapshottable-data-tester-pqls7": Phase="Pending", Reason="", readiness=false. Elapsed: 32.92010064s
Jun  3 16:17:53.363: INFO: Pod "pvc-snapshottable-data-tester-pqls7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.972760437s
STEP: Saw pod success
Jun  3 16:17:53.363: INFO: Pod "pvc-snapshottable-data-tester-pqls7" satisfied condition "Succeeded or Failed"
Jun  3 16:17:53.475: INFO: Pod pvc-snapshottable-data-tester-pqls7 has the following logs: 
Jun  3 16:17:53.475: INFO: Deleting pod "pvc-snapshottable-data-tester-pqls7" in namespace "snapshotting-5248"
Jun  3 16:17:53.534: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-pqls7" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun  3 16:18:11.809: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-5248 exec restored-pvc-tester-kbmlj --namespace=snapshotting-5248 -- cat /mnt/test/data'
... skipping 227 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  3 16:18:13.391: 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.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun  3 16:18:13.653: INFO: Creating resource for dynamic PV
Jun  3 16:18:13.653: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8119-e2e-scv2wlj
STEP: creating a claim
Jun  3 16:18:13.705: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-bwch
STEP: Checking for subpath error in container status
Jun  3 16:18:37.968: INFO: Deleting pod "pod-subpath-test-dynamicpv-bwch" in namespace "provisioning-8119"
Jun  3 16:18:38.025: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-bwch" to be fully deleted
STEP: Deleting pod
Jun  3 16:18:50.139: INFO: Deleting pod "pod-subpath-test-dynamicpv-bwch" in namespace "provisioning-8119"
STEP: Deleting pvc
Jun  3 16:18:50.294: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com5jnpw"
... skipping 10 lines ...

• [SLOW TEST:47.277 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.asTGBjoOr/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.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  3 16:19:00.670: INFO: Driver supports dynamic provisioning, skipping InlineVolume pattern
[AfterEach] [Testpattern: Inline-volume (default fs)] subPath
... skipping 393 lines ...
Jun  3 16:18:54.862: INFO: Waiting for pod aws-client to disappear
Jun  3 16:18:54.916: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun  3 16:18:54.916: INFO: Deleting PersistentVolumeClaim "pvc-gt887"
Jun  3 16:18:54.970: INFO: Deleting PersistentVolume "aws-j64fh"
Jun  3 16:18:55.211: INFO: Couldn't delete PD "aws://us-west-1a/vol-04933068b8e535133", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04933068b8e535133 is currently attached to i-087802f1a3468fa04
	status code: 400, request id: 77c4cb09-7b28-41f1-86ef-c578b9c1077d
Jun  3 16:19:00.535: INFO: Couldn't delete PD "aws://us-west-1a/vol-04933068b8e535133", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04933068b8e535133 is currently attached to i-087802f1a3468fa04
	status code: 400, request id: e578972d-9a45-4146-8178-489f7c28bcb5
Jun  3 16:19:05.901: INFO: Successfully deleted PD "aws://us-west-1a/vol-04933068b8e535133".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumes
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  3 16:19:05.901: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-519" for this suite.
... skipping 108 lines ...
Jun  3 16:18:12.845: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  3 16:18:13.162: INFO: Successfully created a new PD: "aws://us-west-1a/vol-0f129299e80c6d0ef".
Jun  3 16:18:13.162: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-66vn
STEP: Creating a pod to test exec-volume-test
Jun  3 16:18:13.216: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-66vn" in namespace "volume-8422" to be "Succeeded or Failed"
Jun  3 16:18:13.268: INFO: Pod "exec-volume-test-inlinevolume-66vn": Phase="Pending", Reason="", readiness=false. Elapsed: 51.463683ms
Jun  3 16:18:15.320: INFO: Pod "exec-volume-test-inlinevolume-66vn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.103996538s
Jun  3 16:18:17.372: INFO: Pod "exec-volume-test-inlinevolume-66vn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.155375731s
Jun  3 16:18:19.423: INFO: Pod "exec-volume-test-inlinevolume-66vn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.206894116s
Jun  3 16:18:21.476: INFO: Pod "exec-volume-test-inlinevolume-66vn": Phase="Pending", Reason="", readiness=false. Elapsed: 8.259564149s
Jun  3 16:18:23.528: INFO: Pod "exec-volume-test-inlinevolume-66vn": Phase="Pending", Reason="", readiness=false. Elapsed: 10.311231579s
... skipping 8 lines ...
Jun  3 16:18:41.995: INFO: Pod "exec-volume-test-inlinevolume-66vn": Phase="Pending", Reason="", readiness=false. Elapsed: 28.778305913s
Jun  3 16:18:44.047: INFO: Pod "exec-volume-test-inlinevolume-66vn": Phase="Pending", Reason="", readiness=false. Elapsed: 30.83005132s
Jun  3 16:18:46.103: INFO: Pod "exec-volume-test-inlinevolume-66vn": Phase="Pending", Reason="", readiness=false. Elapsed: 32.886805297s
Jun  3 16:18:48.156: INFO: Pod "exec-volume-test-inlinevolume-66vn": Phase="Pending", Reason="", readiness=false. Elapsed: 34.939983262s
Jun  3 16:18:50.208: INFO: Pod "exec-volume-test-inlinevolume-66vn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 36.991232149s
STEP: Saw pod success
Jun  3 16:18:50.208: INFO: Pod "exec-volume-test-inlinevolume-66vn" satisfied condition "Succeeded or Failed"
Jun  3 16:18:50.259: INFO: Trying to get logs from node ip-172-20-32-159.us-west-1.compute.internal pod exec-volume-test-inlinevolume-66vn container exec-container-inlinevolume-66vn: <nil>
STEP: delete the pod
Jun  3 16:18:50.395: INFO: Waiting for pod exec-volume-test-inlinevolume-66vn to disappear
Jun  3 16:18:50.447: INFO: Pod exec-volume-test-inlinevolume-66vn no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-66vn
Jun  3 16:18:50.447: INFO: Deleting pod "exec-volume-test-inlinevolume-66vn" in namespace "volume-8422"
Jun  3 16:18:50.671: INFO: Couldn't delete PD "aws://us-west-1a/vol-0f129299e80c6d0ef", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f129299e80c6d0ef is currently attached to i-0fa3526e84537dbe0
	status code: 400, request id: 1afb0eb3-632f-444b-8562-dde1eeeadc54
Jun  3 16:18:56.007: INFO: Couldn't delete PD "aws://us-west-1a/vol-0f129299e80c6d0ef", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f129299e80c6d0ef is currently attached to i-0fa3526e84537dbe0
	status code: 400, request id: 27047442-0486-48c5-94be-347cc0b8227e
Jun  3 16:19:01.362: INFO: Couldn't delete PD "aws://us-west-1a/vol-0f129299e80c6d0ef", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f129299e80c6d0ef is currently attached to i-0fa3526e84537dbe0
	status code: 400, request id: 403e38ff-be06-4765-9a23-e8a2b0273faf
Jun  3 16:19:06.762: INFO: Successfully deleted PD "aws://us-west-1a/vol-0f129299e80c6d0ef".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  3 16:19:06.762: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8422" for this suite.
... skipping 197 lines ...
Jun  3 16:18:37.303: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  3 16:18:37.797: INFO: Successfully created a new PD: "aws://us-west-1a/vol-000496c9244e888ea".
Jun  3 16:18:37.797: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-xbq6
STEP: Creating a pod to test exec-volume-test
Jun  3 16:18:37.851: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-xbq6" in namespace "volume-7467" to be "Succeeded or Failed"
Jun  3 16:18:37.903: INFO: Pod "exec-volume-test-inlinevolume-xbq6": Phase="Pending", Reason="", readiness=false. Elapsed: 51.021796ms
Jun  3 16:18:39.954: INFO: Pod "exec-volume-test-inlinevolume-xbq6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.102497795s
Jun  3 16:18:42.006: INFO: Pod "exec-volume-test-inlinevolume-xbq6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.154079024s
Jun  3 16:18:44.058: INFO: Pod "exec-volume-test-inlinevolume-xbq6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.20683518s
Jun  3 16:18:46.110: INFO: Pod "exec-volume-test-inlinevolume-xbq6": Phase="Pending", Reason="", readiness=false. Elapsed: 8.258537837s
Jun  3 16:18:48.164: INFO: Pod "exec-volume-test-inlinevolume-xbq6": Phase="Pending", Reason="", readiness=false. Elapsed: 10.312542337s
Jun  3 16:18:50.216: INFO: Pod "exec-volume-test-inlinevolume-xbq6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.364589192s
STEP: Saw pod success
Jun  3 16:18:50.216: INFO: Pod "exec-volume-test-inlinevolume-xbq6" satisfied condition "Succeeded or Failed"
Jun  3 16:18:50.267: INFO: Trying to get logs from node ip-172-20-32-159.us-west-1.compute.internal pod exec-volume-test-inlinevolume-xbq6 container exec-container-inlinevolume-xbq6: <nil>
STEP: delete the pod
Jun  3 16:18:50.395: INFO: Waiting for pod exec-volume-test-inlinevolume-xbq6 to disappear
Jun  3 16:18:50.447: INFO: Pod exec-volume-test-inlinevolume-xbq6 no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-xbq6
Jun  3 16:18:50.447: INFO: Deleting pod "exec-volume-test-inlinevolume-xbq6" in namespace "volume-7467"
Jun  3 16:18:50.651: INFO: Couldn't delete PD "aws://us-west-1a/vol-000496c9244e888ea", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-000496c9244e888ea is currently attached to i-0fa3526e84537dbe0
	status code: 400, request id: 00f08db1-2639-4c39-aa14-e5a915c5b91d
Jun  3 16:18:55.980: INFO: Couldn't delete PD "aws://us-west-1a/vol-000496c9244e888ea", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-000496c9244e888ea is currently attached to i-0fa3526e84537dbe0
	status code: 400, request id: 9e66be95-4b0f-453f-96ca-589742a6b11f
Jun  3 16:19:01.334: INFO: Couldn't delete PD "aws://us-west-1a/vol-000496c9244e888ea", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-000496c9244e888ea is currently attached to i-0fa3526e84537dbe0
	status code: 400, request id: 63a79385-c9f9-4a48-b973-3e5252eb2a45
Jun  3 16:19:06.641: INFO: Couldn't delete PD "aws://us-west-1a/vol-000496c9244e888ea", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-000496c9244e888ea is currently attached to i-0fa3526e84537dbe0
	status code: 400, request id: 1944ed67-c8b0-4881-bf45-e8f6318682e1
Jun  3 16:19:12.007: INFO: Successfully deleted PD "aws://us-west-1a/vol-000496c9244e888ea".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  3 16:19:12.007: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-7467" for this suite.
... skipping 183 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.asTGBjoOr/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.asTGBjoOr/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.asTGBjoOr/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.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 104 lines ...
Jun  3 16:18:53.999: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-487844qsp
STEP: creating a claim
Jun  3 16:18:54.050: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-5nw5
STEP: Creating a pod to test subpath
Jun  3 16:18:54.210: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-5nw5" in namespace "provisioning-4878" to be "Succeeded or Failed"
Jun  3 16:18:54.262: INFO: Pod "pod-subpath-test-dynamicpv-5nw5": Phase="Pending", Reason="", readiness=false. Elapsed: 51.253281ms
Jun  3 16:18:56.314: INFO: Pod "pod-subpath-test-dynamicpv-5nw5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.103339114s
Jun  3 16:18:58.366: INFO: Pod "pod-subpath-test-dynamicpv-5nw5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.155804498s
Jun  3 16:19:00.419: INFO: Pod "pod-subpath-test-dynamicpv-5nw5": Phase="Pending", Reason="", readiness=false. Elapsed: 6.208808767s
Jun  3 16:19:02.472: INFO: Pod "pod-subpath-test-dynamicpv-5nw5": Phase="Pending", Reason="", readiness=false. Elapsed: 8.261892296s
Jun  3 16:19:04.524: INFO: Pod "pod-subpath-test-dynamicpv-5nw5": Phase="Pending", Reason="", readiness=false. Elapsed: 10.313876373s
Jun  3 16:19:06.576: INFO: Pod "pod-subpath-test-dynamicpv-5nw5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.365981481s
STEP: Saw pod success
Jun  3 16:19:06.577: INFO: Pod "pod-subpath-test-dynamicpv-5nw5" satisfied condition "Succeeded or Failed"
Jun  3 16:19:06.628: INFO: Trying to get logs from node ip-172-20-56-152.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-5nw5 container test-container-subpath-dynamicpv-5nw5: <nil>
STEP: delete the pod
Jun  3 16:19:06.766: INFO: Waiting for pod pod-subpath-test-dynamicpv-5nw5 to disappear
Jun  3 16:19:06.817: INFO: Pod pod-subpath-test-dynamicpv-5nw5 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-5nw5
Jun  3 16:19:06.817: INFO: Deleting pod "pod-subpath-test-dynamicpv-5nw5" in namespace "provisioning-4878"
... skipping 228 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.asTGBjoOr/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.asTGBjoOr/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.asTGBjoOr/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.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 72 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  3 16:18:36.659: 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.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun  3 16:18:36.917: INFO: Creating resource for dynamic PV
Jun  3 16:18:36.917: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5489-e2e-sc8qdbn
STEP: creating a claim
Jun  3 16:18:36.969: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-6mmw
STEP: Checking for subpath error in container status
Jun  3 16:19:15.229: INFO: Deleting pod "pod-subpath-test-dynamicpv-6mmw" in namespace "provisioning-5489"
Jun  3 16:19:15.280: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-6mmw" to be fully deleted
STEP: Deleting pod
Jun  3 16:19:21.383: INFO: Deleting pod "pod-subpath-test-dynamicpv-6mmw" in namespace "provisioning-5489"
STEP: Deleting pvc
Jun  3 16:19:21.536: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comzc7td"
... skipping 10 lines ...

• [SLOW TEST:55.247 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.asTGBjoOr/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.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  3 16:19:31.908: INFO: Driver ebs.csi.aws.com doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
... skipping 119 lines ...

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

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

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.asTGBjoOr/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.asTGBjoOr/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.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 164 lines ...
Jun  3 16:19:06.648: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-27295rcd8
STEP: creating a claim
Jun  3 16:19:06.700: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-rdfb
STEP: Creating a pod to test exec-volume-test
Jun  3 16:19:06.862: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-rdfb" in namespace "volume-2729" to be "Succeeded or Failed"
Jun  3 16:19:06.914: INFO: Pod "exec-volume-test-dynamicpv-rdfb": Phase="Pending", Reason="", readiness=false. Elapsed: 51.361025ms
Jun  3 16:19:08.966: INFO: Pod "exec-volume-test-dynamicpv-rdfb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.103487937s
Jun  3 16:19:11.019: INFO: Pod "exec-volume-test-dynamicpv-rdfb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.15615464s
Jun  3 16:19:13.071: INFO: Pod "exec-volume-test-dynamicpv-rdfb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.208408498s
Jun  3 16:19:15.123: INFO: Pod "exec-volume-test-dynamicpv-rdfb": Phase="Pending", Reason="", readiness=false. Elapsed: 8.260872781s
Jun  3 16:19:17.175: INFO: Pod "exec-volume-test-dynamicpv-rdfb": Phase="Pending", Reason="", readiness=false. Elapsed: 10.312632542s
... skipping 2 lines ...
Jun  3 16:19:23.330: INFO: Pod "exec-volume-test-dynamicpv-rdfb": Phase="Pending", Reason="", readiness=false. Elapsed: 16.467704026s
Jun  3 16:19:25.383: INFO: Pod "exec-volume-test-dynamicpv-rdfb": Phase="Pending", Reason="", readiness=false. Elapsed: 18.520848706s
Jun  3 16:19:27.435: INFO: Pod "exec-volume-test-dynamicpv-rdfb": Phase="Pending", Reason="", readiness=false. Elapsed: 20.572849475s
Jun  3 16:19:29.488: INFO: Pod "exec-volume-test-dynamicpv-rdfb": Phase="Pending", Reason="", readiness=false. Elapsed: 22.625301556s
Jun  3 16:19:31.540: INFO: Pod "exec-volume-test-dynamicpv-rdfb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.677999235s
STEP: Saw pod success
Jun  3 16:19:31.540: INFO: Pod "exec-volume-test-dynamicpv-rdfb" satisfied condition "Succeeded or Failed"
Jun  3 16:19:31.592: INFO: Trying to get logs from node ip-172-20-32-159.us-west-1.compute.internal pod exec-volume-test-dynamicpv-rdfb container exec-container-dynamicpv-rdfb: <nil>
STEP: delete the pod
Jun  3 16:19:31.707: INFO: Waiting for pod exec-volume-test-dynamicpv-rdfb to disappear
Jun  3 16:19:31.758: INFO: Pod exec-volume-test-dynamicpv-rdfb no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-rdfb
Jun  3 16:19:31.758: INFO: Deleting pod "exec-volume-test-dynamicpv-rdfb" in namespace "volume-2729"
... skipping 33 lines ...
Jun  3 16:16:28.748: INFO: Creating resource for dynamic PV
Jun  3 16:16:28.748: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-8921-e2e-sclb584
STEP: creating a claim
Jun  3 16:16:28.799: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun  3 16:16:28.955: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-tnlfs" in namespace "snapshotting-8921" to be "Succeeded or Failed"
Jun  3 16:16:29.019: INFO: Pod "pvc-snapshottable-tester-tnlfs": Phase="Pending", Reason="", readiness=false. Elapsed: 63.821823ms
Jun  3 16:16:31.070: INFO: Pod "pvc-snapshottable-tester-tnlfs": Phase="Pending", Reason="", readiness=false. Elapsed: 2.114522474s
Jun  3 16:16:33.122: INFO: Pod "pvc-snapshottable-tester-tnlfs": Phase="Pending", Reason="", readiness=false. Elapsed: 4.166537083s
Jun  3 16:16:35.172: INFO: Pod "pvc-snapshottable-tester-tnlfs": Phase="Pending", Reason="", readiness=false. Elapsed: 6.217090122s
Jun  3 16:16:37.223: INFO: Pod "pvc-snapshottable-tester-tnlfs": Phase="Pending", Reason="", readiness=false. Elapsed: 8.267723235s
Jun  3 16:16:39.273: INFO: Pod "pvc-snapshottable-tester-tnlfs": Phase="Pending", Reason="", readiness=false. Elapsed: 10.317971332s
Jun  3 16:16:41.325: INFO: Pod "pvc-snapshottable-tester-tnlfs": Phase="Pending", Reason="", readiness=false. Elapsed: 12.369473879s
Jun  3 16:16:43.379: INFO: Pod "pvc-snapshottable-tester-tnlfs": Phase="Pending", Reason="", readiness=false. Elapsed: 14.42365623s
Jun  3 16:16:45.429: INFO: Pod "pvc-snapshottable-tester-tnlfs": Phase="Pending", Reason="", readiness=false. Elapsed: 16.47418821s
Jun  3 16:16:47.480: INFO: Pod "pvc-snapshottable-tester-tnlfs": Phase="Pending", Reason="", readiness=false. Elapsed: 18.524801443s
Jun  3 16:16:49.531: INFO: Pod "pvc-snapshottable-tester-tnlfs": Phase="Pending", Reason="", readiness=false. Elapsed: 20.575809126s
Jun  3 16:16:51.584: INFO: Pod "pvc-snapshottable-tester-tnlfs": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.629290574s
STEP: Saw pod success
Jun  3 16:16:51.584: INFO: Pod "pvc-snapshottable-tester-tnlfs" satisfied condition "Succeeded or Failed"
Jun  3 16:16:51.687: INFO: Pod pvc-snapshottable-tester-tnlfs has the following logs: 
Jun  3 16:16:51.687: INFO: Deleting pod "pvc-snapshottable-tester-tnlfs" in namespace "snapshotting-8921"
Jun  3 16:16:51.744: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-tnlfs" to be fully deleted
Jun  3 16:16:51.794: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.com7lw7c] to have phase Bound
Jun  3 16:16:51.845: INFO: PersistentVolumeClaim ebs.csi.aws.com7lw7c found and phase=Bound (50.357303ms)
STEP: [init] checking the claim
... skipping 41 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.asTGBjoOr/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  3 16:17:19.633: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-d2bbs" in namespace "snapshotting-8921" to be "Succeeded or Failed"
Jun  3 16:17:19.684: INFO: Pod "pvc-snapshottable-data-tester-d2bbs": Phase="Pending", Reason="", readiness=false. Elapsed: 50.687191ms
Jun  3 16:17:21.734: INFO: Pod "pvc-snapshottable-data-tester-d2bbs": Phase="Pending", Reason="", readiness=false. Elapsed: 2.101127064s
Jun  3 16:17:23.785: INFO: Pod "pvc-snapshottable-data-tester-d2bbs": Phase="Pending", Reason="", readiness=false. Elapsed: 4.151437469s
Jun  3 16:17:25.837: INFO: Pod "pvc-snapshottable-data-tester-d2bbs": Phase="Pending", Reason="", readiness=false. Elapsed: 6.203790442s
Jun  3 16:17:27.887: INFO: Pod "pvc-snapshottable-data-tester-d2bbs": Phase="Pending", Reason="", readiness=false. Elapsed: 8.254334157s
Jun  3 16:17:29.946: INFO: Pod "pvc-snapshottable-data-tester-d2bbs": Phase="Pending", Reason="", readiness=false. Elapsed: 10.312994499s
... skipping 7 lines ...
Jun  3 16:17:46.356: INFO: Pod "pvc-snapshottable-data-tester-d2bbs": Phase="Pending", Reason="", readiness=false. Elapsed: 26.723251826s
Jun  3 16:17:48.407: INFO: Pod "pvc-snapshottable-data-tester-d2bbs": Phase="Pending", Reason="", readiness=false. Elapsed: 28.774027743s
Jun  3 16:17:50.459: INFO: Pod "pvc-snapshottable-data-tester-d2bbs": Phase="Pending", Reason="", readiness=false. Elapsed: 30.826126048s
Jun  3 16:17:52.510: INFO: Pod "pvc-snapshottable-data-tester-d2bbs": Phase="Pending", Reason="", readiness=false. Elapsed: 32.876890917s
Jun  3 16:17:54.562: INFO: Pod "pvc-snapshottable-data-tester-d2bbs": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.929252836s
STEP: Saw pod success
Jun  3 16:17:54.562: INFO: Pod "pvc-snapshottable-data-tester-d2bbs" satisfied condition "Succeeded or Failed"
Jun  3 16:17:54.665: INFO: Pod pvc-snapshottable-data-tester-d2bbs has the following logs: 
Jun  3 16:17:54.665: INFO: Deleting pod "pvc-snapshottable-data-tester-d2bbs" in namespace "snapshotting-8921"
Jun  3 16:17:54.720: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-d2bbs" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun  3 16:18:18.985: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-8921 exec restored-pvc-tester-82nf6 --namespace=snapshotting-8921 -- cat /mnt/test/data'
... skipping 32 lines ...
Jun  3 16:18:44.038: INFO: volumesnapshotcontents pre-provisioned-snapcontent-b854acd1-d0f0-4da8-a5a0-7212a337352a has been found and is not deleted
Jun  3 16:18:45.089: INFO: volumesnapshotcontents pre-provisioned-snapcontent-b854acd1-d0f0-4da8-a5a0-7212a337352a has been found and is not deleted
Jun  3 16:18:46.140: INFO: volumesnapshotcontents pre-provisioned-snapcontent-b854acd1-d0f0-4da8-a5a0-7212a337352a has been found and is not deleted
Jun  3 16:18:47.191: INFO: volumesnapshotcontents pre-provisioned-snapcontent-b854acd1-d0f0-4da8-a5a0-7212a337352a has been found and is not deleted
Jun  3 16:18:48.243: INFO: volumesnapshotcontents pre-provisioned-snapcontent-b854acd1-d0f0-4da8-a5a0-7212a337352a has been found and is not deleted
Jun  3 16:18:49.293: INFO: volumesnapshotcontents pre-provisioned-snapcontent-b854acd1-d0f0-4da8-a5a0-7212a337352a has been found and is not deleted
Jun  3 16:18:50.294: INFO: WaitUntil failed after reaching the timeout 30s
[AfterEach] volume snapshot controller
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:221
Jun  3 16:18:50.346: INFO: Pod restored-pvc-tester-82nf6 has the following logs: 
Jun  3 16:18:50.346: INFO: Deleting pod "restored-pvc-tester-82nf6" in namespace "snapshotting-8921"
Jun  3 16:18:50.403: INFO: Wait up to 5m0s for pod "restored-pvc-tester-82nf6" to be fully deleted
Jun  3 16:19:34.503: INFO: deleting claim "snapshotting-8921"/"pvc-zhxzc"
... skipping 242 lines ...
Jun  3 16:19:17.707: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-992262zq2
STEP: creating a claim
Jun  3 16:19:17.763: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Jun  3 16:19:17.867: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun  3 16:19:17.986: INFO: Error updating pvc awsg9zjt: PersistentVolumeClaim "awsg9zjt" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-992262zq2",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun  3 16:19:48.199: INFO: Error updating pvc awsg9zjt: PersistentVolumeClaim "awsg9zjt" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 475 lines ...
Jun  3 16:19:04.997: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-6479-e2e-sc2s72m
STEP: creating a claim
Jun  3 16:19:05.049: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-j5z9
STEP: Creating a pod to test exec-volume-test
Jun  3 16:19:05.208: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-j5z9" in namespace "volume-6479" to be "Succeeded or Failed"
Jun  3 16:19:05.259: INFO: Pod "exec-volume-test-dynamicpv-j5z9": Phase="Pending", Reason="", readiness=false. Elapsed: 51.370923ms
Jun  3 16:19:07.312: INFO: Pod "exec-volume-test-dynamicpv-j5z9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.103568295s
Jun  3 16:19:09.364: INFO: Pod "exec-volume-test-dynamicpv-j5z9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.155553274s
Jun  3 16:19:11.417: INFO: Pod "exec-volume-test-dynamicpv-j5z9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.209307241s
Jun  3 16:19:13.470: INFO: Pod "exec-volume-test-dynamicpv-j5z9": Phase="Pending", Reason="", readiness=false. Elapsed: 8.262190484s
Jun  3 16:19:15.522: INFO: Pod "exec-volume-test-dynamicpv-j5z9": Phase="Pending", Reason="", readiness=false. Elapsed: 10.313907799s
Jun  3 16:19:17.575: INFO: Pod "exec-volume-test-dynamicpv-j5z9": Phase="Pending", Reason="", readiness=false. Elapsed: 12.367317152s
Jun  3 16:19:19.628: INFO: Pod "exec-volume-test-dynamicpv-j5z9": Phase="Pending", Reason="", readiness=false. Elapsed: 14.419657317s
Jun  3 16:19:21.679: INFO: Pod "exec-volume-test-dynamicpv-j5z9": Phase="Pending", Reason="", readiness=false. Elapsed: 16.471351027s
Jun  3 16:19:23.733: INFO: Pod "exec-volume-test-dynamicpv-j5z9": Phase="Pending", Reason="", readiness=false. Elapsed: 18.524635995s
Jun  3 16:19:25.785: INFO: Pod "exec-volume-test-dynamicpv-j5z9": Phase="Pending", Reason="", readiness=false. Elapsed: 20.576496976s
Jun  3 16:19:27.840: INFO: Pod "exec-volume-test-dynamicpv-j5z9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.631981087s
STEP: Saw pod success
Jun  3 16:19:27.840: INFO: Pod "exec-volume-test-dynamicpv-j5z9" satisfied condition "Succeeded or Failed"
Jun  3 16:19:27.892: INFO: Trying to get logs from node ip-172-20-32-159.us-west-1.compute.internal pod exec-volume-test-dynamicpv-j5z9 container exec-container-dynamicpv-j5z9: <nil>
STEP: delete the pod
Jun  3 16:19:28.267: INFO: Waiting for pod exec-volume-test-dynamicpv-j5z9 to disappear
Jun  3 16:19:28.318: INFO: Pod exec-volume-test-dynamicpv-j5z9 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-j5z9
Jun  3 16:19:28.318: INFO: Deleting pod "exec-volume-test-dynamicpv-j5z9" in namespace "volume-6479"
... skipping 58 lines ...
Jun  3 16:19:06.146: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-5210-e2e-scdmn9x
STEP: creating a claim
Jun  3 16:19:06.200: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-pjgg
STEP: Creating a pod to test exec-volume-test
Jun  3 16:19:06.360: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-pjgg" in namespace "volume-5210" to be "Succeeded or Failed"
Jun  3 16:19:06.412: INFO: Pod "exec-volume-test-dynamicpv-pjgg": Phase="Pending", Reason="", readiness=false. Elapsed: 51.564019ms
Jun  3 16:19:08.466: INFO: Pod "exec-volume-test-dynamicpv-pjgg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.105509655s
Jun  3 16:19:10.518: INFO: Pod "exec-volume-test-dynamicpv-pjgg": Phase="Pending", Reason="", readiness=false. Elapsed: 4.15763328s
Jun  3 16:19:12.577: INFO: Pod "exec-volume-test-dynamicpv-pjgg": Phase="Pending", Reason="", readiness=false. Elapsed: 6.217155525s
Jun  3 16:19:14.629: INFO: Pod "exec-volume-test-dynamicpv-pjgg": Phase="Pending", Reason="", readiness=false. Elapsed: 8.269261944s
Jun  3 16:19:16.683: INFO: Pod "exec-volume-test-dynamicpv-pjgg": Phase="Pending", Reason="", readiness=false. Elapsed: 10.322594737s
Jun  3 16:19:18.735: INFO: Pod "exec-volume-test-dynamicpv-pjgg": Phase="Pending", Reason="", readiness=false. Elapsed: 12.374687987s
Jun  3 16:19:20.787: INFO: Pod "exec-volume-test-dynamicpv-pjgg": Phase="Pending", Reason="", readiness=false. Elapsed: 14.427208647s
Jun  3 16:19:22.840: INFO: Pod "exec-volume-test-dynamicpv-pjgg": Phase="Pending", Reason="", readiness=false. Elapsed: 16.479658237s
Jun  3 16:19:24.893: INFO: Pod "exec-volume-test-dynamicpv-pjgg": Phase="Pending", Reason="", readiness=false. Elapsed: 18.533209231s
Jun  3 16:19:26.947: INFO: Pod "exec-volume-test-dynamicpv-pjgg": Phase="Pending", Reason="", readiness=false. Elapsed: 20.586642514s
Jun  3 16:19:29.002: INFO: Pod "exec-volume-test-dynamicpv-pjgg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.64165442s
STEP: Saw pod success
Jun  3 16:19:29.002: INFO: Pod "exec-volume-test-dynamicpv-pjgg" satisfied condition "Succeeded or Failed"
Jun  3 16:19:29.055: INFO: Trying to get logs from node ip-172-20-32-159.us-west-1.compute.internal pod exec-volume-test-dynamicpv-pjgg container exec-container-dynamicpv-pjgg: <nil>
STEP: delete the pod
Jun  3 16:19:29.172: INFO: Waiting for pod exec-volume-test-dynamicpv-pjgg to disappear
Jun  3 16:19:29.224: INFO: Pod exec-volume-test-dynamicpv-pjgg no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-pjgg
Jun  3 16:19:29.224: INFO: Deleting pod "exec-volume-test-dynamicpv-pjgg" in namespace "volume-5210"
... skipping 82 lines ...

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

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

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

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 212 lines ...
STEP: Deleting pod hostexec-ip-172-20-56-152.us-west-1.compute.internal-ks77l in namespace volumemode-1590
Jun  3 16:19:52.138: INFO: Deleting pod "pod-c8383ddb-c8e5-44cd-8e01-9e9ea4f33512" in namespace "volumemode-1590"
Jun  3 16:19:52.191: INFO: Wait up to 5m0s for pod "pod-c8383ddb-c8e5-44cd-8e01-9e9ea4f33512" to be fully deleted
STEP: Deleting pv and pvc
Jun  3 16:20:00.294: INFO: Deleting PersistentVolumeClaim "pvc-l9hrc"
Jun  3 16:20:00.346: INFO: Deleting PersistentVolume "aws-cpcqg"
Jun  3 16:20:00.630: INFO: Couldn't delete PD "aws://us-west-1a/vol-0ba8fb66dd6eb8017", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ba8fb66dd6eb8017 is currently attached to i-05d143d647948db9b
	status code: 400, request id: 8d4b8b18-13f6-415c-98b2-dd371498ad2f
Jun  3 16:20:05.999: INFO: Couldn't delete PD "aws://us-west-1a/vol-0ba8fb66dd6eb8017", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ba8fb66dd6eb8017 is currently attached to i-05d143d647948db9b
	status code: 400, request id: 4b8dbb6e-d8bb-40f3-a5f6-58e4c8594e86
Jun  3 16:20:11.336: INFO: Couldn't delete PD "aws://us-west-1a/vol-0ba8fb66dd6eb8017", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ba8fb66dd6eb8017 is currently attached to i-05d143d647948db9b
	status code: 400, request id: 2a26417f-66f3-43bf-a5b3-e1d7dfd94cd9
Jun  3 16:20:16.711: INFO: Successfully deleted PD "aws://us-west-1a/vol-0ba8fb66dd6eb8017".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  3 16:20:16.711: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-1590" for this suite.
... skipping 39 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.asTGBjoOr/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.asTGBjoOr/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.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 13 lines ...
Jun  3 16:19:29.379: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4964-e2e-sc45rcb
STEP: creating a claim
Jun  3 16:19:29.430: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-6lbx
STEP: Creating a pod to test subpath
Jun  3 16:19:29.588: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-6lbx" in namespace "provisioning-4964" to be "Succeeded or Failed"
Jun  3 16:19:29.639: INFO: Pod "pod-subpath-test-dynamicpv-6lbx": Phase="Pending", Reason="", readiness=false. Elapsed: 51.370877ms
Jun  3 16:19:31.692: INFO: Pod "pod-subpath-test-dynamicpv-6lbx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.104059194s
Jun  3 16:19:33.744: INFO: Pod "pod-subpath-test-dynamicpv-6lbx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.156385004s
Jun  3 16:19:35.796: INFO: Pod "pod-subpath-test-dynamicpv-6lbx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.207983555s
Jun  3 16:19:37.848: INFO: Pod "pod-subpath-test-dynamicpv-6lbx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.260393214s
Jun  3 16:19:39.903: INFO: Pod "pod-subpath-test-dynamicpv-6lbx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.315200796s
... skipping 3 lines ...
Jun  3 16:19:48.112: INFO: Pod "pod-subpath-test-dynamicpv-6lbx": Phase="Pending", Reason="", readiness=false. Elapsed: 18.523810866s
Jun  3 16:19:50.164: INFO: Pod "pod-subpath-test-dynamicpv-6lbx": Phase="Pending", Reason="", readiness=false. Elapsed: 20.576706821s
Jun  3 16:19:52.216: INFO: Pod "pod-subpath-test-dynamicpv-6lbx": Phase="Pending", Reason="", readiness=false. Elapsed: 22.628079366s
Jun  3 16:19:54.269: INFO: Pod "pod-subpath-test-dynamicpv-6lbx": Phase="Pending", Reason="", readiness=false. Elapsed: 24.681124539s
Jun  3 16:19:56.321: INFO: Pod "pod-subpath-test-dynamicpv-6lbx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.733762729s
STEP: Saw pod success
Jun  3 16:19:56.322: INFO: Pod "pod-subpath-test-dynamicpv-6lbx" satisfied condition "Succeeded or Failed"
Jun  3 16:19:56.373: INFO: Trying to get logs from node ip-172-20-32-159.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-6lbx container test-container-subpath-dynamicpv-6lbx: <nil>
STEP: delete the pod
Jun  3 16:19:56.491: INFO: Waiting for pod pod-subpath-test-dynamicpv-6lbx to disappear
Jun  3 16:19:56.542: INFO: Pod pod-subpath-test-dynamicpv-6lbx no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-6lbx
Jun  3 16:19:56.542: INFO: Deleting pod "pod-subpath-test-dynamicpv-6lbx" in namespace "provisioning-4964"
... skipping 233 lines ...
Jun  3 16:19:42.554: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7398-e2e-sccmnq2
STEP: creating a claim
Jun  3 16:19:42.606: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-bdtn
STEP: Creating a pod to test subpath
Jun  3 16:19:42.763: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-bdtn" in namespace "provisioning-7398" to be "Succeeded or Failed"
Jun  3 16:19:42.815: INFO: Pod "pod-subpath-test-dynamicpv-bdtn": Phase="Pending", Reason="", readiness=false. Elapsed: 51.83539ms
Jun  3 16:19:44.868: INFO: Pod "pod-subpath-test-dynamicpv-bdtn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.104261404s
Jun  3 16:19:46.919: INFO: Pod "pod-subpath-test-dynamicpv-bdtn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.155991469s
Jun  3 16:19:48.972: INFO: Pod "pod-subpath-test-dynamicpv-bdtn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.209018915s
Jun  3 16:19:51.031: INFO: Pod "pod-subpath-test-dynamicpv-bdtn": Phase="Pending", Reason="", readiness=false. Elapsed: 8.267579296s
Jun  3 16:19:53.090: INFO: Pod "pod-subpath-test-dynamicpv-bdtn": Phase="Pending", Reason="", readiness=false. Elapsed: 10.326164741s
... skipping 2 lines ...
Jun  3 16:19:59.249: INFO: Pod "pod-subpath-test-dynamicpv-bdtn": Phase="Pending", Reason="", readiness=false. Elapsed: 16.485282072s
Jun  3 16:20:01.301: INFO: Pod "pod-subpath-test-dynamicpv-bdtn": Phase="Pending", Reason="", readiness=false. Elapsed: 18.537878985s
Jun  3 16:20:03.356: INFO: Pod "pod-subpath-test-dynamicpv-bdtn": Phase="Pending", Reason="", readiness=false. Elapsed: 20.592105122s
Jun  3 16:20:05.408: INFO: Pod "pod-subpath-test-dynamicpv-bdtn": Phase="Pending", Reason="", readiness=false. Elapsed: 22.644589241s
Jun  3 16:20:07.461: INFO: Pod "pod-subpath-test-dynamicpv-bdtn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.697108816s
STEP: Saw pod success
Jun  3 16:20:07.461: INFO: Pod "pod-subpath-test-dynamicpv-bdtn" satisfied condition "Succeeded or Failed"
Jun  3 16:20:07.519: INFO: Trying to get logs from node ip-172-20-61-108.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-bdtn container test-container-volume-dynamicpv-bdtn: <nil>
STEP: delete the pod
Jun  3 16:20:07.698: INFO: Waiting for pod pod-subpath-test-dynamicpv-bdtn to disappear
Jun  3 16:20:07.752: INFO: Pod pod-subpath-test-dynamicpv-bdtn no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-bdtn
Jun  3 16:20:07.752: INFO: Deleting pod "pod-subpath-test-dynamicpv-bdtn" in namespace "provisioning-7398"
... skipping 295 lines ...
Jun  3 16:20:32.253: INFO: Waiting for pod aws-client to disappear
Jun  3 16:20:32.306: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun  3 16:20:32.306: INFO: Deleting PersistentVolumeClaim "pvc-4zxbw"
Jun  3 16:20:32.359: INFO: Deleting PersistentVolume "aws-8d6q2"
Jun  3 16:20:32.826: INFO: Couldn't delete PD "aws://us-west-1a/vol-09f7723b7c22ae610", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-09f7723b7c22ae610 is currently attached to i-0bc50fa72c0564cf8
	status code: 400, request id: 3cb04cf4-5c8c-4725-b64c-a7116fdeefd2
Jun  3 16:20:38.170: INFO: Couldn't delete PD "aws://us-west-1a/vol-09f7723b7c22ae610", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-09f7723b7c22ae610 is currently attached to i-0bc50fa72c0564cf8
	status code: 400, request id: b3db4bec-3308-4cb5-912f-5bd0e6a6de11
Jun  3 16:20:43.539: INFO: Successfully deleted PD "aws://us-west-1a/vol-09f7723b7c22ae610".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  3 16:20:43.539: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-7671" for this suite.
... skipping 237 lines ...
Jun  3 16:20:27.764: INFO: Pod aws-client still exists
Jun  3 16:20:29.711: INFO: Waiting for pod aws-client to disappear
Jun  3 16:20:29.763: INFO: Pod aws-client still exists
Jun  3 16:20:31.712: INFO: Waiting for pod aws-client to disappear
Jun  3 16:20:31.765: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun  3 16:20:32.160: INFO: Couldn't delete PD "aws://us-west-1a/vol-0b84e45dee43feaca", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0b84e45dee43feaca is currently attached to i-0bc50fa72c0564cf8
	status code: 400, request id: ce3f6cd4-8b46-4702-a528-201cb341403b
Jun  3 16:20:37.480: INFO: Couldn't delete PD "aws://us-west-1a/vol-0b84e45dee43feaca", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0b84e45dee43feaca is currently attached to i-0bc50fa72c0564cf8
	status code: 400, request id: 22c50f71-26a5-4f8b-9da8-e9cbad715a73
Jun  3 16:20:42.834: INFO: Couldn't delete PD "aws://us-west-1a/vol-0b84e45dee43feaca", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0b84e45dee43feaca is currently attached to i-0bc50fa72c0564cf8
	status code: 400, request id: e35d056c-cfb0-4089-b8e0-a046bbaf1d74
Jun  3 16:20:48.223: INFO: Couldn't delete PD "aws://us-west-1a/vol-0b84e45dee43feaca", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0b84e45dee43feaca is currently attached to i-0bc50fa72c0564cf8
	status code: 400, request id: ca975688-9c32-4570-8fdc-83e2f2e01d50
Jun  3 16:20:53.589: INFO: Successfully deleted PD "aws://us-west-1a/vol-0b84e45dee43feaca".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  3 16:20:53.589: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8865" for this suite.
... skipping 172 lines ...
Jun  3 16:20:06.792: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-9025-e2e-sc7skcb      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-9025    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-9025-e2e-sc7skcb,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-9025    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-9025-e2e-sc7skcb,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-9025    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-9025-e2e-sc7skcb,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-9025-e2e-sc7skcb    c24a2a06-98f7-4a99-a8de-f0ae6181608c 13999 0 2021-06-03 16:20:06 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-03 16:20:06 +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-hj4k5 pvc- provisioning-9025  cb5d5c81-a15f-42a2-ae50-162c7aa75f64 14000 0 2021-06-03 16:20:07 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-03 16:20:07 +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-9025-e2e-sc7skcb,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-005eadbf-a2e3-4163-8029-9e84d10cd334 in namespace provisioning-9025
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun  3 16:20:23.381: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-vx7ks" in namespace "provisioning-9025" to be "Succeeded or Failed"
Jun  3 16:20:23.434: INFO: Pod "pvc-volume-tester-writer-vx7ks": Phase="Pending", Reason="", readiness=false. Elapsed: 52.740433ms
Jun  3 16:20:25.487: INFO: Pod "pvc-volume-tester-writer-vx7ks": Phase="Pending", Reason="", readiness=false. Elapsed: 2.105791428s
Jun  3 16:20:27.541: INFO: Pod "pvc-volume-tester-writer-vx7ks": Phase="Pending", Reason="", readiness=false. Elapsed: 4.159363807s
Jun  3 16:20:29.594: INFO: Pod "pvc-volume-tester-writer-vx7ks": Phase="Pending", Reason="", readiness=false. Elapsed: 6.212834076s
Jun  3 16:20:31.651: INFO: Pod "pvc-volume-tester-writer-vx7ks": Phase="Pending", Reason="", readiness=false. Elapsed: 8.269742551s
Jun  3 16:20:33.703: INFO: Pod "pvc-volume-tester-writer-vx7ks": Phase="Pending", Reason="", readiness=false. Elapsed: 10.32211229s
... skipping 7 lines ...
Jun  3 16:20:50.140: INFO: Pod "pvc-volume-tester-writer-vx7ks": Phase="Pending", Reason="", readiness=false. Elapsed: 26.758645863s
Jun  3 16:20:52.194: INFO: Pod "pvc-volume-tester-writer-vx7ks": Phase="Pending", Reason="", readiness=false. Elapsed: 28.812338817s
Jun  3 16:20:54.249: INFO: Pod "pvc-volume-tester-writer-vx7ks": Phase="Pending", Reason="", readiness=false. Elapsed: 30.867599235s
Jun  3 16:20:56.302: INFO: Pod "pvc-volume-tester-writer-vx7ks": Phase="Pending", Reason="", readiness=false. Elapsed: 32.920746328s
Jun  3 16:20:58.357: INFO: Pod "pvc-volume-tester-writer-vx7ks": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.97523697s
STEP: Saw pod success
Jun  3 16:20:58.357: INFO: Pod "pvc-volume-tester-writer-vx7ks" satisfied condition "Succeeded or Failed"
Jun  3 16:20:58.492: INFO: Pod pvc-volume-tester-writer-vx7ks has the following logs: 
Jun  3 16:20:58.492: INFO: Deleting pod "pvc-volume-tester-writer-vx7ks" in namespace "provisioning-9025"
Jun  3 16:20:58.550: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-vx7ks" 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-54-51.us-west-1.compute.internal"
Jun  3 16:20:58.768: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-xhf45" in namespace "provisioning-9025" to be "Succeeded or Failed"
Jun  3 16:20:58.823: INFO: Pod "pvc-volume-tester-reader-xhf45": Phase="Pending", Reason="", readiness=false. Elapsed: 54.790318ms
Jun  3 16:21:00.876: INFO: Pod "pvc-volume-tester-reader-xhf45": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.107928211s
STEP: Saw pod success
Jun  3 16:21:00.876: INFO: Pod "pvc-volume-tester-reader-xhf45" satisfied condition "Succeeded or Failed"
Jun  3 16:21:00.984: INFO: Pod pvc-volume-tester-reader-xhf45 has the following logs: hello world

Jun  3 16:21:00.984: INFO: Deleting pod "pvc-volume-tester-reader-xhf45" in namespace "provisioning-9025"
Jun  3 16:21:01.043: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-xhf45" to be fully deleted
Jun  3 16:21:01.096: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-hj4k5] to have phase Bound
Jun  3 16:21:01.148: INFO: PersistentVolumeClaim pvc-hj4k5 found and phase=Bound (52.568145ms)
... skipping 415 lines ...
Jun  3 16:19:49.472: INFO: Creating resource for dynamic PV
Jun  3 16:19:49.472: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5582-e2e-scfx6j8
STEP: creating a claim
Jun  3 16:19:49.525: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-5582
Jun  3 16:19:49.681: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-5582" in namespace "provisioning-5582" to be "Succeeded or Failed"
Jun  3 16:19:49.733: INFO: Pod "volume-prep-provisioning-5582": Phase="Pending", Reason="", readiness=false. Elapsed: 51.04521ms
Jun  3 16:19:51.784: INFO: Pod "volume-prep-provisioning-5582": Phase="Pending", Reason="", readiness=false. Elapsed: 2.1024838s
Jun  3 16:19:53.840: INFO: Pod "volume-prep-provisioning-5582": Phase="Pending", Reason="", readiness=false. Elapsed: 4.158686436s
Jun  3 16:19:55.892: INFO: Pod "volume-prep-provisioning-5582": Phase="Pending", Reason="", readiness=false. Elapsed: 6.210229827s
Jun  3 16:19:57.944: INFO: Pod "volume-prep-provisioning-5582": Phase="Pending", Reason="", readiness=false. Elapsed: 8.26262161s
Jun  3 16:19:59.997: INFO: Pod "volume-prep-provisioning-5582": Phase="Pending", Reason="", readiness=false. Elapsed: 10.315978248s
... skipping 2 lines ...
Jun  3 16:20:06.157: INFO: Pod "volume-prep-provisioning-5582": Phase="Pending", Reason="", readiness=false. Elapsed: 16.475037669s
Jun  3 16:20:08.211: INFO: Pod "volume-prep-provisioning-5582": Phase="Pending", Reason="", readiness=false. Elapsed: 18.529068345s
Jun  3 16:20:10.264: INFO: Pod "volume-prep-provisioning-5582": Phase="Pending", Reason="", readiness=false. Elapsed: 20.582563814s
Jun  3 16:20:12.316: INFO: Pod "volume-prep-provisioning-5582": Phase="Pending", Reason="", readiness=false. Elapsed: 22.634069686s
Jun  3 16:20:14.367: INFO: Pod "volume-prep-provisioning-5582": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.685925597s
STEP: Saw pod success
Jun  3 16:20:14.369: INFO: Pod "volume-prep-provisioning-5582" satisfied condition "Succeeded or Failed"
Jun  3 16:20:14.369: INFO: Deleting pod "volume-prep-provisioning-5582" in namespace "provisioning-5582"
Jun  3 16:20:14.432: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-5582" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-f4rc
STEP: Checking for subpath error in container status
Jun  3 16:21:20.638: INFO: Deleting pod "pod-subpath-test-dynamicpv-f4rc" in namespace "provisioning-5582"
Jun  3 16:21:20.696: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-f4rc" to be fully deleted
STEP: Deleting pod
Jun  3 16:21:20.750: INFO: Deleting pod "pod-subpath-test-dynamicpv-f4rc" in namespace "provisioning-5582"
STEP: Deleting pvc
Jun  3 16:21:20.904: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comkcgps"
... skipping 123 lines ...
Jun  3 16:21:29.865: INFO: Pod aws-client still exists
Jun  3 16:21:31.812: INFO: Waiting for pod aws-client to disappear
Jun  3 16:21:31.864: INFO: Pod aws-client still exists
Jun  3 16:21:33.814: INFO: Waiting for pod aws-client to disappear
Jun  3 16:21:33.865: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun  3 16:21:34.235: INFO: Couldn't delete PD "aws://us-west-1a/vol-02acee2e41163db92", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02acee2e41163db92 is currently attached to i-0fa3526e84537dbe0
	status code: 400, request id: 91b575c2-9002-4c7f-a4a8-fdee18fe0f92
Jun  3 16:21:39.628: INFO: Successfully deleted PD "aws://us-west-1a/vol-02acee2e41163db92".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  3 16:21:39.628: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8595" for this suite.
... skipping 191 lines ...
    /tmp/kops.asTGBjoOr/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:320
------------------------------


Summarizing 1 Failure:

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

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


Ginkgo ran 1 suite in 10m15.450284227s
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
I0603 16:22:21.644052   26841 app.go:59] RunDir for this run: "/logs/artifacts/baa2b3fe-c484-11eb-92f3-12de509e7c48"
I0603 16:22:21.644230   26841 app.go:90] ID for this run: "baa2b3fe-c484-11eb-92f3-12de509e7c48"
I0603 16:22:21.644250   26841 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
I0603 16:22:21.662170   26847 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
... skipping 1499 lines ...