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

No Test Failures!


Error lines from build-log.txt

... skipping 483 lines ...
I0604 08:04:44.215585   11714 up.go:43] Cleaning up any leaked resources from previous cluster
I0604 08:04:44.215595   11714 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
I0604 08:04:44.227982   11720 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0604 08:04:44.228083   11720 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io" not found
W0604 08:04:44.726687   11714 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0604 08:04:44.726754   11714 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
I0604 08:04:44.738445   11731 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0604 08:04:44.738524   11731 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io" not found
I0604 08:04:45.217611   11714 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/06/04 08:04:45 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
I0604 08:04:45.228768   11714 http.go:37] curl https://ip.jsb.workers.dev
I0604 08:04:45.358519   11714 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.134.86.254/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones us-east-2a --master-size c5.large
I0604 08:04:45.369596   11745 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0604 08:04:45.369696   11745 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I0604 08:04:45.411940   11745 create_cluster.go:728] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0604 08:04:46.042799   11745 new_cluster.go:1022]  Cloud Provider ID = aws
... skipping 40 lines ...

I0604 08:05:10.954606   11714 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
I0604 08:05:10.968054   11765 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0604 08:05:10.968331   11765 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io

W0604 08:05:11.964839   11765 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
W0604 08:05:22.015034   11765 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
W0604 08:05:32.078757   11765 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
W0604 08:05:42.126041   11765 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
W0604 08:05:52.165109   11765 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
W0604 08:06:02.206322   11765 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
W0604 08:06:12.240491   11765 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
W0604 08:06:22.288135   11765 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
W0604 08:06:32.325969   11765 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
W0604 08:06:42.357896   11765 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
W0604 08:06:52.390393   11765 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
W0604 08:07:02.424569   11765 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
W0604 08:07:12.457163   11765 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
W0604 08:07:22.504359   11765 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
W0604 08:07:32.537062   11765 validate_cluster.go:221] (will retry): cluster not yet healthy
W0604 08:07:42.569477   11765 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
W0604 08:07:52.605533   11765 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
W0604 08:08:02.637858   11765 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
W0604 08:08:12.685696   11765 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
W0604 08:08:22.744212   11765 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
W0604 08:08:32.778082   11765 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
W0604 08:08:42.817004   11765 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
W0604 08:08:52.868635   11765 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
W0604 08:09:02.908483   11765 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
W0604 08:09:12.960230   11765 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
W0604 08:09:22.994140   11765 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-5d46c5dc5b-dz5dw		system-cluster-critical pod "cert-manager-5d46c5dc5b-dz5dw" is pending
Pod	kube-system/cert-manager-cainjector-74d69756d5-gqvbl	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-gqvbl" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-5j5hm	system-cluster-critical pod "cert-manager-webhook-7bbf67968-5j5hm" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-h558q		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-h558q" is pending
Pod	kube-system/coredns-f45c4bf76-fffnm			system-cluster-critical pod "coredns-f45c4bf76-fffnm" is pending

Validation Failed
W0604 08:09:34.285622   11765 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-5d46c5dc5b-dz5dw		system-cluster-critical pod "cert-manager-5d46c5dc5b-dz5dw" is pending
Pod	kube-system/cert-manager-cainjector-74d69756d5-gqvbl	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-gqvbl" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-5j5hm	system-cluster-critical pod "cert-manager-webhook-7bbf67968-5j5hm" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-h558q		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-h558q" is pending
Pod	kube-system/coredns-f45c4bf76-fffnm			system-cluster-critical pod "coredns-f45c4bf76-fffnm" is pending

Validation Failed
W0604 08:09:45.193082   11765 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-5d46c5dc5b-dz5dw		system-cluster-critical pod "cert-manager-5d46c5dc5b-dz5dw" is pending
Pod	kube-system/cert-manager-cainjector-74d69756d5-gqvbl	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-gqvbl" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-5j5hm	system-cluster-critical pod "cert-manager-webhook-7bbf67968-5j5hm" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-h558q		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-h558q" is pending
Pod	kube-system/coredns-f45c4bf76-fffnm			system-cluster-critical pod "coredns-f45c4bf76-fffnm" is pending

Validation Failed
W0604 08:09:56.138113   11765 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 12 lines ...
Pod	kube-system/cert-manager-cainjector-74d69756d5-gqvbl			system-cluster-critical pod "cert-manager-cainjector-74d69756d5-gqvbl" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-5j5hm			system-cluster-critical pod "cert-manager-webhook-7bbf67968-5j5hm" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-h558q				system-cluster-critical pod "coredns-autoscaler-6f594f4c58-h558q" is pending
Pod	kube-system/coredns-f45c4bf76-fffnm					system-cluster-critical pod "coredns-f45c4bf76-fffnm" is pending
Pod	kube-system/kube-proxy-ip-172-20-59-33.us-east-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-59-33.us-east-2.compute.internal" is pending

Validation Failed
W0604 08:10:07.114800   11765 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 13 lines ...
Pod	kube-system/cert-manager-5d46c5dc5b-dz5dw		system-cluster-critical pod "cert-manager-5d46c5dc5b-dz5dw" is pending
Pod	kube-system/cert-manager-cainjector-74d69756d5-gqvbl	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-gqvbl" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-5j5hm	system-cluster-critical pod "cert-manager-webhook-7bbf67968-5j5hm" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-h558q		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-h558q" is pending
Pod	kube-system/coredns-f45c4bf76-fffnm			system-cluster-critical pod "coredns-f45c4bf76-fffnm" is pending

Validation Failed
W0604 08:10:18.229389   11765 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 12 lines ...
Pod	kube-system/cert-manager-5d46c5dc5b-dz5dw		system-cluster-critical pod "cert-manager-5d46c5dc5b-dz5dw" is pending
Pod	kube-system/cert-manager-cainjector-74d69756d5-gqvbl	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-gqvbl" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-5j5hm	system-cluster-critical pod "cert-manager-webhook-7bbf67968-5j5hm" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-h558q		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-h558q" is pending
Pod	kube-system/coredns-f45c4bf76-fffnm			system-cluster-critical pod "coredns-f45c4bf76-fffnm" is pending

Validation Failed
W0604 08:10:29.092362   11765 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 9 lines ...
Machine	i-0e9ce963557e07e18					machine "i-0e9ce963557e07e18" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-gqvbl	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-gqvbl" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-5j5hm	system-cluster-critical pod "cert-manager-webhook-7bbf67968-5j5hm" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-h558q		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-h558q" is pending
Pod	kube-system/coredns-f45c4bf76-fffnm			system-cluster-critical pod "coredns-f45c4bf76-fffnm" is pending

Validation Failed
W0604 08:10:40.046103   11765 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 9 lines ...
Machine	i-0e9ce963557e07e18					machine "i-0e9ce963557e07e18" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-gqvbl	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-gqvbl" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-5j5hm	system-cluster-critical pod "cert-manager-webhook-7bbf67968-5j5hm" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-h558q		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-h558q" is pending
Pod	kube-system/coredns-f45c4bf76-fffnm			system-cluster-critical pod "coredns-f45c4bf76-fffnm" is pending

Validation Failed
W0604 08:10:50.926319   11765 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 9 lines ...
Machine	i-0e9ce963557e07e18					machine "i-0e9ce963557e07e18" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-gqvbl	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-gqvbl" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-5j5hm	system-cluster-critical pod "cert-manager-webhook-7bbf67968-5j5hm" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-h558q		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-h558q" is pending
Pod	kube-system/coredns-f45c4bf76-fffnm			system-cluster-critical pod "coredns-f45c4bf76-fffnm" is pending

Validation Failed
W0604 08:11:01.850335   11765 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 9 lines ...
Machine	i-0e9ce963557e07e18					machine "i-0e9ce963557e07e18" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-gqvbl	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-gqvbl" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-5j5hm	system-cluster-critical pod "cert-manager-webhook-7bbf67968-5j5hm" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-h558q		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-h558q" is pending
Pod	kube-system/coredns-f45c4bf76-fffnm			system-cluster-critical pod "coredns-f45c4bf76-fffnm" is pending

Validation Failed
W0604 08:11:12.804517   11765 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 12 lines ...
Pod	kube-system/coredns-autoscaler-6f594f4c58-h558q		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-h558q" is pending
Pod	kube-system/coredns-f45c4bf76-fffnm			system-cluster-critical pod "coredns-f45c4bf76-fffnm" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-nwtv5		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-nwtv5" is pending
Pod	kube-system/ebs-csi-controller-7ffff4ddf5-zt6fr		system-cluster-critical pod "ebs-csi-controller-7ffff4ddf5-zt6fr" is pending
Pod	kube-system/ebs-csi-node-89d6j				system-node-critical pod "ebs-csi-node-89d6j" is pending

Validation Failed
W0604 08:11:23.780903   11765 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 9 lines ...
Machine	i-0e9ce963557e07e18					machine "i-0e9ce963557e07e18" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-gqvbl	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-gqvbl" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-5j5hm	system-cluster-critical pod "cert-manager-webhook-7bbf67968-5j5hm" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-h558q		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-h558q" is pending
Pod	kube-system/coredns-f45c4bf76-fffnm			system-cluster-critical pod "coredns-f45c4bf76-fffnm" is pending

Validation Failed
W0604 08:11:34.696922   11765 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 9 lines ...
Machine	i-0e9ce963557e07e18					machine "i-0e9ce963557e07e18" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-gqvbl	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-gqvbl" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-5j5hm	system-cluster-critical pod "cert-manager-webhook-7bbf67968-5j5hm" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-h558q		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-h558q" is pending
Pod	kube-system/coredns-f45c4bf76-fffnm			system-cluster-critical pod "coredns-f45c4bf76-fffnm" is pending

Validation Failed
W0604 08:11:45.667058   11765 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 9 lines ...
Machine	i-0e9ce963557e07e18					machine "i-0e9ce963557e07e18" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-gqvbl	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-gqvbl" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-5j5hm	system-cluster-critical pod "cert-manager-webhook-7bbf67968-5j5hm" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-h558q		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-h558q" is pending
Pod	kube-system/coredns-f45c4bf76-fffnm			system-cluster-critical pod "coredns-f45c4bf76-fffnm" is pending

Validation Failed
W0604 08:11:56.626354   11765 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 9 lines ...
Machine	i-0e9ce963557e07e18					machine "i-0e9ce963557e07e18" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-gqvbl	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-gqvbl" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-5j5hm	system-cluster-critical pod "cert-manager-webhook-7bbf67968-5j5hm" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-h558q		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-h558q" is pending
Pod	kube-system/coredns-f45c4bf76-fffnm			system-cluster-critical pod "coredns-f45c4bf76-fffnm" is pending

Validation Failed
W0604 08:12:07.535114   11765 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 9 lines ...
Machine	i-0e9ce963557e07e18					machine "i-0e9ce963557e07e18" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-gqvbl	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-gqvbl" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-5j5hm	system-cluster-critical pod "cert-manager-webhook-7bbf67968-5j5hm" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-h558q		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-h558q" is pending
Pod	kube-system/coredns-f45c4bf76-fffnm			system-cluster-critical pod "coredns-f45c4bf76-fffnm" is pending

Validation Failed
W0604 08:12:18.557178   11765 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 9 lines ...
Machine	i-0e9ce963557e07e18					machine "i-0e9ce963557e07e18" has not yet joined cluster
Pod	kube-system/cert-manager-cainjector-74d69756d5-gqvbl	system-cluster-critical pod "cert-manager-cainjector-74d69756d5-gqvbl" is pending
Pod	kube-system/cert-manager-webhook-7bbf67968-5j5hm	system-cluster-critical pod "cert-manager-webhook-7bbf67968-5j5hm" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-h558q		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-h558q" is pending
Pod	kube-system/coredns-f45c4bf76-fffnm			system-cluster-critical pod "coredns-f45c4bf76-fffnm" is pending

Validation Failed
W0604 08:12:29.446381   11765 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 13 lines ...
Pod	kube-system/cert-manager-webhook-7bbf67968-5j5hm			system-cluster-critical pod "cert-manager-webhook-7bbf67968-5j5hm" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-h558q				system-cluster-critical pod "coredns-autoscaler-6f594f4c58-h558q" is pending
Pod	kube-system/coredns-f45c4bf76-fffnm					system-cluster-critical pod "coredns-f45c4bf76-fffnm" is pending
Pod	kube-system/ebs-csi-node-9676h						system-node-critical pod "ebs-csi-node-9676h" is pending
Pod	kube-system/kube-proxy-ip-172-20-44-239.us-east-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-44-239.us-east-2.compute.internal" is pending

Validation Failed
W0604 08:12:40.316459   11765 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 23 lines ...
Pod	kube-system/ebs-csi-node-9676h						system-node-critical pod "ebs-csi-node-9676h" is pending
Pod	kube-system/ebs-csi-node-hz567						system-node-critical pod "ebs-csi-node-hz567" is pending
Pod	kube-system/ebs-csi-node-mvnxh						system-node-critical pod "ebs-csi-node-mvnxh" is pending
Pod	kube-system/kube-proxy-ip-172-20-49-219.us-east-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-49-219.us-east-2.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-51-225.us-east-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-51-225.us-east-2.compute.internal" is pending

Validation Failed
W0604 08:12:51.261979   11765 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 18 lines ...
Pod	kube-system/cert-manager-webhook-7bbf67968-5j5hm	system-cluster-critical pod "cert-manager-webhook-7bbf67968-5j5hm" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-h558q		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-h558q" is pending
Pod	kube-system/coredns-f45c4bf76-fffnm			system-cluster-critical pod "coredns-f45c4bf76-fffnm" is pending
Pod	kube-system/ebs-csi-node-68f7x				system-node-critical pod "ebs-csi-node-68f7x" is pending
Pod	kube-system/ebs-csi-node-mvnxh				system-node-critical pod "ebs-csi-node-mvnxh" is pending

Validation Failed
W0604 08:13:02.171806   11765 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 7 lines ...

VALIDATION ERRORS
KIND	NAME				MESSAGE
Pod	kube-system/calico-node-7xgv7	system-node-critical pod "calico-node-7xgv7" is not ready (calico-node)
Pod	kube-system/calico-node-h2d6f	system-node-critical pod "calico-node-h2d6f" is not ready (calico-node)

Validation Failed
W0604 08:13:13.107374   11765 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 189 lines ...

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

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

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

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 281 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  4 08:16:14.020: 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.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  4 08:16:15.444: INFO: Creating resource for dynamic PV
Jun  4 08:16:15.444: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-9685-e2e-sc86x5t
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  4 08:16:21.677: INFO: Deleting pod "pod-610fe030-2ccd-4a3b-b3c5-fb639289f7d5" in namespace "volumemode-9685"
Jun  4 08:16:21.710: INFO: Wait up to 5m0s for pod "pod-610fe030-2ccd-4a3b-b3c5-fb639289f7d5" to be fully deleted
STEP: Deleting pvc
Jun  4 08:16:25.830: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comwpmjz"
Jun  4 08:16:25.862: INFO: Waiting up to 5m0s for PersistentVolume pvc-166430ab-ba9a-4c85-a9e9-d494680335ca to get deleted
Jun  4 08:16:25.891: INFO: PersistentVolume pvc-166430ab-ba9a-4c85-a9e9-d494680335ca found and phase=Released (29.440698ms)
... skipping 8 lines ...

• [SLOW TEST:22.030 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.HvoHaXSxC/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.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [sig-storage] vsphere statefulset [Feature:vsphere]
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  4 08:16:36.052: INFO: >>> kubeConfig: /root/.kube/config
... skipping 83 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.HvoHaXSxC/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.HvoHaXSxC/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.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 69 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  4 08:16:13.975: 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.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  4 08:16:15.397: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  4 08:16:15.397: INFO: Creating resource for dynamic PV
Jun  4 08:16:15.397: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-62289cv2z
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  4 08:16:23.639: INFO: Deleting pod "pod-24830ab3-367d-48a4-b7b3-9c59980043a9" in namespace "volumemode-6228"
Jun  4 08:16:23.690: INFO: Wait up to 5m0s for pod "pod-24830ab3-367d-48a4-b7b3-9c59980043a9" to be fully deleted
STEP: Deleting pvc
Jun  4 08:16:29.815: INFO: Deleting PersistentVolumeClaim "awsbsqrs"
Jun  4 08:16:29.850: INFO: Waiting up to 5m0s for PersistentVolume pvc-adb22463-b3c9-4be4-8e48-6d2abe947de9 to get deleted
Jun  4 08:16:29.892: INFO: PersistentVolume pvc-adb22463-b3c9-4be4-8e48-6d2abe947de9 found and phase=Bound (41.527867ms)
... skipping 10 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.HvoHaXSxC/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.HvoHaXSxC/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
    /tmp/kops.HvoHaXSxC/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.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
S
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
... skipping 134 lines ...
Jun  4 08:16:12.504: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  4 08:16:12.966: INFO: Successfully created a new PD: "aws://us-east-2a/vol-0c70a2aa05592752a".
Jun  4 08:16:12.967: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-776c
STEP: Creating a pod to test exec-volume-test
Jun  4 08:16:13.000: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-776c" in namespace "volume-9628" to be "Succeeded or Failed"
Jun  4 08:16:13.043: INFO: Pod "exec-volume-test-inlinevolume-776c": Phase="Pending", Reason="", readiness=false. Elapsed: 43.076768ms
Jun  4 08:16:15.076: INFO: Pod "exec-volume-test-inlinevolume-776c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.075800479s
Jun  4 08:16:17.107: INFO: Pod "exec-volume-test-inlinevolume-776c": Phase="Pending", Reason="", readiness=false. Elapsed: 4.107202982s
Jun  4 08:16:19.166: INFO: Pod "exec-volume-test-inlinevolume-776c": Phase="Pending", Reason="", readiness=false. Elapsed: 6.166271882s
Jun  4 08:16:21.197: INFO: Pod "exec-volume-test-inlinevolume-776c": Phase="Pending", Reason="", readiness=false. Elapsed: 8.197005614s
Jun  4 08:16:23.229: INFO: Pod "exec-volume-test-inlinevolume-776c": Phase="Pending", Reason="", readiness=false. Elapsed: 10.228497217s
... skipping 3 lines ...
Jun  4 08:16:31.357: INFO: Pod "exec-volume-test-inlinevolume-776c": Phase="Pending", Reason="", readiness=false. Elapsed: 18.357005782s
Jun  4 08:16:33.389: INFO: Pod "exec-volume-test-inlinevolume-776c": Phase="Pending", Reason="", readiness=false. Elapsed: 20.388417396s
Jun  4 08:16:35.420: INFO: Pod "exec-volume-test-inlinevolume-776c": Phase="Pending", Reason="", readiness=false. Elapsed: 22.42026559s
Jun  4 08:16:37.452: INFO: Pod "exec-volume-test-inlinevolume-776c": Phase="Pending", Reason="", readiness=false. Elapsed: 24.451855445s
Jun  4 08:16:39.484: INFO: Pod "exec-volume-test-inlinevolume-776c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.484011879s
STEP: Saw pod success
Jun  4 08:16:39.484: INFO: Pod "exec-volume-test-inlinevolume-776c" satisfied condition "Succeeded or Failed"
Jun  4 08:16:39.515: INFO: Trying to get logs from node ip-172-20-51-225.us-east-2.compute.internal pod exec-volume-test-inlinevolume-776c container exec-container-inlinevolume-776c: <nil>
STEP: delete the pod
Jun  4 08:16:39.588: INFO: Waiting for pod exec-volume-test-inlinevolume-776c to disappear
Jun  4 08:16:39.618: INFO: Pod exec-volume-test-inlinevolume-776c no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-776c
Jun  4 08:16:39.618: INFO: Deleting pod "exec-volume-test-inlinevolume-776c" in namespace "volume-9628"
Jun  4 08:16:39.811: INFO: Couldn't delete PD "aws://us-east-2a/vol-0c70a2aa05592752a", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c70a2aa05592752a is currently attached to i-067b46a95c9863b19
	status code: 400, request id: d63a1cfc-ac28-44d3-9222-c1c46c5f82d2
Jun  4 08:16:45.056: INFO: Couldn't delete PD "aws://us-east-2a/vol-0c70a2aa05592752a", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0c70a2aa05592752a is currently attached to i-067b46a95c9863b19
	status code: 400, request id: 6c61a0e1-f9eb-4a74-9923-bcee6c1afb8d
Jun  4 08:16:50.316: INFO: Successfully deleted PD "aws://us-east-2a/vol-0c70a2aa05592752a".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  4 08:16:50.317: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-9628" for this suite.
... skipping 144 lines ...
STEP: Creating a kubernetes client
Jun  4 08:16:11.769: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename provisioning
W0604 08:16:12.031787   25615 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Jun  4 08:16:12.031: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail if non-existent subpath is outside the volume [Slow][LinuxOnly]
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun  4 08:16:12.093: INFO: Creating resource for dynamic PV
Jun  4 08:16:12.093: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8024-e2e-scsbgcq
STEP: creating a claim
Jun  4 08:16:12.125: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-tbgh
STEP: Checking for subpath error in container status
Jun  4 08:16:38.313: INFO: Deleting pod "pod-subpath-test-dynamicpv-tbgh" in namespace "provisioning-8024"
Jun  4 08:16:38.348: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-tbgh" to be fully deleted
STEP: Deleting pod
Jun  4 08:16:52.409: INFO: Deleting pod "pod-subpath-test-dynamicpv-tbgh" in namespace "provisioning-8024"
STEP: Deleting pvc
Jun  4 08:16:52.502: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comjlzjh"
... skipping 9 lines ...

• [SLOW TEST:45.950 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.HvoHaXSxC/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.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 10 lines ...
Jun  4 08:16:12.453: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-697697tkp
STEP: creating a claim
Jun  4 08:16:12.495: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-fx5k
STEP: Creating a pod to test subpath
Jun  4 08:16:12.632: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-fx5k" in namespace "provisioning-6976" to be "Succeeded or Failed"
Jun  4 08:16:12.667: INFO: Pod "pod-subpath-test-dynamicpv-fx5k": Phase="Pending", Reason="", readiness=false. Elapsed: 35.653527ms
Jun  4 08:16:14.704: INFO: Pod "pod-subpath-test-dynamicpv-fx5k": Phase="Pending", Reason="", readiness=false. Elapsed: 2.071911799s
Jun  4 08:16:16.735: INFO: Pod "pod-subpath-test-dynamicpv-fx5k": Phase="Pending", Reason="", readiness=false. Elapsed: 4.103229381s
Jun  4 08:16:18.767: INFO: Pod "pod-subpath-test-dynamicpv-fx5k": Phase="Pending", Reason="", readiness=false. Elapsed: 6.135520083s
Jun  4 08:16:20.800: INFO: Pod "pod-subpath-test-dynamicpv-fx5k": Phase="Pending", Reason="", readiness=false. Elapsed: 8.167921755s
Jun  4 08:16:22.831: INFO: Pod "pod-subpath-test-dynamicpv-fx5k": Phase="Pending", Reason="", readiness=false. Elapsed: 10.198858046s
... skipping 2 lines ...
Jun  4 08:16:28.926: INFO: Pod "pod-subpath-test-dynamicpv-fx5k": Phase="Pending", Reason="", readiness=false. Elapsed: 16.294012969s
Jun  4 08:16:30.957: INFO: Pod "pod-subpath-test-dynamicpv-fx5k": Phase="Pending", Reason="", readiness=false. Elapsed: 18.325291213s
Jun  4 08:16:33.027: INFO: Pod "pod-subpath-test-dynamicpv-fx5k": Phase="Pending", Reason="", readiness=false. Elapsed: 20.395439574s
Jun  4 08:16:35.058: INFO: Pod "pod-subpath-test-dynamicpv-fx5k": Phase="Pending", Reason="", readiness=false. Elapsed: 22.426518469s
Jun  4 08:16:37.089: INFO: Pod "pod-subpath-test-dynamicpv-fx5k": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.457169173s
STEP: Saw pod success
Jun  4 08:16:37.089: INFO: Pod "pod-subpath-test-dynamicpv-fx5k" satisfied condition "Succeeded or Failed"
Jun  4 08:16:37.119: INFO: Trying to get logs from node ip-172-20-51-225.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-fx5k container test-container-subpath-dynamicpv-fx5k: <nil>
STEP: delete the pod
Jun  4 08:16:37.197: INFO: Waiting for pod pod-subpath-test-dynamicpv-fx5k to disappear
Jun  4 08:16:37.226: INFO: Pod pod-subpath-test-dynamicpv-fx5k no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-fx5k
Jun  4 08:16:37.226: INFO: Deleting pod "pod-subpath-test-dynamicpv-fx5k" in namespace "provisioning-6976"
... skipping 112 lines ...
Jun  4 08:16:15.043: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-3350-e2e-sccj548
STEP: creating a claim
Jun  4 08:16:15.075: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-p5dt
STEP: Creating a pod to test exec-volume-test
Jun  4 08:16:15.178: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-p5dt" in namespace "volume-3350" to be "Succeeded or Failed"
Jun  4 08:16:15.207: INFO: Pod "exec-volume-test-dynamicpv-p5dt": Phase="Pending", Reason="", readiness=false. Elapsed: 29.105718ms
Jun  4 08:16:17.237: INFO: Pod "exec-volume-test-dynamicpv-p5dt": Phase="Pending", Reason="", readiness=false. Elapsed: 2.0593302s
Jun  4 08:16:19.277: INFO: Pod "exec-volume-test-dynamicpv-p5dt": Phase="Pending", Reason="", readiness=false. Elapsed: 4.098568273s
Jun  4 08:16:21.306: INFO: Pod "exec-volume-test-dynamicpv-p5dt": Phase="Pending", Reason="", readiness=false. Elapsed: 6.128353675s
Jun  4 08:16:23.338: INFO: Pod "exec-volume-test-dynamicpv-p5dt": Phase="Pending", Reason="", readiness=false. Elapsed: 8.159654277s
Jun  4 08:16:25.369: INFO: Pod "exec-volume-test-dynamicpv-p5dt": Phase="Pending", Reason="", readiness=false. Elapsed: 10.190603441s
... skipping 2 lines ...
Jun  4 08:16:31.461: INFO: Pod "exec-volume-test-dynamicpv-p5dt": Phase="Pending", Reason="", readiness=false. Elapsed: 16.283293982s
Jun  4 08:16:33.492: INFO: Pod "exec-volume-test-dynamicpv-p5dt": Phase="Pending", Reason="", readiness=false. Elapsed: 18.314490216s
Jun  4 08:16:35.522: INFO: Pod "exec-volume-test-dynamicpv-p5dt": Phase="Pending", Reason="", readiness=false. Elapsed: 20.344185851s
Jun  4 08:16:37.552: INFO: Pod "exec-volume-test-dynamicpv-p5dt": Phase="Pending", Reason="", readiness=false. Elapsed: 22.374097226s
Jun  4 08:16:39.587: INFO: Pod "exec-volume-test-dynamicpv-p5dt": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.4090937s
STEP: Saw pod success
Jun  4 08:16:39.587: INFO: Pod "exec-volume-test-dynamicpv-p5dt" satisfied condition "Succeeded or Failed"
Jun  4 08:16:39.617: INFO: Trying to get logs from node ip-172-20-44-239.us-east-2.compute.internal pod exec-volume-test-dynamicpv-p5dt container exec-container-dynamicpv-p5dt: <nil>
STEP: delete the pod
Jun  4 08:16:39.705: INFO: Waiting for pod exec-volume-test-dynamicpv-p5dt to disappear
Jun  4 08:16:39.737: INFO: Pod exec-volume-test-dynamicpv-p5dt no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-p5dt
Jun  4 08:16:39.737: INFO: Deleting pod "exec-volume-test-dynamicpv-p5dt" in namespace "volume-3350"
... skipping 161 lines ...
Jun  4 08:16:21.388: INFO: PersistentVolumeClaim pvc-l8kpg found but phase is Pending instead of Bound.
Jun  4 08:16:23.420: INFO: PersistentVolumeClaim pvc-l8kpg found and phase=Bound (10.192805389s)
Jun  4 08:16:23.420: INFO: Waiting up to 3m0s for PersistentVolume aws-zjgrz to have phase Bound
Jun  4 08:16:23.451: INFO: PersistentVolume aws-zjgrz found and phase=Bound (31.021748ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-jtfq
STEP: Creating a pod to test exec-volume-test
Jun  4 08:16:23.549: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-jtfq" in namespace "volume-3631" to be "Succeeded or Failed"
Jun  4 08:16:23.585: INFO: Pod "exec-volume-test-preprovisionedpv-jtfq": Phase="Pending", Reason="", readiness=false. Elapsed: 35.879567ms
Jun  4 08:16:25.616: INFO: Pod "exec-volume-test-preprovisionedpv-jtfq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.06743863s
Jun  4 08:16:27.649: INFO: Pod "exec-volume-test-preprovisionedpv-jtfq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.100138364s
Jun  4 08:16:29.682: INFO: Pod "exec-volume-test-preprovisionedpv-jtfq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.132944898s
Jun  4 08:16:31.713: INFO: Pod "exec-volume-test-preprovisionedpv-jtfq": Phase="Pending", Reason="", readiness=false. Elapsed: 8.164436422s
Jun  4 08:16:33.746: INFO: Pod "exec-volume-test-preprovisionedpv-jtfq": Phase="Pending", Reason="", readiness=false. Elapsed: 10.196908976s
... skipping 5 lines ...
Jun  4 08:16:45.959: INFO: Pod "exec-volume-test-preprovisionedpv-jtfq": Phase="Pending", Reason="", readiness=false. Elapsed: 22.410411734s
Jun  4 08:16:47.991: INFO: Pod "exec-volume-test-preprovisionedpv-jtfq": Phase="Pending", Reason="", readiness=false. Elapsed: 24.44222613s
Jun  4 08:16:50.024: INFO: Pod "exec-volume-test-preprovisionedpv-jtfq": Phase="Pending", Reason="", readiness=false. Elapsed: 26.475546796s
Jun  4 08:16:52.056: INFO: Pod "exec-volume-test-preprovisionedpv-jtfq": Phase="Pending", Reason="", readiness=false. Elapsed: 28.507071092s
Jun  4 08:16:54.089: INFO: Pod "exec-volume-test-preprovisionedpv-jtfq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 30.539951578s
STEP: Saw pod success
Jun  4 08:16:54.089: INFO: Pod "exec-volume-test-preprovisionedpv-jtfq" satisfied condition "Succeeded or Failed"
Jun  4 08:16:54.120: INFO: Trying to get logs from node ip-172-20-49-219.us-east-2.compute.internal pod exec-volume-test-preprovisionedpv-jtfq container exec-container-preprovisionedpv-jtfq: <nil>
STEP: delete the pod
Jun  4 08:16:54.192: INFO: Waiting for pod exec-volume-test-preprovisionedpv-jtfq to disappear
Jun  4 08:16:54.224: INFO: Pod exec-volume-test-preprovisionedpv-jtfq no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-jtfq
Jun  4 08:16:54.224: INFO: Deleting pod "exec-volume-test-preprovisionedpv-jtfq" in namespace "volume-3631"
STEP: Deleting pv and pvc
Jun  4 08:16:54.255: INFO: Deleting PersistentVolumeClaim "pvc-l8kpg"
Jun  4 08:16:54.295: INFO: Deleting PersistentVolume "aws-zjgrz"
Jun  4 08:16:54.508: INFO: Couldn't delete PD "aws://us-east-2a/vol-0e4ea98847c7d34b9", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e4ea98847c7d34b9 is currently attached to i-08609f5438bdf02f8
	status code: 400, request id: bdd6e920-24c3-4973-ab45-83d878177ba9
Jun  4 08:16:59.758: INFO: Couldn't delete PD "aws://us-east-2a/vol-0e4ea98847c7d34b9", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e4ea98847c7d34b9 is currently attached to i-08609f5438bdf02f8
	status code: 400, request id: 99177739-49e4-43fe-8ca6-db291d2644c4
Jun  4 08:17:04.992: INFO: Couldn't delete PD "aws://us-east-2a/vol-0e4ea98847c7d34b9", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e4ea98847c7d34b9 is currently attached to i-08609f5438bdf02f8
	status code: 400, request id: d3a67143-aeb5-4912-b231-a68257eb50d3
Jun  4 08:17:10.270: INFO: Couldn't delete PD "aws://us-east-2a/vol-0e4ea98847c7d34b9", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e4ea98847c7d34b9 is currently attached to i-08609f5438bdf02f8
	status code: 400, request id: 226d68df-928e-4764-8b10-9c57ae7a4210
Jun  4 08:17:15.563: INFO: Couldn't delete PD "aws://us-east-2a/vol-0e4ea98847c7d34b9", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0e4ea98847c7d34b9 is currently attached to i-08609f5438bdf02f8
	status code: 400, request id: cf38f14c-41fa-4105-868c-aea5b5ccd88a
Jun  4 08:17:20.848: INFO: Successfully deleted PD "aws://us-east-2a/vol-0e4ea98847c7d34b9".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  4 08:17:20.848: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-3631" for this suite.
... skipping 459 lines ...

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

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

    /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 104 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  4 08:16:49.193: 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.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun  4 08:16:49.347: INFO: Creating resource for dynamic PV
Jun  4 08:16:49.347: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1738-e2e-scfbmk7
STEP: creating a claim
Jun  4 08:16:49.378: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-5bqk
STEP: Checking for subpath error in container status
Jun  4 08:17:15.534: INFO: Deleting pod "pod-subpath-test-dynamicpv-5bqk" in namespace "provisioning-1738"
Jun  4 08:17:15.566: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-5bqk" to be fully deleted
STEP: Deleting pod
Jun  4 08:17:29.626: INFO: Deleting pod "pod-subpath-test-dynamicpv-5bqk" in namespace "provisioning-1738"
STEP: Deleting pvc
Jun  4 08:17:29.718: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comrgtk4"
... skipping 9 lines ...

• [SLOW TEST:45.716 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath file is outside the volume [Slow][LinuxOnly]
    /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)(allowExpansion)] volume-expand
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (block volmode)(allowExpansion)] volume-expand
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 285 lines ...
Jun  4 08:16:50.799: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-3611-e2e-scj6jtz
STEP: creating a claim
Jun  4 08:16:50.831: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-ln24
STEP: Creating a pod to test exec-volume-test
Jun  4 08:16:50.926: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-ln24" in namespace "volume-3611" to be "Succeeded or Failed"
Jun  4 08:16:50.956: INFO: Pod "exec-volume-test-dynamicpv-ln24": Phase="Pending", Reason="", readiness=false. Elapsed: 30.061218ms
Jun  4 08:16:52.987: INFO: Pod "exec-volume-test-dynamicpv-ln24": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061292785s
Jun  4 08:16:55.018: INFO: Pod "exec-volume-test-dynamicpv-ln24": Phase="Pending", Reason="", readiness=false. Elapsed: 4.092488181s
Jun  4 08:16:57.050: INFO: Pod "exec-volume-test-dynamicpv-ln24": Phase="Pending", Reason="", readiness=false. Elapsed: 6.124272057s
Jun  4 08:16:59.081: INFO: Pod "exec-volume-test-dynamicpv-ln24": Phase="Pending", Reason="", readiness=false. Elapsed: 8.155570435s
Jun  4 08:17:01.112: INFO: Pod "exec-volume-test-dynamicpv-ln24": Phase="Pending", Reason="", readiness=false. Elapsed: 10.186287812s
Jun  4 08:17:03.146: INFO: Pod "exec-volume-test-dynamicpv-ln24": Phase="Pending", Reason="", readiness=false. Elapsed: 12.22020515s
Jun  4 08:17:05.177: INFO: Pod "exec-volume-test-dynamicpv-ln24": Phase="Pending", Reason="", readiness=false. Elapsed: 14.251616678s
Jun  4 08:17:07.208: INFO: Pod "exec-volume-test-dynamicpv-ln24": Phase="Pending", Reason="", readiness=false. Elapsed: 16.282305386s
Jun  4 08:17:09.242: INFO: Pod "exec-volume-test-dynamicpv-ln24": Phase="Pending", Reason="", readiness=false. Elapsed: 18.315739104s
Jun  4 08:17:11.274: INFO: Pod "exec-volume-test-dynamicpv-ln24": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.347666423s
STEP: Saw pod success
Jun  4 08:17:11.274: INFO: Pod "exec-volume-test-dynamicpv-ln24" satisfied condition "Succeeded or Failed"
Jun  4 08:17:11.303: INFO: Trying to get logs from node ip-172-20-49-5.us-east-2.compute.internal pod exec-volume-test-dynamicpv-ln24 container exec-container-dynamicpv-ln24: <nil>
STEP: delete the pod
Jun  4 08:17:11.381: INFO: Waiting for pod exec-volume-test-dynamicpv-ln24 to disappear
Jun  4 08:17:11.411: INFO: Pod exec-volume-test-dynamicpv-ln24 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-ln24
Jun  4 08:17:11.411: INFO: Deleting pod "exec-volume-test-dynamicpv-ln24" in namespace "volume-3611"
... skipping 191 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.HvoHaXSxC/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.HvoHaXSxC/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.HvoHaXSxC/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.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 491 lines ...
Jun  4 08:17:29.141: INFO: Pod aws-client still exists
Jun  4 08:17:31.110: INFO: Waiting for pod aws-client to disappear
Jun  4 08:17:31.142: INFO: Pod aws-client still exists
Jun  4 08:17:33.111: INFO: Waiting for pod aws-client to disappear
Jun  4 08:17:33.142: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun  4 08:17:33.378: INFO: Couldn't delete PD "aws://us-east-2a/vol-0d072c09f6b63927a", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d072c09f6b63927a is currently attached to i-067b46a95c9863b19
	status code: 400, request id: cf5ff245-b9d2-41a7-81dd-af815555c582
Jun  4 08:17:38.641: INFO: Couldn't delete PD "aws://us-east-2a/vol-0d072c09f6b63927a", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d072c09f6b63927a is currently attached to i-067b46a95c9863b19
	status code: 400, request id: a7f00b53-d29b-4cc1-800a-774921f83554
Jun  4 08:17:43.874: INFO: Couldn't delete PD "aws://us-east-2a/vol-0d072c09f6b63927a", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d072c09f6b63927a is currently attached to i-067b46a95c9863b19
	status code: 400, request id: e40d4e4d-e001-410f-8e07-f321ef78e5f0
Jun  4 08:17:49.168: INFO: Couldn't delete PD "aws://us-east-2a/vol-0d072c09f6b63927a", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0d072c09f6b63927a is currently attached to i-067b46a95c9863b19
	status code: 400, request id: 60ece640-a999-4f6f-b07a-136d7b5075b3
Jun  4 08:17:54.405: INFO: Successfully deleted PD "aws://us-east-2a/vol-0d072c09f6b63927a".
[AfterEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  4 08:17:54.406: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-7664" for this suite.
... skipping 110 lines ...
Jun  4 08:17:39.835: INFO: Pod aws-client still exists
Jun  4 08:17:41.803: INFO: Waiting for pod aws-client to disappear
Jun  4 08:17:41.833: INFO: Pod aws-client still exists
Jun  4 08:17:43.803: INFO: Waiting for pod aws-client to disappear
Jun  4 08:17:43.833: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun  4 08:17:44.087: INFO: Couldn't delete PD "aws://us-east-2a/vol-06d69efefe658728a", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-06d69efefe658728a is currently attached to i-08609f5438bdf02f8
	status code: 400, request id: 3cf856c4-8905-43c1-9d3b-9804161085cb
Jun  4 08:17:49.589: INFO: Couldn't delete PD "aws://us-east-2a/vol-06d69efefe658728a", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-06d69efefe658728a is currently attached to i-08609f5438bdf02f8
	status code: 400, request id: 01639550-8329-4875-ad5d-b50e2c311cda
Jun  4 08:17:54.824: INFO: Successfully deleted PD "aws://us-east-2a/vol-06d69efefe658728a".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  4 08:17:54.824: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-4604" for this suite.
... skipping 286 lines ...
Jun  4 08:17:31.197: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-272-e2e-sc5qltl
STEP: creating a claim
Jun  4 08:17:31.233: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-fr5d
STEP: Creating a pod to test exec-volume-test
Jun  4 08:17:31.331: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-fr5d" in namespace "volume-272" to be "Succeeded or Failed"
Jun  4 08:17:31.361: INFO: Pod "exec-volume-test-dynamicpv-fr5d": Phase="Pending", Reason="", readiness=false. Elapsed: 30.019308ms
Jun  4 08:17:33.393: INFO: Pod "exec-volume-test-dynamicpv-fr5d": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061905468s
Jun  4 08:17:35.424: INFO: Pod "exec-volume-test-dynamicpv-fr5d": Phase="Pending", Reason="", readiness=false. Elapsed: 4.09367181s
Jun  4 08:17:37.456: INFO: Pod "exec-volume-test-dynamicpv-fr5d": Phase="Pending", Reason="", readiness=false. Elapsed: 6.124939121s
Jun  4 08:17:39.487: INFO: Pod "exec-volume-test-dynamicpv-fr5d": Phase="Pending", Reason="", readiness=false. Elapsed: 8.156132903s
Jun  4 08:17:41.517: INFO: Pod "exec-volume-test-dynamicpv-fr5d": Phase="Pending", Reason="", readiness=false. Elapsed: 10.186666386s
Jun  4 08:17:43.549: INFO: Pod "exec-volume-test-dynamicpv-fr5d": Phase="Pending", Reason="", readiness=false. Elapsed: 12.218608197s
Jun  4 08:17:45.581: INFO: Pod "exec-volume-test-dynamicpv-fr5d": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.249727891s
STEP: Saw pod success
Jun  4 08:17:45.581: INFO: Pod "exec-volume-test-dynamicpv-fr5d" satisfied condition "Succeeded or Failed"
Jun  4 08:17:45.611: INFO: Trying to get logs from node ip-172-20-44-239.us-east-2.compute.internal pod exec-volume-test-dynamicpv-fr5d container exec-container-dynamicpv-fr5d: <nil>
STEP: delete the pod
Jun  4 08:17:45.680: INFO: Waiting for pod exec-volume-test-dynamicpv-fr5d to disappear
Jun  4 08:17:45.711: INFO: Pod exec-volume-test-dynamicpv-fr5d no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-fr5d
Jun  4 08:17:45.712: INFO: Deleting pod "exec-volume-test-dynamicpv-fr5d" in namespace "volume-272"
... skipping 148 lines ...
Jun  4 08:17:21.566: INFO: Creating resource for dynamic PV
Jun  4 08:17:21.566: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9019-e2e-scgcm6s
STEP: creating a claim
Jun  4 08:17:21.599: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-9019
Jun  4 08:17:21.729: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-9019" in namespace "provisioning-9019" to be "Succeeded or Failed"
Jun  4 08:17:21.760: INFO: Pod "volume-prep-provisioning-9019": Phase="Pending", Reason="", readiness=false. Elapsed: 30.825538ms
Jun  4 08:17:23.792: INFO: Pod "volume-prep-provisioning-9019": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062242978s
Jun  4 08:17:25.823: INFO: Pod "volume-prep-provisioning-9019": Phase="Pending", Reason="", readiness=false. Elapsed: 4.093524979s
Jun  4 08:17:27.855: INFO: Pod "volume-prep-provisioning-9019": Phase="Pending", Reason="", readiness=false. Elapsed: 6.125421119s
Jun  4 08:17:29.900: INFO: Pod "volume-prep-provisioning-9019": Phase="Pending", Reason="", readiness=false. Elapsed: 8.170234019s
Jun  4 08:17:31.932: INFO: Pod "volume-prep-provisioning-9019": Phase="Pending", Reason="", readiness=false. Elapsed: 10.20252852s
Jun  4 08:17:33.974: INFO: Pod "volume-prep-provisioning-9019": Phase="Pending", Reason="", readiness=false. Elapsed: 12.244688081s
Jun  4 08:17:36.006: INFO: Pod "volume-prep-provisioning-9019": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.276532772s
STEP: Saw pod success
Jun  4 08:17:36.006: INFO: Pod "volume-prep-provisioning-9019" satisfied condition "Succeeded or Failed"
Jun  4 08:17:36.006: INFO: Deleting pod "volume-prep-provisioning-9019" in namespace "provisioning-9019"
Jun  4 08:17:36.054: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-9019" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-lzkj
STEP: Checking for subpath error in container status
Jun  4 08:17:38.209: INFO: Deleting pod "pod-subpath-test-dynamicpv-lzkj" in namespace "provisioning-9019"
Jun  4 08:17:38.251: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-lzkj" to be fully deleted
STEP: Deleting pod
Jun  4 08:17:38.289: INFO: Deleting pod "pod-subpath-test-dynamicpv-lzkj" in namespace "provisioning-9019"
STEP: Deleting pvc
Jun  4 08:17:38.382: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comv28ps"
... skipping 251 lines ...
Jun  4 08:17:21.159: INFO: PersistentVolumeClaim pvc-v7ljq found but phase is Pending instead of Bound.
Jun  4 08:17:23.198: INFO: PersistentVolumeClaim pvc-v7ljq found and phase=Bound (12.224653634s)
Jun  4 08:17:23.198: INFO: Waiting up to 3m0s for PersistentVolume aws-ktw2m to have phase Bound
Jun  4 08:17:23.229: INFO: PersistentVolume aws-ktw2m found and phase=Bound (30.999068ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-7gqf
STEP: Creating a pod to test exec-volume-test
Jun  4 08:17:23.320: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-7gqf" in namespace "volume-3763" to be "Succeeded or Failed"
Jun  4 08:17:23.350: INFO: Pod "exec-volume-test-preprovisionedpv-7gqf": Phase="Pending", Reason="", readiness=false. Elapsed: 30.596978ms
Jun  4 08:17:25.382: INFO: Pod "exec-volume-test-preprovisionedpv-7gqf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062774389s
Jun  4 08:17:27.415: INFO: Pod "exec-volume-test-preprovisionedpv-7gqf": Phase="Pending", Reason="", readiness=false. Elapsed: 4.095183539s
Jun  4 08:17:29.446: INFO: Pod "exec-volume-test-preprovisionedpv-7gqf": Phase="Pending", Reason="", readiness=false. Elapsed: 6.126062059s
Jun  4 08:17:31.478: INFO: Pod "exec-volume-test-preprovisionedpv-7gqf": Phase="Pending", Reason="", readiness=false. Elapsed: 8.158167441s
Jun  4 08:17:33.509: INFO: Pod "exec-volume-test-preprovisionedpv-7gqf": Phase="Pending", Reason="", readiness=false. Elapsed: 10.189206562s
... skipping 7 lines ...
Jun  4 08:17:49.769: INFO: Pod "exec-volume-test-preprovisionedpv-7gqf": Phase="Pending", Reason="", readiness=false. Elapsed: 26.448908269s
Jun  4 08:17:51.800: INFO: Pod "exec-volume-test-preprovisionedpv-7gqf": Phase="Pending", Reason="", readiness=false. Elapsed: 28.480054463s
Jun  4 08:17:53.831: INFO: Pod "exec-volume-test-preprovisionedpv-7gqf": Phase="Pending", Reason="", readiness=false. Elapsed: 30.511596587s
Jun  4 08:17:55.862: INFO: Pod "exec-volume-test-preprovisionedpv-7gqf": Phase="Pending", Reason="", readiness=false. Elapsed: 32.54253168s
Jun  4 08:17:57.894: INFO: Pod "exec-volume-test-preprovisionedpv-7gqf": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.574084793s
STEP: Saw pod success
Jun  4 08:17:57.894: INFO: Pod "exec-volume-test-preprovisionedpv-7gqf" satisfied condition "Succeeded or Failed"
Jun  4 08:17:57.924: INFO: Trying to get logs from node ip-172-20-44-239.us-east-2.compute.internal pod exec-volume-test-preprovisionedpv-7gqf container exec-container-preprovisionedpv-7gqf: <nil>
STEP: delete the pod
Jun  4 08:17:57.995: INFO: Waiting for pod exec-volume-test-preprovisionedpv-7gqf to disappear
Jun  4 08:17:58.026: INFO: Pod exec-volume-test-preprovisionedpv-7gqf no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-7gqf
Jun  4 08:17:58.026: INFO: Deleting pod "exec-volume-test-preprovisionedpv-7gqf" in namespace "volume-3763"
STEP: Deleting pv and pvc
Jun  4 08:17:58.056: INFO: Deleting PersistentVolumeClaim "pvc-v7ljq"
Jun  4 08:17:58.088: INFO: Deleting PersistentVolume "aws-ktw2m"
Jun  4 08:17:58.255: INFO: Couldn't delete PD "aws://us-east-2a/vol-090e01bda24be020b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-090e01bda24be020b is currently attached to i-0346968af216cd18f
	status code: 400, request id: 92990a3f-20df-4e38-9101-7f812c4f5120
Jun  4 08:18:03.524: INFO: Couldn't delete PD "aws://us-east-2a/vol-090e01bda24be020b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-090e01bda24be020b is currently attached to i-0346968af216cd18f
	status code: 400, request id: 8bb7b75d-b547-4ddb-846c-d369a690c21c
Jun  4 08:18:08.795: INFO: Couldn't delete PD "aws://us-east-2a/vol-090e01bda24be020b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-090e01bda24be020b is currently attached to i-0346968af216cd18f
	status code: 400, request id: 382bbb7a-5119-486a-ba25-e039dd18861a
Jun  4 08:18:14.047: INFO: Couldn't delete PD "aws://us-east-2a/vol-090e01bda24be020b", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-090e01bda24be020b is currently attached to i-0346968af216cd18f
	status code: 400, request id: 9288d187-0f6f-46ae-bc6e-88ea0ca732b4
Jun  4 08:18:19.329: INFO: Successfully deleted PD "aws://us-east-2a/vol-090e01bda24be020b".
[AfterEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  4 08:18:19.329: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-3763" for this suite.
... skipping 20 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.HvoHaXSxC/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.HvoHaXSxC/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.HvoHaXSxC/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.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267

      Distro debian doesn't support ntfs -- skipping

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

      Driver supports dynamic provisioning, skipping InlineVolume pattern

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

      Distro debian doesn't support ntfs -- skipping

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

      /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 162 lines ...
Jun  4 08:17:39.631: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7772-e2e-scp82fm
STEP: creating a claim
Jun  4 08:17:39.663: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-57kw
STEP: Creating a pod to test subpath
Jun  4 08:17:39.763: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-57kw" in namespace "provisioning-7772" to be "Succeeded or Failed"
Jun  4 08:17:39.796: INFO: Pod "pod-subpath-test-dynamicpv-57kw": Phase="Pending", Reason="", readiness=false. Elapsed: 32.392868ms
Jun  4 08:17:41.828: INFO: Pod "pod-subpath-test-dynamicpv-57kw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.06475232s
Jun  4 08:17:43.860: INFO: Pod "pod-subpath-test-dynamicpv-57kw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.096618482s
Jun  4 08:17:45.892: INFO: Pod "pod-subpath-test-dynamicpv-57kw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.128535656s
Jun  4 08:17:47.923: INFO: Pod "pod-subpath-test-dynamicpv-57kw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.159473889s
Jun  4 08:17:49.957: INFO: Pod "pod-subpath-test-dynamicpv-57kw": Phase="Pending", Reason="", readiness=false. Elapsed: 10.193386151s
... skipping 2 lines ...
Jun  4 08:17:56.052: INFO: Pod "pod-subpath-test-dynamicpv-57kw": Phase="Pending", Reason="", readiness=false. Elapsed: 16.288281102s
Jun  4 08:17:58.084: INFO: Pod "pod-subpath-test-dynamicpv-57kw": Phase="Pending", Reason="", readiness=false. Elapsed: 18.320058686s
Jun  4 08:18:00.115: INFO: Pod "pod-subpath-test-dynamicpv-57kw": Phase="Pending", Reason="", readiness=false. Elapsed: 20.35130531s
Jun  4 08:18:02.146: INFO: Pod "pod-subpath-test-dynamicpv-57kw": Phase="Pending", Reason="", readiness=false. Elapsed: 22.382947974s
Jun  4 08:18:04.179: INFO: Pod "pod-subpath-test-dynamicpv-57kw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.415229449s
STEP: Saw pod success
Jun  4 08:18:04.179: INFO: Pod "pod-subpath-test-dynamicpv-57kw" satisfied condition "Succeeded or Failed"
Jun  4 08:18:04.213: INFO: Trying to get logs from node ip-172-20-49-5.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-57kw container test-container-subpath-dynamicpv-57kw: <nil>
STEP: delete the pod
Jun  4 08:18:04.288: INFO: Waiting for pod pod-subpath-test-dynamicpv-57kw to disappear
Jun  4 08:18:04.318: INFO: Pod pod-subpath-test-dynamicpv-57kw no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-57kw
Jun  4 08:18:04.319: INFO: Deleting pod "pod-subpath-test-dynamicpv-57kw" in namespace "provisioning-7772"
STEP: Creating pod pod-subpath-test-dynamicpv-57kw
STEP: Creating a pod to test subpath
Jun  4 08:18:04.382: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-57kw" in namespace "provisioning-7772" to be "Succeeded or Failed"
Jun  4 08:18:04.412: INFO: Pod "pod-subpath-test-dynamicpv-57kw": Phase="Pending", Reason="", readiness=false. Elapsed: 30.106048ms
Jun  4 08:18:06.444: INFO: Pod "pod-subpath-test-dynamicpv-57kw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062103013s
Jun  4 08:18:08.474: INFO: Pod "pod-subpath-test-dynamicpv-57kw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.092739428s
STEP: Saw pod success
Jun  4 08:18:08.474: INFO: Pod "pod-subpath-test-dynamicpv-57kw" satisfied condition "Succeeded or Failed"
Jun  4 08:18:08.505: INFO: Trying to get logs from node ip-172-20-49-5.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-57kw container test-container-subpath-dynamicpv-57kw: <nil>
STEP: delete the pod
Jun  4 08:18:08.577: INFO: Waiting for pod pod-subpath-test-dynamicpv-57kw to disappear
Jun  4 08:18:08.607: INFO: Pod pod-subpath-test-dynamicpv-57kw no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-57kw
Jun  4 08:18:08.608: INFO: Deleting pod "pod-subpath-test-dynamicpv-57kw" in namespace "provisioning-7772"
... skipping 102 lines ...
Jun  4 08:17:29.116: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7227-e2e-scc5pg5
STEP: creating a claim
Jun  4 08:17:29.148: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-qx86
STEP: Creating a pod to test subpath
Jun  4 08:17:29.244: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-qx86" in namespace "provisioning-7227" to be "Succeeded or Failed"
Jun  4 08:17:29.275: INFO: Pod "pod-subpath-test-dynamicpv-qx86": Phase="Pending", Reason="", readiness=false. Elapsed: 30.494088ms
Jun  4 08:17:31.307: INFO: Pod "pod-subpath-test-dynamicpv-qx86": Phase="Pending", Reason="", readiness=false. Elapsed: 2.06267802s
Jun  4 08:17:33.339: INFO: Pod "pod-subpath-test-dynamicpv-qx86": Phase="Pending", Reason="", readiness=false. Elapsed: 4.095150781s
Jun  4 08:17:35.372: INFO: Pod "pod-subpath-test-dynamicpv-qx86": Phase="Pending", Reason="", readiness=false. Elapsed: 6.127855902s
Jun  4 08:17:37.404: INFO: Pod "pod-subpath-test-dynamicpv-qx86": Phase="Pending", Reason="", readiness=false. Elapsed: 8.159353743s
Jun  4 08:17:39.436: INFO: Pod "pod-subpath-test-dynamicpv-qx86": Phase="Pending", Reason="", readiness=false. Elapsed: 10.191363025s
... skipping 2 lines ...
Jun  4 08:17:45.532: INFO: Pod "pod-subpath-test-dynamicpv-qx86": Phase="Pending", Reason="", readiness=false. Elapsed: 16.287697242s
Jun  4 08:17:47.565: INFO: Pod "pod-subpath-test-dynamicpv-qx86": Phase="Pending", Reason="", readiness=false. Elapsed: 18.320234104s
Jun  4 08:17:49.597: INFO: Pod "pod-subpath-test-dynamicpv-qx86": Phase="Pending", Reason="", readiness=false. Elapsed: 20.353029118s
Jun  4 08:17:51.630: INFO: Pod "pod-subpath-test-dynamicpv-qx86": Phase="Pending", Reason="", readiness=false. Elapsed: 22.385747902s
Jun  4 08:17:53.663: INFO: Pod "pod-subpath-test-dynamicpv-qx86": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.418965046s
STEP: Saw pod success
Jun  4 08:17:53.663: INFO: Pod "pod-subpath-test-dynamicpv-qx86" satisfied condition "Succeeded or Failed"
Jun  4 08:17:53.694: INFO: Trying to get logs from node ip-172-20-49-5.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-qx86 container test-container-subpath-dynamicpv-qx86: <nil>
STEP: delete the pod
Jun  4 08:17:53.766: INFO: Waiting for pod pod-subpath-test-dynamicpv-qx86 to disappear
Jun  4 08:17:53.805: INFO: Pod pod-subpath-test-dynamicpv-qx86 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-qx86
Jun  4 08:17:53.805: INFO: Deleting pod "pod-subpath-test-dynamicpv-qx86" in namespace "provisioning-7227"
... skipping 229 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  4 08:17:54.730: 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.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  4 08:17:54.885: INFO: Creating resource for dynamic PV
Jun  4 08:17:54.885: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-1415-e2e-sc6jwqr
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  4 08:18:01.111: INFO: Deleting pod "pod-7b5f2104-af73-49a3-a826-a54c5ac89b96" in namespace "volumemode-1415"
Jun  4 08:18:01.147: INFO: Wait up to 5m0s for pod "pod-7b5f2104-af73-49a3-a826-a54c5ac89b96" to be fully deleted
STEP: Deleting pvc
Jun  4 08:18:13.272: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comw9zl6"
Jun  4 08:18:13.305: INFO: Waiting up to 5m0s for PersistentVolume pvc-728429ac-2d4f-4d64-b68f-a90a241cf81f to get deleted
Jun  4 08:18:13.336: INFO: PersistentVolume pvc-728429ac-2d4f-4d64-b68f-a90a241cf81f found and phase=Released (30.974349ms)
... skipping 10 lines ...

• [SLOW TEST:38.863 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /tmp/kops.HvoHaXSxC/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.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 304 lines ...
Jun  4 08:18:13.926: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-940-e2e-sc8hbfv
STEP: creating a claim
Jun  4 08:18:13.958: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Jun  4 08:18:14.021: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun  4 08:18:14.086: INFO: Error updating pvc ebs.csi.aws.comsvt7h: PersistentVolumeClaim "ebs.csi.aws.comsvt7h" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-940-e2e-sc8hbfv",
  	... // 2 identical fields
  }

Jun  4 08:18:16.149: INFO: Error updating pvc ebs.csi.aws.comsvt7h: PersistentVolumeClaim "ebs.csi.aws.comsvt7h" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-940-e2e-sc8hbfv",
  	... // 2 identical fields
  }

Jun  4 08:18:18.151: INFO: Error updating pvc ebs.csi.aws.comsvt7h: PersistentVolumeClaim "ebs.csi.aws.comsvt7h" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-940-e2e-sc8hbfv",
  	... // 2 identical fields
  }

Jun  4 08:18:20.152: INFO: Error updating pvc ebs.csi.aws.comsvt7h: PersistentVolumeClaim "ebs.csi.aws.comsvt7h" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-940-e2e-sc8hbfv",
  	... // 2 identical fields
  }

Jun  4 08:18:22.151: INFO: Error updating pvc ebs.csi.aws.comsvt7h: PersistentVolumeClaim "ebs.csi.aws.comsvt7h" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-940-e2e-sc8hbfv",
  	... // 2 identical fields
  }

Jun  4 08:18:24.150: INFO: Error updating pvc ebs.csi.aws.comsvt7h: PersistentVolumeClaim "ebs.csi.aws.comsvt7h" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-940-e2e-sc8hbfv",
  	... // 2 identical fields
  }

Jun  4 08:18:26.151: INFO: Error updating pvc ebs.csi.aws.comsvt7h: PersistentVolumeClaim "ebs.csi.aws.comsvt7h" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-940-e2e-sc8hbfv",
  	... // 2 identical fields
  }

Jun  4 08:18:28.169: INFO: Error updating pvc ebs.csi.aws.comsvt7h: PersistentVolumeClaim "ebs.csi.aws.comsvt7h" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-940-e2e-sc8hbfv",
  	... // 2 identical fields
  }

Jun  4 08:18:30.150: INFO: Error updating pvc ebs.csi.aws.comsvt7h: PersistentVolumeClaim "ebs.csi.aws.comsvt7h" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-940-e2e-sc8hbfv",
  	... // 2 identical fields
  }

Jun  4 08:18:32.150: INFO: Error updating pvc ebs.csi.aws.comsvt7h: PersistentVolumeClaim "ebs.csi.aws.comsvt7h" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-940-e2e-sc8hbfv",
  	... // 2 identical fields
  }

Jun  4 08:18:34.151: INFO: Error updating pvc ebs.csi.aws.comsvt7h: PersistentVolumeClaim "ebs.csi.aws.comsvt7h" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-940-e2e-sc8hbfv",
  	... // 2 identical fields
  }

Jun  4 08:18:36.154: INFO: Error updating pvc ebs.csi.aws.comsvt7h: PersistentVolumeClaim "ebs.csi.aws.comsvt7h" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-940-e2e-sc8hbfv",
  	... // 2 identical fields
  }

Jun  4 08:18:38.150: INFO: Error updating pvc ebs.csi.aws.comsvt7h: PersistentVolumeClaim "ebs.csi.aws.comsvt7h" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-940-e2e-sc8hbfv",
  	... // 2 identical fields
  }

Jun  4 08:18:40.150: INFO: Error updating pvc ebs.csi.aws.comsvt7h: PersistentVolumeClaim "ebs.csi.aws.comsvt7h" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-940-e2e-sc8hbfv",
  	... // 2 identical fields
  }

Jun  4 08:18:42.151: INFO: Error updating pvc ebs.csi.aws.comsvt7h: PersistentVolumeClaim "ebs.csi.aws.comsvt7h" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-940-e2e-sc8hbfv",
  	... // 2 identical fields
  }

Jun  4 08:18:44.155: INFO: Error updating pvc ebs.csi.aws.comsvt7h: PersistentVolumeClaim "ebs.csi.aws.comsvt7h" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-940-e2e-sc8hbfv",
  	... // 2 identical fields
  }

Jun  4 08:18:44.222: INFO: Error updating pvc ebs.csi.aws.comsvt7h: PersistentVolumeClaim "ebs.csi.aws.comsvt7h" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 40 lines ...
Jun  4 08:17:49.523: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3647fhnrf
STEP: creating a claim
Jun  4 08:17:49.553: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-b8lx
STEP: Creating a pod to test subpath
Jun  4 08:17:49.645: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-b8lx" in namespace "provisioning-3647" to be "Succeeded or Failed"
Jun  4 08:17:49.675: INFO: Pod "pod-subpath-test-dynamicpv-b8lx": Phase="Pending", Reason="", readiness=false. Elapsed: 29.339699ms
Jun  4 08:17:51.705: INFO: Pod "pod-subpath-test-dynamicpv-b8lx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.059154183s
Jun  4 08:17:53.735: INFO: Pod "pod-subpath-test-dynamicpv-b8lx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.088975487s
Jun  4 08:17:55.765: INFO: Pod "pod-subpath-test-dynamicpv-b8lx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.1198189s
Jun  4 08:17:57.797: INFO: Pod "pod-subpath-test-dynamicpv-b8lx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.151157493s
Jun  4 08:17:59.830: INFO: Pod "pod-subpath-test-dynamicpv-b8lx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.184030617s
... skipping 10 lines ...
Jun  4 08:18:22.192: INFO: Pod "pod-subpath-test-dynamicpv-b8lx": Phase="Pending", Reason="", readiness=false. Elapsed: 32.546303117s
Jun  4 08:18:24.224: INFO: Pod "pod-subpath-test-dynamicpv-b8lx": Phase="Pending", Reason="", readiness=false. Elapsed: 34.578334103s
Jun  4 08:18:26.256: INFO: Pod "pod-subpath-test-dynamicpv-b8lx": Phase="Pending", Reason="", readiness=false. Elapsed: 36.610376178s
Jun  4 08:18:28.286: INFO: Pod "pod-subpath-test-dynamicpv-b8lx": Phase="Pending", Reason="", readiness=false. Elapsed: 38.640257595s
Jun  4 08:18:30.316: INFO: Pod "pod-subpath-test-dynamicpv-b8lx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 40.670018182s
STEP: Saw pod success
Jun  4 08:18:30.316: INFO: Pod "pod-subpath-test-dynamicpv-b8lx" satisfied condition "Succeeded or Failed"
Jun  4 08:18:30.345: INFO: Trying to get logs from node ip-172-20-49-219.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-b8lx container test-container-volume-dynamicpv-b8lx: <nil>
STEP: delete the pod
Jun  4 08:18:30.420: INFO: Waiting for pod pod-subpath-test-dynamicpv-b8lx to disappear
Jun  4 08:18:30.449: INFO: Pod pod-subpath-test-dynamicpv-b8lx no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-b8lx
Jun  4 08:18:30.449: INFO: Deleting pod "pod-subpath-test-dynamicpv-b8lx" in namespace "provisioning-3647"
... skipping 156 lines ...
Jun  4 08:18:14.550: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-5077n6h4w
STEP: creating a claim
Jun  4 08:18:14.581: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-6zjq
STEP: Creating a pod to test exec-volume-test
Jun  4 08:18:14.675: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-6zjq" in namespace "volume-5077" to be "Succeeded or Failed"
Jun  4 08:18:14.704: INFO: Pod "exec-volume-test-dynamicpv-6zjq": Phase="Pending", Reason="", readiness=false. Elapsed: 29.534778ms
Jun  4 08:18:16.739: INFO: Pod "exec-volume-test-dynamicpv-6zjq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.064539394s
Jun  4 08:18:18.770: INFO: Pod "exec-volume-test-dynamicpv-6zjq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.09520781s
Jun  4 08:18:20.800: INFO: Pod "exec-volume-test-dynamicpv-6zjq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.125689237s
Jun  4 08:18:22.832: INFO: Pod "exec-volume-test-dynamicpv-6zjq": Phase="Pending", Reason="", readiness=false. Elapsed: 8.156975104s
Jun  4 08:18:24.863: INFO: Pod "exec-volume-test-dynamicpv-6zjq": Phase="Pending", Reason="", readiness=false. Elapsed: 10.18817668s
Jun  4 08:18:26.894: INFO: Pod "exec-volume-test-dynamicpv-6zjq": Phase="Pending", Reason="", readiness=false. Elapsed: 12.219228006s
Jun  4 08:18:28.926: INFO: Pod "exec-volume-test-dynamicpv-6zjq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.251610242s
STEP: Saw pod success
Jun  4 08:18:28.926: INFO: Pod "exec-volume-test-dynamicpv-6zjq" satisfied condition "Succeeded or Failed"
Jun  4 08:18:28.956: INFO: Trying to get logs from node ip-172-20-49-5.us-east-2.compute.internal pod exec-volume-test-dynamicpv-6zjq container exec-container-dynamicpv-6zjq: <nil>
STEP: delete the pod
Jun  4 08:18:29.022: INFO: Waiting for pod exec-volume-test-dynamicpv-6zjq to disappear
Jun  4 08:18:29.051: INFO: Pod exec-volume-test-dynamicpv-6zjq no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-6zjq
Jun  4 08:18:29.051: INFO: Deleting pod "exec-volume-test-dynamicpv-6zjq" in namespace "volume-5077"
... skipping 82 lines ...
Jun  4 08:18:19.364: INFO: Creating resource for dynamic PV
Jun  4 08:18:19.364: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-5321wrlhq
STEP: creating a claim
STEP: Expanding non-expandable pvc
Jun  4 08:18:19.471: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun  4 08:18:19.536: INFO: Error updating pvc aws728fr: PersistentVolumeClaim "aws728fr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5321wrlhq",
  	... // 2 identical fields
  }

Jun  4 08:18:21.605: INFO: Error updating pvc aws728fr: PersistentVolumeClaim "aws728fr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5321wrlhq",
  	... // 2 identical fields
  }

Jun  4 08:18:23.601: INFO: Error updating pvc aws728fr: PersistentVolumeClaim "aws728fr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5321wrlhq",
  	... // 2 identical fields
  }

Jun  4 08:18:25.607: INFO: Error updating pvc aws728fr: PersistentVolumeClaim "aws728fr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5321wrlhq",
  	... // 2 identical fields
  }

Jun  4 08:18:27.600: INFO: Error updating pvc aws728fr: PersistentVolumeClaim "aws728fr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5321wrlhq",
  	... // 2 identical fields
  }

Jun  4 08:18:29.597: INFO: Error updating pvc aws728fr: PersistentVolumeClaim "aws728fr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5321wrlhq",
  	... // 2 identical fields
  }

Jun  4 08:18:31.600: INFO: Error updating pvc aws728fr: PersistentVolumeClaim "aws728fr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5321wrlhq",
  	... // 2 identical fields
  }

Jun  4 08:18:33.608: INFO: Error updating pvc aws728fr: PersistentVolumeClaim "aws728fr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5321wrlhq",
  	... // 2 identical fields
  }

Jun  4 08:18:35.598: INFO: Error updating pvc aws728fr: PersistentVolumeClaim "aws728fr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5321wrlhq",
  	... // 2 identical fields
  }

Jun  4 08:18:37.598: INFO: Error updating pvc aws728fr: PersistentVolumeClaim "aws728fr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5321wrlhq",
  	... // 2 identical fields
  }

Jun  4 08:18:39.600: INFO: Error updating pvc aws728fr: PersistentVolumeClaim "aws728fr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5321wrlhq",
  	... // 2 identical fields
  }

Jun  4 08:18:41.597: INFO: Error updating pvc aws728fr: PersistentVolumeClaim "aws728fr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5321wrlhq",
  	... // 2 identical fields
  }

Jun  4 08:18:43.599: INFO: Error updating pvc aws728fr: PersistentVolumeClaim "aws728fr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5321wrlhq",
  	... // 2 identical fields
  }

Jun  4 08:18:45.603: INFO: Error updating pvc aws728fr: PersistentVolumeClaim "aws728fr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5321wrlhq",
  	... // 2 identical fields
  }

Jun  4 08:18:47.603: INFO: Error updating pvc aws728fr: PersistentVolumeClaim "aws728fr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5321wrlhq",
  	... // 2 identical fields
  }

Jun  4 08:18:49.620: INFO: Error updating pvc aws728fr: PersistentVolumeClaim "aws728fr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-5321wrlhq",
  	... // 2 identical fields
  }

Jun  4 08:18:49.687: INFO: Error updating pvc aws728fr: PersistentVolumeClaim "aws728fr" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 165 lines ...
Jun  4 08:18:54.725: INFO: Waiting for pod aws-client to disappear
Jun  4 08:18:54.755: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun  4 08:18:54.755: INFO: Deleting PersistentVolumeClaim "pvc-h5j6s"
Jun  4 08:18:54.787: INFO: Deleting PersistentVolume "aws-khvck"
Jun  4 08:18:55.022: INFO: Couldn't delete PD "aws://us-east-2a/vol-0b24e4c5aa1561a68", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0b24e4c5aa1561a68 is currently attached to i-067b46a95c9863b19
	status code: 400, request id: 26bee351-7778-4be6-b2f4-ed38b666f756
Jun  4 08:19:00.270: INFO: Successfully deleted PD "aws://us-east-2a/vol-0b24e4c5aa1561a68".
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  4 08:19:00.270: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-9892" for this suite.
... skipping 20 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.HvoHaXSxC/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.HvoHaXSxC/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.HvoHaXSxC/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.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256

      Driver supports dynamic provisioning, skipping InlineVolume pattern

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

      Not enough topologies in cluster -- skipping

      /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 62 lines ...
Jun  4 08:17:33.928: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-5207-e2e-scbmlq8      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-5207    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-5207-e2e-scbmlq8,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-5207    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-5207-e2e-scbmlq8,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-5207    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-5207-e2e-scbmlq8,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-5207-e2e-scbmlq8    08c080ee-4140-418d-a445-408ec461af7b 4570 0 2021-06-04 08:17:33 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-04 08:17:33 +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-hj822 pvc- provisioning-5207  4ee558d6-be78-4cb5-83c9-bb6d1090f24f 4576 0 2021-06-04 08:17:34 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-04 08:17:34 +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-5207-e2e-scbmlq8,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-d051f5f7-4a1d-4758-983d-a0d27ebab455 in namespace provisioning-5207
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun  4 08:18:14.283: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-bmd8c" in namespace "provisioning-5207" to be "Succeeded or Failed"
Jun  4 08:18:14.312: INFO: Pod "pvc-volume-tester-writer-bmd8c": Phase="Pending", Reason="", readiness=false. Elapsed: 29.765909ms
Jun  4 08:18:16.343: INFO: Pod "pvc-volume-tester-writer-bmd8c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.060749884s
Jun  4 08:18:18.374: INFO: Pod "pvc-volume-tester-writer-bmd8c": Phase="Pending", Reason="", readiness=false. Elapsed: 4.09164409s
Jun  4 08:18:20.405: INFO: Pod "pvc-volume-tester-writer-bmd8c": Phase="Pending", Reason="", readiness=false. Elapsed: 6.122463957s
Jun  4 08:18:22.436: INFO: Pod "pvc-volume-tester-writer-bmd8c": Phase="Pending", Reason="", readiness=false. Elapsed: 8.153501494s
Jun  4 08:18:24.474: INFO: Pod "pvc-volume-tester-writer-bmd8c": Phase="Pending", Reason="", readiness=false. Elapsed: 10.191365801s
... skipping 7 lines ...
Jun  4 08:18:40.726: INFO: Pod "pvc-volume-tester-writer-bmd8c": Phase="Pending", Reason="", readiness=false. Elapsed: 26.443851348s
Jun  4 08:18:42.757: INFO: Pod "pvc-volume-tester-writer-bmd8c": Phase="Pending", Reason="", readiness=false. Elapsed: 28.474129127s
Jun  4 08:18:44.788: INFO: Pod "pvc-volume-tester-writer-bmd8c": Phase="Pending", Reason="", readiness=false. Elapsed: 30.505041936s
Jun  4 08:18:46.818: INFO: Pod "pvc-volume-tester-writer-bmd8c": Phase="Pending", Reason="", readiness=false. Elapsed: 32.535740694s
Jun  4 08:18:48.849: INFO: Pod "pvc-volume-tester-writer-bmd8c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.566167374s
STEP: Saw pod success
Jun  4 08:18:48.849: INFO: Pod "pvc-volume-tester-writer-bmd8c" satisfied condition "Succeeded or Failed"
Jun  4 08:18:48.913: INFO: Pod pvc-volume-tester-writer-bmd8c has the following logs: 
Jun  4 08:18:48.913: INFO: Deleting pod "pvc-volume-tester-writer-bmd8c" in namespace "provisioning-5207"
Jun  4 08:18:48.951: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-bmd8c" 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-49-5.us-east-2.compute.internal"
Jun  4 08:18:49.083: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-cs7qv" in namespace "provisioning-5207" to be "Succeeded or Failed"
Jun  4 08:18:49.113: INFO: Pod "pvc-volume-tester-reader-cs7qv": Phase="Pending", Reason="", readiness=false. Elapsed: 29.857698ms
Jun  4 08:18:51.147: INFO: Pod "pvc-volume-tester-reader-cs7qv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.064115267s
STEP: Saw pod success
Jun  4 08:18:51.147: INFO: Pod "pvc-volume-tester-reader-cs7qv" satisfied condition "Succeeded or Failed"
Jun  4 08:18:51.211: INFO: Pod pvc-volume-tester-reader-cs7qv has the following logs: hello world

Jun  4 08:18:51.211: INFO: Deleting pod "pvc-volume-tester-reader-cs7qv" in namespace "provisioning-5207"
Jun  4 08:18:51.248: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-cs7qv" to be fully deleted
Jun  4 08:18:51.278: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-hj822] to have phase Bound
Jun  4 08:18:51.309: INFO: PersistentVolumeClaim pvc-hj822 found and phase=Bound (30.974388ms)
... skipping 154 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  /tmp/kops.HvoHaXSxC/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.HvoHaXSxC/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.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 36 lines ...
Jun  4 08:18:29.742: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1211-e2e-sc54dk8
STEP: creating a claim
Jun  4 08:18:29.778: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-k7fz
STEP: Creating a pod to test subpath
Jun  4 08:18:29.882: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-k7fz" in namespace "provisioning-1211" to be "Succeeded or Failed"
Jun  4 08:18:29.926: INFO: Pod "pod-subpath-test-dynamicpv-k7fz": Phase="Pending", Reason="", readiness=false. Elapsed: 43.538307ms
Jun  4 08:18:31.957: INFO: Pod "pod-subpath-test-dynamicpv-k7fz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.074917404s
Jun  4 08:18:33.992: INFO: Pod "pod-subpath-test-dynamicpv-k7fz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.109631122s
Jun  4 08:18:36.024: INFO: Pod "pod-subpath-test-dynamicpv-k7fz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.142504811s
Jun  4 08:18:38.056: INFO: Pod "pod-subpath-test-dynamicpv-k7fz": Phase="Pending", Reason="", readiness=false. Elapsed: 8.173825908s
Jun  4 08:18:40.088: INFO: Pod "pod-subpath-test-dynamicpv-k7fz": Phase="Pending", Reason="", readiness=false. Elapsed: 10.205653196s
... skipping 4 lines ...
Jun  4 08:18:50.256: INFO: Pod "pod-subpath-test-dynamicpv-k7fz": Phase="Pending", Reason="", readiness=false. Elapsed: 20.374267689s
Jun  4 08:18:52.288: INFO: Pod "pod-subpath-test-dynamicpv-k7fz": Phase="Pending", Reason="", readiness=false. Elapsed: 22.40630949s
Jun  4 08:18:54.321: INFO: Pod "pod-subpath-test-dynamicpv-k7fz": Phase="Pending", Reason="", readiness=false. Elapsed: 24.438826618s
Jun  4 08:18:56.353: INFO: Pod "pod-subpath-test-dynamicpv-k7fz": Phase="Pending", Reason="", readiness=false. Elapsed: 26.470889388s
Jun  4 08:18:58.387: INFO: Pod "pod-subpath-test-dynamicpv-k7fz": Phase="Succeeded", Reason="", readiness=false. Elapsed: 28.505209208s
STEP: Saw pod success
Jun  4 08:18:58.387: INFO: Pod "pod-subpath-test-dynamicpv-k7fz" satisfied condition "Succeeded or Failed"
Jun  4 08:18:58.419: INFO: Trying to get logs from node ip-172-20-51-225.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-k7fz container test-container-subpath-dynamicpv-k7fz: <nil>
STEP: delete the pod
Jun  4 08:18:58.496: INFO: Waiting for pod pod-subpath-test-dynamicpv-k7fz to disappear
Jun  4 08:18:58.527: INFO: Pod pod-subpath-test-dynamicpv-k7fz no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-k7fz
Jun  4 08:18:58.527: INFO: Deleting pod "pod-subpath-test-dynamicpv-k7fz" in namespace "provisioning-1211"
... skipping 152 lines ...
Jun  4 08:18:39.214: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7814-e2e-scwjjjj
STEP: creating a claim
Jun  4 08:18:39.245: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-qsdm
STEP: Creating a pod to test subpath
Jun  4 08:18:39.341: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-qsdm" in namespace "provisioning-7814" to be "Succeeded or Failed"
Jun  4 08:18:39.372: INFO: Pod "pod-subpath-test-dynamicpv-qsdm": Phase="Pending", Reason="", readiness=false. Elapsed: 30.953698ms
Jun  4 08:18:41.403: INFO: Pod "pod-subpath-test-dynamicpv-qsdm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062286506s
Jun  4 08:18:43.437: INFO: Pod "pod-subpath-test-dynamicpv-qsdm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.096292925s
Jun  4 08:18:45.469: INFO: Pod "pod-subpath-test-dynamicpv-qsdm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.127932394s
Jun  4 08:18:47.499: INFO: Pod "pod-subpath-test-dynamicpv-qsdm": Phase="Pending", Reason="", readiness=false. Elapsed: 8.158574592s
Jun  4 08:18:49.535: INFO: Pod "pod-subpath-test-dynamicpv-qsdm": Phase="Pending", Reason="", readiness=false. Elapsed: 10.193685392s
... skipping 2 lines ...
Jun  4 08:18:55.628: INFO: Pod "pod-subpath-test-dynamicpv-qsdm": Phase="Pending", Reason="", readiness=false. Elapsed: 16.28710476s
Jun  4 08:18:57.659: INFO: Pod "pod-subpath-test-dynamicpv-qsdm": Phase="Pending", Reason="", readiness=false. Elapsed: 18.31861143s
Jun  4 08:18:59.691: INFO: Pod "pod-subpath-test-dynamicpv-qsdm": Phase="Pending", Reason="", readiness=false. Elapsed: 20.350373601s
Jun  4 08:19:01.723: INFO: Pod "pod-subpath-test-dynamicpv-qsdm": Phase="Pending", Reason="", readiness=false. Elapsed: 22.382313432s
Jun  4 08:19:03.755: INFO: Pod "pod-subpath-test-dynamicpv-qsdm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.413853112s
STEP: Saw pod success
Jun  4 08:19:03.755: INFO: Pod "pod-subpath-test-dynamicpv-qsdm" satisfied condition "Succeeded or Failed"
Jun  4 08:19:03.785: INFO: Trying to get logs from node ip-172-20-49-5.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-qsdm container test-container-volume-dynamicpv-qsdm: <nil>
STEP: delete the pod
Jun  4 08:19:03.857: INFO: Waiting for pod pod-subpath-test-dynamicpv-qsdm to disappear
Jun  4 08:19:03.887: INFO: Pod pod-subpath-test-dynamicpv-qsdm no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-qsdm
Jun  4 08:19:03.887: INFO: Deleting pod "pod-subpath-test-dynamicpv-qsdm" in namespace "provisioning-7814"
... skipping 199 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  4 08:18:49.801: 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.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Jun  4 08:18:49.969: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  4 08:18:49.969: INFO: Creating resource for dynamic PV
Jun  4 08:18:49.969: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9402zw8xc
STEP: creating a claim
Jun  4 08:18:50.006: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-dg9s
STEP: Checking for subpath error in container status
Jun  4 08:19:14.188: INFO: Deleting pod "pod-subpath-test-dynamicpv-dg9s" in namespace "provisioning-9402"
Jun  4 08:19:14.225: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-dg9s" to be fully deleted
STEP: Deleting pod
Jun  4 08:19:24.283: INFO: Deleting pod "pod-subpath-test-dynamicpv-dg9s" in namespace "provisioning-9402"
STEP: Deleting pvc
Jun  4 08:19:24.373: INFO: Deleting PersistentVolumeClaim "awsr7pr4"
... skipping 14 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.HvoHaXSxC/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.HvoHaXSxC/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath file is outside the volume [Slow][LinuxOnly]
      /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
------------------------------
[BeforeEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 57 lines ...
Jun  4 08:19:29.948: INFO: Pod aws-client still exists
Jun  4 08:19:31.916: INFO: Waiting for pod aws-client to disappear
Jun  4 08:19:31.947: INFO: Pod aws-client still exists
Jun  4 08:19:33.916: INFO: Waiting for pod aws-client to disappear
Jun  4 08:19:33.949: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
Jun  4 08:19:34.109: INFO: Couldn't delete PD "aws://us-east-2a/vol-0b2c318fb9de2ee07", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0b2c318fb9de2ee07 is currently attached to i-067b46a95c9863b19
	status code: 400, request id: a467d5c0-423e-4bb4-b97a-b2b225601713
Jun  4 08:19:39.405: INFO: Couldn't delete PD "aws://us-east-2a/vol-0b2c318fb9de2ee07", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0b2c318fb9de2ee07 is currently attached to i-067b46a95c9863b19
	status code: 400, request id: 1f6dc807-85c3-4b85-b4a8-01ac5b9f5ce5
Jun  4 08:19:44.662: INFO: Successfully deleted PD "aws://us-east-2a/vol-0b2c318fb9de2ee07".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  4 08:19:44.662: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-7804" for this suite.
... skipping 386 lines ...
Jun  4 08:19:00.718: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-5594t4h6t
STEP: creating a claim
Jun  4 08:19:00.750: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-kbjc
STEP: Creating a pod to test exec-volume-test
Jun  4 08:19:00.847: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-kbjc" in namespace "volume-5594" to be "Succeeded or Failed"
Jun  4 08:19:00.877: INFO: Pod "exec-volume-test-dynamicpv-kbjc": Phase="Pending", Reason="", readiness=false. Elapsed: 30.101679ms
Jun  4 08:19:02.910: INFO: Pod "exec-volume-test-dynamicpv-kbjc": Phase="Pending", Reason="", readiness=false. Elapsed: 2.063292299s
Jun  4 08:19:04.942: INFO: Pod "exec-volume-test-dynamicpv-kbjc": Phase="Pending", Reason="", readiness=false. Elapsed: 4.095254169s
Jun  4 08:19:06.973: INFO: Pod "exec-volume-test-dynamicpv-kbjc": Phase="Pending", Reason="", readiness=false. Elapsed: 6.12635104s
Jun  4 08:19:09.005: INFO: Pod "exec-volume-test-dynamicpv-kbjc": Phase="Pending", Reason="", readiness=false. Elapsed: 8.158148811s
Jun  4 08:19:11.037: INFO: Pod "exec-volume-test-dynamicpv-kbjc": Phase="Pending", Reason="", readiness=false. Elapsed: 10.190047181s
Jun  4 08:19:13.068: INFO: Pod "exec-volume-test-dynamicpv-kbjc": Phase="Pending", Reason="", readiness=false. Elapsed: 12.221318822s
Jun  4 08:19:15.100: INFO: Pod "exec-volume-test-dynamicpv-kbjc": Phase="Pending", Reason="", readiness=false. Elapsed: 14.253540844s
Jun  4 08:19:17.132: INFO: Pod "exec-volume-test-dynamicpv-kbjc": Phase="Pending", Reason="", readiness=false. Elapsed: 16.285421217s
Jun  4 08:19:19.163: INFO: Pod "exec-volume-test-dynamicpv-kbjc": Phase="Pending", Reason="", readiness=false. Elapsed: 18.316169869s
Jun  4 08:19:21.195: INFO: Pod "exec-volume-test-dynamicpv-kbjc": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.348437011s
STEP: Saw pod success
Jun  4 08:19:21.195: INFO: Pod "exec-volume-test-dynamicpv-kbjc" satisfied condition "Succeeded or Failed"
Jun  4 08:19:21.227: INFO: Trying to get logs from node ip-172-20-49-219.us-east-2.compute.internal pod exec-volume-test-dynamicpv-kbjc container exec-container-dynamicpv-kbjc: <nil>
STEP: delete the pod
Jun  4 08:19:21.300: INFO: Waiting for pod exec-volume-test-dynamicpv-kbjc to disappear
Jun  4 08:19:21.330: INFO: Pod exec-volume-test-dynamicpv-kbjc no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-kbjc
Jun  4 08:19:21.330: INFO: Deleting pod "exec-volume-test-dynamicpv-kbjc" in namespace "volume-5594"
... skipping 429 lines ...
Jun  4 08:19:13.507: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  4 08:19:14.053: INFO: Successfully created a new PD: "aws://us-east-2a/vol-0a8b03a6955863645".
Jun  4 08:19:14.053: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-lk92
STEP: Creating a pod to test exec-volume-test
Jun  4 08:19:14.087: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-lk92" in namespace "volume-5189" to be "Succeeded or Failed"
Jun  4 08:19:14.123: INFO: Pod "exec-volume-test-inlinevolume-lk92": Phase="Pending", Reason="", readiness=false. Elapsed: 36.831798ms
Jun  4 08:19:16.154: INFO: Pod "exec-volume-test-inlinevolume-lk92": Phase="Pending", Reason="", readiness=false. Elapsed: 2.06695931s
Jun  4 08:19:18.185: INFO: Pod "exec-volume-test-inlinevolume-lk92": Phase="Pending", Reason="", readiness=false. Elapsed: 4.097891563s
Jun  4 08:19:20.216: INFO: Pod "exec-volume-test-inlinevolume-lk92": Phase="Pending", Reason="", readiness=false. Elapsed: 6.129353726s
Jun  4 08:19:22.249: INFO: Pod "exec-volume-test-inlinevolume-lk92": Phase="Pending", Reason="", readiness=false. Elapsed: 8.162251928s
Jun  4 08:19:24.280: INFO: Pod "exec-volume-test-inlinevolume-lk92": Phase="Pending", Reason="", readiness=false. Elapsed: 10.19365218s
... skipping 7 lines ...
Jun  4 08:19:40.532: INFO: Pod "exec-volume-test-inlinevolume-lk92": Phase="Pending", Reason="", readiness=false. Elapsed: 26.445231826s
Jun  4 08:19:42.562: INFO: Pod "exec-volume-test-inlinevolume-lk92": Phase="Pending", Reason="", readiness=false. Elapsed: 28.47497277s
Jun  4 08:19:44.593: INFO: Pod "exec-volume-test-inlinevolume-lk92": Phase="Pending", Reason="", readiness=false. Elapsed: 30.506708463s
Jun  4 08:19:46.624: INFO: Pod "exec-volume-test-inlinevolume-lk92": Phase="Pending", Reason="", readiness=false. Elapsed: 32.537250568s
Jun  4 08:19:48.654: INFO: Pod "exec-volume-test-inlinevolume-lk92": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.567489662s
STEP: Saw pod success
Jun  4 08:19:48.654: INFO: Pod "exec-volume-test-inlinevolume-lk92" satisfied condition "Succeeded or Failed"
Jun  4 08:19:48.685: INFO: Trying to get logs from node ip-172-20-49-5.us-east-2.compute.internal pod exec-volume-test-inlinevolume-lk92 container exec-container-inlinevolume-lk92: <nil>
STEP: delete the pod
Jun  4 08:19:48.756: INFO: Waiting for pod exec-volume-test-inlinevolume-lk92 to disappear
Jun  4 08:19:48.785: INFO: Pod exec-volume-test-inlinevolume-lk92 no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-lk92
Jun  4 08:19:48.785: INFO: Deleting pod "exec-volume-test-inlinevolume-lk92" in namespace "volume-5189"
Jun  4 08:19:48.990: INFO: Couldn't delete PD "aws://us-east-2a/vol-0a8b03a6955863645", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a8b03a6955863645 is currently attached to i-0e9ce963557e07e18
	status code: 400, request id: 6efbcfac-e211-43b2-bfda-f3a0b997d758
Jun  4 08:19:54.244: INFO: Couldn't delete PD "aws://us-east-2a/vol-0a8b03a6955863645", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a8b03a6955863645 is currently attached to i-0e9ce963557e07e18
	status code: 400, request id: 328d9a6d-0369-4326-9eb5-d8ee292e84a9
Jun  4 08:19:59.508: INFO: Couldn't delete PD "aws://us-east-2a/vol-0a8b03a6955863645", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a8b03a6955863645 is currently attached to i-0e9ce963557e07e18
	status code: 400, request id: 3b215f6f-9dfb-4d1e-ab5a-e39edd397ea4
Jun  4 08:20:04.784: INFO: Successfully deleted PD "aws://us-east-2a/vol-0a8b03a6955863645".
[AfterEach] [Testpattern: Inline-volume (ext4)] volumes
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  4 08:20:04.784: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-5189" for this suite.
... skipping 20 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.HvoHaXSxC/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.HvoHaXSxC/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    /tmp/kops.HvoHaXSxC/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.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 76 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  4 08:19:29.294: 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.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  4 08:19:29.447: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  4 08:19:29.447: INFO: Creating resource for dynamic PV
Jun  4 08:19:29.447: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-5662wkwsq
STEP: creating a claim
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  4 08:19:35.664: INFO: Deleting pod "pod-6d044e5c-266b-4998-96c0-310cd8f56769" in namespace "volumemode-5662"
Jun  4 08:19:35.696: INFO: Wait up to 5m0s for pod "pod-6d044e5c-266b-4998-96c0-310cd8f56769" to be fully deleted
STEP: Deleting pvc
Jun  4 08:19:43.819: INFO: Deleting PersistentVolumeClaim "awshxwpv"
Jun  4 08:19:43.850: INFO: Waiting up to 5m0s for PersistentVolume pvc-ed4cefad-4d52-427f-bd24-def52c6794d9 to get deleted
Jun  4 08:19:43.881: INFO: PersistentVolume pvc-ed4cefad-4d52-427f-bd24-def52c6794d9 found and phase=Released (31.070009ms)
... skipping 13 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.HvoHaXSxC/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.HvoHaXSxC/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (block volmode)] volumeMode
    /tmp/kops.HvoHaXSxC/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.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic Snapshot (delete policy)] snapshottable[Feature:VolumeSnapshotDataSource]
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic Snapshot (delete policy)] snapshottable[Feature:VolumeSnapshotDataSource]
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 6 lines ...
Jun  4 08:17:19.266: INFO: Creating resource for dynamic PV
Jun  4 08:17:19.266: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-9097-e2e-scjnfw5
STEP: creating a claim
Jun  4 08:17:19.298: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun  4 08:17:19.392: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-8xhq2" in namespace "snapshotting-9097" to be "Succeeded or Failed"
Jun  4 08:17:19.422: INFO: Pod "pvc-snapshottable-tester-8xhq2": Phase="Pending", Reason="", readiness=false. Elapsed: 29.664228ms
Jun  4 08:17:21.455: INFO: Pod "pvc-snapshottable-tester-8xhq2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062087798s
Jun  4 08:17:23.486: INFO: Pod "pvc-snapshottable-tester-8xhq2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.093352438s
Jun  4 08:17:25.517: INFO: Pod "pvc-snapshottable-tester-8xhq2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.124808979s
Jun  4 08:17:27.548: INFO: Pod "pvc-snapshottable-tester-8xhq2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.155090359s
Jun  4 08:17:29.578: INFO: Pod "pvc-snapshottable-tester-8xhq2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.18547878s
... skipping 3 lines ...
Jun  4 08:17:37.706: INFO: Pod "pvc-snapshottable-tester-8xhq2": Phase="Pending", Reason="", readiness=false. Elapsed: 18.313920654s
Jun  4 08:17:39.738: INFO: Pod "pvc-snapshottable-tester-8xhq2": Phase="Pending", Reason="", readiness=false. Elapsed: 20.345740867s
Jun  4 08:17:41.770: INFO: Pod "pvc-snapshottable-tester-8xhq2": Phase="Pending", Reason="", readiness=false. Elapsed: 22.377019609s
Jun  4 08:17:43.801: INFO: Pod "pvc-snapshottable-tester-8xhq2": Phase="Pending", Reason="", readiness=false. Elapsed: 24.408711711s
Jun  4 08:17:45.835: INFO: Pod "pvc-snapshottable-tester-8xhq2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.442933653s
STEP: Saw pod success
Jun  4 08:17:45.835: INFO: Pod "pvc-snapshottable-tester-8xhq2" satisfied condition "Succeeded or Failed"
Jun  4 08:17:45.900: INFO: Pod pvc-snapshottable-tester-8xhq2 has the following logs: 
Jun  4 08:17:45.900: INFO: Deleting pod "pvc-snapshottable-tester-8xhq2" in namespace "snapshotting-9097"
Jun  4 08:17:45.936: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-8xhq2" to be fully deleted
Jun  4 08:17:45.967: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comgt4ch] to have phase Bound
Jun  4 08:17:45.999: INFO: PersistentVolumeClaim ebs.csi.aws.comgt4ch found and phase=Bound (31.262687ms)
STEP: [init] checking the claim
... skipping 41 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.HvoHaXSxC/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  4 08:18:49.353: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-kqjwz" in namespace "snapshotting-9097" to be "Succeeded or Failed"
Jun  4 08:18:49.386: INFO: Pod "pvc-snapshottable-data-tester-kqjwz": Phase="Pending", Reason="", readiness=false. Elapsed: 32.685948ms
Jun  4 08:18:51.419: INFO: Pod "pvc-snapshottable-data-tester-kqjwz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.065271897s
Jun  4 08:18:53.451: INFO: Pod "pvc-snapshottable-data-tester-kqjwz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.097169409s
Jun  4 08:18:55.482: INFO: Pod "pvc-snapshottable-data-tester-kqjwz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.128801367s
Jun  4 08:18:57.514: INFO: Pod "pvc-snapshottable-data-tester-kqjwz": Phase="Pending", Reason="", readiness=false. Elapsed: 8.160471736s
Jun  4 08:18:59.548: INFO: Pod "pvc-snapshottable-data-tester-kqjwz": Phase="Pending", Reason="", readiness=false. Elapsed: 10.194825158s
Jun  4 08:19:01.579: INFO: Pod "pvc-snapshottable-data-tester-kqjwz": Phase="Pending", Reason="", readiness=false. Elapsed: 12.225311969s
Jun  4 08:19:03.612: INFO: Pod "pvc-snapshottable-data-tester-kqjwz": Phase="Pending", Reason="", readiness=false. Elapsed: 14.258954699s
Jun  4 08:19:05.643: INFO: Pod "pvc-snapshottable-data-tester-kqjwz": Phase="Pending", Reason="", readiness=false. Elapsed: 16.28990128s
Jun  4 08:19:07.675: INFO: Pod "pvc-snapshottable-data-tester-kqjwz": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.32175858s
STEP: Saw pod success
Jun  4 08:19:07.675: INFO: Pod "pvc-snapshottable-data-tester-kqjwz" satisfied condition "Succeeded or Failed"
Jun  4 08:19:07.740: INFO: Pod pvc-snapshottable-data-tester-kqjwz has the following logs: 
Jun  4 08:19:07.740: INFO: Deleting pod "pvc-snapshottable-data-tester-kqjwz" in namespace "snapshotting-9097"
Jun  4 08:19:07.787: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-kqjwz" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun  4 08:19:21.952: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-9097 exec restored-pvc-tester-w5r8f --namespace=snapshotting-9097 -- cat /mnt/test/data'
... skipping 256 lines ...
    /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:108
      
      /tmp/kops.HvoHaXSxC/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.HvoHaXSxC/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-9097 exec restored-pvc-tester-w5r8f --namespace=snapshotting-9097 -- 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-9097 exec restored-pvc-tester-w5r8f --namespace=snapshotting-9097 -- 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.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:602
------------------------------
S
... skipping 7 lines ...

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

      Distro debian doesn't support ntfs -- skipping

      /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 185 lines ...
Jun  4 08:20:14.167: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

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

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

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

    /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:92
------------------------------
... skipping 146 lines ...
Jun  4 08:19:39.554: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  4 08:19:40.035: INFO: Successfully created a new PD: "aws://us-east-2a/vol-01dd22a67e61d9d85".
Jun  4 08:19:40.035: INFO: Creating resource for inline volume
STEP: Creating pod exec-volume-test-inlinevolume-h56g
STEP: Creating a pod to test exec-volume-test
Jun  4 08:19:40.075: INFO: Waiting up to 5m0s for pod "exec-volume-test-inlinevolume-h56g" in namespace "volume-1177" to be "Succeeded or Failed"
Jun  4 08:19:40.106: INFO: Pod "exec-volume-test-inlinevolume-h56g": Phase="Pending", Reason="", readiness=false. Elapsed: 30.957188ms
Jun  4 08:19:42.137: INFO: Pod "exec-volume-test-inlinevolume-h56g": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062206831s
Jun  4 08:19:44.169: INFO: Pod "exec-volume-test-inlinevolume-h56g": Phase="Pending", Reason="", readiness=false. Elapsed: 4.094419696s
Jun  4 08:19:46.202: INFO: Pod "exec-volume-test-inlinevolume-h56g": Phase="Pending", Reason="", readiness=false. Elapsed: 6.12709371s
Jun  4 08:19:48.234: INFO: Pod "exec-volume-test-inlinevolume-h56g": Phase="Pending", Reason="", readiness=false. Elapsed: 8.159267053s
Jun  4 08:19:50.269: INFO: Pod "exec-volume-test-inlinevolume-h56g": Phase="Pending", Reason="", readiness=false. Elapsed: 10.19442774s
Jun  4 08:19:52.300: INFO: Pod "exec-volume-test-inlinevolume-h56g": Phase="Pending", Reason="", readiness=false. Elapsed: 12.225658654s
Jun  4 08:19:54.332: INFO: Pod "exec-volume-test-inlinevolume-h56g": Phase="Pending", Reason="", readiness=false. Elapsed: 14.256905508s
Jun  4 08:19:56.363: INFO: Pod "exec-volume-test-inlinevolume-h56g": Phase="Pending", Reason="", readiness=false. Elapsed: 16.288360443s
Jun  4 08:19:58.394: INFO: Pod "exec-volume-test-inlinevolume-h56g": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.318793597s
STEP: Saw pod success
Jun  4 08:19:58.394: INFO: Pod "exec-volume-test-inlinevolume-h56g" satisfied condition "Succeeded or Failed"
Jun  4 08:19:58.424: INFO: Trying to get logs from node ip-172-20-44-239.us-east-2.compute.internal pod exec-volume-test-inlinevolume-h56g container exec-container-inlinevolume-h56g: <nil>
STEP: delete the pod
Jun  4 08:19:58.499: INFO: Waiting for pod exec-volume-test-inlinevolume-h56g to disappear
Jun  4 08:19:58.533: INFO: Pod exec-volume-test-inlinevolume-h56g no longer exists
STEP: Deleting pod exec-volume-test-inlinevolume-h56g
Jun  4 08:19:58.533: INFO: Deleting pod "exec-volume-test-inlinevolume-h56g" in namespace "volume-1177"
Jun  4 08:19:58.696: INFO: Couldn't delete PD "aws://us-east-2a/vol-01dd22a67e61d9d85", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01dd22a67e61d9d85 is currently attached to i-0346968af216cd18f
	status code: 400, request id: adf503a4-1a20-49b6-8507-92a00ac10bfa
Jun  4 08:20:03.978: INFO: Couldn't delete PD "aws://us-east-2a/vol-01dd22a67e61d9d85", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01dd22a67e61d9d85 is currently attached to i-0346968af216cd18f
	status code: 400, request id: 565abd83-3f3f-4b92-b238-60e02a7ca623
Jun  4 08:20:09.265: INFO: Couldn't delete PD "aws://us-east-2a/vol-01dd22a67e61d9d85", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01dd22a67e61d9d85 is currently attached to i-0346968af216cd18f
	status code: 400, request id: 4acec528-6984-4b82-99f1-03e102a9ef0a
Jun  4 08:20:14.561: INFO: Couldn't delete PD "aws://us-east-2a/vol-01dd22a67e61d9d85", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-01dd22a67e61d9d85 is currently attached to i-0346968af216cd18f
	status code: 400, request id: b108cfe7-c4c4-4e8a-a000-763fc4da2318
Jun  4 08:20:19.847: INFO: Successfully deleted PD "aws://us-east-2a/vol-01dd22a67e61d9d85".
[AfterEach] [Testpattern: Inline-volume (default fs)] volumes
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  4 08:20:19.847: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-1177" for this suite.
... skipping 190 lines ...
Jun  4 08:19:44.803: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-316kdglt
STEP: creating a claim
Jun  4 08:19:44.843: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-z2ww
STEP: Creating a pod to test subpath
Jun  4 08:19:44.934: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-z2ww" in namespace "provisioning-316" to be "Succeeded or Failed"
Jun  4 08:19:44.965: INFO: Pod "pod-subpath-test-dynamicpv-z2ww": Phase="Pending", Reason="", readiness=false. Elapsed: 30.550858ms
Jun  4 08:19:46.995: INFO: Pod "pod-subpath-test-dynamicpv-z2ww": Phase="Pending", Reason="", readiness=false. Elapsed: 2.060611423s
Jun  4 08:19:49.025: INFO: Pod "pod-subpath-test-dynamicpv-z2ww": Phase="Pending", Reason="", readiness=false. Elapsed: 4.090655128s
Jun  4 08:19:51.056: INFO: Pod "pod-subpath-test-dynamicpv-z2ww": Phase="Pending", Reason="", readiness=false. Elapsed: 6.121812244s
Jun  4 08:19:53.086: INFO: Pod "pod-subpath-test-dynamicpv-z2ww": Phase="Pending", Reason="", readiness=false. Elapsed: 8.151706868s
Jun  4 08:19:55.116: INFO: Pod "pod-subpath-test-dynamicpv-z2ww": Phase="Pending", Reason="", readiness=false. Elapsed: 10.181661842s
Jun  4 08:19:57.147: INFO: Pod "pod-subpath-test-dynamicpv-z2ww": Phase="Pending", Reason="", readiness=false. Elapsed: 12.212468818s
Jun  4 08:19:59.178: INFO: Pod "pod-subpath-test-dynamicpv-z2ww": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.243802094s
STEP: Saw pod success
Jun  4 08:19:59.178: INFO: Pod "pod-subpath-test-dynamicpv-z2ww" satisfied condition "Succeeded or Failed"
Jun  4 08:19:59.209: INFO: Trying to get logs from node ip-172-20-49-5.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-z2ww container test-container-volume-dynamicpv-z2ww: <nil>
STEP: delete the pod
Jun  4 08:19:59.281: INFO: Waiting for pod pod-subpath-test-dynamicpv-z2ww to disappear
Jun  4 08:19:59.310: INFO: Pod pod-subpath-test-dynamicpv-z2ww no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-z2ww
Jun  4 08:19:59.310: INFO: Deleting pod "pod-subpath-test-dynamicpv-z2ww" in namespace "provisioning-316"
... skipping 56 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  4 08:19:34.550: 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.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun  4 08:19:34.705: INFO: Creating resource for dynamic PV
Jun  4 08:19:34.705: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1631-e2e-sc669bl
STEP: creating a claim
Jun  4 08:19:34.737: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-bfgd
STEP: Checking for subpath error in container status
Jun  4 08:19:58.899: INFO: Deleting pod "pod-subpath-test-dynamicpv-bfgd" in namespace "provisioning-1631"
Jun  4 08:19:58.933: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-bfgd" to be fully deleted
STEP: Deleting pod
Jun  4 08:20:13.004: INFO: Deleting pod "pod-subpath-test-dynamicpv-bfgd" in namespace "provisioning-1631"
STEP: Deleting pvc
Jun  4 08:20:13.099: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comcmwrj"
... skipping 12 lines ...

• [SLOW TEST:58.836 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.HvoHaXSxC/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.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  4 08:19:59.304: 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.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  4 08:19:59.454: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  4 08:19:59.835: INFO: Successfully created a new PD: "aws://us-east-2a/vol-022fc2f81813e8883".
Jun  4 08:19:59.835: INFO: Creating resource for pre-provisioned PV
Jun  4 08:19:59.835: INFO: Creating PVC and PV
... skipping 5 lines ...
Jun  4 08:20:04.067: INFO: PersistentVolumeClaim pvc-zfr9w found but phase is Pending instead of Bound.
Jun  4 08:20:06.098: INFO: PersistentVolumeClaim pvc-zfr9w found but phase is Pending instead of Bound.
Jun  4 08:20:08.129: INFO: PersistentVolumeClaim pvc-zfr9w found and phase=Bound (8.157167502s)
Jun  4 08:20:08.129: INFO: Waiting up to 3m0s for PersistentVolume aws-56dlz to have phase Bound
Jun  4 08:20:08.159: INFO: PersistentVolume aws-56dlz found and phase=Bound (29.699259ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  4 08:20:10.340: INFO: Deleting pod "pod-0fe7fb61-032c-4d90-afe4-9e547cfb105b" in namespace "volumemode-2754"
Jun  4 08:20:10.370: INFO: Wait up to 5m0s for pod "pod-0fe7fb61-032c-4d90-afe4-9e547cfb105b" to be fully deleted
STEP: Deleting pv and pvc
Jun  4 08:20:14.434: INFO: Deleting PersistentVolumeClaim "pvc-zfr9w"
Jun  4 08:20:14.465: INFO: Deleting PersistentVolume "aws-56dlz"
Jun  4 08:20:14.647: INFO: Couldn't delete PD "aws://us-east-2a/vol-022fc2f81813e8883", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-022fc2f81813e8883 is currently attached to i-067b46a95c9863b19
	status code: 400, request id: 26179a55-07d2-499f-94d4-b9baf62bbf2a
Jun  4 08:20:19.950: INFO: Couldn't delete PD "aws://us-east-2a/vol-022fc2f81813e8883", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-022fc2f81813e8883 is currently attached to i-067b46a95c9863b19
	status code: 400, request id: a4f57ca8-eafe-4e1f-a000-6bbdce6fdb59
Jun  4 08:20:25.223: INFO: Couldn't delete PD "aws://us-east-2a/vol-022fc2f81813e8883", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-022fc2f81813e8883 is currently attached to i-067b46a95c9863b19
	status code: 400, request id: 95fee62a-0af1-4d87-9d69-8afeb59f2d42
Jun  4 08:20:30.492: INFO: Couldn't delete PD "aws://us-east-2a/vol-022fc2f81813e8883", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-022fc2f81813e8883 is currently attached to i-067b46a95c9863b19
	status code: 400, request id: f724e405-94b2-4eb0-b140-ec0f777aa84b
Jun  4 08:20:35.755: INFO: Couldn't delete PD "aws://us-east-2a/vol-022fc2f81813e8883", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-022fc2f81813e8883 is currently attached to i-067b46a95c9863b19
	status code: 400, request id: 918b0c70-879b-4dae-a3c1-9ad0c7fee3a5
Jun  4 08:20:41.034: INFO: Successfully deleted PD "aws://us-east-2a/vol-022fc2f81813e8883".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  4 08:20:41.034: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-2754" for this suite.
... skipping 3 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.HvoHaXSxC/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.HvoHaXSxC/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
    /tmp/kops.HvoHaXSxC/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.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  4 08:20:41.099: INFO: Driver ebs.csi.aws.com doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
... skipping 92 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.HvoHaXSxC/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.HvoHaXSxC/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Inline-volume (default fs)] subPath
    /tmp/kops.HvoHaXSxC/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.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278

      Driver supports dynamic provisioning, skipping InlineVolume pattern

      /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:233
------------------------------
... skipping 12 lines ...
Jun  4 08:19:47.150: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass volume-566345v9h
STEP: creating a claim
Jun  4 08:19:47.183: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod exec-volume-test-dynamicpv-2trb
STEP: Creating a pod to test exec-volume-test
Jun  4 08:19:47.279: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-2trb" in namespace "volume-5663" to be "Succeeded or Failed"
Jun  4 08:19:47.316: INFO: Pod "exec-volume-test-dynamicpv-2trb": Phase="Pending", Reason="", readiness=false. Elapsed: 36.808178ms
Jun  4 08:19:49.347: INFO: Pod "exec-volume-test-dynamicpv-2trb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.067892642s
Jun  4 08:19:51.380: INFO: Pod "exec-volume-test-dynamicpv-2trb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.100327678s
Jun  4 08:19:53.411: INFO: Pod "exec-volume-test-dynamicpv-2trb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.131565222s
Jun  4 08:19:55.447: INFO: Pod "exec-volume-test-dynamicpv-2trb": Phase="Pending", Reason="", readiness=false. Elapsed: 8.168072646s
Jun  4 08:19:57.479: INFO: Pod "exec-volume-test-dynamicpv-2trb": Phase="Pending", Reason="", readiness=false. Elapsed: 10.199551531s
... skipping 2 lines ...
Jun  4 08:20:03.597: INFO: Pod "exec-volume-test-dynamicpv-2trb": Phase="Pending", Reason="", readiness=false. Elapsed: 16.317981419s
Jun  4 08:20:05.629: INFO: Pod "exec-volume-test-dynamicpv-2trb": Phase="Pending", Reason="", readiness=false. Elapsed: 18.349886504s
Jun  4 08:20:07.661: INFO: Pod "exec-volume-test-dynamicpv-2trb": Phase="Pending", Reason="", readiness=false. Elapsed: 20.381683101s
Jun  4 08:20:09.696: INFO: Pod "exec-volume-test-dynamicpv-2trb": Phase="Pending", Reason="", readiness=false. Elapsed: 22.416641956s
Jun  4 08:20:11.727: INFO: Pod "exec-volume-test-dynamicpv-2trb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.447649723s
STEP: Saw pod success
Jun  4 08:20:11.727: INFO: Pod "exec-volume-test-dynamicpv-2trb" satisfied condition "Succeeded or Failed"
Jun  4 08:20:11.757: INFO: Trying to get logs from node ip-172-20-49-5.us-east-2.compute.internal pod exec-volume-test-dynamicpv-2trb container exec-container-dynamicpv-2trb: <nil>
STEP: delete the pod
Jun  4 08:20:11.831: INFO: Waiting for pod exec-volume-test-dynamicpv-2trb to disappear
Jun  4 08:20:11.862: INFO: Pod exec-volume-test-dynamicpv-2trb no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-2trb
Jun  4 08:20:11.862: INFO: Deleting pod "exec-volume-test-dynamicpv-2trb" in namespace "volume-5663"
... skipping 93 lines ...
Jun  4 08:20:48.524: INFO: AfterEach: Cleaning up test resources


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

  Only supported for providers [vsphere] (not aws)

  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:64
------------------------------
... skipping 10 lines ...
Jun  4 08:18:08.565: INFO: Creating resource for dynamic PV
Jun  4 08:18:08.565: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-5926-e2e-sczdtvd
STEP: creating a claim
Jun  4 08:18:08.596: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun  4 08:18:08.689: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-wq99c" in namespace "snapshotting-5926" to be "Succeeded or Failed"
Jun  4 08:18:08.720: INFO: Pod "pvc-snapshottable-tester-wq99c": Phase="Pending", Reason="", readiness=false. Elapsed: 30.162168ms
Jun  4 08:18:10.751: INFO: Pod "pvc-snapshottable-tester-wq99c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061745574s
Jun  4 08:18:12.782: INFO: Pod "pvc-snapshottable-tester-wq99c": Phase="Pending", Reason="", readiness=false. Elapsed: 4.092074049s
Jun  4 08:18:14.813: INFO: Pod "pvc-snapshottable-tester-wq99c": Phase="Pending", Reason="", readiness=false. Elapsed: 6.123210695s
Jun  4 08:18:16.844: INFO: Pod "pvc-snapshottable-tester-wq99c": Phase="Pending", Reason="", readiness=false. Elapsed: 8.15466937s
Jun  4 08:18:18.875: INFO: Pod "pvc-snapshottable-tester-wq99c": Phase="Pending", Reason="", readiness=false. Elapsed: 10.185902317s
Jun  4 08:18:20.907: INFO: Pod "pvc-snapshottable-tester-wq99c": Phase="Pending", Reason="", readiness=false. Elapsed: 12.217114843s
Jun  4 08:18:22.938: INFO: Pod "pvc-snapshottable-tester-wq99c": Phase="Pending", Reason="", readiness=false. Elapsed: 14.248093289s
Jun  4 08:18:24.968: INFO: Pod "pvc-snapshottable-tester-wq99c": Phase="Pending", Reason="", readiness=false. Elapsed: 16.278621436s
Jun  4 08:18:27.000: INFO: Pod "pvc-snapshottable-tester-wq99c": Phase="Pending", Reason="", readiness=false. Elapsed: 18.310252282s
Jun  4 08:18:29.032: INFO: Pod "pvc-snapshottable-tester-wq99c": Phase="Pending", Reason="", readiness=false. Elapsed: 20.342331379s
Jun  4 08:18:31.063: INFO: Pod "pvc-snapshottable-tester-wq99c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.373431696s
STEP: Saw pod success
Jun  4 08:18:31.063: INFO: Pod "pvc-snapshottable-tester-wq99c" satisfied condition "Succeeded or Failed"
Jun  4 08:18:31.124: INFO: Pod pvc-snapshottable-tester-wq99c has the following logs: 
Jun  4 08:18:31.125: INFO: Deleting pod "pvc-snapshottable-tester-wq99c" in namespace "snapshotting-5926"
Jun  4 08:18:31.165: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-wq99c" to be fully deleted
Jun  4 08:18:31.196: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.comg8jgb] to have phase Bound
Jun  4 08:18:31.226: INFO: PersistentVolumeClaim ebs.csi.aws.comg8jgb found and phase=Bound (30.102329ms)
STEP: [init] checking the claim
... skipping 51 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.HvoHaXSxC/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  4 08:19:18.676: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-ffgx8" in namespace "snapshotting-5926" to be "Succeeded or Failed"
Jun  4 08:19:18.707: INFO: Pod "pvc-snapshottable-data-tester-ffgx8": Phase="Pending", Reason="", readiness=false. Elapsed: 31.0979ms
Jun  4 08:19:20.738: INFO: Pod "pvc-snapshottable-data-tester-ffgx8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061955422s
Jun  4 08:19:22.770: INFO: Pod "pvc-snapshottable-data-tester-ffgx8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.093752523s
Jun  4 08:19:24.801: INFO: Pod "pvc-snapshottable-data-tester-ffgx8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.125197456s
Jun  4 08:19:26.834: INFO: Pod "pvc-snapshottable-data-tester-ffgx8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.158125157s
Jun  4 08:19:28.865: INFO: Pod "pvc-snapshottable-data-tester-ffgx8": Phase="Pending", Reason="", readiness=false. Elapsed: 10.189140171s
Jun  4 08:19:30.898: INFO: Pod "pvc-snapshottable-data-tester-ffgx8": Phase="Pending", Reason="", readiness=false. Elapsed: 12.221405074s
Jun  4 08:19:32.932: INFO: Pod "pvc-snapshottable-data-tester-ffgx8": Phase="Pending", Reason="", readiness=false. Elapsed: 14.256044987s
Jun  4 08:19:34.964: INFO: Pod "pvc-snapshottable-data-tester-ffgx8": Phase="Pending", Reason="", readiness=false. Elapsed: 16.28805439s
Jun  4 08:19:36.998: INFO: Pod "pvc-snapshottable-data-tester-ffgx8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.321962353s
STEP: Saw pod success
Jun  4 08:19:36.998: INFO: Pod "pvc-snapshottable-data-tester-ffgx8" satisfied condition "Succeeded or Failed"
Jun  4 08:19:37.059: INFO: Pod pvc-snapshottable-data-tester-ffgx8 has the following logs: 
Jun  4 08:19:37.060: INFO: Deleting pod "pvc-snapshottable-data-tester-ffgx8" in namespace "snapshotting-5926"
Jun  4 08:19:37.096: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-ffgx8" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun  4 08:19:57.249: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-5926 exec restored-pvc-tester-ftw6r --namespace=snapshotting-5926 -- cat /mnt/test/data'
... skipping 205 lines ...
Jun  4 08:19:45.599: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8199-e2e-scgtjmz
STEP: creating a claim
Jun  4 08:19:45.631: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-t72m
STEP: Creating a pod to test subpath
Jun  4 08:19:45.742: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-t72m" in namespace "provisioning-8199" to be "Succeeded or Failed"
Jun  4 08:19:45.774: INFO: Pod "pod-subpath-test-dynamicpv-t72m": Phase="Pending", Reason="", readiness=false. Elapsed: 31.733229ms
Jun  4 08:19:47.805: INFO: Pod "pod-subpath-test-dynamicpv-t72m": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062644343s
Jun  4 08:19:49.847: INFO: Pod "pod-subpath-test-dynamicpv-t72m": Phase="Pending", Reason="", readiness=false. Elapsed: 4.104537616s
Jun  4 08:19:51.883: INFO: Pod "pod-subpath-test-dynamicpv-t72m": Phase="Pending", Reason="", readiness=false. Elapsed: 6.140643751s
Jun  4 08:19:53.919: INFO: Pod "pod-subpath-test-dynamicpv-t72m": Phase="Pending", Reason="", readiness=false. Elapsed: 8.176506115s
Jun  4 08:19:55.950: INFO: Pod "pod-subpath-test-dynamicpv-t72m": Phase="Pending", Reason="", readiness=false. Elapsed: 10.207770441s
... skipping 4 lines ...
Jun  4 08:20:06.113: INFO: Pod "pod-subpath-test-dynamicpv-t72m": Phase="Pending", Reason="", readiness=false. Elapsed: 20.37069195s
Jun  4 08:20:08.145: INFO: Pod "pod-subpath-test-dynamicpv-t72m": Phase="Pending", Reason="", readiness=false. Elapsed: 22.402574485s
Jun  4 08:20:10.177: INFO: Pod "pod-subpath-test-dynamicpv-t72m": Phase="Pending", Reason="", readiness=false. Elapsed: 24.434280561s
Jun  4 08:20:12.208: INFO: Pod "pod-subpath-test-dynamicpv-t72m": Phase="Pending", Reason="", readiness=false. Elapsed: 26.465994879s
Jun  4 08:20:14.240: INFO: Pod "pod-subpath-test-dynamicpv-t72m": Phase="Succeeded", Reason="", readiness=false. Elapsed: 28.497705076s
STEP: Saw pod success
Jun  4 08:20:14.240: INFO: Pod "pod-subpath-test-dynamicpv-t72m" satisfied condition "Succeeded or Failed"
Jun  4 08:20:14.272: INFO: Trying to get logs from node ip-172-20-49-219.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-t72m container test-container-volume-dynamicpv-t72m: <nil>
STEP: delete the pod
Jun  4 08:20:14.351: INFO: Waiting for pod pod-subpath-test-dynamicpv-t72m to disappear
Jun  4 08:20:14.381: INFO: Pod pod-subpath-test-dynamicpv-t72m no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-t72m
Jun  4 08:20:14.381: INFO: Deleting pod "pod-subpath-test-dynamicpv-t72m" in namespace "provisioning-8199"
... skipping 634 lines ...
Jun  4 08:20:30.165: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-325742hqn
STEP: creating a claim
Jun  4 08:20:30.195: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-5k2n
STEP: Creating a pod to test subpath
Jun  4 08:20:30.288: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-5k2n" in namespace "provisioning-3257" to be "Succeeded or Failed"
Jun  4 08:20:30.317: INFO: Pod "pod-subpath-test-dynamicpv-5k2n": Phase="Pending", Reason="", readiness=false. Elapsed: 29.335789ms
Jun  4 08:20:32.348: INFO: Pod "pod-subpath-test-dynamicpv-5k2n": Phase="Pending", Reason="", readiness=false. Elapsed: 2.059900856s
Jun  4 08:20:34.380: INFO: Pod "pod-subpath-test-dynamicpv-5k2n": Phase="Pending", Reason="", readiness=false. Elapsed: 4.091754014s
Jun  4 08:20:36.411: INFO: Pod "pod-subpath-test-dynamicpv-5k2n": Phase="Pending", Reason="", readiness=false. Elapsed: 6.123052552s
Jun  4 08:20:38.443: INFO: Pod "pod-subpath-test-dynamicpv-5k2n": Phase="Pending", Reason="", readiness=false. Elapsed: 8.154657771s
Jun  4 08:20:40.473: INFO: Pod "pod-subpath-test-dynamicpv-5k2n": Phase="Pending", Reason="", readiness=false. Elapsed: 10.185400182s
... skipping 2 lines ...
Jun  4 08:20:46.567: INFO: Pod "pod-subpath-test-dynamicpv-5k2n": Phase="Pending", Reason="", readiness=false. Elapsed: 16.278668681s
Jun  4 08:20:48.597: INFO: Pod "pod-subpath-test-dynamicpv-5k2n": Phase="Pending", Reason="", readiness=false. Elapsed: 18.30912338s
Jun  4 08:20:50.628: INFO: Pod "pod-subpath-test-dynamicpv-5k2n": Phase="Pending", Reason="", readiness=false. Elapsed: 20.340332868s
Jun  4 08:20:52.659: INFO: Pod "pod-subpath-test-dynamicpv-5k2n": Phase="Pending", Reason="", readiness=false. Elapsed: 22.37094645s
Jun  4 08:20:54.692: INFO: Pod "pod-subpath-test-dynamicpv-5k2n": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.403803199s
STEP: Saw pod success
Jun  4 08:20:54.692: INFO: Pod "pod-subpath-test-dynamicpv-5k2n" satisfied condition "Succeeded or Failed"
Jun  4 08:20:54.721: INFO: Trying to get logs from node ip-172-20-44-239.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-5k2n container test-container-subpath-dynamicpv-5k2n: <nil>
STEP: delete the pod
Jun  4 08:20:54.808: INFO: Waiting for pod pod-subpath-test-dynamicpv-5k2n to disappear
Jun  4 08:20:54.853: INFO: Pod pod-subpath-test-dynamicpv-5k2n no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-5k2n
Jun  4 08:20:54.853: INFO: Deleting pod "pod-subpath-test-dynamicpv-5k2n" in namespace "provisioning-3257"
... skipping 60 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  4 08:20:19.921: INFO: >>> kubeConfig: /root/.kube/config
STEP: Building a namespace api object, basename provisioning
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail if subpath directory is outside the volume [Slow][LinuxOnly]
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun  4 08:20:20.079: INFO: Creating resource for dynamic PV
Jun  4 08:20:20.079: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9456-e2e-scvwcv9
STEP: creating a claim
Jun  4 08:20:20.117: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-qrjs
STEP: Checking for subpath error in container status
Jun  4 08:20:46.293: INFO: Deleting pod "pod-subpath-test-dynamicpv-qrjs" in namespace "provisioning-9456"
Jun  4 08:20:46.333: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-qrjs" to be fully deleted
STEP: Deleting pod
Jun  4 08:20:58.395: INFO: Deleting pod "pod-subpath-test-dynamicpv-qrjs" in namespace "provisioning-9456"
STEP: Deleting pvc
Jun  4 08:20:58.484: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comtkbwg"
... skipping 12 lines ...

• [SLOW TEST:58.849 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
    should fail if subpath directory is outside the volume [Slow][LinuxOnly]
    /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volume-expand
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volume-expand
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 6 lines ...
Jun  4 08:20:49.951: INFO: Creating resource for dynamic PV
Jun  4 08:20:49.951: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-2112-e2e-sck86zc
STEP: creating a claim
STEP: Expanding non-expandable pvc
Jun  4 08:20:50.071: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun  4 08:20:50.134: INFO: Error updating pvc ebs.csi.aws.comj2tls: PersistentVolumeClaim "ebs.csi.aws.comj2tls" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2112-e2e-sck86zc",
  	... // 2 identical fields
  }

Jun  4 08:20:52.198: INFO: Error updating pvc ebs.csi.aws.comj2tls: PersistentVolumeClaim "ebs.csi.aws.comj2tls" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2112-e2e-sck86zc",
  	... // 2 identical fields
  }

Jun  4 08:20:54.199: INFO: Error updating pvc ebs.csi.aws.comj2tls: PersistentVolumeClaim "ebs.csi.aws.comj2tls" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2112-e2e-sck86zc",
  	... // 2 identical fields
  }

Jun  4 08:20:56.199: INFO: Error updating pvc ebs.csi.aws.comj2tls: PersistentVolumeClaim "ebs.csi.aws.comj2tls" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2112-e2e-sck86zc",
  	... // 2 identical fields
  }

Jun  4 08:20:58.203: INFO: Error updating pvc ebs.csi.aws.comj2tls: PersistentVolumeClaim "ebs.csi.aws.comj2tls" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-2112-e2e-sck86zc",
  	... // 2 identical fields
  }

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

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

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

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

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

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

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

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

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

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

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

Jun  4 08:21:20.262: INFO: Error updating pvc ebs.csi.aws.comj2tls: PersistentVolumeClaim "ebs.csi.aws.comj2tls" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 800 lines ...
STEP: Deleting pod hostexec-ip-172-20-49-5.us-east-2.compute.internal-66vd7 in namespace volumemode-5374
Jun  4 08:21:12.742: INFO: Deleting pod "pod-650d3dc0-7912-423f-b235-032c58c83907" in namespace "volumemode-5374"
Jun  4 08:21:12.772: INFO: Wait up to 5m0s for pod "pod-650d3dc0-7912-423f-b235-032c58c83907" to be fully deleted
STEP: Deleting pv and pvc
Jun  4 08:21:22.831: INFO: Deleting PersistentVolumeClaim "pvc-qlznh"
Jun  4 08:21:22.862: INFO: Deleting PersistentVolume "aws-wthfs"
Jun  4 08:21:23.049: INFO: Couldn't delete PD "aws://us-east-2a/vol-0455d9de8da61d0a0", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0455d9de8da61d0a0 is currently attached to i-0e9ce963557e07e18
	status code: 400, request id: 68d6a797-2fc2-496b-9185-abe5c3263d07
Jun  4 08:21:28.391: INFO: Couldn't delete PD "aws://us-east-2a/vol-0455d9de8da61d0a0", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0455d9de8da61d0a0 is currently attached to i-0e9ce963557e07e18
	status code: 400, request id: 9f873edf-44ef-4339-a10e-0834854d588e
Jun  4 08:21:33.686: INFO: Couldn't delete PD "aws://us-east-2a/vol-0455d9de8da61d0a0", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0455d9de8da61d0a0 is currently attached to i-0e9ce963557e07e18
	status code: 400, request id: c9d82eeb-221b-4cce-b05e-e8bef6db43fa
Jun  4 08:21:38.977: INFO: Successfully deleted PD "aws://us-east-2a/vol-0455d9de8da61d0a0".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  4 08:21:38.977: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-5374" for this suite.
... skipping 101 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  4 08:20:50.356: 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.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Jun  4 08:20:50.509: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  4 08:20:50.509: INFO: Creating resource for dynamic PV
Jun  4 08:20:50.509: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2453s4zqn
STEP: creating a claim
Jun  4 08:20:50.542: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-b2sn
STEP: Checking for subpath error in container status
Jun  4 08:21:14.715: INFO: Deleting pod "pod-subpath-test-dynamicpv-b2sn" in namespace "provisioning-2453"
Jun  4 08:21:14.753: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-b2sn" to be fully deleted
STEP: Deleting pod
Jun  4 08:21:24.820: INFO: Deleting pod "pod-subpath-test-dynamicpv-b2sn" in namespace "provisioning-2453"
STEP: Deleting pvc
Jun  4 08:21:24.921: INFO: Deleting PersistentVolumeClaim "aws7jmsd"
... skipping 13 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.HvoHaXSxC/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.HvoHaXSxC/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50
      should fail if subpath directory is outside the volume [Slow][LinuxOnly]
      /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
Jun  4 08:21:40.175: INFO: Driver supports dynamic provisioning, skipping InlineVolume pattern
[AfterEach] [Testpattern: Inline-volume (default fs)] subPath
... skipping 25 lines ...

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

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

    /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 54 lines ...
Jun  4 08:18:45.973: INFO: Creating resource for dynamic PV
Jun  4 08:18:45.974: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-4642-e2e-scbpj9z
STEP: creating a claim
Jun  4 08:18:46.005: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun  4 08:18:46.099: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-5td6h" in namespace "snapshotting-4642" to be "Succeeded or Failed"
Jun  4 08:18:46.128: INFO: Pod "pvc-snapshottable-tester-5td6h": Phase="Pending", Reason="", readiness=false. Elapsed: 29.511029ms
Jun  4 08:18:48.159: INFO: Pod "pvc-snapshottable-tester-5td6h": Phase="Pending", Reason="", readiness=false. Elapsed: 2.059955437s
Jun  4 08:18:50.190: INFO: Pod "pvc-snapshottable-tester-5td6h": Phase="Pending", Reason="", readiness=false. Elapsed: 4.091112986s
Jun  4 08:18:52.220: INFO: Pod "pvc-snapshottable-tester-5td6h": Phase="Pending", Reason="", readiness=false. Elapsed: 6.121581136s
Jun  4 08:18:54.250: INFO: Pod "pvc-snapshottable-tester-5td6h": Phase="Pending", Reason="", readiness=false. Elapsed: 8.151389546s
Jun  4 08:18:56.280: INFO: Pod "pvc-snapshottable-tester-5td6h": Phase="Pending", Reason="", readiness=false. Elapsed: 10.181412196s
Jun  4 08:18:58.311: INFO: Pod "pvc-snapshottable-tester-5td6h": Phase="Pending", Reason="", readiness=false. Elapsed: 12.212209656s
Jun  4 08:19:00.343: INFO: Pod "pvc-snapshottable-tester-5td6h": Phase="Pending", Reason="", readiness=false. Elapsed: 14.244085477s
Jun  4 08:19:02.380: INFO: Pod "pvc-snapshottable-tester-5td6h": Phase="Pending", Reason="", readiness=false. Elapsed: 16.280815947s
Jun  4 08:19:04.415: INFO: Pod "pvc-snapshottable-tester-5td6h": Phase="Pending", Reason="", readiness=false. Elapsed: 18.316197148s
Jun  4 08:19:06.444: INFO: Pod "pvc-snapshottable-tester-5td6h": Phase="Pending", Reason="", readiness=false. Elapsed: 20.345704579s
Jun  4 08:19:08.475: INFO: Pod "pvc-snapshottable-tester-5td6h": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.37660447s
STEP: Saw pod success
Jun  4 08:19:08.475: INFO: Pod "pvc-snapshottable-tester-5td6h" satisfied condition "Succeeded or Failed"
Jun  4 08:19:08.537: INFO: Pod pvc-snapshottable-tester-5td6h has the following logs: 
Jun  4 08:19:08.537: INFO: Deleting pod "pvc-snapshottable-tester-5td6h" in namespace "snapshotting-4642"
Jun  4 08:19:08.571: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-5td6h" to be fully deleted
Jun  4 08:19:08.602: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.com8lqvw] to have phase Bound
Jun  4 08:19:08.633: INFO: PersistentVolumeClaim ebs.csi.aws.com8lqvw found and phase=Bound (29.990328ms)
STEP: [init] checking the claim
... skipping 30 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.HvoHaXSxC/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  4 08:19:49.599: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-rhz9t" in namespace "snapshotting-4642" to be "Succeeded or Failed"
Jun  4 08:19:49.632: INFO: Pod "pvc-snapshottable-data-tester-rhz9t": Phase="Pending", Reason="", readiness=false. Elapsed: 32.514478ms
Jun  4 08:19:51.663: INFO: Pod "pvc-snapshottable-data-tester-rhz9t": Phase="Pending", Reason="", readiness=false. Elapsed: 2.063388094s
Jun  4 08:19:53.694: INFO: Pod "pvc-snapshottable-data-tester-rhz9t": Phase="Pending", Reason="", readiness=false. Elapsed: 4.094393348s
Jun  4 08:19:55.725: INFO: Pod "pvc-snapshottable-data-tester-rhz9t": Phase="Pending", Reason="", readiness=false. Elapsed: 6.125357622s
Jun  4 08:19:57.754: INFO: Pod "pvc-snapshottable-data-tester-rhz9t": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.154873478s
STEP: Saw pod success
Jun  4 08:19:57.754: INFO: Pod "pvc-snapshottable-data-tester-rhz9t" satisfied condition "Succeeded or Failed"
Jun  4 08:19:57.818: INFO: Pod pvc-snapshottable-data-tester-rhz9t has the following logs: 
Jun  4 08:19:57.818: INFO: Deleting pod "pvc-snapshottable-data-tester-rhz9t" in namespace "snapshotting-4642"
Jun  4 08:19:57.855: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-rhz9t" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun  4 08:20:20.029: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-4642 exec restored-pvc-tester-9nhds --namespace=snapshotting-4642 -- cat /mnt/test/data'
... skipping 33 lines ...
Jun  4 08:20:45.396: INFO: volumesnapshotcontents snapcontent-1d8b2968-2fdd-4a08-8078-dbf54fc69696 has been found and is not deleted
Jun  4 08:20:46.428: INFO: volumesnapshotcontents snapcontent-1d8b2968-2fdd-4a08-8078-dbf54fc69696 has been found and is not deleted
Jun  4 08:20:47.459: INFO: volumesnapshotcontents snapcontent-1d8b2968-2fdd-4a08-8078-dbf54fc69696 has been found and is not deleted
Jun  4 08:20:48.490: INFO: volumesnapshotcontents snapcontent-1d8b2968-2fdd-4a08-8078-dbf54fc69696 has been found and is not deleted
Jun  4 08:20:49.520: INFO: volumesnapshotcontents snapcontent-1d8b2968-2fdd-4a08-8078-dbf54fc69696 has been found and is not deleted
Jun  4 08:20:50.551: INFO: volumesnapshotcontents snapcontent-1d8b2968-2fdd-4a08-8078-dbf54fc69696 has been found and is not deleted
Jun  4 08:20:51.551: INFO: WaitUntil failed after reaching the timeout 30s
[AfterEach] volume snapshot controller
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:221
Jun  4 08:20:51.582: INFO: Pod restored-pvc-tester-9nhds has the following logs: 
Jun  4 08:20:51.582: INFO: Deleting pod "restored-pvc-tester-9nhds" in namespace "snapshotting-4642"
Jun  4 08:20:51.615: INFO: Wait up to 5m0s for pod "restored-pvc-tester-9nhds" to be fully deleted
Jun  4 08:21:33.679: INFO: deleting claim "snapshotting-4642"/"pvc-ktm5w"
... skipping 70 lines ...
Jun  4 08:20:41.689: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4351-e2e-scwd4mn
STEP: creating a claim
Jun  4 08:20:41.720: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-np5x
STEP: Creating a pod to test multi_subpath
Jun  4 08:20:41.815: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-np5x" in namespace "provisioning-4351" to be "Succeeded or Failed"
Jun  4 08:20:41.846: INFO: Pod "pod-subpath-test-dynamicpv-np5x": Phase="Pending", Reason="", readiness=false. Elapsed: 31.241018ms
Jun  4 08:20:43.878: INFO: Pod "pod-subpath-test-dynamicpv-np5x": Phase="Pending", Reason="", readiness=false. Elapsed: 2.06301697s
Jun  4 08:20:45.910: INFO: Pod "pod-subpath-test-dynamicpv-np5x": Phase="Pending", Reason="", readiness=false. Elapsed: 4.094940479s
Jun  4 08:20:47.941: INFO: Pod "pod-subpath-test-dynamicpv-np5x": Phase="Pending", Reason="", readiness=false. Elapsed: 6.126576467s
Jun  4 08:20:49.977: INFO: Pod "pod-subpath-test-dynamicpv-np5x": Phase="Pending", Reason="", readiness=false. Elapsed: 8.162355957s
Jun  4 08:20:52.007: INFO: Pod "pod-subpath-test-dynamicpv-np5x": Phase="Pending", Reason="", readiness=false. Elapsed: 10.192235178s
... skipping 2 lines ...
Jun  4 08:20:58.106: INFO: Pod "pod-subpath-test-dynamicpv-np5x": Phase="Pending", Reason="", readiness=false. Elapsed: 16.291190847s
Jun  4 08:21:00.138: INFO: Pod "pod-subpath-test-dynamicpv-np5x": Phase="Pending", Reason="", readiness=false. Elapsed: 18.323432365s
Jun  4 08:21:02.169: INFO: Pod "pod-subpath-test-dynamicpv-np5x": Phase="Pending", Reason="", readiness=false. Elapsed: 20.354288545s
Jun  4 08:21:04.199: INFO: Pod "pod-subpath-test-dynamicpv-np5x": Phase="Pending", Reason="", readiness=false. Elapsed: 22.384515946s
Jun  4 08:21:06.231: INFO: Pod "pod-subpath-test-dynamicpv-np5x": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.416109966s
STEP: Saw pod success
Jun  4 08:21:06.231: INFO: Pod "pod-subpath-test-dynamicpv-np5x" satisfied condition "Succeeded or Failed"
Jun  4 08:21:06.260: INFO: Trying to get logs from node ip-172-20-49-5.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-np5x container test-container-subpath-dynamicpv-np5x: <nil>
STEP: delete the pod
Jun  4 08:21:06.329: INFO: Waiting for pod pod-subpath-test-dynamicpv-np5x to disappear
Jun  4 08:21:06.359: INFO: Pod pod-subpath-test-dynamicpv-np5x no longer exists
STEP: Deleting pod
Jun  4 08:21:06.359: INFO: Deleting pod "pod-subpath-test-dynamicpv-np5x" in namespace "provisioning-4351"
... skipping 174 lines ...

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

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

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

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

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

      Driver supports dynamic provisioning, skipping PreprovisionedPV pattern

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

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

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.002 seconds]
External Storage [Driver: ebs.csi.aws.com]
/tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:175
  [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /tmp/kops.HvoHaXSxC/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.HvoHaXSxC/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.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/external/external.go:255
------------------------------
... skipping 207 lines ...
Jun  4 08:20:48.681: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-228852khf
STEP: creating a claim
Jun  4 08:20:48.712: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-59k8
STEP: Creating a pod to test atomic-volume-subpath
Jun  4 08:20:48.807: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-59k8" in namespace "provisioning-2288" to be "Succeeded or Failed"
Jun  4 08:20:48.838: INFO: Pod "pod-subpath-test-dynamicpv-59k8": Phase="Pending", Reason="", readiness=false. Elapsed: 30.778578ms
Jun  4 08:20:50.870: INFO: Pod "pod-subpath-test-dynamicpv-59k8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.063329958s
Jun  4 08:20:52.923: INFO: Pod "pod-subpath-test-dynamicpv-59k8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.115643348s
Jun  4 08:20:54.959: INFO: Pod "pod-subpath-test-dynamicpv-59k8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.152578627s
Jun  4 08:20:56.991: INFO: Pod "pod-subpath-test-dynamicpv-59k8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.183870967s
Jun  4 08:20:59.022: INFO: Pod "pod-subpath-test-dynamicpv-59k8": Phase="Pending", Reason="", readiness=false. Elapsed: 10.215460105s
... skipping 11 lines ...
Jun  4 08:21:23.401: INFO: Pod "pod-subpath-test-dynamicpv-59k8": Phase="Running", Reason="", readiness=true. Elapsed: 34.594506201s
Jun  4 08:21:25.434: INFO: Pod "pod-subpath-test-dynamicpv-59k8": Phase="Running", Reason="", readiness=true. Elapsed: 36.626846625s
Jun  4 08:21:27.466: INFO: Pod "pod-subpath-test-dynamicpv-59k8": Phase="Running", Reason="", readiness=true. Elapsed: 38.659296956s
Jun  4 08:21:29.498: INFO: Pod "pod-subpath-test-dynamicpv-59k8": Phase="Running", Reason="", readiness=true. Elapsed: 40.691594808s
Jun  4 08:21:31.531: INFO: Pod "pod-subpath-test-dynamicpv-59k8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 42.724505501s
STEP: Saw pod success
Jun  4 08:21:31.531: INFO: Pod "pod-subpath-test-dynamicpv-59k8" satisfied condition "Succeeded or Failed"
Jun  4 08:21:31.562: INFO: Trying to get logs from node ip-172-20-49-5.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-59k8 container test-container-subpath-dynamicpv-59k8: <nil>
STEP: delete the pod
Jun  4 08:21:31.633: INFO: Waiting for pod pod-subpath-test-dynamicpv-59k8 to disappear
Jun  4 08:21:31.664: INFO: Pod pod-subpath-test-dynamicpv-59k8 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-59k8
Jun  4 08:21:31.664: INFO: Deleting pod "pod-subpath-test-dynamicpv-59k8" in namespace "provisioning-2288"
... skipping 66 lines ...
Jun  4 08:21:39.068: INFO: Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(aws) supported size:{ 1Gi} 
STEP: creating a StorageClass volume-expand-812055g4d
STEP: creating a claim
Jun  4 08:21:39.102: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Expanding non-expandable pvc
Jun  4 08:21:39.166: INFO: currentPvcSize {{1073741824 0} {<nil>} 1Gi BinarySI}, newSize {{2147483648 0} {<nil>}  BinarySI}
Jun  4 08:21:39.227: INFO: Error updating pvc awsffxvj: PersistentVolumeClaim "awsffxvj" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-812055g4d",
  	... // 2 identical fields
  }

Jun  4 08:21:41.290: INFO: Error updating pvc awsffxvj: PersistentVolumeClaim "awsffxvj" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-812055g4d",
  	... // 2 identical fields
  }

Jun  4 08:21:43.289: INFO: Error updating pvc awsffxvj: PersistentVolumeClaim "awsffxvj" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-812055g4d",
  	... // 2 identical fields
  }

Jun  4 08:21:45.291: INFO: Error updating pvc awsffxvj: PersistentVolumeClaim "awsffxvj" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-812055g4d",
  	... // 2 identical fields
  }

Jun  4 08:21:47.289: INFO: Error updating pvc awsffxvj: PersistentVolumeClaim "awsffxvj" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-812055g4d",
  	... // 2 identical fields
  }

Jun  4 08:21:49.291: INFO: Error updating pvc awsffxvj: PersistentVolumeClaim "awsffxvj" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-812055g4d",
  	... // 2 identical fields
  }

Jun  4 08:21:51.290: INFO: Error updating pvc awsffxvj: PersistentVolumeClaim "awsffxvj" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-812055g4d",
  	... // 2 identical fields
  }

Jun  4 08:21:53.288: INFO: Error updating pvc awsffxvj: PersistentVolumeClaim "awsffxvj" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-812055g4d",
  	... // 2 identical fields
  }

Jun  4 08:21:55.291: INFO: Error updating pvc awsffxvj: PersistentVolumeClaim "awsffxvj" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-812055g4d",
  	... // 2 identical fields
  }

Jun  4 08:21:57.289: INFO: Error updating pvc awsffxvj: PersistentVolumeClaim "awsffxvj" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-812055g4d",
  	... // 2 identical fields
  }

Jun  4 08:21:59.290: INFO: Error updating pvc awsffxvj: PersistentVolumeClaim "awsffxvj" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 5 lines ...
  	},
  	VolumeName:       "",
  	StorageClassName: &"volume-expand-812055g4d",
  	... // 2 identical fields
  }

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

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

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

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

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

Jun  4 08:22:09.350: INFO: Error updating pvc awsffxvj: PersistentVolumeClaim "awsffxvj" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims
  core.PersistentVolumeClaimSpec{
  	AccessModes: {"ReadWriteOnce"},
  	Selector:    nil,
  	Resources: core.ResourceRequirements{
  		Limits: nil,
- 		Requests: core.ResourceList{
... skipping 36 lines ...

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

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

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

    /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:92
------------------------------
... skipping 31 lines ...
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  4 08:22:09.732: 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.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192
Jun  4 08:22:09.927: INFO: found topology map[topology.kubernetes.io/zone:us-east-2a]
Jun  4 08:22:09.927: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  4 08:22:09.927: INFO: Not enough topologies in cluster -- skipping
STEP: Deleting pvc
STEP: Deleting sc
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.HvoHaXSxC/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.HvoHaXSxC/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (delayed binding)] topology
    /tmp/kops.HvoHaXSxC/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.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:192

      Not enough topologies in cluster -- skipping

      /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/topology.go:199
------------------------------
... skipping 113 lines ...
Jun  4 08:19:55.645: INFO: Creating resource for dynamic PV
Jun  4 08:19:55.645: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-7762-e2e-sczjz86
STEP: creating a claim
Jun  4 08:19:55.676: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: [init] starting a pod to use the claim
Jun  4 08:19:55.769: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-l7kb9" in namespace "snapshotting-7762" to be "Succeeded or Failed"
Jun  4 08:19:55.799: INFO: Pod "pvc-snapshottable-tester-l7kb9": Phase="Pending", Reason="", readiness=false. Elapsed: 29.847898ms
Jun  4 08:19:57.830: INFO: Pod "pvc-snapshottable-tester-l7kb9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.060585724s
Jun  4 08:19:59.863: INFO: Pod "pvc-snapshottable-tester-l7kb9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.094180919s
Jun  4 08:20:01.897: INFO: Pod "pvc-snapshottable-tester-l7kb9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.127341186s
Jun  4 08:20:03.929: INFO: Pod "pvc-snapshottable-tester-l7kb9": Phase="Pending", Reason="", readiness=false. Elapsed: 8.160084232s
Jun  4 08:20:05.961: INFO: Pod "pvc-snapshottable-tester-l7kb9": Phase="Pending", Reason="", readiness=false. Elapsed: 10.191336907s
Jun  4 08:20:07.991: INFO: Pod "pvc-snapshottable-tester-l7kb9": Phase="Pending", Reason="", readiness=false. Elapsed: 12.221619293s
Jun  4 08:20:10.032: INFO: Pod "pvc-snapshottable-tester-l7kb9": Phase="Pending", Reason="", readiness=false. Elapsed: 14.262330199s
Jun  4 08:20:12.062: INFO: Pod "pvc-snapshottable-tester-l7kb9": Phase="Pending", Reason="", readiness=false. Elapsed: 16.293269946s
Jun  4 08:20:14.093: INFO: Pod "pvc-snapshottable-tester-l7kb9": Phase="Pending", Reason="", readiness=false. Elapsed: 18.323817864s
Jun  4 08:20:16.124: INFO: Pod "pvc-snapshottable-tester-l7kb9": Phase="Pending", Reason="", readiness=false. Elapsed: 20.355196931s
Jun  4 08:20:18.156: INFO: Pod "pvc-snapshottable-tester-l7kb9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.386724298s
STEP: Saw pod success
Jun  4 08:20:18.156: INFO: Pod "pvc-snapshottable-tester-l7kb9" satisfied condition "Succeeded or Failed"
Jun  4 08:20:18.218: INFO: Pod pvc-snapshottable-tester-l7kb9 has the following logs: 
Jun  4 08:20:18.218: INFO: Deleting pod "pvc-snapshottable-tester-l7kb9" in namespace "snapshotting-7762"
Jun  4 08:20:18.258: INFO: Wait up to 5m0s for pod "pvc-snapshottable-tester-l7kb9" to be fully deleted
Jun  4 08:20:18.288: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [ebs.csi.aws.combmjf6] to have phase Bound
Jun  4 08:20:18.319: INFO: PersistentVolumeClaim ebs.csi.aws.combmjf6 found and phase=Bound (30.427398ms)
STEP: [init] checking the claim
... skipping 41 lines ...
[It] should check snapshot fields, check restore correctly works after modifying source data, check deletion
  /tmp/kops.HvoHaXSxC/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  4 08:20:45.403: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-sbjwp" in namespace "snapshotting-7762" to be "Succeeded or Failed"
Jun  4 08:20:45.433: INFO: Pod "pvc-snapshottable-data-tester-sbjwp": Phase="Pending", Reason="", readiness=false. Elapsed: 30.319168ms
Jun  4 08:20:47.464: INFO: Pod "pvc-snapshottable-data-tester-sbjwp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061301009s
Jun  4 08:20:49.495: INFO: Pod "pvc-snapshottable-data-tester-sbjwp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.092114717s
Jun  4 08:20:51.527: INFO: Pod "pvc-snapshottable-data-tester-sbjwp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.123818627s
Jun  4 08:20:53.558: INFO: Pod "pvc-snapshottable-data-tester-sbjwp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.155162748s
Jun  4 08:20:55.590: INFO: Pod "pvc-snapshottable-data-tester-sbjwp": Phase="Pending", Reason="", readiness=false. Elapsed: 10.186790247s
Jun  4 08:20:57.621: INFO: Pod "pvc-snapshottable-data-tester-sbjwp": Phase="Pending", Reason="", readiness=false. Elapsed: 12.217502657s
Jun  4 08:20:59.652: INFO: Pod "pvc-snapshottable-data-tester-sbjwp": Phase="Pending", Reason="", readiness=false. Elapsed: 14.249230627s
Jun  4 08:21:01.684: INFO: Pod "pvc-snapshottable-data-tester-sbjwp": Phase="Pending", Reason="", readiness=false. Elapsed: 16.280930125s
Jun  4 08:21:03.715: INFO: Pod "pvc-snapshottable-data-tester-sbjwp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.311963236s
STEP: Saw pod success
Jun  4 08:21:03.715: INFO: Pod "pvc-snapshottable-data-tester-sbjwp" satisfied condition "Succeeded or Failed"
Jun  4 08:21:03.777: INFO: Pod pvc-snapshottable-data-tester-sbjwp has the following logs: 
Jun  4 08:21:03.777: INFO: Deleting pod "pvc-snapshottable-data-tester-sbjwp" in namespace "snapshotting-7762"
Jun  4 08:21:03.812: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-sbjwp" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the claim
Jun  4 08:21:19.968: INFO: Running '/usr/local/bin/kubectl --server=https://api.e2e-f9b0e6b3f9-a6fg1.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=snapshotting-7762 exec restored-pvc-tester-jpqbz --namespace=snapshotting-7762 -- cat /mnt/test/data'
... skipping 34 lines ...
Jun  4 08:22:12.160: INFO: At 2021-06-04 08:19:59 +0000 UTC - event for pvc-snapshottable-tester-l7kb9: {default-scheduler } Scheduled: Successfully assigned snapshotting-7762/pvc-snapshottable-tester-l7kb9 to ip-172-20-44-239.us-east-2.compute.internal
Jun  4 08:22:12.160: INFO: At 2021-06-04 08:20:07 +0000 UTC - event for pvc-snapshottable-tester-l7kb9: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-999945f9-0834-494e-b50f-f8864bac9e72" 
Jun  4 08:22:12.160: INFO: At 2021-06-04 08:20:16 +0000 UTC - event for pvc-snapshottable-tester-l7kb9: {kubelet ip-172-20-44-239.us-east-2.compute.internal} Started: Started container volume-tester
Jun  4 08:22:12.160: INFO: At 2021-06-04 08:20:16 +0000 UTC - event for pvc-snapshottable-tester-l7kb9: {kubelet ip-172-20-44-239.us-east-2.compute.internal} Created: Created container volume-tester
Jun  4 08:22:12.160: INFO: At 2021-06-04 08:20:16 +0000 UTC - event for pvc-snapshottable-tester-l7kb9: {kubelet ip-172-20-44-239.us-east-2.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" already present on machine
Jun  4 08:22:12.160: INFO: At 2021-06-04 08:20:18 +0000 UTC - event for snapshot-h6w49: {snapshot-controller } CreatingSnapshot: Waiting for a snapshot snapshotting-7762/snapshot-h6w49 to be created by the CSI driver.
Jun  4 08:22:12.160: INFO: At 2021-06-04 08:20:43 +0000 UTC - event for pre-provisioned-snapshot-ff5f6630-7ca1-4724-a65c-cc02d4263b4b: {snapshot-controller } SnapshotBindFailed: Snapshot failed to bind VolumeSnapshotContent, Operation cannot be fulfilled on volumesnapshotcontents.snapshot.storage.k8s.io "pre-provisioned-snapcontent-ff5f6630-7ca1-4724-a65c-cc02d4263b4b": the object has been modified; please apply your changes to the latest version and try again
Jun  4 08:22:12.160: INFO: At 2021-06-04 08:20:45 +0000 UTC - event for pvc-snapshottable-data-tester-sbjwp: {default-scheduler } Scheduled: Successfully assigned snapshotting-7762/pvc-snapshottable-data-tester-sbjwp to ip-172-20-49-5.us-east-2.compute.internal
Jun  4 08:22:12.160: INFO: At 2021-06-04 08:20:59 +0000 UTC - event for pvc-snapshottable-data-tester-sbjwp: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-999945f9-0834-494e-b50f-f8864bac9e72" 
Jun  4 08:22:12.160: INFO: At 2021-06-04 08:21:02 +0000 UTC - event for pvc-snapshottable-data-tester-sbjwp: {kubelet ip-172-20-49-5.us-east-2.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" already present on machine
Jun  4 08:22:12.160: INFO: At 2021-06-04 08:21:02 +0000 UTC - event for pvc-snapshottable-data-tester-sbjwp: {kubelet ip-172-20-49-5.us-east-2.compute.internal} Started: Started container volume-tester
Jun  4 08:22:12.160: INFO: At 2021-06-04 08:21:02 +0000 UTC - event for pvc-snapshottable-data-tester-sbjwp: {kubelet ip-172-20-49-5.us-east-2.compute.internal} Created: Created container volume-tester
Jun  4 08:22:12.160: INFO: At 2021-06-04 08:21:03 +0000 UTC - event for pvc-qqd5z: {persistentvolume-controller } ExternalProvisioning: waiting for a volume to be created, either by external provisioner "ebs.csi.aws.com" or manually created by system administrator
... skipping 3 lines ...
Jun  4 08:22:12.160: INFO: At 2021-06-04 08:21:07 +0000 UTC - event for restored-pvc-tester-jpqbz: {default-scheduler } Scheduled: Successfully assigned snapshotting-7762/restored-pvc-tester-jpqbz to ip-172-20-49-219.us-east-2.compute.internal
Jun  4 08:22:12.160: INFO: At 2021-06-04 08:21:12 +0000 UTC - event for restored-pvc-tester-jpqbz: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-3517679b-3066-47ad-98d9-ce38d7ae2151" 
Jun  4 08:22:12.160: INFO: At 2021-06-04 08:21:14 +0000 UTC - event for restored-pvc-tester-jpqbz: {kubelet ip-172-20-49-219.us-east-2.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" already present on machine
Jun  4 08:22:12.160: INFO: At 2021-06-04 08:21:15 +0000 UTC - event for restored-pvc-tester-jpqbz: {kubelet ip-172-20-49-219.us-east-2.compute.internal} Created: Created container volume-tester
Jun  4 08:22:12.160: INFO: At 2021-06-04 08:21:15 +0000 UTC - event for restored-pvc-tester-jpqbz: {kubelet ip-172-20-49-219.us-east-2.compute.internal} Started: Started container volume-tester
Jun  4 08:22:12.160: INFO: At 2021-06-04 08:21:20 +0000 UTC - event for restored-pvc-tester-jpqbz: {kubelet ip-172-20-49-219.us-east-2.compute.internal} Killing: Stopping container volume-tester
Jun  4 08:22:12.160: INFO: At 2021-06-04 08:22:02 +0000 UTC - event for pre-provisioned-snapshot-ff5f6630-7ca1-4724-a65c-cc02d4263b4b: {snapshot-controller } SnapshotFinalizerError: Failed to check and update snapshot: snapshot controller failed to update snapshotting-7762/pre-provisioned-snapshot-ff5f6630-7ca1-4724-a65c-cc02d4263b4b on API server: Operation cannot be fulfilled on volumesnapshots.snapshot.storage.k8s.io "pre-provisioned-snapshot-ff5f6630-7ca1-4724-a65c-cc02d4263b4b": the object has been modified; please apply your changes to the latest version and try again
Jun  4 08:22:12.190: INFO: POD  NODE  PHASE  GRACE  CONDITIONS
Jun  4 08:22:12.190: INFO: 
Jun  4 08:22:12.222: INFO: 
Logging node info for node ip-172-20-44-239.us-east-2.compute.internal
Jun  4 08:22:12.252: INFO: Node Info: &Node{ObjectMeta:{ip-172-20-44-239.us-east-2.compute.internal    eed20ccc-52a5-4016-83bc-ce4dcd911e7d 12774 0 2021-06-04 08:12:38 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:t3.medium beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:us-east-2 failure-domain.beta.kubernetes.io/zone:us-east-2a kops.k8s.io/instancegroup:nodes-us-east-2a kubernetes.io/arch:amd64 kubernetes.io/hostname:ip-172-20-44-239.us-east-2.compute.internal kubernetes.io/os:linux kubernetes.io/role:node node-role.kubernetes.io/node: node.kubernetes.io/instance-type:t3.medium topology.ebs.csi.aws.com/zone:us-east-2a topology.kubernetes.io/region:us-east-2 topology.kubernetes.io/zone:us-east-2a] map[csi.volume.kubernetes.io/nodeid:{"ebs.csi.aws.com":"i-0346968af216cd18f"} node.alpha.kubernetes.io/ttl:0 projectcalico.org/IPv4Address:172.20.44.239/19 projectcalico.org/IPv4IPIPTunnelAddr:100.102.241.128 volumes.kubernetes.io/controller-managed-attach-detach:true] [] []  [{kops-controller Update v1 2021-06-04 08:12:38 +0000 UTC FieldsV1 {"f:metadata":{"f:labels":{"f:kops.k8s.io/instancegroup":{},"f:kubernetes.io/role":{},"f:node-role.kubernetes.io/node":{}}}}} {calico-node Update v1 2021-06-04 08:12:59 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4IPIPTunnelAddr":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}}} {kube-controller-manager Update v1 2021-06-04 08:21:51 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"100.96.1.0/24\"":{}}}}} {kubelet Update v1 2021-06-04 08:22:08 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:csi.volume.kubernetes.io/nodeid":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.ebs.csi.aws.com/zone":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}},"f:status":{"f:allocatable":{"f:ephemeral-storage":{}},"f:capacity":{"f:ephemeral-storage":{}},"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}}}]},Spec:NodeSpec{PodCIDR:100.96.1.0/24,DoNotUseExternalID:,ProviderID:aws:///us-east-2a/i-0346968af216cd18f,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[100.96.1.0/24],},Status:NodeStatus{Capacity:ResourceList{cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{49895047168 0} {<nil>}  BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{4064759808 0} {<nil>} 3969492Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{44905542377 0} {<nil>} 44905542377 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{3959902208 0} {<nil>} 3867092Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2021-06-04 08:12:59 +0000 UTC,LastTransitionTime:2021-06-04 08:12:59 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2021-06-04 08:22:08 +0000 UTC,LastTransitionTime:2021-06-04 08:12:37 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2021-06-04 08:22:08 +0000 UTC,LastTransitionTime:2021-06-04 08:12:37 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2021-06-04 08:22:08 +0000 UTC,LastTransitionTime:2021-06-04 08:12:37 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2021-06-04 08:22:08 +0000 UTC,LastTransitionTime:2021-06-04 08:12:58 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:172.20.44.239,},NodeAddress{Type:ExternalIP,Address:3.135.216.32,},NodeAddress{Type:Hostname,Address:ip-172-20-44-239.us-east-2.compute.internal,},NodeAddress{Type:InternalDNS,Address:ip-172-20-44-239.us-east-2.compute.internal,},NodeAddress{Type:ExternalDNS,Address:ec2-3-135-216-32.us-east-2.compute.amazonaws.com,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:ec22f4c8ba4aa91d6bff3f07d1ea3991,SystemUUID:ec22f4c8-ba4a-a91d-6bff-3f07d1ea3991,BootID:0d18758b-eb4d-4655-8792-802bf650c0dc,KernelVersion:5.4.0-1045-aws,OSImage:Ubuntu 20.04.2 LTS,ContainerRuntimeVersion:containerd://1.4.6,KubeletVersion:v1.21.0,KubeProxyVersion:v1.21.0,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[k8s.gcr.io/provider-aws/aws-ebs-csi-driver@sha256:a0294bf95fd94eabdc9b313b6c16232019a8707c711c031a2f99ab1f919560bd k8s.gcr.io/provider-aws/aws-ebs-csi-driver:v1.0.0],SizeBytes:67079979,},ContainerImage{Names:[docker.io/calico/node@sha256:bc4a631d553b38fdc169ea4cb8027fa894a656e80d68d513359a4b9d46836b55 docker.io/calico/node:v3.19.1],SizeBytes:58671776,},ContainerImage{Names:[k8s.gcr.io/kube-proxy@sha256:326199e7a5232bf7531a3058e9811c925b07085f33fa882558cc4e89379b9109 k8s.gcr.io/kube-proxy:v1.21.0],SizeBytes:50134170,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/agnhost@sha256:8bd76a6a7778e203b61e18e5ee85b1faf52e6a30eb07e445a165ab90fe9633e3 k8s.gcr.io/e2e-test-images/agnhost:2.31],SizeBytes:49692421,},ContainerImage{Names:[docker.io/calico/cni@sha256:f301171be0add870152483fcce71b28cafb8e910f61ff003032e9b1053b062c4 docker.io/calico/cni:v3.19.1],SizeBytes:48338203,},ContainerImage{Names:[k8s.gcr.io/build-image/debian-iptables@sha256:abe8cef9e116f2d5ec1175c386e33841ff3386779138b425af876384b0fd7ccb k8s.gcr.io/build-image/debian-iptables:buster-v1.5.0],SizeBytes:38088315,},ContainerImage{Names:[quay.io/jetstack/cert-manager-webhook@sha256:41eacd93a30b566b780a6ae525b2547d2a87f1ec5f067fc02840a220aeb0c3f7 quay.io/jetstack/cert-manager-webhook:v1.3.1],SizeBytes:19734169,},ContainerImage{Names:[quay.io/jetstack/cert-manager-cainjector@sha256:51c0df411b66aa175e9fc6840f3135d55b52c3781d0b3d4aa10862066d460193 quay.io/jetstack/cert-manager-cainjector:v1.3.1],SizeBytes:19215137,},ContainerImage{Names:[k8s.gcr.io/sig-storage/snapshot-validation-webhook@sha256:931a753e6428914f5393e3bba5f250f952c57dc2e9ddd16c37593a8f02b6715e k8s.gcr.io/sig-storage/snapshot-validation-webhook:v4.1.1],SizeBytes:18566421,},ContainerImage{Names:[k8s.gcr.io/cpa/cluster-proportional-autoscaler@sha256:67640771ad9fc56f109d5b01e020f0c858e7c890bb0eb15ba0ebd325df3285e7 k8s.gcr.io/cpa/cluster-proportional-autoscaler:1.8.3],SizeBytes:15191740,},ContainerImage{Names:[docker.io/coredns/coredns@sha256:642ff9910da6ea9a8624b0234eef52af9ca75ecbec474c5507cb096bdfbae4e5 docker.io/coredns/coredns:1.8.3],SizeBytes:12893350,},ContainerImage{Names:[docker.io/calico/pod2daemon-flexvol@sha256:bcac7dc4f1301b062d91a177a52d13716907636975c44131fb8350e7f851c944 docker.io/calico/pod2daemon-flexvol:v3.19.1],SizeBytes:9328155,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-node-driver-registrar@sha256:a61d309da54641db41fb8f35718f744e9f730d4d0384f8c4b186ddc9f06cbd5f k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.1.0],SizeBytes:9068367,},ContainerImage{Names:[k8s.gcr.io/sig-storage/livenessprobe@sha256:48da0e4ed7238ad461ea05f68c25921783c37b315f21a5c5a2780157a6460994 k8s.gcr.io/sig-storage/livenessprobe:v2.2.0],SizeBytes:8279778,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/nginx@sha256:503b7abb89e57383eba61cc8a9cb0b495ea575c516108f7d972a6ff6e1ab3c9b k8s.gcr.io/e2e-test-images/nginx:1.14-1],SizeBytes:6979365,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/busybox@sha256:39e1e963e5310e9c313bad51523be012ede7b35bb9316517d19089a010356592 k8s.gcr.io/e2e-test-images/busybox:1.29-1],SizeBytes:732746,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:927d98197ec1141a368550822d18fa1c60bdae27b78b0c004f705f548c07814f k8s.gcr.io/pause:3.2],SizeBytes:299513,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},}
Jun  4 08:22:12.252: INFO: 
... skipping 194 lines ...
    /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/snapshottable.go:108
      
      /tmp/kops.HvoHaXSxC/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.HvoHaXSxC/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-7762 exec restored-pvc-tester-jpqbz --namespace=snapshotting-7762 -- 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-7762 exec restored-pvc-tester-jpqbz --namespace=snapshotting-7762 -- 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.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:602
------------------------------
S
... skipping 84 lines ...
Jun  4 08:21:15.634: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1328tmfmv
STEP: creating a claim
Jun  4 08:21:15.664: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-8nv2
STEP: Creating a pod to test subpath
Jun  4 08:21:15.763: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-8nv2" in namespace "provisioning-1328" to be "Succeeded or Failed"
Jun  4 08:21:15.795: INFO: Pod "pod-subpath-test-dynamicpv-8nv2": Phase="Pending", Reason="", readiness=false. Elapsed: 32.246328ms
Jun  4 08:21:17.827: INFO: Pod "pod-subpath-test-dynamicpv-8nv2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.063654641s
Jun  4 08:21:19.872: INFO: Pod "pod-subpath-test-dynamicpv-8nv2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.108460392s
Jun  4 08:21:21.902: INFO: Pod "pod-subpath-test-dynamicpv-8nv2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.138693945s
Jun  4 08:21:23.933: INFO: Pod "pod-subpath-test-dynamicpv-8nv2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.169673327s
Jun  4 08:21:25.965: INFO: Pod "pod-subpath-test-dynamicpv-8nv2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.202375681s
... skipping 11 lines ...
Jun  4 08:21:50.352: INFO: Pod "pod-subpath-test-dynamicpv-8nv2": Phase="Pending", Reason="", readiness=false. Elapsed: 34.589241087s
Jun  4 08:21:52.382: INFO: Pod "pod-subpath-test-dynamicpv-8nv2": Phase="Pending", Reason="", readiness=false. Elapsed: 36.619355522s
Jun  4 08:21:54.416: INFO: Pod "pod-subpath-test-dynamicpv-8nv2": Phase="Pending", Reason="", readiness=false. Elapsed: 38.653095186s
Jun  4 08:21:56.449: INFO: Pod "pod-subpath-test-dynamicpv-8nv2": Phase="Pending", Reason="", readiness=false. Elapsed: 40.685802748s
Jun  4 08:21:58.479: INFO: Pod "pod-subpath-test-dynamicpv-8nv2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 42.715850602s
STEP: Saw pod success
Jun  4 08:21:58.479: INFO: Pod "pod-subpath-test-dynamicpv-8nv2" satisfied condition "Succeeded or Failed"
Jun  4 08:21:58.508: INFO: Trying to get logs from node ip-172-20-49-5.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-8nv2 container test-container-subpath-dynamicpv-8nv2: <nil>
STEP: delete the pod
Jun  4 08:21:58.590: INFO: Waiting for pod pod-subpath-test-dynamicpv-8nv2 to disappear
Jun  4 08:21:58.619: INFO: Pod pod-subpath-test-dynamicpv-8nv2 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-8nv2
Jun  4 08:21:58.619: INFO: Deleting pod "pod-subpath-test-dynamicpv-8nv2" in namespace "provisioning-1328"
... skipping 199 lines ...
Jun  4 08:21:54.151: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7466w5r2f
STEP: creating a claim
Jun  4 08:21:54.182: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-fpdf
STEP: Creating a pod to test multi_subpath
Jun  4 08:21:54.309: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-fpdf" in namespace "provisioning-7466" to be "Succeeded or Failed"
Jun  4 08:21:54.340: INFO: Pod "pod-subpath-test-dynamicpv-fpdf": Phase="Pending", Reason="", readiness=false. Elapsed: 30.796738ms
Jun  4 08:21:56.371: INFO: Pod "pod-subpath-test-dynamicpv-fpdf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062116912s
Jun  4 08:21:58.402: INFO: Pod "pod-subpath-test-dynamicpv-fpdf": Phase="Pending", Reason="", readiness=false. Elapsed: 4.092648665s
Jun  4 08:22:00.434: INFO: Pod "pod-subpath-test-dynamicpv-fpdf": Phase="Pending", Reason="", readiness=false. Elapsed: 6.124213402s
Jun  4 08:22:02.465: INFO: Pod "pod-subpath-test-dynamicpv-fpdf": Phase="Pending", Reason="", readiness=false. Elapsed: 8.155387667s
Jun  4 08:22:04.496: INFO: Pod "pod-subpath-test-dynamicpv-fpdf": Phase="Pending", Reason="", readiness=false. Elapsed: 10.186315822s
Jun  4 08:22:06.527: INFO: Pod "pod-subpath-test-dynamicpv-fpdf": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.217610027s
STEP: Saw pod success
Jun  4 08:22:06.527: INFO: Pod "pod-subpath-test-dynamicpv-fpdf" satisfied condition "Succeeded or Failed"
Jun  4 08:22:06.557: INFO: Trying to get logs from node ip-172-20-44-239.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-fpdf container test-container-subpath-dynamicpv-fpdf: <nil>
STEP: delete the pod
Jun  4 08:22:06.633: INFO: Waiting for pod pod-subpath-test-dynamicpv-fpdf to disappear
Jun  4 08:22:06.663: INFO: Pod pod-subpath-test-dynamicpv-fpdf no longer exists
STEP: Deleting pod
Jun  4 08:22:06.663: INFO: Deleting pod "pod-subpath-test-dynamicpv-fpdf" in namespace "provisioning-7466"
... skipping 252 lines ...
Jun  4 08:22:09.833: INFO: Waiting for pod aws-client to disappear
Jun  4 08:22:09.865: INFO: Pod aws-client no longer exists
STEP: cleaning the environment after aws
STEP: Deleting pv and pvc
Jun  4 08:22:09.865: INFO: Deleting PersistentVolumeClaim "pvc-h5wdr"
Jun  4 08:22:09.899: INFO: Deleting PersistentVolume "aws-5d5xg"
Jun  4 08:22:10.190: INFO: Couldn't delete PD "aws://us-east-2a/vol-0a5199d62bc7bb6de", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a5199d62bc7bb6de is currently attached to i-0346968af216cd18f
	status code: 400, request id: 7ed8416f-0a3c-4e6a-8be2-908a5970bf2b
Jun  4 08:22:15.440: INFO: Couldn't delete PD "aws://us-east-2a/vol-0a5199d62bc7bb6de", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a5199d62bc7bb6de is currently attached to i-0346968af216cd18f
	status code: 400, request id: 10a01f6f-dbc5-4696-ab85-0097b76fb410
Jun  4 08:22:20.804: INFO: Couldn't delete PD "aws://us-east-2a/vol-0a5199d62bc7bb6de", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0a5199d62bc7bb6de is currently attached to i-0346968af216cd18f
	status code: 400, request id: eb6c00a4-1fe0-4e74-a9ad-9e880bbb6563
Jun  4 08:22:26.062: INFO: Successfully deleted PD "aws://us-east-2a/vol-0a5199d62bc7bb6de".
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumes
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  4 08:22:26.062: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-4718" for this suite.
... skipping 23 lines ...
Jun  4 08:21:28.479: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9071-e2e-scxczqk
STEP: creating a claim
Jun  4 08:21:28.515: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-cvpl
STEP: Creating a pod to test subpath
Jun  4 08:21:28.617: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-cvpl" in namespace "provisioning-9071" to be "Succeeded or Failed"
Jun  4 08:21:28.647: INFO: Pod "pod-subpath-test-dynamicpv-cvpl": Phase="Pending", Reason="", readiness=false. Elapsed: 30.244478ms
Jun  4 08:21:30.678: INFO: Pod "pod-subpath-test-dynamicpv-cvpl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061230919s
Jun  4 08:21:32.709: INFO: Pod "pod-subpath-test-dynamicpv-cvpl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.092169063s
Jun  4 08:21:34.740: INFO: Pod "pod-subpath-test-dynamicpv-cvpl": Phase="Pending", Reason="", readiness=false. Elapsed: 6.123037286s
Jun  4 08:21:36.771: INFO: Pod "pod-subpath-test-dynamicpv-cvpl": Phase="Pending", Reason="", readiness=false. Elapsed: 8.15466697s
Jun  4 08:21:38.803: INFO: Pod "pod-subpath-test-dynamicpv-cvpl": Phase="Pending", Reason="", readiness=false. Elapsed: 10.186333523s
... skipping 2 lines ...
Jun  4 08:21:44.901: INFO: Pod "pod-subpath-test-dynamicpv-cvpl": Phase="Pending", Reason="", readiness=false. Elapsed: 16.284472682s
Jun  4 08:21:46.932: INFO: Pod "pod-subpath-test-dynamicpv-cvpl": Phase="Pending", Reason="", readiness=false. Elapsed: 18.315747727s
Jun  4 08:21:48.964: INFO: Pod "pod-subpath-test-dynamicpv-cvpl": Phase="Pending", Reason="", readiness=false. Elapsed: 20.34760773s
Jun  4 08:21:50.996: INFO: Pod "pod-subpath-test-dynamicpv-cvpl": Phase="Pending", Reason="", readiness=false. Elapsed: 22.379081934s
Jun  4 08:21:53.028: INFO: Pod "pod-subpath-test-dynamicpv-cvpl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.411742468s
STEP: Saw pod success
Jun  4 08:21:53.028: INFO: Pod "pod-subpath-test-dynamicpv-cvpl" satisfied condition "Succeeded or Failed"
Jun  4 08:21:53.058: INFO: Trying to get logs from node ip-172-20-49-5.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-cvpl container test-container-subpath-dynamicpv-cvpl: <nil>
STEP: delete the pod
Jun  4 08:21:53.125: INFO: Waiting for pod pod-subpath-test-dynamicpv-cvpl to disappear
Jun  4 08:21:53.155: INFO: Pod pod-subpath-test-dynamicpv-cvpl no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-cvpl
Jun  4 08:21:53.155: INFO: Deleting pod "pod-subpath-test-dynamicpv-cvpl" in namespace "provisioning-9071"
... skipping 135 lines ...
Jun  4 08:21:51.327: INFO: PersistentVolumeClaim pvc-cdjmz found but phase is Pending instead of Bound.
Jun  4 08:21:53.357: INFO: PersistentVolumeClaim pvc-cdjmz found and phase=Bound (12.221096191s)
Jun  4 08:21:53.357: INFO: Waiting up to 3m0s for PersistentVolume aws-glc64 to have phase Bound
Jun  4 08:21:53.387: INFO: PersistentVolume aws-glc64 found and phase=Bound (30.171268ms)
STEP: Creating pod exec-volume-test-preprovisionedpv-l9zm
STEP: Creating a pod to test exec-volume-test
Jun  4 08:21:53.481: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-l9zm" in namespace "volume-5519" to be "Succeeded or Failed"
Jun  4 08:21:53.513: INFO: Pod "exec-volume-test-preprovisionedpv-l9zm": Phase="Pending", Reason="", readiness=false. Elapsed: 31.665098ms
Jun  4 08:21:55.544: INFO: Pod "exec-volume-test-preprovisionedpv-l9zm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062520182s
Jun  4 08:21:57.576: INFO: Pod "exec-volume-test-preprovisionedpv-l9zm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.094523954s
Jun  4 08:21:59.608: INFO: Pod "exec-volume-test-preprovisionedpv-l9zm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.12702673s
Jun  4 08:22:01.640: INFO: Pod "exec-volume-test-preprovisionedpv-l9zm": Phase="Pending", Reason="", readiness=false. Elapsed: 8.158292076s
Jun  4 08:22:03.670: INFO: Pod "exec-volume-test-preprovisionedpv-l9zm": Phase="Pending", Reason="", readiness=false. Elapsed: 10.189088662s
Jun  4 08:22:05.703: INFO: Pod "exec-volume-test-preprovisionedpv-l9zm": Phase="Pending", Reason="", readiness=false. Elapsed: 12.221421396s
Jun  4 08:22:07.734: INFO: Pod "exec-volume-test-preprovisionedpv-l9zm": Phase="Pending", Reason="", readiness=false. Elapsed: 14.252687681s
Jun  4 08:22:09.769: INFO: Pod "exec-volume-test-preprovisionedpv-l9zm": Phase="Pending", Reason="", readiness=false. Elapsed: 16.288028228s
Jun  4 08:22:11.801: INFO: Pod "exec-volume-test-preprovisionedpv-l9zm": Phase="Pending", Reason="", readiness=false. Elapsed: 18.319931223s
Jun  4 08:22:13.833: INFO: Pod "exec-volume-test-preprovisionedpv-l9zm": Phase="Pending", Reason="", readiness=false. Elapsed: 20.351211921s
Jun  4 08:22:15.868: INFO: Pod "exec-volume-test-preprovisionedpv-l9zm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.386716806s
STEP: Saw pod success
Jun  4 08:22:15.868: INFO: Pod "exec-volume-test-preprovisionedpv-l9zm" satisfied condition "Succeeded or Failed"
Jun  4 08:22:15.899: INFO: Trying to get logs from node ip-172-20-49-5.us-east-2.compute.internal pod exec-volume-test-preprovisionedpv-l9zm container exec-container-preprovisionedpv-l9zm: <nil>
STEP: delete the pod
Jun  4 08:22:15.971: INFO: Waiting for pod exec-volume-test-preprovisionedpv-l9zm to disappear
Jun  4 08:22:16.002: INFO: Pod exec-volume-test-preprovisionedpv-l9zm no longer exists
STEP: Deleting pod exec-volume-test-preprovisionedpv-l9zm
Jun  4 08:22:16.002: INFO: Deleting pod "exec-volume-test-preprovisionedpv-l9zm" in namespace "volume-5519"
STEP: Deleting pv and pvc
Jun  4 08:22:16.032: INFO: Deleting PersistentVolumeClaim "pvc-cdjmz"
Jun  4 08:22:16.064: INFO: Deleting PersistentVolume "aws-glc64"
Jun  4 08:22:16.238: INFO: Couldn't delete PD "aws://us-east-2a/vol-0de366ee417d40c77", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0de366ee417d40c77 is currently attached to i-0e9ce963557e07e18
	status code: 400, request id: f69477ab-f960-4aed-b1f5-226766aad7d4
Jun  4 08:22:21.521: INFO: Couldn't delete PD "aws://us-east-2a/vol-0de366ee417d40c77", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0de366ee417d40c77 is currently attached to i-0e9ce963557e07e18
	status code: 400, request id: a1c2dff0-f4d0-41b0-8328-d5f497b3a973
Jun  4 08:22:26.778: INFO: Couldn't delete PD "aws://us-east-2a/vol-0de366ee417d40c77", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0de366ee417d40c77 is currently attached to i-0e9ce963557e07e18
	status code: 400, request id: 28acbc7e-52b9-46c7-abee-3b88c5e372db
Jun  4 08:22:32.034: INFO: Couldn't delete PD "aws://us-east-2a/vol-0de366ee417d40c77", sleeping 5s: error deleting EBS volumes: VolumeInUse: Volume vol-0de366ee417d40c77 is currently attached to i-0e9ce963557e07e18
	status code: 400, request id: e1f565e2-bd98-4cf3-8d78-8e077df43319
Jun  4 08:22:37.282: INFO: Successfully deleted PD "aws://us-east-2a/vol-0de366ee417d40c77".
[AfterEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Jun  4 08:22:37.284: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volume-5519" for this suite.
... skipping 69 lines ...
Jun  4 08:21:18.927: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-77238s4ln      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-7723    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-77238s4ln,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-7723    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-77238s4ln,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Creating a StorageClass
STEP: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-7723    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-77238s4ln,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-77238s4ln    6db91635-9cc1-4791-af6a-68a9324089af 11260 0 2021-06-04 08:21:18 +0000 UTC <nil> <nil> map[] map[] [] []  [{e2e-kubernetes.test Update storage.k8s.io/v1 2021-06-04 08:21:18 +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-lpczs pvc- provisioning-7723  2e31cf77-2f90-4845-a421-cf76a568b2e4 11262 0 2021-06-04 08:21:19 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection]  [{e2e-kubernetes.test Update v1 2021-06-04 08:21:19 +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-77238s4ln,VolumeMode:*Filesystem,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}
STEP: Deleting pod pod-8c21f3b1-f917-4ad9-bc14-9d2c33bb6d9c in namespace provisioning-7723
STEP: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil}
Jun  4 08:21:33.273: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-c7xsm" in namespace "provisioning-7723" to be "Succeeded or Failed"
Jun  4 08:21:33.302: INFO: Pod "pvc-volume-tester-writer-c7xsm": Phase="Pending", Reason="", readiness=false. Elapsed: 29.652118ms
Jun  4 08:21:35.334: INFO: Pod "pvc-volume-tester-writer-c7xsm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.060948881s
Jun  4 08:21:37.365: INFO: Pod "pvc-volume-tester-writer-c7xsm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.092380235s
Jun  4 08:21:39.400: INFO: Pod "pvc-volume-tester-writer-c7xsm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.127009027s
Jun  4 08:21:41.431: INFO: Pod "pvc-volume-tester-writer-c7xsm": Phase="Pending", Reason="", readiness=false. Elapsed: 8.158684301s
Jun  4 08:21:43.463: INFO: Pod "pvc-volume-tester-writer-c7xsm": Phase="Pending", Reason="", readiness=false. Elapsed: 10.190493072s
... skipping 7 lines ...
Jun  4 08:21:59.714: INFO: Pod "pvc-volume-tester-writer-c7xsm": Phase="Pending", Reason="", readiness=false. Elapsed: 26.441730445s
Jun  4 08:22:01.746: INFO: Pod "pvc-volume-tester-writer-c7xsm": Phase="Pending", Reason="", readiness=false. Elapsed: 28.473412061s
Jun  4 08:22:03.777: INFO: Pod "pvc-volume-tester-writer-c7xsm": Phase="Pending", Reason="", readiness=false. Elapsed: 30.504565556s
Jun  4 08:22:05.809: INFO: Pod "pvc-volume-tester-writer-c7xsm": Phase="Pending", Reason="", readiness=false. Elapsed: 32.536121601s
Jun  4 08:22:07.840: INFO: Pod "pvc-volume-tester-writer-c7xsm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.567642917s
STEP: Saw pod success
Jun  4 08:22:07.840: INFO: Pod "pvc-volume-tester-writer-c7xsm" satisfied condition "Succeeded or Failed"
Jun  4 08:22:07.902: INFO: Pod pvc-volume-tester-writer-c7xsm has the following logs: 
Jun  4 08:22:07.902: INFO: Deleting pod "pvc-volume-tester-writer-c7xsm" in namespace "provisioning-7723"
Jun  4 08:22:07.940: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-c7xsm" 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-49-5.us-east-2.compute.internal"
Jun  4 08:22:08.066: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-z84j8" in namespace "provisioning-7723" to be "Succeeded or Failed"
Jun  4 08:22:08.095: INFO: Pod "pvc-volume-tester-reader-z84j8": Phase="Pending", Reason="", readiness=false. Elapsed: 29.541439ms
Jun  4 08:22:10.129: INFO: Pod "pvc-volume-tester-reader-z84j8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.063146615s
Jun  4 08:22:12.162: INFO: Pod "pvc-volume-tester-reader-z84j8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.0961631s
Jun  4 08:22:14.193: INFO: Pod "pvc-volume-tester-reader-z84j8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.126974298s
STEP: Saw pod success
Jun  4 08:22:14.193: INFO: Pod "pvc-volume-tester-reader-z84j8" satisfied condition "Succeeded or Failed"
Jun  4 08:22:14.259: INFO: Pod pvc-volume-tester-reader-z84j8 has the following logs: hello world

Jun  4 08:22:14.259: INFO: Deleting pod "pvc-volume-tester-reader-z84j8" in namespace "provisioning-7723"
Jun  4 08:22:14.294: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-z84j8" to be fully deleted
Jun  4 08:22:14.326: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-lpczs] to have phase Bound
Jun  4 08:22:14.373: INFO: PersistentVolumeClaim pvc-lpczs found and phase=Bound (47.219458ms)
... skipping 508 lines ...
Jun  4 08:21:39.193: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-341-e2e-scn65cd
STEP: creating a claim
Jun  4 08:21:39.223: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-t2s5
STEP: Creating a pod to test atomic-volume-subpath
Jun  4 08:21:39.315: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-t2s5" in namespace "provisioning-341" to be "Succeeded or Failed"
Jun  4 08:21:39.344: INFO: Pod "pod-subpath-test-dynamicpv-t2s5": Phase="Pending", Reason="", readiness=false. Elapsed: 28.824559ms
Jun  4 08:21:41.373: INFO: Pod "pod-subpath-test-dynamicpv-t2s5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.058569163s
Jun  4 08:21:43.404: INFO: Pod "pod-subpath-test-dynamicpv-t2s5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.089333544s
Jun  4 08:21:45.435: INFO: Pod "pod-subpath-test-dynamicpv-t2s5": Phase="Pending", Reason="", readiness=false. Elapsed: 6.12040616s
Jun  4 08:21:47.465: INFO: Pod "pod-subpath-test-dynamicpv-t2s5": Phase="Pending", Reason="", readiness=false. Elapsed: 8.149742074s
Jun  4 08:21:49.494: INFO: Pod "pod-subpath-test-dynamicpv-t2s5": Phase="Pending", Reason="", readiness=false. Elapsed: 10.179132946s
... skipping 11 lines ...
Jun  4 08:22:13.871: INFO: Pod "pod-subpath-test-dynamicpv-t2s5": Phase="Running", Reason="", readiness=true. Elapsed: 34.555837348s
Jun  4 08:22:15.901: INFO: Pod "pod-subpath-test-dynamicpv-t2s5": Phase="Running", Reason="", readiness=true. Elapsed: 36.585985973s
Jun  4 08:22:17.930: INFO: Pod "pod-subpath-test-dynamicpv-t2s5": Phase="Running", Reason="", readiness=true. Elapsed: 38.615373259s
Jun  4 08:22:19.962: INFO: Pod "pod-subpath-test-dynamicpv-t2s5": Phase="Running", Reason="", readiness=true. Elapsed: 40.647058714s
Jun  4 08:22:21.992: INFO: Pod "pod-subpath-test-dynamicpv-t2s5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 42.677355769s
STEP: Saw pod success
Jun  4 08:22:21.992: INFO: Pod "pod-subpath-test-dynamicpv-t2s5" satisfied condition "Succeeded or Failed"
Jun  4 08:22:22.021: INFO: Trying to get logs from node ip-172-20-49-219.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-t2s5 container test-container-subpath-dynamicpv-t2s5: <nil>
STEP: delete the pod
Jun  4 08:22:22.104: INFO: Waiting for pod pod-subpath-test-dynamicpv-t2s5 to disappear
Jun  4 08:22:22.133: INFO: Pod pod-subpath-test-dynamicpv-t2s5 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-t2s5
Jun  4 08:22:22.133: INFO: Deleting pod "pod-subpath-test-dynamicpv-t2s5" in namespace "provisioning-341"
... skipping 55 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  4 08:22:10.032: 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.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Jun  4 08:22:10.183: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  4 08:22:10.183: INFO: Creating resource for dynamic PV
Jun  4 08:22:10.183: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8348fxkcw
STEP: creating a claim
Jun  4 08:22:10.213: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-fczn
STEP: Checking for subpath error in container status
Jun  4 08:22:38.368: INFO: Deleting pod "pod-subpath-test-dynamicpv-fczn" in namespace "provisioning-8348"
Jun  4 08:22:38.403: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-fczn" to be fully deleted
STEP: Deleting pod
Jun  4 08:22:50.465: INFO: Deleting pod "pod-subpath-test-dynamicpv-fczn" in namespace "provisioning-8348"
STEP: Deleting pvc
Jun  4 08:22:50.561: INFO: Deleting PersistentVolumeClaim "awssd95p"
... skipping 12 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.HvoHaXSxC/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.HvoHaXSxC/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.HvoHaXSxC/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.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
------------------------------
S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
... skipping 533 lines ...
Jun  4 08:22:00.489: INFO: Creating resource for dynamic PV
Jun  4 08:22:00.489: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5616wfkd9
STEP: creating a claim
Jun  4 08:22:00.519: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod to format volume volume-prep-provisioning-5616
Jun  4 08:22:00.612: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-5616" in namespace "provisioning-5616" to be "Succeeded or Failed"
Jun  4 08:22:00.642: INFO: Pod "volume-prep-provisioning-5616": Phase="Pending", Reason="", readiness=false. Elapsed: 30.031829ms
Jun  4 08:22:02.672: INFO: Pod "volume-prep-provisioning-5616": Phase="Pending", Reason="", readiness=false. Elapsed: 2.060289015s
Jun  4 08:22:04.704: INFO: Pod "volume-prep-provisioning-5616": Phase="Pending", Reason="", readiness=false. Elapsed: 4.09180279s
Jun  4 08:22:06.736: INFO: Pod "volume-prep-provisioning-5616": Phase="Pending", Reason="", readiness=false. Elapsed: 6.123835104s
Jun  4 08:22:08.767: INFO: Pod "volume-prep-provisioning-5616": Phase="Pending", Reason="", readiness=false. Elapsed: 8.155758321s
Jun  4 08:22:10.800: INFO: Pod "volume-prep-provisioning-5616": Phase="Pending", Reason="", readiness=false. Elapsed: 10.187939866s
Jun  4 08:22:12.836: INFO: Pod "volume-prep-provisioning-5616": Phase="Pending", Reason="", readiness=false. Elapsed: 12.224195103s
Jun  4 08:22:14.868: INFO: Pod "volume-prep-provisioning-5616": Phase="Pending", Reason="", readiness=false. Elapsed: 14.25617476s
Jun  4 08:22:16.899: INFO: Pod "volume-prep-provisioning-5616": Phase="Pending", Reason="", readiness=false. Elapsed: 16.286869875s
Jun  4 08:22:18.930: INFO: Pod "volume-prep-provisioning-5616": Phase="Pending", Reason="", readiness=false. Elapsed: 18.318030391s
Jun  4 08:22:20.961: INFO: Pod "volume-prep-provisioning-5616": Phase="Pending", Reason="", readiness=false. Elapsed: 20.349144516s
Jun  4 08:22:22.992: INFO: Pod "volume-prep-provisioning-5616": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.379829521s
STEP: Saw pod success
Jun  4 08:22:22.992: INFO: Pod "volume-prep-provisioning-5616" satisfied condition "Succeeded or Failed"
Jun  4 08:22:22.992: INFO: Deleting pod "volume-prep-provisioning-5616" in namespace "provisioning-5616"
Jun  4 08:22:23.025: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-5616" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-b8dd
STEP: Checking for subpath error in container status
Jun  4 08:22:41.147: INFO: Deleting pod "pod-subpath-test-dynamicpv-b8dd" in namespace "provisioning-5616"
Jun  4 08:22:41.187: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-b8dd" to be fully deleted
STEP: Deleting pod
Jun  4 08:22:41.218: INFO: Deleting pod "pod-subpath-test-dynamicpv-b8dd" in namespace "provisioning-5616"
STEP: Deleting pvc
Jun  4 08:22:41.308: INFO: Deleting PersistentVolumeClaim "awsr2kpr"
... skipping 196 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  4 08:23:00.796: 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.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
Jun  4 08:23:00.950: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
STEP: creating a test aws volume
Jun  4 08:23:01.385: INFO: Successfully created a new PD: "aws://us-east-2a/vol-02a6d60002fec64ef".
Jun  4 08:23:01.385: INFO: Creating resource for pre-provisioned PV
Jun  4 08:23:01.385: INFO: Creating PVC and PV
... skipping 4 lines ...
Jun  4 08:23:03.591: INFO: PersistentVolumeClaim pvc-h58rl found but phase is Pending instead of Bound.
Jun  4 08:23:05.623: INFO: PersistentVolumeClaim pvc-h58rl found but phase is Pending instead of Bound.
Jun  4 08:23:07.658: INFO: PersistentVolumeClaim pvc-h58rl found and phase=Bound (6.127547794s)
Jun  4 08:23:07.658: INFO: Waiting up to 3m0s for PersistentVolume aws-2t4dx to have phase Bound
Jun  4 08:23:07.691: INFO: PersistentVolume aws-2t4dx found and phase=Bound (32.6443ms)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jun  4 08:23:09.902: INFO: Deleting pod "pod-898a2838-c1d6-4cbc-a564-7d107101b784" in namespace "volumemode-8456"
Jun  4 08:23:09.951: INFO: Wait up to 5m0s for pod "pod-898a2838-c1d6-4cbc-a564-7d107101b784" to be fully deleted
STEP: Deleting pv and pvc
Jun  4 08:23:24.019: INFO: Deleting PersistentVolumeClaim "pvc-h58rl"
Jun  4 08:23:24.050: INFO: Deleting PersistentVolume "aws-2t4dx"
Jun  4 08:23:24.227: INFO: Successfully deleted PD "aws://us-east-2a/vol-02a6d60002fec64ef".
... skipping 7 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.HvoHaXSxC/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.HvoHaXSxC/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
    /tmp/kops.HvoHaXSxC/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.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:296
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 90 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
Jun  4 08:22:44.249: 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.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Jun  4 08:22:44.396: INFO: In-tree plugin kubernetes.io/aws-ebs is not migrated, not validating any metrics
Jun  4 08:22:44.396: INFO: Creating resource for dynamic PV
Jun  4 08:22:44.396: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5667ldhmk
STEP: creating a claim
Jun  4 08:22:44.428: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-q9sp
STEP: Checking for subpath error in container status
Jun  4 08:23:08.618: INFO: Deleting pod "pod-subpath-test-dynamicpv-q9sp" in namespace "provisioning-5667"
Jun  4 08:23:08.649: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-q9sp" to be fully deleted
STEP: Deleting pod
Jun  4 08:23:22.707: INFO: Deleting pod "pod-subpath-test-dynamicpv-q9sp" in namespace "provisioning-5667"
STEP: Deleting pvc
Jun  4 08:23:22.796: INFO: Deleting PersistentVolumeClaim "aws5qnvj"
... skipping 13 lines ...
[ebs-csi-migration] EBS CSI Migration
/tmp/kops.HvoHaXSxC/tests/e2e-kubernetes/e2e_test.go:85
  [Driver: aws]
  /tmp/kops.HvoHaXSxC/tests/e2e-kubernetes/e2e_test.go:91
    [Testpattern: Dynamic PV (default fs)] subPath
    /tmp/kops.HvoHaXSxC/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.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 78 lines ...
Jun  4 08:23:04.172: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(aws) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-323727v8
STEP: creating a claim
Jun  4 08:23:04.203: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
STEP: Creating pod pod-subpath-test-dynamicpv-dmk2
STEP: Creating a pod to test subpath
Jun  4 08:23:04.303: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-dmk2" in namespace "provisioning-323" to be "Succeeded or Failed"
Jun  4 08:23:04.333: INFO: Pod "pod-subpath-test-dynamicpv-dmk2": Phase="Pending", Reason="", readiness=false. Elapsed: 29.785329ms
Jun  4 08:23:06.364: INFO: Pod "pod-subpath-test-dynamicpv-dmk2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061187106s
Jun  4 08:23:08.395: INFO: Pod "pod-subpath-test-dynamicpv-dmk2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.091960947s
Jun  4 08:23:10.427: INFO: Pod "pod-subpath-test-dynamicpv-dmk2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.124059604s
Jun  4 08:23:12.459: INFO: Pod "pod-subpath-test-dynamicpv-dmk2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.155742154s
Jun  4 08:23:14.490: INFO: Pod "pod-subpath-test-dynamicpv-dmk2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.186656414s
Jun  4 08:23:16.521: INFO: Pod "pod-subpath-test-dynamicpv-dmk2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.218290922s
STEP: Saw pod success
Jun  4 08:23:16.521: INFO: Pod "pod-subpath-test-dynamicpv-dmk2" satisfied condition "Succeeded or Failed"
Jun  4 08:23:16.551: INFO: Trying to get logs from node ip-172-20-49-219.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-dmk2 container test-container-subpath-dynamicpv-dmk2: <nil>
STEP: delete the pod
Jun  4 08:23:16.621: INFO: Waiting for pod pod-subpath-test-dynamicpv-dmk2 to disappear
Jun  4 08:23:16.651: INFO: Pod pod-subpath-test-dynamicpv-dmk2 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-dmk2
Jun  4 08:23:16.651: INFO: Deleting pod "pod-subpath-test-dynamicpv-dmk2" in namespace "provisioning-323"
STEP: Creating pod pod-subpath-test-dynamicpv-dmk2
STEP: Creating a pod to test subpath
Jun  4 08:23:16.714: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-dmk2" in namespace "provisioning-323" to be "Succeeded or Failed"
Jun  4 08:23:16.744: INFO: Pod "pod-subpath-test-dynamicpv-dmk2": Phase="Pending", Reason="", readiness=false. Elapsed: 30.014849ms
Jun  4 08:23:18.776: INFO: Pod "pod-subpath-test-dynamicpv-dmk2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061724079s
Jun  4 08:23:20.807: INFO: Pod "pod-subpath-test-dynamicpv-dmk2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.092987008s
Jun  4 08:23:22.838: INFO: Pod "pod-subpath-test-dynamicpv-dmk2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.123898439s
STEP: Saw pod success
Jun  4 08:23:22.838: INFO: Pod "pod-subpath-test-dynamicpv-dmk2" satisfied condition "Succeeded or Failed"
Jun  4 08:23:22.868: INFO: Trying to get logs from node ip-172-20-49-219.us-east-2.compute.internal pod pod-subpath-test-dynamicpv-dmk2 container test-container-subpath-dynamicpv-dmk2: <nil>
STEP: delete the pod
Jun  4 08:23:22.935: INFO: Waiting for pod pod-subpath-test-dynamicpv-dmk2 to disappear
Jun  4 08:23:22.965: INFO: Pod pod-subpath-test-dynamicpv-dmk2 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-dmk2
Jun  4 08:23:22.965: INFO: Deleting pod "pod-subpath-test-dynamicpv-dmk2" in namespace "provisioning-323"
... skipping 1001 lines ...
      /tmp/kops.HvoHaXSxC/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/ephemeral.go:173
------------------------------


Summarizing 2 Failures:

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

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

Ran 141 of 485 Specs in 516.000 seconds
FAIL! -- 139 Passed | 2 Failed | 0 Pending | 344 Skipped


Ginkgo ran 1 suite in 9m39.172256078s
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
I0604 08:24:47.801495   26804 app.go:59] RunDir for this run: "/logs/artifacts/f46fc0f3-c50a-11eb-b207-42879ebc49dd"
I0604 08:24:47.801649   26804 app.go:90] ID for this run: "f46fc0f3-c50a-11eb-b207-42879ebc49dd"
I0604 08:24:47.801679   26804 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
I0604 08:24:47.815286   26810 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
... skipping 1459 lines ...