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

No Test Failures!


Error lines from build-log.txt

... skipping 502 lines ...
I0611 16:10:23.848805   11755 up.go:43] Cleaning up any leaked resources from previous cluster
I0611 16:10:23.849987   11755 dumplogs.go:38] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops toolbox dump --name e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ubuntu
I0611 16:10:23.868594   11761 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0611 16:10:23.868668   11761 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io" not found
W0611 16:10:24.379392   11755 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0611 16:10:24.379428   11755 down.go:48] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops delete cluster --name e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --yes
I0611 16:10:24.392861   11771 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0611 16:10:24.392932   11771 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io" not found
I0611 16:10:24.881300   11755 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/06/11 16:10:24 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
I0611 16:10:24.898296   11755 http.go:37] curl https://ip.jsb.workers.dev
I0611 16:10:25.065441   11755 up.go:144] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops create cluster --name e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --cloud aws --kubernetes-version 1.21.0 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --networking calico --override=cluster.spec.cloudConfig.awsEBSCSIDriver.enabled=true --override=cluster.spec.snapshotController.enabled=true --override=cluster.spec.certManager.enabled=true --admin-access 34.123.6.164/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones us-west-1a --master-size c5.large
I0611 16:10:25.081934   11787 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0611 16:10:25.082668   11787 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I0611 16:10:25.124312   11787 create_cluster.go:728] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0611 16:10:25.671496   11787 new_cluster.go:1039]  Cloud Provider ID = aws
... skipping 40 lines ...

I0611 16:10:51.910136   11755 up.go:181] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops validate cluster --name e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0611 16:10:51.925826   11806 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0611 16:10:51.926048   11806 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io

W0611 16:10:53.019774   11806 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0611 16:11:03.059726   11806 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0611 16:13:33.623219   11806 validate_cluster.go:221] (will retry): cluster not yet healthy
W0611 16:13:43.665693   11806 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

... skipping 7 lines ...
Machine	i-0904333f4b3ec64fb				machine "i-0904333f4b3ec64fb" has not yet joined cluster
Machine	i-0d96e5f5f1bf58424				machine "i-0d96e5f5f1bf58424" has not yet joined cluster
Machine	i-0e926e71eaea5d363				machine "i-0e926e71eaea5d363" has not yet joined cluster
Pod	kube-system/coredns-autoscaler-6f594f4c58-ccg5f	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-ccg5f" is pending
Pod	kube-system/coredns-f45c4bf76-jtvbm		system-cluster-critical pod "coredns-f45c4bf76-jtvbm" is pending

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

... skipping 7 lines ...
Machine	i-0904333f4b3ec64fb				machine "i-0904333f4b3ec64fb" has not yet joined cluster
Machine	i-0d96e5f5f1bf58424				machine "i-0d96e5f5f1bf58424" has not yet joined cluster
Machine	i-0e926e71eaea5d363				machine "i-0e926e71eaea5d363" has not yet joined cluster
Pod	kube-system/coredns-autoscaler-6f594f4c58-ccg5f	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-ccg5f" is pending
Pod	kube-system/coredns-f45c4bf76-jtvbm		system-cluster-critical pod "coredns-f45c4bf76-jtvbm" is pending

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

... skipping 7 lines ...
Machine	i-0904333f4b3ec64fb				machine "i-0904333f4b3ec64fb" has not yet joined cluster
Machine	i-0d96e5f5f1bf58424				machine "i-0d96e5f5f1bf58424" has not yet joined cluster
Machine	i-0e926e71eaea5d363				machine "i-0e926e71eaea5d363" has not yet joined cluster
Pod	kube-system/coredns-autoscaler-6f594f4c58-ccg5f	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-ccg5f" is pending
Pod	kube-system/coredns-f45c4bf76-jtvbm		system-cluster-critical pod "coredns-f45c4bf76-jtvbm" is pending

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

... skipping 7 lines ...
Machine	i-0904333f4b3ec64fb				machine "i-0904333f4b3ec64fb" has not yet joined cluster
Machine	i-0d96e5f5f1bf58424				machine "i-0d96e5f5f1bf58424" has not yet joined cluster
Machine	i-0e926e71eaea5d363				machine "i-0e926e71eaea5d363" has not yet joined cluster
Pod	kube-system/coredns-autoscaler-6f594f4c58-ccg5f	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-ccg5f" is pending
Pod	kube-system/coredns-f45c4bf76-jtvbm		system-cluster-critical pod "coredns-f45c4bf76-jtvbm" is pending

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

... skipping 7 lines ...
Machine	i-0904333f4b3ec64fb				machine "i-0904333f4b3ec64fb" has not yet joined cluster
Machine	i-0d96e5f5f1bf58424				machine "i-0d96e5f5f1bf58424" has not yet joined cluster
Machine	i-0e926e71eaea5d363				machine "i-0e926e71eaea5d363" has not yet joined cluster
Pod	kube-system/coredns-autoscaler-6f594f4c58-ccg5f	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-ccg5f" is pending
Pod	kube-system/coredns-f45c4bf76-jtvbm		system-cluster-critical pod "coredns-f45c4bf76-jtvbm" is pending

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

... skipping 7 lines ...
Machine	i-0904333f4b3ec64fb				machine "i-0904333f4b3ec64fb" has not yet joined cluster
Machine	i-0d96e5f5f1bf58424				machine "i-0d96e5f5f1bf58424" has not yet joined cluster
Machine	i-0e926e71eaea5d363				machine "i-0e926e71eaea5d363" has not yet joined cluster
Pod	kube-system/coredns-autoscaler-6f594f4c58-ccg5f	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-ccg5f" is pending
Pod	kube-system/coredns-f45c4bf76-jtvbm		system-cluster-critical pod "coredns-f45c4bf76-jtvbm" is pending

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

... skipping 7 lines ...
Machine	i-0904333f4b3ec64fb				machine "i-0904333f4b3ec64fb" has not yet joined cluster
Machine	i-0d96e5f5f1bf58424				machine "i-0d96e5f5f1bf58424" has not yet joined cluster
Machine	i-0e926e71eaea5d363				machine "i-0e926e71eaea5d363" has not yet joined cluster
Pod	kube-system/coredns-autoscaler-6f594f4c58-ccg5f	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-ccg5f" is pending
Pod	kube-system/coredns-f45c4bf76-jtvbm		system-cluster-critical pod "coredns-f45c4bf76-jtvbm" is pending

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

... skipping 7 lines ...
Machine	i-0904333f4b3ec64fb				machine "i-0904333f4b3ec64fb" has not yet joined cluster
Machine	i-0d96e5f5f1bf58424				machine "i-0d96e5f5f1bf58424" has not yet joined cluster
Machine	i-0e926e71eaea5d363				machine "i-0e926e71eaea5d363" has not yet joined cluster
Pod	kube-system/coredns-autoscaler-6f594f4c58-ccg5f	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-ccg5f" is pending
Pod	kube-system/coredns-f45c4bf76-jtvbm		system-cluster-critical pod "coredns-f45c4bf76-jtvbm" is pending

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

... skipping 7 lines ...
Machine	i-0904333f4b3ec64fb				machine "i-0904333f4b3ec64fb" has not yet joined cluster
Machine	i-0d96e5f5f1bf58424				machine "i-0d96e5f5f1bf58424" has not yet joined cluster
Machine	i-0e926e71eaea5d363				machine "i-0e926e71eaea5d363" has not yet joined cluster
Pod	kube-system/coredns-autoscaler-6f594f4c58-ccg5f	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-ccg5f" is pending
Pod	kube-system/coredns-f45c4bf76-jtvbm		system-cluster-critical pod "coredns-f45c4bf76-jtvbm" is pending

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

... skipping 9 lines ...
Machine	i-0e926e71eaea5d363					machine "i-0e926e71eaea5d363" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-z448b	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-z448b" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-zrwwc	system-cluster-critical pod "cert-manager-webhook-7bbf67968-zrwwc" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-ccg5f		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-ccg5f" is pending
Pod	kube-system/coredns-f45c4bf76-jtvbm			system-cluster-critical pod "coredns-f45c4bf76-jtvbm" is pending

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

... skipping 9 lines ...
Machine	i-0e926e71eaea5d363					machine "i-0e926e71eaea5d363" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-z448b	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-z448b" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-zrwwc	system-cluster-critical pod "cert-manager-webhook-7bbf67968-zrwwc" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-ccg5f		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-ccg5f" is pending
Pod	kube-system/coredns-f45c4bf76-jtvbm			system-cluster-critical pod "coredns-f45c4bf76-jtvbm" is pending

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

... skipping 9 lines ...
Machine	i-0e926e71eaea5d363					machine "i-0e926e71eaea5d363" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-z448b	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-z448b" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-zrwwc	system-cluster-critical pod "cert-manager-webhook-7bbf67968-zrwwc" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-ccg5f		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-ccg5f" is pending
Pod	kube-system/coredns-f45c4bf76-jtvbm			system-cluster-critical pod "coredns-f45c4bf76-jtvbm" is pending

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

... skipping 9 lines ...
Machine	i-0e926e71eaea5d363					machine "i-0e926e71eaea5d363" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-z448b	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-z448b" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-zrwwc	system-cluster-critical pod "cert-manager-webhook-7bbf67968-zrwwc" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-ccg5f		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-ccg5f" is pending
Pod	kube-system/coredns-f45c4bf76-jtvbm			system-cluster-critical pod "coredns-f45c4bf76-jtvbm" is pending

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

... skipping 9 lines ...
Machine	i-0e926e71eaea5d363					machine "i-0e926e71eaea5d363" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-z448b	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-z448b" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-zrwwc	system-cluster-critical pod "cert-manager-webhook-7bbf67968-zrwwc" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-ccg5f		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-ccg5f" is pending
Pod	kube-system/coredns-f45c4bf76-jtvbm			system-cluster-critical pod "coredns-f45c4bf76-jtvbm" is pending

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

... skipping 9 lines ...
Machine	i-0e926e71eaea5d363					machine "i-0e926e71eaea5d363" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-z448b	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-z448b" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-zrwwc	system-cluster-critical pod "cert-manager-webhook-7bbf67968-zrwwc" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-ccg5f		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-ccg5f" is pending
Pod	kube-system/coredns-f45c4bf76-jtvbm			system-cluster-critical pod "coredns-f45c4bf76-jtvbm" is pending

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

... skipping 12 lines ...
Pod	kube-system/coredns-autoscaler-6f594f4c58-ccg5f		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-ccg5f" is pending
Pod	kube-system/coredns-f45c4bf76-jtvbm			system-cluster-critical pod "coredns-f45c4bf76-jtvbm" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-qsfvp		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-qsfvp" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-zgctp		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-zgctp" is pending
Pod	kube-system/ebs-csi-node-d8c24				system-node-critical pod "ebs-csi-node-d8c24" is pending

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

... skipping 15 lines ...
Pod	kube-system/coredns-autoscaler-6f594f4c58-ccg5f				system-cluster-critical pod "coredns-autoscaler-6f594f4c58-ccg5f" is pending
Pod	kube-system/coredns-f45c4bf76-jtvbm					system-cluster-critical pod "coredns-f45c4bf76-jtvbm" is pending
Pod	kube-system/ebs-csi-node-bczq5						system-node-critical pod "ebs-csi-node-bczq5" is pending
Pod	kube-system/ebs-csi-node-v2gsc						system-node-critical pod "ebs-csi-node-v2gsc" is pending
Pod	kube-system/kube-proxy-ip-172-20-41-176.us-west-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-41-176.us-west-1.compute.internal" is pending

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

... skipping 23 lines ...
Pod	kube-system/ebs-csi-node-bczq5						system-node-critical pod "ebs-csi-node-bczq5" is pending
Pod	kube-system/ebs-csi-node-sn278						system-node-critical pod "ebs-csi-node-sn278" is pending
Pod	kube-system/ebs-csi-node-v2gsc						system-node-critical pod "ebs-csi-node-v2gsc" is pending
Pod	kube-system/kube-proxy-ip-172-20-42-53.us-west-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-42-53.us-west-1.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-56-114.us-west-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-56-114.us-west-1.compute.internal" is pending

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

... skipping 16 lines ...
Pod	kube-system/cert-manager-cainjector-74d69756d5-z448b	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-z448b" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-zrwwc	system-cluster-critical pod "cert-manager-webhook-7bbf67968-zrwwc" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-ccg5f		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-ccg5f" is pending
Pod	kube-system/coredns-f45c4bf76-jtvbm			system-cluster-critical pod "coredns-f45c4bf76-jtvbm" is pending
Pod	kube-system/ebs-csi-node-sn278				system-node-critical pod "ebs-csi-node-sn278" is pending

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

... skipping 12 lines ...
Pod	kube-system/calico-node-b8f79				system-node-critical pod "calico-node-b8f79" is not ready (calico-node)
Pod	kube-system/calico-node-bshjf				system-node-critical pod "calico-node-bshjf" is not ready (calico-node)
Pod	kube-system/cert-manager-webhook-7bbf67968-zrwwc	system-cluster-critical pod "cert-manager-webhook-7bbf67968-zrwwc" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-ccg5f		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-ccg5f" is pending
Pod	kube-system/coredns-f45c4bf76-jtvbm			system-cluster-critical pod "coredns-f45c4bf76-jtvbm" is pending

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

... skipping 6 lines ...
ip-172-20-56-114.us-west-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-f45c4bf76-v9t9p	system-cluster-critical pod "coredns-f45c4bf76-v9t9p" is pending

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

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

      Distro debian doesn't support ntfs -- skipping

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

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

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

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.xDG68BsTe/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.xDG68BsTe/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.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 121 lines ...
Jun 11 16:21:45.358: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail to schedule a pod which has topologies that conflict with AllowedTopologies [BeforeEach]
    /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

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

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

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

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

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

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

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

      Distro debian doesn't support ntfs -- skipping

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

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

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

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

    /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 97 lines ...
Jun 11 16:21:44.902: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-5980-e2e-scwks5l
STEP: creating a claim
Jun 11 16:21:44.955: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-jgjl
STEP: Creating a pod to test exec-volume-test
Jun 11 16:21:45.112: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-jgjl" in namespace "volume-5980" to be "Succeeded or Failed"
Jun 11 16:21:45.164: INFO: Pod "exec-volume-test-dynamicpv-jgjl": Phase="Pending", Reason="", readiness=false. Elapsed: 51.218365ms
Jun 11 16:21:47.216: INFO: Pod "exec-volume-test-dynamicpv-jgjl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.103705863s
Jun 11 16:21:49.269: INFO: Pod "exec-volume-test-dynamicpv-jgjl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.156337881s
Jun 11 16:21:51.322: INFO: Pod "exec-volume-test-dynamicpv-jgjl": Phase="Pending", Reason="", readiness=false. Elapsed: 6.209756436s
Jun 11 16:21:53.374: INFO: Pod "exec-volume-test-dynamicpv-jgjl": Phase="Pending", Reason="", readiness=false. Elapsed: 8.261974831s
Jun 11 16:21:55.427: INFO: Pod "exec-volume-test-dynamicpv-jgjl": Phase="Pending", Reason="", readiness=false. Elapsed: 10.314749795s
Jun 11 16:21:57.481: INFO: Pod "exec-volume-test-dynamicpv-jgjl": Phase="Pending", Reason="", readiness=false. Elapsed: 12.368032365s
Jun 11 16:21:59.533: INFO: Pod "exec-volume-test-dynamicpv-jgjl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.420238309s
STEP: Saw pod success
Jun 11 16:21:59.533: INFO: Pod "exec-volume-test-dynamicpv-jgjl" satisfied condition "Succeeded or Failed"
Jun 11 16:21:59.587: INFO: Trying to get logs from node ip-172-20-41-176.us-west-1.compute.internal pod exec-volume-test-dynamicpv-jgjl container exec-container-dynamicpv-jgjl: <nil>
STEP: delete the pod
Jun 11 16:21:59.714: INFO: Waiting for pod exec-volume-test-dynamicpv-jgjl to disappear
Jun 11 16:21:59.765: INFO: Pod exec-volume-test-dynamicpv-jgjl no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-jgjl
Jun 11 16:21:59.765: INFO: Deleting pod "exec-volume-test-dynamicpv-jgjl" in namespace "volume-5980"
... skipping 51 lines ...
STEP: Creating a kubernetes client
Jun 11 16:21:42.795: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename provisioning
W0611 16:21:43.640067   25997 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Jun 11 16:21:43.640: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail if subpath file is outside the volume [Slow][LinuxOnly]
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun 11 16:21:43.741: INFO: Creating resource for dynamic PV
Jun 11 16:21:43.741: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1421-e2e-sczhq5f
STEP: creating a claim
Jun 11 16:21:43.793: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-rlrt
STEP: Checking for subpath error in container status
Jun 11 16:22:12.060: INFO: Deleting pod "pod-subpath-test-dynamicpv-rlrt" in namespace "provisioning-1421"
Jun 11 16:22:12.119: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-rlrt" to be fully deleted
STEP: Deleting pod
Jun 11 16:22:22.224: INFO: Deleting pod "pod-subpath-test-dynamicpv-rlrt" in namespace "provisioning-1421"
STEP: Deleting pvc
Jun 11 16:22:22.387: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com8tdl8"
... skipping 12 lines ...

• [SLOW TEST:60.119 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath file is outside the volume [Slow][LinuxOnly]
    /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Dynamic Snapshot (retain policy)] snapshottable-stress[Feature:VolumeSnapshotDataSource]
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 11 16:22:42.916: INFO: Driver ebs.csi.aws.com doesn't specify snapshot stress test options -- skipping
[AfterEach] [Testpattern: Dynamic Snapshot (retain policy)] snapshottable-stress[Feature:VolumeSnapshotDataSource]
... skipping 38 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 16:21:43.563: 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.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun 11 16:21:45.988: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 11 16:21:45.988: INFO: Creating resource for dynamic PV
Jun 11 16:21:45.988: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7178xhqdz
STEP: creating a claim
Jun 11 16:21:46.040: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-cfdn
STEP: Checking for subpath error in container status
Jun 11 16:22:12.301: INFO: Deleting pod "pod-subpath-test-dynamicpv-cfdn" in namespace "provisioning-7178"
Jun 11 16:22:12.353: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-cfdn" to be fully deleted
STEP: Deleting pod
Jun 11 16:22:22.455: INFO: Deleting pod "pod-subpath-test-dynamicpv-cfdn" in namespace "provisioning-7178"
STEP: Deleting pvc
Jun 11 16:22:22.606: INFO: Deleting PersistentVolumeClaim "awsswj2m"
... skipping 14 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.xDG68BsTe/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.xDG68BsTe/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.xDG68BsTe/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.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [sig-storage] Storage Policy Based Volume Provisioning [Feature:vsphere]
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 16:22:42.920: INFO: >>> kubeConfig: /root/.kube/config
... skipping 80 lines ...
Jun 11 16:21:44.543: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9464-e2e-sc5vj4g
STEP: creating a claim
Jun 11 16:21:44.597: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-dddb
STEP: Creating a pod to test subpath
Jun 11 16:21:44.755: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-dddb" in namespace "provisioning-9464" to be "Succeeded or Failed"
Jun 11 16:21:44.813: INFO: Pod "pod-subpath-test-dynamicpv-dddb": Phase="Pending", Reason="", readiness=false. Elapsed: 58.079281ms
Jun 11 16:21:46.872: INFO: Pod "pod-subpath-test-dynamicpv-dddb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.116770786s
Jun 11 16:21:48.924: INFO: Pod "pod-subpath-test-dynamicpv-dddb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.168689268s
Jun 11 16:21:50.983: INFO: Pod "pod-subpath-test-dynamicpv-dddb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.227483957s
Jun 11 16:21:53.035: INFO: Pod "pod-subpath-test-dynamicpv-dddb": Phase="Pending", Reason="", readiness=false. Elapsed: 8.279430932s
Jun 11 16:21:55.087: INFO: Pod "pod-subpath-test-dynamicpv-dddb": Phase="Pending", Reason="", readiness=false. Elapsed: 10.331561329s
Jun 11 16:21:57.158: INFO: Pod "pod-subpath-test-dynamicpv-dddb": Phase="Pending", Reason="", readiness=false. Elapsed: 12.4025013s
Jun 11 16:21:59.209: INFO: Pod "pod-subpath-test-dynamicpv-dddb": Phase="Pending", Reason="", readiness=false. Elapsed: 14.453936363s
Jun 11 16:22:01.263: INFO: Pod "pod-subpath-test-dynamicpv-dddb": Phase="Pending", Reason="", readiness=false. Elapsed: 16.507398731s
Jun 11 16:22:03.314: INFO: Pod "pod-subpath-test-dynamicpv-dddb": Phase="Pending", Reason="", readiness=false. Elapsed: 18.559071319s
Jun 11 16:22:05.367: INFO: Pod "pod-subpath-test-dynamicpv-dddb": Phase="Pending", Reason="", readiness=false. Elapsed: 20.612040647s
Jun 11 16:22:07.420: INFO: Pod "pod-subpath-test-dynamicpv-dddb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.665000128s
STEP: Saw pod success
Jun 11 16:22:07.420: INFO: Pod "pod-subpath-test-dynamicpv-dddb" satisfied condition "Succeeded or Failed"
Jun 11 16:22:07.472: INFO: Trying to get logs from node ip-172-20-40-55.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-dddb container test-container-volume-dynamicpv-dddb: <nil>
STEP: delete the pod
Jun 11 16:22:07.593: INFO: Waiting for pod pod-subpath-test-dynamicpv-dddb to disappear
Jun 11 16:22:07.644: INFO: Pod pod-subpath-test-dynamicpv-dddb no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-dddb
Jun 11 16:22:07.644: INFO: Deleting pod "pod-subpath-test-dynamicpv-dddb" in namespace "provisioning-9464"
... skipping 148 lines ...
Jun 11 16:21:43.034: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7194qtd2j
STEP: creating a claim
Jun 11 16:21:43.087: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-m2p4
STEP: Creating a pod to test subpath
Jun 11 16:21:43.262: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-m2p4" in namespace "provisioning-7194" to be "Succeeded or Failed"
Jun 11 16:21:43.313: INFO: Pod "pod-subpath-test-dynamicpv-m2p4": Phase="Pending", Reason="", readiness=false. Elapsed: 50.966708ms
Jun 11 16:21:45.364: INFO: Pod "pod-subpath-test-dynamicpv-m2p4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.102569344s
Jun 11 16:21:47.417: INFO: Pod "pod-subpath-test-dynamicpv-m2p4": Phase="Pending", Reason="", readiness=false. Elapsed: 4.154711957s
Jun 11 16:21:49.468: INFO: Pod "pod-subpath-test-dynamicpv-m2p4": Phase="Pending", Reason="", readiness=false. Elapsed: 6.206646963s
Jun 11 16:21:51.521: INFO: Pod "pod-subpath-test-dynamicpv-m2p4": Phase="Pending", Reason="", readiness=false. Elapsed: 8.259331101s
Jun 11 16:21:53.573: INFO: Pod "pod-subpath-test-dynamicpv-m2p4": Phase="Pending", Reason="", readiness=false. Elapsed: 10.311291611s
... skipping 2 lines ...
Jun 11 16:21:59.734: INFO: Pod "pod-subpath-test-dynamicpv-m2p4": Phase="Pending", Reason="", readiness=false. Elapsed: 16.472012728s
Jun 11 16:22:01.789: INFO: Pod "pod-subpath-test-dynamicpv-m2p4": Phase="Pending", Reason="", readiness=false. Elapsed: 18.52756415s
Jun 11 16:22:03.844: INFO: Pod "pod-subpath-test-dynamicpv-m2p4": Phase="Pending", Reason="", readiness=false. Elapsed: 20.582466481s
Jun 11 16:22:05.896: INFO: Pod "pod-subpath-test-dynamicpv-m2p4": Phase="Pending", Reason="", readiness=false. Elapsed: 22.634350189s
Jun 11 16:22:07.950: INFO: Pod "pod-subpath-test-dynamicpv-m2p4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.688186028s
STEP: Saw pod success
Jun 11 16:22:07.950: INFO: Pod "pod-subpath-test-dynamicpv-m2p4" satisfied condition "Succeeded or Failed"
Jun 11 16:22:08.001: INFO: Trying to get logs from node ip-172-20-56-114.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-m2p4 container test-container-subpath-dynamicpv-m2p4: <nil>
STEP: delete the pod
Jun 11 16:22:08.640: INFO: Waiting for pod pod-subpath-test-dynamicpv-m2p4 to disappear
Jun 11 16:22:08.691: INFO: Pod pod-subpath-test-dynamicpv-m2p4 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-m2p4
Jun 11 16:22:08.691: INFO: Deleting pod "pod-subpath-test-dynamicpv-m2p4" in namespace "provisioning-7194"
... skipping 68 lines ...
Jun 11 16:21:45.291: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4517-e2e-scrkmrd
STEP: creating a claim
Jun 11 16:21:45.346: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-75wm
STEP: Creating a pod to test subpath
Jun 11 16:21:45.504: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-75wm" in namespace "provisioning-4517" to be "Succeeded or Failed"
Jun 11 16:21:45.556: INFO: Pod "pod-subpath-test-dynamicpv-75wm": Phase="Pending", Reason="", readiness=false. Elapsed: 51.397638ms
Jun 11 16:21:47.607: INFO: Pod "pod-subpath-test-dynamicpv-75wm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.102800192s
Jun 11 16:21:49.660: INFO: Pod "pod-subpath-test-dynamicpv-75wm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.155404902s
Jun 11 16:21:51.712: INFO: Pod "pod-subpath-test-dynamicpv-75wm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.207531928s
Jun 11 16:21:53.764: INFO: Pod "pod-subpath-test-dynamicpv-75wm": Phase="Pending", Reason="", readiness=false. Elapsed: 8.259538368s
Jun 11 16:21:55.816: INFO: Pod "pod-subpath-test-dynamicpv-75wm": Phase="Pending", Reason="", readiness=false. Elapsed: 10.311494773s
... skipping 2 lines ...
Jun 11 16:22:01.973: INFO: Pod "pod-subpath-test-dynamicpv-75wm": Phase="Pending", Reason="", readiness=false. Elapsed: 16.468522584s
Jun 11 16:22:04.024: INFO: Pod "pod-subpath-test-dynamicpv-75wm": Phase="Pending", Reason="", readiness=false. Elapsed: 18.520220696s
Jun 11 16:22:06.077: INFO: Pod "pod-subpath-test-dynamicpv-75wm": Phase="Pending", Reason="", readiness=false. Elapsed: 20.572870457s
Jun 11 16:22:08.131: INFO: Pod "pod-subpath-test-dynamicpv-75wm": Phase="Pending", Reason="", readiness=false. Elapsed: 22.627061173s
Jun 11 16:22:10.184: INFO: Pod "pod-subpath-test-dynamicpv-75wm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.679992327s
STEP: Saw pod success
Jun 11 16:22:10.184: INFO: Pod "pod-subpath-test-dynamicpv-75wm" satisfied condition "Succeeded or Failed"
Jun 11 16:22:10.236: INFO: Trying to get logs from node ip-172-20-56-114.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-75wm container test-container-volume-dynamicpv-75wm: <nil>
STEP: delete the pod
Jun 11 16:22:10.349: INFO: Waiting for pod pod-subpath-test-dynamicpv-75wm to disappear
Jun 11 16:22:10.400: INFO: Pod pod-subpath-test-dynamicpv-75wm no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-75wm
Jun 11 16:22:10.400: INFO: Deleting pod "pod-subpath-test-dynamicpv-75wm" in namespace "provisioning-4517"
... skipping 112 lines ...
Jun 11 16:21:46.340: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-166-e2e-scq9ckn
STEP: creating a claim
Jun 11 16:21:46.393: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-7sw6
STEP: Creating a pod to test exec-volume-test
Jun 11 16:21:46.550: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-7sw6" in namespace "volume-166" to be "Succeeded or Failed"
Jun 11 16:21:46.601: INFO: Pod "exec-volume-test-dynamicpv-7sw6": Phase="Pending", Reason="", readiness=false. Elapsed: 51.003669ms
Jun 11 16:21:48.653: INFO: Pod "exec-volume-test-dynamicpv-7sw6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.102636845s
Jun 11 16:21:50.708: INFO: Pod "exec-volume-test-dynamicpv-7sw6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.157571845s
Jun 11 16:21:52.760: INFO: Pod "exec-volume-test-dynamicpv-7sw6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.209360696s
Jun 11 16:21:54.812: INFO: Pod "exec-volume-test-dynamicpv-7sw6": Phase="Pending", Reason="", readiness=false. Elapsed: 8.26209944s
Jun 11 16:21:56.864: INFO: Pod "exec-volume-test-dynamicpv-7sw6": Phase="Pending", Reason="", readiness=false. Elapsed: 10.313660011s
... skipping 2 lines ...
Jun 11 16:22:03.020: INFO: Pod "exec-volume-test-dynamicpv-7sw6": Phase="Pending", Reason="", readiness=false. Elapsed: 16.469473027s
Jun 11 16:22:05.071: INFO: Pod "exec-volume-test-dynamicpv-7sw6": Phase="Pending", Reason="", readiness=false. Elapsed: 18.521142558s
Jun 11 16:22:07.125: INFO: Pod "exec-volume-test-dynamicpv-7sw6": Phase="Pending", Reason="", readiness=false. Elapsed: 20.574741287s
Jun 11 16:22:09.177: INFO: Pod "exec-volume-test-dynamicpv-7sw6": Phase="Pending", Reason="", readiness=false. Elapsed: 22.627290495s
Jun 11 16:22:11.229: INFO: Pod "exec-volume-test-dynamicpv-7sw6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.6791111s
STEP: Saw pod success
Jun 11 16:22:11.229: INFO: Pod "exec-volume-test-dynamicpv-7sw6" satisfied condition "Succeeded or Failed"
Jun 11 16:22:11.281: INFO: Trying to get logs from node ip-172-20-41-176.us-west-1.compute.internal pod exec-volume-test-dynamicpv-7sw6 container exec-container-dynamicpv-7sw6: <nil>
STEP: delete the pod
Jun 11 16:22:11.394: INFO: Waiting for pod exec-volume-test-dynamicpv-7sw6 to disappear
Jun 11 16:22:11.445: INFO: Pod exec-volume-test-dynamicpv-7sw6 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-7sw6
Jun 11 16:22:11.446: INFO: Deleting pod "exec-volume-test-dynamicpv-7sw6" in namespace "volume-166"
... skipping 209 lines ...
Jun 11 16:21:53.992: INFO: PersistentVolumeClaim pvc-knmrs found but phase is Pending instead of Bound.
Jun 11 16:21:56.044: INFO: PersistentVolumeClaim pvc-knmrs found and phase=Bound (8.25918156s)
Jun 11 16:21:56.044: INFO: Waiting up to 3m0s for PersistentVolume aws-gdw8j to have phase Bound
Jun 11 16:21:56.095: INFO: PersistentVolume aws-gdw8j found and phase=Bound (51.088314ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-kkbv
STEP: Creating a pod to test exec-volume-test
Jun 11 16:21:56.250: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-kkbv" in namespace "volume-8295" to be "Succeeded or Failed"
Jun 11 16:21:56.301: INFO: Pod "exec-volume-test-preprovisionedpv-kkbv": Phase="Pending", Reason="", readiness=false. Elapsed: 51.39482ms
Jun 11 16:21:58.353: INFO: Pod "exec-volume-test-preprovisionedpv-kkbv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.102760318s
Jun 11 16:22:00.404: INFO: Pod "exec-volume-test-preprovisionedpv-kkbv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.154243994s
Jun 11 16:22:02.456: INFO: Pod "exec-volume-test-preprovisionedpv-kkbv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.205886805s
Jun 11 16:22:04.509: INFO: Pod "exec-volume-test-preprovisionedpv-kkbv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.258748465s
Jun 11 16:22:06.561: INFO: Pod "exec-volume-test-preprovisionedpv-kkbv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.311413414s
... skipping 3 lines ...
Jun 11 16:22:14.787: INFO: Pod "exec-volume-test-preprovisionedpv-kkbv": Phase="Pending", Reason="", readiness=false. Elapsed: 18.536920155s
Jun 11 16:22:16.840: INFO: Pod "exec-volume-test-preprovisionedpv-kkbv": Phase="Pending", Reason="", readiness=false. Elapsed: 20.589828761s
Jun 11 16:22:18.892: INFO: Pod "exec-volume-test-preprovisionedpv-kkbv": Phase="Pending", Reason="", readiness=false. Elapsed: 22.641706605s
Jun 11 16:22:20.944: INFO: Pod "exec-volume-test-preprovisionedpv-kkbv": Phase="Pending", Reason="", readiness=false. Elapsed: 24.694451201s
Jun 11 16:22:22.996: INFO: Pod "exec-volume-test-preprovisionedpv-kkbv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.746364932s
STEP: Saw pod success
Jun 11 16:22:22.996: INFO: Pod "exec-volume-test-preprovisionedpv-kkbv" satisfied condition "Succeeded or Failed"
Jun 11 16:22:23.048: INFO: Trying to get logs from node ip-172-20-42-53.us-west-1.compute.internal pod exec-volume-test-preprovisionedpv-kkbv container exec-container-preprovisionedpv-kkbv: <nil>
STEP: delete the pod
Jun 11 16:22:23.526: INFO: Waiting for pod exec-volume-test-preprovisionedpv-kkbv to disappear
Jun 11 16:22:23.578: INFO: Pod exec-volume-test-preprovisionedpv-kkbv no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-kkbv
Jun 11 16:22:23.578: INFO: Deleting pod "exec-volume-test-preprovisionedpv-kkbv" in namespace "volume-8295"
STEP: Deleting pv and pvc
Jun 11 16:22:23.629: INFO: Deleting PersistentVolumeClaim "pvc-knmrs"
Jun 11 16:22:23.698: INFO: Deleting PersistentVolume "aws-gdw8j"
Jun 11 16:22:23.929: INFO: Couldn't delete PD "aws://us-west-1a/vol-07377601ec2155ddc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07377601ec2155ddc is currently attached to i-02fd57ac3b1f478ed
	status code: 400, request id: 7859ab01-09c6-493c-9d0a-5a0c90a30308
Jun 11 16:22:29.298: INFO: Couldn't delete PD "aws://us-west-1a/vol-07377601ec2155ddc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07377601ec2155ddc is currently attached to i-02fd57ac3b1f478ed
	status code: 400, request id: 950f1887-1ee9-4e80-8df5-73038988ec03
Jun 11 16:22:34.664: INFO: Couldn't delete PD "aws://us-west-1a/vol-07377601ec2155ddc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07377601ec2155ddc is currently attached to i-02fd57ac3b1f478ed
	status code: 400, request id: 8a26c45e-3f41-4410-b454-0142174306e5
Jun 11 16:22:40.031: INFO: Couldn't delete PD "aws://us-west-1a/vol-07377601ec2155ddc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07377601ec2155ddc is currently attached to i-02fd57ac3b1f478ed
	status code: 400, request id: 54324898-cc7f-4c48-8103-af6afe5178b4
Jun 11 16:22:45.424: INFO: Couldn't delete PD "aws://us-west-1a/vol-07377601ec2155ddc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07377601ec2155ddc is currently attached to i-02fd57ac3b1f478ed
	status code: 400, request id: 56822904-9a58-42b3-ad23-8f131c178363
Jun 11 16:22:50.745: INFO: Couldn't delete PD "aws://us-west-1a/vol-07377601ec2155ddc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07377601ec2155ddc is currently attached to i-02fd57ac3b1f478ed
	status code: 400, request id: b682705d-83a3-4eb1-a2e0-7765e71ff58b
Jun 11 16:22:56.098: INFO: Successfully deleted PD "aws://us-west-1a/vol-07377601ec2155ddc".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 16:22:56.098: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8295" for this suite.
... skipping 16 lines ...
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 16:22:56.212: 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.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Jun 11 16:22:56.524: INFO: found topology map[topology.kubernetes.io/zone:us-west-1a]
Jun 11 16:22:56.524: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 11 16:22:56.524: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.xDG68BsTe/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.xDG68BsTe/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (immediate binding)] topology
    /tmp/kops.xDG68BsTe/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.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 57 lines ...
Jun 11 16:21:46.042: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2917-e2e-sc5lnl6
STEP: creating a claim
Jun 11 16:21:46.096: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-b622
STEP: Creating a pod to test subpath
Jun 11 16:21:46.256: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-b622" in namespace "provisioning-2917" to be "Succeeded or Failed"
Jun 11 16:21:46.308: INFO: Pod "pod-subpath-test-dynamicpv-b622": Phase="Pending", Reason="", readiness=false. Elapsed: 51.962145ms
Jun 11 16:21:48.365: INFO: Pod "pod-subpath-test-dynamicpv-b622": Phase="Pending", Reason="", readiness=false. Elapsed: 2.108976803s
Jun 11 16:21:50.428: INFO: Pod "pod-subpath-test-dynamicpv-b622": Phase="Pending", Reason="", readiness=false. Elapsed: 4.171377942s
Jun 11 16:21:52.481: INFO: Pod "pod-subpath-test-dynamicpv-b622": Phase="Pending", Reason="", readiness=false. Elapsed: 6.224959959s
Jun 11 16:21:54.534: INFO: Pod "pod-subpath-test-dynamicpv-b622": Phase="Pending", Reason="", readiness=false. Elapsed: 8.277963394s
Jun 11 16:21:56.589: INFO: Pod "pod-subpath-test-dynamicpv-b622": Phase="Pending", Reason="", readiness=false. Elapsed: 10.332597484s
Jun 11 16:21:58.643: INFO: Pod "pod-subpath-test-dynamicpv-b622": Phase="Pending", Reason="", readiness=false. Elapsed: 12.386304762s
Jun 11 16:22:00.695: INFO: Pod "pod-subpath-test-dynamicpv-b622": Phase="Pending", Reason="", readiness=false. Elapsed: 14.438874556s
Jun 11 16:22:02.749: INFO: Pod "pod-subpath-test-dynamicpv-b622": Phase="Pending", Reason="", readiness=false. Elapsed: 16.492654374s
Jun 11 16:22:04.802: INFO: Pod "pod-subpath-test-dynamicpv-b622": Phase="Pending", Reason="", readiness=false. Elapsed: 18.545342453s
Jun 11 16:22:06.855: INFO: Pod "pod-subpath-test-dynamicpv-b622": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.598552087s
STEP: Saw pod success
Jun 11 16:22:06.855: INFO: Pod "pod-subpath-test-dynamicpv-b622" satisfied condition "Succeeded or Failed"
Jun 11 16:22:06.908: INFO: Trying to get logs from node ip-172-20-40-55.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-b622 container test-container-subpath-dynamicpv-b622: <nil>
STEP: delete the pod
Jun 11 16:22:07.037: INFO: Waiting for pod pod-subpath-test-dynamicpv-b622 to disappear
Jun 11 16:22:07.089: INFO: Pod pod-subpath-test-dynamicpv-b622 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-b622
Jun 11 16:22:07.089: INFO: Deleting pod "pod-subpath-test-dynamicpv-b622" in namespace "provisioning-2917"
STEP: Creating pod pod-subpath-test-dynamicpv-b622
STEP: Creating a pod to test subpath
Jun 11 16:22:07.195: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-b622" in namespace "provisioning-2917" to be "Succeeded or Failed"
Jun 11 16:22:07.247: INFO: Pod "pod-subpath-test-dynamicpv-b622": Phase="Pending", Reason="", readiness=false. Elapsed: 51.776312ms
Jun 11 16:22:09.299: INFO: Pod "pod-subpath-test-dynamicpv-b622": Phase="Pending", Reason="", readiness=false. Elapsed: 2.104514141s
Jun 11 16:22:11.352: INFO: Pod "pod-subpath-test-dynamicpv-b622": Phase="Pending", Reason="", readiness=false. Elapsed: 4.157288841s
Jun 11 16:22:13.405: INFO: Pod "pod-subpath-test-dynamicpv-b622": Phase="Pending", Reason="", readiness=false. Elapsed: 6.209752831s
Jun 11 16:22:15.459: INFO: Pod "pod-subpath-test-dynamicpv-b622": Phase="Pending", Reason="", readiness=false. Elapsed: 8.263887298s
Jun 11 16:22:17.512: INFO: Pod "pod-subpath-test-dynamicpv-b622": Phase="Pending", Reason="", readiness=false. Elapsed: 10.317448512s
Jun 11 16:22:19.566: INFO: Pod "pod-subpath-test-dynamicpv-b622": Phase="Pending", Reason="", readiness=false. Elapsed: 12.37162626s
Jun 11 16:22:21.619: INFO: Pod "pod-subpath-test-dynamicpv-b622": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.424443346s
STEP: Saw pod success
Jun 11 16:22:21.619: INFO: Pod "pod-subpath-test-dynamicpv-b622" satisfied condition "Succeeded or Failed"
Jun 11 16:22:21.671: INFO: Trying to get logs from node ip-172-20-40-55.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-b622 container test-container-subpath-dynamicpv-b622: <nil>
STEP: delete the pod
Jun 11 16:22:21.786: INFO: Waiting for pod pod-subpath-test-dynamicpv-b622 to disappear
Jun 11 16:22:21.838: INFO: Pod pod-subpath-test-dynamicpv-b622 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-b622
Jun 11 16:22:21.838: INFO: Deleting pod "pod-subpath-test-dynamicpv-b622" in namespace "provisioning-2917"
... skipping 70 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 16:21:45.407: 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.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun 11 16:21:46.792: INFO: Creating resource for dynamic PV
Jun 11 16:21:46.792: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7956-e2e-scmqxrk
STEP: creating a claim
Jun 11 16:21:46.868: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-jcrk
STEP: Checking for subpath error in container status
Jun 11 16:22:19.154: INFO: Deleting pod "pod-subpath-test-dynamicpv-jcrk" in namespace "provisioning-7956"
Jun 11 16:22:19.207: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-jcrk" to be fully deleted
STEP: Deleting pod
Jun 11 16:22:25.316: INFO: Deleting pod "pod-subpath-test-dynamicpv-jcrk" in namespace "provisioning-7956"
STEP: Deleting pvc
Jun 11 16:22:25.482: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comznvl6"
... skipping 15 lines ...

• [SLOW TEST:75.726 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath directory is outside the volume [Slow][LinuxOnly]
    /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [sig-storage] Zone Support [Feature:vsphere]
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 16:23:01.135: INFO: >>> kubeConfig: /root/.kube/config
... skipping 331 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.xDG68BsTe/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.xDG68BsTe/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.xDG68BsTe/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.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Distro debian doesn't support ntfs -- skipping

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 40 lines ...
Jun 11 16:21:43.191: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3881-e2e-sccwrsj
STEP: creating a claim
Jun 11 16:21:43.253: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-nngs
STEP: Creating a pod to test atomic-volume-subpath
Jun 11 16:21:43.428: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-nngs" in namespace "provisioning-3881" to be "Succeeded or Failed"
Jun 11 16:21:43.482: INFO: Pod "pod-subpath-test-dynamicpv-nngs": Phase="Pending", Reason="", readiness=false. Elapsed: 53.201145ms
Jun 11 16:21:45.535: INFO: Pod "pod-subpath-test-dynamicpv-nngs": Phase="Pending", Reason="", readiness=false. Elapsed: 2.106494262s
Jun 11 16:21:47.588: INFO: Pod "pod-subpath-test-dynamicpv-nngs": Phase="Pending", Reason="", readiness=false. Elapsed: 4.159758249s
Jun 11 16:21:49.643: INFO: Pod "pod-subpath-test-dynamicpv-nngs": Phase="Pending", Reason="", readiness=false. Elapsed: 6.214131788s
Jun 11 16:21:51.696: INFO: Pod "pod-subpath-test-dynamicpv-nngs": Phase="Pending", Reason="", readiness=false. Elapsed: 8.267783896s
Jun 11 16:21:53.752: INFO: Pod "pod-subpath-test-dynamicpv-nngs": Phase="Pending", Reason="", readiness=false. Elapsed: 10.323149351s
... skipping 18 lines ...
Jun 11 16:22:32.765: INFO: Pod "pod-subpath-test-dynamicpv-nngs": Phase="Running", Reason="", readiness=true. Elapsed: 49.336194845s
Jun 11 16:22:34.818: INFO: Pod "pod-subpath-test-dynamicpv-nngs": Phase="Running", Reason="", readiness=true. Elapsed: 51.389987293s
Jun 11 16:22:36.872: INFO: Pod "pod-subpath-test-dynamicpv-nngs": Phase="Running", Reason="", readiness=true. Elapsed: 53.443236304s
Jun 11 16:22:38.926: INFO: Pod "pod-subpath-test-dynamicpv-nngs": Phase="Running", Reason="", readiness=true. Elapsed: 55.497847885s
Jun 11 16:22:40.979: INFO: Pod "pod-subpath-test-dynamicpv-nngs": Phase="Succeeded", Reason="", readiness=false. Elapsed: 57.550518291s
STEP: Saw pod success
Jun 11 16:22:40.979: INFO: Pod "pod-subpath-test-dynamicpv-nngs" satisfied condition "Succeeded or Failed"
Jun 11 16:22:41.052: INFO: Trying to get logs from node ip-172-20-42-53.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-nngs container test-container-subpath-dynamicpv-nngs: <nil>
STEP: delete the pod
Jun 11 16:22:41.166: INFO: Waiting for pod pod-subpath-test-dynamicpv-nngs to disappear
Jun 11 16:22:41.218: INFO: Pod pod-subpath-test-dynamicpv-nngs no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-nngs
Jun 11 16:22:41.218: INFO: Deleting pod "pod-subpath-test-dynamicpv-nngs" in namespace "provisioning-3881"
... skipping 165 lines ...
Jun 11 16:23:11.562: INFO: Waiting for pod aws-client to disappear
Jun 11 16:23:11.614: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 11 16:23:11.614: INFO: Deleting PersistentVolumeClaim "pvc-pwcm2"
Jun 11 16:23:11.666: INFO: Deleting PersistentVolume "aws-hvknt"
Jun 11 16:23:12.075: INFO: Couldn't delete PD "aws://us-west-1a/vol-0f2999880cf93aaf1", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f2999880cf93aaf1 is currently attached to i-0e926e71eaea5d363
	status code: 400, request id: c2de384f-de3d-43c5-aa5d-803b1df15ced
Jun 11 16:23:17.425: INFO: Successfully deleted PD "aws://us-west-1a/vol-0f2999880cf93aaf1".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumes
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 16:23:17.425: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-3248" for this suite.
... skipping 135 lines ...
Jun 11 16:23:04.808: INFO: Pod aws-client still exists
Jun 11 16:23:06.756: INFO: Waiting for pod aws-client to disappear
Jun 11 16:23:06.808: INFO: Pod aws-client still exists
Jun 11 16:23:08.757: INFO: Waiting for pod aws-client to disappear
Jun 11 16:23:08.809: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun 11 16:23:09.204: INFO: Couldn't delete PD "aws://us-west-1a/vol-041c2761e195c599d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-041c2761e195c599d is currently attached to i-0d96e5f5f1bf58424
	status code: 400, request id: c92cdc1b-38b4-4ba3-bb11-0f444c5841a2
Jun 11 16:23:14.527: INFO: Couldn't delete PD "aws://us-west-1a/vol-041c2761e195c599d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-041c2761e195c599d is currently attached to i-0d96e5f5f1bf58424
	status code: 400, request id: 2253e3fb-246e-4ff2-b9c3-e2331c7ba262
Jun 11 16:23:19.894: INFO: Couldn't delete PD "aws://us-west-1a/vol-041c2761e195c599d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-041c2761e195c599d is currently attached to i-0d96e5f5f1bf58424
	status code: 400, request id: 78c7e9b1-ee56-4715-b1ff-9c1cc9ebda9a
Jun 11 16:23:25.241: INFO: Successfully deleted PD "aws://us-west-1a/vol-041c2761e195c599d".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 16:23:25.241: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-1897" for this suite.
... skipping 24 lines ...
Jun 11 16:22:44.523: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7949df7wf
STEP: creating a claim
Jun 11 16:22:44.573: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-zr77
STEP: Creating a pod to test subpath
Jun 11 16:22:44.737: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-zr77" in namespace "provisioning-7949" to be "Succeeded or Failed"
Jun 11 16:22:44.787: INFO: Pod "pod-subpath-test-dynamicpv-zr77": Phase="Pending", Reason="", readiness=false. Elapsed: 50.31905ms
Jun 11 16:22:46.838: INFO: Pod "pod-subpath-test-dynamicpv-zr77": Phase="Pending", Reason="", readiness=false. Elapsed: 2.100916939s
Jun 11 16:22:48.892: INFO: Pod "pod-subpath-test-dynamicpv-zr77": Phase="Pending", Reason="", readiness=false. Elapsed: 4.154521738s
Jun 11 16:22:50.944: INFO: Pod "pod-subpath-test-dynamicpv-zr77": Phase="Pending", Reason="", readiness=false. Elapsed: 6.207322466s
Jun 11 16:22:53.002: INFO: Pod "pod-subpath-test-dynamicpv-zr77": Phase="Pending", Reason="", readiness=false. Elapsed: 8.264937009s
Jun 11 16:22:55.053: INFO: Pod "pod-subpath-test-dynamicpv-zr77": Phase="Pending", Reason="", readiness=false. Elapsed: 10.315659785s
... skipping 3 lines ...
Jun 11 16:23:03.258: INFO: Pod "pod-subpath-test-dynamicpv-zr77": Phase="Pending", Reason="", readiness=false. Elapsed: 18.521035834s
Jun 11 16:23:05.310: INFO: Pod "pod-subpath-test-dynamicpv-zr77": Phase="Pending", Reason="", readiness=false. Elapsed: 20.572894004s
Jun 11 16:23:07.361: INFO: Pod "pod-subpath-test-dynamicpv-zr77": Phase="Pending", Reason="", readiness=false. Elapsed: 22.623719738s
Jun 11 16:23:09.412: INFO: Pod "pod-subpath-test-dynamicpv-zr77": Phase="Pending", Reason="", readiness=false. Elapsed: 24.675155462s
Jun 11 16:23:11.464: INFO: Pod "pod-subpath-test-dynamicpv-zr77": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.726886288s
STEP: Saw pod success
Jun 11 16:23:11.464: INFO: Pod "pod-subpath-test-dynamicpv-zr77" satisfied condition "Succeeded or Failed"
Jun 11 16:23:11.515: INFO: Trying to get logs from node ip-172-20-42-53.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-zr77 container test-container-volume-dynamicpv-zr77: <nil>
STEP: delete the pod
Jun 11 16:23:11.624: INFO: Waiting for pod pod-subpath-test-dynamicpv-zr77 to disappear
Jun 11 16:23:11.678: INFO: Pod pod-subpath-test-dynamicpv-zr77 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-zr77
Jun 11 16:23:11.678: INFO: Deleting pod "pod-subpath-test-dynamicpv-zr77" in namespace "provisioning-7949"
... skipping 267 lines ...
Jun 11 16:23:01.769: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-675v67sl
STEP: creating a claim
Jun 11 16:23:01.823: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-ngxk
STEP: Creating a pod to test subpath
Jun 11 16:23:01.982: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-ngxk" in namespace "provisioning-675" to be "Succeeded or Failed"
Jun 11 16:23:02.034: INFO: Pod "pod-subpath-test-dynamicpv-ngxk": Phase="Pending", Reason="", readiness=false. Elapsed: 52.031621ms
Jun 11 16:23:04.087: INFO: Pod "pod-subpath-test-dynamicpv-ngxk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.104687208s
Jun 11 16:23:06.155: INFO: Pod "pod-subpath-test-dynamicpv-ngxk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.172604148s
Jun 11 16:23:08.208: INFO: Pod "pod-subpath-test-dynamicpv-ngxk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.225303335s
Jun 11 16:23:10.261: INFO: Pod "pod-subpath-test-dynamicpv-ngxk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.278687358s
Jun 11 16:23:12.314: INFO: Pod "pod-subpath-test-dynamicpv-ngxk": Phase="Pending", Reason="", readiness=false. Elapsed: 10.332005532s
Jun 11 16:23:14.367: INFO: Pod "pod-subpath-test-dynamicpv-ngxk": Phase="Pending", Reason="", readiness=false. Elapsed: 12.38497482s
Jun 11 16:23:16.421: INFO: Pod "pod-subpath-test-dynamicpv-ngxk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.438110343s
STEP: Saw pod success
Jun 11 16:23:16.421: INFO: Pod "pod-subpath-test-dynamicpv-ngxk" satisfied condition "Succeeded or Failed"
Jun 11 16:23:16.472: INFO: Trying to get logs from node ip-172-20-41-176.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-ngxk container test-container-volume-dynamicpv-ngxk: <nil>
STEP: delete the pod
Jun 11 16:23:16.585: INFO: Waiting for pod pod-subpath-test-dynamicpv-ngxk to disappear
Jun 11 16:23:16.637: INFO: Pod pod-subpath-test-dynamicpv-ngxk no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-ngxk
Jun 11 16:23:16.637: INFO: Deleting pod "pod-subpath-test-dynamicpv-ngxk" in namespace "provisioning-675"
... skipping 267 lines ...

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

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

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

    /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 37 lines ...
STEP: Deleting pod hostexec-ip-172-20-40-55.us-west-1.compute.internal-jkmth in namespace volumemode-3715
Jun 11 16:23:30.914: INFO: Deleting pod "pod-6229570b-e5c0-45e1-861f-4e341ac6fc86" in namespace "volumemode-3715"
Jun 11 16:23:30.967: INFO: Wait up to 5m0s for pod "pod-6229570b-e5c0-45e1-861f-4e341ac6fc86" to be fully deleted
STEP: Deleting pv and pvc
Jun 11 16:23:37.074: INFO: Deleting PersistentVolumeClaim "pvc-jblcm"
Jun 11 16:23:37.127: INFO: Deleting PersistentVolume "aws-57xcr"
Jun 11 16:23:37.344: INFO: Couldn't delete PD "aws://us-west-1a/vol-0de7488a1d49d6138", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0de7488a1d49d6138 is currently attached to i-0904333f4b3ec64fb
	status code: 400, request id: bee85f9e-1cf8-45a1-b7b3-cc1a9189b69f
Jun 11 16:23:42.675: INFO: Couldn't delete PD "aws://us-west-1a/vol-0de7488a1d49d6138", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0de7488a1d49d6138 is currently attached to i-0904333f4b3ec64fb
	status code: 400, request id: 2aa7be87-48fd-4d5f-a1a1-f39943ec6378
Jun 11 16:23:48.018: INFO: Couldn't delete PD "aws://us-west-1a/vol-0de7488a1d49d6138", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0de7488a1d49d6138 is currently attached to i-0904333f4b3ec64fb
	status code: 400, request id: b56c9680-ddc4-461e-9327-5e9d7f8f7ab0
Jun 11 16:23:53.382: INFO: Couldn't delete PD "aws://us-west-1a/vol-0de7488a1d49d6138", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0de7488a1d49d6138 is currently attached to i-0904333f4b3ec64fb
	status code: 400, request id: 6dfae25e-85b7-46f6-83d9-210628b3d7a8
Jun 11 16:23:58.740: INFO: Successfully deleted PD "aws://us-west-1a/vol-0de7488a1d49d6138".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 16:23:58.740: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-3715" for this suite.
... skipping 338 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 16:23:17.580: 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.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 11 16:23:17.833: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 11 16:23:17.833: INFO: Creating resource for dynamic PV
Jun 11 16:23:17.833: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-72157m4ws
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 11 16:23:24.192: INFO: Deleting pod "pod-59b3a708-404d-4c76-b2c1-f26abb2f89bc" in namespace "volumemode-7215"
Jun 11 16:23:24.243: INFO: Wait up to 5m0s for pod "pod-59b3a708-404d-4c76-b2c1-f26abb2f89bc" to be fully deleted
STEP: Deleting pvc
Jun 11 16:23:36.445: INFO: Deleting PersistentVolumeClaim "awsx5sfv"
Jun 11 16:23:36.496: INFO: Waiting up to 5m0s for PersistentVolume pvc-ae8c41fa-18de-46fc-82cf-d1003366a366 to get deleted
Jun 11 16:23:36.546: INFO: PersistentVolume pvc-ae8c41fa-18de-46fc-82cf-d1003366a366 found and phase=Released (49.955598ms)
... skipping 14 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.xDG68BsTe/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.xDG68BsTe/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (block volmode)] volumeMode
    /tmp/kops.xDG68BsTe/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.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [sig-storage] Storage Policy Based Volume Provisioning [Feature:vsphere]
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 16:24:07.041: INFO: >>> kubeConfig: /root/.kube/config
... skipping 735 lines ...
Jun 11 16:23:46.627: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9414ffcgf
STEP: creating a claim
Jun 11 16:23:46.679: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-48zq
STEP: Creating a pod to test subpath
Jun 11 16:23:46.838: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-48zq" in namespace "provisioning-9414" to be "Succeeded or Failed"
Jun 11 16:23:46.895: INFO: Pod "pod-subpath-test-dynamicpv-48zq": Phase="Pending", Reason="", readiness=false. Elapsed: 57.783499ms
Jun 11 16:23:48.948: INFO: Pod "pod-subpath-test-dynamicpv-48zq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.110342529s
Jun 11 16:23:51.000: INFO: Pod "pod-subpath-test-dynamicpv-48zq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.162088937s
Jun 11 16:23:53.051: INFO: Pod "pod-subpath-test-dynamicpv-48zq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.21367075s
Jun 11 16:23:55.103: INFO: Pod "pod-subpath-test-dynamicpv-48zq": Phase="Pending", Reason="", readiness=false. Elapsed: 8.265767534s
Jun 11 16:23:57.155: INFO: Pod "pod-subpath-test-dynamicpv-48zq": Phase="Pending", Reason="", readiness=false. Elapsed: 10.317810272s
Jun 11 16:23:59.208: INFO: Pod "pod-subpath-test-dynamicpv-48zq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.369965242s
STEP: Saw pod success
Jun 11 16:23:59.208: INFO: Pod "pod-subpath-test-dynamicpv-48zq" satisfied condition "Succeeded or Failed"
Jun 11 16:23:59.259: INFO: Trying to get logs from node ip-172-20-41-176.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-48zq container test-container-subpath-dynamicpv-48zq: <nil>
STEP: delete the pod
Jun 11 16:23:59.372: INFO: Waiting for pod pod-subpath-test-dynamicpv-48zq to disappear
Jun 11 16:23:59.423: INFO: Pod pod-subpath-test-dynamicpv-48zq no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-48zq
Jun 11 16:23:59.423: INFO: Deleting pod "pod-subpath-test-dynamicpv-48zq" in namespace "provisioning-9414"
... skipping 214 lines ...
Jun 11 16:23:03.129: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6455b225r
STEP: creating a claim
Jun 11 16:23:03.182: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-p2rn
STEP: Creating a pod to test subpath
Jun 11 16:23:03.342: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-p2rn" in namespace "provisioning-6455" to be "Succeeded or Failed"
Jun 11 16:23:03.394: INFO: Pod "pod-subpath-test-dynamicpv-p2rn": Phase="Pending", Reason="", readiness=false. Elapsed: 51.78251ms
Jun 11 16:23:05.446: INFO: Pod "pod-subpath-test-dynamicpv-p2rn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.104377184s
Jun 11 16:23:07.507: INFO: Pod "pod-subpath-test-dynamicpv-p2rn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.165054021s
Jun 11 16:23:09.559: INFO: Pod "pod-subpath-test-dynamicpv-p2rn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.217056419s
Jun 11 16:23:11.615: INFO: Pod "pod-subpath-test-dynamicpv-p2rn": Phase="Pending", Reason="", readiness=false. Elapsed: 8.272650566s
Jun 11 16:23:13.669: INFO: Pod "pod-subpath-test-dynamicpv-p2rn": Phase="Pending", Reason="", readiness=false. Elapsed: 10.327258213s
... skipping 2 lines ...
Jun 11 16:23:19.828: INFO: Pod "pod-subpath-test-dynamicpv-p2rn": Phase="Pending", Reason="", readiness=false. Elapsed: 16.486240855s
Jun 11 16:23:21.881: INFO: Pod "pod-subpath-test-dynamicpv-p2rn": Phase="Pending", Reason="", readiness=false. Elapsed: 18.539447486s
Jun 11 16:23:23.934: INFO: Pod "pod-subpath-test-dynamicpv-p2rn": Phase="Pending", Reason="", readiness=false. Elapsed: 20.591760076s
Jun 11 16:23:25.986: INFO: Pod "pod-subpath-test-dynamicpv-p2rn": Phase="Pending", Reason="", readiness=false. Elapsed: 22.644234859s
Jun 11 16:23:28.039: INFO: Pod "pod-subpath-test-dynamicpv-p2rn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.697440785s
STEP: Saw pod success
Jun 11 16:23:28.039: INFO: Pod "pod-subpath-test-dynamicpv-p2rn" satisfied condition "Succeeded or Failed"
Jun 11 16:23:28.092: INFO: Trying to get logs from node ip-172-20-56-114.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-p2rn container test-container-subpath-dynamicpv-p2rn: <nil>
STEP: delete the pod
Jun 11 16:23:28.206: INFO: Waiting for pod pod-subpath-test-dynamicpv-p2rn to disappear
Jun 11 16:23:28.258: INFO: Pod pod-subpath-test-dynamicpv-p2rn no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-p2rn
Jun 11 16:23:28.258: INFO: Deleting pod "pod-subpath-test-dynamicpv-p2rn" in namespace "provisioning-6455"
STEP: Creating pod pod-subpath-test-dynamicpv-p2rn
STEP: Creating a pod to test subpath
Jun 11 16:23:28.365: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-p2rn" in namespace "provisioning-6455" to be "Succeeded or Failed"
Jun 11 16:23:28.416: INFO: Pod "pod-subpath-test-dynamicpv-p2rn": Phase="Pending", Reason="", readiness=false. Elapsed: 51.655177ms
Jun 11 16:23:30.469: INFO: Pod "pod-subpath-test-dynamicpv-p2rn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.10403457s
Jun 11 16:23:32.522: INFO: Pod "pod-subpath-test-dynamicpv-p2rn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.157138707s
Jun 11 16:23:34.574: INFO: Pod "pod-subpath-test-dynamicpv-p2rn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.209726421s
Jun 11 16:23:36.627: INFO: Pod "pod-subpath-test-dynamicpv-p2rn": Phase="Pending", Reason="", readiness=false. Elapsed: 8.262714379s
Jun 11 16:23:38.680: INFO: Pod "pod-subpath-test-dynamicpv-p2rn": Phase="Pending", Reason="", readiness=false. Elapsed: 10.315644694s
... skipping 7 lines ...
Jun 11 16:23:55.110: INFO: Pod "pod-subpath-test-dynamicpv-p2rn": Phase="Pending", Reason="", readiness=false. Elapsed: 26.745722618s
Jun 11 16:23:57.165: INFO: Pod "pod-subpath-test-dynamicpv-p2rn": Phase="Pending", Reason="", readiness=false. Elapsed: 28.80045459s
Jun 11 16:23:59.217: INFO: Pod "pod-subpath-test-dynamicpv-p2rn": Phase="Pending", Reason="", readiness=false. Elapsed: 30.852801192s
Jun 11 16:24:01.286: INFO: Pod "pod-subpath-test-dynamicpv-p2rn": Phase="Pending", Reason="", readiness=false. Elapsed: 32.921443833s
Jun 11 16:24:03.343: INFO: Pod "pod-subpath-test-dynamicpv-p2rn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.978242977s
STEP: Saw pod success
Jun 11 16:24:03.343: INFO: Pod "pod-subpath-test-dynamicpv-p2rn" satisfied condition "Succeeded or Failed"
Jun 11 16:24:03.396: INFO: Trying to get logs from node ip-172-20-41-176.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-p2rn container test-container-subpath-dynamicpv-p2rn: <nil>
STEP: delete the pod
Jun 11 16:24:03.518: INFO: Waiting for pod pod-subpath-test-dynamicpv-p2rn to disappear
Jun 11 16:24:03.569: INFO: Pod pod-subpath-test-dynamicpv-p2rn no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-p2rn
Jun 11 16:24:03.570: INFO: Deleting pod "pod-subpath-test-dynamicpv-p2rn" in namespace "provisioning-6455"
... skipping 94 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.xDG68BsTe/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.xDG68BsTe/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.xDG68BsTe/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.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 127 lines ...
Jun 11 16:23:27.555: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4872vn9xf
STEP: creating a claim
Jun 11 16:23:27.607: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-9q95
STEP: Creating a pod to test subpath
Jun 11 16:23:27.760: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-9q95" in namespace "provisioning-4872" to be "Succeeded or Failed"
Jun 11 16:23:27.812: INFO: Pod "pod-subpath-test-dynamicpv-9q95": Phase="Pending", Reason="", readiness=false. Elapsed: 51.975923ms
Jun 11 16:23:29.863: INFO: Pod "pod-subpath-test-dynamicpv-9q95": Phase="Pending", Reason="", readiness=false. Elapsed: 2.102557348s
Jun 11 16:23:31.913: INFO: Pod "pod-subpath-test-dynamicpv-9q95": Phase="Pending", Reason="", readiness=false. Elapsed: 4.152721678s
Jun 11 16:23:33.965: INFO: Pod "pod-subpath-test-dynamicpv-9q95": Phase="Pending", Reason="", readiness=false. Elapsed: 6.204632587s
Jun 11 16:23:36.015: INFO: Pod "pod-subpath-test-dynamicpv-9q95": Phase="Pending", Reason="", readiness=false. Elapsed: 8.255447633s
Jun 11 16:23:38.067: INFO: Pod "pod-subpath-test-dynamicpv-9q95": Phase="Pending", Reason="", readiness=false. Elapsed: 10.306774682s
... skipping 11 lines ...
Jun 11 16:24:02.686: INFO: Pod "pod-subpath-test-dynamicpv-9q95": Phase="Pending", Reason="", readiness=false. Elapsed: 34.926133879s
Jun 11 16:24:04.738: INFO: Pod "pod-subpath-test-dynamicpv-9q95": Phase="Pending", Reason="", readiness=false. Elapsed: 36.978371401s
Jun 11 16:24:06.790: INFO: Pod "pod-subpath-test-dynamicpv-9q95": Phase="Pending", Reason="", readiness=false. Elapsed: 39.030426101s
Jun 11 16:24:08.841: INFO: Pod "pod-subpath-test-dynamicpv-9q95": Phase="Pending", Reason="", readiness=false. Elapsed: 41.08073145s
Jun 11 16:24:10.891: INFO: Pod "pod-subpath-test-dynamicpv-9q95": Phase="Succeeded", Reason="", readiness=false. Elapsed: 43.131045261s
STEP: Saw pod success
Jun 11 16:24:10.891: INFO: Pod "pod-subpath-test-dynamicpv-9q95" satisfied condition "Succeeded or Failed"
Jun 11 16:24:10.941: INFO: Trying to get logs from node ip-172-20-56-114.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-9q95 container test-container-subpath-dynamicpv-9q95: <nil>
STEP: delete the pod
Jun 11 16:24:11.058: INFO: Waiting for pod pod-subpath-test-dynamicpv-9q95 to disappear
Jun 11 16:24:11.108: INFO: Pod pod-subpath-test-dynamicpv-9q95 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-9q95
Jun 11 16:24:11.108: INFO: Deleting pod "pod-subpath-test-dynamicpv-9q95" in namespace "provisioning-4872"
... skipping 39 lines ...
Jun 11 16:23:59.123: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-7145k78ct
STEP: creating a claim
Jun 11 16:23:59.176: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-sp2q
STEP: Creating a pod to test exec-volume-test
Jun 11 16:23:59.337: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-sp2q" in namespace "volume-7145" to be "Succeeded or Failed"
Jun 11 16:23:59.390: INFO: Pod "exec-volume-test-dynamicpv-sp2q": Phase="Pending", Reason="", readiness=false. Elapsed: 52.150692ms
Jun 11 16:24:01.442: INFO: Pod "exec-volume-test-dynamicpv-sp2q": Phase="Pending", Reason="", readiness=false. Elapsed: 2.104809139s
Jun 11 16:24:03.495: INFO: Pod "exec-volume-test-dynamicpv-sp2q": Phase="Pending", Reason="", readiness=false. Elapsed: 4.15803568s
Jun 11 16:24:05.549: INFO: Pod "exec-volume-test-dynamicpv-sp2q": Phase="Pending", Reason="", readiness=false. Elapsed: 6.212093864s
Jun 11 16:24:07.602: INFO: Pod "exec-volume-test-dynamicpv-sp2q": Phase="Pending", Reason="", readiness=false. Elapsed: 8.264719784s
Jun 11 16:24:09.655: INFO: Pod "exec-volume-test-dynamicpv-sp2q": Phase="Pending", Reason="", readiness=false. Elapsed: 10.318058268s
Jun 11 16:24:11.708: INFO: Pod "exec-volume-test-dynamicpv-sp2q": Phase="Pending", Reason="", readiness=false. Elapsed: 12.370505551s
Jun 11 16:24:13.763: INFO: Pod "exec-volume-test-dynamicpv-sp2q": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.425449853s
STEP: Saw pod success
Jun 11 16:24:13.763: INFO: Pod "exec-volume-test-dynamicpv-sp2q" satisfied condition "Succeeded or Failed"
Jun 11 16:24:13.815: INFO: Trying to get logs from node ip-172-20-56-114.us-west-1.compute.internal pod exec-volume-test-dynamicpv-sp2q container exec-container-dynamicpv-sp2q: <nil>
STEP: delete the pod
Jun 11 16:24:13.949: INFO: Waiting for pod exec-volume-test-dynamicpv-sp2q to disappear
Jun 11 16:24:14.003: INFO: Pod exec-volume-test-dynamicpv-sp2q no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-sp2q
Jun 11 16:24:14.003: INFO: Deleting pod "exec-volume-test-dynamicpv-sp2q" in namespace "volume-7145"
... skipping 68 lines ...
Jun 11 16:23:38.504: INFO: PersistentVolumeClaim pvc-m2b96 found but phase is Pending instead of Bound.
Jun 11 16:23:40.556: INFO: PersistentVolumeClaim pvc-m2b96 found and phase=Bound (14.415435408s)
Jun 11 16:23:40.556: INFO: Waiting up to 3m0s for PersistentVolume aws-46nwp to have phase Bound
Jun 11 16:23:40.608: INFO: PersistentVolume aws-46nwp found and phase=Bound (52.319462ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-8bnz
STEP: Creating a pod to test exec-volume-test
Jun 11 16:23:40.763: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-8bnz" in namespace "volume-4397" to be "Succeeded or Failed"
Jun 11 16:23:40.815: INFO: Pod "exec-volume-test-preprovisionedpv-8bnz": Phase="Pending", Reason="", readiness=false. Elapsed: 52.356595ms
Jun 11 16:23:42.868: INFO: Pod "exec-volume-test-preprovisionedpv-8bnz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.105041229s
Jun 11 16:23:44.920: INFO: Pod "exec-volume-test-preprovisionedpv-8bnz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.156660395s
Jun 11 16:23:46.974: INFO: Pod "exec-volume-test-preprovisionedpv-8bnz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.210384341s
Jun 11 16:23:49.026: INFO: Pod "exec-volume-test-preprovisionedpv-8bnz": Phase="Pending", Reason="", readiness=false. Elapsed: 8.262630549s
Jun 11 16:23:51.077: INFO: Pod "exec-volume-test-preprovisionedpv-8bnz": Phase="Pending", Reason="", readiness=false. Elapsed: 10.314201513s
... skipping 8 lines ...
Jun 11 16:24:09.551: INFO: Pod "exec-volume-test-preprovisionedpv-8bnz": Phase="Pending", Reason="", readiness=false. Elapsed: 28.78832999s
Jun 11 16:24:11.605: INFO: Pod "exec-volume-test-preprovisionedpv-8bnz": Phase="Pending", Reason="", readiness=false. Elapsed: 30.841632459s
Jun 11 16:24:13.657: INFO: Pod "exec-volume-test-preprovisionedpv-8bnz": Phase="Pending", Reason="", readiness=false. Elapsed: 32.89346929s
Jun 11 16:24:15.709: INFO: Pod "exec-volume-test-preprovisionedpv-8bnz": Phase="Pending", Reason="", readiness=false. Elapsed: 34.946143819s
Jun 11 16:24:17.761: INFO: Pod "exec-volume-test-preprovisionedpv-8bnz": Phase="Succeeded", Reason="", readiness=false. Elapsed: 36.998313942s
STEP: Saw pod success
Jun 11 16:24:17.762: INFO: Pod "exec-volume-test-preprovisionedpv-8bnz" satisfied condition "Succeeded or Failed"
Jun 11 16:24:17.813: INFO: Trying to get logs from node ip-172-20-40-55.us-west-1.compute.internal pod exec-volume-test-preprovisionedpv-8bnz container exec-container-preprovisionedpv-8bnz: <nil>
STEP: delete the pod
Jun 11 16:24:17.928: INFO: Waiting for pod exec-volume-test-preprovisionedpv-8bnz to disappear
Jun 11 16:24:17.979: INFO: Pod exec-volume-test-preprovisionedpv-8bnz no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-8bnz
Jun 11 16:24:17.979: INFO: Deleting pod "exec-volume-test-preprovisionedpv-8bnz" in namespace "volume-4397"
STEP: Deleting pv and pvc
Jun 11 16:24:18.031: INFO: Deleting PersistentVolumeClaim "pvc-m2b96"
Jun 11 16:24:18.087: INFO: Deleting PersistentVolume "aws-46nwp"
Jun 11 16:24:18.290: INFO: Couldn't delete PD "aws://us-west-1a/vol-09e4caa0167d1be44", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-09e4caa0167d1be44 is currently attached to i-0904333f4b3ec64fb
	status code: 400, request id: 20b9de36-3c82-4adf-acd4-164773716ec8
Jun 11 16:24:23.620: INFO: Couldn't delete PD "aws://us-west-1a/vol-09e4caa0167d1be44", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-09e4caa0167d1be44 is currently attached to i-0904333f4b3ec64fb
	status code: 400, request id: 28e5d6c3-53df-432d-8de8-5e3b076fc08a
Jun 11 16:24:28.990: INFO: Couldn't delete PD "aws://us-west-1a/vol-09e4caa0167d1be44", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-09e4caa0167d1be44 is currently attached to i-0904333f4b3ec64fb
	status code: 400, request id: d3471062-4b4e-413b-9a4a-f81b62c8eade
Jun 11 16:24:34.332: INFO: Couldn't delete PD "aws://us-west-1a/vol-09e4caa0167d1be44", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-09e4caa0167d1be44 is currently attached to i-0904333f4b3ec64fb
	status code: 400, request id: b85ceb00-f612-40a0-bb22-bf987a3219ae
Jun 11 16:24:39.749: INFO: Successfully deleted PD "aws://us-west-1a/vol-09e4caa0167d1be44".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 16:24:39.750: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-4397" for this suite.
... skipping 24 lines ...
Jun 11 16:24:09.158: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-9796qhvxk
STEP: creating a claim
Jun 11 16:24:09.214: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Jun 11 16:24:09.327: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 11 16:24:09.438: INFO: Error updating pvc aws4f2jx: PersistentVolumeClaim "aws4f2jx" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-9796qhvxk",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun 11 16:24:39.647: INFO: Error updating pvc aws4f2jx: PersistentVolumeClaim "aws4f2jx" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 119 lines ...
Jun 11 16:24:26.612: INFO: Waiting for pod aws-client to disappear
Jun 11 16:24:26.664: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 11 16:24:26.664: INFO: Deleting PersistentVolumeClaim "pvc-b7f44"
Jun 11 16:24:26.717: INFO: Deleting PersistentVolume "aws-ltrmg"
Jun 11 16:24:27.084: INFO: Couldn't delete PD "aws://us-west-1a/vol-0027f8c9936892d0c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0027f8c9936892d0c is currently attached to i-0904333f4b3ec64fb
	status code: 400, request id: c9bfdb60-f3d5-46e9-86d7-bb309717f5f2
Jun 11 16:24:32.471: INFO: Couldn't delete PD "aws://us-west-1a/vol-0027f8c9936892d0c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0027f8c9936892d0c is currently attached to i-0904333f4b3ec64fb
	status code: 400, request id: c6269475-f03b-4fc6-888f-60288a2b1b2a
Jun 11 16:24:37.807: INFO: Couldn't delete PD "aws://us-west-1a/vol-0027f8c9936892d0c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0027f8c9936892d0c is currently attached to i-0904333f4b3ec64fb
	status code: 400, request id: 3e3232cf-ceab-4c84-a29a-d79564881273
Jun 11 16:24:43.172: INFO: Successfully deleted PD "aws://us-west-1a/vol-0027f8c9936892d0c".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 16:24:43.172: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-2233" for this suite.
... skipping 619 lines ...
STEP: Deleting pod hostexec-ip-172-20-40-55.us-west-1.compute.internal-hsz5b in namespace volumemode-7048
Jun 11 16:24:36.563: INFO: Deleting pod "pod-56da8740-da54-41ff-a91d-cd767dd39252" in namespace "volumemode-7048"
Jun 11 16:24:36.614: INFO: Wait up to 5m0s for pod "pod-56da8740-da54-41ff-a91d-cd767dd39252" to be fully deleted
STEP: Deleting pv and pvc
Jun 11 16:24:46.718: INFO: Deleting PersistentVolumeClaim "pvc-d2qg5"
Jun 11 16:24:46.769: INFO: Deleting PersistentVolume "aws-q2nbz"
Jun 11 16:24:46.969: INFO: Couldn't delete PD "aws://us-west-1a/vol-02e180aac9b2a8bcf", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02e180aac9b2a8bcf is currently attached to i-0904333f4b3ec64fb
	status code: 400, request id: 1735262e-a05a-4fd3-bdb9-8dc51f456e0f
Jun 11 16:24:52.360: INFO: Successfully deleted PD "aws://us-west-1a/vol-02e180aac9b2a8bcf".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 16:24:52.361: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-7048" for this suite.
... skipping 108 lines ...
Jun 11 16:24:07.776: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8979-e2e-scs7mwm
STEP: creating a claim
Jun 11 16:24:07.828: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-rj9x
STEP: Creating a pod to test subpath
Jun 11 16:24:07.990: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-rj9x" in namespace "provisioning-8979" to be "Succeeded or Failed"
Jun 11 16:24:08.041: INFO: Pod "pod-subpath-test-dynamicpv-rj9x": Phase="Pending", Reason="", readiness=false. Elapsed: 51.004991ms
Jun 11 16:24:10.093: INFO: Pod "pod-subpath-test-dynamicpv-rj9x": Phase="Pending", Reason="", readiness=false. Elapsed: 2.102919807s
Jun 11 16:24:12.146: INFO: Pod "pod-subpath-test-dynamicpv-rj9x": Phase="Pending", Reason="", readiness=false. Elapsed: 4.15614679s
Jun 11 16:24:14.200: INFO: Pod "pod-subpath-test-dynamicpv-rj9x": Phase="Pending", Reason="", readiness=false. Elapsed: 6.209600138s
Jun 11 16:24:16.252: INFO: Pod "pod-subpath-test-dynamicpv-rj9x": Phase="Pending", Reason="", readiness=false. Elapsed: 8.261684748s
Jun 11 16:24:18.306: INFO: Pod "pod-subpath-test-dynamicpv-rj9x": Phase="Pending", Reason="", readiness=false. Elapsed: 10.31545093s
... skipping 2 lines ...
Jun 11 16:24:24.462: INFO: Pod "pod-subpath-test-dynamicpv-rj9x": Phase="Pending", Reason="", readiness=false. Elapsed: 16.47218936s
Jun 11 16:24:26.516: INFO: Pod "pod-subpath-test-dynamicpv-rj9x": Phase="Pending", Reason="", readiness=false. Elapsed: 18.525247228s
Jun 11 16:24:28.567: INFO: Pod "pod-subpath-test-dynamicpv-rj9x": Phase="Pending", Reason="", readiness=false. Elapsed: 20.576958781s
Jun 11 16:24:30.619: INFO: Pod "pod-subpath-test-dynamicpv-rj9x": Phase="Pending", Reason="", readiness=false. Elapsed: 22.628846696s
Jun 11 16:24:32.670: INFO: Pod "pod-subpath-test-dynamicpv-rj9x": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.680217284s
STEP: Saw pod success
Jun 11 16:24:32.671: INFO: Pod "pod-subpath-test-dynamicpv-rj9x" satisfied condition "Succeeded or Failed"
Jun 11 16:24:32.722: INFO: Trying to get logs from node ip-172-20-42-53.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-rj9x container test-container-subpath-dynamicpv-rj9x: <nil>
STEP: delete the pod
Jun 11 16:24:32.842: INFO: Waiting for pod pod-subpath-test-dynamicpv-rj9x to disappear
Jun 11 16:24:32.893: INFO: Pod pod-subpath-test-dynamicpv-rj9x no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-rj9x
Jun 11 16:24:32.893: INFO: Deleting pod "pod-subpath-test-dynamicpv-rj9x" in namespace "provisioning-8979"
... skipping 55 lines ...
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 16:25:09.109: 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.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Jun 11 16:25:09.421: INFO: found topology map[topology.kubernetes.io/zone:us-west-1a]
Jun 11 16:25:09.421: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 11 16:25:09.421: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.xDG68BsTe/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.xDG68BsTe/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (delayed binding)] topology
    /tmp/kops.xDG68BsTe/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.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 66 lines ...
Jun 11 16:25:06.586: INFO: Waiting for pod aws-client to disappear
Jun 11 16:25:06.638: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 11 16:25:06.638: INFO: Deleting PersistentVolumeClaim "pvc-f9c58"
Jun 11 16:25:06.690: INFO: Deleting PersistentVolume "aws-x7dzv"
Jun 11 16:25:06.931: INFO: Couldn't delete PD "aws://us-west-1a/vol-0284425ae07626beb", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0284425ae07626beb is currently attached to i-02fd57ac3b1f478ed
	status code: 400, request id: 65b632ba-e8a2-4aeb-9707-a9d906dea7c3
Jun 11 16:25:12.273: INFO: Couldn't delete PD "aws://us-west-1a/vol-0284425ae07626beb", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0284425ae07626beb is currently attached to i-02fd57ac3b1f478ed
	status code: 400, request id: da16fa73-a645-4ead-a148-b657d95f1cb8
Jun 11 16:25:17.610: INFO: Couldn't delete PD "aws://us-west-1a/vol-0284425ae07626beb", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0284425ae07626beb is currently attached to i-02fd57ac3b1f478ed
	status code: 400, request id: 1d22ff56-1e95-419f-9c42-9f540d19c429
Jun 11 16:25:22.980: INFO: Successfully deleted PD "aws://us-west-1a/vol-0284425ae07626beb".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 16:25:22.980: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-2515" for this suite.
... skipping 202 lines ...
Jun 11 16:25:12.958: INFO: Waiting for pod aws-client to disappear
Jun 11 16:25:13.009: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 11 16:25:13.009: INFO: Deleting PersistentVolumeClaim "pvc-f8vdw"
Jun 11 16:25:13.063: INFO: Deleting PersistentVolume "aws-n7s52"
Jun 11 16:25:13.428: INFO: Couldn't delete PD "aws://us-west-1a/vol-021dc81486a3a8d3e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-021dc81486a3a8d3e is currently attached to i-0e926e71eaea5d363
	status code: 400, request id: 0748132c-cf37-48cd-8306-ad992d482f74
Jun 11 16:25:18.765: INFO: Couldn't delete PD "aws://us-west-1a/vol-021dc81486a3a8d3e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-021dc81486a3a8d3e is currently attached to i-0e926e71eaea5d363
	status code: 400, request id: 99226748-9421-4340-85da-7b718c1d5c50
Jun 11 16:25:24.157: INFO: Successfully deleted PD "aws://us-west-1a/vol-021dc81486a3a8d3e".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 16:25:24.157: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-1580" for this suite.
... skipping 23 lines ...
Jun 11 16:24:31.277: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4296-e2e-sc5glkh
STEP: creating a claim
Jun 11 16:24:31.330: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-6s4g
STEP: Creating a pod to test subpath
Jun 11 16:24:31.488: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-6s4g" in namespace "provisioning-4296" to be "Succeeded or Failed"
Jun 11 16:24:31.540: INFO: Pod "pod-subpath-test-dynamicpv-6s4g": Phase="Pending", Reason="", readiness=false. Elapsed: 51.8134ms
Jun 11 16:24:33.593: INFO: Pod "pod-subpath-test-dynamicpv-6s4g": Phase="Pending", Reason="", readiness=false. Elapsed: 2.104313651s
Jun 11 16:24:35.645: INFO: Pod "pod-subpath-test-dynamicpv-6s4g": Phase="Pending", Reason="", readiness=false. Elapsed: 4.156583427s
Jun 11 16:24:37.697: INFO: Pod "pod-subpath-test-dynamicpv-6s4g": Phase="Pending", Reason="", readiness=false. Elapsed: 6.209224958s
Jun 11 16:24:39.750: INFO: Pod "pod-subpath-test-dynamicpv-6s4g": Phase="Pending", Reason="", readiness=false. Elapsed: 8.261536853s
Jun 11 16:24:41.803: INFO: Pod "pod-subpath-test-dynamicpv-6s4g": Phase="Pending", Reason="", readiness=false. Elapsed: 10.314491372s
Jun 11 16:24:43.854: INFO: Pod "pod-subpath-test-dynamicpv-6s4g": Phase="Pending", Reason="", readiness=false. Elapsed: 12.366070361s
Jun 11 16:24:45.907: INFO: Pod "pod-subpath-test-dynamicpv-6s4g": Phase="Pending", Reason="", readiness=false. Elapsed: 14.418589815s
Jun 11 16:24:47.959: INFO: Pod "pod-subpath-test-dynamicpv-6s4g": Phase="Pending", Reason="", readiness=false. Elapsed: 16.471171267s
Jun 11 16:24:50.013: INFO: Pod "pod-subpath-test-dynamicpv-6s4g": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.524753814s
STEP: Saw pod success
Jun 11 16:24:50.013: INFO: Pod "pod-subpath-test-dynamicpv-6s4g" satisfied condition "Succeeded or Failed"
Jun 11 16:24:50.064: INFO: Trying to get logs from node ip-172-20-42-53.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-6s4g container test-container-subpath-dynamicpv-6s4g: <nil>
STEP: delete the pod
Jun 11 16:24:50.175: INFO: Waiting for pod pod-subpath-test-dynamicpv-6s4g to disappear
Jun 11 16:24:50.229: INFO: Pod pod-subpath-test-dynamicpv-6s4g no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-6s4g
Jun 11 16:24:50.229: INFO: Deleting pod "pod-subpath-test-dynamicpv-6s4g" in namespace "provisioning-4296"
... skipping 281 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 16:24:52.379: 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.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun 11 16:24:52.638: INFO: Creating resource for dynamic PV
Jun 11 16:24:52.638: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3365-e2e-scpxnsb
STEP: creating a claim
Jun 11 16:24:52.691: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-x4xd
STEP: Checking for subpath error in container status
Jun 11 16:25:08.960: INFO: Deleting pod "pod-subpath-test-dynamicpv-x4xd" in namespace "provisioning-3365"
Jun 11 16:25:09.014: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-x4xd" to be fully deleted
STEP: Deleting pod
Jun 11 16:25:21.117: INFO: Deleting pod "pod-subpath-test-dynamicpv-x4xd" in namespace "provisioning-3365"
STEP: Deleting pvc
Jun 11 16:25:21.272: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comhb6rm"
... skipping 10 lines ...

• [SLOW TEST:39.303 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.xDG68BsTe/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.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 196 lines ...
Jun 11 16:25:21.838: INFO: Pod aws-client still exists
Jun 11 16:25:23.786: INFO: Waiting for pod aws-client to disappear
Jun 11 16:25:23.842: INFO: Pod aws-client still exists
Jun 11 16:25:25.786: INFO: Waiting for pod aws-client to disappear
Jun 11 16:25:25.836: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun 11 16:25:26.164: INFO: Couldn't delete PD "aws://us-west-1a/vol-0b11bf95ce8f8dcbf", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0b11bf95ce8f8dcbf is currently attached to i-0904333f4b3ec64fb
	status code: 400, request id: 14a18d9f-6288-4f0e-a4a5-494a80f0e6f7
Jun 11 16:25:31.529: INFO: Couldn't delete PD "aws://us-west-1a/vol-0b11bf95ce8f8dcbf", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0b11bf95ce8f8dcbf is currently attached to i-0904333f4b3ec64fb
	status code: 400, request id: 1159bd91-60a2-4601-a666-97d0325a72ac
Jun 11 16:25:36.883: INFO: Successfully deleted PD "aws://us-west-1a/vol-0b11bf95ce8f8dcbf".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 16:25:36.883: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-6445" for this suite.
... skipping 18 lines ...

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

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

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

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 15 lines ...
Jun 11 16:25:37.364: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 81 lines ...
Jun 11 16:24:30.326: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3632c4tbf
STEP: creating a claim
Jun 11 16:24:30.378: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-nq5v
STEP: Creating a pod to test atomic-volume-subpath
Jun 11 16:24:30.540: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-nq5v" in namespace "provisioning-3632" to be "Succeeded or Failed"
Jun 11 16:24:30.593: INFO: Pod "pod-subpath-test-dynamicpv-nq5v": Phase="Pending", Reason="", readiness=false. Elapsed: 52.171114ms
Jun 11 16:24:32.645: INFO: Pod "pod-subpath-test-dynamicpv-nq5v": Phase="Pending", Reason="", readiness=false. Elapsed: 2.104959023s
Jun 11 16:24:34.705: INFO: Pod "pod-subpath-test-dynamicpv-nq5v": Phase="Pending", Reason="", readiness=false. Elapsed: 4.164521123s
Jun 11 16:24:36.757: INFO: Pod "pod-subpath-test-dynamicpv-nq5v": Phase="Pending", Reason="", readiness=false. Elapsed: 6.216814859s
Jun 11 16:24:38.810: INFO: Pod "pod-subpath-test-dynamicpv-nq5v": Phase="Pending", Reason="", readiness=false. Elapsed: 8.269163533s
Jun 11 16:24:40.862: INFO: Pod "pod-subpath-test-dynamicpv-nq5v": Phase="Pending", Reason="", readiness=false. Elapsed: 10.321321936s
... skipping 13 lines ...
Jun 11 16:25:09.622: INFO: Pod "pod-subpath-test-dynamicpv-nq5v": Phase="Running", Reason="", readiness=true. Elapsed: 39.081784291s
Jun 11 16:25:11.676: INFO: Pod "pod-subpath-test-dynamicpv-nq5v": Phase="Running", Reason="", readiness=true. Elapsed: 41.135925177s
Jun 11 16:25:13.730: INFO: Pod "pod-subpath-test-dynamicpv-nq5v": Phase="Running", Reason="", readiness=true. Elapsed: 43.189874901s
Jun 11 16:25:15.784: INFO: Pod "pod-subpath-test-dynamicpv-nq5v": Phase="Running", Reason="", readiness=true. Elapsed: 45.243756194s
Jun 11 16:25:17.850: INFO: Pod "pod-subpath-test-dynamicpv-nq5v": Phase="Succeeded", Reason="", readiness=false. Elapsed: 47.310098223s
STEP: Saw pod success
Jun 11 16:25:17.851: INFO: Pod "pod-subpath-test-dynamicpv-nq5v" satisfied condition "Succeeded or Failed"
Jun 11 16:25:17.903: INFO: Trying to get logs from node ip-172-20-42-53.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-nq5v container test-container-subpath-dynamicpv-nq5v: <nil>
STEP: delete the pod
Jun 11 16:25:18.016: INFO: Waiting for pod pod-subpath-test-dynamicpv-nq5v to disappear
Jun 11 16:25:18.070: INFO: Pod pod-subpath-test-dynamicpv-nq5v no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-nq5v
Jun 11 16:25:18.070: INFO: Deleting pod "pod-subpath-test-dynamicpv-nq5v" in namespace "provisioning-3632"
... skipping 494 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 16:24:52.469: 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.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun 11 16:24:52.723: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 11 16:24:52.723: INFO: Creating resource for dynamic PV
Jun 11 16:24:52.723: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-79776z6dw
STEP: creating a claim
Jun 11 16:24:52.774: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-8qpt
STEP: Checking for subpath error in container status
Jun 11 16:25:17.032: INFO: Deleting pod "pod-subpath-test-dynamicpv-8qpt" in namespace "provisioning-7977"
Jun 11 16:25:17.089: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-8qpt" to be fully deleted
STEP: Deleting pod
Jun 11 16:25:25.191: INFO: Deleting pod "pod-subpath-test-dynamicpv-8qpt" in namespace "provisioning-7977"
STEP: Deleting pvc
Jun 11 16:25:25.342: INFO: Deleting PersistentVolumeClaim "awswdzdl"
... skipping 15 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.xDG68BsTe/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.xDG68BsTe/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath directory is outside the volume [Slow][LinuxOnly]
      /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 115 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 16:25:09.579: 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.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun 11 16:25:09.837: INFO: Creating resource for dynamic PV
Jun 11 16:25:09.837: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-549-e2e-sczrz8c
STEP: creating a claim
Jun 11 16:25:09.890: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-pkt4
STEP: Checking for subpath error in container status
Jun 11 16:25:34.155: INFO: Deleting pod "pod-subpath-test-dynamicpv-pkt4" in namespace "provisioning-549"
Jun 11 16:25:34.208: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-pkt4" to be fully deleted
STEP: Deleting pod
Jun 11 16:25:48.312: INFO: Deleting pod "pod-subpath-test-dynamicpv-pkt4" in namespace "provisioning-549"
STEP: Deleting pvc
Jun 11 16:25:48.466: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.commxbd6"
... skipping 10 lines ...

• [SLOW TEST:49.252 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.xDG68BsTe/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.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (ntfs)][Feature:Windows] volumes
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 11 16:25:58.833: INFO: Distro debian doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Pre-provisioned PV (ntfs)][Feature:Windows] volumes
... skipping 115 lines ...
Jun 11 16:24:09.378: INFO: Creating resource for dynamic PV
Jun 11 16:24:09.379: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-5172-e2e-sc7zvmd
STEP: creating a claim
Jun 11 16:24:09.431: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 11 16:24:09.587: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-bplrn" in namespace "snapshotting-5172" to be "Succeeded or Failed"
Jun 11 16:24:09.639: INFO: Pod "pvc-snapshottable-tester-bplrn": Phase="Pending", Reason="", readiness=false. Elapsed: 51.336253ms
Jun 11 16:24:11.691: INFO: Pod "pvc-snapshottable-tester-bplrn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.103941769s
Jun 11 16:24:13.744: INFO: Pod "pvc-snapshottable-tester-bplrn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.157080163s
Jun 11 16:24:15.797: INFO: Pod "pvc-snapshottable-tester-bplrn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.209624039s
Jun 11 16:24:17.848: INFO: Pod "pvc-snapshottable-tester-bplrn": Phase="Pending", Reason="", readiness=false. Elapsed: 8.261120043s
Jun 11 16:24:19.902: INFO: Pod "pvc-snapshottable-tester-bplrn": Phase="Pending", Reason="", readiness=false. Elapsed: 10.314615403s
Jun 11 16:24:21.955: INFO: Pod "pvc-snapshottable-tester-bplrn": Phase="Pending", Reason="", readiness=false. Elapsed: 12.367331578s
Jun 11 16:24:24.006: INFO: Pod "pvc-snapshottable-tester-bplrn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.419102202s
STEP: Saw pod success
Jun 11 16:24:24.006: INFO: Pod "pvc-snapshottable-tester-bplrn" satisfied condition "Succeeded or Failed"
Jun 11 16:24:24.111: INFO: Pod pvc-snapshottable-tester-bplrn has the following logs: 
Jun 11 16:24:24.111: INFO: Deleting pod "pvc-snapshottable-tester-bplrn" in namespace "snapshotting-5172"
Jun 11 16:24:24.167: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-bplrn" to be fully deleted
Jun 11 16:24:24.218: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comhl7pp] to have phase Bound
Jun 11 16:24:24.270: INFO: PersistentVolumeClaim ebs.csi.aws.comhl7pp found and phase=Bound (51.322976ms)
STEP: [init] checking the claim
... skipping 20 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:243
STEP: checking the snapshot
STEP: checking the SnapshotContent
STEP: Modifying source data test
STEP: modifying the data in the source PVC
Jun 11 16:24:45.392: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-s4l56" in namespace "snapshotting-5172" to be "Succeeded or Failed"
Jun 11 16:24:45.443: INFO: Pod "pvc-snapshottable-data-tester-s4l56": Phase="Pending", Reason="", readiness=false. Elapsed: 51.226819ms
Jun 11 16:24:47.495: INFO: Pod "pvc-snapshottable-data-tester-s4l56": Phase="Pending", Reason="", readiness=false. Elapsed: 2.102928248s
Jun 11 16:24:49.547: INFO: Pod "pvc-snapshottable-data-tester-s4l56": Phase="Pending", Reason="", readiness=false. Elapsed: 4.155382361s
Jun 11 16:24:51.607: INFO: Pod "pvc-snapshottable-data-tester-s4l56": Phase="Pending", Reason="", readiness=false. Elapsed: 6.214659911s
Jun 11 16:24:53.659: INFO: Pod "pvc-snapshottable-data-tester-s4l56": Phase="Pending", Reason="", readiness=false. Elapsed: 8.267218356s
Jun 11 16:24:55.712: INFO: Pod "pvc-snapshottable-data-tester-s4l56": Phase="Pending", Reason="", readiness=false. Elapsed: 10.319634048s
Jun 11 16:24:57.764: INFO: Pod "pvc-snapshottable-data-tester-s4l56": Phase="Pending", Reason="", readiness=false. Elapsed: 12.371936216s
Jun 11 16:24:59.816: INFO: Pod "pvc-snapshottable-data-tester-s4l56": Phase="Pending", Reason="", readiness=false. Elapsed: 14.42390908s
Jun 11 16:25:01.868: INFO: Pod "pvc-snapshottable-data-tester-s4l56": Phase="Pending", Reason="", readiness=false. Elapsed: 16.475834151s
Jun 11 16:25:03.920: INFO: Pod "pvc-snapshottable-data-tester-s4l56": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.528142662s
STEP: Saw pod success
Jun 11 16:25:03.920: INFO: Pod "pvc-snapshottable-data-tester-s4l56" satisfied condition "Succeeded or Failed"
Jun 11 16:25:04.025: INFO: Pod pvc-snapshottable-data-tester-s4l56 has the following logs: 
Jun 11 16:25:04.025: INFO: Deleting pod "pvc-snapshottable-data-tester-s4l56" in namespace "snapshotting-5172"
Jun 11 16:25:04.083: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-s4l56" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 11 16:25:18.347: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-5172 exec restored-pvc-tester-7httc --namespace=snapshotting-5172 -- cat /mnt/test/data'
... skipping 49 lines ...
Jun 11 16:26:05.120: INFO: At 2021-06-11 16:25:07 +0000 UTC - event for pvc-m9gtd: {ebs.csi.aws.com_ebs-csi-controller-7ffff4ddf5-zgctp_7b75c306-7a03-4dcf-94cc-158e69cda478 } ProvisioningSucceeded: Successfully provisioned volume pvc-0bbe2293-7c4b-47f3-8800-fef6e7122403
Jun 11 16:26:05.120: INFO: At 2021-06-11 16:25:10 +0000 UTC - event for restored-pvc-tester-7httc: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-0bbe2293-7c4b-47f3-8800-fef6e7122403" 
Jun 11 16:26:05.120: INFO: At 2021-06-11 16:25:16 +0000 UTC - event for restored-pvc-tester-7httc: {kubelet ip-172-20-40-55.us-west-1.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" already present on machine
Jun 11 16:26:05.120: INFO: At 2021-06-11 16:25:16 +0000 UTC - event for restored-pvc-tester-7httc: {kubelet ip-172-20-40-55.us-west-1.compute.internal} Created: Created container volume-tester
Jun 11 16:26:05.120: INFO: At 2021-06-11 16:25:16 +0000 UTC - event for restored-pvc-tester-7httc: {kubelet ip-172-20-40-55.us-west-1.compute.internal} Started: Started container volume-tester
Jun 11 16:26:05.120: INFO: At 2021-06-11 16:25:19 +0000 UTC - event for restored-pvc-tester-7httc: {kubelet ip-172-20-40-55.us-west-1.compute.internal} Killing: Stopping container volume-tester
Jun 11 16:26:05.120: INFO: At 2021-06-11 16:25:55 +0000 UTC - event for snapshot-5w7dp: {snapshot-controller } SnapshotFinalizerError: Failed to check and update snapshot: snapshot controller failed to update snapshotting-5172/snapshot-5w7dp on API server: Operation cannot be fulfilled on volumesnapshots.snapshot.storage.k8s.io "snapshot-5w7dp": the object has been modified; please apply your changes to the latest version and try again
Jun 11 16:26:05.171: INFO: POD  NODE  PHASE  GRACE  CONDITIONS
Jun 11 16:26:05.171: INFO: 
Jun 11 16:26:05.224: INFO: 
Logging node info for node ip-172-20-40-55.us-west-1.compute.internal
Jun 11 16:26:05.275: INFO: Node Info: &Node{ObjectMeta:{ip-172-20-40-55.us-west-1.compute.internal    97e3b1a0-e374-4b43-9cd0-f75e76255d2d 9846 0 2021-06-11 16:17:24 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:t3.medium beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:us-west-1 failure-domain.beta.kubernetes.io/zone:us-west-1a kops.k8s.io/instancegroup:nodes-us-west-1a kubernetes.io/arch:amd64 kubernetes.io/hostname:ip-172-20-40-55.us-west-1.compute.internal kubernetes.io/os:linux kubernetes.io/role:node node-role.kubernetes.io/node: node.kubernetes.io/instance-type:t3.medium topology.ebs.csi.aws.com/zone:us-west-1a topology.kubernetes.io/region:us-west-1 topology.kubernetes.io/zone:us-west-1a] map[csi.volume.kubernetes.io/nodeid:{"ebs.csi.aws.com":"i-0904333f4b3ec64fb"} node.alpha.kubernetes.io/ttl:0 projectcalico.org/IPv4Address:172.20.40.55/19 projectcalico.org/IPv4IPIPTunnelAddr:100.117.128.64 volumes.kubernetes.io/controller-managed-attach-detach:true] [] []  [{kops-controller Update v1 2021-06-11 16:17:24 +0000 UTC FieldsV1 {"f:metadata":{"f:labels":{"f:kops.k8s.io/instancegroup":{},"f:kubernetes.io/role":{},"f:node-role.kubernetes.io/node":{}}}}} {calico-node Update v1 2021-06-11 16:17:49 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4IPIPTunnelAddr":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}}} {kubelet Update v1 2021-06-11 16:21:44 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:csi.volume.kubernetes.io/nodeid":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.ebs.csi.aws.com/zone":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}},"f:status":{"f:allocatable":{"f:ephemeral-storage":{}},"f:capacity":{"f:ephemeral-storage":{}},"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{},"f:volumesInUse":{}}}} {kube-controller-manager Update v1 2021-06-11 16:24:00 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"100.96.2.0/24\"":{}}},"f:status":{"f:volumesAttached":{}}}}]},Spec:NodeSpec{PodCIDR:100.96.2.0/24,DoNotUseExternalID:,ProviderID:aws:///us-west-1a/i-0904333f4b3ec64fb,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[100.96.2.0/24],},Status:NodeStatus{Capacity:ResourceList{cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{49895047168 0} {<nil>}  BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{4064759808 0} {<nil>} 3969492Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{44905542377 0} {<nil>} 44905542377 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{3959902208 0} {<nil>} 3867092Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2021-06-11 16:17:48 +0000 UTC,LastTransitionTime:2021-06-11 16:17:48 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2021-06-11 16:26:04 +0000 UTC,LastTransitionTime:2021-06-11 16:17:24 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2021-06-11 16:26:04 +0000 UTC,LastTransitionTime:2021-06-11 16:17:24 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2021-06-11 16:26:04 +0000 UTC,LastTransitionTime:2021-06-11 16:17:24 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2021-06-11 16:26:04 +0000 UTC,LastTransitionTime:2021-06-11 16:17:44 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:172.20.40.55,},NodeAddress{Type:ExternalIP,Address:52.53.186.111,},NodeAddress{Type:Hostname,Address:ip-172-20-40-55.us-west-1.compute.internal,},NodeAddress{Type:InternalDNS,Address:ip-172-20-40-55.us-west-1.compute.internal,},NodeAddress{Type:ExternalDNS,Address:ec2-52-53-186-111.us-west-1.compute.amazonaws.com,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:ec241214053840fffe1dffdf9a8f95f3,SystemUUID:ec241214-0538-40ff-fe1d-ffdf9a8f95f3,BootID:a46fec45-e4b0-4754-b837-80f541e063d2,KernelVersion:5.4.0-1045-aws,OSImage:Ubuntu 20.04.2 LTS,ContainerRuntimeVersion:containerd://1.4.6,KubeletVersion:v1.21.0,KubeProxyVersion:v1.21.0,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[k8s.gcr.io/provider-aws/aws-ebs-csi-driver@sha256:a0294bf95fd94eabdc9b313b6c16232019a8707c711c031a2f99ab1f919560bd k8s.gcr.io/provider-aws/aws-ebs-csi-driver:v1.0.0],SizeBytes:67079979,},ContainerImage{Names:[docker.io/calico/node@sha256:bc4a631d553b38fdc169ea4cb8027fa894a656e80d68d513359a4b9d46836b55 docker.io/calico/node:v3.19.1],SizeBytes:58671776,},ContainerImage{Names:[k8s.gcr.io/kube-proxy@sha256:326199e7a5232bf7531a3058e9811c925b07085f33fa882558cc4e89379b9109 k8s.gcr.io/kube-proxy:v1.21.0],SizeBytes:50134170,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/agnhost@sha256:8bd76a6a7778e203b61e18e5ee85b1faf52e6a30eb07e445a165ab90fe9633e3 k8s.gcr.io/e2e-test-images/agnhost:2.31],SizeBytes:49692421,},ContainerImage{Names:[docker.io/calico/cni@sha256:f301171be0add870152483fcce71b28cafb8e910f61ff003032e9b1053b062c4 docker.io/calico/cni:v3.19.1],SizeBytes:48338203,},ContainerImage{Names:[k8s.gcr.io/build-image/debian-iptables@sha256:abe8cef9e116f2d5ec1175c386e33841ff3386779138b425af876384b0fd7ccb k8s.gcr.io/build-image/debian-iptables:buster-v1.5.0],SizeBytes:38088315,},ContainerImage{Names:[k8s.gcr.io/sig-storage/snapshot-validation-webhook@sha256:931a753e6428914f5393e3bba5f250f952c57dc2e9ddd16c37593a8f02b6715e k8s.gcr.io/sig-storage/snapshot-validation-webhook:v4.1.1],SizeBytes:18566421,},ContainerImage{Names:[docker.io/calico/pod2daemon-flexvol@sha256:bcac7dc4f1301b062d91a177a52d13716907636975c44131fb8350e7f851c944 docker.io/calico/pod2daemon-flexvol:v3.19.1],SizeBytes:9328155,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-node-driver-registrar@sha256:a61d309da54641db41fb8f35718f744e9f730d4d0384f8c4b186ddc9f06cbd5f k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.1.0],SizeBytes:9068367,},ContainerImage{Names:[k8s.gcr.io/sig-storage/livenessprobe@sha256:48da0e4ed7238ad461ea05f68c25921783c37b315f21a5c5a2780157a6460994 k8s.gcr.io/sig-storage/livenessprobe:v2.2.0],SizeBytes:8279778,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/nginx@sha256:503b7abb89e57383eba61cc8a9cb0b495ea575c516108f7d972a6ff6e1ab3c9b k8s.gcr.io/e2e-test-images/nginx:1.14-1],SizeBytes:6979365,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/busybox@sha256:39e1e963e5310e9c313bad51523be012ede7b35bb9316517d19089a010356592 k8s.gcr.io/e2e-test-images/busybox:1.29-1],SizeBytes:732746,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:927d98197ec1141a368550822d18fa1c60bdae27b78b0c004f705f548c07814f k8s.gcr.io/pause:3.2],SizeBytes:299513,},},VolumesInUse:[kubernetes.io/csi/ebs.csi.aws.com^vol-0560b57c3492c7afe kubernetes.io/csi/ebs.csi.aws.com^vol-058665e2629a5ef03 kubernetes.io/csi/ebs.csi.aws.com^vol-0a72e243ea45eeacb],VolumesAttached:[]AttachedVolume{AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-0560b57c3492c7afe,DevicePath:,},},Config:nil,},}
Jun 11 16:26:05.276: INFO: 
... skipping 193 lines ...
    /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:108
      
      /tmp/kops.xDG68BsTe/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.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:243

        Unexpected error:
            <exec.CodeExitError>: {
                Err: {
                    s: "error running /usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-5172 exec restored-pvc-tester-7httc --namespace=snapshotting-5172 -- cat /mnt/test/data:\nCommand stdout:\n\nstderr:\ncat: can't open '/mnt/test/data': No such file or directory\ncommand terminated with exit code 1\n\nerror:\nexit status 1",
                },
                Code: 1,
            }
            error running /usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-5172 exec restored-pvc-tester-7httc --namespace=snapshotting-5172 -- 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.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:602
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] provisioning
... skipping 109 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.xDG68BsTe/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.xDG68BsTe/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.xDG68BsTe/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.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 55 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 16:25:53.458: 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.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 11 16:25:53.709: INFO: Creating resource for dynamic PV
Jun 11 16:25:53.709: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-1016-e2e-sc97gd5
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 11 16:26:00.080: INFO: Deleting pod "pod-65a46f86-3b92-4f3c-862e-20970b993660" in namespace "volumemode-1016"
Jun 11 16:26:00.133: INFO: Wait up to 5m0s for pod "pod-65a46f86-3b92-4f3c-862e-20970b993660" to be fully deleted
STEP: Deleting pvc
Jun 11 16:26:06.335: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comnspdc"
Jun 11 16:26:06.387: INFO: Waiting up to 5m0s for PersistentVolume pvc-26d83c03-d65d-4d67-800c-4e10718d2cb9 to get deleted
Jun 11 16:26:06.437: INFO: PersistentVolume pvc-26d83c03-d65d-4d67-800c-4e10718d2cb9 found and phase=Released (49.995121ms)
... skipping 9 lines ...

• [SLOW TEST:28.309 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.xDG68BsTe/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.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 72 lines ...
Jun 11 16:25:37.983: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 11 16:25:38.289: INFO: Successfully created a new PD: "aws://us-west-1a/vol-00d12be009105d110".
Jun 11 16:25:38.289: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-lkl2
STEP: Creating a pod to test exec-volume-test
Jun 11 16:25:38.345: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-lkl2" in namespace "volume-3917" to be "Succeeded or Failed"
Jun 11 16:25:38.396: INFO: Pod "exec-volume-test-inlinevolume-lkl2": Phase="Pending", Reason="", readiness=false. Elapsed: 50.704575ms
Jun 11 16:25:40.446: INFO: Pod "exec-volume-test-inlinevolume-lkl2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.101071437s
Jun 11 16:25:42.500: INFO: Pod "exec-volume-test-inlinevolume-lkl2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.154828257s
Jun 11 16:25:44.557: INFO: Pod "exec-volume-test-inlinevolume-lkl2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.212214382s
Jun 11 16:25:46.608: INFO: Pod "exec-volume-test-inlinevolume-lkl2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.263345353s
Jun 11 16:25:48.660: INFO: Pod "exec-volume-test-inlinevolume-lkl2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.314997168s
Jun 11 16:25:50.711: INFO: Pod "exec-volume-test-inlinevolume-lkl2": Phase="Pending", Reason="", readiness=false. Elapsed: 12.366076682s
Jun 11 16:25:52.762: INFO: Pod "exec-volume-test-inlinevolume-lkl2": Phase="Pending", Reason="", readiness=false. Elapsed: 14.417559773s
Jun 11 16:25:54.813: INFO: Pod "exec-volume-test-inlinevolume-lkl2": Phase="Pending", Reason="", readiness=false. Elapsed: 16.468503117s
Jun 11 16:25:56.865: INFO: Pod "exec-volume-test-inlinevolume-lkl2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.519630907s
STEP: Saw pod success
Jun 11 16:25:56.865: INFO: Pod "exec-volume-test-inlinevolume-lkl2" satisfied condition "Succeeded or Failed"
Jun 11 16:25:56.916: INFO: Trying to get logs from node ip-172-20-40-55.us-west-1.compute.internal pod exec-volume-test-inlinevolume-lkl2 container exec-container-inlinevolume-lkl2: <nil>
STEP: delete the pod
Jun 11 16:25:57.027: INFO: Waiting for pod exec-volume-test-inlinevolume-lkl2 to disappear
Jun 11 16:25:57.078: INFO: Pod exec-volume-test-inlinevolume-lkl2 no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-lkl2
Jun 11 16:25:57.078: INFO: Deleting pod "exec-volume-test-inlinevolume-lkl2" in namespace "volume-3917"
Jun 11 16:25:57.264: INFO: Couldn't delete PD "aws://us-west-1a/vol-00d12be009105d110", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00d12be009105d110 is currently attached to i-0904333f4b3ec64fb
	status code: 400, request id: ca3af634-a558-4426-95a7-56bd2007be22
Jun 11 16:26:02.633: INFO: Couldn't delete PD "aws://us-west-1a/vol-00d12be009105d110", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00d12be009105d110 is currently attached to i-0904333f4b3ec64fb
	status code: 400, request id: 8c32892c-4e4a-415b-b253-184bfbb582e3
Jun 11 16:26:07.990: INFO: Couldn't delete PD "aws://us-west-1a/vol-00d12be009105d110", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00d12be009105d110 is currently attached to i-0904333f4b3ec64fb
	status code: 400, request id: 15921abc-a587-49eb-80e0-8ab21f578e36
Jun 11 16:26:13.323: INFO: Couldn't delete PD "aws://us-west-1a/vol-00d12be009105d110", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00d12be009105d110 is currently attached to i-0904333f4b3ec64fb
	status code: 400, request id: b75d2d68-8ee5-43d1-bd4b-5e3da6e3446a
Jun 11 16:26:18.717: INFO: Couldn't delete PD "aws://us-west-1a/vol-00d12be009105d110", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00d12be009105d110 is currently attached to i-0904333f4b3ec64fb
	status code: 400, request id: 1a16d046-6a16-4ed2-a0f4-dd8bf2e4a3c8
Jun 11 16:26:24.070: INFO: Successfully deleted PD "aws://us-west-1a/vol-00d12be009105d110".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 16:26:24.070: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-3917" for this suite.
... skipping 16 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 16:25:34.127: 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.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 11 16:25:34.389: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 11 16:25:34.884: INFO: Successfully created a new PD: "aws://us-west-1a/vol-05a7823a4f8fa0f03".
Jun 11 16:25:34.884: INFO: Creating resource for pre-provisioned PV
Jun 11 16:25:34.884: INFO: Creating PVC and PV
... skipping 4 lines ...
Jun 11 16:25:37.189: INFO: PersistentVolumeClaim pvc-6zxqv found but phase is Pending instead of Bound.
Jun 11 16:25:39.244: INFO: PersistentVolumeClaim pvc-6zxqv found but phase is Pending instead of Bound.
Jun 11 16:25:41.297: INFO: PersistentVolumeClaim pvc-6zxqv found and phase=Bound (6.213690697s)
Jun 11 16:25:41.297: INFO: Waiting up to 3m0s for PersistentVolume aws-4xk7k to have phase Bound
Jun 11 16:25:41.349: INFO: PersistentVolume aws-4xk7k found and phase=Bound (52.099571ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 11 16:25:43.664: INFO: Deleting pod "pod-f1115f2c-8ab3-47ca-a6fd-0559f833c327" in namespace "volumemode-8950"
Jun 11 16:25:43.720: INFO: Wait up to 5m0s for pod "pod-f1115f2c-8ab3-47ca-a6fd-0559f833c327" to be fully deleted
STEP: Deleting pv and pvc
Jun 11 16:25:51.826: INFO: Deleting PersistentVolumeClaim "pvc-6zxqv"
Jun 11 16:25:51.883: INFO: Deleting PersistentVolume "aws-4xk7k"
Jun 11 16:25:52.091: INFO: Couldn't delete PD "aws://us-west-1a/vol-05a7823a4f8fa0f03", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05a7823a4f8fa0f03 is currently attached to i-02fd57ac3b1f478ed
	status code: 400, request id: d37ab3b6-0505-43fd-9518-0d939f2d0c89
Jun 11 16:25:57.430: INFO: Couldn't delete PD "aws://us-west-1a/vol-05a7823a4f8fa0f03", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05a7823a4f8fa0f03 is currently attached to i-02fd57ac3b1f478ed
	status code: 400, request id: c3fc3197-dcfe-409b-9215-215cae03346a
Jun 11 16:26:02.778: INFO: Couldn't delete PD "aws://us-west-1a/vol-05a7823a4f8fa0f03", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05a7823a4f8fa0f03 is currently attached to i-02fd57ac3b1f478ed
	status code: 400, request id: de3c3b19-3238-4983-8944-8dc9b4ce0a98
Jun 11 16:26:08.092: INFO: Couldn't delete PD "aws://us-west-1a/vol-05a7823a4f8fa0f03", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05a7823a4f8fa0f03 is currently attached to i-02fd57ac3b1f478ed
	status code: 400, request id: cdf91eea-b758-4ea6-939b-f34182f4a8bb
Jun 11 16:26:13.483: INFO: Couldn't delete PD "aws://us-west-1a/vol-05a7823a4f8fa0f03", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05a7823a4f8fa0f03 is currently attached to i-02fd57ac3b1f478ed
	status code: 400, request id: 7322bc4d-19d7-4609-a9d5-f70933c8bc86
Jun 11 16:26:18.936: INFO: Couldn't delete PD "aws://us-west-1a/vol-05a7823a4f8fa0f03", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05a7823a4f8fa0f03 is currently attached to i-02fd57ac3b1f478ed
	status code: 400, request id: 601503e3-1b5a-45ba-aa80-5214f8f80427
Jun 11 16:26:24.322: INFO: Successfully deleted PD "aws://us-west-1a/vol-05a7823a4f8fa0f03".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 16:26:24.322: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-8950" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.xDG68BsTe/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.xDG68BsTe/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
    /tmp/kops.xDG68BsTe/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.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeLimits
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
... skipping 462 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail to schedule a pod which has topologies that conflict with AllowedTopologies [BeforeEach]
    /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

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

    /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:92
------------------------------
... skipping 340 lines ...
Jun 11 16:24:43.551: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-434jtgzm      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-434    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-434jtgzm,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-434    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-434jtgzm,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-434    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-434jtgzm,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-434jtgzm    01cf6929-5d2c-4a0a-8fb4-a11c4de2c09d 7407 0 2021-06-11 16:24:43 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-11 16:24:43 +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-rmz7d pvc- provisioning-434  bae8cd1d-1bda-4610-a58c-8e74184d5ffa 7411 0 2021-06-11 16:24:43 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-11 16:24:43 +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-434jtgzm,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-9b04c1c5-7a25-4e4e-914f-440ebb0d1de4 in namespace provisioning-434
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun 11 16:25:14.146: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-kvqp2" in namespace "provisioning-434" to be "Succeeded or Failed"
Jun 11 16:25:14.199: INFO: Pod "pvc-volume-tester-writer-kvqp2": Phase="Pending", Reason="", readiness=false. Elapsed: 52.669382ms
Jun 11 16:25:16.252: INFO: Pod "pvc-volume-tester-writer-kvqp2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.106193856s
Jun 11 16:25:18.306: INFO: Pod "pvc-volume-tester-writer-kvqp2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.160177195s
Jun 11 16:25:20.360: INFO: Pod "pvc-volume-tester-writer-kvqp2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.21372825s
Jun 11 16:25:22.414: INFO: Pod "pvc-volume-tester-writer-kvqp2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.267548485s
Jun 11 16:25:24.466: INFO: Pod "pvc-volume-tester-writer-kvqp2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.320027968s
... skipping 22 lines ...
Jun 11 16:26:11.701: INFO: Pod "pvc-volume-tester-writer-kvqp2": Phase="Pending", Reason="", readiness=false. Elapsed: 57.554539543s
Jun 11 16:26:13.755: INFO: Pod "pvc-volume-tester-writer-kvqp2": Phase="Pending", Reason="", readiness=false. Elapsed: 59.608895412s
Jun 11 16:26:15.808: INFO: Pod "pvc-volume-tester-writer-kvqp2": Phase="Pending", Reason="", readiness=false. Elapsed: 1m1.662211419s
Jun 11 16:26:17.861: INFO: Pod "pvc-volume-tester-writer-kvqp2": Phase="Pending", Reason="", readiness=false. Elapsed: 1m3.715040021s
Jun 11 16:26:19.914: INFO: Pod "pvc-volume-tester-writer-kvqp2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m5.767602468s
STEP: Saw pod success
Jun 11 16:26:19.914: INFO: Pod "pvc-volume-tester-writer-kvqp2" satisfied condition "Succeeded or Failed"
Jun 11 16:26:20.020: INFO: Pod pvc-volume-tester-writer-kvqp2 has the following logs: 
Jun 11 16:26:20.020: INFO: Deleting pod "pvc-volume-tester-writer-kvqp2" in namespace "provisioning-434"
Jun 11 16:26:20.079: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-kvqp2" 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-56-114.us-west-1.compute.internal"
Jun 11 16:26:20.292: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-qrr9b" in namespace "provisioning-434" to be "Succeeded or Failed"
Jun 11 16:26:20.344: INFO: Pod "pvc-volume-tester-reader-qrr9b": Phase="Pending", Reason="", readiness=false. Elapsed: 51.996818ms
Jun 11 16:26:22.397: INFO: Pod "pvc-volume-tester-reader-qrr9b": Phase="Pending", Reason="", readiness=false. Elapsed: 2.104385471s
Jun 11 16:26:24.453: INFO: Pod "pvc-volume-tester-reader-qrr9b": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.160269864s
STEP: Saw pod success
Jun 11 16:26:24.453: INFO: Pod "pvc-volume-tester-reader-qrr9b" satisfied condition "Succeeded or Failed"
Jun 11 16:26:24.561: INFO: Pod pvc-volume-tester-reader-qrr9b has the following logs: hello world

Jun 11 16:26:24.561: INFO: Deleting pod "pvc-volume-tester-reader-qrr9b" in namespace "provisioning-434"
Jun 11 16:26:24.620: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-qrr9b" to be fully deleted
Jun 11 16:26:24.672: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-rmz7d] to have phase Bound
Jun 11 16:26:24.724: INFO: PersistentVolumeClaim pvc-rmz7d found and phase=Bound (51.993579ms)
... skipping 30 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 16:25:31.683: 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.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 11 16:25:31.942: INFO: Creating resource for dynamic PV
Jun 11 16:25:31.942: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-1119-e2e-scncw2p
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 11 16:25:38.311: INFO: Deleting pod "pod-ace54712-3390-4d74-ac5e-b0ebde4e1d8b" in namespace "volumemode-1119"
Jun 11 16:25:38.365: INFO: Wait up to 5m0s for pod "pod-ace54712-3390-4d74-ac5e-b0ebde4e1d8b" to be fully deleted
STEP: Deleting pvc
Jun 11 16:25:42.575: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comzmm8f"
Jun 11 16:25:42.629: INFO: Waiting up to 5m0s for PersistentVolume pvc-3d92a436-6cc3-4b98-b00f-bbada78bacec to get deleted
Jun 11 16:25:42.682: INFO: PersistentVolume pvc-3d92a436-6cc3-4b98-b00f-bbada78bacec found and phase=Released (53.321769ms)
... skipping 19 lines ...

• [SLOW TEST:76.838 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.xDG68BsTe/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.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 174 lines ...
Jun 11 16:24:15.678: INFO: Creating resource for dynamic PV
Jun 11 16:24:15.678: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-3839-e2e-sc22jm2
STEP: creating a claim
Jun 11 16:24:15.731: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 11 16:24:15.889: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-xx4qw" in namespace "snapshotting-3839" to be "Succeeded or Failed"
Jun 11 16:24:15.946: INFO: Pod "pvc-snapshottable-tester-xx4qw": Phase="Pending", Reason="", readiness=false. Elapsed: 56.540796ms
Jun 11 16:24:17.997: INFO: Pod "pvc-snapshottable-tester-xx4qw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.108105134s
Jun 11 16:24:20.050: INFO: Pod "pvc-snapshottable-tester-xx4qw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.161208329s
Jun 11 16:24:22.102: INFO: Pod "pvc-snapshottable-tester-xx4qw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.212980857s
Jun 11 16:24:24.155: INFO: Pod "pvc-snapshottable-tester-xx4qw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.265721368s
Jun 11 16:24:26.208: INFO: Pod "pvc-snapshottable-tester-xx4qw": Phase="Pending", Reason="", readiness=false. Elapsed: 10.318439623s
Jun 11 16:24:28.260: INFO: Pod "pvc-snapshottable-tester-xx4qw": Phase="Pending", Reason="", readiness=false. Elapsed: 12.371242033s
Jun 11 16:24:30.313: INFO: Pod "pvc-snapshottable-tester-xx4qw": Phase="Pending", Reason="", readiness=false. Elapsed: 14.423582449s
Jun 11 16:24:32.365: INFO: Pod "pvc-snapshottable-tester-xx4qw": Phase="Pending", Reason="", readiness=false. Elapsed: 16.475998122s
Jun 11 16:24:34.425: INFO: Pod "pvc-snapshottable-tester-xx4qw": Phase="Pending", Reason="", readiness=false. Elapsed: 18.53542123s
Jun 11 16:24:36.477: INFO: Pod "pvc-snapshottable-tester-xx4qw": Phase="Pending", Reason="", readiness=false. Elapsed: 20.58754794s
Jun 11 16:24:38.528: INFO: Pod "pvc-snapshottable-tester-xx4qw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.638935565s
STEP: Saw pod success
Jun 11 16:24:38.528: INFO: Pod "pvc-snapshottable-tester-xx4qw" satisfied condition "Succeeded or Failed"
Jun 11 16:24:38.632: INFO: Pod pvc-snapshottable-tester-xx4qw has the following logs: 
Jun 11 16:24:38.632: INFO: Deleting pod "pvc-snapshottable-tester-xx4qw" in namespace "snapshotting-3839"
Jun 11 16:24:38.692: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-xx4qw" to be fully deleted
Jun 11 16:24:38.743: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comrwwv9] to have phase Bound
Jun 11 16:24:38.794: INFO: PersistentVolumeClaim ebs.csi.aws.comrwwv9 found and phase=Bound (51.590168ms)
STEP: [init] checking the claim
... skipping 25 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:243
STEP: checking the snapshot
STEP: checking the SnapshotContent
STEP: Modifying source data test
STEP: modifying the data in the source PVC
Jun 11 16:25:10.185: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-wvdcs" in namespace "snapshotting-3839" to be "Succeeded or Failed"
Jun 11 16:25:10.237: INFO: Pod "pvc-snapshottable-data-tester-wvdcs": Phase="Pending", Reason="", readiness=false. Elapsed: 51.172691ms
Jun 11 16:25:12.289: INFO: Pod "pvc-snapshottable-data-tester-wvdcs": Phase="Pending", Reason="", readiness=false. Elapsed: 2.103476606s
Jun 11 16:25:14.342: INFO: Pod "pvc-snapshottable-data-tester-wvdcs": Phase="Pending", Reason="", readiness=false. Elapsed: 4.156364436s
Jun 11 16:25:16.393: INFO: Pod "pvc-snapshottable-data-tester-wvdcs": Phase="Pending", Reason="", readiness=false. Elapsed: 6.207805022s
Jun 11 16:25:18.445: INFO: Pod "pvc-snapshottable-data-tester-wvdcs": Phase="Pending", Reason="", readiness=false. Elapsed: 8.260040011s
Jun 11 16:25:20.497: INFO: Pod "pvc-snapshottable-data-tester-wvdcs": Phase="Pending", Reason="", readiness=false. Elapsed: 10.31155477s
Jun 11 16:25:22.549: INFO: Pod "pvc-snapshottable-data-tester-wvdcs": Phase="Pending", Reason="", readiness=false. Elapsed: 12.363391882s
Jun 11 16:25:24.601: INFO: Pod "pvc-snapshottable-data-tester-wvdcs": Phase="Pending", Reason="", readiness=false. Elapsed: 14.415259416s
Jun 11 16:25:26.653: INFO: Pod "pvc-snapshottable-data-tester-wvdcs": Phase="Pending", Reason="", readiness=false. Elapsed: 16.467618263s
Jun 11 16:25:28.706: INFO: Pod "pvc-snapshottable-data-tester-wvdcs": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.520376334s
STEP: Saw pod success
Jun 11 16:25:28.706: INFO: Pod "pvc-snapshottable-data-tester-wvdcs" satisfied condition "Succeeded or Failed"
Jun 11 16:25:28.810: INFO: Pod pvc-snapshottable-data-tester-wvdcs has the following logs: 
Jun 11 16:25:28.810: INFO: Deleting pod "pvc-snapshottable-data-tester-wvdcs" in namespace "snapshotting-3839"
Jun 11 16:25:28.871: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-wvdcs" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 11 16:26:07.137: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-3839 exec restored-pvc-tester-22tlm --namespace=snapshotting-3839 -- cat /mnt/test/data'
... skipping 141 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 16:26:24.808: 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.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 11 16:26:25.074: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 11 16:26:25.424: INFO: Successfully created a new PD: "aws://us-west-1a/vol-055d8f44e6188ab1d".
Jun 11 16:26:25.424: INFO: Creating resource for pre-provisioned PV
Jun 11 16:26:25.424: INFO: Creating PVC and PV
... skipping 8 lines ...
Jun 11 16:26:35.939: INFO: PersistentVolumeClaim pvc-7pgpv found but phase is Pending instead of Bound.
Jun 11 16:26:37.992: INFO: PersistentVolumeClaim pvc-7pgpv found but phase is Pending instead of Bound.
Jun 11 16:26:40.046: INFO: PersistentVolumeClaim pvc-7pgpv found and phase=Bound (14.437717683s)
Jun 11 16:26:40.046: INFO: Waiting up to 3m0s for PersistentVolume aws-grkv4 to have phase Bound
Jun 11 16:26:40.099: INFO: PersistentVolume aws-grkv4 found and phase=Bound (52.288693ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 11 16:26:42.419: INFO: Deleting pod "pod-9e4b8b53-24bf-4726-b17d-f8ba8caf8579" in namespace "volumemode-4355"
Jun 11 16:26:42.474: INFO: Wait up to 5m0s for pod "pod-9e4b8b53-24bf-4726-b17d-f8ba8caf8579" to be fully deleted
STEP: Deleting pv and pvc
Jun 11 16:26:46.581: INFO: Deleting PersistentVolumeClaim "pvc-7pgpv"
Jun 11 16:26:46.635: INFO: Deleting PersistentVolume "aws-grkv4"
Jun 11 16:26:46.837: INFO: Couldn't delete PD "aws://us-west-1a/vol-055d8f44e6188ab1d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-055d8f44e6188ab1d is currently attached to i-0904333f4b3ec64fb
	status code: 400, request id: 100170c0-c427-418d-8650-15bec77b9634
Jun 11 16:26:52.178: INFO: Couldn't delete PD "aws://us-west-1a/vol-055d8f44e6188ab1d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-055d8f44e6188ab1d is currently attached to i-0904333f4b3ec64fb
	status code: 400, request id: 379f0d21-f524-49f2-b995-76497aecb1d8
Jun 11 16:26:57.492: INFO: Couldn't delete PD "aws://us-west-1a/vol-055d8f44e6188ab1d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-055d8f44e6188ab1d is currently attached to i-0904333f4b3ec64fb
	status code: 400, request id: 8d1b3f39-1200-4e8d-8904-96811b06e203
Jun 11 16:27:02.889: INFO: Successfully deleted PD "aws://us-west-1a/vol-055d8f44e6188ab1d".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 16:27:02.889: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-4355" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.xDG68BsTe/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.xDG68BsTe/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
    /tmp/kops.xDG68BsTe/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.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 11 16:27:02.998: INFO: Driver supports dynamic provisioning, skipping PreprovisionedPV pattern
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
... skipping 49 lines ...
Jun 11 16:26:08.682: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-578-e2e-scn2hmp
STEP: creating a claim
Jun 11 16:26:08.735: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-9vvl
STEP: Creating a pod to test subpath
Jun 11 16:26:08.891: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-9vvl" in namespace "provisioning-578" to be "Succeeded or Failed"
Jun 11 16:26:08.944: INFO: Pod "pod-subpath-test-dynamicpv-9vvl": Phase="Pending", Reason="", readiness=false. Elapsed: 53.325977ms
Jun 11 16:26:10.996: INFO: Pod "pod-subpath-test-dynamicpv-9vvl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.104976743s
Jun 11 16:26:13.048: INFO: Pod "pod-subpath-test-dynamicpv-9vvl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.157074749s
Jun 11 16:26:15.101: INFO: Pod "pod-subpath-test-dynamicpv-9vvl": Phase="Pending", Reason="", readiness=false. Elapsed: 6.210005357s
Jun 11 16:26:17.158: INFO: Pod "pod-subpath-test-dynamicpv-9vvl": Phase="Pending", Reason="", readiness=false. Elapsed: 8.267461266s
Jun 11 16:26:19.210: INFO: Pod "pod-subpath-test-dynamicpv-9vvl": Phase="Pending", Reason="", readiness=false. Elapsed: 10.319005357s
... skipping 2 lines ...
Jun 11 16:26:25.373: INFO: Pod "pod-subpath-test-dynamicpv-9vvl": Phase="Pending", Reason="", readiness=false. Elapsed: 16.482191939s
Jun 11 16:26:27.425: INFO: Pod "pod-subpath-test-dynamicpv-9vvl": Phase="Pending", Reason="", readiness=false. Elapsed: 18.534465939s
Jun 11 16:26:29.478: INFO: Pod "pod-subpath-test-dynamicpv-9vvl": Phase="Pending", Reason="", readiness=false. Elapsed: 20.587743816s
Jun 11 16:26:31.531: INFO: Pod "pod-subpath-test-dynamicpv-9vvl": Phase="Pending", Reason="", readiness=false. Elapsed: 22.64054719s
Jun 11 16:26:33.584: INFO: Pod "pod-subpath-test-dynamicpv-9vvl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.692979201s
STEP: Saw pod success
Jun 11 16:26:33.584: INFO: Pod "pod-subpath-test-dynamicpv-9vvl" satisfied condition "Succeeded or Failed"
Jun 11 16:26:33.635: INFO: Trying to get logs from node ip-172-20-40-55.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-9vvl container test-container-subpath-dynamicpv-9vvl: <nil>
STEP: delete the pod
Jun 11 16:26:33.745: INFO: Waiting for pod pod-subpath-test-dynamicpv-9vvl to disappear
Jun 11 16:26:33.795: INFO: Pod pod-subpath-test-dynamicpv-9vvl no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-9vvl
Jun 11 16:26:33.796: INFO: Deleting pod "pod-subpath-test-dynamicpv-9vvl" in namespace "provisioning-578"
... skipping 854 lines ...
Jun 11 16:26:58.694: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 11 16:26:59.195: INFO: Successfully created a new PD: "aws://us-west-1a/vol-04d73e0448a24edfe".
Jun 11 16:26:59.195: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-6ngt
STEP: Creating a pod to test exec-volume-test
Jun 11 16:26:59.249: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-6ngt" in namespace "volume-8266" to be "Succeeded or Failed"
Jun 11 16:26:59.300: INFO: Pod "exec-volume-test-inlinevolume-6ngt": Phase="Pending", Reason="", readiness=false. Elapsed: 51.326963ms
Jun 11 16:27:01.353: INFO: Pod "exec-volume-test-inlinevolume-6ngt": Phase="Pending", Reason="", readiness=false. Elapsed: 2.103653507s
Jun 11 16:27:03.405: INFO: Pod "exec-volume-test-inlinevolume-6ngt": Phase="Pending", Reason="", readiness=false. Elapsed: 4.156349814s
Jun 11 16:27:05.458: INFO: Pod "exec-volume-test-inlinevolume-6ngt": Phase="Pending", Reason="", readiness=false. Elapsed: 6.209048483s
Jun 11 16:27:07.511: INFO: Pod "exec-volume-test-inlinevolume-6ngt": Phase="Pending", Reason="", readiness=false. Elapsed: 8.261576617s
Jun 11 16:27:09.562: INFO: Pod "exec-volume-test-inlinevolume-6ngt": Phase="Pending", Reason="", readiness=false. Elapsed: 10.313221324s
Jun 11 16:27:11.614: INFO: Pod "exec-volume-test-inlinevolume-6ngt": Phase="Pending", Reason="", readiness=false. Elapsed: 12.365502149s
Jun 11 16:27:13.666: INFO: Pod "exec-volume-test-inlinevolume-6ngt": Phase="Pending", Reason="", readiness=false. Elapsed: 14.417142118s
Jun 11 16:27:15.721: INFO: Pod "exec-volume-test-inlinevolume-6ngt": Phase="Pending", Reason="", readiness=false. Elapsed: 16.472482584s
Jun 11 16:27:17.773: INFO: Pod "exec-volume-test-inlinevolume-6ngt": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.524287021s
STEP: Saw pod success
Jun 11 16:27:17.773: INFO: Pod "exec-volume-test-inlinevolume-6ngt" satisfied condition "Succeeded or Failed"
Jun 11 16:27:17.825: INFO: Trying to get logs from node ip-172-20-42-53.us-west-1.compute.internal pod exec-volume-test-inlinevolume-6ngt container exec-container-inlinevolume-6ngt: <nil>
STEP: delete the pod
Jun 11 16:27:17.939: INFO: Waiting for pod exec-volume-test-inlinevolume-6ngt to disappear
Jun 11 16:27:17.991: INFO: Pod exec-volume-test-inlinevolume-6ngt no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-6ngt
Jun 11 16:27:17.991: INFO: Deleting pod "exec-volume-test-inlinevolume-6ngt" in namespace "volume-8266"
Jun 11 16:27:18.243: INFO: Couldn't delete PD "aws://us-west-1a/vol-04d73e0448a24edfe", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04d73e0448a24edfe is currently attached to i-02fd57ac3b1f478ed
	status code: 400, request id: 5cac8063-0d29-45e4-864c-2bc37a543904
Jun 11 16:27:23.599: INFO: Couldn't delete PD "aws://us-west-1a/vol-04d73e0448a24edfe", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04d73e0448a24edfe is currently attached to i-02fd57ac3b1f478ed
	status code: 400, request id: 90361a15-bb7c-48e6-8f31-295f732fd017
Jun 11 16:27:28.997: INFO: Couldn't delete PD "aws://us-west-1a/vol-04d73e0448a24edfe", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04d73e0448a24edfe is currently attached to i-02fd57ac3b1f478ed
	status code: 400, request id: 67781eba-f173-48eb-a874-e36e5a38c2c9
Jun 11 16:27:34.376: INFO: Successfully deleted PD "aws://us-west-1a/vol-04d73e0448a24edfe".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 16:27:34.376: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8266" for this suite.
... skipping 285 lines ...
Jun 11 16:26:53.822: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-902ctt6v
STEP: creating a claim
Jun 11 16:26:53.876: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-hh48
STEP: Creating a pod to test exec-volume-test
Jun 11 16:26:54.038: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-hh48" in namespace "volume-902" to be "Succeeded or Failed"
Jun 11 16:26:54.090: INFO: Pod "exec-volume-test-dynamicpv-hh48": Phase="Pending", Reason="", readiness=false. Elapsed: 52.623962ms
Jun 11 16:26:56.144: INFO: Pod "exec-volume-test-dynamicpv-hh48": Phase="Pending", Reason="", readiness=false. Elapsed: 2.106060641s
Jun 11 16:26:58.196: INFO: Pod "exec-volume-test-dynamicpv-hh48": Phase="Pending", Reason="", readiness=false. Elapsed: 4.15846657s
Jun 11 16:27:00.249: INFO: Pod "exec-volume-test-dynamicpv-hh48": Phase="Pending", Reason="", readiness=false. Elapsed: 6.211517508s
Jun 11 16:27:02.302: INFO: Pod "exec-volume-test-dynamicpv-hh48": Phase="Pending", Reason="", readiness=false. Elapsed: 8.264392173s
Jun 11 16:27:04.357: INFO: Pod "exec-volume-test-dynamicpv-hh48": Phase="Pending", Reason="", readiness=false. Elapsed: 10.319870829s
Jun 11 16:27:06.410: INFO: Pod "exec-volume-test-dynamicpv-hh48": Phase="Pending", Reason="", readiness=false. Elapsed: 12.372517547s
Jun 11 16:27:08.463: INFO: Pod "exec-volume-test-dynamicpv-hh48": Phase="Pending", Reason="", readiness=false. Elapsed: 14.425785704s
Jun 11 16:27:10.521: INFO: Pod "exec-volume-test-dynamicpv-hh48": Phase="Pending", Reason="", readiness=false. Elapsed: 16.48378031s
Jun 11 16:27:12.574: INFO: Pod "exec-volume-test-dynamicpv-hh48": Phase="Pending", Reason="", readiness=false. Elapsed: 18.536181312s
Jun 11 16:27:14.628: INFO: Pod "exec-volume-test-dynamicpv-hh48": Phase="Pending", Reason="", readiness=false. Elapsed: 20.590025844s
Jun 11 16:27:16.681: INFO: Pod "exec-volume-test-dynamicpv-hh48": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.643555981s
STEP: Saw pod success
Jun 11 16:27:16.681: INFO: Pod "exec-volume-test-dynamicpv-hh48" satisfied condition "Succeeded or Failed"
Jun 11 16:27:16.733: INFO: Trying to get logs from node ip-172-20-56-114.us-west-1.compute.internal pod exec-volume-test-dynamicpv-hh48 container exec-container-dynamicpv-hh48: <nil>
STEP: delete the pod
Jun 11 16:27:16.939: INFO: Waiting for pod exec-volume-test-dynamicpv-hh48 to disappear
Jun 11 16:27:16.993: INFO: Pod exec-volume-test-dynamicpv-hh48 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-hh48
Jun 11 16:27:16.993: INFO: Deleting pod "exec-volume-test-dynamicpv-hh48" in namespace "volume-902"
... skipping 254 lines ...
Jun 11 16:27:03.271: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4648-e2e-scg6hcs
STEP: creating a claim
Jun 11 16:27:03.324: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-87lb
STEP: Creating a pod to test multi_subpath
Jun 11 16:27:03.491: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-87lb" in namespace "provisioning-4648" to be "Succeeded or Failed"
Jun 11 16:27:03.543: INFO: Pod "pod-subpath-test-dynamicpv-87lb": Phase="Pending", Reason="", readiness=false. Elapsed: 52.378454ms
Jun 11 16:27:05.596: INFO: Pod "pod-subpath-test-dynamicpv-87lb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.105567504s
Jun 11 16:27:07.649: INFO: Pod "pod-subpath-test-dynamicpv-87lb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.15845056s
Jun 11 16:27:09.703: INFO: Pod "pod-subpath-test-dynamicpv-87lb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.212815772s
Jun 11 16:27:11.756: INFO: Pod "pod-subpath-test-dynamicpv-87lb": Phase="Pending", Reason="", readiness=false. Elapsed: 8.26515678s
Jun 11 16:27:13.809: INFO: Pod "pod-subpath-test-dynamicpv-87lb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.317991249s
STEP: Saw pod success
Jun 11 16:27:13.809: INFO: Pod "pod-subpath-test-dynamicpv-87lb" satisfied condition "Succeeded or Failed"
Jun 11 16:27:13.861: INFO: Trying to get logs from node ip-172-20-42-53.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-87lb container test-container-subpath-dynamicpv-87lb: <nil>
STEP: delete the pod
Jun 11 16:27:13.985: INFO: Waiting for pod pod-subpath-test-dynamicpv-87lb to disappear
Jun 11 16:27:14.037: INFO: Pod pod-subpath-test-dynamicpv-87lb no longer exists
STEP: Deleting pod
Jun 11 16:27:14.037: INFO: Deleting pod "pod-subpath-test-dynamicpv-87lb" in namespace "provisioning-4648"
... skipping 102 lines ...

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.xDG68BsTe/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.xDG68BsTe/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.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 127 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 16:27:18.984: 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.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 11 16:27:19.263: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 11 16:27:19.263: INFO: Creating resource for dynamic PV
Jun 11 16:27:19.263: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-79017vjxl
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 11 16:27:25.638: INFO: Deleting pod "pod-1f2cdb4d-3adf-4a17-8d2d-e62e32b0f8c9" in namespace "volumemode-7901"
Jun 11 16:27:25.691: INFO: Wait up to 5m0s for pod "pod-1f2cdb4d-3adf-4a17-8d2d-e62e32b0f8c9" to be fully deleted
STEP: Deleting pvc
Jun 11 16:27:37.901: INFO: Deleting PersistentVolumeClaim "awsjp5lb"
Jun 11 16:27:37.953: INFO: Waiting up to 5m0s for PersistentVolume pvc-ffd6cb39-317e-4d5e-b4c1-21347e51efab to get deleted
Jun 11 16:27:38.006: INFO: PersistentVolume pvc-ffd6cb39-317e-4d5e-b4c1-21347e51efab found and phase=Released (52.322926ms)
... skipping 11 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.xDG68BsTe/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.xDG68BsTe/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
    /tmp/kops.xDG68BsTe/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.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 11 16:27:53.331: INFO: Driver "ebs.csi.aws.com" does not support volume type "PreprovisionedPV" - skipping
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
... skipping 233 lines ...

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 10 lines ...
Jun 11 16:24:49.156: INFO: Creating resource for dynamic PV
Jun 11 16:24:49.156: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-7894-e2e-sc4crlq
STEP: creating a claim
Jun 11 16:24:49.209: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 11 16:24:49.366: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-wqn4l" in namespace "snapshotting-7894" to be "Succeeded or Failed"
Jun 11 16:24:49.417: INFO: Pod "pvc-snapshottable-tester-wqn4l": Phase="Pending", Reason="", readiness=false. Elapsed: 50.838239ms
Jun 11 16:24:51.471: INFO: Pod "pvc-snapshottable-tester-wqn4l": Phase="Pending", Reason="", readiness=false. Elapsed: 2.105201982s
Jun 11 16:24:53.524: INFO: Pod "pvc-snapshottable-tester-wqn4l": Phase="Pending", Reason="", readiness=false. Elapsed: 4.15820565s
Jun 11 16:24:55.576: INFO: Pod "pvc-snapshottable-tester-wqn4l": Phase="Pending", Reason="", readiness=false. Elapsed: 6.209979989s
Jun 11 16:24:57.629: INFO: Pod "pvc-snapshottable-tester-wqn4l": Phase="Pending", Reason="", readiness=false. Elapsed: 8.263551393s
Jun 11 16:24:59.681: INFO: Pod "pvc-snapshottable-tester-wqn4l": Phase="Pending", Reason="", readiness=false. Elapsed: 10.31506819s
Jun 11 16:25:01.733: INFO: Pod "pvc-snapshottable-tester-wqn4l": Phase="Pending", Reason="", readiness=false. Elapsed: 12.366983668s
Jun 11 16:25:03.785: INFO: Pod "pvc-snapshottable-tester-wqn4l": Phase="Pending", Reason="", readiness=false. Elapsed: 14.419544756s
Jun 11 16:25:05.837: INFO: Pod "pvc-snapshottable-tester-wqn4l": Phase="Pending", Reason="", readiness=false. Elapsed: 16.471329274s
Jun 11 16:25:07.897: INFO: Pod "pvc-snapshottable-tester-wqn4l": Phase="Pending", Reason="", readiness=false. Elapsed: 18.530635656s
Jun 11 16:25:09.950: INFO: Pod "pvc-snapshottable-tester-wqn4l": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.584036895s
STEP: Saw pod success
Jun 11 16:25:09.950: INFO: Pod "pvc-snapshottable-tester-wqn4l" satisfied condition "Succeeded or Failed"
Jun 11 16:25:10.056: INFO: Pod pvc-snapshottable-tester-wqn4l has the following logs: 
Jun 11 16:25:10.056: INFO: Deleting pod "pvc-snapshottable-tester-wqn4l" in namespace "snapshotting-7894"
Jun 11 16:25:10.113: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-wqn4l" to be fully deleted
Jun 11 16:25:10.165: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comhhwv5] to have phase Bound
Jun 11 16:25:10.217: INFO: PersistentVolumeClaim ebs.csi.aws.comhhwv5 found and phase=Bound (51.678695ms)
STEP: [init] checking the claim
... skipping 60 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:243
STEP: checking the snapshot
STEP: checking the SnapshotContent
STEP: Modifying source data test
STEP: modifying the data in the source PVC
Jun 11 16:26:17.131: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-4d5vb" in namespace "snapshotting-7894" to be "Succeeded or Failed"
Jun 11 16:26:17.183: INFO: Pod "pvc-snapshottable-data-tester-4d5vb": Phase="Pending", Reason="", readiness=false. Elapsed: 52.111098ms
Jun 11 16:26:19.235: INFO: Pod "pvc-snapshottable-data-tester-4d5vb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.103562119s
Jun 11 16:26:21.287: INFO: Pod "pvc-snapshottable-data-tester-4d5vb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.156084689s
Jun 11 16:26:23.339: INFO: Pod "pvc-snapshottable-data-tester-4d5vb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.208323645s
Jun 11 16:26:25.392: INFO: Pod "pvc-snapshottable-data-tester-4d5vb": Phase="Pending", Reason="", readiness=false. Elapsed: 8.260724905s
Jun 11 16:26:27.452: INFO: Pod "pvc-snapshottable-data-tester-4d5vb": Phase="Pending", Reason="", readiness=false. Elapsed: 10.320631325s
Jun 11 16:26:29.511: INFO: Pod "pvc-snapshottable-data-tester-4d5vb": Phase="Pending", Reason="", readiness=false. Elapsed: 12.379997466s
Jun 11 16:26:31.563: INFO: Pod "pvc-snapshottable-data-tester-4d5vb": Phase="Pending", Reason="", readiness=false. Elapsed: 14.431506203s
Jun 11 16:26:33.615: INFO: Pod "pvc-snapshottable-data-tester-4d5vb": Phase="Pending", Reason="", readiness=false. Elapsed: 16.484379427s
Jun 11 16:26:35.669: INFO: Pod "pvc-snapshottable-data-tester-4d5vb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.537555382s
STEP: Saw pod success
Jun 11 16:26:35.669: INFO: Pod "pvc-snapshottable-data-tester-4d5vb" satisfied condition "Succeeded or Failed"
Jun 11 16:26:35.778: INFO: Pod pvc-snapshottable-data-tester-4d5vb has the following logs: 
Jun 11 16:26:35.779: INFO: Deleting pod "pvc-snapshottable-data-tester-4d5vb" in namespace "snapshotting-7894"
Jun 11 16:26:35.841: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-4d5vb" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 11 16:27:14.101: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-7894 exec restored-pvc-tester-fzwpj --namespace=snapshotting-7894 -- cat /mnt/test/data'
... skipping 132 lines ...
Jun 11 16:26:48.782: INFO: Creating resource for dynamic PV
Jun 11 16:26:48.783: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9829xk4fd
STEP: creating a claim
Jun 11 16:26:48.850: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-9829
Jun 11 16:26:49.023: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-9829" in namespace "provisioning-9829" to be "Succeeded or Failed"
Jun 11 16:26:49.077: INFO: Pod "volume-prep-provisioning-9829": Phase="Pending", Reason="", readiness=false. Elapsed: 53.900871ms
Jun 11 16:26:51.130: INFO: Pod "volume-prep-provisioning-9829": Phase="Pending", Reason="", readiness=false. Elapsed: 2.107022491s
Jun 11 16:26:53.184: INFO: Pod "volume-prep-provisioning-9829": Phase="Pending", Reason="", readiness=false. Elapsed: 4.161318557s
Jun 11 16:26:55.237: INFO: Pod "volume-prep-provisioning-9829": Phase="Pending", Reason="", readiness=false. Elapsed: 6.214228473s
Jun 11 16:26:57.289: INFO: Pod "volume-prep-provisioning-9829": Phase="Pending", Reason="", readiness=false. Elapsed: 8.26661642s
Jun 11 16:26:59.342: INFO: Pod "volume-prep-provisioning-9829": Phase="Pending", Reason="", readiness=false. Elapsed: 10.318925505s
Jun 11 16:27:01.394: INFO: Pod "volume-prep-provisioning-9829": Phase="Pending", Reason="", readiness=false. Elapsed: 12.371186274s
Jun 11 16:27:03.445: INFO: Pod "volume-prep-provisioning-9829": Phase="Pending", Reason="", readiness=false. Elapsed: 14.422836123s
Jun 11 16:27:05.497: INFO: Pod "volume-prep-provisioning-9829": Phase="Pending", Reason="", readiness=false. Elapsed: 16.474827714s
Jun 11 16:27:07.549: INFO: Pod "volume-prep-provisioning-9829": Phase="Pending", Reason="", readiness=false. Elapsed: 18.526751891s
Jun 11 16:27:09.602: INFO: Pod "volume-prep-provisioning-9829": Phase="Pending", Reason="", readiness=false. Elapsed: 20.579504291s
Jun 11 16:27:11.654: INFO: Pod "volume-prep-provisioning-9829": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.631238799s
STEP: Saw pod success
Jun 11 16:27:11.654: INFO: Pod "volume-prep-provisioning-9829" satisfied condition "Succeeded or Failed"
Jun 11 16:27:11.654: INFO: Deleting pod "volume-prep-provisioning-9829" in namespace "provisioning-9829"
Jun 11 16:27:11.712: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-9829" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-v2pl
STEP: Checking for subpath error in container status
Jun 11 16:27:45.933: INFO: Deleting pod "pod-subpath-test-dynamicpv-v2pl" in namespace "provisioning-9829"
Jun 11 16:27:45.991: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-v2pl" to be fully deleted
STEP: Deleting pod
Jun 11 16:27:46.043: INFO: Deleting pod "pod-subpath-test-dynamicpv-v2pl" in namespace "provisioning-9829"
STEP: Deleting pvc
Jun 11 16:27:46.198: INFO: Deleting PersistentVolumeClaim "awsgbq9p"
... skipping 394 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.xDG68BsTe/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.xDG68BsTe/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.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 10 lines ...
Jun 11 16:28:02.290: INFO: Creating resource for dynamic PV
Jun 11 16:28:02.290: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-1098-e2e-sc9x487
STEP: creating a claim
STEP: Expanding non-expandable pvc
Jun 11 16:28:02.449: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 11 16:28:02.557: INFO: Error updating pvc ebs.csi.aws.comdplkd: PersistentVolumeClaim "ebs.csi.aws.comdplkd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1098-e2e-sc9x487",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun 11 16:28:32.767: INFO: Error updating pvc ebs.csi.aws.comdplkd: PersistentVolumeClaim "ebs.csi.aws.comdplkd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 66 lines ...
Jun 11 16:28:08.467: INFO: Creating resource for dynamic PV
Jun 11 16:28:08.467: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-3531f2vqt
STEP: creating a claim
STEP: Expanding non-expandable pvc
Jun 11 16:28:08.621: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 11 16:28:08.722: INFO: Error updating pvc awsdfnlt: PersistentVolumeClaim "awsdfnlt" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3531f2vqt",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun 11 16:28:38.944: INFO: Error updating pvc awsdfnlt: PersistentVolumeClaim "awsdfnlt" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 217 lines ...
Jun 11 16:27:44.048: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-3954-e2e-sckr9zm
STEP: creating a claim
Jun 11 16:27:44.100: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-t2nj
STEP: Creating a pod to test exec-volume-test
Jun 11 16:27:44.258: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-t2nj" in namespace "volume-3954" to be "Succeeded or Failed"
Jun 11 16:27:44.308: INFO: Pod "exec-volume-test-dynamicpv-t2nj": Phase="Pending", Reason="", readiness=false. Elapsed: 50.309848ms
Jun 11 16:27:46.359: INFO: Pod "exec-volume-test-dynamicpv-t2nj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.101279828s
Jun 11 16:27:48.410: INFO: Pod "exec-volume-test-dynamicpv-t2nj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.151918126s
Jun 11 16:27:50.462: INFO: Pod "exec-volume-test-dynamicpv-t2nj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.204396773s
Jun 11 16:27:52.514: INFO: Pod "exec-volume-test-dynamicpv-t2nj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.255770374s
Jun 11 16:27:54.567: INFO: Pod "exec-volume-test-dynamicpv-t2nj": Phase="Pending", Reason="", readiness=false. Elapsed: 10.309232374s
Jun 11 16:27:56.633: INFO: Pod "exec-volume-test-dynamicpv-t2nj": Phase="Pending", Reason="", readiness=false. Elapsed: 12.374870002s
Jun 11 16:27:58.684: INFO: Pod "exec-volume-test-dynamicpv-t2nj": Phase="Pending", Reason="", readiness=false. Elapsed: 14.426197147s
Jun 11 16:28:00.735: INFO: Pod "exec-volume-test-dynamicpv-t2nj": Phase="Pending", Reason="", readiness=false. Elapsed: 16.477600998s
Jun 11 16:28:02.786: INFO: Pod "exec-volume-test-dynamicpv-t2nj": Phase="Pending", Reason="", readiness=false. Elapsed: 18.528600578s
Jun 11 16:28:04.838: INFO: Pod "exec-volume-test-dynamicpv-t2nj": Phase="Pending", Reason="", readiness=false. Elapsed: 20.579907214s
Jun 11 16:28:06.896: INFO: Pod "exec-volume-test-dynamicpv-t2nj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.638083613s
STEP: Saw pod success
Jun 11 16:28:06.896: INFO: Pod "exec-volume-test-dynamicpv-t2nj" satisfied condition "Succeeded or Failed"
Jun 11 16:28:06.953: INFO: Trying to get logs from node ip-172-20-56-114.us-west-1.compute.internal pod exec-volume-test-dynamicpv-t2nj container exec-container-dynamicpv-t2nj: <nil>
STEP: delete the pod
Jun 11 16:28:07.078: INFO: Waiting for pod exec-volume-test-dynamicpv-t2nj to disappear
Jun 11 16:28:07.129: INFO: Pod exec-volume-test-dynamicpv-t2nj no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-t2nj
Jun 11 16:28:07.129: INFO: Deleting pod "exec-volume-test-dynamicpv-t2nj" in namespace "volume-3954"
... skipping 170 lines ...
Jun 11 16:28:01.935: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7272dzxzc
STEP: creating a claim
Jun 11 16:28:02.022: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-g9fg
STEP: Creating a pod to test multi_subpath
Jun 11 16:28:02.184: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-g9fg" in namespace "provisioning-7272" to be "Succeeded or Failed"
Jun 11 16:28:02.236: INFO: Pod "pod-subpath-test-dynamicpv-g9fg": Phase="Pending", Reason="", readiness=false. Elapsed: 51.337218ms
Jun 11 16:28:04.289: INFO: Pod "pod-subpath-test-dynamicpv-g9fg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.104469365s
Jun 11 16:28:06.342: INFO: Pod "pod-subpath-test-dynamicpv-g9fg": Phase="Pending", Reason="", readiness=false. Elapsed: 4.157171349s
Jun 11 16:28:08.393: INFO: Pod "pod-subpath-test-dynamicpv-g9fg": Phase="Pending", Reason="", readiness=false. Elapsed: 6.209015489s
Jun 11 16:28:10.446: INFO: Pod "pod-subpath-test-dynamicpv-g9fg": Phase="Pending", Reason="", readiness=false. Elapsed: 8.261102956s
Jun 11 16:28:12.498: INFO: Pod "pod-subpath-test-dynamicpv-g9fg": Phase="Pending", Reason="", readiness=false. Elapsed: 10.313960868s
... skipping 3 lines ...
Jun 11 16:28:20.709: INFO: Pod "pod-subpath-test-dynamicpv-g9fg": Phase="Pending", Reason="", readiness=false. Elapsed: 18.524995183s
Jun 11 16:28:22.762: INFO: Pod "pod-subpath-test-dynamicpv-g9fg": Phase="Pending", Reason="", readiness=false. Elapsed: 20.577337032s
Jun 11 16:28:24.814: INFO: Pod "pod-subpath-test-dynamicpv-g9fg": Phase="Pending", Reason="", readiness=false. Elapsed: 22.629077997s
Jun 11 16:28:26.866: INFO: Pod "pod-subpath-test-dynamicpv-g9fg": Phase="Pending", Reason="", readiness=false. Elapsed: 24.681832517s
Jun 11 16:28:28.919: INFO: Pod "pod-subpath-test-dynamicpv-g9fg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.734901659s
STEP: Saw pod success
Jun 11 16:28:28.919: INFO: Pod "pod-subpath-test-dynamicpv-g9fg" satisfied condition "Succeeded or Failed"
Jun 11 16:28:28.971: INFO: Trying to get logs from node ip-172-20-42-53.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-g9fg container test-container-subpath-dynamicpv-g9fg: <nil>
STEP: delete the pod
Jun 11 16:28:29.083: INFO: Waiting for pod pod-subpath-test-dynamicpv-g9fg to disappear
Jun 11 16:28:29.134: INFO: Pod pod-subpath-test-dynamicpv-g9fg no longer exists
STEP: Deleting pod
Jun 11 16:28:29.134: INFO: Deleting pod "pod-subpath-test-dynamicpv-g9fg" in namespace "provisioning-7272"
... skipping 107 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 16:27:51.936: 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.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun 11 16:27:52.197: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 11 16:27:52.197: INFO: Creating resource for dynamic PV
Jun 11 16:27:52.197: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3204vqvjq
STEP: creating a claim
Jun 11 16:27:52.249: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-rsdx
STEP: Checking for subpath error in container status
Jun 11 16:28:16.523: INFO: Deleting pod "pod-subpath-test-dynamicpv-rsdx" in namespace "provisioning-3204"
Jun 11 16:28:16.575: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-rsdx" to be fully deleted
STEP: Deleting pod
Jun 11 16:28:26.688: INFO: Deleting pod "pod-subpath-test-dynamicpv-rsdx" in namespace "provisioning-3204"
STEP: Deleting pvc
Jun 11 16:28:26.844: INFO: Deleting PersistentVolumeClaim "aws8skpq"
... skipping 15 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.xDG68BsTe/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.xDG68BsTe/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath file is outside the volume [Slow][LinuxOnly]
      /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 367 lines ...
Jun 11 16:28:08.085: INFO: PersistentVolumeClaim pvc-wdw54 found but phase is Pending instead of Bound.
Jun 11 16:28:10.137: INFO: PersistentVolumeClaim pvc-wdw54 found and phase=Bound (6.209798383s)
Jun 11 16:28:10.137: INFO: Waiting up to 3m0s for PersistentVolume aws-m6rn6 to have phase Bound
Jun 11 16:28:10.188: INFO: PersistentVolume aws-m6rn6 found and phase=Bound (51.13083ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-cqxs
STEP: Creating a pod to test exec-volume-test
Jun 11 16:28:10.343: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-cqxs" in namespace "volume-5967" to be "Succeeded or Failed"
Jun 11 16:28:10.395: INFO: Pod "exec-volume-test-preprovisionedpv-cqxs": Phase="Pending", Reason="", readiness=false. Elapsed: 51.594673ms
Jun 11 16:28:12.448: INFO: Pod "exec-volume-test-preprovisionedpv-cqxs": Phase="Pending", Reason="", readiness=false. Elapsed: 2.104961225s
Jun 11 16:28:14.504: INFO: Pod "exec-volume-test-preprovisionedpv-cqxs": Phase="Pending", Reason="", readiness=false. Elapsed: 4.161234068s
Jun 11 16:28:16.556: INFO: Pod "exec-volume-test-preprovisionedpv-cqxs": Phase="Pending", Reason="", readiness=false. Elapsed: 6.212713104s
Jun 11 16:28:18.609: INFO: Pod "exec-volume-test-preprovisionedpv-cqxs": Phase="Pending", Reason="", readiness=false. Elapsed: 8.265837581s
Jun 11 16:28:20.662: INFO: Pod "exec-volume-test-preprovisionedpv-cqxs": Phase="Pending", Reason="", readiness=false. Elapsed: 10.319096675s
... skipping 7 lines ...
Jun 11 16:28:37.084: INFO: Pod "exec-volume-test-preprovisionedpv-cqxs": Phase="Pending", Reason="", readiness=false. Elapsed: 26.740693166s
Jun 11 16:28:39.136: INFO: Pod "exec-volume-test-preprovisionedpv-cqxs": Phase="Pending", Reason="", readiness=false. Elapsed: 28.793060068s
Jun 11 16:28:41.189: INFO: Pod "exec-volume-test-preprovisionedpv-cqxs": Phase="Pending", Reason="", readiness=false. Elapsed: 30.845735102s
Jun 11 16:28:43.241: INFO: Pod "exec-volume-test-preprovisionedpv-cqxs": Phase="Pending", Reason="", readiness=false. Elapsed: 32.897988857s
Jun 11 16:28:45.294: INFO: Pod "exec-volume-test-preprovisionedpv-cqxs": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.951135648s
STEP: Saw pod success
Jun 11 16:28:45.294: INFO: Pod "exec-volume-test-preprovisionedpv-cqxs" satisfied condition "Succeeded or Failed"
Jun 11 16:28:45.345: INFO: Trying to get logs from node ip-172-20-56-114.us-west-1.compute.internal pod exec-volume-test-preprovisionedpv-cqxs container exec-container-preprovisionedpv-cqxs: <nil>
STEP: delete the pod
Jun 11 16:28:45.454: INFO: Waiting for pod exec-volume-test-preprovisionedpv-cqxs to disappear
Jun 11 16:28:45.505: INFO: Pod exec-volume-test-preprovisionedpv-cqxs no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-cqxs
Jun 11 16:28:45.505: INFO: Deleting pod "exec-volume-test-preprovisionedpv-cqxs" in namespace "volume-5967"
STEP: Deleting pv and pvc
Jun 11 16:28:45.557: INFO: Deleting PersistentVolumeClaim "pvc-wdw54"
Jun 11 16:28:45.618: INFO: Deleting PersistentVolume "aws-m6rn6"
Jun 11 16:28:45.826: INFO: Couldn't delete PD "aws://us-west-1a/vol-058846e771fb09dbf", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-058846e771fb09dbf is currently attached to i-0d96e5f5f1bf58424
	status code: 400, request id: 5278a4a9-32da-4425-9486-d1610972fba9
Jun 11 16:28:51.238: INFO: Couldn't delete PD "aws://us-west-1a/vol-058846e771fb09dbf", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-058846e771fb09dbf is currently attached to i-0d96e5f5f1bf58424
	status code: 400, request id: 3cbec00a-be48-43fe-9b37-b806fa802eb8
Jun 11 16:28:56.569: INFO: Couldn't delete PD "aws://us-west-1a/vol-058846e771fb09dbf", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-058846e771fb09dbf is currently attached to i-0d96e5f5f1bf58424
	status code: 400, request id: e953bc2d-8999-4b1e-b80a-f18ab19d363f
Jun 11 16:29:01.924: INFO: Couldn't delete PD "aws://us-west-1a/vol-058846e771fb09dbf", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-058846e771fb09dbf is currently attached to i-0d96e5f5f1bf58424
	status code: 400, request id: 3dbc3e3d-d3fb-4266-9e29-91c7d213484f
Jun 11 16:29:07.306: INFO: Successfully deleted PD "aws://us-west-1a/vol-058846e771fb09dbf".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 16:29:07.307: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-5967" for this suite.
... skipping 146 lines ...
Jun 11 16:28:43.191: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-6815nvdtw
STEP: creating a claim
Jun 11 16:28:43.242: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-72wd
STEP: Creating a pod to test exec-volume-test
Jun 11 16:28:43.397: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-72wd" in namespace "volume-6815" to be "Succeeded or Failed"
Jun 11 16:28:43.447: INFO: Pod "exec-volume-test-dynamicpv-72wd": Phase="Pending", Reason="", readiness=false. Elapsed: 50.230889ms
Jun 11 16:28:45.498: INFO: Pod "exec-volume-test-dynamicpv-72wd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.101016169s
Jun 11 16:28:47.551: INFO: Pod "exec-volume-test-dynamicpv-72wd": Phase="Pending", Reason="", readiness=false. Elapsed: 4.154057924s
Jun 11 16:28:49.603: INFO: Pod "exec-volume-test-dynamicpv-72wd": Phase="Pending", Reason="", readiness=false. Elapsed: 6.205394064s
Jun 11 16:28:51.654: INFO: Pod "exec-volume-test-dynamicpv-72wd": Phase="Pending", Reason="", readiness=false. Elapsed: 8.256699147s
Jun 11 16:28:53.704: INFO: Pod "exec-volume-test-dynamicpv-72wd": Phase="Pending", Reason="", readiness=false. Elapsed: 10.307170839s
Jun 11 16:28:55.755: INFO: Pod "exec-volume-test-dynamicpv-72wd": Phase="Pending", Reason="", readiness=false. Elapsed: 12.358266808s
Jun 11 16:28:57.809: INFO: Pod "exec-volume-test-dynamicpv-72wd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.412118471s
STEP: Saw pod success
Jun 11 16:28:57.809: INFO: Pod "exec-volume-test-dynamicpv-72wd" satisfied condition "Succeeded or Failed"
Jun 11 16:28:57.863: INFO: Trying to get logs from node ip-172-20-42-53.us-west-1.compute.internal pod exec-volume-test-dynamicpv-72wd container exec-container-dynamicpv-72wd: <nil>
STEP: delete the pod
Jun 11 16:28:57.973: INFO: Waiting for pod exec-volume-test-dynamicpv-72wd to disappear
Jun 11 16:28:58.023: INFO: Pod exec-volume-test-dynamicpv-72wd no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-72wd
Jun 11 16:28:58.023: INFO: Deleting pod "exec-volume-test-dynamicpv-72wd" in namespace "volume-6815"
... skipping 128 lines ...
Jun 11 16:26:08.915: INFO: Creating resource for dynamic PV
Jun 11 16:26:08.915: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-4290-e2e-sc2jm2l
STEP: creating a claim
Jun 11 16:26:08.967: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 11 16:26:09.126: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-nj5wx" in namespace "snapshotting-4290" to be "Succeeded or Failed"
Jun 11 16:26:09.177: INFO: Pod "pvc-snapshottable-tester-nj5wx": Phase="Pending", Reason="", readiness=false. Elapsed: 50.832124ms
Jun 11 16:26:11.229: INFO: Pod "pvc-snapshottable-tester-nj5wx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.102277176s
Jun 11 16:26:13.281: INFO: Pod "pvc-snapshottable-tester-nj5wx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.154837706s
Jun 11 16:26:15.333: INFO: Pod "pvc-snapshottable-tester-nj5wx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.206885228s
Jun 11 16:26:17.385: INFO: Pod "pvc-snapshottable-tester-nj5wx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.2587403s
Jun 11 16:26:19.439: INFO: Pod "pvc-snapshottable-tester-nj5wx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.312116451s
Jun 11 16:26:21.490: INFO: Pod "pvc-snapshottable-tester-nj5wx": Phase="Pending", Reason="", readiness=false. Elapsed: 12.363742892s
Jun 11 16:26:23.546: INFO: Pod "pvc-snapshottable-tester-nj5wx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.41929297s
STEP: Saw pod success
Jun 11 16:26:23.546: INFO: Pod "pvc-snapshottable-tester-nj5wx" satisfied condition "Succeeded or Failed"
Jun 11 16:26:23.652: INFO: Pod pvc-snapshottable-tester-nj5wx has the following logs: 
Jun 11 16:26:23.652: INFO: Deleting pod "pvc-snapshottable-tester-nj5wx" in namespace "snapshotting-4290"
Jun 11 16:26:23.709: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-nj5wx" to be fully deleted
Jun 11 16:26:23.760: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comphghp] to have phase Bound
Jun 11 16:26:23.812: INFO: PersistentVolumeClaim ebs.csi.aws.comphghp found and phase=Bound (51.207659ms)
STEP: [init] checking the claim
... skipping 59 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:243
STEP: checking the snapshot
STEP: checking the SnapshotContent
STEP: Modifying source data test
STEP: modifying the data in the source PVC
Jun 11 16:27:28.557: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-t6g4c" in namespace "snapshotting-4290" to be "Succeeded or Failed"
Jun 11 16:27:28.625: INFO: Pod "pvc-snapshottable-data-tester-t6g4c": Phase="Pending", Reason="", readiness=false. Elapsed: 67.673892ms
Jun 11 16:27:30.678: INFO: Pod "pvc-snapshottable-data-tester-t6g4c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.12113725s
Jun 11 16:27:32.731: INFO: Pod "pvc-snapshottable-data-tester-t6g4c": Phase="Pending", Reason="", readiness=false. Elapsed: 4.174381076s
Jun 11 16:27:34.784: INFO: Pod "pvc-snapshottable-data-tester-t6g4c": Phase="Pending", Reason="", readiness=false. Elapsed: 6.226882102s
Jun 11 16:27:36.836: INFO: Pod "pvc-snapshottable-data-tester-t6g4c": Phase="Pending", Reason="", readiness=false. Elapsed: 8.279506396s
Jun 11 16:27:38.889: INFO: Pod "pvc-snapshottable-data-tester-t6g4c": Phase="Pending", Reason="", readiness=false. Elapsed: 10.331806042s
... skipping 6 lines ...
Jun 11 16:27:53.256: INFO: Pod "pvc-snapshottable-data-tester-t6g4c": Phase="Pending", Reason="", readiness=false. Elapsed: 24.698663957s
Jun 11 16:27:55.310: INFO: Pod "pvc-snapshottable-data-tester-t6g4c": Phase="Pending", Reason="", readiness=false. Elapsed: 26.752631797s
Jun 11 16:27:57.362: INFO: Pod "pvc-snapshottable-data-tester-t6g4c": Phase="Pending", Reason="", readiness=false. Elapsed: 28.805134334s
Jun 11 16:27:59.414: INFO: Pod "pvc-snapshottable-data-tester-t6g4c": Phase="Pending", Reason="", readiness=false. Elapsed: 30.857228653s
Jun 11 16:28:01.466: INFO: Pod "pvc-snapshottable-data-tester-t6g4c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 32.909335979s
STEP: Saw pod success
Jun 11 16:28:01.466: INFO: Pod "pvc-snapshottable-data-tester-t6g4c" satisfied condition "Succeeded or Failed"
Jun 11 16:28:01.572: INFO: Pod pvc-snapshottable-data-tester-t6g4c has the following logs: 
Jun 11 16:28:01.572: INFO: Deleting pod "pvc-snapshottable-data-tester-t6g4c" in namespace "snapshotting-4290"
Jun 11 16:28:01.632: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-t6g4c" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 11 16:28:25.919: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-4290 exec restored-pvc-tester-q22dw --namespace=snapshotting-4290 -- cat /mnt/test/data'
... skipping 244 lines ...
    /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:108
      
      /tmp/kops.xDG68BsTe/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.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:243

        Unexpected error:
            <exec.CodeExitError>: {
                Err: {
                    s: "error running /usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-4290 exec restored-pvc-tester-q22dw --namespace=snapshotting-4290 -- cat /mnt/test/data:\nCommand stdout:\n\nstderr:\ncat: can't open '/mnt/test/data': No such file or directory\ncommand terminated with exit code 1\n\nerror:\nexit status 1",
                },
                Code: 1,
            }
            error running /usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-4290 exec restored-pvc-tester-q22dw --namespace=snapshotting-4290 -- 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.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:602
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] volume-expand
... skipping 10 lines ...
Jun 11 16:28:43.172: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-9562-e2e-sc987x8
STEP: creating a claim
Jun 11 16:28:43.223: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Jun 11 16:28:43.330: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 11 16:28:43.432: INFO: Error updating pvc ebs.csi.aws.comgv274: PersistentVolumeClaim "ebs.csi.aws.comgv274" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-9562-e2e-sc987x8",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun 11 16:29:13.648: INFO: Error updating pvc ebs.csi.aws.comgv274: PersistentVolumeClaim "ebs.csi.aws.comgv274" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 220 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 11 16:28:33.401: 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.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun 11 16:28:33.659: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 11 16:28:33.659: INFO: Creating resource for dynamic PV
Jun 11 16:28:33.659: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6734zxxhb
STEP: creating a claim
Jun 11 16:28:33.715: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-kjn2
STEP: Checking for subpath error in container status
Jun 11 16:28:55.989: INFO: Deleting pod "pod-subpath-test-dynamicpv-kjn2" in namespace "provisioning-6734"
Jun 11 16:28:56.042: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-kjn2" to be fully deleted
STEP: Deleting pod
Jun 11 16:29:06.146: INFO: Deleting pod "pod-subpath-test-dynamicpv-kjn2" in namespace "provisioning-6734"
STEP: Deleting pvc
Jun 11 16:29:06.302: INFO: Deleting PersistentVolumeClaim "awsgsthf"
... skipping 14 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.xDG68BsTe/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.xDG68BsTe/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.xDG68BsTe/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.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 473 lines ...
Jun 11 16:28:52.665: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 11 16:28:53.215: INFO: Successfully created a new PD: "aws://us-west-1a/vol-052066c2593917120".
Jun 11 16:28:53.215: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-mx8h
STEP: Creating a pod to test exec-volume-test
Jun 11 16:28:53.274: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-mx8h" in namespace "volume-3753" to be "Succeeded or Failed"
Jun 11 16:28:53.326: INFO: Pod "exec-volume-test-inlinevolume-mx8h": Phase="Pending", Reason="", readiness=false. Elapsed: 51.902566ms
Jun 11 16:28:55.378: INFO: Pod "exec-volume-test-inlinevolume-mx8h": Phase="Pending", Reason="", readiness=false. Elapsed: 2.104530699s
Jun 11 16:28:57.431: INFO: Pod "exec-volume-test-inlinevolume-mx8h": Phase="Pending", Reason="", readiness=false. Elapsed: 4.157099726s
Jun 11 16:28:59.483: INFO: Pod "exec-volume-test-inlinevolume-mx8h": Phase="Pending", Reason="", readiness=false. Elapsed: 6.20942774s
Jun 11 16:29:01.537: INFO: Pod "exec-volume-test-inlinevolume-mx8h": Phase="Pending", Reason="", readiness=false. Elapsed: 8.263430916s
Jun 11 16:29:03.590: INFO: Pod "exec-volume-test-inlinevolume-mx8h": Phase="Pending", Reason="", readiness=false. Elapsed: 10.316478161s
... skipping 6 lines ...
Jun 11 16:29:17.960: INFO: Pod "exec-volume-test-inlinevolume-mx8h": Phase="Pending", Reason="", readiness=false. Elapsed: 24.686696864s
Jun 11 16:29:20.016: INFO: Pod "exec-volume-test-inlinevolume-mx8h": Phase="Pending", Reason="", readiness=false. Elapsed: 26.742565886s
Jun 11 16:29:22.070: INFO: Pod "exec-volume-test-inlinevolume-mx8h": Phase="Pending", Reason="", readiness=false. Elapsed: 28.795903394s
Jun 11 16:29:24.123: INFO: Pod "exec-volume-test-inlinevolume-mx8h": Phase="Pending", Reason="", readiness=false. Elapsed: 30.849367088s
Jun 11 16:29:26.176: INFO: Pod "exec-volume-test-inlinevolume-mx8h": Phase="Succeeded", Reason="", readiness=false. Elapsed: 32.902513041s
STEP: Saw pod success
Jun 11 16:29:26.176: INFO: Pod "exec-volume-test-inlinevolume-mx8h" satisfied condition "Succeeded or Failed"
Jun 11 16:29:26.228: INFO: Trying to get logs from node ip-172-20-40-55.us-west-1.compute.internal pod exec-volume-test-inlinevolume-mx8h container exec-container-inlinevolume-mx8h: <nil>
STEP: delete the pod
Jun 11 16:29:26.339: INFO: Waiting for pod exec-volume-test-inlinevolume-mx8h to disappear
Jun 11 16:29:26.390: INFO: Pod exec-volume-test-inlinevolume-mx8h no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-mx8h
Jun 11 16:29:26.390: INFO: Deleting pod "exec-volume-test-inlinevolume-mx8h" in namespace "volume-3753"
Jun 11 16:29:26.601: INFO: Couldn't delete PD "aws://us-west-1a/vol-052066c2593917120", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-052066c2593917120 is currently attached to i-0904333f4b3ec64fb
	status code: 400, request id: 5b2c4c1c-141f-42b6-8795-05f44139565e
Jun 11 16:29:31.988: INFO: Couldn't delete PD "aws://us-west-1a/vol-052066c2593917120", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-052066c2593917120 is currently attached to i-0904333f4b3ec64fb
	status code: 400, request id: ee57a73f-61e6-4512-809f-47a6a80cbb05
Jun 11 16:29:37.319: INFO: Couldn't delete PD "aws://us-west-1a/vol-052066c2593917120", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-052066c2593917120 is currently attached to i-0904333f4b3ec64fb
	status code: 400, request id: a821dd28-105c-45d1-a4d1-c98870ee8409
Jun 11 16:29:42.699: INFO: Successfully deleted PD "aws://us-west-1a/vol-052066c2593917120".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 11 16:29:42.699: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-3753" for this suite.
... skipping 164 lines ...
Jun 11 16:27:54.237: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-2921-e2e-sc865g8      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-2921    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-2921-e2e-sc865g8,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-2921    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-2921-e2e-sc865g8,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-2921    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-2921-e2e-sc865g8,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-2921-e2e-sc865g8    ded9951f-54dc-49e4-b319-dd76b17f95de 13003 0 2021-06-11 16:27:54 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-11 16:27:54 +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-hjzm7 pvc- provisioning-2921  64bddc71-88b9-4ff7-a9a3-e5702d9ef515 13006 0 2021-06-11 16:27:54 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-11 16:27:54 +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-2921-e2e-sc865g8,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-e6a18a79-8778-4740-bfa1-98fc40824e77 in namespace provisioning-2921
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun 11 16:28:16.836: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-64sv6" in namespace "provisioning-2921" to be "Succeeded or Failed"
Jun 11 16:28:16.889: INFO: Pod "pvc-volume-tester-writer-64sv6": Phase="Pending", Reason="", readiness=false. Elapsed: 53.19535ms
Jun 11 16:28:18.943: INFO: Pod "pvc-volume-tester-writer-64sv6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.107349417s
Jun 11 16:28:20.997: INFO: Pod "pvc-volume-tester-writer-64sv6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.16079176s
Jun 11 16:28:23.050: INFO: Pod "pvc-volume-tester-writer-64sv6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.214448196s
Jun 11 16:28:25.104: INFO: Pod "pvc-volume-tester-writer-64sv6": Phase="Pending", Reason="", readiness=false. Elapsed: 8.268571544s
Jun 11 16:28:27.157: INFO: Pod "pvc-volume-tester-writer-64sv6": Phase="Pending", Reason="", readiness=false. Elapsed: 10.321573659s
... skipping 22 lines ...
Jun 11 16:29:14.393: INFO: Pod "pvc-volume-tester-writer-64sv6": Phase="Pending", Reason="", readiness=false. Elapsed: 57.557190414s
Jun 11 16:29:16.445: INFO: Pod "pvc-volume-tester-writer-64sv6": Phase="Pending", Reason="", readiness=false. Elapsed: 59.609569721s
Jun 11 16:29:18.498: INFO: Pod "pvc-volume-tester-writer-64sv6": Phase="Pending", Reason="", readiness=false. Elapsed: 1m1.662304073s
Jun 11 16:29:20.549: INFO: Pod "pvc-volume-tester-writer-64sv6": Phase="Pending", Reason="", readiness=false. Elapsed: 1m3.71342671s
Jun 11 16:29:22.612: INFO: Pod "pvc-volume-tester-writer-64sv6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m5.776582153s
STEP: Saw pod success
Jun 11 16:29:22.613: INFO: Pod "pvc-volume-tester-writer-64sv6" satisfied condition "Succeeded or Failed"
Jun 11 16:29:22.717: INFO: Pod pvc-volume-tester-writer-64sv6 has the following logs: 
Jun 11 16:29:22.717: INFO: Deleting pod "pvc-volume-tester-writer-64sv6" in namespace "provisioning-2921"
Jun 11 16:29:22.774: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-64sv6" 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-40-55.us-west-1.compute.internal"
Jun 11 16:29:22.983: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-p4jhm" in namespace "provisioning-2921" to be "Succeeded or Failed"
Jun 11 16:29:23.035: INFO: Pod "pvc-volume-tester-reader-p4jhm": Phase="Pending", Reason="", readiness=false. Elapsed: 52.184362ms
Jun 11 16:29:25.087: INFO: Pod "pvc-volume-tester-reader-p4jhm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.103802795s
STEP: Saw pod success
Jun 11 16:29:25.087: INFO: Pod "pvc-volume-tester-reader-p4jhm" satisfied condition "Succeeded or Failed"
Jun 11 16:29:25.193: INFO: Pod pvc-volume-tester-reader-p4jhm has the following logs: hello world

Jun 11 16:29:25.193: INFO: Deleting pod "pvc-volume-tester-reader-p4jhm" in namespace "provisioning-2921"
Jun 11 16:29:25.249: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-p4jhm" to be fully deleted
Jun 11 16:29:25.300: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-hjzm7] to have phase Bound
Jun 11 16:29:25.351: INFO: PersistentVolumeClaim pvc-hjzm7 found and phase=Bound (50.856587ms)
... skipping 508 lines ...
Jun 11 16:28:57.717: INFO: Creating resource for dynamic PV
Jun 11 16:28:57.717: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3890-e2e-scdgzg6
STEP: creating a claim
Jun 11 16:28:57.772: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-3890
Jun 11 16:28:57.936: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-3890" in namespace "provisioning-3890" to be "Succeeded or Failed"
Jun 11 16:28:57.987: INFO: Pod "volume-prep-provisioning-3890": Phase="Pending", Reason="", readiness=false. Elapsed: 50.833888ms
Jun 11 16:29:00.039: INFO: Pod "volume-prep-provisioning-3890": Phase="Pending", Reason="", readiness=false. Elapsed: 2.102332535s
Jun 11 16:29:02.095: INFO: Pod "volume-prep-provisioning-3890": Phase="Pending", Reason="", readiness=false. Elapsed: 4.1588727s
Jun 11 16:29:04.147: INFO: Pod "volume-prep-provisioning-3890": Phase="Pending", Reason="", readiness=false. Elapsed: 6.210752175s
Jun 11 16:29:06.198: INFO: Pod "volume-prep-provisioning-3890": Phase="Pending", Reason="", readiness=false. Elapsed: 8.261894036s
Jun 11 16:29:08.250: INFO: Pod "volume-prep-provisioning-3890": Phase="Pending", Reason="", readiness=false. Elapsed: 10.314229036s
... skipping 9 lines ...
Jun 11 16:29:28.784: INFO: Pod "volume-prep-provisioning-3890": Phase="Pending", Reason="", readiness=false. Elapsed: 30.847947316s
Jun 11 16:29:30.837: INFO: Pod "volume-prep-provisioning-3890": Phase="Pending", Reason="", readiness=false. Elapsed: 32.901279464s
Jun 11 16:29:32.890: INFO: Pod "volume-prep-provisioning-3890": Phase="Pending", Reason="", readiness=false. Elapsed: 34.953756418s
Jun 11 16:29:34.942: INFO: Pod "volume-prep-provisioning-3890": Phase="Running", Reason="", readiness=true. Elapsed: 37.005762455s
Jun 11 16:29:36.995: INFO: Pod "volume-prep-provisioning-3890": Phase="Succeeded", Reason="", readiness=false. Elapsed: 39.058462607s
STEP: Saw pod success
Jun 11 16:29:36.995: INFO: Pod "volume-prep-provisioning-3890" satisfied condition "Succeeded or Failed"
Jun 11 16:29:36.995: INFO: Deleting pod "volume-prep-provisioning-3890" in namespace "provisioning-3890"
Jun 11 16:29:37.053: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-3890" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-jl5t
STEP: Checking for subpath error in container status
Jun 11 16:30:43.263: INFO: Deleting pod "pod-subpath-test-dynamicpv-jl5t" in namespace "provisioning-3890"
Jun 11 16:30:43.327: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-jl5t" to be fully deleted
STEP: Deleting pod
Jun 11 16:30:43.378: INFO: Deleting pod "pod-subpath-test-dynamicpv-jl5t" in namespace "provisioning-3890"
STEP: Deleting pvc
Jun 11 16:30:43.532: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comcjhrs"
... skipping 22 lines ...
    /tmp/kops.xDG68BsTe/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:422
------------------------------


Summarizing 2 Failures:

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

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

Ran 141 of 485 Specs in 576.678 seconds
FAIL! -- 139 Passed | 2 Failed | 0 Pending | 344 Skipped


Ginkgo ran 1 suite in 11m5.831895483s
Test Suite Failed
+ kops-finish
+ kubetest2 kops -v=2 --cloud-provider=aws --cluster-name=e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --admin-access= --kops-binary-path=/home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops --down
I0611 16:31:19.244460   27102 app.go:59] RunDir for this run: "/logs/artifacts/c1ed250d-cace-11eb-ab6f-62c732df09e9"
I0611 16:31:19.311353   27102 app.go:90] ID for this run: "c1ed250d-cace-11eb-ab6f-62c732df09e9"
I0611 16:31:19.311437   27102 dumplogs.go:38] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops toolbox dump --name e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ubuntu
I0611 16:31:19.345525   27108 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
... skipping 1645 lines ...