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

No Test Failures!


Error lines from build-log.txt

... skipping 583 lines ...
I1014 09:27:52.958793   12448 app.go:90] ID for this run: "48588b15-2cd0-11ec-acf4-0afd3ca65cf2"
I1014 09:27:52.979874   12448 up.go:43] Cleaning up any leaked resources from previous cluster
I1014 09:27:52.979953   12448 dumplogs.go:40] /home/prow/go/src/k8s.io/kops/.bazelbuild/dist/linux/amd64/kops toolbox dump --name e2e-b6f7c24027-45100.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ubuntu
I1014 09:27:52.997295   12460 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1014 09:27:52.997365   12460 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I1014 09:27:52.997369   12460 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Error: Cluster.kops.k8s.io "e2e-b6f7c24027-45100.test-cncf-aws.k8s.io" not found
W1014 09:27:53.436447   12448 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I1014 09:27:53.436530   12448 down.go:48] /home/prow/go/src/k8s.io/kops/.bazelbuild/dist/linux/amd64/kops delete cluster --name e2e-b6f7c24027-45100.test-cncf-aws.k8s.io --yes
I1014 09:27:53.453919   12470 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1014 09:27:53.454111   12470 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I1014 09:27:53.454139   12470 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-b6f7c24027-45100.test-cncf-aws.k8s.io" not found
I1014 09:27:53.895035   12448 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/14 09:27:53 failed to get external ip from metadata service: http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip returned 404
I1014 09:27:53.902471   12448 http.go:37] curl https://ip.jsb.workers.dev
I1014 09:27:54.000868   12448 up.go:144] /home/prow/go/src/k8s.io/kops/.bazelbuild/dist/linux/amd64/kops create cluster --name e2e-b6f7c24027-45100.test-cncf-aws.k8s.io --cloud aws --kubernetes-version 1.22.1 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --networking calico --override=cluster.spec.cloudConfig.awsEBSCSIDriver.enabled=true --override=cluster.spec.snapshotController.enabled=true --override=cluster.spec.certManager.enabled=true --admin-access 34.68.176.126/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-southeast-1a --master-size c5.large
I1014 09:27:54.016978   12480 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1014 09:27:54.017048   12480 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I1014 09:27:54.017053   12480 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1014 09:27:54.037191   12480 create_cluster.go:838] Using SSH public key: /etc/aws-ssh/aws-ssh-public
... skipping 32 lines ...
I1014 09:28:15.089550   12448 up.go:181] /home/prow/go/src/k8s.io/kops/.bazelbuild/dist/linux/amd64/kops validate cluster --name e2e-b6f7c24027-45100.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I1014 09:28:15.106070   12498 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1014 09:28:15.106144   12498 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I1014 09:28:15.106148   12498 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-b6f7c24027-45100.test-cncf-aws.k8s.io

W1014 09:28:16.795938   12498 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-b6f7c24027-45100.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-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
W1014 09:28:26.832516   12498 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
W1014 09:28:36.862108   12498 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
W1014 09:28:46.896702   12498 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
W1014 09:28:56.932739   12498 validate_cluster.go:232] (will retry): cluster not yet healthy
W1014 09:29:06.961475   12498 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-b6f7c24027-45100.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-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
W1014 09:29:16.992630   12498 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
W1014 09:29:27.037129   12498 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
W1014 09:29:37.068582   12498 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
W1014 09:29:47.097985   12498 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
W1014 09:29:57.141480   12498 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
W1014 09:30:07.184744   12498 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
W1014 09:30:17.252148   12498 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
W1014 09:30:27.317302   12498 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
W1014 09:30:37.355093   12498 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
W1014 09:30:47.388874   12498 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
W1014 09:30:57.431047   12498 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
W1014 09:31:07.474023   12498 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
W1014 09:31:17.518858   12498 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
W1014 09:31:27.550928   12498 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
W1014 09:31:37.585226   12498 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
W1014 09:31:47.614434   12498 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
W1014 09:31:57.641961   12498 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
W1014 09:32:07.672714   12498 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
W1014 09:32:17.719147   12498 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
W1014 09:32:27.763029   12498 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 13 lines ...
Pod	kube-system/cert-manager-webhook-756bb49f7d-vt2gd	system-cluster-critical pod "cert-manager-webhook-756bb49f7d-vt2gd" is not ready (cert-manager)
Pod	kube-system/coredns-6c8944dbdc-68ppn			system-cluster-critical pod "coredns-6c8944dbdc-68ppn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-hhdqs		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-hhdqs" is pending
Pod	kube-system/ebs-csi-controller-54dc46fc7b-9dv8w		system-cluster-critical pod "ebs-csi-controller-54dc46fc7b-9dv8w" is pending
Pod	kube-system/ebs-csi-node-gp6gv				system-node-critical pod "ebs-csi-node-gp6gv" is pending

Validation Failed
W1014 09:32:42.317183   12498 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 23 lines ...
Pod	kube-system/ebs-csi-node-5pfcc				system-node-critical pod "ebs-csi-node-5pfcc" is pending
Pod	kube-system/ebs-csi-node-6xdfw				system-node-critical pod "ebs-csi-node-6xdfw" is pending
Pod	kube-system/ebs-csi-node-gp6gv				system-node-critical pod "ebs-csi-node-gp6gv" is pending
Pod	kube-system/ebs-csi-node-l5v26				system-node-critical pod "ebs-csi-node-l5v26" is pending
Pod	kube-system/ebs-csi-node-tcj6d				system-node-critical pod "ebs-csi-node-tcj6d" is pending

Validation Failed
W1014 09:32:55.672389   12498 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-5pfcc				system-node-critical pod "ebs-csi-node-5pfcc" is pending
Pod	kube-system/ebs-csi-node-6xdfw				system-node-critical pod "ebs-csi-node-6xdfw" is pending
Pod	kube-system/ebs-csi-node-gp6gv				system-node-critical pod "ebs-csi-node-gp6gv" is pending
Pod	kube-system/ebs-csi-node-l5v26				system-node-critical pod "ebs-csi-node-l5v26" is pending
Pod	kube-system/ebs-csi-node-tcj6d				system-node-critical pod "ebs-csi-node-tcj6d" is pending

Validation Failed
W1014 09:33:08.863579   12498 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 15 lines ...
Pod	kube-system/coredns-autoscaler-84d4cfd89c-hhdqs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-hhdqs" is pending
Pod	kube-system/ebs-csi-node-5pfcc			system-node-critical pod "ebs-csi-node-5pfcc" is pending
Pod	kube-system/ebs-csi-node-6xdfw			system-node-critical pod "ebs-csi-node-6xdfw" is pending
Pod	kube-system/ebs-csi-node-l5v26			system-node-critical pod "ebs-csi-node-l5v26" is pending
Pod	kube-system/ebs-csi-node-tcj6d			system-node-critical pod "ebs-csi-node-tcj6d" is pending

Validation Failed
W1014 09:33:22.309866   12498 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 8 lines ...
VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-proxy-ip-172-20-33-219.ap-southeast-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-33-219.ap-southeast-1.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-37-167.ap-southeast-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-37-167.ap-southeast-1.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-47-16.ap-southeast-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-47-16.ap-southeast-1.compute.internal" is pending

Validation Failed
W1014 09:33:35.478501   12498 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 196 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.h4kFCENj0/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.h4kFCENj0/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.h4kFCENj0/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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.h4kFCENj0/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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  /tmp/kops.h4kFCENj0/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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

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

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

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

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

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

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

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

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.h4kFCENj0/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.h4kFCENj0/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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 223 lines ...
Oct 14 09:37:00.966: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Oct 14 09:37:02.098: INFO: Successfully created a new PD: "aws://ap-southeast-1a/vol-0808c232f209ec826".
Oct 14 09:37:02.098: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-jql8
STEP: Creating a pod to test exec-volume-test
Oct 14 09:37:02.304: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-jql8" in namespace "volume-1330" to be "Succeeded or Failed"
Oct 14 09:37:02.510: INFO: Pod "exec-volume-test-inlinevolume-jql8": Phase="Pending", Reason="", readiness=false. Elapsed: 205.993845ms
Oct 14 09:37:04.706: INFO: Pod "exec-volume-test-inlinevolume-jql8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.402647894s
Oct 14 09:37:06.907: INFO: Pod "exec-volume-test-inlinevolume-jql8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.603814714s
Oct 14 09:37:09.105: INFO: Pod "exec-volume-test-inlinevolume-jql8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.80174053s
Oct 14 09:37:11.303: INFO: Pod "exec-volume-test-inlinevolume-jql8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.999620762s
Oct 14 09:37:13.501: INFO: Pod "exec-volume-test-inlinevolume-jql8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 11.196913623s
STEP: Saw pod success
Oct 14 09:37:13.501: INFO: Pod "exec-volume-test-inlinevolume-jql8" satisfied condition "Succeeded or Failed"
Oct 14 09:37:13.697: INFO: Trying to get logs from node ip-172-20-47-16.ap-southeast-1.compute.internal pod exec-volume-test-inlinevolume-jql8 container exec-container-inlinevolume-jql8: <nil>
STEP: delete the pod
Oct 14 09:37:14.100: INFO: Waiting for pod exec-volume-test-inlinevolume-jql8 to disappear
Oct 14 09:37:14.296: INFO: Pod exec-volume-test-inlinevolume-jql8 no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-jql8
Oct 14 09:37:14.296: INFO: Deleting pod "exec-volume-test-inlinevolume-jql8" in namespace "volume-1330"
Oct 14 09:37:14.812: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-0808c232f209ec826", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0808c232f209ec826 is currently attached to i-0023c706c9d49ee11
	status code: 400, request id: 45f41920-4856-483a-9f75-6af968d3ffbd
Oct 14 09:37:20.754: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-0808c232f209ec826", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0808c232f209ec826 is currently attached to i-0023c706c9d49ee11
	status code: 400, request id: 0702ce4e-0a47-46fc-bf52-126c79bf5516
Oct 14 09:37:26.740: INFO: Successfully deleted PD "aws://ap-southeast-1a/vol-0808c232f209ec826".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 14 09:37:26.740: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-1330" for this suite.
... skipping 45 lines ...
Oct 14 09:37:02.060: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Oct 14 09:37:03.235: INFO: Successfully created a new PD: "aws://ap-southeast-1a/vol-0046a990e87b1c79c".
Oct 14 09:37:03.235: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-dc5f
STEP: Creating a pod to test exec-volume-test
Oct 14 09:37:03.443: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-dc5f" in namespace "volume-3885" to be "Succeeded or Failed"
Oct 14 09:37:03.654: INFO: Pod "exec-volume-test-inlinevolume-dc5f": Phase="Pending", Reason="", readiness=false. Elapsed: 211.00027ms
Oct 14 09:37:05.860: INFO: Pod "exec-volume-test-inlinevolume-dc5f": Phase="Pending", Reason="", readiness=false. Elapsed: 2.416436312s
Oct 14 09:37:08.067: INFO: Pod "exec-volume-test-inlinevolume-dc5f": Phase="Pending", Reason="", readiness=false. Elapsed: 4.623512705s
Oct 14 09:37:10.273: INFO: Pod "exec-volume-test-inlinevolume-dc5f": Phase="Pending", Reason="", readiness=false. Elapsed: 6.829530596s
Oct 14 09:37:12.481: INFO: Pod "exec-volume-test-inlinevolume-dc5f": Phase="Succeeded", Reason="", readiness=false. Elapsed: 9.037771043s
STEP: Saw pod success
Oct 14 09:37:12.481: INFO: Pod "exec-volume-test-inlinevolume-dc5f" satisfied condition "Succeeded or Failed"
Oct 14 09:37:12.687: INFO: Trying to get logs from node ip-172-20-47-16.ap-southeast-1.compute.internal pod exec-volume-test-inlinevolume-dc5f container exec-container-inlinevolume-dc5f: <nil>
STEP: delete the pod
Oct 14 09:37:13.128: INFO: Waiting for pod exec-volume-test-inlinevolume-dc5f to disappear
Oct 14 09:37:13.333: INFO: Pod exec-volume-test-inlinevolume-dc5f no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-dc5f
Oct 14 09:37:13.333: INFO: Deleting pod "exec-volume-test-inlinevolume-dc5f" in namespace "volume-3885"
Oct 14 09:37:13.893: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-0046a990e87b1c79c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0046a990e87b1c79c is currently attached to i-0023c706c9d49ee11
	status code: 400, request id: c39c6a68-bfd4-4932-b66b-5a9ce4c565ed
Oct 14 09:37:19.837: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-0046a990e87b1c79c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0046a990e87b1c79c is currently attached to i-0023c706c9d49ee11
	status code: 400, request id: ac88c156-9aa3-4da6-ad74-0d21b4d7f743
Oct 14 09:37:25.792: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-0046a990e87b1c79c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0046a990e87b1c79c is currently attached to i-0023c706c9d49ee11
	status code: 400, request id: 447a4acd-5cae-4020-9c9a-1002de8053ec
Oct 14 09:37:31.787: INFO: Successfully deleted PD "aws://ap-southeast-1a/vol-0046a990e87b1c79c".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 14 09:37:31.787: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-3885" for this suite.
... skipping 43 lines ...
Oct 14 09:37:01.062: INFO: Creating resource for dynamic PV
Oct 14 09:37:01.062: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-4852-e2e-sc6jvv8
STEP: creating a claim
STEP: Expanding non-expandable pvc
Oct 14 09:37:01.686: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Oct 14 09:37:02.106: INFO: Error updating pvc ebs.csi.aws.com6hht7: PersistentVolumeClaim "ebs.csi.aws.com6hht7" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4852-e2e-sc6jvv8",
  	... // 3 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Oct 14 09:37:32.938: INFO: Error updating pvc ebs.csi.aws.com6hht7: PersistentVolumeClaim "ebs.csi.aws.com6hht7" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 66 lines ...
Oct 14 09:37:02.834: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-5523-e2e-sc47j4z
STEP: creating a claim
Oct 14 09:37:03.046: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Oct 14 09:37:03.467: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Oct 14 09:37:03.886: INFO: Error updating pvc ebs.csi.aws.com6ztrs: PersistentVolumeClaim "ebs.csi.aws.com6ztrs" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5523-e2e-sc47j4z",
  	... // 3 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Oct 14 09:37:34.730: INFO: Error updating pvc ebs.csi.aws.com6ztrs: PersistentVolumeClaim "ebs.csi.aws.com6ztrs" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 73 lines ...
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 14 09:37:38.433: 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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Oct 14 09:37:39.686: INFO: found topology map[topology.ebs.csi.aws.com/zone:ap-southeast-1a]
Oct 14 09:37:39.686: 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.878 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.h4kFCENj0/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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

    Not enough topologies in cluster -- skipping

    /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 11 lines ...
Oct 14 09:37:03.556: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6862-e2e-scdwbbh
STEP: creating a claim
Oct 14 09:37:03.765: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-7xdn
STEP: Creating a pod to test subpath
Oct 14 09:37:04.389: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-7xdn" in namespace "provisioning-6862" to be "Succeeded or Failed"
Oct 14 09:37:04.595: INFO: Pod "pod-subpath-test-dynamicpv-7xdn": Phase="Pending", Reason="", readiness=false. Elapsed: 206.37643ms
Oct 14 09:37:06.809: INFO: Pod "pod-subpath-test-dynamicpv-7xdn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.420579915s
Oct 14 09:37:09.019: INFO: Pod "pod-subpath-test-dynamicpv-7xdn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.629901798s
Oct 14 09:37:11.226: INFO: Pod "pod-subpath-test-dynamicpv-7xdn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.837253849s
Oct 14 09:37:13.435: INFO: Pod "pod-subpath-test-dynamicpv-7xdn": Phase="Pending", Reason="", readiness=false. Elapsed: 9.046582284s
Oct 14 09:37:15.642: INFO: Pod "pod-subpath-test-dynamicpv-7xdn": Phase="Pending", Reason="", readiness=false. Elapsed: 11.253406561s
Oct 14 09:37:17.849: INFO: Pod "pod-subpath-test-dynamicpv-7xdn": Phase="Pending", Reason="", readiness=false. Elapsed: 13.460197709s
Oct 14 09:37:20.056: INFO: Pod "pod-subpath-test-dynamicpv-7xdn": Phase="Pending", Reason="", readiness=false. Elapsed: 15.667525591s
Oct 14 09:37:22.264: INFO: Pod "pod-subpath-test-dynamicpv-7xdn": Phase="Pending", Reason="", readiness=false. Elapsed: 17.874934364s
Oct 14 09:37:24.471: INFO: Pod "pod-subpath-test-dynamicpv-7xdn": Phase="Pending", Reason="", readiness=false. Elapsed: 20.082436087s
Oct 14 09:37:26.688: INFO: Pod "pod-subpath-test-dynamicpv-7xdn": Phase="Pending", Reason="", readiness=false. Elapsed: 22.299792497s
Oct 14 09:37:28.895: INFO: Pod "pod-subpath-test-dynamicpv-7xdn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.506673539s
STEP: Saw pod success
Oct 14 09:37:28.895: INFO: Pod "pod-subpath-test-dynamicpv-7xdn" satisfied condition "Succeeded or Failed"
Oct 14 09:37:29.102: INFO: Trying to get logs from node ip-172-20-47-16.ap-southeast-1.compute.internal pod pod-subpath-test-dynamicpv-7xdn container test-container-volume-dynamicpv-7xdn: <nil>
STEP: delete the pod
Oct 14 09:37:29.550: INFO: Waiting for pod pod-subpath-test-dynamicpv-7xdn to disappear
Oct 14 09:37:29.756: INFO: Pod pod-subpath-test-dynamicpv-7xdn no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-7xdn
Oct 14 09:37:29.756: INFO: Deleting pod "pod-subpath-test-dynamicpv-7xdn" in namespace "provisioning-6862"
... skipping 192 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 14 09:37:03.921: 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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Oct 14 09:37:04.953: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 14 09:37:04.953: INFO: Creating resource for dynamic PV
Oct 14 09:37:04.953: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3104b49z7
STEP: creating a claim
Oct 14 09:37:05.160: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-42vv
STEP: Checking for subpath error in container status
Oct 14 09:37:26.201: INFO: Deleting pod "pod-subpath-test-dynamicpv-42vv" in namespace "provisioning-3104"
Oct 14 09:37:26.429: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-42vv" to be fully deleted
STEP: Deleting pod
Oct 14 09:37:28.854: INFO: Deleting pod "pod-subpath-test-dynamicpv-42vv" in namespace "provisioning-3104"
STEP: Deleting pvc
Oct 14 09:37:29.475: INFO: Deleting PersistentVolumeClaim "aws2nbdx"
... skipping 14 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.h4kFCENj0/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.h4kFCENj0/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.h4kFCENj0/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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Oct 14 09:37:51.347: INFO: Distro debian doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
... skipping 4 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.h4kFCENj0/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.h4kFCENj0/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.h4kFCENj0/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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 91 lines ...
Oct 14 09:37:01.382: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-835pxjjh
STEP: creating a claim
Oct 14 09:37:01.580: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-l9m5
STEP: Creating a pod to test subpath
Oct 14 09:37:02.211: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-l9m5" in namespace "provisioning-835" to be "Succeeded or Failed"
Oct 14 09:37:02.429: INFO: Pod "pod-subpath-test-dynamicpv-l9m5": Phase="Pending", Reason="", readiness=false. Elapsed: 218.452299ms
Oct 14 09:37:04.627: INFO: Pod "pod-subpath-test-dynamicpv-l9m5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.416109783s
Oct 14 09:37:06.829: INFO: Pod "pod-subpath-test-dynamicpv-l9m5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.61808007s
Oct 14 09:37:09.027: INFO: Pod "pod-subpath-test-dynamicpv-l9m5": Phase="Pending", Reason="", readiness=false. Elapsed: 6.816235882s
Oct 14 09:37:11.225: INFO: Pod "pod-subpath-test-dynamicpv-l9m5": Phase="Pending", Reason="", readiness=false. Elapsed: 9.013958079s
Oct 14 09:37:13.423: INFO: Pod "pod-subpath-test-dynamicpv-l9m5": Phase="Pending", Reason="", readiness=false. Elapsed: 11.212308159s
... skipping 2 lines ...
Oct 14 09:37:20.019: INFO: Pod "pod-subpath-test-dynamicpv-l9m5": Phase="Pending", Reason="", readiness=false. Elapsed: 17.808002801s
Oct 14 09:37:22.218: INFO: Pod "pod-subpath-test-dynamicpv-l9m5": Phase="Pending", Reason="", readiness=false. Elapsed: 20.007469534s
Oct 14 09:37:24.417: INFO: Pod "pod-subpath-test-dynamicpv-l9m5": Phase="Pending", Reason="", readiness=false. Elapsed: 22.206005559s
Oct 14 09:37:26.616: INFO: Pod "pod-subpath-test-dynamicpv-l9m5": Phase="Pending", Reason="", readiness=false. Elapsed: 24.405369073s
Oct 14 09:37:28.814: INFO: Pod "pod-subpath-test-dynamicpv-l9m5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.603357217s
STEP: Saw pod success
Oct 14 09:37:28.814: INFO: Pod "pod-subpath-test-dynamicpv-l9m5" satisfied condition "Succeeded or Failed"
Oct 14 09:37:29.011: INFO: Trying to get logs from node ip-172-20-37-167.ap-southeast-1.compute.internal pod pod-subpath-test-dynamicpv-l9m5 container test-container-subpath-dynamicpv-l9m5: <nil>
STEP: delete the pod
Oct 14 09:37:29.794: INFO: Waiting for pod pod-subpath-test-dynamicpv-l9m5 to disappear
Oct 14 09:37:29.991: INFO: Pod pod-subpath-test-dynamicpv-l9m5 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-l9m5
Oct 14 09:37:29.991: INFO: Deleting pod "pod-subpath-test-dynamicpv-l9m5" in namespace "provisioning-835"
... skipping 65 lines ...
Oct 14 09:37:01.059: INFO: Creating resource for dynamic PV
Oct 14 09:37:01.059: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3408-e2e-sct2ws6
STEP: creating a claim
Oct 14 09:37:01.266: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-3408
Oct 14 09:37:01.884: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-3408" in namespace "provisioning-3408" to be "Succeeded or Failed"
Oct 14 09:37:02.089: INFO: Pod "volume-prep-provisioning-3408": Phase="Pending", Reason="", readiness=false. Elapsed: 204.179226ms
Oct 14 09:37:04.295: INFO: Pod "volume-prep-provisioning-3408": Phase="Pending", Reason="", readiness=false. Elapsed: 2.41099042s
Oct 14 09:37:06.508: INFO: Pod "volume-prep-provisioning-3408": Phase="Pending", Reason="", readiness=false. Elapsed: 4.623475343s
Oct 14 09:37:08.713: INFO: Pod "volume-prep-provisioning-3408": Phase="Pending", Reason="", readiness=false. Elapsed: 6.828864156s
Oct 14 09:37:10.919: INFO: Pod "volume-prep-provisioning-3408": Phase="Pending", Reason="", readiness=false. Elapsed: 9.034571215s
Oct 14 09:37:13.126: INFO: Pod "volume-prep-provisioning-3408": Phase="Pending", Reason="", readiness=false. Elapsed: 11.241822031s
Oct 14 09:37:15.331: INFO: Pod "volume-prep-provisioning-3408": Phase="Pending", Reason="", readiness=false. Elapsed: 13.446364507s
Oct 14 09:37:17.537: INFO: Pod "volume-prep-provisioning-3408": Phase="Succeeded", Reason="", readiness=false. Elapsed: 15.652911164s
STEP: Saw pod success
Oct 14 09:37:17.537: INFO: Pod "volume-prep-provisioning-3408" satisfied condition "Succeeded or Failed"
Oct 14 09:37:17.537: INFO: Deleting pod "volume-prep-provisioning-3408" in namespace "provisioning-3408"
Oct 14 09:37:17.748: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-3408" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-vfv8
STEP: Checking for subpath error in container status
Oct 14 09:37:26.587: INFO: Deleting pod "pod-subpath-test-dynamicpv-vfv8" in namespace "provisioning-3408"
Oct 14 09:37:26.797: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-vfv8" to be fully deleted
STEP: Deleting pod
Oct 14 09:37:27.004: INFO: Deleting pod "pod-subpath-test-dynamicpv-vfv8" in namespace "provisioning-3408"
STEP: Deleting pvc
Oct 14 09:37:27.620: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comvr4mh"
... skipping 124 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.h4kFCENj0/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.h4kFCENj0/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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 34 lines ...
Oct 14 09:38:06.367: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 567 lines ...
STEP: Deleting pod aws-client in namespace volume-195
Oct 14 09:38:08.259: INFO: Waiting for pod aws-client to disappear
Oct 14 09:38:08.463: INFO: Pod aws-client still exists
Oct 14 09:38:10.464: INFO: Waiting for pod aws-client to disappear
Oct 14 09:38:10.668: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Oct 14 09:38:11.604: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-072b3a157258f3b38", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-072b3a157258f3b38 is currently attached to i-0023c706c9d49ee11
	status code: 400, request id: 8c6c0a5f-e78c-4fc2-b413-f7b7b60ecc1c
Oct 14 09:38:17.560: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-072b3a157258f3b38", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-072b3a157258f3b38 is currently attached to i-0023c706c9d49ee11
	status code: 400, request id: e5272d99-1f6d-4256-baf2-49432f0e81bb
Oct 14 09:38:23.509: INFO: Successfully deleted PD "aws://ap-southeast-1a/vol-072b3a157258f3b38".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 14 09:38:23.509: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-195" for this suite.
... skipping 444 lines ...
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 14 09:38:38.271: 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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Oct 14 09:38:39.502: INFO: found topology map[topology.kubernetes.io/zone:ap-southeast-1a]
Oct 14 09:38:39.502: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 14 09:38:39.502: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.h4kFCENj0/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.h4kFCENj0/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (immediate binding)] topology
    /tmp/kops.h4kFCENj0/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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 140 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 14 09:37:54.458: 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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Oct 14 09:37:55.506: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 14 09:37:55.506: INFO: Creating resource for dynamic PV
Oct 14 09:37:55.506: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6547qrwb6
STEP: creating a claim
Oct 14 09:37:55.713: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-lksq
STEP: Checking for subpath error in container status
Oct 14 09:38:12.764: INFO: Deleting pod "pod-subpath-test-dynamicpv-lksq" in namespace "provisioning-6547"
Oct 14 09:38:12.993: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-lksq" to be fully deleted
STEP: Deleting pod
Oct 14 09:38:15.406: INFO: Deleting pod "pod-subpath-test-dynamicpv-lksq" in namespace "provisioning-6547"
STEP: Deleting pvc
Oct 14 09:38:16.024: INFO: Deleting PersistentVolumeClaim "aws4fhx4"
... skipping 15 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.h4kFCENj0/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.h4kFCENj0/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath file is outside the volume [Slow][LinuxOnly]
      /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Oct 14 09:38:43.127: INFO: Driver ebs.csi.aws.com doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning
... skipping 103 lines ...
Oct 14 09:37:41.343: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-8727-e2e-sclwtz8
STEP: creating a claim
Oct 14 09:37:41.550: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-qt8r
STEP: Creating a pod to test exec-volume-test
Oct 14 09:37:42.172: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-qt8r" in namespace "volume-8727" to be "Succeeded or Failed"
Oct 14 09:37:42.378: INFO: Pod "exec-volume-test-dynamicpv-qt8r": Phase="Pending", Reason="", readiness=false. Elapsed: 205.85537ms
Oct 14 09:37:44.584: INFO: Pod "exec-volume-test-dynamicpv-qt8r": Phase="Pending", Reason="", readiness=false. Elapsed: 2.412018426s
Oct 14 09:37:46.794: INFO: Pod "exec-volume-test-dynamicpv-qt8r": Phase="Pending", Reason="", readiness=false. Elapsed: 4.622013979s
Oct 14 09:37:49.001: INFO: Pod "exec-volume-test-dynamicpv-qt8r": Phase="Pending", Reason="", readiness=false. Elapsed: 6.829177994s
Oct 14 09:37:51.209: INFO: Pod "exec-volume-test-dynamicpv-qt8r": Phase="Pending", Reason="", readiness=false. Elapsed: 9.036543546s
Oct 14 09:37:53.415: INFO: Pod "exec-volume-test-dynamicpv-qt8r": Phase="Pending", Reason="", readiness=false. Elapsed: 11.242552521s
... skipping 3 lines ...
Oct 14 09:38:02.250: INFO: Pod "exec-volume-test-dynamicpv-qt8r": Phase="Pending", Reason="", readiness=false. Elapsed: 20.077527422s
Oct 14 09:38:04.458: INFO: Pod "exec-volume-test-dynamicpv-qt8r": Phase="Pending", Reason="", readiness=false. Elapsed: 22.286340488s
Oct 14 09:38:06.666: INFO: Pod "exec-volume-test-dynamicpv-qt8r": Phase="Pending", Reason="", readiness=false. Elapsed: 24.49371086s
Oct 14 09:38:08.876: INFO: Pod "exec-volume-test-dynamicpv-qt8r": Phase="Running", Reason="", readiness=true. Elapsed: 26.703978449s
Oct 14 09:38:11.083: INFO: Pod "exec-volume-test-dynamicpv-qt8r": Phase="Succeeded", Reason="", readiness=false. Elapsed: 28.910492991s
STEP: Saw pod success
Oct 14 09:38:11.083: INFO: Pod "exec-volume-test-dynamicpv-qt8r" satisfied condition "Succeeded or Failed"
Oct 14 09:38:11.289: INFO: Trying to get logs from node ip-172-20-37-167.ap-southeast-1.compute.internal pod exec-volume-test-dynamicpv-qt8r container exec-container-dynamicpv-qt8r: <nil>
STEP: delete the pod
Oct 14 09:38:11.710: INFO: Waiting for pod exec-volume-test-dynamicpv-qt8r to disappear
Oct 14 09:38:11.916: INFO: Pod exec-volume-test-dynamicpv-qt8r no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-qt8r
Oct 14 09:38:11.916: INFO: Deleting pod "exec-volume-test-dynamicpv-qt8r" in namespace "volume-8727"
... skipping 128 lines ...
Oct 14 09:38:18.195: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-7349qr8q7
STEP: creating a claim
Oct 14 09:38:18.396: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Oct 14 09:38:18.792: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Oct 14 09:38:19.186: INFO: Error updating pvc aws5vp4n: PersistentVolumeClaim "aws5vp4n" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-7349qr8q7",
  	... // 3 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Oct 14 09:38:50.014: INFO: Error updating pvc aws5vp4n: PersistentVolumeClaim "aws5vp4n" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 322 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 14 09:38:27.658: 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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Oct 14 09:38:28.670: INFO: Creating resource for dynamic PV
Oct 14 09:38:28.670: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7031-e2e-scp56rc
STEP: creating a claim
Oct 14 09:38:28.874: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-xd64
STEP: Checking for subpath error in container status
Oct 14 09:38:45.888: INFO: Deleting pod "pod-subpath-test-dynamicpv-xd64" in namespace "provisioning-7031"
Oct 14 09:38:46.090: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-xd64" to be fully deleted
STEP: Deleting pod
Oct 14 09:38:48.495: INFO: Deleting pod "pod-subpath-test-dynamicpv-xd64" in namespace "provisioning-7031"
STEP: Deleting pvc
Oct 14 09:38:49.101: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comhn4z2"
... skipping 15 lines ...

• [SLOW TEST:58.892 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.h4kFCENj0/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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 450 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 14 09:38:50.068: 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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Oct 14 09:38:51.103: INFO: Creating resource for dynamic PV
Oct 14 09:38:51.103: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-6983-e2e-scz4tql
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Oct 14 09:38:56.561: INFO: Deleting pod "pod-61ab8b02-22c2-4d54-98f5-a5230ff57b64" in namespace "volumemode-6983"
Oct 14 09:38:56.768: INFO: Wait up to 5m0s for pod "pod-61ab8b02-22c2-4d54-98f5-a5230ff57b64" to be fully deleted
STEP: Deleting pvc
Oct 14 09:38:59.595: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comwccvp"
Oct 14 09:38:59.803: INFO: Waiting up to 5m0s for PersistentVolume pvc-c2cfb656-d298-47e8-a85e-1460dd39d721 to get deleted
Oct 14 09:39:00.009: INFO: PersistentVolume pvc-c2cfb656-d298-47e8-a85e-1460dd39d721 found and phase=Released (206.123758ms)
... skipping 12 lines ...

• [SLOW TEST:41.809 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.h4kFCENj0/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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Oct 14 09:39:31.878: INFO: Driver ebs.csi.aws.com doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
... skipping 71 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.h4kFCENj0/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.h4kFCENj0/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.h4kFCENj0/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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 36 lines ...
Oct 14 09:38:41.139: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-1005-e2e-scwdqnd
STEP: creating a claim
Oct 14 09:38:41.343: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-glrt
STEP: Creating a pod to test exec-volume-test
Oct 14 09:38:41.960: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-glrt" in namespace "volume-1005" to be "Succeeded or Failed"
Oct 14 09:38:42.163: INFO: Pod "exec-volume-test-dynamicpv-glrt": Phase="Pending", Reason="", readiness=false. Elapsed: 203.067886ms
Oct 14 09:38:44.369: INFO: Pod "exec-volume-test-dynamicpv-glrt": Phase="Pending", Reason="", readiness=false. Elapsed: 2.408592837s
Oct 14 09:38:46.573: INFO: Pod "exec-volume-test-dynamicpv-glrt": Phase="Pending", Reason="", readiness=false. Elapsed: 4.612492047s
Oct 14 09:38:48.777: INFO: Pod "exec-volume-test-dynamicpv-glrt": Phase="Pending", Reason="", readiness=false. Elapsed: 6.816655284s
Oct 14 09:38:50.982: INFO: Pod "exec-volume-test-dynamicpv-glrt": Phase="Pending", Reason="", readiness=false. Elapsed: 9.021996906s
Oct 14 09:38:53.186: INFO: Pod "exec-volume-test-dynamicpv-glrt": Phase="Pending", Reason="", readiness=false. Elapsed: 11.225481561s
Oct 14 09:38:55.390: INFO: Pod "exec-volume-test-dynamicpv-glrt": Phase="Pending", Reason="", readiness=false. Elapsed: 13.429905625s
Oct 14 09:38:57.594: INFO: Pod "exec-volume-test-dynamicpv-glrt": Phase="Running", Reason="", readiness=true. Elapsed: 15.633742396s
Oct 14 09:38:59.798: INFO: Pod "exec-volume-test-dynamicpv-glrt": Phase="Succeeded", Reason="", readiness=false. Elapsed: 17.837662037s
STEP: Saw pod success
Oct 14 09:38:59.798: INFO: Pod "exec-volume-test-dynamicpv-glrt" satisfied condition "Succeeded or Failed"
Oct 14 09:39:00.001: INFO: Trying to get logs from node ip-172-20-37-167.ap-southeast-1.compute.internal pod exec-volume-test-dynamicpv-glrt container exec-container-dynamicpv-glrt: <nil>
STEP: delete the pod
Oct 14 09:39:00.415: INFO: Waiting for pod exec-volume-test-dynamicpv-glrt to disappear
Oct 14 09:39:00.619: INFO: Pod exec-volume-test-dynamicpv-glrt no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-glrt
Oct 14 09:39:00.619: INFO: Deleting pod "exec-volume-test-dynamicpv-glrt" in namespace "volume-1005"
... skipping 69 lines ...
Oct 14 09:38:45.853: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7633qpn9t
STEP: creating a claim
Oct 14 09:38:46.060: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-xh92
STEP: Creating a pod to test subpath
Oct 14 09:38:46.683: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-xh92" in namespace "provisioning-7633" to be "Succeeded or Failed"
Oct 14 09:38:46.889: INFO: Pod "pod-subpath-test-dynamicpv-xh92": Phase="Pending", Reason="", readiness=false. Elapsed: 205.765319ms
Oct 14 09:38:49.095: INFO: Pod "pod-subpath-test-dynamicpv-xh92": Phase="Pending", Reason="", readiness=false. Elapsed: 2.412028492s
Oct 14 09:38:51.304: INFO: Pod "pod-subpath-test-dynamicpv-xh92": Phase="Pending", Reason="", readiness=false. Elapsed: 4.620449956s
Oct 14 09:38:53.512: INFO: Pod "pod-subpath-test-dynamicpv-xh92": Phase="Pending", Reason="", readiness=false. Elapsed: 6.828638448s
Oct 14 09:38:55.718: INFO: Pod "pod-subpath-test-dynamicpv-xh92": Phase="Pending", Reason="", readiness=false. Elapsed: 9.034473896s
Oct 14 09:38:57.925: INFO: Pod "pod-subpath-test-dynamicpv-xh92": Phase="Pending", Reason="", readiness=false. Elapsed: 11.241749376s
Oct 14 09:39:00.133: INFO: Pod "pod-subpath-test-dynamicpv-xh92": Phase="Pending", Reason="", readiness=false. Elapsed: 13.449464362s
Oct 14 09:39:02.340: INFO: Pod "pod-subpath-test-dynamicpv-xh92": Phase="Pending", Reason="", readiness=false. Elapsed: 15.656391374s
Oct 14 09:39:04.546: INFO: Pod "pod-subpath-test-dynamicpv-xh92": Phase="Pending", Reason="", readiness=false. Elapsed: 17.862825485s
Oct 14 09:39:06.752: INFO: Pod "pod-subpath-test-dynamicpv-xh92": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.06906677s
STEP: Saw pod success
Oct 14 09:39:06.753: INFO: Pod "pod-subpath-test-dynamicpv-xh92" satisfied condition "Succeeded or Failed"
Oct 14 09:39:06.959: INFO: Trying to get logs from node ip-172-20-37-167.ap-southeast-1.compute.internal pod pod-subpath-test-dynamicpv-xh92 container test-container-subpath-dynamicpv-xh92: <nil>
STEP: delete the pod
Oct 14 09:39:07.387: INFO: Waiting for pod pod-subpath-test-dynamicpv-xh92 to disappear
Oct 14 09:39:07.593: INFO: Pod pod-subpath-test-dynamicpv-xh92 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-xh92
Oct 14 09:39:07.593: INFO: Deleting pod "pod-subpath-test-dynamicpv-xh92" in namespace "provisioning-7633"
... skipping 97 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.h4kFCENj0/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.h4kFCENj0/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.h4kFCENj0/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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Driver supports dynamic provisioning, skipping InlineVolume pattern

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 21 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 14 09:38:51.004: 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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Oct 14 09:38:51.991: INFO: Creating resource for dynamic PV
Oct 14 09:38:51.991: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5866-e2e-sc4gzgk
STEP: creating a claim
Oct 14 09:38:52.191: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-7glb
STEP: Checking for subpath error in container status
Oct 14 09:39:07.178: INFO: Deleting pod "pod-subpath-test-dynamicpv-7glb" in namespace "provisioning-5866"
Oct 14 09:39:07.382: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-7glb" to be fully deleted
STEP: Deleting pod
Oct 14 09:39:09.777: INFO: Deleting pod "pod-subpath-test-dynamicpv-7glb" in namespace "provisioning-5866"
STEP: Deleting pvc
Oct 14 09:39:10.366: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comxjbjz"
... skipping 14 lines ...

• [SLOW TEST:51.555 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath file is outside the volume [Slow][LinuxOnly]
    /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 180 lines ...
Oct 14 09:38:26.590: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-536-e2e-scdbvcm
STEP: creating a claim
Oct 14 09:38:26.796: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-ptxp
STEP: Creating a pod to test atomic-volume-subpath
Oct 14 09:38:27.413: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-ptxp" in namespace "provisioning-536" to be "Succeeded or Failed"
Oct 14 09:38:27.617: INFO: Pod "pod-subpath-test-dynamicpv-ptxp": Phase="Pending", Reason="", readiness=false. Elapsed: 204.207029ms
Oct 14 09:38:29.823: INFO: Pod "pod-subpath-test-dynamicpv-ptxp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.409561701s
Oct 14 09:38:32.027: INFO: Pod "pod-subpath-test-dynamicpv-ptxp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.614063925s
Oct 14 09:38:34.234: INFO: Pod "pod-subpath-test-dynamicpv-ptxp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.820554215s
Oct 14 09:38:36.441: INFO: Pod "pod-subpath-test-dynamicpv-ptxp": Phase="Pending", Reason="", readiness=false. Elapsed: 9.027653923s
Oct 14 09:38:38.646: INFO: Pod "pod-subpath-test-dynamicpv-ptxp": Phase="Pending", Reason="", readiness=false. Elapsed: 11.233433636s
... skipping 10 lines ...
Oct 14 09:39:02.915: INFO: Pod "pod-subpath-test-dynamicpv-ptxp": Phase="Running", Reason="", readiness=true. Elapsed: 35.501562728s
Oct 14 09:39:05.119: INFO: Pod "pod-subpath-test-dynamicpv-ptxp": Phase="Running", Reason="", readiness=true. Elapsed: 37.706178171s
Oct 14 09:39:07.329: INFO: Pod "pod-subpath-test-dynamicpv-ptxp": Phase="Running", Reason="", readiness=true. Elapsed: 39.915553173s
Oct 14 09:39:09.533: INFO: Pod "pod-subpath-test-dynamicpv-ptxp": Phase="Running", Reason="", readiness=true. Elapsed: 42.120244477s
Oct 14 09:39:11.738: INFO: Pod "pod-subpath-test-dynamicpv-ptxp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 44.325027149s
STEP: Saw pod success
Oct 14 09:39:11.738: INFO: Pod "pod-subpath-test-dynamicpv-ptxp" satisfied condition "Succeeded or Failed"
Oct 14 09:39:11.945: INFO: Trying to get logs from node ip-172-20-47-16.ap-southeast-1.compute.internal pod pod-subpath-test-dynamicpv-ptxp container test-container-subpath-dynamicpv-ptxp: <nil>
STEP: delete the pod
Oct 14 09:39:12.365: INFO: Waiting for pod pod-subpath-test-dynamicpv-ptxp to disappear
Oct 14 09:39:12.569: INFO: Pod pod-subpath-test-dynamicpv-ptxp no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-ptxp
Oct 14 09:39:12.569: INFO: Deleting pod "pod-subpath-test-dynamicpv-ptxp" in namespace "provisioning-536"
... skipping 190 lines ...
Oct 14 09:39:38.909: INFO: Waiting for pod aws-client to disappear
Oct 14 09:39:39.118: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Oct 14 09:39:39.119: INFO: Deleting PersistentVolumeClaim "pvc-gm2ws"
Oct 14 09:39:39.330: INFO: Deleting PersistentVolume "aws-9mqvt"
Oct 14 09:39:40.518: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-05479a3d5ebf10ce3", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05479a3d5ebf10ce3 is currently attached to i-0053439ffca389c81
	status code: 400, request id: 438a73e4-81cb-41e0-ba3b-062877ed9b37
Oct 14 09:39:46.494: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-05479a3d5ebf10ce3", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05479a3d5ebf10ce3 is currently attached to i-0053439ffca389c81
	status code: 400, request id: 7bc63ece-a719-4646-b299-f77faa2bb83d
Oct 14 09:39:52.528: INFO: Successfully deleted PD "aws://ap-southeast-1a/vol-05479a3d5ebf10ce3".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 14 09:39:52.528: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-1439" for this suite.
... skipping 14 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 14 09:39:33.487: 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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Oct 14 09:39:34.505: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 14 09:39:34.505: INFO: Creating resource for dynamic PV
Oct 14 09:39:34.505: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-86977mb4l
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Oct 14 09:39:39.947: INFO: Deleting pod "pod-aa170aa6-5ada-48ed-b061-20b5f1f007f6" in namespace "volumemode-8697"
Oct 14 09:39:40.152: INFO: Wait up to 5m0s for pod "pod-aa170aa6-5ada-48ed-b061-20b5f1f007f6" to be fully deleted
STEP: Deleting pvc
Oct 14 09:39:42.965: INFO: Deleting PersistentVolumeClaim "aws9n7xs"
Oct 14 09:39:43.174: INFO: Waiting up to 5m0s for PersistentVolume pvc-7337bbf2-dce6-49d7-b47c-9a25741f25d1 to get deleted
Oct 14 09:39:43.378: INFO: PersistentVolume pvc-7337bbf2-dce6-49d7-b47c-9a25741f25d1 found and phase=Released (203.651455ms)
... skipping 10 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.h4kFCENj0/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.h4kFCENj0/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
    /tmp/kops.h4kFCENj0/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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Oct 14 09:39:54.408: INFO: Driver "ebs.csi.aws.com" does not support volume type "PreprovisionedPV" - skipping
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
... skipping 614 lines ...
Oct 14 09:39:27.664: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-36362lm89
STEP: creating a claim
Oct 14 09:39:27.861: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-flgq
STEP: Creating a pod to test exec-volume-test
Oct 14 09:39:28.458: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-flgq" in namespace "volume-3636" to be "Succeeded or Failed"
Oct 14 09:39:28.655: INFO: Pod "exec-volume-test-dynamicpv-flgq": Phase="Pending", Reason="", readiness=false. Elapsed: 196.781363ms
Oct 14 09:39:30.854: INFO: Pod "exec-volume-test-dynamicpv-flgq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.396046475s
Oct 14 09:39:33.053: INFO: Pod "exec-volume-test-dynamicpv-flgq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.594824919s
Oct 14 09:39:35.251: INFO: Pod "exec-volume-test-dynamicpv-flgq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.792787769s
Oct 14 09:39:37.464: INFO: Pod "exec-volume-test-dynamicpv-flgq": Phase="Pending", Reason="", readiness=false. Elapsed: 9.005969343s
Oct 14 09:39:39.661: INFO: Pod "exec-volume-test-dynamicpv-flgq": Phase="Pending", Reason="", readiness=false. Elapsed: 11.203380309s
Oct 14 09:39:41.860: INFO: Pod "exec-volume-test-dynamicpv-flgq": Phase="Pending", Reason="", readiness=false. Elapsed: 13.40176504s
Oct 14 09:39:44.057: INFO: Pod "exec-volume-test-dynamicpv-flgq": Phase="Pending", Reason="", readiness=false. Elapsed: 15.599530291s
Oct 14 09:39:46.255: INFO: Pod "exec-volume-test-dynamicpv-flgq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 17.797390701s
STEP: Saw pod success
Oct 14 09:39:46.255: INFO: Pod "exec-volume-test-dynamicpv-flgq" satisfied condition "Succeeded or Failed"
Oct 14 09:39:46.455: INFO: Trying to get logs from node ip-172-20-33-219.ap-southeast-1.compute.internal pod exec-volume-test-dynamicpv-flgq container exec-container-dynamicpv-flgq: <nil>
STEP: delete the pod
Oct 14 09:39:46.858: INFO: Waiting for pod exec-volume-test-dynamicpv-flgq to disappear
Oct 14 09:39:47.055: INFO: Pod exec-volume-test-dynamicpv-flgq no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-flgq
Oct 14 09:39:47.055: INFO: Deleting pod "exec-volume-test-dynamicpv-flgq" in namespace "volume-3636"
... skipping 683 lines ...
STEP: Deleting pod hostexec-ip-172-20-37-167.ap-southeast-1.compute.internal-b7nxh in namespace volumemode-2066
Oct 14 09:40:03.473: INFO: Deleting pod "pod-57dd6863-11a6-495d-a92c-ed23dd698e05" in namespace "volumemode-2066"
Oct 14 09:40:03.695: INFO: Wait up to 5m0s for pod "pod-57dd6863-11a6-495d-a92c-ed23dd698e05" to be fully deleted
STEP: Deleting pv and pvc
Oct 14 09:40:06.111: INFO: Deleting PersistentVolumeClaim "pvc-dr9gz"
Oct 14 09:40:06.319: INFO: Deleting PersistentVolume "aws-2sr5s"
Oct 14 09:40:06.839: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-005731cf5512a03f2", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-005731cf5512a03f2 is currently attached to i-057009a9735869b54
	status code: 400, request id: a1b2143d-dda6-44a6-9c59-646afc17bc85
Oct 14 09:40:12.786: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-005731cf5512a03f2", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-005731cf5512a03f2 is currently attached to i-057009a9735869b54
	status code: 400, request id: a791d4aa-799c-4fc7-ae01-0660cc7d8dcf
Oct 14 09:40:18.683: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-005731cf5512a03f2", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-005731cf5512a03f2 is currently attached to i-057009a9735869b54
	status code: 400, request id: c83d0559-b10d-4308-b89b-875124c6cb92
Oct 14 09:40:24.637: INFO: Successfully deleted PD "aws://ap-southeast-1a/vol-005731cf5512a03f2".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 14 09:40:24.637: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-2066" for this suite.
... skipping 111 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.h4kFCENj0/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.h4kFCENj0/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.h4kFCENj0/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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Distro debian doesn't support ntfs -- skipping

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.000 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.h4kFCENj0/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.h4kFCENj0/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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 2 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 14 09:39:56.104: 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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Oct 14 09:39:57.114: INFO: Creating resource for dynamic PV
Oct 14 09:39:57.114: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6490-e2e-sc9pbhd
STEP: creating a claim
Oct 14 09:39:57.316: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-kpq8
STEP: Checking for subpath error in container status
Oct 14 09:40:22.335: INFO: Deleting pod "pod-subpath-test-dynamicpv-kpq8" in namespace "provisioning-6490"
Oct 14 09:40:22.540: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-kpq8" to be fully deleted
STEP: Deleting pod
Oct 14 09:40:24.943: INFO: Deleting pod "pod-subpath-test-dynamicpv-kpq8" in namespace "provisioning-6490"
STEP: Deleting pvc
Oct 14 09:40:25.554: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com5x7vh"
... skipping 11 lines ...

• [SLOW TEST:46.069 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.h4kFCENj0/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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 75 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.h4kFCENj0/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.h4kFCENj0/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.h4kFCENj0/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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 11 lines ...
Oct 14 09:40:08.027: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-8210-e2e-scnsclh
STEP: creating a claim
Oct 14 09:40:08.225: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-9mk5
STEP: Creating a pod to test exec-volume-test
Oct 14 09:40:08.818: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-9mk5" in namespace "volume-8210" to be "Succeeded or Failed"
Oct 14 09:40:09.015: INFO: Pod "exec-volume-test-dynamicpv-9mk5": Phase="Pending", Reason="", readiness=false. Elapsed: 196.609798ms
Oct 14 09:40:11.212: INFO: Pod "exec-volume-test-dynamicpv-9mk5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.393891923s
Oct 14 09:40:13.409: INFO: Pod "exec-volume-test-dynamicpv-9mk5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.591087696s
Oct 14 09:40:15.608: INFO: Pod "exec-volume-test-dynamicpv-9mk5": Phase="Pending", Reason="", readiness=false. Elapsed: 6.790054503s
Oct 14 09:40:17.805: INFO: Pod "exec-volume-test-dynamicpv-9mk5": Phase="Pending", Reason="", readiness=false. Elapsed: 8.986510122s
Oct 14 09:40:20.002: INFO: Pod "exec-volume-test-dynamicpv-9mk5": Phase="Pending", Reason="", readiness=false. Elapsed: 11.183397628s
Oct 14 09:40:22.200: INFO: Pod "exec-volume-test-dynamicpv-9mk5": Phase="Pending", Reason="", readiness=false. Elapsed: 13.381781108s
Oct 14 09:40:24.397: INFO: Pod "exec-volume-test-dynamicpv-9mk5": Phase="Pending", Reason="", readiness=false. Elapsed: 15.578756692s
Oct 14 09:40:26.594: INFO: Pod "exec-volume-test-dynamicpv-9mk5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 17.775658393s
STEP: Saw pod success
Oct 14 09:40:26.594: INFO: Pod "exec-volume-test-dynamicpv-9mk5" satisfied condition "Succeeded or Failed"
Oct 14 09:40:26.790: INFO: Trying to get logs from node ip-172-20-47-2.ap-southeast-1.compute.internal pod exec-volume-test-dynamicpv-9mk5 container exec-container-dynamicpv-9mk5: <nil>
STEP: delete the pod
Oct 14 09:40:27.204: INFO: Waiting for pod exec-volume-test-dynamicpv-9mk5 to disappear
Oct 14 09:40:27.403: INFO: Pod exec-volume-test-dynamicpv-9mk5 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-9mk5
Oct 14 09:40:27.403: INFO: Deleting pod "exec-volume-test-dynamicpv-9mk5" in namespace "volume-8210"
... skipping 101 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 14 09:40:20.343: 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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Oct 14 09:40:21.343: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 14 09:40:21.343: INFO: Creating resource for dynamic PV
Oct 14 09:40:21.343: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-37837m7dw
STEP: creating a claim
Oct 14 09:40:21.543: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-tvsm
STEP: Checking for subpath error in container status
Oct 14 09:40:34.546: INFO: Deleting pod "pod-subpath-test-dynamicpv-tvsm" in namespace "provisioning-3783"
Oct 14 09:40:34.747: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-tvsm" to be fully deleted
STEP: Deleting pod
Oct 14 09:40:37.151: INFO: Deleting pod "pod-subpath-test-dynamicpv-tvsm" in namespace "provisioning-3783"
STEP: Deleting pvc
Oct 14 09:40:37.760: INFO: Deleting PersistentVolumeClaim "aws225zh"
... skipping 12 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.h4kFCENj0/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.h4kFCENj0/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath directory is outside the volume [Slow][LinuxOnly]
      /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Oct 14 09:40:49.175: INFO: Driver ebs.csi.aws.com doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
... skipping 94 lines ...
Oct 14 09:39:56.884: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-7423jbgj4      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-7423    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-7423jbgj4,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-7423    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-7423jbgj4,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-7423    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-7423jbgj4,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-7423jbgj4    c882b47d-6361-4e04-a7d2-6aaa208a38eb 7661 0 2021-10-14 09:39:57 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-10-14 09:39:57 +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-zbsm5 pvc- provisioning-7423  4e178b68-5c7d-479b-8782-1452a2343b3a 7694 0 2021-10-14 09:39:57 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-10-14 09:39:57 +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-7423jbgj4,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-7edf9eb1-7b91-41d5-9a2f-efc0bf523047 in namespace provisioning-7423
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Oct 14 09:40:13.134: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-hw6bq" in namespace "provisioning-7423" to be "Succeeded or Failed"
Oct 14 09:40:13.337: INFO: Pod "pvc-volume-tester-writer-hw6bq": Phase="Pending", Reason="", readiness=false. Elapsed: 203.251186ms
Oct 14 09:40:15.541: INFO: Pod "pvc-volume-tester-writer-hw6bq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.407759885s
Oct 14 09:40:17.745: INFO: Pod "pvc-volume-tester-writer-hw6bq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.611243453s
Oct 14 09:40:19.948: INFO: Pod "pvc-volume-tester-writer-hw6bq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.814640966s
STEP: Saw pod success
Oct 14 09:40:19.948: INFO: Pod "pvc-volume-tester-writer-hw6bq" satisfied condition "Succeeded or Failed"
Oct 14 09:40:20.357: INFO: Pod pvc-volume-tester-writer-hw6bq has the following logs: 
Oct 14 09:40:20.357: INFO: Deleting pod "pvc-volume-tester-writer-hw6bq" in namespace "provisioning-7423"
Oct 14 09:40:20.574: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-hw6bq" to be fully deleted
STEP: checking the created volume has the correct mount options, is readable and retains data on the same node "ip-172-20-47-16.ap-southeast-1.compute.internal"
Oct 14 09:40:21.389: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-f7ft8" in namespace "provisioning-7423" to be "Succeeded or Failed"
Oct 14 09:40:21.593: INFO: Pod "pvc-volume-tester-reader-f7ft8": Phase="Pending", Reason="", readiness=false. Elapsed: 203.508431ms
Oct 14 09:40:23.797: INFO: Pod "pvc-volume-tester-reader-f7ft8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.407801495s
Oct 14 09:40:26.008: INFO: Pod "pvc-volume-tester-reader-f7ft8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.618717956s
Oct 14 09:40:28.214: INFO: Pod "pvc-volume-tester-reader-f7ft8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.825343729s
Oct 14 09:40:30.419: INFO: Pod "pvc-volume-tester-reader-f7ft8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 9.029517513s
STEP: Saw pod success
Oct 14 09:40:30.419: INFO: Pod "pvc-volume-tester-reader-f7ft8" satisfied condition "Succeeded or Failed"
Oct 14 09:40:30.827: INFO: Pod pvc-volume-tester-reader-f7ft8 has the following logs: hello world

Oct 14 09:40:30.827: INFO: Deleting pod "pvc-volume-tester-reader-f7ft8" in namespace "provisioning-7423"
Oct 14 09:40:31.039: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-f7ft8" to be fully deleted
Oct 14 09:40:31.243: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-zbsm5] to have phase Bound
Oct 14 09:40:31.446: INFO: PersistentVolumeClaim pvc-zbsm5 found and phase=Bound (203.096578ms)
... skipping 250 lines ...
STEP: Deleting pod hostexec-ip-172-20-47-16.ap-southeast-1.compute.internal-mkphs in namespace volumemode-2196
Oct 14 09:40:46.351: INFO: Deleting pod "pod-3e3e6b43-47c5-416e-932a-1187e78938f2" in namespace "volumemode-2196"
Oct 14 09:40:46.561: INFO: Wait up to 5m0s for pod "pod-3e3e6b43-47c5-416e-932a-1187e78938f2" to be fully deleted
STEP: Deleting pv and pvc
Oct 14 09:40:48.975: INFO: Deleting PersistentVolumeClaim "pvc-j6lmz"
Oct 14 09:40:49.182: INFO: Deleting PersistentVolume "aws-vsj7h"
Oct 14 09:40:49.717: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-042f1f2c6a2510064", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-042f1f2c6a2510064 is currently attached to i-0023c706c9d49ee11
	status code: 400, request id: 4d25b603-3fb4-460f-aa8e-95f7ed6f3caf
Oct 14 09:40:55.676: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-042f1f2c6a2510064", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-042f1f2c6a2510064 is currently attached to i-0023c706c9d49ee11
	status code: 400, request id: 9669d31c-087a-4761-b89e-d14ec72d5ec0
Oct 14 09:41:02.217: INFO: Successfully deleted PD "aws://ap-southeast-1a/vol-042f1f2c6a2510064".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 14 09:41:02.218: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-2196" for this suite.
... skipping 480 lines ...
Oct 14 09:41:02.644: INFO: Waiting for pod aws-client to disappear
Oct 14 09:41:02.846: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Oct 14 09:41:02.846: INFO: Deleting PersistentVolumeClaim "pvc-22wtr"
Oct 14 09:41:03.049: INFO: Deleting PersistentVolume "aws-w5jn7"
Oct 14 09:41:03.558: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-0a556f4fdb8a063c2", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a556f4fdb8a063c2 is currently attached to i-057009a9735869b54
	status code: 400, request id: 5da77c5c-4ed8-4d90-9003-2267c99a4f21
Oct 14 09:41:09.506: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-0a556f4fdb8a063c2", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a556f4fdb8a063c2 is currently attached to i-057009a9735869b54
	status code: 400, request id: 17cdab3d-15a9-4701-a809-a8a98b391387
Oct 14 09:41:15.464: INFO: Successfully deleted PD "aws://ap-southeast-1a/vol-0a556f4fdb8a063c2".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumes
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 14 09:41:15.464: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-7996" for this suite.
... skipping 14 lines ...
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 14 09:41:15.811: 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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Oct 14 09:41:17.022: INFO: found topology map[topology.kubernetes.io/zone:ap-southeast-1a]
Oct 14 09:41:17.022: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 14 09:41:17.022: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.h4kFCENj0/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.h4kFCENj0/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (delayed binding)] topology
    /tmp/kops.h4kFCENj0/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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 10 lines ...
Oct 14 09:40:38.998: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Oct 14 09:40:40.103: INFO: Successfully created a new PD: "aws://ap-southeast-1a/vol-020828e8e1867b391".
Oct 14 09:40:40.103: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-x7t2
STEP: Creating a pod to test exec-volume-test
Oct 14 09:40:40.310: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-x7t2" in namespace "volume-5934" to be "Succeeded or Failed"
Oct 14 09:40:40.505: INFO: Pod "exec-volume-test-inlinevolume-x7t2": Phase="Pending", Reason="", readiness=false. Elapsed: 195.186217ms
Oct 14 09:40:42.705: INFO: Pod "exec-volume-test-inlinevolume-x7t2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.395097043s
Oct 14 09:40:44.904: INFO: Pod "exec-volume-test-inlinevolume-x7t2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.594770481s
Oct 14 09:40:47.100: INFO: Pod "exec-volume-test-inlinevolume-x7t2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.790540025s
Oct 14 09:40:49.298: INFO: Pod "exec-volume-test-inlinevolume-x7t2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.988863166s
Oct 14 09:40:51.498: INFO: Pod "exec-volume-test-inlinevolume-x7t2": Phase="Pending", Reason="", readiness=false. Elapsed: 11.188046809s
Oct 14 09:40:53.694: INFO: Pod "exec-volume-test-inlinevolume-x7t2": Phase="Pending", Reason="", readiness=false. Elapsed: 13.383959181s
Oct 14 09:40:55.890: INFO: Pod "exec-volume-test-inlinevolume-x7t2": Phase="Pending", Reason="", readiness=false. Elapsed: 15.580285418s
Oct 14 09:40:58.087: INFO: Pod "exec-volume-test-inlinevolume-x7t2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 17.777780313s
STEP: Saw pod success
Oct 14 09:40:58.087: INFO: Pod "exec-volume-test-inlinevolume-x7t2" satisfied condition "Succeeded or Failed"
Oct 14 09:40:58.283: INFO: Trying to get logs from node ip-172-20-33-219.ap-southeast-1.compute.internal pod exec-volume-test-inlinevolume-x7t2 container exec-container-inlinevolume-x7t2: <nil>
STEP: delete the pod
Oct 14 09:40:58.684: INFO: Waiting for pod exec-volume-test-inlinevolume-x7t2 to disappear
Oct 14 09:40:58.879: INFO: Pod exec-volume-test-inlinevolume-x7t2 no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-x7t2
Oct 14 09:40:58.879: INFO: Deleting pod "exec-volume-test-inlinevolume-x7t2" in namespace "volume-5934"
Oct 14 09:40:59.397: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-020828e8e1867b391", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-020828e8e1867b391 is currently attached to i-02f264506a5f6d293
	status code: 400, request id: bc20c670-2cd6-4f80-a5fa-f81ae1411e50
Oct 14 09:41:05.362: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-020828e8e1867b391", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-020828e8e1867b391 is currently attached to i-02f264506a5f6d293
	status code: 400, request id: 42f6f4e7-4842-4219-b1dc-f98d8ee7b8ce
Oct 14 09:41:11.302: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-020828e8e1867b391", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-020828e8e1867b391 is currently attached to i-02f264506a5f6d293
	status code: 400, request id: c83fbbf4-2048-4bc4-a395-772c1ca5f597
Oct 14 09:41:17.240: INFO: Successfully deleted PD "aws://ap-southeast-1a/vol-020828e8e1867b391".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 14 09:41:17.240: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-5934" for this suite.
... skipping 286 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.h4kFCENj0/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.h4kFCENj0/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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 265 lines ...
Oct 14 09:37:01.758: INFO: Creating resource for dynamic PV
Oct 14 09:37:01.758: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-6887-e2e-scrqndg
STEP: creating a claim
Oct 14 09:37:01.967: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Oct 14 09:37:02.651: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-66fgp" in namespace "snapshotting-6887" to be "Succeeded or Failed"
Oct 14 09:37:02.855: INFO: Pod "pvc-snapshottable-tester-66fgp": Phase="Pending", Reason="", readiness=false. Elapsed: 203.732921ms
Oct 14 09:37:05.059: INFO: Pod "pvc-snapshottable-tester-66fgp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.408366738s
Oct 14 09:37:07.275: INFO: Pod "pvc-snapshottable-tester-66fgp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.62416858s
Oct 14 09:37:09.480: INFO: Pod "pvc-snapshottable-tester-66fgp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.829091785s
Oct 14 09:37:11.686: INFO: Pod "pvc-snapshottable-tester-66fgp": Phase="Pending", Reason="", readiness=false. Elapsed: 9.034699041s
Oct 14 09:37:13.890: INFO: Pod "pvc-snapshottable-tester-66fgp": Phase="Pending", Reason="", readiness=false. Elapsed: 11.239387616s
Oct 14 09:37:16.096: INFO: Pod "pvc-snapshottable-tester-66fgp": Phase="Pending", Reason="", readiness=false. Elapsed: 13.445379785s
Oct 14 09:37:18.300: INFO: Pod "pvc-snapshottable-tester-66fgp": Phase="Pending", Reason="", readiness=false. Elapsed: 15.649327044s
Oct 14 09:37:20.505: INFO: Pod "pvc-snapshottable-tester-66fgp": Phase="Pending", Reason="", readiness=false. Elapsed: 17.854393875s
Oct 14 09:37:22.710: INFO: Pod "pvc-snapshottable-tester-66fgp": Phase="Pending", Reason="", readiness=false. Elapsed: 20.059162423s
Oct 14 09:37:24.915: INFO: Pod "pvc-snapshottable-tester-66fgp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.26428736s
STEP: Saw pod success
Oct 14 09:37:24.915: INFO: Pod "pvc-snapshottable-tester-66fgp" satisfied condition "Succeeded or Failed"
Oct 14 09:37:26.215: INFO: Pod pvc-snapshottable-tester-66fgp has the following logs: 
Oct 14 09:37:26.215: INFO: Deleting pod "pvc-snapshottable-tester-66fgp" in namespace "snapshotting-6887"
Oct 14 09:37:26.447: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-66fgp" to be fully deleted
Oct 14 09:37:26.681: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comrh5gd] to have phase Bound
Oct 14 09:37:26.885: INFO: PersistentVolumeClaim ebs.csi.aws.comrh5gd found and phase=Bound (203.705791ms)
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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:243
STEP: checking the snapshot
STEP: checking the SnapshotContent
STEP: Modifying source data test
STEP: modifying the data in the source PVC
Oct 14 09:40:05.783: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-glgx2" in namespace "snapshotting-6887" to be "Succeeded or Failed"
Oct 14 09:40:05.994: INFO: Pod "pvc-snapshottable-data-tester-glgx2": Phase="Pending", Reason="", readiness=false. Elapsed: 210.790392ms
Oct 14 09:40:08.199: INFO: Pod "pvc-snapshottable-data-tester-glgx2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.415575491s
Oct 14 09:40:10.408: INFO: Pod "pvc-snapshottable-data-tester-glgx2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.625039492s
Oct 14 09:40:12.618: INFO: Pod "pvc-snapshottable-data-tester-glgx2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.834718612s
Oct 14 09:40:14.822: INFO: Pod "pvc-snapshottable-data-tester-glgx2": Phase="Pending", Reason="", readiness=false. Elapsed: 9.039166809s
Oct 14 09:40:17.027: INFO: Pod "pvc-snapshottable-data-tester-glgx2": Phase="Pending", Reason="", readiness=false. Elapsed: 11.243572673s
... skipping 6 lines ...
Oct 14 09:40:32.463: INFO: Pod "pvc-snapshottable-data-tester-glgx2": Phase="Pending", Reason="", readiness=false. Elapsed: 26.679875694s
Oct 14 09:40:34.668: INFO: Pod "pvc-snapshottable-data-tester-glgx2": Phase="Pending", Reason="", readiness=false. Elapsed: 28.885441888s
Oct 14 09:40:36.873: INFO: Pod "pvc-snapshottable-data-tester-glgx2": Phase="Pending", Reason="", readiness=false. Elapsed: 31.090185812s
Oct 14 09:40:39.078: INFO: Pod "pvc-snapshottable-data-tester-glgx2": Phase="Pending", Reason="", readiness=false. Elapsed: 33.295417868s
Oct 14 09:40:41.284: INFO: Pod "pvc-snapshottable-data-tester-glgx2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 35.500966919s
STEP: Saw pod success
Oct 14 09:40:41.284: INFO: Pod "pvc-snapshottable-data-tester-glgx2" satisfied condition "Succeeded or Failed"
Oct 14 09:40:41.699: INFO: Pod pvc-snapshottable-data-tester-glgx2 has the following logs: 
Oct 14 09:40:41.699: INFO: Deleting pod "pvc-snapshottable-data-tester-glgx2" in namespace "snapshotting-6887"
Oct 14 09:40:41.912: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-glgx2" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Oct 14 09:40:52.937: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-b6f7c24027-45100.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-6887 exec restored-pvc-tester-pkj7j --namespace=snapshotting-6887 -- cat /mnt/test/data'
... skipping 81 lines ...
Oct 14 09:37:01.855: INFO: Creating resource for dynamic PV
Oct 14 09:37:01.855: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-3816-e2e-schnnfh
STEP: creating a claim
Oct 14 09:37:02.060: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Oct 14 09:37:02.685: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-hhjt2" in namespace "snapshotting-3816" to be "Succeeded or Failed"
Oct 14 09:37:02.890: INFO: Pod "pvc-snapshottable-tester-hhjt2": Phase="Pending", Reason="", readiness=false. Elapsed: 204.687447ms
Oct 14 09:37:05.094: INFO: Pod "pvc-snapshottable-tester-hhjt2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.409276511s
Oct 14 09:37:07.317: INFO: Pod "pvc-snapshottable-tester-hhjt2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.632476934s
Oct 14 09:37:09.525: INFO: Pod "pvc-snapshottable-tester-hhjt2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.840073474s
Oct 14 09:37:11.731: INFO: Pod "pvc-snapshottable-tester-hhjt2": Phase="Pending", Reason="", readiness=false. Elapsed: 9.045949242s
Oct 14 09:37:13.936: INFO: Pod "pvc-snapshottable-tester-hhjt2": Phase="Pending", Reason="", readiness=false. Elapsed: 11.251501644s
Oct 14 09:37:16.145: INFO: Pod "pvc-snapshottable-tester-hhjt2": Phase="Pending", Reason="", readiness=false. Elapsed: 13.460447589s
Oct 14 09:37:18.350: INFO: Pod "pvc-snapshottable-tester-hhjt2": Phase="Pending", Reason="", readiness=false. Elapsed: 15.665551441s
Oct 14 09:37:20.556: INFO: Pod "pvc-snapshottable-tester-hhjt2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 17.871408133s
STEP: Saw pod success
Oct 14 09:37:20.556: INFO: Pod "pvc-snapshottable-tester-hhjt2" satisfied condition "Succeeded or Failed"
Oct 14 09:37:20.981: INFO: Pod pvc-snapshottable-tester-hhjt2 has the following logs: 
Oct 14 09:37:20.981: INFO: Deleting pod "pvc-snapshottable-tester-hhjt2" in namespace "snapshotting-3816"
Oct 14 09:37:21.192: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-hhjt2" to be fully deleted
Oct 14 09:37:21.396: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comfcfsq] to have phase Bound
Oct 14 09:37:21.600: INFO: PersistentVolumeClaim ebs.csi.aws.comfcfsq found and phase=Bound (204.084756ms)
STEP: [init] checking the claim
... skipping 105 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:243
STEP: checking the snapshot
STEP: checking the SnapshotContent
STEP: Modifying source data test
STEP: modifying the data in the source PVC
Oct 14 09:40:15.530: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-tc5sf" in namespace "snapshotting-3816" to be "Succeeded or Failed"
Oct 14 09:40:15.728: INFO: Pod "pvc-snapshottable-data-tester-tc5sf": Phase="Pending", Reason="", readiness=false. Elapsed: 197.32281ms
Oct 14 09:40:17.925: INFO: Pod "pvc-snapshottable-data-tester-tc5sf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.394531978s
Oct 14 09:40:20.122: INFO: Pod "pvc-snapshottable-data-tester-tc5sf": Phase="Pending", Reason="", readiness=false. Elapsed: 4.591814506s
Oct 14 09:40:22.321: INFO: Pod "pvc-snapshottable-data-tester-tc5sf": Phase="Pending", Reason="", readiness=false. Elapsed: 6.790491674s
Oct 14 09:40:24.518: INFO: Pod "pvc-snapshottable-data-tester-tc5sf": Phase="Pending", Reason="", readiness=false. Elapsed: 8.987601204s
Oct 14 09:40:26.716: INFO: Pod "pvc-snapshottable-data-tester-tc5sf": Phase="Pending", Reason="", readiness=false. Elapsed: 11.185063098s
Oct 14 09:40:28.913: INFO: Pod "pvc-snapshottable-data-tester-tc5sf": Phase="Pending", Reason="", readiness=false. Elapsed: 13.382787684s
Oct 14 09:40:31.111: INFO: Pod "pvc-snapshottable-data-tester-tc5sf": Phase="Pending", Reason="", readiness=false. Elapsed: 15.58045353s
Oct 14 09:40:33.309: INFO: Pod "pvc-snapshottable-data-tester-tc5sf": Phase="Pending", Reason="", readiness=false. Elapsed: 17.778183198s
Oct 14 09:40:35.507: INFO: Pod "pvc-snapshottable-data-tester-tc5sf": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.976162268s
STEP: Saw pod success
Oct 14 09:40:35.507: INFO: Pod "pvc-snapshottable-data-tester-tc5sf" satisfied condition "Succeeded or Failed"
Oct 14 09:40:35.907: INFO: Pod pvc-snapshottable-data-tester-tc5sf has the following logs: 
Oct 14 09:40:35.908: INFO: Deleting pod "pvc-snapshottable-data-tester-tc5sf" in namespace "snapshotting-3816"
Oct 14 09:40:36.113: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-tc5sf" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Oct 14 09:40:51.113: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-b6f7c24027-45100.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-3816 exec restored-pvc-tester-ctt76 --namespace=snapshotting-3816 -- cat /mnt/test/data'
... skipping 181 lines ...
Oct 14 09:41:04.074: INFO: PersistentVolumeClaim pvc-q9l42 found but phase is Pending instead of Bound.
Oct 14 09:41:06.280: INFO: PersistentVolumeClaim pvc-q9l42 found and phase=Bound (11.2393555s)
Oct 14 09:41:06.280: INFO: Waiting up to 3m0s for PersistentVolume aws-hxp28 to have phase Bound
Oct 14 09:41:06.485: INFO: PersistentVolume aws-hxp28 found and phase=Bound (205.344754ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-5wcg
STEP: Creating a pod to test exec-volume-test
Oct 14 09:41:07.101: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-5wcg" in namespace "volume-5128" to be "Succeeded or Failed"
Oct 14 09:41:07.305: INFO: Pod "exec-volume-test-preprovisionedpv-5wcg": Phase="Pending", Reason="", readiness=false. Elapsed: 204.627006ms
Oct 14 09:41:09.511: INFO: Pod "exec-volume-test-preprovisionedpv-5wcg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.410095492s
Oct 14 09:41:11.716: INFO: Pod "exec-volume-test-preprovisionedpv-5wcg": Phase="Pending", Reason="", readiness=false. Elapsed: 4.615023814s
Oct 14 09:41:13.921: INFO: Pod "exec-volume-test-preprovisionedpv-5wcg": Phase="Pending", Reason="", readiness=false. Elapsed: 6.82076383s
Oct 14 09:41:16.127: INFO: Pod "exec-volume-test-preprovisionedpv-5wcg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 9.026207611s
STEP: Saw pod success
Oct 14 09:41:16.127: INFO: Pod "exec-volume-test-preprovisionedpv-5wcg" satisfied condition "Succeeded or Failed"
Oct 14 09:41:16.333: INFO: Trying to get logs from node ip-172-20-37-167.ap-southeast-1.compute.internal pod exec-volume-test-preprovisionedpv-5wcg container exec-container-preprovisionedpv-5wcg: <nil>
STEP: delete the pod
Oct 14 09:41:16.761: INFO: Waiting for pod exec-volume-test-preprovisionedpv-5wcg to disappear
Oct 14 09:41:16.966: INFO: Pod exec-volume-test-preprovisionedpv-5wcg no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-5wcg
Oct 14 09:41:16.966: INFO: Deleting pod "exec-volume-test-preprovisionedpv-5wcg" in namespace "volume-5128"
STEP: Deleting pv and pvc
Oct 14 09:41:17.170: INFO: Deleting PersistentVolumeClaim "pvc-q9l42"
Oct 14 09:41:17.377: INFO: Deleting PersistentVolume "aws-hxp28"
Oct 14 09:41:17.938: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-07a2134d7d572fa51", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07a2134d7d572fa51 is currently attached to i-057009a9735869b54
	status code: 400, request id: cbc82429-9c87-4386-9f15-fd1e944ad40f
Oct 14 09:41:23.957: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-07a2134d7d572fa51", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07a2134d7d572fa51 is currently attached to i-057009a9735869b54
	status code: 400, request id: ad273fe6-f3e2-41af-b740-b41d259c2cfb
Oct 14 09:41:29.869: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-07a2134d7d572fa51", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07a2134d7d572fa51 is currently attached to i-057009a9735869b54
	status code: 400, request id: 85e620f9-04a6-455c-9ab7-ddefe0280976
Oct 14 09:41:35.819: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-07a2134d7d572fa51", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-07a2134d7d572fa51 is currently attached to i-057009a9735869b54
	status code: 400, request id: 8530b131-7cef-4ee5-a2fc-9b133a49c55d
Oct 14 09:41:41.817: INFO: Successfully deleted PD "aws://ap-southeast-1a/vol-07a2134d7d572fa51".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 14 09:41:41.817: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-5128" for this suite.
... skipping 94 lines ...
Oct 14 09:41:43.685: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.h4kFCENj0/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.h4kFCENj0/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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 12 lines ...
Oct 14 09:40:56.403: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8144xwjlc
STEP: creating a claim
Oct 14 09:40:56.608: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-s7lk
STEP: Creating a pod to test atomic-volume-subpath
Oct 14 09:40:57.229: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-s7lk" in namespace "provisioning-8144" to be "Succeeded or Failed"
Oct 14 09:40:57.435: INFO: Pod "pod-subpath-test-dynamicpv-s7lk": Phase="Pending", Reason="", readiness=false. Elapsed: 206.102271ms
Oct 14 09:40:59.640: INFO: Pod "pod-subpath-test-dynamicpv-s7lk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.410944301s
Oct 14 09:41:01.845: INFO: Pod "pod-subpath-test-dynamicpv-s7lk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.615789252s
Oct 14 09:41:04.053: INFO: Pod "pod-subpath-test-dynamicpv-s7lk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.823822553s
Oct 14 09:41:06.258: INFO: Pod "pod-subpath-test-dynamicpv-s7lk": Phase="Pending", Reason="", readiness=false. Elapsed: 9.02933637s
Oct 14 09:41:08.472: INFO: Pod "pod-subpath-test-dynamicpv-s7lk": Phase="Pending", Reason="", readiness=false. Elapsed: 11.24298663s
... skipping 8 lines ...
Oct 14 09:41:28.318: INFO: Pod "pod-subpath-test-dynamicpv-s7lk": Phase="Running", Reason="", readiness=true. Elapsed: 31.088526654s
Oct 14 09:41:30.522: INFO: Pod "pod-subpath-test-dynamicpv-s7lk": Phase="Running", Reason="", readiness=true. Elapsed: 33.293230702s
Oct 14 09:41:32.727: INFO: Pod "pod-subpath-test-dynamicpv-s7lk": Phase="Running", Reason="", readiness=true. Elapsed: 35.49758888s
Oct 14 09:41:34.931: INFO: Pod "pod-subpath-test-dynamicpv-s7lk": Phase="Running", Reason="", readiness=true. Elapsed: 37.702291753s
Oct 14 09:41:37.136: INFO: Pod "pod-subpath-test-dynamicpv-s7lk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 39.906687954s
STEP: Saw pod success
Oct 14 09:41:37.136: INFO: Pod "pod-subpath-test-dynamicpv-s7lk" satisfied condition "Succeeded or Failed"
Oct 14 09:41:37.340: INFO: Trying to get logs from node ip-172-20-33-219.ap-southeast-1.compute.internal pod pod-subpath-test-dynamicpv-s7lk container test-container-subpath-dynamicpv-s7lk: <nil>
STEP: delete the pod
Oct 14 09:41:37.765: INFO: Waiting for pod pod-subpath-test-dynamicpv-s7lk to disappear
Oct 14 09:41:37.970: INFO: Pod pod-subpath-test-dynamicpv-s7lk no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-s7lk
Oct 14 09:41:37.970: INFO: Deleting pod "pod-subpath-test-dynamicpv-s7lk" in namespace "provisioning-8144"
... skipping 208 lines ...
Oct 14 09:40:56.377: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9625-e2e-scbndsn
STEP: creating a claim
Oct 14 09:40:56.581: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-hfnb
STEP: Creating a pod to test subpath
Oct 14 09:40:57.198: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-hfnb" in namespace "provisioning-9625" to be "Succeeded or Failed"
Oct 14 09:40:57.425: INFO: Pod "pod-subpath-test-dynamicpv-hfnb": Phase="Pending", Reason="", readiness=false. Elapsed: 227.049108ms
Oct 14 09:40:59.629: INFO: Pod "pod-subpath-test-dynamicpv-hfnb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.430896411s
Oct 14 09:41:01.834: INFO: Pod "pod-subpath-test-dynamicpv-hfnb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.635712564s
Oct 14 09:41:04.052: INFO: Pod "pod-subpath-test-dynamicpv-hfnb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.854136663s
Oct 14 09:41:06.257: INFO: Pod "pod-subpath-test-dynamicpv-hfnb": Phase="Pending", Reason="", readiness=false. Elapsed: 9.059061019s
Oct 14 09:41:08.472: INFO: Pod "pod-subpath-test-dynamicpv-hfnb": Phase="Pending", Reason="", readiness=false. Elapsed: 11.273905382s
Oct 14 09:41:10.677: INFO: Pod "pod-subpath-test-dynamicpv-hfnb": Phase="Pending", Reason="", readiness=false. Elapsed: 13.478246542s
Oct 14 09:41:12.881: INFO: Pod "pod-subpath-test-dynamicpv-hfnb": Phase="Pending", Reason="", readiness=false. Elapsed: 15.682898914s
Oct 14 09:41:15.085: INFO: Pod "pod-subpath-test-dynamicpv-hfnb": Phase="Pending", Reason="", readiness=false. Elapsed: 17.886768756s
Oct 14 09:41:17.290: INFO: Pod "pod-subpath-test-dynamicpv-hfnb": Phase="Pending", Reason="", readiness=false. Elapsed: 20.091254616s
Oct 14 09:41:19.494: INFO: Pod "pod-subpath-test-dynamicpv-hfnb": Phase="Pending", Reason="", readiness=false. Elapsed: 22.29565938s
Oct 14 09:41:21.699: INFO: Pod "pod-subpath-test-dynamicpv-hfnb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.500453403s
STEP: Saw pod success
Oct 14 09:41:21.699: INFO: Pod "pod-subpath-test-dynamicpv-hfnb" satisfied condition "Succeeded or Failed"
Oct 14 09:41:21.903: INFO: Trying to get logs from node ip-172-20-33-219.ap-southeast-1.compute.internal pod pod-subpath-test-dynamicpv-hfnb container test-container-subpath-dynamicpv-hfnb: <nil>
STEP: delete the pod
Oct 14 09:41:22.322: INFO: Waiting for pod pod-subpath-test-dynamicpv-hfnb to disappear
Oct 14 09:41:22.525: INFO: Pod pod-subpath-test-dynamicpv-hfnb no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-hfnb
Oct 14 09:41:22.525: INFO: Deleting pod "pod-subpath-test-dynamicpv-hfnb" in namespace "provisioning-9625"
... skipping 121 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.h4kFCENj0/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.h4kFCENj0/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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 12 lines ...
Oct 14 09:41:16.882: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-5669s5ncr
STEP: creating a claim
Oct 14 09:41:17.086: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-dwsp
STEP: Creating a pod to test exec-volume-test
Oct 14 09:41:17.700: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-dwsp" in namespace "volume-5669" to be "Succeeded or Failed"
Oct 14 09:41:17.907: INFO: Pod "exec-volume-test-dynamicpv-dwsp": Phase="Pending", Reason="", readiness=false. Elapsed: 206.49302ms
Oct 14 09:41:20.111: INFO: Pod "exec-volume-test-dynamicpv-dwsp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.410644072s
Oct 14 09:41:22.316: INFO: Pod "exec-volume-test-dynamicpv-dwsp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.615525181s
Oct 14 09:41:24.518: INFO: Pod "exec-volume-test-dynamicpv-dwsp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.81820747s
Oct 14 09:41:26.721: INFO: Pod "exec-volume-test-dynamicpv-dwsp": Phase="Pending", Reason="", readiness=false. Elapsed: 9.021063745s
Oct 14 09:41:28.924: INFO: Pod "exec-volume-test-dynamicpv-dwsp": Phase="Pending", Reason="", readiness=false. Elapsed: 11.223676477s
Oct 14 09:41:31.126: INFO: Pod "exec-volume-test-dynamicpv-dwsp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 13.426038271s
STEP: Saw pod success
Oct 14 09:41:31.126: INFO: Pod "exec-volume-test-dynamicpv-dwsp" satisfied condition "Succeeded or Failed"
Oct 14 09:41:31.328: INFO: Trying to get logs from node ip-172-20-33-219.ap-southeast-1.compute.internal pod exec-volume-test-dynamicpv-dwsp container exec-container-dynamicpv-dwsp: <nil>
STEP: delete the pod
Oct 14 09:41:31.738: INFO: Waiting for pod exec-volume-test-dynamicpv-dwsp to disappear
Oct 14 09:41:31.944: INFO: Pod exec-volume-test-dynamicpv-dwsp no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-dwsp
Oct 14 09:41:31.944: INFO: Deleting pod "exec-volume-test-dynamicpv-dwsp" in namespace "volume-5669"
... skipping 132 lines ...
Oct 14 09:41:18.664: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7825w58kl
STEP: creating a claim
Oct 14 09:41:18.865: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-ws9g
STEP: Creating a pod to test subpath
Oct 14 09:41:19.476: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-ws9g" in namespace "provisioning-7825" to be "Succeeded or Failed"
Oct 14 09:41:19.677: INFO: Pod "pod-subpath-test-dynamicpv-ws9g": Phase="Pending", Reason="", readiness=false. Elapsed: 201.528125ms
Oct 14 09:41:21.880: INFO: Pod "pod-subpath-test-dynamicpv-ws9g": Phase="Pending", Reason="", readiness=false. Elapsed: 2.403593358s
Oct 14 09:41:24.086: INFO: Pod "pod-subpath-test-dynamicpv-ws9g": Phase="Pending", Reason="", readiness=false. Elapsed: 4.610318464s
Oct 14 09:41:26.288: INFO: Pod "pod-subpath-test-dynamicpv-ws9g": Phase="Pending", Reason="", readiness=false. Elapsed: 6.812111835s
Oct 14 09:41:28.492: INFO: Pod "pod-subpath-test-dynamicpv-ws9g": Phase="Pending", Reason="", readiness=false. Elapsed: 9.01566039s
Oct 14 09:41:30.694: INFO: Pod "pod-subpath-test-dynamicpv-ws9g": Phase="Pending", Reason="", readiness=false. Elapsed: 11.218119328s
Oct 14 09:41:32.897: INFO: Pod "pod-subpath-test-dynamicpv-ws9g": Phase="Pending", Reason="", readiness=false. Elapsed: 13.420675681s
Oct 14 09:41:35.098: INFO: Pod "pod-subpath-test-dynamicpv-ws9g": Phase="Succeeded", Reason="", readiness=false. Elapsed: 15.622534482s
STEP: Saw pod success
Oct 14 09:41:35.099: INFO: Pod "pod-subpath-test-dynamicpv-ws9g" satisfied condition "Succeeded or Failed"
Oct 14 09:41:35.300: INFO: Trying to get logs from node ip-172-20-37-167.ap-southeast-1.compute.internal pod pod-subpath-test-dynamicpv-ws9g container test-container-volume-dynamicpv-ws9g: <nil>
STEP: delete the pod
Oct 14 09:41:35.712: INFO: Waiting for pod pod-subpath-test-dynamicpv-ws9g to disappear
Oct 14 09:41:35.913: INFO: Pod pod-subpath-test-dynamicpv-ws9g no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-ws9g
Oct 14 09:41:35.913: INFO: Deleting pod "pod-subpath-test-dynamicpv-ws9g" in namespace "provisioning-7825"
... skipping 154 lines ...
Oct 14 09:41:57.633: INFO: Waiting for pod aws-client to disappear
Oct 14 09:41:57.830: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Oct 14 09:41:57.830: INFO: Deleting PersistentVolumeClaim "pvc-mmqpb"
Oct 14 09:41:58.028: INFO: Deleting PersistentVolume "aws-4nr46"
Oct 14 09:41:59.163: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-00a72b9e3963e6a21", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-00a72b9e3963e6a21 is currently attached to i-02f264506a5f6d293
	status code: 400, request id: b0c09279-c403-4bf0-ad53-fc399d1f6233
Oct 14 09:42:05.121: INFO: Successfully deleted PD "aws://ap-southeast-1a/vol-00a72b9e3963e6a21".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 14 09:42:05.121: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-251" for this suite.
... skipping 224 lines ...
Oct 14 09:41:03.667: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8355-e2e-sc8jpk5
STEP: creating a claim
Oct 14 09:41:03.874: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-dgbv
STEP: Creating a pod to test subpath
Oct 14 09:41:04.497: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-dgbv" in namespace "provisioning-8355" to be "Succeeded or Failed"
Oct 14 09:41:04.703: INFO: Pod "pod-subpath-test-dynamicpv-dgbv": Phase="Pending", Reason="", readiness=false. Elapsed: 206.314292ms
Oct 14 09:41:06.911: INFO: Pod "pod-subpath-test-dynamicpv-dgbv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.41342459s
Oct 14 09:41:09.117: INFO: Pod "pod-subpath-test-dynamicpv-dgbv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.620213971s
Oct 14 09:41:11.325: INFO: Pod "pod-subpath-test-dynamicpv-dgbv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.827698105s
Oct 14 09:41:13.532: INFO: Pod "pod-subpath-test-dynamicpv-dgbv": Phase="Pending", Reason="", readiness=false. Elapsed: 9.03445477s
Oct 14 09:41:15.739: INFO: Pod "pod-subpath-test-dynamicpv-dgbv": Phase="Pending", Reason="", readiness=false. Elapsed: 11.241416441s
... skipping 3 lines ...
Oct 14 09:41:24.577: INFO: Pod "pod-subpath-test-dynamicpv-dgbv": Phase="Pending", Reason="", readiness=false. Elapsed: 20.080200807s
Oct 14 09:41:26.784: INFO: Pod "pod-subpath-test-dynamicpv-dgbv": Phase="Pending", Reason="", readiness=false. Elapsed: 22.286705693s
Oct 14 09:41:28.990: INFO: Pod "pod-subpath-test-dynamicpv-dgbv": Phase="Pending", Reason="", readiness=false. Elapsed: 24.493205722s
Oct 14 09:41:31.197: INFO: Pod "pod-subpath-test-dynamicpv-dgbv": Phase="Pending", Reason="", readiness=false. Elapsed: 26.700010602s
Oct 14 09:41:33.405: INFO: Pod "pod-subpath-test-dynamicpv-dgbv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 28.907708881s
STEP: Saw pod success
Oct 14 09:41:33.405: INFO: Pod "pod-subpath-test-dynamicpv-dgbv" satisfied condition "Succeeded or Failed"
Oct 14 09:41:33.611: INFO: Trying to get logs from node ip-172-20-47-2.ap-southeast-1.compute.internal pod pod-subpath-test-dynamicpv-dgbv container test-container-volume-dynamicpv-dgbv: <nil>
STEP: delete the pod
Oct 14 09:41:34.032: INFO: Waiting for pod pod-subpath-test-dynamicpv-dgbv to disappear
Oct 14 09:41:34.240: INFO: Pod pod-subpath-test-dynamicpv-dgbv no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-dgbv
Oct 14 09:41:34.240: INFO: Deleting pod "pod-subpath-test-dynamicpv-dgbv" in namespace "provisioning-8355"
... skipping 165 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.h4kFCENj0/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.h4kFCENj0/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.h4kFCENj0/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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Distro debian doesn't support ntfs -- skipping

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

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 252 lines ...
Oct 14 09:41:50.116: INFO: PersistentVolumeClaim pvc-8z7t6 found but phase is Pending instead of Bound.
Oct 14 09:41:52.323: INFO: PersistentVolumeClaim pvc-8z7t6 found and phase=Bound (13.448489557s)
Oct 14 09:41:52.323: INFO: Waiting up to 3m0s for PersistentVolume aws-gh2s6 to have phase Bound
Oct 14 09:41:52.529: INFO: PersistentVolume aws-gh2s6 found and phase=Bound (206.496857ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-rggl
STEP: Creating a pod to test exec-volume-test
Oct 14 09:41:53.150: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-rggl" in namespace "volume-3859" to be "Succeeded or Failed"
Oct 14 09:41:53.358: INFO: Pod "exec-volume-test-preprovisionedpv-rggl": Phase="Pending", Reason="", readiness=false. Elapsed: 207.937417ms
Oct 14 09:41:55.566: INFO: Pod "exec-volume-test-preprovisionedpv-rggl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.41606922s
Oct 14 09:41:57.773: INFO: Pod "exec-volume-test-preprovisionedpv-rggl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.623683383s
Oct 14 09:41:59.980: INFO: Pod "exec-volume-test-preprovisionedpv-rggl": Phase="Pending", Reason="", readiness=false. Elapsed: 6.8304268s
Oct 14 09:42:02.188: INFO: Pod "exec-volume-test-preprovisionedpv-rggl": Phase="Pending", Reason="", readiness=false. Elapsed: 9.038802955s
Oct 14 09:42:04.395: INFO: Pod "exec-volume-test-preprovisionedpv-rggl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 11.245783425s
STEP: Saw pod success
Oct 14 09:42:04.395: INFO: Pod "exec-volume-test-preprovisionedpv-rggl" satisfied condition "Succeeded or Failed"
Oct 14 09:42:04.602: INFO: Trying to get logs from node ip-172-20-47-2.ap-southeast-1.compute.internal pod exec-volume-test-preprovisionedpv-rggl container exec-container-preprovisionedpv-rggl: <nil>
STEP: delete the pod
Oct 14 09:42:05.026: INFO: Waiting for pod exec-volume-test-preprovisionedpv-rggl to disappear
Oct 14 09:42:05.233: INFO: Pod exec-volume-test-preprovisionedpv-rggl no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-rggl
Oct 14 09:42:05.233: INFO: Deleting pod "exec-volume-test-preprovisionedpv-rggl" in namespace "volume-3859"
STEP: Deleting pv and pvc
Oct 14 09:42:05.439: INFO: Deleting PersistentVolumeClaim "pvc-8z7t6"
Oct 14 09:42:05.651: INFO: Deleting PersistentVolume "aws-gh2s6"
Oct 14 09:42:06.210: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-0f320589e53b76372", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f320589e53b76372 is currently attached to i-0053439ffca389c81
	status code: 400, request id: d3955684-3384-4374-aa1c-4773fc7a8645
Oct 14 09:42:12.204: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-0f320589e53b76372", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f320589e53b76372 is currently attached to i-0053439ffca389c81
	status code: 400, request id: e0d6006b-65fb-40aa-87a0-5ec3994b0cff
Oct 14 09:42:18.205: INFO: Successfully deleted PD "aws://ap-southeast-1a/vol-0f320589e53b76372".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 14 09:42:18.205: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-3859" for this suite.
... skipping 24 lines ...
Oct 14 09:41:24.268: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4867fghj7
STEP: creating a claim
Oct 14 09:41:24.474: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-gwpn
STEP: Creating a pod to test subpath
Oct 14 09:41:25.093: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-gwpn" in namespace "provisioning-4867" to be "Succeeded or Failed"
Oct 14 09:41:25.300: INFO: Pod "pod-subpath-test-dynamicpv-gwpn": Phase="Pending", Reason="", readiness=false. Elapsed: 206.725314ms
Oct 14 09:41:27.541: INFO: Pod "pod-subpath-test-dynamicpv-gwpn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.447471135s
Oct 14 09:41:29.748: INFO: Pod "pod-subpath-test-dynamicpv-gwpn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.654086282s
Oct 14 09:41:31.954: INFO: Pod "pod-subpath-test-dynamicpv-gwpn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.860479053s
Oct 14 09:41:34.160: INFO: Pod "pod-subpath-test-dynamicpv-gwpn": Phase="Pending", Reason="", readiness=false. Elapsed: 9.066337804s
Oct 14 09:41:36.372: INFO: Pod "pod-subpath-test-dynamicpv-gwpn": Phase="Pending", Reason="", readiness=false. Elapsed: 11.27892924s
... skipping 9 lines ...
Oct 14 09:41:58.436: INFO: Pod "pod-subpath-test-dynamicpv-gwpn": Phase="Pending", Reason="", readiness=false. Elapsed: 33.342811526s
Oct 14 09:42:00.642: INFO: Pod "pod-subpath-test-dynamicpv-gwpn": Phase="Pending", Reason="", readiness=false. Elapsed: 35.548405591s
Oct 14 09:42:02.848: INFO: Pod "pod-subpath-test-dynamicpv-gwpn": Phase="Pending", Reason="", readiness=false. Elapsed: 37.754489717s
Oct 14 09:42:05.055: INFO: Pod "pod-subpath-test-dynamicpv-gwpn": Phase="Pending", Reason="", readiness=false. Elapsed: 39.961324943s
Oct 14 09:42:07.261: INFO: Pod "pod-subpath-test-dynamicpv-gwpn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 42.167175803s
STEP: Saw pod success
Oct 14 09:42:07.261: INFO: Pod "pod-subpath-test-dynamicpv-gwpn" satisfied condition "Succeeded or Failed"
Oct 14 09:42:07.466: INFO: Trying to get logs from node ip-172-20-47-16.ap-southeast-1.compute.internal pod pod-subpath-test-dynamicpv-gwpn container test-container-volume-dynamicpv-gwpn: <nil>
STEP: delete the pod
Oct 14 09:42:07.889: INFO: Waiting for pod pod-subpath-test-dynamicpv-gwpn to disappear
Oct 14 09:42:08.094: INFO: Pod pod-subpath-test-dynamicpv-gwpn no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-gwpn
Oct 14 09:42:08.094: INFO: Deleting pod "pod-subpath-test-dynamicpv-gwpn" in namespace "provisioning-4867"
... skipping 68 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 14 09:42:05.165: 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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Oct 14 09:42:06.175: INFO: Creating resource for dynamic PV
Oct 14 09:42:06.175: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-3392-e2e-sc8n9ft
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Oct 14 09:42:11.595: INFO: Deleting pod "pod-eca07f57-34f4-487c-ab72-2dc6299280ff" in namespace "volumemode-3392"
Oct 14 09:42:11.798: INFO: Wait up to 5m0s for pod "pod-eca07f57-34f4-487c-ab72-2dc6299280ff" to be fully deleted
STEP: Deleting pvc
Oct 14 09:42:14.605: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comldkwz"
Oct 14 09:42:14.811: INFO: Waiting up to 5m0s for PersistentVolume pvc-a8e1d836-5205-4b65-b70d-3549a358b4a8 to get deleted
Oct 14 09:42:15.014: INFO: PersistentVolume pvc-a8e1d836-5205-4b65-b70d-3549a358b4a8 found and phase=Released (202.442192ms)
... skipping 8 lines ...

• [SLOW TEST:20.861 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.h4kFCENj0/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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 417 lines ...
Oct 14 09:42:18.934: INFO: Pod aws-client still exists
Oct 14 09:42:20.934: INFO: Waiting for pod aws-client to disappear
Oct 14 09:42:21.147: INFO: Pod aws-client still exists
Oct 14 09:42:22.935: INFO: Waiting for pod aws-client to disappear
Oct 14 09:42:23.146: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Oct 14 09:42:23.509: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-0e7b5226e0cdd0848", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e7b5226e0cdd0848 is currently attached to i-02f264506a5f6d293
	status code: 400, request id: 2e353ca1-fc13-44d8-9cbe-0fe8c8c2adb6
Oct 14 09:42:29.446: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-0e7b5226e0cdd0848", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e7b5226e0cdd0848 is currently attached to i-02f264506a5f6d293
	status code: 400, request id: 3bc38e86-cbfc-4ca2-ba9a-e1ebf77306ba
Oct 14 09:42:35.389: INFO: Successfully deleted PD "aws://ap-southeast-1a/vol-0e7b5226e0cdd0848".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 14 09:42:35.389: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-9384" for this suite.
... skipping 285 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.h4kFCENj0/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.h4kFCENj0/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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 11 lines ...
Oct 14 09:41:48.597: INFO: Creating resource for dynamic PV
Oct 14 09:41:48.597: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-54819gl8g
STEP: creating a claim
Oct 14 09:41:48.807: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-5481
Oct 14 09:41:49.399: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-5481" in namespace "provisioning-5481" to be "Succeeded or Failed"
Oct 14 09:41:49.595: INFO: Pod "volume-prep-provisioning-5481": Phase="Pending", Reason="", readiness=false. Elapsed: 196.318094ms
Oct 14 09:41:51.792: INFO: Pod "volume-prep-provisioning-5481": Phase="Pending", Reason="", readiness=false. Elapsed: 2.392672085s
Oct 14 09:41:53.989: INFO: Pod "volume-prep-provisioning-5481": Phase="Pending", Reason="", readiness=false. Elapsed: 4.589862848s
Oct 14 09:41:56.185: INFO: Pod "volume-prep-provisioning-5481": Phase="Pending", Reason="", readiness=false. Elapsed: 6.785945254s
Oct 14 09:41:58.382: INFO: Pod "volume-prep-provisioning-5481": Phase="Pending", Reason="", readiness=false. Elapsed: 8.982651238s
Oct 14 09:42:00.578: INFO: Pod "volume-prep-provisioning-5481": Phase="Pending", Reason="", readiness=false. Elapsed: 11.179008133s
Oct 14 09:42:02.795: INFO: Pod "volume-prep-provisioning-5481": Phase="Pending", Reason="", readiness=false. Elapsed: 13.395802927s
Oct 14 09:42:04.994: INFO: Pod "volume-prep-provisioning-5481": Phase="Succeeded", Reason="", readiness=false. Elapsed: 15.594916237s
STEP: Saw pod success
Oct 14 09:42:04.994: INFO: Pod "volume-prep-provisioning-5481" satisfied condition "Succeeded or Failed"
Oct 14 09:42:04.994: INFO: Deleting pod "volume-prep-provisioning-5481" in namespace "provisioning-5481"
Oct 14 09:42:05.201: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-5481" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-pzbn
STEP: Checking for subpath error in container status
Oct 14 09:42:13.995: INFO: Deleting pod "pod-subpath-test-dynamicpv-pzbn" in namespace "provisioning-5481"
Oct 14 09:42:14.195: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-pzbn" to be fully deleted
STEP: Deleting pod
Oct 14 09:42:14.391: INFO: Deleting pod "pod-subpath-test-dynamicpv-pzbn" in namespace "provisioning-5481"
STEP: Deleting pvc
Oct 14 09:42:14.979: INFO: Deleting PersistentVolumeClaim "awsjf57t"
... skipping 180 lines ...

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

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

    /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 167 lines ...
Oct 14 09:42:05.683: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-3074dlrqk
STEP: creating a claim
Oct 14 09:42:05.882: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-jzlw
STEP: Creating a pod to test exec-volume-test
Oct 14 09:42:06.479: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-jzlw" in namespace "volume-3074" to be "Succeeded or Failed"
Oct 14 09:42:06.676: INFO: Pod "exec-volume-test-dynamicpv-jzlw": Phase="Pending", Reason="", readiness=false. Elapsed: 196.516864ms
Oct 14 09:42:08.876: INFO: Pod "exec-volume-test-dynamicpv-jzlw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.39675057s
Oct 14 09:42:11.073: INFO: Pod "exec-volume-test-dynamicpv-jzlw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.593951875s
Oct 14 09:42:13.270: INFO: Pod "exec-volume-test-dynamicpv-jzlw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.790988549s
Oct 14 09:42:15.467: INFO: Pod "exec-volume-test-dynamicpv-jzlw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.987922911s
Oct 14 09:42:17.665: INFO: Pod "exec-volume-test-dynamicpv-jzlw": Phase="Pending", Reason="", readiness=false. Elapsed: 11.185545495s
Oct 14 09:42:19.863: INFO: Pod "exec-volume-test-dynamicpv-jzlw": Phase="Pending", Reason="", readiness=false. Elapsed: 13.383471578s
Oct 14 09:42:22.083: INFO: Pod "exec-volume-test-dynamicpv-jzlw": Phase="Pending", Reason="", readiness=false. Elapsed: 15.603277176s
Oct 14 09:42:24.280: INFO: Pod "exec-volume-test-dynamicpv-jzlw": Phase="Pending", Reason="", readiness=false. Elapsed: 17.800812497s
Oct 14 09:42:26.480: INFO: Pod "exec-volume-test-dynamicpv-jzlw": Phase="Pending", Reason="", readiness=false. Elapsed: 20.000559722s
Oct 14 09:42:28.677: INFO: Pod "exec-volume-test-dynamicpv-jzlw": Phase="Pending", Reason="", readiness=false. Elapsed: 22.198099658s
Oct 14 09:42:30.875: INFO: Pod "exec-volume-test-dynamicpv-jzlw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.395470019s
STEP: Saw pod success
Oct 14 09:42:30.875: INFO: Pod "exec-volume-test-dynamicpv-jzlw" satisfied condition "Succeeded or Failed"
Oct 14 09:42:31.071: INFO: Trying to get logs from node ip-172-20-37-167.ap-southeast-1.compute.internal pod exec-volume-test-dynamicpv-jzlw container exec-container-dynamicpv-jzlw: <nil>
STEP: delete the pod
Oct 14 09:42:31.477: INFO: Waiting for pod exec-volume-test-dynamicpv-jzlw to disappear
Oct 14 09:42:31.674: INFO: Pod exec-volume-test-dynamicpv-jzlw no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-jzlw
Oct 14 09:42:31.674: INFO: Deleting pod "exec-volume-test-dynamicpv-jzlw" in namespace "volume-3074"
... skipping 254 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.h4kFCENj0/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.h4kFCENj0/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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 131 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 14 09:42:38.813: 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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Oct 14 09:42:39.869: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 14 09:42:39.869: INFO: Creating resource for dynamic PV
Oct 14 09:42:39.869: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4425pjnc6
STEP: creating a claim
Oct 14 09:42:40.080: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-sdf5
STEP: Checking for subpath error in container status
Oct 14 09:42:55.136: INFO: Deleting pod "pod-subpath-test-dynamicpv-sdf5" in namespace "provisioning-4425"
Oct 14 09:42:55.348: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-sdf5" to be fully deleted
STEP: Deleting pod
Oct 14 09:42:59.768: INFO: Deleting pod "pod-subpath-test-dynamicpv-sdf5" in namespace "provisioning-4425"
STEP: Deleting pvc
Oct 14 09:43:00.397: INFO: Deleting PersistentVolumeClaim "aws54g8m"
... skipping 12 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.h4kFCENj0/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.h4kFCENj0/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.h4kFCENj0/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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 7 lines ...
Oct 14 09:42:27.033: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7300-e2e-sc8vrv6
STEP: creating a claim
Oct 14 09:42:27.235: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-59jg
STEP: Creating a pod to test subpath
Oct 14 09:42:27.847: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-59jg" in namespace "provisioning-7300" to be "Succeeded or Failed"
Oct 14 09:42:28.048: INFO: Pod "pod-subpath-test-dynamicpv-59jg": Phase="Pending", Reason="", readiness=false. Elapsed: 200.864945ms
Oct 14 09:42:30.250: INFO: Pod "pod-subpath-test-dynamicpv-59jg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.402277848s
Oct 14 09:42:32.452: INFO: Pod "pod-subpath-test-dynamicpv-59jg": Phase="Pending", Reason="", readiness=false. Elapsed: 4.604515407s
Oct 14 09:42:34.657: INFO: Pod "pod-subpath-test-dynamicpv-59jg": Phase="Pending", Reason="", readiness=false. Elapsed: 6.809828973s
Oct 14 09:42:36.859: INFO: Pod "pod-subpath-test-dynamicpv-59jg": Phase="Pending", Reason="", readiness=false. Elapsed: 9.011507296s
Oct 14 09:42:39.061: INFO: Pod "pod-subpath-test-dynamicpv-59jg": Phase="Pending", Reason="", readiness=false. Elapsed: 11.213526876s
... skipping 2 lines ...
Oct 14 09:42:45.667: INFO: Pod "pod-subpath-test-dynamicpv-59jg": Phase="Pending", Reason="", readiness=false. Elapsed: 17.819481103s
Oct 14 09:42:47.869: INFO: Pod "pod-subpath-test-dynamicpv-59jg": Phase="Pending", Reason="", readiness=false. Elapsed: 20.021277008s
Oct 14 09:42:50.070: INFO: Pod "pod-subpath-test-dynamicpv-59jg": Phase="Pending", Reason="", readiness=false. Elapsed: 22.222885331s
Oct 14 09:42:52.272: INFO: Pod "pod-subpath-test-dynamicpv-59jg": Phase="Pending", Reason="", readiness=false. Elapsed: 24.424420758s
Oct 14 09:42:54.474: INFO: Pod "pod-subpath-test-dynamicpv-59jg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.627005017s
STEP: Saw pod success
Oct 14 09:42:54.475: INFO: Pod "pod-subpath-test-dynamicpv-59jg" satisfied condition "Succeeded or Failed"
Oct 14 09:42:54.678: INFO: Trying to get logs from node ip-172-20-33-219.ap-southeast-1.compute.internal pod pod-subpath-test-dynamicpv-59jg container test-container-subpath-dynamicpv-59jg: <nil>
STEP: delete the pod
Oct 14 09:42:55.111: INFO: Waiting for pod pod-subpath-test-dynamicpv-59jg to disappear
Oct 14 09:42:55.311: INFO: Pod pod-subpath-test-dynamicpv-59jg no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-59jg
Oct 14 09:42:55.311: INFO: Deleting pod "pod-subpath-test-dynamicpv-59jg" in namespace "provisioning-7300"
... skipping 111 lines ...
Oct 14 09:42:45.401: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-65089ttwj
STEP: creating a claim
Oct 14 09:42:45.597: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-h5rn
STEP: Creating a pod to test subpath
Oct 14 09:42:46.188: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-h5rn" in namespace "provisioning-6508" to be "Succeeded or Failed"
Oct 14 09:42:46.384: INFO: Pod "pod-subpath-test-dynamicpv-h5rn": Phase="Pending", Reason="", readiness=false. Elapsed: 196.442568ms
Oct 14 09:42:48.580: INFO: Pod "pod-subpath-test-dynamicpv-h5rn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.392047081s
Oct 14 09:42:50.775: INFO: Pod "pod-subpath-test-dynamicpv-h5rn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.587485303s
Oct 14 09:42:52.971: INFO: Pod "pod-subpath-test-dynamicpv-h5rn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.783087939s
Oct 14 09:42:55.175: INFO: Pod "pod-subpath-test-dynamicpv-h5rn": Phase="Pending", Reason="", readiness=false. Elapsed: 8.98780505s
Oct 14 09:42:57.372: INFO: Pod "pod-subpath-test-dynamicpv-h5rn": Phase="Pending", Reason="", readiness=false. Elapsed: 11.184706898s
Oct 14 09:42:59.568: INFO: Pod "pod-subpath-test-dynamicpv-h5rn": Phase="Pending", Reason="", readiness=false. Elapsed: 13.380324559s
Oct 14 09:43:01.765: INFO: Pod "pod-subpath-test-dynamicpv-h5rn": Phase="Pending", Reason="", readiness=false. Elapsed: 15.577448659s
Oct 14 09:43:03.961: INFO: Pod "pod-subpath-test-dynamicpv-h5rn": Phase="Pending", Reason="", readiness=false. Elapsed: 17.773501665s
Oct 14 09:43:06.157: INFO: Pod "pod-subpath-test-dynamicpv-h5rn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.969739688s
STEP: Saw pod success
Oct 14 09:43:06.157: INFO: Pod "pod-subpath-test-dynamicpv-h5rn" satisfied condition "Succeeded or Failed"
Oct 14 09:43:06.354: INFO: Trying to get logs from node ip-172-20-33-219.ap-southeast-1.compute.internal pod pod-subpath-test-dynamicpv-h5rn container test-container-subpath-dynamicpv-h5rn: <nil>
STEP: delete the pod
Oct 14 09:43:06.754: INFO: Waiting for pod pod-subpath-test-dynamicpv-h5rn to disappear
Oct 14 09:43:06.949: INFO: Pod pod-subpath-test-dynamicpv-h5rn no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-h5rn
Oct 14 09:43:06.949: INFO: Deleting pod "pod-subpath-test-dynamicpv-h5rn" in namespace "provisioning-6508"
... skipping 167 lines ...
Oct 14 09:41:56.626: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-1155-e2e-sc5hfjh      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-1155    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-1155-e2e-sc5hfjh,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-1155    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-1155-e2e-sc5hfjh,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-1155    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-1155-e2e-sc5hfjh,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-1155-e2e-sc5hfjh    a9dddabd-e776-492e-a706-0914bc6ff1e0 11370 0 2021-10-14 09:41:56 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-10-14 09:41:56 +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-xbs7c pvc- provisioning-1155  b9a99ad0-3a09-48e6-a075-8227ae2802cb 11386 0 2021-10-14 09:41:57 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-10-14 09:41:57 +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-1155-e2e-sc5hfjh,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-7411c650-af15-42de-8576-f8c45a5ee720 in namespace provisioning-1155
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Oct 14 09:42:12.900: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-89648" in namespace "provisioning-1155" to be "Succeeded or Failed"
Oct 14 09:42:13.103: INFO: Pod "pvc-volume-tester-writer-89648": Phase="Pending", Reason="", readiness=false. Elapsed: 203.10243ms
Oct 14 09:42:15.307: INFO: Pod "pvc-volume-tester-writer-89648": Phase="Pending", Reason="", readiness=false. Elapsed: 2.406928947s
Oct 14 09:42:17.512: INFO: Pod "pvc-volume-tester-writer-89648": Phase="Pending", Reason="", readiness=false. Elapsed: 4.611657752s
Oct 14 09:42:19.715: INFO: Pod "pvc-volume-tester-writer-89648": Phase="Pending", Reason="", readiness=false. Elapsed: 6.815172396s
Oct 14 09:42:21.923: INFO: Pod "pvc-volume-tester-writer-89648": Phase="Pending", Reason="", readiness=false. Elapsed: 9.022569204s
Oct 14 09:42:24.128: INFO: Pod "pvc-volume-tester-writer-89648": Phase="Pending", Reason="", readiness=false. Elapsed: 11.227886634s
Oct 14 09:42:26.334: INFO: Pod "pvc-volume-tester-writer-89648": Phase="Pending", Reason="", readiness=false. Elapsed: 13.433888085s
Oct 14 09:42:28.538: INFO: Pod "pvc-volume-tester-writer-89648": Phase="Pending", Reason="", readiness=false. Elapsed: 15.637509473s
Oct 14 09:42:30.741: INFO: Pod "pvc-volume-tester-writer-89648": Phase="Succeeded", Reason="", readiness=false. Elapsed: 17.841070928s
STEP: Saw pod success
Oct 14 09:42:30.741: INFO: Pod "pvc-volume-tester-writer-89648" satisfied condition "Succeeded or Failed"
Oct 14 09:42:31.495: INFO: Pod pvc-volume-tester-writer-89648 has the following logs: 
Oct 14 09:42:31.495: INFO: Deleting pod "pvc-volume-tester-writer-89648" in namespace "provisioning-1155"
Oct 14 09:42:31.704: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-89648" to be fully deleted
STEP: checking the created volume has the correct mount options, is readable and retains data on the same node "ip-172-20-47-16.ap-southeast-1.compute.internal"
Oct 14 09:42:32.523: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-xdlh9" in namespace "provisioning-1155" to be "Succeeded or Failed"
Oct 14 09:42:32.726: INFO: Pod "pvc-volume-tester-reader-xdlh9": Phase="Pending", Reason="", readiness=false. Elapsed: 203.488165ms
Oct 14 09:42:34.930: INFO: Pod "pvc-volume-tester-reader-xdlh9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.407131076s
Oct 14 09:42:37.134: INFO: Pod "pvc-volume-tester-reader-xdlh9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.611329206s
Oct 14 09:42:39.340: INFO: Pod "pvc-volume-tester-reader-xdlh9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.816917566s
Oct 14 09:42:41.546: INFO: Pod "pvc-volume-tester-reader-xdlh9": Phase="Pending", Reason="", readiness=false. Elapsed: 9.023203029s
Oct 14 09:42:43.750: INFO: Pod "pvc-volume-tester-reader-xdlh9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 11.22761918s
STEP: Saw pod success
Oct 14 09:42:43.750: INFO: Pod "pvc-volume-tester-reader-xdlh9" satisfied condition "Succeeded or Failed"
Oct 14 09:42:44.161: INFO: Pod pvc-volume-tester-reader-xdlh9 has the following logs: hello world

Oct 14 09:42:44.161: INFO: Deleting pod "pvc-volume-tester-reader-xdlh9" in namespace "provisioning-1155"
Oct 14 09:42:44.373: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-xdlh9" to be fully deleted
Oct 14 09:42:44.576: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-xbs7c] to have phase Bound
Oct 14 09:42:44.779: INFO: PersistentVolumeClaim pvc-xbs7c found and phase=Bound (203.145221ms)
... skipping 180 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 14 09:42:53.664: 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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Oct 14 09:42:54.686: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Oct 14 09:42:54.686: INFO: Creating resource for dynamic PV
Oct 14 09:42:54.686: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-3558m7r92
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Oct 14 09:43:00.123: INFO: Deleting pod "pod-238acd32-e0d0-44dc-99b1-4cf86b576ff7" in namespace "volumemode-3558"
Oct 14 09:43:00.329: INFO: Wait up to 5m0s for pod "pod-238acd32-e0d0-44dc-99b1-4cf86b576ff7" to be fully deleted
STEP: Deleting pvc
Oct 14 09:43:03.146: INFO: Deleting PersistentVolumeClaim "awsvjr8n"
Oct 14 09:43:03.352: INFO: Waiting up to 5m0s for PersistentVolume pvc-0e69177b-7b17-4203-a37c-45636468423d to get deleted
Oct 14 09:43:03.556: INFO: PersistentVolume pvc-0e69177b-7b17-4203-a37c-45636468423d found and phase=Released (203.883411ms)
... skipping 13 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.h4kFCENj0/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.h4kFCENj0/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (block volmode)] volumeMode
    /tmp/kops.h4kFCENj0/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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] provisioning
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] provisioning
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 57 lines ...
Oct 14 09:42:58.465: INFO: Creating resource for dynamic PV
Oct 14 09:42:58.465: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-4093nqrrq
STEP: creating a claim
STEP: Expanding non-expandable pvc
Oct 14 09:42:59.057: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Oct 14 09:42:59.452: INFO: Error updating pvc awsfqrn5: PersistentVolumeClaim "awsfqrn5" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-4093nqrrq",
  	... // 3 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 54 lines ...
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 14 09:43:31.084: 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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Oct 14 09:43:32.266: INFO: found topology map[topology.ebs.csi.aws.com/zone:ap-southeast-1a]
Oct 14 09:43:32.267: 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.778 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.h4kFCENj0/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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

    Not enough topologies in cluster -- skipping

    /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 500 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 14 09:42:44.389: 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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Oct 14 09:42:45.387: INFO: Creating resource for dynamic PV
Oct 14 09:42:45.387: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1921-e2e-sccpscs
STEP: creating a claim
Oct 14 09:42:45.589: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-6cz8
STEP: Checking for subpath error in container status
Oct 14 09:43:02.597: INFO: Deleting pod "pod-subpath-test-dynamicpv-6cz8" in namespace "provisioning-1921"
Oct 14 09:43:02.810: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-6cz8" to be fully deleted
STEP: Deleting pod
Oct 14 09:43:05.210: INFO: Deleting pod "pod-subpath-test-dynamicpv-6cz8" in namespace "provisioning-1921"
STEP: Deleting pvc
Oct 14 09:43:05.806: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comgtlf6"
... skipping 15 lines ...

• [SLOW TEST:58.821 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath directory is outside the volume [Slow][LinuxOnly]
    /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Oct 14 09:43:43.212: INFO: Driver ebs.csi.aws.com doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning
... skipping 17 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 14 09:43:30.213: 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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Oct 14 09:43:31.239: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Oct 14 09:43:32.395: INFO: Successfully created a new PD: "aws://ap-southeast-1a/vol-083bc1cc41a39ef6a".
Oct 14 09:43:32.395: INFO: Creating resource for pre-provisioned PV
Oct 14 09:43:32.395: INFO: Creating PVC and PV
... skipping 3 lines ...
Oct 14 09:43:33.009: INFO: PersistentVolumeClaim pvc-9qm24 found but phase is Pending instead of Bound.
Oct 14 09:43:35.214: INFO: PersistentVolumeClaim pvc-9qm24 found but phase is Pending instead of Bound.
Oct 14 09:43:37.419: INFO: PersistentVolumeClaim pvc-9qm24 found and phase=Bound (4.613573147s)
Oct 14 09:43:37.419: INFO: Waiting up to 3m0s for PersistentVolume aws-7rvsz to have phase Bound
Oct 14 09:43:37.623: INFO: PersistentVolume aws-7rvsz found and phase=Bound (203.985069ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Oct 14 09:43:40.853: INFO: Deleting pod "pod-abfd482e-ac7b-474f-9bb5-9c6b8ce8c910" in namespace "volumemode-2847"
Oct 14 09:43:41.060: INFO: Wait up to 5m0s for pod "pod-abfd482e-ac7b-474f-9bb5-9c6b8ce8c910" to be fully deleted
STEP: Deleting pv and pvc
Oct 14 09:43:43.468: INFO: Deleting PersistentVolumeClaim "pvc-9qm24"
Oct 14 09:43:43.674: INFO: Deleting PersistentVolume "aws-7rvsz"
Oct 14 09:43:44.226: INFO: Successfully deleted PD "aws://ap-southeast-1a/vol-083bc1cc41a39ef6a".
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.h4kFCENj0/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.h4kFCENj0/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
    /tmp/kops.h4kFCENj0/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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [sig-storage] Zone Support [Feature:vsphere]
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 14 09:43:44.638: INFO: >>> kubeConfig: /root/.kube/config
... skipping 241 lines ...

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

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

    /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 77 lines ...
Oct 14 09:42:26.618: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5383tclkw
STEP: creating a claim
Oct 14 09:42:26.824: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-j96h
STEP: Creating a pod to test subpath
Oct 14 09:42:27.447: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-j96h" in namespace "provisioning-5383" to be "Succeeded or Failed"
Oct 14 09:42:27.652: INFO: Pod "pod-subpath-test-dynamicpv-j96h": Phase="Pending", Reason="", readiness=false. Elapsed: 205.659263ms
Oct 14 09:42:29.858: INFO: Pod "pod-subpath-test-dynamicpv-j96h": Phase="Pending", Reason="", readiness=false. Elapsed: 2.411283284s
Oct 14 09:42:32.063: INFO: Pod "pod-subpath-test-dynamicpv-j96h": Phase="Pending", Reason="", readiness=false. Elapsed: 4.616779089s
Oct 14 09:42:34.271: INFO: Pod "pod-subpath-test-dynamicpv-j96h": Phase="Pending", Reason="", readiness=false. Elapsed: 6.823901559s
Oct 14 09:42:36.480: INFO: Pod "pod-subpath-test-dynamicpv-j96h": Phase="Pending", Reason="", readiness=false. Elapsed: 9.033674856s
Oct 14 09:42:38.686: INFO: Pod "pod-subpath-test-dynamicpv-j96h": Phase="Pending", Reason="", readiness=false. Elapsed: 11.23958579s
... skipping 2 lines ...
Oct 14 09:42:45.306: INFO: Pod "pod-subpath-test-dynamicpv-j96h": Phase="Pending", Reason="", readiness=false. Elapsed: 17.859612661s
Oct 14 09:42:47.512: INFO: Pod "pod-subpath-test-dynamicpv-j96h": Phase="Pending", Reason="", readiness=false. Elapsed: 20.065592509s
Oct 14 09:42:49.720: INFO: Pod "pod-subpath-test-dynamicpv-j96h": Phase="Pending", Reason="", readiness=false. Elapsed: 22.273251947s
Oct 14 09:42:51.926: INFO: Pod "pod-subpath-test-dynamicpv-j96h": Phase="Pending", Reason="", readiness=false. Elapsed: 24.479323894s
Oct 14 09:42:54.133: INFO: Pod "pod-subpath-test-dynamicpv-j96h": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.686609522s
STEP: Saw pod success
Oct 14 09:42:54.133: INFO: Pod "pod-subpath-test-dynamicpv-j96h" satisfied condition "Succeeded or Failed"
Oct 14 09:42:54.339: INFO: Trying to get logs from node ip-172-20-33-219.ap-southeast-1.compute.internal pod pod-subpath-test-dynamicpv-j96h container test-container-subpath-dynamicpv-j96h: <nil>
STEP: delete the pod
Oct 14 09:42:55.018: INFO: Waiting for pod pod-subpath-test-dynamicpv-j96h to disappear
Oct 14 09:42:55.224: INFO: Pod pod-subpath-test-dynamicpv-j96h no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-j96h
Oct 14 09:42:55.224: INFO: Deleting pod "pod-subpath-test-dynamicpv-j96h" in namespace "provisioning-5383"
STEP: Creating pod pod-subpath-test-dynamicpv-j96h
STEP: Creating a pod to test subpath
Oct 14 09:42:55.636: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-j96h" in namespace "provisioning-5383" to be "Succeeded or Failed"
Oct 14 09:42:55.842: INFO: Pod "pod-subpath-test-dynamicpv-j96h": Phase="Pending", Reason="", readiness=false. Elapsed: 205.853775ms
Oct 14 09:42:58.058: INFO: Pod "pod-subpath-test-dynamicpv-j96h": Phase="Pending", Reason="", readiness=false. Elapsed: 2.421630381s
Oct 14 09:43:00.264: INFO: Pod "pod-subpath-test-dynamicpv-j96h": Phase="Pending", Reason="", readiness=false. Elapsed: 4.627774528s
Oct 14 09:43:02.470: INFO: Pod "pod-subpath-test-dynamicpv-j96h": Phase="Pending", Reason="", readiness=false. Elapsed: 6.833700261s
Oct 14 09:43:04.676: INFO: Pod "pod-subpath-test-dynamicpv-j96h": Phase="Pending", Reason="", readiness=false. Elapsed: 9.040078227s
Oct 14 09:43:06.885: INFO: Pod "pod-subpath-test-dynamicpv-j96h": Phase="Pending", Reason="", readiness=false. Elapsed: 11.249336856s
... skipping 6 lines ...
Oct 14 09:43:22.329: INFO: Pod "pod-subpath-test-dynamicpv-j96h": Phase="Pending", Reason="", readiness=false. Elapsed: 26.692690169s
Oct 14 09:43:24.534: INFO: Pod "pod-subpath-test-dynamicpv-j96h": Phase="Pending", Reason="", readiness=false. Elapsed: 28.898426255s
Oct 14 09:43:26.741: INFO: Pod "pod-subpath-test-dynamicpv-j96h": Phase="Pending", Reason="", readiness=false. Elapsed: 31.105229193s
Oct 14 09:43:28.947: INFO: Pod "pod-subpath-test-dynamicpv-j96h": Phase="Pending", Reason="", readiness=false. Elapsed: 33.311318453s
Oct 14 09:43:31.154: INFO: Pod "pod-subpath-test-dynamicpv-j96h": Phase="Succeeded", Reason="", readiness=false. Elapsed: 35.518126829s
STEP: Saw pod success
Oct 14 09:43:31.154: INFO: Pod "pod-subpath-test-dynamicpv-j96h" satisfied condition "Succeeded or Failed"
Oct 14 09:43:31.360: INFO: Trying to get logs from node ip-172-20-47-16.ap-southeast-1.compute.internal pod pod-subpath-test-dynamicpv-j96h container test-container-subpath-dynamicpv-j96h: <nil>
STEP: delete the pod
Oct 14 09:43:31.783: INFO: Waiting for pod pod-subpath-test-dynamicpv-j96h to disappear
Oct 14 09:43:31.989: INFO: Pod pod-subpath-test-dynamicpv-j96h no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-j96h
Oct 14 09:43:31.989: INFO: Deleting pod "pod-subpath-test-dynamicpv-j96h" in namespace "provisioning-5383"
... skipping 248 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.h4kFCENj0/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.h4kFCENj0/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.h4kFCENj0/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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 386 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Oct 14 09:43:43.214: 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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Oct 14 09:43:44.210: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Oct 14 09:43:45.374: INFO: Successfully created a new PD: "aws://ap-southeast-1a/vol-09ddd036664805080".
Oct 14 09:43:45.374: INFO: Creating resource for pre-provisioned PV
Oct 14 09:43:45.374: INFO: Creating PVC and PV
... skipping 4 lines ...
Oct 14 09:43:48.192: INFO: PersistentVolumeClaim pvc-8wwj2 found but phase is Pending instead of Bound.
Oct 14 09:43:50.392: INFO: PersistentVolumeClaim pvc-8wwj2 found but phase is Pending instead of Bound.
Oct 14 09:43:52.591: INFO: PersistentVolumeClaim pvc-8wwj2 found and phase=Bound (6.800943183s)
Oct 14 09:43:52.591: INFO: Waiting up to 3m0s for PersistentVolume aws-kncnx to have phase Bound
Oct 14 09:43:52.790: INFO: PersistentVolume aws-kncnx found and phase=Bound (199.337439ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Oct 14 09:43:59.994: INFO: Deleting pod "pod-a9718f34-03b9-40e3-b9c7-c285fff8e235" in namespace "volumemode-7330"
Oct 14 09:44:00.194: INFO: Wait up to 5m0s for pod "pod-a9718f34-03b9-40e3-b9c7-c285fff8e235" to be fully deleted
STEP: Deleting pv and pvc
Oct 14 09:44:04.594: INFO: Deleting PersistentVolumeClaim "pvc-8wwj2"
Oct 14 09:44:04.794: INFO: Deleting PersistentVolume "aws-kncnx"
Oct 14 09:44:05.290: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-09ddd036664805080", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-09ddd036664805080 is currently attached to i-057009a9735869b54
	status code: 400, request id: 5d2fd0d9-f521-4c89-8f7a-23d469405a43
Oct 14 09:44:11.258: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-09ddd036664805080", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-09ddd036664805080 is currently attached to i-057009a9735869b54
	status code: 400, request id: 41bb0b73-0f92-4747-9985-3454568c07cf
Oct 14 09:44:17.204: INFO: Successfully deleted PD "aws://ap-southeast-1a/vol-09ddd036664805080".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 14 09:44:17.204: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-7330" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.h4kFCENj0/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.h4kFCENj0/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
    /tmp/kops.h4kFCENj0/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.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 294 lines ...
Oct 14 09:43:48.557: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6376-e2e-sc7b5pf
STEP: creating a claim
Oct 14 09:43:48.766: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-kttj
STEP: Creating a pod to test multi_subpath
Oct 14 09:43:49.384: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-kttj" in namespace "provisioning-6376" to be "Succeeded or Failed"
Oct 14 09:43:49.588: INFO: Pod "pod-subpath-test-dynamicpv-kttj": Phase="Pending", Reason="", readiness=false. Elapsed: 204.402721ms
Oct 14 09:43:51.793: INFO: Pod "pod-subpath-test-dynamicpv-kttj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.408925161s
Oct 14 09:43:53.998: INFO: Pod "pod-subpath-test-dynamicpv-kttj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.6141141s
Oct 14 09:43:56.204: INFO: Pod "pod-subpath-test-dynamicpv-kttj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.819895272s
Oct 14 09:43:58.409: INFO: Pod "pod-subpath-test-dynamicpv-kttj": Phase="Pending", Reason="", readiness=false. Elapsed: 9.025390552s
Oct 14 09:44:00.614: INFO: Pod "pod-subpath-test-dynamicpv-kttj": Phase="Pending", Reason="", readiness=false. Elapsed: 11.230452581s
Oct 14 09:44:02.819: INFO: Pod "pod-subpath-test-dynamicpv-kttj": Phase="Pending", Reason="", readiness=false. Elapsed: 13.435426238s
Oct 14 09:44:05.024: INFO: Pod "pod-subpath-test-dynamicpv-kttj": Phase="Pending", Reason="", readiness=false. Elapsed: 15.64012933s
Oct 14 09:44:07.229: INFO: Pod "pod-subpath-test-dynamicpv-kttj": Phase="Pending", Reason="", readiness=false. Elapsed: 17.845651555s
Oct 14 09:44:09.435: INFO: Pod "pod-subpath-test-dynamicpv-kttj": Phase="Pending", Reason="", readiness=false. Elapsed: 20.050914185s
Oct 14 09:44:11.639: INFO: Pod "pod-subpath-test-dynamicpv-kttj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.255031423s
STEP: Saw pod success
Oct 14 09:44:11.639: INFO: Pod "pod-subpath-test-dynamicpv-kttj" satisfied condition "Succeeded or Failed"
Oct 14 09:44:11.843: INFO: Trying to get logs from node ip-172-20-33-219.ap-southeast-1.compute.internal pod pod-subpath-test-dynamicpv-kttj container test-container-subpath-dynamicpv-kttj: <nil>
STEP: delete the pod
Oct 14 09:44:12.257: INFO: Waiting for pod pod-subpath-test-dynamicpv-kttj to disappear
Oct 14 09:44:12.461: INFO: Pod pod-subpath-test-dynamicpv-kttj no longer exists
STEP: Deleting pod
Oct 14 09:44:12.461: INFO: Deleting pod "pod-subpath-test-dynamicpv-kttj" in namespace "provisioning-6376"
... skipping 33 lines ...
Oct 14 09:43:34.992: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5904-e2e-sc86dkx
STEP: creating a claim
Oct 14 09:43:35.190: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-jgqv
STEP: Creating a pod to test subpath
Oct 14 09:43:35.792: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-jgqv" in namespace "provisioning-5904" to be "Succeeded or Failed"
Oct 14 09:43:35.989: INFO: Pod "pod-subpath-test-dynamicpv-jgqv": Phase="Pending", Reason="", readiness=false. Elapsed: 196.567966ms
Oct 14 09:43:38.192: INFO: Pod "pod-subpath-test-dynamicpv-jgqv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.400229964s
Oct 14 09:43:40.390: INFO: Pod "pod-subpath-test-dynamicpv-jgqv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.597591396s
Oct 14 09:43:42.587: INFO: Pod "pod-subpath-test-dynamicpv-jgqv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.794666663s
Oct 14 09:43:44.784: INFO: Pod "pod-subpath-test-dynamicpv-jgqv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.991937976s
Oct 14 09:43:46.981: INFO: Pod "pod-subpath-test-dynamicpv-jgqv": Phase="Pending", Reason="", readiness=false. Elapsed: 11.189006668s
Oct 14 09:43:49.179: INFO: Pod "pod-subpath-test-dynamicpv-jgqv": Phase="Pending", Reason="", readiness=false. Elapsed: 13.386591945s
Oct 14 09:43:51.376: INFO: Pod "pod-subpath-test-dynamicpv-jgqv": Phase="Pending", Reason="", readiness=false. Elapsed: 15.583996747s
Oct 14 09:43:53.575: INFO: Pod "pod-subpath-test-dynamicpv-jgqv": Phase="Pending", Reason="", readiness=false. Elapsed: 17.782650388s
Oct 14 09:43:55.772: INFO: Pod "pod-subpath-test-dynamicpv-jgqv": Phase="Pending", Reason="", readiness=false. Elapsed: 19.980239262s
Oct 14 09:43:57.969: INFO: Pod "pod-subpath-test-dynamicpv-jgqv": Phase="Pending", Reason="", readiness=false. Elapsed: 22.177431129s
Oct 14 09:44:00.167: INFO: Pod "pod-subpath-test-dynamicpv-jgqv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.375422335s
STEP: Saw pod success
Oct 14 09:44:00.167: INFO: Pod "pod-subpath-test-dynamicpv-jgqv" satisfied condition "Succeeded or Failed"
Oct 14 09:44:00.364: INFO: Trying to get logs from node ip-172-20-33-219.ap-southeast-1.compute.internal pod pod-subpath-test-dynamicpv-jgqv container test-container-subpath-dynamicpv-jgqv: <nil>
STEP: delete the pod
Oct 14 09:44:00.770: INFO: Waiting for pod pod-subpath-test-dynamicpv-jgqv to disappear
Oct 14 09:44:00.969: INFO: Pod pod-subpath-test-dynamicpv-jgqv no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-jgqv
Oct 14 09:44:00.969: INFO: Deleting pod "pod-subpath-test-dynamicpv-jgqv" in namespace "provisioning-5904"
... skipping 202 lines ...
Oct 14 09:43:50.081: INFO: PersistentVolumeClaim pvc-cczqf found but phase is Pending instead of Bound.
Oct 14 09:43:52.279: INFO: PersistentVolumeClaim pvc-cczqf found and phase=Bound (6.788991182s)
Oct 14 09:43:52.279: INFO: Waiting up to 3m0s for PersistentVolume aws-rsj6t to have phase Bound
Oct 14 09:43:52.476: INFO: PersistentVolume aws-rsj6t found and phase=Bound (196.584428ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-twdm
STEP: Creating a pod to test exec-volume-test
Oct 14 09:43:53.067: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-twdm" in namespace "volume-8722" to be "Succeeded or Failed"
Oct 14 09:43:53.266: INFO: Pod "exec-volume-test-preprovisionedpv-twdm": Phase="Pending", Reason="", readiness=false. Elapsed: 199.101848ms
Oct 14 09:43:55.463: INFO: Pod "exec-volume-test-preprovisionedpv-twdm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.396257011s
Oct 14 09:43:57.660: INFO: Pod "exec-volume-test-preprovisionedpv-twdm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.593105198s
Oct 14 09:43:59.857: INFO: Pod "exec-volume-test-preprovisionedpv-twdm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.790728108s
Oct 14 09:44:02.056: INFO: Pod "exec-volume-test-preprovisionedpv-twdm": Phase="Pending", Reason="", readiness=false. Elapsed: 8.989037239s
Oct 14 09:44:04.253: INFO: Pod "exec-volume-test-preprovisionedpv-twdm": Phase="Pending", Reason="", readiness=false. Elapsed: 11.186694851s
... skipping 6 lines ...
Oct 14 09:44:19.635: INFO: Pod "exec-volume-test-preprovisionedpv-twdm": Phase="Pending", Reason="", readiness=false. Elapsed: 26.568694802s
Oct 14 09:44:21.834: INFO: Pod "exec-volume-test-preprovisionedpv-twdm": Phase="Pending", Reason="", readiness=false. Elapsed: 28.767328561s
Oct 14 09:44:24.032: INFO: Pod "exec-volume-test-preprovisionedpv-twdm": Phase="Pending", Reason="", readiness=false. Elapsed: 30.965014419s
Oct 14 09:44:26.231: INFO: Pod "exec-volume-test-preprovisionedpv-twdm": Phase="Pending", Reason="", readiness=false. Elapsed: 33.164241684s
Oct 14 09:44:28.428: INFO: Pod "exec-volume-test-preprovisionedpv-twdm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 35.361053869s
STEP: Saw pod success
Oct 14 09:44:28.428: INFO: Pod "exec-volume-test-preprovisionedpv-twdm" satisfied condition "Succeeded or Failed"
Oct 14 09:44:28.624: INFO: Trying to get logs from node ip-172-20-47-2.ap-southeast-1.compute.internal pod exec-volume-test-preprovisionedpv-twdm container exec-container-preprovisionedpv-twdm: <nil>
STEP: delete the pod
Oct 14 09:44:29.041: INFO: Waiting for pod exec-volume-test-preprovisionedpv-twdm to disappear
Oct 14 09:44:29.237: INFO: Pod exec-volume-test-preprovisionedpv-twdm no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-twdm
Oct 14 09:44:29.237: INFO: Deleting pod "exec-volume-test-preprovisionedpv-twdm" in namespace "volume-8722"
STEP: Deleting pv and pvc
Oct 14 09:44:29.434: INFO: Deleting PersistentVolumeClaim "pvc-cczqf"
Oct 14 09:44:29.631: INFO: Deleting PersistentVolume "aws-rsj6t"
Oct 14 09:44:30.151: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-0ebd88a5ce3a67ca5", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ebd88a5ce3a67ca5 is currently attached to i-0053439ffca389c81
	status code: 400, request id: d34ed817-e7ed-45f6-8271-d16f2c2419c2
Oct 14 09:44:36.089: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-0ebd88a5ce3a67ca5", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ebd88a5ce3a67ca5 is currently attached to i-0053439ffca389c81
	status code: 400, request id: fc40757d-a249-4602-a553-774581abe25f
Oct 14 09:44:42.048: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-0ebd88a5ce3a67ca5", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ebd88a5ce3a67ca5 is currently attached to i-0053439ffca389c81
	status code: 400, request id: 06a1370f-7916-49c2-a4dc-41618497c434
Oct 14 09:44:48.034: INFO: Successfully deleted PD "aws://ap-southeast-1a/vol-0ebd88a5ce3a67ca5".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 14 09:44:48.034: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8722" for this suite.
... skipping 23 lines ...
Oct 14 09:44:11.321: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1922-e2e-sctrgnc
STEP: creating a claim
Oct 14 09:44:11.523: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-hjmq
STEP: Creating a pod to test subpath
Oct 14 09:44:12.118: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-hjmq" in namespace "provisioning-1922" to be "Succeeded or Failed"
Oct 14 09:44:12.316: INFO: Pod "pod-subpath-test-dynamicpv-hjmq": Phase="Pending", Reason="", readiness=false. Elapsed: 197.499066ms
Oct 14 09:44:14.514: INFO: Pod "pod-subpath-test-dynamicpv-hjmq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.395744759s
Oct 14 09:44:16.711: INFO: Pod "pod-subpath-test-dynamicpv-hjmq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.59317168s
Oct 14 09:44:18.909: INFO: Pod "pod-subpath-test-dynamicpv-hjmq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.791167704s
Oct 14 09:44:21.110: INFO: Pod "pod-subpath-test-dynamicpv-hjmq": Phase="Pending", Reason="", readiness=false. Elapsed: 8.991594304s
Oct 14 09:44:23.308: INFO: Pod "pod-subpath-test-dynamicpv-hjmq": Phase="Pending", Reason="", readiness=false. Elapsed: 11.190385535s
Oct 14 09:44:25.508: INFO: Pod "pod-subpath-test-dynamicpv-hjmq": Phase="Pending", Reason="", readiness=false. Elapsed: 13.389478166s
Oct 14 09:44:27.709: INFO: Pod "pod-subpath-test-dynamicpv-hjmq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 15.590718417s
STEP: Saw pod success
Oct 14 09:44:27.709: INFO: Pod "pod-subpath-test-dynamicpv-hjmq" satisfied condition "Succeeded or Failed"
Oct 14 09:44:27.906: INFO: Trying to get logs from node ip-172-20-33-219.ap-southeast-1.compute.internal pod pod-subpath-test-dynamicpv-hjmq container test-container-subpath-dynamicpv-hjmq: <nil>
STEP: delete the pod
Oct 14 09:44:28.314: INFO: Waiting for pod pod-subpath-test-dynamicpv-hjmq to disappear
Oct 14 09:44:28.511: INFO: Pod pod-subpath-test-dynamicpv-hjmq no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-hjmq
Oct 14 09:44:28.511: INFO: Deleting pod "pod-subpath-test-dynamicpv-hjmq" in namespace "provisioning-1922"
STEP: Creating pod pod-subpath-test-dynamicpv-hjmq
STEP: Creating a pod to test subpath
Oct 14 09:44:28.907: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-hjmq" in namespace "provisioning-1922" to be "Succeeded or Failed"
Oct 14 09:44:29.105: INFO: Pod "pod-subpath-test-dynamicpv-hjmq": Phase="Pending", Reason="", readiness=false. Elapsed: 197.358823ms
Oct 14 09:44:31.303: INFO: Pod "pod-subpath-test-dynamicpv-hjmq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.395066039s
Oct 14 09:44:33.501: INFO: Pod "pod-subpath-test-dynamicpv-hjmq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.593575665s
STEP: Saw pod success
Oct 14 09:44:33.501: INFO: Pod "pod-subpath-test-dynamicpv-hjmq" satisfied condition "Succeeded or Failed"
Oct 14 09:44:33.698: INFO: Trying to get logs from node ip-172-20-33-219.ap-southeast-1.compute.internal pod pod-subpath-test-dynamicpv-hjmq container test-container-subpath-dynamicpv-hjmq: <nil>
STEP: delete the pod
Oct 14 09:44:34.100: INFO: Waiting for pod pod-subpath-test-dynamicpv-hjmq to disappear
Oct 14 09:44:34.297: INFO: Pod pod-subpath-test-dynamicpv-hjmq no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-hjmq
Oct 14 09:44:34.297: INFO: Deleting pod "pod-subpath-test-dynamicpv-hjmq" in namespace "provisioning-1922"
... skipping 114 lines ...
STEP: Deleting pod aws-client in namespace volume-7466
Oct 14 09:44:36.948: INFO: Waiting for pod aws-client to disappear
Oct 14 09:44:37.156: INFO: Pod aws-client still exists
Oct 14 09:44:39.156: INFO: Waiting for pod aws-client to disappear
Oct 14 09:44:39.363: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Oct 14 09:44:39.682: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-01a3db9a885bca165", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01a3db9a885bca165 is currently attached to i-0053439ffca389c81
	status code: 400, request id: 657f0088-114b-4146-9002-706fd1d9f033
Oct 14 09:44:45.729: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-01a3db9a885bca165", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01a3db9a885bca165 is currently attached to i-0053439ffca389c81
	status code: 400, request id: 13d4b958-4742-4869-8477-c99098123eee
Oct 14 09:44:51.645: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-01a3db9a885bca165", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01a3db9a885bca165 is currently attached to i-0053439ffca389c81
	status code: 400, request id: 1c1d1c57-f87a-42a8-8bed-b014a3781bd0
Oct 14 09:44:57.643: INFO: Successfully deleted PD "aws://ap-southeast-1a/vol-01a3db9a885bca165".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 14 09:44:57.643: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-7466" for this suite.
... skipping 230 lines ...
Oct 14 09:45:07.717: INFO: Waiting for pod aws-client to disappear
Oct 14 09:45:07.921: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Oct 14 09:45:07.921: INFO: Deleting PersistentVolumeClaim "pvc-wl5pj"
Oct 14 09:45:08.127: INFO: Deleting PersistentVolume "aws-4zq54"
Oct 14 09:45:09.250: INFO: Couldn't delete PD "aws://ap-southeast-1a/vol-026602a9e621ad543", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-026602a9e621ad543 is currently attached to i-0023c706c9d49ee11
	status code: 400, request id: 62b734ac-2439-4731-8dfd-046a1f3af3ae
Oct 14 09:45:15.264: INFO: Successfully deleted PD "aws://ap-southeast-1a/vol-026602a9e621ad543".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Oct 14 09:45:15.264: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-439" for this suite.
... skipping 194 lines ...
Oct 14 09:42:11.138: INFO: Creating resource for dynamic PV
Oct 14 09:42:11.138: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-1847-e2e-scf28t7
STEP: creating a claim
Oct 14 09:42:11.354: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Oct 14 09:42:11.979: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-f988v" in namespace "snapshotting-1847" to be "Succeeded or Failed"
Oct 14 09:42:12.188: INFO: Pod "pvc-snapshottable-tester-f988v": Phase="Pending", Reason="", readiness=false. Elapsed: 208.89295ms
Oct 14 09:42:14.395: INFO: Pod "pvc-snapshottable-tester-f988v": Phase="Pending", Reason="", readiness=false. Elapsed: 2.415260728s
Oct 14 09:42:16.601: INFO: Pod "pvc-snapshottable-tester-f988v": Phase="Pending", Reason="", readiness=false. Elapsed: 4.621777596s
Oct 14 09:42:18.808: INFO: Pod "pvc-snapshottable-tester-f988v": Phase="Pending", Reason="", readiness=false. Elapsed: 6.828449161s
Oct 14 09:42:21.015: INFO: Pod "pvc-snapshottable-tester-f988v": Phase="Pending", Reason="", readiness=false. Elapsed: 9.035815786s
Oct 14 09:42:23.221: INFO: Pod "pvc-snapshottable-tester-f988v": Phase="Pending", Reason="", readiness=false. Elapsed: 11.242001905s
Oct 14 09:42:25.429: INFO: Pod "pvc-snapshottable-tester-f988v": Phase="Pending", Reason="", readiness=false. Elapsed: 13.449189319s
Oct 14 09:42:27.636: INFO: Pod "pvc-snapshottable-tester-f988v": Phase="Pending", Reason="", readiness=false. Elapsed: 15.656365201s
Oct 14 09:42:29.845: INFO: Pod "pvc-snapshottable-tester-f988v": Phase="Pending", Reason="", readiness=false. Elapsed: 17.865348763s
Oct 14 09:42:32.052: INFO: Pod "pvc-snapshottable-tester-f988v": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.072270316s
STEP: Saw pod success
Oct 14 09:42:32.052: INFO: Pod "pvc-snapshottable-tester-f988v" satisfied condition "Succeeded or Failed"
Oct 14 09:42:32.466: INFO: Pod pvc-snapshottable-tester-f988v has the following logs: 
Oct 14 09:42:32.466: INFO: Deleting pod "pvc-snapshottable-tester-f988v" in namespace "snapshotting-1847"
Oct 14 09:42:32.679: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-f988v" to be fully deleted
Oct 14 09:42:32.885: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comkqctk] to have phase Bound
Oct 14 09:42:33.090: INFO: PersistentVolumeClaim ebs.csi.aws.comkqctk found and phase=Bound (205.768635ms)
STEP: [init] checking the claim
... skipping 110 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:243
STEP: checking the snapshot
STEP: checking the SnapshotContent
STEP: Modifying source data test
STEP: modifying the data in the source PVC
Oct 14 09:46:16.204: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-6rwz8" in namespace "snapshotting-1847" to be "Succeeded or Failed"
Oct 14 09:46:16.411: INFO: Pod "pvc-snapshottable-data-tester-6rwz8": Phase="Pending", Reason="", readiness=false. Elapsed: 206.452898ms
Oct 14 09:46:18.619: INFO: Pod "pvc-snapshottable-data-tester-6rwz8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.414226403s
Oct 14 09:46:20.825: INFO: Pod "pvc-snapshottable-data-tester-6rwz8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.620881781s
Oct 14 09:46:23.032: INFO: Pod "pvc-snapshottable-data-tester-6rwz8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.827187611s
STEP: Saw pod success
Oct 14 09:46:23.032: INFO: Pod "pvc-snapshottable-data-tester-6rwz8" satisfied condition "Succeeded or Failed"
Oct 14 09:46:23.451: INFO: Pod pvc-snapshottable-data-tester-6rwz8 has the following logs: 
Oct 14 09:46:23.451: INFO: Deleting pod "pvc-snapshottable-data-tester-6rwz8" in namespace "snapshotting-1847"
Oct 14 09:46:23.662: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-6rwz8" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Oct 14 09:46:34.696: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-b6f7c24027-45100.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-1847 exec restored-pvc-tester-mbn89 --namespace=snapshotting-1847 -- cat /mnt/test/data'
... skipping 28 lines ...
Oct 14 09:47:00.449: INFO: volumesnapshotcontents snapcontent-be28fea2-0cb6-411d-8f81-04defce81991 has been found and is not deleted
Oct 14 09:47:01.657: INFO: volumesnapshotcontents snapcontent-be28fea2-0cb6-411d-8f81-04defce81991 has been found and is not deleted
Oct 14 09:47:02.864: INFO: volumesnapshotcontents snapcontent-be28fea2-0cb6-411d-8f81-04defce81991 has been found and is not deleted
Oct 14 09:47:04.071: INFO: volumesnapshotcontents snapcontent-be28fea2-0cb6-411d-8f81-04defce81991 has been found and is not deleted
Oct 14 09:47:05.277: INFO: volumesnapshotcontents snapcontent-be28fea2-0cb6-411d-8f81-04defce81991 has been found and is not deleted
Oct 14 09:47:06.486: INFO: volumesnapshotcontents snapcontent-be28fea2-0cb6-411d-8f81-04defce81991 has been found and is not deleted
Oct 14 09:47:07.486: INFO: WaitUntil failed after reaching the timeout 30s
[AfterEach] volume snapshot controller
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:221
Oct 14 09:47:07.694: INFO: Pod restored-pvc-tester-mbn89 has the following logs: 
Oct 14 09:47:07.694: INFO: Deleting pod "restored-pvc-tester-mbn89" in namespace "snapshotting-1847"
Oct 14 09:47:07.908: INFO: Wait up to 5m0s for pod "restored-pvc-tester-mbn89" to be fully deleted
Oct 14 09:47:40.321: INFO: deleting claim "snapshotting-1847"/"pvc-c878t"
... skipping 42 lines ...
Oct 14 09:42:42.955: INFO: Creating resource for dynamic PV
Oct 14 09:42:42.955: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-6504-e2e-scg45nn
STEP: creating a claim
Oct 14 09:42:43.153: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Oct 14 09:42:43.745: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-5zgzf" in namespace "snapshotting-6504" to be "Succeeded or Failed"
Oct 14 09:42:43.945: INFO: Pod "pvc-snapshottable-tester-5zgzf": Phase="Pending", Reason="", readiness=false. Elapsed: 200.207938ms
Oct 14 09:42:46.143: INFO: Pod "pvc-snapshottable-tester-5zgzf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.398271917s
Oct 14 09:42:48.343: INFO: Pod "pvc-snapshottable-tester-5zgzf": Phase="Pending", Reason="", readiness=false. Elapsed: 4.598022692s
Oct 14 09:42:50.540: INFO: Pod "pvc-snapshottable-tester-5zgzf": Phase="Pending", Reason="", readiness=false. Elapsed: 6.794598427s
Oct 14 09:42:52.736: INFO: Pod "pvc-snapshottable-tester-5zgzf": Phase="Pending", Reason="", readiness=false. Elapsed: 8.990873946s
Oct 14 09:42:54.936: INFO: Pod "pvc-snapshottable-tester-5zgzf": Phase="Succeeded", Reason="", readiness=false. Elapsed: 11.19087254s
STEP: Saw pod success
Oct 14 09:42:54.936: INFO: Pod "pvc-snapshottable-tester-5zgzf" satisfied condition "Succeeded or Failed"
Oct 14 09:42:55.332: INFO: Pod pvc-snapshottable-tester-5zgzf has the following logs: 
Oct 14 09:42:55.332: INFO: Deleting pod "pvc-snapshottable-tester-5zgzf" in namespace "snapshotting-6504"
Oct 14 09:42:55.532: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-5zgzf" to be fully deleted
Oct 14 09:42:55.730: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comjlfgt] to have phase Bound
Oct 14 09:42:55.929: INFO: PersistentVolumeClaim ebs.csi.aws.comjlfgt found and phase=Bound (198.866465ms)
STEP: [init] checking the claim
... skipping 118 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:243
STEP: checking the snapshot
STEP: checking the SnapshotContent
STEP: Modifying source data test
STEP: modifying the data in the source PVC
Oct 14 09:46:17.892: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-vbkkb" in namespace "snapshotting-6504" to be "Succeeded or Failed"
Oct 14 09:46:18.089: INFO: Pod "pvc-snapshottable-data-tester-vbkkb": Phase="Pending", Reason="", readiness=false. Elapsed: 196.470762ms
Oct 14 09:46:20.286: INFO: Pod "pvc-snapshottable-data-tester-vbkkb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.39314925s
Oct 14 09:46:22.483: INFO: Pod "pvc-snapshottable-data-tester-vbkkb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.590204818s
Oct 14 09:46:24.680: INFO: Pod "pvc-snapshottable-data-tester-vbkkb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.787358997s
STEP: Saw pod success
Oct 14 09:46:24.680: INFO: Pod "pvc-snapshottable-data-tester-vbkkb" satisfied condition "Succeeded or Failed"
Oct 14 09:46:25.081: INFO: Pod pvc-snapshottable-data-tester-vbkkb has the following logs: 
Oct 14 09:46:25.081: INFO: Deleting pod "pvc-snapshottable-data-tester-vbkkb" in namespace "snapshotting-6504"
Oct 14 09:46:25.283: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-vbkkb" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Oct 14 09:46:48.267: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-b6f7c24027-45100.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-6504 exec restored-pvc-tester-v6d6n --namespace=snapshotting-6504 -- cat /mnt/test/data'
... skipping 29 lines ...
Oct 14 09:47:15.041: INFO: volumesnapshotcontents pre-provisioned-snapcontent-d3c9e51c-fa76-44b3-ab23-9a779c8d2c08 has been found and is not deleted
Oct 14 09:47:16.238: INFO: volumesnapshotcontents pre-provisioned-snapcontent-d3c9e51c-fa76-44b3-ab23-9a779c8d2c08 has been found and is not deleted
Oct 14 09:47:17.435: INFO: volumesnapshotcontents pre-provisioned-snapcontent-d3c9e51c-fa76-44b3-ab23-9a779c8d2c08 has been found and is not deleted
Oct 14 09:47:18.636: INFO: volumesnapshotcontents pre-provisioned-snapcontent-d3c9e51c-fa76-44b3-ab23-9a779c8d2c08 has been found and is not deleted
Oct 14 09:47:19.833: INFO: volumesnapshotcontents pre-provisioned-snapcontent-d3c9e51c-fa76-44b3-ab23-9a779c8d2c08 has been found and is not deleted
Oct 14 09:47:21.030: INFO: volumesnapshotcontents pre-provisioned-snapcontent-d3c9e51c-fa76-44b3-ab23-9a779c8d2c08 has been found and is not deleted
Oct 14 09:47:22.030: INFO: WaitUntil failed after reaching the timeout 30s
[AfterEach] volume snapshot controller
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:221
Oct 14 09:47:22.229: INFO: Pod restored-pvc-tester-v6d6n has the following logs: 
Oct 14 09:47:22.229: INFO: Deleting pod "restored-pvc-tester-v6d6n" in namespace "snapshotting-6504"
Oct 14 09:47:22.427: INFO: Wait up to 5m0s for pod "restored-pvc-tester-v6d6n" to be fully deleted
Oct 14 09:47:54.820: INFO: deleting claim "snapshotting-6504"/"pvc-9lm84"
... skipping 46 lines ...
Oct 14 09:43:20.097: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9873pcglp
STEP: creating a claim
Oct 14 09:43:20.294: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-zr4n
STEP: Creating a pod to test multi_subpath
Oct 14 09:43:20.888: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-zr4n" in namespace "provisioning-9873" to be "Succeeded or Failed"
Oct 14 09:43:21.083: INFO: Pod "pod-subpath-test-dynamicpv-zr4n": Phase="Pending", Reason="", readiness=false. Elapsed: 195.256223ms
Oct 14 09:43:23.282: INFO: Pod "pod-subpath-test-dynamicpv-zr4n": Phase="Pending", Reason="", readiness=false. Elapsed: 2.393554607s
Oct 14 09:43:25.487: INFO: Pod "pod-subpath-test-dynamicpv-zr4n": Phase="Pending", Reason="", readiness=false. Elapsed: 4.599006202s
Oct 14 09:43:27.686: INFO: Pod "pod-subpath-test-dynamicpv-zr4n": Phase="Pending", Reason="", readiness=false. Elapsed: 6.797626534s
Oct 14 09:43:29.882: INFO: Pod "pod-subpath-test-dynamicpv-zr4n": Phase="Pending", Reason="", readiness=false. Elapsed: 8.993365878s
Oct 14 09:43:32.077: INFO: Pod "pod-subpath-test-dynamicpv-zr4n": Phase="Pending", Reason="", readiness=false. Elapsed: 11.188987132s
... skipping 125 lines ...
Oct 14 09:48:08.976: INFO: Pod "pod-subpath-test-dynamicpv-zr4n": Phase="Pending", Reason="", readiness=false. Elapsed: 4m48.087780885s
Oct 14 09:48:11.173: INFO: Pod "pod-subpath-test-dynamicpv-zr4n": Phase="Pending", Reason="", readiness=false. Elapsed: 4m50.284488959s
Oct 14 09:48:13.369: INFO: Pod "pod-subpath-test-dynamicpv-zr4n": Phase="Pending", Reason="", readiness=false. Elapsed: 4m52.480586371s
Oct 14 09:48:15.565: INFO: Pod "pod-subpath-test-dynamicpv-zr4n": Phase="Pending", Reason="", readiness=false. Elapsed: 4m54.676856529s
Oct 14 09:48:17.763: INFO: Pod "pod-subpath-test-dynamicpv-zr4n": Phase="Pending", Reason="", readiness=false. Elapsed: 4m56.874516155s
Oct 14 09:48:19.959: INFO: Pod "pod-subpath-test-dynamicpv-zr4n": Phase="Pending", Reason="", readiness=false. Elapsed: 4m59.070774372s
Oct 14 09:48:22.371: INFO: Failed to get logs from node "ip-172-20-37-167.ap-southeast-1.compute.internal" pod "pod-subpath-test-dynamicpv-zr4n" container "init-volume-dynamicpv-zr4n": the server rejected our request for an unknown reason (get pods pod-subpath-test-dynamicpv-zr4n)
Oct 14 09:48:22.568: INFO: Failed to get logs from node "ip-172-20-37-167.ap-southeast-1.compute.internal" pod "pod-subpath-test-dynamicpv-zr4n" container "test-container-subpath-dynamicpv-zr4n": the server rejected our request for an unknown reason (get pods pod-subpath-test-dynamicpv-zr4n)
STEP: delete the pod
Oct 14 09:48:22.765: INFO: Waiting for pod pod-subpath-test-dynamicpv-zr4n to disappear
Oct 14 09:48:22.961: INFO: Pod pod-subpath-test-dynamicpv-zr4n still exists
Oct 14 09:48:24.962: INFO: Waiting for pod pod-subpath-test-dynamicpv-zr4n to disappear
Oct 14 09:48:25.158: INFO: Pod pod-subpath-test-dynamicpv-zr4n still exists
Oct 14 09:48:26.961: INFO: Waiting for pod pod-subpath-test-dynamicpv-zr4n to disappear
... skipping 113 lines ...
STEP: Found 9 events.
Oct 14 09:50:27.319: INFO: At 2021-10-14 09:43:20 +0000 UTC - event for aws6zpt5: {persistentvolume-controller } WaitForFirstConsumer: waiting for first consumer to be created before binding
Oct 14 09:50:27.319: INFO: At 2021-10-14 09:43:21 +0000 UTC - event for aws6zpt5: {persistentvolume-controller } ExternalProvisioning: waiting for a volume to be created, either by external provisioner "ebs.csi.aws.com" or manually created by system administrator
Oct 14 09:50:27.319: INFO: At 2021-10-14 09:43:21 +0000 UTC - event for aws6zpt5: {ebs.csi.aws.com_ebs-csi-controller-54dc46fc7b-9dv8w_493ebf39-b23d-4e4c-9a85-1dfa72469296 } Provisioning: External provisioner is provisioning volume for claim "provisioning-9873/aws6zpt5"
Oct 14 09:50:27.319: INFO: At 2021-10-14 09:43:25 +0000 UTC - event for aws6zpt5: {ebs.csi.aws.com_ebs-csi-controller-54dc46fc7b-9dv8w_493ebf39-b23d-4e4c-9a85-1dfa72469296 } ProvisioningSucceeded: Successfully provisioned volume pvc-4f8dcb33-ba7d-42e7-9ab9-db3869443b17
Oct 14 09:50:27.319: INFO: At 2021-10-14 09:43:25 +0000 UTC - event for pod-subpath-test-dynamicpv-zr4n: {default-scheduler } Scheduled: Successfully assigned provisioning-9873/pod-subpath-test-dynamicpv-zr4n to ip-172-20-37-167.ap-southeast-1.compute.internal
Oct 14 09:50:27.319: INFO: At 2021-10-14 09:44:02 +0000 UTC - event for pod-subpath-test-dynamicpv-zr4n: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-4f8dcb33-ba7d-42e7-9ab9-db3869443b17" : rpc error: code = DeadlineExceeded desc = context deadline exceeded
Oct 14 09:50:27.319: INFO: At 2021-10-14 09:44:05 +0000 UTC - event for pod-subpath-test-dynamicpv-zr4n: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-4f8dcb33-ba7d-42e7-9ab9-db3869443b17" : rpc error: code = Internal desc = Could not attach volume "vol-0acafbe7f5b0d9bad" to node "i-057009a9735869b54": attachment of disk "vol-0acafbe7f5b0d9bad" failed, expected device to be attached but was attaching
Oct 14 09:50:27.319: INFO: At 2021-10-14 09:45:28 +0000 UTC - event for pod-subpath-test-dynamicpv-zr4n: {kubelet ip-172-20-37-167.ap-southeast-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[test-volume], unattached volumes=[kube-api-access-6vktq test-volume liveness-probe-volume]: timed out waiting for the condition
Oct 14 09:50:27.319: INFO: At 2021-10-14 09:50:02 +0000 UTC - event for pod-subpath-test-dynamicpv-zr4n: {kubelet ip-172-20-37-167.ap-southeast-1.compute.internal} FailedMount: Unable to attach or mount volumes: unmounted volumes=[test-volume], unattached volumes=[liveness-probe-volume kube-api-access-6vktq test-volume]: timed out waiting for the condition
Oct 14 09:50:27.515: INFO: POD  NODE  PHASE  GRACE  CONDITIONS
Oct 14 09:50:27.515: INFO: 
Oct 14 09:50:27.711: INFO: 
Logging node info for node ip-172-20-33-219.ap-southeast-1.compute.internal
... skipping 155 lines ...
  /tmp/kops.h4kFCENj0/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should support creating multiple subpath from same volumes [Slow] [It]
      /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:294

      Unexpected error:
          <*errors.errorString | 0xc00077df60>: {
              s: "expected pod \"pod-subpath-test-dynamicpv-zr4n\" success: Gave up after waiting 5m0s for pod \"pod-subpath-test-dynamicpv-zr4n\" to be \"Succeeded or Failed\"",
          }
          expected pod "pod-subpath-test-dynamicpv-zr4n" success: Gave up after waiting 5m0s for pod "pod-subpath-test-dynamicpv-zr4n" to be "Succeeded or Failed"
      occurred

      /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:742
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeLimits
  /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
... skipping 90 lines ...
    /tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumelimits.go:123
------------------------------


Summarizing 1 Failure:

[Fail] [ebs-csi-migration] EBS CSI Migration [Driver: aws] [Testpattern: Dynamic PV (default fs)] subPath [It] should support creating multiple subpath from same volumes [Slow] 
/tmp/kops.h4kFCENj0/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:742

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


Ginkgo ran 1 suite in 20m32.166300291s
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 1507 lines ...