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

No Test Failures!


Error lines from build-log.txt

... skipping 587 lines ...
I0926 07:23:45.066903   13643 app.go:90] ID for this run: "c84926a0-1e99-11ec-a3b0-9242b45c1669"
I0926 07:23:45.092124   13643 up.go:43] Cleaning up any leaked resources from previous cluster
I0926 07:23:45.092218   13643 dumplogs.go:40] /home/prow/go/src/k8s.io/kops/.bazelbuild/dist/linux/amd64/kops toolbox dump --name e2e-c3f2775103-c95b4.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ubuntu
I0926 07:23:45.113243   13653 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0926 07:23:45.114285   13653 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I0926 07:23:45.114291   13653 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Error: Cluster.kops.k8s.io "e2e-c3f2775103-c95b4.test-cncf-aws.k8s.io" not found
W0926 07:23:45.622583   13643 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0926 07:23:45.622674   13643 down.go:48] /home/prow/go/src/k8s.io/kops/.bazelbuild/dist/linux/amd64/kops delete cluster --name e2e-c3f2775103-c95b4.test-cncf-aws.k8s.io --yes
I0926 07:23:45.637753   13664 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0926 07:23:45.637897   13664 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I0926 07:23:45.637902   13664 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-c3f2775103-c95b4.test-cncf-aws.k8s.io" not found
I0926 07:23:46.113893   13643 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/09/26 07:23:46 failed to get external ip from metadata service: http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip returned 404
I0926 07:23:46.132618   13643 http.go:37] curl https://ip.jsb.workers.dev
I0926 07:23:46.243120   13643 up.go:144] /home/prow/go/src/k8s.io/kops/.bazelbuild/dist/linux/amd64/kops create cluster --name e2e-c3f2775103-c95b4.test-cncf-aws.k8s.io --cloud aws --kubernetes-version 1.22.1 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --networking calico --override=cluster.spec.cloudConfig.awsEBSCSIDriver.enabled=true --override=cluster.spec.snapshotController.enabled=true --override=cluster.spec.certManager.enabled=true --admin-access 35.225.74.23/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones us-west-1a --master-size c5.large
I0926 07:23:46.259878   13676 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0926 07:23:46.259986   13676 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I0926 07:23:46.259993   13676 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0926 07:23:46.285224   13676 create_cluster.go:838] Using SSH public key: /etc/aws-ssh/aws-ssh-public
... skipping 33 lines ...
I0926 07:24:12.202841   13643 up.go:181] /home/prow/go/src/k8s.io/kops/.bazelbuild/dist/linux/amd64/kops validate cluster --name e2e-c3f2775103-c95b4.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0926 07:24:12.220285   13694 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0926 07:24:12.221148   13694 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I0926 07:24:12.221197   13694 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-c3f2775103-c95b4.test-cncf-aws.k8s.io

W0926 07:24:13.315782   13694 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-c3f2775103-c95b4.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-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
W0926 07:24:23.340876   13694 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0926 07:25:03.471243   13694 validate_cluster.go:232] (will retry): cluster not yet healthy
W0926 07:25:13.514652   13694 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-c3f2775103-c95b4.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0926 07:25:23.542196   13694 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-c3f2775103-c95b4.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-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
W0926 07:25:33.571816   13694 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

... skipping 8 lines ...
Machine	i-087195b8b11f3270f				machine "i-087195b8b11f3270f" has not yet joined cluster
Machine	i-0c0aac37066181110				machine "i-0c0aac37066181110" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vjnlg		system-cluster-critical pod "coredns-5dc785954d-vjnlg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-4ctcc	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-4ctcc" is pending
Pod	kube-system/ebs-csi-controller-564bc97466-6chfh	system-cluster-critical pod "ebs-csi-controller-564bc97466-6chfh" is pending

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

... skipping 10 lines ...
Node	ip-172-20-46-137.us-west-1.compute.internal	node "ip-172-20-46-137.us-west-1.compute.internal" of role "node" is not ready
Pod	kube-system/calico-node-7p4rj			system-node-critical pod "calico-node-7p4rj" is pending
Pod	kube-system/coredns-5dc785954d-vjnlg		system-cluster-critical pod "coredns-5dc785954d-vjnlg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-4ctcc	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-4ctcc" is pending
Pod	kube-system/ebs-csi-node-rd59g			system-node-critical pod "ebs-csi-node-rd59g" is pending

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

... skipping 18 lines ...
Pod	kube-system/coredns-autoscaler-84d4cfd89c-4ctcc	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-4ctcc" is pending
Pod	kube-system/ebs-csi-node-5swzx			system-node-critical pod "ebs-csi-node-5swzx" is pending
Pod	kube-system/ebs-csi-node-r98kc			system-node-critical pod "ebs-csi-node-r98kc" is pending
Pod	kube-system/ebs-csi-node-rd59g			system-node-critical pod "ebs-csi-node-rd59g" is pending
Pod	kube-system/ebs-csi-node-xzkf4			system-node-critical pod "ebs-csi-node-xzkf4" is pending

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

... skipping 14 lines ...
Pod	kube-system/coredns-autoscaler-84d4cfd89c-4ctcc	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-4ctcc" is pending
Pod	kube-system/ebs-csi-node-5swzx			system-node-critical pod "ebs-csi-node-5swzx" is pending
Pod	kube-system/ebs-csi-node-r98kc			system-node-critical pod "ebs-csi-node-r98kc" is pending
Pod	kube-system/ebs-csi-node-rd59g			system-node-critical pod "ebs-csi-node-rd59g" is pending
Pod	kube-system/ebs-csi-node-xzkf4			system-node-critical pod "ebs-csi-node-xzkf4" is pending

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

... skipping 10 lines ...
Pod	kube-system/calico-node-8vp7r	system-node-critical pod "calico-node-8vp7r" is not ready (calico-node)
Pod	kube-system/ebs-csi-node-5swzx	system-node-critical pod "ebs-csi-node-5swzx" is pending
Pod	kube-system/ebs-csi-node-r98kc	system-node-critical pod "ebs-csi-node-r98kc" is pending
Pod	kube-system/ebs-csi-node-rd59g	system-node-critical pod "ebs-csi-node-rd59g" is pending
Pod	kube-system/ebs-csi-node-xzkf4	system-node-critical pod "ebs-csi-node-xzkf4" is pending

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

... skipping 6 lines ...
ip-172-20-60-23.us-west-1.compute.internal	master	True

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

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

... skipping 6 lines ...
ip-172-20-60-23.us-west-1.compute.internal	master	True

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

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

... skipping 6 lines ...
ip-172-20-60-23.us-west-1.compute.internal	master	True

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

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

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

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

      Distro debian doesn't support ntfs -- skipping

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

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

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

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

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 160 lines ...
Sep 26 07:32:14.179: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 556 lines ...
Sep 26 07:32:17.714: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Sep 26 07:32:18.230: INFO: Successfully created a new PD: "aws://us-west-1a/vol-002ba3d6778b96aa3".
Sep 26 07:32:18.230: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-pczw
STEP: Creating a pod to test exec-volume-test
Sep 26 07:32:18.282: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-pczw" in namespace "volume-5113" to be "Succeeded or Failed"
Sep 26 07:32:18.333: INFO: Pod "exec-volume-test-inlinevolume-pczw": Phase="Pending", Reason="", readiness=false. Elapsed: 50.255775ms
Sep 26 07:32:20.396: INFO: Pod "exec-volume-test-inlinevolume-pczw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.113834121s
Sep 26 07:32:22.448: INFO: Pod "exec-volume-test-inlinevolume-pczw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.165663956s
Sep 26 07:32:24.499: INFO: Pod "exec-volume-test-inlinevolume-pczw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.21640433s
Sep 26 07:32:26.549: INFO: Pod "exec-volume-test-inlinevolume-pczw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.2670072s
Sep 26 07:32:28.601: INFO: Pod "exec-volume-test-inlinevolume-pczw": Phase="Pending", Reason="", readiness=false. Elapsed: 10.318185883s
Sep 26 07:32:30.652: INFO: Pod "exec-volume-test-inlinevolume-pczw": Phase="Pending", Reason="", readiness=false. Elapsed: 12.369897105s
Sep 26 07:32:32.703: INFO: Pod "exec-volume-test-inlinevolume-pczw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.420542406s
STEP: Saw pod success
Sep 26 07:32:32.703: INFO: Pod "exec-volume-test-inlinevolume-pczw" satisfied condition "Succeeded or Failed"
Sep 26 07:32:32.753: INFO: Trying to get logs from node ip-172-20-46-137.us-west-1.compute.internal pod exec-volume-test-inlinevolume-pczw container exec-container-inlinevolume-pczw: <nil>
STEP: delete the pod
Sep 26 07:32:32.876: INFO: Waiting for pod exec-volume-test-inlinevolume-pczw to disappear
Sep 26 07:32:32.926: INFO: Pod exec-volume-test-inlinevolume-pczw no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-pczw
Sep 26 07:32:32.926: INFO: Deleting pod "exec-volume-test-inlinevolume-pczw" in namespace "volume-5113"
Sep 26 07:32:33.146: INFO: Couldn't delete PD "aws://us-west-1a/vol-002ba3d6778b96aa3", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-002ba3d6778b96aa3 is currently attached to i-02155aa2ab4de4c90
	status code: 400, request id: 5c619ee9-a0d5-4e87-ba6b-781a2b57e1e2
Sep 26 07:32:38.497: INFO: Couldn't delete PD "aws://us-west-1a/vol-002ba3d6778b96aa3", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-002ba3d6778b96aa3 is currently attached to i-02155aa2ab4de4c90
	status code: 400, request id: d5f75678-be15-49a1-8112-a8f571435de9
Sep 26 07:32:43.946: INFO: Successfully deleted PD "aws://us-west-1a/vol-002ba3d6778b96aa3".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 26 07:32:43.946: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-5113" for this suite.
... skipping 96 lines ...
Sep 26 07:32:15.615: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-1707-e2e-sct8mnf
STEP: creating a claim
Sep 26 07:32:15.667: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-k9dl
STEP: Creating a pod to test exec-volume-test
Sep 26 07:32:15.831: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-k9dl" in namespace "volume-1707" to be "Succeeded or Failed"
Sep 26 07:32:15.881: INFO: Pod "exec-volume-test-dynamicpv-k9dl": Phase="Pending", Reason="", readiness=false. Elapsed: 50.502931ms
Sep 26 07:32:17.933: INFO: Pod "exec-volume-test-dynamicpv-k9dl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.101885548s
Sep 26 07:32:19.987: INFO: Pod "exec-volume-test-dynamicpv-k9dl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.156005352s
Sep 26 07:32:22.038: INFO: Pod "exec-volume-test-dynamicpv-k9dl": Phase="Pending", Reason="", readiness=false. Elapsed: 6.206947752s
Sep 26 07:32:24.089: INFO: Pod "exec-volume-test-dynamicpv-k9dl": Phase="Pending", Reason="", readiness=false. Elapsed: 8.258594989s
Sep 26 07:32:26.144: INFO: Pod "exec-volume-test-dynamicpv-k9dl": Phase="Pending", Reason="", readiness=false. Elapsed: 10.31347573s
Sep 26 07:32:28.196: INFO: Pod "exec-volume-test-dynamicpv-k9dl": Phase="Pending", Reason="", readiness=false. Elapsed: 12.365054569s
Sep 26 07:32:30.249: INFO: Pod "exec-volume-test-dynamicpv-k9dl": Phase="Pending", Reason="", readiness=false. Elapsed: 14.418228515s
Sep 26 07:32:32.300: INFO: Pod "exec-volume-test-dynamicpv-k9dl": Phase="Pending", Reason="", readiness=false. Elapsed: 16.469546518s
Sep 26 07:32:34.352: INFO: Pod "exec-volume-test-dynamicpv-k9dl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.521148177s
STEP: Saw pod success
Sep 26 07:32:34.352: INFO: Pod "exec-volume-test-dynamicpv-k9dl" satisfied condition "Succeeded or Failed"
Sep 26 07:32:34.405: INFO: Trying to get logs from node ip-172-20-46-137.us-west-1.compute.internal pod exec-volume-test-dynamicpv-k9dl container exec-container-dynamicpv-k9dl: <nil>
STEP: delete the pod
Sep 26 07:32:34.520: INFO: Waiting for pod exec-volume-test-dynamicpv-k9dl to disappear
Sep 26 07:32:34.572: INFO: Pod exec-volume-test-dynamicpv-k9dl no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-k9dl
Sep 26 07:32:34.572: INFO: Deleting pod "exec-volume-test-dynamicpv-k9dl" in namespace "volume-1707"
... skipping 66 lines ...
Sep 26 07:32:16.361: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-2236-e2e-sc22xt7
STEP: creating a claim
Sep 26 07:32:16.412: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-wqth
STEP: Creating a pod to test exec-volume-test
Sep 26 07:32:16.563: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-wqth" in namespace "volume-2236" to be "Succeeded or Failed"
Sep 26 07:32:16.612: INFO: Pod "exec-volume-test-dynamicpv-wqth": Phase="Pending", Reason="", readiness=false. Elapsed: 49.16762ms
Sep 26 07:32:18.662: INFO: Pod "exec-volume-test-dynamicpv-wqth": Phase="Pending", Reason="", readiness=false. Elapsed: 2.098555913s
Sep 26 07:32:20.715: INFO: Pod "exec-volume-test-dynamicpv-wqth": Phase="Pending", Reason="", readiness=false. Elapsed: 4.151739825s
Sep 26 07:32:22.765: INFO: Pod "exec-volume-test-dynamicpv-wqth": Phase="Pending", Reason="", readiness=false. Elapsed: 6.202295066s
Sep 26 07:32:24.815: INFO: Pod "exec-volume-test-dynamicpv-wqth": Phase="Pending", Reason="", readiness=false. Elapsed: 8.252203887s
Sep 26 07:32:26.869: INFO: Pod "exec-volume-test-dynamicpv-wqth": Phase="Pending", Reason="", readiness=false. Elapsed: 10.305791738s
Sep 26 07:32:28.919: INFO: Pod "exec-volume-test-dynamicpv-wqth": Phase="Pending", Reason="", readiness=false. Elapsed: 12.356395243s
Sep 26 07:32:30.970: INFO: Pod "exec-volume-test-dynamicpv-wqth": Phase="Pending", Reason="", readiness=false. Elapsed: 14.407095031s
Sep 26 07:32:33.021: INFO: Pod "exec-volume-test-dynamicpv-wqth": Phase="Pending", Reason="", readiness=false. Elapsed: 16.458020029s
Sep 26 07:32:35.071: INFO: Pod "exec-volume-test-dynamicpv-wqth": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.507788298s
STEP: Saw pod success
Sep 26 07:32:35.071: INFO: Pod "exec-volume-test-dynamicpv-wqth" satisfied condition "Succeeded or Failed"
Sep 26 07:32:35.122: INFO: Trying to get logs from node ip-172-20-37-99.us-west-1.compute.internal pod exec-volume-test-dynamicpv-wqth container exec-container-dynamicpv-wqth: <nil>
STEP: delete the pod
Sep 26 07:32:36.102: INFO: Waiting for pod exec-volume-test-dynamicpv-wqth to disappear
Sep 26 07:32:36.151: INFO: Pod exec-volume-test-dynamicpv-wqth no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-wqth
Sep 26 07:32:36.151: INFO: Deleting pod "exec-volume-test-dynamicpv-wqth" in namespace "volume-2236"
... skipping 36 lines ...
Sep 26 07:32:14.865: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6991846mm
STEP: creating a claim
Sep 26 07:32:14.916: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-659c
STEP: Creating a pod to test multi_subpath
Sep 26 07:32:15.079: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-659c" in namespace "provisioning-6991" to be "Succeeded or Failed"
Sep 26 07:32:15.131: INFO: Pod "pod-subpath-test-dynamicpv-659c": Phase="Pending", Reason="", readiness=false. Elapsed: 52.262906ms
Sep 26 07:32:17.184: INFO: Pod "pod-subpath-test-dynamicpv-659c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.104668742s
Sep 26 07:32:19.244: INFO: Pod "pod-subpath-test-dynamicpv-659c": Phase="Pending", Reason="", readiness=false. Elapsed: 4.165277762s
Sep 26 07:32:21.298: INFO: Pod "pod-subpath-test-dynamicpv-659c": Phase="Pending", Reason="", readiness=false. Elapsed: 6.219073418s
Sep 26 07:32:23.349: INFO: Pod "pod-subpath-test-dynamicpv-659c": Phase="Pending", Reason="", readiness=false. Elapsed: 8.270226802s
Sep 26 07:32:25.403: INFO: Pod "pod-subpath-test-dynamicpv-659c": Phase="Pending", Reason="", readiness=false. Elapsed: 10.323536931s
Sep 26 07:32:27.456: INFO: Pod "pod-subpath-test-dynamicpv-659c": Phase="Pending", Reason="", readiness=false. Elapsed: 12.376549382s
Sep 26 07:32:29.507: INFO: Pod "pod-subpath-test-dynamicpv-659c": Phase="Pending", Reason="", readiness=false. Elapsed: 14.427806301s
Sep 26 07:32:31.559: INFO: Pod "pod-subpath-test-dynamicpv-659c": Phase="Pending", Reason="", readiness=false. Elapsed: 16.479761818s
Sep 26 07:32:33.612: INFO: Pod "pod-subpath-test-dynamicpv-659c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.533131596s
STEP: Saw pod success
Sep 26 07:32:33.612: INFO: Pod "pod-subpath-test-dynamicpv-659c" satisfied condition "Succeeded or Failed"
Sep 26 07:32:33.664: INFO: Trying to get logs from node ip-172-20-46-137.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-659c container test-container-subpath-dynamicpv-659c: <nil>
STEP: delete the pod
Sep 26 07:32:33.776: INFO: Waiting for pod pod-subpath-test-dynamicpv-659c to disappear
Sep 26 07:32:33.827: INFO: Pod pod-subpath-test-dynamicpv-659c no longer exists
STEP: Deleting pod
Sep 26 07:32:33.827: INFO: Deleting pod "pod-subpath-test-dynamicpv-659c" in namespace "provisioning-6991"
... skipping 98 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.h0A0b3MTk/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.h0A0b3MTk/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.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 21 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 26 07:32:14.750: 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.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Sep 26 07:32:17.163: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Sep 26 07:32:17.163: INFO: Creating resource for dynamic PV
Sep 26 07:32:17.163: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6536r4k9g
STEP: creating a claim
Sep 26 07:32:17.218: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-vc4m
STEP: Checking for subpath error in container status
Sep 26 07:32:41.481: INFO: Deleting pod "pod-subpath-test-dynamicpv-vc4m" in namespace "provisioning-6536"
Sep 26 07:32:41.535: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-vc4m" to be fully deleted
STEP: Deleting pod
Sep 26 07:32:47.635: INFO: Deleting pod "pod-subpath-test-dynamicpv-vc4m" in namespace "provisioning-6536"
STEP: Deleting pvc
Sep 26 07:32:47.786: INFO: Deleting PersistentVolumeClaim "awsrblhk"
... skipping 12 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.h0A0b3MTk/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.h0A0b3MTk/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath file is outside the volume [Slow][LinuxOnly]
      /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow]
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Sep 26 07:32:58.169: INFO: Driver supports dynamic provisioning, skipping PreprovisionedPV pattern
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow]
... skipping 23 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.h0A0b3MTk/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.h0A0b3MTk/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.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 43 lines ...
STEP: Deleting pod hostexec-ip-172-20-37-99.us-west-1.compute.internal-v5xf8 in namespace volumemode-2233
Sep 26 07:32:44.446: INFO: Deleting pod "pod-039a3048-1731-4c6f-b51d-fc684179ea06" in namespace "volumemode-2233"
Sep 26 07:32:44.498: INFO: Wait up to 5m0s for pod "pod-039a3048-1731-4c6f-b51d-fc684179ea06" to be fully deleted
STEP: Deleting pv and pvc
Sep 26 07:32:52.600: INFO: Deleting PersistentVolumeClaim "pvc-nlrqq"
Sep 26 07:32:52.651: INFO: Deleting PersistentVolume "aws-dvqtw"
Sep 26 07:32:52.891: INFO: Couldn't delete PD "aws://us-west-1a/vol-0f7fb86f7e77d780a", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f7fb86f7e77d780a is currently attached to i-009d6e8a60bfe9013
	status code: 400, request id: 6b77c64b-c6b4-4425-9864-3497c3656b23
Sep 26 07:32:58.256: INFO: Couldn't delete PD "aws://us-west-1a/vol-0f7fb86f7e77d780a", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f7fb86f7e77d780a is currently attached to i-009d6e8a60bfe9013
	status code: 400, request id: 8d3a865c-f7ec-4751-94da-f6ce65bb981a
Sep 26 07:33:03.628: INFO: Successfully deleted PD "aws://us-west-1a/vol-0f7fb86f7e77d780a".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 26 07:33:03.628: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-2233" for this suite.
... skipping 149 lines ...
Sep 26 07:32:17.214: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-1570-e2e-scpwf54
STEP: creating a claim
Sep 26 07:32:17.266: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-7k9h
STEP: Creating a pod to test exec-volume-test
Sep 26 07:32:17.426: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-7k9h" in namespace "volume-1570" to be "Succeeded or Failed"
Sep 26 07:32:17.476: INFO: Pod "exec-volume-test-dynamicpv-7k9h": Phase="Pending", Reason="", readiness=false. Elapsed: 50.08358ms
Sep 26 07:32:19.531: INFO: Pod "exec-volume-test-dynamicpv-7k9h": Phase="Pending", Reason="", readiness=false. Elapsed: 2.104873565s
Sep 26 07:32:21.583: INFO: Pod "exec-volume-test-dynamicpv-7k9h": Phase="Pending", Reason="", readiness=false. Elapsed: 4.157399009s
Sep 26 07:32:23.635: INFO: Pod "exec-volume-test-dynamicpv-7k9h": Phase="Pending", Reason="", readiness=false. Elapsed: 6.208992313s
Sep 26 07:32:25.685: INFO: Pod "exec-volume-test-dynamicpv-7k9h": Phase="Pending", Reason="", readiness=false. Elapsed: 8.259689774s
Sep 26 07:32:27.737: INFO: Pod "exec-volume-test-dynamicpv-7k9h": Phase="Pending", Reason="", readiness=false. Elapsed: 10.311406631s
Sep 26 07:32:29.789: INFO: Pod "exec-volume-test-dynamicpv-7k9h": Phase="Pending", Reason="", readiness=false. Elapsed: 12.363171985s
Sep 26 07:32:31.841: INFO: Pod "exec-volume-test-dynamicpv-7k9h": Phase="Pending", Reason="", readiness=false. Elapsed: 14.414840885s
Sep 26 07:32:33.891: INFO: Pod "exec-volume-test-dynamicpv-7k9h": Phase="Pending", Reason="", readiness=false. Elapsed: 16.465728367s
Sep 26 07:32:35.943: INFO: Pod "exec-volume-test-dynamicpv-7k9h": Phase="Pending", Reason="", readiness=false. Elapsed: 18.517179612s
Sep 26 07:32:37.994: INFO: Pod "exec-volume-test-dynamicpv-7k9h": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.56809653s
STEP: Saw pod success
Sep 26 07:32:37.994: INFO: Pod "exec-volume-test-dynamicpv-7k9h" satisfied condition "Succeeded or Failed"
Sep 26 07:32:38.045: INFO: Trying to get logs from node ip-172-20-35-50.us-west-1.compute.internal pod exec-volume-test-dynamicpv-7k9h container exec-container-dynamicpv-7k9h: <nil>
STEP: delete the pod
Sep 26 07:32:38.156: INFO: Waiting for pod exec-volume-test-dynamicpv-7k9h to disappear
Sep 26 07:32:38.208: INFO: Pod exec-volume-test-dynamicpv-7k9h no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-7k9h
Sep 26 07:32:38.208: INFO: Deleting pod "exec-volume-test-dynamicpv-7k9h" in namespace "volume-1570"
... skipping 30 lines ...
STEP: Creating a kubernetes client
Sep 26 07:32:13.962: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename provisioning
W0926 07:32:14.866194   26401 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Sep 26 07:32:14.866: 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 directory is outside the volume [Slow][LinuxOnly]
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Sep 26 07:32:14.963: INFO: Creating resource for dynamic PV
Sep 26 07:32:14.963: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4323-e2e-sczvcw5
STEP: creating a claim
Sep 26 07:32:15.013: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-2qpj
STEP: Checking for subpath error in container status
Sep 26 07:32:49.275: INFO: Deleting pod "pod-subpath-test-dynamicpv-2qpj" in namespace "provisioning-4323"
Sep 26 07:32:49.325: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-2qpj" to be fully deleted
STEP: Deleting pod
Sep 26 07:32:55.424: INFO: Deleting pod "pod-subpath-test-dynamicpv-2qpj" in namespace "provisioning-4323"
STEP: Deleting pvc
Sep 26 07:32:55.580: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comltxqg"
... skipping 12 lines ...

• [SLOW TEST:62.126 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath directory is outside the volume [Slow][LinuxOnly]
    /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] provisioning
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] provisioning
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 11 lines ...
Sep 26 07:32:14.124: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-7960k5q4m      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-7960    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-7960k5q4m,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-7960    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-7960k5q4m,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-7960    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-7960k5q4m,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-7960k5q4m    edc3b1cd-fa63-4f46-8126-3a952c450900 2531 0 2021-09-26 07:32:14 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-09-26 07:32:14 +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-vkltq pvc- provisioning-7960  51400ac1-36ed-4895-a1d2-abb0a5e9cd62 2564 0 2021-09-26 07:32:14 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-09-26 07:32:14 +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-7960k5q4m,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-b4c6a76d-2e41-4ca6-ab05-229f852948a6 in namespace provisioning-7960
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Sep 26 07:32:28.789: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-79x5l" in namespace "provisioning-7960" to be "Succeeded or Failed"
Sep 26 07:32:28.840: INFO: Pod "pvc-volume-tester-writer-79x5l": Phase="Pending", Reason="", readiness=false. Elapsed: 51.214491ms
Sep 26 07:32:30.889: INFO: Pod "pvc-volume-tester-writer-79x5l": Phase="Pending", Reason="", readiness=false. Elapsed: 2.100604322s
Sep 26 07:32:32.939: INFO: Pod "pvc-volume-tester-writer-79x5l": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.150464494s
STEP: Saw pod success
Sep 26 07:32:32.939: INFO: Pod "pvc-volume-tester-writer-79x5l" satisfied condition "Succeeded or Failed"
Sep 26 07:32:33.526: INFO: Pod pvc-volume-tester-writer-79x5l has the following logs: 
Sep 26 07:32:33.526: INFO: Deleting pod "pvc-volume-tester-writer-79x5l" in namespace "provisioning-7960"
Sep 26 07:32:33.582: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-79x5l" 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-54-151.us-west-1.compute.internal"
Sep 26 07:32:33.794: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-8t9rc" in namespace "provisioning-7960" to be "Succeeded or Failed"
Sep 26 07:32:33.843: INFO: Pod "pvc-volume-tester-reader-8t9rc": Phase="Pending", Reason="", readiness=false. Elapsed: 49.17563ms
Sep 26 07:32:35.894: INFO: Pod "pvc-volume-tester-reader-8t9rc": Phase="Pending", Reason="", readiness=false. Elapsed: 2.099871348s
Sep 26 07:32:37.944: INFO: Pod "pvc-volume-tester-reader-8t9rc": Phase="Pending", Reason="", readiness=false. Elapsed: 4.150251488s
Sep 26 07:32:39.994: INFO: Pod "pvc-volume-tester-reader-8t9rc": Phase="Pending", Reason="", readiness=false. Elapsed: 6.199692193s
Sep 26 07:32:42.048: INFO: Pod "pvc-volume-tester-reader-8t9rc": Phase="Pending", Reason="", readiness=false. Elapsed: 8.253590847s
Sep 26 07:32:44.097: INFO: Pod "pvc-volume-tester-reader-8t9rc": Phase="Pending", Reason="", readiness=false. Elapsed: 10.303019273s
Sep 26 07:32:46.148: INFO: Pod "pvc-volume-tester-reader-8t9rc": Phase="Pending", Reason="", readiness=false. Elapsed: 12.353410958s
Sep 26 07:32:48.198: INFO: Pod "pvc-volume-tester-reader-8t9rc": Phase="Pending", Reason="", readiness=false. Elapsed: 14.403473183s
Sep 26 07:32:50.249: INFO: Pod "pvc-volume-tester-reader-8t9rc": Phase="Pending", Reason="", readiness=false. Elapsed: 16.455094251s
Sep 26 07:32:52.300: INFO: Pod "pvc-volume-tester-reader-8t9rc": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.505880075s
STEP: Saw pod success
Sep 26 07:32:52.300: INFO: Pod "pvc-volume-tester-reader-8t9rc" satisfied condition "Succeeded or Failed"
Sep 26 07:32:52.405: INFO: Pod pvc-volume-tester-reader-8t9rc has the following logs: hello world

Sep 26 07:32:52.405: INFO: Deleting pod "pvc-volume-tester-reader-8t9rc" in namespace "provisioning-7960"
Sep 26 07:32:52.463: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-8t9rc" to be fully deleted
Sep 26 07:32:52.512: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-vkltq] to have phase Bound
Sep 26 07:32:52.561: INFO: PersistentVolumeClaim pvc-vkltq found and phase=Bound (49.095413ms)
... skipping 81 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 26 07:32:19.219: 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.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Sep 26 07:32:19.473: INFO: Creating resource for dynamic PV
Sep 26 07:32:19.473: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8724-e2e-scklj7f
STEP: creating a claim
Sep 26 07:32:19.533: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-knjz
STEP: Checking for subpath error in container status
Sep 26 07:32:45.811: INFO: Deleting pod "pod-subpath-test-dynamicpv-knjz" in namespace "provisioning-8724"
Sep 26 07:32:45.871: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-knjz" to be fully deleted
STEP: Deleting pod
Sep 26 07:32:47.976: INFO: Deleting pod "pod-subpath-test-dynamicpv-knjz" in namespace "provisioning-8724"
STEP: Deleting pvc
Sep 26 07:32:48.127: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comj76tl"
... skipping 15 lines ...

• [SLOW TEST:64.535 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath file is outside the volume [Slow][LinuxOnly]
    /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)(allowExpansion)][Feature:Windows] volume-expand
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Sep 26 07:33:23.756: INFO: Driver ebs.csi.aws.com doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)(allowExpansion)][Feature:Windows] volume-expand
... skipping 227 lines ...
Sep 26 07:32:14.297: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-65737qg6q
STEP: creating a claim
Sep 26 07:32:14.351: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-l8nd
STEP: Creating a pod to test subpath
Sep 26 07:32:14.542: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-l8nd" in namespace "provisioning-6573" to be "Succeeded or Failed"
Sep 26 07:32:14.602: INFO: Pod "pod-subpath-test-dynamicpv-l8nd": Phase="Pending", Reason="", readiness=false. Elapsed: 60.472068ms
Sep 26 07:32:16.656: INFO: Pod "pod-subpath-test-dynamicpv-l8nd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.113840767s
Sep 26 07:32:18.719: INFO: Pod "pod-subpath-test-dynamicpv-l8nd": Phase="Pending", Reason="", readiness=false. Elapsed: 4.177336349s
Sep 26 07:32:20.771: INFO: Pod "pod-subpath-test-dynamicpv-l8nd": Phase="Pending", Reason="", readiness=false. Elapsed: 6.228965701s
Sep 26 07:32:22.823: INFO: Pod "pod-subpath-test-dynamicpv-l8nd": Phase="Pending", Reason="", readiness=false. Elapsed: 8.280616522s
Sep 26 07:32:24.874: INFO: Pod "pod-subpath-test-dynamicpv-l8nd": Phase="Pending", Reason="", readiness=false. Elapsed: 10.332461207s
Sep 26 07:32:26.925: INFO: Pod "pod-subpath-test-dynamicpv-l8nd": Phase="Pending", Reason="", readiness=false. Elapsed: 12.383050878s
Sep 26 07:32:28.976: INFO: Pod "pod-subpath-test-dynamicpv-l8nd": Phase="Pending", Reason="", readiness=false. Elapsed: 14.433846259s
Sep 26 07:32:31.027: INFO: Pod "pod-subpath-test-dynamicpv-l8nd": Phase="Pending", Reason="", readiness=false. Elapsed: 16.48475966s
Sep 26 07:32:33.078: INFO: Pod "pod-subpath-test-dynamicpv-l8nd": Phase="Pending", Reason="", readiness=false. Elapsed: 18.536297141s
Sep 26 07:32:35.129: INFO: Pod "pod-subpath-test-dynamicpv-l8nd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.58694862s
STEP: Saw pod success
Sep 26 07:32:35.129: INFO: Pod "pod-subpath-test-dynamicpv-l8nd" satisfied condition "Succeeded or Failed"
Sep 26 07:32:35.180: INFO: Trying to get logs from node ip-172-20-35-50.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-l8nd container test-container-subpath-dynamicpv-l8nd: <nil>
STEP: delete the pod
Sep 26 07:32:35.741: INFO: Waiting for pod pod-subpath-test-dynamicpv-l8nd to disappear
Sep 26 07:32:35.794: INFO: Pod pod-subpath-test-dynamicpv-l8nd no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-l8nd
Sep 26 07:32:35.794: INFO: Deleting pod "pod-subpath-test-dynamicpv-l8nd" in namespace "provisioning-6573"
STEP: Creating pod pod-subpath-test-dynamicpv-l8nd
STEP: Creating a pod to test subpath
Sep 26 07:32:35.895: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-l8nd" in namespace "provisioning-6573" to be "Succeeded or Failed"
Sep 26 07:32:35.946: INFO: Pod "pod-subpath-test-dynamicpv-l8nd": Phase="Pending", Reason="", readiness=false. Elapsed: 50.275208ms
Sep 26 07:32:37.997: INFO: Pod "pod-subpath-test-dynamicpv-l8nd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.101257826s
Sep 26 07:32:40.051: INFO: Pod "pod-subpath-test-dynamicpv-l8nd": Phase="Pending", Reason="", readiness=false. Elapsed: 4.156034779s
Sep 26 07:32:42.102: INFO: Pod "pod-subpath-test-dynamicpv-l8nd": Phase="Pending", Reason="", readiness=false. Elapsed: 6.206884307s
Sep 26 07:32:44.153: INFO: Pod "pod-subpath-test-dynamicpv-l8nd": Phase="Pending", Reason="", readiness=false. Elapsed: 8.257514282s
Sep 26 07:32:46.205: INFO: Pod "pod-subpath-test-dynamicpv-l8nd": Phase="Pending", Reason="", readiness=false. Elapsed: 10.309442667s
... skipping 7 lines ...
Sep 26 07:33:02.613: INFO: Pod "pod-subpath-test-dynamicpv-l8nd": Phase="Pending", Reason="", readiness=false. Elapsed: 26.71780592s
Sep 26 07:33:04.665: INFO: Pod "pod-subpath-test-dynamicpv-l8nd": Phase="Pending", Reason="", readiness=false. Elapsed: 28.769253349s
Sep 26 07:33:06.716: INFO: Pod "pod-subpath-test-dynamicpv-l8nd": Phase="Pending", Reason="", readiness=false. Elapsed: 30.820582537s
Sep 26 07:33:08.767: INFO: Pod "pod-subpath-test-dynamicpv-l8nd": Phase="Pending", Reason="", readiness=false. Elapsed: 32.872015919s
Sep 26 07:33:10.818: INFO: Pod "pod-subpath-test-dynamicpv-l8nd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.923023283s
STEP: Saw pod success
Sep 26 07:33:10.818: INFO: Pod "pod-subpath-test-dynamicpv-l8nd" satisfied condition "Succeeded or Failed"
Sep 26 07:33:10.868: INFO: Trying to get logs from node ip-172-20-46-137.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-l8nd container test-container-subpath-dynamicpv-l8nd: <nil>
STEP: delete the pod
Sep 26 07:33:10.976: INFO: Waiting for pod pod-subpath-test-dynamicpv-l8nd to disappear
Sep 26 07:33:11.026: INFO: Pod pod-subpath-test-dynamicpv-l8nd no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-l8nd
Sep 26 07:33:11.026: INFO: Deleting pod "pod-subpath-test-dynamicpv-l8nd" in namespace "provisioning-6573"
... skipping 84 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 26 07:32:44.774: 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.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Sep 26 07:32:45.031: INFO: Creating resource for dynamic PV
Sep 26 07:32:45.031: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2259-e2e-scvw62q
STEP: creating a claim
Sep 26 07:32:45.085: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-njbm
STEP: Checking for subpath error in container status
Sep 26 07:33:07.343: INFO: Deleting pod "pod-subpath-test-dynamicpv-njbm" in namespace "provisioning-2259"
Sep 26 07:33:07.397: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-njbm" to be fully deleted
STEP: Deleting pod
Sep 26 07:33:09.500: INFO: Deleting pod "pod-subpath-test-dynamicpv-njbm" in namespace "provisioning-2259"
STEP: Deleting pvc
Sep 26 07:33:09.650: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comb44w4"
... skipping 12 lines ...

• [SLOW TEST:45.347 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.h0A0b3MTk/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.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [sig-storage] Storage Policy Based Volume Provisioning [Feature:vsphere]
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 26 07:33:30.122: INFO: >>> kubeConfig: /root/.kube/config
... skipping 314 lines ...
Sep 26 07:32:50.840: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6326cl8kh
STEP: creating a claim
Sep 26 07:32:50.892: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-6vcn
STEP: Creating a pod to test subpath
Sep 26 07:32:51.049: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-6vcn" in namespace "provisioning-6326" to be "Succeeded or Failed"
Sep 26 07:32:51.100: INFO: Pod "pod-subpath-test-dynamicpv-6vcn": Phase="Pending", Reason="", readiness=false. Elapsed: 50.903737ms
Sep 26 07:32:53.151: INFO: Pod "pod-subpath-test-dynamicpv-6vcn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.102039079s
Sep 26 07:32:55.480: INFO: Pod "pod-subpath-test-dynamicpv-6vcn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.430955065s
Sep 26 07:32:57.531: INFO: Pod "pod-subpath-test-dynamicpv-6vcn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.482334061s
Sep 26 07:32:59.583: INFO: Pod "pod-subpath-test-dynamicpv-6vcn": Phase="Pending", Reason="", readiness=false. Elapsed: 8.534046852s
Sep 26 07:33:01.637: INFO: Pod "pod-subpath-test-dynamicpv-6vcn": Phase="Pending", Reason="", readiness=false. Elapsed: 10.588270564s
Sep 26 07:33:03.696: INFO: Pod "pod-subpath-test-dynamicpv-6vcn": Phase="Pending", Reason="", readiness=false. Elapsed: 12.647229237s
Sep 26 07:33:05.747: INFO: Pod "pod-subpath-test-dynamicpv-6vcn": Phase="Pending", Reason="", readiness=false. Elapsed: 14.698134175s
Sep 26 07:33:07.798: INFO: Pod "pod-subpath-test-dynamicpv-6vcn": Phase="Pending", Reason="", readiness=false. Elapsed: 16.748977208s
Sep 26 07:33:09.851: INFO: Pod "pod-subpath-test-dynamicpv-6vcn": Phase="Pending", Reason="", readiness=false. Elapsed: 18.801716379s
Sep 26 07:33:11.902: INFO: Pod "pod-subpath-test-dynamicpv-6vcn": Phase="Pending", Reason="", readiness=false. Elapsed: 20.853514365s
Sep 26 07:33:13.954: INFO: Pod "pod-subpath-test-dynamicpv-6vcn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.904821849s
STEP: Saw pod success
Sep 26 07:33:13.954: INFO: Pod "pod-subpath-test-dynamicpv-6vcn" satisfied condition "Succeeded or Failed"
Sep 26 07:33:14.007: INFO: Trying to get logs from node ip-172-20-35-50.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-6vcn container test-container-subpath-dynamicpv-6vcn: <nil>
STEP: delete the pod
Sep 26 07:33:14.121: INFO: Waiting for pod pod-subpath-test-dynamicpv-6vcn to disappear
Sep 26 07:33:14.173: INFO: Pod pod-subpath-test-dynamicpv-6vcn no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-6vcn
Sep 26 07:33:14.173: INFO: Deleting pod "pod-subpath-test-dynamicpv-6vcn" in namespace "provisioning-6326"
... skipping 33 lines ...

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

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 283 lines ...
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 26 07:33:42.439: 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.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Sep 26 07:33:42.745: INFO: found topology map[topology.kubernetes.io/zone:us-west-1a]
Sep 26 07:33:42.745: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Sep 26 07:33:42.745: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.h0A0b3MTk/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.h0A0b3MTk/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (immediate binding)] topology
    /tmp/kops.h0A0b3MTk/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.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 2 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 26 07:33:13.980: 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.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Sep 26 07:33:14.235: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Sep 26 07:33:14.235: INFO: Creating resource for dynamic PV
Sep 26 07:33:14.235: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-1172rs277
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Sep 26 07:33:20.599: INFO: Deleting pod "pod-c58f2e51-fabb-413a-ba6d-bf610fb814b2" in namespace "volumemode-1172"
Sep 26 07:33:20.652: INFO: Wait up to 5m0s for pod "pod-c58f2e51-fabb-413a-ba6d-bf610fb814b2" to be fully deleted
STEP: Deleting pvc
Sep 26 07:33:22.855: INFO: Deleting PersistentVolumeClaim "awsc7z7m"
Sep 26 07:33:22.910: INFO: Waiting up to 5m0s for PersistentVolume pvc-33dbfc3a-7e4a-41e4-a325-647b9c74f700 to get deleted
Sep 26 07:33:22.960: INFO: PersistentVolume pvc-33dbfc3a-7e4a-41e4-a325-647b9c74f700 found and phase=Released (50.287365ms)
... skipping 12 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.h0A0b3MTk/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.h0A0b3MTk/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (block volmode)] volumeMode
    /tmp/kops.h0A0b3MTk/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.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Sep 26 07:33:43.331: INFO: Distro debian doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning
... skipping 243 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.h0A0b3MTk/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.h0A0b3MTk/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.h0A0b3MTk/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.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Driver supports dynamic provisioning, skipping InlineVolume pattern

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 12 lines ...
Sep 26 07:33:27.674: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-8498d7r4v
STEP: creating a claim
Sep 26 07:33:27.725: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-h9cj
STEP: Creating a pod to test exec-volume-test
Sep 26 07:33:27.884: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-h9cj" in namespace "volume-8498" to be "Succeeded or Failed"
Sep 26 07:33:27.934: INFO: Pod "exec-volume-test-dynamicpv-h9cj": Phase="Pending", Reason="", readiness=false. Elapsed: 50.447767ms
Sep 26 07:33:29.985: INFO: Pod "exec-volume-test-dynamicpv-h9cj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.101637719s
Sep 26 07:33:32.037: INFO: Pod "exec-volume-test-dynamicpv-h9cj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.152940348s
Sep 26 07:33:34.088: INFO: Pod "exec-volume-test-dynamicpv-h9cj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.204060361s
Sep 26 07:33:36.139: INFO: Pod "exec-volume-test-dynamicpv-h9cj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.255581642s
Sep 26 07:33:38.191: INFO: Pod "exec-volume-test-dynamicpv-h9cj": Phase="Pending", Reason="", readiness=false. Elapsed: 10.307555845s
Sep 26 07:33:40.248: INFO: Pod "exec-volume-test-dynamicpv-h9cj": Phase="Pending", Reason="", readiness=false. Elapsed: 12.363966935s
Sep 26 07:33:42.301: INFO: Pod "exec-volume-test-dynamicpv-h9cj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.416936297s
STEP: Saw pod success
Sep 26 07:33:42.301: INFO: Pod "exec-volume-test-dynamicpv-h9cj" satisfied condition "Succeeded or Failed"
Sep 26 07:33:42.355: INFO: Trying to get logs from node ip-172-20-46-137.us-west-1.compute.internal pod exec-volume-test-dynamicpv-h9cj container exec-container-dynamicpv-h9cj: <nil>
STEP: delete the pod
Sep 26 07:33:42.467: INFO: Waiting for pod exec-volume-test-dynamicpv-h9cj to disappear
Sep 26 07:33:42.518: INFO: Pod exec-volume-test-dynamicpv-h9cj no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-h9cj
Sep 26 07:33:42.518: INFO: Deleting pod "exec-volume-test-dynamicpv-h9cj" in namespace "volume-8498"
... skipping 52 lines ...
Sep 26 07:33:34.003: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Sep 26 07:33:34.514: INFO: Successfully created a new PD: "aws://us-west-1a/vol-005fb2a86311ea72b".
Sep 26 07:33:34.514: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-4dwr
STEP: Creating a pod to test exec-volume-test
Sep 26 07:33:34.565: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-4dwr" in namespace "volume-7366" to be "Succeeded or Failed"
Sep 26 07:33:34.614: INFO: Pod "exec-volume-test-inlinevolume-4dwr": Phase="Pending", Reason="", readiness=false. Elapsed: 49.553588ms
Sep 26 07:33:36.665: INFO: Pod "exec-volume-test-inlinevolume-4dwr": Phase="Pending", Reason="", readiness=false. Elapsed: 2.100447472s
Sep 26 07:33:38.716: INFO: Pod "exec-volume-test-inlinevolume-4dwr": Phase="Pending", Reason="", readiness=false. Elapsed: 4.151414388s
Sep 26 07:33:40.768: INFO: Pod "exec-volume-test-inlinevolume-4dwr": Phase="Pending", Reason="", readiness=false. Elapsed: 6.203129821s
Sep 26 07:33:42.819: INFO: Pod "exec-volume-test-inlinevolume-4dwr": Phase="Pending", Reason="", readiness=false. Elapsed: 8.253816682s
Sep 26 07:33:44.869: INFO: Pod "exec-volume-test-inlinevolume-4dwr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.304079161s
STEP: Saw pod success
Sep 26 07:33:44.869: INFO: Pod "exec-volume-test-inlinevolume-4dwr" satisfied condition "Succeeded or Failed"
Sep 26 07:33:44.919: INFO: Trying to get logs from node ip-172-20-35-50.us-west-1.compute.internal pod exec-volume-test-inlinevolume-4dwr container exec-container-inlinevolume-4dwr: <nil>
STEP: delete the pod
Sep 26 07:33:45.026: INFO: Waiting for pod exec-volume-test-inlinevolume-4dwr to disappear
Sep 26 07:33:45.078: INFO: Pod exec-volume-test-inlinevolume-4dwr no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-4dwr
Sep 26 07:33:45.078: INFO: Deleting pod "exec-volume-test-inlinevolume-4dwr" in namespace "volume-7366"
Sep 26 07:33:45.284: INFO: Couldn't delete PD "aws://us-west-1a/vol-005fb2a86311ea72b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-005fb2a86311ea72b is currently attached to i-0c0aac37066181110
	status code: 400, request id: fd273013-06d8-45b5-9c50-69cc84325bb2
Sep 26 07:33:50.622: INFO: Couldn't delete PD "aws://us-west-1a/vol-005fb2a86311ea72b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-005fb2a86311ea72b is currently attached to i-0c0aac37066181110
	status code: 400, request id: 8d79a2b6-9b42-4570-a102-e56195ea1667
Sep 26 07:33:56.013: INFO: Couldn't delete PD "aws://us-west-1a/vol-005fb2a86311ea72b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-005fb2a86311ea72b is currently attached to i-0c0aac37066181110
	status code: 400, request id: c1739736-6307-488e-9d7b-91b0503d1b42
Sep 26 07:34:01.392: INFO: Successfully deleted PD "aws://us-west-1a/vol-005fb2a86311ea72b".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 26 07:34:01.392: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-7366" for this suite.
... skipping 174 lines ...
Sep 26 07:33:16.341: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8063hh9dk
STEP: creating a claim
Sep 26 07:33:16.391: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-wlhn
STEP: Creating a pod to test subpath
Sep 26 07:33:16.543: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-wlhn" in namespace "provisioning-8063" to be "Succeeded or Failed"
Sep 26 07:33:16.592: INFO: Pod "pod-subpath-test-dynamicpv-wlhn": Phase="Pending", Reason="", readiness=false. Elapsed: 49.027269ms
Sep 26 07:33:18.642: INFO: Pod "pod-subpath-test-dynamicpv-wlhn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.098537924s
Sep 26 07:33:20.691: INFO: Pod "pod-subpath-test-dynamicpv-wlhn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.148026016s
Sep 26 07:33:22.741: INFO: Pod "pod-subpath-test-dynamicpv-wlhn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.197633591s
Sep 26 07:33:24.790: INFO: Pod "pod-subpath-test-dynamicpv-wlhn": Phase="Pending", Reason="", readiness=false. Elapsed: 8.247239243s
Sep 26 07:33:26.843: INFO: Pod "pod-subpath-test-dynamicpv-wlhn": Phase="Pending", Reason="", readiness=false. Elapsed: 10.299620963s
... skipping 2 lines ...
Sep 26 07:33:32.994: INFO: Pod "pod-subpath-test-dynamicpv-wlhn": Phase="Pending", Reason="", readiness=false. Elapsed: 16.4505769s
Sep 26 07:33:35.044: INFO: Pod "pod-subpath-test-dynamicpv-wlhn": Phase="Pending", Reason="", readiness=false. Elapsed: 18.500686559s
Sep 26 07:33:37.094: INFO: Pod "pod-subpath-test-dynamicpv-wlhn": Phase="Pending", Reason="", readiness=false. Elapsed: 20.551159623s
Sep 26 07:33:39.145: INFO: Pod "pod-subpath-test-dynamicpv-wlhn": Phase="Pending", Reason="", readiness=false. Elapsed: 22.602326847s
Sep 26 07:33:41.196: INFO: Pod "pod-subpath-test-dynamicpv-wlhn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.652824999s
STEP: Saw pod success
Sep 26 07:33:41.196: INFO: Pod "pod-subpath-test-dynamicpv-wlhn" satisfied condition "Succeeded or Failed"
Sep 26 07:33:41.247: INFO: Trying to get logs from node ip-172-20-37-99.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-wlhn container test-container-subpath-dynamicpv-wlhn: <nil>
STEP: delete the pod
Sep 26 07:33:41.359: INFO: Waiting for pod pod-subpath-test-dynamicpv-wlhn to disappear
Sep 26 07:33:41.409: INFO: Pod pod-subpath-test-dynamicpv-wlhn no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-wlhn
Sep 26 07:33:41.409: INFO: Deleting pod "pod-subpath-test-dynamicpv-wlhn" in namespace "provisioning-8063"
... skipping 80 lines ...
Sep 26 07:33:41.908: INFO: Creating resource for dynamic PV
Sep 26 07:33:41.908: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-8249-e2e-scjlbr8
STEP: creating a claim
STEP: Expanding non-expandable pvc
Sep 26 07:33:42.060: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Sep 26 07:33:42.165: INFO: Error updating pvc ebs.csi.aws.com67xrs: PersistentVolumeClaim "ebs.csi.aws.com67xrs" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8249-e2e-scjlbr8",
  	... // 3 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Sep 26 07:34:12.368: INFO: Error updating pvc ebs.csi.aws.com67xrs: PersistentVolumeClaim "ebs.csi.aws.com67xrs" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 135 lines ...
Sep 26 07:33:26.784: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3620-e2e-scxxb28
STEP: creating a claim
Sep 26 07:33:26.834: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-dmtf
STEP: Creating a pod to test subpath
Sep 26 07:33:26.987: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-dmtf" in namespace "provisioning-3620" to be "Succeeded or Failed"
Sep 26 07:33:27.036: INFO: Pod "pod-subpath-test-dynamicpv-dmtf": Phase="Pending", Reason="", readiness=false. Elapsed: 49.578499ms
Sep 26 07:33:29.086: INFO: Pod "pod-subpath-test-dynamicpv-dmtf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.099228369s
Sep 26 07:33:31.137: INFO: Pod "pod-subpath-test-dynamicpv-dmtf": Phase="Pending", Reason="", readiness=false. Elapsed: 4.150368431s
Sep 26 07:33:33.188: INFO: Pod "pod-subpath-test-dynamicpv-dmtf": Phase="Pending", Reason="", readiness=false. Elapsed: 6.200876394s
Sep 26 07:33:35.254: INFO: Pod "pod-subpath-test-dynamicpv-dmtf": Phase="Pending", Reason="", readiness=false. Elapsed: 8.26710087s
Sep 26 07:33:37.304: INFO: Pod "pod-subpath-test-dynamicpv-dmtf": Phase="Pending", Reason="", readiness=false. Elapsed: 10.316931599s
Sep 26 07:33:39.354: INFO: Pod "pod-subpath-test-dynamicpv-dmtf": Phase="Pending", Reason="", readiness=false. Elapsed: 12.366762266s
Sep 26 07:33:41.404: INFO: Pod "pod-subpath-test-dynamicpv-dmtf": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.417170165s
STEP: Saw pod success
Sep 26 07:33:41.404: INFO: Pod "pod-subpath-test-dynamicpv-dmtf" satisfied condition "Succeeded or Failed"
Sep 26 07:33:41.454: INFO: Trying to get logs from node ip-172-20-35-50.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-dmtf container test-container-subpath-dynamicpv-dmtf: <nil>
STEP: delete the pod
Sep 26 07:33:41.570: INFO: Waiting for pod pod-subpath-test-dynamicpv-dmtf to disappear
Sep 26 07:33:41.625: INFO: Pod pod-subpath-test-dynamicpv-dmtf no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-dmtf
Sep 26 07:33:41.625: INFO: Deleting pod "pod-subpath-test-dynamicpv-dmtf" in namespace "provisioning-3620"
... skipping 320 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.h0A0b3MTk/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.h0A0b3MTk/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.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 378 lines ...
Sep 26 07:33:43.160: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9915xtqkh
STEP: creating a claim
Sep 26 07:33:43.214: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-xfsz
STEP: Creating a pod to test subpath
Sep 26 07:33:43.368: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-xfsz" in namespace "provisioning-9915" to be "Succeeded or Failed"
Sep 26 07:33:43.422: INFO: Pod "pod-subpath-test-dynamicpv-xfsz": Phase="Pending", Reason="", readiness=false. Elapsed: 53.07971ms
Sep 26 07:33:45.471: INFO: Pod "pod-subpath-test-dynamicpv-xfsz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.102713661s
Sep 26 07:33:47.521: INFO: Pod "pod-subpath-test-dynamicpv-xfsz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.152965819s
Sep 26 07:33:49.572: INFO: Pod "pod-subpath-test-dynamicpv-xfsz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.203790486s
Sep 26 07:33:51.623: INFO: Pod "pod-subpath-test-dynamicpv-xfsz": Phase="Pending", Reason="", readiness=false. Elapsed: 8.254199455s
Sep 26 07:33:53.677: INFO: Pod "pod-subpath-test-dynamicpv-xfsz": Phase="Pending", Reason="", readiness=false. Elapsed: 10.308918686s
... skipping 2 lines ...
Sep 26 07:33:59.827: INFO: Pod "pod-subpath-test-dynamicpv-xfsz": Phase="Pending", Reason="", readiness=false. Elapsed: 16.458439347s
Sep 26 07:34:01.876: INFO: Pod "pod-subpath-test-dynamicpv-xfsz": Phase="Pending", Reason="", readiness=false. Elapsed: 18.507957638s
Sep 26 07:34:03.926: INFO: Pod "pod-subpath-test-dynamicpv-xfsz": Phase="Pending", Reason="", readiness=false. Elapsed: 20.557826734s
Sep 26 07:34:05.976: INFO: Pod "pod-subpath-test-dynamicpv-xfsz": Phase="Pending", Reason="", readiness=false. Elapsed: 22.607794162s
Sep 26 07:34:08.028: INFO: Pod "pod-subpath-test-dynamicpv-xfsz": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.659000407s
STEP: Saw pod success
Sep 26 07:34:08.028: INFO: Pod "pod-subpath-test-dynamicpv-xfsz" satisfied condition "Succeeded or Failed"
Sep 26 07:34:08.081: INFO: Trying to get logs from node ip-172-20-35-50.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-xfsz container test-container-subpath-dynamicpv-xfsz: <nil>
STEP: delete the pod
Sep 26 07:34:08.188: INFO: Waiting for pod pod-subpath-test-dynamicpv-xfsz to disappear
Sep 26 07:34:08.237: INFO: Pod pod-subpath-test-dynamicpv-xfsz no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-xfsz
Sep 26 07:34:08.237: INFO: Deleting pod "pod-subpath-test-dynamicpv-xfsz" in namespace "provisioning-9915"
... skipping 401 lines ...
Sep 26 07:33:48.811: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6260-e2e-scxxzx2
STEP: creating a claim
Sep 26 07:33:48.862: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-gvl8
STEP: Creating a pod to test subpath
Sep 26 07:33:49.013: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-gvl8" in namespace "provisioning-6260" to be "Succeeded or Failed"
Sep 26 07:33:49.066: INFO: Pod "pod-subpath-test-dynamicpv-gvl8": Phase="Pending", Reason="", readiness=false. Elapsed: 53.371018ms
Sep 26 07:33:51.116: INFO: Pod "pod-subpath-test-dynamicpv-gvl8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.102824742s
Sep 26 07:33:53.172: INFO: Pod "pod-subpath-test-dynamicpv-gvl8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.158767387s
Sep 26 07:33:55.221: INFO: Pod "pod-subpath-test-dynamicpv-gvl8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.208385725s
Sep 26 07:33:57.271: INFO: Pod "pod-subpath-test-dynamicpv-gvl8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.258013897s
Sep 26 07:33:59.322: INFO: Pod "pod-subpath-test-dynamicpv-gvl8": Phase="Pending", Reason="", readiness=false. Elapsed: 10.309354263s
... skipping 3 lines ...
Sep 26 07:34:07.533: INFO: Pod "pod-subpath-test-dynamicpv-gvl8": Phase="Pending", Reason="", readiness=false. Elapsed: 18.519771155s
Sep 26 07:34:09.582: INFO: Pod "pod-subpath-test-dynamicpv-gvl8": Phase="Pending", Reason="", readiness=false. Elapsed: 20.569276539s
Sep 26 07:34:11.632: INFO: Pod "pod-subpath-test-dynamicpv-gvl8": Phase="Pending", Reason="", readiness=false. Elapsed: 22.618963379s
Sep 26 07:34:13.682: INFO: Pod "pod-subpath-test-dynamicpv-gvl8": Phase="Pending", Reason="", readiness=false. Elapsed: 24.669261476s
Sep 26 07:34:15.736: INFO: Pod "pod-subpath-test-dynamicpv-gvl8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.723015273s
STEP: Saw pod success
Sep 26 07:34:15.736: INFO: Pod "pod-subpath-test-dynamicpv-gvl8" satisfied condition "Succeeded or Failed"
Sep 26 07:34:15.797: INFO: Trying to get logs from node ip-172-20-37-99.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-gvl8 container test-container-volume-dynamicpv-gvl8: <nil>
STEP: delete the pod
Sep 26 07:34:15.903: INFO: Waiting for pod pod-subpath-test-dynamicpv-gvl8 to disappear
Sep 26 07:34:15.952: INFO: Pod pod-subpath-test-dynamicpv-gvl8 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-gvl8
Sep 26 07:34:15.953: INFO: Deleting pod "pod-subpath-test-dynamicpv-gvl8" in namespace "provisioning-6260"
... skipping 40 lines ...
Sep 26 07:34:28.050: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-7785jwdqk
STEP: creating a claim
Sep 26 07:34:28.100: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Sep 26 07:34:28.207: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Sep 26 07:34:28.315: INFO: Error updating pvc awsbtffs: PersistentVolumeClaim "awsbtffs" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-7785jwdqk",
  	... // 3 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Sep 26 07:34:58.522: INFO: Error updating pvc awsbtffs: PersistentVolumeClaim "awsbtffs" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 112 lines ...
Sep 26 07:34:34.199: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-7366-e2e-sc4x6bx
STEP: creating a claim
Sep 26 07:34:34.250: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Sep 26 07:34:34.351: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Sep 26 07:34:34.450: INFO: Error updating pvc ebs.csi.aws.comjxrmr: PersistentVolumeClaim "ebs.csi.aws.comjxrmr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-7366-e2e-sc4x6bx",
  	... // 3 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 4 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 26 07:34:58.791: 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.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Sep 26 07:34:59.045: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Sep 26 07:34:59.578: INFO: Successfully created a new PD: "aws://us-west-1a/vol-04e6ffabd0a10846e".
Sep 26 07:34:59.578: INFO: Creating resource for pre-provisioned PV
Sep 26 07:34:59.578: INFO: Creating PVC and PV
... skipping 9 lines ...
Sep 26 07:35:12.107: INFO: PersistentVolumeClaim pvc-gt2pf found but phase is Pending instead of Bound.
Sep 26 07:35:14.159: INFO: PersistentVolumeClaim pvc-gt2pf found but phase is Pending instead of Bound.
Sep 26 07:35:16.210: INFO: PersistentVolumeClaim pvc-gt2pf found and phase=Bound (16.467537211s)
Sep 26 07:35:16.210: INFO: Waiting up to 3m0s for PersistentVolume aws-xtwt9 to have phase Bound
Sep 26 07:35:16.261: INFO: PersistentVolume aws-xtwt9 found and phase=Bound (50.372096ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Sep 26 07:35:18.566: INFO: Deleting pod "pod-b2b7bf4c-dc0f-4e70-a290-871d056d21ea" in namespace "volumemode-1692"
Sep 26 07:35:18.619: INFO: Wait up to 5m0s for pod "pod-b2b7bf4c-dc0f-4e70-a290-871d056d21ea" to be fully deleted
STEP: Deleting pv and pvc
Sep 26 07:35:20.721: INFO: Deleting PersistentVolumeClaim "pvc-gt2pf"
Sep 26 07:35:20.772: INFO: Deleting PersistentVolume "aws-xtwt9"
Sep 26 07:35:21.043: INFO: Successfully deleted PD "aws://us-west-1a/vol-04e6ffabd0a10846e".
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.h0A0b3MTk/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.h0A0b3MTk/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
    /tmp/kops.h0A0b3MTk/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.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Sep 26 07:35:21.148: INFO: Driver "ebs.csi.aws.com" does not support volume type "PreprovisionedPV" - skipping
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
... skipping 17 lines ...
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 26 07:35:21.150: 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.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Sep 26 07:35:21.454: INFO: found topology map[topology.ebs.csi.aws.com/zone:us-west-1a]
Sep 26 07:35:21.454: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
[AfterEach] [Testpattern: Dynamic PV (delayed binding)] topology
... skipping 4 lines ...

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

    Not enough topologies in cluster -- skipping

    /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 11 lines ...
Sep 26 07:34:03.372: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2765-e2e-scgzsgl
STEP: creating a claim
Sep 26 07:34:03.427: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-q27n
STEP: Creating a pod to test atomic-volume-subpath
Sep 26 07:34:03.583: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-q27n" in namespace "provisioning-2765" to be "Succeeded or Failed"
Sep 26 07:34:03.633: INFO: Pod "pod-subpath-test-dynamicpv-q27n": Phase="Pending", Reason="", readiness=false. Elapsed: 50.23745ms
Sep 26 07:34:05.693: INFO: Pod "pod-subpath-test-dynamicpv-q27n": Phase="Pending", Reason="", readiness=false. Elapsed: 2.109848859s
Sep 26 07:34:07.744: INFO: Pod "pod-subpath-test-dynamicpv-q27n": Phase="Pending", Reason="", readiness=false. Elapsed: 4.16164592s
Sep 26 07:34:09.796: INFO: Pod "pod-subpath-test-dynamicpv-q27n": Phase="Pending", Reason="", readiness=false. Elapsed: 6.212819889s
Sep 26 07:34:11.846: INFO: Pod "pod-subpath-test-dynamicpv-q27n": Phase="Pending", Reason="", readiness=false. Elapsed: 8.263502787s
Sep 26 07:34:13.954: INFO: Pod "pod-subpath-test-dynamicpv-q27n": Phase="Pending", Reason="", readiness=false. Elapsed: 10.370661055s
... skipping 8 lines ...
Sep 26 07:34:32.456: INFO: Pod "pod-subpath-test-dynamicpv-q27n": Phase="Running", Reason="", readiness=true. Elapsed: 28.872816472s
Sep 26 07:34:34.510: INFO: Pod "pod-subpath-test-dynamicpv-q27n": Phase="Running", Reason="", readiness=true. Elapsed: 30.927253603s
Sep 26 07:34:36.562: INFO: Pod "pod-subpath-test-dynamicpv-q27n": Phase="Running", Reason="", readiness=true. Elapsed: 32.978829844s
Sep 26 07:34:38.614: INFO: Pod "pod-subpath-test-dynamicpv-q27n": Phase="Running", Reason="", readiness=true. Elapsed: 35.031097533s
Sep 26 07:34:40.667: INFO: Pod "pod-subpath-test-dynamicpv-q27n": Phase="Succeeded", Reason="", readiness=false. Elapsed: 37.084231878s
STEP: Saw pod success
Sep 26 07:34:40.667: INFO: Pod "pod-subpath-test-dynamicpv-q27n" satisfied condition "Succeeded or Failed"
Sep 26 07:34:40.719: INFO: Trying to get logs from node ip-172-20-54-151.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-q27n container test-container-subpath-dynamicpv-q27n: <nil>
STEP: delete the pod
Sep 26 07:34:40.837: INFO: Waiting for pod pod-subpath-test-dynamicpv-q27n to disappear
Sep 26 07:34:40.888: INFO: Pod pod-subpath-test-dynamicpv-q27n no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-q27n
Sep 26 07:34:40.888: INFO: Deleting pod "pod-subpath-test-dynamicpv-q27n" in namespace "provisioning-2765"
... skipping 40 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.h0A0b3MTk/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.h0A0b3MTk/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.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 11 lines ...
Sep 26 07:34:24.510: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4891-e2e-sckbg7z
STEP: creating a claim
Sep 26 07:34:24.562: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-zrlr
STEP: Creating a pod to test subpath
Sep 26 07:34:24.722: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-zrlr" in namespace "provisioning-4891" to be "Succeeded or Failed"
Sep 26 07:34:24.774: INFO: Pod "pod-subpath-test-dynamicpv-zrlr": Phase="Pending", Reason="", readiness=false. Elapsed: 51.389616ms
Sep 26 07:34:26.825: INFO: Pod "pod-subpath-test-dynamicpv-zrlr": Phase="Pending", Reason="", readiness=false. Elapsed: 2.10301733s
Sep 26 07:34:28.877: INFO: Pod "pod-subpath-test-dynamicpv-zrlr": Phase="Pending", Reason="", readiness=false. Elapsed: 4.154289747s
Sep 26 07:34:30.929: INFO: Pod "pod-subpath-test-dynamicpv-zrlr": Phase="Pending", Reason="", readiness=false. Elapsed: 6.206911253s
Sep 26 07:34:32.982: INFO: Pod "pod-subpath-test-dynamicpv-zrlr": Phase="Pending", Reason="", readiness=false. Elapsed: 8.260089303s
Sep 26 07:34:35.033: INFO: Pod "pod-subpath-test-dynamicpv-zrlr": Phase="Pending", Reason="", readiness=false. Elapsed: 10.310828581s
Sep 26 07:34:37.084: INFO: Pod "pod-subpath-test-dynamicpv-zrlr": Phase="Pending", Reason="", readiness=false. Elapsed: 12.36192224s
Sep 26 07:34:39.138: INFO: Pod "pod-subpath-test-dynamicpv-zrlr": Phase="Pending", Reason="", readiness=false. Elapsed: 14.41513571s
Sep 26 07:34:41.190: INFO: Pod "pod-subpath-test-dynamicpv-zrlr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.467165532s
STEP: Saw pod success
Sep 26 07:34:41.190: INFO: Pod "pod-subpath-test-dynamicpv-zrlr" satisfied condition "Succeeded or Failed"
Sep 26 07:34:41.241: INFO: Trying to get logs from node ip-172-20-54-151.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-zrlr container test-container-volume-dynamicpv-zrlr: <nil>
STEP: delete the pod
Sep 26 07:34:41.350: INFO: Waiting for pod pod-subpath-test-dynamicpv-zrlr to disappear
Sep 26 07:34:41.401: INFO: Pod pod-subpath-test-dynamicpv-zrlr no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-zrlr
Sep 26 07:34:41.401: INFO: Deleting pod "pod-subpath-test-dynamicpv-zrlr" in namespace "provisioning-4891"
... skipping 176 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 26 07:34:18.113: 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.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Sep 26 07:34:18.374: INFO: Creating resource for dynamic PV
Sep 26 07:34:18.374: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1040-e2e-sc96277
STEP: creating a claim
Sep 26 07:34:18.425: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-qlf8
STEP: Checking for subpath error in container status
Sep 26 07:34:42.695: INFO: Deleting pod "pod-subpath-test-dynamicpv-qlf8" in namespace "provisioning-1040"
Sep 26 07:34:42.749: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-qlf8" to be fully deleted
STEP: Deleting pod
Sep 26 07:34:44.851: INFO: Deleting pod "pod-subpath-test-dynamicpv-qlf8" in namespace "provisioning-1040"
STEP: Deleting pvc
Sep 26 07:34:45.002: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comjkgbj"
... skipping 21 lines ...

• [SLOW TEST:92.821 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.h0A0b3MTk/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.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 308 lines ...
STEP: Deleting pod hostexec-ip-172-20-35-50.us-west-1.compute.internal-97npm in namespace volumemode-7109
Sep 26 07:35:35.048: INFO: Deleting pod "pod-854adfd7-f857-4b36-ac95-0ccfd36e7006" in namespace "volumemode-7109"
Sep 26 07:35:35.098: INFO: Wait up to 5m0s for pod "pod-854adfd7-f857-4b36-ac95-0ccfd36e7006" to be fully deleted
STEP: Deleting pv and pvc
Sep 26 07:35:39.198: INFO: Deleting PersistentVolumeClaim "pvc-v86kg"
Sep 26 07:35:39.248: INFO: Deleting PersistentVolume "aws-wvpkg"
Sep 26 07:35:39.451: INFO: Couldn't delete PD "aws://us-west-1a/vol-02b4fef45dd490c72", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02b4fef45dd490c72 is currently attached to i-0c0aac37066181110
	status code: 400, request id: 9a287635-0b82-4b1e-91f8-3db6ded9ff12
Sep 26 07:35:44.825: INFO: Couldn't delete PD "aws://us-west-1a/vol-02b4fef45dd490c72", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02b4fef45dd490c72 is currently attached to i-0c0aac37066181110
	status code: 400, request id: d87949aa-b697-47b1-a963-60739ec2a674
Sep 26 07:35:50.170: INFO: Couldn't delete PD "aws://us-west-1a/vol-02b4fef45dd490c72", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02b4fef45dd490c72 is currently attached to i-0c0aac37066181110
	status code: 400, request id: 833c92aa-926f-490a-8874-f447b35b9f6c
Sep 26 07:35:55.540: INFO: Couldn't delete PD "aws://us-west-1a/vol-02b4fef45dd490c72", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02b4fef45dd490c72 is currently attached to i-0c0aac37066181110
	status code: 400, request id: e0c7d785-7628-4316-baba-98c611751d0a
Sep 26 07:36:00.914: INFO: Couldn't delete PD "aws://us-west-1a/vol-02b4fef45dd490c72", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02b4fef45dd490c72 is currently attached to i-0c0aac37066181110
	status code: 400, request id: 92e04822-cd0b-4863-a355-41b3018ceefa
Sep 26 07:36:06.300: INFO: Successfully deleted PD "aws://us-west-1a/vol-02b4fef45dd490c72".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 26 07:36:06.300: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-7109" for this suite.
... skipping 56 lines ...
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 26 07:36:06.409: 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.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Sep 26 07:36:06.705: INFO: found topology map[topology.ebs.csi.aws.com/zone:us-west-1a]
Sep 26 07:36:06.705: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
[AfterEach] [Testpattern: Dynamic PV (immediate binding)] topology
... skipping 4 lines ...

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

    Not enough topologies in cluster -- skipping

    /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 2 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 26 07:34:32.651: 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.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Sep 26 07:34:32.906: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Sep 26 07:34:32.906: INFO: Creating resource for dynamic PV
Sep 26 07:34:32.906: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5784db6p4
STEP: creating a claim
Sep 26 07:34:32.958: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-gbgn
STEP: Checking for subpath error in container status
Sep 26 07:35:49.219: INFO: Deleting pod "pod-subpath-test-dynamicpv-gbgn" in namespace "provisioning-5784"
Sep 26 07:35:49.270: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-gbgn" to be fully deleted
STEP: Deleting pod
Sep 26 07:35:51.373: INFO: Deleting pod "pod-subpath-test-dynamicpv-gbgn" in namespace "provisioning-5784"
STEP: Deleting pvc
Sep 26 07:35:51.536: INFO: Deleting PersistentVolumeClaim "aws9ffzq"
... skipping 13 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.h0A0b3MTk/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.h0A0b3MTk/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.h0A0b3MTk/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.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 361 lines ...
Sep 26 07:34:59.076: INFO: PersistentVolumeClaim pvc-zqj4j found but phase is Pending instead of Bound.
Sep 26 07:35:01.137: INFO: PersistentVolumeClaim pvc-zqj4j found and phase=Bound (8.26065233s)
Sep 26 07:35:01.137: INFO: Waiting up to 3m0s for PersistentVolume aws-b6qvq to have phase Bound
Sep 26 07:35:01.187: INFO: PersistentVolume aws-b6qvq found and phase=Bound (50.151818ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-qmd5
STEP: Creating a pod to test exec-volume-test
Sep 26 07:35:01.338: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-qmd5" in namespace "volume-2717" to be "Succeeded or Failed"
Sep 26 07:35:01.389: INFO: Pod "exec-volume-test-preprovisionedpv-qmd5": Phase="Pending", Reason="", readiness=false. Elapsed: 50.256128ms
Sep 26 07:35:03.440: INFO: Pod "exec-volume-test-preprovisionedpv-qmd5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.101918639s
Sep 26 07:35:05.490: INFO: Pod "exec-volume-test-preprovisionedpv-qmd5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.151767919s
Sep 26 07:35:07.540: INFO: Pod "exec-volume-test-preprovisionedpv-qmd5": Phase="Pending", Reason="", readiness=false. Elapsed: 6.201899289s
Sep 26 07:35:09.591: INFO: Pod "exec-volume-test-preprovisionedpv-qmd5": Phase="Pending", Reason="", readiness=false. Elapsed: 8.252538119s
Sep 26 07:35:11.641: INFO: Pod "exec-volume-test-preprovisionedpv-qmd5": Phase="Pending", Reason="", readiness=false. Elapsed: 10.302307299s
... skipping 23 lines ...
Sep 26 07:36:00.846: INFO: Pod "exec-volume-test-preprovisionedpv-qmd5": Phase="Pending", Reason="", readiness=false. Elapsed: 59.507911727s
Sep 26 07:36:02.897: INFO: Pod "exec-volume-test-preprovisionedpv-qmd5": Phase="Pending", Reason="", readiness=false. Elapsed: 1m1.558767957s
Sep 26 07:36:04.947: INFO: Pod "exec-volume-test-preprovisionedpv-qmd5": Phase="Pending", Reason="", readiness=false. Elapsed: 1m3.608314445s
Sep 26 07:36:06.997: INFO: Pod "exec-volume-test-preprovisionedpv-qmd5": Phase="Pending", Reason="", readiness=false. Elapsed: 1m5.658242868s
Sep 26 07:36:09.047: INFO: Pod "exec-volume-test-preprovisionedpv-qmd5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m7.708761248s
STEP: Saw pod success
Sep 26 07:36:09.047: INFO: Pod "exec-volume-test-preprovisionedpv-qmd5" satisfied condition "Succeeded or Failed"
Sep 26 07:36:09.097: INFO: Trying to get logs from node ip-172-20-37-99.us-west-1.compute.internal pod exec-volume-test-preprovisionedpv-qmd5 container exec-container-preprovisionedpv-qmd5: <nil>
STEP: delete the pod
Sep 26 07:36:09.213: INFO: Waiting for pod exec-volume-test-preprovisionedpv-qmd5 to disappear
Sep 26 07:36:09.272: INFO: Pod exec-volume-test-preprovisionedpv-qmd5 no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-qmd5
Sep 26 07:36:09.272: INFO: Deleting pod "exec-volume-test-preprovisionedpv-qmd5" in namespace "volume-2717"
STEP: Deleting pv and pvc
Sep 26 07:36:09.322: INFO: Deleting PersistentVolumeClaim "pvc-zqj4j"
Sep 26 07:36:09.373: INFO: Deleting PersistentVolume "aws-b6qvq"
Sep 26 07:36:09.787: INFO: Couldn't delete PD "aws://us-west-1a/vol-0e9ef2b271ed77263", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e9ef2b271ed77263 is currently attached to i-009d6e8a60bfe9013
	status code: 400, request id: 6c6fd284-9582-4c0b-98fd-d6332a9d8733
Sep 26 07:36:15.166: INFO: Successfully deleted PD "aws://us-west-1a/vol-0e9ef2b271ed77263".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 26 07:36:15.166: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-2717" for this suite.
... skipping 132 lines ...

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

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

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

    /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 315 lines ...
Sep 26 07:35:51.189: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5926-e2e-sctwsft
STEP: creating a claim
Sep 26 07:35:51.240: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-vxps
STEP: Creating a pod to test multi_subpath
Sep 26 07:35:51.403: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-vxps" in namespace "provisioning-5926" to be "Succeeded or Failed"
Sep 26 07:35:51.458: INFO: Pod "pod-subpath-test-dynamicpv-vxps": Phase="Pending", Reason="", readiness=false. Elapsed: 54.311059ms
Sep 26 07:35:53.509: INFO: Pod "pod-subpath-test-dynamicpv-vxps": Phase="Pending", Reason="", readiness=false. Elapsed: 2.105234914s
Sep 26 07:35:55.560: INFO: Pod "pod-subpath-test-dynamicpv-vxps": Phase="Pending", Reason="", readiness=false. Elapsed: 4.156758598s
Sep 26 07:35:57.612: INFO: Pod "pod-subpath-test-dynamicpv-vxps": Phase="Pending", Reason="", readiness=false. Elapsed: 6.208347234s
Sep 26 07:35:59.664: INFO: Pod "pod-subpath-test-dynamicpv-vxps": Phase="Pending", Reason="", readiness=false. Elapsed: 8.260836563s
Sep 26 07:36:01.717: INFO: Pod "pod-subpath-test-dynamicpv-vxps": Phase="Pending", Reason="", readiness=false. Elapsed: 10.313440871s
Sep 26 07:36:03.768: INFO: Pod "pod-subpath-test-dynamicpv-vxps": Phase="Pending", Reason="", readiness=false. Elapsed: 12.364861228s
Sep 26 07:36:05.835: INFO: Pod "pod-subpath-test-dynamicpv-vxps": Phase="Pending", Reason="", readiness=false. Elapsed: 14.431419907s
Sep 26 07:36:07.886: INFO: Pod "pod-subpath-test-dynamicpv-vxps": Phase="Pending", Reason="", readiness=false. Elapsed: 16.482376577s
Sep 26 07:36:09.937: INFO: Pod "pod-subpath-test-dynamicpv-vxps": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.533071276s
STEP: Saw pod success
Sep 26 07:36:09.937: INFO: Pod "pod-subpath-test-dynamicpv-vxps" satisfied condition "Succeeded or Failed"
Sep 26 07:36:09.987: INFO: Trying to get logs from node ip-172-20-54-151.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-vxps container test-container-subpath-dynamicpv-vxps: <nil>
STEP: delete the pod
Sep 26 07:36:10.101: INFO: Waiting for pod pod-subpath-test-dynamicpv-vxps to disappear
Sep 26 07:36:10.157: INFO: Pod pod-subpath-test-dynamicpv-vxps no longer exists
STEP: Deleting pod
Sep 26 07:36:10.157: INFO: Deleting pod "pod-subpath-test-dynamicpv-vxps" in namespace "provisioning-5926"
... skipping 213 lines ...
Sep 26 07:34:47.123: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2938bfrhm
STEP: creating a claim
Sep 26 07:34:47.174: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-d7fv
STEP: Creating a pod to test atomic-volume-subpath
Sep 26 07:34:47.331: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-d7fv" in namespace "provisioning-2938" to be "Succeeded or Failed"
Sep 26 07:34:47.381: INFO: Pod "pod-subpath-test-dynamicpv-d7fv": Phase="Pending", Reason="", readiness=false. Elapsed: 49.36532ms
Sep 26 07:34:49.430: INFO: Pod "pod-subpath-test-dynamicpv-d7fv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.098667081s
Sep 26 07:34:51.480: INFO: Pod "pod-subpath-test-dynamicpv-d7fv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.149051014s
Sep 26 07:34:53.530: INFO: Pod "pod-subpath-test-dynamicpv-d7fv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.199263275s
Sep 26 07:34:55.582: INFO: Pod "pod-subpath-test-dynamicpv-d7fv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.25034308s
Sep 26 07:34:57.633: INFO: Pod "pod-subpath-test-dynamicpv-d7fv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.301899864s
... skipping 36 lines ...
Sep 26 07:36:13.498: INFO: Pod "pod-subpath-test-dynamicpv-d7fv": Phase="Running", Reason="", readiness=true. Elapsed: 1m26.166847438s
Sep 26 07:36:15.548: INFO: Pod "pod-subpath-test-dynamicpv-d7fv": Phase="Running", Reason="", readiness=true. Elapsed: 1m28.217002715s
Sep 26 07:36:17.599: INFO: Pod "pod-subpath-test-dynamicpv-d7fv": Phase="Running", Reason="", readiness=true. Elapsed: 1m30.26767081s
Sep 26 07:36:19.651: INFO: Pod "pod-subpath-test-dynamicpv-d7fv": Phase="Running", Reason="", readiness=true. Elapsed: 1m32.319857689s
Sep 26 07:36:21.708: INFO: Pod "pod-subpath-test-dynamicpv-d7fv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m34.376856771s
STEP: Saw pod success
Sep 26 07:36:21.708: INFO: Pod "pod-subpath-test-dynamicpv-d7fv" satisfied condition "Succeeded or Failed"
Sep 26 07:36:21.763: INFO: Trying to get logs from node ip-172-20-54-151.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-d7fv container test-container-subpath-dynamicpv-d7fv: <nil>
STEP: delete the pod
Sep 26 07:36:21.887: INFO: Waiting for pod pod-subpath-test-dynamicpv-d7fv to disappear
Sep 26 07:36:21.936: INFO: Pod pod-subpath-test-dynamicpv-d7fv no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-d7fv
Sep 26 07:36:21.936: INFO: Deleting pod "pod-subpath-test-dynamicpv-d7fv" in namespace "provisioning-2938"
... skipping 373 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.h0A0b3MTk/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.h0A0b3MTk/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.h0A0b3MTk/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.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 174 lines ...
Sep 26 07:36:07.104: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-9728trcpp
STEP: creating a claim
Sep 26 07:36:07.156: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-d5xw
STEP: Creating a pod to test exec-volume-test
Sep 26 07:36:07.305: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-d5xw" in namespace "volume-9728" to be "Succeeded or Failed"
Sep 26 07:36:07.354: INFO: Pod "exec-volume-test-dynamicpv-d5xw": Phase="Pending", Reason="", readiness=false. Elapsed: 49.000629ms
Sep 26 07:36:09.404: INFO: Pod "exec-volume-test-dynamicpv-d5xw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.098791338s
Sep 26 07:36:11.457: INFO: Pod "exec-volume-test-dynamicpv-d5xw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.151331138s
Sep 26 07:36:13.507: INFO: Pod "exec-volume-test-dynamicpv-d5xw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.201670907s
Sep 26 07:36:15.557: INFO: Pod "exec-volume-test-dynamicpv-d5xw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.251969106s
Sep 26 07:36:17.607: INFO: Pod "exec-volume-test-dynamicpv-d5xw": Phase="Pending", Reason="", readiness=false. Elapsed: 10.301545972s
Sep 26 07:36:19.657: INFO: Pod "exec-volume-test-dynamicpv-d5xw": Phase="Pending", Reason="", readiness=false. Elapsed: 12.351297817s
Sep 26 07:36:21.708: INFO: Pod "exec-volume-test-dynamicpv-d5xw": Phase="Pending", Reason="", readiness=false. Elapsed: 14.402984024s
Sep 26 07:36:23.759: INFO: Pod "exec-volume-test-dynamicpv-d5xw": Phase="Pending", Reason="", readiness=false. Elapsed: 16.453467876s
Sep 26 07:36:25.810: INFO: Pod "exec-volume-test-dynamicpv-d5xw": Phase="Pending", Reason="", readiness=false. Elapsed: 18.504436649s
Sep 26 07:36:27.860: INFO: Pod "exec-volume-test-dynamicpv-d5xw": Phase="Pending", Reason="", readiness=false. Elapsed: 20.554267351s
Sep 26 07:36:29.909: INFO: Pod "exec-volume-test-dynamicpv-d5xw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.604086802s
STEP: Saw pod success
Sep 26 07:36:29.909: INFO: Pod "exec-volume-test-dynamicpv-d5xw" satisfied condition "Succeeded or Failed"
Sep 26 07:36:29.959: INFO: Trying to get logs from node ip-172-20-37-99.us-west-1.compute.internal pod exec-volume-test-dynamicpv-d5xw container exec-container-dynamicpv-d5xw: <nil>
STEP: delete the pod
Sep 26 07:36:30.087: INFO: Waiting for pod exec-volume-test-dynamicpv-d5xw to disappear
Sep 26 07:36:30.146: INFO: Pod exec-volume-test-dynamicpv-d5xw no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-d5xw
Sep 26 07:36:30.146: INFO: Deleting pod "exec-volume-test-dynamicpv-d5xw" in namespace "volume-9728"
... skipping 377 lines ...
Sep 26 07:36:28.376: INFO: PersistentVolumeClaim pvc-hxj46 found but phase is Pending instead of Bound.
Sep 26 07:36:30.428: INFO: PersistentVolumeClaim pvc-hxj46 found and phase=Bound (14.410210869s)
Sep 26 07:36:30.428: INFO: Waiting up to 3m0s for PersistentVolume aws-h2m92 to have phase Bound
Sep 26 07:36:30.478: INFO: PersistentVolume aws-h2m92 found and phase=Bound (49.759958ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-xsxw
STEP: Creating a pod to test exec-volume-test
Sep 26 07:36:30.628: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-xsxw" in namespace "volume-4600" to be "Succeeded or Failed"
Sep 26 07:36:30.679: INFO: Pod "exec-volume-test-preprovisionedpv-xsxw": Phase="Pending", Reason="", readiness=false. Elapsed: 51.466684ms
Sep 26 07:36:32.733: INFO: Pod "exec-volume-test-preprovisionedpv-xsxw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.105342362s
Sep 26 07:36:34.784: INFO: Pod "exec-volume-test-preprovisionedpv-xsxw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.156055974s
Sep 26 07:36:36.835: INFO: Pod "exec-volume-test-preprovisionedpv-xsxw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.206687747s
Sep 26 07:36:38.884: INFO: Pod "exec-volume-test-preprovisionedpv-xsxw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.256525213s
Sep 26 07:36:40.935: INFO: Pod "exec-volume-test-preprovisionedpv-xsxw": Phase="Pending", Reason="", readiness=false. Elapsed: 10.306705549s
Sep 26 07:36:42.984: INFO: Pod "exec-volume-test-preprovisionedpv-xsxw": Phase="Pending", Reason="", readiness=false. Elapsed: 12.356527225s
Sep 26 07:36:45.034: INFO: Pod "exec-volume-test-preprovisionedpv-xsxw": Phase="Pending", Reason="", readiness=false. Elapsed: 14.406235681s
Sep 26 07:36:47.084: INFO: Pod "exec-volume-test-preprovisionedpv-xsxw": Phase="Pending", Reason="", readiness=false. Elapsed: 16.456514401s
Sep 26 07:36:49.136: INFO: Pod "exec-volume-test-preprovisionedpv-xsxw": Phase="Pending", Reason="", readiness=false. Elapsed: 18.508170484s
Sep 26 07:36:51.186: INFO: Pod "exec-volume-test-preprovisionedpv-xsxw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.557841896s
STEP: Saw pod success
Sep 26 07:36:51.186: INFO: Pod "exec-volume-test-preprovisionedpv-xsxw" satisfied condition "Succeeded or Failed"
Sep 26 07:36:51.235: INFO: Trying to get logs from node ip-172-20-37-99.us-west-1.compute.internal pod exec-volume-test-preprovisionedpv-xsxw container exec-container-preprovisionedpv-xsxw: <nil>
STEP: delete the pod
Sep 26 07:36:51.348: INFO: Waiting for pod exec-volume-test-preprovisionedpv-xsxw to disappear
Sep 26 07:36:51.397: INFO: Pod exec-volume-test-preprovisionedpv-xsxw no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-xsxw
Sep 26 07:36:51.397: INFO: Deleting pod "exec-volume-test-preprovisionedpv-xsxw" in namespace "volume-4600"
STEP: Deleting pv and pvc
Sep 26 07:36:51.447: INFO: Deleting PersistentVolumeClaim "pvc-hxj46"
Sep 26 07:36:51.500: INFO: Deleting PersistentVolume "aws-h2m92"
Sep 26 07:36:51.709: INFO: Couldn't delete PD "aws://us-west-1a/vol-0dcbad499787b9f3a", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0dcbad499787b9f3a is currently attached to i-009d6e8a60bfe9013
	status code: 400, request id: 7d2e9df5-aae5-44f2-83ed-194adc06e5c6
Sep 26 07:36:57.087: INFO: Couldn't delete PD "aws://us-west-1a/vol-0dcbad499787b9f3a", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0dcbad499787b9f3a is currently attached to i-009d6e8a60bfe9013
	status code: 400, request id: 2f54ccf5-996d-41cc-9757-e6f51c27c44d
Sep 26 07:37:02.457: INFO: Couldn't delete PD "aws://us-west-1a/vol-0dcbad499787b9f3a", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0dcbad499787b9f3a is currently attached to i-009d6e8a60bfe9013
	status code: 400, request id: 5208b9aa-f7cf-4bd7-a8dd-6bd937e4870b
Sep 26 07:37:07.810: INFO: Successfully deleted PD "aws://us-west-1a/vol-0dcbad499787b9f3a".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 26 07:37:07.810: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-4600" for this suite.
... skipping 263 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.h0A0b3MTk/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.h0A0b3MTk/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.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 281 lines ...
Sep 26 07:36:56.785: INFO: Pod aws-client still exists
Sep 26 07:36:58.785: INFO: Waiting for pod aws-client to disappear
Sep 26 07:36:58.836: INFO: Pod aws-client still exists
Sep 26 07:37:00.787: INFO: Waiting for pod aws-client to disappear
Sep 26 07:37:00.836: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Sep 26 07:37:01.005: INFO: Couldn't delete PD "aws://us-west-1a/vol-0a6df2e37c80927c3", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a6df2e37c80927c3 is currently attached to i-087195b8b11f3270f
	status code: 400, request id: ea993e1b-8105-4106-8ac9-ffd4125038c1
Sep 26 07:37:06.415: INFO: Couldn't delete PD "aws://us-west-1a/vol-0a6df2e37c80927c3", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a6df2e37c80927c3 is currently attached to i-087195b8b11f3270f
	status code: 400, request id: 263386d9-b7a2-4ba5-aebc-15e46985a559
Sep 26 07:37:11.789: INFO: Couldn't delete PD "aws://us-west-1a/vol-0a6df2e37c80927c3", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a6df2e37c80927c3 is currently attached to i-087195b8b11f3270f
	status code: 400, request id: 34d148cf-4021-41b1-b191-54558299099b
Sep 26 07:37:17.177: INFO: Successfully deleted PD "aws://us-west-1a/vol-0a6df2e37c80927c3".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 26 07:37:17.177: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-1345" for this suite.
... skipping 24 lines ...
Sep 26 07:36:25.263: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8338pz7j9
STEP: creating a claim
Sep 26 07:36:25.314: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-lc8v
STEP: Creating a pod to test subpath
Sep 26 07:36:25.471: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-lc8v" in namespace "provisioning-8338" to be "Succeeded or Failed"
Sep 26 07:36:25.526: INFO: Pod "pod-subpath-test-dynamicpv-lc8v": Phase="Pending", Reason="", readiness=false. Elapsed: 54.714276ms
Sep 26 07:36:27.579: INFO: Pod "pod-subpath-test-dynamicpv-lc8v": Phase="Pending", Reason="", readiness=false. Elapsed: 2.107824801s
Sep 26 07:36:29.632: INFO: Pod "pod-subpath-test-dynamicpv-lc8v": Phase="Pending", Reason="", readiness=false. Elapsed: 4.160323452s
Sep 26 07:36:31.684: INFO: Pod "pod-subpath-test-dynamicpv-lc8v": Phase="Pending", Reason="", readiness=false. Elapsed: 6.212321486s
Sep 26 07:36:33.736: INFO: Pod "pod-subpath-test-dynamicpv-lc8v": Phase="Pending", Reason="", readiness=false. Elapsed: 8.26455898s
Sep 26 07:36:35.788: INFO: Pod "pod-subpath-test-dynamicpv-lc8v": Phase="Pending", Reason="", readiness=false. Elapsed: 10.316560766s
... skipping 10 lines ...
Sep 26 07:36:58.376: INFO: Pod "pod-subpath-test-dynamicpv-lc8v": Phase="Pending", Reason="", readiness=false. Elapsed: 32.9049126s
Sep 26 07:37:00.427: INFO: Pod "pod-subpath-test-dynamicpv-lc8v": Phase="Pending", Reason="", readiness=false. Elapsed: 34.95604321s
Sep 26 07:37:02.478: INFO: Pod "pod-subpath-test-dynamicpv-lc8v": Phase="Pending", Reason="", readiness=false. Elapsed: 37.00657541s
Sep 26 07:37:04.530: INFO: Pod "pod-subpath-test-dynamicpv-lc8v": Phase="Pending", Reason="", readiness=false. Elapsed: 39.058690165s
Sep 26 07:37:06.582: INFO: Pod "pod-subpath-test-dynamicpv-lc8v": Phase="Succeeded", Reason="", readiness=false. Elapsed: 41.110322705s
STEP: Saw pod success
Sep 26 07:37:06.582: INFO: Pod "pod-subpath-test-dynamicpv-lc8v" satisfied condition "Succeeded or Failed"
Sep 26 07:37:06.632: INFO: Trying to get logs from node ip-172-20-37-99.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-lc8v container test-container-volume-dynamicpv-lc8v: <nil>
STEP: delete the pod
Sep 26 07:37:06.741: INFO: Waiting for pod pod-subpath-test-dynamicpv-lc8v to disappear
Sep 26 07:37:06.961: INFO: Pod pod-subpath-test-dynamicpv-lc8v no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-lc8v
Sep 26 07:37:06.962: INFO: Deleting pod "pod-subpath-test-dynamicpv-lc8v" in namespace "provisioning-8338"
... skipping 107 lines ...

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

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

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

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

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

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 211 lines ...
Sep 26 07:37:17.718: INFO: Pod aws-client still exists
Sep 26 07:37:19.667: INFO: Waiting for pod aws-client to disappear
Sep 26 07:37:19.718: INFO: Pod aws-client still exists
Sep 26 07:37:21.667: INFO: Waiting for pod aws-client to disappear
Sep 26 07:37:21.718: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Sep 26 07:37:22.133: INFO: Couldn't delete PD "aws://us-west-1a/vol-01232327507c235b5", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01232327507c235b5 is currently attached to i-0c0aac37066181110
	status code: 400, request id: 46be2f5e-42f5-47fc-a146-8240578434b7
Sep 26 07:37:27.468: INFO: Couldn't delete PD "aws://us-west-1a/vol-01232327507c235b5", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01232327507c235b5 is currently attached to i-0c0aac37066181110
	status code: 400, request id: 08eac319-c948-4dd9-99ef-7d9fb5eb1ad5
Sep 26 07:37:32.835: INFO: Successfully deleted PD "aws://us-west-1a/vol-01232327507c235b5".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 26 07:37:32.835: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-3483" for this suite.
... skipping 314 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 26 07:37:07.751: 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.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Sep 26 07:37:08.018: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Sep 26 07:37:08.018: INFO: Creating resource for dynamic PV
Sep 26 07:37:08.018: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4350qmjqm
STEP: creating a claim
Sep 26 07:37:08.070: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-jxkn
STEP: Checking for subpath error in container status
Sep 26 07:37:24.337: INFO: Deleting pod "pod-subpath-test-dynamicpv-jxkn" in namespace "provisioning-4350"
Sep 26 07:37:24.389: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-jxkn" to be fully deleted
STEP: Deleting pod
Sep 26 07:37:26.503: INFO: Deleting pod "pod-subpath-test-dynamicpv-jxkn" in namespace "provisioning-4350"
STEP: Deleting pvc
Sep 26 07:37:26.660: INFO: Deleting PersistentVolumeClaim "awskp2dq"
... skipping 15 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.h0A0b3MTk/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.h0A0b3MTk/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath directory is outside the volume [Slow][LinuxOnly]
      /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (ntfs)][Feature:Windows] volumes
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Sep 26 07:37:52.196: INFO: Driver "ebs.csi.aws.com" does not support volume type "PreprovisionedPV" - skipping
[AfterEach] [Testpattern: Pre-provisioned PV (ntfs)][Feature:Windows] volumes
... skipping 74 lines ...
Sep 26 07:37:04.092: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-888-e2e-schjvl9
STEP: creating a claim
Sep 26 07:37:04.143: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-v89q
STEP: Creating a pod to test subpath
Sep 26 07:37:04.307: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-v89q" in namespace "provisioning-888" to be "Succeeded or Failed"
Sep 26 07:37:04.364: INFO: Pod "pod-subpath-test-dynamicpv-v89q": Phase="Pending", Reason="", readiness=false. Elapsed: 56.898484ms
Sep 26 07:37:06.424: INFO: Pod "pod-subpath-test-dynamicpv-v89q": Phase="Pending", Reason="", readiness=false. Elapsed: 2.116668586s
Sep 26 07:37:08.475: INFO: Pod "pod-subpath-test-dynamicpv-v89q": Phase="Pending", Reason="", readiness=false. Elapsed: 4.167774422s
Sep 26 07:37:10.525: INFO: Pod "pod-subpath-test-dynamicpv-v89q": Phase="Pending", Reason="", readiness=false. Elapsed: 6.21861769s
Sep 26 07:37:12.578: INFO: Pod "pod-subpath-test-dynamicpv-v89q": Phase="Pending", Reason="", readiness=false. Elapsed: 8.270932757s
Sep 26 07:37:14.630: INFO: Pod "pod-subpath-test-dynamicpv-v89q": Phase="Pending", Reason="", readiness=false. Elapsed: 10.323453411s
Sep 26 07:37:16.682: INFO: Pod "pod-subpath-test-dynamicpv-v89q": Phase="Pending", Reason="", readiness=false. Elapsed: 12.375170557s
Sep 26 07:37:18.733: INFO: Pod "pod-subpath-test-dynamicpv-v89q": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.426160928s
STEP: Saw pod success
Sep 26 07:37:18.733: INFO: Pod "pod-subpath-test-dynamicpv-v89q" satisfied condition "Succeeded or Failed"
Sep 26 07:37:18.783: INFO: Trying to get logs from node ip-172-20-37-99.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-v89q container test-container-subpath-dynamicpv-v89q: <nil>
STEP: delete the pod
Sep 26 07:37:18.896: INFO: Waiting for pod pod-subpath-test-dynamicpv-v89q to disappear
Sep 26 07:37:18.947: INFO: Pod pod-subpath-test-dynamicpv-v89q no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-v89q
Sep 26 07:37:18.947: INFO: Deleting pod "pod-subpath-test-dynamicpv-v89q" in namespace "provisioning-888"
... skipping 34 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.h0A0b3MTk/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.h0A0b3MTk/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.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 340 lines ...
Sep 26 07:37:48.838: INFO: Waiting for pod aws-client to disappear
Sep 26 07:37:48.887: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Sep 26 07:37:48.888: INFO: Deleting PersistentVolumeClaim "pvc-nf5p5"
Sep 26 07:37:48.939: INFO: Deleting PersistentVolume "aws-ngld8"
Sep 26 07:37:49.171: INFO: Couldn't delete PD "aws://us-west-1a/vol-043fe0fc7aa82eef5", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-043fe0fc7aa82eef5 is currently attached to i-009d6e8a60bfe9013
	status code: 400, request id: 559b6e7b-2ea3-4f17-806f-d3e01f3c46c7
Sep 26 07:37:54.519: INFO: Couldn't delete PD "aws://us-west-1a/vol-043fe0fc7aa82eef5", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-043fe0fc7aa82eef5 is currently attached to i-009d6e8a60bfe9013
	status code: 400, request id: 8242125a-5e92-47bc-882b-adee9d5a2d65
Sep 26 07:37:59.914: INFO: Couldn't delete PD "aws://us-west-1a/vol-043fe0fc7aa82eef5", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-043fe0fc7aa82eef5 is currently attached to i-009d6e8a60bfe9013
	status code: 400, request id: a1ca6b51-8c2c-403b-9d81-d9dec73409b1
Sep 26 07:38:05.294: INFO: Successfully deleted PD "aws://us-west-1a/vol-043fe0fc7aa82eef5".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumes
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 26 07:38:05.294: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-3152" for this suite.
... skipping 199 lines ...
Sep 26 07:36:54.783: INFO: Creating resource for dynamic PV
Sep 26 07:36:54.783: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2868kml6g
STEP: creating a claim
Sep 26 07:36:54.833: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-2868
Sep 26 07:36:54.991: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-2868" in namespace "provisioning-2868" to be "Succeeded or Failed"
Sep 26 07:36:55.041: INFO: Pod "volume-prep-provisioning-2868": Phase="Pending", Reason="", readiness=false. Elapsed: 50.407127ms
Sep 26 07:36:57.092: INFO: Pod "volume-prep-provisioning-2868": Phase="Pending", Reason="", readiness=false. Elapsed: 2.101506648s
Sep 26 07:36:59.144: INFO: Pod "volume-prep-provisioning-2868": Phase="Pending", Reason="", readiness=false. Elapsed: 4.153446517s
Sep 26 07:37:01.195: INFO: Pod "volume-prep-provisioning-2868": Phase="Pending", Reason="", readiness=false. Elapsed: 6.204133386s
Sep 26 07:37:03.246: INFO: Pod "volume-prep-provisioning-2868": Phase="Pending", Reason="", readiness=false. Elapsed: 8.255541676s
Sep 26 07:37:05.297: INFO: Pod "volume-prep-provisioning-2868": Phase="Pending", Reason="", readiness=false. Elapsed: 10.306396671s
Sep 26 07:37:07.348: INFO: Pod "volume-prep-provisioning-2868": Phase="Pending", Reason="", readiness=false. Elapsed: 12.357146619s
Sep 26 07:37:09.399: INFO: Pod "volume-prep-provisioning-2868": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.408101953s
STEP: Saw pod success
Sep 26 07:37:09.399: INFO: Pod "volume-prep-provisioning-2868" satisfied condition "Succeeded or Failed"
Sep 26 07:37:09.399: INFO: Deleting pod "volume-prep-provisioning-2868" in namespace "provisioning-2868"
Sep 26 07:37:09.455: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-2868" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-v6mr
STEP: Checking for subpath error in container status
Sep 26 07:37:45.664: INFO: Deleting pod "pod-subpath-test-dynamicpv-v6mr" in namespace "provisioning-2868"
Sep 26 07:37:45.725: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-v6mr" to be fully deleted
STEP: Deleting pod
Sep 26 07:37:45.775: INFO: Deleting pod "pod-subpath-test-dynamicpv-v6mr" in namespace "provisioning-2868"
STEP: Deleting pvc
Sep 26 07:37:45.926: INFO: Deleting PersistentVolumeClaim "awsrsjz8"
... skipping 156 lines ...
Sep 26 07:37:28.239: INFO: PersistentVolumeClaim pvc-z4fsg found but phase is Pending instead of Bound.
Sep 26 07:37:30.290: INFO: PersistentVolumeClaim pvc-z4fsg found and phase=Bound (4.153635213s)
Sep 26 07:37:30.290: INFO: Waiting up to 3m0s for PersistentVolume aws-8w4sw to have phase Bound
Sep 26 07:37:30.348: INFO: PersistentVolume aws-8w4sw found and phase=Bound (57.703231ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-x2rs
STEP: Creating a pod to test exec-volume-test
Sep 26 07:37:30.499: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-x2rs" in namespace "volume-3874" to be "Succeeded or Failed"
Sep 26 07:37:30.549: INFO: Pod "exec-volume-test-preprovisionedpv-x2rs": Phase="Pending", Reason="", readiness=false. Elapsed: 49.419881ms
Sep 26 07:37:32.599: INFO: Pod "exec-volume-test-preprovisionedpv-x2rs": Phase="Pending", Reason="", readiness=false. Elapsed: 2.099249267s
Sep 26 07:37:34.648: INFO: Pod "exec-volume-test-preprovisionedpv-x2rs": Phase="Pending", Reason="", readiness=false. Elapsed: 4.148721997s
Sep 26 07:37:36.698: INFO: Pod "exec-volume-test-preprovisionedpv-x2rs": Phase="Pending", Reason="", readiness=false. Elapsed: 6.198195931s
Sep 26 07:37:38.749: INFO: Pod "exec-volume-test-preprovisionedpv-x2rs": Phase="Pending", Reason="", readiness=false. Elapsed: 8.249551266s
Sep 26 07:37:40.799: INFO: Pod "exec-volume-test-preprovisionedpv-x2rs": Phase="Pending", Reason="", readiness=false. Elapsed: 10.299234873s
Sep 26 07:37:42.849: INFO: Pod "exec-volume-test-preprovisionedpv-x2rs": Phase="Pending", Reason="", readiness=false. Elapsed: 12.34912002s
Sep 26 07:37:44.900: INFO: Pod "exec-volume-test-preprovisionedpv-x2rs": Phase="Pending", Reason="", readiness=false. Elapsed: 14.400549534s
Sep 26 07:37:46.950: INFO: Pod "exec-volume-test-preprovisionedpv-x2rs": Phase="Pending", Reason="", readiness=false. Elapsed: 16.450336596s
Sep 26 07:37:48.999: INFO: Pod "exec-volume-test-preprovisionedpv-x2rs": Phase="Pending", Reason="", readiness=false. Elapsed: 18.49987409s
Sep 26 07:37:51.050: INFO: Pod "exec-volume-test-preprovisionedpv-x2rs": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.550551419s
STEP: Saw pod success
Sep 26 07:37:51.050: INFO: Pod "exec-volume-test-preprovisionedpv-x2rs" satisfied condition "Succeeded or Failed"
Sep 26 07:37:51.101: INFO: Trying to get logs from node ip-172-20-37-99.us-west-1.compute.internal pod exec-volume-test-preprovisionedpv-x2rs container exec-container-preprovisionedpv-x2rs: <nil>
STEP: delete the pod
Sep 26 07:37:51.441: INFO: Waiting for pod exec-volume-test-preprovisionedpv-x2rs to disappear
Sep 26 07:37:51.490: INFO: Pod exec-volume-test-preprovisionedpv-x2rs no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-x2rs
Sep 26 07:37:51.490: INFO: Deleting pod "exec-volume-test-preprovisionedpv-x2rs" in namespace "volume-3874"
STEP: Deleting pv and pvc
Sep 26 07:37:51.539: INFO: Deleting PersistentVolumeClaim "pvc-z4fsg"
Sep 26 07:37:51.589: INFO: Deleting PersistentVolume "aws-8w4sw"
Sep 26 07:37:51.784: INFO: Couldn't delete PD "aws://us-west-1a/vol-0288706e47e68a91d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0288706e47e68a91d is currently attached to i-009d6e8a60bfe9013
	status code: 400, request id: 585da373-b76a-4b08-8d62-245a7254e13c
Sep 26 07:37:57.117: INFO: Couldn't delete PD "aws://us-west-1a/vol-0288706e47e68a91d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0288706e47e68a91d is currently attached to i-009d6e8a60bfe9013
	status code: 400, request id: 46640c37-5724-496c-b5bf-02be3b70995b
Sep 26 07:38:02.510: INFO: Couldn't delete PD "aws://us-west-1a/vol-0288706e47e68a91d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0288706e47e68a91d is currently attached to i-009d6e8a60bfe9013
	status code: 400, request id: 42c76bc2-0eab-40da-87f7-563d6e2870ce
Sep 26 07:38:07.811: INFO: Couldn't delete PD "aws://us-west-1a/vol-0288706e47e68a91d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0288706e47e68a91d is currently attached to i-009d6e8a60bfe9013
	status code: 400, request id: 406169a4-b4fb-453e-b8d9-00ddede6f0e6
Sep 26 07:38:13.176: INFO: Successfully deleted PD "aws://us-west-1a/vol-0288706e47e68a91d".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 26 07:38:13.176: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-3874" for this suite.
... skipping 296 lines ...
Sep 26 07:37:59.604: INFO: Waiting for pod aws-client to disappear
Sep 26 07:37:59.656: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Sep 26 07:37:59.656: INFO: Deleting PersistentVolumeClaim "pvc-cc264"
Sep 26 07:37:59.708: INFO: Deleting PersistentVolume "aws-z525q"
Sep 26 07:37:59.959: INFO: Couldn't delete PD "aws://us-west-1a/vol-0232f556fb2cd722e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0232f556fb2cd722e is currently attached to i-087195b8b11f3270f
	status code: 400, request id: 3f04f353-f105-47ce-a794-3d15620533b6
Sep 26 07:38:05.489: INFO: Couldn't delete PD "aws://us-west-1a/vol-0232f556fb2cd722e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0232f556fb2cd722e is currently attached to i-087195b8b11f3270f
	status code: 400, request id: b2330f9a-a205-4665-8f48-8a714c006538
Sep 26 07:38:10.844: INFO: Couldn't delete PD "aws://us-west-1a/vol-0232f556fb2cd722e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0232f556fb2cd722e is currently attached to i-087195b8b11f3270f
	status code: 400, request id: 11834c19-3a5c-4656-bbeb-5d6d85d02521
Sep 26 07:38:16.202: INFO: Successfully deleted PD "aws://us-west-1a/vol-0232f556fb2cd722e".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 26 07:38:16.202: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-6861" for this suite.
... skipping 24 lines ...
Sep 26 07:37:26.796: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-2168j7ql7
STEP: creating a claim
Sep 26 07:37:26.847: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-hz2m
STEP: Creating a pod to test exec-volume-test
Sep 26 07:37:27.000: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-hz2m" in namespace "volume-2168" to be "Succeeded or Failed"
Sep 26 07:37:27.051: INFO: Pod "exec-volume-test-dynamicpv-hz2m": Phase="Pending", Reason="", readiness=false. Elapsed: 51.294939ms
Sep 26 07:37:29.102: INFO: Pod "exec-volume-test-dynamicpv-hz2m": Phase="Pending", Reason="", readiness=false. Elapsed: 2.102190308s
Sep 26 07:37:31.158: INFO: Pod "exec-volume-test-dynamicpv-hz2m": Phase="Pending", Reason="", readiness=false. Elapsed: 4.158449948s
Sep 26 07:37:33.210: INFO: Pod "exec-volume-test-dynamicpv-hz2m": Phase="Pending", Reason="", readiness=false. Elapsed: 6.210629988s
Sep 26 07:37:35.262: INFO: Pod "exec-volume-test-dynamicpv-hz2m": Phase="Pending", Reason="", readiness=false. Elapsed: 8.262311979s
Sep 26 07:37:37.313: INFO: Pod "exec-volume-test-dynamicpv-hz2m": Phase="Pending", Reason="", readiness=false. Elapsed: 10.313168802s
Sep 26 07:37:39.365: INFO: Pod "exec-volume-test-dynamicpv-hz2m": Phase="Pending", Reason="", readiness=false. Elapsed: 12.365679607s
Sep 26 07:37:41.416: INFO: Pod "exec-volume-test-dynamicpv-hz2m": Phase="Pending", Reason="", readiness=false. Elapsed: 14.416750251s
Sep 26 07:37:43.468: INFO: Pod "exec-volume-test-dynamicpv-hz2m": Phase="Pending", Reason="", readiness=false. Elapsed: 16.468074973s
Sep 26 07:37:45.519: INFO: Pod "exec-volume-test-dynamicpv-hz2m": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.519620459s
STEP: Saw pod success
Sep 26 07:37:45.519: INFO: Pod "exec-volume-test-dynamicpv-hz2m" satisfied condition "Succeeded or Failed"
Sep 26 07:37:45.570: INFO: Trying to get logs from node ip-172-20-54-151.us-west-1.compute.internal pod exec-volume-test-dynamicpv-hz2m container exec-container-dynamicpv-hz2m: <nil>
STEP: delete the pod
Sep 26 07:37:45.680: INFO: Waiting for pod exec-volume-test-dynamicpv-hz2m to disappear
Sep 26 07:37:45.730: INFO: Pod exec-volume-test-dynamicpv-hz2m no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-hz2m
Sep 26 07:37:45.730: INFO: Deleting pod "exec-volume-test-dynamicpv-hz2m" in namespace "volume-2168"
... skipping 69 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 26 07:37:33.691: 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.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Sep 26 07:37:33.947: INFO: Creating resource for dynamic PV
Sep 26 07:37:33.947: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-5602-e2e-sc594lx
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Sep 26 07:37:40.306: INFO: Deleting pod "pod-7412eafe-ff8d-4ce6-bf8c-d175f5f40e0f" in namespace "volumemode-5602"
Sep 26 07:37:40.364: INFO: Wait up to 5m0s for pod "pod-7412eafe-ff8d-4ce6-bf8c-d175f5f40e0f" to be fully deleted
STEP: Deleting pvc
Sep 26 07:37:42.566: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comw9hl6"
Sep 26 07:37:42.616: INFO: Waiting up to 5m0s for PersistentVolume pvc-92184438-d6ae-4e0b-820e-c8d609b67a5f to get deleted
Sep 26 07:37:42.667: INFO: PersistentVolume pvc-92184438-d6ae-4e0b-820e-c8d609b67a5f found and phase=Released (50.073291ms)
... skipping 13 lines ...

• [SLOW TEST:44.510 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.h0A0b3MTk/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.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Sep 26 07:38:18.203: INFO: Distro debian doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
... skipping 84 lines ...
Sep 26 07:38:11.271: INFO: Waiting for pod aws-client to disappear
Sep 26 07:38:11.325: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Sep 26 07:38:11.325: INFO: Deleting PersistentVolumeClaim "pvc-kcsgg"
Sep 26 07:38:11.378: INFO: Deleting PersistentVolume "aws-tp2tc"
Sep 26 07:38:11.594: INFO: Couldn't delete PD "aws://us-west-1a/vol-0b3e94d4d63378a9b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0b3e94d4d63378a9b is currently attached to i-087195b8b11f3270f
	status code: 400, request id: 7e0f52d7-4be5-43ff-81aa-77d131c73af7
Sep 26 07:38:16.953: INFO: Couldn't delete PD "aws://us-west-1a/vol-0b3e94d4d63378a9b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0b3e94d4d63378a9b is currently attached to i-087195b8b11f3270f
	status code: 400, request id: a5ea2bd5-fef1-43af-8fdc-7992702b3a2a
Sep 26 07:38:22.287: INFO: Couldn't delete PD "aws://us-west-1a/vol-0b3e94d4d63378a9b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0b3e94d4d63378a9b is currently attached to i-087195b8b11f3270f
	status code: 400, request id: 7632b4c4-7f7b-46e7-9fb9-e6ae334ab67b
Sep 26 07:38:27.661: INFO: Successfully deleted PD "aws://us-west-1a/vol-0b3e94d4d63378a9b".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 26 07:38:27.661: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-4946" for this suite.
... skipping 217 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 26 07:38:05.588: 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.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Sep 26 07:38:05.835: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Sep 26 07:38:05.835: INFO: Creating resource for dynamic PV
Sep 26 07:38:05.835: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-32317df7w
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Sep 26 07:38:12.184: INFO: Deleting pod "pod-927946bf-d0ec-4f64-8741-89791ff1bf82" in namespace "volumemode-3231"
Sep 26 07:38:12.236: INFO: Wait up to 5m0s for pod "pod-927946bf-d0ec-4f64-8741-89791ff1bf82" to be fully deleted
STEP: Deleting pvc
Sep 26 07:38:14.434: INFO: Deleting PersistentVolumeClaim "aws7hwwz"
Sep 26 07:38:14.484: INFO: Waiting up to 5m0s for PersistentVolume pvc-cc6add53-475b-4864-b7a3-8588cc4f6a33 to get deleted
Sep 26 07:38:14.535: INFO: PersistentVolume pvc-cc6add53-475b-4864-b7a3-8588cc4f6a33 found and phase=Released (50.566291ms)
... skipping 12 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.h0A0b3MTk/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.h0A0b3MTk/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
    /tmp/kops.h0A0b3MTk/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.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumes
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Sep 26 07:38:34.892: INFO: Driver "ebs.csi.aws.com" does not support volume type "PreprovisionedPV" - skipping
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumes
... skipping 17 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 26 07:38:18.206: 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.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Sep 26 07:38:18.462: INFO: Creating resource for dynamic PV
Sep 26 07:38:18.462: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-1793-e2e-scvxx94
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Sep 26 07:38:24.827: INFO: Deleting pod "pod-62202bae-7cfe-4b9d-9eca-967865a4caab" in namespace "volumemode-1793"
Sep 26 07:38:24.878: INFO: Wait up to 5m0s for pod "pod-62202bae-7cfe-4b9d-9eca-967865a4caab" to be fully deleted
STEP: Deleting pvc
Sep 26 07:38:27.079: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comspss8"
Sep 26 07:38:27.131: INFO: Waiting up to 5m0s for PersistentVolume pvc-1083ba2f-a660-4f9c-a3ea-606ec5235ab0 to get deleted
Sep 26 07:38:27.181: INFO: PersistentVolume pvc-1083ba2f-a660-4f9c-a3ea-606ec5235ab0 found and phase=Released (50.105178ms)
... skipping 9 lines ...

• [SLOW TEST:24.282 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.h0A0b3MTk/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.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Sep 26 07:38:42.490: INFO: Driver "ebs.csi.aws.com" does not support volume type "PreprovisionedPV" - skipping
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
... skipping 66 lines ...
Sep 26 07:36:47.898: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2520-e2e-scg2q87
STEP: creating a claim
Sep 26 07:36:47.949: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-vzvn
STEP: Creating a pod to test subpath
Sep 26 07:36:48.102: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-vzvn" in namespace "provisioning-2520" to be "Succeeded or Failed"
Sep 26 07:36:48.151: INFO: Pod "pod-subpath-test-dynamicpv-vzvn": Phase="Pending", Reason="", readiness=false. Elapsed: 49.171759ms
Sep 26 07:36:50.202: INFO: Pod "pod-subpath-test-dynamicpv-vzvn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.099921261s
Sep 26 07:36:52.252: INFO: Pod "pod-subpath-test-dynamicpv-vzvn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.14959892s
Sep 26 07:36:54.302: INFO: Pod "pod-subpath-test-dynamicpv-vzvn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.199232261s
Sep 26 07:36:56.354: INFO: Pod "pod-subpath-test-dynamicpv-vzvn": Phase="Pending", Reason="", readiness=false. Elapsed: 8.251330175s
Sep 26 07:36:58.404: INFO: Pod "pod-subpath-test-dynamicpv-vzvn": Phase="Pending", Reason="", readiness=false. Elapsed: 10.302116667s
Sep 26 07:37:00.455: INFO: Pod "pod-subpath-test-dynamicpv-vzvn": Phase="Pending", Reason="", readiness=false. Elapsed: 12.352641332s
Sep 26 07:37:02.504: INFO: Pod "pod-subpath-test-dynamicpv-vzvn": Phase="Pending", Reason="", readiness=false. Elapsed: 14.402099829s
Sep 26 07:37:04.562: INFO: Pod "pod-subpath-test-dynamicpv-vzvn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.460174719s
STEP: Saw pod success
Sep 26 07:37:04.563: INFO: Pod "pod-subpath-test-dynamicpv-vzvn" satisfied condition "Succeeded or Failed"
Sep 26 07:37:04.612: INFO: Trying to get logs from node ip-172-20-46-137.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-vzvn container test-container-subpath-dynamicpv-vzvn: <nil>
STEP: delete the pod
Sep 26 07:37:04.726: INFO: Waiting for pod pod-subpath-test-dynamicpv-vzvn to disappear
Sep 26 07:37:04.775: INFO: Pod pod-subpath-test-dynamicpv-vzvn no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-vzvn
Sep 26 07:37:04.775: INFO: Deleting pod "pod-subpath-test-dynamicpv-vzvn" in namespace "provisioning-2520"
STEP: Creating pod pod-subpath-test-dynamicpv-vzvn
STEP: Creating a pod to test subpath
Sep 26 07:37:04.874: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-vzvn" in namespace "provisioning-2520" to be "Succeeded or Failed"
Sep 26 07:37:04.923: INFO: Pod "pod-subpath-test-dynamicpv-vzvn": Phase="Pending", Reason="", readiness=false. Elapsed: 49.045813ms
Sep 26 07:37:06.974: INFO: Pod "pod-subpath-test-dynamicpv-vzvn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.099301103s
Sep 26 07:37:09.023: INFO: Pod "pod-subpath-test-dynamicpv-vzvn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.148820626s
Sep 26 07:37:11.073: INFO: Pod "pod-subpath-test-dynamicpv-vzvn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.198396536s
Sep 26 07:37:13.123: INFO: Pod "pod-subpath-test-dynamicpv-vzvn": Phase="Pending", Reason="", readiness=false. Elapsed: 8.248426487s
Sep 26 07:37:15.172: INFO: Pod "pod-subpath-test-dynamicpv-vzvn": Phase="Pending", Reason="", readiness=false. Elapsed: 10.297855872s
... skipping 23 lines ...
Sep 26 07:38:04.375: INFO: Pod "pod-subpath-test-dynamicpv-vzvn": Phase="Pending", Reason="", readiness=false. Elapsed: 59.500895155s
Sep 26 07:38:06.425: INFO: Pod "pod-subpath-test-dynamicpv-vzvn": Phase="Pending", Reason="", readiness=false. Elapsed: 1m1.550573077s
Sep 26 07:38:08.474: INFO: Pod "pod-subpath-test-dynamicpv-vzvn": Phase="Pending", Reason="", readiness=false. Elapsed: 1m3.60008962s
Sep 26 07:38:10.527: INFO: Pod "pod-subpath-test-dynamicpv-vzvn": Phase="Pending", Reason="", readiness=false. Elapsed: 1m5.652257086s
Sep 26 07:38:12.576: INFO: Pod "pod-subpath-test-dynamicpv-vzvn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m7.701914442s
STEP: Saw pod success
Sep 26 07:38:12.576: INFO: Pod "pod-subpath-test-dynamicpv-vzvn" satisfied condition "Succeeded or Failed"
Sep 26 07:38:12.626: INFO: Trying to get logs from node ip-172-20-54-151.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-vzvn container test-container-subpath-dynamicpv-vzvn: <nil>
STEP: delete the pod
Sep 26 07:38:12.752: INFO: Waiting for pod pod-subpath-test-dynamicpv-vzvn to disappear
Sep 26 07:38:12.802: INFO: Pod pod-subpath-test-dynamicpv-vzvn no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-vzvn
Sep 26 07:38:12.802: INFO: Deleting pod "pod-subpath-test-dynamicpv-vzvn" in namespace "provisioning-2520"
... skipping 111 lines ...
Sep 26 07:38:05.645: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-41274vhcs
STEP: creating a claim
Sep 26 07:38:05.694: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-6jrw
STEP: Creating a pod to test subpath
Sep 26 07:38:05.846: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-6jrw" in namespace "provisioning-4127" to be "Succeeded or Failed"
Sep 26 07:38:05.897: INFO: Pod "pod-subpath-test-dynamicpv-6jrw": Phase="Pending", Reason="", readiness=false. Elapsed: 50.727095ms
Sep 26 07:38:07.947: INFO: Pod "pod-subpath-test-dynamicpv-6jrw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.100489057s
Sep 26 07:38:09.999: INFO: Pod "pod-subpath-test-dynamicpv-6jrw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.152258187s
Sep 26 07:38:12.048: INFO: Pod "pod-subpath-test-dynamicpv-6jrw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.201682959s
Sep 26 07:38:14.097: INFO: Pod "pod-subpath-test-dynamicpv-6jrw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.250970609s
Sep 26 07:38:16.147: INFO: Pod "pod-subpath-test-dynamicpv-6jrw": Phase="Pending", Reason="", readiness=false. Elapsed: 10.300346713s
Sep 26 07:38:18.201: INFO: Pod "pod-subpath-test-dynamicpv-6jrw": Phase="Pending", Reason="", readiness=false. Elapsed: 12.354450073s
Sep 26 07:38:20.250: INFO: Pod "pod-subpath-test-dynamicpv-6jrw": Phase="Pending", Reason="", readiness=false. Elapsed: 14.404018854s
Sep 26 07:38:22.300: INFO: Pod "pod-subpath-test-dynamicpv-6jrw": Phase="Pending", Reason="", readiness=false. Elapsed: 16.453640772s
Sep 26 07:38:24.349: INFO: Pod "pod-subpath-test-dynamicpv-6jrw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.503116047s
STEP: Saw pod success
Sep 26 07:38:24.349: INFO: Pod "pod-subpath-test-dynamicpv-6jrw" satisfied condition "Succeeded or Failed"
Sep 26 07:38:24.399: INFO: Trying to get logs from node ip-172-20-54-151.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-6jrw container test-container-volume-dynamicpv-6jrw: <nil>
STEP: delete the pod
Sep 26 07:38:24.504: INFO: Waiting for pod pod-subpath-test-dynamicpv-6jrw to disappear
Sep 26 07:38:24.555: INFO: Pod pod-subpath-test-dynamicpv-6jrw no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-6jrw
Sep 26 07:38:24.555: INFO: Deleting pod "pod-subpath-test-dynamicpv-6jrw" in namespace "provisioning-4127"
... skipping 417 lines ...
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 26 07:38:52.772: 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.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Sep 26 07:38:53.077: INFO: found topology map[topology.kubernetes.io/zone:us-west-1a]
Sep 26 07:38:53.077: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Sep 26 07:38:53.077: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.h0A0b3MTk/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.h0A0b3MTk/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (delayed binding)] topology
    /tmp/kops.h0A0b3MTk/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.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 538 lines ...
Sep 26 07:38:14.603: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6197-e2e-sc49hbz
STEP: creating a claim
Sep 26 07:38:14.654: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-zmqg
STEP: Creating a pod to test subpath
Sep 26 07:38:14.816: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-zmqg" in namespace "provisioning-6197" to be "Succeeded or Failed"
Sep 26 07:38:14.866: INFO: Pod "pod-subpath-test-dynamicpv-zmqg": Phase="Pending", Reason="", readiness=false. Elapsed: 49.415025ms
Sep 26 07:38:16.916: INFO: Pod "pod-subpath-test-dynamicpv-zmqg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.09936488s
Sep 26 07:38:18.967: INFO: Pod "pod-subpath-test-dynamicpv-zmqg": Phase="Pending", Reason="", readiness=false. Elapsed: 4.150381014s
Sep 26 07:38:21.016: INFO: Pod "pod-subpath-test-dynamicpv-zmqg": Phase="Pending", Reason="", readiness=false. Elapsed: 6.199883264s
Sep 26 07:38:23.067: INFO: Pod "pod-subpath-test-dynamicpv-zmqg": Phase="Pending", Reason="", readiness=false. Elapsed: 8.250148976s
Sep 26 07:38:25.117: INFO: Pod "pod-subpath-test-dynamicpv-zmqg": Phase="Pending", Reason="", readiness=false. Elapsed: 10.30089513s
Sep 26 07:38:27.167: INFO: Pod "pod-subpath-test-dynamicpv-zmqg": Phase="Pending", Reason="", readiness=false. Elapsed: 12.350517035s
Sep 26 07:38:29.217: INFO: Pod "pod-subpath-test-dynamicpv-zmqg": Phase="Pending", Reason="", readiness=false. Elapsed: 14.400302997s
Sep 26 07:38:31.267: INFO: Pod "pod-subpath-test-dynamicpv-zmqg": Phase="Pending", Reason="", readiness=false. Elapsed: 16.450214926s
Sep 26 07:38:33.318: INFO: Pod "pod-subpath-test-dynamicpv-zmqg": Phase="Pending", Reason="", readiness=false. Elapsed: 18.501018082s
Sep 26 07:38:35.367: INFO: Pod "pod-subpath-test-dynamicpv-zmqg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.550904219s
STEP: Saw pod success
Sep 26 07:38:35.368: INFO: Pod "pod-subpath-test-dynamicpv-zmqg" satisfied condition "Succeeded or Failed"
Sep 26 07:38:35.417: INFO: Trying to get logs from node ip-172-20-54-151.us-west-1.compute.internal pod pod-subpath-test-dynamicpv-zmqg container test-container-subpath-dynamicpv-zmqg: <nil>
STEP: delete the pod
Sep 26 07:38:35.528: INFO: Waiting for pod pod-subpath-test-dynamicpv-zmqg to disappear
Sep 26 07:38:35.581: INFO: Pod pod-subpath-test-dynamicpv-zmqg no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-zmqg
Sep 26 07:38:35.581: INFO: Deleting pod "pod-subpath-test-dynamicpv-zmqg" in namespace "provisioning-6197"
... skipping 61 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.h0A0b3MTk/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.h0A0b3MTk/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.h0A0b3MTk/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.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 560 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 26 07:38:50.205: 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.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Sep 26 07:38:50.458: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Sep 26 07:38:50.950: INFO: Successfully created a new PD: "aws://us-west-1a/vol-09191c87f41a1ec4a".
Sep 26 07:38:50.951: INFO: Creating resource for pre-provisioned PV
Sep 26 07:38:50.951: INFO: Creating PVC and PV
... skipping 5 lines ...
Sep 26 07:38:55.299: INFO: PersistentVolumeClaim pvc-c557v found but phase is Pending instead of Bound.
Sep 26 07:38:57.352: INFO: PersistentVolumeClaim pvc-c557v found but phase is Pending instead of Bound.
Sep 26 07:38:59.403: INFO: PersistentVolumeClaim pvc-c557v found and phase=Bound (8.259221241s)
Sep 26 07:38:59.403: INFO: Waiting up to 3m0s for PersistentVolume aws-tc4sk to have phase Bound
Sep 26 07:38:59.453: INFO: PersistentVolume aws-tc4sk found and phase=Bound (50.26644ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Sep 26 07:39:01.761: INFO: Deleting pod "pod-6156d8d2-6554-46b1-8845-18b2f97d39b8" in namespace "volumemode-6419"
Sep 26 07:39:01.814: INFO: Wait up to 5m0s for pod "pod-6156d8d2-6554-46b1-8845-18b2f97d39b8" to be fully deleted
STEP: Deleting pv and pvc
Sep 26 07:39:03.917: INFO: Deleting PersistentVolumeClaim "pvc-c557v"
Sep 26 07:39:03.969: INFO: Deleting PersistentVolume "aws-tc4sk"
Sep 26 07:39:04.222: INFO: Couldn't delete PD "aws://us-west-1a/vol-09191c87f41a1ec4a", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-09191c87f41a1ec4a is currently attached to i-02155aa2ab4de4c90
	status code: 400, request id: a00e27fc-a2b7-4fab-88e0-6509aba5d53d
Sep 26 07:39:09.619: INFO: Couldn't delete PD "aws://us-west-1a/vol-09191c87f41a1ec4a", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-09191c87f41a1ec4a is currently attached to i-02155aa2ab4de4c90
	status code: 400, request id: 7f403642-254f-4447-ad49-2f220eb97f56
Sep 26 07:39:14.990: INFO: Couldn't delete PD "aws://us-west-1a/vol-09191c87f41a1ec4a", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-09191c87f41a1ec4a is currently attached to i-02155aa2ab4de4c90
	status code: 400, request id: 78ee8736-59ff-4f3a-885d-436ec958ce58
Sep 26 07:39:20.360: INFO: Couldn't delete PD "aws://us-west-1a/vol-09191c87f41a1ec4a", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-09191c87f41a1ec4a is currently attached to i-02155aa2ab4de4c90
	status code: 400, request id: 41bae677-d630-49d5-9998-74c46f2b5df9
Sep 26 07:39:25.717: INFO: Successfully deleted PD "aws://us-west-1a/vol-09191c87f41a1ec4a".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 26 07:39:25.717: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-6419" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.h0A0b3MTk/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.h0A0b3MTk/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
    /tmp/kops.h0A0b3MTk/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.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)(allowExpansion)][Feature:Windows] volume-expand
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Sep 26 07:39:25.823: INFO: Driver ebs.csi.aws.com doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)(allowExpansion)][Feature:Windows] volume-expand
... skipping 174 lines ...
Sep 26 07:39:26.811: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 211 lines ...
Sep 26 07:39:12.005: INFO: Creating resource for dynamic PV
Sep 26 07:39:12.006: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-91827nw5j
STEP: creating a claim
STEP: Expanding non-expandable pvc
Sep 26 07:39:12.156: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Sep 26 07:39:12.255: INFO: Error updating pvc aws6db9g: PersistentVolumeClaim "aws6db9g" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-91827nw5j",
  	... // 3 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Sep 26 07:39:42.455: INFO: Error updating pvc aws6db9g: PersistentVolumeClaim "aws6db9g" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 160 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 26 07:38:59.438: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename provisioning
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail if non-existent subpath is outside the volume [Slow][LinuxOnly]
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Sep 26 07:38:59.690: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Sep 26 07:38:59.690: INFO: Creating resource for dynamic PV
Sep 26 07:38:59.690: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6934f7r57
STEP: creating a claim
Sep 26 07:38:59.741: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-dwbh
STEP: Checking for subpath error in container status
Sep 26 07:39:21.999: INFO: Deleting pod "pod-subpath-test-dynamicpv-dwbh" in namespace "provisioning-6934"
Sep 26 07:39:22.053: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-dwbh" to be fully deleted
STEP: Deleting pod
Sep 26 07:39:26.154: INFO: Deleting pod "pod-subpath-test-dynamicpv-dwbh" in namespace "provisioning-6934"
STEP: Deleting pvc
Sep 26 07:39:26.305: INFO: Deleting PersistentVolumeClaim "awsjsxb7"
... skipping 14 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.h0A0b3MTk/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.h0A0b3MTk/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.h0A0b3MTk/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.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 136 lines ...
Sep 26 07:39:39.856: INFO: Waiting for pod aws-client to disappear
Sep 26 07:39:39.907: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Sep 26 07:39:39.907: INFO: Deleting PersistentVolumeClaim "pvc-6cphv"
Sep 26 07:39:39.958: INFO: Deleting PersistentVolume "aws-j7tk4"
Sep 26 07:39:40.201: INFO: Couldn't delete PD "aws://us-west-1a/vol-01c38aeff0818f9f1", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01c38aeff0818f9f1 is currently attached to i-087195b8b11f3270f
	status code: 400, request id: 69ed51dd-c579-4b1a-9cb2-6ed3bc645a79
Sep 26 07:39:45.531: INFO: Couldn't delete PD "aws://us-west-1a/vol-01c38aeff0818f9f1", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01c38aeff0818f9f1 is currently attached to i-087195b8b11f3270f
	status code: 400, request id: c63e89d8-682d-4955-ae40-fecaec22580e
Sep 26 07:39:50.899: INFO: Successfully deleted PD "aws://us-west-1a/vol-01c38aeff0818f9f1".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 26 07:39:50.899: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-1867" for this suite.
... skipping 22 lines ...
Sep 26 07:39:17.706: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Sep 26 07:39:18.257: INFO: Successfully created a new PD: "aws://us-west-1a/vol-0c63bc8c8daf74fad".
Sep 26 07:39:18.257: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-nbk9
STEP: Creating a pod to test exec-volume-test
Sep 26 07:39:18.308: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-nbk9" in namespace "volume-7350" to be "Succeeded or Failed"
Sep 26 07:39:18.358: INFO: Pod "exec-volume-test-inlinevolume-nbk9": Phase="Pending", Reason="", readiness=false. Elapsed: 50.287992ms
Sep 26 07:39:20.408: INFO: Pod "exec-volume-test-inlinevolume-nbk9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.099675483s
Sep 26 07:39:22.462: INFO: Pod "exec-volume-test-inlinevolume-nbk9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.154161025s
Sep 26 07:39:24.512: INFO: Pod "exec-volume-test-inlinevolume-nbk9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.203822671s
Sep 26 07:39:26.561: INFO: Pod "exec-volume-test-inlinevolume-nbk9": Phase="Pending", Reason="", readiness=false. Elapsed: 8.25328018s
Sep 26 07:39:28.613: INFO: Pod "exec-volume-test-inlinevolume-nbk9": Phase="Pending", Reason="", readiness=false. Elapsed: 10.304487601s
... skipping 2 lines ...
Sep 26 07:39:34.770: INFO: Pod "exec-volume-test-inlinevolume-nbk9": Phase="Pending", Reason="", readiness=false. Elapsed: 16.461701435s
Sep 26 07:39:36.820: INFO: Pod "exec-volume-test-inlinevolume-nbk9": Phase="Pending", Reason="", readiness=false. Elapsed: 18.51140772s
Sep 26 07:39:38.869: INFO: Pod "exec-volume-test-inlinevolume-nbk9": Phase="Pending", Reason="", readiness=false. Elapsed: 20.560986545s
Sep 26 07:39:40.920: INFO: Pod "exec-volume-test-inlinevolume-nbk9": Phase="Pending", Reason="", readiness=false. Elapsed: 22.612199413s
Sep 26 07:39:42.970: INFO: Pod "exec-volume-test-inlinevolume-nbk9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.661713575s
STEP: Saw pod success
Sep 26 07:39:42.970: INFO: Pod "exec-volume-test-inlinevolume-nbk9" satisfied condition "Succeeded or Failed"
Sep 26 07:39:43.021: INFO: Trying to get logs from node ip-172-20-35-50.us-west-1.compute.internal pod exec-volume-test-inlinevolume-nbk9 container exec-container-inlinevolume-nbk9: <nil>
STEP: delete the pod
Sep 26 07:39:43.142: INFO: Waiting for pod exec-volume-test-inlinevolume-nbk9 to disappear
Sep 26 07:39:43.191: INFO: Pod exec-volume-test-inlinevolume-nbk9 no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-nbk9
Sep 26 07:39:43.191: INFO: Deleting pod "exec-volume-test-inlinevolume-nbk9" in namespace "volume-7350"
Sep 26 07:39:43.392: INFO: Couldn't delete PD "aws://us-west-1a/vol-0c63bc8c8daf74fad", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c63bc8c8daf74fad is currently attached to i-0c0aac37066181110
	status code: 400, request id: 7e92e567-9984-42e1-843d-dfb60ee2808c
Sep 26 07:39:48.720: INFO: Couldn't delete PD "aws://us-west-1a/vol-0c63bc8c8daf74fad", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c63bc8c8daf74fad is currently attached to i-0c0aac37066181110
	status code: 400, request id: 32ebd8c6-2bb6-4e7d-b0ec-dfadcb4baad7
Sep 26 07:39:54.072: INFO: Successfully deleted PD "aws://us-west-1a/vol-0c63bc8c8daf74fad".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 26 07:39:54.073: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-7350" for this suite.
... skipping 653 lines ...
Sep 26 07:39:27.074: INFO: Creating resource for dynamic PV
Sep 26 07:39:27.074: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6331-e2e-scr4dw8
STEP: creating a claim
Sep 26 07:39:27.125: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-6331
Sep 26 07:39:27.280: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-6331" in namespace "provisioning-6331" to be "Succeeded or Failed"
Sep 26 07:39:27.330: INFO: Pod "volume-prep-provisioning-6331": Phase="Pending", Reason="", readiness=false. Elapsed: 50.200578ms
Sep 26 07:39:29.381: INFO: Pod "volume-prep-provisioning-6331": Phase="Pending", Reason="", readiness=false. Elapsed: 2.101629337s
Sep 26 07:39:31.433: INFO: Pod "volume-prep-provisioning-6331": Phase="Pending", Reason="", readiness=false. Elapsed: 4.153668697s
Sep 26 07:39:33.485: INFO: Pod "volume-prep-provisioning-6331": Phase="Pending", Reason="", readiness=false. Elapsed: 6.205368978s
Sep 26 07:39:35.536: INFO: Pod "volume-prep-provisioning-6331": Phase="Pending", Reason="", readiness=false. Elapsed: 8.256233557s
Sep 26 07:39:37.588: INFO: Pod "volume-prep-provisioning-6331": Phase="Pending", Reason="", readiness=false. Elapsed: 10.307961853s
... skipping 2 lines ...
Sep 26 07:39:43.738: INFO: Pod "volume-prep-provisioning-6331": Phase="Pending", Reason="", readiness=false. Elapsed: 16.458346335s
Sep 26 07:39:45.789: INFO: Pod "volume-prep-provisioning-6331": Phase="Pending", Reason="", readiness=false. Elapsed: 18.509531541s
Sep 26 07:39:47.839: INFO: Pod "volume-prep-provisioning-6331": Phase="Pending", Reason="", readiness=false. Elapsed: 20.559618516s
Sep 26 07:39:49.890: INFO: Pod "volume-prep-provisioning-6331": Phase="Pending", Reason="", readiness=false. Elapsed: 22.610511828s
Sep 26 07:39:51.940: INFO: Pod "volume-prep-provisioning-6331": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.660642468s
STEP: Saw pod success
Sep 26 07:39:51.940: INFO: Pod "volume-prep-provisioning-6331" satisfied condition "Succeeded or Failed"
Sep 26 07:39:51.940: INFO: Deleting pod "volume-prep-provisioning-6331" in namespace "provisioning-6331"
Sep 26 07:39:51.997: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-6331" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-8j4l
STEP: Checking for subpath error in container status
Sep 26 07:40:10.199: INFO: Deleting pod "pod-subpath-test-dynamicpv-8j4l" in namespace "provisioning-6331"
Sep 26 07:40:10.254: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-8j4l" to be fully deleted
STEP: Deleting pod
Sep 26 07:40:10.303: INFO: Deleting pod "pod-subpath-test-dynamicpv-8j4l" in namespace "provisioning-6331"
STEP: Deleting pvc
Sep 26 07:40:10.450: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comkfxwf"
... skipping 417 lines ...
Sep 26 07:43:42.128: INFO: Waiting for pod aws-client to disappear
Sep 26 07:43:42.179: INFO: Pod aws-client still exists
Sep 26 07:43:44.128: INFO: Waiting for pod aws-client to disappear
Sep 26 07:43:44.179: INFO: Pod aws-client still exists
Sep 26 07:43:46.129: INFO: Waiting for pod aws-client to disappear
Sep 26 07:43:46.180: INFO: Pod aws-client no longer exists
Sep 26 07:43:46.180: FAIL: Failed to create client pod: timed out waiting for the condition

Full Stack Trace
k8s.io/kubernetes/test/e2e/framework/volume.TestVolumeClient(...)
	/tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/framework/volume/fixtures.go:505
k8s.io/kubernetes/test/e2e/storage/testsuites.(*volumesTestSuite).DefineTests.func3()
	/tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:188 +0x4df
github.com/kubernetes-sigs/aws-ebs-csi-driver/tests/e2e-kubernetes.TestEBSCSI(0x407c59)
	/tmp/kops.h0A0b3MTk/tests/e2e-kubernetes/e2e_test.go:82 +0x319
testing.tRunner(0xc0000d6820, 0x28f9180)
	/usr/local/go/src/testing/testing.go:1259 +0x102
created by testing.(*T).Run
	/usr/local/go/src/testing/testing.go:1306 +0x35a
STEP: cleaning the environment after aws
Sep 26 07:43:46.551: INFO: Couldn't delete PD "aws://us-west-1a/vol-035c6d15be2f9b80e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-035c6d15be2f9b80e is currently attached to i-0c0aac37066181110
	status code: 400, request id: 506049f0-ba80-4168-9158-f48c0238728c
Sep 26 07:43:51.928: INFO: Successfully deleted PD "aws://us-west-1a/vol-035c6d15be2f9b80e".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
STEP: Collecting events from namespace "volume-2658".
STEP: Found 12 events.
Sep 26 07:43:51.979: INFO: At 2021-09-26 07:36:46 +0000 UTC - event for aws-injector: {default-scheduler } Scheduled: Successfully assigned volume-2658/aws-injector to ip-172-20-54-151.us-west-1.compute.internal
Sep 26 07:43:51.979: INFO: At 2021-09-26 07:36:57 +0000 UTC - event for aws-injector: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "ebs.csi.aws.com-vol-035c6d15be2f9b80e" 
Sep 26 07:43:51.979: INFO: At 2021-09-26 07:37:03 +0000 UTC - event for aws-injector: {kubelet ip-172-20-54-151.us-west-1.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" already present on machine
Sep 26 07:43:51.979: INFO: At 2021-09-26 07:37:03 +0000 UTC - event for aws-injector: {kubelet ip-172-20-54-151.us-west-1.compute.internal} Created: Created container aws-injector
Sep 26 07:43:51.979: INFO: At 2021-09-26 07:37:03 +0000 UTC - event for aws-injector: {kubelet ip-172-20-54-151.us-west-1.compute.internal} Started: Started container aws-injector
Sep 26 07:43:51.979: INFO: At 2021-09-26 07:37:07 +0000 UTC - event for aws-injector: {kubelet ip-172-20-54-151.us-west-1.compute.internal} Killing: Stopping container aws-injector
Sep 26 07:43:51.979: INFO: At 2021-09-26 07:37:09 +0000 UTC - event for aws-client: {default-scheduler } Scheduled: Successfully assigned volume-2658/aws-client to ip-172-20-35-50.us-west-1.compute.internal
Sep 26 07:43:51.979: INFO: At 2021-09-26 07:37:09 +0000 UTC - event for aws-client: {attachdetach-controller } FailedAttachVolume: Multi-Attach error for volume "ebs.csi.aws.com-vol-035c6d15be2f9b80e" Volume is already exclusively attached to one node and can't be attached to another
Sep 26 07:43:51.979: INFO: At 2021-09-26 07:37:10 +0000 UTC - event for aws-injector: {kubelet ip-172-20-54-151.us-west-1.compute.internal} FailedKillPod: error killing pod: failed to "KillContainer" for "aws-injector" with KillContainerError: "rpc error: code = NotFound desc = an error occurred when try to find container \"df78e23e2d6e2fbd088e55eff91c76c4e9ef5fed2c96088ddce83e0002c40198\": not found"
Sep 26 07:43:51.979: INFO: At 2021-09-26 07:38:03 +0000 UTC - event for aws-client: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "ebs.csi.aws.com-vol-035c6d15be2f9b80e" : rpc error: code = DeadlineExceeded desc = context deadline exceeded
Sep 26 07:43:51.979: INFO: At 2021-09-26 07:38:05 +0000 UTC - event for aws-client: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "ebs.csi.aws.com-vol-035c6d15be2f9b80e" : rpc error: code = Internal desc = Could not attach volume "vol-035c6d15be2f9b80e" to node "i-0c0aac37066181110": attachment of disk "vol-035c6d15be2f9b80e" failed, expected device to be attached but was attaching
Sep 26 07:43:51.979: INFO: At 2021-09-26 07:39:12 +0000 UTC - event for aws-client: {kubelet ip-172-20-35-50.us-west-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[aws-volume-0], unattached volumes=[aws-volume-0 kube-api-access-8l5x5]: timed out waiting for the condition
Sep 26 07:43:52.029: INFO: POD  NODE  PHASE  GRACE  CONDITIONS
Sep 26 07:43:52.029: INFO: 
Sep 26 07:43:52.081: INFO: 
Logging node info for node ip-172-20-35-50.us-west-1.compute.internal
Sep 26 07:43:52.132: INFO: Node Info: &Node{ObjectMeta:{ip-172-20-35-50.us-west-1.compute.internal    44fc721e-7055-457a-adb1-9cde2238da60 16701 0 2021-09-26 07:28:04 +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-35-50.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-0c0aac37066181110"} node.alpha.kubernetes.io/ttl:0 projectcalico.org/IPv4Address:172.20.35.50/19 projectcalico.org/IPv4IPIPTunnelAddr:100.96.62.0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] []  [{kops-controller Update v1 2021-09-26 07:28:04 +0000 UTC FieldsV1 {"f:metadata":{"f:labels":{"f:kops.k8s.io/instancegroup":{},"f:kubernetes.io/role":{},"f:node-role.kubernetes.io/node":{}}}}} {kubelet Update v1 2021-09-26 07:28:04 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}}}} {kube-controller-manager Update v1 2021-09-26 07:28:14 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"100.96.4.0/24\"":{}}}}} {calico-node Update v1 2021-09-26 07:28:20 +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":{}}}}}} {kube-controller-manager Update v1 2021-09-26 07:32:21 +0000 UTC FieldsV1 {"f:status":{"f:volumesAttached":{}}}} {kubelet Update v1 2021-09-26 07:32:25 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:csi.volume.kubernetes.io/nodeid":{}},"f:labels":{"f:topology.ebs.csi.aws.com/zone":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{},"f:volumesInUse":{}}}}]},Spec:NodeSpec{PodCIDR:100.96.4.0/24,DoNotUseExternalID:,ProviderID:aws:///us-west-1a/i-0c0aac37066181110,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[100.96.4.0/24],},Status:NodeStatus{Capacity:ResourceList{cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{49895047168 0} {<nil>}  BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{4059734016 0} {<nil>}  BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{44905542377 0} {<nil>} 44905542377 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{3954876416 0} {<nil>}  BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2021-09-26 07:28:20 +0000 UTC,LastTransitionTime:2021-09-26 07:28:20 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2021-09-26 07:43:48 +0000 UTC,LastTransitionTime:2021-09-26 07:28:04 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2021-09-26 07:43:48 +0000 UTC,LastTransitionTime:2021-09-26 07:28:04 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2021-09-26 07:43:48 +0000 UTC,LastTransitionTime:2021-09-26 07:28:04 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2021-09-26 07:43:48 +0000 UTC,LastTransitionTime:2021-09-26 07:28:14 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:172.20.35.50,},NodeAddress{Type:ExternalIP,Address:54.153.125.114,},NodeAddress{Type:Hostname,Address:ip-172-20-35-50.us-west-1.compute.internal,},NodeAddress{Type:InternalDNS,Address:ip-172-20-35-50.us-west-1.compute.internal,},NodeAddress{Type:ExternalDNS,Address:ec2-54-153-125-114.us-west-1.compute.amazonaws.com,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:ec22d1c34146ed4f07b32cd7608ca119,SystemUUID:ec22d1c3-4146-ed4f-07b3-2cd7608ca119,BootID:933cfeb7-c025-4018-a1b4-b65507cb6abb,KernelVersion:5.11.0-1017-aws,OSImage:Ubuntu 20.04.3 LTS,ContainerRuntimeVersion:containerd://1.4.9,KubeletVersion:v1.22.1,KubeProxyVersion:v1.22.1,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[k8s.gcr.io/provider-aws/aws-ebs-csi-driver@sha256:732da7df530f4ad1923a7c71b927b0d964e596c622de68c1c6179fb7148704fd k8s.gcr.io/provider-aws/aws-ebs-csi-driver:v1.2.1],SizeBytes:66930652,},ContainerImage{Names:[docker.io/calico/node@sha256:cf8ecfef7efd119fbcc491857005ebcca20acbd06ad98416b5bd876d816238e3 docker.io/calico/node:v3.20.1],SizeBytes:57679520,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/agnhost@sha256:8bd76a6a7778e203b61e18e5ee85b1faf52e6a30eb07e445a165ab90fe9633e3 k8s.gcr.io/e2e-test-images/agnhost:2.31],SizeBytes:49692421,},ContainerImage{Names:[docker.io/calico/cni@sha256:d09c2db1ad87dbe3b1e08ef7300e689c914ad4caae699441c72179e72076bc78 docker.io/calico/cni:v3.20.1],SizeBytes:48389221,},ContainerImage{Names:[k8s.gcr.io/build-image/debian-iptables@sha256:abe8cef9e116f2d5ec1175c386e33841ff3386779138b425af876384b0fd7ccb k8s.gcr.io/build-image/debian-iptables:buster-v1.5.0],SizeBytes:38088315,},ContainerImage{Names:[k8s.gcr.io/kube-proxy@sha256:efcf1d5fb2fc95d28841f534f1385a4884230c7c876fb1b7cf66d2777ad6dc56 k8s.gcr.io/kube-proxy:v1.22.1],SizeBytes:35941601,},ContainerImage{Names:[k8s.gcr.io/coredns/coredns@sha256:6e5a02c21641597998b4be7cb5eb1e7b02c0d8d23cce4dd09f4682d463798890 k8s.gcr.io/coredns/coredns:v1.8.4],SizeBytes:13707249,},ContainerImage{Names:[docker.io/calico/pod2daemon-flexvol@sha256:a173b89decb2bfd5e7cba0acac15d2035008df67e3c52b1f3bd388c284a95917 docker.io/calico/pod2daemon-flexvol:v3.20.1],SizeBytes:9359088,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-node-driver-registrar@sha256:a61d309da54641db41fb8f35718f744e9f730d4d0384f8c4b186ddc9f06cbd5f k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.1.0],SizeBytes:9068367,},ContainerImage{Names:[k8s.gcr.io/sig-storage/livenessprobe@sha256:48da0e4ed7238ad461ea05f68c25921783c37b315f21a5c5a2780157a6460994 k8s.gcr.io/sig-storage/livenessprobe:v2.2.0],SizeBytes:8279778,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/nginx@sha256:503b7abb89e57383eba61cc8a9cb0b495ea575c516108f7d972a6ff6e1ab3c9b k8s.gcr.io/e2e-test-images/nginx:1.14-1],SizeBytes:6979365,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/busybox@sha256:39e1e963e5310e9c313bad51523be012ede7b35bb9316517d19089a010356592 k8s.gcr.io/e2e-test-images/busybox:1.29-1],SizeBytes:732746,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:927d98197ec1141a368550822d18fa1c60bdae27b78b0c004f705f548c07814f k8s.gcr.io/pause:3.2],SizeBytes:299513,},},VolumesInUse:[kubernetes.io/csi/ebs.csi.aws.com^vol-00604efe1b2f48e49 kubernetes.io/csi/ebs.csi.aws.com^vol-019d433954ed43c15 kubernetes.io/csi/ebs.csi.aws.com^vol-01a54a6129b54535f kubernetes.io/csi/ebs.csi.aws.com^vol-01db9c2642a3c00ef kubernetes.io/csi/ebs.csi.aws.com^vol-026e7b0b0fed2a9e8 kubernetes.io/csi/ebs.csi.aws.com^vol-02cb60e57b3e93629 kubernetes.io/csi/ebs.csi.aws.com^vol-035818a5d6d1883f4 kubernetes.io/csi/ebs.csi.aws.com^vol-040337ea0ff978db6 kubernetes.io/csi/ebs.csi.aws.com^vol-04cf9fc2a7ebb88b9 kubernetes.io/csi/ebs.csi.aws.com^vol-058871be23ba3b260 kubernetes.io/csi/ebs.csi.aws.com^vol-070d211ec90f0364a kubernetes.io/csi/ebs.csi.aws.com^vol-075c941b42c7ebc2a kubernetes.io/csi/ebs.csi.aws.com^vol-07813c0dc6652fc80 kubernetes.io/csi/ebs.csi.aws.com^vol-07e8372cc98a0c34e kubernetes.io/csi/ebs.csi.aws.com^vol-08377241aa8871222 kubernetes.io/csi/ebs.csi.aws.com^vol-08ada3b6bbff24691 kubernetes.io/csi/ebs.csi.aws.com^vol-0956d73b54f5d88c3 kubernetes.io/csi/ebs.csi.aws.com^vol-09ab0daf43dd78837 kubernetes.io/csi/ebs.csi.aws.com^vol-09f66c90440ef65d7 kubernetes.io/csi/ebs.csi.aws.com^vol-0a52c61f85bbd1a55 kubernetes.io/csi/ebs.csi.aws.com^vol-0a84c7c5502569a78 kubernetes.io/csi/ebs.csi.aws.com^vol-0aa0dfca665486551 kubernetes.io/csi/ebs.csi.aws.com^vol-0ab2aa29630a5da5b kubernetes.io/csi/ebs.csi.aws.com^vol-0b38c8e9db88ed82f kubernetes.io/csi/ebs.csi.aws.com^vol-0bb3bd4ba4b388540 kubernetes.io/csi/ebs.csi.aws.com^vol-0c4aea13bb963c6da kubernetes.io/csi/ebs.csi.aws.com^vol-0c5c70cf331210db0 kubernetes.io/csi/ebs.csi.aws.com^vol-0c6956e0af6b4fb99 kubernetes.io/csi/ebs.csi.aws.com^vol-0c8d44d75f22d9482 kubernetes.io/csi/ebs.csi.aws.com^vol-0ce5ac9db3cb0a17d kubernetes.io/csi/ebs.csi.aws.com^vol-0d0396e078226aee6 kubernetes.io/csi/ebs.csi.aws.com^vol-0d547057587a631e5 kubernetes.io/csi/ebs.csi.aws.com^vol-0e2d95a4a537653f1 kubernetes.io/csi/ebs.csi.aws.com^vol-0f0968936d92f23a4 kubernetes.io/csi/ebs.csi.aws.com^vol-0f169d0012e16ca79 kubernetes.io/csi/ebs.csi.aws.com^vol-0f2047b686ea71379 kubernetes.io/csi/ebs.csi.aws.com^vol-0f2bae7ff31eb6666 kubernetes.io/csi/ebs.csi.aws.com^vol-0fe52e07e2ae129ed kubernetes.io/csi/ebs.csi.aws.com^vol-0fe9a3fdb6999e13f kubernetes.io/csi/ebs.csi.aws.com^vol-0ffba31b930918105],VolumesAttached:[]AttachedVolume{AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-035818a5d6d1883f4,DevicePath:,},AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-0d547057587a631e5,DevicePath:,},AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-026e7b0b0fed2a9e8,DevicePath:,},AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-040337ea0ff978db6,DevicePath:,},AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-0ab2aa29630a5da5b,DevicePath:,},AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-08377241aa8871222,DevicePath:,},AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-0aa0dfca665486551,DevicePath:,},AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-0ffba31b930918105,DevicePath:,},AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-00604efe1b2f48e49,DevicePath:,},AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-0f2047b686ea71379,DevicePath:,},AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-09ab0daf43dd78837,DevicePath:,},AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-07e8372cc98a0c34e,DevicePath:,},AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-0d0396e078226aee6,DevicePath:,},AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-0c4aea13bb963c6da,DevicePath:,},AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-019d433954ed43c15,DevicePath:,},AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-0c8d44d75f22d9482,DevicePath:,},AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-0b38c8e9db88ed82f,DevicePath:,},AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-0fe9a3fdb6999e13f,DevicePath:,},AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-058871be23ba3b260,DevicePath:,},AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-07813c0dc6652fc80,DevicePath:,},AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-0bb3bd4ba4b388540,DevicePath:,},AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-0ce5ac9db3cb0a17d,DevicePath:,},AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-01db9c2642a3c00ef,DevicePath:,},AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-0c5c70cf331210db0,DevicePath:,},AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-0f169d0012e16ca79,DevicePath:,},AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-09f66c90440ef65d7,DevicePath:,},},Config:nil,},}
... skipping 157 lines ...
  /tmp/kops.h0A0b3MTk/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (ext4)] volumes
    /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should store data [It]
      /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:159

      Sep 26 07:43:46.180: Failed to create client pod: timed out waiting for the condition

      /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/framework/volume/fixtures.go:505
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
... skipping 28 lines ...
STEP: Found 8 events.
Sep 26 07:45:02.676: INFO: At 2021-09-26 07:38:16 +0000 UTC - event for aws9vgpn: {persistentvolume-controller } WaitForFirstConsumer: waiting for first consumer to be created before binding
Sep 26 07:45:02.676: INFO: At 2021-09-26 07:38:16 +0000 UTC - event for aws9vgpn: {persistentvolume-controller } ExternalProvisioning: waiting for a volume to be created, either by external provisioner "ebs.csi.aws.com" or manually created by system administrator
Sep 26 07:45:02.676: INFO: At 2021-09-26 07:38:16 +0000 UTC - event for aws9vgpn: {ebs.csi.aws.com_ebs-csi-controller-564bc97466-6chfh_575b427e-3678-4c6e-a6a6-609631a84f8d } Provisioning: External provisioner is provisioning volume for claim "provisioning-4849/aws9vgpn"
Sep 26 07:45:02.676: INFO: At 2021-09-26 07:38:20 +0000 UTC - event for aws9vgpn: {ebs.csi.aws.com_ebs-csi-controller-564bc97466-6chfh_575b427e-3678-4c6e-a6a6-609631a84f8d } ProvisioningSucceeded: Successfully provisioned volume pvc-e11c91b6-5a5f-4b6d-b7ff-8615f46f5beb
Sep 26 07:45:02.676: INFO: At 2021-09-26 07:38:20 +0000 UTC - event for pod-subpath-test-dynamicpv-nrld: {default-scheduler } Scheduled: Successfully assigned provisioning-4849/pod-subpath-test-dynamicpv-nrld to ip-172-20-35-50.us-west-1.compute.internal
Sep 26 07:45:02.676: INFO: At 2021-09-26 07:38:36 +0000 UTC - event for pod-subpath-test-dynamicpv-nrld: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-e11c91b6-5a5f-4b6d-b7ff-8615f46f5beb" : rpc error: code = Internal desc = Could not attach volume "vol-02cb60e57b3e93629" to node "i-0c0aac37066181110": attachment of disk "vol-02cb60e57b3e93629" failed, expected device to be attached but was attaching
Sep 26 07:45:02.676: INFO: At 2021-09-26 07:40:23 +0000 UTC - event for pod-subpath-test-dynamicpv-nrld: {kubelet ip-172-20-35-50.us-west-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[test-volume], unattached volumes=[test-volume liveness-probe-volume kube-api-access-qsjwq]: timed out waiting for the condition
Sep 26 07:45:02.676: INFO: At 2021-09-26 07:44:55 +0000 UTC - event for pod-subpath-test-dynamicpv-nrld: {kubelet ip-172-20-35-50.us-west-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[test-volume], unattached volumes=[kube-api-access-qsjwq test-volume liveness-probe-volume]: timed out waiting for the condition
Sep 26 07:45:02.727: INFO: POD  NODE  PHASE  GRACE  CONDITIONS
Sep 26 07:45:02.727: INFO: 
Sep 26 07:45:02.779: INFO: 
Logging node info for node ip-172-20-35-50.us-west-1.compute.internal
... skipping 156 lines ...
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should be able to unmount after the subpath directory is deleted [LinuxOnly] [It]
      /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:444

      while waiting for pod to be running
      Unexpected error:
          <*errors.errorString | 0xc0002240e0>: {
              s: "timed out waiting for the condition",
          }
          timed out waiting for the condition
      occurred

... skipping 14 lines ...
Sep 26 07:33:38.739: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-3118-e2e-sc82c4v      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-3118    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-3118-e2e-sc82c4v,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-3118    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-3118-e2e-sc82c4v,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-3118    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-3118-e2e-sc82c4v,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-3118-e2e-sc82c4v    857ba110-e62d-41c3-a77c-1fc551800be8 5203 0 2021-09-26 07:33:38 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-09-26 07:33:38 +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-lzg59 pvc- provisioning-3118  12353bb7-1ad5-47e9-9850-10111886c762 5208 0 2021-09-26 07:33:38 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-09-26 07:33:38 +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-3118-e2e-sc82c4v,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-2990c68d-248f-4f27-9719-9bdcf24dfed6 in namespace provisioning-3118
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Sep 26 07:33:53.347: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-qnn44" in namespace "provisioning-3118" to be "Succeeded or Failed"
Sep 26 07:33:53.396: INFO: Pod "pvc-volume-tester-writer-qnn44": Phase="Pending", Reason="", readiness=false. Elapsed: 49.363887ms
Sep 26 07:33:55.446: INFO: Pod "pvc-volume-tester-writer-qnn44": Phase="Pending", Reason="", readiness=false. Elapsed: 2.099266319s
Sep 26 07:33:57.496: INFO: Pod "pvc-volume-tester-writer-qnn44": Phase="Pending", Reason="", readiness=false. Elapsed: 4.149915058s
Sep 26 07:33:59.547: INFO: Pod "pvc-volume-tester-writer-qnn44": Phase="Pending", Reason="", readiness=false. Elapsed: 6.200888871s
Sep 26 07:34:01.902: INFO: Pod "pvc-volume-tester-writer-qnn44": Phase="Pending", Reason="", readiness=false. Elapsed: 8.555306439s
Sep 26 07:34:03.952: INFO: Pod "pvc-volume-tester-writer-qnn44": Phase="Pending", Reason="", readiness=false. Elapsed: 10.605106967s
... skipping 7 lines ...
Sep 26 07:34:20.368: INFO: Pod "pvc-volume-tester-writer-qnn44": Phase="Pending", Reason="", readiness=false. Elapsed: 27.021096227s
Sep 26 07:34:22.418: INFO: Pod "pvc-volume-tester-writer-qnn44": Phase="Pending", Reason="", readiness=false. Elapsed: 29.071430646s
Sep 26 07:34:24.470: INFO: Pod "pvc-volume-tester-writer-qnn44": Phase="Pending", Reason="", readiness=false. Elapsed: 31.123189575s
Sep 26 07:34:26.521: INFO: Pod "pvc-volume-tester-writer-qnn44": Phase="Pending", Reason="", readiness=false. Elapsed: 33.174858611s
Sep 26 07:34:28.572: INFO: Pod "pvc-volume-tester-writer-qnn44": Phase="Succeeded", Reason="", readiness=false. Elapsed: 35.22568197s
STEP: Saw pod success
Sep 26 07:34:28.572: INFO: Pod "pvc-volume-tester-writer-qnn44" satisfied condition "Succeeded or Failed"
Sep 26 07:34:28.676: INFO: Pod pvc-volume-tester-writer-qnn44 has the following logs: 
Sep 26 07:34:28.676: INFO: Deleting pod "pvc-volume-tester-writer-qnn44" in namespace "provisioning-3118"
Sep 26 07:34:28.778: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-qnn44" 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-35-50.us-west-1.compute.internal"
Sep 26 07:34:28.982: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-zj4st" in namespace "provisioning-3118" to be "Succeeded or Failed"
Sep 26 07:34:29.031: INFO: Pod "pvc-volume-tester-reader-zj4st": Phase="Pending", Reason="", readiness=false. Elapsed: 49.391919ms
Sep 26 07:34:31.082: INFO: Pod "pvc-volume-tester-reader-zj4st": Phase="Pending", Reason="", readiness=false. Elapsed: 2.10037621s
Sep 26 07:34:33.134: INFO: Pod "pvc-volume-tester-reader-zj4st": Phase="Pending", Reason="", readiness=false. Elapsed: 4.152492608s
Sep 26 07:34:35.185: INFO: Pod "pvc-volume-tester-reader-zj4st": Phase="Pending", Reason="", readiness=false. Elapsed: 6.2032862s
Sep 26 07:34:37.236: INFO: Pod "pvc-volume-tester-reader-zj4st": Phase="Pending", Reason="", readiness=false. Elapsed: 8.254010188s
Sep 26 07:34:39.286: INFO: Pod "pvc-volume-tester-reader-zj4st": Phase="Pending", Reason="", readiness=false. Elapsed: 10.304616924s
... skipping 446 lines ...
Sep 26 07:49:29.680: INFO: At 2021-09-26 07:33:43 +0000 UTC - event for pod-2990c68d-248f-4f27-9719-9bdcf24dfed6: {default-scheduler } Scheduled: Successfully assigned provisioning-3118/pod-2990c68d-248f-4f27-9719-9bdcf24dfed6 to ip-172-20-37-99.us-west-1.compute.internal
Sep 26 07:49:29.680: INFO: At 2021-09-26 07:33:46 +0000 UTC - event for pod-2990c68d-248f-4f27-9719-9bdcf24dfed6: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-12353bb7-1ad5-47e9-9850-10111886c762" 
Sep 26 07:49:29.680: INFO: At 2021-09-26 07:33:52 +0000 UTC - event for pod-2990c68d-248f-4f27-9719-9bdcf24dfed6: {kubelet ip-172-20-37-99.us-west-1.compute.internal} Started: Started container write-pod
Sep 26 07:49:29.681: INFO: At 2021-09-26 07:33:52 +0000 UTC - event for pod-2990c68d-248f-4f27-9719-9bdcf24dfed6: {kubelet ip-172-20-37-99.us-west-1.compute.internal} Created: Created container write-pod
Sep 26 07:49:29.681: INFO: At 2021-09-26 07:33:52 +0000 UTC - event for pod-2990c68d-248f-4f27-9719-9bdcf24dfed6: {kubelet ip-172-20-37-99.us-west-1.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" already present on machine
Sep 26 07:49:29.681: INFO: At 2021-09-26 07:33:53 +0000 UTC - event for pvc-volume-tester-writer-qnn44: {default-scheduler } Scheduled: Successfully assigned provisioning-3118/pvc-volume-tester-writer-qnn44 to ip-172-20-35-50.us-west-1.compute.internal
Sep 26 07:49:29.681: INFO: At 2021-09-26 07:33:53 +0000 UTC - event for pvc-volume-tester-writer-qnn44: {attachdetach-controller } FailedAttachVolume: Multi-Attach error for volume "pvc-12353bb7-1ad5-47e9-9850-10111886c762" Volume is already used by pod(s) pod-2990c68d-248f-4f27-9719-9bdcf24dfed6
Sep 26 07:49:29.681: INFO: At 2021-09-26 07:33:54 +0000 UTC - event for pod-2990c68d-248f-4f27-9719-9bdcf24dfed6: {kubelet ip-172-20-37-99.us-west-1.compute.internal} Killing: Stopping container write-pod
Sep 26 07:49:29.681: INFO: At 2021-09-26 07:34:16 +0000 UTC - event for pvc-volume-tester-writer-qnn44: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-12353bb7-1ad5-47e9-9850-10111886c762" 
Sep 26 07:49:29.681: INFO: At 2021-09-26 07:34:25 +0000 UTC - event for pvc-volume-tester-writer-qnn44: {kubelet ip-172-20-35-50.us-west-1.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" already present on machine
Sep 26 07:49:29.681: INFO: At 2021-09-26 07:34:25 +0000 UTC - event for pvc-volume-tester-writer-qnn44: {kubelet ip-172-20-35-50.us-west-1.compute.internal} Created: Created container volume-tester
Sep 26 07:49:29.681: INFO: At 2021-09-26 07:34:26 +0000 UTC - event for pvc-volume-tester-writer-qnn44: {kubelet ip-172-20-35-50.us-west-1.compute.internal} Started: Started container volume-tester
Sep 26 07:49:29.681: INFO: At 2021-09-26 07:34:27 +0000 UTC - event for pvc-volume-tester-writer-qnn44: {kubelet ip-172-20-35-50.us-west-1.compute.internal} FailedMount: MountVolume.SetUp failed for volume "kube-api-access-lxd77" : object "provisioning-3118"/"kube-root-ca.crt" not registered
Sep 26 07:49:29.681: INFO: At 2021-09-26 07:34:28 +0000 UTC - event for pvc-volume-tester-reader-zj4st: {default-scheduler } FailedScheduling: 0/5 nodes are available: 1 node(s) exceed max volume count, 1 node(s) had taint {node-role.kubernetes.io/master: }, that the pod didn't tolerate, 3 node(s) didn't match Pod's node affinity/selector.
Sep 26 07:49:29.681: INFO: At 2021-09-26 07:49:29 +0000 UTC - event for pvc-volume-tester-reader-zj4st: {default-scheduler } FailedScheduling: skip schedule deleting pod: provisioning-3118/pvc-volume-tester-reader-zj4st
Sep 26 07:49:29.754: INFO: POD  NODE  PHASE  GRACE  CONDITIONS
Sep 26 07:49:29.754: INFO: 
Sep 26 07:49:29.999: INFO: 
Logging node info for node ip-172-20-35-50.us-west-1.compute.internal
... skipping 153 lines ...
/tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] provisioning
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should provision storage with mount options [It]
    /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/provisioning.go:179

    Unexpected error:
        <*errors.errorString | 0xc0002408b0>: {
            s: "Gave up after waiting 15m0s for pod \"pvc-volume-tester-reader-zj4st\" to be \"Succeeded or Failed\"",
        }
        Gave up after waiting 15m0s for pod "pvc-volume-tester-reader-zj4st" to be "Succeeded or Failed"
    occurred

    /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/provisioning.go:683
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeLimits
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
... skipping 194 lines ...
Sep 26 08:24:42.949: INFO: At 2021-09-26 07:34:45 +0000 UTC - event for pod-c001365a-5bb8-4a71-9d5e-db32d69827ad: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-802420d0-3a40-42eb-9c07-d6206fef6a46" 
Sep 26 08:24:42.949: INFO: At 2021-09-26 07:34:46 +0000 UTC - event for pod-c001365a-5bb8-4a71-9d5e-db32d69827ad: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-fda79e93-b3ad-438f-8802-cd5063f7aa10" 
Sep 26 08:24:42.949: INFO: At 2021-09-26 07:34:47 +0000 UTC - event for pod-c001365a-5bb8-4a71-9d5e-db32d69827ad: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-7bf095d7-a19a-46e1-93c2-5b7dbe8efbd0" 
Sep 26 08:24:42.949: INFO: At 2021-09-26 07:34:47 +0000 UTC - event for pod-c001365a-5bb8-4a71-9d5e-db32d69827ad: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-cf9e7906-a219-4c28-9b27-98d838789245" 
Sep 26 08:24:42.949: INFO: At 2021-09-26 07:34:48 +0000 UTC - event for pod-c001365a-5bb8-4a71-9d5e-db32d69827ad: {attachdetach-controller } SuccessfulAttachVolume: (combined from similar events): AttachVolume.Attach succeeded for volume "pvc-84e4bcfa-a510-49e9-8406-223a6aec2cb6" 
Sep 26 08:24:42.949: INFO: At 2021-09-26 07:34:48 +0000 UTC - event for pod-c001365a-5bb8-4a71-9d5e-db32d69827ad: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-2e71ff24-cf42-47ec-8820-fcfcac5c5655" 
Sep 26 08:24:42.949: INFO: At 2021-09-26 07:35:08 +0000 UTC - event for pod-c001365a-5bb8-4a71-9d5e-db32d69827ad: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-6ca97aeb-e096-41b4-92d5-d8fd904376eb" : rpc error: code = DeadlineExceeded desc = context deadline exceeded
Sep 26 08:24:42.949: INFO: At 2021-09-26 07:35:08 +0000 UTC - event for pod-c001365a-5bb8-4a71-9d5e-db32d69827ad: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-5dbf019e-f155-45b6-8204-3f9d79470bf1" : rpc error: code = DeadlineExceeded desc = context deadline exceeded
Sep 26 08:24:42.949: INFO: At 2021-09-26 07:35:08 +0000 UTC - event for pod-c001365a-5bb8-4a71-9d5e-db32d69827ad: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-08e4d756-7c2f-499d-9ee5-315c738cf07d" : rpc error: code = DeadlineExceeded desc = context deadline exceeded
Sep 26 08:24:42.949: INFO: At 2021-09-26 07:35:09 +0000 UTC - event for pod-c001365a-5bb8-4a71-9d5e-db32d69827ad: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-73bf0f0e-3ac7-4060-ab6c-8fb6a474ba04" : rpc error: code = DeadlineExceeded desc = context deadline exceeded
Sep 26 08:24:42.949: INFO: At 2021-09-26 07:35:15 +0000 UTC - event for pod-c001365a-5bb8-4a71-9d5e-db32d69827ad: {attachdetach-controller } FailedAttachVolume: (combined from similar events): AttachVolume.Attach failed for volume "pvc-bba38472-0941-486e-a07e-581d2070e511" : rpc error: code = Internal desc = Could not attach volume "vol-04cf9fc2a7ebb88b9" to node "i-0c0aac37066181110": attachment of disk "vol-04cf9fc2a7ebb88b9" failed, expected device to be attached but was attaching
Sep 26 08:24:42.949: INFO: At 2021-09-26 07:36:43 +0000 UTC - event for pod-c001365a-5bb8-4a71-9d5e-db32d69827ad: {kubelet ip-172-20-35-50.us-west-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume1 volume15 volume37 volume22 volume33 volume21 volume14 volume7 volume17 volume26 volume8 volume12 volume18 volume29 volume32 volume10 volume16 volume27], unattached volumes=[volume1 volume34 volume15 volume5 volume3 volume37 volume23 volume11 volume22 volume33 volume21 volume14 volume7 volume17 volume24 volume26 volume39 volume8 volume38 volume19 volume25 volume12 volume2 volume30 volume4 volume9 volume35 volume18 volume36 volume28 volume13 volume29 volume6 volume31 volume32 volume10 volume20 volume16 volume27 kube-api-access-pdfg9]: timed out waiting for the condition
Sep 26 08:24:42.949: INFO: At 2021-09-26 07:39:01 +0000 UTC - event for pod-c001365a-5bb8-4a71-9d5e-db32d69827ad: {kubelet ip-172-20-35-50.us-west-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume27 volume14 volume32 volume21 volume10 volume12 volume8 volume37 volume16 volume1 volume29 volume15 volume17 volume7 volume26 volume33 volume18 volume22], unattached volumes=[volume30 volume20 volume23 volume27 volume4 volume19 volume14 volume32 kube-api-access-pdfg9 volume11 volume21 volume10 volume12 volume8 volume37 volume38 volume16 volume31 volume1 volume29 volume3 volume34 volume2 volume15 volume6 volume5 volume13 volume17 volume7 volume28 volume24 volume39 volume26 volume9 volume33 volume36 volume18 volume22 volume35 volume25]: timed out waiting for the condition
Sep 26 08:24:42.949: INFO: At 2021-09-26 07:41:18 +0000 UTC - event for pod-c001365a-5bb8-4a71-9d5e-db32d69827ad: {kubelet ip-172-20-35-50.us-west-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume21 volume32 volume26 volume33 volume8 volume10 volume22 volume14 volume29 volume1 volume18 volume27 volume37 volume17 volume12], unattached volumes=[volume25 volume6 volume11 volume21 volume3 volume32 kube-api-access-pdfg9 volume26 volume24 volume2 volume33 volume31 volume16 volume35 volume8 volume7 volume20 volume19 volume38 volume10 volume13 volume36 volume22 volume23 volume14 volume29 volume1 volume28 volume9 volume18 volume15 volume27 volume30 volume37 volume4 volume5 volume39 volume17 volume34 volume12]: timed out waiting for the condition
Sep 26 08:24:42.949: INFO: At 2021-09-26 07:43:33 +0000 UTC - event for pod-c001365a-5bb8-4a71-9d5e-db32d69827ad: {kubelet ip-172-20-35-50.us-west-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume18 volume14 volume12 volume17 volume21 volume33 volume26 volume10 volume1 volume27 volume22 volume29 volume37 volume8], unattached volumes=[volume3 volume19 volume18 volume14 volume5 volume6 volume23 volume28 volume12 volume25 volume16 volume4 volume17 volume21 volume20 volume32 volume30 volume24 volume31 volume33 volume38 volume26 volume34 volume36 volume10 volume15 volume2 volume13 volume35 volume1 kube-api-access-pdfg9 volume27 volume9 volume22 volume29 volume39 volume11 volume7 volume37 volume8]: timed out waiting for the condition
Sep 26 08:24:42.949: INFO: At 2021-09-26 07:45:51 +0000 UTC - event for pod-c001365a-5bb8-4a71-9d5e-db32d69827ad: {kubelet ip-172-20-35-50.us-west-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume33 volume27 volume8 volume18 volume10 volume21 volume1 volume37 volume17 volume26 volume22 volume29 volume14], unattached volumes=[volume23 volume33 volume32 volume28 volume27 volume15 volume7 volume16 volume8 volume36 volume18 volume10 volume11 volume19 volume21 volume39 volume3 kube-api-access-pdfg9 volume30 volume31 volume1 volume37 volume35 volume4 volume13 volume6 volume17 volume2 volume38 volume20 volume24 volume34 volume12 volume26 volume22 volume29 volume9 volume14 volume5 volume25]: timed out waiting for the condition
Sep 26 08:24:42.949: INFO: At 2021-09-26 07:48:08 +0000 UTC - event for pod-c001365a-5bb8-4a71-9d5e-db32d69827ad: {kubelet ip-172-20-35-50.us-west-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume33 volume14 volume29 volume1 volume26 volume27 volume8 volume22 volume37 volume21 volume10 volume17 volume18], unattached volumes=[volume33 volume4 volume14 volume23 volume7 volume5 volume15 volume24 volume2 volume20 volume25 kube-api-access-pdfg9 volume29 volume1 volume3 volume28 volume34 volume26 volume39 volume30 volume27 volume32 volume8 volume13 volume36 volume31 volume19 volume11 volume6 volume16 volume22 volume37 volume9 volume21 volume38 volume10 volume12 volume17 volume35 volume18]: timed out waiting for the condition
... skipping 162 lines ...
/tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (filesystem volmode)] volumeLimits
  /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should support volume limits [Serial] [It]
    /tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumelimits.go:123

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

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


Summarizing 4 Failures:

[Fail] [ebs-csi-migration] EBS CSI Migration [Driver: aws] [Testpattern: Inline-volume (ext4)] volumes [It] should store data 
/tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/framework/volume/fixtures.go:505

[Fail] [ebs-csi-migration] EBS CSI Migration [Driver: aws] [Testpattern: Dynamic PV (default fs)] subPath [It] should be able to unmount after the subpath directory is deleted [LinuxOnly] 
/tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:464

[Fail] External Storage [Driver: ebs.csi.aws.com] [Testpattern: Dynamic PV (default fs)] provisioning [It] should provision storage with mount options 
/tmp/kops.h0A0b3MTk/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/provisioning.go:683

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

Ran 140 of 485 Specs in 3152.332 seconds
FAIL! -- 136 Passed | 4 Failed | 0 Pending | 345 Skipped


Ginkgo ran 1 suite in 53m42.060394984s
Test Suite Failed
+ kops-finish
+ kubetest2 kops -v=2 --cloud-provider=aws --cluster-name=e2e-c3f2775103-c95b4.test-cncf-aws.k8s.io --kops-root=/home/prow/go/src/k8s.io/kops --admin-access= --env=KOPS_FEATURE_FLAGS=SpecOverrideFlag --kops-binary-path=/home/prow/go/src/k8s.io/kops/.bazelbuild/dist/linux/amd64/kops --down
I0926 08:24:45.708292   27353 app.go:59] RunDir for this run: "/logs/artifacts/c84926a0-1e99-11ec-a3b0-9242b45c1669"
I0926 08:24:45.709395   27353 app.go:90] ID for this run: "c84926a0-1e99-11ec-a3b0-9242b45c1669"
I0926 08:24:45.749126   27353 dumplogs.go:40] /home/prow/go/src/k8s.io/kops/.bazelbuild/dist/linux/amd64/kops toolbox dump --name e2e-c3f2775103-c95b4.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ubuntu
I0926 08:24:45.770756   27364 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
... skipping 2548 lines ...