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

No Test Failures!


Error lines from build-log.txt

... skipping 596 lines ...
I1014 06:01:08.300005   12519 app.go:90] ID for this run: "20d7e673-2cb3-11ec-8d4f-ca63ca797e20"
I1014 06:01:08.320919   12519 up.go:43] Cleaning up any leaked resources from previous cluster
I1014 06:01:08.320981   12519 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
I1014 06:01:08.339608   12528 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1014 06:01:08.339686   12528 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I1014 06:01:08.339690   12528 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Error: Cluster.kops.k8s.io "e2e-b6f7c24027-45100.test-cncf-aws.k8s.io" not found
W1014 06:01:08.818509   12519 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I1014 06:01:08.818573   12519 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
I1014 06:01:08.837860   12538 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1014 06:01:08.837996   12538 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I1014 06:01:08.838001   12538 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
I1014 06:01:09.318586   12519 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/14 06:01:09 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
I1014 06:01:09.326322   12519 http.go:37] curl https://ip.jsb.workers.dev
I1014 06:01:09.402584   12519 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.239.83.195/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones us-west-1a --master-size c5.large
I1014 06:01:09.420299   12548 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1014 06:01:09.420392   12548 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I1014 06:01:09.420397   12548 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1014 06:01:09.444442   12548 create_cluster.go:838] Using SSH public key: /etc/aws-ssh/aws-ssh-public
... skipping 33 lines ...
I1014 06:01:33.879777   12519 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
I1014 06:01:33.897905   12569 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1014 06:01:33.897989   12569 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I1014 06:01:33.898053   12569 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-b6f7c24027-45100.test-cncf-aws.k8s.io

W1014 06:01:34.941688   12569 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-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1014 06:01:45.005335   12569 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1014 06:01:55.038396   12569 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1014 06:02:05.068801   12569 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1014 06:02:15.111681   12569 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1014 06:02:25.143417   12569 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1014 06:02:35.175027   12569 validate_cluster.go:232] (will retry): cluster not yet healthy
W1014 06:02:45.207269   12569 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-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1014 06:02:55.239718   12569 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1014 06:03:05.299219   12569 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1014 06:03:15.338990   12569 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1014 06:03:25.370385   12569 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1014 06:03:35.403445   12569 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1014 06:03:45.437842   12569 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1014 06:03:55.474597   12569 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1014 06:04:05.513799   12569 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1014 06:04:15.546416   12569 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1014 06:04:25.591729   12569 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1014 06:04:35.624095   12569 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1014 06:04:45.656940   12569 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1014 06:04:55.688060   12569 validate_cluster.go:232] (will retry): cluster not yet healthy
W1014 06:05:05.747910   12569 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://api.e2e-b6f7c24027-45100.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp: 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-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

NODE STATUS
... skipping 18 lines ...
Pod	kube-system/ebs-csi-controller-54dc46fc7b-s2rfq		system-cluster-critical pod "ebs-csi-controller-54dc46fc7b-s2rfq" is pending
Pod	kube-system/ebs-csi-node-8q8xq				system-node-critical pod "ebs-csi-node-8q8xq" is pending
Pod	kube-system/ebs-csi-node-cqp4b				system-node-critical pod "ebs-csi-node-cqp4b" is pending
Pod	kube-system/ebs-csi-node-gxr6d				system-node-critical pod "ebs-csi-node-gxr6d" is pending
Pod	kube-system/ebs-csi-node-pngxv				system-node-critical pod "ebs-csi-node-pngxv" is pending

Validation Failed
W1014 06:05:17.520021   12569 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 18 lines ...
Pod	kube-system/ebs-csi-node-8q8xq			system-node-critical pod "ebs-csi-node-8q8xq" is pending
Pod	kube-system/ebs-csi-node-cqp4b			system-node-critical pod "ebs-csi-node-cqp4b" is pending
Pod	kube-system/ebs-csi-node-gxr6d			system-node-critical pod "ebs-csi-node-gxr6d" is pending
Pod	kube-system/ebs-csi-node-pngxv			system-node-critical pod "ebs-csi-node-pngxv" is pending
Pod	kube-system/ebs-csi-node-qh6zk			system-node-critical pod "ebs-csi-node-qh6zk" is pending

Validation Failed
W1014 06:05:28.782564   12569 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 10 lines ...
Pod	kube-system/calico-node-g49qb	system-node-critical pod "calico-node-g49qb" is pending
Pod	kube-system/ebs-csi-node-cqp4b	system-node-critical pod "ebs-csi-node-cqp4b" is pending
Pod	kube-system/ebs-csi-node-gxr6d	system-node-critical pod "ebs-csi-node-gxr6d" is pending
Pod	kube-system/ebs-csi-node-pngxv	system-node-critical pod "ebs-csi-node-pngxv" is pending
Pod	kube-system/ebs-csi-node-qh6zk	system-node-critical pod "ebs-csi-node-qh6zk" is pending

Validation Failed
W1014 06:05:40.037873   12569 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 6 lines ...
ip-172-20-59-48.us-west-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME				MESSAGE
Pod	kube-system/ebs-csi-node-qh6zk	system-node-critical pod "ebs-csi-node-qh6zk" is pending

Validation Failed
W1014 06:05:51.383738   12569 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 6 lines ...
ip-172-20-59-48.us-west-1.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME				MESSAGE
Pod	kube-system/ebs-csi-node-qh6zk	system-node-critical pod "ebs-csi-node-qh6zk" is pending

Validation Failed
W1014 06:06:02.599000   12569 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 6 lines ...
ip-172-20-59-48.us-west-1.compute.internal	master	True

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

Validation Failed
W1014 06:06:13.836525   12569 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 194 lines ...

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

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

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

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

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

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 434 lines ...
Oct 14 06:09:23.660: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 177 lines ...
STEP: Creating a kubernetes client
Oct 14 06:09:21.504: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename volumemode
W1014 06:09:21.849024   25110 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Oct 14 06:09:21.849: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail to use a volume in a pod with mismatched mode [Slow]
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Oct 14 06:09:21.955: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Oct 14 06:09:22.573: INFO: Successfully created a new PD: "aws://us-west-1a/vol-0dd5021ba17abaa2e".
Oct 14 06:09:22.573: INFO: Creating resource for pre-provisioned PV
Oct 14 06:09:22.573: INFO: Creating PVC and PV
... skipping 4 lines ...
Oct 14 06:09:24.782: INFO: PersistentVolumeClaim pvc-pkxmm found but phase is Pending instead of Bound.
Oct 14 06:09:26.834: INFO: PersistentVolumeClaim pvc-pkxmm found but phase is Pending instead of Bound.
Oct 14 06:09:28.898: INFO: PersistentVolumeClaim pvc-pkxmm found and phase=Bound (6.215506825s)
Oct 14 06:09:28.898: INFO: Waiting up to 3m0s for PersistentVolume aws-hfwjn to have phase Bound
Oct 14 06:09:28.948: INFO: PersistentVolume aws-hfwjn found and phase=Bound (50.144755ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Oct 14 06:09:31.286: INFO: Deleting pod "pod-b48e9256-dddf-47ab-88e4-cb733136d83b" in namespace "volumemode-8622"
Oct 14 06:09:31.337: INFO: Wait up to 5m0s for pod "pod-b48e9256-dddf-47ab-88e4-cb733136d83b" to be fully deleted
STEP: Deleting pv and pvc
Oct 14 06:09:33.439: INFO: Deleting PersistentVolumeClaim "pvc-pkxmm"
Oct 14 06:09:33.491: INFO: Deleting PersistentVolume "aws-hfwjn"
Oct 14 06:09:33.687: INFO: Couldn't delete PD "aws://us-west-1a/vol-0dd5021ba17abaa2e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0dd5021ba17abaa2e is currently attached to i-019e724f48a0be6c0
	status code: 400, request id: 90a85394-18cf-443a-9e8e-754befe1b7f2
Oct 14 06:09:39.058: INFO: Couldn't delete PD "aws://us-west-1a/vol-0dd5021ba17abaa2e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0dd5021ba17abaa2e is currently attached to i-019e724f48a0be6c0
	status code: 400, request id: 85bb479a-6faf-4bbc-8c4a-c2c3a88a3ac9
Oct 14 06:09:44.386: INFO: Couldn't delete PD "aws://us-west-1a/vol-0dd5021ba17abaa2e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0dd5021ba17abaa2e is currently attached to i-019e724f48a0be6c0
	status code: 400, request id: d7efe007-b8b0-4c72-b958-ca0ae23d9fc3
Oct 14 06:09:49.741: INFO: Successfully deleted PD "aws://us-west-1a/vol-0dd5021ba17abaa2e".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 14 06:09:49.741: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-8622" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.SekB7YIla/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.SekB7YIla/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
    /tmp/kops.SekB7YIla/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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Oct 14 06:09:49.901: 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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  /tmp/kops.SekB7YIla/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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

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

    /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 2 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 14 06:09:24.873: 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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Oct 14 06:09:25.903: INFO: Creating resource for dynamic PV
Oct 14 06:09:25.903: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-9698-e2e-scvsfxc
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Oct 14 06:09:32.292: INFO: Deleting pod "pod-377917cd-8823-45c6-8d3f-418e9c29b817" in namespace "volumemode-9698"
Oct 14 06:09:32.346: INFO: Wait up to 5m0s for pod "pod-377917cd-8823-45c6-8d3f-418e9c29b817" to be fully deleted
STEP: Deleting pvc
Oct 14 06:09:34.556: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com6v8v8"
Oct 14 06:09:34.609: INFO: Waiting up to 5m0s for PersistentVolume pvc-5bb4d831-2a30-4bc8-bac8-107cb08d4fc1 to get deleted
Oct 14 06:09:34.660: INFO: PersistentVolume pvc-5bb4d831-2a30-4bc8-bac8-107cb08d4fc1 found and phase=Released (51.238585ms)
... skipping 9 lines ...

• [SLOW TEST:25.108 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.SekB7YIla/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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 52 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.SekB7YIla/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.SekB7YIla/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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 2 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 14 06:09:22.917: 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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Oct 14 06:09:24.954: INFO: Creating resource for dynamic PV
Oct 14 06:09:24.954: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-2544-e2e-sc9ppxm
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Oct 14 06:09:33.314: INFO: Deleting pod "pod-e3676f73-5172-40b2-86d3-fe4a49253fec" in namespace "volumemode-2544"
Oct 14 06:09:33.365: INFO: Wait up to 5m0s for pod "pod-e3676f73-5172-40b2-86d3-fe4a49253fec" to be fully deleted
STEP: Deleting pvc
Oct 14 06:09:35.565: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com65sx7"
Oct 14 06:09:35.617: INFO: Waiting up to 5m0s for PersistentVolume pvc-399c846b-a04b-4036-b665-d1aaf55154e9 to get deleted
Oct 14 06:09:35.667: INFO: PersistentVolume pvc-399c846b-a04b-4036-b665-d1aaf55154e9 found and phase=Released (49.526685ms)
... skipping 9 lines ...

• [SLOW TEST:28.055 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.SekB7YIla/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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 35 lines ...
STEP: Deleting pod hostexec-ip-172-20-47-110.us-west-1.compute.internal-5q948 in namespace volumemode-3021
Oct 14 06:09:38.787: INFO: Deleting pod "pod-64397e0f-cbe1-4d8c-a6ce-bd60f840924c" in namespace "volumemode-3021"
Oct 14 06:09:38.856: INFO: Wait up to 5m0s for pod "pod-64397e0f-cbe1-4d8c-a6ce-bd60f840924c" to be fully deleted
STEP: Deleting pv and pvc
Oct 14 06:09:40.963: INFO: Deleting PersistentVolumeClaim "pvc-tlh9h"
Oct 14 06:09:41.017: INFO: Deleting PersistentVolume "aws-b2k8f"
Oct 14 06:09:41.219: INFO: Couldn't delete PD "aws://us-west-1a/vol-0ebcda4daf76593f6", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ebcda4daf76593f6 is currently attached to i-07be6c3bd073fb26c
	status code: 400, request id: 3cca38bc-c0bc-4316-9c42-5d62dde39521
Oct 14 06:09:46.568: INFO: Couldn't delete PD "aws://us-west-1a/vol-0ebcda4daf76593f6", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ebcda4daf76593f6 is currently attached to i-07be6c3bd073fb26c
	status code: 400, request id: fc6143fe-f621-4f4a-ba1d-1839f47ccb2c
Oct 14 06:09:51.953: INFO: Successfully deleted PD "aws://us-west-1a/vol-0ebcda4daf76593f6".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 14 06:09:51.953: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-3021" for this suite.
... skipping 79 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.SekB7YIla/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.SekB7YIla/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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 287 lines ...
Oct 14 06:09:24.404: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-1353-e2e-scqtsbz
STEP: creating a claim
Oct 14 06:09:24.455: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-46hl
STEP: Creating a pod to test exec-volume-test
Oct 14 06:09:24.623: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-46hl" in namespace "volume-1353" to be "Succeeded or Failed"
Oct 14 06:09:24.672: INFO: Pod "exec-volume-test-dynamicpv-46hl": Phase="Pending", Reason="", readiness=false. Elapsed: 49.067964ms
Oct 14 06:09:26.724: INFO: Pod "exec-volume-test-dynamicpv-46hl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.101241054s
Oct 14 06:09:28.783: INFO: Pod "exec-volume-test-dynamicpv-46hl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.160401767s
Oct 14 06:09:30.833: INFO: Pod "exec-volume-test-dynamicpv-46hl": Phase="Pending", Reason="", readiness=false. Elapsed: 6.210437801s
Oct 14 06:09:32.883: INFO: Pod "exec-volume-test-dynamicpv-46hl": Phase="Pending", Reason="", readiness=false. Elapsed: 8.26036938s
Oct 14 06:09:34.934: INFO: Pod "exec-volume-test-dynamicpv-46hl": Phase="Pending", Reason="", readiness=false. Elapsed: 10.311112548s
Oct 14 06:09:36.984: INFO: Pod "exec-volume-test-dynamicpv-46hl": Phase="Pending", Reason="", readiness=false. Elapsed: 12.360978599s
Oct 14 06:09:39.035: INFO: Pod "exec-volume-test-dynamicpv-46hl": Phase="Pending", Reason="", readiness=false. Elapsed: 14.412388776s
Oct 14 06:09:41.091: INFO: Pod "exec-volume-test-dynamicpv-46hl": Phase="Pending", Reason="", readiness=false. Elapsed: 16.467984633s
Oct 14 06:09:43.141: INFO: Pod "exec-volume-test-dynamicpv-46hl": Phase="Pending", Reason="", readiness=false. Elapsed: 18.518228267s
Oct 14 06:09:45.191: INFO: Pod "exec-volume-test-dynamicpv-46hl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.568372869s
STEP: Saw pod success
Oct 14 06:09:45.191: INFO: Pod "exec-volume-test-dynamicpv-46hl" satisfied condition "Succeeded or Failed"
Oct 14 06:09:45.240: INFO: Trying to get logs from node ip-172-20-44-65.us-west-1.compute.internal pod exec-volume-test-dynamicpv-46hl container exec-container-dynamicpv-46hl: <nil>
STEP: delete the pod
Oct 14 06:09:45.348: INFO: Waiting for pod exec-volume-test-dynamicpv-46hl to disappear
Oct 14 06:09:45.400: INFO: Pod exec-volume-test-dynamicpv-46hl no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-46hl
Oct 14 06:09:45.400: INFO: Deleting pod "exec-volume-test-dynamicpv-46hl" in namespace "volume-1353"
... skipping 34 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.SekB7YIla/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.SekB7YIla/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.SekB7YIla/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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 99 lines ...
Oct 14 06:09:22.853: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-2169-e2e-sc27fql
STEP: creating a claim
Oct 14 06:09:22.906: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-ftq5
STEP: Creating a pod to test exec-volume-test
Oct 14 06:09:23.061: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-ftq5" in namespace "volume-2169" to be "Succeeded or Failed"
Oct 14 06:09:23.112: INFO: Pod "exec-volume-test-dynamicpv-ftq5": Phase="Pending", Reason="", readiness=false. Elapsed: 50.679505ms
Oct 14 06:09:25.167: INFO: Pod "exec-volume-test-dynamicpv-ftq5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.10560128s
Oct 14 06:09:27.218: INFO: Pod "exec-volume-test-dynamicpv-ftq5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.156492507s
Oct 14 06:09:29.273: INFO: Pod "exec-volume-test-dynamicpv-ftq5": Phase="Pending", Reason="", readiness=false. Elapsed: 6.211361854s
Oct 14 06:09:31.325: INFO: Pod "exec-volume-test-dynamicpv-ftq5": Phase="Pending", Reason="", readiness=false. Elapsed: 8.263576293s
Oct 14 06:09:33.375: INFO: Pod "exec-volume-test-dynamicpv-ftq5": Phase="Pending", Reason="", readiness=false. Elapsed: 10.313397897s
... skipping 2 lines ...
Oct 14 06:09:39.532: INFO: Pod "exec-volume-test-dynamicpv-ftq5": Phase="Pending", Reason="", readiness=false. Elapsed: 16.470645692s
Oct 14 06:09:41.582: INFO: Pod "exec-volume-test-dynamicpv-ftq5": Phase="Pending", Reason="", readiness=false. Elapsed: 18.521153716s
Oct 14 06:09:43.632: INFO: Pod "exec-volume-test-dynamicpv-ftq5": Phase="Pending", Reason="", readiness=false. Elapsed: 20.571208158s
Oct 14 06:09:45.683: INFO: Pod "exec-volume-test-dynamicpv-ftq5": Phase="Pending", Reason="", readiness=false. Elapsed: 22.621866s
Oct 14 06:09:47.734: INFO: Pod "exec-volume-test-dynamicpv-ftq5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.673042066s
STEP: Saw pod success
Oct 14 06:09:47.734: INFO: Pod "exec-volume-test-dynamicpv-ftq5" satisfied condition "Succeeded or Failed"
Oct 14 06:09:47.784: INFO: Trying to get logs from node ip-172-20-47-110.us-west-1.compute.internal pod exec-volume-test-dynamicpv-ftq5 container exec-container-dynamicpv-ftq5: <nil>
STEP: delete the pod
Oct 14 06:09:47.890: INFO: Waiting for pod exec-volume-test-dynamicpv-ftq5 to disappear
Oct 14 06:09:47.939: INFO: Pod exec-volume-test-dynamicpv-ftq5 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-ftq5
Oct 14 06:09:47.939: INFO: Deleting pod "exec-volume-test-dynamicpv-ftq5" in namespace "volume-2169"
... skipping 355 lines ...
Oct 14 06:09:26.154: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9847drxxh
STEP: creating a claim
Oct 14 06:09:26.211: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-kgvk
STEP: Creating a pod to test subpath
Oct 14 06:09:26.376: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-kgvk" in namespace "provisioning-9847" to be "Succeeded or Failed"
Oct 14 06:09:26.427: INFO: Pod "pod-subpath-test-dynamicpv-kgvk": Phase="Pending", Reason="", readiness=false. Elapsed: 50.597455ms
Oct 14 06:09:28.478: INFO: Pod "pod-subpath-test-dynamicpv-kgvk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.101845296s
Oct 14 06:09:30.535: INFO: Pod "pod-subpath-test-dynamicpv-kgvk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.158495836s
Oct 14 06:09:32.584: INFO: Pod "pod-subpath-test-dynamicpv-kgvk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.208137568s
Oct 14 06:09:34.634: INFO: Pod "pod-subpath-test-dynamicpv-kgvk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.257599495s
Oct 14 06:09:36.688: INFO: Pod "pod-subpath-test-dynamicpv-kgvk": Phase="Pending", Reason="", readiness=false. Elapsed: 10.311484263s
... skipping 5 lines ...
Oct 14 06:09:48.998: INFO: Pod "pod-subpath-test-dynamicpv-kgvk": Phase="Pending", Reason="", readiness=false. Elapsed: 22.621453966s
Oct 14 06:09:51.051: INFO: Pod "pod-subpath-test-dynamicpv-kgvk": Phase="Pending", Reason="", readiness=false. Elapsed: 24.675165001s
Oct 14 06:09:53.102: INFO: Pod "pod-subpath-test-dynamicpv-kgvk": Phase="Pending", Reason="", readiness=false. Elapsed: 26.725985684s
Oct 14 06:09:55.153: INFO: Pod "pod-subpath-test-dynamicpv-kgvk": Phase="Pending", Reason="", readiness=false. Elapsed: 28.776720098s
Oct 14 06:09:57.203: INFO: Pod "pod-subpath-test-dynamicpv-kgvk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 30.826953223s
STEP: Saw pod success
Oct 14 06:09:57.203: INFO: Pod "pod-subpath-test-dynamicpv-kgvk" satisfied condition "Succeeded or Failed"
Oct 14 06:09:57.253: INFO: Trying to get logs from node ip-172-20-57-80.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-kgvk container test-container-subpath-dynamicpv-kgvk: <nil>
STEP: delete the pod
Oct 14 06:09:57.402: INFO: Waiting for pod pod-subpath-test-dynamicpv-kgvk to disappear
Oct 14 06:09:57.451: INFO: Pod pod-subpath-test-dynamicpv-kgvk no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-kgvk
Oct 14 06:09:57.451: INFO: Deleting pod "pod-subpath-test-dynamicpv-kgvk" in namespace "provisioning-9847"
STEP: Creating pod pod-subpath-test-dynamicpv-kgvk
STEP: Creating a pod to test subpath
Oct 14 06:09:57.561: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-kgvk" in namespace "provisioning-9847" to be "Succeeded or Failed"
Oct 14 06:09:57.619: INFO: Pod "pod-subpath-test-dynamicpv-kgvk": Phase="Pending", Reason="", readiness=false. Elapsed: 57.374325ms
Oct 14 06:09:59.669: INFO: Pod "pod-subpath-test-dynamicpv-kgvk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.107706236s
Oct 14 06:10:01.719: INFO: Pod "pod-subpath-test-dynamicpv-kgvk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.157800628s
Oct 14 06:10:03.769: INFO: Pod "pod-subpath-test-dynamicpv-kgvk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.208271301s
STEP: Saw pod success
Oct 14 06:10:03.770: INFO: Pod "pod-subpath-test-dynamicpv-kgvk" satisfied condition "Succeeded or Failed"
Oct 14 06:10:03.819: INFO: Trying to get logs from node ip-172-20-57-80.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-kgvk container test-container-subpath-dynamicpv-kgvk: <nil>
STEP: delete the pod
Oct 14 06:10:03.932: INFO: Waiting for pod pod-subpath-test-dynamicpv-kgvk to disappear
Oct 14 06:10:03.981: INFO: Pod pod-subpath-test-dynamicpv-kgvk no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-kgvk
Oct 14 06:10:03.981: INFO: Deleting pod "pod-subpath-test-dynamicpv-kgvk" in namespace "provisioning-9847"
... skipping 51 lines ...
STEP: Creating a kubernetes client
Oct 14 06:09:21.665: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename provisioning
W1014 06:09:22.016163   25190 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Oct 14 06:09:22.016: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Oct 14 06:09:22.116: INFO: Creating resource for dynamic PV
Oct 14 06:09:22.116: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8788-e2e-sc77trx
STEP: creating a claim
Oct 14 06:09:22.172: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-tdvx
STEP: Checking for subpath error in container status
Oct 14 06:09:50.608: INFO: Deleting pod "pod-subpath-test-dynamicpv-tdvx" in namespace "provisioning-8788"
Oct 14 06:09:50.664: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-tdvx" to be fully deleted
STEP: Deleting pod
Oct 14 06:09:54.768: INFO: Deleting pod "pod-subpath-test-dynamicpv-tdvx" in namespace "provisioning-8788"
STEP: Deleting pvc
Oct 14 06:09:54.921: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comtwj4k"
... skipping 15 lines ...

• [SLOW TEST:68.945 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.SekB7YIla/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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 8 lines ...
Oct 14 06:09:50.157: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-180fglwd
STEP: creating a claim
Oct 14 06:09:50.207: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-2bbz
STEP: Creating a pod to test subpath
Oct 14 06:09:50.371: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-2bbz" in namespace "provisioning-180" to be "Succeeded or Failed"
Oct 14 06:09:50.424: INFO: Pod "pod-subpath-test-dynamicpv-2bbz": Phase="Pending", Reason="", readiness=false. Elapsed: 53.370327ms
Oct 14 06:09:52.476: INFO: Pod "pod-subpath-test-dynamicpv-2bbz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.104787246s
Oct 14 06:09:54.527: INFO: Pod "pod-subpath-test-dynamicpv-2bbz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.156022333s
Oct 14 06:09:56.581: INFO: Pod "pod-subpath-test-dynamicpv-2bbz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.209969075s
Oct 14 06:09:58.633: INFO: Pod "pod-subpath-test-dynamicpv-2bbz": Phase="Pending", Reason="", readiness=false. Elapsed: 8.262589903s
Oct 14 06:10:00.684: INFO: Pod "pod-subpath-test-dynamicpv-2bbz": Phase="Pending", Reason="", readiness=false. Elapsed: 10.312797522s
... skipping 2 lines ...
Oct 14 06:10:06.835: INFO: Pod "pod-subpath-test-dynamicpv-2bbz": Phase="Pending", Reason="", readiness=false. Elapsed: 16.464462034s
Oct 14 06:10:08.886: INFO: Pod "pod-subpath-test-dynamicpv-2bbz": Phase="Pending", Reason="", readiness=false. Elapsed: 18.51514258s
Oct 14 06:10:10.937: INFO: Pod "pod-subpath-test-dynamicpv-2bbz": Phase="Pending", Reason="", readiness=false. Elapsed: 20.566059877s
Oct 14 06:10:12.988: INFO: Pod "pod-subpath-test-dynamicpv-2bbz": Phase="Pending", Reason="", readiness=false. Elapsed: 22.61683634s
Oct 14 06:10:15.038: INFO: Pod "pod-subpath-test-dynamicpv-2bbz": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.666747874s
STEP: Saw pod success
Oct 14 06:10:15.038: INFO: Pod "pod-subpath-test-dynamicpv-2bbz" satisfied condition "Succeeded or Failed"
Oct 14 06:10:15.088: INFO: Trying to get logs from node ip-172-20-47-110.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-2bbz container test-container-volume-dynamicpv-2bbz: <nil>
STEP: delete the pod
Oct 14 06:10:15.200: INFO: Waiting for pod pod-subpath-test-dynamicpv-2bbz to disappear
Oct 14 06:10:15.249: INFO: Pod pod-subpath-test-dynamicpv-2bbz no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-2bbz
Oct 14 06:10:15.249: INFO: Deleting pod "pod-subpath-test-dynamicpv-2bbz" in namespace "provisioning-180"
... skipping 39 lines ...
Oct 14 06:09:22.117: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3448-e2e-scfcxpl
STEP: creating a claim
Oct 14 06:09:22.171: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-98sz
STEP: Creating a pod to test subpath
Oct 14 06:09:22.459: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-98sz" in namespace "provisioning-3448" to be "Succeeded or Failed"
Oct 14 06:09:22.529: INFO: Pod "pod-subpath-test-dynamicpv-98sz": Phase="Pending", Reason="", readiness=false. Elapsed: 69.917525ms
Oct 14 06:09:24.579: INFO: Pod "pod-subpath-test-dynamicpv-98sz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.119820378s
Oct 14 06:09:26.631: INFO: Pod "pod-subpath-test-dynamicpv-98sz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.171963831s
Oct 14 06:09:28.698: INFO: Pod "pod-subpath-test-dynamicpv-98sz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.239025195s
Oct 14 06:09:30.749: INFO: Pod "pod-subpath-test-dynamicpv-98sz": Phase="Pending", Reason="", readiness=false. Elapsed: 8.289293012s
Oct 14 06:09:32.799: INFO: Pod "pod-subpath-test-dynamicpv-98sz": Phase="Pending", Reason="", readiness=false. Elapsed: 10.339906661s
Oct 14 06:09:34.851: INFO: Pod "pod-subpath-test-dynamicpv-98sz": Phase="Pending", Reason="", readiness=false. Elapsed: 12.391267911s
Oct 14 06:09:36.901: INFO: Pod "pod-subpath-test-dynamicpv-98sz": Phase="Pending", Reason="", readiness=false. Elapsed: 14.441815016s
Oct 14 06:09:38.958: INFO: Pod "pod-subpath-test-dynamicpv-98sz": Phase="Pending", Reason="", readiness=false. Elapsed: 16.498554086s
Oct 14 06:09:41.009: INFO: Pod "pod-subpath-test-dynamicpv-98sz": Phase="Pending", Reason="", readiness=false. Elapsed: 18.5496882s
Oct 14 06:09:43.060: INFO: Pod "pod-subpath-test-dynamicpv-98sz": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.600829911s
STEP: Saw pod success
Oct 14 06:09:43.060: INFO: Pod "pod-subpath-test-dynamicpv-98sz" satisfied condition "Succeeded or Failed"
Oct 14 06:09:43.112: INFO: Trying to get logs from node ip-172-20-44-65.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-98sz container test-container-subpath-dynamicpv-98sz: <nil>
STEP: delete the pod
Oct 14 06:09:43.233: INFO: Waiting for pod pod-subpath-test-dynamicpv-98sz to disappear
Oct 14 06:09:43.282: INFO: Pod pod-subpath-test-dynamicpv-98sz no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-98sz
Oct 14 06:09:43.282: INFO: Deleting pod "pod-subpath-test-dynamicpv-98sz" in namespace "provisioning-3448"
STEP: Creating pod pod-subpath-test-dynamicpv-98sz
STEP: Creating a pod to test subpath
Oct 14 06:09:43.384: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-98sz" in namespace "provisioning-3448" to be "Succeeded or Failed"
Oct 14 06:09:43.436: INFO: Pod "pod-subpath-test-dynamicpv-98sz": Phase="Pending", Reason="", readiness=false. Elapsed: 52.287582ms
Oct 14 06:09:45.487: INFO: Pod "pod-subpath-test-dynamicpv-98sz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.103005397s
Oct 14 06:09:47.538: INFO: Pod "pod-subpath-test-dynamicpv-98sz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.154143837s
Oct 14 06:09:49.590: INFO: Pod "pod-subpath-test-dynamicpv-98sz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.206248934s
Oct 14 06:09:51.641: INFO: Pod "pod-subpath-test-dynamicpv-98sz": Phase="Pending", Reason="", readiness=false. Elapsed: 8.256929908s
Oct 14 06:09:53.692: INFO: Pod "pod-subpath-test-dynamicpv-98sz": Phase="Pending", Reason="", readiness=false. Elapsed: 10.307516022s
... skipping 8 lines ...
Oct 14 06:10:12.146: INFO: Pod "pod-subpath-test-dynamicpv-98sz": Phase="Pending", Reason="", readiness=false. Elapsed: 28.762174384s
Oct 14 06:10:14.196: INFO: Pod "pod-subpath-test-dynamicpv-98sz": Phase="Pending", Reason="", readiness=false. Elapsed: 30.812081202s
Oct 14 06:10:16.247: INFO: Pod "pod-subpath-test-dynamicpv-98sz": Phase="Pending", Reason="", readiness=false. Elapsed: 32.86259634s
Oct 14 06:10:18.298: INFO: Pod "pod-subpath-test-dynamicpv-98sz": Phase="Pending", Reason="", readiness=false. Elapsed: 34.914323563s
Oct 14 06:10:20.349: INFO: Pod "pod-subpath-test-dynamicpv-98sz": Phase="Succeeded", Reason="", readiness=false. Elapsed: 36.965411196s
STEP: Saw pod success
Oct 14 06:10:20.350: INFO: Pod "pod-subpath-test-dynamicpv-98sz" satisfied condition "Succeeded or Failed"
Oct 14 06:10:20.399: INFO: Trying to get logs from node ip-172-20-47-110.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-98sz container test-container-subpath-dynamicpv-98sz: <nil>
STEP: delete the pod
Oct 14 06:10:20.505: INFO: Waiting for pod pod-subpath-test-dynamicpv-98sz to disappear
Oct 14 06:10:20.556: INFO: Pod pod-subpath-test-dynamicpv-98sz no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-98sz
Oct 14 06:10:20.556: INFO: Deleting pod "pod-subpath-test-dynamicpv-98sz" in namespace "provisioning-3448"
... skipping 177 lines ...

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.SekB7YIla/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.SekB7YIla/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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 95 lines ...
STEP: Deleting pod aws-client in namespace volume-1070
Oct 14 06:10:19.454: INFO: Waiting for pod aws-client to disappear
Oct 14 06:10:19.504: INFO: Pod aws-client still exists
Oct 14 06:10:21.504: INFO: Waiting for pod aws-client to disappear
Oct 14 06:10:21.554: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Oct 14 06:10:21.760: INFO: Couldn't delete PD "aws://us-west-1a/vol-04cd9970a9687754c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04cd9970a9687754c is currently attached to i-019e724f48a0be6c0
	status code: 400, request id: ea77fc9d-cfc0-48cf-8c46-9aa3ce1b3fb2
Oct 14 06:10:27.128: INFO: Couldn't delete PD "aws://us-west-1a/vol-04cd9970a9687754c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04cd9970a9687754c is currently attached to i-019e724f48a0be6c0
	status code: 400, request id: ac5927ad-8883-4d2b-bad8-21314782b4c8
Oct 14 06:10:32.496: INFO: Couldn't delete PD "aws://us-west-1a/vol-04cd9970a9687754c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04cd9970a9687754c is currently attached to i-019e724f48a0be6c0
	status code: 400, request id: ec3e8cd9-2d3e-435d-b01c-30e98b5c4740
Oct 14 06:10:37.837: INFO: Couldn't delete PD "aws://us-west-1a/vol-04cd9970a9687754c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04cd9970a9687754c is currently attached to i-019e724f48a0be6c0
	status code: 400, request id: df5a99c2-219f-480d-8092-ca8c0fc2c7b9
Oct 14 06:10:43.214: INFO: Successfully deleted PD "aws://us-west-1a/vol-04cd9970a9687754c".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 14 06:10:43.214: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-1070" for this suite.
... skipping 308 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.SekB7YIla/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.SekB7YIla/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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 224 lines ...
STEP: Deleting pod aws-client in namespace volume-9965
Oct 14 06:10:27.181: INFO: Waiting for pod aws-client to disappear
Oct 14 06:10:27.233: INFO: Pod aws-client still exists
Oct 14 06:10:29.233: INFO: Waiting for pod aws-client to disappear
Oct 14 06:10:29.288: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Oct 14 06:10:29.442: INFO: Couldn't delete PD "aws://us-west-1a/vol-016c5e2d0c6dbb8e0", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-016c5e2d0c6dbb8e0 is currently attached to i-0f3386771e5823100
	status code: 400, request id: 3a513025-a388-468a-b162-8ade4ebc00b0
Oct 14 06:10:34.804: INFO: Couldn't delete PD "aws://us-west-1a/vol-016c5e2d0c6dbb8e0", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-016c5e2d0c6dbb8e0 is currently attached to i-0f3386771e5823100
	status code: 400, request id: 8475b52b-b0cd-4708-9032-b0f33f0e0479
Oct 14 06:10:40.136: INFO: Couldn't delete PD "aws://us-west-1a/vol-016c5e2d0c6dbb8e0", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-016c5e2d0c6dbb8e0 is currently attached to i-0f3386771e5823100
	status code: 400, request id: a2d00d10-193e-42ac-8a05-aaaafdbe3b9f
Oct 14 06:10:45.474: INFO: Couldn't delete PD "aws://us-west-1a/vol-016c5e2d0c6dbb8e0", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-016c5e2d0c6dbb8e0 is currently attached to i-0f3386771e5823100
	status code: 400, request id: 730b2228-0497-4e10-bfad-b37eedd4f12b
Oct 14 06:10:50.824: INFO: Successfully deleted PD "aws://us-west-1a/vol-016c5e2d0c6dbb8e0".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 14 06:10:50.824: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-9965" for this suite.
... skipping 20 lines ...

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

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

    /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 426 lines ...
Oct 14 06:10:24.406: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-5316-e2e-sc7qhfd
STEP: creating a claim
Oct 14 06:10:24.456: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Oct 14 06:10:24.563: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Oct 14 06:10:24.680: INFO: Error updating pvc ebs.csi.aws.com6l7zd: PersistentVolumeClaim "ebs.csi.aws.com6l7zd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5316-e2e-sc7qhfd",
  	... // 3 identical fields
  }

Oct 14 06:10:26.790: INFO: Error updating pvc ebs.csi.aws.com6l7zd: PersistentVolumeClaim "ebs.csi.aws.com6l7zd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5316-e2e-sc7qhfd",
  	... // 3 identical fields
  }

Oct 14 06:10:28.780: INFO: Error updating pvc ebs.csi.aws.com6l7zd: PersistentVolumeClaim "ebs.csi.aws.com6l7zd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5316-e2e-sc7qhfd",
  	... // 3 identical fields
  }

Oct 14 06:10:30.780: INFO: Error updating pvc ebs.csi.aws.com6l7zd: PersistentVolumeClaim "ebs.csi.aws.com6l7zd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5316-e2e-sc7qhfd",
  	... // 3 identical fields
  }

Oct 14 06:10:32.783: INFO: Error updating pvc ebs.csi.aws.com6l7zd: PersistentVolumeClaim "ebs.csi.aws.com6l7zd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5316-e2e-sc7qhfd",
  	... // 3 identical fields
  }

Oct 14 06:10:34.781: INFO: Error updating pvc ebs.csi.aws.com6l7zd: PersistentVolumeClaim "ebs.csi.aws.com6l7zd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5316-e2e-sc7qhfd",
  	... // 3 identical fields
  }

Oct 14 06:10:36.787: INFO: Error updating pvc ebs.csi.aws.com6l7zd: PersistentVolumeClaim "ebs.csi.aws.com6l7zd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5316-e2e-sc7qhfd",
  	... // 3 identical fields
  }

Oct 14 06:10:38.782: INFO: Error updating pvc ebs.csi.aws.com6l7zd: PersistentVolumeClaim "ebs.csi.aws.com6l7zd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5316-e2e-sc7qhfd",
  	... // 3 identical fields
  }

Oct 14 06:10:40.781: INFO: Error updating pvc ebs.csi.aws.com6l7zd: PersistentVolumeClaim "ebs.csi.aws.com6l7zd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5316-e2e-sc7qhfd",
  	... // 3 identical fields
  }

Oct 14 06:10:42.797: INFO: Error updating pvc ebs.csi.aws.com6l7zd: PersistentVolumeClaim "ebs.csi.aws.com6l7zd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5316-e2e-sc7qhfd",
  	... // 3 identical fields
  }

Oct 14 06:10:44.781: INFO: Error updating pvc ebs.csi.aws.com6l7zd: PersistentVolumeClaim "ebs.csi.aws.com6l7zd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5316-e2e-sc7qhfd",
  	... // 3 identical fields
  }

Oct 14 06:10:46.782: INFO: Error updating pvc ebs.csi.aws.com6l7zd: PersistentVolumeClaim "ebs.csi.aws.com6l7zd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5316-e2e-sc7qhfd",
  	... // 3 identical fields
  }

Oct 14 06:10:48.783: INFO: Error updating pvc ebs.csi.aws.com6l7zd: PersistentVolumeClaim "ebs.csi.aws.com6l7zd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5316-e2e-sc7qhfd",
  	... // 3 identical fields
  }

Oct 14 06:10:50.783: INFO: Error updating pvc ebs.csi.aws.com6l7zd: PersistentVolumeClaim "ebs.csi.aws.com6l7zd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5316-e2e-sc7qhfd",
  	... // 3 identical fields
  }

Oct 14 06:10:52.788: INFO: Error updating pvc ebs.csi.aws.com6l7zd: PersistentVolumeClaim "ebs.csi.aws.com6l7zd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5316-e2e-sc7qhfd",
  	... // 3 identical fields
  }

Oct 14 06:10:54.782: INFO: Error updating pvc ebs.csi.aws.com6l7zd: PersistentVolumeClaim "ebs.csi.aws.com6l7zd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5316-e2e-sc7qhfd",
  	... // 3 identical fields
  }

Oct 14 06:10:54.882: INFO: Error updating pvc ebs.csi.aws.com6l7zd: PersistentVolumeClaim "ebs.csi.aws.com6l7zd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 196 lines ...
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 14 06:10:57.856: 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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Oct 14 06:10:58.193: INFO: found topology map[topology.ebs.csi.aws.com/zone:us-west-1a]
Oct 14 06:10:58.194: 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.497 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.SekB7YIla/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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

    Not enough topologies in cluster -- skipping

    /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 10 lines ...
Oct 14 06:10:29.954: INFO: Creating resource for dynamic PV
Oct 14 06:10:29.954: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-6568-e2e-sck5tlc
STEP: creating a claim
STEP: Expanding non-expandable pvc
Oct 14 06:10:30.111: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Oct 14 06:10:30.213: INFO: Error updating pvc ebs.csi.aws.com7lh4d: PersistentVolumeClaim "ebs.csi.aws.com7lh4d" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6568-e2e-sck5tlc",
  	... // 3 identical fields
  }

Oct 14 06:10:32.316: INFO: Error updating pvc ebs.csi.aws.com7lh4d: PersistentVolumeClaim "ebs.csi.aws.com7lh4d" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6568-e2e-sck5tlc",
  	... // 3 identical fields
  }

Oct 14 06:10:34.316: INFO: Error updating pvc ebs.csi.aws.com7lh4d: PersistentVolumeClaim "ebs.csi.aws.com7lh4d" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6568-e2e-sck5tlc",
  	... // 3 identical fields
  }

Oct 14 06:10:36.319: INFO: Error updating pvc ebs.csi.aws.com7lh4d: PersistentVolumeClaim "ebs.csi.aws.com7lh4d" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6568-e2e-sck5tlc",
  	... // 3 identical fields
  }

Oct 14 06:10:38.316: INFO: Error updating pvc ebs.csi.aws.com7lh4d: PersistentVolumeClaim "ebs.csi.aws.com7lh4d" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6568-e2e-sck5tlc",
  	... // 3 identical fields
  }

Oct 14 06:10:40.317: INFO: Error updating pvc ebs.csi.aws.com7lh4d: PersistentVolumeClaim "ebs.csi.aws.com7lh4d" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6568-e2e-sck5tlc",
  	... // 3 identical fields
  }

Oct 14 06:10:42.317: INFO: Error updating pvc ebs.csi.aws.com7lh4d: PersistentVolumeClaim "ebs.csi.aws.com7lh4d" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6568-e2e-sck5tlc",
  	... // 3 identical fields
  }

Oct 14 06:10:44.316: INFO: Error updating pvc ebs.csi.aws.com7lh4d: PersistentVolumeClaim "ebs.csi.aws.com7lh4d" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6568-e2e-sck5tlc",
  	... // 3 identical fields
  }

Oct 14 06:10:46.317: INFO: Error updating pvc ebs.csi.aws.com7lh4d: PersistentVolumeClaim "ebs.csi.aws.com7lh4d" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6568-e2e-sck5tlc",
  	... // 3 identical fields
  }

Oct 14 06:10:48.316: INFO: Error updating pvc ebs.csi.aws.com7lh4d: PersistentVolumeClaim "ebs.csi.aws.com7lh4d" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6568-e2e-sck5tlc",
  	... // 3 identical fields
  }

Oct 14 06:10:50.326: INFO: Error updating pvc ebs.csi.aws.com7lh4d: PersistentVolumeClaim "ebs.csi.aws.com7lh4d" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6568-e2e-sck5tlc",
  	... // 3 identical fields
  }

Oct 14 06:10:52.320: INFO: Error updating pvc ebs.csi.aws.com7lh4d: PersistentVolumeClaim "ebs.csi.aws.com7lh4d" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6568-e2e-sck5tlc",
  	... // 3 identical fields
  }

Oct 14 06:10:54.317: INFO: Error updating pvc ebs.csi.aws.com7lh4d: PersistentVolumeClaim "ebs.csi.aws.com7lh4d" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6568-e2e-sck5tlc",
  	... // 3 identical fields
  }

Oct 14 06:10:56.321: INFO: Error updating pvc ebs.csi.aws.com7lh4d: PersistentVolumeClaim "ebs.csi.aws.com7lh4d" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6568-e2e-sck5tlc",
  	... // 3 identical fields
  }

Oct 14 06:10:58.315: INFO: Error updating pvc ebs.csi.aws.com7lh4d: PersistentVolumeClaim "ebs.csi.aws.com7lh4d" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6568-e2e-sck5tlc",
  	... // 3 identical fields
  }

Oct 14 06:11:00.392: INFO: Error updating pvc ebs.csi.aws.com7lh4d: PersistentVolumeClaim "ebs.csi.aws.com7lh4d" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-6568-e2e-sck5tlc",
  	... // 3 identical fields
  }

Oct 14 06:11:00.504: INFO: Error updating pvc ebs.csi.aws.com7lh4d: PersistentVolumeClaim "ebs.csi.aws.com7lh4d" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 76 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.SekB7YIla/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.SekB7YIla/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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 148 lines ...
Oct 14 06:10:46.029: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6472dvtq4
STEP: creating a claim
Oct 14 06:10:46.084: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-kx6v
STEP: Creating a pod to test subpath
Oct 14 06:10:46.242: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-kx6v" in namespace "provisioning-6472" to be "Succeeded or Failed"
Oct 14 06:10:46.293: INFO: Pod "pod-subpath-test-dynamicpv-kx6v": Phase="Pending", Reason="", readiness=false. Elapsed: 51.006906ms
Oct 14 06:10:48.343: INFO: Pod "pod-subpath-test-dynamicpv-kx6v": Phase="Pending", Reason="", readiness=false. Elapsed: 2.101524706s
Oct 14 06:10:50.395: INFO: Pod "pod-subpath-test-dynamicpv-kx6v": Phase="Pending", Reason="", readiness=false. Elapsed: 4.153213432s
Oct 14 06:10:52.445: INFO: Pod "pod-subpath-test-dynamicpv-kx6v": Phase="Pending", Reason="", readiness=false. Elapsed: 6.203669438s
Oct 14 06:10:54.497: INFO: Pod "pod-subpath-test-dynamicpv-kx6v": Phase="Pending", Reason="", readiness=false. Elapsed: 8.254809643s
Oct 14 06:10:56.547: INFO: Pod "pod-subpath-test-dynamicpv-kx6v": Phase="Pending", Reason="", readiness=false. Elapsed: 10.305498709s
Oct 14 06:10:58.597: INFO: Pod "pod-subpath-test-dynamicpv-kx6v": Phase="Pending", Reason="", readiness=false. Elapsed: 12.355424788s
Oct 14 06:11:00.656: INFO: Pod "pod-subpath-test-dynamicpv-kx6v": Phase="Pending", Reason="", readiness=false. Elapsed: 14.41421591s
Oct 14 06:11:02.706: INFO: Pod "pod-subpath-test-dynamicpv-kx6v": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.464619867s
STEP: Saw pod success
Oct 14 06:11:02.706: INFO: Pod "pod-subpath-test-dynamicpv-kx6v" satisfied condition "Succeeded or Failed"
Oct 14 06:11:02.757: INFO: Trying to get logs from node ip-172-20-37-170.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-kx6v container test-container-subpath-dynamicpv-kx6v: <nil>
STEP: delete the pod
Oct 14 06:11:02.876: INFO: Waiting for pod pod-subpath-test-dynamicpv-kx6v to disappear
Oct 14 06:11:02.928: INFO: Pod pod-subpath-test-dynamicpv-kx6v no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-kx6v
Oct 14 06:11:02.928: INFO: Deleting pod "pod-subpath-test-dynamicpv-kx6v" in namespace "provisioning-6472"
... skipping 463 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.SekB7YIla/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.SekB7YIla/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.SekB7YIla/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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 53 lines ...
Oct 14 06:10:57.920: INFO: PersistentVolumeClaim pvc-rjgh9 found but phase is Pending instead of Bound.
Oct 14 06:10:59.970: INFO: PersistentVolumeClaim pvc-rjgh9 found and phase=Bound (6.215039644s)
Oct 14 06:10:59.970: INFO: Waiting up to 3m0s for PersistentVolume aws-9sn5q to have phase Bound
Oct 14 06:11:00.019: INFO: PersistentVolume aws-9sn5q found and phase=Bound (49.640868ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-rfnx
STEP: Creating a pod to test exec-volume-test
Oct 14 06:11:00.178: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-rfnx" in namespace "volume-8872" to be "Succeeded or Failed"
Oct 14 06:11:00.230: INFO: Pod "exec-volume-test-preprovisionedpv-rfnx": Phase="Pending", Reason="", readiness=false. Elapsed: 52.178768ms
Oct 14 06:11:02.282: INFO: Pod "exec-volume-test-preprovisionedpv-rfnx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.103836712s
Oct 14 06:11:04.337: INFO: Pod "exec-volume-test-preprovisionedpv-rfnx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.159597837s
Oct 14 06:11:06.387: INFO: Pod "exec-volume-test-preprovisionedpv-rfnx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.209567633s
Oct 14 06:11:08.438: INFO: Pod "exec-volume-test-preprovisionedpv-rfnx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.260044086s
Oct 14 06:11:10.490: INFO: Pod "exec-volume-test-preprovisionedpv-rfnx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.312373781s
STEP: Saw pod success
Oct 14 06:11:10.490: INFO: Pod "exec-volume-test-preprovisionedpv-rfnx" satisfied condition "Succeeded or Failed"
Oct 14 06:11:10.544: INFO: Trying to get logs from node ip-172-20-44-65.us-west-1.compute.internal pod exec-volume-test-preprovisionedpv-rfnx container exec-container-preprovisionedpv-rfnx: <nil>
STEP: delete the pod
Oct 14 06:11:10.672: INFO: Waiting for pod exec-volume-test-preprovisionedpv-rfnx to disappear
Oct 14 06:11:10.723: INFO: Pod exec-volume-test-preprovisionedpv-rfnx no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-rfnx
Oct 14 06:11:10.723: INFO: Deleting pod "exec-volume-test-preprovisionedpv-rfnx" in namespace "volume-8872"
STEP: Deleting pv and pvc
Oct 14 06:11:10.783: INFO: Deleting PersistentVolumeClaim "pvc-rjgh9"
Oct 14 06:11:10.834: INFO: Deleting PersistentVolume "aws-9sn5q"
Oct 14 06:11:11.039: INFO: Couldn't delete PD "aws://us-west-1a/vol-01fa5f727aa7ed7e8", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01fa5f727aa7ed7e8 is currently attached to i-0f3386771e5823100
	status code: 400, request id: 5b0c8194-34d2-4e7a-bc1f-d5688d1c711d
Oct 14 06:11:16.345: INFO: Couldn't delete PD "aws://us-west-1a/vol-01fa5f727aa7ed7e8", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01fa5f727aa7ed7e8 is currently attached to i-0f3386771e5823100
	status code: 400, request id: d763cd7f-e8a1-44e3-8d5a-c5d69dd85efd
Oct 14 06:11:21.692: INFO: Couldn't delete PD "aws://us-west-1a/vol-01fa5f727aa7ed7e8", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01fa5f727aa7ed7e8 is currently attached to i-0f3386771e5823100
	status code: 400, request id: 8c940b5f-874a-485c-a18e-5c4fe7cf98ff
Oct 14 06:11:27.034: INFO: Couldn't delete PD "aws://us-west-1a/vol-01fa5f727aa7ed7e8", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01fa5f727aa7ed7e8 is currently attached to i-0f3386771e5823100
	status code: 400, request id: 2e44d941-143e-482c-92d8-d0501981edbc
Oct 14 06:11:32.461: INFO: Couldn't delete PD "aws://us-west-1a/vol-01fa5f727aa7ed7e8", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01fa5f727aa7ed7e8 is currently attached to i-0f3386771e5823100
	status code: 400, request id: 10866932-ca56-4498-9e91-404ddbf6dd2b
Oct 14 06:11:37.839: INFO: Successfully deleted PD "aws://us-west-1a/vol-01fa5f727aa7ed7e8".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 14 06:11:37.839: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8872" for this suite.
... skipping 340 lines ...
Oct 14 06:10:43.069: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-870r9f9m
STEP: creating a claim
Oct 14 06:10:43.122: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-bfs4
STEP: Creating a pod to test subpath
Oct 14 06:10:43.287: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-bfs4" in namespace "provisioning-870" to be "Succeeded or Failed"
Oct 14 06:10:43.341: INFO: Pod "pod-subpath-test-dynamicpv-bfs4": Phase="Pending", Reason="", readiness=false. Elapsed: 53.586351ms
Oct 14 06:10:45.394: INFO: Pod "pod-subpath-test-dynamicpv-bfs4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.107027451s
Oct 14 06:10:47.448: INFO: Pod "pod-subpath-test-dynamicpv-bfs4": Phase="Pending", Reason="", readiness=false. Elapsed: 4.160463419s
Oct 14 06:10:49.500: INFO: Pod "pod-subpath-test-dynamicpv-bfs4": Phase="Pending", Reason="", readiness=false. Elapsed: 6.212722337s
Oct 14 06:10:51.552: INFO: Pod "pod-subpath-test-dynamicpv-bfs4": Phase="Pending", Reason="", readiness=false. Elapsed: 8.264751314s
Oct 14 06:10:53.604: INFO: Pod "pod-subpath-test-dynamicpv-bfs4": Phase="Pending", Reason="", readiness=false. Elapsed: 10.316966405s
... skipping 2 lines ...
Oct 14 06:10:59.760: INFO: Pod "pod-subpath-test-dynamicpv-bfs4": Phase="Pending", Reason="", readiness=false. Elapsed: 16.472421613s
Oct 14 06:11:01.812: INFO: Pod "pod-subpath-test-dynamicpv-bfs4": Phase="Pending", Reason="", readiness=false. Elapsed: 18.524946836s
Oct 14 06:11:03.864: INFO: Pod "pod-subpath-test-dynamicpv-bfs4": Phase="Pending", Reason="", readiness=false. Elapsed: 20.576968581s
Oct 14 06:11:05.925: INFO: Pod "pod-subpath-test-dynamicpv-bfs4": Phase="Pending", Reason="", readiness=false. Elapsed: 22.637552823s
Oct 14 06:11:07.976: INFO: Pod "pod-subpath-test-dynamicpv-bfs4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.689301935s
STEP: Saw pod success
Oct 14 06:11:07.977: INFO: Pod "pod-subpath-test-dynamicpv-bfs4" satisfied condition "Succeeded or Failed"
Oct 14 06:11:08.028: INFO: Trying to get logs from node ip-172-20-47-110.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-bfs4 container test-container-subpath-dynamicpv-bfs4: <nil>
STEP: delete the pod
Oct 14 06:11:08.144: INFO: Waiting for pod pod-subpath-test-dynamicpv-bfs4 to disappear
Oct 14 06:11:08.198: INFO: Pod pod-subpath-test-dynamicpv-bfs4 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-bfs4
Oct 14 06:11:08.198: INFO: Deleting pod "pod-subpath-test-dynamicpv-bfs4" in namespace "provisioning-870"
... skipping 211 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.SekB7YIla/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.SekB7YIla/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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 227 lines ...
Oct 14 06:10:58.613: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-7414-e2e-sc59r24      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-7414    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-7414-e2e-sc59r24,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-7414    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-7414-e2e-sc59r24,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-7414    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-7414-e2e-sc59r24,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-7414-e2e-sc59r24    6a327a04-ba58-43d8-966f-64d6ce237716 5695 0 2021-10-14 06:10:58 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-10-14 06:10:58 +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-djhht pvc- provisioning-7414  cda3a708-6794-4c31-ac6a-36f46bd733b4 5699 0 2021-10-14 06:10:58 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-10-14 06:10:58 +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-7414-e2e-sc59r24,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-635a7c3a-4d60-4c28-8cc0-79b34f7db455 in namespace provisioning-7414
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Oct 14 06:11:11.242: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-tjdq5" in namespace "provisioning-7414" to be "Succeeded or Failed"
Oct 14 06:11:11.297: INFO: Pod "pvc-volume-tester-writer-tjdq5": Phase="Pending", Reason="", readiness=false. Elapsed: 54.291236ms
Oct 14 06:11:13.349: INFO: Pod "pvc-volume-tester-writer-tjdq5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.106319951s
Oct 14 06:11:15.403: INFO: Pod "pvc-volume-tester-writer-tjdq5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.160292235s
STEP: Saw pod success
Oct 14 06:11:15.403: INFO: Pod "pvc-volume-tester-writer-tjdq5" satisfied condition "Succeeded or Failed"
Oct 14 06:11:15.510: INFO: Pod pvc-volume-tester-writer-tjdq5 has the following logs: 
Oct 14 06:11:15.510: INFO: Deleting pod "pvc-volume-tester-writer-tjdq5" in namespace "provisioning-7414"
Oct 14 06:11:15.568: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-tjdq5" 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-47-110.us-west-1.compute.internal"
Oct 14 06:11:15.775: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-mr94r" in namespace "provisioning-7414" to be "Succeeded or Failed"
Oct 14 06:11:15.828: INFO: Pod "pvc-volume-tester-reader-mr94r": Phase="Pending", Reason="", readiness=false. Elapsed: 52.909094ms
Oct 14 06:11:17.881: INFO: Pod "pvc-volume-tester-reader-mr94r": Phase="Pending", Reason="", readiness=false. Elapsed: 2.106169896s
Oct 14 06:11:19.933: INFO: Pod "pvc-volume-tester-reader-mr94r": Phase="Pending", Reason="", readiness=false. Elapsed: 4.158041237s
Oct 14 06:11:21.990: INFO: Pod "pvc-volume-tester-reader-mr94r": Phase="Pending", Reason="", readiness=false. Elapsed: 6.214419719s
Oct 14 06:11:24.042: INFO: Pod "pvc-volume-tester-reader-mr94r": Phase="Pending", Reason="", readiness=false. Elapsed: 8.266859621s
Oct 14 06:11:26.094: INFO: Pod "pvc-volume-tester-reader-mr94r": Phase="Pending", Reason="", readiness=false. Elapsed: 10.318899167s
Oct 14 06:11:28.148: INFO: Pod "pvc-volume-tester-reader-mr94r": Phase="Pending", Reason="", readiness=false. Elapsed: 12.372419754s
Oct 14 06:11:30.200: INFO: Pod "pvc-volume-tester-reader-mr94r": Phase="Pending", Reason="", readiness=false. Elapsed: 14.424536989s
Oct 14 06:11:32.252: INFO: Pod "pvc-volume-tester-reader-mr94r": Phase="Pending", Reason="", readiness=false. Elapsed: 16.476731008s
Oct 14 06:11:34.304: INFO: Pod "pvc-volume-tester-reader-mr94r": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.528737276s
STEP: Saw pod success
Oct 14 06:11:34.304: INFO: Pod "pvc-volume-tester-reader-mr94r" satisfied condition "Succeeded or Failed"
Oct 14 06:11:34.410: INFO: Pod pvc-volume-tester-reader-mr94r has the following logs: hello world

Oct 14 06:11:34.410: INFO: Deleting pod "pvc-volume-tester-reader-mr94r" in namespace "provisioning-7414"
Oct 14 06:11:34.474: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-mr94r" to be fully deleted
Oct 14 06:11:34.526: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-djhht] to have phase Bound
Oct 14 06:11:34.578: INFO: PersistentVolumeClaim pvc-djhht found and phase=Bound (51.919644ms)
... skipping 31 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 14 06:11:38.314: 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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Oct 14 06:11:38.563: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 14 06:11:38.563: INFO: Creating resource for dynamic PV
Oct 14 06:11:38.563: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1876s7gw2
STEP: creating a claim
Oct 14 06:11:38.614: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-xx6s
STEP: Checking for subpath error in container status
Oct 14 06:11:52.870: INFO: Deleting pod "pod-subpath-test-dynamicpv-xx6s" in namespace "provisioning-1876"
Oct 14 06:11:52.921: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-xx6s" to be fully deleted
STEP: Deleting pod
Oct 14 06:11:55.022: INFO: Deleting pod "pod-subpath-test-dynamicpv-xx6s" in namespace "provisioning-1876"
STEP: Deleting pvc
Oct 14 06:11:55.173: INFO: Deleting PersistentVolumeClaim "aws4l2jz"
... skipping 13 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.SekB7YIla/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.SekB7YIla/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.SekB7YIla/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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 250 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.SekB7YIla/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.SekB7YIla/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.SekB7YIla/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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 12 lines ...
Oct 14 06:11:24.225: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-3723jjmvd
STEP: creating a claim
Oct 14 06:11:24.278: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-psmj
STEP: Creating a pod to test exec-volume-test
Oct 14 06:11:24.437: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-psmj" in namespace "volume-3723" to be "Succeeded or Failed"
Oct 14 06:11:24.491: INFO: Pod "exec-volume-test-dynamicpv-psmj": Phase="Pending", Reason="", readiness=false. Elapsed: 53.475178ms
Oct 14 06:11:26.543: INFO: Pod "exec-volume-test-dynamicpv-psmj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.105388033s
Oct 14 06:11:28.594: INFO: Pod "exec-volume-test-dynamicpv-psmj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.156453666s
Oct 14 06:11:30.645: INFO: Pod "exec-volume-test-dynamicpv-psmj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.208083812s
Oct 14 06:11:32.697: INFO: Pod "exec-volume-test-dynamicpv-psmj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.260050417s
Oct 14 06:11:34.750: INFO: Pod "exec-volume-test-dynamicpv-psmj": Phase="Pending", Reason="", readiness=false. Elapsed: 10.312410094s
... skipping 10 lines ...
Oct 14 06:11:57.382: INFO: Pod "exec-volume-test-dynamicpv-psmj": Phase="Pending", Reason="", readiness=false. Elapsed: 32.944661207s
Oct 14 06:11:59.434: INFO: Pod "exec-volume-test-dynamicpv-psmj": Phase="Pending", Reason="", readiness=false. Elapsed: 34.997071818s
Oct 14 06:12:01.486: INFO: Pod "exec-volume-test-dynamicpv-psmj": Phase="Pending", Reason="", readiness=false. Elapsed: 37.048983905s
Oct 14 06:12:03.538: INFO: Pod "exec-volume-test-dynamicpv-psmj": Phase="Pending", Reason="", readiness=false. Elapsed: 39.101339457s
Oct 14 06:12:05.591: INFO: Pod "exec-volume-test-dynamicpv-psmj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 41.153627748s
STEP: Saw pod success
Oct 14 06:12:05.591: INFO: Pod "exec-volume-test-dynamicpv-psmj" satisfied condition "Succeeded or Failed"
Oct 14 06:12:05.642: INFO: Trying to get logs from node ip-172-20-37-170.us-west-1.compute.internal pod exec-volume-test-dynamicpv-psmj container exec-container-dynamicpv-psmj: <nil>
STEP: delete the pod
Oct 14 06:12:05.755: INFO: Waiting for pod exec-volume-test-dynamicpv-psmj to disappear
Oct 14 06:12:05.805: INFO: Pod exec-volume-test-dynamicpv-psmj no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-psmj
Oct 14 06:12:05.805: INFO: Deleting pod "exec-volume-test-dynamicpv-psmj" in namespace "volume-3723"
... skipping 33 lines ...
Oct 14 06:12:05.029: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Oct 14 06:12:05.546: INFO: Successfully created a new PD: "aws://us-west-1a/vol-0c30f73b079ad1828".
Oct 14 06:12:05.546: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-m96q
STEP: Creating a pod to test exec-volume-test
Oct 14 06:12:05.598: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-m96q" in namespace "volume-6576" to be "Succeeded or Failed"
Oct 14 06:12:05.647: INFO: Pod "exec-volume-test-inlinevolume-m96q": Phase="Pending", Reason="", readiness=false. Elapsed: 49.147915ms
Oct 14 06:12:07.701: INFO: Pod "exec-volume-test-inlinevolume-m96q": Phase="Pending", Reason="", readiness=false. Elapsed: 2.103568925s
Oct 14 06:12:09.752: INFO: Pod "exec-volume-test-inlinevolume-m96q": Phase="Pending", Reason="", readiness=false. Elapsed: 4.154758281s
Oct 14 06:12:11.802: INFO: Pod "exec-volume-test-inlinevolume-m96q": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.204569211s
STEP: Saw pod success
Oct 14 06:12:11.802: INFO: Pod "exec-volume-test-inlinevolume-m96q" satisfied condition "Succeeded or Failed"
Oct 14 06:12:11.857: INFO: Trying to get logs from node ip-172-20-37-170.us-west-1.compute.internal pod exec-volume-test-inlinevolume-m96q container exec-container-inlinevolume-m96q: <nil>
STEP: delete the pod
Oct 14 06:12:11.970: INFO: Waiting for pod exec-volume-test-inlinevolume-m96q to disappear
Oct 14 06:12:12.019: INFO: Pod exec-volume-test-inlinevolume-m96q no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-m96q
Oct 14 06:12:12.020: INFO: Deleting pod "exec-volume-test-inlinevolume-m96q" in namespace "volume-6576"
Oct 14 06:12:12.247: INFO: Couldn't delete PD "aws://us-west-1a/vol-0c30f73b079ad1828", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c30f73b079ad1828 is currently attached to i-0f33202ea8f247785
	status code: 400, request id: 5343b9f8-02e2-4540-8c4e-70732019bc23
Oct 14 06:12:17.616: INFO: Couldn't delete PD "aws://us-west-1a/vol-0c30f73b079ad1828", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c30f73b079ad1828 is currently attached to i-0f33202ea8f247785
	status code: 400, request id: 11c785aa-7971-4510-8afe-0ee68a09a13c
Oct 14 06:12:22.986: INFO: Successfully deleted PD "aws://us-west-1a/vol-0c30f73b079ad1828".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 14 06:12:22.986: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-6576" for this suite.
... skipping 150 lines ...
Oct 14 06:11:10.049: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1609-e2e-scx5vh5
STEP: creating a claim
Oct 14 06:11:10.099: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-4tj2
STEP: Creating a pod to test subpath
Oct 14 06:11:10.255: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-4tj2" in namespace "provisioning-1609" to be "Succeeded or Failed"
Oct 14 06:11:10.305: INFO: Pod "pod-subpath-test-dynamicpv-4tj2": Phase="Pending", Reason="", readiness=false. Elapsed: 49.496249ms
Oct 14 06:11:12.355: INFO: Pod "pod-subpath-test-dynamicpv-4tj2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.099394764s
Oct 14 06:11:14.407: INFO: Pod "pod-subpath-test-dynamicpv-4tj2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.151327345s
Oct 14 06:11:16.457: INFO: Pod "pod-subpath-test-dynamicpv-4tj2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.201403176s
Oct 14 06:11:18.507: INFO: Pod "pod-subpath-test-dynamicpv-4tj2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.251771868s
Oct 14 06:11:20.558: INFO: Pod "pod-subpath-test-dynamicpv-4tj2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.30241144s
... skipping 10 lines ...
Oct 14 06:11:43.135: INFO: Pod "pod-subpath-test-dynamicpv-4tj2": Phase="Pending", Reason="", readiness=false. Elapsed: 32.879717143s
Oct 14 06:11:45.186: INFO: Pod "pod-subpath-test-dynamicpv-4tj2": Phase="Pending", Reason="", readiness=false. Elapsed: 34.931073766s
Oct 14 06:11:47.244: INFO: Pod "pod-subpath-test-dynamicpv-4tj2": Phase="Pending", Reason="", readiness=false. Elapsed: 36.988598996s
Oct 14 06:11:49.297: INFO: Pod "pod-subpath-test-dynamicpv-4tj2": Phase="Pending", Reason="", readiness=false. Elapsed: 39.041439021s
Oct 14 06:11:51.348: INFO: Pod "pod-subpath-test-dynamicpv-4tj2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 41.092680195s
STEP: Saw pod success
Oct 14 06:11:51.348: INFO: Pod "pod-subpath-test-dynamicpv-4tj2" satisfied condition "Succeeded or Failed"
Oct 14 06:11:51.398: INFO: Trying to get logs from node ip-172-20-47-110.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-4tj2 container test-container-volume-dynamicpv-4tj2: <nil>
STEP: delete the pod
Oct 14 06:11:51.525: INFO: Waiting for pod pod-subpath-test-dynamicpv-4tj2 to disappear
Oct 14 06:11:51.574: INFO: Pod pod-subpath-test-dynamicpv-4tj2 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-4tj2
Oct 14 06:11:51.574: INFO: Deleting pod "pod-subpath-test-dynamicpv-4tj2" in namespace "provisioning-1609"
... skipping 40 lines ...
Oct 14 06:11:37.478: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2082lxk48
STEP: creating a claim
Oct 14 06:11:37.536: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-h4c2
STEP: Creating a pod to test atomic-volume-subpath
Oct 14 06:11:37.688: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-h4c2" in namespace "provisioning-2082" to be "Succeeded or Failed"
Oct 14 06:11:37.738: INFO: Pod "pod-subpath-test-dynamicpv-h4c2": Phase="Pending", Reason="", readiness=false. Elapsed: 49.706075ms
Oct 14 06:11:39.789: INFO: Pod "pod-subpath-test-dynamicpv-h4c2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.100892375s
Oct 14 06:11:41.840: INFO: Pod "pod-subpath-test-dynamicpv-h4c2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.151871687s
Oct 14 06:11:43.891: INFO: Pod "pod-subpath-test-dynamicpv-h4c2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.203062658s
Oct 14 06:11:45.943: INFO: Pod "pod-subpath-test-dynamicpv-h4c2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.254589077s
Oct 14 06:11:47.996: INFO: Pod "pod-subpath-test-dynamicpv-h4c2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.30818051s
... skipping 11 lines ...
Oct 14 06:12:12.609: INFO: Pod "pod-subpath-test-dynamicpv-h4c2": Phase="Running", Reason="", readiness=true. Elapsed: 34.920906257s
Oct 14 06:12:14.659: INFO: Pod "pod-subpath-test-dynamicpv-h4c2": Phase="Running", Reason="", readiness=true. Elapsed: 36.971083967s
Oct 14 06:12:16.709: INFO: Pod "pod-subpath-test-dynamicpv-h4c2": Phase="Running", Reason="", readiness=true. Elapsed: 39.021338921s
Oct 14 06:12:18.761: INFO: Pod "pod-subpath-test-dynamicpv-h4c2": Phase="Running", Reason="", readiness=true. Elapsed: 41.073186527s
Oct 14 06:12:20.812: INFO: Pod "pod-subpath-test-dynamicpv-h4c2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 43.12423487s
STEP: Saw pod success
Oct 14 06:12:20.812: INFO: Pod "pod-subpath-test-dynamicpv-h4c2" satisfied condition "Succeeded or Failed"
Oct 14 06:12:20.862: INFO: Trying to get logs from node ip-172-20-37-170.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-h4c2 container test-container-subpath-dynamicpv-h4c2: <nil>
STEP: delete the pod
Oct 14 06:12:20.980: INFO: Waiting for pod pod-subpath-test-dynamicpv-h4c2 to disappear
Oct 14 06:12:21.037: INFO: Pod pod-subpath-test-dynamicpv-h4c2 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-h4c2
Oct 14 06:12:21.037: INFO: Deleting pod "pod-subpath-test-dynamicpv-h4c2" in namespace "provisioning-2082"
... skipping 38 lines ...
Oct 14 06:12:10.636: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-32274t76j
STEP: creating a claim
Oct 14 06:12:10.688: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-8cbp
STEP: Creating a pod to test multi_subpath
Oct 14 06:12:10.857: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-8cbp" in namespace "provisioning-3227" to be "Succeeded or Failed"
Oct 14 06:12:10.909: INFO: Pod "pod-subpath-test-dynamicpv-8cbp": Phase="Pending", Reason="", readiness=false. Elapsed: 52.482965ms
Oct 14 06:12:12.962: INFO: Pod "pod-subpath-test-dynamicpv-8cbp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.10502337s
Oct 14 06:12:15.015: INFO: Pod "pod-subpath-test-dynamicpv-8cbp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.158415771s
Oct 14 06:12:17.068: INFO: Pod "pod-subpath-test-dynamicpv-8cbp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.211002314s
Oct 14 06:12:19.120: INFO: Pod "pod-subpath-test-dynamicpv-8cbp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.263236307s
Oct 14 06:12:21.172: INFO: Pod "pod-subpath-test-dynamicpv-8cbp": Phase="Pending", Reason="", readiness=false. Elapsed: 10.315589945s
Oct 14 06:12:23.227: INFO: Pod "pod-subpath-test-dynamicpv-8cbp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.370230396s
STEP: Saw pod success
Oct 14 06:12:23.227: INFO: Pod "pod-subpath-test-dynamicpv-8cbp" satisfied condition "Succeeded or Failed"
Oct 14 06:12:23.283: INFO: Trying to get logs from node ip-172-20-44-65.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-8cbp container test-container-subpath-dynamicpv-8cbp: <nil>
STEP: delete the pod
Oct 14 06:12:23.408: INFO: Waiting for pod pod-subpath-test-dynamicpv-8cbp to disappear
Oct 14 06:12:23.459: INFO: Pod pod-subpath-test-dynamicpv-8cbp no longer exists
STEP: Deleting pod
Oct 14 06:12:23.459: INFO: Deleting pod "pod-subpath-test-dynamicpv-8cbp" in namespace "provisioning-3227"
... skipping 77 lines ...
Oct 14 06:12:11.593: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-4578kjh72
STEP: creating a claim
Oct 14 06:12:11.644: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-4kkq
STEP: Creating a pod to test exec-volume-test
Oct 14 06:12:11.797: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-4kkq" in namespace "volume-4578" to be "Succeeded or Failed"
Oct 14 06:12:11.848: INFO: Pod "exec-volume-test-dynamicpv-4kkq": Phase="Pending", Reason="", readiness=false. Elapsed: 50.692551ms
Oct 14 06:12:13.899: INFO: Pod "exec-volume-test-dynamicpv-4kkq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.102261653s
Oct 14 06:12:15.954: INFO: Pod "exec-volume-test-dynamicpv-4kkq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.157431131s
Oct 14 06:12:18.007: INFO: Pod "exec-volume-test-dynamicpv-4kkq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.209555241s
Oct 14 06:12:20.057: INFO: Pod "exec-volume-test-dynamicpv-4kkq": Phase="Pending", Reason="", readiness=false. Elapsed: 8.259805519s
Oct 14 06:12:22.108: INFO: Pod "exec-volume-test-dynamicpv-4kkq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.311090976s
STEP: Saw pod success
Oct 14 06:12:22.108: INFO: Pod "exec-volume-test-dynamicpv-4kkq" satisfied condition "Succeeded or Failed"
Oct 14 06:12:22.157: INFO: Trying to get logs from node ip-172-20-37-170.us-west-1.compute.internal pod exec-volume-test-dynamicpv-4kkq container exec-container-dynamicpv-4kkq: <nil>
STEP: delete the pod
Oct 14 06:12:22.264: INFO: Waiting for pod exec-volume-test-dynamicpv-4kkq to disappear
Oct 14 06:12:22.316: INFO: Pod exec-volume-test-dynamicpv-4kkq no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-4kkq
Oct 14 06:12:22.316: INFO: Deleting pod "exec-volume-test-dynamicpv-4kkq" in namespace "volume-4578"
... skipping 56 lines ...
Oct 14 06:09:21.969: INFO: Creating resource for dynamic PV
Oct 14 06:09:21.969: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-4368-e2e-scq7cc4
STEP: creating a claim
Oct 14 06:09:22.027: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Oct 14 06:09:22.183: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-wrjcx" in namespace "snapshotting-4368" to be "Succeeded or Failed"
Oct 14 06:09:22.275: INFO: Pod "pvc-snapshottable-tester-wrjcx": Phase="Pending", Reason="", readiness=false. Elapsed: 92.052925ms
Oct 14 06:09:24.326: INFO: Pod "pvc-snapshottable-tester-wrjcx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.143037084s
Oct 14 06:09:26.380: INFO: Pod "pvc-snapshottable-tester-wrjcx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.197254127s
Oct 14 06:09:28.430: INFO: Pod "pvc-snapshottable-tester-wrjcx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.24712213s
Oct 14 06:09:30.483: INFO: Pod "pvc-snapshottable-tester-wrjcx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.300388719s
Oct 14 06:09:32.534: INFO: Pod "pvc-snapshottable-tester-wrjcx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.351290403s
Oct 14 06:09:34.584: INFO: Pod "pvc-snapshottable-tester-wrjcx": Phase="Pending", Reason="", readiness=false. Elapsed: 12.401293198s
Oct 14 06:09:36.634: INFO: Pod "pvc-snapshottable-tester-wrjcx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.450968932s
STEP: Saw pod success
Oct 14 06:09:36.634: INFO: Pod "pvc-snapshottable-tester-wrjcx" satisfied condition "Succeeded or Failed"
Oct 14 06:09:37.254: INFO: Pod pvc-snapshottable-tester-wrjcx has the following logs: 
Oct 14 06:09:37.254: INFO: Deleting pod "pvc-snapshottable-tester-wrjcx" in namespace "snapshotting-4368"
Oct 14 06:09:37.308: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-wrjcx" to be fully deleted
Oct 14 06:09:37.358: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.combmzzc] to have phase Bound
Oct 14 06:09:37.407: INFO: PersistentVolumeClaim ebs.csi.aws.combmzzc found and phase=Bound (49.645133ms)
STEP: [init] checking the claim
... skipping 55 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:243
STEP: checking the snapshot
STEP: checking the SnapshotContent
STEP: Modifying source data test
STEP: modifying the data in the source PVC
Oct 14 06:11:10.349: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-ldhd8" in namespace "snapshotting-4368" to be "Succeeded or Failed"
Oct 14 06:11:10.407: INFO: Pod "pvc-snapshottable-data-tester-ldhd8": Phase="Pending", Reason="", readiness=false. Elapsed: 57.594968ms
Oct 14 06:11:12.460: INFO: Pod "pvc-snapshottable-data-tester-ldhd8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.110530625s
Oct 14 06:11:14.516: INFO: Pod "pvc-snapshottable-data-tester-ldhd8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.166478616s
Oct 14 06:11:16.565: INFO: Pod "pvc-snapshottable-data-tester-ldhd8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.216205513s
Oct 14 06:11:18.619: INFO: Pod "pvc-snapshottable-data-tester-ldhd8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.269448091s
Oct 14 06:11:20.669: INFO: Pod "pvc-snapshottable-data-tester-ldhd8": Phase="Pending", Reason="", readiness=false. Elapsed: 10.320126329s
Oct 14 06:11:22.721: INFO: Pod "pvc-snapshottable-data-tester-ldhd8": Phase="Running", Reason="", readiness=true. Elapsed: 12.371769496s
Oct 14 06:11:24.772: INFO: Pod "pvc-snapshottable-data-tester-ldhd8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.423108747s
STEP: Saw pod success
Oct 14 06:11:24.772: INFO: Pod "pvc-snapshottable-data-tester-ldhd8" satisfied condition "Succeeded or Failed"
Oct 14 06:11:24.874: INFO: Pod pvc-snapshottable-data-tester-ldhd8 has the following logs: 
Oct 14 06:11:24.874: INFO: Deleting pod "pvc-snapshottable-data-tester-ldhd8" in namespace "snapshotting-4368"
Oct 14 06:11:24.932: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-ldhd8" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Oct 14 06:12:03.188: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-b6f7c24027-45100.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-4368 exec restored-pvc-tester-bck85 --namespace=snapshotting-4368 -- cat /mnt/test/data'
... skipping 33 lines ...
Oct 14 06:12:43.916: INFO: At 2021-10-14 06:09:26 +0000 UTC - event for pvc-snapshottable-tester-wrjcx: {default-scheduler } Scheduled: Successfully assigned snapshotting-4368/pvc-snapshottable-tester-wrjcx to ip-172-20-44-65.us-west-1.compute.internal
Oct 14 06:12:43.916: INFO: At 2021-10-14 06:09:28 +0000 UTC - event for pvc-snapshottable-tester-wrjcx: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-067eede7-da1b-447c-a54f-8748d172ca42" 
Oct 14 06:12:43.916: INFO: At 2021-10-14 06:09:33 +0000 UTC - event for pvc-snapshottable-tester-wrjcx: {kubelet ip-172-20-44-65.us-west-1.compute.internal} Pulling: Pulling image "k8s.gcr.io/e2e-test-images/busybox:1.29-1"
Oct 14 06:12:43.916: INFO: At 2021-10-14 06:09:35 +0000 UTC - event for pvc-snapshottable-tester-wrjcx: {kubelet ip-172-20-44-65.us-west-1.compute.internal} Created: Created container volume-tester
Oct 14 06:12:43.916: INFO: At 2021-10-14 06:09:35 +0000 UTC - event for pvc-snapshottable-tester-wrjcx: {kubelet ip-172-20-44-65.us-west-1.compute.internal} Pulled: Successfully pulled image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" in 1.16332408s
Oct 14 06:12:43.916: INFO: At 2021-10-14 06:09:35 +0000 UTC - event for pvc-snapshottable-tester-wrjcx: {kubelet ip-172-20-44-65.us-west-1.compute.internal} Started: Started container volume-tester
Oct 14 06:12:43.916: INFO: At 2021-10-14 06:09:36 +0000 UTC - event for pvc-snapshottable-tester-wrjcx: {kubelet ip-172-20-44-65.us-west-1.compute.internal} FailedMount: MountVolume.SetUp failed for volume "kube-api-access-tq9lx" : object "snapshotting-4368"/"kube-root-ca.crt" not registered
Oct 14 06:12:43.916: INFO: At 2021-10-14 06:09:37 +0000 UTC - event for snapshot-wr8jj: {snapshot-controller } CreatingSnapshot: Waiting for a snapshot snapshotting-4368/snapshot-wr8jj to be created by the CSI driver.
Oct 14 06:12:43.916: INFO: At 2021-10-14 06:09:38 +0000 UTC - event for snapshot-wr8jj: {snapshot-controller } SnapshotCreated: Snapshot snapshotting-4368/snapshot-wr8jj was successfully created by the CSI driver.
Oct 14 06:12:43.916: INFO: At 2021-10-14 06:11:08 +0000 UTC - event for snapshot-wr8jj: {snapshot-controller } SnapshotReady: Snapshot snapshotting-4368/snapshot-wr8jj is ready to use.
Oct 14 06:12:43.916: INFO: At 2021-10-14 06:11:10 +0000 UTC - event for pvc-snapshottable-data-tester-ldhd8: {default-scheduler } Scheduled: Successfully assigned snapshotting-4368/pvc-snapshottable-data-tester-ldhd8 to ip-172-20-37-170.us-west-1.compute.internal
Oct 14 06:12:43.916: INFO: At 2021-10-14 06:11:14 +0000 UTC - event for pvc-snapshottable-data-tester-ldhd8: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-067eede7-da1b-447c-a54f-8748d172ca42" 
Oct 14 06:12:43.916: INFO: At 2021-10-14 06:11:20 +0000 UTC - event for pvc-snapshottable-data-tester-ldhd8: {kubelet ip-172-20-37-170.us-west-1.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" already present on machine
Oct 14 06:12:43.916: INFO: At 2021-10-14 06:11:21 +0000 UTC - event for pvc-snapshottable-data-tester-ldhd8: {kubelet ip-172-20-37-170.us-west-1.compute.internal} Started: Started container volume-tester
Oct 14 06:12:43.916: INFO: At 2021-10-14 06:11:21 +0000 UTC - event for pvc-snapshottable-data-tester-ldhd8: {kubelet ip-172-20-37-170.us-west-1.compute.internal} Created: Created container volume-tester
Oct 14 06:12:43.916: INFO: At 2021-10-14 06:11:23 +0000 UTC - event for pvc-snapshottable-data-tester-ldhd8: {kubelet ip-172-20-37-170.us-west-1.compute.internal} FailedMount: MountVolume.SetUp failed for volume "kube-api-access-9lgbs" : object "snapshotting-4368"/"kube-root-ca.crt" not registered
Oct 14 06:12:43.916: INFO: At 2021-10-14 06:11:25 +0000 UTC - event for pvc-v2dc9: {ebs.csi.aws.com_ebs-csi-controller-54dc46fc7b-s2rfq_c03efed4-cfaa-47c8-8c50-1ef582fbfe37 } Provisioning: External provisioner is provisioning volume for claim "snapshotting-4368/pvc-v2dc9"
Oct 14 06:12:43.916: INFO: At 2021-10-14 06:11:25 +0000 UTC - event for pvc-v2dc9: {persistentvolume-controller } ExternalProvisioning: waiting for a volume to be created, either by external provisioner "ebs.csi.aws.com" or manually created by system administrator
Oct 14 06:12:43.916: INFO: At 2021-10-14 06:11:25 +0000 UTC - event for pvc-v2dc9: {persistentvolume-controller } WaitForFirstConsumer: waiting for first consumer to be created before binding
Oct 14 06:12:43.916: INFO: At 2021-10-14 06:11:28 +0000 UTC - event for pvc-v2dc9: {ebs.csi.aws.com_ebs-csi-controller-54dc46fc7b-s2rfq_c03efed4-cfaa-47c8-8c50-1ef582fbfe37 } ProvisioningSucceeded: Successfully provisioned volume pvc-000b7c39-c823-42d8-8b58-7508ef868352
Oct 14 06:12:43.916: INFO: At 2021-10-14 06:11:29 +0000 UTC - event for restored-pvc-tester-bck85: {default-scheduler } Scheduled: Successfully assigned snapshotting-4368/restored-pvc-tester-bck85 to ip-172-20-47-110.us-west-1.compute.internal
Oct 14 06:12:43.916: INFO: At 2021-10-14 06:11:47 +0000 UTC - event for restored-pvc-tester-bck85: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-000b7c39-c823-42d8-8b58-7508ef868352" 
... skipping 191 lines ...
    /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:108
      
      /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:225
        should check snapshot fields, check restore correctly works after modifying source data, check deletion [It]
        /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:243

        Unexpected error:
            <exec.CodeExitError>: {
                Err: {
                    s: "error running /usr/local/bin/kubectl --server=https://api.e2e-b6f7c24027-45100.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-4368 exec restored-pvc-tester-bck85 --namespace=snapshotting-4368 -- cat /mnt/test/data:\nCommand stdout:\n\nstderr:\ncat: can't open '/mnt/test/data': No such file or directory\ncommand terminated with exit code 1\n\nerror:\nexit status 1",
                },
                Code: 1,
            }
            error running /usr/local/bin/kubectl --server=https://api.e2e-b6f7c24027-45100.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-4368 exec restored-pvc-tester-bck85 --namespace=snapshotting-4368 -- cat /mnt/test/data:
            Command stdout:
            
            stderr:
            cat: can't open '/mnt/test/data': No such file or directory
            command terminated with exit code 1
            
            error:
            exit status 1
        occurred

        /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:602
------------------------------
[BeforeEach] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral
... skipping 255 lines ...
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 14 06:12:52.508: 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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Oct 14 06:12:52.809: INFO: found topology map[topology.kubernetes.io/zone:us-west-1a]
Oct 14 06:12:52.809: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 14 06:12:52.809: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.SekB7YIla/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.SekB7YIla/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (immediate binding)] topology
    /tmp/kops.SekB7YIla/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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 25 lines ...
Oct 14 06:12:28.219: INFO: PersistentVolumeClaim pvc-dxf42 found but phase is Pending instead of Bound.
Oct 14 06:12:30.272: INFO: PersistentVolumeClaim pvc-dxf42 found and phase=Bound (16.473805697s)
Oct 14 06:12:30.272: INFO: Waiting up to 3m0s for PersistentVolume aws-sdmm9 to have phase Bound
Oct 14 06:12:30.324: INFO: PersistentVolume aws-sdmm9 found and phase=Bound (52.398294ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-zr2b
STEP: Creating a pod to test exec-volume-test
Oct 14 06:12:30.493: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-zr2b" in namespace "volume-3390" to be "Succeeded or Failed"
Oct 14 06:12:30.554: INFO: Pod "exec-volume-test-preprovisionedpv-zr2b": Phase="Pending", Reason="", readiness=false. Elapsed: 61.525862ms
Oct 14 06:12:32.609: INFO: Pod "exec-volume-test-preprovisionedpv-zr2b": Phase="Pending", Reason="", readiness=false. Elapsed: 2.115887352s
Oct 14 06:12:34.660: INFO: Pod "exec-volume-test-preprovisionedpv-zr2b": Phase="Pending", Reason="", readiness=false. Elapsed: 4.167349799s
Oct 14 06:12:36.712: INFO: Pod "exec-volume-test-preprovisionedpv-zr2b": Phase="Pending", Reason="", readiness=false. Elapsed: 6.218977085s
Oct 14 06:12:38.764: INFO: Pod "exec-volume-test-preprovisionedpv-zr2b": Phase="Pending", Reason="", readiness=false. Elapsed: 8.271626518s
Oct 14 06:12:40.817: INFO: Pod "exec-volume-test-preprovisionedpv-zr2b": Phase="Pending", Reason="", readiness=false. Elapsed: 10.32395512s
Oct 14 06:12:42.873: INFO: Pod "exec-volume-test-preprovisionedpv-zr2b": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.379836555s
STEP: Saw pod success
Oct 14 06:12:42.873: INFO: Pod "exec-volume-test-preprovisionedpv-zr2b" satisfied condition "Succeeded or Failed"
Oct 14 06:12:42.924: INFO: Trying to get logs from node ip-172-20-57-80.us-west-1.compute.internal pod exec-volume-test-preprovisionedpv-zr2b container exec-container-preprovisionedpv-zr2b: <nil>
STEP: delete the pod
Oct 14 06:12:43.037: INFO: Waiting for pod exec-volume-test-preprovisionedpv-zr2b to disappear
Oct 14 06:12:43.089: INFO: Pod exec-volume-test-preprovisionedpv-zr2b no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-zr2b
Oct 14 06:12:43.089: INFO: Deleting pod "exec-volume-test-preprovisionedpv-zr2b" in namespace "volume-3390"
STEP: Deleting pv and pvc
Oct 14 06:12:43.140: INFO: Deleting PersistentVolumeClaim "pvc-dxf42"
Oct 14 06:12:43.194: INFO: Deleting PersistentVolume "aws-sdmm9"
Oct 14 06:12:43.474: INFO: Couldn't delete PD "aws://us-west-1a/vol-061489020f8529125", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-061489020f8529125 is currently attached to i-019e724f48a0be6c0
	status code: 400, request id: db5ddab8-5ced-4a5f-8574-b8286c4b8bb7
Oct 14 06:12:48.794: INFO: Couldn't delete PD "aws://us-west-1a/vol-061489020f8529125", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-061489020f8529125 is currently attached to i-019e724f48a0be6c0
	status code: 400, request id: 4b752a41-18e7-46a9-8568-1d7514cfee29
Oct 14 06:12:54.152: INFO: Successfully deleted PD "aws://us-west-1a/vol-061489020f8529125".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 14 06:12:54.152: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-3390" for this suite.
... skipping 16 lines ...
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 14 06:12:54.262: 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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Oct 14 06:12:54.574: INFO: found topology map[topology.kubernetes.io/zone:us-west-1a]
Oct 14 06:12:54.574: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 14 06:12:54.574: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.SekB7YIla/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.SekB7YIla/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (delayed binding)] topology
    /tmp/kops.SekB7YIla/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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 96 lines ...
Oct 14 06:09:26.255: INFO: Creating resource for dynamic PV
Oct 14 06:09:26.255: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-7656-e2e-scwwzss
STEP: creating a claim
Oct 14 06:09:26.314: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Oct 14 06:09:26.479: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-zzzqm" in namespace "snapshotting-7656" to be "Succeeded or Failed"
Oct 14 06:09:26.543: INFO: Pod "pvc-snapshottable-tester-zzzqm": Phase="Pending", Reason="", readiness=false. Elapsed: 63.442071ms
Oct 14 06:09:28.593: INFO: Pod "pvc-snapshottable-tester-zzzqm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.113850544s
Oct 14 06:09:30.656: INFO: Pod "pvc-snapshottable-tester-zzzqm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.176469919s
Oct 14 06:09:32.707: INFO: Pod "pvc-snapshottable-tester-zzzqm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.227387959s
Oct 14 06:09:34.759: INFO: Pod "pvc-snapshottable-tester-zzzqm": Phase="Pending", Reason="", readiness=false. Elapsed: 8.279536824s
Oct 14 06:09:36.810: INFO: Pod "pvc-snapshottable-tester-zzzqm": Phase="Pending", Reason="", readiness=false. Elapsed: 10.330848008s
Oct 14 06:09:38.860: INFO: Pod "pvc-snapshottable-tester-zzzqm": Phase="Pending", Reason="", readiness=false. Elapsed: 12.380348288s
Oct 14 06:09:40.911: INFO: Pod "pvc-snapshottable-tester-zzzqm": Phase="Pending", Reason="", readiness=false. Elapsed: 14.431213147s
Oct 14 06:09:42.961: INFO: Pod "pvc-snapshottable-tester-zzzqm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.481504529s
STEP: Saw pod success
Oct 14 06:09:42.961: INFO: Pod "pvc-snapshottable-tester-zzzqm" satisfied condition "Succeeded or Failed"
Oct 14 06:09:43.072: INFO: Pod pvc-snapshottable-tester-zzzqm has the following logs: 
Oct 14 06:09:43.073: INFO: Deleting pod "pvc-snapshottable-tester-zzzqm" in namespace "snapshotting-7656"
Oct 14 06:09:43.135: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-zzzqm" to be fully deleted
Oct 14 06:09:43.185: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.com5s42p] to have phase Bound
Oct 14 06:09:43.238: INFO: PersistentVolumeClaim ebs.csi.aws.com5s42p found and phase=Bound (53.788574ms)
STEP: [init] checking the claim
... skipping 52 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:243
STEP: checking the snapshot
STEP: checking the SnapshotContent
STEP: Modifying source data test
STEP: modifying the data in the source PVC
Oct 14 06:11:10.036: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-xlk7v" in namespace "snapshotting-7656" to be "Succeeded or Failed"
Oct 14 06:11:10.088: INFO: Pod "pvc-snapshottable-data-tester-xlk7v": Phase="Pending", Reason="", readiness=false. Elapsed: 51.942855ms
Oct 14 06:11:12.141: INFO: Pod "pvc-snapshottable-data-tester-xlk7v": Phase="Pending", Reason="", readiness=false. Elapsed: 2.105371406s
Oct 14 06:11:14.194: INFO: Pod "pvc-snapshottable-data-tester-xlk7v": Phase="Pending", Reason="", readiness=false. Elapsed: 4.1580903s
Oct 14 06:11:16.246: INFO: Pod "pvc-snapshottable-data-tester-xlk7v": Phase="Pending", Reason="", readiness=false. Elapsed: 6.210235377s
Oct 14 06:11:18.299: INFO: Pod "pvc-snapshottable-data-tester-xlk7v": Phase="Pending", Reason="", readiness=false. Elapsed: 8.262648949s
Oct 14 06:11:20.351: INFO: Pod "pvc-snapshottable-data-tester-xlk7v": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.314696745s
STEP: Saw pod success
Oct 14 06:11:20.351: INFO: Pod "pvc-snapshottable-data-tester-xlk7v" satisfied condition "Succeeded or Failed"
Oct 14 06:11:20.455: INFO: Pod pvc-snapshottable-data-tester-xlk7v has the following logs: 
Oct 14 06:11:20.456: INFO: Deleting pod "pvc-snapshottable-data-tester-xlk7v" in namespace "snapshotting-7656"
Oct 14 06:11:20.518: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-xlk7v" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Oct 14 06:11:44.790: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-b6f7c24027-45100.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-7656 exec restored-pvc-tester-vrzz9 --namespace=snapshotting-7656 -- cat /mnt/test/data'
... skipping 32 lines ...
Oct 14 06:12:09.892: INFO: volumesnapshotcontents snapcontent-00e29c76-0e19-4082-9d69-77e13658a04d has been found and is not deleted
Oct 14 06:12:10.980: INFO: volumesnapshotcontents snapcontent-00e29c76-0e19-4082-9d69-77e13658a04d has been found and is not deleted
Oct 14 06:12:12.033: INFO: volumesnapshotcontents snapcontent-00e29c76-0e19-4082-9d69-77e13658a04d has been found and is not deleted
Oct 14 06:12:13.114: INFO: volumesnapshotcontents snapcontent-00e29c76-0e19-4082-9d69-77e13658a04d has been found and is not deleted
Oct 14 06:12:14.167: INFO: volumesnapshotcontents snapcontent-00e29c76-0e19-4082-9d69-77e13658a04d has been found and is not deleted
Oct 14 06:12:15.219: INFO: volumesnapshotcontents snapcontent-00e29c76-0e19-4082-9d69-77e13658a04d has been found and is not deleted
Oct 14 06:12:16.219: INFO: WaitUntil failed after reaching the timeout 30s
[AfterEach] volume snapshot controller
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:221
Oct 14 06:12:16.273: INFO: Pod restored-pvc-tester-vrzz9 has the following logs: 
Oct 14 06:12:16.273: INFO: Deleting pod "restored-pvc-tester-vrzz9" in namespace "snapshotting-7656"
Oct 14 06:12:16.326: INFO: Wait up to 5m0s for pod "restored-pvc-tester-vrzz9" to be fully deleted
Oct 14 06:12:48.429: INFO: deleting claim "snapshotting-7656"/"pvc-dzkmf"
... skipping 363 lines ...
Oct 14 06:12:25.554: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Oct 14 06:12:26.086: INFO: Successfully created a new PD: "aws://us-west-1a/vol-099ae483a23904e9d".
Oct 14 06:12:26.086: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-2pdw
STEP: Creating a pod to test exec-volume-test
Oct 14 06:12:26.140: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-2pdw" in namespace "volume-1845" to be "Succeeded or Failed"
Oct 14 06:12:26.190: INFO: Pod "exec-volume-test-inlinevolume-2pdw": Phase="Pending", Reason="", readiness=false. Elapsed: 50.084984ms
Oct 14 06:12:28.241: INFO: Pod "exec-volume-test-inlinevolume-2pdw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.100598429s
Oct 14 06:12:30.292: INFO: Pod "exec-volume-test-inlinevolume-2pdw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.151644676s
Oct 14 06:12:32.342: INFO: Pod "exec-volume-test-inlinevolume-2pdw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.201672095s
Oct 14 06:12:34.392: INFO: Pod "exec-volume-test-inlinevolume-2pdw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.251952811s
Oct 14 06:12:36.443: INFO: Pod "exec-volume-test-inlinevolume-2pdw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.302378953s
STEP: Saw pod success
Oct 14 06:12:36.443: INFO: Pod "exec-volume-test-inlinevolume-2pdw" satisfied condition "Succeeded or Failed"
Oct 14 06:12:36.492: INFO: Trying to get logs from node ip-172-20-44-65.us-west-1.compute.internal pod exec-volume-test-inlinevolume-2pdw container exec-container-inlinevolume-2pdw: <nil>
STEP: delete the pod
Oct 14 06:12:36.605: INFO: Waiting for pod exec-volume-test-inlinevolume-2pdw to disappear
Oct 14 06:12:36.654: INFO: Pod exec-volume-test-inlinevolume-2pdw no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-2pdw
Oct 14 06:12:36.654: INFO: Deleting pod "exec-volume-test-inlinevolume-2pdw" in namespace "volume-1845"
Oct 14 06:12:36.882: INFO: Couldn't delete PD "aws://us-west-1a/vol-099ae483a23904e9d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-099ae483a23904e9d is currently attached to i-0f3386771e5823100
	status code: 400, request id: c34e2903-33c8-42da-85c6-2e851df62551
Oct 14 06:12:42.263: INFO: Couldn't delete PD "aws://us-west-1a/vol-099ae483a23904e9d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-099ae483a23904e9d is currently attached to i-0f3386771e5823100
	status code: 400, request id: f135fb54-ef0e-49b1-92eb-c940195bf277
Oct 14 06:12:47.651: INFO: Couldn't delete PD "aws://us-west-1a/vol-099ae483a23904e9d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-099ae483a23904e9d is currently attached to i-0f3386771e5823100
	status code: 400, request id: d3930d44-4bd5-4564-b394-eac3de1e64b5
Oct 14 06:12:53.240: INFO: Couldn't delete PD "aws://us-west-1a/vol-099ae483a23904e9d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-099ae483a23904e9d is currently attached to i-0f3386771e5823100
	status code: 400, request id: fe6f2bc5-0196-4248-a853-3af19a03e255
Oct 14 06:12:58.592: INFO: Couldn't delete PD "aws://us-west-1a/vol-099ae483a23904e9d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-099ae483a23904e9d is currently attached to i-0f3386771e5823100
	status code: 400, request id: 824fef96-5f98-4b72-b52b-76d62bdbeb20
Oct 14 06:13:03.975: INFO: Successfully deleted PD "aws://us-west-1a/vol-099ae483a23904e9d".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 14 06:13:03.975: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-1845" for this suite.
... skipping 334 lines ...
Oct 14 06:10:52.041: INFO: Creating resource for dynamic PV
Oct 14 06:10:52.041: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-167-e2e-scm8wxb
STEP: creating a claim
Oct 14 06:10:52.094: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Oct 14 06:10:52.266: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-zlzbw" in namespace "snapshotting-167" to be "Succeeded or Failed"
Oct 14 06:10:52.318: INFO: Pod "pvc-snapshottable-tester-zlzbw": Phase="Pending", Reason="", readiness=false. Elapsed: 51.725091ms
Oct 14 06:10:54.371: INFO: Pod "pvc-snapshottable-tester-zlzbw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.104358411s
Oct 14 06:10:56.427: INFO: Pod "pvc-snapshottable-tester-zlzbw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.160603924s
Oct 14 06:10:58.481: INFO: Pod "pvc-snapshottable-tester-zlzbw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.214731024s
Oct 14 06:11:00.536: INFO: Pod "pvc-snapshottable-tester-zlzbw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.269495676s
Oct 14 06:11:02.588: INFO: Pod "pvc-snapshottable-tester-zlzbw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.321808473s
STEP: Saw pod success
Oct 14 06:11:02.588: INFO: Pod "pvc-snapshottable-tester-zlzbw" satisfied condition "Succeeded or Failed"
Oct 14 06:11:02.696: INFO: Pod pvc-snapshottable-tester-zlzbw has the following logs: 
Oct 14 06:11:02.696: INFO: Deleting pod "pvc-snapshottable-tester-zlzbw" in namespace "snapshotting-167"
Oct 14 06:11:02.756: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-zlzbw" to be fully deleted
Oct 14 06:11:02.826: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.com7dlq8] to have phase Bound
Oct 14 06:11:02.884: INFO: PersistentVolumeClaim ebs.csi.aws.com7dlq8 found and phase=Bound (57.924287ms)
STEP: [init] checking the claim
... skipping 61 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:243
STEP: checking the snapshot
STEP: checking the SnapshotContent
STEP: Modifying source data test
STEP: modifying the data in the source PVC
Oct 14 06:12:11.835: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-tzmhk" in namespace "snapshotting-167" to be "Succeeded or Failed"
Oct 14 06:12:11.888: INFO: Pod "pvc-snapshottable-data-tester-tzmhk": Phase="Pending", Reason="", readiness=false. Elapsed: 53.078185ms
Oct 14 06:12:13.941: INFO: Pod "pvc-snapshottable-data-tester-tzmhk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.106236152s
Oct 14 06:12:15.995: INFO: Pod "pvc-snapshottable-data-tester-tzmhk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.159726269s
Oct 14 06:12:18.047: INFO: Pod "pvc-snapshottable-data-tester-tzmhk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.211690456s
Oct 14 06:12:20.100: INFO: Pod "pvc-snapshottable-data-tester-tzmhk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.264808948s
Oct 14 06:12:22.152: INFO: Pod "pvc-snapshottable-data-tester-tzmhk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.317396038s
STEP: Saw pod success
Oct 14 06:12:22.152: INFO: Pod "pvc-snapshottable-data-tester-tzmhk" satisfied condition "Succeeded or Failed"
Oct 14 06:12:22.258: INFO: Pod pvc-snapshottable-data-tester-tzmhk has the following logs: 
Oct 14 06:12:22.258: INFO: Deleting pod "pvc-snapshottable-data-tester-tzmhk" in namespace "snapshotting-167"
Oct 14 06:12:22.315: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-tzmhk" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Oct 14 06:12:32.581: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-b6f7c24027-45100.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-167 exec restored-pvc-tester-mvwmx --namespace=snapshotting-167 -- cat /mnt/test/data'
... skipping 133 lines ...
Oct 14 06:13:17.369: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 93 lines ...
Oct 14 06:12:58.428: INFO: Pod aws-client still exists
Oct 14 06:13:00.429: INFO: Waiting for pod aws-client to disappear
Oct 14 06:13:00.481: INFO: Pod aws-client still exists
Oct 14 06:13:02.429: INFO: Waiting for pod aws-client to disappear
Oct 14 06:13:02.480: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Oct 14 06:13:02.860: INFO: Couldn't delete PD "aws://us-west-1a/vol-002d580ce309f8d2d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-002d580ce309f8d2d is currently attached to i-0f3386771e5823100
	status code: 400, request id: 4324965e-49be-454f-b19d-b2ee99a07b0a
Oct 14 06:13:08.181: INFO: Couldn't delete PD "aws://us-west-1a/vol-002d580ce309f8d2d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-002d580ce309f8d2d is currently attached to i-0f3386771e5823100
	status code: 400, request id: 0018eced-4c1e-4088-b4d7-c6018fbcc879
Oct 14 06:13:13.566: INFO: Couldn't delete PD "aws://us-west-1a/vol-002d580ce309f8d2d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-002d580ce309f8d2d is currently attached to i-0f3386771e5823100
	status code: 400, request id: 56b85e74-ef8c-4470-bc53-70e67e4d52af
Oct 14 06:13:18.943: INFO: Successfully deleted PD "aws://us-west-1a/vol-002d580ce309f8d2d".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 14 06:13:18.943: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-1822" for this suite.
... skipping 195 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.SekB7YIla/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.SekB7YIla/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.SekB7YIla/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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 70 lines ...
Oct 14 06:12:39.318: INFO: Creating resource for dynamic PV
Oct 14 06:12:39.318: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9695zs9f8
STEP: creating a claim
Oct 14 06:12:39.370: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-9695
Oct 14 06:12:39.531: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-9695" in namespace "provisioning-9695" to be "Succeeded or Failed"
Oct 14 06:12:39.582: INFO: Pod "volume-prep-provisioning-9695": Phase="Pending", Reason="", readiness=false. Elapsed: 51.787762ms
Oct 14 06:12:41.635: INFO: Pod "volume-prep-provisioning-9695": Phase="Pending", Reason="", readiness=false. Elapsed: 2.104337308s
Oct 14 06:12:43.688: INFO: Pod "volume-prep-provisioning-9695": Phase="Pending", Reason="", readiness=false. Elapsed: 4.157618613s
Oct 14 06:12:45.741: INFO: Pod "volume-prep-provisioning-9695": Phase="Pending", Reason="", readiness=false. Elapsed: 6.210861369s
Oct 14 06:12:47.793: INFO: Pod "volume-prep-provisioning-9695": Phase="Pending", Reason="", readiness=false. Elapsed: 8.262852364s
Oct 14 06:12:49.846: INFO: Pod "volume-prep-provisioning-9695": Phase="Pending", Reason="", readiness=false. Elapsed: 10.315522655s
Oct 14 06:12:51.899: INFO: Pod "volume-prep-provisioning-9695": Phase="Pending", Reason="", readiness=false. Elapsed: 12.368059861s
Oct 14 06:12:53.951: INFO: Pod "volume-prep-provisioning-9695": Phase="Pending", Reason="", readiness=false. Elapsed: 14.420078512s
Oct 14 06:12:56.004: INFO: Pod "volume-prep-provisioning-9695": Phase="Pending", Reason="", readiness=false. Elapsed: 16.473287887s
Oct 14 06:12:58.057: INFO: Pod "volume-prep-provisioning-9695": Phase="Pending", Reason="", readiness=false. Elapsed: 18.526090828s
Oct 14 06:13:00.115: INFO: Pod "volume-prep-provisioning-9695": Phase="Pending", Reason="", readiness=false. Elapsed: 20.584203928s
Oct 14 06:13:02.171: INFO: Pod "volume-prep-provisioning-9695": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.640757625s
STEP: Saw pod success
Oct 14 06:13:02.171: INFO: Pod "volume-prep-provisioning-9695" satisfied condition "Succeeded or Failed"
Oct 14 06:13:02.171: INFO: Deleting pod "volume-prep-provisioning-9695" in namespace "provisioning-9695"
Oct 14 06:13:02.233: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-9695" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-4lzk
STEP: Checking for subpath error in container status
Oct 14 06:13:08.451: INFO: Deleting pod "pod-subpath-test-dynamicpv-4lzk" in namespace "provisioning-9695"
Oct 14 06:13:08.511: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-4lzk" to be fully deleted
STEP: Deleting pod
Oct 14 06:13:08.562: INFO: Deleting pod "pod-subpath-test-dynamicpv-4lzk" in namespace "provisioning-9695"
STEP: Deleting pvc
Oct 14 06:13:08.716: INFO: Deleting PersistentVolumeClaim "awsmzdqh"
... skipping 81 lines ...
Oct 14 06:13:18.462: INFO: Waiting for pod aws-client to disappear
Oct 14 06:13:18.512: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Oct 14 06:13:18.512: INFO: Deleting PersistentVolumeClaim "pvc-lfvkh"
Oct 14 06:13:18.563: INFO: Deleting PersistentVolume "aws-8l6qz"
Oct 14 06:13:18.775: INFO: Couldn't delete PD "aws://us-west-1a/vol-0a78c35bdb86afbd8", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a78c35bdb86afbd8 is currently attached to i-0f33202ea8f247785
	status code: 400, request id: 50b4bd3a-7ba2-42b1-a117-2c86d422fd7b
Oct 14 06:13:24.094: INFO: Couldn't delete PD "aws://us-west-1a/vol-0a78c35bdb86afbd8", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a78c35bdb86afbd8 is currently attached to i-0f33202ea8f247785
	status code: 400, request id: 3b70dd32-84c0-432f-bfb0-70161723921d
Oct 14 06:13:29.452: INFO: Successfully deleted PD "aws://us-west-1a/vol-0a78c35bdb86afbd8".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 14 06:13:29.452: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-7300" for this suite.
... skipping 83 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.SekB7YIla/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.SekB7YIla/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.SekB7YIla/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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 135 lines ...
Oct 14 06:12:57.882: INFO: PersistentVolumeClaim pvc-fr77r found but phase is Pending instead of Bound.
Oct 14 06:12:59.934: INFO: PersistentVolumeClaim pvc-fr77r found and phase=Bound (4.156248544s)
Oct 14 06:12:59.934: INFO: Waiting up to 3m0s for PersistentVolume aws-bpqzj to have phase Bound
Oct 14 06:12:59.992: INFO: PersistentVolume aws-bpqzj found and phase=Bound (57.929451ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-5rxj
STEP: Creating a pod to test exec-volume-test
Oct 14 06:13:00.151: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-5rxj" in namespace "volume-232" to be "Succeeded or Failed"
Oct 14 06:13:00.204: INFO: Pod "exec-volume-test-preprovisionedpv-5rxj": Phase="Pending", Reason="", readiness=false. Elapsed: 52.494015ms
Oct 14 06:13:02.257: INFO: Pod "exec-volume-test-preprovisionedpv-5rxj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.105431269s
Oct 14 06:13:04.310: INFO: Pod "exec-volume-test-preprovisionedpv-5rxj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.158231921s
Oct 14 06:13:06.362: INFO: Pod "exec-volume-test-preprovisionedpv-5rxj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.210326641s
Oct 14 06:13:08.415: INFO: Pod "exec-volume-test-preprovisionedpv-5rxj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.263575787s
Oct 14 06:13:10.467: INFO: Pod "exec-volume-test-preprovisionedpv-5rxj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.315319449s
STEP: Saw pod success
Oct 14 06:13:10.467: INFO: Pod "exec-volume-test-preprovisionedpv-5rxj" satisfied condition "Succeeded or Failed"
Oct 14 06:13:10.524: INFO: Trying to get logs from node ip-172-20-44-65.us-west-1.compute.internal pod exec-volume-test-preprovisionedpv-5rxj container exec-container-preprovisionedpv-5rxj: <nil>
STEP: delete the pod
Oct 14 06:13:10.635: INFO: Waiting for pod exec-volume-test-preprovisionedpv-5rxj to disappear
Oct 14 06:13:10.686: INFO: Pod exec-volume-test-preprovisionedpv-5rxj no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-5rxj
Oct 14 06:13:10.686: INFO: Deleting pod "exec-volume-test-preprovisionedpv-5rxj" in namespace "volume-232"
STEP: Deleting pv and pvc
Oct 14 06:13:10.738: INFO: Deleting PersistentVolumeClaim "pvc-fr77r"
Oct 14 06:13:10.792: INFO: Deleting PersistentVolume "aws-bpqzj"
Oct 14 06:13:11.013: INFO: Couldn't delete PD "aws://us-west-1a/vol-0a1355a5ef53a084b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a1355a5ef53a084b is currently attached to i-0f3386771e5823100
	status code: 400, request id: 18788213-9e57-40e1-978b-b11c630c3bbb
Oct 14 06:13:16.348: INFO: Couldn't delete PD "aws://us-west-1a/vol-0a1355a5ef53a084b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a1355a5ef53a084b is currently attached to i-0f3386771e5823100
	status code: 400, request id: be6a3a4a-86f5-4cd6-88c6-63fb075554ea
Oct 14 06:13:21.694: INFO: Couldn't delete PD "aws://us-west-1a/vol-0a1355a5ef53a084b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a1355a5ef53a084b is currently attached to i-0f3386771e5823100
	status code: 400, request id: e54c8932-cb5e-4327-a68d-004db2ee45d6
Oct 14 06:13:27.027: INFO: Couldn't delete PD "aws://us-west-1a/vol-0a1355a5ef53a084b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a1355a5ef53a084b is currently attached to i-0f3386771e5823100
	status code: 400, request id: 802a0f2c-d241-4d1f-b5ea-54d2bff39b31
Oct 14 06:13:32.360: INFO: Successfully deleted PD "aws://us-west-1a/vol-0a1355a5ef53a084b".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 14 06:13:32.361: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-232" for this suite.
... skipping 383 lines ...
Oct 14 06:13:24.150: INFO: Waiting for pod aws-client to disappear
Oct 14 06:13:24.199: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Oct 14 06:13:24.199: INFO: Deleting PersistentVolumeClaim "pvc-9gbxc"
Oct 14 06:13:24.263: INFO: Deleting PersistentVolume "aws-sp2gf"
Oct 14 06:13:24.474: INFO: Couldn't delete PD "aws://us-west-1a/vol-0bb6e0b07c24dbf7b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0bb6e0b07c24dbf7b is currently attached to i-019e724f48a0be6c0
	status code: 400, request id: 2eb350a4-84f7-40de-bab8-985b9b65fff2
Oct 14 06:13:29.811: INFO: Couldn't delete PD "aws://us-west-1a/vol-0bb6e0b07c24dbf7b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0bb6e0b07c24dbf7b is currently attached to i-019e724f48a0be6c0
	status code: 400, request id: 4bc57467-2775-4a66-93a1-812aa266e114
Oct 14 06:13:35.193: INFO: Successfully deleted PD "aws://us-west-1a/vol-0bb6e0b07c24dbf7b".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 14 06:13:35.193: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-842" for this suite.
... skipping 23 lines ...
Oct 14 06:12:46.721: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-1656-e2e-sczhtf6
STEP: creating a claim
Oct 14 06:12:46.772: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-227s
STEP: Creating a pod to test exec-volume-test
Oct 14 06:12:46.927: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-227s" in namespace "volume-1656" to be "Succeeded or Failed"
Oct 14 06:12:46.977: INFO: Pod "exec-volume-test-dynamicpv-227s": Phase="Pending", Reason="", readiness=false. Elapsed: 50.009067ms
Oct 14 06:12:49.031: INFO: Pod "exec-volume-test-dynamicpv-227s": Phase="Pending", Reason="", readiness=false. Elapsed: 2.104037854s
Oct 14 06:12:51.083: INFO: Pod "exec-volume-test-dynamicpv-227s": Phase="Pending", Reason="", readiness=false. Elapsed: 4.156237685s
Oct 14 06:12:53.134: INFO: Pod "exec-volume-test-dynamicpv-227s": Phase="Pending", Reason="", readiness=false. Elapsed: 6.207267066s
Oct 14 06:12:55.185: INFO: Pod "exec-volume-test-dynamicpv-227s": Phase="Pending", Reason="", readiness=false. Elapsed: 8.257764532s
Oct 14 06:12:57.236: INFO: Pod "exec-volume-test-dynamicpv-227s": Phase="Pending", Reason="", readiness=false. Elapsed: 10.308827885s
... skipping 9 lines ...
Oct 14 06:13:17.741: INFO: Pod "exec-volume-test-dynamicpv-227s": Phase="Pending", Reason="", readiness=false. Elapsed: 30.813548653s
Oct 14 06:13:19.790: INFO: Pod "exec-volume-test-dynamicpv-227s": Phase="Pending", Reason="", readiness=false. Elapsed: 32.863386381s
Oct 14 06:13:21.840: INFO: Pod "exec-volume-test-dynamicpv-227s": Phase="Pending", Reason="", readiness=false. Elapsed: 34.913326852s
Oct 14 06:13:23.890: INFO: Pod "exec-volume-test-dynamicpv-227s": Phase="Pending", Reason="", readiness=false. Elapsed: 36.963090393s
Oct 14 06:13:25.945: INFO: Pod "exec-volume-test-dynamicpv-227s": Phase="Succeeded", Reason="", readiness=false. Elapsed: 39.018043484s
STEP: Saw pod success
Oct 14 06:13:25.945: INFO: Pod "exec-volume-test-dynamicpv-227s" satisfied condition "Succeeded or Failed"
Oct 14 06:13:25.995: INFO: Trying to get logs from node ip-172-20-44-65.us-west-1.compute.internal pod exec-volume-test-dynamicpv-227s container exec-container-dynamicpv-227s: <nil>
STEP: delete the pod
Oct 14 06:13:26.100: INFO: Waiting for pod exec-volume-test-dynamicpv-227s to disappear
Oct 14 06:13:26.150: INFO: Pod exec-volume-test-dynamicpv-227s no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-227s
Oct 14 06:13:26.150: INFO: Deleting pod "exec-volume-test-dynamicpv-227s" in namespace "volume-1656"
... skipping 96 lines ...
Oct 14 06:13:02.023: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-18008dlgl
STEP: creating a claim
Oct 14 06:13:02.074: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-4q7c
STEP: Creating a pod to test exec-volume-test
Oct 14 06:13:02.229: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-4q7c" in namespace "volume-1800" to be "Succeeded or Failed"
Oct 14 06:13:02.281: INFO: Pod "exec-volume-test-dynamicpv-4q7c": Phase="Pending", Reason="", readiness=false. Elapsed: 52.010864ms
Oct 14 06:13:04.332: INFO: Pod "exec-volume-test-dynamicpv-4q7c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.103060962s
Oct 14 06:13:06.384: INFO: Pod "exec-volume-test-dynamicpv-4q7c": Phase="Pending", Reason="", readiness=false. Elapsed: 4.155174011s
Oct 14 06:13:08.436: INFO: Pod "exec-volume-test-dynamicpv-4q7c": Phase="Pending", Reason="", readiness=false. Elapsed: 6.206498281s
Oct 14 06:13:10.486: INFO: Pod "exec-volume-test-dynamicpv-4q7c": Phase="Pending", Reason="", readiness=false. Elapsed: 8.256583117s
Oct 14 06:13:12.537: INFO: Pod "exec-volume-test-dynamicpv-4q7c": Phase="Pending", Reason="", readiness=false. Elapsed: 10.307748492s
Oct 14 06:13:14.587: INFO: Pod "exec-volume-test-dynamicpv-4q7c": Phase="Pending", Reason="", readiness=false. Elapsed: 12.357858042s
Oct 14 06:13:16.637: INFO: Pod "exec-volume-test-dynamicpv-4q7c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.408083804s
STEP: Saw pod success
Oct 14 06:13:16.637: INFO: Pod "exec-volume-test-dynamicpv-4q7c" satisfied condition "Succeeded or Failed"
Oct 14 06:13:16.687: INFO: Trying to get logs from node ip-172-20-44-65.us-west-1.compute.internal pod exec-volume-test-dynamicpv-4q7c container exec-container-dynamicpv-4q7c: <nil>
STEP: delete the pod
Oct 14 06:13:16.792: INFO: Waiting for pod exec-volume-test-dynamicpv-4q7c to disappear
Oct 14 06:13:16.843: INFO: Pod exec-volume-test-dynamicpv-4q7c no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-4q7c
Oct 14 06:13:16.843: INFO: Deleting pod "exec-volume-test-dynamicpv-4q7c" in namespace "volume-1800"
... skipping 520 lines ...
Oct 14 06:12:57.822: INFO: Creating resource for dynamic PV
Oct 14 06:12:57.822: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5834-e2e-scwjqvx
STEP: creating a claim
Oct 14 06:12:57.874: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-5834
Oct 14 06:12:58.043: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-5834" in namespace "provisioning-5834" to be "Succeeded or Failed"
Oct 14 06:12:58.095: INFO: Pod "volume-prep-provisioning-5834": Phase="Pending", Reason="", readiness=false. Elapsed: 52.063389ms
Oct 14 06:13:00.145: INFO: Pod "volume-prep-provisioning-5834": Phase="Pending", Reason="", readiness=false. Elapsed: 2.102914487s
Oct 14 06:13:02.200: INFO: Pod "volume-prep-provisioning-5834": Phase="Pending", Reason="", readiness=false. Elapsed: 4.157640326s
Oct 14 06:13:04.250: INFO: Pod "volume-prep-provisioning-5834": Phase="Pending", Reason="", readiness=false. Elapsed: 6.207396879s
Oct 14 06:13:06.303: INFO: Pod "volume-prep-provisioning-5834": Phase="Pending", Reason="", readiness=false. Elapsed: 8.260373705s
Oct 14 06:13:08.354: INFO: Pod "volume-prep-provisioning-5834": Phase="Pending", Reason="", readiness=false. Elapsed: 10.31113974s
Oct 14 06:13:10.404: INFO: Pod "volume-prep-provisioning-5834": Phase="Pending", Reason="", readiness=false. Elapsed: 12.361065865s
Oct 14 06:13:12.453: INFO: Pod "volume-prep-provisioning-5834": Phase="Pending", Reason="", readiness=false. Elapsed: 14.410772699s
Oct 14 06:13:14.505: INFO: Pod "volume-prep-provisioning-5834": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.46291474s
STEP: Saw pod success
Oct 14 06:13:14.506: INFO: Pod "volume-prep-provisioning-5834" satisfied condition "Succeeded or Failed"
Oct 14 06:13:14.506: INFO: Deleting pod "volume-prep-provisioning-5834" in namespace "provisioning-5834"
Oct 14 06:13:14.563: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-5834" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-z247
STEP: Checking for subpath error in container status
Oct 14 06:13:18.766: INFO: Deleting pod "pod-subpath-test-dynamicpv-z247" in namespace "provisioning-5834"
Oct 14 06:13:18.825: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-z247" to be fully deleted
STEP: Deleting pod
Oct 14 06:13:18.874: INFO: Deleting pod "pod-subpath-test-dynamicpv-z247" in namespace "provisioning-5834"
STEP: Deleting pvc
Oct 14 06:13:19.024: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comcrzc6"
... skipping 53 lines ...
Oct 14 06:13:34.647: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Oct 14 06:13:35.209: INFO: Successfully created a new PD: "aws://us-west-1a/vol-010af10f8b375c35f".
Oct 14 06:13:35.209: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-ztkk
STEP: Creating a pod to test exec-volume-test
Oct 14 06:13:35.266: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-ztkk" in namespace "volume-6949" to be "Succeeded or Failed"
Oct 14 06:13:35.316: INFO: Pod "exec-volume-test-inlinevolume-ztkk": Phase="Pending", Reason="", readiness=false. Elapsed: 50.752054ms
Oct 14 06:13:37.367: INFO: Pod "exec-volume-test-inlinevolume-ztkk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.101432085s
Oct 14 06:13:39.424: INFO: Pod "exec-volume-test-inlinevolume-ztkk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.158237697s
Oct 14 06:13:41.476: INFO: Pod "exec-volume-test-inlinevolume-ztkk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.210094553s
Oct 14 06:13:43.527: INFO: Pod "exec-volume-test-inlinevolume-ztkk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.261466642s
Oct 14 06:13:45.580: INFO: Pod "exec-volume-test-inlinevolume-ztkk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.313965852s
STEP: Saw pod success
Oct 14 06:13:45.580: INFO: Pod "exec-volume-test-inlinevolume-ztkk" satisfied condition "Succeeded or Failed"
Oct 14 06:13:45.630: INFO: Trying to get logs from node ip-172-20-37-170.us-west-1.compute.internal pod exec-volume-test-inlinevolume-ztkk container exec-container-inlinevolume-ztkk: <nil>
STEP: delete the pod
Oct 14 06:13:45.745: INFO: Waiting for pod exec-volume-test-inlinevolume-ztkk to disappear
Oct 14 06:13:45.796: INFO: Pod exec-volume-test-inlinevolume-ztkk no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-ztkk
Oct 14 06:13:45.796: INFO: Deleting pod "exec-volume-test-inlinevolume-ztkk" in namespace "volume-6949"
Oct 14 06:13:45.996: INFO: Couldn't delete PD "aws://us-west-1a/vol-010af10f8b375c35f", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-010af10f8b375c35f is currently attached to i-0f33202ea8f247785
	status code: 400, request id: dad8cc3a-8a92-4b81-97b5-3450937e2f42
Oct 14 06:13:51.342: INFO: Couldn't delete PD "aws://us-west-1a/vol-010af10f8b375c35f", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-010af10f8b375c35f is currently attached to i-0f33202ea8f247785
	status code: 400, request id: 4b8601e4-b29d-43a5-a7d3-52942f8d3d06
Oct 14 06:13:56.710: INFO: Successfully deleted PD "aws://us-west-1a/vol-010af10f8b375c35f".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 14 06:13:56.710: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-6949" for this suite.
... skipping 188 lines ...
Oct 14 06:13:32.798: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-7705lw92c
STEP: creating a claim
Oct 14 06:13:32.849: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Oct 14 06:13:32.951: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Oct 14 06:13:33.051: INFO: Error updating pvc awshdsht: PersistentVolumeClaim "awshdsht" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-7705lw92c",
  	... // 3 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

Oct 14 06:14:01.154: INFO: Error updating pvc awshdsht: PersistentVolumeClaim "awshdsht" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-7705lw92c",
  	... // 3 identical fields
  }

Oct 14 06:14:03.152: INFO: Error updating pvc awshdsht: PersistentVolumeClaim "awshdsht" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-7705lw92c",
  	... // 3 identical fields
  }

Oct 14 06:14:03.254: INFO: Error updating pvc awshdsht: PersistentVolumeClaim "awshdsht" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 638 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.SekB7YIla/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.SekB7YIla/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.SekB7YIla/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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 30 lines ...
Oct 14 06:13:53.681: INFO: Creating resource for dynamic PV
Oct 14 06:13:53.681: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-4144x4488
STEP: creating a claim
STEP: Expanding non-expandable pvc
Oct 14 06:13:53.843: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Oct 14 06:13:53.945: INFO: Error updating pvc aws24fkr: PersistentVolumeClaim "aws24fkr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4144x4488",
  	... // 3 identical fields
  }

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

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

Oct 14 06:14:00.048: INFO: Error updating pvc aws24fkr: PersistentVolumeClaim "aws24fkr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4144x4488",
  	... // 3 identical fields
  }

Oct 14 06:14:02.047: INFO: Error updating pvc aws24fkr: PersistentVolumeClaim "aws24fkr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4144x4488",
  	... // 3 identical fields
  }

Oct 14 06:14:04.048: INFO: Error updating pvc aws24fkr: PersistentVolumeClaim "aws24fkr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4144x4488",
  	... // 3 identical fields
  }

Oct 14 06:14:06.048: INFO: Error updating pvc aws24fkr: PersistentVolumeClaim "aws24fkr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4144x4488",
  	... // 3 identical fields
  }

Oct 14 06:14:08.048: INFO: Error updating pvc aws24fkr: PersistentVolumeClaim "aws24fkr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4144x4488",
  	... // 3 identical fields
  }

Oct 14 06:14:10.048: INFO: Error updating pvc aws24fkr: PersistentVolumeClaim "aws24fkr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4144x4488",
  	... // 3 identical fields
  }

Oct 14 06:14:12.054: INFO: Error updating pvc aws24fkr: PersistentVolumeClaim "aws24fkr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4144x4488",
  	... // 3 identical fields
  }

Oct 14 06:14:14.050: INFO: Error updating pvc aws24fkr: PersistentVolumeClaim "aws24fkr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4144x4488",
  	... // 3 identical fields
  }

Oct 14 06:14:16.048: INFO: Error updating pvc aws24fkr: PersistentVolumeClaim "aws24fkr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4144x4488",
  	... // 3 identical fields
  }

Oct 14 06:14:18.060: INFO: Error updating pvc aws24fkr: PersistentVolumeClaim "aws24fkr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4144x4488",
  	... // 3 identical fields
  }

Oct 14 06:14:20.047: INFO: Error updating pvc aws24fkr: PersistentVolumeClaim "aws24fkr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4144x4488",
  	... // 3 identical fields
  }

Oct 14 06:14:22.048: INFO: Error updating pvc aws24fkr: PersistentVolumeClaim "aws24fkr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4144x4488",
  	... // 3 identical fields
  }

Oct 14 06:14:24.055: INFO: Error updating pvc aws24fkr: PersistentVolumeClaim "aws24fkr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4144x4488",
  	... // 3 identical fields
  }

Oct 14 06:14:24.160: INFO: Error updating pvc aws24fkr: PersistentVolumeClaim "aws24fkr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 210 lines ...
Oct 14 06:13:49.248: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-39588brfg
STEP: creating a claim
Oct 14 06:13:49.299: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-p6wj
STEP: Creating a pod to test subpath
Oct 14 06:13:49.453: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-p6wj" in namespace "provisioning-3958" to be "Succeeded or Failed"
Oct 14 06:13:49.503: INFO: Pod "pod-subpath-test-dynamicpv-p6wj": Phase="Pending", Reason="", readiness=false. Elapsed: 49.83796ms
Oct 14 06:13:51.554: INFO: Pod "pod-subpath-test-dynamicpv-p6wj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.100948603s
Oct 14 06:13:53.605: INFO: Pod "pod-subpath-test-dynamicpv-p6wj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.151756121s
Oct 14 06:13:55.656: INFO: Pod "pod-subpath-test-dynamicpv-p6wj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.202693226s
Oct 14 06:13:57.708: INFO: Pod "pod-subpath-test-dynamicpv-p6wj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.25434793s
Oct 14 06:13:59.759: INFO: Pod "pod-subpath-test-dynamicpv-p6wj": Phase="Pending", Reason="", readiness=false. Elapsed: 10.305819756s
... skipping 2 lines ...
Oct 14 06:14:05.913: INFO: Pod "pod-subpath-test-dynamicpv-p6wj": Phase="Pending", Reason="", readiness=false. Elapsed: 16.459249372s
Oct 14 06:14:07.964: INFO: Pod "pod-subpath-test-dynamicpv-p6wj": Phase="Pending", Reason="", readiness=false. Elapsed: 18.510627547s
Oct 14 06:14:10.014: INFO: Pod "pod-subpath-test-dynamicpv-p6wj": Phase="Pending", Reason="", readiness=false. Elapsed: 20.560631596s
Oct 14 06:14:12.065: INFO: Pod "pod-subpath-test-dynamicpv-p6wj": Phase="Pending", Reason="", readiness=false. Elapsed: 22.611296455s
Oct 14 06:14:14.116: INFO: Pod "pod-subpath-test-dynamicpv-p6wj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.662172184s
STEP: Saw pod success
Oct 14 06:14:14.116: INFO: Pod "pod-subpath-test-dynamicpv-p6wj" satisfied condition "Succeeded or Failed"
Oct 14 06:14:14.166: INFO: Trying to get logs from node ip-172-20-37-170.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-p6wj container test-container-subpath-dynamicpv-p6wj: <nil>
STEP: delete the pod
Oct 14 06:14:14.276: INFO: Waiting for pod pod-subpath-test-dynamicpv-p6wj to disappear
Oct 14 06:14:14.325: INFO: Pod pod-subpath-test-dynamicpv-p6wj no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-p6wj
Oct 14 06:14:14.325: INFO: Deleting pod "pod-subpath-test-dynamicpv-p6wj" in namespace "provisioning-3958"
... skipping 33 lines ...

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.SekB7YIla/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.SekB7YIla/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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 72 lines ...
Oct 14 06:13:26.333: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6562-e2e-scr4hsm
STEP: creating a claim
Oct 14 06:13:26.383: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-x6xs
STEP: Creating a pod to test subpath
Oct 14 06:13:26.536: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-x6xs" in namespace "provisioning-6562" to be "Succeeded or Failed"
Oct 14 06:13:26.586: INFO: Pod "pod-subpath-test-dynamicpv-x6xs": Phase="Pending", Reason="", readiness=false. Elapsed: 49.529119ms
Oct 14 06:13:28.636: INFO: Pod "pod-subpath-test-dynamicpv-x6xs": Phase="Pending", Reason="", readiness=false. Elapsed: 2.099439543s
Oct 14 06:13:30.685: INFO: Pod "pod-subpath-test-dynamicpv-x6xs": Phase="Pending", Reason="", readiness=false. Elapsed: 4.14930079s
Oct 14 06:13:32.735: INFO: Pod "pod-subpath-test-dynamicpv-x6xs": Phase="Pending", Reason="", readiness=false. Elapsed: 6.199017358s
Oct 14 06:13:34.785: INFO: Pod "pod-subpath-test-dynamicpv-x6xs": Phase="Pending", Reason="", readiness=false. Elapsed: 8.249263807s
Oct 14 06:13:36.836: INFO: Pod "pod-subpath-test-dynamicpv-x6xs": Phase="Pending", Reason="", readiness=false. Elapsed: 10.30021339s
... skipping 10 lines ...
Oct 14 06:13:59.395: INFO: Pod "pod-subpath-test-dynamicpv-x6xs": Phase="Pending", Reason="", readiness=false. Elapsed: 32.859001455s
Oct 14 06:14:01.446: INFO: Pod "pod-subpath-test-dynamicpv-x6xs": Phase="Pending", Reason="", readiness=false. Elapsed: 34.909579158s
Oct 14 06:14:03.496: INFO: Pod "pod-subpath-test-dynamicpv-x6xs": Phase="Pending", Reason="", readiness=false. Elapsed: 36.960066991s
Oct 14 06:14:05.548: INFO: Pod "pod-subpath-test-dynamicpv-x6xs": Phase="Pending", Reason="", readiness=false. Elapsed: 39.011337987s
Oct 14 06:14:07.598: INFO: Pod "pod-subpath-test-dynamicpv-x6xs": Phase="Succeeded", Reason="", readiness=false. Elapsed: 41.061479548s
STEP: Saw pod success
Oct 14 06:14:07.598: INFO: Pod "pod-subpath-test-dynamicpv-x6xs" satisfied condition "Succeeded or Failed"
Oct 14 06:14:07.649: INFO: Trying to get logs from node ip-172-20-44-65.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-x6xs container test-container-subpath-dynamicpv-x6xs: <nil>
STEP: delete the pod
Oct 14 06:14:07.757: INFO: Waiting for pod pod-subpath-test-dynamicpv-x6xs to disappear
Oct 14 06:14:07.806: INFO: Pod pod-subpath-test-dynamicpv-x6xs no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-x6xs
Oct 14 06:14:07.806: INFO: Deleting pod "pod-subpath-test-dynamicpv-x6xs" in namespace "provisioning-6562"
... skipping 65 lines ...
STEP: Deleting pod hostexec-ip-172-20-44-65.us-west-1.compute.internal-5d8bv in namespace volumemode-382
Oct 14 06:14:20.235: INFO: Deleting pod "pod-615372c4-f222-4592-aeca-db979d8c29f8" in namespace "volumemode-382"
Oct 14 06:14:20.290: INFO: Wait up to 5m0s for pod "pod-615372c4-f222-4592-aeca-db979d8c29f8" to be fully deleted
STEP: Deleting pv and pvc
Oct 14 06:14:22.394: INFO: Deleting PersistentVolumeClaim "pvc-9bjlk"
Oct 14 06:14:22.448: INFO: Deleting PersistentVolume "aws-mgmv2"
Oct 14 06:14:22.648: INFO: Couldn't delete PD "aws://us-west-1a/vol-09d3991ff6cf7bc7e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-09d3991ff6cf7bc7e is currently attached to i-0f3386771e5823100
	status code: 400, request id: c82167c6-4512-4b2f-be17-976a3c7ae3ea
Oct 14 06:14:28.005: INFO: Couldn't delete PD "aws://us-west-1a/vol-09d3991ff6cf7bc7e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-09d3991ff6cf7bc7e is currently attached to i-0f3386771e5823100
	status code: 400, request id: 240bdf51-ad0b-4638-abf9-469cf819f45f
Oct 14 06:14:33.356: INFO: Couldn't delete PD "aws://us-west-1a/vol-09d3991ff6cf7bc7e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-09d3991ff6cf7bc7e is currently attached to i-0f3386771e5823100
	status code: 400, request id: ad5272e4-fe8b-445e-9e2b-6bbe236610d1
Oct 14 06:14:38.776: INFO: Couldn't delete PD "aws://us-west-1a/vol-09d3991ff6cf7bc7e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-09d3991ff6cf7bc7e is currently attached to i-0f3386771e5823100
	status code: 400, request id: 4254e74c-9115-4997-adbb-ddbd9307306e
Oct 14 06:14:44.132: INFO: Successfully deleted PD "aws://us-west-1a/vol-09d3991ff6cf7bc7e".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 14 06:14:44.132: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-382" for this suite.
... skipping 79 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.SekB7YIla/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.SekB7YIla/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.SekB7YIla/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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 157 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 14 06:14:03.322: 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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Oct 14 06:14:03.576: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 14 06:14:03.576: INFO: Creating resource for dynamic PV
Oct 14 06:14:03.576: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9661h5tm5
STEP: creating a claim
Oct 14 06:14:03.626: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-2nwq
STEP: Checking for subpath error in container status
Oct 14 06:14:27.882: INFO: Deleting pod "pod-subpath-test-dynamicpv-2nwq" in namespace "provisioning-9661"
Oct 14 06:14:27.953: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-2nwq" to be fully deleted
STEP: Deleting pod
Oct 14 06:14:30.056: INFO: Deleting pod "pod-subpath-test-dynamicpv-2nwq" in namespace "provisioning-9661"
STEP: Deleting pvc
Oct 14 06:14:30.204: INFO: Deleting PersistentVolumeClaim "awsxztmg"
... skipping 13 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.SekB7YIla/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.SekB7YIla/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath directory is outside the volume [Slow][LinuxOnly]
      /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] volumes
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Oct 14 06:14:45.633: INFO: Driver ebs.csi.aws.com doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] volumes
... skipping 201 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.SekB7YIla/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.SekB7YIla/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.SekB7YIla/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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 11 lines ...
Oct 14 06:13:53.948: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3415-e2e-scbdq9l
STEP: creating a claim
Oct 14 06:13:54.005: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-fgh7
STEP: Creating a pod to test subpath
Oct 14 06:13:54.164: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-fgh7" in namespace "provisioning-3415" to be "Succeeded or Failed"
Oct 14 06:13:54.214: INFO: Pod "pod-subpath-test-dynamicpv-fgh7": Phase="Pending", Reason="", readiness=false. Elapsed: 49.931249ms
Oct 14 06:13:56.264: INFO: Pod "pod-subpath-test-dynamicpv-fgh7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.099961112s
Oct 14 06:13:58.315: INFO: Pod "pod-subpath-test-dynamicpv-fgh7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.150564152s
Oct 14 06:14:00.365: INFO: Pod "pod-subpath-test-dynamicpv-fgh7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.200922802s
Oct 14 06:14:02.415: INFO: Pod "pod-subpath-test-dynamicpv-fgh7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.251442541s
Oct 14 06:14:04.466: INFO: Pod "pod-subpath-test-dynamicpv-fgh7": Phase="Pending", Reason="", readiness=false. Elapsed: 10.301813882s
Oct 14 06:14:06.516: INFO: Pod "pod-subpath-test-dynamicpv-fgh7": Phase="Pending", Reason="", readiness=false. Elapsed: 12.35241828s
Oct 14 06:14:08.579: INFO: Pod "pod-subpath-test-dynamicpv-fgh7": Phase="Pending", Reason="", readiness=false. Elapsed: 14.415168741s
Oct 14 06:14:10.630: INFO: Pod "pod-subpath-test-dynamicpv-fgh7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.466385037s
STEP: Saw pod success
Oct 14 06:14:10.630: INFO: Pod "pod-subpath-test-dynamicpv-fgh7" satisfied condition "Succeeded or Failed"
Oct 14 06:14:10.681: INFO: Trying to get logs from node ip-172-20-57-80.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-fgh7 container test-container-volume-dynamicpv-fgh7: <nil>
STEP: delete the pod
Oct 14 06:14:10.803: INFO: Waiting for pod pod-subpath-test-dynamicpv-fgh7 to disappear
Oct 14 06:14:10.852: INFO: Pod pod-subpath-test-dynamicpv-fgh7 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-fgh7
Oct 14 06:14:10.852: INFO: Deleting pod "pod-subpath-test-dynamicpv-fgh7" in namespace "provisioning-3415"
... skipping 87 lines ...
Oct 14 06:14:26.334: INFO: Waiting for pod aws-client to disappear
Oct 14 06:14:26.386: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Oct 14 06:14:26.386: INFO: Deleting PersistentVolumeClaim "pvc-rj5jf"
Oct 14 06:14:26.449: INFO: Deleting PersistentVolume "aws-rmkfn"
Oct 14 06:14:26.659: INFO: Couldn't delete PD "aws://us-west-1a/vol-0e9778c59da8ded00", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e9778c59da8ded00 is currently attached to i-019e724f48a0be6c0
	status code: 400, request id: 4d526c03-1d35-49f7-8721-5dea01e910e6
Oct 14 06:14:32.000: INFO: Couldn't delete PD "aws://us-west-1a/vol-0e9778c59da8ded00", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e9778c59da8ded00 is currently attached to i-019e724f48a0be6c0
	status code: 400, request id: dc9acc0a-7936-4528-8ebc-dcba5d8d18c3
Oct 14 06:14:37.331: INFO: Couldn't delete PD "aws://us-west-1a/vol-0e9778c59da8ded00", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e9778c59da8ded00 is currently attached to i-019e724f48a0be6c0
	status code: 400, request id: 94e44654-5431-4a4f-ab90-59ac1e0e3b0d
Oct 14 06:14:42.655: INFO: Couldn't delete PD "aws://us-west-1a/vol-0e9778c59da8ded00", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e9778c59da8ded00 is currently attached to i-019e724f48a0be6c0
	status code: 400, request id: 44579e76-900b-4b90-ab5e-c88f578d9ad0
Oct 14 06:14:48.091: INFO: Successfully deleted PD "aws://us-west-1a/vol-0e9778c59da8ded00".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumes
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 14 06:14:48.091: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-6345" for this suite.
... skipping 304 lines ...
Oct 14 06:14:45.074: INFO: Waiting for pod aws-client to disappear
Oct 14 06:14:45.129: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Oct 14 06:14:45.129: INFO: Deleting PersistentVolumeClaim "pvc-cg6nb"
Oct 14 06:14:45.181: INFO: Deleting PersistentVolume "aws-rs5h2"
Oct 14 06:14:45.392: INFO: Couldn't delete PD "aws://us-west-1a/vol-0f67fbb866a7ca78e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f67fbb866a7ca78e is currently attached to i-0f33202ea8f247785
	status code: 400, request id: 77f7fb4e-da42-472b-b001-596b8f03dead
Oct 14 06:14:50.793: INFO: Couldn't delete PD "aws://us-west-1a/vol-0f67fbb866a7ca78e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f67fbb866a7ca78e is currently attached to i-0f33202ea8f247785
	status code: 400, request id: 10e8aa78-7918-4f60-8a51-4bd58967b4e6
Oct 14 06:14:56.169: INFO: Successfully deleted PD "aws://us-west-1a/vol-0f67fbb866a7ca78e".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 14 06:14:56.169: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-5364" for this suite.
... skipping 549 lines ...
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 14 06:15:12.094: 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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Oct 14 06:15:12.392: INFO: found topology map[topology.ebs.csi.aws.com/zone:us-west-1a]
Oct 14 06:15:12.393: 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.458 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.SekB7YIla/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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

    Not enough topologies in cluster -- skipping

    /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 207 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 14 06:14:12.404: 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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Oct 14 06:14:12.658: INFO: Creating resource for dynamic PV
Oct 14 06:14:12.658: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7125-e2e-scz2sl7
STEP: creating a claim
Oct 14 06:14:12.710: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-5spt
STEP: Checking for subpath error in container status
Oct 14 06:14:36.974: INFO: Deleting pod "pod-subpath-test-dynamicpv-5spt" in namespace "provisioning-7125"
Oct 14 06:14:37.032: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-5spt" to be fully deleted
STEP: Deleting pod
Oct 14 06:14:39.140: INFO: Deleting pod "pod-subpath-test-dynamicpv-5spt" in namespace "provisioning-7125"
STEP: Deleting pvc
Oct 14 06:14:39.294: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comf84wv"
... skipping 15 lines ...

• [SLOW TEST:62.559 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath file is outside the volume [Slow][LinuxOnly]
    /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 14 06:14:56.638: 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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Oct 14 06:14:56.889: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Oct 14 06:14:57.192: INFO: Successfully created a new PD: "aws://us-west-1a/vol-01dabd4a90f40113c".
Oct 14 06:14:57.192: INFO: Creating resource for pre-provisioned PV
Oct 14 06:14:57.192: INFO: Creating PVC and PV
... skipping 2 lines ...
Oct 14 06:14:57.294: INFO: Waiting up to timeout=3m0s for PersistentVolumeClaims [pvc-svxrs] to have phase Bound
Oct 14 06:14:57.344: INFO: PersistentVolumeClaim pvc-svxrs found but phase is Pending instead of Bound.
Oct 14 06:14:59.395: INFO: PersistentVolumeClaim pvc-svxrs found and phase=Bound (2.100957708s)
Oct 14 06:14:59.395: INFO: Waiting up to 3m0s for PersistentVolume aws-8gb4n to have phase Bound
Oct 14 06:14:59.444: INFO: PersistentVolume aws-8gb4n found and phase=Bound (49.02253ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Oct 14 06:15:03.755: INFO: Deleting pod "pod-d9ea1bd3-580c-40b6-b502-e696ed2f604f" in namespace "volumemode-4333"
Oct 14 06:15:03.808: INFO: Wait up to 5m0s for pod "pod-d9ea1bd3-580c-40b6-b502-e696ed2f604f" to be fully deleted
STEP: Deleting pv and pvc
Oct 14 06:15:05.908: INFO: Deleting PersistentVolumeClaim "pvc-svxrs"
Oct 14 06:15:05.958: INFO: Deleting PersistentVolume "aws-8gb4n"
Oct 14 06:15:06.182: INFO: Couldn't delete PD "aws://us-west-1a/vol-01dabd4a90f40113c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01dabd4a90f40113c is currently attached to i-0f3386771e5823100
	status code: 400, request id: 80fc3c1f-b7ef-44ea-b48f-9c1aad9e9394
Oct 14 06:15:11.524: INFO: Couldn't delete PD "aws://us-west-1a/vol-01dabd4a90f40113c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01dabd4a90f40113c is currently attached to i-0f3386771e5823100
	status code: 400, request id: f35ee815-6099-463f-ab9d-a5768a344aec
Oct 14 06:15:16.869: INFO: Successfully deleted PD "aws://us-west-1a/vol-01dabd4a90f40113c".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 14 06:15:16.869: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-4333" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.SekB7YIla/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.SekB7YIla/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
    /tmp/kops.SekB7YIla/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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Oct 14 06:15:16.972: INFO: Distro debian doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
... skipping 307 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 14 06:14:52.311: 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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Oct 14 06:14:52.569: INFO: Creating resource for dynamic PV
Oct 14 06:14:52.569: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3803-e2e-sc7pghg
STEP: creating a claim
Oct 14 06:14:52.622: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-xmsz
STEP: Checking for subpath error in container status
Oct 14 06:15:12.895: INFO: Deleting pod "pod-subpath-test-dynamicpv-xmsz" in namespace "provisioning-3803"
Oct 14 06:15:12.949: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-xmsz" to be fully deleted
STEP: Deleting pod
Oct 14 06:15:15.052: INFO: Deleting pod "pod-subpath-test-dynamicpv-xmsz" in namespace "provisioning-3803"
STEP: Deleting pvc
Oct 14 06:15:15.209: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comxtz8t"
... skipping 11 lines ...

• [SLOW TEST:38.331 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath directory is outside the volume [Slow][LinuxOnly]
    /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [sig-storage] PersistentVolumes [Feature:vsphere][Feature:LabelSelector]
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 14 06:15:30.644: INFO: >>> kubeConfig: /root/.kube/config
... skipping 274 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 14 06:14:40.360: 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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Oct 14 06:14:40.620: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 14 06:14:40.620: INFO: Creating resource for dynamic PV
Oct 14 06:14:40.620: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3168w6jj
STEP: creating a claim
Oct 14 06:14:40.672: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-mtqg
STEP: Checking for subpath error in container status
Oct 14 06:15:04.938: INFO: Deleting pod "pod-subpath-test-dynamicpv-mtqg" in namespace "provisioning-316"
Oct 14 06:15:04.995: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-mtqg" to be fully deleted
STEP: Deleting pod
Oct 14 06:15:09.101: INFO: Deleting pod "pod-subpath-test-dynamicpv-mtqg" in namespace "provisioning-316"
STEP: Deleting pvc
Oct 14 06:15:09.259: INFO: Deleting PersistentVolumeClaim "awshtcmm"
... skipping 16 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.SekB7YIla/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.SekB7YIla/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath file is outside the volume [Slow][LinuxOnly]
      /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] volumeIO
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] volumeIO
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 77 lines ...
Oct 14 06:14:48.839: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8226-e2e-schcl22
STEP: creating a claim
Oct 14 06:14:48.892: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-7c6l
STEP: Creating a pod to test subpath
Oct 14 06:14:49.080: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-7c6l" in namespace "provisioning-8226" to be "Succeeded or Failed"
Oct 14 06:14:49.138: INFO: Pod "pod-subpath-test-dynamicpv-7c6l": Phase="Pending", Reason="", readiness=false. Elapsed: 57.636936ms
Oct 14 06:14:51.193: INFO: Pod "pod-subpath-test-dynamicpv-7c6l": Phase="Pending", Reason="", readiness=false. Elapsed: 2.113391464s
Oct 14 06:14:53.246: INFO: Pod "pod-subpath-test-dynamicpv-7c6l": Phase="Pending", Reason="", readiness=false. Elapsed: 4.165712964s
Oct 14 06:14:55.298: INFO: Pod "pod-subpath-test-dynamicpv-7c6l": Phase="Pending", Reason="", readiness=false. Elapsed: 6.217747745s
Oct 14 06:14:57.349: INFO: Pod "pod-subpath-test-dynamicpv-7c6l": Phase="Pending", Reason="", readiness=false. Elapsed: 8.269615001s
Oct 14 06:14:59.402: INFO: Pod "pod-subpath-test-dynamicpv-7c6l": Phase="Pending", Reason="", readiness=false. Elapsed: 10.32253979s
Oct 14 06:15:01.454: INFO: Pod "pod-subpath-test-dynamicpv-7c6l": Phase="Pending", Reason="", readiness=false. Elapsed: 12.37446555s
Oct 14 06:15:03.507: INFO: Pod "pod-subpath-test-dynamicpv-7c6l": Phase="Pending", Reason="", readiness=false. Elapsed: 14.42697087s
Oct 14 06:15:05.559: INFO: Pod "pod-subpath-test-dynamicpv-7c6l": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.478696439s
STEP: Saw pod success
Oct 14 06:15:05.559: INFO: Pod "pod-subpath-test-dynamicpv-7c6l" satisfied condition "Succeeded or Failed"
Oct 14 06:15:05.610: INFO: Trying to get logs from node ip-172-20-57-80.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-7c6l container test-container-subpath-dynamicpv-7c6l: <nil>
STEP: delete the pod
Oct 14 06:15:06.366: INFO: Waiting for pod pod-subpath-test-dynamicpv-7c6l to disappear
Oct 14 06:15:06.418: INFO: Pod pod-subpath-test-dynamicpv-7c6l no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-7c6l
Oct 14 06:15:06.418: INFO: Deleting pod "pod-subpath-test-dynamicpv-7c6l" in namespace "provisioning-8226"
... skipping 137 lines ...

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 442 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 14 06:15:12.707: 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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Oct 14 06:15:12.955: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 14 06:15:12.955: INFO: Creating resource for dynamic PV
Oct 14 06:15:12.955: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8031r2fr8
STEP: creating a claim
Oct 14 06:15:13.005: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-n58v
STEP: Checking for subpath error in container status
Oct 14 06:15:37.264: INFO: Deleting pod "pod-subpath-test-dynamicpv-n58v" in namespace "provisioning-8031"
Oct 14 06:15:37.315: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-n58v" to be fully deleted
STEP: Deleting pod
Oct 14 06:15:39.414: INFO: Deleting pod "pod-subpath-test-dynamicpv-n58v" in namespace "provisioning-8031"
STEP: Deleting pvc
Oct 14 06:15:39.571: INFO: Deleting PersistentVolumeClaim "awsvxc7k"
... skipping 14 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.SekB7YIla/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.SekB7YIla/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.SekB7YIla/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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 125 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 14 06:15:32.530: 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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Oct 14 06:15:32.778: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 14 06:15:32.778: INFO: Creating resource for dynamic PV
Oct 14 06:15:32.778: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-3955s8dhg
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Oct 14 06:15:39.140: INFO: Deleting pod "pod-ee789ada-5925-47f0-a6a2-232918ac7e5a" in namespace "volumemode-3955"
Oct 14 06:15:39.195: INFO: Wait up to 5m0s for pod "pod-ee789ada-5925-47f0-a6a2-232918ac7e5a" to be fully deleted
STEP: Deleting pvc
Oct 14 06:15:41.394: INFO: Deleting PersistentVolumeClaim "awsplrw8"
Oct 14 06:15:41.448: INFO: Waiting up to 5m0s for PersistentVolume pvc-d363ecc9-8819-4ef5-832c-adeb9c8fa2ce to get deleted
Oct 14 06:15:41.499: INFO: PersistentVolume pvc-d363ecc9-8819-4ef5-832c-adeb9c8fa2ce found and phase=Released (50.519661ms)
... skipping 16 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.SekB7YIla/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.SekB7YIla/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
    /tmp/kops.SekB7YIla/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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 8 lines ...
Oct 14 06:15:26.685: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9935nfqls
STEP: creating a claim
Oct 14 06:15:26.738: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-zgdt
STEP: Creating a pod to test subpath
Oct 14 06:15:26.893: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-zgdt" in namespace "provisioning-9935" to be "Succeeded or Failed"
Oct 14 06:15:26.942: INFO: Pod "pod-subpath-test-dynamicpv-zgdt": Phase="Pending", Reason="", readiness=false. Elapsed: 49.335726ms
Oct 14 06:15:28.993: INFO: Pod "pod-subpath-test-dynamicpv-zgdt": Phase="Pending", Reason="", readiness=false. Elapsed: 2.100503014s
Oct 14 06:15:31.048: INFO: Pod "pod-subpath-test-dynamicpv-zgdt": Phase="Pending", Reason="", readiness=false. Elapsed: 4.154780384s
Oct 14 06:15:33.100: INFO: Pod "pod-subpath-test-dynamicpv-zgdt": Phase="Pending", Reason="", readiness=false. Elapsed: 6.206840005s
Oct 14 06:15:35.151: INFO: Pod "pod-subpath-test-dynamicpv-zgdt": Phase="Pending", Reason="", readiness=false. Elapsed: 8.257646709s
Oct 14 06:15:37.203: INFO: Pod "pod-subpath-test-dynamicpv-zgdt": Phase="Pending", Reason="", readiness=false. Elapsed: 10.310199693s
... skipping 4 lines ...
Oct 14 06:15:47.458: INFO: Pod "pod-subpath-test-dynamicpv-zgdt": Phase="Pending", Reason="", readiness=false. Elapsed: 20.565411832s
Oct 14 06:15:49.509: INFO: Pod "pod-subpath-test-dynamicpv-zgdt": Phase="Pending", Reason="", readiness=false. Elapsed: 22.615834243s
Oct 14 06:15:51.559: INFO: Pod "pod-subpath-test-dynamicpv-zgdt": Phase="Pending", Reason="", readiness=false. Elapsed: 24.66625334s
Oct 14 06:15:53.610: INFO: Pod "pod-subpath-test-dynamicpv-zgdt": Phase="Pending", Reason="", readiness=false. Elapsed: 26.716963333s
Oct 14 06:15:55.661: INFO: Pod "pod-subpath-test-dynamicpv-zgdt": Phase="Succeeded", Reason="", readiness=false. Elapsed: 28.767679922s
STEP: Saw pod success
Oct 14 06:15:55.661: INFO: Pod "pod-subpath-test-dynamicpv-zgdt" satisfied condition "Succeeded or Failed"
Oct 14 06:15:55.722: INFO: Trying to get logs from node ip-172-20-44-65.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-zgdt container test-container-volume-dynamicpv-zgdt: <nil>
STEP: delete the pod
Oct 14 06:15:56.534: INFO: Waiting for pod pod-subpath-test-dynamicpv-zgdt to disappear
Oct 14 06:15:56.586: INFO: Pod pod-subpath-test-dynamicpv-zgdt no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-zgdt
Oct 14 06:15:56.586: INFO: Deleting pod "pod-subpath-test-dynamicpv-zgdt" in namespace "provisioning-9935"
... skipping 42 lines ...
Oct 14 06:14:43.922: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-1651rt6wt      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-1651    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-1651rt6wt,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-1651    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-1651rt6wt,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-1651    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-1651rt6wt,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-1651rt6wt    fcd4f656-71ff-4645-9902-719f16a623a6 12410 0 2021-10-14 06:14:44 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-10-14 06:14:44 +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-84nwm pvc- provisioning-1651  46d78830-f6ae-4d69-b88e-550d3b456c62 12418 0 2021-10-14 06:14:44 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-10-14 06:14:44 +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-1651rt6wt,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-6424580b-5945-4cac-b74a-ef19420d82e2 in namespace provisioning-1651
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Oct 14 06:15:10.485: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-zt5rx" in namespace "provisioning-1651" to be "Succeeded or Failed"
Oct 14 06:15:10.536: INFO: Pod "pvc-volume-tester-writer-zt5rx": Phase="Pending", Reason="", readiness=false. Elapsed: 50.361016ms
Oct 14 06:15:12.597: INFO: Pod "pvc-volume-tester-writer-zt5rx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.111042953s
Oct 14 06:15:14.649: INFO: Pod "pvc-volume-tester-writer-zt5rx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.163426744s
Oct 14 06:15:16.699: INFO: Pod "pvc-volume-tester-writer-zt5rx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.213719037s
Oct 14 06:15:18.752: INFO: Pod "pvc-volume-tester-writer-zt5rx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.266716235s
Oct 14 06:15:20.804: INFO: Pod "pvc-volume-tester-writer-zt5rx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.318100145s
... skipping 8 lines ...
Oct 14 06:15:39.271: INFO: Pod "pvc-volume-tester-writer-zt5rx": Phase="Pending", Reason="", readiness=false. Elapsed: 28.785471482s
Oct 14 06:15:41.321: INFO: Pod "pvc-volume-tester-writer-zt5rx": Phase="Pending", Reason="", readiness=false. Elapsed: 30.835903883s
Oct 14 06:15:43.373: INFO: Pod "pvc-volume-tester-writer-zt5rx": Phase="Pending", Reason="", readiness=false. Elapsed: 32.887292884s
Oct 14 06:15:45.424: INFO: Pod "pvc-volume-tester-writer-zt5rx": Phase="Pending", Reason="", readiness=false. Elapsed: 34.938265478s
Oct 14 06:15:47.475: INFO: Pod "pvc-volume-tester-writer-zt5rx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 36.989660811s
STEP: Saw pod success
Oct 14 06:15:47.475: INFO: Pod "pvc-volume-tester-writer-zt5rx" satisfied condition "Succeeded or Failed"
Oct 14 06:15:47.577: INFO: Pod pvc-volume-tester-writer-zt5rx has the following logs: 
Oct 14 06:15:47.577: INFO: Deleting pod "pvc-volume-tester-writer-zt5rx" in namespace "provisioning-1651"
Oct 14 06:15:47.636: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-zt5rx" 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-37-170.us-west-1.compute.internal"
Oct 14 06:15:47.844: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-5qqwl" in namespace "provisioning-1651" to be "Succeeded or Failed"
Oct 14 06:15:47.895: INFO: Pod "pvc-volume-tester-reader-5qqwl": Phase="Pending", Reason="", readiness=false. Elapsed: 50.997468ms
Oct 14 06:15:49.947: INFO: Pod "pvc-volume-tester-reader-5qqwl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.102846958s
Oct 14 06:15:51.997: INFO: Pod "pvc-volume-tester-reader-5qqwl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.152856871s
Oct 14 06:15:54.049: INFO: Pod "pvc-volume-tester-reader-5qqwl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.204346266s
STEP: Saw pod success
Oct 14 06:15:54.049: INFO: Pod "pvc-volume-tester-reader-5qqwl" satisfied condition "Succeeded or Failed"
Oct 14 06:15:54.152: INFO: Pod pvc-volume-tester-reader-5qqwl has the following logs: hello world

Oct 14 06:15:54.152: INFO: Deleting pod "pvc-volume-tester-reader-5qqwl" in namespace "provisioning-1651"
Oct 14 06:15:54.213: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-5qqwl" to be fully deleted
Oct 14 06:15:54.262: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-84nwm] to have phase Bound
Oct 14 06:15:54.313: INFO: PersistentVolumeClaim pvc-84nwm found and phase=Bound (50.765165ms)
... skipping 93 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 14 06:15:14.965: 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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Oct 14 06:15:15.220: INFO: Creating resource for dynamic PV
Oct 14 06:15:15.220: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4944-e2e-scmp7hb
STEP: creating a claim
Oct 14 06:15:15.272: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-mfpl
STEP: Checking for subpath error in container status
Oct 14 06:15:31.534: INFO: Deleting pod "pod-subpath-test-dynamicpv-mfpl" in namespace "provisioning-4944"
Oct 14 06:15:31.592: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-mfpl" to be fully deleted
STEP: Deleting pod
Oct 14 06:15:33.695: INFO: Deleting pod "pod-subpath-test-dynamicpv-mfpl" in namespace "provisioning-4944"
STEP: Deleting pvc
Oct 14 06:15:33.843: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.combjgzv"
... skipping 21 lines ...

• [SLOW TEST:84.879 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.SekB7YIla/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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 7 lines ...
Oct 14 06:15:40.115: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4508-e2e-sc6c9cj
STEP: creating a claim
Oct 14 06:15:40.168: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-j5ch
STEP: Creating a pod to test multi_subpath
Oct 14 06:15:40.331: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-j5ch" in namespace "provisioning-4508" to be "Succeeded or Failed"
Oct 14 06:15:40.383: INFO: Pod "pod-subpath-test-dynamicpv-j5ch": Phase="Pending", Reason="", readiness=false. Elapsed: 52.009291ms
Oct 14 06:15:42.442: INFO: Pod "pod-subpath-test-dynamicpv-j5ch": Phase="Pending", Reason="", readiness=false. Elapsed: 2.111332766s
Oct 14 06:15:44.495: INFO: Pod "pod-subpath-test-dynamicpv-j5ch": Phase="Pending", Reason="", readiness=false. Elapsed: 4.164236179s
Oct 14 06:15:46.548: INFO: Pod "pod-subpath-test-dynamicpv-j5ch": Phase="Pending", Reason="", readiness=false. Elapsed: 6.217007506s
Oct 14 06:15:48.601: INFO: Pod "pod-subpath-test-dynamicpv-j5ch": Phase="Pending", Reason="", readiness=false. Elapsed: 8.270299378s
Oct 14 06:15:50.654: INFO: Pod "pod-subpath-test-dynamicpv-j5ch": Phase="Pending", Reason="", readiness=false. Elapsed: 10.323260912s
... skipping 11 lines ...
Oct 14 06:16:15.299: INFO: Pod "pod-subpath-test-dynamicpv-j5ch": Phase="Pending", Reason="", readiness=false. Elapsed: 34.967949003s
Oct 14 06:16:17.351: INFO: Pod "pod-subpath-test-dynamicpv-j5ch": Phase="Pending", Reason="", readiness=false. Elapsed: 37.020237205s
Oct 14 06:16:19.404: INFO: Pod "pod-subpath-test-dynamicpv-j5ch": Phase="Pending", Reason="", readiness=false. Elapsed: 39.073396501s
Oct 14 06:16:21.457: INFO: Pod "pod-subpath-test-dynamicpv-j5ch": Phase="Pending", Reason="", readiness=false. Elapsed: 41.125988741s
Oct 14 06:16:23.510: INFO: Pod "pod-subpath-test-dynamicpv-j5ch": Phase="Succeeded", Reason="", readiness=false. Elapsed: 43.179205047s
STEP: Saw pod success
Oct 14 06:16:23.510: INFO: Pod "pod-subpath-test-dynamicpv-j5ch" satisfied condition "Succeeded or Failed"
Oct 14 06:16:23.562: INFO: Trying to get logs from node ip-172-20-57-80.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-j5ch container test-container-subpath-dynamicpv-j5ch: <nil>
STEP: delete the pod
Oct 14 06:16:23.676: INFO: Waiting for pod pod-subpath-test-dynamicpv-j5ch to disappear
Oct 14 06:16:23.727: INFO: Pod pod-subpath-test-dynamicpv-j5ch no longer exists
STEP: Deleting pod
Oct 14 06:16:23.727: INFO: Deleting pod "pod-subpath-test-dynamicpv-j5ch" in namespace "provisioning-4508"
... skipping 281 lines ...
Oct 14 06:15:14.164: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6854-e2e-scjzncf
STEP: creating a claim
Oct 14 06:15:14.216: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-nk9s
STEP: Creating a pod to test subpath
Oct 14 06:15:14.375: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-nk9s" in namespace "provisioning-6854" to be "Succeeded or Failed"
Oct 14 06:15:14.425: INFO: Pod "pod-subpath-test-dynamicpv-nk9s": Phase="Pending", Reason="", readiness=false. Elapsed: 49.385063ms
Oct 14 06:15:16.475: INFO: Pod "pod-subpath-test-dynamicpv-nk9s": Phase="Pending", Reason="", readiness=false. Elapsed: 2.099538187s
Oct 14 06:15:18.530: INFO: Pod "pod-subpath-test-dynamicpv-nk9s": Phase="Pending", Reason="", readiness=false. Elapsed: 4.154521023s
Oct 14 06:15:20.580: INFO: Pod "pod-subpath-test-dynamicpv-nk9s": Phase="Pending", Reason="", readiness=false. Elapsed: 6.204997708s
Oct 14 06:15:22.632: INFO: Pod "pod-subpath-test-dynamicpv-nk9s": Phase="Pending", Reason="", readiness=false. Elapsed: 8.256795888s
Oct 14 06:15:24.683: INFO: Pod "pod-subpath-test-dynamicpv-nk9s": Phase="Pending", Reason="", readiness=false. Elapsed: 10.307781435s
... skipping 11 lines ...
Oct 14 06:15:49.294: INFO: Pod "pod-subpath-test-dynamicpv-nk9s": Phase="Pending", Reason="", readiness=false. Elapsed: 34.919120885s
Oct 14 06:15:51.344: INFO: Pod "pod-subpath-test-dynamicpv-nk9s": Phase="Pending", Reason="", readiness=false. Elapsed: 36.968897298s
Oct 14 06:15:53.396: INFO: Pod "pod-subpath-test-dynamicpv-nk9s": Phase="Pending", Reason="", readiness=false. Elapsed: 39.020462116s
Oct 14 06:15:55.447: INFO: Pod "pod-subpath-test-dynamicpv-nk9s": Phase="Pending", Reason="", readiness=false. Elapsed: 41.071581565s
Oct 14 06:15:57.498: INFO: Pod "pod-subpath-test-dynamicpv-nk9s": Phase="Succeeded", Reason="", readiness=false. Elapsed: 43.122863239s
STEP: Saw pod success
Oct 14 06:15:57.498: INFO: Pod "pod-subpath-test-dynamicpv-nk9s" satisfied condition "Succeeded or Failed"
Oct 14 06:15:57.549: INFO: Trying to get logs from node ip-172-20-37-170.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-nk9s container test-container-subpath-dynamicpv-nk9s: <nil>
STEP: delete the pod
Oct 14 06:15:57.661: INFO: Waiting for pod pod-subpath-test-dynamicpv-nk9s to disappear
Oct 14 06:15:57.718: INFO: Pod pod-subpath-test-dynamicpv-nk9s no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-nk9s
Oct 14 06:15:57.718: INFO: Deleting pod "pod-subpath-test-dynamicpv-nk9s" in namespace "provisioning-6854"
... skipping 89 lines ...
Oct 14 06:15:36.677: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3496-e2e-schckh8
STEP: creating a claim
Oct 14 06:15:36.731: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-5hlm
STEP: Creating a pod to test atomic-volume-subpath
Oct 14 06:15:36.912: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-5hlm" in namespace "provisioning-3496" to be "Succeeded or Failed"
Oct 14 06:15:36.964: INFO: Pod "pod-subpath-test-dynamicpv-5hlm": Phase="Pending", Reason="", readiness=false. Elapsed: 51.884184ms
Oct 14 06:15:39.017: INFO: Pod "pod-subpath-test-dynamicpv-5hlm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.104871938s
Oct 14 06:15:41.070: INFO: Pod "pod-subpath-test-dynamicpv-5hlm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.157292812s
Oct 14 06:15:43.122: INFO: Pod "pod-subpath-test-dynamicpv-5hlm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.209566017s
Oct 14 06:15:45.184: INFO: Pod "pod-subpath-test-dynamicpv-5hlm": Phase="Pending", Reason="", readiness=false. Elapsed: 8.271213114s
Oct 14 06:15:47.236: INFO: Pod "pod-subpath-test-dynamicpv-5hlm": Phase="Pending", Reason="", readiness=false. Elapsed: 10.323261622s
... skipping 22 lines ...
Oct 14 06:16:34.474: INFO: Pod "pod-subpath-test-dynamicpv-5hlm": Phase="Running", Reason="", readiness=true. Elapsed: 57.561669313s
Oct 14 06:16:36.526: INFO: Pod "pod-subpath-test-dynamicpv-5hlm": Phase="Running", Reason="", readiness=true. Elapsed: 59.613487896s
Oct 14 06:16:38.579: INFO: Pod "pod-subpath-test-dynamicpv-5hlm": Phase="Running", Reason="", readiness=true. Elapsed: 1m1.666813992s
Oct 14 06:16:40.632: INFO: Pod "pod-subpath-test-dynamicpv-5hlm": Phase="Running", Reason="", readiness=true. Elapsed: 1m3.719727664s
Oct 14 06:16:42.684: INFO: Pod "pod-subpath-test-dynamicpv-5hlm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m5.771935733s
STEP: Saw pod success
Oct 14 06:16:42.684: INFO: Pod "pod-subpath-test-dynamicpv-5hlm" satisfied condition "Succeeded or Failed"
Oct 14 06:16:42.736: INFO: Trying to get logs from node ip-172-20-47-110.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-5hlm container test-container-subpath-dynamicpv-5hlm: <nil>
STEP: delete the pod
Oct 14 06:16:42.880: INFO: Waiting for pod pod-subpath-test-dynamicpv-5hlm to disappear
Oct 14 06:16:42.932: INFO: Pod pod-subpath-test-dynamicpv-5hlm no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-5hlm
Oct 14 06:16:42.932: INFO: Deleting pod "pod-subpath-test-dynamicpv-5hlm" in namespace "provisioning-3496"
... skipping 471 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 14 06:15:42.259: 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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Oct 14 06:15:42.516: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 14 06:15:42.516: INFO: Creating resource for dynamic PV
Oct 14 06:15:42.516: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-6073rstm7
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Oct 14 06:16:06.882: INFO: Deleting pod "pod-8043a4c8-4de2-4e5a-b8d0-3d602ca9a997" in namespace "volumemode-6073"
Oct 14 06:16:06.935: INFO: Wait up to 5m0s for pod "pod-8043a4c8-4de2-4e5a-b8d0-3d602ca9a997" to be fully deleted
STEP: Deleting pvc
Oct 14 06:16:09.150: INFO: Deleting PersistentVolumeClaim "awsrs66t"
Oct 14 06:16:09.204: INFO: Waiting up to 5m0s for PersistentVolume pvc-d140db2f-4628-443e-8475-e69086fb33aa to get deleted
Oct 14 06:16:09.256: INFO: PersistentVolume pvc-d140db2f-4628-443e-8475-e69086fb33aa found and phase=Released (51.398135ms)
... skipping 39 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.SekB7YIla/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.SekB7YIla/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (block volmode)] volumeMode
    /tmp/kops.SekB7YIla/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.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeLimits
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeLimits
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 97 lines ...
Oct 14 06:14:44.866: INFO: Creating resource for dynamic PV
Oct 14 06:14:44.866: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-2462-e2e-scsjt62
STEP: creating a claim
Oct 14 06:14:44.918: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Oct 14 06:14:45.081: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-cqxsk" in namespace "snapshotting-2462" to be "Succeeded or Failed"
Oct 14 06:14:45.132: INFO: Pod "pvc-snapshottable-tester-cqxsk": Phase="Pending", Reason="", readiness=false. Elapsed: 51.385224ms
Oct 14 06:14:47.188: INFO: Pod "pvc-snapshottable-tester-cqxsk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.106639637s
Oct 14 06:14:49.246: INFO: Pod "pvc-snapshottable-tester-cqxsk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.164526341s
Oct 14 06:14:51.298: INFO: Pod "pvc-snapshottable-tester-cqxsk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.216817248s
Oct 14 06:14:53.352: INFO: Pod "pvc-snapshottable-tester-cqxsk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.270736178s
Oct 14 06:14:55.403: INFO: Pod "pvc-snapshottable-tester-cqxsk": Phase="Pending", Reason="", readiness=false. Elapsed: 10.322425768s
... skipping 2 lines ...
Oct 14 06:15:01.562: INFO: Pod "pvc-snapshottable-tester-cqxsk": Phase="Pending", Reason="", readiness=false. Elapsed: 16.481207795s
Oct 14 06:15:03.615: INFO: Pod "pvc-snapshottable-tester-cqxsk": Phase="Pending", Reason="", readiness=false. Elapsed: 18.533879207s
Oct 14 06:15:05.666: INFO: Pod "pvc-snapshottable-tester-cqxsk": Phase="Pending", Reason="", readiness=false. Elapsed: 20.585465777s
Oct 14 06:15:07.720: INFO: Pod "pvc-snapshottable-tester-cqxsk": Phase="Running", Reason="", readiness=true. Elapsed: 22.638979588s
Oct 14 06:15:09.776: INFO: Pod "pvc-snapshottable-tester-cqxsk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.695398146s
STEP: Saw pod success
Oct 14 06:15:09.776: INFO: Pod "pvc-snapshottable-tester-cqxsk" satisfied condition "Succeeded or Failed"
Oct 14 06:15:09.889: INFO: Pod pvc-snapshottable-tester-cqxsk has the following logs: 
Oct 14 06:15:09.889: INFO: Deleting pod "pvc-snapshottable-tester-cqxsk" in namespace "snapshotting-2462"
Oct 14 06:15:10.003: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-cqxsk" to be fully deleted
Oct 14 06:15:10.055: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.com4w4rp] to have phase Bound
Oct 14 06:15:10.106: INFO: PersistentVolumeClaim ebs.csi.aws.com4w4rp found and phase=Bound (51.242936ms)
STEP: [init] checking the claim
... skipping 78 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:243
STEP: checking the snapshot
STEP: checking the SnapshotContent
STEP: Modifying source data test
STEP: modifying the data in the source PVC
Oct 14 06:16:53.889: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-xhwzn" in namespace "snapshotting-2462" to be "Succeeded or Failed"
Oct 14 06:16:53.941: INFO: Pod "pvc-snapshottable-data-tester-xhwzn": Phase="Pending", Reason="", readiness=false. Elapsed: 51.601503ms
Oct 14 06:16:55.992: INFO: Pod "pvc-snapshottable-data-tester-xhwzn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.103242228s
Oct 14 06:16:58.044: INFO: Pod "pvc-snapshottable-data-tester-xhwzn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.155057048s
Oct 14 06:17:00.097: INFO: Pod "pvc-snapshottable-data-tester-xhwzn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.207433466s
Oct 14 06:17:02.149: INFO: Pod "pvc-snapshottable-data-tester-xhwzn": Phase="Pending", Reason="", readiness=false. Elapsed: 8.259871885s
Oct 14 06:17:04.201: INFO: Pod "pvc-snapshottable-data-tester-xhwzn": Phase="Pending", Reason="", readiness=false. Elapsed: 10.312106155s
Oct 14 06:17:06.254: INFO: Pod "pvc-snapshottable-data-tester-xhwzn": Phase="Pending", Reason="", readiness=false. Elapsed: 12.364904693s
Oct 14 06:17:08.308: INFO: Pod "pvc-snapshottable-data-tester-xhwzn": Phase="Pending", Reason="", readiness=false. Elapsed: 14.419197497s
Oct 14 06:17:10.361: INFO: Pod "pvc-snapshottable-data-tester-xhwzn": Phase="Pending", Reason="", readiness=false. Elapsed: 16.472132771s
Oct 14 06:17:12.414: INFO: Pod "pvc-snapshottable-data-tester-xhwzn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.524657542s
STEP: Saw pod success
Oct 14 06:17:12.414: INFO: Pod "pvc-snapshottable-data-tester-xhwzn" satisfied condition "Succeeded or Failed"
Oct 14 06:17:12.519: INFO: Pod pvc-snapshottable-data-tester-xhwzn has the following logs: 
Oct 14 06:17:12.519: INFO: Deleting pod "pvc-snapshottable-data-tester-xhwzn" in namespace "snapshotting-2462"
Oct 14 06:17:12.585: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-xhwzn" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Oct 14 06:21:28.846: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-b6f7c24027-45100.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-2462 exec restored-pvc-tester-wxd6m --namespace=snapshotting-2462 -- cat /mnt/test/data'
... skipping 32 lines ...
Oct 14 06:21:54.285: INFO: volumesnapshotcontents pre-provisioned-snapcontent-f27613a2-de51-4c91-bc5e-ae066818a971 has been found and is not deleted
Oct 14 06:21:55.336: INFO: volumesnapshotcontents pre-provisioned-snapcontent-f27613a2-de51-4c91-bc5e-ae066818a971 has been found and is not deleted
Oct 14 06:21:56.387: INFO: volumesnapshotcontents pre-provisioned-snapcontent-f27613a2-de51-4c91-bc5e-ae066818a971 has been found and is not deleted
Oct 14 06:21:57.437: INFO: volumesnapshotcontents pre-provisioned-snapcontent-f27613a2-de51-4c91-bc5e-ae066818a971 has been found and is not deleted
Oct 14 06:21:58.488: INFO: volumesnapshotcontents pre-provisioned-snapcontent-f27613a2-de51-4c91-bc5e-ae066818a971 has been found and is not deleted
Oct 14 06:21:59.539: INFO: volumesnapshotcontents pre-provisioned-snapcontent-f27613a2-de51-4c91-bc5e-ae066818a971 has been found and is not deleted
Oct 14 06:22:00.539: INFO: WaitUntil failed after reaching the timeout 30s
[AfterEach] volume snapshot controller
  /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:221
Oct 14 06:22:00.598: INFO: Pod restored-pvc-tester-wxd6m has the following logs: 
Oct 14 06:22:00.599: INFO: Deleting pod "restored-pvc-tester-wxd6m" in namespace "snapshotting-2462"
Oct 14 06:22:00.650: INFO: Wait up to 5m0s for pod "restored-pvc-tester-wxd6m" to be fully deleted
Oct 14 06:22:32.749: INFO: deleting claim "snapshotting-2462"/"pvc-l62b7"
... skipping 32 lines ...
        /tmp/kops.SekB7YIla/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:243
------------------------------


Summarizing 1 Failure:

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

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


Ginkgo ran 1 suite in 14m28.584670457s
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 1481 lines ...