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

No Test Failures!


Error lines from build-log.txt

... skipping 486 lines ...
I0610 00:08:41.748628   11670 up.go:43] Cleaning up any leaked resources from previous cluster
I0610 00:08:41.748641   11670 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
I0610 00:08:41.763944   11676 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0610 00:08:41.764126   11676 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io" not found
W0610 00:08:42.296904   11670 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0610 00:08:42.296974   11670 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
I0610 00:08:42.310115   11686 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0610 00:08:42.310194   11686 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io" not found
I0610 00:08:42.855312   11670 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/06/10 00:08:42 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
I0610 00:08:42.863955   11670 http.go:37] curl https://ip.jsb.workers.dev
I0610 00:08:43.065572   11670 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 34.69.21.147/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones us-east-2a --master-size c5.large
I0610 00:08:43.078999   11698 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0610 00:08:43.079161   11698 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I0610 00:08:43.122486   11698 create_cluster.go:728] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0610 00:08:43.703857   11698 new_cluster.go:1039]  Cloud Provider ID = aws
... skipping 40 lines ...

I0610 00:09:09.201106   11670 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
I0610 00:09:09.214731   11719 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0610 00:09:09.214812   11719 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io

W0610 00:09:10.399060   11719 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-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

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
W0610 00:09:20.441841   11719 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

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
W0610 00:09:30.502621   11719 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

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
W0610 00:09:40.561574   11719 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

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
W0610 00:09:50.595399   11719 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

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
W0610 00:10:00.641384   11719 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

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
W0610 00:10:10.708281   11719 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

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
W0610 00:10:20.752676   11719 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

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
W0610 00:10:30.809872   11719 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

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
W0610 00:10:40.856376   11719 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

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
W0610 00:10:50.900962   11719 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

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
W0610 00:11:00.947536   11719 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

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
W0610 00:11:11.005732   11719 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

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
W0610 00:11:21.056678   11719 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

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
W0610 00:11:31.098533   11719 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

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
W0610 00:11:41.207464   11719 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

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
W0610 00:11:51.263178   11719 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

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
W0610 00:12:01.306947   11719 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

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
W0610 00:12:11.392854   11719 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

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
W0610 00:12:21.436469   11719 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

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
W0610 00:12:31.497886   11719 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

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
W0610 00:12:41.554271   11719 validate_cluster.go:221] (will retry): cluster not yet healthy
W0610 00:12:51.585420   11719 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-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

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
W0610 00:13:01.624342   11719 validate_cluster.go:221] (will retry): cluster not yet healthy
W0610 00:13:11.669968   11719 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-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

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
W0610 00:13:21.726872   11719 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

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
W0610 00:13:31.761752   11719 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

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
W0610 00:13:41.803844   11719 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

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
W0610 00:13:51.862186   11719 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

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
W0610 00:14:01.922494   11719 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

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
W0610 00:14:11.962893   11719 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

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
W0610 00:14:22.029743   11719 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

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
W0610 00:14:32.075120   11719 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

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
W0610 00:14:42.128616   11719 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 15 lines ...
Pod	kube-system/coredns-autoscaler-6f594f4c58-4k77g		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-4k77g" is pending
Pod	kube-system/coredns-f45c4bf76-6mnr9			system-cluster-critical pod "coredns-f45c4bf76-6mnr9" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-hscl7		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-hscl7" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-zrvjv		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-zrvjv" is pending
Pod	kube-system/kops-controller-vlnzh			system-node-critical pod "kops-controller-vlnzh" is pending

Validation Failed
W0610 00:14:53.599468   11719 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Pod	kube-system/cert-manager-webhook-7bbf67968-8dhmp	system-cluster-critical pod "cert-manager-webhook-7bbf67968-8dhmp" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-4k77g		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-4k77g" is pending
Pod	kube-system/coredns-f45c4bf76-6mnr9			system-cluster-critical pod "coredns-f45c4bf76-6mnr9" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-hscl7		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-hscl7" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-zrvjv		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-zrvjv" is pending

Validation Failed
W0610 00:15:04.731301   11719 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 17 lines ...
Pod	kube-system/coredns-f45c4bf76-6mnr9					system-cluster-critical pod "coredns-f45c4bf76-6mnr9" is pending
Pod	kube-system/ebs-csi-node-5dj6k						system-node-critical pod "ebs-csi-node-5dj6k" is pending
Pod	kube-system/ebs-csi-node-mddvg						system-node-critical pod "ebs-csi-node-mddvg" is pending
Pod	kube-system/kube-proxy-ip-172-20-37-21.us-east-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-37-21.us-east-2.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-56-177.us-east-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-56-177.us-east-2.compute.internal" is pending

Validation Failed
W0610 00:15:15.812016   11719 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 22 lines ...
Pod	kube-system/ebs-csi-node-5dj6k						system-node-critical pod "ebs-csi-node-5dj6k" is pending
Pod	kube-system/ebs-csi-node-cs4x8						system-node-critical pod "ebs-csi-node-cs4x8" is pending
Pod	kube-system/ebs-csi-node-mddvg						system-node-critical pod "ebs-csi-node-mddvg" is pending
Pod	kube-system/ebs-csi-node-wv627						system-node-critical pod "ebs-csi-node-wv627" is pending
Pod	kube-system/kube-proxy-ip-172-20-40-185.us-east-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-40-185.us-east-2.compute.internal" is pending

Validation Failed
W0610 00:15:26.914835   11719 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 17 lines ...
Pod	kube-system/cert-manager-webhook-7bbf67968-8dhmp	system-cluster-critical pod "cert-manager-webhook-7bbf67968-8dhmp" is not ready (cert-manager)
Pod	kube-system/coredns-autoscaler-6f594f4c58-4k77g		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-4k77g" is pending
Pod	kube-system/coredns-f45c4bf76-6mnr9			system-cluster-critical pod "coredns-f45c4bf76-6mnr9" is pending
Pod	kube-system/ebs-csi-node-cs4x8				system-node-critical pod "ebs-csi-node-cs4x8" is pending
Pod	kube-system/ebs-csi-node-wv627				system-node-critical pod "ebs-csi-node-wv627" is pending

Validation Failed
W0610 00:15:38.056334   11719 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Node	ip-172-20-40-185.us-east-2.compute.internal	node "ip-172-20-40-185.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/calico-node-vgvdq			system-node-critical pod "calico-node-vgvdq" is not ready (calico-node)
Pod	kube-system/calico-node-wqnzl			system-node-critical pod "calico-node-wqnzl" is pending

Validation Failed
W0610 00:15:49.172617   11719 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

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

      Distro debian doesn't support ntfs -- skipping

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

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

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

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

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

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

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

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

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

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 175 lines ...
STEP: Creating a kubernetes client
Jun 10 00:19:04.115: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename volumemode
W0610 00:19:04.445430   25615 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Jun 10 00:19:04.445: 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.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 10 00:19:04.536: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 10 00:19:05.077: INFO: Successfully created a new PD: "aws://us-east-2a/vol-020006dd3ec3c6731".
Jun 10 00:19:05.077: INFO: Creating resource for pre-provisioned PV
Jun 10 00:19:05.077: INFO: Creating PVC and PV
... skipping 5 lines ...
Jun 10 00:19:09.533: INFO: PersistentVolumeClaim pvc-68lwr found but phase is Pending instead of Bound.
Jun 10 00:19:11.576: INFO: PersistentVolumeClaim pvc-68lwr found but phase is Pending instead of Bound.
Jun 10 00:19:13.620: INFO: PersistentVolumeClaim pvc-68lwr found and phase=Bound (8.210777597s)
Jun 10 00:19:13.620: INFO: Waiting up to 3m0s for PersistentVolume aws-wnxtp to have phase Bound
Jun 10 00:19:13.661: INFO: PersistentVolume aws-wnxtp found and phase=Bound (41.389374ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 10 00:19:17.912: INFO: Deleting pod "pod-2f02c7c8-8749-41c2-ae10-1b6c5133e1f2" in namespace "volumemode-6009"
Jun 10 00:19:17.957: INFO: Wait up to 5m0s for pod "pod-2f02c7c8-8749-41c2-ae10-1b6c5133e1f2" to be fully deleted
STEP: Deleting pv and pvc
Jun 10 00:19:24.042: INFO: Deleting PersistentVolumeClaim "pvc-68lwr"
Jun 10 00:19:24.086: INFO: Deleting PersistentVolume "aws-wnxtp"
Jun 10 00:19:24.264: INFO: Couldn't delete PD "aws://us-east-2a/vol-020006dd3ec3c6731", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-020006dd3ec3c6731 is currently attached to i-0c35a223bdb203427
	status code: 400, request id: 1f27b6f0-e9b1-414a-ae42-5b99c40b594c
Jun 10 00:19:29.580: INFO: Successfully deleted PD "aws://us-east-2a/vol-020006dd3ec3c6731".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 10 00:19:29.580: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-6009" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Ze8yNfZ8r/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Ze8yNfZ8r/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
    /tmp/kops.Ze8yNfZ8r/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.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 10 00:19:29.727: INFO: Driver ebs.csi.aws.com doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
... skipping 51 lines ...
Jun 10 00:19:08.016: INFO: Creating resource for dynamic PV
Jun 10 00:19:08.016: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-647582plp
STEP: creating a claim
STEP: Expanding non-expandable pvc
Jun 10 00:19:08.145: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 10 00:19:08.239: INFO: Error updating pvc awsbxhdt: PersistentVolumeClaim "awsbxhdt" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-647582plp",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun 10 00:19:38.415: INFO: Error updating pvc awsbxhdt: PersistentVolumeClaim "awsbxhdt" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 115 lines ...
Jun 10 00:19:07.611: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 10 00:19:08.086: INFO: Successfully created a new PD: "aws://us-east-2a/vol-0d63a1382df72671d".
Jun 10 00:19:08.086: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-8fp9
STEP: Creating a pod to test exec-volume-test
Jun 10 00:19:08.135: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-8fp9" in namespace "volume-5848" to be "Succeeded or Failed"
Jun 10 00:19:08.176: INFO: Pod "exec-volume-test-inlinevolume-8fp9": Phase="Pending", Reason="", readiness=false. Elapsed: 40.873104ms
Jun 10 00:19:10.221: INFO: Pod "exec-volume-test-inlinevolume-8fp9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.08578215s
Jun 10 00:19:12.268: INFO: Pod "exec-volume-test-inlinevolume-8fp9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.133059659s
Jun 10 00:19:14.312: INFO: Pod "exec-volume-test-inlinevolume-8fp9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.176316735s
Jun 10 00:19:16.354: INFO: Pod "exec-volume-test-inlinevolume-8fp9": Phase="Pending", Reason="", readiness=false. Elapsed: 8.218366128s
Jun 10 00:19:18.395: INFO: Pod "exec-volume-test-inlinevolume-8fp9": Phase="Pending", Reason="", readiness=false. Elapsed: 10.259749332s
Jun 10 00:19:20.438: INFO: Pod "exec-volume-test-inlinevolume-8fp9": Phase="Pending", Reason="", readiness=false. Elapsed: 12.302786815s
Jun 10 00:19:22.480: INFO: Pod "exec-volume-test-inlinevolume-8fp9": Phase="Running", Reason="", readiness=true. Elapsed: 14.34451469s
Jun 10 00:19:24.522: INFO: Pod "exec-volume-test-inlinevolume-8fp9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.386358386s
STEP: Saw pod success
Jun 10 00:19:24.522: INFO: Pod "exec-volume-test-inlinevolume-8fp9" satisfied condition "Succeeded or Failed"
Jun 10 00:19:24.563: INFO: Trying to get logs from node ip-172-20-56-177.us-east-2.compute.internal pod exec-volume-test-inlinevolume-8fp9 container exec-container-inlinevolume-8fp9: <nil>
STEP: delete the pod
Jun 10 00:19:25.679: INFO: Waiting for pod exec-volume-test-inlinevolume-8fp9 to disappear
Jun 10 00:19:25.720: INFO: Pod exec-volume-test-inlinevolume-8fp9 no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-8fp9
Jun 10 00:19:25.720: INFO: Deleting pod "exec-volume-test-inlinevolume-8fp9" in namespace "volume-5848"
Jun 10 00:19:25.912: INFO: Couldn't delete PD "aws://us-east-2a/vol-0d63a1382df72671d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d63a1382df72671d is currently attached to i-0d2e89f8b75d98870
	status code: 400, request id: 2b2b8fcc-7ca1-4016-bd7c-54df7ef69919
Jun 10 00:19:31.239: INFO: Couldn't delete PD "aws://us-east-2a/vol-0d63a1382df72671d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d63a1382df72671d is currently attached to i-0d2e89f8b75d98870
	status code: 400, request id: 7345f8c5-462a-459a-8d70-1bd5aa91ff56
Jun 10 00:19:36.611: INFO: Couldn't delete PD "aws://us-east-2a/vol-0d63a1382df72671d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d63a1382df72671d is currently attached to i-0d2e89f8b75d98870
	status code: 400, request id: f58cdca4-5514-4804-9977-b32ce2fd9046
Jun 10 00:19:41.980: INFO: Couldn't delete PD "aws://us-east-2a/vol-0d63a1382df72671d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d63a1382df72671d is currently attached to i-0d2e89f8b75d98870
	status code: 400, request id: d13de11c-90ad-4212-b0fc-0266e9f452b4
Jun 10 00:19:47.269: INFO: Couldn't delete PD "aws://us-east-2a/vol-0d63a1382df72671d", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d63a1382df72671d is currently attached to i-0d2e89f8b75d98870
	status code: 400, request id: 566b35df-b6bf-4b61-9179-48f59130c9b1
Jun 10 00:19:52.609: INFO: Successfully deleted PD "aws://us-east-2a/vol-0d63a1382df72671d".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 10 00:19:52.609: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-5848" for this suite.
... skipping 153 lines ...
Jun 10 00:19:06.558: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9789-e2e-scf8mtk
STEP: creating a claim
Jun 10 00:19:06.600: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-s729
STEP: Creating a pod to test subpath
Jun 10 00:19:06.727: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-s729" in namespace "provisioning-9789" to be "Succeeded or Failed"
Jun 10 00:19:06.768: INFO: Pod "pod-subpath-test-dynamicpv-s729": Phase="Pending", Reason="", readiness=false. Elapsed: 41.288246ms
Jun 10 00:19:08.811: INFO: Pod "pod-subpath-test-dynamicpv-s729": Phase="Pending", Reason="", readiness=false. Elapsed: 2.083634711s
Jun 10 00:19:10.854: INFO: Pod "pod-subpath-test-dynamicpv-s729": Phase="Pending", Reason="", readiness=false. Elapsed: 4.126598285s
Jun 10 00:19:12.895: INFO: Pod "pod-subpath-test-dynamicpv-s729": Phase="Pending", Reason="", readiness=false. Elapsed: 6.168257705s
Jun 10 00:19:14.937: INFO: Pod "pod-subpath-test-dynamicpv-s729": Phase="Pending", Reason="", readiness=false. Elapsed: 8.209707172s
Jun 10 00:19:16.979: INFO: Pod "pod-subpath-test-dynamicpv-s729": Phase="Pending", Reason="", readiness=false. Elapsed: 10.252086452s
Jun 10 00:19:19.022: INFO: Pod "pod-subpath-test-dynamicpv-s729": Phase="Pending", Reason="", readiness=false. Elapsed: 12.294667957s
Jun 10 00:19:21.064: INFO: Pod "pod-subpath-test-dynamicpv-s729": Phase="Pending", Reason="", readiness=false. Elapsed: 14.337174524s
Jun 10 00:19:23.109: INFO: Pod "pod-subpath-test-dynamicpv-s729": Phase="Pending", Reason="", readiness=false. Elapsed: 16.381733283s
Jun 10 00:19:25.150: INFO: Pod "pod-subpath-test-dynamicpv-s729": Phase="Pending", Reason="", readiness=false. Elapsed: 18.423108193s
Jun 10 00:19:27.193: INFO: Pod "pod-subpath-test-dynamicpv-s729": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.465709399s
STEP: Saw pod success
Jun 10 00:19:27.193: INFO: Pod "pod-subpath-test-dynamicpv-s729" satisfied condition "Succeeded or Failed"
Jun 10 00:19:27.234: INFO: Trying to get logs from node ip-172-20-53-235.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-s729 container test-container-subpath-dynamicpv-s729: <nil>
STEP: delete the pod
Jun 10 00:19:27.598: INFO: Waiting for pod pod-subpath-test-dynamicpv-s729 to disappear
Jun 10 00:19:27.639: INFO: Pod pod-subpath-test-dynamicpv-s729 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-s729
Jun 10 00:19:27.639: INFO: Deleting pod "pod-subpath-test-dynamicpv-s729" in namespace "provisioning-9789"
... skipping 42 lines ...
Jun 10 00:19:05.405: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-466cbzz7
STEP: creating a claim
Jun 10 00:19:05.448: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-nwgr
STEP: Creating a pod to test subpath
Jun 10 00:19:05.581: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-nwgr" in namespace "provisioning-466" to be "Succeeded or Failed"
Jun 10 00:19:05.623: INFO: Pod "pod-subpath-test-dynamicpv-nwgr": Phase="Pending", Reason="", readiness=false. Elapsed: 42.254832ms
Jun 10 00:19:07.666: INFO: Pod "pod-subpath-test-dynamicpv-nwgr": Phase="Pending", Reason="", readiness=false. Elapsed: 2.085351771s
Jun 10 00:19:09.709: INFO: Pod "pod-subpath-test-dynamicpv-nwgr": Phase="Pending", Reason="", readiness=false. Elapsed: 4.127792145s
Jun 10 00:19:11.786: INFO: Pod "pod-subpath-test-dynamicpv-nwgr": Phase="Pending", Reason="", readiness=false. Elapsed: 6.205414752s
Jun 10 00:19:13.829: INFO: Pod "pod-subpath-test-dynamicpv-nwgr": Phase="Pending", Reason="", readiness=false. Elapsed: 8.248351036s
Jun 10 00:19:15.872: INFO: Pod "pod-subpath-test-dynamicpv-nwgr": Phase="Pending", Reason="", readiness=false. Elapsed: 10.290512546s
... skipping 4 lines ...
Jun 10 00:19:26.085: INFO: Pod "pod-subpath-test-dynamicpv-nwgr": Phase="Pending", Reason="", readiness=false. Elapsed: 20.503838929s
Jun 10 00:19:28.128: INFO: Pod "pod-subpath-test-dynamicpv-nwgr": Phase="Pending", Reason="", readiness=false. Elapsed: 22.546845179s
Jun 10 00:19:30.170: INFO: Pod "pod-subpath-test-dynamicpv-nwgr": Phase="Pending", Reason="", readiness=false. Elapsed: 24.589100939s
Jun 10 00:19:32.212: INFO: Pod "pod-subpath-test-dynamicpv-nwgr": Phase="Pending", Reason="", readiness=false. Elapsed: 26.63117474s
Jun 10 00:19:34.255: INFO: Pod "pod-subpath-test-dynamicpv-nwgr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 28.674009122s
STEP: Saw pod success
Jun 10 00:19:34.255: INFO: Pod "pod-subpath-test-dynamicpv-nwgr" satisfied condition "Succeeded or Failed"
Jun 10 00:19:34.297: INFO: Trying to get logs from node ip-172-20-40-185.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-nwgr container test-container-volume-dynamicpv-nwgr: <nil>
STEP: delete the pod
Jun 10 00:19:34.893: INFO: Waiting for pod pod-subpath-test-dynamicpv-nwgr to disappear
Jun 10 00:19:34.935: INFO: Pod pod-subpath-test-dynamicpv-nwgr no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-nwgr
Jun 10 00:19:34.935: INFO: Deleting pod "pod-subpath-test-dynamicpv-nwgr" in namespace "provisioning-466"
... skipping 246 lines ...
Jun 10 00:19:05.059: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-7643-e2e-scqvph2
STEP: creating a claim
Jun 10 00:19:05.101: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-5h7r
STEP: Creating a pod to test exec-volume-test
Jun 10 00:19:05.226: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-5h7r" in namespace "volume-7643" to be "Succeeded or Failed"
Jun 10 00:19:05.267: INFO: Pod "exec-volume-test-dynamicpv-5h7r": Phase="Pending", Reason="", readiness=false. Elapsed: 40.782762ms
Jun 10 00:19:07.309: INFO: Pod "exec-volume-test-dynamicpv-5h7r": Phase="Pending", Reason="", readiness=false. Elapsed: 2.082746451s
Jun 10 00:19:09.351: INFO: Pod "exec-volume-test-dynamicpv-5h7r": Phase="Pending", Reason="", readiness=false. Elapsed: 4.124527999s
Jun 10 00:19:11.393: INFO: Pod "exec-volume-test-dynamicpv-5h7r": Phase="Pending", Reason="", readiness=false. Elapsed: 6.166324585s
Jun 10 00:19:13.435: INFO: Pod "exec-volume-test-dynamicpv-5h7r": Phase="Pending", Reason="", readiness=false. Elapsed: 8.20859886s
Jun 10 00:19:15.476: INFO: Pod "exec-volume-test-dynamicpv-5h7r": Phase="Pending", Reason="", readiness=false. Elapsed: 10.249846767s
... skipping 5 lines ...
Jun 10 00:19:27.731: INFO: Pod "exec-volume-test-dynamicpv-5h7r": Phase="Pending", Reason="", readiness=false. Elapsed: 22.505068927s
Jun 10 00:19:29.775: INFO: Pod "exec-volume-test-dynamicpv-5h7r": Phase="Pending", Reason="", readiness=false. Elapsed: 24.54832269s
Jun 10 00:19:31.823: INFO: Pod "exec-volume-test-dynamicpv-5h7r": Phase="Pending", Reason="", readiness=false. Elapsed: 26.596447625s
Jun 10 00:19:33.864: INFO: Pod "exec-volume-test-dynamicpv-5h7r": Phase="Pending", Reason="", readiness=false. Elapsed: 28.637915386s
Jun 10 00:19:35.907: INFO: Pod "exec-volume-test-dynamicpv-5h7r": Phase="Succeeded", Reason="", readiness=false. Elapsed: 30.681025011s
STEP: Saw pod success
Jun 10 00:19:35.907: INFO: Pod "exec-volume-test-dynamicpv-5h7r" satisfied condition "Succeeded or Failed"
Jun 10 00:19:35.948: INFO: Trying to get logs from node ip-172-20-53-235.us-east-2.compute.internal pod exec-volume-test-dynamicpv-5h7r container exec-container-dynamicpv-5h7r: <nil>
STEP: delete the pod
Jun 10 00:19:36.038: INFO: Waiting for pod exec-volume-test-dynamicpv-5h7r to disappear
Jun 10 00:19:36.080: INFO: Pod exec-volume-test-dynamicpv-5h7r no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-5h7r
Jun 10 00:19:36.080: INFO: Deleting pod "exec-volume-test-dynamicpv-5h7r" in namespace "volume-7643"
... skipping 173 lines ...
Jun 10 00:19:05.803: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5334-e2e-sc8rdqq
STEP: creating a claim
Jun 10 00:19:05.845: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-dv76
STEP: Creating a pod to test subpath
Jun 10 00:19:05.972: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-dv76" in namespace "provisioning-5334" to be "Succeeded or Failed"
Jun 10 00:19:06.014: INFO: Pod "pod-subpath-test-dynamicpv-dv76": Phase="Pending", Reason="", readiness=false. Elapsed: 41.378905ms
Jun 10 00:19:08.056: INFO: Pod "pod-subpath-test-dynamicpv-dv76": Phase="Pending", Reason="", readiness=false. Elapsed: 2.083805116s
Jun 10 00:19:10.113: INFO: Pod "pod-subpath-test-dynamicpv-dv76": Phase="Pending", Reason="", readiness=false. Elapsed: 4.140545819s
Jun 10 00:19:12.157: INFO: Pod "pod-subpath-test-dynamicpv-dv76": Phase="Pending", Reason="", readiness=false. Elapsed: 6.184465748s
Jun 10 00:19:14.199: INFO: Pod "pod-subpath-test-dynamicpv-dv76": Phase="Pending", Reason="", readiness=false. Elapsed: 8.225980855s
Jun 10 00:19:16.240: INFO: Pod "pod-subpath-test-dynamicpv-dv76": Phase="Pending", Reason="", readiness=false. Elapsed: 10.267605699s
... skipping 6 lines ...
Jun 10 00:19:30.534: INFO: Pod "pod-subpath-test-dynamicpv-dv76": Phase="Pending", Reason="", readiness=false. Elapsed: 24.561713421s
Jun 10 00:19:32.576: INFO: Pod "pod-subpath-test-dynamicpv-dv76": Phase="Pending", Reason="", readiness=false. Elapsed: 26.603073488s
Jun 10 00:19:34.618: INFO: Pod "pod-subpath-test-dynamicpv-dv76": Phase="Pending", Reason="", readiness=false. Elapsed: 28.645347683s
Jun 10 00:19:36.659: INFO: Pod "pod-subpath-test-dynamicpv-dv76": Phase="Pending", Reason="", readiness=false. Elapsed: 30.686580722s
Jun 10 00:19:38.701: INFO: Pod "pod-subpath-test-dynamicpv-dv76": Phase="Succeeded", Reason="", readiness=false. Elapsed: 32.72835931s
STEP: Saw pod success
Jun 10 00:19:38.701: INFO: Pod "pod-subpath-test-dynamicpv-dv76" satisfied condition "Succeeded or Failed"
Jun 10 00:19:38.745: INFO: Trying to get logs from node ip-172-20-37-21.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-dv76 container test-container-volume-dynamicpv-dv76: <nil>
STEP: delete the pod
Jun 10 00:19:38.843: INFO: Waiting for pod pod-subpath-test-dynamicpv-dv76 to disappear
Jun 10 00:19:38.884: INFO: Pod pod-subpath-test-dynamicpv-dv76 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-dv76
Jun 10 00:19:38.884: INFO: Deleting pod "pod-subpath-test-dynamicpv-dv76" in namespace "provisioning-5334"
... skipping 169 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.Ze8yNfZ8r/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.Ze8yNfZ8r/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.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 192 lines ...
Jun 10 00:19:06.162: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-4621-e2e-scgncq2      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-4621    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-4621-e2e-scgncq2,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-4621    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-4621-e2e-scgncq2,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-4621    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-4621-e2e-scgncq2,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-4621-e2e-scgncq2    4a1444ef-49ab-4896-80cd-a1f32ef57e05 2442 0 2021-06-10 00:19:06 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-10 00:19: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-k4cc7 pvc- provisioning-4621  3a50cf73-ee25-4964-8f92-629212e71897 2447 0 2021-06-10 00:19:06 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-10 00:19: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-4621-e2e-scgncq2,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-0bb8ae48-dede-4dd1-9c98-b5fec0f22410 in namespace provisioning-4621
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun 10 00:19:28.637: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-2wg5v" in namespace "provisioning-4621" to be "Succeeded or Failed"
Jun 10 00:19:28.679: INFO: Pod "pvc-volume-tester-writer-2wg5v": Phase="Pending", Reason="", readiness=false. Elapsed: 41.62876ms
Jun 10 00:19:30.723: INFO: Pod "pvc-volume-tester-writer-2wg5v": Phase="Pending", Reason="", readiness=false. Elapsed: 2.08567288s
Jun 10 00:19:32.765: INFO: Pod "pvc-volume-tester-writer-2wg5v": Phase="Pending", Reason="", readiness=false. Elapsed: 4.127930819s
Jun 10 00:19:34.809: INFO: Pod "pvc-volume-tester-writer-2wg5v": Phase="Pending", Reason="", readiness=false. Elapsed: 6.171015333s
Jun 10 00:19:36.852: INFO: Pod "pvc-volume-tester-writer-2wg5v": Phase="Pending", Reason="", readiness=false. Elapsed: 8.214297055s
Jun 10 00:19:38.895: INFO: Pod "pvc-volume-tester-writer-2wg5v": Phase="Pending", Reason="", readiness=false. Elapsed: 10.257466366s
... skipping 7 lines ...
Jun 10 00:19:55.236: INFO: Pod "pvc-volume-tester-writer-2wg5v": Phase="Pending", Reason="", readiness=false. Elapsed: 26.598487549s
Jun 10 00:19:57.279: INFO: Pod "pvc-volume-tester-writer-2wg5v": Phase="Pending", Reason="", readiness=false. Elapsed: 28.641743297s
Jun 10 00:19:59.322: INFO: Pod "pvc-volume-tester-writer-2wg5v": Phase="Pending", Reason="", readiness=false. Elapsed: 30.684909134s
Jun 10 00:20:01.365: INFO: Pod "pvc-volume-tester-writer-2wg5v": Phase="Pending", Reason="", readiness=false. Elapsed: 32.727110106s
Jun 10 00:20:03.407: INFO: Pod "pvc-volume-tester-writer-2wg5v": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.769626025s
STEP: Saw pod success
Jun 10 00:20:03.407: INFO: Pod "pvc-volume-tester-writer-2wg5v" satisfied condition "Succeeded or Failed"
Jun 10 00:20:03.493: INFO: Pod pvc-volume-tester-writer-2wg5v has the following logs: 
Jun 10 00:20:03.493: INFO: Deleting pod "pvc-volume-tester-writer-2wg5v" in namespace "provisioning-4621"
Jun 10 00:20:03.542: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-2wg5v" to be fully deleted
STEP: checking the created volume has the correct mount options, is readable and retains data on the same node "ip-172-20-37-21.us-east-2.compute.internal"
Jun 10 00:20:03.717: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-mbxvd" in namespace "provisioning-4621" to be "Succeeded or Failed"
Jun 10 00:20:03.759: INFO: Pod "pvc-volume-tester-reader-mbxvd": Phase="Pending", Reason="", readiness=false. Elapsed: 42.179093ms
Jun 10 00:20:05.804: INFO: Pod "pvc-volume-tester-reader-mbxvd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.087172371s
STEP: Saw pod success
Jun 10 00:20:05.804: INFO: Pod "pvc-volume-tester-reader-mbxvd" satisfied condition "Succeeded or Failed"
Jun 10 00:20:05.891: INFO: Pod pvc-volume-tester-reader-mbxvd has the following logs: hello world

Jun 10 00:20:05.891: INFO: Deleting pod "pvc-volume-tester-reader-mbxvd" in namespace "provisioning-4621"
Jun 10 00:20:05.939: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-mbxvd" to be fully deleted
Jun 10 00:20:05.983: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-k4cc7] to have phase Bound
Jun 10 00:20:06.025: INFO: PersistentVolumeClaim pvc-k4cc7 found and phase=Bound (41.530589ms)
... skipping 32 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.Ze8yNfZ8r/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.Ze8yNfZ8r/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.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 178 lines ...
Jun 10 00:20:27.244: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 40 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 00:19:59.607: 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.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 10 00:19:59.819: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 10 00:20:00.350: INFO: Successfully created a new PD: "aws://us-east-2a/vol-031608517450aa3dc".
Jun 10 00:20:00.350: INFO: Creating resource for pre-provisioned PV
Jun 10 00:20:00.350: INFO: Creating PVC and PV
... skipping 8 lines ...
Jun 10 00:20:10.776: INFO: PersistentVolumeClaim pvc-s7fqh found but phase is Pending instead of Bound.
Jun 10 00:20:12.819: INFO: PersistentVolumeClaim pvc-s7fqh found but phase is Pending instead of Bound.
Jun 10 00:20:14.861: INFO: PersistentVolumeClaim pvc-s7fqh found and phase=Bound (14.340865723s)
Jun 10 00:20:14.861: INFO: Waiting up to 3m0s for PersistentVolume aws-lpvsx to have phase Bound
Jun 10 00:20:14.903: INFO: PersistentVolume aws-lpvsx found and phase=Bound (41.650754ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 10 00:20:17.158: INFO: Deleting pod "pod-5c4a025f-f298-4965-9a0b-6be3ae74614e" in namespace "volumemode-7953"
Jun 10 00:20:17.201: INFO: Wait up to 5m0s for pod "pod-5c4a025f-f298-4965-9a0b-6be3ae74614e" to be fully deleted
STEP: Deleting pv and pvc
Jun 10 00:20:23.286: INFO: Deleting PersistentVolumeClaim "pvc-s7fqh"
Jun 10 00:20:23.330: INFO: Deleting PersistentVolume "aws-lpvsx"
Jun 10 00:20:23.512: INFO: Couldn't delete PD "aws://us-east-2a/vol-031608517450aa3dc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-031608517450aa3dc is currently attached to i-0a2e25b9d9c987751
	status code: 400, request id: 65d315b6-a032-40fb-bbdc-ca1bb38c1f33
Jun 10 00:20:28.833: INFO: Successfully deleted PD "aws://us-east-2a/vol-031608517450aa3dc".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 10 00:20:28.833: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-7953" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Ze8yNfZ8r/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Ze8yNfZ8r/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
    /tmp/kops.Ze8yNfZ8r/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.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [sig-storage] vsphere cloud provider stress [Feature:vsphere]
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 00:20:28.921: INFO: >>> kubeConfig: /root/.kube/config
... skipping 265 lines ...
Jun 10 00:19:30.241: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9217-e2e-sc5hbgv
STEP: creating a claim
Jun 10 00:19:30.284: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-hk5l
STEP: Creating a pod to test atomic-volume-subpath
Jun 10 00:19:30.411: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-hk5l" in namespace "provisioning-9217" to be "Succeeded or Failed"
Jun 10 00:19:30.453: INFO: Pod "pod-subpath-test-dynamicpv-hk5l": Phase="Pending", Reason="", readiness=false. Elapsed: 41.288583ms
Jun 10 00:19:32.495: INFO: Pod "pod-subpath-test-dynamicpv-hk5l": Phase="Pending", Reason="", readiness=false. Elapsed: 2.083600833s
Jun 10 00:19:34.537: INFO: Pod "pod-subpath-test-dynamicpv-hk5l": Phase="Pending", Reason="", readiness=false. Elapsed: 4.125969109s
Jun 10 00:19:36.581: INFO: Pod "pod-subpath-test-dynamicpv-hk5l": Phase="Pending", Reason="", readiness=false. Elapsed: 6.16988642s
Jun 10 00:19:38.623: INFO: Pod "pod-subpath-test-dynamicpv-hk5l": Phase="Pending", Reason="", readiness=false. Elapsed: 8.211760059s
Jun 10 00:19:40.665: INFO: Pod "pod-subpath-test-dynamicpv-hk5l": Phase="Pending", Reason="", readiness=false. Elapsed: 10.25338223s
... skipping 14 lines ...
Jun 10 00:20:11.314: INFO: Pod "pod-subpath-test-dynamicpv-hk5l": Phase="Running", Reason="", readiness=true. Elapsed: 40.902585806s
Jun 10 00:20:13.357: INFO: Pod "pod-subpath-test-dynamicpv-hk5l": Phase="Running", Reason="", readiness=true. Elapsed: 42.945112005s
Jun 10 00:20:15.399: INFO: Pod "pod-subpath-test-dynamicpv-hk5l": Phase="Running", Reason="", readiness=true. Elapsed: 44.987175918s
Jun 10 00:20:17.440: INFO: Pod "pod-subpath-test-dynamicpv-hk5l": Phase="Running", Reason="", readiness=true. Elapsed: 47.028510737s
Jun 10 00:20:19.481: INFO: Pod "pod-subpath-test-dynamicpv-hk5l": Phase="Succeeded", Reason="", readiness=false. Elapsed: 49.069867663s
STEP: Saw pod success
Jun 10 00:20:19.481: INFO: Pod "pod-subpath-test-dynamicpv-hk5l" satisfied condition "Succeeded or Failed"
Jun 10 00:20:19.523: INFO: Trying to get logs from node ip-172-20-56-177.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-hk5l container test-container-subpath-dynamicpv-hk5l: <nil>
STEP: delete the pod
Jun 10 00:20:19.614: INFO: Waiting for pod pod-subpath-test-dynamicpv-hk5l to disappear
Jun 10 00:20:19.663: INFO: Pod pod-subpath-test-dynamicpv-hk5l no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-hk5l
Jun 10 00:20:19.663: INFO: Deleting pod "pod-subpath-test-dynamicpv-hk5l" in namespace "provisioning-9217"
... skipping 460 lines ...
STEP: Deleting pod hostexec-ip-172-20-53-235.us-east-2.compute.internal-5x4fg in namespace volumemode-3477
Jun 10 00:20:35.139: INFO: Deleting pod "pod-3c19e120-89c2-4e69-bb1d-cbeaed4a92f4" in namespace "volumemode-3477"
Jun 10 00:20:35.182: INFO: Wait up to 5m0s for pod "pod-3c19e120-89c2-4e69-bb1d-cbeaed4a92f4" to be fully deleted
STEP: Deleting pv and pvc
Jun 10 00:20:47.278: INFO: Deleting PersistentVolumeClaim "pvc-98hvv"
Jun 10 00:20:47.320: INFO: Deleting PersistentVolume "aws-92fgc"
Jun 10 00:20:47.553: INFO: Couldn't delete PD "aws://us-east-2a/vol-0a98ff554010f1871", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a98ff554010f1871 is currently attached to i-0c35a223bdb203427
	status code: 400, request id: e8917978-4ac9-4bdd-a392-5a717a23553e
Jun 10 00:20:52.907: INFO: Couldn't delete PD "aws://us-east-2a/vol-0a98ff554010f1871", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a98ff554010f1871 is currently attached to i-0c35a223bdb203427
	status code: 400, request id: 731d6fae-50ca-438f-87d5-188338321a15
Jun 10 00:20:58.229: INFO: Successfully deleted PD "aws://us-east-2a/vol-0a98ff554010f1871".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 10 00:20:58.229: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-3477" for this suite.
... skipping 183 lines ...
Jun 10 00:19:06.256: INFO: Creating resource for dynamic PV
Jun 10 00:19:06.256: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-3505-e2e-sc7clwz
STEP: creating a claim
Jun 10 00:19:06.302: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 10 00:19:06.442: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-22cpg" in namespace "snapshotting-3505" to be "Succeeded or Failed"
Jun 10 00:19:06.484: INFO: Pod "pvc-snapshottable-tester-22cpg": Phase="Pending", Reason="", readiness=false. Elapsed: 42.118448ms
Jun 10 00:19:08.529: INFO: Pod "pvc-snapshottable-tester-22cpg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.086788463s
Jun 10 00:19:10.572: INFO: Pod "pvc-snapshottable-tester-22cpg": Phase="Pending", Reason="", readiness=false. Elapsed: 4.130109068s
Jun 10 00:19:12.614: INFO: Pod "pvc-snapshottable-tester-22cpg": Phase="Pending", Reason="", readiness=false. Elapsed: 6.172530155s
Jun 10 00:19:14.657: INFO: Pod "pvc-snapshottable-tester-22cpg": Phase="Pending", Reason="", readiness=false. Elapsed: 8.21523898s
Jun 10 00:19:16.701: INFO: Pod "pvc-snapshottable-tester-22cpg": Phase="Pending", Reason="", readiness=false. Elapsed: 10.258922424s
Jun 10 00:19:18.744: INFO: Pod "pvc-snapshottable-tester-22cpg": Phase="Pending", Reason="", readiness=false. Elapsed: 12.302369208s
Jun 10 00:19:20.797: INFO: Pod "pvc-snapshottable-tester-22cpg": Phase="Pending", Reason="", readiness=false. Elapsed: 14.355014191s
Jun 10 00:19:22.840: INFO: Pod "pvc-snapshottable-tester-22cpg": Phase="Pending", Reason="", readiness=false. Elapsed: 16.397857877s
Jun 10 00:19:24.883: INFO: Pod "pvc-snapshottable-tester-22cpg": Phase="Pending", Reason="", readiness=false. Elapsed: 18.441342188s
Jun 10 00:19:26.926: INFO: Pod "pvc-snapshottable-tester-22cpg": Phase="Pending", Reason="", readiness=false. Elapsed: 20.484381621s
Jun 10 00:19:28.971: INFO: Pod "pvc-snapshottable-tester-22cpg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.528915185s
STEP: Saw pod success
Jun 10 00:19:28.971: INFO: Pod "pvc-snapshottable-tester-22cpg" satisfied condition "Succeeded or Failed"
Jun 10 00:19:29.068: INFO: Pod pvc-snapshottable-tester-22cpg has the following logs: 
Jun 10 00:19:29.068: INFO: Deleting pod "pvc-snapshottable-tester-22cpg" in namespace "snapshotting-3505"
Jun 10 00:19:29.124: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-22cpg" to be fully deleted
Jun 10 00:19:29.166: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comm5zzz] to have phase Bound
Jun 10 00:19:29.208: INFO: PersistentVolumeClaim ebs.csi.aws.comm5zzz found and phase=Bound (42.248021ms)
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.Ze8yNfZ8r/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 10 00:20:00.803: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-thscg" in namespace "snapshotting-3505" to be "Succeeded or Failed"
Jun 10 00:20:00.845: INFO: Pod "pvc-snapshottable-data-tester-thscg": Phase="Pending", Reason="", readiness=false. Elapsed: 41.912388ms
Jun 10 00:20:02.889: INFO: Pod "pvc-snapshottable-data-tester-thscg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.085823365s
Jun 10 00:20:04.932: INFO: Pod "pvc-snapshottable-data-tester-thscg": Phase="Pending", Reason="", readiness=false. Elapsed: 4.128548795s
Jun 10 00:20:06.975: INFO: Pod "pvc-snapshottable-data-tester-thscg": Phase="Pending", Reason="", readiness=false. Elapsed: 6.171365237s
Jun 10 00:20:09.018: INFO: Pod "pvc-snapshottable-data-tester-thscg": Phase="Pending", Reason="", readiness=false. Elapsed: 8.214284346s
Jun 10 00:20:11.061: INFO: Pod "pvc-snapshottable-data-tester-thscg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.257550866s
STEP: Saw pod success
Jun 10 00:20:11.061: INFO: Pod "pvc-snapshottable-data-tester-thscg" satisfied condition "Succeeded or Failed"
Jun 10 00:20:11.147: INFO: Pod pvc-snapshottable-data-tester-thscg has the following logs: 
Jun 10 00:20:11.147: INFO: Deleting pod "pvc-snapshottable-data-tester-thscg" in namespace "snapshotting-3505"
Jun 10 00:20:11.199: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-thscg" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 10 00:20:21.426: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-3505 exec restored-pvc-tester-slz8t --namespace=snapshotting-3505 -- cat /mnt/test/data'
... skipping 153 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Ze8yNfZ8r/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Ze8yNfZ8r/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.Ze8yNfZ8r/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.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Distro debian doesn't support ntfs -- skipping

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

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

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

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.Ze8yNfZ8r/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.Ze8yNfZ8r/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.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 136 lines ...
Jun 10 00:21:18.905: INFO: Pod aws-client still exists
Jun 10 00:21:20.863: INFO: Waiting for pod aws-client to disappear
Jun 10 00:21:20.904: INFO: Pod aws-client still exists
Jun 10 00:21:22.863: INFO: Waiting for pod aws-client to disappear
Jun 10 00:21:22.904: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun 10 00:21:23.248: INFO: Couldn't delete PD "aws://us-east-2a/vol-0594ceb7e08d698e4", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0594ceb7e08d698e4 is currently attached to i-0a2e25b9d9c987751
	status code: 400, request id: ea6487f6-b913-490f-abee-630f83d18655
Jun 10 00:21:28.580: INFO: Successfully deleted PD "aws://us-east-2a/vol-0594ceb7e08d698e4".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 10 00:21:28.580: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-2854" for this suite.
... skipping 23 lines ...
Jun 10 00:20:58.013: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6432-e2e-sc4jfcr
STEP: creating a claim
Jun 10 00:20:58.056: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-g8n2
STEP: Creating a pod to test subpath
Jun 10 00:20:58.186: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-g8n2" in namespace "provisioning-6432" to be "Succeeded or Failed"
Jun 10 00:20:58.228: INFO: Pod "pod-subpath-test-dynamicpv-g8n2": Phase="Pending", Reason="", readiness=false. Elapsed: 42.454242ms
Jun 10 00:21:00.273: INFO: Pod "pod-subpath-test-dynamicpv-g8n2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.086667775s
Jun 10 00:21:02.316: INFO: Pod "pod-subpath-test-dynamicpv-g8n2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.129773598s
Jun 10 00:21:04.358: INFO: Pod "pod-subpath-test-dynamicpv-g8n2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.172471554s
Jun 10 00:21:06.402: INFO: Pod "pod-subpath-test-dynamicpv-g8n2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.215833851s
Jun 10 00:21:08.460: INFO: Pod "pod-subpath-test-dynamicpv-g8n2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.273913383s
Jun 10 00:21:10.505: INFO: Pod "pod-subpath-test-dynamicpv-g8n2": Phase="Pending", Reason="", readiness=false. Elapsed: 12.319453033s
Jun 10 00:21:12.549: INFO: Pod "pod-subpath-test-dynamicpv-g8n2": Phase="Pending", Reason="", readiness=false. Elapsed: 14.363148539s
Jun 10 00:21:14.592: INFO: Pod "pod-subpath-test-dynamicpv-g8n2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.405965154s
STEP: Saw pod success
Jun 10 00:21:14.592: INFO: Pod "pod-subpath-test-dynamicpv-g8n2" satisfied condition "Succeeded or Failed"
Jun 10 00:21:14.635: INFO: Trying to get logs from node ip-172-20-37-21.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-g8n2 container test-container-subpath-dynamicpv-g8n2: <nil>
STEP: delete the pod
Jun 10 00:21:14.729: INFO: Waiting for pod pod-subpath-test-dynamicpv-g8n2 to disappear
Jun 10 00:21:14.771: INFO: Pod pod-subpath-test-dynamicpv-g8n2 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-g8n2
Jun 10 00:21:14.771: INFO: Deleting pod "pod-subpath-test-dynamicpv-g8n2" in namespace "provisioning-6432"
... skipping 238 lines ...

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

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

    /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:92
------------------------------
... skipping 186 lines ...
Jun 10 00:21:11.255: INFO: PersistentVolumeClaim pvc-j9q8r found but phase is Pending instead of Bound.
Jun 10 00:21:13.297: INFO: PersistentVolumeClaim pvc-j9q8r found and phase=Bound (14.335849999s)
Jun 10 00:21:13.297: INFO: Waiting up to 3m0s for PersistentVolume aws-kqfl6 to have phase Bound
Jun 10 00:21:13.338: INFO: PersistentVolume aws-kqfl6 found and phase=Bound (41.399043ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-g2lp
STEP: Creating a pod to test exec-volume-test
Jun 10 00:21:13.464: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-g2lp" in namespace "volume-7103" to be "Succeeded or Failed"
Jun 10 00:21:13.507: INFO: Pod "exec-volume-test-preprovisionedpv-g2lp": Phase="Pending", Reason="", readiness=false. Elapsed: 43.155934ms
Jun 10 00:21:15.549: INFO: Pod "exec-volume-test-preprovisionedpv-g2lp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.085257849s
Jun 10 00:21:17.592: INFO: Pod "exec-volume-test-preprovisionedpv-g2lp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.128291196s
Jun 10 00:21:19.637: INFO: Pod "exec-volume-test-preprovisionedpv-g2lp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.172676953s
Jun 10 00:21:21.680: INFO: Pod "exec-volume-test-preprovisionedpv-g2lp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.215644458s
Jun 10 00:21:23.722: INFO: Pod "exec-volume-test-preprovisionedpv-g2lp": Phase="Pending", Reason="", readiness=false. Elapsed: 10.257536487s
Jun 10 00:21:25.764: INFO: Pod "exec-volume-test-preprovisionedpv-g2lp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.299621138s
STEP: Saw pod success
Jun 10 00:21:25.764: INFO: Pod "exec-volume-test-preprovisionedpv-g2lp" satisfied condition "Succeeded or Failed"
Jun 10 00:21:25.810: INFO: Trying to get logs from node ip-172-20-37-21.us-east-2.compute.internal pod exec-volume-test-preprovisionedpv-g2lp container exec-container-preprovisionedpv-g2lp: <nil>
STEP: delete the pod
Jun 10 00:21:25.913: INFO: Waiting for pod exec-volume-test-preprovisionedpv-g2lp to disappear
Jun 10 00:21:25.956: INFO: Pod exec-volume-test-preprovisionedpv-g2lp no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-g2lp
Jun 10 00:21:25.956: INFO: Deleting pod "exec-volume-test-preprovisionedpv-g2lp" in namespace "volume-7103"
STEP: Deleting pv and pvc
Jun 10 00:21:25.997: INFO: Deleting PersistentVolumeClaim "pvc-j9q8r"
Jun 10 00:21:26.041: INFO: Deleting PersistentVolume "aws-kqfl6"
Jun 10 00:21:26.218: INFO: Couldn't delete PD "aws://us-east-2a/vol-08118d2cccaf7007e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08118d2cccaf7007e is currently attached to i-06f8a1a98a822b359
	status code: 400, request id: af9ea419-cc65-4ddc-85f0-ebb322e06681
Jun 10 00:21:31.574: INFO: Couldn't delete PD "aws://us-east-2a/vol-08118d2cccaf7007e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08118d2cccaf7007e is currently attached to i-06f8a1a98a822b359
	status code: 400, request id: 787c5e4c-fc27-4cc2-ac27-07ba3761950c
Jun 10 00:21:36.874: INFO: Couldn't delete PD "aws://us-east-2a/vol-08118d2cccaf7007e", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-08118d2cccaf7007e is currently attached to i-06f8a1a98a822b359
	status code: 400, request id: de831e50-15d8-47a2-acca-03fe23a68f19
Jun 10 00:21:42.202: INFO: Successfully deleted PD "aws://us-east-2a/vol-08118d2cccaf7007e".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 10 00:21:42.202: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-7103" for this suite.
... skipping 99 lines ...
Jun 10 00:21:11.437: INFO: PersistentVolumeClaim pvc-k8qtt found but phase is Pending instead of Bound.
Jun 10 00:21:13.483: INFO: PersistentVolumeClaim pvc-k8qtt found and phase=Bound (8.21515236s)
Jun 10 00:21:13.483: INFO: Waiting up to 3m0s for PersistentVolume aws-h5fvz to have phase Bound
Jun 10 00:21:13.525: INFO: PersistentVolume aws-h5fvz found and phase=Bound (42.10435ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-qrbn
STEP: Creating a pod to test exec-volume-test
Jun 10 00:21:13.654: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-qrbn" in namespace "volume-1875" to be "Succeeded or Failed"
Jun 10 00:21:13.697: INFO: Pod "exec-volume-test-preprovisionedpv-qrbn": Phase="Pending", Reason="", readiness=false. Elapsed: 42.088069ms
Jun 10 00:21:15.740: INFO: Pod "exec-volume-test-preprovisionedpv-qrbn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.085137082s
Jun 10 00:21:17.782: INFO: Pod "exec-volume-test-preprovisionedpv-qrbn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.127879273s
Jun 10 00:21:19.825: INFO: Pod "exec-volume-test-preprovisionedpv-qrbn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.170667793s
Jun 10 00:21:21.868: INFO: Pod "exec-volume-test-preprovisionedpv-qrbn": Phase="Pending", Reason="", readiness=false. Elapsed: 8.213810071s
Jun 10 00:21:23.912: INFO: Pod "exec-volume-test-preprovisionedpv-qrbn": Phase="Pending", Reason="", readiness=false. Elapsed: 10.257473248s
Jun 10 00:21:25.956: INFO: Pod "exec-volume-test-preprovisionedpv-qrbn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.301110784s
STEP: Saw pod success
Jun 10 00:21:25.956: INFO: Pod "exec-volume-test-preprovisionedpv-qrbn" satisfied condition "Succeeded or Failed"
Jun 10 00:21:25.998: INFO: Trying to get logs from node ip-172-20-37-21.us-east-2.compute.internal pod exec-volume-test-preprovisionedpv-qrbn container exec-container-preprovisionedpv-qrbn: <nil>
STEP: delete the pod
Jun 10 00:21:26.096: INFO: Waiting for pod exec-volume-test-preprovisionedpv-qrbn to disappear
Jun 10 00:21:26.138: INFO: Pod exec-volume-test-preprovisionedpv-qrbn no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-qrbn
Jun 10 00:21:26.138: INFO: Deleting pod "exec-volume-test-preprovisionedpv-qrbn" in namespace "volume-1875"
STEP: Deleting pv and pvc
Jun 10 00:21:26.180: INFO: Deleting PersistentVolumeClaim "pvc-k8qtt"
Jun 10 00:21:26.224: INFO: Deleting PersistentVolume "aws-h5fvz"
Jun 10 00:21:26.429: INFO: Couldn't delete PD "aws://us-east-2a/vol-04e10a14713e2ab13", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04e10a14713e2ab13 is currently attached to i-06f8a1a98a822b359
	status code: 400, request id: 0e698c28-6d93-44a4-99be-e29462699081
Jun 10 00:21:31.736: INFO: Couldn't delete PD "aws://us-east-2a/vol-04e10a14713e2ab13", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04e10a14713e2ab13 is currently attached to i-06f8a1a98a822b359
	status code: 400, request id: c3af03ef-1554-4700-8990-5264305aaecd
Jun 10 00:21:37.059: INFO: Couldn't delete PD "aws://us-east-2a/vol-04e10a14713e2ab13", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04e10a14713e2ab13 is currently attached to i-06f8a1a98a822b359
	status code: 400, request id: 402150d3-fcb5-4ae0-839e-70a6e8e4f6b6
Jun 10 00:21:42.386: INFO: Couldn't delete PD "aws://us-east-2a/vol-04e10a14713e2ab13", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-04e10a14713e2ab13 is currently attached to i-06f8a1a98a822b359
	status code: 400, request id: 1e1f5ad3-4e48-45b9-8dd8-1dd7d09eab04
Jun 10 00:21:47.711: INFO: Successfully deleted PD "aws://us-east-2a/vol-04e10a14713e2ab13".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 10 00:21:47.711: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-1875" for this suite.
... skipping 215 lines ...

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

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

    /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 37 lines ...
Jun 10 00:20:47.454: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-906pfkpt
STEP: creating a claim
Jun 10 00:20:47.499: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-qkxq
STEP: Creating a pod to test atomic-volume-subpath
Jun 10 00:20:47.631: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-qkxq" in namespace "provisioning-906" to be "Succeeded or Failed"
Jun 10 00:20:47.674: INFO: Pod "pod-subpath-test-dynamicpv-qkxq": Phase="Pending", Reason="", readiness=false. Elapsed: 42.936025ms
Jun 10 00:20:49.717: INFO: Pod "pod-subpath-test-dynamicpv-qkxq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.08659495s
Jun 10 00:20:51.761: INFO: Pod "pod-subpath-test-dynamicpv-qkxq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.129956661s
Jun 10 00:20:53.805: INFO: Pod "pod-subpath-test-dynamicpv-qkxq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.174546616s
Jun 10 00:20:55.849: INFO: Pod "pod-subpath-test-dynamicpv-qkxq": Phase="Pending", Reason="", readiness=false. Elapsed: 8.218416522s
Jun 10 00:20:57.893: INFO: Pod "pod-subpath-test-dynamicpv-qkxq": Phase="Pending", Reason="", readiness=false. Elapsed: 10.262313522s
... skipping 7 lines ...
Jun 10 00:21:14.280: INFO: Pod "pod-subpath-test-dynamicpv-qkxq": Phase="Running", Reason="", readiness=true. Elapsed: 26.649363223s
Jun 10 00:21:16.323: INFO: Pod "pod-subpath-test-dynamicpv-qkxq": Phase="Running", Reason="", readiness=true. Elapsed: 28.692921416s
Jun 10 00:21:18.369: INFO: Pod "pod-subpath-test-dynamicpv-qkxq": Phase="Running", Reason="", readiness=true. Elapsed: 30.73883402s
Jun 10 00:21:20.413: INFO: Pod "pod-subpath-test-dynamicpv-qkxq": Phase="Running", Reason="", readiness=true. Elapsed: 32.782417405s
Jun 10 00:21:22.457: INFO: Pod "pod-subpath-test-dynamicpv-qkxq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.826652135s
STEP: Saw pod success
Jun 10 00:21:22.457: INFO: Pod "pod-subpath-test-dynamicpv-qkxq" satisfied condition "Succeeded or Failed"
Jun 10 00:21:22.500: INFO: Trying to get logs from node ip-172-20-37-21.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-qkxq container test-container-subpath-dynamicpv-qkxq: <nil>
STEP: delete the pod
Jun 10 00:21:22.608: INFO: Waiting for pod pod-subpath-test-dynamicpv-qkxq to disappear
Jun 10 00:21:22.651: INFO: Pod pod-subpath-test-dynamicpv-qkxq no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-qkxq
Jun 10 00:21:22.651: INFO: Deleting pod "pod-subpath-test-dynamicpv-qkxq" in namespace "provisioning-906"
... skipping 206 lines ...
Jun 10 00:21:55.985: INFO: Waiting for pod aws-client to disappear
Jun 10 00:21:56.027: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 10 00:21:56.027: INFO: Deleting PersistentVolumeClaim "pvc-d4xfq"
Jun 10 00:21:56.070: INFO: Deleting PersistentVolume "aws-mk9rh"
Jun 10 00:21:56.401: INFO: Couldn't delete PD "aws://us-east-2a/vol-0c690e28a77d19bae", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c690e28a77d19bae is currently attached to i-0c35a223bdb203427
	status code: 400, request id: a8e25303-6d87-4640-86c3-f71097e900e6
Jun 10 00:22:01.707: INFO: Couldn't delete PD "aws://us-east-2a/vol-0c690e28a77d19bae", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c690e28a77d19bae is currently attached to i-0c35a223bdb203427
	status code: 400, request id: 27a72ea2-d60a-47a3-9eec-87180a00bbf6
Jun 10 00:22:07.040: INFO: Couldn't delete PD "aws://us-east-2a/vol-0c690e28a77d19bae", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c690e28a77d19bae is currently attached to i-0c35a223bdb203427
	status code: 400, request id: 1d59249d-76bc-4787-a1d6-12be3a8ad94b
Jun 10 00:22:12.370: INFO: Successfully deleted PD "aws://us-east-2a/vol-0c690e28a77d19bae".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumes
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 10 00:22:12.370: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-8885" for this suite.
... skipping 319 lines ...
Jun 10 00:21:22.761: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-862-e2e-scg5xgb
STEP: creating a claim
Jun 10 00:21:22.806: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-pqgd
STEP: Creating a pod to test subpath
Jun 10 00:21:22.937: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-pqgd" in namespace "provisioning-862" to be "Succeeded or Failed"
Jun 10 00:21:22.979: INFO: Pod "pod-subpath-test-dynamicpv-pqgd": Phase="Pending", Reason="", readiness=false. Elapsed: 42.062689ms
Jun 10 00:21:25.024: INFO: Pod "pod-subpath-test-dynamicpv-pqgd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.086590944s
Jun 10 00:21:27.067: INFO: Pod "pod-subpath-test-dynamicpv-pqgd": Phase="Pending", Reason="", readiness=false. Elapsed: 4.130004327s
Jun 10 00:21:29.110: INFO: Pod "pod-subpath-test-dynamicpv-pqgd": Phase="Pending", Reason="", readiness=false. Elapsed: 6.173227579s
Jun 10 00:21:31.153: INFO: Pod "pod-subpath-test-dynamicpv-pqgd": Phase="Pending", Reason="", readiness=false. Elapsed: 8.215843505s
Jun 10 00:21:33.197: INFO: Pod "pod-subpath-test-dynamicpv-pqgd": Phase="Pending", Reason="", readiness=false. Elapsed: 10.259496291s
... skipping 2 lines ...
Jun 10 00:21:39.333: INFO: Pod "pod-subpath-test-dynamicpv-pqgd": Phase="Pending", Reason="", readiness=false. Elapsed: 16.396230206s
Jun 10 00:21:41.377: INFO: Pod "pod-subpath-test-dynamicpv-pqgd": Phase="Pending", Reason="", readiness=false. Elapsed: 18.439479016s
Jun 10 00:21:43.419: INFO: Pod "pod-subpath-test-dynamicpv-pqgd": Phase="Pending", Reason="", readiness=false. Elapsed: 20.481919327s
Jun 10 00:21:45.462: INFO: Pod "pod-subpath-test-dynamicpv-pqgd": Phase="Pending", Reason="", readiness=false. Elapsed: 22.524678884s
Jun 10 00:21:47.504: INFO: Pod "pod-subpath-test-dynamicpv-pqgd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.566923272s
STEP: Saw pod success
Jun 10 00:21:47.504: INFO: Pod "pod-subpath-test-dynamicpv-pqgd" satisfied condition "Succeeded or Failed"
Jun 10 00:21:47.547: INFO: Trying to get logs from node ip-172-20-40-185.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-pqgd container test-container-volume-dynamicpv-pqgd: <nil>
STEP: delete the pod
Jun 10 00:21:47.652: INFO: Waiting for pod pod-subpath-test-dynamicpv-pqgd to disappear
Jun 10 00:21:47.704: INFO: Pod pod-subpath-test-dynamicpv-pqgd no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-pqgd
Jun 10 00:21:47.704: INFO: Deleting pod "pod-subpath-test-dynamicpv-pqgd" in namespace "provisioning-862"
... skipping 39 lines ...
Jun 10 00:21:51.830: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4330-e2e-scqplkm
STEP: creating a claim
Jun 10 00:21:51.884: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-246d
STEP: Creating a pod to test multi_subpath
Jun 10 00:21:52.020: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-246d" in namespace "provisioning-4330" to be "Succeeded or Failed"
Jun 10 00:21:52.062: INFO: Pod "pod-subpath-test-dynamicpv-246d": Phase="Pending", Reason="", readiness=false. Elapsed: 41.877841ms
Jun 10 00:21:54.104: INFO: Pod "pod-subpath-test-dynamicpv-246d": Phase="Pending", Reason="", readiness=false. Elapsed: 2.083489462s
Jun 10 00:21:56.146: INFO: Pod "pod-subpath-test-dynamicpv-246d": Phase="Pending", Reason="", readiness=false. Elapsed: 4.125773317s
Jun 10 00:21:58.190: INFO: Pod "pod-subpath-test-dynamicpv-246d": Phase="Pending", Reason="", readiness=false. Elapsed: 6.16948463s
Jun 10 00:22:00.233: INFO: Pod "pod-subpath-test-dynamicpv-246d": Phase="Pending", Reason="", readiness=false. Elapsed: 8.212791718s
Jun 10 00:22:02.275: INFO: Pod "pod-subpath-test-dynamicpv-246d": Phase="Pending", Reason="", readiness=false. Elapsed: 10.255151811s
... skipping 2 lines ...
Jun 10 00:22:08.405: INFO: Pod "pod-subpath-test-dynamicpv-246d": Phase="Pending", Reason="", readiness=false. Elapsed: 16.384486222s
Jun 10 00:22:10.448: INFO: Pod "pod-subpath-test-dynamicpv-246d": Phase="Pending", Reason="", readiness=false. Elapsed: 18.427929313s
Jun 10 00:22:12.490: INFO: Pod "pod-subpath-test-dynamicpv-246d": Phase="Pending", Reason="", readiness=false. Elapsed: 20.469963754s
Jun 10 00:22:14.536: INFO: Pod "pod-subpath-test-dynamicpv-246d": Phase="Pending", Reason="", readiness=false. Elapsed: 22.515310173s
Jun 10 00:22:16.579: INFO: Pod "pod-subpath-test-dynamicpv-246d": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.558801009s
STEP: Saw pod success
Jun 10 00:22:16.579: INFO: Pod "pod-subpath-test-dynamicpv-246d" satisfied condition "Succeeded or Failed"
Jun 10 00:22:16.621: INFO: Trying to get logs from node ip-172-20-53-235.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-246d container test-container-subpath-dynamicpv-246d: <nil>
STEP: delete the pod
Jun 10 00:22:16.716: INFO: Waiting for pod pod-subpath-test-dynamicpv-246d to disappear
Jun 10 00:22:16.759: INFO: Pod pod-subpath-test-dynamicpv-246d no longer exists
STEP: Deleting pod
Jun 10 00:22:16.759: INFO: Deleting pod "pod-subpath-test-dynamicpv-246d" in namespace "provisioning-4330"
... skipping 291 lines ...
Jun 10 00:21:35.818: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9376zzfdl
STEP: creating a claim
Jun 10 00:21:35.859: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-rm5c
STEP: Creating a pod to test subpath
Jun 10 00:21:35.988: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-rm5c" in namespace "provisioning-9376" to be "Succeeded or Failed"
Jun 10 00:21:36.029: INFO: Pod "pod-subpath-test-dynamicpv-rm5c": Phase="Pending", Reason="", readiness=false. Elapsed: 41.208991ms
Jun 10 00:21:38.073: INFO: Pod "pod-subpath-test-dynamicpv-rm5c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.084937661s
Jun 10 00:21:40.116: INFO: Pod "pod-subpath-test-dynamicpv-rm5c": Phase="Pending", Reason="", readiness=false. Elapsed: 4.12862724s
Jun 10 00:21:42.159: INFO: Pod "pod-subpath-test-dynamicpv-rm5c": Phase="Pending", Reason="", readiness=false. Elapsed: 6.170723356s
Jun 10 00:21:44.201: INFO: Pod "pod-subpath-test-dynamicpv-rm5c": Phase="Pending", Reason="", readiness=false. Elapsed: 8.213522367s
Jun 10 00:21:46.243: INFO: Pod "pod-subpath-test-dynamicpv-rm5c": Phase="Pending", Reason="", readiness=false. Elapsed: 10.255208431s
... skipping 9 lines ...
Jun 10 00:22:06.688: INFO: Pod "pod-subpath-test-dynamicpv-rm5c": Phase="Pending", Reason="", readiness=false. Elapsed: 30.700598074s
Jun 10 00:22:08.731: INFO: Pod "pod-subpath-test-dynamicpv-rm5c": Phase="Pending", Reason="", readiness=false. Elapsed: 32.743236588s
Jun 10 00:22:10.773: INFO: Pod "pod-subpath-test-dynamicpv-rm5c": Phase="Pending", Reason="", readiness=false. Elapsed: 34.785258088s
Jun 10 00:22:12.816: INFO: Pod "pod-subpath-test-dynamicpv-rm5c": Phase="Pending", Reason="", readiness=false. Elapsed: 36.828343975s
Jun 10 00:22:14.859: INFO: Pod "pod-subpath-test-dynamicpv-rm5c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 38.870981899s
STEP: Saw pod success
Jun 10 00:22:14.859: INFO: Pod "pod-subpath-test-dynamicpv-rm5c" satisfied condition "Succeeded or Failed"
Jun 10 00:22:14.900: INFO: Trying to get logs from node ip-172-20-37-21.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-rm5c container test-container-volume-dynamicpv-rm5c: <nil>
STEP: delete the pod
Jun 10 00:22:14.995: INFO: Waiting for pod pod-subpath-test-dynamicpv-rm5c to disappear
Jun 10 00:22:15.036: INFO: Pod pod-subpath-test-dynamicpv-rm5c no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-rm5c
Jun 10 00:22:15.036: INFO: Deleting pod "pod-subpath-test-dynamicpv-rm5c" in namespace "provisioning-9376"
... skipping 214 lines ...
Jun 10 00:21:28.876: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-9063-e2e-scstb64
STEP: creating a claim
Jun 10 00:21:28.917: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-8bfr
STEP: Creating a pod to test exec-volume-test
Jun 10 00:21:29.042: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-8bfr" in namespace "volume-9063" to be "Succeeded or Failed"
Jun 10 00:21:29.086: INFO: Pod "exec-volume-test-dynamicpv-8bfr": Phase="Pending", Reason="", readiness=false. Elapsed: 43.485263ms
Jun 10 00:21:31.127: INFO: Pod "exec-volume-test-dynamicpv-8bfr": Phase="Pending", Reason="", readiness=false. Elapsed: 2.084688204s
Jun 10 00:21:33.170: INFO: Pod "exec-volume-test-dynamicpv-8bfr": Phase="Pending", Reason="", readiness=false. Elapsed: 4.127169097s
Jun 10 00:21:35.211: INFO: Pod "exec-volume-test-dynamicpv-8bfr": Phase="Pending", Reason="", readiness=false. Elapsed: 6.168607607s
Jun 10 00:21:37.253: INFO: Pod "exec-volume-test-dynamicpv-8bfr": Phase="Pending", Reason="", readiness=false. Elapsed: 8.210313852s
Jun 10 00:21:39.295: INFO: Pod "exec-volume-test-dynamicpv-8bfr": Phase="Pending", Reason="", readiness=false. Elapsed: 10.252804301s
... skipping 9 lines ...
Jun 10 00:21:59.709: INFO: Pod "exec-volume-test-dynamicpv-8bfr": Phase="Pending", Reason="", readiness=false. Elapsed: 30.66703571s
Jun 10 00:22:01.751: INFO: Pod "exec-volume-test-dynamicpv-8bfr": Phase="Pending", Reason="", readiness=false. Elapsed: 32.708662763s
Jun 10 00:22:03.794: INFO: Pod "exec-volume-test-dynamicpv-8bfr": Phase="Pending", Reason="", readiness=false. Elapsed: 34.751713925s
Jun 10 00:22:05.841: INFO: Pod "exec-volume-test-dynamicpv-8bfr": Phase="Pending", Reason="", readiness=false. Elapsed: 36.799042851s
Jun 10 00:22:07.884: INFO: Pod "exec-volume-test-dynamicpv-8bfr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 38.841282436s
STEP: Saw pod success
Jun 10 00:22:07.884: INFO: Pod "exec-volume-test-dynamicpv-8bfr" satisfied condition "Succeeded or Failed"
Jun 10 00:22:07.925: INFO: Trying to get logs from node ip-172-20-37-21.us-east-2.compute.internal pod exec-volume-test-dynamicpv-8bfr container exec-container-dynamicpv-8bfr: <nil>
STEP: delete the pod
Jun 10 00:22:08.018: INFO: Waiting for pod exec-volume-test-dynamicpv-8bfr to disappear
Jun 10 00:22:08.059: INFO: Pod exec-volume-test-dynamicpv-8bfr no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-8bfr
Jun 10 00:22:08.059: INFO: Deleting pod "exec-volume-test-dynamicpv-8bfr" in namespace "volume-9063"
... skipping 57 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.Ze8yNfZ8r/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.Ze8yNfZ8r/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.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 45 lines ...
Jun 10 00:21:53.533: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6569-e2e-sch72bd
STEP: creating a claim
Jun 10 00:21:53.578: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-m7zh
STEP: Creating a pod to test subpath
Jun 10 00:21:53.712: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-m7zh" in namespace "provisioning-6569" to be "Succeeded or Failed"
Jun 10 00:21:53.757: INFO: Pod "pod-subpath-test-dynamicpv-m7zh": Phase="Pending", Reason="", readiness=false. Elapsed: 44.229748ms
Jun 10 00:21:55.813: INFO: Pod "pod-subpath-test-dynamicpv-m7zh": Phase="Pending", Reason="", readiness=false. Elapsed: 2.10015443s
Jun 10 00:21:57.856: INFO: Pod "pod-subpath-test-dynamicpv-m7zh": Phase="Pending", Reason="", readiness=false. Elapsed: 4.143542307s
Jun 10 00:21:59.902: INFO: Pod "pod-subpath-test-dynamicpv-m7zh": Phase="Pending", Reason="", readiness=false. Elapsed: 6.189703625s
Jun 10 00:22:01.945: INFO: Pod "pod-subpath-test-dynamicpv-m7zh": Phase="Pending", Reason="", readiness=false. Elapsed: 8.232836858s
Jun 10 00:22:03.988: INFO: Pod "pod-subpath-test-dynamicpv-m7zh": Phase="Pending", Reason="", readiness=false. Elapsed: 10.276022976s
Jun 10 00:22:06.032: INFO: Pod "pod-subpath-test-dynamicpv-m7zh": Phase="Pending", Reason="", readiness=false. Elapsed: 12.319710367s
Jun 10 00:22:08.077: INFO: Pod "pod-subpath-test-dynamicpv-m7zh": Phase="Pending", Reason="", readiness=false. Elapsed: 14.364096894s
Jun 10 00:22:10.120: INFO: Pod "pod-subpath-test-dynamicpv-m7zh": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.407421852s
STEP: Saw pod success
Jun 10 00:22:10.120: INFO: Pod "pod-subpath-test-dynamicpv-m7zh" satisfied condition "Succeeded or Failed"
Jun 10 00:22:10.163: INFO: Trying to get logs from node ip-172-20-40-185.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-m7zh container test-container-subpath-dynamicpv-m7zh: <nil>
STEP: delete the pod
Jun 10 00:22:10.270: INFO: Waiting for pod pod-subpath-test-dynamicpv-m7zh to disappear
Jun 10 00:22:10.324: INFO: Pod pod-subpath-test-dynamicpv-m7zh no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-m7zh
Jun 10 00:22:10.324: INFO: Deleting pod "pod-subpath-test-dynamicpv-m7zh" in namespace "provisioning-6569"
STEP: Creating pod pod-subpath-test-dynamicpv-m7zh
STEP: Creating a pod to test subpath
Jun 10 00:22:10.413: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-m7zh" in namespace "provisioning-6569" to be "Succeeded or Failed"
Jun 10 00:22:10.455: INFO: Pod "pod-subpath-test-dynamicpv-m7zh": Phase="Pending", Reason="", readiness=false. Elapsed: 42.423537ms
Jun 10 00:22:12.498: INFO: Pod "pod-subpath-test-dynamicpv-m7zh": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.085465893s
STEP: Saw pod success
Jun 10 00:22:12.498: INFO: Pod "pod-subpath-test-dynamicpv-m7zh" satisfied condition "Succeeded or Failed"
Jun 10 00:22:12.541: INFO: Trying to get logs from node ip-172-20-40-185.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-m7zh container test-container-subpath-dynamicpv-m7zh: <nil>
STEP: delete the pod
Jun 10 00:22:12.634: INFO: Waiting for pod pod-subpath-test-dynamicpv-m7zh to disappear
Jun 10 00:22:12.677: INFO: Pod pod-subpath-test-dynamicpv-m7zh no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-m7zh
Jun 10 00:22:12.677: INFO: Deleting pod "pod-subpath-test-dynamicpv-m7zh" in namespace "provisioning-6569"
... skipping 59 lines ...

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

      Distro debian doesn't support ntfs -- skipping

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.Ze8yNfZ8r/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.Ze8yNfZ8r/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.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 12 lines ...
Jun 10 00:22:42.334: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7377g2d8b
STEP: creating a claim
Jun 10 00:22:42.376: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-5j9z
STEP: Creating a pod to test multi_subpath
Jun 10 00:22:42.539: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-5j9z" in namespace "provisioning-7377" to be "Succeeded or Failed"
Jun 10 00:22:42.585: INFO: Pod "pod-subpath-test-dynamicpv-5j9z": Phase="Pending", Reason="", readiness=false. Elapsed: 46.482644ms
Jun 10 00:22:44.627: INFO: Pod "pod-subpath-test-dynamicpv-5j9z": Phase="Pending", Reason="", readiness=false. Elapsed: 2.088527322s
Jun 10 00:22:46.670: INFO: Pod "pod-subpath-test-dynamicpv-5j9z": Phase="Pending", Reason="", readiness=false. Elapsed: 4.130578622s
Jun 10 00:22:48.713: INFO: Pod "pod-subpath-test-dynamicpv-5j9z": Phase="Pending", Reason="", readiness=false. Elapsed: 6.174310687s
Jun 10 00:22:50.762: INFO: Pod "pod-subpath-test-dynamicpv-5j9z": Phase="Pending", Reason="", readiness=false. Elapsed: 8.223324978s
Jun 10 00:22:52.805: INFO: Pod "pod-subpath-test-dynamicpv-5j9z": Phase="Pending", Reason="", readiness=false. Elapsed: 10.265625558s
Jun 10 00:22:54.847: INFO: Pod "pod-subpath-test-dynamicpv-5j9z": Phase="Pending", Reason="", readiness=false. Elapsed: 12.308272815s
Jun 10 00:22:56.890: INFO: Pod "pod-subpath-test-dynamicpv-5j9z": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.351410893s
STEP: Saw pod success
Jun 10 00:22:56.890: INFO: Pod "pod-subpath-test-dynamicpv-5j9z" satisfied condition "Succeeded or Failed"
Jun 10 00:22:56.932: INFO: Trying to get logs from node ip-172-20-56-177.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-5j9z container test-container-subpath-dynamicpv-5j9z: <nil>
STEP: delete the pod
Jun 10 00:22:57.030: INFO: Waiting for pod pod-subpath-test-dynamicpv-5j9z to disappear
Jun 10 00:22:57.075: INFO: Pod pod-subpath-test-dynamicpv-5j9z no longer exists
STEP: Deleting pod
Jun 10 00:22:57.075: INFO: Deleting pod "pod-subpath-test-dynamicpv-5j9z" in namespace "provisioning-7377"
... skipping 439 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.Ze8yNfZ8r/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.Ze8yNfZ8r/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.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 107 lines ...
Jun 10 00:23:06.413: INFO: Pod aws-client still exists
Jun 10 00:23:08.370: INFO: Waiting for pod aws-client to disappear
Jun 10 00:23:08.412: INFO: Pod aws-client still exists
Jun 10 00:23:10.370: INFO: Waiting for pod aws-client to disappear
Jun 10 00:23:10.412: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun 10 00:23:10.742: INFO: Couldn't delete PD "aws://us-east-2a/vol-081a28e51f7a5b1f7", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-081a28e51f7a5b1f7 is currently attached to i-0d2e89f8b75d98870
	status code: 400, request id: ba667c26-99e2-4102-93ef-a65ccd28c832
Jun 10 00:23:16.038: INFO: Couldn't delete PD "aws://us-east-2a/vol-081a28e51f7a5b1f7", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-081a28e51f7a5b1f7 is currently attached to i-0d2e89f8b75d98870
	status code: 400, request id: 5492b824-bf87-441d-8a05-ab05fff8bf38
Jun 10 00:23:21.335: INFO: Successfully deleted PD "aws://us-east-2a/vol-081a28e51f7a5b1f7".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 10 00:23:21.336: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-9033" for this suite.
... skipping 203 lines ...
Jun 10 00:22:41.479: INFO: PersistentVolumeClaim pvc-8x7c9 found but phase is Pending instead of Bound.
Jun 10 00:22:43.520: INFO: PersistentVolumeClaim pvc-8x7c9 found and phase=Bound (2.083987082s)
Jun 10 00:22:43.520: INFO: Waiting up to 3m0s for PersistentVolume aws-n6pnv to have phase Bound
Jun 10 00:22:43.562: INFO: PersistentVolume aws-n6pnv found and phase=Bound (41.966577ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-nxsp
STEP: Creating a pod to test exec-volume-test
Jun 10 00:22:43.688: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-nxsp" in namespace "volume-5076" to be "Succeeded or Failed"
Jun 10 00:22:43.730: INFO: Pod "exec-volume-test-preprovisionedpv-nxsp": Phase="Pending", Reason="", readiness=false. Elapsed: 41.773435ms
Jun 10 00:22:45.772: INFO: Pod "exec-volume-test-preprovisionedpv-nxsp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.083888502s
Jun 10 00:22:47.815: INFO: Pod "exec-volume-test-preprovisionedpv-nxsp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.126437232s
Jun 10 00:22:49.856: INFO: Pod "exec-volume-test-preprovisionedpv-nxsp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.167656959s
Jun 10 00:22:51.899: INFO: Pod "exec-volume-test-preprovisionedpv-nxsp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.210470624s
Jun 10 00:22:53.942: INFO: Pod "exec-volume-test-preprovisionedpv-nxsp": Phase="Pending", Reason="", readiness=false. Elapsed: 10.253832289s
Jun 10 00:22:55.986: INFO: Pod "exec-volume-test-preprovisionedpv-nxsp": Phase="Pending", Reason="", readiness=false. Elapsed: 12.29808179s
Jun 10 00:22:58.030: INFO: Pod "exec-volume-test-preprovisionedpv-nxsp": Phase="Pending", Reason="", readiness=false. Elapsed: 14.341475247s
Jun 10 00:23:00.071: INFO: Pod "exec-volume-test-preprovisionedpv-nxsp": Phase="Pending", Reason="", readiness=false. Elapsed: 16.382898711s
Jun 10 00:23:02.114: INFO: Pod "exec-volume-test-preprovisionedpv-nxsp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.425842327s
STEP: Saw pod success
Jun 10 00:23:02.114: INFO: Pod "exec-volume-test-preprovisionedpv-nxsp" satisfied condition "Succeeded or Failed"
Jun 10 00:23:02.155: INFO: Trying to get logs from node ip-172-20-56-177.us-east-2.compute.internal pod exec-volume-test-preprovisionedpv-nxsp container exec-container-preprovisionedpv-nxsp: <nil>
STEP: delete the pod
Jun 10 00:23:02.246: INFO: Waiting for pod exec-volume-test-preprovisionedpv-nxsp to disappear
Jun 10 00:23:02.287: INFO: Pod exec-volume-test-preprovisionedpv-nxsp no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-nxsp
Jun 10 00:23:02.287: INFO: Deleting pod "exec-volume-test-preprovisionedpv-nxsp" in namespace "volume-5076"
STEP: Deleting pv and pvc
Jun 10 00:23:02.328: INFO: Deleting PersistentVolumeClaim "pvc-8x7c9"
Jun 10 00:23:02.370: INFO: Deleting PersistentVolume "aws-n6pnv"
Jun 10 00:23:02.568: INFO: Couldn't delete PD "aws://us-east-2a/vol-026ec1b00517e4c24", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-026ec1b00517e4c24 is currently attached to i-0d2e89f8b75d98870
	status code: 400, request id: 96b33c34-41c0-4f52-bd55-b620e07c97c6
Jun 10 00:23:07.903: INFO: Couldn't delete PD "aws://us-east-2a/vol-026ec1b00517e4c24", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-026ec1b00517e4c24 is currently attached to i-0d2e89f8b75d98870
	status code: 400, request id: 69c8e37e-110b-4f0b-a570-35f2f49e5d55
Jun 10 00:23:13.210: INFO: Couldn't delete PD "aws://us-east-2a/vol-026ec1b00517e4c24", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-026ec1b00517e4c24 is currently attached to i-0d2e89f8b75d98870
	status code: 400, request id: 967e2c4f-3eff-4fd7-8bac-75eb84d084f9
Jun 10 00:23:18.533: INFO: Couldn't delete PD "aws://us-east-2a/vol-026ec1b00517e4c24", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-026ec1b00517e4c24 is currently attached to i-0d2e89f8b75d98870
	status code: 400, request id: 7cb049ea-96a5-43bd-8269-7e4ac2cf584b
Jun 10 00:23:23.862: INFO: Successfully deleted PD "aws://us-east-2a/vol-026ec1b00517e4c24".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 10 00:23:23.862: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-5076" for this suite.
... skipping 99 lines ...
Jun 10 00:22:53.335: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-62127jbks
STEP: creating a claim
Jun 10 00:22:53.376: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-f8hb
STEP: Creating a pod to test exec-volume-test
Jun 10 00:22:53.504: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-f8hb" in namespace "volume-6212" to be "Succeeded or Failed"
Jun 10 00:22:53.546: INFO: Pod "exec-volume-test-dynamicpv-f8hb": Phase="Pending", Reason="", readiness=false. Elapsed: 41.887107ms
Jun 10 00:22:55.588: INFO: Pod "exec-volume-test-dynamicpv-f8hb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.083886264s
Jun 10 00:22:57.631: INFO: Pod "exec-volume-test-dynamicpv-f8hb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.127261719s
Jun 10 00:22:59.673: INFO: Pod "exec-volume-test-dynamicpv-f8hb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.169339715s
Jun 10 00:23:01.715: INFO: Pod "exec-volume-test-dynamicpv-f8hb": Phase="Pending", Reason="", readiness=false. Elapsed: 8.211099019s
Jun 10 00:23:03.757: INFO: Pod "exec-volume-test-dynamicpv-f8hb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.25279162s
STEP: Saw pod success
Jun 10 00:23:03.757: INFO: Pod "exec-volume-test-dynamicpv-f8hb" satisfied condition "Succeeded or Failed"
Jun 10 00:23:03.797: INFO: Trying to get logs from node ip-172-20-56-177.us-east-2.compute.internal pod exec-volume-test-dynamicpv-f8hb container exec-container-dynamicpv-f8hb: <nil>
STEP: delete the pod
Jun 10 00:23:03.888: INFO: Waiting for pod exec-volume-test-dynamicpv-f8hb to disappear
Jun 10 00:23:03.929: INFO: Pod exec-volume-test-dynamicpv-f8hb no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-f8hb
Jun 10 00:23:03.929: INFO: Deleting pod "exec-volume-test-dynamicpv-f8hb" in namespace "volume-6212"
... skipping 437 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Ze8yNfZ8r/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Ze8yNfZ8r/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.Ze8yNfZ8r/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.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 67 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 00:22:59.731: 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.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun 10 00:22:59.941: INFO: Creating resource for dynamic PV
Jun 10 00:22:59.941: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7727-e2e-sc9fppp
STEP: creating a claim
Jun 10 00:22:59.983: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-ms4v
STEP: Checking for subpath error in container status
Jun 10 00:23:26.213: INFO: Deleting pod "pod-subpath-test-dynamicpv-ms4v" in namespace "provisioning-7727"
Jun 10 00:23:26.256: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-ms4v" to be fully deleted
STEP: Deleting pod
Jun 10 00:23:38.340: INFO: Deleting pod "pod-subpath-test-dynamicpv-ms4v" in namespace "provisioning-7727"
STEP: Deleting pvc
Jun 10 00:23:38.466: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com84hw5"
... skipping 9 lines ...

• [SLOW TEST:44.002 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath directory is outside the volume [Slow][LinuxOnly]
    /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ext3)] volumes
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 10 00:23:43.735: INFO: Driver ebs.csi.aws.com doesn't support ext3 -- skipping
[AfterEach] [Testpattern: Dynamic PV (ext3)] volumes
... skipping 196 lines ...
Jun 10 00:23:21.639: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-9642-e2e-sc6jjfk
STEP: creating a claim
Jun 10 00:23:21.684: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Jun 10 00:23:21.771: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 10 00:23:21.869: INFO: Error updating pvc ebs.csi.aws.comvn8jc: PersistentVolumeClaim "ebs.csi.aws.comvn8jc" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-9642-e2e-sc6jjfk",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 10 lines ...
Jun 10 00:21:42.503: INFO: Creating resource for dynamic PV
Jun 10 00:21:42.503: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-9801-e2e-scp6lvp
STEP: creating a claim
Jun 10 00:21:42.547: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 10 00:21:42.678: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-nxfl6" in namespace "snapshotting-9801" to be "Succeeded or Failed"
Jun 10 00:21:42.722: INFO: Pod "pvc-snapshottable-tester-nxfl6": Phase="Pending", Reason="", readiness=false. Elapsed: 43.628158ms
Jun 10 00:21:44.765: INFO: Pod "pvc-snapshottable-tester-nxfl6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.086916141s
Jun 10 00:21:46.807: INFO: Pod "pvc-snapshottable-tester-nxfl6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.128909494s
Jun 10 00:21:48.850: INFO: Pod "pvc-snapshottable-tester-nxfl6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.17130258s
Jun 10 00:21:50.893: INFO: Pod "pvc-snapshottable-tester-nxfl6": Phase="Pending", Reason="", readiness=false. Elapsed: 8.214208538s
Jun 10 00:21:52.936: INFO: Pod "pvc-snapshottable-tester-nxfl6": Phase="Pending", Reason="", readiness=false. Elapsed: 10.257968824s
Jun 10 00:21:54.978: INFO: Pod "pvc-snapshottable-tester-nxfl6": Phase="Pending", Reason="", readiness=false. Elapsed: 12.299727912s
Jun 10 00:21:57.020: INFO: Pod "pvc-snapshottable-tester-nxfl6": Phase="Pending", Reason="", readiness=false. Elapsed: 14.341755777s
Jun 10 00:21:59.062: INFO: Pod "pvc-snapshottable-tester-nxfl6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.38366494s
STEP: Saw pod success
Jun 10 00:21:59.062: INFO: Pod "pvc-snapshottable-tester-nxfl6" satisfied condition "Succeeded or Failed"
Jun 10 00:21:59.146: INFO: Pod pvc-snapshottable-tester-nxfl6 has the following logs: 
Jun 10 00:21:59.146: INFO: Deleting pod "pvc-snapshottable-tester-nxfl6" in namespace "snapshotting-9801"
Jun 10 00:21:59.207: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-nxfl6" to be fully deleted
Jun 10 00:21:59.248: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comzxdq4] to have phase Bound
Jun 10 00:21:59.289: INFO: PersistentVolumeClaim ebs.csi.aws.comzxdq4 found and phase=Bound (41.478345ms)
STEP: [init] checking the claim
... skipping 34 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.Ze8yNfZ8r/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 10 00:22:48.820: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-h8cjt" in namespace "snapshotting-9801" to be "Succeeded or Failed"
Jun 10 00:22:48.862: INFO: Pod "pvc-snapshottable-data-tester-h8cjt": Phase="Pending", Reason="", readiness=false. Elapsed: 42.10995ms
Jun 10 00:22:50.905: INFO: Pod "pvc-snapshottable-data-tester-h8cjt": Phase="Pending", Reason="", readiness=false. Elapsed: 2.085086369s
Jun 10 00:22:52.949: INFO: Pod "pvc-snapshottable-data-tester-h8cjt": Phase="Pending", Reason="", readiness=false. Elapsed: 4.128902984s
Jun 10 00:22:54.995: INFO: Pod "pvc-snapshottable-data-tester-h8cjt": Phase="Pending", Reason="", readiness=false. Elapsed: 6.174714768s
Jun 10 00:22:57.037: INFO: Pod "pvc-snapshottable-data-tester-h8cjt": Phase="Pending", Reason="", readiness=false. Elapsed: 8.216822096s
Jun 10 00:22:59.081: INFO: Pod "pvc-snapshottable-data-tester-h8cjt": Phase="Pending", Reason="", readiness=false. Elapsed: 10.260989413s
Jun 10 00:23:01.125: INFO: Pod "pvc-snapshottable-data-tester-h8cjt": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.304639708s
STEP: Saw pod success
Jun 10 00:23:01.125: INFO: Pod "pvc-snapshottable-data-tester-h8cjt" satisfied condition "Succeeded or Failed"
Jun 10 00:23:01.210: INFO: Pod pvc-snapshottable-data-tester-h8cjt has the following logs: 
Jun 10 00:23:01.210: INFO: Deleting pod "pvc-snapshottable-data-tester-h8cjt" in namespace "snapshotting-9801"
Jun 10 00:23:01.264: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-h8cjt" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 10 00:23:23.476: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-9801 exec restored-pvc-tester-gq8zq --namespace=snapshotting-9801 -- cat /mnt/test/data'
... skipping 319 lines ...
Jun 10 00:23:54.069: INFO: Waiting for pod aws-client to disappear
Jun 10 00:23:54.112: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 10 00:23:54.112: INFO: Deleting PersistentVolumeClaim "pvc-9gwtk"
Jun 10 00:23:54.155: INFO: Deleting PersistentVolume "aws-68b27"
Jun 10 00:23:54.491: INFO: Couldn't delete PD "aws://us-east-2a/vol-09ae6e6f2d2aab7fc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-09ae6e6f2d2aab7fc is currently attached to i-0a2e25b9d9c987751
	status code: 400, request id: 9f670a5b-f802-45fb-83a4-330c90fcd5f3
Jun 10 00:23:59.827: INFO: Couldn't delete PD "aws://us-east-2a/vol-09ae6e6f2d2aab7fc", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-09ae6e6f2d2aab7fc is currently attached to i-0a2e25b9d9c987751
	status code: 400, request id: a23e1538-2266-4a98-a813-7fba696fcce8
Jun 10 00:24:05.140: INFO: Successfully deleted PD "aws://us-east-2a/vol-09ae6e6f2d2aab7fc".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 10 00:24:05.140: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-2604" for this suite.
... skipping 234 lines ...
Jun 10 00:23:39.800: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-6384tnwt2
STEP: creating a claim
Jun 10 00:23:39.842: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-8ldv
STEP: Creating a pod to test exec-volume-test
Jun 10 00:23:39.969: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-8ldv" in namespace "volume-6384" to be "Succeeded or Failed"
Jun 10 00:23:40.010: INFO: Pod "exec-volume-test-dynamicpv-8ldv": Phase="Pending", Reason="", readiness=false. Elapsed: 41.265086ms
Jun 10 00:23:42.052: INFO: Pod "exec-volume-test-dynamicpv-8ldv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.082621691s
Jun 10 00:23:44.097: INFO: Pod "exec-volume-test-dynamicpv-8ldv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.127812711s
Jun 10 00:23:46.138: INFO: Pod "exec-volume-test-dynamicpv-8ldv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.168940098s
Jun 10 00:23:48.179: INFO: Pod "exec-volume-test-dynamicpv-8ldv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.210187302s
Jun 10 00:23:50.220: INFO: Pod "exec-volume-test-dynamicpv-8ldv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.250860676s
Jun 10 00:23:52.263: INFO: Pod "exec-volume-test-dynamicpv-8ldv": Phase="Pending", Reason="", readiness=false. Elapsed: 12.293861043s
Jun 10 00:23:54.304: INFO: Pod "exec-volume-test-dynamicpv-8ldv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.335097527s
STEP: Saw pod success
Jun 10 00:23:54.304: INFO: Pod "exec-volume-test-dynamicpv-8ldv" satisfied condition "Succeeded or Failed"
Jun 10 00:23:54.346: INFO: Trying to get logs from node ip-172-20-56-177.us-east-2.compute.internal pod exec-volume-test-dynamicpv-8ldv container exec-container-dynamicpv-8ldv: <nil>
STEP: delete the pod
Jun 10 00:23:54.445: INFO: Waiting for pod exec-volume-test-dynamicpv-8ldv to disappear
Jun 10 00:23:54.486: INFO: Pod exec-volume-test-dynamicpv-8ldv no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-8ldv
Jun 10 00:23:54.487: INFO: Deleting pod "exec-volume-test-dynamicpv-8ldv" in namespace "volume-6384"
... skipping 119 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Ze8yNfZ8r/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Ze8yNfZ8r/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.Ze8yNfZ8r/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.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 87 lines ...
Jun 10 00:23:52.518: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-83337jvmw
STEP: creating a claim
Jun 10 00:23:52.562: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Jun 10 00:23:52.654: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 10 00:23:52.767: INFO: Error updating pvc awslqsvb: PersistentVolumeClaim "awslqsvb" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-83337jvmw",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun 10 00:24:22.942: INFO: Error updating pvc awslqsvb: PersistentVolumeClaim "awslqsvb" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 32 lines ...
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 00:24:23.161: 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.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Jun 10 00:24:23.416: INFO: found topology map[topology.kubernetes.io/zone:us-east-2a]
Jun 10 00:24:23.416: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 10 00:24:23.416: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Ze8yNfZ8r/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Ze8yNfZ8r/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (delayed binding)] topology
    /tmp/kops.Ze8yNfZ8r/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.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.Ze8yNfZ8r/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.Ze8yNfZ8r/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.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 176 lines ...
Jun 10 00:23:43.588: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1358t58wd
STEP: creating a claim
Jun 10 00:23:43.631: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-46l7
STEP: Creating a pod to test subpath
Jun 10 00:23:43.761: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-46l7" in namespace "provisioning-1358" to be "Succeeded or Failed"
Jun 10 00:23:43.803: INFO: Pod "pod-subpath-test-dynamicpv-46l7": Phase="Pending", Reason="", readiness=false. Elapsed: 41.287052ms
Jun 10 00:23:45.845: INFO: Pod "pod-subpath-test-dynamicpv-46l7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.083612298s
Jun 10 00:23:47.888: INFO: Pod "pod-subpath-test-dynamicpv-46l7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.126067478s
Jun 10 00:23:49.929: INFO: Pod "pod-subpath-test-dynamicpv-46l7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.167968009s
Jun 10 00:23:51.971: INFO: Pod "pod-subpath-test-dynamicpv-46l7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.209963795s
Jun 10 00:23:54.016: INFO: Pod "pod-subpath-test-dynamicpv-46l7": Phase="Pending", Reason="", readiness=false. Elapsed: 10.254484547s
Jun 10 00:23:56.058: INFO: Pod "pod-subpath-test-dynamicpv-46l7": Phase="Pending", Reason="", readiness=false. Elapsed: 12.296300956s
Jun 10 00:23:58.100: INFO: Pod "pod-subpath-test-dynamicpv-46l7": Phase="Pending", Reason="", readiness=false. Elapsed: 14.338493986s
Jun 10 00:24:00.142: INFO: Pod "pod-subpath-test-dynamicpv-46l7": Phase="Pending", Reason="", readiness=false. Elapsed: 16.380184322s
Jun 10 00:24:02.184: INFO: Pod "pod-subpath-test-dynamicpv-46l7": Phase="Pending", Reason="", readiness=false. Elapsed: 18.422230112s
Jun 10 00:24:04.226: INFO: Pod "pod-subpath-test-dynamicpv-46l7": Phase="Pending", Reason="", readiness=false. Elapsed: 20.46419457s
Jun 10 00:24:06.267: INFO: Pod "pod-subpath-test-dynamicpv-46l7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.505793936s
STEP: Saw pod success
Jun 10 00:24:06.267: INFO: Pod "pod-subpath-test-dynamicpv-46l7" satisfied condition "Succeeded or Failed"
Jun 10 00:24:06.310: INFO: Trying to get logs from node ip-172-20-40-185.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-46l7 container test-container-subpath-dynamicpv-46l7: <nil>
STEP: delete the pod
Jun 10 00:24:06.402: INFO: Waiting for pod pod-subpath-test-dynamicpv-46l7 to disappear
Jun 10 00:24:06.446: INFO: Pod pod-subpath-test-dynamicpv-46l7 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-46l7
Jun 10 00:24:06.446: INFO: Deleting pod "pod-subpath-test-dynamicpv-46l7" in namespace "provisioning-1358"
... skipping 383 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 00:23:43.737: 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.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun 10 00:23:43.947: INFO: Creating resource for dynamic PV
Jun 10 00:23:43.947: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2280-e2e-scrzp6p
STEP: creating a claim
Jun 10 00:23:43.992: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-kpmz
STEP: Checking for subpath error in container status
Jun 10 00:24:08.218: INFO: Deleting pod "pod-subpath-test-dynamicpv-kpmz" in namespace "provisioning-2280"
Jun 10 00:24:08.262: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-kpmz" to be fully deleted
STEP: Deleting pod
Jun 10 00:24:16.347: INFO: Deleting pod "pod-subpath-test-dynamicpv-kpmz" in namespace "provisioning-2280"
STEP: Deleting pvc
Jun 10 00:24:16.474: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comx2c8m"
... skipping 11 lines ...

• [SLOW TEST:48.091 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath file is outside the volume [Slow][LinuxOnly]
    /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 10 00:24:31.830: INFO: Driver "ebs.csi.aws.com" does not support volume type "CSIInlineVolume" - skipping
[AfterEach] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral
... skipping 237 lines ...
Jun 10 00:24:30.144: INFO: Waiting for pod aws-client to disappear
Jun 10 00:24:30.185: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun 10 00:24:30.185: INFO: Deleting PersistentVolumeClaim "pvc-msz8s"
Jun 10 00:24:30.228: INFO: Deleting PersistentVolume "aws-sl5hl"
Jun 10 00:24:30.615: INFO: Couldn't delete PD "aws://us-east-2a/vol-038a0687ee2db1398", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-038a0687ee2db1398 is currently attached to i-06f8a1a98a822b359
	status code: 400, request id: 2769b453-96d6-4864-93c7-6a6bfd91a914
Jun 10 00:24:35.911: INFO: Couldn't delete PD "aws://us-east-2a/vol-038a0687ee2db1398", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-038a0687ee2db1398 is currently attached to i-06f8a1a98a822b359
	status code: 400, request id: f80ee8a4-8191-45f9-88b7-e3e2276034c9
Jun 10 00:24:41.190: INFO: Successfully deleted PD "aws://us-east-2a/vol-038a0687ee2db1398".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 10 00:24:41.190: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-6787" for this suite.
... skipping 86 lines ...
Jun 10 00:23:39.408: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2520wtqp8
STEP: creating a claim
Jun 10 00:23:39.451: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-48qx
STEP: Creating a pod to test subpath
Jun 10 00:23:39.584: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-48qx" in namespace "provisioning-2520" to be "Succeeded or Failed"
Jun 10 00:23:39.630: INFO: Pod "pod-subpath-test-dynamicpv-48qx": Phase="Pending", Reason="", readiness=false. Elapsed: 45.880683ms
Jun 10 00:23:41.673: INFO: Pod "pod-subpath-test-dynamicpv-48qx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.089115362s
Jun 10 00:23:43.716: INFO: Pod "pod-subpath-test-dynamicpv-48qx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.132075466s
Jun 10 00:23:45.758: INFO: Pod "pod-subpath-test-dynamicpv-48qx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.174498249s
Jun 10 00:23:47.803: INFO: Pod "pod-subpath-test-dynamicpv-48qx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.219149223s
Jun 10 00:23:49.846: INFO: Pod "pod-subpath-test-dynamicpv-48qx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.262094309s
... skipping 2 lines ...
Jun 10 00:23:55.977: INFO: Pod "pod-subpath-test-dynamicpv-48qx": Phase="Pending", Reason="", readiness=false. Elapsed: 16.393620835s
Jun 10 00:23:58.021: INFO: Pod "pod-subpath-test-dynamicpv-48qx": Phase="Pending", Reason="", readiness=false. Elapsed: 18.436803059s
Jun 10 00:24:00.064: INFO: Pod "pod-subpath-test-dynamicpv-48qx": Phase="Pending", Reason="", readiness=false. Elapsed: 20.480203637s
Jun 10 00:24:02.107: INFO: Pod "pod-subpath-test-dynamicpv-48qx": Phase="Pending", Reason="", readiness=false. Elapsed: 22.523656819s
Jun 10 00:24:04.150: INFO: Pod "pod-subpath-test-dynamicpv-48qx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.566553196s
STEP: Saw pod success
Jun 10 00:24:04.150: INFO: Pod "pod-subpath-test-dynamicpv-48qx" satisfied condition "Succeeded or Failed"
Jun 10 00:24:04.193: INFO: Trying to get logs from node ip-172-20-53-235.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-48qx container test-container-subpath-dynamicpv-48qx: <nil>
STEP: delete the pod
Jun 10 00:24:04.288: INFO: Waiting for pod pod-subpath-test-dynamicpv-48qx to disappear
Jun 10 00:24:04.330: INFO: Pod pod-subpath-test-dynamicpv-48qx no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-48qx
Jun 10 00:24:04.330: INFO: Deleting pod "pod-subpath-test-dynamicpv-48qx" in namespace "provisioning-2520"
STEP: Creating pod pod-subpath-test-dynamicpv-48qx
STEP: Creating a pod to test subpath
Jun 10 00:24:04.420: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-48qx" in namespace "provisioning-2520" to be "Succeeded or Failed"
Jun 10 00:24:04.462: INFO: Pod "pod-subpath-test-dynamicpv-48qx": Phase="Pending", Reason="", readiness=false. Elapsed: 42.320192ms
Jun 10 00:24:06.505: INFO: Pod "pod-subpath-test-dynamicpv-48qx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.085456028s
Jun 10 00:24:08.549: INFO: Pod "pod-subpath-test-dynamicpv-48qx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.129050365s
STEP: Saw pod success
Jun 10 00:24:08.551: INFO: Pod "pod-subpath-test-dynamicpv-48qx" satisfied condition "Succeeded or Failed"
Jun 10 00:24:08.593: INFO: Trying to get logs from node ip-172-20-53-235.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-48qx container test-container-subpath-dynamicpv-48qx: <nil>
STEP: delete the pod
Jun 10 00:24:08.685: INFO: Waiting for pod pod-subpath-test-dynamicpv-48qx to disappear
Jun 10 00:24:08.727: INFO: Pod pod-subpath-test-dynamicpv-48qx no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-48qx
Jun 10 00:24:08.727: INFO: Deleting pod "pod-subpath-test-dynamicpv-48qx" in namespace "provisioning-2520"
... skipping 40 lines ...
Jun 10 00:24:01.985: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 10 00:24:02.469: INFO: Successfully created a new PD: "aws://us-east-2a/vol-05d69538fe26344bb".
Jun 10 00:24:02.469: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-5hkr
STEP: Creating a pod to test exec-volume-test
Jun 10 00:24:02.518: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-5hkr" in namespace "volume-3954" to be "Succeeded or Failed"
Jun 10 00:24:02.561: INFO: Pod "exec-volume-test-inlinevolume-5hkr": Phase="Pending", Reason="", readiness=false. Elapsed: 42.893268ms
Jun 10 00:24:04.605: INFO: Pod "exec-volume-test-inlinevolume-5hkr": Phase="Pending", Reason="", readiness=false. Elapsed: 2.086795636s
Jun 10 00:24:06.649: INFO: Pod "exec-volume-test-inlinevolume-5hkr": Phase="Pending", Reason="", readiness=false. Elapsed: 4.131147277s
Jun 10 00:24:08.695: INFO: Pod "exec-volume-test-inlinevolume-5hkr": Phase="Pending", Reason="", readiness=false. Elapsed: 6.176551244s
Jun 10 00:24:10.739: INFO: Pod "exec-volume-test-inlinevolume-5hkr": Phase="Pending", Reason="", readiness=false. Elapsed: 8.220697577s
Jun 10 00:24:12.782: INFO: Pod "exec-volume-test-inlinevolume-5hkr": Phase="Pending", Reason="", readiness=false. Elapsed: 10.264215542s
Jun 10 00:24:14.825: INFO: Pod "exec-volume-test-inlinevolume-5hkr": Phase="Pending", Reason="", readiness=false. Elapsed: 12.30709371s
Jun 10 00:24:16.868: INFO: Pod "exec-volume-test-inlinevolume-5hkr": Phase="Pending", Reason="", readiness=false. Elapsed: 14.349726887s
Jun 10 00:24:18.912: INFO: Pod "exec-volume-test-inlinevolume-5hkr": Phase="Pending", Reason="", readiness=false. Elapsed: 16.393923993s
Jun 10 00:24:20.954: INFO: Pod "exec-volume-test-inlinevolume-5hkr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.435941474s
STEP: Saw pod success
Jun 10 00:24:20.954: INFO: Pod "exec-volume-test-inlinevolume-5hkr" satisfied condition "Succeeded or Failed"
Jun 10 00:24:20.996: INFO: Trying to get logs from node ip-172-20-56-177.us-east-2.compute.internal pod exec-volume-test-inlinevolume-5hkr container exec-container-inlinevolume-5hkr: <nil>
STEP: delete the pod
Jun 10 00:24:21.086: INFO: Waiting for pod exec-volume-test-inlinevolume-5hkr to disappear
Jun 10 00:24:21.127: INFO: Pod exec-volume-test-inlinevolume-5hkr no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-5hkr
Jun 10 00:24:21.127: INFO: Deleting pod "exec-volume-test-inlinevolume-5hkr" in namespace "volume-3954"
Jun 10 00:24:21.352: INFO: Couldn't delete PD "aws://us-east-2a/vol-05d69538fe26344bb", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05d69538fe26344bb is currently attached to i-0d2e89f8b75d98870
	status code: 400, request id: a869f945-e463-4e9e-aafc-bf9e1b5158eb
Jun 10 00:24:26.673: INFO: Couldn't delete PD "aws://us-east-2a/vol-05d69538fe26344bb", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05d69538fe26344bb is currently attached to i-0d2e89f8b75d98870
	status code: 400, request id: 872e22b6-2e77-42d5-b92b-b86fd51eec4d
Jun 10 00:24:31.968: INFO: Couldn't delete PD "aws://us-east-2a/vol-05d69538fe26344bb", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05d69538fe26344bb is currently attached to i-0d2e89f8b75d98870
	status code: 400, request id: 39db5cb9-9d0d-43dd-b788-cec3cb3d63c6
Jun 10 00:24:37.269: INFO: Couldn't delete PD "aws://us-east-2a/vol-05d69538fe26344bb", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05d69538fe26344bb is currently attached to i-0d2e89f8b75d98870
	status code: 400, request id: 10797533-65cc-463b-a726-4adac8e7d59d
Jun 10 00:24:42.564: INFO: Couldn't delete PD "aws://us-east-2a/vol-05d69538fe26344bb", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-05d69538fe26344bb is currently attached to i-0d2e89f8b75d98870
	status code: 400, request id: 76d95aa7-0fc6-4dcd-ba26-c34c45d42f5b
Jun 10 00:24:47.904: INFO: Successfully deleted PD "aws://us-east-2a/vol-05d69538fe26344bb".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 10 00:24:47.904: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-3954" for this suite.
... skipping 157 lines ...
Jun 10 00:24:50.165: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 84 lines ...
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 00:24:50.174: 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.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Jun 10 00:24:50.429: INFO: found topology map[topology.kubernetes.io/zone:us-east-2a]
Jun 10 00:24:50.429: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 10 00:24:50.429: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Ze8yNfZ8r/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Ze8yNfZ8r/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (immediate binding)] topology
    /tmp/kops.Ze8yNfZ8r/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.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 2 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 00:24:04.614: 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.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun 10 00:24:04.834: INFO: Creating resource for dynamic PV
Jun 10 00:24:04.834: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9701-e2e-scjq22j
STEP: creating a claim
Jun 10 00:24:04.878: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-t2cm
STEP: Checking for subpath error in container status
Jun 10 00:24:19.099: INFO: Deleting pod "pod-subpath-test-dynamicpv-t2cm" in namespace "provisioning-9701"
Jun 10 00:24:19.141: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-t2cm" to be fully deleted
STEP: Deleting pod
Jun 10 00:24:33.224: INFO: Deleting pod "pod-subpath-test-dynamicpv-t2cm" in namespace "provisioning-9701"
STEP: Deleting pvc
Jun 10 00:24:33.349: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comfrqwd"
... skipping 12 lines ...

• [SLOW TEST:49.139 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.Ze8yNfZ8r/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.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
... skipping 115 lines ...
Jun 10 00:23:48.690: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-7340mw7t6      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-7340    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-7340mw7t6,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-7340    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-7340mw7t6,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-7340    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-7340mw7t6,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-7340mw7t6    ad727c08-fb89-4318-9ad4-b7f7e9c461ae 10111 0 2021-06-10 00:23:48 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-10 00:23:48 +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-rnwnx pvc- provisioning-7340  337ec396-ed80-40ad-8009-441f030e2310 10121 0 2021-06-10 00:23:48 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-10 00:23:48 +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-7340mw7t6,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-40d4b7b3-bcea-4be1-acc5-4097bab33ecb in namespace provisioning-7340
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun 10 00:24:03.188: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-cd8hd" in namespace "provisioning-7340" to be "Succeeded or Failed"
Jun 10 00:24:03.231: INFO: Pod "pvc-volume-tester-writer-cd8hd": Phase="Pending", Reason="", readiness=false. Elapsed: 43.766813ms
Jun 10 00:24:05.278: INFO: Pod "pvc-volume-tester-writer-cd8hd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.090499067s
Jun 10 00:24:07.322: INFO: Pod "pvc-volume-tester-writer-cd8hd": Phase="Pending", Reason="", readiness=false. Elapsed: 4.133953579s
Jun 10 00:24:09.365: INFO: Pod "pvc-volume-tester-writer-cd8hd": Phase="Pending", Reason="", readiness=false. Elapsed: 6.176975145s
Jun 10 00:24:11.409: INFO: Pod "pvc-volume-tester-writer-cd8hd": Phase="Pending", Reason="", readiness=false. Elapsed: 8.22141625s
Jun 10 00:24:13.452: INFO: Pod "pvc-volume-tester-writer-cd8hd": Phase="Pending", Reason="", readiness=false. Elapsed: 10.264498242s
... skipping 7 lines ...
Jun 10 00:24:29.806: INFO: Pod "pvc-volume-tester-writer-cd8hd": Phase="Pending", Reason="", readiness=false. Elapsed: 26.618607572s
Jun 10 00:24:31.852: INFO: Pod "pvc-volume-tester-writer-cd8hd": Phase="Pending", Reason="", readiness=false. Elapsed: 28.664922381s
Jun 10 00:24:33.897: INFO: Pod "pvc-volume-tester-writer-cd8hd": Phase="Pending", Reason="", readiness=false. Elapsed: 30.709654332s
Jun 10 00:24:35.940: INFO: Pod "pvc-volume-tester-writer-cd8hd": Phase="Pending", Reason="", readiness=false. Elapsed: 32.75281216s
Jun 10 00:24:37.983: INFO: Pod "pvc-volume-tester-writer-cd8hd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.795881308s
STEP: Saw pod success
Jun 10 00:24:37.984: INFO: Pod "pvc-volume-tester-writer-cd8hd" satisfied condition "Succeeded or Failed"
Jun 10 00:24:38.089: INFO: Pod pvc-volume-tester-writer-cd8hd has the following logs: 
Jun 10 00:24:38.089: INFO: Deleting pod "pvc-volume-tester-writer-cd8hd" in namespace "provisioning-7340"
Jun 10 00:24:38.141: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-cd8hd" to be fully deleted
STEP: checking the created volume has the correct mount options, is readable and retains data on the same node "ip-172-20-37-21.us-east-2.compute.internal"
Jun 10 00:24:38.317: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-hqt4q" in namespace "provisioning-7340" to be "Succeeded or Failed"
Jun 10 00:24:38.360: INFO: Pod "pvc-volume-tester-reader-hqt4q": Phase="Pending", Reason="", readiness=false. Elapsed: 42.294163ms
Jun 10 00:24:40.404: INFO: Pod "pvc-volume-tester-reader-hqt4q": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.086321473s
STEP: Saw pod success
Jun 10 00:24:40.404: INFO: Pod "pvc-volume-tester-reader-hqt4q" satisfied condition "Succeeded or Failed"
Jun 10 00:24:40.522: INFO: Pod pvc-volume-tester-reader-hqt4q has the following logs: hello world

Jun 10 00:24:40.522: INFO: Deleting pod "pvc-volume-tester-reader-hqt4q" in namespace "provisioning-7340"
Jun 10 00:24:40.572: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-hqt4q" to be fully deleted
Jun 10 00:24:40.614: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-rnwnx] to have phase Bound
Jun 10 00:24:40.657: INFO: PersistentVolumeClaim pvc-rnwnx found and phase=Bound (42.609923ms)
... skipping 178 lines ...
Jun 10 00:24:30.248: INFO: Creating resource for dynamic PV
Jun 10 00:24:30.248: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-3465-e2e-scdqltp
STEP: creating a claim
STEP: Expanding non-expandable pvc
Jun 10 00:24:30.377: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun 10 00:24:30.460: INFO: Error updating pvc ebs.csi.aws.com7fnwd: PersistentVolumeClaim "ebs.csi.aws.com7fnwd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-3465-e2e-scdqltp",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Jun 10 00:25:00.628: INFO: Error updating pvc ebs.csi.aws.com7fnwd: PersistentVolumeClaim "ebs.csi.aws.com7fnwd" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 53 lines ...

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

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

    /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:92
------------------------------
... skipping 342 lines ...
Jun 10 00:23:29.970: INFO: Creating resource for dynamic PV
Jun 10 00:23:29.970: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-1132-e2e-sc47kzs
STEP: creating a claim
Jun 10 00:23:30.012: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 10 00:23:30.139: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-2f988" in namespace "snapshotting-1132" to be "Succeeded or Failed"
Jun 10 00:23:30.192: INFO: Pod "pvc-snapshottable-tester-2f988": Phase="Pending", Reason="", readiness=false. Elapsed: 53.439002ms
Jun 10 00:23:32.233: INFO: Pod "pvc-snapshottable-tester-2f988": Phase="Pending", Reason="", readiness=false. Elapsed: 2.094434449s
Jun 10 00:23:34.275: INFO: Pod "pvc-snapshottable-tester-2f988": Phase="Pending", Reason="", readiness=false. Elapsed: 4.135795995s
Jun 10 00:23:36.316: INFO: Pod "pvc-snapshottable-tester-2f988": Phase="Pending", Reason="", readiness=false. Elapsed: 6.177071026s
Jun 10 00:23:38.357: INFO: Pod "pvc-snapshottable-tester-2f988": Phase="Pending", Reason="", readiness=false. Elapsed: 8.218609523s
Jun 10 00:23:40.400: INFO: Pod "pvc-snapshottable-tester-2f988": Phase="Pending", Reason="", readiness=false. Elapsed: 10.261004001s
Jun 10 00:23:42.442: INFO: Pod "pvc-snapshottable-tester-2f988": Phase="Pending", Reason="", readiness=false. Elapsed: 12.303177673s
Jun 10 00:23:44.484: INFO: Pod "pvc-snapshottable-tester-2f988": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.34521277s
STEP: Saw pod success
Jun 10 00:23:44.484: INFO: Pod "pvc-snapshottable-tester-2f988" satisfied condition "Succeeded or Failed"
Jun 10 00:23:44.576: INFO: Pod pvc-snapshottable-tester-2f988 has the following logs: 
Jun 10 00:23:44.576: INFO: Deleting pod "pvc-snapshottable-tester-2f988" in namespace "snapshotting-1132"
Jun 10 00:23:44.647: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-2f988" to be fully deleted
Jun 10 00:23:44.691: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comz99m2] to have phase Bound
Jun 10 00:23:44.733: INFO: PersistentVolumeClaim ebs.csi.aws.comz99m2 found and phase=Bound (42.58993ms)
STEP: [init] checking the claim
... skipping 33 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.Ze8yNfZ8r/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 10 00:23:55.842: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-2dj6w" in namespace "snapshotting-1132" to be "Succeeded or Failed"
Jun 10 00:23:55.884: INFO: Pod "pvc-snapshottable-data-tester-2dj6w": Phase="Pending", Reason="", readiness=false. Elapsed: 41.082713ms
Jun 10 00:23:57.925: INFO: Pod "pvc-snapshottable-data-tester-2dj6w": Phase="Pending", Reason="", readiness=false. Elapsed: 2.0830747s
Jun 10 00:23:59.967: INFO: Pod "pvc-snapshottable-data-tester-2dj6w": Phase="Pending", Reason="", readiness=false. Elapsed: 4.1242199s
Jun 10 00:24:02.008: INFO: Pod "pvc-snapshottable-data-tester-2dj6w": Phase="Pending", Reason="", readiness=false. Elapsed: 6.16542327s
Jun 10 00:24:04.050: INFO: Pod "pvc-snapshottable-data-tester-2dj6w": Phase="Pending", Reason="", readiness=false. Elapsed: 8.208061176s
Jun 10 00:24:06.093: INFO: Pod "pvc-snapshottable-data-tester-2dj6w": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.250936045s
STEP: Saw pod success
Jun 10 00:24:06.093: INFO: Pod "pvc-snapshottable-data-tester-2dj6w" satisfied condition "Succeeded or Failed"
Jun 10 00:24:06.177: INFO: Pod pvc-snapshottable-data-tester-2dj6w has the following logs: 
Jun 10 00:24:06.177: INFO: Deleting pod "pvc-snapshottable-data-tester-2dj6w" in namespace "snapshotting-1132"
Jun 10 00:24:06.223: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-2dj6w" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 10 00:24:28.430: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-1132 exec restored-pvc-tester-82ggx --namespace=snapshotting-1132 -- cat /mnt/test/data'
... skipping 259 lines ...
    /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:108
      
      /tmp/kops.Ze8yNfZ8r/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.Ze8yNfZ8r/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-1132 exec restored-pvc-tester-82ggx --namespace=snapshotting-1132 -- 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-1132 exec restored-pvc-tester-82ggx --namespace=snapshotting-1132 -- 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.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:602
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeLimits
... skipping 77 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.Ze8yNfZ8r/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.Ze8yNfZ8r/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.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 87 lines ...
STEP: Deleting pod hostexec-ip-172-20-37-21.us-east-2.compute.internal-pz8cz in namespace volumemode-4793
Jun 10 00:25:05.255: INFO: Deleting pod "pod-4b3ec834-3519-4eb0-8b42-9c519d503e27" in namespace "volumemode-4793"
Jun 10 00:25:05.298: INFO: Wait up to 5m0s for pod "pod-4b3ec834-3519-4eb0-8b42-9c519d503e27" to be fully deleted
STEP: Deleting pv and pvc
Jun 10 00:25:19.386: INFO: Deleting PersistentVolumeClaim "pvc-lk29t"
Jun 10 00:25:19.429: INFO: Deleting PersistentVolume "aws-4664r"
Jun 10 00:25:19.689: INFO: Couldn't delete PD "aws://us-east-2a/vol-019ec1139c017c103", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-019ec1139c017c103 is currently attached to i-06f8a1a98a822b359
	status code: 400, request id: c18b2e34-b1b1-48bf-9eb9-20109b7b361b
Jun 10 00:25:25.047: INFO: Successfully deleted PD "aws://us-east-2a/vol-019ec1139c017c103".
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 10 00:25:25.048: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-4793" for this suite.
... skipping 110 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Ze8yNfZ8r/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Ze8yNfZ8r/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.Ze8yNfZ8r/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.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 146 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 00:24:56.784: 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.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 10 00:24:56.999: INFO: Creating resource for dynamic PV
Jun 10 00:24:56.999: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-7446-e2e-sc8vffr
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 10 00:25:03.305: INFO: Deleting pod "pod-dffd3913-f2ae-4635-b6a8-572e1033faf0" in namespace "volumemode-7446"
Jun 10 00:25:03.351: INFO: Wait up to 5m0s for pod "pod-dffd3913-f2ae-4635-b6a8-572e1033faf0" to be fully deleted
STEP: Deleting pvc
Jun 10 00:25:07.523: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comh98j8"
Jun 10 00:25:07.567: INFO: Waiting up to 5m0s for PersistentVolume pvc-06ac82a0-69f4-437f-a203-e64044ef6bcb to get deleted
Jun 10 00:25:07.610: INFO: PersistentVolume pvc-06ac82a0-69f4-437f-a203-e64044ef6bcb found and phase=Released (42.852617ms)
... skipping 13 lines ...

• [SLOW TEST:46.260 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.Ze8yNfZ8r/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.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 10 00:25:43.046: INFO: Driver "ebs.csi.aws.com" does not support volume type "InlineVolume" - skipping
[AfterEach] [Testpattern: Inline-volume (default fs)] subPath
... skipping 27 lines ...
Jun 10 00:24:48.209: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9788ndpk7
STEP: creating a claim
Jun 10 00:24:48.252: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-wlx9
STEP: Creating a pod to test subpath
Jun 10 00:24:48.390: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-wlx9" in namespace "provisioning-9788" to be "Succeeded or Failed"
Jun 10 00:24:48.433: INFO: Pod "pod-subpath-test-dynamicpv-wlx9": Phase="Pending", Reason="", readiness=false. Elapsed: 43.062598ms
Jun 10 00:24:50.476: INFO: Pod "pod-subpath-test-dynamicpv-wlx9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.086204305s
Jun 10 00:24:52.520: INFO: Pod "pod-subpath-test-dynamicpv-wlx9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.129743817s
Jun 10 00:24:54.564: INFO: Pod "pod-subpath-test-dynamicpv-wlx9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.173427732s
Jun 10 00:24:56.608: INFO: Pod "pod-subpath-test-dynamicpv-wlx9": Phase="Pending", Reason="", readiness=false. Elapsed: 8.217850311s
Jun 10 00:24:58.652: INFO: Pod "pod-subpath-test-dynamicpv-wlx9": Phase="Pending", Reason="", readiness=false. Elapsed: 10.262049127s
Jun 10 00:25:00.696: INFO: Pod "pod-subpath-test-dynamicpv-wlx9": Phase="Pending", Reason="", readiness=false. Elapsed: 12.305791441s
Jun 10 00:25:02.739: INFO: Pod "pod-subpath-test-dynamicpv-wlx9": Phase="Pending", Reason="", readiness=false. Elapsed: 14.349199562s
Jun 10 00:25:04.785: INFO: Pod "pod-subpath-test-dynamicpv-wlx9": Phase="Pending", Reason="", readiness=false. Elapsed: 16.395182318s
Jun 10 00:25:06.830: INFO: Pod "pod-subpath-test-dynamicpv-wlx9": Phase="Pending", Reason="", readiness=false. Elapsed: 18.439305375s
Jun 10 00:25:08.873: INFO: Pod "pod-subpath-test-dynamicpv-wlx9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.48326724s
STEP: Saw pod success
Jun 10 00:25:08.874: INFO: Pod "pod-subpath-test-dynamicpv-wlx9" satisfied condition "Succeeded or Failed"
Jun 10 00:25:08.917: INFO: Trying to get logs from node ip-172-20-40-185.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-wlx9 container test-container-subpath-dynamicpv-wlx9: <nil>
STEP: delete the pod
Jun 10 00:25:09.224: INFO: Waiting for pod pod-subpath-test-dynamicpv-wlx9 to disappear
Jun 10 00:25:09.267: INFO: Pod pod-subpath-test-dynamicpv-wlx9 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-wlx9
Jun 10 00:25:09.267: INFO: Deleting pod "pod-subpath-test-dynamicpv-wlx9" in namespace "provisioning-9788"
... skipping 161 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 00:25:02.710: 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.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun 10 00:25:02.917: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 10 00:25:02.917: INFO: Creating resource for dynamic PV
Jun 10 00:25:02.917: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2733dbmrt
STEP: creating a claim
Jun 10 00:25:02.976: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-v6gw
STEP: Checking for subpath error in container status
Jun 10 00:25:19.193: INFO: Deleting pod "pod-subpath-test-dynamicpv-v6gw" in namespace "provisioning-2733"
Jun 10 00:25:19.236: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-v6gw" to be fully deleted
STEP: Deleting pod
Jun 10 00:25:29.319: INFO: Deleting pod "pod-subpath-test-dynamicpv-v6gw" in namespace "provisioning-2733"
STEP: Deleting pvc
Jun 10 00:25:29.444: INFO: Deleting PersistentVolumeClaim "awspg465"
... skipping 14 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Ze8yNfZ8r/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Ze8yNfZ8r/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath file is outside the volume [Slow][LinuxOnly]
      /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
SS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
... skipping 6 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Ze8yNfZ8r/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Ze8yNfZ8r/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    /tmp/kops.Ze8yNfZ8r/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.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 11 lines ...
Jun 10 00:24:59.839: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-6169-e2e-sc6pmql
STEP: creating a claim
Jun 10 00:24:59.883: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-th4s
STEP: Creating a pod to test exec-volume-test
Jun 10 00:25:00.031: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-th4s" in namespace "volume-6169" to be "Succeeded or Failed"
Jun 10 00:25:00.073: INFO: Pod "exec-volume-test-dynamicpv-th4s": Phase="Pending", Reason="", readiness=false. Elapsed: 42.225997ms
Jun 10 00:25:02.117: INFO: Pod "exec-volume-test-dynamicpv-th4s": Phase="Pending", Reason="", readiness=false. Elapsed: 2.085672053s
Jun 10 00:25:04.159: INFO: Pod "exec-volume-test-dynamicpv-th4s": Phase="Pending", Reason="", readiness=false. Elapsed: 4.128217292s
Jun 10 00:25:06.204: INFO: Pod "exec-volume-test-dynamicpv-th4s": Phase="Pending", Reason="", readiness=false. Elapsed: 6.173158103s
Jun 10 00:25:08.248: INFO: Pod "exec-volume-test-dynamicpv-th4s": Phase="Pending", Reason="", readiness=false. Elapsed: 8.217271444s
Jun 10 00:25:10.291: INFO: Pod "exec-volume-test-dynamicpv-th4s": Phase="Pending", Reason="", readiness=false. Elapsed: 10.26031549s
Jun 10 00:25:12.333: INFO: Pod "exec-volume-test-dynamicpv-th4s": Phase="Pending", Reason="", readiness=false. Elapsed: 12.302306744s
Jun 10 00:25:14.379: INFO: Pod "exec-volume-test-dynamicpv-th4s": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.347551786s
STEP: Saw pod success
Jun 10 00:25:14.379: INFO: Pod "exec-volume-test-dynamicpv-th4s" satisfied condition "Succeeded or Failed"
Jun 10 00:25:14.420: INFO: Trying to get logs from node ip-172-20-56-177.us-east-2.compute.internal pod exec-volume-test-dynamicpv-th4s container exec-container-dynamicpv-th4s: <nil>
STEP: delete the pod
Jun 10 00:25:14.518: INFO: Waiting for pod exec-volume-test-dynamicpv-th4s to disappear
Jun 10 00:25:14.560: INFO: Pod exec-volume-test-dynamicpv-th4s no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-th4s
Jun 10 00:25:14.560: INFO: Deleting pod "exec-volume-test-dynamicpv-th4s" in namespace "volume-6169"
... skipping 102 lines ...
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 00:25:01.157: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename volumemode
Jun 10 00:25:01.206: INFO: Namespace name "volumemode-8096" was already taken, generate a new name and retry
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.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 10 00:25:03.415: INFO: Creating resource for dynamic PV
Jun 10 00:25:03.415: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-3571-e2e-sct7dlh
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 10 00:25:11.710: INFO: Deleting pod "pod-b3776729-8162-4a43-8a18-a7493f5b1252" in namespace "volumemode-3571"
Jun 10 00:25:11.753: INFO: Wait up to 5m0s for pod "pod-b3776729-8162-4a43-8a18-a7493f5b1252" to be fully deleted
STEP: Deleting pvc
Jun 10 00:25:17.922: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comcx2xn"
Jun 10 00:25:17.964: INFO: Waiting up to 5m0s for PersistentVolume pvc-a1676a05-73f1-494c-8f24-1a62cda322f0 to get deleted
Jun 10 00:25:18.006: INFO: PersistentVolume pvc-a1676a05-73f1-494c-8f24-1a62cda322f0 found and phase=Released (41.260584ms)
... skipping 13 lines ...

• [SLOW TEST:52.288 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.Ze8yNfZ8r/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.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] capacity
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
... skipping 40 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 00:25:10.496: 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.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun 10 00:25:10.702: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 10 00:25:10.702: INFO: Creating resource for dynamic PV
Jun 10 00:25:10.703: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8645tz4h7
STEP: creating a claim
Jun 10 00:25:10.745: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-lm8c
STEP: Checking for subpath error in container status
Jun 10 00:25:32.962: INFO: Deleting pod "pod-subpath-test-dynamicpv-lm8c" in namespace "provisioning-8645"
Jun 10 00:25:33.006: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-lm8c" to be fully deleted
STEP: Deleting pod
Jun 10 00:25:49.113: INFO: Deleting pod "pod-subpath-test-dynamicpv-lm8c" in namespace "provisioning-8645"
STEP: Deleting pvc
Jun 10 00:25:49.236: INFO: Deleting PersistentVolumeClaim "awsclktr"
... skipping 11 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Ze8yNfZ8r/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Ze8yNfZ8r/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath directory is outside the volume [Slow][LinuxOnly]
      /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)(allowExpansion)][Feature:Windows] volume-expand
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 10 00:25:54.500: INFO: Driver ebs.csi.aws.com doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)(allowExpansion)][Feature:Windows] volume-expand
... skipping 139 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 00:25:21.719: 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.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun 10 00:25:21.936: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 10 00:25:21.936: INFO: Creating resource for dynamic PV
Jun 10 00:25:21.937: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5732bsgrw
STEP: creating a claim
Jun 10 00:25:21.979: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-ps7z
STEP: Checking for subpath error in container status
Jun 10 00:25:36.189: INFO: Deleting pod "pod-subpath-test-dynamicpv-ps7z" in namespace "provisioning-5732"
Jun 10 00:25:36.233: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-ps7z" to be fully deleted
STEP: Deleting pod
Jun 10 00:25:50.315: INFO: Deleting pod "pod-subpath-test-dynamicpv-ps7z" in namespace "provisioning-5732"
STEP: Deleting pvc
Jun 10 00:25:50.438: INFO: Deleting PersistentVolumeClaim "awsvz67m"
... skipping 11 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Ze8yNfZ8r/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Ze8yNfZ8r/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.Ze8yNfZ8r/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.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow]
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 10 00:25:55.699: INFO: Driver supports dynamic provisioning, skipping PreprovisionedPV pattern
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow]
... skipping 118 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 00:25:25.134: 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.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 10 00:25:25.341: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 10 00:25:25.341: INFO: Creating resource for dynamic PV
Jun 10 00:25:25.341: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-4257np2qc
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 10 00:25:31.641: INFO: Deleting pod "pod-c093c343-ab8b-43f3-ae02-a566ccb4b18b" in namespace "volumemode-4257"
Jun 10 00:25:31.685: INFO: Wait up to 5m0s for pod "pod-c093c343-ab8b-43f3-ae02-a566ccb4b18b" to be fully deleted
STEP: Deleting pvc
Jun 10 00:25:41.873: INFO: Deleting PersistentVolumeClaim "awsg2qp2"
Jun 10 00:25:41.916: INFO: Waiting up to 5m0s for PersistentVolume pvc-8b12465c-a1b6-41d0-acee-d16557c58baf to get deleted
Jun 10 00:25:41.957: INFO: PersistentVolume pvc-8b12465c-a1b6-41d0-acee-d16557c58baf found and phase=Released (40.673124ms)
... skipping 11 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Ze8yNfZ8r/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Ze8yNfZ8r/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
    /tmp/kops.Ze8yNfZ8r/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.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 10 00:25:57.220: INFO: Driver ebs.csi.aws.com doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
... skipping 409 lines ...
Jun 10 00:25:48.573: INFO: Pod aws-client still exists
Jun 10 00:25:50.530: INFO: Waiting for pod aws-client to disappear
Jun 10 00:25:50.574: INFO: Pod aws-client still exists
Jun 10 00:25:52.530: INFO: Waiting for pod aws-client to disappear
Jun 10 00:25:52.572: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun 10 00:25:52.894: INFO: Couldn't delete PD "aws://us-east-2a/vol-0b407f6877eed9241", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0b407f6877eed9241 is currently attached to i-0a2e25b9d9c987751
	status code: 400, request id: f7955cbb-fbb5-46bb-ab5e-1394e5984b0b
Jun 10 00:25:58.218: INFO: Couldn't delete PD "aws://us-east-2a/vol-0b407f6877eed9241", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0b407f6877eed9241 is currently attached to i-0a2e25b9d9c987751
	status code: 400, request id: e842f035-972d-4f78-8d33-467c83a2159f
Jun 10 00:26:03.546: INFO: Couldn't delete PD "aws://us-east-2a/vol-0b407f6877eed9241", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0b407f6877eed9241 is currently attached to i-0a2e25b9d9c987751
	status code: 400, request id: a134ac75-4c05-46f2-be16-3998a2652d51
Jun 10 00:26:08.871: INFO: Successfully deleted PD "aws://us-east-2a/vol-0b407f6877eed9241".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 10 00:26:08.871: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-4873" for this suite.
... skipping 79 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 00:25:02.812: 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.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun 10 00:25:03.021: INFO: Creating resource for dynamic PV
Jun 10 00:25:03.021: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-20-e2e-scrnxd5
STEP: creating a claim
Jun 10 00:25:03.065: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-gtx5
STEP: Checking for subpath error in container status
Jun 10 00:25:27.285: INFO: Deleting pod "pod-subpath-test-dynamicpv-gtx5" in namespace "provisioning-20"
Jun 10 00:25:27.328: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-gtx5" to be fully deleted
STEP: Deleting pod
Jun 10 00:25:33.413: INFO: Deleting pod "pod-subpath-test-dynamicpv-gtx5" in namespace "provisioning-20"
STEP: Deleting pvc
Jun 10 00:25:33.541: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com49t4k"
... skipping 15 lines ...

• [SLOW TEST:66.246 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.Ze8yNfZ8r/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.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun 10 00:26:09.060: INFO: Distro debian doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
... skipping 54 lines ...
Jun 10 00:25:37.580: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-771479ckh
STEP: creating a claim
Jun 10 00:25:37.622: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-mzqj
STEP: Creating a pod to test subpath
Jun 10 00:25:37.753: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-mzqj" in namespace "provisioning-7714" to be "Succeeded or Failed"
Jun 10 00:25:37.795: INFO: Pod "pod-subpath-test-dynamicpv-mzqj": Phase="Pending", Reason="", readiness=false. Elapsed: 41.622844ms
Jun 10 00:25:39.838: INFO: Pod "pod-subpath-test-dynamicpv-mzqj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.084052657s
Jun 10 00:25:41.881: INFO: Pod "pod-subpath-test-dynamicpv-mzqj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.127696956s
Jun 10 00:25:43.924: INFO: Pod "pod-subpath-test-dynamicpv-mzqj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.170149891s
Jun 10 00:25:45.966: INFO: Pod "pod-subpath-test-dynamicpv-mzqj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.212572201s
Jun 10 00:25:48.009: INFO: Pod "pod-subpath-test-dynamicpv-mzqj": Phase="Pending", Reason="", readiness=false. Elapsed: 10.255555889s
Jun 10 00:25:50.053: INFO: Pod "pod-subpath-test-dynamicpv-mzqj": Phase="Pending", Reason="", readiness=false. Elapsed: 12.299223084s
Jun 10 00:25:52.096: INFO: Pod "pod-subpath-test-dynamicpv-mzqj": Phase="Pending", Reason="", readiness=false. Elapsed: 14.342333344s
Jun 10 00:25:54.139: INFO: Pod "pod-subpath-test-dynamicpv-mzqj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.385460101s
STEP: Saw pod success
Jun 10 00:25:54.139: INFO: Pod "pod-subpath-test-dynamicpv-mzqj" satisfied condition "Succeeded or Failed"
Jun 10 00:25:54.181: INFO: Trying to get logs from node ip-172-20-40-185.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-mzqj container test-container-subpath-dynamicpv-mzqj: <nil>
STEP: delete the pod
Jun 10 00:25:54.271: INFO: Waiting for pod pod-subpath-test-dynamicpv-mzqj to disappear
Jun 10 00:25:54.313: INFO: Pod pod-subpath-test-dynamicpv-mzqj no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-mzqj
Jun 10 00:25:54.313: INFO: Deleting pod "pod-subpath-test-dynamicpv-mzqj" in namespace "provisioning-7714"
... skipping 338 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 00:25:57.224: 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.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun 10 00:25:57.431: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 10 00:25:57.431: INFO: Creating resource for dynamic PV
Jun 10 00:25:57.431: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-99778d6q4
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun 10 00:26:01.726: INFO: Deleting pod "pod-fb70aa9e-689a-4878-a41c-ab635631dfda" in namespace "volumemode-9977"
Jun 10 00:26:01.770: INFO: Wait up to 5m0s for pod "pod-fb70aa9e-689a-4878-a41c-ab635631dfda" to be fully deleted
STEP: Deleting pvc
Jun 10 00:26:11.941: INFO: Deleting PersistentVolumeClaim "awsk6zzf"
Jun 10 00:26:11.983: INFO: Waiting up to 5m0s for PersistentVolume pvc-ebfe9554-ebdd-4459-ac5d-3d911b091dcf to get deleted
Jun 10 00:26:12.024: INFO: PersistentVolume pvc-ebfe9554-ebdd-4459-ac5d-3d911b091dcf found and phase=Released (41.018957ms)
... skipping 10 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Ze8yNfZ8r/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Ze8yNfZ8r/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (block volmode)] volumeMode
    /tmp/kops.Ze8yNfZ8r/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.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 208 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun 10 00:25:49.836: 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.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun 10 00:25:50.044: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun 10 00:25:50.044: INFO: Creating resource for dynamic PV
Jun 10 00:25:50.044: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-508jhfd4
STEP: creating a claim
Jun 10 00:25:50.086: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-56wm
STEP: Checking for subpath error in container status
Jun 10 00:26:04.303: INFO: Deleting pod "pod-subpath-test-dynamicpv-56wm" in namespace "provisioning-508"
Jun 10 00:26:04.350: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-56wm" to be fully deleted
STEP: Deleting pod
Jun 10 00:26:18.434: INFO: Deleting pod "pod-subpath-test-dynamicpv-56wm" in namespace "provisioning-508"
STEP: Deleting pvc
Jun 10 00:26:18.562: INFO: Deleting PersistentVolumeClaim "aws7c6w6"
... skipping 12 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.Ze8yNfZ8r/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.Ze8yNfZ8r/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.Ze8yNfZ8r/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.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 6 lines ...
Jun 10 00:25:43.284: INFO: Creating resource for dynamic PV
Jun 10 00:25:43.284: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5903-e2e-scvxdst
STEP: creating a claim
Jun 10 00:25:43.330: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-5903
Jun 10 00:25:43.464: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-5903" in namespace "provisioning-5903" to be "Succeeded or Failed"
Jun 10 00:25:43.506: INFO: Pod "volume-prep-provisioning-5903": Phase="Pending", Reason="", readiness=false. Elapsed: 42.582605ms
Jun 10 00:25:45.549: INFO: Pod "volume-prep-provisioning-5903": Phase="Pending", Reason="", readiness=false. Elapsed: 2.085708328s
Jun 10 00:25:47.593: INFO: Pod "volume-prep-provisioning-5903": Phase="Pending", Reason="", readiness=false. Elapsed: 4.129165958s
Jun 10 00:25:49.636: INFO: Pod "volume-prep-provisioning-5903": Phase="Pending", Reason="", readiness=false. Elapsed: 6.172192434s
Jun 10 00:25:51.679: INFO: Pod "volume-prep-provisioning-5903": Phase="Pending", Reason="", readiness=false. Elapsed: 8.215433777s
Jun 10 00:25:53.723: INFO: Pod "volume-prep-provisioning-5903": Phase="Pending", Reason="", readiness=false. Elapsed: 10.258944181s
Jun 10 00:25:55.773: INFO: Pod "volume-prep-provisioning-5903": Phase="Pending", Reason="", readiness=false. Elapsed: 12.309363045s
Jun 10 00:25:57.818: INFO: Pod "volume-prep-provisioning-5903": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.354104074s
STEP: Saw pod success
Jun 10 00:25:57.818: INFO: Pod "volume-prep-provisioning-5903" satisfied condition "Succeeded or Failed"
Jun 10 00:25:57.818: INFO: Deleting pod "volume-prep-provisioning-5903" in namespace "provisioning-5903"
Jun 10 00:25:57.868: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-5903" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-ktb5
STEP: Checking for subpath error in container status
Jun 10 00:26:00.044: INFO: Deleting pod "pod-subpath-test-dynamicpv-ktb5" in namespace "provisioning-5903"
Jun 10 00:26:00.093: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-ktb5" to be fully deleted
STEP: Deleting pod
Jun 10 00:26:00.135: INFO: Deleting pod "pod-subpath-test-dynamicpv-ktb5" in namespace "provisioning-5903"
STEP: Deleting pvc
Jun 10 00:26:00.265: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comggr45"
... skipping 160 lines ...
Jun 10 00:26:08.224: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-1564zlb45
STEP: creating a claim
Jun 10 00:26:08.269: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-t8q4
STEP: Creating a pod to test exec-volume-test
Jun 10 00:26:08.398: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-t8q4" in namespace "volume-1564" to be "Succeeded or Failed"
Jun 10 00:26:08.440: INFO: Pod "exec-volume-test-dynamicpv-t8q4": Phase="Pending", Reason="", readiness=false. Elapsed: 41.531933ms
Jun 10 00:26:10.481: INFO: Pod "exec-volume-test-dynamicpv-t8q4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.083380265s
Jun 10 00:26:12.523: INFO: Pod "exec-volume-test-dynamicpv-t8q4": Phase="Pending", Reason="", readiness=false. Elapsed: 4.125035375s
Jun 10 00:26:14.567: INFO: Pod "exec-volume-test-dynamicpv-t8q4": Phase="Pending", Reason="", readiness=false. Elapsed: 6.169025951s
Jun 10 00:26:16.612: INFO: Pod "exec-volume-test-dynamicpv-t8q4": Phase="Pending", Reason="", readiness=false. Elapsed: 8.213638421s
Jun 10 00:26:18.654: INFO: Pod "exec-volume-test-dynamicpv-t8q4": Phase="Pending", Reason="", readiness=false. Elapsed: 10.255535333s
Jun 10 00:26:20.697: INFO: Pod "exec-volume-test-dynamicpv-t8q4": Phase="Pending", Reason="", readiness=false. Elapsed: 12.298632039s
Jun 10 00:26:22.740: INFO: Pod "exec-volume-test-dynamicpv-t8q4": Phase="Pending", Reason="", readiness=false. Elapsed: 14.341477083s
Jun 10 00:26:24.783: INFO: Pod "exec-volume-test-dynamicpv-t8q4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.384856705s
STEP: Saw pod success
Jun 10 00:26:24.783: INFO: Pod "exec-volume-test-dynamicpv-t8q4" satisfied condition "Succeeded or Failed"
Jun 10 00:26:24.828: INFO: Trying to get logs from node ip-172-20-53-235.us-east-2.compute.internal pod exec-volume-test-dynamicpv-t8q4 container exec-container-dynamicpv-t8q4: <nil>
STEP: delete the pod
Jun 10 00:26:24.924: INFO: Waiting for pod exec-volume-test-dynamicpv-t8q4 to disappear
Jun 10 00:26:24.965: INFO: Pod exec-volume-test-dynamicpv-t8q4 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-t8q4
Jun 10 00:26:24.965: INFO: Deleting pod "exec-volume-test-dynamicpv-t8q4" in namespace "volume-1564"
... skipping 499 lines ...
Jun 10 00:24:24.071: INFO: Creating resource for dynamic PV
Jun 10 00:24:24.071: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3433xtppm
STEP: creating a claim
Jun 10 00:24:24.115: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-3433
Jun 10 00:24:24.246: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-3433" in namespace "provisioning-3433" to be "Succeeded or Failed"
Jun 10 00:24:24.292: INFO: Pod "volume-prep-provisioning-3433": Phase="Pending", Reason="", readiness=false. Elapsed: 45.963233ms
Jun 10 00:24:26.335: INFO: Pod "volume-prep-provisioning-3433": Phase="Pending", Reason="", readiness=false. Elapsed: 2.088669358s
Jun 10 00:24:28.385: INFO: Pod "volume-prep-provisioning-3433": Phase="Pending", Reason="", readiness=false. Elapsed: 4.139022999s
Jun 10 00:24:30.427: INFO: Pod "volume-prep-provisioning-3433": Phase="Pending", Reason="", readiness=false. Elapsed: 6.180790198s
Jun 10 00:24:32.469: INFO: Pod "volume-prep-provisioning-3433": Phase="Pending", Reason="", readiness=false. Elapsed: 8.223050543s
Jun 10 00:24:34.511: INFO: Pod "volume-prep-provisioning-3433": Phase="Pending", Reason="", readiness=false. Elapsed: 10.264794006s
... skipping 24 lines ...
Jun 10 00:25:25.621: INFO: Pod "volume-prep-provisioning-3433": Phase="Pending", Reason="", readiness=false. Elapsed: 1m1.37529058s
Jun 10 00:25:27.663: INFO: Pod "volume-prep-provisioning-3433": Phase="Pending", Reason="", readiness=false. Elapsed: 1m3.417338081s
Jun 10 00:25:29.705: INFO: Pod "volume-prep-provisioning-3433": Phase="Pending", Reason="", readiness=false. Elapsed: 1m5.45928406s
Jun 10 00:25:31.747: INFO: Pod "volume-prep-provisioning-3433": Phase="Pending", Reason="", readiness=false. Elapsed: 1m7.501445144s
Jun 10 00:25:33.790: INFO: Pod "volume-prep-provisioning-3433": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m9.543959418s
STEP: Saw pod success
Jun 10 00:25:33.790: INFO: Pod "volume-prep-provisioning-3433" satisfied condition "Succeeded or Failed"
Jun 10 00:25:33.790: INFO: Deleting pod "volume-prep-provisioning-3433" in namespace "provisioning-3433"
Jun 10 00:25:33.840: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-3433" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-th8k
STEP: Checking for subpath error in container status
Jun 10 00:26:40.013: INFO: Deleting pod "pod-subpath-test-dynamicpv-th8k" in namespace "provisioning-3433"
Jun 10 00:26:40.060: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-th8k" to be fully deleted
STEP: Deleting pod
Jun 10 00:26:40.102: INFO: Deleting pod "pod-subpath-test-dynamicpv-th8k" in namespace "provisioning-3433"
STEP: Deleting pvc
Jun 10 00:26:40.231: INFO: Deleting PersistentVolumeClaim "awsfsc78"
... skipping 82 lines ...
Jun 10 00:25:55.999: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun 10 00:25:56.519: INFO: Successfully created a new PD: "aws://us-east-2a/vol-02043e7c12460d8cf".
Jun 10 00:25:56.519: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-mmsd
STEP: Creating a pod to test exec-volume-test
Jun 10 00:25:56.566: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-mmsd" in namespace "volume-7163" to be "Succeeded or Failed"
Jun 10 00:25:56.607: INFO: Pod "exec-volume-test-inlinevolume-mmsd": Phase="Pending", Reason="", readiness=false. Elapsed: 40.804779ms
Jun 10 00:25:58.650: INFO: Pod "exec-volume-test-inlinevolume-mmsd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.083113104s
Jun 10 00:26:00.691: INFO: Pod "exec-volume-test-inlinevolume-mmsd": Phase="Pending", Reason="", readiness=false. Elapsed: 4.124533559s
Jun 10 00:26:02.732: INFO: Pod "exec-volume-test-inlinevolume-mmsd": Phase="Pending", Reason="", readiness=false. Elapsed: 6.165877583s
Jun 10 00:26:04.774: INFO: Pod "exec-volume-test-inlinevolume-mmsd": Phase="Pending", Reason="", readiness=false. Elapsed: 8.207223667s
Jun 10 00:26:06.815: INFO: Pod "exec-volume-test-inlinevolume-mmsd": Phase="Pending", Reason="", readiness=false. Elapsed: 10.248879814s
... skipping 23 lines ...
Jun 10 00:26:55.838: INFO: Pod "exec-volume-test-inlinevolume-mmsd": Phase="Pending", Reason="", readiness=false. Elapsed: 59.271386746s
Jun 10 00:26:57.880: INFO: Pod "exec-volume-test-inlinevolume-mmsd": Phase="Pending", Reason="", readiness=false. Elapsed: 1m1.314051988s
Jun 10 00:26:59.923: INFO: Pod "exec-volume-test-inlinevolume-mmsd": Phase="Pending", Reason="", readiness=false. Elapsed: 1m3.356227622s
Jun 10 00:27:01.965: INFO: Pod "exec-volume-test-inlinevolume-mmsd": Phase="Pending", Reason="", readiness=false. Elapsed: 1m5.398203226s
Jun 10 00:27:04.006: INFO: Pod "exec-volume-test-inlinevolume-mmsd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m7.439480911s
STEP: Saw pod success
Jun 10 00:27:04.006: INFO: Pod "exec-volume-test-inlinevolume-mmsd" satisfied condition "Succeeded or Failed"
Jun 10 00:27:04.049: INFO: Trying to get logs from node ip-172-20-37-21.us-east-2.compute.internal pod exec-volume-test-inlinevolume-mmsd container exec-container-inlinevolume-mmsd: <nil>
STEP: delete the pod
Jun 10 00:27:04.145: INFO: Waiting for pod exec-volume-test-inlinevolume-mmsd to disappear
Jun 10 00:27:04.185: INFO: Pod exec-volume-test-inlinevolume-mmsd no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-mmsd
Jun 10 00:27:04.185: INFO: Deleting pod "exec-volume-test-inlinevolume-mmsd" in namespace "volume-7163"
Jun 10 00:27:04.552: INFO: Couldn't delete PD "aws://us-east-2a/vol-02043e7c12460d8cf", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02043e7c12460d8cf is currently attached to i-06f8a1a98a822b359
	status code: 400, request id: 776bdb5e-1792-4c4c-9e56-e9e88e17d9a2
Jun 10 00:27:09.856: INFO: Couldn't delete PD "aws://us-east-2a/vol-02043e7c12460d8cf", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-02043e7c12460d8cf is currently attached to i-06f8a1a98a822b359
	status code: 400, request id: 46ba270a-6fa7-485f-a602-5f00a5b5055f
Jun 10 00:27:15.186: INFO: Successfully deleted PD "aws://us-east-2a/vol-02043e7c12460d8cf".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun 10 00:27:15.187: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-7163" for this suite.
... skipping 84 lines ...
Jun 10 00:26:15.081: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1502-e2e-sc9qqgr
STEP: creating a claim
Jun 10 00:26:15.125: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-hpc2
STEP: Creating a pod to test subpath
Jun 10 00:26:15.255: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-hpc2" in namespace "provisioning-1502" to be "Succeeded or Failed"
Jun 10 00:26:15.296: INFO: Pod "pod-subpath-test-dynamicpv-hpc2": Phase="Pending", Reason="", readiness=false. Elapsed: 41.434214ms
Jun 10 00:26:17.339: INFO: Pod "pod-subpath-test-dynamicpv-hpc2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.084508524s
Jun 10 00:26:19.383: INFO: Pod "pod-subpath-test-dynamicpv-hpc2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.12853078s
Jun 10 00:26:21.425: INFO: Pod "pod-subpath-test-dynamicpv-hpc2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.170510642s
Jun 10 00:26:23.467: INFO: Pod "pod-subpath-test-dynamicpv-hpc2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.212881993s
Jun 10 00:26:25.511: INFO: Pod "pod-subpath-test-dynamicpv-hpc2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.256306353s
... skipping 10 lines ...
Jun 10 00:26:47.988: INFO: Pod "pod-subpath-test-dynamicpv-hpc2": Phase="Pending", Reason="", readiness=false. Elapsed: 32.733789656s
Jun 10 00:26:50.031: INFO: Pod "pod-subpath-test-dynamicpv-hpc2": Phase="Pending", Reason="", readiness=false. Elapsed: 34.776767586s
Jun 10 00:26:52.075: INFO: Pod "pod-subpath-test-dynamicpv-hpc2": Phase="Pending", Reason="", readiness=false. Elapsed: 36.820269675s
Jun 10 00:26:54.118: INFO: Pod "pod-subpath-test-dynamicpv-hpc2": Phase="Pending", Reason="", readiness=false. Elapsed: 38.863298236s
Jun 10 00:26:56.160: INFO: Pod "pod-subpath-test-dynamicpv-hpc2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 40.905704658s
STEP: Saw pod success
Jun 10 00:26:56.160: INFO: Pod "pod-subpath-test-dynamicpv-hpc2" satisfied condition "Succeeded or Failed"
Jun 10 00:26:56.202: INFO: Trying to get logs from node ip-172-20-40-185.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-hpc2 container test-container-subpath-dynamicpv-hpc2: <nil>
STEP: delete the pod
Jun 10 00:26:56.297: INFO: Waiting for pod pod-subpath-test-dynamicpv-hpc2 to disappear
Jun 10 00:26:56.339: INFO: Pod pod-subpath-test-dynamicpv-hpc2 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-hpc2
Jun 10 00:26:56.339: INFO: Deleting pod "pod-subpath-test-dynamicpv-hpc2" in namespace "provisioning-1502"
... skipping 337 lines ...
Jun 10 00:26:09.272: INFO: Creating resource for dynamic PV
Jun 10 00:26:09.272: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-3661-e2e-sc74nhs
STEP: creating a claim
Jun 10 00:26:09.315: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun 10 00:26:09.443: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-nxj66" in namespace "snapshotting-3661" to be "Succeeded or Failed"
Jun 10 00:26:09.484: INFO: Pod "pvc-snapshottable-tester-nxj66": Phase="Pending", Reason="", readiness=false. Elapsed: 41.084956ms
Jun 10 00:26:11.527: INFO: Pod "pvc-snapshottable-tester-nxj66": Phase="Pending", Reason="", readiness=false. Elapsed: 2.0834705s
Jun 10 00:26:13.569: INFO: Pod "pvc-snapshottable-tester-nxj66": Phase="Pending", Reason="", readiness=false. Elapsed: 4.125573404s
Jun 10 00:26:15.617: INFO: Pod "pvc-snapshottable-tester-nxj66": Phase="Pending", Reason="", readiness=false. Elapsed: 6.173370331s
Jun 10 00:26:17.663: INFO: Pod "pvc-snapshottable-tester-nxj66": Phase="Pending", Reason="", readiness=false. Elapsed: 8.219319651s
Jun 10 00:26:19.707: INFO: Pod "pvc-snapshottable-tester-nxj66": Phase="Pending", Reason="", readiness=false. Elapsed: 10.264162046s
Jun 10 00:26:21.750: INFO: Pod "pvc-snapshottable-tester-nxj66": Phase="Pending", Reason="", readiness=false. Elapsed: 12.306326228s
Jun 10 00:26:23.792: INFO: Pod "pvc-snapshottable-tester-nxj66": Phase="Pending", Reason="", readiness=false. Elapsed: 14.349196324s
Jun 10 00:26:25.835: INFO: Pod "pvc-snapshottable-tester-nxj66": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.3919063s
STEP: Saw pod success
Jun 10 00:26:25.835: INFO: Pod "pvc-snapshottable-tester-nxj66" satisfied condition "Succeeded or Failed"
Jun 10 00:26:25.922: INFO: Pod pvc-snapshottable-tester-nxj66 has the following logs: 
Jun 10 00:26:25.922: INFO: Deleting pod "pvc-snapshottable-tester-nxj66" in namespace "snapshotting-3661"
Jun 10 00:26:25.968: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-nxj66" to be fully deleted
Jun 10 00:26:26.009: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comrh8fn] to have phase Bound
Jun 10 00:26:26.051: INFO: PersistentVolumeClaim ebs.csi.aws.comrh8fn found and phase=Bound (41.564151ms)
STEP: [init] checking the claim
... skipping 37 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.Ze8yNfZ8r/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 10 00:27:21.724: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-vj8w9" in namespace "snapshotting-3661" to be "Succeeded or Failed"
Jun 10 00:27:21.766: INFO: Pod "pvc-snapshottable-data-tester-vj8w9": Phase="Pending", Reason="", readiness=false. Elapsed: 41.992961ms
Jun 10 00:27:23.809: INFO: Pod "pvc-snapshottable-data-tester-vj8w9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.084462887s
Jun 10 00:27:25.852: INFO: Pod "pvc-snapshottable-data-tester-vj8w9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.127413446s
Jun 10 00:27:27.894: INFO: Pod "pvc-snapshottable-data-tester-vj8w9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.17015447s
Jun 10 00:27:29.937: INFO: Pod "pvc-snapshottable-data-tester-vj8w9": Phase="Pending", Reason="", readiness=false. Elapsed: 8.212574528s
Jun 10 00:27:31.979: INFO: Pod "pvc-snapshottable-data-tester-vj8w9": Phase="Pending", Reason="", readiness=false. Elapsed: 10.254413724s
Jun 10 00:27:34.021: INFO: Pod "pvc-snapshottable-data-tester-vj8w9": Phase="Pending", Reason="", readiness=false. Elapsed: 12.296614295s
Jun 10 00:27:36.063: INFO: Pod "pvc-snapshottable-data-tester-vj8w9": Phase="Pending", Reason="", readiness=false. Elapsed: 14.338779089s
Jun 10 00:27:38.105: INFO: Pod "pvc-snapshottable-data-tester-vj8w9": Phase="Pending", Reason="", readiness=false. Elapsed: 16.380771052s
Jun 10 00:27:40.148: INFO: Pod "pvc-snapshottable-data-tester-vj8w9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.423848609s
STEP: Saw pod success
Jun 10 00:27:40.148: INFO: Pod "pvc-snapshottable-data-tester-vj8w9" satisfied condition "Succeeded or Failed"
Jun 10 00:27:40.241: INFO: Pod pvc-snapshottable-data-tester-vj8w9 has the following logs: 
Jun 10 00:27:40.241: INFO: Deleting pod "pvc-snapshottable-data-tester-vj8w9" in namespace "snapshotting-3661"
Jun 10 00:27:40.289: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-vj8w9" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun 10 00:27:50.502: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-3661 exec restored-pvc-tester-gnvsb --namespace=snapshotting-3661 -- cat /mnt/test/data'
... skipping 32 lines ...
Jun 10 00:28:15.242: INFO: volumesnapshotcontents snapcontent-90cf3fe5-092c-4a54-a349-e154a5918e62 has been found and is not deleted
Jun 10 00:28:16.285: INFO: volumesnapshotcontents snapcontent-90cf3fe5-092c-4a54-a349-e154a5918e62 has been found and is not deleted
Jun 10 00:28:17.327: INFO: volumesnapshotcontents snapcontent-90cf3fe5-092c-4a54-a349-e154a5918e62 has been found and is not deleted
Jun 10 00:28:18.370: INFO: volumesnapshotcontents snapcontent-90cf3fe5-092c-4a54-a349-e154a5918e62 has been found and is not deleted
Jun 10 00:28:19.413: INFO: volumesnapshotcontents snapcontent-90cf3fe5-092c-4a54-a349-e154a5918e62 has been found and is not deleted
Jun 10 00:28:20.455: INFO: volumesnapshotcontents snapcontent-90cf3fe5-092c-4a54-a349-e154a5918e62 has been found and is not deleted
Jun 10 00:28:21.455: INFO: WaitUntil failed after reaching the timeout 30s
[AfterEach] volume snapshot controller
  /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:221
Jun 10 00:28:21.500: INFO: Pod restored-pvc-tester-gnvsb has the following logs: 
Jun 10 00:28:21.500: INFO: Deleting pod "restored-pvc-tester-gnvsb" in namespace "snapshotting-3661"
Jun 10 00:28:21.543: INFO: Wait up to 5m0s for pod "restored-pvc-tester-gnvsb" to be fully deleted
Jun 10 00:28:57.626: INFO: deleting claim "snapshotting-3661"/"pvc-rfv6s"
... skipping 32 lines ...
        /tmp/kops.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:243
------------------------------


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.Ze8yNfZ8r/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:602

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


Ginkgo ran 1 suite in 11m19.013731587s
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
I0610 00:29:05.401659   26801 app.go:59] RunDir for this run: "/logs/artifacts/4deed458-c97f-11eb-a09e-ca7f85cb5ec2"
I0610 00:29:05.401787   26801 app.go:90] ID for this run: "4deed458-c97f-11eb-a09e-ca7f85cb5ec2"
I0610 00:29:05.401813   26801 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
I0610 00:29:05.415889   26807 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
... skipping 1479 lines ...