This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-06-08 00:03
Elapsed31m21s
Revisionmaster

No Test Failures!


Error lines from build-log.txt

... skipping 488 lines ...
I0608 00:07:16.101176   11641 up.go:43] Cleaning up any leaked resources from previous cluster
I0608 00:07:16.101207   11641 dumplogs.go:38] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops toolbox dump --name e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ubuntu
I0608 00:07:16.117532   11647 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0608 00:07:16.117748   11647 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io" not found
W0608 00:07:16.686007   11641 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0608 00:07:16.686056   11641 down.go:48] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops delete cluster --name e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --yes
I0608 00:07:16.703165   11657 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0608 00:07:16.703282   11657 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io" not found
I0608 00:07:17.254184   11641 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/06/08 00:07:17 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
I0608 00:07:17.266230   11641 http.go:37] curl https://ip.jsb.workers.dev
I0608 00:07:17.464288   11641 up.go:144] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops create cluster --name e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --cloud aws --kubernetes-version 1.21.0 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --networking calico --override=cluster.spec.cloudConfig.awsEBSCSIDriver.enabled=true --override=cluster.spec.snapshotController.enabled=true --override=cluster.spec.certManager.enabled=true --admin-access 35.224.171.180/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ca-central-1a --master-size c5.large
I0608 00:07:17.478722   11671 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0608 00:07:17.478807   11671 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I0608 00:07:17.524496   11671 create_cluster.go:728] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0608 00:07:18.222717   11671 new_cluster.go:1051]  Cloud Provider ID = aws
... skipping 40 lines ...

I0608 00:07:43.546826   11641 up.go:181] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops validate cluster --name e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0608 00:07:43.562961   11692 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0608 00:07:43.563161   11692 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io

W0608 00:07:44.705592   11692 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0608 00:07:54.749027   11692 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W0608 00:08:04.793274   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W0608 00:08:14.853276   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W0608 00:08:24.901908   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W0608 00:08:34.958567   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W0608 00:08:45.003616   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W0608 00:08:55.049804   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W0608 00:09:05.106839   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W0608 00:09:15.160306   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W0608 00:09:25.217371   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
W0608 00:09:35.255626   11692 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W0608 00:09:45.300861   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W0608 00:09:55.345607   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
W0608 00:10:05.403777   11692 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W0608 00:10:15.445579   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W0608 00:10:25.490630   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W0608 00:10:35.529563   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W0608 00:10:45.571376   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W0608 00:10:55.612101   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
W0608 00:11:05.629890   11692 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W0608 00:11:15.676520   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W0608 00:11:25.717640   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W0608 00:11:35.758404   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W0608 00:11:45.804203   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W0608 00:11:55.848996   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W0608 00:12:05.907759   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W0608 00:12:15.966138   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W0608 00:12:26.027948   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W0608 00:12:36.086732   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W0608 00:12:46.131872   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W0608 00:12:56.176156   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W0608 00:13:06.219436   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W0608 00:13:16.265689   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W0608 00:13:26.302645   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W0608 00:13:36.347346   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W0608 00:13:46.406190   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W0608 00:13:56.462932   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W0608 00:14:06.522937   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W0608 00:14:16.569206   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W0608 00:14:26.629538   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0f1ca4a47ab66c5f4					machine "i-0f1ca4a47ab66c5f4" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-p88w7	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-p88w7" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-8gspg	system-cluster-critical pod "cert-manager-webhook-7bbf67968-8gspg" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-9dtxc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-9dtxc" is pending
Pod	kube-system/coredns-f45c4bf76-jb4b9			system-cluster-critical pod "coredns-f45c4bf76-jb4b9" is pending

Validation Failed
W0608 00:14:38.291801   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0f1ca4a47ab66c5f4					machine "i-0f1ca4a47ab66c5f4" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-p88w7	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-p88w7" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-8gspg	system-cluster-critical pod "cert-manager-webhook-7bbf67968-8gspg" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-9dtxc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-9dtxc" is pending
Pod	kube-system/coredns-f45c4bf76-jb4b9			system-cluster-critical pod "coredns-f45c4bf76-jb4b9" is pending

Validation Failed
W0608 00:14:49.424692   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0f1ca4a47ab66c5f4					machine "i-0f1ca4a47ab66c5f4" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-p88w7	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-p88w7" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-8gspg	system-cluster-critical pod "cert-manager-webhook-7bbf67968-8gspg" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-9dtxc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-9dtxc" is pending
Pod	kube-system/coredns-f45c4bf76-jb4b9			system-cluster-critical pod "coredns-f45c4bf76-jb4b9" is pending

Validation Failed
W0608 00:15:00.526028   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0f1ca4a47ab66c5f4					machine "i-0f1ca4a47ab66c5f4" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-p88w7	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-p88w7" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-8gspg	system-cluster-critical pod "cert-manager-webhook-7bbf67968-8gspg" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-9dtxc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-9dtxc" is pending
Pod	kube-system/coredns-f45c4bf76-jb4b9			system-cluster-critical pod "coredns-f45c4bf76-jb4b9" is pending

Validation Failed
W0608 00:15:11.596958   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0f1ca4a47ab66c5f4					machine "i-0f1ca4a47ab66c5f4" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-p88w7	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-p88w7" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-8gspg	system-cluster-critical pod "cert-manager-webhook-7bbf67968-8gspg" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-9dtxc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-9dtxc" is pending
Pod	kube-system/coredns-f45c4bf76-jb4b9			system-cluster-critical pod "coredns-f45c4bf76-jb4b9" is pending

Validation Failed
W0608 00:15:22.663928   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0f1ca4a47ab66c5f4					machine "i-0f1ca4a47ab66c5f4" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-p88w7	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-p88w7" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-8gspg	system-cluster-critical pod "cert-manager-webhook-7bbf67968-8gspg" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-9dtxc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-9dtxc" is pending
Pod	kube-system/coredns-f45c4bf76-jb4b9			system-cluster-critical pod "coredns-f45c4bf76-jb4b9" is pending

Validation Failed
W0608 00:15:33.757524   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0f1ca4a47ab66c5f4					machine "i-0f1ca4a47ab66c5f4" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-p88w7	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-p88w7" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-8gspg	system-cluster-critical pod "cert-manager-webhook-7bbf67968-8gspg" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-9dtxc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-9dtxc" is pending
Pod	kube-system/coredns-f45c4bf76-jb4b9			system-cluster-critical pod "coredns-f45c4bf76-jb4b9" is pending

Validation Failed
W0608 00:15:44.910639   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0f1ca4a47ab66c5f4					machine "i-0f1ca4a47ab66c5f4" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-p88w7	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-p88w7" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-8gspg	system-cluster-critical pod "cert-manager-webhook-7bbf67968-8gspg" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-9dtxc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-9dtxc" is pending
Pod	kube-system/coredns-f45c4bf76-jb4b9			system-cluster-critical pod "coredns-f45c4bf76-jb4b9" is pending

Validation Failed
W0608 00:15:56.015864   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0f1ca4a47ab66c5f4					machine "i-0f1ca4a47ab66c5f4" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-p88w7	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-p88w7" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-8gspg	system-cluster-critical pod "cert-manager-webhook-7bbf67968-8gspg" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-9dtxc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-9dtxc" is pending
Pod	kube-system/coredns-f45c4bf76-jb4b9			system-cluster-critical pod "coredns-f45c4bf76-jb4b9" is pending

Validation Failed
W0608 00:16:07.122527   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0f1ca4a47ab66c5f4					machine "i-0f1ca4a47ab66c5f4" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-p88w7	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-p88w7" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-8gspg	system-cluster-critical pod "cert-manager-webhook-7bbf67968-8gspg" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-9dtxc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-9dtxc" is pending
Pod	kube-system/coredns-f45c4bf76-jb4b9			system-cluster-critical pod "coredns-f45c4bf76-jb4b9" is pending

Validation Failed
W0608 00:16:18.277058   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 10 lines ...
Pod	kube-system/cert-manager-cainjector-74d69756d5-p88w7	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-p88w7" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-8gspg	system-cluster-critical pod "cert-manager-webhook-7bbf67968-8gspg" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-9dtxc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-9dtxc" is pending
Pod	kube-system/coredns-f45c4bf76-jb4b9			system-cluster-critical pod "coredns-f45c4bf76-jb4b9" is pending
Pod	kube-system/kops-controller-x7x9v			system-node-critical pod "kops-controller-x7x9v" is pending

Validation Failed
W0608 00:16:29.346001   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0f1ca4a47ab66c5f4					machine "i-0f1ca4a47ab66c5f4" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-p88w7	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-p88w7" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-8gspg	system-cluster-critical pod "cert-manager-webhook-7bbf67968-8gspg" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-9dtxc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-9dtxc" is pending
Pod	kube-system/coredns-f45c4bf76-jb4b9			system-cluster-critical pod "coredns-f45c4bf76-jb4b9" is pending

Validation Failed
W0608 00:16:40.435695   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 17 lines ...
Pod	kube-system/cert-manager-webhook-7bbf67968-8gspg			system-cluster-critical pod "cert-manager-webhook-7bbf67968-8gspg" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-9dtxc				system-cluster-critical pod "coredns-autoscaler-6f594f4c58-9dtxc" is pending
Pod	kube-system/coredns-f45c4bf76-jb4b9					system-cluster-critical pod "coredns-f45c4bf76-jb4b9" is pending
Pod	kube-system/kube-proxy-ip-172-20-36-176.ca-central-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-36-176.ca-central-1.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-48-35.ca-central-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-48-35.ca-central-1.compute.internal" is pending

Validation Failed
W0608 00:16:51.602653   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 16 lines ...
Pod	kube-system/cert-manager-cainjector-74d69756d5-p88w7			system-cluster-critical pod "cert-manager-cainjector-74d69756d5-p88w7" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-8gspg			system-cluster-critical pod "cert-manager-webhook-7bbf67968-8gspg" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-9dtxc				system-cluster-critical pod "coredns-autoscaler-6f594f4c58-9dtxc" is pending
Pod	kube-system/coredns-f45c4bf76-jb4b9					system-cluster-critical pod "coredns-f45c4bf76-jb4b9" is pending
Pod	kube-system/kube-proxy-ip-172-20-35-56.ca-central-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-35-56.ca-central-1.compute.internal" is pending

Validation Failed
W0608 00:17:02.802391   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 12 lines ...
Pod	kube-system/calico-node-fb9jw				system-node-critical pod "calico-node-fb9jw" is not ready (calico-node)
Pod	kube-system/calico-node-kqj2v				system-node-critical pod "calico-node-kqj2v" is not ready (calico-node)
Pod	kube-system/cert-manager-cainjector-74d69756d5-p88w7	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-p88w7" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-8gspg	system-cluster-critical pod "cert-manager-webhook-7bbf67968-8gspg" is not ready (cert-manager)
Pod	kube-system/coredns-f45c4bf76-8dfpk			system-cluster-critical pod "coredns-f45c4bf76-8dfpk" is pending

Validation Failed
W0608 00:17:14.082251   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 27 lines ...
Pod	kube-system/ebs-csi-node-5jt92			system-node-critical pod "ebs-csi-node-5jt92" is pending
Pod	kube-system/ebs-csi-node-6cvlq			system-node-critical pod "ebs-csi-node-6cvlq" is pending
Pod	kube-system/ebs-csi-node-ctbh2			system-node-critical pod "ebs-csi-node-ctbh2" is pending
Pod	kube-system/ebs-csi-node-kdl22			system-node-critical pod "ebs-csi-node-kdl22" is pending
Pod	kube-system/ebs-csi-node-w59bb			system-node-critical pod "ebs-csi-node-w59bb" is pending

Validation Failed
W0608 00:17:36.252559   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-2fnkw	system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-2fnkw" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-sbtvx	system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-sbtvx" is pending

Validation Failed
W0608 00:17:47.378022   11692 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

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

      Distro debian doesn't support ntfs -- skipping

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

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

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

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

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

    /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:92
------------------------------
... skipping 151 lines ...

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

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

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

    /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 321 lines ...
Jun  8 00:21:04.268: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 104 lines ...
STEP: Creating a kubernetes client
Jun  8 00:21:01.857: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename volumemode
W0608 00:21:02.195619   25627 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Jun  8 00:21:02.195: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail to use a volume in a pod with mismatched mode [Slow]
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  8 00:21:02.284: INFO: Creating resource for dynamic PV
Jun  8 00:21:02.284: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-320-e2e-sc7gt5f
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  8 00:21:10.621: INFO: Deleting pod "pod-d3b3620e-3b85-447a-b4f6-df29dae8cfa7" in namespace "volumemode-320"
Jun  8 00:21:10.675: INFO: Wait up to 5m0s for pod "pod-d3b3620e-3b85-447a-b4f6-df29dae8cfa7" to be fully deleted
STEP: Deleting pvc
Jun  8 00:21:12.866: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comcr8bd"
Jun  8 00:21:12.912: INFO: Waiting up to 5m0s for PersistentVolume pvc-3fcd8d6b-63b2-43b2-9166-1c0b8a248ef5 to get deleted
Jun  8 00:21:12.957: INFO: PersistentVolume pvc-3fcd8d6b-63b2-43b2-9166-1c0b8a248ef5 found and phase=Released (44.673596ms)
... skipping 9 lines ...

• [SLOW TEST:26.428 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.yi3ZpreUa/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.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 6 lines ...
Jun  8 00:21:06.945: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  8 00:21:07.419: INFO: Successfully created a new PD: "aws://ca-central-1a/vol-0ac3106c9f75c82d0".
Jun  8 00:21:07.419: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-6v29
STEP: Creating a pod to test exec-volume-test
Jun  8 00:21:07.471: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-6v29" in namespace "volume-4931" to be "Succeeded or Failed"
Jun  8 00:21:07.516: INFO: Pod "exec-volume-test-inlinevolume-6v29": Phase="Pending", Reason="", readiness=false. Elapsed: 44.869063ms
Jun  8 00:21:09.563: INFO: Pod "exec-volume-test-inlinevolume-6v29": Phase="Pending", Reason="", readiness=false. Elapsed: 2.092268481s
Jun  8 00:21:11.613: INFO: Pod "exec-volume-test-inlinevolume-6v29": Phase="Pending", Reason="", readiness=false. Elapsed: 4.142544885s
Jun  8 00:21:13.659: INFO: Pod "exec-volume-test-inlinevolume-6v29": Phase="Pending", Reason="", readiness=false. Elapsed: 6.188321721s
Jun  8 00:21:15.705: INFO: Pod "exec-volume-test-inlinevolume-6v29": Phase="Pending", Reason="", readiness=false. Elapsed: 8.233877784s
Jun  8 00:21:17.751: INFO: Pod "exec-volume-test-inlinevolume-6v29": Phase="Pending", Reason="", readiness=false. Elapsed: 10.279808262s
Jun  8 00:21:19.796: INFO: Pod "exec-volume-test-inlinevolume-6v29": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.324857276s
STEP: Saw pod success
Jun  8 00:21:19.796: INFO: Pod "exec-volume-test-inlinevolume-6v29" satisfied condition "Succeeded or Failed"
Jun  8 00:21:19.841: INFO: Trying to get logs from node ip-172-20-41-166.ca-central-1.compute.internal pod exec-volume-test-inlinevolume-6v29 container exec-container-inlinevolume-6v29: <nil>
STEP: delete the pod
Jun  8 00:21:19.987: INFO: Waiting for pod exec-volume-test-inlinevolume-6v29 to disappear
Jun  8 00:21:20.032: INFO: Pod exec-volume-test-inlinevolume-6v29 no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-6v29
Jun  8 00:21:20.032: INFO: Deleting pod "exec-volume-test-inlinevolume-6v29" in namespace "volume-4931"
Jun  8 00:21:20.246: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0ac3106c9f75c82d0", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ac3106c9f75c82d0 is currently attached to i-0f1ca4a47ab66c5f4
	status code: 400, request id: 510b25a1-6a0b-42a4-8bb3-19a11f2a91f1
Jun  8 00:21:25.564: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0ac3106c9f75c82d0", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0ac3106c9f75c82d0 is currently attached to i-0f1ca4a47ab66c5f4
	status code: 400, request id: de753e1f-ce98-4a3c-8833-16ada269e05c
Jun  8 00:21:30.898: INFO: Successfully deleted PD "aws://ca-central-1a/vol-0ac3106c9f75c82d0".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  8 00:21:30.898: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-4931" for this suite.
... skipping 79 lines ...
STEP: Creating a kubernetes client
Jun  8 00:21:01.909: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename volumemode
W0608 00:21:02.268180   25703 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Jun  8 00:21:02.268: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail to use a volume in a pod with mismatched mode [Slow]
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  8 00:21:02.356: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  8 00:21:02.356: INFO: Creating resource for dynamic PV
Jun  8 00:21:02.356: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-257whkb9
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  8 00:21:14.682: INFO: Deleting pod "pod-26ab47d7-cacd-45c7-8ec7-32f9e5f17b4f" in namespace "volumemode-257"
Jun  8 00:21:14.729: INFO: Wait up to 5m0s for pod "pod-26ab47d7-cacd-45c7-8ec7-32f9e5f17b4f" to be fully deleted
STEP: Deleting pvc
Jun  8 00:21:16.914: INFO: Deleting PersistentVolumeClaim "awsk7nhj"
Jun  8 00:21:16.959: INFO: Waiting up to 5m0s for PersistentVolume pvc-279b97d0-2f1b-468b-8456-6df6f0a5b34d to get deleted
Jun  8 00:21:17.004: INFO: PersistentVolume pvc-279b97d0-2f1b-468b-8456-6df6f0a5b34d found and phase=Released (44.397714ms)
... skipping 11 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.yi3ZpreUa/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.yi3ZpreUa/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
    /tmp/kops.yi3ZpreUa/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.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  8 00:21:32.328: INFO: Driver ebs.csi.aws.com doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
... skipping 25 lines ...
Jun  8 00:21:03.336: INFO: Creating resource for dynamic PV
Jun  8 00:21:03.336: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-7918-e2e-sc986fj
STEP: creating a claim
STEP: Expanding non-expandable pvc
Jun  8 00:21:03.472: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun  8 00:21:03.565: INFO: Error updating pvc ebs.csi.aws.com77t8c: PersistentVolumeClaim "ebs.csi.aws.com77t8c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-7918-e2e-sc986fj",
  	... // 2 identical fields
  }

Jun  8 00:21:05.657: INFO: Error updating pvc ebs.csi.aws.com77t8c: PersistentVolumeClaim "ebs.csi.aws.com77t8c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-7918-e2e-sc986fj",
  	... // 2 identical fields
  }

Jun  8 00:21:07.657: INFO: Error updating pvc ebs.csi.aws.com77t8c: PersistentVolumeClaim "ebs.csi.aws.com77t8c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-7918-e2e-sc986fj",
  	... // 2 identical fields
  }

Jun  8 00:21:09.659: INFO: Error updating pvc ebs.csi.aws.com77t8c: PersistentVolumeClaim "ebs.csi.aws.com77t8c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-7918-e2e-sc986fj",
  	... // 2 identical fields
  }

Jun  8 00:21:11.658: INFO: Error updating pvc ebs.csi.aws.com77t8c: PersistentVolumeClaim "ebs.csi.aws.com77t8c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-7918-e2e-sc986fj",
  	... // 2 identical fields
  }

Jun  8 00:21:13.656: INFO: Error updating pvc ebs.csi.aws.com77t8c: PersistentVolumeClaim "ebs.csi.aws.com77t8c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-7918-e2e-sc986fj",
  	... // 2 identical fields
  }

Jun  8 00:21:15.658: INFO: Error updating pvc ebs.csi.aws.com77t8c: PersistentVolumeClaim "ebs.csi.aws.com77t8c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-7918-e2e-sc986fj",
  	... // 2 identical fields
  }

Jun  8 00:21:17.655: INFO: Error updating pvc ebs.csi.aws.com77t8c: PersistentVolumeClaim "ebs.csi.aws.com77t8c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-7918-e2e-sc986fj",
  	... // 2 identical fields
  }

Jun  8 00:21:19.655: INFO: Error updating pvc ebs.csi.aws.com77t8c: PersistentVolumeClaim "ebs.csi.aws.com77t8c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-7918-e2e-sc986fj",
  	... // 2 identical fields
  }

Jun  8 00:21:21.655: INFO: Error updating pvc ebs.csi.aws.com77t8c: PersistentVolumeClaim "ebs.csi.aws.com77t8c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-7918-e2e-sc986fj",
  	... // 2 identical fields
  }

Jun  8 00:21:23.655: INFO: Error updating pvc ebs.csi.aws.com77t8c: PersistentVolumeClaim "ebs.csi.aws.com77t8c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-7918-e2e-sc986fj",
  	... // 2 identical fields
  }

Jun  8 00:21:25.656: INFO: Error updating pvc ebs.csi.aws.com77t8c: PersistentVolumeClaim "ebs.csi.aws.com77t8c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-7918-e2e-sc986fj",
  	... // 2 identical fields
  }

Jun  8 00:21:27.660: INFO: Error updating pvc ebs.csi.aws.com77t8c: PersistentVolumeClaim "ebs.csi.aws.com77t8c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-7918-e2e-sc986fj",
  	... // 2 identical fields
  }

Jun  8 00:21:29.657: INFO: Error updating pvc ebs.csi.aws.com77t8c: PersistentVolumeClaim "ebs.csi.aws.com77t8c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-7918-e2e-sc986fj",
  	... // 2 identical fields
  }

Jun  8 00:21:31.654: INFO: Error updating pvc ebs.csi.aws.com77t8c: PersistentVolumeClaim "ebs.csi.aws.com77t8c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-7918-e2e-sc986fj",
  	... // 2 identical fields
  }

Jun  8 00:21:33.658: INFO: Error updating pvc ebs.csi.aws.com77t8c: PersistentVolumeClaim "ebs.csi.aws.com77t8c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-7918-e2e-sc986fj",
  	... // 2 identical fields
  }

Jun  8 00:21:33.750: INFO: Error updating pvc ebs.csi.aws.com77t8c: PersistentVolumeClaim "ebs.csi.aws.com77t8c" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 42 lines ...
Jun  8 00:21:04.481: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1326mvkgn
STEP: creating a claim
Jun  8 00:21:04.525: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-pb99
STEP: Creating a pod to test subpath
Jun  8 00:21:04.661: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-pb99" in namespace "provisioning-1326" to be "Succeeded or Failed"
Jun  8 00:21:04.705: INFO: Pod "pod-subpath-test-dynamicpv-pb99": Phase="Pending", Reason="", readiness=false. Elapsed: 44.22621ms
Jun  8 00:21:06.769: INFO: Pod "pod-subpath-test-dynamicpv-pb99": Phase="Pending", Reason="", readiness=false. Elapsed: 2.108175734s
Jun  8 00:21:08.815: INFO: Pod "pod-subpath-test-dynamicpv-pb99": Phase="Pending", Reason="", readiness=false. Elapsed: 4.153712841s
Jun  8 00:21:10.862: INFO: Pod "pod-subpath-test-dynamicpv-pb99": Phase="Pending", Reason="", readiness=false. Elapsed: 6.201061145s
Jun  8 00:21:12.907: INFO: Pod "pod-subpath-test-dynamicpv-pb99": Phase="Pending", Reason="", readiness=false. Elapsed: 8.245696922s
Jun  8 00:21:14.951: INFO: Pod "pod-subpath-test-dynamicpv-pb99": Phase="Pending", Reason="", readiness=false. Elapsed: 10.290076453s
Jun  8 00:21:16.996: INFO: Pod "pod-subpath-test-dynamicpv-pb99": Phase="Pending", Reason="", readiness=false. Elapsed: 12.334638063s
Jun  8 00:21:19.042: INFO: Pod "pod-subpath-test-dynamicpv-pb99": Phase="Pending", Reason="", readiness=false. Elapsed: 14.380732203s
Jun  8 00:21:21.088: INFO: Pod "pod-subpath-test-dynamicpv-pb99": Phase="Pending", Reason="", readiness=false. Elapsed: 16.426908548s
Jun  8 00:21:23.134: INFO: Pod "pod-subpath-test-dynamicpv-pb99": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.472749638s
STEP: Saw pod success
Jun  8 00:21:23.134: INFO: Pod "pod-subpath-test-dynamicpv-pb99" satisfied condition "Succeeded or Failed"
Jun  8 00:21:23.178: INFO: Trying to get logs from node ip-172-20-48-35.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-pb99 container test-container-volume-dynamicpv-pb99: <nil>
STEP: delete the pod
Jun  8 00:21:23.295: INFO: Waiting for pod pod-subpath-test-dynamicpv-pb99 to disappear
Jun  8 00:21:23.340: INFO: Pod pod-subpath-test-dynamicpv-pb99 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-pb99
Jun  8 00:21:23.340: INFO: Deleting pod "pod-subpath-test-dynamicpv-pb99" in namespace "provisioning-1326"
... skipping 156 lines ...
Jun  8 00:21:05.240: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-93026lh4l
STEP: creating a claim
Jun  8 00:21:05.288: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-ns88
STEP: Creating a pod to test exec-volume-test
Jun  8 00:21:05.434: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-ns88" in namespace "volume-9302" to be "Succeeded or Failed"
Jun  8 00:21:05.480: INFO: Pod "exec-volume-test-dynamicpv-ns88": Phase="Pending", Reason="", readiness=false. Elapsed: 45.285649ms
Jun  8 00:21:07.528: INFO: Pod "exec-volume-test-dynamicpv-ns88": Phase="Pending", Reason="", readiness=false. Elapsed: 2.094016854s
Jun  8 00:21:09.577: INFO: Pod "exec-volume-test-dynamicpv-ns88": Phase="Pending", Reason="", readiness=false. Elapsed: 4.142767662s
Jun  8 00:21:11.626: INFO: Pod "exec-volume-test-dynamicpv-ns88": Phase="Pending", Reason="", readiness=false. Elapsed: 6.191350158s
Jun  8 00:21:13.671: INFO: Pod "exec-volume-test-dynamicpv-ns88": Phase="Pending", Reason="", readiness=false. Elapsed: 8.23683775s
Jun  8 00:21:15.719: INFO: Pod "exec-volume-test-dynamicpv-ns88": Phase="Pending", Reason="", readiness=false. Elapsed: 10.284238386s
Jun  8 00:21:17.765: INFO: Pod "exec-volume-test-dynamicpv-ns88": Phase="Pending", Reason="", readiness=false. Elapsed: 12.330385838s
Jun  8 00:21:19.810: INFO: Pod "exec-volume-test-dynamicpv-ns88": Phase="Pending", Reason="", readiness=false. Elapsed: 14.376041831s
Jun  8 00:21:21.856: INFO: Pod "exec-volume-test-dynamicpv-ns88": Phase="Pending", Reason="", readiness=false. Elapsed: 16.421933199s
Jun  8 00:21:23.902: INFO: Pod "exec-volume-test-dynamicpv-ns88": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.467733197s
STEP: Saw pod success
Jun  8 00:21:23.902: INFO: Pod "exec-volume-test-dynamicpv-ns88" satisfied condition "Succeeded or Failed"
Jun  8 00:21:23.947: INFO: Trying to get logs from node ip-172-20-36-176.ca-central-1.compute.internal pod exec-volume-test-dynamicpv-ns88 container exec-container-dynamicpv-ns88: <nil>
STEP: delete the pod
Jun  8 00:21:24.889: INFO: Waiting for pod exec-volume-test-dynamicpv-ns88 to disappear
Jun  8 00:21:24.935: INFO: Pod exec-volume-test-dynamicpv-ns88 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-ns88
Jun  8 00:21:24.935: INFO: Deleting pod "exec-volume-test-dynamicpv-ns88" in namespace "volume-9302"
... skipping 83 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  8 00:21:04.641: 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.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun  8 00:21:05.993: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  8 00:21:05.993: INFO: Creating resource for dynamic PV
Jun  8 00:21:05.993: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-45919w6tn
STEP: creating a claim
Jun  8 00:21:06.038: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-b5mk
STEP: Checking for subpath error in container status
Jun  8 00:21:24.272: INFO: Deleting pod "pod-subpath-test-dynamicpv-b5mk" in namespace "provisioning-4591"
Jun  8 00:21:24.320: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-b5mk" to be fully deleted
STEP: Deleting pod
Jun  8 00:21:34.411: INFO: Deleting pod "pod-subpath-test-dynamicpv-b5mk" in namespace "provisioning-4591"
STEP: Deleting pvc
Jun  8 00:21:34.544: INFO: Deleting PersistentVolumeClaim "awsr6qxs"
... skipping 13 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.yi3ZpreUa/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.yi3ZpreUa/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath directory is outside the volume [Slow][LinuxOnly]
      /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (ntfs)][Feature:Windows] volumes
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  8 00:21:49.912: INFO: Distro debian doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Pre-provisioned PV (ntfs)][Feature:Windows] volumes
... skipping 48 lines ...

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

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

    /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 21 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  8 00:21:03.871: 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.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun  8 00:21:05.641: INFO: Creating resource for dynamic PV
Jun  8 00:21:05.641: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5299-e2e-sc52594
STEP: creating a claim
Jun  8 00:21:05.686: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-cm2c
STEP: Checking for subpath error in container status
Jun  8 00:21:29.928: INFO: Deleting pod "pod-subpath-test-dynamicpv-cm2c" in namespace "provisioning-5299"
Jun  8 00:21:29.973: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-cm2c" to be fully deleted
STEP: Deleting pod
Jun  8 00:21:36.077: INFO: Deleting pod "pod-subpath-test-dynamicpv-cm2c" in namespace "provisioning-5299"
STEP: Deleting pvc
Jun  8 00:21:36.216: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comp42s8"
... skipping 12 lines ...

• [SLOW TEST:52.760 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath directory is outside the volume [Slow][LinuxOnly]
    /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
S
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow]
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
... skipping 47 lines ...
Jun  8 00:21:06.292: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2242-e2e-sc8gdw5
STEP: creating a claim
Jun  8 00:21:06.340: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-ksgg
STEP: Creating a pod to test subpath
Jun  8 00:21:06.484: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-ksgg" in namespace "provisioning-2242" to be "Succeeded or Failed"
Jun  8 00:21:06.530: INFO: Pod "pod-subpath-test-dynamicpv-ksgg": Phase="Pending", Reason="", readiness=false. Elapsed: 46.058392ms
Jun  8 00:21:08.694: INFO: Pod "pod-subpath-test-dynamicpv-ksgg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.210382088s
Jun  8 00:21:10.744: INFO: Pod "pod-subpath-test-dynamicpv-ksgg": Phase="Pending", Reason="", readiness=false. Elapsed: 4.260102347s
Jun  8 00:21:12.791: INFO: Pod "pod-subpath-test-dynamicpv-ksgg": Phase="Pending", Reason="", readiness=false. Elapsed: 6.307123151s
Jun  8 00:21:14.839: INFO: Pod "pod-subpath-test-dynamicpv-ksgg": Phase="Pending", Reason="", readiness=false. Elapsed: 8.354555349s
Jun  8 00:21:16.889: INFO: Pod "pod-subpath-test-dynamicpv-ksgg": Phase="Pending", Reason="", readiness=false. Elapsed: 10.404809893s
Jun  8 00:21:18.981: INFO: Pod "pod-subpath-test-dynamicpv-ksgg": Phase="Pending", Reason="", readiness=false. Elapsed: 12.497274265s
Jun  8 00:21:21.029: INFO: Pod "pod-subpath-test-dynamicpv-ksgg": Phase="Pending", Reason="", readiness=false. Elapsed: 14.54533661s
Jun  8 00:21:23.313: INFO: Pod "pod-subpath-test-dynamicpv-ksgg": Phase="Pending", Reason="", readiness=false. Elapsed: 16.829361156s
Jun  8 00:21:25.700: INFO: Pod "pod-subpath-test-dynamicpv-ksgg": Phase="Pending", Reason="", readiness=false. Elapsed: 19.215641587s
Jun  8 00:21:28.047: INFO: Pod "pod-subpath-test-dynamicpv-ksgg": Phase="Pending", Reason="", readiness=false. Elapsed: 21.562819892s
Jun  8 00:21:30.139: INFO: Pod "pod-subpath-test-dynamicpv-ksgg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.655418261s
STEP: Saw pod success
Jun  8 00:21:30.140: INFO: Pod "pod-subpath-test-dynamicpv-ksgg" satisfied condition "Succeeded or Failed"
Jun  8 00:21:30.278: INFO: Trying to get logs from node ip-172-20-36-176.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-ksgg container test-container-subpath-dynamicpv-ksgg: <nil>
STEP: delete the pod
Jun  8 00:21:31.074: INFO: Waiting for pod pod-subpath-test-dynamicpv-ksgg to disappear
Jun  8 00:21:31.121: INFO: Pod pod-subpath-test-dynamicpv-ksgg no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-ksgg
Jun  8 00:21:31.121: INFO: Deleting pod "pod-subpath-test-dynamicpv-ksgg" in namespace "provisioning-2242"
STEP: Creating pod pod-subpath-test-dynamicpv-ksgg
STEP: Creating a pod to test subpath
Jun  8 00:21:31.349: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-ksgg" in namespace "provisioning-2242" to be "Succeeded or Failed"
Jun  8 00:21:31.395: INFO: Pod "pod-subpath-test-dynamicpv-ksgg": Phase="Pending", Reason="", readiness=false. Elapsed: 45.946988ms
Jun  8 00:21:33.742: INFO: Pod "pod-subpath-test-dynamicpv-ksgg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.393423011s
Jun  8 00:21:35.836: INFO: Pod "pod-subpath-test-dynamicpv-ksgg": Phase="Pending", Reason="", readiness=false. Elapsed: 4.486946391s
Jun  8 00:21:37.928: INFO: Pod "pod-subpath-test-dynamicpv-ksgg": Phase="Pending", Reason="", readiness=false. Elapsed: 6.578733971s
Jun  8 00:21:40.020: INFO: Pod "pod-subpath-test-dynamicpv-ksgg": Phase="Pending", Reason="", readiness=false. Elapsed: 8.670901446s
Jun  8 00:21:42.066: INFO: Pod "pod-subpath-test-dynamicpv-ksgg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.717444181s
STEP: Saw pod success
Jun  8 00:21:42.066: INFO: Pod "pod-subpath-test-dynamicpv-ksgg" satisfied condition "Succeeded or Failed"
Jun  8 00:21:42.407: INFO: Trying to get logs from node ip-172-20-36-176.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-ksgg container test-container-subpath-dynamicpv-ksgg: <nil>
STEP: delete the pod
Jun  8 00:21:42.552: INFO: Waiting for pod pod-subpath-test-dynamicpv-ksgg to disappear
Jun  8 00:21:42.599: INFO: Pod pod-subpath-test-dynamicpv-ksgg no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-ksgg
Jun  8 00:21:42.599: INFO: Deleting pod "pod-subpath-test-dynamicpv-ksgg" in namespace "provisioning-2242"
... skipping 114 lines ...
Jun  8 00:21:08.791: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-97974rlh
STEP: creating a claim
Jun  8 00:21:08.836: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-fmtz
STEP: Creating a pod to test subpath
Jun  8 00:21:08.981: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-fmtz" in namespace "provisioning-979" to be "Succeeded or Failed"
Jun  8 00:21:09.026: INFO: Pod "pod-subpath-test-dynamicpv-fmtz": Phase="Pending", Reason="", readiness=false. Elapsed: 44.871402ms
Jun  8 00:21:11.072: INFO: Pod "pod-subpath-test-dynamicpv-fmtz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.091231396s
Jun  8 00:21:13.118: INFO: Pod "pod-subpath-test-dynamicpv-fmtz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.137174105s
Jun  8 00:21:15.164: INFO: Pod "pod-subpath-test-dynamicpv-fmtz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.18324564s
Jun  8 00:21:17.209: INFO: Pod "pod-subpath-test-dynamicpv-fmtz": Phase="Pending", Reason="", readiness=false. Elapsed: 8.228182949s
Jun  8 00:21:19.256: INFO: Pod "pod-subpath-test-dynamicpv-fmtz": Phase="Pending", Reason="", readiness=false. Elapsed: 10.274824308s
... skipping 2 lines ...
Jun  8 00:21:25.425: INFO: Pod "pod-subpath-test-dynamicpv-fmtz": Phase="Pending", Reason="", readiness=false. Elapsed: 16.443826274s
Jun  8 00:21:27.470: INFO: Pod "pod-subpath-test-dynamicpv-fmtz": Phase="Pending", Reason="", readiness=false. Elapsed: 18.489243566s
Jun  8 00:21:29.516: INFO: Pod "pod-subpath-test-dynamicpv-fmtz": Phase="Pending", Reason="", readiness=false. Elapsed: 20.534673828s
Jun  8 00:21:31.560: INFO: Pod "pod-subpath-test-dynamicpv-fmtz": Phase="Pending", Reason="", readiness=false. Elapsed: 22.57932006s
Jun  8 00:21:33.605: INFO: Pod "pod-subpath-test-dynamicpv-fmtz": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.623773539s
STEP: Saw pod success
Jun  8 00:21:33.605: INFO: Pod "pod-subpath-test-dynamicpv-fmtz" satisfied condition "Succeeded or Failed"
Jun  8 00:21:33.650: INFO: Trying to get logs from node ip-172-20-41-166.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-fmtz container test-container-volume-dynamicpv-fmtz: <nil>
STEP: delete the pod
Jun  8 00:21:33.754: INFO: Waiting for pod pod-subpath-test-dynamicpv-fmtz to disappear
Jun  8 00:21:33.798: INFO: Pod pod-subpath-test-dynamicpv-fmtz no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-fmtz
Jun  8 00:21:33.798: INFO: Deleting pod "pod-subpath-test-dynamicpv-fmtz" in namespace "provisioning-979"
... skipping 148 lines ...
Jun  8 00:21:34.214: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-49422fhdj
STEP: creating a claim
Jun  8 00:21:34.259: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-mt7m
STEP: Creating a pod to test subpath
Jun  8 00:21:34.407: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-mt7m" in namespace "provisioning-4942" to be "Succeeded or Failed"
Jun  8 00:21:34.451: INFO: Pod "pod-subpath-test-dynamicpv-mt7m": Phase="Pending", Reason="", readiness=false. Elapsed: 44.33871ms
Jun  8 00:21:36.496: INFO: Pod "pod-subpath-test-dynamicpv-mt7m": Phase="Pending", Reason="", readiness=false. Elapsed: 2.088989219s
Jun  8 00:21:38.544: INFO: Pod "pod-subpath-test-dynamicpv-mt7m": Phase="Pending", Reason="", readiness=false. Elapsed: 4.137577816s
Jun  8 00:21:40.590: INFO: Pod "pod-subpath-test-dynamicpv-mt7m": Phase="Pending", Reason="", readiness=false. Elapsed: 6.182776423s
Jun  8 00:21:42.634: INFO: Pod "pod-subpath-test-dynamicpv-mt7m": Phase="Pending", Reason="", readiness=false. Elapsed: 8.227190192s
Jun  8 00:21:44.682: INFO: Pod "pod-subpath-test-dynamicpv-mt7m": Phase="Pending", Reason="", readiness=false. Elapsed: 10.275159033s
Jun  8 00:21:46.726: INFO: Pod "pod-subpath-test-dynamicpv-mt7m": Phase="Pending", Reason="", readiness=false. Elapsed: 12.319655559s
Jun  8 00:21:48.771: INFO: Pod "pod-subpath-test-dynamicpv-mt7m": Phase="Pending", Reason="", readiness=false. Elapsed: 14.364538122s
Jun  8 00:21:50.817: INFO: Pod "pod-subpath-test-dynamicpv-mt7m": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.410377867s
STEP: Saw pod success
Jun  8 00:21:50.817: INFO: Pod "pod-subpath-test-dynamicpv-mt7m" satisfied condition "Succeeded or Failed"
Jun  8 00:21:50.862: INFO: Trying to get logs from node ip-172-20-41-166.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-mt7m container test-container-subpath-dynamicpv-mt7m: <nil>
STEP: delete the pod
Jun  8 00:21:50.957: INFO: Waiting for pod pod-subpath-test-dynamicpv-mt7m to disappear
Jun  8 00:21:51.002: INFO: Pod pod-subpath-test-dynamicpv-mt7m no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-mt7m
Jun  8 00:21:51.002: INFO: Deleting pod "pod-subpath-test-dynamicpv-mt7m" in namespace "provisioning-4942"
... skipping 289 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.yi3ZpreUa/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.yi3ZpreUa/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.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 242 lines ...
Jun  8 00:21:40.687: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5349-e2e-sc7mcm8
STEP: creating a claim
Jun  8 00:21:40.743: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-mclc
STEP: Creating a pod to test multi_subpath
Jun  8 00:21:40.890: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-mclc" in namespace "provisioning-5349" to be "Succeeded or Failed"
Jun  8 00:21:40.935: INFO: Pod "pod-subpath-test-dynamicpv-mclc": Phase="Pending", Reason="", readiness=false. Elapsed: 45.175307ms
Jun  8 00:21:42.980: INFO: Pod "pod-subpath-test-dynamicpv-mclc": Phase="Pending", Reason="", readiness=false. Elapsed: 2.090484278s
Jun  8 00:21:45.026: INFO: Pod "pod-subpath-test-dynamicpv-mclc": Phase="Pending", Reason="", readiness=false. Elapsed: 4.136185748s
Jun  8 00:21:47.079: INFO: Pod "pod-subpath-test-dynamicpv-mclc": Phase="Pending", Reason="", readiness=false. Elapsed: 6.188852525s
Jun  8 00:21:49.125: INFO: Pod "pod-subpath-test-dynamicpv-mclc": Phase="Pending", Reason="", readiness=false. Elapsed: 8.234699721s
Jun  8 00:21:51.171: INFO: Pod "pod-subpath-test-dynamicpv-mclc": Phase="Pending", Reason="", readiness=false. Elapsed: 10.280795939s
... skipping 3 lines ...
Jun  8 00:21:59.360: INFO: Pod "pod-subpath-test-dynamicpv-mclc": Phase="Pending", Reason="", readiness=false. Elapsed: 18.469935552s
Jun  8 00:22:01.406: INFO: Pod "pod-subpath-test-dynamicpv-mclc": Phase="Pending", Reason="", readiness=false. Elapsed: 20.515977386s
Jun  8 00:22:03.452: INFO: Pod "pod-subpath-test-dynamicpv-mclc": Phase="Pending", Reason="", readiness=false. Elapsed: 22.561987962s
Jun  8 00:22:05.497: INFO: Pod "pod-subpath-test-dynamicpv-mclc": Phase="Pending", Reason="", readiness=false. Elapsed: 24.607384376s
Jun  8 00:22:07.543: INFO: Pod "pod-subpath-test-dynamicpv-mclc": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.652956345s
STEP: Saw pod success
Jun  8 00:22:07.543: INFO: Pod "pod-subpath-test-dynamicpv-mclc" satisfied condition "Succeeded or Failed"
Jun  8 00:22:07.588: INFO: Trying to get logs from node ip-172-20-35-56.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-mclc container test-container-subpath-dynamicpv-mclc: <nil>
STEP: delete the pod
Jun  8 00:22:07.687: INFO: Waiting for pod pod-subpath-test-dynamicpv-mclc to disappear
Jun  8 00:22:07.732: INFO: Pod pod-subpath-test-dynamicpv-mclc no longer exists
STEP: Deleting pod
Jun  8 00:22:07.732: INFO: Deleting pod "pod-subpath-test-dynamicpv-mclc" in namespace "provisioning-5349"
... skipping 418 lines ...
Jun  8 00:21:59.122: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-8747-e2e-scbcnks
STEP: creating a claim
Jun  8 00:21:59.170: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Jun  8 00:21:59.266: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun  8 00:21:59.362: INFO: Error updating pvc ebs.csi.aws.com5jw7d: PersistentVolumeClaim "ebs.csi.aws.com5jw7d" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8747-e2e-scbcnks",
  	... // 2 identical fields
  }

Jun  8 00:22:01.799: INFO: Error updating pvc ebs.csi.aws.com5jw7d: PersistentVolumeClaim "ebs.csi.aws.com5jw7d" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8747-e2e-scbcnks",
  	... // 2 identical fields
  }

Jun  8 00:22:03.503: INFO: Error updating pvc ebs.csi.aws.com5jw7d: PersistentVolumeClaim "ebs.csi.aws.com5jw7d" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8747-e2e-scbcnks",
  	... // 2 identical fields
  }

Jun  8 00:22:05.455: INFO: Error updating pvc ebs.csi.aws.com5jw7d: PersistentVolumeClaim "ebs.csi.aws.com5jw7d" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8747-e2e-scbcnks",
  	... // 2 identical fields
  }

Jun  8 00:22:07.455: INFO: Error updating pvc ebs.csi.aws.com5jw7d: PersistentVolumeClaim "ebs.csi.aws.com5jw7d" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8747-e2e-scbcnks",
  	... // 2 identical fields
  }

Jun  8 00:22:09.456: INFO: Error updating pvc ebs.csi.aws.com5jw7d: PersistentVolumeClaim "ebs.csi.aws.com5jw7d" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8747-e2e-scbcnks",
  	... // 2 identical fields
  }

Jun  8 00:22:11.467: INFO: Error updating pvc ebs.csi.aws.com5jw7d: PersistentVolumeClaim "ebs.csi.aws.com5jw7d" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8747-e2e-scbcnks",
  	... // 2 identical fields
  }

Jun  8 00:22:13.478: INFO: Error updating pvc ebs.csi.aws.com5jw7d: PersistentVolumeClaim "ebs.csi.aws.com5jw7d" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8747-e2e-scbcnks",
  	... // 2 identical fields
  }

Jun  8 00:22:15.458: INFO: Error updating pvc ebs.csi.aws.com5jw7d: PersistentVolumeClaim "ebs.csi.aws.com5jw7d" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8747-e2e-scbcnks",
  	... // 2 identical fields
  }

Jun  8 00:22:17.567: INFO: Error updating pvc ebs.csi.aws.com5jw7d: PersistentVolumeClaim "ebs.csi.aws.com5jw7d" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8747-e2e-scbcnks",
  	... // 2 identical fields
  }

Jun  8 00:22:19.635: INFO: Error updating pvc ebs.csi.aws.com5jw7d: PersistentVolumeClaim "ebs.csi.aws.com5jw7d" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8747-e2e-scbcnks",
  	... // 2 identical fields
  }

Jun  8 00:22:21.501: INFO: Error updating pvc ebs.csi.aws.com5jw7d: PersistentVolumeClaim "ebs.csi.aws.com5jw7d" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8747-e2e-scbcnks",
  	... // 2 identical fields
  }

Jun  8 00:22:23.502: INFO: Error updating pvc ebs.csi.aws.com5jw7d: PersistentVolumeClaim "ebs.csi.aws.com5jw7d" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8747-e2e-scbcnks",
  	... // 2 identical fields
  }

Jun  8 00:22:25.669: INFO: Error updating pvc ebs.csi.aws.com5jw7d: PersistentVolumeClaim "ebs.csi.aws.com5jw7d" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8747-e2e-scbcnks",
  	... // 2 identical fields
  }

Jun  8 00:22:27.932: INFO: Error updating pvc ebs.csi.aws.com5jw7d: PersistentVolumeClaim "ebs.csi.aws.com5jw7d" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8747-e2e-scbcnks",
  	... // 2 identical fields
  }

Jun  8 00:22:29.867: INFO: Error updating pvc ebs.csi.aws.com5jw7d: PersistentVolumeClaim "ebs.csi.aws.com5jw7d" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-8747-e2e-scbcnks",
  	... // 2 identical fields
  }

Jun  8 00:22:30.012: INFO: Error updating pvc ebs.csi.aws.com5jw7d: PersistentVolumeClaim "ebs.csi.aws.com5jw7d" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 123 lines ...
Jun  8 00:22:00.847: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-5274f4d5g
STEP: creating a claim
Jun  8 00:22:00.892: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-ckz7
STEP: Creating a pod to test exec-volume-test
Jun  8 00:22:01.030: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-ckz7" in namespace "volume-5274" to be "Succeeded or Failed"
Jun  8 00:22:01.075: INFO: Pod "exec-volume-test-dynamicpv-ckz7": Phase="Pending", Reason="", readiness=false. Elapsed: 44.673742ms
Jun  8 00:22:03.121: INFO: Pod "exec-volume-test-dynamicpv-ckz7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.090881701s
Jun  8 00:22:05.167: INFO: Pod "exec-volume-test-dynamicpv-ckz7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.136499803s
Jun  8 00:22:07.212: INFO: Pod "exec-volume-test-dynamicpv-ckz7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.182239364s
Jun  8 00:22:09.258: INFO: Pod "exec-volume-test-dynamicpv-ckz7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.227445723s
Jun  8 00:22:11.303: INFO: Pod "exec-volume-test-dynamicpv-ckz7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.273033789s
STEP: Saw pod success
Jun  8 00:22:11.303: INFO: Pod "exec-volume-test-dynamicpv-ckz7" satisfied condition "Succeeded or Failed"
Jun  8 00:22:11.348: INFO: Trying to get logs from node ip-172-20-36-176.ca-central-1.compute.internal pod exec-volume-test-dynamicpv-ckz7 container exec-container-dynamicpv-ckz7: <nil>
STEP: delete the pod
Jun  8 00:22:11.488: INFO: Waiting for pod exec-volume-test-dynamicpv-ckz7 to disappear
Jun  8 00:22:11.539: INFO: Pod exec-volume-test-dynamicpv-ckz7 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-ckz7
Jun  8 00:22:11.540: INFO: Deleting pod "exec-volume-test-dynamicpv-ckz7" in namespace "volume-5274"
... skipping 215 lines ...
Jun  8 00:22:37.354: INFO: Waiting for pod aws-client to disappear
Jun  8 00:22:37.407: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun  8 00:22:37.407: INFO: Deleting PersistentVolumeClaim "pvc-m8bn4"
Jun  8 00:22:37.453: INFO: Deleting PersistentVolume "aws-khqrc"
Jun  8 00:22:37.808: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0f1299a983918cb5b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0f1299a983918cb5b is currently attached to i-0c5448675ce608039
	status code: 400, request id: 6d3352c5-9b1d-456e-8507-5aa9c725223a
Jun  8 00:22:43.160: INFO: Successfully deleted PD "aws://ca-central-1a/vol-0f1299a983918cb5b".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  8 00:22:43.160: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8565" for this suite.
... skipping 631 lines ...
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  8 00:23:07.199: 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.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Jun  8 00:23:07.467: INFO: found topology map[topology.kubernetes.io/zone:ca-central-1a]
Jun  8 00:23:07.467: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  8 00:23:07.467: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.yi3ZpreUa/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.yi3ZpreUa/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (delayed binding)] topology
    /tmp/kops.yi3ZpreUa/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.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 34 lines ...
Jun  8 00:22:07.110: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7819-e2e-sc8dpzs
STEP: creating a claim
Jun  8 00:22:07.157: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-rn4w
STEP: Creating a pod to test subpath
Jun  8 00:22:07.301: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-rn4w" in namespace "provisioning-7819" to be "Succeeded or Failed"
Jun  8 00:22:07.345: INFO: Pod "pod-subpath-test-dynamicpv-rn4w": Phase="Pending", Reason="", readiness=false. Elapsed: 44.057576ms
Jun  8 00:22:09.389: INFO: Pod "pod-subpath-test-dynamicpv-rn4w": Phase="Pending", Reason="", readiness=false. Elapsed: 2.088607628s
Jun  8 00:22:11.438: INFO: Pod "pod-subpath-test-dynamicpv-rn4w": Phase="Pending", Reason="", readiness=false. Elapsed: 4.136767156s
Jun  8 00:22:13.485: INFO: Pod "pod-subpath-test-dynamicpv-rn4w": Phase="Pending", Reason="", readiness=false. Elapsed: 6.184308956s
Jun  8 00:22:15.530: INFO: Pod "pod-subpath-test-dynamicpv-rn4w": Phase="Pending", Reason="", readiness=false. Elapsed: 8.228696612s
Jun  8 00:22:17.574: INFO: Pod "pod-subpath-test-dynamicpv-rn4w": Phase="Pending", Reason="", readiness=false. Elapsed: 10.273107276s
... skipping 2 lines ...
Jun  8 00:22:23.710: INFO: Pod "pod-subpath-test-dynamicpv-rn4w": Phase="Pending", Reason="", readiness=false. Elapsed: 16.409104811s
Jun  8 00:22:25.754: INFO: Pod "pod-subpath-test-dynamicpv-rn4w": Phase="Pending", Reason="", readiness=false. Elapsed: 18.453366012s
Jun  8 00:22:27.799: INFO: Pod "pod-subpath-test-dynamicpv-rn4w": Phase="Pending", Reason="", readiness=false. Elapsed: 20.49863058s
Jun  8 00:22:29.844: INFO: Pod "pod-subpath-test-dynamicpv-rn4w": Phase="Pending", Reason="", readiness=false. Elapsed: 22.543451785s
Jun  8 00:22:31.893: INFO: Pod "pod-subpath-test-dynamicpv-rn4w": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.592411731s
STEP: Saw pod success
Jun  8 00:22:31.893: INFO: Pod "pod-subpath-test-dynamicpv-rn4w" satisfied condition "Succeeded or Failed"
Jun  8 00:22:31.938: INFO: Trying to get logs from node ip-172-20-36-176.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-rn4w container test-container-volume-dynamicpv-rn4w: <nil>
STEP: delete the pod
Jun  8 00:22:32.033: INFO: Waiting for pod pod-subpath-test-dynamicpv-rn4w to disappear
Jun  8 00:22:32.077: INFO: Pod pod-subpath-test-dynamicpv-rn4w no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-rn4w
Jun  8 00:22:32.077: INFO: Deleting pod "pod-subpath-test-dynamicpv-rn4w" in namespace "provisioning-7819"
... skipping 74 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.yi3ZpreUa/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.yi3ZpreUa/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.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 40 lines ...
Jun  8 00:22:28.914: INFO: PersistentVolumeClaim pvc-27t5n found but phase is Pending instead of Bound.
Jun  8 00:22:30.960: INFO: PersistentVolumeClaim pvc-27t5n found and phase=Bound (4.135911723s)
Jun  8 00:22:30.960: INFO: Waiting up to 3m0s for PersistentVolume aws-kwlz8 to have phase Bound
Jun  8 00:22:31.006: INFO: PersistentVolume aws-kwlz8 found and phase=Bound (45.617067ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-w2n6
STEP: Creating a pod to test exec-volume-test
Jun  8 00:22:31.149: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-w2n6" in namespace "volume-4253" to be "Succeeded or Failed"
Jun  8 00:22:31.193: INFO: Pod "exec-volume-test-preprovisionedpv-w2n6": Phase="Pending", Reason="", readiness=false. Elapsed: 43.899968ms
Jun  8 00:22:33.238: INFO: Pod "exec-volume-test-preprovisionedpv-w2n6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.088789013s
Jun  8 00:22:35.294: INFO: Pod "exec-volume-test-preprovisionedpv-w2n6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.144229404s
Jun  8 00:22:37.338: INFO: Pod "exec-volume-test-preprovisionedpv-w2n6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.188526056s
Jun  8 00:22:39.382: INFO: Pod "exec-volume-test-preprovisionedpv-w2n6": Phase="Pending", Reason="", readiness=false. Elapsed: 8.23290732s
Jun  8 00:22:41.427: INFO: Pod "exec-volume-test-preprovisionedpv-w2n6": Phase="Pending", Reason="", readiness=false. Elapsed: 10.277791422s
Jun  8 00:22:43.471: INFO: Pod "exec-volume-test-preprovisionedpv-w2n6": Phase="Pending", Reason="", readiness=false. Elapsed: 12.322085103s
Jun  8 00:22:45.516: INFO: Pod "exec-volume-test-preprovisionedpv-w2n6": Phase="Pending", Reason="", readiness=false. Elapsed: 14.366665967s
Jun  8 00:22:47.561: INFO: Pod "exec-volume-test-preprovisionedpv-w2n6": Phase="Pending", Reason="", readiness=false. Elapsed: 16.411654037s
Jun  8 00:22:49.606: INFO: Pod "exec-volume-test-preprovisionedpv-w2n6": Phase="Pending", Reason="", readiness=false. Elapsed: 18.45685539s
Jun  8 00:22:51.651: INFO: Pod "exec-volume-test-preprovisionedpv-w2n6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.501860904s
STEP: Saw pod success
Jun  8 00:22:51.651: INFO: Pod "exec-volume-test-preprovisionedpv-w2n6" satisfied condition "Succeeded or Failed"
Jun  8 00:22:51.701: INFO: Trying to get logs from node ip-172-20-36-176.ca-central-1.compute.internal pod exec-volume-test-preprovisionedpv-w2n6 container exec-container-preprovisionedpv-w2n6: <nil>
STEP: delete the pod
Jun  8 00:22:51.799: INFO: Waiting for pod exec-volume-test-preprovisionedpv-w2n6 to disappear
Jun  8 00:22:51.843: INFO: Pod exec-volume-test-preprovisionedpv-w2n6 no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-w2n6
Jun  8 00:22:51.843: INFO: Deleting pod "exec-volume-test-preprovisionedpv-w2n6" in namespace "volume-4253"
STEP: Deleting pv and pvc
Jun  8 00:22:51.889: INFO: Deleting PersistentVolumeClaim "pvc-27t5n"
Jun  8 00:22:51.935: INFO: Deleting PersistentVolume "aws-kwlz8"
Jun  8 00:22:52.124: INFO: Couldn't delete PD "aws://ca-central-1a/vol-014b5c09994c84ab9", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-014b5c09994c84ab9 is currently attached to i-05ae10a17dc5bb2c8
	status code: 400, request id: bae4b397-4e87-484a-a889-9dea811cdc5f
Jun  8 00:22:57.476: INFO: Couldn't delete PD "aws://ca-central-1a/vol-014b5c09994c84ab9", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-014b5c09994c84ab9 is currently attached to i-05ae10a17dc5bb2c8
	status code: 400, request id: 95e77a9c-3aa0-482e-868b-a177d0d70e8b
Jun  8 00:23:02.829: INFO: Couldn't delete PD "aws://ca-central-1a/vol-014b5c09994c84ab9", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-014b5c09994c84ab9 is currently attached to i-05ae10a17dc5bb2c8
	status code: 400, request id: 02fffe80-2d48-4b1b-b4a2-f22719bf6260
Jun  8 00:23:08.170: INFO: Successfully deleted PD "aws://ca-central-1a/vol-014b5c09994c84ab9".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  8 00:23:08.170: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-4253" for this suite.
... skipping 23 lines ...
Jun  8 00:22:43.536: INFO: Creating resource for dynamic PV
Jun  8 00:22:43.536: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-92819jnjq
STEP: creating a claim
STEP: Expanding non-expandable pvc
Jun  8 00:22:43.673: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun  8 00:22:43.768: INFO: Error updating pvc aws2rg8m: PersistentVolumeClaim "aws2rg8m" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-92819jnjq",
  	... // 2 identical fields
  }

Jun  8 00:22:45.863: INFO: Error updating pvc aws2rg8m: PersistentVolumeClaim "aws2rg8m" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-92819jnjq",
  	... // 2 identical fields
  }

Jun  8 00:22:47.861: INFO: Error updating pvc aws2rg8m: PersistentVolumeClaim "aws2rg8m" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-92819jnjq",
  	... // 2 identical fields
  }

Jun  8 00:22:49.866: INFO: Error updating pvc aws2rg8m: PersistentVolumeClaim "aws2rg8m" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-92819jnjq",
  	... // 2 identical fields
  }

Jun  8 00:22:51.859: INFO: Error updating pvc aws2rg8m: PersistentVolumeClaim "aws2rg8m" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-92819jnjq",
  	... // 2 identical fields
  }

Jun  8 00:22:53.859: INFO: Error updating pvc aws2rg8m: PersistentVolumeClaim "aws2rg8m" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-92819jnjq",
  	... // 2 identical fields
  }

Jun  8 00:22:55.862: INFO: Error updating pvc aws2rg8m: PersistentVolumeClaim "aws2rg8m" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-92819jnjq",
  	... // 2 identical fields
  }

Jun  8 00:22:57.860: INFO: Error updating pvc aws2rg8m: PersistentVolumeClaim "aws2rg8m" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-92819jnjq",
  	... // 2 identical fields
  }

Jun  8 00:22:59.859: INFO: Error updating pvc aws2rg8m: PersistentVolumeClaim "aws2rg8m" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-92819jnjq",
  	... // 2 identical fields
  }

Jun  8 00:23:01.860: INFO: Error updating pvc aws2rg8m: PersistentVolumeClaim "aws2rg8m" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-92819jnjq",
  	... // 2 identical fields
  }

Jun  8 00:23:03.859: INFO: Error updating pvc aws2rg8m: PersistentVolumeClaim "aws2rg8m" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-92819jnjq",
  	... // 2 identical fields
  }

Jun  8 00:23:05.875: INFO: Error updating pvc aws2rg8m: PersistentVolumeClaim "aws2rg8m" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-92819jnjq",
  	... // 2 identical fields
  }

Jun  8 00:23:07.859: INFO: Error updating pvc aws2rg8m: PersistentVolumeClaim "aws2rg8m" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-92819jnjq",
  	... // 2 identical fields
  }

Jun  8 00:23:09.861: INFO: Error updating pvc aws2rg8m: PersistentVolumeClaim "aws2rg8m" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-92819jnjq",
  	... // 2 identical fields
  }

Jun  8 00:23:11.860: INFO: Error updating pvc aws2rg8m: PersistentVolumeClaim "aws2rg8m" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-92819jnjq",
  	... // 2 identical fields
  }

Jun  8 00:23:13.867: INFO: Error updating pvc aws2rg8m: PersistentVolumeClaim "aws2rg8m" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-92819jnjq",
  	... // 2 identical fields
  }

Jun  8 00:23:13.958: INFO: Error updating pvc aws2rg8m: PersistentVolumeClaim "aws2rg8m" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 167 lines ...

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 109 lines ...
Jun  8 00:23:00.609: INFO: Pod aws-client still exists
Jun  8 00:23:02.610: INFO: Waiting for pod aws-client to disappear
Jun  8 00:23:02.655: INFO: Pod aws-client still exists
Jun  8 00:23:04.610: INFO: Waiting for pod aws-client to disappear
Jun  8 00:23:04.655: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun  8 00:23:04.980: INFO: Couldn't delete PD "aws://ca-central-1a/vol-064c60afdfaa3e751", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-064c60afdfaa3e751 is currently attached to i-0f1ca4a47ab66c5f4
	status code: 400, request id: e441821b-dddd-4c5d-b20d-78e8dd758034
Jun  8 00:23:10.267: INFO: Couldn't delete PD "aws://ca-central-1a/vol-064c60afdfaa3e751", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-064c60afdfaa3e751 is currently attached to i-0f1ca4a47ab66c5f4
	status code: 400, request id: 4326c646-e776-4a94-9744-785e9e5b1b22
Jun  8 00:23:15.593: INFO: Couldn't delete PD "aws://ca-central-1a/vol-064c60afdfaa3e751", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-064c60afdfaa3e751 is currently attached to i-0f1ca4a47ab66c5f4
	status code: 400, request id: 77ee8955-e986-484c-a833-b5a57eaacf43
Jun  8 00:23:20.903: INFO: Successfully deleted PD "aws://ca-central-1a/vol-064c60afdfaa3e751".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  8 00:23:20.903: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8802" for this suite.
... skipping 23 lines ...
Jun  8 00:22:25.505: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-9133-e2e-scwp65q
STEP: creating a claim
Jun  8 00:22:25.549: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-6pjl
STEP: Creating a pod to test exec-volume-test
Jun  8 00:22:25.686: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-6pjl" in namespace "volume-9133" to be "Succeeded or Failed"
Jun  8 00:22:25.730: INFO: Pod "exec-volume-test-dynamicpv-6pjl": Phase="Pending", Reason="", readiness=false. Elapsed: 44.136758ms
Jun  8 00:22:27.775: INFO: Pod "exec-volume-test-dynamicpv-6pjl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.088391721s
Jun  8 00:22:29.820: INFO: Pod "exec-volume-test-dynamicpv-6pjl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.133628053s
Jun  8 00:22:31.865: INFO: Pod "exec-volume-test-dynamicpv-6pjl": Phase="Pending", Reason="", readiness=false. Elapsed: 6.179113549s
Jun  8 00:22:33.911: INFO: Pod "exec-volume-test-dynamicpv-6pjl": Phase="Pending", Reason="", readiness=false. Elapsed: 8.224648312s
Jun  8 00:22:35.957: INFO: Pod "exec-volume-test-dynamicpv-6pjl": Phase="Pending", Reason="", readiness=false. Elapsed: 10.270464592s
... skipping 2 lines ...
Jun  8 00:22:42.091: INFO: Pod "exec-volume-test-dynamicpv-6pjl": Phase="Pending", Reason="", readiness=false. Elapsed: 16.404847903s
Jun  8 00:22:44.135: INFO: Pod "exec-volume-test-dynamicpv-6pjl": Phase="Pending", Reason="", readiness=false. Elapsed: 18.449038606s
Jun  8 00:22:46.180: INFO: Pod "exec-volume-test-dynamicpv-6pjl": Phase="Pending", Reason="", readiness=false. Elapsed: 20.493520396s
Jun  8 00:22:48.224: INFO: Pod "exec-volume-test-dynamicpv-6pjl": Phase="Pending", Reason="", readiness=false. Elapsed: 22.537859057s
Jun  8 00:22:50.269: INFO: Pod "exec-volume-test-dynamicpv-6pjl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.583123058s
STEP: Saw pod success
Jun  8 00:22:50.269: INFO: Pod "exec-volume-test-dynamicpv-6pjl" satisfied condition "Succeeded or Failed"
Jun  8 00:22:50.313: INFO: Trying to get logs from node ip-172-20-48-35.ca-central-1.compute.internal pod exec-volume-test-dynamicpv-6pjl container exec-container-dynamicpv-6pjl: <nil>
STEP: delete the pod
Jun  8 00:22:50.407: INFO: Waiting for pod exec-volume-test-dynamicpv-6pjl to disappear
Jun  8 00:22:50.453: INFO: Pod exec-volume-test-dynamicpv-6pjl no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-6pjl
Jun  8 00:22:50.453: INFO: Deleting pod "exec-volume-test-dynamicpv-6pjl" in namespace "volume-9133"
... skipping 62 lines ...
Jun  8 00:22:59.156: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-9444-e2e-sch5hjq
STEP: creating a claim
Jun  8 00:22:59.201: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-pn5z
STEP: Creating a pod to test exec-volume-test
Jun  8 00:22:59.340: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-pn5z" in namespace "volume-9444" to be "Succeeded or Failed"
Jun  8 00:22:59.384: INFO: Pod "exec-volume-test-dynamicpv-pn5z": Phase="Pending", Reason="", readiness=false. Elapsed: 44.322032ms
Jun  8 00:23:01.429: INFO: Pod "exec-volume-test-dynamicpv-pn5z": Phase="Pending", Reason="", readiness=false. Elapsed: 2.088780835s
Jun  8 00:23:03.474: INFO: Pod "exec-volume-test-dynamicpv-pn5z": Phase="Pending", Reason="", readiness=false. Elapsed: 4.134661314s
Jun  8 00:23:05.519: INFO: Pod "exec-volume-test-dynamicpv-pn5z": Phase="Pending", Reason="", readiness=false. Elapsed: 6.179292223s
Jun  8 00:23:07.564: INFO: Pod "exec-volume-test-dynamicpv-pn5z": Phase="Pending", Reason="", readiness=false. Elapsed: 8.22448171s
Jun  8 00:23:09.610: INFO: Pod "exec-volume-test-dynamicpv-pn5z": Phase="Pending", Reason="", readiness=false. Elapsed: 10.269804554s
Jun  8 00:23:11.654: INFO: Pod "exec-volume-test-dynamicpv-pn5z": Phase="Pending", Reason="", readiness=false. Elapsed: 12.314201514s
Jun  8 00:23:13.699: INFO: Pod "exec-volume-test-dynamicpv-pn5z": Phase="Pending", Reason="", readiness=false. Elapsed: 14.359624827s
Jun  8 00:23:15.744: INFO: Pod "exec-volume-test-dynamicpv-pn5z": Phase="Pending", Reason="", readiness=false. Elapsed: 16.40420818s
Jun  8 00:23:17.792: INFO: Pod "exec-volume-test-dynamicpv-pn5z": Phase="Pending", Reason="", readiness=false. Elapsed: 18.452527145s
Jun  8 00:23:19.837: INFO: Pod "exec-volume-test-dynamicpv-pn5z": Phase="Pending", Reason="", readiness=false. Elapsed: 20.496882682s
Jun  8 00:23:21.881: INFO: Pod "exec-volume-test-dynamicpv-pn5z": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.541386437s
STEP: Saw pod success
Jun  8 00:23:21.881: INFO: Pod "exec-volume-test-dynamicpv-pn5z" satisfied condition "Succeeded or Failed"
Jun  8 00:23:21.925: INFO: Trying to get logs from node ip-172-20-41-166.ca-central-1.compute.internal pod exec-volume-test-dynamicpv-pn5z container exec-container-dynamicpv-pn5z: <nil>
STEP: delete the pod
Jun  8 00:23:22.028: INFO: Waiting for pod exec-volume-test-dynamicpv-pn5z to disappear
Jun  8 00:23:22.072: INFO: Pod exec-volume-test-dynamicpv-pn5z no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-pn5z
Jun  8 00:23:22.073: INFO: Deleting pod "exec-volume-test-dynamicpv-pn5z" in namespace "volume-9444"
... skipping 318 lines ...
Jun  8 00:23:08.488: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-237-e2e-sc5nk8l
STEP: creating a claim
Jun  8 00:23:08.534: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-kr9d
STEP: Creating a pod to test subpath
Jun  8 00:23:08.670: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-kr9d" in namespace "provisioning-237" to be "Succeeded or Failed"
Jun  8 00:23:08.714: INFO: Pod "pod-subpath-test-dynamicpv-kr9d": Phase="Pending", Reason="", readiness=false. Elapsed: 44.061306ms
Jun  8 00:23:10.759: INFO: Pod "pod-subpath-test-dynamicpv-kr9d": Phase="Pending", Reason="", readiness=false. Elapsed: 2.08897492s
Jun  8 00:23:12.805: INFO: Pod "pod-subpath-test-dynamicpv-kr9d": Phase="Pending", Reason="", readiness=false. Elapsed: 4.134764644s
Jun  8 00:23:14.849: INFO: Pod "pod-subpath-test-dynamicpv-kr9d": Phase="Pending", Reason="", readiness=false. Elapsed: 6.179406546s
Jun  8 00:23:16.895: INFO: Pod "pod-subpath-test-dynamicpv-kr9d": Phase="Pending", Reason="", readiness=false. Elapsed: 8.22540412s
Jun  8 00:23:18.940: INFO: Pod "pod-subpath-test-dynamicpv-kr9d": Phase="Pending", Reason="", readiness=false. Elapsed: 10.27037627s
Jun  8 00:23:20.985: INFO: Pod "pod-subpath-test-dynamicpv-kr9d": Phase="Pending", Reason="", readiness=false. Elapsed: 12.315669537s
Jun  8 00:23:23.030: INFO: Pod "pod-subpath-test-dynamicpv-kr9d": Phase="Pending", Reason="", readiness=false. Elapsed: 14.360330087s
Jun  8 00:23:25.075: INFO: Pod "pod-subpath-test-dynamicpv-kr9d": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.405257304s
STEP: Saw pod success
Jun  8 00:23:25.075: INFO: Pod "pod-subpath-test-dynamicpv-kr9d" satisfied condition "Succeeded or Failed"
Jun  8 00:23:25.119: INFO: Trying to get logs from node ip-172-20-41-166.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-kr9d container test-container-volume-dynamicpv-kr9d: <nil>
STEP: delete the pod
Jun  8 00:23:25.215: INFO: Waiting for pod pod-subpath-test-dynamicpv-kr9d to disappear
Jun  8 00:23:25.260: INFO: Pod pod-subpath-test-dynamicpv-kr9d no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-kr9d
Jun  8 00:23:25.260: INFO: Deleting pod "pod-subpath-test-dynamicpv-kr9d" in namespace "provisioning-237"
... skipping 36 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.yi3ZpreUa/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.yi3ZpreUa/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.yi3ZpreUa/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.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 162 lines ...
Jun  8 00:21:08.542: INFO: Creating resource for dynamic PV
Jun  8 00:21:08.542: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-8095-e2e-scsd85z
STEP: creating a claim
Jun  8 00:21:08.588: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun  8 00:21:08.726: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-tswkm" in namespace "snapshotting-8095" to be "Succeeded or Failed"
Jun  8 00:21:08.770: INFO: Pod "pvc-snapshottable-tester-tswkm": Phase="Pending", Reason="", readiness=false. Elapsed: 44.014411ms
Jun  8 00:21:10.820: INFO: Pod "pvc-snapshottable-tester-tswkm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.093816761s
Jun  8 00:21:12.865: INFO: Pod "pvc-snapshottable-tester-tswkm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.139000624s
Jun  8 00:21:14.910: INFO: Pod "pvc-snapshottable-tester-tswkm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.184118891s
Jun  8 00:21:16.956: INFO: Pod "pvc-snapshottable-tester-tswkm": Phase="Pending", Reason="", readiness=false. Elapsed: 8.229489458s
Jun  8 00:21:19.002: INFO: Pod "pvc-snapshottable-tester-tswkm": Phase="Pending", Reason="", readiness=false. Elapsed: 10.275508791s
... skipping 3 lines ...
Jun  8 00:21:27.181: INFO: Pod "pvc-snapshottable-tester-tswkm": Phase="Pending", Reason="", readiness=false. Elapsed: 18.454457255s
Jun  8 00:21:29.229: INFO: Pod "pvc-snapshottable-tester-tswkm": Phase="Pending", Reason="", readiness=false. Elapsed: 20.502742389s
Jun  8 00:21:31.274: INFO: Pod "pvc-snapshottable-tester-tswkm": Phase="Pending", Reason="", readiness=false. Elapsed: 22.547706629s
Jun  8 00:21:33.321: INFO: Pod "pvc-snapshottable-tester-tswkm": Phase="Pending", Reason="", readiness=false. Elapsed: 24.594554724s
Jun  8 00:21:35.365: INFO: Pod "pvc-snapshottable-tester-tswkm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.638979808s
STEP: Saw pod success
Jun  8 00:21:35.365: INFO: Pod "pvc-snapshottable-tester-tswkm" satisfied condition "Succeeded or Failed"
Jun  8 00:21:35.752: INFO: Pod pvc-snapshottable-tester-tswkm has the following logs: 
Jun  8 00:21:35.752: INFO: Deleting pod "pvc-snapshottable-tester-tswkm" in namespace "snapshotting-8095"
Jun  8 00:21:35.810: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-tswkm" to be fully deleted
Jun  8 00:21:35.854: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comtwgkn] to have phase Bound
Jun  8 00:21:35.901: INFO: PersistentVolumeClaim ebs.csi.aws.comtwgkn found and phase=Bound (47.214354ms)
STEP: [init] checking the claim
... skipping 17 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:243
STEP: checking the snapshot
STEP: checking the SnapshotContent
STEP: Modifying source data test
STEP: modifying the data in the source PVC
Jun  8 00:21:50.745: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-9nz7h" in namespace "snapshotting-8095" to be "Succeeded or Failed"
Jun  8 00:21:50.789: INFO: Pod "pvc-snapshottable-data-tester-9nz7h": Phase="Pending", Reason="", readiness=false. Elapsed: 44.494085ms
Jun  8 00:21:52.835: INFO: Pod "pvc-snapshottable-data-tester-9nz7h": Phase="Pending", Reason="", readiness=false. Elapsed: 2.089973146s
Jun  8 00:21:54.880: INFO: Pod "pvc-snapshottable-data-tester-9nz7h": Phase="Pending", Reason="", readiness=false. Elapsed: 4.135530276s
Jun  8 00:21:56.926: INFO: Pod "pvc-snapshottable-data-tester-9nz7h": Phase="Pending", Reason="", readiness=false. Elapsed: 6.180956468s
Jun  8 00:21:58.971: INFO: Pod "pvc-snapshottable-data-tester-9nz7h": Phase="Pending", Reason="", readiness=false. Elapsed: 8.226570857s
Jun  8 00:22:01.016: INFO: Pod "pvc-snapshottable-data-tester-9nz7h": Phase="Pending", Reason="", readiness=false. Elapsed: 10.270929324s
Jun  8 00:22:03.060: INFO: Pod "pvc-snapshottable-data-tester-9nz7h": Phase="Pending", Reason="", readiness=false. Elapsed: 12.315434355s
Jun  8 00:22:05.106: INFO: Pod "pvc-snapshottable-data-tester-9nz7h": Phase="Pending", Reason="", readiness=false. Elapsed: 14.360988872s
Jun  8 00:22:07.151: INFO: Pod "pvc-snapshottable-data-tester-9nz7h": Phase="Pending", Reason="", readiness=false. Elapsed: 16.406520806s
Jun  8 00:22:09.196: INFO: Pod "pvc-snapshottable-data-tester-9nz7h": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.451317349s
STEP: Saw pod success
Jun  8 00:22:09.196: INFO: Pod "pvc-snapshottable-data-tester-9nz7h" satisfied condition "Succeeded or Failed"
Jun  8 00:22:09.286: INFO: Pod pvc-snapshottable-data-tester-9nz7h has the following logs: 
Jun  8 00:22:09.286: INFO: Deleting pod "pvc-snapshottable-data-tester-9nz7h" in namespace "snapshotting-8095"
Jun  8 00:22:09.339: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-9nz7h" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun  8 00:22:49.566: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-8095 exec restored-pvc-tester-2kcp5 --namespace=snapshotting-8095 -- cat /mnt/test/data'
... skipping 32 lines ...
Jun  8 00:23:14.449: INFO: volumesnapshotcontents snapcontent-58ee7103-eeda-4eab-9037-155176cbb77d has been found and is not deleted
Jun  8 00:23:15.494: INFO: volumesnapshotcontents snapcontent-58ee7103-eeda-4eab-9037-155176cbb77d has been found and is not deleted
Jun  8 00:23:16.540: INFO: volumesnapshotcontents snapcontent-58ee7103-eeda-4eab-9037-155176cbb77d has been found and is not deleted
Jun  8 00:23:17.585: INFO: volumesnapshotcontents snapcontent-58ee7103-eeda-4eab-9037-155176cbb77d has been found and is not deleted
Jun  8 00:23:18.631: INFO: volumesnapshotcontents snapcontent-58ee7103-eeda-4eab-9037-155176cbb77d has been found and is not deleted
Jun  8 00:23:19.677: INFO: volumesnapshotcontents snapcontent-58ee7103-eeda-4eab-9037-155176cbb77d has been found and is not deleted
Jun  8 00:23:20.678: INFO: WaitUntil failed after reaching the timeout 30s
[AfterEach] volume snapshot controller
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:221
Jun  8 00:23:20.726: INFO: Pod restored-pvc-tester-2kcp5 has the following logs: 
Jun  8 00:23:20.726: INFO: Deleting pod "restored-pvc-tester-2kcp5" in namespace "snapshotting-8095"
Jun  8 00:23:20.777: INFO: Wait up to 5m0s for pod "restored-pvc-tester-2kcp5" to be fully deleted
Jun  8 00:23:58.866: INFO: deleting claim "snapshotting-8095"/"pvc-5nqjj"
... skipping 107 lines ...
Jun  8 00:23:21.226: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-25622jkkc
STEP: creating a claim
Jun  8 00:23:21.271: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-jcs6
STEP: Creating a pod to test subpath
Jun  8 00:23:21.409: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-jcs6" in namespace "provisioning-2562" to be "Succeeded or Failed"
Jun  8 00:23:21.454: INFO: Pod "pod-subpath-test-dynamicpv-jcs6": Phase="Pending", Reason="", readiness=false. Elapsed: 45.029756ms
Jun  8 00:23:23.506: INFO: Pod "pod-subpath-test-dynamicpv-jcs6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.097341703s
Jun  8 00:23:25.555: INFO: Pod "pod-subpath-test-dynamicpv-jcs6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.145717497s
Jun  8 00:23:27.600: INFO: Pod "pod-subpath-test-dynamicpv-jcs6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.191099562s
Jun  8 00:23:29.646: INFO: Pod "pod-subpath-test-dynamicpv-jcs6": Phase="Pending", Reason="", readiness=false. Elapsed: 8.237317404s
Jun  8 00:23:31.692: INFO: Pod "pod-subpath-test-dynamicpv-jcs6": Phase="Pending", Reason="", readiness=false. Elapsed: 10.283430453s
Jun  8 00:23:33.738: INFO: Pod "pod-subpath-test-dynamicpv-jcs6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.329564301s
STEP: Saw pod success
Jun  8 00:23:33.739: INFO: Pod "pod-subpath-test-dynamicpv-jcs6" satisfied condition "Succeeded or Failed"
Jun  8 00:23:33.784: INFO: Trying to get logs from node ip-172-20-48-35.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-jcs6 container test-container-subpath-dynamicpv-jcs6: <nil>
STEP: delete the pod
Jun  8 00:23:33.883: INFO: Waiting for pod pod-subpath-test-dynamicpv-jcs6 to disappear
Jun  8 00:23:33.928: INFO: Pod pod-subpath-test-dynamicpv-jcs6 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-jcs6
Jun  8 00:23:33.928: INFO: Deleting pod "pod-subpath-test-dynamicpv-jcs6" in namespace "provisioning-2562"
... skipping 267 lines ...
Jun  8 00:23:01.402: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-9151gzqbf      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-9151    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-9151gzqbf,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-9151    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-9151gzqbf,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-9151    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-9151gzqbf,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-9151gzqbf    6fb98d47-5271-4ddf-b274-99d1de5954a1 6362 0 2021-06-08 00:23:01 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-08 00:23:01 +0000 UTC FieldsV1 {"f:mountOptions":{},"f:provisioner":{},"f:reclaimPolicy":{},"f:volumeBindingMode":{}}}]},Provisioner:kubernetes.io/aws-ebs,Parameters:map[string]string{},ReclaimPolicy:*Delete,MountOptions:[debug nouid32],AllowVolumeExpansion:nil,VolumeBindingMode:*WaitForFirstConsumer,AllowedTopologies:[]TopologySelectorTerm{},} claim=&PersistentVolumeClaim{ObjectMeta:{pvc-thqcw pvc- provisioning-9151  c6bc4935-6cb2-4ee3-9b7f-fed571b2ca86 6363 0 2021-06-08 00:23:01 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-08 00:23:01 +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-9151gzqbf,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-08445c02-4197-4e4c-9a5e-76ad1f864406 in namespace provisioning-9151
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun  8 00:23:15.934: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-xrf69" in namespace "provisioning-9151" to be "Succeeded or Failed"
Jun  8 00:23:15.981: INFO: Pod "pvc-volume-tester-writer-xrf69": Phase="Pending", Reason="", readiness=false. Elapsed: 46.171212ms
Jun  8 00:23:18.036: INFO: Pod "pvc-volume-tester-writer-xrf69": Phase="Pending", Reason="", readiness=false. Elapsed: 2.101665629s
Jun  8 00:23:20.081: INFO: Pod "pvc-volume-tester-writer-xrf69": Phase="Pending", Reason="", readiness=false. Elapsed: 4.146159275s
Jun  8 00:23:22.128: INFO: Pod "pvc-volume-tester-writer-xrf69": Phase="Pending", Reason="", readiness=false. Elapsed: 6.193379963s
Jun  8 00:23:24.173: INFO: Pod "pvc-volume-tester-writer-xrf69": Phase="Pending", Reason="", readiness=false. Elapsed: 8.238278301s
Jun  8 00:23:26.217: INFO: Pod "pvc-volume-tester-writer-xrf69": Phase="Pending", Reason="", readiness=false. Elapsed: 10.282975898s
... skipping 8 lines ...
Jun  8 00:23:44.625: INFO: Pod "pvc-volume-tester-writer-xrf69": Phase="Pending", Reason="", readiness=false. Elapsed: 28.69086921s
Jun  8 00:23:46.670: INFO: Pod "pvc-volume-tester-writer-xrf69": Phase="Pending", Reason="", readiness=false. Elapsed: 30.735986344s
Jun  8 00:23:48.716: INFO: Pod "pvc-volume-tester-writer-xrf69": Phase="Pending", Reason="", readiness=false. Elapsed: 32.781707625s
Jun  8 00:23:50.761: INFO: Pod "pvc-volume-tester-writer-xrf69": Phase="Pending", Reason="", readiness=false. Elapsed: 34.82676166s
Jun  8 00:23:52.806: INFO: Pod "pvc-volume-tester-writer-xrf69": Phase="Succeeded", Reason="", readiness=false. Elapsed: 36.871414184s
STEP: Saw pod success
Jun  8 00:23:52.806: INFO: Pod "pvc-volume-tester-writer-xrf69" satisfied condition "Succeeded or Failed"
Jun  8 00:23:52.896: INFO: Pod pvc-volume-tester-writer-xrf69 has the following logs: 
Jun  8 00:23:52.896: INFO: Deleting pod "pvc-volume-tester-writer-xrf69" in namespace "provisioning-9151"
Jun  8 00:23:52.948: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-xrf69" to be fully deleted
STEP: checking the created volume has the correct mount options, is readable and retains data on the same node "ip-172-20-35-56.ca-central-1.compute.internal"
Jun  8 00:23:53.131: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-8gbtp" in namespace "provisioning-9151" to be "Succeeded or Failed"
Jun  8 00:23:53.175: INFO: Pod "pvc-volume-tester-reader-8gbtp": Phase="Pending", Reason="", readiness=false. Elapsed: 44.137202ms
Jun  8 00:23:55.221: INFO: Pod "pvc-volume-tester-reader-8gbtp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.090298349s
Jun  8 00:23:57.267: INFO: Pod "pvc-volume-tester-reader-8gbtp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.13566481s
STEP: Saw pod success
Jun  8 00:23:57.267: INFO: Pod "pvc-volume-tester-reader-8gbtp" satisfied condition "Succeeded or Failed"
Jun  8 00:23:57.360: INFO: Pod pvc-volume-tester-reader-8gbtp has the following logs: hello world

Jun  8 00:23:57.360: INFO: Deleting pod "pvc-volume-tester-reader-8gbtp" in namespace "provisioning-9151"
Jun  8 00:23:57.422: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-8gbtp" to be fully deleted
Jun  8 00:23:57.466: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-thqcw] to have phase Bound
Jun  8 00:23:57.510: INFO: PersistentVolumeClaim pvc-thqcw found and phase=Bound (44.089881ms)
... skipping 303 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  8 00:23:07.818: 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.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  8 00:23:08.039: INFO: Creating resource for dynamic PV
Jun  8 00:23:08.039: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-6842-e2e-scxrrvh
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  8 00:23:14.356: INFO: Deleting pod "pod-997c71c4-1a24-443f-8955-971071f97fdc" in namespace "volumemode-6842"
Jun  8 00:23:14.401: INFO: Wait up to 5m0s for pod "pod-997c71c4-1a24-443f-8955-971071f97fdc" to be fully deleted
STEP: Deleting pvc
Jun  8 00:23:18.592: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comvfqbv"
Jun  8 00:23:18.639: INFO: Waiting up to 5m0s for PersistentVolume pvc-9024c8bd-4b1d-4b7c-ab45-9c8f2ad9ba7f to get deleted
Jun  8 00:23:18.684: INFO: PersistentVolume pvc-9024c8bd-4b1d-4b7c-ab45-9c8f2ad9ba7f found and phase=Released (44.96526ms)
... skipping 19 lines ...

• [SLOW TEST:76.642 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.yi3ZpreUa/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.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  8 00:24:24.462: INFO: Driver "ebs.csi.aws.com" does not support volume type "InlineVolume" - skipping
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
... skipping 52 lines ...
STEP: Deleting pod hostexec-ip-172-20-48-35.ca-central-1.compute.internal-79lgx in namespace volumemode-4529
Jun  8 00:23:50.559: INFO: Deleting pod "pod-0518a778-cb1b-4f62-ae89-1380d1adfa8a" in namespace "volumemode-4529"
Jun  8 00:23:50.604: INFO: Wait up to 5m0s for pod "pod-0518a778-cb1b-4f62-ae89-1380d1adfa8a" to be fully deleted
STEP: Deleting pv and pvc
Jun  8 00:23:58.693: INFO: Deleting PersistentVolumeClaim "pvc-n4vkl"
Jun  8 00:23:58.739: INFO: Deleting PersistentVolume "aws-dg4g6"
Jun  8 00:23:58.937: INFO: Couldn't delete PD "aws://ca-central-1a/vol-08fde355c7f501c2c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08fde355c7f501c2c is currently attached to i-0c5448675ce608039
	status code: 400, request id: fcfeb770-b5b5-4e17-9ac0-abcda5bcdd3e
Jun  8 00:24:04.288: INFO: Couldn't delete PD "aws://ca-central-1a/vol-08fde355c7f501c2c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08fde355c7f501c2c is currently attached to i-0c5448675ce608039
	status code: 400, request id: 2516858b-31c9-4dd5-be66-fcb19e0fa722
Jun  8 00:24:09.632: INFO: Couldn't delete PD "aws://ca-central-1a/vol-08fde355c7f501c2c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08fde355c7f501c2c is currently attached to i-0c5448675ce608039
	status code: 400, request id: 21326965-1b01-4c95-9d90-b9d87a901293
Jun  8 00:24:14.952: INFO: Couldn't delete PD "aws://ca-central-1a/vol-08fde355c7f501c2c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08fde355c7f501c2c is currently attached to i-0c5448675ce608039
	status code: 400, request id: 521789b4-6a0a-442f-9370-e0d051f690da
Jun  8 00:24:20.239: INFO: Couldn't delete PD "aws://ca-central-1a/vol-08fde355c7f501c2c", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08fde355c7f501c2c is currently attached to i-0c5448675ce608039
	status code: 400, request id: dabbe5bd-b066-4737-9da0-400be6270d5a
Jun  8 00:24:25.523: INFO: Successfully deleted PD "aws://ca-central-1a/vol-08fde355c7f501c2c".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  8 00:24:25.523: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-4529" for this suite.
... skipping 255 lines ...

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

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

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 299 lines ...
Jun  8 00:22:21.331: INFO: Creating resource for dynamic PV
Jun  8 00:22:21.331: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-2813-e2e-scpnfwc
STEP: creating a claim
Jun  8 00:22:21.383: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun  8 00:22:21.527: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-6rqjt" in namespace "snapshotting-2813" to be "Succeeded or Failed"
Jun  8 00:22:21.575: INFO: Pod "pvc-snapshottable-tester-6rqjt": Phase="Pending", Reason="", readiness=false. Elapsed: 47.653853ms
Jun  8 00:22:23.620: INFO: Pod "pvc-snapshottable-tester-6rqjt": Phase="Pending", Reason="", readiness=false. Elapsed: 2.093379942s
Jun  8 00:22:25.667: INFO: Pod "pvc-snapshottable-tester-6rqjt": Phase="Pending", Reason="", readiness=false. Elapsed: 4.139498977s
Jun  8 00:22:27.712: INFO: Pod "pvc-snapshottable-tester-6rqjt": Phase="Pending", Reason="", readiness=false. Elapsed: 6.185104009s
Jun  8 00:22:29.759: INFO: Pod "pvc-snapshottable-tester-6rqjt": Phase="Pending", Reason="", readiness=false. Elapsed: 8.231529059s
Jun  8 00:22:31.808: INFO: Pod "pvc-snapshottable-tester-6rqjt": Phase="Pending", Reason="", readiness=false. Elapsed: 10.281088586s
Jun  8 00:22:33.854: INFO: Pod "pvc-snapshottable-tester-6rqjt": Phase="Pending", Reason="", readiness=false. Elapsed: 12.326788981s
Jun  8 00:22:35.901: INFO: Pod "pvc-snapshottable-tester-6rqjt": Phase="Pending", Reason="", readiness=false. Elapsed: 14.374089384s
Jun  8 00:22:37.948: INFO: Pod "pvc-snapshottable-tester-6rqjt": Phase="Pending", Reason="", readiness=false. Elapsed: 16.420693726s
Jun  8 00:22:39.994: INFO: Pod "pvc-snapshottable-tester-6rqjt": Phase="Pending", Reason="", readiness=false. Elapsed: 18.467375028s
Jun  8 00:22:42.040: INFO: Pod "pvc-snapshottable-tester-6rqjt": Phase="Pending", Reason="", readiness=false. Elapsed: 20.513141188s
Jun  8 00:22:44.086: INFO: Pod "pvc-snapshottable-tester-6rqjt": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.558877273s
STEP: Saw pod success
Jun  8 00:22:44.086: INFO: Pod "pvc-snapshottable-tester-6rqjt" satisfied condition "Succeeded or Failed"
Jun  8 00:22:44.179: INFO: Pod pvc-snapshottable-tester-6rqjt has the following logs: 
Jun  8 00:22:44.179: INFO: Deleting pod "pvc-snapshottable-tester-6rqjt" in namespace "snapshotting-2813"
Jun  8 00:22:44.229: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-6rqjt" to be fully deleted
Jun  8 00:22:44.274: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comttrff] to have phase Bound
Jun  8 00:22:44.324: INFO: PersistentVolumeClaim ebs.csi.aws.comttrff found and phase=Bound (49.660522ms)
STEP: [init] checking the claim
... skipping 15 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:243
STEP: checking the snapshot
STEP: checking the SnapshotContent
STEP: Modifying source data test
STEP: modifying the data in the source PVC
Jun  8 00:22:55.071: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-f8ls2" in namespace "snapshotting-2813" to be "Succeeded or Failed"
Jun  8 00:22:55.117: INFO: Pod "pvc-snapshottable-data-tester-f8ls2": Phase="Pending", Reason="", readiness=false. Elapsed: 45.263151ms
Jun  8 00:22:57.162: INFO: Pod "pvc-snapshottable-data-tester-f8ls2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.090839865s
Jun  8 00:22:59.210: INFO: Pod "pvc-snapshottable-data-tester-f8ls2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.138850011s
Jun  8 00:23:01.256: INFO: Pod "pvc-snapshottable-data-tester-f8ls2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.184434714s
Jun  8 00:23:03.305: INFO: Pod "pvc-snapshottable-data-tester-f8ls2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.233486819s
Jun  8 00:23:05.351: INFO: Pod "pvc-snapshottable-data-tester-f8ls2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.280062657s
... skipping 7 lines ...
Jun  8 00:23:21.723: INFO: Pod "pvc-snapshottable-data-tester-f8ls2": Phase="Pending", Reason="", readiness=false. Elapsed: 26.651987118s
Jun  8 00:23:23.769: INFO: Pod "pvc-snapshottable-data-tester-f8ls2": Phase="Pending", Reason="", readiness=false. Elapsed: 28.69757429s
Jun  8 00:23:25.816: INFO: Pod "pvc-snapshottable-data-tester-f8ls2": Phase="Pending", Reason="", readiness=false. Elapsed: 30.744745587s
Jun  8 00:23:27.863: INFO: Pod "pvc-snapshottable-data-tester-f8ls2": Phase="Pending", Reason="", readiness=false. Elapsed: 32.791458369s
Jun  8 00:23:29.909: INFO: Pod "pvc-snapshottable-data-tester-f8ls2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.837929308s
STEP: Saw pod success
Jun  8 00:23:29.909: INFO: Pod "pvc-snapshottable-data-tester-f8ls2" satisfied condition "Succeeded or Failed"
Jun  8 00:23:30.002: INFO: Pod pvc-snapshottable-data-tester-f8ls2 has the following logs: 
Jun  8 00:23:30.002: INFO: Deleting pod "pvc-snapshottable-data-tester-f8ls2" in namespace "snapshotting-2813"
Jun  8 00:23:30.050: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-f8ls2" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun  8 00:23:54.283: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-2813 exec restored-pvc-tester-rm87m --namespace=snapshotting-2813 -- cat /mnt/test/data'
... skipping 459 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.yi3ZpreUa/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.yi3ZpreUa/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.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 273 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  8 00:24:04.601: 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.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun  8 00:24:04.823: INFO: Creating resource for dynamic PV
Jun  8 00:24:04.823: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8071-e2e-sc56vfw
STEP: creating a claim
Jun  8 00:24:04.869: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-lxzc
STEP: Checking for subpath error in container status
Jun  8 00:24:45.094: INFO: Deleting pod "pod-subpath-test-dynamicpv-lxzc" in namespace "provisioning-8071"
Jun  8 00:24:45.143: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-lxzc" to be fully deleted
STEP: Deleting pod
Jun  8 00:24:55.233: INFO: Deleting pod "pod-subpath-test-dynamicpv-lxzc" in namespace "provisioning-8071"
STEP: Deleting pvc
Jun  8 00:24:55.371: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com49nb4"
... skipping 11 lines ...

• [SLOW TEST:66.133 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.yi3ZpreUa/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.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (ext3)] volumes
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  8 00:25:10.737: INFO: Driver "ebs.csi.aws.com" does not support volume type "PreprovisionedPV" - skipping
[AfterEach] [Testpattern: Pre-provisioned PV (ext3)] volumes
... skipping 25 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.yi3ZpreUa/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.yi3ZpreUa/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.yi3ZpreUa/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.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 273 lines ...
Jun  8 00:23:14.425: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5279-e2e-scmsdtc
STEP: creating a claim
Jun  8 00:23:14.472: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-mj5x
STEP: Creating a pod to test subpath
Jun  8 00:23:14.613: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-mj5x" in namespace "provisioning-5279" to be "Succeeded or Failed"
Jun  8 00:23:14.659: INFO: Pod "pod-subpath-test-dynamicpv-mj5x": Phase="Pending", Reason="", readiness=false. Elapsed: 45.998851ms
Jun  8 00:23:16.705: INFO: Pod "pod-subpath-test-dynamicpv-mj5x": Phase="Pending", Reason="", readiness=false. Elapsed: 2.091177768s
Jun  8 00:23:18.751: INFO: Pod "pod-subpath-test-dynamicpv-mj5x": Phase="Pending", Reason="", readiness=false. Elapsed: 4.137905722s
Jun  8 00:23:20.798: INFO: Pod "pod-subpath-test-dynamicpv-mj5x": Phase="Pending", Reason="", readiness=false. Elapsed: 6.184522828s
Jun  8 00:23:22.844: INFO: Pod "pod-subpath-test-dynamicpv-mj5x": Phase="Pending", Reason="", readiness=false. Elapsed: 8.23005929s
Jun  8 00:23:24.889: INFO: Pod "pod-subpath-test-dynamicpv-mj5x": Phase="Pending", Reason="", readiness=false. Elapsed: 10.275413695s
... skipping 38 lines ...
Jun  8 00:24:44.747: INFO: Pod "pod-subpath-test-dynamicpv-mj5x": Phase="Pending", Reason="", readiness=false. Elapsed: 1m30.133889617s
Jun  8 00:24:46.792: INFO: Pod "pod-subpath-test-dynamicpv-mj5x": Phase="Pending", Reason="", readiness=false. Elapsed: 1m32.178914027s
Jun  8 00:24:48.838: INFO: Pod "pod-subpath-test-dynamicpv-mj5x": Phase="Pending", Reason="", readiness=false. Elapsed: 1m34.224251733s
Jun  8 00:24:50.884: INFO: Pod "pod-subpath-test-dynamicpv-mj5x": Phase="Pending", Reason="", readiness=false. Elapsed: 1m36.271009029s
Jun  8 00:24:52.932: INFO: Pod "pod-subpath-test-dynamicpv-mj5x": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m38.318361702s
STEP: Saw pod success
Jun  8 00:24:52.932: INFO: Pod "pod-subpath-test-dynamicpv-mj5x" satisfied condition "Succeeded or Failed"
Jun  8 00:24:52.977: INFO: Trying to get logs from node ip-172-20-36-176.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-mj5x container test-container-subpath-dynamicpv-mj5x: <nil>
STEP: delete the pod
Jun  8 00:24:53.083: INFO: Waiting for pod pod-subpath-test-dynamicpv-mj5x to disappear
Jun  8 00:24:53.127: INFO: Pod pod-subpath-test-dynamicpv-mj5x no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-mj5x
Jun  8 00:24:53.127: INFO: Deleting pod "pod-subpath-test-dynamicpv-mj5x" in namespace "provisioning-5279"
... skipping 133 lines ...
Jun  8 00:25:35.167: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

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

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

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

    /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 183 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  8 00:24:40.979: 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.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun  8 00:24:41.209: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  8 00:24:41.209: INFO: Creating resource for dynamic PV
Jun  8 00:24:41.209: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7787vw866
STEP: creating a claim
Jun  8 00:24:41.255: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-n98j
STEP: Checking for subpath error in container status
Jun  8 00:25:19.486: INFO: Deleting pod "pod-subpath-test-dynamicpv-n98j" in namespace "provisioning-7787"
Jun  8 00:25:19.534: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-n98j" to be fully deleted
STEP: Deleting pod
Jun  8 00:25:27.633: INFO: Deleting pod "pod-subpath-test-dynamicpv-n98j" in namespace "provisioning-7787"
STEP: Deleting pvc
Jun  8 00:25:27.773: INFO: Deleting PersistentVolumeClaim "awsxnb2t"
... skipping 12 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.yi3ZpreUa/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.yi3ZpreUa/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath file is outside the volume [Slow][LinuxOnly]
      /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] volumes
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  8 00:25:38.114: INFO: Driver ebs.csi.aws.com doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] volumes
... skipping 209 lines ...
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  8 00:25:38.864: 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.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Jun  8 00:25:39.133: INFO: found topology map[topology.kubernetes.io/zone:ca-central-1a]
Jun  8 00:25:39.134: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  8 00:25:39.134: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.yi3ZpreUa/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.yi3ZpreUa/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (immediate binding)] topology
    /tmp/kops.yi3ZpreUa/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.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 163 lines ...
Jun  8 00:24:42.289: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-1465-e2e-sc6brk5
STEP: creating a claim
Jun  8 00:24:42.380: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-plsc
STEP: Creating a pod to test exec-volume-test
Jun  8 00:24:42.568: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-plsc" in namespace "volume-1465" to be "Succeeded or Failed"
Jun  8 00:24:42.865: INFO: Pod "exec-volume-test-dynamicpv-plsc": Phase="Pending", Reason="", readiness=false. Elapsed: 296.928304ms
Jun  8 00:24:44.956: INFO: Pod "exec-volume-test-dynamicpv-plsc": Phase="Pending", Reason="", readiness=false. Elapsed: 2.388241521s
Jun  8 00:24:47.208: INFO: Pod "exec-volume-test-dynamicpv-plsc": Phase="Pending", Reason="", readiness=false. Elapsed: 4.640406583s
Jun  8 00:24:49.457: INFO: Pod "exec-volume-test-dynamicpv-plsc": Phase="Pending", Reason="", readiness=false. Elapsed: 6.889545675s
Jun  8 00:24:51.594: INFO: Pod "exec-volume-test-dynamicpv-plsc": Phase="Pending", Reason="", readiness=false. Elapsed: 9.026426491s
Jun  8 00:24:53.687: INFO: Pod "exec-volume-test-dynamicpv-plsc": Phase="Pending", Reason="", readiness=false. Elapsed: 11.118995268s
Jun  8 00:24:55.738: INFO: Pod "exec-volume-test-dynamicpv-plsc": Phase="Pending", Reason="", readiness=false. Elapsed: 13.170648005s
Jun  8 00:24:57.786: INFO: Pod "exec-volume-test-dynamicpv-plsc": Phase="Pending", Reason="", readiness=false. Elapsed: 15.217759831s
Jun  8 00:24:59.834: INFO: Pod "exec-volume-test-dynamicpv-plsc": Phase="Pending", Reason="", readiness=false. Elapsed: 17.266015465s
Jun  8 00:25:02.324: INFO: Pod "exec-volume-test-dynamicpv-plsc": Phase="Pending", Reason="", readiness=false. Elapsed: 19.756090001s
Jun  8 00:25:04.417: INFO: Pod "exec-volume-test-dynamicpv-plsc": Phase="Pending", Reason="", readiness=false. Elapsed: 21.849088019s
Jun  8 00:25:06.759: INFO: Pod "exec-volume-test-dynamicpv-plsc": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.191040632s
STEP: Saw pod success
Jun  8 00:25:06.759: INFO: Pod "exec-volume-test-dynamicpv-plsc" satisfied condition "Succeeded or Failed"
Jun  8 00:25:06.806: INFO: Trying to get logs from node ip-172-20-35-56.ca-central-1.compute.internal pod exec-volume-test-dynamicpv-plsc container exec-container-dynamicpv-plsc: <nil>
STEP: delete the pod
Jun  8 00:25:06.953: INFO: Waiting for pod exec-volume-test-dynamicpv-plsc to disappear
Jun  8 00:25:07.000: INFO: Pod exec-volume-test-dynamicpv-plsc no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-plsc
Jun  8 00:25:07.000: INFO: Deleting pod "exec-volume-test-dynamicpv-plsc" in namespace "volume-1465"
... skipping 65 lines ...
Jun  8 00:24:32.324: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9970zkb9g
STEP: creating a claim
Jun  8 00:24:32.368: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-86qn
STEP: Creating a pod to test atomic-volume-subpath
Jun  8 00:24:32.505: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-86qn" in namespace "provisioning-9970" to be "Succeeded or Failed"
Jun  8 00:24:32.549: INFO: Pod "pod-subpath-test-dynamicpv-86qn": Phase="Pending", Reason="", readiness=false. Elapsed: 43.586788ms
Jun  8 00:24:34.594: INFO: Pod "pod-subpath-test-dynamicpv-86qn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.088573636s
Jun  8 00:24:36.638: INFO: Pod "pod-subpath-test-dynamicpv-86qn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.132887299s
Jun  8 00:24:38.683: INFO: Pod "pod-subpath-test-dynamicpv-86qn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.177629516s
Jun  8 00:24:40.728: INFO: Pod "pod-subpath-test-dynamicpv-86qn": Phase="Pending", Reason="", readiness=false. Elapsed: 8.222966737s
Jun  8 00:24:42.773: INFO: Pod "pod-subpath-test-dynamicpv-86qn": Phase="Pending", Reason="", readiness=false. Elapsed: 10.267877578s
... skipping 11 lines ...
Jun  8 00:25:07.312: INFO: Pod "pod-subpath-test-dynamicpv-86qn": Phase="Running", Reason="", readiness=true. Elapsed: 34.807316181s
Jun  8 00:25:09.357: INFO: Pod "pod-subpath-test-dynamicpv-86qn": Phase="Running", Reason="", readiness=true. Elapsed: 36.851559897s
Jun  8 00:25:11.402: INFO: Pod "pod-subpath-test-dynamicpv-86qn": Phase="Running", Reason="", readiness=true. Elapsed: 38.896746296s
Jun  8 00:25:13.446: INFO: Pod "pod-subpath-test-dynamicpv-86qn": Phase="Running", Reason="", readiness=true. Elapsed: 40.940968258s
Jun  8 00:25:15.498: INFO: Pod "pod-subpath-test-dynamicpv-86qn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 42.992723458s
STEP: Saw pod success
Jun  8 00:25:15.498: INFO: Pod "pod-subpath-test-dynamicpv-86qn" satisfied condition "Succeeded or Failed"
Jun  8 00:25:15.542: INFO: Trying to get logs from node ip-172-20-35-56.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-86qn container test-container-subpath-dynamicpv-86qn: <nil>
STEP: delete the pod
Jun  8 00:25:15.640: INFO: Waiting for pod pod-subpath-test-dynamicpv-86qn to disappear
Jun  8 00:25:15.684: INFO: Pod pod-subpath-test-dynamicpv-86qn no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-86qn
Jun  8 00:25:15.684: INFO: Deleting pod "pod-subpath-test-dynamicpv-86qn" in namespace "provisioning-9970"
... skipping 102 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.yi3ZpreUa/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.yi3ZpreUa/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.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 292 lines ...
Jun  8 00:24:58.774: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  8 00:24:59.225: INFO: Successfully created a new PD: "aws://ca-central-1a/vol-055884accec83ee3e".
Jun  8 00:24:59.225: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-q7c5
STEP: Creating a pod to test exec-volume-test
Jun  8 00:24:59.271: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-q7c5" in namespace "volume-5102" to be "Succeeded or Failed"
Jun  8 00:24:59.315: INFO: Pod "exec-volume-test-inlinevolume-q7c5": Phase="Pending", Reason="", readiness=false. Elapsed: 43.835401ms
Jun  8 00:25:01.360: INFO: Pod "exec-volume-test-inlinevolume-q7c5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.08818052s
Jun  8 00:25:03.404: INFO: Pod "exec-volume-test-inlinevolume-q7c5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.132955937s
Jun  8 00:25:05.450: INFO: Pod "exec-volume-test-inlinevolume-q7c5": Phase="Pending", Reason="", readiness=false. Elapsed: 6.178284355s
Jun  8 00:25:07.495: INFO: Pod "exec-volume-test-inlinevolume-q7c5": Phase="Pending", Reason="", readiness=false. Elapsed: 8.223503552s
Jun  8 00:25:09.539: INFO: Pod "exec-volume-test-inlinevolume-q7c5": Phase="Pending", Reason="", readiness=false. Elapsed: 10.267733754s
Jun  8 00:25:11.584: INFO: Pod "exec-volume-test-inlinevolume-q7c5": Phase="Pending", Reason="", readiness=false. Elapsed: 12.313025103s
Jun  8 00:25:13.630: INFO: Pod "exec-volume-test-inlinevolume-q7c5": Phase="Pending", Reason="", readiness=false. Elapsed: 14.358789964s
Jun  8 00:25:15.676: INFO: Pod "exec-volume-test-inlinevolume-q7c5": Phase="Pending", Reason="", readiness=false. Elapsed: 16.404701116s
Jun  8 00:25:17.722: INFO: Pod "exec-volume-test-inlinevolume-q7c5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.450198737s
STEP: Saw pod success
Jun  8 00:25:17.722: INFO: Pod "exec-volume-test-inlinevolume-q7c5" satisfied condition "Succeeded or Failed"
Jun  8 00:25:17.766: INFO: Trying to get logs from node ip-172-20-35-56.ca-central-1.compute.internal pod exec-volume-test-inlinevolume-q7c5 container exec-container-inlinevolume-q7c5: <nil>
STEP: delete the pod
Jun  8 00:25:17.860: INFO: Waiting for pod exec-volume-test-inlinevolume-q7c5 to disappear
Jun  8 00:25:17.904: INFO: Pod exec-volume-test-inlinevolume-q7c5 no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-q7c5
Jun  8 00:25:17.904: INFO: Deleting pod "exec-volume-test-inlinevolume-q7c5" in namespace "volume-5102"
Jun  8 00:25:18.100: INFO: Couldn't delete PD "aws://ca-central-1a/vol-055884accec83ee3e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-055884accec83ee3e is currently attached to i-0216cc8a3d86cc491
	status code: 400, request id: edb429f1-4e21-4eed-8571-2345bdf01190
Jun  8 00:25:23.444: INFO: Couldn't delete PD "aws://ca-central-1a/vol-055884accec83ee3e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-055884accec83ee3e is currently attached to i-0216cc8a3d86cc491
	status code: 400, request id: 90375856-4b40-4960-8a84-a89ff3a1784b
Jun  8 00:25:28.756: INFO: Couldn't delete PD "aws://ca-central-1a/vol-055884accec83ee3e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-055884accec83ee3e is currently attached to i-0216cc8a3d86cc491
	status code: 400, request id: 0835dfdc-9c34-4b5d-b47c-0992749b5043
Jun  8 00:25:34.141: INFO: Couldn't delete PD "aws://ca-central-1a/vol-055884accec83ee3e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-055884accec83ee3e is currently attached to i-0216cc8a3d86cc491
	status code: 400, request id: 53cdf622-32e1-4332-b614-a7ad76597027
Jun  8 00:25:39.434: INFO: Couldn't delete PD "aws://ca-central-1a/vol-055884accec83ee3e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-055884accec83ee3e is currently attached to i-0216cc8a3d86cc491
	status code: 400, request id: b4980f58-1097-4d19-bbce-1fe51490e06a
Jun  8 00:25:44.774: INFO: Couldn't delete PD "aws://ca-central-1a/vol-055884accec83ee3e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-055884accec83ee3e is currently attached to i-0216cc8a3d86cc491
	status code: 400, request id: c17d2ca1-dc44-4776-ad94-e50c889bae7e
Jun  8 00:25:50.137: INFO: Successfully deleted PD "aws://ca-central-1a/vol-055884accec83ee3e".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  8 00:25:50.137: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-5102" for this suite.
... skipping 143 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.yi3ZpreUa/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.yi3ZpreUa/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.yi3ZpreUa/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.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 71 lines ...
Jun  8 00:24:01.561: INFO: Creating resource for dynamic PV
Jun  8 00:24:01.562: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6361-e2e-scfftcp
STEP: creating a claim
Jun  8 00:24:01.607: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-6361
Jun  8 00:24:01.744: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-6361" in namespace "provisioning-6361" to be "Succeeded or Failed"
Jun  8 00:24:01.788: INFO: Pod "volume-prep-provisioning-6361": Phase="Pending", Reason="", readiness=false. Elapsed: 44.011462ms
Jun  8 00:24:03.833: INFO: Pod "volume-prep-provisioning-6361": Phase="Pending", Reason="", readiness=false. Elapsed: 2.088927451s
Jun  8 00:24:05.878: INFO: Pod "volume-prep-provisioning-6361": Phase="Pending", Reason="", readiness=false. Elapsed: 4.134566082s
Jun  8 00:24:07.924: INFO: Pod "volume-prep-provisioning-6361": Phase="Pending", Reason="", readiness=false. Elapsed: 6.180048296s
Jun  8 00:24:09.969: INFO: Pod "volume-prep-provisioning-6361": Phase="Pending", Reason="", readiness=false. Elapsed: 8.225288006s
Jun  8 00:24:12.014: INFO: Pod "volume-prep-provisioning-6361": Phase="Pending", Reason="", readiness=false. Elapsed: 10.270174609s
... skipping 26 lines ...
Jun  8 00:25:07.244: INFO: Pod "volume-prep-provisioning-6361": Phase="Pending", Reason="", readiness=false. Elapsed: 1m5.500211712s
Jun  8 00:25:09.289: INFO: Pod "volume-prep-provisioning-6361": Phase="Pending", Reason="", readiness=false. Elapsed: 1m7.545592655s
Jun  8 00:25:11.333: INFO: Pod "volume-prep-provisioning-6361": Phase="Pending", Reason="", readiness=false. Elapsed: 1m9.589638749s
Jun  8 00:25:13.379: INFO: Pod "volume-prep-provisioning-6361": Phase="Pending", Reason="", readiness=false. Elapsed: 1m11.635257644s
Jun  8 00:25:15.424: INFO: Pod "volume-prep-provisioning-6361": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m13.680318253s
STEP: Saw pod success
Jun  8 00:25:15.424: INFO: Pod "volume-prep-provisioning-6361" satisfied condition "Succeeded or Failed"
Jun  8 00:25:15.424: INFO: Deleting pod "volume-prep-provisioning-6361" in namespace "provisioning-6361"
Jun  8 00:25:15.474: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-6361" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-zq7q
STEP: Checking for subpath error in container status
Jun  8 00:25:19.655: INFO: Deleting pod "pod-subpath-test-dynamicpv-zq7q" in namespace "provisioning-6361"
Jun  8 00:25:19.705: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-zq7q" to be fully deleted
STEP: Deleting pod
Jun  8 00:25:19.749: INFO: Deleting pod "pod-subpath-test-dynamicpv-zq7q" in namespace "provisioning-6361"
STEP: Deleting pvc
Jun  8 00:25:19.881: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comg49b9"
... skipping 185 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.yi3ZpreUa/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.yi3ZpreUa/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.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 452 lines ...
Jun  8 00:24:53.406: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8975-e2e-sc87mkl
STEP: creating a claim
Jun  8 00:24:53.451: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-vk5p
STEP: Creating a pod to test atomic-volume-subpath
Jun  8 00:24:53.595: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-vk5p" in namespace "provisioning-8975" to be "Succeeded or Failed"
Jun  8 00:24:53.639: INFO: Pod "pod-subpath-test-dynamicpv-vk5p": Phase="Pending", Reason="", readiness=false. Elapsed: 44.538503ms
Jun  8 00:24:55.684: INFO: Pod "pod-subpath-test-dynamicpv-vk5p": Phase="Pending", Reason="", readiness=false. Elapsed: 2.088793278s
Jun  8 00:24:57.728: INFO: Pod "pod-subpath-test-dynamicpv-vk5p": Phase="Pending", Reason="", readiness=false. Elapsed: 4.133268114s
Jun  8 00:24:59.773: INFO: Pod "pod-subpath-test-dynamicpv-vk5p": Phase="Pending", Reason="", readiness=false. Elapsed: 6.178527774s
Jun  8 00:25:01.818: INFO: Pod "pod-subpath-test-dynamicpv-vk5p": Phase="Pending", Reason="", readiness=false. Elapsed: 8.223523845s
Jun  8 00:25:03.863: INFO: Pod "pod-subpath-test-dynamicpv-vk5p": Phase="Pending", Reason="", readiness=false. Elapsed: 10.268235763s
... skipping 11 lines ...
Jun  8 00:25:28.417: INFO: Pod "pod-subpath-test-dynamicpv-vk5p": Phase="Running", Reason="", readiness=true. Elapsed: 34.822147954s
Jun  8 00:25:30.462: INFO: Pod "pod-subpath-test-dynamicpv-vk5p": Phase="Running", Reason="", readiness=true. Elapsed: 36.867616127s
Jun  8 00:25:32.509: INFO: Pod "pod-subpath-test-dynamicpv-vk5p": Phase="Running", Reason="", readiness=true. Elapsed: 38.914535294s
Jun  8 00:25:34.554: INFO: Pod "pod-subpath-test-dynamicpv-vk5p": Phase="Running", Reason="", readiness=true. Elapsed: 40.959069637s
Jun  8 00:25:36.598: INFO: Pod "pod-subpath-test-dynamicpv-vk5p": Phase="Succeeded", Reason="", readiness=false. Elapsed: 43.003560782s
STEP: Saw pod success
Jun  8 00:25:36.599: INFO: Pod "pod-subpath-test-dynamicpv-vk5p" satisfied condition "Succeeded or Failed"
Jun  8 00:25:36.643: INFO: Trying to get logs from node ip-172-20-36-176.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-vk5p container test-container-subpath-dynamicpv-vk5p: <nil>
STEP: delete the pod
Jun  8 00:25:36.739: INFO: Waiting for pod pod-subpath-test-dynamicpv-vk5p to disappear
Jun  8 00:25:36.782: INFO: Pod pod-subpath-test-dynamicpv-vk5p no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-vk5p
Jun  8 00:25:36.782: INFO: Deleting pod "pod-subpath-test-dynamicpv-vk5p" in namespace "provisioning-8975"
... skipping 40 lines ...
Jun  8 00:25:23.543: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-1341qtvhh
STEP: creating a claim
Jun  8 00:25:23.589: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-fzxw
STEP: Creating a pod to test exec-volume-test
Jun  8 00:25:23.728: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-fzxw" in namespace "volume-1341" to be "Succeeded or Failed"
Jun  8 00:25:23.773: INFO: Pod "exec-volume-test-dynamicpv-fzxw": Phase="Pending", Reason="", readiness=false. Elapsed: 44.864173ms
Jun  8 00:25:25.820: INFO: Pod "exec-volume-test-dynamicpv-fzxw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.091984054s
Jun  8 00:25:27.867: INFO: Pod "exec-volume-test-dynamicpv-fzxw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.138487406s
Jun  8 00:25:29.912: INFO: Pod "exec-volume-test-dynamicpv-fzxw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.183931611s
Jun  8 00:25:31.959: INFO: Pod "exec-volume-test-dynamicpv-fzxw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.230379731s
Jun  8 00:25:34.005: INFO: Pod "exec-volume-test-dynamicpv-fzxw": Phase="Pending", Reason="", readiness=false. Elapsed: 10.27698538s
... skipping 10 lines ...
Jun  8 00:25:56.517: INFO: Pod "exec-volume-test-dynamicpv-fzxw": Phase="Pending", Reason="", readiness=false. Elapsed: 32.788126299s
Jun  8 00:25:58.596: INFO: Pod "exec-volume-test-dynamicpv-fzxw": Phase="Pending", Reason="", readiness=false. Elapsed: 34.867635576s
Jun  8 00:26:00.643: INFO: Pod "exec-volume-test-dynamicpv-fzxw": Phase="Pending", Reason="", readiness=false. Elapsed: 36.914772079s
Jun  8 00:26:02.688: INFO: Pod "exec-volume-test-dynamicpv-fzxw": Phase="Pending", Reason="", readiness=false. Elapsed: 38.959921176s
Jun  8 00:26:04.734: INFO: Pod "exec-volume-test-dynamicpv-fzxw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 41.005423393s
STEP: Saw pod success
Jun  8 00:26:04.734: INFO: Pod "exec-volume-test-dynamicpv-fzxw" satisfied condition "Succeeded or Failed"
Jun  8 00:26:04.779: INFO: Trying to get logs from node ip-172-20-35-56.ca-central-1.compute.internal pod exec-volume-test-dynamicpv-fzxw container exec-container-dynamicpv-fzxw: <nil>
STEP: delete the pod
Jun  8 00:26:04.883: INFO: Waiting for pod exec-volume-test-dynamicpv-fzxw to disappear
Jun  8 00:26:04.928: INFO: Pod exec-volume-test-dynamicpv-fzxw no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-fzxw
Jun  8 00:26:04.928: INFO: Deleting pod "exec-volume-test-dynamicpv-fzxw" in namespace "volume-1341"
... skipping 84 lines ...
Jun  8 00:25:59.208: INFO: PersistentVolumeClaim pvc-pnbnk found but phase is Pending instead of Bound.
Jun  8 00:26:01.253: INFO: PersistentVolumeClaim pvc-pnbnk found and phase=Bound (10.26926919s)
Jun  8 00:26:01.253: INFO: Waiting up to 3m0s for PersistentVolume aws-htl6n to have phase Bound
Jun  8 00:26:01.309: INFO: PersistentVolume aws-htl6n found and phase=Bound (55.979885ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-kzw9
STEP: Creating a pod to test exec-volume-test
Jun  8 00:26:01.448: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-kzw9" in namespace "volume-583" to be "Succeeded or Failed"
Jun  8 00:26:01.492: INFO: Pod "exec-volume-test-preprovisionedpv-kzw9": Phase="Pending", Reason="", readiness=false. Elapsed: 44.647265ms
Jun  8 00:26:03.537: INFO: Pod "exec-volume-test-preprovisionedpv-kzw9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.08957073s
Jun  8 00:26:05.582: INFO: Pod "exec-volume-test-preprovisionedpv-kzw9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.134006899s
Jun  8 00:26:07.627: INFO: Pod "exec-volume-test-preprovisionedpv-kzw9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.17921365s
Jun  8 00:26:09.673: INFO: Pod "exec-volume-test-preprovisionedpv-kzw9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.22526104s
STEP: Saw pod success
Jun  8 00:26:09.673: INFO: Pod "exec-volume-test-preprovisionedpv-kzw9" satisfied condition "Succeeded or Failed"
Jun  8 00:26:09.718: INFO: Trying to get logs from node ip-172-20-41-166.ca-central-1.compute.internal pod exec-volume-test-preprovisionedpv-kzw9 container exec-container-preprovisionedpv-kzw9: <nil>
STEP: delete the pod
Jun  8 00:26:09.815: INFO: Waiting for pod exec-volume-test-preprovisionedpv-kzw9 to disappear
Jun  8 00:26:09.860: INFO: Pod exec-volume-test-preprovisionedpv-kzw9 no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-kzw9
Jun  8 00:26:09.860: INFO: Deleting pod "exec-volume-test-preprovisionedpv-kzw9" in namespace "volume-583"
STEP: Deleting pv and pvc
Jun  8 00:26:09.905: INFO: Deleting PersistentVolumeClaim "pvc-pnbnk"
Jun  8 00:26:09.951: INFO: Deleting PersistentVolume "aws-htl6n"
Jun  8 00:26:10.162: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0cf89aa3d563ff0ee", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0cf89aa3d563ff0ee is currently attached to i-0f1ca4a47ab66c5f4
	status code: 400, request id: 34150254-9600-41f0-bc01-e4ab89678c13
Jun  8 00:26:15.512: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0cf89aa3d563ff0ee", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0cf89aa3d563ff0ee is currently attached to i-0f1ca4a47ab66c5f4
	status code: 400, request id: 6cd4ac6e-0eb5-4108-b03e-67d9584d5e81
Jun  8 00:26:20.850: INFO: Successfully deleted PD "aws://ca-central-1a/vol-0cf89aa3d563ff0ee".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  8 00:26:20.850: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-583" for this suite.
... skipping 68 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.yi3ZpreUa/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.yi3ZpreUa/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.yi3ZpreUa/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.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 19 lines ...
Jun  8 00:25:58.767: INFO: PersistentVolumeClaim pvc-n22h9 found but phase is Pending instead of Bound.
Jun  8 00:26:00.812: INFO: PersistentVolumeClaim pvc-n22h9 found and phase=Bound (4.146259829s)
Jun  8 00:26:00.812: INFO: Waiting up to 3m0s for PersistentVolume aws-fd4mc to have phase Bound
Jun  8 00:26:00.857: INFO: PersistentVolume aws-fd4mc found and phase=Bound (44.590709ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-c82j
STEP: Creating a pod to test exec-volume-test
Jun  8 00:26:01.018: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-c82j" in namespace "volume-5578" to be "Succeeded or Failed"
Jun  8 00:26:01.064: INFO: Pod "exec-volume-test-preprovisionedpv-c82j": Phase="Pending", Reason="", readiness=false. Elapsed: 45.688425ms
Jun  8 00:26:03.109: INFO: Pod "exec-volume-test-preprovisionedpv-c82j": Phase="Pending", Reason="", readiness=false. Elapsed: 2.091038035s
Jun  8 00:26:05.155: INFO: Pod "exec-volume-test-preprovisionedpv-c82j": Phase="Pending", Reason="", readiness=false. Elapsed: 4.137220969s
Jun  8 00:26:07.200: INFO: Pod "exec-volume-test-preprovisionedpv-c82j": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.181980311s
STEP: Saw pod success
Jun  8 00:26:07.200: INFO: Pod "exec-volume-test-preprovisionedpv-c82j" satisfied condition "Succeeded or Failed"
Jun  8 00:26:07.245: INFO: Trying to get logs from node ip-172-20-35-56.ca-central-1.compute.internal pod exec-volume-test-preprovisionedpv-c82j container exec-container-preprovisionedpv-c82j: <nil>
STEP: delete the pod
Jun  8 00:26:07.350: INFO: Waiting for pod exec-volume-test-preprovisionedpv-c82j to disappear
Jun  8 00:26:07.394: INFO: Pod exec-volume-test-preprovisionedpv-c82j no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-c82j
Jun  8 00:26:07.394: INFO: Deleting pod "exec-volume-test-preprovisionedpv-c82j" in namespace "volume-5578"
STEP: Deleting pv and pvc
Jun  8 00:26:07.440: INFO: Deleting PersistentVolumeClaim "pvc-n22h9"
Jun  8 00:26:07.485: INFO: Deleting PersistentVolume "aws-fd4mc"
Jun  8 00:26:07.687: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0c5bf3f6611d27e02", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c5bf3f6611d27e02 is currently attached to i-0216cc8a3d86cc491
	status code: 400, request id: c26b4eaf-5c70-4407-acee-5094649a7532
Jun  8 00:26:13.010: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0c5bf3f6611d27e02", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c5bf3f6611d27e02 is currently attached to i-0216cc8a3d86cc491
	status code: 400, request id: d326c965-9a10-489b-b748-813776c4a444
Jun  8 00:26:18.342: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0c5bf3f6611d27e02", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c5bf3f6611d27e02 is currently attached to i-0216cc8a3d86cc491
	status code: 400, request id: 864771b5-4a29-4f88-8eb9-f9a8fd13e700
Jun  8 00:26:23.643: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0c5bf3f6611d27e02", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c5bf3f6611d27e02 is currently attached to i-0216cc8a3d86cc491
	status code: 400, request id: 922f36f9-1d08-4737-ade4-95522b4feac6
Jun  8 00:26:28.932: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0c5bf3f6611d27e02", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c5bf3f6611d27e02 is currently attached to i-0216cc8a3d86cc491
	status code: 400, request id: e5ca5744-a5eb-4cf2-9795-25d4c9930262
Jun  8 00:26:34.222: INFO: Successfully deleted PD "aws://ca-central-1a/vol-0c5bf3f6611d27e02".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  8 00:26:34.222: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-5578" for this suite.
... skipping 14 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  8 00:25:28.859: 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.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun  8 00:25:29.086: INFO: Creating resource for dynamic PV
Jun  8 00:25:29.086: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6451-e2e-sc8nt92
STEP: creating a claim
Jun  8 00:25:29.132: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-9z5z
STEP: Checking for subpath error in container status
Jun  8 00:25:47.364: INFO: Deleting pod "pod-subpath-test-dynamicpv-9z5z" in namespace "provisioning-6451"
Jun  8 00:25:47.424: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-9z5z" to be fully deleted
STEP: Deleting pod
Jun  8 00:25:59.514: INFO: Deleting pod "pod-subpath-test-dynamicpv-9z5z" in namespace "provisioning-6451"
STEP: Deleting pvc
Jun  8 00:25:59.650: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comgkws4"
... skipping 15 lines ...

• [SLOW TEST:66.411 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.yi3ZpreUa/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.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  8 00:26:35.272: INFO: Driver "ebs.csi.aws.com" does not support volume type "InlineVolume" - skipping
[AfterEach] [Testpattern: Inline-volume (default fs)] subPath
... skipping 71 lines ...
Jun  8 00:25:51.004: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2830phnnr
STEP: creating a claim
Jun  8 00:25:51.049: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-qrgp
STEP: Creating a pod to test multi_subpath
Jun  8 00:25:51.185: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-qrgp" in namespace "provisioning-2830" to be "Succeeded or Failed"
Jun  8 00:25:51.230: INFO: Pod "pod-subpath-test-dynamicpv-qrgp": Phase="Pending", Reason="", readiness=false. Elapsed: 44.08435ms
Jun  8 00:25:53.274: INFO: Pod "pod-subpath-test-dynamicpv-qrgp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.088933572s
Jun  8 00:25:55.320: INFO: Pod "pod-subpath-test-dynamicpv-qrgp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.134806166s
Jun  8 00:25:57.365: INFO: Pod "pod-subpath-test-dynamicpv-qrgp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.179707596s
Jun  8 00:25:59.410: INFO: Pod "pod-subpath-test-dynamicpv-qrgp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.224356011s
Jun  8 00:26:01.456: INFO: Pod "pod-subpath-test-dynamicpv-qrgp": Phase="Pending", Reason="", readiness=false. Elapsed: 10.270475168s
... skipping 2 lines ...
Jun  8 00:26:07.592: INFO: Pod "pod-subpath-test-dynamicpv-qrgp": Phase="Pending", Reason="", readiness=false. Elapsed: 16.406690544s
Jun  8 00:26:09.638: INFO: Pod "pod-subpath-test-dynamicpv-qrgp": Phase="Pending", Reason="", readiness=false. Elapsed: 18.452684757s
Jun  8 00:26:11.685: INFO: Pod "pod-subpath-test-dynamicpv-qrgp": Phase="Pending", Reason="", readiness=false. Elapsed: 20.499341136s
Jun  8 00:26:13.730: INFO: Pod "pod-subpath-test-dynamicpv-qrgp": Phase="Pending", Reason="", readiness=false. Elapsed: 22.544040644s
Jun  8 00:26:15.777: INFO: Pod "pod-subpath-test-dynamicpv-qrgp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.591562731s
STEP: Saw pod success
Jun  8 00:26:15.777: INFO: Pod "pod-subpath-test-dynamicpv-qrgp" satisfied condition "Succeeded or Failed"
Jun  8 00:26:15.826: INFO: Trying to get logs from node ip-172-20-41-166.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-qrgp container test-container-subpath-dynamicpv-qrgp: <nil>
STEP: delete the pod
Jun  8 00:26:15.935: INFO: Waiting for pod pod-subpath-test-dynamicpv-qrgp to disappear
Jun  8 00:26:15.980: INFO: Pod pod-subpath-test-dynamicpv-qrgp no longer exists
STEP: Deleting pod
Jun  8 00:26:15.980: INFO: Deleting pod "pod-subpath-test-dynamicpv-qrgp" in namespace "provisioning-2830"
... skipping 202 lines ...
Jun  8 00:26:14.900: INFO: Pod aws-client still exists
Jun  8 00:26:16.854: INFO: Waiting for pod aws-client to disappear
Jun  8 00:26:16.898: INFO: Pod aws-client still exists
Jun  8 00:26:18.854: INFO: Waiting for pod aws-client to disappear
Jun  8 00:26:18.898: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun  8 00:26:19.235: INFO: Couldn't delete PD "aws://ca-central-1a/vol-01383a30380663c57", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01383a30380663c57 is currently attached to i-05ae10a17dc5bb2c8
	status code: 400, request id: 1ff5bdcc-93d8-43c0-8f8e-b6fc402dfd6a
Jun  8 00:26:24.535: INFO: Couldn't delete PD "aws://ca-central-1a/vol-01383a30380663c57", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01383a30380663c57 is currently attached to i-05ae10a17dc5bb2c8
	status code: 400, request id: dc642be2-6180-4c26-b7de-03ccea8a1777
Jun  8 00:26:29.873: INFO: Couldn't delete PD "aws://ca-central-1a/vol-01383a30380663c57", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01383a30380663c57 is currently attached to i-05ae10a17dc5bb2c8
	status code: 400, request id: b072ad7c-ecc3-4f52-9ee5-0c3788dcf453
Jun  8 00:26:35.184: INFO: Couldn't delete PD "aws://ca-central-1a/vol-01383a30380663c57", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01383a30380663c57 is currently attached to i-05ae10a17dc5bb2c8
	status code: 400, request id: 8b4f158b-7f7a-4f99-8169-1c4b91df69df
Jun  8 00:26:40.483: INFO: Couldn't delete PD "aws://ca-central-1a/vol-01383a30380663c57", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01383a30380663c57 is currently attached to i-05ae10a17dc5bb2c8
	status code: 400, request id: a6b3aeef-0ae6-4c2b-929d-049eb8240e07
Jun  8 00:26:45.823: INFO: Successfully deleted PD "aws://ca-central-1a/vol-01383a30380663c57".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  8 00:26:45.823: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-2433" for this suite.
... skipping 168 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  8 00:26:35.600: 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.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  8 00:26:35.844: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  8 00:26:35.844: INFO: Creating resource for dynamic PV
Jun  8 00:26:35.844: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-4591b497t
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  8 00:26:42.165: INFO: Deleting pod "pod-92e2469c-6d7b-4bfe-b5bb-6c73dee0f595" in namespace "volumemode-4591"
Jun  8 00:26:42.214: INFO: Wait up to 5m0s for pod "pod-92e2469c-6d7b-4bfe-b5bb-6c73dee0f595" to be fully deleted
STEP: Deleting pvc
Jun  8 00:26:46.397: INFO: Deleting PersistentVolumeClaim "awsj7rwm"
Jun  8 00:26:46.443: INFO: Waiting up to 5m0s for PersistentVolume pvc-73d7fd44-dbb8-4113-89b5-13746b3ac24e to get deleted
Jun  8 00:26:46.488: INFO: PersistentVolume pvc-73d7fd44-dbb8-4113-89b5-13746b3ac24e found and phase=Released (44.835625ms)
... skipping 9 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.yi3ZpreUa/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.yi3ZpreUa/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (block volmode)] volumeMode
    /tmp/kops.yi3ZpreUa/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.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned Snapshot (delete policy)] snapshottable[Feature:VolumeSnapshotDataSource]
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Pre-provisioned Snapshot (delete policy)] snapshottable[Feature:VolumeSnapshotDataSource]
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 6 lines ...
Jun  8 00:24:41.482: INFO: Creating resource for dynamic PV
Jun  8 00:24:41.482: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-973-e2e-sc7xzv4
STEP: creating a claim
Jun  8 00:24:41.532: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun  8 00:24:41.676: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-8x5sv" in namespace "snapshotting-973" to be "Succeeded or Failed"
Jun  8 00:24:41.721: INFO: Pod "pvc-snapshottable-tester-8x5sv": Phase="Pending", Reason="", readiness=false. Elapsed: 45.148869ms
Jun  8 00:24:43.768: INFO: Pod "pvc-snapshottable-tester-8x5sv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.091899243s
Jun  8 00:24:45.818: INFO: Pod "pvc-snapshottable-tester-8x5sv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.14121738s
Jun  8 00:24:47.863: INFO: Pod "pvc-snapshottable-tester-8x5sv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.186660011s
Jun  8 00:24:49.912: INFO: Pod "pvc-snapshottable-tester-8x5sv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.235257754s
Jun  8 00:24:51.957: INFO: Pod "pvc-snapshottable-tester-8x5sv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.281007713s
... skipping 2 lines ...
Jun  8 00:24:58.095: INFO: Pod "pvc-snapshottable-tester-8x5sv": Phase="Pending", Reason="", readiness=false. Elapsed: 16.418974335s
Jun  8 00:25:00.142: INFO: Pod "pvc-snapshottable-tester-8x5sv": Phase="Pending", Reason="", readiness=false. Elapsed: 18.465698621s
Jun  8 00:25:02.188: INFO: Pod "pvc-snapshottable-tester-8x5sv": Phase="Pending", Reason="", readiness=false. Elapsed: 20.511315771s
Jun  8 00:25:04.236: INFO: Pod "pvc-snapshottable-tester-8x5sv": Phase="Pending", Reason="", readiness=false. Elapsed: 22.559284813s
Jun  8 00:25:06.283: INFO: Pod "pvc-snapshottable-tester-8x5sv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.60648807s
STEP: Saw pod success
Jun  8 00:25:06.283: INFO: Pod "pvc-snapshottable-tester-8x5sv" satisfied condition "Succeeded or Failed"
Jun  8 00:25:06.375: INFO: Pod pvc-snapshottable-tester-8x5sv has the following logs: 
Jun  8 00:25:06.375: INFO: Deleting pod "pvc-snapshottable-tester-8x5sv" in namespace "snapshotting-973"
Jun  8 00:25:06.429: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-8x5sv" to be fully deleted
Jun  8 00:25:06.475: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comhv4c5] to have phase Bound
Jun  8 00:25:06.520: INFO: PersistentVolumeClaim ebs.csi.aws.comhv4c5 found and phase=Bound (45.237829ms)
STEP: [init] checking the claim
... skipping 43 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:243
STEP: checking the snapshot
STEP: checking the SnapshotContent
STEP: Modifying source data test
STEP: modifying the data in the source PVC
Jun  8 00:25:38.200: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-bjp4n" in namespace "snapshotting-973" to be "Succeeded or Failed"
Jun  8 00:25:38.246: INFO: Pod "pvc-snapshottable-data-tester-bjp4n": Phase="Pending", Reason="", readiness=false. Elapsed: 45.224685ms
Jun  8 00:25:40.293: INFO: Pod "pvc-snapshottable-data-tester-bjp4n": Phase="Pending", Reason="", readiness=false. Elapsed: 2.092748563s
Jun  8 00:25:42.339: INFO: Pod "pvc-snapshottable-data-tester-bjp4n": Phase="Pending", Reason="", readiness=false. Elapsed: 4.138275383s
Jun  8 00:25:44.384: INFO: Pod "pvc-snapshottable-data-tester-bjp4n": Phase="Pending", Reason="", readiness=false. Elapsed: 6.183740728s
Jun  8 00:25:46.430: INFO: Pod "pvc-snapshottable-data-tester-bjp4n": Phase="Pending", Reason="", readiness=false. Elapsed: 8.229133021s
Jun  8 00:25:48.476: INFO: Pod "pvc-snapshottable-data-tester-bjp4n": Phase="Pending", Reason="", readiness=false. Elapsed: 10.27574684s
Jun  8 00:25:50.522: INFO: Pod "pvc-snapshottable-data-tester-bjp4n": Phase="Pending", Reason="", readiness=false. Elapsed: 12.321783917s
Jun  8 00:25:52.569: INFO: Pod "pvc-snapshottable-data-tester-bjp4n": Phase="Pending", Reason="", readiness=false. Elapsed: 14.368781299s
Jun  8 00:25:54.616: INFO: Pod "pvc-snapshottable-data-tester-bjp4n": Phase="Pending", Reason="", readiness=false. Elapsed: 16.41580823s
Jun  8 00:25:56.663: INFO: Pod "pvc-snapshottable-data-tester-bjp4n": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.462543316s
STEP: Saw pod success
Jun  8 00:25:56.663: INFO: Pod "pvc-snapshottable-data-tester-bjp4n" satisfied condition "Succeeded or Failed"
Jun  8 00:25:56.777: INFO: Pod pvc-snapshottable-data-tester-bjp4n has the following logs: 
Jun  8 00:25:56.777: INFO: Deleting pod "pvc-snapshottable-data-tester-bjp4n" in namespace "snapshotting-973"
Jun  8 00:25:56.830: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-bjp4n" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun  8 00:26:07.096: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-973 exec restored-pvc-tester-vhwzh --namespace=snapshotting-973 -- cat /mnt/test/data'
... skipping 69 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  8 00:26:20.440: 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.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  8 00:26:20.668: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  8 00:26:21.117: INFO: Successfully created a new PD: "aws://ca-central-1a/vol-0faf9e3d4bd264cfd".
Jun  8 00:26:21.117: INFO: Creating resource for pre-provisioned PV
Jun  8 00:26:21.117: INFO: Creating PVC and PV
... skipping 6 lines ...
Jun  8 00:26:27.466: INFO: PersistentVolumeClaim pvc-fxgxm found but phase is Pending instead of Bound.
Jun  8 00:26:29.513: INFO: PersistentVolumeClaim pvc-fxgxm found but phase is Pending instead of Bound.
Jun  8 00:26:31.560: INFO: PersistentVolumeClaim pvc-fxgxm found and phase=Bound (10.282805058s)
Jun  8 00:26:31.560: INFO: Waiting up to 3m0s for PersistentVolume aws-lqzzj to have phase Bound
Jun  8 00:26:31.605: INFO: PersistentVolume aws-lqzzj found and phase=Bound (44.988131ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  8 00:26:31.832: INFO: Deleting pod "pod-94bce6ba-0560-458f-8e76-7dae9f4e96d4" in namespace "volumemode-2647"
Jun  8 00:26:31.878: INFO: Wait up to 5m0s for pod "pod-94bce6ba-0560-458f-8e76-7dae9f4e96d4" to be fully deleted
STEP: Deleting pv and pvc
Jun  8 00:26:37.969: INFO: Deleting PersistentVolumeClaim "pvc-fxgxm"
Jun  8 00:26:38.015: INFO: Deleting PersistentVolume "aws-lqzzj"
Jun  8 00:26:38.218: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0faf9e3d4bd264cfd", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0faf9e3d4bd264cfd is currently attached to i-05ae10a17dc5bb2c8
	status code: 400, request id: 7f72b42e-6b39-4676-8588-8a8113ce83ed
Jun  8 00:26:43.568: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0faf9e3d4bd264cfd", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0faf9e3d4bd264cfd is currently attached to i-05ae10a17dc5bb2c8
	status code: 400, request id: 8ddc69d0-fd98-400a-9c2a-fa485a01f7fb
Jun  8 00:26:48.881: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0faf9e3d4bd264cfd", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0faf9e3d4bd264cfd is currently attached to i-05ae10a17dc5bb2c8
	status code: 400, request id: 02a7eafd-cd7f-4d33-bfc9-65e486782470
Jun  8 00:26:54.179: INFO: Successfully deleted PD "aws://ca-central-1a/vol-0faf9e3d4bd264cfd".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  8 00:26:54.179: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-2647" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.yi3ZpreUa/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.yi3ZpreUa/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
    /tmp/kops.yi3ZpreUa/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.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 163 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  8 00:26:12.507: 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.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun  8 00:26:12.729: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  8 00:26:12.729: INFO: Creating resource for dynamic PV
Jun  8 00:26:12.729: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-32365h8c2
STEP: creating a claim
Jun  8 00:26:12.773: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-5nbg
STEP: Checking for subpath error in container status
Jun  8 00:26:37.005: INFO: Deleting pod "pod-subpath-test-dynamicpv-5nbg" in namespace "provisioning-3236"
Jun  8 00:26:37.054: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-5nbg" to be fully deleted
STEP: Deleting pod
Jun  8 00:26:47.143: INFO: Deleting pod "pod-subpath-test-dynamicpv-5nbg" in namespace "provisioning-3236"
STEP: Deleting pvc
Jun  8 00:26:47.275: INFO: Deleting PersistentVolumeClaim "aws2zqt4"
... skipping 12 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.yi3ZpreUa/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.yi3ZpreUa/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.yi3ZpreUa/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.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  8 00:26:10.704: 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.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun  8 00:26:10.941: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  8 00:26:10.941: INFO: Creating resource for dynamic PV
Jun  8 00:26:10.941: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-769464bmq
STEP: creating a claim
Jun  8 00:26:10.987: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-jwwm
STEP: Checking for subpath error in container status
Jun  8 00:26:35.222: INFO: Deleting pod "pod-subpath-test-dynamicpv-jwwm" in namespace "provisioning-7694"
Jun  8 00:26:35.280: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-jwwm" to be fully deleted
STEP: Deleting pod
Jun  8 00:26:47.388: INFO: Deleting pod "pod-subpath-test-dynamicpv-jwwm" in namespace "provisioning-7694"
STEP: Deleting pvc
Jun  8 00:26:47.529: INFO: Deleting PersistentVolumeClaim "awswqgnx"
... skipping 13 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.yi3ZpreUa/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.yi3ZpreUa/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.yi3ZpreUa/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.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned Snapshot (retain policy)] snapshottable[Feature:VolumeSnapshotDataSource]
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Pre-provisioned Snapshot (retain policy)] snapshottable[Feature:VolumeSnapshotDataSource]
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 6 lines ...
Jun  8 00:23:53.665: INFO: Creating resource for dynamic PV
Jun  8 00:23:53.665: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-531-e2e-scrtrjr
STEP: creating a claim
Jun  8 00:23:53.712: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun  8 00:23:53.851: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-9fl97" in namespace "snapshotting-531" to be "Succeeded or Failed"
Jun  8 00:23:53.895: INFO: Pod "pvc-snapshottable-tester-9fl97": Phase="Pending", Reason="", readiness=false. Elapsed: 44.58914ms
Jun  8 00:23:55.940: INFO: Pod "pvc-snapshottable-tester-9fl97": Phase="Pending", Reason="", readiness=false. Elapsed: 2.089486659s
Jun  8 00:23:57.994: INFO: Pod "pvc-snapshottable-tester-9fl97": Phase="Pending", Reason="", readiness=false. Elapsed: 4.142917956s
Jun  8 00:24:00.039: INFO: Pod "pvc-snapshottable-tester-9fl97": Phase="Pending", Reason="", readiness=false. Elapsed: 6.188041549s
Jun  8 00:24:02.084: INFO: Pod "pvc-snapshottable-tester-9fl97": Phase="Pending", Reason="", readiness=false. Elapsed: 8.233443249s
Jun  8 00:24:04.129: INFO: Pod "pvc-snapshottable-tester-9fl97": Phase="Pending", Reason="", readiness=false. Elapsed: 10.278490806s
... skipping 25 lines ...
Jun  8 00:24:57.315: INFO: Pod "pvc-snapshottable-tester-9fl97": Phase="Pending", Reason="", readiness=false. Elapsed: 1m3.46424364s
Jun  8 00:24:59.361: INFO: Pod "pvc-snapshottable-tester-9fl97": Phase="Pending", Reason="", readiness=false. Elapsed: 1m5.510038127s
Jun  8 00:25:01.406: INFO: Pod "pvc-snapshottable-tester-9fl97": Phase="Pending", Reason="", readiness=false. Elapsed: 1m7.554909142s
Jun  8 00:25:03.451: INFO: Pod "pvc-snapshottable-tester-9fl97": Phase="Pending", Reason="", readiness=false. Elapsed: 1m9.599789869s
Jun  8 00:25:05.499: INFO: Pod "pvc-snapshottable-tester-9fl97": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m11.648369072s
STEP: Saw pod success
Jun  8 00:25:05.499: INFO: Pod "pvc-snapshottable-tester-9fl97" satisfied condition "Succeeded or Failed"
Jun  8 00:25:05.595: INFO: Pod pvc-snapshottable-tester-9fl97 has the following logs: 
Jun  8 00:25:05.595: INFO: Deleting pod "pvc-snapshottable-tester-9fl97" in namespace "snapshotting-531"
Jun  8 00:25:05.651: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-9fl97" to be fully deleted
Jun  8 00:25:05.696: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.compg8d5] to have phase Bound
Jun  8 00:25:05.743: INFO: PersistentVolumeClaim ebs.csi.aws.compg8d5 found and phase=Bound (46.181277ms)
STEP: [init] checking the claim
... skipping 44 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:243
STEP: checking the snapshot
STEP: checking the SnapshotContent
STEP: Modifying source data test
STEP: modifying the data in the source PVC
Jun  8 00:25:39.509: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-8n4cv" in namespace "snapshotting-531" to be "Succeeded or Failed"
Jun  8 00:25:39.553: INFO: Pod "pvc-snapshottable-data-tester-8n4cv": Phase="Pending", Reason="", readiness=false. Elapsed: 44.484062ms
Jun  8 00:25:41.598: INFO: Pod "pvc-snapshottable-data-tester-8n4cv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.089404859s
Jun  8 00:25:43.651: INFO: Pod "pvc-snapshottable-data-tester-8n4cv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.141773481s
Jun  8 00:25:45.696: INFO: Pod "pvc-snapshottable-data-tester-8n4cv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.186866105s
Jun  8 00:25:47.742: INFO: Pod "pvc-snapshottable-data-tester-8n4cv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.232845859s
Jun  8 00:25:49.788: INFO: Pod "pvc-snapshottable-data-tester-8n4cv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.278681222s
Jun  8 00:25:51.833: INFO: Pod "pvc-snapshottable-data-tester-8n4cv": Phase="Pending", Reason="", readiness=false. Elapsed: 12.323729571s
Jun  8 00:25:53.881: INFO: Pod "pvc-snapshottable-data-tester-8n4cv": Phase="Pending", Reason="", readiness=false. Elapsed: 14.371951807s
Jun  8 00:25:55.948: INFO: Pod "pvc-snapshottable-data-tester-8n4cv": Phase="Pending", Reason="", readiness=false. Elapsed: 16.438686061s
Jun  8 00:25:57.994: INFO: Pod "pvc-snapshottable-data-tester-8n4cv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.484656785s
STEP: Saw pod success
Jun  8 00:25:57.994: INFO: Pod "pvc-snapshottable-data-tester-8n4cv" satisfied condition "Succeeded or Failed"
Jun  8 00:25:58.090: INFO: Pod pvc-snapshottable-data-tester-8n4cv has the following logs: 
Jun  8 00:25:58.090: INFO: Deleting pod "pvc-snapshottable-data-tester-8n4cv" in namespace "snapshotting-531"
Jun  8 00:25:58.140: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-8n4cv" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun  8 00:26:20.380: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-531 exec restored-pvc-tester-d4hfc --namespace=snapshotting-531 -- cat /mnt/test/data'
... skipping 28 lines ...
STEP: Found 27 events.
Jun  8 00:27:02.999: INFO: At 2021-06-08 00:23:53 +0000 UTC - event for ebs.csi.aws.compg8d5: {persistentvolume-controller } WaitForFirstConsumer: waiting for first consumer to be created before binding
Jun  8 00:27:03.000: INFO: At 2021-06-08 00:23:53 +0000 UTC - event for ebs.csi.aws.compg8d5: {persistentvolume-controller } ExternalProvisioning: waiting for a volume to be created, either by external provisioner "ebs.csi.aws.com" or manually created by system administrator
Jun  8 00:27:03.000: INFO: At 2021-06-08 00:23:53 +0000 UTC - event for ebs.csi.aws.compg8d5: {ebs.csi.aws.com_ebs-csi-controller-7ffff4ddf5-sbtvx_adf94ab2-13a5-4b26-a128-eb4ea88ac25d } Provisioning: External provisioner is provisioning volume for claim "snapshotting-531/ebs.csi.aws.compg8d5"
Jun  8 00:27:03.000: INFO: At 2021-06-08 00:23:57 +0000 UTC - event for ebs.csi.aws.compg8d5: {ebs.csi.aws.com_ebs-csi-controller-7ffff4ddf5-sbtvx_adf94ab2-13a5-4b26-a128-eb4ea88ac25d } ProvisioningSucceeded: Successfully provisioned volume pvc-46a76f72-8714-422b-972d-eb8e8be16a27
Jun  8 00:27:03.000: INFO: At 2021-06-08 00:23:57 +0000 UTC - event for pvc-snapshottable-tester-9fl97: {default-scheduler } Scheduled: Successfully assigned snapshotting-531/pvc-snapshottable-tester-9fl97 to ip-172-20-48-35.ca-central-1.compute.internal
Jun  8 00:27:03.000: INFO: At 2021-06-08 00:24:13 +0000 UTC - event for pvc-snapshottable-tester-9fl97: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-46a76f72-8714-422b-972d-eb8e8be16a27" : rpc error: code = DeadlineExceeded desc = context deadline exceeded
Jun  8 00:27:03.000: INFO: At 2021-06-08 00:24:18 +0000 UTC - event for pvc-snapshottable-tester-9fl97: {attachdetach-controller } FailedAttachVolume: AttachVolume.Attach failed for volume "pvc-46a76f72-8714-422b-972d-eb8e8be16a27" : rpc error: code = Internal desc = Could not attach volume "vol-0deb70fb13252bb55" to node "i-0c5448675ce608039": attachment of disk "vol-0deb70fb13252bb55" failed, expected device to be attached but was attaching
Jun  8 00:27:03.000: INFO: At 2021-06-08 00:24:31 +0000 UTC - event for pvc-snapshottable-tester-9fl97: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-46a76f72-8714-422b-972d-eb8e8be16a27" 
Jun  8 00:27:03.000: INFO: At 2021-06-08 00:25:03 +0000 UTC - event for pvc-snapshottable-tester-9fl97: {kubelet ip-172-20-48-35.ca-central-1.compute.internal} Started: Started container volume-tester
Jun  8 00:27:03.000: INFO: At 2021-06-08 00:25:03 +0000 UTC - event for pvc-snapshottable-tester-9fl97: {kubelet ip-172-20-48-35.ca-central-1.compute.internal} Created: Created container volume-tester
Jun  8 00:27:03.000: INFO: At 2021-06-08 00:25:03 +0000 UTC - event for pvc-snapshottable-tester-9fl97: {kubelet ip-172-20-48-35.ca-central-1.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" already present on machine
Jun  8 00:27:03.000: INFO: At 2021-06-08 00:25:05 +0000 UTC - event for snapshot-wr4q2: {snapshot-controller } CreatingSnapshot: Waiting for a snapshot snapshotting-531/snapshot-wr4q2 to be created by the CSI driver.
Jun  8 00:27:03.000: INFO: At 2021-06-08 00:25:39 +0000 UTC - event for pvc-snapshottable-data-tester-8n4cv: {default-scheduler } Scheduled: Successfully assigned snapshotting-531/pvc-snapshottable-data-tester-8n4cv to ip-172-20-41-166.ca-central-1.compute.internal
... skipping 219 lines ...
    /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:108
      
      /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:225
        should check snapshot fields, check restore correctly works after modifying source data, check deletion [It]
        /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:243

        Unexpected error:
            <exec.CodeExitError>: {
                Err: {
                    s: "error running /usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-531 exec restored-pvc-tester-d4hfc --namespace=snapshotting-531 -- cat /mnt/test/data:\nCommand stdout:\n\nstderr:\ncat: can't open '/mnt/test/data': No such file or directory\ncommand terminated with exit code 1\n\nerror:\nexit status 1",
                },
                Code: 1,
            }
            error running /usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-531 exec restored-pvc-tester-d4hfc --namespace=snapshotting-531 -- cat /mnt/test/data:
            Command stdout:
            
            stderr:
            cat: can't open '/mnt/test/data': No such file or directory
            command terminated with exit code 1
            
            error:
            exit status 1
        occurred

        /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:602
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
... skipping 95 lines ...
Jun  8 00:26:43.453: INFO: Pod aws-client still exists
Jun  8 00:26:45.409: INFO: Waiting for pod aws-client to disappear
Jun  8 00:26:45.453: INFO: Pod aws-client still exists
Jun  8 00:26:47.409: INFO: Waiting for pod aws-client to disappear
Jun  8 00:26:47.453: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun  8 00:26:47.780: INFO: Couldn't delete PD "aws://ca-central-1a/vol-099c0ee3443595b43", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-099c0ee3443595b43 is currently attached to i-0c5448675ce608039
	status code: 400, request id: a5d7a655-a3e0-442d-a30a-460810f8ea84
Jun  8 00:26:53.075: INFO: Couldn't delete PD "aws://ca-central-1a/vol-099c0ee3443595b43", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-099c0ee3443595b43 is currently attached to i-0c5448675ce608039
	status code: 400, request id: 0b6102e3-8a80-4d10-8a06-52089045c94e
Jun  8 00:26:58.382: INFO: Couldn't delete PD "aws://ca-central-1a/vol-099c0ee3443595b43", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-099c0ee3443595b43 is currently attached to i-0c5448675ce608039
	status code: 400, request id: 0297604d-11ec-4af7-b33e-9aebf8f166c3
Jun  8 00:27:03.723: INFO: Couldn't delete PD "aws://ca-central-1a/vol-099c0ee3443595b43", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-099c0ee3443595b43 is currently attached to i-0c5448675ce608039
	status code: 400, request id: 10ad4145-8ff4-46f4-b1c7-22ea71f56e81
Jun  8 00:27:09.015: INFO: Successfully deleted PD "aws://ca-central-1a/vol-099c0ee3443595b43".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  8 00:27:09.015: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-6389" for this suite.
... skipping 134 lines ...
Jun  8 00:25:44.652: INFO: Creating resource for dynamic PV
Jun  8 00:25:44.652: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8009lbtqm
STEP: creating a claim
Jun  8 00:25:44.700: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-8009
Jun  8 00:25:44.891: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-8009" in namespace "provisioning-8009" to be "Succeeded or Failed"
Jun  8 00:25:45.142: INFO: Pod "volume-prep-provisioning-8009": Phase="Pending", Reason="", readiness=false. Elapsed: 250.523553ms
Jun  8 00:25:47.233: INFO: Pod "volume-prep-provisioning-8009": Phase="Pending", Reason="", readiness=false. Elapsed: 2.342124875s
Jun  8 00:25:49.282: INFO: Pod "volume-prep-provisioning-8009": Phase="Pending", Reason="", readiness=false. Elapsed: 4.391264452s
Jun  8 00:25:51.525: INFO: Pod "volume-prep-provisioning-8009": Phase="Pending", Reason="", readiness=false. Elapsed: 6.634415371s
Jun  8 00:25:53.618: INFO: Pod "volume-prep-provisioning-8009": Phase="Pending", Reason="", readiness=false. Elapsed: 8.727381229s
Jun  8 00:25:55.667: INFO: Pod "volume-prep-provisioning-8009": Phase="Pending", Reason="", readiness=false. Elapsed: 10.775797449s
Jun  8 00:25:57.908: INFO: Pod "volume-prep-provisioning-8009": Phase="Pending", Reason="", readiness=false. Elapsed: 13.016466045s
Jun  8 00:26:00.000: INFO: Pod "volume-prep-provisioning-8009": Phase="Pending", Reason="", readiness=false. Elapsed: 15.109045952s
Jun  8 00:26:02.048: INFO: Pod "volume-prep-provisioning-8009": Phase="Pending", Reason="", readiness=false. Elapsed: 17.156701916s
Jun  8 00:26:04.167: INFO: Pod "volume-prep-provisioning-8009": Phase="Pending", Reason="", readiness=false. Elapsed: 19.276156499s
Jun  8 00:26:06.259: INFO: Pod "volume-prep-provisioning-8009": Phase="Pending", Reason="", readiness=false. Elapsed: 21.368279591s
Jun  8 00:26:08.354: INFO: Pod "volume-prep-provisioning-8009": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.462884978s
STEP: Saw pod success
Jun  8 00:26:08.354: INFO: Pod "volume-prep-provisioning-8009" satisfied condition "Succeeded or Failed"
Jun  8 00:26:08.354: INFO: Deleting pod "volume-prep-provisioning-8009" in namespace "provisioning-8009"
Jun  8 00:26:08.475: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-8009" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-7f6f
STEP: Checking for subpath error in container status
Jun  8 00:26:44.845: INFO: Deleting pod "pod-subpath-test-dynamicpv-7f6f" in namespace "provisioning-8009"
Jun  8 00:26:44.936: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-7f6f" to be fully deleted
STEP: Deleting pod
Jun  8 00:26:44.982: INFO: Deleting pod "pod-subpath-test-dynamicpv-7f6f" in namespace "provisioning-8009"
STEP: Deleting pvc
Jun  8 00:26:45.121: INFO: Deleting PersistentVolumeClaim "aws7pc5d"
... skipping 109 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.yi3ZpreUa/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.yi3ZpreUa/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.yi3ZpreUa/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.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Driver supports dynamic provisioning, skipping InlineVolume pattern

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

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 125 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  8 00:26:54.895: 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.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  8 00:26:55.118: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  8 00:26:55.628: INFO: Successfully created a new PD: "aws://ca-central-1a/vol-027781f6158c93db4".
Jun  8 00:26:55.628: INFO: Creating resource for pre-provisioned PV
Jun  8 00:26:55.628: INFO: Creating PVC and PV
... skipping 3 lines ...
Jun  8 00:26:55.840: INFO: PersistentVolumeClaim pvc-46ngz found but phase is Pending instead of Bound.
Jun  8 00:26:57.885: INFO: PersistentVolumeClaim pvc-46ngz found but phase is Pending instead of Bound.
Jun  8 00:26:59.932: INFO: PersistentVolumeClaim pvc-46ngz found and phase=Bound (4.137217402s)
Jun  8 00:26:59.932: INFO: Waiting up to 3m0s for PersistentVolume aws-zt4dx to have phase Bound
Jun  8 00:26:59.979: INFO: PersistentVolume aws-zt4dx found and phase=Bound (47.379113ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  8 00:27:02.263: INFO: Deleting pod "pod-d2fa92bd-2c5d-4577-906d-ef33ab91471f" in namespace "volumemode-1627"
Jun  8 00:27:02.309: INFO: Wait up to 5m0s for pod "pod-d2fa92bd-2c5d-4577-906d-ef33ab91471f" to be fully deleted
STEP: Deleting pv and pvc
Jun  8 00:27:12.398: INFO: Deleting PersistentVolumeClaim "pvc-46ngz"
Jun  8 00:27:12.444: INFO: Deleting PersistentVolume "aws-zt4dx"
Jun  8 00:27:12.635: INFO: Couldn't delete PD "aws://ca-central-1a/vol-027781f6158c93db4", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-027781f6158c93db4 is currently attached to i-0216cc8a3d86cc491
	status code: 400, request id: 2e2fbffa-b4d4-4e3c-9098-6b84b3a24255
Jun  8 00:27:17.963: INFO: Couldn't delete PD "aws://ca-central-1a/vol-027781f6158c93db4", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-027781f6158c93db4 is currently attached to i-0216cc8a3d86cc491
	status code: 400, request id: bf129861-29e8-48db-ad9e-322c147b0ffb
Jun  8 00:27:23.293: INFO: Couldn't delete PD "aws://ca-central-1a/vol-027781f6158c93db4", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-027781f6158c93db4 is currently attached to i-0216cc8a3d86cc491
	status code: 400, request id: 3212d266-6986-4d95-8c66-2d23a7f458ef
Jun  8 00:27:28.645: INFO: Successfully deleted PD "aws://ca-central-1a/vol-027781f6158c93db4".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  8 00:27:28.645: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-1627" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.yi3ZpreUa/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.yi3ZpreUa/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
    /tmp/kops.yi3ZpreUa/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.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] volumeIO
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] volumeIO
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 566 lines ...
Jun  8 00:26:37.059: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  8 00:26:37.479: INFO: Successfully created a new PD: "aws://ca-central-1a/vol-0a31c8d7669ec1dc3".
Jun  8 00:26:37.479: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-k4hx
STEP: Creating a pod to test exec-volume-test
Jun  8 00:26:37.526: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-k4hx" in namespace "volume-1953" to be "Succeeded or Failed"
Jun  8 00:26:37.571: INFO: Pod "exec-volume-test-inlinevolume-k4hx": Phase="Pending", Reason="", readiness=false. Elapsed: 44.388387ms
Jun  8 00:26:39.617: INFO: Pod "exec-volume-test-inlinevolume-k4hx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.090172803s
Jun  8 00:26:41.662: INFO: Pod "exec-volume-test-inlinevolume-k4hx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.135591649s
Jun  8 00:26:43.708: INFO: Pod "exec-volume-test-inlinevolume-k4hx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.181252173s
Jun  8 00:26:45.754: INFO: Pod "exec-volume-test-inlinevolume-k4hx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.227381412s
Jun  8 00:26:47.798: INFO: Pod "exec-volume-test-inlinevolume-k4hx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.272072072s
Jun  8 00:26:49.844: INFO: Pod "exec-volume-test-inlinevolume-k4hx": Phase="Pending", Reason="", readiness=false. Elapsed: 12.317552256s
Jun  8 00:26:51.890: INFO: Pod "exec-volume-test-inlinevolume-k4hx": Phase="Pending", Reason="", readiness=false. Elapsed: 14.363197748s
Jun  8 00:26:53.934: INFO: Pod "exec-volume-test-inlinevolume-k4hx": Phase="Pending", Reason="", readiness=false. Elapsed: 16.408036161s
Jun  8 00:26:55.987: INFO: Pod "exec-volume-test-inlinevolume-k4hx": Phase="Pending", Reason="", readiness=false. Elapsed: 18.461064471s
Jun  8 00:26:58.032: INFO: Pod "exec-volume-test-inlinevolume-k4hx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.505440112s
STEP: Saw pod success
Jun  8 00:26:58.032: INFO: Pod "exec-volume-test-inlinevolume-k4hx" satisfied condition "Succeeded or Failed"
Jun  8 00:26:58.076: INFO: Trying to get logs from node ip-172-20-36-176.ca-central-1.compute.internal pod exec-volume-test-inlinevolume-k4hx container exec-container-inlinevolume-k4hx: <nil>
STEP: delete the pod
Jun  8 00:26:58.179: INFO: Waiting for pod exec-volume-test-inlinevolume-k4hx to disappear
Jun  8 00:26:58.226: INFO: Pod exec-volume-test-inlinevolume-k4hx no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-k4hx
Jun  8 00:26:58.226: INFO: Deleting pod "exec-volume-test-inlinevolume-k4hx" in namespace "volume-1953"
Jun  8 00:26:58.425: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0a31c8d7669ec1dc3", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a31c8d7669ec1dc3 is currently attached to i-05ae10a17dc5bb2c8
	status code: 400, request id: 212f7d50-70fd-4f72-a6c4-e57b4845165c
Jun  8 00:27:03.716: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0a31c8d7669ec1dc3", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a31c8d7669ec1dc3 is currently attached to i-05ae10a17dc5bb2c8
	status code: 400, request id: 8fbe6e76-3b2c-4b72-954c-f20b155f8edb
Jun  8 00:27:09.078: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0a31c8d7669ec1dc3", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a31c8d7669ec1dc3 is currently attached to i-05ae10a17dc5bb2c8
	status code: 400, request id: c508d1de-6a63-41b2-9af9-6d604cb5be11
Jun  8 00:27:14.366: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0a31c8d7669ec1dc3", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a31c8d7669ec1dc3 is currently attached to i-05ae10a17dc5bb2c8
	status code: 400, request id: 044168f8-d0af-4a50-844c-d40c8ac13b43
Jun  8 00:27:19.697: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0a31c8d7669ec1dc3", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a31c8d7669ec1dc3 is currently attached to i-05ae10a17dc5bb2c8
	status code: 400, request id: 734987ee-03ea-4cd6-8bce-3c9cab1ba58c
Jun  8 00:27:25.008: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0a31c8d7669ec1dc3", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a31c8d7669ec1dc3 is currently attached to i-05ae10a17dc5bb2c8
	status code: 400, request id: cddd0892-3d24-4b77-99d6-ce3e4dc724d7
Jun  8 00:27:30.359: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0a31c8d7669ec1dc3", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a31c8d7669ec1dc3 is currently attached to i-05ae10a17dc5bb2c8
	status code: 400, request id: 6c5164a8-f2a3-4d5c-a616-d2e91dcc4a2c
Jun  8 00:27:35.656: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0a31c8d7669ec1dc3", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a31c8d7669ec1dc3 is currently attached to i-05ae10a17dc5bb2c8
	status code: 400, request id: 72869e76-7077-4e90-892d-7984053aec06
Jun  8 00:27:40.978: INFO: Successfully deleted PD "aws://ca-central-1a/vol-0a31c8d7669ec1dc3".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  8 00:27:40.979: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-1953" for this suite.
... skipping 18 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.yi3ZpreUa/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.yi3ZpreUa/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.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 238 lines ...
Jun  8 00:26:51.960: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7940sk2qq
STEP: creating a claim
Jun  8 00:26:52.006: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-hts4
STEP: Creating a pod to test subpath
Jun  8 00:26:52.153: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-hts4" in namespace "provisioning-7940" to be "Succeeded or Failed"
Jun  8 00:26:52.198: INFO: Pod "pod-subpath-test-dynamicpv-hts4": Phase="Pending", Reason="", readiness=false. Elapsed: 45.052053ms
Jun  8 00:26:54.243: INFO: Pod "pod-subpath-test-dynamicpv-hts4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.090303869s
Jun  8 00:26:56.289: INFO: Pod "pod-subpath-test-dynamicpv-hts4": Phase="Pending", Reason="", readiness=false. Elapsed: 4.136337565s
Jun  8 00:26:58.337: INFO: Pod "pod-subpath-test-dynamicpv-hts4": Phase="Pending", Reason="", readiness=false. Elapsed: 6.184334256s
Jun  8 00:27:00.382: INFO: Pod "pod-subpath-test-dynamicpv-hts4": Phase="Pending", Reason="", readiness=false. Elapsed: 8.229586442s
Jun  8 00:27:02.428: INFO: Pod "pod-subpath-test-dynamicpv-hts4": Phase="Pending", Reason="", readiness=false. Elapsed: 10.275599351s
... skipping 2 lines ...
Jun  8 00:27:08.574: INFO: Pod "pod-subpath-test-dynamicpv-hts4": Phase="Pending", Reason="", readiness=false. Elapsed: 16.421643101s
Jun  8 00:27:10.621: INFO: Pod "pod-subpath-test-dynamicpv-hts4": Phase="Pending", Reason="", readiness=false. Elapsed: 18.46809626s
Jun  8 00:27:12.667: INFO: Pod "pod-subpath-test-dynamicpv-hts4": Phase="Pending", Reason="", readiness=false. Elapsed: 20.51465951s
Jun  8 00:27:14.714: INFO: Pod "pod-subpath-test-dynamicpv-hts4": Phase="Pending", Reason="", readiness=false. Elapsed: 22.561555243s
Jun  8 00:27:16.760: INFO: Pod "pod-subpath-test-dynamicpv-hts4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.607159038s
STEP: Saw pod success
Jun  8 00:27:16.760: INFO: Pod "pod-subpath-test-dynamicpv-hts4" satisfied condition "Succeeded or Failed"
Jun  8 00:27:16.805: INFO: Trying to get logs from node ip-172-20-48-35.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-hts4 container test-container-subpath-dynamicpv-hts4: <nil>
STEP: delete the pod
Jun  8 00:27:16.942: INFO: Waiting for pod pod-subpath-test-dynamicpv-hts4 to disappear
Jun  8 00:27:16.988: INFO: Pod pod-subpath-test-dynamicpv-hts4 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-hts4
Jun  8 00:27:16.988: INFO: Deleting pod "pod-subpath-test-dynamicpv-hts4" in namespace "provisioning-7940"
... skipping 410 lines ...
Jun  8 00:26:21.171: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8164-e2e-sc4dfcr
STEP: creating a claim
Jun  8 00:26:21.218: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-rzlw
STEP: Creating a pod to test subpath
Jun  8 00:26:21.355: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-rzlw" in namespace "provisioning-8164" to be "Succeeded or Failed"
Jun  8 00:26:21.400: INFO: Pod "pod-subpath-test-dynamicpv-rzlw": Phase="Pending", Reason="", readiness=false. Elapsed: 44.389136ms
Jun  8 00:26:23.445: INFO: Pod "pod-subpath-test-dynamicpv-rzlw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.089814654s
Jun  8 00:26:25.490: INFO: Pod "pod-subpath-test-dynamicpv-rzlw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.134758485s
Jun  8 00:26:27.535: INFO: Pod "pod-subpath-test-dynamicpv-rzlw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.179593855s
Jun  8 00:26:29.580: INFO: Pod "pod-subpath-test-dynamicpv-rzlw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.224372319s
Jun  8 00:26:31.626: INFO: Pod "pod-subpath-test-dynamicpv-rzlw": Phase="Pending", Reason="", readiness=false. Elapsed: 10.27073925s
... skipping 9 lines ...
Jun  8 00:26:52.093: INFO: Pod "pod-subpath-test-dynamicpv-rzlw": Phase="Pending", Reason="", readiness=false. Elapsed: 30.73798644s
Jun  8 00:26:54.138: INFO: Pod "pod-subpath-test-dynamicpv-rzlw": Phase="Pending", Reason="", readiness=false. Elapsed: 32.782515786s
Jun  8 00:26:56.185: INFO: Pod "pod-subpath-test-dynamicpv-rzlw": Phase="Pending", Reason="", readiness=false. Elapsed: 34.829884964s
Jun  8 00:26:58.239: INFO: Pod "pod-subpath-test-dynamicpv-rzlw": Phase="Pending", Reason="", readiness=false. Elapsed: 36.883738974s
Jun  8 00:27:00.284: INFO: Pod "pod-subpath-test-dynamicpv-rzlw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 38.92861648s
STEP: Saw pod success
Jun  8 00:27:00.284: INFO: Pod "pod-subpath-test-dynamicpv-rzlw" satisfied condition "Succeeded or Failed"
Jun  8 00:27:00.328: INFO: Trying to get logs from node ip-172-20-36-176.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-rzlw container test-container-subpath-dynamicpv-rzlw: <nil>
STEP: delete the pod
Jun  8 00:27:00.434: INFO: Waiting for pod pod-subpath-test-dynamicpv-rzlw to disappear
Jun  8 00:27:00.478: INFO: Pod pod-subpath-test-dynamicpv-rzlw no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-rzlw
Jun  8 00:27:00.478: INFO: Deleting pod "pod-subpath-test-dynamicpv-rzlw" in namespace "provisioning-8164"
... skipping 45 lines ...
Jun  8 00:27:09.331: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2562-e2e-scg584t
STEP: creating a claim
Jun  8 00:27:09.378: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-hxsq
STEP: Creating a pod to test subpath
Jun  8 00:27:09.515: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-hxsq" in namespace "provisioning-2562" to be "Succeeded or Failed"
Jun  8 00:27:09.558: INFO: Pod "pod-subpath-test-dynamicpv-hxsq": Phase="Pending", Reason="", readiness=false. Elapsed: 43.921245ms
Jun  8 00:27:11.606: INFO: Pod "pod-subpath-test-dynamicpv-hxsq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.090988256s
Jun  8 00:27:13.650: INFO: Pod "pod-subpath-test-dynamicpv-hxsq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.135315131s
Jun  8 00:27:15.695: INFO: Pod "pod-subpath-test-dynamicpv-hxsq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.17995851s
Jun  8 00:27:17.739: INFO: Pod "pod-subpath-test-dynamicpv-hxsq": Phase="Pending", Reason="", readiness=false. Elapsed: 8.224582332s
Jun  8 00:27:19.786: INFO: Pod "pod-subpath-test-dynamicpv-hxsq": Phase="Pending", Reason="", readiness=false. Elapsed: 10.271039899s
... skipping 10 lines ...
Jun  8 00:27:42.283: INFO: Pod "pod-subpath-test-dynamicpv-hxsq": Phase="Pending", Reason="", readiness=false. Elapsed: 32.768263118s
Jun  8 00:27:44.327: INFO: Pod "pod-subpath-test-dynamicpv-hxsq": Phase="Pending", Reason="", readiness=false. Elapsed: 34.812731997s
Jun  8 00:27:46.380: INFO: Pod "pod-subpath-test-dynamicpv-hxsq": Phase="Pending", Reason="", readiness=false. Elapsed: 36.865147327s
Jun  8 00:27:48.424: INFO: Pod "pod-subpath-test-dynamicpv-hxsq": Phase="Pending", Reason="", readiness=false. Elapsed: 38.90965442s
Jun  8 00:27:50.472: INFO: Pod "pod-subpath-test-dynamicpv-hxsq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 40.95734518s
STEP: Saw pod success
Jun  8 00:27:50.472: INFO: Pod "pod-subpath-test-dynamicpv-hxsq" satisfied condition "Succeeded or Failed"
Jun  8 00:27:50.517: INFO: Trying to get logs from node ip-172-20-36-176.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-hxsq container test-container-subpath-dynamicpv-hxsq: <nil>
STEP: delete the pod
Jun  8 00:27:50.627: INFO: Waiting for pod pod-subpath-test-dynamicpv-hxsq to disappear
Jun  8 00:27:50.674: INFO: Pod pod-subpath-test-dynamicpv-hxsq no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-hxsq
Jun  8 00:27:50.674: INFO: Deleting pod "pod-subpath-test-dynamicpv-hxsq" in namespace "provisioning-2562"
... skipping 31 lines ...

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

Jun  8 00:27:57.736: INFO: Error updating pvc awsx52bb: PersistentVolumeClaim "awsx52bb" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-647rh2bs",
  	... // 2 identical fields
  }

Jun  8 00:27:59.736: INFO: Error updating pvc awsx52bb: PersistentVolumeClaim "awsx52bb" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-647rh2bs",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun  8 00:28:25.847: INFO: Error updating pvc awsx52bb: PersistentVolumeClaim "awsx52bb" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 196 lines ...

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

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

    /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:92
------------------------------
... skipping 79 lines ...
Jun  8 00:28:14.551: INFO: Waiting for pod aws-client to disappear
Jun  8 00:28:14.596: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun  8 00:28:14.596: INFO: Deleting PersistentVolumeClaim "pvc-t4j2z"
Jun  8 00:28:14.649: INFO: Deleting PersistentVolume "aws-nqff8"
Jun  8 00:28:15.049: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0c5d9c6414063dd6d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c5d9c6414063dd6d is currently attached to i-0216cc8a3d86cc491
	status code: 400, request id: 10f895b1-9d57-47a6-aa9a-544969ea51c4
Jun  8 00:28:20.380: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0c5d9c6414063dd6d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c5d9c6414063dd6d is currently attached to i-0216cc8a3d86cc491
	status code: 400, request id: b01c37be-f8b4-4e86-a77e-6a129c12c6aa
Jun  8 00:28:25.708: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0c5d9c6414063dd6d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c5d9c6414063dd6d is currently attached to i-0216cc8a3d86cc491
	status code: 400, request id: 15df6748-0978-4b5e-9448-dd729fc3b76c
Jun  8 00:28:31.022: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0c5d9c6414063dd6d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c5d9c6414063dd6d is currently attached to i-0216cc8a3d86cc491
	status code: 400, request id: f8243fc0-b5e5-4289-916b-2feba37b499b
Jun  8 00:28:36.322: INFO: Successfully deleted PD "aws://ca-central-1a/vol-0c5d9c6414063dd6d".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumes
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  8 00:28:36.323: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-167" for this suite.
... skipping 14 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  8 00:27:11.286: 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.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun  8 00:27:11.591: INFO: Creating resource for dynamic PV
Jun  8 00:27:11.591: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7895-e2e-sc5z28z
STEP: creating a claim
Jun  8 00:27:11.639: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-sv7g
STEP: Checking for subpath error in container status
Jun  8 00:27:54.079: INFO: Deleting pod "pod-subpath-test-dynamicpv-sv7g" in namespace "provisioning-7895"
Jun  8 00:27:54.175: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-sv7g" to be fully deleted
STEP: Deleting pod
Jun  8 00:28:00.314: INFO: Deleting pod "pod-subpath-test-dynamicpv-sv7g" in namespace "provisioning-7895"
STEP: Deleting pvc
Jun  8 00:28:00.470: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com96lxq"
... skipping 15 lines ...

• [SLOW TEST:86.194 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath file is outside the volume [Slow][LinuxOnly]
    /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 76 lines ...
Jun  8 00:28:34.579: INFO: Waiting for pod aws-client to disappear
Jun  8 00:28:34.624: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun  8 00:28:34.624: INFO: Deleting PersistentVolumeClaim "pvc-9xslb"
Jun  8 00:28:34.675: INFO: Deleting PersistentVolume "aws-fqhzb"
Jun  8 00:28:35.074: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0eaeb72bf675484ae", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0eaeb72bf675484ae is currently attached to i-0216cc8a3d86cc491
	status code: 400, request id: 9861c1ff-3e6a-4ccb-a321-45fa9523e9f3
Jun  8 00:28:40.390: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0eaeb72bf675484ae", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0eaeb72bf675484ae is currently attached to i-0216cc8a3d86cc491
	status code: 400, request id: 4fd7fd0d-797b-4753-9046-1b58023b732e
Jun  8 00:28:45.740: INFO: Successfully deleted PD "aws://ca-central-1a/vol-0eaeb72bf675484ae".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  8 00:28:45.834: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8042" for this suite.
... skipping 286 lines ...
Jun  8 00:28:48.465: INFO: Waiting for pod aws-client to disappear
Jun  8 00:28:48.509: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun  8 00:28:48.509: INFO: Deleting PersistentVolumeClaim "pvc-5mq8j"
Jun  8 00:28:48.555: INFO: Deleting PersistentVolume "aws-dvzrd"
Jun  8 00:28:48.929: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0e95a0f0e393b7395", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e95a0f0e393b7395 is currently attached to i-0c5448675ce608039
	status code: 400, request id: d448035c-c27e-4736-abaf-188a78b7974d
Jun  8 00:28:54.209: INFO: Couldn't delete PD "aws://ca-central-1a/vol-0e95a0f0e393b7395", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e95a0f0e393b7395 is currently attached to i-0c5448675ce608039
	status code: 400, request id: 28bd847f-61f4-4a9c-b57a-8916fd904cc2
Jun  8 00:28:59.550: INFO: Successfully deleted PD "aws://ca-central-1a/vol-0e95a0f0e393b7395".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  8 00:28:59.550: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-3696" for this suite.
... skipping 158 lines ...
Jun  8 00:28:11.484: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6948rpglb
STEP: creating a claim
Jun  8 00:28:11.529: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-zbwd
STEP: Creating a pod to test subpath
Jun  8 00:28:11.665: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-zbwd" in namespace "provisioning-6948" to be "Succeeded or Failed"
Jun  8 00:28:11.709: INFO: Pod "pod-subpath-test-dynamicpv-zbwd": Phase="Pending", Reason="", readiness=false. Elapsed: 43.911857ms
Jun  8 00:28:13.754: INFO: Pod "pod-subpath-test-dynamicpv-zbwd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.089160312s
Jun  8 00:28:15.809: INFO: Pod "pod-subpath-test-dynamicpv-zbwd": Phase="Pending", Reason="", readiness=false. Elapsed: 4.14464101s
Jun  8 00:28:17.861: INFO: Pod "pod-subpath-test-dynamicpv-zbwd": Phase="Pending", Reason="", readiness=false. Elapsed: 6.196547611s
Jun  8 00:28:19.907: INFO: Pod "pod-subpath-test-dynamicpv-zbwd": Phase="Pending", Reason="", readiness=false. Elapsed: 8.242039727s
Jun  8 00:28:21.951: INFO: Pod "pod-subpath-test-dynamicpv-zbwd": Phase="Pending", Reason="", readiness=false. Elapsed: 10.286780662s
... skipping 10 lines ...
Jun  8 00:28:44.492: INFO: Pod "pod-subpath-test-dynamicpv-zbwd": Phase="Pending", Reason="", readiness=false. Elapsed: 32.827373805s
Jun  8 00:28:46.537: INFO: Pod "pod-subpath-test-dynamicpv-zbwd": Phase="Pending", Reason="", readiness=false. Elapsed: 34.871998622s
Jun  8 00:28:48.582: INFO: Pod "pod-subpath-test-dynamicpv-zbwd": Phase="Pending", Reason="", readiness=false. Elapsed: 36.917638414s
Jun  8 00:28:50.627: INFO: Pod "pod-subpath-test-dynamicpv-zbwd": Phase="Pending", Reason="", readiness=false. Elapsed: 38.962380199s
Jun  8 00:28:52.672: INFO: Pod "pod-subpath-test-dynamicpv-zbwd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 41.007787892s
STEP: Saw pod success
Jun  8 00:28:52.673: INFO: Pod "pod-subpath-test-dynamicpv-zbwd" satisfied condition "Succeeded or Failed"
Jun  8 00:28:52.717: INFO: Trying to get logs from node ip-172-20-48-35.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-zbwd container test-container-subpath-dynamicpv-zbwd: <nil>
STEP: delete the pod
Jun  8 00:28:52.817: INFO: Waiting for pod pod-subpath-test-dynamicpv-zbwd to disappear
Jun  8 00:28:52.861: INFO: Pod pod-subpath-test-dynamicpv-zbwd no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-zbwd
Jun  8 00:28:52.861: INFO: Deleting pod "pod-subpath-test-dynamicpv-zbwd" in namespace "provisioning-6948"
STEP: Creating pod pod-subpath-test-dynamicpv-zbwd
STEP: Creating a pod to test subpath
Jun  8 00:28:52.953: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-zbwd" in namespace "provisioning-6948" to be "Succeeded or Failed"
Jun  8 00:28:53.026: INFO: Pod "pod-subpath-test-dynamicpv-zbwd": Phase="Pending", Reason="", readiness=false. Elapsed: 72.750182ms
Jun  8 00:28:55.080: INFO: Pod "pod-subpath-test-dynamicpv-zbwd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.126917721s
STEP: Saw pod success
Jun  8 00:28:55.080: INFO: Pod "pod-subpath-test-dynamicpv-zbwd" satisfied condition "Succeeded or Failed"
Jun  8 00:28:55.126: INFO: Trying to get logs from node ip-172-20-48-35.ca-central-1.compute.internal pod pod-subpath-test-dynamicpv-zbwd container test-container-subpath-dynamicpv-zbwd: <nil>
STEP: delete the pod
Jun  8 00:28:55.226: INFO: Waiting for pod pod-subpath-test-dynamicpv-zbwd to disappear
Jun  8 00:28:55.273: INFO: Pod pod-subpath-test-dynamicpv-zbwd no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-zbwd
Jun  8 00:28:55.273: INFO: Deleting pod "pod-subpath-test-dynamicpv-zbwd" in namespace "provisioning-6948"
... skipping 808 lines ...
Jun  8 00:28:06.737: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-5830-e2e-scj5bfg      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-5830    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-5830-e2e-scj5bfg,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-5830    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-5830-e2e-scj5bfg,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-5830    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-5830-e2e-scj5bfg,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-5830-e2e-scj5bfg    9a576c9f-a340-45dd-81c9-2cd2425e6244 13989 0 2021-06-08 00:28:06 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-08 00:28:06 +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-dljwc pvc- provisioning-5830  8ff9ed07-7013-483f-a282-e4d97c53ccac 13990 0 2021-06-08 00:28:06 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-08 00:28:06 +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-5830-e2e-scj5bfg,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-a8bbfa05-77d3-4b44-8b22-73490afea8a5 in namespace provisioning-5830
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun  8 00:28:21.239: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-mwsgd" in namespace "provisioning-5830" to be "Succeeded or Failed"
Jun  8 00:28:21.283: INFO: Pod "pvc-volume-tester-writer-mwsgd": Phase="Pending", Reason="", readiness=false. Elapsed: 44.446964ms
Jun  8 00:28:23.328: INFO: Pod "pvc-volume-tester-writer-mwsgd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.089831224s
Jun  8 00:28:25.373: INFO: Pod "pvc-volume-tester-writer-mwsgd": Phase="Pending", Reason="", readiness=false. Elapsed: 4.134562937s
Jun  8 00:28:27.418: INFO: Pod "pvc-volume-tester-writer-mwsgd": Phase="Pending", Reason="", readiness=false. Elapsed: 6.179045464s
Jun  8 00:28:29.463: INFO: Pod "pvc-volume-tester-writer-mwsgd": Phase="Pending", Reason="", readiness=false. Elapsed: 8.224400062s
Jun  8 00:28:31.510: INFO: Pod "pvc-volume-tester-writer-mwsgd": Phase="Pending", Reason="", readiness=false. Elapsed: 10.271334778s
... skipping 22 lines ...
Jun  8 00:29:18.572: INFO: Pod "pvc-volume-tester-writer-mwsgd": Phase="Pending", Reason="", readiness=false. Elapsed: 57.333703503s
Jun  8 00:29:20.617: INFO: Pod "pvc-volume-tester-writer-mwsgd": Phase="Pending", Reason="", readiness=false. Elapsed: 59.378240566s
Jun  8 00:29:22.661: INFO: Pod "pvc-volume-tester-writer-mwsgd": Phase="Pending", Reason="", readiness=false. Elapsed: 1m1.422582658s
Jun  8 00:29:24.706: INFO: Pod "pvc-volume-tester-writer-mwsgd": Phase="Pending", Reason="", readiness=false. Elapsed: 1m3.467107613s
Jun  8 00:29:26.750: INFO: Pod "pvc-volume-tester-writer-mwsgd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m5.511748919s
STEP: Saw pod success
Jun  8 00:29:26.750: INFO: Pod "pvc-volume-tester-writer-mwsgd" satisfied condition "Succeeded or Failed"
Jun  8 00:29:26.840: INFO: Pod pvc-volume-tester-writer-mwsgd has the following logs: 
Jun  8 00:29:26.840: INFO: Deleting pod "pvc-volume-tester-writer-mwsgd" in namespace "provisioning-5830"
Jun  8 00:29:26.888: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-mwsgd" 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-48-35.ca-central-1.compute.internal"
Jun  8 00:29:27.068: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-fzcgd" in namespace "provisioning-5830" to be "Succeeded or Failed"
Jun  8 00:29:27.112: INFO: Pod "pvc-volume-tester-reader-fzcgd": Phase="Pending", Reason="", readiness=false. Elapsed: 44.237046ms
Jun  8 00:29:29.158: INFO: Pod "pvc-volume-tester-reader-fzcgd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.090007312s
Jun  8 00:29:31.202: INFO: Pod "pvc-volume-tester-reader-fzcgd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.134479052s
STEP: Saw pod success
Jun  8 00:29:31.202: INFO: Pod "pvc-volume-tester-reader-fzcgd" satisfied condition "Succeeded or Failed"
Jun  8 00:29:31.292: INFO: Pod pvc-volume-tester-reader-fzcgd has the following logs: hello world

Jun  8 00:29:31.292: INFO: Deleting pod "pvc-volume-tester-reader-fzcgd" in namespace "provisioning-5830"
Jun  8 00:29:31.343: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-fzcgd" to be fully deleted
Jun  8 00:29:31.387: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-dljwc] to have phase Bound
Jun  8 00:29:31.438: INFO: PersistentVolumeClaim pvc-dljwc found and phase=Bound (50.362703ms)
... skipping 338 lines ...
    /tmp/kops.yi3ZpreUa/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/ephemeral.go:173
------------------------------


Summarizing 1 Failure:

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

Ran 141 of 485 Specs in 575.993 seconds
FAIL! -- 140 Passed | 1 Failed | 0 Pending | 344 Skipped


Ginkgo ran 1 suite in 10m52.113433599s
Test Suite Failed
+ kops-finish
+ kubetest2 kops -v=2 --cloud-provider=aws --cluster-name=e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --admin-access= --kops-binary-path=/home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops --down
I0608 00:30:37.571471   26751 app.go:59] RunDir for this run: "/logs/artifacts/d99a3341-c7ec-11eb-8f42-e213a67c471c"
I0608 00:30:37.571630   26751 app.go:90] ID for this run: "d99a3341-c7ec-11eb-8f42-e213a67c471c"
I0608 00:30:37.571659   26751 dumplogs.go:38] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops toolbox dump --name e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ubuntu
I0608 00:30:37.597382   26757 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
... skipping 1489 lines ...