This job view page is being replaced by Spyglass soon. Check out the new job view.
PRrifelpet: Upgrade EBS CSI Driver to v1.4.0
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-10-13 04:39
Elapsed41m43s
Revision13e1fef44a587d553120b45bfb11b5accdbb0a20
Refs 12529

No Test Failures!


Error lines from build-log.txt

... skipping 592 lines ...
I1013 04:45:37.020710   12572 app.go:90] ID for this run: "740c85ce-2bdf-11ec-b5e2-c6fa34815830"
I1013 04:45:37.042817   12572 up.go:43] Cleaning up any leaked resources from previous cluster
I1013 04:45:37.044209   12572 dumplogs.go:40] /home/prow/go/src/k8s.io/kops/.bazelbuild/dist/linux/amd64/kops toolbox dump --name e2e-b6f7c24027-45100.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ubuntu
I1013 04:45:37.063717   12583 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1013 04:45:37.063803   12583 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I1013 04:45:37.063807   12583 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Error: Cluster.kops.k8s.io "e2e-b6f7c24027-45100.test-cncf-aws.k8s.io" not found
W1013 04:45:37.529629   12572 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I1013 04:45:37.529679   12572 down.go:48] /home/prow/go/src/k8s.io/kops/.bazelbuild/dist/linux/amd64/kops delete cluster --name e2e-b6f7c24027-45100.test-cncf-aws.k8s.io --yes
I1013 04:45:37.549284   12593 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1013 04:45:37.549363   12593 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I1013 04:45:37.549368   12593 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-b6f7c24027-45100.test-cncf-aws.k8s.io" not found
I1013 04:45:38.007028   12572 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/13 04:45:38 failed to get external ip from metadata service: http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip returned 404
I1013 04:45:38.018062   12572 http.go:37] curl https://ip.jsb.workers.dev
I1013 04:45:38.130968   12572 up.go:144] /home/prow/go/src/k8s.io/kops/.bazelbuild/dist/linux/amd64/kops create cluster --name e2e-b6f7c24027-45100.test-cncf-aws.k8s.io --cloud aws --kubernetes-version 1.22.1 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --networking calico --override=cluster.spec.cloudConfig.awsEBSCSIDriver.enabled=true --override=cluster.spec.snapshotController.enabled=true --override=cluster.spec.certManager.enabled=true --admin-access 35.222.171.231/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones eu-west-2a --master-size c5.large
I1013 04:45:38.147761   12603 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1013 04:45:38.148109   12603 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I1013 04:45:38.148139   12603 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1013 04:45:38.169916   12603 create_cluster.go:838] Using SSH public key: /etc/aws-ssh/aws-ssh-public
... skipping 33 lines ...
I1013 04:46:04.388071   12572 up.go:181] /home/prow/go/src/k8s.io/kops/.bazelbuild/dist/linux/amd64/kops validate cluster --name e2e-b6f7c24027-45100.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I1013 04:46:04.406388   12623 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1013 04:46:04.406473   12623 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I1013 04:46:04.406478   12623 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-b6f7c24027-45100.test-cncf-aws.k8s.io

W1013 04:46:05.588347   12623 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-b6f7c24027-45100.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W1013 04:46:15.633601   12623 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-b6f7c24027-45100.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1013 04:46:25.672895   12623 validate_cluster.go:232] (will retry): cluster not yet healthy
W1013 04:46:35.690761   12623 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-b6f7c24027-45100.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W1013 04:46:45.751475   12623 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-b6f7c24027-45100.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1013 04:46:55.781562   12623 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1013 04:47:05.817701   12623 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1013 04:47:15.851153   12623 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1013 04:47:25.916945   12623 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1013 04:47:35.950073   12623 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1013 04:47:45.987966   12623 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1013 04:47:56.017027   12623 validate_cluster.go:232] (will retry): cluster not yet healthy
W1013 04:48:06.048763   12623 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-b6f7c24027-45100.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1013 04:48:16.080548   12623 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1013 04:48:26.109862   12623 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1013 04:48:36.142237   12623 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1013 04:48:46.171450   12623 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1013 04:48:56.202029   12623 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1013 04:49:06.246882   12623 validate_cluster.go:232] (will retry): cluster not yet healthy
W1013 04:49:16.275860   12623 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-b6f7c24027-45100.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1013 04:49:26.304482   12623 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 15 lines ...
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kztjg				system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kztjg" is pending
Pod	kube-system/ebs-csi-controller-54dc46fc7b-pnzr5				system-cluster-critical pod "ebs-csi-controller-54dc46fc7b-pnzr5" is pending
Pod	kube-system/ebs-csi-node-w4hnh						system-node-critical pod "ebs-csi-node-w4hnh" is pending
Pod	kube-system/ebs-csi-node-zw6hd						system-node-critical pod "ebs-csi-node-zw6hd" is pending
Pod	kube-system/kube-proxy-ip-172-20-53-241.eu-west-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-53-241.eu-west-2.compute.internal" is pending

Validation Failed
W1013 04:49:38.890615   12623 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 19 lines ...
Pod	kube-system/ebs-csi-node-5xhwj						system-node-critical pod "ebs-csi-node-5xhwj" is pending
Pod	kube-system/ebs-csi-node-qzvrs						system-node-critical pod "ebs-csi-node-qzvrs" is pending
Pod	kube-system/ebs-csi-node-w4hnh						system-node-critical pod "ebs-csi-node-w4hnh" is pending
Pod	kube-system/ebs-csi-node-zw6hd						system-node-critical pod "ebs-csi-node-zw6hd" is pending
Pod	kube-system/kube-proxy-ip-172-20-45-187.eu-west-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-45-187.eu-west-2.compute.internal" is pending

Validation Failed
W1013 04:49:50.646526   12623 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 18 lines ...
Pod	kube-system/coredns-6c8944dbdc-vzg9s		system-cluster-critical pod "coredns-6c8944dbdc-vzg9s" is pending
Pod	kube-system/ebs-csi-node-5xhwj			system-node-critical pod "ebs-csi-node-5xhwj" is pending
Pod	kube-system/ebs-csi-node-qzvrs			system-node-critical pod "ebs-csi-node-qzvrs" is pending
Pod	kube-system/ebs-csi-node-w2sh2			system-node-critical pod "ebs-csi-node-w2sh2" is pending
Pod	kube-system/ebs-csi-node-zw6hd			system-node-critical pod "ebs-csi-node-zw6hd" is pending

Validation Failed
W1013 04:50:02.593256   12623 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 10 lines ...
Pod	kube-system/calico-node-d27pd	system-node-critical pod "calico-node-d27pd" is pending
Pod	kube-system/calico-node-llkhl	system-node-critical pod "calico-node-llkhl" is not ready (calico-node)
Pod	kube-system/ebs-csi-node-5xhwj	system-node-critical pod "ebs-csi-node-5xhwj" is pending
Pod	kube-system/ebs-csi-node-qzvrs	system-node-critical pod "ebs-csi-node-qzvrs" is pending
Pod	kube-system/ebs-csi-node-w2sh2	system-node-critical pod "ebs-csi-node-w2sh2" is pending

Validation Failed
W1013 04:50:14.480127   12623 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME				MESSAGE
Pod	kube-system/calico-node-d27pd	system-node-critical pod "calico-node-d27pd" is not ready (calico-node)
Pod	kube-system/ebs-csi-node-w2sh2	system-node-critical pod "ebs-csi-node-w2sh2" is pending

Validation Failed
W1013 04:50:26.243257   12623 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 21 lines ...
ip-172-20-62-14.eu-west-2.compute.internal	node	True

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

Validation Failed
W1013 04:50:49.846122   12623 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 331 lines ...
Oct 13 04:55:18.573: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 444 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 04:55:18.755: 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.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Oct 13 04:55:21.274: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Oct 13 04:55:21.940: INFO: Successfully created a new PD: "aws://eu-west-2a/vol-01288f948f74ab525".
Oct 13 04:55:21.941: INFO: Creating resource for pre-provisioned PV
Oct 13 04:55:21.941: INFO: Creating PVC and PV
... skipping 8 lines ...
Oct 13 04:55:32.732: INFO: PersistentVolumeClaim pvc-j6k66 found but phase is Pending instead of Bound.
Oct 13 04:55:34.830: INFO: PersistentVolumeClaim pvc-j6k66 found but phase is Pending instead of Bound.
Oct 13 04:55:36.927: INFO: PersistentVolumeClaim pvc-j6k66 found and phase=Bound (14.789143713s)
Oct 13 04:55:36.927: INFO: Waiting up to 3m0s for PersistentVolume aws-jgzqr to have phase Bound
Oct 13 04:55:37.024: INFO: PersistentVolume aws-jgzqr found and phase=Bound (96.866337ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Oct 13 04:55:37.528: INFO: Deleting pod "pod-179f9029-7d6a-4dc0-b6c8-40580fab365a" in namespace "volumemode-5102"
Oct 13 04:55:37.626: INFO: Wait up to 5m0s for pod "pod-179f9029-7d6a-4dc0-b6c8-40580fab365a" to be fully deleted
STEP: Deleting pv and pvc
Oct 13 04:55:47.829: INFO: Deleting PersistentVolumeClaim "pvc-j6k66"
Oct 13 04:55:47.927: INFO: Deleting PersistentVolume "aws-jgzqr"
Oct 13 04:55:48.250: INFO: Successfully deleted PD "aws://eu-west-2a/vol-01288f948f74ab525".
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.2A194ozXw/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.2A194ozXw/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
    /tmp/kops.2A194ozXw/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.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [sig-storage] Volume Operations Storm [Feature:vsphere]
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 04:55:48.450: INFO: >>> kubeConfig: /root/.kube/config
... skipping 153 lines ...
Oct 13 04:55:19.868: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6991-e2e-scmpjf2
STEP: creating a claim
Oct 13 04:55:19.969: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-jn2j
STEP: Creating a pod to test subpath
Oct 13 04:55:20.269: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-jn2j" in namespace "provisioning-6991" to be "Succeeded or Failed"
Oct 13 04:55:20.365: INFO: Pod "pod-subpath-test-dynamicpv-jn2j": Phase="Pending", Reason="", readiness=false. Elapsed: 96.467472ms
Oct 13 04:55:22.463: INFO: Pod "pod-subpath-test-dynamicpv-jn2j": Phase="Pending", Reason="", readiness=false. Elapsed: 2.19426252s
Oct 13 04:55:24.562: INFO: Pod "pod-subpath-test-dynamicpv-jn2j": Phase="Pending", Reason="", readiness=false. Elapsed: 4.29342972s
Oct 13 04:55:26.660: INFO: Pod "pod-subpath-test-dynamicpv-jn2j": Phase="Pending", Reason="", readiness=false. Elapsed: 6.390828671s
Oct 13 04:55:28.757: INFO: Pod "pod-subpath-test-dynamicpv-jn2j": Phase="Pending", Reason="", readiness=false. Elapsed: 8.488557544s
Oct 13 04:55:30.855: INFO: Pod "pod-subpath-test-dynamicpv-jn2j": Phase="Pending", Reason="", readiness=false. Elapsed: 10.586554044s
Oct 13 04:55:32.953: INFO: Pod "pod-subpath-test-dynamicpv-jn2j": Phase="Pending", Reason="", readiness=false. Elapsed: 12.683984877s
Oct 13 04:55:35.051: INFO: Pod "pod-subpath-test-dynamicpv-jn2j": Phase="Pending", Reason="", readiness=false. Elapsed: 14.781718593s
Oct 13 04:55:37.150: INFO: Pod "pod-subpath-test-dynamicpv-jn2j": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.881602032s
STEP: Saw pod success
Oct 13 04:55:37.150: INFO: Pod "pod-subpath-test-dynamicpv-jn2j" satisfied condition "Succeeded or Failed"
Oct 13 04:55:37.248: INFO: Trying to get logs from node ip-172-20-53-241.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-jn2j container test-container-volume-dynamicpv-jn2j: <nil>
STEP: delete the pod
Oct 13 04:55:37.497: INFO: Waiting for pod pod-subpath-test-dynamicpv-jn2j to disappear
Oct 13 04:55:37.593: INFO: Pod pod-subpath-test-dynamicpv-jn2j no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-jn2j
Oct 13 04:55:37.594: INFO: Deleting pod "pod-subpath-test-dynamicpv-jn2j" in namespace "provisioning-6991"
... skipping 108 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 04:55:20.566: 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.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Oct 13 04:55:22.021: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 13 04:55:22.021: INFO: Creating resource for dynamic PV
Oct 13 04:55:22.021: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5714f6kl
STEP: creating a claim
Oct 13 04:55:22.119: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-6bsv
STEP: Checking for subpath error in container status
Oct 13 04:55:46.609: INFO: Deleting pod "pod-subpath-test-dynamicpv-6bsv" in namespace "provisioning-571"
Oct 13 04:55:46.707: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-6bsv" to be fully deleted
STEP: Deleting pod
Oct 13 04:55:52.900: INFO: Deleting pod "pod-subpath-test-dynamicpv-6bsv" in namespace "provisioning-571"
STEP: Deleting pvc
Oct 13 04:55:53.188: INFO: Deleting PersistentVolumeClaim "awsw7tcd"
... skipping 11 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.2A194ozXw/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.2A194ozXw/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.2A194ozXw/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.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow]
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Oct 13 04:55:58.775: INFO: Driver "ebs.csi.aws.com" does not support volume type "PreprovisionedPV" - skipping
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow]
... skipping 27 lines ...
Oct 13 04:55:22.129: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5624n7cdx
STEP: creating a claim
Oct 13 04:55:22.230: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-xqs6
STEP: Creating a pod to test subpath
Oct 13 04:55:22.521: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-xqs6" in namespace "provisioning-5624" to be "Succeeded or Failed"
Oct 13 04:55:22.617: INFO: Pod "pod-subpath-test-dynamicpv-xqs6": Phase="Pending", Reason="", readiness=false. Elapsed: 95.962633ms
Oct 13 04:55:24.714: INFO: Pod "pod-subpath-test-dynamicpv-xqs6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.192662263s
Oct 13 04:55:26.810: INFO: Pod "pod-subpath-test-dynamicpv-xqs6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.289171832s
Oct 13 04:55:28.908: INFO: Pod "pod-subpath-test-dynamicpv-xqs6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.386657783s
Oct 13 04:55:31.006: INFO: Pod "pod-subpath-test-dynamicpv-xqs6": Phase="Pending", Reason="", readiness=false. Elapsed: 8.485313409s
Oct 13 04:55:33.103: INFO: Pod "pod-subpath-test-dynamicpv-xqs6": Phase="Pending", Reason="", readiness=false. Elapsed: 10.581616431s
Oct 13 04:55:35.200: INFO: Pod "pod-subpath-test-dynamicpv-xqs6": Phase="Pending", Reason="", readiness=false. Elapsed: 12.679358951s
Oct 13 04:55:37.298: INFO: Pod "pod-subpath-test-dynamicpv-xqs6": Phase="Pending", Reason="", readiness=false. Elapsed: 14.777256195s
Oct 13 04:55:39.399: INFO: Pod "pod-subpath-test-dynamicpv-xqs6": Phase="Pending", Reason="", readiness=false. Elapsed: 16.878199136s
Oct 13 04:55:41.497: INFO: Pod "pod-subpath-test-dynamicpv-xqs6": Phase="Pending", Reason="", readiness=false. Elapsed: 18.975541599s
Oct 13 04:55:43.595: INFO: Pod "pod-subpath-test-dynamicpv-xqs6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.073793681s
STEP: Saw pod success
Oct 13 04:55:43.595: INFO: Pod "pod-subpath-test-dynamicpv-xqs6" satisfied condition "Succeeded or Failed"
Oct 13 04:55:43.691: INFO: Trying to get logs from node ip-172-20-53-241.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-xqs6 container test-container-subpath-dynamicpv-xqs6: <nil>
STEP: delete the pod
Oct 13 04:55:43.908: INFO: Waiting for pod pod-subpath-test-dynamicpv-xqs6 to disappear
Oct 13 04:55:44.016: INFO: Pod pod-subpath-test-dynamicpv-xqs6 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-xqs6
Oct 13 04:55:44.017: INFO: Deleting pod "pod-subpath-test-dynamicpv-xqs6" in namespace "provisioning-5624"
... skipping 57 lines ...
Oct 13 04:55:21.221: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1454wtjgh
STEP: creating a claim
Oct 13 04:55:21.318: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-dzkl
STEP: Creating a pod to test subpath
Oct 13 04:55:21.617: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-dzkl" in namespace "provisioning-1454" to be "Succeeded or Failed"
Oct 13 04:55:21.714: INFO: Pod "pod-subpath-test-dynamicpv-dzkl": Phase="Pending", Reason="", readiness=false. Elapsed: 96.949898ms
Oct 13 04:55:23.821: INFO: Pod "pod-subpath-test-dynamicpv-dzkl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.203975065s
Oct 13 04:55:25.917: INFO: Pod "pod-subpath-test-dynamicpv-dzkl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.300232428s
Oct 13 04:55:28.014: INFO: Pod "pod-subpath-test-dynamicpv-dzkl": Phase="Pending", Reason="", readiness=false. Elapsed: 6.397145059s
Oct 13 04:55:30.111: INFO: Pod "pod-subpath-test-dynamicpv-dzkl": Phase="Pending", Reason="", readiness=false. Elapsed: 8.494357007s
Oct 13 04:55:32.209: INFO: Pod "pod-subpath-test-dynamicpv-dzkl": Phase="Pending", Reason="", readiness=false. Elapsed: 10.591664284s
... skipping 5 lines ...
Oct 13 04:55:44.794: INFO: Pod "pod-subpath-test-dynamicpv-dzkl": Phase="Pending", Reason="", readiness=false. Elapsed: 23.176851148s
Oct 13 04:55:46.891: INFO: Pod "pod-subpath-test-dynamicpv-dzkl": Phase="Pending", Reason="", readiness=false. Elapsed: 25.274116935s
Oct 13 04:55:48.989: INFO: Pod "pod-subpath-test-dynamicpv-dzkl": Phase="Pending", Reason="", readiness=false. Elapsed: 27.372113666s
Oct 13 04:55:51.086: INFO: Pod "pod-subpath-test-dynamicpv-dzkl": Phase="Pending", Reason="", readiness=false. Elapsed: 29.469344962s
Oct 13 04:55:53.184: INFO: Pod "pod-subpath-test-dynamicpv-dzkl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 31.567397791s
STEP: Saw pod success
Oct 13 04:55:53.185: INFO: Pod "pod-subpath-test-dynamicpv-dzkl" satisfied condition "Succeeded or Failed"
Oct 13 04:55:53.281: INFO: Trying to get logs from node ip-172-20-48-140.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-dzkl container test-container-volume-dynamicpv-dzkl: <nil>
STEP: delete the pod
Oct 13 04:55:53.520: INFO: Waiting for pod pod-subpath-test-dynamicpv-dzkl to disappear
Oct 13 04:55:53.619: INFO: Pod pod-subpath-test-dynamicpv-dzkl no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-dzkl
Oct 13 04:55:53.619: INFO: Deleting pod "pod-subpath-test-dynamicpv-dzkl" in namespace "provisioning-1454"
... skipping 226 lines ...
Oct 13 04:56:08.217: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 41 lines ...
Oct 13 04:55:19.738: INFO: PersistentVolumeClaim pvc-fwchz found but phase is Pending instead of Bound.
Oct 13 04:55:21.834: INFO: PersistentVolumeClaim pvc-fwchz found and phase=Bound (2.193155s)
Oct 13 04:55:21.834: INFO: Waiting up to 3m0s for PersistentVolume aws-7dtdm to have phase Bound
Oct 13 04:55:21.940: INFO: PersistentVolume aws-7dtdm found and phase=Bound (105.629457ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-jzsv
STEP: Creating a pod to test exec-volume-test
Oct 13 04:55:22.234: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-jzsv" in namespace "volume-8359" to be "Succeeded or Failed"
Oct 13 04:55:22.330: INFO: Pod "exec-volume-test-preprovisionedpv-jzsv": Phase="Pending", Reason="", readiness=false. Elapsed: 96.144412ms
Oct 13 04:55:24.431: INFO: Pod "exec-volume-test-preprovisionedpv-jzsv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.196371834s
Oct 13 04:55:26.528: INFO: Pod "exec-volume-test-preprovisionedpv-jzsv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.293900425s
Oct 13 04:55:28.629: INFO: Pod "exec-volume-test-preprovisionedpv-jzsv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.39448041s
Oct 13 04:55:30.725: INFO: Pod "exec-volume-test-preprovisionedpv-jzsv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.490907266s
Oct 13 04:55:32.822: INFO: Pod "exec-volume-test-preprovisionedpv-jzsv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.587380812s
... skipping 4 lines ...
Oct 13 04:55:43.307: INFO: Pod "exec-volume-test-preprovisionedpv-jzsv": Phase="Pending", Reason="", readiness=false. Elapsed: 21.073106333s
Oct 13 04:55:45.406: INFO: Pod "exec-volume-test-preprovisionedpv-jzsv": Phase="Pending", Reason="", readiness=false. Elapsed: 23.171734539s
Oct 13 04:55:47.503: INFO: Pod "exec-volume-test-preprovisionedpv-jzsv": Phase="Pending", Reason="", readiness=false. Elapsed: 25.268474528s
Oct 13 04:55:49.600: INFO: Pod "exec-volume-test-preprovisionedpv-jzsv": Phase="Pending", Reason="", readiness=false. Elapsed: 27.365458323s
Oct 13 04:55:51.697: INFO: Pod "exec-volume-test-preprovisionedpv-jzsv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 29.463155308s
STEP: Saw pod success
Oct 13 04:55:51.698: INFO: Pod "exec-volume-test-preprovisionedpv-jzsv" satisfied condition "Succeeded or Failed"
Oct 13 04:55:51.794: INFO: Trying to get logs from node ip-172-20-62-14.eu-west-2.compute.internal pod exec-volume-test-preprovisionedpv-jzsv container exec-container-preprovisionedpv-jzsv: <nil>
STEP: delete the pod
Oct 13 04:55:51.998: INFO: Waiting for pod exec-volume-test-preprovisionedpv-jzsv to disappear
Oct 13 04:55:52.094: INFO: Pod exec-volume-test-preprovisionedpv-jzsv no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-jzsv
Oct 13 04:55:52.094: INFO: Deleting pod "exec-volume-test-preprovisionedpv-jzsv" in namespace "volume-8359"
STEP: Deleting pv and pvc
Oct 13 04:55:52.193: INFO: Deleting PersistentVolumeClaim "pvc-fwchz"
Oct 13 04:55:52.292: INFO: Deleting PersistentVolume "aws-7dtdm"
Oct 13 04:55:52.582: INFO: Couldn't delete PD "aws://eu-west-2a/vol-07827b8dd7e48ed9c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07827b8dd7e48ed9c is currently attached to i-0cd8e7c27c713b3cc
	status code: 400, request id: 6aeb082c-c45d-4196-a1ad-9f29aa24c7e6
Oct 13 04:55:58.101: INFO: Couldn't delete PD "aws://eu-west-2a/vol-07827b8dd7e48ed9c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07827b8dd7e48ed9c is currently attached to i-0cd8e7c27c713b3cc
	status code: 400, request id: 31c4a0d2-a9b9-4d13-b8f0-2753a55f9653
Oct 13 04:56:03.599: INFO: Couldn't delete PD "aws://eu-west-2a/vol-07827b8dd7e48ed9c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07827b8dd7e48ed9c is currently attached to i-0cd8e7c27c713b3cc
	status code: 400, request id: 7d8e94ff-3500-48d6-9be5-9f08d9251e15
Oct 13 04:56:09.133: INFO: Successfully deleted PD "aws://eu-west-2a/vol-07827b8dd7e48ed9c".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 04:56:09.133: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8359" for this suite.
... skipping 20 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.2A194ozXw/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.2A194ozXw/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.2A194ozXw/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.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 12 lines ...
Oct 13 04:55:21.674: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9059hz8mb
STEP: creating a claim
Oct 13 04:55:21.772: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-p6p6
STEP: Creating a pod to test subpath
Oct 13 04:55:22.076: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-p6p6" in namespace "provisioning-9059" to be "Succeeded or Failed"
Oct 13 04:55:22.174: INFO: Pod "pod-subpath-test-dynamicpv-p6p6": Phase="Pending", Reason="", readiness=false. Elapsed: 97.828045ms
Oct 13 04:55:24.272: INFO: Pod "pod-subpath-test-dynamicpv-p6p6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.196105857s
Oct 13 04:55:26.372: INFO: Pod "pod-subpath-test-dynamicpv-p6p6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.295739419s
Oct 13 04:55:28.471: INFO: Pod "pod-subpath-test-dynamicpv-p6p6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.394351135s
Oct 13 04:55:30.569: INFO: Pod "pod-subpath-test-dynamicpv-p6p6": Phase="Pending", Reason="", readiness=false. Elapsed: 8.492189443s
Oct 13 04:55:32.666: INFO: Pod "pod-subpath-test-dynamicpv-p6p6": Phase="Pending", Reason="", readiness=false. Elapsed: 10.589923032s
... skipping 2 lines ...
Oct 13 04:55:38.959: INFO: Pod "pod-subpath-test-dynamicpv-p6p6": Phase="Pending", Reason="", readiness=false. Elapsed: 16.882964569s
Oct 13 04:55:41.057: INFO: Pod "pod-subpath-test-dynamicpv-p6p6": Phase="Pending", Reason="", readiness=false. Elapsed: 18.980745441s
Oct 13 04:55:43.155: INFO: Pod "pod-subpath-test-dynamicpv-p6p6": Phase="Pending", Reason="", readiness=false. Elapsed: 21.078520138s
Oct 13 04:55:45.253: INFO: Pod "pod-subpath-test-dynamicpv-p6p6": Phase="Pending", Reason="", readiness=false. Elapsed: 23.176511475s
Oct 13 04:55:47.357: INFO: Pod "pod-subpath-test-dynamicpv-p6p6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 25.280412167s
STEP: Saw pod success
Oct 13 04:55:47.357: INFO: Pod "pod-subpath-test-dynamicpv-p6p6" satisfied condition "Succeeded or Failed"
Oct 13 04:55:47.454: INFO: Trying to get logs from node ip-172-20-53-241.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-p6p6 container test-container-subpath-dynamicpv-p6p6: <nil>
STEP: delete the pod
Oct 13 04:55:47.668: INFO: Waiting for pod pod-subpath-test-dynamicpv-p6p6 to disappear
Oct 13 04:55:47.769: INFO: Pod pod-subpath-test-dynamicpv-p6p6 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-p6p6
Oct 13 04:55:47.769: INFO: Deleting pod "pod-subpath-test-dynamicpv-p6p6" in namespace "provisioning-9059"
... skipping 89 lines ...
Oct 13 04:55:56.130: INFO: Pod aws-client still exists
Oct 13 04:55:58.133: INFO: Waiting for pod aws-client to disappear
Oct 13 04:55:58.230: INFO: Pod aws-client still exists
Oct 13 04:56:00.131: INFO: Waiting for pod aws-client to disappear
Oct 13 04:56:00.228: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Oct 13 04:56:00.474: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0baed0e2f5c1a8e2c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0baed0e2f5c1a8e2c is currently attached to i-0a4eb7973d6932982
	status code: 400, request id: 1883340f-c3cf-46e8-aca7-a1e26bfc250e
Oct 13 04:56:06.044: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0baed0e2f5c1a8e2c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0baed0e2f5c1a8e2c is currently attached to i-0a4eb7973d6932982
	status code: 400, request id: 90f2cb29-b7b9-47da-8f3f-2a135e56365a
Oct 13 04:56:11.531: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0baed0e2f5c1a8e2c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0baed0e2f5c1a8e2c is currently attached to i-0a4eb7973d6932982
	status code: 400, request id: da2e5624-5587-487c-8024-5b3b68c70be8
Oct 13 04:56:17.100: INFO: Successfully deleted PD "aws://eu-west-2a/vol-0baed0e2f5c1a8e2c".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 04:56:17.100: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-706" for this suite.
... skipping 25 lines ...
Oct 13 04:55:18.256: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3205-e2e-sc7p5cn
STEP: creating a claim
Oct 13 04:55:18.354: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-62zd
STEP: Creating a pod to test subpath
Oct 13 04:55:18.654: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-62zd" in namespace "provisioning-3205" to be "Succeeded or Failed"
Oct 13 04:55:18.754: INFO: Pod "pod-subpath-test-dynamicpv-62zd": Phase="Pending", Reason="", readiness=false. Elapsed: 99.940845ms
Oct 13 04:55:20.851: INFO: Pod "pod-subpath-test-dynamicpv-62zd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.19741093s
Oct 13 04:55:22.949: INFO: Pod "pod-subpath-test-dynamicpv-62zd": Phase="Pending", Reason="", readiness=false. Elapsed: 4.295069414s
Oct 13 04:55:25.072: INFO: Pod "pod-subpath-test-dynamicpv-62zd": Phase="Pending", Reason="", readiness=false. Elapsed: 6.417888587s
Oct 13 04:55:27.187: INFO: Pod "pod-subpath-test-dynamicpv-62zd": Phase="Pending", Reason="", readiness=false. Elapsed: 8.533010276s
Oct 13 04:55:29.288: INFO: Pod "pod-subpath-test-dynamicpv-62zd": Phase="Pending", Reason="", readiness=false. Elapsed: 10.633643813s
Oct 13 04:55:31.385: INFO: Pod "pod-subpath-test-dynamicpv-62zd": Phase="Pending", Reason="", readiness=false. Elapsed: 12.73093383s
Oct 13 04:55:33.483: INFO: Pod "pod-subpath-test-dynamicpv-62zd": Phase="Pending", Reason="", readiness=false. Elapsed: 14.828982123s
Oct 13 04:55:35.583: INFO: Pod "pod-subpath-test-dynamicpv-62zd": Phase="Pending", Reason="", readiness=false. Elapsed: 16.929158639s
Oct 13 04:55:37.691: INFO: Pod "pod-subpath-test-dynamicpv-62zd": Phase="Pending", Reason="", readiness=false. Elapsed: 19.036930801s
Oct 13 04:55:39.789: INFO: Pod "pod-subpath-test-dynamicpv-62zd": Phase="Pending", Reason="", readiness=false. Elapsed: 21.134840169s
Oct 13 04:55:41.887: INFO: Pod "pod-subpath-test-dynamicpv-62zd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.232765847s
STEP: Saw pod success
Oct 13 04:55:41.887: INFO: Pod "pod-subpath-test-dynamicpv-62zd" satisfied condition "Succeeded or Failed"
Oct 13 04:55:41.983: INFO: Trying to get logs from node ip-172-20-45-187.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-62zd container test-container-subpath-dynamicpv-62zd: <nil>
STEP: delete the pod
Oct 13 04:55:42.656: INFO: Waiting for pod pod-subpath-test-dynamicpv-62zd to disappear
Oct 13 04:55:42.753: INFO: Pod pod-subpath-test-dynamicpv-62zd no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-62zd
Oct 13 04:55:42.753: INFO: Deleting pod "pod-subpath-test-dynamicpv-62zd" in namespace "provisioning-3205"
... skipping 124 lines ...
Oct 13 04:55:21.136: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1994-e2e-scjdnhd
STEP: creating a claim
Oct 13 04:55:21.235: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-n499
STEP: Creating a pod to test subpath
Oct 13 04:55:21.527: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-n499" in namespace "provisioning-1994" to be "Succeeded or Failed"
Oct 13 04:55:21.628: INFO: Pod "pod-subpath-test-dynamicpv-n499": Phase="Pending", Reason="", readiness=false. Elapsed: 100.869524ms
Oct 13 04:55:23.728: INFO: Pod "pod-subpath-test-dynamicpv-n499": Phase="Pending", Reason="", readiness=false. Elapsed: 2.20039191s
Oct 13 04:55:25.826: INFO: Pod "pod-subpath-test-dynamicpv-n499": Phase="Pending", Reason="", readiness=false. Elapsed: 4.298693426s
Oct 13 04:55:27.923: INFO: Pod "pod-subpath-test-dynamicpv-n499": Phase="Pending", Reason="", readiness=false. Elapsed: 6.395679194s
Oct 13 04:55:30.021: INFO: Pod "pod-subpath-test-dynamicpv-n499": Phase="Pending", Reason="", readiness=false. Elapsed: 8.493547317s
Oct 13 04:55:32.120: INFO: Pod "pod-subpath-test-dynamicpv-n499": Phase="Pending", Reason="", readiness=false. Elapsed: 10.592876328s
... skipping 2 lines ...
Oct 13 04:55:38.419: INFO: Pod "pod-subpath-test-dynamicpv-n499": Phase="Pending", Reason="", readiness=false. Elapsed: 16.891844854s
Oct 13 04:55:40.516: INFO: Pod "pod-subpath-test-dynamicpv-n499": Phase="Pending", Reason="", readiness=false. Elapsed: 18.988630517s
Oct 13 04:55:42.613: INFO: Pod "pod-subpath-test-dynamicpv-n499": Phase="Pending", Reason="", readiness=false. Elapsed: 21.085562036s
Oct 13 04:55:44.711: INFO: Pod "pod-subpath-test-dynamicpv-n499": Phase="Running", Reason="", readiness=false. Elapsed: 23.183484862s
Oct 13 04:55:46.808: INFO: Pod "pod-subpath-test-dynamicpv-n499": Phase="Succeeded", Reason="", readiness=false. Elapsed: 25.280819808s
STEP: Saw pod success
Oct 13 04:55:46.808: INFO: Pod "pod-subpath-test-dynamicpv-n499" satisfied condition "Succeeded or Failed"
Oct 13 04:55:46.905: INFO: Trying to get logs from node ip-172-20-45-187.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-n499 container test-container-volume-dynamicpv-n499: <nil>
STEP: delete the pod
Oct 13 04:55:47.114: INFO: Waiting for pod pod-subpath-test-dynamicpv-n499 to disappear
Oct 13 04:55:47.212: INFO: Pod pod-subpath-test-dynamicpv-n499 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-n499
Oct 13 04:55:47.212: INFO: Deleting pod "pod-subpath-test-dynamicpv-n499" in namespace "provisioning-1994"
... skipping 104 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.2A194ozXw/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.2A194ozXw/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.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 75 lines ...
Oct 13 04:56:00.662: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Oct 13 04:56:01.349: INFO: Successfully created a new PD: "aws://eu-west-2a/vol-03def752e6a827518".
Oct 13 04:56:01.349: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-w8fd
STEP: Creating a pod to test exec-volume-test
Oct 13 04:56:01.448: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-w8fd" in namespace "volume-6061" to be "Succeeded or Failed"
Oct 13 04:56:01.545: INFO: Pod "exec-volume-test-inlinevolume-w8fd": Phase="Pending", Reason="", readiness=false. Elapsed: 96.261332ms
Oct 13 04:56:03.643: INFO: Pod "exec-volume-test-inlinevolume-w8fd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.194254931s
Oct 13 04:56:05.740: INFO: Pod "exec-volume-test-inlinevolume-w8fd": Phase="Pending", Reason="", readiness=false. Elapsed: 4.291871679s
Oct 13 04:56:07.837: INFO: Pod "exec-volume-test-inlinevolume-w8fd": Phase="Pending", Reason="", readiness=false. Elapsed: 6.388273723s
Oct 13 04:56:09.934: INFO: Pod "exec-volume-test-inlinevolume-w8fd": Phase="Pending", Reason="", readiness=false. Elapsed: 8.485641115s
Oct 13 04:56:12.031: INFO: Pod "exec-volume-test-inlinevolume-w8fd": Phase="Pending", Reason="", readiness=false. Elapsed: 10.582448632s
Oct 13 04:56:14.132: INFO: Pod "exec-volume-test-inlinevolume-w8fd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.683352723s
STEP: Saw pod success
Oct 13 04:56:14.132: INFO: Pod "exec-volume-test-inlinevolume-w8fd" satisfied condition "Succeeded or Failed"
Oct 13 04:56:14.228: INFO: Trying to get logs from node ip-172-20-48-140.eu-west-2.compute.internal pod exec-volume-test-inlinevolume-w8fd container exec-container-inlinevolume-w8fd: <nil>
STEP: delete the pod
Oct 13 04:56:14.438: INFO: Waiting for pod exec-volume-test-inlinevolume-w8fd to disappear
Oct 13 04:56:14.534: INFO: Pod exec-volume-test-inlinevolume-w8fd no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-w8fd
Oct 13 04:56:14.534: INFO: Deleting pod "exec-volume-test-inlinevolume-w8fd" in namespace "volume-6061"
Oct 13 04:56:14.824: INFO: Couldn't delete PD "aws://eu-west-2a/vol-03def752e6a827518", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-03def752e6a827518 is currently attached to i-0466ff1ba288150de
	status code: 400, request id: 578b970a-3f81-463c-9230-917f1e5208d3
Oct 13 04:56:20.371: INFO: Couldn't delete PD "aws://eu-west-2a/vol-03def752e6a827518", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-03def752e6a827518 is currently attached to i-0466ff1ba288150de
	status code: 400, request id: a795d02a-974c-42f4-bd9b-0a5d76886abb
Oct 13 04:56:25.866: INFO: Couldn't delete PD "aws://eu-west-2a/vol-03def752e6a827518", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-03def752e6a827518 is currently attached to i-0466ff1ba288150de
	status code: 400, request id: b60238f6-7d39-4e6c-b0c5-93c2bb13c985
Oct 13 04:56:31.402: INFO: Successfully deleted PD "aws://eu-west-2a/vol-03def752e6a827518".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 04:56:31.402: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-6061" for this suite.
... skipping 128 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 04:55:20.019: 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.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Oct 13 04:55:21.970: INFO: Creating resource for dynamic PV
Oct 13 04:55:21.970: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-159-e2e-scn247x
STEP: creating a claim
Oct 13 04:55:22.078: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-nhw7
STEP: Checking for subpath error in container status
Oct 13 04:56:04.583: INFO: Deleting pod "pod-subpath-test-dynamicpv-nhw7" in namespace "provisioning-159"
Oct 13 04:56:04.683: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-nhw7" to be fully deleted
STEP: Deleting pod
Oct 13 04:56:06.878: INFO: Deleting pod "pod-subpath-test-dynamicpv-nhw7" in namespace "provisioning-159"
STEP: Deleting pvc
Oct 13 04:56:07.172: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.combrvzs"
... skipping 15 lines ...

• [SLOW TEST:83.389 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.2A194ozXw/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.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 04:56:43.410: 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.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Oct 13 04:56:43.994: INFO: found topology map[topology.ebs.csi.aws.com/zone:eu-west-2a]
Oct 13 04:56:43.995: 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.877 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.2A194ozXw/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.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

    Not enough topologies in cluster -- skipping

    /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 624 lines ...
Oct 13 04:56:14.646: INFO: Creating resource for dynamic PV
Oct 13 04:56:14.646: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6733qd2ck
STEP: creating a claim
Oct 13 04:56:14.744: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-6733
Oct 13 04:56:15.040: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-6733" in namespace "provisioning-6733" to be "Succeeded or Failed"
Oct 13 04:56:15.138: INFO: Pod "volume-prep-provisioning-6733": Phase="Pending", Reason="", readiness=false. Elapsed: 98.1334ms
Oct 13 04:56:17.237: INFO: Pod "volume-prep-provisioning-6733": Phase="Pending", Reason="", readiness=false. Elapsed: 2.197233629s
Oct 13 04:56:19.335: INFO: Pod "volume-prep-provisioning-6733": Phase="Pending", Reason="", readiness=false. Elapsed: 4.294971555s
Oct 13 04:56:21.434: INFO: Pod "volume-prep-provisioning-6733": Phase="Pending", Reason="", readiness=false. Elapsed: 6.39341688s
Oct 13 04:56:23.532: INFO: Pod "volume-prep-provisioning-6733": Phase="Pending", Reason="", readiness=false. Elapsed: 8.492132048s
Oct 13 04:56:25.636: INFO: Pod "volume-prep-provisioning-6733": Phase="Pending", Reason="", readiness=false. Elapsed: 10.595440888s
Oct 13 04:56:27.733: INFO: Pod "volume-prep-provisioning-6733": Phase="Pending", Reason="", readiness=false. Elapsed: 12.692880665s
Oct 13 04:56:29.832: INFO: Pod "volume-prep-provisioning-6733": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.79162797s
STEP: Saw pod success
Oct 13 04:56:29.832: INFO: Pod "volume-prep-provisioning-6733" satisfied condition "Succeeded or Failed"
Oct 13 04:56:29.832: INFO: Deleting pod "volume-prep-provisioning-6733" in namespace "provisioning-6733"
Oct 13 04:56:29.934: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-6733" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-shbj
STEP: Checking for subpath error in container status
Oct 13 04:56:32.331: INFO: Deleting pod "pod-subpath-test-dynamicpv-shbj" in namespace "provisioning-6733"
Oct 13 04:56:32.437: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-shbj" to be fully deleted
STEP: Deleting pod
Oct 13 04:56:32.537: INFO: Deleting pod "pod-subpath-test-dynamicpv-shbj" in namespace "provisioning-6733"
STEP: Deleting pvc
Oct 13 04:56:32.828: INFO: Deleting PersistentVolumeClaim "awsq6fck"
... skipping 163 lines ...
Oct 13 04:55:18.414: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3245-e2e-sctxdqq
STEP: creating a claim
Oct 13 04:55:18.517: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-rz7m
STEP: Creating a pod to test subpath
Oct 13 04:55:18.808: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-rz7m" in namespace "provisioning-3245" to be "Succeeded or Failed"
Oct 13 04:55:18.904: INFO: Pod "pod-subpath-test-dynamicpv-rz7m": Phase="Pending", Reason="", readiness=false. Elapsed: 95.382538ms
Oct 13 04:55:21.000: INFO: Pod "pod-subpath-test-dynamicpv-rz7m": Phase="Pending", Reason="", readiness=false. Elapsed: 2.191900226s
Oct 13 04:55:23.096: INFO: Pod "pod-subpath-test-dynamicpv-rz7m": Phase="Pending", Reason="", readiness=false. Elapsed: 4.288151259s
Oct 13 04:55:25.211: INFO: Pod "pod-subpath-test-dynamicpv-rz7m": Phase="Pending", Reason="", readiness=false. Elapsed: 6.403069491s
Oct 13 04:55:27.307: INFO: Pod "pod-subpath-test-dynamicpv-rz7m": Phase="Pending", Reason="", readiness=false. Elapsed: 8.499244482s
Oct 13 04:55:29.405: INFO: Pod "pod-subpath-test-dynamicpv-rz7m": Phase="Pending", Reason="", readiness=false. Elapsed: 10.596654733s
... skipping 4 lines ...
Oct 13 04:55:39.885: INFO: Pod "pod-subpath-test-dynamicpv-rz7m": Phase="Pending", Reason="", readiness=false. Elapsed: 21.076782249s
Oct 13 04:55:41.982: INFO: Pod "pod-subpath-test-dynamicpv-rz7m": Phase="Pending", Reason="", readiness=false. Elapsed: 23.173539895s
Oct 13 04:55:44.078: INFO: Pod "pod-subpath-test-dynamicpv-rz7m": Phase="Pending", Reason="", readiness=false. Elapsed: 25.270204191s
Oct 13 04:55:46.174: INFO: Pod "pod-subpath-test-dynamicpv-rz7m": Phase="Pending", Reason="", readiness=false. Elapsed: 27.36606317s
Oct 13 04:55:48.271: INFO: Pod "pod-subpath-test-dynamicpv-rz7m": Phase="Succeeded", Reason="", readiness=false. Elapsed: 29.462465181s
STEP: Saw pod success
Oct 13 04:55:48.271: INFO: Pod "pod-subpath-test-dynamicpv-rz7m" satisfied condition "Succeeded or Failed"
Oct 13 04:55:48.367: INFO: Trying to get logs from node ip-172-20-62-14.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-rz7m container test-container-subpath-dynamicpv-rz7m: <nil>
STEP: delete the pod
Oct 13 04:55:49.163: INFO: Waiting for pod pod-subpath-test-dynamicpv-rz7m to disappear
Oct 13 04:55:49.258: INFO: Pod pod-subpath-test-dynamicpv-rz7m no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-rz7m
Oct 13 04:55:49.258: INFO: Deleting pod "pod-subpath-test-dynamicpv-rz7m" in namespace "provisioning-3245"
STEP: Creating pod pod-subpath-test-dynamicpv-rz7m
STEP: Creating a pod to test subpath
Oct 13 04:55:49.452: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-rz7m" in namespace "provisioning-3245" to be "Succeeded or Failed"
Oct 13 04:55:49.547: INFO: Pod "pod-subpath-test-dynamicpv-rz7m": Phase="Pending", Reason="", readiness=false. Elapsed: 95.393284ms
Oct 13 04:55:51.643: INFO: Pod "pod-subpath-test-dynamicpv-rz7m": Phase="Pending", Reason="", readiness=false. Elapsed: 2.191603353s
Oct 13 04:55:53.740: INFO: Pod "pod-subpath-test-dynamicpv-rz7m": Phase="Pending", Reason="", readiness=false. Elapsed: 4.288037845s
Oct 13 04:55:55.835: INFO: Pod "pod-subpath-test-dynamicpv-rz7m": Phase="Pending", Reason="", readiness=false. Elapsed: 6.38365543s
Oct 13 04:55:57.931: INFO: Pod "pod-subpath-test-dynamicpv-rz7m": Phase="Pending", Reason="", readiness=false. Elapsed: 8.479632174s
Oct 13 04:56:00.027: INFO: Pod "pod-subpath-test-dynamicpv-rz7m": Phase="Pending", Reason="", readiness=false. Elapsed: 10.575281778s
... skipping 7 lines ...
Oct 13 04:56:16.804: INFO: Pod "pod-subpath-test-dynamicpv-rz7m": Phase="Pending", Reason="", readiness=false. Elapsed: 27.352151371s
Oct 13 04:56:18.901: INFO: Pod "pod-subpath-test-dynamicpv-rz7m": Phase="Pending", Reason="", readiness=false. Elapsed: 29.448930671s
Oct 13 04:56:20.996: INFO: Pod "pod-subpath-test-dynamicpv-rz7m": Phase="Pending", Reason="", readiness=false. Elapsed: 31.544565328s
Oct 13 04:56:23.092: INFO: Pod "pod-subpath-test-dynamicpv-rz7m": Phase="Pending", Reason="", readiness=false. Elapsed: 33.640470732s
Oct 13 04:56:25.189: INFO: Pod "pod-subpath-test-dynamicpv-rz7m": Phase="Succeeded", Reason="", readiness=false. Elapsed: 35.736900592s
STEP: Saw pod success
Oct 13 04:56:25.189: INFO: Pod "pod-subpath-test-dynamicpv-rz7m" satisfied condition "Succeeded or Failed"
Oct 13 04:56:25.284: INFO: Trying to get logs from node ip-172-20-45-187.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-rz7m container test-container-subpath-dynamicpv-rz7m: <nil>
STEP: delete the pod
Oct 13 04:56:25.483: INFO: Waiting for pod pod-subpath-test-dynamicpv-rz7m to disappear
Oct 13 04:56:25.579: INFO: Pod pod-subpath-test-dynamicpv-rz7m no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-rz7m
Oct 13 04:56:25.579: INFO: Deleting pod "pod-subpath-test-dynamicpv-rz7m" in namespace "provisioning-3245"
... skipping 541 lines ...
Oct 13 04:56:19.908: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-94715dk86
STEP: creating a claim
Oct 13 04:56:20.006: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-ld9k
STEP: Creating a pod to test exec-volume-test
Oct 13 04:56:20.305: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-ld9k" in namespace "volume-9471" to be "Succeeded or Failed"
Oct 13 04:56:20.409: INFO: Pod "exec-volume-test-dynamicpv-ld9k": Phase="Pending", Reason="", readiness=false. Elapsed: 104.054363ms
Oct 13 04:56:22.506: INFO: Pod "exec-volume-test-dynamicpv-ld9k": Phase="Pending", Reason="", readiness=false. Elapsed: 2.20125886s
Oct 13 04:56:24.604: INFO: Pod "exec-volume-test-dynamicpv-ld9k": Phase="Pending", Reason="", readiness=false. Elapsed: 4.299335736s
Oct 13 04:56:26.701: INFO: Pod "exec-volume-test-dynamicpv-ld9k": Phase="Pending", Reason="", readiness=false. Elapsed: 6.396273286s
Oct 13 04:56:28.801: INFO: Pod "exec-volume-test-dynamicpv-ld9k": Phase="Pending", Reason="", readiness=false. Elapsed: 8.495872448s
Oct 13 04:56:30.898: INFO: Pod "exec-volume-test-dynamicpv-ld9k": Phase="Pending", Reason="", readiness=false. Elapsed: 10.593103847s
... skipping 8 lines ...
Oct 13 04:56:49.773: INFO: Pod "exec-volume-test-dynamicpv-ld9k": Phase="Pending", Reason="", readiness=false. Elapsed: 29.468643407s
Oct 13 04:56:51.870: INFO: Pod "exec-volume-test-dynamicpv-ld9k": Phase="Pending", Reason="", readiness=false. Elapsed: 31.565328643s
Oct 13 04:56:53.967: INFO: Pod "exec-volume-test-dynamicpv-ld9k": Phase="Pending", Reason="", readiness=false. Elapsed: 33.662187078s
Oct 13 04:56:56.064: INFO: Pod "exec-volume-test-dynamicpv-ld9k": Phase="Pending", Reason="", readiness=false. Elapsed: 35.759091368s
Oct 13 04:56:58.163: INFO: Pod "exec-volume-test-dynamicpv-ld9k": Phase="Succeeded", Reason="", readiness=false. Elapsed: 37.857870398s
STEP: Saw pod success
Oct 13 04:56:58.163: INFO: Pod "exec-volume-test-dynamicpv-ld9k" satisfied condition "Succeeded or Failed"
Oct 13 04:56:58.263: INFO: Trying to get logs from node ip-172-20-62-14.eu-west-2.compute.internal pod exec-volume-test-dynamicpv-ld9k container exec-container-dynamicpv-ld9k: <nil>
STEP: delete the pod
Oct 13 04:56:58.462: INFO: Waiting for pod exec-volume-test-dynamicpv-ld9k to disappear
Oct 13 04:56:58.559: INFO: Pod exec-volume-test-dynamicpv-ld9k no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-ld9k
Oct 13 04:56:58.559: INFO: Deleting pod "exec-volume-test-dynamicpv-ld9k" in namespace "volume-9471"
... skipping 95 lines ...
Oct 13 04:56:39.949: INFO: Creating resource for dynamic PV
Oct 13 04:56:39.949: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-65192zn2d
STEP: creating a claim
STEP: Expanding non-expandable pvc
Oct 13 04:56:40.241: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Oct 13 04:56:40.437: INFO: Error updating pvc aws76v62: PersistentVolumeClaim "aws76v62" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-65192zn2d",
  	... // 3 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Oct 13 04:57:10.827: INFO: Error updating pvc aws76v62: PersistentVolumeClaim "aws76v62" is invalid: spec: Forbidden: spec is 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 ...
Oct 13 04:56:08.703: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4531vg965
STEP: creating a claim
Oct 13 04:56:08.800: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-sj99
STEP: Creating a pod to test atomic-volume-subpath
Oct 13 04:56:09.092: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-sj99" in namespace "provisioning-4531" to be "Succeeded or Failed"
Oct 13 04:56:09.189: INFO: Pod "pod-subpath-test-dynamicpv-sj99": Phase="Pending", Reason="", readiness=false. Elapsed: 96.965225ms
Oct 13 04:56:11.286: INFO: Pod "pod-subpath-test-dynamicpv-sj99": Phase="Pending", Reason="", readiness=false. Elapsed: 2.193993362s
Oct 13 04:56:13.383: INFO: Pod "pod-subpath-test-dynamicpv-sj99": Phase="Pending", Reason="", readiness=false. Elapsed: 4.290735416s
Oct 13 04:56:15.480: INFO: Pod "pod-subpath-test-dynamicpv-sj99": Phase="Pending", Reason="", readiness=false. Elapsed: 6.387322609s
Oct 13 04:56:17.577: INFO: Pod "pod-subpath-test-dynamicpv-sj99": Phase="Pending", Reason="", readiness=false. Elapsed: 8.484327622s
Oct 13 04:56:19.674: INFO: Pod "pod-subpath-test-dynamicpv-sj99": Phase="Pending", Reason="", readiness=false. Elapsed: 10.581769162s
... skipping 7 lines ...
Oct 13 04:56:36.452: INFO: Pod "pod-subpath-test-dynamicpv-sj99": Phase="Running", Reason="", readiness=true. Elapsed: 27.359386299s
Oct 13 04:56:38.548: INFO: Pod "pod-subpath-test-dynamicpv-sj99": Phase="Running", Reason="", readiness=true. Elapsed: 29.456111029s
Oct 13 04:56:40.646: INFO: Pod "pod-subpath-test-dynamicpv-sj99": Phase="Running", Reason="", readiness=true. Elapsed: 31.553758292s
Oct 13 04:56:42.744: INFO: Pod "pod-subpath-test-dynamicpv-sj99": Phase="Running", Reason="", readiness=true. Elapsed: 33.651582376s
Oct 13 04:56:44.841: INFO: Pod "pod-subpath-test-dynamicpv-sj99": Phase="Succeeded", Reason="", readiness=false. Elapsed: 35.748269289s
STEP: Saw pod success
Oct 13 04:56:44.841: INFO: Pod "pod-subpath-test-dynamicpv-sj99" satisfied condition "Succeeded or Failed"
Oct 13 04:56:44.937: INFO: Trying to get logs from node ip-172-20-48-140.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-sj99 container test-container-subpath-dynamicpv-sj99: <nil>
STEP: delete the pod
Oct 13 04:56:45.137: INFO: Waiting for pod pod-subpath-test-dynamicpv-sj99 to disappear
Oct 13 04:56:45.233: INFO: Pod pod-subpath-test-dynamicpv-sj99 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-sj99
Oct 13 04:56:45.233: INFO: Deleting pod "pod-subpath-test-dynamicpv-sj99" in namespace "provisioning-4531"
... skipping 30 lines ...
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 04:57:11.331: 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.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Oct 13 04:57:11.913: INFO: found topology map[topology.kubernetes.io/zone:eu-west-2a]
Oct 13 04:57:11.913: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 13 04:57:11.913: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.2A194ozXw/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.2A194ozXw/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (delayed binding)] topology
    /tmp/kops.2A194ozXw/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.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 209 lines ...
Oct 13 04:55:59.262: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-29508flsj
STEP: creating a claim
Oct 13 04:55:59.359: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-zgkt
STEP: Creating a pod to test subpath
Oct 13 04:55:59.675: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-zgkt" in namespace "provisioning-2950" to be "Succeeded or Failed"
Oct 13 04:55:59.771: INFO: Pod "pod-subpath-test-dynamicpv-zgkt": Phase="Pending", Reason="", readiness=false. Elapsed: 96.398998ms
Oct 13 04:56:01.868: INFO: Pod "pod-subpath-test-dynamicpv-zgkt": Phase="Pending", Reason="", readiness=false. Elapsed: 2.193467896s
Oct 13 04:56:03.966: INFO: Pod "pod-subpath-test-dynamicpv-zgkt": Phase="Pending", Reason="", readiness=false. Elapsed: 4.29098464s
Oct 13 04:56:06.062: INFO: Pod "pod-subpath-test-dynamicpv-zgkt": Phase="Pending", Reason="", readiness=false. Elapsed: 6.387627015s
Oct 13 04:56:08.159: INFO: Pod "pod-subpath-test-dynamicpv-zgkt": Phase="Pending", Reason="", readiness=false. Elapsed: 8.484458724s
Oct 13 04:56:10.257: INFO: Pod "pod-subpath-test-dynamicpv-zgkt": Phase="Pending", Reason="", readiness=false. Elapsed: 10.582006016s
Oct 13 04:56:12.353: INFO: Pod "pod-subpath-test-dynamicpv-zgkt": Phase="Pending", Reason="", readiness=false. Elapsed: 12.678834424s
Oct 13 04:56:14.451: INFO: Pod "pod-subpath-test-dynamicpv-zgkt": Phase="Pending", Reason="", readiness=false. Elapsed: 14.776538464s
Oct 13 04:56:16.548: INFO: Pod "pod-subpath-test-dynamicpv-zgkt": Phase="Pending", Reason="", readiness=false. Elapsed: 16.872944368s
Oct 13 04:56:18.645: INFO: Pod "pod-subpath-test-dynamicpv-zgkt": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.970682217s
STEP: Saw pod success
Oct 13 04:56:18.645: INFO: Pod "pod-subpath-test-dynamicpv-zgkt" satisfied condition "Succeeded or Failed"
Oct 13 04:56:18.742: INFO: Trying to get logs from node ip-172-20-45-187.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-zgkt container test-container-subpath-dynamicpv-zgkt: <nil>
STEP: delete the pod
Oct 13 04:56:18.942: INFO: Waiting for pod pod-subpath-test-dynamicpv-zgkt to disappear
Oct 13 04:56:19.038: INFO: Pod pod-subpath-test-dynamicpv-zgkt no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-zgkt
Oct 13 04:56:19.038: INFO: Deleting pod "pod-subpath-test-dynamicpv-zgkt" in namespace "provisioning-2950"
STEP: Creating pod pod-subpath-test-dynamicpv-zgkt
STEP: Creating a pod to test subpath
Oct 13 04:56:19.232: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-zgkt" in namespace "provisioning-2950" to be "Succeeded or Failed"
Oct 13 04:56:19.332: INFO: Pod "pod-subpath-test-dynamicpv-zgkt": Phase="Pending", Reason="", readiness=false. Elapsed: 99.906389ms
Oct 13 04:56:21.429: INFO: Pod "pod-subpath-test-dynamicpv-zgkt": Phase="Pending", Reason="", readiness=false. Elapsed: 2.197444427s
Oct 13 04:56:23.527: INFO: Pod "pod-subpath-test-dynamicpv-zgkt": Phase="Pending", Reason="", readiness=false. Elapsed: 4.295512988s
Oct 13 04:56:25.625: INFO: Pod "pod-subpath-test-dynamicpv-zgkt": Phase="Pending", Reason="", readiness=false. Elapsed: 6.393612222s
Oct 13 04:56:27.723: INFO: Pod "pod-subpath-test-dynamicpv-zgkt": Phase="Pending", Reason="", readiness=false. Elapsed: 8.491630037s
Oct 13 04:56:29.824: INFO: Pod "pod-subpath-test-dynamicpv-zgkt": Phase="Pending", Reason="", readiness=false. Elapsed: 10.592021847s
... skipping 7 lines ...
Oct 13 04:56:46.603: INFO: Pod "pod-subpath-test-dynamicpv-zgkt": Phase="Pending", Reason="", readiness=false. Elapsed: 27.371096379s
Oct 13 04:56:48.700: INFO: Pod "pod-subpath-test-dynamicpv-zgkt": Phase="Pending", Reason="", readiness=false. Elapsed: 29.467832138s
Oct 13 04:56:50.800: INFO: Pod "pod-subpath-test-dynamicpv-zgkt": Phase="Pending", Reason="", readiness=false. Elapsed: 31.568107981s
Oct 13 04:56:52.897: INFO: Pod "pod-subpath-test-dynamicpv-zgkt": Phase="Pending", Reason="", readiness=false. Elapsed: 33.664837063s
Oct 13 04:56:54.994: INFO: Pod "pod-subpath-test-dynamicpv-zgkt": Phase="Succeeded", Reason="", readiness=false. Elapsed: 35.762276584s
STEP: Saw pod success
Oct 13 04:56:54.994: INFO: Pod "pod-subpath-test-dynamicpv-zgkt" satisfied condition "Succeeded or Failed"
Oct 13 04:56:55.090: INFO: Trying to get logs from node ip-172-20-48-140.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-zgkt container test-container-subpath-dynamicpv-zgkt: <nil>
STEP: delete the pod
Oct 13 04:56:55.289: INFO: Waiting for pod pod-subpath-test-dynamicpv-zgkt to disappear
Oct 13 04:56:55.388: INFO: Pod pod-subpath-test-dynamicpv-zgkt no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-zgkt
Oct 13 04:56:55.388: INFO: Deleting pod "pod-subpath-test-dynamicpv-zgkt" in namespace "provisioning-2950"
... skipping 50 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 04:56:58.815: 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.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Oct 13 04:56:59.303: INFO: Creating resource for dynamic PV
Oct 13 04:56:59.304: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-6676-e2e-sckkdz5
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Oct 13 04:57:03.993: INFO: Deleting pod "pod-3a62a585-addb-4d61-abf8-87e132658acb" in namespace "volumemode-6676"
Oct 13 04:57:04.097: INFO: Wait up to 5m0s for pod "pod-3a62a585-addb-4d61-abf8-87e132658acb" to be fully deleted
STEP: Deleting pvc
Oct 13 04:57:06.492: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comt94dn"
Oct 13 04:57:06.591: INFO: Waiting up to 5m0s for PersistentVolume pvc-b09028ed-0bca-4c42-9ffe-a63286c44ba4 to get deleted
Oct 13 04:57:06.688: INFO: PersistentVolume pvc-b09028ed-0bca-4c42-9ffe-a63286c44ba4 found and phase=Released (96.984621ms)
... skipping 8 lines ...

• [SLOW TEST:18.366 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.2A194ozXw/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.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 47 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 04:57:03.860: 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.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Oct 13 04:57:04.398: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 13 04:57:04.398: INFO: Creating resource for dynamic PV
Oct 13 04:57:04.398: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-3147plpjt
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Oct 13 04:57:09.084: INFO: Deleting pod "pod-148240ad-1ddf-49af-8542-53f72aba26ba" in namespace "volumemode-3147"
Oct 13 04:57:09.181: INFO: Wait up to 5m0s for pod "pod-148240ad-1ddf-49af-8542-53f72aba26ba" to be fully deleted
STEP: Deleting pvc
Oct 13 04:57:13.566: INFO: Deleting PersistentVolumeClaim "awshl4x5"
Oct 13 04:57:13.666: INFO: Waiting up to 5m0s for PersistentVolume pvc-fc9d5a10-1438-45a5-b82d-1fcefe302fd5 to get deleted
Oct 13 04:57:13.767: INFO: PersistentVolume pvc-fc9d5a10-1438-45a5-b82d-1fcefe302fd5 found and phase=Released (101.244506ms)
... skipping 12 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.2A194ozXw/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.2A194ozXw/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (block volmode)] volumeMode
    /tmp/kops.2A194ozXw/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.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [sig-storage] Volume Provisioning On Clustered Datastore [Feature:vsphere]
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 04:57:34.451: INFO: >>> kubeConfig: /root/.kube/config
... skipping 129 lines ...
Oct 13 04:57:12.087: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-8929-e2e-sc4w7rg
STEP: creating a claim
Oct 13 04:57:12.191: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-cpnp
STEP: Creating a pod to test exec-volume-test
Oct 13 04:57:12.485: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-cpnp" in namespace "volume-8929" to be "Succeeded or Failed"
Oct 13 04:57:12.581: INFO: Pod "exec-volume-test-dynamicpv-cpnp": Phase="Pending", Reason="", readiness=false. Elapsed: 96.369172ms
Oct 13 04:57:14.678: INFO: Pod "exec-volume-test-dynamicpv-cpnp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.193173516s
Oct 13 04:57:16.777: INFO: Pod "exec-volume-test-dynamicpv-cpnp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.2925914s
Oct 13 04:57:18.874: INFO: Pod "exec-volume-test-dynamicpv-cpnp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.389011901s
Oct 13 04:57:20.973: INFO: Pod "exec-volume-test-dynamicpv-cpnp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.487972136s
Oct 13 04:57:23.070: INFO: Pod "exec-volume-test-dynamicpv-cpnp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.585382417s
STEP: Saw pod success
Oct 13 04:57:23.070: INFO: Pod "exec-volume-test-dynamicpv-cpnp" satisfied condition "Succeeded or Failed"
Oct 13 04:57:23.167: INFO: Trying to get logs from node ip-172-20-45-187.eu-west-2.compute.internal pod exec-volume-test-dynamicpv-cpnp container exec-container-dynamicpv-cpnp: <nil>
STEP: delete the pod
Oct 13 04:57:23.366: INFO: Waiting for pod exec-volume-test-dynamicpv-cpnp to disappear
Oct 13 04:57:23.462: INFO: Pod exec-volume-test-dynamicpv-cpnp no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-cpnp
Oct 13 04:57:23.462: INFO: Deleting pod "exec-volume-test-dynamicpv-cpnp" in namespace "volume-8929"
... skipping 160 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 04:56:26.967: 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.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Oct 13 04:56:27.454: INFO: Creating resource for dynamic PV
Oct 13 04:56:27.454: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5072-e2e-sc6m6vd
STEP: creating a claim
Oct 13 04:56:27.552: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-dpcb
STEP: Checking for subpath error in container status
Oct 13 04:57:08.042: INFO: Deleting pod "pod-subpath-test-dynamicpv-dpcb" in namespace "provisioning-5072"
Oct 13 04:57:08.141: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-dpcb" to be fully deleted
STEP: Deleting pod
Oct 13 04:57:10.341: INFO: Deleting pod "pod-subpath-test-dynamicpv-dpcb" in namespace "provisioning-5072"
STEP: Deleting pvc
Oct 13 04:57:10.633: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com5s5fw"
... skipping 15 lines ...

• [SLOW TEST:79.857 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath file is outside the volume [Slow][LinuxOnly]
    /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 8 lines ...
Oct 13 04:57:13.828: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9375tg9fl
STEP: creating a claim
Oct 13 04:57:13.926: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-vc62
STEP: Creating a pod to test subpath
Oct 13 04:57:14.217: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-vc62" in namespace "provisioning-9375" to be "Succeeded or Failed"
Oct 13 04:57:14.355: INFO: Pod "pod-subpath-test-dynamicpv-vc62": Phase="Pending", Reason="", readiness=false. Elapsed: 138.013588ms
Oct 13 04:57:16.455: INFO: Pod "pod-subpath-test-dynamicpv-vc62": Phase="Pending", Reason="", readiness=false. Elapsed: 2.238268237s
Oct 13 04:57:18.555: INFO: Pod "pod-subpath-test-dynamicpv-vc62": Phase="Pending", Reason="", readiness=false. Elapsed: 4.338264727s
Oct 13 04:57:20.653: INFO: Pod "pod-subpath-test-dynamicpv-vc62": Phase="Pending", Reason="", readiness=false. Elapsed: 6.43572276s
Oct 13 04:57:22.749: INFO: Pod "pod-subpath-test-dynamicpv-vc62": Phase="Pending", Reason="", readiness=false. Elapsed: 8.532510943s
Oct 13 04:57:24.847: INFO: Pod "pod-subpath-test-dynamicpv-vc62": Phase="Pending", Reason="", readiness=false. Elapsed: 10.630312686s
Oct 13 04:57:26.944: INFO: Pod "pod-subpath-test-dynamicpv-vc62": Phase="Pending", Reason="", readiness=false. Elapsed: 12.72705397s
Oct 13 04:57:29.041: INFO: Pod "pod-subpath-test-dynamicpv-vc62": Phase="Pending", Reason="", readiness=false. Elapsed: 14.823858544s
Oct 13 04:57:31.138: INFO: Pod "pod-subpath-test-dynamicpv-vc62": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.921313641s
STEP: Saw pod success
Oct 13 04:57:31.138: INFO: Pod "pod-subpath-test-dynamicpv-vc62" satisfied condition "Succeeded or Failed"
Oct 13 04:57:31.234: INFO: Trying to get logs from node ip-172-20-48-140.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-vc62 container test-container-volume-dynamicpv-vc62: <nil>
STEP: delete the pod
Oct 13 04:57:31.439: INFO: Waiting for pod pod-subpath-test-dynamicpv-vc62 to disappear
Oct 13 04:57:31.535: INFO: Pod pod-subpath-test-dynamicpv-vc62 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-vc62
Oct 13 04:57:31.535: INFO: Deleting pod "pod-subpath-test-dynamicpv-vc62" in namespace "provisioning-9375"
... skipping 30 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 04:56:54.051: 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.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Oct 13 04:56:54.562: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 13 04:56:54.562: INFO: Creating resource for dynamic PV
Oct 13 04:56:54.562: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-55684wrv8
STEP: creating a claim
Oct 13 04:56:54.659: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-9rkt
STEP: Checking for subpath error in container status
Oct 13 04:57:19.148: INFO: Deleting pod "pod-subpath-test-dynamicpv-9rkt" in namespace "provisioning-5568"
Oct 13 04:57:19.246: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-9rkt" to be fully deleted
STEP: Deleting pod
Oct 13 04:57:21.440: INFO: Deleting pod "pod-subpath-test-dynamicpv-9rkt" in namespace "provisioning-5568"
STEP: Deleting pvc
Oct 13 04:57:21.730: INFO: Deleting PersistentVolumeClaim "aws8kdrp"
... skipping 15 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.2A194ozXw/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.2A194ozXw/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.2A194ozXw/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.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Oct 13 04:57:47.711: INFO: Driver "ebs.csi.aws.com" does not support volume type "InlineVolume" - skipping
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
... skipping 73 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.2A194ozXw/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.2A194ozXw/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.2A194ozXw/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.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 12 lines ...
Oct 13 04:55:51.699: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-8775-e2e-sctwkqj      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-8775    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-8775-e2e-sctwkqj,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-8775    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-8775-e2e-sctwkqj,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-8775    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-8775-e2e-sctwkqj,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-8775-e2e-sctwkqj    6af5a0a3-17ad-490e-9c5e-7f5dd0548ad8 3896 0 2021-10-13 04:55:51 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-10-13 04:55:51 +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-5w96n pvc- provisioning-8775  e4fc59f7-2802-4b7d-bd6f-63b02ff155d7 3911 0 2021-10-13 04:55:52 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-10-13 04:55:52 +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-8775-e2e-sctwkqj,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-e55cb688-dcfc-4374-a485-02ac2ebba937 in namespace provisioning-8775
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Oct 13 04:56:04.794: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-pphrs" in namespace "provisioning-8775" to be "Succeeded or Failed"
Oct 13 04:56:04.891: INFO: Pod "pvc-volume-tester-writer-pphrs": Phase="Pending", Reason="", readiness=false. Elapsed: 96.959374ms
Oct 13 04:56:06.989: INFO: Pod "pvc-volume-tester-writer-pphrs": Phase="Pending", Reason="", readiness=false. Elapsed: 2.194720029s
Oct 13 04:56:09.086: INFO: Pod "pvc-volume-tester-writer-pphrs": Phase="Pending", Reason="", readiness=false. Elapsed: 4.292398032s
Oct 13 04:56:11.184: INFO: Pod "pvc-volume-tester-writer-pphrs": Phase="Pending", Reason="", readiness=false. Elapsed: 6.390195101s
Oct 13 04:56:13.283: INFO: Pod "pvc-volume-tester-writer-pphrs": Phase="Pending", Reason="", readiness=false. Elapsed: 8.488700425s
Oct 13 04:56:15.381: INFO: Pod "pvc-volume-tester-writer-pphrs": Phase="Pending", Reason="", readiness=false. Elapsed: 10.587152871s
... skipping 23 lines ...
Oct 13 04:57:05.737: INFO: Pod "pvc-volume-tester-writer-pphrs": Phase="Pending", Reason="", readiness=false. Elapsed: 1m0.942968303s
Oct 13 04:57:07.835: INFO: Pod "pvc-volume-tester-writer-pphrs": Phase="Pending", Reason="", readiness=false. Elapsed: 1m3.041247279s
Oct 13 04:57:09.933: INFO: Pod "pvc-volume-tester-writer-pphrs": Phase="Pending", Reason="", readiness=false. Elapsed: 1m5.138658888s
Oct 13 04:57:12.031: INFO: Pod "pvc-volume-tester-writer-pphrs": Phase="Pending", Reason="", readiness=false. Elapsed: 1m7.236912643s
Oct 13 04:57:14.128: INFO: Pod "pvc-volume-tester-writer-pphrs": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m9.334479117s
STEP: Saw pod success
Oct 13 04:57:14.128: INFO: Pod "pvc-volume-tester-writer-pphrs" satisfied condition "Succeeded or Failed"
Oct 13 04:57:14.328: INFO: Pod pvc-volume-tester-writer-pphrs has the following logs: 
Oct 13 04:57:14.328: INFO: Deleting pod "pvc-volume-tester-writer-pphrs" in namespace "provisioning-8775"
Oct 13 04:57:14.430: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-pphrs" 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-62-14.eu-west-2.compute.internal"
Oct 13 04:57:14.824: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-8js4d" in namespace "provisioning-8775" to be "Succeeded or Failed"
Oct 13 04:57:14.923: INFO: Pod "pvc-volume-tester-reader-8js4d": Phase="Pending", Reason="", readiness=false. Elapsed: 99.201536ms
Oct 13 04:57:17.022: INFO: Pod "pvc-volume-tester-reader-8js4d": Phase="Pending", Reason="", readiness=false. Elapsed: 2.197809148s
Oct 13 04:57:19.121: INFO: Pod "pvc-volume-tester-reader-8js4d": Phase="Pending", Reason="", readiness=false. Elapsed: 4.296637553s
Oct 13 04:57:21.219: INFO: Pod "pvc-volume-tester-reader-8js4d": Phase="Pending", Reason="", readiness=false. Elapsed: 6.394847533s
Oct 13 04:57:23.316: INFO: Pod "pvc-volume-tester-reader-8js4d": Phase="Pending", Reason="", readiness=false. Elapsed: 8.492110883s
Oct 13 04:57:25.414: INFO: Pod "pvc-volume-tester-reader-8js4d": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.590290657s
STEP: Saw pod success
Oct 13 04:57:25.414: INFO: Pod "pvc-volume-tester-reader-8js4d" satisfied condition "Succeeded or Failed"
Oct 13 04:57:25.619: INFO: Pod pvc-volume-tester-reader-8js4d has the following logs: hello world

Oct 13 04:57:25.619: INFO: Deleting pod "pvc-volume-tester-reader-8js4d" in namespace "provisioning-8775"
Oct 13 04:57:25.720: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-8js4d" to be fully deleted
Oct 13 04:57:25.817: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-5w96n] to have phase Bound
Oct 13 04:57:25.914: INFO: PersistentVolumeClaim pvc-5w96n found and phase=Bound (96.93826ms)
... skipping 376 lines ...
Oct 13 04:57:13.031: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8423qc4mk
STEP: creating a claim
Oct 13 04:57:13.128: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-ntfd
STEP: Creating a pod to test subpath
Oct 13 04:57:13.423: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-ntfd" in namespace "provisioning-8423" to be "Succeeded or Failed"
Oct 13 04:57:13.520: INFO: Pod "pod-subpath-test-dynamicpv-ntfd": Phase="Pending", Reason="", readiness=false. Elapsed: 96.764411ms
Oct 13 04:57:15.616: INFO: Pod "pod-subpath-test-dynamicpv-ntfd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.19368322s
Oct 13 04:57:17.714: INFO: Pod "pod-subpath-test-dynamicpv-ntfd": Phase="Pending", Reason="", readiness=false. Elapsed: 4.291063148s
Oct 13 04:57:19.814: INFO: Pod "pod-subpath-test-dynamicpv-ntfd": Phase="Pending", Reason="", readiness=false. Elapsed: 6.390847978s
Oct 13 04:57:21.915: INFO: Pod "pod-subpath-test-dynamicpv-ntfd": Phase="Pending", Reason="", readiness=false. Elapsed: 8.492298653s
Oct 13 04:57:24.012: INFO: Pod "pod-subpath-test-dynamicpv-ntfd": Phase="Pending", Reason="", readiness=false. Elapsed: 10.589027596s
... skipping 2 lines ...
Oct 13 04:57:30.303: INFO: Pod "pod-subpath-test-dynamicpv-ntfd": Phase="Pending", Reason="", readiness=false. Elapsed: 16.880596268s
Oct 13 04:57:32.401: INFO: Pod "pod-subpath-test-dynamicpv-ntfd": Phase="Pending", Reason="", readiness=false. Elapsed: 18.977962355s
Oct 13 04:57:34.497: INFO: Pod "pod-subpath-test-dynamicpv-ntfd": Phase="Pending", Reason="", readiness=false. Elapsed: 21.074638465s
Oct 13 04:57:36.594: INFO: Pod "pod-subpath-test-dynamicpv-ntfd": Phase="Pending", Reason="", readiness=false. Elapsed: 23.171249552s
Oct 13 04:57:38.691: INFO: Pod "pod-subpath-test-dynamicpv-ntfd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 25.268612816s
STEP: Saw pod success
Oct 13 04:57:38.691: INFO: Pod "pod-subpath-test-dynamicpv-ntfd" satisfied condition "Succeeded or Failed"
Oct 13 04:57:38.788: INFO: Trying to get logs from node ip-172-20-45-187.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-ntfd container test-container-subpath-dynamicpv-ntfd: <nil>
STEP: delete the pod
Oct 13 04:57:38.990: INFO: Waiting for pod pod-subpath-test-dynamicpv-ntfd to disappear
Oct 13 04:57:39.085: INFO: Pod pod-subpath-test-dynamicpv-ntfd no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-ntfd
Oct 13 04:57:39.085: INFO: Deleting pod "pod-subpath-test-dynamicpv-ntfd" in namespace "provisioning-8423"
... skipping 115 lines ...

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

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 134 lines ...
Oct 13 04:57:47.312: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-8728gjr2b
STEP: creating a claim
Oct 13 04:57:47.409: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Oct 13 04:57:47.608: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Oct 13 04:57:47.804: INFO: Error updating pvc awshmkxz: PersistentVolumeClaim "awshmkxz" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8728gjr2b",
  	... // 3 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Oct 13 04:58:18.192: INFO: Error updating pvc awshmkxz: PersistentVolumeClaim "awshmkxz" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 187 lines ...
Oct 13 04:58:14.632: INFO: Waiting for pod aws-client to disappear
Oct 13 04:58:14.729: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Oct 13 04:58:14.729: INFO: Deleting PersistentVolumeClaim "pvc-drzqj"
Oct 13 04:58:14.826: INFO: Deleting PersistentVolume "aws-tln2d"
Oct 13 04:58:15.456: INFO: Couldn't delete PD "aws://eu-west-2a/vol-01f48f663971c42ea", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01f48f663971c42ea is currently attached to i-0466ff1ba288150de
	status code: 400, request id: 2836453b-a34f-44fa-ac56-8f04fe127d98
Oct 13 04:58:20.995: INFO: Successfully deleted PD "aws://eu-west-2a/vol-01f48f663971c42ea".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 04:58:20.995: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8125" for this suite.
... skipping 299 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.2A194ozXw/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.2A194ozXw/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.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 15 lines ...
Oct 13 04:57:05.579: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-6471x6hrc      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-6471    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-6471x6hrc,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-6471    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-6471x6hrc,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-6471    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-6471x6hrc,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-6471x6hrc    1850761f-6812-4a97-9190-00eccf032f8c 6037 0 2021-10-13 04:57:05 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-10-13 04:57:05 +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-f68j2 pvc- provisioning-6471  78a11064-3531-4e8f-a1a6-05fbeb718aee 6042 0 2021-10-13 04:57:06 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-10-13 04:57:06 +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-6471x6hrc,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-32067dc1-dcf9-4bd6-9b30-4fb706d21ba2 in namespace provisioning-6471
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Oct 13 04:57:20.647: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-nf28t" in namespace "provisioning-6471" to be "Succeeded or Failed"
Oct 13 04:57:20.756: INFO: Pod "pvc-volume-tester-writer-nf28t": Phase="Pending", Reason="", readiness=false. Elapsed: 108.898078ms
Oct 13 04:57:22.852: INFO: Pod "pvc-volume-tester-writer-nf28t": Phase="Pending", Reason="", readiness=false. Elapsed: 2.205281608s
Oct 13 04:57:24.948: INFO: Pod "pvc-volume-tester-writer-nf28t": Phase="Pending", Reason="", readiness=false. Elapsed: 4.30155094s
Oct 13 04:57:27.045: INFO: Pod "pvc-volume-tester-writer-nf28t": Phase="Pending", Reason="", readiness=false. Elapsed: 6.397795788s
Oct 13 04:57:29.142: INFO: Pod "pvc-volume-tester-writer-nf28t": Phase="Pending", Reason="", readiness=false. Elapsed: 8.495320222s
Oct 13 04:57:31.238: INFO: Pod "pvc-volume-tester-writer-nf28t": Phase="Pending", Reason="", readiness=false. Elapsed: 10.591453436s
... skipping 6 lines ...
Oct 13 04:57:45.920: INFO: Pod "pvc-volume-tester-writer-nf28t": Phase="Pending", Reason="", readiness=false. Elapsed: 25.272937216s
Oct 13 04:57:48.016: INFO: Pod "pvc-volume-tester-writer-nf28t": Phase="Pending", Reason="", readiness=false. Elapsed: 27.369686707s
Oct 13 04:57:50.114: INFO: Pod "pvc-volume-tester-writer-nf28t": Phase="Pending", Reason="", readiness=false. Elapsed: 29.466869242s
Oct 13 04:57:52.211: INFO: Pod "pvc-volume-tester-writer-nf28t": Phase="Pending", Reason="", readiness=false. Elapsed: 31.564006085s
Oct 13 04:57:54.307: INFO: Pod "pvc-volume-tester-writer-nf28t": Phase="Succeeded", Reason="", readiness=false. Elapsed: 33.660639536s
STEP: Saw pod success
Oct 13 04:57:54.308: INFO: Pod "pvc-volume-tester-writer-nf28t" satisfied condition "Succeeded or Failed"
Oct 13 04:57:54.515: INFO: Pod pvc-volume-tester-writer-nf28t has the following logs: 
Oct 13 04:57:54.515: INFO: Deleting pod "pvc-volume-tester-writer-nf28t" in namespace "provisioning-6471"
Oct 13 04:57:54.616: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-nf28t" 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-45-187.eu-west-2.compute.internal"
Oct 13 04:57:55.006: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-7f7nk" in namespace "provisioning-6471" to be "Succeeded or Failed"
Oct 13 04:57:55.106: INFO: Pod "pvc-volume-tester-reader-7f7nk": Phase="Pending", Reason="", readiness=false. Elapsed: 99.476983ms
Oct 13 04:57:57.203: INFO: Pod "pvc-volume-tester-reader-7f7nk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.196579735s
Oct 13 04:57:59.299: INFO: Pod "pvc-volume-tester-reader-7f7nk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.293043247s
STEP: Saw pod success
Oct 13 04:57:59.299: INFO: Pod "pvc-volume-tester-reader-7f7nk" satisfied condition "Succeeded or Failed"
Oct 13 04:57:59.493: INFO: Pod pvc-volume-tester-reader-7f7nk has the following logs: hello world

Oct 13 04:57:59.493: INFO: Deleting pod "pvc-volume-tester-reader-7f7nk" in namespace "provisioning-6471"
Oct 13 04:57:59.595: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-7f7nk" to be fully deleted
Oct 13 04:57:59.691: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-f68j2] to have phase Bound
Oct 13 04:57:59.787: INFO: PersistentVolumeClaim pvc-f68j2 found and phase=Bound (95.789552ms)
... skipping 218 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.2A194ozXw/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.2A194ozXw/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.2A194ozXw/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.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 598 lines ...
Oct 13 04:58:07.944: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-44652b6zm
STEP: creating a claim
Oct 13 04:58:08.043: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-kcpj
STEP: Creating a pod to test multi_subpath
Oct 13 04:58:08.338: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-kcpj" in namespace "provisioning-4465" to be "Succeeded or Failed"
Oct 13 04:58:08.436: INFO: Pod "pod-subpath-test-dynamicpv-kcpj": Phase="Pending", Reason="", readiness=false. Elapsed: 98.030836ms
Oct 13 04:58:10.533: INFO: Pod "pod-subpath-test-dynamicpv-kcpj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.195229096s
Oct 13 04:58:12.630: INFO: Pod "pod-subpath-test-dynamicpv-kcpj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.292090761s
Oct 13 04:58:14.729: INFO: Pod "pod-subpath-test-dynamicpv-kcpj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.391337659s
Oct 13 04:58:16.827: INFO: Pod "pod-subpath-test-dynamicpv-kcpj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.489109153s
Oct 13 04:58:18.924: INFO: Pod "pod-subpath-test-dynamicpv-kcpj": Phase="Pending", Reason="", readiness=false. Elapsed: 10.586082708s
Oct 13 04:58:21.024: INFO: Pod "pod-subpath-test-dynamicpv-kcpj": Phase="Pending", Reason="", readiness=false. Elapsed: 12.6859316s
Oct 13 04:58:23.124: INFO: Pod "pod-subpath-test-dynamicpv-kcpj": Phase="Pending", Reason="", readiness=false. Elapsed: 14.786004456s
Oct 13 04:58:25.222: INFO: Pod "pod-subpath-test-dynamicpv-kcpj": Phase="Pending", Reason="", readiness=false. Elapsed: 16.883877652s
Oct 13 04:58:27.334: INFO: Pod "pod-subpath-test-dynamicpv-kcpj": Phase="Pending", Reason="", readiness=false. Elapsed: 18.996333882s
Oct 13 04:58:29.432: INFO: Pod "pod-subpath-test-dynamicpv-kcpj": Phase="Pending", Reason="", readiness=false. Elapsed: 21.093926915s
Oct 13 04:58:31.529: INFO: Pod "pod-subpath-test-dynamicpv-kcpj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.190510649s
STEP: Saw pod success
Oct 13 04:58:31.529: INFO: Pod "pod-subpath-test-dynamicpv-kcpj" satisfied condition "Succeeded or Failed"
Oct 13 04:58:31.625: INFO: Trying to get logs from node ip-172-20-45-187.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-kcpj container test-container-subpath-dynamicpv-kcpj: <nil>
STEP: delete the pod
Oct 13 04:58:31.828: INFO: Waiting for pod pod-subpath-test-dynamicpv-kcpj to disappear
Oct 13 04:58:31.924: INFO: Pod pod-subpath-test-dynamicpv-kcpj no longer exists
STEP: Deleting pod
Oct 13 04:58:31.924: INFO: Deleting pod "pod-subpath-test-dynamicpv-kcpj" in namespace "provisioning-4465"
... skipping 227 lines ...
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 04:58:53.317: 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.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Oct 13 04:58:53.907: INFO: found topology map[topology.ebs.csi.aws.com/zone:eu-west-2a]
Oct 13 04:58:53.911: 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.886 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.2A194ozXw/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.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

    Not enough topologies in cluster -- skipping

    /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 78 lines ...
Oct 13 04:58:04.963: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1880-e2e-scr69fx
STEP: creating a claim
Oct 13 04:58:05.061: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-xk58
STEP: Creating a pod to test subpath
Oct 13 04:58:05.359: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-xk58" in namespace "provisioning-1880" to be "Succeeded or Failed"
Oct 13 04:58:05.456: INFO: Pod "pod-subpath-test-dynamicpv-xk58": Phase="Pending", Reason="", readiness=false. Elapsed: 97.036141ms
Oct 13 04:58:07.554: INFO: Pod "pod-subpath-test-dynamicpv-xk58": Phase="Pending", Reason="", readiness=false. Elapsed: 2.195129332s
Oct 13 04:58:09.665: INFO: Pod "pod-subpath-test-dynamicpv-xk58": Phase="Pending", Reason="", readiness=false. Elapsed: 4.30598557s
Oct 13 04:58:11.763: INFO: Pod "pod-subpath-test-dynamicpv-xk58": Phase="Pending", Reason="", readiness=false. Elapsed: 6.404423984s
Oct 13 04:58:13.863: INFO: Pod "pod-subpath-test-dynamicpv-xk58": Phase="Pending", Reason="", readiness=false. Elapsed: 8.504081203s
Oct 13 04:58:15.963: INFO: Pod "pod-subpath-test-dynamicpv-xk58": Phase="Pending", Reason="", readiness=false. Elapsed: 10.60375547s
Oct 13 04:58:18.061: INFO: Pod "pod-subpath-test-dynamicpv-xk58": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.702242423s
STEP: Saw pod success
Oct 13 04:58:18.061: INFO: Pod "pod-subpath-test-dynamicpv-xk58" satisfied condition "Succeeded or Failed"
Oct 13 04:58:18.159: INFO: Trying to get logs from node ip-172-20-62-14.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-xk58 container test-container-subpath-dynamicpv-xk58: <nil>
STEP: delete the pod
Oct 13 04:58:18.375: INFO: Waiting for pod pod-subpath-test-dynamicpv-xk58 to disappear
Oct 13 04:58:18.472: INFO: Pod pod-subpath-test-dynamicpv-xk58 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-xk58
Oct 13 04:58:18.472: INFO: Deleting pod "pod-subpath-test-dynamicpv-xk58" in namespace "provisioning-1880"
... skipping 143 lines ...

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

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

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

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 189 lines ...
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 04:59:14.486: 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.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Oct 13 04:59:15.072: INFO: found topology map[topology.kubernetes.io/zone:eu-west-2a]
Oct 13 04:59:15.072: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 13 04:59:15.072: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.2A194ozXw/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.2A194ozXw/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (immediate binding)] topology
    /tmp/kops.2A194ozXw/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.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 48 lines ...

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

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

    /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 50 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.2A194ozXw/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.2A194ozXw/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.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 80 lines ...
Oct 13 04:58:54.947: INFO: Pod aws-client still exists
Oct 13 04:58:56.948: INFO: Waiting for pod aws-client to disappear
Oct 13 04:58:57.045: INFO: Pod aws-client still exists
Oct 13 04:58:58.947: INFO: Waiting for pod aws-client to disappear
Oct 13 04:58:59.044: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Oct 13 04:58:59.243: INFO: Couldn't delete PD "aws://eu-west-2a/vol-08f7af3e90238c234", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08f7af3e90238c234 is currently attached to i-0466ff1ba288150de
	status code: 400, request id: 0dd46322-69e0-4fc6-94ab-cd285d92d2e5
Oct 13 04:59:04.749: INFO: Couldn't delete PD "aws://eu-west-2a/vol-08f7af3e90238c234", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08f7af3e90238c234 is currently attached to i-0466ff1ba288150de
	status code: 400, request id: 57e8f07e-551a-405f-b967-e9c3c8c2ea53
Oct 13 04:59:10.305: INFO: Couldn't delete PD "aws://eu-west-2a/vol-08f7af3e90238c234", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08f7af3e90238c234 is currently attached to i-0466ff1ba288150de
	status code: 400, request id: e59b20a5-5ece-4208-92fa-cefd5b0d737a
Oct 13 04:59:15.867: INFO: Successfully deleted PD "aws://eu-west-2a/vol-08f7af3e90238c234".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 04:59:15.867: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-4433" for this suite.
... skipping 93 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.2A194ozXw/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.2A194ozXw/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.2A194ozXw/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.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 11 lines ...
Oct 13 04:58:50.024: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-6248-e2e-scmwn5c
STEP: creating a claim
Oct 13 04:58:50.122: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Oct 13 04:58:50.316: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Oct 13 04:58:50.510: INFO: Error updating pvc ebs.csi.aws.comc4c4g: PersistentVolumeClaim "ebs.csi.aws.comc4c4g" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6248-e2e-scmwn5c",
  	... // 3 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Oct 13 04:59:20.913: INFO: Error updating pvc ebs.csi.aws.comc4c4g: PersistentVolumeClaim "ebs.csi.aws.comc4c4g" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 39 lines ...
Oct 13 04:58:22.854: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-2905-e2e-sc5zxwz
STEP: creating a claim
Oct 13 04:58:22.952: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-dxnz
STEP: Creating a pod to test exec-volume-test
Oct 13 04:58:23.240: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-dxnz" in namespace "volume-2905" to be "Succeeded or Failed"
Oct 13 04:58:23.336: INFO: Pod "exec-volume-test-dynamicpv-dxnz": Phase="Pending", Reason="", readiness=false. Elapsed: 95.619328ms
Oct 13 04:58:25.432: INFO: Pod "exec-volume-test-dynamicpv-dxnz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.191180276s
Oct 13 04:58:27.528: INFO: Pod "exec-volume-test-dynamicpv-dxnz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.287151408s
Oct 13 04:58:29.625: INFO: Pod "exec-volume-test-dynamicpv-dxnz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.384168548s
Oct 13 04:58:31.724: INFO: Pod "exec-volume-test-dynamicpv-dxnz": Phase="Pending", Reason="", readiness=false. Elapsed: 8.48347721s
Oct 13 04:58:33.819: INFO: Pod "exec-volume-test-dynamicpv-dxnz": Phase="Pending", Reason="", readiness=false. Elapsed: 10.57893898s
... skipping 10 lines ...
Oct 13 04:58:56.881: INFO: Pod "exec-volume-test-dynamicpv-dxnz": Phase="Pending", Reason="", readiness=false. Elapsed: 33.640845093s
Oct 13 04:58:58.977: INFO: Pod "exec-volume-test-dynamicpv-dxnz": Phase="Pending", Reason="", readiness=false. Elapsed: 35.737025874s
Oct 13 04:59:01.074: INFO: Pod "exec-volume-test-dynamicpv-dxnz": Phase="Pending", Reason="", readiness=false. Elapsed: 37.833856278s
Oct 13 04:59:03.170: INFO: Pod "exec-volume-test-dynamicpv-dxnz": Phase="Pending", Reason="", readiness=false. Elapsed: 39.930022759s
Oct 13 04:59:05.266: INFO: Pod "exec-volume-test-dynamicpv-dxnz": Phase="Succeeded", Reason="", readiness=false. Elapsed: 42.025738696s
STEP: Saw pod success
Oct 13 04:59:05.266: INFO: Pod "exec-volume-test-dynamicpv-dxnz" satisfied condition "Succeeded or Failed"
Oct 13 04:59:05.362: INFO: Trying to get logs from node ip-172-20-62-14.eu-west-2.compute.internal pod exec-volume-test-dynamicpv-dxnz container exec-container-dynamicpv-dxnz: <nil>
STEP: delete the pod
Oct 13 04:59:05.561: INFO: Waiting for pod exec-volume-test-dynamicpv-dxnz to disappear
Oct 13 04:59:05.657: INFO: Pod exec-volume-test-dynamicpv-dxnz no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-dxnz
Oct 13 04:59:05.657: INFO: Deleting pod "exec-volume-test-dynamicpv-dxnz" in namespace "volume-2905"
... skipping 49 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.2A194ozXw/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.2A194ozXw/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.2A194ozXw/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.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 121 lines ...
Oct 13 04:59:08.131: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Oct 13 04:59:08.803: INFO: Successfully created a new PD: "aws://eu-west-2a/vol-034dd38674a29ac12".
Oct 13 04:59:08.803: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-cqwx
STEP: Creating a pod to test exec-volume-test
Oct 13 04:59:08.903: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-cqwx" in namespace "volume-5898" to be "Succeeded or Failed"
Oct 13 04:59:09.000: INFO: Pod "exec-volume-test-inlinevolume-cqwx": Phase="Pending", Reason="", readiness=false. Elapsed: 97.041941ms
Oct 13 04:59:11.099: INFO: Pod "exec-volume-test-inlinevolume-cqwx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.1964639s
Oct 13 04:59:13.197: INFO: Pod "exec-volume-test-inlinevolume-cqwx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.294175218s
Oct 13 04:59:15.295: INFO: Pod "exec-volume-test-inlinevolume-cqwx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.392720242s
STEP: Saw pod success
Oct 13 04:59:15.295: INFO: Pod "exec-volume-test-inlinevolume-cqwx" satisfied condition "Succeeded or Failed"
Oct 13 04:59:15.395: INFO: Trying to get logs from node ip-172-20-62-14.eu-west-2.compute.internal pod exec-volume-test-inlinevolume-cqwx container exec-container-inlinevolume-cqwx: <nil>
STEP: delete the pod
Oct 13 04:59:15.601: INFO: Waiting for pod exec-volume-test-inlinevolume-cqwx to disappear
Oct 13 04:59:15.700: INFO: Pod exec-volume-test-inlinevolume-cqwx no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-cqwx
Oct 13 04:59:15.700: INFO: Deleting pod "exec-volume-test-inlinevolume-cqwx" in namespace "volume-5898"
Oct 13 04:59:16.043: INFO: Couldn't delete PD "aws://eu-west-2a/vol-034dd38674a29ac12", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-034dd38674a29ac12 is currently attached to i-0cd8e7c27c713b3cc
	status code: 400, request id: 9505270d-0438-4211-aacb-c199fa26df97
Oct 13 04:59:21.576: INFO: Couldn't delete PD "aws://eu-west-2a/vol-034dd38674a29ac12", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-034dd38674a29ac12 is currently attached to i-0cd8e7c27c713b3cc
	status code: 400, request id: eda20198-22e4-4094-8f3e-342dfd54cdb2
Oct 13 04:59:27.128: INFO: Successfully deleted PD "aws://eu-west-2a/vol-034dd38674a29ac12".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 04:59:27.128: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-5898" for this suite.
... skipping 43 lines ...
Oct 13 04:58:56.263: INFO: Creating resource for dynamic PV
Oct 13 04:58:56.263: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-6777-e2e-sc7hncv
STEP: creating a claim
STEP: Expanding non-expandable pvc
Oct 13 04:58:56.557: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Oct 13 04:58:56.754: INFO: Error updating pvc ebs.csi.aws.comhfbcs: PersistentVolumeClaim "ebs.csi.aws.comhfbcs" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6777-e2e-sc7hncv",
  	... // 3 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Oct 13 04:59:27.164: INFO: Error updating pvc ebs.csi.aws.comhfbcs: PersistentVolumeClaim "ebs.csi.aws.comhfbcs" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 69 lines ...
STEP: Deleting pod hostexec-ip-172-20-53-241.eu-west-2.compute.internal-8tqll in namespace volumemode-650
Oct 13 04:59:14.283: INFO: Deleting pod "pod-08897c73-13e8-4626-99d9-5bb9d8c95de5" in namespace "volumemode-650"
Oct 13 04:59:14.381: INFO: Wait up to 5m0s for pod "pod-08897c73-13e8-4626-99d9-5bb9d8c95de5" to be fully deleted
STEP: Deleting pv and pvc
Oct 13 04:59:16.577: INFO: Deleting PersistentVolumeClaim "pvc-cpjwh"
Oct 13 04:59:16.674: INFO: Deleting PersistentVolume "aws-v8rxt"
Oct 13 04:59:16.990: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0e096f86eb55d048b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e096f86eb55d048b is currently attached to i-04c4fbfe2ad884963
	status code: 400, request id: 267720f1-107d-4e49-9613-315c8250205a
Oct 13 04:59:22.548: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0e096f86eb55d048b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e096f86eb55d048b is currently attached to i-04c4fbfe2ad884963
	status code: 400, request id: c96846c6-13c9-4021-b6cc-748fb7701523
Oct 13 04:59:28.090: INFO: Successfully deleted PD "aws://eu-west-2a/vol-0e096f86eb55d048b".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 04:59:28.090: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-650" for this suite.
... skipping 49 lines ...

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

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 69 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 04:59:15.102: 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.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Oct 13 04:59:15.587: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Oct 13 04:59:16.281: INFO: Successfully created a new PD: "aws://eu-west-2a/vol-024a90a986c52f356".
Oct 13 04:59:16.281: INFO: Creating resource for pre-provisioned PV
Oct 13 04:59:16.281: INFO: Creating PVC and PV
... skipping 4 lines ...
Oct 13 04:59:18.673: INFO: PersistentVolumeClaim pvc-4mvnr found but phase is Pending instead of Bound.
Oct 13 04:59:20.773: INFO: PersistentVolumeClaim pvc-4mvnr found but phase is Pending instead of Bound.
Oct 13 04:59:22.870: INFO: PersistentVolumeClaim pvc-4mvnr found and phase=Bound (6.391882127s)
Oct 13 04:59:22.870: INFO: Waiting up to 3m0s for PersistentVolume aws-x48jk to have phase Bound
Oct 13 04:59:22.967: INFO: PersistentVolume aws-x48jk found and phase=Bound (96.777523ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Oct 13 04:59:25.548: INFO: Deleting pod "pod-42a6513c-5267-4282-8d2c-032d16f2696b" in namespace "volumemode-3758"
Oct 13 04:59:25.645: INFO: Wait up to 5m0s for pod "pod-42a6513c-5267-4282-8d2c-032d16f2696b" to be fully deleted
STEP: Deleting pv and pvc
Oct 13 04:59:27.839: INFO: Deleting PersistentVolumeClaim "pvc-4mvnr"
Oct 13 04:59:27.953: INFO: Deleting PersistentVolume "aws-x48jk"
Oct 13 04:59:28.242: INFO: Couldn't delete PD "aws://eu-west-2a/vol-024a90a986c52f356", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-024a90a986c52f356 is currently attached to i-0a4eb7973d6932982
	status code: 400, request id: 84762fa7-643d-40c4-8cbc-0287eab6d536
Oct 13 04:59:33.758: INFO: Couldn't delete PD "aws://eu-west-2a/vol-024a90a986c52f356", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-024a90a986c52f356 is currently attached to i-0a4eb7973d6932982
	status code: 400, request id: 5aa2950d-a853-4c17-83e0-e3e96115b8ac
Oct 13 04:59:39.265: INFO: Couldn't delete PD "aws://eu-west-2a/vol-024a90a986c52f356", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-024a90a986c52f356 is currently attached to i-0a4eb7973d6932982
	status code: 400, request id: 3900c8b9-1b08-431a-9539-3b5d009263d5
Oct 13 04:59:44.830: INFO: Successfully deleted PD "aws://eu-west-2a/vol-024a90a986c52f356".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 04:59:44.830: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-3758" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.2A194ozXw/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.2A194ozXw/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
    /tmp/kops.2A194ozXw/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.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Oct 13 04:59:45.028: INFO: Driver "ebs.csi.aws.com" does not support volume type "PreprovisionedPV" - skipping
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
... skipping 2 lines ...

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 2 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 04:59:16.067: 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.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Oct 13 04:59:16.553: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 13 04:59:16.553: INFO: Creating resource for dynamic PV
Oct 13 04:59:16.553: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-36875mvwk
STEP: creating a claim
Oct 13 04:59:16.650: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-jn67
STEP: Checking for subpath error in container status
Oct 13 04:59:41.136: INFO: Deleting pod "pod-subpath-test-dynamicpv-jn67" in namespace "provisioning-3687"
Oct 13 04:59:41.236: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-jn67" to be fully deleted
STEP: Deleting pod
Oct 13 04:59:43.430: INFO: Deleting pod "pod-subpath-test-dynamicpv-jn67" in namespace "provisioning-3687"
STEP: Deleting pvc
Oct 13 04:59:43.721: INFO: Deleting PersistentVolumeClaim "aws46lvw"
... skipping 12 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.2A194ozXw/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.2A194ozXw/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath file is outside the volume [Slow][LinuxOnly]
      /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Oct 13 04:59:54.405: INFO: Driver supports dynamic provisioning, skipping PreprovisionedPV pattern
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
... skipping 544 lines ...
STEP: Deleting pod aws-client in namespace volume-1071
Oct 13 04:59:42.267: INFO: Waiting for pod aws-client to disappear
Oct 13 04:59:42.365: INFO: Pod aws-client still exists
Oct 13 04:59:44.366: INFO: Waiting for pod aws-client to disappear
Oct 13 04:59:44.462: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Oct 13 04:59:44.645: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0fad8520ac4829c5c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0fad8520ac4829c5c is currently attached to i-0a4eb7973d6932982
	status code: 400, request id: a4700519-5388-42b8-a548-37e852d02ccb
Oct 13 04:59:50.203: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0fad8520ac4829c5c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0fad8520ac4829c5c is currently attached to i-0a4eb7973d6932982
	status code: 400, request id: e484cc6e-0d43-425d-99d7-c14f632af9c2
Oct 13 04:59:55.770: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0fad8520ac4829c5c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0fad8520ac4829c5c is currently attached to i-0a4eb7973d6932982
	status code: 400, request id: d428224a-a0b7-47a2-937b-135f537e3b6e
Oct 13 05:00:01.304: INFO: Successfully deleted PD "aws://eu-west-2a/vol-0fad8520ac4829c5c".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 05:00:01.304: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-1071" for this suite.
... skipping 205 lines ...
Oct 13 04:59:40.083: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-6899zhhg
STEP: creating a claim
Oct 13 04:59:40.180: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-9zt7
STEP: Creating a pod to test exec-volume-test
Oct 13 04:59:40.474: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-9zt7" in namespace "volume-689" to be "Succeeded or Failed"
Oct 13 04:59:40.570: INFO: Pod "exec-volume-test-dynamicpv-9zt7": Phase="Pending", Reason="", readiness=false. Elapsed: 95.90125ms
Oct 13 04:59:42.667: INFO: Pod "exec-volume-test-dynamicpv-9zt7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.192806976s
Oct 13 04:59:44.763: INFO: Pod "exec-volume-test-dynamicpv-9zt7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.289051614s
Oct 13 04:59:46.863: INFO: Pod "exec-volume-test-dynamicpv-9zt7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.388664669s
Oct 13 04:59:48.960: INFO: Pod "exec-volume-test-dynamicpv-9zt7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.485844947s
Oct 13 04:59:51.057: INFO: Pod "exec-volume-test-dynamicpv-9zt7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.583111572s
STEP: Saw pod success
Oct 13 04:59:51.057: INFO: Pod "exec-volume-test-dynamicpv-9zt7" satisfied condition "Succeeded or Failed"
Oct 13 04:59:51.153: INFO: Trying to get logs from node ip-172-20-48-140.eu-west-2.compute.internal pod exec-volume-test-dynamicpv-9zt7 container exec-container-dynamicpv-9zt7: <nil>
STEP: delete the pod
Oct 13 04:59:51.361: INFO: Waiting for pod exec-volume-test-dynamicpv-9zt7 to disappear
Oct 13 04:59:51.456: INFO: Pod exec-volume-test-dynamicpv-9zt7 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-9zt7
Oct 13 04:59:51.456: INFO: Deleting pod "exec-volume-test-dynamicpv-9zt7" in namespace "volume-689"
... skipping 273 lines ...
Oct 13 04:59:50.044: INFO: PersistentVolumeClaim pvc-n9mhs found but phase is Pending instead of Bound.
Oct 13 04:59:52.140: INFO: PersistentVolumeClaim pvc-n9mhs found and phase=Bound (12.691143285s)
Oct 13 04:59:52.140: INFO: Waiting up to 3m0s for PersistentVolume aws-8np56 to have phase Bound
Oct 13 04:59:52.237: INFO: PersistentVolume aws-8np56 found and phase=Bound (96.202529ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-6kzk
STEP: Creating a pod to test exec-volume-test
Oct 13 04:59:52.529: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-6kzk" in namespace "volume-517" to be "Succeeded or Failed"
Oct 13 04:59:52.625: INFO: Pod "exec-volume-test-preprovisionedpv-6kzk": Phase="Pending", Reason="", readiness=false. Elapsed: 96.224367ms
Oct 13 04:59:54.722: INFO: Pod "exec-volume-test-preprovisionedpv-6kzk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.192807839s
Oct 13 04:59:56.819: INFO: Pod "exec-volume-test-preprovisionedpv-6kzk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.289764383s
Oct 13 04:59:58.917: INFO: Pod "exec-volume-test-preprovisionedpv-6kzk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.387382556s
STEP: Saw pod success
Oct 13 04:59:58.917: INFO: Pod "exec-volume-test-preprovisionedpv-6kzk" satisfied condition "Succeeded or Failed"
Oct 13 04:59:59.013: INFO: Trying to get logs from node ip-172-20-48-140.eu-west-2.compute.internal pod exec-volume-test-preprovisionedpv-6kzk container exec-container-preprovisionedpv-6kzk: <nil>
STEP: delete the pod
Oct 13 04:59:59.212: INFO: Waiting for pod exec-volume-test-preprovisionedpv-6kzk to disappear
Oct 13 04:59:59.309: INFO: Pod exec-volume-test-preprovisionedpv-6kzk no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-6kzk
Oct 13 04:59:59.309: INFO: Deleting pod "exec-volume-test-preprovisionedpv-6kzk" in namespace "volume-517"
STEP: Deleting pv and pvc
Oct 13 04:59:59.405: INFO: Deleting PersistentVolumeClaim "pvc-n9mhs"
Oct 13 04:59:59.502: INFO: Deleting PersistentVolume "aws-8np56"
Oct 13 04:59:59.840: INFO: Couldn't delete PD "aws://eu-west-2a/vol-080f54a418330e3ab", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-080f54a418330e3ab is currently attached to i-0466ff1ba288150de
	status code: 400, request id: bcc3c34a-d772-46dd-ad0b-8dea5827013f
Oct 13 05:00:05.406: INFO: Couldn't delete PD "aws://eu-west-2a/vol-080f54a418330e3ab", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-080f54a418330e3ab is currently attached to i-0466ff1ba288150de
	status code: 400, request id: 8d37a91c-67e7-499a-bc9c-2bdc23808f01
Oct 13 05:00:11.009: INFO: Successfully deleted PD "aws://eu-west-2a/vol-080f54a418330e3ab".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 05:00:11.009: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-517" for this suite.
... skipping 171 lines ...
Oct 13 04:59:28.773: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-9060h9pkv
STEP: creating a claim
Oct 13 04:59:28.870: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-m9nn
STEP: Creating a pod to test exec-volume-test
Oct 13 04:59:29.164: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-m9nn" in namespace "volume-9060" to be "Succeeded or Failed"
Oct 13 04:59:29.261: INFO: Pod "exec-volume-test-dynamicpv-m9nn": Phase="Pending", Reason="", readiness=false. Elapsed: 96.442616ms
Oct 13 04:59:31.358: INFO: Pod "exec-volume-test-dynamicpv-m9nn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.193567976s
Oct 13 04:59:33.460: INFO: Pod "exec-volume-test-dynamicpv-m9nn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.295610469s
Oct 13 04:59:35.558: INFO: Pod "exec-volume-test-dynamicpv-m9nn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.393403754s
Oct 13 04:59:37.654: INFO: Pod "exec-volume-test-dynamicpv-m9nn": Phase="Pending", Reason="", readiness=false. Elapsed: 8.490162015s
Oct 13 04:59:39.753: INFO: Pod "exec-volume-test-dynamicpv-m9nn": Phase="Pending", Reason="", readiness=false. Elapsed: 10.589012922s
... skipping 3 lines ...
Oct 13 04:59:48.144: INFO: Pod "exec-volume-test-dynamicpv-m9nn": Phase="Pending", Reason="", readiness=false. Elapsed: 18.979423522s
Oct 13 04:59:50.240: INFO: Pod "exec-volume-test-dynamicpv-m9nn": Phase="Pending", Reason="", readiness=false. Elapsed: 21.076040467s
Oct 13 04:59:52.336: INFO: Pod "exec-volume-test-dynamicpv-m9nn": Phase="Pending", Reason="", readiness=false. Elapsed: 23.172218503s
Oct 13 04:59:54.433: INFO: Pod "exec-volume-test-dynamicpv-m9nn": Phase="Pending", Reason="", readiness=false. Elapsed: 25.268469914s
Oct 13 04:59:56.530: INFO: Pod "exec-volume-test-dynamicpv-m9nn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 27.365506375s
STEP: Saw pod success
Oct 13 04:59:56.530: INFO: Pod "exec-volume-test-dynamicpv-m9nn" satisfied condition "Succeeded or Failed"
Oct 13 04:59:56.627: INFO: Trying to get logs from node ip-172-20-45-187.eu-west-2.compute.internal pod exec-volume-test-dynamicpv-m9nn container exec-container-dynamicpv-m9nn: <nil>
STEP: delete the pod
Oct 13 04:59:56.827: INFO: Waiting for pod exec-volume-test-dynamicpv-m9nn to disappear
Oct 13 04:59:56.924: INFO: Pod exec-volume-test-dynamicpv-m9nn no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-m9nn
Oct 13 04:59:56.924: INFO: Deleting pod "exec-volume-test-dynamicpv-m9nn" in namespace "volume-9060"
... skipping 48 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 04:59:54.414: 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.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Oct 13 04:59:54.915: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 13 04:59:54.915: INFO: Creating resource for dynamic PV
Oct 13 04:59:54.915: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-2778p6jp8
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Oct 13 05:00:01.601: INFO: Deleting pod "pod-883f6556-f09b-4b61-bfba-1f03ca766fd6" in namespace "volumemode-2778"
Oct 13 05:00:01.721: INFO: Wait up to 5m0s for pod "pod-883f6556-f09b-4b61-bfba-1f03ca766fd6" to be fully deleted
STEP: Deleting pvc
Oct 13 05:00:04.111: INFO: Deleting PersistentVolumeClaim "aws8tt5s"
Oct 13 05:00:04.209: INFO: Waiting up to 5m0s for PersistentVolume pvc-61742f6c-94ff-42c3-9ae0-945f73141eda to get deleted
Oct 13 05:00:04.306: INFO: PersistentVolume pvc-61742f6c-94ff-42c3-9ae0-945f73141eda found and phase=Released (96.577288ms)
... skipping 13 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.2A194ozXw/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.2A194ozXw/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
    /tmp/kops.2A194ozXw/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.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Oct 13 05:00:30.088: INFO: Driver ebs.csi.aws.com doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
... skipping 2 lines ...

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

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

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.2A194ozXw/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.2A194ozXw/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.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 30 lines ...
Oct 13 04:59:27.841: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8584-e2e-sctrmqz
STEP: creating a claim
Oct 13 04:59:27.943: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-cwz7
STEP: Creating a pod to test subpath
Oct 13 04:59:28.238: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-cwz7" in namespace "provisioning-8584" to be "Succeeded or Failed"
Oct 13 04:59:28.335: INFO: Pod "pod-subpath-test-dynamicpv-cwz7": Phase="Pending", Reason="", readiness=false. Elapsed: 97.040405ms
Oct 13 04:59:30.434: INFO: Pod "pod-subpath-test-dynamicpv-cwz7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.196373064s
Oct 13 04:59:32.573: INFO: Pod "pod-subpath-test-dynamicpv-cwz7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.33495006s
Oct 13 04:59:34.671: INFO: Pod "pod-subpath-test-dynamicpv-cwz7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.432586446s
Oct 13 04:59:36.770: INFO: Pod "pod-subpath-test-dynamicpv-cwz7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.531590935s
Oct 13 04:59:38.868: INFO: Pod "pod-subpath-test-dynamicpv-cwz7": Phase="Pending", Reason="", readiness=false. Elapsed: 10.629515744s
... skipping 2 lines ...
Oct 13 04:59:45.161: INFO: Pod "pod-subpath-test-dynamicpv-cwz7": Phase="Pending", Reason="", readiness=false. Elapsed: 16.923185391s
Oct 13 04:59:47.260: INFO: Pod "pod-subpath-test-dynamicpv-cwz7": Phase="Pending", Reason="", readiness=false. Elapsed: 19.022177074s
Oct 13 04:59:49.359: INFO: Pod "pod-subpath-test-dynamicpv-cwz7": Phase="Pending", Reason="", readiness=false. Elapsed: 21.120783868s
Oct 13 04:59:51.456: INFO: Pod "pod-subpath-test-dynamicpv-cwz7": Phase="Pending", Reason="", readiness=false. Elapsed: 23.21839872s
Oct 13 04:59:53.555: INFO: Pod "pod-subpath-test-dynamicpv-cwz7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 25.316508195s
STEP: Saw pod success
Oct 13 04:59:53.555: INFO: Pod "pod-subpath-test-dynamicpv-cwz7" satisfied condition "Succeeded or Failed"
Oct 13 04:59:53.652: INFO: Trying to get logs from node ip-172-20-45-187.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-cwz7 container test-container-subpath-dynamicpv-cwz7: <nil>
STEP: delete the pod
Oct 13 04:59:53.855: INFO: Waiting for pod pod-subpath-test-dynamicpv-cwz7 to disappear
Oct 13 04:59:53.954: INFO: Pod pod-subpath-test-dynamicpv-cwz7 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-cwz7
Oct 13 04:59:53.954: INFO: Deleting pod "pod-subpath-test-dynamicpv-cwz7" in namespace "provisioning-8584"
... skipping 92 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.2A194ozXw/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.2A194ozXw/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.2A194ozXw/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.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 290 lines ...
Oct 13 04:59:28.858: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8585-e2e-sctq942
STEP: creating a claim
Oct 13 04:59:28.955: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-cpwk
STEP: Creating a pod to test multi_subpath
Oct 13 04:59:29.249: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-cpwk" in namespace "provisioning-8585" to be "Succeeded or Failed"
Oct 13 04:59:29.346: INFO: Pod "pod-subpath-test-dynamicpv-cpwk": Phase="Pending", Reason="", readiness=false. Elapsed: 97.079094ms
Oct 13 04:59:31.453: INFO: Pod "pod-subpath-test-dynamicpv-cpwk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.203778477s
Oct 13 04:59:33.552: INFO: Pod "pod-subpath-test-dynamicpv-cpwk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.303353614s
Oct 13 04:59:35.650: INFO: Pod "pod-subpath-test-dynamicpv-cpwk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.40084766s
Oct 13 04:59:37.748: INFO: Pod "pod-subpath-test-dynamicpv-cpwk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.499167895s
Oct 13 04:59:39.847: INFO: Pod "pod-subpath-test-dynamicpv-cpwk": Phase="Pending", Reason="", readiness=false. Elapsed: 10.597792687s
... skipping 5 lines ...
Oct 13 04:59:52.443: INFO: Pod "pod-subpath-test-dynamicpv-cpwk": Phase="Pending", Reason="", readiness=false. Elapsed: 23.193650453s
Oct 13 04:59:54.541: INFO: Pod "pod-subpath-test-dynamicpv-cpwk": Phase="Pending", Reason="", readiness=false. Elapsed: 25.291818634s
Oct 13 04:59:56.639: INFO: Pod "pod-subpath-test-dynamicpv-cpwk": Phase="Pending", Reason="", readiness=false. Elapsed: 27.390084565s
Oct 13 04:59:58.738: INFO: Pod "pod-subpath-test-dynamicpv-cpwk": Phase="Pending", Reason="", readiness=false. Elapsed: 29.488622457s
Oct 13 05:00:00.836: INFO: Pod "pod-subpath-test-dynamicpv-cpwk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 31.587234706s
STEP: Saw pod success
Oct 13 05:00:00.836: INFO: Pod "pod-subpath-test-dynamicpv-cpwk" satisfied condition "Succeeded or Failed"
Oct 13 05:00:00.937: INFO: Trying to get logs from node ip-172-20-45-187.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-cpwk container test-container-subpath-dynamicpv-cpwk: <nil>
STEP: delete the pod
Oct 13 05:00:01.142: INFO: Waiting for pod pod-subpath-test-dynamicpv-cpwk to disappear
Oct 13 05:00:01.240: INFO: Pod pod-subpath-test-dynamicpv-cpwk no longer exists
STEP: Deleting pod
Oct 13 05:00:01.240: INFO: Deleting pod "pod-subpath-test-dynamicpv-cpwk" in namespace "provisioning-8585"
... skipping 32 lines ...

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

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

    /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 403 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 05:00:05.914: 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.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Oct 13 05:00:06.392: INFO: Creating resource for dynamic PV
Oct 13 05:00:06.392: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2423-e2e-scgk278
STEP: creating a claim
Oct 13 05:00:06.489: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-fcjb
STEP: Checking for subpath error in container status
Oct 13 05:00:22.981: INFO: Deleting pod "pod-subpath-test-dynamicpv-fcjb" in namespace "provisioning-2423"
Oct 13 05:00:23.080: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-fcjb" to be fully deleted
STEP: Deleting pod
Oct 13 05:00:25.274: INFO: Deleting pod "pod-subpath-test-dynamicpv-fcjb" in namespace "provisioning-2423"
STEP: Deleting pvc
Oct 13 05:00:25.566: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.commfp76"
... skipping 12 lines ...

• [SLOW TEST:40.567 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath directory is outside the volume [Slow][LinuxOnly]
    /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 59 lines ...
Oct 13 05:00:32.859: INFO: Waiting for pod aws-client to disappear
Oct 13 05:00:32.956: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Oct 13 05:00:32.956: INFO: Deleting PersistentVolumeClaim "pvc-6fj9r"
Oct 13 05:00:33.057: INFO: Deleting PersistentVolume "aws-56whx"
Oct 13 05:00:33.670: INFO: Couldn't delete PD "aws://eu-west-2a/vol-055538d8c56188d69", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-055538d8c56188d69 is currently attached to i-0a4eb7973d6932982
	status code: 400, request id: 17e91edf-99ba-48ee-a4c2-23d47d843427
Oct 13 05:00:39.173: INFO: Couldn't delete PD "aws://eu-west-2a/vol-055538d8c56188d69", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-055538d8c56188d69 is currently attached to i-0a4eb7973d6932982
	status code: 400, request id: 9096164b-95eb-4458-b6c0-ae967cf86ea7
Oct 13 05:00:44.659: INFO: Couldn't delete PD "aws://eu-west-2a/vol-055538d8c56188d69", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-055538d8c56188d69 is currently attached to i-0a4eb7973d6932982
	status code: 400, request id: 50ebea3a-56b8-4bbf-ba80-f1ccd593c09d
Oct 13 05:00:50.210: INFO: Successfully deleted PD "aws://eu-west-2a/vol-055538d8c56188d69".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 05:00:50.210: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-5695" for this suite.
... skipping 22 lines ...
Oct 13 04:59:56.174: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Oct 13 04:59:56.885: INFO: Successfully created a new PD: "aws://eu-west-2a/vol-0ee9687281f37294d".
Oct 13 04:59:56.885: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-c24g
STEP: Creating a pod to test exec-volume-test
Oct 13 04:59:56.984: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-c24g" in namespace "volume-9622" to be "Succeeded or Failed"
Oct 13 04:59:57.081: INFO: Pod "exec-volume-test-inlinevolume-c24g": Phase="Pending", Reason="", readiness=false. Elapsed: 95.993202ms
Oct 13 04:59:59.178: INFO: Pod "exec-volume-test-inlinevolume-c24g": Phase="Pending", Reason="", readiness=false. Elapsed: 2.193812443s
Oct 13 05:00:01.276: INFO: Pod "exec-volume-test-inlinevolume-c24g": Phase="Pending", Reason="", readiness=false. Elapsed: 4.291362563s
Oct 13 05:00:03.373: INFO: Pod "exec-volume-test-inlinevolume-c24g": Phase="Pending", Reason="", readiness=false. Elapsed: 6.388623014s
Oct 13 05:00:05.470: INFO: Pod "exec-volume-test-inlinevolume-c24g": Phase="Pending", Reason="", readiness=false. Elapsed: 8.485293044s
Oct 13 05:00:07.569: INFO: Pod "exec-volume-test-inlinevolume-c24g": Phase="Pending", Reason="", readiness=false. Elapsed: 10.584161274s
... skipping 7 lines ...
Oct 13 05:00:24.341: INFO: Pod "exec-volume-test-inlinevolume-c24g": Phase="Pending", Reason="", readiness=false. Elapsed: 27.35680974s
Oct 13 05:00:26.439: INFO: Pod "exec-volume-test-inlinevolume-c24g": Phase="Pending", Reason="", readiness=false. Elapsed: 29.454365438s
Oct 13 05:00:28.535: INFO: Pod "exec-volume-test-inlinevolume-c24g": Phase="Pending", Reason="", readiness=false. Elapsed: 31.55086167s
Oct 13 05:00:30.635: INFO: Pod "exec-volume-test-inlinevolume-c24g": Phase="Pending", Reason="", readiness=false. Elapsed: 33.650613819s
Oct 13 05:00:32.732: INFO: Pod "exec-volume-test-inlinevolume-c24g": Phase="Succeeded", Reason="", readiness=false. Elapsed: 35.747602858s
STEP: Saw pod success
Oct 13 05:00:32.732: INFO: Pod "exec-volume-test-inlinevolume-c24g" satisfied condition "Succeeded or Failed"
Oct 13 05:00:32.830: INFO: Trying to get logs from node ip-172-20-45-187.eu-west-2.compute.internal pod exec-volume-test-inlinevolume-c24g container exec-container-inlinevolume-c24g: <nil>
STEP: delete the pod
Oct 13 05:00:33.028: INFO: Waiting for pod exec-volume-test-inlinevolume-c24g to disappear
Oct 13 05:00:33.124: INFO: Pod exec-volume-test-inlinevolume-c24g no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-c24g
Oct 13 05:00:33.124: INFO: Deleting pod "exec-volume-test-inlinevolume-c24g" in namespace "volume-9622"
Oct 13 05:00:33.439: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0ee9687281f37294d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ee9687281f37294d is currently attached to i-0a4eb7973d6932982
	status code: 400, request id: 521e5b56-3fd9-4e12-8e0d-28c6fb0fdcb5
Oct 13 05:00:39.002: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0ee9687281f37294d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ee9687281f37294d is currently attached to i-0a4eb7973d6932982
	status code: 400, request id: efa428bc-6609-4354-9e41-1376084ef19b
Oct 13 05:00:44.581: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0ee9687281f37294d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ee9687281f37294d is currently attached to i-0a4eb7973d6932982
	status code: 400, request id: aadc631e-3f17-4180-9949-2b9c17feb18c
Oct 13 05:00:50.119: INFO: Couldn't delete PD "aws://eu-west-2a/vol-0ee9687281f37294d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ee9687281f37294d is currently attached to i-0a4eb7973d6932982
	status code: 400, request id: 36123a7f-d7b2-47f0-a676-cfd4b073de62
Oct 13 05:00:55.629: INFO: Successfully deleted PD "aws://eu-west-2a/vol-0ee9687281f37294d".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 05:00:55.629: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-9622" for this suite.
... skipping 73 lines ...
Oct 13 05:00:44.558: INFO: Waiting for pod aws-client to disappear
Oct 13 05:00:44.656: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Oct 13 05:00:44.656: INFO: Deleting PersistentVolumeClaim "pvc-mlpzq"
Oct 13 05:00:44.755: INFO: Deleting PersistentVolume "aws-8x8hc"
Oct 13 05:00:45.458: INFO: Couldn't delete PD "aws://eu-west-2a/vol-05c916b99b0e09032", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05c916b99b0e09032 is currently attached to i-0a4eb7973d6932982
	status code: 400, request id: 472065a1-3025-4966-9b85-8f1a8700ba89
Oct 13 05:00:51.029: INFO: Couldn't delete PD "aws://eu-west-2a/vol-05c916b99b0e09032", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05c916b99b0e09032 is currently attached to i-0a4eb7973d6932982
	status code: 400, request id: b79a15bd-c898-4b18-bb8b-1b4cfe5a2552
Oct 13 05:00:56.569: INFO: Successfully deleted PD "aws://eu-west-2a/vol-05c916b99b0e09032".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumes
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 05:00:56.569: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-5723" for this suite.
... skipping 196 lines ...
Oct 13 04:59:56.950: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7329-e2e-scwtd5f
STEP: creating a claim
Oct 13 04:59:57.050: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-wbpp
STEP: Creating a pod to test atomic-volume-subpath
Oct 13 04:59:57.375: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-wbpp" in namespace "provisioning-7329" to be "Succeeded or Failed"
Oct 13 04:59:57.472: INFO: Pod "pod-subpath-test-dynamicpv-wbpp": Phase="Pending", Reason="", readiness=false. Elapsed: 96.9399ms
Oct 13 04:59:59.570: INFO: Pod "pod-subpath-test-dynamicpv-wbpp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.194674816s
Oct 13 05:00:01.675: INFO: Pod "pod-subpath-test-dynamicpv-wbpp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.300593094s
Oct 13 05:00:03.772: INFO: Pod "pod-subpath-test-dynamicpv-wbpp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.397374689s
Oct 13 05:00:05.869: INFO: Pod "pod-subpath-test-dynamicpv-wbpp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.494234809s
Oct 13 05:00:07.967: INFO: Pod "pod-subpath-test-dynamicpv-wbpp": Phase="Pending", Reason="", readiness=false. Elapsed: 10.591826202s
... skipping 11 lines ...
Oct 13 05:00:33.135: INFO: Pod "pod-subpath-test-dynamicpv-wbpp": Phase="Running", Reason="", readiness=true. Elapsed: 35.760252806s
Oct 13 05:00:35.233: INFO: Pod "pod-subpath-test-dynamicpv-wbpp": Phase="Running", Reason="", readiness=true. Elapsed: 37.858523192s
Oct 13 05:00:37.331: INFO: Pod "pod-subpath-test-dynamicpv-wbpp": Phase="Running", Reason="", readiness=true. Elapsed: 39.956259109s
Oct 13 05:00:39.428: INFO: Pod "pod-subpath-test-dynamicpv-wbpp": Phase="Running", Reason="", readiness=true. Elapsed: 42.053179779s
Oct 13 05:00:41.526: INFO: Pod "pod-subpath-test-dynamicpv-wbpp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 44.150664045s
STEP: Saw pod success
Oct 13 05:00:41.526: INFO: Pod "pod-subpath-test-dynamicpv-wbpp" satisfied condition "Succeeded or Failed"
Oct 13 05:00:41.622: INFO: Trying to get logs from node ip-172-20-62-14.eu-west-2.compute.internal pod pod-subpath-test-dynamicpv-wbpp container test-container-subpath-dynamicpv-wbpp: <nil>
STEP: delete the pod
Oct 13 05:00:41.830: INFO: Waiting for pod pod-subpath-test-dynamicpv-wbpp to disappear
Oct 13 05:00:41.926: INFO: Pod pod-subpath-test-dynamicpv-wbpp no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-wbpp
Oct 13 05:00:41.926: INFO: Deleting pod "pod-subpath-test-dynamicpv-wbpp" in namespace "provisioning-7329"
... skipping 789 lines ...
STEP: Deleting pod hostexec-ip-172-20-62-14.eu-west-2.compute.internal-s2fn7 in namespace volumemode-9072
Oct 13 05:01:15.728: INFO: Deleting pod "pod-61c47075-4400-44a7-a351-ce8a6078df03" in namespace "volumemode-9072"
Oct 13 05:01:15.827: INFO: Wait up to 5m0s for pod "pod-61c47075-4400-44a7-a351-ce8a6078df03" to be fully deleted
STEP: Deleting pv and pvc
Oct 13 05:01:20.023: INFO: Deleting PersistentVolumeClaim "pvc-pbkrv"
Oct 13 05:01:20.122: INFO: Deleting PersistentVolume "aws-6vfz5"
Oct 13 05:01:20.465: INFO: Couldn't delete PD "aws://eu-west-2a/vol-084d054a62e3b32df", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-084d054a62e3b32df is currently attached to i-0cd8e7c27c713b3cc
	status code: 400, request id: bf88a842-473e-48a1-9246-c02fff513c14
Oct 13 05:01:25.992: INFO: Couldn't delete PD "aws://eu-west-2a/vol-084d054a62e3b32df", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-084d054a62e3b32df is currently attached to i-0cd8e7c27c713b3cc
	status code: 400, request id: 85f983a0-4ac7-4137-92bc-ca02f47214f7
Oct 13 05:01:31.509: INFO: Successfully deleted PD "aws://eu-west-2a/vol-084d054a62e3b32df".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 05:01:31.509: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-9072" for this suite.
... skipping 178 lines ...
Oct 13 05:01:16.473: INFO: Waiting for pod aws-client to disappear
Oct 13 05:01:16.571: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Oct 13 05:01:16.572: INFO: Deleting PersistentVolumeClaim "pvc-mwqkl"
Oct 13 05:01:16.670: INFO: Deleting PersistentVolume "aws-zw7js"
Oct 13 05:01:17.332: INFO: Couldn't delete PD "aws://eu-west-2a/vol-03a7a74d6d7e15da5", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-03a7a74d6d7e15da5 is currently attached to i-0a4eb7973d6932982
	status code: 400, request id: cc7079ca-ccd4-479a-8a11-fe7cc641e966
Oct 13 05:01:22.839: INFO: Couldn't delete PD "aws://eu-west-2a/vol-03a7a74d6d7e15da5", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-03a7a74d6d7e15da5 is currently attached to i-0a4eb7973d6932982
	status code: 400, request id: f3ace4c5-68dd-4113-a004-25e7cb83c95d
Oct 13 05:01:28.345: INFO: Couldn't delete PD "aws://eu-west-2a/vol-03a7a74d6d7e15da5", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-03a7a74d6d7e15da5 is currently attached to i-0a4eb7973d6932982
	status code: 400, request id: 45625683-ed10-4b8e-8f06-d79f80fc5f97
Oct 13 05:01:33.879: INFO: Successfully deleted PD "aws://eu-west-2a/vol-03a7a74d6d7e15da5".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 05:01:33.879: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-1834" for this suite.
... skipping 101 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 05:00:02.438: 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.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Oct 13 05:00:02.919: INFO: Creating resource for dynamic PV
Oct 13 05:00:02.919: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7065-e2e-sc9hmr8
STEP: creating a claim
Oct 13 05:00:03.016: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-66pk
STEP: Checking for subpath error in container status
Oct 13 05:00:27.501: INFO: Deleting pod "pod-subpath-test-dynamicpv-66pk" in namespace "provisioning-7065"
Oct 13 05:00:27.600: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-66pk" to be fully deleted
STEP: Deleting pod
Oct 13 05:00:29.795: INFO: Deleting pod "pod-subpath-test-dynamicpv-66pk" in namespace "provisioning-7065"
STEP: Deleting pvc
Oct 13 05:00:30.088: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comwb75z"
... skipping 21 lines ...

• [SLOW TEST:94.438 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.2A194ozXw/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.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)(allowExpansion)][Feature:Windows] volume-expand
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
... skipping 88 lines ...

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 2 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 05:00:55.827: 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.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Oct 13 05:00:56.312: INFO: Creating resource for dynamic PV
Oct 13 05:00:56.312: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-9067-e2e-scfnjmg
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Oct 13 05:01:02.994: INFO: Deleting pod "pod-acfac8b0-cc15-4b67-8e8b-ebebcf582457" in namespace "volumemode-9067"
Oct 13 05:01:03.091: INFO: Wait up to 5m0s for pod "pod-acfac8b0-cc15-4b67-8e8b-ebebcf582457" to be fully deleted
STEP: Deleting pvc
Oct 13 05:01:05.476: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comch2q9"
Oct 13 05:01:05.573: INFO: Waiting up to 5m0s for PersistentVolume pvc-0619e0ee-5679-41fc-8122-4d7c9d8e2e7b to get deleted
Oct 13 05:01:05.669: INFO: PersistentVolume pvc-0619e0ee-5679-41fc-8122-4d7c9d8e2e7b found and phase=Released (95.821541ms)
... skipping 13 lines ...

• [SLOW TEST:45.825 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.2A194ozXw/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.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 602 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 05:01:30.854: 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.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Oct 13 05:01:31.337: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 13 05:01:31.337: INFO: Creating resource for dynamic PV
Oct 13 05:01:31.337: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-70524dsqh
STEP: creating a claim
Oct 13 05:01:31.435: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-cb4c
STEP: Checking for subpath error in container status
Oct 13 05:01:47.924: INFO: Deleting pod "pod-subpath-test-dynamicpv-cb4c" in namespace "provisioning-7052"
Oct 13 05:01:48.021: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-cb4c" to be fully deleted
STEP: Deleting pod
Oct 13 05:01:50.214: INFO: Deleting pod "pod-subpath-test-dynamicpv-cb4c" in namespace "provisioning-7052"
STEP: Deleting pvc
Oct 13 05:01:50.513: INFO: Deleting PersistentVolumeClaim "awsr2xx8"
... skipping 16 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.2A194ozXw/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.2A194ozXw/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath directory is outside the volume [Slow][LinuxOnly]
      /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 20 lines ...
Oct 13 05:01:34.361: INFO: PersistentVolumeClaim pvc-5xr9g found but phase is Pending instead of Bound.
Oct 13 05:01:36.466: INFO: PersistentVolumeClaim pvc-5xr9g found and phase=Bound (14.788450956s)
Oct 13 05:01:36.466: INFO: Waiting up to 3m0s for PersistentVolume aws-lvfwb to have phase Bound
Oct 13 05:01:36.562: INFO: PersistentVolume aws-lvfwb found and phase=Bound (95.863932ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-5mmj
STEP: Creating a pod to test exec-volume-test
Oct 13 05:01:36.853: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-5mmj" in namespace "volume-194" to be "Succeeded or Failed"
Oct 13 05:01:36.951: INFO: Pod "exec-volume-test-preprovisionedpv-5mmj": Phase="Pending", Reason="", readiness=false. Elapsed: 98.730604ms
Oct 13 05:01:39.048: INFO: Pod "exec-volume-test-preprovisionedpv-5mmj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.195144117s
Oct 13 05:01:41.144: INFO: Pod "exec-volume-test-preprovisionedpv-5mmj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.291562975s
Oct 13 05:01:43.242: INFO: Pod "exec-volume-test-preprovisionedpv-5mmj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.38890747s
Oct 13 05:01:45.338: INFO: Pod "exec-volume-test-preprovisionedpv-5mmj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.485225902s
Oct 13 05:01:47.435: INFO: Pod "exec-volume-test-preprovisionedpv-5mmj": Phase="Pending", Reason="", readiness=false. Elapsed: 10.582627781s
Oct 13 05:01:49.532: INFO: Pod "exec-volume-test-preprovisionedpv-5mmj": Phase="Pending", Reason="", readiness=false. Elapsed: 12.678880408s
Oct 13 05:01:51.629: INFO: Pod "exec-volume-test-preprovisionedpv-5mmj": Phase="Pending", Reason="", readiness=false. Elapsed: 14.776133881s
Oct 13 05:01:53.727: INFO: Pod "exec-volume-test-preprovisionedpv-5mmj": Phase="Pending", Reason="", readiness=false. Elapsed: 16.873975369s
Oct 13 05:01:55.823: INFO: Pod "exec-volume-test-preprovisionedpv-5mmj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.970525953s
STEP: Saw pod success
Oct 13 05:01:55.823: INFO: Pod "exec-volume-test-preprovisionedpv-5mmj" satisfied condition "Succeeded or Failed"
Oct 13 05:01:55.919: INFO: Trying to get logs from node ip-172-20-48-140.eu-west-2.compute.internal pod exec-volume-test-preprovisionedpv-5mmj container exec-container-preprovisionedpv-5mmj: <nil>
STEP: delete the pod
Oct 13 05:01:56.122: INFO: Waiting for pod exec-volume-test-preprovisionedpv-5mmj to disappear
Oct 13 05:01:56.218: INFO: Pod exec-volume-test-preprovisionedpv-5mmj no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-5mmj
Oct 13 05:01:56.218: INFO: Deleting pod "exec-volume-test-preprovisionedpv-5mmj" in namespace "volume-194"
STEP: Deleting pv and pvc
Oct 13 05:01:56.314: INFO: Deleting PersistentVolumeClaim "pvc-5xr9g"
Oct 13 05:01:56.411: INFO: Deleting PersistentVolume "aws-lvfwb"
Oct 13 05:01:56.711: INFO: Couldn't delete PD "aws://eu-west-2a/vol-018507d19c176bad3", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-018507d19c176bad3 is currently attached to i-0466ff1ba288150de
	status code: 400, request id: 6fd4b616-c1cd-4d04-b08a-6008950eda57
Oct 13 05:02:02.210: INFO: Couldn't delete PD "aws://eu-west-2a/vol-018507d19c176bad3", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-018507d19c176bad3 is currently attached to i-0466ff1ba288150de
	status code: 400, request id: 0384d091-f1d3-4df3-a671-02cfd5c8e0ca
Oct 13 05:02:07.721: INFO: Couldn't delete PD "aws://eu-west-2a/vol-018507d19c176bad3", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-018507d19c176bad3 is currently attached to i-0466ff1ba288150de
	status code: 400, request id: 1c9d26e0-69ed-45d1-80a2-7259dc84f996
Oct 13 05:02:13.255: INFO: Couldn't delete PD "aws://eu-west-2a/vol-018507d19c176bad3", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-018507d19c176bad3 is currently attached to i-0466ff1ba288150de
	status code: 400, request id: 19be47c9-fddc-4fb1-ae39-6615ef8b42ae
Oct 13 05:02:18.802: INFO: Couldn't delete PD "aws://eu-west-2a/vol-018507d19c176bad3", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-018507d19c176bad3 is currently attached to i-0466ff1ba288150de
	status code: 400, request id: cb0f8133-4676-4ad9-b0f0-02984bb4e26b
Oct 13 05:02:24.340: INFO: Successfully deleted PD "aws://eu-west-2a/vol-018507d19c176bad3".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 05:02:24.340: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-194" for this suite.
... skipping 68 lines ...
Oct 13 05:01:29.864: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-1354-e2e-scx2gqc
STEP: creating a claim
Oct 13 05:01:29.962: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-6zvk
STEP: Creating a pod to test exec-volume-test
Oct 13 05:01:30.255: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-6zvk" in namespace "volume-1354" to be "Succeeded or Failed"
Oct 13 05:01:30.351: INFO: Pod "exec-volume-test-dynamicpv-6zvk": Phase="Pending", Reason="", readiness=false. Elapsed: 96.482777ms
Oct 13 05:01:32.448: INFO: Pod "exec-volume-test-dynamicpv-6zvk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.193195385s
Oct 13 05:01:34.545: INFO: Pod "exec-volume-test-dynamicpv-6zvk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.290889857s
Oct 13 05:01:36.644: INFO: Pod "exec-volume-test-dynamicpv-6zvk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.389053455s
Oct 13 05:01:38.740: INFO: Pod "exec-volume-test-dynamicpv-6zvk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.485661885s
Oct 13 05:01:40.838: INFO: Pod "exec-volume-test-dynamicpv-6zvk": Phase="Pending", Reason="", readiness=false. Elapsed: 10.583725347s
Oct 13 05:01:42.939: INFO: Pod "exec-volume-test-dynamicpv-6zvk": Phase="Pending", Reason="", readiness=false. Elapsed: 12.684236278s
Oct 13 05:01:45.036: INFO: Pod "exec-volume-test-dynamicpv-6zvk": Phase="Pending", Reason="", readiness=false. Elapsed: 14.78126486s
Oct 13 05:01:47.133: INFO: Pod "exec-volume-test-dynamicpv-6zvk": Phase="Pending", Reason="", readiness=false. Elapsed: 16.878401022s
Oct 13 05:01:49.230: INFO: Pod "exec-volume-test-dynamicpv-6zvk": Phase="Pending", Reason="", readiness=false. Elapsed: 18.975381565s
Oct 13 05:01:51.328: INFO: Pod "exec-volume-test-dynamicpv-6zvk": Phase="Pending", Reason="", readiness=false. Elapsed: 21.073083522s
Oct 13 05:01:53.425: INFO: Pod "exec-volume-test-dynamicpv-6zvk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.170625034s
STEP: Saw pod success
Oct 13 05:01:53.425: INFO: Pod "exec-volume-test-dynamicpv-6zvk" satisfied condition "Succeeded or Failed"
Oct 13 05:01:53.522: INFO: Trying to get logs from node ip-172-20-62-14.eu-west-2.compute.internal pod exec-volume-test-dynamicpv-6zvk container exec-container-dynamicpv-6zvk: <nil>
STEP: delete the pod
Oct 13 05:01:53.723: INFO: Waiting for pod exec-volume-test-dynamicpv-6zvk to disappear
Oct 13 05:01:53.821: INFO: Pod exec-volume-test-dynamicpv-6zvk no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-6zvk
Oct 13 05:01:53.821: INFO: Deleting pod "exec-volume-test-dynamicpv-6zvk" in namespace "volume-1354"
... skipping 508 lines ...
Oct 13 05:01:20.349: INFO: Creating resource for dynamic PV
Oct 13 05:01:20.349: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3156-e2e-scw9trr
STEP: creating a claim
Oct 13 05:01:20.446: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-3156
Oct 13 05:01:20.741: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-3156" in namespace "provisioning-3156" to be "Succeeded or Failed"
Oct 13 05:01:20.839: INFO: Pod "volume-prep-provisioning-3156": Phase="Pending", Reason="", readiness=false. Elapsed: 98.392926ms
Oct 13 05:01:22.936: INFO: Pod "volume-prep-provisioning-3156": Phase="Pending", Reason="", readiness=false. Elapsed: 2.195121493s
Oct 13 05:01:25.034: INFO: Pod "volume-prep-provisioning-3156": Phase="Pending", Reason="", readiness=false. Elapsed: 4.293064695s
Oct 13 05:01:27.132: INFO: Pod "volume-prep-provisioning-3156": Phase="Pending", Reason="", readiness=false. Elapsed: 6.390482832s
Oct 13 05:01:29.228: INFO: Pod "volume-prep-provisioning-3156": Phase="Pending", Reason="", readiness=false. Elapsed: 8.487272593s
Oct 13 05:01:31.326: INFO: Pod "volume-prep-provisioning-3156": Phase="Pending", Reason="", readiness=false. Elapsed: 10.585334488s
... skipping 8 lines ...
Oct 13 05:01:50.204: INFO: Pod "volume-prep-provisioning-3156": Phase="Pending", Reason="", readiness=false. Elapsed: 29.462447611s
Oct 13 05:01:52.301: INFO: Pod "volume-prep-provisioning-3156": Phase="Pending", Reason="", readiness=false. Elapsed: 31.55977808s
Oct 13 05:01:54.399: INFO: Pod "volume-prep-provisioning-3156": Phase="Pending", Reason="", readiness=false. Elapsed: 33.657483841s
Oct 13 05:01:56.495: INFO: Pod "volume-prep-provisioning-3156": Phase="Pending", Reason="", readiness=false. Elapsed: 35.754313944s
Oct 13 05:01:58.592: INFO: Pod "volume-prep-provisioning-3156": Phase="Succeeded", Reason="", readiness=false. Elapsed: 37.851139515s
STEP: Saw pod success
Oct 13 05:01:58.592: INFO: Pod "volume-prep-provisioning-3156" satisfied condition "Succeeded or Failed"
Oct 13 05:01:58.592: INFO: Deleting pod "volume-prep-provisioning-3156" in namespace "provisioning-3156"
Oct 13 05:01:58.695: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-3156" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-hhtm
STEP: Checking for subpath error in container status
Oct 13 05:03:05.088: INFO: Deleting pod "pod-subpath-test-dynamicpv-hhtm" in namespace "provisioning-3156"
Oct 13 05:03:05.190: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-hhtm" to be fully deleted
STEP: Deleting pod
Oct 13 05:03:05.286: INFO: Deleting pod "pod-subpath-test-dynamicpv-hhtm" in namespace "provisioning-3156"
STEP: Deleting pvc
Oct 13 05:03:05.580: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comqd5rr"
... skipping 234 lines ...
Oct 13 05:08:02.981: INFO: At 2021-10-13 05:00:43 +0000 UTC - event for pod-31811359-b8ef-440a-8ea8-2cd447aa64c4: {kubelet ip-172-20-45-187.eu-west-2.compute.internal} SuccessfulMountVolume: MapVolume.MapPodDevice succeeded for volume "pvc-dcb79503-f4f8-43dd-b54a-becbb0f61d01" globalMapPath "/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/pvc-dcb79503-f4f8-43dd-b54a-becbb0f61d01/dev"
Oct 13 05:08:02.981: INFO: At 2021-10-13 05:00:45 +0000 UTC - event for pod-31811359-b8ef-440a-8ea8-2cd447aa64c4: {kubelet ip-172-20-45-187.eu-west-2.compute.internal} Created: Created container write-pod
Oct 13 05:08:02.981: INFO: At 2021-10-13 05:00:45 +0000 UTC - event for pod-31811359-b8ef-440a-8ea8-2cd447aa64c4: {kubelet ip-172-20-45-187.eu-west-2.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" already present on machine
Oct 13 05:08:02.981: INFO: At 2021-10-13 05:00:45 +0000 UTC - event for pod-31811359-b8ef-440a-8ea8-2cd447aa64c4: {kubelet ip-172-20-45-187.eu-west-2.compute.internal} Started: Started container write-pod
Oct 13 05:08:02.981: INFO: At 2021-10-13 05:00:56 +0000 UTC - event for pod-31811359-b8ef-440a-8ea8-2cd447aa64c4: {kubelet ip-172-20-45-187.eu-west-2.compute.internal} Killing: Stopping container write-pod
Oct 13 05:08:02.981: INFO: At 2021-10-13 05:00:58 +0000 UTC - event for pod-02e0332f-d49b-422f-8270-885bc39f4f9e: {default-scheduler } Scheduled: Successfully assigned multivolume-838/pod-02e0332f-d49b-422f-8270-885bc39f4f9e to ip-172-20-45-187.eu-west-2.compute.internal
Oct 13 05:08:02.981: INFO: At 2021-10-13 05:01:14 +0000 UTC - event for pod-02e0332f-d49b-422f-8270-885bc39f4f9e: {kubelet ip-172-20-45-187.eu-west-2.compute.internal} FailedMapVolume: MapVolume.WaitForAttach failed for volume "pvc-dcb79503-f4f8-43dd-b54a-becbb0f61d01" : volume attachment is being deleted
Oct 13 05:08:02.981: INFO: At 2021-10-13 05:01:18 +0000 UTC - event for pod-02e0332f-d49b-422f-8270-885bc39f4f9e: {kubelet ip-172-20-45-187.eu-west-2.compute.internal} FailedMapVolume: MapVolume.WaitForAttach failed for volume "pvc-dcb79503-f4f8-43dd-b54a-becbb0f61d01" : volume vol-04f1c5f73d13f0847 has GET error for volume attachment csi-490d650f89f7ffdbb506f20e42cf7469429eb83ef4206baeb523f1e0f24dceeb: volumeattachments.storage.k8s.io "csi-490d650f89f7ffdbb506f20e42cf7469429eb83ef4206baeb523f1e0f24dceeb" is forbidden: User "system:node:ip-172-20-45-187.eu-west-2.compute.internal" cannot get resource "volumeattachments" in API group "storage.k8s.io" at the cluster scope: no relationship found between node 'ip-172-20-45-187.eu-west-2.compute.internal' and this object
Oct 13 05:08:02.981: INFO: At 2021-10-13 05:01:21 +0000 UTC - event for pod-02e0332f-d49b-422f-8270-885bc39f4f9e: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-80361c4f-551a-4ea9-a0a5-18e6c4ee2656" 
Oct 13 05:08:02.981: INFO: At 2021-10-13 05:02:18 +0000 UTC - event for pod-02e0332f-d49b-422f-8270-885bc39f4f9e: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-dcb79503-f4f8-43dd-b54a-becbb0f61d01" : rpc error: code = Internal desc = Could not attach volume "vol-04f1c5f73d13f0847" to node "i-0a4eb7973d6932982": attachment of disk "vol-04f1c5f73d13f0847" failed, expected device to be attached but was attaching
Oct 13 05:08:02.981: INFO: At 2021-10-13 05:02:20 +0000 UTC - event for pod-02e0332f-d49b-422f-8270-885bc39f4f9e: {kubelet ip-172-20-45-187.eu-west-2.compute.internal} FailedMapVolume: MapVolume.WaitForAttach failed for volume "pvc-dcb79503-f4f8-43dd-b54a-becbb0f61d01" : rpc error: code = Internal desc = Could not attach volume "vol-04f1c5f73d13f0847" to node "i-0a4eb7973d6932982": attachment of disk "vol-04f1c5f73d13f0847" failed, expected device to be attached but was attaching
Oct 13 05:08:02.981: INFO: At 2021-10-13 05:03:01 +0000 UTC - event for pod-02e0332f-d49b-422f-8270-885bc39f4f9e: {kubelet ip-172-20-45-187.eu-west-2.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume1], unattached volumes=[volume2 kube-api-access-zvpq7 volume1]: timed out waiting for the condition
Oct 13 05:08:02.981: INFO: At 2021-10-13 05:07:28 +0000 UTC - event for pod-02e0332f-d49b-422f-8270-885bc39f4f9e: {kubelet ip-172-20-45-187.eu-west-2.compute.internal} SuccessfulMountVolume: MapVolume.MapPodDevice succeeded for volume "pvc-dcb79503-f4f8-43dd-b54a-becbb0f61d01" volumeMapPath "/var/lib/kubelet/pods/c6e29536-384b-4ee4-8d8d-8fb633c904dc/volumeDevices/kubernetes.io~csi"
Oct 13 05:08:02.981: INFO: At 2021-10-13 05:07:28 +0000 UTC - event for pod-02e0332f-d49b-422f-8270-885bc39f4f9e: {kubelet ip-172-20-45-187.eu-west-2.compute.internal} SuccessfulMountVolume: MapVolume.MapPodDevice succeeded for volume "pvc-dcb79503-f4f8-43dd-b54a-becbb0f61d01" globalMapPath "/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/pvc-dcb79503-f4f8-43dd-b54a-becbb0f61d01/dev"
Oct 13 05:08:02.981: INFO: At 2021-10-13 05:07:29 +0000 UTC - event for pod-02e0332f-d49b-422f-8270-885bc39f4f9e: {kubelet ip-172-20-45-187.eu-west-2.compute.internal} Started: Started container write-pod
Oct 13 05:08:02.981: INFO: At 2021-10-13 05:07:29 +0000 UTC - event for pod-02e0332f-d49b-422f-8270-885bc39f4f9e: {kubelet ip-172-20-45-187.eu-west-2.compute.internal} Created: Created container write-pod
Oct 13 05:08:02.981: INFO: At 2021-10-13 05:07:29 +0000 UTC - event for pod-02e0332f-d49b-422f-8270-885bc39f4f9e: {kubelet ip-172-20-45-187.eu-west-2.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" already present on machine
... skipping 161 lines ...
  /tmp/kops.2A194ozXw/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
    /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should access to two volumes with different volume mode and retain data across pod recreation on the same node [LinuxOnly] [It]
      /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/multivolume.go:214

      Unexpected error:
          <*errors.errorString | 0xc00021e5d0>: {
              s: "pod \"pod-02e0332f-d49b-422f-8270-885bc39f4f9e\" is not Running: timed out waiting for the condition",
          }
          pod "pod-02e0332f-d49b-422f-8270-885bc39f4f9e" is not Running: timed out waiting for the condition
      occurred

... skipping 98 lines ...
    /tmp/kops.2A194ozXw/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumelimits.go:123
------------------------------


Summarizing 1 Failure:

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

Ran 140 of 485 Specs in 1300.961 seconds
FAIL! -- 139 Passed | 1 Failed | 0 Pending | 345 Skipped


Ginkgo ran 1 suite in 24m3.380740067s
Test Suite Failed

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