This job view page is being replaced by Spyglass soon. Check out the new job view.
PRrifelpet: Stop skipping snapshot fields tests in EBS CSI e2e
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-10-13 19:11
Elapsed34m19s
Revision2b2f0c146abbea685b69f4b28ab3fefb78bf3ad0
Refs 12531

No Test Failures!


Error lines from build-log.txt

... skipping 594 lines ...
I1013 19:17:53.276257   12582 app.go:90] ID for this run: "52afa3fa-2c59-11ec-a43b-3a3c05ae6ad7"
I1013 19:17:53.300561   12582 up.go:43] Cleaning up any leaked resources from previous cluster
I1013 19:17:53.300643   12582 dumplogs.go:40] /home/prow/go/src/k8s.io/kops/.bazelbuild/dist/linux/amd64/kops toolbox dump --name e2e-b6f7c24027-45100.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ubuntu
I1013 19:17:53.318519   12591 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1013 19:17:53.318593   12591 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I1013 19:17:53.318597   12591 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Error: Cluster.kops.k8s.io "e2e-b6f7c24027-45100.test-cncf-aws.k8s.io" not found
W1013 19:17:53.747192   12582 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I1013 19:17:53.747248   12582 down.go:48] /home/prow/go/src/k8s.io/kops/.bazelbuild/dist/linux/amd64/kops delete cluster --name e2e-b6f7c24027-45100.test-cncf-aws.k8s.io --yes
I1013 19:17:53.763752   12600 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1013 19:17:53.763835   12600 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I1013 19:17:53.763840   12600 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-b6f7c24027-45100.test-cncf-aws.k8s.io" not found
I1013 19:17:54.209052   12582 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/13 19:17:54 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
I1013 19:17:54.218160   12582 http.go:37] curl https://ip.jsb.workers.dev
I1013 19:17:54.362009   12582 up.go:144] /home/prow/go/src/k8s.io/kops/.bazelbuild/dist/linux/amd64/kops create cluster --name e2e-b6f7c24027-45100.test-cncf-aws.k8s.io --cloud aws --kubernetes-version 1.22.1 --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.69.29.75/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ca-central-1a --master-size c5.large
I1013 19:17:54.377447   12610 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1013 19:17:54.377953   12610 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I1013 19:17:54.377968   12610 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1013 19:17:54.398052   12610 create_cluster.go:838] Using SSH public key: /etc/aws-ssh/aws-ssh-public
... skipping 33 lines ...
I1013 19:18:38.908996   12582 up.go:181] /home/prow/go/src/k8s.io/kops/.bazelbuild/dist/linux/amd64/kops validate cluster --name e2e-b6f7c24027-45100.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I1013 19:18:38.925864   12632 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1013 19:18:38.925945   12632 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I1013 19:18:38.925949   12632 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-b6f7c24027-45100.test-cncf-aws.k8s.io

W1013 19:18:39.872389   12632 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-b6f7c24027-45100.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W1013 19:18:49.907141   12632 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-b6f7c24027-45100.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W1013 19:18:59.938272   12632 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W1013 19:19:09.969332   12632 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W1013 19:19:19.998269   12632 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W1013 19:19:30.029285   12632 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W1013 19:19:40.058843   12632 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W1013 19:19:50.120266   12632 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W1013 19:20:00.151745   12632 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W1013 19:20:10.198073   12632 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W1013 19:20:20.229399   12632 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W1013 19:20:30.278082   12632 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W1013 19:20:40.313467   12632 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W1013 19:20:50.354349   12632 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W1013 19:21:00.399212   12632 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W1013 19:21:10.437416   12632 validate_cluster.go:232] (will retry): cluster not yet healthy
W1013 19:21:20.463916   12632 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-b6f7c24027-45100.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W1013 19:21:30.496740   12632 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W1013 19:21:40.533009   12632 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W1013 19:21:50.584175   12632 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W1013 19:22:00.624427   12632 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 10 lines ...
Node	ip-172-20-44-168.ca-central-1.compute.internal	master "ip-172-20-44-168.ca-central-1.compute.internal" is missing kube-controller-manager pod
Pod	kube-system/coredns-6c8944dbdc-qp2jj		system-cluster-critical pod "coredns-6c8944dbdc-qp2jj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxhqz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxhqz" is pending
Pod	kube-system/ebs-csi-controller-54dc46fc7b-xwl4n	system-cluster-critical pod "ebs-csi-controller-54dc46fc7b-xwl4n" is pending
Pod	kube-system/ebs-csi-node-2bp7v			system-node-critical pod "ebs-csi-node-2bp7v" is pending

Validation Failed
W1013 19:22:11.881637   12632 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 8 lines ...
Machine	i-05786989bd674e173				machine "i-05786989bd674e173" has not yet joined cluster
Machine	i-0ffcb4d54aeaf8020				machine "i-0ffcb4d54aeaf8020" has not yet joined cluster
Node	ip-172-20-44-168.ca-central-1.compute.internal	master "ip-172-20-44-168.ca-central-1.compute.internal" is missing kube-controller-manager pod
Pod	kube-system/coredns-6c8944dbdc-qp2jj		system-cluster-critical pod "coredns-6c8944dbdc-qp2jj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxhqz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxhqz" is pending

Validation Failed
W1013 19:22:22.858784   12632 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 13 lines ...
Pod	kube-system/calico-node-vl5qb			system-node-critical pod "calico-node-vl5qb" is pending
Pod	kube-system/coredns-6c8944dbdc-qp2jj		system-cluster-critical pod "coredns-6c8944dbdc-qp2jj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxhqz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxhqz" is pending
Pod	kube-system/ebs-csi-node-cj7f5			system-node-critical pod "ebs-csi-node-cj7f5" is pending
Pod	kube-system/ebs-csi-node-cjd9c			system-node-critical pod "ebs-csi-node-cjd9c" is pending

Validation Failed
W1013 19:22:33.704771   12632 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 19 lines ...
Pod	kube-system/ebs-csi-node-b4zz7								system-node-critical pod "ebs-csi-node-b4zz7" is pending
Pod	kube-system/ebs-csi-node-cj7f5								system-node-critical pod "ebs-csi-node-cj7f5" is pending
Pod	kube-system/ebs-csi-node-cjd9c								system-node-critical pod "ebs-csi-node-cjd9c" is pending
Pod	kube-system/ebs-csi-node-cszbf								system-node-critical pod "ebs-csi-node-cszbf" is pending
Pod	kube-system/kube-controller-manager-ip-172-20-44-168.ca-central-1.compute.internal	system-cluster-critical pod "kube-controller-manager-ip-172-20-44-168.ca-central-1.compute.internal" is pending

Validation Failed
W1013 19:22:44.677517   12632 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 13 lines ...
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxhqz	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxhqz" is pending
Pod	kube-system/ebs-csi-node-b4zz7			system-node-critical pod "ebs-csi-node-b4zz7" is pending
Pod	kube-system/ebs-csi-node-cj7f5			system-node-critical pod "ebs-csi-node-cj7f5" is pending
Pod	kube-system/ebs-csi-node-cjd9c			system-node-critical pod "ebs-csi-node-cjd9c" is pending
Pod	kube-system/ebs-csi-node-cszbf			system-node-critical pod "ebs-csi-node-cszbf" is pending

Validation Failed
W1013 19:22:55.631426   12632 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
KIND	NAME					MESSAGE
Pod	kube-system/coredns-6c8944dbdc-5rh2h	system-cluster-critical pod "coredns-6c8944dbdc-5rh2h" is pending
Pod	kube-system/ebs-csi-node-b4zz7		system-node-critical pod "ebs-csi-node-b4zz7" is pending
Pod	kube-system/ebs-csi-node-cjd9c		system-node-critical pod "ebs-csi-node-cjd9c" is pending
Pod	kube-system/ebs-csi-node-cszbf		system-node-critical pod "ebs-csi-node-cszbf" is pending

Validation Failed
W1013 19:23:06.545708   12632 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 6 lines ...
ip-172-20-58-97.ca-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-proxy-ip-172-20-50-191.ca-central-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-50-191.ca-central-1.compute.internal" is pending

Validation Failed
W1013 19:23:17.501861   12632 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 6 lines ...
ip-172-20-58-97.ca-central-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-proxy-ip-172-20-38-144.ca-central-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-38-144.ca-central-1.compute.internal" is pending

Validation Failed
W1013 19:23:28.348690   12632 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 255 lines ...

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

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 277 lines ...

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

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

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

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

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 119 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.3EB0eDjiI/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.3EB0eDjiI/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.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 61 lines ...
STEP: Deleting pod hostexec-ip-172-20-58-97.ca-central-1.compute.internal-7z2vt in namespace volumemode-8630
Oct 13 19:26:57.311: INFO: Deleting pod "pod-f9ebc999-ca4a-4613-bd7d-ed078233edcd" in namespace "volumemode-8630"
Oct 13 19:26:57.343: INFO: Wait up to 5m0s for pod "pod-f9ebc999-ca4a-4613-bd7d-ed078233edcd" to be fully deleted
STEP: Deleting pv and pvc
Oct 13 19:27:03.404: INFO: Deleting PersistentVolumeClaim "pvc-pp7rg"
Oct 13 19:27:03.436: INFO: Deleting PersistentVolume "aws-nrkv8"
Oct 13 19:27:03.570: INFO: Couldn't delete PD "aws://ca-central-1a/vol-05fedce0a4032e158", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05fedce0a4032e158 is currently attached to i-00168f04de77a5ce5
	status code: 400, request id: 7c92e0c6-9fa2-421b-bec5-6b74f1dd4857
Oct 13 19:27:08.824: INFO: Couldn't delete PD "aws://ca-central-1a/vol-05fedce0a4032e158", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05fedce0a4032e158 is currently attached to i-00168f04de77a5ce5
	status code: 400, request id: 1f50c8e4-a644-4328-ab40-ef55b31ccf35
Oct 13 19:27:14.103: INFO: Successfully deleted PD "aws://ca-central-1a/vol-05fedce0a4032e158".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 19:27:14.103: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-8630" for this suite.
... skipping 181 lines ...
Oct 13 19:26:36.547: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3489bqrkn
STEP: creating a claim
Oct 13 19:26:36.578: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-thth
STEP: Creating a pod to test subpath
Oct 13 19:26:36.676: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-thth" in namespace "provisioning-3489" to be "Succeeded or Failed"
Oct 13 19:26:36.707: INFO: Pod "pod-subpath-test-dynamicpv-thth": Phase="Pending", Reason="", readiness=false. Elapsed: 30.788151ms
Oct 13 19:26:38.738: INFO: Pod "pod-subpath-test-dynamicpv-thth": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061879748s
Oct 13 19:26:40.771: INFO: Pod "pod-subpath-test-dynamicpv-thth": Phase="Pending", Reason="", readiness=false. Elapsed: 4.095245107s
Oct 13 19:26:42.807: INFO: Pod "pod-subpath-test-dynamicpv-thth": Phase="Pending", Reason="", readiness=false. Elapsed: 6.13053724s
Oct 13 19:26:44.838: INFO: Pod "pod-subpath-test-dynamicpv-thth": Phase="Pending", Reason="", readiness=false. Elapsed: 8.161999688s
Oct 13 19:26:46.870: INFO: Pod "pod-subpath-test-dynamicpv-thth": Phase="Pending", Reason="", readiness=false. Elapsed: 10.194274508s
Oct 13 19:26:48.903: INFO: Pod "pod-subpath-test-dynamicpv-thth": Phase="Pending", Reason="", readiness=false. Elapsed: 12.226944517s
Oct 13 19:26:50.935: INFO: Pod "pod-subpath-test-dynamicpv-thth": Phase="Pending", Reason="", readiness=false. Elapsed: 14.259319255s
Oct 13 19:26:52.968: INFO: Pod "pod-subpath-test-dynamicpv-thth": Phase="Pending", Reason="", readiness=false. Elapsed: 16.292037969s
Oct 13 19:26:55.000: INFO: Pod "pod-subpath-test-dynamicpv-thth": Phase="Pending", Reason="", readiness=false. Elapsed: 18.323953565s
Oct 13 19:26:57.032: INFO: Pod "pod-subpath-test-dynamicpv-thth": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.35603623s
STEP: Saw pod success
Oct 13 19:26:57.032: INFO: Pod "pod-subpath-test-dynamicpv-thth" satisfied condition "Succeeded or Failed"
Oct 13 19:26:57.064: INFO: Trying to get logs from node ip-172-20-58-97.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-thth container test-container-subpath-dynamicpv-thth: <nil>
STEP: delete the pod
Oct 13 19:26:57.293: INFO: Waiting for pod pod-subpath-test-dynamicpv-thth to disappear
Oct 13 19:26:57.326: INFO: Pod pod-subpath-test-dynamicpv-thth no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-thth
Oct 13 19:26:57.326: INFO: Deleting pod "pod-subpath-test-dynamicpv-thth" in namespace "provisioning-3489"
... skipping 44 lines ...
Oct 13 19:26:35.446: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-1658txf6r
STEP: creating a claim
Oct 13 19:26:35.477: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-cxg5
STEP: Creating a pod to test exec-volume-test
Oct 13 19:26:35.575: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-cxg5" in namespace "volume-1658" to be "Succeeded or Failed"
Oct 13 19:26:35.608: INFO: Pod "exec-volume-test-dynamicpv-cxg5": Phase="Pending", Reason="", readiness=false. Elapsed: 33.407391ms
Oct 13 19:26:37.640: INFO: Pod "exec-volume-test-dynamicpv-cxg5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.065092712s
Oct 13 19:26:39.671: INFO: Pod "exec-volume-test-dynamicpv-cxg5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.096002586s
Oct 13 19:26:41.703: INFO: Pod "exec-volume-test-dynamicpv-cxg5": Phase="Pending", Reason="", readiness=false. Elapsed: 6.128498684s
Oct 13 19:26:43.735: INFO: Pod "exec-volume-test-dynamicpv-cxg5": Phase="Pending", Reason="", readiness=false. Elapsed: 8.160393593s
Oct 13 19:26:45.766: INFO: Pod "exec-volume-test-dynamicpv-cxg5": Phase="Pending", Reason="", readiness=false. Elapsed: 10.191439944s
... skipping 3 lines ...
Oct 13 19:26:53.897: INFO: Pod "exec-volume-test-dynamicpv-cxg5": Phase="Pending", Reason="", readiness=false. Elapsed: 18.322450692s
Oct 13 19:26:55.928: INFO: Pod "exec-volume-test-dynamicpv-cxg5": Phase="Pending", Reason="", readiness=false. Elapsed: 20.353277937s
Oct 13 19:26:57.959: INFO: Pod "exec-volume-test-dynamicpv-cxg5": Phase="Pending", Reason="", readiness=false. Elapsed: 22.38423751s
Oct 13 19:26:59.990: INFO: Pod "exec-volume-test-dynamicpv-cxg5": Phase="Pending", Reason="", readiness=false. Elapsed: 24.415253709s
Oct 13 19:27:02.025: INFO: Pod "exec-volume-test-dynamicpv-cxg5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.449910491s
STEP: Saw pod success
Oct 13 19:27:02.025: INFO: Pod "exec-volume-test-dynamicpv-cxg5" satisfied condition "Succeeded or Failed"
Oct 13 19:27:02.056: INFO: Trying to get logs from node ip-172-20-50-163.ca-central-1.compute.internal pod exec-volume-test-dynamicpv-cxg5 container exec-container-dynamicpv-cxg5: <nil>
STEP: delete the pod
Oct 13 19:27:02.568: INFO: Waiting for pod exec-volume-test-dynamicpv-cxg5 to disappear
Oct 13 19:27:02.603: INFO: Pod exec-volume-test-dynamicpv-cxg5 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-cxg5
Oct 13 19:27:02.603: INFO: Deleting pod "exec-volume-test-dynamicpv-cxg5" in namespace "volume-1658"
... skipping 233 lines ...
Oct 13 19:27:22.075: INFO: Waiting for pod aws-client to disappear
Oct 13 19:27:22.106: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Oct 13 19:27:22.106: INFO: Deleting PersistentVolumeClaim "pvc-frkg5"
Oct 13 19:27:22.140: INFO: Deleting PersistentVolume "aws-6j555"
Oct 13 19:27:22.306: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0062cbe01f69c3d18", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0062cbe01f69c3d18 is currently attached to i-05786989bd674e173
	status code: 400, request id: f5241e94-f0a4-456d-b631-17def0f19bc5
Oct 13 19:27:27.555: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0062cbe01f69c3d18", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0062cbe01f69c3d18 is currently attached to i-05786989bd674e173
	status code: 400, request id: 1ec6a178-f1ce-49d6-ac26-a5b132f9e13b
Oct 13 19:27:32.809: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0062cbe01f69c3d18", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0062cbe01f69c3d18 is currently attached to i-05786989bd674e173
	status code: 400, request id: 3f0c4144-f86e-4496-a659-62be906bf2e4
Oct 13 19:27:38.070: INFO: Successfully deleted PD "aws://ca-central-1a/vol-0062cbe01f69c3d18".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 19:27:38.070: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-9922" for this suite.
... skipping 16 lines ...
STEP: Creating a kubernetes client
Oct 13 19:26:34.518: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename provisioning
W1013 19:26:34.993403   25280 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Oct 13 19:26:34.993: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly]
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Oct 13 19:26:35.055: INFO: Creating resource for dynamic PV
Oct 13 19:26:35.055: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3560-e2e-scglr7n
STEP: creating a claim
Oct 13 19:26:35.087: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-m2t7
STEP: Checking for subpath error in container status
Oct 13 19:27:01.288: INFO: Deleting pod "pod-subpath-test-dynamicpv-m2t7" in namespace "provisioning-3560"
Oct 13 19:27:01.326: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-m2t7" to be fully deleted
STEP: Deleting pod
Oct 13 19:27:05.387: INFO: Deleting pod "pod-subpath-test-dynamicpv-m2t7" in namespace "provisioning-3560"
STEP: Deleting pvc
Oct 13 19:27:05.482: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comtksrm"
... skipping 15 lines ...

• [SLOW TEST:66.391 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.3EB0eDjiI/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.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] provisioning
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] provisioning
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 694 lines ...
Oct 13 19:26:38.615: INFO: Creating resource for dynamic PV
Oct 13 19:26:38.615: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8293-e2e-sccvzqh
STEP: creating a claim
Oct 13 19:26:38.648: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-8293
Oct 13 19:26:38.745: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-8293" in namespace "provisioning-8293" to be "Succeeded or Failed"
Oct 13 19:26:38.776: INFO: Pod "volume-prep-provisioning-8293": Phase="Pending", Reason="", readiness=false. Elapsed: 31.118425ms
Oct 13 19:26:40.810: INFO: Pod "volume-prep-provisioning-8293": Phase="Pending", Reason="", readiness=false. Elapsed: 2.06484246s
Oct 13 19:26:42.842: INFO: Pod "volume-prep-provisioning-8293": Phase="Pending", Reason="", readiness=false. Elapsed: 4.096796638s
Oct 13 19:26:44.872: INFO: Pod "volume-prep-provisioning-8293": Phase="Pending", Reason="", readiness=false. Elapsed: 6.127499185s
Oct 13 19:26:46.904: INFO: Pod "volume-prep-provisioning-8293": Phase="Pending", Reason="", readiness=false. Elapsed: 8.158838916s
Oct 13 19:26:48.935: INFO: Pod "volume-prep-provisioning-8293": Phase="Pending", Reason="", readiness=false. Elapsed: 10.19057816s
Oct 13 19:26:50.966: INFO: Pod "volume-prep-provisioning-8293": Phase="Pending", Reason="", readiness=false. Elapsed: 12.221411977s
Oct 13 19:26:53.011: INFO: Pod "volume-prep-provisioning-8293": Phase="Pending", Reason="", readiness=false. Elapsed: 14.26577458s
Oct 13 19:26:55.043: INFO: Pod "volume-prep-provisioning-8293": Phase="Pending", Reason="", readiness=false. Elapsed: 16.297946346s
Oct 13 19:26:57.075: INFO: Pod "volume-prep-provisioning-8293": Phase="Pending", Reason="", readiness=false. Elapsed: 18.329927592s
Oct 13 19:26:59.110: INFO: Pod "volume-prep-provisioning-8293": Phase="Pending", Reason="", readiness=false. Elapsed: 20.365130885s
Oct 13 19:27:01.142: INFO: Pod "volume-prep-provisioning-8293": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.39718934s
STEP: Saw pod success
Oct 13 19:27:01.142: INFO: Pod "volume-prep-provisioning-8293" satisfied condition "Succeeded or Failed"
Oct 13 19:27:01.142: INFO: Deleting pod "volume-prep-provisioning-8293" in namespace "provisioning-8293"
Oct 13 19:27:01.178: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-8293" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-pg7k
STEP: Checking for subpath error in container status
Oct 13 19:27:39.303: INFO: Deleting pod "pod-subpath-test-dynamicpv-pg7k" in namespace "provisioning-8293"
Oct 13 19:27:39.339: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-pg7k" to be fully deleted
STEP: Deleting pod
Oct 13 19:27:39.371: INFO: Deleting pod "pod-subpath-test-dynamicpv-pg7k" in namespace "provisioning-8293"
STEP: Deleting pvc
Oct 13 19:27:39.466: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comh22ns"
... skipping 166 lines ...
Oct 13 19:27:38.300: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-87912x4rp
STEP: creating a claim
Oct 13 19:27:38.335: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-9vh4
STEP: Creating a pod to test exec-volume-test
Oct 13 19:27:38.429: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-9vh4" in namespace "volume-8791" to be "Succeeded or Failed"
Oct 13 19:27:38.460: INFO: Pod "exec-volume-test-dynamicpv-9vh4": Phase="Pending", Reason="", readiness=false. Elapsed: 30.738898ms
Oct 13 19:27:40.494: INFO: Pod "exec-volume-test-dynamicpv-9vh4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.064460626s
Oct 13 19:27:42.537: INFO: Pod "exec-volume-test-dynamicpv-9vh4": Phase="Pending", Reason="", readiness=false. Elapsed: 4.107893771s
Oct 13 19:27:44.569: INFO: Pod "exec-volume-test-dynamicpv-9vh4": Phase="Pending", Reason="", readiness=false. Elapsed: 6.13960862s
Oct 13 19:27:46.600: INFO: Pod "exec-volume-test-dynamicpv-9vh4": Phase="Pending", Reason="", readiness=false. Elapsed: 8.170731577s
Oct 13 19:27:48.632: INFO: Pod "exec-volume-test-dynamicpv-9vh4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.20283582s
STEP: Saw pod success
Oct 13 19:27:48.632: INFO: Pod "exec-volume-test-dynamicpv-9vh4" satisfied condition "Succeeded or Failed"
Oct 13 19:27:48.663: INFO: Trying to get logs from node ip-172-20-50-191.ca-central-1.compute.internal pod exec-volume-test-dynamicpv-9vh4 container exec-container-dynamicpv-9vh4: <nil>
STEP: delete the pod
Oct 13 19:27:48.733: INFO: Waiting for pod exec-volume-test-dynamicpv-9vh4 to disappear
Oct 13 19:27:48.764: INFO: Pod exec-volume-test-dynamicpv-9vh4 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-9vh4
Oct 13 19:27:48.764: INFO: Deleting pod "exec-volume-test-dynamicpv-9vh4" in namespace "volume-8791"
... skipping 154 lines ...
Oct 13 19:27:14.353: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5920-e2e-scxs52x
STEP: creating a claim
Oct 13 19:27:14.385: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-b7mf
STEP: Creating a pod to test subpath
Oct 13 19:27:14.480: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-b7mf" in namespace "provisioning-5920" to be "Succeeded or Failed"
Oct 13 19:27:14.511: INFO: Pod "pod-subpath-test-dynamicpv-b7mf": Phase="Pending", Reason="", readiness=false. Elapsed: 30.668862ms
Oct 13 19:27:16.542: INFO: Pod "pod-subpath-test-dynamicpv-b7mf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061999883s
Oct 13 19:27:18.574: INFO: Pod "pod-subpath-test-dynamicpv-b7mf": Phase="Pending", Reason="", readiness=false. Elapsed: 4.093464495s
Oct 13 19:27:20.604: INFO: Pod "pod-subpath-test-dynamicpv-b7mf": Phase="Pending", Reason="", readiness=false. Elapsed: 6.124061805s
Oct 13 19:27:22.635: INFO: Pod "pod-subpath-test-dynamicpv-b7mf": Phase="Pending", Reason="", readiness=false. Elapsed: 8.155007043s
Oct 13 19:27:24.667: INFO: Pod "pod-subpath-test-dynamicpv-b7mf": Phase="Pending", Reason="", readiness=false. Elapsed: 10.186549797s
... skipping 3 lines ...
Oct 13 19:27:32.805: INFO: Pod "pod-subpath-test-dynamicpv-b7mf": Phase="Pending", Reason="", readiness=false. Elapsed: 18.324686762s
Oct 13 19:27:34.837: INFO: Pod "pod-subpath-test-dynamicpv-b7mf": Phase="Pending", Reason="", readiness=false. Elapsed: 20.356854607s
Oct 13 19:27:36.870: INFO: Pod "pod-subpath-test-dynamicpv-b7mf": Phase="Pending", Reason="", readiness=false. Elapsed: 22.389563943s
Oct 13 19:27:38.901: INFO: Pod "pod-subpath-test-dynamicpv-b7mf": Phase="Pending", Reason="", readiness=false. Elapsed: 24.420842368s
Oct 13 19:27:40.933: INFO: Pod "pod-subpath-test-dynamicpv-b7mf": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.45260742s
STEP: Saw pod success
Oct 13 19:27:40.933: INFO: Pod "pod-subpath-test-dynamicpv-b7mf" satisfied condition "Succeeded or Failed"
Oct 13 19:27:40.963: INFO: Trying to get logs from node ip-172-20-38-144.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-b7mf container test-container-subpath-dynamicpv-b7mf: <nil>
STEP: delete the pod
Oct 13 19:27:41.035: INFO: Waiting for pod pod-subpath-test-dynamicpv-b7mf to disappear
Oct 13 19:27:41.066: INFO: Pod pod-subpath-test-dynamicpv-b7mf no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-b7mf
Oct 13 19:27:41.066: INFO: Deleting pod "pod-subpath-test-dynamicpv-b7mf" in namespace "provisioning-5920"
STEP: Creating pod pod-subpath-test-dynamicpv-b7mf
STEP: Creating a pod to test subpath
Oct 13 19:27:41.128: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-b7mf" in namespace "provisioning-5920" to be "Succeeded or Failed"
Oct 13 19:27:41.159: INFO: Pod "pod-subpath-test-dynamicpv-b7mf": Phase="Pending", Reason="", readiness=false. Elapsed: 30.341722ms
Oct 13 19:27:43.191: INFO: Pod "pod-subpath-test-dynamicpv-b7mf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062384818s
Oct 13 19:27:45.221: INFO: Pod "pod-subpath-test-dynamicpv-b7mf": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.093008855s
STEP: Saw pod success
Oct 13 19:27:45.222: INFO: Pod "pod-subpath-test-dynamicpv-b7mf" satisfied condition "Succeeded or Failed"
Oct 13 19:27:45.252: INFO: Trying to get logs from node ip-172-20-38-144.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-b7mf container test-container-subpath-dynamicpv-b7mf: <nil>
STEP: delete the pod
Oct 13 19:27:45.325: INFO: Waiting for pod pod-subpath-test-dynamicpv-b7mf to disappear
Oct 13 19:27:45.356: INFO: Pod pod-subpath-test-dynamicpv-b7mf no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-b7mf
Oct 13 19:27:45.356: INFO: Deleting pod "pod-subpath-test-dynamicpv-b7mf" in namespace "provisioning-5920"
... skipping 319 lines ...
STEP: Deleting pod hostexec-ip-172-20-50-191.ca-central-1.compute.internal-c5n5r in namespace volumemode-7326
Oct 13 19:27:55.981: INFO: Deleting pod "pod-5c65f188-74c1-4816-809f-4d3c37b87ac9" in namespace "volumemode-7326"
Oct 13 19:27:56.029: INFO: Wait up to 5m0s for pod "pod-5c65f188-74c1-4816-809f-4d3c37b87ac9" to be fully deleted
STEP: Deleting pv and pvc
Oct 13 19:27:58.092: INFO: Deleting PersistentVolumeClaim "pvc-rctrx"
Oct 13 19:27:58.123: INFO: Deleting PersistentVolume "aws-gw8np"
Oct 13 19:27:58.314: INFO: Couldn't delete PD "aws://ca-central-1a/vol-03b419824335875c0", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-03b419824335875c0 is currently attached to i-0ffcb4d54aeaf8020
	status code: 400, request id: 94ba7731-1def-477b-806d-b0a4857fd936
Oct 13 19:28:03.596: INFO: Couldn't delete PD "aws://ca-central-1a/vol-03b419824335875c0", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-03b419824335875c0 is currently attached to i-0ffcb4d54aeaf8020
	status code: 400, request id: 8d10d9e6-f8e4-4a9e-80c2-3ae024057d6c
Oct 13 19:28:08.884: INFO: Couldn't delete PD "aws://ca-central-1a/vol-03b419824335875c0", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-03b419824335875c0 is currently attached to i-0ffcb4d54aeaf8020
	status code: 400, request id: 4e7fefba-1dd5-42b2-a632-9f3d09c7d5c7
Oct 13 19:28:14.166: INFO: Successfully deleted PD "aws://ca-central-1a/vol-03b419824335875c0".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 19:28:14.166: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-7326" for this suite.
... skipping 235 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 19:27:30.999: 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.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Oct 13 19:27:31.153: INFO: Creating resource for dynamic PV
Oct 13 19:27:31.153: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5825-e2e-scnp9zc
STEP: creating a claim
Oct 13 19:27:31.186: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-nw98
STEP: Checking for subpath error in container status
Oct 13 19:27:55.343: INFO: Deleting pod "pod-subpath-test-dynamicpv-nw98" in namespace "provisioning-5825"
Oct 13 19:27:55.375: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-nw98" to be fully deleted
STEP: Deleting pod
Oct 13 19:27:59.438: INFO: Deleting pod "pod-subpath-test-dynamicpv-nw98" in namespace "provisioning-5825"
STEP: Deleting pvc
Oct 13 19:27:59.531: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com5vtlv"
... skipping 12 lines ...

• [SLOW TEST:48.837 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.3EB0eDjiI/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.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 68 lines ...
Oct 13 19:27:33.044: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-9407-e2e-sc82fkr
STEP: creating a claim
Oct 13 19:27:33.077: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-k5cj
STEP: Creating a pod to test exec-volume-test
Oct 13 19:27:33.174: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-k5cj" in namespace "volume-9407" to be "Succeeded or Failed"
Oct 13 19:27:33.217: INFO: Pod "exec-volume-test-dynamicpv-k5cj": Phase="Pending", Reason="", readiness=false. Elapsed: 43.194443ms
Oct 13 19:27:35.249: INFO: Pod "exec-volume-test-dynamicpv-k5cj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.075333897s
Oct 13 19:27:37.281: INFO: Pod "exec-volume-test-dynamicpv-k5cj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.106758282s
Oct 13 19:27:39.313: INFO: Pod "exec-volume-test-dynamicpv-k5cj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.13881324s
Oct 13 19:27:41.344: INFO: Pod "exec-volume-test-dynamicpv-k5cj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.17021127s
Oct 13 19:27:43.376: INFO: Pod "exec-volume-test-dynamicpv-k5cj": Phase="Pending", Reason="", readiness=false. Elapsed: 10.201580045s
Oct 13 19:27:45.407: INFO: Pod "exec-volume-test-dynamicpv-k5cj": Phase="Pending", Reason="", readiness=false. Elapsed: 12.233489124s
Oct 13 19:27:47.446: INFO: Pod "exec-volume-test-dynamicpv-k5cj": Phase="Pending", Reason="", readiness=false. Elapsed: 14.271816233s
Oct 13 19:27:49.479: INFO: Pod "exec-volume-test-dynamicpv-k5cj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.304749214s
STEP: Saw pod success
Oct 13 19:27:49.479: INFO: Pod "exec-volume-test-dynamicpv-k5cj" satisfied condition "Succeeded or Failed"
Oct 13 19:27:49.512: INFO: Trying to get logs from node ip-172-20-50-191.ca-central-1.compute.internal pod exec-volume-test-dynamicpv-k5cj container exec-container-dynamicpv-k5cj: <nil>
STEP: delete the pod
Oct 13 19:27:49.584: INFO: Waiting for pod exec-volume-test-dynamicpv-k5cj to disappear
Oct 13 19:27:49.615: INFO: Pod exec-volume-test-dynamicpv-k5cj no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-k5cj
Oct 13 19:27:49.615: INFO: Deleting pod "exec-volume-test-dynamicpv-k5cj" in namespace "volume-9407"
... skipping 34 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.3EB0eDjiI/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.3EB0eDjiI/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.3EB0eDjiI/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.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 243 lines ...
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 19:28:29.373: 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.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Oct 13 19:28:29.577: INFO: found topology map[topology.ebs.csi.aws.com/zone:ca-central-1a]
Oct 13 19:28:29.578: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
[AfterEach] [Testpattern: Dynamic PV (immediate binding)] topology
... skipping 4 lines ...

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

    Not enough topologies in cluster -- skipping

    /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 6 lines ...

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

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

    /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 73 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.000 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.3EB0eDjiI/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.3EB0eDjiI/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.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 194 lines ...
Oct 13 19:27:42.208: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-3516-e2e-scbnmgl
STEP: creating a claim
Oct 13 19:27:42.240: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-zn8d
STEP: Creating a pod to test exec-volume-test
Oct 13 19:27:42.337: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-zn8d" in namespace "volume-3516" to be "Succeeded or Failed"
Oct 13 19:27:42.367: INFO: Pod "exec-volume-test-dynamicpv-zn8d": Phase="Pending", Reason="", readiness=false. Elapsed: 30.43122ms
Oct 13 19:27:44.401: INFO: Pod "exec-volume-test-dynamicpv-zn8d": Phase="Pending", Reason="", readiness=false. Elapsed: 2.064573468s
Oct 13 19:27:46.434: INFO: Pod "exec-volume-test-dynamicpv-zn8d": Phase="Pending", Reason="", readiness=false. Elapsed: 4.097465846s
Oct 13 19:27:48.466: INFO: Pod "exec-volume-test-dynamicpv-zn8d": Phase="Pending", Reason="", readiness=false. Elapsed: 6.129474497s
Oct 13 19:27:50.499: INFO: Pod "exec-volume-test-dynamicpv-zn8d": Phase="Pending", Reason="", readiness=false. Elapsed: 8.162049237s
Oct 13 19:27:52.531: INFO: Pod "exec-volume-test-dynamicpv-zn8d": Phase="Pending", Reason="", readiness=false. Elapsed: 10.194541642s
Oct 13 19:27:54.564: INFO: Pod "exec-volume-test-dynamicpv-zn8d": Phase="Pending", Reason="", readiness=false. Elapsed: 12.226617803s
Oct 13 19:27:56.594: INFO: Pod "exec-volume-test-dynamicpv-zn8d": Phase="Pending", Reason="", readiness=false. Elapsed: 14.257500366s
Oct 13 19:27:58.626: INFO: Pod "exec-volume-test-dynamicpv-zn8d": Phase="Pending", Reason="", readiness=false. Elapsed: 16.288679326s
Oct 13 19:28:00.661: INFO: Pod "exec-volume-test-dynamicpv-zn8d": Phase="Pending", Reason="", readiness=false. Elapsed: 18.323775534s
Oct 13 19:28:02.692: INFO: Pod "exec-volume-test-dynamicpv-zn8d": Phase="Pending", Reason="", readiness=false. Elapsed: 20.354683344s
Oct 13 19:28:04.722: INFO: Pod "exec-volume-test-dynamicpv-zn8d": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.385537647s
STEP: Saw pod success
Oct 13 19:28:04.723: INFO: Pod "exec-volume-test-dynamicpv-zn8d" satisfied condition "Succeeded or Failed"
Oct 13 19:28:04.755: INFO: Trying to get logs from node ip-172-20-50-163.ca-central-1.compute.internal pod exec-volume-test-dynamicpv-zn8d container exec-container-dynamicpv-zn8d: <nil>
STEP: delete the pod
Oct 13 19:28:04.828: INFO: Waiting for pod exec-volume-test-dynamicpv-zn8d to disappear
Oct 13 19:28:04.859: INFO: Pod exec-volume-test-dynamicpv-zn8d no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-zn8d
Oct 13 19:28:04.859: INFO: Deleting pod "exec-volume-test-dynamicpv-zn8d" in namespace "volume-3516"
... skipping 74 lines ...
Oct 13 19:28:16.455: INFO: PersistentVolumeClaim pvc-dvk6w found but phase is Pending instead of Bound.
Oct 13 19:28:18.486: INFO: PersistentVolumeClaim pvc-dvk6w found and phase=Bound (12.221275139s)
Oct 13 19:28:18.486: INFO: Waiting up to 3m0s for PersistentVolume aws-x6gx7 to have phase Bound
Oct 13 19:28:18.517: INFO: PersistentVolume aws-x6gx7 found and phase=Bound (30.637728ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-4zk5
STEP: Creating a pod to test exec-volume-test
Oct 13 19:28:18.608: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-4zk5" in namespace "volume-5188" to be "Succeeded or Failed"
Oct 13 19:28:18.641: INFO: Pod "exec-volume-test-preprovisionedpv-4zk5": Phase="Pending", Reason="", readiness=false. Elapsed: 32.125502ms
Oct 13 19:28:20.671: INFO: Pod "exec-volume-test-preprovisionedpv-4zk5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062975425s
Oct 13 19:28:22.707: INFO: Pod "exec-volume-test-preprovisionedpv-4zk5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.098121872s
Oct 13 19:28:24.741: INFO: Pod "exec-volume-test-preprovisionedpv-4zk5": Phase="Pending", Reason="", readiness=false. Elapsed: 6.132352692s
Oct 13 19:28:26.772: INFO: Pod "exec-volume-test-preprovisionedpv-4zk5": Phase="Pending", Reason="", readiness=false. Elapsed: 8.16399648s
Oct 13 19:28:28.803: INFO: Pod "exec-volume-test-preprovisionedpv-4zk5": Phase="Pending", Reason="", readiness=false. Elapsed: 10.194604058s
Oct 13 19:28:30.835: INFO: Pod "exec-volume-test-preprovisionedpv-4zk5": Phase="Pending", Reason="", readiness=false. Elapsed: 12.22656364s
Oct 13 19:28:32.865: INFO: Pod "exec-volume-test-preprovisionedpv-4zk5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.256976985s
STEP: Saw pod success
Oct 13 19:28:32.865: INFO: Pod "exec-volume-test-preprovisionedpv-4zk5" satisfied condition "Succeeded or Failed"
Oct 13 19:28:32.895: INFO: Trying to get logs from node ip-172-20-50-163.ca-central-1.compute.internal pod exec-volume-test-preprovisionedpv-4zk5 container exec-container-preprovisionedpv-4zk5: <nil>
STEP: delete the pod
Oct 13 19:28:32.973: INFO: Waiting for pod exec-volume-test-preprovisionedpv-4zk5 to disappear
Oct 13 19:28:33.003: INFO: Pod exec-volume-test-preprovisionedpv-4zk5 no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-4zk5
Oct 13 19:28:33.004: INFO: Deleting pod "exec-volume-test-preprovisionedpv-4zk5" in namespace "volume-5188"
STEP: Deleting pv and pvc
Oct 13 19:28:33.034: INFO: Deleting PersistentVolumeClaim "pvc-dvk6w"
Oct 13 19:28:33.065: INFO: Deleting PersistentVolume "aws-x6gx7"
Oct 13 19:28:33.203: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0ac950524ec32c720", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ac950524ec32c720 is currently attached to i-05786989bd674e173
	status code: 400, request id: 8d53a08e-40bd-4876-b555-0f7ffaaf2a87
Oct 13 19:28:38.487: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0ac950524ec32c720", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ac950524ec32c720 is currently attached to i-05786989bd674e173
	status code: 400, request id: 731d4fa6-f057-4765-a041-71d69a0d92c7
Oct 13 19:28:43.762: INFO: Successfully deleted PD "aws://ca-central-1a/vol-0ac950524ec32c720".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 19:28:43.762: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-5188" for this suite.
... skipping 337 lines ...
Oct 13 19:28:14.385: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2867g4hxz
STEP: creating a claim
Oct 13 19:28:14.416: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-fhd9
STEP: Creating a pod to test subpath
Oct 13 19:28:14.519: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-fhd9" in namespace "provisioning-2867" to be "Succeeded or Failed"
Oct 13 19:28:14.550: INFO: Pod "pod-subpath-test-dynamicpv-fhd9": Phase="Pending", Reason="", readiness=false. Elapsed: 31.221363ms
Oct 13 19:28:16.581: INFO: Pod "pod-subpath-test-dynamicpv-fhd9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062353909s
Oct 13 19:28:18.616: INFO: Pod "pod-subpath-test-dynamicpv-fhd9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.097087106s
Oct 13 19:28:20.649: INFO: Pod "pod-subpath-test-dynamicpv-fhd9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.129692021s
Oct 13 19:28:22.680: INFO: Pod "pod-subpath-test-dynamicpv-fhd9": Phase="Pending", Reason="", readiness=false. Elapsed: 8.161444642s
Oct 13 19:28:24.717: INFO: Pod "pod-subpath-test-dynamicpv-fhd9": Phase="Pending", Reason="", readiness=false. Elapsed: 10.19841224s
... skipping 2 lines ...
Oct 13 19:28:30.815: INFO: Pod "pod-subpath-test-dynamicpv-fhd9": Phase="Pending", Reason="", readiness=false. Elapsed: 16.295643076s
Oct 13 19:28:32.845: INFO: Pod "pod-subpath-test-dynamicpv-fhd9": Phase="Pending", Reason="", readiness=false. Elapsed: 18.32645952s
Oct 13 19:28:34.876: INFO: Pod "pod-subpath-test-dynamicpv-fhd9": Phase="Pending", Reason="", readiness=false. Elapsed: 20.357438406s
Oct 13 19:28:36.909: INFO: Pod "pod-subpath-test-dynamicpv-fhd9": Phase="Pending", Reason="", readiness=false. Elapsed: 22.39036539s
Oct 13 19:28:38.940: INFO: Pod "pod-subpath-test-dynamicpv-fhd9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.421126783s
STEP: Saw pod success
Oct 13 19:28:38.940: INFO: Pod "pod-subpath-test-dynamicpv-fhd9" satisfied condition "Succeeded or Failed"
Oct 13 19:28:38.971: INFO: Trying to get logs from node ip-172-20-50-191.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-fhd9 container test-container-volume-dynamicpv-fhd9: <nil>
STEP: delete the pod
Oct 13 19:28:39.047: INFO: Waiting for pod pod-subpath-test-dynamicpv-fhd9 to disappear
Oct 13 19:28:39.082: INFO: Pod pod-subpath-test-dynamicpv-fhd9 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-fhd9
Oct 13 19:28:39.082: INFO: Deleting pod "pod-subpath-test-dynamicpv-fhd9" in namespace "provisioning-2867"
... skipping 191 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.3EB0eDjiI/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.3EB0eDjiI/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.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 153 lines ...
Oct 13 19:28:31.352: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Oct 13 19:28:31.757: INFO: Successfully created a new PD: "aws://ca-central-1a/vol-0af39014a7c8d10b1".
Oct 13 19:28:31.757: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-mzsg
STEP: Creating a pod to test exec-volume-test
Oct 13 19:28:31.792: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-mzsg" in namespace "volume-2604" to be "Succeeded or Failed"
Oct 13 19:28:31.825: INFO: Pod "exec-volume-test-inlinevolume-mzsg": Phase="Pending", Reason="", readiness=false. Elapsed: 32.969813ms
Oct 13 19:28:33.857: INFO: Pod "exec-volume-test-inlinevolume-mzsg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.065590725s
Oct 13 19:28:35.889: INFO: Pod "exec-volume-test-inlinevolume-mzsg": Phase="Pending", Reason="", readiness=false. Elapsed: 4.096872263s
Oct 13 19:28:37.921: INFO: Pod "exec-volume-test-inlinevolume-mzsg": Phase="Pending", Reason="", readiness=false. Elapsed: 6.129325012s
Oct 13 19:28:39.952: INFO: Pod "exec-volume-test-inlinevolume-mzsg": Phase="Pending", Reason="", readiness=false. Elapsed: 8.160483015s
Oct 13 19:28:41.984: INFO: Pod "exec-volume-test-inlinevolume-mzsg": Phase="Pending", Reason="", readiness=false. Elapsed: 10.191769138s
Oct 13 19:28:44.015: INFO: Pod "exec-volume-test-inlinevolume-mzsg": Phase="Pending", Reason="", readiness=false. Elapsed: 12.223444587s
Oct 13 19:28:46.047: INFO: Pod "exec-volume-test-inlinevolume-mzsg": Phase="Pending", Reason="", readiness=false. Elapsed: 14.254992435s
Oct 13 19:28:48.078: INFO: Pod "exec-volume-test-inlinevolume-mzsg": Phase="Pending", Reason="", readiness=false. Elapsed: 16.286481112s
Oct 13 19:28:50.111: INFO: Pod "exec-volume-test-inlinevolume-mzsg": Phase="Pending", Reason="", readiness=false. Elapsed: 18.319083633s
Oct 13 19:28:52.143: INFO: Pod "exec-volume-test-inlinevolume-mzsg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.351493658s
STEP: Saw pod success
Oct 13 19:28:52.143: INFO: Pod "exec-volume-test-inlinevolume-mzsg" satisfied condition "Succeeded or Failed"
Oct 13 19:28:52.174: INFO: Trying to get logs from node ip-172-20-38-144.ca-central-1.compute.internal pod exec-volume-test-inlinevolume-mzsg container exec-container-inlinevolume-mzsg: <nil>
STEP: delete the pod
Oct 13 19:28:52.246: INFO: Waiting for pod exec-volume-test-inlinevolume-mzsg to disappear
Oct 13 19:28:52.276: INFO: Pod exec-volume-test-inlinevolume-mzsg no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-mzsg
Oct 13 19:28:52.276: INFO: Deleting pod "exec-volume-test-inlinevolume-mzsg" in namespace "volume-2604"
Oct 13 19:28:52.427: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0af39014a7c8d10b1", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0af39014a7c8d10b1 is currently attached to i-049bea91c6928b078
	status code: 400, request id: 4f748010-eb68-4951-8af6-4db4a70ff800
Oct 13 19:28:57.711: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0af39014a7c8d10b1", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0af39014a7c8d10b1 is currently attached to i-049bea91c6928b078
	status code: 400, request id: 95337a69-309d-40d4-86a7-8c59055d11d7
Oct 13 19:29:02.952: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0af39014a7c8d10b1", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0af39014a7c8d10b1 is currently attached to i-049bea91c6928b078
	status code: 400, request id: c51e8e57-3bf4-4b5b-b58f-03c35fef145c
Oct 13 19:29:08.223: INFO: Successfully deleted PD "aws://ca-central-1a/vol-0af39014a7c8d10b1".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 19:29:08.223: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-2604" for this suite.
... skipping 81 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 19:28:19.838: 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.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Oct 13 19:28:19.994: INFO: Creating resource for dynamic PV
Oct 13 19:28:19.994: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-700-e2e-scxd2zx
STEP: creating a claim
Oct 13 19:28:20.026: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-rg4v
STEP: Checking for subpath error in container status
Oct 13 19:28:44.184: INFO: Deleting pod "pod-subpath-test-dynamicpv-rg4v" in namespace "provisioning-700"
Oct 13 19:28:44.218: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-rg4v" to be fully deleted
STEP: Deleting pod
Oct 13 19:28:48.279: INFO: Deleting pod "pod-subpath-test-dynamicpv-rg4v" in namespace "provisioning-700"
STEP: Deleting pvc
Oct 13 19:28:48.372: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comfnrmx"
... skipping 12 lines ...

• [SLOW TEST:48.830 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath directory is outside the volume [Slow][LinuxOnly]
    /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Oct 13 19:29:08.672: INFO: Driver ebs.csi.aws.com doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
... skipping 182 lines ...
Oct 13 19:28:48.148: INFO: Waiting for pod aws-client to disappear
Oct 13 19:28:48.178: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Oct 13 19:28:48.178: INFO: Deleting PersistentVolumeClaim "pvc-dfp92"
Oct 13 19:28:48.211: INFO: Deleting PersistentVolume "aws-sjlxj"
Oct 13 19:28:48.374: INFO: Couldn't delete PD "aws://ca-central-1a/vol-004ec1bdde321727c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-004ec1bdde321727c is currently attached to i-05786989bd674e173
	status code: 400, request id: b4bf6fe1-1df7-4400-990f-7fc821a005e2
Oct 13 19:28:53.637: INFO: Couldn't delete PD "aws://ca-central-1a/vol-004ec1bdde321727c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-004ec1bdde321727c is currently attached to i-05786989bd674e173
	status code: 400, request id: 8f9f3182-3c05-4622-a32b-d7b3f73b2634
Oct 13 19:28:58.919: INFO: Couldn't delete PD "aws://ca-central-1a/vol-004ec1bdde321727c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-004ec1bdde321727c is currently attached to i-05786989bd674e173
	status code: 400, request id: a20ce389-c23a-4485-8890-42761fec808c
Oct 13 19:29:04.190: INFO: Couldn't delete PD "aws://ca-central-1a/vol-004ec1bdde321727c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-004ec1bdde321727c is currently attached to i-05786989bd674e173
	status code: 400, request id: abe02b1b-5f08-448f-ad4d-44c150996cd0
Oct 13 19:29:09.413: INFO: Couldn't delete PD "aws://ca-central-1a/vol-004ec1bdde321727c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-004ec1bdde321727c is currently attached to i-05786989bd674e173
	status code: 400, request id: 8f8d08b4-a471-4090-a7bc-b9c5703a8ccf
Oct 13 19:29:14.675: INFO: Successfully deleted PD "aws://ca-central-1a/vol-004ec1bdde321727c".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 19:29:14.675: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-4840" for this suite.
... skipping 447 lines ...
Oct 13 19:28:25.275: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8476-e2e-sccnlcg
STEP: creating a claim
Oct 13 19:28:25.308: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-dwvp
STEP: Creating a pod to test subpath
Oct 13 19:28:25.404: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-dwvp" in namespace "provisioning-8476" to be "Succeeded or Failed"
Oct 13 19:28:25.435: INFO: Pod "pod-subpath-test-dynamicpv-dwvp": Phase="Pending", Reason="", readiness=false. Elapsed: 30.950697ms
Oct 13 19:28:27.467: INFO: Pod "pod-subpath-test-dynamicpv-dwvp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.0630118s
Oct 13 19:28:29.499: INFO: Pod "pod-subpath-test-dynamicpv-dwvp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.095221225s
Oct 13 19:28:31.530: INFO: Pod "pod-subpath-test-dynamicpv-dwvp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.126462638s
Oct 13 19:28:33.561: INFO: Pod "pod-subpath-test-dynamicpv-dwvp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.157823764s
Oct 13 19:28:35.593: INFO: Pod "pod-subpath-test-dynamicpv-dwvp": Phase="Pending", Reason="", readiness=false. Elapsed: 10.189867148s
... skipping 2 lines ...
Oct 13 19:28:41.686: INFO: Pod "pod-subpath-test-dynamicpv-dwvp": Phase="Pending", Reason="", readiness=false. Elapsed: 16.282872634s
Oct 13 19:28:43.718: INFO: Pod "pod-subpath-test-dynamicpv-dwvp": Phase="Pending", Reason="", readiness=false. Elapsed: 18.314401876s
Oct 13 19:28:45.749: INFO: Pod "pod-subpath-test-dynamicpv-dwvp": Phase="Pending", Reason="", readiness=false. Elapsed: 20.345582485s
Oct 13 19:28:47.780: INFO: Pod "pod-subpath-test-dynamicpv-dwvp": Phase="Pending", Reason="", readiness=false. Elapsed: 22.376783471s
Oct 13 19:28:49.813: INFO: Pod "pod-subpath-test-dynamicpv-dwvp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.408977106s
STEP: Saw pod success
Oct 13 19:28:49.813: INFO: Pod "pod-subpath-test-dynamicpv-dwvp" satisfied condition "Succeeded or Failed"
Oct 13 19:28:49.849: INFO: Trying to get logs from node ip-172-20-38-144.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-dwvp container test-container-subpath-dynamicpv-dwvp: <nil>
STEP: delete the pod
Oct 13 19:28:49.943: INFO: Waiting for pod pod-subpath-test-dynamicpv-dwvp to disappear
Oct 13 19:28:49.974: INFO: Pod pod-subpath-test-dynamicpv-dwvp no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-dwvp
Oct 13 19:28:49.974: INFO: Deleting pod "pod-subpath-test-dynamicpv-dwvp" in namespace "provisioning-8476"
... skipping 137 lines ...
Oct 13 19:28:34.589: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-400-e2e-scxg59w
STEP: creating a claim
Oct 13 19:28:34.621: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-gkf2
STEP: Creating a pod to test multi_subpath
Oct 13 19:28:34.721: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-gkf2" in namespace "provisioning-400" to be "Succeeded or Failed"
Oct 13 19:28:34.751: INFO: Pod "pod-subpath-test-dynamicpv-gkf2": Phase="Pending", Reason="", readiness=false. Elapsed: 30.507814ms
Oct 13 19:28:36.781: INFO: Pod "pod-subpath-test-dynamicpv-gkf2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.06077594s
Oct 13 19:28:38.812: INFO: Pod "pod-subpath-test-dynamicpv-gkf2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.091366155s
Oct 13 19:28:40.844: INFO: Pod "pod-subpath-test-dynamicpv-gkf2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.123190596s
Oct 13 19:28:42.876: INFO: Pod "pod-subpath-test-dynamicpv-gkf2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.155056765s
Oct 13 19:28:44.909: INFO: Pod "pod-subpath-test-dynamicpv-gkf2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.188365739s
Oct 13 19:28:46.940: INFO: Pod "pod-subpath-test-dynamicpv-gkf2": Phase="Pending", Reason="", readiness=false. Elapsed: 12.219382429s
Oct 13 19:28:48.971: INFO: Pod "pod-subpath-test-dynamicpv-gkf2": Phase="Pending", Reason="", readiness=false. Elapsed: 14.250747577s
Oct 13 19:28:51.002: INFO: Pod "pod-subpath-test-dynamicpv-gkf2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.281392532s
STEP: Saw pod success
Oct 13 19:28:51.002: INFO: Pod "pod-subpath-test-dynamicpv-gkf2" satisfied condition "Succeeded or Failed"
Oct 13 19:28:51.033: INFO: Trying to get logs from node ip-172-20-50-163.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-gkf2 container test-container-subpath-dynamicpv-gkf2: <nil>
STEP: delete the pod
Oct 13 19:28:51.112: INFO: Waiting for pod pod-subpath-test-dynamicpv-gkf2 to disappear
Oct 13 19:28:51.194: INFO: Pod pod-subpath-test-dynamicpv-gkf2 no longer exists
STEP: Deleting pod
Oct 13 19:28:51.194: INFO: Deleting pod "pod-subpath-test-dynamicpv-gkf2" in namespace "provisioning-400"
... skipping 132 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 19:28:59.494: 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.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Oct 13 19:28:59.647: INFO: Creating resource for dynamic PV
Oct 13 19:28:59.647: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-8271-e2e-scvwjbd
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Oct 13 19:29:05.867: INFO: Deleting pod "pod-c51fbbf1-d5c3-4a34-a03a-e2dc971bb04e" in namespace "volumemode-8271"
Oct 13 19:29:05.898: INFO: Wait up to 5m0s for pod "pod-c51fbbf1-d5c3-4a34-a03a-e2dc971bb04e" to be fully deleted
STEP: Deleting pvc
Oct 13 19:29:08.020: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com5xltj"
Oct 13 19:29:08.055: INFO: Waiting up to 5m0s for PersistentVolume pvc-cb487980-bf96-4a9b-9202-a7e8ffaa811c to get deleted
Oct 13 19:29:08.085: INFO: PersistentVolume pvc-cb487980-bf96-4a9b-9202-a7e8ffaa811c found and phase=Released (30.215483ms)
... skipping 10 lines ...

• [SLOW TEST:28.814 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.3EB0eDjiI/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.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 100 lines ...
Oct 13 19:28:18.330: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5566-e2e-sc9zplz
STEP: creating a claim
Oct 13 19:28:18.361: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-z752
STEP: Creating a pod to test atomic-volume-subpath
Oct 13 19:28:18.455: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-z752" in namespace "provisioning-5566" to be "Succeeded or Failed"
Oct 13 19:28:18.487: INFO: Pod "pod-subpath-test-dynamicpv-z752": Phase="Pending", Reason="", readiness=false. Elapsed: 31.188204ms
Oct 13 19:28:20.518: INFO: Pod "pod-subpath-test-dynamicpv-z752": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062985439s
Oct 13 19:28:22.550: INFO: Pod "pod-subpath-test-dynamicpv-z752": Phase="Pending", Reason="", readiness=false. Elapsed: 4.094802642s
Oct 13 19:28:24.582: INFO: Pod "pod-subpath-test-dynamicpv-z752": Phase="Pending", Reason="", readiness=false. Elapsed: 6.126926153s
Oct 13 19:28:26.614: INFO: Pod "pod-subpath-test-dynamicpv-z752": Phase="Pending", Reason="", readiness=false. Elapsed: 8.159023116s
Oct 13 19:28:28.646: INFO: Pod "pod-subpath-test-dynamicpv-z752": Phase="Pending", Reason="", readiness=false. Elapsed: 10.190880031s
... skipping 8 lines ...
Oct 13 19:28:46.941: INFO: Pod "pod-subpath-test-dynamicpv-z752": Phase="Running", Reason="", readiness=true. Elapsed: 28.48567637s
Oct 13 19:28:48.972: INFO: Pod "pod-subpath-test-dynamicpv-z752": Phase="Running", Reason="", readiness=true. Elapsed: 30.516960579s
Oct 13 19:28:51.003: INFO: Pod "pod-subpath-test-dynamicpv-z752": Phase="Running", Reason="", readiness=true. Elapsed: 32.547953807s
Oct 13 19:28:53.034: INFO: Pod "pod-subpath-test-dynamicpv-z752": Phase="Running", Reason="", readiness=true. Elapsed: 34.578843655s
Oct 13 19:28:55.066: INFO: Pod "pod-subpath-test-dynamicpv-z752": Phase="Succeeded", Reason="", readiness=false. Elapsed: 36.610962352s
STEP: Saw pod success
Oct 13 19:28:55.066: INFO: Pod "pod-subpath-test-dynamicpv-z752" satisfied condition "Succeeded or Failed"
Oct 13 19:28:55.098: INFO: Trying to get logs from node ip-172-20-38-144.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-z752 container test-container-subpath-dynamicpv-z752: <nil>
STEP: delete the pod
Oct 13 19:28:55.169: INFO: Waiting for pod pod-subpath-test-dynamicpv-z752 to disappear
Oct 13 19:28:55.199: INFO: Pod pod-subpath-test-dynamicpv-z752 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-z752
Oct 13 19:28:55.199: INFO: Deleting pod "pod-subpath-test-dynamicpv-z752" in namespace "provisioning-5566"
... skipping 79 lines ...
Oct 13 19:28:49.916: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1386-e2e-sc5v7kp
STEP: creating a claim
Oct 13 19:28:49.954: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-2cwh
STEP: Creating a pod to test subpath
Oct 13 19:28:50.055: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-2cwh" in namespace "provisioning-1386" to be "Succeeded or Failed"
Oct 13 19:28:50.086: INFO: Pod "pod-subpath-test-dynamicpv-2cwh": Phase="Pending", Reason="", readiness=false. Elapsed: 31.375391ms
Oct 13 19:28:52.120: INFO: Pod "pod-subpath-test-dynamicpv-2cwh": Phase="Pending", Reason="", readiness=false. Elapsed: 2.064895313s
Oct 13 19:28:54.152: INFO: Pod "pod-subpath-test-dynamicpv-2cwh": Phase="Pending", Reason="", readiness=false. Elapsed: 4.096920045s
Oct 13 19:28:56.186: INFO: Pod "pod-subpath-test-dynamicpv-2cwh": Phase="Pending", Reason="", readiness=false. Elapsed: 6.131802357s
Oct 13 19:28:58.218: INFO: Pod "pod-subpath-test-dynamicpv-2cwh": Phase="Pending", Reason="", readiness=false. Elapsed: 8.162954215s
Oct 13 19:29:00.251: INFO: Pod "pod-subpath-test-dynamicpv-2cwh": Phase="Pending", Reason="", readiness=false. Elapsed: 10.195846136s
Oct 13 19:29:02.282: INFO: Pod "pod-subpath-test-dynamicpv-2cwh": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.227429385s
STEP: Saw pod success
Oct 13 19:29:02.282: INFO: Pod "pod-subpath-test-dynamicpv-2cwh" satisfied condition "Succeeded or Failed"
Oct 13 19:29:02.313: INFO: Trying to get logs from node ip-172-20-38-144.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-2cwh container test-container-volume-dynamicpv-2cwh: <nil>
STEP: delete the pod
Oct 13 19:29:02.388: INFO: Waiting for pod pod-subpath-test-dynamicpv-2cwh to disappear
Oct 13 19:29:02.419: INFO: Pod pod-subpath-test-dynamicpv-2cwh no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-2cwh
Oct 13 19:29:02.419: INFO: Deleting pod "pod-subpath-test-dynamicpv-2cwh" in namespace "provisioning-1386"
... skipping 210 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.3EB0eDjiI/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.3EB0eDjiI/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.3EB0eDjiI/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.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 53 lines ...
Oct 13 19:29:30.797: INFO: PersistentVolumeClaim pvc-xjt46 found but phase is Pending instead of Bound.
Oct 13 19:29:32.829: INFO: PersistentVolumeClaim pvc-xjt46 found and phase=Bound (14.254440618s)
Oct 13 19:29:32.829: INFO: Waiting up to 3m0s for PersistentVolume aws-6lngk to have phase Bound
Oct 13 19:29:32.860: INFO: PersistentVolume aws-6lngk found and phase=Bound (30.478861ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-9qmq
STEP: Creating a pod to test exec-volume-test
Oct 13 19:29:32.954: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-9qmq" in namespace "volume-8465" to be "Succeeded or Failed"
Oct 13 19:29:32.986: INFO: Pod "exec-volume-test-preprovisionedpv-9qmq": Phase="Pending", Reason="", readiness=false. Elapsed: 31.267094ms
Oct 13 19:29:35.019: INFO: Pod "exec-volume-test-preprovisionedpv-9qmq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.064882225s
Oct 13 19:29:37.051: INFO: Pod "exec-volume-test-preprovisionedpv-9qmq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.096956884s
Oct 13 19:29:39.082: INFO: Pod "exec-volume-test-preprovisionedpv-9qmq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.128030667s
Oct 13 19:29:41.115: INFO: Pod "exec-volume-test-preprovisionedpv-9qmq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.160169393s
STEP: Saw pod success
Oct 13 19:29:41.115: INFO: Pod "exec-volume-test-preprovisionedpv-9qmq" satisfied condition "Succeeded or Failed"
Oct 13 19:29:41.146: INFO: Trying to get logs from node ip-172-20-50-191.ca-central-1.compute.internal pod exec-volume-test-preprovisionedpv-9qmq container exec-container-preprovisionedpv-9qmq: <nil>
STEP: delete the pod
Oct 13 19:29:41.224: INFO: Waiting for pod exec-volume-test-preprovisionedpv-9qmq to disappear
Oct 13 19:29:41.254: INFO: Pod exec-volume-test-preprovisionedpv-9qmq no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-9qmq
Oct 13 19:29:41.255: INFO: Deleting pod "exec-volume-test-preprovisionedpv-9qmq" in namespace "volume-8465"
STEP: Deleting pv and pvc
Oct 13 19:29:41.285: INFO: Deleting PersistentVolumeClaim "pvc-xjt46"
Oct 13 19:29:41.325: INFO: Deleting PersistentVolume "aws-6lngk"
Oct 13 19:29:41.534: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0ed4f7de2622e1e0b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ed4f7de2622e1e0b is currently attached to i-0ffcb4d54aeaf8020
	status code: 400, request id: 9341b673-52b4-47f9-a755-ac0f9150765b
Oct 13 19:29:46.764: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0ed4f7de2622e1e0b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ed4f7de2622e1e0b is currently attached to i-0ffcb4d54aeaf8020
	status code: 400, request id: 9ded40f8-67c8-4e60-b239-d1f6be7ab6e6
Oct 13 19:29:52.012: INFO: Successfully deleted PD "aws://ca-central-1a/vol-0ed4f7de2622e1e0b".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 19:29:52.012: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8465" for this suite.
... skipping 23 lines ...
Oct 13 19:28:56.248: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3315-e2e-scmnb8k
STEP: creating a claim
Oct 13 19:28:56.280: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-rvk8
STEP: Creating a pod to test subpath
Oct 13 19:28:56.376: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-rvk8" in namespace "provisioning-3315" to be "Succeeded or Failed"
Oct 13 19:28:56.407: INFO: Pod "pod-subpath-test-dynamicpv-rvk8": Phase="Pending", Reason="", readiness=false. Elapsed: 30.679291ms
Oct 13 19:28:58.438: INFO: Pod "pod-subpath-test-dynamicpv-rvk8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061612207s
Oct 13 19:29:00.473: INFO: Pod "pod-subpath-test-dynamicpv-rvk8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.096510903s
Oct 13 19:29:02.504: INFO: Pod "pod-subpath-test-dynamicpv-rvk8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.127891297s
Oct 13 19:29:04.536: INFO: Pod "pod-subpath-test-dynamicpv-rvk8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.159502836s
Oct 13 19:29:06.567: INFO: Pod "pod-subpath-test-dynamicpv-rvk8": Phase="Pending", Reason="", readiness=false. Elapsed: 10.190382064s
Oct 13 19:29:08.598: INFO: Pod "pod-subpath-test-dynamicpv-rvk8": Phase="Pending", Reason="", readiness=false. Elapsed: 12.221658195s
Oct 13 19:29:10.630: INFO: Pod "pod-subpath-test-dynamicpv-rvk8": Phase="Pending", Reason="", readiness=false. Elapsed: 14.253817727s
Oct 13 19:29:12.661: INFO: Pod "pod-subpath-test-dynamicpv-rvk8": Phase="Pending", Reason="", readiness=false. Elapsed: 16.284477092s
Oct 13 19:29:14.693: INFO: Pod "pod-subpath-test-dynamicpv-rvk8": Phase="Pending", Reason="", readiness=false. Elapsed: 18.316138221s
Oct 13 19:29:16.725: INFO: Pod "pod-subpath-test-dynamicpv-rvk8": Phase="Pending", Reason="", readiness=false. Elapsed: 20.348399493s
Oct 13 19:29:18.756: INFO: Pod "pod-subpath-test-dynamicpv-rvk8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.379433877s
STEP: Saw pod success
Oct 13 19:29:18.756: INFO: Pod "pod-subpath-test-dynamicpv-rvk8" satisfied condition "Succeeded or Failed"
Oct 13 19:29:18.787: INFO: Trying to get logs from node ip-172-20-50-163.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-rvk8 container test-container-subpath-dynamicpv-rvk8: <nil>
STEP: delete the pod
Oct 13 19:29:18.863: INFO: Waiting for pod pod-subpath-test-dynamicpv-rvk8 to disappear
Oct 13 19:29:18.893: INFO: Pod pod-subpath-test-dynamicpv-rvk8 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-rvk8
Oct 13 19:29:18.893: INFO: Deleting pod "pod-subpath-test-dynamicpv-rvk8" in namespace "provisioning-3315"
... skipping 260 lines ...
Oct 13 19:29:08.296: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1327q5vxm
STEP: creating a claim
Oct 13 19:29:08.332: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-522c
STEP: Creating a pod to test subpath
Oct 13 19:29:08.432: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-522c" in namespace "provisioning-1327" to be "Succeeded or Failed"
Oct 13 19:29:08.463: INFO: Pod "pod-subpath-test-dynamicpv-522c": Phase="Pending", Reason="", readiness=false. Elapsed: 30.484904ms
Oct 13 19:29:10.493: INFO: Pod "pod-subpath-test-dynamicpv-522c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061058381s
Oct 13 19:29:12.525: INFO: Pod "pod-subpath-test-dynamicpv-522c": Phase="Pending", Reason="", readiness=false. Elapsed: 4.092911305s
Oct 13 19:29:14.556: INFO: Pod "pod-subpath-test-dynamicpv-522c": Phase="Pending", Reason="", readiness=false. Elapsed: 6.123531876s
Oct 13 19:29:16.586: INFO: Pod "pod-subpath-test-dynamicpv-522c": Phase="Pending", Reason="", readiness=false. Elapsed: 8.154230672s
Oct 13 19:29:18.617: INFO: Pod "pod-subpath-test-dynamicpv-522c": Phase="Pending", Reason="", readiness=false. Elapsed: 10.184946381s
... skipping 2 lines ...
Oct 13 19:29:24.713: INFO: Pod "pod-subpath-test-dynamicpv-522c": Phase="Pending", Reason="", readiness=false. Elapsed: 16.281130718s
Oct 13 19:29:26.744: INFO: Pod "pod-subpath-test-dynamicpv-522c": Phase="Pending", Reason="", readiness=false. Elapsed: 18.311765609s
Oct 13 19:29:28.775: INFO: Pod "pod-subpath-test-dynamicpv-522c": Phase="Pending", Reason="", readiness=false. Elapsed: 20.343299805s
Oct 13 19:29:30.806: INFO: Pod "pod-subpath-test-dynamicpv-522c": Phase="Pending", Reason="", readiness=false. Elapsed: 22.374367422s
Oct 13 19:29:32.839: INFO: Pod "pod-subpath-test-dynamicpv-522c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.407149024s
STEP: Saw pod success
Oct 13 19:29:32.839: INFO: Pod "pod-subpath-test-dynamicpv-522c" satisfied condition "Succeeded or Failed"
Oct 13 19:29:32.870: INFO: Trying to get logs from node ip-172-20-50-191.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-522c container test-container-subpath-dynamicpv-522c: <nil>
STEP: delete the pod
Oct 13 19:29:32.939: INFO: Waiting for pod pod-subpath-test-dynamicpv-522c to disappear
Oct 13 19:29:32.977: INFO: Pod pod-subpath-test-dynamicpv-522c no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-522c
Oct 13 19:29:32.977: INFO: Deleting pod "pod-subpath-test-dynamicpv-522c" in namespace "provisioning-1327"
STEP: Creating pod pod-subpath-test-dynamicpv-522c
STEP: Creating a pod to test subpath
Oct 13 19:29:33.042: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-522c" in namespace "provisioning-1327" to be "Succeeded or Failed"
Oct 13 19:29:33.073: INFO: Pod "pod-subpath-test-dynamicpv-522c": Phase="Pending", Reason="", readiness=false. Elapsed: 30.482522ms
Oct 13 19:29:35.105: INFO: Pod "pod-subpath-test-dynamicpv-522c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062372898s
Oct 13 19:29:37.137: INFO: Pod "pod-subpath-test-dynamicpv-522c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.094177152s
STEP: Saw pod success
Oct 13 19:29:37.137: INFO: Pod "pod-subpath-test-dynamicpv-522c" satisfied condition "Succeeded or Failed"
Oct 13 19:29:37.168: INFO: Trying to get logs from node ip-172-20-50-191.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-522c container test-container-subpath-dynamicpv-522c: <nil>
STEP: delete the pod
Oct 13 19:29:37.239: INFO: Waiting for pod pod-subpath-test-dynamicpv-522c to disappear
Oct 13 19:29:37.269: INFO: Pod pod-subpath-test-dynamicpv-522c no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-522c
Oct 13 19:29:37.269: INFO: Deleting pod "pod-subpath-test-dynamicpv-522c" in namespace "provisioning-1327"
... skipping 37 lines ...
Oct 13 19:29:30.879: INFO: Creating resource for dynamic PV
Oct 13 19:29:30.879: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-9439-e2e-sc89m77
STEP: creating a claim
STEP: Expanding non-expandable pvc
Oct 13 19:29:30.976: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Oct 13 19:29:31.042: INFO: Error updating pvc ebs.csi.aws.comftw8g: PersistentVolumeClaim "ebs.csi.aws.comftw8g" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-9439-e2e-sc89m77",
  	... // 3 identical fields
  }

Oct 13 19:29:33.104: INFO: Error updating pvc ebs.csi.aws.comftw8g: PersistentVolumeClaim "ebs.csi.aws.comftw8g" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-9439-e2e-sc89m77",
  	... // 3 identical fields
  }

Oct 13 19:29:35.104: INFO: Error updating pvc ebs.csi.aws.comftw8g: PersistentVolumeClaim "ebs.csi.aws.comftw8g" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-9439-e2e-sc89m77",
  	... // 3 identical fields
  }

Oct 13 19:29:37.104: INFO: Error updating pvc ebs.csi.aws.comftw8g: PersistentVolumeClaim "ebs.csi.aws.comftw8g" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-9439-e2e-sc89m77",
  	... // 3 identical fields
  }

Oct 13 19:29:39.112: INFO: Error updating pvc ebs.csi.aws.comftw8g: PersistentVolumeClaim "ebs.csi.aws.comftw8g" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-9439-e2e-sc89m77",
  	... // 3 identical fields
  }

Oct 13 19:29:41.104: INFO: Error updating pvc ebs.csi.aws.comftw8g: PersistentVolumeClaim "ebs.csi.aws.comftw8g" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-9439-e2e-sc89m77",
  	... // 3 identical fields
  }

Oct 13 19:29:43.105: INFO: Error updating pvc ebs.csi.aws.comftw8g: PersistentVolumeClaim "ebs.csi.aws.comftw8g" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-9439-e2e-sc89m77",
  	... // 3 identical fields
  }

Oct 13 19:29:45.119: INFO: Error updating pvc ebs.csi.aws.comftw8g: PersistentVolumeClaim "ebs.csi.aws.comftw8g" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-9439-e2e-sc89m77",
  	... // 3 identical fields
  }

Oct 13 19:29:47.115: INFO: Error updating pvc ebs.csi.aws.comftw8g: PersistentVolumeClaim "ebs.csi.aws.comftw8g" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-9439-e2e-sc89m77",
  	... // 3 identical fields
  }

Oct 13 19:29:49.110: INFO: Error updating pvc ebs.csi.aws.comftw8g: PersistentVolumeClaim "ebs.csi.aws.comftw8g" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-9439-e2e-sc89m77",
  	... // 3 identical fields
  }

Oct 13 19:29:51.104: INFO: Error updating pvc ebs.csi.aws.comftw8g: PersistentVolumeClaim "ebs.csi.aws.comftw8g" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-9439-e2e-sc89m77",
  	... // 3 identical fields
  }

Oct 13 19:29:53.104: INFO: Error updating pvc ebs.csi.aws.comftw8g: PersistentVolumeClaim "ebs.csi.aws.comftw8g" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-9439-e2e-sc89m77",
  	... // 3 identical fields
  }

Oct 13 19:29:55.103: INFO: Error updating pvc ebs.csi.aws.comftw8g: PersistentVolumeClaim "ebs.csi.aws.comftw8g" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-9439-e2e-sc89m77",
  	... // 3 identical fields
  }

Oct 13 19:29:57.108: INFO: Error updating pvc ebs.csi.aws.comftw8g: PersistentVolumeClaim "ebs.csi.aws.comftw8g" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-9439-e2e-sc89m77",
  	... // 3 identical fields
  }

Oct 13 19:29:59.106: INFO: Error updating pvc ebs.csi.aws.comftw8g: PersistentVolumeClaim "ebs.csi.aws.comftw8g" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-9439-e2e-sc89m77",
  	... // 3 identical fields
  }

Oct 13 19:30:01.107: INFO: Error updating pvc ebs.csi.aws.comftw8g: PersistentVolumeClaim "ebs.csi.aws.comftw8g" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-9439-e2e-sc89m77",
  	... // 3 identical fields
  }

Oct 13 19:30:01.172: INFO: Error updating pvc ebs.csi.aws.comftw8g: PersistentVolumeClaim "ebs.csi.aws.comftw8g" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 258 lines ...
Oct 13 19:30:03.800: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 199 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 19:29:38.955: 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.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Oct 13 19:29:39.110: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 13 19:29:39.110: INFO: Creating resource for dynamic PV
Oct 13 19:29:39.110: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5577w584z
STEP: creating a claim
Oct 13 19:29:39.144: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-g69f
STEP: Checking for subpath error in container status
Oct 13 19:29:51.307: INFO: Deleting pod "pod-subpath-test-dynamicpv-g69f" in namespace "provisioning-5577"
Oct 13 19:29:51.340: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-g69f" to be fully deleted
STEP: Deleting pod
Oct 13 19:29:55.401: INFO: Deleting pod "pod-subpath-test-dynamicpv-g69f" in namespace "provisioning-5577"
STEP: Deleting pvc
Oct 13 19:29:55.493: INFO: Deleting PersistentVolumeClaim "awsz9wcd"
... skipping 13 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.3EB0eDjiI/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.3EB0eDjiI/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath file is outside the volume [Slow][LinuxOnly]
      /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 19:29:57.680: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename volumemode
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail to use a volume in a pod with mismatched mode [Slow]
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Oct 13 19:29:57.839: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 13 19:29:57.839: INFO: Creating resource for dynamic PV
Oct 13 19:29:57.839: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-8003vn6r5
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Oct 13 19:30:04.063: INFO: Deleting pod "pod-66eb4849-f1eb-464a-be21-bfc3987fd91e" in namespace "volumemode-8003"
Oct 13 19:30:04.100: INFO: Wait up to 5m0s for pod "pod-66eb4849-f1eb-464a-be21-bfc3987fd91e" to be fully deleted
STEP: Deleting pvc
Oct 13 19:30:06.222: INFO: Deleting PersistentVolumeClaim "awsbdwqp"
Oct 13 19:30:06.254: INFO: Waiting up to 5m0s for PersistentVolume pvc-55dd0c02-1522-4d75-a74b-b4169712bc1f to get deleted
Oct 13 19:30:06.285: INFO: PersistentVolume pvc-55dd0c02-1522-4d75-a74b-b4169712bc1f found and phase=Released (30.567978ms)
... skipping 10 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.3EB0eDjiI/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.3EB0eDjiI/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
    /tmp/kops.3EB0eDjiI/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.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 144 lines ...
Oct 13 19:29:28.465: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5621xbb7p
STEP: creating a claim
Oct 13 19:29:28.496: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-n8kv
STEP: Creating a pod to test atomic-volume-subpath
Oct 13 19:29:28.593: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-n8kv" in namespace "provisioning-5621" to be "Succeeded or Failed"
Oct 13 19:29:28.624: INFO: Pod "pod-subpath-test-dynamicpv-n8kv": Phase="Pending", Reason="", readiness=false. Elapsed: 30.410762ms
Oct 13 19:29:30.659: INFO: Pod "pod-subpath-test-dynamicpv-n8kv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.065725344s
Oct 13 19:29:32.691: INFO: Pod "pod-subpath-test-dynamicpv-n8kv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.097650137s
Oct 13 19:29:34.726: INFO: Pod "pod-subpath-test-dynamicpv-n8kv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.132702264s
Oct 13 19:29:36.764: INFO: Pod "pod-subpath-test-dynamicpv-n8kv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.170530936s
Oct 13 19:29:38.795: INFO: Pod "pod-subpath-test-dynamicpv-n8kv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.201513203s
... skipping 6 lines ...
Oct 13 19:29:53.019: INFO: Pod "pod-subpath-test-dynamicpv-n8kv": Phase="Running", Reason="", readiness=true. Elapsed: 24.425115576s
Oct 13 19:29:55.050: INFO: Pod "pod-subpath-test-dynamicpv-n8kv": Phase="Running", Reason="", readiness=true. Elapsed: 26.456486588s
Oct 13 19:29:57.083: INFO: Pod "pod-subpath-test-dynamicpv-n8kv": Phase="Running", Reason="", readiness=true. Elapsed: 28.489656311s
Oct 13 19:29:59.118: INFO: Pod "pod-subpath-test-dynamicpv-n8kv": Phase="Running", Reason="", readiness=true. Elapsed: 30.524560593s
Oct 13 19:30:01.149: INFO: Pod "pod-subpath-test-dynamicpv-n8kv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 32.555743201s
STEP: Saw pod success
Oct 13 19:30:01.149: INFO: Pod "pod-subpath-test-dynamicpv-n8kv" satisfied condition "Succeeded or Failed"
Oct 13 19:30:01.182: INFO: Trying to get logs from node ip-172-20-38-144.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-n8kv container test-container-subpath-dynamicpv-n8kv: <nil>
STEP: delete the pod
Oct 13 19:30:01.260: INFO: Waiting for pod pod-subpath-test-dynamicpv-n8kv to disappear
Oct 13 19:30:01.291: INFO: Pod pod-subpath-test-dynamicpv-n8kv no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-n8kv
Oct 13 19:30:01.291: INFO: Deleting pod "pod-subpath-test-dynamicpv-n8kv" in namespace "provisioning-5621"
... skipping 60 lines ...
Oct 13 19:28:56.367: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-2539-e2e-scjqlzh      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-2539    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-2539-e2e-scjqlzh,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-2539    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-2539-e2e-scjqlzh,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-2539    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-2539-e2e-scjqlzh,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-2539-e2e-scjqlzh    813b5b30-0cc0-4c70-b4a8-23794117093a 6972 0 2021-10-13 19:28:56 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-10-13 19:28:56 +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-njbgm pvc- provisioning-2539  fad88ee2-4728-4bde-a597-647be1326b75 6976 0 2021-10-13 19:28:56 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-10-13 19:28:56 +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-2539-e2e-scjqlzh,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-2251b753-185b-4b72-ab2c-a73766122747 in namespace provisioning-2539
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Oct 13 19:29:12.716: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-xst2b" in namespace "provisioning-2539" to be "Succeeded or Failed"
Oct 13 19:29:12.746: INFO: Pod "pvc-volume-tester-writer-xst2b": Phase="Pending", Reason="", readiness=false. Elapsed: 30.27184ms
Oct 13 19:29:14.779: INFO: Pod "pvc-volume-tester-writer-xst2b": Phase="Pending", Reason="", readiness=false. Elapsed: 2.063825821s
Oct 13 19:29:16.810: INFO: Pod "pvc-volume-tester-writer-xst2b": Phase="Pending", Reason="", readiness=false. Elapsed: 4.094382525s
Oct 13 19:29:18.842: INFO: Pod "pvc-volume-tester-writer-xst2b": Phase="Pending", Reason="", readiness=false. Elapsed: 6.125906706s
Oct 13 19:29:20.872: INFO: Pod "pvc-volume-tester-writer-xst2b": Phase="Pending", Reason="", readiness=false. Elapsed: 8.156463847s
Oct 13 19:29:22.904: INFO: Pod "pvc-volume-tester-writer-xst2b": Phase="Pending", Reason="", readiness=false. Elapsed: 10.188694788s
... skipping 8 lines ...
Oct 13 19:29:41.190: INFO: Pod "pvc-volume-tester-writer-xst2b": Phase="Pending", Reason="", readiness=false. Elapsed: 28.47479992s
Oct 13 19:29:43.221: INFO: Pod "pvc-volume-tester-writer-xst2b": Phase="Pending", Reason="", readiness=false. Elapsed: 30.505742068s
Oct 13 19:29:45.253: INFO: Pod "pvc-volume-tester-writer-xst2b": Phase="Pending", Reason="", readiness=false. Elapsed: 32.53758691s
Oct 13 19:29:47.284: INFO: Pod "pvc-volume-tester-writer-xst2b": Phase="Pending", Reason="", readiness=false. Elapsed: 34.568423104s
Oct 13 19:29:49.316: INFO: Pod "pvc-volume-tester-writer-xst2b": Phase="Succeeded", Reason="", readiness=false. Elapsed: 36.599890099s
STEP: Saw pod success
Oct 13 19:29:49.316: INFO: Pod "pvc-volume-tester-writer-xst2b" satisfied condition "Succeeded or Failed"
Oct 13 19:29:49.378: INFO: Pod pvc-volume-tester-writer-xst2b has the following logs: 
Oct 13 19:29:49.378: INFO: Deleting pod "pvc-volume-tester-writer-xst2b" in namespace "provisioning-2539"
Oct 13 19:29:49.415: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-xst2b" to be fully deleted
STEP: checking the created volume has the correct mount options, is readable and retains data on the same node "ip-172-20-58-97.ca-central-1.compute.internal"
Oct 13 19:29:49.539: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-n225p" in namespace "provisioning-2539" to be "Succeeded or Failed"
Oct 13 19:29:49.569: INFO: Pod "pvc-volume-tester-reader-n225p": Phase="Pending", Reason="", readiness=false. Elapsed: 30.000025ms
Oct 13 19:29:51.600: INFO: Pod "pvc-volume-tester-reader-n225p": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061333465s
Oct 13 19:29:53.632: INFO: Pod "pvc-volume-tester-reader-n225p": Phase="Pending", Reason="", readiness=false. Elapsed: 4.092574096s
Oct 13 19:29:55.663: INFO: Pod "pvc-volume-tester-reader-n225p": Phase="Pending", Reason="", readiness=false. Elapsed: 6.1236644s
Oct 13 19:29:57.694: INFO: Pod "pvc-volume-tester-reader-n225p": Phase="Pending", Reason="", readiness=false. Elapsed: 8.155096394s
Oct 13 19:29:59.727: INFO: Pod "pvc-volume-tester-reader-n225p": Phase="Pending", Reason="", readiness=false. Elapsed: 10.187915341s
Oct 13 19:30:01.758: INFO: Pod "pvc-volume-tester-reader-n225p": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.219163234s
STEP: Saw pod success
Oct 13 19:30:01.758: INFO: Pod "pvc-volume-tester-reader-n225p" satisfied condition "Succeeded or Failed"
Oct 13 19:30:01.821: INFO: Pod pvc-volume-tester-reader-n225p has the following logs: hello world

Oct 13 19:30:01.821: INFO: Deleting pod "pvc-volume-tester-reader-n225p" in namespace "provisioning-2539"
Oct 13 19:30:01.858: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-n225p" to be fully deleted
Oct 13 19:30:01.888: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-njbgm] to have phase Bound
Oct 13 19:30:01.921: INFO: PersistentVolumeClaim pvc-njbgm found and phase=Bound (32.714494ms)
... skipping 64 lines ...

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

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

    /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 168 lines ...
Oct 13 19:30:08.328: INFO: Waiting for pod aws-client to disappear
Oct 13 19:30:08.360: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Oct 13 19:30:08.360: INFO: Deleting PersistentVolumeClaim "pvc-p5bbk"
Oct 13 19:30:08.393: INFO: Deleting PersistentVolume "aws-kttcz"
Oct 13 19:30:08.569: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0bdc1faf520ad7932", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0bdc1faf520ad7932 is currently attached to i-00168f04de77a5ce5
	status code: 400, request id: fc5cd2ad-c55d-4408-9e92-f62bfed9b191
Oct 13 19:30:13.889: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0bdc1faf520ad7932", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0bdc1faf520ad7932 is currently attached to i-00168f04de77a5ce5
	status code: 400, request id: 1a3899a5-8bce-4eb8-a3cb-4a9ceb28520e
Oct 13 19:30:19.124: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0bdc1faf520ad7932", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0bdc1faf520ad7932 is currently attached to i-00168f04de77a5ce5
	status code: 400, request id: b17742be-51e2-47ac-8672-b650d5d09c8b
Oct 13 19:30:24.375: INFO: Successfully deleted PD "aws://ca-central-1a/vol-0bdc1faf520ad7932".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 19:30:24.375: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-3971" for this suite.
... skipping 615 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.3EB0eDjiI/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.3EB0eDjiI/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.3EB0eDjiI/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.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 103 lines ...
Oct 13 19:30:10.422: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Oct 13 19:30:10.825: INFO: Successfully created a new PD: "aws://ca-central-1a/vol-08a3cbb9ff5257304".
Oct 13 19:30:10.825: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-22cz
STEP: Creating a pod to test exec-volume-test
Oct 13 19:30:10.859: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-22cz" in namespace "volume-7553" to be "Succeeded or Failed"
Oct 13 19:30:10.891: INFO: Pod "exec-volume-test-inlinevolume-22cz": Phase="Pending", Reason="", readiness=false. Elapsed: 31.146849ms
Oct 13 19:30:12.923: INFO: Pod "exec-volume-test-inlinevolume-22cz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.063865614s
Oct 13 19:30:14.956: INFO: Pod "exec-volume-test-inlinevolume-22cz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.09674344s
Oct 13 19:30:16.990: INFO: Pod "exec-volume-test-inlinevolume-22cz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.130851444s
Oct 13 19:30:19.022: INFO: Pod "exec-volume-test-inlinevolume-22cz": Phase="Pending", Reason="", readiness=false. Elapsed: 8.162770376s
Oct 13 19:30:21.053: INFO: Pod "exec-volume-test-inlinevolume-22cz": Phase="Pending", Reason="", readiness=false. Elapsed: 10.193884134s
Oct 13 19:30:23.084: INFO: Pod "exec-volume-test-inlinevolume-22cz": Phase="Pending", Reason="", readiness=false. Elapsed: 12.2249963s
Oct 13 19:30:25.116: INFO: Pod "exec-volume-test-inlinevolume-22cz": Phase="Pending", Reason="", readiness=false. Elapsed: 14.256799705s
Oct 13 19:30:27.147: INFO: Pod "exec-volume-test-inlinevolume-22cz": Phase="Pending", Reason="", readiness=false. Elapsed: 16.28802893s
Oct 13 19:30:29.179: INFO: Pod "exec-volume-test-inlinevolume-22cz": Phase="Pending", Reason="", readiness=false. Elapsed: 18.319185007s
Oct 13 19:30:31.211: INFO: Pod "exec-volume-test-inlinevolume-22cz": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.351112647s
STEP: Saw pod success
Oct 13 19:30:31.211: INFO: Pod "exec-volume-test-inlinevolume-22cz" satisfied condition "Succeeded or Failed"
Oct 13 19:30:31.241: INFO: Trying to get logs from node ip-172-20-38-144.ca-central-1.compute.internal pod exec-volume-test-inlinevolume-22cz container exec-container-inlinevolume-22cz: <nil>
STEP: delete the pod
Oct 13 19:30:31.312: INFO: Waiting for pod exec-volume-test-inlinevolume-22cz to disappear
Oct 13 19:30:31.344: INFO: Pod exec-volume-test-inlinevolume-22cz no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-22cz
Oct 13 19:30:31.344: INFO: Deleting pod "exec-volume-test-inlinevolume-22cz" in namespace "volume-7553"
Oct 13 19:30:31.500: INFO: Couldn't delete PD "aws://ca-central-1a/vol-08a3cbb9ff5257304", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08a3cbb9ff5257304 is currently attached to i-049bea91c6928b078
	status code: 400, request id: 67dcde9f-d6ba-4a8e-a8b8-1ccaa7d37143
Oct 13 19:30:36.726: INFO: Couldn't delete PD "aws://ca-central-1a/vol-08a3cbb9ff5257304", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08a3cbb9ff5257304 is currently attached to i-049bea91c6928b078
	status code: 400, request id: 9bfbcccb-74a6-480f-95bc-3adcd34940ca
Oct 13 19:30:41.941: INFO: Couldn't delete PD "aws://ca-central-1a/vol-08a3cbb9ff5257304", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08a3cbb9ff5257304 is currently attached to i-049bea91c6928b078
	status code: 400, request id: bd20fd36-7b0d-4780-924a-3ee1c4a894bf
Oct 13 19:30:47.200: INFO: Successfully deleted PD "aws://ca-central-1a/vol-08a3cbb9ff5257304".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 19:30:47.200: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-7553" for this suite.
... skipping 317 lines ...
Oct 13 19:30:10.905: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-58976cx4d
STEP: creating a claim
Oct 13 19:30:10.937: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-qb6x
STEP: Creating a pod to test subpath
Oct 13 19:30:11.035: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-qb6x" in namespace "provisioning-5897" to be "Succeeded or Failed"
Oct 13 19:30:11.065: INFO: Pod "pod-subpath-test-dynamicpv-qb6x": Phase="Pending", Reason="", readiness=false. Elapsed: 30.0101ms
Oct 13 19:30:13.097: INFO: Pod "pod-subpath-test-dynamicpv-qb6x": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061560694s
Oct 13 19:30:15.128: INFO: Pod "pod-subpath-test-dynamicpv-qb6x": Phase="Pending", Reason="", readiness=false. Elapsed: 4.093227042s
Oct 13 19:30:17.160: INFO: Pod "pod-subpath-test-dynamicpv-qb6x": Phase="Pending", Reason="", readiness=false. Elapsed: 6.124373311s
Oct 13 19:30:19.191: INFO: Pod "pod-subpath-test-dynamicpv-qb6x": Phase="Pending", Reason="", readiness=false. Elapsed: 8.155363216s
Oct 13 19:30:21.222: INFO: Pod "pod-subpath-test-dynamicpv-qb6x": Phase="Pending", Reason="", readiness=false. Elapsed: 10.186423876s
... skipping 3 lines ...
Oct 13 19:30:29.351: INFO: Pod "pod-subpath-test-dynamicpv-qb6x": Phase="Pending", Reason="", readiness=false. Elapsed: 18.315363599s
Oct 13 19:30:31.383: INFO: Pod "pod-subpath-test-dynamicpv-qb6x": Phase="Pending", Reason="", readiness=false. Elapsed: 20.347525855s
Oct 13 19:30:33.419: INFO: Pod "pod-subpath-test-dynamicpv-qb6x": Phase="Pending", Reason="", readiness=false. Elapsed: 22.383568651s
Oct 13 19:30:35.451: INFO: Pod "pod-subpath-test-dynamicpv-qb6x": Phase="Pending", Reason="", readiness=false. Elapsed: 24.416115268s
Oct 13 19:30:37.483: INFO: Pod "pod-subpath-test-dynamicpv-qb6x": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.447911561s
STEP: Saw pod success
Oct 13 19:30:37.483: INFO: Pod "pod-subpath-test-dynamicpv-qb6x" satisfied condition "Succeeded or Failed"
Oct 13 19:30:37.514: INFO: Trying to get logs from node ip-172-20-50-191.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-qb6x container test-container-volume-dynamicpv-qb6x: <nil>
STEP: delete the pod
Oct 13 19:30:37.584: INFO: Waiting for pod pod-subpath-test-dynamicpv-qb6x to disappear
Oct 13 19:30:37.614: INFO: Pod pod-subpath-test-dynamicpv-qb6x no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-qb6x
Oct 13 19:30:37.614: INFO: Deleting pod "pod-subpath-test-dynamicpv-qb6x" in namespace "provisioning-5897"
... skipping 53 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.3EB0eDjiI/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.3EB0eDjiI/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.3EB0eDjiI/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.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 90 lines ...
Oct 13 19:30:27.604: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1290-e2e-scbl5zd
STEP: creating a claim
Oct 13 19:30:27.636: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-f2w9
STEP: Creating a pod to test subpath
Oct 13 19:30:27.733: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-f2w9" in namespace "provisioning-1290" to be "Succeeded or Failed"
Oct 13 19:30:27.764: INFO: Pod "pod-subpath-test-dynamicpv-f2w9": Phase="Pending", Reason="", readiness=false. Elapsed: 31.21702ms
Oct 13 19:30:29.799: INFO: Pod "pod-subpath-test-dynamicpv-f2w9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.066417655s
Oct 13 19:30:31.832: INFO: Pod "pod-subpath-test-dynamicpv-f2w9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.098619432s
Oct 13 19:30:33.862: INFO: Pod "pod-subpath-test-dynamicpv-f2w9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.129342359s
Oct 13 19:30:35.893: INFO: Pod "pod-subpath-test-dynamicpv-f2w9": Phase="Pending", Reason="", readiness=false. Elapsed: 8.160077463s
Oct 13 19:30:37.924: INFO: Pod "pod-subpath-test-dynamicpv-f2w9": Phase="Pending", Reason="", readiness=false. Elapsed: 10.190981405s
Oct 13 19:30:39.956: INFO: Pod "pod-subpath-test-dynamicpv-f2w9": Phase="Pending", Reason="", readiness=false. Elapsed: 12.223130712s
Oct 13 19:30:41.987: INFO: Pod "pod-subpath-test-dynamicpv-f2w9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.254283302s
STEP: Saw pod success
Oct 13 19:30:41.987: INFO: Pod "pod-subpath-test-dynamicpv-f2w9" satisfied condition "Succeeded or Failed"
Oct 13 19:30:42.018: INFO: Trying to get logs from node ip-172-20-50-191.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-f2w9 container test-container-volume-dynamicpv-f2w9: <nil>
STEP: delete the pod
Oct 13 19:30:42.086: INFO: Waiting for pod pod-subpath-test-dynamicpv-f2w9 to disappear
Oct 13 19:30:42.116: INFO: Pod pod-subpath-test-dynamicpv-f2w9 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-f2w9
Oct 13 19:30:42.116: INFO: Deleting pod "pod-subpath-test-dynamicpv-f2w9" in namespace "provisioning-1290"
... skipping 52 lines ...
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 19:31:02.752: 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.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Oct 13 19:31:02.937: INFO: found topology map[topology.ebs.csi.aws.com/zone:ca-central-1a]
Oct 13 19:31:02.937: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
[AfterEach] [Testpattern: Dynamic PV (delayed binding)] topology
... skipping 4 lines ...

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

    Not enough topologies in cluster -- skipping

    /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 94 lines ...
Oct 13 19:27:55.111: INFO: Creating resource for dynamic PV
Oct 13 19:27:55.111: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-7711-e2e-sc55ssl
STEP: creating a claim
Oct 13 19:27:55.142: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Oct 13 19:27:55.237: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-6wn9n" in namespace "snapshotting-7711" to be "Succeeded or Failed"
Oct 13 19:27:55.271: INFO: Pod "pvc-snapshottable-tester-6wn9n": Phase="Pending", Reason="", readiness=false. Elapsed: 33.74787ms
Oct 13 19:27:57.307: INFO: Pod "pvc-snapshottable-tester-6wn9n": Phase="Pending", Reason="", readiness=false. Elapsed: 2.069343337s
Oct 13 19:27:59.338: INFO: Pod "pvc-snapshottable-tester-6wn9n": Phase="Pending", Reason="", readiness=false. Elapsed: 4.100956969s
Oct 13 19:28:01.369: INFO: Pod "pvc-snapshottable-tester-6wn9n": Phase="Pending", Reason="", readiness=false. Elapsed: 6.131692759s
Oct 13 19:28:03.401: INFO: Pod "pvc-snapshottable-tester-6wn9n": Phase="Pending", Reason="", readiness=false. Elapsed: 8.164069419s
Oct 13 19:28:05.432: INFO: Pod "pvc-snapshottable-tester-6wn9n": Phase="Pending", Reason="", readiness=false. Elapsed: 10.194648347s
Oct 13 19:28:07.463: INFO: Pod "pvc-snapshottable-tester-6wn9n": Phase="Pending", Reason="", readiness=false. Elapsed: 12.226248685s
Oct 13 19:28:09.498: INFO: Pod "pvc-snapshottable-tester-6wn9n": Phase="Pending", Reason="", readiness=false. Elapsed: 14.260947282s
Oct 13 19:28:11.529: INFO: Pod "pvc-snapshottable-tester-6wn9n": Phase="Pending", Reason="", readiness=false. Elapsed: 16.291542008s
Oct 13 19:28:13.560: INFO: Pod "pvc-snapshottable-tester-6wn9n": Phase="Pending", Reason="", readiness=false. Elapsed: 18.32300886s
Oct 13 19:28:15.591: INFO: Pod "pvc-snapshottable-tester-6wn9n": Phase="Pending", Reason="", readiness=false. Elapsed: 20.353774257s
Oct 13 19:28:17.622: INFO: Pod "pvc-snapshottable-tester-6wn9n": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.384274389s
STEP: Saw pod success
Oct 13 19:28:17.622: INFO: Pod "pvc-snapshottable-tester-6wn9n" satisfied condition "Succeeded or Failed"
Oct 13 19:28:17.685: INFO: Pod pvc-snapshottable-tester-6wn9n has the following logs: 
Oct 13 19:28:17.685: INFO: Deleting pod "pvc-snapshottable-tester-6wn9n" in namespace "snapshotting-7711"
Oct 13 19:28:17.729: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-6wn9n" to be fully deleted
Oct 13 19:28:17.760: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comzfgd2] to have phase Bound
Oct 13 19:28:17.790: INFO: PersistentVolumeClaim ebs.csi.aws.comzfgd2 found and phase=Bound (30.123436ms)
STEP: [init] checking the claim
... skipping 57 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.3EB0eDjiI/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
Oct 13 19:29:17.398: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-bbbdb" in namespace "snapshotting-7711" to be "Succeeded or Failed"
Oct 13 19:29:17.429: INFO: Pod "pvc-snapshottable-data-tester-bbbdb": Phase="Pending", Reason="", readiness=false. Elapsed: 30.780978ms
Oct 13 19:29:19.460: INFO: Pod "pvc-snapshottable-data-tester-bbbdb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061407392s
Oct 13 19:29:21.490: INFO: Pod "pvc-snapshottable-data-tester-bbbdb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.092017245s
Oct 13 19:29:23.526: INFO: Pod "pvc-snapshottable-data-tester-bbbdb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.127434472s
Oct 13 19:29:25.556: INFO: Pod "pvc-snapshottable-data-tester-bbbdb": Phase="Pending", Reason="", readiness=false. Elapsed: 8.157860177s
Oct 13 19:29:27.587: INFO: Pod "pvc-snapshottable-data-tester-bbbdb": Phase="Pending", Reason="", readiness=false. Elapsed: 10.188904086s
Oct 13 19:29:29.619: INFO: Pod "pvc-snapshottable-data-tester-bbbdb": Phase="Pending", Reason="", readiness=false. Elapsed: 12.220489258s
Oct 13 19:29:31.651: INFO: Pod "pvc-snapshottable-data-tester-bbbdb": Phase="Pending", Reason="", readiness=false. Elapsed: 14.252515236s
Oct 13 19:29:33.689: INFO: Pod "pvc-snapshottable-data-tester-bbbdb": Phase="Pending", Reason="", readiness=false. Elapsed: 16.290418725s
Oct 13 19:29:35.723: INFO: Pod "pvc-snapshottable-data-tester-bbbdb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.324458916s
STEP: Saw pod success
Oct 13 19:29:35.723: INFO: Pod "pvc-snapshottable-data-tester-bbbdb" satisfied condition "Succeeded or Failed"
Oct 13 19:29:35.787: INFO: Pod pvc-snapshottable-data-tester-bbbdb has the following logs: 
Oct 13 19:29:35.787: INFO: Deleting pod "pvc-snapshottable-data-tester-bbbdb" in namespace "snapshotting-7711"
Oct 13 19:29:35.825: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-bbbdb" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Oct 13 19:29:53.987: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-b6f7c24027-45100.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-7711 exec restored-pvc-tester-cf7lh --namespace=snapshotting-7711 -- cat /mnt/test/data'
... skipping 33 lines ...
Oct 13 19:30:19.320: INFO: volumesnapshotcontents pre-provisioned-snapcontent-a86ff624-ee80-40ab-879f-01c2ab881774 has been found and is not deleted
Oct 13 19:30:20.351: INFO: volumesnapshotcontents pre-provisioned-snapcontent-a86ff624-ee80-40ab-879f-01c2ab881774 has been found and is not deleted
Oct 13 19:30:21.384: INFO: volumesnapshotcontents pre-provisioned-snapcontent-a86ff624-ee80-40ab-879f-01c2ab881774 has been found and is not deleted
Oct 13 19:30:22.415: INFO: volumesnapshotcontents pre-provisioned-snapcontent-a86ff624-ee80-40ab-879f-01c2ab881774 has been found and is not deleted
Oct 13 19:30:23.447: INFO: volumesnapshotcontents pre-provisioned-snapcontent-a86ff624-ee80-40ab-879f-01c2ab881774 has been found and is not deleted
Oct 13 19:30:24.482: INFO: volumesnapshotcontents pre-provisioned-snapcontent-a86ff624-ee80-40ab-879f-01c2ab881774 has been found and is not deleted
Oct 13 19:30:25.483: INFO: WaitUntil failed after reaching the timeout 30s
[AfterEach] volume snapshot controller
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:221
Oct 13 19:30:25.515: INFO: Pod restored-pvc-tester-cf7lh has the following logs: 
Oct 13 19:30:25.515: INFO: Deleting pod "restored-pvc-tester-cf7lh" in namespace "snapshotting-7711"
Oct 13 19:30:25.548: INFO: Wait up to 5m0s for pod "restored-pvc-tester-cf7lh" to be fully deleted
Oct 13 19:30:57.609: INFO: deleting claim "snapshotting-7711"/"pvc-5n8rh"
... skipping 36 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 19:30:16.450: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename provisioning
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly]
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Oct 13 19:30:16.603: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 13 19:30:16.603: INFO: Creating resource for dynamic PV
Oct 13 19:30:16.604: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6395ss2gk
STEP: creating a claim
Oct 13 19:30:16.634: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-2v47
STEP: Checking for subpath error in container status
Oct 13 19:30:42.797: INFO: Deleting pod "pod-subpath-test-dynamicpv-2v47" in namespace "provisioning-6395"
Oct 13 19:30:42.830: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-2v47" to be fully deleted
STEP: Deleting pod
Oct 13 19:30:44.898: INFO: Deleting pod "pod-subpath-test-dynamicpv-2v47" in namespace "provisioning-6395"
STEP: Deleting pvc
Oct 13 19:30:44.996: INFO: Deleting PersistentVolumeClaim "awssp7zz"
... skipping 15 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.3EB0eDjiI/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.3EB0eDjiI/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.3EB0eDjiI/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.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [sig-storage] vsphere statefulset [Feature:vsphere]
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 19:31:10.321: INFO: >>> kubeConfig: /root/.kube/config
... skipping 83 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.3EB0eDjiI/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.3EB0eDjiI/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.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 51 lines ...
STEP: Deleting pod aws-client in namespace volume-7476
Oct 13 19:30:50.697: INFO: Waiting for pod aws-client to disappear
Oct 13 19:30:50.728: INFO: Pod aws-client still exists
Oct 13 19:30:52.730: INFO: Waiting for pod aws-client to disappear
Oct 13 19:30:52.760: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Oct 13 19:30:52.875: INFO: Couldn't delete PD "aws://ca-central-1a/vol-094162cfa5a0c5466", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-094162cfa5a0c5466 is currently attached to i-049bea91c6928b078
	status code: 400, request id: 4783ab4c-54ff-4b8c-9fb6-3fbecce7636a
Oct 13 19:30:58.120: INFO: Couldn't delete PD "aws://ca-central-1a/vol-094162cfa5a0c5466", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-094162cfa5a0c5466 is currently attached to i-049bea91c6928b078
	status code: 400, request id: 003a0e78-13ba-4952-af5c-a217996867fe
Oct 13 19:31:03.357: INFO: Couldn't delete PD "aws://ca-central-1a/vol-094162cfa5a0c5466", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-094162cfa5a0c5466 is currently attached to i-049bea91c6928b078
	status code: 400, request id: 52d8db8f-e353-448e-b2e1-ec778cb21047
Oct 13 19:31:08.777: INFO: Couldn't delete PD "aws://ca-central-1a/vol-094162cfa5a0c5466", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-094162cfa5a0c5466 is currently attached to i-049bea91c6928b078
	status code: 400, request id: dd2f7e79-2544-43c3-bce7-50cd89a4c705
Oct 13 19:31:14.029: INFO: Successfully deleted PD "aws://ca-central-1a/vol-094162cfa5a0c5466".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 19:31:14.029: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-7476" for this suite.
... skipping 126 lines ...
Oct 13 19:30:21.906: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5024-e2e-sc4h7c6
STEP: creating a claim
Oct 13 19:30:21.941: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-x2p7
STEP: Creating a pod to test subpath
Oct 13 19:30:22.038: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-x2p7" in namespace "provisioning-5024" to be "Succeeded or Failed"
Oct 13 19:30:22.069: INFO: Pod "pod-subpath-test-dynamicpv-x2p7": Phase="Pending", Reason="", readiness=false. Elapsed: 30.672548ms
Oct 13 19:30:24.100: INFO: Pod "pod-subpath-test-dynamicpv-x2p7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062530991s
Oct 13 19:30:26.132: INFO: Pod "pod-subpath-test-dynamicpv-x2p7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.093648712s
Oct 13 19:30:28.168: INFO: Pod "pod-subpath-test-dynamicpv-x2p7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.12970654s
Oct 13 19:30:30.199: INFO: Pod "pod-subpath-test-dynamicpv-x2p7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.16097347s
Oct 13 19:30:32.232: INFO: Pod "pod-subpath-test-dynamicpv-x2p7": Phase="Pending", Reason="", readiness=false. Elapsed: 10.194261506s
Oct 13 19:30:34.264: INFO: Pod "pod-subpath-test-dynamicpv-x2p7": Phase="Pending", Reason="", readiness=false. Elapsed: 12.225698934s
Oct 13 19:30:36.296: INFO: Pod "pod-subpath-test-dynamicpv-x2p7": Phase="Pending", Reason="", readiness=false. Elapsed: 14.257655841s
Oct 13 19:30:38.328: INFO: Pod "pod-subpath-test-dynamicpv-x2p7": Phase="Pending", Reason="", readiness=false. Elapsed: 16.289719644s
Oct 13 19:30:40.359: INFO: Pod "pod-subpath-test-dynamicpv-x2p7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.320697444s
STEP: Saw pod success
Oct 13 19:30:40.359: INFO: Pod "pod-subpath-test-dynamicpv-x2p7" satisfied condition "Succeeded or Failed"
Oct 13 19:30:40.390: INFO: Trying to get logs from node ip-172-20-38-144.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-x2p7 container test-container-subpath-dynamicpv-x2p7: <nil>
STEP: delete the pod
Oct 13 19:30:40.459: INFO: Waiting for pod pod-subpath-test-dynamicpv-x2p7 to disappear
Oct 13 19:30:40.490: INFO: Pod pod-subpath-test-dynamicpv-x2p7 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-x2p7
Oct 13 19:30:40.490: INFO: Deleting pod "pod-subpath-test-dynamicpv-x2p7" in namespace "provisioning-5024"
... skipping 432 lines ...

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

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

    /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 268 lines ...
Oct 13 19:30:52.975: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-3691rwz57
STEP: creating a claim
Oct 13 19:30:53.006: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-w8db
STEP: Creating a pod to test exec-volume-test
Oct 13 19:30:53.104: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-w8db" in namespace "volume-3691" to be "Succeeded or Failed"
Oct 13 19:30:53.135: INFO: Pod "exec-volume-test-dynamicpv-w8db": Phase="Pending", Reason="", readiness=false. Elapsed: 30.91357ms
Oct 13 19:30:55.166: INFO: Pod "exec-volume-test-dynamicpv-w8db": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062556376s
Oct 13 19:30:57.201: INFO: Pod "exec-volume-test-dynamicpv-w8db": Phase="Pending", Reason="", readiness=false. Elapsed: 4.097042922s
Oct 13 19:30:59.233: INFO: Pod "exec-volume-test-dynamicpv-w8db": Phase="Pending", Reason="", readiness=false. Elapsed: 6.128950105s
Oct 13 19:31:01.264: INFO: Pod "exec-volume-test-dynamicpv-w8db": Phase="Pending", Reason="", readiness=false. Elapsed: 8.160155863s
Oct 13 19:31:03.301: INFO: Pod "exec-volume-test-dynamicpv-w8db": Phase="Pending", Reason="", readiness=false. Elapsed: 10.196964332s
Oct 13 19:31:05.333: INFO: Pod "exec-volume-test-dynamicpv-w8db": Phase="Pending", Reason="", readiness=false. Elapsed: 12.228879806s
Oct 13 19:31:07.365: INFO: Pod "exec-volume-test-dynamicpv-w8db": Phase="Pending", Reason="", readiness=false. Elapsed: 14.2607041s
Oct 13 19:31:09.397: INFO: Pod "exec-volume-test-dynamicpv-w8db": Phase="Pending", Reason="", readiness=false. Elapsed: 16.29307957s
Oct 13 19:31:11.429: INFO: Pod "exec-volume-test-dynamicpv-w8db": Phase="Pending", Reason="", readiness=false. Elapsed: 18.325389076s
Oct 13 19:31:13.461: INFO: Pod "exec-volume-test-dynamicpv-w8db": Phase="Pending", Reason="", readiness=false. Elapsed: 20.35680285s
Oct 13 19:31:15.492: INFO: Pod "exec-volume-test-dynamicpv-w8db": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.388152256s
STEP: Saw pod success
Oct 13 19:31:15.492: INFO: Pod "exec-volume-test-dynamicpv-w8db" satisfied condition "Succeeded or Failed"
Oct 13 19:31:15.527: INFO: Trying to get logs from node ip-172-20-38-144.ca-central-1.compute.internal pod exec-volume-test-dynamicpv-w8db container exec-container-dynamicpv-w8db: <nil>
STEP: delete the pod
Oct 13 19:31:15.606: INFO: Waiting for pod exec-volume-test-dynamicpv-w8db to disappear
Oct 13 19:31:15.639: INFO: Pod exec-volume-test-dynamicpv-w8db no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-w8db
Oct 13 19:31:15.639: INFO: Deleting pod "exec-volume-test-dynamicpv-w8db" in namespace "volume-3691"
... skipping 206 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.3EB0eDjiI/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.3EB0eDjiI/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.3EB0eDjiI/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.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 232 lines ...
Oct 13 19:31:16.168: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-27962wdwp
STEP: creating a claim
Oct 13 19:31:16.199: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-l2tm
STEP: Creating a pod to test subpath
Oct 13 19:31:16.302: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-l2tm" in namespace "provisioning-2796" to be "Succeeded or Failed"
Oct 13 19:31:16.334: INFO: Pod "pod-subpath-test-dynamicpv-l2tm": Phase="Pending", Reason="", readiness=false. Elapsed: 32.037625ms
Oct 13 19:31:18.373: INFO: Pod "pod-subpath-test-dynamicpv-l2tm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.071087835s
Oct 13 19:31:20.405: INFO: Pod "pod-subpath-test-dynamicpv-l2tm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.102905996s
Oct 13 19:31:22.438: INFO: Pod "pod-subpath-test-dynamicpv-l2tm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.135676712s
Oct 13 19:31:24.470: INFO: Pod "pod-subpath-test-dynamicpv-l2tm": Phase="Pending", Reason="", readiness=false. Elapsed: 8.168251477s
Oct 13 19:31:26.508: INFO: Pod "pod-subpath-test-dynamicpv-l2tm": Phase="Pending", Reason="", readiness=false. Elapsed: 10.205537766s
Oct 13 19:31:28.545: INFO: Pod "pod-subpath-test-dynamicpv-l2tm": Phase="Pending", Reason="", readiness=false. Elapsed: 12.242459463s
Oct 13 19:31:30.580: INFO: Pod "pod-subpath-test-dynamicpv-l2tm": Phase="Pending", Reason="", readiness=false. Elapsed: 14.278368202s
Oct 13 19:31:32.612: INFO: Pod "pod-subpath-test-dynamicpv-l2tm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.310155536s
STEP: Saw pod success
Oct 13 19:31:32.612: INFO: Pod "pod-subpath-test-dynamicpv-l2tm" satisfied condition "Succeeded or Failed"
Oct 13 19:31:32.643: INFO: Trying to get logs from node ip-172-20-50-191.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-l2tm container test-container-subpath-dynamicpv-l2tm: <nil>
STEP: delete the pod
Oct 13 19:31:32.715: INFO: Waiting for pod pod-subpath-test-dynamicpv-l2tm to disappear
Oct 13 19:31:32.745: INFO: Pod pod-subpath-test-dynamicpv-l2tm no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-l2tm
Oct 13 19:31:32.745: INFO: Deleting pod "pod-subpath-test-dynamicpv-l2tm" in namespace "provisioning-2796"
... skipping 33 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.3EB0eDjiI/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.3EB0eDjiI/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.3EB0eDjiI/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.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 6 lines ...

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 2 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 19:31:25.987: 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.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Oct 13 19:31:26.143: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Oct 13 19:31:26.529: INFO: Successfully created a new PD: "aws://ca-central-1a/vol-02a0aa27bf7b4f6a1".
Oct 13 19:31:26.529: INFO: Creating resource for pre-provisioned PV
Oct 13 19:31:26.530: INFO: Creating PVC and PV
... skipping 4 lines ...
Oct 13 19:31:28.671: INFO: PersistentVolumeClaim pvc-k2t69 found but phase is Pending instead of Bound.
Oct 13 19:31:30.703: INFO: PersistentVolumeClaim pvc-k2t69 found but phase is Pending instead of Bound.
Oct 13 19:31:32.738: INFO: PersistentVolumeClaim pvc-k2t69 found and phase=Bound (6.140327114s)
Oct 13 19:31:32.738: INFO: Waiting up to 3m0s for PersistentVolume aws-q9wd2 to have phase Bound
Oct 13 19:31:32.769: INFO: PersistentVolume aws-q9wd2 found and phase=Bound (31.008312ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Oct 13 19:31:34.960: INFO: Deleting pod "pod-a28a2c73-048d-4e35-bb62-eddd3acc70dc" in namespace "volumemode-4573"
Oct 13 19:31:34.993: INFO: Wait up to 5m0s for pod "pod-a28a2c73-048d-4e35-bb62-eddd3acc70dc" to be fully deleted
STEP: Deleting pv and pvc
Oct 13 19:31:39.066: INFO: Deleting PersistentVolumeClaim "pvc-k2t69"
Oct 13 19:31:39.106: INFO: Deleting PersistentVolume "aws-q9wd2"
Oct 13 19:31:39.274: INFO: Couldn't delete PD "aws://ca-central-1a/vol-02a0aa27bf7b4f6a1", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02a0aa27bf7b4f6a1 is currently attached to i-0ffcb4d54aeaf8020
	status code: 400, request id: 95207e17-b0e4-4047-8595-a15cd335574d
Oct 13 19:31:44.536: INFO: Successfully deleted PD "aws://ca-central-1a/vol-02a0aa27bf7b4f6a1".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 19:31:44.536: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-4573" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.3EB0eDjiI/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.3EB0eDjiI/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
    /tmp/kops.3EB0eDjiI/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.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Oct 13 19:31:44.601: INFO: Driver ebs.csi.aws.com doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
... skipping 73 lines ...
Oct 13 19:31:20.637: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-3270tbtld
STEP: creating a claim
Oct 13 19:31:20.668: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Oct 13 19:31:20.734: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Oct 13 19:31:20.796: INFO: Error updating pvc aws8xwbx: PersistentVolumeClaim "aws8xwbx" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3270tbtld",
  	... // 3 identical fields
  }

Oct 13 19:31:22.858: INFO: Error updating pvc aws8xwbx: PersistentVolumeClaim "aws8xwbx" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3270tbtld",
  	... // 3 identical fields
  }

Oct 13 19:31:24.860: INFO: Error updating pvc aws8xwbx: PersistentVolumeClaim "aws8xwbx" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3270tbtld",
  	... // 3 identical fields
  }

Oct 13 19:31:26.869: INFO: Error updating pvc aws8xwbx: PersistentVolumeClaim "aws8xwbx" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3270tbtld",
  	... // 3 identical fields
  }

Oct 13 19:31:28.862: INFO: Error updating pvc aws8xwbx: PersistentVolumeClaim "aws8xwbx" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3270tbtld",
  	... // 3 identical fields
  }

Oct 13 19:31:30.861: INFO: Error updating pvc aws8xwbx: PersistentVolumeClaim "aws8xwbx" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3270tbtld",
  	... // 3 identical fields
  }

Oct 13 19:31:32.858: INFO: Error updating pvc aws8xwbx: PersistentVolumeClaim "aws8xwbx" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3270tbtld",
  	... // 3 identical fields
  }

Oct 13 19:31:34.860: INFO: Error updating pvc aws8xwbx: PersistentVolumeClaim "aws8xwbx" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3270tbtld",
  	... // 3 identical fields
  }

Oct 13 19:31:36.859: INFO: Error updating pvc aws8xwbx: PersistentVolumeClaim "aws8xwbx" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3270tbtld",
  	... // 3 identical fields
  }

Oct 13 19:31:38.858: INFO: Error updating pvc aws8xwbx: PersistentVolumeClaim "aws8xwbx" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3270tbtld",
  	... // 3 identical fields
  }

Oct 13 19:31:40.859: INFO: Error updating pvc aws8xwbx: PersistentVolumeClaim "aws8xwbx" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3270tbtld",
  	... // 3 identical fields
  }

Oct 13 19:31:42.859: INFO: Error updating pvc aws8xwbx: PersistentVolumeClaim "aws8xwbx" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3270tbtld",
  	... // 3 identical fields
  }

Oct 13 19:31:44.860: INFO: Error updating pvc aws8xwbx: PersistentVolumeClaim "aws8xwbx" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3270tbtld",
  	... // 3 identical fields
  }

Oct 13 19:31:46.859: INFO: Error updating pvc aws8xwbx: PersistentVolumeClaim "aws8xwbx" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3270tbtld",
  	... // 3 identical fields
  }

Oct 13 19:31:48.861: INFO: Error updating pvc aws8xwbx: PersistentVolumeClaim "aws8xwbx" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3270tbtld",
  	... // 3 identical fields
  }

Oct 13 19:31:50.865: INFO: Error updating pvc aws8xwbx: PersistentVolumeClaim "aws8xwbx" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3270tbtld",
  	... // 3 identical fields
  }

Oct 13 19:31:50.926: INFO: Error updating pvc aws8xwbx: PersistentVolumeClaim "aws8xwbx" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 117 lines ...
Oct 13 19:31:32.539: INFO: Pod aws-client still exists
Oct 13 19:31:34.539: INFO: Waiting for pod aws-client to disappear
Oct 13 19:31:34.570: INFO: Pod aws-client still exists
Oct 13 19:31:36.540: INFO: Waiting for pod aws-client to disappear
Oct 13 19:31:36.571: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Oct 13 19:31:36.689: INFO: Couldn't delete PD "aws://ca-central-1a/vol-02965cbd725066c11", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02965cbd725066c11 is currently attached to i-05786989bd674e173
	status code: 400, request id: 9fc5eb88-48ae-4629-8f58-be1bcbe35ba2
Oct 13 19:31:41.962: INFO: Couldn't delete PD "aws://ca-central-1a/vol-02965cbd725066c11", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02965cbd725066c11 is currently attached to i-05786989bd674e173
	status code: 400, request id: 93301f9a-e992-40b1-b67c-aff418e61054
Oct 13 19:31:47.241: INFO: Couldn't delete PD "aws://ca-central-1a/vol-02965cbd725066c11", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02965cbd725066c11 is currently attached to i-05786989bd674e173
	status code: 400, request id: 695f5f96-6eec-4daa-90df-07b78d1e5c00
Oct 13 19:31:52.521: INFO: Successfully deleted PD "aws://ca-central-1a/vol-02965cbd725066c11".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 19:31:52.522: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8952" for this suite.
... skipping 297 lines ...
Oct 13 19:28:40.719: INFO: Creating resource for dynamic PV
Oct 13 19:28:40.719: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-688-e2e-schk2nx
STEP: creating a claim
Oct 13 19:28:40.750: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Oct 13 19:28:40.845: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-qr9wh" in namespace "snapshotting-688" to be "Succeeded or Failed"
Oct 13 19:28:40.875: INFO: Pod "pvc-snapshottable-tester-qr9wh": Phase="Pending", Reason="", readiness=false. Elapsed: 30.547541ms
Oct 13 19:28:42.907: INFO: Pod "pvc-snapshottable-tester-qr9wh": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061975396s
Oct 13 19:28:44.938: INFO: Pod "pvc-snapshottable-tester-qr9wh": Phase="Pending", Reason="", readiness=false. Elapsed: 4.093556515s
Oct 13 19:28:46.970: INFO: Pod "pvc-snapshottable-tester-qr9wh": Phase="Pending", Reason="", readiness=false. Elapsed: 6.124695286s
Oct 13 19:28:49.001: INFO: Pod "pvc-snapshottable-tester-qr9wh": Phase="Pending", Reason="", readiness=false. Elapsed: 8.15623183s
Oct 13 19:28:51.033: INFO: Pod "pvc-snapshottable-tester-qr9wh": Phase="Pending", Reason="", readiness=false. Elapsed: 10.188056045s
... skipping 2 lines ...
Oct 13 19:28:57.129: INFO: Pod "pvc-snapshottable-tester-qr9wh": Phase="Pending", Reason="", readiness=false. Elapsed: 16.283845999s
Oct 13 19:28:59.160: INFO: Pod "pvc-snapshottable-tester-qr9wh": Phase="Pending", Reason="", readiness=false. Elapsed: 18.31552959s
Oct 13 19:29:01.229: INFO: Pod "pvc-snapshottable-tester-qr9wh": Phase="Pending", Reason="", readiness=false. Elapsed: 20.383806755s
Oct 13 19:29:03.266: INFO: Pod "pvc-snapshottable-tester-qr9wh": Phase="Pending", Reason="", readiness=false. Elapsed: 22.420922578s
Oct 13 19:29:05.299: INFO: Pod "pvc-snapshottable-tester-qr9wh": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.454130133s
STEP: Saw pod success
Oct 13 19:29:05.299: INFO: Pod "pvc-snapshottable-tester-qr9wh" satisfied condition "Succeeded or Failed"
Oct 13 19:29:05.363: INFO: Pod pvc-snapshottable-tester-qr9wh has the following logs: 
Oct 13 19:29:05.363: INFO: Deleting pod "pvc-snapshottable-tester-qr9wh" in namespace "snapshotting-688"
Oct 13 19:29:05.398: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-qr9wh" to be fully deleted
Oct 13 19:29:05.429: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comgbkmt] to have phase Bound
Oct 13 19:29:05.459: INFO: PersistentVolumeClaim ebs.csi.aws.comgbkmt found and phase=Bound (30.204412ms)
STEP: [init] checking the claim
... skipping 51 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.3EB0eDjiI/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
Oct 13 19:30:29.197: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-2wp7s" in namespace "snapshotting-688" to be "Succeeded or Failed"
Oct 13 19:30:29.228: INFO: Pod "pvc-snapshottable-data-tester-2wp7s": Phase="Pending", Reason="", readiness=false. Elapsed: 31.303594ms
Oct 13 19:30:31.259: INFO: Pod "pvc-snapshottable-data-tester-2wp7s": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061935654s
Oct 13 19:30:33.292: INFO: Pod "pvc-snapshottable-data-tester-2wp7s": Phase="Pending", Reason="", readiness=false. Elapsed: 4.095014014s
Oct 13 19:30:35.324: INFO: Pod "pvc-snapshottable-data-tester-2wp7s": Phase="Pending", Reason="", readiness=false. Elapsed: 6.126638854s
Oct 13 19:30:37.356: INFO: Pod "pvc-snapshottable-data-tester-2wp7s": Phase="Pending", Reason="", readiness=false. Elapsed: 8.158580461s
Oct 13 19:30:39.387: INFO: Pod "pvc-snapshottable-data-tester-2wp7s": Phase="Pending", Reason="", readiness=false. Elapsed: 10.189800881s
Oct 13 19:30:41.419: INFO: Pod "pvc-snapshottable-data-tester-2wp7s": Phase="Pending", Reason="", readiness=false. Elapsed: 12.221425678s
Oct 13 19:30:43.455: INFO: Pod "pvc-snapshottable-data-tester-2wp7s": Phase="Pending", Reason="", readiness=false. Elapsed: 14.257949016s
Oct 13 19:30:45.486: INFO: Pod "pvc-snapshottable-data-tester-2wp7s": Phase="Pending", Reason="", readiness=false. Elapsed: 16.289075506s
Oct 13 19:30:47.520: INFO: Pod "pvc-snapshottable-data-tester-2wp7s": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.322687677s
STEP: Saw pod success
Oct 13 19:30:47.520: INFO: Pod "pvc-snapshottable-data-tester-2wp7s" satisfied condition "Succeeded or Failed"
Oct 13 19:30:47.583: INFO: Pod pvc-snapshottable-data-tester-2wp7s has the following logs: 
Oct 13 19:30:47.583: INFO: Deleting pod "pvc-snapshottable-data-tester-2wp7s" in namespace "snapshotting-688"
Oct 13 19:30:47.621: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-2wp7s" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Oct 13 19:31:25.795: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-b6f7c24027-45100.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-688 exec restored-pvc-tester-dlndz --namespace=snapshotting-688 -- cat /mnt/test/data'
... skipping 171 lines ...
Oct 13 19:31:26.618: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-84642lk4k
STEP: creating a claim
Oct 13 19:31:26.650: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-58bm
STEP: Creating a pod to test subpath
Oct 13 19:31:26.753: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-58bm" in namespace "provisioning-8464" to be "Succeeded or Failed"
Oct 13 19:31:26.784: INFO: Pod "pod-subpath-test-dynamicpv-58bm": Phase="Pending", Reason="", readiness=false. Elapsed: 30.66132ms
Oct 13 19:31:28.822: INFO: Pod "pod-subpath-test-dynamicpv-58bm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.069014134s
Oct 13 19:31:30.853: INFO: Pod "pod-subpath-test-dynamicpv-58bm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.100221548s
Oct 13 19:31:32.891: INFO: Pod "pod-subpath-test-dynamicpv-58bm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.137399544s
Oct 13 19:31:34.922: INFO: Pod "pod-subpath-test-dynamicpv-58bm": Phase="Pending", Reason="", readiness=false. Elapsed: 8.168596753s
Oct 13 19:31:36.953: INFO: Pod "pod-subpath-test-dynamicpv-58bm": Phase="Pending", Reason="", readiness=false. Elapsed: 10.199813586s
Oct 13 19:31:38.984: INFO: Pod "pod-subpath-test-dynamicpv-58bm": Phase="Pending", Reason="", readiness=false. Elapsed: 12.230830961s
Oct 13 19:31:41.015: INFO: Pod "pod-subpath-test-dynamicpv-58bm": Phase="Pending", Reason="", readiness=false. Elapsed: 14.261935488s
Oct 13 19:31:43.046: INFO: Pod "pod-subpath-test-dynamicpv-58bm": Phase="Pending", Reason="", readiness=false. Elapsed: 16.292962121s
Oct 13 19:31:45.079: INFO: Pod "pod-subpath-test-dynamicpv-58bm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.325646098s
STEP: Saw pod success
Oct 13 19:31:45.079: INFO: Pod "pod-subpath-test-dynamicpv-58bm" satisfied condition "Succeeded or Failed"
Oct 13 19:31:45.110: INFO: Trying to get logs from node ip-172-20-38-144.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-58bm container test-container-subpath-dynamicpv-58bm: <nil>
STEP: delete the pod
Oct 13 19:31:45.181: INFO: Waiting for pod pod-subpath-test-dynamicpv-58bm to disappear
Oct 13 19:31:45.212: INFO: Pod pod-subpath-test-dynamicpv-58bm no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-58bm
Oct 13 19:31:45.212: INFO: Deleting pod "pod-subpath-test-dynamicpv-58bm" in namespace "provisioning-8464"
... skipping 216 lines ...
Oct 13 19:32:11.160: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 99 lines ...
Oct 13 19:31:52.188: INFO: Pod aws-client still exists
Oct 13 19:31:54.188: INFO: Waiting for pod aws-client to disappear
Oct 13 19:31:54.223: INFO: Pod aws-client still exists
Oct 13 19:31:56.188: INFO: Waiting for pod aws-client to disappear
Oct 13 19:31:56.219: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Oct 13 19:31:56.333: INFO: Couldn't delete PD "aws://ca-central-1a/vol-09b9254b692bf938d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-09b9254b692bf938d is currently attached to i-049bea91c6928b078
	status code: 400, request id: 4787ed21-6601-4652-8773-f2e5365dc957
Oct 13 19:32:01.580: INFO: Couldn't delete PD "aws://ca-central-1a/vol-09b9254b692bf938d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-09b9254b692bf938d is currently attached to i-049bea91c6928b078
	status code: 400, request id: d6195488-5408-4a6e-b46e-9c73559c7f40
Oct 13 19:32:06.824: INFO: Couldn't delete PD "aws://ca-central-1a/vol-09b9254b692bf938d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-09b9254b692bf938d is currently attached to i-049bea91c6928b078
	status code: 400, request id: 499a8bb8-9810-41c2-bf6a-169085e54184
Oct 13 19:32:12.087: INFO: Successfully deleted PD "aws://ca-central-1a/vol-09b9254b692bf938d".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 19:32:12.087: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-5123" for this suite.
... skipping 93 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.3EB0eDjiI/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.3EB0eDjiI/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.3EB0eDjiI/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.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 72 lines ...
Oct 13 19:31:43.256: INFO: Creating resource for dynamic PV
Oct 13 19:31:43.256: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-8130ftghv
STEP: creating a claim
STEP: Expanding non-expandable pvc
Oct 13 19:31:43.364: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Oct 13 19:31:43.429: INFO: Error updating pvc awshxbmb: PersistentVolumeClaim "awshxbmb" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8130ftghv",
  	... // 3 identical fields
  }

Oct 13 19:31:45.491: INFO: Error updating pvc awshxbmb: PersistentVolumeClaim "awshxbmb" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8130ftghv",
  	... // 3 identical fields
  }

Oct 13 19:31:47.493: INFO: Error updating pvc awshxbmb: PersistentVolumeClaim "awshxbmb" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8130ftghv",
  	... // 3 identical fields
  }

Oct 13 19:31:49.491: INFO: Error updating pvc awshxbmb: PersistentVolumeClaim "awshxbmb" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8130ftghv",
  	... // 3 identical fields
  }

Oct 13 19:31:51.491: INFO: Error updating pvc awshxbmb: PersistentVolumeClaim "awshxbmb" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8130ftghv",
  	... // 3 identical fields
  }

Oct 13 19:31:53.492: INFO: Error updating pvc awshxbmb: PersistentVolumeClaim "awshxbmb" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8130ftghv",
  	... // 3 identical fields
  }

Oct 13 19:31:55.491: INFO: Error updating pvc awshxbmb: PersistentVolumeClaim "awshxbmb" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8130ftghv",
  	... // 3 identical fields
  }

Oct 13 19:31:57.493: INFO: Error updating pvc awshxbmb: PersistentVolumeClaim "awshxbmb" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8130ftghv",
  	... // 3 identical fields
  }

Oct 13 19:31:59.492: INFO: Error updating pvc awshxbmb: PersistentVolumeClaim "awshxbmb" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8130ftghv",
  	... // 3 identical fields
  }

Oct 13 19:32:01.491: INFO: Error updating pvc awshxbmb: PersistentVolumeClaim "awshxbmb" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8130ftghv",
  	... // 3 identical fields
  }

Oct 13 19:32:03.501: INFO: Error updating pvc awshxbmb: PersistentVolumeClaim "awshxbmb" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8130ftghv",
  	... // 3 identical fields
  }

Oct 13 19:32:05.492: INFO: Error updating pvc awshxbmb: PersistentVolumeClaim "awshxbmb" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8130ftghv",
  	... // 3 identical fields
  }

Oct 13 19:32:07.491: INFO: Error updating pvc awshxbmb: PersistentVolumeClaim "awshxbmb" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8130ftghv",
  	... // 3 identical fields
  }

Oct 13 19:32:09.491: INFO: Error updating pvc awshxbmb: PersistentVolumeClaim "awshxbmb" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8130ftghv",
  	... // 3 identical fields
  }

Oct 13 19:32:11.499: INFO: Error updating pvc awshxbmb: PersistentVolumeClaim "awshxbmb" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8130ftghv",
  	... // 3 identical fields
  }

Oct 13 19:32:13.493: INFO: Error updating pvc awshxbmb: PersistentVolumeClaim "awshxbmb" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8130ftghv",
  	... // 3 identical fields
  }

Oct 13 19:32:13.556: INFO: Error updating pvc awshxbmb: PersistentVolumeClaim "awshxbmb" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 89 lines ...
Oct 13 19:31:52.510: INFO: Waiting for pod aws-client to disappear
Oct 13 19:31:52.541: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Oct 13 19:31:52.541: INFO: Deleting PersistentVolumeClaim "pvc-79xwx"
Oct 13 19:31:52.572: INFO: Deleting PersistentVolume "aws-f8744"
Oct 13 19:31:52.767: INFO: Couldn't delete PD "aws://ca-central-1a/vol-018621daabbcaffd3", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-018621daabbcaffd3 is currently attached to i-0ffcb4d54aeaf8020
	status code: 400, request id: 107d6fa8-a319-4be2-a72b-1ae3a142c9f4
Oct 13 19:31:58.048: INFO: Couldn't delete PD "aws://ca-central-1a/vol-018621daabbcaffd3", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-018621daabbcaffd3 is currently attached to i-0ffcb4d54aeaf8020
	status code: 400, request id: 7ab493e0-0ba2-4baf-82ff-ddb4ae94ef57
Oct 13 19:32:03.360: INFO: Couldn't delete PD "aws://ca-central-1a/vol-018621daabbcaffd3", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-018621daabbcaffd3 is currently attached to i-0ffcb4d54aeaf8020
	status code: 400, request id: b0d086b2-b18e-4a7f-b236-a51501055649
Oct 13 19:32:08.598: INFO: Couldn't delete PD "aws://ca-central-1a/vol-018621daabbcaffd3", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-018621daabbcaffd3 is currently attached to i-0ffcb4d54aeaf8020
	status code: 400, request id: f2141f0e-10be-4307-ba35-2cf70460cbc1
Oct 13 19:32:13.867: INFO: Successfully deleted PD "aws://ca-central-1a/vol-018621daabbcaffd3".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumes
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 19:32:13.867: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-498" for this suite.
... skipping 97 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.3EB0eDjiI/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.3EB0eDjiI/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.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 271 lines ...
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 19:32:26.600: 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.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Oct 13 19:32:26.788: INFO: found topology map[topology.kubernetes.io/zone:ca-central-1a]
Oct 13 19:32:26.788: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 13 19:32:26.788: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.3EB0eDjiI/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.3EB0eDjiI/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (immediate binding)] topology
    /tmp/kops.3EB0eDjiI/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.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 211 lines ...
Oct 13 19:31:24.198: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-7196s2sm6      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-7196    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-7196s2sm6,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-7196    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-7196s2sm6,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-7196    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-7196s2sm6,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-7196s2sm6    2862abc2-cdc1-470a-8ffe-7614fb2d77df 11753 0 2021-10-13 19:31:24 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-10-13 19:31:24 +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-h84mp pvc- provisioning-7196  c09d364f-b890-4e44-94a5-cc30a291320d 11758 0 2021-10-13 19:31:24 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-10-13 19:31:24 +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-7196s2sm6,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-aca2d68a-a853-4218-a9f4-f62895d9696b in namespace provisioning-7196
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Oct 13 19:31:38.563: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-ghzqh" in namespace "provisioning-7196" to be "Succeeded or Failed"
Oct 13 19:31:38.594: INFO: Pod "pvc-volume-tester-writer-ghzqh": Phase="Pending", Reason="", readiness=false. Elapsed: 30.925409ms
Oct 13 19:31:40.624: INFO: Pod "pvc-volume-tester-writer-ghzqh": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061532745s
Oct 13 19:31:42.655: INFO: Pod "pvc-volume-tester-writer-ghzqh": Phase="Pending", Reason="", readiness=false. Elapsed: 4.092716009s
Oct 13 19:31:44.687: INFO: Pod "pvc-volume-tester-writer-ghzqh": Phase="Pending", Reason="", readiness=false. Elapsed: 6.124379294s
Oct 13 19:31:46.724: INFO: Pod "pvc-volume-tester-writer-ghzqh": Phase="Pending", Reason="", readiness=false. Elapsed: 8.16157744s
Oct 13 19:31:48.756: INFO: Pod "pvc-volume-tester-writer-ghzqh": Phase="Pending", Reason="", readiness=false. Elapsed: 10.193246106s
... skipping 8 lines ...
Oct 13 19:32:07.040: INFO: Pod "pvc-volume-tester-writer-ghzqh": Phase="Pending", Reason="", readiness=false. Elapsed: 28.477425448s
Oct 13 19:32:09.081: INFO: Pod "pvc-volume-tester-writer-ghzqh": Phase="Pending", Reason="", readiness=false. Elapsed: 30.518527027s
Oct 13 19:32:11.114: INFO: Pod "pvc-volume-tester-writer-ghzqh": Phase="Pending", Reason="", readiness=false. Elapsed: 32.551036466s
Oct 13 19:32:13.144: INFO: Pod "pvc-volume-tester-writer-ghzqh": Phase="Pending", Reason="", readiness=false. Elapsed: 34.581743035s
Oct 13 19:32:15.177: INFO: Pod "pvc-volume-tester-writer-ghzqh": Phase="Succeeded", Reason="", readiness=false. Elapsed: 36.614153967s
STEP: Saw pod success
Oct 13 19:32:15.177: INFO: Pod "pvc-volume-tester-writer-ghzqh" satisfied condition "Succeeded or Failed"
Oct 13 19:32:15.243: INFO: Pod pvc-volume-tester-writer-ghzqh has the following logs: 
Oct 13 19:32:15.243: INFO: Deleting pod "pvc-volume-tester-writer-ghzqh" in namespace "provisioning-7196"
Oct 13 19:32:15.281: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-ghzqh" 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-50-191.ca-central-1.compute.internal"
Oct 13 19:32:15.409: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-bf6qm" in namespace "provisioning-7196" to be "Succeeded or Failed"
Oct 13 19:32:15.439: INFO: Pod "pvc-volume-tester-reader-bf6qm": Phase="Pending", Reason="", readiness=false. Elapsed: 30.40416ms
Oct 13 19:32:17.472: INFO: Pod "pvc-volume-tester-reader-bf6qm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.063588941s
Oct 13 19:32:19.503: INFO: Pod "pvc-volume-tester-reader-bf6qm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.094712326s
STEP: Saw pod success
Oct 13 19:32:19.503: INFO: Pod "pvc-volume-tester-reader-bf6qm" satisfied condition "Succeeded or Failed"
Oct 13 19:32:19.568: INFO: Pod pvc-volume-tester-reader-bf6qm has the following logs: hello world

Oct 13 19:32:19.568: INFO: Deleting pod "pvc-volume-tester-reader-bf6qm" in namespace "provisioning-7196"
Oct 13 19:32:19.607: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-bf6qm" to be fully deleted
Oct 13 19:32:19.638: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-h84mp] to have phase Bound
Oct 13 19:32:19.669: INFO: PersistentVolumeClaim pvc-h84mp found and phase=Bound (30.821264ms)
... skipping 61 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.3EB0eDjiI/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.3EB0eDjiI/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.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 323 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 19:32:11.410: 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.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Oct 13 19:32:11.566: INFO: Creating resource for dynamic PV
Oct 13 19:32:11.566: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-4431-e2e-sckt4sm
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Oct 13 19:32:17.788: INFO: Deleting pod "pod-28b4037e-1f8b-4599-9d7d-b76121f8c682" in namespace "volumemode-4431"
Oct 13 19:32:17.829: INFO: Wait up to 5m0s for pod "pod-28b4037e-1f8b-4599-9d7d-b76121f8c682" to be fully deleted
STEP: Deleting pvc
Oct 13 19:32:19.957: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comwq4dx"
Oct 13 19:32:19.995: INFO: Waiting up to 5m0s for PersistentVolume pvc-5c1bb716-b5a5-4dea-844b-c8e004280d81 to get deleted
Oct 13 19:32:20.034: INFO: PersistentVolume pvc-5c1bb716-b5a5-4dea-844b-c8e004280d81 found and phase=Released (38.639787ms)
... skipping 10 lines ...

• [SLOW TEST:28.856 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.3EB0eDjiI/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.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 206 lines ...
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 19:32:43.383: 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.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Oct 13 19:32:43.571: INFO: found topology map[topology.kubernetes.io/zone:ca-central-1a]
Oct 13 19:32:43.571: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 13 19:32:43.571: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.3EB0eDjiI/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.3EB0eDjiI/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (delayed binding)] topology
    /tmp/kops.3EB0eDjiI/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.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 48 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 19:32:09.090: 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.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Oct 13 19:32:09.248: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 13 19:32:09.248: INFO: Creating resource for dynamic PV
Oct 13 19:32:09.248: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-510nl8rg
STEP: creating a claim
Oct 13 19:32:09.280: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-dnrz
STEP: Checking for subpath error in container status
Oct 13 19:32:21.441: INFO: Deleting pod "pod-subpath-test-dynamicpv-dnrz" in namespace "provisioning-510"
Oct 13 19:32:21.473: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-dnrz" to be fully deleted
STEP: Deleting pod
Oct 13 19:32:23.542: INFO: Deleting pod "pod-subpath-test-dynamicpv-dnrz" in namespace "provisioning-510"
STEP: Deleting pvc
Oct 13 19:32:23.636: INFO: Deleting PersistentVolumeClaim "awsxbdzt"
... skipping 14 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.3EB0eDjiI/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.3EB0eDjiI/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath directory is outside the volume [Slow][LinuxOnly]
      /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 19:32:33.022: 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.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Oct 13 19:32:33.175: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 13 19:32:33.175: INFO: Creating resource for dynamic PV
Oct 13 19:32:33.175: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-9611rkvn7
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Oct 13 19:32:37.399: INFO: Deleting pod "pod-26f960dc-828f-42cc-b019-244c34ea66db" in namespace "volumemode-9611"
Oct 13 19:32:37.431: INFO: Wait up to 5m0s for pod "pod-26f960dc-828f-42cc-b019-244c34ea66db" to be fully deleted
STEP: Deleting pvc
Oct 13 19:32:39.555: INFO: Deleting PersistentVolumeClaim "awshxmdz"
Oct 13 19:32:39.588: INFO: Waiting up to 5m0s for PersistentVolume pvc-c4f1c739-bc42-435e-853f-a687f415aa15 to get deleted
Oct 13 19:32:39.618: INFO: PersistentVolume pvc-c4f1c739-bc42-435e-853f-a687f415aa15 found and phase=Released (30.170857ms)
... skipping 10 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.3EB0eDjiI/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.3EB0eDjiI/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (block volmode)] volumeMode
    /tmp/kops.3EB0eDjiI/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.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ext3)] volumes
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Oct 13 19:32:49.776: INFO: Driver aws doesn't support ext3 -- skipping
[AfterEach] [Testpattern: Dynamic PV (ext3)] volumes
... skipping 183 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.3EB0eDjiI/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.3EB0eDjiI/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.3EB0eDjiI/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.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 38 lines ...
Oct 13 19:32:16.404: INFO: PersistentVolumeClaim pvc-svz2c found but phase is Pending instead of Bound.
Oct 13 19:32:18.435: INFO: PersistentVolumeClaim pvc-svz2c found and phase=Bound (4.106160131s)
Oct 13 19:32:18.436: INFO: Waiting up to 3m0s for PersistentVolume aws-5bvff to have phase Bound
Oct 13 19:32:18.466: INFO: PersistentVolume aws-5bvff found and phase=Bound (30.494235ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-kmvz
STEP: Creating a pod to test exec-volume-test
Oct 13 19:32:18.559: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-kmvz" in namespace "volume-8665" to be "Succeeded or Failed"
Oct 13 19:32:18.593: INFO: Pod "exec-volume-test-preprovisionedpv-kmvz": Phase="Pending", Reason="", readiness=false. Elapsed: 33.505142ms
Oct 13 19:32:20.623: INFO: Pod "exec-volume-test-preprovisionedpv-kmvz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.064330063s
Oct 13 19:32:22.654: INFO: Pod "exec-volume-test-preprovisionedpv-kmvz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.095445127s
Oct 13 19:32:24.686: INFO: Pod "exec-volume-test-preprovisionedpv-kmvz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.126948s
Oct 13 19:32:26.717: INFO: Pod "exec-volume-test-preprovisionedpv-kmvz": Phase="Pending", Reason="", readiness=false. Elapsed: 8.158143999s
Oct 13 19:32:28.749: INFO: Pod "exec-volume-test-preprovisionedpv-kmvz": Phase="Pending", Reason="", readiness=false. Elapsed: 10.189595279s
Oct 13 19:32:30.780: INFO: Pod "exec-volume-test-preprovisionedpv-kmvz": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.220643933s
STEP: Saw pod success
Oct 13 19:32:30.780: INFO: Pod "exec-volume-test-preprovisionedpv-kmvz" satisfied condition "Succeeded or Failed"
Oct 13 19:32:30.810: INFO: Trying to get logs from node ip-172-20-50-163.ca-central-1.compute.internal pod exec-volume-test-preprovisionedpv-kmvz container exec-container-preprovisionedpv-kmvz: <nil>
STEP: delete the pod
Oct 13 19:32:30.891: INFO: Waiting for pod exec-volume-test-preprovisionedpv-kmvz to disappear
Oct 13 19:32:30.926: INFO: Pod exec-volume-test-preprovisionedpv-kmvz no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-kmvz
Oct 13 19:32:30.926: INFO: Deleting pod "exec-volume-test-preprovisionedpv-kmvz" in namespace "volume-8665"
STEP: Deleting pv and pvc
Oct 13 19:32:30.956: INFO: Deleting PersistentVolumeClaim "pvc-svz2c"
Oct 13 19:32:30.988: INFO: Deleting PersistentVolume "aws-5bvff"
Oct 13 19:32:31.169: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0a5c003d71707065c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a5c003d71707065c is currently attached to i-05786989bd674e173
	status code: 400, request id: 8f253966-364d-47c1-8c7c-c5d3941ba25d
Oct 13 19:32:36.392: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0a5c003d71707065c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a5c003d71707065c is currently attached to i-05786989bd674e173
	status code: 400, request id: 26c7ee8a-0a85-43ae-9f27-72e0129a52b4
Oct 13 19:32:41.619: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0a5c003d71707065c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a5c003d71707065c is currently attached to i-05786989bd674e173
	status code: 400, request id: bfcd00ed-2f01-40fc-89b8-5e26ac6dbd8f
Oct 13 19:32:46.867: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0a5c003d71707065c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a5c003d71707065c is currently attached to i-05786989bd674e173
	status code: 400, request id: 8f2d5ee2-1132-48f8-8298-96d2edee339d
Oct 13 19:32:52.129: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0a5c003d71707065c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a5c003d71707065c is currently attached to i-05786989bd674e173
	status code: 400, request id: 77798df1-68d9-4a6f-8882-16e23d05fddd
Oct 13 19:32:57.381: INFO: Successfully deleted PD "aws://ca-central-1a/vol-0a5c003d71707065c".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 19:32:57.381: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8665" for this suite.
... skipping 105 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 19:32:43.921: 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.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Oct 13 19:32:44.077: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Oct 13 19:32:44.444: INFO: Successfully created a new PD: "aws://ca-central-1a/vol-00b0406dafed2f047".
Oct 13 19:32:44.444: INFO: Creating resource for pre-provisioned PV
Oct 13 19:32:44.444: INFO: Creating PVC and PV
... skipping 3 lines ...
Oct 13 19:32:44.538: INFO: PersistentVolumeClaim pvc-8w5nl found but phase is Pending instead of Bound.
Oct 13 19:32:46.570: INFO: PersistentVolumeClaim pvc-8w5nl found but phase is Pending instead of Bound.
Oct 13 19:32:48.601: INFO: PersistentVolumeClaim pvc-8w5nl found and phase=Bound (4.092557699s)
Oct 13 19:32:48.601: INFO: Waiting up to 3m0s for PersistentVolume aws-knlvj to have phase Bound
Oct 13 19:32:48.632: INFO: PersistentVolume aws-knlvj found and phase=Bound (30.852282ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Oct 13 19:32:50.825: INFO: Deleting pod "pod-6dccbf88-4f69-4f84-8f10-511b87bd7eb4" in namespace "volumemode-6187"
Oct 13 19:32:50.858: INFO: Wait up to 5m0s for pod "pod-6dccbf88-4f69-4f84-8f10-511b87bd7eb4" to be fully deleted
STEP: Deleting pv and pvc
Oct 13 19:32:52.921: INFO: Deleting PersistentVolumeClaim "pvc-8w5nl"
Oct 13 19:32:52.956: INFO: Deleting PersistentVolume "aws-knlvj"
Oct 13 19:32:53.131: INFO: Couldn't delete PD "aws://ca-central-1a/vol-00b0406dafed2f047", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00b0406dafed2f047 is currently attached to i-049bea91c6928b078
	status code: 400, request id: 5107ae3d-8430-4f33-994b-45e77eca6087
Oct 13 19:32:58.349: INFO: Couldn't delete PD "aws://ca-central-1a/vol-00b0406dafed2f047", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00b0406dafed2f047 is currently attached to i-049bea91c6928b078
	status code: 400, request id: 13cb5ee1-3363-433c-93a4-bd0d839e908e
Oct 13 19:33:03.638: INFO: Successfully deleted PD "aws://ca-central-1a/vol-00b0406dafed2f047".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 19:33:03.638: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-6187" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.3EB0eDjiI/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.3EB0eDjiI/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
    /tmp/kops.3EB0eDjiI/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.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] provisioning
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] provisioning
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 145 lines ...
Oct 13 19:32:11.044: INFO: Creating resource for dynamic PV
Oct 13 19:32:11.044: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-222h9z26
STEP: creating a claim
Oct 13 19:32:11.076: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-222
Oct 13 19:32:11.174: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-222" in namespace "provisioning-222" to be "Succeeded or Failed"
Oct 13 19:32:11.211: INFO: Pod "volume-prep-provisioning-222": Phase="Pending", Reason="", readiness=false. Elapsed: 37.333074ms
Oct 13 19:32:13.243: INFO: Pod "volume-prep-provisioning-222": Phase="Pending", Reason="", readiness=false. Elapsed: 2.069365182s
Oct 13 19:32:15.279: INFO: Pod "volume-prep-provisioning-222": Phase="Pending", Reason="", readiness=false. Elapsed: 4.104936549s
Oct 13 19:32:17.310: INFO: Pod "volume-prep-provisioning-222": Phase="Pending", Reason="", readiness=false. Elapsed: 6.136304886s
Oct 13 19:32:19.342: INFO: Pod "volume-prep-provisioning-222": Phase="Pending", Reason="", readiness=false. Elapsed: 8.168608113s
Oct 13 19:32:21.373: INFO: Pod "volume-prep-provisioning-222": Phase="Pending", Reason="", readiness=false. Elapsed: 10.199500662s
Oct 13 19:32:23.404: INFO: Pod "volume-prep-provisioning-222": Phase="Pending", Reason="", readiness=false. Elapsed: 12.230618215s
Oct 13 19:32:25.436: INFO: Pod "volume-prep-provisioning-222": Phase="Pending", Reason="", readiness=false. Elapsed: 14.262665103s
Oct 13 19:32:27.468: INFO: Pod "volume-prep-provisioning-222": Phase="Pending", Reason="", readiness=false. Elapsed: 16.294221406s
Oct 13 19:32:29.499: INFO: Pod "volume-prep-provisioning-222": Phase="Pending", Reason="", readiness=false. Elapsed: 18.325792972s
Oct 13 19:32:31.534: INFO: Pod "volume-prep-provisioning-222": Phase="Pending", Reason="", readiness=false. Elapsed: 20.359917286s
Oct 13 19:32:33.565: INFO: Pod "volume-prep-provisioning-222": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.391631291s
STEP: Saw pod success
Oct 13 19:32:33.565: INFO: Pod "volume-prep-provisioning-222" satisfied condition "Succeeded or Failed"
Oct 13 19:32:33.565: INFO: Deleting pod "volume-prep-provisioning-222" in namespace "provisioning-222"
Oct 13 19:32:33.602: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-222" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-l995
STEP: Checking for subpath error in container status
Oct 13 19:32:39.728: INFO: Deleting pod "pod-subpath-test-dynamicpv-l995" in namespace "provisioning-222"
Oct 13 19:32:39.770: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-l995" to be fully deleted
STEP: Deleting pod
Oct 13 19:32:39.800: INFO: Deleting pod "pod-subpath-test-dynamicpv-l995" in namespace "provisioning-222"
STEP: Deleting pvc
Oct 13 19:32:39.893: INFO: Deleting PersistentVolumeClaim "aws9l5hh"
... skipping 34 lines ...
Oct 13 19:32:43.370: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Oct 13 19:32:43.645: INFO: Successfully created a new PD: "aws://ca-central-1a/vol-0f997999a12a4579e".
Oct 13 19:32:43.645: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-8f5v
STEP: Creating a pod to test exec-volume-test
Oct 13 19:32:43.677: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-8f5v" in namespace "volume-4028" to be "Succeeded or Failed"
Oct 13 19:32:43.710: INFO: Pod "exec-volume-test-inlinevolume-8f5v": Phase="Pending", Reason="", readiness=false. Elapsed: 32.761651ms
Oct 13 19:32:45.741: INFO: Pod "exec-volume-test-inlinevolume-8f5v": Phase="Pending", Reason="", readiness=false. Elapsed: 2.064014491s
Oct 13 19:32:47.772: INFO: Pod "exec-volume-test-inlinevolume-8f5v": Phase="Pending", Reason="", readiness=false. Elapsed: 4.095050997s
Oct 13 19:32:49.803: INFO: Pod "exec-volume-test-inlinevolume-8f5v": Phase="Pending", Reason="", readiness=false. Elapsed: 6.125958857s
Oct 13 19:32:51.835: INFO: Pod "exec-volume-test-inlinevolume-8f5v": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.158089703s
STEP: Saw pod success
Oct 13 19:32:51.836: INFO: Pod "exec-volume-test-inlinevolume-8f5v" satisfied condition "Succeeded or Failed"
Oct 13 19:32:51.866: INFO: Trying to get logs from node ip-172-20-38-144.ca-central-1.compute.internal pod exec-volume-test-inlinevolume-8f5v container exec-container-inlinevolume-8f5v: <nil>
STEP: delete the pod
Oct 13 19:32:51.938: INFO: Waiting for pod exec-volume-test-inlinevolume-8f5v to disappear
Oct 13 19:32:51.968: INFO: Pod exec-volume-test-inlinevolume-8f5v no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-8f5v
Oct 13 19:32:51.969: INFO: Deleting pod "exec-volume-test-inlinevolume-8f5v" in namespace "volume-4028"
Oct 13 19:32:52.127: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0f997999a12a4579e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f997999a12a4579e is currently attached to i-049bea91c6928b078
	status code: 400, request id: 612a3e93-3c7d-4e79-82ac-b31144b84825
Oct 13 19:32:57.387: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0f997999a12a4579e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f997999a12a4579e is currently attached to i-049bea91c6928b078
	status code: 400, request id: 3d40e7b2-512e-4229-b2a2-de27c8fd19e7
Oct 13 19:33:02.643: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0f997999a12a4579e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f997999a12a4579e is currently attached to i-049bea91c6928b078
	status code: 400, request id: 69a49eee-9b4d-4593-a030-4aa4ffdc81ac
Oct 13 19:33:07.894: INFO: Successfully deleted PD "aws://ca-central-1a/vol-0f997999a12a4579e".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 19:33:07.894: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-4028" for this suite.
... skipping 204 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 19:32:36.222: 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.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Oct 13 19:32:36.382: INFO: Creating resource for dynamic PV
Oct 13 19:32:36.382: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5509-e2e-sc656p2
STEP: creating a claim
Oct 13 19:32:36.414: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-ltmz
STEP: Checking for subpath error in container status
Oct 13 19:32:52.572: INFO: Deleting pod "pod-subpath-test-dynamicpv-ltmz" in namespace "provisioning-5509"
Oct 13 19:32:52.604: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-ltmz" to be fully deleted
STEP: Deleting pod
Oct 13 19:32:54.667: INFO: Deleting pod "pod-subpath-test-dynamicpv-ltmz" in namespace "provisioning-5509"
STEP: Deleting pvc
Oct 13 19:32:54.760: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com5kjbh"
... skipping 12 lines ...

• [SLOW TEST:38.826 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath file is outside the volume [Slow][LinuxOnly]
    /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 8 lines ...
Oct 13 19:32:24.372: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3268lwwpx
STEP: creating a claim
Oct 13 19:32:24.405: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-j7fr
STEP: Creating a pod to test multi_subpath
Oct 13 19:32:24.501: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-j7fr" in namespace "provisioning-3268" to be "Succeeded or Failed"
Oct 13 19:32:24.533: INFO: Pod "pod-subpath-test-dynamicpv-j7fr": Phase="Pending", Reason="", readiness=false. Elapsed: 32.324211ms
Oct 13 19:32:26.565: INFO: Pod "pod-subpath-test-dynamicpv-j7fr": Phase="Pending", Reason="", readiness=false. Elapsed: 2.064024136s
Oct 13 19:32:28.597: INFO: Pod "pod-subpath-test-dynamicpv-j7fr": Phase="Pending", Reason="", readiness=false. Elapsed: 4.095510919s
Oct 13 19:32:30.627: INFO: Pod "pod-subpath-test-dynamicpv-j7fr": Phase="Pending", Reason="", readiness=false. Elapsed: 6.126366274s
Oct 13 19:32:32.659: INFO: Pod "pod-subpath-test-dynamicpv-j7fr": Phase="Pending", Reason="", readiness=false. Elapsed: 8.15773491s
Oct 13 19:32:34.694: INFO: Pod "pod-subpath-test-dynamicpv-j7fr": Phase="Pending", Reason="", readiness=false. Elapsed: 10.193279589s
Oct 13 19:32:36.725: INFO: Pod "pod-subpath-test-dynamicpv-j7fr": Phase="Pending", Reason="", readiness=false. Elapsed: 12.22412281s
Oct 13 19:32:38.757: INFO: Pod "pod-subpath-test-dynamicpv-j7fr": Phase="Pending", Reason="", readiness=false. Elapsed: 14.25611846s
Oct 13 19:32:40.788: INFO: Pod "pod-subpath-test-dynamicpv-j7fr": Phase="Pending", Reason="", readiness=false. Elapsed: 16.287098516s
Oct 13 19:32:42.821: INFO: Pod "pod-subpath-test-dynamicpv-j7fr": Phase="Pending", Reason="", readiness=false. Elapsed: 18.319440463s
Oct 13 19:32:44.851: INFO: Pod "pod-subpath-test-dynamicpv-j7fr": Phase="Pending", Reason="", readiness=false. Elapsed: 20.350182582s
Oct 13 19:32:46.882: INFO: Pod "pod-subpath-test-dynamicpv-j7fr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.381372486s
STEP: Saw pod success
Oct 13 19:32:46.883: INFO: Pod "pod-subpath-test-dynamicpv-j7fr" satisfied condition "Succeeded or Failed"
Oct 13 19:32:46.914: INFO: Trying to get logs from node ip-172-20-38-144.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-j7fr container test-container-subpath-dynamicpv-j7fr: <nil>
STEP: delete the pod
Oct 13 19:32:46.982: INFO: Waiting for pod pod-subpath-test-dynamicpv-j7fr to disappear
Oct 13 19:32:47.012: INFO: Pod pod-subpath-test-dynamicpv-j7fr no longer exists
STEP: Deleting pod
Oct 13 19:32:47.012: INFO: Deleting pod "pod-subpath-test-dynamicpv-j7fr" in namespace "provisioning-3268"
... skipping 38 lines ...
Oct 13 19:32:49.933: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-3334-e2e-scd8jlw
STEP: creating a claim
Oct 13 19:32:49.964: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Oct 13 19:32:50.027: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Oct 13 19:32:50.089: INFO: Error updating pvc ebs.csi.aws.com6n8s5: PersistentVolumeClaim "ebs.csi.aws.com6n8s5" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3334-e2e-scd8jlw",
  	... // 3 identical fields
  }

Oct 13 19:32:52.192: INFO: Error updating pvc ebs.csi.aws.com6n8s5: PersistentVolumeClaim "ebs.csi.aws.com6n8s5" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3334-e2e-scd8jlw",
  	... // 3 identical fields
  }

Oct 13 19:32:54.151: INFO: Error updating pvc ebs.csi.aws.com6n8s5: PersistentVolumeClaim "ebs.csi.aws.com6n8s5" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3334-e2e-scd8jlw",
  	... // 3 identical fields
  }

Oct 13 19:32:56.151: INFO: Error updating pvc ebs.csi.aws.com6n8s5: PersistentVolumeClaim "ebs.csi.aws.com6n8s5" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3334-e2e-scd8jlw",
  	... // 3 identical fields
  }

Oct 13 19:32:58.151: INFO: Error updating pvc ebs.csi.aws.com6n8s5: PersistentVolumeClaim "ebs.csi.aws.com6n8s5" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3334-e2e-scd8jlw",
  	... // 3 identical fields
  }

Oct 13 19:33:00.152: INFO: Error updating pvc ebs.csi.aws.com6n8s5: PersistentVolumeClaim "ebs.csi.aws.com6n8s5" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3334-e2e-scd8jlw",
  	... // 3 identical fields
  }

Oct 13 19:33:02.151: INFO: Error updating pvc ebs.csi.aws.com6n8s5: PersistentVolumeClaim "ebs.csi.aws.com6n8s5" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3334-e2e-scd8jlw",
  	... // 3 identical fields
  }

Oct 13 19:33:04.153: INFO: Error updating pvc ebs.csi.aws.com6n8s5: PersistentVolumeClaim "ebs.csi.aws.com6n8s5" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3334-e2e-scd8jlw",
  	... // 3 identical fields
  }

Oct 13 19:33:06.151: INFO: Error updating pvc ebs.csi.aws.com6n8s5: PersistentVolumeClaim "ebs.csi.aws.com6n8s5" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3334-e2e-scd8jlw",
  	... // 3 identical fields
  }

Oct 13 19:33:08.151: INFO: Error updating pvc ebs.csi.aws.com6n8s5: PersistentVolumeClaim "ebs.csi.aws.com6n8s5" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3334-e2e-scd8jlw",
  	... // 3 identical fields
  }

Oct 13 19:33:10.155: INFO: Error updating pvc ebs.csi.aws.com6n8s5: PersistentVolumeClaim "ebs.csi.aws.com6n8s5" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3334-e2e-scd8jlw",
  	... // 3 identical fields
  }

Oct 13 19:33:12.151: INFO: Error updating pvc ebs.csi.aws.com6n8s5: PersistentVolumeClaim "ebs.csi.aws.com6n8s5" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3334-e2e-scd8jlw",
  	... // 3 identical fields
  }

Oct 13 19:33:14.151: INFO: Error updating pvc ebs.csi.aws.com6n8s5: PersistentVolumeClaim "ebs.csi.aws.com6n8s5" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3334-e2e-scd8jlw",
  	... // 3 identical fields
  }

Oct 13 19:33:16.153: INFO: Error updating pvc ebs.csi.aws.com6n8s5: PersistentVolumeClaim "ebs.csi.aws.com6n8s5" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3334-e2e-scd8jlw",
  	... // 3 identical fields
  }

Oct 13 19:33:18.158: INFO: Error updating pvc ebs.csi.aws.com6n8s5: PersistentVolumeClaim "ebs.csi.aws.com6n8s5" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3334-e2e-scd8jlw",
  	... // 3 identical fields
  }

Oct 13 19:33:20.157: INFO: Error updating pvc ebs.csi.aws.com6n8s5: PersistentVolumeClaim "ebs.csi.aws.com6n8s5" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3334-e2e-scd8jlw",
  	... // 3 identical fields
  }

Oct 13 19:33:20.219: INFO: Error updating pvc ebs.csi.aws.com6n8s5: PersistentVolumeClaim "ebs.csi.aws.com6n8s5" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 38 lines ...
Oct 13 19:30:21.764: INFO: Creating resource for dynamic PV
Oct 13 19:30:21.764: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-2754-e2e-scfllwn
STEP: creating a claim
Oct 13 19:30:21.799: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Oct 13 19:30:21.905: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-64n2c" in namespace "snapshotting-2754" to be "Succeeded or Failed"
Oct 13 19:30:21.936: INFO: Pod "pvc-snapshottable-tester-64n2c": Phase="Pending", Reason="", readiness=false. Elapsed: 31.029775ms
Oct 13 19:30:23.968: INFO: Pod "pvc-snapshottable-tester-64n2c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.063163028s
Oct 13 19:30:25.999: INFO: Pod "pvc-snapshottable-tester-64n2c": Phase="Pending", Reason="", readiness=false. Elapsed: 4.094092575s
Oct 13 19:30:28.030: INFO: Pod "pvc-snapshottable-tester-64n2c": Phase="Pending", Reason="", readiness=false. Elapsed: 6.124908744s
Oct 13 19:30:30.061: INFO: Pod "pvc-snapshottable-tester-64n2c": Phase="Pending", Reason="", readiness=false. Elapsed: 8.156102098s
Oct 13 19:30:32.092: INFO: Pod "pvc-snapshottable-tester-64n2c": Phase="Pending", Reason="", readiness=false. Elapsed: 10.1872663s
Oct 13 19:30:34.126: INFO: Pod "pvc-snapshottable-tester-64n2c": Phase="Pending", Reason="", readiness=false. Elapsed: 12.22064129s
Oct 13 19:30:36.158: INFO: Pod "pvc-snapshottable-tester-64n2c": Phase="Pending", Reason="", readiness=false. Elapsed: 14.252432024s
Oct 13 19:30:38.189: INFO: Pod "pvc-snapshottable-tester-64n2c": Phase="Pending", Reason="", readiness=false. Elapsed: 16.284368417s
Oct 13 19:30:40.222: INFO: Pod "pvc-snapshottable-tester-64n2c": Phase="Pending", Reason="", readiness=false. Elapsed: 18.316447816s
Oct 13 19:30:42.255: INFO: Pod "pvc-snapshottable-tester-64n2c": Phase="Pending", Reason="", readiness=false. Elapsed: 20.34940849s
Oct 13 19:30:44.286: INFO: Pod "pvc-snapshottable-tester-64n2c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.381350945s
STEP: Saw pod success
Oct 13 19:30:44.287: INFO: Pod "pvc-snapshottable-tester-64n2c" satisfied condition "Succeeded or Failed"
Oct 13 19:30:44.362: INFO: Pod pvc-snapshottable-tester-64n2c has the following logs: 
Oct 13 19:30:44.362: INFO: Deleting pod "pvc-snapshottable-tester-64n2c" in namespace "snapshotting-2754"
Oct 13 19:30:44.400: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-64n2c" to be fully deleted
Oct 13 19:30:44.431: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comszxpg] to have phase Bound
Oct 13 19:30:44.468: INFO: PersistentVolumeClaim ebs.csi.aws.comszxpg found and phase=Bound (36.340475ms)
STEP: [init] checking the claim
... skipping 32 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.3EB0eDjiI/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
Oct 13 19:31:29.628: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-58pgp" in namespace "snapshotting-2754" to be "Succeeded or Failed"
Oct 13 19:31:29.658: INFO: Pod "pvc-snapshottable-data-tester-58pgp": Phase="Pending", Reason="", readiness=false. Elapsed: 30.608846ms
Oct 13 19:31:31.689: INFO: Pod "pvc-snapshottable-data-tester-58pgp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061695052s
Oct 13 19:31:33.721: INFO: Pod "pvc-snapshottable-data-tester-58pgp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.093241342s
Oct 13 19:31:35.753: INFO: Pod "pvc-snapshottable-data-tester-58pgp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.125025076s
Oct 13 19:31:37.784: INFO: Pod "pvc-snapshottable-data-tester-58pgp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.156438324s
Oct 13 19:31:39.816: INFO: Pod "pvc-snapshottable-data-tester-58pgp": Phase="Pending", Reason="", readiness=false. Elapsed: 10.188590054s
Oct 13 19:31:41.875: INFO: Pod "pvc-snapshottable-data-tester-58pgp": Phase="Pending", Reason="", readiness=false. Elapsed: 12.247773986s
Oct 13 19:31:43.907: INFO: Pod "pvc-snapshottable-data-tester-58pgp": Phase="Pending", Reason="", readiness=false. Elapsed: 14.279559631s
Oct 13 19:31:45.939: INFO: Pod "pvc-snapshottable-data-tester-58pgp": Phase="Pending", Reason="", readiness=false. Elapsed: 16.311077034s
Oct 13 19:31:47.970: INFO: Pod "pvc-snapshottable-data-tester-58pgp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.342192196s
STEP: Saw pod success
Oct 13 19:31:47.970: INFO: Pod "pvc-snapshottable-data-tester-58pgp" satisfied condition "Succeeded or Failed"
Oct 13 19:31:48.033: INFO: Pod pvc-snapshottable-data-tester-58pgp has the following logs: 
Oct 13 19:31:48.033: INFO: Deleting pod "pvc-snapshottable-data-tester-58pgp" in namespace "snapshotting-2754"
Oct 13 19:31:48.069: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-58pgp" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Oct 13 19:32:10.232: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-b6f7c24027-45100.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-2754 exec restored-pvc-tester-24npd --namespace=snapshotting-2754 -- cat /mnt/test/data'
... skipping 33 lines ...
Oct 13 19:32:35.698: INFO: volumesnapshotcontents snapcontent-eb2a0d5c-9bfc-4535-940e-c3791f3076ef has been found and is not deleted
Oct 13 19:32:36.730: INFO: volumesnapshotcontents snapcontent-eb2a0d5c-9bfc-4535-940e-c3791f3076ef has been found and is not deleted
Oct 13 19:32:37.763: INFO: volumesnapshotcontents snapcontent-eb2a0d5c-9bfc-4535-940e-c3791f3076ef has been found and is not deleted
Oct 13 19:32:38.795: INFO: volumesnapshotcontents snapcontent-eb2a0d5c-9bfc-4535-940e-c3791f3076ef has been found and is not deleted
Oct 13 19:32:39.827: INFO: volumesnapshotcontents snapcontent-eb2a0d5c-9bfc-4535-940e-c3791f3076ef has been found and is not deleted
Oct 13 19:32:40.858: INFO: volumesnapshotcontents snapcontent-eb2a0d5c-9bfc-4535-940e-c3791f3076ef has been found and is not deleted
Oct 13 19:32:41.859: INFO: WaitUntil failed after reaching the timeout 30s
[AfterEach] volume snapshot controller
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:221
Oct 13 19:32:41.892: INFO: Pod restored-pvc-tester-24npd has the following logs: 
Oct 13 19:32:41.892: INFO: Deleting pod "restored-pvc-tester-24npd" in namespace "snapshotting-2754"
Oct 13 19:32:41.923: INFO: Wait up to 5m0s for pod "restored-pvc-tester-24npd" to be fully deleted
Oct 13 19:33:13.987: INFO: deleting claim "snapshotting-2754"/"pvc-c4756"
... skipping 160 lines ...
Oct 13 19:32:36.671: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-7367-e2e-sc4qb25
STEP: creating a claim
Oct 13 19:32:36.702: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-9dxn
STEP: Creating a pod to test exec-volume-test
Oct 13 19:32:36.796: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-9dxn" in namespace "volume-7367" to be "Succeeded or Failed"
Oct 13 19:32:36.826: INFO: Pod "exec-volume-test-dynamicpv-9dxn": Phase="Pending", Reason="", readiness=false. Elapsed: 30.172421ms
Oct 13 19:32:38.856: INFO: Pod "exec-volume-test-dynamicpv-9dxn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.060633797s
Oct 13 19:32:40.888: INFO: Pod "exec-volume-test-dynamicpv-9dxn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.09217659s
Oct 13 19:32:42.919: INFO: Pod "exec-volume-test-dynamicpv-9dxn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.123047705s
Oct 13 19:32:44.950: INFO: Pod "exec-volume-test-dynamicpv-9dxn": Phase="Pending", Reason="", readiness=false. Elapsed: 8.153789302s
Oct 13 19:32:46.984: INFO: Pod "exec-volume-test-dynamicpv-9dxn": Phase="Pending", Reason="", readiness=false. Elapsed: 10.187740691s
Oct 13 19:32:49.015: INFO: Pod "exec-volume-test-dynamicpv-9dxn": Phase="Pending", Reason="", readiness=false. Elapsed: 12.219460003s
Oct 13 19:32:51.046: INFO: Pod "exec-volume-test-dynamicpv-9dxn": Phase="Pending", Reason="", readiness=false. Elapsed: 14.250041031s
Oct 13 19:32:53.078: INFO: Pod "exec-volume-test-dynamicpv-9dxn": Phase="Pending", Reason="", readiness=false. Elapsed: 16.281871112s
Oct 13 19:32:55.109: INFO: Pod "exec-volume-test-dynamicpv-9dxn": Phase="Pending", Reason="", readiness=false. Elapsed: 18.313115467s
Oct 13 19:32:57.141: INFO: Pod "exec-volume-test-dynamicpv-9dxn": Phase="Pending", Reason="", readiness=false. Elapsed: 20.344948982s
Oct 13 19:32:59.172: INFO: Pod "exec-volume-test-dynamicpv-9dxn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.375960745s
STEP: Saw pod success
Oct 13 19:32:59.172: INFO: Pod "exec-volume-test-dynamicpv-9dxn" satisfied condition "Succeeded or Failed"
Oct 13 19:32:59.202: INFO: Trying to get logs from node ip-172-20-50-163.ca-central-1.compute.internal pod exec-volume-test-dynamicpv-9dxn container exec-container-dynamicpv-9dxn: <nil>
STEP: delete the pod
Oct 13 19:32:59.277: INFO: Waiting for pod exec-volume-test-dynamicpv-9dxn to disappear
Oct 13 19:32:59.308: INFO: Pod exec-volume-test-dynamicpv-9dxn no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-9dxn
Oct 13 19:32:59.308: INFO: Deleting pod "exec-volume-test-dynamicpv-9dxn" in namespace "volume-7367"
... skipping 81 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 19:33:04.104: 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.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Oct 13 19:33:04.258: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 13 19:33:04.258: INFO: Creating resource for dynamic PV
Oct 13 19:33:04.258: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2966snnm
STEP: creating a claim
Oct 13 19:33:04.289: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-lhb6
STEP: Checking for subpath error in container status
Oct 13 19:33:20.464: INFO: Deleting pod "pod-subpath-test-dynamicpv-lhb6" in namespace "provisioning-296"
Oct 13 19:33:20.496: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-lhb6" to be fully deleted
STEP: Deleting pod
Oct 13 19:33:22.560: INFO: Deleting pod "pod-subpath-test-dynamicpv-lhb6" in namespace "provisioning-296"
STEP: Deleting pvc
Oct 13 19:33:22.651: INFO: Deleting PersistentVolumeClaim "awsxhs5b"
... skipping 14 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.3EB0eDjiI/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.3EB0eDjiI/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.3EB0eDjiI/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.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 897 lines ...
Oct 13 19:32:30.873: INFO: Creating resource for dynamic PV
Oct 13 19:32:30.873: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-7638-e2e-scbgv22
STEP: creating a claim
Oct 13 19:32:30.904: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Oct 13 19:32:31.009: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-6qnhw" in namespace "snapshotting-7638" to be "Succeeded or Failed"
Oct 13 19:32:31.039: INFO: Pod "pvc-snapshottable-tester-6qnhw": Phase="Pending", Reason="", readiness=false. Elapsed: 30.360074ms
Oct 13 19:32:33.070: INFO: Pod "pvc-snapshottable-tester-6qnhw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061409128s
Oct 13 19:32:35.106: INFO: Pod "pvc-snapshottable-tester-6qnhw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.097541998s
Oct 13 19:32:37.137: INFO: Pod "pvc-snapshottable-tester-6qnhw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.128238872s
Oct 13 19:32:39.170: INFO: Pod "pvc-snapshottable-tester-6qnhw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.161318602s
Oct 13 19:32:41.202: INFO: Pod "pvc-snapshottable-tester-6qnhw": Phase="Pending", Reason="", readiness=false. Elapsed: 10.192940415s
... skipping 9 lines ...
Oct 13 19:33:01.520: INFO: Pod "pvc-snapshottable-tester-6qnhw": Phase="Pending", Reason="", readiness=false. Elapsed: 30.511522369s
Oct 13 19:33:03.553: INFO: Pod "pvc-snapshottable-tester-6qnhw": Phase="Pending", Reason="", readiness=false. Elapsed: 32.543721771s
Oct 13 19:33:05.585: INFO: Pod "pvc-snapshottable-tester-6qnhw": Phase="Pending", Reason="", readiness=false. Elapsed: 34.576375478s
Oct 13 19:33:07.616: INFO: Pod "pvc-snapshottable-tester-6qnhw": Phase="Pending", Reason="", readiness=false. Elapsed: 36.607327665s
Oct 13 19:33:09.648: INFO: Pod "pvc-snapshottable-tester-6qnhw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 38.638796544s
STEP: Saw pod success
Oct 13 19:33:09.648: INFO: Pod "pvc-snapshottable-tester-6qnhw" satisfied condition "Succeeded or Failed"
Oct 13 19:33:09.711: INFO: Pod pvc-snapshottable-tester-6qnhw has the following logs: 
Oct 13 19:33:09.711: INFO: Deleting pod "pvc-snapshottable-tester-6qnhw" in namespace "snapshotting-7638"
Oct 13 19:33:09.746: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-6qnhw" to be fully deleted
Oct 13 19:33:09.777: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.compqqhs] to have phase Bound
Oct 13 19:33:09.807: INFO: PersistentVolumeClaim ebs.csi.aws.compqqhs found and phase=Bound (30.533749ms)
STEP: [init] checking the claim
... skipping 109 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.3EB0eDjiI/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
Oct 13 19:35:55.069: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-49fsl" in namespace "snapshotting-7638" to be "Succeeded or Failed"
Oct 13 19:35:55.109: INFO: Pod "pvc-snapshottable-data-tester-49fsl": Phase="Pending", Reason="", readiness=false. Elapsed: 39.827835ms
Oct 13 19:35:57.140: INFO: Pod "pvc-snapshottable-data-tester-49fsl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.070412985s
Oct 13 19:35:59.171: INFO: Pod "pvc-snapshottable-data-tester-49fsl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.101736018s
Oct 13 19:36:01.203: INFO: Pod "pvc-snapshottable-data-tester-49fsl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.133766933s
STEP: Saw pod success
Oct 13 19:36:01.203: INFO: Pod "pvc-snapshottable-data-tester-49fsl" satisfied condition "Succeeded or Failed"
Oct 13 19:36:01.272: INFO: Pod pvc-snapshottable-data-tester-49fsl has the following logs: 
Oct 13 19:36:01.272: INFO: Deleting pod "pvc-snapshottable-data-tester-49fsl" in namespace "snapshotting-7638"
Oct 13 19:36:01.307: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-49fsl" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Oct 13 19:36:11.465: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-b6f7c24027-45100.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-7638 exec restored-pvc-tester-48zm8 --namespace=snapshotting-7638 -- cat /mnt/test/data'
... skipping 28 lines ...
STEP: Found 33 events.
Oct 13 19:36:51.565: INFO: At 2021-10-13 19:32:30 +0000 UTC - event for ebs.csi.aws.compqqhs: {persistentvolume-controller } WaitForFirstConsumer: waiting for first consumer to be created before binding
Oct 13 19:36:51.565: INFO: At 2021-10-13 19:32:31 +0000 UTC - event for ebs.csi.aws.compqqhs: {persistentvolume-controller } ExternalProvisioning: waiting for a volume to be created, either by external provisioner "ebs.csi.aws.com" or manually created by system administrator
Oct 13 19:36:51.565: INFO: At 2021-10-13 19:32:31 +0000 UTC - event for ebs.csi.aws.compqqhs: {ebs.csi.aws.com_ebs-csi-controller-54dc46fc7b-xwl4n_74d64462-c0ab-4356-84cb-5027dc4947d1 } Provisioning: External provisioner is provisioning volume for claim "snapshotting-7638/ebs.csi.aws.compqqhs"
Oct 13 19:36:51.565: INFO: At 2021-10-13 19:32:34 +0000 UTC - event for ebs.csi.aws.compqqhs: {ebs.csi.aws.com_ebs-csi-controller-54dc46fc7b-xwl4n_74d64462-c0ab-4356-84cb-5027dc4947d1 } ProvisioningSucceeded: Successfully provisioned volume pvc-70689a9e-b1bd-4918-9438-09ddc2398775
Oct 13 19:36:51.565: INFO: At 2021-10-13 19:32:35 +0000 UTC - event for pvc-snapshottable-tester-6qnhw: {default-scheduler } Scheduled: Successfully assigned snapshotting-7638/pvc-snapshottable-tester-6qnhw to ip-172-20-50-163.ca-central-1.compute.internal
Oct 13 19:36:51.565: INFO: At 2021-10-13 19:32:50 +0000 UTC - event for pvc-snapshottable-tester-6qnhw: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-70689a9e-b1bd-4918-9438-09ddc2398775" : rpc error: code = DeadlineExceeded desc = context deadline exceeded
Oct 13 19:36:51.565: INFO: At 2021-10-13 19:32:55 +0000 UTC - event for pvc-snapshottable-tester-6qnhw: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-70689a9e-b1bd-4918-9438-09ddc2398775" 
Oct 13 19:36:51.565: INFO: At 2021-10-13 19:33:09 +0000 UTC - event for pvc-snapshottable-tester-6qnhw: {kubelet ip-172-20-50-163.ca-central-1.compute.internal} FailedMount: MountVolume.SetUp failed for volume "kube-api-access-n8p8b" : object "snapshotting-7638"/"kube-root-ca.crt" not registered
Oct 13 19:36:51.565: INFO: At 2021-10-13 19:33:09 +0000 UTC - event for pvc-snapshottable-tester-6qnhw: {kubelet ip-172-20-50-163.ca-central-1.compute.internal} Started: Started container volume-tester
Oct 13 19:36:51.565: INFO: At 2021-10-13 19:33:09 +0000 UTC - event for pvc-snapshottable-tester-6qnhw: {kubelet ip-172-20-50-163.ca-central-1.compute.internal} Created: Created container volume-tester
Oct 13 19:36:51.565: INFO: At 2021-10-13 19:33:09 +0000 UTC - event for pvc-snapshottable-tester-6qnhw: {kubelet ip-172-20-50-163.ca-central-1.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" already present on machine
Oct 13 19:36:51.565: INFO: At 2021-10-13 19:33:09 +0000 UTC - event for snapshot-p286d: {snapshot-controller } CreatingSnapshot: Waiting for a snapshot snapshotting-7638/snapshot-p286d to be created by the CSI driver.
Oct 13 19:36:51.565: INFO: At 2021-10-13 19:33:10 +0000 UTC - event for snapshot-p286d: {snapshot-controller } SnapshotCreated: Snapshot snapshotting-7638/snapshot-p286d was successfully created by the CSI driver.
Oct 13 19:36:51.565: INFO: At 2021-10-13 19:35:51 +0000 UTC - event for snapshot-p286d: {snapshot-controller } SnapshotReady: Snapshot snapshotting-7638/snapshot-p286d is ready to use.
Oct 13 19:36:51.565: INFO: At 2021-10-13 19:35:53 +0000 UTC - event for pre-provisioned-snapshot-68b83bfd-1e53-4bc4-a338-8a4c10a98410: {snapshot-controller } SnapshotReady: Snapshot snapshotting-7638/pre-provisioned-snapshot-68b83bfd-1e53-4bc4-a338-8a4c10a98410 is ready to use.
Oct 13 19:36:51.565: INFO: At 2021-10-13 19:35:53 +0000 UTC - event for pre-provisioned-snapshot-68b83bfd-1e53-4bc4-a338-8a4c10a98410: {snapshot-controller } SnapshotCreated: Snapshot snapshotting-7638/pre-provisioned-snapshot-68b83bfd-1e53-4bc4-a338-8a4c10a98410 was successfully created by the CSI driver.
Oct 13 19:36:51.565: INFO: At 2021-10-13 19:35:55 +0000 UTC - event for pvc-snapshottable-data-tester-49fsl: {default-scheduler } Scheduled: Successfully assigned snapshotting-7638/pvc-snapshottable-data-tester-49fsl to ip-172-20-38-144.ca-central-1.compute.internal
Oct 13 19:36:51.565: INFO: At 2021-10-13 19:35:56 +0000 UTC - event for pvc-snapshottable-data-tester-49fsl: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-70689a9e-b1bd-4918-9438-09ddc2398775" 
Oct 13 19:36:51.565: INFO: At 2021-10-13 19:35:59 +0000 UTC - event for pvc-snapshottable-data-tester-49fsl: {kubelet ip-172-20-38-144.ca-central-1.compute.internal} Created: Created container volume-tester
Oct 13 19:36:51.565: INFO: At 2021-10-13 19:35:59 +0000 UTC - event for pvc-snapshottable-data-tester-49fsl: {kubelet ip-172-20-38-144.ca-central-1.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" already present on machine
Oct 13 19:36:51.565: INFO: At 2021-10-13 19:35:59 +0000 UTC - event for pvc-snapshottable-data-tester-49fsl: {kubelet ip-172-20-38-144.ca-central-1.compute.internal} Started: Started container volume-tester
Oct 13 19:36:51.565: INFO: At 2021-10-13 19:36:00 +0000 UTC - event for pvc-snapshottable-data-tester-49fsl: {kubelet ip-172-20-38-144.ca-central-1.compute.internal} FailedMount: MountVolume.SetUp failed for volume "kube-api-access-lm226" : object "snapshotting-7638"/"kube-root-ca.crt" not registered
Oct 13 19:36:51.565: INFO: At 2021-10-13 19:36:01 +0000 UTC - event for pvc-rqb97: {ebs.csi.aws.com_ebs-csi-controller-54dc46fc7b-xwl4n_74d64462-c0ab-4356-84cb-5027dc4947d1 } Provisioning: External provisioner is provisioning volume for claim "snapshotting-7638/pvc-rqb97"
Oct 13 19:36:51.565: INFO: At 2021-10-13 19:36:01 +0000 UTC - event for pvc-rqb97: {persistentvolume-controller } ExternalProvisioning: waiting for a volume to be created, either by external provisioner "ebs.csi.aws.com" or manually created by system administrator
Oct 13 19:36:51.565: INFO: At 2021-10-13 19:36:01 +0000 UTC - event for pvc-rqb97: {persistentvolume-controller } WaitForFirstConsumer: waiting for first consumer to be created before binding
Oct 13 19:36:51.565: INFO: At 2021-10-13 19:36:04 +0000 UTC - event for pvc-rqb97: {ebs.csi.aws.com_ebs-csi-controller-54dc46fc7b-xwl4n_74d64462-c0ab-4356-84cb-5027dc4947d1 } ProvisioningSucceeded: Successfully provisioned volume pvc-db822ff5-53f9-46fb-857a-10a2c4119be1
Oct 13 19:36:51.565: INFO: At 2021-10-13 19:36:05 +0000 UTC - event for restored-pvc-tester-48zm8: {default-scheduler } Scheduled: Successfully assigned snapshotting-7638/restored-pvc-tester-48zm8 to ip-172-20-38-144.ca-central-1.compute.internal
Oct 13 19:36:51.565: INFO: At 2021-10-13 19:36:07 +0000 UTC - event for restored-pvc-tester-48zm8: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-db822ff5-53f9-46fb-857a-10a2c4119be1" 
Oct 13 19:36:51.565: INFO: At 2021-10-13 19:36:09 +0000 UTC - event for restored-pvc-tester-48zm8: {kubelet ip-172-20-38-144.ca-central-1.compute.internal} Started: Started container volume-tester
Oct 13 19:36:51.565: INFO: At 2021-10-13 19:36:09 +0000 UTC - event for restored-pvc-tester-48zm8: {kubelet ip-172-20-38-144.ca-central-1.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" already present on machine
Oct 13 19:36:51.565: INFO: At 2021-10-13 19:36:09 +0000 UTC - event for restored-pvc-tester-48zm8: {kubelet ip-172-20-38-144.ca-central-1.compute.internal} Created: Created container volume-tester
Oct 13 19:36:51.565: INFO: At 2021-10-13 19:36:12 +0000 UTC - event for restored-pvc-tester-48zm8: {kubelet ip-172-20-38-144.ca-central-1.compute.internal} Killing: Stopping container volume-tester
Oct 13 19:36:51.565: INFO: At 2021-10-13 19:36:43 +0000 UTC - event for restored-pvc-tester-48zm8: {kubelet ip-172-20-38-144.ca-central-1.compute.internal} FailedKillPod: error killing pod: failed to "KillContainer" for "volume-tester" with KillContainerError: "rpc error: code = NotFound desc = an error occurred when try to find container \"10d45b0c6010cb22cb7d99ef73bdf00a1fb4657881089f6be811f1bac77d957d\": not found"
Oct 13 19:36:51.595: INFO: POD  NODE  PHASE  GRACE  CONDITIONS
Oct 13 19:36:51.595: INFO: 
Oct 13 19:36:51.626: INFO: 
Logging node info for node ip-172-20-38-144.ca-central-1.compute.internal
Oct 13 19:36:51.656: INFO: Node Info: &Node{ObjectMeta:{ip-172-20-38-144.ca-central-1.compute.internal    13114671-0b8a-4ea2-833e-d947b2d0cb78 17430 0 2021-10-13 19:22:35 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:t3.medium beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:ca-central-1 failure-domain.beta.kubernetes.io/zone:ca-central-1a kops.k8s.io/instancegroup:nodes-ca-central-1a kubernetes.io/arch:amd64 kubernetes.io/hostname:ip-172-20-38-144.ca-central-1.compute.internal kubernetes.io/os:linux kubernetes.io/role:node node-role.kubernetes.io/node: node.kubernetes.io/instance-type:t3.medium topology.ebs.csi.aws.com/zone:ca-central-1a topology.kubernetes.io/region:ca-central-1 topology.kubernetes.io/zone:ca-central-1a] map[csi.volume.kubernetes.io/nodeid:{"ebs.csi.aws.com":"i-049bea91c6928b078"} node.alpha.kubernetes.io/ttl:0 projectcalico.org/IPv4Address:172.20.38.144/19 projectcalico.org/IPv4IPIPTunnelAddr:100.122.180.64 volumes.kubernetes.io/controller-managed-attach-detach:true] [] []  [{kops-controller Update v1 2021-10-13 19:22:35 +0000 UTC FieldsV1 {"f:metadata":{"f:labels":{"f:kops.k8s.io/instancegroup":{},"f:kubernetes.io/role":{},"f:node-role.kubernetes.io/node":{}}}}} {kube-controller-manager Update v1 2021-10-13 19:22:35 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"100.96.4.0/24\"":{}}}}} {kubelet Update v1 2021-10-13 19:22:35 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}}}} {calico-node Update v1 2021-10-13 19:22:48 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4IPIPTunnelAddr":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}}} {kubelet Update v1 2021-10-13 19:36:46 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:csi.volume.kubernetes.io/nodeid":{}},"f:labels":{"f:topology.ebs.csi.aws.com/zone":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}}}]},Spec:NodeSpec{PodCIDR:100.96.4.0/24,DoNotUseExternalID:,ProviderID:aws:///ca-central-1a/i-049bea91c6928b078,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[100.96.4.0/24],},Status:NodeStatus{Capacity:ResourceList{cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{49895047168 0} {<nil>}  BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{4059734016 0} {<nil>}  BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{44905542377 0} {<nil>} 44905542377 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{3954876416 0} {<nil>}  BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2021-10-13 19:22:48 +0000 UTC,LastTransitionTime:2021-10-13 19:22:48 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2021-10-13 19:36:46 +0000 UTC,LastTransitionTime:2021-10-13 19:22:35 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2021-10-13 19:36:46 +0000 UTC,LastTransitionTime:2021-10-13 19:22:35 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2021-10-13 19:36:46 +0000 UTC,LastTransitionTime:2021-10-13 19:22:35 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2021-10-13 19:36:46 +0000 UTC,LastTransitionTime:2021-10-13 19:22:45 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:172.20.38.144,},NodeAddress{Type:ExternalIP,Address:52.60.200.103,},NodeAddress{Type:Hostname,Address:ip-172-20-38-144.ca-central-1.compute.internal,},NodeAddress{Type:InternalDNS,Address:ip-172-20-38-144.ca-central-1.compute.internal,},NodeAddress{Type:ExternalDNS,Address:ec2-52-60-200-103.ca-central-1.compute.amazonaws.com,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:ec2d7839d6b04fa9247041815fb23635,SystemUUID:ec2d7839-d6b0-4fa9-2470-41815fb23635,BootID:7321fdac-64a7-419d-868e-4e85df408007,KernelVersion:5.11.0-1019-aws,OSImage:Ubuntu 20.04.3 LTS,ContainerRuntimeVersion:containerd://1.4.11,KubeletVersion:v1.22.1,KubeProxyVersion:v1.22.1,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[k8s.gcr.io/provider-aws/aws-ebs-csi-driver@sha256:5c03401df9e8fa384b66efc8bfd954a0371ad584a9430eca7d4d9338654d7fe0 k8s.gcr.io/provider-aws/aws-ebs-csi-driver:v1.4.0],SizeBytes:116606616,},ContainerImage{Names:[docker.io/calico/node@sha256:1ae8f57edec7c3a84cd48dd94132a1dcfd7c61bfff819c559f9379d4a56fe3b1 docker.io/calico/node:v3.20.2],SizeBytes:57637498,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/agnhost@sha256:8bd76a6a7778e203b61e18e5ee85b1faf52e6a30eb07e445a165ab90fe9633e3 k8s.gcr.io/e2e-test-images/agnhost:2.31],SizeBytes:49692421,},ContainerImage{Names:[docker.io/calico/cni@sha256:3dae26de7388ff3c124b9abd7e8d12863887391f23549c4aebfbfa20cc0700a5 docker.io/calico/cni:v3.20.2],SizeBytes:48389252,},ContainerImage{Names:[k8s.gcr.io/build-image/debian-iptables@sha256:abe8cef9e116f2d5ec1175c386e33841ff3386779138b425af876384b0fd7ccb k8s.gcr.io/build-image/debian-iptables:buster-v1.5.0],SizeBytes:38088315,},ContainerImage{Names:[k8s.gcr.io/kube-proxy@sha256:efcf1d5fb2fc95d28841f534f1385a4884230c7c876fb1b7cf66d2777ad6dc56 k8s.gcr.io/kube-proxy:v1.22.1],SizeBytes:35941601,},ContainerImage{Names:[docker.io/calico/pod2daemon-flexvol@sha256:4514cc1b2f7536fe1d514fad8a2c46103382243bb9db5ea2d0063fcd2001e8f7 docker.io/calico/pod2daemon-flexvol:v3.20.2],SizeBytes:9359081,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-node-driver-registrar@sha256:a61d309da54641db41fb8f35718f744e9f730d4d0384f8c4b186ddc9f06cbd5f k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.1.0],SizeBytes:9068367,},ContainerImage{Names:[k8s.gcr.io/sig-storage/livenessprobe@sha256:48da0e4ed7238ad461ea05f68c25921783c37b315f21a5c5a2780157a6460994 k8s.gcr.io/sig-storage/livenessprobe:v2.2.0],SizeBytes:8279778,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/nginx@sha256:503b7abb89e57383eba61cc8a9cb0b495ea575c516108f7d972a6ff6e1ab3c9b k8s.gcr.io/e2e-test-images/nginx:1.14-1],SizeBytes:6979365,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/busybox@sha256:39e1e963e5310e9c313bad51523be012ede7b35bb9316517d19089a010356592 k8s.gcr.io/e2e-test-images/busybox:1.29-1],SizeBytes:732746,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:927d98197ec1141a368550822d18fa1c60bdae27b78b0c004f705f548c07814f k8s.gcr.io/pause:3.2],SizeBytes:299513,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},}
Oct 13 19:36:51.657: INFO: 
... skipping 155 lines ...
    /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:108
      
      /tmp/kops.3EB0eDjiI/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.3EB0eDjiI/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-b6f7c24027-45100.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-7638 exec restored-pvc-tester-48zm8 --namespace=snapshotting-7638 -- 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-b6f7c24027-45100.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-7638 exec restored-pvc-tester-48zm8 --namespace=snapshotting-7638 -- 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.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:602
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)(allowExpansion)] volume-expand
... skipping 185 lines ...
    /tmp/kops.3EB0eDjiI/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumelimits.go:123
------------------------------


Summarizing 1 Failure:

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

Ran 144 of 485 Specs in 947.125 seconds
FAIL! -- 143 Passed | 1 Failed | 0 Pending | 341 Skipped


Ginkgo ran 1 suite in 16m57.127082728s
Test Suite Failed

Ginkgo 2.0 is coming soon!
==========================
Ginkgo 2.0 is under active development and will introduce several new features, improvements, and a small handful of breaking changes.
A release candidate for 2.0 is now available and 2.0 should GA in Fall 2021.  Please give the RC a try and send us feedback!
  - To learn more, view the migration guide at https://github.com/onsi/ginkgo/blob/ver2/docs/MIGRATING_TO_V2.md
... skipping 1525 lines ...