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-27 07:36
Elapsed1h13m
Revision77b92960f75e2c807b849d370d6fee7aef74265e
Refs 12419

No Test Failures!


Error lines from build-log.txt

... skipping 570 lines ...
I0927 07:40:46.271077   12446 app.go:90] ID for this run: "923bfa1a-1f65-11ec-aef2-36f71ef8a223"
I0927 07:40:46.291704   12446 up.go:43] Cleaning up any leaked resources from previous cluster
I0927 07:40:46.291766   12446 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
I0927 07:40:46.313360   12457 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0927 07:40:46.313443   12457 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I0927 07:40:46.313449   12457 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Error: Cluster.kops.k8s.io "e2e-c3f2775103-c95b4.test-cncf-aws.k8s.io" not found
W0927 07:40:46.792154   12446 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0927 07:40:46.792264   12446 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
I0927 07:40:46.809402   12467 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0927 07:40:46.809494   12467 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I0927 07:40:46.809499   12467 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
I0927 07:40:47.262368   12446 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/09/27 07:40:47 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
I0927 07:40:47.269554   12446 http.go:37] curl https://ip.jsb.workers.dev
I0927 07:40:47.365794   12446 up.go:144] /home/prow/go/src/k8s.io/kops/.bazelbuild/dist/linux/amd64/kops create cluster --name e2e-c3f2775103-c95b4.test-cncf-aws.k8s.io --cloud aws --kubernetes-version 1.22.1 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --networking calico --override=cluster.spec.cloudConfig.awsEBSCSIDriver.enabled=true --override=cluster.spec.snapshotController.enabled=true --override=cluster.spec.certManager.enabled=true --admin-access 34.69.131.253/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones eu-west-3a --master-size c5.large
I0927 07:40:47.382892   12477 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0927 07:40:47.383109   12477 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I0927 07:40:47.383150   12477 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0927 07:40:47.406702   12477 create_cluster.go:838] Using SSH public key: /etc/aws-ssh/aws-ssh-public
... skipping 33 lines ...
I0927 07:41:14.256450   12446 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
I0927 07:41:14.273214   12499 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0927 07:41:14.273337   12499 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I0927 07:41:14.273342   12499 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-c3f2775103-c95b4.test-cncf-aws.k8s.io

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

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

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
W0927 07:41:45.574372   12499 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0927 07:41:55.604531   12499 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0927 07:42:05.636113   12499 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0927 07:42:15.676522   12499 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0927 07:42:25.704579   12499 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0927 07:42:35.747139   12499 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0927 07:42:45.789353   12499 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0927 07:42:55.830696   12499 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0927 07:43:05.874680   12499 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0927 07:43:15.904286   12499 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0927 07:43:25.935049   12499 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0927 07:43:35.968178   12499 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0927 07:43:45.996784   12499 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0927 07:43:56.024248   12499 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0927 07:44:06.049615   12499 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0927 07:44:16.084655   12499 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0927 07:44:26.128614   12499 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0927 07:44:36.156773   12499 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0927 07:44:46.189088   12499 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0927 07:44:56.216448   12499 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 10 lines ...
Node	ip-172-20-41-224.eu-west-3.compute.internal	master "ip-172-20-41-224.eu-west-3.compute.internal" is missing kube-controller-manager pod
Pod	kube-system/coredns-5dc785954d-m88xx		system-cluster-critical pod "coredns-5dc785954d-m88xx" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-899nd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-899nd" is pending
Pod	kube-system/ebs-csi-controller-564bc97466-qf4v9	system-cluster-critical pod "ebs-csi-controller-564bc97466-qf4v9" is pending
Pod	kube-system/ebs-csi-node-ttt5p			system-node-critical pod "ebs-csi-node-ttt5p" is pending

Validation Failed
W0927 07:45:08.789748   12499 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 15 lines ...
Pod	kube-system/coredns-5dc785954d-m88xx		system-cluster-critical pod "coredns-5dc785954d-m88xx" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-899nd	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-899nd" is pending
Pod	kube-system/ebs-csi-controller-564bc97466-qf4v9	system-cluster-critical pod "ebs-csi-controller-564bc97466-qf4v9" is pending
Pod	kube-system/ebs-csi-node-8bblp			system-node-critical pod "ebs-csi-node-8bblp" is pending
Pod	kube-system/ebs-csi-node-hhpk2			system-node-critical pod "ebs-csi-node-hhpk2" is pending

Validation Failed
W0927 07:45:20.702866   12499 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 16 lines ...
Pod	kube-system/coredns-autoscaler-84d4cfd89c-899nd					system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-899nd" is pending
Pod	kube-system/ebs-csi-node-8bblp							system-node-critical pod "ebs-csi-node-8bblp" is pending
Pod	kube-system/ebs-csi-node-hhpk2							system-node-critical pod "ebs-csi-node-hhpk2" is pending
Pod	kube-system/ebs-csi-node-r2zrc							system-node-critical pod "ebs-csi-node-r2zrc" is pending
Pod	kube-system/kube-controller-manager-ip-172-20-41-224.eu-west-3.compute.internal	system-cluster-critical pod "kube-controller-manager-ip-172-20-41-224.eu-west-3.compute.internal" is pending

Validation Failed
W0927 07:45:32.605372   12499 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-8bblp							system-node-critical pod "ebs-csi-node-8bblp" is pending
Pod	kube-system/ebs-csi-node-hhpk2							system-node-critical pod "ebs-csi-node-hhpk2" is pending
Pod	kube-system/ebs-csi-node-r2zrc							system-node-critical pod "ebs-csi-node-r2zrc" is pending
Pod	kube-system/ebs-csi-node-wpxz9							system-node-critical pod "ebs-csi-node-wpxz9" is pending
Pod	kube-system/etcd-manager-main-ip-172-20-41-224.eu-west-3.compute.internal	system-cluster-critical pod "etcd-manager-main-ip-172-20-41-224.eu-west-3.compute.internal" is pending

Validation Failed
W0927 07:45:44.533737   12499 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/calico-node-vlr9v						system-node-critical pod "calico-node-vlr9v" is pending
Pod	kube-system/ebs-csi-node-wpxz9						system-node-critical pod "ebs-csi-node-wpxz9" is pending
Pod	kube-system/kube-proxy-ip-172-20-40-65.eu-west-3.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-40-65.eu-west-3.compute.internal" is pending

Validation Failed
W0927 07:45:56.535670   12499 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/calico-node-vlr9v						system-node-critical pod "calico-node-vlr9v" is not ready (calico-node)
Pod	kube-system/ebs-csi-node-wpxz9						system-node-critical pod "ebs-csi-node-wpxz9" is pending
Pod	kube-system/kube-proxy-ip-172-20-56-87.eu-west-3.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-56-87.eu-west-3.compute.internal" is pending

Validation Failed
W0927 07:46:08.486542   12499 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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

      Distro debian doesn't support ntfs -- skipping

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

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 407 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.8TytcAgTJ/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.8TytcAgTJ/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.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 746 lines ...
STEP: Creating a kubernetes client
Sep 27 07:49:22.513: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename volumemode
W0927 07:49:23.193711   25047 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Sep 27 07:49:23.193: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail to use a volume in a pod with mismatched mode [Slow]
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Sep 27 07:49:23.401: INFO: Creating resource for dynamic PV
Sep 27 07:49:23.402: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-3744-e2e-sc86xls
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Sep 27 07:49:28.140: INFO: Deleting pod "pod-95f8ed1c-77e9-4da3-907a-bb9f89f0befd" in namespace "volumemode-3744"
Sep 27 07:49:28.248: INFO: Wait up to 5m0s for pod "pod-95f8ed1c-77e9-4da3-907a-bb9f89f0befd" to be fully deleted
STEP: Deleting pvc
Sep 27 07:49:30.664: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comrsdf2"
Sep 27 07:49:30.769: INFO: Waiting up to 5m0s for PersistentVolume pvc-a9a67925-e79c-4d7e-8e1b-0c2a306051b0 to get deleted
Sep 27 07:49:30.879: INFO: PersistentVolume pvc-a9a67925-e79c-4d7e-8e1b-0c2a306051b0 found and phase=Released (109.643885ms)
... skipping 9 lines ...

• [SLOW TEST:24.107 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.8TytcAgTJ/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.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [sig-storage] Volume Operations Storm [Feature:vsphere]
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 27 07:49:46.623: INFO: >>> kubeConfig: /root/.kube/config
... skipping 111 lines ...
Sep 27 07:49:49.579: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 36 lines ...
Sep 27 07:49:26.392: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-9737-e2e-scv4vc7
STEP: creating a claim
Sep 27 07:49:26.497: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Sep 27 07:49:26.707: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Sep 27 07:49:26.920: INFO: Error updating pvc ebs.csi.aws.commrpxx: PersistentVolumeClaim "ebs.csi.aws.commrpxx" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-9737-e2e-scv4vc7",
  	... // 3 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.8TytcAgTJ/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.8TytcAgTJ/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.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 30 lines ...
Sep 27 07:49:27.143: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4801-e2e-sctvhc6
STEP: creating a claim
Sep 27 07:49:27.252: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-svgp
STEP: Creating a pod to test subpath
Sep 27 07:49:27.609: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-svgp" in namespace "provisioning-4801" to be "Succeeded or Failed"
Sep 27 07:49:27.713: INFO: Pod "pod-subpath-test-dynamicpv-svgp": Phase="Pending", Reason="", readiness=false. Elapsed: 104.613769ms
Sep 27 07:49:29.818: INFO: Pod "pod-subpath-test-dynamicpv-svgp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.209325791s
Sep 27 07:49:31.922: INFO: Pod "pod-subpath-test-dynamicpv-svgp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.313708423s
Sep 27 07:49:34.027: INFO: Pod "pod-subpath-test-dynamicpv-svgp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.418409911s
Sep 27 07:49:36.133: INFO: Pod "pod-subpath-test-dynamicpv-svgp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.524204404s
Sep 27 07:49:38.238: INFO: Pod "pod-subpath-test-dynamicpv-svgp": Phase="Pending", Reason="", readiness=false. Elapsed: 10.628963258s
Sep 27 07:49:40.342: INFO: Pod "pod-subpath-test-dynamicpv-svgp": Phase="Pending", Reason="", readiness=false. Elapsed: 12.733160801s
Sep 27 07:49:42.446: INFO: Pod "pod-subpath-test-dynamicpv-svgp": Phase="Pending", Reason="", readiness=false. Elapsed: 14.837538181s
Sep 27 07:49:44.553: INFO: Pod "pod-subpath-test-dynamicpv-svgp": Phase="Pending", Reason="", readiness=false. Elapsed: 16.944044324s
Sep 27 07:49:46.658: INFO: Pod "pod-subpath-test-dynamicpv-svgp": Phase="Pending", Reason="", readiness=false. Elapsed: 19.049800535s
Sep 27 07:49:48.767: INFO: Pod "pod-subpath-test-dynamicpv-svgp": Phase="Pending", Reason="", readiness=false. Elapsed: 21.158729627s
Sep 27 07:49:50.873: INFO: Pod "pod-subpath-test-dynamicpv-svgp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.264192858s
STEP: Saw pod success
Sep 27 07:49:50.873: INFO: Pod "pod-subpath-test-dynamicpv-svgp" satisfied condition "Succeeded or Failed"
Sep 27 07:49:50.977: INFO: Trying to get logs from node ip-172-20-54-99.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-svgp container test-container-volume-dynamicpv-svgp: <nil>
STEP: delete the pod
Sep 27 07:49:51.196: INFO: Waiting for pod pod-subpath-test-dynamicpv-svgp to disappear
Sep 27 07:49:51.300: INFO: Pod pod-subpath-test-dynamicpv-svgp no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-svgp
Sep 27 07:49:51.300: INFO: Deleting pod "pod-subpath-test-dynamicpv-svgp" in namespace "provisioning-4801"
... skipping 38 lines ...
Sep 27 07:49:23.637: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3488b9kjn
STEP: creating a claim
Sep 27 07:49:23.742: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-rgkm
STEP: Creating a pod to test subpath
Sep 27 07:49:24.076: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-rgkm" in namespace "provisioning-3488" to be "Succeeded or Failed"
Sep 27 07:49:24.179: INFO: Pod "pod-subpath-test-dynamicpv-rgkm": Phase="Pending", Reason="", readiness=false. Elapsed: 102.995978ms
Sep 27 07:49:26.284: INFO: Pod "pod-subpath-test-dynamicpv-rgkm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.208035548s
Sep 27 07:49:28.388: INFO: Pod "pod-subpath-test-dynamicpv-rgkm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.312158786s
Sep 27 07:49:30.492: INFO: Pod "pod-subpath-test-dynamicpv-rgkm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.41567337s
Sep 27 07:49:32.596: INFO: Pod "pod-subpath-test-dynamicpv-rgkm": Phase="Pending", Reason="", readiness=false. Elapsed: 8.520139319s
Sep 27 07:49:34.700: INFO: Pod "pod-subpath-test-dynamicpv-rgkm": Phase="Pending", Reason="", readiness=false. Elapsed: 10.623482127s
Sep 27 07:49:36.803: INFO: Pod "pod-subpath-test-dynamicpv-rgkm": Phase="Pending", Reason="", readiness=false. Elapsed: 12.727122072s
Sep 27 07:49:38.906: INFO: Pod "pod-subpath-test-dynamicpv-rgkm": Phase="Pending", Reason="", readiness=false. Elapsed: 14.830246101s
Sep 27 07:49:41.011: INFO: Pod "pod-subpath-test-dynamicpv-rgkm": Phase="Pending", Reason="", readiness=false. Elapsed: 16.93451406s
Sep 27 07:49:43.115: INFO: Pod "pod-subpath-test-dynamicpv-rgkm": Phase="Pending", Reason="", readiness=false. Elapsed: 19.038678307s
Sep 27 07:49:45.220: INFO: Pod "pod-subpath-test-dynamicpv-rgkm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.143687476s
STEP: Saw pod success
Sep 27 07:49:45.220: INFO: Pod "pod-subpath-test-dynamicpv-rgkm" satisfied condition "Succeeded or Failed"
Sep 27 07:49:45.326: INFO: Trying to get logs from node ip-172-20-54-99.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-rgkm container test-container-subpath-dynamicpv-rgkm: <nil>
STEP: delete the pod
Sep 27 07:49:46.093: INFO: Waiting for pod pod-subpath-test-dynamicpv-rgkm to disappear
Sep 27 07:49:46.196: INFO: Pod pod-subpath-test-dynamicpv-rgkm no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-rgkm
Sep 27 07:49:46.196: INFO: Deleting pod "pod-subpath-test-dynamicpv-rgkm" in namespace "provisioning-3488"
... skipping 142 lines ...
Sep 27 07:49:26.294: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3128-e2e-scsmjs4
STEP: creating a claim
Sep 27 07:49:26.399: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-c7l8
STEP: Creating a pod to test subpath
Sep 27 07:49:26.714: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-c7l8" in namespace "provisioning-3128" to be "Succeeded or Failed"
Sep 27 07:49:26.818: INFO: Pod "pod-subpath-test-dynamicpv-c7l8": Phase="Pending", Reason="", readiness=false. Elapsed: 103.894694ms
Sep 27 07:49:28.926: INFO: Pod "pod-subpath-test-dynamicpv-c7l8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.211953859s
Sep 27 07:49:31.031: INFO: Pod "pod-subpath-test-dynamicpv-c7l8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.317469974s
Sep 27 07:49:33.137: INFO: Pod "pod-subpath-test-dynamicpv-c7l8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.422772178s
Sep 27 07:49:35.242: INFO: Pod "pod-subpath-test-dynamicpv-c7l8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.528324449s
Sep 27 07:49:37.352: INFO: Pod "pod-subpath-test-dynamicpv-c7l8": Phase="Pending", Reason="", readiness=false. Elapsed: 10.638399816s
... skipping 4 lines ...
Sep 27 07:49:47.877: INFO: Pod "pod-subpath-test-dynamicpv-c7l8": Phase="Pending", Reason="", readiness=false. Elapsed: 21.162826747s
Sep 27 07:49:49.981: INFO: Pod "pod-subpath-test-dynamicpv-c7l8": Phase="Pending", Reason="", readiness=false. Elapsed: 23.267105445s
Sep 27 07:49:52.086: INFO: Pod "pod-subpath-test-dynamicpv-c7l8": Phase="Pending", Reason="", readiness=false. Elapsed: 25.371979742s
Sep 27 07:49:54.191: INFO: Pod "pod-subpath-test-dynamicpv-c7l8": Phase="Pending", Reason="", readiness=false. Elapsed: 27.477176404s
Sep 27 07:49:56.296: INFO: Pod "pod-subpath-test-dynamicpv-c7l8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 29.582122791s
STEP: Saw pod success
Sep 27 07:49:56.296: INFO: Pod "pod-subpath-test-dynamicpv-c7l8" satisfied condition "Succeeded or Failed"
Sep 27 07:49:56.400: INFO: Trying to get logs from node ip-172-20-55-93.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-c7l8 container test-container-subpath-dynamicpv-c7l8: <nil>
STEP: delete the pod
Sep 27 07:49:56.625: INFO: Waiting for pod pod-subpath-test-dynamicpv-c7l8 to disappear
Sep 27 07:49:56.728: INFO: Pod pod-subpath-test-dynamicpv-c7l8 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-c7l8
Sep 27 07:49:56.728: INFO: Deleting pod "pod-subpath-test-dynamicpv-c7l8" in namespace "provisioning-3128"
... skipping 63 lines ...
STEP: Deleting pod hostexec-ip-172-20-54-99.eu-west-3.compute.internal-wtf2j in namespace volumemode-4475
Sep 27 07:49:56.508: INFO: Deleting pod "pod-81afe456-2e79-4cc2-aa9a-a51f21b270c9" in namespace "volumemode-4475"
Sep 27 07:49:56.612: INFO: Wait up to 5m0s for pod "pod-81afe456-2e79-4cc2-aa9a-a51f21b270c9" to be fully deleted
STEP: Deleting pv and pvc
Sep 27 07:49:58.818: INFO: Deleting PersistentVolumeClaim "pvc-6gcrj"
Sep 27 07:49:58.924: INFO: Deleting PersistentVolume "aws-88d5b"
Sep 27 07:49:59.240: INFO: Couldn't delete PD "aws://eu-west-3a/vol-02392d04f6848a674", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02392d04f6848a674 is currently attached to i-03ec4335fb22bd051
	status code: 400, request id: 33c56506-edf5-40d5-b9b0-0466f0e214cc
Sep 27 07:50:04.801: INFO: Couldn't delete PD "aws://eu-west-3a/vol-02392d04f6848a674", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02392d04f6848a674 is currently attached to i-03ec4335fb22bd051
	status code: 400, request id: a6344d40-842b-44a8-9c97-20f270462586
Sep 27 07:50:10.382: INFO: Couldn't delete PD "aws://eu-west-3a/vol-02392d04f6848a674", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02392d04f6848a674 is currently attached to i-03ec4335fb22bd051
	status code: 400, request id: 635163e6-4a7a-40a8-964b-dc0417090d0a
Sep 27 07:50:15.938: INFO: Successfully deleted PD "aws://eu-west-3a/vol-02392d04f6848a674".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 27 07:50:15.938: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-4475" for this suite.
... skipping 53 lines ...
Sep 27 07:49:27.292: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4542bgnpg
STEP: creating a claim
Sep 27 07:49:27.407: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-mprq
STEP: Creating a pod to test multi_subpath
Sep 27 07:49:27.738: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-mprq" in namespace "provisioning-4542" to be "Succeeded or Failed"
Sep 27 07:49:27.846: INFO: Pod "pod-subpath-test-dynamicpv-mprq": Phase="Pending", Reason="", readiness=false. Elapsed: 108.298501ms
Sep 27 07:49:29.951: INFO: Pod "pod-subpath-test-dynamicpv-mprq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.213072788s
Sep 27 07:49:32.058: INFO: Pod "pod-subpath-test-dynamicpv-mprq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.320131995s
Sep 27 07:49:34.162: INFO: Pod "pod-subpath-test-dynamicpv-mprq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.423986553s
Sep 27 07:49:36.265: INFO: Pod "pod-subpath-test-dynamicpv-mprq": Phase="Pending", Reason="", readiness=false. Elapsed: 8.527481262s
Sep 27 07:49:38.368: INFO: Pod "pod-subpath-test-dynamicpv-mprq": Phase="Pending", Reason="", readiness=false. Elapsed: 10.630812036s
... skipping 4 lines ...
Sep 27 07:49:48.885: INFO: Pod "pod-subpath-test-dynamicpv-mprq": Phase="Pending", Reason="", readiness=false. Elapsed: 21.147859717s
Sep 27 07:49:50.991: INFO: Pod "pod-subpath-test-dynamicpv-mprq": Phase="Pending", Reason="", readiness=false. Elapsed: 23.253834611s
Sep 27 07:49:53.095: INFO: Pod "pod-subpath-test-dynamicpv-mprq": Phase="Pending", Reason="", readiness=false. Elapsed: 25.357172838s
Sep 27 07:49:55.198: INFO: Pod "pod-subpath-test-dynamicpv-mprq": Phase="Pending", Reason="", readiness=false. Elapsed: 27.460488852s
Sep 27 07:49:57.304: INFO: Pod "pod-subpath-test-dynamicpv-mprq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 29.566249919s
STEP: Saw pod success
Sep 27 07:49:57.304: INFO: Pod "pod-subpath-test-dynamicpv-mprq" satisfied condition "Succeeded or Failed"
Sep 27 07:49:57.408: INFO: Trying to get logs from node ip-172-20-56-87.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-mprq container test-container-subpath-dynamicpv-mprq: <nil>
STEP: delete the pod
Sep 27 07:49:57.624: INFO: Waiting for pod pod-subpath-test-dynamicpv-mprq to disappear
Sep 27 07:49:57.727: INFO: Pod pod-subpath-test-dynamicpv-mprq no longer exists
STEP: Deleting pod
Sep 27 07:49:57.727: INFO: Deleting pod "pod-subpath-test-dynamicpv-mprq" in namespace "provisioning-4542"
... skipping 37 lines ...
Sep 27 07:49:25.686: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5219-e2e-scwmkdq
STEP: creating a claim
Sep 27 07:49:25.790: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-ccnm
STEP: Creating a pod to test subpath
Sep 27 07:49:26.100: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-ccnm" in namespace "provisioning-5219" to be "Succeeded or Failed"
Sep 27 07:49:26.206: INFO: Pod "pod-subpath-test-dynamicpv-ccnm": Phase="Pending", Reason="", readiness=false. Elapsed: 106.62648ms
Sep 27 07:49:28.309: INFO: Pod "pod-subpath-test-dynamicpv-ccnm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.209010826s
Sep 27 07:49:30.411: INFO: Pod "pod-subpath-test-dynamicpv-ccnm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.311709862s
Sep 27 07:49:32.515: INFO: Pod "pod-subpath-test-dynamicpv-ccnm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.414936117s
Sep 27 07:49:34.617: INFO: Pod "pod-subpath-test-dynamicpv-ccnm": Phase="Pending", Reason="", readiness=false. Elapsed: 8.517904974s
Sep 27 07:49:36.721: INFO: Pod "pod-subpath-test-dynamicpv-ccnm": Phase="Pending", Reason="", readiness=false. Elapsed: 10.621052786s
Sep 27 07:49:38.823: INFO: Pod "pod-subpath-test-dynamicpv-ccnm": Phase="Pending", Reason="", readiness=false. Elapsed: 12.723491522s
Sep 27 07:49:40.929: INFO: Pod "pod-subpath-test-dynamicpv-ccnm": Phase="Pending", Reason="", readiness=false. Elapsed: 14.829739293s
Sep 27 07:49:43.033: INFO: Pod "pod-subpath-test-dynamicpv-ccnm": Phase="Pending", Reason="", readiness=false. Elapsed: 16.933906089s
Sep 27 07:49:45.136: INFO: Pod "pod-subpath-test-dynamicpv-ccnm": Phase="Pending", Reason="", readiness=false. Elapsed: 19.036010645s
Sep 27 07:49:47.244: INFO: Pod "pod-subpath-test-dynamicpv-ccnm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.144504364s
STEP: Saw pod success
Sep 27 07:49:47.244: INFO: Pod "pod-subpath-test-dynamicpv-ccnm" satisfied condition "Succeeded or Failed"
Sep 27 07:49:47.349: INFO: Trying to get logs from node ip-172-20-56-87.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-ccnm container test-container-subpath-dynamicpv-ccnm: <nil>
STEP: delete the pod
Sep 27 07:49:48.320: INFO: Waiting for pod pod-subpath-test-dynamicpv-ccnm to disappear
Sep 27 07:49:48.422: INFO: Pod pod-subpath-test-dynamicpv-ccnm no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-ccnm
Sep 27 07:49:48.422: INFO: Deleting pod "pod-subpath-test-dynamicpv-ccnm" in namespace "provisioning-5219"
... skipping 102 lines ...
Sep 27 07:50:00.665: INFO: Pod aws-client still exists
Sep 27 07:50:02.665: INFO: Waiting for pod aws-client to disappear
Sep 27 07:50:02.769: INFO: Pod aws-client still exists
Sep 27 07:50:04.665: INFO: Waiting for pod aws-client to disappear
Sep 27 07:50:04.769: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Sep 27 07:50:04.959: INFO: Couldn't delete PD "aws://eu-west-3a/vol-08380f61f86af6c2e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08380f61f86af6c2e is currently attached to i-03991f0757f6206b7
	status code: 400, request id: 47aed76c-5116-4ed0-848c-796047a9ccc3
Sep 27 07:50:10.512: INFO: Couldn't delete PD "aws://eu-west-3a/vol-08380f61f86af6c2e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08380f61f86af6c2e is currently attached to i-03991f0757f6206b7
	status code: 400, request id: 09f08c01-1e64-442b-b444-178cd994911b
Sep 27 07:50:16.042: INFO: Couldn't delete PD "aws://eu-west-3a/vol-08380f61f86af6c2e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08380f61f86af6c2e is currently attached to i-03991f0757f6206b7
	status code: 400, request id: c8902a2f-7439-4140-8ec4-1effc7d7dba6
Sep 27 07:50:21.602: INFO: Couldn't delete PD "aws://eu-west-3a/vol-08380f61f86af6c2e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08380f61f86af6c2e is currently attached to i-03991f0757f6206b7
	status code: 400, request id: 4a08aa20-03b8-464d-9ea8-0724509ad09e
Sep 27 07:50:27.143: INFO: Successfully deleted PD "aws://eu-west-3a/vol-08380f61f86af6c2e".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 27 07:50:27.143: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-3076" for this suite.
... skipping 339 lines ...
Sep 27 07:49:28.566: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-8959-e2e-sc44kcc
STEP: creating a claim
Sep 27 07:49:28.675: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-jwmc
STEP: Creating a pod to test exec-volume-test
Sep 27 07:49:28.996: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-jwmc" in namespace "volume-8959" to be "Succeeded or Failed"
Sep 27 07:49:29.109: INFO: Pod "exec-volume-test-dynamicpv-jwmc": Phase="Pending", Reason="", readiness=false. Elapsed: 112.776328ms
Sep 27 07:49:31.223: INFO: Pod "exec-volume-test-dynamicpv-jwmc": Phase="Pending", Reason="", readiness=false. Elapsed: 2.22724636s
Sep 27 07:49:33.329: INFO: Pod "exec-volume-test-dynamicpv-jwmc": Phase="Pending", Reason="", readiness=false. Elapsed: 4.333164687s
Sep 27 07:49:35.434: INFO: Pod "exec-volume-test-dynamicpv-jwmc": Phase="Pending", Reason="", readiness=false. Elapsed: 6.438361253s
Sep 27 07:49:37.542: INFO: Pod "exec-volume-test-dynamicpv-jwmc": Phase="Pending", Reason="", readiness=false. Elapsed: 8.54589791s
Sep 27 07:49:39.648: INFO: Pod "exec-volume-test-dynamicpv-jwmc": Phase="Pending", Reason="", readiness=false. Elapsed: 10.651785426s
... skipping 5 lines ...
Sep 27 07:49:52.288: INFO: Pod "exec-volume-test-dynamicpv-jwmc": Phase="Pending", Reason="", readiness=false. Elapsed: 23.291707856s
Sep 27 07:49:54.392: INFO: Pod "exec-volume-test-dynamicpv-jwmc": Phase="Pending", Reason="", readiness=false. Elapsed: 25.396425737s
Sep 27 07:49:56.508: INFO: Pod "exec-volume-test-dynamicpv-jwmc": Phase="Pending", Reason="", readiness=false. Elapsed: 27.512154892s
Sep 27 07:49:58.615: INFO: Pod "exec-volume-test-dynamicpv-jwmc": Phase="Pending", Reason="", readiness=false. Elapsed: 29.619209784s
Sep 27 07:50:00.722: INFO: Pod "exec-volume-test-dynamicpv-jwmc": Phase="Succeeded", Reason="", readiness=false. Elapsed: 31.725570281s
STEP: Saw pod success
Sep 27 07:50:00.722: INFO: Pod "exec-volume-test-dynamicpv-jwmc" satisfied condition "Succeeded or Failed"
Sep 27 07:50:00.826: INFO: Trying to get logs from node ip-172-20-56-87.eu-west-3.compute.internal pod exec-volume-test-dynamicpv-jwmc container exec-container-dynamicpv-jwmc: <nil>
STEP: delete the pod
Sep 27 07:50:01.043: INFO: Waiting for pod exec-volume-test-dynamicpv-jwmc to disappear
Sep 27 07:50:01.150: INFO: Pod exec-volume-test-dynamicpv-jwmc no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-jwmc
Sep 27 07:50:01.150: INFO: Deleting pod "exec-volume-test-dynamicpv-jwmc" in namespace "volume-8959"
... skipping 191 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.8TytcAgTJ/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.8TytcAgTJ/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.8TytcAgTJ/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.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 282 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 27 07:50:13.003: 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.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Sep 27 07:50:13.525: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Sep 27 07:50:14.182: INFO: Successfully created a new PD: "aws://eu-west-3a/vol-00080ae4567c9a8af".
Sep 27 07:50:14.182: INFO: Creating resource for pre-provisioned PV
Sep 27 07:50:14.182: INFO: Creating PVC and PV
... skipping 5 lines ...
Sep 27 07:50:18.768: INFO: PersistentVolumeClaim pvc-vjlbx found but phase is Pending instead of Bound.
Sep 27 07:50:20.873: INFO: PersistentVolumeClaim pvc-vjlbx found but phase is Pending instead of Bound.
Sep 27 07:50:22.977: INFO: PersistentVolumeClaim pvc-vjlbx found and phase=Bound (8.520523744s)
Sep 27 07:50:22.977: INFO: Waiting up to 3m0s for PersistentVolume aws-6h92b to have phase Bound
Sep 27 07:50:23.080: INFO: PersistentVolume aws-6h92b found and phase=Bound (103.631179ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Sep 27 07:50:23.602: INFO: Deleting pod "pod-49d0938b-2c90-4d9a-937c-c5d5ca612ff2" in namespace "volumemode-1677"
Sep 27 07:50:23.719: INFO: Wait up to 5m0s for pod "pod-49d0938b-2c90-4d9a-937c-c5d5ca612ff2" to be fully deleted
STEP: Deleting pv and pvc
Sep 27 07:50:25.928: INFO: Deleting PersistentVolumeClaim "pvc-vjlbx"
Sep 27 07:50:26.032: INFO: Deleting PersistentVolume "aws-6h92b"
Sep 27 07:50:26.361: INFO: Couldn't delete PD "aws://eu-west-3a/vol-00080ae4567c9a8af", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00080ae4567c9a8af is currently attached to i-03991f0757f6206b7
	status code: 400, request id: 47220cbd-e686-4c44-9f12-39fdab583698
Sep 27 07:50:31.894: INFO: Couldn't delete PD "aws://eu-west-3a/vol-00080ae4567c9a8af", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00080ae4567c9a8af is currently attached to i-03991f0757f6206b7
	status code: 400, request id: af4db5fb-f6f0-44f8-b73d-67d71e5d74ef
Sep 27 07:50:37.434: INFO: Couldn't delete PD "aws://eu-west-3a/vol-00080ae4567c9a8af", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00080ae4567c9a8af is currently attached to i-03991f0757f6206b7
	status code: 400, request id: 3aee5d64-eff9-4f75-b62f-a9cc4a440eb8
Sep 27 07:50:42.945: INFO: Couldn't delete PD "aws://eu-west-3a/vol-00080ae4567c9a8af", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00080ae4567c9a8af is currently attached to i-03991f0757f6206b7
	status code: 400, request id: b309ef59-9d7e-431c-8124-6cb0fd186d1f
Sep 27 07:50:48.496: INFO: Couldn't delete PD "aws://eu-west-3a/vol-00080ae4567c9a8af", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00080ae4567c9a8af is currently attached to i-03991f0757f6206b7
	status code: 400, request id: 203efa05-a975-4896-97f0-78c928ddfb86
Sep 27 07:50:54.010: INFO: Successfully deleted PD "aws://eu-west-3a/vol-00080ae4567c9a8af".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 27 07:50:54.010: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-1677" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.8TytcAgTJ/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.8TytcAgTJ/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
    /tmp/kops.8TytcAgTJ/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.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 27 07:49:50.312: 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.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Sep 27 07:49:50.832: INFO: Creating resource for dynamic PV
Sep 27 07:49:50.832: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7815-e2e-sc4jd9j
STEP: creating a claim
Sep 27 07:49:50.938: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-fcbd
STEP: Checking for subpath error in container status
Sep 27 07:50:15.464: INFO: Deleting pod "pod-subpath-test-dynamicpv-fcbd" in namespace "provisioning-7815"
Sep 27 07:50:15.594: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-fcbd" to be fully deleted
STEP: Deleting pod
Sep 27 07:50:17.802: INFO: Deleting pod "pod-subpath-test-dynamicpv-fcbd" in namespace "provisioning-7815"
STEP: Deleting pvc
Sep 27 07:50:18.124: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com6g6nc"
... skipping 15 lines ...

• [SLOW TEST:64.067 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath directory is outside the volume [Slow][LinuxOnly]
    /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Sep 27 07:50:54.381: INFO: Driver "ebs.csi.aws.com" does not support volume type "CSIInlineVolume" - skipping
[AfterEach] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral
... skipping 153 lines ...
Sep 27 07:50:40.795: INFO: Waiting for pod aws-client to disappear
Sep 27 07:50:40.899: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Sep 27 07:50:40.900: INFO: Deleting PersistentVolumeClaim "pvc-5np7m"
Sep 27 07:50:41.006: INFO: Deleting PersistentVolume "aws-wpj2g"
Sep 27 07:50:41.649: INFO: Couldn't delete PD "aws://eu-west-3a/vol-07fa390bfbe142e47", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07fa390bfbe142e47 is currently attached to i-0dcb927116601f3cf
	status code: 400, request id: 9f113a17-0031-4173-82c1-75339d767281
Sep 27 07:50:47.176: INFO: Couldn't delete PD "aws://eu-west-3a/vol-07fa390bfbe142e47", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07fa390bfbe142e47 is currently attached to i-0dcb927116601f3cf
	status code: 400, request id: bc3a52a1-898d-44cc-ba77-c40b58957f29
Sep 27 07:50:52.695: INFO: Couldn't delete PD "aws://eu-west-3a/vol-07fa390bfbe142e47", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07fa390bfbe142e47 is currently attached to i-0dcb927116601f3cf
	status code: 400, request id: 5ed2c1c8-8edd-4d3f-9952-de0832fb3f32
Sep 27 07:50:58.232: INFO: Successfully deleted PD "aws://eu-west-3a/vol-07fa390bfbe142e47".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 27 07:50:58.232: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-2114" for this suite.
... skipping 20 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.8TytcAgTJ/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.8TytcAgTJ/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.8TytcAgTJ/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.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 154 lines ...

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

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

    /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 155 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.8TytcAgTJ/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.8TytcAgTJ/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.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 20 lines ...
Sep 27 07:50:22.309: INFO: PersistentVolumeClaim pvc-9dhtw found but phase is Pending instead of Bound.
Sep 27 07:50:24.413: INFO: PersistentVolumeClaim pvc-9dhtw found and phase=Bound (6.414857873s)
Sep 27 07:50:24.413: INFO: Waiting up to 3m0s for PersistentVolume aws-8fpqq to have phase Bound
Sep 27 07:50:24.528: INFO: PersistentVolume aws-8fpqq found and phase=Bound (115.210689ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-jr2w
STEP: Creating a pod to test exec-volume-test
Sep 27 07:50:24.837: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-jr2w" in namespace "volume-1429" to be "Succeeded or Failed"
Sep 27 07:50:24.939: INFO: Pod "exec-volume-test-preprovisionedpv-jr2w": Phase="Pending", Reason="", readiness=false. Elapsed: 102.129681ms
Sep 27 07:50:27.043: INFO: Pod "exec-volume-test-preprovisionedpv-jr2w": Phase="Pending", Reason="", readiness=false. Elapsed: 2.205775702s
Sep 27 07:50:29.147: INFO: Pod "exec-volume-test-preprovisionedpv-jr2w": Phase="Pending", Reason="", readiness=false. Elapsed: 4.309382919s
Sep 27 07:50:31.250: INFO: Pod "exec-volume-test-preprovisionedpv-jr2w": Phase="Pending", Reason="", readiness=false. Elapsed: 6.412375142s
Sep 27 07:50:33.354: INFO: Pod "exec-volume-test-preprovisionedpv-jr2w": Phase="Pending", Reason="", readiness=false. Elapsed: 8.516361377s
Sep 27 07:50:35.457: INFO: Pod "exec-volume-test-preprovisionedpv-jr2w": Phase="Pending", Reason="", readiness=false. Elapsed: 10.619453644s
Sep 27 07:50:37.580: INFO: Pod "exec-volume-test-preprovisionedpv-jr2w": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.742895125s
STEP: Saw pod success
Sep 27 07:50:37.580: INFO: Pod "exec-volume-test-preprovisionedpv-jr2w" satisfied condition "Succeeded or Failed"
Sep 27 07:50:37.683: INFO: Trying to get logs from node ip-172-20-55-93.eu-west-3.compute.internal pod exec-volume-test-preprovisionedpv-jr2w container exec-container-preprovisionedpv-jr2w: <nil>
STEP: delete the pod
Sep 27 07:50:37.901: INFO: Waiting for pod exec-volume-test-preprovisionedpv-jr2w to disappear
Sep 27 07:50:38.003: INFO: Pod exec-volume-test-preprovisionedpv-jr2w no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-jr2w
Sep 27 07:50:38.004: INFO: Deleting pod "exec-volume-test-preprovisionedpv-jr2w" in namespace "volume-1429"
STEP: Deleting pv and pvc
Sep 27 07:50:38.106: INFO: Deleting PersistentVolumeClaim "pvc-9dhtw"
Sep 27 07:50:38.210: INFO: Deleting PersistentVolume "aws-8fpqq"
Sep 27 07:50:38.505: INFO: Couldn't delete PD "aws://eu-west-3a/vol-01794fad86a155602", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01794fad86a155602 is currently attached to i-03991f0757f6206b7
	status code: 400, request id: 3dc004d2-f0ed-4f77-bf15-7a0c00406b73
Sep 27 07:50:44.043: INFO: Couldn't delete PD "aws://eu-west-3a/vol-01794fad86a155602", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01794fad86a155602 is currently attached to i-03991f0757f6206b7
	status code: 400, request id: 8169184c-004e-4cda-a41d-0a3f7297e20d
Sep 27 07:50:49.593: INFO: Couldn't delete PD "aws://eu-west-3a/vol-01794fad86a155602", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01794fad86a155602 is currently attached to i-03991f0757f6206b7
	status code: 400, request id: f5876b33-99fc-4db6-850d-5b5743be5d30
Sep 27 07:50:55.121: INFO: Couldn't delete PD "aws://eu-west-3a/vol-01794fad86a155602", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01794fad86a155602 is currently attached to i-03991f0757f6206b7
	status code: 400, request id: 27bd8d17-cc1e-42ed-a9e9-45a8c008fed4
Sep 27 07:51:00.716: INFO: Couldn't delete PD "aws://eu-west-3a/vol-01794fad86a155602", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01794fad86a155602 is currently attached to i-03991f0757f6206b7
	status code: 400, request id: f676058e-b53d-410a-a13c-7ee1c970460f
Sep 27 07:51:06.288: INFO: Successfully deleted PD "aws://eu-west-3a/vol-01794fad86a155602".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 27 07:51:06.288: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-1429" for this suite.
... skipping 299 lines ...
Sep 27 07:50:54.452: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2112-e2e-scjnmfp
STEP: creating a claim
Sep 27 07:50:54.556: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-67xx
STEP: Creating a pod to test multi_subpath
Sep 27 07:50:54.868: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-67xx" in namespace "provisioning-2112" to be "Succeeded or Failed"
Sep 27 07:50:54.972: INFO: Pod "pod-subpath-test-dynamicpv-67xx": Phase="Pending", Reason="", readiness=false. Elapsed: 103.421518ms
Sep 27 07:50:57.076: INFO: Pod "pod-subpath-test-dynamicpv-67xx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.207777068s
Sep 27 07:50:59.180: INFO: Pod "pod-subpath-test-dynamicpv-67xx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.312340667s
Sep 27 07:51:01.284: INFO: Pod "pod-subpath-test-dynamicpv-67xx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.416214019s
Sep 27 07:51:03.389: INFO: Pod "pod-subpath-test-dynamicpv-67xx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.520448457s
Sep 27 07:51:05.493: INFO: Pod "pod-subpath-test-dynamicpv-67xx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.624730344s
Sep 27 07:51:07.597: INFO: Pod "pod-subpath-test-dynamicpv-67xx": Phase="Pending", Reason="", readiness=false. Elapsed: 12.729121457s
Sep 27 07:51:09.703: INFO: Pod "pod-subpath-test-dynamicpv-67xx": Phase="Pending", Reason="", readiness=false. Elapsed: 14.834551531s
Sep 27 07:51:11.808: INFO: Pod "pod-subpath-test-dynamicpv-67xx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.939961917s
STEP: Saw pod success
Sep 27 07:51:11.808: INFO: Pod "pod-subpath-test-dynamicpv-67xx" satisfied condition "Succeeded or Failed"
Sep 27 07:51:11.912: INFO: Trying to get logs from node ip-172-20-54-99.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-67xx container test-container-subpath-dynamicpv-67xx: <nil>
STEP: delete the pod
Sep 27 07:51:12.129: INFO: Waiting for pod pod-subpath-test-dynamicpv-67xx to disappear
Sep 27 07:51:12.232: INFO: Pod pod-subpath-test-dynamicpv-67xx no longer exists
STEP: Deleting pod
Sep 27 07:51:12.232: INFO: Deleting pod "pod-subpath-test-dynamicpv-67xx" in namespace "provisioning-2112"
... skipping 28 lines ...

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

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

    /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 33 lines ...
Sep 27 07:50:32.853: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7886fqp5j
STEP: creating a claim
Sep 27 07:50:32.956: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-fhjb
STEP: Creating a pod to test subpath
Sep 27 07:50:33.272: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-fhjb" in namespace "provisioning-7886" to be "Succeeded or Failed"
Sep 27 07:50:33.376: INFO: Pod "pod-subpath-test-dynamicpv-fhjb": Phase="Pending", Reason="", readiness=false. Elapsed: 103.649681ms
Sep 27 07:50:35.478: INFO: Pod "pod-subpath-test-dynamicpv-fhjb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.206336289s
Sep 27 07:50:37.596: INFO: Pod "pod-subpath-test-dynamicpv-fhjb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.324228643s
Sep 27 07:50:39.699: INFO: Pod "pod-subpath-test-dynamicpv-fhjb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.427126224s
Sep 27 07:50:41.804: INFO: Pod "pod-subpath-test-dynamicpv-fhjb": Phase="Pending", Reason="", readiness=false. Elapsed: 8.531868179s
Sep 27 07:50:43.907: INFO: Pod "pod-subpath-test-dynamicpv-fhjb": Phase="Pending", Reason="", readiness=false. Elapsed: 10.635327978s
... skipping 9 lines ...
Sep 27 07:51:04.946: INFO: Pod "pod-subpath-test-dynamicpv-fhjb": Phase="Pending", Reason="", readiness=false. Elapsed: 31.674330653s
Sep 27 07:51:07.049: INFO: Pod "pod-subpath-test-dynamicpv-fhjb": Phase="Pending", Reason="", readiness=false. Elapsed: 33.777091968s
Sep 27 07:51:09.151: INFO: Pod "pod-subpath-test-dynamicpv-fhjb": Phase="Pending", Reason="", readiness=false. Elapsed: 35.879366469s
Sep 27 07:51:11.254: INFO: Pod "pod-subpath-test-dynamicpv-fhjb": Phase="Pending", Reason="", readiness=false. Elapsed: 37.981707866s
Sep 27 07:51:13.359: INFO: Pod "pod-subpath-test-dynamicpv-fhjb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 40.087030582s
STEP: Saw pod success
Sep 27 07:51:13.359: INFO: Pod "pod-subpath-test-dynamicpv-fhjb" satisfied condition "Succeeded or Failed"
Sep 27 07:51:13.461: INFO: Trying to get logs from node ip-172-20-55-93.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-fhjb container test-container-volume-dynamicpv-fhjb: <nil>
STEP: delete the pod
Sep 27 07:51:13.680: INFO: Waiting for pod pod-subpath-test-dynamicpv-fhjb to disappear
Sep 27 07:51:13.782: INFO: Pod pod-subpath-test-dynamicpv-fhjb no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-fhjb
Sep 27 07:51:13.782: INFO: Deleting pod "pod-subpath-test-dynamicpv-fhjb" in namespace "provisioning-7886"
... skipping 53 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 27 07:50:59.195: 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.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Sep 27 07:50:59.718: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Sep 27 07:50:59.718: INFO: Creating resource for dynamic PV
Sep 27 07:50:59.718: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3302vxgps
STEP: creating a claim
Sep 27 07:50:59.823: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-b7kv
STEP: Checking for subpath error in container status
Sep 27 07:51:14.352: INFO: Deleting pod "pod-subpath-test-dynamicpv-b7kv" in namespace "provisioning-3302"
Sep 27 07:51:14.463: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-b7kv" to be fully deleted
STEP: Deleting pod
Sep 27 07:51:16.682: INFO: Deleting pod "pod-subpath-test-dynamicpv-b7kv" in namespace "provisioning-3302"
STEP: Deleting pvc
Sep 27 07:51:17.010: INFO: Deleting PersistentVolumeClaim "aws7kdnf"
... skipping 13 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.8TytcAgTJ/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.8TytcAgTJ/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath directory is outside the volume [Slow][LinuxOnly]
      /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (ext3)] volumes
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Sep 27 07:51:32.858: INFO: Driver aws doesn't support ext3 -- skipping
[AfterEach] [Testpattern: Pre-provisioned PV (ext3)] volumes
... skipping 23 lines ...

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

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

    /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 100 lines ...

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 73 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 27 07:51:05.478: 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.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Sep 27 07:51:05.996: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Sep 27 07:51:05.996: INFO: Creating resource for dynamic PV
Sep 27 07:51:05.996: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-95rfhg4
STEP: creating a claim
Sep 27 07:51:06.100: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-gzbc
STEP: Checking for subpath error in container status
Sep 27 07:51:22.630: INFO: Deleting pod "pod-subpath-test-dynamicpv-gzbc" in namespace "provisioning-95"
Sep 27 07:51:22.735: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-gzbc" to be fully deleted
STEP: Deleting pod
Sep 27 07:51:24.947: INFO: Deleting pod "pod-subpath-test-dynamicpv-gzbc" in namespace "provisioning-95"
STEP: Deleting pvc
Sep 27 07:51:25.255: INFO: Deleting PersistentVolumeClaim "awsxmrwh"
... skipping 13 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.8TytcAgTJ/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.8TytcAgTJ/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.8TytcAgTJ/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.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 27 07:51:01.375: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename provisioning
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail if subpath file is outside the volume [Slow][LinuxOnly]
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Sep 27 07:51:01.897: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Sep 27 07:51:01.897: INFO: Creating resource for dynamic PV
Sep 27 07:51:01.897: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-69476h4fs
STEP: creating a claim
Sep 27 07:51:02.001: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-f78f
STEP: Checking for subpath error in container status
Sep 27 07:51:18.524: INFO: Deleting pod "pod-subpath-test-dynamicpv-f78f" in namespace "provisioning-6947"
Sep 27 07:51:18.632: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-f78f" to be fully deleted
STEP: Deleting pod
Sep 27 07:51:22.845: INFO: Deleting pod "pod-subpath-test-dynamicpv-f78f" in namespace "provisioning-6947"
STEP: Deleting pvc
Sep 27 07:51:23.163: INFO: Deleting PersistentVolumeClaim "awsk24gx"
... skipping 14 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.8TytcAgTJ/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.8TytcAgTJ/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath file is outside the volume [Slow][LinuxOnly]
      /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 172 lines ...
Sep 27 07:50:09.012: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9181-e2e-scb6zj5
STEP: creating a claim
Sep 27 07:50:09.117: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-h6cv
STEP: Creating a pod to test subpath
Sep 27 07:50:09.430: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-h6cv" in namespace "provisioning-9181" to be "Succeeded or Failed"
Sep 27 07:50:09.533: INFO: Pod "pod-subpath-test-dynamicpv-h6cv": Phase="Pending", Reason="", readiness=false. Elapsed: 102.993885ms
Sep 27 07:50:11.639: INFO: Pod "pod-subpath-test-dynamicpv-h6cv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.209171269s
Sep 27 07:50:13.749: INFO: Pod "pod-subpath-test-dynamicpv-h6cv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.318935945s
Sep 27 07:50:15.852: INFO: Pod "pod-subpath-test-dynamicpv-h6cv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.422070625s
Sep 27 07:50:17.957: INFO: Pod "pod-subpath-test-dynamicpv-h6cv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.526849953s
Sep 27 07:50:20.062: INFO: Pod "pod-subpath-test-dynamicpv-h6cv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.631406708s
Sep 27 07:50:22.166: INFO: Pod "pod-subpath-test-dynamicpv-h6cv": Phase="Pending", Reason="", readiness=false. Elapsed: 12.735393964s
Sep 27 07:50:24.269: INFO: Pod "pod-subpath-test-dynamicpv-h6cv": Phase="Pending", Reason="", readiness=false. Elapsed: 14.838520062s
Sep 27 07:50:26.372: INFO: Pod "pod-subpath-test-dynamicpv-h6cv": Phase="Pending", Reason="", readiness=false. Elapsed: 16.941782917s
Sep 27 07:50:28.476: INFO: Pod "pod-subpath-test-dynamicpv-h6cv": Phase="Pending", Reason="", readiness=false. Elapsed: 19.045898993s
Sep 27 07:50:30.581: INFO: Pod "pod-subpath-test-dynamicpv-h6cv": Phase="Pending", Reason="", readiness=false. Elapsed: 21.150459098s
Sep 27 07:50:32.684: INFO: Pod "pod-subpath-test-dynamicpv-h6cv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.253764646s
STEP: Saw pod success
Sep 27 07:50:32.684: INFO: Pod "pod-subpath-test-dynamicpv-h6cv" satisfied condition "Succeeded or Failed"
Sep 27 07:50:32.787: INFO: Trying to get logs from node ip-172-20-55-93.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-h6cv container test-container-subpath-dynamicpv-h6cv: <nil>
STEP: delete the pod
Sep 27 07:50:33.012: INFO: Waiting for pod pod-subpath-test-dynamicpv-h6cv to disappear
Sep 27 07:50:33.114: INFO: Pod pod-subpath-test-dynamicpv-h6cv no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-h6cv
Sep 27 07:50:33.115: INFO: Deleting pod "pod-subpath-test-dynamicpv-h6cv" in namespace "provisioning-9181"
STEP: Creating pod pod-subpath-test-dynamicpv-h6cv
STEP: Creating a pod to test subpath
Sep 27 07:50:33.324: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-h6cv" in namespace "provisioning-9181" to be "Succeeded or Failed"
Sep 27 07:50:33.427: INFO: Pod "pod-subpath-test-dynamicpv-h6cv": Phase="Pending", Reason="", readiness=false. Elapsed: 103.210925ms
Sep 27 07:50:35.531: INFO: Pod "pod-subpath-test-dynamicpv-h6cv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.20747741s
Sep 27 07:50:37.636: INFO: Pod "pod-subpath-test-dynamicpv-h6cv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.312299364s
Sep 27 07:50:39.739: INFO: Pod "pod-subpath-test-dynamicpv-h6cv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.415401679s
Sep 27 07:50:41.843: INFO: Pod "pod-subpath-test-dynamicpv-h6cv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.519159097s
Sep 27 07:50:43.947: INFO: Pod "pod-subpath-test-dynamicpv-h6cv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.623388078s
... skipping 7 lines ...
Sep 27 07:51:00.779: INFO: Pod "pod-subpath-test-dynamicpv-h6cv": Phase="Pending", Reason="", readiness=false. Elapsed: 27.45574143s
Sep 27 07:51:02.883: INFO: Pod "pod-subpath-test-dynamicpv-h6cv": Phase="Pending", Reason="", readiness=false. Elapsed: 29.559291681s
Sep 27 07:51:04.987: INFO: Pod "pod-subpath-test-dynamicpv-h6cv": Phase="Pending", Reason="", readiness=false. Elapsed: 31.663489565s
Sep 27 07:51:07.091: INFO: Pod "pod-subpath-test-dynamicpv-h6cv": Phase="Pending", Reason="", readiness=false. Elapsed: 33.767471589s
Sep 27 07:51:09.195: INFO: Pod "pod-subpath-test-dynamicpv-h6cv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 35.871221395s
STEP: Saw pod success
Sep 27 07:51:09.195: INFO: Pod "pod-subpath-test-dynamicpv-h6cv" satisfied condition "Succeeded or Failed"
Sep 27 07:51:09.298: INFO: Trying to get logs from node ip-172-20-56-87.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-h6cv container test-container-subpath-dynamicpv-h6cv: <nil>
STEP: delete the pod
Sep 27 07:51:09.516: INFO: Waiting for pod pod-subpath-test-dynamicpv-h6cv to disappear
Sep 27 07:51:09.619: INFO: Pod pod-subpath-test-dynamicpv-h6cv no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-h6cv
Sep 27 07:51:09.619: INFO: Deleting pod "pod-subpath-test-dynamicpv-h6cv" in namespace "provisioning-9181"
... skipping 376 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.8TytcAgTJ/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.8TytcAgTJ/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.8TytcAgTJ/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.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Driver supports dynamic provisioning, skipping InlineVolume pattern

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 82 lines ...
STEP: Deleting pod hostexec-ip-172-20-56-87.eu-west-3.compute.internal-8jsdz in namespace volumemode-4121
Sep 27 07:51:32.027: INFO: Deleting pod "pod-1e73b37c-a185-4f27-a480-4d9b68c5c273" in namespace "volumemode-4121"
Sep 27 07:51:32.132: INFO: Wait up to 5m0s for pod "pod-1e73b37c-a185-4f27-a480-4d9b68c5c273" to be fully deleted
STEP: Deleting pv and pvc
Sep 27 07:51:34.337: INFO: Deleting PersistentVolumeClaim "pvc-wqtf9"
Sep 27 07:51:34.447: INFO: Deleting PersistentVolume "aws-5jsjz"
Sep 27 07:51:34.760: INFO: Couldn't delete PD "aws://eu-west-3a/vol-05ab0ebb6e135ee69", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05ab0ebb6e135ee69 is currently attached to i-0dcb927116601f3cf
	status code: 400, request id: 8a78be1b-717f-42f3-b281-a3f1d12760b2
Sep 27 07:51:40.311: INFO: Couldn't delete PD "aws://eu-west-3a/vol-05ab0ebb6e135ee69", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05ab0ebb6e135ee69 is currently attached to i-0dcb927116601f3cf
	status code: 400, request id: 5f7e8c54-9344-42ab-8954-869151d35281
Sep 27 07:51:45.873: INFO: Couldn't delete PD "aws://eu-west-3a/vol-05ab0ebb6e135ee69", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05ab0ebb6e135ee69 is currently attached to i-0dcb927116601f3cf
	status code: 400, request id: 2b7dbe69-eb96-4f0d-a1a5-0528fa8ee812
Sep 27 07:51:51.492: INFO: Couldn't delete PD "aws://eu-west-3a/vol-05ab0ebb6e135ee69", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05ab0ebb6e135ee69 is currently attached to i-0dcb927116601f3cf
	status code: 400, request id: 0db536de-b22e-4aa6-8f37-2139f6f1f2df
Sep 27 07:51:57.048: INFO: Successfully deleted PD "aws://eu-west-3a/vol-05ab0ebb6e135ee69".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 27 07:51:57.048: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-4121" for this suite.
... skipping 606 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.8TytcAgTJ/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.8TytcAgTJ/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.8TytcAgTJ/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.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 21 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 27 07:51:45.148: 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.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Sep 27 07:51:45.660: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Sep 27 07:51:45.660: INFO: Creating resource for dynamic PV
Sep 27 07:51:45.660: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-9222rcj6q
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Sep 27 07:51:50.393: INFO: Deleting pod "pod-3ac59fc6-47fc-49e9-a8b1-27e3f7f8daba" in namespace "volumemode-9222"
Sep 27 07:51:50.495: INFO: Wait up to 5m0s for pod "pod-3ac59fc6-47fc-49e9-a8b1-27e3f7f8daba" to be fully deleted
STEP: Deleting pvc
Sep 27 07:51:52.902: INFO: Deleting PersistentVolumeClaim "awsw98hr"
Sep 27 07:51:53.004: INFO: Waiting up to 5m0s for PersistentVolume pvc-1d776dd9-1bff-47ba-9832-cb989b669f7b to get deleted
Sep 27 07:51:53.105: INFO: PersistentVolume pvc-1d776dd9-1bff-47ba-9832-cb989b669f7b found and phase=Released (100.730076ms)
... skipping 12 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.8TytcAgTJ/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.8TytcAgTJ/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
    /tmp/kops.8TytcAgTJ/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.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 139 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 27 07:51:47.731: 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.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Sep 27 07:51:48.246: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Sep 27 07:51:48.246: INFO: Creating resource for dynamic PV
Sep 27 07:51:48.246: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-631559sx6
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Sep 27 07:51:54.981: INFO: Deleting pod "pod-58487ec4-7992-4c72-9ef0-d6dd00f5fb3a" in namespace "volumemode-6315"
Sep 27 07:51:55.084: INFO: Wait up to 5m0s for pod "pod-58487ec4-7992-4c72-9ef0-d6dd00f5fb3a" to be fully deleted
STEP: Deleting pvc
Sep 27 07:51:57.518: INFO: Deleting PersistentVolumeClaim "awsdjlp9"
Sep 27 07:51:57.625: INFO: Waiting up to 5m0s for PersistentVolume pvc-505327d3-8955-420c-a178-09c875eae641 to get deleted
Sep 27 07:51:57.728: INFO: PersistentVolume pvc-505327d3-8955-420c-a178-09c875eae641 found and phase=Released (102.312941ms)
... skipping 12 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.8TytcAgTJ/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.8TytcAgTJ/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (block volmode)] volumeMode
    /tmp/kops.8TytcAgTJ/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.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 212 lines ...
Sep 27 07:51:47.584: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8857wgvd
STEP: creating a claim
Sep 27 07:51:47.692: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-jnz8
STEP: Creating a pod to test subpath
Sep 27 07:51:48.005: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-jnz8" in namespace "provisioning-885" to be "Succeeded or Failed"
Sep 27 07:51:48.108: INFO: Pod "pod-subpath-test-dynamicpv-jnz8": Phase="Pending", Reason="", readiness=false. Elapsed: 103.199405ms
Sep 27 07:51:50.211: INFO: Pod "pod-subpath-test-dynamicpv-jnz8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.206474707s
Sep 27 07:51:52.315: INFO: Pod "pod-subpath-test-dynamicpv-jnz8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.309914454s
Sep 27 07:51:54.422: INFO: Pod "pod-subpath-test-dynamicpv-jnz8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.41706426s
Sep 27 07:51:56.526: INFO: Pod "pod-subpath-test-dynamicpv-jnz8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.521182124s
Sep 27 07:51:58.631: INFO: Pod "pod-subpath-test-dynamicpv-jnz8": Phase="Pending", Reason="", readiness=false. Elapsed: 10.625912981s
Sep 27 07:52:00.735: INFO: Pod "pod-subpath-test-dynamicpv-jnz8": Phase="Pending", Reason="", readiness=false. Elapsed: 12.730337173s
Sep 27 07:52:02.840: INFO: Pod "pod-subpath-test-dynamicpv-jnz8": Phase="Pending", Reason="", readiness=false. Elapsed: 14.834507104s
Sep 27 07:52:04.944: INFO: Pod "pod-subpath-test-dynamicpv-jnz8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.939022829s
STEP: Saw pod success
Sep 27 07:52:04.944: INFO: Pod "pod-subpath-test-dynamicpv-jnz8" satisfied condition "Succeeded or Failed"
Sep 27 07:52:05.047: INFO: Trying to get logs from node ip-172-20-54-99.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-jnz8 container test-container-subpath-dynamicpv-jnz8: <nil>
STEP: delete the pod
Sep 27 07:52:05.262: INFO: Waiting for pod pod-subpath-test-dynamicpv-jnz8 to disappear
Sep 27 07:52:05.365: INFO: Pod pod-subpath-test-dynamicpv-jnz8 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-jnz8
Sep 27 07:52:05.365: INFO: Deleting pod "pod-subpath-test-dynamicpv-jnz8" in namespace "provisioning-885"
... skipping 84 lines ...
Sep 27 07:51:41.616: INFO: Creating resource for dynamic PV
Sep 27 07:51:41.616: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1082hgcf2
STEP: creating a claim
Sep 27 07:51:41.721: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-1082
Sep 27 07:51:42.034: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-1082" in namespace "provisioning-1082" to be "Succeeded or Failed"
Sep 27 07:51:42.138: INFO: Pod "volume-prep-provisioning-1082": Phase="Pending", Reason="", readiness=false. Elapsed: 103.44268ms
Sep 27 07:51:44.243: INFO: Pod "volume-prep-provisioning-1082": Phase="Pending", Reason="", readiness=false. Elapsed: 2.208708283s
Sep 27 07:51:46.354: INFO: Pod "volume-prep-provisioning-1082": Phase="Pending", Reason="", readiness=false. Elapsed: 4.319545658s
Sep 27 07:51:48.463: INFO: Pod "volume-prep-provisioning-1082": Phase="Pending", Reason="", readiness=false. Elapsed: 6.428871974s
Sep 27 07:51:50.567: INFO: Pod "volume-prep-provisioning-1082": Phase="Pending", Reason="", readiness=false. Elapsed: 8.533014586s
Sep 27 07:51:52.671: INFO: Pod "volume-prep-provisioning-1082": Phase="Pending", Reason="", readiness=false. Elapsed: 10.636655778s
Sep 27 07:51:54.775: INFO: Pod "volume-prep-provisioning-1082": Phase="Pending", Reason="", readiness=false. Elapsed: 12.740380146s
Sep 27 07:51:56.879: INFO: Pod "volume-prep-provisioning-1082": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.844274106s
STEP: Saw pod success
Sep 27 07:51:56.879: INFO: Pod "volume-prep-provisioning-1082" satisfied condition "Succeeded or Failed"
Sep 27 07:51:56.879: INFO: Deleting pod "volume-prep-provisioning-1082" in namespace "provisioning-1082"
Sep 27 07:51:56.989: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-1082" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-l4t5
STEP: Checking for subpath error in container status
Sep 27 07:52:07.410: INFO: Deleting pod "pod-subpath-test-dynamicpv-l4t5" in namespace "provisioning-1082"
Sep 27 07:52:07.538: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-l4t5" to be fully deleted
STEP: Deleting pod
Sep 27 07:52:07.644: INFO: Deleting pod "pod-subpath-test-dynamicpv-l4t5" in namespace "provisioning-1082"
STEP: Deleting pvc
Sep 27 07:52:07.953: INFO: Deleting PersistentVolumeClaim "aws9698x"
... skipping 61 lines ...
Sep 27 07:51:58.516: INFO: Creating resource for dynamic PV
Sep 27 07:51:58.516: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-3729q7866
STEP: creating a claim
STEP: Expanding non-expandable pvc
Sep 27 07:51:58.832: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Sep 27 07:51:59.038: INFO: Error updating pvc awsnkqrj: PersistentVolumeClaim "awsnkqrj" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3729q7866",
  	... // 3 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Sep 27 07:52:29.475: INFO: Error updating pvc awsnkqrj: PersistentVolumeClaim "awsnkqrj" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 175 lines ...
Sep 27 07:52:06.069: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Sep 27 07:52:06.773: INFO: Successfully created a new PD: "aws://eu-west-3a/vol-0feda9bb06eebe36c".
Sep 27 07:52:06.773: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-xbnr
STEP: Creating a pod to test exec-volume-test
Sep 27 07:52:06.880: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-xbnr" in namespace "volume-5165" to be "Succeeded or Failed"
Sep 27 07:52:06.984: INFO: Pod "exec-volume-test-inlinevolume-xbnr": Phase="Pending", Reason="", readiness=false. Elapsed: 104.120415ms
Sep 27 07:52:09.088: INFO: Pod "exec-volume-test-inlinevolume-xbnr": Phase="Pending", Reason="", readiness=false. Elapsed: 2.20841139s
Sep 27 07:52:11.193: INFO: Pod "exec-volume-test-inlinevolume-xbnr": Phase="Pending", Reason="", readiness=false. Elapsed: 4.312610379s
Sep 27 07:52:13.298: INFO: Pod "exec-volume-test-inlinevolume-xbnr": Phase="Pending", Reason="", readiness=false. Elapsed: 6.417861415s
Sep 27 07:52:15.403: INFO: Pod "exec-volume-test-inlinevolume-xbnr": Phase="Pending", Reason="", readiness=false. Elapsed: 8.523377304s
Sep 27 07:52:17.513: INFO: Pod "exec-volume-test-inlinevolume-xbnr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.632673975s
STEP: Saw pod success
Sep 27 07:52:17.513: INFO: Pod "exec-volume-test-inlinevolume-xbnr" satisfied condition "Succeeded or Failed"
Sep 27 07:52:17.617: INFO: Trying to get logs from node ip-172-20-54-99.eu-west-3.compute.internal pod exec-volume-test-inlinevolume-xbnr container exec-container-inlinevolume-xbnr: <nil>
STEP: delete the pod
Sep 27 07:52:17.840: INFO: Waiting for pod exec-volume-test-inlinevolume-xbnr to disappear
Sep 27 07:52:17.944: INFO: Pod exec-volume-test-inlinevolume-xbnr no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-xbnr
Sep 27 07:52:17.944: INFO: Deleting pod "exec-volume-test-inlinevolume-xbnr" in namespace "volume-5165"
Sep 27 07:52:18.533: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0feda9bb06eebe36c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0feda9bb06eebe36c is currently attached to i-03ec4335fb22bd051
	status code: 400, request id: 3e9056aa-e64f-4882-a3f8-adbbbd4ee9a2
Sep 27 07:52:24.110: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0feda9bb06eebe36c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0feda9bb06eebe36c is currently attached to i-03ec4335fb22bd051
	status code: 400, request id: c2a21619-7f67-4f59-9f4b-2aad386f1b8a
Sep 27 07:52:29.677: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0feda9bb06eebe36c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0feda9bb06eebe36c is currently attached to i-03ec4335fb22bd051
	status code: 400, request id: f2043431-7881-4718-94a9-7aec75f4794d
Sep 27 07:52:35.238: INFO: Successfully deleted PD "aws://eu-west-3a/vol-0feda9bb06eebe36c".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 27 07:52:35.238: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-5165" for this suite.
... skipping 14 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 27 07:52:02.900: 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.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Sep 27 07:52:03.411: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Sep 27 07:52:03.411: INFO: Creating resource for dynamic PV
Sep 27 07:52:03.412: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-14sdgj6
STEP: creating a claim
Sep 27 07:52:03.515: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-vpmt
STEP: Checking for subpath error in container status
Sep 27 07:52:18.029: INFO: Deleting pod "pod-subpath-test-dynamicpv-vpmt" in namespace "provisioning-14"
Sep 27 07:52:18.132: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-vpmt" to be fully deleted
STEP: Deleting pod
Sep 27 07:52:20.336: INFO: Deleting pod "pod-subpath-test-dynamicpv-vpmt" in namespace "provisioning-14"
STEP: Deleting pvc
Sep 27 07:52:20.640: INFO: Deleting PersistentVolumeClaim "aws4g9h8"
... skipping 13 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.8TytcAgTJ/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.8TytcAgTJ/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.8TytcAgTJ/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.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Sep 27 07:52:36.477: INFO: Driver supports dynamic provisioning, skipping PreprovisionedPV pattern
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
... skipping 57 lines ...
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 27 07:52:36.483: 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.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Sep 27 07:52:37.096: INFO: found topology map[topology.kubernetes.io/zone:eu-west-3a]
Sep 27 07:52:37.096: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Sep 27 07:52:37.096: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.8TytcAgTJ/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.8TytcAgTJ/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (delayed binding)] topology
    /tmp/kops.8TytcAgTJ/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.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 2 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 27 07:51:44.845: 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.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Sep 27 07:51:45.368: INFO: Creating resource for dynamic PV
Sep 27 07:51:45.368: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1621-e2e-sch8t92
STEP: creating a claim
Sep 27 07:51:45.473: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-rm8b
STEP: Checking for subpath error in container status
Sep 27 07:52:02.030: INFO: Deleting pod "pod-subpath-test-dynamicpv-rm8b" in namespace "provisioning-1621"
Sep 27 07:52:02.141: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-rm8b" to be fully deleted
STEP: Deleting pod
Sep 27 07:52:04.350: INFO: Deleting pod "pod-subpath-test-dynamicpv-rm8b" in namespace "provisioning-1621"
STEP: Deleting pvc
Sep 27 07:52:04.660: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comnz6zp"
... skipping 15 lines ...

• [SLOW TEST:56.080 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.8TytcAgTJ/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.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] volumes
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] volumes
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 7 lines ...
Sep 27 07:51:09.791: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-9066-e2e-scplbqh
STEP: creating a claim
Sep 27 07:51:09.893: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-5rsp
STEP: Creating a pod to test exec-volume-test
Sep 27 07:51:10.202: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-5rsp" in namespace "volume-9066" to be "Succeeded or Failed"
Sep 27 07:51:10.305: INFO: Pod "exec-volume-test-dynamicpv-5rsp": Phase="Pending", Reason="", readiness=false. Elapsed: 102.18192ms
Sep 27 07:51:12.407: INFO: Pod "exec-volume-test-dynamicpv-5rsp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.204128268s
Sep 27 07:51:14.509: INFO: Pod "exec-volume-test-dynamicpv-5rsp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.306629224s
Sep 27 07:51:16.612: INFO: Pod "exec-volume-test-dynamicpv-5rsp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.40933636s
Sep 27 07:51:18.716: INFO: Pod "exec-volume-test-dynamicpv-5rsp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.513486511s
Sep 27 07:51:20.820: INFO: Pod "exec-volume-test-dynamicpv-5rsp": Phase="Pending", Reason="", readiness=false. Elapsed: 10.617628302s
... skipping 3 lines ...
Sep 27 07:51:29.234: INFO: Pod "exec-volume-test-dynamicpv-5rsp": Phase="Pending", Reason="", readiness=false. Elapsed: 19.03199176s
Sep 27 07:51:31.338: INFO: Pod "exec-volume-test-dynamicpv-5rsp": Phase="Pending", Reason="", readiness=false. Elapsed: 21.13510329s
Sep 27 07:51:33.447: INFO: Pod "exec-volume-test-dynamicpv-5rsp": Phase="Pending", Reason="", readiness=false. Elapsed: 23.244716627s
Sep 27 07:51:35.550: INFO: Pod "exec-volume-test-dynamicpv-5rsp": Phase="Pending", Reason="", readiness=false. Elapsed: 25.347052701s
Sep 27 07:51:37.653: INFO: Pod "exec-volume-test-dynamicpv-5rsp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 27.450927855s
STEP: Saw pod success
Sep 27 07:51:37.653: INFO: Pod "exec-volume-test-dynamicpv-5rsp" satisfied condition "Succeeded or Failed"
Sep 27 07:51:37.756: INFO: Trying to get logs from node ip-172-20-56-87.eu-west-3.compute.internal pod exec-volume-test-dynamicpv-5rsp container exec-container-dynamicpv-5rsp: <nil>
STEP: delete the pod
Sep 27 07:51:37.974: INFO: Waiting for pod exec-volume-test-dynamicpv-5rsp to disappear
Sep 27 07:51:38.075: INFO: Pod exec-volume-test-dynamicpv-5rsp no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-5rsp
Sep 27 07:51:38.075: INFO: Deleting pod "exec-volume-test-dynamicpv-5rsp" in namespace "volume-9066"
... skipping 38 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.8TytcAgTJ/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.8TytcAgTJ/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.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 216 lines ...
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 27 07:52:53.123: 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.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Sep 27 07:52:53.743: INFO: found topology map[topology.ebs.csi.aws.com/zone:eu-west-3a]
Sep 27 07:52:53.744: 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.928 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.8TytcAgTJ/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.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

    Not enough topologies in cluster -- skipping

    /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 312 lines ...
Sep 27 07:52:20.835: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3677xwn44
STEP: creating a claim
Sep 27 07:52:20.937: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-2p9f
STEP: Creating a pod to test subpath
Sep 27 07:52:21.248: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-2p9f" in namespace "provisioning-3677" to be "Succeeded or Failed"
Sep 27 07:52:21.350: INFO: Pod "pod-subpath-test-dynamicpv-2p9f": Phase="Pending", Reason="", readiness=false. Elapsed: 102.107859ms
Sep 27 07:52:23.453: INFO: Pod "pod-subpath-test-dynamicpv-2p9f": Phase="Pending", Reason="", readiness=false. Elapsed: 2.205133077s
Sep 27 07:52:25.556: INFO: Pod "pod-subpath-test-dynamicpv-2p9f": Phase="Pending", Reason="", readiness=false. Elapsed: 4.308502565s
Sep 27 07:52:27.663: INFO: Pod "pod-subpath-test-dynamicpv-2p9f": Phase="Pending", Reason="", readiness=false. Elapsed: 6.414888023s
Sep 27 07:52:29.767: INFO: Pod "pod-subpath-test-dynamicpv-2p9f": Phase="Pending", Reason="", readiness=false. Elapsed: 8.518802502s
Sep 27 07:52:31.869: INFO: Pod "pod-subpath-test-dynamicpv-2p9f": Phase="Pending", Reason="", readiness=false. Elapsed: 10.621705994s
... skipping 2 lines ...
Sep 27 07:52:38.182: INFO: Pod "pod-subpath-test-dynamicpv-2p9f": Phase="Pending", Reason="", readiness=false. Elapsed: 16.934393484s
Sep 27 07:52:40.285: INFO: Pod "pod-subpath-test-dynamicpv-2p9f": Phase="Pending", Reason="", readiness=false. Elapsed: 19.037654576s
Sep 27 07:52:42.388: INFO: Pod "pod-subpath-test-dynamicpv-2p9f": Phase="Pending", Reason="", readiness=false. Elapsed: 21.140255986s
Sep 27 07:52:44.492: INFO: Pod "pod-subpath-test-dynamicpv-2p9f": Phase="Pending", Reason="", readiness=false. Elapsed: 23.243954129s
Sep 27 07:52:46.596: INFO: Pod "pod-subpath-test-dynamicpv-2p9f": Phase="Succeeded", Reason="", readiness=false. Elapsed: 25.348459574s
STEP: Saw pod success
Sep 27 07:52:46.596: INFO: Pod "pod-subpath-test-dynamicpv-2p9f" satisfied condition "Succeeded or Failed"
Sep 27 07:52:46.698: INFO: Trying to get logs from node ip-172-20-55-93.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-2p9f container test-container-volume-dynamicpv-2p9f: <nil>
STEP: delete the pod
Sep 27 07:52:46.917: INFO: Waiting for pod pod-subpath-test-dynamicpv-2p9f to disappear
Sep 27 07:52:47.019: INFO: Pod pod-subpath-test-dynamicpv-2p9f no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-2p9f
Sep 27 07:52:47.019: INFO: Deleting pod "pod-subpath-test-dynamicpv-2p9f" in namespace "provisioning-3677"
... skipping 184 lines ...
Sep 27 07:52:18.001: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3823-e2e-sc8l99x
STEP: creating a claim
Sep 27 07:52:18.106: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-hjlh
STEP: Creating a pod to test subpath
Sep 27 07:52:18.425: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-hjlh" in namespace "provisioning-3823" to be "Succeeded or Failed"
Sep 27 07:52:18.528: INFO: Pod "pod-subpath-test-dynamicpv-hjlh": Phase="Pending", Reason="", readiness=false. Elapsed: 103.495922ms
Sep 27 07:52:20.633: INFO: Pod "pod-subpath-test-dynamicpv-hjlh": Phase="Pending", Reason="", readiness=false. Elapsed: 2.208131086s
Sep 27 07:52:22.741: INFO: Pod "pod-subpath-test-dynamicpv-hjlh": Phase="Pending", Reason="", readiness=false. Elapsed: 4.316581857s
Sep 27 07:52:24.845: INFO: Pod "pod-subpath-test-dynamicpv-hjlh": Phase="Pending", Reason="", readiness=false. Elapsed: 6.420244315s
Sep 27 07:52:26.949: INFO: Pod "pod-subpath-test-dynamicpv-hjlh": Phase="Pending", Reason="", readiness=false. Elapsed: 8.52432964s
Sep 27 07:52:29.055: INFO: Pod "pod-subpath-test-dynamicpv-hjlh": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.630606358s
STEP: Saw pod success
Sep 27 07:52:29.055: INFO: Pod "pod-subpath-test-dynamicpv-hjlh" satisfied condition "Succeeded or Failed"
Sep 27 07:52:29.160: INFO: Trying to get logs from node ip-172-20-54-99.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-hjlh container test-container-volume-dynamicpv-hjlh: <nil>
STEP: delete the pod
Sep 27 07:52:29.401: INFO: Waiting for pod pod-subpath-test-dynamicpv-hjlh to disappear
Sep 27 07:52:29.522: INFO: Pod pod-subpath-test-dynamicpv-hjlh no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-hjlh
Sep 27 07:52:29.522: INFO: Deleting pod "pod-subpath-test-dynamicpv-hjlh" in namespace "provisioning-3823"
... skipping 34 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.8TytcAgTJ/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.8TytcAgTJ/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.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 12 lines ...
Sep 27 07:52:14.349: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-3982jwzl4
STEP: creating a claim
Sep 27 07:52:14.468: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-mqq7
STEP: Creating a pod to test exec-volume-test
Sep 27 07:52:14.777: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-mqq7" in namespace "volume-3982" to be "Succeeded or Failed"
Sep 27 07:52:14.878: INFO: Pod "exec-volume-test-dynamicpv-mqq7": Phase="Pending", Reason="", readiness=false. Elapsed: 101.126538ms
Sep 27 07:52:16.986: INFO: Pod "exec-volume-test-dynamicpv-mqq7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.209038096s
Sep 27 07:52:19.089: INFO: Pod "exec-volume-test-dynamicpv-mqq7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.311926566s
Sep 27 07:52:21.191: INFO: Pod "exec-volume-test-dynamicpv-mqq7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.413858328s
Sep 27 07:52:23.297: INFO: Pod "exec-volume-test-dynamicpv-mqq7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.519672323s
Sep 27 07:52:25.398: INFO: Pod "exec-volume-test-dynamicpv-mqq7": Phase="Pending", Reason="", readiness=false. Elapsed: 10.621372893s
... skipping 2 lines ...
Sep 27 07:52:31.704: INFO: Pod "exec-volume-test-dynamicpv-mqq7": Phase="Pending", Reason="", readiness=false. Elapsed: 16.926616575s
Sep 27 07:52:33.805: INFO: Pod "exec-volume-test-dynamicpv-mqq7": Phase="Pending", Reason="", readiness=false. Elapsed: 19.027999847s
Sep 27 07:52:35.907: INFO: Pod "exec-volume-test-dynamicpv-mqq7": Phase="Pending", Reason="", readiness=false. Elapsed: 21.129960276s
Sep 27 07:52:38.009: INFO: Pod "exec-volume-test-dynamicpv-mqq7": Phase="Pending", Reason="", readiness=false. Elapsed: 23.231742866s
Sep 27 07:52:40.110: INFO: Pod "exec-volume-test-dynamicpv-mqq7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 25.333477606s
STEP: Saw pod success
Sep 27 07:52:40.110: INFO: Pod "exec-volume-test-dynamicpv-mqq7" satisfied condition "Succeeded or Failed"
Sep 27 07:52:40.211: INFO: Trying to get logs from node ip-172-20-56-87.eu-west-3.compute.internal pod exec-volume-test-dynamicpv-mqq7 container exec-container-dynamicpv-mqq7: <nil>
STEP: delete the pod
Sep 27 07:52:40.424: INFO: Waiting for pod exec-volume-test-dynamicpv-mqq7 to disappear
Sep 27 07:52:40.530: INFO: Pod exec-volume-test-dynamicpv-mqq7 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-mqq7
Sep 27 07:52:40.530: INFO: Deleting pod "exec-volume-test-dynamicpv-mqq7" in namespace "volume-3982"
... skipping 136 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.8TytcAgTJ/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.8TytcAgTJ/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.8TytcAgTJ/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.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 75 lines ...
Sep 27 07:51:51.661: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-8261vmk7p
STEP: creating a claim
Sep 27 07:51:51.765: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-mw2l
STEP: Creating a pod to test exec-volume-test
Sep 27 07:51:52.080: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-mw2l" in namespace "volume-8261" to be "Succeeded or Failed"
Sep 27 07:51:52.184: INFO: Pod "exec-volume-test-dynamicpv-mw2l": Phase="Pending", Reason="", readiness=false. Elapsed: 103.678129ms
Sep 27 07:51:54.287: INFO: Pod "exec-volume-test-dynamicpv-mw2l": Phase="Pending", Reason="", readiness=false. Elapsed: 2.206925542s
Sep 27 07:51:56.391: INFO: Pod "exec-volume-test-dynamicpv-mw2l": Phase="Pending", Reason="", readiness=false. Elapsed: 4.311314557s
Sep 27 07:51:58.497: INFO: Pod "exec-volume-test-dynamicpv-mw2l": Phase="Pending", Reason="", readiness=false. Elapsed: 6.417328177s
Sep 27 07:52:00.606: INFO: Pod "exec-volume-test-dynamicpv-mw2l": Phase="Pending", Reason="", readiness=false. Elapsed: 8.526272726s
Sep 27 07:52:02.710: INFO: Pod "exec-volume-test-dynamicpv-mw2l": Phase="Pending", Reason="", readiness=false. Elapsed: 10.629980583s
... skipping 8 lines ...
Sep 27 07:52:21.657: INFO: Pod "exec-volume-test-dynamicpv-mw2l": Phase="Pending", Reason="", readiness=false. Elapsed: 29.577094679s
Sep 27 07:52:23.764: INFO: Pod "exec-volume-test-dynamicpv-mw2l": Phase="Pending", Reason="", readiness=false. Elapsed: 31.683477423s
Sep 27 07:52:25.868: INFO: Pod "exec-volume-test-dynamicpv-mw2l": Phase="Pending", Reason="", readiness=false. Elapsed: 33.788028493s
Sep 27 07:52:27.972: INFO: Pod "exec-volume-test-dynamicpv-mw2l": Phase="Pending", Reason="", readiness=false. Elapsed: 35.891677206s
Sep 27 07:52:30.076: INFO: Pod "exec-volume-test-dynamicpv-mw2l": Phase="Succeeded", Reason="", readiness=false. Elapsed: 37.996079664s
STEP: Saw pod success
Sep 27 07:52:30.076: INFO: Pod "exec-volume-test-dynamicpv-mw2l" satisfied condition "Succeeded or Failed"
Sep 27 07:52:30.179: INFO: Trying to get logs from node ip-172-20-54-99.eu-west-3.compute.internal pod exec-volume-test-dynamicpv-mw2l container exec-container-dynamicpv-mw2l: <nil>
STEP: delete the pod
Sep 27 07:52:30.392: INFO: Waiting for pod exec-volume-test-dynamicpv-mw2l to disappear
Sep 27 07:52:30.496: INFO: Pod exec-volume-test-dynamicpv-mw2l no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-mw2l
Sep 27 07:52:30.496: INFO: Deleting pod "exec-volume-test-dynamicpv-mw2l" in namespace "volume-8261"
... skipping 40 lines ...
Sep 27 07:51:51.278: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5330nsflr
STEP: creating a claim
Sep 27 07:51:51.382: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-nt6h
STEP: Creating a pod to test atomic-volume-subpath
Sep 27 07:51:51.697: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-nt6h" in namespace "provisioning-5330" to be "Succeeded or Failed"
Sep 27 07:51:51.801: INFO: Pod "pod-subpath-test-dynamicpv-nt6h": Phase="Pending", Reason="", readiness=false. Elapsed: 103.538006ms
Sep 27 07:51:53.904: INFO: Pod "pod-subpath-test-dynamicpv-nt6h": Phase="Pending", Reason="", readiness=false. Elapsed: 2.206987314s
Sep 27 07:51:56.012: INFO: Pod "pod-subpath-test-dynamicpv-nt6h": Phase="Pending", Reason="", readiness=false. Elapsed: 4.31408416s
Sep 27 07:51:58.116: INFO: Pod "pod-subpath-test-dynamicpv-nt6h": Phase="Pending", Reason="", readiness=false. Elapsed: 6.41888309s
Sep 27 07:52:00.219: INFO: Pod "pod-subpath-test-dynamicpv-nt6h": Phase="Pending", Reason="", readiness=false. Elapsed: 8.521966732s
Sep 27 07:52:02.324: INFO: Pod "pod-subpath-test-dynamicpv-nt6h": Phase="Pending", Reason="", readiness=false. Elapsed: 10.626364765s
... skipping 18 lines ...
Sep 27 07:52:42.313: INFO: Pod "pod-subpath-test-dynamicpv-nt6h": Phase="Running", Reason="", readiness=true. Elapsed: 50.615260934s
Sep 27 07:52:44.416: INFO: Pod "pod-subpath-test-dynamicpv-nt6h": Phase="Running", Reason="", readiness=true. Elapsed: 52.718577886s
Sep 27 07:52:46.519: INFO: Pod "pod-subpath-test-dynamicpv-nt6h": Phase="Running", Reason="", readiness=true. Elapsed: 54.821641023s
Sep 27 07:52:48.623: INFO: Pod "pod-subpath-test-dynamicpv-nt6h": Phase="Running", Reason="", readiness=true. Elapsed: 56.925751392s
Sep 27 07:52:50.728: INFO: Pod "pod-subpath-test-dynamicpv-nt6h": Phase="Succeeded", Reason="", readiness=false. Elapsed: 59.030359154s
STEP: Saw pod success
Sep 27 07:52:50.728: INFO: Pod "pod-subpath-test-dynamicpv-nt6h" satisfied condition "Succeeded or Failed"
Sep 27 07:52:50.831: INFO: Trying to get logs from node ip-172-20-55-93.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-nt6h container test-container-subpath-dynamicpv-nt6h: <nil>
STEP: delete the pod
Sep 27 07:52:51.047: INFO: Waiting for pod pod-subpath-test-dynamicpv-nt6h to disappear
Sep 27 07:52:51.150: INFO: Pod pod-subpath-test-dynamicpv-nt6h no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-nt6h
Sep 27 07:52:51.150: INFO: Deleting pod "pod-subpath-test-dynamicpv-nt6h" in namespace "provisioning-5330"
... skipping 192 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 27 07:52:46.370: 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.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Sep 27 07:52:46.887: INFO: Creating resource for dynamic PV
Sep 27 07:52:46.887: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7963-e2e-sc92gdt
STEP: creating a claim
Sep 27 07:52:46.992: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-wxjp
STEP: Checking for subpath error in container status
Sep 27 07:52:59.528: INFO: Deleting pod "pod-subpath-test-dynamicpv-wxjp" in namespace "provisioning-7963"
Sep 27 07:52:59.637: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-wxjp" to be fully deleted
STEP: Deleting pod
Sep 27 07:53:01.844: INFO: Deleting pod "pod-subpath-test-dynamicpv-wxjp" in namespace "provisioning-7963"
STEP: Deleting pvc
Sep 27 07:53:02.153: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comgwxmx"
... skipping 11 lines ...

• [SLOW TEST:31.623 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath file is outside the volume [Slow][LinuxOnly]
    /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
S
------------------------------
[BeforeEach] [Testpattern: Inline-volume (ext3)] volumes
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
... skipping 56 lines ...
Sep 27 07:52:30.525: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-4899jqwcg
STEP: creating a claim
Sep 27 07:52:30.631: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-7wsm
STEP: Creating a pod to test exec-volume-test
Sep 27 07:52:30.948: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-7wsm" in namespace "volume-4899" to be "Succeeded or Failed"
Sep 27 07:52:31.051: INFO: Pod "exec-volume-test-dynamicpv-7wsm": Phase="Pending", Reason="", readiness=false. Elapsed: 103.34644ms
Sep 27 07:52:33.156: INFO: Pod "exec-volume-test-dynamicpv-7wsm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.208284043s
Sep 27 07:52:35.261: INFO: Pod "exec-volume-test-dynamicpv-7wsm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.312650148s
Sep 27 07:52:37.366: INFO: Pod "exec-volume-test-dynamicpv-7wsm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.418215319s
Sep 27 07:52:39.476: INFO: Pod "exec-volume-test-dynamicpv-7wsm": Phase="Pending", Reason="", readiness=false. Elapsed: 8.527886384s
Sep 27 07:52:41.580: INFO: Pod "exec-volume-test-dynamicpv-7wsm": Phase="Pending", Reason="", readiness=false. Elapsed: 10.631584324s
Sep 27 07:52:43.685: INFO: Pod "exec-volume-test-dynamicpv-7wsm": Phase="Pending", Reason="", readiness=false. Elapsed: 12.736511047s
Sep 27 07:52:45.789: INFO: Pod "exec-volume-test-dynamicpv-7wsm": Phase="Pending", Reason="", readiness=false. Elapsed: 14.840565224s
Sep 27 07:52:47.893: INFO: Pod "exec-volume-test-dynamicpv-7wsm": Phase="Pending", Reason="", readiness=false. Elapsed: 16.944627553s
Sep 27 07:52:50.001: INFO: Pod "exec-volume-test-dynamicpv-7wsm": Phase="Pending", Reason="", readiness=false. Elapsed: 19.053246996s
Sep 27 07:52:52.110: INFO: Pod "exec-volume-test-dynamicpv-7wsm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.161733502s
STEP: Saw pod success
Sep 27 07:52:52.110: INFO: Pod "exec-volume-test-dynamicpv-7wsm" satisfied condition "Succeeded or Failed"
Sep 27 07:52:52.213: INFO: Trying to get logs from node ip-172-20-54-99.eu-west-3.compute.internal pod exec-volume-test-dynamicpv-7wsm container exec-container-dynamicpv-7wsm: <nil>
STEP: delete the pod
Sep 27 07:52:52.428: INFO: Waiting for pod exec-volume-test-dynamicpv-7wsm to disappear
Sep 27 07:52:52.535: INFO: Pod exec-volume-test-dynamicpv-7wsm no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-7wsm
Sep 27 07:52:52.535: INFO: Deleting pod "exec-volume-test-dynamicpv-7wsm" in namespace "volume-4899"
... skipping 149 lines ...
Sep 27 07:52:30.159: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2966wv5cn
STEP: creating a claim
Sep 27 07:52:30.263: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-7tfb
STEP: Creating a pod to test subpath
Sep 27 07:52:30.575: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-7tfb" in namespace "provisioning-2966" to be "Succeeded or Failed"
Sep 27 07:52:30.678: INFO: Pod "pod-subpath-test-dynamicpv-7tfb": Phase="Pending", Reason="", readiness=false. Elapsed: 103.051922ms
Sep 27 07:52:32.786: INFO: Pod "pod-subpath-test-dynamicpv-7tfb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.210851472s
Sep 27 07:52:34.891: INFO: Pod "pod-subpath-test-dynamicpv-7tfb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.31553852s
Sep 27 07:52:36.995: INFO: Pod "pod-subpath-test-dynamicpv-7tfb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.419937798s
Sep 27 07:52:39.100: INFO: Pod "pod-subpath-test-dynamicpv-7tfb": Phase="Pending", Reason="", readiness=false. Elapsed: 8.524424866s
Sep 27 07:52:41.204: INFO: Pod "pod-subpath-test-dynamicpv-7tfb": Phase="Pending", Reason="", readiness=false. Elapsed: 10.628766839s
Sep 27 07:52:43.308: INFO: Pod "pod-subpath-test-dynamicpv-7tfb": Phase="Pending", Reason="", readiness=false. Elapsed: 12.733063638s
Sep 27 07:52:45.412: INFO: Pod "pod-subpath-test-dynamicpv-7tfb": Phase="Pending", Reason="", readiness=false. Elapsed: 14.836591195s
Sep 27 07:52:47.520: INFO: Pod "pod-subpath-test-dynamicpv-7tfb": Phase="Pending", Reason="", readiness=false. Elapsed: 16.944860521s
Sep 27 07:52:49.626: INFO: Pod "pod-subpath-test-dynamicpv-7tfb": Phase="Pending", Reason="", readiness=false. Elapsed: 19.050542204s
Sep 27 07:52:51.730: INFO: Pod "pod-subpath-test-dynamicpv-7tfb": Phase="Pending", Reason="", readiness=false. Elapsed: 21.154369274s
Sep 27 07:52:53.835: INFO: Pod "pod-subpath-test-dynamicpv-7tfb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.259255668s
STEP: Saw pod success
Sep 27 07:52:53.835: INFO: Pod "pod-subpath-test-dynamicpv-7tfb" satisfied condition "Succeeded or Failed"
Sep 27 07:52:53.938: INFO: Trying to get logs from node ip-172-20-54-99.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-7tfb container test-container-subpath-dynamicpv-7tfb: <nil>
STEP: delete the pod
Sep 27 07:52:54.153: INFO: Waiting for pod pod-subpath-test-dynamicpv-7tfb to disappear
Sep 27 07:52:54.256: INFO: Pod pod-subpath-test-dynamicpv-7tfb no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-7tfb
Sep 27 07:52:54.256: INFO: Deleting pod "pod-subpath-test-dynamicpv-7tfb" in namespace "provisioning-2966"
... skipping 76 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 27 07:52:40.927: 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.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Sep 27 07:52:41.446: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Sep 27 07:52:42.136: INFO: Successfully created a new PD: "aws://eu-west-3a/vol-0d8e9d3675878a9a5".
Sep 27 07:52:42.136: INFO: Creating resource for pre-provisioned PV
Sep 27 07:52:42.136: INFO: Creating PVC and PV
... skipping 6 lines ...
Sep 27 07:52:48.857: INFO: PersistentVolumeClaim pvc-nfvwn found but phase is Pending instead of Bound.
Sep 27 07:52:50.961: INFO: PersistentVolumeClaim pvc-nfvwn found but phase is Pending instead of Bound.
Sep 27 07:52:53.071: INFO: PersistentVolumeClaim pvc-nfvwn found and phase=Bound (10.637122249s)
Sep 27 07:52:53.071: INFO: Waiting up to 3m0s for PersistentVolume aws-42ltn to have phase Bound
Sep 27 07:52:53.178: INFO: PersistentVolume aws-42ltn found and phase=Bound (106.686677ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Sep 27 07:52:55.810: INFO: Deleting pod "pod-a69df3af-dd7d-408b-ad51-a22d7ac0a4d8" in namespace "volumemode-5429"
Sep 27 07:52:55.926: INFO: Wait up to 5m0s for pod "pod-a69df3af-dd7d-408b-ad51-a22d7ac0a4d8" to be fully deleted
STEP: Deleting pv and pvc
Sep 27 07:52:58.139: INFO: Deleting PersistentVolumeClaim "pvc-nfvwn"
Sep 27 07:52:58.244: INFO: Deleting PersistentVolume "aws-42ltn"
Sep 27 07:52:58.566: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0d8e9d3675878a9a5", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d8e9d3675878a9a5 is currently attached to i-03991f0757f6206b7
	status code: 400, request id: a83a5f6c-fae5-48c5-8c01-af2c62af280b
Sep 27 07:53:04.124: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0d8e9d3675878a9a5", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d8e9d3675878a9a5 is currently attached to i-03991f0757f6206b7
	status code: 400, request id: dfc081a0-c4b8-4683-80f3-a67e00c31ce3
Sep 27 07:53:09.688: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0d8e9d3675878a9a5", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d8e9d3675878a9a5 is currently attached to i-03991f0757f6206b7
	status code: 400, request id: 13842d34-0f91-48d6-95a7-b7d12015fac0
Sep 27 07:53:15.248: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0d8e9d3675878a9a5", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d8e9d3675878a9a5 is currently attached to i-03991f0757f6206b7
	status code: 400, request id: 282105c5-68f3-4321-b4ae-96633669c7d7
Sep 27 07:53:20.837: INFO: Successfully deleted PD "aws://eu-west-3a/vol-0d8e9d3675878a9a5".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 27 07:53:20.837: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-5429" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.8TytcAgTJ/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.8TytcAgTJ/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
    /tmp/kops.8TytcAgTJ/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.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
S
------------------------------
[BeforeEach] [sig-storage] Storage Policy Based Volume Provisioning [Feature:vsphere]
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 35 lines ...
Sep 27 07:51:35.712: INFO: Creating resource for dynamic PV
Sep 27 07:51:35.712: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9846-e2e-scljs9z
STEP: creating a claim
Sep 27 07:51:35.817: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-9846
Sep 27 07:51:36.131: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-9846" in namespace "provisioning-9846" to be "Succeeded or Failed"
Sep 27 07:51:36.239: INFO: Pod "volume-prep-provisioning-9846": Phase="Pending", Reason="", readiness=false. Elapsed: 108.19608ms
Sep 27 07:51:38.344: INFO: Pod "volume-prep-provisioning-9846": Phase="Pending", Reason="", readiness=false. Elapsed: 2.212653316s
Sep 27 07:51:40.448: INFO: Pod "volume-prep-provisioning-9846": Phase="Pending", Reason="", readiness=false. Elapsed: 4.317101948s
Sep 27 07:51:42.552: INFO: Pod "volume-prep-provisioning-9846": Phase="Pending", Reason="", readiness=false. Elapsed: 6.421132887s
Sep 27 07:51:44.656: INFO: Pod "volume-prep-provisioning-9846": Phase="Pending", Reason="", readiness=false. Elapsed: 8.525190909s
Sep 27 07:51:46.762: INFO: Pod "volume-prep-provisioning-9846": Phase="Pending", Reason="", readiness=false. Elapsed: 10.630911281s
... skipping 8 lines ...
Sep 27 07:52:05.712: INFO: Pod "volume-prep-provisioning-9846": Phase="Pending", Reason="", readiness=false. Elapsed: 29.581307652s
Sep 27 07:52:07.819: INFO: Pod "volume-prep-provisioning-9846": Phase="Pending", Reason="", readiness=false. Elapsed: 31.687897188s
Sep 27 07:52:09.923: INFO: Pod "volume-prep-provisioning-9846": Phase="Pending", Reason="", readiness=false. Elapsed: 33.792193034s
Sep 27 07:52:12.028: INFO: Pod "volume-prep-provisioning-9846": Phase="Pending", Reason="", readiness=false. Elapsed: 35.896646085s
Sep 27 07:52:14.131: INFO: Pod "volume-prep-provisioning-9846": Phase="Succeeded", Reason="", readiness=false. Elapsed: 38.000555623s
STEP: Saw pod success
Sep 27 07:52:14.132: INFO: Pod "volume-prep-provisioning-9846" satisfied condition "Succeeded or Failed"
Sep 27 07:52:14.132: INFO: Deleting pod "volume-prep-provisioning-9846" in namespace "provisioning-9846"
Sep 27 07:52:14.239: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-9846" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-rgvw
STEP: Checking for subpath error in container status
Sep 27 07:52:48.675: INFO: Deleting pod "pod-subpath-test-dynamicpv-rgvw" in namespace "provisioning-9846"
Sep 27 07:52:48.784: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-rgvw" to be fully deleted
STEP: Deleting pod
Sep 27 07:52:48.888: INFO: Deleting pod "pod-subpath-test-dynamicpv-rgvw" in namespace "provisioning-9846"
STEP: Deleting pvc
Sep 27 07:52:49.199: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comvktx7"
... skipping 88 lines ...
Sep 27 07:53:16.041: INFO: Pod aws-client still exists
Sep 27 07:53:18.042: INFO: Waiting for pod aws-client to disappear
Sep 27 07:53:18.145: INFO: Pod aws-client still exists
Sep 27 07:53:20.041: INFO: Waiting for pod aws-client to disappear
Sep 27 07:53:20.143: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Sep 27 07:53:20.333: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0333520c4afa70a2b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0333520c4afa70a2b is currently attached to i-0dcb927116601f3cf
	status code: 400, request id: 7e674db7-069d-4720-8404-afb5bb897cba
Sep 27 07:53:25.887: INFO: Successfully deleted PD "aws://eu-west-3a/vol-0333520c4afa70a2b".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 27 07:53:25.887: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-3813" for this suite.
... skipping 291 lines ...
Sep 27 07:52:34.806: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7425j9htv
STEP: creating a claim
Sep 27 07:52:34.910: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-6grp
STEP: Creating a pod to test subpath
Sep 27 07:52:35.223: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-6grp" in namespace "provisioning-7425" to be "Succeeded or Failed"
Sep 27 07:52:35.325: INFO: Pod "pod-subpath-test-dynamicpv-6grp": Phase="Pending", Reason="", readiness=false. Elapsed: 101.649629ms
Sep 27 07:52:37.429: INFO: Pod "pod-subpath-test-dynamicpv-6grp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.20566551s
Sep 27 07:52:39.532: INFO: Pod "pod-subpath-test-dynamicpv-6grp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.308863271s
Sep 27 07:52:41.653: INFO: Pod "pod-subpath-test-dynamicpv-6grp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.430098092s
Sep 27 07:52:43.756: INFO: Pod "pod-subpath-test-dynamicpv-6grp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.532524042s
Sep 27 07:52:45.858: INFO: Pod "pod-subpath-test-dynamicpv-6grp": Phase="Pending", Reason="", readiness=false. Elapsed: 10.634929303s
... skipping 2 lines ...
Sep 27 07:52:52.171: INFO: Pod "pod-subpath-test-dynamicpv-6grp": Phase="Pending", Reason="", readiness=false. Elapsed: 16.947807006s
Sep 27 07:52:54.274: INFO: Pod "pod-subpath-test-dynamicpv-6grp": Phase="Pending", Reason="", readiness=false. Elapsed: 19.050969927s
Sep 27 07:52:56.377: INFO: Pod "pod-subpath-test-dynamicpv-6grp": Phase="Pending", Reason="", readiness=false. Elapsed: 21.153445568s
Sep 27 07:52:58.480: INFO: Pod "pod-subpath-test-dynamicpv-6grp": Phase="Pending", Reason="", readiness=false. Elapsed: 23.256443961s
Sep 27 07:53:00.584: INFO: Pod "pod-subpath-test-dynamicpv-6grp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 25.360469092s
STEP: Saw pod success
Sep 27 07:53:00.584: INFO: Pod "pod-subpath-test-dynamicpv-6grp" satisfied condition "Succeeded or Failed"
Sep 27 07:53:00.686: INFO: Trying to get logs from node ip-172-20-54-99.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-6grp container test-container-subpath-dynamicpv-6grp: <nil>
STEP: delete the pod
Sep 27 07:53:00.898: INFO: Waiting for pod pod-subpath-test-dynamicpv-6grp to disappear
Sep 27 07:53:01.000: INFO: Pod pod-subpath-test-dynamicpv-6grp no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-6grp
Sep 27 07:53:01.000: INFO: Deleting pod "pod-subpath-test-dynamicpv-6grp" in namespace "provisioning-7425"
STEP: Creating pod pod-subpath-test-dynamicpv-6grp
STEP: Creating a pod to test subpath
Sep 27 07:53:01.205: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-6grp" in namespace "provisioning-7425" to be "Succeeded or Failed"
Sep 27 07:53:01.307: INFO: Pod "pod-subpath-test-dynamicpv-6grp": Phase="Pending", Reason="", readiness=false. Elapsed: 101.884875ms
Sep 27 07:53:03.417: INFO: Pod "pod-subpath-test-dynamicpv-6grp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.212049497s
Sep 27 07:53:05.519: INFO: Pod "pod-subpath-test-dynamicpv-6grp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.314782656s
Sep 27 07:53:07.622: INFO: Pod "pod-subpath-test-dynamicpv-6grp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.417686095s
STEP: Saw pod success
Sep 27 07:53:07.622: INFO: Pod "pod-subpath-test-dynamicpv-6grp" satisfied condition "Succeeded or Failed"
Sep 27 07:53:07.744: INFO: Trying to get logs from node ip-172-20-54-99.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-6grp container test-container-subpath-dynamicpv-6grp: <nil>
STEP: delete the pod
Sep 27 07:53:07.955: INFO: Waiting for pod pod-subpath-test-dynamicpv-6grp to disappear
Sep 27 07:53:08.064: INFO: Pod pod-subpath-test-dynamicpv-6grp no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-6grp
Sep 27 07:53:08.064: INFO: Deleting pod "pod-subpath-test-dynamicpv-6grp" in namespace "provisioning-7425"
... skipping 38 lines ...
Sep 27 07:53:07.476: INFO: Creating resource for dynamic PV
Sep 27 07:53:07.476: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-1620-e2e-sc25k4b
STEP: creating a claim
STEP: Expanding non-expandable pvc
Sep 27 07:53:07.803: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Sep 27 07:53:08.012: INFO: Error updating pvc ebs.csi.aws.commslfz: PersistentVolumeClaim "ebs.csi.aws.commslfz" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-1620-e2e-sc25k4b",
  	... // 3 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Sep 27 07:53:38.430: INFO: Error updating pvc ebs.csi.aws.commslfz: PersistentVolumeClaim "ebs.csi.aws.commslfz" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 110 lines ...
Sep 27 07:52:28.026: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-2595xr57r      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-2595    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-2595xr57r,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-2595    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-2595xr57r,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-2595    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-2595xr57r,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-2595xr57r    ae22f6e8-5fcc-403b-aff0-b89fdd45a783 7782 0 2021-09-27 07:52:28 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-09-27 07:52:28 +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-sr5sq pvc- provisioning-2595  09a26e26-f24b-42b0-9fd9-a9f5d0737f70 7804 0 2021-09-27 07:52:28 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-09-27 07:52:28 +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-2595xr57r,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-ea9b7be4-63c2-4f55-a89e-97b457ebc8ee in namespace provisioning-2595
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Sep 27 07:52:41.180: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-pv9gc" in namespace "provisioning-2595" to be "Succeeded or Failed"
Sep 27 07:52:41.284: INFO: Pod "pvc-volume-tester-writer-pv9gc": Phase="Pending", Reason="", readiness=false. Elapsed: 103.614481ms
Sep 27 07:52:43.389: INFO: Pod "pvc-volume-tester-writer-pv9gc": Phase="Pending", Reason="", readiness=false. Elapsed: 2.208656857s
Sep 27 07:52:45.493: INFO: Pod "pvc-volume-tester-writer-pv9gc": Phase="Pending", Reason="", readiness=false. Elapsed: 4.312868173s
Sep 27 07:52:47.600: INFO: Pod "pvc-volume-tester-writer-pv9gc": Phase="Pending", Reason="", readiness=false. Elapsed: 6.419949963s
Sep 27 07:52:49.705: INFO: Pod "pvc-volume-tester-writer-pv9gc": Phase="Pending", Reason="", readiness=false. Elapsed: 8.524981719s
Sep 27 07:52:51.811: INFO: Pod "pvc-volume-tester-writer-pv9gc": Phase="Pending", Reason="", readiness=false. Elapsed: 10.630413334s
... skipping 7 lines ...
Sep 27 07:53:08.648: INFO: Pod "pvc-volume-tester-writer-pv9gc": Phase="Pending", Reason="", readiness=false. Elapsed: 27.46725644s
Sep 27 07:53:10.753: INFO: Pod "pvc-volume-tester-writer-pv9gc": Phase="Pending", Reason="", readiness=false. Elapsed: 29.572777851s
Sep 27 07:53:12.865: INFO: Pod "pvc-volume-tester-writer-pv9gc": Phase="Pending", Reason="", readiness=false. Elapsed: 31.684226158s
Sep 27 07:53:14.972: INFO: Pod "pvc-volume-tester-writer-pv9gc": Phase="Pending", Reason="", readiness=false. Elapsed: 33.791237924s
Sep 27 07:53:17.077: INFO: Pod "pvc-volume-tester-writer-pv9gc": Phase="Succeeded", Reason="", readiness=false. Elapsed: 35.896825873s
STEP: Saw pod success
Sep 27 07:53:17.077: INFO: Pod "pvc-volume-tester-writer-pv9gc" satisfied condition "Succeeded or Failed"
Sep 27 07:53:17.295: INFO: Pod pvc-volume-tester-writer-pv9gc has the following logs: 
Sep 27 07:53:17.295: INFO: Deleting pod "pvc-volume-tester-writer-pv9gc" in namespace "provisioning-2595"
Sep 27 07:53:17.435: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-pv9gc" to be fully deleted
STEP: checking the created volume has the correct mount options, is readable and retains data on the same node "ip-172-20-56-87.eu-west-3.compute.internal"
Sep 27 07:53:17.857: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-lhlr5" in namespace "provisioning-2595" to be "Succeeded or Failed"
Sep 27 07:53:17.962: INFO: Pod "pvc-volume-tester-reader-lhlr5": Phase="Pending", Reason="", readiness=false. Elapsed: 104.558964ms
Sep 27 07:53:20.068: INFO: Pod "pvc-volume-tester-reader-lhlr5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.211195634s
Sep 27 07:53:22.174: INFO: Pod "pvc-volume-tester-reader-lhlr5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.316447137s
Sep 27 07:53:24.278: INFO: Pod "pvc-volume-tester-reader-lhlr5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.421164842s
STEP: Saw pod success
Sep 27 07:53:24.278: INFO: Pod "pvc-volume-tester-reader-lhlr5" satisfied condition "Succeeded or Failed"
Sep 27 07:53:24.488: INFO: Pod pvc-volume-tester-reader-lhlr5 has the following logs: hello world

Sep 27 07:53:24.488: INFO: Deleting pod "pvc-volume-tester-reader-lhlr5" in namespace "provisioning-2595"
Sep 27 07:53:24.604: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-lhlr5" to be fully deleted
Sep 27 07:53:24.710: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-sr5sq] to have phase Bound
Sep 27 07:53:24.814: INFO: PersistentVolumeClaim pvc-sr5sq found and phase=Bound (103.985008ms)
... skipping 429 lines ...
Sep 27 07:53:06.739: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5340-e2e-sc29stc
STEP: creating a claim
Sep 27 07:53:06.844: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-tb6t
STEP: Creating a pod to test subpath
Sep 27 07:53:07.163: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-tb6t" in namespace "provisioning-5340" to be "Succeeded or Failed"
Sep 27 07:53:07.268: INFO: Pod "pod-subpath-test-dynamicpv-tb6t": Phase="Pending", Reason="", readiness=false. Elapsed: 103.978026ms
Sep 27 07:53:09.381: INFO: Pod "pod-subpath-test-dynamicpv-tb6t": Phase="Pending", Reason="", readiness=false. Elapsed: 2.217115789s
Sep 27 07:53:11.485: INFO: Pod "pod-subpath-test-dynamicpv-tb6t": Phase="Pending", Reason="", readiness=false. Elapsed: 4.320987421s
Sep 27 07:53:13.590: INFO: Pod "pod-subpath-test-dynamicpv-tb6t": Phase="Pending", Reason="", readiness=false. Elapsed: 6.426426631s
Sep 27 07:53:15.697: INFO: Pod "pod-subpath-test-dynamicpv-tb6t": Phase="Pending", Reason="", readiness=false. Elapsed: 8.533760437s
Sep 27 07:53:17.802: INFO: Pod "pod-subpath-test-dynamicpv-tb6t": Phase="Pending", Reason="", readiness=false. Elapsed: 10.638678667s
... skipping 2 lines ...
Sep 27 07:53:24.119: INFO: Pod "pod-subpath-test-dynamicpv-tb6t": Phase="Pending", Reason="", readiness=false. Elapsed: 16.95586483s
Sep 27 07:53:26.239: INFO: Pod "pod-subpath-test-dynamicpv-tb6t": Phase="Pending", Reason="", readiness=false. Elapsed: 19.075898753s
Sep 27 07:53:28.344: INFO: Pod "pod-subpath-test-dynamicpv-tb6t": Phase="Pending", Reason="", readiness=false. Elapsed: 21.180428812s
Sep 27 07:53:30.448: INFO: Pod "pod-subpath-test-dynamicpv-tb6t": Phase="Pending", Reason="", readiness=false. Elapsed: 23.28433329s
Sep 27 07:53:32.552: INFO: Pod "pod-subpath-test-dynamicpv-tb6t": Phase="Succeeded", Reason="", readiness=false. Elapsed: 25.388269893s
STEP: Saw pod success
Sep 27 07:53:32.552: INFO: Pod "pod-subpath-test-dynamicpv-tb6t" satisfied condition "Succeeded or Failed"
Sep 27 07:53:32.655: INFO: Trying to get logs from node ip-172-20-54-99.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-tb6t container test-container-subpath-dynamicpv-tb6t: <nil>
STEP: delete the pod
Sep 27 07:53:32.873: INFO: Waiting for pod pod-subpath-test-dynamicpv-tb6t to disappear
Sep 27 07:53:32.979: INFO: Pod pod-subpath-test-dynamicpv-tb6t no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-tb6t
Sep 27 07:53:32.979: INFO: Deleting pod "pod-subpath-test-dynamicpv-tb6t" in namespace "provisioning-5340"
... skipping 91 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.000 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.8TytcAgTJ/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.8TytcAgTJ/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.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 154 lines ...
Sep 27 07:53:34.048: INFO: Waiting for pod aws-client to disappear
Sep 27 07:53:34.157: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Sep 27 07:53:34.158: INFO: Deleting PersistentVolumeClaim "pvc-4bmzw"
Sep 27 07:53:34.261: INFO: Deleting PersistentVolume "aws-6lzxt"
Sep 27 07:53:34.625: INFO: Couldn't delete PD "aws://eu-west-3a/vol-036388211a9a64f37", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-036388211a9a64f37 is currently attached to i-0af665c181bc566c8
	status code: 400, request id: e5133423-9ba9-4eee-a862-c631293e8a5d
Sep 27 07:53:40.160: INFO: Couldn't delete PD "aws://eu-west-3a/vol-036388211a9a64f37", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-036388211a9a64f37 is currently attached to i-0af665c181bc566c8
	status code: 400, request id: 24ace9ba-79a0-4156-b830-72edda9a2316
Sep 27 07:53:45.706: INFO: Couldn't delete PD "aws://eu-west-3a/vol-036388211a9a64f37", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-036388211a9a64f37 is currently attached to i-0af665c181bc566c8
	status code: 400, request id: 47468ffa-1d5d-4e22-97a1-31d0a83506f5
Sep 27 07:53:51.254: INFO: Successfully deleted PD "aws://eu-west-3a/vol-036388211a9a64f37".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumes
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 27 07:53:51.254: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-4467" for this suite.
... skipping 71 lines ...
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 27 07:53:50.861: 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.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Sep 27 07:53:51.498: INFO: found topology map[topology.ebs.csi.aws.com/zone:eu-west-3a]
Sep 27 07:53:51.498: 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.954 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.8TytcAgTJ/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.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

    Not enough topologies in cluster -- skipping

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

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 62 lines ...
Sep 27 07:53:43.122: INFO: Waiting for pod aws-client to disappear
Sep 27 07:53:43.224: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Sep 27 07:53:43.224: INFO: Deleting PersistentVolumeClaim "pvc-rzx5t"
Sep 27 07:53:43.327: INFO: Deleting PersistentVolume "aws-mzfjs"
Sep 27 07:53:43.658: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0805988f4aac2af20", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0805988f4aac2af20 is currently attached to i-0af665c181bc566c8
	status code: 400, request id: e048244e-e678-4c8a-bdc3-d972b53ec299
Sep 27 07:53:49.216: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0805988f4aac2af20", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0805988f4aac2af20 is currently attached to i-0af665c181bc566c8
	status code: 400, request id: e90772c1-e228-46aa-9b72-2ba2036d8169
Sep 27 07:53:54.795: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0805988f4aac2af20", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0805988f4aac2af20 is currently attached to i-0af665c181bc566c8
	status code: 400, request id: eeb93b03-24ed-482d-903c-1744cb8a1518
Sep 27 07:54:00.338: INFO: Successfully deleted PD "aws://eu-west-3a/vol-0805988f4aac2af20".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 27 07:54:00.338: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8542" for this suite.
... skipping 134 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 27 07:53:26.097: 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.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Sep 27 07:53:26.637: INFO: Creating resource for dynamic PV
Sep 27 07:53:26.637: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9399-e2e-sc5gv8m
STEP: creating a claim
Sep 27 07:53:26.740: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-6nlg
STEP: Checking for subpath error in container status
Sep 27 07:53:43.261: INFO: Deleting pod "pod-subpath-test-dynamicpv-6nlg" in namespace "provisioning-9399"
Sep 27 07:53:43.372: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-6nlg" to be fully deleted
STEP: Deleting pod
Sep 27 07:53:45.578: INFO: Deleting pod "pod-subpath-test-dynamicpv-6nlg" in namespace "provisioning-9399"
STEP: Deleting pvc
Sep 27 07:53:45.889: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com4ddtn"
... skipping 11 lines ...

• [SLOW TEST:35.629 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.8TytcAgTJ/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.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [sig-storage] Volume FStype [Feature:vsphere]
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 27 07:54:01.536: INFO: >>> kubeConfig: /root/.kube/config
... skipping 36 lines ...
Sep 27 07:54:02.443: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 171 lines ...
Sep 27 07:53:37.107: INFO: PersistentVolumeClaim pvc-qnhvd found but phase is Pending instead of Bound.
Sep 27 07:53:39.214: INFO: PersistentVolumeClaim pvc-qnhvd found and phase=Bound (8.522747636s)
Sep 27 07:53:39.214: INFO: Waiting up to 3m0s for PersistentVolume aws-vns8q to have phase Bound
Sep 27 07:53:39.317: INFO: PersistentVolume aws-vns8q found and phase=Bound (103.270367ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-7n5n
STEP: Creating a pod to test exec-volume-test
Sep 27 07:53:39.634: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-7n5n" in namespace "volume-9237" to be "Succeeded or Failed"
Sep 27 07:53:39.737: INFO: Pod "exec-volume-test-preprovisionedpv-7n5n": Phase="Pending", Reason="", readiness=false. Elapsed: 103.617559ms
Sep 27 07:53:41.846: INFO: Pod "exec-volume-test-preprovisionedpv-7n5n": Phase="Pending", Reason="", readiness=false. Elapsed: 2.212207042s
Sep 27 07:53:43.951: INFO: Pod "exec-volume-test-preprovisionedpv-7n5n": Phase="Pending", Reason="", readiness=false. Elapsed: 4.317490998s
Sep 27 07:53:46.056: INFO: Pod "exec-volume-test-preprovisionedpv-7n5n": Phase="Pending", Reason="", readiness=false. Elapsed: 6.422051691s
Sep 27 07:53:48.161: INFO: Pod "exec-volume-test-preprovisionedpv-7n5n": Phase="Pending", Reason="", readiness=false. Elapsed: 8.526941713s
Sep 27 07:53:50.265: INFO: Pod "exec-volume-test-preprovisionedpv-7n5n": Phase="Pending", Reason="", readiness=false. Elapsed: 10.631160953s
Sep 27 07:53:52.369: INFO: Pod "exec-volume-test-preprovisionedpv-7n5n": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.735137373s
STEP: Saw pod success
Sep 27 07:53:52.369: INFO: Pod "exec-volume-test-preprovisionedpv-7n5n" satisfied condition "Succeeded or Failed"
Sep 27 07:53:52.474: INFO: Trying to get logs from node ip-172-20-54-99.eu-west-3.compute.internal pod exec-volume-test-preprovisionedpv-7n5n container exec-container-preprovisionedpv-7n5n: <nil>
STEP: delete the pod
Sep 27 07:53:52.693: INFO: Waiting for pod exec-volume-test-preprovisionedpv-7n5n to disappear
Sep 27 07:53:52.796: INFO: Pod exec-volume-test-preprovisionedpv-7n5n no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-7n5n
Sep 27 07:53:52.797: INFO: Deleting pod "exec-volume-test-preprovisionedpv-7n5n" in namespace "volume-9237"
STEP: Deleting pv and pvc
Sep 27 07:53:52.903: INFO: Deleting PersistentVolumeClaim "pvc-qnhvd"
Sep 27 07:53:53.008: INFO: Deleting PersistentVolume "aws-vns8q"
Sep 27 07:53:53.333: INFO: Couldn't delete PD "aws://eu-west-3a/vol-083f19336c3d5af0d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-083f19336c3d5af0d is currently attached to i-03ec4335fb22bd051
	status code: 400, request id: 582f9b48-a2a0-48ba-a33a-eff48ac38180
Sep 27 07:53:58.862: INFO: Couldn't delete PD "aws://eu-west-3a/vol-083f19336c3d5af0d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-083f19336c3d5af0d is currently attached to i-03ec4335fb22bd051
	status code: 400, request id: c61503fe-bf87-4656-a8c7-7292bd0a5ce5
Sep 27 07:54:04.401: INFO: Couldn't delete PD "aws://eu-west-3a/vol-083f19336c3d5af0d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-083f19336c3d5af0d is currently attached to i-03ec4335fb22bd051
	status code: 400, request id: 7a0d8e8d-9d68-4124-a124-1a3021ba0de8
Sep 27 07:54:09.950: INFO: Couldn't delete PD "aws://eu-west-3a/vol-083f19336c3d5af0d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-083f19336c3d5af0d is currently attached to i-03ec4335fb22bd051
	status code: 400, request id: 1142ca7f-4db9-4350-960f-48ad9661c97b
Sep 27 07:54:15.500: INFO: Successfully deleted PD "aws://eu-west-3a/vol-083f19336c3d5af0d".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 27 07:54:15.500: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-9237" for this suite.
... skipping 187 lines ...

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 30 lines ...
Sep 27 07:53:03.611: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4016-e2e-sctxxd9
STEP: creating a claim
Sep 27 07:53:03.717: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-lnfx
STEP: Creating a pod to test atomic-volume-subpath
Sep 27 07:53:04.033: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-lnfx" in namespace "provisioning-4016" to be "Succeeded or Failed"
Sep 27 07:53:04.137: INFO: Pod "pod-subpath-test-dynamicpv-lnfx": Phase="Pending", Reason="", readiness=false. Elapsed: 104.131501ms
Sep 27 07:53:06.244: INFO: Pod "pod-subpath-test-dynamicpv-lnfx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.210888398s
Sep 27 07:53:08.359: INFO: Pod "pod-subpath-test-dynamicpv-lnfx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.326217801s
Sep 27 07:53:10.465: INFO: Pod "pod-subpath-test-dynamicpv-lnfx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.431833126s
Sep 27 07:53:12.572: INFO: Pod "pod-subpath-test-dynamicpv-lnfx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.539037009s
Sep 27 07:53:14.677: INFO: Pod "pod-subpath-test-dynamicpv-lnfx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.644084783s
... skipping 11 lines ...
Sep 27 07:53:39.965: INFO: Pod "pod-subpath-test-dynamicpv-lnfx": Phase="Running", Reason="", readiness=true. Elapsed: 35.93186576s
Sep 27 07:53:42.070: INFO: Pod "pod-subpath-test-dynamicpv-lnfx": Phase="Running", Reason="", readiness=true. Elapsed: 38.036945709s
Sep 27 07:53:44.175: INFO: Pod "pod-subpath-test-dynamicpv-lnfx": Phase="Running", Reason="", readiness=true. Elapsed: 40.14213361s
Sep 27 07:53:46.280: INFO: Pod "pod-subpath-test-dynamicpv-lnfx": Phase="Running", Reason="", readiness=true. Elapsed: 42.246611766s
Sep 27 07:53:48.384: INFO: Pod "pod-subpath-test-dynamicpv-lnfx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 44.351223228s
STEP: Saw pod success
Sep 27 07:53:48.384: INFO: Pod "pod-subpath-test-dynamicpv-lnfx" satisfied condition "Succeeded or Failed"
Sep 27 07:53:48.489: INFO: Trying to get logs from node ip-172-20-55-93.eu-west-3.compute.internal pod pod-subpath-test-dynamicpv-lnfx container test-container-subpath-dynamicpv-lnfx: <nil>
STEP: delete the pod
Sep 27 07:53:48.764: INFO: Waiting for pod pod-subpath-test-dynamicpv-lnfx to disappear
Sep 27 07:53:48.873: INFO: Pod pod-subpath-test-dynamicpv-lnfx no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-lnfx
Sep 27 07:53:48.873: INFO: Deleting pod "pod-subpath-test-dynamicpv-lnfx" in namespace "provisioning-4016"
... skipping 141 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.8TytcAgTJ/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.8TytcAgTJ/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.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 316 lines ...
Sep 27 07:54:17.723: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-9767pfc8p
STEP: creating a claim
Sep 27 07:54:17.827: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Sep 27 07:54:18.038: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Sep 27 07:54:18.246: INFO: Error updating pvc awsk9rsp: PersistentVolumeClaim "awsk9rsp" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-9767pfc8p",
  	... // 3 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Sep 27 07:54:48.664: INFO: Error updating pvc awsk9rsp: PersistentVolumeClaim "awsk9rsp" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 472 lines ...
Sep 27 07:54:26.120: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Sep 27 07:54:26.795: INFO: Successfully created a new PD: "aws://eu-west-3a/vol-080e62b45f5025926".
Sep 27 07:54:26.795: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-w4gw
STEP: Creating a pod to test exec-volume-test
Sep 27 07:54:26.907: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-w4gw" in namespace "volume-7109" to be "Succeeded or Failed"
Sep 27 07:54:27.011: INFO: Pod "exec-volume-test-inlinevolume-w4gw": Phase="Pending", Reason="", readiness=false. Elapsed: 104.668267ms
Sep 27 07:54:29.120: INFO: Pod "exec-volume-test-inlinevolume-w4gw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.213387665s
Sep 27 07:54:31.225: INFO: Pod "exec-volume-test-inlinevolume-w4gw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.318344962s
Sep 27 07:54:33.330: INFO: Pod "exec-volume-test-inlinevolume-w4gw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.423327177s
Sep 27 07:54:35.435: INFO: Pod "exec-volume-test-inlinevolume-w4gw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.528208072s
Sep 27 07:54:37.539: INFO: Pod "exec-volume-test-inlinevolume-w4gw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.632897205s
STEP: Saw pod success
Sep 27 07:54:37.540: INFO: Pod "exec-volume-test-inlinevolume-w4gw" satisfied condition "Succeeded or Failed"
Sep 27 07:54:37.644: INFO: Trying to get logs from node ip-172-20-54-99.eu-west-3.compute.internal pod exec-volume-test-inlinevolume-w4gw container exec-container-inlinevolume-w4gw: <nil>
STEP: delete the pod
Sep 27 07:54:37.868: INFO: Waiting for pod exec-volume-test-inlinevolume-w4gw to disappear
Sep 27 07:54:37.974: INFO: Pod exec-volume-test-inlinevolume-w4gw no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-w4gw
Sep 27 07:54:37.974: INFO: Deleting pod "exec-volume-test-inlinevolume-w4gw" in namespace "volume-7109"
Sep 27 07:54:38.295: INFO: Couldn't delete PD "aws://eu-west-3a/vol-080e62b45f5025926", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-080e62b45f5025926 is currently attached to i-03ec4335fb22bd051
	status code: 400, request id: aa250f1c-ddfd-4502-a204-cec8380fb3b3
Sep 27 07:54:43.862: INFO: Couldn't delete PD "aws://eu-west-3a/vol-080e62b45f5025926", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-080e62b45f5025926 is currently attached to i-03ec4335fb22bd051
	status code: 400, request id: e87a551f-6488-4155-907f-79a3f5995337
Sep 27 07:54:49.410: INFO: Couldn't delete PD "aws://eu-west-3a/vol-080e62b45f5025926", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-080e62b45f5025926 is currently attached to i-03ec4335fb22bd051
	status code: 400, request id: 94df7545-08c3-4906-b879-a018a841e13e
Sep 27 07:54:54.922: INFO: Couldn't delete PD "aws://eu-west-3a/vol-080e62b45f5025926", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-080e62b45f5025926 is currently attached to i-03ec4335fb22bd051
	status code: 400, request id: e494adb0-9e11-4926-8f93-b6b9b6caa130
Sep 27 07:55:00.520: INFO: Couldn't delete PD "aws://eu-west-3a/vol-080e62b45f5025926", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-080e62b45f5025926 is currently attached to i-03ec4335fb22bd051
	status code: 400, request id: 11da7db8-0479-43bd-a005-9e965d36fb2d
Sep 27 07:55:06.092: INFO: Successfully deleted PD "aws://eu-west-3a/vol-080e62b45f5025926".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 27 07:55:06.092: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-7109" for this suite.
... skipping 268 lines ...
Sep 27 07:53:52.348: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-1387-e2e-scs9h96
STEP: creating a claim
Sep 27 07:53:52.455: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-fq8d
STEP: Creating a pod to test exec-volume-test
Sep 27 07:53:52.779: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-fq8d" in namespace "volume-1387" to be "Succeeded or Failed"
Sep 27 07:53:52.883: INFO: Pod "exec-volume-test-dynamicpv-fq8d": Phase="Pending", Reason="", readiness=false. Elapsed: 104.283591ms
Sep 27 07:53:54.988: INFO: Pod "exec-volume-test-dynamicpv-fq8d": Phase="Pending", Reason="", readiness=false. Elapsed: 2.209089315s
Sep 27 07:53:57.094: INFO: Pod "exec-volume-test-dynamicpv-fq8d": Phase="Pending", Reason="", readiness=false. Elapsed: 4.314756358s
Sep 27 07:53:59.199: INFO: Pod "exec-volume-test-dynamicpv-fq8d": Phase="Pending", Reason="", readiness=false. Elapsed: 6.419430711s
Sep 27 07:54:01.304: INFO: Pod "exec-volume-test-dynamicpv-fq8d": Phase="Pending", Reason="", readiness=false. Elapsed: 8.52457588s
Sep 27 07:54:03.409: INFO: Pod "exec-volume-test-dynamicpv-fq8d": Phase="Pending", Reason="", readiness=false. Elapsed: 10.629431517s
... skipping 9 lines ...
Sep 27 07:54:24.486: INFO: Pod "exec-volume-test-dynamicpv-fq8d": Phase="Pending", Reason="", readiness=false. Elapsed: 31.706766146s
Sep 27 07:54:26.591: INFO: Pod "exec-volume-test-dynamicpv-fq8d": Phase="Pending", Reason="", readiness=false. Elapsed: 33.811409821s
Sep 27 07:54:28.696: INFO: Pod "exec-volume-test-dynamicpv-fq8d": Phase="Pending", Reason="", readiness=false. Elapsed: 35.917258478s
Sep 27 07:54:30.802: INFO: Pod "exec-volume-test-dynamicpv-fq8d": Phase="Pending", Reason="", readiness=false. Elapsed: 38.023137497s
Sep 27 07:54:32.907: INFO: Pod "exec-volume-test-dynamicpv-fq8d": Phase="Succeeded", Reason="", readiness=false. Elapsed: 40.127896046s
STEP: Saw pod success
Sep 27 07:54:32.907: INFO: Pod "exec-volume-test-dynamicpv-fq8d" satisfied condition "Succeeded or Failed"
Sep 27 07:54:33.012: INFO: Trying to get logs from node ip-172-20-54-99.eu-west-3.compute.internal pod exec-volume-test-dynamicpv-fq8d container exec-container-dynamicpv-fq8d: <nil>
STEP: delete the pod
Sep 27 07:54:33.228: INFO: Waiting for pod exec-volume-test-dynamicpv-fq8d to disappear
Sep 27 07:54:33.332: INFO: Pod exec-volume-test-dynamicpv-fq8d no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-fq8d
Sep 27 07:54:33.332: INFO: Deleting pod "exec-volume-test-dynamicpv-fq8d" in namespace "volume-1387"
... skipping 266 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.8TytcAgTJ/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.8TytcAgTJ/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.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 242 lines ...
Sep 27 07:55:05.568: INFO: Waiting for pod aws-client to disappear
Sep 27 07:55:05.670: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Sep 27 07:55:05.670: INFO: Deleting PersistentVolumeClaim "pvc-5fqhz"
Sep 27 07:55:05.773: INFO: Deleting PersistentVolume "aws-64wfj"
Sep 27 07:55:06.439: INFO: Couldn't delete PD "aws://eu-west-3a/vol-02869f865ccb97f9a", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02869f865ccb97f9a is currently attached to i-03ec4335fb22bd051
	status code: 400, request id: ddfff0df-a846-4848-b34e-cd74fe8c0c8b
Sep 27 07:55:12.034: INFO: Couldn't delete PD "aws://eu-west-3a/vol-02869f865ccb97f9a", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02869f865ccb97f9a is currently attached to i-03ec4335fb22bd051
	status code: 400, request id: c6fc03b9-54f8-4252-99da-1f342799a50a
Sep 27 07:55:17.575: INFO: Couldn't delete PD "aws://eu-west-3a/vol-02869f865ccb97f9a", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02869f865ccb97f9a is currently attached to i-03ec4335fb22bd051
	status code: 400, request id: a390befc-51a1-4541-9f53-cc604ed20c8a
Sep 27 07:55:23.130: INFO: Successfully deleted PD "aws://eu-west-3a/vol-02869f865ccb97f9a".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 27 07:55:23.130: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-555" for this suite.
... skipping 333 lines ...
STEP: Deleting pod aws-client in namespace volume-3802
Sep 27 07:55:16.995: INFO: Waiting for pod aws-client to disappear
Sep 27 07:55:17.099: INFO: Pod aws-client still exists
Sep 27 07:55:19.100: INFO: Waiting for pod aws-client to disappear
Sep 27 07:55:19.204: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Sep 27 07:55:19.388: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0a6f8eee211d9f974", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a6f8eee211d9f974 is currently attached to i-0dcb927116601f3cf
	status code: 400, request id: 37d3f7a8-e0cc-4bea-b591-670d5e629926
Sep 27 07:55:24.969: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0a6f8eee211d9f974", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a6f8eee211d9f974 is currently attached to i-0dcb927116601f3cf
	status code: 400, request id: 7d837090-0b5e-49fd-a015-0a2ebdf5bc39
Sep 27 07:55:30.536: INFO: Successfully deleted PD "aws://eu-west-3a/vol-0a6f8eee211d9f974".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 27 07:55:30.536: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-3802" for this suite.
... skipping 20 lines ...

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

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

    /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 23 lines ...
Sep 27 07:55:05.872: INFO: PersistentVolumeClaim pvc-8mlzc found but phase is Pending instead of Bound.
Sep 27 07:55:07.975: INFO: PersistentVolumeClaim pvc-8mlzc found and phase=Bound (12.729585015s)
Sep 27 07:55:07.975: INFO: Waiting up to 3m0s for PersistentVolume aws-85dwx to have phase Bound
Sep 27 07:55:08.078: INFO: PersistentVolume aws-85dwx found and phase=Bound (103.2492ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-c4nv
STEP: Creating a pod to test exec-volume-test
Sep 27 07:55:08.393: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-c4nv" in namespace "volume-4971" to be "Succeeded or Failed"
Sep 27 07:55:08.497: INFO: Pod "exec-volume-test-preprovisionedpv-c4nv": Phase="Pending", Reason="", readiness=false. Elapsed: 103.482294ms
Sep 27 07:55:10.600: INFO: Pod "exec-volume-test-preprovisionedpv-c4nv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.207067909s
Sep 27 07:55:12.704: INFO: Pod "exec-volume-test-preprovisionedpv-c4nv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.310930686s
Sep 27 07:55:14.807: INFO: Pod "exec-volume-test-preprovisionedpv-c4nv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.414156232s
Sep 27 07:55:16.911: INFO: Pod "exec-volume-test-preprovisionedpv-c4nv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.517647647s
Sep 27 07:55:19.015: INFO: Pod "exec-volume-test-preprovisionedpv-c4nv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.622023804s
Sep 27 07:55:21.120: INFO: Pod "exec-volume-test-preprovisionedpv-c4nv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.726943345s
STEP: Saw pod success
Sep 27 07:55:21.120: INFO: Pod "exec-volume-test-preprovisionedpv-c4nv" satisfied condition "Succeeded or Failed"
Sep 27 07:55:21.231: INFO: Trying to get logs from node ip-172-20-55-93.eu-west-3.compute.internal pod exec-volume-test-preprovisionedpv-c4nv container exec-container-preprovisionedpv-c4nv: <nil>
STEP: delete the pod
Sep 27 07:55:21.455: INFO: Waiting for pod exec-volume-test-preprovisionedpv-c4nv to disappear
Sep 27 07:55:21.558: INFO: Pod exec-volume-test-preprovisionedpv-c4nv no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-c4nv
Sep 27 07:55:21.558: INFO: Deleting pod "exec-volume-test-preprovisionedpv-c4nv" in namespace "volume-4971"
STEP: Deleting pv and pvc
Sep 27 07:55:21.661: INFO: Deleting PersistentVolumeClaim "pvc-8mlzc"
Sep 27 07:55:21.766: INFO: Deleting PersistentVolume "aws-85dwx"
Sep 27 07:55:22.103: INFO: Couldn't delete PD "aws://eu-west-3a/vol-05d4633737b710c87", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05d4633737b710c87 is currently attached to i-03991f0757f6206b7
	status code: 400, request id: 500a8ab1-42bb-4a0e-9af3-46c2b4564a69
Sep 27 07:55:27.618: INFO: Couldn't delete PD "aws://eu-west-3a/vol-05d4633737b710c87", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05d4633737b710c87 is currently attached to i-03991f0757f6206b7
	status code: 400, request id: c47065c1-4558-4e23-9b4c-89d47fd9fbff
Sep 27 07:55:33.178: INFO: Successfully deleted PD "aws://eu-west-3a/vol-05d4633737b710c87".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 27 07:55:33.178: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-4971" for this suite.
... skipping 139 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.8TytcAgTJ/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.8TytcAgTJ/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.8TytcAgTJ/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.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Driver supports dynamic provisioning, skipping InlineVolume pattern

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

      Not enough topologies in cluster -- skipping

      /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 12 lines ...
Sep 27 07:54:01.782: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-2147-e2e-scl6zs9      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-2147    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-2147-e2e-scl6zs9,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-2147    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-2147-e2e-scl6zs9,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-2147    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-2147-e2e-scl6zs9,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-2147-e2e-scl6zs9    10b19b59-173e-4680-8784-8405db9d6080 11006 0 2021-09-27 07:54:01 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-09-27 07:54:01 +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-sqhpc pvc- provisioning-2147  029850af-f193-43df-9d3f-1a3c862b56a3 11016 0 2021-09-27 07:54:02 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-09-27 07:54:02 +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-2147-e2e-scl6zs9,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-c4a04aba-39c6-49be-bdeb-ed408b93a354 in namespace provisioning-2147
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Sep 27 07:54:12.913: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-4fmzc" in namespace "provisioning-2147" to be "Succeeded or Failed"
Sep 27 07:54:13.015: INFO: Pod "pvc-volume-tester-writer-4fmzc": Phase="Pending", Reason="", readiness=false. Elapsed: 101.951808ms
Sep 27 07:54:15.117: INFO: Pod "pvc-volume-tester-writer-4fmzc": Phase="Pending", Reason="", readiness=false. Elapsed: 2.204332397s
Sep 27 07:54:17.221: INFO: Pod "pvc-volume-tester-writer-4fmzc": Phase="Pending", Reason="", readiness=false. Elapsed: 4.307881413s
Sep 27 07:54:19.324: INFO: Pod "pvc-volume-tester-writer-4fmzc": Phase="Pending", Reason="", readiness=false. Elapsed: 6.411485735s
Sep 27 07:54:21.428: INFO: Pod "pvc-volume-tester-writer-4fmzc": Phase="Pending", Reason="", readiness=false. Elapsed: 8.51485356s
Sep 27 07:54:23.531: INFO: Pod "pvc-volume-tester-writer-4fmzc": Phase="Pending", Reason="", readiness=false. Elapsed: 10.618089405s
Sep 27 07:54:25.633: INFO: Pod "pvc-volume-tester-writer-4fmzc": Phase="Pending", Reason="", readiness=false. Elapsed: 12.720088455s
Sep 27 07:54:27.736: INFO: Pod "pvc-volume-tester-writer-4fmzc": Phase="Pending", Reason="", readiness=false. Elapsed: 14.822802637s
Sep 27 07:54:29.846: INFO: Pod "pvc-volume-tester-writer-4fmzc": Phase="Pending", Reason="", readiness=false. Elapsed: 16.932870123s
Sep 27 07:54:31.949: INFO: Pod "pvc-volume-tester-writer-4fmzc": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.035790415s
STEP: Saw pod success
Sep 27 07:54:31.949: INFO: Pod "pvc-volume-tester-writer-4fmzc" satisfied condition "Succeeded or Failed"
Sep 27 07:54:32.161: INFO: Pod pvc-volume-tester-writer-4fmzc has the following logs: 
Sep 27 07:54:32.161: INFO: Deleting pod "pvc-volume-tester-writer-4fmzc" in namespace "provisioning-2147"
Sep 27 07:54:32.270: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-4fmzc" 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-55-93.eu-west-3.compute.internal"
Sep 27 07:54:32.683: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-892gx" in namespace "provisioning-2147" to be "Succeeded or Failed"
Sep 27 07:54:32.785: INFO: Pod "pvc-volume-tester-reader-892gx": Phase="Pending", Reason="", readiness=false. Elapsed: 101.93063ms
Sep 27 07:54:34.889: INFO: Pod "pvc-volume-tester-reader-892gx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.205564345s
Sep 27 07:54:36.997: INFO: Pod "pvc-volume-tester-reader-892gx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.313377095s
Sep 27 07:54:39.099: INFO: Pod "pvc-volume-tester-reader-892gx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.41590992s
Sep 27 07:54:41.202: INFO: Pod "pvc-volume-tester-reader-892gx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.518439779s
Sep 27 07:54:43.306: INFO: Pod "pvc-volume-tester-reader-892gx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.622715884s
... skipping 6 lines ...
Sep 27 07:54:58.035: INFO: Pod "pvc-volume-tester-reader-892gx": Phase="Pending", Reason="", readiness=false. Elapsed: 25.35213735s
Sep 27 07:55:00.138: INFO: Pod "pvc-volume-tester-reader-892gx": Phase="Pending", Reason="", readiness=false. Elapsed: 27.454824116s
Sep 27 07:55:02.242: INFO: Pod "pvc-volume-tester-reader-892gx": Phase="Pending", Reason="", readiness=false. Elapsed: 29.558967958s
Sep 27 07:55:04.345: INFO: Pod "pvc-volume-tester-reader-892gx": Phase="Pending", Reason="", readiness=false. Elapsed: 31.66181965s
Sep 27 07:55:06.447: INFO: Pod "pvc-volume-tester-reader-892gx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 33.764027369s
STEP: Saw pod success
Sep 27 07:55:06.447: INFO: Pod "pvc-volume-tester-reader-892gx" satisfied condition "Succeeded or Failed"
Sep 27 07:55:06.654: INFO: Pod pvc-volume-tester-reader-892gx has the following logs: hello world

Sep 27 07:55:06.654: INFO: Deleting pod "pvc-volume-tester-reader-892gx" in namespace "provisioning-2147"
Sep 27 07:55:06.761: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-892gx" to be fully deleted
Sep 27 07:55:06.863: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-sqhpc] to have phase Bound
Sep 27 07:55:06.965: INFO: PersistentVolumeClaim pvc-sqhpc found and phase=Bound (101.551146ms)
... skipping 1063 lines ...
Sep 27 07:55:44.895: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Sep 27 07:55:45.564: INFO: Successfully created a new PD: "aws://eu-west-3a/vol-0dedd8863b48b148d".
Sep 27 07:55:45.564: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-2xcb
STEP: Creating a pod to test exec-volume-test
Sep 27 07:55:45.668: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-2xcb" in namespace "volume-1507" to be "Succeeded or Failed"
Sep 27 07:55:45.770: INFO: Pod "exec-volume-test-inlinevolume-2xcb": Phase="Pending", Reason="", readiness=false. Elapsed: 102.118921ms
Sep 27 07:55:47.873: INFO: Pod "exec-volume-test-inlinevolume-2xcb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.204759365s
Sep 27 07:55:49.977: INFO: Pod "exec-volume-test-inlinevolume-2xcb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.308447371s
Sep 27 07:55:52.079: INFO: Pod "exec-volume-test-inlinevolume-2xcb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.410604098s
Sep 27 07:55:54.182: INFO: Pod "exec-volume-test-inlinevolume-2xcb": Phase="Pending", Reason="", readiness=false. Elapsed: 8.514058225s
Sep 27 07:55:56.285: INFO: Pod "exec-volume-test-inlinevolume-2xcb": Phase="Pending", Reason="", readiness=false. Elapsed: 10.616512774s
... skipping 21 lines ...
Sep 27 07:56:42.559: INFO: Pod "exec-volume-test-inlinevolume-2xcb": Phase="Pending", Reason="", readiness=false. Elapsed: 56.891049926s
Sep 27 07:56:44.663: INFO: Pod "exec-volume-test-inlinevolume-2xcb": Phase="Pending", Reason="", readiness=false. Elapsed: 58.994375823s
Sep 27 07:56:46.766: INFO: Pod "exec-volume-test-inlinevolume-2xcb": Phase="Pending", Reason="", readiness=false. Elapsed: 1m1.097999612s
Sep 27 07:56:48.869: INFO: Pod "exec-volume-test-inlinevolume-2xcb": Phase="Pending", Reason="", readiness=false. Elapsed: 1m3.20058567s
Sep 27 07:56:50.972: INFO: Pod "exec-volume-test-inlinevolume-2xcb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m5.304320193s
STEP: Saw pod success
Sep 27 07:56:50.973: INFO: Pod "exec-volume-test-inlinevolume-2xcb" satisfied condition "Succeeded or Failed"
Sep 27 07:56:51.075: INFO: Trying to get logs from node ip-172-20-55-93.eu-west-3.compute.internal pod exec-volume-test-inlinevolume-2xcb container exec-container-inlinevolume-2xcb: <nil>
STEP: delete the pod
Sep 27 07:56:51.289: INFO: Waiting for pod exec-volume-test-inlinevolume-2xcb to disappear
Sep 27 07:56:51.391: INFO: Pod exec-volume-test-inlinevolume-2xcb no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-2xcb
Sep 27 07:56:51.391: INFO: Deleting pod "exec-volume-test-inlinevolume-2xcb" in namespace "volume-1507"
Sep 27 07:56:51.723: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0dedd8863b48b148d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0dedd8863b48b148d is currently attached to i-03991f0757f6206b7
	status code: 400, request id: 6b8f68af-88f0-4cd8-89e8-13d535b1dcc3
Sep 27 07:56:57.274: INFO: Couldn't delete PD "aws://eu-west-3a/vol-0dedd8863b48b148d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0dedd8863b48b148d is currently attached to i-03991f0757f6206b7
	status code: 400, request id: 8f5f92c2-46fc-43d3-adc2-431e54b8912b
Sep 27 07:57:02.853: INFO: Successfully deleted PD "aws://eu-west-3a/vol-0dedd8863b48b148d".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Sep 27 07:57:02.853: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-1507" for this suite.
... skipping 361 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Sep 27 07:55:36.915: 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.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Sep 27 07:55:37.436: INFO: Creating resource for dynamic PV
Sep 27 07:55:37.436: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-6705-e2e-sch8jf4
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Sep 27 07:55:46.195: INFO: Deleting pod "pod-06869f92-6036-4b0a-8ebe-7f831b28d7b7" in namespace "volumemode-6705"
Sep 27 07:55:46.301: INFO: Wait up to 5m0s for pod "pod-06869f92-6036-4b0a-8ebe-7f831b28d7b7" to be fully deleted
STEP: Deleting pvc
Sep 27 07:55:48.717: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comgnxmn"
Sep 27 07:55:48.823: INFO: Waiting up to 5m0s for PersistentVolume pvc-9b1a1012-f4cf-4e34-8813-dc817499ae7d to get deleted
Sep 27 07:55:48.926: INFO: PersistentVolume pvc-9b1a1012-f4cf-4e34-8813-dc817499ae7d found and phase=Released (103.450166ms)
... skipping 25 lines ...

• [SLOW TEST:109.326 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.8TytcAgTJ/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.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 665 lines ...
Sep 27 08:45:44.113: INFO: At 2021-09-27 07:55:48 +0000 UTC - event for pod-425bd77e-87d0-4627-b601-b38c6c32f67c: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-64ae75e0-b849-4ad4-b204-480f6ef51391" 
Sep 27 08:45:44.113: INFO: At 2021-09-27 07:55:49 +0000 UTC - event for pod-425bd77e-87d0-4627-b601-b38c6c32f67c: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-b420a5a2-2209-4910-a29b-7924e394e4f9" 
Sep 27 08:45:44.113: INFO: At 2021-09-27 07:55:50 +0000 UTC - event for pod-425bd77e-87d0-4627-b601-b38c6c32f67c: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-93dd21ca-9baa-4684-8f8a-465f7a4b8b42" 
Sep 27 08:45:44.113: INFO: At 2021-09-27 07:55:51 +0000 UTC - event for pod-425bd77e-87d0-4627-b601-b38c6c32f67c: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-d613745d-3759-47a8-b562-8a92e22febbb" 
Sep 27 08:45:44.113: INFO: At 2021-09-27 07:55:51 +0000 UTC - event for pod-425bd77e-87d0-4627-b601-b38c6c32f67c: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-195c6d8a-5a87-4c43-9974-2ce9db48ed63" 
Sep 27 08:45:44.113: INFO: At 2021-09-27 07:55:51 +0000 UTC - event for pod-425bd77e-87d0-4627-b601-b38c6c32f67c: {attachdetach-controller } SuccessfulAttachVolume: (combined from similar events): AttachVolume.Attach succeeded for volume "pvc-a3c1cde7-b172-4c17-ac00-95a269ecbe5b" 
Sep 27 08:45:44.113: INFO: At 2021-09-27 07:56:13 +0000 UTC - event for pod-425bd77e-87d0-4627-b601-b38c6c32f67c: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-947ee549-3034-4173-b5a1-31f074da9319" : rpc error: code = DeadlineExceeded desc = context deadline exceeded
Sep 27 08:45:44.113: INFO: At 2021-09-27 07:56:15 +0000 UTC - event for pod-425bd77e-87d0-4627-b601-b38c6c32f67c: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-93e4332d-cf68-4605-94cf-51b3fa29ff6f" : rpc error: code = DeadlineExceeded desc = context deadline exceeded
Sep 27 08:45:44.113: INFO: At 2021-09-27 07:56:15 +0000 UTC - event for pod-425bd77e-87d0-4627-b601-b38c6c32f67c: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-be977ae5-e8cc-42dc-9079-94a8e422db4b" : rpc error: code = DeadlineExceeded desc = context deadline exceeded
Sep 27 08:45:44.113: INFO: At 2021-09-27 07:56:20 +0000 UTC - event for pod-425bd77e-87d0-4627-b601-b38c6c32f67c: {attachdetach-controller } FailedAttachVolume: (combined from similar events): AttachVolume.Attach failed for volume "pvc-947ee549-3034-4173-b5a1-31f074da9319" : rpc error: code = Internal desc = Could not attach volume "vol-0857834bdb4fc3a39" to node "i-0af665c181bc566c8": attachment of disk "vol-0857834bdb4fc3a39" failed, expected device to be attached but was attaching
Sep 27 08:45:44.113: INFO: At 2021-09-27 07:57:46 +0000 UTC - event for pod-425bd77e-87d0-4627-b601-b38c6c32f67c: {kubelet ip-172-20-40-65.eu-west-3.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume29 volume13 volume22 volume30 volume6 volume36 volume8 volume2 volume3 volume14 volume34 volume27 volume31 volume21 volume26 volume20 volume10 volume24], unattached volumes=[volume29 volume1 volume38 volume16 volume4 volume9 volume13 kube-api-access-glzxg volume22 volume23 volume30 volume6 volume35 volume36 volume8 volume25 volume2 volume19 volume37 volume18 volume32 volume3 volume14 volume5 volume34 volume28 volume27 volume31 volume15 volume21 volume12 volume26 volume20 volume7 volume10 volume39 volume11 volume33 volume17 volume24]: timed out waiting for the condition
Sep 27 08:45:44.113: INFO: At 2021-09-27 08:00:04 +0000 UTC - event for pod-425bd77e-87d0-4627-b601-b38c6c32f67c: {kubelet ip-172-20-40-65.eu-west-3.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume26 volume10 volume6 volume20 volume36 volume22 volume8 volume13 volume27 volume24 volume14 volume30 volume21 volume3 volume34 volume31 volume2 volume29], unattached volumes=[volume12 volume18 volume26 volume35 volume1 volume10 volume23 volume39 volume9 volume6 volume38 volume17 volume20 volume36 volume33 volume5 volume22 volume11 volume16 volume8 volume4 volume13 volume15 volume25 volume37 volume27 volume24 volume28 volume14 volume30 kube-api-access-glzxg volume21 volume3 volume34 volume31 volume7 volume32 volume19 volume2 volume29]: timed out waiting for the condition
Sep 27 08:45:44.113: INFO: At 2021-09-27 08:02:20 +0000 UTC - event for pod-425bd77e-87d0-4627-b601-b38c6c32f67c: {kubelet ip-172-20-40-65.eu-west-3.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume27 volume24 volume2 volume31 volume20 volume34 volume26 volume36 volume29 volume8 volume14 volume21 volume30 volume13 volume10 volume3 volume22], unattached volumes=[volume19 volume27 kube-api-access-glzxg volume1 volume6 volume24 volume2 volume31 volume20 volume34 volume26 volume18 volume23 volume35 volume39 volume37 volume15 volume36 volume12 volume7 volume29 volume38 volume4 volume5 volume17 volume25 volume8 volume11 volume9 volume33 volume14 volume21 volume28 volume30 volume13 volume32 volume10 volume3 volume16 volume22]: timed out waiting for the condition
Sep 27 08:45:44.113: INFO: At 2021-09-27 08:02:31 +0000 UTC - event for pod-425bd77e-87d0-4627-b601-b38c6c32f67c: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-947ee549-3034-4173-b5a1-31f074da9319" : rpc error: code = Internal desc = Could not attach volume "vol-0857834bdb4fc3a39" to node "i-0af665c181bc566c8": attachment of disk "vol-0857834bdb4fc3a39" failed, expected device to be attached but was attaching
Sep 27 08:45:44.113: INFO: At 2021-09-27 08:04:34 +0000 UTC - event for pod-425bd77e-87d0-4627-b601-b38c6c32f67c: {kubelet ip-172-20-40-65.eu-west-3.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume10 volume22 volume31 volume36 volume27 volume8 volume14 volume2 volume21 volume13 volume20 volume34 volume3], unattached volumes=[volume10 volume33 volume22 volume31 volume18 volume7 volume36 volume26 volume15 volume23 volume27 volume16 volume12 volume8 volume4 volume14 volume39 volume32 kube-api-access-glzxg volume25 volume30 volume9 volume2 volume29 volume21 volume13 volume38 volume20 volume6 volume34 volume5 volume24 volume35 volume19 volume1 volume28 volume17 volume3 volume11 volume37]: timed out waiting for the condition
Sep 27 08:45:44.113: INFO: At 2021-09-27 08:04:38 +0000 UTC - event for pod-425bd77e-87d0-4627-b601-b38c6c32f67c: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-59958d56-7ba5-488f-8a87-e63e4ed79122" : rpc error: code = Internal desc = Could not attach volume "vol-0034927fa3fcd17ee" to node "i-0af665c181bc566c8": attachment of disk "vol-0034927fa3fcd17ee" failed, expected device to be attached but was attaching
Sep 27 08:45:44.113: INFO: At 2021-09-27 08:06:50 +0000 UTC - event for pod-425bd77e-87d0-4627-b601-b38c6c32f67c: {kubelet ip-172-20-40-65.eu-west-3.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume20 volume10 volume34 volume3 volume31 volume14 volume13 volume8 volume36 volume22 volume21 volume2 volume27], unattached volumes=[volume15 volume20 volume5 volume10 volume34 volume30 volume12 volume3 volume31 volume14 volume1 volume13 volume39 volume8 kube-api-access-glzxg volume4 volume7 volume36 volume18 volume19 volume22 volume26 volume21 volume32 volume28 volume17 volume2 volume11 volume33 volume16 volume9 volume27 volume23 volume37 volume6 volume29 volume35 volume25 volume38 volume24]: timed out waiting for the condition
Sep 27 08:45:44.113: INFO: At 2021-09-27 08:09:06 +0000 UTC - event for pod-425bd77e-87d0-4627-b601-b38c6c32f67c: {kubelet ip-172-20-40-65.eu-west-3.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume14 volume10 volume20 volume3 volume2 volume8 volume27 volume13 volume36 volume34 volume21 volume31 volume22], unattached volumes=[volume14 volume38 volume37 volume1 volume9 volume35 volume7 volume5 volume10 volume11 volume20 volume4 volume29 volume12 kube-api-access-glzxg volume3 volume2 volume33 volume8 volume23 volume39 volume26 volume24 volume27 volume13 volume18 volume36 volume34 volume19 volume21 volume16 volume6 volume32 volume25 volume30 volume17 volume15 volume28 volume31 volume22]: timed out waiting for the condition
Sep 27 08:45:44.113: INFO: At 2021-09-27 08:11:21 +0000 UTC - event for pod-425bd77e-87d0-4627-b601-b38c6c32f67c: {kubelet ip-172-20-40-65.eu-west-3.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume21 volume3 volume2 volume20 volume13 volume27 volume31 volume10 volume8 volume22 volume36 volume34 volume14], unattached volumes=[volume11 volume5 volume23 volume21 volume3 volume2 volume19 volume24 volume20 volume1 volume13 volume17 volume4 volume27 volume31 volume9 volume16 volume35 volume10 volume18 volume25 volume8 volume30 volume33 volume22 volume36 volume26 volume39 volume6 volume38 volume12 volume34 volume15 volume7 volume14 volume32 kube-api-access-glzxg volume28 volume37 volume29]: timed out waiting for the condition
Sep 27 08:45:44.113: INFO: At 2021-09-27 08:13:37 +0000 UTC - event for pod-425bd77e-87d0-4627-b601-b38c6c32f67c: {kubelet ip-172-20-40-65.eu-west-3.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume2 volume31 volume3 volume22 volume36 volume14 volume27 volume8 volume10 volume21 volume34 volume13 volume20], unattached volumes=[volume19 volume38 volume2 volume31 volume12 volume30 volume35 volume17 volume5 volume32 volume3 volume28 volume22 volume24 volume7 volume25 volume36 volume18 volume37 volume6 volume14 volume11 volume29 volume27 volume4 volume23 volume33 volume16 volume8 volume26 volume10 volume1 volume9 volume39 kube-api-access-glzxg volume21 volume34 volume15 volume13 volume20]: timed out waiting for the condition
Sep 27 08:45:44.113: INFO: At 2021-09-27 08:15:51 +0000 UTC - event for pod-425bd77e-87d0-4627-b601-b38c6c32f67c: {kubelet ip-172-20-40-65.eu-west-3.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume20 volume31 volume8 volume34 volume22 volume14 volume3 volume21 volume27 volume13 volume36 volume10 volume2], unattached volumes=[volume20 volume25 volume26 volume31 volume8 volume24 volume34 volume5 volume23 volume28 volume16 volume30 volume11 volume39 volume9 volume22 volume14 volume3 volume17 volume1 volume6 volume29 volume12 volume21 volume38 volume35 volume27 volume18 volume15 volume19 volume32 volume13 volume36 volume37 kube-api-access-glzxg volume10 volume33 volume2 volume4 volume7]: timed out waiting for the condition
Sep 27 08:45:44.113: INFO: At 2021-09-27 08:18:05 +0000 UTC - event for pod-425bd77e-87d0-4627-b601-b38c6c32f67c: {kubelet ip-172-20-40-65.eu-west-3.compute.internal} FailedMount: (combined from similar events): Unable to attach or mount volumes: unmounted volumes=[volume22 volume36 volume34 volume27 volume13 volume14 volume10 volume8 volume31 volume20 volume21 volume2 volume3], unattached volumes=[volume19 volume5 volume17 volume30 kube-api-access-glzxg volume33 volume22 volume16 volume32 volume36 volume15 volume7 volume34 volume9 volume27 volume4 volume28 volume12 volume6 volume13 volume14 volume18 volume10 volume8 volume38 volume25 volume31 volume1 volume26 volume24 volume37 volume11 volume20 volume21 volume23 volume29 volume2 volume39 volume3 volume35]: timed out waiting for the condition
... skipping 158 lines ...
/tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (filesystem volmode)] volumeLimits
  /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should support volume limits [Serial] [It]
    /tmp/kops.8TytcAgTJ/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumelimits.go:123

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

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


Summarizing 1 Failure:

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

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


Ginkgo ran 1 suite in 57m34.485998079s
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
I0927 08:45:48.422350   26175 app.go:59] RunDir for this run: "/logs/artifacts/923bfa1a-1f65-11ec-aef2-36f71ef8a223"
I0927 08:45:48.422519   26175 app.go:90] ID for this run: "923bfa1a-1f65-11ec-aef2-36f71ef8a223"
I0927 08:45:48.443181   26175 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
I0927 08:45:48.460265   26187 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
... skipping 2710 lines ...