This job view page is being replaced by Spyglass soon. Check out the new job view.
PReddycharly: feat: add support for custom audience in aws oidc provider
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-09-26 20:28
Elapsed1h8m
Revision77b92960f75e2c807b849d370d6fee7aef74265e
Refs 12419

No Test Failures!


Error lines from build-log.txt

... skipping 571 lines ...
I0926 20:32:36.912623   12430 app.go:90] ID for this run: "3701040b-1f08-11ec-a3b0-9242b45c1669"
I0926 20:32:36.933812   12430 up.go:43] Cleaning up any leaked resources from previous cluster
I0926 20:32:36.933855   12430 dumplogs.go:40] /home/prow/go/src/k8s.io/kops/.bazelbuild/dist/linux/amd64/kops toolbox dump --name e2e-c3f2775103-c95b4.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ubuntu
I0926 20:32:36.953768   12441 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0926 20:32:36.953863   12441 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I0926 20:32:36.953868   12441 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Error: Cluster.kops.k8s.io "e2e-c3f2775103-c95b4.test-cncf-aws.k8s.io" not found
W0926 20:32:37.413156   12430 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0926 20:32:37.413240   12430 down.go:48] /home/prow/go/src/k8s.io/kops/.bazelbuild/dist/linux/amd64/kops delete cluster --name e2e-c3f2775103-c95b4.test-cncf-aws.k8s.io --yes
I0926 20:32:37.428752   12451 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0926 20:32:37.429462   12451 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I0926 20:32:37.429497   12451 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-c3f2775103-c95b4.test-cncf-aws.k8s.io" not found
I0926 20:32:37.892483   12430 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/09/26 20:32:37 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
I0926 20:32:37.900338   12430 http.go:37] curl https://ip.jsb.workers.dev
I0926 20:32:38.002226   12430 up.go:144] /home/prow/go/src/k8s.io/kops/.bazelbuild/dist/linux/amd64/kops create cluster --name e2e-c3f2775103-c95b4.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.70.108.110/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones eu-west-1a --master-size c5.large
I0926 20:32:38.020038   12462 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0926 20:32:38.020134   12462 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I0926 20:32:38.020139   12462 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0926 20:32:38.042172   12462 create_cluster.go:838] Using SSH public key: /etc/aws-ssh/aws-ssh-public
... skipping 33 lines ...
I0926 20:33:05.063645   12430 up.go:181] /home/prow/go/src/k8s.io/kops/.bazelbuild/dist/linux/amd64/kops validate cluster --name e2e-c3f2775103-c95b4.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0926 20:33:05.081094   12481 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0926 20:33:05.081186   12481 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I0926 20:33:05.081190   12481 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-c3f2775103-c95b4.test-cncf-aws.k8s.io

W0926 20:33:06.478664   12481 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-c3f2775103-c95b4.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0926 20:33:16.508136   12481 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-c3f2775103-c95b4.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0926 20:33:26.553558   12481 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0926 20:33:36.585886   12481 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0926 20:33:46.630567   12481 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0926 20:33:56.659701   12481 validate_cluster.go:232] (will retry): cluster not yet healthy
W0926 20:34:06.694698   12481 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-c3f2775103-c95b4.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0926 20:34:16.729073   12481 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0926 20:34:26.760100   12481 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0926 20:34:36.788797   12481 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0926 20:34:46.854298   12481 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0926 20:34:56.883403   12481 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0926 20:35:06.921991   12481 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0926 20:35:16.949476   12481 validate_cluster.go:232] (will retry): cluster not yet healthy
W0926 20:35:26.978107   12481 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-c3f2775103-c95b4.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0926 20:35:37.010767   12481 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0926 20:35:47.054229   12481 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0926 20:35:57.085532   12481 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0926 20:36:07.112462   12481 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0926 20:36:17.156294   12481 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0926 20:36:27.188702   12481 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0926 20:36:37.223205   12481 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0926 20:36:47.252814   12481 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0926 20:36:57.297163   12481 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 11 lines ...
Pod	kube-system/calico-node-8dnp5							system-node-critical pod "calico-node-8dnp5" is pending
Pod	kube-system/coredns-5dc785954d-qxkmv						system-cluster-critical pod "coredns-5dc785954d-qxkmv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mjvxh					system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mjvxh" is pending
Pod	kube-system/ebs-csi-node-9w782							system-node-critical pod "ebs-csi-node-9w782" is pending
Pod	kube-system/kube-controller-manager-ip-172-20-44-79.eu-west-1.compute.internal	system-cluster-critical pod "kube-controller-manager-ip-172-20-44-79.eu-west-1.compute.internal" is pending

Validation Failed
W0926 20:37:10.255347   12481 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 9 lines ...
Machine	i-0ede337f3f46589a5				machine "i-0ede337f3f46589a5" has not yet joined cluster
Pod	kube-system/calico-node-8dnp5			system-node-critical pod "calico-node-8dnp5" is pending
Pod	kube-system/coredns-5dc785954d-qxkmv		system-cluster-critical pod "coredns-5dc785954d-qxkmv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mjvxh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mjvxh" is pending
Pod	kube-system/ebs-csi-node-9w782			system-node-critical pod "ebs-csi-node-9w782" is pending

Validation Failed
W0926 20:37:22.168902   12481 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 17 lines ...
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mjvxh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mjvxh" is pending
Pod	kube-system/ebs-csi-node-8hskr			system-node-critical pod "ebs-csi-node-8hskr" is pending
Pod	kube-system/ebs-csi-node-9w782			system-node-critical pod "ebs-csi-node-9w782" is pending
Pod	kube-system/ebs-csi-node-ljls7			system-node-critical pod "ebs-csi-node-ljls7" is pending
Pod	kube-system/ebs-csi-node-njq6c			system-node-critical pod "ebs-csi-node-njq6c" is pending

Validation Failed
W0926 20:37:34.217243   12481 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 12 lines ...
Pod	kube-system/calico-node-jndnj	system-node-critical pod "calico-node-jndnj" is pending
Pod	kube-system/ebs-csi-node-8hskr	system-node-critical pod "ebs-csi-node-8hskr" is pending
Pod	kube-system/ebs-csi-node-9w782	system-node-critical pod "ebs-csi-node-9w782" is pending
Pod	kube-system/ebs-csi-node-ljls7	system-node-critical pod "ebs-csi-node-ljls7" is pending
Pod	kube-system/ebs-csi-node-njq6c	system-node-critical pod "ebs-csi-node-njq6c" is pending

Validation Failed
W0926 20:37:46.149472   12481 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 10 lines ...
Pod	kube-system/calico-node-8dnp5						system-node-critical pod "calico-node-8dnp5" is not ready (calico-node)
Pod	kube-system/calico-node-jndnj						system-node-critical pod "calico-node-jndnj" is not ready (calico-node)
Pod	kube-system/ebs-csi-node-8hskr						system-node-critical pod "ebs-csi-node-8hskr" is pending
Pod	kube-system/ebs-csi-node-njq6c						system-node-critical pod "ebs-csi-node-njq6c" is pending
Pod	kube-system/kube-proxy-ip-172-20-32-228.eu-west-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-32-228.eu-west-1.compute.internal" is pending

Validation Failed
W0926 20:37:58.202769   12481 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 21 lines ...
ip-172-20-49-137.eu-west-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-proxy-ip-172-20-39-136.eu-west-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-39-136.eu-west-1.compute.internal" is pending

Validation Failed
W0926 20:38:21.957560   12481 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 194 lines ...

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

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

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

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 136 lines ...
STEP: Creating a kubernetes client
Sep 26 20:41:34.999: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename topology
W0926 20:41:37.198498   25166 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Sep 26 20:41:37.198: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail to schedule a pod which has topologies that conflict with AllowedTopologies
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Sep 26 20:41:37.625: INFO: found topology map[topology.kubernetes.io/zone:eu-west-1a]
Sep 26 20:41:37.626: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Sep 26 20:41:37.626: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.GDxjzwo8j/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.GDxjzwo8j/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (immediate binding)] topology
    /tmp/kops.GDxjzwo8j/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.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 36 lines ...
Sep 26 20:41:38.664: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.GDxjzwo8j/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.GDxjzwo8j/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.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 4 lines ...
STEP: Creating a kubernetes client
Sep 26 20:41:34.805: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename volumemode
W0926 20:41:35.484983   25095 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Sep 26 20:41:35.485: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail to use a volume in a pod with mismatched mode [Slow]
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Sep 26 20:41:35.693: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Sep 26 20:41:36.437: INFO: Successfully created a new PD: "aws://eu-west-1a/vol-01d43ea88ce9b1bd7".
Sep 26 20:41:36.437: INFO: Creating resource for pre-provisioned PV
Sep 26 20:41:36.437: INFO: Creating PVC and PV
... skipping 4 lines ...
Sep 26 20:41:39.125: INFO: PersistentVolumeClaim pvc-nb8lb found but phase is Pending instead of Bound.
Sep 26 20:41:41.231: INFO: PersistentVolumeClaim pvc-nb8lb found but phase is Pending instead of Bound.
Sep 26 20:41:43.337: INFO: PersistentVolumeClaim pvc-nb8lb found and phase=Bound (6.422298209s)
Sep 26 20:41:43.337: INFO: Waiting up to 3m0s for PersistentVolume aws-hvx8s to have phase Bound
Sep 26 20:41:43.442: INFO: PersistentVolume aws-hvx8s found and phase=Bound (104.588303ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Sep 26 20:41:46.089: INFO: Deleting pod "pod-d76ae113-5b36-4f4d-87d8-19334a630bbd" in namespace "volumemode-3739"
Sep 26 20:41:46.199: INFO: Wait up to 5m0s for pod "pod-d76ae113-5b36-4f4d-87d8-19334a630bbd" to be fully deleted
STEP: Deleting pv and pvc
Sep 26 20:41:48.413: INFO: Deleting PersistentVolumeClaim "pvc-nb8lb"
Sep 26 20:41:48.518: INFO: Deleting PersistentVolume "aws-hvx8s"
Sep 26 20:41:48.861: INFO: Couldn't delete PD "aws://eu-west-1a/vol-01d43ea88ce9b1bd7", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01d43ea88ce9b1bd7 is currently attached to i-06820b72c8819710e
	status code: 400, request id: 5505f49f-46ad-4f22-8f75-52f062ccac4c
Sep 26 20:41:54.505: INFO: Couldn't delete PD "aws://eu-west-1a/vol-01d43ea88ce9b1bd7", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01d43ea88ce9b1bd7 is currently attached to i-06820b72c8819710e
	status code: 400, request id: 05327633-58f8-4d84-a382-47f6e743ff47
Sep 26 20:42:00.166: INFO: Successfully deleted PD "aws://eu-west-1a/vol-01d43ea88ce9b1bd7".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 26 20:42:00.166: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-3739" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.GDxjzwo8j/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.GDxjzwo8j/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
    /tmp/kops.GDxjzwo8j/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.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Sep 26 20:42:00.488: INFO: Driver aws doesn't support CSIInlineVolume -- skipping
[AfterEach] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral
... skipping 40 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 26 20:41:38.923: 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.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Sep 26 20:41:39.461: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Sep 26 20:41:39.462: INFO: Creating resource for dynamic PV
Sep 26 20:41:39.462: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-30834xrdz
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Sep 26 20:41:48.216: INFO: Deleting pod "pod-210767c3-4001-434c-919c-8ff8b688747d" in namespace "volumemode-3083"
Sep 26 20:41:48.329: INFO: Wait up to 5m0s for pod "pod-210767c3-4001-434c-919c-8ff8b688747d" to be fully deleted
STEP: Deleting pvc
Sep 26 20:41:50.760: INFO: Deleting PersistentVolumeClaim "awsx94n8"
Sep 26 20:41:50.868: INFO: Waiting up to 5m0s for PersistentVolume pvc-c8b04155-7b79-4d7a-af2d-e1028333a3f7 to get deleted
Sep 26 20:41:50.975: INFO: PersistentVolume pvc-c8b04155-7b79-4d7a-af2d-e1028333a3f7 found and phase=Released (107.162401ms)
... skipping 10 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.GDxjzwo8j/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.GDxjzwo8j/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
    /tmp/kops.GDxjzwo8j/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.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow]
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Sep 26 20:42:01.517: INFO: Driver "ebs.csi.aws.com" does not support volume type "PreprovisionedPV" - skipping
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow]
... skipping 52 lines ...
STEP: Deleting pod hostexec-ip-172-20-32-24.eu-west-1.compute.internal-wtr7p in namespace volumemode-3312
Sep 26 20:41:57.183: INFO: Deleting pod "pod-1861daa6-0190-47a9-98cb-17c469ee9d8b" in namespace "volumemode-3312"
Sep 26 20:41:57.291: INFO: Wait up to 5m0s for pod "pod-1861daa6-0190-47a9-98cb-17c469ee9d8b" to be fully deleted
STEP: Deleting pv and pvc
Sep 26 20:42:01.510: INFO: Deleting PersistentVolumeClaim "pvc-h2cww"
Sep 26 20:42:01.619: INFO: Deleting PersistentVolume "aws-5qm5k"
Sep 26 20:42:01.915: INFO: Couldn't delete PD "aws://eu-west-1a/vol-0e0d87efa79c29099", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e0d87efa79c29099 is currently attached to i-0ede337f3f46589a5
	status code: 400, request id: 0e86a5ff-f5ac-4570-aa9a-d423bdbcdfc8
Sep 26 20:42:07.617: INFO: Successfully deleted PD "aws://eu-west-1a/vol-0e0d87efa79c29099".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 26 20:42:07.617: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-3312" for this suite.
... skipping 24 lines ...
Sep 26 20:41:38.053: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-5551ltcfd
STEP: creating a claim
Sep 26 20:41:38.160: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Sep 26 20:41:38.378: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Sep 26 20:41:38.593: INFO: Error updating pvc awswm8n9: PersistentVolumeClaim "awswm8n9" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5551ltcfd",
  	... // 3 identical fields
  }

Sep 26 20:41:40.816: INFO: Error updating pvc awswm8n9: PersistentVolumeClaim "awswm8n9" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5551ltcfd",
  	... // 3 identical fields
  }

Sep 26 20:41:42.805: INFO: Error updating pvc awswm8n9: PersistentVolumeClaim "awswm8n9" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5551ltcfd",
  	... // 3 identical fields
  }

Sep 26 20:41:44.806: INFO: Error updating pvc awswm8n9: PersistentVolumeClaim "awswm8n9" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5551ltcfd",
  	... // 3 identical fields
  }

Sep 26 20:41:46.805: INFO: Error updating pvc awswm8n9: PersistentVolumeClaim "awswm8n9" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5551ltcfd",
  	... // 3 identical fields
  }

Sep 26 20:41:48.858: INFO: Error updating pvc awswm8n9: PersistentVolumeClaim "awswm8n9" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5551ltcfd",
  	... // 3 identical fields
  }

Sep 26 20:41:50.806: INFO: Error updating pvc awswm8n9: PersistentVolumeClaim "awswm8n9" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5551ltcfd",
  	... // 3 identical fields
  }

Sep 26 20:41:52.804: INFO: Error updating pvc awswm8n9: PersistentVolumeClaim "awswm8n9" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5551ltcfd",
  	... // 3 identical fields
  }

Sep 26 20:41:54.805: INFO: Error updating pvc awswm8n9: PersistentVolumeClaim "awswm8n9" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5551ltcfd",
  	... // 3 identical fields
  }

Sep 26 20:41:56.806: INFO: Error updating pvc awswm8n9: PersistentVolumeClaim "awswm8n9" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5551ltcfd",
  	... // 3 identical fields
  }

Sep 26 20:41:58.804: INFO: Error updating pvc awswm8n9: PersistentVolumeClaim "awswm8n9" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5551ltcfd",
  	... // 3 identical fields
  }

Sep 26 20:42:00.806: INFO: Error updating pvc awswm8n9: PersistentVolumeClaim "awswm8n9" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5551ltcfd",
  	... // 3 identical fields
  }

Sep 26 20:42:02.808: INFO: Error updating pvc awswm8n9: PersistentVolumeClaim "awswm8n9" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5551ltcfd",
  	... // 3 identical fields
  }

Sep 26 20:42:04.805: INFO: Error updating pvc awswm8n9: PersistentVolumeClaim "awswm8n9" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5551ltcfd",
  	... // 3 identical fields
  }

Sep 26 20:42:06.807: INFO: Error updating pvc awswm8n9: PersistentVolumeClaim "awswm8n9" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5551ltcfd",
  	... // 3 identical fields
  }

Sep 26 20:42:08.808: INFO: Error updating pvc awswm8n9: PersistentVolumeClaim "awswm8n9" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5551ltcfd",
  	... // 3 identical fields
  }

Sep 26 20:42:09.047: INFO: Error updating pvc awswm8n9: PersistentVolumeClaim "awswm8n9" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 65 lines ...
Sep 26 20:41:36.354: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4608k9rrn
STEP: creating a claim
Sep 26 20:41:36.460: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-h256
STEP: Creating a pod to test subpath
Sep 26 20:41:36.793: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-h256" in namespace "provisioning-4608" to be "Succeeded or Failed"
Sep 26 20:41:36.900: INFO: Pod "pod-subpath-test-dynamicpv-h256": Phase="Pending", Reason="", readiness=false. Elapsed: 104.716246ms
Sep 26 20:41:39.006: INFO: Pod "pod-subpath-test-dynamicpv-h256": Phase="Pending", Reason="", readiness=false. Elapsed: 2.210313629s
Sep 26 20:41:41.112: INFO: Pod "pod-subpath-test-dynamicpv-h256": Phase="Pending", Reason="", readiness=false. Elapsed: 4.31666133s
Sep 26 20:41:43.224: INFO: Pod "pod-subpath-test-dynamicpv-h256": Phase="Pending", Reason="", readiness=false. Elapsed: 6.428444498s
Sep 26 20:41:45.329: INFO: Pod "pod-subpath-test-dynamicpv-h256": Phase="Pending", Reason="", readiness=false. Elapsed: 8.533799149s
Sep 26 20:41:47.435: INFO: Pod "pod-subpath-test-dynamicpv-h256": Phase="Pending", Reason="", readiness=false. Elapsed: 10.640012722s
Sep 26 20:41:49.542: INFO: Pod "pod-subpath-test-dynamicpv-h256": Phase="Pending", Reason="", readiness=false. Elapsed: 12.74637115s
Sep 26 20:41:51.648: INFO: Pod "pod-subpath-test-dynamicpv-h256": Phase="Pending", Reason="", readiness=false. Elapsed: 14.852639949s
Sep 26 20:41:53.753: INFO: Pod "pod-subpath-test-dynamicpv-h256": Phase="Pending", Reason="", readiness=false. Elapsed: 16.958163397s
Sep 26 20:41:55.858: INFO: Pod "pod-subpath-test-dynamicpv-h256": Phase="Pending", Reason="", readiness=false. Elapsed: 19.063119326s
Sep 26 20:41:57.965: INFO: Pod "pod-subpath-test-dynamicpv-h256": Phase="Pending", Reason="", readiness=false. Elapsed: 21.169642232s
Sep 26 20:42:00.072: INFO: Pod "pod-subpath-test-dynamicpv-h256": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.276228234s
STEP: Saw pod success
Sep 26 20:42:00.072: INFO: Pod "pod-subpath-test-dynamicpv-h256" satisfied condition "Succeeded or Failed"
Sep 26 20:42:00.176: INFO: Trying to get logs from node ip-172-20-32-228.eu-west-1.compute.internal pod pod-subpath-test-dynamicpv-h256 container test-container-volume-dynamicpv-h256: <nil>
STEP: delete the pod
Sep 26 20:42:00.397: INFO: Waiting for pod pod-subpath-test-dynamicpv-h256 to disappear
Sep 26 20:42:00.501: INFO: Pod pod-subpath-test-dynamicpv-h256 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-h256
Sep 26 20:42:00.501: INFO: Deleting pod "pod-subpath-test-dynamicpv-h256" in namespace "provisioning-4608"
... skipping 52 lines ...
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 26 20:42:12.532: 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.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Sep 26 20:42:13.167: INFO: found topology map[topology.kubernetes.io/zone:eu-west-1a]
Sep 26 20:42:13.167: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Sep 26 20:42:13.167: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.GDxjzwo8j/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.GDxjzwo8j/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (delayed binding)] topology
    /tmp/kops.GDxjzwo8j/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.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 50 lines ...
STEP: Creating a kubernetes client
Sep 26 20:41:35.025: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename provisioning
W0926 20:41:36.904835   25216 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Sep 26 20:41:36.904: 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.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Sep 26 20:41:37.115: INFO: Creating resource for dynamic PV
Sep 26 20:41:37.115: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3080-e2e-scr954b
STEP: creating a claim
Sep 26 20:41:37.223: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-ntms
STEP: Checking for subpath error in container status
Sep 26 20:41:55.757: INFO: Deleting pod "pod-subpath-test-dynamicpv-ntms" in namespace "provisioning-3080"
Sep 26 20:41:55.865: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-ntms" to be fully deleted
STEP: Deleting pod
Sep 26 20:42:00.084: INFO: Deleting pod "pod-subpath-test-dynamicpv-ntms" in namespace "provisioning-3080"
STEP: Deleting pvc
Sep 26 20:42:00.405: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comrxs2h"
... skipping 11 lines ...

• [SLOW TEST:41.338 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.GDxjzwo8j/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.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [sig-storage] Volume FStype [Feature:vsphere]
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 26 20:42:16.365: INFO: >>> kubeConfig: /root/.kube/config
... skipping 29 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.GDxjzwo8j/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.GDxjzwo8j/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.GDxjzwo8j/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.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 23 lines ...
Sep 26 20:41:43.379: INFO: PersistentVolumeClaim pvc-q2wt6 found but phase is Pending instead of Bound.
Sep 26 20:41:45.487: INFO: PersistentVolumeClaim pvc-q2wt6 found and phase=Bound (8.533641398s)
Sep 26 20:41:45.487: INFO: Waiting up to 3m0s for PersistentVolume aws-chpsq to have phase Bound
Sep 26 20:41:45.594: INFO: PersistentVolume aws-chpsq found and phase=Bound (106.521628ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-98lx
STEP: Creating a pod to test exec-volume-test
Sep 26 20:41:45.915: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-98lx" in namespace "volume-6448" to be "Succeeded or Failed"
Sep 26 20:41:46.021: INFO: Pod "exec-volume-test-preprovisionedpv-98lx": Phase="Pending", Reason="", readiness=false. Elapsed: 106.057446ms
Sep 26 20:41:48.128: INFO: Pod "exec-volume-test-preprovisionedpv-98lx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.212669238s
Sep 26 20:41:50.236: INFO: Pod "exec-volume-test-preprovisionedpv-98lx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.320960947s
Sep 26 20:41:52.343: INFO: Pod "exec-volume-test-preprovisionedpv-98lx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.428136242s
Sep 26 20:41:54.449: INFO: Pod "exec-volume-test-preprovisionedpv-98lx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.533867508s
Sep 26 20:41:56.556: INFO: Pod "exec-volume-test-preprovisionedpv-98lx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.640949775s
Sep 26 20:41:58.664: INFO: Pod "exec-volume-test-preprovisionedpv-98lx": Phase="Pending", Reason="", readiness=false. Elapsed: 12.749182961s
Sep 26 20:42:00.770: INFO: Pod "exec-volume-test-preprovisionedpv-98lx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.854791721s
STEP: Saw pod success
Sep 26 20:42:00.770: INFO: Pod "exec-volume-test-preprovisionedpv-98lx" satisfied condition "Succeeded or Failed"
Sep 26 20:42:00.875: INFO: Trying to get logs from node ip-172-20-32-228.eu-west-1.compute.internal pod exec-volume-test-preprovisionedpv-98lx container exec-container-preprovisionedpv-98lx: <nil>
STEP: delete the pod
Sep 26 20:42:01.094: INFO: Waiting for pod exec-volume-test-preprovisionedpv-98lx to disappear
Sep 26 20:42:01.200: INFO: Pod exec-volume-test-preprovisionedpv-98lx no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-98lx
Sep 26 20:42:01.200: INFO: Deleting pod "exec-volume-test-preprovisionedpv-98lx" in namespace "volume-6448"
STEP: Deleting pv and pvc
Sep 26 20:42:01.305: INFO: Deleting PersistentVolumeClaim "pvc-q2wt6"
Sep 26 20:42:01.412: INFO: Deleting PersistentVolume "aws-chpsq"
Sep 26 20:42:01.726: INFO: Couldn't delete PD "aws://eu-west-1a/vol-01d8376fbed760c80", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01d8376fbed760c80 is currently attached to i-06820b72c8819710e
	status code: 400, request id: 069273fa-da90-4b64-b58b-07e3171da668
Sep 26 20:42:07.385: INFO: Couldn't delete PD "aws://eu-west-1a/vol-01d8376fbed760c80", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01d8376fbed760c80 is currently attached to i-06820b72c8819710e
	status code: 400, request id: 76c1a746-7489-494e-96ca-cd856635ddbb
Sep 26 20:42:13.020: INFO: Couldn't delete PD "aws://eu-west-1a/vol-01d8376fbed760c80", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01d8376fbed760c80 is currently attached to i-06820b72c8819710e
	status code: 400, request id: f3d6fb1f-5581-4fe3-bc46-e7997910cce8
Sep 26 20:42:18.647: INFO: Successfully deleted PD "aws://eu-west-1a/vol-01d8376fbed760c80".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 26 20:42:18.647: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-6448" for this suite.
... skipping 71 lines ...
Sep 26 20:41:35.542: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8458-e2e-sctcqvl
STEP: creating a claim
Sep 26 20:41:35.651: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-2jrs
STEP: Creating a pod to test multi_subpath
Sep 26 20:41:35.975: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-2jrs" in namespace "provisioning-8458" to be "Succeeded or Failed"
Sep 26 20:41:36.082: INFO: Pod "pod-subpath-test-dynamicpv-2jrs": Phase="Pending", Reason="", readiness=false. Elapsed: 106.71898ms
Sep 26 20:41:38.192: INFO: Pod "pod-subpath-test-dynamicpv-2jrs": Phase="Pending", Reason="", readiness=false. Elapsed: 2.217119301s
Sep 26 20:41:40.299: INFO: Pod "pod-subpath-test-dynamicpv-2jrs": Phase="Pending", Reason="", readiness=false. Elapsed: 4.324148283s
Sep 26 20:41:42.409: INFO: Pod "pod-subpath-test-dynamicpv-2jrs": Phase="Pending", Reason="", readiness=false. Elapsed: 6.433857761s
Sep 26 20:41:44.516: INFO: Pod "pod-subpath-test-dynamicpv-2jrs": Phase="Pending", Reason="", readiness=false. Elapsed: 8.541298957s
Sep 26 20:41:46.634: INFO: Pod "pod-subpath-test-dynamicpv-2jrs": Phase="Pending", Reason="", readiness=false. Elapsed: 10.658688135s
Sep 26 20:41:48.743: INFO: Pod "pod-subpath-test-dynamicpv-2jrs": Phase="Pending", Reason="", readiness=false. Elapsed: 12.768163941s
Sep 26 20:41:50.850: INFO: Pod "pod-subpath-test-dynamicpv-2jrs": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.875438465s
STEP: Saw pod success
Sep 26 20:41:50.851: INFO: Pod "pod-subpath-test-dynamicpv-2jrs" satisfied condition "Succeeded or Failed"
Sep 26 20:41:50.958: INFO: Trying to get logs from node ip-172-20-32-228.eu-west-1.compute.internal pod pod-subpath-test-dynamicpv-2jrs container test-container-subpath-dynamicpv-2jrs: <nil>
STEP: delete the pod
Sep 26 20:41:51.726: INFO: Waiting for pod pod-subpath-test-dynamicpv-2jrs to disappear
Sep 26 20:41:51.833: INFO: Pod pod-subpath-test-dynamicpv-2jrs no longer exists
STEP: Deleting pod
Sep 26 20:41:51.833: INFO: Deleting pod "pod-subpath-test-dynamicpv-2jrs" in namespace "provisioning-8458"
... skipping 61 lines ...
Sep 26 20:41:35.905: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4128jm6fv
STEP: creating a claim
Sep 26 20:41:36.011: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-sbmh
STEP: Creating a pod to test subpath
Sep 26 20:41:36.329: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-sbmh" in namespace "provisioning-4128" to be "Succeeded or Failed"
Sep 26 20:41:36.434: INFO: Pod "pod-subpath-test-dynamicpv-sbmh": Phase="Pending", Reason="", readiness=false. Elapsed: 105.30076ms
Sep 26 20:41:38.545: INFO: Pod "pod-subpath-test-dynamicpv-sbmh": Phase="Pending", Reason="", readiness=false. Elapsed: 2.2163258s
Sep 26 20:41:40.663: INFO: Pod "pod-subpath-test-dynamicpv-sbmh": Phase="Pending", Reason="", readiness=false. Elapsed: 4.334190936s
Sep 26 20:41:42.770: INFO: Pod "pod-subpath-test-dynamicpv-sbmh": Phase="Pending", Reason="", readiness=false. Elapsed: 6.441254248s
Sep 26 20:41:44.876: INFO: Pod "pod-subpath-test-dynamicpv-sbmh": Phase="Pending", Reason="", readiness=false. Elapsed: 8.547005732s
Sep 26 20:41:46.983: INFO: Pod "pod-subpath-test-dynamicpv-sbmh": Phase="Pending", Reason="", readiness=false. Elapsed: 10.653897621s
Sep 26 20:41:49.088: INFO: Pod "pod-subpath-test-dynamicpv-sbmh": Phase="Pending", Reason="", readiness=false. Elapsed: 12.759684127s
Sep 26 20:41:51.197: INFO: Pod "pod-subpath-test-dynamicpv-sbmh": Phase="Pending", Reason="", readiness=false. Elapsed: 14.868597357s
Sep 26 20:41:53.304: INFO: Pod "pod-subpath-test-dynamicpv-sbmh": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.97532675s
STEP: Saw pod success
Sep 26 20:41:53.304: INFO: Pod "pod-subpath-test-dynamicpv-sbmh" satisfied condition "Succeeded or Failed"
Sep 26 20:41:53.409: INFO: Trying to get logs from node ip-172-20-32-228.eu-west-1.compute.internal pod pod-subpath-test-dynamicpv-sbmh container test-container-subpath-dynamicpv-sbmh: <nil>
STEP: delete the pod
Sep 26 20:41:53.629: INFO: Waiting for pod pod-subpath-test-dynamicpv-sbmh to disappear
Sep 26 20:41:53.738: INFO: Pod pod-subpath-test-dynamicpv-sbmh no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-sbmh
Sep 26 20:41:53.738: INFO: Deleting pod "pod-subpath-test-dynamicpv-sbmh" in namespace "provisioning-4128"
STEP: Creating pod pod-subpath-test-dynamicpv-sbmh
STEP: Creating a pod to test subpath
Sep 26 20:41:53.949: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-sbmh" in namespace "provisioning-4128" to be "Succeeded or Failed"
Sep 26 20:41:54.057: INFO: Pod "pod-subpath-test-dynamicpv-sbmh": Phase="Pending", Reason="", readiness=false. Elapsed: 107.431141ms
Sep 26 20:41:56.162: INFO: Pod "pod-subpath-test-dynamicpv-sbmh": Phase="Pending", Reason="", readiness=false. Elapsed: 2.21292208s
Sep 26 20:41:58.269: INFO: Pod "pod-subpath-test-dynamicpv-sbmh": Phase="Pending", Reason="", readiness=false. Elapsed: 4.319390928s
Sep 26 20:42:00.375: INFO: Pod "pod-subpath-test-dynamicpv-sbmh": Phase="Pending", Reason="", readiness=false. Elapsed: 6.425741711s
Sep 26 20:42:02.482: INFO: Pod "pod-subpath-test-dynamicpv-sbmh": Phase="Pending", Reason="", readiness=false. Elapsed: 8.532119191s
Sep 26 20:42:04.590: INFO: Pod "pod-subpath-test-dynamicpv-sbmh": Phase="Pending", Reason="", readiness=false. Elapsed: 10.640315776s
Sep 26 20:42:06.695: INFO: Pod "pod-subpath-test-dynamicpv-sbmh": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.746072574s
STEP: Saw pod success
Sep 26 20:42:06.696: INFO: Pod "pod-subpath-test-dynamicpv-sbmh" satisfied condition "Succeeded or Failed"
Sep 26 20:42:06.801: INFO: Trying to get logs from node ip-172-20-32-228.eu-west-1.compute.internal pod pod-subpath-test-dynamicpv-sbmh container test-container-subpath-dynamicpv-sbmh: <nil>
STEP: delete the pod
Sep 26 20:42:07.021: INFO: Waiting for pod pod-subpath-test-dynamicpv-sbmh to disappear
Sep 26 20:42:07.126: INFO: Pod pod-subpath-test-dynamicpv-sbmh no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-sbmh
Sep 26 20:42:07.126: INFO: Deleting pod "pod-subpath-test-dynamicpv-sbmh" in namespace "provisioning-4128"
... skipping 107 lines ...
Sep 26 20:41:36.060: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-315-e2e-scxx772
STEP: creating a claim
Sep 26 20:41:36.170: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-c7rn
STEP: Creating a pod to test subpath
Sep 26 20:41:36.491: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-c7rn" in namespace "provisioning-315" to be "Succeeded or Failed"
Sep 26 20:41:36.597: INFO: Pod "pod-subpath-test-dynamicpv-c7rn": Phase="Pending", Reason="", readiness=false. Elapsed: 105.35179ms
Sep 26 20:41:38.702: INFO: Pod "pod-subpath-test-dynamicpv-c7rn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.211089272s
Sep 26 20:41:40.811: INFO: Pod "pod-subpath-test-dynamicpv-c7rn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.319458679s
Sep 26 20:41:42.919: INFO: Pod "pod-subpath-test-dynamicpv-c7rn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.427504136s
Sep 26 20:41:45.026: INFO: Pod "pod-subpath-test-dynamicpv-c7rn": Phase="Pending", Reason="", readiness=false. Elapsed: 8.534305972s
Sep 26 20:41:47.133: INFO: Pod "pod-subpath-test-dynamicpv-c7rn": Phase="Pending", Reason="", readiness=false. Elapsed: 10.641614431s
Sep 26 20:41:49.240: INFO: Pod "pod-subpath-test-dynamicpv-c7rn": Phase="Pending", Reason="", readiness=false. Elapsed: 12.74865189s
Sep 26 20:41:51.347: INFO: Pod "pod-subpath-test-dynamicpv-c7rn": Phase="Pending", Reason="", readiness=false. Elapsed: 14.85590357s
Sep 26 20:41:53.454: INFO: Pod "pod-subpath-test-dynamicpv-c7rn": Phase="Pending", Reason="", readiness=false. Elapsed: 16.962929412s
Sep 26 20:41:55.560: INFO: Pod "pod-subpath-test-dynamicpv-c7rn": Phase="Pending", Reason="", readiness=false. Elapsed: 19.068811962s
Sep 26 20:41:57.666: INFO: Pod "pod-subpath-test-dynamicpv-c7rn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.174689862s
STEP: Saw pod success
Sep 26 20:41:57.666: INFO: Pod "pod-subpath-test-dynamicpv-c7rn" satisfied condition "Succeeded or Failed"
Sep 26 20:41:57.772: INFO: Trying to get logs from node ip-172-20-39-136.eu-west-1.compute.internal pod pod-subpath-test-dynamicpv-c7rn container test-container-subpath-dynamicpv-c7rn: <nil>
STEP: delete the pod
Sep 26 20:41:58.534: INFO: Waiting for pod pod-subpath-test-dynamicpv-c7rn to disappear
Sep 26 20:41:58.639: INFO: Pod pod-subpath-test-dynamicpv-c7rn no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-c7rn
Sep 26 20:41:58.639: INFO: Deleting pod "pod-subpath-test-dynamicpv-c7rn" in namespace "provisioning-315"
... skipping 165 lines ...
Sep 26 20:42:01.021: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-147982h68
STEP: creating a claim
Sep 26 20:42:01.127: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-twhr
STEP: Creating a pod to test multi_subpath
Sep 26 20:42:01.444: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-twhr" in namespace "provisioning-1479" to be "Succeeded or Failed"
Sep 26 20:42:01.549: INFO: Pod "pod-subpath-test-dynamicpv-twhr": Phase="Pending", Reason="", readiness=false. Elapsed: 104.700927ms
Sep 26 20:42:03.661: INFO: Pod "pod-subpath-test-dynamicpv-twhr": Phase="Pending", Reason="", readiness=false. Elapsed: 2.217120707s
Sep 26 20:42:05.775: INFO: Pod "pod-subpath-test-dynamicpv-twhr": Phase="Pending", Reason="", readiness=false. Elapsed: 4.331416281s
Sep 26 20:42:07.881: INFO: Pod "pod-subpath-test-dynamicpv-twhr": Phase="Pending", Reason="", readiness=false. Elapsed: 6.436591294s
Sep 26 20:42:09.988: INFO: Pod "pod-subpath-test-dynamicpv-twhr": Phase="Pending", Reason="", readiness=false. Elapsed: 8.544305986s
Sep 26 20:42:12.094: INFO: Pod "pod-subpath-test-dynamicpv-twhr": Phase="Pending", Reason="", readiness=false. Elapsed: 10.650217667s
Sep 26 20:42:14.202: INFO: Pod "pod-subpath-test-dynamicpv-twhr": Phase="Pending", Reason="", readiness=false. Elapsed: 12.757819036s
Sep 26 20:42:16.309: INFO: Pod "pod-subpath-test-dynamicpv-twhr": Phase="Pending", Reason="", readiness=false. Elapsed: 14.865164478s
Sep 26 20:42:18.414: INFO: Pod "pod-subpath-test-dynamicpv-twhr": Phase="Pending", Reason="", readiness=false. Elapsed: 16.97036895s
Sep 26 20:42:20.520: INFO: Pod "pod-subpath-test-dynamicpv-twhr": Phase="Pending", Reason="", readiness=false. Elapsed: 19.076373735s
Sep 26 20:42:22.626: INFO: Pod "pod-subpath-test-dynamicpv-twhr": Phase="Pending", Reason="", readiness=false. Elapsed: 21.181793474s
Sep 26 20:42:24.731: INFO: Pod "pod-subpath-test-dynamicpv-twhr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.286954487s
STEP: Saw pod success
Sep 26 20:42:24.731: INFO: Pod "pod-subpath-test-dynamicpv-twhr" satisfied condition "Succeeded or Failed"
Sep 26 20:42:24.836: INFO: Trying to get logs from node ip-172-20-32-228.eu-west-1.compute.internal pod pod-subpath-test-dynamicpv-twhr container test-container-subpath-dynamicpv-twhr: <nil>
STEP: delete the pod
Sep 26 20:42:25.054: INFO: Waiting for pod pod-subpath-test-dynamicpv-twhr to disappear
Sep 26 20:42:25.159: INFO: Pod pod-subpath-test-dynamicpv-twhr no longer exists
STEP: Deleting pod
Sep 26 20:42:25.159: INFO: Deleting pod "pod-subpath-test-dynamicpv-twhr" in namespace "provisioning-1479"
... skipping 348 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 26 20:42:28.621: 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.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Sep 26 20:42:29.148: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Sep 26 20:42:29.148: INFO: Creating resource for dynamic PV
Sep 26 20:42:29.148: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-758677x4j
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Sep 26 20:42:35.894: INFO: Deleting pod "pod-a855f0d9-c433-4c2d-959a-ee91d637adfd" in namespace "volumemode-7586"
Sep 26 20:42:36.000: INFO: Wait up to 5m0s for pod "pod-a855f0d9-c433-4c2d-959a-ee91d637adfd" to be fully deleted
STEP: Deleting pvc
Sep 26 20:42:38.426: INFO: Deleting PersistentVolumeClaim "aws8pbzh"
Sep 26 20:42:38.539: INFO: Waiting up to 5m0s for PersistentVolume pvc-64101e8c-982b-4baf-b4c9-b6c3a8eade17 to get deleted
Sep 26 20:42:38.644: INFO: PersistentVolume pvc-64101e8c-982b-4baf-b4c9-b6c3a8eade17 found and phase=Released (105.549586ms)
... skipping 11 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.GDxjzwo8j/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.GDxjzwo8j/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (block volmode)] volumeMode
    /tmp/kops.GDxjzwo8j/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.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 64 lines ...
Sep 26 20:42:52.778: INFO: Waiting for pod aws-client to disappear
Sep 26 20:42:52.886: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Sep 26 20:42:52.886: INFO: Deleting PersistentVolumeClaim "pvc-4btzp"
Sep 26 20:42:52.994: INFO: Deleting PersistentVolume "aws-h9ncs"
Sep 26 20:42:53.764: INFO: Couldn't delete PD "aws://eu-west-1a/vol-0a7b1c61f62f94d9b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a7b1c61f62f94d9b is currently attached to i-06820b72c8819710e
	status code: 400, request id: 90a3cd13-c274-4886-95ac-824a96ca030d
Sep 26 20:42:59.358: INFO: Successfully deleted PD "aws://eu-west-1a/vol-0a7b1c61f62f94d9b".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 26 20:42:59.358: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-738" for this suite.
... skipping 165 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.GDxjzwo8j/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.GDxjzwo8j/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.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 12 lines ...
Sep 26 20:42:08.380: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9496m942j
STEP: creating a claim
Sep 26 20:42:08.488: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-krb9
STEP: Creating a pod to test atomic-volume-subpath
Sep 26 20:42:08.815: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-krb9" in namespace "provisioning-9496" to be "Succeeded or Failed"
Sep 26 20:42:08.942: INFO: Pod "pod-subpath-test-dynamicpv-krb9": Phase="Pending", Reason="", readiness=false. Elapsed: 127.359796ms
Sep 26 20:42:11.050: INFO: Pod "pod-subpath-test-dynamicpv-krb9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.235747478s
Sep 26 20:42:13.159: INFO: Pod "pod-subpath-test-dynamicpv-krb9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.34436366s
Sep 26 20:42:15.267: INFO: Pod "pod-subpath-test-dynamicpv-krb9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.452697634s
Sep 26 20:42:17.377: INFO: Pod "pod-subpath-test-dynamicpv-krb9": Phase="Pending", Reason="", readiness=false. Elapsed: 8.562489981s
Sep 26 20:42:19.486: INFO: Pod "pod-subpath-test-dynamicpv-krb9": Phase="Pending", Reason="", readiness=false. Elapsed: 10.671121533s
... skipping 7 lines ...
Sep 26 20:42:36.372: INFO: Pod "pod-subpath-test-dynamicpv-krb9": Phase="Running", Reason="", readiness=true. Elapsed: 27.557707653s
Sep 26 20:42:38.480: INFO: Pod "pod-subpath-test-dynamicpv-krb9": Phase="Running", Reason="", readiness=true. Elapsed: 29.665743777s
Sep 26 20:42:40.589: INFO: Pod "pod-subpath-test-dynamicpv-krb9": Phase="Running", Reason="", readiness=true. Elapsed: 31.774026296s
Sep 26 20:42:42.698: INFO: Pod "pod-subpath-test-dynamicpv-krb9": Phase="Running", Reason="", readiness=true. Elapsed: 33.883384249s
Sep 26 20:42:44.806: INFO: Pod "pod-subpath-test-dynamicpv-krb9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 35.991644878s
STEP: Saw pod success
Sep 26 20:42:44.806: INFO: Pod "pod-subpath-test-dynamicpv-krb9" satisfied condition "Succeeded or Failed"
Sep 26 20:42:44.914: INFO: Trying to get logs from node ip-172-20-39-136.eu-west-1.compute.internal pod pod-subpath-test-dynamicpv-krb9 container test-container-subpath-dynamicpv-krb9: <nil>
STEP: delete the pod
Sep 26 20:42:45.149: INFO: Waiting for pod pod-subpath-test-dynamicpv-krb9 to disappear
Sep 26 20:42:45.260: INFO: Pod pod-subpath-test-dynamicpv-krb9 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-krb9
Sep 26 20:42:45.260: INFO: Deleting pod "pod-subpath-test-dynamicpv-krb9" in namespace "provisioning-9496"
... skipping 93 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 26 20:42:36.253: 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.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Sep 26 20:42:36.783: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Sep 26 20:42:36.783: INFO: Creating resource for dynamic PV
Sep 26 20:42:36.783: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-47037lsk8
STEP: creating a claim
Sep 26 20:42:36.889: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-rbdk
STEP: Checking for subpath error in container status
Sep 26 20:42:49.453: INFO: Deleting pod "pod-subpath-test-dynamicpv-rbdk" in namespace "provisioning-4703"
Sep 26 20:42:49.564: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-rbdk" to be fully deleted
STEP: Deleting pod
Sep 26 20:42:51.776: INFO: Deleting pod "pod-subpath-test-dynamicpv-rbdk" in namespace "provisioning-4703"
STEP: Deleting pvc
Sep 26 20:42:52.092: INFO: Deleting PersistentVolumeClaim "awsrzdk8"
... skipping 12 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.GDxjzwo8j/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.GDxjzwo8j/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath directory is outside the volume [Slow][LinuxOnly]
      /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Sep 26 20:43:02.858: INFO: Driver "ebs.csi.aws.com" does not support volume type "PreprovisionedPV" - skipping
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
... skipping 381 lines ...
Sep 26 20:42:17.644: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-592-e2e-sc92sjq
STEP: creating a claim
Sep 26 20:42:17.751: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-8j2z
STEP: Creating a pod to test subpath
Sep 26 20:42:18.071: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-8j2z" in namespace "provisioning-592" to be "Succeeded or Failed"
Sep 26 20:42:18.177: INFO: Pod "pod-subpath-test-dynamicpv-8j2z": Phase="Pending", Reason="", readiness=false. Elapsed: 105.574451ms
Sep 26 20:42:20.288: INFO: Pod "pod-subpath-test-dynamicpv-8j2z": Phase="Pending", Reason="", readiness=false. Elapsed: 2.216515143s
Sep 26 20:42:22.395: INFO: Pod "pod-subpath-test-dynamicpv-8j2z": Phase="Pending", Reason="", readiness=false. Elapsed: 4.323638448s
Sep 26 20:42:24.501: INFO: Pod "pod-subpath-test-dynamicpv-8j2z": Phase="Pending", Reason="", readiness=false. Elapsed: 6.429426622s
Sep 26 20:42:26.608: INFO: Pod "pod-subpath-test-dynamicpv-8j2z": Phase="Pending", Reason="", readiness=false. Elapsed: 8.536384596s
Sep 26 20:42:28.714: INFO: Pod "pod-subpath-test-dynamicpv-8j2z": Phase="Pending", Reason="", readiness=false. Elapsed: 10.64283073s
Sep 26 20:42:30.820: INFO: Pod "pod-subpath-test-dynamicpv-8j2z": Phase="Pending", Reason="", readiness=false. Elapsed: 12.748565217s
Sep 26 20:42:32.930: INFO: Pod "pod-subpath-test-dynamicpv-8j2z": Phase="Pending", Reason="", readiness=false. Elapsed: 14.859168347s
Sep 26 20:42:35.036: INFO: Pod "pod-subpath-test-dynamicpv-8j2z": Phase="Pending", Reason="", readiness=false. Elapsed: 16.964721028s
Sep 26 20:42:37.204: INFO: Pod "pod-subpath-test-dynamicpv-8j2z": Phase="Pending", Reason="", readiness=false. Elapsed: 19.132406995s
Sep 26 20:42:39.310: INFO: Pod "pod-subpath-test-dynamicpv-8j2z": Phase="Pending", Reason="", readiness=false. Elapsed: 21.238872251s
Sep 26 20:42:41.428: INFO: Pod "pod-subpath-test-dynamicpv-8j2z": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.356643643s
STEP: Saw pod success
Sep 26 20:42:41.428: INFO: Pod "pod-subpath-test-dynamicpv-8j2z" satisfied condition "Succeeded or Failed"
Sep 26 20:42:41.537: INFO: Trying to get logs from node ip-172-20-32-228.eu-west-1.compute.internal pod pod-subpath-test-dynamicpv-8j2z container test-container-subpath-dynamicpv-8j2z: <nil>
STEP: delete the pod
Sep 26 20:42:41.768: INFO: Waiting for pod pod-subpath-test-dynamicpv-8j2z to disappear
Sep 26 20:42:41.873: INFO: Pod pod-subpath-test-dynamicpv-8j2z no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-8j2z
Sep 26 20:42:41.873: INFO: Deleting pod "pod-subpath-test-dynamicpv-8j2z" in namespace "provisioning-592"
... skipping 70 lines ...
Sep 26 20:42:47.681: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-1627-e2e-scxxq7b
STEP: creating a claim
Sep 26 20:42:47.788: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Sep 26 20:42:48.003: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Sep 26 20:42:48.218: INFO: Error updating pvc ebs.csi.aws.comjd2c4: PersistentVolumeClaim "ebs.csi.aws.comjd2c4" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1627-e2e-scxxq7b",
  	... // 3 identical fields
  }

Sep 26 20:42:50.431: INFO: Error updating pvc ebs.csi.aws.comjd2c4: PersistentVolumeClaim "ebs.csi.aws.comjd2c4" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1627-e2e-scxxq7b",
  	... // 3 identical fields
  }

Sep 26 20:42:52.438: INFO: Error updating pvc ebs.csi.aws.comjd2c4: PersistentVolumeClaim "ebs.csi.aws.comjd2c4" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1627-e2e-scxxq7b",
  	... // 3 identical fields
  }

Sep 26 20:42:54.431: INFO: Error updating pvc ebs.csi.aws.comjd2c4: PersistentVolumeClaim "ebs.csi.aws.comjd2c4" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1627-e2e-scxxq7b",
  	... // 3 identical fields
  }

Sep 26 20:42:56.458: INFO: Error updating pvc ebs.csi.aws.comjd2c4: PersistentVolumeClaim "ebs.csi.aws.comjd2c4" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1627-e2e-scxxq7b",
  	... // 3 identical fields
  }

Sep 26 20:42:58.431: INFO: Error updating pvc ebs.csi.aws.comjd2c4: PersistentVolumeClaim "ebs.csi.aws.comjd2c4" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1627-e2e-scxxq7b",
  	... // 3 identical fields
  }

Sep 26 20:43:00.431: INFO: Error updating pvc ebs.csi.aws.comjd2c4: PersistentVolumeClaim "ebs.csi.aws.comjd2c4" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1627-e2e-scxxq7b",
  	... // 3 identical fields
  }

Sep 26 20:43:02.433: INFO: Error updating pvc ebs.csi.aws.comjd2c4: PersistentVolumeClaim "ebs.csi.aws.comjd2c4" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1627-e2e-scxxq7b",
  	... // 3 identical fields
  }

Sep 26 20:43:04.432: INFO: Error updating pvc ebs.csi.aws.comjd2c4: PersistentVolumeClaim "ebs.csi.aws.comjd2c4" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1627-e2e-scxxq7b",
  	... // 3 identical fields
  }

Sep 26 20:43:06.433: INFO: Error updating pvc ebs.csi.aws.comjd2c4: PersistentVolumeClaim "ebs.csi.aws.comjd2c4" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1627-e2e-scxxq7b",
  	... // 3 identical fields
  }

Sep 26 20:43:08.437: INFO: Error updating pvc ebs.csi.aws.comjd2c4: PersistentVolumeClaim "ebs.csi.aws.comjd2c4" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1627-e2e-scxxq7b",
  	... // 3 identical fields
  }

Sep 26 20:43:10.435: INFO: Error updating pvc ebs.csi.aws.comjd2c4: PersistentVolumeClaim "ebs.csi.aws.comjd2c4" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1627-e2e-scxxq7b",
  	... // 3 identical fields
  }

Sep 26 20:43:12.435: INFO: Error updating pvc ebs.csi.aws.comjd2c4: PersistentVolumeClaim "ebs.csi.aws.comjd2c4" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1627-e2e-scxxq7b",
  	... // 3 identical fields
  }

Sep 26 20:43:14.439: INFO: Error updating pvc ebs.csi.aws.comjd2c4: PersistentVolumeClaim "ebs.csi.aws.comjd2c4" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1627-e2e-scxxq7b",
  	... // 3 identical fields
  }

Sep 26 20:43:16.431: INFO: Error updating pvc ebs.csi.aws.comjd2c4: PersistentVolumeClaim "ebs.csi.aws.comjd2c4" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1627-e2e-scxxq7b",
  	... // 3 identical fields
  }

Sep 26 20:43:18.434: INFO: Error updating pvc ebs.csi.aws.comjd2c4: PersistentVolumeClaim "ebs.csi.aws.comjd2c4" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1627-e2e-scxxq7b",
  	... // 3 identical fields
  }

Sep 26 20:43:18.647: INFO: Error updating pvc ebs.csi.aws.comjd2c4: PersistentVolumeClaim "ebs.csi.aws.comjd2c4" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 207 lines ...

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 172 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 26 20:42:09.589: 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.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Sep 26 20:42:10.116: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Sep 26 20:42:10.116: INFO: Creating resource for dynamic PV
Sep 26 20:42:10.116: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9577c4nm
STEP: creating a claim
Sep 26 20:42:10.222: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-xdf9
STEP: Checking for subpath error in container status
Sep 26 20:42:50.754: INFO: Deleting pod "pod-subpath-test-dynamicpv-xdf9" in namespace "provisioning-957"
Sep 26 20:42:50.866: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-xdf9" to be fully deleted
STEP: Deleting pod
Sep 26 20:42:55.077: INFO: Deleting pod "pod-subpath-test-dynamicpv-xdf9" in namespace "provisioning-957"
STEP: Deleting pvc
Sep 26 20:42:55.393: INFO: Deleting PersistentVolumeClaim "awsvxfd7"
... skipping 21 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.GDxjzwo8j/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.GDxjzwo8j/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.GDxjzwo8j/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.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] provisioning
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] provisioning
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 141 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.GDxjzwo8j/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.GDxjzwo8j/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.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 265 lines ...
Sep 26 20:43:20.421: INFO: Waiting for pod aws-client to disappear
Sep 26 20:43:20.527: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Sep 26 20:43:20.527: INFO: Deleting PersistentVolumeClaim "pvc-8rvxj"
Sep 26 20:43:20.634: INFO: Deleting PersistentVolume "aws-bnz5p"
Sep 26 20:43:20.943: INFO: Couldn't delete PD "aws://eu-west-1a/vol-02d0e78c7fc5d97de", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02d0e78c7fc5d97de is currently attached to i-06820b72c8819710e
	status code: 400, request id: 70bba89e-9b5f-4a0d-9b76-97ed185d5a5c
Sep 26 20:43:26.573: INFO: Couldn't delete PD "aws://eu-west-1a/vol-02d0e78c7fc5d97de", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02d0e78c7fc5d97de is currently attached to i-06820b72c8819710e
	status code: 400, request id: ac887043-a99d-4fa6-924c-a8f54affef08
Sep 26 20:43:32.262: INFO: Couldn't delete PD "aws://eu-west-1a/vol-02d0e78c7fc5d97de", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02d0e78c7fc5d97de is currently attached to i-06820b72c8819710e
	status code: 400, request id: 8b79bd61-583d-4859-9768-e2cddd42dad1
Sep 26 20:43:37.876: INFO: Couldn't delete PD "aws://eu-west-1a/vol-02d0e78c7fc5d97de", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02d0e78c7fc5d97de is currently attached to i-06820b72c8819710e
	status code: 400, request id: a76667c7-94b6-4618-8c0b-5b399515697a
Sep 26 20:43:43.459: INFO: Couldn't delete PD "aws://eu-west-1a/vol-02d0e78c7fc5d97de", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02d0e78c7fc5d97de is currently attached to i-06820b72c8819710e
	status code: 400, request id: 288ad426-87af-449b-b8cb-e033d82b2faa
Sep 26 20:43:49.103: INFO: Couldn't delete PD "aws://eu-west-1a/vol-02d0e78c7fc5d97de", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02d0e78c7fc5d97de is currently attached to i-06820b72c8819710e
	status code: 400, request id: ae83d187-e844-4550-94dc-3b2e4c1bdb46
Sep 26 20:43:54.682: INFO: Couldn't delete PD "aws://eu-west-1a/vol-02d0e78c7fc5d97de", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02d0e78c7fc5d97de is currently attached to i-06820b72c8819710e
	status code: 400, request id: 2009aa13-5d48-4117-9cae-735cab71c8bd
Sep 26 20:44:00.356: INFO: Couldn't delete PD "aws://eu-west-1a/vol-02d0e78c7fc5d97de", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02d0e78c7fc5d97de is currently attached to i-06820b72c8819710e
	status code: 400, request id: d6eae11b-a630-467f-a840-6749756d0062
Sep 26 20:44:05.992: INFO: Couldn't delete PD "aws://eu-west-1a/vol-02d0e78c7fc5d97de", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02d0e78c7fc5d97de is currently attached to i-06820b72c8819710e
	status code: 400, request id: 5d12b3b5-243d-461f-9be3-9861b50b0dec
Sep 26 20:44:11.635: INFO: Successfully deleted PD "aws://eu-west-1a/vol-02d0e78c7fc5d97de".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumes
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 26 20:44:11.635: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-9764" for this suite.
... skipping 141 lines ...
Sep 26 20:42:55.690: INFO: PersistentVolumeClaim pvc-wtqrq found but phase is Pending instead of Bound.
Sep 26 20:42:57.796: INFO: PersistentVolumeClaim pvc-wtqrq found and phase=Bound (2.212260245s)
Sep 26 20:42:57.796: INFO: Waiting up to 3m0s for PersistentVolume aws-mv2hf to have phase Bound
Sep 26 20:42:57.901: INFO: PersistentVolume aws-mv2hf found and phase=Bound (105.180304ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-64p8
STEP: Creating a pod to test exec-volume-test
Sep 26 20:42:58.218: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-64p8" in namespace "volume-8571" to be "Succeeded or Failed"
Sep 26 20:42:58.323: INFO: Pod "exec-volume-test-preprovisionedpv-64p8": Phase="Pending", Reason="", readiness=false. Elapsed: 105.143356ms
Sep 26 20:43:00.431: INFO: Pod "exec-volume-test-preprovisionedpv-64p8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.213146388s
Sep 26 20:43:02.538: INFO: Pod "exec-volume-test-preprovisionedpv-64p8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.31933558s
Sep 26 20:43:04.643: INFO: Pod "exec-volume-test-preprovisionedpv-64p8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.424890823s
Sep 26 20:43:06.751: INFO: Pod "exec-volume-test-preprovisionedpv-64p8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.532607492s
Sep 26 20:43:08.859: INFO: Pod "exec-volume-test-preprovisionedpv-64p8": Phase="Pending", Reason="", readiness=false. Elapsed: 10.640734878s
Sep 26 20:43:10.964: INFO: Pod "exec-volume-test-preprovisionedpv-64p8": Phase="Pending", Reason="", readiness=false. Elapsed: 12.746257173s
Sep 26 20:43:13.071: INFO: Pod "exec-volume-test-preprovisionedpv-64p8": Phase="Pending", Reason="", readiness=false. Elapsed: 14.852357397s
Sep 26 20:43:15.179: INFO: Pod "exec-volume-test-preprovisionedpv-64p8": Phase="Pending", Reason="", readiness=false. Elapsed: 16.960812575s
Sep 26 20:43:17.287: INFO: Pod "exec-volume-test-preprovisionedpv-64p8": Phase="Pending", Reason="", readiness=false. Elapsed: 19.069213851s
Sep 26 20:43:19.393: INFO: Pod "exec-volume-test-preprovisionedpv-64p8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.175037648s
STEP: Saw pod success
Sep 26 20:43:19.393: INFO: Pod "exec-volume-test-preprovisionedpv-64p8" satisfied condition "Succeeded or Failed"
Sep 26 20:43:19.501: INFO: Trying to get logs from node ip-172-20-32-24.eu-west-1.compute.internal pod exec-volume-test-preprovisionedpv-64p8 container exec-container-preprovisionedpv-64p8: <nil>
STEP: delete the pod
Sep 26 20:43:20.123: INFO: Waiting for pod exec-volume-test-preprovisionedpv-64p8 to disappear
Sep 26 20:43:20.234: INFO: Pod exec-volume-test-preprovisionedpv-64p8 no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-64p8
Sep 26 20:43:20.234: INFO: Deleting pod "exec-volume-test-preprovisionedpv-64p8" in namespace "volume-8571"
STEP: Deleting pv and pvc
Sep 26 20:43:20.339: INFO: Deleting PersistentVolumeClaim "pvc-wtqrq"
Sep 26 20:43:20.445: INFO: Deleting PersistentVolume "aws-mv2hf"
Sep 26 20:43:20.743: INFO: Couldn't delete PD "aws://eu-west-1a/vol-05ecc227f2c7c75c4", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05ecc227f2c7c75c4 is currently attached to i-0ede337f3f46589a5
	status code: 400, request id: 3e558c52-5303-4328-a23d-9a6a181c9384
Sep 26 20:43:26.411: INFO: Couldn't delete PD "aws://eu-west-1a/vol-05ecc227f2c7c75c4", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05ecc227f2c7c75c4 is currently attached to i-0ede337f3f46589a5
	status code: 400, request id: 31a930bc-c9fb-4c07-933f-99608039c129
Sep 26 20:43:32.107: INFO: Couldn't delete PD "aws://eu-west-1a/vol-05ecc227f2c7c75c4", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05ecc227f2c7c75c4 is currently attached to i-0ede337f3f46589a5
	status code: 400, request id: 9733e67f-a80d-442d-907d-67088a55aaec
Sep 26 20:43:37.675: INFO: Couldn't delete PD "aws://eu-west-1a/vol-05ecc227f2c7c75c4", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05ecc227f2c7c75c4 is currently attached to i-0ede337f3f46589a5
	status code: 400, request id: 231cedad-2855-4653-af1d-8aee6d8cdd5b
Sep 26 20:43:43.259: INFO: Couldn't delete PD "aws://eu-west-1a/vol-05ecc227f2c7c75c4", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05ecc227f2c7c75c4 is currently attached to i-0ede337f3f46589a5
	status code: 400, request id: ed717ff9-9472-422b-897d-11e03f95406a
Sep 26 20:43:48.829: INFO: Couldn't delete PD "aws://eu-west-1a/vol-05ecc227f2c7c75c4", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05ecc227f2c7c75c4 is currently attached to i-0ede337f3f46589a5
	status code: 400, request id: 633a7541-bd3b-4657-82b5-63f60ce455a2
Sep 26 20:43:54.367: INFO: Couldn't delete PD "aws://eu-west-1a/vol-05ecc227f2c7c75c4", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05ecc227f2c7c75c4 is currently attached to i-0ede337f3f46589a5
	status code: 400, request id: 0783a121-be29-4451-bdc9-0608230a9915
Sep 26 20:43:59.947: INFO: Couldn't delete PD "aws://eu-west-1a/vol-05ecc227f2c7c75c4", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05ecc227f2c7c75c4 is currently attached to i-0ede337f3f46589a5
	status code: 400, request id: 060c9739-3a25-4f82-b289-398d9537c21a
Sep 26 20:44:05.515: INFO: Couldn't delete PD "aws://eu-west-1a/vol-05ecc227f2c7c75c4", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05ecc227f2c7c75c4 is currently attached to i-0ede337f3f46589a5
	status code: 400, request id: 51b083b0-52eb-44f6-9964-6f6c4e71aff1
Sep 26 20:44:11.140: INFO: Couldn't delete PD "aws://eu-west-1a/vol-05ecc227f2c7c75c4", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05ecc227f2c7c75c4 is currently attached to i-0ede337f3f46589a5
	status code: 400, request id: 14000052-04e5-408d-a52f-0dab08e48cc4
Sep 26 20:44:16.699: INFO: Successfully deleted PD "aws://eu-west-1a/vol-05ecc227f2c7c75c4".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 26 20:44:16.700: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8571" for this suite.
... skipping 504 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.GDxjzwo8j/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.GDxjzwo8j/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.GDxjzwo8j/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.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 320 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 26 20:43:29.381: 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.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Sep 26 20:43:29.913: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Sep 26 20:43:29.913: INFO: Creating resource for dynamic PV
Sep 26 20:43:29.913: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3079dqfw5
STEP: creating a claim
Sep 26 20:43:30.019: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-xxbb
STEP: Checking for subpath error in container status
Sep 26 20:44:42.561: INFO: Deleting pod "pod-subpath-test-dynamicpv-xxbb" in namespace "provisioning-3079"
Sep 26 20:44:42.670: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-xxbb" to be fully deleted
STEP: Deleting pod
Sep 26 20:44:44.883: INFO: Deleting pod "pod-subpath-test-dynamicpv-xxbb" in namespace "provisioning-3079"
STEP: Deleting pvc
Sep 26 20:44:45.200: INFO: Deleting PersistentVolumeClaim "awshpml6"
... skipping 14 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.GDxjzwo8j/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.GDxjzwo8j/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.GDxjzwo8j/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.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [sig-storage] Zone Support [Feature:vsphere]
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 26 20:45:06.188: INFO: >>> kubeConfig: /root/.kube/config
... skipping 32 lines ...
Sep 26 20:43:20.512: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-2732-e2e-scxbm5s
STEP: creating a claim
Sep 26 20:43:20.623: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-bgw6
STEP: Creating a pod to test exec-volume-test
Sep 26 20:43:20.946: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-bgw6" in namespace "volume-2732" to be "Succeeded or Failed"
Sep 26 20:43:21.052: INFO: Pod "exec-volume-test-dynamicpv-bgw6": Phase="Pending", Reason="", readiness=false. Elapsed: 106.310394ms
Sep 26 20:43:23.161: INFO: Pod "exec-volume-test-dynamicpv-bgw6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.215467132s
Sep 26 20:43:25.268: INFO: Pod "exec-volume-test-dynamicpv-bgw6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.322117204s
Sep 26 20:43:27.376: INFO: Pod "exec-volume-test-dynamicpv-bgw6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.429962119s
Sep 26 20:43:29.483: INFO: Pod "exec-volume-test-dynamicpv-bgw6": Phase="Pending", Reason="", readiness=false. Elapsed: 8.537400893s
Sep 26 20:43:31.591: INFO: Pod "exec-volume-test-dynamicpv-bgw6": Phase="Pending", Reason="", readiness=false. Elapsed: 10.64520986s
... skipping 23 lines ...
Sep 26 20:44:22.181: INFO: Pod "exec-volume-test-dynamicpv-bgw6": Phase="Pending", Reason="", readiness=false. Elapsed: 1m1.235605383s
Sep 26 20:44:24.288: INFO: Pod "exec-volume-test-dynamicpv-bgw6": Phase="Pending", Reason="", readiness=false. Elapsed: 1m3.34239814s
Sep 26 20:44:26.395: INFO: Pod "exec-volume-test-dynamicpv-bgw6": Phase="Pending", Reason="", readiness=false. Elapsed: 1m5.448760326s
Sep 26 20:44:28.502: INFO: Pod "exec-volume-test-dynamicpv-bgw6": Phase="Pending", Reason="", readiness=false. Elapsed: 1m7.556146454s
Sep 26 20:44:30.611: INFO: Pod "exec-volume-test-dynamicpv-bgw6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m9.665138266s
STEP: Saw pod success
Sep 26 20:44:30.611: INFO: Pod "exec-volume-test-dynamicpv-bgw6" satisfied condition "Succeeded or Failed"
Sep 26 20:44:30.718: INFO: Trying to get logs from node ip-172-20-32-228.eu-west-1.compute.internal pod exec-volume-test-dynamicpv-bgw6 container exec-container-dynamicpv-bgw6: <nil>
STEP: delete the pod
Sep 26 20:44:30.949: INFO: Waiting for pod exec-volume-test-dynamicpv-bgw6 to disappear
Sep 26 20:44:31.056: INFO: Pod exec-volume-test-dynamicpv-bgw6 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-bgw6
Sep 26 20:44:31.056: INFO: Deleting pod "exec-volume-test-dynamicpv-bgw6" in namespace "volume-2732"
... skipping 288 lines ...
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 26 20:45:07.687: 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.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Sep 26 20:45:08.326: INFO: found topology map[topology.ebs.csi.aws.com/zone:eu-west-1a]
Sep 26 20:45:08.326: 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.964 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.GDxjzwo8j/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.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

    Not enough topologies in cluster -- skipping

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

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

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

    /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 11 lines ...
Sep 26 20:43:20.635: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3045-e2e-scgzpmc
STEP: creating a claim
Sep 26 20:43:20.744: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-zt8b
STEP: Creating a pod to test subpath
Sep 26 20:43:21.065: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-zt8b" in namespace "provisioning-3045" to be "Succeeded or Failed"
Sep 26 20:43:21.185: INFO: Pod "pod-subpath-test-dynamicpv-zt8b": Phase="Pending", Reason="", readiness=false. Elapsed: 119.135827ms
Sep 26 20:43:23.291: INFO: Pod "pod-subpath-test-dynamicpv-zt8b": Phase="Pending", Reason="", readiness=false. Elapsed: 2.225596819s
Sep 26 20:43:25.397: INFO: Pod "pod-subpath-test-dynamicpv-zt8b": Phase="Pending", Reason="", readiness=false. Elapsed: 4.331880683s
Sep 26 20:43:27.504: INFO: Pod "pod-subpath-test-dynamicpv-zt8b": Phase="Pending", Reason="", readiness=false. Elapsed: 6.438765662s
Sep 26 20:43:29.610: INFO: Pod "pod-subpath-test-dynamicpv-zt8b": Phase="Pending", Reason="", readiness=false. Elapsed: 8.544624339s
Sep 26 20:43:31.717: INFO: Pod "pod-subpath-test-dynamicpv-zt8b": Phase="Pending", Reason="", readiness=false. Elapsed: 10.651650404s
... skipping 27 lines ...
Sep 26 20:44:30.728: INFO: Pod "pod-subpath-test-dynamicpv-zt8b": Phase="Pending", Reason="", readiness=false. Elapsed: 1m9.662827275s
Sep 26 20:44:32.836: INFO: Pod "pod-subpath-test-dynamicpv-zt8b": Phase="Pending", Reason="", readiness=false. Elapsed: 1m11.770255747s
Sep 26 20:44:34.942: INFO: Pod "pod-subpath-test-dynamicpv-zt8b": Phase="Pending", Reason="", readiness=false. Elapsed: 1m13.87665262s
Sep 26 20:44:37.049: INFO: Pod "pod-subpath-test-dynamicpv-zt8b": Phase="Pending", Reason="", readiness=false. Elapsed: 1m15.983270444s
Sep 26 20:44:39.154: INFO: Pod "pod-subpath-test-dynamicpv-zt8b": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m18.089010663s
STEP: Saw pod success
Sep 26 20:44:39.154: INFO: Pod "pod-subpath-test-dynamicpv-zt8b" satisfied condition "Succeeded or Failed"
Sep 26 20:44:39.260: INFO: Trying to get logs from node ip-172-20-32-228.eu-west-1.compute.internal pod pod-subpath-test-dynamicpv-zt8b container test-container-volume-dynamicpv-zt8b: <nil>
STEP: delete the pod
Sep 26 20:44:39.511: INFO: Waiting for pod pod-subpath-test-dynamicpv-zt8b to disappear
Sep 26 20:44:39.617: INFO: Pod pod-subpath-test-dynamicpv-zt8b no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-zt8b
Sep 26 20:44:39.617: INFO: Deleting pod "pod-subpath-test-dynamicpv-zt8b" in namespace "provisioning-3045"
... skipping 498 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.GDxjzwo8j/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.GDxjzwo8j/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.GDxjzwo8j/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.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 222 lines ...
Sep 26 20:43:01.003: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Sep 26 20:43:01.364: INFO: Successfully created a new PD: "aws://eu-west-1a/vol-062c3386692979b38".
Sep 26 20:43:01.365: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-8bfg
STEP: Creating a pod to test exec-volume-test
Sep 26 20:43:01.477: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-8bfg" in namespace "volume-488" to be "Succeeded or Failed"
Sep 26 20:43:01.584: INFO: Pod "exec-volume-test-inlinevolume-8bfg": Phase="Pending", Reason="", readiness=false. Elapsed: 107.291625ms
Sep 26 20:43:03.695: INFO: Pod "exec-volume-test-inlinevolume-8bfg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.218503477s
Sep 26 20:43:05.803: INFO: Pod "exec-volume-test-inlinevolume-8bfg": Phase="Pending", Reason="", readiness=false. Elapsed: 4.32632956s
Sep 26 20:43:07.912: INFO: Pod "exec-volume-test-inlinevolume-8bfg": Phase="Pending", Reason="", readiness=false. Elapsed: 6.435787803s
Sep 26 20:43:10.021: INFO: Pod "exec-volume-test-inlinevolume-8bfg": Phase="Pending", Reason="", readiness=false. Elapsed: 8.543975956s
Sep 26 20:43:12.129: INFO: Pod "exec-volume-test-inlinevolume-8bfg": Phase="Pending", Reason="", readiness=false. Elapsed: 10.652506576s
... skipping 56 lines ...
Sep 26 20:45:12.336: INFO: Pod "exec-volume-test-inlinevolume-8bfg": Phase="Pending", Reason="", readiness=false. Elapsed: 2m10.858914369s
Sep 26 20:45:14.444: INFO: Pod "exec-volume-test-inlinevolume-8bfg": Phase="Pending", Reason="", readiness=false. Elapsed: 2m12.967101619s
Sep 26 20:45:16.552: INFO: Pod "exec-volume-test-inlinevolume-8bfg": Phase="Pending", Reason="", readiness=false. Elapsed: 2m15.074924329s
Sep 26 20:45:18.661: INFO: Pod "exec-volume-test-inlinevolume-8bfg": Phase="Pending", Reason="", readiness=false. Elapsed: 2m17.184605799s
Sep 26 20:45:20.769: INFO: Pod "exec-volume-test-inlinevolume-8bfg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2m19.292155012s
STEP: Saw pod success
Sep 26 20:45:20.769: INFO: Pod "exec-volume-test-inlinevolume-8bfg" satisfied condition "Succeeded or Failed"
Sep 26 20:45:20.876: INFO: Trying to get logs from node ip-172-20-49-137.eu-west-1.compute.internal pod exec-volume-test-inlinevolume-8bfg container exec-container-inlinevolume-8bfg: <nil>
STEP: delete the pod
Sep 26 20:45:21.099: INFO: Waiting for pod exec-volume-test-inlinevolume-8bfg to disappear
Sep 26 20:45:21.206: INFO: Pod exec-volume-test-inlinevolume-8bfg no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-8bfg
Sep 26 20:45:21.206: INFO: Deleting pod "exec-volume-test-inlinevolume-8bfg" in namespace "volume-488"
Sep 26 20:45:21.890: INFO: Couldn't delete PD "aws://eu-west-1a/vol-062c3386692979b38", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-062c3386692979b38 is currently attached to i-03889c28dcccf7b5b
	status code: 400, request id: 74e5f9a6-cd5f-4ce2-ae65-35eff55d5069
Sep 26 20:45:27.457: INFO: Couldn't delete PD "aws://eu-west-1a/vol-062c3386692979b38", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-062c3386692979b38 is currently attached to i-03889c28dcccf7b5b
	status code: 400, request id: bc426b12-0346-4250-8216-9875d8a3a671
Sep 26 20:45:33.108: INFO: Successfully deleted PD "aws://eu-west-1a/vol-062c3386692979b38".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 26 20:45:33.108: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-488" for this suite.
... skipping 360 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.GDxjzwo8j/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.GDxjzwo8j/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.GDxjzwo8j/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.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Distro debian doesn't support ntfs -- skipping

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

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 369 lines ...
STEP: Deleting pod aws-client in namespace volume-4863
Sep 26 20:45:42.871: INFO: Waiting for pod aws-client to disappear
Sep 26 20:45:42.978: INFO: Pod aws-client still exists
Sep 26 20:45:44.978: INFO: Waiting for pod aws-client to disappear
Sep 26 20:45:45.086: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Sep 26 20:45:45.513: INFO: Couldn't delete PD "aws://eu-west-1a/vol-003f4f2f31ff5d23f", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-003f4f2f31ff5d23f is currently attached to i-03040e2b3f955aa52
	status code: 400, request id: cb9c1de8-97c2-4982-a861-4cf7f06f4e34
Sep 26 20:45:51.088: INFO: Couldn't delete PD "aws://eu-west-1a/vol-003f4f2f31ff5d23f", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-003f4f2f31ff5d23f is currently attached to i-03040e2b3f955aa52
	status code: 400, request id: bbf7b060-39ca-44f0-b7c8-bc49644f9945
Sep 26 20:45:56.671: INFO: Couldn't delete PD "aws://eu-west-1a/vol-003f4f2f31ff5d23f", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-003f4f2f31ff5d23f is currently attached to i-03040e2b3f955aa52
	status code: 400, request id: 8e1ad2ce-772e-4de1-b2fa-6ff1d3a54f36
Sep 26 20:46:02.324: INFO: Successfully deleted PD "aws://eu-west-1a/vol-003f4f2f31ff5d23f".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 26 20:46:02.324: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-4863" for this suite.
... skipping 81 lines ...

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

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

    /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 66 lines ...
Sep 26 20:45:09.184: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8129-e2e-sc4s4gv
STEP: creating a claim
Sep 26 20:45:09.292: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-gkdx
STEP: Creating a pod to test subpath
Sep 26 20:45:09.621: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-gkdx" in namespace "provisioning-8129" to be "Succeeded or Failed"
Sep 26 20:45:09.727: INFO: Pod "pod-subpath-test-dynamicpv-gkdx": Phase="Pending", Reason="", readiness=false. Elapsed: 105.464666ms
Sep 26 20:45:11.833: INFO: Pod "pod-subpath-test-dynamicpv-gkdx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.212247713s
Sep 26 20:45:13.940: INFO: Pod "pod-subpath-test-dynamicpv-gkdx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.318996748s
Sep 26 20:45:16.047: INFO: Pod "pod-subpath-test-dynamicpv-gkdx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.425615536s
Sep 26 20:45:18.153: INFO: Pod "pod-subpath-test-dynamicpv-gkdx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.532177088s
Sep 26 20:45:20.261: INFO: Pod "pod-subpath-test-dynamicpv-gkdx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.639459559s
Sep 26 20:45:22.369: INFO: Pod "pod-subpath-test-dynamicpv-gkdx": Phase="Pending", Reason="", readiness=false. Elapsed: 12.747817712s
Sep 26 20:45:24.476: INFO: Pod "pod-subpath-test-dynamicpv-gkdx": Phase="Pending", Reason="", readiness=false. Elapsed: 14.85527505s
Sep 26 20:45:26.583: INFO: Pod "pod-subpath-test-dynamicpv-gkdx": Phase="Pending", Reason="", readiness=false. Elapsed: 16.96202193s
Sep 26 20:45:28.690: INFO: Pod "pod-subpath-test-dynamicpv-gkdx": Phase="Pending", Reason="", readiness=false. Elapsed: 19.069193384s
Sep 26 20:45:30.802: INFO: Pod "pod-subpath-test-dynamicpv-gkdx": Phase="Pending", Reason="", readiness=false. Elapsed: 21.180861945s
Sep 26 20:45:32.912: INFO: Pod "pod-subpath-test-dynamicpv-gkdx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.29094985s
STEP: Saw pod success
Sep 26 20:45:32.912: INFO: Pod "pod-subpath-test-dynamicpv-gkdx" satisfied condition "Succeeded or Failed"
Sep 26 20:45:33.018: INFO: Trying to get logs from node ip-172-20-32-228.eu-west-1.compute.internal pod pod-subpath-test-dynamicpv-gkdx container test-container-subpath-dynamicpv-gkdx: <nil>
STEP: delete the pod
Sep 26 20:45:33.238: INFO: Waiting for pod pod-subpath-test-dynamicpv-gkdx to disappear
Sep 26 20:45:33.344: INFO: Pod pod-subpath-test-dynamicpv-gkdx no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-gkdx
Sep 26 20:45:33.344: INFO: Deleting pod "pod-subpath-test-dynamicpv-gkdx" in namespace "provisioning-8129"
... skipping 40 lines ...
Sep 26 20:45:42.866: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-3759pj6ld
STEP: creating a claim
Sep 26 20:45:42.973: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-2wgj
STEP: Creating a pod to test exec-volume-test
Sep 26 20:45:43.298: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-2wgj" in namespace "volume-3759" to be "Succeeded or Failed"
Sep 26 20:45:43.404: INFO: Pod "exec-volume-test-dynamicpv-2wgj": Phase="Pending", Reason="", readiness=false. Elapsed: 106.32511ms
Sep 26 20:45:45.512: INFO: Pod "exec-volume-test-dynamicpv-2wgj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.213609677s
Sep 26 20:45:47.620: INFO: Pod "exec-volume-test-dynamicpv-2wgj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.32190914s
Sep 26 20:45:49.728: INFO: Pod "exec-volume-test-dynamicpv-2wgj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.429531671s
Sep 26 20:45:51.835: INFO: Pod "exec-volume-test-dynamicpv-2wgj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.536837205s
Sep 26 20:45:53.943: INFO: Pod "exec-volume-test-dynamicpv-2wgj": Phase="Pending", Reason="", readiness=false. Elapsed: 10.645264759s
Sep 26 20:45:56.052: INFO: Pod "exec-volume-test-dynamicpv-2wgj": Phase="Pending", Reason="", readiness=false. Elapsed: 12.753541616s
Sep 26 20:45:58.159: INFO: Pod "exec-volume-test-dynamicpv-2wgj": Phase="Pending", Reason="", readiness=false. Elapsed: 14.86070986s
Sep 26 20:46:00.265: INFO: Pod "exec-volume-test-dynamicpv-2wgj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.967321403s
STEP: Saw pod success
Sep 26 20:46:00.266: INFO: Pod "exec-volume-test-dynamicpv-2wgj" satisfied condition "Succeeded or Failed"
Sep 26 20:46:00.372: INFO: Trying to get logs from node ip-172-20-32-24.eu-west-1.compute.internal pod exec-volume-test-dynamicpv-2wgj container exec-container-dynamicpv-2wgj: <nil>
STEP: delete the pod
Sep 26 20:46:00.600: INFO: Waiting for pod exec-volume-test-dynamicpv-2wgj to disappear
Sep 26 20:46:00.707: INFO: Pod exec-volume-test-dynamicpv-2wgj no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-2wgj
Sep 26 20:46:00.707: INFO: Deleting pod "exec-volume-test-dynamicpv-2wgj" in namespace "volume-3759"
... skipping 303 lines ...

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

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

    /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 194 lines ...
Sep 26 20:45:59.226: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Sep 26 20:46:00.007: INFO: Successfully created a new PD: "aws://eu-west-1a/vol-0aed24f2a6005dd73".
Sep 26 20:46:00.007: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-mm2l
STEP: Creating a pod to test exec-volume-test
Sep 26 20:46:00.117: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-mm2l" in namespace "volume-2242" to be "Succeeded or Failed"
Sep 26 20:46:00.222: INFO: Pod "exec-volume-test-inlinevolume-mm2l": Phase="Pending", Reason="", readiness=false. Elapsed: 104.852262ms
Sep 26 20:46:02.329: INFO: Pod "exec-volume-test-inlinevolume-mm2l": Phase="Pending", Reason="", readiness=false. Elapsed: 2.212233899s
Sep 26 20:46:04.435: INFO: Pod "exec-volume-test-inlinevolume-mm2l": Phase="Pending", Reason="", readiness=false. Elapsed: 4.318167755s
Sep 26 20:46:06.541: INFO: Pod "exec-volume-test-inlinevolume-mm2l": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.424483684s
STEP: Saw pod success
Sep 26 20:46:06.541: INFO: Pod "exec-volume-test-inlinevolume-mm2l" satisfied condition "Succeeded or Failed"
Sep 26 20:46:06.646: INFO: Trying to get logs from node ip-172-20-32-228.eu-west-1.compute.internal pod exec-volume-test-inlinevolume-mm2l container exec-container-inlinevolume-mm2l: <nil>
STEP: delete the pod
Sep 26 20:46:06.873: INFO: Waiting for pod exec-volume-test-inlinevolume-mm2l to disappear
Sep 26 20:46:06.983: INFO: Pod exec-volume-test-inlinevolume-mm2l no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-mm2l
Sep 26 20:46:06.983: INFO: Deleting pod "exec-volume-test-inlinevolume-mm2l" in namespace "volume-2242"
Sep 26 20:46:07.314: INFO: Couldn't delete PD "aws://eu-west-1a/vol-0aed24f2a6005dd73", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0aed24f2a6005dd73 is currently attached to i-06820b72c8819710e
	status code: 400, request id: 02f8a344-80ee-436c-b94a-6e60fd768234
Sep 26 20:46:12.897: INFO: Couldn't delete PD "aws://eu-west-1a/vol-0aed24f2a6005dd73", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0aed24f2a6005dd73 is currently attached to i-06820b72c8819710e
	status code: 400, request id: d05e8d8f-dd1c-4e33-af99-99240e75886c
Sep 26 20:46:18.457: INFO: Couldn't delete PD "aws://eu-west-1a/vol-0aed24f2a6005dd73", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0aed24f2a6005dd73 is currently attached to i-06820b72c8819710e
	status code: 400, request id: d2aba45c-0538-4305-808a-e5bf5498f4ae
Sep 26 20:46:24.160: INFO: Successfully deleted PD "aws://eu-west-1a/vol-0aed24f2a6005dd73".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 26 20:46:24.160: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-2242" for this suite.
... skipping 49 lines ...
Sep 26 20:45:42.082: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-8730hmcn6
STEP: creating a claim
Sep 26 20:45:42.188: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-zltj
STEP: Creating a pod to test exec-volume-test
Sep 26 20:45:42.513: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-zltj" in namespace "volume-8730" to be "Succeeded or Failed"
Sep 26 20:45:42.620: INFO: Pod "exec-volume-test-dynamicpv-zltj": Phase="Pending", Reason="", readiness=false. Elapsed: 106.807869ms
Sep 26 20:45:44.726: INFO: Pod "exec-volume-test-dynamicpv-zltj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.212805549s
Sep 26 20:45:46.835: INFO: Pod "exec-volume-test-dynamicpv-zltj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.321964701s
Sep 26 20:45:48.946: INFO: Pod "exec-volume-test-dynamicpv-zltj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.432265s
Sep 26 20:45:51.052: INFO: Pod "exec-volume-test-dynamicpv-zltj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.538206056s
Sep 26 20:45:53.158: INFO: Pod "exec-volume-test-dynamicpv-zltj": Phase="Pending", Reason="", readiness=false. Elapsed: 10.645034123s
Sep 26 20:45:55.265: INFO: Pod "exec-volume-test-dynamicpv-zltj": Phase="Pending", Reason="", readiness=false. Elapsed: 12.751204666s
Sep 26 20:45:57.372: INFO: Pod "exec-volume-test-dynamicpv-zltj": Phase="Pending", Reason="", readiness=false. Elapsed: 14.858697998s
Sep 26 20:45:59.479: INFO: Pod "exec-volume-test-dynamicpv-zltj": Phase="Pending", Reason="", readiness=false. Elapsed: 16.965205103s
Sep 26 20:46:01.585: INFO: Pod "exec-volume-test-dynamicpv-zltj": Phase="Running", Reason="", readiness=true. Elapsed: 19.071729782s
Sep 26 20:46:03.692: INFO: Pod "exec-volume-test-dynamicpv-zltj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.178794669s
STEP: Saw pod success
Sep 26 20:46:03.692: INFO: Pod "exec-volume-test-dynamicpv-zltj" satisfied condition "Succeeded or Failed"
Sep 26 20:46:03.799: INFO: Trying to get logs from node ip-172-20-49-137.eu-west-1.compute.internal pod exec-volume-test-dynamicpv-zltj container exec-container-dynamicpv-zltj: <nil>
STEP: delete the pod
Sep 26 20:46:04.028: INFO: Waiting for pod exec-volume-test-dynamicpv-zltj to disappear
Sep 26 20:46:04.134: INFO: Pod exec-volume-test-dynamicpv-zltj no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-zltj
Sep 26 20:46:04.134: INFO: Deleting pod "exec-volume-test-dynamicpv-zltj" in namespace "volume-8730"
... skipping 39 lines ...
Sep 26 20:45:40.961: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2079v87hj
STEP: creating a claim
Sep 26 20:45:41.072: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-dw54
STEP: Creating a pod to test subpath
Sep 26 20:45:41.396: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-dw54" in namespace "provisioning-2079" to be "Succeeded or Failed"
Sep 26 20:45:41.503: INFO: Pod "pod-subpath-test-dynamicpv-dw54": Phase="Pending", Reason="", readiness=false. Elapsed: 106.08944ms
Sep 26 20:45:43.609: INFO: Pod "pod-subpath-test-dynamicpv-dw54": Phase="Pending", Reason="", readiness=false. Elapsed: 2.212764518s
Sep 26 20:45:45.718: INFO: Pod "pod-subpath-test-dynamicpv-dw54": Phase="Pending", Reason="", readiness=false. Elapsed: 4.321652458s
Sep 26 20:45:47.825: INFO: Pod "pod-subpath-test-dynamicpv-dw54": Phase="Pending", Reason="", readiness=false. Elapsed: 6.428636247s
Sep 26 20:45:49.932: INFO: Pod "pod-subpath-test-dynamicpv-dw54": Phase="Pending", Reason="", readiness=false. Elapsed: 8.53505331s
Sep 26 20:45:52.038: INFO: Pod "pod-subpath-test-dynamicpv-dw54": Phase="Pending", Reason="", readiness=false. Elapsed: 10.641780438s
... skipping 2 lines ...
Sep 26 20:45:58.359: INFO: Pod "pod-subpath-test-dynamicpv-dw54": Phase="Pending", Reason="", readiness=false. Elapsed: 16.962561936s
Sep 26 20:46:00.467: INFO: Pod "pod-subpath-test-dynamicpv-dw54": Phase="Pending", Reason="", readiness=false. Elapsed: 19.070100207s
Sep 26 20:46:02.573: INFO: Pod "pod-subpath-test-dynamicpv-dw54": Phase="Pending", Reason="", readiness=false. Elapsed: 21.176705377s
Sep 26 20:46:04.703: INFO: Pod "pod-subpath-test-dynamicpv-dw54": Phase="Pending", Reason="", readiness=false. Elapsed: 23.306187059s
Sep 26 20:46:06.814: INFO: Pod "pod-subpath-test-dynamicpv-dw54": Phase="Succeeded", Reason="", readiness=false. Elapsed: 25.41790728s
STEP: Saw pod success
Sep 26 20:46:06.814: INFO: Pod "pod-subpath-test-dynamicpv-dw54" satisfied condition "Succeeded or Failed"
Sep 26 20:46:06.928: INFO: Trying to get logs from node ip-172-20-39-136.eu-west-1.compute.internal pod pod-subpath-test-dynamicpv-dw54 container test-container-subpath-dynamicpv-dw54: <nil>
STEP: delete the pod
Sep 26 20:46:07.159: INFO: Waiting for pod pod-subpath-test-dynamicpv-dw54 to disappear
Sep 26 20:46:07.265: INFO: Pod pod-subpath-test-dynamicpv-dw54 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-dw54
Sep 26 20:46:07.265: INFO: Deleting pod "pod-subpath-test-dynamicpv-dw54" in namespace "provisioning-2079"
... skipping 253 lines ...
STEP: Deleting pod hostexec-ip-172-20-32-228.eu-west-1.compute.internal-v27qr in namespace volumemode-4377
Sep 26 20:46:36.805: INFO: Deleting pod "pod-935a4997-c607-419a-9098-cb4c638dd0e2" in namespace "volumemode-4377"
Sep 26 20:46:36.913: INFO: Wait up to 5m0s for pod "pod-935a4997-c607-419a-9098-cb4c638dd0e2" to be fully deleted
STEP: Deleting pv and pvc
Sep 26 20:46:41.126: INFO: Deleting PersistentVolumeClaim "pvc-84zjw"
Sep 26 20:46:41.232: INFO: Deleting PersistentVolume "aws-6dvsc"
Sep 26 20:46:41.577: INFO: Couldn't delete PD "aws://eu-west-1a/vol-07e399255364a24a6", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07e399255364a24a6 is currently attached to i-06820b72c8819710e
	status code: 400, request id: d2d208f6-49d1-41f7-98ee-e8967fdc5ff7
Sep 26 20:46:47.183: INFO: Successfully deleted PD "aws://eu-west-1a/vol-07e399255364a24a6".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 26 20:46:47.183: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-4377" for this suite.
... skipping 45 lines ...
Sep 26 20:46:03.086: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2966w6kj7
STEP: creating a claim
Sep 26 20:46:03.193: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-xps4
STEP: Creating a pod to test subpath
Sep 26 20:46:03.516: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-xps4" in namespace "provisioning-2966" to be "Succeeded or Failed"
Sep 26 20:46:03.623: INFO: Pod "pod-subpath-test-dynamicpv-xps4": Phase="Pending", Reason="", readiness=false. Elapsed: 106.784434ms
Sep 26 20:46:05.731: INFO: Pod "pod-subpath-test-dynamicpv-xps4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.214223312s
Sep 26 20:46:07.855: INFO: Pod "pod-subpath-test-dynamicpv-xps4": Phase="Pending", Reason="", readiness=false. Elapsed: 4.338841944s
Sep 26 20:46:09.962: INFO: Pod "pod-subpath-test-dynamicpv-xps4": Phase="Pending", Reason="", readiness=false. Elapsed: 6.445597655s
Sep 26 20:46:12.070: INFO: Pod "pod-subpath-test-dynamicpv-xps4": Phase="Pending", Reason="", readiness=false. Elapsed: 8.55328975s
Sep 26 20:46:14.178: INFO: Pod "pod-subpath-test-dynamicpv-xps4": Phase="Pending", Reason="", readiness=false. Elapsed: 10.661083574s
Sep 26 20:46:16.286: INFO: Pod "pod-subpath-test-dynamicpv-xps4": Phase="Pending", Reason="", readiness=false. Elapsed: 12.769642206s
Sep 26 20:46:18.393: INFO: Pod "pod-subpath-test-dynamicpv-xps4": Phase="Pending", Reason="", readiness=false. Elapsed: 14.876397605s
Sep 26 20:46:20.500: INFO: Pod "pod-subpath-test-dynamicpv-xps4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.983274056s
STEP: Saw pod success
Sep 26 20:46:20.500: INFO: Pod "pod-subpath-test-dynamicpv-xps4" satisfied condition "Succeeded or Failed"
Sep 26 20:46:20.606: INFO: Trying to get logs from node ip-172-20-49-137.eu-west-1.compute.internal pod pod-subpath-test-dynamicpv-xps4 container test-container-subpath-dynamicpv-xps4: <nil>
STEP: delete the pod
Sep 26 20:46:20.836: INFO: Waiting for pod pod-subpath-test-dynamicpv-xps4 to disappear
Sep 26 20:46:20.942: INFO: Pod pod-subpath-test-dynamicpv-xps4 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-xps4
Sep 26 20:46:20.942: INFO: Deleting pod "pod-subpath-test-dynamicpv-xps4" in namespace "provisioning-2966"
... skipping 57 lines ...
Sep 26 20:45:28.846: INFO: Creating resource for dynamic PV
Sep 26 20:45:28.846: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4667-e2e-scwv8t9
STEP: creating a claim
Sep 26 20:45:28.954: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-4667
Sep 26 20:45:29.279: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-4667" in namespace "provisioning-4667" to be "Succeeded or Failed"
Sep 26 20:45:29.387: INFO: Pod "volume-prep-provisioning-4667": Phase="Pending", Reason="", readiness=false. Elapsed: 107.267989ms
Sep 26 20:45:31.495: INFO: Pod "volume-prep-provisioning-4667": Phase="Pending", Reason="", readiness=false. Elapsed: 2.215207986s
Sep 26 20:45:33.603: INFO: Pod "volume-prep-provisioning-4667": Phase="Pending", Reason="", readiness=false. Elapsed: 4.323792546s
Sep 26 20:45:35.712: INFO: Pod "volume-prep-provisioning-4667": Phase="Pending", Reason="", readiness=false. Elapsed: 6.432635904s
Sep 26 20:45:37.822: INFO: Pod "volume-prep-provisioning-4667": Phase="Pending", Reason="", readiness=false. Elapsed: 8.542306172s
Sep 26 20:45:39.930: INFO: Pod "volume-prep-provisioning-4667": Phase="Pending", Reason="", readiness=false. Elapsed: 10.650860817s
Sep 26 20:45:42.038: INFO: Pod "volume-prep-provisioning-4667": Phase="Pending", Reason="", readiness=false. Elapsed: 12.758618542s
Sep 26 20:45:44.149: INFO: Pod "volume-prep-provisioning-4667": Phase="Pending", Reason="", readiness=false. Elapsed: 14.869260656s
Sep 26 20:45:46.257: INFO: Pod "volume-prep-provisioning-4667": Phase="Pending", Reason="", readiness=false. Elapsed: 16.977187308s
Sep 26 20:45:48.366: INFO: Pod "volume-prep-provisioning-4667": Phase="Pending", Reason="", readiness=false. Elapsed: 19.08615152s
Sep 26 20:45:50.477: INFO: Pod "volume-prep-provisioning-4667": Phase="Pending", Reason="", readiness=false. Elapsed: 21.197016238s
Sep 26 20:45:52.585: INFO: Pod "volume-prep-provisioning-4667": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.305856559s
STEP: Saw pod success
Sep 26 20:45:52.585: INFO: Pod "volume-prep-provisioning-4667" satisfied condition "Succeeded or Failed"
Sep 26 20:45:52.585: INFO: Deleting pod "volume-prep-provisioning-4667" in namespace "provisioning-4667"
Sep 26 20:45:52.704: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-4667" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-fvdc
STEP: Checking for subpath error in container status
Sep 26 20:46:11.138: INFO: Deleting pod "pod-subpath-test-dynamicpv-fvdc" in namespace "provisioning-4667"
Sep 26 20:46:11.251: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-fvdc" to be fully deleted
STEP: Deleting pod
Sep 26 20:46:11.358: INFO: Deleting pod "pod-subpath-test-dynamicpv-fvdc" in namespace "provisioning-4667"
STEP: Deleting pvc
Sep 26 20:46:11.680: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comht9wp"
... skipping 539 lines ...
Sep 26 20:46:23.974: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-9657l8b7w
STEP: creating a claim
Sep 26 20:46:24.081: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-ssx6
STEP: Creating a pod to test exec-volume-test
Sep 26 20:46:24.409: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-ssx6" in namespace "volume-9657" to be "Succeeded or Failed"
Sep 26 20:46:24.516: INFO: Pod "exec-volume-test-dynamicpv-ssx6": Phase="Pending", Reason="", readiness=false. Elapsed: 106.874183ms
Sep 26 20:46:26.623: INFO: Pod "exec-volume-test-dynamicpv-ssx6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.213954942s
Sep 26 20:46:28.731: INFO: Pod "exec-volume-test-dynamicpv-ssx6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.321837618s
Sep 26 20:46:30.840: INFO: Pod "exec-volume-test-dynamicpv-ssx6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.431418633s
Sep 26 20:46:32.948: INFO: Pod "exec-volume-test-dynamicpv-ssx6": Phase="Pending", Reason="", readiness=false. Elapsed: 8.538587753s
Sep 26 20:46:35.055: INFO: Pod "exec-volume-test-dynamicpv-ssx6": Phase="Pending", Reason="", readiness=false. Elapsed: 10.645611954s
Sep 26 20:46:37.163: INFO: Pod "exec-volume-test-dynamicpv-ssx6": Phase="Pending", Reason="", readiness=false. Elapsed: 12.753650612s
Sep 26 20:46:39.271: INFO: Pod "exec-volume-test-dynamicpv-ssx6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.862233892s
STEP: Saw pod success
Sep 26 20:46:39.271: INFO: Pod "exec-volume-test-dynamicpv-ssx6" satisfied condition "Succeeded or Failed"
Sep 26 20:46:39.380: INFO: Trying to get logs from node ip-172-20-49-137.eu-west-1.compute.internal pod exec-volume-test-dynamicpv-ssx6 container exec-container-dynamicpv-ssx6: <nil>
STEP: delete the pod
Sep 26 20:46:39.601: INFO: Waiting for pod exec-volume-test-dynamicpv-ssx6 to disappear
Sep 26 20:46:39.707: INFO: Pod exec-volume-test-dynamicpv-ssx6 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-ssx6
Sep 26 20:46:39.708: INFO: Deleting pod "exec-volume-test-dynamicpv-ssx6" in namespace "volume-9657"
... skipping 32 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.GDxjzwo8j/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.GDxjzwo8j/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.GDxjzwo8j/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.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 124 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 26 20:46:10.088: 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.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Sep 26 20:46:10.627: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Sep 26 20:46:10.627: INFO: Creating resource for dynamic PV
Sep 26 20:46:10.627: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-14277x58v
STEP: creating a claim
Sep 26 20:46:10.733: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-tw7m
STEP: Checking for subpath error in container status
Sep 26 20:46:35.273: INFO: Deleting pod "pod-subpath-test-dynamicpv-tw7m" in namespace "provisioning-1427"
Sep 26 20:46:35.382: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-tw7m" to be fully deleted
STEP: Deleting pod
Sep 26 20:46:37.595: INFO: Deleting pod "pod-subpath-test-dynamicpv-tw7m" in namespace "provisioning-1427"
STEP: Deleting pvc
Sep 26 20:46:37.912: INFO: Deleting PersistentVolumeClaim "awsw6zf9"
... skipping 14 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.GDxjzwo8j/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.GDxjzwo8j/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath file is outside the volume [Slow][LinuxOnly]
      /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 63 lines ...
Sep 26 20:46:47.749: INFO: Waiting for pod aws-client to disappear
Sep 26 20:46:47.855: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Sep 26 20:46:47.855: INFO: Deleting PersistentVolumeClaim "pvc-9fx49"
Sep 26 20:46:47.960: INFO: Deleting PersistentVolume "aws-25qhl"
Sep 26 20:46:48.717: INFO: Couldn't delete PD "aws://eu-west-1a/vol-06dbd14d0b72a2b8b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-06dbd14d0b72a2b8b is currently attached to i-06820b72c8819710e
	status code: 400, request id: 1302025d-2060-48f8-8ebf-241e3a969b72
Sep 26 20:46:54.306: INFO: Couldn't delete PD "aws://eu-west-1a/vol-06dbd14d0b72a2b8b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-06dbd14d0b72a2b8b is currently attached to i-06820b72c8819710e
	status code: 400, request id: 1f8e104a-862c-4893-bd87-966516275fac
Sep 26 20:46:59.936: INFO: Successfully deleted PD "aws://eu-west-1a/vol-06dbd14d0b72a2b8b".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 26 20:46:59.936: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-847" for this suite.
... skipping 377 lines ...
Sep 26 20:46:29.267: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2395-e2e-scvtv96
STEP: creating a claim
Sep 26 20:46:29.374: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-vj9t
STEP: Creating a pod to test atomic-volume-subpath
Sep 26 20:46:29.698: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-vj9t" in namespace "provisioning-2395" to be "Succeeded or Failed"
Sep 26 20:46:29.809: INFO: Pod "pod-subpath-test-dynamicpv-vj9t": Phase="Pending", Reason="", readiness=false. Elapsed: 111.147653ms
Sep 26 20:46:31.916: INFO: Pod "pod-subpath-test-dynamicpv-vj9t": Phase="Pending", Reason="", readiness=false. Elapsed: 2.21754461s
Sep 26 20:46:34.023: INFO: Pod "pod-subpath-test-dynamicpv-vj9t": Phase="Pending", Reason="", readiness=false. Elapsed: 4.324542886s
Sep 26 20:46:36.129: INFO: Pod "pod-subpath-test-dynamicpv-vj9t": Phase="Pending", Reason="", readiness=false. Elapsed: 6.431026683s
Sep 26 20:46:38.237: INFO: Pod "pod-subpath-test-dynamicpv-vj9t": Phase="Pending", Reason="", readiness=false. Elapsed: 8.539039635s
Sep 26 20:46:40.344: INFO: Pod "pod-subpath-test-dynamicpv-vj9t": Phase="Running", Reason="", readiness=true. Elapsed: 10.645418496s
... skipping 5 lines ...
Sep 26 20:46:52.996: INFO: Pod "pod-subpath-test-dynamicpv-vj9t": Phase="Running", Reason="", readiness=true. Elapsed: 23.298336011s
Sep 26 20:46:55.104: INFO: Pod "pod-subpath-test-dynamicpv-vj9t": Phase="Running", Reason="", readiness=true. Elapsed: 25.405857287s
Sep 26 20:46:57.214: INFO: Pod "pod-subpath-test-dynamicpv-vj9t": Phase="Running", Reason="", readiness=true. Elapsed: 27.515779239s
Sep 26 20:46:59.321: INFO: Pod "pod-subpath-test-dynamicpv-vj9t": Phase="Running", Reason="", readiness=true. Elapsed: 29.62323651s
Sep 26 20:47:01.429: INFO: Pod "pod-subpath-test-dynamicpv-vj9t": Phase="Succeeded", Reason="", readiness=false. Elapsed: 31.731141016s
STEP: Saw pod success
Sep 26 20:47:01.429: INFO: Pod "pod-subpath-test-dynamicpv-vj9t" satisfied condition "Succeeded or Failed"
Sep 26 20:47:01.537: INFO: Trying to get logs from node ip-172-20-39-136.eu-west-1.compute.internal pod pod-subpath-test-dynamicpv-vj9t container test-container-subpath-dynamicpv-vj9t: <nil>
STEP: delete the pod
Sep 26 20:47:01.835: INFO: Waiting for pod pod-subpath-test-dynamicpv-vj9t to disappear
Sep 26 20:47:01.942: INFO: Pod pod-subpath-test-dynamicpv-vj9t no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-vj9t
Sep 26 20:47:01.942: INFO: Deleting pod "pod-subpath-test-dynamicpv-vj9t" in namespace "provisioning-2395"
... skipping 69 lines ...
Sep 26 20:46:39.928: INFO: PersistentVolumeClaim pvc-lnbj6 found but phase is Pending instead of Bound.
Sep 26 20:46:42.034: INFO: PersistentVolumeClaim pvc-lnbj6 found and phase=Bound (6.423404553s)
Sep 26 20:46:42.034: INFO: Waiting up to 3m0s for PersistentVolume aws-rrrs5 to have phase Bound
Sep 26 20:46:42.142: INFO: PersistentVolume aws-rrrs5 found and phase=Bound (107.751585ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-qkgx
STEP: Creating a pod to test exec-volume-test
Sep 26 20:46:42.471: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-qkgx" in namespace "volume-5757" to be "Succeeded or Failed"
Sep 26 20:46:42.577: INFO: Pod "exec-volume-test-preprovisionedpv-qkgx": Phase="Pending", Reason="", readiness=false. Elapsed: 105.992363ms
Sep 26 20:46:44.684: INFO: Pod "exec-volume-test-preprovisionedpv-qkgx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.213084021s
Sep 26 20:46:46.792: INFO: Pod "exec-volume-test-preprovisionedpv-qkgx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.320979803s
Sep 26 20:46:48.901: INFO: Pod "exec-volume-test-preprovisionedpv-qkgx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.430073919s
Sep 26 20:46:51.007: INFO: Pod "exec-volume-test-preprovisionedpv-qkgx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.536340519s
Sep 26 20:46:53.121: INFO: Pod "exec-volume-test-preprovisionedpv-qkgx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.650807481s
Sep 26 20:46:55.232: INFO: Pod "exec-volume-test-preprovisionedpv-qkgx": Phase="Pending", Reason="", readiness=false. Elapsed: 12.760891687s
Sep 26 20:46:57.338: INFO: Pod "exec-volume-test-preprovisionedpv-qkgx": Phase="Pending", Reason="", readiness=false. Elapsed: 14.866869918s
Sep 26 20:46:59.444: INFO: Pod "exec-volume-test-preprovisionedpv-qkgx": Phase="Pending", Reason="", readiness=false. Elapsed: 16.97370348s
Sep 26 20:47:01.551: INFO: Pod "exec-volume-test-preprovisionedpv-qkgx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.080036173s
STEP: Saw pod success
Sep 26 20:47:01.551: INFO: Pod "exec-volume-test-preprovisionedpv-qkgx" satisfied condition "Succeeded or Failed"
Sep 26 20:47:01.657: INFO: Trying to get logs from node ip-172-20-32-228.eu-west-1.compute.internal pod exec-volume-test-preprovisionedpv-qkgx container exec-container-preprovisionedpv-qkgx: <nil>
STEP: delete the pod
Sep 26 20:47:01.928: INFO: Waiting for pod exec-volume-test-preprovisionedpv-qkgx to disappear
Sep 26 20:47:02.035: INFO: Pod exec-volume-test-preprovisionedpv-qkgx no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-qkgx
Sep 26 20:47:02.035: INFO: Deleting pod "exec-volume-test-preprovisionedpv-qkgx" in namespace "volume-5757"
STEP: Deleting pv and pvc
Sep 26 20:47:02.151: INFO: Deleting PersistentVolumeClaim "pvc-lnbj6"
Sep 26 20:47:02.268: INFO: Deleting PersistentVolume "aws-rrrs5"
Sep 26 20:47:02.621: INFO: Couldn't delete PD "aws://eu-west-1a/vol-06b12e92e85c2cf5d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-06b12e92e85c2cf5d is currently attached to i-06820b72c8819710e
	status code: 400, request id: bfc17aa9-db11-4c10-9db7-1adf68f8e35f
Sep 26 20:47:08.353: INFO: Couldn't delete PD "aws://eu-west-1a/vol-06b12e92e85c2cf5d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-06b12e92e85c2cf5d is currently attached to i-06820b72c8819710e
	status code: 400, request id: 0cc9ee40-2cbe-40ea-8705-5cb764e885a9
Sep 26 20:47:14.058: INFO: Couldn't delete PD "aws://eu-west-1a/vol-06b12e92e85c2cf5d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-06b12e92e85c2cf5d is currently attached to i-06820b72c8819710e
	status code: 400, request id: 2a8a6f28-7c8c-43bf-be7e-2e43ff461be6
Sep 26 20:47:19.747: INFO: Successfully deleted PD "aws://eu-west-1a/vol-06b12e92e85c2cf5d".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 26 20:47:19.747: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-5757" for this suite.
... skipping 14 lines ...
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 26 20:47:19.033: 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.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Sep 26 20:47:19.680: INFO: found topology map[topology.ebs.csi.aws.com/zone:eu-west-1a]
Sep 26 20:47:19.680: 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.972 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.GDxjzwo8j/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.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

    Not enough topologies in cluster -- skipping

    /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 2 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 26 20:46:24.375: 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.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Sep 26 20:46:24.906: INFO: Creating resource for dynamic PV
Sep 26 20:46:24.906: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3555-e2e-scl7gbr
STEP: creating a claim
Sep 26 20:46:25.013: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-p72k
STEP: Checking for subpath error in container status
Sep 26 20:46:41.546: INFO: Deleting pod "pod-subpath-test-dynamicpv-p72k" in namespace "provisioning-3555"
Sep 26 20:46:41.652: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-p72k" to be fully deleted
STEP: Deleting pod
Sep 26 20:46:43.862: INFO: Deleting pod "pod-subpath-test-dynamicpv-p72k" in namespace "provisioning-3555"
STEP: Deleting pvc
Sep 26 20:46:44.177: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comzv27x"
... skipping 15 lines ...

• [SLOW TEST:56.076 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.GDxjzwo8j/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.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [sig-storage] Volume Disk Format [Feature:vsphere]
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 26 20:47:19.962: INFO: >>> kubeConfig: /root/.kube/config
... skipping 23 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 26 20:46:50.294: 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.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Sep 26 20:46:50.831: INFO: Creating resource for dynamic PV
Sep 26 20:46:50.831: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1357-e2e-sc5svx8
STEP: creating a claim
Sep 26 20:46:50.940: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-dc6c
STEP: Checking for subpath error in container status
Sep 26 20:47:09.482: INFO: Deleting pod "pod-subpath-test-dynamicpv-dc6c" in namespace "provisioning-1357"
Sep 26 20:47:09.591: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-dc6c" to be fully deleted
STEP: Deleting pod
Sep 26 20:47:11.809: INFO: Deleting pod "pod-subpath-test-dynamicpv-dc6c" in namespace "provisioning-1357"
STEP: Deleting pvc
Sep 26 20:47:12.132: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comqdtjp"
... skipping 11 lines ...

• [SLOW TEST:37.715 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath directory is outside the volume [Slow][LinuxOnly]
    /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] provisioning
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
... skipping 11 lines ...
Sep 26 20:46:12.320: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-5878qsqv4      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-5878    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-5878qsqv4,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-5878    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-5878qsqv4,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-5878    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-5878qsqv4,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-5878qsqv4    862ee5a4-1074-4ec7-9d09-3746e230a7bb 10319 0 2021-09-26 20:46:12 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-09-26 20:46:12 +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-rbbpn pvc- provisioning-5878  763c71ec-b00c-4096-92a0-b29adeb8b836 10324 0 2021-09-26 20:46:12 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-09-26 20:46:12 +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-5878qsqv4,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-2f82a1bb-a8fb-45f6-9fc2-57072b2c8b30 in namespace provisioning-5878
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Sep 26 20:46:27.496: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-m6h5m" in namespace "provisioning-5878" to be "Succeeded or Failed"
Sep 26 20:46:27.605: INFO: Pod "pvc-volume-tester-writer-m6h5m": Phase="Pending", Reason="", readiness=false. Elapsed: 109.407288ms
Sep 26 20:46:29.715: INFO: Pod "pvc-volume-tester-writer-m6h5m": Phase="Pending", Reason="", readiness=false. Elapsed: 2.219739171s
Sep 26 20:46:31.823: INFO: Pod "pvc-volume-tester-writer-m6h5m": Phase="Pending", Reason="", readiness=false. Elapsed: 4.327034917s
Sep 26 20:46:33.930: INFO: Pod "pvc-volume-tester-writer-m6h5m": Phase="Pending", Reason="", readiness=false. Elapsed: 6.434292289s
Sep 26 20:46:36.038: INFO: Pod "pvc-volume-tester-writer-m6h5m": Phase="Pending", Reason="", readiness=false. Elapsed: 8.542018455s
Sep 26 20:46:38.145: INFO: Pod "pvc-volume-tester-writer-m6h5m": Phase="Pending", Reason="", readiness=false. Elapsed: 10.648872572s
... skipping 6 lines ...
Sep 26 20:46:52.916: INFO: Pod "pvc-volume-tester-writer-m6h5m": Phase="Pending", Reason="", readiness=false. Elapsed: 25.420334328s
Sep 26 20:46:55.023: INFO: Pod "pvc-volume-tester-writer-m6h5m": Phase="Pending", Reason="", readiness=false. Elapsed: 27.52728589s
Sep 26 20:46:57.130: INFO: Pod "pvc-volume-tester-writer-m6h5m": Phase="Pending", Reason="", readiness=false. Elapsed: 29.633923826s
Sep 26 20:46:59.237: INFO: Pod "pvc-volume-tester-writer-m6h5m": Phase="Pending", Reason="", readiness=false. Elapsed: 31.740889945s
Sep 26 20:47:01.345: INFO: Pod "pvc-volume-tester-writer-m6h5m": Phase="Succeeded", Reason="", readiness=false. Elapsed: 33.84938594s
STEP: Saw pod success
Sep 26 20:47:01.345: INFO: Pod "pvc-volume-tester-writer-m6h5m" satisfied condition "Succeeded or Failed"
Sep 26 20:47:01.577: INFO: Pod pvc-volume-tester-writer-m6h5m has the following logs: 
Sep 26 20:47:01.577: INFO: Deleting pod "pvc-volume-tester-writer-m6h5m" in namespace "provisioning-5878"
Sep 26 20:47:01.688: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-m6h5m" 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-49-137.eu-west-1.compute.internal"
Sep 26 20:47:02.132: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-pkzlm" in namespace "provisioning-5878" to be "Succeeded or Failed"
Sep 26 20:47:02.239: INFO: Pod "pvc-volume-tester-reader-pkzlm": Phase="Pending", Reason="", readiness=false. Elapsed: 106.817493ms
Sep 26 20:47:04.347: INFO: Pod "pvc-volume-tester-reader-pkzlm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.214527818s
Sep 26 20:47:06.454: INFO: Pod "pvc-volume-tester-reader-pkzlm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.321419941s
STEP: Saw pod success
Sep 26 20:47:06.454: INFO: Pod "pvc-volume-tester-reader-pkzlm" satisfied condition "Succeeded or Failed"
Sep 26 20:47:06.668: INFO: Pod pvc-volume-tester-reader-pkzlm has the following logs: hello world

Sep 26 20:47:06.669: INFO: Deleting pod "pvc-volume-tester-reader-pkzlm" in namespace "provisioning-5878"
Sep 26 20:47:06.782: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-pkzlm" to be fully deleted
Sep 26 20:47:06.888: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-rbbpn] to have phase Bound
Sep 26 20:47:06.994: INFO: PersistentVolumeClaim pvc-rbbpn found and phase=Bound (106.207243ms)
... skipping 34 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.GDxjzwo8j/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.GDxjzwo8j/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.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 86 lines ...
Sep 26 20:46:57.982: INFO: Creating resource for dynamic PV
Sep 26 20:46:57.982: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-1092jjhrx
STEP: creating a claim
STEP: Expanding non-expandable pvc
Sep 26 20:46:58.307: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Sep 26 20:46:58.523: INFO: Error updating pvc awsz8swx: PersistentVolumeClaim "awsz8swx" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1092jjhrx",
  	... // 3 identical fields
  }

Sep 26 20:47:00.738: INFO: Error updating pvc awsz8swx: PersistentVolumeClaim "awsz8swx" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1092jjhrx",
  	... // 3 identical fields
  }

Sep 26 20:47:02.738: INFO: Error updating pvc awsz8swx: PersistentVolumeClaim "awsz8swx" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1092jjhrx",
  	... // 3 identical fields
  }

Sep 26 20:47:04.738: INFO: Error updating pvc awsz8swx: PersistentVolumeClaim "awsz8swx" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1092jjhrx",
  	... // 3 identical fields
  }

Sep 26 20:47:06.738: INFO: Error updating pvc awsz8swx: PersistentVolumeClaim "awsz8swx" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1092jjhrx",
  	... // 3 identical fields
  }

Sep 26 20:47:08.740: INFO: Error updating pvc awsz8swx: PersistentVolumeClaim "awsz8swx" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1092jjhrx",
  	... // 3 identical fields
  }

Sep 26 20:47:10.738: INFO: Error updating pvc awsz8swx: PersistentVolumeClaim "awsz8swx" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1092jjhrx",
  	... // 3 identical fields
  }

Sep 26 20:47:12.739: INFO: Error updating pvc awsz8swx: PersistentVolumeClaim "awsz8swx" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1092jjhrx",
  	... // 3 identical fields
  }

Sep 26 20:47:14.738: INFO: Error updating pvc awsz8swx: PersistentVolumeClaim "awsz8swx" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1092jjhrx",
  	... // 3 identical fields
  }

Sep 26 20:47:16.738: INFO: Error updating pvc awsz8swx: PersistentVolumeClaim "awsz8swx" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1092jjhrx",
  	... // 3 identical fields
  }

Sep 26 20:47:18.739: INFO: Error updating pvc awsz8swx: PersistentVolumeClaim "awsz8swx" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1092jjhrx",
  	... // 3 identical fields
  }

Sep 26 20:47:20.739: INFO: Error updating pvc awsz8swx: PersistentVolumeClaim "awsz8swx" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1092jjhrx",
  	... // 3 identical fields
  }

Sep 26 20:47:22.738: INFO: Error updating pvc awsz8swx: PersistentVolumeClaim "awsz8swx" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1092jjhrx",
  	... // 3 identical fields
  }

Sep 26 20:47:24.738: INFO: Error updating pvc awsz8swx: PersistentVolumeClaim "awsz8swx" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1092jjhrx",
  	... // 3 identical fields
  }

Sep 26 20:47:26.738: INFO: Error updating pvc awsz8swx: PersistentVolumeClaim "awsz8swx" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1092jjhrx",
  	... // 3 identical fields
  }

Sep 26 20:47:28.739: INFO: Error updating pvc awsz8swx: PersistentVolumeClaim "awsz8swx" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1092jjhrx",
  	... // 3 identical fields
  }

Sep 26 20:47:28.953: INFO: Error updating pvc awsz8swx: PersistentVolumeClaim "awsz8swx" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 400 lines ...
Sep 26 20:47:20.560: INFO: Creating resource for dynamic PV
Sep 26 20:47:20.560: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-1093-e2e-sc9qxrn
STEP: creating a claim
STEP: Expanding non-expandable pvc
Sep 26 20:47:20.885: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Sep 26 20:47:21.101: INFO: Error updating pvc ebs.csi.aws.combkxz2: PersistentVolumeClaim "ebs.csi.aws.combkxz2" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1093-e2e-sc9qxrn",
  	... // 3 identical fields
  }

Sep 26 20:47:23.322: INFO: Error updating pvc ebs.csi.aws.combkxz2: PersistentVolumeClaim "ebs.csi.aws.combkxz2" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1093-e2e-sc9qxrn",
  	... // 3 identical fields
  }

Sep 26 20:47:25.319: INFO: Error updating pvc ebs.csi.aws.combkxz2: PersistentVolumeClaim "ebs.csi.aws.combkxz2" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1093-e2e-sc9qxrn",
  	... // 3 identical fields
  }

Sep 26 20:47:27.317: INFO: Error updating pvc ebs.csi.aws.combkxz2: PersistentVolumeClaim "ebs.csi.aws.combkxz2" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1093-e2e-sc9qxrn",
  	... // 3 identical fields
  }

Sep 26 20:47:29.321: INFO: Error updating pvc ebs.csi.aws.combkxz2: PersistentVolumeClaim "ebs.csi.aws.combkxz2" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1093-e2e-sc9qxrn",
  	... // 3 identical fields
  }

Sep 26 20:47:31.316: INFO: Error updating pvc ebs.csi.aws.combkxz2: PersistentVolumeClaim "ebs.csi.aws.combkxz2" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1093-e2e-sc9qxrn",
  	... // 3 identical fields
  }

Sep 26 20:47:33.326: INFO: Error updating pvc ebs.csi.aws.combkxz2: PersistentVolumeClaim "ebs.csi.aws.combkxz2" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1093-e2e-sc9qxrn",
  	... // 3 identical fields
  }

Sep 26 20:47:35.320: INFO: Error updating pvc ebs.csi.aws.combkxz2: PersistentVolumeClaim "ebs.csi.aws.combkxz2" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1093-e2e-sc9qxrn",
  	... // 3 identical fields
  }

Sep 26 20:47:37.316: INFO: Error updating pvc ebs.csi.aws.combkxz2: PersistentVolumeClaim "ebs.csi.aws.combkxz2" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1093-e2e-sc9qxrn",
  	... // 3 identical fields
  }

Sep 26 20:47:39.316: INFO: Error updating pvc ebs.csi.aws.combkxz2: PersistentVolumeClaim "ebs.csi.aws.combkxz2" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1093-e2e-sc9qxrn",
  	... // 3 identical fields
  }

Sep 26 20:47:41.317: INFO: Error updating pvc ebs.csi.aws.combkxz2: PersistentVolumeClaim "ebs.csi.aws.combkxz2" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1093-e2e-sc9qxrn",
  	... // 3 identical fields
  }

Sep 26 20:47:43.318: INFO: Error updating pvc ebs.csi.aws.combkxz2: PersistentVolumeClaim "ebs.csi.aws.combkxz2" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1093-e2e-sc9qxrn",
  	... // 3 identical fields
  }

Sep 26 20:47:45.316: INFO: Error updating pvc ebs.csi.aws.combkxz2: PersistentVolumeClaim "ebs.csi.aws.combkxz2" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1093-e2e-sc9qxrn",
  	... // 3 identical fields
  }

Sep 26 20:47:47.317: INFO: Error updating pvc ebs.csi.aws.combkxz2: PersistentVolumeClaim "ebs.csi.aws.combkxz2" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1093-e2e-sc9qxrn",
  	... // 3 identical fields
  }

Sep 26 20:47:49.318: INFO: Error updating pvc ebs.csi.aws.combkxz2: PersistentVolumeClaim "ebs.csi.aws.combkxz2" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1093-e2e-sc9qxrn",
  	... // 3 identical fields
  }

Sep 26 20:47:51.318: INFO: Error updating pvc ebs.csi.aws.combkxz2: PersistentVolumeClaim "ebs.csi.aws.combkxz2" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1093-e2e-sc9qxrn",
  	... // 3 identical fields
  }

Sep 26 20:47:51.534: INFO: Error updating pvc ebs.csi.aws.combkxz2: PersistentVolumeClaim "ebs.csi.aws.combkxz2" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 74 lines ...

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

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

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

    /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 112 lines ...
STEP: Deleting pod aws-client in namespace volume-5142
Sep 26 20:47:40.720: INFO: Waiting for pod aws-client to disappear
Sep 26 20:47:40.825: INFO: Pod aws-client still exists
Sep 26 20:47:42.826: INFO: Waiting for pod aws-client to disappear
Sep 26 20:47:42.930: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Sep 26 20:47:43.229: INFO: Couldn't delete PD "aws://eu-west-1a/vol-02678a11edf8038c0", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02678a11edf8038c0 is currently attached to i-06820b72c8819710e
	status code: 400, request id: 070931b5-70ab-40b5-a1ac-808746321a91
Sep 26 20:47:48.936: INFO: Couldn't delete PD "aws://eu-west-1a/vol-02678a11edf8038c0", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02678a11edf8038c0 is currently attached to i-06820b72c8819710e
	status code: 400, request id: 40ef3c69-ad78-4e0f-aa81-a4b8336a4278
Sep 26 20:47:54.638: INFO: Couldn't delete PD "aws://eu-west-1a/vol-02678a11edf8038c0", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02678a11edf8038c0 is currently attached to i-06820b72c8819710e
	status code: 400, request id: 0d643a4e-1f7c-4ed8-9470-50a4aca39d9c
Sep 26 20:48:00.318: INFO: Successfully deleted PD "aws://eu-west-1a/vol-02678a11edf8038c0".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 26 20:48:00.318: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-5142" for this suite.
... skipping 421 lines ...
Sep 26 20:47:29.308: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2389snf8j
STEP: creating a claim
Sep 26 20:47:29.416: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-dnmm
STEP: Creating a pod to test subpath
Sep 26 20:47:29.746: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-dnmm" in namespace "provisioning-2389" to be "Succeeded or Failed"
Sep 26 20:47:29.853: INFO: Pod "pod-subpath-test-dynamicpv-dnmm": Phase="Pending", Reason="", readiness=false. Elapsed: 107.42651ms
Sep 26 20:47:31.961: INFO: Pod "pod-subpath-test-dynamicpv-dnmm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.215557233s
Sep 26 20:47:34.076: INFO: Pod "pod-subpath-test-dynamicpv-dnmm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.33043887s
Sep 26 20:47:36.185: INFO: Pod "pod-subpath-test-dynamicpv-dnmm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.439351441s
Sep 26 20:47:38.293: INFO: Pod "pod-subpath-test-dynamicpv-dnmm": Phase="Pending", Reason="", readiness=false. Elapsed: 8.547150119s
Sep 26 20:47:40.401: INFO: Pod "pod-subpath-test-dynamicpv-dnmm": Phase="Pending", Reason="", readiness=false. Elapsed: 10.655734163s
... skipping 2 lines ...
Sep 26 20:47:46.730: INFO: Pod "pod-subpath-test-dynamicpv-dnmm": Phase="Pending", Reason="", readiness=false. Elapsed: 16.984120464s
Sep 26 20:47:48.839: INFO: Pod "pod-subpath-test-dynamicpv-dnmm": Phase="Pending", Reason="", readiness=false. Elapsed: 19.093319678s
Sep 26 20:47:50.953: INFO: Pod "pod-subpath-test-dynamicpv-dnmm": Phase="Pending", Reason="", readiness=false. Elapsed: 21.207643782s
Sep 26 20:47:53.062: INFO: Pod "pod-subpath-test-dynamicpv-dnmm": Phase="Pending", Reason="", readiness=false. Elapsed: 23.316738248s
Sep 26 20:47:55.170: INFO: Pod "pod-subpath-test-dynamicpv-dnmm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 25.42455215s
STEP: Saw pod success
Sep 26 20:47:55.170: INFO: Pod "pod-subpath-test-dynamicpv-dnmm" satisfied condition "Succeeded or Failed"
Sep 26 20:47:55.278: INFO: Trying to get logs from node ip-172-20-32-228.eu-west-1.compute.internal pod pod-subpath-test-dynamicpv-dnmm container test-container-subpath-dynamicpv-dnmm: <nil>
STEP: delete the pod
Sep 26 20:47:55.502: INFO: Waiting for pod pod-subpath-test-dynamicpv-dnmm to disappear
Sep 26 20:47:55.609: INFO: Pod pod-subpath-test-dynamicpv-dnmm no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-dnmm
Sep 26 20:47:55.609: INFO: Deleting pod "pod-subpath-test-dynamicpv-dnmm" in namespace "provisioning-2389"
... skipping 58 lines ...
Sep 26 20:47:21.235: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6831-e2e-sc2fcm7
STEP: creating a claim
Sep 26 20:47:21.342: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-xqt5
STEP: Creating a pod to test subpath
Sep 26 20:47:21.662: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-xqt5" in namespace "provisioning-6831" to be "Succeeded or Failed"
Sep 26 20:47:21.767: INFO: Pod "pod-subpath-test-dynamicpv-xqt5": Phase="Pending", Reason="", readiness=false. Elapsed: 105.741375ms
Sep 26 20:47:23.873: INFO: Pod "pod-subpath-test-dynamicpv-xqt5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.211732408s
Sep 26 20:47:25.980: INFO: Pod "pod-subpath-test-dynamicpv-xqt5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.317998333s
Sep 26 20:47:28.086: INFO: Pod "pod-subpath-test-dynamicpv-xqt5": Phase="Pending", Reason="", readiness=false. Elapsed: 6.424001311s
Sep 26 20:47:30.192: INFO: Pod "pod-subpath-test-dynamicpv-xqt5": Phase="Pending", Reason="", readiness=false. Elapsed: 8.530071073s
Sep 26 20:47:32.300: INFO: Pod "pod-subpath-test-dynamicpv-xqt5": Phase="Pending", Reason="", readiness=false. Elapsed: 10.638455979s
... skipping 3 lines ...
Sep 26 20:47:40.730: INFO: Pod "pod-subpath-test-dynamicpv-xqt5": Phase="Pending", Reason="", readiness=false. Elapsed: 19.06867949s
Sep 26 20:47:42.838: INFO: Pod "pod-subpath-test-dynamicpv-xqt5": Phase="Pending", Reason="", readiness=false. Elapsed: 21.175953654s
Sep 26 20:47:44.944: INFO: Pod "pod-subpath-test-dynamicpv-xqt5": Phase="Pending", Reason="", readiness=false. Elapsed: 23.282103223s
Sep 26 20:47:47.050: INFO: Pod "pod-subpath-test-dynamicpv-xqt5": Phase="Pending", Reason="", readiness=false. Elapsed: 25.388112195s
Sep 26 20:47:49.156: INFO: Pod "pod-subpath-test-dynamicpv-xqt5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 27.494053668s
STEP: Saw pod success
Sep 26 20:47:49.156: INFO: Pod "pod-subpath-test-dynamicpv-xqt5" satisfied condition "Succeeded or Failed"
Sep 26 20:47:49.262: INFO: Trying to get logs from node ip-172-20-39-136.eu-west-1.compute.internal pod pod-subpath-test-dynamicpv-xqt5 container test-container-subpath-dynamicpv-xqt5: <nil>
STEP: delete the pod
Sep 26 20:47:49.481: INFO: Waiting for pod pod-subpath-test-dynamicpv-xqt5 to disappear
Sep 26 20:47:49.587: INFO: Pod pod-subpath-test-dynamicpv-xqt5 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-xqt5
Sep 26 20:47:49.587: INFO: Deleting pod "pod-subpath-test-dynamicpv-xqt5" in namespace "provisioning-6831"
STEP: Creating pod pod-subpath-test-dynamicpv-xqt5
STEP: Creating a pod to test subpath
Sep 26 20:47:49.798: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-xqt5" in namespace "provisioning-6831" to be "Succeeded or Failed"
Sep 26 20:47:49.904: INFO: Pod "pod-subpath-test-dynamicpv-xqt5": Phase="Pending", Reason="", readiness=false. Elapsed: 105.451826ms
Sep 26 20:47:52.010: INFO: Pod "pod-subpath-test-dynamicpv-xqt5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.212014676s
Sep 26 20:47:54.117: INFO: Pod "pod-subpath-test-dynamicpv-xqt5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.318530657s
Sep 26 20:47:56.223: INFO: Pod "pod-subpath-test-dynamicpv-xqt5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.424340054s
STEP: Saw pod success
Sep 26 20:47:56.223: INFO: Pod "pod-subpath-test-dynamicpv-xqt5" satisfied condition "Succeeded or Failed"
Sep 26 20:47:56.328: INFO: Trying to get logs from node ip-172-20-39-136.eu-west-1.compute.internal pod pod-subpath-test-dynamicpv-xqt5 container test-container-subpath-dynamicpv-xqt5: <nil>
STEP: delete the pod
Sep 26 20:47:56.553: INFO: Waiting for pod pod-subpath-test-dynamicpv-xqt5 to disappear
Sep 26 20:47:56.660: INFO: Pod pod-subpath-test-dynamicpv-xqt5 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-xqt5
Sep 26 20:47:56.660: INFO: Deleting pod "pod-subpath-test-dynamicpv-xqt5" in namespace "provisioning-6831"
... skipping 417 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.GDxjzwo8j/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.GDxjzwo8j/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.GDxjzwo8j/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.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 15 lines ...
Sep 26 20:48:19.723: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 48 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 26 20:48:00.541: 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.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Sep 26 20:48:01.067: INFO: Creating resource for dynamic PV
Sep 26 20:48:01.067: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-323-e2e-scxvlmw
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Sep 26 20:48:07.808: INFO: Deleting pod "pod-c375c88b-a87c-4b64-9e4e-d171090d549a" in namespace "volumemode-323"
Sep 26 20:48:07.915: INFO: Wait up to 5m0s for pod "pod-c375c88b-a87c-4b64-9e4e-d171090d549a" to be fully deleted
STEP: Deleting pvc
Sep 26 20:48:10.334: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comjhs5b"
Sep 26 20:48:10.439: INFO: Waiting up to 5m0s for PersistentVolume pvc-c730404f-05de-46b9-b89f-1896ceaf0099 to get deleted
Sep 26 20:48:10.543: INFO: PersistentVolume pvc-c730404f-05de-46b9-b89f-1896ceaf0099 found and phase=Released (103.716675ms)
... skipping 8 lines ...

• [SLOW TEST:20.532 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.GDxjzwo8j/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.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Sep 26 20:48:21.074: INFO: Driver supports dynamic provisioning, skipping PreprovisionedPV pattern
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
... skipping 96 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.GDxjzwo8j/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.GDxjzwo8j/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.GDxjzwo8j/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.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Distro debian doesn't support ntfs -- skipping

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.000 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.GDxjzwo8j/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.GDxjzwo8j/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.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 90 lines ...
Sep 26 20:46:48.757: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-6141-e2e-sc7h4hd      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-6141    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-6141-e2e-sc7h4hd,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-6141    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-6141-e2e-sc7h4hd,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-6141    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-6141-e2e-sc7h4hd,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-6141-e2e-sc7h4hd    47d01cde-9b4f-44b4-be69-a98aeeea4a9e 11426 0 2021-09-26 20:46:48 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-09-26 20:46:48 +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-4t5kj pvc- provisioning-6141  4f70ede9-5b8f-4da8-8e74-8b0ad0fd899a 11439 0 2021-09-26 20:46:49 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-09-26 20:46:49 +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-6141-e2e-sc7h4hd,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-5259bef7-e7cd-47b6-9941-d3caf40a6e78 in namespace provisioning-6141
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Sep 26 20:47:05.944: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-d4v62" in namespace "provisioning-6141" to be "Succeeded or Failed"
Sep 26 20:47:06.050: INFO: Pod "pvc-volume-tester-writer-d4v62": Phase="Pending", Reason="", readiness=false. Elapsed: 106.216699ms
Sep 26 20:47:08.157: INFO: Pod "pvc-volume-tester-writer-d4v62": Phase="Pending", Reason="", readiness=false. Elapsed: 2.213019506s
Sep 26 20:47:10.266: INFO: Pod "pvc-volume-tester-writer-d4v62": Phase="Pending", Reason="", readiness=false. Elapsed: 4.321430643s
Sep 26 20:47:12.381: INFO: Pod "pvc-volume-tester-writer-d4v62": Phase="Pending", Reason="", readiness=false. Elapsed: 6.436408345s
Sep 26 20:47:14.488: INFO: Pod "pvc-volume-tester-writer-d4v62": Phase="Pending", Reason="", readiness=false. Elapsed: 8.544031916s
Sep 26 20:47:16.597: INFO: Pod "pvc-volume-tester-writer-d4v62": Phase="Pending", Reason="", readiness=false. Elapsed: 10.65263977s
... skipping 22 lines ...
Sep 26 20:48:05.075: INFO: Pod "pvc-volume-tester-writer-d4v62": Phase="Pending", Reason="", readiness=false. Elapsed: 59.1305517s
Sep 26 20:48:07.185: INFO: Pod "pvc-volume-tester-writer-d4v62": Phase="Pending", Reason="", readiness=false. Elapsed: 1m1.24077355s
Sep 26 20:48:09.292: INFO: Pod "pvc-volume-tester-writer-d4v62": Phase="Pending", Reason="", readiness=false. Elapsed: 1m3.347810644s
Sep 26 20:48:11.401: INFO: Pod "pvc-volume-tester-writer-d4v62": Phase="Pending", Reason="", readiness=false. Elapsed: 1m5.45660912s
Sep 26 20:48:13.508: INFO: Pod "pvc-volume-tester-writer-d4v62": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m7.563350228s
STEP: Saw pod success
Sep 26 20:48:13.508: INFO: Pod "pvc-volume-tester-writer-d4v62" satisfied condition "Succeeded or Failed"
Sep 26 20:48:13.724: INFO: Pod pvc-volume-tester-writer-d4v62 has the following logs: 
Sep 26 20:48:13.724: INFO: Deleting pod "pvc-volume-tester-writer-d4v62" in namespace "provisioning-6141"
Sep 26 20:48:13.839: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-d4v62" 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-39-136.eu-west-1.compute.internal"
Sep 26 20:48:14.269: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-4p28q" in namespace "provisioning-6141" to be "Succeeded or Failed"
Sep 26 20:48:14.376: INFO: Pod "pvc-volume-tester-reader-4p28q": Phase="Pending", Reason="", readiness=false. Elapsed: 106.497574ms
Sep 26 20:48:16.484: INFO: Pod "pvc-volume-tester-reader-4p28q": Phase="Pending", Reason="", readiness=false. Elapsed: 2.214370685s
Sep 26 20:48:18.592: INFO: Pod "pvc-volume-tester-reader-4p28q": Phase="Pending", Reason="", readiness=false. Elapsed: 4.322174819s
Sep 26 20:48:20.700: INFO: Pod "pvc-volume-tester-reader-4p28q": Phase="Pending", Reason="", readiness=false. Elapsed: 6.430802731s
Sep 26 20:48:22.807: INFO: Pod "pvc-volume-tester-reader-4p28q": Phase="Pending", Reason="", readiness=false. Elapsed: 8.537807323s
Sep 26 20:48:24.914: INFO: Pod "pvc-volume-tester-reader-4p28q": Phase="Pending", Reason="", readiness=false. Elapsed: 10.64466473s
Sep 26 20:48:27.021: INFO: Pod "pvc-volume-tester-reader-4p28q": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.751930987s
STEP: Saw pod success
Sep 26 20:48:27.021: INFO: Pod "pvc-volume-tester-reader-4p28q" satisfied condition "Succeeded or Failed"
Sep 26 20:48:27.256: INFO: Pod pvc-volume-tester-reader-4p28q has the following logs: hello world

Sep 26 20:48:27.256: INFO: Deleting pod "pvc-volume-tester-reader-4p28q" in namespace "provisioning-6141"
Sep 26 20:48:27.379: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-4p28q" to be fully deleted
Sep 26 20:48:27.498: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-4t5kj] to have phase Bound
Sep 26 20:48:27.605: INFO: PersistentVolumeClaim pvc-4t5kj found and phase=Bound (106.716611ms)
... skipping 203 lines ...
Sep 26 20:48:06.762: INFO: Creating resource for dynamic PV
Sep 26 20:48:06.762: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8347w6jq8
STEP: creating a claim
Sep 26 20:48:06.868: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-8347
Sep 26 20:48:07.190: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-8347" in namespace "provisioning-8347" to be "Succeeded or Failed"
Sep 26 20:48:07.296: INFO: Pod "volume-prep-provisioning-8347": Phase="Pending", Reason="", readiness=false. Elapsed: 105.821386ms
Sep 26 20:48:09.402: INFO: Pod "volume-prep-provisioning-8347": Phase="Pending", Reason="", readiness=false. Elapsed: 2.211868178s
Sep 26 20:48:11.511: INFO: Pod "volume-prep-provisioning-8347": Phase="Pending", Reason="", readiness=false. Elapsed: 4.321623166s
Sep 26 20:48:13.619: INFO: Pod "volume-prep-provisioning-8347": Phase="Pending", Reason="", readiness=false. Elapsed: 6.429074501s
Sep 26 20:48:15.725: INFO: Pod "volume-prep-provisioning-8347": Phase="Running", Reason="", readiness=true. Elapsed: 8.535180065s
Sep 26 20:48:17.832: INFO: Pod "volume-prep-provisioning-8347": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.641991831s
STEP: Saw pod success
Sep 26 20:48:17.832: INFO: Pod "volume-prep-provisioning-8347" satisfied condition "Succeeded or Failed"
Sep 26 20:48:17.832: INFO: Deleting pod "volume-prep-provisioning-8347" in namespace "provisioning-8347"
Sep 26 20:48:17.945: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-8347" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-82cc
STEP: Checking for subpath error in container status
Sep 26 20:48:28.369: INFO: Deleting pod "pod-subpath-test-dynamicpv-82cc" in namespace "provisioning-8347"
Sep 26 20:48:28.480: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-82cc" to be fully deleted
STEP: Deleting pod
Sep 26 20:48:28.600: INFO: Deleting pod "pod-subpath-test-dynamicpv-82cc" in namespace "provisioning-8347"
STEP: Deleting pvc
Sep 26 20:48:28.916: INFO: Deleting PersistentVolumeClaim "aws2fsdl"
... skipping 148 lines ...
Sep 26 20:48:39.662: INFO: Waiting for pod aws-client to disappear
Sep 26 20:48:39.771: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Sep 26 20:48:39.771: INFO: Deleting PersistentVolumeClaim "pvc-sjr6c"
Sep 26 20:48:39.879: INFO: Deleting PersistentVolume "aws-bgtvr"
Sep 26 20:48:40.754: INFO: Couldn't delete PD "aws://eu-west-1a/vol-0892d2516d2556050", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0892d2516d2556050 is currently attached to i-03889c28dcccf7b5b
	status code: 400, request id: 6c844608-feaf-4407-9aa2-d92cd42563d1
Sep 26 20:48:46.419: INFO: Couldn't delete PD "aws://eu-west-1a/vol-0892d2516d2556050", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0892d2516d2556050 is currently attached to i-03889c28dcccf7b5b
	status code: 400, request id: 7478423f-5266-4424-8bfe-25fb7ed8ae4c
Sep 26 20:48:52.084: INFO: Successfully deleted PD "aws://eu-west-1a/vol-0892d2516d2556050".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 26 20:48:52.084: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8092" for this suite.
... skipping 192 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 26 20:48:22.098: 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.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Sep 26 20:48:22.634: INFO: Creating resource for dynamic PV
Sep 26 20:48:22.634: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4526-e2e-scsdpw5
STEP: creating a claim
Sep 26 20:48:22.740: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-l6vr
STEP: Checking for subpath error in container status
Sep 26 20:48:45.273: INFO: Deleting pod "pod-subpath-test-dynamicpv-l6vr" in namespace "provisioning-4526"
Sep 26 20:48:45.383: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-l6vr" to be fully deleted
STEP: Deleting pod
Sep 26 20:48:47.596: INFO: Deleting pod "pod-subpath-test-dynamicpv-l6vr" in namespace "provisioning-4526"
STEP: Deleting pvc
Sep 26 20:48:47.912: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com9twk4"
... skipping 11 lines ...

• [SLOW TEST:41.681 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath file is outside the volume [Slow][LinuxOnly]
    /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (ext3)] volumes
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Sep 26 20:49:03.780: INFO: Driver "ebs.csi.aws.com" does not support volume type "PreprovisionedPV" - skipping
[AfterEach] [Testpattern: Pre-provisioned PV (ext3)] volumes
... skipping 72 lines ...
Sep 26 20:48:12.316: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-1932-e2e-scwmmrt
STEP: creating a claim
Sep 26 20:48:12.422: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-g64j
STEP: Creating a pod to test exec-volume-test
Sep 26 20:48:12.742: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-g64j" in namespace "volume-1932" to be "Succeeded or Failed"
Sep 26 20:48:12.851: INFO: Pod "exec-volume-test-dynamicpv-g64j": Phase="Pending", Reason="", readiness=false. Elapsed: 108.795573ms
Sep 26 20:48:14.957: INFO: Pod "exec-volume-test-dynamicpv-g64j": Phase="Pending", Reason="", readiness=false. Elapsed: 2.215269663s
Sep 26 20:48:17.064: INFO: Pod "exec-volume-test-dynamicpv-g64j": Phase="Pending", Reason="", readiness=false. Elapsed: 4.321535349s
Sep 26 20:48:19.170: INFO: Pod "exec-volume-test-dynamicpv-g64j": Phase="Pending", Reason="", readiness=false. Elapsed: 6.428021049s
Sep 26 20:48:21.277: INFO: Pod "exec-volume-test-dynamicpv-g64j": Phase="Pending", Reason="", readiness=false. Elapsed: 8.534706595s
Sep 26 20:48:23.385: INFO: Pod "exec-volume-test-dynamicpv-g64j": Phase="Pending", Reason="", readiness=false. Elapsed: 10.64254396s
Sep 26 20:48:25.494: INFO: Pod "exec-volume-test-dynamicpv-g64j": Phase="Pending", Reason="", readiness=false. Elapsed: 12.751387547s
Sep 26 20:48:27.600: INFO: Pod "exec-volume-test-dynamicpv-g64j": Phase="Pending", Reason="", readiness=false. Elapsed: 14.858325751s
Sep 26 20:48:29.708: INFO: Pod "exec-volume-test-dynamicpv-g64j": Phase="Pending", Reason="", readiness=false. Elapsed: 16.966123013s
Sep 26 20:48:31.815: INFO: Pod "exec-volume-test-dynamicpv-g64j": Phase="Pending", Reason="", readiness=false. Elapsed: 19.072393033s
Sep 26 20:48:33.922: INFO: Pod "exec-volume-test-dynamicpv-g64j": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.179881469s
STEP: Saw pod success
Sep 26 20:48:33.922: INFO: Pod "exec-volume-test-dynamicpv-g64j" satisfied condition "Succeeded or Failed"
Sep 26 20:48:34.028: INFO: Trying to get logs from node ip-172-20-32-228.eu-west-1.compute.internal pod exec-volume-test-dynamicpv-g64j container exec-container-dynamicpv-g64j: <nil>
STEP: delete the pod
Sep 26 20:48:34.247: INFO: Waiting for pod exec-volume-test-dynamicpv-g64j to disappear
Sep 26 20:48:34.352: INFO: Pod exec-volume-test-dynamicpv-g64j no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-g64j
Sep 26 20:48:34.353: INFO: Deleting pod "exec-volume-test-dynamicpv-g64j" in namespace "volume-1932"
... skipping 67 lines ...
Sep 26 20:48:45.310: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-57002fcp9
STEP: creating a claim
Sep 26 20:48:45.416: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-p5ln
STEP: Creating a pod to test subpath
Sep 26 20:48:45.739: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-p5ln" in namespace "provisioning-5700" to be "Succeeded or Failed"
Sep 26 20:48:45.847: INFO: Pod "pod-subpath-test-dynamicpv-p5ln": Phase="Pending", Reason="", readiness=false. Elapsed: 108.00171ms
Sep 26 20:48:47.953: INFO: Pod "pod-subpath-test-dynamicpv-p5ln": Phase="Pending", Reason="", readiness=false. Elapsed: 2.214180634s
Sep 26 20:48:50.059: INFO: Pod "pod-subpath-test-dynamicpv-p5ln": Phase="Pending", Reason="", readiness=false. Elapsed: 4.32003243s
Sep 26 20:48:52.167: INFO: Pod "pod-subpath-test-dynamicpv-p5ln": Phase="Pending", Reason="", readiness=false. Elapsed: 6.427489494s
Sep 26 20:48:54.273: INFO: Pod "pod-subpath-test-dynamicpv-p5ln": Phase="Pending", Reason="", readiness=false. Elapsed: 8.534143907s
Sep 26 20:48:56.380: INFO: Pod "pod-subpath-test-dynamicpv-p5ln": Phase="Pending", Reason="", readiness=false. Elapsed: 10.640358217s
Sep 26 20:48:58.489: INFO: Pod "pod-subpath-test-dynamicpv-p5ln": Phase="Pending", Reason="", readiness=false. Elapsed: 12.749536322s
Sep 26 20:49:00.595: INFO: Pod "pod-subpath-test-dynamicpv-p5ln": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.85537165s
STEP: Saw pod success
Sep 26 20:49:00.595: INFO: Pod "pod-subpath-test-dynamicpv-p5ln" satisfied condition "Succeeded or Failed"
Sep 26 20:49:00.702: INFO: Trying to get logs from node ip-172-20-32-24.eu-west-1.compute.internal pod pod-subpath-test-dynamicpv-p5ln container test-container-volume-dynamicpv-p5ln: <nil>
STEP: delete the pod
Sep 26 20:49:00.955: INFO: Waiting for pod pod-subpath-test-dynamicpv-p5ln to disappear
Sep 26 20:49:01.061: INFO: Pod pod-subpath-test-dynamicpv-p5ln no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-p5ln
Sep 26 20:49:01.061: INFO: Deleting pod "pod-subpath-test-dynamicpv-p5ln" in namespace "provisioning-5700"
... skipping 257 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.GDxjzwo8j/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.GDxjzwo8j/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.GDxjzwo8j/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.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 375 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 26 20:48:53.230: 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.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Sep 26 20:48:53.757: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Sep 26 20:48:54.603: INFO: Successfully created a new PD: "aws://eu-west-1a/vol-0ccf96a95d9c05fb2".
Sep 26 20:48:54.603: INFO: Creating resource for pre-provisioned PV
Sep 26 20:48:54.603: INFO: Creating PVC and PV
... skipping 2 lines ...
Sep 26 20:48:54.955: INFO: Waiting up to timeout=3m0s for PersistentVolumeClaims [pvc-qx2fc] to have phase Bound
Sep 26 20:48:55.060: INFO: PersistentVolumeClaim pvc-qx2fc found but phase is Pending instead of Bound.
Sep 26 20:48:57.173: INFO: PersistentVolumeClaim pvc-qx2fc found and phase=Bound (2.217893779s)
Sep 26 20:48:57.173: INFO: Waiting up to 3m0s for PersistentVolume aws-bx227 to have phase Bound
Sep 26 20:48:57.278: INFO: PersistentVolume aws-bx227 found and phase=Bound (104.894172ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Sep 26 20:48:57.808: INFO: Deleting pod "pod-cc66ea1a-ded1-4718-bb50-70c0d3dba139" in namespace "volumemode-9322"
Sep 26 20:48:57.917: INFO: Wait up to 5m0s for pod "pod-cc66ea1a-ded1-4718-bb50-70c0d3dba139" to be fully deleted
STEP: Deleting pv and pvc
Sep 26 20:49:00.128: INFO: Deleting PersistentVolumeClaim "pvc-qx2fc"
Sep 26 20:49:00.235: INFO: Deleting PersistentVolume "aws-bx227"
Sep 26 20:49:00.574: INFO: Couldn't delete PD "aws://eu-west-1a/vol-0ccf96a95d9c05fb2", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ccf96a95d9c05fb2 is currently attached to i-06820b72c8819710e
	status code: 400, request id: 684b98e3-ebcb-4a3d-b437-d5c69267d25e
Sep 26 20:49:06.247: INFO: Couldn't delete PD "aws://eu-west-1a/vol-0ccf96a95d9c05fb2", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ccf96a95d9c05fb2 is currently attached to i-06820b72c8819710e
	status code: 400, request id: 310dc6da-8116-42ce-b7cc-0ecba63f3947
Sep 26 20:49:11.879: INFO: Couldn't delete PD "aws://eu-west-1a/vol-0ccf96a95d9c05fb2", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ccf96a95d9c05fb2 is currently attached to i-06820b72c8819710e
	status code: 400, request id: d20d368b-3962-4597-be86-f3296c666f8f
Sep 26 20:49:17.616: INFO: Couldn't delete PD "aws://eu-west-1a/vol-0ccf96a95d9c05fb2", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ccf96a95d9c05fb2 is currently attached to i-06820b72c8819710e
	status code: 400, request id: 3784ba5f-5ae2-4022-8251-8bfa47fcc87b
Sep 26 20:49:23.242: INFO: Successfully deleted PD "aws://eu-west-1a/vol-0ccf96a95d9c05fb2".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 26 20:49:23.242: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-9322" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.GDxjzwo8j/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.GDxjzwo8j/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
    /tmp/kops.GDxjzwo8j/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.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (ntfs)][Feature:Windows] volumes
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Sep 26 20:49:23.455: INFO: Distro debian doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Pre-provisioned PV (ntfs)][Feature:Windows] volumes
... skipping 338 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 26 20:48:52.310: 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.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Sep 26 20:48:52.847: INFO: Creating resource for dynamic PV
Sep 26 20:48:52.847: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-6631-e2e-scbb786
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Sep 26 20:48:59.604: INFO: Deleting pod "pod-276ed8a2-e5d6-4cac-aa62-1010394e223a" in namespace "volumemode-6631"
Sep 26 20:48:59.712: INFO: Wait up to 5m0s for pod "pod-276ed8a2-e5d6-4cac-aa62-1010394e223a" to be fully deleted
STEP: Deleting pvc
Sep 26 20:49:02.145: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comr2x8l"
Sep 26 20:49:02.258: INFO: Waiting up to 5m0s for PersistentVolume pvc-9fb0c1a1-3f8d-4228-bc89-7d6775d35c15 to get deleted
Sep 26 20:49:02.366: INFO: PersistentVolume pvc-9fb0c1a1-3f8d-4228-bc89-7d6775d35c15 found and phase=Released (107.951765ms)
... skipping 13 lines ...

• [SLOW TEST:46.155 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.GDxjzwo8j/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.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 160 lines ...
Sep 26 20:49:13.530: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-815-e2e-sc7vjh9
STEP: creating a claim
Sep 26 20:49:13.637: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-wplf
STEP: Creating a pod to test subpath
Sep 26 20:49:13.957: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-wplf" in namespace "provisioning-815" to be "Succeeded or Failed"
Sep 26 20:49:14.063: INFO: Pod "pod-subpath-test-dynamicpv-wplf": Phase="Pending", Reason="", readiness=false. Elapsed: 105.404524ms
Sep 26 20:49:16.169: INFO: Pod "pod-subpath-test-dynamicpv-wplf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.21192758s
Sep 26 20:49:18.277: INFO: Pod "pod-subpath-test-dynamicpv-wplf": Phase="Pending", Reason="", readiness=false. Elapsed: 4.319144664s
Sep 26 20:49:20.384: INFO: Pod "pod-subpath-test-dynamicpv-wplf": Phase="Pending", Reason="", readiness=false. Elapsed: 6.426377119s
Sep 26 20:49:22.490: INFO: Pod "pod-subpath-test-dynamicpv-wplf": Phase="Pending", Reason="", readiness=false. Elapsed: 8.532355402s
Sep 26 20:49:24.596: INFO: Pod "pod-subpath-test-dynamicpv-wplf": Phase="Pending", Reason="", readiness=false. Elapsed: 10.638216209s
Sep 26 20:49:26.704: INFO: Pod "pod-subpath-test-dynamicpv-wplf": Phase="Pending", Reason="", readiness=false. Elapsed: 12.746586202s
Sep 26 20:49:28.816: INFO: Pod "pod-subpath-test-dynamicpv-wplf": Phase="Pending", Reason="", readiness=false. Elapsed: 14.858006187s
Sep 26 20:49:30.922: INFO: Pod "pod-subpath-test-dynamicpv-wplf": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.964368401s
STEP: Saw pod success
Sep 26 20:49:30.922: INFO: Pod "pod-subpath-test-dynamicpv-wplf" satisfied condition "Succeeded or Failed"
Sep 26 20:49:31.028: INFO: Trying to get logs from node ip-172-20-32-228.eu-west-1.compute.internal pod pod-subpath-test-dynamicpv-wplf container test-container-volume-dynamicpv-wplf: <nil>
STEP: delete the pod
Sep 26 20:49:31.250: INFO: Waiting for pod pod-subpath-test-dynamicpv-wplf to disappear
Sep 26 20:49:31.355: INFO: Pod pod-subpath-test-dynamicpv-wplf no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-wplf
Sep 26 20:49:31.355: INFO: Deleting pod "pod-subpath-test-dynamicpv-wplf" in namespace "provisioning-815"
... skipping 65 lines ...
STEP: Deleting pod aws-client in namespace volume-3666
Sep 26 20:49:40.258: INFO: Waiting for pod aws-client to disappear
Sep 26 20:49:40.364: INFO: Pod aws-client still exists
Sep 26 20:49:42.365: INFO: Waiting for pod aws-client to disappear
Sep 26 20:49:42.472: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Sep 26 20:49:42.720: INFO: Couldn't delete PD "aws://eu-west-1a/vol-042775f6505c1cc57", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-042775f6505c1cc57 is currently attached to i-06820b72c8819710e
	status code: 400, request id: 4da62070-9731-4bdb-8ca1-4899d9659edd
Sep 26 20:49:48.358: INFO: Successfully deleted PD "aws://eu-west-1a/vol-042775f6505c1cc57".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 26 20:49:48.358: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-3666" for this suite.
... skipping 109 lines ...
Sep 26 20:49:21.462: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-3926-e2e-scbhlcv
STEP: creating a claim
Sep 26 20:49:21.568: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-7k5h
STEP: Creating a pod to test exec-volume-test
Sep 26 20:49:21.887: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-7k5h" in namespace "volume-3926" to be "Succeeded or Failed"
Sep 26 20:49:21.992: INFO: Pod "exec-volume-test-dynamicpv-7k5h": Phase="Pending", Reason="", readiness=false. Elapsed: 104.955187ms
Sep 26 20:49:24.098: INFO: Pod "exec-volume-test-dynamicpv-7k5h": Phase="Pending", Reason="", readiness=false. Elapsed: 2.210649331s
Sep 26 20:49:26.204: INFO: Pod "exec-volume-test-dynamicpv-7k5h": Phase="Pending", Reason="", readiness=false. Elapsed: 4.316271818s
Sep 26 20:49:28.310: INFO: Pod "exec-volume-test-dynamicpv-7k5h": Phase="Pending", Reason="", readiness=false. Elapsed: 6.422638077s
Sep 26 20:49:30.416: INFO: Pod "exec-volume-test-dynamicpv-7k5h": Phase="Pending", Reason="", readiness=false. Elapsed: 8.528296078s
Sep 26 20:49:32.521: INFO: Pod "exec-volume-test-dynamicpv-7k5h": Phase="Pending", Reason="", readiness=false. Elapsed: 10.633971629s
Sep 26 20:49:34.628: INFO: Pod "exec-volume-test-dynamicpv-7k5h": Phase="Pending", Reason="", readiness=false. Elapsed: 12.740478477s
Sep 26 20:49:36.734: INFO: Pod "exec-volume-test-dynamicpv-7k5h": Phase="Pending", Reason="", readiness=false. Elapsed: 14.846145863s
Sep 26 20:49:38.840: INFO: Pod "exec-volume-test-dynamicpv-7k5h": Phase="Pending", Reason="", readiness=false. Elapsed: 16.952316771s
Sep 26 20:49:40.945: INFO: Pod "exec-volume-test-dynamicpv-7k5h": Phase="Pending", Reason="", readiness=false. Elapsed: 19.057912769s
Sep 26 20:49:43.053: INFO: Pod "exec-volume-test-dynamicpv-7k5h": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.165741481s
STEP: Saw pod success
Sep 26 20:49:43.053: INFO: Pod "exec-volume-test-dynamicpv-7k5h" satisfied condition "Succeeded or Failed"
Sep 26 20:49:43.158: INFO: Trying to get logs from node ip-172-20-49-137.eu-west-1.compute.internal pod exec-volume-test-dynamicpv-7k5h container exec-container-dynamicpv-7k5h: <nil>
STEP: delete the pod
Sep 26 20:49:43.402: INFO: Waiting for pod exec-volume-test-dynamicpv-7k5h to disappear
Sep 26 20:49:43.511: INFO: Pod exec-volume-test-dynamicpv-7k5h no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-7k5h
Sep 26 20:49:43.511: INFO: Deleting pod "exec-volume-test-dynamicpv-7k5h" in namespace "volume-3926"
... skipping 359 lines ...
STEP: Found 9 events.
Sep 26 20:50:15.618: INFO: At 2021-09-26 20:43:21 +0000 UTC - event for awsfblr2: {persistentvolume-controller } WaitForFirstConsumer: waiting for first consumer to be created before binding
Sep 26 20:50:15.618: INFO: At 2021-09-26 20:43:21 +0000 UTC - event for awsfblr2: {persistentvolume-controller } ExternalProvisioning: waiting for a volume to be created, either by external provisioner "ebs.csi.aws.com" or manually created by system administrator
Sep 26 20:50:15.618: INFO: At 2021-09-26 20:43:21 +0000 UTC - event for awsfblr2: {ebs.csi.aws.com_ebs-csi-controller-564bc97466-sh5rd_7b36448d-4594-4fe3-a232-822f90cd0b9a } Provisioning: External provisioner is provisioning volume for claim "volume-expand-8131/awsfblr2"
Sep 26 20:50:15.618: INFO: At 2021-09-26 20:43:25 +0000 UTC - event for awsfblr2: {ebs.csi.aws.com_ebs-csi-controller-564bc97466-sh5rd_7b36448d-4594-4fe3-a232-822f90cd0b9a } ProvisioningSucceeded: Successfully provisioned volume pvc-16fe1748-4069-4679-9f8b-ae74191ac980
Sep 26 20:50:15.618: INFO: At 2021-09-26 20:43:25 +0000 UTC - event for pod-c02dc442-4278-4a4b-b006-6784c9b91893: {default-scheduler } Scheduled: Successfully assigned volume-expand-8131/pod-c02dc442-4278-4a4b-b006-6784c9b91893 to ip-172-20-32-24.eu-west-1.compute.internal
Sep 26 20:50:15.618: INFO: At 2021-09-26 20:44:15 +0000 UTC - event for pod-c02dc442-4278-4a4b-b006-6784c9b91893: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-16fe1748-4069-4679-9f8b-ae74191ac980" : rpc error: code = DeadlineExceeded desc = context deadline exceeded
Sep 26 20:50:15.618: INFO: At 2021-09-26 20:44:21 +0000 UTC - event for pod-c02dc442-4278-4a4b-b006-6784c9b91893: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-16fe1748-4069-4679-9f8b-ae74191ac980" : rpc error: code = Internal desc = Could not attach volume "vol-0a5ba45c67564d4ac" to node "i-0ede337f3f46589a5": attachment of disk "vol-0a5ba45c67564d4ac" failed, expected device to be attached but was attaching
Sep 26 20:50:15.618: INFO: At 2021-09-26 20:45:28 +0000 UTC - event for pod-c02dc442-4278-4a4b-b006-6784c9b91893: {kubelet ip-172-20-32-24.eu-west-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume1], unattached volumes=[kube-api-access-zpmbf volume1]: timed out waiting for the condition
Sep 26 20:50:15.618: INFO: At 2021-09-26 20:47:43 +0000 UTC - event for pod-c02dc442-4278-4a4b-b006-6784c9b91893: {kubelet ip-172-20-32-24.eu-west-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume1], unattached volumes=[volume1 kube-api-access-zpmbf]: timed out waiting for the condition
Sep 26 20:50:15.723: INFO: POD  NODE  PHASE  GRACE  CONDITIONS
Sep 26 20:50:15.723: INFO: 
Sep 26 20:50:15.830: INFO: 
Logging node info for node ip-172-20-32-228.eu-west-1.compute.internal
... skipping 168 lines ...
    [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand
    /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      Verify if offline PVC expansion works [It]
      /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volume_expand.go:174

      While creating pods for resizing
      Unexpected error:
          <*errors.errorString | 0xc000ed4170>: {
              s: "pod \"pod-c02dc442-4278-4a4b-b006-6784c9b91893\" is not Running: timed out waiting for the condition",
          }
          pod "pod-c02dc442-4278-4a4b-b006-6784c9b91893" is not Running: timed out waiting for the condition
      occurred

... skipping 32 lines ...
STEP: Found 8 events.
Sep 26 20:50:33.720: INFO: At 2021-09-26 20:43:29 +0000 UTC - event for awsjnqnq: {persistentvolume-controller } WaitForFirstConsumer: waiting for first consumer to be created before binding
Sep 26 20:50:33.720: INFO: At 2021-09-26 20:43:30 +0000 UTC - event for awsjnqnq: {persistentvolume-controller } ExternalProvisioning: waiting for a volume to be created, either by external provisioner "ebs.csi.aws.com" or manually created by system administrator
Sep 26 20:50:33.720: INFO: At 2021-09-26 20:43:30 +0000 UTC - event for awsjnqnq: {ebs.csi.aws.com_ebs-csi-controller-564bc97466-sh5rd_7b36448d-4594-4fe3-a232-822f90cd0b9a } Provisioning: External provisioner is provisioning volume for claim "volume-expand-8986/awsjnqnq"
Sep 26 20:50:33.720: INFO: At 2021-09-26 20:43:33 +0000 UTC - event for awsjnqnq: {ebs.csi.aws.com_ebs-csi-controller-564bc97466-sh5rd_7b36448d-4594-4fe3-a232-822f90cd0b9a } ProvisioningSucceeded: Successfully provisioned volume pvc-84b6e5e5-2f11-45ba-9fa0-e17325e7c357
Sep 26 20:50:33.721: INFO: At 2021-09-26 20:43:34 +0000 UTC - event for pod-43053679-89e8-4c9f-b799-d9b16001d606: {default-scheduler } Scheduled: Successfully assigned volume-expand-8986/pod-43053679-89e8-4c9f-b799-d9b16001d606 to ip-172-20-32-24.eu-west-1.compute.internal
Sep 26 20:50:33.721: INFO: At 2021-09-26 20:44:18 +0000 UTC - event for pod-43053679-89e8-4c9f-b799-d9b16001d606: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-84b6e5e5-2f11-45ba-9fa0-e17325e7c357" : rpc error: code = DeadlineExceeded desc = context deadline exceeded
Sep 26 20:50:33.721: INFO: At 2021-09-26 20:44:19 +0000 UTC - event for pod-43053679-89e8-4c9f-b799-d9b16001d606: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-84b6e5e5-2f11-45ba-9fa0-e17325e7c357" : rpc error: code = Internal desc = Could not attach volume "vol-004fb583edd2a9e29" to node "i-0ede337f3f46589a5": attachment of disk "vol-004fb583edd2a9e29" failed, expected device to be attached but was attaching
Sep 26 20:50:33.721: INFO: At 2021-09-26 20:45:37 +0000 UTC - event for pod-43053679-89e8-4c9f-b799-d9b16001d606: {kubelet ip-172-20-32-24.eu-west-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume1], unattached volumes=[kube-api-access-bxxvg volume1]: timed out waiting for the condition
Sep 26 20:50:33.826: INFO: POD  NODE  PHASE  GRACE  CONDITIONS
Sep 26 20:50:33.826: INFO: 
Sep 26 20:50:33.933: INFO: 
Logging node info for node ip-172-20-32-228.eu-west-1.compute.internal
Sep 26 20:50:34.039: INFO: Node Info: &Node{ObjectMeta:{ip-172-20-32-228.eu-west-1.compute.internal    03d8b477-261c-4e50-9efe-36ddf3b977f4 16057 0 2021-09-26 20:37:31 +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:eu-west-1 failure-domain.beta.kubernetes.io/zone:eu-west-1a kops.k8s.io/instancegroup:nodes-eu-west-1a kubernetes.io/arch:amd64 kubernetes.io/hostname:ip-172-20-32-228.eu-west-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:eu-west-1a topology.kubernetes.io/region:eu-west-1 topology.kubernetes.io/zone:eu-west-1a] map[csi.volume.kubernetes.io/nodeid:{"ebs.csi.aws.com":"i-06820b72c8819710e"} node.alpha.kubernetes.io/ttl:0 projectcalico.org/IPv4Address:172.20.32.228/19 projectcalico.org/IPv4IPIPTunnelAddr:100.115.134.192 volumes.kubernetes.io/controller-managed-attach-detach:true] [] []  [{kops-controller Update v1 2021-09-26 20:37:31 +0000 UTC FieldsV1 {"f:metadata":{"f:labels":{"f:kops.k8s.io/instancegroup":{},"f:kubernetes.io/role":{},"f:node-role.kubernetes.io/node":{}}}}} {kubelet Update v1 2021-09-26 20:37:31 +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":{}}}} {kube-controller-manager Update v1 2021-09-26 20:37:36 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"100.96.3.0/24\"":{}}}}} {calico-node Update v1 2021-09-26 20:37: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-09-26 20:50:32 +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.3.0/24,DoNotUseExternalID:,ProviderID:aws:///eu-west-1a/i-06820b72c8819710e,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[100.96.3.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-09-26 20:37:48 +0000 UTC,LastTransitionTime:2021-09-26 20:37:48 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2021-09-26 20:50:32 +0000 UTC,LastTransitionTime:2021-09-26 20:37:31 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2021-09-26 20:50:32 +0000 UTC,LastTransitionTime:2021-09-26 20:37:31 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2021-09-26 20:50:32 +0000 UTC,LastTransitionTime:2021-09-26 20:37:31 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2021-09-26 20:50:32 +0000 UTC,LastTransitionTime:2021-09-26 20:37:41 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:172.20.32.228,},NodeAddress{Type:ExternalIP,Address:63.33.56.83,},NodeAddress{Type:Hostname,Address:ip-172-20-32-228.eu-west-1.compute.internal,},NodeAddress{Type:InternalDNS,Address:ip-172-20-32-228.eu-west-1.compute.internal,},NodeAddress{Type:ExternalDNS,Address:ec2-63-33-56-83.eu-west-1.compute.amazonaws.com,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:ec202d2b7caa677e1f190a948f3ba88b,SystemUUID:ec202d2b-7caa-677e-1f19-0a948f3ba88b,BootID:462a37e5-11ca-45ac-9750-c5a90f55c524,KernelVersion:5.11.0-1017-aws,OSImage:Ubuntu 20.04.3 LTS,ContainerRuntimeVersion:containerd://1.4.9,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:732da7df530f4ad1923a7c71b927b0d964e596c622de68c1c6179fb7148704fd k8s.gcr.io/provider-aws/aws-ebs-csi-driver:v1.2.1],SizeBytes:66930652,},ContainerImage{Names:[docker.io/calico/node@sha256:cf8ecfef7efd119fbcc491857005ebcca20acbd06ad98416b5bd876d816238e3 docker.io/calico/node:v3.20.1],SizeBytes:57679520,},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:d09c2db1ad87dbe3b1e08ef7300e689c914ad4caae699441c72179e72076bc78 docker.io/calico/cni:v3.20.1],SizeBytes:48389221,},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:a173b89decb2bfd5e7cba0acac15d2035008df67e3c52b1f3bd388c284a95917 docker.io/calico/pod2daemon-flexvol:v3.20.1],SizeBytes:9359088,},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,},}
... skipping 163 lines ...
    [Testpattern: Dynamic PV (block volmode)(allowExpansion)] volume-expand
    /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should resize volume when PVC is edited while pod is using it [It]
      /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volume_expand.go:246

      While creating pods for resizing
      Unexpected error:
          <*errors.errorString | 0xc000c5aee0>: {
              s: "pod \"pod-43053679-89e8-4c9f-b799-d9b16001d606\" is not Running: timed out waiting for the condition",
          }
          pod "pod-43053679-89e8-4c9f-b799-d9b16001d606" is not Running: timed out waiting for the condition
      occurred

... skipping 229 lines ...
Sep 26 20:47:30.331: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Sep 26 20:47:31.019: INFO: Successfully created a new PD: "aws://eu-west-1a/vol-06d0cfe161bcce58e".
Sep 26 20:47:31.019: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-x82d
STEP: Creating a pod to test exec-volume-test
Sep 26 20:47:31.131: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-x82d" in namespace "volume-948" to be "Succeeded or Failed"
Sep 26 20:47:31.237: INFO: Pod "exec-volume-test-inlinevolume-x82d": Phase="Pending", Reason="", readiness=false. Elapsed: 106.297841ms
Sep 26 20:47:33.344: INFO: Pod "exec-volume-test-inlinevolume-x82d": Phase="Pending", Reason="", readiness=false. Elapsed: 2.213318313s
Sep 26 20:47:35.451: INFO: Pod "exec-volume-test-inlinevolume-x82d": Phase="Pending", Reason="", readiness=false. Elapsed: 4.320397416s
Sep 26 20:47:37.560: INFO: Pod "exec-volume-test-inlinevolume-x82d": Phase="Pending", Reason="", readiness=false. Elapsed: 6.429422837s
Sep 26 20:47:39.667: INFO: Pod "exec-volume-test-inlinevolume-x82d": Phase="Pending", Reason="", readiness=false. Elapsed: 8.536408213s
Sep 26 20:47:41.775: INFO: Pod "exec-volume-test-inlinevolume-x82d": Phase="Pending", Reason="", readiness=false. Elapsed: 10.644154269s
... skipping 131 lines ...
Sep 26 20:52:20.035: INFO: Pod "exec-volume-test-inlinevolume-x82d": Phase="Pending", Reason="", readiness=false. Elapsed: 4m48.904309111s
Sep 26 20:52:22.144: INFO: Pod "exec-volume-test-inlinevolume-x82d": Phase="Pending", Reason="", readiness=false. Elapsed: 4m51.013057448s
Sep 26 20:52:24.251: INFO: Pod "exec-volume-test-inlinevolume-x82d": Phase="Pending", Reason="", readiness=false. Elapsed: 4m53.120443258s
Sep 26 20:52:26.359: INFO: Pod "exec-volume-test-inlinevolume-x82d": Phase="Pending", Reason="", readiness=false. Elapsed: 4m55.228098775s
Sep 26 20:52:28.466: INFO: Pod "exec-volume-test-inlinevolume-x82d": Phase="Pending", Reason="", readiness=false. Elapsed: 4m57.335705632s
Sep 26 20:52:30.574: INFO: Pod "exec-volume-test-inlinevolume-x82d": Phase="Pending", Reason="", readiness=false. Elapsed: 4m59.443737858s
Sep 26 20:52:32.796: INFO: Failed to get logs from node "ip-172-20-32-24.eu-west-1.compute.internal" pod "exec-volume-test-inlinevolume-x82d" container "exec-container-inlinevolume-x82d": the server rejected our request for an unknown reason (get pods exec-volume-test-inlinevolume-x82d)
STEP: delete the pod
Sep 26 20:52:32.904: INFO: Waiting for pod exec-volume-test-inlinevolume-x82d to disappear
Sep 26 20:52:33.011: INFO: Pod exec-volume-test-inlinevolume-x82d still exists
Sep 26 20:52:35.011: INFO: Waiting for pod exec-volume-test-inlinevolume-x82d to disappear
Sep 26 20:52:35.118: INFO: Pod exec-volume-test-inlinevolume-x82d still exists
Sep 26 20:52:37.012: INFO: Waiting for pod exec-volume-test-inlinevolume-x82d to disappear
... skipping 87 lines ...
Sep 26 20:54:05.011: INFO: Waiting for pod exec-volume-test-inlinevolume-x82d to disappear
Sep 26 20:54:05.118: INFO: Pod exec-volume-test-inlinevolume-x82d still exists
Sep 26 20:54:07.012: INFO: Waiting for pod exec-volume-test-inlinevolume-x82d to disappear
Sep 26 20:54:07.119: INFO: Pod exec-volume-test-inlinevolume-x82d still exists
Sep 26 20:54:09.012: INFO: Waiting for pod exec-volume-test-inlinevolume-x82d to disappear
Sep 26 20:54:09.119: INFO: Pod exec-volume-test-inlinevolume-x82d no longer exists
Sep 26 20:54:09.784: INFO: Couldn't delete PD "aws://eu-west-1a/vol-06d0cfe161bcce58e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-06d0cfe161bcce58e is currently attached to i-0ede337f3f46589a5
	status code: 400, request id: 0b730a91-8e63-43b0-a9d9-52d7f9a3ea4b
Sep 26 20:54:15.374: INFO: Couldn't delete PD "aws://eu-west-1a/vol-06d0cfe161bcce58e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-06d0cfe161bcce58e is currently attached to i-0ede337f3f46589a5
	status code: 400, request id: c0c3978b-d169-48b4-86c9-66542c8a4441
Sep 26 20:54:21.000: INFO: Successfully deleted PD "aws://eu-west-1a/vol-06d0cfe161bcce58e".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
STEP: Collecting events from namespace "volume-948".
STEP: Found 5 events.
Sep 26 20:54:21.107: INFO: At 2021-09-26 20:47:31 +0000 UTC - event for exec-volume-test-inlinevolume-x82d: {default-scheduler } Scheduled: Successfully assigned volume-948/exec-volume-test-inlinevolume-x82d to ip-172-20-32-24.eu-west-1.compute.internal
Sep 26 20:54:21.107: INFO: At 2021-09-26 20:47:32 +0000 UTC - event for exec-volume-test-inlinevolume-x82d: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "ebs.csi.aws.com-vol-06d0cfe161bcce58e" : rpc error: code = Internal desc = Could not attach volume "vol-06d0cfe161bcce58e" to node "i-0ede337f3f46589a5": could not attach volume "vol-06d0cfe161bcce58e" to node "i-0ede337f3f46589a5": IncorrectState: vol-06d0cfe161bcce58e is not 'available'.
	status code: 400, request id: 02953ade-ee51-443d-b9ea-caee10d39321
Sep 26 20:54:21.107: INFO: At 2021-09-26 20:47:50 +0000 UTC - event for exec-volume-test-inlinevolume-x82d: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "ebs.csi.aws.com-vol-06d0cfe161bcce58e" : rpc error: code = Internal desc = Could not attach volume "vol-06d0cfe161bcce58e" to node "i-0ede337f3f46589a5": attachment of disk "vol-06d0cfe161bcce58e" failed, expected device to be attached but was attaching
Sep 26 20:54:21.107: INFO: At 2021-09-26 20:49:34 +0000 UTC - event for exec-volume-test-inlinevolume-x82d: {kubelet ip-172-20-32-24.eu-west-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[vol1], unattached volumes=[vol1 kube-api-access-l5kvv]: timed out waiting for the condition
Sep 26 20:54:21.107: INFO: At 2021-09-26 20:51:50 +0000 UTC - event for exec-volume-test-inlinevolume-x82d: {kubelet ip-172-20-32-24.eu-west-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[vol1], unattached volumes=[kube-api-access-l5kvv vol1]: timed out waiting for the condition
Sep 26 20:54:21.214: INFO: POD  NODE  PHASE  GRACE  CONDITIONS
Sep 26 20:54:21.214: INFO: 
Sep 26 20:54:21.322: INFO: 
Logging node info for node ip-172-20-32-228.eu-west-1.compute.internal
... skipping 161 lines ...
  /tmp/kops.GDxjzwo8j/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (xfs)][Slow] volumes
    /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should allow exec of files on the volume [It]
      /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:196

      Unexpected error:
          <*errors.errorString | 0xc000e588b0>: {
              s: "expected pod \"exec-volume-test-inlinevolume-x82d\" success: Gave up after waiting 5m0s for pod \"exec-volume-test-inlinevolume-x82d\" to be \"Succeeded or Failed\"",
          }
          expected pod "exec-volume-test-inlinevolume-x82d" success: Gave up after waiting 5m0s for pod "exec-volume-test-inlinevolume-x82d" to be "Succeeded or Failed"
      occurred

      /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:742
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
... skipping 80 lines ...
STEP: Found 11 events.
Sep 26 20:58:24.095: INFO: At 2021-09-26 20:48:21 +0000 UTC - event for awsm2dhc: {persistentvolume-controller } WaitForFirstConsumer: waiting for first consumer to be created before binding
Sep 26 20:58:24.095: INFO: At 2021-09-26 20:48:21 +0000 UTC - event for awsm2dhc: {persistentvolume-controller } ExternalProvisioning: waiting for a volume to be created, either by external provisioner "ebs.csi.aws.com" or manually created by system administrator
Sep 26 20:58:24.095: INFO: At 2021-09-26 20:48:21 +0000 UTC - event for awsm2dhc: {ebs.csi.aws.com_ebs-csi-controller-564bc97466-sh5rd_7b36448d-4594-4fe3-a232-822f90cd0b9a } Provisioning: External provisioner is provisioning volume for claim "fsgroupchangepolicy-9225/awsm2dhc"
Sep 26 20:58:24.095: INFO: At 2021-09-26 20:48:25 +0000 UTC - event for awsm2dhc: {ebs.csi.aws.com_ebs-csi-controller-564bc97466-sh5rd_7b36448d-4594-4fe3-a232-822f90cd0b9a } ProvisioningSucceeded: Successfully provisioned volume pvc-35235212-ee18-4757-b949-6df9d022994c
Sep 26 20:58:24.095: INFO: At 2021-09-26 20:48:25 +0000 UTC - event for pod-2626ae05-021b-41b8-9f4b-4d7e524fcdf6: {default-scheduler } Scheduled: Successfully assigned fsgroupchangepolicy-9225/pod-2626ae05-021b-41b8-9f4b-4d7e524fcdf6 to ip-172-20-32-24.eu-west-1.compute.internal
Sep 26 20:58:24.095: INFO: At 2021-09-26 20:48:41 +0000 UTC - event for pod-2626ae05-021b-41b8-9f4b-4d7e524fcdf6: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-35235212-ee18-4757-b949-6df9d022994c" : rpc error: code = Internal desc = Could not attach volume "vol-024baece95d1adbd8" to node "i-0ede337f3f46589a5": attachment of disk "vol-024baece95d1adbd8" failed, expected device to be attached but was attaching
Sep 26 20:58:24.095: INFO: At 2021-09-26 20:50:29 +0000 UTC - event for pod-2626ae05-021b-41b8-9f4b-4d7e524fcdf6: {kubelet ip-172-20-32-24.eu-west-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume1], unattached volumes=[volume1 kube-api-access-ssfcl]: timed out waiting for the condition
Sep 26 20:58:24.095: INFO: At 2021-09-26 20:52:56 +0000 UTC - event for pod-2626ae05-021b-41b8-9f4b-4d7e524fcdf6: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-35235212-ee18-4757-b949-6df9d022994c" 
Sep 26 20:58:24.095: INFO: At 2021-09-26 20:54:40 +0000 UTC - event for pod-2626ae05-021b-41b8-9f4b-4d7e524fcdf6: {kubelet ip-172-20-32-24.eu-west-1.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" already present on machine
Sep 26 20:58:24.095: INFO: At 2021-09-26 20:54:40 +0000 UTC - event for pod-2626ae05-021b-41b8-9f4b-4d7e524fcdf6: {kubelet ip-172-20-32-24.eu-west-1.compute.internal} Created: Created container write-pod
Sep 26 20:58:24.095: INFO: At 2021-09-26 20:54:40 +0000 UTC - event for pod-2626ae05-021b-41b8-9f4b-4d7e524fcdf6: {kubelet ip-172-20-32-24.eu-west-1.compute.internal} Started: Started container write-pod
Sep 26 20:58:24.199: INFO: POD                                       NODE                                        PHASE    GRACE  CONDITIONS
... skipping 165 lines ...
  /tmp/kops.GDxjzwo8j/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
    /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      (Always)[LinuxOnly], pod created with an initial fsgroup, new pod fsgroup applied to volume contents [It]
      /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/fsgroupchangepolicy.go:208

      Unexpected error:
          <*errors.errorString | 0xc000c33f60>: {
              s: "pod \"pod-2626ae05-021b-41b8-9f4b-4d7e524fcdf6\" is not Running: timed out waiting for the condition",
          }
          pod "pod-2626ae05-021b-41b8-9f4b-4d7e524fcdf6" is not Running: timed out waiting for the condition
      occurred

... skipping 13 lines ...
Sep 26 20:44:17.894: INFO: Deleting pod "inline-volume-xthzv" in namespace "ephemeral-3963"
Sep 26 20:44:18.000: INFO: Wait up to 5m0s for pod "inline-volume-xthzv" to be fully deleted
Sep 26 20:44:18.106: INFO: Creating resource for dynamic PV
Sep 26 20:44:18.106: INFO: Using claimSize:1Gi, test suite supported size:{ }, driver(aws) supported size:{ } 
STEP: creating a StorageClass ephemeral-3963gwt6w
STEP: checking the requested inline volume exists in the pod running on node {Name: Selector:map[] Affinity:nil}
Sep 26 20:59:18.747: INFO: Error getting logs for pod inline-volume-tester-q2nqh: the server rejected our request for an unknown reason (get pods inline-volume-tester-q2nqh)
Sep 26 20:59:19.065: INFO: Deleting pod "inline-volume-tester-q2nqh" in namespace "ephemeral-3963"
Sep 26 20:59:19.171: INFO: Wait up to 5m0s for pod "inline-volume-tester-q2nqh" to be fully deleted
Sep 26 21:00:15.383: INFO: Wait up to 5m0s for pod PV pvc-6a24eb71-df63-47fb-9159-5b23e17f59e8 to be fully deleted
Sep 26 21:00:15.383: INFO: Waiting up to 5m0s for PersistentVolume pvc-6a24eb71-df63-47fb-9159-5b23e17f59e8 to get deleted
Sep 26 21:00:15.489: INFO: PersistentVolume pvc-6a24eb71-df63-47fb-9159-5b23e17f59e8 found and phase=Released (105.921143ms)
Sep 26 21:00:20.595: INFO: PersistentVolume pvc-6a24eb71-df63-47fb-9159-5b23e17f59e8 found and phase=Released (5.212135407s)
... skipping 16 lines ...
Sep 26 21:00:31.128: INFO: At 2021-09-26 20:44:19 +0000 UTC - event for inline-volume-tester-q2nqh-my-volume-0: {persistentvolume-controller } ExternalProvisioning: waiting for a volume to be created, either by external provisioner "ebs.csi.aws.com" or manually created by system administrator
Sep 26 21:00:31.128: INFO: At 2021-09-26 20:44:19 +0000 UTC - event for inline-volume-tester-q2nqh-my-volume-1: {persistentvolume-controller } ExternalProvisioning: waiting for a volume to be created, either by external provisioner "ebs.csi.aws.com" or manually created by system administrator
Sep 26 21:00:31.128: INFO: At 2021-09-26 20:44:19 +0000 UTC - event for inline-volume-tester-q2nqh-my-volume-1: {ebs.csi.aws.com_ebs-csi-controller-564bc97466-sh5rd_7b36448d-4594-4fe3-a232-822f90cd0b9a } Provisioning: External provisioner is provisioning volume for claim "ephemeral-3963/inline-volume-tester-q2nqh-my-volume-1"
Sep 26 21:00:31.128: INFO: At 2021-09-26 20:44:23 +0000 UTC - event for inline-volume-tester-q2nqh: {default-scheduler } Scheduled: Successfully assigned ephemeral-3963/inline-volume-tester-q2nqh to ip-172-20-32-24.eu-west-1.compute.internal
Sep 26 21:00:31.128: INFO: At 2021-09-26 20:44:23 +0000 UTC - event for inline-volume-tester-q2nqh-my-volume-0: {ebs.csi.aws.com_ebs-csi-controller-564bc97466-sh5rd_7b36448d-4594-4fe3-a232-822f90cd0b9a } ProvisioningSucceeded: Successfully provisioned volume pvc-6a24eb71-df63-47fb-9159-5b23e17f59e8
Sep 26 21:00:31.128: INFO: At 2021-09-26 20:44:23 +0000 UTC - event for inline-volume-tester-q2nqh-my-volume-1: {ebs.csi.aws.com_ebs-csi-controller-564bc97466-sh5rd_7b36448d-4594-4fe3-a232-822f90cd0b9a } ProvisioningSucceeded: Successfully provisioned volume pvc-853f3e60-72e0-4944-a84b-6d116c5c3414
Sep 26 21:00:31.128: INFO: At 2021-09-26 20:44:42 +0000 UTC - event for inline-volume-tester-q2nqh: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-853f3e60-72e0-4944-a84b-6d116c5c3414" : rpc error: code = Internal desc = Could not attach volume "vol-0c5e1df810cc3a56f" to node "i-0ede337f3f46589a5": attachment of disk "vol-0c5e1df810cc3a56f" failed, expected device to be attached but was attaching
Sep 26 21:00:31.128: INFO: At 2021-09-26 20:44:42 +0000 UTC - event for inline-volume-tester-q2nqh: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-6a24eb71-df63-47fb-9159-5b23e17f59e8" : rpc error: code = Internal desc = Could not attach volume "vol-0a42d19cc79b5bae0" to node "i-0ede337f3f46589a5": attachment of disk "vol-0a42d19cc79b5bae0" failed, expected device to be attached but was attaching
Sep 26 21:00:31.128: INFO: At 2021-09-26 20:46:26 +0000 UTC - event for inline-volume-tester-q2nqh: {kubelet ip-172-20-32-24.eu-west-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[my-volume-0 my-volume-1], unattached volumes=[my-volume-0 my-volume-1 kube-api-access-9kqvg]: timed out waiting for the condition
Sep 26 21:00:31.128: INFO: At 2021-09-26 20:48:57 +0000 UTC - event for inline-volume-tester-q2nqh: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-853f3e60-72e0-4944-a84b-6d116c5c3414" 
Sep 26 21:00:31.128: INFO: At 2021-09-26 20:51:01 +0000 UTC - event for inline-volume-tester-q2nqh: {kubelet ip-172-20-32-24.eu-west-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[my-volume-0], unattached volumes=[my-volume-1 kube-api-access-9kqvg my-volume-0]: timed out waiting for the condition
Sep 26 21:00:31.128: INFO: At 2021-09-26 20:53:19 +0000 UTC - event for inline-volume-tester-q2nqh: {kubelet ip-172-20-32-24.eu-west-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[my-volume-0], unattached volumes=[my-volume-0 my-volume-1 kube-api-access-9kqvg]: timed out waiting for the condition
Sep 26 21:00:31.128: INFO: At 2021-09-26 20:55:37 +0000 UTC - event for inline-volume-tester-q2nqh: {kubelet ip-172-20-32-24.eu-west-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[my-volume-0], unattached volumes=[kube-api-access-9kqvg my-volume-0 my-volume-1]: timed out waiting for the condition
Sep 26 21:00:31.233: INFO: POD  NODE  PHASE  GRACE  CONDITIONS
... skipping 161 lines ...
    [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral
    /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should support multiple inline ephemeral volumes [It]
      /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/ephemeral.go:211

      waiting for pod with inline volume
      Unexpected error:
          <*errors.errorString | 0xc0002120d0>: {
              s: "timed out waiting for the condition",
          }
          timed out waiting for the condition
      occurred

... skipping 418 lines ...
  /tmp/kops.GDxjzwo8j/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
    /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should access to two volumes with the same volume mode and retain data across pod recreation on different node [LinuxOnly] [It]
      /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/multivolume.go:164

      Unexpected error:
          <*errors.errorString | 0xc000e956c0>: {
              s: "pod \"pod-4e4ae09f-252c-4add-bef2-d25d06e1ec92\" was not deleted: timed out waiting for the condition",
          }
          pod "pod-4e4ae09f-252c-4add-bef2-d25d06e1ec92" was not deleted: timed out waiting for the condition
      occurred

... skipping 252 lines ...
Sep 26 21:33:16.504: INFO: At 2021-09-26 20:43:23 +0000 UTC - event for pod-0a3175be-c8ce-4929-886f-f0ac16cfa8a1: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-3b78b15d-9d84-4c31-91f4-275d0e216168" 
Sep 26 21:33:16.504: INFO: At 2021-09-26 20:43:23 +0000 UTC - event for pod-0a3175be-c8ce-4929-886f-f0ac16cfa8a1: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-010398db-04eb-4d9c-9339-20eee1150bac" 
Sep 26 21:33:16.504: INFO: At 2021-09-26 20:43:24 +0000 UTC - event for pod-0a3175be-c8ce-4929-886f-f0ac16cfa8a1: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-5f9cc5af-0a9d-47b4-8d5f-6cbdaed62278" 
Sep 26 21:33:16.504: INFO: At 2021-09-26 20:43:25 +0000 UTC - event for pod-0a3175be-c8ce-4929-886f-f0ac16cfa8a1: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-d512360e-4e7e-4765-b2e2-c491ae00a4de" 
Sep 26 21:33:16.504: INFO: At 2021-09-26 20:43:26 +0000 UTC - event for pod-0a3175be-c8ce-4929-886f-f0ac16cfa8a1: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-e89522cc-625e-4c12-a317-5769dc975fd4" 
Sep 26 21:33:16.504: INFO: At 2021-09-26 20:43:27 +0000 UTC - event for pod-0a3175be-c8ce-4929-886f-f0ac16cfa8a1: {attachdetach-controller } SuccessfulAttachVolume: (combined from similar events): AttachVolume.Attach succeeded for volume "pvc-7237293b-d554-4602-bdc4-368b714ada33" 
Sep 26 21:33:16.504: INFO: At 2021-09-26 20:43:45 +0000 UTC - event for pod-0a3175be-c8ce-4929-886f-f0ac16cfa8a1: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-486467cb-9aaa-4029-8ab1-1023617a84fb" : rpc error: code = DeadlineExceeded desc = context deadline exceeded
Sep 26 21:33:16.504: INFO: At 2021-09-26 20:43:45 +0000 UTC - event for pod-0a3175be-c8ce-4929-886f-f0ac16cfa8a1: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-9149aa76-d599-4e24-837f-5d40c9312147" : rpc error: code = DeadlineExceeded desc = context deadline exceeded
Sep 26 21:33:16.504: INFO: At 2021-09-26 20:43:54 +0000 UTC - event for pod-0a3175be-c8ce-4929-886f-f0ac16cfa8a1: {attachdetach-controller } FailedAttachVolume: (combined from similar events): AttachVolume.Attach failed for volume "pvc-486467cb-9aaa-4029-8ab1-1023617a84fb" : rpc error: code = Internal desc = Could not attach volume "vol-03d8128697a942dfd" to node "i-0ede337f3f46589a5": attachment of disk "vol-03d8128697a942dfd" failed, expected device to be attached but was attaching
Sep 26 21:33:16.504: INFO: At 2021-09-26 20:45:18 +0000 UTC - event for pod-0a3175be-c8ce-4929-886f-f0ac16cfa8a1: {kubelet ip-172-20-32-24.eu-west-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume29 volume17 volume1 volume26 volume9 volume24 volume4 volume32 volume22 volume39 volume18 volume6 volume35 volume38 volume19 volume37], unattached volumes=[volume29 volume30 volume11 volume17 volume1 volume26 volume9 volume23 volume25 volume24 volume34 volume12 volume27 volume4 volume32 volume16 volume22 volume8 volume20 volume39 volume18 volume31 volume15 volume14 volume7 volume33 volume2 volume28 volume6 volume10 volume5 volume35 volume3 volume13 volume21 volume38 volume19 volume36 kube-api-access-6zlf4 volume37]: timed out waiting for the condition
Sep 26 21:33:16.504: INFO: At 2021-09-26 20:47:35 +0000 UTC - event for pod-0a3175be-c8ce-4929-886f-f0ac16cfa8a1: {kubelet ip-172-20-32-24.eu-west-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume39 volume32 volume37 volume1 volume17 volume9 volume18 volume22 volume24 volume29 volume6 volume38 volume19 volume26 volume4 volume35], unattached volumes=[volume39 volume25 volume30 volume33 volume2 volume15 volume7 volume27 volume32 volume37 volume13 volume20 volume1 volume8 volume17 volume9 volume18 volume22 volume14 volume31 volume5 volume24 volume21 volume28 volume16 volume29 volume6 volume38 volume10 volume34 kube-api-access-6zlf4 volume19 volume26 volume4 volume11 volume12 volume23 volume36 volume3 volume35]: timed out waiting for the condition
Sep 26 21:33:16.504: INFO: At 2021-09-26 20:49:51 +0000 UTC - event for pod-0a3175be-c8ce-4929-886f-f0ac16cfa8a1: {kubelet ip-172-20-32-24.eu-west-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume18 volume35 volume32 volume4 volume26 volume37 volume29 volume19 volume39 volume6 volume22 volume38 volume24 volume1 volume17 volume9], unattached volumes=[volume18 volume35 volume13 volume28 volume27 kube-api-access-6zlf4 volume21 volume12 volume32 volume36 volume4 volume26 volume37 volume25 volume11 volume29 volume2 volume20 volume15 volume5 volume34 volume10 volume7 volume8 volume19 volume39 volume6 volume23 volume30 volume22 volume31 volume3 volume38 volume24 volume33 volume16 volume1 volume17 volume14 volume9]: timed out waiting for the condition
Sep 26 21:33:16.504: INFO: At 2021-09-26 20:52:07 +0000 UTC - event for pod-0a3175be-c8ce-4929-886f-f0ac16cfa8a1: {kubelet ip-172-20-32-24.eu-west-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume18 volume32 volume39 volume29 volume19 volume4 volume17 volume9 volume6 volume1 volume26 volume22 volume35 volume24 volume37 volume38], unattached volumes=[volume10 volume18 volume32 volume39 volume29 volume19 volume27 volume4 volume3 volume20 volume17 volume36 volume34 volume8 kube-api-access-6zlf4 volume9 volume13 volume15 volume23 volume6 volume1 volume25 volume31 volume7 volume26 volume11 volume21 volume2 volume16 volume22 volume35 volume12 volume24 volume5 volume37 volume33 volume14 volume38 volume28 volume30]: timed out waiting for the condition
Sep 26 21:33:16.504: INFO: At 2021-09-26 20:54:21 +0000 UTC - event for pod-0a3175be-c8ce-4929-886f-f0ac16cfa8a1: {kubelet ip-172-20-32-24.eu-west-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume9 volume37 volume35 volume18 volume24 volume4 volume17 volume26 volume1 volume6 volume32 volume39 volume29 volume22 volume38 volume19], unattached volumes=[volume20 volume9 volume37 volume35 volume18 volume24 volume4 volume21 volume34 volume31 volume11 volume17 volume26 volume10 volume1 volume6 volume32 volume8 volume23 volume36 volume39 volume27 volume29 volume12 volume22 volume25 kube-api-access-6zlf4 volume13 volume5 volume30 volume38 volume15 volume33 volume19 volume7 volume2 volume28 volume3 volume14 volume16]: timed out waiting for the condition
Sep 26 21:33:16.504: INFO: At 2021-09-26 20:56:10 +0000 UTC - event for pod-0a3175be-c8ce-4929-886f-f0ac16cfa8a1: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-486467cb-9aaa-4029-8ab1-1023617a84fb" : rpc error: code = Internal desc = Could not attach volume "vol-03d8128697a942dfd" to node "i-0ede337f3f46589a5": attachment of disk "vol-03d8128697a942dfd" failed, expected device to be attached but was attaching
Sep 26 21:33:16.504: INFO: At 2021-09-26 20:56:37 +0000 UTC - event for pod-0a3175be-c8ce-4929-886f-f0ac16cfa8a1: {kubelet ip-172-20-32-24.eu-west-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume1 volume22 volume19 volume39 volume35 volume38 volume37 volume6 volume26 volume4 volume9 volume17 volume32 volume18 volume24], unattached volumes=[volume1 volume22 volume2 volume10 volume19 volume39 volume35 volume38 volume37 volume3 volume6 volume26 volume4 volume23 kube-api-access-6zlf4 volume25 volume34 volume21 volume9 volume30 volume17 volume36 volume20 volume27 volume31 volume32 volume18 volume24 volume15 volume14 volume11 volume16 volume8 volume28 volume13 volume12 volume33 volume29 volume5 volume7]: timed out waiting for the condition
Sep 26 21:33:16.504: INFO: At 2021-09-26 20:58:54 +0000 UTC - event for pod-0a3175be-c8ce-4929-886f-f0ac16cfa8a1: {kubelet ip-172-20-32-24.eu-west-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume38 volume26 volume6 volume24 volume18 volume37 volume9 volume17 volume4 volume32 volume39 volume35 volume1 volume19 volume22], unattached volumes=[volume3 volume38 volume26 kube-api-access-6zlf4 volume6 volume24 volume36 volume8 volume15 volume30 volume18 volume37 volume9 volume17 volume4 volume23 volume32 volume39 volume11 volume10 volume35 volume2 volume29 volume14 volume1 volume25 volume28 volume20 volume13 volume31 volume33 volume21 volume5 volume7 volume16 volume19 volume27 volume12 volume22 volume34]: timed out waiting for the condition
Sep 26 21:33:16.504: INFO: At 2021-09-26 21:01:10 +0000 UTC - event for pod-0a3175be-c8ce-4929-886f-f0ac16cfa8a1: {kubelet ip-172-20-32-24.eu-west-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume9 volume19 volume22 volume6 volume32 volume26 volume38 volume24 volume37 volume35 volume39 volume4 volume1 volume18 volume17], unattached volumes=[volume29 volume14 volume9 volume19 volume22 volume5 volume6 volume23 volume32 volume8 volume11 volume30 volume21 volume26 volume12 volume16 volume38 volume24 volume10 volume37 volume28 volume35 volume33 volume39 kube-api-access-6zlf4 volume4 volume1 volume18 volume27 volume34 volume2 volume31 volume17 volume13 volume7 volume15 volume36 volume25 volume3 volume20]: timed out waiting for the condition
Sep 26 21:33:16.504: INFO: At 2021-09-26 21:03:26 +0000 UTC - event for pod-0a3175be-c8ce-4929-886f-f0ac16cfa8a1: {kubelet ip-172-20-32-24.eu-west-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume9 volume22 volume4 volume38 volume24 volume1 volume35 volume18 volume6 volume37 volume17 volume39 volume19 volume26 volume32], unattached volumes=[volume36 volume28 volume30 volume12 volume29 volume23 volume33 volume9 volume3 volume15 volume22 kube-api-access-6zlf4 volume4 volume20 volume27 volume16 volume38 volume24 volume14 volume1 volume31 volume11 volume21 volume25 volume34 volume35 volume18 volume8 volume7 volume5 volume6 volume37 volume10 volume13 volume17 volume39 volume19 volume26 volume32 volume2]: timed out waiting for the condition
Sep 26 21:33:16.504: INFO: At 2021-09-26 21:05:42 +0000 UTC - event for pod-0a3175be-c8ce-4929-886f-f0ac16cfa8a1: {kubelet ip-172-20-32-24.eu-west-1.compute.internal} FailedMount: (combined from similar events): Unable to attach or mount volumes: unmounted volumes=[volume1 volume38 volume9 volume17 volume39 volume26 volume35 volume4 volume37 volume6 volume22 volume24 volume19], unattached volumes=[volume1 volume38 volume2 volume9 volume21 volume29 volume28 volume5 volume18 volume17 volume32 volume3 kube-api-access-6zlf4 volume13 volume39 volume10 volume36 volume16 volume23 volume25 volume7 volume26 volume12 volume27 volume15 volume35 volume8 volume31 volume11 volume4 volume14 volume37 volume33 volume6 volume22 volume30 volume34 volume20 volume24 volume19]: timed out waiting for the condition
Sep 26 21:33:16.610: INFO: POD                                       NODE                                        PHASE    GRACE  CONDITIONS
... skipping 159 lines ...
/tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (filesystem volmode)] volumeLimits
  /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should support volume limits [Serial] [It]
    /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumelimits.go:123

    Unexpected error:
        <*errors.errorString | 0xc0002140d0>: {
            s: "timed out waiting for the condition",
        }
        timed out waiting for the condition
    occurred

    /tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumelimits.go:202
------------------------------


Summarizing 7 Failures:

[Fail] [ebs-csi-migration] EBS CSI Migration [Driver: aws] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand [It] Verify if offline PVC expansion works 
/tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volume_expand.go:192

[Fail] [ebs-csi-migration] EBS CSI Migration [Driver: aws] [Testpattern: Dynamic PV (block volmode)(allowExpansion)] volume-expand [It] should resize volume when PVC is edited while pod is using it 
/tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volume_expand.go:264

[Fail] [ebs-csi-migration] EBS CSI Migration [Driver: aws] [Testpattern: Inline-volume (xfs)][Slow] volumes [It] should allow exec of files on the volume 
/tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:742

[Fail] [ebs-csi-migration] EBS CSI Migration [Driver: aws] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy [It] (Always)[LinuxOnly], pod created with an initial fsgroup, new pod fsgroup applied to volume contents 
/tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/fsgroupchangepolicy.go:250

[Fail] [ebs-csi-migration] EBS CSI Migration [Driver: aws] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral [It] should support multiple inline ephemeral volumes 
/tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/ephemeral.go:307

[Fail] [ebs-csi-migration] EBS CSI Migration [Driver: aws] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] [It] should access to two volumes with the same volume mode and retain data across pod recreation on different node [LinuxOnly] 
/tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/multivolume.go:417

[Fail] External Storage [Driver: ebs.csi.aws.com] [Testpattern: Dynamic PV (filesystem volmode)] volumeLimits [It] should support volume limits [Serial] 
/tmp/kops.GDxjzwo8j/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumelimits.go:202

Ran 140 of 485 Specs in 3107.086 seconds
FAIL! -- 133 Passed | 7 Failed | 0 Pending | 345 Skipped


Ginkgo ran 1 suite in 52m54.410286939s
Test Suite Failed
+ kops-finish
+ kubetest2 kops -v=2 --cloud-provider=aws --cluster-name=e2e-c3f2775103-c95b4.test-cncf-aws.k8s.io --kops-root=/home/prow/go/src/k8s.io/kops --admin-access= --env=KOPS_FEATURE_FLAGS=SpecOverrideFlag --kops-binary-path=/home/prow/go/src/k8s.io/kops/.bazelbuild/dist/linux/amd64/kops --down
I0926 21:33:21.786314   26172 app.go:59] RunDir for this run: "/logs/artifacts/3701040b-1f08-11ec-a3b0-9242b45c1669"
I0926 21:33:21.786503   26172 app.go:90] ID for this run: "3701040b-1f08-11ec-a3b0-9242b45c1669"
I0926 21:33:21.877285   26172 dumplogs.go:40] /home/prow/go/src/k8s.io/kops/.bazelbuild/dist/linux/amd64/kops toolbox dump --name e2e-c3f2775103-c95b4.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ubuntu
I0926 21:33:21.895962   26184 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
... skipping 2776 lines ...