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

No Test Failures!


Error lines from build-log.txt

... skipping 598 lines ...
I1013 19:18:00.999900   12527 app.go:90] ID for this run: "52b152a6-2c59-11ec-a43b-3a3c05ae6ad7"
I1013 19:18:01.022656   12527 up.go:43] Cleaning up any leaked resources from previous cluster
I1013 19:18:01.024040   12527 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
I1013 19:18:01.041901   12537 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1013 19:18:01.042750   12537 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I1013 19:18:01.042759   12537 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Error: Cluster.kops.k8s.io "e2e-c3f2775103-c95b4.test-cncf-aws.k8s.io" not found
W1013 19:18:01.515506   12527 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I1013 19:18:01.515564   12527 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
I1013 19:18:01.535654   12547 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1013 19:18:01.535871   12547 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I1013 19:18:01.535899   12547 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
I1013 19:18:01.985606   12527 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/13 19:18:01 failed to get external ip from metadata service: http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip returned 404
I1013 19:18:01.998815   12527 http.go:37] curl https://ip.jsb.workers.dev
I1013 19:18:02.091147   12527 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.71.6.63/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-southeast-1a --master-size c5.large
I1013 19:18:02.110370   12558 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1013 19:18:02.110456   12558 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I1013 19:18:02.110460   12558 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1013 19:18:02.133175   12558 create_cluster.go:838] Using SSH public key: /etc/aws-ssh/aws-ssh-public
... skipping 32 lines ...
I1013 19:18:23.678370   12527 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
I1013 19:18:23.700563   12580 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1013 19:18:23.700650   12580 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I1013 19:18:23.700654   12580 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-c3f2775103-c95b4.test-cncf-aws.k8s.io

W1013 19:18:25.287969   12580 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
W1013 19:18:35.322562   12580 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-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1013 19:18:45.369482   12580 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1013 19:18:55.405123   12580 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1013 19:19:05.456133   12580 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1013 19:19:15.492404   12580 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1013 19:19:25.534574   12580 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1013 19:19:35.601769   12580 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1013 19:19:45.638939   12580 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1013 19:19:55.674537   12580 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1013 19:20:05.726581   12580 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1013 19:20:15.755865   12580 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1013 19:20:25.794597   12580 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1013 19:20:35.834308   12580 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1013 19:20:45.872745   12580 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1013 19:20:55.927846   12580 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1013 19:21:05.963720   12580 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1013 19:21:15.997549   12580 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1013 19:21:26.034351   12580 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1013 19:21:36.070518   12580 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1013 19:21:46.107043   12580 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1013 19:21:56.137989   12580 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1013 19:22:06.173419   12580 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 21 lines ...
Pod	kube-system/ebs-csi-node-dgrr7				system-node-critical pod "ebs-csi-node-dgrr7" is pending
Pod	kube-system/ebs-csi-node-hklh5				system-node-critical pod "ebs-csi-node-hklh5" is pending
Pod	kube-system/ebs-csi-node-rgsk2				system-node-critical pod "ebs-csi-node-rgsk2" is pending
Pod	kube-system/ebs-csi-node-sh4t5				system-node-critical pod "ebs-csi-node-sh4t5" is pending
Pod	kube-system/ebs-csi-node-zr8nt				system-node-critical pod "ebs-csi-node-zr8nt" is pending

Validation Failed
W1013 19:22:20.976655   12580 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 21 lines ...
Pod	kube-system/ebs-csi-node-dgrr7				system-node-critical pod "ebs-csi-node-dgrr7" is pending
Pod	kube-system/ebs-csi-node-hklh5				system-node-critical pod "ebs-csi-node-hklh5" is pending
Pod	kube-system/ebs-csi-node-rgsk2				system-node-critical pod "ebs-csi-node-rgsk2" is pending
Pod	kube-system/ebs-csi-node-sh4t5				system-node-critical pod "ebs-csi-node-sh4t5" is pending
Pod	kube-system/ebs-csi-node-zr8nt				system-node-critical pod "ebs-csi-node-zr8nt" is pending

Validation Failed
W1013 19:22:34.198009   12580 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-controller-5c899887d-kb25t	system-cluster-critical pod "ebs-csi-controller-5c899887d-kb25t" is pending
Pod	kube-system/ebs-csi-node-hklh5			system-node-critical pod "ebs-csi-node-hklh5" is pending
Pod	kube-system/ebs-csi-node-rgsk2			system-node-critical pod "ebs-csi-node-rgsk2" is pending
Pod	kube-system/ebs-csi-node-sh4t5			system-node-critical pod "ebs-csi-node-sh4t5" is pending
Pod	kube-system/ebs-csi-node-zr8nt			system-node-critical pod "ebs-csi-node-zr8nt" is pending

Validation Failed
W1013 19:22:47.853697   12580 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 12 lines ...
Pod	kube-system/coredns-6c8944dbdc-g7zd6					system-cluster-critical pod "coredns-6c8944dbdc-g7zd6" is pending
Pod	kube-system/ebs-csi-node-hklh5						system-node-critical pod "ebs-csi-node-hklh5" is pending
Pod	kube-system/ebs-csi-node-rgsk2						system-node-critical pod "ebs-csi-node-rgsk2" is pending
Pod	kube-system/ebs-csi-node-zr8nt						system-node-critical pod "ebs-csi-node-zr8nt" is pending
Pod	kube-system/kube-proxy-ip-172-20-46-86.ap-southeast-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-46-86.ap-southeast-1.compute.internal" is pending

Validation Failed
W1013 19:23:01.322047   12580 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 463 lines ...

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

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

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

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

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 206 lines ...
STEP: Creating a kubernetes client
Oct 13 19:26:32.990: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename volumemode
W1013 19:26:34.257277   25127 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Oct 13 19:26:34.257: 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.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Oct 13 19:26:34.654: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 13 19:26:34.654: INFO: Creating resource for dynamic PV
Oct 13 19:26:34.654: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-2453hdtrr
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Oct 13 19:26:40.055: INFO: Deleting pod "pod-91daf933-e7ba-45be-b77e-80cb51a2c0e1" in namespace "volumemode-2453"
Oct 13 19:26:40.256: INFO: Wait up to 5m0s for pod "pod-91daf933-e7ba-45be-b77e-80cb51a2c0e1" to be fully deleted
STEP: Deleting pvc
Oct 13 19:26:43.054: INFO: Deleting PersistentVolumeClaim "awshc4fp"
Oct 13 19:26:43.258: INFO: Waiting up to 5m0s for PersistentVolume pvc-1957e12f-4ea9-4f08-8de0-2ed63f27f8e5 to get deleted
Oct 13 19:26:43.457: INFO: PersistentVolume pvc-1957e12f-4ea9-4f08-8de0-2ed63f27f8e5 found and phase=Released (199.205654ms)
... skipping 10 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.R8VRd6QTn/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.R8VRd6QTn/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (block volmode)] volumeMode
    /tmp/kops.R8VRd6QTn/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.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Oct 13 19:26:54.657: INFO: Driver supports dynamic provisioning, skipping PreprovisionedPV pattern
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
... skipping 88 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.R8VRd6QTn/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.R8VRd6QTn/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.R8VRd6QTn/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.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Driver supports dynamic provisioning, skipping InlineVolume pattern

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.R8VRd6QTn/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.R8VRd6QTn/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.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 6 lines ...
STEP: Creating a kubernetes client
Oct 13 19:26:33.241: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename volumemode
W1013 19:26:34.774361   25308 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Oct 13 19:26:34.774: 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.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Oct 13 19:26:35.167: INFO: Creating resource for dynamic PV
Oct 13 19:26:35.167: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-360-e2e-sckfv49
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Oct 13 19:26:40.567: INFO: Deleting pod "pod-ce74190b-af8f-44b1-9fb6-536dee0559d2" in namespace "volumemode-360"
Oct 13 19:26:40.771: INFO: Wait up to 5m0s for pod "pod-ce74190b-af8f-44b1-9fb6-536dee0559d2" to be fully deleted
STEP: Deleting pvc
Oct 13 19:26:43.564: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comctj4d"
Oct 13 19:26:43.763: INFO: Waiting up to 5m0s for PersistentVolume pvc-55cb0e04-f9b1-4323-8c7b-f7dc74b1130f to get deleted
Oct 13 19:26:43.961: INFO: PersistentVolume pvc-55cb0e04-f9b1-4323-8c7b-f7dc74b1130f found and phase=Released (197.398777ms)
... skipping 9 lines ...

• [SLOW TEST:27.113 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.R8VRd6QTn/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.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Oct 13 19:27:00.356: INFO: Driver "ebs.csi.aws.com" does not support volume type "CSIInlineVolume" - skipping
[AfterEach] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral
... skipping 98 lines ...
Oct 13 19:26:35.796: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-4100qlrzj
STEP: creating a claim
Oct 13 19:26:36.002: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Oct 13 19:26:36.412: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Oct 13 19:26:36.823: INFO: Error updating pvc awslspvb: PersistentVolumeClaim "awslspvb" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4100qlrzj",
  	... // 3 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Oct 13 19:27:07.653: INFO: Error updating pvc awslspvb: PersistentVolumeClaim "awslspvb" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 105 lines ...
STEP: Creating a kubernetes client
Oct 13 19:26:33.224: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename provisioning
W1013 19:26:34.724090   25296 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Oct 13 19:26:34.724: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail if non-existent subpath is outside the volume [Slow][LinuxOnly]
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Oct 13 19:26:35.116: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 13 19:26:35.116: INFO: Creating resource for dynamic PV
Oct 13 19:26:35.116: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1826wcjft
STEP: creating a claim
Oct 13 19:26:35.312: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-j2d4
STEP: Checking for subpath error in container status
Oct 13 19:26:58.315: INFO: Deleting pod "pod-subpath-test-dynamicpv-j2d4" in namespace "provisioning-1826"
Oct 13 19:26:58.513: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-j2d4" to be fully deleted
STEP: Deleting pod
Oct 13 19:27:02.906: INFO: Deleting pod "pod-subpath-test-dynamicpv-j2d4" in namespace "provisioning-1826"
STEP: Deleting pvc
Oct 13 19:27:03.500: INFO: Deleting PersistentVolumeClaim "aws5dk4t"
... skipping 12 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.R8VRd6QTn/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.R8VRd6QTn/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.R8VRd6QTn/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.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 34 lines ...
STEP: Deleting pod hostexec-ip-172-20-46-86.ap-southeast-1.compute.internal-lswnk in namespace volumemode-370
Oct 13 19:27:05.458: INFO: Deleting pod "pod-d273fdaf-f2fc-42dd-a9a7-e08eac30460a" in namespace "volumemode-370"
Oct 13 19:27:05.669: INFO: Wait up to 5m0s for pod "pod-d273fdaf-f2fc-42dd-a9a7-e08eac30460a" to be fully deleted
STEP: Deleting pv and pvc
Oct 13 19:27:08.082: INFO: Deleting PersistentVolumeClaim "pvc-92kkg"
Oct 13 19:27:08.293: INFO: Deleting PersistentVolume "aws-svv9z"
Oct 13 19:27:08.821: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-027f87efe507e9bab", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-027f87efe507e9bab is currently attached to i-0c7ecffbeb1cae944
	status code: 400, request id: 4240b5ff-7891-4e8c-b964-7f91c35e583f
Oct 13 19:27:14.812: INFO: Successfully deleted PD "aws://ap-southeast-1a/vol-027f87efe507e9bab".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 19:27:14.812: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-370" for this suite.
... skipping 41 lines ...
Oct 13 19:26:36.992: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Oct 13 19:26:38.135: INFO: Successfully created a new PD: "aws://ap-southeast-1a/vol-0ec73ffd077122bed".
Oct 13 19:26:38.135: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-z57r
STEP: Creating a pod to test exec-volume-test
Oct 13 19:26:38.352: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-z57r" in namespace "volume-1502" to be "Succeeded or Failed"
Oct 13 19:26:38.557: INFO: Pod "exec-volume-test-inlinevolume-z57r": Phase="Pending", Reason="", readiness=false. Elapsed: 204.909313ms
Oct 13 19:26:40.765: INFO: Pod "exec-volume-test-inlinevolume-z57r": Phase="Pending", Reason="", readiness=false. Elapsed: 2.412814087s
Oct 13 19:26:42.971: INFO: Pod "exec-volume-test-inlinevolume-z57r": Phase="Pending", Reason="", readiness=false. Elapsed: 4.618496615s
Oct 13 19:26:45.176: INFO: Pod "exec-volume-test-inlinevolume-z57r": Phase="Pending", Reason="", readiness=false. Elapsed: 6.823574652s
Oct 13 19:26:47.382: INFO: Pod "exec-volume-test-inlinevolume-z57r": Phase="Pending", Reason="", readiness=false. Elapsed: 9.029634926s
Oct 13 19:26:49.588: INFO: Pod "exec-volume-test-inlinevolume-z57r": Phase="Pending", Reason="", readiness=false. Elapsed: 11.235988378s
Oct 13 19:26:51.794: INFO: Pod "exec-volume-test-inlinevolume-z57r": Phase="Pending", Reason="", readiness=false. Elapsed: 13.441926225s
Oct 13 19:26:54.001: INFO: Pod "exec-volume-test-inlinevolume-z57r": Phase="Pending", Reason="", readiness=false. Elapsed: 15.648409167s
Oct 13 19:26:56.207: INFO: Pod "exec-volume-test-inlinevolume-z57r": Phase="Pending", Reason="", readiness=false. Elapsed: 17.854578229s
Oct 13 19:26:58.413: INFO: Pod "exec-volume-test-inlinevolume-z57r": Phase="Pending", Reason="", readiness=false. Elapsed: 20.060541038s
Oct 13 19:27:00.618: INFO: Pod "exec-volume-test-inlinevolume-z57r": Phase="Pending", Reason="", readiness=false. Elapsed: 22.265367513s
Oct 13 19:27:02.823: INFO: Pod "exec-volume-test-inlinevolume-z57r": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.470628155s
STEP: Saw pod success
Oct 13 19:27:02.823: INFO: Pod "exec-volume-test-inlinevolume-z57r" satisfied condition "Succeeded or Failed"
Oct 13 19:27:03.027: INFO: Trying to get logs from node ip-172-20-53-140.ap-southeast-1.compute.internal pod exec-volume-test-inlinevolume-z57r container exec-container-inlinevolume-z57r: <nil>
STEP: delete the pod
Oct 13 19:27:03.466: INFO: Waiting for pod exec-volume-test-inlinevolume-z57r to disappear
Oct 13 19:27:03.671: INFO: Pod exec-volume-test-inlinevolume-z57r no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-z57r
Oct 13 19:27:03.671: INFO: Deleting pod "exec-volume-test-inlinevolume-z57r" in namespace "volume-1502"
Oct 13 19:27:04.216: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-0ec73ffd077122bed", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ec73ffd077122bed is currently attached to i-0eabc97ff75480cc2
	status code: 400, request id: 3be12b1e-cb6f-49fa-bd90-d86cf36b4603
Oct 13 19:27:10.147: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-0ec73ffd077122bed", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ec73ffd077122bed is currently attached to i-0eabc97ff75480cc2
	status code: 400, request id: 3b643b7b-76f0-43c3-8273-696d3645759e
Oct 13 19:27:16.154: INFO: Successfully deleted PD "aws://ap-southeast-1a/vol-0ec73ffd077122bed".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 19:27:16.154: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-1502" for this suite.
... skipping 45 lines ...
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 19:27:18.011: 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.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Oct 13 19:27:19.249: INFO: found topology map[topology.ebs.csi.aws.com/zone:ap-southeast-1a]
Oct 13 19:27:19.250: 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] [1.857 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.R8VRd6QTn/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.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

    Not enough topologies in cluster -- skipping

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

      Not enough topologies in cluster -- skipping

      /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 12 lines ...
Oct 13 19:26:37.196: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2109ks2mq
STEP: creating a claim
Oct 13 19:26:37.405: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-gmxq
STEP: Creating a pod to test subpath
Oct 13 19:26:38.024: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-gmxq" in namespace "provisioning-2109" to be "Succeeded or Failed"
Oct 13 19:26:38.231: INFO: Pod "pod-subpath-test-dynamicpv-gmxq": Phase="Pending", Reason="", readiness=false. Elapsed: 206.26937ms
Oct 13 19:26:40.440: INFO: Pod "pod-subpath-test-dynamicpv-gmxq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.415368449s
Oct 13 19:26:42.647: INFO: Pod "pod-subpath-test-dynamicpv-gmxq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.622328923s
Oct 13 19:26:44.857: INFO: Pod "pod-subpath-test-dynamicpv-gmxq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.832169814s
Oct 13 19:26:47.064: INFO: Pod "pod-subpath-test-dynamicpv-gmxq": Phase="Pending", Reason="", readiness=false. Elapsed: 9.039414757s
Oct 13 19:26:49.270: INFO: Pod "pod-subpath-test-dynamicpv-gmxq": Phase="Pending", Reason="", readiness=false. Elapsed: 11.246076574s
Oct 13 19:26:51.477: INFO: Pod "pod-subpath-test-dynamicpv-gmxq": Phase="Pending", Reason="", readiness=false. Elapsed: 13.453085119s
Oct 13 19:26:53.683: INFO: Pod "pod-subpath-test-dynamicpv-gmxq": Phase="Pending", Reason="", readiness=false. Elapsed: 15.658990814s
Oct 13 19:26:55.891: INFO: Pod "pod-subpath-test-dynamicpv-gmxq": Phase="Pending", Reason="", readiness=false. Elapsed: 17.866209292s
Oct 13 19:26:58.098: INFO: Pod "pod-subpath-test-dynamicpv-gmxq": Phase="Pending", Reason="", readiness=false. Elapsed: 20.073252032s
Oct 13 19:27:00.304: INFO: Pod "pod-subpath-test-dynamicpv-gmxq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.279193709s
STEP: Saw pod success
Oct 13 19:27:00.304: INFO: Pod "pod-subpath-test-dynamicpv-gmxq" satisfied condition "Succeeded or Failed"
Oct 13 19:27:00.509: INFO: Trying to get logs from node ip-172-20-53-140.ap-southeast-1.compute.internal pod pod-subpath-test-dynamicpv-gmxq container test-container-subpath-dynamicpv-gmxq: <nil>
STEP: delete the pod
Oct 13 19:27:00.939: INFO: Waiting for pod pod-subpath-test-dynamicpv-gmxq to disappear
Oct 13 19:27:01.145: INFO: Pod pod-subpath-test-dynamicpv-gmxq no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-gmxq
Oct 13 19:27:01.154: INFO: Deleting pod "pod-subpath-test-dynamicpv-gmxq" in namespace "provisioning-2109"
... skipping 78 lines ...
Oct 13 19:26:36.642: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4770-e2e-scdp2n9
STEP: creating a claim
Oct 13 19:26:36.848: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-72zs
STEP: Creating a pod to test subpath
Oct 13 19:26:37.538: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-72zs" in namespace "provisioning-4770" to be "Succeeded or Failed"
Oct 13 19:26:37.744: INFO: Pod "pod-subpath-test-dynamicpv-72zs": Phase="Pending", Reason="", readiness=false. Elapsed: 205.811999ms
Oct 13 19:26:39.949: INFO: Pod "pod-subpath-test-dynamicpv-72zs": Phase="Pending", Reason="", readiness=false. Elapsed: 2.411016904s
Oct 13 19:26:42.155: INFO: Pod "pod-subpath-test-dynamicpv-72zs": Phase="Pending", Reason="", readiness=false. Elapsed: 4.616230865s
Oct 13 19:26:44.361: INFO: Pod "pod-subpath-test-dynamicpv-72zs": Phase="Pending", Reason="", readiness=false. Elapsed: 6.822248367s
Oct 13 19:26:46.567: INFO: Pod "pod-subpath-test-dynamicpv-72zs": Phase="Pending", Reason="", readiness=false. Elapsed: 9.028586058s
Oct 13 19:26:48.773: INFO: Pod "pod-subpath-test-dynamicpv-72zs": Phase="Pending", Reason="", readiness=false. Elapsed: 11.234401649s
Oct 13 19:26:50.978: INFO: Pod "pod-subpath-test-dynamicpv-72zs": Phase="Pending", Reason="", readiness=false. Elapsed: 13.439312257s
Oct 13 19:26:53.183: INFO: Pod "pod-subpath-test-dynamicpv-72zs": Phase="Pending", Reason="", readiness=false. Elapsed: 15.644611677s
Oct 13 19:26:55.389: INFO: Pod "pod-subpath-test-dynamicpv-72zs": Phase="Pending", Reason="", readiness=false. Elapsed: 17.850653568s
Oct 13 19:26:57.610: INFO: Pod "pod-subpath-test-dynamicpv-72zs": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.071847752s
STEP: Saw pod success
Oct 13 19:26:57.610: INFO: Pod "pod-subpath-test-dynamicpv-72zs" satisfied condition "Succeeded or Failed"
Oct 13 19:26:57.815: INFO: Trying to get logs from node ip-172-20-32-51.ap-southeast-1.compute.internal pod pod-subpath-test-dynamicpv-72zs container test-container-volume-dynamicpv-72zs: <nil>
STEP: delete the pod
Oct 13 19:26:58.243: INFO: Waiting for pod pod-subpath-test-dynamicpv-72zs to disappear
Oct 13 19:26:58.447: INFO: Pod pod-subpath-test-dynamicpv-72zs no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-72zs
Oct 13 19:26:58.447: INFO: Deleting pod "pod-subpath-test-dynamicpv-72zs" in namespace "provisioning-4770"
... skipping 75 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 19:27:23.840: 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.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Oct 13 19:27:24.868: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Oct 13 19:27:26.048: INFO: Successfully created a new PD: "aws://ap-southeast-1a/vol-06aa5329f0883b0b9".
Oct 13 19:27:26.048: INFO: Creating resource for pre-provisioned PV
Oct 13 19:27:26.048: INFO: Creating PVC and PV
... skipping 4 lines ...
Oct 13 19:27:28.886: INFO: PersistentVolumeClaim pvc-t29hj found but phase is Pending instead of Bound.
Oct 13 19:27:31.093: INFO: PersistentVolumeClaim pvc-t29hj found but phase is Pending instead of Bound.
Oct 13 19:27:33.299: INFO: PersistentVolumeClaim pvc-t29hj found and phase=Bound (6.825467981s)
Oct 13 19:27:33.299: INFO: Waiting up to 3m0s for PersistentVolume aws-wr7rc to have phase Bound
Oct 13 19:27:33.505: INFO: PersistentVolume aws-wr7rc found and phase=Bound (205.81865ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Oct 13 19:27:36.746: INFO: Deleting pod "pod-eb339c30-f8ef-4db5-9c96-07112065e247" in namespace "volumemode-8128"
Oct 13 19:27:36.955: INFO: Wait up to 5m0s for pod "pod-eb339c30-f8ef-4db5-9c96-07112065e247" to be fully deleted
STEP: Deleting pv and pvc
Oct 13 19:27:39.369: INFO: Deleting PersistentVolumeClaim "pvc-t29hj"
Oct 13 19:27:39.577: INFO: Deleting PersistentVolume "aws-wr7rc"
Oct 13 19:27:40.134: INFO: Successfully deleted PD "aws://ap-southeast-1a/vol-06aa5329f0883b0b9".
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.R8VRd6QTn/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.R8VRd6QTn/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
    /tmp/kops.R8VRd6QTn/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.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 21 lines ...
Oct 13 19:26:47.608: INFO: PersistentVolumeClaim pvc-pfx9j found but phase is Pending instead of Bound.
Oct 13 19:26:49.811: INFO: PersistentVolumeClaim pvc-pfx9j found and phase=Bound (13.416944454s)
Oct 13 19:26:49.811: INFO: Waiting up to 3m0s for PersistentVolume aws-4fmf4 to have phase Bound
Oct 13 19:26:50.014: INFO: PersistentVolume aws-4fmf4 found and phase=Bound (202.860311ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-mblb
STEP: Creating a pod to test exec-volume-test
Oct 13 19:26:50.622: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-mblb" in namespace "volume-8721" to be "Succeeded or Failed"
Oct 13 19:26:50.823: INFO: Pod "exec-volume-test-preprovisionedpv-mblb": Phase="Pending", Reason="", readiness=false. Elapsed: 201.164915ms
Oct 13 19:26:53.025: INFO: Pod "exec-volume-test-preprovisionedpv-mblb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.403514813s
Oct 13 19:26:55.227: INFO: Pod "exec-volume-test-preprovisionedpv-mblb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.604890891s
Oct 13 19:26:57.428: INFO: Pod "exec-volume-test-preprovisionedpv-mblb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.806391362s
Oct 13 19:26:59.630: INFO: Pod "exec-volume-test-preprovisionedpv-mblb": Phase="Pending", Reason="", readiness=false. Elapsed: 9.007747346s
Oct 13 19:27:01.831: INFO: Pod "exec-volume-test-preprovisionedpv-mblb": Phase="Pending", Reason="", readiness=false. Elapsed: 11.20939771s
Oct 13 19:27:04.033: INFO: Pod "exec-volume-test-preprovisionedpv-mblb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 13.411492022s
STEP: Saw pod success
Oct 13 19:27:04.033: INFO: Pod "exec-volume-test-preprovisionedpv-mblb" satisfied condition "Succeeded or Failed"
Oct 13 19:27:04.234: INFO: Trying to get logs from node ip-172-20-32-51.ap-southeast-1.compute.internal pod exec-volume-test-preprovisionedpv-mblb container exec-container-preprovisionedpv-mblb: <nil>
STEP: delete the pod
Oct 13 19:27:04.644: INFO: Waiting for pod exec-volume-test-preprovisionedpv-mblb to disappear
Oct 13 19:27:04.845: INFO: Pod exec-volume-test-preprovisionedpv-mblb no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-mblb
Oct 13 19:27:04.845: INFO: Deleting pod "exec-volume-test-preprovisionedpv-mblb" in namespace "volume-8721"
STEP: Deleting pv and pvc
Oct 13 19:27:05.045: INFO: Deleting PersistentVolumeClaim "pvc-pfx9j"
Oct 13 19:27:05.247: INFO: Deleting PersistentVolume "aws-4fmf4"
Oct 13 19:27:05.787: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-00cfd86656e067e03", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00cfd86656e067e03 is currently attached to i-08bcea51a1937d594
	status code: 400, request id: 3f068108-bb47-4c27-9cb8-61c4c59330fa
Oct 13 19:27:11.731: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-00cfd86656e067e03", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00cfd86656e067e03 is currently attached to i-08bcea51a1937d594
	status code: 400, request id: cbd58650-9da6-4c70-9537-9f0e7649d1cc
Oct 13 19:27:17.709: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-00cfd86656e067e03", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00cfd86656e067e03 is currently attached to i-08bcea51a1937d594
	status code: 400, request id: 39cbbe15-b4b7-4623-9527-edee6e61f552
Oct 13 19:27:23.665: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-00cfd86656e067e03", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00cfd86656e067e03 is currently attached to i-08bcea51a1937d594
	status code: 400, request id: a6a903d6-a42e-4dd7-aec1-7baf55a0ccff
Oct 13 19:27:29.618: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-00cfd86656e067e03", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00cfd86656e067e03 is currently attached to i-08bcea51a1937d594
	status code: 400, request id: 3058fecd-8ef6-4923-9bee-f568f3953711
Oct 13 19:27:35.583: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-00cfd86656e067e03", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00cfd86656e067e03 is currently attached to i-08bcea51a1937d594
	status code: 400, request id: 673c2051-08c6-42c2-9b4e-73062cf6da99
Oct 13 19:27:41.544: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-00cfd86656e067e03", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00cfd86656e067e03 is currently attached to i-08bcea51a1937d594
	status code: 400, request id: e25d9d12-3c39-439c-8020-e57852dd9ab8
Oct 13 19:27:47.582: INFO: Successfully deleted PD "aws://ap-southeast-1a/vol-00cfd86656e067e03".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 19:27:47.582: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8721" for this suite.
... skipping 24 lines ...
Oct 13 19:26:37.863: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-50816pf62
STEP: creating a claim
Oct 13 19:26:38.076: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-hhdr
STEP: Creating a pod to test subpath
Oct 13 19:26:38.711: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-hhdr" in namespace "provisioning-5081" to be "Succeeded or Failed"
Oct 13 19:26:38.920: INFO: Pod "pod-subpath-test-dynamicpv-hhdr": Phase="Pending", Reason="", readiness=false. Elapsed: 208.878894ms
Oct 13 19:26:41.130: INFO: Pod "pod-subpath-test-dynamicpv-hhdr": Phase="Pending", Reason="", readiness=false. Elapsed: 2.419068869s
Oct 13 19:26:43.347: INFO: Pod "pod-subpath-test-dynamicpv-hhdr": Phase="Pending", Reason="", readiness=false. Elapsed: 4.636190178s
Oct 13 19:26:45.557: INFO: Pod "pod-subpath-test-dynamicpv-hhdr": Phase="Pending", Reason="", readiness=false. Elapsed: 6.845896758s
Oct 13 19:26:47.767: INFO: Pod "pod-subpath-test-dynamicpv-hhdr": Phase="Pending", Reason="", readiness=false. Elapsed: 9.056046593s
Oct 13 19:26:49.977: INFO: Pod "pod-subpath-test-dynamicpv-hhdr": Phase="Pending", Reason="", readiness=false. Elapsed: 11.266140618s
... skipping 2 lines ...
Oct 13 19:26:56.608: INFO: Pod "pod-subpath-test-dynamicpv-hhdr": Phase="Pending", Reason="", readiness=false. Elapsed: 17.896758101s
Oct 13 19:26:58.819: INFO: Pod "pod-subpath-test-dynamicpv-hhdr": Phase="Pending", Reason="", readiness=false. Elapsed: 20.108579249s
Oct 13 19:27:01.029: INFO: Pod "pod-subpath-test-dynamicpv-hhdr": Phase="Pending", Reason="", readiness=false. Elapsed: 22.318152591s
Oct 13 19:27:03.238: INFO: Pod "pod-subpath-test-dynamicpv-hhdr": Phase="Pending", Reason="", readiness=false. Elapsed: 24.527209778s
Oct 13 19:27:05.450: INFO: Pod "pod-subpath-test-dynamicpv-hhdr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.739328169s
STEP: Saw pod success
Oct 13 19:27:05.450: INFO: Pod "pod-subpath-test-dynamicpv-hhdr" satisfied condition "Succeeded or Failed"
Oct 13 19:27:05.659: INFO: Trying to get logs from node ip-172-20-46-86.ap-southeast-1.compute.internal pod pod-subpath-test-dynamicpv-hhdr container test-container-subpath-dynamicpv-hhdr: <nil>
STEP: delete the pod
Oct 13 19:27:06.088: INFO: Waiting for pod pod-subpath-test-dynamicpv-hhdr to disappear
Oct 13 19:27:06.297: INFO: Pod pod-subpath-test-dynamicpv-hhdr no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-hhdr
Oct 13 19:27:06.297: INFO: Deleting pod "pod-subpath-test-dynamicpv-hhdr" in namespace "provisioning-5081"
... skipping 140 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.R8VRd6QTn/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.R8VRd6QTn/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.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 12 lines ...
Oct 13 19:27:02.744: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6734cchk5
STEP: creating a claim
Oct 13 19:27:02.942: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-kg2l
STEP: Creating a pod to test subpath
Oct 13 19:27:03.558: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-kg2l" in namespace "provisioning-6734" to be "Succeeded or Failed"
Oct 13 19:27:03.755: INFO: Pod "pod-subpath-test-dynamicpv-kg2l": Phase="Pending", Reason="", readiness=false. Elapsed: 197.269591ms
Oct 13 19:27:05.953: INFO: Pod "pod-subpath-test-dynamicpv-kg2l": Phase="Pending", Reason="", readiness=false. Elapsed: 2.39555471s
Oct 13 19:27:08.151: INFO: Pod "pod-subpath-test-dynamicpv-kg2l": Phase="Pending", Reason="", readiness=false. Elapsed: 4.593199178s
Oct 13 19:27:10.348: INFO: Pod "pod-subpath-test-dynamicpv-kg2l": Phase="Pending", Reason="", readiness=false. Elapsed: 6.790674447s
Oct 13 19:27:12.548: INFO: Pod "pod-subpath-test-dynamicpv-kg2l": Phase="Pending", Reason="", readiness=false. Elapsed: 8.99009097s
Oct 13 19:27:14.745: INFO: Pod "pod-subpath-test-dynamicpv-kg2l": Phase="Pending", Reason="", readiness=false. Elapsed: 11.187814279s
Oct 13 19:27:16.943: INFO: Pod "pod-subpath-test-dynamicpv-kg2l": Phase="Succeeded", Reason="", readiness=false. Elapsed: 13.385497315s
STEP: Saw pod success
Oct 13 19:27:16.943: INFO: Pod "pod-subpath-test-dynamicpv-kg2l" satisfied condition "Succeeded or Failed"
Oct 13 19:27:17.141: INFO: Trying to get logs from node ip-172-20-37-108.ap-southeast-1.compute.internal pod pod-subpath-test-dynamicpv-kg2l container test-container-subpath-dynamicpv-kg2l: <nil>
STEP: delete the pod
Oct 13 19:27:17.554: INFO: Waiting for pod pod-subpath-test-dynamicpv-kg2l to disappear
Oct 13 19:27:17.751: INFO: Pod pod-subpath-test-dynamicpv-kg2l no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-kg2l
Oct 13 19:27:17.751: INFO: Deleting pod "pod-subpath-test-dynamicpv-kg2l" in namespace "provisioning-6734"
... skipping 97 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.R8VRd6QTn/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.R8VRd6QTn/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.R8VRd6QTn/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.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 67 lines ...
Oct 13 19:27:27.176: INFO: Waiting for pod aws-client to disappear
Oct 13 19:27:27.377: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Oct 13 19:27:27.377: INFO: Deleting PersistentVolumeClaim "pvc-fhs7q"
Oct 13 19:27:27.583: INFO: Deleting PersistentVolume "aws-hpjmg"
Oct 13 19:27:28.117: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-0c11e2943bcddd427", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c11e2943bcddd427 is currently attached to i-0eabc97ff75480cc2
	status code: 400, request id: b59ab5fc-7fa0-42a5-ba93-bd5304d0fc13
Oct 13 19:27:34.071: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-0c11e2943bcddd427", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c11e2943bcddd427 is currently attached to i-0eabc97ff75480cc2
	status code: 400, request id: 3eb477b4-8518-4249-8a7a-e951c13080c2
Oct 13 19:27:40.027: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-0c11e2943bcddd427", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c11e2943bcddd427 is currently attached to i-0eabc97ff75480cc2
	status code: 400, request id: 909b0c1a-8902-4699-a45e-47639579f5de
Oct 13 19:27:46.004: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-0c11e2943bcddd427", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c11e2943bcddd427 is currently attached to i-0eabc97ff75480cc2
	status code: 400, request id: 05292478-0b12-4d71-bc0e-456a9a12ccc3
Oct 13 19:27:52.020: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-0c11e2943bcddd427", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c11e2943bcddd427 is currently attached to i-0eabc97ff75480cc2
	status code: 400, request id: 7107fb54-070b-4654-9717-e41e39755524
Oct 13 19:27:57.977: INFO: Successfully deleted PD "aws://ap-southeast-1a/vol-0c11e2943bcddd427".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 19:27:57.977: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-559" for this suite.
... skipping 71 lines ...
Oct 13 19:26:37.244: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9742-e2e-scbxx87
STEP: creating a claim
Oct 13 19:26:37.451: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-2bb9
STEP: Creating a pod to test subpath
Oct 13 19:26:38.070: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-2bb9" in namespace "provisioning-9742" to be "Succeeded or Failed"
Oct 13 19:26:38.275: INFO: Pod "pod-subpath-test-dynamicpv-2bb9": Phase="Pending", Reason="", readiness=false. Elapsed: 205.408039ms
Oct 13 19:26:40.486: INFO: Pod "pod-subpath-test-dynamicpv-2bb9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.416601388s
Oct 13 19:26:42.693: INFO: Pod "pod-subpath-test-dynamicpv-2bb9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.622895977s
Oct 13 19:26:44.899: INFO: Pod "pod-subpath-test-dynamicpv-2bb9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.829653541s
Oct 13 19:26:47.106: INFO: Pod "pod-subpath-test-dynamicpv-2bb9": Phase="Pending", Reason="", readiness=false. Elapsed: 9.036037129s
Oct 13 19:26:49.313: INFO: Pod "pod-subpath-test-dynamicpv-2bb9": Phase="Pending", Reason="", readiness=false. Elapsed: 11.242796492s
Oct 13 19:26:51.519: INFO: Pod "pod-subpath-test-dynamicpv-2bb9": Phase="Pending", Reason="", readiness=false. Elapsed: 13.449596959s
Oct 13 19:26:53.726: INFO: Pod "pod-subpath-test-dynamicpv-2bb9": Phase="Pending", Reason="", readiness=false. Elapsed: 15.656128734s
Oct 13 19:26:55.931: INFO: Pod "pod-subpath-test-dynamicpv-2bb9": Phase="Pending", Reason="", readiness=false. Elapsed: 17.861663345s
Oct 13 19:26:58.138: INFO: Pod "pod-subpath-test-dynamicpv-2bb9": Phase="Pending", Reason="", readiness=false. Elapsed: 20.067808882s
Oct 13 19:27:00.345: INFO: Pod "pod-subpath-test-dynamicpv-2bb9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.275768136s
STEP: Saw pod success
Oct 13 19:27:00.346: INFO: Pod "pod-subpath-test-dynamicpv-2bb9" satisfied condition "Succeeded or Failed"
Oct 13 19:27:00.551: INFO: Trying to get logs from node ip-172-20-46-86.ap-southeast-1.compute.internal pod pod-subpath-test-dynamicpv-2bb9 container test-container-subpath-dynamicpv-2bb9: <nil>
STEP: delete the pod
Oct 13 19:27:00.980: INFO: Waiting for pod pod-subpath-test-dynamicpv-2bb9 to disappear
Oct 13 19:27:01.187: INFO: Pod pod-subpath-test-dynamicpv-2bb9 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-2bb9
Oct 13 19:27:01.187: INFO: Deleting pod "pod-subpath-test-dynamicpv-2bb9" in namespace "provisioning-9742"
... skipping 271 lines ...
Oct 13 19:26:37.284: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9243gp875
STEP: creating a claim
Oct 13 19:26:37.532: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-qfb4
STEP: Creating a pod to test subpath
Oct 13 19:26:38.148: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-qfb4" in namespace "provisioning-9243" to be "Succeeded or Failed"
Oct 13 19:26:38.353: INFO: Pod "pod-subpath-test-dynamicpv-qfb4": Phase="Pending", Reason="", readiness=false. Elapsed: 204.996016ms
Oct 13 19:26:40.556: INFO: Pod "pod-subpath-test-dynamicpv-qfb4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.40813204s
Oct 13 19:26:42.759: INFO: Pod "pod-subpath-test-dynamicpv-qfb4": Phase="Pending", Reason="", readiness=false. Elapsed: 4.610865916s
Oct 13 19:26:44.962: INFO: Pod "pod-subpath-test-dynamicpv-qfb4": Phase="Pending", Reason="", readiness=false. Elapsed: 6.813905565s
Oct 13 19:26:47.164: INFO: Pod "pod-subpath-test-dynamicpv-qfb4": Phase="Pending", Reason="", readiness=false. Elapsed: 9.01625823s
Oct 13 19:26:49.366: INFO: Pod "pod-subpath-test-dynamicpv-qfb4": Phase="Pending", Reason="", readiness=false. Elapsed: 11.218334111s
Oct 13 19:26:51.573: INFO: Pod "pod-subpath-test-dynamicpv-qfb4": Phase="Pending", Reason="", readiness=false. Elapsed: 13.425289869s
Oct 13 19:26:53.775: INFO: Pod "pod-subpath-test-dynamicpv-qfb4": Phase="Pending", Reason="", readiness=false. Elapsed: 15.627282674s
Oct 13 19:26:55.981: INFO: Pod "pod-subpath-test-dynamicpv-qfb4": Phase="Pending", Reason="", readiness=false. Elapsed: 17.832818752s
Oct 13 19:26:58.183: INFO: Pod "pod-subpath-test-dynamicpv-qfb4": Phase="Pending", Reason="", readiness=false. Elapsed: 20.034956496s
Oct 13 19:27:00.386: INFO: Pod "pod-subpath-test-dynamicpv-qfb4": Phase="Pending", Reason="", readiness=false. Elapsed: 22.237712233s
Oct 13 19:27:02.589: INFO: Pod "pod-subpath-test-dynamicpv-qfb4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.440827149s
STEP: Saw pod success
Oct 13 19:27:02.589: INFO: Pod "pod-subpath-test-dynamicpv-qfb4" satisfied condition "Succeeded or Failed"
Oct 13 19:27:02.791: INFO: Trying to get logs from node ip-172-20-37-108.ap-southeast-1.compute.internal pod pod-subpath-test-dynamicpv-qfb4 container test-container-subpath-dynamicpv-qfb4: <nil>
STEP: delete the pod
Oct 13 19:27:03.471: INFO: Waiting for pod pod-subpath-test-dynamicpv-qfb4 to disappear
Oct 13 19:27:03.672: INFO: Pod pod-subpath-test-dynamicpv-qfb4 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-qfb4
Oct 13 19:27:03.673: INFO: Deleting pod "pod-subpath-test-dynamicpv-qfb4" in namespace "provisioning-9243"
STEP: Creating pod pod-subpath-test-dynamicpv-qfb4
STEP: Creating a pod to test subpath
Oct 13 19:27:04.079: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-qfb4" in namespace "provisioning-9243" to be "Succeeded or Failed"
Oct 13 19:27:04.281: INFO: Pod "pod-subpath-test-dynamicpv-qfb4": Phase="Pending", Reason="", readiness=false. Elapsed: 201.514637ms
Oct 13 19:27:06.484: INFO: Pod "pod-subpath-test-dynamicpv-qfb4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.404297201s
Oct 13 19:27:08.687: INFO: Pod "pod-subpath-test-dynamicpv-qfb4": Phase="Pending", Reason="", readiness=false. Elapsed: 4.607830169s
Oct 13 19:27:10.889: INFO: Pod "pod-subpath-test-dynamicpv-qfb4": Phase="Pending", Reason="", readiness=false. Elapsed: 6.80990261s
Oct 13 19:27:13.092: INFO: Pod "pod-subpath-test-dynamicpv-qfb4": Phase="Pending", Reason="", readiness=false. Elapsed: 9.012236246s
Oct 13 19:27:15.300: INFO: Pod "pod-subpath-test-dynamicpv-qfb4": Phase="Pending", Reason="", readiness=false. Elapsed: 11.220016482s
... skipping 20 lines ...
Oct 13 19:28:01.557: INFO: Pod "pod-subpath-test-dynamicpv-qfb4": Phase="Pending", Reason="", readiness=false. Elapsed: 57.477503923s
Oct 13 19:28:03.761: INFO: Pod "pod-subpath-test-dynamicpv-qfb4": Phase="Pending", Reason="", readiness=false. Elapsed: 59.681499663s
Oct 13 19:28:05.963: INFO: Pod "pod-subpath-test-dynamicpv-qfb4": Phase="Pending", Reason="", readiness=false. Elapsed: 1m1.883420208s
Oct 13 19:28:08.165: INFO: Pod "pod-subpath-test-dynamicpv-qfb4": Phase="Pending", Reason="", readiness=false. Elapsed: 1m4.085491791s
Oct 13 19:28:10.369: INFO: Pod "pod-subpath-test-dynamicpv-qfb4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m6.289781003s
STEP: Saw pod success
Oct 13 19:28:10.369: INFO: Pod "pod-subpath-test-dynamicpv-qfb4" satisfied condition "Succeeded or Failed"
Oct 13 19:28:10.574: INFO: Trying to get logs from node ip-172-20-32-51.ap-southeast-1.compute.internal pod pod-subpath-test-dynamicpv-qfb4 container test-container-subpath-dynamicpv-qfb4: <nil>
STEP: delete the pod
Oct 13 19:28:10.988: INFO: Waiting for pod pod-subpath-test-dynamicpv-qfb4 to disappear
Oct 13 19:28:11.189: INFO: Pod pod-subpath-test-dynamicpv-qfb4 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-qfb4
Oct 13 19:28:11.189: INFO: Deleting pod "pod-subpath-test-dynamicpv-qfb4" in namespace "provisioning-9243"
... skipping 218 lines ...
Oct 13 19:28:00.801: INFO: PersistentVolumeClaim pvc-2sznt found but phase is Pending instead of Bound.
Oct 13 19:28:03.017: INFO: PersistentVolumeClaim pvc-2sznt found and phase=Bound (9.060719471s)
Oct 13 19:28:03.017: INFO: Waiting up to 3m0s for PersistentVolume aws-vzpgx to have phase Bound
Oct 13 19:28:03.226: INFO: PersistentVolume aws-vzpgx found and phase=Bound (208.999567ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-dxzb
STEP: Creating a pod to test exec-volume-test
Oct 13 19:28:03.855: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-dxzb" in namespace "volume-8520" to be "Succeeded or Failed"
Oct 13 19:28:04.064: INFO: Pod "exec-volume-test-preprovisionedpv-dxzb": Phase="Pending", Reason="", readiness=false. Elapsed: 209.247437ms
Oct 13 19:28:06.275: INFO: Pod "exec-volume-test-preprovisionedpv-dxzb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.419760391s
Oct 13 19:28:08.488: INFO: Pod "exec-volume-test-preprovisionedpv-dxzb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.632414336s
Oct 13 19:28:10.697: INFO: Pod "exec-volume-test-preprovisionedpv-dxzb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.841723207s
Oct 13 19:28:12.908: INFO: Pod "exec-volume-test-preprovisionedpv-dxzb": Phase="Pending", Reason="", readiness=false. Elapsed: 9.052751966s
Oct 13 19:28:15.117: INFO: Pod "exec-volume-test-preprovisionedpv-dxzb": Phase="Pending", Reason="", readiness=false. Elapsed: 11.262093106s
Oct 13 19:28:17.327: INFO: Pod "exec-volume-test-preprovisionedpv-dxzb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 13.471760558s
STEP: Saw pod success
Oct 13 19:28:17.327: INFO: Pod "exec-volume-test-preprovisionedpv-dxzb" satisfied condition "Succeeded or Failed"
Oct 13 19:28:17.536: INFO: Trying to get logs from node ip-172-20-46-86.ap-southeast-1.compute.internal pod exec-volume-test-preprovisionedpv-dxzb container exec-container-preprovisionedpv-dxzb: <nil>
STEP: delete the pod
Oct 13 19:28:17.963: INFO: Waiting for pod exec-volume-test-preprovisionedpv-dxzb to disappear
Oct 13 19:28:18.172: INFO: Pod exec-volume-test-preprovisionedpv-dxzb no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-dxzb
Oct 13 19:28:18.172: INFO: Deleting pod "exec-volume-test-preprovisionedpv-dxzb" in namespace "volume-8520"
STEP: Deleting pv and pvc
Oct 13 19:28:18.381: INFO: Deleting PersistentVolumeClaim "pvc-2sznt"
Oct 13 19:28:18.591: INFO: Deleting PersistentVolume "aws-vzpgx"
Oct 13 19:28:19.108: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-055f9eda56ccbf0bb", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-055f9eda56ccbf0bb is currently attached to i-0c7ecffbeb1cae944
	status code: 400, request id: 727b50c7-aec9-44fc-b403-0bb6bd6da3ac
Oct 13 19:28:25.102: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-055f9eda56ccbf0bb", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-055f9eda56ccbf0bb is currently attached to i-0c7ecffbeb1cae944
	status code: 400, request id: 3e8cf1f9-72b9-49f4-bf57-42bb9aa180a4
Oct 13 19:28:31.111: INFO: Successfully deleted PD "aws://ap-southeast-1a/vol-055f9eda56ccbf0bb".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 19:28:31.111: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8520" for this suite.
... skipping 43 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 19:27:58.587: 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.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Oct 13 19:27:59.596: INFO: Creating resource for dynamic PV
Oct 13 19:27:59.596: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7494-e2e-scdlj6s
STEP: creating a claim
Oct 13 19:27:59.804: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-vbt6
STEP: Checking for subpath error in container status
Oct 13 19:28:16.821: INFO: Deleting pod "pod-subpath-test-dynamicpv-vbt6" in namespace "provisioning-7494"
Oct 13 19:28:17.024: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-vbt6" to be fully deleted
STEP: Deleting pod
Oct 13 19:28:19.427: INFO: Deleting pod "pod-subpath-test-dynamicpv-vbt6" in namespace "provisioning-7494"
STEP: Deleting pvc
Oct 13 19:28:20.029: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comkvkhh"
... skipping 11 lines ...

• [SLOW TEST:38.070 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath directory is outside the volume [Slow][LinuxOnly]
    /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 187 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 19:28:22.601: 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.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Oct 13 19:28:23.626: INFO: Creating resource for dynamic PV
Oct 13 19:28:23.626: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-777-e2e-scbptz5
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Oct 13 19:28:29.067: INFO: Deleting pod "pod-1a6cce66-1669-4d81-86c7-17c439c9be0d" in namespace "volumemode-777"
Oct 13 19:28:29.273: INFO: Wait up to 5m0s for pod "pod-1a6cce66-1669-4d81-86c7-17c439c9be0d" to be fully deleted
STEP: Deleting pvc
Oct 13 19:28:32.094: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comhv7q4"
Oct 13 19:28:32.299: INFO: Waiting up to 5m0s for PersistentVolume pvc-b953444c-6d7c-44c4-a84a-5cd3fd4db804 to get deleted
Oct 13 19:28:32.504: INFO: PersistentVolume pvc-b953444c-6d7c-44c4-a84a-5cd3fd4db804 found and phase=Released (204.524315ms)
... skipping 9 lines ...

• [SLOW TEST:26.158 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.R8VRd6QTn/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.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] provisioning
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] provisioning
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 31 lines ...
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 19:28:50.206: 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.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Oct 13 19:28:51.437: INFO: found topology map[topology.ebs.csi.aws.com/zone:ap-southeast-1a]
Oct 13 19:28:51.438: 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] [1.851 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.R8VRd6QTn/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.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

    Not enough topologies in cluster -- skipping

    /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 75 lines ...
Oct 13 19:28:11.789: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-77094zhzk
STEP: creating a claim
Oct 13 19:28:11.995: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-g5lq
STEP: Creating a pod to test subpath
Oct 13 19:28:12.617: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-g5lq" in namespace "provisioning-7709" to be "Succeeded or Failed"
Oct 13 19:28:12.822: INFO: Pod "pod-subpath-test-dynamicpv-g5lq": Phase="Pending", Reason="", readiness=false. Elapsed: 205.268618ms
Oct 13 19:28:15.027: INFO: Pod "pod-subpath-test-dynamicpv-g5lq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.410711892s
Oct 13 19:28:17.234: INFO: Pod "pod-subpath-test-dynamicpv-g5lq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.617429713s
Oct 13 19:28:19.440: INFO: Pod "pod-subpath-test-dynamicpv-g5lq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.823033052s
Oct 13 19:28:21.646: INFO: Pod "pod-subpath-test-dynamicpv-g5lq": Phase="Pending", Reason="", readiness=false. Elapsed: 9.028829733s
Oct 13 19:28:23.852: INFO: Pod "pod-subpath-test-dynamicpv-g5lq": Phase="Pending", Reason="", readiness=false. Elapsed: 11.235280733s
Oct 13 19:28:26.058: INFO: Pod "pod-subpath-test-dynamicpv-g5lq": Phase="Pending", Reason="", readiness=false. Elapsed: 13.441153125s
Oct 13 19:28:28.265: INFO: Pod "pod-subpath-test-dynamicpv-g5lq": Phase="Pending", Reason="", readiness=false. Elapsed: 15.648014931s
Oct 13 19:28:30.474: INFO: Pod "pod-subpath-test-dynamicpv-g5lq": Phase="Pending", Reason="", readiness=false. Elapsed: 17.857330433s
Oct 13 19:28:32.681: INFO: Pod "pod-subpath-test-dynamicpv-g5lq": Phase="Pending", Reason="", readiness=false. Elapsed: 20.063901252s
Oct 13 19:28:34.887: INFO: Pod "pod-subpath-test-dynamicpv-g5lq": Phase="Pending", Reason="", readiness=false. Elapsed: 22.27023977s
Oct 13 19:28:37.094: INFO: Pod "pod-subpath-test-dynamicpv-g5lq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.477651578s
STEP: Saw pod success
Oct 13 19:28:37.094: INFO: Pod "pod-subpath-test-dynamicpv-g5lq" satisfied condition "Succeeded or Failed"
Oct 13 19:28:37.300: INFO: Trying to get logs from node ip-172-20-32-51.ap-southeast-1.compute.internal pod pod-subpath-test-dynamicpv-g5lq container test-container-volume-dynamicpv-g5lq: <nil>
STEP: delete the pod
Oct 13 19:28:37.718: INFO: Waiting for pod pod-subpath-test-dynamicpv-g5lq to disappear
Oct 13 19:28:37.923: INFO: Pod pod-subpath-test-dynamicpv-g5lq no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-g5lq
Oct 13 19:28:37.923: INFO: Deleting pod "pod-subpath-test-dynamicpv-g5lq" in namespace "provisioning-7709"
... skipping 81 lines ...
Oct 13 19:28:56.871: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 232 lines ...
Oct 13 19:28:44.293: INFO: Waiting for pod aws-client to disappear
Oct 13 19:28:44.502: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Oct 13 19:28:44.502: INFO: Deleting PersistentVolumeClaim "pvc-8kf6d"
Oct 13 19:28:44.709: INFO: Deleting PersistentVolume "aws-n7v85"
Oct 13 19:28:45.226: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-0e0eec243d5ffb384", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e0eec243d5ffb384 is currently attached to i-013c922fab027b6ad
	status code: 400, request id: 9e276a0e-3949-4ab5-bb62-3535aae340d8
Oct 13 19:28:51.187: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-0e0eec243d5ffb384", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e0eec243d5ffb384 is currently attached to i-013c922fab027b6ad
	status code: 400, request id: bf6f4b7c-3933-4416-9cd5-fbf3dbc3c839
Oct 13 19:28:57.129: INFO: Successfully deleted PD "aws://ap-southeast-1a/vol-0e0eec243d5ffb384".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 19:28:57.129: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-7356" for this suite.
... skipping 186 lines ...
Oct 13 19:27:16.270: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6781-e2e-scxfdmp
STEP: creating a claim
Oct 13 19:27:16.478: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-8prj
STEP: Creating a pod to test atomic-volume-subpath
Oct 13 19:27:17.105: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-8prj" in namespace "provisioning-6781" to be "Succeeded or Failed"
Oct 13 19:27:17.312: INFO: Pod "pod-subpath-test-dynamicpv-8prj": Phase="Pending", Reason="", readiness=false. Elapsed: 206.646328ms
Oct 13 19:27:19.520: INFO: Pod "pod-subpath-test-dynamicpv-8prj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.414796159s
Oct 13 19:27:21.727: INFO: Pod "pod-subpath-test-dynamicpv-8prj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.621989537s
Oct 13 19:27:23.935: INFO: Pod "pod-subpath-test-dynamicpv-8prj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.830123199s
Oct 13 19:27:26.144: INFO: Pod "pod-subpath-test-dynamicpv-8prj": Phase="Pending", Reason="", readiness=false. Elapsed: 9.038741874s
Oct 13 19:27:28.353: INFO: Pod "pod-subpath-test-dynamicpv-8prj": Phase="Pending", Reason="", readiness=false. Elapsed: 11.24802281s
... skipping 31 lines ...
Oct 13 19:28:39.017: INFO: Pod "pod-subpath-test-dynamicpv-8prj": Phase="Running", Reason="", readiness=true. Elapsed: 1m21.911882492s
Oct 13 19:28:41.227: INFO: Pod "pod-subpath-test-dynamicpv-8prj": Phase="Running", Reason="", readiness=true. Elapsed: 1m24.12222809s
Oct 13 19:28:43.435: INFO: Pod "pod-subpath-test-dynamicpv-8prj": Phase="Running", Reason="", readiness=true. Elapsed: 1m26.330424395s
Oct 13 19:28:45.643: INFO: Pod "pod-subpath-test-dynamicpv-8prj": Phase="Running", Reason="", readiness=true. Elapsed: 1m28.538236265s
Oct 13 19:28:47.851: INFO: Pod "pod-subpath-test-dynamicpv-8prj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m30.745951296s
STEP: Saw pod success
Oct 13 19:28:47.851: INFO: Pod "pod-subpath-test-dynamicpv-8prj" satisfied condition "Succeeded or Failed"
Oct 13 19:28:48.061: INFO: Trying to get logs from node ip-172-20-37-108.ap-southeast-1.compute.internal pod pod-subpath-test-dynamicpv-8prj container test-container-subpath-dynamicpv-8prj: <nil>
STEP: delete the pod
Oct 13 19:28:48.501: INFO: Waiting for pod pod-subpath-test-dynamicpv-8prj to disappear
Oct 13 19:28:48.708: INFO: Pod pod-subpath-test-dynamicpv-8prj no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-8prj
Oct 13 19:28:48.708: INFO: Deleting pod "pod-subpath-test-dynamicpv-8prj" in namespace "provisioning-6781"
... skipping 552 lines ...
Oct 13 19:28:53.084: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-7694-e2e-scmtvr7
STEP: creating a claim
Oct 13 19:28:53.290: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Oct 13 19:28:53.702: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Oct 13 19:28:54.114: INFO: Error updating pvc ebs.csi.aws.com9b97k: PersistentVolumeClaim "ebs.csi.aws.com9b97k" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-7694-e2e-scmtvr7",
  	... // 3 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Oct 13 19:29:24.940: INFO: Error updating pvc ebs.csi.aws.com9b97k: PersistentVolumeClaim "ebs.csi.aws.com9b97k" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 53 lines ...

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

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

    /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 103 lines ...
Oct 13 19:29:07.284: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-1938vqnpf
STEP: creating a claim
Oct 13 19:29:07.495: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-zj9q
STEP: Creating a pod to test exec-volume-test
Oct 13 19:29:08.126: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-zj9q" in namespace "volume-1938" to be "Succeeded or Failed"
Oct 13 19:29:08.341: INFO: Pod "exec-volume-test-dynamicpv-zj9q": Phase="Pending", Reason="", readiness=false. Elapsed: 215.718032ms
Oct 13 19:29:10.551: INFO: Pod "exec-volume-test-dynamicpv-zj9q": Phase="Pending", Reason="", readiness=false. Elapsed: 2.425490623s
Oct 13 19:29:12.761: INFO: Pod "exec-volume-test-dynamicpv-zj9q": Phase="Pending", Reason="", readiness=false. Elapsed: 4.635632085s
Oct 13 19:29:14.971: INFO: Pod "exec-volume-test-dynamicpv-zj9q": Phase="Pending", Reason="", readiness=false. Elapsed: 6.845221624s
Oct 13 19:29:17.183: INFO: Pod "exec-volume-test-dynamicpv-zj9q": Phase="Pending", Reason="", readiness=false. Elapsed: 9.057236018s
Oct 13 19:29:19.396: INFO: Pod "exec-volume-test-dynamicpv-zj9q": Phase="Pending", Reason="", readiness=false. Elapsed: 11.27067964s
Oct 13 19:29:21.606: INFO: Pod "exec-volume-test-dynamicpv-zj9q": Phase="Running", Reason="", readiness=true. Elapsed: 13.480382343s
Oct 13 19:29:23.817: INFO: Pod "exec-volume-test-dynamicpv-zj9q": Phase="Succeeded", Reason="", readiness=false. Elapsed: 15.691019247s
STEP: Saw pod success
Oct 13 19:29:23.817: INFO: Pod "exec-volume-test-dynamicpv-zj9q" satisfied condition "Succeeded or Failed"
Oct 13 19:29:24.026: INFO: Trying to get logs from node ip-172-20-53-140.ap-southeast-1.compute.internal pod exec-volume-test-dynamicpv-zj9q container exec-container-dynamicpv-zj9q: <nil>
STEP: delete the pod
Oct 13 19:29:24.468: INFO: Waiting for pod exec-volume-test-dynamicpv-zj9q to disappear
Oct 13 19:29:24.677: INFO: Pod exec-volume-test-dynamicpv-zj9q no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-zj9q
Oct 13 19:29:24.677: INFO: Deleting pod "exec-volume-test-dynamicpv-zj9q" in namespace "volume-1938"
... skipping 34 lines ...
Oct 13 19:28:40.375: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6919-e2e-scxfq52
STEP: creating a claim
Oct 13 19:28:40.588: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-5sgg
STEP: Creating a pod to test multi_subpath
Oct 13 19:28:41.220: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-5sgg" in namespace "provisioning-6919" to be "Succeeded or Failed"
Oct 13 19:28:41.429: INFO: Pod "pod-subpath-test-dynamicpv-5sgg": Phase="Pending", Reason="", readiness=false. Elapsed: 208.700481ms
Oct 13 19:28:43.638: INFO: Pod "pod-subpath-test-dynamicpv-5sgg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.417718488s
Oct 13 19:28:45.848: INFO: Pod "pod-subpath-test-dynamicpv-5sgg": Phase="Pending", Reason="", readiness=false. Elapsed: 4.627667159s
Oct 13 19:28:48.059: INFO: Pod "pod-subpath-test-dynamicpv-5sgg": Phase="Pending", Reason="", readiness=false. Elapsed: 6.839126826s
Oct 13 19:28:50.269: INFO: Pod "pod-subpath-test-dynamicpv-5sgg": Phase="Pending", Reason="", readiness=false. Elapsed: 9.049113115s
Oct 13 19:28:52.479: INFO: Pod "pod-subpath-test-dynamicpv-5sgg": Phase="Pending", Reason="", readiness=false. Elapsed: 11.259449529s
Oct 13 19:28:54.689: INFO: Pod "pod-subpath-test-dynamicpv-5sgg": Phase="Pending", Reason="", readiness=false. Elapsed: 13.468601571s
Oct 13 19:28:56.898: INFO: Pod "pod-subpath-test-dynamicpv-5sgg": Phase="Pending", Reason="", readiness=false. Elapsed: 15.677791699s
Oct 13 19:28:59.108: INFO: Pod "pod-subpath-test-dynamicpv-5sgg": Phase="Pending", Reason="", readiness=false. Elapsed: 17.888065507s
Oct 13 19:29:01.319: INFO: Pod "pod-subpath-test-dynamicpv-5sgg": Phase="Pending", Reason="", readiness=false. Elapsed: 20.098480079s
Oct 13 19:29:03.531: INFO: Pod "pod-subpath-test-dynamicpv-5sgg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.311131505s
STEP: Saw pod success
Oct 13 19:29:03.531: INFO: Pod "pod-subpath-test-dynamicpv-5sgg" satisfied condition "Succeeded or Failed"
Oct 13 19:29:03.740: INFO: Trying to get logs from node ip-172-20-32-51.ap-southeast-1.compute.internal pod pod-subpath-test-dynamicpv-5sgg container test-container-subpath-dynamicpv-5sgg: <nil>
STEP: delete the pod
Oct 13 19:29:04.169: INFO: Waiting for pod pod-subpath-test-dynamicpv-5sgg to disappear
Oct 13 19:29:04.378: INFO: Pod pod-subpath-test-dynamicpv-5sgg no longer exists
STEP: Deleting pod
Oct 13 19:29:04.378: INFO: Deleting pod "pod-subpath-test-dynamicpv-5sgg" in namespace "provisioning-6919"
... skipping 369 lines ...
Oct 13 19:27:41.580: INFO: Creating resource for dynamic PV
Oct 13 19:27:41.580: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9095-e2e-sc2l85g
STEP: creating a claim
Oct 13 19:27:41.787: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-9095
Oct 13 19:27:42.407: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-9095" in namespace "provisioning-9095" to be "Succeeded or Failed"
Oct 13 19:27:42.613: INFO: Pod "volume-prep-provisioning-9095": Phase="Pending", Reason="", readiness=false. Elapsed: 205.733191ms
Oct 13 19:27:44.818: INFO: Pod "volume-prep-provisioning-9095": Phase="Pending", Reason="", readiness=false. Elapsed: 2.411518094s
Oct 13 19:27:47.027: INFO: Pod "volume-prep-provisioning-9095": Phase="Pending", Reason="", readiness=false. Elapsed: 4.620253996s
Oct 13 19:27:49.233: INFO: Pod "volume-prep-provisioning-9095": Phase="Pending", Reason="", readiness=false. Elapsed: 6.826050914s
Oct 13 19:27:51.440: INFO: Pod "volume-prep-provisioning-9095": Phase="Pending", Reason="", readiness=false. Elapsed: 9.033271103s
Oct 13 19:27:53.646: INFO: Pod "volume-prep-provisioning-9095": Phase="Pending", Reason="", readiness=false. Elapsed: 11.239344554s
... skipping 23 lines ...
Oct 13 19:28:46.618: INFO: Pod "volume-prep-provisioning-9095": Phase="Pending", Reason="", readiness=false. Elapsed: 1m4.210847615s
Oct 13 19:28:48.824: INFO: Pod "volume-prep-provisioning-9095": Phase="Pending", Reason="", readiness=false. Elapsed: 1m6.417298362s
Oct 13 19:28:51.031: INFO: Pod "volume-prep-provisioning-9095": Phase="Pending", Reason="", readiness=false. Elapsed: 1m8.624252306s
Oct 13 19:28:53.237: INFO: Pod "volume-prep-provisioning-9095": Phase="Pending", Reason="", readiness=false. Elapsed: 1m10.830413817s
Oct 13 19:28:55.440: INFO: Pod "volume-prep-provisioning-9095": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m13.033499562s
STEP: Saw pod success
Oct 13 19:28:55.441: INFO: Pod "volume-prep-provisioning-9095" satisfied condition "Succeeded or Failed"
Oct 13 19:28:55.441: INFO: Deleting pod "volume-prep-provisioning-9095" in namespace "provisioning-9095"
Oct 13 19:28:55.648: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-9095" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-zskx
STEP: Checking for subpath error in container status
Oct 13 19:29:30.466: INFO: Deleting pod "pod-subpath-test-dynamicpv-zskx" in namespace "provisioning-9095"
Oct 13 19:29:30.676: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-zskx" to be fully deleted
STEP: Deleting pod
Oct 13 19:29:30.877: INFO: Deleting pod "pod-subpath-test-dynamicpv-zskx" in namespace "provisioning-9095"
STEP: Deleting pvc
Oct 13 19:29:31.482: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comh6s6w"
... skipping 89 lines ...
Oct 13 19:29:20.244: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-1436s7lpg
STEP: creating a claim
Oct 13 19:29:20.454: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-56hp
STEP: Creating a pod to test exec-volume-test
Oct 13 19:29:21.077: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-56hp" in namespace "volume-1436" to be "Succeeded or Failed"
Oct 13 19:29:21.284: INFO: Pod "exec-volume-test-dynamicpv-56hp": Phase="Pending", Reason="", readiness=false. Elapsed: 206.806557ms
Oct 13 19:29:23.491: INFO: Pod "exec-volume-test-dynamicpv-56hp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.414385343s
Oct 13 19:29:25.699: INFO: Pod "exec-volume-test-dynamicpv-56hp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.621571047s
Oct 13 19:29:27.906: INFO: Pod "exec-volume-test-dynamicpv-56hp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.82926057s
Oct 13 19:29:30.114: INFO: Pod "exec-volume-test-dynamicpv-56hp": Phase="Pending", Reason="", readiness=false. Elapsed: 9.037337524s
Oct 13 19:29:32.321: INFO: Pod "exec-volume-test-dynamicpv-56hp": Phase="Pending", Reason="", readiness=false. Elapsed: 11.244237819s
Oct 13 19:29:34.530: INFO: Pod "exec-volume-test-dynamicpv-56hp": Phase="Pending", Reason="", readiness=false. Elapsed: 13.452657288s
Oct 13 19:29:36.737: INFO: Pod "exec-volume-test-dynamicpv-56hp": Phase="Pending", Reason="", readiness=false. Elapsed: 15.660126745s
Oct 13 19:29:38.944: INFO: Pod "exec-volume-test-dynamicpv-56hp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 17.866956736s
STEP: Saw pod success
Oct 13 19:29:38.944: INFO: Pod "exec-volume-test-dynamicpv-56hp" satisfied condition "Succeeded or Failed"
Oct 13 19:29:39.150: INFO: Trying to get logs from node ip-172-20-37-108.ap-southeast-1.compute.internal pod exec-volume-test-dynamicpv-56hp container exec-container-dynamicpv-56hp: <nil>
STEP: delete the pod
Oct 13 19:29:39.574: INFO: Waiting for pod exec-volume-test-dynamicpv-56hp to disappear
Oct 13 19:29:39.780: INFO: Pod exec-volume-test-dynamicpv-56hp no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-56hp
Oct 13 19:29:39.780: INFO: Deleting pod "exec-volume-test-dynamicpv-56hp" in namespace "volume-1436"
... skipping 36 lines ...
Oct 13 19:29:01.492: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-50567qhhg      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-5056    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-50567qhhg,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-5056    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-50567qhhg,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-5056    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-50567qhhg,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-50567qhhg    0cd04ab6-be2e-441e-aedd-c7423349be4f 6652 0 2021-10-13 19:29:01 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-10-13 19:29:01 +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-gvktt pvc- provisioning-5056  1b318bc8-eaee-45ca-80c3-b1f1c95efdc4 6675 0 2021-10-13 19:29:02 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-10-13 19:29: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-50567qhhg,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-a886e5b3-29ea-441e-8e17-e0b6263bfbd0 in namespace provisioning-5056
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Oct 13 19:29:17.807: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-gcdvd" in namespace "provisioning-5056" to be "Succeeded or Failed"
Oct 13 19:29:18.016: INFO: Pod "pvc-volume-tester-writer-gcdvd": Phase="Pending", Reason="", readiness=false. Elapsed: 209.142027ms
Oct 13 19:29:20.227: INFO: Pod "pvc-volume-tester-writer-gcdvd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.420027796s
STEP: Saw pod success
Oct 13 19:29:20.227: INFO: Pod "pvc-volume-tester-writer-gcdvd" satisfied condition "Succeeded or Failed"
Oct 13 19:29:20.647: INFO: Pod pvc-volume-tester-writer-gcdvd has the following logs: 
Oct 13 19:29:20.647: INFO: Deleting pod "pvc-volume-tester-writer-gcdvd" in namespace "provisioning-5056"
Oct 13 19:29:20.861: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-gcdvd" to be fully deleted
STEP: checking the created volume has the correct mount options, is readable and retains data on the same node "ip-172-20-37-108.ap-southeast-1.compute.internal"
Oct 13 19:29:21.697: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-dmbdt" in namespace "provisioning-5056" to be "Succeeded or Failed"
Oct 13 19:29:21.905: INFO: Pod "pvc-volume-tester-reader-dmbdt": Phase="Pending", Reason="", readiness=false. Elapsed: 208.887742ms
Oct 13 19:29:24.116: INFO: Pod "pvc-volume-tester-reader-dmbdt": Phase="Pending", Reason="", readiness=false. Elapsed: 2.419703169s
Oct 13 19:29:26.330: INFO: Pod "pvc-volume-tester-reader-dmbdt": Phase="Pending", Reason="", readiness=false. Elapsed: 4.63365125s
Oct 13 19:29:28.544: INFO: Pod "pvc-volume-tester-reader-dmbdt": Phase="Pending", Reason="", readiness=false. Elapsed: 6.847015252s
Oct 13 19:29:30.760: INFO: Pod "pvc-volume-tester-reader-dmbdt": Phase="Pending", Reason="", readiness=false. Elapsed: 9.063158667s
Oct 13 19:29:32.970: INFO: Pod "pvc-volume-tester-reader-dmbdt": Phase="Pending", Reason="", readiness=false. Elapsed: 11.273438357s
Oct 13 19:29:35.179: INFO: Pod "pvc-volume-tester-reader-dmbdt": Phase="Pending", Reason="", readiness=false. Elapsed: 13.482743178s
Oct 13 19:29:37.388: INFO: Pod "pvc-volume-tester-reader-dmbdt": Phase="Pending", Reason="", readiness=false. Elapsed: 15.691785975s
Oct 13 19:29:39.599: INFO: Pod "pvc-volume-tester-reader-dmbdt": Phase="Pending", Reason="", readiness=false. Elapsed: 17.902795311s
Oct 13 19:29:41.809: INFO: Pod "pvc-volume-tester-reader-dmbdt": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.112104915s
STEP: Saw pod success
Oct 13 19:29:41.809: INFO: Pod "pvc-volume-tester-reader-dmbdt" satisfied condition "Succeeded or Failed"
Oct 13 19:29:42.228: INFO: Pod pvc-volume-tester-reader-dmbdt has the following logs: hello world

Oct 13 19:29:42.228: INFO: Deleting pod "pvc-volume-tester-reader-dmbdt" in namespace "provisioning-5056"
Oct 13 19:29:42.443: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-dmbdt" to be fully deleted
Oct 13 19:29:42.652: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-gvktt] to have phase Bound
Oct 13 19:29:42.860: INFO: PersistentVolumeClaim pvc-gvktt found and phase=Bound (208.40199ms)
... skipping 359 lines ...
Oct 13 19:29:21.966: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-3697-e2e-scl9fgf
STEP: creating a claim
Oct 13 19:29:22.166: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-qpd6
STEP: Creating a pod to test exec-volume-test
Oct 13 19:29:22.768: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-qpd6" in namespace "volume-3697" to be "Succeeded or Failed"
Oct 13 19:29:22.967: INFO: Pod "exec-volume-test-dynamicpv-qpd6": Phase="Pending", Reason="", readiness=false. Elapsed: 198.590873ms
Oct 13 19:29:25.167: INFO: Pod "exec-volume-test-dynamicpv-qpd6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.398634955s
Oct 13 19:29:27.366: INFO: Pod "exec-volume-test-dynamicpv-qpd6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.598055604s
Oct 13 19:29:29.565: INFO: Pod "exec-volume-test-dynamicpv-qpd6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.797287177s
Oct 13 19:29:31.766: INFO: Pod "exec-volume-test-dynamicpv-qpd6": Phase="Pending", Reason="", readiness=false. Elapsed: 8.997819006s
Oct 13 19:29:33.966: INFO: Pod "exec-volume-test-dynamicpv-qpd6": Phase="Pending", Reason="", readiness=false. Elapsed: 11.197597747s
Oct 13 19:29:36.168: INFO: Pod "exec-volume-test-dynamicpv-qpd6": Phase="Pending", Reason="", readiness=false. Elapsed: 13.400153272s
Oct 13 19:29:38.369: INFO: Pod "exec-volume-test-dynamicpv-qpd6": Phase="Pending", Reason="", readiness=false. Elapsed: 15.600461122s
Oct 13 19:29:40.569: INFO: Pod "exec-volume-test-dynamicpv-qpd6": Phase="Pending", Reason="", readiness=false. Elapsed: 17.800644774s
Oct 13 19:29:42.770: INFO: Pod "exec-volume-test-dynamicpv-qpd6": Phase="Pending", Reason="", readiness=false. Elapsed: 20.002314786s
Oct 13 19:29:44.971: INFO: Pod "exec-volume-test-dynamicpv-qpd6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.203168184s
STEP: Saw pod success
Oct 13 19:29:44.971: INFO: Pod "exec-volume-test-dynamicpv-qpd6" satisfied condition "Succeeded or Failed"
Oct 13 19:29:45.170: INFO: Trying to get logs from node ip-172-20-32-51.ap-southeast-1.compute.internal pod exec-volume-test-dynamicpv-qpd6 container exec-container-dynamicpv-qpd6: <nil>
STEP: delete the pod
Oct 13 19:29:45.576: INFO: Waiting for pod exec-volume-test-dynamicpv-qpd6 to disappear
Oct 13 19:29:45.775: INFO: Pod exec-volume-test-dynamicpv-qpd6 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-qpd6
Oct 13 19:29:45.775: INFO: Deleting pod "exec-volume-test-dynamicpv-qpd6" in namespace "volume-3697"
... skipping 128 lines ...
Oct 13 19:29:38.449: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-952697tg4
STEP: creating a claim
Oct 13 19:29:38.659: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-d4pn
STEP: Creating a pod to test atomic-volume-subpath
Oct 13 19:29:39.290: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-d4pn" in namespace "provisioning-9526" to be "Succeeded or Failed"
Oct 13 19:29:39.499: INFO: Pod "pod-subpath-test-dynamicpv-d4pn": Phase="Pending", Reason="", readiness=false. Elapsed: 208.909645ms
Oct 13 19:29:41.709: INFO: Pod "pod-subpath-test-dynamicpv-d4pn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.418498415s
Oct 13 19:29:43.919: INFO: Pod "pod-subpath-test-dynamicpv-d4pn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.628476161s
Oct 13 19:29:46.133: INFO: Pod "pod-subpath-test-dynamicpv-d4pn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.842476277s
Oct 13 19:29:48.345: INFO: Pod "pod-subpath-test-dynamicpv-d4pn": Phase="Pending", Reason="", readiness=false. Elapsed: 9.054923426s
Oct 13 19:29:50.555: INFO: Pod "pod-subpath-test-dynamicpv-d4pn": Phase="Running", Reason="", readiness=true. Elapsed: 11.264755857s
... skipping 4 lines ...
Oct 13 19:30:01.605: INFO: Pod "pod-subpath-test-dynamicpv-d4pn": Phase="Running", Reason="", readiness=true. Elapsed: 22.314381912s
Oct 13 19:30:03.814: INFO: Pod "pod-subpath-test-dynamicpv-d4pn": Phase="Running", Reason="", readiness=true. Elapsed: 24.523782976s
Oct 13 19:30:06.026: INFO: Pod "pod-subpath-test-dynamicpv-d4pn": Phase="Running", Reason="", readiness=true. Elapsed: 26.735905818s
Oct 13 19:30:08.236: INFO: Pod "pod-subpath-test-dynamicpv-d4pn": Phase="Running", Reason="", readiness=true. Elapsed: 28.945361773s
Oct 13 19:30:10.446: INFO: Pod "pod-subpath-test-dynamicpv-d4pn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 31.155832188s
STEP: Saw pod success
Oct 13 19:30:10.446: INFO: Pod "pod-subpath-test-dynamicpv-d4pn" satisfied condition "Succeeded or Failed"
Oct 13 19:30:10.655: INFO: Trying to get logs from node ip-172-20-32-51.ap-southeast-1.compute.internal pod pod-subpath-test-dynamicpv-d4pn container test-container-subpath-dynamicpv-d4pn: <nil>
STEP: delete the pod
Oct 13 19:30:11.100: INFO: Waiting for pod pod-subpath-test-dynamicpv-d4pn to disappear
Oct 13 19:30:11.309: INFO: Pod pod-subpath-test-dynamicpv-d4pn no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-d4pn
Oct 13 19:30:11.309: INFO: Deleting pod "pod-subpath-test-dynamicpv-d4pn" in namespace "provisioning-9526"
... skipping 140 lines ...
Oct 13 19:29:52.918: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2283fjjx5
STEP: creating a claim
Oct 13 19:29:53.125: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-dj4x
STEP: Creating a pod to test subpath
Oct 13 19:29:53.750: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-dj4x" in namespace "provisioning-2283" to be "Succeeded or Failed"
Oct 13 19:29:53.956: INFO: Pod "pod-subpath-test-dynamicpv-dj4x": Phase="Pending", Reason="", readiness=false. Elapsed: 206.614978ms
Oct 13 19:29:56.165: INFO: Pod "pod-subpath-test-dynamicpv-dj4x": Phase="Pending", Reason="", readiness=false. Elapsed: 2.415221584s
Oct 13 19:29:58.373: INFO: Pod "pod-subpath-test-dynamicpv-dj4x": Phase="Pending", Reason="", readiness=false. Elapsed: 4.623748712s
Oct 13 19:30:00.585: INFO: Pod "pod-subpath-test-dynamicpv-dj4x": Phase="Pending", Reason="", readiness=false. Elapsed: 6.835116988s
Oct 13 19:30:02.793: INFO: Pod "pod-subpath-test-dynamicpv-dj4x": Phase="Pending", Reason="", readiness=false. Elapsed: 9.042874975s
Oct 13 19:30:05.001: INFO: Pod "pod-subpath-test-dynamicpv-dj4x": Phase="Pending", Reason="", readiness=false. Elapsed: 11.251172212s
Oct 13 19:30:07.209: INFO: Pod "pod-subpath-test-dynamicpv-dj4x": Phase="Pending", Reason="", readiness=false. Elapsed: 13.459431959s
Oct 13 19:30:09.417: INFO: Pod "pod-subpath-test-dynamicpv-dj4x": Phase="Succeeded", Reason="", readiness=false. Elapsed: 15.667390966s
STEP: Saw pod success
Oct 13 19:30:09.417: INFO: Pod "pod-subpath-test-dynamicpv-dj4x" satisfied condition "Succeeded or Failed"
Oct 13 19:30:09.624: INFO: Trying to get logs from node ip-172-20-37-108.ap-southeast-1.compute.internal pod pod-subpath-test-dynamicpv-dj4x container test-container-volume-dynamicpv-dj4x: <nil>
STEP: delete the pod
Oct 13 19:30:10.062: INFO: Waiting for pod pod-subpath-test-dynamicpv-dj4x to disappear
Oct 13 19:30:10.269: INFO: Pod pod-subpath-test-dynamicpv-dj4x no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-dj4x
Oct 13 19:30:10.269: INFO: Deleting pod "pod-subpath-test-dynamicpv-dj4x" in namespace "provisioning-2283"
... skipping 138 lines ...
Oct 13 19:30:06.814: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Oct 13 19:30:08.161: INFO: Successfully created a new PD: "aws://ap-southeast-1a/vol-0091a4d4adc0da48b".
Oct 13 19:30:08.162: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-qbxd
STEP: Creating a pod to test exec-volume-test
Oct 13 19:30:08.419: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-qbxd" in namespace "volume-6498" to be "Succeeded or Failed"
Oct 13 19:30:08.621: INFO: Pod "exec-volume-test-inlinevolume-qbxd": Phase="Pending", Reason="", readiness=false. Elapsed: 201.838026ms
Oct 13 19:30:10.823: INFO: Pod "exec-volume-test-inlinevolume-qbxd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.404278239s
Oct 13 19:30:13.025: INFO: Pod "exec-volume-test-inlinevolume-qbxd": Phase="Pending", Reason="", readiness=false. Elapsed: 4.606304792s
Oct 13 19:30:15.231: INFO: Pod "exec-volume-test-inlinevolume-qbxd": Phase="Pending", Reason="", readiness=false. Elapsed: 6.812042194s
Oct 13 19:30:17.435: INFO: Pod "exec-volume-test-inlinevolume-qbxd": Phase="Pending", Reason="", readiness=false. Elapsed: 9.01584019s
Oct 13 19:30:19.638: INFO: Pod "exec-volume-test-inlinevolume-qbxd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 11.219140392s
STEP: Saw pod success
Oct 13 19:30:19.638: INFO: Pod "exec-volume-test-inlinevolume-qbxd" satisfied condition "Succeeded or Failed"
Oct 13 19:30:19.840: INFO: Trying to get logs from node ip-172-20-37-108.ap-southeast-1.compute.internal pod exec-volume-test-inlinevolume-qbxd container exec-container-inlinevolume-qbxd: <nil>
STEP: delete the pod
Oct 13 19:30:20.250: INFO: Waiting for pod exec-volume-test-inlinevolume-qbxd to disappear
Oct 13 19:30:20.454: INFO: Pod exec-volume-test-inlinevolume-qbxd no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-qbxd
Oct 13 19:30:20.454: INFO: Deleting pod "exec-volume-test-inlinevolume-qbxd" in namespace "volume-6498"
Oct 13 19:30:21.057: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-0091a4d4adc0da48b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0091a4d4adc0da48b is currently attached to i-013c922fab027b6ad
	status code: 400, request id: 18f09a74-db63-4de1-8128-956ce97648ec
Oct 13 19:30:27.007: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-0091a4d4adc0da48b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0091a4d4adc0da48b is currently attached to i-013c922fab027b6ad
	status code: 400, request id: 70f02d50-fac5-48d7-85d1-c69582b7d0d5
Oct 13 19:30:32.942: INFO: Successfully deleted PD "aws://ap-southeast-1a/vol-0091a4d4adc0da48b".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 19:30:32.942: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-6498" for this suite.
... skipping 699 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.R8VRd6QTn/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.R8VRd6QTn/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.R8VRd6QTn/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.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 89 lines ...
Oct 13 19:29:49.144: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-8113-e2e-scgmbz2      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-8113    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-8113-e2e-scgmbz2,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-8113    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-8113-e2e-scgmbz2,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-8113    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-8113-e2e-scgmbz2,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-8113-e2e-scgmbz2    cbcfac38-2266-4cd8-909e-d6cf53b6d89c 7944 0 2021-10-13 19:29:49 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-10-13 19:29:49 +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-mxqnx pvc- provisioning-8113  eefe0594-82f2-46d4-9835-8f249ae126af 7964 0 2021-10-13 19:29:50 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-10-13 19:29:50 +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-8113-e2e-scgmbz2,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-7138e802-fac2-4d84-a797-0f204a43e697 in namespace provisioning-8113
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Oct 13 19:30:01.371: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-gvj7n" in namespace "provisioning-8113" to be "Succeeded or Failed"
Oct 13 19:30:01.573: INFO: Pod "pvc-volume-tester-writer-gvj7n": Phase="Pending", Reason="", readiness=false. Elapsed: 201.18275ms
Oct 13 19:30:03.775: INFO: Pod "pvc-volume-tester-writer-gvj7n": Phase="Pending", Reason="", readiness=false. Elapsed: 2.404020254s
Oct 13 19:30:05.979: INFO: Pod "pvc-volume-tester-writer-gvj7n": Phase="Pending", Reason="", readiness=false. Elapsed: 4.607720918s
Oct 13 19:30:08.182: INFO: Pod "pvc-volume-tester-writer-gvj7n": Phase="Pending", Reason="", readiness=false. Elapsed: 6.810597064s
Oct 13 19:30:10.388: INFO: Pod "pvc-volume-tester-writer-gvj7n": Phase="Pending", Reason="", readiness=false. Elapsed: 9.016849091s
Oct 13 19:30:12.592: INFO: Pod "pvc-volume-tester-writer-gvj7n": Phase="Pending", Reason="", readiness=false. Elapsed: 11.22018709s
... skipping 7 lines ...
Oct 13 19:30:30.241: INFO: Pod "pvc-volume-tester-writer-gvj7n": Phase="Pending", Reason="", readiness=false. Elapsed: 28.869218405s
Oct 13 19:30:32.447: INFO: Pod "pvc-volume-tester-writer-gvj7n": Phase="Pending", Reason="", readiness=false. Elapsed: 31.075560901s
Oct 13 19:30:34.653: INFO: Pod "pvc-volume-tester-writer-gvj7n": Phase="Pending", Reason="", readiness=false. Elapsed: 33.281947159s
Oct 13 19:30:36.860: INFO: Pod "pvc-volume-tester-writer-gvj7n": Phase="Pending", Reason="", readiness=false. Elapsed: 35.48885639s
Oct 13 19:30:39.067: INFO: Pod "pvc-volume-tester-writer-gvj7n": Phase="Succeeded", Reason="", readiness=false. Elapsed: 37.695729257s
STEP: Saw pod success
Oct 13 19:30:39.067: INFO: Pod "pvc-volume-tester-writer-gvj7n" satisfied condition "Succeeded or Failed"
Oct 13 19:30:39.482: INFO: Pod pvc-volume-tester-writer-gvj7n has the following logs: 
Oct 13 19:30:39.482: INFO: Deleting pod "pvc-volume-tester-writer-gvj7n" in namespace "provisioning-8113"
Oct 13 19:30:39.694: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-gvj7n" to be fully deleted
STEP: checking the created volume has the correct mount options, is readable and retains data on the same node "ip-172-20-37-108.ap-southeast-1.compute.internal"
Oct 13 19:30:40.522: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-vbq2b" in namespace "provisioning-8113" to be "Succeeded or Failed"
Oct 13 19:30:40.728: INFO: Pod "pvc-volume-tester-reader-vbq2b": Phase="Pending", Reason="", readiness=false. Elapsed: 205.892408ms
Oct 13 19:30:42.934: INFO: Pod "pvc-volume-tester-reader-vbq2b": Phase="Pending", Reason="", readiness=false. Elapsed: 2.411626739s
Oct 13 19:30:45.140: INFO: Pod "pvc-volume-tester-reader-vbq2b": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.617639923s
STEP: Saw pod success
Oct 13 19:30:45.140: INFO: Pod "pvc-volume-tester-reader-vbq2b" satisfied condition "Succeeded or Failed"
Oct 13 19:30:45.556: INFO: Pod pvc-volume-tester-reader-vbq2b has the following logs: hello world

Oct 13 19:30:45.556: INFO: Deleting pod "pvc-volume-tester-reader-vbq2b" in namespace "provisioning-8113"
Oct 13 19:30:45.774: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-vbq2b" to be fully deleted
Oct 13 19:30:45.980: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-mxqnx] to have phase Bound
Oct 13 19:30:46.185: INFO: PersistentVolumeClaim pvc-mxqnx found and phase=Bound (205.216526ms)
... skipping 344 lines ...
Oct 13 19:30:39.871: INFO: Creating resource for dynamic PV
Oct 13 19:30:39.871: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-9514-e2e-scmjf94
STEP: creating a claim
STEP: Expanding non-expandable pvc
Oct 13 19:30:40.487: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Oct 13 19:30:40.896: INFO: Error updating pvc ebs.csi.aws.com7sfzf: PersistentVolumeClaim "ebs.csi.aws.com7sfzf" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-9514-e2e-scmjf94",
  	... // 3 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Oct 13 19:31:11.714: INFO: Error updating pvc ebs.csi.aws.com7sfzf: PersistentVolumeClaim "ebs.csi.aws.com7sfzf" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 176 lines ...

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

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

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

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.R8VRd6QTn/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.R8VRd6QTn/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.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 12 lines ...
Oct 13 19:26:36.450: INFO: Creating resource for dynamic PV
Oct 13 19:26:36.450: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-5846-e2e-sctfwnw
STEP: creating a claim
Oct 13 19:26:36.658: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Oct 13 19:26:37.283: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-7jqgp" in namespace "snapshotting-5846" to be "Succeeded or Failed"
Oct 13 19:26:37.541: INFO: Pod "pvc-snapshottable-tester-7jqgp": Phase="Pending", Reason="", readiness=false. Elapsed: 257.177078ms
Oct 13 19:26:39.747: INFO: Pod "pvc-snapshottable-tester-7jqgp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.46397409s
Oct 13 19:26:41.964: INFO: Pod "pvc-snapshottable-tester-7jqgp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.681138727s
Oct 13 19:26:44.171: INFO: Pod "pvc-snapshottable-tester-7jqgp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.887984165s
Oct 13 19:26:46.379: INFO: Pod "pvc-snapshottable-tester-7jqgp": Phase="Pending", Reason="", readiness=false. Elapsed: 9.095641736s
Oct 13 19:26:48.586: INFO: Pod "pvc-snapshottable-tester-7jqgp": Phase="Pending", Reason="", readiness=false. Elapsed: 11.302485301s
... skipping 2 lines ...
Oct 13 19:26:55.210: INFO: Pod "pvc-snapshottable-tester-7jqgp": Phase="Pending", Reason="", readiness=false. Elapsed: 17.926395725s
Oct 13 19:26:57.416: INFO: Pod "pvc-snapshottable-tester-7jqgp": Phase="Pending", Reason="", readiness=false. Elapsed: 20.133085049s
Oct 13 19:26:59.624: INFO: Pod "pvc-snapshottable-tester-7jqgp": Phase="Pending", Reason="", readiness=false. Elapsed: 22.340639778s
Oct 13 19:27:01.831: INFO: Pod "pvc-snapshottable-tester-7jqgp": Phase="Pending", Reason="", readiness=false. Elapsed: 24.547860557s
Oct 13 19:27:04.038: INFO: Pod "pvc-snapshottable-tester-7jqgp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.755096805s
STEP: Saw pod success
Oct 13 19:27:04.039: INFO: Pod "pvc-snapshottable-tester-7jqgp" satisfied condition "Succeeded or Failed"
Oct 13 19:27:04.454: INFO: Pod pvc-snapshottable-tester-7jqgp has the following logs: 
Oct 13 19:27:04.454: INFO: Deleting pod "pvc-snapshottable-tester-7jqgp" in namespace "snapshotting-5846"
Oct 13 19:27:04.669: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-7jqgp" to be fully deleted
Oct 13 19:27:04.877: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comq957k] to have phase Bound
Oct 13 19:27:05.083: INFO: PersistentVolumeClaim ebs.csi.aws.comq957k found and phase=Bound (205.80645ms)
STEP: [init] checking the claim
... skipping 81 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:243
STEP: checking the snapshot
STEP: checking the SnapshotContent
STEP: Modifying source data test
STEP: modifying the data in the source PVC
Oct 13 19:29:44.161: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-b7bp5" in namespace "snapshotting-5846" to be "Succeeded or Failed"
Oct 13 19:29:44.367: INFO: Pod "pvc-snapshottable-data-tester-b7bp5": Phase="Pending", Reason="", readiness=false. Elapsed: 206.169183ms
Oct 13 19:29:46.574: INFO: Pod "pvc-snapshottable-data-tester-b7bp5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.413536071s
Oct 13 19:29:48.783: INFO: Pod "pvc-snapshottable-data-tester-b7bp5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.622447022s
Oct 13 19:29:50.991: INFO: Pod "pvc-snapshottable-data-tester-b7bp5": Phase="Pending", Reason="", readiness=false. Elapsed: 6.83064124s
Oct 13 19:29:53.199: INFO: Pod "pvc-snapshottable-data-tester-b7bp5": Phase="Pending", Reason="", readiness=false. Elapsed: 9.038482262s
Oct 13 19:29:55.407: INFO: Pod "pvc-snapshottable-data-tester-b7bp5": Phase="Pending", Reason="", readiness=false. Elapsed: 11.246493335s
Oct 13 19:29:57.615: INFO: Pod "pvc-snapshottable-data-tester-b7bp5": Phase="Pending", Reason="", readiness=false. Elapsed: 13.454260476s
Oct 13 19:29:59.825: INFO: Pod "pvc-snapshottable-data-tester-b7bp5": Phase="Pending", Reason="", readiness=false. Elapsed: 15.664303649s
Oct 13 19:30:02.033: INFO: Pod "pvc-snapshottable-data-tester-b7bp5": Phase="Pending", Reason="", readiness=false. Elapsed: 17.872152716s
Oct 13 19:30:04.241: INFO: Pod "pvc-snapshottable-data-tester-b7bp5": Phase="Pending", Reason="", readiness=false. Elapsed: 20.079949107s
Oct 13 19:30:06.448: INFO: Pod "pvc-snapshottable-data-tester-b7bp5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.287691007s
STEP: Saw pod success
Oct 13 19:30:06.449: INFO: Pod "pvc-snapshottable-data-tester-b7bp5" satisfied condition "Succeeded or Failed"
Oct 13 19:30:06.868: INFO: Pod pvc-snapshottable-data-tester-b7bp5 has the following logs: 
Oct 13 19:30:06.868: INFO: Deleting pod "pvc-snapshottable-data-tester-b7bp5" in namespace "snapshotting-5846"
Oct 13 19:30:07.079: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-b7bp5" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Oct 13 19:30:30.123: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-c3f2775103-c95b4.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-5846 exec restored-pvc-tester-rmvlz --namespace=snapshotting-5846 -- cat /mnt/test/data'
... skipping 28 lines ...
Oct 13 19:30:55.907: INFO: volumesnapshotcontents snapcontent-91f5401a-305e-48b9-8152-a30fb4ed6979 has been found and is not deleted
Oct 13 19:30:57.114: INFO: volumesnapshotcontents snapcontent-91f5401a-305e-48b9-8152-a30fb4ed6979 has been found and is not deleted
Oct 13 19:30:58.322: INFO: volumesnapshotcontents snapcontent-91f5401a-305e-48b9-8152-a30fb4ed6979 has been found and is not deleted
Oct 13 19:30:59.529: INFO: volumesnapshotcontents snapcontent-91f5401a-305e-48b9-8152-a30fb4ed6979 has been found and is not deleted
Oct 13 19:31:00.737: INFO: volumesnapshotcontents snapcontent-91f5401a-305e-48b9-8152-a30fb4ed6979 has been found and is not deleted
Oct 13 19:31:01.945: INFO: volumesnapshotcontents snapcontent-91f5401a-305e-48b9-8152-a30fb4ed6979 has been found and is not deleted
Oct 13 19:31:02.945: INFO: WaitUntil failed after reaching the timeout 30s
[AfterEach] volume snapshot controller
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:221
Oct 13 19:31:03.154: INFO: Pod restored-pvc-tester-rmvlz has the following logs: 
Oct 13 19:31:03.154: INFO: Deleting pod "restored-pvc-tester-rmvlz" in namespace "snapshotting-5846"
Oct 13 19:31:03.361: INFO: Wait up to 5m0s for pod "restored-pvc-tester-rmvlz" to be fully deleted
Oct 13 19:31:35.775: INFO: deleting claim "snapshotting-5846"/"pvc-hfn5f"
... skipping 461 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.R8VRd6QTn/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.R8VRd6QTn/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.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 261 lines ...
Oct 13 19:31:22.932: INFO: Creating resource for dynamic PV
Oct 13 19:31:22.932: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-8511f9qcc
STEP: creating a claim
STEP: Expanding non-expandable pvc
Oct 13 19:31:23.525: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Oct 13 19:31:23.922: INFO: Error updating pvc awsd69tw: PersistentVolumeClaim "awsd69tw" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8511f9qcc",
  	... // 3 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Oct 13 19:31:54.722: INFO: Error updating pvc awsd69tw: PersistentVolumeClaim "awsd69tw" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 41 lines ...
Oct 13 19:30:54.654: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-2607-e2e-scj65w8
STEP: creating a claim
Oct 13 19:30:54.859: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-ln8z
STEP: Creating a pod to test exec-volume-test
Oct 13 19:30:55.476: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-ln8z" in namespace "volume-2607" to be "Succeeded or Failed"
Oct 13 19:30:55.681: INFO: Pod "exec-volume-test-dynamicpv-ln8z": Phase="Pending", Reason="", readiness=false. Elapsed: 204.71105ms
Oct 13 19:30:57.886: INFO: Pod "exec-volume-test-dynamicpv-ln8z": Phase="Pending", Reason="", readiness=false. Elapsed: 2.409740955s
Oct 13 19:31:00.091: INFO: Pod "exec-volume-test-dynamicpv-ln8z": Phase="Pending", Reason="", readiness=false. Elapsed: 4.615599431s
Oct 13 19:31:02.297: INFO: Pod "exec-volume-test-dynamicpv-ln8z": Phase="Pending", Reason="", readiness=false. Elapsed: 6.821510814s
Oct 13 19:31:04.502: INFO: Pod "exec-volume-test-dynamicpv-ln8z": Phase="Pending", Reason="", readiness=false. Elapsed: 9.026605004s
Oct 13 19:31:06.714: INFO: Pod "exec-volume-test-dynamicpv-ln8z": Phase="Pending", Reason="", readiness=false. Elapsed: 11.237874383s
Oct 13 19:31:08.920: INFO: Pod "exec-volume-test-dynamicpv-ln8z": Phase="Pending", Reason="", readiness=false. Elapsed: 13.443914995s
Oct 13 19:31:11.125: INFO: Pod "exec-volume-test-dynamicpv-ln8z": Phase="Pending", Reason="", readiness=false. Elapsed: 15.649064344s
Oct 13 19:31:13.330: INFO: Pod "exec-volume-test-dynamicpv-ln8z": Phase="Pending", Reason="", readiness=false. Elapsed: 17.854340679s
Oct 13 19:31:15.535: INFO: Pod "exec-volume-test-dynamicpv-ln8z": Phase="Pending", Reason="", readiness=false. Elapsed: 20.059299031s
Oct 13 19:31:17.741: INFO: Pod "exec-volume-test-dynamicpv-ln8z": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.265214239s
STEP: Saw pod success
Oct 13 19:31:17.741: INFO: Pod "exec-volume-test-dynamicpv-ln8z" satisfied condition "Succeeded or Failed"
Oct 13 19:31:17.946: INFO: Trying to get logs from node ip-172-20-37-108.ap-southeast-1.compute.internal pod exec-volume-test-dynamicpv-ln8z container exec-container-dynamicpv-ln8z: <nil>
STEP: delete the pod
Oct 13 19:31:18.375: INFO: Waiting for pod exec-volume-test-dynamicpv-ln8z to disappear
Oct 13 19:31:18.586: INFO: Pod exec-volume-test-dynamicpv-ln8z no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-ln8z
Oct 13 19:31:18.586: INFO: Deleting pod "exec-volume-test-dynamicpv-ln8z" in namespace "volume-2607"
... skipping 252 lines ...
Oct 13 19:31:37.685: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-384-e2e-scrnr4k
STEP: creating a claim
Oct 13 19:31:37.895: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-ddn2
STEP: Creating a pod to test subpath
Oct 13 19:31:38.525: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-ddn2" in namespace "provisioning-384" to be "Succeeded or Failed"
Oct 13 19:31:38.734: INFO: Pod "pod-subpath-test-dynamicpv-ddn2": Phase="Pending", Reason="", readiness=false. Elapsed: 208.706077ms
Oct 13 19:31:40.943: INFO: Pod "pod-subpath-test-dynamicpv-ddn2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.418108441s
Oct 13 19:31:43.153: INFO: Pod "pod-subpath-test-dynamicpv-ddn2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.627587174s
Oct 13 19:31:45.364: INFO: Pod "pod-subpath-test-dynamicpv-ddn2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.839284686s
Oct 13 19:31:47.574: INFO: Pod "pod-subpath-test-dynamicpv-ddn2": Phase="Pending", Reason="", readiness=false. Elapsed: 9.049014489s
Oct 13 19:31:49.784: INFO: Pod "pod-subpath-test-dynamicpv-ddn2": Phase="Pending", Reason="", readiness=false. Elapsed: 11.258451827s
Oct 13 19:31:51.994: INFO: Pod "pod-subpath-test-dynamicpv-ddn2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 13.469337184s
STEP: Saw pod success
Oct 13 19:31:51.995: INFO: Pod "pod-subpath-test-dynamicpv-ddn2" satisfied condition "Succeeded or Failed"
Oct 13 19:31:52.203: INFO: Trying to get logs from node ip-172-20-32-51.ap-southeast-1.compute.internal pod pod-subpath-test-dynamicpv-ddn2 container test-container-volume-dynamicpv-ddn2: <nil>
STEP: delete the pod
Oct 13 19:31:52.633: INFO: Waiting for pod pod-subpath-test-dynamicpv-ddn2 to disappear
Oct 13 19:31:52.842: INFO: Pod pod-subpath-test-dynamicpv-ddn2 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-ddn2
Oct 13 19:31:52.842: INFO: Deleting pod "pod-subpath-test-dynamicpv-ddn2" in namespace "provisioning-384"
... skipping 32 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.R8VRd6QTn/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.R8VRd6QTn/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.R8VRd6QTn/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.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 313 lines ...
Oct 13 19:31:45.663: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Oct 13 19:31:46.799: INFO: Successfully created a new PD: "aws://ap-southeast-1a/vol-05e1d613dca6bebeb".
Oct 13 19:31:46.800: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-lll9
STEP: Creating a pod to test exec-volume-test
Oct 13 19:31:47.011: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-lll9" in namespace "volume-2132" to be "Succeeded or Failed"
Oct 13 19:31:47.220: INFO: Pod "exec-volume-test-inlinevolume-lll9": Phase="Pending", Reason="", readiness=false. Elapsed: 209.037016ms
Oct 13 19:31:49.430: INFO: Pod "exec-volume-test-inlinevolume-lll9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.419159741s
Oct 13 19:31:51.639: INFO: Pod "exec-volume-test-inlinevolume-lll9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.628456543s
Oct 13 19:31:53.849: INFO: Pod "exec-volume-test-inlinevolume-lll9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.838440834s
Oct 13 19:31:56.067: INFO: Pod "exec-volume-test-inlinevolume-lll9": Phase="Pending", Reason="", readiness=false. Elapsed: 9.056158804s
Oct 13 19:31:58.282: INFO: Pod "exec-volume-test-inlinevolume-lll9": Phase="Pending", Reason="", readiness=false. Elapsed: 11.271324186s
Oct 13 19:32:00.493: INFO: Pod "exec-volume-test-inlinevolume-lll9": Phase="Pending", Reason="", readiness=false. Elapsed: 13.482068951s
Oct 13 19:32:02.703: INFO: Pod "exec-volume-test-inlinevolume-lll9": Phase="Pending", Reason="", readiness=false. Elapsed: 15.691777832s
Oct 13 19:32:04.913: INFO: Pod "exec-volume-test-inlinevolume-lll9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 17.902401002s
STEP: Saw pod success
Oct 13 19:32:04.913: INFO: Pod "exec-volume-test-inlinevolume-lll9" satisfied condition "Succeeded or Failed"
Oct 13 19:32:05.128: INFO: Trying to get logs from node ip-172-20-46-86.ap-southeast-1.compute.internal pod exec-volume-test-inlinevolume-lll9 container exec-container-inlinevolume-lll9: <nil>
STEP: delete the pod
Oct 13 19:32:05.629: INFO: Waiting for pod exec-volume-test-inlinevolume-lll9 to disappear
Oct 13 19:32:05.839: INFO: Pod exec-volume-test-inlinevolume-lll9 no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-lll9
Oct 13 19:32:05.839: INFO: Deleting pod "exec-volume-test-inlinevolume-lll9" in namespace "volume-2132"
Oct 13 19:32:06.358: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-05e1d613dca6bebeb", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05e1d613dca6bebeb is currently attached to i-0c7ecffbeb1cae944
	status code: 400, request id: 1106e047-6342-4aec-aa7f-423c51cd7b2f
Oct 13 19:32:12.373: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-05e1d613dca6bebeb", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05e1d613dca6bebeb is currently attached to i-0c7ecffbeb1cae944
	status code: 400, request id: 9f5b64b1-e4c3-44ec-a1c8-97052edcaee0
Oct 13 19:32:18.343: INFO: Successfully deleted PD "aws://ap-southeast-1a/vol-05e1d613dca6bebeb".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 19:32:18.343: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-2132" for this suite.
... skipping 37 lines ...

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

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

    /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 635 lines ...
Oct 13 19:31:51.795: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7620-e2e-sczqgj7
STEP: creating a claim
Oct 13 19:31:52.001: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-jmsb
STEP: Creating a pod to test subpath
Oct 13 19:31:52.620: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-jmsb" in namespace "provisioning-7620" to be "Succeeded or Failed"
Oct 13 19:31:52.825: INFO: Pod "pod-subpath-test-dynamicpv-jmsb": Phase="Pending", Reason="", readiness=false. Elapsed: 205.080931ms
Oct 13 19:31:55.031: INFO: Pod "pod-subpath-test-dynamicpv-jmsb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.411551476s
Oct 13 19:31:57.237: INFO: Pod "pod-subpath-test-dynamicpv-jmsb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.616883142s
Oct 13 19:31:59.442: INFO: Pod "pod-subpath-test-dynamicpv-jmsb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.822246668s
Oct 13 19:32:01.650: INFO: Pod "pod-subpath-test-dynamicpv-jmsb": Phase="Pending", Reason="", readiness=false. Elapsed: 9.029971256s
Oct 13 19:32:03.856: INFO: Pod "pod-subpath-test-dynamicpv-jmsb": Phase="Pending", Reason="", readiness=false. Elapsed: 11.236472109s
Oct 13 19:32:06.064: INFO: Pod "pod-subpath-test-dynamicpv-jmsb": Phase="Pending", Reason="", readiness=false. Elapsed: 13.443874266s
Oct 13 19:32:08.269: INFO: Pod "pod-subpath-test-dynamicpv-jmsb": Phase="Pending", Reason="", readiness=false. Elapsed: 15.649539072s
Oct 13 19:32:10.475: INFO: Pod "pod-subpath-test-dynamicpv-jmsb": Phase="Pending", Reason="", readiness=false. Elapsed: 17.855225633s
Oct 13 19:32:12.680: INFO: Pod "pod-subpath-test-dynamicpv-jmsb": Phase="Pending", Reason="", readiness=false. Elapsed: 20.06053106s
Oct 13 19:32:14.888: INFO: Pod "pod-subpath-test-dynamicpv-jmsb": Phase="Pending", Reason="", readiness=false. Elapsed: 22.26797722s
Oct 13 19:32:17.095: INFO: Pod "pod-subpath-test-dynamicpv-jmsb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.474905699s
STEP: Saw pod success
Oct 13 19:32:17.095: INFO: Pod "pod-subpath-test-dynamicpv-jmsb" satisfied condition "Succeeded or Failed"
Oct 13 19:32:17.300: INFO: Trying to get logs from node ip-172-20-32-51.ap-southeast-1.compute.internal pod pod-subpath-test-dynamicpv-jmsb container test-container-subpath-dynamicpv-jmsb: <nil>
STEP: delete the pod
Oct 13 19:32:17.723: INFO: Waiting for pod pod-subpath-test-dynamicpv-jmsb to disappear
Oct 13 19:32:17.929: INFO: Pod pod-subpath-test-dynamicpv-jmsb no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-jmsb
Oct 13 19:32:17.929: INFO: Deleting pod "pod-subpath-test-dynamicpv-jmsb" in namespace "provisioning-7620"
... skipping 39 lines ...
Oct 13 19:32:36.880: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 54 lines ...
Oct 13 19:32:26.327: INFO: Waiting for pod aws-client to disappear
Oct 13 19:32:26.525: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Oct 13 19:32:26.525: INFO: Deleting PersistentVolumeClaim "pvc-7ptsq"
Oct 13 19:32:26.727: INFO: Deleting PersistentVolume "aws-sbtjj"
Oct 13 19:32:27.221: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-01cedef9facc50f2c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01cedef9facc50f2c is currently attached to i-08bcea51a1937d594
	status code: 400, request id: 404eb25a-3fdd-465e-8439-aa77cd7a10a5
Oct 13 19:32:33.213: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-01cedef9facc50f2c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01cedef9facc50f2c is currently attached to i-08bcea51a1937d594
	status code: 400, request id: 2c53d192-09d8-4a74-aa5d-45add1fd9706
Oct 13 19:32:39.194: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-01cedef9facc50f2c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01cedef9facc50f2c is currently attached to i-08bcea51a1937d594
	status code: 400, request id: 258ba31d-9d2d-4443-8305-c20548b3a37a
Oct 13 19:32:45.127: INFO: Successfully deleted PD "aws://ap-southeast-1a/vol-01cedef9facc50f2c".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 19:32:45.128: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-7803" for this suite.
... skipping 360 lines ...
Oct 13 19:32:26.353: INFO: Pod aws-client still exists
Oct 13 19:32:28.353: INFO: Waiting for pod aws-client to disappear
Oct 13 19:32:28.557: INFO: Pod aws-client still exists
Oct 13 19:32:30.353: INFO: Waiting for pod aws-client to disappear
Oct 13 19:32:30.557: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Oct 13 19:32:31.538: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-0e60f1a098f828dd1", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e60f1a098f828dd1 is currently attached to i-013c922fab027b6ad
	status code: 400, request id: 3ecb7e06-a961-4f70-ba1e-cb15c0a11106
Oct 13 19:32:37.542: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-0e60f1a098f828dd1", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e60f1a098f828dd1 is currently attached to i-013c922fab027b6ad
	status code: 400, request id: 1c34033f-c340-4b2d-ac6e-8954183b154e
Oct 13 19:32:43.533: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-0e60f1a098f828dd1", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e60f1a098f828dd1 is currently attached to i-013c922fab027b6ad
	status code: 400, request id: 313b3eae-4f91-45ff-9e74-5d39e327fc11
Oct 13 19:32:49.550: INFO: Successfully deleted PD "aws://ap-southeast-1a/vol-0e60f1a098f828dd1".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 19:32:49.550: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-7318" for this suite.
... skipping 39 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 19:32:19.681: 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.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Oct 13 19:32:20.689: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Oct 13 19:32:21.777: INFO: Successfully created a new PD: "aws://ap-southeast-1a/vol-09f0fbb124e607a2d".
Oct 13 19:32:21.777: INFO: Creating resource for pre-provisioned PV
Oct 13 19:32:21.777: INFO: Creating PVC and PV
... skipping 6 lines ...
Oct 13 19:32:29.006: INFO: PersistentVolumeClaim pvc-qmfsz found but phase is Pending instead of Bound.
Oct 13 19:32:31.209: INFO: PersistentVolumeClaim pvc-qmfsz found but phase is Pending instead of Bound.
Oct 13 19:32:33.410: INFO: PersistentVolumeClaim pvc-qmfsz found and phase=Bound (11.229034778s)
Oct 13 19:32:33.410: INFO: Waiting up to 3m0s for PersistentVolume aws-28hwh to have phase Bound
Oct 13 19:32:33.611: INFO: PersistentVolume aws-28hwh found and phase=Bound (200.711928ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Oct 13 19:32:36.821: INFO: Deleting pod "pod-ffa7048d-fa20-4a31-8e07-12a0fb008a73" in namespace "volumemode-7331"
Oct 13 19:32:37.023: INFO: Wait up to 5m0s for pod "pod-ffa7048d-fa20-4a31-8e07-12a0fb008a73" to be fully deleted
STEP: Deleting pv and pvc
Oct 13 19:32:39.425: INFO: Deleting PersistentVolumeClaim "pvc-qmfsz"
Oct 13 19:32:39.628: INFO: Deleting PersistentVolume "aws-28hwh"
Oct 13 19:32:40.132: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-09f0fbb124e607a2d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-09f0fbb124e607a2d is currently attached to i-0eabc97ff75480cc2
	status code: 400, request id: ac5bb3a8-157b-4ea6-9ca2-27ff5a636fcd
Oct 13 19:32:46.071: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-09f0fbb124e607a2d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-09f0fbb124e607a2d is currently attached to i-0eabc97ff75480cc2
	status code: 400, request id: 52d3be6f-f237-4bb2-a2b7-6cf4675e3416
Oct 13 19:32:52.018: INFO: Successfully deleted PD "aws://ap-southeast-1a/vol-09f0fbb124e607a2d".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 19:32:52.018: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-7331" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.R8VRd6QTn/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.R8VRd6QTn/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
    /tmp/kops.R8VRd6QTn/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.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Oct 13 19:32:52.427: INFO: Driver aws doesn't support CSIInlineVolume -- skipping
[AfterEach] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral
... skipping 23 lines ...

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

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 23 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 19:31:50.911: 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.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Oct 13 19:31:51.940: INFO: Creating resource for dynamic PV
Oct 13 19:31:51.940: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4450-e2e-sc2t59g
STEP: creating a claim
Oct 13 19:31:52.147: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-7x8r
STEP: Checking for subpath error in container status
Oct 13 19:32:35.176: INFO: Deleting pod "pod-subpath-test-dynamicpv-7x8r" in namespace "provisioning-4450"
Oct 13 19:32:35.382: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-7x8r" to be fully deleted
STEP: Deleting pod
Oct 13 19:32:37.794: INFO: Deleting pod "pod-subpath-test-dynamicpv-7x8r" in namespace "provisioning-4450"
STEP: Deleting pvc
Oct 13 19:32:38.410: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comcsdx2"
... skipping 11 lines ...

• [SLOW TEST:64.150 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.R8VRd6QTn/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.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 19:32:21.923: 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.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Oct 13 19:32:22.932: INFO: Creating resource for dynamic PV
Oct 13 19:32:22.932: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4853-e2e-scdfhpq
STEP: creating a claim
Oct 13 19:32:23.135: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-242r
STEP: Checking for subpath error in container status
Oct 13 19:32:40.151: INFO: Deleting pod "pod-subpath-test-dynamicpv-242r" in namespace "provisioning-4853"
Oct 13 19:32:40.357: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-242r" to be fully deleted
STEP: Deleting pod
Oct 13 19:32:42.762: INFO: Deleting pod "pod-subpath-test-dynamicpv-242r" in namespace "provisioning-4853"
STEP: Deleting pvc
Oct 13 19:32:43.368: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com4wb4m"
... skipping 11 lines ...

• [SLOW TEST:38.064 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.R8VRd6QTn/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.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Oct 13 19:32:59.989: INFO: Driver "ebs.csi.aws.com" does not support volume type "PreprovisionedPV" - skipping
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
... skipping 40 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.R8VRd6QTn/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.R8VRd6QTn/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.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 30 lines ...
Oct 13 19:31:59.159: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5821-e2e-scxfxt9
STEP: creating a claim
Oct 13 19:31:59.364: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-67jk
STEP: Creating a pod to test subpath
Oct 13 19:31:59.981: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-67jk" in namespace "provisioning-5821" to be "Succeeded or Failed"
Oct 13 19:32:00.187: INFO: Pod "pod-subpath-test-dynamicpv-67jk": Phase="Pending", Reason="", readiness=false. Elapsed: 206.220147ms
Oct 13 19:32:02.394: INFO: Pod "pod-subpath-test-dynamicpv-67jk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.412876543s
Oct 13 19:32:04.601: INFO: Pod "pod-subpath-test-dynamicpv-67jk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.620043601s
Oct 13 19:32:06.807: INFO: Pod "pod-subpath-test-dynamicpv-67jk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.825889167s
Oct 13 19:32:09.012: INFO: Pod "pod-subpath-test-dynamicpv-67jk": Phase="Pending", Reason="", readiness=false. Elapsed: 9.031247064s
Oct 13 19:32:11.217: INFO: Pod "pod-subpath-test-dynamicpv-67jk": Phase="Pending", Reason="", readiness=false. Elapsed: 11.236474698s
... skipping 2 lines ...
Oct 13 19:32:17.836: INFO: Pod "pod-subpath-test-dynamicpv-67jk": Phase="Pending", Reason="", readiness=false. Elapsed: 17.855462028s
Oct 13 19:32:20.042: INFO: Pod "pod-subpath-test-dynamicpv-67jk": Phase="Pending", Reason="", readiness=false. Elapsed: 20.060779579s
Oct 13 19:32:22.248: INFO: Pod "pod-subpath-test-dynamicpv-67jk": Phase="Pending", Reason="", readiness=false. Elapsed: 22.266521172s
Oct 13 19:32:24.453: INFO: Pod "pod-subpath-test-dynamicpv-67jk": Phase="Pending", Reason="", readiness=false. Elapsed: 24.471677872s
Oct 13 19:32:26.658: INFO: Pod "pod-subpath-test-dynamicpv-67jk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.676597664s
STEP: Saw pod success
Oct 13 19:32:26.658: INFO: Pod "pod-subpath-test-dynamicpv-67jk" satisfied condition "Succeeded or Failed"
Oct 13 19:32:26.863: INFO: Trying to get logs from node ip-172-20-53-140.ap-southeast-1.compute.internal pod pod-subpath-test-dynamicpv-67jk container test-container-subpath-dynamicpv-67jk: <nil>
STEP: delete the pod
Oct 13 19:32:27.297: INFO: Waiting for pod pod-subpath-test-dynamicpv-67jk to disappear
Oct 13 19:32:27.501: INFO: Pod pod-subpath-test-dynamicpv-67jk no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-67jk
Oct 13 19:32:27.501: INFO: Deleting pod "pod-subpath-test-dynamicpv-67jk" in namespace "provisioning-5821"
... skipping 198 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.R8VRd6QTn/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.R8VRd6QTn/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.R8VRd6QTn/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.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Distro debian doesn't support ntfs -- skipping

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.R8VRd6QTn/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.R8VRd6QTn/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.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 30 lines ...
Oct 13 19:31:40.712: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8393-e2e-scz5fzw
STEP: creating a claim
Oct 13 19:31:40.923: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-xdp2
STEP: Creating a pod to test subpath
Oct 13 19:31:41.555: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-xdp2" in namespace "provisioning-8393" to be "Succeeded or Failed"
Oct 13 19:31:41.764: INFO: Pod "pod-subpath-test-dynamicpv-xdp2": Phase="Pending", Reason="", readiness=false. Elapsed: 209.48203ms
Oct 13 19:31:43.975: INFO: Pod "pod-subpath-test-dynamicpv-xdp2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.420105864s
Oct 13 19:31:46.185: INFO: Pod "pod-subpath-test-dynamicpv-xdp2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.630198646s
Oct 13 19:31:48.396: INFO: Pod "pod-subpath-test-dynamicpv-xdp2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.841065735s
Oct 13 19:31:50.605: INFO: Pod "pod-subpath-test-dynamicpv-xdp2": Phase="Pending", Reason="", readiness=false. Elapsed: 9.050233771s
Oct 13 19:31:52.815: INFO: Pod "pod-subpath-test-dynamicpv-xdp2": Phase="Pending", Reason="", readiness=false. Elapsed: 11.259720602s
... skipping 8 lines ...
Oct 13 19:32:12.700: INFO: Pod "pod-subpath-test-dynamicpv-xdp2": Phase="Pending", Reason="", readiness=false. Elapsed: 31.14483987s
Oct 13 19:32:14.909: INFO: Pod "pod-subpath-test-dynamicpv-xdp2": Phase="Pending", Reason="", readiness=false. Elapsed: 33.35406787s
Oct 13 19:32:17.118: INFO: Pod "pod-subpath-test-dynamicpv-xdp2": Phase="Pending", Reason="", readiness=false. Elapsed: 35.563241532s
Oct 13 19:32:19.329: INFO: Pod "pod-subpath-test-dynamicpv-xdp2": Phase="Pending", Reason="", readiness=false. Elapsed: 37.774326511s
Oct 13 19:32:21.539: INFO: Pod "pod-subpath-test-dynamicpv-xdp2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 39.983675428s
STEP: Saw pod success
Oct 13 19:32:21.539: INFO: Pod "pod-subpath-test-dynamicpv-xdp2" satisfied condition "Succeeded or Failed"
Oct 13 19:32:21.747: INFO: Trying to get logs from node ip-172-20-53-140.ap-southeast-1.compute.internal pod pod-subpath-test-dynamicpv-xdp2 container test-container-subpath-dynamicpv-xdp2: <nil>
STEP: delete the pod
Oct 13 19:32:23.354: INFO: Waiting for pod pod-subpath-test-dynamicpv-xdp2 to disappear
Oct 13 19:32:23.562: INFO: Pod pod-subpath-test-dynamicpv-xdp2 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-xdp2
Oct 13 19:32:23.562: INFO: Deleting pod "pod-subpath-test-dynamicpv-xdp2" in namespace "provisioning-8393"
STEP: Creating pod pod-subpath-test-dynamicpv-xdp2
STEP: Creating a pod to test subpath
Oct 13 19:32:23.988: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-xdp2" in namespace "provisioning-8393" to be "Succeeded or Failed"
Oct 13 19:32:24.197: INFO: Pod "pod-subpath-test-dynamicpv-xdp2": Phase="Pending", Reason="", readiness=false. Elapsed: 208.893814ms
Oct 13 19:32:26.406: INFO: Pod "pod-subpath-test-dynamicpv-xdp2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.418347301s
Oct 13 19:32:28.616: INFO: Pod "pod-subpath-test-dynamicpv-xdp2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.628256209s
Oct 13 19:32:30.827: INFO: Pod "pod-subpath-test-dynamicpv-xdp2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.838482117s
Oct 13 19:32:33.037: INFO: Pod "pod-subpath-test-dynamicpv-xdp2": Phase="Pending", Reason="", readiness=false. Elapsed: 9.04880875s
Oct 13 19:32:35.247: INFO: Pod "pod-subpath-test-dynamicpv-xdp2": Phase="Pending", Reason="", readiness=false. Elapsed: 11.259305066s
Oct 13 19:32:37.456: INFO: Pod "pod-subpath-test-dynamicpv-xdp2": Phase="Pending", Reason="", readiness=false. Elapsed: 13.468408437s
Oct 13 19:32:39.667: INFO: Pod "pod-subpath-test-dynamicpv-xdp2": Phase="Pending", Reason="", readiness=false. Elapsed: 15.678618249s
Oct 13 19:32:41.877: INFO: Pod "pod-subpath-test-dynamicpv-xdp2": Phase="Pending", Reason="", readiness=false. Elapsed: 17.889184598s
Oct 13 19:32:44.087: INFO: Pod "pod-subpath-test-dynamicpv-xdp2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.099397021s
STEP: Saw pod success
Oct 13 19:32:44.088: INFO: Pod "pod-subpath-test-dynamicpv-xdp2" satisfied condition "Succeeded or Failed"
Oct 13 19:32:44.297: INFO: Trying to get logs from node ip-172-20-53-140.ap-southeast-1.compute.internal pod pod-subpath-test-dynamicpv-xdp2 container test-container-subpath-dynamicpv-xdp2: <nil>
STEP: delete the pod
Oct 13 19:32:44.724: INFO: Waiting for pod pod-subpath-test-dynamicpv-xdp2 to disappear
Oct 13 19:32:44.933: INFO: Pod pod-subpath-test-dynamicpv-xdp2 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-xdp2
Oct 13 19:32:44.933: INFO: Deleting pod "pod-subpath-test-dynamicpv-xdp2" in namespace "provisioning-8393"
... skipping 35 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.R8VRd6QTn/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.R8VRd6QTn/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.R8VRd6QTn/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.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 127 lines ...
Oct 13 19:33:07.560: INFO: Waiting for pod aws-client to disappear
Oct 13 19:33:07.765: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Oct 13 19:33:07.765: INFO: Deleting PersistentVolumeClaim "pvc-5n2j9"
Oct 13 19:33:07.970: INFO: Deleting PersistentVolume "aws-dqjql"
Oct 13 19:33:09.160: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-07de9a06f3391a4fa", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07de9a06f3391a4fa is currently attached to i-013c922fab027b6ad
	status code: 400, request id: ed543894-e093-44e2-80ba-1dd8a9c97a8b
Oct 13 19:33:15.133: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-07de9a06f3391a4fa", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07de9a06f3391a4fa is currently attached to i-013c922fab027b6ad
	status code: 400, request id: 88d4d914-bc67-497a-8733-3508c6cb0281
Oct 13 19:33:21.155: INFO: Successfully deleted PD "aws://ap-southeast-1a/vol-07de9a06f3391a4fa".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumes
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 19:33:21.155: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-4074" for this suite.
... skipping 344 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 19:32:49.964: 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.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Oct 13 19:32:50.993: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 13 19:32:50.993: INFO: Creating resource for dynamic PV
Oct 13 19:32:50.993: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6437sdbbb
STEP: creating a claim
Oct 13 19:32:51.197: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-k4gp
STEP: Checking for subpath error in container status
Oct 13 19:33:12.226: INFO: Deleting pod "pod-subpath-test-dynamicpv-k4gp" in namespace "provisioning-6437"
Oct 13 19:33:12.433: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-k4gp" to be fully deleted
STEP: Deleting pod
Oct 13 19:33:14.843: INFO: Deleting pod "pod-subpath-test-dynamicpv-k4gp" in namespace "provisioning-6437"
STEP: Deleting pvc
Oct 13 19:33:15.454: INFO: Deleting PersistentVolumeClaim "awsm4gkd"
... skipping 13 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.R8VRd6QTn/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.R8VRd6QTn/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath directory is outside the volume [Slow][LinuxOnly]
      /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow]
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Oct 13 19:33:32.099: INFO: Driver "ebs.csi.aws.com" does not support volume type "PreprovisionedPV" - skipping
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow]
... skipping 47 lines ...
Oct 13 19:33:01.003: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-2694-e2e-scxb6d4
STEP: creating a claim
Oct 13 19:33:01.206: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-rn7t
STEP: Creating a pod to test exec-volume-test
Oct 13 19:33:01.814: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-rn7t" in namespace "volume-2694" to be "Succeeded or Failed"
Oct 13 19:33:02.015: INFO: Pod "exec-volume-test-dynamicpv-rn7t": Phase="Pending", Reason="", readiness=false. Elapsed: 201.26735ms
Oct 13 19:33:04.217: INFO: Pod "exec-volume-test-dynamicpv-rn7t": Phase="Pending", Reason="", readiness=false. Elapsed: 2.403180295s
Oct 13 19:33:06.420: INFO: Pod "exec-volume-test-dynamicpv-rn7t": Phase="Pending", Reason="", readiness=false. Elapsed: 4.605937579s
Oct 13 19:33:08.623: INFO: Pod "exec-volume-test-dynamicpv-rn7t": Phase="Pending", Reason="", readiness=false. Elapsed: 6.809350684s
Oct 13 19:33:10.825: INFO: Pod "exec-volume-test-dynamicpv-rn7t": Phase="Pending", Reason="", readiness=false. Elapsed: 9.010682205s
Oct 13 19:33:13.026: INFO: Pod "exec-volume-test-dynamicpv-rn7t": Phase="Pending", Reason="", readiness=false. Elapsed: 11.211865181s
Oct 13 19:33:15.228: INFO: Pod "exec-volume-test-dynamicpv-rn7t": Phase="Pending", Reason="", readiness=false. Elapsed: 13.413773458s
Oct 13 19:33:17.429: INFO: Pod "exec-volume-test-dynamicpv-rn7t": Phase="Succeeded", Reason="", readiness=false. Elapsed: 15.61516561s
STEP: Saw pod success
Oct 13 19:33:17.429: INFO: Pod "exec-volume-test-dynamicpv-rn7t" satisfied condition "Succeeded or Failed"
Oct 13 19:33:17.634: INFO: Trying to get logs from node ip-172-20-37-108.ap-southeast-1.compute.internal pod exec-volume-test-dynamicpv-rn7t container exec-container-dynamicpv-rn7t: <nil>
STEP: delete the pod
Oct 13 19:33:18.045: INFO: Waiting for pod exec-volume-test-dynamicpv-rn7t to disappear
Oct 13 19:33:18.247: INFO: Pod exec-volume-test-dynamicpv-rn7t no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-rn7t
Oct 13 19:33:18.247: INFO: Deleting pod "exec-volume-test-dynamicpv-rn7t" in namespace "volume-2694"
... skipping 51 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.R8VRd6QTn/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.R8VRd6QTn/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.R8VRd6QTn/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.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 74 lines ...
Oct 13 19:31:56.702: INFO: Creating resource for dynamic PV
Oct 13 19:31:56.702: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-1003-e2e-sc79m62
STEP: creating a claim
Oct 13 19:31:56.901: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Oct 13 19:31:57.495: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-ws5z8" in namespace "snapshotting-1003" to be "Succeeded or Failed"
Oct 13 19:31:57.693: INFO: Pod "pvc-snapshottable-tester-ws5z8": Phase="Pending", Reason="", readiness=false. Elapsed: 198.621808ms
Oct 13 19:31:59.890: INFO: Pod "pvc-snapshottable-tester-ws5z8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.395647435s
Oct 13 19:32:02.089: INFO: Pod "pvc-snapshottable-tester-ws5z8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.594647057s
Oct 13 19:32:04.287: INFO: Pod "pvc-snapshottable-tester-ws5z8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.792842039s
Oct 13 19:32:06.486: INFO: Pod "pvc-snapshottable-tester-ws5z8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.991093855s
Oct 13 19:32:08.688: INFO: Pod "pvc-snapshottable-tester-ws5z8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 11.192958028s
STEP: Saw pod success
Oct 13 19:32:08.688: INFO: Pod "pvc-snapshottable-tester-ws5z8" satisfied condition "Succeeded or Failed"
Oct 13 19:32:09.125: INFO: Pod pvc-snapshottable-tester-ws5z8 has the following logs: 
Oct 13 19:32:09.125: INFO: Deleting pod "pvc-snapshottable-tester-ws5z8" in namespace "snapshotting-1003"
Oct 13 19:32:09.327: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-ws5z8" to be fully deleted
Oct 13 19:32:09.526: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comqkb92] to have phase Bound
Oct 13 19:32:09.729: INFO: PersistentVolumeClaim ebs.csi.aws.comqkb92 found and phase=Bound (203.047432ms)
STEP: [init] checking the claim
... skipping 22 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:243
STEP: checking the snapshot
STEP: checking the SnapshotContent
STEP: Modifying source data test
STEP: modifying the data in the source PVC
Oct 13 19:32:38.291: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-2gv6r" in namespace "snapshotting-1003" to be "Succeeded or Failed"
Oct 13 19:32:38.488: INFO: Pod "pvc-snapshottable-data-tester-2gv6r": Phase="Pending", Reason="", readiness=false. Elapsed: 197.041914ms
Oct 13 19:32:40.686: INFO: Pod "pvc-snapshottable-data-tester-2gv6r": Phase="Pending", Reason="", readiness=false. Elapsed: 2.39555327s
Oct 13 19:32:42.886: INFO: Pod "pvc-snapshottable-data-tester-2gv6r": Phase="Pending", Reason="", readiness=false. Elapsed: 4.594926179s
Oct 13 19:32:45.083: INFO: Pod "pvc-snapshottable-data-tester-2gv6r": Phase="Pending", Reason="", readiness=false. Elapsed: 6.792326973s
Oct 13 19:32:47.281: INFO: Pod "pvc-snapshottable-data-tester-2gv6r": Phase="Pending", Reason="", readiness=false. Elapsed: 8.990231783s
Oct 13 19:32:49.480: INFO: Pod "pvc-snapshottable-data-tester-2gv6r": Phase="Succeeded", Reason="", readiness=false. Elapsed: 11.18893385s
STEP: Saw pod success
Oct 13 19:32:49.480: INFO: Pod "pvc-snapshottable-data-tester-2gv6r" satisfied condition "Succeeded or Failed"
Oct 13 19:32:49.883: INFO: Pod pvc-snapshottable-data-tester-2gv6r has the following logs: 
Oct 13 19:32:49.883: INFO: Deleting pod "pvc-snapshottable-data-tester-2gv6r" in namespace "snapshotting-1003"
Oct 13 19:32:50.088: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-2gv6r" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Oct 13 19:33:05.089: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-c3f2775103-c95b4.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-1003 exec restored-pvc-tester-pplt2 --namespace=snapshotting-1003 -- cat /mnt/test/data'
... skipping 243 lines ...
Oct 13 19:27:17.583: INFO: Waiting up to timeout=3m0s for PersistentVolumeClaims [pvc-s6hl5] to have phase Bound
Oct 13 19:27:17.779: INFO: PersistentVolumeClaim pvc-s6hl5 found and phase=Bound (196.371636ms)
Oct 13 19:27:17.779: INFO: Waiting up to 3m0s for PersistentVolume aws-2drdg to have phase Bound
Oct 13 19:27:17.975: INFO: PersistentVolume aws-2drdg found and phase=Bound (196.012719ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-g5f4
STEP: Creating a pod to test exec-volume-test
Oct 13 19:27:18.571: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-g5f4" in namespace "volume-5547" to be "Succeeded or Failed"
Oct 13 19:27:18.767: INFO: Pod "exec-volume-test-preprovisionedpv-g5f4": Phase="Pending", Reason="", readiness=false. Elapsed: 196.138556ms
Oct 13 19:27:20.965: INFO: Pod "exec-volume-test-preprovisionedpv-g5f4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.393849473s
Oct 13 19:27:23.162: INFO: Pod "exec-volume-test-preprovisionedpv-g5f4": Phase="Pending", Reason="", readiness=false. Elapsed: 4.591163795s
Oct 13 19:27:25.360: INFO: Pod "exec-volume-test-preprovisionedpv-g5f4": Phase="Pending", Reason="", readiness=false. Elapsed: 6.788914364s
Oct 13 19:27:27.557: INFO: Pod "exec-volume-test-preprovisionedpv-g5f4": Phase="Pending", Reason="", readiness=false. Elapsed: 8.986203253s
Oct 13 19:27:29.754: INFO: Pod "exec-volume-test-preprovisionedpv-g5f4": Phase="Pending", Reason="", readiness=false. Elapsed: 11.183002692s
... skipping 125 lines ...
Oct 13 19:32:06.688: INFO: Pod "exec-volume-test-preprovisionedpv-g5f4": Phase="Pending", Reason="", readiness=false. Elapsed: 4m48.116765145s
Oct 13 19:32:08.927: INFO: Pod "exec-volume-test-preprovisionedpv-g5f4": Phase="Pending", Reason="", readiness=false. Elapsed: 4m50.356171268s
Oct 13 19:32:11.128: INFO: Pod "exec-volume-test-preprovisionedpv-g5f4": Phase="Pending", Reason="", readiness=false. Elapsed: 4m52.556782011s
Oct 13 19:32:13.325: INFO: Pod "exec-volume-test-preprovisionedpv-g5f4": Phase="Pending", Reason="", readiness=false. Elapsed: 4m54.753764108s
Oct 13 19:32:15.525: INFO: Pod "exec-volume-test-preprovisionedpv-g5f4": Phase="Pending", Reason="", readiness=false. Elapsed: 4m56.954481907s
Oct 13 19:32:17.723: INFO: Pod "exec-volume-test-preprovisionedpv-g5f4": Phase="Pending", Reason="", readiness=false. Elapsed: 4m59.152361472s
Oct 13 19:32:20.120: INFO: Failed to get logs from node "ip-172-20-46-86.ap-southeast-1.compute.internal" pod "exec-volume-test-preprovisionedpv-g5f4" container "exec-container-preprovisionedpv-g5f4": the server rejected our request for an unknown reason (get pods exec-volume-test-preprovisionedpv-g5f4)
STEP: delete the pod
Oct 13 19:32:20.320: INFO: Waiting for pod exec-volume-test-preprovisionedpv-g5f4 to disappear
Oct 13 19:32:20.517: INFO: Pod exec-volume-test-preprovisionedpv-g5f4 still exists
Oct 13 19:32:22.517: INFO: Waiting for pod exec-volume-test-preprovisionedpv-g5f4 to disappear
Oct 13 19:32:22.718: INFO: Pod exec-volume-test-preprovisionedpv-g5f4 still exists
Oct 13 19:32:24.517: INFO: Waiting for pod exec-volume-test-preprovisionedpv-g5f4 to disappear
... skipping 86 lines ...
Oct 13 19:33:50.714: INFO: Pod exec-volume-test-preprovisionedpv-g5f4 still exists
Oct 13 19:33:52.518: INFO: Waiting for pod exec-volume-test-preprovisionedpv-g5f4 to disappear
Oct 13 19:33:52.714: INFO: Pod exec-volume-test-preprovisionedpv-g5f4 no longer exists
STEP: Deleting pv and pvc
Oct 13 19:33:52.715: INFO: Deleting PersistentVolumeClaim "pvc-s6hl5"
Oct 13 19:33:52.913: INFO: Deleting PersistentVolume "aws-2drdg"
Oct 13 19:33:54.072: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-0bbb9f42ac948a061", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0bbb9f42ac948a061 is currently attached to i-0c7ecffbeb1cae944
	status code: 400, request id: 21f79a24-6817-4f64-b83c-4701386dd6af
Oct 13 19:34:00.016: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-0bbb9f42ac948a061", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0bbb9f42ac948a061 is currently attached to i-0c7ecffbeb1cae944
	status code: 400, request id: c6537c98-aee0-492b-bb94-44e7e1ebafe8
Oct 13 19:34:06.098: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-0bbb9f42ac948a061", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0bbb9f42ac948a061 is currently attached to i-0c7ecffbeb1cae944
	status code: 400, request id: b42ff75c-2943-4254-9042-d2ad971f0d7c
Oct 13 19:34:12.091: INFO: Successfully deleted PD "aws://ap-southeast-1a/vol-0bbb9f42ac948a061".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
STEP: Collecting events from namespace "volume-5547".
STEP: Found 9 events.
Oct 13 19:34:12.288: INFO: At 2021-10-13 19:27:17 +0000 UTC - event for pvc-s6hl5: {persistentvolume-controller } ProvisioningFailed: storageclass.storage.k8s.io "volume-5547" not found
Oct 13 19:34:12.288: INFO: At 2021-10-13 19:27:18 +0000 UTC - event for exec-volume-test-preprovisionedpv-g5f4: {default-scheduler } Scheduled: Successfully assigned volume-5547/exec-volume-test-preprovisionedpv-g5f4 to ip-172-20-46-86.ap-southeast-1.compute.internal
Oct 13 19:34:12.288: INFO: At 2021-10-13 19:27:57 +0000 UTC - event for exec-volume-test-preprovisionedpv-g5f4: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "aws-2drdg" : rpc error: code = Internal desc = Could not attach volume "vol-0bbb9f42ac948a061" to node "i-0c7ecffbeb1cae944": attachment of disk "vol-0bbb9f42ac948a061" failed, expected device to be attached but was attaching
Oct 13 19:34:12.288: INFO: At 2021-10-13 19:29:21 +0000 UTC - event for exec-volume-test-preprovisionedpv-g5f4: {kubelet ip-172-20-46-86.ap-southeast-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[vol1], unattached volumes=[kube-api-access-vrzx8 vol1]: timed out waiting for the condition
Oct 13 19:34:12.288: INFO: At 2021-10-13 19:31:35 +0000 UTC - event for exec-volume-test-preprovisionedpv-g5f4: {kubelet ip-172-20-46-86.ap-southeast-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[vol1], unattached volumes=[vol1 kube-api-access-vrzx8]: timed out waiting for the condition
Oct 13 19:34:12.288: INFO: At 2021-10-13 19:32:12 +0000 UTC - event for exec-volume-test-preprovisionedpv-g5f4: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "aws-2drdg" 
Oct 13 19:34:12.288: INFO: At 2021-10-13 19:33:49 +0000 UTC - event for exec-volume-test-preprovisionedpv-g5f4: {kubelet ip-172-20-46-86.ap-southeast-1.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/nginx:1.14-1" already present on machine
Oct 13 19:34:12.288: INFO: At 2021-10-13 19:33:49 +0000 UTC - event for exec-volume-test-preprovisionedpv-g5f4: {kubelet ip-172-20-46-86.ap-southeast-1.compute.internal} Created: Created container exec-container-preprovisionedpv-g5f4
Oct 13 19:34:12.288: INFO: At 2021-10-13 19:33:49 +0000 UTC - event for exec-volume-test-preprovisionedpv-g5f4: {kubelet ip-172-20-46-86.ap-southeast-1.compute.internal} Started: Started container exec-container-preprovisionedpv-g5f4
... skipping 190 lines ...
  /tmp/kops.R8VRd6QTn/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] volumes
    /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should allow exec of files on the volume [It]
      /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:196

      Unexpected error:
          <*errors.errorString | 0xc000582360>: {
              s: "expected pod \"exec-volume-test-preprovisionedpv-g5f4\" success: Gave up after waiting 5m0s for pod \"exec-volume-test-preprovisionedpv-g5f4\" to be \"Succeeded or Failed\"",
          }
          expected pod "exec-volume-test-preprovisionedpv-g5f4" success: Gave up after waiting 5m0s for pod "exec-volume-test-preprovisionedpv-g5f4" to be "Succeeded or Failed"
      occurred

      /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:742
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
... skipping 225 lines ...
Oct 13 19:32:15.368: INFO: Creating resource for dynamic PV
Oct 13 19:32:15.368: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-578-e2e-scjh7vl
STEP: creating a claim
Oct 13 19:32:15.581: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Oct 13 19:32:16.209: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-rw2ql" in namespace "snapshotting-578" to be "Succeeded or Failed"
Oct 13 19:32:16.419: INFO: Pod "pvc-snapshottable-tester-rw2ql": Phase="Pending", Reason="", readiness=false. Elapsed: 209.230298ms
Oct 13 19:32:18.629: INFO: Pod "pvc-snapshottable-tester-rw2ql": Phase="Pending", Reason="", readiness=false. Elapsed: 2.419286461s
Oct 13 19:32:20.838: INFO: Pod "pvc-snapshottable-tester-rw2ql": Phase="Pending", Reason="", readiness=false. Elapsed: 4.62846454s
Oct 13 19:32:23.047: INFO: Pod "pvc-snapshottable-tester-rw2ql": Phase="Pending", Reason="", readiness=false. Elapsed: 6.837480452s
Oct 13 19:32:25.259: INFO: Pod "pvc-snapshottable-tester-rw2ql": Phase="Pending", Reason="", readiness=false. Elapsed: 9.049898711s
Oct 13 19:32:27.469: INFO: Pod "pvc-snapshottable-tester-rw2ql": Phase="Pending", Reason="", readiness=false. Elapsed: 11.259382258s
Oct 13 19:32:29.679: INFO: Pod "pvc-snapshottable-tester-rw2ql": Phase="Succeeded", Reason="", readiness=false. Elapsed: 13.46946795s
STEP: Saw pod success
Oct 13 19:32:29.679: INFO: Pod "pvc-snapshottable-tester-rw2ql" satisfied condition "Succeeded or Failed"
Oct 13 19:32:30.098: INFO: Pod pvc-snapshottable-tester-rw2ql has the following logs: 
Oct 13 19:32:30.099: INFO: Deleting pod "pvc-snapshottable-tester-rw2ql" in namespace "snapshotting-578"
Oct 13 19:32:30.316: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-rw2ql" to be fully deleted
Oct 13 19:32:30.525: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.com5p5kj] to have phase Bound
Oct 13 19:32:30.733: INFO: PersistentVolumeClaim ebs.csi.aws.com5p5kj found and phase=Bound (208.381909ms)
STEP: [init] checking the claim
... skipping 43 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:243
STEP: checking the snapshot
STEP: checking the SnapshotContent
STEP: Modifying source data test
STEP: modifying the data in the source PVC
Oct 13 19:33:08.392: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-lcpgg" in namespace "snapshotting-578" to be "Succeeded or Failed"
Oct 13 19:33:08.610: INFO: Pod "pvc-snapshottable-data-tester-lcpgg": Phase="Pending", Reason="", readiness=false. Elapsed: 217.204311ms
Oct 13 19:33:10.818: INFO: Pod "pvc-snapshottable-data-tester-lcpgg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.426057976s
Oct 13 19:33:13.027: INFO: Pod "pvc-snapshottable-data-tester-lcpgg": Phase="Pending", Reason="", readiness=false. Elapsed: 4.634580089s
Oct 13 19:33:15.235: INFO: Pod "pvc-snapshottable-data-tester-lcpgg": Phase="Pending", Reason="", readiness=false. Elapsed: 6.842796896s
Oct 13 19:33:17.444: INFO: Pod "pvc-snapshottable-data-tester-lcpgg": Phase="Pending", Reason="", readiness=false. Elapsed: 9.051372096s
Oct 13 19:33:19.653: INFO: Pod "pvc-snapshottable-data-tester-lcpgg": Phase="Pending", Reason="", readiness=false. Elapsed: 11.260635736s
Oct 13 19:33:21.863: INFO: Pod "pvc-snapshottable-data-tester-lcpgg": Phase="Pending", Reason="", readiness=false. Elapsed: 13.470928582s
Oct 13 19:33:24.072: INFO: Pod "pvc-snapshottable-data-tester-lcpgg": Phase="Pending", Reason="", readiness=false. Elapsed: 15.679917093s
Oct 13 19:33:26.281: INFO: Pod "pvc-snapshottable-data-tester-lcpgg": Phase="Pending", Reason="", readiness=false. Elapsed: 17.888838697s
Oct 13 19:33:28.503: INFO: Pod "pvc-snapshottable-data-tester-lcpgg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.110842861s
STEP: Saw pod success
Oct 13 19:33:28.503: INFO: Pod "pvc-snapshottable-data-tester-lcpgg" satisfied condition "Succeeded or Failed"
Oct 13 19:33:28.922: INFO: Pod pvc-snapshottable-data-tester-lcpgg has the following logs: 
Oct 13 19:33:28.922: INFO: Deleting pod "pvc-snapshottable-data-tester-lcpgg" in namespace "snapshotting-578"
Oct 13 19:33:29.136: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-lcpgg" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Oct 13 19:33:44.190: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-c3f2775103-c95b4.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-578 exec restored-pvc-tester-lp2pn --namespace=snapshotting-578 -- cat /mnt/test/data'
... skipping 352 lines ...
Oct 13 19:33:19.161: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-51504b64q
STEP: creating a claim
Oct 13 19:33:19.373: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-bhdv
STEP: Creating a pod to test multi_subpath
Oct 13 19:33:20.003: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-bhdv" in namespace "provisioning-5150" to be "Succeeded or Failed"
Oct 13 19:33:20.215: INFO: Pod "pod-subpath-test-dynamicpv-bhdv": Phase="Pending", Reason="", readiness=false. Elapsed: 211.166982ms
Oct 13 19:33:22.424: INFO: Pod "pod-subpath-test-dynamicpv-bhdv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.420434137s
Oct 13 19:33:24.633: INFO: Pod "pod-subpath-test-dynamicpv-bhdv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.62966897s
Oct 13 19:33:26.843: INFO: Pod "pod-subpath-test-dynamicpv-bhdv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.839829503s
Oct 13 19:33:29.053: INFO: Pod "pod-subpath-test-dynamicpv-bhdv": Phase="Pending", Reason="", readiness=false. Elapsed: 9.049190017s
Oct 13 19:33:31.262: INFO: Pod "pod-subpath-test-dynamicpv-bhdv": Phase="Pending", Reason="", readiness=false. Elapsed: 11.258242588s
Oct 13 19:33:33.472: INFO: Pod "pod-subpath-test-dynamicpv-bhdv": Phase="Pending", Reason="", readiness=false. Elapsed: 13.468470913s
Oct 13 19:33:35.682: INFO: Pod "pod-subpath-test-dynamicpv-bhdv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 15.678510984s
STEP: Saw pod success
Oct 13 19:33:35.682: INFO: Pod "pod-subpath-test-dynamicpv-bhdv" satisfied condition "Succeeded or Failed"
Oct 13 19:33:35.893: INFO: Trying to get logs from node ip-172-20-53-140.ap-southeast-1.compute.internal pod pod-subpath-test-dynamicpv-bhdv container test-container-subpath-dynamicpv-bhdv: <nil>
STEP: delete the pod
Oct 13 19:33:36.337: INFO: Waiting for pod pod-subpath-test-dynamicpv-bhdv to disappear
Oct 13 19:33:36.545: INFO: Pod pod-subpath-test-dynamicpv-bhdv no longer exists
STEP: Deleting pod
Oct 13 19:33:36.545: INFO: Deleting pod "pod-subpath-test-dynamicpv-bhdv" in namespace "provisioning-5150"
... skipping 107 lines ...

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 284 lines ...
Oct 13 19:34:35.778: INFO: Waiting for pod aws-client to disappear
Oct 13 19:34:35.982: INFO: Pod aws-client still exists
Oct 13 19:34:37.778: INFO: Waiting for pod aws-client to disappear
Oct 13 19:34:37.982: INFO: Pod aws-client still exists
Oct 13 19:34:39.778: INFO: Waiting for pod aws-client to disappear
Oct 13 19:34:39.982: INFO: Pod aws-client no longer exists
Oct 13 19:34:39.982: FAIL: Failed to create client pod: timed out waiting for the condition

Full Stack Trace
k8s.io/kubernetes/test/e2e/framework/volume.TestVolumeClient(...)
	/tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/framework/volume/fixtures.go:505
k8s.io/kubernetes/test/e2e/storage/testsuites.(*volumesTestSuite).DefineTests.func3()
	/tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:188 +0x4df
github.com/kubernetes-sigs/aws-ebs-csi-driver/tests/e2e-kubernetes.TestEBSCSI(0x407c59)
	/tmp/kops.R8VRd6QTn/tests/e2e-kubernetes/e2e_test.go:82 +0x319
testing.tRunner(0xc000a089c0, 0x28f9180)
	/usr/local/go/src/testing/testing.go:1259 +0x102
created by testing.(*T).Run
	/usr/local/go/src/testing/testing.go:1306 +0x35a
STEP: cleaning the environment after aws
Oct 13 19:34:40.978: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-03dde8fe3dc03daf7", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-03dde8fe3dc03daf7 is currently attached to i-0c7ecffbeb1cae944
	status code: 400, request id: 04d724e0-d2f4-4d72-8b8f-61b19aeeb90b
Oct 13 19:34:47.113: INFO: Successfully deleted PD "aws://ap-southeast-1a/vol-03dde8fe3dc03daf7".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
STEP: Collecting events from namespace "volume-8533".
STEP: Found 10 events.
Oct 13 19:34:47.323: INFO: At 2021-10-13 19:27:12 +0000 UTC - event for aws-injector: {default-scheduler } Scheduled: Successfully assigned volume-8533/aws-injector to ip-172-20-46-86.ap-southeast-1.compute.internal
Oct 13 19:34:47.323: INFO: At 2021-10-13 19:27:30 +0000 UTC - event for aws-injector: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "ebs.csi.aws.com-vol-03dde8fe3dc03daf7" 
Oct 13 19:34:47.323: INFO: At 2021-10-13 19:27:37 +0000 UTC - event for aws-injector: {kubelet ip-172-20-46-86.ap-southeast-1.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" already present on machine
Oct 13 19:34:47.323: INFO: At 2021-10-13 19:27:37 +0000 UTC - event for aws-injector: {kubelet ip-172-20-46-86.ap-southeast-1.compute.internal} Created: Created container aws-injector
Oct 13 19:34:47.323: INFO: At 2021-10-13 19:27:37 +0000 UTC - event for aws-injector: {kubelet ip-172-20-46-86.ap-southeast-1.compute.internal} Started: Started container aws-injector
Oct 13 19:34:47.323: INFO: At 2021-10-13 19:27:50 +0000 UTC - event for aws-injector: {kubelet ip-172-20-46-86.ap-southeast-1.compute.internal} Killing: Stopping container aws-injector
Oct 13 19:34:47.323: INFO: At 2021-10-13 19:28:02 +0000 UTC - event for aws-client: {default-scheduler } Scheduled: Successfully assigned volume-8533/aws-client to ip-172-20-46-86.ap-southeast-1.compute.internal
Oct 13 19:34:47.323: INFO: At 2021-10-13 19:28:21 +0000 UTC - event for aws-client: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "ebs.csi.aws.com-vol-03dde8fe3dc03daf7" : rpc error: code = DeadlineExceeded desc = context deadline exceeded
Oct 13 19:34:47.323: INFO: At 2021-10-13 19:28:22 +0000 UTC - event for aws-client: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "ebs.csi.aws.com-vol-03dde8fe3dc03daf7" : rpc error: code = Internal desc = Could not attach volume "vol-03dde8fe3dc03daf7" to node "i-0c7ecffbeb1cae944": attachment of disk "vol-03dde8fe3dc03daf7" failed, expected device to be attached but was attaching
Oct 13 19:34:47.323: INFO: At 2021-10-13 19:30:05 +0000 UTC - event for aws-client: {kubelet ip-172-20-46-86.ap-southeast-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[aws-volume-0], unattached volumes=[aws-volume-0 kube-api-access-qdmnz]: timed out waiting for the condition
Oct 13 19:34:47.527: INFO: POD  NODE  PHASE  GRACE  CONDITIONS
Oct 13 19:34:47.527: INFO: 
Oct 13 19:34:47.733: INFO: 
Logging node info for node ip-172-20-32-51.ap-southeast-1.compute.internal
Oct 13 19:34:47.937: INFO: Node Info: &Node{ObjectMeta:{ip-172-20-32-51.ap-southeast-1.compute.internal    fc3e8d8b-185a-4be9-98cc-e30f21ab7502 15360 0 2021-10-13 19:22:14 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:t3.medium beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:ap-southeast-1 failure-domain.beta.kubernetes.io/zone:ap-southeast-1a kops.k8s.io/instancegroup:nodes-ap-southeast-1a kubernetes.io/arch:amd64 kubernetes.io/hostname:ip-172-20-32-51.ap-southeast-1.compute.internal kubernetes.io/os:linux kubernetes.io/role:node node-role.kubernetes.io/node: node.kubernetes.io/instance-type:t3.medium topology.ebs.csi.aws.com/zone:ap-southeast-1a topology.kubernetes.io/region:ap-southeast-1 topology.kubernetes.io/zone:ap-southeast-1a] map[csi.volume.kubernetes.io/nodeid:{"ebs.csi.aws.com":"i-08bcea51a1937d594"} node.alpha.kubernetes.io/ttl:0 projectcalico.org/IPv4Address:172.20.32.51/19 projectcalico.org/IPv4IPIPTunnelAddr:100.120.163.0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] []  [{kops-controller Update v1 2021-10-13 19:22:14 +0000 UTC FieldsV1 {"f:metadata":{"f:labels":{"f:kops.k8s.io/instancegroup":{},"f:kubernetes.io/role":{},"f:node-role.kubernetes.io/node":{}}}}} {kubelet Update v1 2021-10-13 19:22:14 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}}}} {kube-controller-manager Update v1 2021-10-13 19:22:17 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"100.96.1.0/24\"":{}}}}} {calico-node Update v1 2021-10-13 19:22:40 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4IPIPTunnelAddr":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}}} {kubelet Update v1 2021-10-13 19:26:44 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:csi.volume.kubernetes.io/nodeid":{}},"f:labels":{"f:topology.ebs.csi.aws.com/zone":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{},"f:volumesInUse":{}}}} {kube-controller-manager Update v1 2021-10-13 19:31:44 +0000 UTC FieldsV1 {"f:status":{"f:volumesAttached":{}}}}]},Spec:NodeSpec{PodCIDR:100.96.1.0/24,DoNotUseExternalID:,ProviderID:aws:///ap-southeast-1a/i-08bcea51a1937d594,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[100.96.1.0/24],},Status:NodeStatus{Capacity:ResourceList{cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{49895047168 0} {<nil>}  BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{4059742208 0} {<nil>}  BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{44905542377 0} {<nil>} 44905542377 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{3954884608 0} {<nil>}  BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2021-10-13 19:22:40 +0000 UTC,LastTransitionTime:2021-10-13 19:22:40 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2021-10-13 19:34:44 +0000 UTC,LastTransitionTime:2021-10-13 19:22:13 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2021-10-13 19:34:44 +0000 UTC,LastTransitionTime:2021-10-13 19:22:13 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2021-10-13 19:34:44 +0000 UTC,LastTransitionTime:2021-10-13 19:22:13 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2021-10-13 19:34:44 +0000 UTC,LastTransitionTime:2021-10-13 19:22:34 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:172.20.32.51,},NodeAddress{Type:ExternalIP,Address:54.255.202.107,},NodeAddress{Type:Hostname,Address:ip-172-20-32-51.ap-southeast-1.compute.internal,},NodeAddress{Type:InternalDNS,Address:ip-172-20-32-51.ap-southeast-1.compute.internal,},NodeAddress{Type:ExternalDNS,Address:ec2-54-255-202-107.ap-southeast-1.compute.amazonaws.com,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:ec2efb43120c2f7e75951b78e689fae1,SystemUUID:ec2efb43-120c-2f7e-7595-1b78e689fae1,BootID:68d77089-ace1-4b40-a795-96187c9a134e,KernelVersion:5.11.0-1019-aws,OSImage:Ubuntu 20.04.3 LTS,ContainerRuntimeVersion:containerd://1.4.11,KubeletVersion:v1.22.1,KubeProxyVersion:v1.22.1,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[k8s.gcr.io/provider-aws/aws-ebs-csi-driver@sha256:5c03401df9e8fa384b66efc8bfd954a0371ad584a9430eca7d4d9338654d7fe0 k8s.gcr.io/provider-aws/aws-ebs-csi-driver:v1.4.0],SizeBytes:116606616,},ContainerImage{Names:[docker.io/calico/node@sha256:1ae8f57edec7c3a84cd48dd94132a1dcfd7c61bfff819c559f9379d4a56fe3b1 docker.io/calico/node:v3.20.2],SizeBytes:57637498,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/agnhost@sha256:8bd76a6a7778e203b61e18e5ee85b1faf52e6a30eb07e445a165ab90fe9633e3 k8s.gcr.io/e2e-test-images/agnhost:2.31],SizeBytes:49692421,},ContainerImage{Names:[docker.io/calico/cni@sha256:3dae26de7388ff3c124b9abd7e8d12863887391f23549c4aebfbfa20cc0700a5 docker.io/calico/cni:v3.20.2],SizeBytes:48389252,},ContainerImage{Names:[k8s.gcr.io/build-image/debian-iptables@sha256:abe8cef9e116f2d5ec1175c386e33841ff3386779138b425af876384b0fd7ccb k8s.gcr.io/build-image/debian-iptables:buster-v1.5.0],SizeBytes:38088315,},ContainerImage{Names:[k8s.gcr.io/kube-proxy@sha256:efcf1d5fb2fc95d28841f534f1385a4884230c7c876fb1b7cf66d2777ad6dc56 k8s.gcr.io/kube-proxy:v1.22.1],SizeBytes:35941601,},ContainerImage{Names:[k8s.gcr.io/cpa/cluster-proportional-autoscaler@sha256:fd636b33485c7826fb20ef0688a83ee0910317dbb6c0c6f3ad14661c1db25def k8s.gcr.io/cpa/cluster-proportional-autoscaler:1.8.4],SizeBytes:15209393,},ContainerImage{Names:[k8s.gcr.io/coredns/coredns@sha256:43a9f52f5dce39bf1816afe6141724cc2d08811e466dd46e6628c925e2419bdc k8s.gcr.io/coredns/coredns:v1.8.5],SizeBytes:13581340,},ContainerImage{Names:[k8s.gcr.io/sig-storage/snapshot-validation-webhook@sha256:cc9dfe74bb10a5ceed6aac4db24e1177cad6d5f4b0cdae53630c9212b75c0dde k8s.gcr.io/sig-storage/snapshot-validation-webhook:v4.2.1],SizeBytes:10479598,},ContainerImage{Names:[docker.io/calico/pod2daemon-flexvol@sha256:4514cc1b2f7536fe1d514fad8a2c46103382243bb9db5ea2d0063fcd2001e8f7 docker.io/calico/pod2daemon-flexvol:v3.20.2],SizeBytes:9359081,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-node-driver-registrar@sha256:a61d309da54641db41fb8f35718f744e9f730d4d0384f8c4b186ddc9f06cbd5f k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.1.0],SizeBytes:9068367,},ContainerImage{Names:[k8s.gcr.io/sig-storage/livenessprobe@sha256:48da0e4ed7238ad461ea05f68c25921783c37b315f21a5c5a2780157a6460994 k8s.gcr.io/sig-storage/livenessprobe:v2.2.0],SizeBytes:8279778,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/nginx@sha256:503b7abb89e57383eba61cc8a9cb0b495ea575c516108f7d972a6ff6e1ab3c9b k8s.gcr.io/e2e-test-images/nginx:1.14-1],SizeBytes:6979365,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/busybox@sha256:39e1e963e5310e9c313bad51523be012ede7b35bb9316517d19089a010356592 k8s.gcr.io/e2e-test-images/busybox:1.29-1],SizeBytes:732746,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:927d98197ec1141a368550822d18fa1c60bdae27b78b0c004f705f548c07814f k8s.gcr.io/pause:3.2],SizeBytes:299513,},},VolumesInUse:[kubernetes.io/csi/ebs.csi.aws.com^vol-055c8bc4459d4595a kubernetes.io/csi/ebs.csi.aws.com^vol-083674ec8ae5bf2b9 kubernetes.io/csi/ebs.csi.aws.com^vol-0ead89c1b1f31cc06],VolumesAttached:[]AttachedVolume{AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-0ead89c1b1f31cc06,DevicePath:,},AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-055c8bc4459d4595a,DevicePath:,},AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-083674ec8ae5bf2b9,DevicePath:,},},Config:nil,},}
... skipping 190 lines ...
  /tmp/kops.R8VRd6QTn/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (xfs)][Slow] volumes
    /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should store data [It]
      /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:159

      Oct 13 19:34:39.982: Failed to create client pod: timed out waiting for the condition

      /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/framework/volume/fixtures.go:505
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 19:34:55.023: 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.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Oct 13 19:34:56.251: INFO: found topology map[topology.kubernetes.io/zone:ap-southeast-1a]
Oct 13 19:34:56.251: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 13 19:34:56.251: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.R8VRd6QTn/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.R8VRd6QTn/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (delayed binding)] topology
    /tmp/kops.R8VRd6QTn/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.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 63 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 19:33:23.008: 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.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Oct 13 19:33:24.039: INFO: Creating resource for dynamic PV
Oct 13 19:33:24.039: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2607-e2e-scvprf7
STEP: creating a claim
Oct 13 19:33:24.244: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-bxfq
STEP: Checking for subpath error in container status
Oct 13 19:34:37.271: INFO: Deleting pod "pod-subpath-test-dynamicpv-bxfq" in namespace "provisioning-2607"
Oct 13 19:34:37.481: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-bxfq" to be fully deleted
STEP: Deleting pod
Oct 13 19:34:39.891: INFO: Deleting pod "pod-subpath-test-dynamicpv-bxfq" in namespace "provisioning-2607"
STEP: Deleting pvc
Oct 13 19:34:40.505: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comkc2c6"
... skipping 11 lines ...

• [SLOW TEST:94.164 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath file is outside the volume [Slow][LinuxOnly]
    /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 30 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 19:34:30.321: 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.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Oct 13 19:34:31.371: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 13 19:34:31.371: INFO: Creating resource for dynamic PV
Oct 13 19:34:31.371: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-856726mfk
STEP: creating a claim
Oct 13 19:34:31.580: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-wsqk
STEP: Checking for subpath error in container status
Oct 13 19:34:44.629: INFO: Deleting pod "pod-subpath-test-dynamicpv-wsqk" in namespace "provisioning-8567"
Oct 13 19:34:44.840: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-wsqk" to be fully deleted
STEP: Deleting pod
Oct 13 19:34:47.258: INFO: Deleting pod "pod-subpath-test-dynamicpv-wsqk" in namespace "provisioning-8567"
STEP: Deleting pvc
Oct 13 19:34:47.887: INFO: Deleting PersistentVolumeClaim "aws6cn9l"
... skipping 12 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.R8VRd6QTn/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.R8VRd6QTn/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.R8VRd6QTn/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.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 19:34:48.521: 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.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Oct 13 19:34:49.555: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 13 19:34:49.555: INFO: Creating resource for dynamic PV
Oct 13 19:34:49.555: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-770777whs
STEP: creating a claim
Oct 13 19:34:49.757: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-5wfq
STEP: Checking for subpath error in container status
Oct 13 19:35:04.769: INFO: Deleting pod "pod-subpath-test-dynamicpv-5wfq" in namespace "provisioning-7707"
Oct 13 19:35:04.971: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-5wfq" to be fully deleted
STEP: Deleting pod
Oct 13 19:35:07.374: INFO: Deleting pod "pod-subpath-test-dynamicpv-5wfq" in namespace "provisioning-7707"
STEP: Deleting pvc
Oct 13 19:35:07.980: INFO: Deleting PersistentVolumeClaim "awssncfn"
... skipping 12 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.R8VRd6QTn/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.R8VRd6QTn/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath file is outside the volume [Slow][LinuxOnly]
      /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
... skipping 74 lines ...
Oct 13 19:34:47.251: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-8426bt2pg
STEP: creating a claim
Oct 13 19:34:47.450: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-6tcj
STEP: Creating a pod to test exec-volume-test
Oct 13 19:34:48.050: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-6tcj" in namespace "volume-8426" to be "Succeeded or Failed"
Oct 13 19:34:48.250: INFO: Pod "exec-volume-test-dynamicpv-6tcj": Phase="Pending", Reason="", readiness=false. Elapsed: 199.377431ms
Oct 13 19:34:50.450: INFO: Pod "exec-volume-test-dynamicpv-6tcj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.400118314s
Oct 13 19:34:52.655: INFO: Pod "exec-volume-test-dynamicpv-6tcj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.604810752s
Oct 13 19:34:54.854: INFO: Pod "exec-volume-test-dynamicpv-6tcj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.804230906s
Oct 13 19:34:57.053: INFO: Pod "exec-volume-test-dynamicpv-6tcj": Phase="Pending", Reason="", readiness=false. Elapsed: 9.003128831s
Oct 13 19:34:59.253: INFO: Pod "exec-volume-test-dynamicpv-6tcj": Phase="Pending", Reason="", readiness=false. Elapsed: 11.203134601s
Oct 13 19:35:01.454: INFO: Pod "exec-volume-test-dynamicpv-6tcj": Phase="Pending", Reason="", readiness=false. Elapsed: 13.403830927s
Oct 13 19:35:03.656: INFO: Pod "exec-volume-test-dynamicpv-6tcj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 15.605723932s
STEP: Saw pod success
Oct 13 19:35:03.656: INFO: Pod "exec-volume-test-dynamicpv-6tcj" satisfied condition "Succeeded or Failed"
Oct 13 19:35:03.855: INFO: Trying to get logs from node ip-172-20-46-86.ap-southeast-1.compute.internal pod exec-volume-test-dynamicpv-6tcj container exec-container-dynamicpv-6tcj: <nil>
STEP: delete the pod
Oct 13 19:35:04.261: INFO: Waiting for pod exec-volume-test-dynamicpv-6tcj to disappear
Oct 13 19:35:04.463: INFO: Pod exec-volume-test-dynamicpv-6tcj no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-6tcj
Oct 13 19:35:04.463: INFO: Deleting pod "exec-volume-test-dynamicpv-6tcj" in namespace "volume-8426"
... skipping 375 lines ...
STEP: Deleting pod hostexec-ip-172-20-46-86.ap-southeast-1.compute.internal-d9fk4 in namespace volumemode-6931
Oct 13 19:35:14.941: INFO: Deleting pod "pod-85af8ec8-4286-44cb-aed3-40f1af190f39" in namespace "volumemode-6931"
Oct 13 19:35:15.153: INFO: Wait up to 5m0s for pod "pod-85af8ec8-4286-44cb-aed3-40f1af190f39" to be fully deleted
STEP: Deleting pv and pvc
Oct 13 19:35:17.571: INFO: Deleting PersistentVolumeClaim "pvc-9954g"
Oct 13 19:35:17.783: INFO: Deleting PersistentVolume "aws-vjk65"
Oct 13 19:35:18.338: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-0f082556886362a59", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f082556886362a59 is currently attached to i-0c7ecffbeb1cae944
	status code: 400, request id: 283b6336-4543-4d86-bec0-f69f0bbe9a65
Oct 13 19:35:24.386: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-0f082556886362a59", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f082556886362a59 is currently attached to i-0c7ecffbeb1cae944
	status code: 400, request id: 02817d69-5a35-4b1c-bb84-680dd17b2902
Oct 13 19:35:30.398: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-0f082556886362a59", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f082556886362a59 is currently attached to i-0c7ecffbeb1cae944
	status code: 400, request id: ebf05cb4-0501-4614-b9f7-54f6f0ba98ba
Oct 13 19:35:36.554: INFO: Successfully deleted PD "aws://ap-southeast-1a/vol-0f082556886362a59".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 19:35:36.554: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-6931" for this suite.
... skipping 98 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 13 19:34:49.601: 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.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Oct 13 19:34:50.629: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 13 19:34:50.629: INFO: Creating resource for dynamic PV
Oct 13 19:34:50.630: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-3025pjsh9
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Oct 13 19:34:56.074: INFO: Deleting pod "pod-1712c7c2-ba4b-49eb-a02c-da8414cd320d" in namespace "volumemode-3025"
Oct 13 19:34:56.284: INFO: Wait up to 5m0s for pod "pod-1712c7c2-ba4b-49eb-a02c-da8414cd320d" to be fully deleted
STEP: Deleting pvc
Oct 13 19:34:59.114: INFO: Deleting PersistentVolumeClaim "aws72c7r"
Oct 13 19:34:59.324: INFO: Waiting up to 5m0s for PersistentVolume pvc-2dbb989a-38fb-4c46-ab44-5b2af18f7839 to get deleted
Oct 13 19:34:59.532: INFO: PersistentVolume pvc-2dbb989a-38fb-4c46-ab44-5b2af18f7839 found and phase=Released (208.059975ms)
... skipping 16 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.R8VRd6QTn/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.R8VRd6QTn/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
    /tmp/kops.R8VRd6QTn/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.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 161 lines ...
Oct 13 19:32:33.101: INFO: Creating resource for dynamic PV
Oct 13 19:32:33.101: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-8505-e2e-sc4jpmc
STEP: creating a claim
Oct 13 19:32:33.307: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Oct 13 19:32:33.926: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-gt5rt" in namespace "snapshotting-8505" to be "Succeeded or Failed"
Oct 13 19:32:34.131: INFO: Pod "pvc-snapshottable-tester-gt5rt": Phase="Pending", Reason="", readiness=false. Elapsed: 204.097716ms
Oct 13 19:32:36.338: INFO: Pod "pvc-snapshottable-tester-gt5rt": Phase="Pending", Reason="", readiness=false. Elapsed: 2.411005616s
Oct 13 19:32:38.543: INFO: Pod "pvc-snapshottable-tester-gt5rt": Phase="Pending", Reason="", readiness=false. Elapsed: 4.616734689s
Oct 13 19:32:40.749: INFO: Pod "pvc-snapshottable-tester-gt5rt": Phase="Pending", Reason="", readiness=false. Elapsed: 6.822556998s
Oct 13 19:32:42.954: INFO: Pod "pvc-snapshottable-tester-gt5rt": Phase="Pending", Reason="", readiness=false. Elapsed: 9.027299469s
Oct 13 19:32:45.160: INFO: Pod "pvc-snapshottable-tester-gt5rt": Phase="Pending", Reason="", readiness=false. Elapsed: 11.233355723s
Oct 13 19:32:47.366: INFO: Pod "pvc-snapshottable-tester-gt5rt": Phase="Pending", Reason="", readiness=false. Elapsed: 13.439531833s
Oct 13 19:32:49.573: INFO: Pod "pvc-snapshottable-tester-gt5rt": Phase="Pending", Reason="", readiness=false. Elapsed: 15.645959261s
Oct 13 19:32:51.778: INFO: Pod "pvc-snapshottable-tester-gt5rt": Phase="Succeeded", Reason="", readiness=false. Elapsed: 17.851049975s
STEP: Saw pod success
Oct 13 19:32:51.778: INFO: Pod "pvc-snapshottable-tester-gt5rt" satisfied condition "Succeeded or Failed"
Oct 13 19:32:52.199: INFO: Pod pvc-snapshottable-tester-gt5rt has the following logs: 
Oct 13 19:32:52.199: INFO: Deleting pod "pvc-snapshottable-tester-gt5rt" in namespace "snapshotting-8505"
Oct 13 19:32:52.420: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-gt5rt" to be fully deleted
Oct 13 19:32:52.624: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comxjvwl] to have phase Bound
Oct 13 19:32:52.829: INFO: PersistentVolumeClaim ebs.csi.aws.comxjvwl found and phase=Bound (204.442938ms)
STEP: [init] checking the claim
... skipping 54 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:243
STEP: checking the snapshot
STEP: checking the SnapshotContent
STEP: Modifying source data test
STEP: modifying the data in the source PVC
Oct 13 19:33:54.562: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-mjw7b" in namespace "snapshotting-8505" to be "Succeeded or Failed"
Oct 13 19:33:54.766: INFO: Pod "pvc-snapshottable-data-tester-mjw7b": Phase="Pending", Reason="", readiness=false. Elapsed: 204.560404ms
Oct 13 19:33:56.971: INFO: Pod "pvc-snapshottable-data-tester-mjw7b": Phase="Pending", Reason="", readiness=false. Elapsed: 2.409361472s
Oct 13 19:33:59.176: INFO: Pod "pvc-snapshottable-data-tester-mjw7b": Phase="Pending", Reason="", readiness=false. Elapsed: 4.614174787s
Oct 13 19:34:01.381: INFO: Pod "pvc-snapshottable-data-tester-mjw7b": Phase="Pending", Reason="", readiness=false. Elapsed: 6.81893774s
Oct 13 19:34:03.586: INFO: Pod "pvc-snapshottable-data-tester-mjw7b": Phase="Pending", Reason="", readiness=false. Elapsed: 9.023907747s
Oct 13 19:34:05.792: INFO: Pod "pvc-snapshottable-data-tester-mjw7b": Phase="Pending", Reason="", readiness=false. Elapsed: 11.230123603s
Oct 13 19:34:07.997: INFO: Pod "pvc-snapshottable-data-tester-mjw7b": Phase="Pending", Reason="", readiness=false. Elapsed: 13.435163978s
Oct 13 19:34:10.203: INFO: Pod "pvc-snapshottable-data-tester-mjw7b": Phase="Pending", Reason="", readiness=false. Elapsed: 15.641463611s
Oct 13 19:34:12.409: INFO: Pod "pvc-snapshottable-data-tester-mjw7b": Phase="Succeeded", Reason="", readiness=false. Elapsed: 17.847787025s
STEP: Saw pod success
Oct 13 19:34:12.410: INFO: Pod "pvc-snapshottable-data-tester-mjw7b" satisfied condition "Succeeded or Failed"
Oct 13 19:34:12.822: INFO: Pod pvc-snapshottable-data-tester-mjw7b has the following logs: 
Oct 13 19:34:12.822: INFO: Deleting pod "pvc-snapshottable-data-tester-mjw7b" in namespace "snapshotting-8505"
Oct 13 19:34:13.031: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-mjw7b" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Oct 13 19:34:36.056: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-c3f2775103-c95b4.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-8505 exec restored-pvc-tester-jcs2v --namespace=snapshotting-8505 -- cat /mnt/test/data'
... skipping 28 lines ...
Oct 13 19:35:01.828: INFO: volumesnapshotcontents pre-provisioned-snapcontent-28b397b8-8dd8-4da2-99d9-dff329eb60ee has been found and is not deleted
Oct 13 19:35:03.033: INFO: volumesnapshotcontents pre-provisioned-snapcontent-28b397b8-8dd8-4da2-99d9-dff329eb60ee has been found and is not deleted
Oct 13 19:35:04.239: INFO: volumesnapshotcontents pre-provisioned-snapcontent-28b397b8-8dd8-4da2-99d9-dff329eb60ee has been found and is not deleted
Oct 13 19:35:05.446: INFO: volumesnapshotcontents pre-provisioned-snapcontent-28b397b8-8dd8-4da2-99d9-dff329eb60ee has been found and is not deleted
Oct 13 19:35:06.651: INFO: volumesnapshotcontents pre-provisioned-snapcontent-28b397b8-8dd8-4da2-99d9-dff329eb60ee has been found and is not deleted
Oct 13 19:35:07.857: INFO: volumesnapshotcontents pre-provisioned-snapcontent-28b397b8-8dd8-4da2-99d9-dff329eb60ee has been found and is not deleted
Oct 13 19:35:08.858: INFO: WaitUntil failed after reaching the timeout 30s
[AfterEach] volume snapshot controller
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:221
Oct 13 19:35:09.084: INFO: Pod restored-pvc-tester-jcs2v has the following logs: 
Oct 13 19:35:09.084: INFO: Deleting pod "restored-pvc-tester-jcs2v" in namespace "snapshotting-8505"
Oct 13 19:35:09.292: INFO: Wait up to 5m0s for pod "restored-pvc-tester-jcs2v" to be fully deleted
Oct 13 19:35:41.705: INFO: deleting claim "snapshotting-8505"/"pvc-qmvzh"
... skipping 271 lines ...
STEP: Deleting pod aws-client in namespace volume-5287
Oct 13 19:35:43.816: INFO: Waiting for pod aws-client to disappear
Oct 13 19:35:44.021: INFO: Pod aws-client still exists
Oct 13 19:35:46.021: INFO: Waiting for pod aws-client to disappear
Oct 13 19:35:46.225: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Oct 13 19:35:46.582: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-05fe90d8a4c7a76e4", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05fe90d8a4c7a76e4 is currently attached to i-0c7ecffbeb1cae944
	status code: 400, request id: 16ee1608-4bd6-4c73-b5cc-df1a7cd38284
Oct 13 19:35:52.561: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-05fe90d8a4c7a76e4", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05fe90d8a4c7a76e4 is currently attached to i-0c7ecffbeb1cae944
	status code: 400, request id: c97db98b-0e7a-4e8a-be68-bec1f9c5ba0e
Oct 13 19:35:58.555: INFO: Successfully deleted PD "aws://ap-southeast-1a/vol-05fe90d8a4c7a76e4".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 13 19:35:58.555: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-5287" for this suite.
... skipping 379 lines ...
Oct 13 19:33:49.325: INFO: Creating resource for dynamic PV
Oct 13 19:33:49.325: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2597vxd5r
STEP: creating a claim
Oct 13 19:33:49.529: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-2597
Oct 13 19:33:50.134: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-2597" in namespace "provisioning-2597" to be "Succeeded or Failed"
Oct 13 19:33:50.335: INFO: Pod "volume-prep-provisioning-2597": Phase="Pending", Reason="", readiness=false. Elapsed: 200.51471ms
Oct 13 19:33:52.537: INFO: Pod "volume-prep-provisioning-2597": Phase="Pending", Reason="", readiness=false. Elapsed: 2.40278869s
Oct 13 19:33:54.739: INFO: Pod "volume-prep-provisioning-2597": Phase="Pending", Reason="", readiness=false. Elapsed: 4.604593325s
Oct 13 19:33:56.941: INFO: Pod "volume-prep-provisioning-2597": Phase="Pending", Reason="", readiness=false. Elapsed: 6.806443738s
Oct 13 19:33:59.142: INFO: Pod "volume-prep-provisioning-2597": Phase="Pending", Reason="", readiness=false. Elapsed: 9.007761446s
Oct 13 19:34:01.343: INFO: Pod "volume-prep-provisioning-2597": Phase="Pending", Reason="", readiness=false. Elapsed: 11.209185715s
... skipping 55 lines ...
Oct 13 19:36:04.692: INFO: Pod "volume-prep-provisioning-2597": Phase="Pending", Reason="", readiness=false. Elapsed: 2m14.557576259s
Oct 13 19:36:06.894: INFO: Pod "volume-prep-provisioning-2597": Phase="Pending", Reason="", readiness=false. Elapsed: 2m16.759680741s
Oct 13 19:36:09.095: INFO: Pod "volume-prep-provisioning-2597": Phase="Pending", Reason="", readiness=false. Elapsed: 2m18.961142966s
Oct 13 19:36:11.298: INFO: Pod "volume-prep-provisioning-2597": Phase="Pending", Reason="", readiness=false. Elapsed: 2m21.163588192s
Oct 13 19:36:13.499: INFO: Pod "volume-prep-provisioning-2597": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2m23.364321801s
STEP: Saw pod success
Oct 13 19:36:13.499: INFO: Pod "volume-prep-provisioning-2597" satisfied condition "Succeeded or Failed"
Oct 13 19:36:13.499: INFO: Deleting pod "volume-prep-provisioning-2597" in namespace "provisioning-2597"
Oct 13 19:36:13.707: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-2597" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-vhpl
STEP: Checking for subpath error in container status
Oct 13 19:36:32.514: INFO: Deleting pod "pod-subpath-test-dynamicpv-vhpl" in namespace "provisioning-2597"
Oct 13 19:36:32.721: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-vhpl" to be fully deleted
STEP: Deleting pod
Oct 13 19:36:32.922: INFO: Deleting pod "pod-subpath-test-dynamicpv-vhpl" in namespace "provisioning-2597"
STEP: Deleting pvc
Oct 13 19:36:33.525: INFO: Deleting PersistentVolumeClaim "aws59lvl"
... skipping 201 lines ...
Oct 13 19:37:14.118: INFO: At 2021-10-13 19:26:49 +0000 UTC - event for pod-1c097799-580e-4340-9d5e-8f3fb0e9e4c4: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-55ed8b9e-0a8f-46aa-a798-21598e8f2947" 
Oct 13 19:37:14.118: INFO: At 2021-10-13 19:26:51 +0000 UTC - event for pod-1c097799-580e-4340-9d5e-8f3fb0e9e4c4: {kubelet ip-172-20-37-108.ap-southeast-1.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" already present on machine
Oct 13 19:37:14.118: INFO: At 2021-10-13 19:26:51 +0000 UTC - event for pod-1c097799-580e-4340-9d5e-8f3fb0e9e4c4: {kubelet ip-172-20-37-108.ap-southeast-1.compute.internal} Created: Created container write-pod
Oct 13 19:37:14.119: INFO: At 2021-10-13 19:26:52 +0000 UTC - event for pod-1c097799-580e-4340-9d5e-8f3fb0e9e4c4: {kubelet ip-172-20-37-108.ap-southeast-1.compute.internal} Started: Started container write-pod
Oct 13 19:37:14.119: INFO: At 2021-10-13 19:27:07 +0000 UTC - event for pod-1c097799-580e-4340-9d5e-8f3fb0e9e4c4: {kubelet ip-172-20-37-108.ap-southeast-1.compute.internal} Killing: Stopping container write-pod
Oct 13 19:37:14.119: INFO: At 2021-10-13 19:27:09 +0000 UTC - event for pod-b2808829-4c61-4765-bd35-3e275084d136: {default-scheduler } Scheduled: Successfully assigned fsgroupchangepolicy-1498/pod-b2808829-4c61-4765-bd35-3e275084d136 to ip-172-20-46-86.ap-southeast-1.compute.internal
Oct 13 19:37:14.119: INFO: At 2021-10-13 19:27:09 +0000 UTC - event for pod-b2808829-4c61-4765-bd35-3e275084d136: {attachdetach-controller } FailedAttachVolume: Multi-Attach error for volume "pvc-55ed8b9e-0a8f-46aa-a798-21598e8f2947" Volume is already exclusively attached to one node and can't be attached to another
Oct 13 19:37:14.119: INFO: At 2021-10-13 19:28:02 +0000 UTC - event for pod-b2808829-4c61-4765-bd35-3e275084d136: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-55ed8b9e-0a8f-46aa-a798-21598e8f2947" : rpc error: code = Internal desc = Could not attach volume "vol-0137442f0a559d6a7" to node "i-0c7ecffbeb1cae944": attachment of disk "vol-0137442f0a559d6a7" failed, expected device to be attached but was attaching
Oct 13 19:37:14.119: INFO: At 2021-10-13 19:29:12 +0000 UTC - event for pod-b2808829-4c61-4765-bd35-3e275084d136: {kubelet ip-172-20-46-86.ap-southeast-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume1], unattached volumes=[kube-api-access-5vn2w volume1]: timed out waiting for the condition
Oct 13 19:37:14.119: INFO: At 2021-10-13 19:31:30 +0000 UTC - event for pod-b2808829-4c61-4765-bd35-3e275084d136: {kubelet ip-172-20-46-86.ap-southeast-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume1], unattached volumes=[volume1 kube-api-access-5vn2w]: timed out waiting for the condition
Oct 13 19:37:14.119: INFO: At 2021-10-13 19:33:57 +0000 UTC - event for pod-b2808829-4c61-4765-bd35-3e275084d136: {kubelet ip-172-20-46-86.ap-southeast-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume1], unattached volumes=[kube-api-access-5vn2w volume1]: error processing PVC fsgroupchangepolicy-1498/awsfxhbt: PVC is being deleted
Oct 13 19:37:14.119: INFO: At 2021-10-13 19:34:12 +0000 UTC - event for pod-b2808829-4c61-4765-bd35-3e275084d136: {kubelet ip-172-20-46-86.ap-southeast-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[volume1], unattached volumes=[volume1 kube-api-access-5vn2w]: error processing PVC fsgroupchangepolicy-1498/awsfxhbt: PVC is being deleted
Oct 13 19:37:14.330: INFO: POD                                       NODE                                             PHASE    GRACE  CONDITIONS
Oct 13 19:37:14.330: INFO: pod-b2808829-4c61-4765-bd35-3e275084d136  ip-172-20-46-86.ap-southeast-1.compute.internal  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2021-10-13 19:27:09 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2021-10-13 19:27:09 +0000 UTC ContainersNotReady containers with unready status: [write-pod]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2021-10-13 19:27:09 +0000 UTC ContainersNotReady containers with unready status: [write-pod]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2021-10-13 19:27:09 +0000 UTC  }]
Oct 13 19:37:14.330: INFO: 
Oct 13 19:37:14.543: INFO: 
Logging node info for node ip-172-20-32-51.ap-southeast-1.compute.internal
Oct 13 19:37:14.755: INFO: Node Info: &Node{ObjectMeta:{ip-172-20-32-51.ap-southeast-1.compute.internal    fc3e8d8b-185a-4be9-98cc-e30f21ab7502 17416 0 2021-10-13 19:22:14 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:t3.medium beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:ap-southeast-1 failure-domain.beta.kubernetes.io/zone:ap-southeast-1a kops.k8s.io/instancegroup:nodes-ap-southeast-1a kubernetes.io/arch:amd64 kubernetes.io/hostname:ip-172-20-32-51.ap-southeast-1.compute.internal kubernetes.io/os:linux kubernetes.io/role:node node-role.kubernetes.io/node: node.kubernetes.io/instance-type:t3.medium topology.ebs.csi.aws.com/zone:ap-southeast-1a topology.kubernetes.io/region:ap-southeast-1 topology.kubernetes.io/zone:ap-southeast-1a] map[csi.volume.kubernetes.io/nodeid:{"ebs.csi.aws.com":"i-08bcea51a1937d594"} node.alpha.kubernetes.io/ttl:0 projectcalico.org/IPv4Address:172.20.32.51/19 projectcalico.org/IPv4IPIPTunnelAddr:100.120.163.0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] []  [{kops-controller Update v1 2021-10-13 19:22:14 +0000 UTC FieldsV1 {"f:metadata":{"f:labels":{"f:kops.k8s.io/instancegroup":{},"f:kubernetes.io/role":{},"f:node-role.kubernetes.io/node":{}}}}} {kubelet Update v1 2021-10-13 19:22:14 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}}}} {kube-controller-manager Update v1 2021-10-13 19:22:17 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"100.96.1.0/24\"":{}}}}} {calico-node Update v1 2021-10-13 19:22:40 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4IPIPTunnelAddr":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}}} {kubelet Update v1 2021-10-13 19:36:44 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:csi.volume.kubernetes.io/nodeid":{}},"f:labels":{"f:topology.ebs.csi.aws.com/zone":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}}}]},Spec:NodeSpec{PodCIDR:100.96.1.0/24,DoNotUseExternalID:,ProviderID:aws:///ap-southeast-1a/i-08bcea51a1937d594,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[100.96.1.0/24],},Status:NodeStatus{Capacity:ResourceList{cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{49895047168 0} {<nil>}  BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{4059742208 0} {<nil>}  BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{44905542377 0} {<nil>} 44905542377 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{3954884608 0} {<nil>}  BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2021-10-13 19:22:40 +0000 UTC,LastTransitionTime:2021-10-13 19:22:40 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2021-10-13 19:36:44 +0000 UTC,LastTransitionTime:2021-10-13 19:22:13 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2021-10-13 19:36:44 +0000 UTC,LastTransitionTime:2021-10-13 19:22:13 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2021-10-13 19:36:44 +0000 UTC,LastTransitionTime:2021-10-13 19:22:13 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2021-10-13 19:36:44 +0000 UTC,LastTransitionTime:2021-10-13 19:22:34 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:172.20.32.51,},NodeAddress{Type:ExternalIP,Address:54.255.202.107,},NodeAddress{Type:Hostname,Address:ip-172-20-32-51.ap-southeast-1.compute.internal,},NodeAddress{Type:InternalDNS,Address:ip-172-20-32-51.ap-southeast-1.compute.internal,},NodeAddress{Type:ExternalDNS,Address:ec2-54-255-202-107.ap-southeast-1.compute.amazonaws.com,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:ec2efb43120c2f7e75951b78e689fae1,SystemUUID:ec2efb43-120c-2f7e-7595-1b78e689fae1,BootID:68d77089-ace1-4b40-a795-96187c9a134e,KernelVersion:5.11.0-1019-aws,OSImage:Ubuntu 20.04.3 LTS,ContainerRuntimeVersion:containerd://1.4.11,KubeletVersion:v1.22.1,KubeProxyVersion:v1.22.1,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[k8s.gcr.io/provider-aws/aws-ebs-csi-driver@sha256:5c03401df9e8fa384b66efc8bfd954a0371ad584a9430eca7d4d9338654d7fe0 k8s.gcr.io/provider-aws/aws-ebs-csi-driver:v1.4.0],SizeBytes:116606616,},ContainerImage{Names:[docker.io/calico/node@sha256:1ae8f57edec7c3a84cd48dd94132a1dcfd7c61bfff819c559f9379d4a56fe3b1 docker.io/calico/node:v3.20.2],SizeBytes:57637498,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/agnhost@sha256:8bd76a6a7778e203b61e18e5ee85b1faf52e6a30eb07e445a165ab90fe9633e3 k8s.gcr.io/e2e-test-images/agnhost:2.31],SizeBytes:49692421,},ContainerImage{Names:[docker.io/calico/cni@sha256:3dae26de7388ff3c124b9abd7e8d12863887391f23549c4aebfbfa20cc0700a5 docker.io/calico/cni:v3.20.2],SizeBytes:48389252,},ContainerImage{Names:[k8s.gcr.io/build-image/debian-iptables@sha256:abe8cef9e116f2d5ec1175c386e33841ff3386779138b425af876384b0fd7ccb k8s.gcr.io/build-image/debian-iptables:buster-v1.5.0],SizeBytes:38088315,},ContainerImage{Names:[k8s.gcr.io/kube-proxy@sha256:efcf1d5fb2fc95d28841f534f1385a4884230c7c876fb1b7cf66d2777ad6dc56 k8s.gcr.io/kube-proxy:v1.22.1],SizeBytes:35941601,},ContainerImage{Names:[k8s.gcr.io/cpa/cluster-proportional-autoscaler@sha256:fd636b33485c7826fb20ef0688a83ee0910317dbb6c0c6f3ad14661c1db25def k8s.gcr.io/cpa/cluster-proportional-autoscaler:1.8.4],SizeBytes:15209393,},ContainerImage{Names:[k8s.gcr.io/coredns/coredns@sha256:43a9f52f5dce39bf1816afe6141724cc2d08811e466dd46e6628c925e2419bdc k8s.gcr.io/coredns/coredns:v1.8.5],SizeBytes:13581340,},ContainerImage{Names:[k8s.gcr.io/sig-storage/snapshot-validation-webhook@sha256:cc9dfe74bb10a5ceed6aac4db24e1177cad6d5f4b0cdae53630c9212b75c0dde k8s.gcr.io/sig-storage/snapshot-validation-webhook:v4.2.1],SizeBytes:10479598,},ContainerImage{Names:[docker.io/calico/pod2daemon-flexvol@sha256:4514cc1b2f7536fe1d514fad8a2c46103382243bb9db5ea2d0063fcd2001e8f7 docker.io/calico/pod2daemon-flexvol:v3.20.2],SizeBytes:9359081,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-node-driver-registrar@sha256:a61d309da54641db41fb8f35718f744e9f730d4d0384f8c4b186ddc9f06cbd5f k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.1.0],SizeBytes:9068367,},ContainerImage{Names:[k8s.gcr.io/sig-storage/livenessprobe@sha256:48da0e4ed7238ad461ea05f68c25921783c37b315f21a5c5a2780157a6460994 k8s.gcr.io/sig-storage/livenessprobe:v2.2.0],SizeBytes:8279778,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/nginx@sha256:503b7abb89e57383eba61cc8a9cb0b495ea575c516108f7d972a6ff6e1ab3c9b k8s.gcr.io/e2e-test-images/nginx:1.14-1],SizeBytes:6979365,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/busybox@sha256:39e1e963e5310e9c313bad51523be012ede7b35bb9316517d19089a010356592 k8s.gcr.io/e2e-test-images/busybox:1.29-1],SizeBytes:732746,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:927d98197ec1141a368550822d18fa1c60bdae27b78b0c004f705f548c07814f k8s.gcr.io/pause:3.2],SizeBytes:299513,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},}
... skipping 158 lines ...
  /tmp/kops.R8VRd6QTn/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
    /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      (Always)[LinuxOnly], pod created with an initial fsgroup, volume contents ownership changed in first pod, new pod with different fsgroup applied to the volume contents [It]
      /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/fsgroupchangepolicy.go:208

      Unexpected error:
          <*errors.errorString | 0xc000b42ca0>: {
              s: "pod \"pod-b2808829-4c61-4765-bd35-3e275084d136\" is not Running: timed out waiting for the condition",
          }
          pod "pod-b2808829-4c61-4765-bd35-3e275084d136" is not Running: timed out waiting for the condition
      occurred

... skipping 139 lines ...
    /tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumelimits.go:123
------------------------------


Summarizing 3 Failures:

[Fail] [ebs-csi-migration] EBS CSI Migration [Driver: aws] [Testpattern: Pre-provisioned PV (default fs)] volumes [It] should allow exec of files on the volume 
/tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:742

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

[Fail] [ebs-csi-migration] EBS CSI Migration [Driver: aws] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy [It] (Always)[LinuxOnly], pod created with an initial fsgroup, volume contents ownership changed in first pod, new pod with different fsgroup applied to the volume contents 
/tmp/kops.R8VRd6QTn/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/fsgroupchangepolicy.go:250

Ran 144 of 485 Specs in 1316.203 seconds
FAIL! -- 141 Passed | 3 Failed | 0 Pending | 341 Skipped


Ginkgo ran 1 suite in 23m8.129558493s
Test Suite Failed

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